yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] Tzfardaya:
Somewhat common error...

Just add

chmod 664 /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

Above the echo to scaling_max_freq line in the script....
[Nexus 5 Original Android Development] Pichingo:
Same identical thing happened multple of times. I'm undervolting 75mv across the board. I never had this happening since Franco started his Kernel on the N5.

I do have xposed installed with Gravity,greenify,minguard,GEL and youtubeaway installed.
[Nexus 5 Original Android Development] h4m74ro:
r38 and r39 with stock settings have lots of lag in a game I play (8 ball pool). Back to r37 for now.

Edit: also laggy with VomerTweaks
[Nexus 5 Original Android Development] floepie:
Running kernel with all default settings - no OC, UV, etc. Core 0 remains at 1.5 Mhz as long as screen is on. This has been reported before by others, but not sure whether these reports were associated with altered tunable settings, but completely default here. So, SOT times has been reduced by about 20% for r39 compared to r38.

Additionally, according to CPU stats, the only CPU freq used is that very 1.5 Mhz, besides deep sleep. No other CPU speeds are used.

Screenshot.
[Nexus 5 Original Android Development] ibilln:
Had twrp 2.6.3.4. Installed 2.7.0.0. Worked. (!)
[Nexus 5 Original Android Development] floepie:
Hey, just wanted to share that I cleared up that "stuck at 1.5 Ghz or deep sleep" problem as I have been seeing. I simply uninstalled the FKU app and reinstalled. I could probably have simply cleared data for the app, but now all the CPU frequencies are being utilized and core 0 returns to 300 MHz while screen on.
[Nexus 5 Original Android Development] dead90:
For everyone who s having problem with vomer zip, you have to update twrp with 2.7.0.0 version

Tapatalked with my N5 Franco Pure
[Nexus 5 Original Android Development] venelar:
Can someone who is proficient at diagnosing a last_kmseg have a look at this? When i power on my phone from being off, it'll always reboot once, then it's good to go. Just curious as to whats causing it.
[Nexus 5 Original Android Development] gustavo_pr:
Can confirm this. Has restored r37, and flashed again r39 and cleared FKU app data. Frequencies are looking more as usual. Stock settings.
[Nexus 5 Original Android Development] ROADKING17:
Black screen r39 stock
[Nexus 5 Original Android Development] wendiko:
I have the same problem. Will try to clear the data.

=========

Ok I clicked the clear data inside FKU and looks like it fixed. I am out of battery for now but I'll keep an eye on it.

+++++++++

Before my battery end I want to report that I am still locked at 1.5

Enviado de meu Nexus 5 usando Tapatalk
[Nexus 5 Original Android Development] franciscofranco:
Pushed r40:

* Fix a couple issues introduced with r39
[Nexus 5 Original Android Development] choosetobelieve:
Hi Franco,

For your view, is there any change in terms of battery life and performance since the version 32? Thanks
[Nexus 5 Original Android Development] BTT8:
Haha of course he's going to say yes!
[Nexus 5 Original Android Development] wendiko:
Flash the #40 did the job for met at stuck @1.5ghz

