yashsingh1/xdaforums huggingface dataset:
[HTC Droid DNA] crpalmer:
In replying to this, I just noticed that I had a typo when I added the light table to the build that causes it not to use the brightest level. If you're in very bright light, that might be the problem and I'll push out a new version shortly.

Either way, the brightness will be lower (and even more so because of my brain fart), but the stock settings shouldn't be too dim for the rest of the range. What ROM are you using? Maybe it has its own brightness table already built into it? I'm using Viper 1.2.0 and I prefer a dimmer phone and the "normal" settings are still very bright on my phone..

You can revert back to the original brightness by running this command:

echo 1 3 21 3a1 5a0 15ee 2169 307f 3f96 ffff > /sys/class/optical_sensors/lightsensor/ls_adc_table

from an adb shell (as root, of course). To use the levels that I intended to be set (and what they will be in the next release), you can run:

echo 21 3a1 5a0 15ee 2169 307f 3f96 63d3 ae13 ffff > /sys/class/optical_sensors/lightsensor/ls_adc_table
[HTC Droid DNA] wpsantennas:
Thx! I'm running the stock ROM. I'll try the adb commands when I get back by my PC.

Bob

wpsantennas.com
[HTC Droid DNA] crpalmer:
New version:

Version 2.0.23: May 13, 2013: Lightsensor fix, 3.4.45, faster freq. changes:

* Fix an error transcribing the lightsensor ranges into the source.

* Update to Linux 3.4.45

* cpufreq: use a high priority to target new frequencies to allow faster changes under load
[HTC Droid DNA] Irieone:
To confirm... If your kernel reads my bin as "fast" it will automatically -100 mv across the board? If so, any undervolting I would be doing with Venom tweaks or a 3rd party app would be in addition to the -100 mv set by the kernel?
[HTC Droid DNA] crpalmer:
Yes.

Although, if you've saved voltage settings and are applying them on boot, I would expect all tools to set the values that you had before. That is, if you did -X mV and told it to set on boot, you should have exactly the same voltages before and after this change. However, if you tell it not to set on boot, then you would have (my) -100 mV.
[HTC Droid DNA] fronc:
Auto brightness a little low for my taste, but if I can get used to it, I think it's going to save me mucho on the battery life. Good performance overall.

Any chance we can get Lionheart cpu governor built in? I like that it scales to higher frequencies and seems to use every interval in between.

Send from my Sense 5 Droid DNA...
[HTC Droid DNA] jasoraso:
Default brightness settings were a little too dim for me, too (on Newt's M7 rom). I used the shell commands to revert ...

Thanks for the update.

Jason
[HTC Droid DNA] Irieone:
I'm seeing some screen artifacts when the phone is shutting down. Lines and smeared colors. It just started happening with .20 & .23 kernels.
[HTC Droid DNA] fronc:
Noticing that Nav voice makes music playback all garbled when they occur at the same time, screen on. No longer plays soft while voice speaks.

Send from my Sense 5 Droid DNA...
[HTC Droid DNA] spinkick:
Yep its a little on the darker side for the screen but ill deal if it makes that much of a difference in battery.
[HTC Droid DNA] crpalmer:
Do you mean when powering down or when hitting the power button to turn off the screen?
[HTC Droid DNA] fronc:
Powering down. I see it too. Happens on this kernel and beastmode. Probably has to do with GPU overclocking. I noticed I can't change it off of 487mhz through trickstermod either. Always just resets.

Send from my Sense 5 Droid DNA...
[HTC Droid DNA] Irieone:
Powering down
[HTC Droid DNA] crpalmer:
If you're not happy with the brightness, there are two apps that I know of that have gotten good reviews. Lux (which I think tends to default to being far too bright, so you may like it.... :-]) and Velis Auto Brightness which I'm currently playing with. With more (meaningful) brightness levels, it should be easier to customize the brightness to your liking.
[HTC Droid DNA] wpsantennas:
I'm with others in that I like it a little brighter. I love the kernel, however, so I started playing with Velis Auto Brightness earlier today and it seems to work pretty well. I never tried Lux but I liked how Velis let you pick a starting point that allowed you to choose a base that was reasonably close to what you like. It didn't take me too long to get the brightness dialed in a little better (not *that* bright!) and then some tweaking of other settings so that the brightness changes weren't that frequent/noticeable - i.e. trying to mimic the default brightness on earlier kernels.

Anyway, great kernel, thx!
[HTC Droid DNA] Zer0r:
I am using the same car charger, but with other kernels (for ex. Zarboz) - phone gets up to 900mAh, while with your kernel it stays at 500mAh level (it is accordingly to Battery Monitor Widget info)... I will double check it, because my tests was brief.
[HTC Droid DNA] CharliesTheMan:
Really nice job on the latest build crpalmer. I was thrilled to see you adjusting the default autobrightness values. I've been adjusting my brightness manually due to auto brightness being too bright.
[HTC Droid DNA] Zer0r:
+1!! It makes so easy to create a tweak apk that even will provide GUI for making own autobrightness settings for every ROM!!! All you need - is just this awesome kernel!

---------- Post added at 10:52 AM ---------- Previous post was at 10:04 AM ----------

Strange... I have no strings with PVS in dmesg... Tried both in recovery and system modes...
[HTC Droid DNA] JWhetstone02:
The 2.0.20 update has been wonderful. I charged my phone fully flashed the kernel once I seen it was available and haven't charged back up since

Hope the 2.0.23 update is just as good :)

