yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Original Android Development] franciscofranco:
The vibrator driver is on the Kernel yes. My 6P vibrates correctly for fingerprint allow/incorrect. But I'm glad you mention this, I was waiting to see when someone noticed. I lowered the default vibrator value because it was unbearable to me. I'm glad to see after hundreds of flashes only 1-2 users noticed it so I might just increase it a little bit next release until we find a sweet spot for everyone.
[Nexus 6P Original Android Development] inffy:
I am actually on the same boat wit Franco. The stock vibrate is way too loud
[Nexus 6P Original Android Development] Vangelis13:
I assumed you wouldn't have. Odd, I'll investigate further. Maybe the old unpair & pair again will help. Right now so loud it's unusable! ?
[Nexus 6P Original Android Development] franciscofranco:
Keep us posted :)
[Nexus 6P Original Android Development] __NBH__:
Now I'm home I can feel it very slightly but when I was out and the wind was blowing I couldn't feel anything, I don't mind it being lower, I'm just used to my hand touching the phone by accident when it's in my pocket and I feel the double vibrate, now I don't feel anything.

The kernel is running great, amazing battery and it feels really snappy.
[Nexus 6P Original Android Development] franciscofranco:
I'll add this interface to FKUpdater.
[Nexus 6P Original Android Development] daivee:
[MENTION=3292224]franciscofranco[/MENTION] thank you so f****** much! Only kernel I really care about is alive!
[Nexus 6P Original Android Development] infamous84:
will we be able to manually change this?
[Nexus 6P Original Android Development] Ulver:
I thought I was going to stay completely stock, but now I have to give Franco kernel a go! Thanks!
[Nexus 6P Original Android Development] THATTON:
I've tried to install this kernel a few times and every time it appears to unroot my phone. Any ideas? Root was working fine until I flash the kernel all 3 times. I am running Cataclysm 6.0.1
[Nexus 6P Original Android Development] rebretz000:
Now that it's been mentioned I do notice it's nice and subtle vibration when using fingerprint to unlock. I think this is the sweet spot.

Also I like that your kernel app does require busybox. Bonus.

And it has a dark theme option.
[Nexus 6P Original Android Development] franciscofranco:
You can do it manually using adb. The path is in /system/init.angler.rc, last couple lines, something like /sys/class/timed_output bla bla. Stock value is 1800. I'll add this to FKUpdater soon.

Did you read the first page, or the change-log linked on the first post? You need to use system-less root.
[Nexus 6P Original Android Development] Neverendingxsin:
Are you using 2.61 systemless?

Also random question, but why busybox on rails instead of the normal busybox installer? Anything different or better?
[Nexus 6P Original Android Development] Msan2000:
I'm currently on Elemental-X kernel.. Can I just flash over that?
[Nexus 6P Original Android Development] THATTON:
I did read and the first page and I am using the systemless root.

---------- Post added at 09:43 AM ---------- Previous post was at 09:43 AM ----------

Yes I am using systemless root.
[Nexus 6P Original Android Development] franciscofranco:
Yes.

You need to flash SuperSu zip AFTER flashing the Kernel because SuperSu patches the boot.img.
[Nexus 6P Original Android Development] THATTON:
That is what I just did and was coming back to report that I had to flash the SuperSU.zip after. So do we have to flash the SuperSU.zip after flashing a new kernel each time? I just began using the systemless root method so I am unfamiliar with standard practices regarding it. Thanks btw!

I read the OP a hundred times just to be sure I didn't miss anything and I didn't know that we would need to flash Super SU each time. It may not be a bad idea to add those instructions to the OP. Just a thought.
[Nexus 6P Original Android Development] franciscofranco:
Yes, good idea, I'll add the supersu part to the OP. And yes, you need to flash supersu zip after flashing a Kernel, every time. It's a good tradeoff because this method doesn't change /system so for OTA's you just need to flash stock boot.img back and you can apply the ota without a problem. And Android Pay works.
[Nexus 6P Original Android Development] infamous84:
Ya you dont need busybox for FKU, because it is built off of the systemless root method
[Nexus 6P Original Android Development] dmeadows013:
What version does it have preloaded?
[Nexus 6P Original Android Development] Nocturnal86:
Had a question for you,

So if I'm stock rooted with systemless 2.65 and have FK and don't pass CTS with the app. What are my options to get AP working?
[Nexus 6P Original Android Development] rp1226:
If it didn't pass CTS profile, there is a modification in the system. If you are completely stock and you just flashed root and FK, then the issue is most likely in the folder structure that SU installs. The fix is simple, just delete the following folder:

