yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note I717] thair7391:
Excellent! Glad it helped. The only thing I'm really not satisfied with is Chrome's performance and I'm not 100% sure that it is related to JB rather than Chrome itself. Even in the latest official pure CM9 builds where we KNOW that hardware acceleration is working properly, Chrome is still a bit behind when you're scrolling, almost as if it uses its own API for scrolling instead of the one Android provides, which is odd because I would think Google's own web browser would integrate perfectly into their OS.

The only ROM in which I have used Chrome and had perfectly smooth to the eye scrolling without lag is h0tw1r3's h0tsauce derivative of CM9 that he made in the 14th and 17th of August. He must have added something in of his own that improved it but I'm wondering if it was a Chrome setting or an Android setting. perhaps I should ask him directly! Then maybe we could integrate the same tweak into Jb and have a complete JB experience.

I'll keep all of you informed on this endeavor.
[AT&T Samsung Galaxy Note I717] Web-head:
I would chalk it up to Chrome really.

I had a Galaxy Nexus. Bought one when Google first started selling them unlocked on the Play Store. Had it for only a week before I sold it, but I tried Chrome on it and it ran worse than the Stock Browser in terms of choppiness.

Now Chrome was in beta then, so that could be the difference, but even the newest version runs worse than the ICS Browser on the Note, so I think it still may not be ready for primetime fully.

Add in that Chrome hasn't seen an update since Jellybean was released (if I'm not mistaken) and I think it just might not be optimized for it yet. Or optimized period, as it never worked better than the ICS browser on either the Note or the GNex in my experience.
[AT&T Samsung Galaxy Note I717] Fasty12:
Wait a min fully accelerated??? no more lag!!!??!?!? if so then HELL YES!!!
[AT&T Samsung Galaxy Note I717] thair7391:
Yep! In the meantime have you tried the tweak I found to get GPU rendered performance?
[AT&T Samsung Galaxy Note I717] wase4711:
no, she likes being rooted, but doesnt flash roms; she is an IT Project mgr for a major corp though, so we both enjoy lots of hi tech stuff..
[AT&T Samsung Galaxy Note I717] Fasty12:
Yea im dling the new liquid rom atm will get back.
[AT&T Samsung Galaxy Note I717] ManelScout4Life:
Don't get your hopes up about this. It's in my new build, flicker got better but still exists.
[AT&T Samsung Galaxy Note I717] thair7391:
Haha. She likes being rooted eh? ;) lol. That's spectacular. I just had my heart broken for the first time when the girl I love left me and she was into computers too. Isn't it spectacular?? I suppose it is until they outsmart you! She hasn't done so has she?
[AT&T Samsung Galaxy Note I717] thair7391:
Thanks for letting me know. I suppose I was just excited to see the hardware getting some attention at all from Steve Kondik! Did you implement the debug.compositing.type="GPU" setting that I've mentioned earlier in your latest build? If not, have you experimented with the setting yourself any? I'm getting incredible results with it.
[AT&T Samsung Galaxy Note I717] ManelScout4Life:
I tried it, didn't seem much different. I'm pretty sure my ROM has a setting for that.
[AT&T Samsung Galaxy Note I717] Fasty12:
Hey thair i checked it out and it did make scrolling between homepage smooth, notif bar is smoother. However transition animation is still laggy especially since opening apps. WOnt this make your gpu overheat though?
[AT&T Samsung Galaxy Note I717] Gater2011:
My fav thread ..I use to always have a pondered look when people say these ROMs are so smooth..but I've always experienced lag..especially when transitioning from one home page to another ..glad to know it wasn't just me..the latest nightlys of CM10 are the first "smooth" JB ROMs I've experienced.. I do appreciate all the hard work all the devs put into making these ROMs though!
[AT&T Samsung Galaxy Note I717] Reclaim:
If the latest CM10 ROMs are smooth, the other ROMs will have it soon since they're based on CM10.
[AT&T Samsung Galaxy Note I717] thair7391:
I wouldn't think so. It isn't stressing the GPU beyond factory specifications (i.e. voltage, base clock, etc...) so it should remain under normal operating conditions regardless of how much is utilized. The only thing this setting is doing is telling Android to always use the GPU instead of the CPU when drawing graphics (or compositing) which is exactly the purpose of the GPU in the first place lol.
[AT&T Samsung Galaxy Note I717] thair7391:
How did the debug.compositing.type fix work for you when changing it to "gpu" instead of "dyn"
[AT&T Samsung Galaxy Note I717] Gater2011:
Let me put it this way..I laid in my bed watching a television show while scrolling through my home screen and app drawer for 30 min without opening any applications.. I was amazed when I changed it from "dyn" to "gpu".....awesome find :thumbup:
[AT&T Samsung Galaxy Note I717] borijess:
If this has been a great find, then why do you not see any devs implementing this?

