yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] jerrylzy:
try deleting this line in build.prop: debug.composition.type=gpu

---------- Post added at 04:46 PM ---------- Previous post was at 04:40 PM ----------

I believe c2d refers to jdi_c2_display. We should use HW overlay IMO. I'll try ur values and test:D

EDIT1: I rebooted with ur values, but the result is worse. I'll test more combinations

EDIT2: OK, I almost tried all possible combinations. I think mdp is innocent; the real culprit should be 'debug.composition.type=gpu'.

After I deleted this line the phone gives me incredible smoothness.

It also proved my result that disabling hw overlay lowers performances in gaming. [MENTION=1144067]hamdir[/MENTION]
[One (M7) Original Android Development] Mikanoshi:
gpu is a default value when debug.sf.hw = 1, so how it influences anything? :D
[One (M7) Original Android Development] jerrylzy:
I believe the later line sets it to mdp. If u delete it and reboot u'll notice the difference. Just repeatedly press app drawer button
[One (M7) Original Android Development] Luisit0:
so if i get stutters scrolling on the appdrawer and blinkfeed (and some others, not so noticable) i should delete that line, reboot and see a difference?
[One (M7) Original Android Development] jlevy73:
Thanks Jerry tried your suggestion but it didn't help. I still get the same micro-stuttering.

---------- Post added at 05:12 AM ---------- Previous post was at 05:11 AM ----------

That's the theory, however, I just tried and didn't see any difference. Try for yourself though, hopefully it will improve things for you.
[One (M7) Original Android Development] DeSaint2:
The thing that helped me was taking out the persist.hwc line or making false.
[One (M7) Original Android Development] superbellefleche:
+1
[One (M7) Original Android Development] b00f13:
Did you remove "debug.composition.type=gpu" ?
[One (M7) Original Android Development] DeSaint2:
No left that. If I read correctly that is what forces gpu rendering of Ui. The persist line causes a conflict so it falls back on cpu rendering.

If I am wrong, anybody feel free to correct me.
[One (M7) Original Android Development] Luisit0:
I won't lie, this literally smoothened the UI to the point of almost no stutter left. Blinkfeed is as smooth as ever, page transitions too, opening and closing folders, opening and closing app drawer, everything is lagfree, except for up/down scrolling on the app drawer... That's almost, ALMOST, lag/stutter free, but occasionally a tad bit of stutter can be seen. Though, it's so minimal now, I can live with it :) thanks a million for sharing this discovery!
[One (M7) Original Android Development] lilhaiti:
+1

Maybe it's placebo but I notice a lot more smoothness after setting to false. I was at one point doing this manually in Developer Options and checking Disable HW overlay. Same results but I had to do it at every boot.
[One (M7) Original Android Development] jlevy73:
Yes, that did the trick, even on stock kernel it makes a big difference.
[One (M7) Original Android Development] MartinS13X:
I never really knew what people meant with "micro stutter". Paid attention to some animations before setting the line to FALSE, and after rebooting the first thought that went through my mind was:

"so that's what they mean with microstutter!".

Every animation seems so much smoother, faster.

Love it. :highfive:
[One (M7) Original Android Development] jerrylzy:
Have you guys checked Force 2d gpu rendering? Or maybe my phone is so different than all of yours?

My way to test is to repeatedly press app drawer button, and no other combinations gave me smoothness of that level

Here are my settings:

ondemand

deadline

read buffer size 128k

HW Overlay Enabled

Force 2d GPU Rendering

debug.composition.type=gpu removed

persist.hwc.mdpcomp intact

