yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] biggiestuff:
Okay my cpu 1 is stuck on 300 right now. I wasn't in deep idle, but I was chatting hangouts a lot and then moved from wifi to mobile when I walked to another building, that's when I noticed the lag when trying to read hangouts while I was walking. I'll leave it stuck at 300 in case you need me to pull something.

Stock ROM

r16 via FKU (full)

noticed at 74% battery life

default FKU settings except for charging LED off

conservative.
[Nexus 6  Original Android Development] mindfever91:
Also cpu0 stuck here on 300 MHz. Output of scaling_governor is "conservative".
[Nexus 6  Original Android Development] Circaflex:
edited
[Nexus 6  Original Android Development] mindfever91:
What do you want? I and several others posted the log he asked for, you even quoted his request. Everything else is totally random ROM stuff that's most likely unrelated to the bug that's obviously happening on the kernel side.
[Nexus 6  Original Android Development] Circaflex:
What apps were you using at the time? I still cant replicate this on 4 different custom roms and franco hasn't either. I do remember franco mentioning the only time he saw something like this happen was when antutu ads in the background made the cpu freqs go crazy. I still think its a rogue app, or conflicting cpu tweaker software built into some roms.

I have never had either of the two recent "bugs" people haven mentioning. My CPU0 doesn't get stuck at 300mhz, nor do my cores 2/3 get stuck at max freq. I have used OMNI Rom, CM, SlimLP and Paranoid.
[Nexus 6  Original Android Development] mindfever91:
Actually I didn't use the phone at all, it has been sitting on idle for about twenty minutes. Prior to that I made a 15 minute call. Of course it's hard to replicate because it happens absolutely randomly. I think I've never seen an app that locked only one cpu core at its lowest frequency, if that's even possible. There's definitely something wrong on the kernel side.
[Nexus 6  Original Android Development] vomer:
GUYS FRANCO KNOWS CPU1 GETS STUCK no need to post it a million times...

things are being investigated.... test the kernel instead of uselessly repeating the same thing... http://xdaforums.com/showpost.php?p=58907831&postcount=3480
[Nexus 6  Original Android Development] Skripka:
A gentleman is someone who knows how to play the piano, and does not.
[Nexus 6  Original Android Development] android_mp99:
I have run this boot.img since you posted it and everything is working fine so far. I will keep running it and let you know if something changes.

Side note: Had a laugh at the donation comments. Also donated the franco.Kernel updater because I think you deserve to be paid again for the constant updates and the updated app. Thanks for the great work and fast response as always.
[Nexus 6  Original Android Development] akhan47:
R14 is running so perfectly for me, amazing battery life. I don't see any need to update, is this ok or am I just being silly?
[Nexus 6  Original Android Development] paychex:
The test image seems to have solved the CPU 0 (let's all try and use the correct nomenclature) issue. Everything is back to awesome
[Nexus 6  Original Android Development] anthonyg45157:
Cpu0 core stuck at 300 for me. The scaling gov says conservative as others have reported.. If you need anything else. Please let me know. Waiting to flash boot image in case you need something from me... Standing by at the ready.

Sent from my Nexus 6
[Nexus 6  Original Android Development] Circaflex:
Your info is the the same info posted by other users, go ahead and flash the test image to see if it resolves your issue.
[Nexus 6  Original Android Development] javacody:
Just checked and I have the 300mhz issue as well! Stock ROM using FKU, no other kernel apps.

I'll run the test kernel.

I would like to add that the fanboys who continually post about how they have zero issues are getting REALLY annoying.
[Nexus 6  Original Android Development] Circaflex:
Similarly, we feel the users continuing to just state "I have the 300mhz bug" are annoying, we get it some have an issue and franco is working on it but continuing to post "me too, me three, I have the 300mhz bug, etc" does nothing.

Can you elaborate how we are "fanboys" because we state we are not experiencing the bug? I fail to see how that makes me a fanboy, but whatever floats your boat.
[Nexus 6  Original Android Development] enzoevo:
Test image seems to have fixed the cpu0 behavior on my n6.

Via my CleanROM Nexus 6
[Nexus 6  Original Android Development] comminus:
Agreed. I'm unable to reproduce the stuck cpu0 behaviour using the test image; the issue appears to be resolved.
[Nexus 6  Original Android Development] insty:
Thanks Franco, this has fixed it for me.
[Nexus 6  Original Android Development] yoyoz808:
[MENTION=3292224]franciscofranco[/MENTION]

Seems the latest worked for me too as well. I'll run it for a little long to see if it happens but from the sounds of everyone else it doesn't seem to do it anymore.

I was trying to figure out how to reproduce it exactly but it seemed to be random I guess. You have any clue to what it could be yet? Or did you find it?
[Nexus 6  Original Android Development] javacody:
We have to continue to post to actually get the issue corrected because you fanboys don't seem to comprehend the nature of computer programming. And then you further go on to speculate that people with the issue are somehow to blame.

It's total BS. I added my comment to add that I'm running fully stock and also have the issue.

It gives more facts and SHOULD help to troubleshoot the issue.

Being a nothingwrongwithmines fanboy isn't helpful. At all.

And to make this post actually useful instead of responding to a jankhole, the test kernel is running well so far.
[Nexus 6  Original Android Development] Circaflex:
its been stated by the OP himself that continuous posting of "me too, me three" doesn't help. Franco is super active in his threads, I doubt reposting over and over will get things done any faster, your comment makes it seem as if there have been major bugs throughout all releases and the only way to "get franco to fix it" is to continuously repeat the same thing over and over. Oh well.
[Nexus 6  Original Android Development] paychex:
True. But simply adding "I have it too" without logs--especially after Franco had asked for a specific thing to look for--adds very little. And is a ****ty thank you for his free kernel. Don't know if that particularly applies to you.
[Nexus 6  Original Android Development] yoyoz808:
Every post helps. Even if it's the same thing. The great thing about Franco is he works with the community and has so many people contribute to help make this device better. You may think it doesn't help but even a first time user can contribute to making this device better for everyone :)
[Nexus 6  Original Android Development] Circaflex:
No, that isn't correct. You guys are missing the point, Franco asked that people no longer post "me too, me three, I have the bug, etc" it does no good. Look, he knows there is an issue, he is working on it, but to just randomly post I have the bug does no good and he has asked that people don't do that; so no you shouldn't keep posting if it is the same info. Instead he wants users to test this boot.img and report back.

