yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Original Android Development] bobby_digital234:
hey flashed and booting now on the 1-10 build for sprint testing. sorry i had some xfinity internet issues right in the middle of my download last night

---------- Post added at 10:50 PM ---------- Previous post was at 10:39 PM ----------

sprint data on 1-10 build is working great. thanks for the update. i guess the question now will be should i stay on this build or get the 1-11 build i saw you pushed today
[Nexus 6P Original Android Development] chadouming:
New build should keep working well.
[Nexus 6P Original Android Development] bobby_digital234:
awesome thanks so far so good. one questoin though about fingerprint reader delay when screen off am i the only one getting this? or is it because i just flashed and need to let things settle down a bit.
[Nexus 6P Original Android Development] indian84:
No. You are not alone. I also have delay.

But unfortunately no one else reported this issue, so assumed it was my phone that's behaving funny.

@ Chad, you mind looking at this? I can assist with some debugging if you want.
[Nexus 6P Original Android Development] TrainNanpaMaster:
in developer options, turn off animations.

Please report if you still have fingerprint delay.
[Nexus 6P Original Android Development] bobby_digital234:
the delay is reduced slightly as far as screen turning on but there is a noticeable delay from the time i touch the reader to the time i get feed back and action. say maybe 2-3 seconds.
[Nexus 6P Original Android Development] TrainNanpaMaster:
Guys!! I think i found the problem! (albeit accidentally).

I forgot to flash SuperSU. The rom booted, but it was raped of so much functionality. I would place my finger on the fingerprint sensor, and there was indeed a 2 second sh1tty delay.

Perhaps....you're using old SuperSU or none at all?

If you haven't already, please download and flash SuperSU 2.79 SR3 beta:

http://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip

This is why i never had the problem. fingerprint sensor opens instantly!
[Nexus 6P Original Android Development] TrainNanpaMaster:
Chad - I noticed Nathan (Flash) managed to release his latest kernel iteration on gcc 6.3.1. I noticed your faster kernels are 6.2.1.

Any way you could give the newer gcc a whirl for your kernel nightlies?

Or, is there no real benefit to doing so?
[Nexus 6P Original Android Development] chadouming:
I only forgot to update the toolchain i build my kernel with, look for R47 with 6.3.1 soon. Benefits won't be night and day.
[Nexus 6P Original Android Development] cutmylifein2:
[MENTION=1986924]chadouming[/MENTION]

Just saw that 17 Jan build is 600mb.. Any reason for the same.. Anything new
[Nexus 6P Original Android Development] TrainNanpaMaster:
?? I just downloaded it, it says 289 mb.

---------- Post added at 01:51 AM ---------- Previous post was at 01:00 AM ----------

Chad excellent job on the Kernel. It might be placebo, and maybe you changed the parameters like touch response time or Touch Boost, but the kernel is DEFINITELY noticeably faster.

Oh I don't want to gripe or complain, but in the 1/17 build, the camera seems to be missing from the rom.
[Nexus 6P Original Android Development] puritan007:
Awesome ty for all your excellent work
[Nexus 6P Original Android Development] kingmikel:
[MENTION=5169465]DespairFactor[/MENTION] can't wait to flash this and give it a try! Any recommended settings?
[Nexus 6P Original Android Development] DespairFactor:
Using the default should be fine for now:)
[Nexus 6P Original Android Development] kingmikel:
Damn it man... I just downloaded 2.1... and 2.2 is out?!? Jk jk!
[Nexus 6P Original Android Development] jodvova:
On Kylo! Thanks!
[Nexus 6P Original Android Development] Pilz:
It's good to see kernels out already! I enjoyed the crazy sh*t you did on the Nexus 6. I need to flash this later today :)

Edit: This is my 5000th post too! I can't believe I've had that many
[Nexus 6P Original Android Development] DespairFactor:
You'll say the same at 10,000!

I noticed by default the min frequencies are not being set at the minimum, go check it out and fix it on your devices.
[Nexus 6P Original Android Development] jodvova:
Hi Despair,

