yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] wund3rground:
Like, just turn the screen off?

Never mind, I see. Restart for me as well trying to power down. Also, can't reboot to recovery via power menu.
[Nexus 5 Original Android Development] MoJo:
test r41: using Power menu I choose "Reboot in Recovery", but phone reboots in Normal mode. No problem with r40.
[Nexus 5 Original Android Development] chikimonke:
Yup, confirmed here too, Power Off and Reboot to Recovery (TWRP for me) both result in a standard reboot.
[Nexus 5 Original Android Development] Tzfardaya:
well, looks like it doesn't matter if it was auto-flashed via fku or the zip flashed via recovery... both mean reboot instead of shutting down...

But, at least it looks like the SoD issue got fixed (huge thanks [MENTION=669468]francos[/MENTION]cofranco)

forcing to recovery (power + volume down) still works...

and the phone will power off in twrp since franco kernel isn't running at the time.
[Nexus 5 Original Android Development] LRC1710:
Just flashed vomerteaks, device feels a lil bit laggy tho, ill test battery life vs performance in the next days to see if its really worth it, however, how do I go back to stock Franco settings if I decide to go back ?
[Nexus 5 Original Android Development] laureanop:
Confirming the recovery, shut off issue on stock with xposed
[Nexus 5 Original Android Development] Sparx75:
Confirming as well. Can't power off or reboot to recovery. I can last a day on this, the snappiness is with it.
[Nexus 5 Original Android Development] Tzfardaya:
If you're using voters init.d setup, just delete (or move) his script file from the /etc/init.d folder and reboot...
[Nexus 5 Original Android Development] LRC1710:
No, I flashed the zip for it
[Nexus 5 Original Android Development] WettbackMartyr:
+1 here too, can't power down the device, auto reboots (r41 stock everything)
[Nexus 5 Original Android Development] Tzfardaya:
Yes, but I think he set that up to do all the work for you wrt the init.d. Check /system/etc/init.d for a script file...

---------- Post added at 10:12 PM ---------- Previous post was at 10:10 PM ----------

You can power down.. Just takes a few extra steps.... Force a reboot to bootloader (hold power and volume down buttons until the device boots into bootloader, then power off from there.
[Nexus 5 Original Android Development] LRC1710:
Oh yeah found it, so I just move it to another location and that's it right? Thanks!
[Nexus 5 Original Android Development] Tzfardaya:
Move it from that folder and reboot, yes..
[Nexus 5 Original Android Development] WettbackMartyr:
[MENTION=4860519]Tzfardaya[/MENTION] yes I understand I can power down by going through recovery. By conventional means, however, I was conforming that in Stock ROM, stock everything, modless, power menu "power off" command results in a reboot.
[Nexus 5 Original Android Development] Tzfardaya:
No worries, just wanted to make sure the info was out there, some of the users here seemed to be having mild panic attacks about not being able to get into recovery... :P
[Nexus 5 Original Android Development] nym27jrey:
Can also confirm. How odd.
[Nexus 5 Original Android Development] hellsgod:
About the reboot into recovery issue, [MENTION=3292224]franciscofranco[/MENTION] revert this one. It bugged me on the N4 and faux123 on N5. https://github.com/franciscofranco/hammerhead/commit/6856549d67cc24b7b68f83e5ab5b828967adc9f7

hells
[Nexus 5 Original Android Development] kumar_r100:
r41 seems good to me. standby for 2 hrs dropped 2% batt. no reboot .
[Nexus 5 Original Android Development] Laggalot:
i also can confirm that bechmarks mean nothing as i am using PAM aswell .... but that power on ART is something new to me

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] ibilln:
I also have the won't power off, etc issue on r41. Never a single issue before.

