yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] Mercado_Negro:
I've also had lots of lockups and random reboots since yesterday but I've been so busy that I didn't have time to upload the logs until now. Here it is:

https://www.dropbox.com/s/eqwq0s4dl8yfv63/logs12-15-15.zip?dl=0

Today it was bad with the lockups while I was writting in Whatsapp and Google Messenger using SwiftKey latest version. Everything is full stock 6.0.1 here (with SuperSU 2.62).
[Nexus 6  Original Android Development] franciscofranco:
Thanks for the feedback guys. I'll do some changes and push r38 sometime soon.

Yes, from your terminal. I don't recommend changing that value though.
[Nexus 6  Original Android Development] NOSTALGIA:
fortunately im not getting any reboots with cataclysm and r37
[Nexus 6  Original Android Development] wrsg:
Which logs should we upload?

I have had my first reboot like the other guys, I'm on r37

I don't have xposed installed, just the supersu beta 2.62-3
[Nexus 6  Original Android Development] NLBeev:
Wait till it happens several tines
[Nexus 6  Original Android Development] dunjamon:
Mine's been running fine, and then all of a sudden yesterday afternoon \ evening I had 3 in a row.
[Nexus 6  Original Android Development] NOSTALGIA:
what are these guys doing when the phone got into reboots?? on my 2nd day and i dont have any reboot yet.. hopefully, not gonna get one..
[Nexus 6  Original Android Development] jmtjr278:
Don't have logs so I am not expecting support. But I was using 37 with cataclysm and all was well for a day. Then the reboots began. The phone was sitting next to me while playing Xbox when I noticed it was on the marshmallow boot animation. During one round of call of duty it rebooted 3 times.

As I said I have no logs. Just wanted to share my experience
[Nexus 6  Original Android Development] TR2N:
Is it just me or battery life on 6.0.1 sucks? I'm also have the feeling - that might be a placebo - that the phone gets warmer since the update. I flashed it with the images as clean install and using SuperSU 2.62-3.
[Nexus 6  Original Android Development] Rykochet:
Here is CatLog with some touchboost errors.
[Nexus 6  Original Android Development] patriotaus:
It gets really bad. Unusable bad. In Google Camera, it refreshes the view maybe once every 3 seconds. Pressing home/recents/back doesn't work for at least 15-30 seconds. Stuff crashes.

I just started from scratch, wiped and flashed 6.0.1, installed systemless root and flash latest kernel... and now it seems worse. It's now happening even at near full battery. It does seem to be worse in Google camera but there is definite slow down in other apps (maybe the camera relies more on the cpu)

I'm going to do it all again because I got a bootloop because of the lack of system space which I fixed but maybe not properly. I'll get back to you. (Honestly, I thought it was the kernel to begin with, but now I'm thinking its Google pushing sht updates to their apps, they're really dropping the ball recently)
[Nexus 6  Original Android Development] franciscofranco:
r38 is out, flash asap!
[Nexus 6  Original Android Development] franciscofranco:
That's not an issue, it's just saying it's trying to write to a file that doesn't exist.

Can you try r38 please? Thanks.
[Nexus 6  Original Android Development] Prack:
I need to flash supersu again after correct? Nvm answered my own question as soon as it booted :)
[Nexus 6  Original Android Development] franciscofranco:
Yes sir! It's a small price to pay for an unmodified-system with Android Pay compatibility.
[Nexus 6  Original Android Development] Prack:
I know you are busy but are you still working on fixing fkupdater for per app modes, same with servicly? I'm not sure that we can drop the app in system/app-priv any longer.
[Nexus 6  Original Android Development] TonikJDK:
Flashed 38 and reflashed root. So far all is well. Its only been a few minutes of course. Phone works and root works.
[Nexus 6  Original Android Development] TR2N:
Just curious.. Is it needed to wipe cache/dalvik after updating r38 and flashing SuperSU over it - generally when updating kernels?
[Nexus 6  Original Android Development] franciscofranco:
FKUpdater works with Per-App Profiles on my local build :) Servicely will be updated as soon as FKUpdater is out!

Wiping caches is the biggest myth in the world. Only Android Updates for non-Nexus devices are more of a myth than wiping caches. You get the idea!
[Nexus 6  Original Android Development] TR2N:
Haha, thank you Francisco!

By the way.. I don't know what you did or your cat, but the first impression is far far better than r37! Especially when scrolling through the app drawer!
[Nexus 6  Original Android Development] pkgnex:
Just flashed r38 and su 2.62-3. Still have root and phone didn't reboot or do anything weird.

Scrolling and animations seem quite jittery, but I also just noticed I'm below 40% battery which I don't often get down to, so it's probably that.

