yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Original Android Development] franciscofranco:
r15 is up, but only for Marshmallow. I'll push a new N build when the next N OTA release is up since it'll most likely have a lot of Kernel changes.

Also check this out if you're a FKUpdater user: https://plus.google.com/u/0/+FranciscoFranco1990/posts/WGBDtjUAHLL

Enjoy!
[Nexus 6P Original Android Development] ironjon:
Are the April security patches included?

Google just released minutes ago

Enviado desde mi Nexus 6P mediante Tapatalk
[Nexus 6P Original Android Development] franciscofranco:
The source wasnt updated so I couldnt include any Kernel patches they might've added. I'll update this if there are new things.
[Nexus 6P Original Android Development] blsrbl:
I noticed that the bluedroid wakelock is enabled by default on this release.
[Nexus 6P Original Android Development] edved:
I've rooted and I still get the "unfortunately, FKUpdater has stopped" error message. That's with the paid version, while the free version will install but once you activate the download, the download doesn't stop and obviously doesn't install. I did manage to instlall the zip with TWRP and is so far working well.
[Nexus 6P Original Android Development] franciscofranco:
Uh? It's been always enabled.
[Nexus 6P Original Android Development] franciscofranco:
A little more info would go a great way. What app version? What triggers the FC? My tests didn't trigger anything.
[Nexus 6P Original Android Development] franciscofranco:
Fix it yourself, it's your phone, and it's most likely one of your apps doing that.
[Nexus 6P Original Android Development] porter11:
https://goo.gl/photos/bS2kFsrwJwR6vfhaA
[Nexus 6P Original Android Development] kiefferbp:
I think any developer worth his salt knows what a FC looks like. Do you have any more information that you can provide?
[Nexus 6P Original Android Development] franciscofranco:
That doesn't help anything... what FKUpdater version are you using?
[Nexus 6P Original Android Development] edved:
It's me! At least that's what I suspect anyway. Full format and will re-install. I'm thinking this should fix it!

Cheers.
[Nexus 6P Original Android Development] franciscofranco:
I just confirmed r15 has all the Kernel security patches present on April's security OTA.
[Nexus 6P Original Android Development] Ad.Shk2:
Located this post through search. So, i don't seem to be able to find the color profile folder for Franco. Furthermore, there are only 5 color profiles built into the fku, any others that can be added?
[Nexus 6P Original Android Development] kingmikel:
I too was running into this. I could not install it without it causing an FC. I was enrolled for the beta version, so I un enrolled, installed the stable version and it works fine. I hope that helps
[Nexus 6P Original Android Development] Vekhez:
I'm getting a force close too, on the April Security Level, rooted with stock kernel. FKU version 14.2b, first time I've tried to use the app on this install (did a clean install with factory image to April this morning). Granted the app storage permissions, wiped cache and data and forced closed didn't work. Tried a reinstall and that didn't work. Not sure what else to do? Force closes on launch, don't even get to the "splash screen" just force closes straight back to home screen virtually instantaneously.
[Nexus 6P Original Android Development] DaveHTC200:
I think the man would need logs to see what's happening ?
[Nexus 6P Original Android Development] noobhero:
no issue for me.

fastboot flash system and vendor images

reboot bootloader

fastboot flash twrp again to cover my (Y)

reboot into recovery

r12 was already on my device, so i just flashed it.

flash supersu

flash xposed

reboot ............

launch fkupdater and auto flash update.

to the guys hving fcs. try removing root permission and grant them again?

just a wild shot
[Nexus 6P Original Android Development] pyro2677:
hahaha that's an awesome reply...
[Nexus 6P Original Android Development] Vekhez:
I'm not around my computer for the next few days or so, so I'm not really much use for that but I can test to see if the app is working again if there is a Play Store update or APK.

Well here's what I did.

fastboot update -w image-angler-mhc19q.zip
fastboot flash recovery twrp-3.0.1-0-angler.img
adb sideload RC-SuperSU-v2.70-20160314191951.zip

Then rebooted, downloaded FKU and tried to open and force close. I have the cleanest install you can get, so I am pretty sure that it's not a problem with that (and I did a complete wipe and flash again, and had the same problem just to make sure). So I'm pretty confident it's nothing on my end. FKU closes before there is a chance to grant it root permissions, but if I go into SuperSU Pro and change the default access to "grant" it doesn't make a difference.
[Nexus 6P Original Android Development] lillypad_33:
Pretty stoked to be on a Franco kernel again.

Used to be on it with my galaxy nexus....and now within a day of getting my Nexus 6p I couldn't contain myself.

