yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] haibane:
http://xdaforums.com/showthread.php?t=2868133

Make sure you are using that version of SuperSU also as old versions won't work. Don't let twrp install SuperSU either.
[Nexus 6  Original Android Development] dansan382:
thats the supersu file i flashed. thought i didn't need the boot image if i used a correct kernel. okay time to find this boot image then.
[Nexus 6  Original Android Development] TonikJDK:
You also will need to uninstall some apps from system. MM doesn't leave enough free space in system for the hosts file. I used TB to remove Books and News...both of which can be added back from the store if you want.
[Nexus 6  Original Android Development] haibane:
Boot.img shouldn't be needed, but its worth trying. It's on that thread last I checked
[Nexus 6  Original Android Development] dansan382:
ahh good to know. guess ill play around. everything seems to work, root wise. not sure if I needed to allow TWRP do whatever it asked me originally.
[Nexus 6  Original Android Development] dansan382:
sorry for the double post.

purchased the app, cant seem to get double tap to work. I have it ticked, see photo. I rebooted and nothing. anyone else having issues? I saw some people having problems but they were on like r31 or r32
[Nexus 6  Original Android Development] Tzfardaya:
Touch the label to switch the "disabled" to "enabled" under the "double tap to wake"... You've flipped the set on boot toggle.
[Nexus 6  Original Android Development] dansan382:
pure genius.. thanks so much guys for the help.
[Nexus 6  Original Android Development] Mercado_Negro:
[MENTION=3347759]dansan382[/MENTION] just a FYI, you don't need to flash Chainfire's boot image if you're coming from a pure stock setup. Franco.kernel has all the necessary ramdisk changes (not for systemless root, though). As long as you flash the latest franco.kernel version and SuperSU 2.52 everything should work just fine. Btw, as others mentioned, your problem installing the apps was caused by the lack of space in the system partition. Uninstalling a few system apps will get you some free space back. Also, the TWRP message you saw was just an optional system partition modification. It doesn't matter if you kept it read only or allowed the modification.
[Nexus 6  Original Android Development] dansan382:
yea i ended up figuring that out about not needing the boot image, same with the lack of space thanks to others who posted. thanks for the heads up though. setup is running great right now, battery life seems solid and im still pounding the phone setting it up and everything. haven't touched a single setting, dont really plan on it.

just out of curiosity, how does one change that TWRP message about the system partition? i tried digging through recovery, couldnt see it
[Nexus 6  Original Android Development] Mercado_Negro:
You can't change it back to read-only once you've allowed the modification. Don't sweat it, though. The worst scenario is you won't probably be able to update your device via OTA.
[Nexus 6  Original Android Development] dansan382:
i actually set it to read only when it popped up. when OTA's come in (at least when i was on LP) i just reflashed stock /system, reboot and let it take the OTA then reroot it. still going to have to do it that way since i touched the /system partition with root and moving things.
[Nexus 6  Original Android Development] j4rp0:
Anyone??
[Nexus 6  Original Android Development] LeonDX82:
I tried it once and I think the radio did not switch to 4g tower after leaving my works WiFi area, it stayed on 3gg

I only disable the firs 2 wakelocks in the app
[Nexus 6  Original Android Development] sjgore:
Yes, there seems to be critically low space on the system partition after flashing the third and latest factory image for the Nexus 6 (MRA58R). To root and use this kernel together with SuperSU, I did the following with Wug's NRT:

1. Flashed the Marshmallow factory image.

2. Booted into TWRP temporary recovery, and flashed permenant TWRP recovery, SuperSU 2.52 Beta, and Franco Kernel.

3. When booting into Android, when prompted to update SuperSU binaries I chose the "TWRP/CWM" method, as the "Normal" method won't work.

4. After binaries are installed in recovery, after booting back into Android I removed a load of apps and keyboards that I don't use.

5. There is now room on the system partition, and apps like Adaway can now install things without throwing up error messages like "No room on system partition".

Actually, just realised this probably isn't particularly related to Franco's Kernel, and is more of a general Nexus 6 Marshmallow rootimg issue, so apologies if so.
[Nexus 6  Original Android Development] jtwebfusion:
To make room in the system partition, delete any foreign language keyboard that you don't need...
[Nexus 6  Original Android Development] TransportedMan:
Evolvere. Its basically Z3/Z5 everything ported over to Nexus 6.
[Nexus 6  Original Android Development] nikeman513:
Why is minimum cpu stuck at 1497? I change it to 300Mhz and it just goes back.
[Nexus 6  Original Android Development] suku_patel_22:
Arghh. Explained thousands of times in this thread. Open system monitor and look at the CPU frequencies for 2 mins .