I'll recharge and see if it improves. I'll only re-post if it is still a problem (assuming it's just the battery limiting cpu/gpu freq.).
[Nexus 6  Original Android Development] franciscofranco:
I increased input boost freq to 1.5GHz, 1.1GHz is too low for this device.

I'll burn my 6P to go below 40% and try to figure it out.
[Nexus 6  Original Android Development] Stroky:
Is anybody running this Kernel on cm 13?

Gesendet von meinem SGP511 mit Tapatalk
[Nexus 6  Original Android Development] franciscofranco:
Nope.
[Nexus 6  Original Android Development] pkgnex:
Now over 40% (still on charger) jitter seems reduced.

Had Chrome and Photos force close on me before I started charging, too. It's been a LONG time since I had any apps force close... I don't think it's happened to me since Lollipop.

Were the stock kernel binder patches reverted in r38? To be honest, though, I had no force closes on r36 or r37, so I don't think those stock kernel commits were causing me any problems.
[Nexus 6  Original Android Development] Stroky:
Thx

One more question.

How long is the touch boost with your Kernel?

Gesendet von meinem SGP511 mit Tapatalk
[Nexus 6  Original Android Development] franciscofranco:
I reverted the binder patches.

500ms.
[Nexus 6  Original Android Development] Tylog:
Thanks for the update. I had no issues with 37 but let's flash 38. Greetings
[Nexus 6  Original Android Development] cris_webb:
Hi everyone. Sorry, but I can't find UnSu. Can someone give me the link? Thanks and sorry.
[Nexus 6  Original Android Development] :
http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/post63615067#post63615067

Edit
[Nexus 6  Original Android Development] nathanchance:
Right here
[Nexus 6  Original Android Development] cris_webb:
Thanks [emoji14]
[Nexus 6  Original Android Development] Tylog:
Take this https://db.tt/M8bIaSyV

Edit: doesn't see it was posted before
[Nexus 6  Original Android Development] pkgnex:
So once I was fully recharged and off my charger, things seem good. I verified by running a bunch of apps on both r37 and r38 (I flashed back and forth a couple times) and everything seems at least as good on r38 as on r37. I'll chalk the two app FC's to random chance since it hasn't happened since and I've been running the phone really hard during the last hour to do the r37 / r38 comparisons.
[Nexus 6  Original Android Development] patriotaus:
Hey Franco, v38 seems much better to me. Camera is working perfectly (albeit functionless (thanks Google)) now even at low battery levels. Literally the only difference was the kernel version and the fact that I didn't change the DPI this time around (which I don't think was the issue because I hadn't changed the DPI for at least a few months, and the issue seemed to come on with the new kernel version).

I suppose I could try changing the DPI but I don't want to modify the system and the non build.prop way doesn't work properly. (anyway around this guys? I'm hoping to get OTAs)

Thanks
[Nexus 6  Original Android Development] Gedablo666:
Hello,

Sorry for offtopic, but after I flashed latest franco kernel I saw that in status bar appear icon (marked in red) and I don't know what it is and how to remove it. Maybe it was there before flashing. I just dont remember. Maybe anyone know what it is?

Thank you.

[IMG="Screenshot"]http://i1117.photobucket.com/albums/k585/Gedablo/Screenshot_20151217-094917_zpsdkowlulm.jpg[/IMG]
[Nexus 6  Original Android Development] Stroky:
can someone please provide the settings for the conserative governor, like up threshold etc.?
[Nexus 6  Original Android Development] xthetobs:
does it work with 6.0.1? or just 6.0

im on nexus pure

EDIT: Ok I have tried it. Won't boot up now. The boot animation is going on but won't boot up. Any Ideas? I used twrp to flash zip
[Nexus 6  Original Android Development] jmtjr278:
If you look at Franco's post you will see that this is for 6.01 only. It will never boot with any other Android version.
[Nexus 6  Original Android Development] pkgnex:
I'm not familiar with nexus pure, but here are a couple things:

1. This kernel is for 6.0.1 only - not 6.0, so you had that reversed in your assumption. If your ROM is 6.0, that's a problem. If it is 6.0.1., keep reading...

2. This kernel requires the new "systemless root" method - e.g. SuperSU 2.62-3 (most current). You need a clean flash of the 6.0.1 system image for this to work - you can't just flash this kernel on a previously-rooted system image (e.g. using SuperSU 2.52 or earlier).

3. The new systemless root method requires flashing the SuperSU after each kernel flash to modify the boot.img to obtain root.

So, to be safe, flash your ROM clean (full wipe), then flash the kernel, then flash SuperSU 2.62-3, and it should work - again assuming you're on a 6.0.1 ROM.
[Nexus 6  Original Android Development] hlxanthus:
As a side note, any ROM that preroots with the system version of SuperSU you also need to flash the unSU package to remove it FIRST, then flash kernel, and finally SuperSU 2.62-3.

http://xdaforums.com/showthread.php?p=63615067
[Nexus 6  Original Android Development] xthetobs:
pure nexus rom has build in root. if i would also flash systemless root it works?
[Nexus 6  Original Android Development] justibasa:
1. Flash Rom

2. Flash unSU.zip

3. Flash Franco

4. Flash Supersu 2.60 or newer

That's the only way it will work with pure nexus.
[Nexus 6  Original Android Development] NLBeev:
Full wipe = wipe the system partition.
[Nexus 6  Original Android Development] FedericoUY:
Hi. Had 2 random reboots on r38 / cataclysm rom. Also had some lags mostly all when opening recent apps. Is this happening to anyone?
[Nexus 6  Original Android Development] ijustwantaname:
Looks like DT2W missing on r38. Am I blind, did it get moved, or is this intentional?

Edit: nevermind. Forgot to re-flash SuperSU. All is right in the world, again!
[Nexus 6  Original Android Development] holeindalip:
Quick question, when power saving profile is activated and limits CPU to 1267 does input boost still go to 1.5??
[Nexus 6  Original Android Development] miguelito18:
[MENTION=3292224]franciscofranco[/MENTION] Hello.

Is your interactive governor in any way similar to dyninteractive one?
[Nexus 6  Original Android Development] ben_pyett:
On which kernel have you seen/used dyninteractive?
[Nexus 6  Original Android Development] NLBeev:
Maybe they are both interactive. So there must be some similarities.
[Nexus 6  Original Android Development] miguelito18:
[MENTION=354700]ben_pyett[/MENTION] in singularity kernel, but now I'm back on franco
[Nexus 6  Original Android Development] ben_pyett:
I'm completely guessing here, but I suspect that dyn* is just a rebadged tuned customised version of interactive, so without Franco reading all of the code by from the singularity kernel developer, then he'll have to guess.
[Nexus 6  Original Android Development] quailallstar:
Crap... My phone downloaded r38 through FKUpdater, flashed and rebooted. Now it's stuck on the Marshmallow boot screen. Guessing this version is still not working with 6.0.1?
[Nexus 6  Original Android Development] TonikJDK:
It has been fine on 6.01 for several versions now.
[Nexus 6  Original Android Development] miguelito18:
[MENTION=354700]ben_pyett[/MENTION] yes, from what I read it saves even more battery than normal interactive without compromissing performance. And in kernel adiutor when checking the tunables it said that it wasn't changeable
[Nexus 6  Original Android Development] justibasa:
You do know that you have to flash SuperSU 2.60 or above after Franco right. It only works with the new systemless root. Did you not read the changelog?

1. Flash Rom

2. Flash unSU.zip if your on a rooted rom

3. Flash Franco

4. Flash SuperSU 2.60 or above

Changelog: http://kernels.franco-lnx.net/Nexus6/6.0/appfiles/changelog.xml
[Nexus 6  Original Android Development] usafle:
I'm not sure about Android Pay compatibility, just tried to use it yesterday and I got the "can't verify stock Android software" on this phone. I wish the OG Google Wallet was still usable!
[Nexus 6  Original Android Development] LittleJakub:
dear forumers... I am looking for help!

starting with the release r34 my phone has no service - it says no SIM card.

I tested every single build since then - including the r38.

still no SIM...

however, when trying elementalX or stock - I use LTE network (and can input my SIM card PIN).

does anyone have any idea what might be causing this?

I really miss using franco... :(

---------- Post added at 09:40 PM ---------- Previous post was at 09:24 PM ----------

*using with stock ROM - tried both with and without root.
[Nexus 6  Original Android Development] NLBeev:
It is possible that you use systemless root. When this is true you need to flash SuperSU 2.6x as the last file.
[Nexus 6  Original Android Development] NOSTALGIA:
try cata rom .. then flash the latest systemless root then franco.. its good.. cata is just same as stock with some extra features..
[Nexus 6  Original Android Development] ironjon:
Not in this order, first cata, then Franco and finally systemless root

Enviado desde mi Nexus 6 mediante Tapatalk
[Nexus 6  Original Android Development] NOSTALGIA:
well i mixed it up.. but your right..

:good:
[Nexus 6  Original Android Development] NLBeev:
Flash SuperSU 2.6x as the LAST file. To avoid non-detecting sim-card.
[Nexus 6  Original Android Development] rasengan82:
I agree, no FC issues with the stock kernel binder patches.
[Nexus 6  Original Android Development] LittleJakub:
tried doing all that was advised - still no luck... I cannot understand, what is happening :(

once more I'll point out - with elementalX everything works - so I am wondering, if there is some code in franco kernel that blocks my SIM card :(
[Nexus 6  Original Android Development] Gedablo666:
Has anyone noticed that with Franco kernel app drawer having lag spikes? I tried on both Cataclysm and Chroma ROM with Franco. Just flashed back Chroma without Franco and issue dissapear. I'm using Nova launcher (vertical app drawer).
[Nexus 6  Original Android Development] NLBeev:
In many cases non detecting sim-card issues are caused by flashing a Rom and systemless root and leftovers of previous Rom/SuperSU versions.

That's why the system partition and caches need to be wiped before flashing. And the systemless SuperSU 2.6x must be flashed as the last file. So if you flash a kernel, than a reflash of SuperSU 2.6x is also necessary.
[Nexus 6  Original Android Development] LittleJakub:
my steps were:

flash stock 6.0.1 using WugFresh's Nexus Toolkit

flash TWRP

open TWRP, perform "wipe data" and "factory reset"

reboot to recovery

flash franco kernel zip (r38)

wipe cache & dalvik

flash SuperSU 2.62-3 zip

wipe cache & dalvik

reboot system

I end up not being able to use SIM card :(
[Nexus 6  Original Android Development] NLBeev:
In your list I miss 'wipe system partition' followed by flash a 6.0.1 Rom and SuperSU 2,6x as the last file.
[Nexus 6  Original Android Development] hlxanthus:
He is on the stock factory images, and as long as he is on the 6.0.1 versions there should be no issues. That is essentially what I did.
[Nexus 6  Original Android Development] usafle:
Excuse my ignorance, but I can't locate anything marked "touch boost freq" in the paid version of the app.

I'd like to be able to tinker a bit to get better battery life and always try to use others recommendations.

Thanks!
[Nexus 6  Original Android Development] LittleJakub:
when a stock image is flashed, the old system partition is erased.

and SuperSu 2.6x is flashed as the last file :)
[Nexus 6  Original Android Development] NLBeev:
...because the sim-card isn't detected, consider to give 'wipe system' a try.....
[Nexus 6  Original Android Development] hlxanthus:
That would be simply ridiculous and pointless. He flashed the factory images and he doesn't want to run a custom ROM. I think this guy actually has an issue here that isn't user error . .
[Nexus 6  Original Android Development] LittleJakub:
as soon as I saw your response (and it's a day off) I tried doing as you advised. this ended up in the following steps:

run TWRP

wipe everything through advanced wipe option

reboot to bootloader (TWRP warns about no system installed)

flash stock 6.0.1 using WugFresh's Nexus Toolkit

flash TWRP

open TWRP, perform "wipe data" and "factory reset"

reboot to TWRP

flash franco kernel zip (r38)

wipe cache & dalvik

flash SuperSU 2.62-3 zip

wipe cache & dalvik

reboot system

still no luck :( no SIM card detected...

is it possible that I am having trouble because my SIM card is weird in some way (I know - stupid thought, but I am semi-desperate)?
[Nexus 6  Original Android Development] LittleJakub:
thank you for understanding - I've been into tweaking stuff in Android for a few years now, and I really read the instructions - this one baffles me.

because one thing is sure (I think) - isn't franco kernel supposed to work even without root (of course then the FKU updater app won't work, but this shows that the kernel itself should be ok)?
[Nexus 6  Original Android Development] TonikJDK:
Flash stock wiping everything along the way. Stop there and boot the phone. Lets see if it works fully stock and narrow the variables down.
[Nexus 6  Original Android Development] LittleJakub:
just to be clear - I did a so called "bughunt" to see which variable causes the thing, before seeing your proposition :) I really always try to seek my mistakes before asking people for help :)

so the options covered were:

flashed clean stock with full wipe along the way - everything works

boot to bootloader

flash stock 6.0.1 using WugFresh's Nexus Toolkit

reboot system

flashed clean stock with SuperSU 2.62-3 - everything works

boot to bootloader

flash stock 6.0.1 using WugFresh's Nexus Toolkit

reboot to bootloader

flash TWRP

boot to TWRP

perform "wipe data" and "factory reset"

reboot to TWRP

wipe cache & dalvik

flash SuperSU 2.62-3 zip

wipe cache & dalvik

reboot system

flashed clean stock with elementalX 3.07 + SuperSU 2.62-3 - everything works

boot to bootloader

flash stock 6.0.1 using WugFresh's Nexus Toolkit

reboot to bootloader

flash TWRP

boot to TWRP

perform "wipe data" and "factory reset"

reboot to TWRP

wipe cache & dalvik

flash elementalX 3.07 zip

wipe cache & dalvik

flash SuperSU 2.62-3 zip

wipe cache & dalvik

reboot system

flashed clean stock with franco kernel r38 + SuperSU 2.62-3 - no SIM card detected

boot to bootloader

flash stock 6.0.1 using WugFresh's Nexus Toolkit

reboot to bootloader

flash TWRP

boot to TWRP

perform "wipe data" and "factory reset"

reboot to TWRP

wipe cache & dalvik

flash franco kernel zip (r38)

wipe cache & dalvik

flash SuperSU 2.62-3 zip

wipe cache & dalvik

reboot system
[Nexus 6  Original Android Development] NLBeev:
Call it what you want. Give him a better idea. For me wiping the system partition was a solution for the same issue.
[Nexus 6  Original Android Development] LittleJakub:
I want to point out, that I tried your proposition - it's just that it didn't fix the problem for me :)

nevertheless - I am thankful for your help - it means a lot that users are trying to come up with possible solutions :)
[Nexus 6  Original Android Development] NLBeev:
In a forum misunderstanding is always possible. The reason of my previous response was the use of Wug's toolkit.

I assumed you could have used the root option. The toolkit uses for rooting SuperSU 2.5x that includes changes of the system partition. When later the systemless root is used it may be the cause of issues. There is a script somewhere called Unsu.zip that removes 'old' su stuff. But wiping the system should do the same. I am sorry for you the sim-card issue is still there,
[Nexus 6  Original Android Development] LittleJakub:
it's OK - I am pretty sure that somehow in this forum we're going to find a solution :)

