yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] dastinger:
Probably. Unless he was coming from an earlier than r38 version.

Anyway, there must be something related on the phones of people that are experiencing SODs. I never have experienced any SOD since I've got my Nexus and it never ran any kernel other than Franco. Also, kufi from Slim team said they merged the same commits as Franco regarding video and I've never seen any SOD report over at the Slim thread. Really weird.
[Nexus 5 Original Android Development] david279:
I just got a SOD on 40. Very random, First time ever getting one..Using all the stock settings in FKU. I when to my car came back in the house and it wouldn't come on.

Here's a last kmsg

pastebin.com/LsEQPNt9
[Nexus 5 Original Android Development] The Gingerbread Man:
All fine here for me ;)
[Nexus 5 Original Android Development] fbf2201:
Outdated [emoji6]

Try the new r41 test build
[Nexus 5 Original Android Development] Red5:
I just had one, my phone was plugged into my computer. Im wondering if being plugged in has anything to do with SoD.
[Nexus 5 Original Android Development] i860:
Don't want to speak to soon but i am on r40 with 15h and no sod.
[Nexus 5 Original Android Development] jdec529:
Those that are getting SoD. Try the new test kernel that Franco posted a few pages back
[Nexus 5 Original Android Development] franciscofranco:
Try r41 test please :)
[Nexus 5 Original Android Development] castaway1:
I should say that SoD is apper for me 1-2 times a day so this testing need time before some conclusion. (runnig r41t).
[Nexus 5 Original Android Development] danibri82:
screen wont turn on, i'm assuming i gotta wait it out till the battery dies?
[Nexus 5 Original Android Development] aavvaallooss:
One SOD yesterday with r39. Need to force reboot. Is it possible to get a log after rebooting or it will be 'erased'? 24h on r40 without problems. If it happen again I'll try t41
[Nexus 5 Original Android Development] EmperorX:
Not sure if sarcasm or not?

If not... Hold the power button for 10 seconds
[Nexus 5 Original Android Development] lolcopter:
My r40 logs after reboot worked earlier
[Nexus 5 Original Android Development] danibri82:
first phone I've ever had w/out physical buttons or a removable battery. this is for realzies.

also the other night was the first time I changed my kernel in my N5 since purchase.

thank you for the help.
[Nexus 5 Original Android Development] Savant:
Easy phone to use and mod without any problems.
[Nexus 5 Original Android Development] aavvaallooss:
Hold power alone didn't help to me. Holding both power AND vol - forced reboot (battery pull emulation)
[Nexus 5 Original Android Development] psp9000333:
if you guys are having trouble with the SoD, it's probably because you overclocked too high. try underclocking or setting the speed to default.
[Nexus 5 Original Android Development] lolcopter:
You must be new around here :D
[Nexus 5 Original Android Development] shreddintyres:
Just got a SOD on r40 as well, min and max freq locked to default frequencies using FKU, no changes to UV, all settings are the same as default with exception of input_boost_freq being lowered to 960000.

Running slimkat official 4 build 3700, ART, ViperAudio, greenify but only user apps no system apps, no other mods

SOD occurred when i turned off my phone after sending a text message then i received a notification after which I attempted to turn the phone on (time frame of <1s after notification arrived. SOD. Waited 3 minutes in case it was just a random race thing no success, hard reboot from power key. I looked through last_kmsg didnt see anything pertaining to trying to set the max cpu to 3GHz as some one else had noticed before (my apologies i cant recall who it was).

One thing that did jump out at me was a line where the cpu reports numerous tasks REFUSING to idle/terminate (idk what teh proper jargon is here)

Last_Kmsg pulled as soon as i could after reboot. I dont have ADB set up on this laptop so i was unable to pull a logcat during the incident.

hope this helps.

- Cheers

ps thought i should also add that this SOD occurred after having r40 up since release. first occurrence for me.
[Nexus 5 Original Android Development] danibri82:
nope.

HTC Hero --- HTC Evo Shift - iPhone 4S - Galaxy Note 2 - iPhone 5 - Nexus 5 - Galaxy Note 3

last three are currently in my stable Just knew how to resolve this sort of issue with my Sammys, but not the Nexus.

I appreciate the trick I didn't know prior.
[Nexus 5 Original Android Development] xlys:
Franco i don't have any issue with r41 (no SOD), before i have it almost every 2 or 3 hours, so the best thing is put r41 in normal version to poeple don't read this thread is crazy how to many poeples complain and don't read r41 is out in test version for this problem.
[Nexus 5 Original Android Development] lolcopter:
lol no the guy guessing all the SoD stuff was because of over clocking. Multiple confirmations of SoD without any oc/uc itt
[Nexus 5 Original Android Development] ChazzMatt:
Nope. No overclocking, the Snapdragon 800 chip on the Nexus 5 is fast enough. :good:

Had 2 SODs on r39, but none on r40. However flashing test r41 now to ward off evil. :)
[Nexus 5 Original Android Development] Piereligio:
Oh, the day when v7 would have overcame v5.5 has come earlier of than I was guessing. There's been a second downloads'boom. Cool! I appreciate this, my work has been useful. It's cool to thinking about the fact that at least 4 hundreds nexus 5 in the world have my profile on. :D

