yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] Sneakyghost:
Is that a known and common issue? Sorry I am following the thread only partially. I feel really guilty :D

I haven't ever thought about linking the overheating to low voltages.

mobile post
[One (M7) Original Android Development] DeSaint2:
Well some say it stresses the cpu to work harder due to it trying to pull more juice but obviously since it is limited it can't and thus is overworked. I have a pvs 4 and while I can safely uv -75 across the board without reboots I didn't notice any less heating or any more battery time.
[One (M7) Original Android Development] Pointlol:
I'm pretty sure it doesn't work like that lol.
[One (M7) Original Android Development] Bluewall:
Even if the CPU doesn't shut down the device due to low voltage, the CPU may make more mistake and have to work harder when Undervolted. It's hard to tell but some personal test help

Envoyé depuis mon HTC One en utilisant Tapatalk 4 Beta
[One (M7) Original Android Development] godfirst:
Just like the other two stated, not only can over undervolting cause the phone run hotter faster and inefficient, but it can cause your phone to freeze and reboot. I would raise the voltage!:good:
[One (M7) Original Android Development] flar2:
I would check to see if you have any apps running wild. This phone will definitely heat up fast if all cores are running.

My temps in normal use are around 40C. Ambient temps here have been about 75 to 90 Fahrenheit
[One (M7) Original Android Development] FangorX:
Download "OS Monitor" and check your running processes. It should idle around 1-2% CPU usage. Also make sure only one core is active and at 384MHz when idle. There's been a few times where my CPU got stuck with all four cores on, or a bad process was hogging the CPU.
[One (M7) Original Android Development] Sneakyghost:
One core seems to be up full all the time and only seldom drop out. Load keeps around 25-30 percent.

Only happens on this kernel. Gotta check it out more.

mobile post
[One (M7) Original Android Development] DSC05:
You're on Viper I guess. Me too and very often after I install a new kernel there is weird interaction with venom tweaks. Take a look into the tweaks cpu tab if the minium cpu is really set to 384.
[One (M7) Original Android Development] flar2:
The kernel itself won't cause much cpu usage, apps or the system will cause it.
[One (M7) Original Android Development] FangorX:
I had that exact problem on my N7 - it got really hot and lost 1% per minute after flashing a new kernel. Turns out Google Backup Transport was keeping the CPU at max speed. I fixed it by force closing and disabling it in settings. When I re-enabled it later it worked properly again. Also make sure the min clock speed really is set to 384 haha.

[MENTION=4684315]flar2[/MENTION] - I've noticed that on 2.4 the framerate is more choppy when playing 3D games compared to 2.2. I am using the same ROM and settings - ViperOne, Intellidemand, Stock voltage, 400MHz GPU and 1.2GHz CPU to reduce heat. Using 1.7GHz helps but it still seems choppier than 2.2. Other than that the kernel is super smooth and stable. Were any GPU settings changed in 2.4?
[One (M7) Original Android Development] tiny4579:
Yes. Check the changelog.
[One (M7) Original Android Development] Sneakyghost:
Thanks for the input guys! Now i used up all my legit Thanks in one thread haha!

Much appreciated. I bet i just have a screwed system as i mess too much with viper for the guys over there testing my phone to death but hell yeah, everyone else seems to have a brilliant time with this kernel so i will look into it when i am not as tired anymore. Thanks again dudes.

PS: everything else on 2.4 seems to work pretty damn solid. Even the Fastcharge is now working as it should for me. Had ample opportunity to test it at work and in the car today as the battery kept going down all the time producing heat :D haha.
[One (M7) Original Android Development] langer hans:
A friend of mine just had this problem where the phone will reboot when you hit install. Turns out that turning "Fast Boot" off in Settings->Power fixed the flashing process for him. Just leaving this info here.
[One (M7) Original Android Development] kosique:
Delete.
[One (M7) Original Android Development] wmg316:
[MENTION=4684315]flar2[/MENTION].

The fix for the problem with starting different apps during call appears to be working great now!

I have another question....I saw that you installed ViperOne recently.

On ViperOne, I have a minor problem during calls.

I can start a call in the house in normal room light. If I go outside into full sun light, and take the phone away from my ear, the screen comes on as it should...I return to my ear, and the screen goes off as it should. But if I move back into the house with normal room light during this same call, and take the phone away from my ear, the screen stays "off". I then have to press the power button to have the screen turn on when taking the phone away from my ear...and press the power button again to have the screen turn off when returning the phone to my ear.

