yashsingh1/xdaforums huggingface dataset:
[HTC Droid DNA] k2trill:
Voltage table

No success with Android Tuner or Kernel Tuner changing voltage table. Incredicontrol looks like it MIGHT work but I think due to the phones resolution or somethin, the values cannot even be read on that app. No option for access to the voltage table even shows when using Android Tuner and selecting the voltage table option in Kernel Tuner FC's the whole app.
[HTC Droid DNA] iOSh8er:
As long as I don't clock it over 1.83 she's a happy phone!

---------- Post added at 07:41 AM ---------- Previous post was at 07:39 AM ----------

System tuner let me play with the voltages, though I'm not sure if they stuck (didn't pay attention). I will start tweaking it a little today.
[HTC Droid DNA] dsb9938:
I don't control the apps. I know System Tuner works, as I've said more than once.

If the app doesn't look in the right place (and NO it isn't always in the same place) then it won't be able to control it. That's why the GPU part of Kernel Tuner craps out, it hasn't been updated yet for our GPU.

You guys need to realize this is a whole new CPU, and most things have to be updated for it.

I don't post anything I haven't at least briefly tested. And I usually run it for a bit before posting.

D

.
[HTC Droid DNA] k2trill:
I can dig it. I traded in System Tuner Pro for Android Tuner Pro or whatever (same dev). I didn't want too many redundant apps installed and I also figured both apps were basically the same but there may be more functionality in Android Tuner. It also sounded like he was finalizing development of System Tuner. That's why I made the jump. I know there is a free version of System Tuner (System Tuner) but I was hoping to get some use of this $13 app. Especially since it's not the best for "sticking" CPU frequencies either. Oh well, I'll continue the waiting game. Thanks for your input...

EDIT: so I just figured out I CAN adjust voltage table with Android Tuner. The layout is just a little bit different from System Tuner.
[HTC Droid DNA] Stryker1297:
does "fastboot flash boot (file)" mean the boot.img or modules? i'm an htc noob so yea.... PLEASE HELP i dont want to brick this bad boy
[HTC Droid DNA] x70xchallengerx:
I flashed this last night around 10pm and so far all I did was enable sweep2wake and my phone has frozen once at 1am and once this morning. Though thank god I was able to killswitch and restart whereas on the other kernel (earlier version) it bootlooped and locked the data partition ... This morning I changed the gov to intellidemand then went into recovery and wiped cache / dalvik and ran fix permissions .. so we'll see how it goes lol. I am running stock rooted odexed Rom ...

---------- Post added at 11:41 AM ---------- Previous post was at 11:41 AM ----------

That's the boot.img , flash the modules.zip in recovery
[HTC Droid DNA] Stryker1297:
thanks :)
[HTC Droid DNA] calbruc:
Are cores running "offline" normal in a multi-core phone?

Flashed 1.2.5 and installed System Tuner and CPU0 seems to be the only one doing any work. Are the other three fired up when needed?
[HTC Droid DNA] Zarboz:
yes

if they all ran you would have like NO battery life :D
[HTC Droid DNA] scumpoop:
Kernel version: 2.4.2

Kernel Tuner

384/1620

Badass

FIOPS

Froze up when screen was turned on while charging and then another random crash. Here are the kmsg from the crashes. Hope this helps.

http://db.tt/HHxBGrVP

http://db.tt/CQdxgX3k

BTW this is a neat program to pull kmsg automatically after a crash. Dumps the file right to the internal storage.

https://play.google.com/store/apps/details?id=se.mumu21.bootlog
[HTC Droid DNA] PhantomApollyon:
Random Reboot- I just sent a text and locked the screen when this reboot occured, still no CPU control apps of any kind, everything default

