yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] feered:
No, it's fine. I was just curious. I know it's hacky but it's a nice alternative to constantly flashing a new ROM.

I commend you though for sticking to your morals.

Cheers!
[Nexus 6  Original Android Development] grayskul:
That's a hardware problem. I had the same thing happen to me so I went back to T-Mobile and got a replacement. My friends does the same thing.

---------- Post added at 10:09 AM ---------- Previous post was at 10:06 AM ----------

Oh and my friends nexus 6 is stock not rooted. He's actually sitting right next to me right now and asked him if it's still happening to him and he said yes it is.
[Nexus 6  Original Android Development] duminduweera:
This might be a bug, or may be just how the kernel works. I noticed that r17 is a bit laggy than the previous releases. Therefore i decided to check my cpu stats using system monitor.

I've noticed that my cpu 3&4 does not go online even though im doing multiple things. in previous releases, if i scroll in fb or in tapatalk, the cpu 3&4 comes online. But it doesnt anymore, 95% of the time only 2cores work.

I know that the cores come online according to hotplug controls, and I haven't changed any settings.

To test this, i decided to change the max cpu speed to 653mhz hoping the more cores will go online.but even then,95% of the time only 2cores are online.

Just to make sure, my load threshold is set to default "98".
[Nexus 6  Original Android Development] jodvova:
I have exactly the same behavior.

Governor = conservative.
[Nexus 6  Original Android Development] githyanki:
Try with load threshold set to 0. Will make all cores online. Runs much smoother and little or no battery affect.
[Nexus 6  Original Android Development] trickster2369:
This works well, and you probably won't even notice a battery hit.

Sent from my SinLess Shamu
[Nexus 6  Original Android Development] cdsbj6508:
Franco I applaud you for your patience with some of these questions. [emoji122]
[Nexus 6  Original Android Development] Ladduro:
Can anyone else confirm this will have minimal impact on battery?

[MENTION=3292224]franciscofranco[/MENTION] what do you think?

Thanks
[Nexus 6  Original Android Development] SmokeyMon:
[MENTION=3821325]dcoy82[/MENTION]

Agreed. I created an RMA for mine doing the same. I found mine manifested the behavior on different Roms and kernels. Given enough time I suspect you will too..

The issue was known to moto support. Basically if a factory reset doesn't fix it they will RMA it. In my research, I found several t mobile users with the issue in a reddit thread, some threads here, there was a theory in another thread regarding cold temps causing it. Regardless, some users have never experienced it.
[Nexus 6  Original Android Development] GregNexus:
If i go to Better Battery Stats and then to the section "Partial Wakelocks"

There is an Wakelock on the top which is called "AudioMix"

For what does this Wakelock stand for? How to stop this ? Has it a large impact on battery? (i was not playing music on my device since the last boot)

even if this is an partial wakelock, would there an negative impact if you would disable this wakelock?
[Nexus 6  Original Android Development] Mistertac:
AudioMix is a catch all of sorts for Sound, be it your notifications, music, ringers, touch sounds etc... It shouldn't be an issue and is needed.

You could use something like Wakelock Detector to see what app exactly is using AudioMix and troubleshoot from there if you think it's an issue.

I've not been using WLD on LP like I used to on Kit Kat, but it should hopefully be working the same where you can expand each app and see the Alarms and WL.
[Nexus 6  Original Android Development] big_adventure:
This is how I usually ran my N5, and how I've been running my N6 for quite a while. I get pretty decent battery life - and objectively a little bit better than I got running stock load_threshold. Unloaded cores stay way down in frequency, and consume almost no power at all down there, but they are instantly ready (no need to sample) to ramp in case of load, which means the whole phone can step back down to low frequencies more rapidly. Keeping core load, and therefore frequency, low lets the phone also keep the memory and other subsystems at a lower voltage, which is the hidden advantage of low CPU frequencies.

