yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] Cy_n_ic:
In the OP are instructions for using lkconfig to tweak some aspects of the kernel not available in the kernel apps. You will see the option to enable the power save feature we are speaking of and it is different than the cpu governor you screenshot. You can enable the power save and also select whatever governor from a kernel app. Lkconfig is not quite as robust as the stand alone apps but it does enough for me that i do not require one and actually prefer this method. It just feels more technical and geeky which i find more appealing.
[Nexus 6  Original Android Development] ggmask:
So it does, missed the first time through.

Thanks everyone :good:

---------- Post added at 01:18 AM ---------- Previous post was at 01:17 AM ----------

Sure I can see that, I just like the convenience of kernal apps, but every kernel I've tried always has something that isn't accessible via the apps and it always bugs me. Anyway I'm using the terminal app now and it's fine.
[Nexus 6  Original Android Development] Imoseyon:
So I spent a bit of time on this. I never tried Lightflow before so it's possible I'm using it wrong, but I can't get it work on any of the leankernel versions. It looks like the app is writing to leds-qpnp-f0049800 which doesn't exist on shamu. Are you sure this worked for you on v1.8?

And the app seems to FC a lot.
[Nexus 6  Original Android Development] akellar:
Just to make sure, you are using the paid app correct?
[Nexus 6  Original Android Development] Imoseyon:
lol is that difference? The free app doesn't work on nexus 6 at all?
[Nexus 6  Original Android Development] akellar:
Yeah unless something has changed since I looked last, the free version hasn't been updated in close to a year and doesn't work with n6
[Nexus 6  Original Android Development] Cy_n_ic:
Native LED is included in alot of the roms now. Could their be conflict between kernel, native led and lightflow all trying to do something at the same time? I never used lightflow so im just tossing ideas out there. Nobody mentioned what rom they are using or if it included native LED or whether it was disabled or not.
[Nexus 6  Original Android Development] merouleau:
I have not tried the Lite version, but I read somewhere that the paid version is required because of the tweaks needed to bring the N6's unsupported LED to life. LK 1.8 and earlier work very well for me. When I get back to my desk I'll kick in to cover the Light Flow cost and then some as I have not yet contributed. Thanks for having a look.
[Nexus 6  Original Android Development] Cy_n_ic:
Yea i think its root access thats required from lightflow to work with this devce, but the free version doesnt offer that function
[Nexus 6  Original Android Development] poczynek:
1.9 works fine for me on led with blisspop's own LED settings. I used to use light flow but no need now as the Rom has it inbuilt.
[Nexus 6  Original Android Development] Imoseyon:
Hmm unfortunately the paid app doesn't work for me either. Tried both v1.8 and v1.9. Perhaps there's a trick in getting this to work. I didn't see anything obvious in logcat either.
[Nexus 6  Original Android Development] franciscofranco:
Of course you don't see anything on logcat, since when do you know Java and Exceptions on Java? :angel:
[Nexus 6  Original Android Development] poczynek:
Yes did you try with Direct Mode and root mode and change the mixer?
[Nexus 6  Original Android Development] funcrusher:
Question:

So either disabling screen_off_maxfreq via lk config or setting it to your max frequency with trickster will restore factory image kernel behavior?
[Nexus 6  Original Android Development] arcanexvi:
For lightflow to work on shamu your settings should look like this (with notification access granted as well)
[Nexus 6  Original Android Development] poczynek:
Or just try blisspop where it's added into settings and no need for light flow.
[Nexus 6  Original Android Development] arcanexvi:
Or... as his kernel is designed for stock he can try to fix whatever changed since it used to work. Shouldn't have to switch ROMs to fix it. You mentioned this before but is an unreasonable suggestion for anyone who runs the stock + kernel combo since that is extremely popular right now.

I don't even use the notification light because it's not a very clean look or interface for this device but regardless, people shouldn't have to change ROMs.
[Nexus 6  Original Android Development] poczynek:
It was just a suggestion!
[Nexus 6  Original Android Development] merouleau:
Here are the settings that work for me:

General settings

Enable Light Flow

Show LED in Priority Mode

Enable "Clear All"

Accessibility check

Version upgrade reminder​

Persistent Icon - uncheck Run in foreground

Device Settings and Root

Direct mode

Root mode

Run every command as root

Nexus 5 force LED reset​