http://d-h.st/BbN
[HTC Droid DNA] rayfin:
I just want to chime in and say I'm getting random reboots and lock ups too. It varies on what I'm doing. It could be Chrome, camera, G+, Gtalk.
[HTC Droid DNA] elkay:
I still haven't had another random reboot or freeze yet. I upped all voltages +25. If it doesn't do it for a few days, maybe we've tracked down the culprit. I don't think anyone else has crashed since doing that on stock clocks.
[HTC Droid DNA] elkay:
Spoke too soon - SOD. Phone rebooted itself into a lockup with screen on at the booted-up unlock screen. Of interesting note - this is only the second time this has happened to me and both times it did, it was on my wireless charging stand. I'm wondering if I'd let it sit long enough, if the phone would have gone to recovery like I had found it the morning of my first reboot. Looks like the voltages aren't a fix. Tried to pull /proc/last_kmsg but it did not exist, I guess because of the lockup that I had to hold power until it rebooted a second time. Browsed to it with Root Explorer and definitely not there. :(
[HTC Droid DNA] PhantomApollyon:
If you can, please pull the log after it happens.
[HTC Droid DNA] spinkick:
Sod during charging this morning. All voltages bumped up one, lion heart gov, stock cpu and settings. No log, had to force restart by holding the button
[HTC Droid DNA] bakemcbride21:
From reading the last few pages, I assumed upping the voltages "one notch"'meant 12.5V, as that's the increments in system tuner?

Maybe 25 is too much?

Mine goes to 11....lol

Going to give it a try today and report back
[HTC Droid DNA] spinkick:
Yep, 12.5 from me across the board
[HTC Droid DNA] Shamrock13:
I just flashed this last night, and I had the SOD this morning on the charger. I was forced to restart so I don't have a log either. Also, I didn't have any settings changed as I just flashed it last night.
[HTC Droid DNA] JWhetstone02:
Has happened twice this morning while charging. Only streaming Google music.

lionheart

sio

Max:1512

Min:486

Upped 25 across the board using incredicontrol.

Before this morning, it ran a whole day without any issues. Have noticed it more when I'm plugged in and charging.

http://db.tt/zTp8AzDi <<< last_ksmg after reboot

-HTC Droid DNA-
[HTC Droid DNA] PhantomApollyon:
Random reboot after sending a text, no cpu control, all default

http://d-h.st/R3N
[HTC Droid DNA] xaffron:
I had an SOD

CPU binning: NOMINAL

Kernel version: 2.4.2

Governor: ondemand

I/O Scheduler: sio

Min/Max speeds: 384M/1512M

Remarks: FastCharge ON, Sweep2Wake OFF, all others default
[HTC Droid DNA] abn.geek:
Well it was solid all day yesterday until about 11pm, then SOD and I had to force a reboot. From there it wouldn't go past the droid boot-up screen, so I'm wiping and re-flashing everything :(.
[HTC Droid DNA] elkay:
Sorry, guess I was too brief. I meant 2 notches across the board when I said 25 lol. So another notch up doesn't fix it, either. Doesn't seem to be a voltage problem.
[HTC Droid DNA] PhantomApollyon:
Another random reboot, no cpu changes

http://d-h.st/T8i
[HTC Droid DNA] iOSh8er:
ROFL... This kernel is most definitely not happy on your device.

Please don't touch my "Thanks" button, it doesn't like you... ;)
[HTC Droid DNA] elkay:
Was thinking the same thing. Guess that's not bad though, the more logs we have the better, and if it happens more consistently for some people than others then maybe we can isolate the difference, unless it's the CPU quality. I barely get crashes but I'm on a "Faster" one so it might have more tolerance to the problem.
[HTC Droid DNA] PhantomApollyon:
I'm actually posting logs from 2 different devices but I will say 1-3 random reboots a day is normal for me under heavy use. CPU binned "Fast" on one and "Faster" on the other unit, both have pretty heavy usage.
[HTC Droid DNA] spinkick:
Mine is rated "fast" and I get about 3 reboots or so a day. Give or take one.
[HTC Droid DNA] jamesbra:
I'm binned at faster and have had one reboot in a week or so, but it was not kernel related. Under clocking and light usage because it was my seven on
[HTC Droid DNA] SwordOfWar:
Had 2 crashes since installing bootlog uptime. The saved logs are linked below.

