yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] SweetwaterBurns:
I know you don't believe me, but since November, when I started using the beta of Fku that led to the current stable version, I've seen the behavior. As I said before, It started on my nexus 4 and it has happened on my nexus 6. I had set up some watchdog scripts on my phone to try and figure out what process is changing things, but they aren't catching everything and I haven't had time to debug them yet. Maybe on my spring break. It might not be a bug in your code, but a conflict that gets triggered with my usage while using your app. I haven't figured out how to reproduce it yet, but I can tell you with 100% certainty that removing fku seems to stop it from occurring. Since [MENTION=5392575]C00lBeanz[/MENTION] seems to be experiencing the same issue and no one else is offering a solution, it can't hurt for him to test and see if running without the app solves it for him, too.
[Nexus 6  Original Android Development] Damon13:
In WIFI settings under advanced turn off scanning always available. Whether WIFI is on or off it's always scanning thus in battery graph you will see it as on.
[Nexus 6  Original Android Development] franciscofranco:
I understand, but I assure you there's no way FKUpdater can do that. If it was a free app I would open source the code and show it doesn't do anything like that, there's no way.
[Nexus 6  Original Android Development] franciscofranco:
Pushed r15! Happy Sunday!
[Nexus 6  Original Android Development] schizophrenia:
Thanks for reminding but as I first posted I have turned off "Scanning always available" since day 1. So it's not related in this case.

---------- Post added 16th February 2015 at 12:03 AM ---------- Previous post was 15th February 2015 at 11:44 PM ----------

got quite an urgent problem here right after I tried to flash r15.zip from FKU directly using the built-in file manager "auto flash".

So i did flash r15 from FKU directly after download, it went to "fastboot" screen and it just stopped there. Whatever I click (e.g. Start), it just goes back to the "fastboot" screen. I see from the "Bootloader logs" it says "Invalid boot image size! failed to validate boot image" So I chose to go to Recovery but since i am on a pattern lock, i can't access to "Storage" as i dont have a password to access the encrypted storage.

Anyone got a solution for me and do you know why it happened? Thanks.
[Nexus 6  Original Android Development] :
Can't update from r1 to r15. I auto flash and reboot but when I have rebooted it still says my kernel is v r1
[Nexus 6  Original Android Development] pinoyflayv:
R15

Happy Sunday all! Flashed R15, same as usual Butter! Thanks Francisco!
[Nexus 6  Original Android Development] stas333:
Patiently waiting for the FKU update :D
[Nexus 6  Original Android Development] anthonyg45157:
Flashed r15 running great. If I disable msm_hsic_host, does it stay disabled after reboot, or would I have to disable every time I reboot?

Thanks!

Sent from my Nexus 6

---------- Post added at 11:17 AM ---------- Previous post was at 11:17 AM ----------

This!! :thumbup:

Sent from my Nexus 6
[Nexus 6  Original Android Development] ambichetan:
How do we disable msm_hsic_host manually ?
[Nexus 6  Original Android Development] zephiK:
It's an option in FKU, not sure if it's been updated on the play store or not.

Or you can modify the path directly.
[Nexus 6  Original Android Development] :
When I auto flash it still says my kernel is v r1
[Nexus 6  Original Android Development] trickster2369:
Autoflashed from r14 to r15. FKU says update available still. Kernel version in about phone says r14 as well.

Sent from my SinLess Shamu
[Nexus 6  Original Android Development] anthonyg45157:
Maybe try to clear cache or data of fku. I downloaded and flashed with recovery and had no issues with this.

Sent from my Nexus 6
[Nexus 6  Original Android Development] adrman:
Perfect Auto-Flash on Chroma.
[Nexus 6  Original Android Development] stas333:
i like doing manual updates. no issues here.
[Nexus 6  Original Android Development] Skripka:
Flashed fine here from r14
[Nexus 6  Original Android Development] CRXed:
You currently have no Kernel! You will need to flash one manually using Fastboot.

FKU downloads a ZIP file and offers the Auto-flash option on a ZIP file in the File Manager. But that's not possible, it can only auto-flash .IMG files.

Franco has not released an update to fix this yet, he acknowledged this bug before.

Either Auto-flash on a ZIP file needs to be removed from the menu options in the File Manager, or the apps needs to do an unzip before flashing.

Good luck with getting your phone to boot again.
[Nexus 6  Original Android Development] schizophrenia:
Thanks and now I know why. At least from now on I know what to avoid.
[Nexus 6  Original Android Development] trickster2369:
I've been using FKU to autoflash since around r6 without this issue, so I'm just reporting. And I'm sure flashing it in recovery works just fine, however, isn't the autoflash feature kind of the purpose of FKU(Franco kernel updater)? Leads me to believe there might be an error in the script? Just thinking out loud.

