yashsingh1/xdaforums huggingface dataset:
[Hero CDMA Android Development] Matches-Malone:
I am running CM 6.0.0 with uncappedkernel-stable-11182010 (I believe it was #43), batterytweak-Decamodv2.2. I used the battery tweak to overclock it to 729 while on battery. I am experiencing some wake lag. Is there a more ideal uncapped kernel, or battery tweak for 6.0? I may just need to drop down the overclock to 710 and give that a try.
[Hero CDMA Android Development] theimpaler747:
You need to update to CM 6.1.0, should go away after that :)
[Hero CDMA Android Development] Matches-Malone:
Thanks Impaler. Just thought I'd throw out how it ran. Other than the wake lag it ran great, It's at 11 hours and 30 minutes and still 71% battery. After I update to 6.1.0 do I need to reflash the uncapped kernel and battery tweak, or will they still be active?

Thank you. :D
[Hero CDMA Android Development] Decad3nce:
You'll need to reflash both of them.
[Hero CDMA Android Development] theimpaler747:
Reflash both and you'll be fine :)
[Hero CDMA Android Development] Matches-Malone:
Well this should take a few minutes. Thanks again.
[Hero CDMA Android Development] Matches-Malone:
Well running 6.1.0 now and it seems to be running smoother. I changed it to run at 729600 on battery power in the terminal emulator, but it says 691 still. Maybe because I'm at 70%.
[Hero CDMA Android Development] GeezyAF:
Will there ever be any undervolting with this kernel?
[Hero CDMA Android Development] theimpaler747:
Yeah, that's why :)
[Hero CDMA Android Development] theimpaler747:
It already is... otherwise the phone would be a lot hotter than it is ;)
[Hero CDMA Android Development] Decad3nce:
Check the freq table. Already is undervolted.

{ 518400, ACPU_PLL_2, 2, 1, 132000, 3, VDD_6, 160000, 0, 5, -1, 0x1a },
{ 537600, ACPU_PLL_2, 2, 1, 132000, 3, VDD_6, 160000, 0, 5, -1, 0x1b },
{ 576000, ACPU_PLL_2, 2, 1, 132000, 3, VDD_6, 160000, 0, 5, -1, 0x1d },
{ 614400, ACPU_PLL_2, 2, 1, 132000, 3, VDD_6, 160000, 0, 5, -1, 0x20 },
{ 652800, ACPU_PLL_2, 2, 1, 132000, 3, VDD_6, 160000, 0, 5, -1, 0x22 },
{ 691200, ACPU_PLL_2, 2, 1, 132000, 3, VDD_6, 160000, 0, 5, -1, 0x24 },
{ 710400, ACPU_PLL_2, 2, 1, 132000, 3, VDD_6, 160000, 0, 5, -1, 0x25 },
{ 729600, ACPU_PLL_2, 2, 1, 132000, 3, VDD_6, 160000, 0, 5, -1, 0x26 },
{ 748800, ACPU_PLL_2, 2, 1, 132000, 3, VDD_6, 160000, 0, 5, -1, 0x27 },
{ 768000, ACPU_PLL_2, 2, 1, 132000, 3, VDD_6, 160000, 0, 5, -1, 0x28 },

Check VDD_6(1.2V) instead of initial start on VDD_7(1.325V) past 480000.

Meaning, yes.
[Hero CDMA Android Development] andythegreenguy:
Deca - It's taking forever to make a copy of the kmsg file. Is it normal? I checked the size of the file within the proc folder, it says 0 bytes... :eek:. I used cat and cp, both are taking a while. Am I doing anything wrong?
[Hero CDMA Android Development] GeezyAF:
That's helpful.

Thanks for the explanation.
[Hero CDMA Android Development] Decad3nce:
That's irrelevant, and not an indicator of undervolted. Especially with our freq table which allows the phone to override any preset initial VDD to keep from a power collapse.

Please, don't misinform.
[Hero CDMA Android Development] Decad3nce:
Oh sorry, lol.

