yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] Luisit0:
Thing is, with stock kernel on my current Rom and firmware, I don't have the issue... I haven't tried tbalden's kernel on the new firmware, but I guess I'll flash it tomorrow and test it out aswell.

---------- Post added at 11:13 PM ---------- Previous post was at 11:02 PM ----------

Did it happen all the on ur phone? Or was it randomly? Cause as I just edited my prev post, it only happens sometimes, though pretty often... Maybe twice a day.

-H7C 0N3
[One (M7) Original Android Development] wmg316:
Yes. I could reproduce the issue 100% of the time on my Dev Edition. I have not experienced the issue on my AT&T version of the One. I did not update firmware on AT&T version either...
[One (M7) Original Android Development] cee43ja1:
After running 3.3 for a day, I think I have to go back to 3.2. The S2W fixes seems like it made my phone less responsive to S2W. I feel like I had a wider sweep area in 3.2, and I can repeatedly S2W/S2S with no problems, sometimes even activating screenshots.

If the older S2W was paired with the new tweaks/fixes in 3.3, I think it would be a solid kernel.
[One (M7) Original Android Development] wmg316:
Upon first install of 3.3, my S2W barely worked...specifically after a period of being in sleep state. I reinstalled, and all was ok after the 2nd install. Might give that a try before reverting back...
[One (M7) Original Android Development] iElvis:
The only issue I'm having is that I don't seem to need to plug my phone in anymore.
[One (M7) Original Android Development] flar2:
If you set /sys/android_touch/button_timeout to 0 it will be the same as in 3.2.

This will also prevent accidentally sleeping with a quick doubletap of home. I thought I set it low enough, it's really hard for me to double tap it to sleep. My normal double taps to activate the recent apps dialog never make it sleep.

The last couple version have also had a timeout that prevents repeated sleeping/waking. That means you can't just sweep back and forth to turn it off and on. You have to wait about 0.8 seconds between each sleep or wake.

I put a lot of limits on sweep2wake because people were still having problems with accidental wakes and screenshots.
[One (M7) Original Android Development] runganwt:
WoW! amazing use, How can you use your phone for 2 days with minimum screen on time...:D:p:D

I only use my phone to watch porn, it took me a lot of screen on time....(just kidding)

This is the best custom kernel still :good::good::good:
[One (M7) Original Android Development] iElvis:
In truth, that's probably a best case scenario. I haven't used my phone all that much the last two days, just some texting, email and minor apps. I left the house only twice for about an hour total, the rest of the time it was on wifi. Still, I've noticed a real improvement since moving to 3.x.
[One (M7) Original Android Development] runganwt:
How did you config your kernel? Any UV or what Governor are you used? I would love to have the same experiences. :good:
[One (M7) Original Android Development] cee43ja1:
Don't feel any difference after a reflash. But I do need to stay on a kernel for more than a day since I'm still trying to get a good reading from the battery and need to do more testing between intellidemand and ondemand CPU governors.

Is there anyway to make it permanently 0? After rebooting, it resets back to 6.
[One (M7) Original Android Development] baadnewz:
happens to me too, only way to turn up the display si to press the power button. firmware is 2.24 one, with stock kernel doesn't happen.

truth to be told with stock you might end up ending the call with your ear if you don't keep the phone press enough
[One (M7) Original Android Development] kazemitsui:
well i seem to be in the complete opposite of you guys since 3.3...

I dont remember what version I was on previously maybe 2.7 or something...

But now with 3.2 or 3.3 I can barely have 80% remaining from 820am to 1pm. and with super light usage during that time. just whatsapp occasionally and music on the way to work which is about a 40min ride.

Before I could listen to music for like i said 40 minutes. and occasional Whatsapp msg and still be at around the 90-91% range from around 820 to 1pm (lunch time) ahha

now after typing this, I just remembered I changed radio to 4A.17.3250.14. Could changing radio affect my battery that much?

also this is all on 3G from say 820-9am then wifi at the office.
[One (M7) Original Android Development] Luisit0:
I'll admit battery life is insanely good, muuuuuch better than stock for me! Even with OC cpu and gpu, my only issue is with proximity and it's only sometimes, so I'll try getting a logcat of it and maybe wait out 'till I can replicate it manually myself... In any case, I still got 'till August 6 to get an exchange, since this unit is a warranty exchange too... Wow, now that I realize it, I can't believe it's been almost 90 days with my One :eek:

