yashsingh1/xdaforums huggingface dataset:
[One (M9) Original Android Development] skulldreamz:
Do a clean install and don't restore apps and data with titanium backuo if your using it. I've owned the m7, m8, m9 and never ever had a bootloop because I format data every time b4 I flash a rom and kernel. I know it might sound like it takes longer but if you restore everything with a app like tibu and get bootloop then have to reinstall clean it actually is taking twice as long. Just set up fresh each time and you won't deal with any issues if your on the correct firmware.
[One (M9) Original Android Development] allroy75:
Man you are getting like twice as good as me. That is crazy. I've been using ELX since my m8 but never had the manager app. Just bought it. I think I got mine set up as above. Can anyone give me any more good tips in getting the best performance out this kernel? Thanks.
[One (M9) Original Android Development] 1337jay:
Hexacore settings do not apply on boot if selected in EX Kernel App, gotta manually switch after every reboot.
[One (M9) Original Android Development] Christof-:
You can also choose it in the aroma installer. Worked for me.
[One (M9) Original Android Development] dsg2003:
Snah001, thx for your settings, I will give them a try on my phone. I will report.
[One (M9) Original Android Development] 1337jay:
I know, thanks...just wanted to share this so it gets fixed asap.
[One (M9) Original Android Development] dsg2003:
Readahead and minimum performance level (60%) can only setted in elemental app,right? Unfortunately you must set this settings after every reboot. Or is there a possibility to save this settings?
[One (M9) Original Android Development] 1337jay:
You can set this in Aroma aswell, performance level is Select performance mode (set to balanced by default) and readahead is there too.

But you can click the switch at the end of each line in the EX App to apply settings on boot (the icon has to become blue).
[One (M9) Original Android Development] skulldreamz:
[MENTION=4684315]flar2[/MENTION] do you know if this will work on the new 2.11 developer firmware? Probably not just curious...
[One (M9) Original Android Development] Snah001:
Sometimes the app doesn't apply the manual setting of the app after reboot.

So I always check it after a reboot to be good.
[One (M9) Original Android Development] flar2:
The app always applies the settings after boot, but:

- the settings are not applied right away, I had to add a delay because of pnpmgr

-there is also a delay for the settings in elementalx.conf

-if each has different settings, there's a race, and not sure which settings will win (should be the app)

-both of these also race with pnpmgr and HTC's settings

The only thing I can do is make the delay longer

Also make sure you wait for a minute or two before checking the settings after rebooting.
[One (M9) Original Android Development] k1moe:
No mate, the app is perfect as it is [emoji106]

All settings are working for me..

tapatalked..
[One (M9) Original Android Development] Snah001:
Results from today, now with 30 mins call time again at about 50% battery remaining:
[One (M9) Original Android Development] dsg2003:
Snah001, that's amazing. I have set your settings in my kernel configuration. But after a few hours I can tell, that my result will be not so good as yours....
[One (M9) Original Android Development] BUBBA DUB'S:
Don't know if you have tried this, but let your battery run out completely till your device shuts off, then charge to 100%. Also make sure to wipe both caches in recovery when changing setting in aroma.
[One (M9) Original Android Development] dsg2003:
No I didn't charge from 0 to 100... Is there really a difference.....

Normally I always wipe cache and dalvik when I install something. But I installed elemental kernel from the elemental app. After aroma settings and installation automatically comes a reboot....there was no chance to wipe cache.
[One (M9) Original Android Development] BUBBA DUB'S:
I notice a difference when I let the battery drain out fully. I'll plug it into my charger let sit for 15 minutes while off , then turn it on and wait till 100% before I use it. I'll reset my battery monitor when I start work tomorrow , but I'm at 70% since 5am and work outside in the heat.

I don't know if my screen on time will be as good as shown above because I need full brightness to see when its sunny.
[One (M9) Original Android Development] Snah001:
This is after 5 hrs SOT just browsing, tapatalk, blinkfeed, read mail etc. and still 25% left. So I gues with these settings 6hrs+ SOT time till empty shoud be possible. Depends on usage.
[One (M9) Original Android Development] 1337jay:
Do you mind posting a screenshot of Apps usage in GSam?
[One (M9) Original Android Development] gelo01:
Why keep posting pics with 50% usage? Who needs that anyway.. Why not post until 1% of the battery is left, therefore we can see the total battery endurance of the M9. Smh.. :rolleyes:
[One (M9) Original Android Development] Snah001:
Because when I go to sleep phone is still at 20% so I post the results just after dinner time. At least that gives a pretty good idea of the sot.