The reason I decided to switch is that everybody kept on going on about how great the battery life was on stock. I didn't see too much evidence that this was actually true, so I decided to flash Franco and see if things will go as well as they did with the Galaxy Nexus.

Nothing of note so far other than to say that is it possible to feel even smoother than the stock ROM already was? **** flies off the screen!
[Nexus 6P Original Android Development] Fauert:
No issues here !
[Nexus 6P Original Android Development] Gytole:
I always fastboot erase boot, flash boot, then flash anyzip in twrp
[Nexus 6P Original Android Development] arhung:
Camera not working with r15 and MHC19Q anyone get same issue？
[Nexus 6P Original Android Development] franciscofranco:
You're drunk, go home.
[Nexus 6P Original Android Development] crowsnestitsupport:
No issues here.. Using April 5th build of benzo with April patches and Franco r15. Took many photos today with no issues:)
[Nexus 6P Original Android Development] anmar21:
Same issue here. FKU (paid) crashes at launch. Stock rom and stock kernel but xposed and rooted (obviously).

FC report sent through the app.
[Nexus 6P Original Android Development] inimaitimepass:
Manually flashed r15, but the about phone section shows kernel version as #14, mar 19 build!

Tried downloading and flashing from 2 different machines but still it is like that. Is it like this for all?
[Nexus 6P Original Android Development] crowsnestitsupport:
Nope.. All good here. I downloaded from link on this page and flashed in twrp.
[Nexus 6P Original Android Development] Bwyan Benton:
Camera works perfect here with r15 and stock April security update. Also I have xposed V81, a bunch of my own tweaks and phone is sleeping like a baby. Haven't tried a different kernel in over a month now. No need, phone is doing exactly what I want/need it to.

Thanks Franco!
[Nexus 6P Original Android Development] franciscofranco:
You're probably flashing the wrong zip or something.
[Nexus 6P Original Android Development] Bwyan Benton:
Nope. Mine is as it should be
[Nexus 6P Original Android Development] inimaitimepass:
These are the contents of the folder! :rolleyes:

I'll try downloading again tomorrow.
[Nexus 6P Original Android Development] mannyalba:
You can never uninstall xposed bro, xposed is cancer, only way you'll solve this issue is clean flashing without the cancer, i assure you it will work again.
[Nexus 6P Original Android Development] kiefferbp:
I had the same issue (with similar logs) on my Nexus 5 after the April update, but not on my 6P. I un-installed the FKUpdater app on my Nexus 5 and re-installed it and it fixed the issue. I didn't bring it up originally since it appears to be Xposed related.

Also, just because you "un-installed" Xposed doesn't mean that traces aren't still there.
[Nexus 6P Original Android Development] edved:
I guess it's not me! I have reformatted and a fresh install and I'm still getting the same error message, while inexplicably the free app appears to be working.
[Nexus 6P Original Android Development] ZachPatterson:
True, I should have specified that I flashed the uninstaller.zip in the Xposed thread.

But I've never had an app crash with Xposed that wasn't module related in someway.

I just did a clean install this past Sunday too >_>
[Nexus 6P Original Android Development] franciscofranco:
Guys chill out, I'm pushing a new beta release, the FC was my own doing, by mistake. That's what betas are for ;)
[Nexus 6P Original Android Development] arrrgh:
I'm guessing you are flashing SuperSU after kernel? That would make SuperSU flash the backup kernel which would be the previous r14.

If you had root before, just flash r15 and skip flashing SuperSU.
[Nexus 6P Original Android Development] mystertom101:
That was cold???
[Nexus 6P Original Android Development] hinxnz:
Yes you can but you need to wipe dalvik-cache.

Most people don't realize that xposed can be temporarily disabled on boot, the normal way isn't working with 6p but you can just enter a terminal command in twrp or in os/adb.

touch /data/data/de.robv.android.xposed.installer/conf/disabled

Then delete it to enable xposed on boot or you can just rename it to 'enable'.

rm /data/data/de.robv.android.xposed.installer/conf/disabled
[Nexus 6P Original Android Development] marbertshere:
Pretty sure you can uninstall it with the xposed_uninstaller zip found in the xposed thread. I understand there are people that aren't fans, but I've never had problems with it.
[Nexus 6P Original Android Development] franciscofranco:
Users that were having that FC on FKUpdater 14.2b, have you updated to the newest build and see if the issue is fixed?
[Nexus 6P Original Android Development] Ad.Shk2:
Bump.... :)
[Nexus 6P Original Android Development] Vekhez:
Yes, it's fully working now, thanks!
[Nexus 6P Original Android Development] franciscofranco:
Just paste me the profiles you want added.
[Nexus 6P Original Android Development] Ad.Shk2:
I found some in the ex kernel folder. I'll upload them and link here.
[Nexus 6P Original Android Development] G-Bus:
Woke up this morning and phone rebooted itself again on r15.