Sent from my SinLess Shamu
[Nexus 6  Original Android Development] franciscofranco:
There's a bug on the File Manager where you auto-flash a .zip file it writes the .zip block to the boot block, thus rendering you without a Kernel. Just auto-flash.

If you bothered to read the change-log I provide the path there...
[Nexus 6  Original Android Development] daleski75:
It seems to reset itself on each reboot in my testing, can others confirm this as well?
[Nexus 6  Original Android Development] franciscofranco:
Auto-flash code is the same since ever. I download the .img file to /sdcard/franco_kernel_updater/kernel_backups/boot-rWhatever.img, then I write the .img to the boot block using dd.

public static String dd(String arg0, String arg1) {
int size = getImageSize(arg0);
return "dd if=" + arg0 + " of=" + arg1 + " bs=" + size + " count=1";
}

I run this inside an interactive Shell from libsuperuser. I have a callback that is triggered when the command is finished, then I reboot the device.

If anyone thinks this is wrong, please, I'm all ears :)
[Nexus 6  Original Android Development] franciscofranco:
And again, sysfs entries always reset on reboot. That's why we use scripts and apps.
[Nexus 6  Original Android Development] comminus:
su -c echo 0 > /sys/module/wakeup/parameters/enable_msm_hsic_ws

Edit: damn you Tapatalk delay...
[Nexus 6  Original Android Development] trickster2369:
Thanks for the response. I tried to autoflash twice without luck, so I just flashed in recovery, so no big deal. Anything you could think of as to why it didn't autoflash for me?

Edit: not questioning your code in any way,

Sent from my SinLess Shamu
[Nexus 6  Original Android Development] SweetwaterBurns:
If I remember right, the pattern lock corresponds to the numbers in the same position. 1 in the top left, 9 in the bottom right, etc. Type the code in the order you normally swipe.
[Nexus 6  Original Android Development] schizophrenia:
that's great tip. let me try. thanks.

Edit: you are right. thanks.
[Nexus 6  Original Android Development] franciscofranco:
Absolutely no idea. Question, are you SELinux permissive or enforcing? What's your SuperSu version?
[Nexus 6  Original Android Development] :
Flashed r15.... lost root
[Nexus 6  Original Android Development] trickster2369:
I haven't changed SELinux, and SUPERSU is, according to the app, 2.40.

Edit : might be because I don't enable SU at boot?

Sent from my SinLess Shamu
[Nexus 6  Original Android Development] Mervingio:
Jesus........ [emoji23] [emoji23] [emoji23] [emoji23]
[Nexus 6  Original Android Development] franciscofranco:
Ok.

