yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] TheHighlightGuy:
Y'all need to pull some logs, either kmsg or logcat, Franco can't really fix it and has already tried to reproduce the issues. Just Google "adb logcat" or "adb kmsg"
[Nexus 5 Original Android Development] Nbsss:
Don't think the logs were useful, I posted three separate ones in an earlier post
[Nexus 5 Original Android Development] franciscofranco:
I don't know what the problem is, I don't even know that there is a problem on my end at this point, I cannot reproduce it.
[Nexus 5 Original Android Development] i860:
I tray to reproduce but it didn't happen on my end.
[Nexus 5 Original Android Development] drawde40599:
Check your pm .
[Nexus 5 Original Android Development] drawde40599:
I had this happen , but it was after I had set up some pre app modes . I cleared app and never happen agn , and I haven't had a chance to try to reproduce it .
[Nexus 5 Original Android Development] Tzfardaya:
Even if franco and others couldn't find any problems with the logs you provided, there are too many people just going "me too" without providing logs of their own. By looking at multiple log from multiple devices the problem has a better chance of being found.

Yes, not all issues will show up in logs, but without any logs this problem will likely never be found, especially since many others can't seem to reproduce it on their own devices...

So I'll ask again, what screen lock type are you people using when you experience these reboots? slide, face, pattern, pin, password?

does changing the type make the problem go away?

and how are you rebooting the phone, power off, then back on, 3rd party app to add a reboot feature, custom rom reboot feature?
[Nexus 5 Original Android Development] stereoprologic:
Just flashed r21 and root was gone. I did not change anything else, is anyone else having that problem?
[Nexus 5 Original Android Development] sNoxious:
Same thing happened to me. Can you post your last_kmsg? Could be the same "wdog_reset".

Sent from my Nexus 5
[Nexus 5 Original Android Development] i860:
Nope.

Flash supersu in recovery and you are ready to go.
[Nexus 5 Original Android Development] dsr13:
just to report fyi: using multi ROM, r21 boots but will not allow the multirom interface to load... It just boots into the primary rom. Reporting here and on the multirom thread.
[Nexus 5 Original Android Development] zephiK:
It has nothing to do with the kernel, your phone probably auto-updated SuperSU which received a update to 1.85 today. Open SuperSU and then update the binary (it'll pop up)
[Nexus 5 Original Android Development] Nbsss:
It doesn't really bother me as I hardly ever reboot, and I just keep the phone awake for the first minute if I do, so I haven't checked for this bug in r20 or r21, I'll do so later today.

If I remember correct some were saying clearing FKU data solved it, maybe you guys could try that.

FYI lockscreen is default, reboot through gravity box module.
[Nexus 5 Original Android Development] iraqi92:
Ok .now no problem ..im come from ElementalX kernel and have this problem ..im try install b20 ..and than install b21 and run whitout any problem ..

franco plz add to this kernel "color preset" like ElementalX kenel its really nice ..
[Nexus 5 Original Android Development] pitjago74:
flashing r21, I open SU ​​and asks me to update binaries, if I give .... and perfect ... thank Franco

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] omvir:
Franco, I never have problems with your kernel but today after autoflashing r21, 3 cores are on while idling. Cores 0, 1 and 3. I think a reboot should fix it. But I just wanted to report in case there's something on the kernel side that may have gone wrong!! I'll edit this if a reboot fixes it.

Edit: reboot fixed it.
[Nexus 5 Original Android Development] FaithCry:
also had this but 4 cores online, but a reboot also fixed it.
[Nexus 5 Original Android Development] Zeduaz:
R21 on stock... No problems there...

Odesláno z mého Nexus 5 pomocí Tapatalk
[Nexus 5 Original Android Development] Pretoriano80:
I don't know if this will help but a last_kmsg log is the least i can do to help.

http://pastebin.com/fJeQfsNF

Inviato dal mio Nexus 5
[Nexus 5 Original Android Development] pkelly517:
Uhm, you can't get a log from a boot loop.

And, for this particular issue, plugging in a cable negates the problem.
[Nexus 5 Original Android Development] Pretoriano80:
It's not a "real" bootloop because you just have to unlock the phone in order to stop it from rebooting again and get a last_kmsg log.

Inviato dal mio Nexus 5
[Nexus 5 Original Android Development] omvir:
Ummmmm okay now 3 cores are online again. Cores 0, 1, and 2 this time... Hmm. Doesn't seem to be effecting battery that much tho. Hopefully you can figure out what's wrong. Probably some of the changes done on the hotplug system?

