yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Original Android Development] lobrau:
[MENTION=6364268]Franciso[/MENTION]franco Thanks for the awesome work on this kernel so far. I've personally noticed that there is a bit of stutter on scrolling performance start up and finish (smooth during). Performance otherwise is imperceptibility different from stock. Is there an easy governor tweak to help this while minimally impacting the battery life. Or is there some other method you suggest? Thanks for the info on the readahead buffer.
[Nexus 6P Original Android Development] blueren:
Thanks Franco. On a separate note, Is PAM working completely OK? Or is it still WIP? I say this because I've caught the high power CPU in ridiculously low max freq every now and then (the app says so) and it's not due to throttling. A reboot bumps it back to normal.

Secondly, I've noticed this:

You're in an app with PAM enabled. You swipe down the notification shade to read the notification - PAM deactivates. Swipe it back up, the PAM doesn't re-enable again. Need to get out of the app and in again.

The reverse is also true. You read a notification from an app that has PAM, and the profile turns on even though I'm not in the app

This doesn't happen all the time though. Is this all expected behaviour?

Yes, I noticed that it was atmos too. The sound quality increases multifold when the app is active, even though viper is on. Too bad it derps out when screen is off. Most of the time, I listen to music when I do nothing on my phone. So will have to force it off and lose out on the soundgasm :). Is it the same case with beats?
[Nexus 6P Original Android Development] franciscofranco:
Hmm. You can increase input_boost_ms inside CPU Manager to 500.

Is that with a custom PAProfile or using one of the pre-built Perf profiles inside PAM?
[Nexus 6P Original Android Development] blueren:
Custom profile. Basically I have a couple of them which only bumps down the max cpu freq. Nothing else. One for a game, one for a reading app. Both have max freq set to around 900MHZ. which itself is plenty sufficient.
[Nexus 6P Original Android Development] franciscofranco:
Can you try the same thing but with the preset profiles?
[Nexus 6P Original Android Development] squall_kay:
today tried again to install this kernel, still not success.

steps that i had done:

1. restore to factory image. boot. ok.

2. root (Su2.66)

3. install chroma ROM+Gapps

4. reboot. ok

5. install franco kernel

6. boot, stuck chroma hexagon logo
[Nexus 6P Original Android Development] rebretz000:
You gotta flash Franco then SuperSU.
[Nexus 6P Original Android Development] troffers:
Flash SuperSU again, AFTER flashing the kernel. Read the OP
[Nexus 6P Original Android Development] squall_kay:
i missed out to include in the steps, but i had done that. infact, i flash UnSu.zip, then Su.2.66.
[Nexus 6P Original Android Development] SymbioticGenius:
The reason I gave you the order that I did is because it would be able to determine which part of the install went wrong. The way you did it, I still have no clue.

At this point, we know that stock works on your phone. We don't know if stock works rooted. We don't know if stock works with Franco rooted. Do it again, flash everything one at a time and after every flash you need to boot. Once it stops booting you know what the problem is.
[Nexus 6P Original Android Development] rebretz000:
Follow these steps by [MENTION=6842057]nathanchance[/MENTION]

It say for pure Nexus but same deal as Chroma. I assume Chroma still has system root built in.

http://xdaforums.com/showpost.php?p=64399854
[Nexus 6P Original Android Development] blueren:
I just tried this with power save profile. Here's the detail

1. Open app, Pam applies.

2. Pull notification shade down (had perfmon notification) Pam reverts to default.

3. Close notification shade, Pam does not reapply

4a. Quit app, check max freq in fku, stuck at power save profiles settings.

4b. Swipe app away from recent, check fku - high performance cluster disappeared lol. Pic attached. Refreshed app to get it back, but max freq still sick at power save profiles settings.

4c. Reopen app, Pam reapplies
[Nexus 6P Original Android Development] eep2378:
Looking good!

Sent from the Nodes of Ranvier
[Nexus 6P Original Android Development] ananbanka:
My phone can't seem to kick into doze after flashing FK. And AndroidOS and Play Services are contributing to major battery drains. Anything I can do to fix this?
[Nexus 6P Original Android Development] franciscofranco:
Ok... I'll try to reproduce.

It has nothing to do with FK, Doze is Kernel agnostic. You have Play Services ****ing your idle battery life, may the Android gods help you.
[Nexus 6P Original Android Development] ananbanka:
Will reflashing stock images, and the r7 kernel help? I don't mind setting the whole phone up fro scratch if I can get half the battery life as others on this thread.