I was wondering if you could test that issue if you are still on ViperOne.

Do you think that would be a kernel issue? ROM issue? Or just my phone!!??

Thanks!
[One (M7) Original Android Development] wzu7:
can someone make screenshoot about > software > kernel parts ...(what text said there !!) ..thanks
[One (M7) Original Android Development] Sneakyghost:
This?

mobile post
[One (M7) Original Android Development] flar2:
I tried but could not replicate that.

Version 2.4 should say:

aaron@bella #24

version 2.3 would say: aaron@bella #23, etc...
[One (M7) Original Android Development] wzu7:
[MENTION=1102297]Sneakyghost[/MENTION], [MENTION=4684315]flar2[/MENTION] ...thanks
[One (M7) Original Android Development] meduza01:
I've Installed the Flar2 release and you were right it runs much smoother, but S2W and S2S still did not work. Then after installing trickster mod found the option to enable the S2W and S2S now it works perfectly even without setting GPU to performance. Thanks for advice.:good:
[One (M7) Original Android Development] lbell:
I have installed ElementalX 2.4 but it is still charged slowly by USB. How to toggle fast charge on?
[One (M7) Original Android Development] boss336:
Flar I'm on bulletproof latest version running awesome what's the difference between bulletproof and elemental
[One (M7) Original Android Development] Hussainally:
Thanks flar 2.4 battery life is crazy good
[One (M7) Original Android Development] lbell:
Haha. I just leave the CPU frequency stock. Is it much hotter or consume much more power when OC to 1850?

'

'
[One (M7) Original Android Development] poondog:
Toggle it on in an app like trickstermod

You can test by trying to access storage from the computer you're charging it from. Fastcharge will disable phone storage mounting thing :)
[One (M7) Original Android Development] boss336:
Is elemental better than bulletproof and should I choose cool for thermal
[One (M7) Original Android Development] Hussainally:
Try it
[One (M7) Original Android Development] DeSaint2:
If I remember correctly the settings cause thermal throttling at different temps. Cooler = throttling at a lower temp and vice versa
[One (M7) Original Android Development] jerrylzy:
First, there is no 1850, only 1836 & 1890. Second, I undervolted 100mv. At 1890 mhz the voltage is 1050mv, and I haven't experienced much heat till now.
[One (M7) Original Android Development] boss336:
So what's the best option stock cool or more cool
[One (M7) Original Android Development] jerrylzy:
If you need less performance and cooler body, then choose extra cool.

If you want a balance between phone's body temperature and peformance, choose stock.

If you want high performance, then choose hot.
[One (M7) Original Android Development] gianton:
What PVS is your chip? Is it stable at -100mV?
[One (M7) Original Android Development] jerrylzy:
PVS 4, stable
[One (M7) Original Android Development] mustbevick:
Wow

Super impressed with how fast the Aroma Installer is... props...

my fav kernel thus far

THANK YOU :D
[One (M7) Original Android Development] ArmedandDangerous:
Anyone having issues with WiFi-Hotspot? Doesn't seem to work anymore >.<
[One (M7) Original Android Development] goulies:
Random question :Will it ever be possible to undervolt the gpu for less heat?
[One (M7) Original Android Development] __:
WiFi-Hotspot

I am experiencing the same here, but did not think, it could be the kernel!

Now, that you are mentioning this, I realized: It could be the kernel.

[MENTION=4684315]flar2[/MENTION]

Would you please check this issue?;)

Thank you again and again for your great work.
[One (M7) Original Android Development] gianton:
Working fine here, with ARHD 12.0 and EX 2.4
[One (M7) Original Android Development] ArmedandDangerous:
I'm on ARHD 12.0 and EX 2.4 as well, but when I turn WiFi-hotspot on, it turns on normally but other devices cannot successfully connect to it. It will either get stuck at "Getting IP", or "Verifying", and then it will say "Avoided bad connection" or something like that then it will just fail.
[One (M7) Original Android Development] gianton:
No such issue here, 2 devices connected fine my N4 and my laptop with W7.
[One (M7) Original Android Development] godfirst:
All I have to say is, elemental 2.4 is sooooo fast. :D:cool:

