Android thread V-garychencool finally rooted his phone and got ICS edition - Hardware & Software

[QUOTE=Van-man;37734428]Still great they're being integrated. Hoping they'll be merged in the Android mainline soon, along with a proper port to x86.[/QUOTE] Google have all these amazing projects thrown at them but they just don't care.

[QUOTE=PyroCF;37734433]Google have all these amazing projects thrown at them but they just don't care.[/QUOTE] It's like they [B]WANT[/B] Android to end up as a mediocre mobile Operating System.

[QUOTE=Van-man;37734561]It's like they [B]WANT[/B] Android to end up as a mediocre mobile Operating System.[/QUOTE] Next major update better be a re-write. They've found their UI style with holo and that now.

[QUOTE=PyroCF;37734576]Next major update better be a re-write. They've found their UI style with holo and that now.[/QUOTE] C/C++ instead of [I]javajavajava[/I] wannabe. [I]PleasepleasePLEEAASSEEEE!![/I]

[QUOTE=Van-man;37734606]C/C++ instead of [I]javajavajava[/I] wannabe. [I]PleasepleasePLEEAASSEEEE!![/I][/QUOTE] What's the incentive to do so until Android growth starts to slow?

My Nexus 7 is in transit and should arrive today or tomorrow. Not that I'll be around during office hours to pick it up unfortunately. And why is DHL trusted with fragile objects? When our suppliers send my (liquor) store stuff via them its guaranteed that a quarter of what we get arrives broken (wine bottles) per box. Not that my tablet is being sent by them, it was $30 for 3-8 day delivery via dhl or $7 for 1-2 day express delivery by Canada Post

[QUOTE=Van-man;37734606]C/C++ instead of [I]javajavajava[/I] wannabe. [I]PleasepleasePLEEAASSEEEE!![/I][/QUOTE] Imagine if Google decided to add both C and Java support for apps, best of both worlds. Then make system apps like Framework-ui written in C for mega smoothness

[QUOTE=K1ngo64;37735138]Imagine if Google decided to add both C and Java support for apps, best of both worlds. Then make system apps like Framework-ui written in C for mega smoothness[/QUOTE] They can just keep Dalvik for app compatibility.

I feel like I'm the only person in this thread who doesn't really care what programming language is Android written in.

[QUOTE=iCole;37735485]I feel like I'm the only person in this thread who doesn't really care what programming language is Android written in.[/QUOTE] You would if you've ever used android side by side with windows phone 7

[QUOTE=Sgt. Jerky;37735686]You would if you've ever used android side by side with windows phone 7[/QUOTE] Or if you're not so bothered about it being 60FPS constantly

I know about the speed difference, but I knew about that before I bought an Android phone, and I still went for Android. Plus, since then, Android speed has improved dramatically and I bet that Project Butter was just the beginning, although I don't think we'll see dramatic rewrites.

The HTC desire Z wins my "worst phone I've ever used" award Restarted for no reason all of today a long with it being so insanely slow, heavy, and having a loose hinge makes me want to throw it out the window I MUCH preferred using my Nokia E63, except I'm hooked on certain android features so I can't leave

So me and some friends are fixing a Samsung Galaxy S Capative and it broke during Kies firmware update, can't even boot into download/recovery mode -_- It's a pretty old phone.

[QUOTE=iCole;37735485]I feel like I'm the only person in this thread who doesn't really care what programming language is Android written in.[/QUOTE] because native code is much faster than bytecode executed by a VM.

The move to another language is probably too big of a move to even seriously consider. to the outside world it would seem like they made a mistake with java and that they're desperately trying to fix it with the other language. best option for them is to insanely optimize dalvik

[QUOTE=Oicani Gonzales;37737138]i wont lie, i am when i got my gnex i was really worried about how slow it was. [B]the big problem here is that i use this chrome addon that makes all smooth movement at 60fps[/B], so im kinda used to it when i put jelly bean on it, though, it was amazing and i wouldnt change my os to anything else[/QUOTE] Do share!

