yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] mko000:
I installed your kernel for the first time yesterday (Exp:b12, faster binned CPU, default settings). This morning I had a random reboot while using Google Reader on AOKP. The last_kmsg shows the watchdog as reboot reason, so I don't know if you can get anything from the log. I'll attach it anyway.

Thanks in advance for any info!
[Nexus 4 Original Android Development] karanrajpal14:
I've faced 3 reboots since morning, once while reading an article online and twice while texting. I was unable to get a log dice they're pretty random. And yeah this is happening after the latest update to build 12. Wasn't occurring before. Please look into this issue! Thanks!
[Nexus 4 Original Android Development] ptesmoke:
Just got same thing while browsing memedroid. Culprit "watchdog"
[Nexus 4 Original Android Development] karanrajpal14:
Just got another one after submitting the previous comment. Reverting to build 10. Please fix this!
[Nexus 4 Original Android Development] consolidate42:
The b12 with inert powerhal is working splendedly for me so far - very smooth for screen browsing and ~18k for antutu. I did have a bit of a scare earlier with a random reboot followed by persistant screen flickering. Might be unrelated as was also testing different roms at the time.
[Nexus 4 Original Android Development] greg17477:
I think you should also tell your CPU bin. (nominal, fast, faster, etc..) Might help debugging. I am on faster cpu and had no reboots yet. I am UV to 975mV on 1,5Ghz
[Nexus 4 Original Android Development] batman368:
same for me, b12 runs awesome, no reboots. i have a fast cpu on 1,5Ghz@1V
[Nexus 4 Original Android Development] mundixx:
Hi Motley,

I had a reboot due to kernel panic. Using b12 experimental.. I've attached the last_kmsg for your reference.

I was using the Interactive governor.
[Nexus 4 Original Android Development] mgear356:
No reboots so far.. Running fast bin, 1000mv @ 1.5ghz uv - b12 + xylon 016 nightly
[Nexus 4 Original Android Development] karanrajpal14:
How do I find that out? I'm pretty sure it's the kernel as I have not faced any reboots after reverting. And for the others facing reboots, which ROM you guys on?
[Nexus 4 Original Android Development] greg17477:
its surely the kernel, but it might help narrowing down the problem.

You can find it out by typing in the terminal:

dmesg | grep PVS

btw, one reboot has got me too.. i am testing further.
[Nexus 4 Original Android Development] _motley:
Hi everyone. Sorry if you are experiencing issues in b12. If you need a stable kernel and don't want to help troubleshoot, then I suggest you go back to b10 as that was stable and everyone seemed to be enjoying it (this is when you always hate to release a new build:()

I am not yet exactly sure sure why only some are having the random reboot issues, but I have some general ideas that we can check out. Nothing with voltage was changed from b10 to b12, so I don't think it has anything to do with the binning of the chips. I have a nominal chip and I haven't seen any reboots.

For those of you that ARE having the reboot issues and want to help. Please do the following steps:

Test 1 - flash the "Inert PowerHAL" in the OP (near the bottom). Keep using the default interactive governor after reboot. This step will take away the touchboost call from PowerHAL and will thus stop the interactive/auto_plug touchboost activity which is new in this version.

If this solves the problem, stop and let me know. If not, move on to step 2.

Test 2 - switch the governor to OnDemand. This will help test to see if the new interactive governor from Google is causing the problem.

If this solves the problem, stop and let me know.

If you still have the problem after test 2, let me know:

a-Which ROM you are using

b-Which kernel you were using before this one - shouldn't matter really

c-Is there an activity that seems to always trigger it or happens more often? web browsing to a certain page etc? If it's random, then that is an OK answer as well.
​

I also have some other ideas about some changes from b10 to b12. After work today, I can try reverting some of these changes to see if that helps. However, if we can have the info from above by then, we would be one step ahead of the game and might better understand the cause before I get started with the secondary changes.

Thanks for all the feedback and logs!
[Nexus 4 Original Android Development] Remoteconcern:
Thanks motley. Don't worry, b12 is just a stepping stone onto the even better b13, once we've nailed this.

Just had a reboot. Here's a log attached, looks like a watchdog reset.

I've also flashed the inert PowerHAL, so I'll let you know if I get anything else happening.

Thanks for your work.
[Nexus 4 Original Android Development] karanrajpal14:
Well testing is not a problem. We'll do it and try to help you fix this. Will try and let you know soon. Thanks!
[Nexus 4 Original Android Development] dark_ente:
I'm testing b12 now, and if I have reboot I'll try the step you mentioned.

