yashsingh1/xdaforums huggingface dataset:
[One (M9) Original Android Development] shivasrage:
Make sure you are on latest firmware 1.40.401.8 otherwise you will have issuses. ;)
[One (M9) Original Android Development] mcnaget:
I am on latest .8 firmware.

regards
[One (M9) Original Android Development] Andrewbud:
No issues while using viper. Thank you.
[One (M9) Original Android Development] colorprint:
works fine with stock 1.40.709.4 firmware
[One (M9) Original Android Development] ZeroInfinity:
Works great on MaximusHD 4.0.1 :)
[One (M9) Original Android Development] liam_davenport:
No problems here on LeeDroid with .8 firmware
[One (M9) Original Android Development] sirioo:
Works on ViperoneM9 2.3.1 with 1.40.401.8 firmware
[One (M9) Original Android Development] feenty:
Sorry if it was answered before, but disable cover means disabling magnetic sensor for dot view case?
[One (M9) Original Android Development] mcnaget:
Ok im gonna try again.

thx

---------- Post added at 12:55 PM ---------- Previous post was at 12:32 PM ----------

Nope no go , im gonna try maximus rom

regards
[One (M9) Original Android Development] Devaster:
Same here
[One (M9) Original Android Development] ahrion:
What do those of us who can't get the 1.4 firmware do (T-Mobile)
[One (M9) Original Android Development] donmarkoni:
You could cry in desperation, or you can use version 0.3 and enjoy it. ;) Performance and features are the same.

Cheers! :)
[One (M9) Original Android Development] flar2:
Yes, version 0.3 is absolutely fine if you're on earlier firmware.
[One (M9) Original Android Development] flar2:
If any of the people who couldn't get 0.3 to boot are still around, let me know how 1.00 goes. '

If there are still problems, another dev told me what was causing it. But I'm crossing my fingers that I don't need to change anything on 1.40 base.
[One (M9) Original Android Development] Anzinger:
Sorry, the Problem with bootloop is always there
[One (M9) Original Android Development] mcnaget:
I have tried two different rom maximus and leedroid but no effort could not go pass the htc logo , keep restarting.

Unlocked , s-off , .8 firmware

If helps in anyway

regards
[One (M9) Original Android Development] flar2:
You have the same problem as a couple others. I will try to fix it this weekend. Another dev told me that removing sweep2sleep fixed it for him. I don't want to remove it, I'll just try to fix it so it works for everyone.
[One (M9) Original Android Development] shivasrage:
Also here.....working fine on MaximusHd 4.0.1 with vers. 1.00 and 1.40.401.8 firmware...:)

regards
[One (M9) Original Android Development] itzsnookums:
I'm in love
[One (M9) Original Android Development] Andrewbud:
battery drain is very high. Getting a slow charge warning when charging. HTC weather refuses to function. Will try a fresh install this evening.
[One (M9) Original Android Development] iElvis:
Updated to 1.401.401.8 firmware, flashed 1.00, all seems to be working fine.

The app does want me to download 0.3, but I assume that's just a naming issue.
[One (M9) Original Android Development] sirioo:
Gov : elementalx ?
[One (M9) Original Android Development] itzsnookums:
Yeah
[One (M9) Original Android Development] DroidShift79:
1.40 kernel? I thought there isn't a source, yet

Gesendet von meinem HTC One M9 mit Tapatalk
[One (M9) Original Android Development] jollywhitefoot:
Flar got it last night and cranked the updated kernel out shortly thereafter.
[One (M9) Original Android Development] flar2:
I guarantee none of this is due to the kernel.
[One (M9) Original Android Development] flar2:
Interesting, I am getting a slightly higher battery drain on elementalx governor than I did on 0.3 (this is not a big difference, only something you would notice if you scientifically measure it). It must be due to changes in pnpmgr, as kernel side is identical on 1.00 and 0.3. I will to measure this for a longer period of time to see if it's real.