My Logs:

http://www.mediafire.com/?3yohchgmpy31h13,pqc0x392y27383p

Stock ROM with Cubed kernel 2.4.2 (no settings changed).
[HTC Droid DNA] orangechoochoo:
Lol, I'm waiting for an sod so I can test Bootlog Uptime :p
[HTC Droid DNA] scumpoop:
It works very well. Unfortunately lol. Just make sure you enable copy kmgs in the preferences.

Hopefully this app helps us debug issues easier and faster. Makes it easy to give a helping hand.
[HTC Droid DNA] scumpoop:
Lol I uploaded it through tapatalk. Didn't realize it was so huge.
[HTC Droid DNA] elkay:
That's what she said. :)

Anyway, now that everyone is cheerful again, have any of the logs been helpful toward debugging the SOD, dsb?
[HTC Droid DNA] Flak_Munky:
Had a crash at 11:17 today. I was doing some backup and restores on the /system and /data as I needed to revert to a clean install to test something for work. It happened right after that.

CPU Bin: Faster

IO Scheduler: cfq

Clock speed min/max: 192MHz/1.89GHz

Gov: badass

Voltage: -12.5 mV across the board

Kernel version: 2.4.2

I have had a crash here and there before since switching to Cubed (but before adjusting voltage), but wasn't able to get logs at the times.

Attached is the log from that crash.
[HTC Droid DNA] elkay:
This happened to me early this morning just waking up the phone to answer a text message. I turned on the screen to it being frozen at the lock screen with the message being displayed. I turned off the phone by holding the power button within 1 minute of the screen being on and simply turned it back on. Of interesting note, I'd been texting back and forth every 5 minutes or so with someone for at least the past 45 minutes. Yet, the graph shows the phone locked in an awake state and that my screen never registered as actually being off for what appears to be over an hour of time. I know my screen was off between all of those texts. Perhaps this will shed some light on the cause of the freezing problem?
[HTC Droid DNA] rexdog1888:
Crash

2.4.2

All stock settings

"Fast" CPU

http://db.tt/gHK17mxL
[HTC Droid DNA] orangechoochoo:
Dsb, can you let us know if these logs have helped you narrow down the problem?
[HTC Droid DNA] spinkick:
Would nexus 4 kernel work on our phone? same processor, but i imagine the chipset isnt the same.
[HTC Droid DNA] PhantomApollyon:
Latest random reboot, no cpu changes, etc

http://d-h.st/lRh
[HTC Droid DNA] dsb9938:
I have been sick and haven't done much of anything.

Prolly gonna be a few more days.

D

.
[HTC Droid DNA] elkay:
No worries, feel better man.
[HTC Droid DNA] jonah1234:
The kernel is already beast so no need to worry about it. Feel better get some rest man.

Sent from my HTC Droid DNA
[HTC Droid DNA] orangechoochoo:
Get better.

Btw, will the decrypted ruu help at all with the sod problem?
[HTC Droid DNA] bakemcbride21:
Hoping someone has an idea for me. I find when switching kernels, when going back to stock, no matter what I do, all 4 cores are constantly on at 384 when the phone is basically at rest, when normally CPU 1-3 should be offline and fire only when needed.

No matter how many times I fast boot flash the boot.img, wipe cache/dalvik, flash the zip modules I get the same behavior..all 4 cores at rest at 384..which I imagine would be awful for battery life...lol

Anyone have any ideas?

Thanks in advance!
[HTC Droid DNA] iOSh8er:
I have the same issue. It started after I flashed the Back to Stock files in this OP.

I haven't talked to D yet to see what causes it as he has been super sick.

I'll let you know whats found, if anything.

edit: I am only using System Tuner to see that all cores are online. It may or may not be true, everything could be fine afaik.

edit2: In the past I did flash other kernels without flashing the Back to Stock files in this OP and everything seemed to run fine.

Maybe me doing this in the past made my CPU act this way now, after flashing the proper Back to Stock files. Hrmmm..