http://xdaforums.com/showpost.php?p=58907831&postcount=3480
[Nexus 6  Original Android Development] yoyoz808:
Lol I suppose but if enough people didn't post that similar problem he probably wouldn't have taken the time to look into it. Along the way I think he mentioned finding something else that needed to clean up the code so.....but you're not wrong:good:
[Nexus 6  Original Android Development] zephiK:
Franco already fixed the problem as we've already known this a couple pages back. Bickering about whos right and whos wrong on "me too," "not having problems" posts not contributing, yes they those posts don't contribute to anything but this argument back and forth isn't contributing to anything either.

Just stop. And yes I know my post right here doesn't contribute to anything either, let's move on.
[Nexus 6  Original Android Development] suku_patel_22:
[MENTION=3292224]franciscofranco[/MENTION] Just woke my device up from overnight and had a reboot.

The screen was off. When I pressed the power button it turned on but I couldn't do anything. I tried swiping up to get to the pattern lock but it wouldn't work and then it rebooted.

I also lost 10% overnight and there are no battery stats.

I am running r16 and have made nlo changes to CPU settings. Have only reduced thermal threshold to 60°

Logs at the below link.

https://drive.google.com/folder/d/0B367Vothe28iaVVaeWNBTUYwc3c/edit

Sent from my Nexus 6
[Nexus 6  Original Android Development] franciscofranco:
Pushed r17 which fixes the cpu0 bug **** and fixes a performance regression on sequential read speed.
[Nexus 6  Original Android Development] ozg33k:
Is there an option to cause a little vibration when double tapping to wake?
[Nexus 6  Original Android Development] italia0101:
All I asked was " care to elaborate"? Not sure why you said" how would you know? " I didn't disagree with your statement at all, just wanted to know your situation is all..

Your original post mentioned" not sure why wasn't it posted here to begin with "... Maybe because others didn't have the issue? Food for thought.

And for me, yes, my device goes into deep sleep and stays there longer, so it is helping for me
[Nexus 6  Original Android Development] GregNexus:
is there a way to disable the msm_hsic_host wakelock completely ?Maybe via a function in FKU?

or would [MENTION=3292224]franciscofranco[/MENTION] disable it by default?

This is on top of my wakelocks in BBS.

in the leankernel version 1.14 you are able to set a timer for this wakelock to hold it back.

A testkernel (1.13.2) has shown that there are no negative side effects if you disable it completely.
[Nexus 6  Original Android Development] Damon13:
Hey Greg to disable it go to /sys/module/wakeup/parameters/enable_msm_hsic_ws and change to false, or echo 0 > /sys/module/wakeup/parameters/enable_msm_hsic_ws

