yashsingh1/xdaforums huggingface dataset:
[One (M9) Original Android Development] cyber_system:
Why do we want pnpmgr running ?

Is it bad for my device to turn it off.

I am asking because that when i play a game and my HTC One M9 gets a little warm, it downclocks the CPU to 950Mhz, if i remember right :)

My guess it's to protect against overheating ?

Also when i try to set CPU cluster 2 to 1958Mhz. After some min. it sets itself to 1536Mhz again. I am not a pro. But that must be pnpmgr that doing that. When i turn pnpmgr off i Venom tweaks, i have full control of the CPU setting :)

Is there a larger meaning with pnpmgr ?
[One (M9) Original Android Development] flar2:
I don't know. I really don't like the new bootloader, it makes development difficult.

It looks like it boots a kernel for download mode, can you see if adb shell works in download mode and grab a log there (same commands)?

One more question: how long does it stay on the initial splash screen with red lettering? If it stays there a long time, you might be able to get adb shell whle that screen is showing, but it might require many attempts. I've found that adb shell access is very inconsistent, sometimes I can get it right away, and other times not until it's fully booted.
[One (M9) Original Android Development] ahrion:
Saveable profiles/scripts like the way ktoonsez does it would be sicknastygross. ?
[One (M9) Original Android Development] sdamark:
Verizon support?

Good morning, sir.

I have a VZW M9, S-off, running Viper 1.9.1.

The packaged kernel, with the rom, does not support Quick Charge 2.0.

I have 2 official Qualcom 2.0 chargers, one for home and one for the car.

I'm looking for a kernel that has this ability.

LeeDroid's kernel has usb fastcharge and works with VZW, but I don't believe this is the same thing as Quick Charge 2.0 as its not near as fast to charge as it was on stock.

Any help or advise would be greatly appreciated.

Thank you.
[One (M9) Original Android Development] flar2:
Mine still charges super fast, I tested this extensively when I added USB fastcharge to make sure everything was working correctly.

The charge rate can be affected by things like battery or system temperature. So please check it again. Or it could be something specific to Verizon and this kernel, as I am not sure that HTC included everything we need in the device tree.

Btw, the fastcharge in the other kernels does nothing.

Also, it's very difficult to read the charge rate on this phone, apps like Ampere can't do it. HTC added a ton of convoluted code to the charge driver.
[One (M9) Original Android Development] itzsnookums:
So far, still going
[One (M9) Original Android Development] pmacevad:
That's pretty similar to my results last night, and that was my first charge cycle. Excellent work on this version. Very stable and battery has been great so far.

Sent from the m9...
[One (M9) Original Android Development] sdamark:
Thanks for the quick response.

Judging by your answer, this kernel should be okay to try on my Verizon M9.

It installed fine, booted up, and I'll be giving it a whirl for a day or two.

Thanks again.
[One (M9) Original Android Development] flar2:
I don't know all the things pnpmgr does, but it's very busy.

I'm pretty sure it has a list of apps and modifies performance accordingly.

It optimizes Sense for smooth performance (scrolling through app drawer and notification, and task switching, etc)

It has a big role in thermal management.

It does some network stuff, not sure what.

It is the reason cpu frequencies don't stick (I've always recommended leaving them alone anyway)

It controls powersave mode and high performance mode

If you disable pnpmgr at the wrong moment, you could be stuck with non-optimal settings.
[One (M9) Original Android Development] cyber_system:
Thank you for explaining :) It makes 'Sense' ;)
[One (M9) Original Android Development] TorrentzRock:
I'm just gonna leave this here. The battery if compared to stock... Unbelievable. Thank you SO MUCH! I am interested to see how it performs for me tomorrow when I return to work and my phone has a typical day of usage.

HTC One M9 | ARHD
[One (M9) Original Android Development] Nekromantik:
I flashed this on IC ROM and now I cant boot my phone.

Starts up with HTC logo and keeps restarting.

I used the Elemental x Kernal Manager to download 0.3
[One (M9) Original Android Development] Anzinger:
Same for me with viper 191
[One (M9) Original Android Development] flar2:
There are two others who can't boot. I don't know why, none of my changes are risky.

If you can get the kernel log during boot up, I would appreciate it. That's the only way for me to figure out the problem.
[One (M9) Original Android Development] flar2:
You're number 4

Were you able to use version 0.2?
[One (M9) Original Android Development] Nekromantik:
Not tried 0.2, 0.1 was fine though.