about the SuperSU in Wugfresh's tool - I know that in it there is 2.5x, so I always flash SuperSU on my own and never through the tool ;)
[Nexus 6  Original Android Development] holeindalip:
I was just sitting at McDonalds waiting for my wife to call and the signal went blank and no sim icon popped up for a few seconds and then signal came back and all is normal again, so I don't think it's isolated to a single person. I know franco tries to stay close to stock with mods but something fishy is going on somewhere
[Nexus 6  Original Android Development] hlxanthus:
[MENTION=3292224]franciscofranco[/MENTION] or any other users. Has this been tested yet with chainfire's latest v2.64 systemless SuperSU root?
[Nexus 6  Original Android Development] patriotaus:
[MENTION=470754]Franco[/MENTION]

I've run my phone down a bit for a few days in a row and the lag and instability is completely gone on r38. Thanks.
[Nexus 6  Original Android Development] ben_pyett:
[MENTION=3292224]franciscofranco[/MENTION]

Today I've strangely suffered a couple of random reboots. Attached are logs, let me know if there's any obvious, or something which I should be concerned about?
[Nexus 6  Original Android Development] PCWright86:
Yes, it works fine. I have been running v2.64 with Franco r38 for a few hours with zero problems
[Nexus 6  Original Android Development] Mercado_Negro:
I've also experienced that problem where the SIM card is not detected. In fact, I had it a lot with r38 along with some random reboots which were supposed to be fixed. I switched to the stock kernel and it's been rock solid for 3 days now. I also think there's something weird going on with franco.Kernel.
[Nexus 6  Original Android Development] holeindalip:
I've done everything I can think of, I'm on a full system wipe and format,factory reset everything and I still get rr with newest builds and very poor performance,stock kernel works fine
[Nexus 6  Original Android Development] noneabove:
For me my largest drain seems to be location (i think..)

with 2 hours 41 min of use, my phone was kept awake during screen off for 33 min, that number seems pretty high to me

for some reason BBS won't let me view kernel wake locks but i doubt it's that tbh, seems to be hangouts + locations.
[Nexus 6  Original Android Development] franciscofranco:
Because that network is pretty busy.
[Nexus 6  Original Android Development] cmo220:
A lot of people love to talk about their screen on time. A lot of people complain that they aren't getting what others get. Not many know much about kernels, most even spell it wrong. I don't know much about kernels either but I do know that there are many reasons that you don't get the same battery life as other people. For me, I have horrible signal strength throughout the day. On top of that I spend most of my day listening to audio books through my Bluetooth headphones while I'm at work. Today, after work, I have 61% battery. With 18 minutes of screen on time using this kernel. I consider this pretty good.

Most people don't seem to understand that so many different things go into battery usage so they think the kernel is causing problems. Look at your usage and signal first, but mainly don't expect to have the same life as people putting in screenshots. It would be nice but usually not likely.