yashsingh1/xdaforums huggingface dataset:
[Android Apps and Games] SuperMario=ITA=:
I've rooted my phone, so I use RootHelper and HomeHelper options in WL. WL replaced the default lockscreen completly. If I press home during a NoLed notification, I return to WL lockscreen. No default locker, neither the home.

Also, I downloaded again from the market an hour ago too. Same behaviour.

Anyway, the go SMS problem is not so important. I can uncheck the "turn on screen" without problems.

But the proximity sensor problem is still there and it is far more important than others.

As I said, the proximity sensor is on (I can see the red light inside turning on), but when an object covers it, it turns off and NoLed notification remains on. After that, the sensor is not turning on without get the notification read.

Ask anything if you had to ;)
[Android Apps and Games] madmack:
The sensor is on, and when covered, the screen is still on? is this what's happening?
[Android Apps and Games] SuperMario=ITA=:
yes.

and the sensor won't turn on again if the object is removed.
[Android Apps and Games] madmack:
that, i can't explain . lol

the sensor either works or it doesn't. if you see that the light is on and an object moves over it, the screen has to respond directly to it by shutting off. if the screen does shut off but doesn't turn back on, then i can figure something out, but that is not happening with you. :confused::confused:
[Android Apps and Games] SuperMario=ITA=:
yeah, quite odd. But why in 5.0.5 there is no problem? Tried to uninstall reinstall update multiple times, no luck. :(
[Android Apps and Games] madmack:
you know how to get a logcat ?

can you please try the attached file. I think I know what's happening but I'll need to see your logcat to be sure.

first install this apk, then get a NoLED notification. wave your hands in front of the proximity sensor, (make it disable itself) and then send me the logcat via pastebin or here in code quotations.
[Android Apps and Games] SuperMario=ITA=:
errr no, don't know how to get a logcat. If you tell me how I will surely provide. ;)

For now, installed your app (5.0.6 debug), bug still there.
[Android Apps and Games] madmack:
ok, download aLogcat from the market.

after you do the steps.. and replicate the issue, save it to sd and paste the content to pastebin. post a link to your paste here.
[Android Apps and Games] SuperMario=ITA=:
done

http://pastebin.com/tzKPd5Eq

anyway, I discovered that I can't get any notification icon with all programs that use popups.

So, I can't get notification of Go SMS, but also of Viber, Whatsapp and others with popups.

Can you make NoLed fully compatible with WidgetLocker again? Maybe, if NoLed detects WL installed, then behaves like 4.8 version. If not, it behaves like newer versions.

If you can't do this, I must use the 4.8 version because I need both programs running fine...:(

Also other people that use widget locker because it was the only one compatible with NoLed would be disappointed of this incompatibility...
[Android Apps and Games] gollyzila:
I'm using Widgetlocker, GoSMS PRO w/ no pop ups, and the latest NoLED with no problems except some rare times when NoLED shows while the screen is on.

Also, since I don't use a popup with GoSMS is there a way to disable the SMS delay in NoLED?
[Android Apps and Games] madmack:
I just checked your logs, it seems that you have the "Home" key to dismiss disabled in NoLED settings that's why the proximity sensor is not working properly.

Please make sure that "Home" is checked. See if the proximity sensor problem continues.

Otherwise, NoLED is compatible with the default WL settings. It is acting up because you don't have a lockscreen to fall back onto by using the "Home" replacement thingy in the settings.

Anyways, what you said is true. Any 3rd party popups will malfunction as well if you keep that WL setting intact. Your only way out of it would be to put back the default lock screen. It is to your benefit anyways as your settings will also wake the screen by pressing on any of the volume keys if i remember correctly.

The proximity issue you're having will be solved once you have that "Dismiss with Home" enabled in NoLED.

Edit: what version of WidgetLocker are you using? I tried to replicate your issue by setting the "homeHelper" thingy and NoLED, (even with the home button disabled) still works with the proximity sensor as it should. It seems like I can't even replicate your problem.

To disable the SMS delay, simply uncheck it. Don't ever relaunch the settings screen because that will check that setting back.

I'll add an option that will show a "don't remind me again" kinda dialog. I just had to release something as a quick workaround for the GoSMS users that we have and that are pretty vocal in the Market comments :cool:
[Android Apps and Games] EricB68:
it is the same story ever. The phone is only as smart as the user, holding it in his hands. At the moment I feel very stupid, cause I am doing something wrong.

-SGS9000i Andro 2.1 factory firmware.

-NoLED 0.6 installed, is shown as service.

-let the phone sleep, waked up, as described in the start thread.

After missing my own call from my landline, it shows me the normal notification from Samsung and switches off the screen, as it does without NoLED. Unfortunally it keeps being black, whole screen :confused:

Because of the fact this nice phone is absolutely new to me, I am sure I have done something wrong. But what is wrong?
[Android Apps and Games] Clay:
Best idea I have heard all day. The soft keys are independently lit as when you push one of the soft keys it turns the light off. This would be great if possible.
[Android Apps and Games] emelie:
there's a seperate thread for this app idea (buttons backlight for notification):

http://xdaforums.com/showthread.php?t=706426
[Android Apps and Games] madmack:
Yes, I believe when the screen is activated, all pixels have a slight "glow". I guess AMOLED's technology does emit some light even when displaying black pixels.

I'll shoot em an email and see what we can do.

I will have to agree that leaving the notifications on for a long time drains the batteries quite considerably.. Perhaps we can make NoLED timeout after an hour ? I'm done implementing a toggle widget that you can place on the homescreen to turn NoLED off when you know you won't be attending your phone for a while. It should alleviate that problem. I'm also considering setting up a GUI to disable/enable NoLED at certain times of the day that the user specifies.

Redownload 0.6 or wait til 0.7 is released (should be anytime now), I already made the green dot "lighter". I think it matches the brightness of other dots now.

Try waiting for exactly 10 seconds after the missed call. Screen should turn off, and the blue dot should appear. Don't activate the screen before that.

Speaking of which, I should really use a smarter way to display these missed calls notifications instead of waiting a whole 10 seconds. oh well, something else on the Todo list.
[Android Apps and Games] Karupan:
An option where the user can set the amount of time the notification can be active will be really helpful! It can also solve most of the battery drain issues.
[Android Apps and Games] muntos:
Don't know why and how to replicate this, but I'm sure that the notifications (at least for missed calls) are not triggered always. Just rebooted my phone, called myself from another phone, screen turned off and after 10 sec I had the notification.

Dismissed the missed call, did once again the same steeps, this time no notification :(

I know that there are no many information to deal with, maybe if you could integrate (at least until a stable version is out) a debugger/log that you could look at it to see what's wrong wouldn't be a bad idea ?
[Android Apps and Games] EricB68:
Ok I know that 10 sec can be a long time, so I made an other test and waited more than a minute. But there was no point on the screen :confused:
[Android Apps and Games] madmack:
It did happen to me once or twice too. Anyways, I did some redesign on how SMS and missed calls are handled in v0.7. Hopefully this will fix the issue. (no longer have to wait 10 seconds, see change log)
[Android Apps and Games] madmack:
Eric, try with 0.7. this might fix the issue. Otherwise, try sending yourself an email or a gtalk message and see if anything does show up on the screen?
[Android Apps and Games] sturmeh:
I know the purpose of the app is to make notifications visible whilst using minimal power, but could you make an exception for periods immediately following an event?

For example, if someone talks to me on Gtalk, can't the screen render the message for a second, then dissapear and do it's usual thing?

That way you can have the phone on the table locked, u can get a message and read it without even touching the phone.

That goes one step ahead of the lack of notification light. :)
[Android Apps and Games] EricB68:
OK, now it is getting funny, can tell you that it works with version 0.6 now.

After testing the mail and messenger notification, the phone notification also works.

But the time to get the point running on the screen was ca 45 sec. after the screen became black. That is no problem at all :)
[Android Apps and Games] dafunky:
That would be awesome, as Widget Locker is an excellent app and I can't use NoLED until this problem won't be fixed :rolleyes:
[Android Apps and Games] muntos:
Installed 0.7 but still there are situations where the notifications won't trigger... :(