:( My Unit is so different that disabling HW overlay gives me lags and performance loss in games
[One (M7) Original Android Development] cee43ja1:
Edited the build.prop to hwc.mdpcomp.enable=false, and scrolling seems smoother now.

[MENTION=4684315]flar2[/MENTION], is it possible to change the vibration strength when compiling the kernel? Trickster MOD shows it at 2000, and that's extremely low; haptic feedback is basically nonexistant. 2700-2800 seems to be close to stock. ElementalX 3.12 and previous versions didn't have low vibration strength.
[One (M7) Original Android Development] Shan89:
You guys should know that this could increase battery drain , HTC most likely users mdp for battery life.

Anyway I'm not having issues on latest insertcoin.
[One (M7) Original Android Development] Luisit0:
i always test scrolling as slow as i can up and down on the app drawer and on blinkfeed, so smooth now i cant believe it was a matter of changint a line from true to false lol especially after having messed with gpu so much before.. so u also have force gpu rendering for 2d graphics and hw overlay enabled? i might try that too, though i didnt delete the debug.composition.type=gpu line and im running fiops scheduler
[One (M7) Original Android Development] hamdir:
nevermind more info here:

http://xdaforums.com/showpost.php?p=46044104&postcount=5653
[One (M7) Original Android Development] WastedJoker:
FYI, this also fixes the issue with Amazon Kindle app not working unless developer options are switched off.

Kindle used to dislike Force GPU Rendering being switched on so I assume setting the prop entry to "false" works in a similar vein.
[One (M7) Original Android Development] Shan89:
@ Hamdir

I'm telling " force 2d gpu rendering "works 100% , please do this so you see yourself , turn off 2d rendering , download " advanced mobile care " from market , open it , you'll see the box in the middle click it it'll slide up a menu you'll see it lagg/stutter like hell , exit the app , enable " force 2d rendering " and open the app and do the same you'll see menu will slide up perfectly smooth 60 fps.

Anyone else who's willing to test this please do so and report , ty.
[One (M7) Original Android Development] hamdir:
look what ever it is, one thing is very clear, commenting out will give you the same result, in fact commenting out the entire display section will give you the same results, so there is only one clear conclusion android is not supposed to work this way

---------- Post added at 08:50 AM ---------- Previous post was at 08:41 AM ----------

Force 2D GPU rendering seems to work within apps, ie: forcing apps to use GPU, you can use it from the developers section and it sticks on reboot

i am more concerned with the UI smoothness which what the disable HW overlays seems to clearly affect and this one doesn't stick on reboot if used from the developers section

like i said you dont even have to disable HW overlays, set compositions to what ever you want, just remove the persist mdp line which is clearly brute forcing everything into mdp

hell even 60fps videos are now working without CPU boost on EX, what more proof do you want that mdp shouldn't be brute forced?
[One (M7) Original Android Development] WastedJoker:
I'm not arguing with you :)

After installing latest available build of 4.3 with 3.22.1540.1 base I discovered Amazon Kindle app would FC every time. I googled around and most people suggested turning off "Force GPU Rendering" but I never even had it switched on. I messed around a bit and eventually found the solution was to turn off Developer Options.

Then someone posted in ARHD22 thread about your discovery so I tried it. I then got to wondering, because it was an edit to do with rendering, whether this would affect Kindle app. So I turned Dev Options back on, rebooted ad voila! Kindle now works without crashing.

So, in summary, I don't think this is a placebo considering it had an actual effect on the ability of an app to function.
[One (M7) Original Android Development] Shan89:
The weird part is I don't have any of the stutters across the ui , it's in fact smoothest ui I ever had on insertcoin 4.0.1 there's 4.0.2 tho update is for s-on users , I'm also odexed , maybe odex + 0.25 animations are responsible for the smoothness. I'm also on stock kernel + power saver enabled , waiting for the source so Flar updates , don't like the mini stutters atm tho gaming is no match stock vs ex 5.4

Also some users are reporting after flashing complete 3.22 ruu their phone feels a lot faster , hamdir willing to test lol :sly: ?
[One (M7) Original Android Development] hamdir:
dude im testing both stock kernel and EX, and you can clearly see the issue if you zoom out from root explorer, script manager or opera mini, try it!

i edited my previous post, even 60fps videos no longer stutter without boosting the CPU on EX

i just dont see why would HTC force everything on mdp, makes no sense
[One (M7) Original Android Development] Shan89:
I assume you're talking about zoom in / and out on multitasking ? If so I see minor stutter there.
[One (M7) Original Android Development] hamdir:
no its lag not stutter in certain apps only and you cant really judge from your custom ROMs like insertcoin since chefs doe their own tweaks as well

i am talking about the pure HTC build.prop

---------- Post added at 09:19 AM ---------- Previous post was at 09:15 AM ----------

seems its also being used in GE

Sense, 3.22

#
#system props for display
#
debug.sf.hw=1
debug.egl.hw=1
debug.composition.type=gpu
debug.enabletr=true
ro.hwui.renderer.disable_opaque=true
ro.sf.lcd_density=480
persist.hwc.mdpcomp.enable=true
debug.mdpcomp.maxlayer=3
debug.egl.buffcount=4

GE, 3.07

#
#system props for display
#
debug.enabletr=true
ro.hwui.renderer.disable_opaque=true
ro.sf.lcd_density=480
persist.hwc.mdpcomp.enable=true
debug.mdpcomp.maxlayer=3

i am looking online seems this is added to all 4.2.2 in general...hmm :rolleyes:
[One (M7) Original Android Development] Shan89:
Ahh I see , well I guess I'll step a side since I'm never on stock unless applying ota.
[One (M7) Original Android Development] hamdir:
ok more info here from the firefox devs, persist seems to be added in Android 4.2.2

so this looks like MDP is a better power saver compared to GPU compositions, however apps needs to support it properly, compositions can run on the GPU, partial MDP or full MDP, so looks like older apps needs to support it in new versions or something

anyway if you want to disable hw overlays and force it on boot, that's the only way, to remove the persist line
[One (M7) Original Android Development] gGabi:
Meanwhile, around 30 OT posts, nobody seems to care :)
[One (M7) Original Android Development] hamdir:
around a dozen people are discussing this, so please let's not generalize and have some respect