Until then I'm gonna enable all 4 cores and experiment with governor settings just to experiment :D so far I've got input boost at 1036 MHz, sync freq at 729mhz, hi speed at 1574 MHz and min/max at 300/1728 MHz. Smoothhhh!
[Nexus 5 Original Android Development] drawde40599:
Only 2 cores running here till 3-4 r necessary.. U try clearing whatever app your using to control the kernel ?
[Nexus 5 Original Android Development] omvir:
I use FKU and yes I have. Running stock ROM as well with no mods. Clean as it could be.
[Nexus 5 Original Android Development] manny05:
Just wanted to report I flashed r21 and no problems here at all. Smooth as it can be. Great work!
[Nexus 5 Original Android Development] aamitabh28:
I have the same issue..started with r21 ..reboot fixes it

Sent from my Nexus 5
[Nexus 5 Original Android Development] capcanuck:
I also am having this same issue...
[Nexus 5 Original Android Development] omvir:
So we have 3 people, including me making it 4, who has this problem.
[Nexus 5 Original Android Development] kurnis:
cancel, i fixed it.

great work franco! :D
[Nexus 5 Original Android Development] pkelly517:
Maybe for you. A phone that constantly reboots without user intervention is in a bootloop But we're talking semantics. To me, it's real.

This is something with Franco kernel and his app. If I under clock and set on boot, it's 100% reproducible. It does NOT happen if I don't set on boot. It happens on stock It happens with SlimKat. The watchdog kicks in after about 2 1/2 minutes. Every time. I've posted logs, and they look like every other log. posted on the issue. I'd be happy to post another if it would help.
[Nexus 5 Original Android Development] Edo 91:
Have you downloaded the update from google play? if yes, launch supersu and update the binaries ;)
[Nexus 5 Original Android Development] Rxpert:
I'm getting a lock on all 4 CPUs while listening to audio r21

Reboot only temporarily fixes it. They all lock again after x time
[Nexus 5 Original Android Development] ben_pyett:
No issues here so far, after a couple of hours varied use.
[Nexus 5 Original Android Development] sNoxious:
Like I said yesterday, the thing that fixes the bootloop for me is clearing FKU data. Dunno if that's the case for everyone else.

Sent from my Nexus 5
[Nexus 5 Original Android Development] sidhaarthm:
Anyone else who is unable to change the Max CPU values in FKU? It is current stuck at 2265MHz but unable to go higher or lower...? The option menu opens, but when you select a different frequency, the UI on the page remains at 2265Mhz.

I am definitely running R21 on Stock 4.4.2.

Edit: Reboot and the issue is resolved.
[Nexus 5 Original Android Development] Enddo:
i had the 3 active cores too. it wouldn't lock down core number 4. it was running 1, 2, and 3 at 300mhz even after i turned the screen off. a reboot fixed it but some people say it's only temporary. I haven't seen it again, but im still testing. i just wanted to make the comment to show there was another person seeing it.

franco kernel r21 with stock android 4.4.2(very minimal apps are installed and running, i basically only use whatsapp on the device)
[Nexus 5 Original Android Development] peikojose:
4 cores online running at 300Mhz.. No apps open... R21... Slimkat 4.4.2 didn't happen with r20...
[Nexus 5 Original Android Development] nexusmaniac:
I also had 3 cores online after I flashed r21, reboot fixed it and I haven't seen it again :)
[Nexus 5 Original Android Development] Nocturnal86:
Im having a similar issuea as others. Im getting 4 cores online at all times and they idle at 300mhz with slight jumps in random cores when nothing is going on
[Nexus 5 Original Android Development] TrenchKato:
Reboot
[Nexus 5 Original Android Development] Nocturnal86:
reboot seems to have fixed it. Ill see if it comes back.
[Nexus 5 Original Android Development] omvir:
Reboots don't help. I've rebooted 3 times now. Happens again after some time. Always random. So for the time being I lowered core threshold to 0 so now I'm running all cores and I tweaked governor settings keeping in mind I have 4 cores running. So far so good. This will do until Franco knows what's up with the kernel. Pm if you want the settings. Not much to it.
[Nexus 5 Original Android Development] franciscofranco:
Hmm cores shouldn't stay up like that if there's no load. Might be an error on my calculations after the changes I added and I didn't observe the issue so I thought everything was ok. Back to the drawing board.

Thanks for the log.
[Nexus 5 Original Android Development] Tzfardaya:
okay, I finally managed to replicate, set slide to unlock and underclocked on boot... [MENTION=3292224]franciscofranco[/MENTION] I know you've said you haven't been able to replicate it before, have you tried this too?

