yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] H.Ahmadi:
Thanks a lot. I already have BBS installed. Here are the screens

Appreciate your help.
[Nexus 6  Original Android Development] H.Ahmadi:
These are screens from wake detector.

Each app is showing different stats. I really don't know what to concentrate on to figure out the fault
[Nexus 6  Original Android Development] H.Ahmadi:
And this is the summary screen from wake lock detector.

I have no idea which app is working with lollipop and reliable. Some are giving similar stats in a section and in another it is completely different.
[Nexus 6  Original Android Development] Krunk83:
Nova

nexus 6
[Nexus 6  Original Android Development] warrenis1234:
we really shouldn't be discussing wake locks in here since it isn't helped or hurt by custom kernels. go to the battery forum in nexus 6 general, all these things are still being discussed
[Nexus 6  Original Android Development] TonikJDK:
Happy birthday sir. I got you a cake, from IKEA.
[Nexus 6  Original Android Development] ijustwantaname:
My apologies, I may not have been clear enough. I know to use the Set on Boot slider, my dilemma is that after rebooting even though the toggle remains enabled the setting itself is back to default values (the set-on-boot settings remain - DT2W is still enabled, for example - but it's back to "disabled). The app is consistently, persistently forgetting my settings on each reboot.
[Nexus 6  Original Android Development] PielunA:
Happy birthday Mr. franco :D
[Nexus 6  Original Android Development] stigui:
Happy birfday Franco listen to some 2pac with your cat.
[Nexus 6  Original Android Development] greeneyez15o:
Im on stock lite, with cata mod. Do i flash franco over , or do i pull out boot.img from stock lite or cata and then flash over? I found stock boot.img on flashify can i flash that 1st and then franco. Or will that make me encrypted again ? Sorry in advance
[Nexus 6  Original Android Development] electricpete1:
I used setcpu on an old phone but I'm brand new to FKupdater pro... confused about the interrelationship among three different ways to set up things like cpu control:

Performance profiles tab: has power-saving, balance, performance. These seem like presets.

Per-app profiles - if don't select one of above presets for a specific app, we can build our own custom per-app profile using 5 parameters: Fmin, Fmax, cpu governor, input boost frequency, max gpu frequency.

cpu manager - sets on boot options: max cpu, min cpu, cpu governor, volt control, governor control, cpu boost, gpu control. More detailed settings

.

Questions (please start with just 1 if you don't feel like tackling them all)

Question 1 - is there any definition of the preset performance profiles? (ex what are Fmin, Fmax, governor for powersaving mode).

Question 2 - custom per-app profiles are completely independent of the three performance profiles? i.e. doesn't matter on whether you had powersaving or balanced selected before the per-app profile is invoked?

Question 3 - when exit a per-app profile... it goes back to the previously selected performance tab preset profile (in yellow), not to the cpu manbager set on boot values?

Question 4 - when I boot, it goes to the cpu manager set on boot options or the preset performance profiles?

Question 5 - are the performance profiles tab items true fixed presets? or are they affected by changes in the cpu manager tab?

I'm obviously a little confused on how it fits together. Hope someone can steer me a little bit.

Thanks in advance
[Nexus 6  Original Android Development] icsterm:
I've installed the paid vomertweaks app from the Play store and it's trash because no more hotplug control on the latest Franco kernel versions. Also If i untick set on boot it still sets the dynamic mode frequency of ~1.5Ghz on boot despite the previous used profile in FKU.

Questions:

1 . to clear all the mess, uninstalling FKU, vomertweaks app and reinstalling the kernel then reinstalling FKU will make the kernel 'out of the box' without any pre-defined boot settings?

2. setting a performance profile to anything except 'balanced' will overwrite any cpu/gpu settings I've saved with 'apply on boot' setting. After a reboot, do my custom on-bootsettings remain saved with the previous settings before applying the performance profile in the first place?

3. do performance profiles stick after reboots or I need to use tasker for that?

4. what exactly does the automatic battery saving option do? The phone already has one built in Marshmallow ROM. When the battery level is lower than the threshold, will this auto-activate 'Power saving' profile? If the Marshmallow battery saver option kicks in with FKU bater saving option at the same time, will the phone too much and I should use just one of the features at a time?

5. Does the balanced/performance performance profile top up at 1728 MHz max? Because I've reinstalled the kernel and it won't even let me set anything above this value as max cpu frequency. I think it's the vomertweaks that messed my kernel or it's some kind of bug with the FKU app // FIXED by me, it seems the battery saving was locked somehow and I had to charge my battery.
[Nexus 6  Original Android Development] GeekMcLeod:
I don't post here much anymore because I never have any issues with this kernel. I've tried a lot in my 4 years of Android but I always come back.

As a thank you, I have donated a few beers to the amazing [MENTION=3292224]franciscofranco[/MENTION]. Enjoy my friend! and keep up the amazing work :) 8TJ88364C0222572J.
[Nexus 6  Original Android Development] CRXed:
Most of the times when I reboot, changing brightness manually doesn't work.

I have to disable automatic HBM and then it automatically goes to the correct brightness. Then I enable automatic HBM again and then everything is okay, brightness slider works again.

It's the only issue I have with HBM.

Nexus 6.
[Nexus 6  Original Android Development] pkaiser86:
Ok, I'm just confirming. The warning states:

"If you're already on r42 or newer disregard the messages below - if not:

* If you're on stock rom + r41, or older, you should be flashing stock boot.img first, then r42, or newer;

* If you're on a custom rom + r41, or older, you should dirty flash the rom (or extract its boot.img and fastboot flash it) and then r42, or newer;"

I am currently not running Franco Kernel right now, do i need to worry about the above instructions? Or can i just auto flash?

Thanks in advance
[Nexus 6  Original Android Development] Galaen:
If you are on your rom's stock kernel, and you have NOT switched out your kernel since the last time you flashed your rom, then you do not have to flash your boot image or dirty flash.
[Nexus 6  Original Android Development] pkgnex:
[MENTION=3292224]franciscofranco[/MENTION],

It appears Google updated the stock kernel as part of the March security update. The boot.img file size is actually smaller than previous, and the source has been posted to AOSP.
[Nexus 6  Original Android Development] icsterm:
Is it normal when I use my phone in max brightness(slider maxed) with both adaptive brightness and high brightness mode on off, for the display to wake up sometimes at minimum brightness? The slider is still at maximum brightness and moving the slider fixes the problem.

Also, double tap to wake up works 25% of times. I need to try different spots and many times before the display comes on. Can aggressive doze from Greenify to be the fault of this issue? Seems kinda odd.
[Nexus 6  Original Android Development] jameseelin:
hi, thanks for your excellent work :)