Basically, voltage isn't linear with frequency on a CPU core. The phone doesn't use 2x the energy per second at 2.6ghz versus 1.3ghz, the ratio is a fair bit higher than that. So, in general, just the CPU cores use less electricity doing the same task at 1.3ghz than at 2.6ghz, though the task takes twice as long. HOWEVER, there are a number of other subsystems that ALSO need electricity, and those systems step up in voltage as frequency increases. So, let's say that task A uses "1 unit" of electricity for the CPU if the cores can stay at 1.3ghz, and 2.8 units to do the same task at 2.6ghz. Big edge for slower cores, right? Well, not as big as that, because the memory and bus and such ALSO use power when stepped up in speed, and keeping them stepped up longer uses a fair bit of power itself. Here is a big advantage of "racing to sleep" - the idea that there are efficiencies gained by letting the CPU, GPU and everything else cycle back to resting states more quickly. In addition, non-app operations, like hotplugging in and out, consume power but don't get any work done.

Running 4 cores seems to work well for me, giving good performance while also a) letting the system race to sleep more quickly, b) not using any power to handle hot-plugging and c) needing to cycle cores up to high frequencies somewhat less frequently. Your mileage may vary, of course. Plus, all of this ignores one very important thing:

The display on this phone is by far the biggest consumer of energy. And no kernel is going to change that.

All of that said, I get a full day of moderate to heavy use every day (actually got two days recently of light-to-moderate use) running with 4 cores always on, and what more does anyone expect from a modern smartphone? Sure, gaming will kill the thing, but no faster than gaming always kills a phone.
[Nexus 6  Original Android Development] franciscofranco:
As I said before, if you guys think it's not onlining cpus as much as you'd like you can change the behaviour... just change load_threshold to 90 or something... you don't need my permission to change it.

I think you should try and reach your own conclusions based on your usage! ;)

Probably notification sound when the device is sleeping or something. Don't pay attention to it.
[Nexus 6  Original Android Development] bpdev:
Flar2 posted a process which is permanent and works for any kernel. (as long as you are using SuperSu)

[MENTION=3292224]franciscofranco[/MENTION] that's what they were talking about
[Nexus 6  Original Android Development] yoyoz808:
[MENTION=3292224]franciscofranco[/MENTION]

I've been noticing while playing music and browse the web at the same time, music volume goes soft like it starts to decrease and when I switch back to the music player, volume increases. Its a big difference in sound and was wondering of that DSP patch u used might cause that?

edit: can't reproduce it after I rebooted. I'll get back to u on this if I can reproduce.
[Nexus 6  Original Android Development] franciscofranco:
Might be a bug on the DSP. The patch that I merged doesn't touch that, it just allows for buffers that are not power of 2 to be used.
[Nexus 6  Original Android Development] franciscofranco:
They can use it if they want... it has nothing to do with the Kernel.
[Nexus 6  Original Android Development] tommy0823:
Well, as far as I'm concerned, [MENTION=3292224]franciscofranco[/MENTION], you're the man. Between Franco's kernel, and the occasional switch to lean kernel, I get consistent cycles like this. This is from last night. And the WiFi bar is inaccurate. I forgot to disable "always search for WiFi". I was actually out most of the day, as you can tell from my signal. My settings are 300min, 1728 max, and I set the GPU to 500. Performance is still spectacular, nothing lags, games work fine, movies play flawlessly. I've had nexus devices since the ns4g, and have never really strayed from these two kernels. I've used others, but always wind up here. I don't participate in this thread too often, but I'm always lurking. Never really have a reason to complain. So anyways, thank you Franco for all the work you put in on this, as well as fku.
[Nexus 6  Original Android Development] jiv101:
Hey Franco i was just wondering, love the kernel and it has produced some of the best battery life and buttery smooth performance then i could say but will you ever implement the vibration on the double tap to wake feature.
[Nexus 6  Original Android Development] franciscofranco:
Nah, don't count on it, I don't plan to touch any of the double tap to wake code from Google/Motorola.
[Nexus 6  Original Android Development] franciscofranco:
https://plus.google.com/u/0/106873500108976028532/posts/WfS1GVQ9tDR
[Nexus 6  Original Android Development] blueren:
Hi [MENTION=3292224]franciscofranco[/MENTION]-- I'd like to give some feedback...

Whats the difference between power-saver performance profile and the newly introduced battery saver? Are they the same?

The persistent Orange box which tells you how to automate performance profile .. it's a little too strong for the eyes. Something about it kinda breaks the overall aesthetics. Given that most normal users don't use it, why not make hidden it within a wrapper or something?

Something similar to the new looks of the per app more. Here, people who use it, already know what each option does. So why keep the instructions always persistent? Wouldn't it be better to have a "?" which says what each is or maybe keep it as a one time feature which tells you what each is when you first install the app? The block of colors is again breaking the subtle aesthetics of the app.