-H7C 0N3
[One (M7) Original Android Development] flar2:
I'll add it to the installer next version.

Yes. Radio probably makes the biggest difference of anything if you're on mobile data for any length of time. You should go back to your previous radio. I've never flashed a radio on any of my phones because it usually does more harm than good. There is no reason to change it unless you are having specific problems.

adb logcat > logcat.txt

adb shell cat /proc/kmsg > kmsg.txt
[One (M7) Original Android Development] kazemitsui:
alright good thing i kept writing my previous radio all over my work notes... ahha dont ask why. so I just found a flashable zip (makes life easier) and will see that it hopefully restores my old battery life.

Is there a reason why radios can affect battery life so much? I never really followed that. just roms and kernels for me... but even still im quite noobish with those things.
[One (M7) Original Android Development] vomer:
3.3 looking great so far! trying out the new simple GPU
[One (M7) Original Android Development] Luisit0:
I'll do it tomorrow if I get the issue happening again since I don't have a pc right now

-H7C 0N3
[One (M7) Original Android Development] iElvis:
I posted my setup a couple of pages back. Really nothing elaborate.
[One (M7) Original Android Development] lichti1901:
Same for me. But i dont changed the Radio since a few weeks. Same settings as with previous kernels.

batterylife is the half as before with same usage. No wakelocks, same apps installed, same Kernel settings. Dont know, maybe its the temperature, we have +15℃ more outside as 2 weeks before.

Sent from my HTC ONE running ViperRom
[One (M7) Original Android Development] redvil:
How can you have no wakelocks?
[One (M7) Original Android Development] donmarkoni:
No. At least for me. ;)

Have you tried flashing it again? Looks like some modules didn't flash properly.

You could make init.d script until flar2 adds option to new version (echo 0 > /sys/android_touch/button_timeout).

You should really try new radio 4A.17.3250.20 (mirror). :good: I have tried few and returned to original, as it was best for my location. That is, until I tried this new one. ;)
[One (M7) Original Android Development] lolpos:
The new tmobile radio gives me better signal and improved lte speed. Battery drain is good for me
[One (M7) Original Android Development] djbenny1:
Hey flar did you get a chance to look at my recovery log yet?

Thanks
[One (M7) Original Android Development] kazemitsui:
Thanks. I went back to 4A.14.3250.13 which was my previous radio. ill test it out for a day and then test the latest that you just posted on saturday or something...

im just annoyed that I could drop only 10% for the 4-5hrs and now its draining 20% for those same 4-5hrs.... double the drain same usage!

only major changes to my phone was kernel and radio...

-------------

BTW is the radio you posted flashable in recovery or fastboot?
[One (M7) Original Android Development] maverick1103:
Could someone kindly share the 3.2 beta please, I'm running 2.4 and went to download the 3.2 beta after reading all the positive feedback, then came here this morning to find 3.3 beta was out; don't think I'm complaining here lol! I just have read that some people are having some issues with 3.3 beta and I'm going to be busy over the weekend so won't have time to spend much time on XDA etc.

It would be greatly appreciated if someone could share it, thanks :)
[One (M7) Original Android Development] kazemitsui:
search son

http://xdaforums.com/showpost.php?p=43825627&postcount=2857
[One (M7) Original Android Development] maverick1103:
Thanks, I did search using the app and couldn't find anything! Oh and I'm not your son! :D
[One (M7) Original Android Development] lichti1901:
No wakelocks what drains the battery higher than normal.

And pls dont post unuseful comments which doesnt help anyone. ;)

Sent from my HTC ONE running ViperRom
[One (M7) Original Android Development] Huubs:
In aroma i've disabled the sweep and logo things, kernel-settings like governor etc. are untouched.
[One (M7) Original Android Development] vanu:
hi all, just a quick question, i'm on stock kernel with ARHD 12.1, and i'm wondering - is there any point in flashing this kernel if i'm not going to use oc/uv or the different wake methods, is there any real benefit besides that, like performance-wise? Thanks in advance, I don't feel like I need more processing power in any application, but there is always room for improvement, you know. :)
[One (M7) Original Android Development] SleemLDJ:
Wil this kernel work on cm10.1
[One (M7) Original Android Development] donmarkoni:
I could bet my a$$ off it's not kernel, as someone said, there is no kernel here with more satisfied users. :)