I cant get a kernel log at the moment. Need my phone as im expecting some calls.
[One (M9) Original Android Development] TorrentzRock:
I am by no means a dev, however I do see a trend here. If memory serves me correct, no one running ARHD is having an issue. Could it be something that Mikes rom has (or doesn't have) that is different from these other roms that are having trouble?

HTC One M9 | ARHD
[One (M9) Original Android Development] flar2:
ARHD is really close to stock. Others are successfully running it on Viper. I think there are a couple possiblities: hardware variations, or some weird combination of settings in IC/Viper
[One (M9) Original Android Development] Quadrider10:
im on ARHD and have 0 issues

As far as the 2nd cluster, it is hitting 1958MHz even though it says 1556. when i launch the elemental app, i see it spike up real quick.
[One (M9) Original Android Development] flar2:
To the guys with the bootloops:

Do you have dotview? Or are you disabling magnetic cover event? That always caused weird issues on m8.

Also, what is your firmware version?
[One (M9) Original Android Development] flar2:
I downloaded three different version of the source from htcdev and there were hardly any changes from .6 to .15 and no changes at all from .15 to .15r1

I'm using this test kernel based on .15r1 source code with the stock .6 base that came with my phone. If this doesn't work on .17, it's probably just a matter of updating the ramdisk.
[One (M9) Original Android Development] p50kombi:
At the moment your kernel is running lovely and smooth with ARHD 4.1

Can't wait for you to start throwing in your goodies and then moving onto your new elementalx app... :)
[One (M9) Original Android Development] aooga:
[MENTION=4684315]flar2[/MENTION] Awesome...glad to have you here for the M9!

When you say international only, is there something that doesn't work with the Tmobile variant that you know of? The most current software for the tmobile one is 1.32.531.33.
[One (M9) Original Android Development] flar2:
I have no idea. You could do a backup of system and boot and try it.

The updater script is copying the kernel to the device by named partition rather than a specific partition, so there should be no risk.
[One (M9) Original Android Development] guidogsbn:
Nice to see your development here. It will of course be an interesting time of testing now. That makes me really happy. I just want to change to the main international firmware tomorrow.:good:
[One (M9) Original Android Development] aooga:
Thanks. I can confirm it works on the most current tmobile software!
[One (M9) Original Android Development] frankcck:
It also works on AT&T.
[One (M9) Original Android Development] flar2:
AT&T is usually the same as the international ones. I'm pretty sure it's identical to the major Canadian carrier versions. I'm never sure about t-mobile. Verizon and Sprint are always different.

Basically, this should work on everything except Verizon and Sprint
[One (M9) Original Android Development] motoelliot:
Crap... Was hoping for some sprint love soon...
[One (M9) Original Android Development] peca_slo:
Is your app also working on M9?
[One (M9) Original Android Development] flar2:
Yes, and when it is re-released it will have full octacore support
[One (M9) Original Android Development] kangconsumer:
Can i use your app also with other kernels? Does it have the same features like trickster mod or kernel adjutor app?

If yes i'd like to support your efforts
[One (M9) Original Android Development] j to the 4n:
..about time you appear (-:
[One (M9) Original Android Development] Cryosx:
I'm curious to see what kind of performance and battery life we can get if we overclocked the A53 cores and disabled the A57 cluster.
[One (M9) Original Android Development] timsah:
Very glad to see you here and getting your hands on M9. :good:

I can't wait to get the app with the new design. :)
[One (M9) Original Android Development] itzsnookums:
I was also wondering
[One (M9) Original Android Development] flar2:
The phone was just released in Canada, so I couldn't get it until now.
[One (M9) Original Android Development] frankcck:
[MENTION=4684315]flar2[/MENTION]

FYI, while I was listening Youtube in background and reading Tapatalk and chatting in hangout, my phone was laggy and music was stuttering.

After changed back to stock kernel, had no problem in same situation.

It might be related to governor, you certainly know that better than me ?

Anyway, really happy to see you here even though the poll you made in Google+ was...... ?

hTc one M9 LET THEM STARE
[One (M9) Original Android Development] timsah:
Since when is Canada a third world country :p

I also had some laggs in multitasking.
[One (M9) Original Android Development] CWick4141:
Glad to see you here... Loved your kernel on the N5/N7...Then I switched to the note series and missed the performance
[One (M9) Original Android Development] Nekromantik:
Not got dot view, not disabled mangnetic cover.
[One (M9) Original Android Development] matteh80:
I have dotview.

I also tried on ARHD with the same result. Flashed your kernel right after rom.
[One (M9) Original Android Development] flar2:
I didn't think it had anything to do with dotwiew or the magnetic sensor.
[One (M9) Original Android Development] matteh80:
Firmware version: 1.32.401.17
[One (M9) Original Android Development] C.H.T.J.:
Should i turn pnpmgr on or off ? What is better ? Thanks for help...
[One (M9) Original Android Development] TorrentzRock:
Did you let the rom do a full boot before flashing kernel?

HTC One M9 | ARHD | ElementalX
[One (M9) Original Android Development] brittoking:
Short answer... No don't turn it off

http://xdaforums.com/showthread.php?p=60959254
[One (M9) Original Android Development] C.H.T.J.:
Okay so just let it like IT is on the Screenshot? Thanks
[One (M9) Original Android Development] brittoking:
I just meant follow flars directions would probably be best

"I don't know all the things pnpmgr does, but it's very busy.

I'm pretty sure it has a list of apps and modifies performance accordingly.

It optimizes Sense for smooth performance (scrolling through app drawer and notification, and task switching, etc)

It has a big role in thermal management.

It does some network stuff, not sure what.

It is the reason cpu frequencies don't stick (I've always recommended leaving them alone anyway)

It controls powersave mode and high performance mode

If you disable pnpmgr at the wrong moment, you could be stuck with non-optimal settings."
[One (M9) Original Android Development] jollywhitefoot:
Just thought I would post a report after 2 days of light usage.

The kernel is incredibly stable and smooth and battery life has been fantastic, although usage has been extremely light so far. As you can see from the screen shot, very little screen on time, but over 33.5 hours on battery and apparently I still have another 1:45 of battery time.

For what it's worth, I'm on AT&T and the latest Insert Coin (1.6.0 revision 9).

edit: [MENTION=4684315]flar2[/MENTION], spoke too soon on the bootloops. About an hour after making this post, my battery died and when I plugged it in, I got bootloops. I'll work to get you a good log if I can reproduce it. I installed your kernel on Saturday shortly after you released it. It booted and ran fine after initial install.

The bootloops happened on the HTC One animated screen. I'm not really familiar with getting logs, so any advice would be appreciated. ADB driver is usually pretty dependable on my laptop.

Edit 2: I can't get another bootloop to occur. I dirty flashed Insert Coin booted the device, rebooted to recovery, installed the .3 kernel, and the device booted fine. I've rebooted about 5 more times and it boots perfectly every time. Maybe the bootloops were because my battery was dead even though I was plugged in?
[One (M9) Original Android Development] Anzinger:
I have fw 13240117 and dot view. I dont try Version 02 but with 01 i had no bootloop
[One (M9) Original Android Development] Johnny424:
Delete
[One (M9) Original Android Development] flar2:
It was probably your battery or some other one time thing. The bootloops are only affecting a few people, and they are unable to run the kernel at all. If it boots, as it does for 99% of users, it will be perfectly stable.
[One (M9) Original Android Development] iElvis:
Have definitely noticed an improvement in battery life on 0.3 over 0.2. Now let's get those CPUs under control. :cool:
[One (M9) Original Android Development] flar2:
Can you try version 2?

https://www.androidfilehost.com/?fid=23991606952606477
[One (M9) Original Android Development] 030575753:
both 0.1 anf 0.2 work fine.

0.3 is after the red word, black screen then vibrate and reboot again
[One (M9) Original Android Development] Anzinger:
No Problem with 02
[One (M9) Original Android Development] matteh80:
I tried installing ARHD again...

After "Android is upgrading" I get some error messages:

- unfortunately system ui has stopped

- unfortunately easyaccessservice has stopped

- unfortunately htc dot view has stopped

Then the phone stays at "Unlocking your SIM card and setting up your phone".

I rebooted into recovery and flashed unsecured BOOT from Viper and the Rom boots without a problem. The same with LeeDroid kernel.

I know I had the same problem with Viper ROM when I choose the "Stock" option in Aroma instead of setting up the ROM with the best "Viper options".
[One (M9) Original Android Development] lolpos:
Running elemental 0.3 for a day now. All stock settings, with elementalx as governor. Everything works great and is smooth. I have the htc rapid charger 2.0 and it works just as fine (fully charges my phone in about one hour to one 1/2hour) I did not turn on fast charge. Im on tmobile variant using latest tmous fw along with viper 1.9.1
[One (M9) Original Android Development] Quadrider10:
do N RUU and do not wipe anything this time except when installing ROM from aroma when it asks you.
[One (M9) Original Android Development] flar2:
That narrows it down, I'll send one or two test versions tonight and we'll see the problem
[One (M9) Original Android Development] :
Hey [MENTION=4684315]flar2[/MENTION], I'm loving your kernel. Is there any way you could look into getting wifi calling to work with other roms? I'm stilling running your kernel with Viper 1.9.1 even though it breaks wifi calling... it's that good!
[One (M9) Original Android Development] matteh80:
Awesome!
[One (M9) Original Android Development] TwinAdk:
Fastcharge (qualcomm chargers, not ac charge on usb), has been reported not working, with viper ROM specifically, check the thread.

Viper 1 9 1 here, international m9 on secure boot and no dot view cover. No problems at all, been here since 0.1, loving it!!

Kind Regards

TwinAdk
[One (M9) Original Android Development] ahrion:
QC 2.0 works fine for me?
[One (M9) Original Android Development] Doughnut643:
I have WiFi calling working and elementalx .3 working on viper 1.9.1 ?

Try doing a clean install, let it boot up, make a backup, then flash ex and wipe caches

Update: quoted wrong person. I hope my point gets across. Great job on the kernel, flair2. I'm glad to see you again (me coming from a nexus 5)
[One (M9) Original Android Development] sdamark:
Just reporting back in. After 1 day of use (barely enough time to settle), I'm getting great battery life (5+ hours screen on time), Quick Charge 2.0 seems to be working great (came up 75% in just under an hour), and my phone is running fine as frog hair. Thank you [MENTION=4684315]flar2[/MENTION] great job. :good:
[One (M9) Original Android Development] flar2:
Here is the first test kernel for those who could not get version 0.3 to boot:

elementalx.org/uploads/test_a.zip

Let me know if it works.

Others: there is no need to flash this. There is nothing new
[One (M9) Original Android Development] brittoking:
Darn nothing new! Haha
[One (M9) Original Android Development] BUBBA DUB'S:
[MENTION=4684315]flar2[/MENTION] , HTC posted the source code for the m9 kernel on their site for download. I don't know if that would help you with development, but I figured I would share (if you didn't already know).

