PDA

View Full Version : Android Lag, Even With Project Butter?




ReanimationN
Sep 29, 2012, 10:47 AM
Ever since the advent of Project Butter, Android is basically meant to be on a par with iOS when it comes to responsiveness, right? Has anyone found this isn't the case?

I know when I was looking at videos, trying to decide whether to get the Nexus 7 or not, the reviewers would show off the responsiveness of Project Butter as a key feature. To do this, they'd often flick between home screens or open up the browser and do quick flicks up and down the page. The Nexus, for the most part, does perform those actions very quickly, it's when you slow things down that it seems to fall apart.

The vast majority of the time I do my browsing by placing a finger on the screen and dragging up very slowly as I read down the page. The Nexus stutters and jerks constantly doing this, whereas the same action on an iOS device is perfectly smooth. It's not terrible stuttering, it's like the difference between scrolling in iTunes on OS X and Windows- Windows scrolling seems like it is taken in 'steps', where a song at a time goes past if you scroll (or 2 or more, depending on your scrolling speed), whereas OS X feels perfectly smooth, without the stepping and jerkiness found in Windows. The Nexus feels like Windows scrolling, slow things right down and it seems really jerky and jumpy, but doing quick flicks around seems fine. Now that I've noticed it, I hate it.

I was really looking forward to getting a Galaxy S3, but the jerky scrolling will send me insane if it's on my daily driver. Are all Android devices like this or have I got a bad Nexus unit? How have you found Project Butter- a success, or does it still leave a lot of room for improvement?



daveathall
Sep 29, 2012, 10:54 AM
I must admit that I don't suffer from jerkiness on my SGS3 using ICS.

parapup
Sep 29, 2012, 10:57 AM
This is what I tell my OC friends - if you are convinced iOS has no lags or stutters whatsoever, just stick with it. But I also show them my iPod Touch last gen - it's no saint when it comes to responsiveness - launching apps is laggy as hell, even scrolling doesn't always work the way it does on the iPad for most time (it is unresponsive when loading background tabs for example), and even on the iPad my Safari (Airplay) tabs are reloaded many times - this all leads to very suboptimal experience.

But if you are sold on iOS - these are very easy to ignore. Same way for Android - if you are not OC about minor things - you don't even notice it. I use my Nexus 7 way more than my iPad - I know at least it won't kill my apps and tabs as much and for bonus it doesn't hurt my hands as much.

