yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] flar2:
Is there some way for me to replicate the stutter you guys are talking about? For example, what app, or what conditions are showing the stutter.

I want to get at the root cause, rather than brute force it with the governor. Can someone who sees this stutter try out this boot.img. It's exactly like version 2.4 except I used a different toolchain and compile options. Just want to see if anyone notices a difference.

http://goo.im/devs/flar2/One/boot.img

You can test it temporarily by rebooting to bootloader and typing:

fastboot boot boot.img

The next reboot will return to your previously installed kernel.
[One (M7) Original Android Development] cee43ja1:
That's how mine is, which would mean pocket detection is working for us.
[One (M7) Original Android Development] c5satellite2:
I had to stop using pocket detection because it wouldn't wake up if it was too dark unless I used the power button. Otherwise it worked.
[One (M7) Original Android Development] flar2:
Don't bother with this one, I don't think out helps. I'll have another one to try later.
[One (M7) Original Android Development] Tabtoub:
Yes the phone didn't even boot, it stuck on splash screen

This is what I did :

did a fresh install of the rom

rebooted

flashed ElementalX 3.4

rebooted

wiped cache and dalvik

rebooted into bootloader and flashed this boot.img

rebooted to system, but it get stuck in splash screen

PS: I have those mico lags only with ElementalX and Tbalden's kernel performance edition, don't have any lag with Bulletproof or tbalden's kernel stable ed, or with any other stock kernel.. I tried all the possible configurations in trickster but no luck, that's why I stick with bulletproof
[One (M7) Original Android Development] flar2:
Just do fastboot boot boot.img, nothing fancy. Just keep your existing elementalx installation so you have all the right modules, etc.

This is the one I want you guys to test:

http://goo.im/devs/flar2/One/boot.img

(same link, but different file)
[One (M7) Original Android Development] jlevy73:
Give me a few minutes and I will test it.

---------- Post added at 04:44 AM ---------- Previous post was at 04:25 AM ----------

Thanks flar but unfortunately that didn't help the micro-stutters, actually it made it a bit worse.
[One (M7) Original Android Development] flar2:
Okay, here's another one, this will tell me if it's possible to fix it at all:

http://goo.im/devs/flar2/One/boot.img

Same link, new file. Same procedure: fastboot boot boot.img
[One (M7) Original Android Development] jlevy73:
That's perfect, no stutter at all!!
[One (M7) Original Android Development] FangorX:
Edit: never mind.
[One (M7) Original Android Development] flar2:
There's something wrong with your setup. I benchmark with Antutu all the time running 1728 and it's always around 25000.

**********************************************

One more test kernel for the stutter thing:

http://goo.im/devs/flar2/One/boot.img

Again: fastboot boot boot.img
[One (M7) Original Android Development] FangorX:
I'm almost positive it is being caused by either the performance governor or low battery charge. I'm getting normal results after switching my governor back to ondemand. Now to test the kernels...
[One (M7) Original Android Development] flar2:
Compare the one I posted above:

http://goo.im/devs/flar2/One/boot.img

to this one:

http://goo.im/devs/flar2/One/boot2.img

Which one is better?
[One (M7) Original Android Development] Johnny424:
Maybe thermal throttle? I know back in my sgs3 days sometimes bad benchmarks could be attributed to throttling..maybe try with much cooler temps
[One (M7) Original Android Development] skulldreamz:
People say benchmarks are for idiot's and blah blah but this is the smoothest my phone has ever run and I just benched 25706 and I'm on 2.4 so when I run benches that are not as good my phone doesn't run as good in areas and I pay close attention to detail so I'm thumbs up to benchmarks... thanks flar2!

---------- Post added at 02:43 AM ---------- Previous post was at 02:18 AM ----------

Boot2 is the only one that will even run for me. M getting bootloops on boot1.IMG so it defeats the purpose cuz its going back to my normal boot. So boot 2 for me
[One (M7) Original Android Development] FangorX:
OK I'm testing now... fastboot boot just froze the bootloader for some reason but they both boot when flashed.