Enviado de meu Nexus 5 usando Tapatalk
[Nexus 5 Original Android Development] menboi1:
In last r39 and r40 always the screen gones black and i have too boot in recovery using vol up vol down and power button) :/ then i have a bootloop i need to flash the rom im using for boot again

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] laureanop:
Francisco could those issues introduced in 39 cause SOD. ?? Never had any reboots on the N5 but yesterday I had two sod s with 39 ( sorry I was busy at work and couldn't get a log )
[Nexus 5 Original Android Development] WettbackMartyr:
I'm not a fanboy by a long shot, but I am a realist and have to say there is no point in being sensitive about [MENTION=3292224]franciscofranco[/MENTION] and his response. It was matter of fact. He's a matter of fact guy. I can relate so maybe that's why I wouldn't take what he said personally. He's just shooting straight with you guys. Be cool everyone.
[Nexus 5 Original Android Development] Tzfardaya:
No worries, if they can't understand that battery life varies depending on the situation and usage, then they'll never be happy with the work from any kernel dev...

Oh, and people, watch how you edit the quotes... they're being misattributed...
[Nexus 5 Original Android Development] NYCHitman1:
Orrrrr people could stop being so damn sensitive all of the time. Grow a pair, folks.

Yeah, there was an issue with quoting on the application. That wasn't meant for you.
[Nexus 5 Original Android Development] Tzfardaya:
Please stop quoting me with things I haven't said... :(
[Nexus 5 Original Android Development] franciscofranco:
We know it wasn't you ;)
[Nexus 5 Original Android Development] Bhonka:
Mine boots fine but as soon as you hit the power button the screen goes black and wont return.

Tried rolling back to older firmwares and the same thing happens now...
[Nexus 5 Original Android Development] franciscofranco:
Something else might've gone bonkers, maybe not Kernel related? I have no problems.
[Nexus 5 Original Android Development] EmperorX:
I just had what I think he is referring to. SoD? Got an email, went to turn the screen on, totally black. Had to hold power to reset. Third time since yesterday that this has occurred, no changes other than kernel. The two other occurrences did not involve me getting a mail, just reaching for my phone to turn it on and getting the same results. Just upgraded to r40 so hoping for the best. Let me know what I can do to help solve this
[Nexus 5 Original Android Development] alcurtis93:
I'm getting these very often lately. Started on r38 I think. Again stock ROM and not a single setting changed in the fku app apart from colour profile
[Nexus 5 Original Android Development] vomer:
[MENTION=3292224]franciscofranco[/MENTION] r40 seems to have fixed that frequency stuck problem :good: thanks!
[Nexus 5 Original Android Development] franciscofranco:
Let us know if it still happens with r40.
[Nexus 5 Original Android Development] EmperorX:
Will do!
[Nexus 5 Original Android Development] psp9000333:
great work on r40! i honestly dont know how you got to version 200 - 300 + on some devices...
[Nexus 5 Original Android Development] Fluidification:
[MENTION=3292224]franciscofranco[/MENTION] is there a way to incorporate a display gpio reset in the early boot stages of the kernel so that the display will come on already color coordinated
[Nexus 5 Original Android Development] menboi1:
still happening in r40
[Nexus 5 Original Android Development] Asuppa180:
Just got a SoD. Couldn't grab a log. But completely clean flash of FK and latest PA. Never experienced it, but I haven't updated since r37. This was on clean flash of r40. The SoD was on an attempted wake up.
[Nexus 5 Original Android Development] menboi1:
what is SoD?

Sorry for my ignorace
[Nexus 5 Original Android Development] prstorero:
Sleep of death. Pretty much just the device won't wake up from deep sleep.

prshosting.org
[Nexus 5 Original Android Development] Asuppa180:
Screen will not turn on from an off state. I don't UV or anything. Run stock settings except for I change vibration setting from 100 to 70.
[Nexus 5 Original Android Development] BTT8:
Running r39 on latest cataclysm with uv-100 across the board. 625 mv at 300. I am NOT having any issues. I actually have never had and SOD on any of the versions of the kernel. Just FYI
[Nexus 5 Original Android Development] Swiftks:
Franco, my phone is acting totally normal on r40. In fact, it may even be better than normal... What do you think the problem could be? ;)
[Nexus 5 Original Android Development] DarknessWarrior:
just flashed r40 from r38 and as soon as I flashed I had a SoD. Something's weird going on, I'll revert back to r38 for now, if I have another SoD I'll try to grab a kmesg
[Nexus 5 Original Android Development] big_adventure:
There are a lot of people mentioning SOD issues - has anyone posted a log? And maybe a detailed configuration? It's kind of hard to troubleshoot something without any information.
[Nexus 5 Original Android Development] Martin-Doc:
How are you going to grab a kmesg for the latest kernel when you are reverting to r38?
[Nexus 5 Original Android Development] joeyfong:
I do have sod problem since r38
[Nexus 5 Original Android Development] DarknessWarrior:
if it happens again before I get the chance to revert.
[Nexus 5 Original Android Development] hello00:
just flashed 40..lets see how it behaves
[Nexus 5 Original Android Development] menboi1:
Again i have a SoD in r40 since r38

i try to flash the rom for clean install of franco kernel but before i clean data of fku app in app directly. flash the last r40 and in 30 minutes after i have the black screen again

I use paranoid android and i dont have been this problem in a stable version before, only in test version

For daily use i will flash to r36 :/

ps: the only modification i use in franco kernel app is color control and per app modes, everything else is like franco set it
[Nexus 5 Original Android Development] Kookitza:
+1

I use Purity rom..
[Nexus 5 Original Android Development] JNewms:
You guys aren't helping though. You're not providing logs. Instead of switching to another kernel number grab logs and post them so that the root of the issue can be found.

