yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] deeplyyoung:
Systemless Root working flawlessly with MR
[Nexus 6  Original Android Development] Droidphilev:
Yes, i know (but not flashing to secondary). I posted my findings before in Multirom.
[Nexus 6  Original Android Development] yamahakid:
I am experiencing similar problems, with r35 and SU2.61, however I'm on stock 6.0.1. I was able to pull a log from a reboot I had yesterday and franco said everything looked okay. However last night I experienced the phone getting very hot and battery draining, and the phone froze on me twice in a 30 min period.
[Nexus 6  Original Android Development] haibane:
So I am going to assume the preferred method to get this to work with CM is by using SuperSU from Chainfire for systemless root?

Is there a way to get this working using the built in root on CM?
[Nexus 6  Original Android Development] ben_pyett:
I'm afraid that the issue certainly seems to be FK for me, as since I switched back to stock (cata) kernel first thing this morning I've had zero issues all day, I have now switched onto ElemX to see how that goes and will then jump back into FK so see if it messes up again....
[Nexus 6  Original Android Development] pkgnex:
I had the "hot phone / battery drain" problem for a bit this morning, too. After a reboot it hasn't resurfaced, and of course I didn't get any logs.

On a separate note, when Franco releases r36, what is the new flashing procedure with the systemless root - do I need to flash SuperSu 2.61 to re-modify the ramdisk after flashing the kernel every time I want to install a new kernel or update?
[Nexus 6  Original Android Development] Amos91:
Since flashing factory 6.0.1 (super su2.61) my phone has on three occasions gone completely unresponsive (black screen).

I have to hold the power button for quite a while to force a restart. When the phone comes back on, the clock has reset to something silly like 1am & 30 years ago throwing up all sorts of app errors. This then updates and the phone continues to work fine. As a result of the dates etc I don't think the log cat is working properly.

Running -

Franco Kernel - stock settings apart from vibration, volume & colour change

Xposed Framework - Amplify, GravityBox, Greenify, Snapprefs, Youtube Adaway.
[Nexus 6  Original Android Development] ben_pyett:
It's comforting to know that it wasn't just me and that two other users have suffered the same issues, certainly makes me feel better.

In answer to your question, yes I believe that you'll need to re flash the latest SuperSu zip after each kernel change.
[Nexus 6  Original Android Development] Amos91:
My logcat -

https://paste.ee/p/C7umB
[Nexus 6  Original Android Development] miguelito18:
Well, dunno if this is also kernel related but with supersu 2.61 sim card does not get detected, but with 2.60 all working good
[Nexus 6  Original Android Development] PCWright86:
Woke up this morning after flashing Franco r35 last night. Phone was unresponsive. Charging light was lit but the phone would not turn on. I have a question though, will the new release only work with systemless root. Or does it still work with SuperSU 2.52
[Nexus 6  Original Android Development] pkgnex:
Just had a random reboot on stock Rom with r35 and SuperSU 2.61. Here are the logs:

https://www.dropbox.com/sh/8j0zxv3kmqa7gkf/AAAY1CFaxCCZMFX2Ia_SmiMQa?dl=0
[Nexus 6  Original Android Development] Amos91:
I had a random rebbot too. Will upload the log later.
[Nexus 6  Original Android Development] gee2012:
Nope only with systemless root, not with traditional root.
[Nexus 6  Original Android Development] d u o XIV:
I'm running into the same problems as ben_pyatt and amos91. Set up Cataclysm 6.0.1, SuperSU v2.61, and the latest Franco kernel and went to sleep. At some point during the night, my phone went unresponsive and I missed my alarm (awesome start to the day). I had to hold the power button down for about 10-15 seconds before my phone came back to life. I'm currently running the latest Cataclysm, its stock kernel, and the latest SU to see if it actually is Franco kernel.
[Nexus 6  Original Android Development] MizzouBrent:
Anyone used Bluetooth audio? I flashed the stock factory image and Franco r35 boot image and my Bluetooth audio is crazy loud even at the lowest setting.
[Nexus 6  Original Android Development] twan69666:
You can add me to the list of unresponsive black screens. Also on SuperSU 2.61 and R35. No logs because I decided to look here first, but now I'll be a little more ready
[Nexus 6  Original Android Development] NLBeev:
Did you flash Supersu2.6x as the last file?
[Nexus 6  Original Android Development] Amos91:
Yep, the latest one available at the time.