Boot2 is better. Still a small amount of stuttering but TBH I have never seen a completely stutter-free android device.
[One (M7) Original Android Development] deagleone:
compared to the last two, # 2 feels snapier, but microlags still present compared to stock or Bulletproof (thats why i´m crying for ultra cool thermal control in bulletproof ;) ), its Time to refill your coffee found....
[One (M7) Original Android Development] jlevy73:
#2 is good but still a small amount of micro-stuttering. I tried out bulletproof and that is completely buttery no stutter at all.
[One (M7) Original Android Development] skulldreamz:
Was I suppose to flash them? I was just running fastboot boot boot.img and fastboot boot boot2.img. If you flash it then I thought it would stick after you reboot hence making it take longer and more complicated to test and get back results to flar but I'm a noob, what do I know..lol
[One (M7) Original Android Development] FangorX:
Fastboot boot works fine as long as it boots. I just flashed them because fastboot boot wasn't working for me. It doesn't really matter because it takes less than a minute to enter fastboot and flash another one or the 2.4 boot.img
[One (M7) Original Android Development] skulldreamz:
I don't if the rom has anything to do with the microstuttering or lag people are talking about so u guys n gals r probably wondering what the hell is this dude even testing if he isn't feeling the problem...lol I just wanted to put out my setup for people in case anyone cares. So I just compiled the latest renovate using svn, that's the rom I use or insert coin. Elementalx 2.4 each core oc at 2160, gpu oc at 450, uv to 725 at 384 (not globally), thermal'd to cool, s2w w/ no vibration and I don't enable pocket detection because I have never had my phone s2w by itself in my pocket, bln, l2m and I'm getting awesome battery life considering I'm oc to 2160 because I'm getting into games now, thanks flar

I also use lagfix, don't know if it really helps but I'm not going to stop because why try to fix something thats not broken. Meaning my phone is running awesome and I'm always loving the updates from flar2 because every time there is a update, something improves dramatically it seems to me!
[One (M7) Original Android Development] jlevy73:
the difference between fastboot boot and fastboot flash is that with boot, upon rebooting the kernel will revert to what you had previously. With fastboot flash it's permanent. So fastboot boot is a good way of testing something quickly without having to worry whether it works or not because if it doesn't just reboot and your back to what you had previously.

You probably already knew that, just pointing it our for those that might not know the difference.
[One (M7) Original Android Development] gianton:
Just flashed Bulletproof 3.4 and it does feel smoother than ElementalX 2.4 even OCed.
[One (M7) Original Android Development] redvil:
How can you see it's smoother?bench?
[One (M7) Original Android Development] :
Hi,

"Smoothness" has nothing to do with benchs, you'll see "smoothness" in the general UI (User Interface) like animations, app drawer, scrolling in apps like browser or a file explorer with a long list of files to scroll, settings, etc..., opening / closing apps...

Benchs are only for to measure the "raw power" (?), you can have high scores in benchs with a laggy general UI and vice versa, lower scores in benchs but with a smooth general UI.

:)
[One (M7) Original Android Development] redvil:
Mmmm...i so i have to try bullet..;)
[One (M7) Original Android Development] Teejai80:
Hmm my built in wifi tethering isn't working as well, however, third party apps are fine. Trick droid GE, about to search that thread, don't really think it's kernel based but just wanted to add evidence in case.

---------- Post added at 11:27 AM ---------- Previous post was at 11:17 AM ----------

Edit: wifi tether seems to have issues on Trick droid GE so ignore me. :)
[One (M7) Original Android Development] gianton:
Exactly that
[One (M7) Original Android Development] :
Hi,

;)

We would not have seen in the Nexus 4 forum (or Galaxy Nexus, don't remember exactly)? :D

:)
[One (M7) Original Android Development] gianton:
Hi,

We are getting the same devices, now I recall you name.

Still have the N4 and running great with CM linaro and anarkia76 kernel!
[One (M7) Original Android Development] carlos67:
OK, time to jump ship and try Bulletproof to see what all the fuss is about. I'm looking for butter and not really found it with ElementalX any version.
[One (M7) Original Android Development] flar2:
It's only the last couple versions where I disabled pnpmgr. It'll be fixed tonight.

Plus, there were four or five thousand downloads before any one brought it up, it's not that big a deal.
[One (M7) Original Android Development] threetwentyfizzle:
I tried bulletproof yesterday to see what all the fuss was about, and bulletproof was indeed smooth, but I noticed the same "microlags" as elementalx. To further elaborate, the transition animation of the app drawer will lag slightly if I unlock my device from sleep state, or if the cpu is idling at a low frequency. This would happen on both elemental and bulletproof.

Swiping between homescreens on both kernals would sometimes create a "blurring" effect, it's hard to describe but it feels like the screen is trying to catch up to rendering the transition, don't really consider that a microlag.

