yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] big_adventure:
Two things:

1. You are wrong: "everyone" is not having it. I am most certainly not having it, nor is TGM, JNewms, Vomer,* et. al. I don't believe Franco is having it, though he hasn't come and explicitly stated so.

2. Where is your log? Have you tried any of the steps recommended by me on this page? Since this is a problem affecting at least some people, it sure would be nice to figure out why and to solve it.

* Note: I do not mean to imply that I am remotely as valuable to the community as those folks. I'm not!
[Nexus 5 Original Android Development] Hatshipuh:
Guess I'm not everyone then ;)

I was one of those with stutter on r38, luckily not one of those with SoD in the follow-ups.
[Nexus 5 Original Android Development] lolcopter:
1. Enlighten us with your setup without problems then, since that seems to be of the utmost importance for all us crazies experiencing this issue

2. Dunno what I'm doing at all with logs, I was merely confirming the existence of a reoccurring problem the developer ASKED FOR

I used the app from a couple pages back and only excluded modem logs, dunno what I'm looking for exactly but hopefully this is of some use

https://www.dropbox.com/s/rt1ff890eazl17t/2014-04-07_05.48-Franco_r40-1.zip

Stock KOT49H

Franco r40

ART runtime

No xposed, no gravitybox

No uv/no uc

Completely stock kernel settings
[Nexus 5 Original Android Development] SketchyStunts:
9hrs on R40 with no issues here. Running settings close to TGM settings. Slimkat.
[Nexus 5 Original Android Development] Puzzlegirl:
No. I'm not "everyone" and I haven't had any of the issues brought up by "everyone". In fact I can't remember the last time I had any problems on this kernel. I'm on stock with Xposed and GravityBox and no changes to the kernel whatsoever.
[Nexus 5 Original Android Development] lolcopter:
My logs may not be helpful at all because you need logs from before a reboot? I have no clue tbh

Big_adventure continue that spit ball with confirming your good-to-go setup. I was fine on both r39 and r40 for 12+ hours each time too fwiw
[Nexus 5 Original Android Development] gee2012:
The logs should indicate the issue and therefore also the solution ;)

If users post logs be as specific as possible:

Stock/custom rom

Dalvik/Linaro/Xperia Z2 etc enhancements used

Dalvik or ART

Mods installed.

UV/OC
[Nexus 5 Original Android Development] big_adventure:
1. My (current) setup is:

Max CPU: 1574mhz

load_threshold 0

GPU max: 320

GPU up: 25

GPU down: 5

UV to 675 @ 300, 700 @ 422 and -25 everywhere else (phone is a PVS 2)

Governor setup:

above_hispeed_delay: 120000

boostpulse_duration: 250000

go_hispeed_load: 99

hispeed_freq: 1267200

input_boost_freq: 1190400

min_sample_time: 10000

sync_freq: 960000

target_loads: 90

up_threshold_any_cpu_load: 50

I use several per-app modes, mostly to reduce resources for games that don't need but will use them. I also use a PAM for the camera and chrome that permit 2265mhz CPU max frequency and 450mhz GPU max frequency.

2. The easiest way to get a log is to open a terminal emulator (download one from the Store if you don't have one - "Terminal Emulator" is your search term) and enter:

su

cat /proc/last_kmsg > /sdcard/last_kmsg.txt

This will take the pre-reboot kernel message log, generated on boot by the phone, and export it to a file on your storage. You can then upload that file. Pastebin or something is best, but you can also just attach the thing or a link to it.
[Nexus 5 Original Android Development] lolcopter:
This is great thank you
[Nexus 5 Original Android Development] big_adventure:
Your logs are actually fine - the application you used packaged up the boot kernel log along with the last_kmsg. I'm looking through them now.
[Nexus 5 Original Android Development] Laggalot:
i had the SOD once yesterday but nothing since then!

i changed nothing but the kernel (r40)

slimkat 4.0 ART PAM and UV

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] big_adventure:
No problem, though, as I said, the app you used to package everything up gave the last_kmsg.

It also (fortunately) included the active kernel log from the reboot, and your phone is doing the same thing matesc's was doing: setting max cpu to 3ghz :

<6>[ 116.858865] msm_thermal: Setting cpu0 max frequency to 1497600

<6>[ 116.859045] msm_thermal: Setting cpu1 max frequency to 1497600

<6>[ 116.859164] msm_thermal: Setting cpu2 max frequency to 1497600

<6>[ 116.859678] msm_thermal: Setting cpu3 max frequency to 1497600

<6>[ 117.108833] msm_thermal: Setting cpu0 max frequency to 3014400

