yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] Krunk83:
Yeah I'm still on beta r11. Just had an issue with Wi-Fi though where it showed connection but I had no service. When I left the house it still showed I was connected even though I was miles away from my Wi-Fi. Just got back home and still wouldn't connect. Reboot fixed the connection. Bug or just a fluke? Dunno.

As far as stuttering, none yet.

Nexus 6
[Nexus 6  Original Android Development] franciscofranco:
Fluke. Wi-Fi is ****ed to begin with anyway.
[Nexus 6  Original Android Development] MrMaverick03:
I didn't mean it that way, I understand it is not your kernel's fault. I was just looking for guidance on an out of the box way to trim Chrome's usage. I will probably just find a browser that doesn't put all four cores on full power when using it. I think Chrome is overstepping its bounds by leaving core 2 and 3 on full throttle even after backing out of the app.

Nothing but respect for your time and work on these kernels. Franco is always my go to on my Nexus family.
[Nexus 6  Original Android Development] franciscofranco:
Ah sorry, I misinterpreted. Toggle that option that I told you and you'll be able to see what process if ****ing you. I'm sure your device is pretty hot during usage. As soon as you understand which process is doing it you'll easily troubleshoot it.
[Nexus 6  Original Android Development] SweetwaterBurns:
It's a bug in trickstermod that causes it, at least from my experience. Not sure if it happens with other kernels or just this one. To check if you're seeing the same bug I did, turn off set on boot and restart and it shouldn't lock those cores to the higher frequency. As soon as you change and apply any cpu settings in trickster, the cores will start locking again.
[Nexus 6  Original Android Development] MrMaverick03:
So far I haven't made any mods to franco's kernel. Everything works well as is. I just use trickster periodically to check the core's usage. Actually went back and deleted chrome, data and cache and the problem has seemed to stop for now. Thanks for the help everyone, I will let you know if the issue persists.
[Nexus 6  Original Android Development] MrMaverick03:
Core

[MENTION=3292224]franciscofranco[/MENTION] Attached is my screenshot of what you told me to do. The top right cpu info shows no real usage of chrome but trickster shows that the last two cores are maxxed out. This is what had me freaking out. Hope this helps what I poorly explained earlier.
[Nexus 6  Original Android Development] simms22:
use a live cpu use app to check out your cores online, dont use trickster. i like the perfmon app.
[Nexus 6  Original Android Development] Janzen254:
I like Christian Göllner's System Monitor.
[Nexus 6  Original Android Development] MrMaverick03:
Thank you everyone!

Went ahead and did a few things to remedy the core 2 and 3 issue. First off bought FKU Updater as a thanks for your work, second downloaded the system moniton from Christian and watched the activity for a while. Decided the best option was to run Vomer's Dynamic settings to cool off the last two cores unless absolutely necessary. Thanks again for the advice everyone.
[Nexus 6  Original Android Development] franciscofranco:
First of all thanks.

The part that I bolded is not a fix, it's just a bandaid, you should first try and understand where exactly is that load coming from, System Monitor has a page that shows the apps that are using the CPU, you should start there and figure it out.
[Nexus 6  Original Android Development] franciscofranco:
Pushed r11, more a maintenance release than anything. Changes do not affect battery life so if you come crying about something related to that compared to rXXX release, you can kick yourself in the balls.
[Nexus 6  Original Android Development] erraggy:
Just be sure to deflate them first. Then feel free to kick away.
[Nexus 6  Original Android Development] mazubo:
Instructions duly noted! :D:D:D
[Nexus 6  Original Android Development] warrenis1234:
at the risk of maintaining OT, the only issue I've seen from disabling animations is in hangouts. when you send a message, the text area moving up to show that new message in line is an animation, so it doesn't move. minor annoyance. I think only 1 of the 3 animation options is responsible however
[Nexus 6  Original Android Development] dmeadows013:
Franco, battery life on r11 is EXACTLY the same is r10 it should be better y u no fix my cat is sad plz make it better now kthxbai
[Nexus 6  Original Android Development] pinoyflayv:
Deflategate, Go Shehawks!!!
[Nexus 6  Original Android Development] paychex:
The part I bolded is not a fix; it's just a bandaid
[Nexus 6  Original Android Development] hdtechk:
Stupid movie I'm casting to my TV won't end so I can flash
[Nexus 6  Original Android Development] Downy:
Still no 127 vib strenght possible :( do I have to wait for a kernel or a FKU update to make that possible? Or can it be set manually in any way? That would also be OK :)