when people keep blaming stutters on the kernel and it turns out to be something else it's certainly on topic, not to mention performance seeking is also on topic

anyway im done
[One (M7) Original Android Development] donmarkoni:
Thank you very much for your analysis! :good: And it was not off-topic, if everybody blames the kernel, as you said.

Please keep yourself involved. There are people here that respect your work and opinion. :highfive:
[One (M7) Original Android Development] Shan89:
+1

I should mention one of the reasons why I even bought last year one x and this one is cuz of hamdir , I enjoy his findings and reading the stuff he posts + it's a joy to experiment with him and find things out , HTC One forum would be boring for me without his contributions.
[One (M7) Original Android Development] lichti1901:
Your´s included mate ;)
[One (M7) Original Android Development] jlevy73:
I tried this on stock kernel to see how it would run and seems smooth. Will try flashing EX 5.4 and see how things run then. Thanks for the suggestion, hopefully this will resolve the stuttering.
[One (M7) Original Android Development] tiho5:
Just want to say : Thank you, mate!

Good to have guys like you around here!
[One (M7) Original Android Development] hamdir:
look guys to summarize

the persist mdp compositions command was added to android in 4.2.2, MDP is better for battery and app devs will need to migrate their apps

however apps needs to support it, for example i had root explorer 2.4 lagging on every zoom out and it was solved by forcing GPU overlays

however I re-enabled HW overlays and updated root explorer 3.1.1, now it buttery smooth, most likley it means the app is properly supporting mdp now

so this is only an issue which affects old apps or non updated apps

equally now we know how to disable HW overlays and force GPU compositions on boot

it's as simple as that let's now over blow the whole thing

lets move on
[One (M7) Original Android Development] KS_Ho:
Proximity Sensor Issues

Anyone found a fix for the proximity sensor issue? Seems like it's a custom kernel issue as TeamSeven also have this problem where the screen would stay black after a call, unless you place the sensor under extreme bright light. I've already asked the users on ARHD 22.0 and the users that are on Stock Kernel do not have this issue, only custom kernel users (ElementalX / TeamSeven).
[One (M7) Original Android Development] Shan89:
I don't have this issue on any 4.3 based kernel.
[One (M7) Original Android Development] Ozonethegreat:
Multi-Rom Support?

It is possible to include the kexec-hardboot patch to support Multi-Rom? http://xdaforums.com/showthread.php?t=2460886
[One (M7) Original Android Development] EtherealRemnant:
I am in love with this kernel but I'm wondering if I can tweak this further.

Aroma - 1566 max, 750 at 384, 504 GPU.

I massively scaled down the voltages using Trickster but I'm curious if I should go to 1.9 and undervolt a bit further or just leave it alone. Its totally stable. And my temps hit 103 under load max while charging and benchmarking whereas previously it would hit 110 and throttle.

http://img.tapatalk.com/d/13/10/01/6aju3y7u.jpg[/IMG

Edit: No matter what settings I use, The Simpsons: Tapped Out crashes with this kernel. Anyone else have that issue?
[One (M7) Original Android Development] threetwentyfizzle:
Holy hell 3.12.1 is flying on Viper 2.7. 504 gpu and 1.9 cpu is the smoothest and fastest ive seen. Loving it thanks again Flar!
[One (M7) Original Android Development] safepacket:
+1 for that ..

On viper 2.7.0 (the best 4..2.2 combo i have experienced)

deadline/Ondemand (up_threshold changed to 70) @ 1.8 uv -850

read ahead 128 with simple gpu@504..

3.11 was great.. but 3.12.1 is pure awesomeness thanks Flar! :good:
[One (M7) Original Android Development] flab80:
Fantastic kernel

Version 5.4 beta works fine with ARHD 22 and base 3.22.

Now i works with CPU at 2160 and GPU at 504.