Sent from my Nexus 6P
[Nexus 6P Original Android Development] motoridersd:
Has anyone noticed issues with people not hearing you properly on phone calls if the phone is slightly off angle? I haven't had issues since I got the phone when it came out, but lately I have had way too many people tell me they can't hear me. Did r15 change anything with noise cancellation or microphone gains?

Using Speakerphone or bluetooth I have no issues, as I would expect.
[Nexus 6P Original Android Development] Ad.Shk2:
Here you go

https://drive.google.com/folderview?id=0B-YehMCBHI-nNUFzamMwMFB0dFk
[Nexus 6P Original Android Development] franciscofranco:
I don't know. I can't reproduce. I need to see /sys/fs/pstore/console-ramoops

What is your setup? Rom? Xposed? etc

Nope, 100% stock.
[Nexus 6P Original Android Development] Prattham:
The only kernel i ever flashed on my N5

Again and again i just keep flashing it back on my N6p [MENTION=3292224]franciscofranco[/MENTION] do you know i love you? :D:p
[Nexus 6P Original Android Development] motoridersd:
Thanks Franco. Maybe my beard is too long now :D
[Nexus 6P Original Android Development] franciscofranco:
Nevertheless you should flash stock boot.img, make a couple calls, and see if other people still complain, then flash back r15 and test again.
[Nexus 6P Original Android Development] Lartza:
I've had reboots on r14 and r15 with CM13+Xposed too. I've only noticed it happen once every couple days or even less often so far. I'll need to get some concrete details on this when I have more time. I can't remember it ever happening a couple weeks or so ago, running obviously older CM13 nightly(+Xposed) and fk pre r14.
[Nexus 6P Original Android Development] franciscofranco:
That's like a time-bomb, ready to blow anytime. Without /sys/fs/pstore/console-ramoops I can't even see if that's my fault or not, though I doubt it - my N6P is the development device and I have 0 reboots ever running stock rom without any xposed ****.
[Nexus 6P Original Android Development] Lartza:
Attached is my console-ramoops. And this is on CM 20160405 with Xposed v81.
[Nexus 6P Original Android Development] franciscofranco:
[ 0.000000] Linux version 3.10.73-gcf36678 (android-build@kpfj7.cbf.corp.google.com) (gcc version 4.9.x-google 20140827 (prerelease) (GCC) ) #1 SMP PREEMPT Thu Oct 8 05:46:28 UTC 2015

That's probably the log from the recovery. The ramoops log only shows up after you boot up after the crash. If you reboot again or boot into recovery in between, you're goners.
[Nexus 6P Original Android Development] Lartza:
I didn't reboot though... And when I rebooted now and checked ramoops it's completely different https://gist.github.com/Lartza/19568e92ccd705ac7e7648b52c4296d8

I'll keep an eye out for future reboots.
[Nexus 6P Original Android Development] G-Bus:
Chroma + r15. Tried stock boot.img and it didn't do it. I wake up in the morning and it asks me to input pattern again because phone rebooted itself. It started doing it with r14. I'll try to get a log. What do I need to open the file?

Sent from my Nexus 6P
[Nexus 6P Original Android Development] .psd:
On one hand I'm hoping people with non-stock setups will stop harassing Franco, because he's stated so many times that he doesn't support anything other than a completely stock setup. I would have exploded by now if I were him, and yet he still finds time to reply to people who use xposed or third party ROMs.

On the other hand I hope people with non-stock setups keep harassing him, so he'll eventually realize his userbase is literally people who DON'T WANT to be stock. If they wanted to be stock then they wouldn't be here at XDA, flashing hacks like custom kernels and stuff.
[Nexus 6P Original Android Development] G-Bus:
I get what you're saying and I feel bad. However if I was going to run stock, like you said, I wouldn't be on XDA.