The kmsg is constantly written to, so you're constantly dumping its contents to the txt file. You can just kill the dump via "^C"

Check the contents after that. Then paste to pastebin.com.
[Hero CDMA Android Development] theimpaler747:
Actually, I was not basing the fact of undervoltage off of the phone temp, just as a repercussion of being UVed... I've had non UVed kernels when the first kernels were out, and they got terribly hot.... and since my answer is correct, how exactly is that misinformation?
[Hero CDMA Android Development] Decad3nce:
I'll requote myself:

Idle temp might drop off, but not drastically. The older kernels weren't as stable and consistently held a process or two active that they weren't supposed to. Same with older, outdated ROMS.
[Hero CDMA Android Development] theimpaler747:
I know that, and like I said, since temp does drop, and it's UVed, all seems ok in Denmark ;)
[Hero CDMA Android Development] Decad3nce:
The lower frequencies aren't undervolted.. and they can't really be since they don't have a specified frequency unless I set it myself. Which I actually recently "upped" to VDD_3 so it's 1.2V across the freq table as per HTC recommendations. The "power pull" also is also mostly irrelevant during idle/sleep in terms of temperature since the VDD's will drop on their own(same override method).

We only set initial starting VDD's, and I've only set them lower for the higher(post 480000hz) frequencies, which don't ever get touched during idle/sleep, especially so with the interactive cpu governor.

So no. Temp drops regardless of this type of undervolt.

With specified voltages for each frequency you would be right, but in these terms, your not.
[Hero CDMA Android Development] theimpaler747:
If the lower frequencies were UVed, it could crash due to instability, yes?
[Hero CDMA Android Development] andythegreenguy:
Here you go: http://pastebin.com/pBTYMFVq. Once you have looked at it, can you also let me know what you were looking for?

BTW, the wake lag is there only on battery... not when it is plugged in.
[Hero CDMA Android Development] Decad3nce:
There's no way to set them any lower, they're not specified with a variable. You'd have to code that entire mechanism yourself before you could get to the point where you could push it to instability.

Regardless, the arm11 acpu code doesn't allow for instability(as default).
[Hero CDMA Android Development] Decad3nce:
Ahh.. I need you to recreate the problem while dumping the kmsg.

This only shows that your battery was charging :P

You can also just reboot, then dump the /proc/last_kmsg and it'll show your entire last kernel session.
[Hero CDMA Android Development] theimpaler747:
Ok gotcha.
[Hero CDMA Android Development] Matches-Malone:
Thanks again guys. I'll charge it overnight and run it as is tomorrow. I'm betting that takes care of it.
[Hero CDMA Android Development] andythegreenguy:
Ok... let me recreate the problem a couple of times, reboot and send you the dump.
[Hero CDMA Android Development] andythegreenguy:
Here you go: http://pastebin.com/9dhbZCHr.

Deca - As always, thanks for all your efforts... :).
[Hero CDMA Android Development] Decad3nce:
pm_op(): platform_pm_suspend+0x0/0x58 returns -16
PM: Device alarm failed to suspend: error -16
PM: Some devices failed to suspend

and from the looks of it, stems from the RIL.

Tomorrow, I'll see if I can replicate this issue on my own device. Then if I can, I'll work on finding the problem.
[Hero CDMA Android Development] andythegreenguy:
I'll pretend I understood all that... :D. Anyways, I'll hold off going back to # 23 (which I think was the snappiest w/ no lag), till we hear from you.
[Hero CDMA Android Development] Decad3nce:
It just means some device isn't suspending properly, and based on your last_kmsg.. it only happens once in a while
[Hero CDMA Android Development] Matches-Malone:
Just throwing out an update. Wake lag is little to none now. Definitely helped out alot going from 6.0.0 to 6.1.0 running UncappedKernel-stable #43, and battery tweak Decamod v2.2. My phone is set to run at 710 max on battery power in the battery tweak. I unplugged my phone at 6:45 a.m. central time and it is now 7:49 p.m. central time, and I am just now at 70 % battery life after 13 hours runtime. Granted I don't use my phone non-stop, more like slight to moderate usage.