Beside that, r10 and now r11 running great, best to get for Nex6!
[Nexus 6  Original Android Development] samdroid24:
Lmaaaaaaaooooooooooo

You sir, are a legend

Btw, I get faster battery drain on R11 than R10, what the hell is up with that?
[Nexus 6  Original Android Development] franciscofranco:
Yes you can use 127, check my git.
[Nexus 6  Original Android Development] ultravorx:
So I'm still having issues with the charging led turning back on after boot.

Per suggestions I changed some settings in chroma notifications, however its the fku that keeps turning on the charging led. Anytime I reboot, the setting doesn't stick.

Any ideas?

Frank
[Nexus 6  Original Android Development] wrongway213:
No other kernel tweaker like trickster installed? No Lightflow? You already said you turned off battery LED in Chroma so not a ROM issue, dunno what else it would be as long as you have it disabled and set on boot, works fine here.
[Nexus 6  Original Android Development] bowser001:
I had the same exact issue and it only happens when I install Franco's Kernal via the FKU app. Currently not having this issue and also don't have the latest Kernal version 11 installed. I just clean installed CR 1.4.0 with no kernal update, but planning to flash Franco's latest. Will report back. Just to clarify I didn't have the “charging led box” inside settings of the app checked when I was having the issue.
[Nexus 6  Original Android Development] franciscofranco:
Sorry can't help you, FKUpdater set on boot works flawlessly for me and I can't reproduce anything wrong with it.

Sent from my Nexus 9
[Nexus 6  Original Android Development] franciscofranco:
I've seen that happening. My guess is that I'm not doing a conventional System reboot (to do that my app would have to be a system signed app, which only Google apps are), after it's booted up Android does not broadcast BOOT_COMPLETED then the set on boot service doesn't start. I'm guessing a bit, but I've seen this happen.
[Nexus 6  Original Android Development] michmeister:
Go patriots! Deflatefgate a freaking joke.
[Nexus 6  Original Android Development] paychex:
Your whole team is a joke. Serial cheaters
[Nexus 6  Original Android Development] BigCrisco39:
Who cares about football. They only play 11 minutes of actual play time.

http://www.sportsgrid.com/nfl/pie-c...watching-nfl-game-vs-replays-commercials-etc/

Let's just get back to watching hockey.

:)
[Nexus 6  Original Android Development] TheySaidWhat?!:
lightflow

The app has always updated for me since I got the kernel in r6. And when light flow didn't work after a flash in the past I would uninstall then re-install and boom, my LED's are fine. I tried r11 and light flow doesn't function after repeating the above. Flashed r10 and it functioned.

Can anyone suggest what I should troubleshoot for the latest release to function with light flow? I'll sacrifice light flow til r12 if I have to but I would like to know any "pro tips" I may have missed if any.
[Nexus 6  Original Android Development] wrongway213:
You have to set it up again when changing kernels or sometimes when a new release for the kernel changes something, I don't know what. I've been able to flash since r6 as well without clearing Light Flow app data. For r11, you need to set Light Flow up again. Go into Light Flow --> app info and delete app data, then set it back up again, it will work.

Edit: Just for completeness's sake, if you ever flash another ROM you will always have to set Light Flow up. If you switch ROMs or kernels often I find it helpful to back up your Light Flow settings in Light Flow's settings menu and then restore them as needed instead of setting it all up again multiple times daily.
[Nexus 6  Original Android Development] Tzfardaya:
Manually resetting light flow up works, restoring backup config doesn't always...
[Nexus 6  Original Android Development] pwned3:
Hey I remember you from the rezound forums i think. How's things been going

Sent from my Nexus 6 using Xparent Skyblue Tapatalk 2
[Nexus 6  Original Android Development] TheySaidWhat?!:
Thanks for the tips. I had backed up r10 already and tried restoring it after flashing 11, but to no avail for me. However, manually configuring the app from scratch afterwards worked!? But the clearing app data tip you gave me is quicker than going to the play store to un & re-install. And made life a bit easier, I appreciate that!

---------- Post added at 05:10 PM ---------- Previous post was at 05:05 PM ----------

Thanks for the input! Yes indeed it's working now. I'm relieved I don't have to sacrifice anything now ;)

