yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] Byrd San:
So far the wlan_rx_wake wakelock doesn't seem any higher to me than it normally is (and it can get unusually high sometimes but that's probably router related issues). I got some pretty decent result with msm_hsic_host disabled yesterday. There was no difference in my data than with it enabled and my phone seemed to idle better too. I unplugged it around 4:00PM with around 90% battery and when to bed around 3:00AM with around 65-60% battery left. And that's with me usual my phone like I usually do. My phone would normally be on the charger after about 8 hours of usage, and I live in a area where I get crappy service. So far so good for me though. I'm giving it another run today with my battery fully charged and I should have my final verdict later on today/tonight.

Side note: I read that Imoseyon released a test kernel where he drastically reduced both wlan_rx_wake and msm_hsic_host wakelocks and a few users already have had good results from it. Just out of curiosity, would doing the same thing to wlan_rx_wake like you did to msm_hsic_host have horrible effects on our phones and break completely WiFi and data functionality or is Imoseyon's method a safer bet?
[Nexus 6  Original Android Development] franciscofranco:
Imoseyon's solution is probably safer. I don't really know why wlan_rx_wake is held, I can assume is either the chip wakelocking to either scan the network, or scan for networks to connect, or trying to hold on if the signal is weak. I'm assuming, I don't know.
[Nexus 6  Original Android Development] paychex:
Can you release a kernel with no kernel wakelocks?
[Nexus 6  Original Android Development] sirbanger:
I'm curious, similar to the Nexus 5, is gamma control possible for the Nexus 6? I know we have RGB control, but would love to have gamma control so I can make the display a little cooler.

It would be awesome to recreate my banged_up N5 profile for the N6 :)
[Nexus 6  Original Android Development] enzoevo:
I want a kernel that just makes my phone sleep. Always. I'm wet thinking about the battery life. :rolleyes:
[Nexus 6  Original Android Development] githyanki:
I don't know what I said to upset you. I did not explicitly, or implicitly, implicate any ROM, custom or stock. If it sounds better, I could have said that it is the general consensus that it is not the kernel, but Franko is trying to ameliorate the issue with a kernel change.
[Nexus 6  Original Android Development] franciscofranco:
I hope you're joking, if not... then I seriously suggest you to read what is a wakelock and what its purpose.

I haven't attempted anything on gamma adjustments, I don't know if it's possible, or not.
[Nexus 6  Original Android Development] C00lBeanz:
What color profiles are you guys using for a cooler screen?
[Nexus 6  Original Android Development] franciscofranco:
I use 237,238,255 since I got my phone, it's been set-on-boot every since, I don't even remember anymore that this is not stock colors unless for the first seconds after a reboot.
[Nexus 6  Original Android Development] laureanop:
The sensor_ Ind wake lock is a known bug in stock Lollipop images and AOSP. It doesn't matter what ROM you're on. Your apps and set up trigger it.
[Nexus 6  Original Android Development] stas333:
that is a good combination.
[Nexus 6  Original Android Development] 413vzwh8r:
Last 2 releases have brought crappy battery life and a much warmer phone.... Stock settings, stock ROM, rooted and kernel only. Nothing else changed. I used to have over 50% battery left at the end of my work day, and now it's down to 37% and I have an hour left. And no my usage isn't higher. Never had this happen before. What has changed?
[Nexus 6  Original Android Development] franciscofranco:
No.

Chances are some app decided to play a game with you by keeping your device awake for longer periods. A couple days ago I noticed my N6 freqs were crazy, cores going up/down, and I was just idling at the home screen. I fired dev options -> show cpu usage and there I see it Quadrant process hogging CPU load like some of my drunk friends drink alchool. Obviously I check it and it's the ads running at the bottom of Quadrant's main screen. I force close the app and boom, CPU load goes back to normal, cores stay put, freqs are not nervous anymore.

There's SO much more that is happening on your phone that can **** your battery life. Flashing a new Kernel isn't necessarily your culprit. Heck, 99% of the times it's not.
[Nexus 6  Original Android Development] Jaspah:
It also depends how much hosts are on the network. At my work, where there are significantly more hosts on the network than at my home, I definitely notice the wlan_rx_wake usage being higher. The phone is picking up traffic (rx meaning receive) generated by the other hosts and quickly determining if that traffic is destined for your phone or not.
[Nexus 6  Original Android Development] slekkas:
With the latest test build with the msm wakelock disabled I get random reboots
[Nexus 6  Original Android Development] Tzfardaya:
Logs please
[Nexus 6  Original Android Development] C00lBeanz:
Thanks that is a really nice combination :good:
[Nexus 6  Original Android Development] sirbanger:
Ok, thanks for the heads up. Fingers crossed for the future :)
[Nexus 6  Original Android Development] paychex:
I am joking. But I think you should do it to prove a point