Thanks for all the help.
[Hero CDMA Android Development] theimpaler747:
No problem, glad you got it going well now! :)
[Hero CDMA Android Development] ickwonder:
I have been getting random shutdowns running Pandora. I'm on cm 6.1.0 and #43 overclock at 768 with deca's battery tweak. It happens with jit on and off. When I was on the previous kernal this didn't happen. Its getting annoying.
[Hero CDMA Android Development] theimpaler747:
Flash the capped 691 CFS kernel :)
[Hero CDMA Android Development] ickwonder:
My phone has always been able to run at 768
[Hero CDMA Android Development] theimpaler747:
But still, seems something is messed up... try putting VM heap to 24
[Hero CDMA Android Development] ickwonder:
Vm Heap has been at 24. Another thing is that it only happens when the display is off
[Hero CDMA Android Development] theimpaler747:
Ahhh ok that was an issue with a few of Deca's kernels kernels earlier, I think you'll have to talk to him about fixing it.
[Hero CDMA Android Development] Matches-Malone:
I have no idea how to fix the problem, but would the pandora crash while display being off have something to do with the clock being restricted to a lower speed during display being off? Maybe it's being overloaded while it has the clock speed capped at 352. Or, maybe i'm just making stuff up in my head. :) Either way, good luck. Maybe I should install pandora on mine and see how it runs.
[Hero CDMA Android Development] theimpaler747:
That could be... but I think I remember this being an issue on earlier kernel builds too
[Hero CDMA Android Development] ickwonder:
I'm on the 768 default setting on decas Battery tweak I dont know what clock speed it runs at when the screen is off. Could that be a problem should I custumize the settings. I'm going to test it again cause I only had one shutdown when jit is turn off
[Hero CDMA Android Development] theimpaler747:
You're probably at the default 245
[Hero CDMA Android Development] Matches-Malone:
ickwonder, I doubt this has anything to do with your issue, but as far as i'm aware the default setting on the 768 uncapped kernel with the battery tweak still leaves the phone at 691 on battery power. It only ups the clock to 768 while plugged into a power source either ac or usb.

To have your hero reach higher than 691 on battery power you have to customize the battery tweak settings.

In either the terminal emulator on your phone or the terminal on your computer while using adb with your phone connected.

type 'su' then enter

type "batt-cfg' then enter

option 3 allows customization.

then carefully follow the customization instructions.

I left everything default except the max power on battery which I set to 710400. It tells you what option you can enter. You may want to consult with a higher entity before following my advice that may doom your phone. Or, as everyone says before doing some major change you could do a nandroid backup.

Good luck.
[Hero CDMA Android Development] theimpaler747:
I don't think that'll do it, but it's worth a try! :)
[Hero CDMA Android Development] il Duce:
Ickwonder, I read the lay few pages about this pandora thing. Are you also running set cpu or overclock widget also, I don't think there is a screen off max on the kernel out in the tweak unless youre on smartass governor, it just runs the tweak settings...

One other thing, wipe dalvik when you flash the cfs.

Also, impaler help me on this but could the spare parts screen off sleep mode do this?

sent from my hero, which no longer sucks ass.
[Hero CDMA Android Development] theimpaler747:
I guess it could, but it shouldn't make the phone reboot

Sent from my hero running froyo... take that Sprint!
[Hero CDMA Android Development] il Duce:
There is no screen off max setting with interactive right ? it sounded for a sec like he had set cpu and the tweak...

sent from my hero, which no longer sucks ass.
[Hero CDMA Android Development] il Duce:
Oh I just read your response to the sense rom wipe question I had, did you mean I didn't have to wipe for a sense rom? No way you must have meant I don't need to update my profile/prl.

sent from my hero, which no longer sucks ass.
[Hero CDMA Android Development] theimpaler747:
Do this: nandroid cm, wipe, flash sense, update blah blah, and then nandroid back and you're good to go :)