And lastly, scrolling in the web browser or some apps such as xda, swipe scrolling fast is smooth as can be, but if you slightly free scroll by flicking the screen up or down, I see the same rendering effect as the homescreen swiping, where the pixels are trying to render behind the scrolling, which kinda looks like a wave ripple. Both elemental and bulletproof experienced this.

None of these issues bother me that much, with that being said, I jumped right back over to elementalx, as I enjoy being able to UV my phone to 750 and run cool thermal throttleing with a slight OC. I've been extremely impressed with elementalx in the past on my Hoxl and won't be jumping ship anytime soon.

(hope these descriptions help flar2)
[One (M7) Original Android Development] jlevy73:
Sorry [MENTION=4684315]flar2[/MENTION] wasn't trying to make a big deal about the micro-lags. People talk so much about the little niggles and forget what great work you are doing. Your work on thermal control is excellent especially for someone like me who enjoys gaming. Both of your kernels are amazing work and really appreciate all the time you put into making these perfect (even with the imperfect source code given to us by HTC).
[One (M7) Original Android Development] carlos67:
Yes +1, I wasn't moaning and hope you didn't see it that way. I will try Bulletproof for rest of the day and tomorrow will try the new ElementalX out or whenever it's ready.

Thanks for all the work Flar2 :good:

p.s. I'm noticing that when setting governor settings like "optimal_freq" it is not sticking. I can't seem to get it to consistently stick. I like to set optimal freq. to 1566000 but it sometimes reverts back to 918000. Same for other tunables within ondemand governor. This seems to happen on both bulletproof and EX. I have it set to "set on boot" with a 35 second delay. Tried MP-Decision on and off and also tried lock frequencies on and off but it still happens. I'm using trickster Mod to make the changes but nothing else on my system eg. Rom toolbox, setCPU etc etc.

I just can't fathom why the tweaks sometimes stick but other times when I go back into trickster mod to check they have reverted back. It's so frustrating.
[One (M7) Original Android Development] hoevito:
I know it's a paid app and all...but I have no such issue with fauxclock, so maybe it's trickster? Try a different control app and see if you get better results...

---------- Post added at 07:21 PM ---------- Previous post was at 07:16 PM ----------

I'm no kernel wiz by any strech, but I have a question for you flar....I know you aren't seeing the "microlags" being reported, but do you know maybe if the sampling rate *could* cause stutters and small lags here and there say if it's set to 90 as opposed to 40...? The default rate after installing elementalx was 90 I think and when I changed it to 40 it did seem to help...just curious...
[One (M7) Original Android Development] Tabtoub:
I'm sure all those micro lags will be fixed when HTC releases 4.2 kernel source code :D

Till then, we are all enjoying the excellent kernels you make Flar :) Thanks a lot bro
[One (M7) Original Android Development] ChronoWerX:
[MENTION=4684315]flar2[/MENTION] what is the difference for elementalx 2.5 and elementalx viper 2.5?

Gesendet von meinem HTC One mit Tapatalk 4 Beta
[One (M7) Original Android Development] FangorX:
[MENTION=4684315]flar2[/MENTION] Is C2 supposed to be disabled in ElementalX? I only see C0 and C3 working, but in Bulletproof C2 works as well.

[MENTION=4928648]threetwentyfizzle[/MENTION]

I notice the same thing with the on demand governor. I think there is some background process that dynamically changes the governor settings based on the state of the phone to improve efficiency. It doesn't happen with intellidemand.
[One (M7) Original Android Development] Thug_4_Life:
None, it's just for convenience

Sent from my HTC One
[One (M7) Original Android Development] carlos67:
Phone seems to run far smoother with MP-Decision turned off (using intellidemand with SIO). I know this means multi cores active but the difference is huge. Totally buttery smooth (on Bulletproof latest). This will prob rape the battery but its nice to see how smooth it becomes. No lags/micro stutters at all! Nada!

Up threshold set to 60. GPU performance Gov 400MHz. -50 Mv UV across the board. Using fauxclock because the settings seem to stick where-as they didn't using tricksterMOD.
[One (M7) Original Android Development] lichti1901:
Love the battery on 2.4.

Good work. ;)

Sent from my HTC ONE running ViperRom
[One (M7) Original Android Development] baste07:
What settings did you apply
[One (M7) Original Android Development] smartanks:
Hi [MENTION=4684315]flar2[/MENTION],