<6>[ 117.108984] msm_thermal: Setting cpu1 max frequency to 3014400

<6>[ 117.109063] msm_thermal: Setting cpu2 max frequency to 3014400

<6>[ 117.109199] msm_thermal: Setting cpu3 max frequency to 3014400

<6>[ 118.358904] msm_thermal: Setting cpu0 max frequency to 1497600

<6>[ 118.359203] msm_thermal: Setting cpu1 max frequency to 1497600

<6>[ 118.359436] msm_thermal: Setting cpu2 max frequency to 1497600

<6>[ 118.360527] msm_thermal: Setting cpu3 max frequency to 1497600

<6>[ 118.608875] msm_thermal: Setting cpu0 max frequency to 3014400

<6>[ 118.608994] msm_thermal: Setting cpu1 max frequency to 3014400

<6>[ 118.609060] msm_thermal: Setting cpu2 max frequency to 3014400

<6>[ 118.609173] msm_thermal: Setting cpu3 max frequency to 3014400

I force max to 1.5ghz, and I don't have any similar messages in my dmesg at or after boot.

So maybe, just maybe, there is a derp somewhere that is mistakenly setting max_cpu to 3ghz after boot?

Do me a favor - go into FKU and change max CPU freq to 2ghz, and make it set on boot. Don't change anything else. Then, reboot the phone. Wait 5 minutes, then open your terminal emulator and run:

su

dmesg > /sdcard/2Ghz_kmsg.log

Then post the log. I want to see if you still have this odd "force to three gig" thing going on once it is forced. We can isolate to governor controls or not that way.
[Nexus 5 Original Android Development] lolcopter:
For the purposes of using that SysLog app again, would I only need to pull "Last Kernel Log" from the options?

Kernel Log

Last Kernel Log

Main Log

Modem Log

(command line method is good but the more info the better for all, thanks again)
[Nexus 5 Original Android Development] big_adventure:
Welllllll, generally, for a kernel based reboot, last_kmsg ("Last Kernel Log") is what you need. However, I don't see any smoking gun in your last_kmsg log. Your last few sleeps and wakes (what is caught in last_kmsg - it only grabs maybe the last 15 minutes or so before boot) are nearly identical to sleeps and wakes that work on mine.

However, thanks to you having the current Kernel Log, as well as matesc having his SoD in the first 6 minutes after boot, I can see a weird thing that bears confirming - that frequency-set thing.

So, if you don't mind helping:

1. Do the steps I asked for in the last post - set max CPU to 2ghz, set that on boot, reboot, take the Kernel Log five minutes after boot, send it - to see if that changes.

2. Keep including both Last Kernel Log and Kernel Log when you save it after a reboot.

Thanks!
[Nexus 5 Original Android Development] alcurtis93:
Still getting black screen on r40 :(
[Nexus 5 Original Android Development] big_adventure:
Would you consider getting some logs of the event?
[Nexus 5 Original Android Development] emd2009:
Getting black screen on 40. Reverting back to 39
[Nexus 5 Original Android Development] alcurtis93:
How do I log it?
[Nexus 5 Original Android Development] gee2012:
Its posted twice in the last 10 ages how to create a last_ksmg.txt log ;)
[Nexus 5 Original Android Development] big_adventure:
Wait 4 minutes or so after reboot, then open a terminal emulator. Enter these commands:

su

cat /proc/last_kmsg > /sdcard/last_kmsg.log

dmesg > /sdcard/boot_dmesg.log

Then link those files to a post here.

---------- Post added at 02:48 PM ---------- Previous post was at 02:47 PM ----------

Now three times. :)
[Nexus 5 Original Android Development] Ben36:
Weird... Anyone else tried?
[Nexus 5 Original Android Development] big_adventure:
OK, so I confirmed one thing. Something in the kernel or in FKU is setting max CPU to 3ghz after boot if the frequency is not specified and set with set on boot beforehand. The messages I saw before from [MENTION=2785960]lolcopter[/MENTION] and [MENTION=4648685]matesc[/MENTION] both show this, and when I disabled forcing the frequency on boot and then rebooted, I get the same stuff:

<6>[ 116.858865] msm_thermal: Setting cpu0 max frequency to 1497600

<6>[ 116.859045] msm_thermal: Setting cpu1 max frequency to 1497600

<6>[ 116.859164] msm_thermal: Setting cpu2 max frequency to 1497600

<6>[ 116.859678] msm_thermal: Setting cpu3 max frequency to 1497600

<6>[ 117.108833] msm_thermal: Setting cpu0 max frequency to 3014400

<6>[ 117.108984] msm_thermal: Setting cpu1 max frequency to 3014400

