**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
Related
Just wondering about the fire and how fast and smooth Ics runs. I would think the tp would be better due to specs.
Also if any devs read this wanted to ask what potential is reached on the to with the latest Ics. Like I have done all the tweaks and it still lags a little. Feel like its gpu related
Pure ICS only
Since you didn't mention what rom and clock speed and tweaks you have installed I can't really give you a biased answer on your question.
As for my TP, smooth, no lag, occasional errors and glitches, but keeping in mind the touchpad was never designed with android in mind as a daily driver. Through the hard work of the devs, we have it, but its still also ALPHA status. The kindle on the other hand was native android. Albeit a modified version, the kernel/drivers and other essential building blocks were already in place.
And as for my TP, AOKP, build 37, adreno 220 patch, rohans 1.4 patch which was still supercharged, and 1782mhz with performance governor.
Yeah it have pretty almost all your same mods. The lag I mean is touch response. Its like a split second lag and its minor.
Anyway was asking if the kindle fire rooms with Ics are smoother than the tp. I don't know if you were speaking from experience or just explaining something I already know.
Pure ICS only
Should have been a little clearer on your original question. Since I've never used or seen a kindle fire in person, I can't answer that. As for the AOKP rom, rom control has an option for scrolling cache under performance settings. While it does help, even my xperia arc with ICS has a slight snap when scrolling. In the CM7 roms there were settings to adjust the snap and bounce effects. Maybe down the line we will see those settings becoming adjustable but for now you just have to accept it.
Fataldesain said:
Yeah it have pretty almost all your same mods. The lag I mean is touch response. Its like a split second lag and its minor.
Anyway was asking if the kindle fire rooms with Ics are smoother than the tp. I don't know if you were speaking from experience or just explaining something I already know.
Pure ICS only
Click to expand...
Click to collapse
ICS roms run fine on the Fire. I'm on Gummy right now with no issues and no noticeable lag. That's with the new 3.0 kernel Hashcode is developing. With the 2.6 kernel I would have said stay away from ICS on the Fire, but the new kernel runs perfectly. I can honestly say I notice no performance difference between the Fire and the Touchpad in the ui and in general usage.
The Fire is a helluva budget tablet.
Sent from my Amazon Kindle Fire using Tapatalk 2
Hi new to android i have a GS 3 and want to know if Jelly bean will improve the gaming performance `framerates`???
davidebanks said:
Hi new to android i have a GS 3 and want to know if Jelly bean will improve the gaming performance `framerates`???
Click to expand...
Click to collapse
No. I don't think so. Google said that it had added extra frames for the ui animations only.
Gaming may improve if there is a newer linux kernel in jb.
Sent from my GT-S5830 using Tapatalk 2
I hope both improvements but I don't really know it, sorry
I'd put my money on it. Processing will now revolve around the VSync timing which should maximise the amount of time the phone has to render the next frame. If a frame is dropped, triple buffering will kick in and hopefully make it a smoother experience while increasing latency a little, and getting rid of it once it is no longer a problem.
Assuming this hasn't already been implented by games in some way (which i can't vouch for), there will definitely be a boost in consistent framerate (not performance, your CPU and GPU aren't becoming more powerful).
i think jelly bean is more simple and light than the older one, it should improve gaming performance.
Harbb said:
I'd put my money on it. Processing will now revolve around the VSync timing which should maximise the amount of time the phone has to render the next frame. If a frame is dropped, triple buffering will kick in and hopefully make it a smoother experience while increasing latency a little, and getting rid of it once it is no longer a problem.
Assuming this hasn't already been implented by games in some way (which i can't vouch for), there will definitely be a boost in consistent framerate (not performance, your CPU and GPU aren't becoming more powerful).
Click to expand...
Click to collapse
i watched the developer casts and it seems to be not like you pointed out. vsync is an additional feature which you as an app maker can use if you wanted to. they provide tools to line up your frames nicely but it will probably not affect anything else. im running JB for a week now and no app or game seemed faster to me. i saw the improvements when using their launcher though.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
molesarecoming said:
i watched the developer casts and it seems to be not like you pointed out. vsync is an additional feature which you as an app maker can use if you wanted to. they provide tools to line up your frames nicely but it will probably not affect anything else. im running JB for a week now and no app or game seemed faster to me. i saw the improvements when using their launcher though.
Click to expand...
Click to collapse
I watched the vsync portion of the presentation again to see if I got it wrong but ended up with the same understanding as I said. Unless there is a fundamental difference with games (now or in the past), it will all revolve around vsync timings internally within android.
Watch it again, if you understand otherwise let me know and correct me, I don't want to spread false information
Android 4.0 brought a ton of improvements in regards to the tracking of your finger on the screen. Using the Galaxy Nexus was a joy - accurately flicking through long lists with similar smoothness and accuracy to iOS. Jelly Bean brought it to another level surpassing iOS imo (but that's a different topic).
On the S3 "flicking" through lists or the browser feels disconnected and is much less accurate producing incorrect interpretations and scrolling when it shouldn't or vice versa. The main culprit I can see is the "smoothing" algorithm Samsung has added throughout the system and in the browser which works okay if you scroll very slowly and over large areas like a grandpa but for faster and quicker movements it just produces errors. Why couldn't they just stick with the ICS default behavior? Is there any way to get rid of the Samsung behavior besides flashing an AOSP-based ROM like CM or AOKP? I'd gladly flash those roms the day they get driver support but for now I just can't live without being able to use my camera and other "basic" things.
Using cm9 and camera I working fine snappy and touchscreen is very nice!
Sent from my GT-I9300 using xda premium
dinan said:
Android 4.0 brought a ton of improvements in regards to the tracking of your finger on the screen. Using the Galaxy Nexus was a joy - accurately flicking through long lists with similar smoothness and accuracy to iOS. Jelly Bean brought it to another level surpassing iOS imo (but that's a different topic).
On the S3 "flicking" through lists or the browser feels disconnected and is much less accurate producing incorrect interpretations and scrolling when it shouldn't or vice versa. The main culprit I can see is the "smoothing" algorithm Samsung has added throughout the system and in the browser which works okay if you scroll very slowly and over large areas like a grandpa but for faster and quicker movements it just produces errors. Why couldn't they just stick with the ICS default behavior? Is there any way to get rid of the Samsung behavior besides flashing an AOSP-based ROM like CM or AOKP? I'd gladly flash those roms the day they get driver support but for now I just can't live without being able to use my camera and other "basic" things.
Click to expand...
Click to collapse
There is driver support for CM9, samsung dropped the source code for ICS around release date, everything works and theres even CM9 stable releases in rom manager.
as far as i can tell 99% of things also work in CM10, the camera was 100% fixed today
mintvilla said:
There is driver support for CM9, samsung dropped the source code for ICS around release date, everything works and theres even CM9 stable releases in rom manager.
as far as i can tell 99% of things also work in CM10, the camera was 100% fixed today
Click to expand...
Click to collapse
Ok, wow I've been out of the loop, guess I'll have to update tonight.
Still, my original qualm is still valid is it not? =)
dinan said:
Ok, wow I've been out of the loop, guess I'll have to update tonight.
Still, my original qualm is still valid is it not? =)
Click to expand...
Click to collapse
so did you sort out how to feed your finger tracking needs ??
i feel i think exactly like you... id like to keep my crapwiz functionalitues, but i'm crying out for the miss of smoothness here.
since me and u seems to have the same needs on this topic, please let me know if you find out somethig intresting.
c ya
dinan said:
On the S3 "flicking" through lists or the browser feels disconnected and is much less accurate producing incorrect interpretations and scrolling when it shouldn't or vice versa. The main culprit I can see is the "smoothing" algorithm Samsung has added throughout the system and in the browser which works okay if you scroll very slowly and over large areas like a grandpa but for faster and quicker movements it just produces errors. Why couldn't they just stick with the ICS default behavior? Is there any way to get rid of the Samsung behavior besides flashing an AOSP-based ROM like CM or AOKP? I'd gladly flash those roms the day they get driver support but for now I just can't live without being able to use my camera and other "basic" things.
Click to expand...
Click to collapse
Have you tried running a custom stock-based ROM that has the scrolling cache disabled (such as WanamLite) or with a kitchen option to disable this cache (such as Omega)?
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
All in all jelly bean is nicer looking and snappy when scrolling where it may not have been with ICS however I've tried 3 different roms now and am experiencing a system wide lag when performing basic transitions like going back in an app or clicking a link within it, even typing like I am right now it occasionally misses a beat then speeds back up. Its to the point where it takes almost 10 seconds to click on a link in facebook before the next action progresses. I would assume its the cpu or ram but not sure how to address the issue. Any help would be appreciated
xlxcrossing said:
All in all jelly bean is nicer looking and snappy when scrolling where it may not have been with ICS however I've tried 3 different roms now and am experiencing a system wide lag when performing basic transitions like going back in an app or clicking a link within it, even typing like I am right now it occasionally misses a beat then speeds back up. Its to the point where it takes almost 10 seconds to click on a link in facebook before the next action progresses. I would assume its the cpu or ram but not sure how to address the issue. Any help would be appreciated
Click to expand...
Click to collapse
had the same problem with jelly bean so I went to Meanbeam and it is much much better.
I have noticed that a difference after getting rid of bloat as well.
Sent from my EVO using xda premium
Turns out it was a memory issue (obviousely). It seems inherent in the initial build for our device the ram management is simply not on par with how ICS handled it. I had less than 50mb free memory but you've got to consider that HTC sense has already been allocated its memory so it shouldn't lag the whole system. Hopefully the next update will address the issue...til then I ran v6 supercharger script and patched the framework for new minfrees.
There's a lot of sense related bloat in the stock ROM. If you're not interested in bloat, try cm10. Everything that matters works as of 1/16. Cm10.1 is fancy, camera will shape up when deck isn't sleeping. Just don't go for a cheap lazy king of cm, especially if it's one of 5 by the same winzipper, or if it crams 6 or 7 buzzword in the topic title like "Linaro optimized" or "battery boost." I dunno whatever.
Sent from my EVO using xda app-developers app