Sent from the TermiNOTEr! ;)
[AT&T Samsung Galaxy Note I717] thair7391:
Either they haven't found it yet or there are negative repercussions from changing it that I haven't encountered yet.
[AT&T Samsung Galaxy Note I717] Reclaim:
If that's the case, someone should pass it along.
[AT&T Samsung Galaxy Note I717] Gater2011:
Like the other gentleman stated..maybe its some type of hardware issue that occurs..I've have yet to encounter any though...:D
[AT&T Samsung Galaxy Note I717] Afishl1:
Hey guys been doing some testing on this (though battery had been under 25% during so don't know how that's been affecting results).

For me, what I think I've noticed is that the switch from dyn to gpu has made the device overall faster, even verified through quadrant scores (btw I'm on PA cm10 plus flapps OC/UV).

HOWEVER, what I have also noticed is an increased occurrence of what I'd like to term "jitteriness(jt)"(not sure if this is the same thing people are talking about when they mention flickering) when scrolling, whether it's on long xda threads or on pdfs. This can be most seen in slow scrolling but comes from mixing fast and slow scroll speeds.

There is even also more of chance of this jt when "disable HW overlays(dho)" is checked in developer options (which for some odd reason is recommended to do).

For me, I'm in a little bit of an internal struggle, I always love speed, how ever I also love smoothness which for me is defined as the least bit of jt.

And so far, the configuration that has given me the least, and I really want to say actually no jt, is dyn w/ dho unchecked.

Can't comment on battery, and changing the other debug option (#1) also gave me jt.

These are easy tests and I'd definitely be curious to see what you guys think is the best config. Think I'm gonna leave gpu w/ dho unchecked for now as that was the last test config and it gives a lil bit of both worlds, speed and only slight jt (though I might have to go back, dyn is still pretty fast).

Sent from the Jelly Way Galaxy
[AT&T Samsung Galaxy Note I717] vijovame:
Thanks for the info, let me reboot my phone and test ;)

Edit: the maxlayer 2 to 3 did not worked for me, i got flikering

Dyn to gpu worked, my rom is faster now! Thanks
[AT&T Samsung Galaxy Note I717] thair7391:
I appreciate you sharing your thorough analysis with us about your experience. The "jitteriness" has unfortunately been n issue in Jelly Bean ever since it's been released for our device. I would differentiate that from "flickering" though. Flickering is where the screen essentially goes black for a fraction of a second and may do so once every minute, or a few times in a second; inconsistently either way. The reason that many developer are recommending that you check the "HW Overlays" option as well as change mdpcomp.maxlayer form 3 to 2 is because it stops the flickering, however not without its opportunity cost. By doing this, you are disabling an use of the GPU at all in rendering graphics, forcing the CPU to render everything (the HW overlays option) and you are also limiting the buffers (changing maxlayer form 3 to 2 buffers) that Android can use to Vsync or "smooth out" your graphics, so basically you have to disable HW acceleration and sacrifice smoothness to eliminate flicker at this point.

By changing from "dyn" to "gpu", I not only noticed an increase in speed of the overall phone, but a major increase in smoothness (less jitteriness), which is exactly what I was going for. I think from your post you said that you attained more jitteriness by making this change so you may have had a different experience than me. But by "jitteriness", I mean drops in frame rate, and you'll get more of that with the setting on "dyn" and the maxlayer set to 2.

There were some interesting changes in today's CM10 nightly that may pertain to graphics and buffers so I'm going to give the release a spin, investigate system changes, and report back on the performance.

And in the meantime, check out the changes and grab the build for yourselves!

And just so you guys know, I do a full wipe before installing each CM10 nightly, even though you can easily flash new ones over your current one because I want to be able to give everyone the most accurate information possible on what has changed and what has improved. If I flash over my current one, certain options like the debug.compositing.type could remain unchanged and then I'll never know if Steve Kondik added the change or if it's my old setting. I can also get a pure accurate assessment of CM's pure performance in its latest state and then compare it to the system changes that I usually make for performance.