Nah, that is unrelated. I'm completely at a loss. The code is the same as ever and I can't reproduce :( I have SuperSu 2.40 as well, no issues. I'll do my best to try and understand what's up.

Can you try with my Free app? Thanks.
[Nexus 6  Original Android Development] yoyoz808:
Maybe try update to SuperSU 2.46
[Nexus 6  Original Android Development] trickster2369:
I have that zip, and will do that as soon as I update SinLess today.

Sent from my SinLess Shamu
[Nexus 6  Original Android Development] franciscofranco:
Have you tried flashing with my free app? I'm really clueless here. If you're up for it, can you nandroid your rom, flash stock, flash supersu and try to auto-flash using FKUpdater?
[Nexus 6  Original Android Development] C00lBeanz:
Why do your kernels keep killing my cats franco!? :mad:
[Nexus 6  Original Android Development] franciscofranco:
You're their owner, it's on you.
[Nexus 6  Original Android Development] gparmar76:
Wow, that's harsh..but probably true.
[Nexus 6  Original Android Development] codygs83:
Finally got r15 installed and running great ?

Saw a few other people with the same problem I had. Wouldn't dload or install from paid fku app.

Had to grab link in op and flash manually.

First world problems... Lol
[Nexus 6  Original Android Development] trickster2369:
Sorry for the delay. I flashed a new version of SinLess rom first. Flashed r13. Installed free fku to update, and it worked fine. Uninstalled fku, flashed r13 again. Installed fku paid to update to r15, and it worked fine. Not sure what the issue was before, but apparently a clean flash was the answer. Sorry for taking up space, and thanks for all your work.

Sent from my SinLess Shamu
[Nexus 6  Original Android Development] biggiestuff:
Did you ever figure out a fix for your cpu1 getting stuck at 300mhz? I'm stock, rooted and using fku to update. I'm on r15 and after some stuttering came here to see what the issue be and saw your post and verified in experiencing the same issue.
[Nexus 6  Original Android Development] franciscofranco:
It doesn't scale past 300MHz? You 100% sure? How do I reproduce?
[Nexus 6  Original Android Development] manup456:
I just purchased the app, installed the kernel and enabled double tap to wake and it won't stick after reboot. Any suggestions or info on this.
[Nexus 6  Original Android Development] murdok83:
You need to set the parameter first (enable/disable) and only after you check "set on boot"
[Nexus 6  Original Android Development] biggiestuff:
I don't know what reproduces it but when checking the CPU manager I'll see cpu1 stuck at 300mhz. Cpu2 will scale up and down accordingly but cpu1 won't. I followed what the other poster said and switched back and forth between conservative and performance and back and cpu1 will get off 300mhz. I'll see if I can try to reproduce it on command but at first I noticed it when the battery was low so I assumed it might be by design to conserve battery but I'm currently at 70% and just came out of a long 2 .5 hour idle and noticed scrolling in Tapatalk was sluggish so I checked CPU manager and that's when I saw that it was stuck at 300mhz again.
[Nexus 6  Original Android Development] yoyoz808:
No I never found a fix but that was on test boot.IMG r15 and it happened on r14 but it does t seem to do that anymore for me. I was thinking it had something to do with the qcom's crappy thermal hotplug routine. Since a better one was put in place my cpu1 doesn't stay at 300mhz anymore.

[MENTION=3292224]franciscofranco[/MENTION]

After a while of idle and waking the screen, sometimes the cpu1 gets stuck at 300mhz. You can try go back to the test IMG from a couple days ago or r14 and I noticed this problem and others as well. But like I said I don't notice it anymore since you put a better thermal hotplug routine :D or one of the other patches you put on the latest release.

---------- Post added at 01:01 PM ---------- Previous post was at 12:59 PM ----------

If u change just your max freq to whatever it will come off of 300mhz and you can switch back the max freq and all will work normal but after a little while of idle and screen off it will do it again.
[Nexus 6  Original Android Development] manup456:
Yeah I tried all that, but as soon as I even back out of kernel settings is goes back to disabled. I uninstalled and re-installed app, flashed kernel again and still. I am not sure why this is going on.
[Nexus 6  Original Android Development] Dabarr:
+1 having the exact same problem here. Everything else works fine.

Franco, Thanks for the recent update btw! Can't wait to see if and how battery life is affected. Great kernel the anyway though!
[Nexus 6  Original Android Development] yoyoz808:
[MENTION=3292224]franciscofranco[/MENTION]

The 300mhz issue is still hapenning on r15. Just started happeneing.
[Nexus 6  Original Android Development] franciscofranco:
Either your root is busted or your rom is reseting the double tap to wake value after you screen off/on.

Let me know if you figure out how to reproduce it.

:)

Your root is busted.

Your root is busted.
[Nexus 6  Original Android Development] franciscofranco:
Just out of the blue?
[Nexus 6  Original Android Development] yoyoz808:
Yup. I think it has something to do when the screen turns off and goes into idle and wakes from that state.
[Nexus 6  Original Android Development] franciscofranco:
Hmm... that's weird. I'll go check my code again on that part.
[Nexus 6  Original Android Development] yoyoz808:
Okay so I reproduced it by turning the screen off and leaving it at idle for 5-10 mins and then using the phone.
[Nexus 6  Original Android Development] franciscofranco:
I just did that, no issues what-so-ever. I'm gonna change some code and post a test boot.img. I haven't even messed with that code a while. Weird.
[Nexus 6  Original Android Development] yoyoz808:
Weird... Well I noticed after a fresh reboot it doesn't do it the first few hours but after a while of phone use and then it happens continually.

I was wondering if it had anything to do with that patch you did a little while back that tames certain CPU cores because of conservative's aggressiveness with frequencies?
[Nexus 6  Original Android Development] ozg33k:
I never use OTA apps or anything other than recovery to flash anything lol..

---------- Post added at 04:40 PM ---------- Previous post was at 04:38 PM ----------

I can't believe I just learned this. Haha nice.
[Nexus 6  Original Android Development] manup456:
[MENTION=3292224]franciscofranco[/MENTION]

You where 100% correct all is well now, great work on the kernel.
[Nexus 6  Original Android Development] franciscofranco:
Nah, that code doesn't prevent the device to ramp up at all. I'll look at that code nevertheless.
[Nexus 6  Original Android Development] bradputt:
does color control sticks after reboot for you guys on R2??

