Database Info

my few nitpicks

I love this phone without a doubt coming from the OG Droid, although using my friend's incredible pretty often.
#1 the led notification is tiny. unless youre looking at it head on you wont know if you have one.
#2 the vibration is very weak, i hope there is a way to improve this
#3 the brightness. on my old phone on the power widgets toggle, you would tap it and it would go from minimum, medium, max, off, etc. On this one you either set it on auto or have to adjust the slider constantly. I have to think you can get more battery hours out of this if it was like the old display.
#4 i dont like that there isn't a camera button. I don't care who you are, this is more like iphone using the touch screen to take a pic and youre more likely to move the screen while hitting it.
Other than that, i love this phone. it's nitro fast even compared to the 1ghtz overclocked droid, I can't wait to root and overclock and put on CM7

Why don't you use your fancy new Thunderbolt to call someone that cares.

@RichyRich said:
Why don't you use your fancy new Thunderbolt to call someone that cares.
Click to expand...
Click to collapse
Jealousy is a stinky cologne

rotorocker said:
I love this phone without a doubt coming from the OG Droid, although using my friend's incredible pretty often.
#1 the led notification is tiny. unless youre looking at it head on you wont know if you have one.
#2 the vibration is very weak, i hope there is a way to improve this
#3 the brightness. on my old phone on the power widgets toggle, you would tap it and it would go from minimum, medium, max, off, etc. On this one you either set it on auto or have to adjust the slider constantly. I have to think you can get more battery hours out of this if it was like the old display.
#4 i dont like that there isn't a camera button. I don't care who you are, this is more like iphone using the touch screen to take a pic and youre more likely to move the screen while hitting it.
Other than that, i love this phone. it's nitro fast even compared to the 1ghtz overclocked droid, I can't wait to root and overclock and put on CM7
Click to expand...
Click to collapse
i've noticed 1 and 2, i dont feel the vibration in my pocket and i thought it was my case. after taking it off it make no difference. my og droid had an awesome led and i customized it like crazy.

I agree that the LED notification can be pretty hard to see sometimes. But the brightness toggle widget does indeed change the brightness to min, med, max.

HonestEnd said:
I agree that the LED notification can be pretty hard to see sometimes. But the brightness toggle widget does indeed change the brightness to min, med, max.
Click to expand...
Click to collapse
only if you use the slider, you cant click on the brightness icon and have it rotate through brightness

rotorocker said:
only if you use the slider, you cant click on the brightness icon and have it rotate through brightness
Click to expand...
Click to collapse
Mine works that way... with each click you can see the screen and the widget change modes.
You don't see this when clicking on your widget?

R1lover said:
Mine works that way... with each click you can see the screen and the widget change modes.
You don't see this when clicking on your widget?
Click to expand...
Click to collapse
If you take the brightness out of "Auto" the brightness widget allows you to select threed different modes.

right, if its not in auto mode, it brings up the slider. I can't just tap 2-3 times on the icon to change different levels.

rotorocker said:
right, if its not in auto mode, it brings up the slider. I can't just tap 2-3 times on the icon to change different levels.
Click to expand...
Click to collapse
I just doubled checked mine to be 100% sure.... No matter the setting (auto or not) I can tap the widget and it will change through the modes like normal.
If your's is not doing this then something is up I would say.

That is VERY wierd because I works on mine. All if have to do is tap the widget and it gets changes modes. Are you using the Official HTC brightness widget? Also are you using the "solo" brightness widget? (The one with just the brightness, not the power bar widget)

okay, what exactly is the name of the widget youre doing this with so were on the same page?

I just tap mine....No problems it adjust up and down....I used the screen on my incredible to take pics so this is the same to me.....

rotorocker said:
okay, what exactly is the name of the widget youre doing this with so were on the same page?
Click to expand...
Click to collapse
It's called "Screen Brightness" located under the "Settings" category under Widgets. I'm guessing you're using the Power Dashboard widget which displays all of different settings on one bar.