Is there any way you can reenable QC 2.0 in the kernel?
[Nexus 6P Original Android Development] DespairFactor:
Find me proof of the battery actually having g it and it being beneficial. This phone charges at 3 amps, pretty sure that's higher than the quick charge standard
[Nexus 6P Original Android Development] Pilz:
I didn't flash it yet, but there's definitely some issue in the stock kernel. I am getting a ton of drain on it so I need to flash your kernel sooner rather than later so my phone doesn't die at a faster rate doing minimal tasks.
[Nexus 6P Original Android Development] DespairFactor:
Flash it, you can shoot me a hangouts message too
[Nexus 6P Original Android Development] ninjosh97:
This would be phenomenal. The lack of 3amp chargers is a serious issue. Would be sweet if I could just buy a quick charger.
[Nexus 6P Original Android Development] Pilz:
I'll let you know, my 128gb comes tomorrow finally (ordered 9/29) so I can send the 32gb one back. I was going to flash it earlier, but now that my initial order shipped I will until it gets delivered to do it. I don't want to worry about restoring a phone since I have a class all weekend from 0800-1700 including tomorrow :eek: but at least I will have my 128gb to flash it on :D If I have any issues I'll shoot you a message! Thank you for all of your hard work!
[Nexus 6P Original Android Development] DespairFactor:
The lack? your phone comes with one...
[Nexus 6P Original Android Development] ninjosh97:
I meant 3rd party. I need more than 1 charger. If you saw the way I have it plugged in you would understand. ☺
[Nexus 6P Original Android Development] kibmikey1:
Just an fyi, chainfire's systemless image works with 08M as is. So, if I want to return to stock (or cf stock modified...) all I'd need to do is flash the boot image in fastboot, right?NVM...re-read OP and facepalmed...
[Nexus 6P Original Android Development] seanayyy:
SOT is good

I was getting 3.5 hours of SOT with stock kernel, now quite a bit better with R2.2 w/ 5.5 hrs

Can you flash R2.3 over R2.2?
[Nexus 6P Original Android Development] jodvova:
Could you make Linaro build as well?

Is 2.4 any good or should I stick with 2.3 for now?
[Nexus 6P Original Android Development] teh roxxorz:
In the app, select the CPU tab. Then from either big or little select the check mark on the core you want to disable. It will say offline then.

Sent from an educated cellular device
[Nexus 6P Original Android Development] DespairFactor:
The wifi drivers are 100% the same... as is cellular on every kernel. No one has modified these yet...................
[Nexus 6P Original Android Development] hibby50:
Idk what's up with your WiFi maybe try another hotspot. There shouldn't be any problems with either. But for lte you can try repairing your network settings (if you're on fi) by dialing *#*#34963#*#*
[Nexus 6P Original Android Development] TheShamsMan:
It was strange.. Everything was fine until I flashed Kylo. Network would only work to some extent, like I can Google search, but can't click on any of the results. Facebook and Instagram would not load any images or comments. No notifications.

What's really strange is that I regained all network functionalities when I plugged my device in via USB. No mode selected. Just plugged in to charge and bam! Network. Really weird.

Anyways. I flashed stock and starting from scratch again. Will report back! I appreciate the help guys!
[Nexus 6P Original Android Development] xSilas43:
Try flashing the latest vendor.img and radio.img
[Nexus 6P Original Android Development] jaythenut:
4.8 running nice and smooth mate :good:
[Nexus 6P Original Android Development] Jsilver73:
Nice kernel, nice ROM - I like :good::)
[Nexus 6P Original Android Development] chrisexv6:
Which theme was it?
[Nexus 6P Original Android Development] mtw4991:
Strange, on 4.6 kernel, interactive all cores on as shown below, I ran Antutu and get only 55000 or so but cpu spy doesn't show anything above 1333. Normal or not?
[Nexus 6P Original Android Development] dabug123:
I hit all oc speeds
[Nexus 6P Original Android Development] mtw4991:
Just flashed 4.8 kernel, will reset CPU Spy and re-run Antutu. Will use Ondemand gov also to see it it registers

EDIT: Ondemand for Big/Little both, CPU Spy still shows max 1333MHz. Wonder if it only reads the Little core, not Big...anyone know? Kernel Audiutor shows all cores running fine, btw
[Nexus 6P Original Android Development] ChronoReverse:
Is there a changelog for 4.8?
[Nexus 6P Original Android Development] DaveHTC200:
I would imagine it's just reading the smaller core

Edit: its not been updated since 2013, so single core is all its reading, that's what I believe! Use an updated app that monitors multiple cores
[Nexus 6P Original Android Development] joeyac02:
Been running this kernel with pure nexus and goodness what great battery life and performance! Thanks for everything!
[Nexus 6P Original Android Development] ahoslc:
Anyone have some good settings I don't game just text and browsing and music?
[Nexus 6P Original Android Development] SwimDrewid:
I read previously:

I haven't yet seen how to keep all cores on (or if this is necessary). I see for me that Big: core 2 and 4 sporadically toggle on/off. Dunno if that's a thing.

