yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Original Android Development] swallowingled:
Option 2 sounds good. But is there a way in FKU to give the option when auto flashing (which reboots system), to give an option to reboot straight to recovery to manually reflash whatever SU we have? No big deal if not. Choosing the download zip and then rebooting to recovery(using Simple Reboot of course) and flashing FK then SU works just as well.
[Nexus 6P Original Android Development] THATTON:
If people would read, I would say option 1 but since they don't... Option 2.
[Nexus 6P Original Android Development] nexusmaniac:
Option 2 for me :)
[Nexus 6P Original Android Development] rp1226:
2
[Nexus 6P Original Android Development] Empty Hand:
Option 2 to avoid the pages of posts about issues from people who don't read.
[Nexus 6P Original Android Development] M1LL3R:
I don't know if its already reported or its only for me but when I try to change the saturation values it don't change anything... Any one in the same boat?

Option 2 for me.
[Nexus 6P Original Android Development] :
I say two too ?

Sent from San Antonio Tx- Nexus 6p
[Nexus 6P Original Android Development] Didgeridoohan:
Option 2.

And until another solution comes along, you should probably remove the auto flash from FKUpdater. Adding a button to restart to recovery would probably also be appreciated by some...
[Nexus 6P Original Android Development] troymz1:
Option 2. Avoid headaches for yourself.
[Nexus 6P Original Android Development] Grassinator:
FranCO

Franco My Bro... SOOOOO Glad ur back my man! Hope all is well and wish you and yours the Merriest Christmas and Happy New Year sir. Thank you for being you!

:cool:
[Nexus 6P Original Android Development] Subiegsr:
Awesome, thanks for explaining this. I was wondering if I would always be stuck with running supersu 2.61 to just use android pay. Going to try this tonight!
[Nexus 6P Original Android Development] crash822:
Option 2. I like being able to able to still use SU 2.61 and keep android pay.

For those on higher SU versions, is there a reason I should use a newer version if super user is already working great for me?
[Nexus 6P Original Android Development] Dr_Ownage:
I vote option 2 as well.
[Nexus 6P Original Android Development] handols:
Voting for something that I can flash to and not bootloop
[Nexus 6P Original Android Development] badboy47:
Option 2!
[Nexus 6P Original Android Development] franciscofranco:
Ok guys, r5's coming up without this SuperSu thing. Thanks for the feedback, immensely appreciated.
[Nexus 6P Original Android Development] Bxrider117:
Great. I'll wait for it to come out instead of flashing r4.
[Nexus 6P Original Android Development] tehpud:
Option 2 is my vote.

Lost my download of SU 2.65 and the zip on the SU thread is giving me a bad zip file that is empty. Anyone else have this?
[Nexus 6P Original Android Development] xluco:
loving r4 franco!

I'm trying to build r4 myself just for fun but I can't get it to boot, it just gets to the Google logo then back to TWRP, anybody got any ideas?

Simply put I'm pretty much doing the following:

make angler_defconfig
make -j4
./mkbootfs ../ramdisk | gzip -9 > ramdisk.cpio.gz
./mkbootimg --kernel Image.gz-dtb --ramdisk ramdisk.cpio.gz --ramdisk_offset 0x02000000 --tags_offset 0x01E00000 --cmdline 'androidboot.hardware=angler androidboot.console=ttyHSL0 msm_rtb.filter=0x37 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 boot_cpus=0-3' --pagesize 4096 -o boot.img

Am I missing something? I've noticed that the boot.img is about 2mb smaller than francos, I get no errors when building but did notice it say "nothing to be done for 'dtbs'" :crying:
[Nexus 6P Original Android Development] mgear356:
[MENTION=3292224]franciscofranco[/MENTION] for info Pls.. Still getting hangs in r4
[Nexus 6P Original Android Development] franciscofranco:
I'll keep searching, but so far I haven't been able to reproduce this anymore, I played Marvel Future Fight for 5hrs, then another day left it running for the entire night, then uninstalled and installed it again and still no hang during start up. Also tried other games and I was not able to reproduce it anymore.

What rom are you on?
[Nexus 6P Original Android Development] franciscofranco:
r5 is up, grab it. Don't forget to flash SuperSu afterwards. I'll probably add a "Flash SuperSu afterwards on FKUpdater sooner than later".

Also check the screenshot below on Geekbench after merging an upstream patch for our task scheduler. Stock scores multi-core around ~4300. Shouldn't result in any battery hit. Read the commits messages to learn more.
[Nexus 6P Original Android Development] tehpud:
Thanks Franco!