Sent from my Nexus 4
[Nexus 4 Original Android Development] ragiut1:
I havent had any reboots on b12 since yesterday.

UVed 100mv across the board, and CPU capped at 1.4

Hope this helps
[Nexus 4 Original Android Development] mgear356:
great friendly support motley! thumbs up for u!

Is it possible to look into USB fast charge? I know its enable but it does not show up in AOKP & Xylon roms under quick toggle... So far only franco one shows up..

Anyways to make it happen?
[Nexus 4 Original Android Development] rlaw:
AOKP is not CM-based. They're both AOSP-based projects. It's possible the ports you've seen were CM-based.
[Nexus 4 Original Android Development] consolidate42:
After flashing the inert PowerHAL, I've yet to receive a random reboot.
[Nexus 4 Original Android Development] AnthonyAldrete:
This kernel performs a little faster than stock which is plus for me :) thank you for this.
[Nexus 4 Original Android Development] Hrithan2020:
@All,

Those who are on b12. Please guide me regarding the interactive settings required for good battery life. [right now running max @1.242 ghz]

Does the boost needs to be set to on [ under trickster mod settings]. After going through the thread in bits and pieces , I have modified the hispeed_freq to 1026 Mhz. Is there any other suggestion? [ I have UV'ed of course beyond the standard faster UV settings which motley has].
[Nexus 4 Original Android Development] consolidate42:
I'm currently testing the settings myself.

I recommend flashing the inert powerhal linked in the OP.

The only settings I've changed are:

highspeed_freq = 1026000

highspeed_load = 80

target_loads = 95
[Nexus 4 Original Android Development] Hrithan2020:
Thanks. But haven't had any reboots so far, so wasn't sure whether it was required.

So you also have disabled the boost? [ it comes by default disabled, I think]

Also by highspeed_load I assume you meant "go_highspeed_load" right?

EDIT: Flashed it anyway :)
[Nexus 4 Original Android Development] Remoteconcern:
No reboots since I've flashed the powerhal. Anyone else?
[Nexus 4 Original Android Development] Audioboxer:
No reboots on 12 with powerhal and omdemand.
[Nexus 4 Original Android Development] samwebbo1990:
No reboots for me with powerhal and interactive
[Nexus 4 Original Android Development] rlaw:
Haven't had any reboots with b12 since I downloaded yesterday soon after it was up. Using interactive.
[Nexus 4 Original Android Development] ptesmoke:
System tuner here as well. 800mv as low as we can go?
[Nexus 4 Original Android Development] _motley:
Thanks for the confirmation from you and the other CM10.1 users. Glad it is working well. For the user that reported it wasn't working, please make sure you use the AnyKernel zip and not the boot.img install.