Thanks

-HTC Droid DNA-
[HTC Droid DNA] ML417:
You can do that with any kernel, and he already mentioned a couple apps that let you do just that
[HTC Droid DNA] Zer0r:
Oops, looks like I missed... Could you point me please?
[HTC Droid DNA] orangechoochoo:
I used to use those autobrightness apps but I stopped because it was draining the battery and wouldn't play nice with some apps
[HTC Droid DNA] Zer0r:
I believe we are talking about different apps. Those autobrightness apps in Google Play Market are working in background and replacing values for the sensor in realtime. The way crpalmer suggests - is replacing the whole table. This way allows to use native system autobrightness without any additional process in memory.
[HTC Droid DNA] orangechoochoo:
Replacing the table instead of having a background app running is preferable.

Lux and the other one crpamlmer mentioned I prefer not to use them.
[HTC Droid DNA] ML417:
Check back a couple pages in here
[HTC Droid DNA] crpalmer:
The auto-brightness is a little bit more convoluted than that. The table that I changed maps the sensor values into a number from 1-10 (well, 0-9, but you get the idea). These bins then get turned back into 10 fixed readings. I think these values are 10, 40, 90, 220, 320, 640, 1280, 2600, inf. Finally, the autobrightness app (either the one built into android or one that is installed) uses the current reading (one of these values) to potentially change the screen brightness.

My changed table just changed the brightness because I shifted the readings slight. The HTC table has the 5th bin at 2% of the light sensor range. That is, basically half of the light readings are under 2%. I changed it to be the same percentiles as the mako kernel which parts the 5th bin at 13% of the light range.

Finally, in terms of battery usage, at least in theory there is no reason why one of the market apps couldn't be as battery efficient as the built-in one as they are both simply reacting to changes in the sensor values.
[HTC Droid DNA] matteebee:
These settings below binned "nominal" random rebooted playing SiriusXM on speaker and browsing blinkfeed.

Log here: http://db.tt/YCA7eHZl

Stay thirsty, my friends
[HTC Droid DNA] crpalmer:
Thanks for the last_kmsg. It is definitely an interesting one! It looks like the reboot was caused by an error interrupt sent from the modem. I see one commit in CAF that might be related. but it's hard to know if it fixes anything if this isn't a problem that is easily reproduced.

Was there any chance that the phone was about to go to sleep when this happened or were you actively interacting with blinkfeed?
[HTC Droid DNA] matteebee:
I don't have any sleep processes and I was just reading, opened an article and it froze and rebooted, no fade out or splash screen.

Stay thirsty, my friends
[HTC Droid DNA] ML417:
Did it freeze while you were opening an article or while you were reading and the screen was about to time out?
[HTC Droid DNA] matteebee:
While I was reading it froze or timed out and became unresponsive, then straight to off (not black) and rebooted.

Stay thirsty, my friends
[HTC Droid DNA] crpalmer:
Unfortunately, there isn't much I can get from the last_kmsg. It looks like the modem threw an error and there is really no other information in the log (the last message was 8 seconds before the error).

If you have another instance of this, please send me another log as maybe the next one will give me more information!
[HTC Droid DNA] Zer0r:
Is there any way to change UV table before installation? It looks like it makes my CPU go crazy. After installation of v.23 I have only one full boot, and then some graphics artifacts becomes to appear, and after that I have continuous reboots... I was testing on clean RageDNA (2.06) ROM. Stock kernel or Zarboz's - works properly. So - this behavior looks very much like excessive undervoltage, as I was observing it before.
[HTC Droid DNA] crpalmer:
Just to confirm, are you binned fast?