Thanks for this awesome kernel, getting great battery life and performance out of it . With the new version 2.4 the finally there is no touchscreen input during calls , however the capacitive keys are still fully functional . this means whenever i end the call either i am in the multitasking menu or google now when i end the calls. Also i keep getting vibrations during calls as my face hits these keys

Would it be possible for you to create an option where the capacitive keys are also non-responsive when proximity sensor forced screen-off.

Thanks.

---------- Post added at 01:49 AM ---------- Previous post was at 01:28 AM ----------

Well i guess the threshold is set to 90 for having a better battery life. I somehow see my battery percentage ticking in front of my eyes when i reduce the threshold to either 40 or 60. sort of like 4-6% in an hour :S
[One (M7) Original Android Development] FangorX:
Lol smartanks you must have a big head. I can't hit the buttons with my face even if I try. I never even had a problem before the proximity issue was fixed, because I try to keep the screen from touching my face anyway. Keeps the grease down.
[One (M7) Original Android Development] azrael97c:
Hi, has anyone noticed if wifi is draining more battery than normal?

this is on ARHD 9.4, elementalx (forgot if this was 1.0 or 1.1), 1.29 firmware, and 4A.14.3250.13 radio

this is on ARHD 12, elementalx 2.4, and 2.24 firmware, and 4A.17.3250.14 radio

wifi is always on. although this may not be kernel related at all, i'm just putting the question out there.

thanks,
[One (M7) Original Android Development] c5satellite2:
HDR is crashing again for me. ARHD 10.3. ElementalX 2.4, 1.5 GHZ, stock voltage, no GPU OC, s2w, nothing else. First few times it crashed, then it worked, now back to crashing camera.

Edit: works fine if the shot is well lit, crashes in very low light shots.
[One (M7) Original Android Development] flar2:
Microstutter: I spent all night and day testing different kernels , flicking my screen trying to get it to stutter. I found that re-enabling pnpmgr improved the smoothness (means you can't lock frequencies on all cores) Other than that, there are many tradeoffs in a kernel. It's possible that some of the powersaving tweaks I've enabled cause a bit of stutter, but I tried without them and it didn't seem to make a difference. Another culprit could be the thermal management, which also messes with frequencies, but I doubt it. HTC changed the mpdecision daemon, but it's a binary blob so I don't know what they did.

If you are looking for it, you can get any kernel to stutter because there are so many things (i/o, a background process, network, etc.) that can cause a stutter. I think the smoothness in this version is acceptable.

Ondemand governor settings: If you've tried some of the governor tweaks posted in the thread, you'll notice that the values change. This is because the system adjust the values (not the kernel).

Sweep2wake/pocket_detection/proximity weird scenarios: the last few of these mentioned in the thread are fixed.

I also fixed up the menubar scripts, and add a fastcharge option

I switched to a new toolchain, linaro 4.8, so this needs more testing before I consider it stable.

Download:

ElementalX-m7-2.6 *BETA*

Changes:

-use linaro 4.8 toolchain

-fix capacitive buttons sometimes still active while screen off

-fix multiple qemu.hw.mainkeys entries in build.prop

-add fastcharge option

-re-enable pnpmgr
[One (M7) Original Android Development] flar2:
Can't do much about camera stuff, the drivers are way too complicated and totally undocumented. That's what I hate about smartphone/tablet hardware, everything is specially coded for each device. Not like PC's where there are lots of standard drivers.
[One (M7) Original Android Development] Rumball:
Do you have auto-flash enabled? My camera hangs on this kernel if I have HDR and auto-flash in low light conditions. HDR works fine in low light if I turn off the flash.
[One (M7) Original Android Development] lichti1901:
TCP Veno, read agrar 2048, sheduler fiops, 384/1728, ondemand, UV -25, hotplug cool :D

Sent from my HTC ONE running ViperRom
[One (M7) Original Android Development] randykzc:
my hdr crashes in low light with my flash off..hdr works fine if its well lit area..
[One (M7) Original Android Development] evilmastr:
I have no idea what you are doing but it's working. I've always underclocked my CPU with your kernel and with each version it seems to go faster and faster. Haha! Good work!

One thing I have noticed on versions past 2.2 is that the phone bootloops (goes to splash and then reboots) once after installation. Is this supposed to happen? Not a big deal since it works after all. :)