---------- Post added at 04:46 PM ---------- Previous post was at 04:45 PM ----------

Another reason to pay for apps
[Nexus 6  Original Android Development] suku_patel_22:
Now this is called idle battery drain :)

This is with both disabled. Thanks franco!!

Sent from my Nexus 6
[Nexus 6  Original Android Development] yoyoz808:
After the phone has been in use without booting for a while. I noticed my CPU 1 core stuck at 300mhz using the system monitor. Has anyone experienced this issue? Could this be due to an app?, or system monitor itself having a bug? Using stock ROM stock settings on latest test boot.img
[Nexus 6  Original Android Development] paychex:
Data off and 13 seconds of screen time. I would hope
[Nexus 6  Original Android Development] suku_patel_22:
Was sleeping dude :)

Sent from my Nexus 6
[Nexus 6  Original Android Development] Tzfardaya:
You're not allowed to sleep on xda...
[Nexus 6  Original Android Development] crashercarlton:
Is that saying you didn't have service whether cell/WiFi on the entire time?
[Nexus 6  Original Android Development] suku_patel_22:
WiFi and mobile data off. Had good solid network. That unknown signal must be a bug or something. Will report it to chamonix.

Sent from my Nexus 6
[Nexus 6  Original Android Development] big_adventure:
Don't bother - it will always say no or unknown signal when it is not using mobile data. It even does this when I'm on wifi (but still with mobile signal and mobile data on), and I'm on stock rom.
[Nexus 6  Original Android Development] goinflyn:
Does the kernel control the proximity sensor? Is there a way to make the settings less sensitive? I notice that I have to hold the phone a certain way to keep the screen from turning on during a call.
[Nexus 6  Original Android Development] blueren:
I've noticed this. It's more so because the phone is big (wide) and the proximity censor is not directly atop your earlobe :)
[Nexus 6  Original Android Development] franciscofranco:
The hardware driver for the sensor is obviously on the Kernel, but the Hal (hardware abstraction layer) that connects the hardware to the Android framework is not on the Kernel.

I'm curious, are you using r14 or the test version with sensor_ind disabled?
[Nexus 6  Original Android Development] goinflyn:
I'm using the r14 build.
[Nexus 6  Original Android Development] franciscofranco:
Ok. Nevertheless, proximity sensor behavior is not in the Kernel.
[Nexus 6  Original Android Development] stas333:
been noticing this for sometime now. way before r14
[Nexus 6  Original Android Development] Tzfardaya:
But the proximity sensor is less than half a centimeter from the speaker...
[Nexus 6  Original Android Development] franciscofranco:
This is my last reply to this matter.

Here's what we're gonna do. Flash stock Kernel. And you'll see it will work the same way. Proximity sensor driver on the Kernel is 100% stock. The rest of the proximity sensor stack is on the upper layers.
[Nexus 6  Original Android Development] hdtechk:
Installing cheap screen savers can mess with proximity sensors
[Nexus 6  Original Android Development] RTNDO128:
I'm running the latest CM nightly and color control doesn't appear to be working. I make the RGB adjustments, check the box to set on boot, but everything defaults back to 255 when I go back into the settings.
[Nexus 6  Original Android Development] Tzfardaya:
If the screen saver affects the proximity sensor... It's a dangerously coded saver... Don't use that one... Who knows what other systems it wreaking havoc on...
[Nexus 6  Original Android Development] stas333:
actually, it was doing the same think on the stock kernel
[Nexus 6  Original Android Development] zephiK:
The built-in color control with CM is meant to work with CM's stock kernel and not other kernels.

Stick to using the more uniformed RGB controls as seen in FKU and other kernel apps.
[Nexus 6  Original Android Development] RTNDO128:
That's what I mean. I've flashed franco's kernel over today's CM nightly, and it doesn't work. I'm trying to set RGB in FKU.
[Nexus 6  Original Android Development] franciscofranco:
I have my color settings saved to set on boot since December, never have them once failed on my 100 reboots per-day. My guess is that something is ****ed on your root status.
[Nexus 6  Original Android Development] RTNDO128:
Good call. I had root access prior to installing today's nightly and your kernel, I don't know what the culprit is. There is no longer a "root access" option under my developer options.