Fyi, to revert/restore, go to Franco Updater, click backup/restore. There you will see various kernels you've flashed. Pick one (I went back to r40), click it, it will restore that version.
[Nexus 5 Original Android Development] blueren:
All of a sudden people are losing their minds because they can't turn off their phones? :D when was the last time anyone turned off their phones! :D
[Nexus 5 Original Android Development] msgfromside3:
I was just wondering about that while catching up with the thread. I first thought it was screen off restarted phone, which is a big deal, but after a few I realized it was shut off. Really? Should we worry about it? ^_________^
[Nexus 5 Original Android Development] Laggalot:
i got a differrent bug ^^ i cant even flash 41 through fku because it sayis i have it already even though im on the testbuild :D ( a thought of mine for you guys ... a SOD where you cant turn off your phone would be a horror

ps : i can shut down my phone!!!

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] srpanadero:
Revert to earlier kernel then flash the latest 41. An s.o.d. is that case you would just hold down vol- and power.
[Nexus 5 Original Android Development] PainfulLover:
I'll take benchmarks over placebo any time of the day.
[Nexus 5 Original Android Development] baedaa:
guys, I'm on this Kernel with the SoD bug since it was released, that makes it 4 days now and I had exactly 1 SoD. So please don't tell the world when it didn't happen to you in the last 15 minutes... this looks to be pretty random and could also happen to the people who claim to be not affected.

Since I'm on r41test there was no SoD but I also had none with r39 ;) lets wait and see
[Nexus 5 Original Android Development] topgeardave:
Sounds like it IS SMP issues if people aren't getting SOD from setting hotplug to 0. Looks like Franco will have to look at chaos kernels github as he's finally found a way to get round the plaguing screen of death
[Nexus 5 Original Android Development] lesp4ul:
Running r41 for 10 hours, no SOD yet. Vanir 7 April, 1.5GHz max, hotplug load_treshold 60, -50mV, 675mV on 300MHz.
[Nexus 5 Original Android Development] EnricoTFYKD:
FYI, I was able to get to recovery by pressing vol+, vol- and power while it hanged during the shutdown process. This way you get to the bootloader screen, from which you can go to recovery and shut down your phone. Just a workaround if you really need to shut off your phone.
[Nexus 5 Original Android Development] a2k:
Power down and boot into recovery issues as well from power down menu. Had to revert back to 40.
[Nexus 5 Original Android Development] KiD3991:
[MENTION=3292224]franciscofranco[/MENTION] or anyone who might have the file.

Can you guys upload the latest franco available for the Nexus S? i9023.

Many thanks.
[Nexus 5 Original Android Development] joeyfong:
no SOD so far since flashed both test and official r41.
[Nexus 5 Original Android Development] shinesthru:
Use FKU.
[Nexus 5 Original Android Development] aavvaallooss:
Or Flashify or web...
[Nexus 5 Original Android Development] rockafellor:
I can confirm that when trying to "switch off" the phone, it reboots

Sent from my francofied cataclysmd Nexus 5
[Nexus 5 Original Android Development] :
[MENTION=410271]fransisco[/MENTION]franco should add this reboot thing as a kernel feature.

"So battery friendly you literally can't switch off your phone!"
[Nexus 5 Original Android Development] Hatshipuh:
Had threshold set to 20 over night and still no SoD on r40, going to r41 now anyway.

Tap-a-talked from my Nexus 5
[Nexus 5 Original Android Development] Eliranu:
Just bought the app

Thanks for all the efforts to make this beast device even better!
[Nexus 5 Original Android Development] kashix:
Great work as usual sir! Coming from galaxy nexus with your kernel. When you decided to work on the nexus 5, I got the device right away! Thanks for the hard work! Test driving r12 now!
[Nexus 5 Original Android Development] Zainiak:
This had been asked many times. It is not a priority, it may be done later
[Nexus 5 Original Android Development] cadbomb:
Could it be the double underscore in line 178?

Powershell and light c# guy here so not sure about android coding, but seems odd to me.

Sent from my Cataclysm-powered Franco-charged Nexus 5
[Nexus 5 Original Android Development] bleuxeon:
Just for testing purpose, I did switch from interactive governor to performance : bang! Antutu crashed.

I maybe have run 30 or more complete Antutu tests under interactive gov and have had zero problem.