Please don't touch my "Thanks" button, it doesn't like you... ;)
[HTC Droid DNA] spinkick:
This is the same issue for me. Cant go back to stock using the above files unless I want all 4 cores going. Strange one, indeed.

---------- Post added at 10:00 AM ---------- Previous post was at 10:00 AM ----------

what does a ruu do? Should I google? hehe
[HTC Droid DNA] gwallers:
Just for the record same behavior with me. All stuck on after flashing back to stock.
[HTC Droid DNA] madAdam6LOVE:
Same here, until I did full wipe and installed UKB 1.3.0 and then flashed Stock Writable modules.
[HTC Droid DNA] Cadillac Johnson:
If you guys are curious if all the cores are actually running or if System Tuner is mis-reading something, you could try CPU Stats from Takke in the Play Store. Shows each core and its activity. Has a nice status bar icon showing each core and its load as well.
[HTC Droid DNA] bakemcbride21:
I hope D gets better soon! I imagine it's a touch of that nasty flu going aroud everywhere :(

I use System Tuner as well and it reports Cores 1-3 as offline when at rest on Stock or Cubed Stock w/System Write when everything is peachy.

If I flash my nandroid or another ROM (as I'll probably flash Hatka 2.3.0 tomorrow) and it will resolve itself, no biggie. Once I do that I can go between pure stock and Cubed Stock System Write without issue. Just curious if there was a fix or I was doing someting amiss in my kernel flashing method.
[HTC Droid DNA] Danzoman:
I went back to the stock write kernel and have been noticing horrific battery life last two days. I don't use this app, but installed to look. Is this what you guys see that say all cores are stuck on?
[HTC Droid DNA] iOSh8er:
Yessir!
[HTC Droid DNA] elkay:
Now I'm glad I decided to just stick it out with this kernel for the moment. I hate the random crashes and I'm paranoid about checking my phone to make sure it hasn't locked right now, but to have even worse battery life than HTC-stock would drive me even more batty.
[HTC Droid DNA] sams2100:
Did you guys, who went back to stock, also flash the stock modules zip? That is required to make everything work again.
[HTC Droid DNA] bakemcbride21:
it doesn't get any better charging ;) tough to get juice to a phone with all 4 cores on :)

I'll be flashing hatka 2.3.0 to remedy...I only wished my backup pro would friggin restore my home screens properly... it can't recreate the folders with all the apps in them I create...
[HTC Droid DNA] iOSh8er:
Yes.

Please don't touch my "Thanks" button, it doesn't like you... ;)
[HTC Droid DNA] Danzoman:
Yes I did flash the return to stock package and then the modified write to system after.

---------- Post added at 01:59 PM ---------- Previous post was at 01:57 PM ----------

What are you trying to say lol?! My phone charges and I touched nothing in the app just opened it. I have never messed this deeply with a kernel before, only using Franco's app on ny gnex. You see something in my screenie?
[HTC Droid DNA] iOSh8er:
How will that fix this? Or are you restoring a backup?

Edit: Restoring a backup did not fix this for me BTW..
[HTC Droid DNA] rexdog1888:
Random reboot

2.4.2

Stock setting, no kernel control app

Log: http://db.tt/m7TAJ74w
[HTC Droid DNA] spinkick:
Backup doesnt help. The only known fix is factory wipe right now
[HTC Droid DNA] Danzoman:
So basically factory data reset, cache,dalvic, like flashing a rom. I never thought to do that. And also I thought flashing a rom doesn't mess with the boot anyways?
[HTC Droid DNA] spinkick:
It doesnt but I think the modules is the problem. I'm not really sure.
[HTC Droid DNA] iOSh8er:
Didn't do it for me :(

Update: It took a factory reset AND I had to flash the ROM again.

I will do some quick testing to see if this was self caused as suggested by DSB. :D

Still running on all 4 cores.

Please don't touch my "Thanks" button, it doesn't like you... ;)
[HTC Droid DNA] orangechoochoo:
I'm currious to flash back to stock to replicate your problems but I haven't had an sod in three days.