I'm sure you have valid reasons for these, but this is just my feedback.

Thanks!
[Nexus 6  Original Android Development] big_adventure:
New version seems to be working fine - though I never had real issues with the old one.
[Nexus 6  Original Android Development] instinctkiller:
New version is running fine !

Very nice to see the wakelocks toggle :) Nice update... The app feels faster than the previous one, lighter.
[Nexus 6  Original Android Development] jodvova:
Can anyone explain how can I access a beta channel?
[Nexus 6  Original Android Development] Amos91:
How do I get the beta version of the app?

Tried accessing the beta channel here but it errors out:

https://play.google.com/apps/testing/com.franco.kernel
[Nexus 6  Original Android Development] jodvova:
You need to join Franco kernel community on G+ for this link to work.
[Nexus 6  Original Android Development] Amos91:
Ah yes of course! I follow Francisco but forgot about that page too.
[Nexus 6  Original Android Development] GregNexus:
Is there a fix for the auto flash function in the file manager? (In the beta)

I tried the beta once, the first thing i noticed was the improved performance of the FKU.

But: i have set the battery saver via the Franco kernel to 15%

Once my device was reaching the 15% it was shutting down because the device was thinking that the battery was empty... This was the first time ever this happend to me while using this kernel. Dont know if this is this related to the battery saver setting at 15%? Some other people had the problem too in this thread that there was an to early shutdown

And is this possible via the kernel, or you need a custom kernel for this?:

If you turn on the original orange battery saver mode in the battery settings, that this mode will use francos settings for the savings?
[Nexus 6  Original Android Development] SmokeyMon:
tasker intents

Guys,

I just started using tasker. I'm having getting the intents for the performance profile intents to work. Can someone who is using them help a brother out?
[Nexus 6  Original Android Development] CRXed:
This morning my device did a shutddown too, when it reached 5% and battery saver kicked in.

Normally it would just continue to work untill it reached 0%

this is with R16 and normal Play Store FKU

---------- Post added at 02:20 PM ---------- Previous post was at 02:17 PM ----------

Grabbed a log, it is happening every time if I open FKU from the notification:

--------- beginning of crash
E/AndroidRuntime(12093): FATAL EXCEPTION: main
E/AndroidRuntime(12093): Process: com.franco.kernel, PID: 12093
E/AndroidRuntime(12093): java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.String.endsWith(java.lang.String)' on a null object reference
E/AndroidRuntime(12093):	at com.franco.kernel.c.p.a(SourceFile:72)
E/AndroidRuntime(12093):	at com.franco.kernel.c.p.a(SourceFile:387)
E/AndroidRuntime(12093):	at com.franco.kernel.an.onClick(SourceFile:88)
E/AndroidRuntime(12093):	at android.view.View.performClick(View.java:4756)
E/AndroidRuntime(12093):	at android.view.View$PerformClick.run(View.java:19749)
E/AndroidRuntime(12093):	at android.os.Handler.handleCallback(Handler.java:739)
E/AndroidRuntime(12093):	at android.os.Handler.dispatchMessage(Handler.java:95)
E/AndroidRuntime(12093):	at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime(12093):	at android.app.ActivityThread.main(ActivityThread.java:5221)
E/AndroidRuntime(12093):	at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime(12093):	at java.lang.reflect.Method.invoke(Method.java:372)
E/AndroidRuntime(12093):	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:899)
E/AndroidRuntime(12093):	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:694)
W/ActivityManager( 783): Force finishing activity com.franco.kernel/.KernelDownload
[Nexus 6  Original Android Development] githyanki:
Try r17
[Nexus 6  Original Android Development] GregNexus:
This happend to me with r17, but with the new FKU Beta.

---------- Post added at 03:56 PM ---------- Previous post was at 03:40 PM ----------