After testing all of the color combinations available with the LED Mixer, I decided to leave LED Mixer unchecked in all of my notifications and refrain from using even the pre-configured blends like cyan, orange, white, and purple. I think all of the color mixes look like kludges - red, green, and blue are the only settings that I find to be identifiable at a glance on the Nexus 6. Also, while I think it has worked in the past with charging LED on in lkconfig, I have been leaving that kernel setting off to avoid semantically overloading green. (I use green for non-urgent notifications like personal email and social media updates, blue for text messages and business email, and red for reminders, voice messages, and emergencies.)

I just tried 1.7, 1.6, and 1.5. They all worked. Then I flashed 1.9. It still doesn't work. Then I flashed 1.8. It works and is what I'm running now.

My test is

Notification settings

Make sure Calendar apps (all reminders) color is red

Press three vertical dots for Calendar apps (all reminders) and choose Settings

Press three vertical dots and choose Test

Wait five seconds with screen on and note red LED

Press CLOSE
​

I'm running CleanROM 1.2.5, which I perceive to be the LeanKernel of ROMs - it prioritizes stability, battery life, and performance over features and is probably the closest to stock of the Nexus 6 custom ROMs distributed via xda-developers.
[Nexus 6  Original Android Development] eggydrums:
My apologies if it's been asked already, but is theming still not fully functional? I managed to apply a theme but started getting force closes all over and had to revert
[Nexus 6  Original Android Development] beyeond:
I don't use cm or a Rom that has themes, but I thought that was fixed. It was discussed very recently in this thread... try a few pages back.
[Nexus 6  Original Android Development] nobnut:
The FCs are nothing to do with the kernel. The kernel issue was related to installing the theme in the first place.

As reported by CM, you should reboot after applying the theme as FCs are 'normal'.

Either that, or the theme you're trying to use is borked.
[Nexus 6  Original Android Development] Imoseyon:
Hey you should know that I once created a Java compiler from scratch! Looking through logcat sucks though - I only do this when there are reports of apps working on one leankernel version and not on another.

Well this is funny but with your settings I see notifications on both 1.8 and 1.9! lol what the heck. I'm on stock ROM though. I'll take another look at this.

EDIT: I thought maybe i had flashed a test version so I downloaded/flashed 1.9 again from my onedrive, and lightflow definitely works. I think previously I just missed the "direct mode" setting. Try reinstalling the app? (per [MENTION=6345907]NikWillOrStuff[/MENTION] below)

Most likely not the kernel, but if you can shoot me a logcat when it FC's. I may be able to see something there.
[Nexus 6  Original Android Development] Cy_n_ic:
I have heard that changing SELinux to permissive will remedy some theme engine issues. Their is an app in the play store to change SELinux status. Maybe try that.
[Nexus 6  Original Android Development] NikWillOrStuff:
hm, I had the LED problem when updating to 1.9, but I reinstalled lightflow and configured all the settings again and... it works again :eek:

settings I changed: turned off 'run in forground', turned on 'direct mode', 'root mode', and 'run every command as root' (everything else left default)

very strange
[Nexus 6  Original Android Development] Cy_n_ic:
I thought it was common knowledge to the lightflow peeps that if you install a new kernel that lightflow HAS to be reconfigured. Every time. Isnt this correct?
[Nexus 6  Original Android Development] Imoseyon:
I gotta say that there were a ton of selinux policy allows missing for the theme engine. It's possible that v1.9 is still missing a few. Logcat (grep for "avc" if you're using adb) will help.
[Nexus 6  Original Android Development] NikWillOrStuff:
well lightflow didn't bother me when upgrading from 1.6 to 1.7 to 1.8, so I didn't expect 1.9 to be any different. the more you know!

just some more info, I was running cyanogenmod through all this, updating it all the time
[Nexus 6  Original Android Development] old_fart:
removed and replaced lightflow and 'surprise', it is back making with the LED twinkle . . .

next is the logcat of when it is working . . .

01-21 22:17:49.398 323 337 E MP-Decision: Failed to reset optimization for resource: 1 level: 14

01-21 22:17:53.748 827 1041 E WifiStateMachine: WifiStateMachine CMD_START_SCAN source -2 txSuccessRate=0.00 rxSuccessRate=3.17 targetRoamBSSID=any RSSI=-47

01-21 22:17:53.749 827 1041 E WifiStateMachine: WifiStateMachine starting scan for "jhvihvvh3cf5"WPA_PSK with 2422

01-21 22:17:54.169 316 1062 E audio_a2dp_hw: adev_set_parameters: ERROR: set param called even when stream out is null