I've never once had this SOD or whatever is being mentioned, so I have no logs to contribute. I'm running a personal build of purity right now.
[Nexus 5 Original Android Development] baedaa:
r40 SoD just happend while streaming youtube to my tv. tried to turn the screen on again to switch to the next video but it stayed dark

---------- Post added at 09:08 AM ---------- Previous post was at 09:06 AM ----------

calm. you're not helping either. franco asked if it still happens and people provided the answers
[Nexus 5 Original Android Development] menboi1:
easy bro
[Nexus 5 Original Android Development] Foggy79:
+1
[Nexus 5 Original Android Development] JNewms:
I'm actually very calm. I'm trying to tell you guys what needs to be done for it to be fixed. It's not affecting everyone, so I'm just speculating that it is probably a certain mod or something. But again, without a log no one knows. Do as you please, it honestly doesn't affect me either way.
[Nexus 5 Original Android Development] granets:
Guys I think I've had those SOD as you would call them, or something similar. A couple of times I tried to switch my screen on, but my phone didn't respond. So I waited 3 seconds, mashing the power button and voila. It started working like normal. Maybe the phone is so deep asleep it's hard to wake it? I never concidered it a problem, so no last_kmsg or log, but just getting that out there. I think when you get it, just be patient, count to ten and press the power again.

EDIT: This was on pre r40 kernels!!! No issues with r40 so far!
[Nexus 5 Original Android Development] menboi1:
i flash another version beacuse i will use my phone tomorrow and i need a functionaly version for ME. Thats beacause i dont can put a log

---------- Post added at 02:17 AM ---------- Previous post was at 02:14 AM ----------

my phone usually do that but since these days, my phone not wake up i need to use recovery boot buttons and flash my rom for the default kernel, and if i restart my phone without flash the rom i have a bootloop
[Nexus 5 Original Android Development] outofthisworld:
The majority of those experiencing SoD have given very little device setup info, let alone made an effort to post logs.

A few of you only now just mentioned that they weren't on stock ROM. Why not go on PA or Purity and mention you've had SoD.

If you're going to post here surely you're willing to throw as much info as possible into your post, it could help you find the common link.
[Nexus 5 Original Android Development] Enddo:
because that's what we need around here. apologists. with multiple ROMs being used by multiple people reporting SoD issues, it's very obvious that it's a kernel issue. quit making excuses

sure, they could have posted logs but saying it's the ROM and not the kernel is ignorant when there's so many reports here from people even on stock. you're no better than the people who aren't posting a log. congratulations :good:
[Nexus 5 Original Android Development] shinesthru:
This topic has been covered extensively. It's a good idea to search the thread before posting new questions.
[Nexus 5 Original Android Development] Cotw:
Just flashed r12. Great job on the new colors, love it.
[Nexus 5 Original Android Development] marcusva79:
Franco said that everything that the GN and Nexus 4 had kernel will soon be with the N5. His kernel has made the screen better and the sound. I know currently he is getting is apk ready in the play store to work well with the N5. Patience, should be coming soon.

r12 is working great. Lockscreen hiccups are gone. Battery life is great. Glad I got rid of my Note 3.:D
[Nexus 5 Original Android Development] KTT16:
So far r12 is great. SOT is noticeably better. When I wasn't sleeping, and reading up on development here, battery drain was much improved over stock.

I lost about 11% with over an hour of SOT, so that was really good for me. I think previously on stock after an hour I lost ~15%. Also brightness set at about 10%.

Great job Franco! Look forward to the FKUapp update. Will continue to monitor throughout the day to report back on typical day use vs. Stock.
[Nexus 5 Original Android Development] AndroidUzer:
Overclocking...

Do you think once things settle down a bit in the N5 world Francisco will add some options for overclocking?

I have noticed that most of the custom Kernels out there are playing it pretty tight to stock frequencies...
[Nexus 5 Original Android Development] nickj2010:
He doesn't do overclocking unless it's necessary, which it just isn't with this phone.
[Nexus 5 Original Android Development] Stevemeister:
Best battery life I've ever had on a mobile phone! My S4 didn't get passed the 5,5 hour mark. 6 hours 40 minutes SOT on a total on time off 1 day 14 and a half hour is just insane.

Let's see if r12 can get more SOT than r11.
[Nexus 5 Original Android Development] Bobtehblob:
Seriously guys! If you aren't getting great battery life then it's something on your end!

Here's my battery stats for the day. Listened to over 6 hours of music. Auto brightness set for about 80% of the time. Minimum brightness when I got home and was using my phone in the dark.