That's touch boost for you.
[Nexus 6  Original Android Development] NLBeev:
'thousands of' = 'several'
[Nexus 6  Original Android Development] suku_patel_22:
Save me, grammar nazi is here...
[Nexus 6  Original Android Development] NLBeev:
Exaggerated again.
[Nexus 6  Original Android Development] rignfool:
At 714 pages... With mention on every page at least twice...

Thousands was more appropriate...

I am however amazed at how people would take an expensive device and just 'flash' stuff on it without reading...
[Nexus 6  Original Android Development] holeindalip:
With the 6 being so cheap we have a lot more noobs coming in, going to be a lot more incoming
[Nexus 6  Original Android Development] NLBeev:
Already regretting to be OT. But suku....got the message.
[Nexus 6  Original Android Development] provolinoo:
is the warning real (I mean system space is too less for real) or is it something related to boot.img modification?
[Nexus 6  Original Android Development] TonikJDK:
Its real, stock rooted will do the same.
[Nexus 6  Original Android Development] provolinoo:
It sounds kinda weird Google released an official system image that doesn't "fit" properly in the device partition :confused:
[Nexus 6  Original Android Development] TonikJDK:
It fits fine as they intend it to work. It is a bit of a security feature to keep bad apps from writing to system.
[Nexus 6  Original Android Development] a63548:
I had flashed the latest 6.0_r26 [MDB08M] Chroma 11/08/2015r2 build along with r34, and had issues with a constant LED and strange battery percentages. It seems that it has to do with what was posted here. Just wanted to see if you knew about it and if it could be something that might be able to be fixed in a later release.

Also, just wanted to say thank you for such an awesome kernel! It is truly one of the reasons I got this phone originally, knowing that your kernel would be here.
[Nexus 6  Original Android Development] TR2N:
Hi Franco,

i am a little bit confused about the current "Security Update" situation and your kernel. I have read somewhere, that the MRA58R / MRA48N kernel changed / got updatet in comparsion to MRA58K. Is it OK to use the r34 kernel with MRA58R or MRA48N (i am currently on MR58N that i have sideloaded)? So far no problems here, but i am asking just for info and to be on the "safe side".

Thank you!
[Nexus 6  Original Android Development] dansan382:
I'm on MRA58R and rocking r34 kernel. no issues here.
[Nexus 6  Original Android Development] haibane:
Same here
[Nexus 6  Original Android Development] PCWright86:
On MDB08M, r34 causes some weird things. Battery reading in the thousands is the main thing I noticed.
[Nexus 6  Original Android Development] HueyT:
It's not R34, it's Chainfire's modified boot.img. Install stock boot.img and should fix it. Chroma's dev noted that in other forum.
[Nexus 6  Original Android Development] hlxanthus:
No, but it is an incompatibility with ROMs built with aosp 6.0 r26. I know chroma, octos, and pure nexus all have issues with the current release of Franco kernel.
[Nexus 6  Original Android Development] :
I'm on Pure Nexus rom MDB08M and have this same thing.

Thing is I never flashed chainfires boot image just r34 over the stock kernel that was already in rom unless Beans used it.. Gonna flash stock kernel then back to r34 and see if it fixes this. VERY annoying!! I have 3,786% battery. lol. Will report back in a few.

Edit