PS. 1. Thank you for FKU, BTW. Helped me reduce the pinkish tint on my screen to a great deal!

2. Also, HBM doesn't seem to work. It gets disabled automatically, and never works using the auto enabler. I'm on r7 and faced this issue on r6 as well.
[Nexus 6P Original Android Development] blueren:
Noticed something else as well. The notification shade Pam happens only once. The second time you repeat, it's ok.

The reverse also happens. Let's say you're in your home screen / any app.

Le wild notification appears (from the app that has Pam set)

When you pull down the notification to glance at it, the app's Pam applies.

Thanks for looking into this!
[Nexus 6P Original Android Development] Arunabh:
That's not going to help.

It'll happen again. Google really needs to start working on this.

It was a problem in jb,kk,lollipop and I really thought they'd have done something about it in marshmallow, but nope. It is what it is!

Memory usage on average is almost 500 mb by Android system and about 300 mb by the os.

This is really stupid.

Only solution is reboot the phone.

I just reboot once when I'm plugging in my phone for a while.
[Nexus 6P Original Android Development] hosmsdos:
I am having issues with double tap to wake. It's enabled with set on boot true all is working fine, but when I restart it will change to disabled with set on boot true. Tried clearing app data same issue.

Thanks
[Nexus 6P Original Android Development] Lightarrow:
I had the same issue. Clearing fku app data and cache fixed the issue for me. Had the app since the start of nexus 6p, problems arose after a few updates.
[Nexus 6P Original Android Development] EarlZ:
Speaking of clearing the FKU app i see it still keeps some values like the vibration, speaker and etc. Would be nice id the button would clear everything and not just prompt the system delete cache and data
[Nexus 6P Original Android Development] Franzie3:
Had the same issue with d2tw not sticking. What i ended up doing was flashing my rom that includes stock kernel. Wiping data/cache on ALL kernel modification apps (FKU, Kernel Aduitor, EX to name a few you could have) and then flash FK and only used FKU to tweak.

Sometimes other kernel apps might hold specific setting data and override FKU, might be best to just have 1 kernel tweaking app
[Nexus 6P Original Android Development] flar2:
It's not the apps' fault. If the app's apply-on-boot service tries to enable dt2w while the screen is off, it will not get enabled. That's why it's hit or miss.

These patches fix the behaviour:

https://github.com/flar2/angler/commit/12cea9ee691f9794d3b0a76c6b381b4bde670bda

https://github.com/flar2/angler/commit/f4286dee51fde5c1082732381c9474c8381b8fb6
[Nexus 6P Original Android Development] franciscofranco:
What? When you clear the app data everything is cleared and all saved values are reset are deleted from the app's preferences.