Verstuurd van mijn HTC One M9
[One (M9) Original Android Development] donmarkoni:
Guys, please move battery life and screen on time discussion to appropriate thread:

http://xdaforums.com/showthread.php?p=59766668

Thanks and cheers! :)
[One (M9) Original Android Development] Mostafa Wael:
[MENTION=4684315]flar2[/MENTION] why does your elementalx governor keeps both clusters at 960 MHz most of the time ?

what's the benefit ?!

i am interested to test it

now i am going full stock settings in AROMA, i mean your default settings, even the clocks of both clusters, though i feel 1555 MHz is a bit high for the A53 cluster.

Anyway, does disabling the fsync have a negative impact on the battery life ?

this kernel has a lot of potential. It is a beast!
[One (M9) Original Android Development] baskva:
Should I wipe cache/dalvik after flashing elementalx?
[One (M9) Original Android Development] k1moe:
Yes it's recommended to wipe cache/dalvik. Otherwise you might stuck in bootloop..

tapatalked..
[One (M9) Original Android Development] gelo01:
I installed EX without wiping anything. Works flawless.
[One (M9) Original Android Development] k1moe:
Yes, should work.

But sometimes there are problems and so you can reduce them [emoji6] Had the same problem without wiping cache/dalvik after first installation coming from another kernel.

tapatalked..
[One (M9) Original Android Development] 1337jay:
It keeps it at 960MHz while you use your phone, its under governor optuons, active_floor_freq. No, it might have a positive impact on battery life but can cause data loss, better to leave it enabled.

I'm running the hexacore setup someone posted a few posts back and I am still not sure about battery life..seems the same or maybe just a tiny bit better.
[One (M9) Original Android Development] Mostafa Wael:
Yeah i was just wondering what's the point of leaving it on 960 MHz and not the 384 MHz ??! ;)
[One (M9) Original Android Development] Quadrider10:
So far i found this setup to be quite nice on thermals, performance, and battery:

Stock Performance mode

Interactive Gov

A53 1.2GHz

A57 1.5GHz

Hexa-core mode

1024 readahead

ROW scheduler

My battery problems are all due to google play services sucking it all up. Game performance is decent.
[One (M9) Original Android Development] white stormy:
i am using this on verizon and it works great except the usb charging mod doesn't seem to work. is this a known problem or is it just me doing something wrong?
[One (M9) Original Android Development] 1337jay:
[MENTION=4684315]flar2[/MENTION], do you use default settings of your kernel for daily use or have you made any changes? Cannot decide what to use...lol.
[One (M9) Original Android Development] flar2:
Works fine for me

I'm changing settings a lot right now
[One (M9) Original Android Development] flar2:
Update!!!

Some tweaks to the GPU to combat throttling, minor CAF updates and a new minimum brightness setting (backlight_min)

I will add the backlight_min setting to my app next update. For now you can change it like this:

echo 700 > /sys/backlight_dimmer/backlight_min

You can put any value between 5 and 4095 and the screen brightness won't drop below the value.

Download:

ElementalX-m9-3.06

Changes:

-reduce GPU throttle by one step

-increase down differential for simple ondemand GPU governor

-CAF updates to interactive and scheduler

-add backlight_min option
[One (M9) Original Android Development] Cryosx:
Got reboots with 3.06 (flashed over 3.05).
[One (M9) Original Android Development] mick_soul:
Same situation here.
[One (M9) Original Android Development] k1moe:
wipe cache/dalvik. worked fine for me..

thanks a lot mate.. thats a sweet awekening :highfive:
[One (M9) Original Android Development] skulldreamz:
Working insanely good for me. Has anyone ever seen active drain this low?
[One (M9) Original Android Development] Mostafa Wael:
What governor are you using ? Elementalx governor ? On 3.06 ?!
[One (M9) Original Android Development] Snah001:
Have continueous reboots even after wiping cache/dalvik.

Getting once optimising apps and then it keeps rebooting.

So back to previous build.
[One (M9) Original Android Development] Iceberger:
me too
[One (M9) Original Android Development] ZeroInfinity:
yup, same here
[One (M9) Original Android Development] k1moe:
Hm confused.. why it works for some peps and for others not? [emoji52]

What ROM are you guys using, xposed or any tweaking apps like trickster mod? Are you coming from 3.05 or from another kernel?