Apparently it's something with latest Aosp.. I couldn't stand looking at it so I went back to stock kernel. Will return soon as its true. My ocd is full blast. :o
[Nexus 6  Original Android Development] Prack:
3,786% battery is the magic that franco puts in the kernel though!
[Nexus 6  Original Android Development] withoutme5:
The led stays always on with chroma :(
[Nexus 6  Original Android Development] ben_pyett:
None of these issues exist with cataclysm and Franco, just saying.
[Nexus 6  Original Android Development] Stigga:
I am on mra58k and rooted last night through Wugfresh - can I flash r34 through the franco updater or has the process changed with Marshmallow? Thanks!
[Nexus 6  Original Android Development] haibane:
You're good to just use the app. I highly recommend learning how to use and in the future as I have found wugfresh to install a not so ideal version of roms etc..., but it works well if you don't know what you are doing.
[Nexus 6  Original Android Development] Stigga:
Thanks I will flash it now. What do you mean "I highly recommend learning how to use and in the future" ?
[Nexus 6  Original Android Development] haibane:
Whoops. I meant for that to be adb. Autocorrect won.
[Nexus 6  Original Android Development] Stigga:
lol - makes much more sense now
[Nexus 6  Original Android Development] pkgnex:
I just flashed stock MRA58R and Franco r34, and no issues with that combo, either.

It's a ROM issue.
[Nexus 6  Original Android Development] withoutme5:
Because cataclysm is different compilation.
[Nexus 6  Original Android Development] :
From what i have read it only happens on roms built with latest Aosp like Chroma and Pure Nex.
[Nexus 6  Original Android Development] Stigga:
Great color settings!
[Nexus 6  Original Android Development] yamahakid:
So I've noticed that a lot of the random reboots (unable to wake from lock, followed by a soft reboot) are happening when my battery is on the lower end. I'm guessing it is somehow related to the kernel throttling the cpu down (it does that... Right?) . It's weird that it doesn't happen all the time though, but it is consistently when the battery is low, when it is happening.

I'm off today so I'll attempt to pull a log if it happens today (also, where are the logs located)
[Nexus 6  Original Android Development] haibane:
What rom are you on? I haven't experienced these issues so I wonder if it is a rom.
[Nexus 6  Original Android Development] yamahakid:
I'm stock, rooted.
[Nexus 6  Original Android Development] hlxanthus:
/sys/fs/pstore/console-ramoops
[Nexus 6  Original Android Development] yamahakid:
Just found 2 logs in there that seem to be from earlier today. What's the best way to post them?
[Nexus 6  Original Android Development] dansan382:
not sure what format they are in but if not already in a .txt format just paste them into a text doc and attach the files
[Nexus 6  Original Android Development] yamahakid:
here is what i was able to pull from yesterday. I have absolutely no idea what I am looking for in these, so if someone finds something could you tell me what it is, so that I can start to get an idea of what I would be looking for. Thanks.
[Nexus 6  Original Android Development] PCWright86:
Will the next release have compatibility with AOSP MBD08M ROMs. I really like running Franco kernel. Battery life and performance from this kernel are amazing.
[Nexus 6  Original Android Development] haibane:
PCWright,

I am not sure why the current version wouldn't work with AOSP MBD08M... Is there a different bootloader or something?
[Nexus 6  Original Android Development] Steve Lazarus:
Kernel just needs updated... You'll get weird battery % in status bar, example .9830%.. Also DTTW issues and waking from sleep... Takes multiple attempts to get the screen to come on using power button. Just a couple of things I've experienced.... I'm sure Franco's all fu**ing over it..[emoji12]
[Nexus 6  Original Android Development] haibane:
Well it sounds like you would almost have to make a Kernel for the Roms where that is an issue that is separate.

Seems like it would make more sense for the Rom to fix the issue on their side. Maybe I am misunderstanding it, but if there is a change to fix this for AOSP, then it won't work for the ones that already worked.
[Nexus 6  Original Android Development] ghostspectrum:
I've been running into issues lately despite not changing anything on my phone. Complete llock ups and hard and soft reboots. And I'm on stock ROM.
[Nexus 6  Original Android Development] haibane:
Can you pull a log of these issues? Have you tried doing a clean wipe and reinstall? I am running stock without any lock ups or reboots.
[Nexus 6  Original Android Development] ghostspectrum:
Where would I go for these logs? And when you say wipe as in wipe the entire phone?
[Nexus 6  Original Android Development] PCWright86:
It is not the ROM. It is the latest aosp update not mixing with the kernel. Hence the reason for updates on both kernels and ROM that periodically happen. When google changes things, kernel and ROM developers have to change things.
[Nexus 6  Original Android Development] yamahakid:
I posted about the same issue yesterday, and Im also stock. I posted my logs just hoping someone can take a look at them.

Surprisingly enough, I didn't have a single issue yesterday, and ran my phone all the way down to about 5%
[Nexus 6  Original Android Development] TR2N:
Hi Franco,

would you provide a test kernel with Chainfires systemless root method included? What do you think about it?

Kindly regards
[Nexus 6  Original Android Development] bensl84:
This is probably the worst place for this request/idea, so bare with me. I love all your apps. Have used them on all my nexus devices.

But I was wondering. Since Google fi is out and it's only for nexus devices, could you make an app that tells us what cell tower we are on and force switch towers and reset apn settings ect.

Also my personal request would be a setting that forces the jump to tmoble if we get a call or are on a call so we can have voice over lte.

That would be amazing. Again I'm sure this is the wrong place so let me know if I should post this somewhere else.

Thanks
[Nexus 6  Original Android Development] dansan382:
I've had some "issues" with it taking a second to wake up from sleep but never had a soft reboot. I'm on stock ROM as well. kernel flash was done right after i factory reset the phone and set it up. I have yet to have a soft reboot but sometimes I've noticed i have to give the phone a second or two to wake up.

I checked my logs, the pmsg-ramoops-0 file is filled with lines from the Lightflow app which is crazy. No idea what any of it means. I am also getting a slight hiccup in apps too, where it pauses for a second. you can definitely notice it in apps like facebook or IG when scrolling, it seems to become unresponsive for a second then kick in.'

Been also having a problem where I wasn't getting text messages until I did a reboot which was so strange. I cannot tell if I had that issue before flashing kernel or not as I did the kernel flash right off the bat. No idea if the two are related at all
[Nexus 6  Original Android Development] ghostspectrum:
I've been having the not receiving text problem the past couple days. Could all this really be light flow?
[Nexus 6  Original Android Development] dansan382:
I don't know how Light Flow would have any effect on not receiving texts. Maybe not getting a notification, but the texts weren't received at all. If anything, this is my first issue im having with light flow. been using the same version for awhile now, after an update broke all my settings I turned off the auto update for it. Didn't notice any of these "glitches" until I came to MM and this kernel so i have 2 variables which makes it hard for me to narrow down which did it.
[Nexus 6  Original Android Development] ghostspectrum:
Suddenly the camera doesn't function...
[Nexus 6  Original Android Development] JNewms:
OK? No details, no logs... How is anyone supposed to help you?
[Nexus 6  Original Android Development] wrongway213:
http://xdaforums.com/android/software-hacking/vomertweaks-perfect-balance-performance-t2873369
[Nexus 6  Original Android Development] kmaner:
Awesome. Thank you!
[Nexus 6  Original Android Development] franciscofranco:
Try the Power saver profile, it bends the device to its knees if you absolutely need battery life in expense of performance.
[Nexus 6  Original Android Development] kmaner:
I think I am really after the balanced attack. I just loaded r4 earlier and will stick to the balanced for a few days...I am going to flash VT as well I suppose.

Thanks
[Nexus 6  Original Android Development] old_fart:
I put it on 'power saver' and ran epic citadel and got 52 fps ( beautiful and smooth ). . And then I put it on 'performance' mode and got 59 fps ( same beautiful and smooth - my eye balls could not tell any difference ! ) . And so I am asking if you could make four settings where their be only 'one' cpu a huffing and a puffing ? ? ? . Hmm ?
[Nexus 6  Original Android Development] cobyman7035:
Can any1 run ? here beta maps with no lag? When u scroll the maps… plz confirm or not.. I think I will flash franco plus vomer… rip elementalx

Via my NeXus™ 7FHD on XDA Premium app
[Nexus 6  Original Android Development] suku_patel_22:
Was checking out powersave today. Why is there a difference between FKU and CPU Spy/BBS?
[Nexus 6  Original Android Development] 5FOOTER:
Times are different. One looks like on for over 5 mins the other only 13 secs.
[Nexus 6  Original Android Development] suku_patel_22:
What i intended to say is that, FKU states that max and min clock are 1036 Mhz, while it actually hits all frequencies up to 1036 Mhz.

What is the correct behaviourr of power saver mode?
[Nexus 6  Original Android Development] muntain:
Stock kernel + r4 very good behaviour
[Nexus 6  Original Android Development] Jeremy:
How do you have both stock kernel and franco...?
[Nexus 6  Original Android Development] muntain:
No I mean stock lollipop + franco kernel sorry ;)
[Nexus 6  Original Android Development] Anonymouze:
I'm using MyAndroidTools. You can find this app on Google Play. In the Servicesection off this app you have to swype to System and search for the Google Play Services. There you can find an turn off the "NlpLocationReceiverService"