Also, don't know if this is the normal behavior or not, but lets say that I have one missed call, the NoLed is on screen, I press the Homekey and see the lockscreen, then I do nothing so the screen turn off again. In this situation the notification won't show up again, is by design or not ? On other applications the notifications are triggered until the events are cleared.
[Android Apps and Games] boardbunny_79:
how do i download on my mac?

I would like to use this program, but i have a macbook and i don't know how to dl the file. can you please help?
[Android Apps and Games] elbasso:
Version .7 is amazing! It even works with Handcent when the pop-up messages are used. Also, you can see multiple notifications at the same time. That's truly wicked. Won't get that with back-light button notifications.

All respect to madmack.
[Android Apps and Games] chongchoe:
v.7 home key not working

Installed v.7; notification dots work perfectly. I get all the different colors. But the home key isn't working now. Each time I press it, the led lights up, but the notification dot stays there and keeps bouncing. I've done everything I can think of to unlock the phone, but no luck and had to restart. I've tested it three times now and the home key hasn't worked every time and I've needed to restart each time.

On Samsung Vibrant.
[Android Apps and Games] madmack:
This is strange, it does disappear here when I press the Home button. It could be caused by some other app or screen lock that is capturing that key.
[Android Apps and Games] rotzleffi:
doesn´t work for me on FW JP3