tapatalked..
[One (M9) Original Android Development] ZeroInfinity:
MaximusHD, nothing else and I just use the ElementalX app. Flashed from 3.05. Wiped Cache/Dalvik but rebooted after optimising then went back to "Android is upgrading" screen for the second time and it keeps on rebooting back to that screen.
[One (M9) Original Android Development] Snah001:
Same Rom here too.

Went back to 3.05 and all is ok again.

Did the update by the elemental app again and same results.

So back to 05 build till problem is solved.
[One (M9) Original Android Development] skulldreamz:
I'm using interactive for the first time on my m9, using deadline i/o, read ahead 512, all 8 cores on stock frequencies. I would really like to know why the such night and day difference because the changelog was not real invasive. It's either the new caf updates or the combination of interactive+deadline+512+simple_gpu_governor+8_cores. In a couple days I will keep everything the same but try changing to hex mode and see if that's even better and report.

Also I came from a clean install and by clean install I mean that I also format data/media anytime I install a rom even if its just a small update and I set up from new and I NEVER have any of the issues that I read other people talk about. You always want to install on a new clean ramdisk from my experience. I will never dirty flash anything, just don't see the point...
[One (M9) Original Android Development] k1moe:
I have flashed manually via recovery.. Maybe that's the difference?!

tapatalked..
[One (M9) Original Android Development] mick_soul:
I flashed it manually too, but have the problem.
[One (M9) Original Android Development] skulldreamz:
Also want to report that my cpu temperature is hanging around 27°C which it has never done b4. Always been around 35°C - 32°C b4 this change :D
[One (M9) Original Android Development] Snah001:
Tried flashing manually in twrp too and made absolutely no difference and why should it? From kernel app it also reboots into twrp!
[One (M9) Original Android Development] p50kombi:
Exact same here... Booting, then rebooting, rebooting.... You can fill in the rest [emoji6]

Exept I'm on arhd

**********

Sent from a tin of baked beans using some chewing gum, tinfoil, a piece of string and a manual written by MacGyver
[One (M9) Original Android Development] skulldreamz:
[MENTION=4684315]flar2[/MENTION] if you get the time could you please make a test elemental governor where it idles like interactive but keep everything else exactly as you have it and 1 more request, could you add user voltage regulation to your kernel please. Thanks my dude
[One (M9) Original Android Development] Mostafa Wael:
[MENTION=4684315]flar2[/MENTION] what's this confusion ?! never saw this before, even the alpha 0.1 :rolleyes:

looks like i am going to back off on 3.05 till this confusion is sorted out .... :/
[One (M9) Original Android Development] mick_soul:
Voltage changes are difficult on that device, because of pnpmgr and chipset reasons. Flar explained that many times...
[One (M9) Original Android Development] atomantmk:
Reboot after reboot and all day long, going back to 3.05
[One (M9) Original Android Development] flar2:
Not even one log after all these reboot reports?

How am I supposed to know what the problem is?
[One (M9) Original Android Development] flar2:
I assume these are boot loops? ( ie, it never actually boots into the system?)

Which settings are being chosen in aroma?

And I also need the log files in /sys/fs/pstore
[One (M9) Original Android Development] qriozum:
In fact, I confirm that occurs bootloop, despite wiping the Dalvik of the cache. No matter whether the wipe is made on or before flash files kenel.

ROM base is ViperOneM9 v3.5.0

regards

q.

--

wysłane z HTCOne (m9) przez Tapatalk v5.1.5
[One (M9) Original Android Development] Ferrum Master:
No problems for me also. Booted fine.
[One (M9) Original Android Development] gelo01:
Do you guys with know the proper combo in Color Control inside EX kernel app to mimic the display on M8? I think it's more vibrant than the M9. some pictures and games look dull..
[One (M9) Original Android Development] Ferrum Master:
First thing, you can't. The M8 gives a very warm tone. Red is very strong albeit also not correct.. But there are at least 3 versions of M8 LCD's i've cherry picked simply from many, they differ in contrast also a lot. I guess Mine was the Sharp one.

You can try mine... But as I said, they tend to differ a lot. - RGB 256:242:239
[One (M9) Original Android Development] gelo01:
I previously owned an M8 and the display on mine is just perfect. Not too warm, not too cold, so i am somehow disappointed with the M9's display. While the M8, you said that there were 3 diff displays, is that also the case on the M9? Anyway, thanks for the reply mate. Your settings are a little bit on the warm side so i just use 245 on Blue. :D
[One (M9) Original Android Development] flar2:
I've been using my m8 a lot for testing lately. While it has a very appealing display, when you put it side by side with other devices, the color accuracy is poor. The green in my DevCheck app looks bad on the m8. The m9 screen is more accurate, but not as bright and not as vibrant. There's nothing you can do about that, no settings will change it.
[One (M9) Original Android Development] Strangeland16:
Reboots also. Wiped the cache and still reboots. It never boots to system just get the HTC logo then phone vibrates and reboots and keeps looping the same thing. Running ice 3.1.2. Running with default settings in aroma
[One (M9) Original Android Development] flar2:
Can someone please post the information I asked for?

