Related
I've put this in the Development section because whilst it is almost fully functional, it still needs a lot of development. Please be aware of this when you download it. I am not to be held responsible for anything that may happen as a result of running this app.
Requirements:
Root Access & a Custom ROM (StreakDroid 1.8.0 recommended (CONFIRMED WORKING ON 1.8.0))
Built under a 2.2 framework. If you are running anything pre-2.2 please be aware it may not work.
Please remember to remove all previous versions of the app before installing.
Simply open the app and press the "Menu" button. I hope you can figure the rest out! Enjoy!
"LED Notification FREE" has been uploaded in the Market. It has full functionality and it Ad Supported.
Please be aware that this version includes an "AdBlocker Check". This will block the app from opening if you have an adblocker installed on your phone. Sorry about this but i hate adblockers Alternatively, you can just remove all instances of Admob from your Hosts file.
Code:
[I][B][COLOR="blue"]QUICK HANDCENT FIX[/COLOR][/B]:
Open Handcent, press 'Menu > Settings > Notification settings > Popup settings'.
[B]MAKE SURE[/B] 'Screen on for popup' is [B]UNCHECKED[/B].
Handcent wont interfere with my app from then on :D[/I]
NEW TO 2.0.1
Asks for SU Access when the app first loads Fixes some weird error that happens every now and again.
Completely re-coded the SMS receiver. Much smoother now!
SMS and Gmail Notifications can be turned on or off
New settings page - done properly now, wont save anything to sdcard [you can delete your STREAKLED folder now!] Press the 'menu' button when you open the app for settings.
Permissions tweaked (should be less LED problems)
KNOWN BUGS
Changing orientation during the pattern causes problems. Just don't do it!
Notifications overwrite each other. So if an SMS message arrives and then a Gmail, only the Menu button will be lit, and vice versa.
Services cannot be stopped (only by uninstalling) FIXED - 2.0
Sometimes all the buttons will end up being lit, not sure why. [SHOULD BE FIXED]
TODO
Add options for turning the SMS and Gmail notifications on and off DONE - 2.0
Have different patterns for each DONE - 1.3
Improve the UI (sort of) DONE - 2.0
Improve the pattern flashing sequence (sort of) DONE - 2.0
Clean up the code (WIP )DONE - 2.0
Fix orientation issue
This will ALWAYS be available for free on here, on Modaco and on my website (see sig) but i have uploaded a 'donate' version on the Android Market Place priced at £1.50, just incase you fancy buying me a beer
Enjoy
Meltus said:
I've put this in the Development section because it is not fully functional and still needs a lot of development. This is basically a proof of concept app.
Requirements: Root Access (tested on 2.1 but build under a 1.6 framework so it should work on 1.6)
All you have to do is run the application, hit the home button and receive a text (or send yourself one). If your phone is locked it will wake up and dim the screen and flash the home/menu/back LEDs in a nice pattern and then keep the screen dimmed until you unlock the phone manually.
The only problem is that you will receive a Force Close error message and you will then have the re-open the app for it to work again. I am trying to fix this but will not be able to look into it for a few days so i thought i would release what i've done so far.
I will be adding settings and more patterns as soon as i can fix this FC error.
Enjoy
Click to expand...
Click to collapse
Well... GREAT!!! Thanks! It works... Was searching this kind of app for weeks. Thanks again!
Great little app. Can't wait for thenext update
Nice work.
Just out of interest though, what's the dangers of having the screen on dim all night if I get a text message at stupid o'clock?
Wouldn't want to burn anything on my screen if that is possible.
Amdathlonuk said:
Nice work.
Just out of interest though, what's the dangers of having the screen on dim all night if I get a text message at stupid o'clock?
Wouldn't want to burn anything on my screen if that is possible.
Click to expand...
Click to collapse
Screen burn is an issue on LCD screens, hence why i set it to do a dim wake lock instead of a full brightness one. Saying that, i have absolutely no idea whether screen burn would still occur but ill test it tonight and report back
On a positive note i have fixed the FC error and will release the fully working version tomorrow!!
Nice work dude ! Look forward to a full release tomorrow.
Any way to make this compatible with non rooted steaks on 1.6?
Sent from my Dell Streak using XDA App
jdmnash said:
Any way to make this compatible with non rooted steaks on 1.6?
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
No, i'm afraid not.
Without Root Access it will probably just force close.
Currently in the process of adding more LED patterns
It also now wakes the phone, unlocks the phone and displays an "SMS Message Received" popup which it then hangs at until you close it.
Do you guys think this is better or should I make it lock the screen instead?
What else should i add/change?
Meltus said:
Do you guys think this is better or should I make it lock the screen instead?
What else should i add/change?
Click to expand...
Click to collapse
I'd prefer it stayed locked, also if I read this thread correctly, it leaves the screen on (but dimmed?) is that true? I would need it to kill the screen, because as noted, it could kill your battery if you went a long time w/o clearing the alert.
Nice work so far though...
a042349 said:
I'd prefer it stayed locked, also if I read this thread correctly, it leaves the screen on (but dimmed?) is that true? I would need it to kill the screen, because as noted, it could kill your battery if you went a long time w/o clearing the alert.
Nice work so far though...
Click to expand...
Click to collapse
Yeah, that's the only problem.
unfortunately, killing the screen freezes the LEDs in whatever state they're in, completely defying the point of the app
What i could do though, is wake up the screen, flash the LEDs but leave one on and turn the screen back off. This would turn everything off apart from that 1 LED and you could use different LEDs for different notifications. I'll try that out later.
Yeah, that seems like a good idea. Maybe the Back LED for missed SMS, the Menu LED for missed call. Something like that.
That would be cool, I'll await your work and give it a try.
Well, it turns out that works miles better than what i was trying before.
Basically, it now turns the screen on, keeps it locked, flashes the LEDs, turns the screen back off and leaves the home LED on.
Give me about 10 mins and i'll put up a working version. No FC error this time
Can't wait for this!
Sent from my Dell Streak using XDA App
First post updated with a working version
None of the options work on the main screen yet, but they will.
Enjoy
I haven't tried this yet, but I just want to say THANKS! No notification light was driving me crazy! I'm gonna install it now. I like that it would kill the screen but leave the LED light on. That's perfect!
**EDIT**
Well, it didn't work perfectly. Here's what happened on my Beta Streak....
With locking disabled (I use the 'NO LOCK' widget), it turned the screen on and said 'SMS received' and the home LED was on, for about 1-2 minutes, then both went off. When I turned back on the screen and read the msg, the LED went out.
With locking enabled, like most people would be using the app, the screen turned on for a few seconds while the LED pulsed, then both went out. No notification. When I unlock and read the msg, the home LED stays on. I have to 'clear' the app in the notification tray and lock then unlock the screen to make the home LED go out.
Seems like they're little tweaks that could be needed. If you can make this work and be functional, I'll donate to your Paypal! Again, thanks for your work on this project!!
Yeah, it's still pretty much in it's 'Alpha' stage
Cheers, for the feedback, i'll look into the errors.
I know that if the screen is unlocked the Home LED will stay on until you lock/unlock the screen, but that should be an easy fix (hopefully), and i've not set up the Thread's quite right i don't think which could be causing the timing errors.
I'll be spending all of tomorrow getting this thing working so i'll report back
Awesome! You are the man!
A thought for down the road development:
Earlier today when I was thinking about this, I imagined an interface where the user could "record" their own flash sequence for each type of notification they had - email, sms, mms, missed call, etc. Just choose which notification they want to specify, click record, then tap the capacitive buttons in the sequence you want them to light up, then end the recording. Interval timing could be recorded or specified manually. Just a few ideas!
Thanks so much for this. I'll give it a run soon.
Awesome work. Wanted something like this. I hope you will be able to add notifications for misssed calls and gmail as well. Keeping my fingers crossed.
I am having some issues with widgetlocker. It seems that about 1 out of every 10 times I hit the power button to turn the screen on the stock lockscreen shows up instead of the widgetlocker screen. Why is this happening and how can I fix it?? Thanks.
happens to me too a little less frequently though, maybe 1 in 15 or 20. no clue btw
primetime34 said:
I am having some issues with widgetlocker. It seems that doesnabout 1 out of every 10 times I hit the power button to turn the screen on the stock lockscreen shows up instead of the widgetlocker screen. Why is this happening and how can I fix it?? Thanks.
Click to expand...
Click to collapse
Are you using the supercharger script? I am, and found that the two don't play nicely together. I'm guessing widget locker doesn't have high enough priority, but what do I know. I switched my settings down to megamemory one and it helped, but not enough to keep it.
Supercharge script > widget locker. IMO. I had to pick one...
I also noticed that widget locker enables while im on the phone forcing me to unlock it to hang up the phone. I contacted the dev and he said my settings are correct so its the phones fault. yay chalk another one up for this pos phone.
My Thunderbolt is rooted, and I have tried several different ROMs (some AOSP even) and different kernels, and still I get this strange problem... I use WidgetLocker and fairly often when I go to unlock my phone, the touch screen doesn't work. I have to turn the screen on and off several times and sometimes that works, but it may take up to several minutes for it to finally register my touch. I even sometimes have to pull the battery because after ten minutes, nothing is responding. At first, I thought it the ROM/kernel - I used BAMF in the beginning and that is when I noticed it. Then I switched to ShiftSense, and I barely noticed the touch screen ever failing on me, but the lack of GPS locking and accuracy made me switch to NonSense, which I enjoy but again the touch screen not working at the WidgetLocker lock screen comes up again. My other theory was maybe the HTC Ring Lock Screen gets in the way, so I downloaded NoLock and disabled it, but that didn't work. Then I tried use the WL HomeHelper, but that didn't work... I tried different settings, but no avail. I really enjoy WidgetLocker and I want to try to keep it, but I am not sure what other things I should try to fix this problem. Any suggestions would be greatly appreciated! Thanks guys!
widget locker did that to me several times so I gave up on it. Its definitely a problem with widget locker and not your phone or ROM. It freezes. I even set it to unlock with long press of back button and that would freeze as well.
my phone does the same thing, i think its a problem with our phone and gingerbread. it happens less with froyo. I believe its a radio issue.
Sent from my ADR6400L using xda premium
I have used widget locker on over 10 different android devices I've own. I've never had a freeze issue with it. Reason I've had freeze issue starting with low RAM device. Then voltage to low or cpu frequency to low.
Is there a good alternative with Widget Locker? I just love the use of my own custom slider/widgets/custom background... Does any other app do that? I sort of want to try another app and test to see if it is in fact my phone/RAM/ROM/whatever or Widget Locker.
Aup808 said:
Is there a good alternative with Widget Locker? I just love the use of my own custom slider/widgets/custom background... Does any other app do that? I sort of want to try another app and test to see if it is in fact my phone/RAM/ROM/whatever or Widget Locker.
Click to expand...
Click to collapse
take off or freeze widget locker for a few days and see how your phone does. If it doesn't freeze, then you know its the app.
As for the guy that has used widget locker on 10 devices without problems, I call BS, I tried it on stock, and several customs and always had problems.
I sort of like the features of WidgetLocker than my default lock screen doesn't have and the look of it, so if I turn it off, I sort of want to try to find a replacement app in the meantime.
I just wanted to chime in and say I have this issue with my Thunderbolt and Widgetlocker as well. I've found that it usually freezes if I let my screen turn off by timing out. I'll turn it back on and the screen doesn't respond at all. I've found that if I let my screen timeout again while on the Widgetlocker screen, my touch screen will be responsive the next time I turn it on again.
Sent from my Bolt
Same problem here, I stopped using widget locker and just use the sense 3 lockscreen now.
I just wanted to put in my two cents - I was have the same problems with WidgetLocker on BAMF Forever (1.0.7 & 1.0.9). I found another thread on here (http://forum.xda-developers.com/showthread.php?t=1151269) that someone with a BAMF Sense 3 ROM and a custom kernel was having the same issue. Someone else suggested upping the voltage on the kernel to 368 or changing the kernel. It didn't work for him, but it did for me. I'm not using a custom kernel, but there is an option to change that in BAMF Settings. I've been running it at 368 for several days now and I only had one lockup (but that was shortly after bootup and the phone was probably busy doing other things in the background). HTH
Hi all
I'm very satisfied with my S6 Edge (925F) but I'm facing a weird problem: when I unlock the phone using my fingerprint(s), it works perfectly but sometimes it's not the home screen which is displayed, but another random app, (i.e Facebook, Settings, News Republic or other...)
I have to press the back button to return to the home screen...
Anyone having the same problem? (not a big deal but...)
Started to happen to me as well a couple of days back. It's strange because it never happened before and I didn't change anything on the phone.
Never happened to me so far. Are you sure you weren't already in that app when you locked your device? The fingerprint unlocks into the last open app. Go back to home before locking.
Another possibility is that you are tapping a notification before unlocking. Say you have a notification from FB and you tap on it. The screen will stay locked, but it will open the FB app. Unlocking with fingerprints will then show FB open. Same can happen for email, texts, etc. You can also pull down the status bar and tap settings, then when you unlock, settings will be open.
TXRangerXDA said:
Another possibility is that you are tapping a notification before unlocking. Say you have a notification from FB and you tap on it. The screen will stay locked, but it will open the FB app. Unlocking with fingerprints will then show FB open. Same can happen for email, texts, etc. You can also pull down the status bar and tap settings, then when you unlock, settings will be open.
Click to expand...
Click to collapse
Thanks but not at all.
It happens randomly, either I'm in an app or not (and if so, it's not necesseraly the one I was on!)
Quite mysterious...
I was using Nova Launcher (maybe the cause), will give 2-3 days Touchwiz a chance, and will report back...
Hey guys,
same problem for me. It is not dependant of the unlock method (i'm experiencing it with finger print or regular unlock).
I think it is a Nova launcher bug, only occur with nova for me.
++
exploreresp said:
Hey guys,
same problem for me. It is not dependant of the unlock method (i'm experiencing it with finger print or regular unlock).
I think it is a Nova launcher bug, only occur with nova for me.
++
Click to expand...
Click to collapse
I think so...unfortunately...
I think it's the latest nova launcher beta version that causes the issue.
I'm using Nova since I got the phone, a month ago, haven't experienced this.
I have been having this problem too and was about to start a new thread. I am using Nova too, though I did try installing the google now launcher and seemed to have the same problem. I suppose Nova simply being installed may cause the problem.
I will try uninstalling Nova and use TouchWiz for a bit. Not sure how long I will last, I think I prefer the random apps to Touchwiz.
How did the rest of you get on after switching away from Nova?
I have been experiencing this issue as well but ive been using the nokia Z-launcher. I have a feeling it might also be my fingers inadvertently touching the curved portion of the screen when i hold it.
I have the same thing happen to me. I thought I was going insane. The worst part is, I'm on a note 3 and I'm using touchwiz lollipop. I'm 100% sure no applications are running before I lock the phone, and when I use the pattern unlock, whatever application shortcut that was on the screen when I lock the phone, a random app from that screen will run when I unlock the phone. It doesnt happen all the time, but it happens at least a couple times a day.
Reason
Hey guys. I am using Nova Launcher too. And I have the same problem. I don't have the sollution, but I found the reason. ? When you lock your S6, the touchscreen stays for a second active. And if you hit an app in that second it will open when you unlock your S6.
Sorry for my bad English, I hope someone can do something with this information.
Cya ??
Ignotis said:
Hey guys. I am using Nova Launcher too. And I have the same problem. I don't have the sollution, but I found the reason. When you lock your S6, the touchscreen stays for a second active. And if you hit an app in that second it will open when you unlock your S6.
Sorry for my bad English, I hope someone can do something with this information.
Cya ?
Click to expand...
Click to collapse
It seems that if the Nova's desktop margin is set to "Medium" or "Big", this problem is reduced, but I don't know if it's fully solved. Will see...
Have you found any other solution?
eruyome said:
It seems that if the Nova's desktop margin is set to "Medium" or "Big", this problem is reduced, but I don't know if it's fully solved. Will see...
Have you found any other solution?
Click to expand...
Click to collapse
I think that has nothing to do with it. It could be true that it reduces it, but the only reason it would do that is because:
Mostly when you lock your S6 your fingers touch the side of the screen.
When you set margin to "Medium" or "Big" and you lock your phone, your fingers wil most likely touch no app on the side of your desktop, because the margin "pushes" them to the middle of the screen.
I haven't found a solution. Still waiting for an update to fix it.
Ignotis said:
I think that has nothing to do with it. It could be true that it reduces it, but the only reason it would do that is because:
Mostly when you lock your S6 your fingers touch the side of the screen.
When you set margin to "Medium" or "Big" and you lock your phone, your fingers wil most likely touch no app on the side of your desktop, because the margin "pushes" them to the middle of the screen.
I haven't found a solution. Still waiting for an update to fix it.
Click to expand...
Click to collapse
Yes, that makes sense. Anyway, if looks perfectly good with marging set to medium, and I've had no issues with this problem since I changed the setting (yesterday). So if it reduces the problem so much, I can live with it...
eruyome said:
Yes, that makes sense. Anyway, if looks perfectly good with marging set to medium, and I've had no issues with this problem since I changed the setting (yesterday). So if it reduces the problem so much, I can live with it...
Click to expand...
Click to collapse
Great news, the update I got today (4.2.2) fixed the bug. It was from Nova. I think this ends the thread. Happy new year guys. Cya!
Yep, it is finally fixed! Cheers!
Still happening in the latest Nova... running in Oppo phone.
I've tried a couple of the recommended apps. Pixel Pulse was still too subtle to be noticed from afar. I couldn't get Always on Edge to wake up my phone screen, though after a lot of trouble it DID finally blink when I had the screen on... I'm almost positive I gave it all the requested (and optional) permissions. Is there another recommended app that could produce a noticeable blinking light when I get a notification? In case it matters, I am using a Pixel 3a.
E_Pixie said:
I've tried a couple of the recommended apps. Pixel Pulse was still too subtle to be noticed from afar. I couldn't get Always on Edge to wake up my phone screen, though after a lot of trouble it DID finally blink when I had the screen on... I'm almost positive I gave it all the requested (and optional) permissions. Is there another recommended app that could produce a noticeable blinking light when I get a notification? In case it matters, I am using a Pixel 3a.
Click to expand...
Click to collapse
Have a look at NotifyBuddy
decker39 said:
Have a look at NotifyBuddy
Click to expand...
Click to collapse
I tried it, but it doesn't seem to work for me. I don't know if it is because notifications are waking my screen, or what. But I don't get any notification light while my screen is off.
EDIT: I had seen the developer reply to a comment saying it wouldn't work after screen wake, by design, as a deliberate effort to save battery. I just turned off the "Wake Screen Upon Notification" option on my phone, and that made NotificationBuddy work. But I want something that will still work after the screen wakes.
I am pretty sure with this device your only choice is to use AOD and then these apps work. Otherwise, they can only really wake the screen. I use LED blinker with AOD on and it works every time, but can be a bit glitchy when trying to open the phone to see the notification. What I mean is, if I use my fingerprint, it does not always go to homescreen, I have to press power button to relock and try again. This is really google's fault for not adding a native option for some kind of blinking on the screen. I think no matter what it would require AOD to work though.
I've always said that something as tiny as the notification LED on Android phones made them far more useful than iPhones. I'm disappointed that Google has removed this once great advantage over Apple, just as it did with the old notification ticker from the pre-lollipop days.
wangdaning said:
I am pretty sure with this device your only choice is to use AOD and then these apps work. Otherwise, they can only really wake the screen. I use LED blinker with AOD on and it works every time, but can be a bit glitchy when trying to open the phone to see the notification. What I mean is, if I use my fingerprint, it does not always go to homescreen, I have to press power button to relock and try again. This is really google's fault for not adding a native option for some kind of blinking on the screen. I think no matter what it would require AOD to work though.
Click to expand...
Click to collapse
Even with AOD on (which is not my preference) these apps still don't seem to work correctly. Do I also have to disable the wake screen for notifications option? I really dislike these choices.
I'm getting really frustrated that I practically have to hack my phone to get it to do things that my phone from 4 years ago could do natively.
E_Pixie said:
Even with AOD on (which is not my preference) these apps still don't seem to work correctly. Do I also have to disable the wake screen for notifications option? I really dislike these choices.
I'm getting really frustrated that I practically have to hack my phone to get it to do things that my phone from 4 years ago could do natively.
Click to expand...
Click to collapse
Not sure, I am running a custom rom. All I have done is enabled AOD and installed the app and it works.
I have led blinker, it's the best one I found... Not as perfect as a real notification led but it do the work