No OTG support for Nexus 4 yet for direct connect via USB :(, but it's being looked into and hopefully the community or maybe Google will figure something out. I haven't studied up on it enough yet to understand exactly where the limitations lie. Using CIFS, you could mount a shared drive on a network (create a CIFS/Windows Networking share based on the USB drive you need access to). Using the app CIFS Manager is typically my preferred way to mount and access network shares, although dropbox has really limited my need for that and OTG.

Thanks for all the great feedback on battery usage and UV. I have been trying many of these same types of things and agree that the screen off battery usage has been better than stock.

I recommend System Tuner as a good all-in-one solution, but others may work as well. The UV stuff is a bit tricky and not all programs will work properly.

Good question as I know it is probably confusing to some. The anykernel zip will insert the kernel binary into your existing ramdisk provided by the ROM (stock, CM, AOKP, PA, etc). The ramdisk has the init files that dictate a lot of things as the system starts up. The anykernel zip is recommend for any ROM that doesn't use the stock AOSP ramdisk since it just slips the kernel in and leave the rest alone. For me, I would use the anykernel zip and flash via custom recovery in case the ROM dev/cook has tweaked things in the ramdisk.

For stock ROM, you can also use the anykernel zip or you could also use the custom boot.img. In the stock ramdisk, the init script sets the default CPU governor to OnDemand on startup regarless of the default set in the kernel. OnDemand is a fine governor and is the default for the N4. However, I also like the Interactive governor and didn't want to have to have an app setting it for me on boot. The boot.img posted is only for stock and the only differences from the stock boot.img are covered in the OP. Setting the lowest frequency may or may not matter. In my experience it will still use the lower 304 frequency either way, but I did alter the ramdisk init script to set the min freq at 304 instead of 384. Even if you don't use the boot.img, you can still set the default governor and min frequency using System Tuner (recommended) or other compatible apps.
[Nexus 4 Original Android Development] _motley:
For now that is the min in the current release, but I will be looking into it and doing some testing.
[Nexus 4 Original Android Development] ptesmoke:
Thanks buddy, currently -150mv on cm10.1 11/30 nightly. Will report back later with initial results.
[Nexus 4 Original Android Development] Mahdi786:
Try CPU tweaks from playstore
[Nexus 4 Original Android Development] digweed4me:
I couldn't find cpu tweak on Google play would u mind giving me a link sir?
[Nexus 4 Original Android Development] mikeyinid:
600 Mv would be a good minimum to be able to UV to. I have a feeling most devices would be able to go that low and remain stable. On the lower freqs at least. Also, would you look at adding a lower freq? I think something in the 164 MHz range would also be stable for a min freq.
[Nexus 4 Original Android Development] Mahdi786:
Sorry its called CPU Tweaker
[Nexus 4 Original Android Development] gbroon:
While I have been testing undervolting limits on my phone I have found a few things.

Sometimes its not possible to underclock below 1GHz, if you try it just jumps back up. though sometimes if you reboot it does allow lower. This may be apps not being updated though.

In voltages there are a lot of settings for frequencies that aren't actually used, not able to clock the processor to them and they don't show up in CPU spy.

If I'm using stability test to stress the CPU system tuner shows that 3 of the cores are running at a lower speed, this may be the processor though as it throttled down further when the temperature reached 80ish degrees when set to full 1.5GHz.
[Nexus 4 Original Android Development] ptesmoke:
This chip set is new..and its got some funky things to it. I'm sure motley will have this thing singing. Its a matter of trial and error guys...don't forget this thing is new to the kernel devs as well...once all the throttling/scaling is figured out I'm sure things will make more sense.
[Nexus 4 Original Android Development] Cyb3rGlitch:
I noticed that if I set the maximum clock rate to 1GHz with any app, the device will still occasionally clock over this. Scheduler is 'interactive'.
[Nexus 4 Original Android Development] kaiser_tytnii:
Project butter... CPU clock ramps up as soon as the screen is touched
[Nexus 4 Original Android Development] Cyb3rGlitch:
It does it even when it hasn't been touched. Also, it can jump to 1.5GHz which butter doesn't do IIRC.
[Nexus 4 Original Android Development] tpboi:
i use system tuner, very good a very complete app.
[Nexus 4 Original Android Development] aventu:
When I reduce the clock I still get 1,5ghz at cpu 1-3.
[Nexus 4 Original Android Development] Cyb3rGlitch:
Yeah, the maximum CPU setting only seems to affect the first core.
[Nexus 4 Original Android Development] aventu:
Moreover I think that the current governors and butter are too aggressive with clock speeds and lasts too long at these frequencies, even interactive.
[Nexus 4 Original Android Development] keda:
What's the second scroll bar that you clocked at1.02 GHZ? Is it for 2-4 core?
[Nexus 4 Original Android Development] faux123:
All of CPU control apps except mine have bugs controlling the Qualcomm multi-core CPUs due to the asynchronous SMP design.
[Nexus 4 Original Android Development] Cyb3rGlitch:
Do we have to use the Inteli governer to set the max on each core? Or should it work for on all govs?

Edit: just remembered what thread I was in! This kernel doesn't have that governer. I'll check now.

Edit: Faux123 doesn't cap all cores. Confirmed with PrefMon.
[Nexus 4 Original Android Development] rbanaco:
No reboots here! b12 with powerhal (whatever that is) and interactive...
[Nexus 4 Original Android Development] ReD_AvEnGeR:
kernel works perfectly !
[Nexus 4 Original Android Development] Domx92:
b12 is great ! had one reebot in about 24 hours, don't know why :b

Any sugfestions for settings that give great battery life ?
[Nexus 4 Original Android Development] flipim:
First 24 hours with no reboots.. Then in 2 hours 2 reboots...

I hope it doesnt repeat..

---------- Post added at 08:51 PM ---------- Previous post was at 07:53 PM ----------

3rd reboot.. going to wipe and probably change kernel..
[Nexus 4 Original Android Development] rlaw:
Try b10.
[Nexus 4 Original Android Development] consolidate42:
These governor settings for b12 /w inert PowerHAL are working really well for me: pretty optimal battery life /w 18k antutu

above_hispeed_delay 20000

boost off

boostpulse_duration 40000

go_hispeed_load 80

hispeed_freq 1026000

min_sample_time 40000

target_loads 95

timer_rate 20000

timer_slack 80000

These settings will mostly set the clock @ 1026 and below for moderate cpu loads, but is able to ramp up higher when needed. I highly recommend people try to find their lowest stable voltage for 1026 mhz, as it seems to be the sweet-spot for power/performance.

I can do 600mV at 1026, but only 850mV @ 1134 - so the idea is to try and keep clocks <=1026mhz for low-to-medium sustained cpu activity i.e. watching streamed video, while also allowing the governor to go at max speeds for bursts of high load (initial program loading and gaming).

I confirmed this behavior with cpu frequencies overlay-ed on top my my status bar while testing. And while people love to rag on benchmarks, I really do think they serve as a perfectly reasonable test of how responsive governors are to quick changes in cpu load as there are several idle periods during which successive tests much be queued up. If the governor is slow to respond, then the scores will be lower.
[Nexus 4 Original Android Development] mko000:
Did you have the inert PowerHAL flashed?
[Nexus 4 Original Android Development] flipim:
What do I have to flash before install b10 if Im coming from Franco r33 kernel?

I have make full wipe, changed rom, and installed Franco r33, but I have already installed all apps and settings.. so I wouldnt like to wipe everything again...
[Nexus 4 Original Android Development] ctfrommn:
Reset kernel on the 1st page.....http://xdaforums.com/attachment.php?attachmentid=1550949&d=1355107145
[Nexus 4 Original Android Development] Remoteconcern:
What CPU bin are you? Would be great to get my voltages that low.
[Nexus 4 Original Android Development] JmPTaz09:
No reboots here running 12 for a day... I think I have a nominal chip though always have problems checking... I uv'd 50mv more than it was when I flashed (was 1100 at 1.5ghz, I'm running at 1050 and did -50 for all frequencies; 700mv for 304). Stock kernel settings, nothing changed but under volt, so I'm using interactive. Seems pretty good so far! Using Xenon ROM.
[Nexus 4 Original Android Development] consolidate42:
Fast.