Idle drain is slightly lower than stock kernel, and this is the exact same behaviour as on 0.3. (Again, we're talking very slight, 0.6 to 0.7% per hour on stock vs 0.4-0.5% per hour on EX).

Another note: I haven't looked closely at the differences in source, but there were a lot of changes to battery stuff, which I left alone. So, the "no charge" bug seen on the 1.40 base is probably there (I have not experienced it personally)
[One (M9) Original Android Development] Andrewbud:
Possibly my bad flashing habits. Will try a fresh install of everything after Work.
[One (M9) Original Android Development] feenty:
On latest maximus with latest fw i had bootloops too at the red warning screen.

(disabled the sweep2sleep, elementalx gov, underclocked gpu to 510mhz, balance, usb fastcharge enabled, backlight dimmer enabled, i/o default) if i remember correctly
[One (M9) Original Android Development] Nekromantik:
Same here, getting boot loops again :(
[One (M9) Original Android Development] grv00711:
nice
[One (M9) Original Android Development] Svid:
Same issue here.

Can't pass the HTC splash screen, rebotting itself all the time.
[One (M9) Original Android Development] Strangeland16:
you still think you can get some more battery life with on screen time like you thought a while back mate ?
[One (M9) Original Android Development] flar2:
Definitely, but it's a moving target with HTC constantly changing things around. Even worse, there is no changelog except a couple lines in the OTA, no kernel commit history, and pnpmgr is a closed binary. I have no idea what's in it.
[One (M9) Original Android Development] Strangeland16:
Nice one they don't like making it easy for you do they ?. Keep upthe good work it's developers like you that are Making the battery on this device usable without your hard work I would not get a day usage before having to recharge . Thanks your hard work is appreciated
[One (M9) Original Android Development] feenty:
What rom are you using? Tried with different rom?

Its not working for me with maximus. Should i try with different one?

... From Tapatalk by M9
[One (M9) Original Android Development] Svid:
ViperM9 2.3.1.

Did clean install - same result.

Unlocked + S-OFF
[One (M9) Original Android Development] jeryx:
[MENTION=4684315]flar2[/MENTION] I'm on latest maximus rom... Latest firmware... I'm also using your app... Problem: if I enter aroma and make the settings and confirm to flash, it's start shortly and make the reboot...nothing changed after this... I downloaded from the app, tried it several times... No luck... I also wiped cache and dalvik... No idea... Never had this problem before... Thanks in advance!

Edit : I have to say, it don't start to flash something... The device restart shortly after confirm the settings I chose... I hope that helps...
[One (M9) Original Android Development] guiltyundertaker:
I just flashed on viper 2.3.1 and everything appears to be fine here so far...
[One (M9) Original Android Development] flar2:
Aroma crashes? Try the express version.
[One (M9) Original Android Development] itzsnookums:
Still going strong
[One (M9) Original Android Development] atomantmk:
I'm using ARHD 8.1 and after installing version for 1.40 base phone don't want to boot, all i see is how phone reboots and HTC logo.

I have try several times to install kernel with different options but no success.
[One (M9) Original Android Development] iElvis:
Not seeing any bugs on mine. If anything, the charging is faster on this firmware.
[One (M9) Original Android Development] Favorito:
tried to flash it after flashing leedroid, but got bootloop unfortunately. I used your kernel in my nexus 5 but cannot get around it in the M9 ... talking in the firmware 1.40.408 and 1.0 elementalx.
[One (M9) Original Android Development] ThE_DeamoN:
This one is with stock kernel on Viper One and almost 4 hours of music playing

Tomorrow I will test Flar's creation :)
[One (M9) Original Android Development] Cryosx:
Drain is greater but responsiveness is back to normal. Stock 1.40 would get sluggish.
[One (M9) Original Android Development] iElvis:
Battery performance much improved for me as well. Went from ~3%/hr in normal use to 1.5%.
[One (M9) Original Android Development] flar2:
The boot loop is a known problem, it happened on 0.3 too. It's probably due to the vibration option I added to sweep2sleep. There must be hardware variations. I will release a new version without it later tonight.
[One (M9) Original Android Development] fallenangel408:
i am running same as you buddy but i had to reinstall older version new one gives me reboots when i make a call and try to use volume it reboots...can u try that?

i am back to 0.3 version no probs
[One (M9) Original Android Development] flar2:
version 1.00 doesn't match your firmware/ROM combo

It doesn't matter, 0.3 and 1.00 are virtually the same. My changes are exactly the same in each, and HTC barely made any kernel changes in 1.40. But the slight changes they made depend on specific firmware.
[One (M9) Original Android Development] flar2:
Would those who had bootloops on version 1.00 please try this and let me know if it works:

https://www.androidfilehost.com/?fid=24052804347762221
[One (M9) Original Android Development] TorrentzRock:
ARHD 8.1, newest firmware, and EX 1.0 flashed last night. No problems to report here. Battery is a tiny bit better than stock kernel, responsiveness is A LOT better than stock. Thanks [MENTION=4684315]flar2[/MENTION]!

HTC One M9 | ARHD | ElementalX
[One (M9) Original Android Development] fallenangel408:
thank you will update firmware and try again :)

*update firmware and alls well thanks again
[One (M9) Original Android Development] feenty:
Sorry, but bootloops too with that. :(

... From Tapatalk by M9
[One (M9) Original Android Development] Svid:
Negative. Same bootloop after splash screen
[One (M9) Original Android Development] flar2:
Alright, another test (gets rid of sweep2sleep completely):

https://www.androidfilehost.com/?fid=24052804347762255
[One (M9) Original Android Development] feenty:
Yes, finaly booted up with version D!

Thanks for your hard work!

... From Tapatalk by M9
[One (M9) Original Android Development] flar2:
Alright, now to figure out why sweep2sleep built in to the kernel causes a bootloop. If anyone knows how to get a log from that bootloop, I would really like to see it.
[One (M9) Original Android Development] mcnaget:
Yes this version is ok.

regards
[One (M9) Original Android Development] Anzinger:
Same to me. The Test Version is okay. Never made a logcat. Is this the right One?
[One (M9) Original Android Development] Asselalf:
Good work on V1

Gesendet von meinem HTC One M9
[One (M9) Original Android Development] Nekromantik:
Test D works here too :)
[One (M9) Original Android Development] Serebii179175 IV:
Works

Test D works here
[One (M9) Original Android Development] Andrewbud:
With a fresh rom install everything is perfect. Thank you :)
[One (M9) Original Android Development] Svid:
I can confirm sucsessful boot
[One (M9) Original Android Development] uniquey:
Still in bootloop