Sent from my hero running froyo... take that Sprint!
[Hero CDMA Android Development] Matches-Malone:
Il Duce, I was under the impression that the uncapped kernel and battery tweak are running the smartass governor by default, unless you change it.... AH, I see it runs interactive governor by default. My bad. Sometimes I just get excited about something new to me and start spouting information that I think I may know just to find out afterwards I was wrong. :rolleyes:

Thanks. :)
[Hero CDMA Android Development] ickwonder:
Well I haven't had time to duplicate the shutting down just yet. I've been busy but I can tell u that when installing the kernal I wiped davlik before and after installation. And the phone doesn't reboot it shuts down. It doesn't let me turn it back on unless I pull the battery then turn it on. And also this happen plugged in via USB and not plugged in. I'm gonna test it now ill report back.
[Hero CDMA Android Development] ickwonder:
Oh yeah I'm not running set CPU or the widget
[Hero CDMA Android Development] ickwonder:
Ok so I got it to shut down again with jit disabled. But I noticed this time since its very quite right now that I hear a soft fuzzy sound through the earpiece like if the phone is still on but appears to be off due to the screen being off and the phone being unresponsive. Weird.
[Hero CDMA Android Development] il Duce:
Weird indeed, try impalers advice, I would also wipe dalvik again, and obviously turn off jit.

sent from my hero, which no longer sucks ass.
[Hero CDMA Android Development] theimpaler747:
Hey, its how we learn :) Fyi I like interactive better, smartass was slow for me

Sent from my hero running froyo... take that Sprint!
[Hero CDMA Android Development] andythegreenguy:
Deca - any luck with this? If not, should I just revert to #23.

Sorry to bother, just eager... ;).
[Hero CDMA Android Development] Decad3nce:
Not a kernel issue. Update your CM6 to a newer nightly.

It was a CM6 problem. Clock speed isn't capped at 352.. not even with smartass.. It just allows that range during sleep.

Either use the "3 finger salute" to reboot or just

adb reboot

then pull the last_kmsg

Had a long.. incoherent... night last night. But yes, I did manage to replicate the problem but I wasn't around a Computer to check it out.
[Hero CDMA Android Development] c00ller:
I finally decided to try uninstalling SetCPU and try using the decamod battery tweak. Just going by the percentage things seem about the same, however I checked spare parts and my time spent without sleeping is about 50%! This used to only be able 9-10% typically back when I used SetCPU with no profiles.

I used batt-cfg and used custom setup to basically set everything from 245-729 MHz. Is there anything I should check out?
[Hero CDMA Android Development] theimpaler747:
Sounds fine to me, about what my settings are. I'd do interactive governor, but other than that just see how it ends up going!
[Hero CDMA Android Development] Decad3nce:
Use the "top" command to see what's keeping things active?
[Hero CDMA Android Development] pyovue:
for some reason, this un-rooted my phone. Wouldnt let me set any permissions on quickboot, setcpu, or other apps that needs SU. weird. Im on liquidsense rom.
[Hero CDMA Android Development] theimpaler747:
Flash this from recovery and you'll be good to go :D
[Hero CDMA Android Development] ickwonder:
What is the 3 finger salute &

How do I pull the last _kmsg

Should I do this first before I update to a nightly
[Hero CDMA Android Development] i@jim:
Is it safe?

I'm already cringing at how stupid the following question is gonna sound to you guys, but I've googled myself silly and can't seem to find an answer to it (so here goes) (hold yer noses):