/su/xbin_bind

Try it and let me know if that resolves your issue. Feel free to PM me.

Edit: Don't forget to reboot and run SafetyNet Helper again.

Cheers!
[Nexus 6P Original Android Development] bigxie:
Looks like v1.22.1
[Nexus 6P Original Android Development] dmeadows013:
Cool! WiFi calling now works, thanks!
[Nexus 6P Original Android Development] mystertom101:
3 hours of Bluetooth speaker music playback and general heavy usage I'm actually impressed now
[Nexus 6P Original Android Development] aeppacher:
tried this but it just reboots when I do this. I am pretty sure volume buttons are broken and is stuck in a bootloop. I can only let it loop until it dies a few hours later but moment I try to boot it into anything the loop starts again. Already RMAd. Thanks for help though
[Nexus 6P Original Android Development] franciscofranco:
Busybox is completely unrelated to FKUpdater and you only need root access.

That's a coincidence, time not updating is caused by Aggressive Doze. Or maybe the rom you're using has different Doze parameters that are ducking you. If you're on stock then I suggest you to disable Aggressive Doze, it might not be working correctly for you.

You're ducking welcome.

Then you seriously have a big problem with your device that goes beyond Kernel flashing. Good luck, glad you got it RMA'd!
[Nexus 6P Original Android Development] marcus4004:
2 in part.

Could you incorporate the ability for the user to choose their SU version in FKU(or auto detect) ? FKU then downloads the respective SU and then flashes automatically the correct version after the Kernel has been flashed? Allows for an automated process with the security of no bootloops - although more legwork on your end.
[Nexus 6P Original Android Development] carlylemiii:
That's what I was saying, it seems like coincidence. The thing is, my ROM is stock and Aggressive Doze DOES work correctly with SuperSU 2.65 and R4, but not with R5. And in your Naptime app, I have changed zero settings besides enabling Aggressive Doze. Any other ideas why things would be funky with R5, even if not actually /caused/ by it?
[Nexus 6P Original Android Development] franciscofranco:
It's just a coincidence, and a one-time occurrence I'm sure.
[Nexus 6P Original Android Development] inimaitimepass:
Hey Francis,

This is the follow up of the UHD video recording issue. Device setup: Stock ROM, stock kernel, rooted, de-bloated.

Looks like google has put some limits on UHD recording. It's 12:55 mins/3.80GB. I've tried recording 3 different videos and the recording automatically stopped on all 3 times at 12:55 mins, file size 3.80 GB.

But I still wonder why it failed at 10:32 and 8:35 with r4.

Gonna try r4 and r5 tonight. Can you please advice how to fetch logs in case of issues?
[Nexus 6P Original Android Development] mgear356:
[MENTION=3292224]franciscofranco[/MENTION] bro do let me know on how can I help.. Cause its not fair for you to play the game.. Might as well I help you test out any ideas or beta kernel.

Or do let me know if u need any more logs
[Nexus 6P Original Android Development] Rahulrulez:
I am still on r4. The sleep time or idle battery life is great with it. However when I start using the phone, I find little aggressive drain than earlier it was with stock.

Any reason? Don't see any wakelock triggering it
[Nexus 6P Original Android Development] agjdsouza:
Call me crazy but only change I made was going from r4 to r5 and my SOT has jumped from 5 hours to nearly 9 with the same usage. Must be some sort of fluke but while it lasts, praise Franco!
[Nexus 6P Original Android Development] JazzMozz:
Maybe slight OT but how did you get GSAM to work on Marshmallow/Nexus 6P? For all I know is that the dev is still working on a version that is compatible.

Verstuurd vanaf mijn Nexus 6P met Tapatalk
[Nexus 6P Original Android Development] Rahulrulez:
I have no idea. :eek: :rolleyes: :rolleyes: I just downloaded it from play store.. it works :P
[Nexus 6P Original Android Development] Christopher.J.M:
Don't care for benchmarks but, after a cold boot and 10 minutes left aside scores were unusually low. Single core - 1033 Multi core - 3446. Stock with R5 kernel.
[Nexus 6P Original Android Development] EarlZ:
How do you guys tell that doze is not working
[Nexus 6P Original Android Development] NuLLV01D:
By checking the battery graph whether it shows parallel lines to the x axis
[Nexus 6P Original Android Development] redbullman:
Is it me or tap 2 wake doesn't work at the moment? I can't activate it.
[Nexus 6P Original Android Development] EarlZ:
If thats the basis then my note 3 has doze on 5.0 too :p
[Nexus 6P Original Android Development] Gytole:
That's not new, the 4K limit was 5 minites on all devices in the past. It is hardware limitations due to heat. It most likely ran warmer because you were just playing a game or rexording previously and it stopped at 10 minutes due to heat.