Is there a better (more recommended) governor than interactive? I'm on Pure Nexus. Not a heavy gamer. Mostly Doctor Who Legacy, videos and social media
[Nexus 6P Original Android Development] DespairFactor:
I run impulse on my device on both clusters
[Nexus 6P Original Android Development] hibby50:
Has anyone messed with the undervolting yet? What's a safe amount to do for all frequencies?

Edit: just tried in kernel adiutor and the voltages don't stick. Guess it hasn't been implemented yet or I'm screwing something up.
[Nexus 6P Original Android Development] DespairFactor:
It is just exposed values at the moment, no tweaking
[Nexus 6P Original Android Development] mtw4991:
That's what I think also, any recommendations for apps that can read both?
[Nexus 6P Original Android Development] ahoslc:
Jan 17th

Jan 17th also shows 626mb when I download it afraid to flash it lol
[Nexus 6P Original Android Development] TrainNanpaMaster:
Please read the thread a little before posting. The rom is normal sized, 289 mb.
[Nexus 6P Original Android Development] ahoslc:
What are you talking about I did read the thread and I know the normal size is 289mb! Did you read my message when I said 1-17 shows a size of 640mb I also downloaded the file and it's also 640mb
[Nexus 6P Original Android Development] TrainNanpaMaster:
That's bizarre. I download the first time it was showing up as 289 megabytes in my system folder. I installed it and it's running great. But now I redownloaded it, and it is showing 656.

Maybe......gapps is included?
[Nexus 6P Original Android Development] chadouming:
it is really 640 MB more or less, now gapps are included cause i was tired of waiting for gapps to flash.

Included is what i use. Nano gapps, with chrome, google camera, music and maps.