<6>[ 117.109063] msm_thermal: Setting cpu2 max frequency to 3014400

<6>[ 117.109199] msm_thermal: Setting cpu3 max frequency to 3014400

<6>[ 118.358904] msm_thermal: Setting cpu0 max frequency to 1497600

<6>[ 118.359203] msm_thermal: Setting cpu1 max frequency to 1497600

<6>[ 118.359436] msm_thermal: Setting cpu2 max frequency to 1497600

<6>[ 118.360527] msm_thermal: Setting cpu3 max frequency to 1497600

<6>[ 118.608875] msm_thermal: Setting cpu0 max frequency to 3014400

<6>[ 118.608994] msm_thermal: Setting cpu1 max frequency to 3014400

<6>[ 118.609060] msm_thermal: Setting cpu2 max frequency to 3014400

<6>[ 118.609173] msm_thermal: Setting cpu3 max frequency to 3014400

Those messages do NOT exist when the frequency is forced on boot in the FKU app.

Note: the FKU app indicates that max cpu freq is 2265mhz, but the kernel log indicates that it is higher.

Now, I tried to actually make the CPU ramp to that, and none of my apps ramp it higher than 2.3, so it is possible that this message doesn't really mean anything.

In any case, to people I asked to provide me a current kernel log after boot but with frequency forced, don't bother, I've confirmed what I wanted to see.
[Nexus 5 Original Android Development] gravityy:
I'm using linaro to, no sod problem so far :D
[Nexus 5 Original Android Development] big_adventure:
The problem is, since most people are not having SoD issues, to prove a correlation, you'd need someone who DOES get SoDs on Franco normal, and who does not on Linaro, with enough time testing to "absolutely" confirm this. This means:

1. I don't get SoDs on Franco normal, so me not getting them on Linaro wouldn't prove some immunity inherent in the Linaro chain.

2. You can't prove a negative (i.e. Linaro-built francoKernel does not have this issue) - and you can't even come close in just a few hours.

---------- Post added at 03:23 PM ---------- Previous post was at 03:16 PM ----------

I've been through the logs thus far posted, and the logs taken on r40 don't really show any consistent error message. [MENTION=2785960]lolcopter[/MENTION]'s kernel log messages around his sleeps and awakens are about the same as mine.

There is that odd set of messages about max cpu freq being set to 3ghz - if you don't force frequency in FKU, you get those messages on boot. But I can't be sure that's a problem.

I would propose two test groups to try to isolate some things:

Group 1: change the CPU frequency to, oh, 2ghz or something and set it to set on boot. Change nothing else, and report if you still see SoD.

Group 2: change the hotplug load_threshold to 0, to eliminate the hotplug driver as a problem. Again, change nothing else.

Obviously, don't UV or anything.
[Nexus 5 Original Android Development] Technecium:
Just an idea, can someone provide a log of the sod via adb?

ie. after sod occurs don't try to reset or reboot, connect to pc, adb logcat

we might have a better chance of catching the error.
[Nexus 5 Original Android Development] icethegreat:
User error
[Nexus 5 Original Android Development] pikachukaki:
Can it be a kernels fault that some users have drain on android system causing by usage of system_Server and screenflinger??
[Nexus 5 Original Android Development] icomar:
Everything is fine here. I'm dirty flashing latest PA beta ROM since ages and dirty flashing this kernel since r34 via FKU. No issues, no srtuttering, no sod... Keep going franco! This kernel + my tweaks (combination of vomer's and gingerbread's) + greenify = super battery.
[Nexus 5 Original Android Development] hello00:
been using r40 with no SoD yet..
[Nexus 5 Original Android Development] granets:
Hello, A friendly tip. You can wrap your images in "[hidе][/hidе]" code (as I did above), to hide them, so they don't take the whole screen when you post :)

Have a good day
[Nexus 5 Original Android Development] franciscofranco:
On other devices I've made more mistakes so had to release more versions. I don't do as many mistakes as I did.

myfluxi tried that and the results were not good and the display appeared all jammed.