Stock + Xposed was an option for me until franco said he hates Xposed so I stopped using that and I use closest to stock roms that gives me the little options GravityBox did.
[Nexus 6P Original Android Development] franciscofranco:
Well... I can't be hating on users that use my stuff, that would be rude. It's true that I prefer stock phones (just rooted and FK), but I guess everyone has the liberty to use whatever they want, but they must be aware of the consequences. FK is ramdisk agnostic right now so it'll work on all roms.
[Nexus 6P Original Android Development] :
To those with cm13+xposed random reboobs - no more lube.
[Nexus 6P Original Android Development] Degenerator9000:
Is there something other than gravitybox in xposed that will let me enable an immersive mode that doesn't break my keyboard (ie requiring me to un-hide the navigation bar every time I wanna type)?

I haven't had any issues with it yet but seeing how many devs just don't wanna **** with xposed kind of makes me wanna find a workaround

Fku updated my mhc19q w/O issues btw
[Nexus 6P Original Android Development] dwang:
Try the swipe navigation app
[Nexus 6P Original Android Development] droid_1989:
Can someone help me with the Ghost Pepper script, where should it be moved to, can someone link me it?
[Nexus 6P Original Android Development] .psd:
Can confirm dwang's solution.

1. Add "qemu.hw.mainkeys = 1" to the end of your build prop. This perma-hids the Nav Bar.

2. Install Swipe Navigation. This will make it so you navigate by swiping where the Nav Bar used to be. It's totally invisible and utterly intuitive, you literally just swipe up from the edge, no buttons, no timing to trigger something, no worrying about how far or fast you swiped...it just works.

You will need root and I THINK you have to buy the unlock code for like $1.50, but it is by far the most sophisticated, elegant, intuitive solution to gain real estate. I've been asking someone to develop this app for years so I'm a strong advocate for it, if you haven't noticed :p
[Nexus 6P Original Android Development] Juzman:
PureNexus running fine with r15. I wouldn't even use Xposed if there was alternatives to:

MinMinGuard

YouTube Adaway

XInsta

XGPM
[Nexus 6P Original Android Development] JazzMozz:
Maybe a long shot, but would it be possible to have the DT2W only execute when the proximity sensor is set on far? The reason is that I carry my phone in the pocket of my trousers, screen facing my leg (to protect the screen from impacts). The fabric of my pockets however is so thin that the skin of my leg very often activates the DT2W. This not only causes unnecessary battery drain but also has the risk of butt dialing and things like that.
[Nexus 6P Original Android Development] Asselalf:
Flash the Boot.img from your ROM
[Nexus 6P Original Android Development] franciscofranco:
Yes, if you're using FKUpdater inside CPU Manager -> CPU-boost there's an option called input_boost_enabled. If you're not using my app you can do it through adb, echo 0 > /sys/module/cpu_boost/parameters/input_boost_enabled

About the governor question, HELL NO.

That's only possible through an app.
[Nexus 6P Original Android Development] Degenerator9000:
I got used to gravityboxes version of pie controls instead but I'll give this a shot with something like lmt

I did the build prop editing but GB immersive appears to add it's own navigation bar on swipe from bottom
[Nexus 6P Original Android Development] :
If you like pie, and can do without immersive navbar, LMT is an option too.
[Nexus 6P Original Android Development] DaveHTC200:
Swipe navigation is am awesome app, only found it last night [emoji2]
[Nexus 6P Original Android Development] Degenerator9000:
I had GMD gestures and LMT installed already from before but I think I like the LMT pie controls more

A lot of other pie apps have a slight delay after you press a button which kinda kills them for me
[Nexus 6P Original Android Development] binaryfalcon:
High power cluster settings have dissapeared from the FKupdater app for me, what's up with that?

edit: assigning values is not possible in ex kernel manager either
[Nexus 6P Original Android Development] kiefferbp:
The answer hasn't changed from the billion other times this was asked: you're being thermal throttled.
[Nexus 6P Original Android Development] binaryfalcon:
the search feature in this thread would suggest otherwise.

either way, when the temp is at 25°C what you are saying doesn't make sense
[Nexus 6P Original Android Development] franciscofranco:
Yeah you were thermal throttled. Where are you seeing that temperature from? That looks like battery temperature and not CPU.
[Nexus 6P Original Android Development] binaryfalcon:
apologies, that wasn't the cpu temp