I'm new to this custom kernels thing and you're the first one that came to my mind when I thought of what custom kernel to try out :D

I've a question, I'm currently running stock rom with your latest r42 kernel on default settings.

I have greenify installed as well, and it seems like the function "cut wake up path" (the scissor logo) is missing? I have rebooted a lot of times and yes I have root (system-less root). Can someone help?

Thank you!
[Nexus 6  Original Android Development] sashank:
Hi everyone, I'm coming back here after a quite a while. I've read Franco's posts about the changed flashing method from r42 onwards. I just wanted to ask if there's any way to just be able to flash the boot.img as before? When I was rooted I used the FKUpdater paid app to flash the kernels, but after years of rooting I stopped when Lollipop 5.1 was released. After that, I used to just download the boot.img from Franco's site and flash it but it seems like I can't do that now. Is there any way to flash the latest r42 for shamu without rooting/flashing custom recovery? Thanks.
[Nexus 6  Original Android Development] holeindalip:
Absolutely,

Fastboot flash stock boot.img

Fastboot boot recovery (recovery image name)

While in twrp transfer r-42 over to phone and flash away
[Nexus 6  Original Android Development] sashank:
That worked great, thanks! I completely forgot about booting into TWRP, though I've done it quite a few times before. I guess I've been away for too long :D
[Nexus 6  Original Android Development] CRXed:
For me it's the other way around, it starts at maximum brightness and moving the slider doesn't do anything. High Brightness mode is kinda wonky, it messes up the normal automatic brightnes, but only after right a reboot.
[Nexus 6  Original Android Development] ameerhashoul:
i am having random reboots here.. (every 2-4 days) phones just lags/ freezes and then it restarts, i have franco 42 + chroma latest version, what should i do? thankss
[Nexus 6  Original Android Development] jmtjr278:
You need to post logs after a reboot to help diagnose the problem. Without logs and a bit about your setup we can't help too much. Do you under volt? That's often a cause.
[Nexus 6  Original Android Development] madyoda:
Random Reboots

Completely random reboots here also. no pattern, nothing.

Unsure what to post, I have /dev/kmsg which is below and I can also post a logcat from when the device booted back up.