[Gee I hope I didn't reply to a troll post - just went back to my Nexus 7 and it felt as smooth as ever.]

ReanimationN
Sep 29, 2012, 11:16 AM
[Gee I hope I didn't reply to a troll post - just went back to my Nexus 7 and it felt as smooth as ever.]
Nah, I'm not trolling, look at my post history, I've been far more critical of Apple than I have of Google or Microsoft.
It's annoying me big time because other than this, I've really been enjoying Android.

Try loading up a webpage, then put one finger on your screen, then don't take it off, leave it on there and scroll up as slowly as you possibly can. Is there no juddering or jerkiness during super, super slow scrolling? If there isn't, I must have a bad Nexus 7, I just don't have anything to compare it to other than my 3GS, which doesn't suffer from this at all. My 3GS just fails at everything else, including holding a cell signal and not auto-closing an app I switched away from 10 seconds ago.

zbarvian
Sep 29, 2012, 11:23 AM
Touch screen interaction is best on iOS devices. Windows phone is real close, though. Project Butter boosts Android some, but it's still not there yet. It's one of the big reasons I stay on iOS.

The Robot Cow
Sep 29, 2012, 11:24 AM
I did notice when i was messing with an ip5 at an att store that it does scroll in the browser alot smoother than my galaxy nexus running a custom jelly bean rom. Project Butter is ment to make things alot smoother compared to Ice Cream Sandwich, not to match ios.
http://www.youtube.com/watch?v=FCVMvvXHqxU

If that did bother you, the thing i noticed on the ip5 is that it kinda stutters going between the home screens. It does go quickly but it had this tiny bit of stutter in the animation which gave it that look.

onthecouchagain
Sep 29, 2012, 11:28 AM
You know what lags? When you open folders in iOS. There's the slightest hangup. There are other examples too, but that's the most frequent.

No OS is completely lag-free.

Definitely not JB, project butter or not.

paulsalter
Sep 29, 2012, 11:30 AM
If I do very very slow scrolling on my Nexus 7 it judders

I would normally never scroll at that speed so not noticed it

parapup
Sep 29, 2012, 11:34 AM
Try loading up a webpage, then put one finger on your screen, then don't take it off, leave it on there and scroll up as slowly as you possibly can. Is there no juddering or jerkiness during super, super slow scrolling?

Not sure why this particular scrolling method matters to you - I always tend to scroll at least few lines in a single flick. But I tried to replicate your method and I didn't see any stutter or lag - it responds in real time. But what I did see was a bit of flicker. Now N7s are known to have varying degrees of screen flicker issue due to aggressive auto brightness control. But then I tried the same thing on iPad and I saw similar scrolling performance but much less noticeable flicker.

Frankly the flicker sometimes bugged me on N7 but scrolling I could not meaningfully differentiate from that on the iPad.

ReanimationN
Sep 29, 2012, 11:53 AM
Touch screen interaction is best on iOS devices. Windows phone is real close, though. Project Butter boosts Android some, but it's still not there yet. It's one of the big reasons I stay on iOS.
Yeah, that seems to be it in a nutshell- Android's now so close, but just not quite there yet.
I did notice when i was messing with an ip5 at an att store that it does scroll in the browser alot smoother than my galaxy nexus running a custom jelly bean rom. Project Butter is ment to make things alot smoother compared to Ice Cream Sandwich, not to match ios.
http://www.youtube.com/watch?v=FCVMvvXHqxU

If that did bother you, the thing i noticed on the ip5 is that it kinda stutters going between the home screens. It does go quickly but it had this tiny bit of stutter in the animation which gave it that look.Yeah, that's where I'm noticing the biggest difference- in the browser, and that tends to be what I use most on my phone/tablet, so it's important to me.

And I definitely didn't come away very impressed from a hands-on with the iP5- the screen size feels quite awkward and I really couldn't notice any speed improvements over the 4S.
You know what lags? When you open folders in iOS. There's the slightest hangup. There are other examples too, but that's the most frequent.

No OS is completely lag-free.

Definitely not JB, project butter or not.
That's right, I'm definitely used to iOS lagging, I'm on a 3GS after all. ;) Mine takes a good 10-12 seconds to open Messages most of the time and double that to open Mail.
If I do very very slow scrolling on my Nexus 7 it judders

I would normally never scroll at that speed so not noticed it
Not sure why this particular scrolling method matters to you - I always tend to scroll at least few lines in a single flick. But I tried to replicate your method and I didn't see any stutter or lag - it responds in real time. But what I did see was a bit of flicker. Now N7s are known to have varying degrees of screen flicker issue due to aggressive auto brightness control. But then I tried the same thing on iPad and I saw similar scrolling performance but much less noticeable flicker.

Frankly the flicker sometimes bugged me on N7 but scrolling I could not meaningfully differentiate from that on the iPad.
Ahh, yes, that seems to be part of the issue. Scrolling slowly, the screen seems to flicker quite a bit. Combined with the choppiness, that's what's irritating me.

My touch response doesn't quite respond in real time though when scrolling slowly, maybe I should chance an exchange and see if I get an improvement. Judging from other people's posts though, it may just be Jelly Bean.

Thanks for the responses everyone, without another Android device on hand to compare mine to, it's hard to know whether mine's acting normally or not.

Dolorian
Sep 29, 2012, 11:56 AM
I have an S3 with Ice Cream Sandwich (using stock TouchWiz) and I don't get any lag.

cynics
Sep 29, 2012, 01:36 PM
The way the operating systems work is the issue. Project butter for the most part tries to use more raw power to force everything to be smooth, it helps but isn't perfect obviously.

iOS does the opposite. It prioritized user input over task running. This is why if you are scrolling in safari the web page will stop loading until you are done. On a fast Internet connection it's hard to notice but its there.

It's all a matter of preference. Personally I like the way the Apple does it on a phone, but on a tablet I prefer Android. I like to have things running and loading in the background as its more of a computer environment to me however user input isn't as fluid as it is on my phone.

matttye
Sep 29, 2012, 02:06 PM
Android is a lot more responsive now, it's definitely acceptable and I have no complaints. It's not as responsive as iOS still. Not sure there's anything Google can do other than to ditch Java.

BoxerGT2.5
Sep 29, 2012, 02:50 PM
Touch screen interaction is best on iOS devices. Windows phone is real close, though. Project Butter boosts Android some, but it's still not there yet. It's one of the big reasons I stay on iOS.


Yet many have noted the iphone 5 not registering touches?

1member1
Sep 29, 2012, 02:54 PM
I don't believe project butter. I saw many android devices with 4.1 lagging and crashing all day long.

if you see iOS devices with lag so they probably on the last versions after 2-3 years.

zbarvian
Sep 29, 2012, 03:04 PM
Yet many have noted the iphone 5 not registering touches?

As if you can make some sort of claim about iOS's touch interaction from a couple of glitchy iPhone 5 screens.

cynics
Sep 29, 2012, 03:10 PM
I don't believe project butter. I saw many android devices with 4.1 lagging and crashing all day long.

if you see iOS devices with lag so they probably on the last versions after 2-3 years.

Exactly how many devices have you seen with JB? Even my Xoom is reasonable (good not great) on JB and it pales in comparison to the hardware these new super phones have.

1member1
Sep 29, 2012, 03:34 PM
Exactly how many devices have you seen with JB? Even my Xoom is reasonable (good not great) on JB and it pales in comparison to the hardware these new super phones have.

about 10-15. I think it's enough.

Dr McKay
Sep 29, 2012, 03:36 PM
iOS isnt immune from scroll judder. When slowly scrolling in the app store on my iPhone 5, it's like scrolling in Android 2.2

cynics
Sep 29, 2012, 03:42 PM
about 10-15. I think it's enough.

But which devices? There are only a handful of Android devices officially on JB (not 10-15) unless you actually mean like 10-15 of the same make model device. Lol

b166er
Sep 29, 2012, 04:14 PM
in my experience iOS has always been and still is the best when it comes to lag. As long as you are not a few generations behind on hardware and trying to run the latest iOS. So far nothing comes close in my eyes. However iOS's lack of.... well you know the usual list of complaints.... it makes using Android a little less painful. I have a Nexus 7 and it's damn smooth. I know WP7 is even smoother, I am hoping WP8 matches iOS in terms of smoothness.

aznguyen316
Sep 29, 2012, 04:16 PM
I have official nightly CM10 on my s3 haha. Good enough for me. Can't go back to ICS after using JB

Vegastouch
Sep 29, 2012, 05:09 PM
I must admit that I don't suffer from jerkiness on my SGS3 using ICS.

Put me on this list as well

Dunbar
Sep 29, 2012, 05:37 PM
The only lag I get on my S3 is the update flicker you get sometimes when hitting the home button. The same thing happens randomly with widgets updating so I stopped using them. It's by far my biggest issue with the phone. Really hope the official JB update fixes it or I may flash a custom ROM

onthecouchagain
Sep 29, 2012, 05:54 PM
Yet many have noted the iphone 5 not registering touches?

Actually, i think it's OS related. I notice more and more frequently that my touches don't always register the first time. And I know it's not because I'm "pressing fast" because I see the slight gray-ness when you touch an icon; it just doesn't register to actually launch the app. It's bizarre. I've noticed it happening more and more both when I was on iOS 5 and still now with iOS 6. This is my third gen iPad, but I def. noticed it happening too on my 4S when it was on iOS 5.

unlinked
Sep 29, 2012, 09:21 PM
Project butter for the most part tries to use more raw power to force everything to be smooth, it helps but isn't perfect obviously.



What are you basing this comment on?

blackhand1001
Sep 30, 2012, 10:02 AM
Try a browser other than chrome. Chrome for android in my opinion isn't ready yet. The stock aosp browser is way smoother but that's not on the stock ROM of the nexus 7 for some dumb reason. Dolphin HD or boat browser are great alternatives if you don't wanna root. Custom ROMs have the aosp browser and you can install it on the stock ROM as well with root.

----------

The way the operating systems work is the issue. Project butter for the most part tries to use more raw power to force everything to be smooth, it helps but isn't perfect obviously.

iOS does the opposite. It prioritized user input over task running. This is why if you are scrolling in safari the web page will stop loading until you are done. On a fast Internet connection it's hard to notice but its there.

It's all a matter of preference. Personally I like the way the Apple does it on a phone, but on a tablet I prefer Android. I like to have things running and loading in the background as its more of a computer environment to me however user input isn't as fluid as it is on my phone.

Having used ICS and jb extensively on my galaxy nexus its not using raw power. Jb is much smoother and no longer has the lag whenever a toast notification would come up. It also doesn't lag because of the button glow animation anymore. Jellybean made a huge difference for the galaxy nexus. The issue people are having with chrome is a problem with chrome. I really think Google made a mistake by only including chrome on the nexus 7. The stock android browser is so much better, faster, and smoother.

cynics
Sep 30, 2012, 10:09 AM
What are you basing this comment on?

http://www.androidpolice.com/2012/07/12/getting-to-know-android-4-1-part-3-project-butter-how-it-works-and-what-it-added/

cynics
Sep 30, 2012, 10:13 AM
Try a browser other than chrome. Chrome for android in my opinion isn't ready yet. The stock aosp browser is way smoother but that's not on the stock ROM of the nexus 7 for some dumb reason. Dolphin HD or boat browser are great alternatives if you don't wanna root. Custom ROMs have the aosp browser and you can install it on the stock ROM as well with root.

----------



Having used ICS and jb extensively on my galaxy nexus its not using raw power. Jb is much smoother and no longer has the lag whenever a toast notification would come up. It also doesn't lag because of the button glow animation anymore. Jellybean made a huge difference for the galaxy nexus. The issue people are having with chrome is a problem with chrome. I really think Google made a mistake by only including chrome on the nexus 7. The stock android browser is so much better, faster, and smoother.

Sorry, the added triple buffering, vsync pulse etc to force the OS to be smoother. Read above link.

That's the opposite Apples approach of doing less in the background. Android still does what it dud before plus some to make the OS more fluid.

matttye
Sep 30, 2012, 10:18 AM
Sorry, the added triple buffering, vsync pulse etc to force the OS to be smoother. Read above link.

That's the opposite Apples approach of doing less in the background. Android still does what it dud before plus some to make the OS more fluid.

Some apps for Android are just badly coded.

Take Tapatalk as a perfect example. It's buttery smooth in iOS, but in Android it stutters and freezes while scrolling even in Jelly Bean.

blackhand1001
Sep 30, 2012, 10:27 AM
Some apps for Android are just badly coded.

Take Tapatalk as a perfect example. It's buttery smooth in iOS, but in Android it stutters and freezes while scrolling even in Jelly Bean.
Enabling force gpu rendering in dev options helps a lot. There's still a bit of stutter though. That's one of the choppiest apps around. Most are much better.

matttye
Sep 30, 2012, 10:40 AM
Enabling force gpu rendering in dev options helps a lot. There's still a bit of stutter though. That's one of the choppiest apps around. Most are much better.

Agreed, I haven't seen any other apps as bad as Tapatalk.

ReanimationN
Sep 30, 2012, 10:41 AM
Try a browser other than chrome. Chrome for android in my opinion isn't ready yet. The stock aosp browser is way smoother but that's not on the stock ROM of the nexus 7 for some dumb reason. Dolphin HD or boat browser are great alternatives if you don't wanna root. Custom ROMs have the aosp browser and you can install it on the stock ROM as well with root.
Wow, you are definitely right there. I just tried Boat Browser, it's so much smoother than Chrome. The juddering at slower scrolling speeds still exists, but it's not as bad as Chrome.

LIVEFRMNYC
Sep 30, 2012, 10:41 AM
I must admit that I don't suffer from jerkiness on my SGS3 using ICS.

I have an S3 with Ice Cream Sandwich (using stock TouchWiz) and I don't get any lag.

Same here for me.

kdarling
Sep 30, 2012, 10:43 AM
http://www.androidpolice.com/2012/07/12/getting-to-know-android-4-1-part-3-project-butter-how-it-works-and-what-it-added/
The way the operating systems work is the issue. Project butter for the most part tries to use more raw power to force everything to be smooth, it helps but isn't perfect obviously.

That Project Butter article didn't talk about using more raw power.

VSync and sometimes using a triple-buffer, is about using better TIMING to start doing the same things it did before.

blackhand1001
Sep 30, 2012, 10:52 AM
Wow, you are definitely right there. I just tried Boat Browser, it's so much smoother than Chrome. The juddering at slower scrolling speeds still exists, but it's not as bad as Chrome.

The juttering is nexus 7 specific. Theres actually newer touchscreen drivers out now that fix it, they should be included in the next OTA update. Custom roms have already solved this but google just pushed the new drivers to AOSP which means they will be included in the OTA.

You can read more about the new drivers here.
http://forum.xda-developers.com/showthread.php?t=1905961

ReanimationN
Sep 30, 2012, 11:12 AM
The juttering is nexus 7 specific.
Now that is good to hear! I feel a lot less hesitant about an S3 now.
Theres actually newer touchscreen drivers out now that fix it, they should be included in the next OTA update. Custom roms have already solved this but google just pushed the new drivers to AOSP which means they will be included in the OTA.

You can read more about the new drivers here.
http://forum.xda-developers.com/showthread.php?t=1905961Excellent, can't wait for the update. Generally how long does an update take to get pushed out to stock Nexus devices after Google's released new code?

cynics
Sep 30, 2012, 11:35 AM
That Project Butter article didn't talk about using more raw power.

VSync and sometimes using a triple-buffer, is about using better TIMING to start doing the same things it did before.

I guess we are defining raw power differently. Using "things" and doing more is what I mean. The opposite approach would be doing less in the background to allocate resources for fluidity.

I don't mean it's using more energy or you need to shovel coal into the phone or whatever you are assuming.

blackhand1001
Sep 30, 2012, 11:43 AM
Now that is good to hear! I feel a lot less hesitant about an S3 now.
Excellent, can't wait for the update. Generally how long does an update take to get pushed out to stock Nexus devices after Google's released new code?

Whenever the OTA is issued you should get it instantly. Google should be doing an OTA pretty soon most likely.

Vegastouch
Sep 30, 2012, 11:56 AM
Try a browser other than chrome. Chrome for android in my opinion isn't ready yet. The stock aosp browser is way smoother but that's not on the stock ROM of the nexus 7 for some dumb reason. Dolphin HD or boat browser are great alternatives if you don't wanna root. Custom ROMs have the aosp browser and you can install it on the stock ROM as well with root.

----------



Having used ICS and jb extensively on my galaxy nexus its not using raw power. Jb is much smoother and no longer has the lag whenever a toast notification would come up. It also doesn't lag because of the button glow animation anymore. Jellybean made a huge difference for the galaxy nexus. The issue people are having with chrome is a problem with chrome. I really think Google made a mistake by only including chrome on the nexus 7. The stock android browser is so much better, faster, and smoother.

Not for me it isnt. Chrome works well and is the fastest browser.

cynics
Sep 30, 2012, 11:57 AM
Whenever the OTA is issued you should get it instantly. Google should be doing an OTA pretty soon most likely.

Carriers hold up the process, this is why GSM models get updates before Verizon. If its a wifi device like the Xoom or N7. You get the update immediately but if the device has cellular data it has to be tested by the carrier. Hence why the wifi Xoom has official JB but the lte Xoom does not.

Verizon Gnex is just getting JB.

blackhand1001
Sep 30, 2012, 11:58 AM
Not for me it isnt. Chrome works well and is the fastest browser.

On jellybean on nexus devices its definitely smoother. I can't speak for the galaxy s3 since samsung made customizations to the stock browser.

Renzatic
Sep 30, 2012, 11:59 AM
Sorry, the added triple buffering, vsync pulse etc to force the OS to be smoother. Read above link.

That's the opposite Apples approach of doing less in the background. Android still does what it dud before plus some to make the OS more fluid.

Actually, what makes iOS so smooth is that the UI has processor priority over everything else. Android takes the opposite approach, giving priority to apps above everything else.

It's weird that in actual usage Android is a goodly bit faster than iOS in certain situations, but the lag and stutters you see make you believe it's much chunkier and rough than it actually is. It's a weird situation where the presentation of smoothness and the illusion of speed gives you a better experience than honest to god actual speed.

Also, I'm fairly sure triple buffering and vsync are used in iOS. Without vsync, you'd get tearing across the middle of the screen whenever you do a quick scroll.

Vetvito
Sep 30, 2012, 12:03 PM
On jellybean on nexus devices its definitely smoother. I can't speak for the galaxy s3 since samsung made customizations to the stock browser.

Huh? That makes no sense. The stock browser on the GS3 isn't Chrome.

Vegastouch
Sep 30, 2012, 12:05 PM
On jellybean on nexus devices its definitely smoother. I can't speak for the galaxy s3 since samsung made customizations to the stock browser.

I dont have a N7 so im talking about my GS3

Vetvito
Sep 30, 2012, 12:13 PM
I don't believe project butter. I saw many android devices with 4.1 lagging and crashing all day long.

if you see iOS devices with lag so they probably on the last versions after 2-3 years.

Are you serious? I have more iPhone apps not launching at all on my 4s than I have ever had on my Nexus.

I try launching Angry Birds Space, I get a black screen and then it jumps back to springboard. What's up with that? Same with GTA3.

kdarling
Sep 30, 2012, 01:44 PM
Actually, what makes iOS so smooth is that the UI has processor priority over everything else. Android takes the opposite approach, giving priority to apps above everything else.

Yep, this has long been a tug-of-war in OS design.

In the earliest days of personal computers, the OS needed priority in order to handle a lot of time-dependent tasks (software serial ports, keyboard scanning, etc). Later, as chips were made to take over such tasks, the OS could afford to let UI actions take more precedence.

My own background is heavily in realtime systems, where UI actions had to take less precedence at times. For example, it is almost always more important to close a valve to prevent the factory from blowing up, before showing the user that the valve has closed :)

Btw, another way that iOS differs (or rather, differed) is that it tended to show a lot of blank screen if it couldn't keep up. Android tended to wait until the data was ready to show before continuing. This caused list scrolling lag on Android while it waited for good data to be drawn, versus fast scrolling on iOS that had missing data.

Also, I'm fairly sure triple buffering and vsync are used in iOS. Without vsync, you'd get tearing across the middle of the screen whenever you do a quick scroll.

Yes, the technique of at least double-buffering and flipping buffers during vsync, has been used since the dawn of computer graphics.

What they're talking about here, is simply making sure that drawing on Buffer B for the next screen STARTS the earliest that it can (right after Buffer B is no longer being displayed), instead of just randomly starting at some other point in time.

I guess we are defining raw power differently. Using "things" and doing more is what I mean. The opposite approach would be doing less in the background to allocate resources for fluidity.

The point is that it's neither doing more nor less.

It's doing the same old stuff, but starting at an earlier point in order to lower the chances of the drawing not being ready to be displayed at the next usual frame time.

The only resource it uses more of, is sometimes a third screen buffer.

Cheers!

cynics
Sep 30, 2012, 02:02 PM
The point is that it's neither doing more nor less.

It's doing the same old stuff, but starting at an earlier point in order to lower the chances of the drawing not being ready to be displayed at the next usual frame time.

The only resource it uses more of, is sometimes a third screen buffer.

Cheers!

I can assure you I'm not trying to start a debate over what it is or isn't doing but if you feel the need to be right you'll contradict yourself I'll gladly concede the conversation. It does precisely what you say it does, which is exactly what I said.... :)