Stay tuned!....
[AT&T Samsung Galaxy Note I717] thair7391:
Yeah, the maxlayer setting controls flickering at this point since there are glitches in using HW acceleration with more buffers (2 or 3). Unfortunately although a value of 3 gives you much smoother, faster performance, it comes with the flickering. I personally can deal with the flicker to get smoother performance so mine is at 3 but I can see why many people are using 2 for now. Either way, fortunately we have the new compositing.type setting to boost our performance that is independent of flickering so if you want to leave it on 2, you still get a boost!
[AT&T Samsung Galaxy Note I717] thair7391:
As I'm new to Android, I need to brush up on few things first, but I plan on making a ROM of my own for our device which will most definitely implement this feature.
[AT&T Samsung Galaxy Note I717] thair7391:
OK everyone I just gave the new CM10 nightly build (September 6) a spin and wow!! The performance has increased quite dramatically! The graphical smoothness is about the same, but it seems much more responsive! Many of you will be thrilled to learn that the flickering has been almost completely eliminated (withOUT having to sacrifice performance by changing maxlayer to 2!). Some things still trigger it though such as pressing the menu button on the home screen (in Nova Launcher anyways) and waiting on the lock screen with the display on. I still find it necessary to change the "dyn" setting to "gpu" in this build as there are instances of lag and stutter present that aren't present when I change the setting. The bug that causes the phone to crash when using the multi-task switcher still exists (very frustrating), as well as using Google Play Music to stream your online library. In my experience, it may play the first song you start but then it says "Could not play the requested stream" when you change tracks.

Apart from that I find it worth upgrading to. I am using DaGr8's recent kernel since it offers more governors, but I'm sure flapjaxx's kernel works just as well in this build, as I used it in the previous one.
[AT&T Samsung Galaxy Note I717] :
I agree it seems better. Unfortunately I'm getting phone calls that go straight to speaker phone and the toggle doesn't change it. Or crash when I receive a call

There are some open audio commits and I'd say wait for next nightly if you want a phone tbh. If you don't talk on the phone ever, probably not an issue, but audio is pretty messed up on 906.
[AT&T Samsung Galaxy Note I717] Slammin:
I use Apex and after reading this entire thread (thanks OP for bringing this up in a constructive way), the only way I can attain what I feel is ultimate smoothness is by not displaying icon names on the home screen. Try that and you will be amazed!
[AT&T Samsung Galaxy Note I717] thair7391:
Yeah I've also seen reports about audio issues as well. Better stay on the 9-05 build for now.
[AT&T Samsung Galaxy Note I717] thair7391:
Just thought I'd let everyone know, I'm downloading the prerequisites that I'll need for compiling a customized ROM of my own for the first time as I type this so expect something (even if its garbage lol) within the coming two or three days. I'll at least promise that whatever the end product is, it won't harm your device!