If you open and close the sidebar in the fku on the left side with the button, there is sometimes not a very smooth animation (you have to look very close, but this isnt a real issue for me):)
[Nexus 6  Original Android Development] hdtechk:
[MENTION=2269140]CRXed[/MENTION] Phone shutting down before empty sounds like battery calibration. Go into TWRP wipe battery stats. Reboot Then run phone tell it dies. Then charge tell full
[Nexus 6  Original Android Development] dcoy82:
Good morning Francisco. Just wanted to follow up with you about the split screen problem. After my original message, I started getting the split screen more and more frequently, especially when watching YouTube. It got to the point that YouTube would freeze half the screen every minute or so. So I decided to flash the stock kernel (didn't wipe phone, I'm still rooted and unlocked) and I'm going on almost 24 hours now without a split screen freeze up. I just finished a 45 minutes YouTube video with no freezes. I'm going to go another day on stock kernel to see if I continue getting none then flash back to Franco to see what happens. I'm know it's a hardware issue but it seems like something with the kernel isn't agreeing with the gpu flaw where the stock kernel seems to ignore the gpu flaw.
[Nexus 6  Original Android Development] franciscofranco:
1 - The battery saver just toggles Power-saving when it reaches the threshold that you define. If it's not explicit enough I'll add a "?" next to it

2 - I kinda like it to be honest, but yes I can add something to hide/show

3 - I took the idea from Newstand, where they use similar blocks of color/data. So far I only got favorable feedback, but I'll think about what you said and see if there's anything I can do to improve it if users don't want to read the description.

Thanks!

Auto-flash function on the File Manager? You can auto-flash .imgs just fine.

I think that's just poor battery calibration - I mean, Android must be wrongly calculating the remaining battery, so it shows 15% but in reality it's 0%. I've seen similar reports on stock Kernel from a few users

Android battery saver and FKUpdater battery saver are independent from each other.

What exactly is the problem? We can't help if you don't specify what's going wrong ;)

I fixed that FC on the latest BETA, I managed to reproduce it and it was, in fact, a big **** on my end, I forgot to send some intent's data to the activity from the notification :)

Hmm I don't see any lag on the animation. It's using the same code as Google does on their apps :/
[Nexus 6  Original Android Development] SmokeyMon:
Re : tasker

I can't seem to send the intent com.franco.kernel.POWER_SAVING

With the tasker profile of screen off. I admit I am not versed in the tasker app yet just trying to learn it. I am targeting activity I assume? Aside from the intent name and target I have changed nothing else.
[Nexus 6  Original Android Development] Circaflex:
Snakeoil wiping battery stats does nothing, same with calibrating
[Nexus 6  Original Android Development] blueren:
You're the boss. Had the entire app followed chunky blocks of colours, it would've been uniform. Just having a single subsection of the app throw up blobs of colours and blocks kinda makes it a deviant :)
[Nexus 6  Original Android Development] franciscofranco:
Well... 100% uniformity can be a little boring too. If it follows a similar design language I don't think it hurts by spicing things a little :)
[Nexus 6  Original Android Development] flar2:
I am affected by the split screen problem too. I believe it is a hardware defect. From what I gather, it happens more often when the phone is cold (I can't use mine outside or it happens every 30 seconds). It also happens less often when using the interactive governor, so I switch to interactive sometimes. Stock uses interactive, so it will not happen as often with the stock kernel, but it absolutely does occur on a completely stock setup (mine did it the first time I powered it on!). I want to replace/repair my phone under warranty, but I don't want to be without it for several weeks. Others have gotten replacements for this problem.
[Nexus 6  Original Android Development] dcoy82:
Yea I'm trying not to replace mine if I don't have to either. I had the phone about 2 weeks on stock kernel (rooted and unlocked) but never got a split screen. When I flashed Franco I got my first one within a couple of hours and they seemed to happen more and more frequently. After about two days of it I flashed back to stock and have yet to get another one. All the times I received one was when the phone was warm or being used frequently, not cold. It's like 18 degrees outside right now I'm going to take it out and try to watch a YouTube video out there and see what happens on stock.
[Nexus 6  Original Android Development] Circaflex:
I also had the split screen problem on my Tmobile Shamu, it was probably one of the first few batches; I RMA'd the phone and since then I haven't had an issue at all with the new one.
[Nexus 6  Original Android Development] flar2:
[MENTION=3821325]dcoy82[/MENTION]

Definitely get a replacement if you can, the problem will get worse over time
[Nexus 6  Original Android Development] simms22:
wrong thread i posted into :angel:
[Nexus 6  Original Android Development] franciscofranco:
Heretic!
[Nexus 6  Original Android Development] simms22:
i ended up answering a question that was asked several weeks ago :angel:
[Nexus 6  Original Android Development] franciscofranco:
You're, officially, forgiven.
[Nexus 6  Original Android Development] CRXed:
But not .zip files, that is the bug he is referring to.

Please remove the Auto-flash option in the menu for zip files, or more people will end up without a kernel when trying it.
[Nexus 6  Original Android Development] franciscofranco:
I removed it on the latest beta.
[Nexus 6  Original Android Development] GaSpartacus:
Beta FKU running great ;) great job