For the first time I choose performance gov : crash.

I realy dont care since I have absolutly no plan to use performance gov, but just to let you know.
[Nexus 5 Original Android Development] PhantomGamers:
[MENTION=4459653]bleuxeon[/MENTION] Did it reboot your phone or force close?
[Nexus 5 Original Android Development] bleuxeon:
Hard reboot.

Can't be 100% sure because I was typing on my PC's keyboard at the same time.

Edit : mhhh, "hard reboot" is not the right words. It rebooted it self, shows me Google logo, then went to the small color balls dance then reach lock screen.
[Nexus 5 Original Android Development] ks2332:
Hey [MENTION=3292224]franciscofranco[/MENTION] if you don't mind what was your solution you added for the idle WiFi drain?
[Nexus 5 Original Android Development] PhantomGamers:
[MENTION=2703429]ks2332[/MENTION] https://android-review.googlesource.com/#/c/70213/
[Nexus 5 Original Android Development] dandwhelan:
I had the same issue
[Nexus 5 Original Android Development] PhantomGamers:
It's a known problem I was just making sure he didn't mean it fc'd. Because that would have been new.
[Nexus 5 Original Android Development] bobloadmire:
FKU updated!
[Nexus 5 Original Android Development] luisvilla1993:
I think speaker gain was added under kernel settings!!

---------- Post added at 05:26 PM ---------- Previous post was at 05:22 PM ----------

Speaker gain works great but unfortunately the boost in sound still goes away after you change the song!
[Nexus 5 Original Android Development] the1dynasty:
no0b here... just thought i'd take up a pointless post to subscribe to this thread :D

will this work on my Nexus S 4G with Sprint?

j/k lol... i've heard nothing but great things and i'm gonna give this one a shot and see now that i've done my testing with stock for about a week!!
[Nexus 5 Original Android Development] CyborgW:
Yeah, just verified... But i think LG has decided the actual speaker gain as a consequence of the crappy quality of it... The distortion makes it really unlistenable :S

By the way, thanks Franco for the excellen work here! :good:
[Nexus 5 Original Android Development] pogi1100:
Franco, will you add exFAT support with this kernel in the future?
[Nexus 5 Original Android Development] egofreak:
And yet still version 10.3.3? Am I missing something? It does say it was updated today in the play store, but I dont see evidence of that happening.
[Nexus 5 Original Android Development] nexusmaniac:
It's an update for the beta users :)
[Nexus 5 Original Android Development] egofreak:
And here I was thinking that Franco here went all super man and pushed a new non beta app in record time.:crying:
[Nexus 5 Original Android Development] matesc:
Just had a SoD on official r41. Very strange log.....
[Nexus 5 Original Android Development] aavvaallooss:
Back to r40. No SOD in 3 days despite undervolt, underclock, undereverything and a lot of tweaks. One SOD un r39 with same modifications
[Nexus 5 Original Android Development] Therion87:
I can confirm the reboot issue on r41. Will try to post some logs later.
[Nexus 5 Original Android Development] lesp4ul:
First random reboot. Manual shutdown was fine. Not a SOD.

http://pastebin.com/qDscACid
[Nexus 5 Original Android Development] FAdrums:
:)

Enviado do meu Nexus 5 através de Tapatalk
[Nexus 5 Original Android Development] Kenshiro79:
Many users on G+ wonder: why setting the various settings on the Franco Kernel restart the device returns to default?
[Nexus 5 Original Android Development] big_adventure:
You need to configure the settings to set on boot, and you also need to wait at least 2 minutes after boot before you check in FKU - give the app time to set.
[Nexus 5 Original Android Development] Kenshiro79:
Ok but have been waiting for half a day before restarting. The result is always the same.
[Nexus 5 Original Android Development] nerotix:
And did u check the setting to stick after reboot?
[Nexus 5 Original Android Development] big_adventure:
You don't seem to understand what I'm saying:

First, the settings won't stay in FKU if you don't configure EACH SETTING to "Set on Boot". This is that little box on the right in each setting line. If you don't check that box, it won't set on boot.

Second, even when you DO put "set on boot", AFTER you reboot, you have to WAIT a minute or two before FKU puts the settings in. If you go into FKU before FKU puts the settings in, you will see the default settings.

Clear?
[Nexus 5 Original Android Development] finesse:
Newbie question - how do I restart the phone when SOD occurs?
[Nexus 5 Original Android Development] snives:
Hold Vol Up + Power for a while (10s?) and it will do a simulated battery pull. Then you can turn it back on like usual.
[Nexus 5 Original Android Development] Shane_IL:
Hold in the power button for about 10s, phone should reboot
[Nexus 5 Original Android Development] big_adventure:
You have something extremely odd in your log - and you did last time as well. You have a f$€*ton of uncorrected errors. Nobody else's log has the same crap in it that yours does. It's all this:

[ 219.761666] PM: resume of devicEs complete after 76.84 msecs

[ 219.763849] Restarting tasks ... done.

[ 219.587711U PM: suspend exit 2014-04-09 08238:13.178195194 UTC

[ 219.848435] [Touch] touch on

[ 219.854117] mako_hotplug: resume

[ 219.954407] dhd_set_quspend: Remove extra suspend settIng

[ 219.991828] max17048_work sc0@7F vPel002 o=0v@m=81@iu=177Pt39[ Q2@.@453 dsd@ipnlo@

20083]lD33P_akih_n@[ 4D.118 Pm60PbPclgto@fA[ 4.91@1 h_eD_Pu@pn:freeta@S@sÀedst@ig

P 209A56D]ms_s_aDe_f:[ 4.562P Tuh o@c f

2$1!1P96] P:s@sTedety21-40 83 :459347U@C[ €4.@819 M@ y@cn iAeytm .D @oe

 347@26]ddstPsAseAd @eoeeta@ssedstigM

 371@7A2P]ddsts@s@ed oc xr upn etn [A 5.954 h_Ae_u@pn:RmBv@ [MENTION=317916]XR[/MENTION] upn eBtnA [ 5.553 h_e_upn:Pf@reeTtaS@seDdstig

 36781]d0d@stssPed @e`o@e@eta@ssedstig

36966@]m@x74_okP sc0@7D vAel00F o=0v@m=88iu@=78@2tA33[ 5.312@ h@_e_$upn@:fr@eetaSsedst@ig

 39440]ddstssed eoeetassedst i@g

 37348]ddsts@sed oc xr up@n etn [ 7.170 h_e_upnd8 Reeove extra suspend setting

1512 Corrected bytes, 669 unrecoverable blocks

...right at the end. I've looked at a dozen last_kmsg files and haven't seen anyone else's with this - except the last one you posted:

27546]@P:ssedety21-40 81:429910UC[ 2.942 M ycn ieytm . oe

27656]Fezn srs aepoess. .(lpe .0 e od)dn.[ 2. 191 reigrmaigfezbetss..( lpe .0 e od )dn.[ 2.194 up nigcnoes u en_osl_upn odbg

27772]P:ssedo eie opeeatr8.6 Dsc

 2U7U7Q94 ]uP:Tlt5 upn fdv cscmlt fe .9 sc

27725]P :niqssedo eie opeeatr316mes[ 2.11@6 iaElUnT To-ot@CQU A.P

27737]mmp_ne

27737]mmp_ne:pwrclas 27737]mmp_ne:rtr

2 7 762]P:niqrsm fdvcscmlt fe .9@ s c

277 82] PM: early resume of devices complete after 1.417 msecs

[ 227.801125] PM: resume of devices complete after 82.176 msecs

[ 227.803899] Restarting tasks ... done.

[ 227.826494] PM: suspend exit 2014-04-07 08:19:55.986979432 UTC

[ 227.895866] [Touch] touch on

[ 227.896743] mako_hotplug: resume

[ 228.027299] max17048_work: rsoc=0x89D9 rvcell=0x0C65 soc=70 v_mv=3966 i_ua=139959 t=345

[ 228.104582] mdss_dsi_panel_on

[ 228.187859] lm3630_backlight_on

[ 312.601717] max17048_work: rsoc=0x88EA rvcell=0x0C41 soc=70 v_mv=3921 i_ua=458644 t=346

[ 326.985429] lm3630_backlight_off

[ 327.211414] mdss_dsi_panel_off:

[ 327.234628] [Touch] touch off

[ 328.004416] PM: suspend entry 2014-04-07 08:21:36.164869966 UTC

[ 328.004674] PM: Syncing filesystems ... done.

891 Corrected bytes, 162 unrecoverable blocks
[Nexus 5 Original Android Development] Kenshiro79:
Without any procedure that we know both me and other users. After setting the parameters of the kernel we flagged the icon that is in part. While waiting cpoem you say two minutes eventually find is that the returns to default!
[Nexus 5 Original Android Development] matesc:
Yes, I saw that. Strange, isn't it?

I thing it's time for a clean installation ;)
[Nexus 5 Original Android Development] finesse:
Thanks
[Nexus 5 Original Android Development] mattcooper:
What's been done to improve the quality, would be cool to know?!
[Nexus 5 Original Android Development] big_adventure:
Take some screenshots. I don't have that issue and never have.
[Nexus 5 Original Android Development] slider112:
Every night. :D
[Nexus 5 Original Android Development] Laggalot:
dammit ... i just got a SOD .... my phone vibrated as i got a message and the led blinked but i couldnt wake it up!¡

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] franciscofranco:
Some of you need to take a chill pill more often. Here's r42 with that bug fixed that prevented to reboot to recovery/bootloader.
[Nexus 5 Original Android Development] The Gingerbread Man:
Since flashing r41 and playing back music iv had several of the pauses while screened off. With the pauses music won't play again until headphone is unplugged and plugged back in again. The counter in Google play music will increase as the track is supposed to play. When you remove and reinsert headphones the track goes back to where it should of been roughly where the pause began. There's 4 culprits at play in log cat which I dought can be fixed without being sometime to do with user space stuff. Even so music would recover from the pauses before r41 when the io errors finished ****ting everywhere. Music on r35 (caf audio) was fine apart from the right earphone clipping at very high volumes. Here's a screen shot showing the culprits
[Nexus 5 Original Android Development] franciscofranco:
There's a patch from CAF that does that and I applied it.
[Nexus 5 Original Android Development] nerotix:
Gotta ask bro.. Did u try to fix the SOD's in r41/42? Havent seen anything saying about it in the changelog, only seens 'fixes' which has a broad meaning :)
[Nexus 5 Original Android Development] Tylog:
The last 100 pages ( tapatalk ) " I have sod , I have no sod , I have sod [emoji22] "

" I have SOD , Fix it , NOW , you DEV you MUST " The logs in this postings I can count on five fingers. Extremely helpful for the DEV to solve the issues.

Sometimes I really can only shake the Head and surprise me.

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] Tzfardaya:
When pressed, the people who were saying" no SoD here" were using vomer or tgb settings... Which seemed to be what was preventing them...

No one has posted a SOD event listing 41 or 42..

And the last sod report didn't state which version...

Since 41 I've gone back to settings which seemed susceptible to SOD's and haven't had one yet...
[Nexus 5 Original Android Development] yoyoz808:
I agree. I don't comment much but i remembered it was mentioned that this kernel is made to flash and forget. I just use your new versions and enjoy it even though there are small bugs here and there. I don't look for what's wrong. I look for how great it performs. I Know the bugs get fixed eventually and it's not like the bugs prevent you from using your phone completely. ENJOY THE KERNEL!

Thanks Franco!
[Nexus 5 Original Android Development] PetritH:
Using stock settings for 2 days, no sot, i just flashed r42..
[Nexus 5 Original Android Development] andresee:
As always thx for your work!
[Nexus 5 Original Android Development] SketchyStunts:
Thanks Franco. I heart your work & have had nothing but great performance/battery.
[Nexus 5 Original Android Development] Tzfardaya:
I'd like to, but I'm getting ready for work... Chill pills interfere with my ability to do my job... Might take one Friday after work though.... :P
[Nexus 5 Original Android Development] fredfox_uk:
Not using anyone's tweaks and hotplug set at default (60) and no SoD with over 2 days since last reboot.
[Nexus 5 Original Android Development] Tzfardaya:
Sorry, overgeneralization... I had mentioned to say "most" of the people....
[Nexus 5 Original Android Development] jmudrick:
You're wrong on two counts. Folks have reported SOD on r41, and people with stock settings on r40 (me and presumably our developer among them) have reported no SOD problem. And remember, people without problems tend not to post.
[Nexus 5 Original Android Development] big_adventure:
I like that bug, I'm going to stick with r41. How DARE you take out the carefully-crafted "block kids from getting to bootloader / recovery patch!" How DARE you try to quickly improve a product you release and optimize for free. The NERVE.

I have an idea, can you run two separate trees, one with that "feature" and one without it? What was that? "Go fù$k myself?" OK then - I'm not paying you for this kernel!!!!! What? I don't pay for it now? Again, how DARE you.

/end glib
[Nexus 5 Original Android Development] Tzfardaya:
sorry, You're right... since 41 was released (r41, not test41) there's been a while 2 sod reports... one listing r41, (but with a really fscked up log, which makes me think it was something other than the kernel glitching, but I could be wrong there) and one with no kernel version reported...

as to the comment about the stock settings on 40.. I already retracted and said it was an over generalization... geez, give me a break here, I just woke up.... maybe you're one of those that franciscofranco said needs to take a chill pill... and as to franco reporting the bugs he experiences... he seems to report them about as often as he reports what settings he uses (happens, but not very often..) usually he just works on a fix rather than coming here to log a bug report... :p he will acknowledge a bug, and sometimes ask for more information if he can't reproduce it.. but usually doesn't come here and ask "anyone else experiencing this bug, anyone know of a fix/workaround?"
[Nexus 5 Original Android Development] mibtnt:
Omg this battery life though. I'm resisting updating to r42 lol. R41 battery life so far on PA4.2b4 is sick!!! Thanks ff

---sent from a N5 on PA4 + Franco's kernel
[Nexus 5 Original Android Development] big_adventure:
For a more detailed report:

People getting SoD's included mostly people running just about bone-stock tuneables. No UV, no clock changes, etc. for most users. Various ROMs were used, many with stock, some with others.

This does NOT mean that everyone running stock settings gets SoD's.

It also does NOT mean that not running stock settings prevents SoD's.

There really isn't anything conspicuously useful in the kernel log - I went line-by-line with some other folks' logs, and their behavior going into and coming out of sleep seems pretty identical to mine.

However, one thing seems abundantly clear (up until now): nobody running hotplug load_threshold: 0 ever saw an SoD. That is the only common factor that I can ID. People who had been experiencing SoDs and who changed to load_threshold 0 didn't see any more of them.

This does not mean that this "cured" the issue, since it's not re-creatable on demand, and a number of people have only seen one or a few SoDs. It is just possible that it didn't crop up.

However, not one person who solely runs load_threshold 0 has reported a single SoD.

So, it seems most likely that the SoD situation has something to do with kernel hotplugging. Disabling hotplugging seems to disable the SoD "feature." Is it sure? Of course not. It could be something else.* But it's where the evidence I've seen points.

*I posited earlier that it could be keeping the phone out of a cpu bin that is flawed, since most of us who run load_threshold 0 also underclock, and maybe there is a voltage issue in a certain bin, but the phone doesn't usually run up to high bins with the screen off anyway, so this seems maybe a little less likely

Clear so far?
[Nexus 5 Original Android Development] Tzfardaya:
just one comment... cpu bin usually refers to the QA rating of the chip... non-mutable.. I think you meant frequency/voltage steps there.. :p