While in the process of flashing the 11/18 uncapped-768 ROM over the 11/18uncapped-691 ROM, I have my Hero connected to my PC via USB. I'm doing that because the battery's low and I don't wanna risk it shutting down mid-update. So is it safe to have the phone connected to the computer like this while flashing?
[Hero CDMA Android Development] Decad3nce:
Should be fine. Even if the update fails, you'll just corrupt the boot.img.. your recovery and bootloader should remain intact.
[Hero CDMA Android Development] i@jim:
Wow, super. Thanks agin!
[Hero CDMA Android Development] theimpaler747:
Couldn't have put it better :) You should be fine going with it, I've done it before
[Hero CDMA Android Development] i@jim:
Fantastic. As ever! I'll letcha know how it goes...
[Hero CDMA Android Development] theimpaler747:
Cool, let us know, and like I said, you should be absolutely fine
[Hero CDMA Android Development] c00ller:
I'm looking at the output of the top command, and it just keeps refreshing a long list of processes. I don't see any data relevant to time spent in each process or anything like that... the CPU% etc data seems to be updating in real time, so how do I tell what has been using a lot of active time cumulatively?
[Hero CDMA Android Development] theimpaler747:
The top command is only for current processes, use spare parts to get an overview of entire CPU/battery usage
[Hero CDMA Android Development] Decad3nce:
Just paste the output of

top -m 5 -n 1

-m suffix: maximum number of proc

-n suffix: iterations to go through

Not sure if you can look at the cumulative process history

http://linux.about.com/od/commands/l/blcmdl1_top.htm

IE:

User 1%, System 4%, IOW 0%, IRQ 0%
User 5 + Nice 0 + Sys 15 + Idle 298 + IOW 0 + IRQ 0 + SIRQ 0 = 318

PID CPU% S #THR VSS RSS PCY UID Name
3222 5% R 1 944K 388K fg root top
183 0% S 53 200572K 39648K fg system system_server
3 0% S 1 0K 0K fg root ksoftirqd/0
4 0% S 1 0K 0K fg root watchdog/0
5 0% S 1 0K 0K fg root events/0

Only the top command is using any percentage of the cpu.
[Hero CDMA Android Development] theimpaler747:
You can't with the top command, you can with spare parts however ;)
[Hero CDMA Android Development] Decad3nce:
That's great.. not detailed enough and doesn't show specific kernel threads. Not too terribly helpful for kernel debugging.
[Hero CDMA Android Development] theimpaler747:
Not for debugging no, but for general knowledge, yes. It also tells you the actual name of the process just like the top command.
[Hero CDMA Android Development] Decad3nce:
Top command shows specific kernel threads. Spare parts shows the processes running on the android system server. It's not the same thing.
[Hero CDMA Android Development] theimpaler747:
I don't think I said it was :confused: Simply that for a user's experience, spare parts will be great for seeing what's eating up battery/CPU on the history of a charge. I'm not sure why you really want to argue about it :(
[Hero CDMA Android Development] Decad3nce:
I'm not arguing. Just saying that it's more relevant in a thread about a kernel which I'm trying to debug. Sorry.

For a general user, you're right, spare parts is all you need.
[Hero CDMA Android Development] theimpaler747:
Point taken, and fair enough :) I'm sorry if I was not clicking with what you were doing either
[Hero CDMA Android Development] aosp:
does spare parts come with the kernel or do i have to buy it in the market place:confused:
[Hero CDMA Android Development] theimpaler747:
It's a free app in the market, and it's included in CM6 :D
[Hero CDMA Android Development] aosp:
this was a test of the xda support system:p
[Hero CDMA Android Development] theimpaler747:
Lol :p Hope we passed!
[Hero CDMA Android Development] CrashV2010:
Omg, this is great !!!!!!!!!! ;)
[Hero CDMA Android Development] i@jim:
You two are great. And the uncapped 768 is great too. But I'm considering going without battery tweak -- absolute time btwn charges is not a high priority for me. Which brings me to my next Q: can I get actual 768mhz out of my little unplugged heroc without the battery tweak configuration? Using OSMonitor, looks to me like it never gets above 691 on battery power.