I don't know why doing it manually altogether didn't occur to me earlier - oops. But the friendly reminder came in handy and all is well for my Nexus 6!
[Nexus 6  Original Android Development] suku_patel_22:
Set on boot wasn't working for me on Stock ROM. After switching to Chroma, it has started working for me.

Try a factory reset.

Maybe it was just the factory reset, and Chroma has nothing to do with it.
[Nexus 6  Original Android Development] Downy:
I checked your git, found a lot of well explained descriptions but not that one point for vibration strength. Do I need to compile a copy of your kernel based on the git sources with the change?

Sorry, I'm little confused...
[Nexus 6  Original Android Development] franciscofranco:
https://github.com/franciscofranco/Shamu/commit/e0ef15c9f0c547092c23e09fc39477249ea00189

You can already use a vibration up to 127 with r11, you can use my app or just echo it through terminal/adb/whatever :)
[Nexus 6  Original Android Development] michmeister:
Raven are a bunch of cry baby tattletales. Sore losers. Lol. Go pats. Everyone hates a winner.

Sorry. No more football talk.
[Nexus 6  Original Android Development] Tzfardaya:
Franciscofranco, did the path to the charging led mutate a bit? It used to be f002ee00, now f0030e00? Is this drift common, or?
[Nexus 6  Original Android Development] paychex:
1. Who says I'm a Ravens fan?

2. You appear to be trying to make the "two wrongs" argument. So you have no real retort.

3. Throwing in your reply then deciding "no more football talk" is a ***** move--basically a written sucker punch. Not surprised, seeing who you root for.
[Nexus 6  Original Android Development] Circaflex:
if you think the pats are the only team cheating/doing anything to win at all costs you're delusional.

now back to the topic at hand, so far R11 running smooth on my AOSPA build, thanks for the hard work
[Nexus 6  Original Android Development] Skripka:
It is...I actually know the guy who wrote the book on the Physics of Football....who actually worked for the Patriots organization under Belicheck for a while.

Colts didn't loose due to cheating...they lost because they were not the best team. Heck the Colts didn't even really seem to show up to the field. Cheating or what have you had little to do with that.
[Nexus 6  Original Android Development] paychex:
That would mean the Pats are the worst team in the league at cheating and I don't think that is true
[Nexus 6  Original Android Development] Circaflex:
I agree with you. Honestly, the media has blown the whole defaltegate out of hand. Did you see the sports science video regarding deflate-gate? Under-inflated balls in the range being talked about for this "scandal" have a miniscule/negligible effect on pretty much everything. They give minimal advantage for 'gripping' and a very minor disadvantage for ball velocity.

The rain sticking to the football had more than 10x the effect on ball weight and ability to grip as the PSI difference would have had.

There is literally almost no chance this had any effect on the outcome of this game, nor would it have mattered to almost any game that was decided by more than 1 point.

Here is the link, ESPN removed it from their sources because it says the opposite of what this media storm has said.

https://www.youtube.com/watch?v=VZ_S8F3mKFE&x-yt-cl=84503534&x-yt-ts=1421914688
[Nexus 6  Original Android Development] Skripka:
Tim's opinion is that it can provide an edge...but it is small, and only if you practice a heck of a lot with it:

http://www.amazon.com/The-Physics-Football-Bone-Crunching-Awe-Inspiring/dp/0060826347

Most of the physics pundits on the TV have gotten the whole thing wrong actually in explaining it. The whole thing isn't about gauge pressure (what people citing the NFL rules book measurements are using), it is about absolute pressure...which is a very different animal. That is what happens when you interview cosmologists (and otherwise very smart specialists) like de Grasse Tyson on mundane matters like football inflation :) . Funny part is that Tim wrote the book, but no media outlet bothered asking him (the expert) until this last week about it.
[Nexus 6  Original Android Development] michmeister:
I didn't say you were. And your very angry person. It's a sport a game no need to get personal and nasty geez. Now I know you must be ravens fan. Ignoring.

---------- Post added at 02:04 PM ---------- Previous post was at 01:58 PM ----------

Not to mention just about every ex qb say every quarterback manipulates ball to get the way they like. Some a little more as in Rodgers ans some like less. This is so much to do about nothing its laughable.
[Nexus 6  Original Android Development] franciscofranco:
No idea at all, I think that patch is generated automagically. I'll check if some of qualcomm's patches that I merged can influence that somehow, but it's indeed odd as ****.
[Nexus 6  Original Android Development] funcrusher:
No one is saying the colts would have won if the pats hadn't cheated (ridiculous). But rules are rules and the pats broke them, no?
[Nexus 6  Original Android Development] codygs83:
Really????