EDIT 5 years later: Meh, 400 downloads aren't that many, compared to what aospUI has done. :)
[Nexus 5 Original Android Development] psp9000333:
alright, explain how I got a SoD from over clocking, with stock voltages? its a part of something along with voltages.
[Nexus 5 Original Android Development] gee2012:
Hold the power button for 10-15 seconds and the phone will reboot.
[Nexus 5 Original Android Development] ben_pyett:
Sod on r40 not plugged into anything, just sitting on the table

Loading r41 test
[Nexus 5 Original Android Development] vomer:
Congrats buddy :)

Sent from my Nexus 5
[Nexus 5 Original Android Development] crkone:
Stock settings and stock rom and had a reboot while using Tune in Radio in my pocket. Phone was stuck at the nexus boot screen. Held down power button to fix it. Just flashed to test 41.
[Nexus 5 Original Android Development] cdx47:
On my phone I was stuck on your version 2 as that was very close to perfect. At last your version 6.6 is almost exactly gamma 2.2. Looking forward to trying version 7 but I can't see it being better than 6.6. But then I said that about all the versions before version 6.

Good job!
[Nexus 5 Original Android Development] spelaben:
Just had a SoD with the new t41, logs are attached. Thanks for looking into it.
[Nexus 5 Original Android Development] cdx47:
I am coming late to this discussion but won't the individual characteristics of your screen affect the readings you get? For example up until recently only Piereligios version 2 got me close to 2.2 while others had better luck with later versions.
[Nexus 5 Original Android Development] FAdrums:
I'm one of them! [emoji41]

Rocking v7! Thanks for your work!!!

Enviado do meu Nexus 5 através de Tapatalk
[Nexus 5 Original Android Development] franciscofranco:
Damn, now that's unfortunate.

Looked into the logs and found absolutely no reason. Now this hard.

out_write: error -1 - cannot write stream data: I/O error

That coming from the AudioFlinger is not good news, but that's Android userspace. I see the write was blocked for 15s, was that the amount of time your music stopped?
[Nexus 5 Original Android Development] The Gingerbread Man:
I must admit I didn't count to be honest, it certainly could of been.

I captured another log, I cleared the log cat and screened off and almost instantly another happened, could of been about 5 seconds pause maybe, here's the log for that and saved as the pause finished https://docs.google.com/file/d/0B2ar5BB6clkDREJnVFh1UGxOamc/edit?usp=docslist_api (pastie.org seems to be having an issue saving that for some reason.) It seems to be full of camera ****ting its self mostly which at the time don't have anything to do with camera open, only using face unlock screen lock. I tried not using that before and didn't help.