http://www.htcdev.com/devcenter/downloads
[One (M9) Original Android Development] Anzinger:
Here is the first test kernel for those who could not get version 0.3 to boot:

elementalx.org/uploads/test_a.zip

Let me know if it works.

Others: there is no need to flash this. There is nothing new

Same Problem, bootloop
[One (M9) Original Android Development] flar2:
I will upload another one tomorrow
[One (M9) Original Android Development] bzhmobile:
+1, no problem on V003 with Pyrana's Rom on Intl model (no changes in Aroma)...
[One (M9) Original Android Development] ahrion:
I get bootloops but I restart until the device boots.

The errors I get are usually zygote errors or schedule boost errors. I know this because I use Liveboot.
[One (M9) Original Android Development] matteh80:
Is this log of any use to you?
[One (M9) Original Android Development] sirioo:
Thanks for the quick response.I hope it is possible..!!
[One (M9) Original Android Development] flar2:
You mean it does eventually boot if you keep trying?

My next test will reuse the existing ramdisk, I think that will solve the problem. I have a baseball game tonight, so maybe late tonight.
[One (M9) Original Android Development] matteh80:
Nope. Doesn't boot at all for me.
[One (M9) Original Android Development] grim489:
Wi-Fi calling works for me and I have viper 1.9.1 with this kernel.