Edit: Flashed the 2/13 CM nightly again without flashing your kernel. Root is back and I have the "Root Access" option under the developer options.
[Nexus 6  Original Android Development] Tzfardaya:
Probably just cm not playing nice again...
[Nexus 6  Original Android Development] laureanop:
On the proximity sensor issue, I find that AOSP based Roms have a more finicky one, while stock based ROMs the sensor behaves as it should
[Nexus 6  Original Android Development] hdtechk:
Sorry I meant screen protector I had custom on made once and couldn't answer phone because the covered it up
[Nexus 6  Original Android Development] franciscofranco:
Yes there's something off with Superuser and my ramdisk. I haven't figured it out yet. I suggest you flash SuperSu in the meantime.
[Nexus 6  Original Android Development] HiGhDRo3o5:
Been on this kernel since r6 and always great. Just have one quick question does this kernel hve the ramdisk changes for ok google everywhere?
[Nexus 6  Original Android Development] franciscofranco:
What ramdisk changes? Google Now is completely Kernel agnostic.
[Nexus 6  Original Android Development] HiGhDRo3o5:
Just asking cause i was reading broken os thread and they where talking about wether this kernel had fixes to ramdisk for ok google everywhere to be able to work correctly even after reboot and ive had issues with this myself so just thought id ask. Ok google now works perfect its just when i set it everywhere.
[Nexus 6  Original Android Development] franciscofranco:
Please, don't believe everything you read, 99.99% users on this forums don't know what they are talking about.
[Nexus 6  Original Android Development] yoyoz808:
Is anyone else having a problem after idle sometimes the cpu1 core gets stuck at 300mhz? If I change the performance profile then it goes back to normal.

Edit: it goes back to normal after changing the max frequency and back.
[Nexus 6  Original Android Development] jiv101:
Yeah it's happening to me also
[Nexus 6  Original Android Development] yoyoz808:
Yea after I change the max freq and back, after a few minutes it's gets stuck at 300mhz again.
[Nexus 6  Original Android Development] ShadyBooster:
After the last 2 updates I can never get over 4 hours of SOT before getting to low battery. Eh, something always has to go wrong with my tech.
[Nexus 6  Original Android Development] jiv101:
Are you running volmers tweaks, I wonder if that's the problem
[Nexus 6  Original Android Development] yoyoz808:
Nope. Just good old stock ROM and latest test boot.img Franco kernel with default settings and nothing else.
[Nexus 6  Original Android Development] HiGhDRo3o5:
Wasnt a user was the dev and has said it before so i just thought id ask
[Nexus 6  Original Android Development] hdtechk:
How many new apps have you installed especially social apps
[Nexus 6  Original Android Development] duminduweera:
I've also had cpu0 stuck on 300mhz once.changed the governer to interavtive and back to conservative, now its fine.

I've been running the test kernel with msm_hsic_host disabled and it has worked like a charm for the past 2 days. One more question, do i have to disable msm_hsic_host manually after each reboot, because the value in sys/module/wakeup/parameters/enabke_hsic_hs doesn't stick after a reboot.
[Nexus 6  Original Android Development] enzoevo:
You probably need an init.d script to set it every boot.

Via my CleanROM Nexus 6
[Nexus 6  Original Android Development] ShadyBooster:
None, lel. I don't really use the norm social media, 3boring5me.
[Nexus 6  Original Android Development] franciscofranco:
sysfs entries don't restore their custom states on reboot. That's why we use apps etc.
[Nexus 6  Original Android Development] Janzen254:
[MENTION=3292224]franciscofranco[/MENTION],

Will you add init.d support?
[Nexus 6  Original Android Development] franciscofranco:
Doubt it, init.d it's kinda obsolete, specially now that Root's daemon init can take a while and jeopardize the operation if the init.d run-parts is triggered before the daemon is up.
[Nexus 6  Original Android Development] Janzen254:
OK, I just like how it does it faster than with apps especially to disable the charge LED.
[Nexus 6  Original Android Development] franciscofranco:
Do you really reboot that often that you need that extra 1s with charge LED disabled...?
[Nexus 6  Original Android Development] Janzen254:
No
[Nexus 6  Original Android Development] C00lBeanz:
XPOSED MODULES ARE BREAKING YOUR KERNEL AND IS CAUSING ME PROBLEMS RAH RAH RAH Also I have never kissed a girl.....
[Nexus 6  Original Android Development] lainemac:
I'm having all these problems as well. Plus, my cat barely lasts a full day. And I don't even have a cat!
[Nexus 6  Original Android Development] C00lBeanz:
Made my cat cough up modules, and I have a dog!
[Nexus 6  Original Android Development] Janzen254:
[MENTION=3292224]franciscofranco[/MENTION]