I'll merge those, thanks!
[Nexus 6P Original Android Development] franciscofranco:
r8 will come sometime this week, I'm merging this to the new anyKernel2 format as I type this - we already nailed the auto-flash from FKUpdater with this format (took us a couple days) :)
[Nexus 6P Original Android Development] nathanchance:
If you don't mind me asking for knowledge purposes (totally okay if you choose not to answer), what had to change with the auto-flashing between a boot.img and a zip file?
[Nexus 6P Original Android Development] franciscofranco:
The idea is the same, although the boot.img I could simply dd it to the boot partition, with this new method we had to create an intelligent script to unpack the current boot.img into ramdisk & Kernel binary and then repackage it all together with an edited ramdisk + new Kernel binary, while maintaining all permissions (permissions in live Android can be a little tricky depending on what directory you're working in) and then flash it to the boot partition. It's a little tricker than what I'm trying to convey, we ([MENTION=4544860]osm0sis[/MENTION] and I) took a couple days to nail this down, a lot of bootloops and broken boot partitions happened :)

Or were you asking for the script code itself?
[Nexus 6P Original Android Development] nathanchance:
Nope, that explanation was exactly what I was looking for, thanks for writing it! :good: Just always trying to increase my knowledge of Android development lol.
[Nexus 6P Original Android Development] wietse1988:
Looking forward to try this, keep up the good work :good:
[Nexus 6P Original Android Development] EarlZ:
No not for me, numerical settings keep the values Ive used before but its apply on boot goes back to off/default.
[Nexus 6P Original Android Development] SchmilK:
I was surprised that it was a bit tougher to get to 6500k than expected.

6000k

R=256

G=254

B=246

Sat=243

Display=245

Contrast=245

Hue=0

6500k

R=241

G=253

B=256

Sat=243

Display=245

Contrast=245

Hue=0
[Nexus 6P Original Android Development] JoKe_42:
About the FKUpdater APP:

Does anyone have a negative impact on the battery by using the "battery service" or the "per app profile service"? I want to use the per app profiles to limit the resources Skype can use. Since this is a giant drainer and heats up the whole phone.

Regards,
[Nexus 6P Original Android Development] franciscofranco:
Of course... clearing the app clears all its preferences, it doesn't restore the actual default values... that would be pretty stupid. If you wanna go back to the defaults clear the app data and reboot. Or just remove the set on boot tick on the values you wanna go back to default and reboot. Simple.

Freakin' amazing. I love the 6500K profile!

Battery service is part of the System Monitor package inside FKUpdater. It doesn't use any battery, it doesn't hold wakelocks during suspend too, so it's fine. Per-App Profiles service same thing. I wouldn't ever ship a service that would **** your battery life.
[Nexus 6P Original Android Development] Franzie3:
nice!!, hope your truck got fixed!!
[Nexus 6P Original Android Development] SchmilK:
Yeah, new fuel rail pump and it's all good.

Now I need to figure out why the block heater isn't working, surprisingly it's started first try at the -6F that it was last night and this morning. (I suspect corroded cable since I had to polish the plug with my dremel to see metal again)

---------- Post added at 11:13 AM ---------- Previous post was at 11:12 AM ----------

Surprisingly enough...so do I!
[Nexus 6P Original Android Development] G-Bus:
I haven't read much about this method however If I'm clear, with this script we'll be able to use the auto flash feature, however we will still need to flash SuperSU afterwards right?
[Nexus 6P Original Android Development] franciscofranco:
You'll just need to flash SuperSu once.
[Nexus 6P Original Android Development] nathanchance:
Nope. The AnyKernel format doesn't overwrite the ramdisk so you will only need to flash SuperSU once, either before or after the first installation. Any updates to Franco Kernel will not require a reflash because the patched status will remain the same. In fact, flashing SuperSU again overwrites the kernel since if it detects that the kernel has already been patched, it restores an unpatched version then patches that. You would need to flash it after ROM/stock Android updates though.

EDIT: ninja'd.
[Nexus 6P Original Android Development] G-Bus:
Thanks for and answers guys. So considering I'm on R7 with SuperSU, when R8 comes out I just "auto-flash" thru FKU and that's it? Or I'll have to reflash SuperSU after R8 and future updates afterwards wont need supersu flash after?
[Nexus 6P Original Android Development] franciscofranco:
When r8 comes out you'll be able to do that yes, and you won't need to reflash SuperSu.
[Nexus 6P Original Android Development] G-Bus:
Alright great thanks for the hard work once again!
[Nexus 6P Original Android Development] Asselalf:
Thank you [MENTION=3292224]franciscofranco[/MENTION]

Gesendet von meinem Nexus 6P mit Tapatalk
[Nexus 6P Original Android Development] arunkr:
Can u provide the values to enter in kernel aduitor?..because the value given for saturation is not possible to attain with that app.
[Nexus 6P Original Android Development] EarlZ:
Sorry if it was a simple question, it was my understanding that clearing an app data puts all userdefined values to stock.
[Nexus 6P Original Android Development] wietse1988:
Can't wait to see r8. Currently on pure nexus, should I wait? Or do you guys recommend to all ready go for r7 with system less root?
[Nexus 6P Original Android Development] JoKe_42:
Why wait? It doesn't take more than 5 minutes to flash r7 (including reboot) and you can already explore it and benefit from it.

Regards,
[Nexus 6P Original Android Development] arunkr:
wait it out, it will get released in 1 or 2 days hopefully..:D..
[Nexus 6P Original Android Development] bisco:
[MENTION=3292224]franciscofranco[/MENTION] first of all thank you for the amazing kernel and also for the app naptime!

my question is: can i trigger aggressive doze vom your app with tasker? what code do i have to run to toggle in on and off?

hope you can help me out, thanks!
[Nexus 6P Original Android Development] inffy:
or maybe just buy the damn app
[Nexus 6P Original Android Development] arunkr:
as if i donno that, read the question dude...:rolleyes:
[Nexus 6P Original Android Development] SchmilK:
Sorry I can't. If the numbers aren't the same, then kernel auditor isn't obeying the values created by Franco. I would suggest supporting Franco and get FKU.
[Nexus 6P Original Android Development] arunkr:
Thanks man..will do
[Nexus 6P Original Android Development] xadidas4lifex:
How?
[Nexus 6P Original Android Development] Asselalf:
Ask franciscofranco...

Gesendet von meinem Nexus 6P mit Tapatalk
[Nexus 6P Original Android Development] __NBH__:
I'm trying to edit my screen colour values and if I pick 241,253,255 and exit fku then go back in it changes the figures to 242,254,255 like it doesn't do odd numbers apart from the 255 max.
[Nexus 6P Original Android Development] TheDarkAngel666:
put simply 250,252,255 and you get 251,253,255
[Nexus 6P Original Android Development] franciscofranco:
I don't have an intent for that, but I can create one.

Are you using the latest 14.0.3?
[Nexus 6P Original Android Development] bisco:
If you could do that.. Well that would be f**** awesome!

Sent using XDA One
[Nexus 6P Original Android Development] __NBH__:
Yes latest version. Putting the numbers one more as suggested actually works.
[Nexus 6P Original Android Development] xadidas4lifex:
That battery life was beautiful.

I havent seen anything close to that on franco...

Any settings or tweaks you applied?
[Nexus 6P Original Android Development] resynx:
I'm using 14.0.3 and it happens to me too. Always goes up by 1 number so I just set it 1 number below and let it go up haha. I could grab a log if you'd like?
[Nexus 6P Original Android Development] eep2378:
Same here using the latest FKU. [MENTION=674332]SchmilK[/MENTION], 6500k, FTW!

Sent from the Nodes of Ranvier
[Nexus 6P Original Android Development] Asselalf:
Not much. Using Greenify and disabled the Kernel Wakelocks in FKU. Display brightness is at 30 - 35% with the 6500K profile from [MENTION=674332]SchmilK[/MENTION]. Location service is off. Pro tip: uninstall the crap apps like facebook and so on

Gesendet von meinem Nexus 6P mit Tapatalk
[Nexus 6P Original Android Development] gqukyo:
I get the +1 increase also
[Nexus 6P Original Android Development] resynx:
2nd day using r7 and I have 2:40 SOT at 51%, and that's while I'm out and about. The battery should be even better the second half while I'm home! :) This battery life is phenomenal.
[Nexus 6P Original Android Development] franciscofranco:
I'll check my code on that +1 increase on the RGB section. Thanks & sorry.
[Nexus 6P Original Android Development] franciscofranco:
Yeah fixed :)
[Nexus 6P Original Android Development] franciscofranco:
I believe I fixed the bug reported about Per-app profiles. I did exactly as reported and I can't reproduce it anymore.
[Nexus 6P Original Android Development] resynx:
Wasn't me who reported anything about per-app, I only reported on the rgb -1 bug xD But whoever did is going to be very happy :D haha
[Nexus 6P Original Android Development] blueren:
It was me who reported the PAM issue :) Happy to know you fixed it!