Sent from my HTC One using Xparent Red Tapatalk 2
[One (M7) Original Android Development] mwilky:
Hey mate, great work as always! Just noticed that if you start to overclock you get a few stutters here and there, scrolling in home screens etc, maybe something for you to look into! I set it back to 1.7 and all seems fine

Cheers!
[One (M7) Original Android Development] Nekromantik:
Sad to say but proximty fix not working on viper. Still on old base so nothing fixes that bug.
[One (M7) Original Android Development] gianton:
At 384/1890MHz with -50mV UV I have no stutters or lag running ARHD 12.
[One (M7) Original Android Development] carlos67:
Hey man this is interesting. I run OC'ed to 1.89 GHz and have occasional micro stutters. But surely it's counter-intuitive that a lower CPU speed means a smoother UI. It can't be like that, can it?

p.s. Manchester lad too!
[One (M7) Original Android Development] gianton:
Try these steps guys and see if lag/stutters gone.

1. Settings/Developer options/Advanced/Animation set all three to 0.5x

2. Download lagfix app and check all three partitions, tap on run and reboot.

Credit to baadnewz for the above.
[One (M7) Original Android Development] randykzc:
just a quick question..how to "Advanced users can apply settings on the fly by running /etc/init.d/99elementalx as root." ???
[One (M7) Original Android Development] poondog:
Either reboot to run the script (init.d scripts are run at boot if done right)

Or run it with an app like script manager
[One (M7) Original Android Development] semool:
Lagfix is Not needed with this Kernel. The Kernel itself Run trimfs at every Boot.

Gesendet von meinem HTC One mit Tapatalk 4 Beta
[One (M7) Original Android Development] poondog:
Really? Pretty cool :)

[MENTION=4684315]flar2[/MENTION] is it possible that you lower the minimum battery percantage where the flashlight still works?

I think it's in one of the board-m7 files in arch/arm/mach-msm

Used to be called low_cap_limit or something

Thanks :)
[One (M7) Original Android Development] flar2:
WiFi hotspot works for me. Try clearing cache

What proximity issue are you talking about? I've never had any proximity issues. The fix in the latest version was for digitizer not turning off all the way during calls. Proximity has always worked for me.

This device is finely tuned. I've tried all kinds of tweaking of bus bandwidth, l2 cache, gpu crews, etc, and changing from stock usually results in worse performance. I run 1728 or 1836 and have no lag or stutter.
[One (M7) Original Android Development] jlevy73:
Always a fan of [MENTION=298610]Flar[/MENTION]'s work, excellent developer with excellent support.

I'm running the latest and greatest with InsertCoin Rom @ 1736 stock voltage with GPU @ 450 and am seeing quite a bit of micro-stuttering when scrolling through the homescreen. Tried all different combinations of governors and I/O and have not been able to resolve it. I had the same issue with IC and EX 2.2 so I'm thinking it might be something in the Rom causing the conflict. Very strange because the benchmarks for example, 3DMark are through the roof (as is GFXBench).
[One (M7) Original Android Development] flar2:
TRy bulletproof
[One (M7) Original Android Development] jlevy73:
Good idea, thanks.
[One (M7) Original Android Development] Pointlol:
Seeing as you're online now, bumping this old post (only this once, I promise). Tried to see if it was any different with 2.4, but it hasn't changed sadly. An easy to see example is Subway surf, it's not very demanding which results into the CPU being too conservative which then leads to inconsistent fps especially as the game speeds up. It used to have 60fps consistently on your 4.1 kernels.
[One (M7) Original Android Development] hoevito:
To all you people complaining about micro stutters/lags, I had them too for awhile until I did this...

in your "tweaking" app of choice (i use fauxclock)...

change the ondemand governor profile to this=

up threshold=40

two phase frequency=- 1242000, 1242000,1242000,1242000 (for all 4 cores)

Sampling rate=50000

optimal frequency=1242000

sync frequency=1242000

Basically I found that the "stutters" you all are referring to go away once the sampling rate and up threshold are changed. I have had absolutely no issues since changing these parameters :cool:
[One (M7) Original Android Development] hassan89:
Thanks dude ,that worked :) It is much better now.
[One (M7) Original Android Development] Nekromantik:
Issue is that, the touch screen still registers touches during a call and so brightness turns all the way up.

I think its a base issue, the 2.24 base fixed it people are saying.
[One (M7) Original Android Development] jlevy73:
Correct, if you updated the firmware you shouldn't have the issue anymore. HTC included new touch drivers that resolved that annoying problem.