T9'd from my black HTC One M7
[One (M7) Original Android Development] flar2:
Are you s on?
[One (M7) Original Android Development] poondog:
Mine does too lol I am new to the One

Also is everyones GPU speed being set properly from AROMA? Mine says 200MHz max in trickster and I set 450 in aroma. Maybe I did something wrong in the installer or something

Linaro 4.8 build working well so far apart from the GPU problem I have :)
[One (M7) Original Android Development] evilmastr:
No, I'm S-OFF.

I think my hboot version is 1.54 something, if that helps. Unlocked.

T9'd from my black HTC One M7

---------- Post added at 06:30 AM ---------- Previous post was at 06:29 AM ----------

Trickster seems to lose it's settings after install. Change it manually and set it to launch on boot and everything is fine.

T9'd from my black HTC One M7
[One (M7) Original Android Development] poondog:
Not that, I did not set anything in trickster. I am saying that maybe something I did in aroma made it

Never mind must be something I did cause the 99elementalx init.d script seems to be showing 450

Thanks anyway :)
[One (M7) Original Android Development] flar2:
For some reason the init script is not setting it. You have to change it manually for now.

That's why 2.6 is still beta
[One (M7) Original Android Development] poondog:
Ah okay, thanks for the reply

Everything else is good so far for me :)
[One (M7) Original Android Development] c5satellite2:
No auto flash here. Another user reported it as well in viper Rom thread a few hours ago. Stock kernel does not crash HDR in low light.

Current workaround for HDR crashing camera: Don't take HDR shots in low light!

Everything else is great here with 2.4, battery and speed are both sweet, just wanted Flar to know about this. Thanks again Flar, top notch work.
[One (M7) Original Android Development] dryspuri:
[MENTION=4684315]flar2[/MENTION], great Job with this, I am runing elementalx on my GE edition, will you please suggest how to get back to stock kernel, or point me to thread, again many thanks with great job.
[One (M7) Original Android Development] kazemitsui:
reflashing the rom is the easiest way to get back to stock kernel
[One (M7) Original Android Development] c5satellite2:
Delete
[One (M7) Original Android Development] wmg316:
2.6 is a winner for me. Least amount of "stutter" I've had yet on ElementalX!
[One (M7) Original Android Development] smartanks:
Hi [MENTION=4684315]flar2[/MENTION],

2.6 performing very nicely. Here is something to keep you motivated :)

Confirmation number: 9Y4480600J7727336
[One (M7) Original Android Development] bluegizmo83:
Is there going to be anymore work done on your Sense 5 Android 4.1.2 kernel?
[One (M7) Original Android Development] smartanks:
This happened to me as well. Bootlooped twice , but after that booted up fine. Currently working really smooth, almost butter. However i am S-On , i think this might be related to the new hboot which is common between me an [MENTION=2135799]evilmastr[/MENTION]

Edit : Capacitive button dont work during calls now :good::good::good::good:
[One (M7) Original Android Development] FangorX:
I'm sure flar2 has better things to do with his time than work on a kernel almost nobody would use... Why would anyone want to stay on 4.1.2 if their bootloader is unlocked?

2.6 is running really well so far! I actually get a little excited every time flar2 releases an update haha
[One (M7) Original Android Development] cee43ja1:
Nope. Still on original 1.44 HBOOT and S-OFF and it reboots twice. But once it actually boots, all is well.

2.6 seems a tad smoother. Flipping through Blinkfeed at 1.2ghz is still smooth.
[One (M7) Original Android Development] tyyau:
Wow, 2.6 is great.....
[One (M7) Original Android Development] mikbe:
I have a strange problem. After I press call screen immediately switches off and wakes only by pressing power button. In other case it doesn't switch off at all and my face does funny things with my phone. It's like it stopped using proximity sensor completely.

Pocket is enabled, S2W disabled, DT2W enabled, L2W disabled, L2M enabled

I'm on IC 3.0.4 and ElementalX 2.4

Anyone else with similar issues? Gonna try with 2.6 for starters and provide logcats if that's not helping.

SOLUTION:

NiLS widget broke it. Auto wake setting to be exact.
[One (M7) Original Android Development] jerrylzy:
Hi, flar2!

Everything seems to be working in 2.6 beta :D

EDIT: pnpmgr does not seem to work, for I can still adjust and stick the frequency.
[One (M7) Original Android Development] FangorX:
I was trying to figure out why power saver wouldn't reduce the CPU frequency.