/dev/kmsg: http://hastebin.com/raw/ifuqaqojal

edit: this is on dirtyunicorns, but same behaviour was on stock 6.0.1 aswell.
[Nexus 6  Original Android Development] gabethepiggy:
my battery life is off on version 42. often tells me something like the battery is at 41% when twrp tells me it's at 37% and I'm on the latest twrp
[Nexus 6  Original Android Development] mgear356:
[MENTION=3292224]franciscofranco[/MENTION] any goodies for N6, like what happened in March's build for 6p, 5x where there is better performance hidden in the improved frameworks?
[Nexus 6  Original Android Development] TonikJDK:
He posted on google plus that the performance enhancements wouldn't apply to the 6. Different hardware. But that we were missing a couple of the security updates.
[Nexus 6  Original Android Development] randiye:
what settings do you guys use that gives the the best battery life, in your opinion? Thanks!
[Nexus 6  Original Android Development] graydiggy:
That's an extremely open Question. No one person will have the same experience. It's best to try some settings and see how they work. There are plenty of suggestions in this thread alone.
[Nexus 6  Original Android Development] randiye:
well, I don't know how to alter the settings so I just wanna see what people are using so i can use them too.
[Nexus 6  Original Android Development] icsterm:
Hell, I'm getting almost 7 hours of screen-on time with brightness pumped at 50%.

This kernel is bad-ass.

Anyone can tell me their UV settings so I can have a start point for tweaking voltages?
[Nexus 6  Original Android Development] randiye:
should I disable the wakelocks for better battery life?
[Nexus 6  Original Android Development] rignfool:
You should learn what the wakelocks are... And what they let happen...

Then you should see if they affect your battery...

Then you should decide if the features you lose by blocking them are worth losing...
[Nexus 6  Original Android Development] randiye:
Switching kernels

I'm currently on chroma with hellscore kernel. I want to switch to franco. Is it necessary to first dirty flash the rom then flash franco?
[Nexus 6  Original Android Development] gee2012:
Yup, it is highly advised or you may run into trouble ;)
[Nexus 6  Original Android Development] Prack:
[MENTION=3292224]franciscofranco[/MENTION] my phone is too boring, could you update the kernel and introduce a few new bugs? :)
[Nexus 6  Original Android Development] Didgeridoohan:
I've been a bit annoyed at my phone the last week or so. The screen would be so dark when turning it on I didn't even realise it was on. Initially I thought the phone was sluggish and not reacting to pressing the power button. But, after a few seconds the brightness would increase and everything would be back to normal. I also noticed that the light would randomly dim from time to time during use.

Today I disabled "Backlight dim" in the kernel settings and everything is back to normal.

A bit aggressive that setting...
[Nexus 6  Original Android Development] TR2N:
Updaaaaaaaaaaaaaate?
[Nexus 6  Original Android Development] rignfool:
Nooooooo

Eeeeee

Ttttt

Aaaa
[Nexus 6  Original Android Development] NLBeev:
Ignoring could be an alternative for shouting.
[Nexus 6  Original Android Development] TR2N:
I am just asking because of missing March security updates..
[Nexus 6  Original Android Development] gabethepiggy:
well you have to realize that starting with r42 Franco kernel uses anykernel which uses the kernel you flash it over as a base, ergo he most likely doesn't need to update the kernel for security as long as the kernel you flash it over has the security patches
[Nexus 6  Original Android Development] christianpeso:
I don't think that is true.
[Nexus 6  Original Android Development] rignfool:
True... If the changes are in the ramdisk...

But... If the changes are in the zimage...
[Nexus 6  Original Android Development] TonikJDK:
I went back to stock kernel. Not running without that kernel patch. But I do miss this one.
[Nexus 6  Original Android Development] TonikJDK:
Confirmed with Franco that 42 will overwrite the March patches. He mentioned we are only missing 1 or maybe 2 of the kernel patches.
[Nexus 6  Original Android Development] deeppans:
[MENTION=3292224]franciscofranco[/MENTION] will there be kernel update for Nexus 6?