When I was on the stock writeable kernel I forgot to flash the return to stock zip and I never had the problem where all the processors are on. Maybe you guys can flash the OC kernel & modules and then flash the stock writeable kernel & modules without flashing the return to stock zip.
[HTC Droid DNA] elkay:
I wouldn't suggest anyone do any crazy cross-flashing until dsb speaks up with what the issue might actually be, seeing as now it's a lot of people reporting the problem so it isn't simply one person overlooking a step.
[HTC Droid DNA] iOSh8er:
As usual, the man knows WTF he is talking about...

All cores come online if we flash another kernel without flashing the stock package on THIS OP.

Where I effed up is flashing ROM's that require or request you to flash the included boot.img BEFORE flashing the new ROM, which includes its own modules.

I'm guessing I'm not the only one!?

Thanks to spinkick for sharing the remedy (full wipe)

Sorry for my clutter D.
[HTC Droid DNA] Danzoman:
Oh well hopefully tomorrow I have a reason to full wipe and flash a "different" Rom to see if that helps ...cough cough wink wink...
[HTC Droid DNA] orangechoochoo:
A couple roms include DSB's stock writeable kernel and they have you flash the boot.img but there's no mention of flashing the modules. Is this because the modules are flashed when the Rom is flashed or the developer did not know to mention it?

But, the flashing of the kernel is required only if you're coming from stock so there is no need to flash the roms kernel if we are using the oc or stock writeable kernel. But if the Rom includes the stock writeable modules in the flashing process it would mess up things if you're running the oc kernel.
[HTC Droid DNA] iOSh8er:
What got me stuck with all cores on:

Was running O.C. test kernel and flashed a very new ROM which has a boot.img included in the OP.

I flashed the boot.img, flashed the ROM, flashed the back to stock boot.img and modules, then I was locked with all 4 cores humming.

The dev of that particular ROM States that he created the boot.img, so I'm sure that's where my issue started.

Please don't touch my "Thanks" button, it doesn't like you... ;)
[HTC Droid DNA] bakemcbride21:
on a car charger my phone will barely increase in battery percentage with all 4 cores online...I drove an hour this morning and it went up like 3 %

lol I'm sure it charges fine, albeit still a little slower on AC power

as for always curing it with either a android or flashing another ROM.. it always works for me because I factory reset/ data wipe... wipe cache.. wipe dalvik... format cache.. format data.. format system before restoring my nandroid or flashing a new ROM

I also name my backups something to the effect of Hatka2-0CubedSysWrite so I know what it is/ what kernel it had.

that way after the restore...I flash the appropriate boot.img in fastboot before restarting the phone.

I've been good to do go every time.

on a side note my USB flap cover broke off when I just opened it a few minutes ago... probably for the best but that sucks lol

I pulled the hanging chad that was left.. Al Gore was not amused...
[HTC Droid DNA] orangechoochoo:
I don't know of any other person aside from dsb who is developing kernels so I would believe they are using DSB'S kernel.

As far as recovery, does a backup include the kernel?

Lastly, does a factory reset put back the stock kernel and modules? I thought it only deleted user data & apps, and reset settings but does not include the writing of a kernel or its modules. Some people say it works so maybe there's something new to FDR. The only true way to get back to stock is via ruu.
[HTC Droid DNA] iOSh8er:
Removed useless bs clutter..
[HTC Droid DNA] bakemcbride21:
a backup will contain the kernel... however a restore cannot write to the boot partition on our current S- On phone.

thus on restore you still need to flash the appropriate boot.img for whatever kernel the backup was running on.. preferably in fast boot before restarting the phone after a restore

I will also re flash the appropriate models after a restore jic...

hence my naming system for backups in my prior post.. it can get confusing!
[HTC Droid DNA] orangechoochoo:
codis uses DSB'S kernel and I think Hatka does too.

---------- Post added at 05:07 PM ---------- Previous post was at 05:00 PM ----------