for me the value sticks but it will revert to the yellow tint after reboot.
[Nexus 6  Original Android Development] franciscofranco:
It's a bug on FKU if that's what you're referring.
[Nexus 6  Original Android Development] franciscofranco:
If you mean USB fast charge, yes soon.
[Nexus 6  Original Android Development] Anonymouze:
Just bought your FKU-Pro App. Now I'm looking forward to get some information how to configure the app/kernel, just joking ;)

With stock rooted kernel and Terminus-Rom as it comes, I get about 5h SoT, I will leave feedback what's possible with your kernel. Don't forget I won't change anything and use your kernel as it comes.

I hope my english isn't so bad and everybody understand what I mean. Greetings from Germany
[Nexus 6  Original Android Development] zephiK:
Your English is just fine, I completely understand it :)
[Nexus 6  Original Android Development] nexusmaniac:
Hi Franco :) I just thought I'd give a tiny bit of feedback. It might be because of my usage of the device but I think that r2 battery life is slightly worse than r1. Not so bad that I'm going to flash back but quite a bit less screen on time ~40mins :( That might be because of your touch boost change between r1 and r2. Not seeing anything out of the ordinary in the battery page so I'm putting the kernel as the cause :)
[Nexus 6  Original Android Development] Elpatii:
Franco kernel for Nexus 6, yeah :D

But... my CPU min freq is stucking at 1728MHz, even after reboot with "set on boot : on".

If I change to 2,6GHz, it will revert back instantaneously to 1728MHz. I've the latest SuperSU, FKU pro version with root allowed.
[Nexus 6  Original Android Development] EcHoFiiVe:
Got 6 1/2 hrs SOT with slight tweaking with 10% left. Amazing, I would get 2 1/2 hrs before.
[Nexus 6  Original Android Development] franciscofranco:
Oh I just increased from 1.1ghz to 1.2ghz. But decreased the boost period from 80ms to 40ms. Its not enough to justify a power usage regression.
[Nexus 6  Original Android Development] paychex:
For what?
[Nexus 6  Original Android Development] vomer:
Combine qualcomms quick charge with usb fast charge = rainbows and ponies?!?!
[Nexus 6  Original Android Development] csavino3:
Excellent, thanks for the quick response. Love the work so far.
[Nexus 6  Original Android Development] bpdev:
[MENTION=3292224]franciscofranco[/MENTION] Do you think this is accurate? If so is there anything that can be done besides wait for google to update the drivers?

I got that from this thread by the way (page 13):

http://xdaforums.com/nexus-6/general/getting-concerned-performance-phone-t2980267/page14

Edit: Maybe this
[Nexus 6  Original Android Development] Smallsmx3:
I just played Madden after updating to r2 and it's still pretty choppy. Not blaming FK.... It's like that on stock. Question is are the newer drivers available if this post is accurate
[Nexus 6  Original Android Development] occtec:
Apparently Android 5.0 - 5.0.1 has a memory leak, we may possibly see a lollipop update to fix this issue soon 5.0.3 https://ausdroid.net/2014/12/31/android-5-0-lollipop-memory-leak-found-fix-coming/
[Nexus 6  Original Android Development] The5Venomz:
Do you mind posting your settings that you used? Trickster Mod? Or Franco Updater?
[Nexus 6  Original Android Development] Krunk83:
What can I increase the input boost to to get the best smooth scrolling results? Is the input boost nabbed "boost" in governor control?

nexus 6
[Nexus 6  Original Android Development] franciscofranco:
input_boost_freq is inside CPU-Boost.
[Nexus 6  Original Android Development] hutzdani:
Just flashed r2 after issues with r1 hiding home and recent and crashing when put on a QI charger.

Wow with the r2 dt2w is works like 99.9% of the time ! Great work !

And also none of the mentioned issues with QI and home / recents occurs now awesome !

However it has broken lightflow from working with the charging LED : fixed this by re installing the light flow app and not enabling the mixer mode
[Nexus 6  Original Android Development] Zenzr:
This has been said before lol.
[Nexus 6  Original Android Development] dvdivx:
The only problems I've had waking the device up after it's idle comes from the proximity sensor. Turn it off and the problem goes away.
[Nexus 6  Original Android Development] yoyoz808:
That's nothing to do with what we're taking about...
[Nexus 6  Original Android Development] franciscofranco:
Try the attached boot.img, I made some serious changes.
[Nexus 6  Original Android Development] yoyoz808:
Giving it a try. I'll report back in a few hours :good:

---------- Post added at 06:42 PM ---------- Previous post was at 05:47 PM ----------

Strange.... After a couple hours its still doing it
[Nexus 6  Original Android Development] franciscofranco:
When did this start? That test .img that I posted 2 days ago? Or r14?
[Nexus 6  Original Android Development] cmo220:
This isn't the same issue but I feel like I've seen it mentioned in here before.

The auto flash in the app doesn't work for me (tried paid and free, wiped data, uninstalled reinstalled and all that).

I'm sure it's something on my end just wondering if anyone knows the fix?

It worked fine before but never has on this phone. I got a replacement a couple weeks ago.

Tomorrow if I have time I'll go back to stock and start over unless I hear another option first.

It works fine if I download the zip and flash through recovery.

I do know other people on the same ROM do not have this issue. I am on latest Super SU and FKU.
[Nexus 6  Original Android Development] yoyoz808:
I haven't tried it on r13 but went back to r14 and still had that problem. Trying to get a logcat to see of anything comes up.
[Nexus 6  Original Android Development] franciscofranco:
There are no logs for this. Let me get you another boot.img.

EDIT: Here.
[Nexus 6  Original Android Development] yoyoz808:
Yea I didn't think so but I thought I'd try lol. Giving the new test a try.
[Nexus 6  Original Android Development] trailblazerz11:
Hey, [MENTION=3292224]franciscofranco[/MENTION] I've been talking to you on G+ about Cores 3+4 getting stuck at 2.6Ghz and not offlining.

First of all, really confused why I (and at least another user) can reproduce but you can't >_<

Anyways I've found that cores 3+4 get stuck because they seem to use performance governor.

Still trying to figure why that would happen but at least it makes sense now that setting the governor again in FKU fixes it.

The issue does seem isolated to the thermal driver as I've tested r14 along with a kernel compiled with the thermal commits reverted and they run fine.

My guess is some odd combination and timing of cores hotplugging and thermal throttling(noticeably during boot) is causing it. It also

seems capable of 'fixing' itself with another combination but that requires getting it to throttle.

You might be right about something with init though as the first cpufreq prints have interactive and performance during boot:

<6>[ 6.793364] cpufreq: updating policy for CPU 0 min 300000 max 2649600 policy 0 governor interactive
<6>[ 6.793507] msm_thermal: Setting cpu0 max frequency to 1728000
<6>[ 6.793518] cpufreq: updating policy for CPU 1 min 300000 max 2649600 policy 0 governor performance
<6>[ 6.793632] msm_thermal: Setting cpu1 max frequency to 1728000
<6>[ 6.793643] cpufreq: updating policy for CPU 2 min 300000 max 2649600 policy 0 governor performance
<6>[ 6.793760] msm_thermal: Setting cpu2 max frequency to 1728000
<6>[ 6.793769] cpufreq: updating policy for CPU 3 min 300000 max 2649600 policy 0 governor performance
<6>[ 6.793934] msm_thermal: Setting cpu3 max frequency to 1728000

Then Core 0+1 get changed to conservative while 3+4 stay on performance. [58.293376]

Attached is the full log with cpufreq_update_policy info being spammed. #nofilter I'm thinking I need prints for Cores online/offline to get the full picture.

Though I actually have no idea how in msm_thermal.c cpufreq_update_policy(cpu) call relates to your struct thermal_info so I'll doing some reading on that but off to bed now.
[Nexus 6  Original Android Development] yoyoz808:
Still doing it :/ fk updater wouldn't be causing that would it? I was trying to reproduce and i couldn't do it untill I opened your app and then turned off the screen and 5 min later, same problem... Maybe just a coincidence about the app but I can't figure out if its something on my side like an app or ROM or something with the code. I like to try think its code last :p
[Nexus 6  Original Android Development] duminduweera:
I too have the last 2 cpu cores stuck at 2.6mhz, but there is no way of reproducing it. it happen to me like 10mins ago :(
[Nexus 6  Original Android Development] kossiewossie:
would you by any chance be using facebook messager? it was causing me this issue, for some odd reason it be locking two of my cores at max speed. draining the battery pretty quickly.
[Nexus 6  Original Android Development] SmokeyMon:
I could repro this on previous versions of the kernel using viper4android super high quality drivers. Basically with those drivers selected, after I played audio, cores 2 and 3 would be turned up to 2.6 and not seem to reset after the music stops. I regressed the drivers to the medium quality and the problem went away. Its likely application related. That's also why its hard to repro widely.

[MENTION=3901108]duminduweera[/MENTION]
[Nexus 6  Original Android Development] ldkud50:
I also found Facebook Messenger to be the cause of the stuck cpu's. Uninstalled. Trying DISA now.