Nope, I was wrong. I could've sworn I had installed this kernel. Sorry about that. :/
[One (M9) Original Android Development] Alcolawl:
[MENTION=4684315]flar2[/MENTION], loving the app and the kernel so far. I have a quick question, however. Would there me a way to split the CPU Times Table (The table that shows how much each frequency has been used by the CPU) between the two clusters? Right now it merges both clusters into one table, but it'd be interesting to see how often the big CPU cluster has to step in and help out.

I'm running the latest LeeDroid and this Kernel and Wifi calling works just fine. Just called my house phone to test, because you guys were starting to make me doubt myself lolol.
[One (M9) Original Android Development] donmarkoni:
Until [MENTION=4684315]flar2[/MENTION] makes it available in his app, you can check /sys/devices/system/cpu/cpu4/cpufreq/stats/time_in_state ;)
[One (M9) Original Android Development] flar2:
Actually the cpu times are for the first cluster only. For the second cluster, the stats are erased and start over each time it goes offline (which is every time the screen turns off)
[One (M9) Original Android Development] ahrion:
Yes. I noticed that if I use liveboot I cab see what's going on. I keep getting "retry" and "attempt", but usually I just hardware reset until it boots.
[One (M9) Original Android Development] colorprint:
With 1.40 firmware this kernel makes my phone to reboot when I try to turn it on with power button after sleep.