Why not just record at 1080p? 4K is kindy a waste of space.
[Nexus 6P Original Android Development] troyolson92:
help with reboots

could someone please look at ligcats I'm having major reboot issues after r5 update. thank you very much.
[Nexus 6P Original Android Development] x.Orville.x:
Question i am in other kernel i can flash this one without problem?
[Nexus 6P Original Android Development] nathanchance:
Logcat does nothing for a kernel caused reboot. Need to grab the contents of the /sys/fs/pstore folder.

Yes, this is a complete kernel package.
[Nexus 6P Original Android Development] troyolson92:
random reboots pstore log

thank you for your help with reboots...
[Nexus 6P Original Android Development] inimaitimepass:
Not a gamer. Not even a single game installed in my phone.

May be right for the second time coz I tried recording again within few minutes after it FC'd.

But for the first time FC, there was no major usage till then.

Heat was the most probable cause I guess. But with stock kernel, even after 3 back to back UHD recordings for almost 45 mins continuously, no heat felt at all.

BTW, using r5 now and looks like it is okay. Will check recording back to back to see if heat is the real culprit.

4k is better than 1080p, OCD may be?!!! :D
[Nexus 6P Original Android Development] nigne:
Have stock settings or have u change anything?:)

Skickat från min Nexus 6P via Tapatalk
[Nexus 6P Original Android Development] pratik_vartak:
Someone please upload newer superSU which works with kernal.. Plz
[Nexus 6P Original Android Development] igalmarino:
http://xdaforums.com/showthread.php?t=3219344

Sent from my Nexus 6P
[Nexus 6P Original Android Development] kauemelhado:
Running Cataclysm + FK r5 + SU 2.63 like a b055.

You're ducking awesome franco ! xD
[Nexus 6P Original Android Development] Gytole:
Hahaha I meant the heat of the EMMC5.0 not the processor. I:m willing to bet it was not ocnarF's kernel but something that had heated up the disk prior.

Oh wellll...lol I still don't get 4K...hahaha
[Nexus 6P Original Android Development] franciscofranco:
Nice to know about that limit :)

I'm doing all I can. I'm not working 24/7 on this Kernel, I have other devices and apps to work on so I can't be pushing tests all the time. I'll keep searching.

Well, there's not much more I can do to improve screen on time. Maybe your usage is simply aggressive enough to make it use higher freqs or you have a lot of threads/processes being migrated to/from big cluster. I can't really pinpoint it like this...

#praiseFranco

I'll guess, cpu7 and cpu6 are offline because you're low on battery.

Magical and psychical deduction.

Double tap to wake is not supported officially by Google - it's there, but it's finicky. You gotta live with it if you want to use it.

Ok, I saw a lot of "msm_rng:Data not available!" I've saw that being spammed on 100% stock device as well, I have no idea why that's being spammed, but hwrng crashed the device after a while. Are you on 100% stock rom?

This is not a ****ing tech support forum for lazy people. There's a SuperSu thread, search it.

#praiseFranco
[Nexus 6P Original Android Development] Tehpdub:
[MENTION=3292224]franciscofranco[/MENTION] I like how you're so brutally honest. lol
[Nexus 6P Original Android Development] mystertom101:
Is this compatible with this kernel?

http://xdaforums.com/nexus-6/themes-apps/viper4android-t2952137
[Nexus 6P Original Android Development] franciscofranco:
And you don't know the half of it, but sometimes I have problems in real life because of that :)
[Nexus 6P Original Android Development] mystertom101:
How do I get it to replace stock equaliser in Spotify? Because right now I can't actually use it
[Nexus 6P Original Android Development] franciscofranco:
Dunno, that's for you to figure out.
[Nexus 6P Original Android Development] chikimonke:
If I'm not mistaken 3.80GB is the limit for 32bit systems/apps? Is it possible that the camera app isn't running as a 64bit app and therefore can only utilize 3.80GB of space or something weird like that?
[Nexus 6P Original Android Development] troyolson92:
franco could the msm_rng messages be adware blocker or layers? other than that i only have the typical root apps, titanium, tasker, and google apps plus only about 10 other apps i use. i run very minimal apps.
[Nexus 6P Original Android Development] franciscofranco:
I have no ducking idea on both of the posts questions [emoji36]
[Nexus 6P Original Android Development] Ofthecats:
Isn't rng random number generator? Low entropy?
[Nexus 6P Original Android Development] Tzfardaya:
Franco allows the cpu to sit longer at higher freqs before throttling, this allows short tasks to finish quicker and longer idle times, but it also means if you're running a heavy process, the battery drains faster than stock and the phone heats up more...