On a secondary note, were you able to reproduce the HBM .. dimmness?

Scenario: Turn on auto HBM, set arbitrary value (Eg. 3500). Use phone normally. Occasionally when you whip your phone out of your pocket and unlock it, it takes 2-3 seconds for the display to amp up to the right brightness scale. Until then, the display brightness will be at minimum. Turning off the atuo HBM solves this.
[Nexus 6P Original Android Development] jackie_jagger:
I have 2 quick questions, yes I read the last ~10 -12 pages but I am still a *little* confused about this:

1. I only got around to flashing r7 about last week and the January security update yesterday. Today at the gym - with my Bluetooth earbuds connected (I also have an Android Wear watch that was connected to the phone as well at the same time). I noticed that my phone got really warm and battery was draining like crazy. I checked BBS and saw that bluesleep and Google Play Music didn't let the phone - at all, even with the screen off. Is this expected behaviour or do I need to tweak something in the app. This was with stock settings.

2. I also noticed in Android Battery status that "Android OS" kept the device awake for about the same time - which I'm assuming is the same as #1? (confused about this because Bluetooth was a different entry).

Thanks guys.
[Nexus 6P Original Android Development] xadidas4lifex:
kinda having the same issue, but i have tried all your steps even from the chroma thread. just cant get android pay to work
[Nexus 6P Original Android Development] franciscofranco:
I managed to reproduce the issue :)

How interesting, the ambient light sensor keeps working with the display off.

Anyhow, it's fixed!
[Nexus 6P Original Android Development] franciscofranco:
1 - Welcome to Android - the age of the wakelocks. Nothing we can do about it and as seen previously, disabling Blueesleep wakelock will panic the Kernel;

2 - Android OS entry is always confusing, even I have some issues trying to figure out what exactly it means. I'll wage that it's related to #1.