Hi, first n1 idea and its really a must for every Galaxy S User.

Everything worked great, but 0.7 doesnt work anymore.

I have Firmware Version JP3 and its possible to install, but

even if i restart or turn it on by widget application hangs.

In Application menu its installed but u cant stop or start it.

I deinstalled, restarted and reinstalled it allready but still application hangs after turning on by widget.

Any ideas?

greets, rotzleffi
[Android Apps and Games] madmack:
It's probably a permission conflict between Eclair and Froyo. If you know how to trace the exception in logcat. I would appreciate it if you could send that to me via pm. I can easily fix this if I have the exception :)
[Android Apps and Games] Jamesoow:
What if we did something like this:

I'm not so good at making such animations.. but u get the idea!

Or would this hog too much battery ??
[Android Apps and Games] SuperMario=ITA=:
1) never mind. I upgraded WL, proximity sensor works fine now also with Home unchecked, like before ;)

2) NoLed worked fine with HomeHelper & rootHelper on in WL in version 4.x, so why now you tell me to use it only with default WL settings?

I will not use WL with default settings for obvious reasons...Why you made NoLed losing compatibility with WL with HomeHelper&RootHelper on?

If before it ran like a charm, I don't understand why you keep me telling that it is compatible only with default settings... :/ :confused:
[Android Apps and Games] madmack:
lets forget about what I said earlier if everything is running fine now :)

the problem is that I introduced some stuff that will make NoLED work sans lockscreen and at the same time support the default popups in goSMS. these changes directly relate to the bug on the old WL "homeHelper" so that's why I was suggesting you stick to the default settings.

anywho, its all working now so lets be happy that we resolved your issue without disabling the homeHelper.
[Android Apps and Games] madmack:
thanks for the logcat. can you please try this attached apk and see if permanent time will stick to the screen this time?
[Android Apps and Games] takerhbk:
although people say that it is useful. I never like this. Mayb just my personal choice. I find it to be using much battery. I may be wrong :)
[Android Apps and Games] RaymondPJR:
NoLED

You have to effectively use the time-out features of your choice, or you will get battery drain.:)

EDIT:

Nope, it changes even faster, by about half a second and still loops.
[Android Apps and Games] SuperMario=ITA=:
It's no all working, the popup issues stille there. :(

I resolved only the proximity sensor problem.

If in Go SMS I can turn off the option "turn on screen", in other programs that use popups there isn't such an option, so NoLed is useless for them.

seems that introducing new code made NoLed compatible with all lockers but only with default settings. But I will NOT use WL with default settings, because usually I got the default lockscreen and other issues...

I will use NoLed 4.8 if you can't restore compatibility with WL with no default settings. But I will miss new interestings functions that you introduced in version 5.x

You can't release a new version that loses compatibility with certain other program's functions. Try to improve compatibility with other lockers without changing the NoLed behaviour with WL. It will be much appreciated ;)
[Android Apps and Games] Warren_Orange:
Hi.