Oh, sweetie, you haven't seen anything yet... He's still holding back...
[Nexus 6P Original Android Development] chikimonke:
Wasn't so much a question for you but rather me thinking aloud and throwing it out there for anyone.
[Nexus 6P Original Android Development] Casyis:
I'm seeing FKU in battery stats under Process even though I'm not using app profiles. Can't say I'm perceiving any abnormal drain, though. I just noticed this, so I couldn't tell you if it was always there or started recently. Anything I should do?

Edit: I did reboot while charging and it persists. Will try a fresh installation of the app.

https://drive.google.com/file/d/0B-GQrtMAjZH8cU0xVlR0bkVBdGM/view?usp=docslist_api
[Nexus 6P Original Android Development] Ryanscobberwash:
You say you're not using app profiles but have you disabled the process in the fku app settings? :)
[Nexus 6P Original Android Development] Casyis:
That must have been it. It is disabled now but I must have accidentally ticked it before. Doh.
[Nexus 6P Original Android Development] Ryanscobberwash:
Haha that's good! glad you fixed it! :)
[Nexus 6P Original Android Development] Casyis:
Yeah, just me going too fast. Thanks.
[Nexus 6P Original Android Development] franciscofranco:
That's just showing that you've been using the app, therefore it appears on the list since it has a nice slice of usage time on your battery cycle. Not a problem.
[Nexus 6P Original Android Development] Casyis:
Thanks, was basically what I was thinking at first. R5 is great, by the way. Had a fifteen minute phone call, casted Plex for the same amount of time, sent a few texts and replied to some XDA stuff before I broke 100%. That was with Android Wear connected and Wi-Fi running the whole time. I know stats can be somewhat inaccurate at a high charge, but still was very happy.
[Nexus 6P Original Android Development] franciscofranco:
#praiseFranco
[Nexus 6P Original Android Development] mgear356:
#praiseFranco :)
[Nexus 6P Original Android Development] badboy47:
Buttery smooth! Thanks.
[Nexus 6P Original Android Development] redbullman:
Is there any reason why I CAN enable double tap to wake via the kernel auditor app, but not directly in the franco paid app? Once enabled in auditor, it then says enabled in Franco, but this is the only way to enable it. Thanks.
[Nexus 6P Original Android Development] leekslk:
[MENTION=3292224]franciscofranco[/MENTION] not sure if the fingerprint sensor is the same as those on the other Huawei(s). Any chance to explore if we could use it to scroll in different applications. (basically a separate fingerprint gesture module if you'll feel fit) Ignore the question if it has nothing to do with the kernel. Sorry.
[Nexus 6P Original Android Development] mgear356:
[MENTION=3292224]franciscofranco[/MENTION] did some tests on my end with future fight with R5 chroma 10 dec rom

Tried the following and it still ends up hanging. can be within a min or can last up to 30mins before it freeze

- set min big cluster speed to 633mhz

- lowered max and min big cluster speed to 384mhz

- set gpu to 180mhz

- changed from cfq to deadline

hope this helps :)
[Nexus 6P Original Android Development] Phazmos:
Cpu frequencies seem bass ackwards - you get hangs/freezes and limit the cpu. That makes no sense.

PS - also running chroma and tried this game for a couple hours on 2 days - didn't have any trouble.
[Nexus 6P Original Android Development] kagevazquez:
This is what I've been thinking about for some time lol it would be awesome to scroll with the fingerprint sensor
[Nexus 6P Original Android Development] franciscofranco:
I can enable double tap to wake on FKUpdater just fine. Make sure you're on the latest 14.0.1 release.

I don't know anything about the fingerprint stack, sorry.