But what about Francisco's amazing kernel and the update that was just pushed?

Don't they have football threads elsewhere??
[Nexus 6  Original Android Development] funcrusher:
This thread doesn't need new dev disciples.
[Nexus 6  Original Android Development] simms22:
not on xda. so, at the moment, this is the only "football" thread on xda.
[Nexus 6  Original Android Development] franciscofranco:
It's fine, as long as it's constructive conversation that doesn't block Kernel issues or someone asking for help I'm fine with it, as explicitly said in the OP :)
[Nexus 6  Original Android Development] old_fart:
Hey Franco, can you add in a 'core control', so you can select : one / two / four override ?

( More for the core, ooh raah, drop and give me fifty ( pushups ) ) . . .
[Nexus 6  Original Android Development] franciscofranco:
Nope. That's a finer grain control that I don't want to expose. Less than 2 cores online -> no chance that would ever happen. If you want only 2 cores change my driver's load_threshold to 100. If you want full quad core set it to 0. That's all that there is, I don't plan on giving any type of control that can break existing code functionality.
[Nexus 6  Original Android Development] ShadyBooster:
Charging Led

Previously I could change the color of my led with light flow. But now, it seems that it's locked green. Also, in my app there isn't even an option to disable the notification led like I have been seeing in this thread.
[Nexus 6  Original Android Development] Circaflex:
clear lightflow data and setup again.
[Nexus 6  Original Android Development] CRXed:
Auto-flash works awesome, but manually flashing with the FKU app through the built-in file explorer, after downloading the zip, still leaves you without a kernel. See screenshots.First screenhot is what you see right after FKU reboots your phone.

NOTE1: I do not have a custom recovery.

NOTE2: no need to tell me I need to use TWRP or anything else, I just want to report this kinda huge bug.
[Nexus 6  Original Android Development] kergefarkas:
it might be there only in the paid version

cm just added led control, that interferes with trickster settings as well. maybe lightflow as well.
[Nexus 6  Original Android Development] Circaflex:
but don't you need a custom recovery for FKU to send the openrecovery script to the recovery in order to flash? I think so because I just flashed a zip using filemanager in FKU and it boots fine for me
[Nexus 6  Original Android Development] CRXed:
I don't know, I don't need a custom recovery to use Auto-flash apparently....
[Nexus 6  Original Android Development] franciscofranco:
Wow that... shouldn't happen, ever... I use the same code for Auto-Flash as I use for the flash through the File Manager. I'm so sorry for the bad experience, Auto-Flash is the core of the app and was why I started it 3 years ago. I'm going to try to reproduce that bug on my devices.

EDIT: wait a sec, you tried to flash a .zip through the File Manager? Can you explain in a bit more detail what were your steps?
[Nexus 6  Original Android Development] simms22:
manually flashing.. i wont tell you, but you do need any other recovery but the stock recovery. the bug is that you arent using one.
[Nexus 6  Original Android Development] Jleech330:
I've tried clearing data and cache. Reinstalling. Light flow still not working
[Nexus 6  Original Android Development] CRXed:
I open the FKU app

I use the ZIP D/L option

I get a notification that it is downloaded successfully

I go to the File Manager in FKU

I find the downloaded zip, it's always on the root of the sdcard

I tap the zip file

I tap the Auto-flash option

Phone is rebooted to the recovery screen and kernel is gone
[Nexus 6  Original Android Development] paychex:
it's not a bug. It's pretty much common knowledge that you need a custom recovery to flash zip files
[Nexus 6  Original Android Development] CRXed:
The FKU app can auto-flash without a custom recovery, so if that option is presented though the in-built file manager, it should not leave a user without a kernel.
[Nexus 6  Original Android Development] despisedIcon:
This exact issue happened to me when flashing through file manager. Had to boot into TWRP and manually flash the zip.

---------- Post added at 10:01 PM ---------- Previous post was at 10:00 PM ----------

This is incorrect. It also occured on my device which has TWRP recovery.
[Nexus 6  Original Android Development] grayskul:
Have you done it that way before? If not get the latest TWRP and then try again.
[Nexus 6  Original Android Development] Circaflex:
the command is different, its essentially doing a fastboot flash of an img file, if you manually flash .img files you don't need a custom recovery, zips on the otherhand are another story.
[Nexus 6  Original Android Development] ShadyBooster:
Did that, have that