My lowest stable @ 1512mhz is 987.5mV which seems pretty typical of 'fast' bins. I recommend that you try and find the lowest stable for each frequency as the progression isn't exactly linear.

It might so happen that you're able to get 810mhz or 918mhz stable at 600mV. If so, then set that as your hi_speed to try and bias the governor to your most 'efficient' clock.
[Nexus 4 Original Android Development] greg17477:
I think these two should be other way around:

go_hispeed_load 80 -> 95

target_loads 95 -> 80

I am not sure, however, as far as i know the target_loads value specifies the load you want to get by rasing the cpu freuencies. The frequencies will be raised until the load gets equal or below targets_value (80 in this case). And go_hispeed_load means, as soon as the load reaches the specified value, the cpu raises the frequency to the highest value (1,5Ghz by default). I would assume in your settings target_loads (95) never get used because as soon as your load reaches go_hispeed_load (80) it ramps up the frequency to the maximum value set.

But honestly, i am not 100% sure about this, maybe motley could clarify this ;) Its something for the post #2 :)
[Nexus 4 Original Android Development] Remoteconcern:
Thanks. I'm a fast too, so I will try jumping to your values as a quick fix - normally I try and gradually move downwards but I'm feeling impulsive today :laugh:

Actually, checking what I'd already moved it down to, 1.5Ghz is at 950mV already. I might have a good bit of silicon on my hands. :good:
[Nexus 4 Original Android Development] consolidate42:
I'm pretty sure hi_speed_load corresponds to hispeed_frequency and target_loads corresponds to max because if it were the other way around, I would be logging lot more time at 1512mhz compared to 1026, while the opposite is true.
[Nexus 4 Original Android Development] poolemit:
thank you for posting this. i independently arrived at the same lowest stable voltages as you did (stress testing w/ stability test) on my 'fast' cpu so i think we have very similar chips. will see how this goes. cheers!
[Nexus 4 Original Android Development] Zaihanzainal:
Noob question. I'm coming from Franco kernel been trying to flash this but keep b getting boot loop both with and w/wo wipes.... Any advice?
[Nexus 4 Original Android Development] poolemit:
if you haven't, you need to flash stock kernel in order to 'reset'. copy/paste from OP:

(go to OP for download link)
[Nexus 4 Original Android Development] ctfrommn:
Flash reset/stock kernel in the OP......http://xdaforums.com/attachment.php?attachmentid=1550949&d=1355107145
[Nexus 4 Original Android Development] bclark:
Random reboot. Faster chip. Using interactive. Underclocked to 1134 with uv. Slimbean Rom. Pre New power Hal.

Last kmsg:

http://db.tt/J2y1CpDI
[Nexus 4 Original Android Development] _motley:
Thanks for the feedback on b12 everyone. I am going over the logs and info you have provided to see what I can figure out. If anyone has any additional feedback to post about the two troubleshooting steps I posted this morning, please let me know.

I still haven't ever experienced a reboot b12 myself. Usually this would be a good thing, but not so much in this case!. These appear to be watchdog events where something isn't reporting back to the watchdog service in the kernel, so it decides that something is wrong and it requests the reboot. The good news is that it is a controlled reboot, so no harm should be being done.
[Nexus 4 Original Android Development] rlaw:
I used to have reboots on b10 maybe once or twice a week. It'd start off as a soft reboot (from bootanim) then once everything was initialized, it'd freeze and go to hard reboot.

With b12, I've had no issues (yet) and am able to safely uv to a level that would previously result in almost instant instability and a reboot.

You've done a great job with b12!

Shame others are having issues.
[Nexus 4 Original Android Development] _motley:
Yeah, isn't that how it goes! On b10, I had one person email me with a log and random reboot, can' t recall if this was you or not. For me, I never have had reboots on either build. I am running the stock ROM.

Finicky little things these phones are. Besides the slightly different hw, add in the different ROM's, apps, and configuration options users like to make, and we have ourselves a complex little ecosystem to play in.

I'm thinking about doing a halfway backward build. Take out the top suspects and work our way back towards b10.
[Nexus 4 Original Android Development] mobilehavoc:
B12 is working perfectly fine for me. I hope you don't revert too much.

Sent from my SAMSUNG-SGH-I747
[Nexus 4 Original Android Development] lazer155:
I've been using the experimental kernel (currently b10 but am planning to test b12) for awhile now and am wanting to try undervolting for even more battery savings. I have a 'fast' binned processor. Could someone explain how I know how much to undervolt by for each frequency? For example what increments should I start with and how do I know if it is stable? I assume that if I mess up by decreasing it to much my N4 could be bricked, is that correct? Or will it always be recoverable from recovery mode? I think CWM runs its own kernel and doesn't rely on the one on the rom side, at least that's what I read in the CWM release thread at some point. I apologize for this being such a dumb question.

What exactly does powerHal do when it stops touchboost requests? If it is dulling things down by stopping the CPU ramp up on touch input and you said powerHal was present in b8/10, I don't understand how it was active in those 2 betas because I always got the CPU ramp up in those 2 betas.
[Nexus 4 Original Android Development] karanrajpal14:
I haven't faced any reboots after flashing the power HAL. Just thought I'd let you know. It may help you! Thanks for the awesome kernel!
[Nexus 4 Original Android Development] elkhouri:
B12 is working perfectly for me as well, for the most part. Had a reboot yesterday with it, but working just fine today after I flashed the inert powerHAL. Even hitting the 6 hour screen time mark. Using Xylon 16 stable by the way.
[Nexus 4 Original Android Development] _motley:
Experiment build 14 posted

Thanks for the feedback guys. I have just posted build 14.

I am hoping this will keep the stability of b10 and still allow us to have the adjustable boostpulse/hotplug integration functionality from b12. See the release notes for the updated settings. The interactive gov settings are now back to the way they were in b10.

Let me know how it goes!
[Nexus 4 Original Android Development] ptesmoke:
https://docs.google.com/spreadsheet/ccc?key=0Agopkmi7sKmkdGhwZHduVEV1OFozUTNRSDMtSGVhSVE

Here's my table. Keep in mind I'm faster binned.
[Nexus 4 Original Android Development] lazer155:
It says I need to request access to view it. Can you make it public? Do you know of any google doc undervolt collections with various bins?
[Nexus 4 Original Android Development] _motley:
I have updated post #2 to reflect b14 tuning options...time to get some rest now:silly:

P.S. Great to see everyone helping each each other!
[Nexus 4 Original Android Development] ptesmoke:
I allowed you but how do I make it public? Sorry...new to Google docs..

---------- Post added at 09:41 PM ---------- Previous post was at 09:38 PM ----------

Your a beast!!!
[Nexus 4 Original Android Development] lazer155:
I sent you a request email just now. It will let you approve me there.