Next time I'll count the seconds paused if that helps.
[Nexus 5 Original Android Development] franciscofranco:
Yeah that's AudioFlinger's ****. I don't know why it says I/O error to be honest, I know nothing of the higher level shared libs. Just because can you change back to CFQ and try to reproduce it? Just because.
[Nexus 5 Original Android Development] The Gingerbread Man:
Changed to CFQ and not had the music completely pause yet but the skipping seems more frequent, quite poppy also like the headphone jack is being interfered with. This log contains some stuff about storage errors and a whole load of camera ****s https://docs.google.com/file/d/0B2ar5BB6clkDYjRIRU91Q1N3ODg/edit?usp=docslist_api larger than 64k so pastie.org won't allow
[Nexus 5 Original Android Development] franciscofranco:
Can you change the readahead value to the default 128 please? Path is /sys/devices/virtual/bdi/179:0/read_ahead_kb. Thanks.
[Nexus 5 Original Android Development] vomer:
Nice catch! I just had a few of these 15-20 sec pauses/skips on r40. Really weird :eek:
[Nexus 5 Original Android Development] scrack26:
I updated to r40 using auto flash from FKU, then everythings going well, not until today, after fully charge, i just rebooted the phone by selecting reboot, then im stuck, screen is not opening when i press power button, when i connect the USB on PC, it just make sounds like usb connection but, i check on adb devices nothing is listed. please help :(

---

Edit: Did the Volume Down + Power, it booted again, but this time i reverted back to r38.
[Nexus 5 Original Android Development] franciscofranco:
Beyond this there's not much I can do. You've tested with stock Kernel/stock rom and it still happens. As I said before the audio stack is busted and I'm sure there's some work to be done on Hammerhead's DSP driver. Something similar happened on the Nexus 4 when it was released. I know nothing of the audio stack to help.
[Nexus 5 Original Android Development] The Gingerbread Man:
Ya, thanks for looking again. Hopefully the guys at Qualcomm are putting as much effort into the DSP as they are with these monthly dev GPU drivers. I'm glad I have finally got a log of the issue, changing log cat app helped.
[Nexus 5 Original Android Development] J_Whit85:
I've had issues with cfq and music skipping. I switched to noop and it went away. I also have my read ahead set to 1024
[Nexus 5 Original Android Development] :
Is anyone else still getting stutters whilst playing music with the screen off? I'm on r38, with stock settings, using Shuttle+ player.
[Nexus 5 Original Android Development] The Gingerbread Man:
This is what iv been talking about for the last page or so. Even noop the pausing is still going on.

If you could star the issue I created on Google bug tracker that would be great https://code.google.com/p/android/issues/detail?id=68275&thanks=68275&ts=1396915086 . The more stars items receive the greater priority things are given (generally).
[Nexus 5 Original Android Development] Therion87:
Starred
[Nexus 5 Original Android Development] Hatshipuh:
Is this a common issue?

Because I don't have it with stock settings and PlayerPro. Actually never had with any version of franco's.
[Nexus 5 Original Android Development] bigknowz:
Off the reservation

Couldn't deal with the stutters, music is too important to me. After trying workarounds for over a month, I tried faux. It does not have the leaving wifi / screen off stutter issue. There is very slight static when exiting airplane mode, but its fixed by having Tasker switch to performance governor prior to exiting airplane and then back to interactive after 30 seconds. [MENTION=3292224]franciscofranco[/MENTION], maybe faux has some thoughts on a possible resolution?
[Nexus 5 Original Android Development] franciscofranco:
I don't know his code but its possible he's not blocking other cpus to come online during screen off which is the workaround to prevent this from happening, but then the drain will be bigger as every couple milliseconds the resume/suspend cycle kicks and when that happens the Kernel enables and disables the boot cpus every time. That did not happen ever on other devices that I've been supporting so my guess still stands, theres a major problem on the audio stack on Android + this device.
[Nexus 5 Original Android Development] :
Starred. Is it a Google fault? I haven't actually played with the Stock kernel or any other; I flashed Franco within 7 minutes of receiving my phone, so I don't know where the problem lies, exactly.

I've always had issues with music playback, back from the r20s. I always thought it was the player I was using (Poweramp), and after I switched to Shuttle+, the stutters did reduce. It's become worse since I flashed r36-37, though. I always thought I was the only one with this problem because after r32, people stopped complaining about the stutters. And recently I've been getting stutters even when the screen is off.
[Nexus 5 Original Android Development] franciscofranco:
Because on r32-r35 I merged a TON of audio stack patches from CAF which fix a lot of code and behaviour. I had to revert them later because a small group of users were having problems with right earbud losing sound after a while and I simply could not reproduce or fix it. That's why I keep saying there's a problem in the audio stack and a problem with the audio subsystem on the Nexus 5. I simply cannot wait for 4.4.3.
[Nexus 5 Original Android Development] tcat007:
Was on r39 with no issues, flashed r41, no issues. No stutter or stops with G Music, using Viper.

Wow, scrolling is so smooth and fast, even in tapatalk and Facebook!
[Nexus 5 Original Android Development] wendiko:
I'm using #40 was #39 before. No problem with SOD or with sound. I walk for 1:30h at the beach every day listening to music.

Stock rom and default settings at Francisco's kernel

Enviado de meu Nexus 5 usando Tapatalk
[Nexus 5 Original Android Development] :
So is the issue prevalent on the stock kernel as well? Or is it that the low power tweaks you've implemented are causing this?

Also, besides the music issue, I've noticed a slightly higher battery drain on r38 as compared to r36-37. I'm holding off on upgrading to r40 because of the SOD reports I've read. Is there something you've done between r37 and r38 that could be causing the battery to not be as efficient?
[Nexus 5 Original Android Development] psp9000333:
[MENTION=3292224]franciscofranco[/MENTION] when 4.4.3 comes out, are you going to rebuild the kernel from that?
[Nexus 5 Original Android Development] LRC1710:
What does SoD mean?
[Nexus 5 Original Android Development] Mo'HAWK:
Screen of death.
[Nexus 5 Original Android Development] Technecium:
search or die... jk

screen of death
[Nexus 5 Original Android Development] crford:
Sleep of death. When it won't wake up from sleep.
[Nexus 5 Original Android Development] franciscofranco:
Even on stock music playback is not flawless.

I don't have any battery drain.

I don't plan to, but if Google does some crazy **** then I'll have to.
[Nexus 5 Original Android Development] Mo'HAWK:
With the rumors of the next update being a fix For different things I doubt that you will need to rebuild but who knows until it's released.
[Nexus 5 Original Android Development] maverick_hunter:
Screen of death on test r41. Logs attached.

PA beta 3, just listening to a podcast when she refused to wake.
[Nexus 5 Original Android Development] RobbieL811:
Say I were to ship you an N5 that has confirmed the skipping & right earbud cutting out completely on 33. Could you fix it then? I have an extra N5 sitting in my backpack. I could flash 33 & make sure it's the one that does it & send it to you. Would you be able to return it?

Edit - Or is it not worth it now?

Sent from my Nexus 5
[Nexus 5 Original Android Development] Annihlist:
SOD r41. No undervolt

https://www.dropbox.com/s/qsh71qxgif8pldd/last_kmsg
[Nexus 5 Original Android Development] mibtnt:
Wait. I am not the only one got the SOD. nice. Will see if r40 has it. I tried stock today. Didn't go too well

---sent from a N5 on PA4 + Franco's kernel
[Nexus 5 Original Android Development] vomer:
It's weird I have not had any SoD so far. There must be some common denominator with people getting it...

Sent from my Nexus 7
[Nexus 5 Original Android Development] msgfromside3:
I had my first sod in this mornong since I ran r40 when it was first released. I had beeb wondering why ppl was getting sod because I didn't for at least 24 hours. Flash r41 test and so far no sod nor any issue. But I think there is something triggering it. Fyi, I am running all stack and gb with expose.
[Nexus 5 Original Android Development] IAreKyleW00t:
I haven't gotten one either. Never got one on r39, r39, or r40. I'm using t41 though and it still seems just as good.
[Nexus 5 Original Android Development] daniel84cs:
+1

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] jmudrick:
I'm not sure it's weird, I mean there are hundreds of people running this kernel (I'm presuming), if somebody's phone goes ape**** it seems people are more likely to post here than on Mark Zuckerberg's Facebook page that a FB update is messing with your N5, and if you have no problem you are likely not to post about a non-event. I presume that most people, like me, don't have the problem, and that it only emerges given a complex of circumstances which is hard to figure out given that we have no idea how everyone on the kernel is using their device, especially what combination of apps and settings might be contributing.
[Nexus 5 Original Android Development] Laggalot:
must be it ..... i know there were not that kinda changes, but it just feels much better

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] choosetobelieve:
Hi Vomer,