Community: Struggling to find a working version for SU 2.65. The thread zip is showing as a bad zip. Anyone get the same issue?
[Nexus 6P Original Android Development] franciscofranco:
Just use this: http://xdaforums.com/showthread.php?t=2073775. I use his unpack/repack scripts, saves me a lot of time.
[Nexus 6P Original Android Development] x.Orville.x:
Looking for the same
[Nexus 6P Original Android Development] swallowingled:
I had the same issue earlier. TWRP said the file was corrupt. I downloaded a second time using Chrome on my 6P and that download worked fine.
[Nexus 6P Original Android Development] azsl1326:
Every time I tried to flash SU 2.65, TWRP stated it was a bad zip. Haven't found a working one yet.
[Nexus 6P Original Android Development] mgear356:
I am on chroma 10/12 bro.The hangs seemed to be lesser but still exist.. Hmm eleemntalx lean have no issue on the same rom..
[Nexus 6P Original Android Development] franciscofranco:
[No message]
[Nexus 6P Original Android Development] franciscofranco:
OK, try something for me, set high cluster min cpu freq to 633MHz (that's stock's min freq for the big cluster) and let me know if that changed anything. Thanks.
[Nexus 6P Original Android Development] Ulver:
I agree, option 2 is the way to go
[Nexus 6P Original Android Development] franciscofranco:
Already done on r5. Go get it.
[Nexus 6P Original Android Development] pahlerc1:
All is up and running for me on Pure Nexus with r5! Just flashed over r4 and flashed SuperSU 2.65, wipes caches rebooted. Thanks
[Nexus 6P Original Android Development] TugBoatTed:
Anyone else have issues with rgb adjustments not sticking on reboot when using fkupdater? Seems that blue reverts to low double digits on occasion
[Nexus 6P Original Android Development] franciscofranco:
Nope :( Always works.
[Nexus 6P Original Android Development] TugBoatTed:
Yeah, it may only be when I flash a new version of the kernel. No big deal!
[Nexus 6P Original Android Development] porter11:
Flashed r5 Test Geekbench

https://goo.gl/photos/BydsxiKrCz1zdTJA9
[Nexus 6P Original Android Development] franciscofranco:
You're either thermal throttled or cpu 6 and 7 are offline due to heat.
[Nexus 6P Original Android Development] bigxie:
Hey guys,

About to try this, but just double checking with all this systemless root talk around: if I don't care about that at all, can I install r5 simply by reflashing Chroma and then flashing the kernel afterwards? I'd prefer to keep SU 2.52.

Thanks!
[Nexus 6P Original Android Development] franciscofranco:
Hi. From the first post:
[Nexus 6P Original Android Development] infamous84:
this kernel only works with systemless root and i believe you need su 2.60 or higher. All the requirements are listed on the first page.
[Nexus 6P Original Android Development] bigxie:
Thanks, got it!
[Nexus 6P Original Android Development] tehpud:
Thank you good sir!

Franco posted the SU 2.65 on previous page download. Working for me now.
[Nexus 6P Original Android Development] mgear356:
Did that bro, but still got hang at loading screen on r5. Hmm sorry for being so troublesome.. Do let me know if u have any more ideas.. Would be glad to try it out
[Nexus 6P Original Android Development] inimaitimepass:
Lag and Camera FC while recording in UHD with Flash on

Hey francis,

I've faced an issue while recording UHD videos with flash on. I was on r4, stock ROM, SuperSU 2.65 when this happened. framework-res and SystemUI apk's modded to downsize navbar height. No other mods other than these.

First time, I was filming my 2yr old son playing and after about 10:32 mins when I hit the stop button the phone got freeze, It stayed like that for 4 or 5 mins, hitting the back or home key resulted in extreme lag. So I rebooted the phone, things were normal but the video file got corrupted (file size 3.20gb), probably coz of the reboot I guess, as the video file might be still in processing. Bit disappointed coz I know that moment will never come back :(

Second time, I wanted to reproduce the error, and this time after 8:35 mins the camera app got FC'd. But the video file was not corrupted (file size 2.26gb). I remember I got this similar issue when I was on EX kernel a month back.

On both occasions phone got moderate to heavy warm.

Then I flashed the stock kernel just to test, and even after recording for 12 mins the problem never occurred. No FC from camera app, phone didn't hang at all when hitting the stop button, the video file was okay (file size 3.54gb). No warmness felt.

I didn't try any other kernels coz I don't want to. I'm not sure whether it is kernel related or not. I'm reluctant to try r4 again to get logs or r5, coz I don't want to miss things that matters. Can you please take a look into it?
[Nexus 6P Original Android Development] Gytole:
R5 and 2.65 clear as filtered water here. Thanks ocnarF!

---------- Post added at 11:18 PM ---------- Previous post was at 11:12 PM ----------

Try downloading fstrim from the playstore and checking ALL THREE boxes and running trim. Friends have trouble with video recording sometimes, I NEVER have but unlike them I use trimmer (;

Good luck!
[Nexus 6P Original Android Development] G-Bus:
[MENTION=3292224]franciscofranco[/MENTION] is it cool to run greenify in conjunction with naptime?
[Nexus 6P Original Android Development] franciscofranco:
****. I'll try something else, I'll post a test r5 for you in a little bit.

Oh my, I'm so sorry! I know nothing will bring that moment back so either that problem was caused by FK or not I still feel obliged to apologize. That's a very rare scenario, I don't know how I'll reproduce, but I'll give a shot.

Yaps!
[Nexus 6P Original Android Development] G-Bus:
I noticed that with naptime in aggresive doze mode I keep getting this playstore error. Any way around it?
[Nexus 6P Original Android Development] Tehpdub:
I get the same thing and Facebook it says something like "can't find connection"
[Nexus 6P Original Android Development] tacosrdelicioso:
This is simply because you haven't updated your Facebook application. Yes, they're being tricky here but next time try not to place blame where it isn't.

This is unrelated to aggressive doze I have never seen this check your background data settings in the data section of settings
[Nexus 6P Original Android Development] azsl1326:
Sorry, but I was having the same issue with the play store. I turned off aggressive doze and it stopped!
[Nexus 6P Original Android Development] G-Bus:
I already made sure background data is on. When disabled agressive doze, it goes away.
[Nexus 6P Original Android Development] azsl1326:
Same issue. I turned aggressive doze off and it stopped.
[Nexus 6P Original Android Development] G-Bus:
Now with agressive doze off, does naptime do anything more than regular doze?
[Nexus 6P Original Android Development] tacosrdelicioso:
I've just never had these issues. Strange
[Nexus 6P Original Android Development] franciscofranco:
That's because Doze kills background internet connectivity. I disable force disable Doze when the display lights up, but sometimes it might take a couple more seconds to completely come out of force mode or something, so when you open some apps the first time after Doze was forced to be enabled some might warn you about bg data being off (which it isn't). Just close the app and open it again and you'll be fine. I have a newer Naptime version with revised timers to try and go around that, and I've barely see that warning anymore, so watch out for the Play Store in a couple days.

TL: DR - don't freak out, close the app and open it again. Wait for Naptime update with revised screen off/on aggressive doze timers.
[Nexus 6P Original Android Development] bouchigo:
I had the same issue with r2 and r3, but haven't seen it with r4 and r5...yet.
[Nexus 6P Original Android Development] venelar:
[MENTION=3492699]G-Bus[/MENTION]

You can leave aggressive doze on if you go into battery settings and un-optimize play store. Only solution I found.
[Nexus 6P Original Android Development] G-Bus:
Ok. Thanks for the clarification.
[Nexus 6P Original Android Development] swallowingled:
I actually had this issue a couple weeks back when I was on stock kernel, before ever trying a custom kernel on my 6P. I checked and background data was already enabled but the Play Store kept giving me that error. So I rebooted and that solved the issue. I haven't seen it since then either. I think it's either a MM issue or Play Store app issue(just a guess though). There's a thread in the 6P forum with a few others seeing this error as well.
[Nexus 6P Original Android Development] inimaitimepass:
I'll give it a try sometime later, though I don't have this issue with stock kernel.

Pls don't. I like your work and I still want to use your kernel, that's why I came here to report about it. If any others, I would never come back. I'll try to investigate more tonight.

And thanks for your kindness.
[Nexus 6P Original Android Development] nldxda:
I got a bootloop after auto flashing r5 from within FKUdater app..

Went into RECOVERY move and flashed r3 and then SuperSU 2.65 and everything is working properly again

.. Scared to try flashing r5 again ?
[Nexus 6P Original Android Development] frost_nz:
Did you read the instructions?

Edit: sorry, didn't mean to sound rude. You'll need to download the zip installer, flash it, then flash superSU
[Nexus 6P Original Android Development] nldxda:
Well no, I auto-flashed it from within the FKUdater app after I noticed the thread title here had been updated to r5
[Nexus 6P Original Android Development] frost_nz:
Yup, a change was reverted that means you still need to flash superSU manually for now
[Nexus 6P Original Android Development] nldxda:
OK just flashed r5 from recovery as well as SuperSU 2.65 directly after and it booted properly and everything is working fine now..
[Nexus 6P Original Android Development] ROADKING17:
r5 and SuperSU 2.65 and everything is smooth as butter Gracias Franco!
[Nexus 6P Original Android Development] rbrenart:
What do you mean by disable XBIN in SU? I'm failing the SafetyNet Helper app on the CTS verification step, and I'm guessing that's why.

edit: Oh, I see, you just mean move the SU file out of the /System/XBIN/ folder. Passing SafetyNet Helper now with r5, Systemless 2.64, and Stock Rom.
[Nexus 6P Original Android Development] franciscofranco:
Maybe read the change-log the next time :p
[Nexus 6P Original Android Development] franciscofranco:
[MENTION=1029492]mgear356[/MENTION] please test the attached boot.img
[Nexus 6P Original Android Development] tehpud:
OK. Noticed a couple bugs but could be superSU related. I had R5 flashed and 2.61. Got the latest 2.65. Went into recovery, ran unSU, flashed 2.65.

Noticed the time on notification bar wasn't updating and websites were not fully loading. If i killed WiFi then it would kick in and sites would load. But the time would be frozen unless i locked screen and unlocked again.

Running R5 now, cataclysm, and superSU 2.61 again. Everything working as normal again.

Wanted to share the hiccups!
[Nexus 6P Original Android Development] 220volt:
Wow how did you get that score? I'm only getting 4100-4300 running r5.

Skickat från min Nexus 6P via Tapatalk
[Nexus 6P Original Android Development] jodvova:
Franco, what tool chain and compiler version do you use to build the kernel?
[Nexus 6P Original Android Development] mgear356:
Gotten first in game freeze after 40mins..

On a side note, the game seems smoother.. Was it a placebo?

EDIT 2: no go bro, after closing the first game, got a 2nd hang at loading screen
[Nexus 6P Original Android Development] :
[MENTION=3292224]franciscofranco[/MENTION]

Would you consider adding i/o readahead to fk updater? Thanks!
[Nexus 6P Original Android Development] Subiegsr:
I followed the steps (minus reflashing rom/gapps), although it didn't seem to do anything inside the terminal from what I could tell. Hopefully that's right?

After typing the three lines I just exited out and flashed. Flashed 2.65 with r5 fine and Android pay opens up fine.
[Nexus 6P Original Android Development] shawnaye:
Quick question, is it advisable to clear cache after flashing new kernels?
[Nexus 6P Original Android Development] DaveHTC200:
It's not required, not sure it ever has been, well I've never done so [emoji4]
[Nexus 6P Original Android Development] rebretz000:
That's what I was getting also.
[Nexus 6P Original Android Development] 220volt:
Same as me or Franco?

Skickat från min Nexus 6P via Tapatalk
[Nexus 6P Original Android Development] rebretz000:
Sorry, same as you. Highest I got was around 4200.
[Nexus 6P Original Android Development] TheDarkAngel666:
Same here, 4300 in multi, that commit is not working very well xD
[Nexus 6P Original Android Development] SuperQvas:
Wow, thats humble! I wasnt expecting that. Theres no peoblem

Inviato dal mio Nexus 5X utilizzando Tapatalk
[Nexus 6P Original Android Development] M1LL3R:
don't know if its already reported or its only for me but when I try to change the saturation values it don't change anything... Any one in the same boat?
[Nexus 6P Original Android Development] d3xt3r:
Y is this wake up occurring?? N how to stop it

Edit- If any other info needed, will be happy to provide. I'm on r5
[Nexus 6P Original Android Development] Brembo109:
No need to wipe anything after or before flashing a kernel. Wiping cache has no effect on the kernel partition.

Gesendet von meinem Nexus 6P mit Tapatalk
[Nexus 6P Original Android Development] franciscofranco:
That looks like Aggressive Doze was enabled or something.

I get it consistently when the device is cold. Nevertheless, I saw a performance boost on hackbench, which is reliable for me.

aarch64-linux-android-4.9 from https://android.googlesource.com

****.

Nope, it's pointless and most users don't know what's it for other than "perceived" inflated I/O benchmark numbers.

Works just fine, I tested it. Don't forget to screen off/on to make sure the values are applied (although it shouldn't be needed).

Long shot: you're roaming, maybe it's working hard to scan for networks? If that's not it then I don't know, just seeing "android" doesn't say anything to me.
[Nexus 6P Original Android Development] avetny:
Stock debloated rom.

Franco did you notice that when u running antutu on your kernel the animation there is lags. (On stock no)

The kernel is quick, but somehow the animation is smoother on stock kernel.

Best regards
[Nexus 6P Original Android Development] jodvova:
Franco, can you support 5.3 tool chain?
[Nexus 6P Original Android Development] franciscofranco:
I don't run Antutu, so I don't know. Increase input_boost_ms if you want.

No.
[Nexus 6P Original Android Development] rbrenart:
It opens fine, but run SafetyNet Helper from the play store and see if you pass all 3 checks. My understanding is it won't actually process a payment if you don't get a green light on all 3, though I haven't tested it when failing one personally.

I had to take the last step of opening /system/xbin/ in root explorer and deleting the su file there (actually I moved it to another directory in case I was borking something). Now I have a green light in that app with Franco r5 on stock ROM. Though I've been a home body lately so I have not confirmed android pay yet.
[Nexus 6P Original Android Development] rp1226:
I've been using AP and having no issues. Last time I used it, I was on FKr4 w/ Su 2.65. No issues there. Just make sure to remove the directory /su/xbin_bind/. Reboot. Green checks all around and good to go!

Edit: Just used it now. FKr5 w/ SU 2.65 no issues.
[Nexus 6P Original Android Development] d3xt3r:
Maybe that's the reason, cause I had to manually register on my network as it had a v Sh*tty reception out here for 3g. I switched to 2g. Let's see how it goes. Thank you for the support
[Nexus 6P Original Android Development] franciscofranco:
I think I finally fixed PerApp-Profiles for good. It requires a special permission, but that's the only way. Been testing it for the past few days and it's been working flawlessly, If all goes well 14.0.2 should go up today.
[Nexus 6P Original Android Development] andreoidb:
I was running perfmon with r5 and was noticing that none of the cores where going offline. Anyone else seeing this?
[Nexus 6P Original Android Development] franciscofranco:
Yes, same behaviour as stock Kernel.
[Nexus 6P Original Android Development] andreoidb:
Really?! What would be the downsides to unplugging a few of the big cores if they are not needed?
[Nexus 6P Original Android Development] franciscofranco:
There's no need to plug them off, they go into a deep idle state during runtime.
[Nexus 6P Original Android Development] dmeadows013:
Franco—

Everything running flawlessly on r5 right now, great work! One question: Do you have any plans to add T-Mobile WiFi calling support? I thought root might be breaking it but it is working for others on 2.62-3.

Thanks
[Nexus 6P Original Android Development] Subiegsr:
Just downloaded the safety net helper app and passed all three checks. Thanks for the tip, didn't know that app existed.

I just checked through root Explorer and my xbin directory is still there though, should I delete this to be safe? Even though I passed the checks?
[Nexus 6P Original Android Development] rp1226:
If the checks are passed, don't worry about it.
[Nexus 6P Original Android Development] bikeryder007:
I have t-mo wifi calling working right now with r5 and 2.65

I had to troubleshoot the duck out of what was breaking wifi calling, and traced it back to busybox.

Even with a totally clean system and android pay working, busybox still breaks my wifi calling.
[Nexus 6P Original Android Development] carlylemiii:
I noticed the time issue with R5 and 2.65 as well...I reverted back to R4 and 2.65 for the time being, and now my time is updating appropriately. Yes, I do have Aggressive Doze enabled, but I have this whole time and on R4 and earlier and pre-2.65. Hoping whatever it is just somehow works itself out in R6 :)
[Nexus 6P Original Android Development] bigxie:
Maybe it depends on the busybox distro? My wifi calling is working fine on Chroma with the included busybox and r5, SU 2.65.
[Nexus 6P Original Android Development] dmeadows013:
Huh. Can you still do everything in FKU without busybox? If so, I'd happily uninstall it
[Nexus 6P Original Android Development] ParadingLunatic:
I don't seem to be having this issue. My phone is still vibrating (correctly) when unlocking with the fingerprint scanner. Although perhaps it may not be as strong as before.

edit...yeah I believe the vibration may not be quite as strong as it was before.
[Nexus 6P Original Android Development] franciscofranco:
Stock volume is not equal? I admit I don't use the speakers that often.

Neps.

Probably neps, for now.

Heya :D I didn't touch anything sound related, it's all stock! I've used my Philips M2BT a lot lately when doing stuff around my room and I actually thought it wasn't THAT loud and those headphones are only 16ohm.

Something is ****ing your device, it's not my Kernel.

:good:

System-less root doesn't break Android Pay, you're safe to use it. Busybox on the other hand changes /system. Don't use it. You can tell Kernel Auditor dev to fix his app to stop using busybox.

Question: do you notice any lag when gaming? I told you, I ran several benchmarks, scores are unchanged vs stock so there's no performance regression when running demanding workloads. And how are you even checking if cores are on or off? Is it a reliable app?