Complely impossible for me to do anything about this until I get that info.
[One (M9) Original Android Development] Ferrum Master:
Yes my current display is very cold, and with screen protector it gets even colder. Anyway I also noticed that M8 display was better out of the box. I like the device so much I didn't sell it and keep as a backup phone.

M9 is so rare in Baltics due to fact that there are no sales contract anymore valid, HTC strangely decided to add us to the Russian market, and their sales represantative just... disappered somewhere during winter without a finished contract lol, guess showing up F-22 Raptors in our turf won't help much. So only the Asian grey market units around, I have not had the possibility to order a bunch of M9 LCD's and compare them besides.

One thing is sure. There are two of them, just because of the sensor IC, my hipster device carries the max1187 one not the Synaptics.
[One (M9) Original Android Development] Strangeland16:
Have sent you a pm flar2
[One (M9) Original Android Development] fokus:
Same here on ARHD. Where can i get the last 3.05 version? THX.

Made a factory reset, so unfortunately i killed the old download folder :(
[One (M9) Original Android Development] Whiskey103:
http://www.vps.whiskey103.nl/owncloud/index.php/s/YcxqyIiEjROPhg6
[One (M9) Original Android Development] flar2:
I have no clue whatsoever why some people have bootloop. I've installed 3.06 with every setting and it's fine. Another HTC mystery, I'm betting it's related to firmware.

If you had the bootloop, try this kernel and see if it still does it:

https://www.androidfilehost.com/?fid=24052804347809588

Also, absolutely never flash my kernel over another custom kernel. It will break for sure.
[One (M9) Original Android Development] skulldreamz:
[MENTION=4684315]flar2[/MENTION] I flashed the original 3.06 on 2.10.401.1 T-Mobile ICE 3.1.1 and had a great experience for about 2-3 hours. Then all of a sudden it rebooted and none of the 2nd cluster cores would come on. I was getting the best experience until that happened. I will try 3.06b and if anything happens I will be due to get you a log
[One (M9) Original Android Development] k1moe:
Works fine.. even after 2nd installation and X reboots for testing..

What's that for a kernel is it worth to collect them? [emoji57]

tapatalked..
[One (M9) Original Android Development] liam_davenport:
Flashed on LeeDrOiD R30, Firm: 2.10.401.1, Xposed, No reboots :thumbup: :beer:
[One (M9) Original Android Development] Whiskey103:
Maybe ppl can tell they used the App route, Recovery route, express, custom etc.

Maybe we can narrow it down this way.

So ppl, state your situation... How did you install and what is your firmware etc.

I used the App route, settings express/default and latest 2.10 firmware.
[One (M9) Original Android Development] baadnewz:
Works fine here with my Rom (ICE) I doubt is Rom or settings related. Wild though. S-on/s-off? Fully unlocked? (see Scotty's thread in m9 general)
[One (M9) Original Android Development] flar2:
We need to be organized, please. Since there are no logs, I need to narrow t down by trial and error.

Only install 3.06b if you had bootloop from 3.06. And report in detail.
[One (M9) Original Android Development] Quadrider10:
Flar, what GPU gov do u recommend?
[One (M9) Original Android Development] p50kombi:
B does same for me. The system bits, the device starts normal, I see my wallpaper but before the pin screen pops up the device reboots. Then the same happens, so it does boot up the system but reboots before the pin screen. No laptop at hand so can't pull the logs, sorry.

**********

Sent from a tin of baked beans using some chewing gum, tinfoil, a piece of string and a manual written by MacGyver
[One (M9) Original Android Development] sdamark:
3.06b also repeated bl (will not boot to system). Installed with latest TWRP, Hex, balanced, all stock, s2s right & left, usb fast charge, dimmer, disable magnetic... Everything else in is my Signature.
[One (M9) Original Android Development] mick_soul:
3.0.6 and 3.0.6b not working for me too.

My settings in aroma are the same as for 3.0.5:

first cluster: 1205MHz

second cluster:1500MHz

GPU: 510MHz

s2s left, enable fastcharge, backlight dimmer

I attach the files of the folder /sys/fs/pstore and hope this will help you.
[One (M9) Original Android Development] DAIDY:
Imstalled EX 3.6 with ICE 3.1.2 no problem no reboot.

Inviato dal mio HTC One M9 utilizzando Tapatalk
[One (M9) Original Android Development] flar2:
Another test for people who had the bootloop with 3.06:

https://www.androidfilehost.com/?fid=24052804347809712
[One (M9) Original Android Development] flar2:
Perfect, that's how it's done!

Are you (and others with the bootloop) using an exFAT sdcard?
[One (M9) Original Android Development] mick_soul:
yes, I use an exFAT sdcard
[One (M9) Original Android Development] mamdouhn:
yes me too, I use an exFAT sdcard
[One (M9) Original Android Development] p50kombi:
C doesn't boot completely for me still, first cluster 13, 2nd 15, flops, 1024, s2w and only fast charge selected.

Got 128 gb sd card, think it's exfat but can't say for sure.

**********

Sent from a tin of baked beans using some chewing gum, tinfoil, a piece of string and a manual written by MacGyver
[One (M9) Original Android Development] Snah001:
Just jumped in here again. Have an exFat formatted card too.
[One (M9) Original Android Development] flar2:
The scheduler changes in 3.06 have caused the exfat mdule to break. I will have to revert them.

If you don't have exfat sdcard, 3.06 is perfectly fine.

This shows how critically important logs are, I looked at the log for 30 seconds and it was clear. Next time there is a problem, please post a log asap as it will save everyone a lot of time. Thanks [MENTION=4782292]mick_soul[/MENTION]
[One (M9) Original Android Development] Snah001:
After this morning I was gone so just jumped back in here.

When I knew this morning which file to pull for you I would have done it then.

But nevertheless good that you found the culprit,
[One (M9) Original Android Development] mikey_sk:
so the elemental app decided to upgrade the kernal and now i have bootloop too. what's the way out of this? never had an elematal x upgrade fail as spectacularly as this before .

i have 3.05 on the sd card will go into recovery and install that over, hopefully that will fix things ...
[One (M9) Original Android Development] Quadrider10:
Boot loops here with an exfat SD card.
[One (M9) Original Android Development] flar2:
Could someone with a bootloop on 3.06 try this one? I don't have an exFAT sdcard to test with, but it will probably be fixed.

https://www.androidfilehost.com/?fid=24052804347809900

The problem with 3.06 was the textfat module. I made changes to core parts of the kernel which broke the texfat.ko module. Because the texfat module (used for exFAT filesystems) is proprietary, there is no source code and I have to use the one that comes with stock (actually there is some source for exFAT driver, but it doesn't work properly with HTC). That means I am limited on the changes I can make to the kernel and still maintain compatibility.

As an aside, this is probably a big reason why Google discourages sdcards. A lot of them are formatted with exFAT, and exFAT is proprietary and not supported by the linux kernel. HTC has to pay Microsoft to support exFAT. So if Google wanted sdcards, they would either have to pay Microsoft or deal with thousands of angry users trying to use sdcards formatted with exFAT.

TLDR: the kernel itself was not unstable. It was the texfat module that caused the crash. So hopefully everyone isn't scared away from custom kernels again. People using stock are really missing out.
[One (M9) Original Android Development] k1moe:
Got an exFat formatted sdcard at home and will check it out ASAP.. think in the early morning..

"Scared away from custom kernels" whaaat?? [emoji15]

We don't wanna miss a thing [emoji106]

tapatalked..
[One (M9) Original Android Development] Quadrider10:
Working all good here!
[One (M9) Original Android Development] sdamark:
Booted up perfect. Thank you sir.

---------- Post added at 05:21 PM ---------- Previous post was at 05:20 PM ----------

P.S. nothing scares me away from anything. ?

---------- Post added at 05:24 PM ---------- Previous post was at 05:21 PM ----------

If the thing breaks, it breaks. After all, I'm the one that modded it in the first place.
[One (M9) Original Android Development] flar2:
Alright, pushing 3.07 out to the app.
[One (M9) Original Android Development] Quadrider10:
Sweet! What gpu gov do u recommend?
[One (M9) Original Android Development] frankcck:
No problem here on 3.07 with exfat.

Thanks again for your amazing works man!
[One (M9) Original Android Development] flar2:
stock for most purposes, simple-ondemand for gaming