This Service gives me high wakelocks. Im new to "disable service" so you will do this on your own risk.
[Nexus 6  Original Android Development] franciscofranco:
Nope, there are no benefits in running only 1 core on this chip.

I'll say once more. 1036MHz as min only happens for 80ms. When you click the CPU Manager tab min gets bumped to 1GHz (touchboost) and my code reads min as in 1GHz, but then it goes down to 300MHz again 80ms later (0.08s). Do I really need to make a fake min_freq hook so that people stop asking about it? I made a fake one before for the N5, nobody knew it, nobody asked anymore! :)
[Nexus 6  Original Android Development] bills742:
I'm waking up to a phone that turns itself off after leaving it on the wireless charger overnight, anyone else? Pretty sure it's kernel related because I haven't switched ROMs in a while and this is the first time experiencing it.
[Nexus 6  Original Android Development] franciscofranco:
There are absolutely no changes at all on anything related to wireless charging or charging in particular, it's 100% equal to stock.
[Nexus 6  Original Android Development] rsa 329:
No issues of the kind here. Just took it off the charger.
[Nexus 6  Original Android Development] elijahah:
Hotplug cores

Are the 3rd and 4th core supposed to turn off? My 3rd and 4th core are always on, even when at 0% load.
[Nexus 6  Original Android Development] franciscofranco:
Doesn't seem like there's 0% load, you see both bores at 2GHz. The driver is functioning correctly, either there's load or you set the threshold to a really low value.
[Nexus 6  Original Android Development] lionelhuts:
Franco, thanks for bringing your stuff to the Shamu.

