So had my nexus 10 for a few days now and im confused about the general stuttery performance issues. my galaxy s3 running cm10 runs android rather buttery and smooth. the nexus 10 seems to be lacking butter. ive tried the nexus 4 and it's a great buttery performance but the 10 lags and stutters alot, is this just because of the screen resolution or is a fault of android? ive tried cm10 and others nexus 10 roms but still seems kinda stuttery. is over clocking the answer? it's only really 2d performance where the 10 seems to be lacking and i expected more from a 1.7 dual core proc.
something i have noticed is that as long as i keep my finger on the screen, it does not lag, however if i fling and then remove my figure it lags and stutters.
i want to hear other peoples opinions on nexus 10 performance because so far, i fail to see the butter.
moonytoonyking said:
i want to hear other peoples opinions on nexus 10 performance because so far, i fail to see the butter.
Click to expand...
Click to collapse
If there are performance problems, the reason they never get fixed is that people insist on posting subjective experience with "lag" on xda instead of objective, useful bug reports on the AOSP bug tracker..
In my experience, though, it's always a ****ty app hogging the UI thread in a service or some other noob developer move causing lag.
My N10 is smooth and stock.
The idea behind Project Butter, I believe, is that when you have your finger on the screen, then the governor automatically ramps up the speed to whatever the max has been set to. This is the reason why interactive is now the most common governor of choice for AOSP. I suppose you could root and flash a different kernel with other specialised governors like KToonses, which comes with PegasusQ, KToonsertive and others. Or even on stock you could change to other kernels and see if that helps out. I haven't really been noticing much problem with the stutter even on interactive tbh. Animations are fine, so could be that you do have some cpu intensive app causing the lag.
Sent from my HTC One X using xda premium
I use both daily, cm 10.1 on my d2vzw and can tell you my N10 doesn't lag/stutter, both are comparable speed wise in daily use here. As others have suggested I would check your installed apps for irregular behavior
Sent from my SCH-I535 using XDA
I have a nexus 10 and a 9300i too, and my nexus 10 is much much faster!
Actually thinking about it 1 app runs better on my S3, google chrome. I use the AOSP browser instead on my N10, for this as well as flash support.
Think i found the problem
it would appear that having google currents syncing in the background causes lag. tablet is super fast after disabling.
No lag here whatsoever. Running cm10.1 nightlies.
I haven't had a single hint of lag since day one. Seriously, literally as smooth as smooth can be as far as 2D desktop experience goes. If you're suffering noticeable lag I'd honestly think you have a faulty tablet. This thing is BUTTER.
moonytoonyking said:
it would appear that having google currents syncing in the background causes lag. tablet is super fast after disabling.
Click to expand...
Click to collapse
I believe the thread you're referring to is here:
http://forum.xda-developers.com/showthread.php?t=2012756
bamboosensei said:
The idea behind Project Butter, I believe, is that when you have your finger on the screen, then the governor automatically ramps up the speed to whatever the max has been set to. This is the reason why interactive is now the most common governor of choice for AOSP. I suppose you could root and flash a different kernel with other specialised governors like KToonses, which comes with PegasusQ, KToonsertive and others. Or even on stock you could change to other kernels and see if that helps out. I haven't really been noticing much problem with the stutter even on interactive tbh. Animations are fine, so could be that you do have some cpu intensive app causing the lag.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
The other aspects of project butter such as the vsync made a much bigger difference than the ramping up CPU. Prior to jellybean if a toast notification came up all the animations would become really choppy. Even with the CPU at low speeds the animations stay smooth as they are rendered by the GPU.
Sent from my Nexus 7 using xda premium
blackhand1001 said:
The other aspects of project butter such as the vsync made a much bigger difference than the ramping up CPU. Prior to jellybean if a toast notification came up all the animations would become really choppy. Even with the CPU at low speeds the animations stay smooth as they are rendered by the GPU.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I agree but the TC stated that it didn't lag when he kept his finger on the screen so I assumed it was due to that particular part of Project Butter that made a difference.
Sent from my HTC One X using xda premium
Related
**DISCLAIMERS**
This thread has no intention of attempting to complain, diminish, degrade, or criticize any developers on this forum or any of their work, as all of us are nothing but grateful for the amount of free, altruistic, and superior quality code that they provide us with. :good:
This thread has no intention of trying to reiterate the content of the "Butery Smoothness" thread found at http://forum.xda-developers.com/showthread.php?t=1814010 nor to define what "Buttery Smoothness" is, as the previous thread defines it well enough already through the posts and insight of multiple users.
This thread has been created with full knowledge and consideration of the alpha development stage that Android 4.1.1 is currently in and all content discussed in this thread is stated with regard to said knowledge and should only be perceived as an attempt to contribute to at least one of multiple bug fixes to further improve the state of Android 4.1.1 on the SGH-i717 for the good of all users
Purpose
The purpose of this thread is to solve the perceived lack of graphical smoothness and fluidity inside of Android 4.1.1 (Jelly Bean) on the SGH-i717 which has been noticed and reported by many users in multiple ROM's through the collaboration of information, ideas, and solutions between all users and developers.
Background
Many users have reported a significant lack of graphical performance in multiple Jelly Bean ROM's for the SGH-i717 in various scenarios such as home screen navigation, UI animations, and in-app scrolling where there is not only a user-noticeable drop in performance but a quantifiable drop in frame-rate. With Google's Project Butter being a highlight of Jelly Bean, the lack of smoothness in its current state for our device brings not only dismay but logical confusion as other, older devices with lower specifications (such as the Galaxy Nexus for example) perform better graphically than the SGH-i717 with higher specifications. The higher graphical performance in the older Ice Cream Sandwich indicates that the highlighted performance issue in Jelly Bean is not related to hardware incapability but to software utilization of the hardware.
I want to leave as little of my insight in this thread as possible because I want to hear from other users but I'll post some initial information and questions to provoke some response.
Ever since Jelly Bean development began, I've noticed this issue on my device and have even had a replacement device with the same experience so hardware isn't a likely culprit in my opinion. h0tw1r3 was one of the first developers to bring a Jelly Bean ROM to SGH-i717 users and other ROM's were formed briefly after his using it as a base. Until about the third or fourth build ( 8-21 I believe), the performance was sluggishly the same. After this build though, there was a noticeable increase in graphical performance, although still significantly behind ICS. That new standard hasn't changed much since until the latest CM10 nightly builds where I've noticed quite an increase in graphical performance putting it a little closer to ICS performance but still painfully behind such that Dolphin is the only browser that feels smooth enough to use efficiently.
I have also noticed an odd phenomenon where the performance varies from build to build without a noticeably significant change. For example, I remember using DaGr8's AOKP port for a while and finding it smoother than other ROM's at the time but once installing his next build (that only mentioned minor unrelated changes, although some could have been unlisted) the performance was back down again. I have experienced this with multiple different ROM's though which is what is most peculiar that there is so much inconsistency.
Helpful Questions
Have you noticed any of these issues before? If so, which ones?
Do you think the issue is hardware or software/driver related?
How would you compare your best JB experience to stable ICS builds?
Which processes/applications perform the best and the worst for you graphically?
Which ROM's run smooth for you and which ones don't?
Which browsers have you tried in Jelly Bean and which ones do you prefer the most?
Have you noticed graphical performance issues in Chrome consistently at all? If so, in which ROM's or instances have you experienced such?
Do you have any ideas/suggestions as to what is causing or what could fix this issue?
And regardless of the inevitable bugs we are experiencing in alpha software, are you extremely grateful for the developers who have provided us with them? (SAY YES!!)
If any of you would like to add more content or questions to this list (and PLEASE do), just ask them and I'll add them to this OP.
Suggestions and Modifications for Improvement (list will grow over time as new information is presented)
1) Verify that the "debug.mdpcomp.maxlayer" parameter in build.prop is set to the value of 3 and not 2 when you first install a ROM (thanks to NYConex for the tip!). Some developers/ROM chefs (lol) will customize this setting based on their preference. This setting disables (value 2) and enables (value 3) GPU acceleration taking the load off of the CPU. Disabling has fixed the flicker issue that has developed in Jelly Bean for many people but will severely impact performance and graphical smoothness as well as battery life potentially. For flickering, I instead recommend using a live wallpaper which will force the GPU to refresh the screen much more often disabling flicker (in the homescreen at least).
2)**ESSENTIAL FIX FOR SIGNIFICANT IMPROVEMENT** Change the debug.composition.type in /system/build.prop from "dyn" to "gpu" and reboot. This makes a MAJOR difference in ALL areas of performance. The existing string that is entered by default is a "dynamic" setting which alternates putting the graphical load on either the GPU or CPU depending upon resource allocation. Changing the setting to "gpu" will force Android to constantly use the GPU for graphics so you won't notice stutter and lag as Android switches the load from the CPU and GPU. Using this setting also increases overall system speed IMMENSELY as it allows the CPU to do more central tasks like launching applications and communicating with hardware instead of handling the graphics. This "constant GPU setting" plays very nicely with Project Butter in the sense that it uses a constant component of hardware to render graphics along with the constant frame rate that VSync provides. I may try to learn how to make my first ROM sometime soon and when I do, I'll be sure and integrate this into the ROM. Either thank the post or let everyone know if this has helped you!
I have noticed that the liquid ROM as well as the most recent nightly (2 SEP) have been pretty smooth. Nova launcher works great and I don't really see a lot of lag outside the launchers. One thing that kinda brothers me is the lag that is introduced when you enable the nav bar. I don't know exactly what happens behind the scenes (other than it disable the hw keys and enables the soft keys) but it adds a lot of lag. Is there a way to monitor exactly what happens when doing things to your phone? When I use liquid it changes without a reboot but with cm10 I have to manually disable the hw keys so it requires a reboot. Anyone know what's going on with it?
NYConex said:
I have noticed that the liquid ROM as well as the most recent nightly (2 SEP) have been pretty smooth. Nova launcher works great and I don't really see a lot of lag outside the launchers. One thing that kinda brothers me is the lag that is introduced when you enable the nav bar. I don't know exactly what happens behind the scenes (other than it disable the hw keys and enables the soft keys) but it adds a lot of lag. Is there a way to monitor exactly what happens when doing things to your phone? When I use liquid it changes without a reboot but with cm10 I have to manually disable the hw keys so it requires a reboot. Anyone know what's going on with it?
Click to expand...
Click to collapse
Good question. I know there are settings in Developer options that allow you to show GPU status and updates which may provide some insight into GPU/CPU utilization. I don't have an immediate answer for you though. I'll do some research and report back.
With the Liquid ROM, I noticed it to be of the poorest performance as others. Was your experience smooth out of the box or did you have to change the debug.mdcomp.maxlayer from 2 back to 3 first?
**EDIT**
I just tried the Liquid ROM again and realized the debug.mdpcomp.maxlayer setting was set to 2 by default in that ROM and after the changing it, the performance was much better, though about the same as CM10 nightlies.
The mdcomp.maxlayer is always the first thing I check after flashing a ROM. I always set it to 3. But if you go back to liquid try the navbar and you will see what I mean. In not home right now but when I get back I'll mess with it a little.
I'm on the Liquid ROM and I don't notice any lag. So i don't think anything needs fixed...since I dont have the problems u describe.
I use almost all aspects of the Note except little music and games.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Try pulling down the notification drawer. Now sit there and tell me to my face its 60fps. No its not... its really choppy.
Fasty12 said:
Try pulling down the notification drawer. Now sit there and tell me to my face its 60fps. No its not... its really choppy.
Click to expand...
Click to collapse
Lol damn right. I'd say its between 14-21 FPS variably.
Which ROM's have worked the best for you so far?
On mobile, had 2 scroll forever to read topic
SayWhat10 said:
On mobile, had 2 scroll forever to read topic
Click to expand...
Click to collapse
Are you saying that my OP is too long which made you scroll forever or are you saying that the lag in Jelly Bean cause you to scroll forever?
andrawer said:
I'm on the Liquid ROM and I don't notice any lag. So i don't think anything needs fixed...since I dont have the problems u describe.
I use almost all aspects of the Note except little music and games.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
Do you use Google Chrome? If so, how would you describe its performance in comparison to Ice Cream Sandwich?
The CM10 nightly has been the smoothest this far. So going by experience heres the rankings ATM.
1) Nightly... Smooth but constant flicker.
2) Liquid
2) Paranoid
3) Aokp
4) manualscout4life's rom.
Fasty12 said:
Try pulling down the notification drawer. Now sit there and tell me to my face its 60fps. No its not... its really choppy.
Click to expand...
Click to collapse
not sure if i understand.
I use my thumb to initiate the notification bar/drawer pulling down and it's immediate and smooth?? Up/down/up/down/up/down...smooth...just tried it. Not even a hint of lag...and that's with 4 notifications waiting for me to do something.
The mentioned lag on jellybean compared to anything previous doesn't come from anything done by Google or issues with software but comes from the lack of hardware acceleration which we don't get to use with jellybean, so our device is not being used to the fullest, is known like previous versions of android when it comes out and ported , is not going to performed like it's supposed to until HWA becomes available. This is the performance drop in fps compared to ICS. Some think because is a newer version of android is going to be better performing out of the box, but that won't happen unless an official version with HWA becomes available or a developer figures out how to implement it into a ROM.
I think JB is amazing and smooth in the little time it has been out.
RoloRacer Paranoid on JellyBean
I agree about the sluggishness of JB at its current state, its normal since we don't have HW acceleration, I'm on Paranoid and flashed Flaps Hot kernel, OC'ed to 1.7Ghz and its performing really well, you should try it out
Sent from my Nexus 7 using xda premium
egomezmorales said:
I agree about the sluggishness of JB at its current state, its normal since we don't have HW acceleration, I'm on Paranoid and flashed Flaps Hot kernel, OC'ed to 1.7Ghz and its performing really well, you should try it out
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
So when will we get hardware acceleration? When jb officially comes out for the note?
roloracer said:
The mentioned lag on jellybean compared to anything previous doesn't come from anything done by Google or issues with software but comes from the lack of hardware acceleration which we don't get to use with jellybean, so our device is not being used to the fullest, is known like previous versions of android when it comes out and ported , is not going to performed like it's supposed to until HWA becomes available. This is the performance drop in fps compared to ICS. Some think because is a newer version of android is going to be better performing out of the box, but that won't happen unless an official version with HWA becomes available or a developer figures out how to implement it into a ROM.
I think JB is amazing and smooth in the little time it has been out.
RoloRacer Paranoid on JellyBean
Click to expand...
Click to collapse
This has been my thought and awareness all along and what I've wanted to work on repairing. Perhaps it's everyone's use of the term "smooth" that is making everything amiss. When people boast that their JB experiences are "incredibly smooth!" and even more specifically "smoother than ICS!" I think they are making very fallible statements because I don't think that my perception of JB being behind ICS in smoothness can be interpreted as just a "difference in opinion or interpretation". It's definitely factual and quantifiable when testing frame rates and comparing them to ICS. Perhaps it's safe to say that "Jelly Bean is remarkably usable right now considering its alpha state", but to say that it is smooth is quite a fallacy. It's really not much better than Gingerbread and Gingerbread lacked HW acceleration altogether.
But if JB lacks hardware acceleration completely, then how is toggling the maxlayer setting and HW overlay setting in developer options clearly affecting performance if HW acceleration isn't even supported at all in the first place? Some sort of acceleration is clearly being enabled for the evident difference in performance to occur.
I am grateful that you recognize JB's current state to be behind and also attribute it to HW acceleration as I initially did. Now we can hopefully gain some momentum on finding the hindrance of bringing HW acceleration to JB!
If there's anything we've learned thus far, it's not to label a ROM officially "smooth" unless you can prove it greater than or equal to stable ICS builds with quantifiable means!
The word "smooth" is beginning to become a profanity for me, which is rather extreme, as there aren't many words I don't say! Lol...
Everyone should read this.
http://www.androidpolice.com/2012/0...roject-butter-how-it-works-and-what-it-added/
Jb runs exceptionally well for me with just the 2 buffers. Are all the animations perfect every single time? No, but it's perfectly usable, and slick enough for my dd. I'm sure it will be sorted in time.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
So far the smoothest jb rom for me has been dagr8's aokp Sept 1 build.
HW overlays are disabled and cpu at stock frequencies. Running Nova 1.2.2 and have fluid home screen transitions and overall smoothness.
If I were to nitpick, the notification bar is the only thing that seems somewhat sluggish but only when I pull it down on the home screen (I am running a live wallpaper.)
No reboots or sleep of deaths so far, loving this rom at the moment.
yollasho said:
Everyone should read this.
http://www.androidpolice.com/2012/0...roject-butter-how-it-works-and-what-it-added/
Jb runs exceptionally well for me with just the 2 buffers. Are all the animations perfect every single time? No, but it's perfectly usable, and slick enough for my dd. I'm sure it will be sorted in time.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
Really interesting read, thanks for sharing!
Sent from my Nexus 7 using xda premium
---------- Post added at 01:04 PM ---------- Previous post was at 01:04 PM ----------
Fasty12 said:
So when will we get hardware acceleration? When jb officially comes out for the note?
Click to expand...
Click to collapse
Yep, or that a developer taps on how to get HW acceleration
Sent from my Nexus 7 using xda premium
We've had hardware acceleration.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
How do you all find the new Jellybean update's battery life? Better or worse than ICS? I'm guessing worse because of Google Now, but just wondering...(I don't have phone yet)
seems worse to me i was gettinf better battery life on ICS.. my battery drops from 100% to 50% way to fast..
Battery life on the new JB update is amazing!
Even MeanROM never was this good with battery life!.
After a couple of days and restarts its looking good
Sent from my EVO using xda premium
evo401 said:
seems worse to me i was gettinf better battery life on ICS.. my battery drops from 100% to 50% way to fast..
Click to expand...
Click to collapse
If you were not such a FLASHAHOLIC just sayin
There is actually a logical and technical reason as to why JB have worse battery life than ics.
As many people probably know, JB focuses on project butter which aims to make the android experience smoother.
Unfortunately, Google's philosophy is about brute forcing into the problem by relying on raw cpu and gpu power instead of fixing their shaddy code.
The most noticeable difference on JB is UI becomes smoother but that smoothness came at a price, the cpu and gpu has to work harder to maintain 60fps with added vsync triple buffering on top of it.
I also noticed that HTC has boosted the.default 3d gpu clock of adreno 225 on their latest kernel to compensate for the additional workload to maintain smoothness. Some people that is familiar to overclocking knows that if the clocks are increased, the power consumption also increases. It is also not help by the fact that EVO 4g LTE can't always maintain 60fps so it has to work extra hard.
Probably not a lot of people know this but android has abysmal input lag and Google tried to address the issue(in which imo they horribly failed) by boosting the cpu clocks everytime you touched the screen. Obviously, raising the clocks would have negative impact on battery life so if you type a lot or Swype a lot or scroll alot, the cpu would get raised everytime. You could see it yourself by installing a program called micro cpu monitor.
The most obvious way to see the input lag in action is try playing a music then replicate the beats on apps like real drums. The lumia 900 which has single core or even the iPhone 4 which has single core 800mhz cortex a8 does not suffer from horrible input lag.
I was really disappointed with Google and it seems like they have no plans to really fix the core problems in the near future.
Sent from my EVO using xda premium
bigdaddy619 said:
If you were not such a FLASHAHOLIC just sayin
Click to expand...
Click to collapse
hahahah!! u are so rite!! i do have a problem with flashing
I've made a thread similar to this before but people assured me it was something i was doing wrong but despite trying everything thats been suggested to me nothing seems to work. ive had this ****ty tablet that i paid £400 for about 3 months now and im sick of it. My galaxy siii is as smooth as i can ask for, its perfect. This tablet however is a different story. the scrolling is truely horrid, i mean its so janky and stuttery and even when it dosent stutter the screen has a sort of deforming effect. I feel like either google really need to spend some time optimising this tablet or the hardware just cannot support this screen resolution. I love android and even back on my older phones with ics and froyo i found their scrolling often smoother than this ****TY TABLET. I've tried about 15 roms, 4 kernels and even tried over-clocking to about 2.0ghz, nothing. made a difference. does anyone know if gooogle is optimising this tablet? because if i see no improvements within the next month im selling this piece of junk. I dont understand how a tablet that can maintain 60 fps on a 3D game can't even manage to scroll a webpage or app drawer page without dropping frames and having janky and stuttery scrolling. I am also very sure this isnt a problem with android. as i said my phone i9300 galaxy siii handles scrolling super smooth on stock and cm10.1 so it can't be an android problem.
My main question is; Does anyone else find this tablets scrolling performance to be stuttery and janky? or do i have a dud?
Another thing i would like to say is that, the animations are perfectly smooth and in terms of app open speed and gaming performance this tablet is great. however i tend to use tablets for mostly web browsing and other 2D applications which is something that this tablet cant handle for some reason. (oh btw i have tried about 5 different browsers and i know chrome is utter **** this isnt chrome that im tlaking about)
My N10 is stock and not rooted, the only application that behaves anything like that is Firefox which can be really bad. No other issues like that at all. If your looking to resolve the problem I'd go back to basics. It's much more likely to be a software issue than anything else.
Sent from my Nexus 10 using XDA Premium HD app
Perhaps checking the Force GPU rendering in the developers options will help remedy the issue you are having with scrolling.
I do not have this issue when scrolling through a website =\ I do have Force GPU rendering enabled as well as Disable HW overlays checked.
before I returned my two through the play store I noticed a horrible amount of scroll "waving" while in portrait. If you have it in portrait and scroll up and down really fast you can see it big time. Even on daily normal scrolling I could see it. It really bothered me. Its too many pixles. I'd rather have uniform scrolling then the last line of pixels be a half second late compared to the first line. It's hard to explain but it is very annoying.
1920 X 1200 is probably the sweet spot right now. Anything over that is overkill and the GPU/CPU cant keep up.
Sorry to disappoint you but if you want a silky smooth performance go check out the iPad.
Android is just not made that way, it cannot be. iOS is always running on a device it is perfectly optimized for whereas Android has to run on no less then 4 different CPU manufacturers, not to even mention the differences within that particular chip set, then GPU, ram and screen. There are thousands of configurations Android has to support. That said, having so much support means you support the lowest and the highest of the bunch, offering a sub par experience on both.
You mention your GS3 often, just recall that the N10 is pushing over twice the resolution on a next-gen chip (read: android isn't optimized for it yet). For every 10 images on a web page loading on your GS3 there are 20 in higher resolution. You can see the issue.
Its no different then the age old battle of Winblows vs OSX. OSX is built for one architecture, one series of chips. Windows has to be run on thousands of configurations. A Windows PC will never be as smooth as a OSX device, even though the OSX device may have lower specs. On a OS level thats what you will always battle against. Windows and Android share the same issue. Also that's why Windows Mobile is so buttery, they only support a small chip set base.
Games are a little different, they can neglect the lower rung of devices and shoot for the Tegra or high end Snapdragons and Exynos. Hence why the N10 is so spectacular on this level.
So to sum it all up, if you want smoothness throughout the OS you need full optimization. Android in its base state cannot offer that and unless Android changes it will never. Samsung optimizes its Touchwiz systems to a large extent and that gives better performance. But in the flip side, the time it takes to optimize it is taken by delaying releases and not being current on the builds of Android.
Sent from my Nexus 10 using Tapatalk HD
altimax98 said:
Sorry to disappoint you but if you want a silky smooth performance go check out the iPad.
Android is just not made that way, it cannot be. iOS is always running on a device it is perfectly optimized for whereas Android has to run on no less then 4 different CPU manufacturers, not to even mention the differences within that particular chip set, then GPU, ram and screen. There are thousands of configurations Android has to support. That said, having so much support means you support the lowest and the highest of the bunch, offering a sub par experience on both.
You mention your GS3 often, just recall that the N10 is pushing over twice the resolution on a next-gen chip (read: android isn't optimized for it yet). For every 10 images on a web page loading on your GS3 there are 20 in higher resolution. You can see the issue.
Its no different then the age old battle of Winblows vs OSX. OSX is built for one architecture, one series of chips. Windows has to be run on thousands of configurations. A Windows PC will never be as smooth as a OSX device, even though the OSX device may have lower specs. On a OS level thats what you will always battle against. Windows and Android share the same issue. Also that's why Windows Mobile is so buttery, they only support a small chip set base.
Games are a little different, they can neglect the lower rung of devices and shoot for the Tegra or high end Snapdragons and Exynos. Hence why the N10 is so spectacular on this level.
So to sum it all up, if you want smoothness throughout the OS you need full optimization. Android in its base state cannot offer that and unless Android changes it will never. Samsung optimizes its Touchwiz systems to a large extent and that gives better performance. But in the flip side, the time it takes to optimize it is taken by delaying releases and not being current on the builds of Android.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Except I have a Galaxy Note 2 which is just as smooth as my iPad 3 was. This is nowhere close to as smooth as either device.
try the eos rom, i think it smooth, stable.... it also keeps running smooth after days of use.
http://forum.xda-developers.com/showthread.php?t=2178128
also in developer options there are 3 things i change on every rom down to. 5:
window animation scale
transition animation scale
animation duration scale
only web pg that doesnt seem to be smooth is 9 gag.
i keep my browser in desktop mode always.
bummer u have a bad taste from it, i find it to be a great hardware, but i like to tweak on it alot.
You are not the only one, check this video, N10 is not as smooth as the ipad or surface, go to min 5.00 http://www.youtube.com/watch?v=cI53tTXcPY8&feature=youtube_gdata_player
stock and boat browser made things much better for me, never use chrome.
NickTheMajin said:
Except I have a Galaxy Note 2 which is just as smooth as my iPad 3 was. This is nowhere close to as smooth as either device.
Click to expand...
Click to collapse
Again, this is an A15 w/2x the pixels to push
Sent from my Nexus 10 using Tapatalk HD
altimax98 said:
snip
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
That would be an excuse if this tablet wasn't designed by Google. Google was in charge of optimizing. They had to do it.
Sent from my A100 using xda app-developers app
I'm using the Ocean browser and scrolling is very smooth. So, maybe its inefficient apps?
plznote said:
That would be an excuse if this tablet wasn't designed by Google. Google was in charge of optimizing. They had to do it.
Sent from my A100 using xda app-developers app
Click to expand...
Click to collapse
Thaz the thing about software it can always be edited with new optimization and thus improve it. Its still a work in progress. Android always has been
Sent from my Galaxy Nexus
Settings -> developer options -> ( check ) force GPU rendering
Little more batt life drain I think ...
If you want good browsers :
(Smoothest)
Naked browser
AOKP browser
Sent from my Nexus 10 using xda app-developers app
Like every android device out there you just need to tweak the min free values to make it smoother. A good ROM/kernel combo helps too.
Add these lines to an init.d file:
chmod 775 /sys/module/lowmemorykiller/parameters/minfree
chmod 775 /sys/module/lowmemorykiller/parameters/adj
echo "0,1,3,7,11,15" > /sys/module/lowmemorykiller/parameters/adj;
echo "16384,20480,25600,51200,76800,102400" > /sys/module/lowmemorykiller/parameters/minfree;
chmod 644 /sys/module/lowmemorykiller/parameters/adj
chmod 644 /sys/module/lowmemorykiller/parameters/minfree
Where do I find the init.d file?
Sent from my Nexus 10 using xda premium
215alexdx said:
Where do I find the init.d file?
Sent from my Nexus 10 using xda premium
Click to expand...
Click to collapse
System/etc/init.d
Web browsing mostly also, here's...
the steps which have my n10 scrolling smoothly...
1. Start with tablet stock, locked, and setup complete.
2. Unlock and root tablet by preferred method and create nandroid backup. (May require understanding/knowledge of how to get out of bootloop)
3. Go to Play Store and update SuperSu (if required) and install Quick Boot.
4. Install preferred custom Recovery (TWRP is mine)
5. Download preferred custom ROM, gapps ( I prefer a minimum package like Rascarlo's), and kernel. (See mine in signature).
6. Use Quick Boot to boot into recovery, wipe cache, factory reset, then system. I just do...
7. Install ROM, wipe cache and dalvik, install kernel, then gapps. Again, I just do...
8. Reboot system.
9. Set up tablet then go to Play Store and update SuperSu (if needed).
10. Download and install BusyBox.
11. Update, install, and setup required/preferred apps from Play Store (AdAway and Naked Browser required for my tablet!)
12. Go into Settings and clean/disable everything under each setting I don't require or need for my tablet to web browse.
13. Boot into Recovery and "fix permissions".
14. Reboot system, set governor parameters, and enjoy!
This has worked for me without issue, can't/won't guaranty my results for others so use at own risk! :laugh:
My scrolling is good. I'm just on rooted stock 4.2.2. But then again, I may just not be as picky as other people.
Sent from my Nexus 10 using xda app-developers app
No problem here, my Nexus10 is running fast and smooth. CM10.1 no mods, with Dolphin as browser.
Paranoid Android + KToonsez kernel = silky smooth scrolling.
One flick will scroll top to bottom ANY page I have came across and it is VERY smooth.
Try one of the custom roms / kernels for this device and you will change your mind.
There are any disadvantages to go back to ice cream sandwich 4.0 version? Now I have custom 4.4.2 and it is laggy no matter what.
P7500
Sent from my Nexus 5 using xda premium
Lior84 said:
There are any disadvantages to go back to ice cream sandwich 4.0 version? Now I have custom 4.4.2 and it is laggy no matter what.
P7500
Sent from my Nexus 5 using xda premium
Click to expand...
Click to collapse
Perhaps you could try one of the lollipop versions. They (both aosp and Omni) are really stable. If you however need 3G I would suggest the aosp rom.
There's no harm in trying them out. If you still feel that they lag to much you can always go back to stock.
I've been running the aosp rom on my wifi tab for some time now and it performs pretty great actually.
Pretty great you mean responsive? Because I use omni 4.4.2 and it's laggy no matter what I do.
Sent from my Nexus 5 using xda premium
Lior84 said:
Pretty great you mean responsive? Because I use omni 4.4.2 and it's laggy no matter what I do.
Sent from my Nexus 5 using xda premium
Click to expand...
Click to collapse
Yes, responsive. I did overclock it to 1400mhz but it's running stable. Only youtube is sometimes not the best when running 720p videos.
Not responsive :/
Is it smooth when using chrome, scrolling and doing other activities?
Tell me the best settings to get it fast with Lollipop.
P.S: i suggest the cm10.2 ROM with tabletUI if you want smooth scrolling and graphics.
Mast3rC22 said:
Is it smooth when using chrome, scrolling and doing other activities?
Tell me the best settings to get it fast with Lollipop.
P.S: i suggest the cm10.2 ROM with tabletUI if you want smooth scrolling and graphics.
Click to expand...
Click to collapse
I can only speak from my experience with the aosp rom but scrolling in Chrome is smooth, I'm also using Nova Launcher and it is overclocked to 1400 mhz. Please don't expect miracles from this old device that samsung gave up on one ago. It runs 5.1.1 as smooth as it can. Also don't expect any hard core gaming and youtube will sometimes have issues. If all these things are deal-breakers then stay with whatever you have now. I wrote this from my own experience with my own tab. My father has the same one else only that one is bone stock. Touch wiz and everything with only a handful of apps installed. And yes it runs smooth and has less "issues" but it's running 4.0.4... I hope my explanation helps you make an informed decision.
Lior84 said:
There are any disadvantages to go back to ice cream sandwich 4.0 version? Now I have custom 4.4.2 and it is laggy no matter what.
P7500
Sent from my Nexus 5 using xda premium
Click to expand...
Click to collapse
I was considering the same. I was on 4.4 omni, seemed laggy. Flashed stock ICS, which did seem snappy but still bloated. I thought I'd give AOSP 5.1 a go. Haven't over clocked anything and its definitely smoother than 4.4 omni. Very compact ROM, I installed gapps and that only set google play. Currently tested WiFi and GPS and they're working. Chrome is smooth and running flash smoothly. Auto detected resolution on YouTube.com is smooth. Haven't tried YouTube app as yet. I normally use tubemate anyway. This tab will always have trouble playing 1080p vid. Max I go now is 720. Tried and its working fine using mxplayer. 5.1 is still in social testing but the bugs are slowly being fixed. I was on ICS for a long time as it performed well. Having experienced the same with 4.4 and now upgrading to this rom , I'm happy with how smooth and responsive it is. Ticks the boxes.
My main concern is lags. I run omni 4.4 on with nova and the response is disappointing.
Most of the time, my son use it to watch movies, YouTube and some games but nothing really hard. When I take it to do some stuff on it, the lags just giving me crazy. I know that the main problem is lack of RAM but hey, with 4.0.4 it works OK.
Sent from my Nexus 5 using xda premium
Going back does mean stability. The way I look at it though is you can only put so much into a mini, but it will always be a mini, not a Ferrari. Lollipop seems to work OK but its stretching the capability of this tab. For me with minor tweaks its going OK. A goto software always on all my droids is Greenify. It kills all the apps lingering in the background and stops them from opening again unless I open them. Try it out, you need all the ram you can get outta these older tabs. With the paid version it also kills system apps like google play services which is a big ram hog. I guess the only way you'll make your mind up is give ICS a go for a few days then try LP and see what you think.
A lollipop ROM might be smoother, if there would be the "Performance" menu in the settings app (like CM12).
If anyone has got any cyanogenmod ROM, i suggest these settings:
CPU governor:
• Intellidemand/ondemand: The CPU will increase the frequency when needed. It's default in many kernels. I really suggest that, because the device will be very stable (and smooth) and the battery life will be quite good :good: ;
• Performance: The CPU frequency will be set to max setting;
• Powersave: The CPU frequency will be set to minimum setting.
CPU min frequency: 150mhz (max. 200mhz)
CPU max frequency: overclock to 1400Mhz (do not overclock to 1.5 or 1.6ghz, the cpu will freeze and might be damaged)
I/O scheduler: deadline
zRam: 18%
Resources clean: on
KSM: on
PS: Enable "Set on boot" to each menu.
Sorry for the worst english ever.
I like decatf's 5.1 AOSP rom. He put a lot of work into creating a wrapper for hwcomposer which does a better job translating some of the newer rendering apis to work with the ancient ics binary Nvidia video driver blobs. That's why videos and animations are much smoother on his rom than the alternatives and why you don't get that weird "lightning bolt" rendering effect that's been around since pershoot's cyanogen jelly bean roms. He also implemented an audio driver wrapper as well in the same vein. And if you use his TWRP version, you can format /cache and /data to use f2fs, which definitely helps with disk I/O. He even ported over Multirom so you can dual-boot, but alas, it doesn't boot Ice Cream Sandwich roms at the moment.
It's the best modern rom thus far for the original Tab 10.1. Other than proper modern and native Nvidia drivers updated for Lollipop, the only thing really holding back the original 10.1 at this point is the Tegra 2's lack of NEON support. But there's nothing decatf can do about that.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Some phones exhibit choppy scrolling, especially when navigating long web pages when multiple apps are running in the background. Rate this thread to express how you smooth scrolling feels on the Essential Phone under such conditions. A higher rating indicates that scrolling is always buttery smooth, even when you're reading a 10,000 word article on "how to kiss a girl".
Then, drop a comment if you have anything to add!
It is choppy and freezes a lot. I did not expect this from a highend phone
Mine has a slight chop to it especially if there are ads and pictures in the article. Usually it is fine.
My first device ran pretty smooth, but after 2 months the fingerprint scanner stopped working. I received a replacement unit this week and this just runs horribly. I don't know if this is a touchscreen issue or software. Scrolling through Youtube or a web page will seem to just hang and not move. The other day the phone just hung in the launcher. I'm getting more disappointed with this on a daily basis. I'm almost tempted to install the Oreo beta just to see if that improves things.
Scrolling is hands down much smoother on my 2 year old Nexus 5x. Hoping Essential can fix it. It's been choppy on all of the stock-based ROMs. AOSP/custom ROMs appears to be really smooth.
If you're rooted try a kernel control app & switch the gpu governor to CPU freq, userspace, or performance. That worked well for me. Especially cpu freq & performance.
Scrolling has been smooth on open beta 2 and 3.
Sent from my PH-1 using Tapatalk
GPU governor
lbcary said:
If you're rooted try a kernel control app & switch the gpu governor to CPU freq, userspace, or performance. That worked well for me. Especially cpu freq & performance.
Click to expand...
Click to collapse
Touch scrolling is very choppy on my device. Even the app drawer is choppy as hell. I was on OB3 and it was the same. The only fix for me on all ROMs is to set GPU governor to cpufreq or performance (which I believe are similar in keeping GPU clock mostly at max). In the past Lineage 14.1 was super smooth, but for some reason all Oreo based ROMs are just as choppy as stock. Fortunately, the GPU governor tweak works great until Essential finally releases a fix. I'll believe it when I see it. If the GPU governor tweak didn't work, I would have moved on to a different device.
I thought it was really smooth with the GPU performance governor until I used my friend's Note 8. That thing has some smooth scrolling.
This device has horrible scrolling stutter that doesn't seem will be resolved anytime before I pick up the OP6. It's unfortunate that there isn't a fix for this problem, despite having released supposed fixes. I miss the OP3, never had a single issue.
If you like a buttery smooth and readable/responsive experience, pick any other phone. This won't give it to you.
On beta 3 stock, never rooted.
I don't own the phone, but I read about the issue, and this sort of thing has really bugged me in the past. I'm curious: has anyone tested the refresh rate by going to vsynctester.com in Chrome? I wonder if the refresh rate is significantly off the reported value and resulting in an asynchronicity of sorts.
MaulingDeOso said:
I don't own the phone, but I read about the issue, and this sort of thing has really bugged me in the past. I'm curious: has anyone tested the refresh rate by going to vsynctester.com in Chrome? I wonder if the refresh rate is significantly off the reported value and resulting in an asynchronicity of sorts.
Click to expand...
Click to collapse
Haven't used this site before, but on my phone, it's reporting 60.3-60.7 Hz refresh rate, on a 60.7 Hz screen. The word on the right generally stays grey with only 1-2 flashes of blue or red.
That’s not perfect, but it’s not too off the mark. I was expecting something like 55 or 65hz if it were to be the source of the stuttering. It’s gotta be something else causing it, then.
I'm running 8.1 Beta and the only place I notice a slight choppiness is on my Google Feed page. Very smooth everywhere else.
spmcd9 said:
I'm running 8.1 Beta and the only place I notice a slight choppiness is on my Google Feed page. Very smooth everywhere else.
Click to expand...
Click to collapse
I am on beta 8.1 already, the phone is not that smooth compared to my pixel 2 XL.
on Los 15.1 03/10/2018 and is buttery smooooooooooth!!!!!!!!!!!!!!!!!!!
For anyone who sees this and runs latest stock rom as of this reply, how is scrolling smoothness now? I am considering getting this phone for a relative but they come from a Nexus 6P and with that, smooth scrolling so switching to something like the PH-1 and have choppy scrolling. Is it any better than before?
JBlaze05 said:
For anyone who sees this and runs latest stock rom as of this reply, how is scrolling smoothness now? I am considering getting this phone for a relative but they come from a Nexus 6P and with that, smooth scrolling so switching to something like the PH-1 and have choppy scrolling. Is it any better than before?
Click to expand...
Click to collapse
I'm on P beta 2, scrolling jitter/frame drops are still there. Coming from a Nexus 6P I'm sure they will notice it.
NikoZBK said:
I'm on P beta 2, scrolling jitter/frame drops are still there. Coming from a Nexus 6P I'm sure they will notice it.
Click to expand...
Click to collapse
What about latest 8.1 build?
JBlaze05 said:
What about latest 8.1 build?
Click to expand...
Click to collapse
It is an issue with the screen/digitizer so it is never going to get fixed. You can either up the responsiveness and get jitters or make it smooth but very unresponsive.