---

Flashable. Easier,

no computer needed. ;)

Read the OP again and if you like other features - flash away. :D

BTW, you will see slight increase in performance even w/o OC.

Sent from my HTC One
[One (M7) Original Android Development] alex6600:
If you don't use oc/uv- try other kernel from flar2- http://xdaforums.com/showthread.php?t=2233665
[One (M7) Original Android Development] killman2659:
No.

---------- Post added at 07:21 AM ---------- Previous post was at 07:14 AM ----------

I have never thought about it, but would disabling the sweep2wake/logo2wake/pocket detection things improve battery life?
[One (M7) Original Android Development] popokrew:
I have the same issue, haven't found a fix yet. When you did your firmware updates, did you go directly to 2.24? Did you skip the leak before it? (I think it's 2.19?)
[One (M7) Original Android Development] flar2:
There are no issues with it except a few people don't like the new sweep2wake defaults.

Other than that, version 3.3 fixes the ondemand gpu governor, which is broken in 3.2, and has better build optimizations.

Any other issues are specific to certain users and would be there in any version.

As mentioned, you could try Bulletproof: http://xdaforums.com/showthread.php?t=2233665

Elemental is more customizable, but both are better than stock.

They might, depending on how you carry your phone. There will be no noticeable difference if you set the phone on your desk all day. You might see a difference if you constantly take your phone in and out of your pocket and the lining in your pocket is thin.

In practice, for most people it doesn't make much difference in battery life. Personally, I'd rather have the features than the battery life (which is adequate on this phone even with stock configuration)

It will take a couple charge cycles to start getting accurate readings again after flashing new stuff. Especially if you flash many different ROMs and kernels.
[One (M7) Original Android Development] Beremus:
Few charge cycles is hard to do when we test every single kernel you release! =P
[One (M7) Original Android Development] flar2:
Barring any unforeseen problems, this will be the new official release.

Sweep2wake works differently (starting with version 3.3):

• There should be fewer accidental wakes, no accidental screenshots, and it should wake from deep sleep easily.

• The bigger change fixes an old bug where sweeping to sleep brought you back to the homescreen. Now, if you swipe fast enough, it will not register a home button press in the sweep, and your last app will be there when you unlock the phone again.

• Depending on how quick your fingers are, double tapping home could put the phone to sleep instead of opening recent apps. I've made the default button_timeout such that it is almost impossible for this to happen in normal use (button_timeout = 6). If you find that it happens too often, you can set button_timeout to a lower number, or disable it completely by setting it to 0.

• There is an option to set button_timeout in the Aroma installer. The setting can be changed after installation in /etc/elementalx.conf

• For button_timeout:

• Higher values make it more likely that your last app will be open after you sweep to sleep, but there is a higher risk of accidentally putting the device to sleep when double tapping home.

• Lower values make it less likely that your last app will be open after you sweep to sleep, but reduces the chance of a double tap of home being mistaken for a sweep2sleep.

• Setting button_timeout to 0 disables this feature completely

Simple GPU Governor:

• I adjusted the simple governor a bit so it doesn't constantly spike up to the max frequency. It's still very sensitive and shouldn't be noticeable performance-wise, but it will be slightly better on battery.

Some of the small changes:

• I've updated the modules to the ones from the 2.24 base

• The installer wipes cache at the beginning of install now

• Nothing in the installer mounts /data now (should help with encrypted phones)

• default max screen off frequency is now 702MHz and is applied to all cores (previously only applied to first core)

Download:

ElementalX-m7-3.4 RELEASE CANDIDATE

Changes:

-updated modules

-updated installer

-default max screen off frequency 702MHz

-fix screen off frequency applied to all cores

-sweep2wake adjustments

-adjust simple governor

-home button timeout option in installer
[One (M7) Original Android Development] lichti1901:
Thanks for the update.

Thats a good way to end the work day and start my freetime. :)