Antutu reports me 31021.

Fantastic!!!!

Thanks flar
[One (M7) Original Android Development] GelullaBarr:
What settings did you made to get that score?
[One (M7) Original Android Development] vrthe1:
Can you implement Flick2Wake and Pick2Wake?
[One (M7) Original Android Development] flab80:
Hello,

with Trickster MOD i used settings in attacehd images
[One (M7) Original Android Development] EtherealRemnant:
What are your temps like with that set up? Seems like something you couldn't run for very long.
[One (M7) Original Android Development] flab80:
I use this config all day without problems. As governor instead of performance I use intellidemand for cpu and on-demand for gpu but frequencies and voltages are the same
[One (M7) Original Android Development] EtherealRemnant:
I might have to try it. I am running 1.9 @ 1125000 right now and loving the speed and battery life. I need to tweak my voltages some more though - I don't have the full Trickster MOD so I have to test with Trickster and then and only then use Kernel Tuner since the settings stick on reboot and I end up having to reinstall my ROM if I end up in a boot loop.
[One (M7) Original Android Development] flab80:
Me too I don't have full Trickster,I use the free version of Google play.

I try to tests some frequencies but the most stable I use is 2.160 @ 1275000 and intellidemand

Before I must restore system several times cause bootloops or instability!

Now, with more than 15h cpu temp is 36 and battery is 30.2 with 60% remaining.
[One (M7) Original Android Development] milesjohnson:
does anybody have good settings for trickstermod for good battery life? i dont understand all the technical stuff involved in the app but if someone could just provide me with settings that work well for them for good battery life i would be very grateful.....

on that note....what about using the settings from this post (fauxs kernel) for battery life? http://xdaforums.com/showpost.php?p=40835632&postcount=2 will they work just the same on this kernel? and i purchased the fauxclock app....do i need trickstermod to input these settings? thanks guys :cowboy::cowboy::cowboy:
[One (M7) Original Android Development] Freak07:
you may use faux's app too, but not all the settings he built into his kernel will be available in elemental.
[One (M7) Original Android Development] SleemLDJ:
I'm running a GPE rom that has Seeder as an option in aroma so I installed.

My question is if I install elementalx kernel for GPE and seeded options are enabled, are there gonna be any clashes?
[One (M7) Original Android Development] Freak07:
i do not think it will interfere but you really don't need any seeder app on this phone ;)
[One (M7) Original Android Development] iexplus:
May I ask if there is any differences or changes between 5.4 beta and 5.4?

Thanks.
[One (M7) Original Android Development] iElvis:
flar2 can confirm, but I really doubt it as he always changes the version number if there are differences. You can assume he just dropped the "beta" because 5.4 was ready for daily driver use (and it is).
[One (M7) Original Android Development] Denpech:
In a theme date [Oct2] ElementalX |OC|UV|GPU OC|S2W|L2W|DT2W|L2M|THERMAL|BLN was replaced, there was a new updating? I it do not see.
[One (M7) Original Android Development] GelullaBarr:
no more beta for 5.4 and now is just 5.4...maby this is the reason
[One (M7) Original Android Development] hamdir:
[MENTION=4684315]flar2[/MENTION] if I may I have a suggestion mate

in the GPU OC situation, the best thing is the ability to change the clocks on the fly like using scripts but there is no need for high gpu clocks during UI use, sadly 320mhz is noticable in less UI smoothness, I can't help but wish if I can use the 400mhz during non boost and use the higher clocks in boost, currently we are forced to choose between 450 and 320, there is no inbetween

I also think u should keep pnpmanager disabled and keep adjustable gpu clocks, to hell with android OEMs contextual performance! we should take control

and by the way everyone

I managed to fix my drain

caused by HW overlays disable and keep my UI

smoothness for non mdp apps

simply comment these three lines in build.prop

#debug.sf.hw=1

#debug.composition.type=gpu

#persist.hwc.mdpcomp.enable=true

this should allow apps to choose mdp or gpu on

their own instead of forcing either modes, there is little battery side effects this way
[One (M7) Original Android Development] wmg316:
This seems to be the winning combination for me! Noticeable difference!

Thanks [MENTION=1144067]hamdir[/MENTION]!
[One (M7) Original Android Development] rohorubo:
Where did you set these commands?