Still not working. Oh well, I might just go back to r10 while/if this gets a fix then.
[Nexus 6  Original Android Development] CRXed:
I see your point.

Then the bug is that the FKU app presents an Auto-flash option in the File Manager and actually executes it, on a downloaded zip.

It does not unzip the file apparently.
[Nexus 6  Original Android Development] wrongway213:
there will be no fix, light flow works on r11 just as it did on r10, clear app data and start from scratch or if that doesn't work (it should but you're saying it doesn't) uninstall, reinstall and set up that way. it works, i did it today, it's been the same for all kernel and ROM updates.. you can just stay on one lightflow set of settings for a while if you never update ROM and stay on the same kernel is what gets people confused.
[Nexus 6  Original Android Development] old_fart:
same for me ! does it take a 'total wipe' ? But hey, that ( across the pond ) lightflow dev was ( maybe ) going to add in some fixes that imoseyon showed him . . .
[Nexus 6  Original Android Development] Tzfardaya:
All I know guys is that I'm on r11 (stock rom/decrypted) and lightflow is working here..

Just had to wipe the app data/cache in android app settings and reconfigure.
[Nexus 6  Original Android Development] paychex:
It can auto-flash .img files

---------- Post added at 04:36 PM ---------- Previous post was at 04:33 PM ----------

Well that would be a bug. But that's not what I said. Without a custom recovery he would be sol either way
[Nexus 6  Original Android Development] ShadyBooster:
the notification led works for me, I just can't change the color of the charging led.
[Nexus 6  Original Android Development] BigCrisco39:
OK, quick question.

Does Lightflow actually give you a "notification light" ie. blink or does it just turn it on?

Can you change the color for different notifications?
[Nexus 6  Original Android Development] Tzfardaya:
They're two different leds... If you're trying to use lightflow to change the colour, set the charging led brightness to 0 in fku, then use lightflow to pick your colour.
[Nexus 6  Original Android Development] ShadyBooster:
yes, it just turns on. you can only choose from red,green,blue,light blue.

---------- Post added at 10:28 PM ---------- Previous post was at 10:22 PM ----------

that option is nonexistent in my franco app, and yes it's not the free one.

I got my led to change color again, at first I wiped data then uninstalled which resulted in the same green but, after doing the process again and selecting wipe from all users (don't know if that makes a difference since no others had it) it suddenly worked again.
[Nexus 6  Original Android Development] Tzfardaya:
No Kernel settings -> charging LED?
[Nexus 6  Original Android Development] dmeadows013:
Yeah I remember you as well. Been busy, but good. You?
[Nexus 6  Original Android Development] CRXed:
It also gives the Auto-flash option on zips = bug

I'm not SOL....I got a working device, because there is something like terminal commands.

Apparantly saying "don't tell me I need a custom recovery" triggers people to tell me exactly that.... :rolleyes:
[Nexus 6  Original Android Development] michmeister:
Lightflow works fine on 11
[Nexus 6  Original Android Development] ShadyBooster:
Nope
[Nexus 6  Original Android Development] Tzfardaya:
Wait.. You're missing a few options..

Can you post your fku kernel and support pages? When was the last time you updated fku?
[Nexus 6  Original Android Development] paychex:
It's not a bug! Use a custom recovery or stop complaining--especially cause you can use "something like terminal commands". And yeah, if you want to auto-flash zip files without a custom recovery--you are SOL
[Nexus 6  Original Android Development] franciscofranco:
Hey, calm your tits, it's a bug alright, just checked my code and there's a **** on my switch clause. It's a legitimate bug report, let's not scare off users that spend time to report bugs with detail and with a reproducible case ;)
[Nexus 6  Original Android Development] C00lBeanz:
Nice :)
[Nexus 6  Original Android Development] ShadyBooster:
Op
[Nexus 6  Original Android Development] Tzfardaya:
Missed an update had you?
[Nexus 6  Original Android Development] blueren:
Given that the cream of N6 population is in this thread, I'd dare ask a completely off topic question --- how are your back covers looking? Getting the infamous cover-popping-off issues due to battery puff / weak glue?
[Nexus 6  Original Android Development] gamewarden234:
Got mine two days before release on November 19 I think. Just took my cover off and don't have any issues. Or my wives.. Maybe because it's been in a case since day one?