Technarchy
Sep 30, 2012, 02:27 PM
Touch screen interaction is best on iOS devices. Windows phone is real close, though. Project Butter boosts Android some, but it's still not there yet. It's one of the big reasons I stay on iOS.

And the fact that iOS was actually designed to provide a multitouch experience from day one. As was Windows Phone.

They weren't ripped out of a blackberry clone and shoehorned into an iPhone clone.

3bs
Sep 30, 2012, 02:31 PM
Try a browser other than chrome. Chrome for android in my opinion isn't ready yet. The stock aosp browser is way smoother but that's not on the stock ROM of the nexus 7 for some dumb reason. Dolphin HD or boat browser are great alternatives if you don't wanna root. Custom ROMs have the aosp browser and you can install it on the stock ROM as well with root.

My only issue with the stock AOSP browser is that it doesn't sync bookmarks with my gmail account. I try to sync it in accounts but it fails every time.

unlinked
Sep 30, 2012, 05:51 PM
http://www.androidpolice.com/2012/07/12/getting-to-know-android-4-1-part-3-project-butter-how-it-works-and-what-it-added/

I only scanned but that seems to be based off the IO 2012 talk they gave.
None of that is about using more raw power. Most of it is about managing the timing in the render pipeline.

It just seems strange to claim project butter (that is a marketing name not the projects real name) is about using raw power because afaik the only new device released with Jelly Bean so far is the Nexus 7 and that is a $200 tablet.