So FDR really shouldn't have any effect on the kernel problems, so maybe there's something else going on.

So many boot.img's, it would be prudent to give them individual names if they're not stock for sanity's sake.
[HTC Droid DNA] bakemcbride21:
oh all my IMGs in my ADB folder are stockboot.img, stockbootsyswrite.img, boot242.img or whatever numerical version we're on.

however flash gui doesn't support anything not named boot.img so my diligence keeps me on ADB

Joey ktim says he may add a setting you can check to flash a file not named boot.ing.. but currently he restricts it to avoid people flashing ajpeg as their kernel and killing their phone... Lol. I have to agree with him on that!
[HTC Droid DNA] spinkick:
Guys I flashed lemonparty.jpg on my phone, what do I do?
[HTC Droid DNA] orangechoochoo:
Have some lemonade with vodka.
[HTC Droid DNA] iOSh8er:
Disgusting!

Please don't touch my "Thanks" button, it doesn't like you... ;)
[HTC Droid DNA] PhantomApollyon:
SOD log - no cpu changes

http://d-h.st/KtP
[HTC Droid DNA] madAdam6LOVE:
I put my boot.img files in named folders so I can use Flash GUI and still keep track.
[HTC Droid DNA] dsb9938:
I don't know why you guys seem to be having such a hard time with this.

If you are going to use a different kernel, go to the FIRST POST IN

THIS THREAD

AND DOWNLOAD THE PACKAGE I MADE TO RETURN TO STOCK. FLASH

BOTH THE MODULES AND THE BOOT.IMG

. And then you can flash another kernel.

If you wanna flash a ROM and use it's kernel, you do the same thing before flashing anything from the new ROM.

If you wanna flash a ROM and use this kernel, you flash the ROM, then reflash this kernel and it's modules.

And yes, you still have to flash the package even if you are going to my Stock Write kernel.

It's pretty straight forward, and very simple.

D

.
[HTC Droid DNA] spinkick:
I'll try again, but I think that is what we are doing.
[HTC Droid DNA] Danzoman:
I did all that and all was good except all the cores were stuck on. When I wiped system and factory reset and flashed a new Rom it was remedied. I think what it is we aren't used to wiping those two for a kernel change imho.

Via Viper DNA
[HTC Droid DNA] orangechoochoo:
Viper DNA, where did you get that?
[HTC Droid DNA] Danzoman:
I am a beta tester. :D

There was a sign up in the Ukb thread. You guys are on here so much I figured you would have seen that.

Via Viper DNA Beta
[HTC Droid DNA] WolfsFang:
so no need to use the boot.img again if we are sticking to the same kernel but different rom?
[HTC Droid DNA] sams2100:
If changing roms, or upgrading an existing rom, you do not need to load a new boot.img. You DO need install the kernels modules zip AFTER installing/upgrading the rom.
[HTC Droid DNA] dsb9938:
Wiping does nothing for kernels.

Reinstalling a ROM puts back the files.

But so does the file I posted.

If you have issues after, then you did something wrong.

There is nothing I can do for you. It's not broken.

D

.
[HTC Droid DNA] orangechoochoo:
That's the thing, I noticed these roms don't require you to flash the modules so I'm not sure if the modules are flashed during the install of the Rom. If you have DSB's oc kerneland flash a rRom then you probably would have to flash the oc kernel modules.

These roms all say if you're using a non-stock Rom you don't need to do anything but I have a feeling they are flashing some type of modules during the install process, hence the absence of the requirement to flash any modules.

---------- Post added at 07:40 PM ---------- Previous post was at 07:35 PM ----------

To be problem free I would flash the back to stock stuff, flash the Rom as if coming from stock, then flash DSB's kernel and modules.
[HTC Droid DNA] dsb9938:
I tell people to always flash everything.

It's the safest bet.

Most of the time, they just don't want to, or forget.

D

.
[HTC Droid DNA] ML417:
you know, it just occurred to me what the problem might be. could be people are forgetting to extract the boot.img and zips and just try flashing the entire thing?