the Kernel treats an int 1 or 0 the same as a boolean true or false. It will work regardless, you can echo Y/N or 1/0 or true/false.
[Nexus 6  Original Android Development] GregNexus:
Thanks for your quick response :)

If the kernel gets an update, i have to change it again to false? Or is this an procedure that i have to do just once?
[Nexus 6  Original Android Development] suku_patel_22:
You need to do it on every boot.

Sent from my Nexus 6
[Nexus 6  Original Android Development] GregNexus:
:crying::crying:
[Nexus 6  Original Android Development] rignfool:
Or learn how to write an init.d script... And where to put it :)
[Nexus 6  Original Android Development] suku_patel_22:
Or use apps like Llama or tasker

Sent from my Nexus 6
[Nexus 6  Original Android Development] kergefarkas:
Or wait for the FKU updater that will add a ticker for this (or maybe it will be just the other one, can't remember properly)
[Nexus 6  Original Android Development] GregNexus:
jep, i will give it a try :cowboy:

What could be the reason, that franco has not disabled it?
[Nexus 6  Original Android Development] SmokeyMon:
Its not proven so he made it optional. He did say there will be a toggle button in the next fku app update.
[Nexus 6  Original Android Development] GregNexus:
oh dude, you made my day:D
[Nexus 6  Original Android Development] franciscofranco:
Next FKUpdater will have toggle for that, don't worry! :)
[Nexus 6  Original Android Development] suku_patel_22:
Hey did you take a look at the ram oops I posted here?

http://xdaforums.com/showthread.php?p=58920965

Sent from my Nexus 6
[Nexus 6  Original Android Development] GregNexus:
Love your support!

Is it possible to make a larger donation than 10€?:D

Hope there will be an option for this in the next update too!:D
[Nexus 6  Original Android Development] franciscofranco:
Yes, it's a bug on the GPU stack. I can reproduce that on stock Kernel/rom. Nothing we can do.

Hmm, 10's probably the max for now, but if you want you can buy those multiple times.
[Nexus 6  Original Android Development] michmeister:
I know version 9 of this kernel works with xposed, if I update kernel to latest version will it still work?

Im on liguid ROM.
[Nexus 6  Original Android Development] HTC_Phone:
Currently running r17 with xposed
[Nexus 6  Original Android Development] michmeister:
Without soft reboot after every boot? Not working for me. Just works with r9.
[Nexus 6  Original Android Development] tmrma:
have now random reboots with r17. is there a solution?
[Nexus 6  Original Android Development] dark2099:
Yup, explain exactly what you are doing when they happen, and provide logs for Franco. Them he will be able to figure it out. No info means no fix.
[Nexus 6  Original Android Development] suku_patel_22:
No logs and no fix. Post logs from /sys/fs/pstore right after a random reboot.

Sent from my Nexus 6
[Nexus 6  Original Android Development] tmrma:
thanks, which log you mean annotate or console or both? I'll check this after a reboot. it was previously 3 reboots since r17 but before it just does not (r16...). have stock rom with, fk with disabled msm_hsic_ws, nothing special set with fk-app (led, dt2w disabled, conservative setting, sometimes max cpu to 1,9ghz; i have now changed to 2,7ghz again)
[Nexus 6  Original Android Development] suku_patel_22:
Yes both of them.

Sent from my Nexus 6
[Nexus 6  Original Android Development] taranfx:
[MENTION=3292224]franciscofranco[/MENTION] Can you add minimum frequency support for 35mhz? Vindicator kernel supports and it works pretty well.
[Nexus 6  Original Android Development] franciscofranco:
Nope. Qualcomm engineers know better than us, if 300MHz is the minimum then must be a reason for that. Besides, with a frequency SO low the device would be ramping up all the time, negating any <possible(?)> battery improvements on a lower frequency.
[Nexus 6  Original Android Development] taranfx:
If only Qualcomm knew the best, MP-Decision would've been awesome. Make-Poor Decision => Make-Precise decision.
[Nexus 6  Original Android Development] Pure Drive GT:
getting last_kmsg

Dunno why but I'm having trouble grabbing kernel logs. How do you guys do it? I used to simply go to where the last_kmsg is and grab it but now it's just called kmsg but more improtantly I always fail to simply pull it over, even with adb pull in root mode. I can't even simply open it. A few posts earlier there is something about /sys/fs/pstore, there are 3 files located there, which one is important?

adb shell cat /proc/kmsg gets stuck up :(

adb shell dmesg > xyz.txt does not really show me what I want to see :(

Sorry for this probably being a noobish problem, but any advice would be appreciated.
[Nexus 6  Original Android Development] franciscofranco:
/sys/fs/pstore/console-ramoops
[Nexus 6  Original Android Development] okgnew:
I get no WiFi and no BT on r17 (does not connect to any router/device).

Reverted back to r15 and everything works fine.
[Nexus 6  Original Android Development] Circaflex:
what rom? I believe it is something on your end, otherwise this thread would be flooded with these same reports after franco released r17
[Nexus 6  Original Android Development] okgnew:
Stock ROM

Build LRX22C
[Nexus 6  Original Android Development] damosthated162:
my results

I am running 14 and this is what I get, the device is flawless, doesn't overheat like some other versions IMO and the device is just snappier. Thank you Franco...
[Nexus 6  Original Android Development] GaSpartacus:
After flashing r17 i have two cores stuck at max freq. Going to reboot and see if it doesn't comeback

Enviado do meu Nexus 6 através de Tapatalk
[Nexus 6  Original Android Development] trickster2369:
I've used both today without issue.

Sent from my SinLess Shamu
[Nexus 6  Original Android Development] franciscofranco:
Coincidence, Wi-Fi and BT stack is stock and I made no changes on r17 on anything that could affect it.
[Nexus 6  Original Android Development] HipKat:
Works fine in Chroma....
[Nexus 6  Original Android Development] CRXed:
Just had a Force Close in the FKU app.

When the new kernel notification came in and I pressed it, it opened the changelog. Then when I pressed the circle icon below the changelog, FKU crashed.

Have sent the report.
[Nexus 6  Original Android Development] Andrewtst:
Thanks for this wonderful kernel, it is blazing fast, so far so great everything is working. :o
[Nexus 6  Original Android Development] biggiestuff:
My issue went away and I'm pretty sure it wasn't related to the kernel at all but I thought it was weird. I flashed r17 while on the carpet floor. After flashing I couldn't connect to my 5ghz network. Restarted still couldn't connect. Removed and tried to add back no luck. 2.4ghz was fine. Finally I lifted it off the carpet and it connected. Put it back on the carpet and it lost connection. I was able to repeat for about 5 times and finally it stopped and all connectivity was fine. Pretty weird I must say. Yeah sorry to waste your time.
[Nexus 6  Original Android Development] Janzen254:
Do you have carpet that interferes with ≈5 GHz ISM radio bands?
[Nexus 6  Original Android Development] franciscofranco:
Think you can grab me the log manually? adb logcat | grep com.franco.kernel
[Nexus 6  Original Android Development] feered:
SELinux option feature?

Will there ever be a SELinux option similar to ElementalX. I'd like to have the ability to alternative from permissive to enforced.

Thank you!
[Nexus 6  Original Android Development] franciscofranco:
permissive

adb shell
su
setenforce 0

enforce

adb shell
su
setenforce 1
[Nexus 6  Original Android Development] feered:
Thanks. Does this permanently set SELinux? Or is this required after each boot? I only ask because Xposed requires permissive and doing a soft reboot each time to obtain functionality from Xposed is tedious, especially when you have to reboot for each installed / updated module.
[Nexus 6  Original Android Development] biggiestuff:
Haha I was thinking I did. It definitely was strange.
[Nexus 6  Original Android Development] dcoy82:
Hey Franco, love the kernel and app thanks for the hard work. I've had two random problems though not sure what's causing it. Twice in the last couple of days (on r15) the right half of my screen froze up while my left half was still functional. Seems like something happening with the gpu maybe. I didn't get a chance to get a logcat, and I just upgraded to r17 moments ago. The first time it happened I turned the screen on and double clicked on a notification to launch it, the second time I was playing a game. Aside from that, it's working great!
[Nexus 6  Original Android Development] Janzen254:
Hardware problem
[Nexus 6  Original Android Development] hutzdani:
Ah fair play I just got back from flashing some other kernels with light flow for the tutorial and posted my findings, I just never checked all the posted here.
[Nexus 6  Original Android Development] wrongway213:
Everyone, installing ANY new kernel will "break" LightFlow until you clear app data and set it up again. Franco is just EXTREMELY popular so everyone flashed it and that was the first time many users saw their LightFlow stop working so now everyone thinks this kernel messes up LightFlow.. it doesn't in any way more than flashing absolutely any other kernel
[Nexus 6  Original Android Development] zenxaero:
Does this happen to anyone else when trying to go in CPU_Boost
[Nexus 6  Original Android Development] zephiK:
No.

1. Are you using Franco Kernel?

2. Is your app updated to the latest?
[Nexus 6  Original Android Development] stas333:
yes. happens to me.
[Nexus 6  Original Android Development] saddog5523:
Same thing for me. Everything is updated to the newest everything.
[Nexus 6  Original Android Development] caspersfi:
Same here. Blank screen on CPU boost. Just confirming.
[Nexus 6  Original Android Development] Krunk83:
That directory is empty. Future update?

nexus 6
[Nexus 6  Original Android Development] owyheendn:
Anybody Running this with Validus Rom? And if so what Gapps you using? I really wanna try Validus, but its hard to track down the info over on Google+ lol, Thanx
[Nexus 6  Original Android Development] dems86:
Ditto here as well...didn't want to be left out ?
[Nexus 6  Original Android Development] enzoevo:
Yes. Mine is empty as well.
[Nexus 6  Original Android Development] caspersfi:
Sent ya a PM with info. So we don't clutter thread. :)
[Nexus 6  Original Android Development] owyheendn:
Thanks buddy
[Nexus 6  Original Android Development] franciscofranco:
Bug on FKU. Fixed next release.
[Nexus 6  Original Android Development] wolfeyes30:
Same here.
[Nexus 6  Original Android Development] epicnoob66:
I think there is some magic in franco's kernel, or vomer's tweaks...maybe its the combo. So far I'm have the best battery on my device ever!

Tldr Thanks
[Nexus 6  Original Android Development] matrox00612:
Hi Franco,

Its possible to have init.d support on next release?

Thanks, for great Kernel
[Nexus 6  Original Android Development] wrongway213:
Kernel has init.d support, it's certain ROMs as well as stock Android that do not have init.d support. Both are required, for example a rom with init.d support requires a kernel with init.d support just as a kernel with init.d support requires a rom with init.d support.
[Nexus 6  Original Android Development] matrox00612:
I'm using Team Nocturnal Limited Edition 2.06, if I use the Kernel that came with rom and the LK 1.3 Kernel with both works, but with FK r0.2 did not work that's why i assume that need init.d support.
[Nexus 6  Original Android Development] wrongway213:
This app will tell you whether or not your ROM/kernel has init.d support and if it doesn't it'll enable them.. and it's free :good: https://play.google.com/store/apps/details?id=com.androguide.universal.init.d
[Nexus 6  Original Android Development] dcoy82:
I don't think it is, I had the phone for a little while running stock kernel and it didn't start doing it until I flashed this kernel a couple days ago.
[Nexus 6  Original Android Development] Janzen254:
It is a known issue. Just search "Nexus 6 half screen" on XDA or Google (or your prefered search engine).
[Nexus 6  Original Android Development] franciscofranco:
It's not permanent no. Well, though luck with Xposed. I'm not going to compromise the device security because of a shady injection mechanism. I applaud the Xposed developer, it's an engineering feat, but the whole process is SO hacky and leaves so many security breaches open... Anything that involves Xposed is up to the user and I wish to play no part in it. Sorry if the answer disappoints you, but this is my view of things and it most likely ain't gonna change.

That split screen thingy happens on any Nexus 6, it's random, it also happens on 100% stock devices. That random reboot that you describe I've also seen before on stock Kernel. In fact, I had a reproducible case using FKUpdater, I could crash the device instantly due to a GPU hang during a RenderThread operation. It's ugly. I reproduced it with Stock, FK and LeanKernel. There isn't much I can do :'(
[Nexus 6  Original Android Development] Janzen254:
I hope I never see it.
[Nexus 6  Original Android Development] dvdivx:
Maybe I'm wrong but can't you manually change SELinux Permissive through a command prompt or using the SELinux app or does that not work with this kernel?
[Nexus 6  Original Android Development] franciscofranco:
Yes... I posted the command last page..
[Nexus 6  Original Android Development] Janzen254:
Yes, go to page 358 for the command line.
[Nexus 6  Original Android Development] dvdivx:
Looking back the question got unanswered as to if it's temporary or permanent unless manually changed back. I don't know if manually changing it is permanent.
[Nexus 6  Original Android Development] Janzen254:
That was answered on this page (359).

Not permanent
[Nexus 6  Original Android Development] franciscofranco:
I answered... I said most likely not permanent (99% certainty).