Just been to the cinema, phone has dropped about 70% battery, really hot and unresponsive

---------- Post added at 10:23 PM ---------- Previous post was at 09:52 PM ----------

Here is a logcat, phone restarted between 16:59 & 17:02.

https://drive.google.com/file/d/0B5nT4tFDASAlb0c4cVhGVXFmb28/view?usp=docslist_api
[Nexus 6  Original Android Development] ben_pyett:
[MENTION=3292224]franciscofranco[/MENTION]

Any thoughts/ideas/feedback on the unfortunate reports from multiple users over the last page who are all experiencing similar problems on the latest iteration of FK #35
[Nexus 6  Original Android Development] ReventonPro:
I'm going to revert back to r34 for the time being. I just flashed and I'm getting bootloops. It never leaves the boot animation. Running Cataclysm 6.0.
[Nexus 6  Original Android Development] JNewms:
That's because the new kernel is only for 6.0.1, like he said. There's a 6.0.1 cataclysm already.
[Nexus 6  Original Android Development] nathanchance:
Installation help

Hey guys, I have seen a lot of posts confused about installation or getting boot loops. If you are anything like me, I like to have a step by step to follow. I tested this on Chroma but it should be applicable to any ROM. Hopefully this isn’t too intrusive or repetitive.

Pre-requisites: be on a 6.0.1 stock/ROM.

Process:

Custom ROM (pre-rooted):

1. Either clean flash your ROM + GApps or dirty flash the ROM zip to eliminate previous custom kernel.

2. Flash UnSU (to remove SuperSU from the system partition).

3. Flash Franco Kernel.

4. Flash SuperSU 2.61.

5. Reboot and profit.

Stock or custom ROM that is not pre-rooted:

1. Flash Franco Kernel.

2. Flash SuperSU 2.61.

3. Reboot and profit.
[Nexus 6  Original Android Development] russlowe73:
So it can be used with any 6.0.1 rom, regardless if using SuperSU 2.6 or 2.52?
[Nexus 6  Original Android Development] nathanchance:
No, you must have 2.61, 2.52 will cause a boot loop. I have a process right above your post if your ROM comes pre-rooted. If you are on stock, you can just flash the kernel then SuperSU 2.61.
[Nexus 6  Original Android Development] russlowe73:
I know how to use 2.61, just don't know if I want to after reading all these posts of problems.
[Nexus 6  Original Android Development] nathanchance:
I have not had a single issue with 2.61 since I started running it a few days ago. I've used it with both ElementalX and this kernel. The majority of problems you have been reading about have been caused by user error. If you follow that process, you will be fine. It is up to you but r35 (6.0.1 release) can't be rooted without 2.61.
[Nexus 6  Original Android Development] tb417:
Absolutely love this kernel. Great battery life, V4A works flawlessly when other kernels wouldn't install driver, and multirom support is built in. Thanks for the awesome work.
[Nexus 6  Original Android Development] chief2842:
Worked Flawless on Chroma for me. I take it we will have to flash it this way each team Zep releases a new update?
[Nexus 6  Original Android Development] Gedablo666:
Hello.

I'm thinking about to come back from Chroma to Stock. I wonder if SELinuxModeChanger will work? I need to change to permissive because I want to restore backup with Titanium Backup and after that change back to enforcing. Yesterday I tried this app on Chroma + Franco + SuperSU 2.61 so its doesn't worked for me. Popup message that phone don't have root or something. So I'm curious if the same will be with Stock + Franco? Maybe it's cousing by SuperSU 2.62?