I am trying to use Team win version 2.6.3.4 to flash your vomertweaks zip file but the error occurred during flashing. The error was binary error. In addition, you mentioned that we can use:

Open Terminal Emulator

Type: su -

Type: sh /sdcard/Download/01VomerTweaks

When I tried and error: permission denied occurred.

I found that there is raw text about your settings. Is raw text settings same as 01VomerTweaks,If they are the same, I do not have issue with modifying figures mannually. Thanks
[Nexus 5 Original Android Development] big_adventure:
To answer for him, yes, the raw text information is the same as the zip - you can mod your stuff by hand and get the same results.
[Nexus 5 Original Android Development] choosetobelieve:
Thanks!
[Nexus 5 Original Android Development] RobbieL811:
You need to update TWRP. That's why you are getting the error. It has been posted in this thread.

Sent from my Nexus 5
[Nexus 5 Original Android Development] big_adventure:
[MENTION=1363323]vomer[/MENTION]

I theorized earlier that it was linked with something in hotplug or a voltage derp at high freqs - basically, people like you and I, running 4 cores on and max cpu reduced never have the issue. I've read every last_kmsg of the derp posted to the thread, and there just isn't anything really conclusive there. Having a logcat taken during the sod could help, I guess, but that's going to require someone plugging the phone into a computer before rebooting.
[Nexus 5 Original Android Development] Tung_meister:
Just experienced my first SoD running t41
[Nexus 5 Original Android Development] AmmarGitham:
Got a SOD on r39. last_kmsg attached.
[Nexus 5 Original Android Development] silvan g:
Starred:)
[Nexus 5 Original Android Development] chikimonke:
I would agree. People should post the ROM and any other tweaks (xposed for instance) they are using, as well as the bin their chip is from. I know I personally have one of the lower quality ones, never could under volt stably and I believe I even have a higher stock voltage because of it. I was also having SODs on 39, though things looked good on 40 and I haven't given 41test a try yet.