Test D does not work for me, It is still in bootloop, I'm using viperone m9 2.3.1 and latest firmware. thank you
[One (M9) Original Android Development] darkmantra:
Works fine here on Vipers 2.3.1 no reboot so far. Battery seems good.. @14Hrs still at 57%
[One (M9) Original Android Development] Chris32B:
Test D works fine here on MaximusHD 4.0.1. :)
[One (M9) Original Android Development] jimmy69:
Test D works fine here on InsertCoin
[One (M9) Original Android Development] Mostafa Wael:
Anyone ? :D
[One (M9) Original Android Development] ksword23:
I can consistently get 5 hours SOT with about 18 hours standby and have about 10% left every day on 1.40 firmware and this kernel :)
[One (M9) Original Android Development] BUBBA DUB'S:
Does quick charge improve with use of this kernel on 1.40.xxx.8 update? Just curious due to reading about issues with slow charging after that update.
[One (M9) Original Android Development] Andrewbud:
Charging is fantastic.
[One (M9) Original Android Development] jollywhitefoot:
I did experience slow charge issue with this kernel after going to 1.40 base.
[One (M9) Original Android Development] uniquey:
question for bootloop

Sorry. I'm a noob here. Should I upgrade my firmware 1.40.xxx.5 to 1.40.xxx8 ? Because for some reason, the test D file still gives me bootloop. I'm T-Mobile and currently running viper one 2.3.1. I'm able to run elemental X 0.3 but I can't run 1.0. Thank you very much
[One (M9) Original Android Development] gnomish:
FYI - New test version worked for me. Original was giving me TWRP reset and then forced boot when trying to install. (1.4 w/ latest viper 2.3.1 on dev unlocked s-off.) Thanks for all the hard work! Can't wait to try this new config out
[One (M9) Original Android Development] BUBBA DUB'S:
All up to you, 1.0 requires 1.40 firmware while 0.3 is based off of 1.32. 1.40.xxx.5 vs 1.40.xxx.8 both work, I believe with 1.0 elemental. I am not familiar with the subtle differences between 1.40.xxx.5 and 1.40.xxx.8 though.
[One (M9) Original Android Development] bzhmobile:
[MENTION=1187431]gnomish[/MENTION]

Did you use the lastest version of TWRP from Captain_Throwback?
[One (M9) Original Android Development] gnomish:
Actually no, is it listed here? http://xdaforums.com/one-m9/orig-development/recovery-twrp-touch-recovery-t3066720

I will try it, thanks!
[One (M9) Original Android Development] uniquey:
If 1.40.xxx.5 and 1.40.xxx.8 both should work, then why elemental X 1.0 (test D version) still gives me bootloop? And what should I do here? Thanks

---------- Post added 22nd June 2015 at 12:27 AM ---------- Previous post was 21st June 2015 at 11:59 PM ----------

If 1.40.xxx.5 and 1.40.xxx.8 both should work, then why elemental X 1.0 (test D version) still gives me bootloop when my firmware is 1.40.xxx.5? And what should I do here? Thanks
[One (M9) Original Android Development] bzhmobile:
This one 2.8.6.1_CPTB-B2 ;)
[One (M9) Original Android Development] sdamark:
If the .3 build is working for you, then you are still on old firmware.
[One (M9) Original Android Development] PlatinumNick:
noob question on the installation piece, i know to install you have to install it after you flash your desired rom, only because if you flash the rom after its going to wipe the kernel and put the stock one on, but how do you get out of a bootloop if such things occur, im used to a samsung where i just take out the battery lol
[One (M9) Original Android Development] feenty:
You have to hold down the power+vol down button for 10 or 15 sec and it will restart to download mode...