Thank you.
[Nexus 6  Original Android Development] nathanchance:
Titanium Backup should be able to run in Enforcing, they updated it a while ago. When you flashed this for Chroma, you should have done it in the following order: Chroma, UnSU, Franco, SuperSU 2.61. After that there should be no issues with root. For stock, it would be stock, Franco then SuperSU 2.61.
[Nexus 6  Original Android Development] gharrrrrr:
No random reboots for me. But after installing Chroma 6.0.1, Franco, and SuperSU 2.61 all was fine for about 24hrs. Then I received a notification. Tried to check it. SOD. Had to force reboot. Sounds similar to what others have reported. Busy and can't grab log right now. Will if it happens again. Just had phone in pocket. No other mods or tweaks to kernel.
[Nexus 6  Original Android Development] Chahk:
I have noticed this as well. Not sure if it's the fault of the kernel or 6.0.1. I'm about to revert to stock kernel and re-test.
[Nexus 6  Original Android Development] sjgore:
Have had 3 "black screens of death" (i.e. won't wake up) in the last 12 hours, phone eventually reboots to the "Google" logo and open-padlock symbol after a few minutes of button pressing and waiting. Have also had one reboot when the phone slowed to a crawl for a few minutes and eventually rebooted. Battery was almost full. Am running stock 6.0.1 and SuperSU 2.61.

-EDIT- Just checked, no log files saved.
[Nexus 6  Original Android Development] Chahk:
I reverted to stock (with systemless root) and can confirm that the BT loudness issue exists in stock kernel as well. I can't imagine root could be causing this behavior, so I think this was an issue Google introduced in 6.0.1, because Bluetooth volume was working just fine on 6.0 MRA58R.
[Nexus 6  Original Android Development] mangusZen:
Well, since supersu 2.61 gave me problems with some apps, I flashed 2.52 on top of that and strangely all work fine with last franco kernel and cataclysm 6.01.

Strange but true.

So I probably let 2.61 patch the ramdisk and then revert back to stable system root, if you dont need android pay.
[Nexus 6  Original Android Development] MizzouBrent:
Thank goodness I'm not alone. It's the same way completely bone stock with a factory image flash. Sorry for the OT but what are you connecting with? I have an older set of LG Tones.
[Nexus 6  Original Android Development] SubwayJrd:
I've had 2 of these in the last 24 hours. My phone was VERY hot after the last one (it started making my leg uncomfortable while sitting in my pocket).
[Nexus 6  Original Android Development] Chahk:
Mine is a year-old LG HBS-730.
[Nexus 6  Original Android Development] TR2N:
Also for me r35 is completely useless. Phone went hot and sleeps to death. Using gerars kernel now.
[Nexus 6  Original Android Development] Amos91:
I've temporarily switched to elementalx. Been fine for nearly 24hours.
[Nexus 6  Original Android Development] bautrupp:
I'm back on stock kernel for now.

Had several SODs and sudden reboots lately. No logs, sorry.
[Nexus 6  Original Android Development] justibasa:
I've also had several sod's and a reboot. Luckily I got a log. Hopefully it helps. :)
[Nexus 6  Original Android Development] pkgnex:
Funny thing is for the last day or so I've had no issues at all. I've even tried rebooting a few times just to see if I can get the problems back so I could get more logs for Franco.

So, since the first morning after the flash (where my phone started cooking), and then the reboot later that same day (which I posted logs for), now everything seems fine.