also, I tried digging through Pret's kmsg (though it is a little beyond me...) and it shows wdog_reset at the end as well... but about line 903 there seems to be a trace started ...

"WARNING: at arch/arm/mach-msm/pm-8x60.c:1066 msm_pm_enter+0x22c/0x41c()"

might that have anything to do with it? I'm going to pull logs from my phone with a clean boot and replicating the reboot cycle from underclocking+lock screen and see if mine throws the same warnings....

Mine doesn't throw the same errors, and my last_kmsg is much shorter, I'm assuming that's because of differing roms... (http://pastebin.com/P3iYqdif) but it does still reboot if left (while locked and underclocked)
[Nexus 5 Original Android Development] PresidentMcCain:
Could be relevant, but it seems r21 created a folder called "ro, remount" in / (root path). Probably just a tiny mistake in a script somewhere.
[Nexus 5 Original Android Development] omvir:
R21 test was perfectly fine. So probably something between r21 test and official r21.
[Nexus 5 Original Android Development] Enddo:
reboot only helps for like 30 minutes. i had the 3 cores online before reboot and now im at 4 cores online with no other apps running except FKU
[Nexus 5 Original Android Development] drawde40599:
Mine was fine for hours (2 core ) I looked agn and 3 cores is on at all times now . I'm on 100% default settings besides fysnc and logs tuned off . looks like its random
[Nexus 5 Original Android Development] TheHighlightGuy:
Also having the same issue, 4 cored online at 300mhz and no apps other than FKU open. Would a logcat suffice to help you figure out what's keeping them online?
[Nexus 5 Original Android Development] franciscofranco:
Yeah I've seen the trace, but thing is I haven't touched that driver, its all stock

Wtf... the Kernel doesn't create folders to the userspace like that, but now that I checked I have that too. Funny thing is that I haven't changed anything that could do that, not even in the ramdisk. Its like sorcery.

Yeah I made a couple of changes last night, I think I found the error on my code.
[Nexus 5 Original Android Development] javacody:
Having the same issue. All cores on all the time. Reflashed 21 test to see if it happens there as well.
[Nexus 5 Original Android Development] franciscofranco:
[ 64.343345] write_local_on_cmds

[ 64.345135] write_local_on_cmds

[ 64.346419] write_local_on_cmds

[ 64.347721] write_local_on_cmds

[ 64.349037] write_local_on_cmds

[ 64.350345] write_local_on_cmds

[ 64.359618] write_local_on_cmds

[ 64.360727] write_kgamma_send: Panel off, failed to send commands

Can you disable the gamma app and try again? Because it seems the actual power management of the Kernel fails to kick in when this scenario happens and then the watchdog goes boom.
[Nexus 5 Original Android Development] Pretoriano80:
Franco it looks like clearing FKU data with the option provided within the app fixed the stupid "reboot loop" issue.Tested with the default settings and with my own UV settings and i'm no longer able to reproduce the issue.

Btw, i also tested the issue with the 4 cores always online but i can't reproduce, i always have only 2 cores ON when there's no heavy load.