you are correct, mine is listed as power widget. I don't see the one you're referring to

HonestEnd said:
It's called "Screen Brightness" located under the "Settings" category under Widgets. I'm guessing you're using the Power Dashboard widget which displays all of different settings on one bar.
Click to expand...
Click to collapse
Just to test, I installed both and they both work the same for me... each press changed the brightness as it should.

You're running Sense right? No ADW or LauncherPro correct? I'm starting to think he's running a launcher and using the default widgets that come with Android.

oh sorry, I am running launcher pro. I apologize, i didnt know that made a difference

rotorocker said:
oh sorry, I am running launcher pro. I apologize, i didnt know that made a difference
Click to expand...
Click to collapse
Yea, you can't access the HTC Widgets when you're running another launcher such as ADW or LauncherPro.
Edit: Dammit, I made my 10 posts, where's my "Edit Signature" option in UserCP XDA?!

rotorocker said:
Jealousy is a stinky cologne
Click to expand...
Click to collapse
I have a Thunderbolt, Atrix, iPhone 4, and BlackBerry 9700 sitting next to me; what exactly is it that I'm supposed to be jealous of?

[APP][2.1+] TeslaLED 3.0 beta

TeslaLED is an LED flashlight app for many phones. TeslaLED has been out for over a year, but TeslaLED 3.0 beta is a fresh rewrite (giving me an test bed to try some new development ideas and tools).
Features of TeslaLED:
LED Flashlight
Strobe/Morse Code
Keep LED on with screen off (May flicker once)
Different widget styles
Free and No ads
TeslaLED is known to work on the following devices. It may work on other devices as well, but may require changing the "LED Method" in preferences.
Nexus One, Nexus S
Motorola Droid, Droid X, Droid 2, Atrix
HTC EVO, Droid Incredible, Thunderbolt, Desire, Desire HD, MyTouch 3G Slide, T-Mobile G2, Legend
Galaxy S II i9100
Galaxy S Epic and Fascinate (Strobe/Morse code do not work)
Galaxy Tab 7" and 10.1"
Xoom
Acer A500
I'm looking for bug reports (especially features of phones that broke since the Market version 2.0.4)
Download Link:
https://market.android.com/details?id=com.teslacoilsw.flashlight
http://teslacoilsw.com/android/teslaled/TeslaLED_3.0.1.apk
Note: My google-alerts show this APK spreading to pirate sites. The app is free so this isn't a big deal, but if doing so can you link back here?

Great app.
Thanks.
Sent from my MB860 using XDA Premium App

FC on Thunderbolt GB on first start up after install, but it was good and well after

Works as expected on my Acer A500 tab, haven't updated on my Nexus One yet.

0mie said:
FC on Thunderbolt GB on first start up after install, but it was good and well after
Click to expand...
Click to collapse
Can you Settings > Bug Report? This will let you email me with the stack trace. I have an idea of what it is, but good to verify.

Works great on HTC EVO.

I have the old donate version. Do you recommend uninstalling that before installing this?

jasonsf said:
I have the old donate version. Do you recommend uninstalling that before installing this?
Click to expand...
Click to collapse
It won't hurt to have both installed (This is actually how I tested and compared, using TeslaLED Donate 2.0.4 and TeslaLED (non-donate) 3.0beta ), however having both installed means when going to add the widget you'll see both listed as TeslaLED with the same icon so it's a bit confusing. On my devices the 2nd option was the 3.0 beta but I'm not sure how android sorts that list so it might vary.

Have you thought about pulsing the signal to the LED so quickly that it emulates a true PWM feature or using the built in PWM on the LED in most phones to create pulsing or breathing LED with variable speeds or patterns.
I would love to help you with it and we could add the one good Apple thing to our phones that they don't even have on the iPhone.
Sound Cool?

0mie said:
FC on Thunderbolt GB on first start up after install, but it was good and well after
Click to expand...
Click to collapse
Same here. But I did the bug reporting
Worked on xoom 3.1 and no fc. Police lights are blinding haha