Thanks for your good work!
[Nexus 6  Original Android Development] rignfool:
See the message DIRECTLY... Above yours...
[Nexus 6  Original Android Development] Didgeridoohan:
The message directly above his doesn't really answer his question. It only confirms that fk r42 for the N6 is slightly outdated (but it's still quite usable).
[Nexus 6  Original Android Development] rignfool:
It mentions that Franco is happy with r42... And don't worry till April...
[Nexus 6  Original Android Development] ben_pyett:
Just to say running Franco 42 on April security update, have encountered no issues in last 12 hours.. Behaviour appears normal.
[Nexus 6  Original Android Development] mikeprius:
Is there a way to turn off the hepatic feedback (vibrate) on double tap 2 wake ?
[Nexus 6  Original Android Development] franciscofranco:
r43 is up! You're ****ing welcome.
[Nexus 6  Original Android Development] TonikJDK:
Installed, no issues and no cats were harmed in the process.
[Nexus 6  Original Android Development] franciscofranco:
Beautiful.
[Nexus 6  Original Android Development] szale9001:
Hey franco, just in case it wasn't intentional, you disabled KSM and enabled Process Reclaim in your ramdisk. Only, process reclaim isn't in the code. Just fyi. :confused:
[Nexus 6  Original Android Development] gabethepiggy:
does anybody know if the battery percentage is accurate in the newer twrp images?
[Nexus 6  Original Android Development] franciscofranco:
**** me. I was working on it a couple weeks ago and I forgot I didn't finish the merge. Thanks.
[Nexus 6  Original Android Development] franciscofranco:
What does that have anything to do with the thread?
[Nexus 6  Original Android Development] cyberon:
Shall we wait for another version or is this one safe to use? ?
[Nexus 6  Original Android Development] TonikJDK:
Mine is running fine on 43. Based upon my computer knowledge and googling the terms mentioned I would say it currently isn't handling memory as well as it could.
[Nexus 6  Original Android Development] Prack:
r44 coming yes/no maybe so? Also I'm still not getting credit for flashing these in FKUpdater since the any kernel update. How will I ever be a flasher warlord?!
[Nexus 6  Original Android Development] chillwill11:
Thankyou very much for the updates Franco ?
[Nexus 6  Original Android Development] franciscofranco:
Of course it's safe to use -_-

That's nothing like it.
[Nexus 6  Original Android Development] mikeprius:
Is there a way to disable the vibrate during the double tap to wake
[Nexus 6  Original Android Development] franciscofranco:
Not currently. Why?
[Nexus 6  Original Android Development] pkgnex:
r43 wifi

[MENTION=3292224]franciscofranco[/MENTION],

I had a weird wifi issue that I have to assume is related to disabling all the wlan_* wakelocks by default in r43.

After flashing r43 I could not connect to wifi at all. Trying to turn on wifi in settings = "looking for networks" infinite sit-and-spin.

I re-enabled all the wlan_* wakelocks in fku, toggled to set this way on boot, and rebooted... same thing. Could not see any wifi networks.

Reflashing r43 fixed it - but only after setting the wlan_* wakelocks to enabled and setting the "on-boot" toggle. Simply re-flashing the kernel without forcing these boot settings left me with no wifi.

BTW - better battery stats never showed the wlan_* wakelocks being an issue on my phone since 5.0. On 5.0.1 onward these wakelocks literally kept my phone awake for 1 - 10 minutes in a 24 hour period... so disabling these by default is not worth chasing anyways IMHO.

Anyone else having wifi issues with r43? If so, I hope the process described above can help you.
[Nexus 6  Original Android Development] mikeprius:
No worries. I'm just OCD. I prefer to have no vibration as I use double tap to wake my phone all the time and I don't like it to viberate:) I keep my phone silent at all times.
[Nexus 6  Original Android Development] franciscofranco:
I really REALLY doubt that's anywhere related. When the phone is awake and being used wakelocks are worthless. The idea of a Wakelock is to wakeup your phone from idle (screen off) to perform some task, because the device is almost shutdown and peripherals are power gated. So when the display is on wakelocks are not doing anything since there's nothing to wake up.
[Nexus 6  Original Android Development] SubwayJrd:
Just to confirm, I've been on multiple different WiFi networks since flashing r43, no issues at all with the default (wlan_* wakelocks disabled). Connects fine and fast, as always.
[Nexus 6  Original Android Development] pkgnex:
Fair enough. You know more about this than I ever will so am confident you're right.

It was probably just some freak coincidence.