Inviato dal mio Nexus 5
[Nexus 5 Original Android Development] franciscofranco:
Wtf... I'll try to underclock on FKU, set on boot, reboot and see if I make it crash. I'm really puzzled :eek:
[Nexus 5 Original Android Development] shaker2k:
This is a test Franco. The Google overlords did this to test your skills!
[Nexus 5 Original Android Development] Pretoriano80:
Just did another test now before going to bed and i confirm that clearing FKU data fixed the issue (let it sit for 5 five minutes after reboot and with the same FKU's settings i used before) so for those having the same issue i recommend a Clear Data from FKU.

BTW i never underclocked here, just UV and Thermal Throttling set to 80.

Night [MENTION=535343]all[/MENTION]!

Inviato dal mio Nexus 5
[Nexus 5 Original Android Development] radical86:
I can confirm that clearing FKU data from within the app allows you to set settings on boot in CPU manager without putting the device in bootloop.

Thank you for sharing this!
[Nexus 5 Original Android Development] DoesntPostAThing:
I was having issues with what seemed like backlight bleeding on whites at low brightness on r21 test, where one corner would be brighter than the rest when the screen dimmed. Nothing of the sort in r20.

Sent from my Nexus 5
[Nexus 5 Original Android Development] franciscofranco:
By the way thanks to everyone who reported problems on r21, some of them I didn't even know they existed because they were not triggered before or simply I didn't reproduce it during testing. Thank you all.
[Nexus 5 Original Android Development] heisven:
Got 4 Cores online [MENTION=1785406]300m[/MENTION]hz while idling. I'll change back to test21, did work quite good for me.
[Nexus 5 Original Android Development] franciscofranco:
?

Only thing that happened was lower minimum brightness, if its showing bleeding in very low brightness on r21 its because your display has imperfections.
[Nexus 5 Original Android Development] Tzfardaya:
As much as we all would love perfection with every release, Francisco, we know that errors, glitches, and goofs will occasionally sneak in when you're not looking... after all, you can't watch every line of code every second, now can you? And those code-bugs can be sneaky....
[Nexus 5 Original Android Development] franciscofranco:
Thank you sherlock.

Every now and then something slips, but I need to be more careful. Sometimes you code, all seems good because we're following our own logic, and its hard to spot for errors without looking through different logics. Good thing that I'm here and can fix bugs almost as soon as they come up.
[Nexus 5 Original Android Development] TheHighlightGuy:
Class act :good: Thanks for the great work Franco. Clearing FKU data seems to have fixed the 4 cores online problem I was having

Try clearing the app's data
[Nexus 5 Original Android Development] DoesntPostAThing:
I see then, could you please make the low brightness optional?

Sent from my Nexus 5
[Nexus 5 Original Android Development] MaxNXS:
Same here.
[Nexus 5 Original Android Development] drawde40599:
Read the last 10 pages .
[Nexus 5 Original Android Development] franciscofranco:
Clearing FKU does nothing for that cores during idle, its just a erratic init of a two variables in the hotplug driver.

But why? Just increase the minimum brightness up to the point where it is on stock...
[Nexus 5 Original Android Development] heisven:
I decided to switch from Trickster to FKU this afternoon. Great app by the way. Looks like someone put emphasis not only on functionality. Ill keep an eye on CPU monitor, hope clearing so app data does the trick.

Sherlock over.
[Nexus 5 Original Android Development] franciscofranco:
On my local build of r22 I did this:

1 - open FKU, underclock to 1,7GHz, tick set on boot and reboot

2 - after reboot left the device alone and it eventually screened off without touching anything before that happened

3 - let it sit for 5 minutes, clicked the power button, unlocked, and no device reboot

Either I fixed it on the Kernel side or its something else.
[Nexus 5 Original Android Development] Tzfardaya:
care for a second check?
[Nexus 5 Original Android Development] DoesntPostAThing:
Right... Forgot that often the best fix is the simplest... Just don't look at whites at low brightness :good:

Sent from my Nexus 5
[Nexus 5 Original Android Development] franciscofranco:
Sure, here I go.

And you hit the jackpot, I reproduced it.
[Nexus 5 Original Android Development] chazall1:
Great Build Franco, keep it up!
[Nexus 5 Original Android Development] keclarke:
Surprised to see issues with R21. I'm flying along. The best just got better. Thanks Franco!
[Nexus 5 Original Android Development] Tzfardaya:
ha ha, I meant if you wanted a second device to check it.. :silly:

or don't I rate as an alpha tester for you yet. :rolleyes:

nvm... you made it loop too...

I'm really curious what's causing these reboots... not that I experience them under my daily config... (no lock screen used here, and I use per-apps to UC the apps that hold the freq too high for my tastes)
[Nexus 5 Original Android Development] niv3d:
Lol well looks like we'll see r22 soon. I'm just loving Franco's work and look forward to future updates.
[Nexus 5 Original Android Development] franciscofranco:
Honestly I think its FKU, I've tried other apps that set freqs on boot and my device doesn't crash. If I use FKU to set max freq on boot... if the display is not on during the set on boot process, boom, I can reproduce it 100%. Fúck :)
[Nexus 5 Original Android Development] UnknownzD:
The same thing happened on my device as well. Although I am not using the official build of your kernel, but rather the Linaro toolchain build, but once I set the 3.0 GHz at boot, it will crash very quickly after switched on / screened off.
[Nexus 5 Original Android Development] Savant:
You're phone is probably throttling and can't handle the frequency so try a different one.
[Nexus 5 Original Android Development] franciscofranco:
[MENTION=4154904]PresidentMcCain[/MENTION]

ro.remount folder on root / is created by the new SuperSu update, I just tested in a 100% stock device after updating the device with the newest SuperSu.
[Nexus 5 Original Android Development] alextso321:
I am on r20 now but it seems that there are some bugs in r21, should I wait for r22 and skip r21 at this moment?
[Nexus 5 Original Android Development] franciscofranco:
Well, one does not need to be Sherlock Holmes to be almost 100% certain that your device cannot run 3.0GHz.
[Nexus 5 Original Android Development] drawde40599:
There is probably only going to be 1 out of 100 phones that can handle those high freq . u don't have a issue
[Nexus 5 Original Android Development] TheHighlightGuy:
Hmm... Just had a weird reboot. Maybe the one that people were reporting when they left the phone alone after it booted? Here's the last_kmsg