[email protected] said:
Can you Settings > Bug Report? This will let you email me with the stack trace. I have an idea of what it is, but good to verify.
Click to expand...
Click to collapse
Sent
10char

Okay I've updated the OP with a link for beta3. This fixes the first-run bug some of you were experiencing. (No real need to update if you already have beta2 as it won't happen again)

works with galaxy s2 , thanks

Childofthehorn said:
Have you thought about pulsing the signal to the LED so quickly that it emulates a true PWM feature or using the built in PWM on the LED in most phones to create pulsing or breathing LED with variable speeds or patterns.
I would love to help you with it and we could add the one good Apple thing to our phones that they don't even have on the iPhone.
Sound Cool?
Click to expand...
Click to collapse
Unfortunately the LED APIs are more like desktop APIs rather than microcontroller APIs (or bits to twiddle I guess).
HTC's is best which gives variable brightness (most likely implemented by an internal PWM) and responds quickly and is easy to use (write to a file in /sys/devices).
Standard/Standard+ are using the camera APIs which are a bit slow and have the choice of either on or off
TeslaLED's strobe at 20Hz stutters once in a while when using the camera API and PWM would need much higher than 20Hz.
With root or a custom kernel I'm sure you could have a bit more control over the flash, but it'd likely be rather device specific and still might not even lead to true PWM control as the camera might have it's own private controller that is slow to accept commands.

Runs great on Stock Samsung Galaxy SII
1000 Thanks man!
Greetz Tokl

Beta 3 runs great on the Incredible (Sense)! Love the new Sense styled widget. Thanks!!!

Got problems on my Galaxy S2, I started the LED, either using widget locker or using the widget on my home screen, then after the screen goes off, the led goes off then on again (which I believe is normal). If I wait a further 15 seconds approximately then the LED goes off again and this time stays off.
At this point both the widget won't work to turn it back on or off, nor the built in widget for widget locker. I can however close it using the notification bar. When I try to close it using the above methods I get a force close error:
"The application TeslaLED (process com.teslacoilsw.flashlight) has stopped unexpectedly. Please try again."
This is the case for both beta 3 and the released version of the software. I've sent a bug report.

icehot666 said:
Got problems on my Galaxy S2, I started the LED, either using widget locker or using the widget on my home screen, then after the screen goes off, the led goes off then on again (which I believe is normal). If I wait a further 15 seconds approximately then the LED goes off again and this time stays off.
Click to expand...
Click to collapse
I have a Galaxy S2 now and I was wondering why I couldn't reproduce the problems people said they had, even when I was using the old version. It seems the wait 15 seconds, with the device not plugged into a computer, is key. It also makes it much more difficult to get debug logs.
Unfortunately I couldn't find any tricks to get the LED to stay on with the screen off, so I'm going to need to disable that ability on the GS2. Keeping the screen on works and TeslaLED has a (disabled by default) "Dim Screen" page you can use to have a fake-screen-off. Not perfect though (and only accessible from the app).