aznguyen316
Sep 30, 2012, 06:07 PM
I only scanned but that seems to be based off the IO 2012 talk they gave.
None of that is about using more raw power. Most of it is about managing the timing in the render pipeline.

It just seems strange to claim project butter (that is a markting name not the projects real name) is about using raw power because afaik the only new device released with Jelly Bean so far is the Nexus 7 and that is a $200 tablet.

Galaxy Nexus officially got it a week ago. My S3 has it thanks to CM10 though, been using it for the past 3-4 weeks. Started on nightly 9-2 I think.

Vetvito
Oct 1, 2012, 01:02 AM
^ no CDMA aka carrier Nexus officially got Jelly Bean. Unlocked Nexus had it for months.

aznguyen316
Oct 1, 2012, 04:02 AM
^ no CDMA aka carrier Nexus officially got Jelly Bean. Unlocked Nexus had it for months.

http://m.engadget.com/2012/09/21/verizon-galaxy-nexus-finally-lands-jelly-bean-update/

Vetvito
Oct 1, 2012, 09:50 AM
Lol that's proving my point. CDMA aka carrier branded aka Verizon/Sprint just got Jelly Bean. GSM unlocked pure Google phones have had it for months.

aznguyen316
Oct 1, 2012, 09:57 AM
Lol that's proving my point. CDMA aka carrier branded aka Verizon/Sprint just got Jelly Bean. GSM unlocked pure Google phones have had it for months.