Android Pay works fine as long as /system is untouched, that's all you need to know. If you changed /system through any way, you gotta undo it.
[Nexus 6P Original Android Development] nathanchance:
Unfortunately it seems like Google has tightened SafetyNet restrictions. I have been told in a few different threads that they can't activate Android Pay. Some root apps break it even though they didn't before.

And what Franco said.
[Nexus 6P Original Android Development] blueren:
Liek a baus. Another bugga squshied!
[Nexus 6P Original Android Development] xadidas4lifex:
thanks for the quick response. idk if you remember me from the n5, n10 forum and other threads, but i appreciate your work alot.

i think the only changes I made was changing my dpi and deleting audio_conf so V4A would work.

do you know the default dpi? i think its 560

and should i put the audio_conf file back?
[Nexus 6P Original Android Development] nathanchance:
Oh you changed DPI? That 100% breaks it. Yes default is 560 I believe. There are Android Pay compatible V4A, there is a link in my signature with a guide by [MENTION=5244502]micmars[/MENTION] that has some info on it.
[Nexus 6P Original Android Development] xadidas4lifex:
yea i tried changing it to 560 initially, and it didnt work. i just asked to confirm thats the dpi.

i will try the v4a in your link
[Nexus 6P Original Android Development] jackie_jagger:
Whelp ! I did have a kernel panic causing a soft reboot this morning with Blueesleep disabled. So I reverted back to stock.

But yes, I know what you mean. Thanks for the quick reply.

also, this may sound absolutely stupid but does double tap to wake drain battery? I know in Nexus 5 the digitizer was tied to the screen causing battery drain but I'm not sure if N6P is any different.
[Nexus 6P Original Android Development] nathanchance:
Nope, wake gestures do not drain battery on the 6 or the 6P.
[Nexus 6P Original Android Development] jackie_jagger:
Thank you sir.
[Nexus 6P Original Android Development] Devhux:
Soft reboot isn't a kernel panic.... That's a framework issue usually (Xposed module or something quite possibly)
[Nexus 6P Original Android Development] jackie_jagger:
Really eh? TIL.

No xposed here, I'm running fully stock with just root and franco. Wonder what that was about. Either way the battery seems to have stabilized now, not sure what that was. Guess just one of those days on Android.
[Nexus 6P Original Android Development] GeneralRam:
I seem to be noticing quite a few lags/freezes on my phone recently after installing R7 (Or at least I think it's due to R7). I'm going to put R3 back on, see if that solves it and I'll report back.

I'm running the latest stock image and Franco - I haven't bothered with anything else.
[Nexus 6P Original Android Development] Devhux:
I may have misunderstood Franco when he mentioned it to me (I thought the kernel was panicking when the phone did a soft reboot).
[Nexus 6P Original Android Development] eluspo:
You meant we can now update our phone via ota even if we are rooted and have fk?
[Nexus 6P Original Android Development] heleos:
OTA's from custom roms, not from Google
[Nexus 6P Original Android Development] resynx:
Had a reboot in my pocket this morning. Running Cataclysm and r7.

console-ramoops: http://pastiebin.com/56a1224b10af4

pmsg-ramoops-0: http://pastiebin.com/56a122993565e
[Nexus 6P Original Android Development] franciscofranco:
The log is incomplete, sorry.
[Nexus 6P Original Android Development] resynx:
Thanks for looking into it. Is it incomplete because I missed something or are incomplete logs generated sometimes?
[Nexus 6P Original Android Development] jackie_jagger:
I'm facing the same, r3 was pretty stable for me in terms of performance and battery. I'll try the same as well.

Android OS kept my device up for long periods of time and used CPU. I was down to 60% of battery with a mere 42mins of SOT. I can't seem to nail the root cause of this, any help or pointers will be appreciated.
[Nexus 6P Original Android Development] Franzie3:
try using betterbattery stats or wakelock detector to narrow the the specific cause.
[Nexus 6P Original Android Development] jackie_jagger:
BBS was showing PowerManagerService wakelock - how do I narrow it down from there? The BBS wiki said to look at partial wakelocks to narrow down what that caused it. I'll monitor it and see what pops up, since I restarted it a while ago and lost the data.
[Nexus 6P Original Android Development] guta12:
I hope New build of this kernel
[Nexus 6P Original Android Development] Franzie3:
That's the device turning on out even active display. I turned that off. Check alarms and partial wakelocks. Also download wakelock detector

Patience. Good things come to those who wait... AND are patient
[Nexus 6P Original Android Development] jackie_jagger:
How do you turn that off? I assume I check for the alarms and partial wakelocks through wakelock detector right? Installed it and will monitor