from there you can navigate to recovery and can do a dirty flash of original kernel or the rom itself (it contains the kernel)
[One (M9) Original Android Development] PlatinumNick:
ok, so you flash your desired rom, then flash this kernel and follow the aroma installer?
[One (M9) Original Android Development] jollywhitefoot:
Yes. Just make sure you get the correct version for your current firmware. Version 0.3 of this kernel is for 1.32 and version 1.0 is for 1.40.
[One (M9) Original Android Development] flar2:
Question:

For those who had boot problems on the standard versions with sweep2sleep, were you able to use the sweep2sleep module I made for the stock kernel?
[One (M9) Original Android Development] flar2:
Upon further testing, I'm getting similar battery life with elementalx governor and stock interactive. This will vary slightly depending on the performance mode chosen during install. If you choose balanced or stock profile and use elementalx governor, it should generate slightly less heat than stock.

Idle drain is marginally better with ElementalX kernel compared to stock kernel.

Responsiveness is better with ElementalX.
[One (M9) Original Android Development] flar2:
CPU Times

I made a new app so you can monitor CPU usage (time in state) on the A57 cluster. This one is free and doesn't require root.

https://play.google.com/store/apps/details?id=flar2.cputime

If you have EX Kernel Manager, this is already built in. I wanted to try doing a freemium app and see how that goes, plus this fills a niche because CPU Spy only shows stats for the first cluster.
[One (M9) Original Android Development] Anzinger:
I dont know that you do sweep2sleep for Stock Kernel. Where can i find it?
[One (M9) Original Android Development] flar2:
http://xdaforums.com/one-m9/orig-development/mod-sweep2sleep-t3095952
[One (M9) Original Android Development] Nekromantik:
Cant answer that as I never used S2W.
[One (M9) Original Android Development] Mostafa Wael:
Does elementalx make use of the hotplug ? Or does it keep all the cores online? And how does it balance loads? Does it lean more on the A53 like stock or lean more on the A57 cluster ?

Thanks alot

Looking forward to installing your kernel ...
[One (M9) Original Android Development] flar2:
Hotplugging is same as stock (A57 offline while screen is off). According to my tests, its not worthwhile to offline cores. Traditional hotplugging goes against the idea of big.LITTLE instantaneous thread migration.

Load balancing is updated with the latest CAF commits, plus I've added a setting to control pnpmgr's throttling of A57 use. Check earlier in the thread for an explanation of min_budget
[One (M9) Original Android Development] uniquey:
Forgive me if I am wrong. Under my about -> software information -> build number, it shows 1.40.401.5 CLXXXXX release-keys, but I can only run elementalX 0.3. 1.0 still gives me bootloop. I also tried wipe catch, and still no luck. I am tmobile, running on viperone 2.3.1. Please let me know if I checked my firmware in the wrong way, and what should I do next. Still a big noob here thanx
[One (M9) Original Android Development] jollywhitefoot:
Reboot into download mode and your firmware is listed as OS.

Edit: the build number is derived from the Rom's build.prop file so may not be accurate...for example, mine says 1.32.501.9 (early AT&T firmware), but I'm really on 1.40.401.8.

Edit2: if 0.3 works, then you're certainly on the 1.32 firmware. You can run 1.40 roms as long as you flash 1.32 kernel and Viper does this for you in Aroma installation.
[One (M9) Original Android Development] iElvis:
For those of you with the slow charging bug, it seems HTC has come up with a solution:

http://xdaforums.com/showpost.php?p=61481111&postcount=39

Many people are reporting this solves the problem and that the fix sticks. Seems that something in the 1.40 firmware upgrade process borked the battery management system, and the battery needs to be recalibrated if you're having trouble.

Bottom line, it has nothing to do with the kernel.
[One (M9) Original Android Development] uniquey:
Thank you so much! I just checked and yes, in the download mode, it showed 1.32 firmware. I will try to update my firmware. Allow me to ask one more noob question, so far, I don't think Tmobile has 1.40 firmware, but can I still flash 1.40?
[One (M9) Original Android Development] jollywhitefoot:
If you're s-off you should be able to. Otherwise you need to wait until TMobile releases the new firmware, return your system to stock, and take the OTA update with the new firmware.
[One (M9) Original Android Development] 123421342:
So anyone using this kernel on the latest viper? Does it actually offer any battery enhancements?
[One (M9) Original Android Development] sdamark:
T-mobile has not yet updated to 1.4xxx firmware. You can use Super CID and install international firmware, however Wi-Fi internet calling will be lost.

