yashsingh1/xdaforums huggingface dataset:
[HTC Droid DNA] jbarcus81:
Got it.. Thanks! Couldn't remember if crpalmer's had the same or not..
[HTC Droid DNA] rfarrah:
Had a couple of random reboots. Back to stock for now.
[HTC Droid DNA] orangechoochoo:
I haven't had any random reboots but when I reboot 50% of the time it hangs on the boot animation.
[HTC Droid DNA] -DroidIsDNA-:
Battery seems better than 2.0, but not quite at 1.2.6. That being said, battery life is still a full day. I got to about 26 percent and had to plug it in, whereas on 1.2.6 it was consistently about 45%. Not bad at all man! Performance is like a train with no breaks and without tracks.
[HTC Droid DNA] spinkick:
2.03 seems solid. Runs cooler to me. Anyone else ?

---------- Post added at 10:02 PM ---------- Previous post was at 09:52 PM ----------

Also, how much does overclocking to 1.73 affect battery? Is it a huge drain? I dont know if I can tell the difference between 1.51 and 1.7, but if its not much of a difference battery wise, why not? What do you guys think?

---------- Post added at 10:03 PM ---------- Previous post was at 10:02 PM ----------

What clockspeeds are you running?
[HTC Droid DNA] -DroidIsDNA-:
Im 192/1.5. No overclock. My voltages are as low as i used on 1.2.6. Actually, i overclocked 1.2.6, that's what makes that version's battery life so good...
[HTC Droid DNA] crpalmer:
If you have a problem, you need to grab /proc/last_kmsg. There's nothing I can do without it.
[HTC Droid DNA] crpalmer:
Getting /proc/last_kmsg would help for that as well.
[HTC Droid DNA] rfarrah:
Not sure I know how to get that for you.

Honestly, it seems like I've had trouble with every non-stock kernel since the OTA/update. It could easily be something in my system. When the next Viper version is released, I plan to wipe everything and start over - maybe that will help. In the meantime I'll keep giving these a try. No harm done.

Thanks again for developing for us!
[HTC Droid DNA] CharliesTheMan:
If you ever need help just let me know and I can make sure you're adb and drivers are setup correctly and walk you through it so you can learn along the way.

If your ADB is already working everything else is a breeze.

http://xdaforums.com/showthread.php?t=1726238
[HTC Droid DNA] spinkick:
Get a program called lumberjack, it makes it easy to get your last k_msg file.
[HTC Droid DNA] rfarrah:
Thanks, guys. Just tested Beastmode as well. Same bootlooping experience. I'm sure it must be something I've done with my current setup. Will reset everything when the new/updated Viper drops.
[HTC Droid DNA] crpalmer:
It probably a script that some app has dropped into your init.d...
[HTC Droid DNA] rfarrah:
That should be fun to find. :p
[HTC Droid DNA] orangechoochoo:
Just my luck, I rebooted five times in a row to get the error but it booted fine.
[HTC Droid DNA] iOSh8er:
Boots fine for me. -.75 across the board. Seems slightly sluggish on Sense 5 (with and without undervolting). Not as bad on Viper. Thanks for the update!

Please don't touch my "Thanks" button, it doesn't like you... ;)
[HTC Droid DNA] almania6:
Anyone having a problem with it bootlooping ? Mine usually bootloops for a while then it boots then when I reboot it does the same thing again
[HTC Droid DNA] Zarboz:
Crpalmer the voltage hack you reverted can be useful if you just add the voltage to the tables and the settings of min max freq in cpufreq.c set safe booting variables rather than ramping max clock on boot maybe why people are having a hard time
[HTC Droid DNA] crpalmer:
The voltage hack just adds 25mV to all the frequencies. That wasn't a problem before the 2.04 source drop and I'm not sure why it would suddenly be a problem for the same hardware....

I really should limit the frequencies on boot but it's not that likely to be a problem. The phone bounces around between frequencies a lot during the boot (spending less than 25% with a core at 1.7GHz. It's really only likely a problem if someone can't tolerate 1.7GHz at all. If that was the case, I doubt it would get past firing up the cores in the first place (definitely not long enough to appear to boot loop).