Weird.
[Nexus 6  Original Android Development] ben_pyett:
Unfortunately still seems that additional reports are coming in from multiple users reporting very similar sod, reboots, and super heating /power off symptoms.
[Nexus 6  Original Android Development] Neejay:
Fortunately, I haven't had any issues on tupac4u's debloated 6.0.1 AND xposed, and I've been using r35 almost immediately after it was released.
[Nexus 6  Original Android Development] franciscofranco:
r36 is up. Mostly fixes (LEDs, F2FS, etc). Let me know if the issues you encountered are fixed, I wasn't able to reproduce them so far.

I'll keep a close eye on the thread, if something crazy starts happening I'll try different things.
[Nexus 6  Original Android Development] J:
Thanks for the awesome fùckìng support as always.
[Nexus 6  Original Android Development] pantmunu:
Man, I have seen your work for a very long time and you seem to amaze every god damn time sir , seriously, every god damn time. I am not trying to be a fan boy or anything, I ain't even using ur kernel ATM, but looking at all the pas devices and ur kernels I have used , I have always been a happy camper. Thank you for everything that you provide us and keep being the man you are . and say hi to ur cat.
[Nexus 6  Original Android Development] franciscofranco:
She says hi back! ;)
[Nexus 6  Original Android Development] pantmunu:
Him too !! ??
[Nexus 6  Original Android Development] franciscofranco:
She's in love with him, love at first sight.
[Nexus 6  Original Android Development] pantmunu:
Hahaha. He is a handsome dude. The colors match too. Hmu if u ever visit new York. ☺☺
[Nexus 6  Original Android Development] franciscofranco:
Russian blue? Mine is :)
[Nexus 6  Original Android Development] goinflyn:
R36 is for 6.0.1 only?
[Nexus 6  Original Android Development] hlxanthus:
[MENTION=3292224]franciscofranco[/MENTION] at least for me I cannot turn off the charging led in r36 with fku
[Nexus 6  Original Android Development] pantmunu:
Mine is kinda greyish. Russian blue , heard that name for the first time lol.

Anyhow , about to flash now. ;)

---------- Post added at 06:46 AM ---------- Previous post was at 06:42 AM ----------

Yes.
[Nexus 6  Original Android Development] franciscofranco:
Yes.