---------- Post added at 05:54 PM ---------- Previous post was at 05:53 PM ----------

Nice, that definitely did help. Micro-stutter isn't completely gone but significantly reduced. Thanks for the tip.
[One (M7) Original Android Development] flar2:
Since Jelly Bean came out, Android will change the sampling rate as needed (it will get changed back even if you try to set it). HTC changed something about ondemand and mpdecision in the 4.2.2 ROMs. One of the reasons 4.2.2 has battery improvements is because it's not ramping up as much. This behaviour is built into the system, not the kernel.

I used Bulletproof for a while and know it's very smooth, but I mostly use ElementalX and I don't experience any microstutter or lack of smoothness that bothers me. I really think that HTC does some serious fine tuning to optimize the stock speeds. Overclocked elementalx will get you higher performance in games and stuff like that.

I will experiment with a few things to see what happens, I have a couple ideas.

No, that's definitely fixed in 2.4 and was due to s2w and dt2w leaving the touch sensor on during calls. It had nothing to do with the proximity sensor or base or firmware.
[One (M7) Original Android Development] Bluewall:
I'm wondering if those improvement in the system about the CPU are part of the GE ROM (which I use :p)

Just made a clean flash of GE and your kernel. Running on-demand and FIOPS.

Interested to have a feedback tomorrow? :)

Envoyé depuis mon HTC One en utilisant Tapatalk 4 Beta
[One (M7) Original Android Development] arhung:
Hi, I want to know do you guys enable the power save mode with this kernel?
[One (M7) Original Android Development] mrwilly:
Power save for the CPU does not work with this kernel
[One (M7) Original Android Development] hoevito:
I noticed that myself...sampling rate does jump around a bit, but I think maybe the "up threshold" has a lot to do with these so called "microstutters" people are experiencing maybe...because there was a definitive improvement in smoothness and performance after changing it. To be honest, I've noticed small lags and stutters on every custom kernel I've ever tried on the One, from faux to teamseven, yours, etc. so that led me to believe it's more of a governor issue than anything. I read around a little bit in various threads and noticed faux had a recommended profile/setup for the ondemand governor which included a modified up threshold and sampling rate, so I experimented by applying those parameters with your kernel and they smoothed out things immensely while using ondemand. The sync frequency/optimal frequency stuff I applied at 1242mhz since my voltages for 1134 and 1242 are the same and run perfectly fine. I figured the slight speed bump would help since the phone spends a lot of time on those frequencies....
[One (M7) Original Android Development] baadnewz:
if you have some time please test this fix.
[One (M7) Original Android Development] mwilky:
I know it's weird I can't get my head around it, maybe depends on our speed binbor something but bulletproof seems smoother than elemntal at 1.7.

If you need any logs let me know
[One (M7) Original Android Development] jerrycoffman45:
for me the brightness turns all the way down after a call
[One (M7) Original Android Development] cee43ja1:
I never updated the firmware when I flashed the stock rooted deodexed 2.24.401.1 rom, and ElementalX 2.4 fixed the in-call problem. Whatever firmware was on 1.26.502.10 is still on my phone.
[One (M7) Original Android Development] __:
Good evening flar2,

sorry for disturbing again.

Please try the following (please read it twice before trying):

Wake the device, cover the proximity sensor, make the device sleep.

Please keep the sensor still covered while swipeing twice the touch buttons from left to right.

Does your device wake although the sensor is covered?

Mine does!

Would you have a look please? ;)

By the way: I am using S2W, pocket detection and L2M.

please keep this great work going :thumbup:

Thanks in advance
[One (M7) Original Android Development] jlevy73:
Thanks Baad, I tried out your fix and noticed significant improvement. When I couple this with changing the up threshold and sampling rate, the micro-stutters are almost nearly gone.
[One (M7) Original Android Development] cee43ja1:
-power button/s2w to turn on screen

-cover sensors

-power button/s2w to turn off screen

-s2w with sensors covered

Does not wake up. Using pocket detection, s2w, l2m.
[One (M7) Original Android Development] iElvis:
This is interesting. As long as I keep the sensors covered the entire time, swiping twice will wake it up.

But if I sleep the phone, then cover the sensor, it stays asleep.

I suspect the phone is taking the last reading on the sensor as ambient, so if it's zero, there's no difference when it's asleep and in a pocket.
[One (M7) Original Android Development] cee43ja1:
Are you letting the screen turn off on its own, or hitting the power button/s2w to turn off the screen? I just let the screen shut off right now with the sensors covered, and doing s2w twice does nothing.