Sent from my HTC ONE running ViperRom
[One (M7) Original Android Development] sensationfan623:
Anybody have any opinions usb fastcharge?
[One (M7) Original Android Development] michmeister:
It works!

Sent from my HTC One
[One (M7) Original Android Development] sensationfan623:
Huzzah! I've heard however that it's bad for the battery's health. That true?
[One (M7) Original Android Development] kazemitsui:
haha you tell me it takes a couple charge cycles and then you go an release 3.4 :p

off to flashhh as i dont want trickester to set the default screen off heh
[One (M7) Original Android Development] flar2:
No. It just allows you to charge faster from a USB port, if the port can deliver the current.

I'm hoping this is the official release and no more updates for a while.
[One (M7) Original Android Development] maverick1103:
Ok thanks I will go ahead and flash the 3.3 then, I was having some issues with sweep2wake before so hopefully the new version will be better for me.... thanks for the feedback :)

Edit: Well as you have released 3.4 I'll go straight to that one :cowboy:
[One (M7) Original Android Development] lolpos:
Flash 3.4 it is an rc
[One (M7) Original Android Development] maverick1103:
Yeah I am, didn't see the 3.4 release until after I wrote the message.....dam he's quick!!!
[One (M7) Original Android Development] glor:
After installing 3.4 the Menu button in Google Play is gone. Any help?
[One (M7) Original Android Development] maverick1103:
That's because it's set by default to remove the menu button, reflash kernel and choose restore on that option.
[One (M7) Original Android Development] glor:
Thanks a lot. It works.
[One (M7) Original Android Development] maverick1103:
Glad to help :)
[One (M7) Original Android Development] tyraelasd:
"Some of the small changes:

• I've updated the modules to the ones from the 2.24 base

• The installer wipes cache at the beginning of install now

Hey [MENTION=4684315]flar2[/MENTION] , what If I'm running ViperOne wich hasn't been updated to that base, is still on 2.19 , wouldn't that be a problem to flash 3.4? I'm on 3.3 .

Thanks so much, I'll donate very soon after a couple of days using this amazing kernel.
[One (M7) Original Android Development] flar2:
No problem at all, I'm using Viper right now.
[One (M7) Original Android Development] :
flar2 thanks to the 3.4, great job!
[One (M7) Original Android Development] WTFunk:
3.4 is perfect now. Thanks for all the betas but time to slap an official tag on it and profit. I had the screenshot issue and d2w screen off but their both gone now.
[One (M7) Original Android Development] flar2:
Thanks to all who tested the many beta versions. There are so many options and different configurations that I depend on having hundreds of people test these out to uncover bugs. That's why I've kept the open beta concept.

Sorry for the rapid fire release, but I think it was worth it :good:
[One (M7) Original Android Development] aamitabh28:
Totally man..

Your kernel is really the best.

Thanks.
[One (M7) Original Android Development] zboq:
I have noticed that, trickster mod has some kind of problem with setting max cpu freq. I can see a lot of messages like this in logcat:

Write 'sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq' failed (Invalid argument).

Same for other cpus aswell. Ideas ?.

Wysłane z mojego HTC One
[One (M7) Original Android Development] michmeister:
3.4 working perfectly!

Sent from my HTC One
[One (M7) Original Android Development] lichti1901:
+1 for open beta testing :)

Sent from my HTC ONE running ViperRom
[One (M7) Original Android Development] evilmastr:
The beta testing has been very fun. Always something new to try. I've tried all the betas and 3.4 is the best! I managed to take a screenshot by tapping the home button, but only once and I can't replicate it again. :)

Thank you flar2! I can't afford to donate anything but I hope you know how much your work is appreciated!

T9'd from my black HTC One M7
[One (M7) Original Android Development] Luisit0:
At first I did, but then I flashed the 2.17 leak and re-flashed the 2.24 firmware again....
[One (M7) Original Android Development] tiho5:
Thank you, Flar!