1000's of thanx!
[Hero CDMA Android Development] theimpaler747:
No problem man, and yes you can :) If you uninstall the tweak, install set cpu and then you can set the battery to min max 768-768 if you'd like... really fast, but eats battery ;)
[Hero CDMA Android Development] i@jim:
Woohoo! But for something less extraterrestrial, 245-768 would work, no?
[Hero CDMA Android Development] theimpaler747:
Yes it will, but if you use option 3 in the battery configuration, you can set it to do that :)
[Hero CDMA Android Development] i@jim:
Ah, I see what you mean. Very cool. Thanks!

--

sent from my

rooted little heroc

usin tapatalk pro
[Hero CDMA Android Development] i@jim:
Ok though, speaking of SetCPU (if I go this route) here's one more Q: any reason NOT to check the "Set on boot" option?

--

sent from my

rooted little heroc

usin tapatalk pro
[Hero CDMA Android Development] theimpaler747:
If you do set CPU, make sure you uninstall the battery tweak, as they conflict. And yes, if you're not sure if some frequencies are stable on your phone, don't check set on boot until you're sure they're fine :D
[Hero CDMA Android Development] i@jim:
And man, now I am afraid I'm becoming a real pest with all these very noob questions, but I just want to make sure: if I use neither battery tweak nor SetCPU, then how is the actual speed of my little heroc governed? And will it reach 768mhz on its own? Lemme know if I'm being a pain!

--

sent from my

rooted little heroc

usin tapatalk pro
[Hero CDMA Android Development] theimpaler747:
You're not being a pain at all :) Just trying to learn. If neither are used, the kernel will "govern" itself, and yes it will reach 768 by itself, as long as you run the uncapped kernel :D
[Hero CDMA Android Development] Decad3nce:
The ramdisk in CM6 overwrites the max and min scaling frequencies to 245-691. So If you're using cm6, you'll have to change that for the kernel to reach 768mhz.
[Hero CDMA Android Development] Decad3nce:
Not on CM6 or on any ROM where there is an overwrite on the ramdisk regardless if the kernel is "uncapped".

See above.
[Hero CDMA Android Development] theimpaler747:
Well then how can anyone run 768 :confused:
[Hero CDMA Android Development] Decad3nce:
Because you don't understand how the kernel works.

min_scaling_freq and max_scaling_freq can be changed on the fly and that's how you get your scaling range, but they can only be changed to an available frequency. I make the frequencies above 691 available in the 768 kernel so that programs or the tweak can overwrite the max_scaling_freq above 691.
[Hero CDMA Android Development] theimpaler747:
That's what I'm saying. If 768 is an available frequency, which it obviously is on a 768 kernel, then anyone on a 768 kernel can overclock to 768
[Hero CDMA Android Development] dedian:
You have to have something (Battery tweak, SetCPU, OC widget) that sets the limits higher, or you'll be limited to the defaults in the CM6 ramdisk (unless you change that yourself and rebuild CM6, I think). Upping the ramdisk limit would more or less be like selecting "Set on boot" in SetCPU, and is probably one reason the limit is at 691, rather than something higher.
[Hero CDMA Android Development] theimpaler747:
I'm sure I've run 768 on no tweak/set CPU before, perhaps that was an older version of CM or DarchDroid 2.7
[Hero CDMA Android Development] Decad3nce:
No you said the kernel will go up to that frequency on default ("govern itself") without user interaction, it won't on cm6.
[Hero CDMA Android Development] theimpaler747:
See post above ;) Probably did it on DD 2.7 or earlier CM
[Hero CDMA Android Development] CrashV2010:
It will default, if the phone is plugged in, to 768...
[Hero CDMA Android Development] theimpaler747:
That's what I though too
[Hero CDMA Android Development] CrashV2010:
All the rest of the times, it's at 691 then it will scale down if you have deca's tweaks...And selection One.....
[Hero CDMA Android Development] theimpaler747:
Well, you can adjust that with the tweak, that's what I did, I have them max at 768 at all times
[Hero CDMA Android Development] Decad3nce:
That's only with the tweak. I explained that. The kernel itself, wont.
[Hero CDMA Android Development] CrashV2010:
Great work deca.... I do get a heck of a lot more phone time, while not plugged in, when in use away from a power source.