BTW, I do know what wakelocks do... I was just theorizing that maybe not allowing wifi to wake up after being in idle was preventing it from waking up at all for some odd reason.
[Nexus 6  Original Android Development] electricpete1:
Maybe two freak coincidences. I've had franco a long time, no problems, wifi fine. Then a week or two ago, I was surfing and google chrome got bogged down and pretty much froze. That seemed to be the beginning of my problem... ever since then my Nexus 6 has been very spotty on wifi while my other devices/pc work fine on the same network. Cleared cache in recovery, rebooted many times, no luck. I was hoping it would cure itself when I flashed the complete April update (including stock kernel) but it didn't. Ran a day or so on stock kernel with April update... still had the problem (does FKupdater affect those settings even on the stock kernel?). Flashed franco r43... still had the problem. Read the comments from pkgnex above and tried it out...I put all the wlan* switches on, made them all enabled, toggled a few times for good measure and left enabled, rebooted.... been surfing for an hour now better than it's ever been for more than a week. Definitely a night-and-day difference.

Sorry, I'm not trying to turn this into a troubleshooting thread. There may have been some other factors at work on my phone (based on the fact that the problem seemed to start all at once when browsing... I don't think I changed anything in FKupdater around the time the problem started) but toggling those wlan wakelock settings and rebooting definitely seemed to fix my wifi problem for my particular situation.
[Nexus 6  Original Android Development] franciscofranco:
FKUpdater doesn't do anything unless you tell it to. It doesn't even work without root. Stock Kernel has all those wakelocks enabled and it doesn't have the hooks to even disabling them.

I think that's one big coincidence. If it's borked with stock then it's nothing I'm doing.
[Nexus 6  Original Android Development] pkgnex:
Wait. What? FKU doesn't fix the stock kernel, correct random software and hardware glitches, or otherwise automagically make the world a better place?

Then why did I buy it?
[Nexus 6  Original Android Development] franciscofranco:
Because I demanded you to!
[Nexus 6  Original Android Development] pkgnex:
I think osm0sis said I needed to buy it in order to become a member of the Dev Team club, or something ;)
[Nexus 6  Original Android Development] Omar04:
Hello Fransiscco

Well I have an issue with the kernel, rocking r43. Ever since flashed the kernel started to experience display issues, is like half of the display is upside down and other half is okay. Its way weird, never seen something like that, it happens every time I'm using the phone but only after opening any app, after spending a min or two it happens. To get rid of the issue I have to lock screen and unlock device again.

Device: Nexus 6

ROM: Currently CM13

But happens with any ROM I used so far like: (DirtyUnicorns/Chroma/CM) when Flash FKr43 I believe is something with the kernel because the only

common denominator here is when flashing the Kernel that always happens. Maybe I'm wrong Franco. Can you check things related to GPU/Display/Graphics on the kernel?

All is okay every time I go back to Original ROM Kernel. I don't know what's wrong.
[Nexus 6  Original Android Development] NOSTALGIA:
on stock and not having this split screen issue with r43
[Nexus 6  Original Android Development] franciscofranco:
Does it happen with stock rom?
[Nexus 6  Original Android Development] NOSTALGIA:
not happening on stock rom. im on stock rom right now but its not idling. im losing 1%-3% per hour and i dont have any rogue apps as i can see
[Nexus 6  Original Android Development] bmakk2055:
+1
[Nexus 6  Original Android Development] MrBrady:
Isn't that the screen tearing issue that is so popular with our device? I hear Motorola knows about it and will RMA the phone. Mine does that too occasionally, but it definitely seems to be affected by which kernel I run.

For example, I am currently on Blackbird kernel and was getting more screen tearing than normal. What eliminated it for me was flashing the Adreno GPU drivers from Qualcomm.

Edit: Here's the link if you want to try. I flashed the updated version on the last page. http://xdaforums.com/nexus-6/themes-apps/marshmallow-qualcomm-adreno-gpu-drivers-t3227999
[Nexus 6  Original Android Development] franciscofranco:
I'm pretty sure it's either an app or bad service or something.
[Nexus 6  Original Android Development] franciscofranco:
Yeah, this been happening since the day the device was released, stock or not.
[Nexus 6  Original Android Development] TR2N:
No, I can confirm that. Since r43 my battery drains as ****.. And nothing has changed, just the kernel update. Maybe the missing patches you forgot to merge?
[Nexus 6  Original Android Development] NLBeev:
Did you check the value of 'wifi_suplicant_scan_interval' in 'build.prop' ?
[Nexus 6  Original Android Development] pkgnex:
It's something specific to your device - or maybe a bad download. I've been on r43 since it dropped an my phone is sleeping like a baby - 0.5% idle drain, 26 hours off charger right now with 51% battery left - 2.5 hrs screen on time.