Most of my usage was reading via flipboard, falcon pro, Firefox beta, Instagram, Google +, quick office and of course Tapatalk. I also spent a lot of time texting/messaging in hangouts.

Location settings are set to device only and wifi always scanning is off.

Around half of my usage was at home (wifi), the other half at uni (wifi), with an hour of travel time (data).

-50mv undervolt across the board and GPU underclocked to 300mhz. All other kernel settings stock.
[Nexus 5 Original Android Development] bigbiceps:
Stock gives me only 3.5 hrs SOT even after 4 cycles. I restored my tibu backup from galaxy nexus(also had poor bat life). I also have 7 pages of apps.

Is there any problem with this?

Better bat stats hadn't reported any bad apps when using galaxy nexus...

What kind of average SOT are you guys extracting?

Sent from my H@mmerHe@d
[Nexus 5 Original Android Development] franciscofranco:
I merged: https://android-review.googlesource.com/#/c/70213/ last night and my Wi-Fi drain overnight decreased by around 4-5% from what normally does so expect a r13 later today.

Will be possible in an update coming today.

Sure.
[Nexus 5 Original Android Development] Bobtehblob:
Is there much use to over clocking on here though? It's pretty heavily thermally limited as it is?
[Nexus 5 Original Android Development] P.Mobile:
gesshhh!! thats some great battery life guys! flashing now :)
[Nexus 5 Original Android Development] yanner2012:
Fku is franco Kernel only? Thanks you

Inviato dal mio Nexus 5
[Nexus 5 Original Android Development] tr1cky1:
Just had a crash while trying to unlock the screen.

last_kmsg attached.

E: I'm on r12
[Nexus 5 Original Android Development] KTT16:
Franco Kernel Updater app
[Nexus 5 Original Android Development] franciscofranco:
Weird crash on this function: http://lxr.free-electrons.com/source/kernel/smp.c#L176

Thanks.
[Nexus 5 Original Android Development] 75markus:
F ranco

U updater

C ustom

K ernel

-

Y our

O ptimal

U tility

;):p
[Nexus 5 Original Android Development] bobloadmire:
I'm on WiFi all day, can't wait for r13
[Nexus 5 Original Android Development] Aerowinder:
The email sync is your largest problem.
[Nexus 5 Original Android Development] mrgold2505:
can someone tell me if the FKU beta is the same payed app that's we used for the nexus 4 ?
[Nexus 5 Original Android Development] nldxda:
Edit: I'm using stock ROM, xposed, dalvik runtime
[Nexus 5 Original Android Development] gee2012:
Creating last_ksmg log easily

For those who are not very familiar with making kmsg_logs can use SysLog from here https://play.google.com/store/apps/details?id=com.tortel.syslog&hl=nl.

Or in terminal emulator type su and hit enter and type: cat /proc/last_kmsg > /sdcard/last_kmsg.txt
[Nexus 5 Original Android Development] castaway1:
My SoD log.

sadly its r39 but it can help anyway. MAHDI latest ROM. Default settings (vibration amp 20)
[Nexus 5 Original Android Development] JNewms:
Thank you. I've looked it over some. I'll go through it all in a few hours after a little sleep. Franco may beat me to it since his day is getting close to starting. ?
[Nexus 5 Original Android Development] matesc:
SoD on r40 stock Rom. Log attached. Good luck :)
[Nexus 5 Original Android Development] Hatshipuh:
Looks like SoD is the new stutter.

Ironically those who have blamed the Rom for the stutter and having SoD now are touchy when they are told it might be the Rom ;)

Tap-a-talked from my Nexus 5
[Nexus 5 Original Android Development] Ben36:
It can't be rom related if all you did was flash a different kernel. Unless you also updated your rom at the same /similar time
[Nexus 5 Original Android Development] JNewms:
It can be a few things. I gotta read through these two logs thoroughly. I'm not as quick as Franco is at seeing the exactly what it is.

---------- Post added at 05:09 AM ---------- Previous post was at 05:04 AM ----------

Did you OC your cpu to the max? (3014)
[Nexus 5 Original Android Development] matesc:
Nope, pretty close to stock settings.

Only changes:

- input boost: 1190400

- temp: 70° C

- vibration: 63

- and headset gain and speaker...
[Nexus 5 Original Android Development] JNewms:
I saw those changes in the log. It also shows max cpu being raised. The two logs I've seen so far aren't showing me a common error. Double check your max freq. I'll need to look at these again after some sleep.
[Nexus 5 Original Android Development] Ben36:
What about if people who are getting the SOD issue try the linaro version of franco's Kernel here - http://xdaforums.com/devdb/project/dl/?id=5309