In my opinion, I would wait.

T-mobile should be releasing their own updated firmware shortly, and then everything will work.

The international firmware has a slow charge bug for some, that should be fixed when TMOus, Sprint, and Verizon release their update.

---------- Post added at 03:47 PM ---------- Previous post was at 03:44 PM ----------

Yes, and, yes. ?
[One (M9) Original Android Development] uniquey:
thank you so much, learn a lot. I will wait for the tmobile update. One last noob question, so once the T mobile firmware is out, I should unroot my device and return to the original Tmobile stock to update the firmware, and then root again with the rom I want, right? (if I don't want to s off, and flash the firmware)
[One (M9) Original Android Development] sdamark:
Just break out the ol' wallet and pay the guys @ Sunshine their $25 and get your device S-Off. :good:

That way you can update or downgrade your firmware as you please. :D

Problems in the past, on other devices, was the new firmware came out and HTC patched the exploit for S-Off.

It was several months before, luckily, another exploit was discovered.

So.... my advice to you is get it while it's there and it works.
[One (M9) Original Android Development] flar2:
Another test (because I don't want to get rid of sweep2sleep)

In this one, I've built sweep2sleep as a module.

I would like one of the people who had bootloops to try something:

1. In the Aroma installer, select either sweep2sleep right or left (or both) and see if it boots

2. If it crashes and reboots shortly after booting (ie, when the module loads), then please grab a log so I can see what is causing it to reboot.

To get the log, let it crash, then when it reboots, right after the initial splash with the red text disappears, connect the phone to your computer via usb and type:

adb shell cat /sys/fs/pstore/console-ramoops > kmsg.txt

Download test_e:

https://www.androidfilehost.com/?fid=24052804347763697
[One (M9) Original Android Development] flar2:
Anyone?

Check out the battery life on this one too, I left in some experimental changes
[One (M9) Original Android Development] Strangeland16:
I never had boot loops on previous but I'm willing to try it out if it helps ? Can report back about battery will it effect screen on time or just stand just so I know what I'm looking out for ?

---------- Post added at 01:03 PM ---------- Previous post was at 12:56 PM ----------

No boot loops but as I say I never had in previous will let you know about battery life once I've used it for a while
[One (M9) Original Android Development] shivasrage:
Same for me... I also willing to help but never had bootloops with 1.00 so I can´t help you with the log you need.

Only thing I can do I can compare the battery from test_e with the 1.00 version.

regards
[One (M9) Original Android Development] flar2:
Should be better screen on time
[One (M9) Original Android Development] Strangeland16:
Great will let you know thanks
[One (M9) Original Android Development] feenty:
I need a few hours to get home, then i can test for you.
[One (M9) Original Android Development] brittoking:
Should we try this [MENTION=4684315]flar2[/MENTION] if, like the other two posters who offered to test, if we haven't ever experienced the boot loops? I'd love to help AND id love to get some extra screen on time. Let me know if there's any log you need collected or something in particular I should be paying attention to.
[One (M9) Original Android Development] Golv:
As I understand there was reduced minimum frequency of cores 4-7 - 384MHz in new stock kernel from new firmware 2.7.401.1 (Android 5.1) ????
[One (M9) Original Android Development] 123421342:
So is this compatible with the new 2.7 firmware?
[One (M9) Original Android Development] iElvis:
Unlikely, since the Android base has changed: 5.0->5.1.
[One (M9) Original Android Development] flar2:
Probably, I saw a commit for this in CAF repos.
[One (M9) Original Android Development] ksword23:
Now we wait an eternity and a half for HTC to release their new source :crying:
[One (M9) Original Android Development] shivasrage:
In my first test shot 1.00 boots with 2.7.401.1 base and MaximusHD 5.0.0 ... WIFI etc. is working except the camera.

Camera shows no picture after a while it FCes...

regards

edit:

with new stock kernel the min freq. of big cluster now goes down to 384 MHz
[One (M9) Original Android Development] iElvis:
Well, that's not good, but hardly surprising.
[One (M9) Original Android Development] patience88:
Gonna test now:D:D

Sent from my HTC One M9 using Xparent BlueTapatalk 2
[One (M9) Original Android Development] matteh80:
It doesn't work for me. Kind of boots up, but reboots right after showing lock screen for a very short time. Will send log tomorrow if not anyone else does it before me.

Test d worked fine by the way.

Skickat från min HTC One M9 via Tapatalk