First off I want to say what an awesome app NoLed is. Really top draw.

What I want to do is set NoLed to display my hotmail account. I've read I need to go into monitored apps and enable NoLed in accessibilty settings. When I go to do this it comes up with a warning that NoLed can see everything I type on the handset, included passwords etc.

Is this safe to do? Won't it be a security risk?

Cheers.
[Android Apps and Games] madmack:
I really want to fix this issue that you're having. Can you tell me which version did this problem start occurring with?

Thing is, I've setup my phone to use permanent time display, and I also put in the audio reminder just as you've done. My log looks exactly like yours and the time displays correctly without disappearing. This is on my device and on the emulator. It seems that NoLED on your phone is getting dismissed manually as I see no trace of "automatic dismissal" by my own code. I'm starting to suspect a task killer/manager might be the culprit here. Are you using any such app? I think this task killer terminates apps if the screen is off and given that NoLED (starting from v5.0) starts the notification screen before switching the screen on, the task manager might be terminating it.

Is this happening with all types of notifications or with permanent time only?

I'm at a point of no return to the old inefficient method of displaying notifications given the rewrite in v5.x and above. I disagree fundamentally that I should write code that specifically makes NoLED work with some lock screens and leave out some others that don't expose any APIs. The right way of doing this is in a global solution that works universally, not one that patches the code for certain locker apps. :rolleyes:

Having said that, please give me examples of applications that use popups. I might be able to add a little "trick" to make the newer NoLED work with these as well sans lockscreen.

Hi Warren,

please read the FAQ #10. link to it is in the OP (first page of this thread).
[Android Apps and Games] SuperMario=ITA=:
Every messaging programs at all, in fact. Viber, Whatsapp, GO SMS are the first I tried. Also Calendar Snooze.

What about display every notification that has an icon on the top left side in the statusbar? If there is an icon there, and the program is marked in NoLed, then display a NoLed notification. Could be this method good?
[Android Apps and Games] madmack:
well, that's what "monitored apps" does really. it checks your status bar for modifications by these apps that you select in there. the reason why they're not triggering is because your setup fails the two checks 1. is screen off. 2. is the default lock screen present.

i think if you use the "delay all" feature to make noled trigger after these popups appear, noled will trigger correctly for you.

now, if only i can find a way to send myself whatsapp messages to test this thing.. ..
[Android Apps and Games] Nelthalin:
I'm currently testing battery drain.

I'm getting the feeling white icons are causing high drain (not strange because you need multiple leds active to make that color)

Test setup:

Stock Rom + Abyssnote 3.7 Kernel

CPU UV 1600 MHz 1350mv max - 100 825mv min

noLED on with:

-grey clock Jumping arround the screen (quite big, bit bigger then medium icons but its only grey tekst (build in clock))

-Call missed dot in upper left corner

-noLED Weather on jumping arround the screen.

I currently have a drain of 1% every 6-7 min.

With only a Call missed dot in upper left corner and a SMS icon it seemed to be less. But i will test that tonight.

But this kind of drain is to much over night. It will your battery very fast: 9-10% every hour. And thats with only one icon with white in it (its mostly white with blue and a bit of yellow because if the weather. It has some white teskt next to it with the city name and temperature) and some tekst on the screen from the weather info and the grey clock.

But i will try to do some extra testing so see what causes drain. I dont like to use timeouts but maybe i can minimize it by using other icons.
[Android Apps and Games] madmack:
Raymond,

can you test this debug version, replicate the issue and then send me the logcat? Preferably on pastebin.com

It's driving me crazy, lol. but this version I'm sending out is filled with debug messages that should give me a clearer picture.
[Android Apps and Games] Nelthalin:
Ok i did some extra tests:

Test2:

Disable noLED Weather. Result: 1% drain in 7-8 min. In 62min i lost 9% battery

Test3: Disable clock only a big missed call icon (largest). Result: Still 1% in 7-8 min. i again lost 9% battery in 60 min of testing

Test4: only a small dot in the upper left corner. Result: Again the same 1% in 7-8 min and lost 9% battery in 60 min of testing