http://pastebin.com/b6D03vF6

EDIT: One thing to note: all settings stock except vibration amp at 85 and a universal 50mV undervolt
[Nexus 5 Original Android Development] franciscofranco:
Pushed r22:

* Fixes a couple of bugs introduced on r21

For the boot-up crash when underclocking using FKU, I need to issue an update in the app for that bug, I hope I can do push it tomorrow. Sorry for the inconvenience.
[Nexus 5 Original Android Development] daniel84cs:
Franco from version 20 onwards I'm having problems with the same stable configuration that I had with previous versions. With 19 UV -75 never had a reboot, it could be that I have problems with the frequency of touchboost higher and the UV. Maybe I should raise the voltage slightly, but with the 19 I have never had any restart issue with -75 mv on my PVS 3.

The only difference is that before I had the Catalyst 4.1.1 and now the 4.4.2 stock with Art Runtime.

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] mitchdickson:
You sure that doesn't have anything to do with updated Android versions? I have read of another user who was not able to UV as much after the update to 4.4.1.
[Nexus 5 Original Android Development] franciscofranco:
Dunno and honestly I don't care - if you have crashes with UV then don't do it, seems straight forward to me. These devices are made to run with the specified stock voltages, anything else you're always risking failure.
[Nexus 5 Original Android Development] daniel84cs:
You are quite right, then try to remove the UV and see if the problem persists. Thanks for the immediate support and congratulations for the excellent work.

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] 5FOOTER:
Back to cpu1 and cpu2 online and 3 and 4 offline..nice
[Nexus 5 Original Android Development] Tachyon1986:
Well I just realized why I have a slightly higher than normal battery drain. Exchange services (Hotmail) was set to push. Keeps the phone awake frequently. Setting it to 1 hour now, and will check battery life.

Edit: Thanks for r22, didn't have any issues with r21 though
[Nexus 5 Original Android Development] Enddo:
same here, cpus are running how they should be at idle. thank you for the quick update franco. i hope you can relax the rest of the night
[Nexus 5 Original Android Development] daniel84cs:
Franco thanks for R22.

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] KTT16:
Hey man,

Thank you for all your hard work. I also confirm the 2 CPUs online. Awesome! One thing that just happened to me:

1) Auto-flash to r22 via V11.1 beta

2) Rebooted

3) Go into FKU

4) Set CPU to 1574MHz - Set on boot

5) Set Voltage to UV -50 global - Set on boot

6) Exit FKU to homescreen

7) Go back to FKU

8) Tried to reset values, but can't unselect set on boot, or access menus.

Are you or anyone else able to duplicate? Anyway, keep on rockin'!

Best,

K

EDIT: Reboot reset CPU value - and all menus are accessible. Seems like 1574 is a bit too low?

EDIT#2: Set CPU to 1700MHz, but menus froze again...maybe it's the FKU app? Maybe uninstall/reinstall app will help.
[Nexus 5 Original Android Development] franciscofranco:
Thanks for the bug report, I just reproduced it! :) No need to reboot though, force closing the app does the trick, must be some bug in the layouts.
[Nexus 5 Original Android Development] Nucleotide:
I get the feeling this is how [MENTION=3292224]franciscofranco[/MENTION] rolls! :laugh:

Light joke. Love your work man. Greatly appreciate everything you do for both my devices.
[Nexus 5 Original Android Development] Rxpert:
r22 fixes my cpu issues.

Thanks franco
[Nexus 5 Original Android Development] shinesthru:
Ditto. I'm all out of "thanks" for the day so: thanks Franco!
[Nexus 5 Original Android Development] locke84:
LOL'd at this

Anyway, as usual, great job franco, thanks for the r22 :good:!!!!
[Nexus 5 Original Android Development] cobyman7035:
is this the same process for updating the nexus5 w/ franco kernel ? thanks

can anyone confirm this process here?

im still on 4.4 only

and does r22 have FAST usb charging yet? thats like one of the top options i need for custom kernel
[Nexus 5 Original Android Development] :
You could have just done a search this has been answered several times including by Franco himself when 4.4.1 and 4.4.2 were released
[Nexus 5 Original Android Development] daniel84cs:
+1

R22 works very well with my setting.

Inviato dal mio Nexus 5 utilizzando Tapatalk