Could it be the 2.24 firmware? I never flashed it, so I'm on whatever 1.26.502.10 has.
[One (M7) Original Android Development] Nekromantik:
I have never enabled any of the wake features.

I also had the issue in stock kernel. If I flash back to a pre 4.2.2 ROM my phone works fine. I have yet to try a 4.2.2 2.24 ROM however. Viper not updated the base from 2.17.
[One (M7) Original Android Development] Sneakyghost:
I can confirm with identical settings regarding s2w, L2M and pocket detection the device wakes up on second swipe.

mobile post
[One (M7) Original Android Development] hoevito:
I flashed this fix as well... It definitely helped. Whatever you did should be posted and stickied somewhere :)
[One (M7) Original Android Development] DeSaint2:
Huh, your own personal settings for I'm assuming on-demand governor with some additional minfree settings. I don't suffer from the lags and stutters others report but it's looking like you did a good job from all the good reports. Keep it up man.
[One (M7) Original Android Development] wmg316:
Not the firmware. I have 2.24....followed the instructions in that post...letting it go to sleep naturally, and letting it go to sleep by pressing power button. Tried to wake the device in both instances with the swipes mentioned, and it did not wake up...stayed asleep. Removed finger from proximity, swiped, and phone woke up. Seems to be working as it should for me.
[One (M7) Original Android Development] tfriedrich_:
I have logo2menu enabled and it works. However, I still have the on screen menu button showing up.
[One (M7) Original Android Development] kivine:
Use a rom that supports the removal of 3 dot menu or install a mod
[One (M7) Original Android Development] jlevy73:
I hope HTC released the earpiece code because one of things I've noticed is that volume from the external speakers with custom kernels greatly reduces the volume through the external speakers. Actually, I'm not sure if that workaround is the root cause but it's a likely culprit.
[One (M7) Original Android Development] jsbutran:
+1. Even I am experiencing the same. On stock kernel it was perfect. Would like to go back to stock. Could you kindly provide link to flash able zip of STOCK KERNEL. I am on latest base.
[One (M7) Original Android Development] jlevy73:
It's in the 2nd or 3rd post of renovate rom. You can flash the kernel and it will give stock kernel for .13
[One (M7) Original Android Development] flar2:
I should have a new version up by the end of the week. I added some patches from code aurora and the new source from HTC (no camera stuff unfortunately) This thing uses practically no power when idle, my battery was still at 100% this morning. There'll be a few other things too.

EDIT: upon close inspection, I think it might fix the camera. I'll have to test it out.
[One (M7) Original Android Development] jlevy73:
Did they update the earpiece code by chance?
[One (M7) Original Android Development] flar2:
Nope
[One (M7) Original Android Development] ramon.nmgn:
Does elenantalx improves the battery?
[One (M7) Original Android Development] flar2:
It does for me
[One (M7) Original Android Development] jlevy73:
Cuz your using v0.5 :D
[One (M7) Original Android Development] paranoid2007:
Really great kernel. I've been using it all week now without any hickups. Running undervolt of 700 mV on lowest frequency and 800 mv up to 900 Mhz. Please keep up the good work! :o
[One (M7) Original Android Development] kzakaria:
+1000000000
[One (M7) Original Android Development] monkboy24:
Hey flar what are u overclocked to?
[One (M7) Original Android Development] flar2:
Mine's not a good overclocker :crying: I've been running 1890 on the first core, 1728 on the rest. Seems to work well. There's not much need to ramp it up too much, you pay the price by running hot.

I'm still adding a 2160 step to the next version though :D
[One (M7) Original Android Development] mwilky:
Maybe you could look at adding a lower minimum frequency matey? :p
[One (M7) Original Android Development] ramon.nmgn:
Wow sorry for asking, But can i install this kernel and dont do anything Myself with overclocking?

I mean, is it good too use the defaults this kernel gets installed with?
[One (M7) Original Android Development] ratchetjaw:
Was just wondering this too
[One (M7) Original Android Development] ramon.nmgn:
Hehe im kinda new too Android and just want an improved battery life and logo wakeup hihi
[One (M7) Original Android Development] tfriedrich_:
Yes. I believe the lowest clock speed by default is undervolted by just installing the kernel which will lead to better battery.