So it seems it does not matter much how much of the screen is on.

What i also noticed when i was in the dark and had the small dot in the upper right corner that the whole screen lit up a bit. When i moved my hand over the proximity sensor it went to complete black.

So its not local the whole screen is still lighting up a little bit.

I checked the screen that should be inside a Galaxy Note: It said it was a Super-Amoled HD. A new version of the Super Amoled. And not the Super Amoled Plus technique that is used in the SII

I dont know if that makes a difference but when you use noLED you will keep having a drain of 7% per hour (in case of a Galaxy Note). Maybe a little bit more depending on your settings :(

Btw i checked my idle drain and thats 0-1% per hour. so its less then one 1%

Edit:

I'm now testing the blinking option. It turns the screen on for 0,5 / 1 second every 8 seconds. Maybe that will lower the power consumption.

I already noticed it sometimes fails to keep the interval regular. Sometimes it stay's off a bit longer and after that it goes on and off within 2 seconds for 2 times. When i look in the dark the screen is completely off during that 8 sec interval. If it lowers the drain to 2-3% per hour i'm happy.

Edit2:

I did the test: screen on 0,5 sec screen off 10 sec. Battery drain 1% per +- 20-22 min battery was down 2% in 44 minutes. So i will be using these settings in the future :) maybe a little bit faster interval but for the rest its working like a charm. A real improvement.

Edit3:

One more thing. I used the lowest brightness setting in the battery saving menu for all my tests. Its more then bright enough like that. And with auto the default brightness is higher then the lowest setting even when its dark in the room. So i decided to use a fixed setting.
[Android Apps and Games] ew:
I would like to thank you from the recent modification to NoLED that enables the "no lockscreen" mode. I reluctantly stopped using NoLED because I hated having to unlock all the time. I tried a number of "nolock" type apps, but none were as smooth as I wanted. So, I reluctantly used a second rate substitute for NoLED.:D

I was overjoyed to see that you had rewritten NoLED so that a lockscreen was not required. Perhaps this feature will case some challenges, but it is definitely welcome.
[Android Apps and Games] RaymondPJR:
NoLED

It started with 5.0.5. I have been reverting back to 5.0.3b and the problem always goes away. One thing I noticed was that my weather widget was not updating. I noticed it was always saying 40 degrees and realized that was not correct. I can't say for sure, but I wonder if the newer versions somehow turn off the weather sync and maybe that's why it kept waking up. I flashed to a new version of my ROM last night, but I'll push install 5.0.7 again to see what happens. I have no task killers of any kind.

EDIT: Nope, it has nothing to do with the weather widget. I re-installed 5.0.6, manually updated the weather, and it is cycling as I write this. I'll install the other version you posted just above before I do a necessary wipe install of my ROM tonight. Have to find out what pastebin is first, though, lol.

EDIT: I'm letting it cycle right now. I have pastebin.com open and ready. I have named it Madmack 5.0.7b.debug in advance. I also sent myself an email to see if it will come through and if the same behaviour is exhibited. Can't wait for something to show up, lol.

EDIT: Interesting, I have the Gmail app set to poll every 5 minutes for new emails. I'm past that time interval right now and nothing is showing up as it cycles. On 5.0.3b, which I was using all day today, I got several Gmails and several calls, no problem. I'll wait two more minutes then send the logcat.

EDIT: 6:42 Pacific time, done!
[Android Apps and Games] madmack:
I really appreciate these tests. They're something I didn't take the time to do them properly so thank you.

The SII and S both have the same dimmed back light effect with these supposedly completely black pixels. I actually did learn a thing or two from your tests and that's a solid testimony to Blink's battery savings.

You wouldn't mind if I link to your two posts from NoLED's FAQ?

It is causing a lot of challenges indeed :o I always wanted to make NoLED work without a lock screen. I just never really invested enough trial and error to get it to behave properly and consistently. I'm still struggling on that front a bit :rolleyes: but I'm sure we'll iron out all the problems sooner or later.

pastebin is simple really, just go to pastebin.com, paste the content of the log file that you obtain from alogcat, and once you submit, it'll give you a URL. copy that URL to me here.

once i get that, i'll hopefully fix that issue.