[email protected] said:
I have a Galaxy S2 now and I was wondering why I couldn't reproduce the problems people said they had, even when I was using the old version. It seems the wait 15 seconds, with the device not plugged into a computer, is key. It also makes it much more difficult to get debug logs.
Unfortunately I couldn't find any tricks to get the LED to stay on with the screen off, so I'm going to need to disable that ability on the GS2. Keeping the screen on works and TeslaLED has a (disabled by default) "Dim Screen" page you can use to have a fake-screen-off. Not perfect though (and only accessible from the app).
Click to expand...
Click to collapse
I think it happens when phone enters in deep sleep state where the CPU is turned off to save battery (so when plugged it's not needed). You should try using wakelock threads to keep it active
Sent from my GT-I9100
If you find this post usefull please press the "Thanks" button

nightranger73 said:
I think it happens when phone enters in deep sleep state where the CPU is turned off to save battery (so when plugged it's not needed). You should try using wakelock threads to keep it active
Click to expand...
Click to collapse
Already tried that, no go

Touch key brightness

Hey all, I'm trying to figure out how to get some brightness settings for the touch key brightness to stick. I've used LG 2x Notifications and O2x Touch Key Brightness, and they both work up until the point where i put the phone to sleep by tapping the power button. As soon as I wake it up, the brightness goes straight to zero unless i head back to the app and raise it up again. And if i uninstall the apps, the brightness on my keys stay off until i re-flash or reinstall the app again. Help!

My issue is a little different but similar. It worked fine for me on every basic gingerbread rom, but when I switched to a cm7 based rom the lights change with the brightness of the screen. I turned off all the light notifications but it did not help.
If anyone has any ideas, I'd love to hear them.

What rom?
Sent from my LG-P999 using XDA

redmonke255 said:
What rom?
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
On SinghUI but it doesn't have built-in LED notifications, if that's what you're getting at.

If the setting from one of those apps doesn't stick, then it's most likely being set by your ROM or Kernel. Have you tried checking if you get the same issue with other ROMs?
@jcbofkc That's a built-in setting that can't really be changed unless you get a custom ROM or Kernel cooked up to remove the link between the brightnesses.

xBIGREDDx said:
If the setting from one of those apps doesn't stick, then it's most likely being set by your ROM or Kernel. Have you tried checking if you get the same issue with other ROMs?
@jcbofkc That's a built-in setting that can't really be changed unless you get a custom ROM or Kernel cooked up to remove the link between the brightnesses.
Click to expand...
Click to collapse
90% sure the ROM doesn't have built in notifications. I'm noticing now that very rarely the settings do stick. Perhaps there is a way to force the app to stay in memory?

rrroach said:
90% sure the ROM doesn't have built in notifications. I'm noticing now that very rarely the settings do stick. Perhaps there is a way to force the app to stay in memory?
Click to expand...
Click to collapse
That wouldn't work. All that those apps do is write a number from 0-20 to the text file:
/sys/devices/platform/star_touch_led/wled
in your root file system.
When you read the file, it shows you the current output to the LEDs (from 0uA to 2000uA).
When you write to the file, it interacts with the Kernel and sets the brightness.
The Touch Key Lights type apps, all they do is when you move the slider they write a value to that file, and that's it. The only reason it wouldn't stick is if your ROM or Kernel is changing the value in the background. For example it will set it to 0 when you turn the screen off, and then it should set it back to wherever it was before when you turn the screen on again.
The closest you could get is to take the source for LG Touch LED Notifications and modify it to set the brightness every few seconds or something, but that probably wouldn't be too good for your battery life.
Based on your symptoms it appears that either your ROM or your phone doesn't really handle the modifying of the brightness very well. It looks like SinghUI does use a kernel from CM7, so I don't think your kernel is the problem. I'd suggest flashing the most recent CM7.2 RC, and seeing if you have the same problem there. CyanogenMod will change your LED brightness based on your screen brightness though.
EDIT: Ignore all that for a moment, try this first. It is a post from January 21st in the SinghUI thread, so it might not work now, but go ahead and try it: http://forum.xda-developers.com/showpost.php?p=21652744&postcount=293
Also I'd suggest posting in the SinghUI thread as everyone there is using your ROM, so they might be able to help better.

xBIGREDDx said:
That wouldn't work. All that those apps do is write a number from 0-20 to the text file:
/sys/devices/platform/star_touch_led/wled
in your root file system.
When you read the file, it shows you the current output to the LEDs (from 0uA to 2000uA).
When you write to the file, it interacts with the Kernel and sets the brightness.
The Touch Key Lights type apps, all they do is when you move the slider they write a value to that file, and that's it. The only reason it wouldn't stick is if your ROM or Kernel is changing the value in the background. For example it will set it to 0 when you turn the screen off, and then it should set it back to wherever it was before when you turn the screen on again.
The closest you could get is to take the source for LG Touch LED Notifications and modify it to set the brightness every few seconds or something, but that probably wouldn't be too good for your battery life.
Based on your symptoms it appears that either your ROM or your phone doesn't really handle the modifying of the brightness very well. It looks like SinghUI does use a kernel from CM7, so I don't think your kernel is the problem. I'd suggest flashing the most recent CM7.2 RC, and seeing if you have the same problem there. CyanogenMod will change your LED brightness based on your screen brightness though.
EDIT: Ignore all that for a moment, try this first. It is a post from January 21st in the SinghUI thread, so it might not work now, but go ahead and try it: http://forum.xda-developers.com/showpost.php?p=21652744&postcount=293
Also I'd suggest posting in the SinghUI thread as everyone there is using your ROM, so they might be able to help better.
Click to expand...
Click to collapse
Thanks for the link. It turns out that the ROM does have led notifications. However, disabling them didn't help the problem. :/ the g2x has just been an awful experience for me! :/

[Q] Wonky Brightness - Help?

Sorry the title couldn't describe much, but this situation with my VZWGS3 is a special one. I have not been able to find a situation similar to mine by searching this forum or the internet.
My problem, is that when i wake my device with the power button, it automatically ducks my brightness down to minimum. In my brightness settings, I disabled auto brightness and I have the slider at 100%. I have to tickle the brightness slider to get it to come back up to 100% brightness. My first thought is that the lock screen is forcing the screen to dim. It isn't even a smooth transition. When I do enable auto brightness, it still dims the screen on wake, but it only changes when the ambient lighting changes (thus causing auto brightness to kick in) and then it looks normal. The result of this problem is that I cant see my screen when i turn it on outside or in bright rooms. This does not have anything to do with battery, because this happens even when it is plugged in and at 100%
I'm on a deodexed stock pre-rooted touchwiz rom. Baseband version: I535VRBMF1. Android Version: 4.1.2. Kernel: 3.0.31-1152558 [email protected] #1
Android build number: JZO54K.I535VRBMF1
Later on today, I can make a video of this happening to better describe the issue. For now, just let this ponder in your heads.

Also, is it possible to debug which apps cause something to happen to the system? For instance, scan to see which apps & processes are controlling brightness.

jtcressy said:
Also, is it possible to debug which apps cause something to happen to the system? For instance, scan to see which apps & processes are controlling brightness.
Click to expand...
Click to collapse
Oops accidentally thanked you haha. But back on topic, I dont know of a way to debug that type of problem. what i would suggest since you're rooted is to make a backup in Titanium and a Nandroid. Then try doing a factory reset. That is a very strange problem indeed..
Sent from my Galaxy S3

TheKucho said:
Oops accidentally thanked you haha. But back on topic, I dont know of a way to debug that type of problem. what i would suggest since you're rooted is to make a backup in Titanium and a Nandroid. Then try doing a factory reset. That is a very strange problem indeed..
Sent from my Galaxy S3
Click to expand...
Click to collapse
Thanks for your reply. I'll probably try a factory reset. Can't hurt. There's a question I have about TiBu when it restores apps, so i'll ask that in another forum before I begin the process. In the meantime, this thread is still open to ideas.

Ok. This is a bit of a *facepalm* moment. Let it be noted that the main reason my GS3 was having this problem was the app called "Light Flow". I came upon this conclusion by giving the safemode of android a try. The problem immediately disappeared, so I realized it was an app. I thought a bit about what app could be controlling the lights of the phone, and the lightbulb went off. Uninstalled Light Flow and the problem stopped. I guess I kinda miss the custom notification light, which is why I downloaded Light Flow in the first place because I miss some of the notification light customization features on other Cyanogen based roms. Later on I heard from a buddy that Light Flow really screws up some things on the GS3.

jtcressy said:
Ok. This is a bit of a *facepalm* moment. Let it be noted that the main reason my GS3 was having this problem was the app called "Light Flow". I came upon this conclusion by giving the safemode of android a try. The problem immediately disappeared, so I realized it was an app. I thought a bit about what app could be controlling the lights of the phone, and the lightbulb went off. Uninstalled Light Flow and the problem stopped. I guess I kinda miss the custom notification light, which is why I downloaded Light Flow in the first place because I miss some of the notification light customization features on other Cyanogen based roms. Later on I heard from a buddy that Light Flow really screws up some things on the GS3.
Click to expand...
Click to collapse
Yeah, I tried light flow a while back and wound up uninstalling it for weird behavior.
Sent from my SCH-I535 using xda app-developers app

Light Flow

Has anyone been able to get Light Flow to work on the OnePlus One? I like light flow a lot better than the CM notification center, but I just can't seem to get it to work.
Has anyone here getten it to work? If so, mind sharing your settings?

So far I've had one person say it worked and two not!
Can you try and see if led color tester by coolbeans works on the phone (with lightflow either not installed or disabled) and let me know if that works?

I'm interested in this as well. I enjoy Lightflow so much more than any of the other notification apps I've tried. I'll be heartbroken if it doesn't work...

i used lightflow with paranoid android and it works fine on my oneplus one chinese version

andrewpmoore said:
So far I've had one person say it worked and two not!
Can you try and see if led color tester by coolbeans works on the phone (with lightflow either not installed or disabled) and let me know if that works?
Click to expand...
Click to collapse
Hello. I'm a big fan of your work (been using on the N4 and N5).
I also have this app on my OnePlus One. I noticed that up until the most recent build that all my notifications were working. Gmail and stuff were all fine.
Is it me or did the latest build change something? When notifications come in I get a white light blinking. When I power my screen on and off again it seems like Light Flow then registers, and now I get green pulses.
I'm not sure if its the most recent build of Light Flow or if its because I added a second Gmail account). I am rooted so I'm on root mode, but maybe some of my settings are whacked?

dmo580 said:
Is it me or did the latest build change something? When notifications come in I get a white light blinking. When I power my screen on and off again it seems like Light Flow then registers, and now I get green pulses.
Click to expand...
Click to collapse
Yep, have the same "issue". Before the last Update everything was fine..

No Light Flow issues here.
Just got my OnePlus One today. Installed, restored the app generated backup from my S4, good to go.
Some apps need to have their own LED setting disabled for LF to work properly since the last version.

dmo580 said:
Hello. I'm a big fan of your work (been using on the N4 and N5).
I also have this app on my OnePlus One. I noticed that up until the most recent build that all my notifications were working. Gmail and stuff were all fine.
Is it me or did the latest build change something? When notifications come in I get a white light blinking. When I power my screen on and off again it seems like Light Flow then registers, and now I get green pulses.
I'm not sure if its the most recent build of Light Flow or if its because I added a second Gmail account). I am rooted so I'm on root mode, but maybe some of my settings are whacked?
Click to expand...
Click to collapse
I'm aware of this for some users and I've just pushed out an update (it should show in the play store over the next few hours) I've had a few people testing who had that issue and reports so far seem to be that it fixes that issue.

andrewpmoore said:
I'm aware of this for some users and I've just pushed out an update (it should show in the play store over the next few hours) I've had a few people testing who had that issue and reports so far seem to be that it fixes that issue.
Click to expand...
Click to collapse
Just got my OPO today and Light Flow is working great. Just restored my backup from my Nexus 4 and no probs. Love the new UI too!

andrewpmoore said:
I'm aware of this for some users and I've just pushed out an update (it should show in the play store over the next few hours) I've had a few people testing who had that issue and reports so far seem to be that it fixes that issue.
Click to expand...
Click to collapse
You sir are a hero. It no longer requires me to use Gravity Box UNC to override settings.
Question: Do you recommend for high end phones like the N5 and OPO to run in foreground or background? I see no issues with background on my OPO and the app doesn't get killed at all.
Second question: You're still going to roll out global settings someday right? Having to change speeds for every app is a bit annoying, or even custom blink settings.
Final question: Is it possible to adjust the brightness for the LED? I see a brightness option in the sleep options for night blinking, but adjustments for individual notifications? Would be nice to have global for this too

dmo580 said:
Question: Do you recommend for high end phones like the N5 and OPO to run in foreground or background? I see no issues with background on my OPO and the app doesn't get killed at all.
Click to expand...
Click to collapse
On the N5 I find it does work better with the option on, without it once every few days maybe it'll get killed off by android (which is fairly normal for any background service) so it'll miss a notification.
dmo580 said:
Second question: You're still going to roll out global settings someday right? Having to change speeds for every app is a bit annoying, or even custom blink settings.
Click to expand...
Click to collapse
Yes that's still on the list. If google hadn't brought out android L I'd have been working on that, but I've had to divert my time to issues with that!
dmo580 said:
Final question: Is it possible to adjust the brightness for the LED? I see a brightness option in the sleep options for night blinking, but adjustments for individual notifications? Would be nice to have global for this too
Click to expand...
Click to collapse
There's a global option for this (in lightflow, settings, general settings, led brightness), but not individual, you'd just have to use the custom color option at the moment.

Lightflow works for me.

I can't get LF working, or if it does work it just flashes white. I'm 100% stock/unrooted so is there anything else I need to activate to get it working? I had no issues with my previous Nexus 4/5 so it must be something silly!
EDIT: Reinstalled and seems to be working OK now, so obviously something I did wrong!

Thanks for the help @andrewpmoore
Is it possible to have the lights on even when the screen on? Is that the "Samsung direct mode?" I don't believe that worked on my other non Samsung devices, so I doubt it will work on the OPO.
I ask because CM's battery LED seems to by default remain on even when the screen is on or off.

rubytuesday007 said:
Lightflow works for me.
Click to expand...
Click to collapse
Same here. Rooted. Locked bootloader. Dunno if it matters...
Correction! There seems to be a small glitch: At the end of Charging when switching to Charged it seems to start switching between Charging and Charged rather than just using the Charged notification.

I've a fix coming for switching between charged and charging.

What 'Device Settings' is everyone running to make this work? Is anyone using:
Direct Mode?
Samsung root mode?
Reset color before change?
Nexus 5 force LED reset?
For some reason mine works for a period of time than I start getting SMS's and it stops working. I restart the app, but it doesn't continue to work again. Not sure what's going on.

kroogar said:
Correction! There seems to be a small glitch: At the end of Charging when switching to Charged it seems to start switching between Charging and Charged rather than just using the Charged notification.
Click to expand...
Click to collapse
The glitch seems to have exploded... nothing seems to be working now... not mail, not sms ... nothing. Tried to enable the root option but it makes no difference

DJMartini said:
What 'Device Settings' is everyone running to make this work? Is anyone using:
Direct Mode?
Samsung root mode?
Reset color before change?
Nexus 5 force LED reset?
For some reason mine works for a period of time than I start getting SMS's and it stops working. I restart the app, but it doesn't continue to work again. Not sure what's going on.
Click to expand...
Click to collapse
The Nexus 5 thing is the only box I have checked (must've been by default since I didn't do it).
kroogar said:
The glitch seems to have exploded... nothing seems to be working now... not mail, not sms ... nothing. Tried to enable the root option but it makes no difference
Click to expand...
Click to collapse
Not having any issues... maybe backup your notification settings and then wipe and restore them. Ensure LF has the proper notifications access, etc.

dmarden said:
Not having any issues... maybe backup your notification settings and then wipe and restore them. Ensure LF has the proper notifications access, etc.
Click to expand...
Click to collapse
Nope. Nothing. Tried to clear the cache and data. Tested the notifications and nothing... Checked Notification access and tried enabling root mode. Still nothing... Phone is stock though rooted.