That way it should also fix ok google problem (Reinstall google app if it doesn't work)
[Nexus 6P Original Android Development] eqbirvin:
Great call IMO. We can pick that up from your https://temp.bbqdroid.org, right?
[Nexus 6P Original Android Development] TrainNanpaMaster:
Chad - the AOSP camera included in gapps is great, but it doesn't seem to have shutter silence feature. The old camera that used to include within the ROM had this feature. And also renaming the media > UI > camera_click doesn't work anymore to silence the shutter.
[Nexus 6P Original Android Development] ChongoDroid:
Always thought that was against the rules but maybe things have changed. Saves me time as thats what I use as well.
[Nexus 6P Original Android Development] ChongoDroid:
I've searched for an answer and I see that a few people have encountered this issue. Sorry if it's been covered I just couldn't seem to put my finger on it.

The TWRP wrong password bug. First time I've encountered this one. Is there a compatible version of TWRP or a different su package used to root? Seems as if on first boot after flashing the latest SuperSU that the PIN somehow comes back as incorrect.

Again, sorry if this has been covered. I love this ROM, functional mods like the charge rate on the lockscreen will keep me coming back for more ?

---------- Post added at 11:46 AM ---------- Previous post was at 11:26 AM ----------

Oh weird, I just tried 0000 and it worked! Lol, well nevermind... I'm all good to go.

Edit: OK so 0000 works to enter recovery but won't decrypt the phone.

Using the 19 build
[Nexus 6P Original Android Development] xSilas43:
Use the latest twrp 3.0.3 should fix this. Your phone is encrypted so you need to use your pin to boot the device.
[Nexus 6P Original Android Development] ChongoDroid:
I am using the latest TWRP 3.0.3.0

---------- Post added at 04:50 PM ---------- Previous post was at 04:48 PM ----------

I understand how direct boot works and I've never encountered this bug on stock rooted, custom etc

I just tried switching to pattern and it says it's an incorrect pattern upon first boot.
[Nexus 6P Original Android Development] xSilas43:
Was your phone previously decrypted? If so then I believe the ROM has encrypted your device and you'll have to wipe internal storage unfortunately. A few pages back I believe someone had the same issue with the stock kernel.
[Nexus 6P Original Android Development] ChongoDroid:
Nope, never decrypted. Flashed the latest ROM and kernel and then SuperSU and that happens on the next boot.

Just tried it after clean flashing the latest system image and it still happens. Anyone on the 19 build confirm this?
[Nexus 6P Original Android Development] ChongoDroid:
I'm kind of lost as how this modifies your security pin. This is the only ROM that's done this.

So can any user tell me which version they're using successfully rooted? Just tried the latest kernel thinking it might fix it but it's still screwed. It's a bit annoying since you have to flash a factory image to fix it.

---------- Post added at 10:27 AM ---------- Previous post was at 10:22 AM ----------

Same problem. SuperSU is not the culprit. I've flashed beta SuperSU, I've flashed release SuperSU, I've even tried phh Superuser.

Are people just not rooting with this ROM?

---------- Post added at 10:29 AM ---------- Previous post was at 10:27 AM ----------

Wait, this is N4F26J, right? If I've been using the wrong vendor I'll literally put my palm through my forehead

---------- Post added at 10:34 AM ---------- Previous post was at 10:29 AM ----------

Just noticed there's a 21 build, guess I'll try that and see if it fixes this. I simply won't switch to another ROM, this one has every feature I want and performance is fantastic.
[Nexus 6P Original Android Development] ChongoDroid:
Ok I give up. I flashed the 21 build, and upon booting into recovery to flash superuser, I get the wrong password error. So now it's happening even without root.

Starting to feel like an echo chamber so I'll try again when this is fixed or even addressed.
[Nexus 6P Original Android Development] TrainNanpaMaster:
It's official. I'm now a BELIEVER.

In F2FS.

I finally took the leap and converted to it.

Nathan (Flash) managed to find a way to let us convert the cache partition to f2fs (in his new 3.0.3-1) TWRP build. So now we are able to use f2fs as it was intended, on both data AND cache.

To anyone that I showed doubt to in regards to f2fs, I sincerely apologize. It is indeed noticeably faster. Apps fly open now, everything is glassier, and snappier. There is definitely a profoundly noticeable difference over ext4. In fact, it really feels like I have a new device. The best way I can explain it - is that the phone feels like it's running at a constant 60fps now.

I was able to move my ext4 nandroid over to my freshly partitioned f2fs 6p. This saved HUGE amounts of time setting everything back up. I just had to copy over TWRP backup (and restore) the DCIM folder, as well as my titanium backup folder, along with all the standard rom stuff like gapps, rom, kernel etc.

All in all, I'm extremely impressed with f2fs. I'm now a believer.
[Nexus 6P Original Android Development] Dbj.Dhaval:
Does it survives reboot ie every time I convert to f2fs in twrp during first time it will say data converted to f2fs Bt when I reboot to twrp again the data is again automatically converted to ext4
[Nexus 6P Original Android Development] TrainNanpaMaster:
Mine stayed f2fs. It survives reboot.
[Nexus 6P Original Android Development] aoaleman:
Care to share what ROM and kernel you are using? Chad's build?
[Nexus 6P Original Android Development] TrainNanpaMaster:
Sure, no problem at all:
[Nexus 6P Original Android Development] aoaleman:
Thank you! Might give this all a shot.
[Nexus 6P Original Android Development] TrainNanpaMaster:
I was the biggest detractor/skeptic of this. If you go a few pages back, you'll see I was questioning a few users if it's worth it. Now i feel like a d0uche.

It's definitely worth it.
[Nexus 6P Original Android Development] aoaleman:
I think I remember that, lol. It's all good. :D
[Nexus 6P Original Android Development] bobby_digital234:
I'm curious where you got a version of TWRP that works to convert to f2fs I always have a default password needed to decrypt when I try any of the ones I've seen. Oh and they are 3.0.3-0 ... I've not seen a 3.0.3-1 anywhere
[Nexus 6P Original Android Development] TrainNanpaMaster:
http://nchancellor.net/TWRP/

Custom TWRP designed by Nathan (Flash) Dev.

No default password is needed. Simply go to WIPE > Format Data.

If for some strange reason it does ask you for a default password, I believe it's 0 0 0 0.
[Nexus 6P Original Android Development] bobby_digital234:
Hey thanks man I appreciate it I'm excited to get f2fs working because on my old m8 it was a HUGE improvement
[Nexus 6P Original Android Development] TrainNanpaMaster:
My pleasure man.

Until recently I never would have believed it myself.

But it is a huge Improvement.
[Nexus 6P Original Android Development] bobby_digital234:
Yeah it traditionally is thought to only impact older slower styles of memory but it in fact is overall a massive speed increase. I had an old Moto droid Maxx that used f2fs stock and it was probably the fastest phone I've ever owned and it only has a dual core processor
[Nexus 6P Original Android Development] TrainNanpaMaster:
One thing I noticed right away is that apps pop open quite a bit faster. Also - scrolling is basically flawless now. So smooth and glassy.

When you're switching from Google keyboard to Google voice input, the transition is instantaneous.

Apps just fly open now. It feels like I'm running FRAPS, and I just turned up the playback speed.
[Nexus 6P Original Android Development] ChongoDroid:
Think I'll have to be trying out f2fs as well. Cheers.
[Nexus 6P Original Android Development] Dbj.Dhaval:
No matter what I try mine does not survive a reboot data does not but cache survives a reboot
[Nexus 6P Original Android Development] TrainNanpaMaster:
That sucks man. Are you using Chad's newest everything? Rom and kernel?

TWRP import and restore definitely permanently works for me.

Maybe... clean flashing is the only way that will work for you?

Here's a method that will probably work for you:

The 22nd build has been uploaded. If your TWRP nandroid is the 21st build, go ahead and restore that.

Go ahead and then boot into the rom. At this point, you should definitely still be on f2fs. Now, boot directly into recovery. Install the 22nd build.

From this point forward, the f2fs should 'catch' and not give you any more difficulties.

And by the way, are you using the newest Chainfire Beta SuperSU? 2.79 SR3? That's what I'm using.
[Nexus 6P Original Android Development] Dbj.Dhaval:
Thanks for the help will try ur method and report back.
[Nexus 6P Original Android Development] TrainNanpaMaster:
I just noticed, r50 and 1/23 builds are now up.

Chad is a machine.
[Nexus 6P Original Android Development] TrainNanpaMaster:
WAIT! I think I discovered the problem.

When you originally converted data and cache to f2fs, did you format data first?

This MUST be done. The whole phone must be decrypted and reformatted.

This will completely wipe your device though. So please backup your important files.

Per Flash the developer on his modified TWRP:

* If swapping to F2FS does not stick, try formatting your data with TWRP (Wipe > Format Data) or fastboot format userdata first.
[Nexus 6P Original Android Development] Dbj.Dhaval:
Yup even done that. Will try again Tonight. Even tried with other rom still no luck.
[Nexus 6P Original Android Development] bobby_digital234:
The above method definetly works fastboot format system cache and user data, boot to correct recovery. Change data to f2fs THEN cache then reboot recovery and verify it stuck now transfer your ROM ,I'm on 1-22 build right now... Flash ROM and SuperSU sr-3 then boot ROM and you should be golden
[Nexus 6P Original Android Development] ariefabuzaky:
Do you use substratum ? Mono ?
[Nexus 6P Original Android Development] bobby_digital234:
I have not really messed with substratum themes, too many are incomplete. Ill have to check that one out
[Nexus 6P Original Android Development] Utkarsh-ezzo:
where can I find the builds? and list of features included?

Sorry If asking too much, new to this thread.
[Nexus 6P Original Android Development] cutmylifein2:
OK google detection is intermittent in chads latest build of 24/1. Sometimes it detects and most of the time it doesn't
[Nexus 6P Original Android Development] TrainNanpaMaster:
Not really my place to say, but not sure why so many people like to use 'Ok Google'. I feel like a huge turkey walking around saying that in public. It feels gimmicky more than anything. If i need Google Assistant just have that set to 'swipe up' in middle of my phone with tasker.
[Nexus 6P Original Android Development] spuri78:
https://temp.bbqdroid.org/
[Nexus 6P Original Android Development] rakkkar:
Not sure if anybody can help me but is anyone having issues with fingerprint recognition to unlock? When my phone does not recognize my finger and vibrates, it does not take a second try until I wake the screen and try again. It does not even vibrate after the first try until I do that and same goes for when I have woken up the display (only allows for one try again). I have been having this issue with every built in recent times.
[Nexus 6P Original Android Development] cutmylifein2:
+1
[Nexus 6P Original Android Development] rakkkar:
I have a quick question, I have successfully used your method of choice to get f2fs set up but funnily enough, I do seem unable to flash a custom kernel now (it successfully flashes in recovery but once I reboot, I am still seeing the one coming with the ROM). Have you tried the same and can confirm that it does not work or is there something I might be doing incorrectly (I have for example tried flash kernel which should work on f2fs, if I am not mistaken).
[Nexus 6P Original Android Development] bobby_digital234:
That's a good question I wouldn't know for sure about flash kernel but i did after a first setup and reboot successfully flash Chad's #50 kernel and it took. I've seen in the past where if you flash the kernel before first boot TWRP doesn't successfully flash the kernel. I.E. flask ROM,Gapps , kernel before initial boot can cause issues so I've resorted to always flashing the ROM booting then flashing kernel after that. Hope this helps if not it may be worth asking flash I know he's been revising and making improvements to his kernel and I may check it out again soon.
[Nexus 6P Original Android Development] rakkkar:
Thanks! I did not flash it before the first boot so I was surprised that it did not stick. I'll probably try and flash the newest faster kernel to see if it does stick. If it does I'll hit the Flash up.

Edit: Didn't work. I suppose it could either be the recovery or the ROM so I'll redownload the modified TWRP and try it again with that before clean flashing yet again.