Charging-led is disabled by default. You're rooted, right?
[Nexus 6  Original Android Development] Mercado_Negro:
Are you sure it says "disabled" when you touch the option (not the switch, that's for "apply on boot")? I just enabled/disabled that here several times using FKU and it works fine.
[Nexus 6  Original Android Development] NLBeev:
Update of the kernel may cause an issue when systemless root is used (v 2.61 and Lite rom 6.0.1 of Danvdh).

The sim-card is not detected. Can be solved by reflashing SuperSU 2.61.

So fkupdater is not enough when systemless root is used.
[Nexus 6  Original Android Development] Amos91:
Thanks Franco. I've temporarily switched to Elemental so I'll flash the stock boot image, flash yours and the new SuperSU and see if the black screen of death returns.
[Nexus 6  Original Android Development] ben_pyett:
Same here, so will try the same this morning and report back later this evening.
[Nexus 6  Original Android Development] ben_pyett:
[MENTION=3292224]franciscofranco[/MENTION]

Re-flashed the #36 also on supersu v2.62

After a couple of hours, found device screen off, Led still lit, completely unresponsive, wouldn't wake and wouldn't receive a phone call.

Had to two finger reboot.

See attached logs in the hope that you can find something in one of them, not sure how useful.

EDIT

Similar thing occurred a second time, another set of logs attached.
[Nexus 6  Original Android Development] Amos91:
Mine has also soft rebooted (on SuperSu v2.62 this time). Pressed the power button to wake the device and it flicked straight to the Google boot screen. No decent log info unfortunately.

Looks like its back to ElementalX for now.
[Nexus 6  Original Android Development] ben_pyett:
Yep, sadly, similar experience(twice now) , I also upgraded superSU to v2.62, so I will revert to EX for this afternoon, to see if I get a stable run and hopefully determine if its the ROM or new systemless root causing the problems.
[Nexus 6  Original Android Development] hlxanthus:
Yes I am rooted with chainfires systemless root on stock 6.0.1, yes kernel version in about phone and within fku both say r36, have wiped fku app data, and charging led is working and shows "40" in fku
[Nexus 6  Original Android Development] Amos91:
Let me know how you get on!
[Nexus 6  Original Android Development] pkgnex:
Flashed r36 and SU 2.62 this morning, things seemed OK.

Drove to work, and phone wouldn't wake up. Holding power did nothing. Had to hold power and vol-down to get into recovery, immediately rebooted system, but there were no logs.
[Nexus 6  Original Android Development] Mercado_Negro:
Indeed, there's something wrong with both r35 and r36. Woke up this morning and phone wouldn't wake up. I had to hold power button to reboot.

Log here: https://www.dropbox.com/s/f5j4f2xcuuwcp9f/console-ramoops.zip?dl=0
[Nexus 6  Original Android Development] ben_pyett:
A couple of us have also had this...see above.

I flashed back to elemental X and have not encountered it since after it occurred twice in a number of hours this morning.

Still on later supersu 2.62
[Nexus 6  Original Android Development] franciscofranco:
Thanks guys. Back to the drawing board!
[Nexus 6  Original Android Development] franciscofranco:
Try r37 please.
[Nexus 6  Original Android Development] Amos91:
Flashing now!
[Nexus 6  Original Android Development] pantmunu:
I have no issues running systemless root on chroma's latest , people with issues , are u guys using systemless root ,if u are , what was the order u guys flashed the su and kernel . u have to flash the kernel first and then super su 2.62.

More detailed : flashed chroma , banks gasps, unsu.zip , flashed Franco and flashed supersu2.62 .
[Nexus 6  Original Android Development] franciscofranco:
Yes, first the Kernel then SuperSu.
[Nexus 6  Original Android Development] pkgnex:
I've been flashing the kernel first, then supersu. r35 / 2.61 and r36 / 2.62 both caused my issues. The odd thing is that it was after the initial flashing in both cases. After the second boot, I didn't have any more issues.

I'm on the 6.01 stock ROM, btw.

I'll try r37 (followed by 2.62) now and will report back.
[Nexus 6  Original Android Development] nextelbuddy:
ok so i was on stock kernel again for 2 days and loving it, was able to get 6 hours of SOT but that was trying really hard on wifi none the less it was really boring using my phone for 6 hours straight just to get that SOT. During that time I was using adaptive brightness with no issues or wakelocks. deep sleep was not an issue.

I decided to install Franco kernel R4, i downloaded the FKU updater again, auto flashed R4 and rebooted and left everything alone (this was last night before going to bed). took device off wireless charger this morning around 9am got to work this morning and noticed battery was already down to 93% wtf. I looked and my device was not deep sleeping, looked up BBS and it shows sensor_ind ugh....

i disabled adaptive brightness and cleared CPU SPY and turned the screen off. turned screen back on after 3 min and voila deep sleep no more wake lock.

any correlation to the kernel or just another coincidence with timing?
[Nexus 6  Original Android Development] stas333:
i think this wakelock has something to do with google hangouts and adaptive brightness.
[Nexus 6  Original Android Development] wrongway213:
Sensor_ind wakelock has been an issue on multiple kernels, dunno if it's one on stock but it just takes a reboot to fix.. dunno what causes it so I'll let someone more knowledgeable answer that part
[Nexus 6  Original Android Development] nextelbuddy:
I understand its been around, I was one of the first few people to report it on reddit when i got my N6 in november and traced it back to adaptive brightness, ambient display and hangouts (sometimes).

since that time I have made some personal discoveries with my OCD and found that:

1. Stock kernel with NO greenify and Adaptive brightness and Ambient display ENABLED, = no wakelock of sensor_ind for me.

2. Stock kernel with YES greenify installed and greenifying all apps sans system apps with Adaptive brightness and Ambient display ENABLED, = wakelock of sensor_ind

3. lean kernel/franco kernel and NO greenify with Adaptive brightness and Ambient display ENABLED, = Wakelock of sensor_ind

thats what I have found and tested consistently so far.

I'm sure my scenario like MANY is unique and that there are LOTS of people out there that will say that they have tested the same scenarios as me and have no issue and priobably also get 8 hours of SOT as well go figure but I am simply putting my results in here. If Mr Franco doesnt need them or they are not helpful then no harm done but if by chance one of these scenarios helps him track down anything then it was worth it.
[Nexus 6  Original Android Development] noneabove:
Where do you find this wake lock? I have Franco and greenify and can't seem to find that wakelock
[Nexus 6  Original Android Development] nextelbuddy:
i used CPUSPY to see if i was getting DEEP SLEEP or not, once I see im not going into DEEP SLEEP then I use BETTER BATTERY STATS to see what my kernel and partial wakelocks are and that is where you will see sensor_ind if you are getting it or not.
[Nexus 6  Original Android Development] anuragvivek93:
Was getting close to 5.5-6 hr SOT on RC2.

But from Rc3 getting 3.5-4hr. No change in settings. Most apps greenified and location off.

Using RC4 now, and still only 1hr in 20 percent. :(
[Nexus 6  Original Android Development] wrongway213:
in BBS under kernel wakelock but only when it occurs which is quite rarely, it'll prevent your phone from deep sleeping
[Nexus 6  Original Android Development] franciscofranco:
Battery technology has evolved so much, I don't see a reason why we would need that kind of protection. Besides Motorola's battery technology is leaps and bounds better than any of the other vendors.
[Nexus 6  Original Android Development] franciscofranco:
I think it's just coincidence, I haven't touched any of that.

RC?

You know that battery life varies per-day... do you wake up, eat, open/close your eyes, feel hunger, and **** everyday at the same time? This is not an exact science... and besides 20% x 5 = 100% 1h x 5 = 5h... seems fine to me with normal usage.
[Nexus 6  Original Android Development] elijahah:
It jumped to 1-2% after taking the screenshot, I watched it sit at 0% and stay active. I haven't touched anything else on the kernel except the color controls via FKU. Where can I set the threshold value?
[Nexus 6  Original Android Development] warrenis1234:
I remember trying this a few weeks ago. i believe it stops gmaps from locking on your location
[Nexus 6  Original Android Development] Anonymouze:
Im going to test maps tomorrow with deactivated service
[Nexus 6  Original Android Development] cobyman7035:
im getting msm_hsic_host kernel wakelocks...not sure if thats a big issue or not

is that from using chomp SMS texing app?
[Nexus 6  Original Android Development] franciscofranco:
It's simply related to the modem, don't bother with it.
[Nexus 6  Original Android Development] Langduscher:
I can't find any significant wakelocks - but ever since L Preview I'm experiencing massive drain (4%/ h) when screen is off & WiFi is on. This is on all my devices running Lollipop. If I turn WiFi off before turning screen off - all is good.

I've investigated my own network thoroughly (although nothing changed but the OS on my devices) and couldn't find anything weird.

Anyone else?

I refer to this phenomenon as the Wifibug.
[Nexus 6  Original Android Development] JasonJoel:
I don't see that kind of screen off drain on any of my lollipop devices (2 nexus 7 + 1 nexus 6).
[Nexus 6  Original Android Development] paychex:
Unless you KNOW what the kernel wakelock is (not just its name--what it actually does) and that it is specifically related to an issue with THIS kernel, you are better off going to the BBS thread. Almost all the time kernel wakelocks are things that are required for your phone to work--and have little to no impact on battery. Besides, the battery is plenty big. No need to be so OCD
[Nexus 6  Original Android Development] Langduscher:
I do - on n5, n6, n10, s4 & tft300t. Weird.