Related
Just got 2 new EVOs a few days back, and I noticed my backlight pulsing. It will just barely dim in what seems a constant cycle, approx every 5 seconds. It's not a lot, but when constantly looking at the screen, like during a game or something, it's quite annoying. It's not noticeable on something dark (duh) or something that is constantly distracting (movies), put playing a word game or something, it's definitely noticeable (and did I say annoying?).
I thought maybe it was my phone until the wife asked me if mine did it. D'oh, can't imagine that both of ours doing it is a fluke. So wondering if anyone else knows why it's doing that.
At first I was thinking it was a slight reminder that I had a status message or something... so cleared all those and still doing it. I've got it set on automatic light sensing and will change it to manual today to see if it still does it. Maybe the light sensor is to sensitive (wouldn't explain the steady pulsing though, would expect that to be more random). I did test them both in the same environment, lighting, etc. In light and in pitch dark, with a static image on the screen (as to not have the EVO itself causing the light sensor detect light change).
Possibly it's signalling something else, but I can't think of what (batteries were charged).
Wondered if anyone else has noticed this, and like me thought maybe it was just their phone. Again, it's not a DRASTIC change, but enough to be ... yes. . ANNOYING lol
Mine does this too. Maybe not every 5 seconds but it does do it consistently. It distracts me every once in awhile as I think I just got a text.
Post what hardware version you have. If both of you guys have 003 it may be another thing to that revisions list of errors for them to correct.
It may be the auto brightness setting. Someone mentioned it in another thread. My auto brightness is turned on.
I think it is the Auto Brightness setting. It was on mine at least. Turned it off and the pulsing went away.
Yeah, turn off the autobrightness, it was doing the same thing for me and turning it off and then adjusting to a good level, and now its fixed.
fixed? eh
I wouldn't say disabling auto brightness fixes it. I actually like the feature, and was one of the features I actually liked on my iPhone.
And yes, it is hardware version 0003. I'll look for a thread on the 0003 hardware issues, unless someone links my to it first. Thanks
I just updated to DK28 using the update.zip over stock software (no root) and on top of various new features and new bugs, I've noticed a strange new behavior.
At least several times per hour, my phone will give a quick vibration pulse, then maybe a second or two later will give two (or sometimes three) real quick pulses. I have no idea why it's doing this and whether it means something or not. Anyone know?
I can't seem to correlate the behavior to anything in particular the phone is doing at the time. It happens with the phone sleeping, and it does it while I'm using it. It happens when I'm on the home screen, when I'm reading web articles, when I'm playing with other apps, when it's on the charger, when it's off...
pilby said:
I just updated to DK28 using the update.zip over stock software (no root) and on top of various new features and new bugs, I've noticed a strange new behavior.
At least several times per hour, my phone will give a quick vibration pulse, then maybe a second or two later will give two (or sometimes three) real quick pulses. I have no idea why it's doing this and whether it means something or not. Anyone know?
I can't seem to correlate the behavior to anything in particular the phone is doing at the time. It happens with the phone sleeping, and it does it while I'm using it. It happens when I'm on the home screen, when I'm reading web articles, when I'm playing with other apps, when it's on the charger, when it's off...
Click to expand...
Click to collapse
I got that too, plus lag and other bugs when first went to 2.2 (rooted 2.1 and used update.zip). Did you wipe when you updated? I didn't so it was acting weird... Plus the GPS didn't work so I did the Odin thing and now it works fantastic.
Did you wipe when you updated?
Click to expand...
Click to collapse
No. I probably should.
I just wondered whether these little vibration pulses were meant to indicate something, or whether they're just a bug.
happens when an app crashes
My vibration was related to turning on the WIFI became very unstable. The DK28 I had came with clockwork mod so I did a recovery to Epic Experence 2.0.7 chosing the recover form a specific zip file I had copied to my SDcard. Fixed the vibration problem and my USB connection then agin worked on my Windows 7 laptop
So my Incredible just recently and randomly started to make a clicking noise. It happens when the screen is on at 1 second intervals and for a while after the screen is turned off as well. It's not a software sound but a sound from inside the phone. Its an amoled version running CM7 and other various customizations. I was wondering if anybody has ever had this happen and if it is something I should be worried about? Also, I'd like to know the cause and how I can stop it from happening.
Does your phone still vibrate? If it doesn't it might be the mechanism inside.
Sent from my sexy assistant. (AMOLED HTC Incredible)
It does vibrate as normal. Everything works just as before but I'm curious to know what it could be.
PitaBlackZ said:
It does vibrate as normal. Everything works just as before but I'm curious to know what it could be.
Click to expand...
Click to collapse
has it ever gotten wet? maybe something fell inside the the phone and is now shorting it. do you have insurance?
maybe take it apart and see if there is anything floating around.
No, its never gotten wet. It doesn't sound like something is rattling inside. I could be wrong but I think its got something to do with overclocking it. When I turn on the screen it instantly starts clicking sometimes fast but moslty at 1 second intervals. When I shut the screen off it usually stops instantly. Sometimes it clicks for a short while afterwards. The sound is like a clock ticking. Unfortunately I don't have insurance.
PitaBlackZ said:
No, its never gotten wet. It doesn't sound like something is rattling inside. I could be wrong but I think its got something to do with overclocking it. When I turn on the screen it instantly starts clicking sometimes fast but moslty at 1 second intervals. When I shut the screen off it usually stops instantly. Sometimes it clicks for a short while afterwards. The sound is like a clock ticking. Unfortunately I don't have insurance.
Click to expand...
Click to collapse
I had a computer that did that exact same thing. Windoze machine, actually. Some BS process was running in the background that kept doing something that used that sound effect. Is it like the sound used when you have audio feed back turn on for the keyboard? I definitely think it's a software issue, not hardware, so it's probably fixable in some way.
Is it the same clicking noise like when you open up an app that uses your camera? I know whenever I open up the camera, bar code scanner, etc I hear a clicking noise. Not sure if some app keeps trying to access the camera and maybe that is where it is coming from?
I bet its the camera being used for some background app.
Is it the same quiet click from the camera you hear when the phone boots up?
The clicking stopped yesterday just as randomly as it started. It didn't sound like the sound the camera makes when started. It actually sounded like a clock ticking. Its very odd.
I had that happen on my evo. Soneone mentioned that it was an app that was bugging and it was causing the touch panel in the lcd to think it was being touched. But android wasn't handling it properly so it caused a ticking noise to come from my speaker. I just wiped and reinstalled my rom and it went away.
Sent from my Recharged EVO.
Interesting. The sound didn't seem to come from the speaker in my Incredible but I can't be 100% sure. I haven't uninstalled any apps nor did I download any new ones before the sound started. Very strange stuff lol. Althought its since stopped, I'd still like to know what it was. I'm sure it was an app but.I don't have a clue as to which one.
as long as its not damaging the phone its fine
The phone seems to be perfectly fine thankfully. Guess I'll never know what it was. Oh well... thanks to everyone for the input.
Being an ex-Galaxy S1 and Galaxy S2 owner I was happy to finally have a notification LED on my phone. However I have found that the behaviour of the LED just isn't reliable.
When I got it a week ago it worked, then it stopped working for no reason, then it worked again, then stopped, now it works sometimes but most it just doesn't. I find the behaviour to be quite erratic and difficult to diagnose.
I tried using both the stock LED code and LightFlow (exclusively and at the same time) but both exhibit the same erratic sometimes-works-sometimes-doesn't behaviour. Totally unreliable.
This has happened with my original 4.1.1 ROM (stock, unrooted), then 4.1.1 rooted, then 4.1.2 stock unrooted and now I'm on stock 4.1.2 rooted. No different. Sometimes it works, most times it doesn't.
Is your Note II notification LED reliable? Searching got me some threads on LED trouble (both for SGS3 and Note2), but no conclusive reasons/solutions.
PS: I checked the LED with the factory test code and it works perfectly there - it does not appear to be a hardware issue at all.
It works for me all time. Very reliable I'd say. And I'm a person who hates any sort of non working things. Like Smart Alert, which has literally stopped working for me. And like you, it works each time perfectly on test mode.
PS: I switched to LED Light Manager last week, but that doesn't mean the stock LED didn't work.
Swyped from my GT-N7100
My native LED works fine but it's pretty limited. Better than nothing. I like Lightflow the best but it interferes with/invokes the Note II Accessibility functions so I removed it until they are worked out. Light Manager seems to work but the only thing I don't like about it, that Lightflow has, is the ability to flash network status when you have good signal (i.e. green flashing LED when you have signal; Lightflow does but LM does not have this function).
Ideally I just want an LED manager to mimic Blackberry, flashing green in standby mode, and flashing red when "something comes in". I have no need for 18,000,000 color combos.
Cheers
I haven't had any issues with my LED notification light. It has always worked for me. I don't use any apps though. The most I do is go into an app and select the color I want the LED to flash. But that's already built into the app. But they stay on while my screen is off. If it's flashing, and I turn on my screen, then I believe they disappear. But to be honest, if it flashes and I turn on my phone, I usually check the messages, reply to them, or clear them / swipe them away.
So despite all the problem threads I found, 3 users with no issues at all, interesting.
I can understand that as for the first days the LED behaviour was accurate, but since then it has been quite randomish and I have been unable to find a pattern. Somtimes I have a missing call and have the LED blinking, sometimes I have a missing call and nothing happens. There is no easy difference between the two situations.
I will try LED Light Manager, never used it and one more shot won't hurt. Meanwhile I was starting to think that the LED unreliability was the reason why 99.9% of all Galaxy Note II covers designers don't bother to add a LED cutout. :laugh:
Mine has been reliable so far.
The notification LED on my Note II has been very reliable, unlike on a past HTC phone where the light would either not blink or would not stop blinking.
All of my led are working fine
n7100
omega rom v10 perseus kernel 31
hit thanks its free anyway
It's working properly on my N7100 also.
No problems at all.
Now for the solution:-
1.You can try reflashing a rom (stock or custom)
2. Install ths.
https://play.google.com/store/apps/details?id=com.koo.lightmanager&feature=search_result
This should override the stock LED functions and may improve it's performance.
No issues what so ever with the LED, I've never used custom roms/kernels on my phone though.
I'm even more puzzled than before now, as I cannot find a reason for the erratic behaviour on my phone.
Did you read my post and try my method?
zeeshanonlyme said:
Did you read my post and try my method?
Click to expand...
Click to collapse
Yes, I already had Light Manager. I also have LightFlow, but first started using teh samsung notifications only.
I find the same pattern in them all... sometimes teh notifications trigger/clean properly, some times they don't. Usually they don't.
I tried several combinations, Samsung LED app only, Lightflow off, Light Manager off, etc. And the same remains. The behaviour is erratic. Seen other users complaining about this in other foruns, but since it seems tricky to reproduce, no solution is clear.
I'l on 4.1.2 stock (bot rooted now) and besides de rooting my phone has almost no customization at all. Going for a full wipe/reset seems overkill, as it appeared to have done nother with other users.
Still trying to find out if this is a documented bug or just something specific to certain OS/apps.
I've noticed with Facebook messenger that if I get a message right as the screen goes dark and messenger was the last program on the screen, the LED will not light up. The phone must think I already checked it in that case. Other then that, it works as it should.
Mine works aswell
Mine never fails to notify me of events, but sometimes it lights dimly with no reason.
I'am still wondering why ...
Beowulf_pt said:
Being an ex-Galaxy S1 and Galaxy S2 owner I was happy to finally have a notification LED on my phone. However I have found that the behaviour of the LED just isn't reliable.
When I got it a week ago it worked, then it stopped working for no reason, then it worked again, then stopped, now it works sometimes but most it just doesn't. I find the behaviour to be quite erratic and difficult to diagnose.
I tried using both the stock LED code and LightFlow (exclusively and at the same time) but both exhibit the same erratic sometimes-works-sometimes-doesn't behaviour. Totally unreliable.
This has happened with my original 4.1.1 ROM (stock, unrooted), then 4.1.1 rooted, then 4.1.2 stock unrooted and now I'm on stock 4.1.2 rooted. No different. Sometimes it works, most times it doesn't.
Is your Note II notification LED reliable? Searching got me some threads on LED trouble (both for SGS3 and Note2), but no conclusive reasons/solutions.
PS: I checked the LED with the factory test code and it works perfectly there - it does not appear to be a hardware issue at all.
Click to expand...
Click to collapse
I have only problem while charging some times the LED color be light orange and some times be dark orange or red I don´t know why?
moulip said:
Mine never fails to notify me of events, but sometimes it lights dimly with no reason.
I'am still wondering why ...
Click to expand...
Click to collapse
The LED's glow bright if the ambient lighting is powerful, like in Sunlight or in a well lit room, and it'll be on the darker (dimmer) side when the ambient lighting is dark, like in a dark or low lit room.
Swyped from my GT-N7100
After about 3 weeks with the Note 2 I am still puzzled by the LED. I have days when it works perfectly (like you guys are reporting) but others when it just stops triggering and so far I found no pattern. Some code related to it must be really flaky. But when it works, it usually works fine...
All your LED are belong to us
I have a weird issue with my A2 Lite.
I tried couple of ROMs so far and it's all the same.
When I receive a call and answer it, I bring the phone to my ear and I can see that display goes off - that's good. But, despite keeping the phone close to my ear, the flash light turns on, bt or even airplane mode so it disconnects the call, it changes the screen brightness or mutes the mic during the call. It's like touch sensor was alway on with display off, so I can't even see what I'm touching and switching.
I even went back to stock MIUI to be able to run system check with *#*#64...etc. and proximity sensor works fine.
My problem is similiar to this one: https://forum.xda-developers.com/mi-a2-lite/help/lockscreen-notification-sound-proximity-t3867872.
This drives me crazy!!!
Did anyone have this problem or knows some tricks to fix it (beside smashing the sh..t on the wall)?
I experience the same thing sometimes with stock rom
keyone72 said:
I experience the same thing sometimes with stock rom
Click to expand...
Click to collapse
That - I didn't expect...
But it has to do something with the Android or kernel maybe. How does it come, that screen is being turned off but not locked (meaning insensitive for touches)?
Weird...
And I'm almost sure, it wasn't like this before... before I installed one of custom ROMs (Arrow maybe). But since then I even went back to stock Pie, so if any firmware/kernel manipulation caused it, with stock - it should've fixed.
I'm starting to dislike daisies...