Enviado do meu Nexus 6 através de Tapatalk
[Nexus 6  Original Android Development] grayskul:
I had this problem and replaced it real quick.
[Nexus 6  Original Android Development] androidobsessed:
I only saw a couple about the qi charger (from people who had issues with it). It seems great if it works, so I just wanna check that it does before I buy one
[Nexus 6  Original Android Development] SmokeyMon:
[MENTION=3292224]franciscofranco[/MENTION]

Sick work my man. Your kernel and chroma ROM. I'm sitting 33 percent and have logged almost 5 hours SOT. For reference that used to be a full cycle for me. No UC no UV. I also have crap 4g signal and have to push exchange for work. Its becoming absurd. So thanks grealty.
[Nexus 6  Original Android Development] xXghostXx313:
Anybody settings Dont stick in fku? My phone turn off and when I turn it on, All the setting seem to revert back to default. I think it might be because I keep restoring the app with titanium backup. I just wipe the app data to see if it can fix it.

Edit: I think it might of been the ROM fault because something's reverted back wtf?
[Nexus 6  Original Android Development] franciscofranco:
I'd like to appologise to those users who reported that cpu2 and cpu3 were not onlining as often as before, in fact they were almost static. I was doing some thorough tests and I can concur that I seem to have introduced a bug on r16 (that persisted to r17) that made this happen. I'll fix it for r18.

In the mean time you can change some settings to emulate older behaviour:

high_load_counter: 3

load_threshold: 80

That should help it.
[Nexus 6  Original Android Development] schizophrenia:
"r" is experimental anyway. no worry. looking forward to a new r. thanks
[Nexus 6  Original Android Development] jodvova:
Thanks Franco
[Nexus 6  Original Android Development] franciscofranco:
**** now that I'm out savoca made his Qcom display control code compatible with the N6! Sorry folks, you gotta hang on for a couple hours, I won't be home soon.
[Nexus 6  Original Android Development] anthonyg45157:
**** yeah! Lets see it! What are the benefits? Gamma control?

Edit saw the thread. Looks awesome! Intrested in seeing how much it can make shamu look.

Sent from my Nexus 6
[Nexus 6  Original Android Development] C00lBeanz:
And I just resurrected my cat!
[Nexus 6  Original Android Development] rignfool:
I think your obsession with cats in a little unhealthy...
[Nexus 6  Original Android Development] Tzfardaya:
I think your obsession with not cats is a little unhealthy...
[Nexus 6  Original Android Development] nexicon:
Thank God. My phone has been running poorly. I can't wait for 18
[Nexus 6  Original Android Development] Janzen254:
It was

high_load_counter: 20

load_threshold: 98

before r16. If that is what you mean by a bug. I do not remember which release it was when defaulted to that but I think it was before r15.
[Nexus 6  Original Android Development] biggiestuff:
I've always had problems staying connected to my power pack micro when I was stock and rooted. After flashing Franco since r13 I've just now noticed my power pack micro stays connected all the time now. Is there something in the Franco kernel that could have fixed it?
[Nexus 6  Original Android Development] Utini:
I am on r17 with latest chroma build an have a problem with the "charging led":

When " charging led" in kernel settings is off then a blue led is on while charging (which is red when battery is below 15%). How ever when enabling "charging led" then the blue led as well as a green led are on. So I want to turn off the charging led but that only disables a green led while the blue one is still active while charging?
[Nexus 6  Original Android Development] adrman:
The blue one is built into chroma. You can change the color on the charging led in the rom settings to black.
[Nexus 6  Original Android Development] Utini:
Aaahhh thanks a lot ! :D
[Nexus 6  Original Android Development] cobyman7035:
does anyone else experience LED blinking blips? i think it only happens on certain chargers and amp rates i think

< blink , blink , blink, *longer blip blink*, repeat >
[Nexus 6  Original Android Development] SaZh047:
Would you mind sharing your kernel set up? :)

Thanks a lot...