On my Galaxy Nexus, your kernel included the Battery Life eXtender (BLX) mod from Ezekeel. (This would prevent the battery from being charged over a user defined percentage). Any plans to bring this to the N6?
[Nexus 6  Original Android Development] Tylog:
A update with systemless root method would be nice yes. For now with most roms in combination with FK no battery stats available, that's a problem.
[Nexus 6  Original Android Development] ghostspectrum:
Sorry im not sure how to pull those logs, that was just a quick post while I was at work. Tried to send a message with Textra and tried to take a picture through the app itself, and only got black. Exited and tried the camera app, first got an error, and then only black screens.
[Nexus 6  Original Android Development] JNewms:
What ROM are you running?
[Nexus 6  Original Android Development] ghostspectrum:
Stock ROM since day one.

---------- Post added at 03:36 PM ---------- Previous post was at 03:29 PM ----------

Is it last_log in recovery?

https://docs.google.com/document/d/...Q1STrkPapUK2ryatZiFqnAU/edit?usp=docslist_api
[Nexus 6  Original Android Development] ben_pyett:
You'll need to name roms and give examples as everything running and battery stats working fine with stock based roms, well mine is anyway.
[Nexus 6  Original Android Development] PCWright86:
MBD08M based roms
[Nexus 6  Original Android Development] ghostspectrum:
Huh. So I uninstalled Light Flow and I'm noticing am immediate performance and stability boost...
[Nexus 6  Original Android Development] ben_pyett:
Hmmm, I'm afraid this is difficult to believe, sounds more like placebo or the change was caused by something else and was unrelated to LF.

I've personally used the application for many years without issues with FK and read many of the Nexus device (N4, N5 & N6) LF specific threads and have never read any evidence to back that... Even anecdotal.

What change in stability did you see?
[Nexus 6  Original Android Development] ghostspectrum:
It very well may be unrelated but I know what you mean. I've been using the app for years without issue. Though lately they've updated and there's a problem with the app that forces a persistent notification (something I'd disable if allowed) and the update of the app almost perfectly coincides with my own personal drop in stability.

Lately it's almost become a chore to use my phone, with almost constant lock screen locks (unable to unlock with power button), unresponsive screen, soft reboots, hard reboots, inconsistent locking ( hit power to turn screen off, screen turns off but never locks like it should) and general slow and sluggish phone usage.

That's all gone now. Obviously I'll need to test further but just throwing this out there. App updates are the only thing to have changed on my phone since my stability nose dived, and Light Flow is one of the only system Root requiring apps I use.
[Nexus 6  Original Android Development] ben_pyett:
I'll agree that the persistent notification is an issue, and I believe that the dev is working on trying to address this, but I'd certainly question whether the stability is related.

Edit seen you're on stock.
[Nexus 6  Original Android Development] ghostspectrum:
Yeah I wouldn't be as suspicious if I was on a custom ROM :-\
[Nexus 6  Original Android Development] sjgore:
I use Lightflow too, with stock MRA58R, and I resolved all the issues you describe by going back from r34 to r33. Have had zero issues since doing so, just like I had zero problems running r33 the first time in the days/weeks that it was the latest version before r34 was released.