edit: turned off the phone for a while and back to normal now - got worried since it was like that all day
[Nexus 6P Original Android Development] franciscofranco:
Worried that the big cluster packed its bags and left your phone to go on a trip around the world? Seems legit :)
[Nexus 6P Original Android Development] DaveHTC200:
And why shouldn't it be allowed a little break ?
[Nexus 6P Original Android Development] binaryfalcon:
seeing as your app requested supersu every second and I wasn't aware of that the throttling removed the cluster from the settings during that time, totally legit ;)
[Nexus 6P Original Android Development] franciscofranco:
Requested su every second? Wat [emoji52]
[Nexus 6P Original Android Development] binaryfalcon:
kept going for several minutes
[Nexus 6P Original Android Development] YudmudTR:
I don't have this problem.
[Nexus 6P Original Android Development] blsrbl:
I wake up in the morning and my phone asked for a pin code which means the phone rebooted itself during night. I'm on latest chroma + r15 with no xposed. It happened like 6 hrs ago but i didn't reboot my phone after. Can i still provide the right log files?
[Nexus 6P Original Android Development] franciscofranco:
Uh I have no clue. Maybe high brightness mode? Per app profiles?
[Nexus 6P Original Android Development] franciscofranco:
/sys/fs/pstore/console-ramoops
[Nexus 6P Original Android Development] noobhero:
probably high on dope, it's weekend, why not?! ;)
[Nexus 6P Original Android Development] franciscofranco:
You win!
[Nexus 6P Original Android Development] treIII:
Does Naptime disable WiFi while activated? Also, does Naptime engage while phone is in motion? I'm concerned with my wifi calling with T-Mobile working if I use Naptime. Really wanting to give it a try though. Thanks to those who may respond
[Nexus 6P Original Android Development] Soundtallica:
Managed almost 6 hours of SOT on r15 with the March update. Nice job on the efficiency with r15, it's the best I've seen out of this kernel yet!

However, I'm getting the issue where if I charge overnight, sometimes the battery isn't fully charged and is anywhere in the 90%-100% range when I wake up... a minor inconvenience to live with though.
[Nexus 6P Original Android Development] franciscofranco:
Naptime doesn't disable Wi-Fi per-se, but it cuts internet connection during screen off (because it forces Doze right off the bat). Best way is for you to install Naptime and ask someone to initiate an Wi-Fi call about 1-2 minutes after you screen off, then you'll know.

Awesome!

Well, battery drivers are 100% stock. Are you charging with the stock charger + cable?
[Nexus 6P Original Android Development] dephsone:
I love trying kernels but DAMN!

Always come back here.

This kernel is one be(a)st things for the 6P!

Great job dev!

❤Nexus6P❤
[Nexus 6P Original Android Development] Juzman:
Just bought fku [MENTION=3292224]franciscofranco[/MENTION] :) keep up the good work!
[Nexus 6P Original Android Development] franciscofranco:
Thanks, enjoy!
[Nexus 6P Original Android Development] arunkr:
[MENTION=3292224]franciscofranco[/MENTION]: Hi dude, this may be a one off case for u(but I have seen some users experiencing the same), this is not a problem with ur kernel or anything, just need some help fixing an issue that has been bugging my device for some time now. This started during the march update, the problem is fingerprint scanner sometimes takes 1 sec or more to register my finger. The problem is that, this is mostly random(majorly this happens after keeping the phone idle for some seconds(15-20), but sometimes it has the problem even before that(5 seconds)). Please note that the fingerprint authentication is 100% accurate. the only issue is waking up/ scanning. I tried putting the kernel in performance governor, the problem goes away when I do that. While charging also its blazing fast. That gave me an impression that it can be solved by playing around with the CPU governor settings, so I thought ill try my luck asking u for some kind of diagnosis.:). I understand that since u don't have the problem which I'm facing, it will be difficult for u to test it out, but it would be really helpful if u can lemme know what all parameters determine the speed of the scanning(the scanner is not working for that 1sec+, while its working its really quick). I'm running clean install of latest purenexus and r15 without greenify,naptime,xposed or any of that sort of apps. I have tried almost everything under my knowledge to fix this, still having problem. the only thing left is going completely stock + locking the bootloader. Pls help, :(
[Nexus 6P Original Android Development] Degenerator9000:
Incredibly weird that it goes away when the governor is set to performance, I wouldn't have thought the scanner was that cpu-intensive

Do you have this issue with FK and the stock rom?
[Nexus 6P Original Android Development] arunkr:
I think its because the CPU is not getting ramped up or scaling up from idle and not coz its cpu intensive(as u said even I think its not gonna be cpu intensive). Ya I had that issue with stock + franco. It used to be so fast...pls note this happens randomly..
[Nexus 6P Original Android Development] Reuben_skelz92:
R15 is running great. Good battery life. Snappy and smooth. Previous builds I haven't Franco to be as smooth as others. But now its as good if not smoother than all the other kernels. Used it on aosip 4.1 for a while and now on DU latest weekly. Thanks