[QUOTE=garrynohome;37734700]What's the incentive to do so until Android growth starts to slow?[/QUOTE] Shutting up every person who complains about the sluggishness of the UI, and wasted performance compared to the hardware used. AKA a minority and Apple fanatics (though the latter will whine about [B]ANYTHING[/B] not Apple). [QUOTE=FPtje;37737058]The move to another language is probably too big of a move to even seriously consider. to the outside world it would seem like they made a mistake with java and that they're desperately trying to fix it with the other language. [B]best option for them is to insanely optimize dalvik[/B][/QUOTE] It's Java (based), that's like polishing a turd. Android has [I]"outgrown"[/I] it and needs something more efficient than that.

[QUOTE=FPtje;37737058]The move to another language is probably too big of a move to even seriously consider. to the outside world it would seem like they made a mistake with java and that they're desperately trying to fix it with the other language. best option for them is to insanely optimize dalvik[/QUOTE] Where does this idea come from? I'll link it again because people seem to not ignore it. [url]http://blog.xamarin.com/2012/05/01/android-in-c-sharp/[/url] A random software company did this THEMSELVES! The idea that Google couldn't do it because it's too big of a move had no basis at all, it's simply Google not wanting to do so. Redo it in a better language, have some sort of emulation layer for compatibility with legacy apps from all previous versions.

well it won't be c# that's for sure Microsoft would be pissed

[QUOTE=Oicani Gonzales;37737228][url]https://github.com/galambalazs/smoothscroll[/url] [editline]20th September 2012[/editline] chrome theoretically has it too but i never tried it and it isnt as customizable chrome://flags/[/QUOTE] This is just a modified form of scrolling where it's a form of continuous movement instead of how browsers typically scroll in chunks corresponding with a degree of movement on the mouse wheel. It doesn't magically bring the browser up to 60fps. [editline]20th September 2012[/editline] [QUOTE=Ezhik;37738177]well it won't be c# that's for sure Microsoft would be pissed[/QUOTE] Yah I get that, it's just an example of how porting it to another language is not some job that'll take forever like people keep pretending it is to try and give themselves some sort of false justification as to why it hasn't been done already. [editline]20th September 2012[/editline] Oh and to be fair, the UI seems fine to me now. It's the DAMN APPS! The fucking apps are your worst nightmare even more so now because you go from this great smooth UI to something that gives me flashbacks to my old Palm Pre.

[QUOTE=garrynohome;37738186]Oh and to be fair, the UI seems fine to me now. It's the DAMN APPS! The fucking apps are your worst nightmare even more so now because you go from this great smooth UI to something that gives me flashbacks to my old Palm Pre.[/QUOTE] Java :rolleyes: And also a dash or two of inefficient coding techniques from the app developers side..

[QUOTE=Van-man;37738372]Java :rolleyes: And also a dash or two of inefficient coding techniques from the app developers side..[/QUOTE] Yup it sucks. I think a lot of what Google was trying to do early on was to build an OS without simultaneously thinking about what exactly this OS was going to run on. Oh and I mean they borrowed the whole multitouch idea from Apple after the iPhone launched instead of making Android into a trackball+keyboard Blackberry style OS like it was intended so that probably doesn't help performance with response time and when the OS tries to process stuff and do touch movement at the same time.

[QUOTE=Lyoko774;37735693]Or if you're not so bothered about it being 60FPS constantly[/QUOTE] A little background - I'm a graphics artist that has worked on UIs for mobile platforms. I know my beef with a phone's responsiveness may be extremely nitpicky, but when I spend my time designing an interface to be as user friendly as possible, I don't want that experience marred by an issue in the underlying framework of the platform. I don't care so much about a constant 60fps as much as I do the microstutter anytime I'm scrolling in an application. The scrolling isn't as smooth as I would expect it to be. A lot of the time jitters quite severely (especially when trying to handle background data) - even though my Galaxy Nexus is a dual-core machine OC'd to 1.6ghz per core, with a full 1GB of system ram. All of that is twice the clock speed and ram capacity as the iPhone 4s which (from my experiences) suffers from microstuttering far, far less. That said, things HAVE gotten significantly better with Jellybean's release and a few framework.jar tweaks (namely disabling the scroll cache system-wide), but it's still not as "buttery smooth" as Google lead me to believe it was going to be with Project Butter. [B]EDIT:[/B] Also, don't get me wrong - I would never, ever trade my Android experience for anything else out there. Google Now is probably the most amazing piece of software I've had the pleasure of experiencing. The first time I saw the notification popup showing me the directions to my new job, and when I needed to leave my house in order to arrive on time made me feel fuzzy all over. I have been a diehard fan since I first got my hands on the OG Droid, and while certain improvements in JB have really made my phone feel worthy of the "smartphone" title, I just know that the OS is capable of so, so much more than it is currently handling performance wise.