Get ready for all the bug reports caused by Xposed.
[Nexus 6  Original Android Development] uhguy:
I've been running Xposed for 7ish hours with no issues so far. I would hope that people would realize something that requires as many changes as Xposed (especially in an alpha state) would cause issues and not come in here dumping on the kernel. I say hope because I know people will come in here doing that anyway.
[Nexus 6  Original Android Development] wrongway213:
Not directed at you, you are not even having issues lol, just a general statement about Xposed and issues that everyone is predicting: If you have issues with Xposed you need to familiarize yourself with 3 things: your ROM's features, your kernel's features, and the concept of overlap. If you have a basic understanding of those things and understand that overlap, in this situation is completely and totally bad, Xposed can be a great thing - unfortunately most people want GravityBox and baked in goodies... nope.
[Nexus 6  Original Android Development] C00lBeanz:
The Max CPU keeps resetting to 17##! Right when I leave the app, it resets to 17##, please fix this it is making my phone really slow...
[Nexus 6  Original Android Development] suku_patel_22:
You must be low on battery or your cpu temperature must be high or some app might be doing it for you. I have no such issues.

Sent from my Nexus 6
[Nexus 6  Original Android Development] uhguy:
Mine was just a general statement as well lol. I was just stating I hadn't had a problem with xposed (yet) but that I'm sure people will come in here and try to blame the kernel. I probably won't even keep xposed long myself. I'm currently running the stock rom with franco's kernel and that's about all the tweaking I've done to my phone. I don't usually go for all of that other stuff either, but I like to fool with new stuff for a few days till I get bored.

Anyway, back to talking about how awesome this kernel is. :D
[Nexus 6  Original Android Development] C00lBeanz:
Chroma rom, battery 37%, temperature 38.9 Celsius...
[Nexus 6  Original Android Development] suku_patel_22:
Do you have trickster or something similar that would mess with cpu speed? Are you using powersave profile? Are you using vomer?

It has got to be anything but the kernel. Try resetting data of FKU.

Sent from my Nexus 6
[Nexus 6  Original Android Development] C00lBeanz:
Got nothing that messes with the CPU speed, no vomer no trickster, and i'm using the Balanced profile...

EDIT: Deleted Data and Cache and what do you know, it stays at 26## now! :)

EDIT #2: And now it resetted back to 17##...
[Nexus 6  Original Android Development] suku_patel_22:
What does cpu spy say?

Sent from my Nexus 6
[Nexus 6  Original Android Development] oOuzzielOo:
Have you tried reproducing the same behavior using stock Rom?Just asking since no one else seems to be reporting the same issue you seem to be having
[Nexus 6  Original Android Development] zephiK:
My rom has absolutely nothing to do with altering a user's cpu maximum frequency.

I have used the rom on a daily basis testing it before releasing and my maximum cpu frequency has not changed by itself.

Something else is causing your phone to change its maximum frequency. You can find out which one it is one by one but your best and easiest choice is to do a clean wipe, install fku and then your problem should be gone.
[Nexus 6  Original Android Development] Utini:
Just ordered my Nexus 6 and should get it in 3-5 days. And which kernel will I choose? The same as wit hmy Nexus 4 -> franco.kernel :)

Usually the best mix between performance & battery life.
[Nexus 6  Original Android Development] franciscofranco:
But fix what? Do you think I programmed that just to **** you? I'm sure its the thermal driver changing it for you, either low on battery or some other heuristic.

But you're just giving me more fuel to get rid of Qcom's thermal solution.
[Nexus 6  Original Android Development] franciscofranco:
Obvious choice :)
[Nexus 6  Original Android Development] Utini:
I am just curious how you can keep up all the work for the different Nexus devices while there are "teams" of 3-4 people focusing on the development of a kernel for only one device ?
[Nexus 6  Original Android Development] Daki_23:
I'm also facing the same issue, though I don't know what's causing it. My battery level is around 70%. Please tell me what you would need in order to find out what the issue is, and I will do my best to provide it to you.