And see if they still get the issue. Because no one on that thread has mentioned it yet
[Nexus 5 Original Android Development] matesc:
That's weird. I haven't touched the max freq at all. Also I use only FKU for those settings. Thank you for your previous answer!
[Nexus 5 Original Android Development] abra5umente:
On r40 with Vomers settings. Runs like a dream.
[Nexus 5 Original Android Development] big_adventure:
Care to explain how your post here is better than the people you are *****ing at? Didn't think so.

Seriously, a number of people have reported this issue (I've not seen it at all), but not one has posted a log. Without a log, what, exactly, do they expect the developer, who is not having the same problem, to do about it? It's like asking Franco what you should say to the girl who works in the next cubicle over - without more context, it's going to be extraordinarily difficult to provide useful assistance.

Now, I can agree that some people have tones that are perhaps a bit harsh when asking for more information - most of us have been guilty of that from time to time. But then again, this thread is something like 9 million pages now, and on every single page someone presents a problem without a log and someone else says please give a log. If someone can't be bothered to spend 60 seconds getting and posting a log, I guess their problem isn't really all that serious.

Here is a little compilation of what we've seen here so far (it seems to me...)

Certain people have experienced "SoD" issues with r39, r38 kernels.

Many seem to be running stock rom. Some are using other ROMs.

Most claim that they are using Franco's default settings, plus perhaps PAM. Most claim not to be UV'ing.

Not a single person, that I have seen, who is using extensively modified kernel settings claims the problem - nobody who is running load_threshold 0, for example, or Vomer's / TGM's tweaks. I run something similar to their setups, and haven't seen any inkling of this issue - and I use my phone a LOT.

So, perhaps there is a derp in some core management stuff in the hotplug code, or in the governor? None of us underclocking to 1.5 or less and running all four cores on line are going to touch some of that code? Perhaps there is something odd in the voltage regulation?

Some people have cleared FKU data and not seen the issue, so that's a thing to try, obviously.

If that doesn't work here's what I'd advise if you are having this issue:

1. ALWAYS collect the log after the reboot. ALWAYS.

2. Try overvolting - go into FKU and add +25 or +50mv everywhere. Run for a day. Do you get the issue? If so, there might be a voltage problem to solve.

3. Try setting load_threshold to 0 to eliminate the hotplug driver.

I'm just spitballing here, trying to find common points in the total absence of hard data.
[Nexus 5 Original Android Development] gee2012:
+1 above, post a log or it didn`t happen (CM directive) ;)
[Nexus 5 Original Android Development] JNewms:
You may be on to something. I'm using settings very similar to Vomer's. (0 hotplug) in both logs there is cpu boost failures. I'm pretty tired and blurry eyed so I didn't go line by line through the logs, but both of them had that same failure. It would be interesting to see a couple more logs, to see if that really is the common issue.
[Nexus 5 Original Android Development] joeyfong:
Roll back to r38, SODs occurred at both r39 and r40, even at stock voltages.
[Nexus 5 Original Android Development] big_adventure:
Or you could help people giving freely of themselves trying to make a better tool for all of us to use. Just a thought. At least send a log before backing off to r38 (which has its own small issues).
[Nexus 5 Original Android Development] MBQ_:
This kernel sucks.

Whenever I use my phone, the battery drains.

Trollface.jpg
[Nexus 5 Original Android Development] 093236:
So, don't use your phone.[emoji5]

Sent from my Nexus 5
[Nexus 5 Original Android Development] MBQ_:
hahahaha

touche ;)
[Nexus 5 Original Android Development] :
The only persistent issue on r38 was people coming from r37 felt it was slower in animations, I checked the governor settings and realized r38 had more conservative values probably why I experienced that perceived lag. So I'd personally stick to r37 but I'm not on this kernel at the moment
[Nexus 5 Original Android Development] big_adventure:
I know - check my posts, I actually tested and confirmed it by turning off 4 cores (since it isn't present when amped up like that). I just didn't figure it was worth re-hashing that for everyone when we had 500 posts on the subject two days ago. :)
[Nexus 5 Original Android Development] jmudrick:
Linaro, no SOD issues.
[Nexus 5 Original Android Development] lolcopter:
Everyone is having it

Confirmed again under r40. Alarm went off when phone was on airplane mode this morning, but screen would not wake up again.

Stock ART, r39 and r40 both had SoD. NO other tweaks, no uv/uc, no xposed