I was also a little worried about a thermal problem (the driver doesn't kick in immediately on boot) but the temperature wasn't anywhere close to a problem range on a boot or two.

Of course, if someone has problems and uploads/PMs a /proc/last_kmsg, that might help one way or the other.
[HTC Droid DNA] orangechoochoo:
Does increasing the read ahead buffer size from 128 to a higher number make much of a difference with our phones since we don't have an external ad card?

I also noticed the go_hispeed load in the governor settings of interactive are different: crpalmer uses the stock figure of 99 and Zarboz uses 50. Is there an advantage to having it set to 50?
[HTC Droid DNA] -DroidIsDNA-:
I'm only seeing a min of 384 on this build.
[HTC Droid DNA] rfarrah:
Yup, I had to give it up. But it looks like several people are having good luck with it.
[HTC Droid DNA] crpalmer:
I played with the readahead at one point and couldn't tell any benefit to changing it.

Zarboz's setting would make it more aggressive to ramp up to max frequency.
[HTC Droid DNA] orangechoochoo:
Thanks, Z keeps it at 128 too, so it looks like the consensus amount kernel devs is to keep it stock.

Also, I've rebooted the phone several more times and it doesn't hang at the boot animation anymore.
[HTC Droid DNA] CharliesTheMan:
I did read/write testing bumping the sd read ahead cache and my read write speeds increased a good bit up to 1024 but above that there wasn't any improvement. But I'm constantly downloading and transferring files back and fourth to my SSD. I think there's so many setup variables that it would be an individual decision.
[HTC Droid DNA] KyJelly69:
Mine shows 2048 after installing zarboz's
[HTC Droid DNA] CharliesTheMan:
A lot of roms do that with a hot reboot, the hanging at boot animation. Not sure what Rom you're running though if its not a sense 4+ Rom that's not the issue.
[HTC Droid DNA] orangechoochoo:
What I mean is it didn't get past the boot animation no matter how long I wait, but that was within the first hour of flashing the kernel.

Since then I've gone back and forth between this and Z's kernel and not had that issue. Crpalmer wanted a last_kmsg so I purposely rebooted several times but I couldn't get the error.
[HTC Droid DNA] spinkick:
Getting a lot better battery on this build it seems. Performance feels good!
[HTC Droid DNA] CharliesTheMan:
What about if you do a hot reboot instead of regular reboot.
[HTC Droid DNA] del9800:
She sleeps so nice. Thanks crpalmer for great kernel.

Sent from my HTC6435LVW using Xparent Red Tapatalk 2
[HTC Droid DNA] orangechoochoo:
Got a reboot

http://db.tt/sd64Uepy
[HTC Droid DNA] keithce:
Been running brilliantly. Definitely seen improved battery life over 2.0.

Thank you!
[HTC Droid DNA] crpalmer:
The kernel version in that last_kmsg is:

Linux version 3.4.7-g6b5c34d

which is definitely not mine (mine is based on 3.4.39)! Did it reboot into recovery and then you rebooted back to the ROM before pulling the last_kmsg?
[HTC Droid DNA] axeldiks1:
Which one would you guys choose for battery life this one or beatsmode?
[HTC Droid DNA] orangechoochoo:
Yes :( I noticed the kernel info too. I was previously running Z's 5.5 but since it was a new day I decided to flash yours. It booted fine so I left the phone on the couch and when I came back the boot animation was showing. I rebooted and it started fine so I used lumberjack to pull the kmsg hoping the error would still be there.

Is a new kmsg is generated every reboot?
[HTC Droid DNA] axeldiks1:
If you are on sense 5 Rom glad7 m7 stock kernel wipe cache dalvik and then flash this , worked for me
[HTC Droid DNA] orangechoochoo:
That's usually what I do, for some reason 2.0.3 hangs on the boot animation during the first couple of reboots, then it's completely fine after that no matter how many times I manually reboot.
[HTC Droid DNA] crpalmer:
New version posted. Mostly aimed at the people that are having issues with bootloops or hanging boots. I don't know that it's going to change anything (I haven't had any problems myself), but the changes are generally good anyway:

Version 2.0.6: April 17, 2013: boot changes, linux 3.4.40:

* Linux 3.4.40 (upstream).

* Limit CPU speeds during boot to stock speeds.

* Enable the thermal driver 5 seconds into the boot (previously was 30 seconds).

* Small changes to the ramdisk from the 2.04 update (I forgot these before).
[HTC Droid DNA] rfarrah:
I'll give that a shot and report back.
[HTC Droid DNA] ML417:
So I flashed 2.0.6 and managed to get past the boot animation without bootlooping, though it's still a bit rough. Also, my phone felt warm after boot so I checked and the temperature shot up to 40C on boot to this kernel, which it does not do with Z's kernel as I booted a few minutes before flashing this kernel and the graph shows that it did not spike (or get that high) until I flashed this. I'm grabbing logs and will upload shortly.

EDIT: https://www.dropbox.com/s/3qvqqrb1uic0s6i/logs4-17.zip

it has the logcat, the radio logact, and the last_kmsg because I wasn't sure which one it will show up on.

I hope you can find the reason for the temperature spike.

EDIT2: I just tried OCing and my phone did not reboot from 1.7GHz. The most I could get from Z's was 1.53GHz. Now if we could only get the good parts of both your kernels my phone would be very happy.
[HTC Droid DNA] flyinj54:
Everything running great here on newest 2.0.6. Thanks!
[HTC Droid DNA] ML417:
I spoke too soon. I think my phone decided that 1.7GHZ was too much. here is another log for your evening read.

https://www.dropbox.com/s/kwrvozbrf35c0pz/last_kmsg4-17.txt

EDIT(I know I'm doing this a lot tonight): so, it didnt like 1.67GHz either. It didn't crash, but I lost the touchscreen for some reason.
[HTC Droid DNA] orangechoochoo:
No stoppage at boot animation!
[HTC Droid DNA] monkboy24:
Finally your kernel has booted for my device long enough for me to pull a log :D tried to Oc to 1.7 and got a black screen with lines in it. At the same time this build feels very snappy at 1.6ghz but I know that my phone can handle 1.89ghz. Something might be going on with 1.7ghz on this kernel:o here's the log http://db.tt/oZfReIpe
[HTC Droid DNA] rfarrah:
Mine has been running smooth all evening. Haven't yet set up SetCpu.....
[HTC Droid DNA] del9800:
I've noticed that setcpu has been giving me that hanging on splash screen and others problems not mentioned. Has anyone that has had problems tried kernel tuner?

Sent from my HTC6435LVW using Xparent Red Tapatalk 2
[HTC Droid DNA] ML417:
I know that crpalmer uses setcpu which is why I was using it as well.
[HTC Droid DNA] del9800:
Not all phones are created equal.

Sent from my HTC6435LVW using Xparent Red Tapatalk 2
[HTC Droid DNA] crpalmer:
Kernel Tuner caused all sorts of crazy, hard to figure out, strangeness in the settings of the different cores. I do not recommend using it with my kernel.
[HTC Droid DNA] CharliesTheMan:
I can confirm similar findings with kernel tuner. Its like its causing problems, especially with hot plugging governors, with either mpdecision or hot plugging or something like that.
[HTC Droid DNA] del9800:
So what are you guys using to configure voltage?

Sent from my HTC6435LVW using Xparent Red Tapatalk 2
[HTC Droid DNA] rfarrah:
Loaded up 2.06 late yesterday and ran it with no problems at all overnight and this morning. Then I installed SetCPU.

Initial settings came up as 192/192. Managed to set it to 1512/384 before it reset and rebooted itself. Ran okay for about an hour then the phone locked up completely. Forced reboot and immediately disabled SetCPU. Seems to be running okay since then, but the "sync" icon in the status bar hasn't gone away.

UPDATE: Sync icon did eventually go away.
[HTC Droid DNA] yearn2burn:
System Tuner also does voltage. If I remember, that was LK's go to CPU tuning app.
[HTC Droid DNA] CharliesTheMan:
I haven't tested android tuner yet but its a nice app in general.

If somebody wants to test it, the app developer has gotten to be a pretty good friend of mine and if you give me a heads up on the symptoms we can see about figuring out the issues and solving it.

I've just been crazy busy in real life and spending my android time working on a brand new Rom along with helping with some existing stuff.
[HTC Droid DNA] spinkick:
I run system tuner pro and it works great with no issues.
[HTC Droid DNA] rfarrah:
I've had nothing but bootlooping with all versions of both this and Zarboz's kernel.

I've stated before that I don't blame the devs or their work and that I suspected it was something I've screwed up or set up or installed on my phone.

Based on spinkick's recommendation above, I downloadeed System Tuner (free) to give it a shot managing this kernel - and so far it is working great!

At this point in time it appears as though it may have been SetCPU that was causing all the trouble for me.

...just thought I'd post this in case others found themselves in a similar situation.
[HTC Droid DNA] ML417:
If you think you're having problems with an app, try uninstalling it and flashing the kernel without any app
[HTC Droid DNA] CharliesTheMan:
In my opinion the best thing you can do is run the kernel without a control app at all when it's possible as a permanent solution but at least just for testing
[HTC Droid DNA] djh816:
Which governor would I use to have the new mpdecision? Also are there plans to work on the msm-dcvs governor?
[HTC Droid DNA] orangechoochoo:
Mpdecision is built in, it's not specific to a governor. Regarding msm-dcvs, there are no plans since it can't be overclocked.
[HTC Droid DNA] djh816:
Thanks, appreciate it. Any technical reason msm-dcvs isn't overclockable? Just curious.
[HTC Droid DNA] CharliesTheMan:
MSM-DCVS

MSM stands for the prefix of qualcomm's SOC, and DCVS stands for Dynamic Clock and Voltage Scaling

(Geez this is hard to put into words and when someone corrects my poor definitions I'll edit this post)

The reason it can't be overclocked like a standard governor is because it has so many default settings because of that Dynamic Clock ability, so from second to second cpu freq tables are changing, instead of the static ones where once they've been set they stay that way.

In my humble opinion the governor would have to be completely rewritten, after being reverse engineered. And it would probably need to be set for max frequency, so if a kernel was set up with msm dcvs scratch built you wouldn't be able to change the max frequency because as soon as it got a load on it, it would basically out think whatever what trying to control it. Think if it as the stubborn governor lol.
[HTC Droid DNA] orangechoochoo:
I also don't think the source for that governor is available. It is a Qualcomm creation.
[HTC Droid DNA] azndan2:
Hi crpalmer,

I am on Nos m7 2.0. Volume wake is enabled by default. Once I flashed your kernel, it seems that volume wake doesn't work on deep sleep. Is there a way to fix this or do I have to go back to the stock kernel in order to keep volume wake?

Thanks,

Daniel
[HTC Droid DNA] spinkick:
How's people's battery life?
[HTC Droid DNA] del9800:
19 hrs 3+ hrs of screen on no WiFi. My opinion kernel is great. But I do undervolt...

Sent from my HTC6435LVW using Xparent Red Tapatalk 2
[HTC Droid DNA] flyinj54:
I'm consistently on WiFi and last two charges I've managed to get two hours screen time with 30+ hours before charge. Pretty amazing work. I am running low min 192mhz on demand and overclocked just a bit on top
[HTC Droid DNA] keithce:
Great! No complaints
[HTC Droid DNA] wpsantennas:
Bob

wpsantennas.com
[HTC Droid DNA] del9800:
Wow I'm impressed... Share settings if you don't mind.

Sent from my HTC6435LVW using Xparent Red Tapatalk 2
[HTC Droid DNA] spinkick:
I think bob turns of automatic data sync and whatnot right? I need push email etc for work.
[HTC Droid DNA] wpsantennas:
Actually, I have auto sync and background data enabled so that most stuff is able to sync whenever it wants. I don't go overboard with background data but likewise I don't want to hamper the phone's functionality. In the case of e-mail I do have it set to manual sync as I tend to check it frequently anyway.

I'm running the stock rooted 2.04.605.2 ROM with a few tweaks and a few apps removed and the newest radio. I never run WiFi but I generally always have great LTE signal strength. As long as I've been running either DSB's, Elkay's or this kernel I've had very good battery life. On this kernel, I'm running 192 min, 1.5 max, default governor, undervolted 50mv.
[HTC Droid DNA] crpalmer:
What version did you have problems with? Originally, I just slapped in dsb's ramdisk and it contained something (I forget what) related to volwake. I cleaned that up a fair while ago and I don't know of anything that I've changed related to that.

If you are trying a recent kernel, you could try sending a dmesg output after trying to wake it to see if there is anything meaningful in there.
[HTC Droid DNA] crpalmer:
New version posted. This is mostly just a linux patch update to 3.4.41:

Version 2.0.9: April 23, 2013: 3.4.41 and small fixes:

* Linux 3.4.41

* Small fixes from CAF

* Clean up some more HTC crap in the kernel

I did also update the instructions for flashing this to say that you should wipe cache before flashing this kernel. I'm not sure why, but with all the 1.15 kernel work I did, I never had a problem but now with 2.04 I am seeing hangs sometimes when booting after flashing a new kernel. So far, I haven't seen a hang after wiping cache and flashing a new kernel.
[HTC Droid DNA] orangechoochoo:
It's never perfect. I love the fact that you and Zarboz continually tweak your work, I look forward to your guy's posts :good:
[HTC Droid DNA] johnwaug:
I agree. It seems like every evening I get to flash something new. No matter what anyone else writes we are lucky to have such great developers. Thanks cp for the update. I am sure it is as terrific as all the other work you have done.

Sent from my newtorooted Droid DNA 5
[HTC Droid DNA] spinkick:
Bob, I can confirm that as well. I'm overclocked to 1.7 and 192mhz

https://www.dropbox.com/s/yx0hwudebc4xquj/2013-04-23 21.44.01.png
[HTC Droid DNA] azndan2:
Thanks for responding. Could you be a little more specific on how I can get a dmesg output?

Also, is there a reason that I couldn't select the MSM DCVS governor from setcpu when I was on your kernel? (2.06)

Thanks!
[HTC Droid DNA] crpalmer:
From a command prompt that can access adb:

adb shell dmesg > dmesg.txt

and then post a link to the file dmesg.txt that was created.

That is HTC proprietary code that is not released and I can't build it.
[HTC Droid DNA] keithce:
[MENTION=3857343]crpalmer[/MENTION]

It seems like with this latest update that the Wi-Fi speed has slowed to a crawl. I used to be able to update and download apps from the Play Store at 1-2 MB/s and now it crawls along at 100KB/s.

I did clear the cache and dalvik cache before installing the kernel as you suggested. I've normally cleared it after install before booting for the first time without any issues.
[HTC Droid DNA] orangechoochoo:
That's odd, I notice my WiFi seems to be snappy today.
[HTC Droid DNA] crpalmer:
There weren't any changes to the network layer in this release of the kernel. Maybe the play store is just being slow? I feel like I've seen a few comments in different threads about it being slow.

To confirm that it's not really a problem, run a speedtest on your phone and on another device attached to the same access point to see if there is a significant difference between the two.
[HTC Droid DNA] jbarcus81:
Maybe I should have skimmed more through the thread.. and if it's in the OP I missed it.. But when you state "removing more HTC crap" .. What exactly are you talking about?? I am just wondering what is in there... I know nothing if kernels.. Just that they make my phone sexy.. HA! :cyclops:
[HTC Droid DNA] keithce:
I think you're right. Maybe it was just the Play Store. I just ran the Speedtest.net App and got 22/6 Mbps on Wifi and 11.1/1 Mbps on 4G (in my house which is amazing!)

Thanks for the quick response.
[HTC Droid DNA] crpalmer:
HTC has added a lot of extra random code to the kernel for debugging purposes. I try to remove useless additions as they potentially make it harder to include other fixes and consume extra resources (battery, cpu and/or memory).
[HTC Droid DNA] jbarcus81:
Got it.. makes sense.. Always forget about that debugging code they always include..
[HTC Droid DNA] cbrown245:
Amazing battery life on this last update , on viper 1.2 . Thanks great job
[HTC Droid DNA] rfarrah:
What settings are you using?
[HTC Droid DNA] cbrown245:
Powersave , noop , max freq at 135_ and min at 192.
[HTC Droid DNA] -DroidIsDNA-:
So basically your phone is a paperweight?
[HTC Droid DNA] orangechoochoo:
A good looking paperweight.
[HTC Droid DNA] rfarrah:
He probably just didn't remember the last digit of the max frequency, so he put a blank. So he is actually/roughly 1350 and 192.

That's not a paperweight. :cool:
[HTC Droid DNA] cbrown245:
Its 1350000 I just did put all the 00's but I use it all day with no issues .
[HTC Droid DNA] -DroidIsDNA-:
Hahaha ok, i was gonna say, why the heck would anyone clock so low? Question, what is that watch running apps tab on the pic you posted?
[HTC Droid DNA] crpalmer:
I wanted a baseline for the current cost of my kernel being on but otherwise idle. For kicks I also ran the same test with the stock kernel as a comparison.

My simple test was as follows. I ran my 1.1.5 kernel at 192MHz/1.83GHz with ondemand and compared it with DSB's stock write (because that was the easiest thing to flash on Viper). I turned the brightness down to 0, screen timeout to 30 minutes and left the phone untouched for 30 minutes. To quantify the battery use, I assume that the screen and radio battery consumption will be constant and looked at the ratio between these as an indicator of the relative battery consumption.

Stock used 1.7x more battery when otherwise idle but turned on.
[HTC Droid DNA] eleazar123:
Thanks for all your work on this.

I'm excited to try the bluetooth kernel. Before Venom 1.1.1, I was unable to stream any music via bluetooth except from the stock music player (lots of people having this issue on this forum and rootz).

Anyways, the sound quality of bluetooth streaming on HTC devices has been terrible ever since I tried it on my Thunderbolt almost 2 years ago. (horrible distortion on any high pitch sounds, ie. cymbals, guitar, etc.)

Hopefully the stock bluetooth drivers will help :) I'll give it a shot and let you know how it works out.
[HTC Droid DNA] crpalmer:
New versions 1.0.7 and 1.1.7 are now available:

* Linux 3.4.31.

* Now using the 2013-01 build of the Linaro toolchain.

* Major rewrite of the thermal driver to remove polling (now uses essentially no power).

* Tweaks to the hot-plug driver to reduce CPU consumed to reduce power consumed.
[HTC Droid DNA] jeremy46er:
Re: [Kernel] [Linaro] [Linux 3.4.31] Version 1.0.7 / Bluetooth test 1.1.7 - Feb 15

I'm keeping a close eye on this thread, thanks for your work man.
[HTC Droid DNA] dsb9938:
We know.

We're watchin you, watchin us, watchin you, watchin us. :highfive:

D

.
[HTC Droid DNA] t1gartist:
lol its all true

im flashing your latest 1.1.7 no ill let you know
[HTC Droid DNA] pio_masaki:
Re: [Kernel] [Linaro] [Linux 3.4.31] Version 1.0.7 / Bluetooth test 1.1.7 - Feb 15

OK I can shift to my gnex again, gonna use the updated kernel and see if I still get reboots, I can spend more time debugging it now. Hopefully all goes well, I'll report back as I find stuff and they stuff, just edited it into this post, paste bin the kernel logs etc.

Sent from my HTC DNA
[HTC Droid DNA] lohthx1r:
Re: [Kernel] [Linaro] [Linux 3.4.31] Version 1.0.7 / Bluetooth test 1.1.7 - Feb 15

Hi, does this work on x920d, international version? Thanks.
[HTC Droid DNA] crpalmer:
Re: [Kernel] [Linaro] [Linux 3.4.31] Version 1.0.7 / Bluetooth test 1.1.7 - Feb 15

I highly doubt it.