Can you grab a last_kmsg from a failed boot? If you're using TWRP, try holding down volume when it's rebooting from a crash to get to the bootloader and then recovery and from there you should be able to get the last_kmsg.
[HTC Droid DNA] Zer0r:
Yes, it is fast. But behavior is very similar - that is why I made this assumption.

Ok, but will be able to do this in 4 hours. Thanks a lot for your help! :D
[HTC Droid DNA] hawknest:
Just thought I'd share ...

Went to bed with 63% woke up with 63%

Edit: I'm still on 2.0.17 version of the kernel

Sent From My EclipticNA
[HTC Droid DNA] Zer0r:
Strange... I can not reproduce it anymore... I was playing yesturday for a few hours with the same result. But that was on RELOCKED bootloader. Today I made unlock again, restored the same nandroid - and two things happened: firstly, my dmesg showed me PVS value (binned fast), which was empty on RELOCKED bootloader, and second - this kernel is now working normally. I can not reproduce the problem that I certainly had yesturday!
[HTC Droid DNA] [indiferenc]:
NOOB QUESTION: what is "binned fast" and how do i get it?

excellent speed vs. battery life on this BTW
[HTC Droid DNA] jasoraso:
Each CPU is put under a stress test in the factory, to make sure it runs reliably at the spec'd CPU clock (1.5ghz?). During that test, each CPU performs a little different, and requires a certain voltage to run the spec'd cpu speed reliably. Each CPU is then rated (binned) based on the voltage requirements to run the default speed: slow, nominal, fast, or faster.

There is a shell command to determine what your CPU is binned at.

To get a fast cpu, you need merely need to win the lottery :)

If your cpu is binned "fast" then the latest kernel will be a little more aggressive at lowering the voltages for the default cpu speed. conversely, if you are binned slow or nominal, you might need to bump the voltage a little bit more if you want to o/c.
[HTC Droid DNA] [indiferenc]:
thanks! very informative :victory: do you happen to know the shell command?
[HTC Droid DNA] fronc:
adb shell dmesg | grep PVS

See thread here: http://xdaforums.com/showthread.php?t=2039475
[HTC Droid DNA] Zer0r:
No, everything in place. Just had to let it work for a while - and I got reboot. Will post my last_kmesg tonight.

UPD: Got it. It was quite qood untill I raised maxCPU freq. to maximum (1,7). Here is my last_kmesg.

So, I am pretty sure this is UV problem. My CPU, despite it is binned as fast, just can not handle those settings. Is it possible to chenge them? Thanks a lot in advance!
[HTC Droid DNA] crpalmer:
I agree that your crash looks likely to be UV. Try this version (which turns off the UV) and see if it makes your phone happier:

Version 2.0.24: May 16, 2013, Revert UV

* Revert UV change

* Add PVS information to /proc/cpuinfo
[HTC Droid DNA] crpalmer:
Doh. Too early in the morning. I broke wifi on the version I uploaded... I just posted a new link and changed the post to point to the new link. If you already downloaded it, you should do so again. Sorry about that!
[HTC Droid DNA] Zer0r:
Sh*t... I already made two versions of package (to replace all the modules), flashed them with no result, and prepared to reinstall my system, lol!:eek:

Thanks for the fix! :D

But everything else is working flawless!
[HTC Droid DNA] shizumie:
Thanks for that!

One question tho. Im binned FASTER, so should i do anything? Since its setup for fast should i volt a little more aggressively?

Thanks.

Signed with the blood of my DNA
[HTC Droid DNA] keithce:
I hope this is just a temporary change! I'm a fan of this undervolting . I'm getting longer life and I don't think I've seen any adverse affects.

sent from my Droid DNA
[HTC Droid DNA] kierren:
I concur with this statement. I'm binned fast and the undervolted kernel was working great. I was getting a bit of extra battery life as well. Any chance you might do two builds of future kernels, or should I use this System Tuner that I hear some people talking about?
[HTC Droid DNA] CharliesTheMan:
You might try android tuner free. I'm using the pro version and its been working well.
[HTC Droid DNA] Zer0r:
I don't know what happened to new Android base, but on ICS all the kernels had the same way to store settings. And there are a lot of apks that allow to manipulate them, like Android Tuner, Kernel Tuner, etc, with freq. control for each CPU, governor, voltage conrol, and even thermald and mpdecision control. But now each kernel uses it's own settings, and there is no more regular way to change them. It's a pity.
[HTC Droid DNA] [indiferenc]:
+1

