Hey all,
I've been looking around for a while, researching about the capacitive lights on the Captivate. I have two friends with Vibrants, and their lights are much more brighter and responsive than mine. Mine just look really dim all the time. I was hoping that I could get them brighter so I could use something like Blinky or BLN pro instead of NoLED, seeing as it eats up so much battery. The problem is that they're so dim that I can't actually tell when they're flashing. Does anyone have any ideas of any way to control these lights? I don't know if it's important, but I'm running Serendipity 5.12 with the SpeedMod k13c kernel. Any help would be great.
Thanks!
Related
Hey guys, a friend of mine has this ap, NoLED for his galaxy and its friggin awesome, and I tried it on my incredible just to see if it worked (didnt see anything about phone support) but my phone started spazzing and rebooting.
wondering if anyone else can get it running or if a possible port might happen?
heres the guys home page
http://www.devasque.com/noled/index.php
This is an awesome idea. Would really like to see if this can b ported to the inc. Since the inc has a shabby led as is, turning the screen into a led notification would b a +1. Hopefully some of the devs can respond on this.
I would not agree. For several reasons. I had two of the GS phones, vibrant and epic. The vibrant has no led so they created that app.
For one... it caused several problems. And didn't help the meager battery life. Although development perhaps continued along after I uninstalled.
Two... even on AMOLED it uses alot of battery to constantly keep that light on. Okay well on AMOLEDs, black pixels use no power. Each pixel is self powered. so theoretically only that tiny led dot is using power. I just remembered the Dinc's use AMOLEDS, so that is not necc an issue, except for the SLCDs which are backlit. In any case ask Nexus owners how much battery one led can use.
Overall, I changed my mind... it's xda, the theory here tends to be if you can do it, you should. So hey go for it. Just remember my review. It's useful to a point although I always wished you could swap the red led for pictures or whatever else you want, but it does drain your battery and can be confusing in use.
i use it all the time without issues, but it kills battery life. 100% wake time blows.
I have been using it for a while as well, works great but battery life sucks.
Seems like all the kernels for me are having small problems with the backlights. The only problem is that it no longer comes on after turning the screen on, you have to tap one of the softkeys and then the light up. They go off when the screen goes off however.
Currently i'm on Stock Rom, Trinity 1.2.2 Kernel. I've had the same problem with morific's kernels with stock/Cm7 as well. Its not a big issue as voodoo sounds amazing, but im a slight perfectionist.
Thanks in Advanced
Rob
Ok,
So my home row buttons (Menu, Home, Back, Search) do not light up as they should! if the room is dark they will not work at all! and ive never seen them work in a dark room! However every day in the late afternoon when im in my living room and the phone is charging they will just light up! (at first i though it was a refection or just ambient light in the room so i grabbed the phone and ran into my closet and WOW they light up!) so i figured it was something with my settings so i reset my phone to new and still same problem, then said WTH and rooted and updated to 2.3.4 (best thing ive done with it so far!) and have the exact same problem... So then i decided to try another charge (brand new out of the box 1 day old!) and the lights will do the same and light up when its moderately light in the room but then they wont turn off...
So a chat with samsung and they tell me that these phones dont have that feature! so off to verizon and lets test a few more devices!!! and what? at some point they lit up also in inappropriate lighting conditions, so after puzzled VZW people i consult samsung again and they tell me yet again that the featured isnt offered on this phone, so my guess is that its a software flaw?
any ideas?
anyone having lighting issues?
thanks
Wow, that's a lot of exclamation points. I don't know what you're talking about, mine work fine
Sent from my Droid Charge running Humble 1.4
Pictures
Here are 2 pictures that show what im talking about, i will try to get a few more
Odd, works fine for me. Is it possible that you have a screen protector covering your light sensor? In the day time the back lights are off, then if I cover the light sensor they come right on.
mtmcghee said:
Ok,
So my home row buttons (Menu, Home, Back, Search) do not light up as they should! if the room is dark they will not work at all! and ive never seen them work in a dark room! However every day in the late afternoon when im in my living room and the phone is charging they will just light up! (at first i though it was a refection or just ambient light in the room so i grabbed the phone and ran into my closet and WOW they light up!) so i figured it was something with my settings so i reset my phone to new and still same problem, then said WTH and rooted and updated to 2.3.4 (best thing ive done with it so far!) and have the exact same problem... So then i decided to try another charge (brand new out of the box 1 day old!) and the lights will do the same and light up when its moderately light in the room but then they wont turn off...
So a chat with samsung and they tell me that these phones dont have that feature! so off to verizon and lets test a few more devices!!! and what? at some point they lit up also in inappropriate lighting conditions, so after puzzled VZW people i consult samsung again and they tell me yet again that the featured isnt offered on this phone, so my guess is that its a software flaw?
any ideas?
anyone having lighting issues?
thanks
Click to expand...
Click to collapse
The light sensors (which controls auto brightness and the backlights on the hardkey) is broken in the kernel for Gingerbread..
If this is a huge issue for you you might want to consider going back to Froyo
kejar31 said:
The light sensors (which controls auto brightness and the backlights on the hardkey) is broken in the kernel for Gingerbread..
If this is a huge issue for you you might want to consider going back to Froyo
Click to expand...
Click to collapse
But he said it happened with the new phone and the verizon display one...?
Sent from my Droid Charge running Humble 1.42
It might even be broken on the stock Froyo. All the people who said it's working fine for them right now are running custom ROMs, kernels, firmwares and all that jazz. Maybe it was fixed through one of these custom updates. I dunno.
I just got a brand new Charge (thanks to the Fascinate swap program).
The bottom buttons do not light up. This is fresh out of the box.
I also do not see any way in which they would light up - the icons appear to be painted on to the physical buttons. No underlay for LED backlight.. but I suppose there is one if custom ROMs allow for it.
Which I will know shortly
reply
blarrick said:
Odd, works fine for me. Is it possible that you have a screen protector covering your light sensor? In the day time the back lights are off, then if I cover the light sensor they come right on.
Click to expand...
Click to collapse
there is no screen protector or case on either of the phones, and both phones were cleaned well to make sure nothing was hindering the sensors.
[/QUOTE]The light sensors (which controls auto brightness and the backlights on the hardkey) is broken in the kernel for Gingerbread..
If this is a huge issue for you you might want to consider going back to Froyo[/QUOTE]
The problem is not only to the one that is rooted and flashed but also happens to the 2 at verizon that i inspected (brand new out of the box) and the 2nd one that i have that is also brand new with no mods
[/QUOTE]It might even be broken on the stock Froyo. All the people who said it's working fine for them right now are running custom ROMs, kernels, firmwares and all that jazz. Maybe it was fixed through one of these custom updates. I dunno.[/QUOTE]
I think that the kernel for this phone was just snatched and quickly edited (by samsung) from another product and this is one thing that they havent been able to fix and figure out, because the woman at samsung told me
(Ruby: As your phone has physical keypads, there is no light feature available for keys.
Visitor: the small row of buttons (4 to be exact) at the bottom of the phone should be back lit in low light situations, however they occasionally light up but only in moderately to brightly light rooms
Ruby: I am sorry, there is no feature available on your phone.
Visitor: im sorry but i can prove that this phone does have back lit keys
Ruby: I am sorry, your phone home key rows do not have light option)
but we all know that the button do actually have a lighting option and samsung is just trying to delete the function but isnt 100% successful..
I don't know what to say, they work properly for me. This includes when I was fully stock EE4, as well as now (deodexed, rooted ROM, PBJ kernel, voodoo enabled).
droid charge doesnt have backilights in the keys.. wth are you all talking about... no wait there they are! barely. what th! where did they go again?
Stock froyo from the factory... Daylight = button lights off; sensor covered (night) = button lights on.
Sent from my SCH-I510 using XDA App
so as many users are no doubt aware that samsung has left off a led for notifications i have been thinking of ways around it. i have tried the NoLED app and it works ok but im not crazy about it. I feel like there is a simpler way. Is it possible to just use the backlights on the hard keys at the bottom as a notification light when a user receives a text, gtalk, missed call, etc... ? Anyone have an idea of how difficult it would be or if this is even possible? Im thinking that maybe all 4 lights blink in some sort of pattern, or if it is all one light then i guess you just blink that for 10 seconds or something then let it sleep for 30 seconds maybe? thoughts? I'm, not familiar with android development so the task sounds awfully daunting to me.
Is it really that hard to post in the questions section? And I think it'd be a fantastic idea. A bit of a battery suck, but I'd be willing to give up some juice for a backlight notification system.
Sleek69 said:
Is it really that hard to post in the questions section? And I think it'd be a fantastic idea. A bit of a battery suck, but I'd be willing to give up some juice for a backlight notification system.
Click to expand...
Click to collapse
Well, while I did ask a question, it was about an app so I guess this could have been posted in either thread. Also, I wasn't so much asking for permission or advice for the app as I was hoping that someone with knowledge of the hardware might respond and let me know if my idea is even possible. Is the backlight on the hard keys all one light or could we individually illuminate just one key at a time?
I don't think it would be any worse on battery life than the NoLED application which actually turns your whole screen when you have a notification. There are battery saving options but I would think periodically blinking the backlight would be slightly better than turning on the whole screen, right?
it is possible, there were BLN (backlight notifications) on my Fascinate before I got my Charge... however its quite a bit of work to hack it into the kernel especially without official kernel source for GB yet (which is most likely where you'll get BLN is GB or CM7) and imo is pretty worthless since the lights are so dim
blazing through on my 4G Droid Charge
anoninja118 said:
it is possible, there were BLN (backlight notifications) on my Fascinate before I got my Charge... however its quite a bit of work to hack it into the kernel especially without official kernel source for GB yet (which is most likely where you'll get BLN is GB or CM7) and imo is pretty worthless since the lights are so dim
Click to expand...
Click to collapse
so are you saying that hacking it into the kernel is the only way to go about this? it's not an app that you could just run in the background? i do imagine that it's probably much better in the kernel though. I just checked the CM website and they dont support the charge yet, but I assume they will at some point. I do like the GummyCharged ROM that im running now though. Yes, the lights are dim but at least it's something. that's better than constantly having to turn the screen on to see if I have missed anything.
leaveone said:
so are you saying that hacking it into the kernel is the only way to go about this? it's not an app that you could just run in the background? i do imagine that it's probably much better in the kernel though. I just checked the CM website and they dont support the charge yet, but I assume they will at some point. I do like the GummyCharged ROM that im running now though. Yes, the lights are dim but at least it's something. that's better than constantly having to turn the screen on to see if I have missed anything.
Click to expand...
Click to collapse
yes it's only done through hacking kernel/rom scripts, and an awesome developer who goes by jt1134 is hard at work with our other awesome Charge devs to get CM7 going on our phones so hopefully soon
OK guess in having my first problems? Today my capacitate buttons at the bottom of the phone have just started going out on there own. Literally while I'm typing this they have come on and went out like 5 times now. Is anyone else experiencing anything like this? Weird cause up until now I have had zero problems with my phone. Maybe a sensor having glitches?
Are you typing in landscape mode?
Sent from my MB865 using XDA App
No portrait ...right now they won't even come on? Like they all of a sudden have a mind of their own LoL
have you tried covering the light sensor by the speaker grill? The button lights are brightness sensitive, so by covering the sensor, they should turn on. Otherwise, I would guess there might be a problem with your auto brightness or the sensor itself. When I first got this coming from a captivate, I was confused since the captivate turned them on when you touched the screen.
Sent from my MB865 using XDA App
Yep tried the light sensor and a battery pull as well. Now they won't even light up? Not like its a killer dealbreaker for me or nothing. Just weird they all of a sudden went crazy?
Now that you mention it I've been experiencing the same issue with my atrix2. Its like the buttons have a mind if their own.
Sent from my MB865 using xda premium
Yeah, mine come on when they want to. Right now they are off.
Sent from my mAtrix2!!
All moto phones do this. The software for the light sensor is just REALLY bad, so there is really nothing we can do about it, unless a dev wants to help us out.
Well it really just started doing this today. But after playing aroung with the display settings I'm thinking the light sensor is either going bad or is bad. When I set it to auto brightness it gets dimmer then the lowest manual setting in a completely dark room. Oh well, like I said not a killer deal for me. Just never had one fail quickly like this.
try turning off auto brightness and see if they still do it
svtfmook said:
try turning off auto brightness and see if they still do it
Click to expand...
Click to collapse
I never use auto brightness its always set at about the lowest brightness on manual. I've played with it back and forth and think the light sensor is just acting up.
Wow, I hope that's not a widespread issue.
My A2 doesn't have that problem. It's quite new but I think it's my 4th now (I've lost count of how many times I've seen a dead pixel on that otherwise gorgeous screen) and I do remember the capacitive buttons' backlight doing weird things on my other Atrix(es). I can't remember if that was on my OG Atrix, or if it was on one of my A2s in a car and the lighting kept changing, or if it was an actual problem.
But anyways, the light sensor works pretty well for me on my current A2. I usually have it on auto-brightness.
Mine work perfectly on manual or auto.