01-21 22:17:54.194 827 1041 E native : do suspend false

01-21 22:17:54.245 323 337 E MP-Decision: Failed to apply optimization for resource: 1 level: 14

01-21 22:17:54.245 323 337 E MP-Decision: Failed to apply optimization for resource: 2 level: 14

01-21 22:17:54.261 316 872 E ACDB-LOADER: Error: ACDB AFE returned = -19

01-21 22:17:54.513 316 1682 E audio_a2dp_hw: adev_set_parameters: ERROR: set param called even when stream out is null

01-21 22:17:54.521 827 1041 E native : do suspend true

01-21 22:17:54.782 3658 3658 E ProcessCpuTracker: Retrieving the UID for PID 4161 from the filestat didn't work - got a UID of: 0

01-21 22:17:57.247 323 337 E MP-Decision: Failed to reset optimization for resource: 2 level: 14

01-21 22:17:57.247 323 337 E MP-Decision: Failed to reset optimization for resource: 1 level: 14

01-21 22:17:57.813 827 864 E libsuspend: Error writing to /sys/power/state: Device or resource busy

01-21 22:18:43.003 3017 3035 E SQLiteLog: (284) automatic index on sqlite_sq_A3728880(STAT_DATA_ID)

01-21 22:18:43.075 1121 4350 E MediaPlayer: Should have subtitle controller already set

01-21 22:18:43.175 827 827 E NotificationService: Not posting notification with icon==0: Notification(pri=2 contentView=null vibrate=null sound=null defaults=0x0 flags=0x0 color=0xffd20300 category=alarm vis=PRIVATE)

01-21 22:18:43.175 827 827 E NotificationService: WARNING: In a future release this will crash the app: com.rageconsulting.android.lightflow

01-21 22:18:43.210 1121 4350 E MediaPlayer: Should have subtitle controller already set

01-21 22:18:43.221 316 872 E ACDB-LOADER: Error: ACDB AFE returned = -19

01-21 22:18:52.144 323 337 E MP-Decision: Failed to apply optimization for resource: 3 level: 2

01-21 22:18:52.144 323 337 E MP-Decision: Failed to apply optimization for resource: 1 level: 14

01-21 22:18:52.144 323 337 E MP-Decision: Failed to apply optimization for resource: 2 level: 14

01-21 22:18:52.180 316 1680 E audio_a2dp_hw: adev_set_parameters: ERROR: set param called even when stream out is null

01-21 22:18:52.211 827 1041 E native : do suspend false

01-21 22:18:52.401 827 1041 E WifiStateMachine: WifiStateMachine CMD_START_SCAN source -2 txSuccessRate=0.00 rxSuccessRate=0.00 targetRoamBSSID=any RSSI=-46

01-21 22:18:52.466 827 863 E libEGL : call to OpenGL ES API with no current context (logged once per thread)

01-21 22:18:54.296 316 872 E ACDB-LOADER: Error: ACDB AFE returned = -19
[Nexus 6  Original Android Development] nextelbuddy:
Is it possible to get a flashable zip of the stock kernel with flag encryption disabled? Last time I flashed the lean kernel 1.4 and went back to stock, the stock kernel zip include in the first post had encryption enabled and id like to not reencrypt my device again if possible.

Why is a stock kernel with encryption enabled included if the kernel we are flashing has it disabled?
[Nexus 6  Original Android Development] old_fart:
The description 'stock', means its really following what it says it is . . . But I agree with you. . A normal stock with the toggle 'on' and modified stock with the toggle 'off' should be easily available . . . . Hmmm, doesn't wugfresh's NRT give you that ?

.

And many users are wanting and going out of their way to stay encrypted . . . It's a badge of honour ! . The government CAN'T barge / snoop into their business.
[Nexus 6  Original Android Development] nextelbuddy:
In using trickster mod paid app and for the life of me can not get the cpu frequencies to change. Every time I set the min and Max to 233 min and 2.8 max and touch save.. The min and max immediately changes to 1.7ghz and my device status at those speeds. What gives? I've tried other speed and same results.
[Nexus 6  Original Android Development] Cy_n_ic:
Good thing your life doesn't rely on reading the OP otherwise you would be a dead droid...
[Nexus 6  Original Android Development] merouleau:
LightFlow and LK v1.9

Well, like Nik and old_fart, I was able to make LightFlow turn on LEDs on 1.9 by uninstalling and reinstalling. Unfortunately, I have 24 notifications with custom sound, vibration, and color settings, so it's time-consuming to reconfigure it from scratch. I tried some other solutions:

1. A data-only restore from Titanium Backup.

2. Configuration changes like unchecking / checking Enable Light Flow and Direct Mode.

3. Flash ElementalX v0.20.

4. Flash Franco r9.

Those didn't work, so I bit the bullet and reconfigured. Then, just for grins, I did the following:

1. Flash LK v1.8. For the first time, it does not work!

2. Flash ElementalX v0.20. It does not work.

3. Flash Franco r9. It does not work.

4 Flash LK v1.9. It still works.
[Nexus 6  Original Android Development] NikWillOrStuff:
maybe we can convince the dev to implement a "backup/restore notification data" button in the settings, but I think this is going a little off topic now :p
[Nexus 6  Original Android Development] modstorm:
LightFlow already has a Backup feature. Just go to Tools and you'll see it there :)
[Nexus 6  Original Android Development] franciscofranco:
I'll reduce myself to my own insignificance :)
[Nexus 6  Original Android Development] shelooga:
fixed my lightflow problems.

after i uninstalled and reinstalled 100 times, i uninstalled it last night again in a last ditch effort. then i was cleaning up my sd space a little and decided id delete the folder and backups. reinstalled this morning, voila! i hate re-doing every single notification settings, but i guess it gives me a chance to improve them
[Nexus 6  Original Android Development] beyeond:
Man I'm glad I don't use this light flow app or led notifications.. Sounds like a pain in the ass.
[Nexus 6  Original Android Development] old_fart:
At work, the phone is about a foot away from my left ear in my little work cubby . . . . So it'll do its " Brang ! " chime that'll scare the crap out of me and make me jump. I'm sure my cubby neighbor's are not too happy with the noise maker either. I need to locate a "mellow & soothing" chime repository and ditch this default one. But the jumpy noise one is not a bother ( maybe liked ) in the car and at home . . .
[Nexus 6  Original Android Development] oak:
Me too! Every thread on xda is cluttered with these is issues.
[Nexus 6  Original Android Development] Franzie3:
i recommend a better notification sound...

i have a quack from the character gunther from adventure time.....hysterical when peoples reactions when they hear a random quack

also good ones i have are:

final fantasy 7 victory theme

metal gear solid commlink sound

Super Mario death sound (i have this for when people who annoy me call)
[Nexus 6  Original Android Development] knitler:
Good selection
[Nexus 6  Original Android Development] Imoseyon:
Something else about lightflow. It doesn't seem all that stable. It will crash on you eventually. I sent a crash report to the author, and then uninstalled it. :)
[Nexus 6  Original Android Development] Smallsmx3:
That's how I always felt about it. You'd be surprised how many people complained over the years how light flow didn't work right. Even though almost every custom ROM had built in LED controls for previous nexus phones
[Nexus 6  Original Android Development] nobnut:
Lightflow is a lot like an iPhone. On paper it's good, you *think* you want the functionality, you think it will enhance your productivity, you get ownership of it... and you realise it's a load of old {expletive}.

Great concept, catastrophically executed.
[Nexus 6  Original Android Development] eggydrums:
I'm surprised at so many people having problems with it. I've always heard good things about it, especially in sites like Reddit
[Nexus 6  Original Android Development] nextelbuddy:
Sorry i forgot that many times people opt to put additional information in the following post after the initial thread post.

So it appears that the Freq MIN and MIX will almost always change in the kernel manager due to a refresh issue in that panel and stock MP decision enabled by default and that as long as I am ok with that just being a visual issue in the kernel manager and being stuck with the default MIN and MAX i should be fine. the only time it should matter is if I want to actually set a specific MIN above the minimum and a MAX below the default maximum then I will have to flash the additional files that will allow me to disable MP Decision in the kernel manger thus allowing me to lock the MIN and MAX frequency to a different frequency.

i think i am fine with that.

Its just that last night when I had 10% battery despite that I did NOT have battery saver mode enabled, my CPU frequency never exceeded 1700ghz no matter what kernel i tried. i flashed franco and lean kernel and CPU spy always showed max of 1.7 GHZ and my device was extremely choppy as if battery saver mode was enabled.

once I charged my device to full charge that issue went away.

so weird.
[Nexus 6  Original Android Development] SeanPlunk:
Lightflow has stopped working for me too.