And thanks for making this brilliant Kernel.
[Nexus 6  Original Android Development] franciscofranco:
The only thing that has the power to change freqs like that is the thermal driver. They have a bunch of heuristics, its a cluster****. I'll just replace it with my simple driver and get done with it.
[Nexus 6  Original Android Development] anthonyg45157:
So did we ever come to agreement on if preventing the msm_hsic_host wake lock has any negative effects. I'm using boot.IMG with sensor ind disabled with no issues at all.

Sent from my Nexus 6
[Nexus 6  Original Android Development] AnonymousPenguin:
How did you manage to get it running on a kernel that by default isn't permissive ?
[Nexus 6  Original Android Development] drdoulittle:
Take Flashify app from PlayStore when FKU say "your up to Date" or flash with adb or restore the boot.img from Folder Backup / FKU
[Nexus 6  Original Android Development] italia0101:
Been running with that disabled for a day now and no problems
[Nexus 6  Original Android Development] TR2N:
Hi guys, is there a reason why vibration settings don't stick after reboot?
[Nexus 6  Original Android Development] suku_patel_22:
Which ROM are you on?

When I was on stock ROM, nothing would get applied on reboot. Now I am on Chroma and everything sticks fine for me on reboot.

Sent from my Nexus 6
[Nexus 6  Original Android Development] franciscofranco:
I was out of the house all day with data and msm_hsic_host disabled and no issues what-so-ever :o battery life's been pretty good together with sensor_ind gone.
[Nexus 6  Original Android Development] suku_patel_22:
Same here. Been running with both dished since Imoseyon released it and later when you added it in. No issues whatsoever.

Sent from my Nexus 6
[Nexus 6  Original Android Development] blueren:
I smell an update
[Nexus 6  Original Android Development] brizey:
Soft reboot after setting to permissive. The app changes things to permissive some time after boot...too late for xposed.

Sorry for the OT.
[Nexus 6  Original Android Development] Janzen254:
How does your thermal driver work?
[Nexus 6  Original Android Development] suku_patel_22:
I am running the test kernel and having some issues while waking up the device. Sometimes it's taking more than one press of the power button to wake it up.

Sent from my Nexus 6
[Nexus 6  Original Android Development] MrMaverick03:
Chroma

If you're running Chroma it probably has nothing to do with the kernel. Uncheck "accidental wake-up" in display settings and you should be good. I noticed a similar issue but all has been well since turning off the feature. I don't use dt2w or ambient display so the feature is not particularly useful.
[Nexus 6  Original Android Development] schizophrenia:
just got my N6 and am getting ready to flash franco.

just want to double check would OTA update of stock ROM be affected if I just flash back to stock kernel? In the past [MENTION=3292224]franciscofranco[/MENTION] you mentioned this in the general Q&A "Franco's kernel changes these system files below, so to change them back you can remove the .bak extension, or fastboot system.IMG and boot.IMG from a Google factory image which is probably easier and faster."

Thanks.
[Nexus 6  Original Android Development] C00lBeanz:
Today it kept clocking to 10##, is anyone else receiving this problem?
[Nexus 6  Original Android Development] franciscofranco:
Nop.

No.
[Nexus 6  Original Android Development] fhk:
Charging led settings do not stick after reboot. Anyone knows why?
[Nexus 6  Original Android Development] SweetwaterBurns:
No one that they'll listen to. Try uninstalling Franco kernel updater, if you have it installed. That fixed it for me.
[Nexus 6  Original Android Development] franciscofranco:
LOL sorry that's bull****, my app does not change frequencies on the fly unless the user has set up Per-App Profiles set up for different apps, but that's the user's responsibility.
[Nexus 6  Original Android Development] schizophrenia:
quick question as I am not sure if it's related to franco kernel.

after flashing franco kernel this afternoon, even if I turned off wifi and "wifi always available".. i still see "wifi" being used on battery graph. Anyone else having similar problem? could this be kernel related at all? This did not happen when I was on stock

Thanks.
[Nexus 6  Original Android Development] old_fart:
Is setup /advanced wifi / notifications ( ie. discovery ) turned 'on' ?
[Nexus 6  Original Android Development] schizophrenia:
yes it is on, whether my wifi is on or off and i never touched that since i bought the phone. Wifi never showed up on battery graph when I was on stock kernel when wifi is off.

I am rebooting the phone to see if it's still like that. thanks anyway