Same problem with some other custom kernels.

Fixed only with /boot partition restore to stock kernel.
[One (M9) Original Android Development] Quadrider10:
Could voltage control be an option? I see that my CPU hits52c sometimes. Same with battery.
[One (M9) Original Android Development] flar2:
I'm sure this will be a continuing problem. HTC is a major pain to develop for.

I'm probably not doing voltage control, as the latest chipsets typically manage voltages better than users can. Not only that, but there is little to no benefit in undervolting the latest chipsets because the voltages are already very low.
[One (M9) Original Android Development] :
It is all good. I can deal with wifi calling being broken, but if it would work that would be a huge plus! :)
[One (M9) Original Android Development] flar2:
I don't think wifi calling has anything to do with the kernel actually. It's userspace stuff, and dpending on your carrier, could be very strict about working with anything other than a stock setup.
[One (M9) Original Android Development] :
On Viperrom 1.9.1 if you stay with the kernel that comes with it, wifi calling works. If you flash any other kernel it breaks. This is what [MENTION=4905624]j to the 4n[/MENTION] said about it, It's the screen shot.
[One (M9) Original Android Development] flar2:
Someone else said wifi calling worked fine with this kernel.

I don't see anything on thicklizard's github page about wifi calling and don't see how it is related to the kernel. It's userspace stuff as far as I know.

I do know that some carriers don't allow it to work with anything other than a stock configuration. Viper uses the stock kernel and is based on the stock ROM, so maybe that's close enough to work.
[One (M9) Original Android Development] colorprint:
no, the problem persist even it was cold (about 40C)
[One (M9) Original Android Development] DroidShift79:
Is it somehow possible to implement zzmoove governor which is known in i9300 world?
[One (M9) Original Android Development] Asselalf:
ElementalX governor is good for the QSD810. No need for other governors

Gesendet von meinem HTC One M9
[One (M9) Original Android Development] grim489:
Okay now my Wi-Fi calling is working. It was giving me a reg 90 error until now. On viper one 1.9.1
[One (M9) Original Android Development] flar2:
Next test for those who can't boot:

elementalx.org/uploads/test_b.zip

This must be flashed over a working kernel for your ROM. It re-uses the existing ramdisk.

I would like others to test it as well, I'm thinking of going this way even if it doesn't solve the no-boot problem.

There is nothing new in this kernel, only flash if you want to test and give feedback on the new installer.
[One (M9) Original Android Development] Johnny424:
One issue I have noticed is the changes to ex gov. Via ex app settings do not stick or survive a reboot. Changed upthreshold and one other for both sets of cores but it returns to default after boot. Pnpmngr at play flar?
[One (M9) Original Android Development] BUBBA DUB'S:
I'll give her a whirl, just flash over existing v.3? Backed up and ready to flash.
[One (M9) Original Android Development] flar2:
They won't stick on the second cluster. It resets as soon as the cluster goes offline (when screen is off)

It's a huge job adapting it to work with clusters, I still have a lot of things to fix.
[One (M9) Original Android Development] flar2:
Yup, flash over 0.3 will work (as long as 0.3 works)
[One (M9) Original Android Development] Johnny424:
Not complaining at all. Just doing my job as a user and reporting anything I see. Kernel runs flawlessly but just thought I'd bring it up. My settings also reset on the first cluster as well. No bigger though as I said everything works and feels awesome without any changes
[One (M9) Original Android Development] flar2:
Probably not. I don't add exotic governors, especially ones designed for other devices. I will instead work on interactive and elementalx to optimize for this device.
[One (M9) Original Android Development] flar2:
Oh yes, they probably won't apply on boot because I have to delay seeing the gov to elmentalx because the system forces interactive. HTC always makes things difficult
[One (M9) Original Android Development] BUBBA DUB'S:
Just flashed, no problems , booted up as normal. I haven't installed your app yet and don't use any other kernel app, but let me know if you want me to look at anything specific.