[QUOTE=sdwise;40073030]I disagree. Battery tech isn't there yet and "optimizing" the software while still skinning the fuck out of it would prolong the update cycle even more.
I don't know if you experienced the Maxx on Gingerbread, but that fucker would go 8 hours of my use (which is heavy/moderate to very heavy) and I'd get home with 50% left. If motorolas software division hadn't fucked the dog with ICS, it could have run just as well.
And the phone, while a bit big (not so much in the latest iterations), is very comfortable. Feels a hell of a lot better than any of the latest samsung devices I've felt.[/QUOTE]
I was referring to the iPhone and windows phones that do way better than android phones per mAh. I wasn't comparing it to other skinned android devices.
[QUOTE=Kaabii;40073052]I was referring to the iPhone and windows phones that do way better than android phones per mAh. I wasn't comparing it to other skinned android devices.[/QUOTE]
My maxx on gingerbread would outlast my friend's iPhone 4S every day.
And I think part of the reason windows and ios devices tend to have more optimized software is that iOS and Windows mobile os doesn't really iterate as often as Android, so there's more time to work on it. They also run clean. Just the stock OS. Everyone really except Moto make these hugely invasive UI overlays that have to be redone for each iteration of android and their own iterations.
What I'm getting at is, with the tech that exists, I think sticking a 3300 mAh battery in a lightly-skinned phone is the most sensible way to make a long-life smartphone on Android.
[QUOTE=sdwise;40073114]My maxx on gingerbread would outlast my friend's iPhone 4S every day. And I think part of that is that iOS and Windows mobile os doesn't really iterate as often as Android, so there's more time to work on it. They also run clean. Just the stock OS. Everyone really except Moto make these hugely invasive UI overlays that have to be redone for each iteration of android and their own iterations.
What I'm getting at is, with the tech that exists, I think sticking a 3300 mAh battery in a lightly-skinned phone is the most sensible way to make a long-life smartphone on Android.[/QUOTE]
That's the point that makes sense. On android, it's the best method. It's honestly not necessary elsewhere.
Also I've been wondering. Why does Motorola have any skin at all? Why not just use stock android since you're already pretty close to it anyway.
[QUOTE=Kaabii;40073132]That's the point that makes sense. On android, it's the best method. It's honestly not necessary elsewhere.[/QUOTE]
Absolutely. I wouldnt try to apply a strategy that works in the android ecosystem to another ecosystem. iOS, windows, and android are all dispersed in very unique ways.
[editline]28th March 2013[/editline]
[QUOTE=Kaabii;40073150]Also I've been wondering. Why does Motorola have any skin at all? Why not just use stock android since you're already pretty close to it anyway.[/QUOTE]
They're moving that way. The only real difference between the RAZR's 4.1 and stock 4.1 is the settings menu has colored icons, the notification bar looks different, and the lockscreen is ugly as fuck.
Blur is slowly going away. I think the only reason its still there is because Google can't put 100% vanilla on an "in house" device. It would disenfranchise the other OEMs.
[editline]28th March 2013[/editline]
Motorola still competes with the likes of samsung. If google were to say "fuck it, motorola runs stock", the other companies would see that as not only an unfair advantage (and thus be more likely to pull away from the core of android), but those in the Nexus program would feel fucked out of a deal.
[QUOTE=FlubberNugget;40072278]I remember letting out a high pitched squee when I first held my nexus 7, such a step up from my Desire HD :v:[/QUOTE]
I remember when I got mine, I was calling all over the city and couldn't find one. Then I called Staples and they didn't think they had any, though it turned out they had one left. As soon as I got off the phone, I hopped in the car and picked it up. It was sooo much smoother than my Nexus S I had at the time.
[QUOTE=Kaabii;40072974]A 3300mAh battery isn't how long life smartphones should be done. Having optimized software that doesn't suck and getting the same battery life with 1400-1500mAh is how it should be done.[/QUOTE]
It's a shame Java is so slow. Android needs to be rewritten.
[QUOTE=kaze4159;40071115][img]http://imgkk.com/i/9wa3.jpg[/img]
Already simmering[/QUOTE]
oh shit, not the premium soy sauce!
[QUOTE=jaybuz;40073526]It's a shame Java is so slow. Android needs to be rewritten.[/QUOTE]
Thats kind of what Butter tried to do. Worked on some devices.
Really, when it comes to software optimization, OEMs are more interested in skinning android than making it run well.
Additionally, Android is kind of bleeding edge as far as mobile operating systems go, meaning it usually outpaces the hardware thats actually on the market. Comes with being the most updated.
I believe the only reason why Android is slow is because it's running a virtual machine and Java has always been a resource hog. Native code = faster
I don't see them rewriting android, though. They've got 8 full iterations and more .x updates built on it. They're not gonna rebuild it.
Every other mobile OS is so smooth compared to Android. It's makes me sad :(.
[QUOTE=garychencool;40073582]I believe the only reason why Android is slow is because it's running a virtual machine and Java has always been a resource hog. Native code = faster[/QUOTE]
the Davlik VM seemns a bit better than the standard JVM at resources in many cases
[del]I have a Motorola Droid 4 and I just updated to 4.1.2 (I think?). I was perfectly fine until I started typing (Droid 4 has a physical keyboard, for those unaware) and I'm pissed as fuck now. Prior to the update, pressing shift once would change it from "abc" to "Abc," so the first letter typed would be capital. Now, I have to hold it in order to type a capital letter. This is extremely annoying for the left half of the keyboard. Is there any way to revert this or something?[/del]
Got it working. If you go to Language & Input and click the cog next to the Android Keyboard, you can scroll down and uncheck "Popup on keypress" and you have your old shift-key function. Yay, Google!
--
Just kidding, now it's not working.
[QUOTE=garychencool;40073582]I believe the only reason why Android is slow is because it's running a virtual machine and Java has always been a resource hog. Native code = faster[/QUOTE]
Many custom ROMs, at least for my N4, have bionic patches, which, as far as I can tell, replace java libraries with chip-specific native code versions, which gives a huge speed boost to the relevant instructions.
[QUOTE=Unisath;40074168]I have a Motorola Droid 4 and I just updated to 4.1.2 (I think?). I was perfectly fine until I started typing (Droid 4 has a physical keyboard, for those unaware) and I'm pissed as fuck now. Prior to the update, pressing shift once would change it from "abc" to "Abc," so the first letter typed would be capital. Now, I have to hold it in order to type a capital letter. This is extremely annoying for the left half of the keyboard. Is there any way to revert this or something?[/QUOTE]
II would suggest googling. I bet there's a droidforums post about it on something.
[QUOTE=mblunk;40074224]Many custom ROMs, at least for my N4, have bionic patches, which, as far as I can tell, replace java libraries with chip-specific native code versions, which gives a huge speed boost to the relevant instructions.[/QUOTE]
carrier forever locked bootloader :(
[QUOTE=garychencool;40074314]carrier forever locked bootloader :([/QUOTE]
Need a "know that feel" rating.
[QUOTE=sdwise;40074396]Need a "know that feel" rating.[/QUOTE]
friendly rating is the equivalent.
[QUOTE=garychencool;40074314]carrier forever locked bootloader :([/QUOTE]
I miss tethering.
I can tether and do everything else with root but not install custom roms and all of that cool shit :\
So my Nexus 7 came in a few hours ago and I've been setting it up since. Apparently they don't give free movies or $25 credits like I was let to believe but whatever.
[QUOTE=Jurikuer;40075546]So my Nexus 7 came in a few hours ago and I've been setting it up since. Apparently they don't give free movies or $25 credits like I was let to believe but whatever.[/QUOTE]
That was like, forever ago, when it first launched.
[editline]28th March 2013[/editline]
[QUOTE=sdwise;40073576]Thats kind of what Butter tried to do. Worked on some devices.
Really, when it comes to software optimization, OEMs are more interested in skinning android than making it run well.
Additionally, Android is kind of bleeding edge as far as mobile operating systems go, meaning it usually outpaces the hardware thats actually on the market. Comes with being the most updated.[/QUOTE]
OK first of all, butter really isn't better code. Look at the RAM usage for JB vs ICS, a ton of RAM is being used for HW acceleration and it's why 512MB devices don't really get any boost from JB, and actually can get worse.
Second of all, saying it's bleeding edge is trying to praise something that is a failure of software design, and it's not even a valid explaination. The real situation is Apple and Microsoft designed operating systems to work with the hardware that goes into phones and so their operating systems run well, while Google has what could basically be called a streamlined Linux with absolutely no regard for what it has to run on. That is NOT a good thing. Now adding features and capability is great, but that's not the reason and that's the problem.
Now why is calling it bleeding edge not valid? Because a jailbroken iOS device, or one of the Gen 1 Windows Phones that were able to get a "windowbreak" can do pretty much anything an Android device can, and the device will still keep running seamlessly on something like two Cortex-A9 cores and 512MB of RAM. There is no validity in putting Android's issues to it being so bleeding edge that it's just so far ahead of the hardware that exists. It's laziness, lack of quality, nothing more.
[QUOTE=Jurikuer;40075546]So my Nexus 7 came in a few hours ago and I've been setting it up since. Apparently they don't give free movies or $25 credits like I was let to believe but whatever.[/QUOTE]
They stopped that promotion way back last september
[QUOTE=Kaabii;40075685]That was like, forever ago, when it first launched.
[editline]28th March 2013[/editline]
OK first of all, butter really isn't better code. Look at the RAM usage for JB vs ICS, a ton of RAM is being used for HW acceleration and it's why 512MB devices don't really get any boost from JB, and actually can get worse.
Second of all, saying it's bleeding edge is trying to praise something that is a failure of software design, and it's not even a valid explaination. The real situation is Apple and Microsoft designed operating systems to work with the hardware that goes into phones and so their operating systems run well, while Google has what could basically be called a streamlined Linux with absolutely no regard for what it has to run on. That is NOT a good thing. Now adding features and capability is great, but that's not the reason and that's the problem.
Now why is calling it bleeding edge not valid? Because a jailbroken iOS device, or one of the Gen 1 Windows Phones that were able to get a "windowbreak" can do pretty much anything an Android device can, and the device will still keep running seamlessly on something like two Cortex-A9 cores and 512MB of RAM. There is no validity in putting Android's issues to it being so bleeding edge that it's just so far ahead of the hardware that exists. It's laziness, lack of quality, nothing more.[/QUOTE]
Maybe I shouldve been more clear. They iterate android upward. They don't really cater to existing hardware when they release an update except [i]maybe[/i] the current nexus.
When I said "bleeding edge" I wasn't being a fanboy, I was referring to the hardware requirements to run the software being next-gen rather than current gen.
[QUOTE=Sergeant Turtle;40075953]They stopped that promotion way back last september[/QUOTE]
Yea but my email told me of a free copy of Ice Age. No where to be found. Doesn't matter, I have a few movies I can put on it.
[QUOTE=sdwise;40076046]Maybe I shouldve been more clear. They iterate android upward. They don't really cater to existing hardware when they release an update except [i]maybe[/i] the current nexus.
When I said "bleeding edge" I wasn't being a fanboy, I was referring to the hardware requirements to run the software being next-gen rather than current gen.[/QUOTE]
But there is no legitimate reason for the hardware requirements whatsoever. There isn't anything Android does that honestly requires four cortex A15 cores and 2GB of RAM. If Google had made an OS in some form of native code, for a closed hardware set, they could easily do it on two Krait cores, maybe even two Cortex-A9s, and with 512MB-1GB of RAM.
Meh. Flagships these days on Android are pretty much where they need to be in terms of smoothness.
[editline]28th March 2013[/editline]
Wow, Pocketnow is reporting that Sense 5 on the One has absolutely zero lag. I don't know if it's WP8 smooth, but it's probably Nexus 4/GS3 smooth or better.
And Engadget said the Galaxy Nexus on ICS was buttery smooth, but it wasn't and still isn't. I honestly want someone who has experience in FPS game benchmarking to take a look at these devices and give their opinions, because I hear "zero lag" and "buttery smooth" all the time from Android users when I see blatant framerate slowdowns and areas where animations will stutter on the same devices.
Also GS3 smooth is pretty much zero lag, in the launcher anyway. Unless you put like ten million badly programmed widgets.
[QUOTE=Jurikuer;40076193]Yea but my email told me of a free copy of Ice Age. No where to be found. Doesn't matter, I have a few movies I can put on it.[/QUOTE]
Did you check the play movies app? I'm fairly sure that's where the old free copy of Transformers popped up.
Sorry, you need to Log In to post a reply to this thread.