Really great result!
[One (M7) Original Android Development] Beremus:
I find that ondemand is better for battery than intellidemand... Is it normal?
[One (M7) Original Android Development] cubsfan187:
Just a quick question. Any chance of seeing a way to change screen colors (like on the GNex) within the kernels for the ONE? That is the only think I miss from that phone. Lol. I know Faux was looking into it but that was a while ago.
[One (M7) Original Android Development] erto90:
What is wrong with the screen? Is absolutely the best lcd i ever seen in a phone!
[One (M7) Original Android Development] cubsfan187:
Nothing is 'wrong' with it. I just like the ability to change things. It was a great options for the GNex kernels. I love this screen too. Hell the whole phone for that matter. But the ability to make it warmer/colder colors would be cool too.
[One (M7) Original Android Development] 99piotrek:
I would Love to see that possibility...

Love it on nexus 4
[One (M7) Original Android Development] cubsfan187:
I hope someone looks into it soon.At least find out if it's possible or not.
[One (M7) Original Android Development] flar2:
Eventually, but I'm taking a break now. Probably until HTC releases new source code.
[One (M7) Original Android Development] Bluewall:
May I ask for good settings for Simple GPU governor? Or anything you would recommend [MENTION=4684315]flar2[/MENTION]?

Envoyé depuis mon HTC One en utilisant Tapatalk 4 Beta
[One (M7) Original Android Development] hasan_abeer:
Please any chances to record calls from kernel dev ...please we need your help. ...
[One (M7) Original Android Development] tiho5:
+ 1
[One (M7) Original Android Development] Dangermous79:
[MENTION=4684315]flar2[/MENTION] Just like to say thank-you for this great kernel, smoothness and battery life is amazing. Great work :victory:
[One (M7) Original Android Development] michmeister:
+1

Sent from my HTC One
[One (M7) Original Android Development] cubsfan187:
Thanks for the reply Flar. Love the kernel btw. Keep up the great work with it. Looking forward to what's next for ElementalX.
[One (M7) Original Android Development] flar2:
Je tu recommande de laisser les réglages par défaut.

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

After I take little break and update my other kernels, I'll have a look at the call recording and color things. No guarantees that I'll be able to come up with anything in either case, I haven't looked into these at all yet.
[One (M7) Original Android Development] Bluewall:
Wow a french answer? Many thanks mate :)

Envoyé depuis mon HTC One en utilisant Tapatalk 4 Beta
[One (M7) Original Android Development] nickabbott:
Flar2 is from Canada and quite a lot of Canadians will speak French :)

Speaking of which I'm posting this from Disneyland Paris too :D

Still time to catch up when back in the hotel!!!
[One (M7) Original Android Development] Beremus:
En effet!
[One (M7) Original Android Development] Bluewall:
Les francophone prennent le pouvoir !

Well, anyone using Simple GPU governor ? Do you feel any improvement with it ?
[One (M7) Original Android Development] picard47:
Testet 3.4 on Renovate 4.0. Seems not to cooperate with this ROM.

Short test with Antutu got 19000 points, first run even crashed. After 10 minutes the phone was so hot that I thought the screen melts.

Flashed back the original Renovate boot.img and temperatur went back to normal and round about 24500 points.
[One (M7) Original Android Development] a box of kittens:
Is my French off or is that bad grammar;) ooh I see he probably meant je te* makes more sense.... Love the french and the kernel!
[One (M7) Original Android Development] michmeister:
Works amazing on arhd 12.1

Sent from my HTC One
[One (M7) Original Android Development] flar2:
You're doing something wrong

Whoops, sshould be je te :good:
[One (M7) Original Android Development] picard47:
[MENTION=4684315]flar2[/MENTION]

Possible. I've tested your kernel sporadically up to 3.2 with Stock ROM and never got such problems. Renovate ROM has a lot of own modifications and init.d scripts. Maybe there is somehing that not come along with elementalx. But I didn't want to test it out so much longer because I have no backup phone at the moment and I am not familiar with that kind of stuff :D.

Btw. In the CM10.1 thread they already came to the conclusion that every One Device can react quite different on same circumstances. (In the german android-hilfe.de forum a guy just lost his usb connection ability after flashing the bulletproof) .... strange mysterys of android^^

Thats no criticism on kernel. Just feedback.
[One (M7) Original Android Development] mwilky:
Works amazingly well with renovate, twice as good as stock kernel

HTC One - RenovateROM
[One (M7) Original Android Development] poondog:
I'm running 3.3 on renovate 4 no problems :)