Edit: My info

Latest SlimKat

Stock Franco settings, Mag01 color profile

Xposed for Greenify only

PVS Bin 1
[Nexus 5 Original Android Development] federikk90:
horrible battery drain in r40 ...
[Nexus 5 Original Android Development] tuncan:
On my phone I didn't notice any SOD (Franco Kernel 40 and Cataclysm ROM).
[Nexus 5 Original Android Development] topgeardave:
Only ROM/Kernel that has no sound derping is CAF based ROMs such as CM. Think CAF repos have fixed it
[Nexus 5 Original Android Development] fbf2201:
Could be anything (kernel, apps, system)... Your post doesn't help at all, unless you provide some logs (BetterBatteryStats for instance).
[Nexus 5 Original Android Development] federikk90:
don't think so, being on franco since begin of development of this kernel. i am fine with r36, so i think i'll stay on this release until a new one will come out
[Nexus 5 Original Android Development] fradbari:
Hi, anyone know if last f40 works on beta 4 paranoid?

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] big_adventure:
A number of people actually HAVE posted such things. At least two people have sent that they are running stock roms, stock settings, and they included enough dmesg to see that their PVS is 2.

I run PVS 2, stock rom, custom settings, never have seen a SoD, despite, effectively, trying to.
[Nexus 5 Original Android Development] Momotani-Hitoshi:
Pretty sure you haven't done anything specific to fix the issue with encryption, but just to update on the latest builds. r32 still works with encryption.

Tested R40 & R41test on my device with encryption, still having SoD. Attached logs. Last line on kmsg still "PM: Syncing filesystems".
[Nexus 5 Original Android Development] Ramone360:
Nice! What's your profile? Sorry if I'm late
[Nexus 5 Original Android Development] jv.batista:
Just had a SoD right after connecting the phone to the pc. Just changed to scheduler to row, everything else is stock and I'm using r40

Will post the log as soon as I can.
[Nexus 5 Original Android Development] Enddo:
same here. with no change in usage. i was getting half the battery life I would normally get in the first 20% of drain

reverting to r38 and it instantly gave me back the type of battery life im used to(i was on r39 before and it too gave me much less battery life)

an no, it's not a rogue app or service. i keep a keen eye on BBS logs and use extremely conservative kernel tunables. i could have let it do a 0% drain to recheck. but after reverting back to r38 and seeing the battery life that im used to instantly come back, I doubt that would have helped
[Nexus 5 Original Android Development] irro94:
Why there are only 2 governor (Performance and Interactive)?
[MENTION=3292224]franciscofranco[/MENTION]

thanks :)
[Nexus 5 Original Android Development] zephiK:
As said by Franco, because those are the only governors that are needed. He believes including all other governors like (wheatley,lazy,smartass,smartassv2,etc) are useless and are just a waste of space. Interactive is his recommended governor as performance is usually used towards benchmarking or whatnot even though this isn't a benchmarking kernel. Interactive is highly optimized with newer patches from Google so its not 100% stock interactive

On N4, he experimented with using ondemand.

Edit: Well he didn't say it like that, I kind of paraphrased it :p

use search next time, http://xdaforums.com/showthread.php?p=47401262&highlight=governor#post47401262 is his post. I kinda added more to what franco said. Upon doing research on my own, I believe hes putting stock ondemand back in when a user requested not too long ago so maybe it'll be in r13? but end of the day, interactive is where its at.
[Nexus 5 Original Android Development] irro94:
sorry i have another question: the FKU app v11.0 is the beta version? thanks!