Ok that's useful! I think I know what might be then! Might be the video decoder core, I merged some patches on r38 for it and those SoDs according to some started on r38.
[Nexus 5 Original Android Development] franciscofranco:
People with those strange SoDs can you test this please: http://192.241.177.15/Nexus5/4.4/tests/boot-test41.img thanks.
[Nexus 5 Original Android Development] Red5:
R39 has been so good for me the past few days. I dont even want to try r40. R39 is super smooth and scrolls great. Ive been playing a game and Ive noticed if I scroll down fast, its sort of jittery, and has been on several builds, but r39 took that away. Im happy. Not one SOD either.
[Nexus 5 Original Android Development] franciscofranco:
Flash r40, its just a bug fix release, that smoothness thingy you feel is still there, I didn't remove those patches, I love them.
[Nexus 5 Original Android Development] floepie:
2 occurrences with SOD on r40 but never before r40. Both times when I left my home WiFi. Everything at stock kernel settings. Was not playing videos however. Hth.
[Nexus 5 Original Android Development] franciscofranco:
Just re-posting this on the new page.
[Nexus 5 Original Android Development] kufikugel:
Just a FYI merged the vidc patches as well into slim kernel and we did not get any SoD reports till now. Does not mean it cannot be the case just wanted to share my experience with them.
[Nexus 5 Original Android Development] tsubus:
FYI: me and a buddy of mine run the exact same setup with linaro-compiled kernel. I have no issues whatsoever, he gets the random SoD (sorry, no log of that...and he's reverted to r37 since then). This is just to disregard the notion that linaro kernel is fine.
[Nexus 5 Original Android Development] wvcadle:
I'm experiencing the same thing. FKU not only crashes, but it disappears from the app drawer and Apps in Settings. It even uninstalled itself (or something uninstalled it), because when I went to the Play store, it gave me the option to install it again.
[Nexus 5 Original Android Development] franciscofranco:
It doesn't uninstall itself -.-
[Nexus 5 Original Android Development] wvcadle:
Not to be a fanboy, but you always get it worked out. Nothing more than a hiccup. I'm happy.
[Nexus 5 Original Android Development] menboi1:
Thanks Franco

I will give you my review as soon as possible
[Nexus 5 Original Android Development] spelaben:
Just had a SoD with r40, trying test41 now. Logs attached, maybe there is something useful in there. Thanks!
[Nexus 5 Original Android Development] Johnny424:
I have seen titanium backup do this before..no personally with fku but other apps..especially when converting an app back to system once its been updated through the market
[Nexus 5 Original Android Development] gee2012:
Quote: [maybe there is something useful in there]

Now that sounds a bit arrogant imo, who says its soley kernel related as not all users suffer from this SoD issue :)
[Nexus 5 Original Android Development] franciscofranco:
If it never happened before and users didn't change anything else rather than the Kernel then its a Kernel issue and we'll find it and fix it ;)
[Nexus 5 Original Android Development] big_adventure:
You think he meant that arrogantly? I didn't - it seems like someone actually trying to post logs (as we all always beg) and then legitimately hoping that it helps. We really shouldn't be assuming bad juju about people who actually do post logs instead of complaining about phantom problems, should we? Plus, he actually posted non-kernel logs as well (not that they are useful in this case, as they are all post-reboot).
[Nexus 5 Original Android Development] daniel84cs:
Personally I had no problem with all versions from 38 to 41T. I've never had a SOD since I reached my limit of UV ... I never had the CPU fixed at 1.5 ghz, use the default setting since I have not found great improvements with UC and changing settings the governor and dell'hotplug. To 99% of the SOD are caused by low voltages.

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] gee2012:
Yes, you`re right. I missread and assumed he meant something usefull in the 41 test build instead of the logs. My bad and apologies to the user i quoted :o

[MENTION=4212629]spelaben[/MENTION] Sorry mate for my comment, missinterpreted you post mate :)
[Nexus 5 Original Android Development] KuChar_:
Looking forward, i just had SoD on r40. Flashing r41-test..
[Nexus 5 Original Android Development] big_adventure:
In general, I'd agree, but in this specific case, there are a number of people apparently running default settings who complain of SoDs and only since r38 or r39. Their only change was the kernel, with no settings mods. Which is why I recommended trying overvolting earlier for people getting SoDs.

---------- Post added at 06:44 PM ---------- Previous post was at 06:42 PM ----------

If only my worst internet foibles were as minor as misinterpreting the tone on something in a forum. :)
[Nexus 5 Original Android Development] WatsonDue:
I got a sod too,two days ago with r39. All stock, no underclock or undervolt, standard settings in fku (changed only the hotplug threshold to 0). The event is very rare, but it's there. Last kmsg says only "reboot by key" , so it's pointless to post it! I'll try the new test kernel, thanks Franco.

Inviato dal mio Nexus 5 utilizzando Tapatalk

---------- Post added at 06:44 PM ---------- Previous post was at 06:44 PM ----------

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] GHOSTIVVI:
I'm running latest PA ROM along with r37. R38,39,40 were all stuttering to me and didn't really notice any difference in battery for the couple of days I was off r37
[Nexus 5 Original Android Development] daniel84cs:
Then they will make a different use of the device and we can not reproduce the problem ... I use for more than a month with the Paranoid ART runtime and Franco (a "heavy" UV) never had SOD and reboots .....

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] menboi1:
Using r41 test last 1 hour and seems to be fixed the sod, but i will give you more details in the day

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] armymax:
Second SOD... Using r39 (UV: -25; vibration: 80), PA 4.2 beta 2, dalvik
[Nexus 5 Original Android Development] chrisch91:
Sry for the noob question, but what is sod?
[Nexus 5 Original Android Development] vomer:
https://en.wikipedia.org/wiki/Sod
[Nexus 5 Original Android Development] Miz_Buzzer:
Just had a SoD with r40 (installed the kernel around 1 hour ago). Had to go into fastboot and start the phone. Running PA with stock settings.
[Nexus 5 Original Android Development] lolz mclollerson:
sleep of death. meaning screen off and it won't turn back on when you press power.
[Nexus 5 Original Android Development] menboi1:
for who have sod in other release try using r41 test and give your review to franco http://192.241.177.15/Nexus5/4.4/tests/

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] bobloadmire:
I'm on PA with r40 and no SOD problems. R39 either.
[Nexus 5 Original Android Development] CarlosAbia:
Having big 1013 audiofix wakelocks with r40. Not complaining, just reporting!! Thanks
[Nexus 5 Original Android Development] Red5:
You beat me to it.
[Nexus 5 Original Android Development] IAreKyleW00t:
Didn't have any SOD issues with r40, but I just flashed t41.

Also, is it required/recommended to wipe dalvik+cache after each new flash? I know some kernels recommend doing that.
[Nexus 5 Original Android Development] vomer:
Great minds think alike! :p
[Nexus 5 Original Android Development] mp187263:
Experienced intermittent SODs starting with r38. Usually when going into standby and back again several times in succession. So far no issues with r41. UV -50, the rest stock.
[Nexus 5 Original Android Development] tkalli:
Franco says not necessary.
[Nexus 5 Original Android Development] franciscofranco:
Absolutely unnecessary and unrelated.
[Nexus 5 Original Android Development] big_adventure:
It's not just that Franco says it - there cache and Dalvik are userspace stuff, so wiping them will change all of nothing when it comes to a kernel.

I have never wiped anything for a kernel or for a ROM upgrade (most of which clear cache and dalvik themselves), and usually don't wipe anything (not cache, not data, nothing) even for a rom that fully changes base. Wiping is completely overrated and mostly useless UNLESS you have a specific problem that you can't diagnose. Wiping should generally be almost a last resort, not a default behavior.

/End rant.
[Nexus 5 Original Android Development] Laggalot:
test 41 is soooo daaamn fast i dont even get it !! noticed it immediatly after the boot!!! so responsive and so smooth animations!!

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] Enddo:
placebo?
[Nexus 5 Original Android Development] defffizz:
R40 working flawlessly!

Bright Red Nexus 5, franco
[Nexus 5 Original Android Development] psp9000333:
I don't understand how you guys managed to get SoD on r40. I was on r40 and I never got it, even undervolted minimum frequency to 675 mV. running t41 just because.
[Nexus 5 Original Android Development] WatsonDue:
Maybe because probably the sods are not "undervolt" related. Kernel is not only a matter of mV.

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] Red5:
Are people having SoD when their phone is plugged into something, like wall charger/computer/car?
[Nexus 5 Original Android Development] LRC1710:
I keep getting black screen not turning on until a reboot issue, had it on r39 and still have it in r40, running PA latest beta and stock settings in fku
[Nexus 5 Original Android Development] PetritH:
Franco posted a test version, maybe it has this issue fixed, give it a try, few pages back
[Nexus 5 Original Android Development] jv.batista:
I had 2 SoD in r39 with completely stock kernel options. on r40, until now, I didn't have any SoD...
[Nexus 5 Original Android Development] lolcopter:
EDIT: actually YES, the phone was charging via USB cable prior to the r40 lock up, but had been unplugged hours before it happened

On r39 I was using my phone doing reading stuff, pocketed it, and once I got out of the elevator it just wouldn't wake back up.

The second incident on r40, my phone was in airplane mode for alarm clock use, I had woke up in the middle of the night, unplugged the charger, and changed the alarm from a set time to "smart alarm" in SleepBot. The alarm went off as planned however the screen did not light up or respond and the alarm didn't quit until a forced reboot by holding the power button.

Both were one off occasions that I could not reliably produce again, and only one instance on each version.

Have since reverted to r37 in the meantime without issue aside from the annoying auto dimming that was fixed in newer versions. Performance wise no complaints at all, only the one off SoD's with both 39 and 40. Nothing video related here afaict