Question for anyone reading or posting here. What brightness do you run your phones/tablets at? I've always just run em at full and they last a work/school day so I've never needed to lower it. But people always seem to complain about brightness killing their battery life so I was wondering what people set it to. I hear a lot of people saying they use autobrightness but [url=http://www.displaymate.com/AutoBrightness_Controls_2.htm]it's not the best idea.[/url]

[QUOTE=garrynohome;37739596]Question for anyone reading or posting here. What brightness do you run your phones/tablets at? I've always just run em at full and they last a work/school day so I've never needed to lower it. But people always seem to complain about brightness killing their battery life so I was wondering what people set it to. I hear a lot of people saying they use autobrightness but [URL="http://www.displaymate.com/AutoBrightness_Controls_2.htm"]it's not the best idea.[/URL][/QUOTE] I usually run mine on auto or about 1/3 of the way up. The Galaxy Nexus screen eats battery like no other.

[QUOTE=garrynohome;37739596]Question for anyone reading or posting here. What brightness do you run your phones/tablets at? I've always just run em at full and they last a work/school day so I've never needed to lower it. But people always seem to complain about brightness killing their battery life so I was wondering what people set it to. I hear a lot of people saying they use autobrightness but [URL="http://www.displaymate.com/AutoBrightness_Controls_2.htm"]it's not the best idea.[/URL][/QUOTE] Auto-Brightness but SiyahKernel has some funky stuff to 'fix' it which works pretty well.

[QUOTE=garrynohome;37739596]Question for anyone reading or posting here. What brightness do you run your phones/tablets at? I've always just run em at full and they last a work/school day so I've never needed to lower it. But people always seem to complain about brightness killing their battery life so I was wondering what people set it to. I hear a lot of people saying they use autobrightness but [url=http://www.displaymate.com/AutoBrightness_Controls_2.htm]it's not the best idea.[/url][/QUOTE] I always have mine set to the lowest it can go. I get crushing headaches otherwise, it was so bad that I had to actually and go into my framework and DECREASE the lowest available brightness from 10 to 2. Everyone always complains when they use my phone that my screen is way too dark though. On the plus side I can get about 2-3 days of use/4ish hours of screen-on time :v:

[QUOTE=garrynohome;37739596]Question for anyone reading or posting here. What brightness do you run your phones/tablets at? I've always just run em at full and they last a work/school day so I've never needed to lower it. But people always seem to complain about brightness killing their battery life so I was wondering what people set it to. I hear a lot of people saying they use autobrightness but [url=http://www.displaymate.com/AutoBrightness_Controls_2.htm]it's not the best idea.[/url][/QUOTE] I never even go close half at this time, probably because it's dark and gloomy (cloudy). But during the summer time when I need to be able to see what I'm tapping, I turn it up. In general, it's often at 1/4 or lower, but up to 3/4. The only time I ever used full brightness is on super sunny days and I can't see shit when I'm taking photos. Either way, I usually keep it low. Saves power on LED-backlite LCD screen. Oh and here's a protip for the one's who can't turn down the brightness any lower due to the rom or whatever, if you don't have root use Screen Filter or other variants. If you are rooted, use RootDim. [url]https://play.google.com/store/apps/details?id=mobi.pruss.superdim[/url] I was able to dim it down from 30 to 8. Screen filter just adds grey.

Used to have it at lowest, a bit above lowest. Used screen filter at 40% at night added onto the lowest stock brightness. Have yet to see how long the phone lasts now with CM9 though.