i'm binned "faster" and the undervolt and oc combo works great. my phone stays very cool compared to other kernels. hope this feature stays
[HTC Droid DNA] crpalmer:
I'm playing with some ideas for building two different versions. If I don't get something that works well enough to make me happy (aka, doesn't require that I do manual work for each build), I will try to do so. If not, I'm probably going to leave the UV reverted because it's not overly hard to get an app to do the UV for you but it's impossible to boot the phone at all if your phone can't handle the UV. We'll see what options I figure out.
[HTC Droid DNA] crpalmer:
For a hot-plug enabled device (which a quad core really, really, really wants to be), I personally don't know of a good reason to want per-cpu control for speeds/governors/etc. For that matter, the only reason to disable thermald / mpdecision is if you are running an alternative version (which is why I disable the stock versions in my kernel). Not running one at all would be bad (thermald-bad == kill your phone if you overheat it too much, mpdecision-bad == run out of battery fast).

All the kernels that I have looked at use faux123's voltage control so that is one which should be pretty standard across kernel / across devices.

That rant complete, if there is some tool that you think doesn't work well with my kernel, can you tell me "when I do X", "I expect it to Y", "but instead it does Z" so I can reproduce it and see if there is something I'm doing wrong?
[HTC Droid DNA] orangechoochoo:
I think he is saying these kernel tuning apps don't properly read kernel settings because the kernel settings are someplace else where these apps don't know where to look.

For example, on Z's kernel I uninstalled my kernel tuning app, flashed Z's kernel, and installed a kernel tuning app to see what settings it reports. Then I repeated the process three more times for three other kernel turning apps. The purpose was to verify that the options I chose in Aroma were set and reported appropriately. My findings showed each app reported something different, either the scheduler was wrong or the min and max frequencies were wrong.

I don't know if it's because the app was reading the wrong settings or Aroma is not properly applying the chosen settings.

I did the same test for your kernel (although there is no Aroma installer) but I notediced the min freq is set at 384 instead of 192. I don't know if you kernel has 384 set as the stock minimum frequency or not.
[HTC Droid DNA] crpalmer:
Stock min frequency is 384 (I stayed with HTC's speeds as the defaults) so that one is right.

In general, if you think that something is mis-reported, let me know with the what I expect/what I see explanation and I can either explain or fix...
[HTC Droid DNA] ML417:
could you create a second flashable zip that only changes the voltage table? that way you won't have to update it every time.

anyways, I just did a 7.5 hour drive with GPS, Spotify, and full brightness. The kernel handled well, but the phone decided to act funny. I also ended up hanging the phone off of the AC vent using the pull out arm on my Seidio Active Case so it cooled down from 52C to 31C after I did that, but it was a hot day anyways. Overall lesson is, mount your phone on an AC vent and use a good charger :P
[HTC Droid DNA] Zer0r:
Accordingly to what crpalmer said - all the kernels are using the same UV control. Therefore - you can use KernelTuner to change your CPU voltage. No flashable zips needed.
[HTC Droid DNA] ML417:
I know, that was just my take on the two files idea from last page.
[HTC Droid DNA] wpsantennas:
Strike that, after playing with Velis for a few days it started to irritate me because I couldn't get it work as well as the built in auto brightness. No matter what I did it was much more obtrusive so I ended up going back to the 2.0.17 kernel.
[HTC Droid DNA] CharliesTheMan:
I prefer the built in autobrightness too. The apps are great for some people I even helped with development of a custom brightness app, but I will use autobrightness if its built on a custom table with reduced brightness, and that's my preference, but I can adjust manually well enough that I don't care for the apps.
[HTC Droid DNA] hurtfuljeep:
Loving this kernel, great UV and awesome battery on eclipticNA revamped.

Sent from EclipticNa REVAMPED!!!!!
[HTC Droid DNA] android4temo:
I couldn't get this kernel to deep sleep on Ecliptic Revamped??

Sent from my Rooted and ROM'ed, Droid DNA!

"When has a locked BOOTLOADER ever stopped me"?!
[HTC Droid DNA] shizumie:
What app are you using to set clocks? I have noticed some walnt allow deep sleep for me. I thought it was the kernel at first but now i get great deep sleep/ battery life on this and zarboz. I bounce between the 2, mostly just because i can lol.

Signed with the blood of my DNA
[HTC Droid DNA] android4temo:
Using SetCPU. I changed to LK's most recent kernel and have been getting deep sleep out the gate.

Sent from my Rooted and ROM'ed, Droid DNA!

"When has a locked BOOTLOADER ever stopped me"?!
[HTC Droid DNA] CharliesTheMan:
Please post over in that Rom thread about your issue tomorrow and ill see about helping you get it figured out.
[HTC Droid DNA] matteebee:
http://db.tt/QLPIP3ax

Last_kmsg from 2.0.23 sod

192-1728

ondemand bfq

Setcpu app

Newt's latest M7

Stay thirsty, my friends
[HTC Droid DNA] jaysinsalot:
Not too shabby viper 1.3 and kernel as is no tuner app

Droid DNA S-off Viper 1.3 TT2
[HTC Droid DNA] Zer0r:
Well, so far - kernel works flawless, I hadn't any reboot. The only thing - is fastcharge is not working. It is for sure. You can see it on screenshot. With Z's kernel it works normally. Maybe it is a matter of names - I mean that 900mA should be from any charger, not only from original. I am using 1A Belkin charger in the office, 2.1A charger in the car, and original one at home.
[HTC Droid DNA] keithce:
Just had a reboot. I was using voice search from Google Now.

http://db.tt/1eHs0v9V

I'm using v2.0.23.

sent from my Droid DNA
[HTC Droid DNA] crpalmer:
That looks potentially like too much undervolting, are you binned fast? Try the next release with less or no undervolting if you are.
[HTC Droid DNA] crpalmer:
New release:

Version 2.0.26: May 23, 2013: init.d tweaks, 3.4.46, no default undervolting

* Added PVS information to /proc/cpuinfo in case you wanted to knoiw what it is for your phone.

* Linux upstream version 3.4.46

* Improve how I set the CPU frequences to safe levels for boot without having to reset them every time a core is hot-plugged in.

* New init.d scripts for some common tweaks (see post #2).

The new init.d tweaks are:

I really like Zarboz's goal of trying to get rid of the need for 3rd party apps to make the common changes that we want to make to some of the configurable parameters of the kernel. I created some scripts that run on boot (init.d) because I install my kernel so many times that I would go insane if I had to use an installer. By using these scripts and configuration files on the sdcard, I can just configure it once and keep installing away to my heart's content.

After installing this kernel, there will be:

/system/etc/init.d/99crpalmer

run at boot, even if you switch to another kernel. It is safe to leave this file there and to let it run as it only makes changes if the kernel contains "crpalmer" in the version.

The tweaks are:

CPU Frequencies

* Frequencies loaded from /sdcard/crpalmer-cpufreq-min and /sdcard/crpalmer-cpufreq-max

* If you specify either or both of these frequencies, it will lock down all of the CPU frequency controls. I had to do this because HTC overrides them in a script that is run very late in the boot process (thanks HTC!).

* E.g. adb su -c "echo 192000 > /sdcard/crpalmer-cpufreq-min"

* E.g. adb su -c "echo 1728000 > /sdcard/crpalmer-cpufreq-max"

Undervolting

* + or - value loaded from /sdcard/crplamer-uv

* The undervolting in 2.0.23 for FAST binned CPUs would be specified as:

* E.g. adb su -c "echo -100 > /sdcard/crpalmer-uv"

Lightsensor

* My light sensor changes didn't sound like they worked well for everyone. If you don't like them you can disable them by:

* E.g. adb touch /sdcard/crpalmer-stock-lightsensor
[HTC Droid DNA] CharliesTheMan:
Crpalmer just wanted to let you know I just flashed it and wiped caches and it booted up perfect :D

You just don't know how excited I am about this changelog. Thank you soooo much man.

PS - Its really nice to see a developer that keeps similar hours to me.

I just ran the commands and set min and max frequencies in terminal emulator, once I rebooted they were stuck like chuck so all is perfect so far :D

I put the badass in Team BAMF
[HTC Droid DNA] spinkick:
got it working. Hope everyone knows they need to create the text files in the root of their sdcard and put in those values. I am a noob so I had to figure it out by reading the log and what it was doing.
[HTC Droid DNA] rajuabju:
This Kernel is sexy.
[HTC Droid DNA] orangechoochoo:
How can we change the governor and scheduler using these scripts?
[HTC Droid DNA] [indiferenc]:
i dont believe this is true. by running the scripts in terminal emulator, these files were created for me automatically.
[HTC Droid DNA] crpalmer:
The governor didn't like being changed during the boot like that. I ended up not looking too hard at it because I very rarely change it (and never change the I/O scheduler).

If you (or anyone else) wants to take a crack at adding the governor to /system/etc/crpalmer/cpufreq.sh and/or creating a script to set the I/O scheduler I would happily add them into the kernel build. You can just PM the script to me or sent a pull request to my github.
[HTC Droid DNA] crpalmer:
It shouldn't create any of the config files, you have to do them yourself.

FYI, I put example adb commands in the explanation of the tweaks that should work to create all the different config files.