Yeah your wording was pretty confusing in your post. "no CDMA aka carrier Nexus officially got Jelly Bean." Maybe if you added when JB officially released. I already mentioned in my post that you were "^" to that Nexus received the update last week. Wasn't sure where you were going with that.

blackhand1001
Oct 1, 2012, 11:30 AM
^ no CDMA aka carrier Nexus officially got Jelly Bean. Unlocked Nexus had it for months.

Both sprint and verizon have rolled out jellybean already. Even the sprint nexus s has it as well.

Mrg02d
Oct 1, 2012, 02:20 PM
There is a leaked ROM for GS3 from Sprint that is JB. Its super smooth, more so than iOS, but glitchy. Good thing its a leak. As for benchmarks, it crushes ICS on Gs3.

3bs
Oct 1, 2012, 02:29 PM
My only issue with the stock AOSP browser is that it doesn't sync bookmarks with my gmail account. I try to sync it in accounts but it fails every time.

If anyone else is having this issue then try this. I'm glad I decided to google my issue and like most times, I found a solution :p https://productforums.google.com/forum/?fromgroups=#!topic/chrome/T18wWp8MhRc

Vetvito
Oct 1, 2012, 05:11 PM
Yeah your wording was pretty confusing in your post. "no CDMA aka carrier Nexus officially got Jelly Bean." Maybe if you added when JB officially released. I already mentioned in my post that you were "^" to that Nexus received the update last week. Wasn't sure where you were going with that.

My fault, got to use these commas.

thelezzy
Jul 5, 2013, 11:16 PM
There is lag with every os. iOS had minor mili second lag when scrolling to spotlight search or returning home from the photo booth app.

Android is rather acceptable since having quad core A15s under the hood. I nearly noticed any unacceptable lag from home onwards with the store demo units HTC ones and S4s

adder7712
Jul 7, 2013, 04:40 PM
In some instances, the iPad 3 can be a lagfest. Especially while using Maps and flicking through the App Store.

egoistaxx9
Jul 7, 2013, 04:54 PM
yep, i also noticed it on my nexus 7. but havent seen it on any of my android phones.

Tarzanman
Jul 8, 2013, 09:37 AM
yep, i also noticed it on my nexus 7. but havent seen it on any of my android phones.

A factory reset fixed my nexus 7 lag issues.

egoistaxx9
Jul 8, 2013, 03:54 PM
A factory reset fixed my nexus 7 lag issues.

will check it out, thanks for the help!