(No one ask to donate... Donations NOT necessary. Considering how new I am to this, it probably wouldn't be worth it anyways haha)
[AT&T Samsung Galaxy Note I717] wase4711:
I assume you will be paying us to be your test crash dummies...
[AT&T Samsung Galaxy Note I717] thair7391:
Hmm... Depends! What form of currency are you expecting?
[AT&T Samsung Galaxy Note I717] wase4711:
gold bullion would work for me
[AT&T Samsung Galaxy Note I717] ManelScout4Life:
If you'd like a make shift guide that I have made for others PM me your email.
[AT&T Samsung Galaxy Note I717] thair7391:
Damn... How about a steady flow of releases once I start getting the hang of things?
[AT&T Samsung Galaxy Note I717] thair7391:
Thanks John!! I'm going to give it a shot with what I have and I'll gladly request your guide after my first compilation. I know that you're fairly new as well so perhaps I can learn a lot from you. Hell, maybe we can form a partnership if I foresee having any proficiency in this sort of thing.
[AT&T Samsung Galaxy Note I717] Afishl1:
Hey thair, so could you give a little more specifics on how to show flickering, I'm not sure if I'm getting that or not.

As for the fps, I agree that the gpu does better than the dyn in quadrant, but I think that is different than the jt I was talking about, did you try looking at the scrolling on pdfs and such while mixing up the scrolling movements/speeds?

I think we need some specific things to try/tests to compare results, even as simple as a certain youtube video or something like that.

Sent from the Jelly Way Galaxy
[AT&T Samsung Galaxy Note I717] thair7391:
When you say "how to show flickering", what do you mean? I know what fixes it in CM10's current state as well as what enables it, but is that what you're asking or are you wanting me to illustrate or demonstrate what my interpretation of flickering is?
[AT&T Samsung Galaxy Note I717] Afishl1:
I meant is there some repeatable action I/we can do on our phones to check if we have it?

Now, that I think of it, maybe I don't want to know, ignorance is bl...

No, but really, is there?

Btw, when I'm talking about scrolling, I'm not taking about flicking the screen up and down watching the smoothness of the momentum/inertia scroll, I'm talking about keeping your finger on the screen moving it up and down and looking at the text for the jt.

For me with gpu, sometimes it will jt and sometimes it won't, but on dyn it never did from what I remember.

Try loading a pdf over at least 1MB.

Sent from the Jelly Way Galaxy
[AT&T Samsung Galaxy Note I717] ManelScout4Life:
Bringing up the power menu will show the flicker if your ROM has it.
[AT&T Samsung Galaxy Note I717] Afishl1:
Do you have to look really hard for it, or is it easily noticeable, cause I'm having trouble seeing it.

Maybe I'm just lucky and don't have it.

Sent from the Jelly Way Galaxy
[AT&T Samsung Galaxy Note I717] ManelScout4Life:
The ROM your using doesn't have it. You would notice it right away.
[AT&T Samsung Galaxy Note I717] Afishl1:
Yeah for me I think the biggest annoyance is the jitter and now even see some of that it lag, what ever you want to call it in the momentum part of a scroll on long threads (good example is [and first set your options to 50 posts a page] using this xda app and going to the link a few posts down in dagr8's kernel thread which leads you to a thread explaining governors, I/O scheduling etc; would link but don't know how to through this app).

Sent from the Jelly Way Galaxy
[AT&T Samsung Galaxy Note I717] Afishl1:
Man, I updated to the PA 2.1 Sept 06 from Aug 28 build and now I have the flicker :'(

So now I have to check the HW overlays option and with gpu I got those nasty jitters.

I also switched to dagr8's kernel so I'm not sure if that had anything to do with the flicker or jitters.

I'm also wondering if messing with setcpu settings, like tweaking the governor or changing the scheduler would effect the jitters.

The other thing I've noticed and feel is related is super fast scrolling of a long page in a thread with long posts, it for some reason will just pause momentarily and then continue to keep scrolling, like it's loading it for a split second. I wonder if this is a cache related issue.

I really don't mean to hijack this thread with all this jitter talk and I don't know how many of you have this, but to me that is a huge part of smoothness that is in my face all the time.

Sent from the Jelly Way Galaxy
[AT&T Samsung Galaxy Note I717] wase4711:
i think your jitters made you post this in the wrong thread..
[AT&T Samsung Galaxy Note I717] Afishl1:
Nope, don't know where your coming from with that, reread through the thread

Sent from the Jelly Way Galaxy
[AT&T Samsung Galaxy Note I717] wase4711:
yep, sorry, you are right...too early to think!
[AT&T Samsung Galaxy Note I717] thair7391:
Lol. You thought he had amphetamine jitters?
[AT&T Samsung Galaxy Note I717] thair7391:
Earlier you differentiated jitter from smoothness so the only thing I can really think of is that its a sort of calibration issue. When you say "jitter", do you mean, if you slowly drag your finger across a page of some sort and the page kind of jumps or moves inconsistently with how your finger is moving? That happens to me sometimes but only if my finger is damp or very cold or something. It's due to interruptions in "touch transmissions".

If you are attributing the jitter to smoothness, then I don't think you're hijacking this thread, but if your jitter is what I explained in this post, then it may be a separate issue than we are discussing in this thread.
[AT&T Samsung Galaxy Note I717] vijovame:
Adding this post from q&a thread of pa cm10 from jamie, is good to let here know why maxlayer 2 to 3 did not worked
[AT&T Samsung Galaxy Note I717] Slammin:
Can someone try turning off icon labels on the home screen only and report the result? For me, everything gets smooth as glass (running Apex) at the home screen. All other screens are already jitter-free for me.

If you only have a few icons, it may not make a difference but I run 7x7/7x7 and have about 21 icons on my home screen.
[AT&T Samsung Galaxy Note I717] wase4711:
No, I had those "lack of caffeine" jitters...
[AT&T Samsung Galaxy Note I717] thair7391:
Ahh same difference. Caffeine is a phenethylamine derivative and amphetamine is just an abbreviation for "alpha-methyl-phenethylamine". They both modulate the release of dopamine and norepinephrine to increase energy, focus, and alertness and have similar withdrawal syndrome symptoms. :)
[AT&T Samsung Galaxy Note I717] wase4711:
are you in med school, or just a drug addict? :eek::eek:
[AT&T Samsung Galaxy Note I717] Afishl1:
wish I knew, feel like it's something is have to show in person, just going that one day it magically gets fixed.