Up to this point it had been dead stable with no crashes. I've been on LeanKernel since 1.2 I believe. Strange.
[Nexus 6  Original Android Development] old_fart:
There is probably a dozen or more senior developers wasting their time on the bugginess of the LED light app. . Our leader [MENTION=3357040]Imoseyon[/MENTION] stated the thing has "ISSUES" ( buggy ) so we wait for the app developer to fix his stuff . . . more . . .

.

On a more ( pointedly on topic ) good note, wow ! the latest update to the governor sure made a noticeable improvement to the battery life. Now I have the luxury of doing stupid ( and wasteful things ) and worrying less !
[Nexus 6  Original Android Development] rignfool:
Iirc that is a feature of the thermal driver...

It under clocks starting at 20% to 1728MHz...

And at 5% it cuts down again... I forget where...

All in an attempt to keep your phone alive...

It does reset when it gets above 20% though

Sent from my Nexus 6
[Nexus 6  Original Android Development] andrewpmoore:
I was pointed here my someone regarding the issues and being buggy. I'd be interested what the thoughts are on it being buggy. The led control on the nexus 6 is pretty straightforward just echoing out to the brightness files to control the led. It'll run as su or a standard user (but requires permissive mode to do so with the led drivers being in the /sys directory).

I'd love to try and resolve the issues people are having but it's a rather large thread to look through. If someone could pm on any issues they have picked up on I'll certainly look into it without clogging up this thread.
[Nexus 6  Original Android Development] r80ies:
I too have similar results as yours. However, it could be signal issues with my scenario.
[Nexus 6  Original Android Development] old_fart:
Thank you. We know your job of getting it to work on so "many" different h/w platforms is tough . . . extremely tough. . Please direct me to the 'nexus 6' developer notes.

Um, you state 'requires permissive mode' . . I've never done that. I've never read a note telling me to do that. . For me the app works and then it does not work Five pages back I posted a short logcat of it 'not' working and then another of it working . . Hmm, so do I use << https://play.google.com/store/apps/d...mrbimc.selinux >> and make the N6 permissive, as a critical pre-step ?
[Nexus 6  Original Android Development] PhilDX:
I haven't had a single issue with Light Flow (paid) on two different nexus 6 devices over the past two months. this is on stock Lollipop with both stock kernel and Lean kernel (tested versions 1.5 through 1.8). it's been rock solid and I love it.

personally, I think the issue is one of these:

- some folks don't follow the installation tutorial provided in the app

- some folks don't uninstall/reinstall after kernel updates

- custom ROM complications and/or dirty ROM flashes
[Nexus 6  Original Android Development] fitz420:
This quote has me smiling like crazy. Thanks for the laugh.

That's all.
[Nexus 6  Original Android Development] merouleau:
Hard to argue with this as that's what we all needed to do with the transition from LK v1.8 to 1.9. It's a good thing none of the other 150 apps on my phone quietly stop functioning correctly every time I change kernels.

It does beg a couple of questions:

1. What makes Light Flow so special?

2. Since many of our Light Flow installations handled the LK v1.6 -> 1.7 -> 1.8 transitions without trouble, what change in 1.9 required the reinstallation?
[Nexus 6  Original Android Development] Imoseyon:
hey thanks for visiting this thread. You shouldn't need to require permissive mode (just root) to be able to write to /sys. Also, the app crashed on me multiple times while testing with my kernel. I sent you a crash report (came from my email address) - please take a look :)

The folks that are likely to notice the new cpu scheduler power efficiency are typically the ones that use the phone a lot on medium to low workload (ie. listen to music, read book, browse, etc.). Even then the effect may be subtle depending on your use case. Keep in mind that just about any kernel change is going to be subtle - rarely is it going to blow you away. :D

My recommendation would to be keep the powersaving mode on if you're satisfied with the performance.

That is a very valid question. The only thing I can think of is that there are a bunch of Selinux related fixes in v1.9. Is it possible that that could have a negative effect on some apps? Possibly.
[Nexus 6  Original Android Development] grinchyyy:
I fit this description and can report no loss in performance and a noticeable increase in battery life. Thanks!
[Nexus 6  Original Android Development] Cy_n_ic:
I have to say im quite satisfied with 1.9 update. I have had lk power save (not to be confused with lollipops power save) enabled the whole time and iv not had any noticeable change in performance and battery life feels good. One thing i did kinda notice is the native battery graph looks alot less jaged. Instead of dropping in what looks like stair steps is now more like a smooth wave as it goes down. Like the drain is more consistent or like if it has more data points to build the graph off of so its a cleaner line. Maybe its just me idk but im quite pleased