Gesendet von meinem HTC One mit Tapatalk 4
[One (M7) Original Android Development] eyosen:
/system/build.prop
[One (M7) Original Android Development] belloni:
Trying to install this kernal on Maximus 14 but when it gets to the installation part, it gets to 10% then reboots itself to normal?!
[One (M7) Original Android Development] strickyy:
flar2 Could you add a lower auto brightness? Mayb an option in Aroma to install CM brigtness levels? You'd make my day, month and year. Loving the kernel anyways though.
[One (M7) Original Android Development] tiny4579:
That's a ROM feature not kernel.
[One (M7) Original Android Development] tiny4579:
Doesn't commenting out debug.sf.hw=1 disable hw composer? I wouldnt think wed want that. Unless it uses androids default which may be 1 anyway.

Interesting thing I noted was that cm is using dyn instead of GPU. Not sure what's different. Perhaps I need to look into the source a bit more.
[One (M7) Original Android Development] EtherealRemnant:
I wonder if those settings have anything to do with The Simpsons Tapped Out crashing... It works fine on the stock kernel but as soon as the town starts loading, it crashes back to Sense :/

I don't have any other problems with the kernel, just that one.

Sent from my HTC One
[One (M7) Original Android Development] morfini:
The most awkward moment for my phone's ui, is after holding my finger down to chose a widget. The lag is very noticeable. Is there something that can be done for that?
[One (M7) Original Android Development] mistersquires:
my benchmark scores have gone down but its the most stable combination ive found so far. changing the settings is easy with trickster and the changes stick until I reboot. my actual performance loss is unnoticeable so ive kept this setup for a few months now
[One (M7) Original Android Development] Androidian10:
So I flashed 3.12.1 up from 3.11 a while ago and it wiped my phone. Lucky I got a nandroid backup ready.

Any idea why it happened?

I reflashed it again and this time it didn't wipe my phone. Might be a isolated case...
[One (M7) Original Android Development] MartinS13X:
Could it be possible you checked the "wipe-option" by accident?
[One (M7) Original Android Development] donmarkoni:
I can assure you it wasn't kernel's fault. There is not a remote possibility for it to wipe system. Probably it wasn't even wiped, just stuck, or in a bootloop.

There is no "wipe-option" in kernel installation. There is no point for it to exist.
[One (M7) Original Android Development] nightwind84:
sorry but what is fsynch? :)
[One (M7) Original Android Development] anarchychris:
http://xdaforums.com/showthread.php?p=33333127
[One (M7) Original Android Development] nosferatu997:
https://www.google.com/search?hl=pl...c.1.27.mobile-gws-serp..5.11.2047.CjIUVBGfeLY
[One (M7) Original Android Development] nightwind84:
so you might turn it off or leave it on?
[One (M7) Original Android Development] anarchychris:
I leave it on but it's up to you.
[One (M7) Original Android Development] superbellefleche:
Sorry for my noobness but I can't understand what you mean by "simply comment these three lines in build.prop". Does "comment" mean to add a "#" at the beginning of each line? Thanks for your answer
[One (M7) Original Android Development] poondog:
Leaving it on is stock and safe

Turning it off will give you marginally better performance and battery (we're talking about 30 seconds worth of battery) it will boost your benchmarks, but at the cost of if your phone decides to crap itself and hot reboot, your data could be lost as it is not "synced" or accounted for constantly. This data could corrupt your rom install or be as simple as losing game data or account data or something.

I'd keep it on

---------- Post added at 10:18 PM ---------- Previous post was at 10:17 PM ----------

Yes. Makes them not do anything
[One (M7) Original Android Development] flar2:
I don't think I can add 400 MHz step without reworking the gpu driver quite a bit. There are only three levels available. Can't do it on the fly either, because the 400 step uses different pll and dividers than the overclock frequencies.
[One (M7) Original Android Development] hamdir:
How about 410 or even 405?
[One (M7) Original Android Development] flar2:
This I can do
[One (M7) Original Android Development] jeryx:
Thanks you're the man... I'm curious about your new magic... Keep it up mate!

Gesendet von meinem HTC One mit Tapatalk 4
[One (M7) Original Android Development] hamdir:
This is what I meant :) awesome
[One (M7) Original Android Development] Wafflez_SE:
Try fastboot erase cache.

Skickat från min HTC One med Tapatalk 4
[One (M7) Original Android Development] dente01:
Great job [MENTION=4684315]flar2[/MENTION]

Enviado desde mi HTC One usando Tapatalk 2
[One (M7) Original Android Development] kosique:
Hi all,

I feel like 3.12.1 is using more battery on ARHD 13.3 (4.2.2) while idle. Upgrades from 3.11 yesterday with the exact settings but battery use is actually doubled while idle. Anyone has this as well?

Thanks,

Marc