Btw, think dagr8's kernel gave me flickering

Sent from the Jelly Way Galaxy
[AT&T Samsung Galaxy Note I717] Eric-1987:
I don't think addict is the correct word. Maybe not a drug idiot? If I do something I make sure I'm well researched before hand.
[AT&T Samsung Galaxy Note I717] thair7391:
Neither. I'm just extremely interested in organic chemistry and pharmacology. And a curiosity for the experiences psychotropic substances can bring because I believe they can make sense of misunderstood human conditions as well as unlock potential for humans to conceive that which is limited by the physical extent of the natural realm.
[AT&T Samsung Galaxy Note I717] thair7391:
Hmm... I've tried both and neither kernel has "caused" flickering. Double check your maxlayer. That is the only thing controlling flicker at this point. At 2 there is no flicker but slow performance. At 3 smooth performance but flicker.
[AT&T Samsung Galaxy Note I717] wase4711:
flapp has just released a rom called Slappjaxx; its on his website, and it is the smoothest JB rom I have tried, bar none!

its a Kang of the Liquid Rom..

cheek it out, if you want to see buttery smooth jb!
[AT&T Samsung Galaxy Note I717] ArborRes:
Link please?
[AT&T Samsung Galaxy Note I717] wase4711:
http://rootdev.org/topic/rommodkang-slappjaxxx-liquid-smooth-962012/
[AT&T Samsung Galaxy Note I717] thair7391:
Hey guys, I've had a few unexpected, unfortunate events that have delayed my progress in finding more solutions to JB smoothness, flicker, and creating my own first ROM, but accept this as it were, a mere delay. Not a termination! I'll be picking back up where I left off in a few days or so.

I did however want to let all of you know a temporary solution I've been using all day today since the recent issues the past fee nightly builds of CM10 have been having with audio and Bluetooth and such. They have great performance boosts but they have seemed to disable previously working functionality so to get the best of both worlds, I have flashed the latest 9-8 build first (with a clean wipe) and then after initializing it and setting up Google account, I flashed the 9-5 (the last known stable build with functional audio and Bluetooth) only wiping Cache and Dalvik afterward. I've noticed that the "dyn" to "GPU" setting works SIGNIFICANTLY better on the 9-5 build than others (haven't figured out why this is yet) so definitely change that after flashing the 9-5 build atop the 9-8 build. And finally, I've found that they "could not play media stream" error in Google Play Music can be resolved by removing Apollo! I'm not sure why but since I'm streaming my music through Play and not playing it locally, I can afford to remove Apollo (although I am rather fond of it for local music) so this is the fix for me. I know it's all kind of a dirty set of solutions but in the end, it makes for a very decent stable OS on our device in context of what we have available so that's why I'm sharing. I plan on including all of these mentioned items in the ROM I build if these issues are still present when I finally compile.

Let me know if this has helped you so I can know whether this is a viable solution for many users as opposed to just me.
[AT&T Samsung Galaxy Note I717] Emir5kurt:
I have a question. Isn't changing the prop.build from dyn to gpu same thing as checking "force gpu rendering" in developer options?
[AT&T Samsung Galaxy Note I717] thair7391:
Intuitively, one might think so, but in reality, they can't be the same because enabling the developer option will disable flicker and cripple performance, making me think its closely related to the maxlayer setting, while changing compositing.type setting only increases performance and has no effect on flicker. I find this odd also... Learning is fun!
[AT&T Samsung Galaxy Note I717] esco757:
Tested & confirmed.... My phone is flying!!!!!:good::cowboy:......This is the one that needs to be supported
[AT&T Samsung Galaxy Note I717] thair7391:
Hmm... To be honest, i tried that ROM and didn't really notice any difference. What all did you do to configure it after you installed it to get at running as good as you say it does? I changed the maxlayer back to 3 (because 2 is too laggy) and tried the type setting on both "dyn" and "gpu" and still found th performance behind CM10 nightly builds.