Can you backup your rom, then flash stock 6.0.1, flash FK and try it out?
[Nexus 6P Original Android Development] troymz1:
Does anyone else get stupid google play services drain? Some days is fine, but other days it drains more than my screen. And I can't figure out why.
[Nexus 6P Original Android Development] franciscofranco:
Because Google is giving you the middle finger. It's annoying, so I understand your frustration.
[Nexus 6P Original Android Development] bhughes3:
Seeing some strange things after installing R5 with SuperSU 2.65. In FKUpdater, Haptic Vibration and DT2W not sticking after reboot, and also, SU file came back in /system/xbin folder so I had to delete it again in order to pass SafetyNet checks. Is anyone else seeing these issues?
[Nexus 6P Original Android Development] franciscofranco:
SuperSu is completely agnostic to FK and FKUpdater.
[Nexus 6P Original Android Development] heleos:
You're ticking the button next to the vib and dt2w to persist on boot right?
[Nexus 6P Original Android Development] bhughes3:
Yup. Screenshots of before and after reboot below. This is on Chroma.
[Nexus 6P Original Android Development] bhughes3:
One more
[Nexus 6P Original Android Development] heleos:
Are you doing systemless root? Did you add the "SYSTEMLESS=true" to your /data/.supersu file?

My /system/xbin folder is completely empty, it looks like your busybox installed there. There should be an option to install to /su/bin
[Nexus 6P Original Android Development] bhughes3:
flashed back to r3, SuperSU 2.61 and su is gone from /system/xbin/ after reboot, so pretty sure that was due to SuperSU 2.65 which breaks SafetyNet check. This setup was working fine for me, just wanted to try updating to the latest version of each. Still not seeing the Haptic vibration of DT2W sticking in FKUpdater app after reboot though.
[Nexus 6P Original Android Development] Brembo109:
I checked mine out of curiosity and it went back to 33 after a reboot too. I'm on stock 6.0.1, R5 and 2.65. Didn't change a thing since R5 came out.

Edit: Made a second reboot and it sticked. Maybe ignore my post, can't 100% confirm it was set to 60 before the first reboot.

Gesendet von meinem Nexus 6P mit Tapatalk
[Nexus 6P Original Android Development] Franzie3:
I've had issues where dt2w disables itself after a few reboots.... Very weird...

More important... Maybe anyone can help if not I can grabs logs for you [MENTION=3292224]franciscofranco[/MENTION]

I have a Huawei watch completely stock. Anytime I get a phone call on my 6p (using r5 with chroma rom) and I answer the phone through wat h or normally. After about 30-60 seconds the call disconnects. Any ideas??
[Nexus 6P Original Android Development] pospower:
How do I change roms. After I switched to Franco. Each time I changed roms. I had to go back to stock and re root. It would just boot loop.
[Nexus 6P Original Android Development] frost_nz:
Have you read everything in the OP?
[Nexus 6P Original Android Development] mgear356:
actually these 4 scenarios are set and revert to default before trying out the next.

since u are on chroma, can u help try to run the game for like 3hrs non stop? i.e. playing various stages? So far I have experience 1-2hrs non stop no hangs/freeze but at times, it can hang within within 30mins..
[Nexus 6P Original Android Development] franciscofranco:
Since Lollipop there's a weird behaviour with the boot sequence. We rely on a broadcast called BOOT_COMPLETED, but if you do a hard reboot (such as calling adb reboot, or something that's not a normal reboot) for some reason BOOT_COMPLETED doesn't always show up, which then ****s how we re-apply those settings. And you can't call a normal reboot because only System apps can do it. Maybe there's a way around it, I'll research.
[Nexus 6P Original Android Development] Phazmos:
Sorry, but I have no interest running that game - for any length of time. I don't find it interesting enough to run that long, and besides, I didn't have any trouble with it when I did test it. So, no problem, no need for further testing.

Right now - too many variables to even try and help.

Good luck!
[Nexus 6P Original Android Development] pospower:
Can you help a brother out its been a long year what did I miss. Thus thread is 1200 plus posted.
[Nexus 6P Original Android Development] largeselection:
Might this ever make it over to the nexus 5x? I've been a supporter and user anytime I had a phone that had this as an option and they have always been great!
[Nexus 6P Original Android Development] nathanchance:
He just posted today on G+ he got the Nexus 5X so yes, soon.
[Nexus 6P Original Android Development] Nocturnal86:
I stand corrected! didnt see that^^^

He's said no because he doesn't use the device or want to spend money or time on a device that he won't use. He even tried to pool money to buy the device from interested parties and couldn't reach a third of the cost of the device. So clearly not enough people are interested or if they are are not willing to pay for his work or time or a device to work on.
[Nexus 6P Original Android Development] franciscofranco:
What do you need to know exactly? I think everything you need to know is in the first post.