Related
I hate that notification because I use my phone for my alarm and it lights up in the middle of the night. Has anybody figured out a way to turn that notification off? I have looked and not found anything on the phone or in the forums.
If you can't find a way to suppress the notification, do what I do...turn the phone over. If you don't have the Body Glove case that lifts the screen off the furniture and are concerned about scratches, put it on a paper towel or similar item to protect it. I use a wash cloth.
would also like to know how to turn that stupid notification off - software based and not using a towel though
I don't know much yet but I was digging around in root explorer and if you go to /system/media there are a bunch of .qmg files for battery related stuff, and two of them are named chargingwarning.qmg and Disconnected.qmg. Could one of these be the file for the fully charged notification?
rockr09 said:
I don't know much yet but I was digging around in root explorer and if you go to /system/media there are a bunch of .qmg files for battery related stuff, and two of them are named chargingwarning.qmg and Disconnected.qmg. Could one of these be the file for the fully charged notification?
Click to expand...
Click to collapse
Probably not because the notifications are all text, and QMGs are the 3d files used at boot-up. Most likely those animations are used in the battery meter that is displayed when the phone is off (turn your phone off and plug it in).
This won't help with the light, but the sound can be fixed.
http://forum.xda-developers.com/showthread.php?t=737147
seriously? we are all STILL dealing with this? has anyone found a solution to prevent this notification from popping up?
GarciaM25 said:
seriously? we are all STILL dealing with this? has anyone found a solution to prevent this notification from popping up?
Click to expand...
Click to collapse
It is confirmed fix in the 2.2 release - at least the JI6 build we are all playing with. They moved it to the notification bar.
Bumpage!
Been a lurker but just recently got my Captivate. Great forum here! Looking forward to contribute as well.
Well my issue with the "Fully Charged" battery notification is the display will stay on for the entire night. When I wake up in the morning, I see the phone's display on with the notification. Is this normal? I think this was happening just recently but I can't remember. Shouldn't the display turn off after the set amount time of inactivity? Thanks.
Nevermind, I figured it out. Within the development settings, the option to never allow the phone to sleep while plugged into the usb was checked. I wonder why that was checked.
Sent from my SAMSUNG-SGH-I897 using XDA App
Ok, I THOUGH disabling that option would put the display to sleep when the notification comes on but it doesn't. =(
Is this normal behavior? The screen stays lit after the notification is on? The only reason why i'm concern is if I'm plugging it in night after night and it's on that particular screen for hours at a time, there might be some burn in issues.
dawei213 said:
Ok, I THOUGH disabling that option would put the display to sleep when the notification comes on but it doesn't. =(
Is this normal behavior? The screen stays lit after the notification is on? The only reason why i'm concern is if I'm plugging it in night after night and it's on that particular screen for hours at a time, there might be some burn in issues.
Click to expand...
Click to collapse
Not likely. It's not a rear projection tv or a CRT monitor. Burn-in problems died with those.
miztaken1312 said:
Not likely. It's not a rear projection tv or a CRT monitor. Burn-in problems died with those.
Click to expand...
Click to collapse
Guess you haven't seen some of the demo Captivate at your local AT&T stores. Seeing the burned in images on those beautiful SAMOLED screen just kills a little bit of me.
In any case, so it's normal for the screen to take on after the message notification comes on?
dawei213 said:
Guess you haven't seen some of the demo Captivate at your local AT&T stores. Seeing the burned in images on those beautiful SAMOLED screen just kills a little bit of me.
In any case, so it's normal for the screen to take on after the message notification comes on?
Click to expand...
Click to collapse
None of the models I saw had burn-in at all. I got my phone on August 30th of this year. The phone had been on the shelves since July. But I would imagine it's normal for the screen to come on.
I got my phone only three weeks ago, so the phone sitting on display has probably been there a long time. And yeah, samoled screen can get burned in. well guess I'll have to charge it during the day time for now until I can figure out a way to disable the pop up.
Oh my worry is that the screen might be in the on state with the same image for hours while I sleep. That's something I can't leave to chance.
Sent from my SAMSUNG-SGH-I897 using XDA App
dawei213 said:
I got my phone only three weeks ago, so the phone sitting on display has probably been there a long time. And yeah, samoled screen can get burned in. well guess I'll have to charge it during the day time for now until I can figure out a way to disable the pop up.
Oh my worry is that the screen might be in the on state with the same image for hours while I sleep. That's something I can't leave to chance.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
As long as you're not using a Samsung Dock or have the Stay Awake option checked off in settings, it won't stay on. I watch my phone every night. It usually finishes charging long before I ever go to sleep (case in point, it's 3:11am, and the phone was done around 1am) and the screen always times out and turns itself off. It doesn't come back on either.
miztaken1312 said:
As long as you're not using a Samsung Dock or have the Stay Awake option checked off in settings, it won't stay on. I watch my phone every night. It usually finishes charging long before I ever go to sleep (case in point, it's 3:11am, and the phone was done around 1am) and the screen always times out and turns itself off. It doesn't come back on either.
Click to expand...
Click to collapse
Ok, yeah that's what I figured. Thanks for confirming it for me. I do have that option "not checked". Something might be preventing it to fall back asleep.
Is there any log within the file system which might keep track of system events? I might have to do a little digging around.
Thanks for your input.
dawei213 said:
Ok, yeah that's what I figured. Thanks for confirming it for me. I do have that option "not checked". Something might be preventing it to fall back asleep.
Is there any log within the file system which might keep track of system events? I might have to do a little digging around.
Thanks for your input.
Click to expand...
Click to collapse
I don't believe there's any logs, but you might have some luck installing logcat from the market and checking that after one night
Sent from my Captivate
Charged notification PROBLEM SOLVED !
PROBLEM SOLVED ! NO COST !
I saw this suggestion in another forum and it WORKS, so I'm passing it on !
Set the global notifications to SILENT.
Set the notification on Gmail to any ringtone, NOT DEFAULT.
Set the notification on messaging to any ringtone, NOT DEFAULT.
You'll still have a tone when you 1st plug the phone in to the charger, but NO tone when it's fully charged.
Where are these settings? I can't find them any where.
My Shift is not shutting off the screen like it should while in a call. I am sure this is draining my battery quicker as well as being annoying when I hit mute, speaker, or hang up with my face. Any idea what my issue might be?
Phone is stock:
Android Version
2.3.3
HTC Sense Version
2.1
Home screen widgets and icons...
Sense Clock with weather
People, WiFi, Battery (HTC Widget), Voicemail
Messages, Market, Flashlight, Camera
laid out in that order from top to bottom, left to right. I have only one other widget on another screen for Player Pro. Running Lookout.
Download "proximity sensor finder" from the market.
And once opened you should see it say 9.0cm. cover your finger over the proximity sensor (little circle to the left of speaker grill) and that number should change to a 0...
if it doesnt you need to take your phone to sprint
I guess it is broken. I covered it and it did nothing. It messed up a few times where it would work a little, then come back on now the screen is on all the time. I have resorted to pushing the power button while in a call to turn the screen off. Does the same thing I guess but it really doesn't matter much. I think I am going to get the Photon soon.
Thanks for the tip on the app. I think I will use it in the future.
evilthx said:
I guess it is broken. I covered it and it did nothing. It messed up a few times where it would work a little, then come back on now the screen is on all the time. I have resorted to pushing the power button while in a call to turn the screen off. Does the same thing I guess but it really doesn't matter much. I think I am going to get the Photon soon.
Thanks for the tip on the app. I think I will use it in the future.
Click to expand...
Click to collapse
No problem,
Although since that is just a defect that came with the phone, Sprint will replace that for free, without any problems.
(and tell/show them the apps responses if they do, they cant deny proof )
Just make sure you run the RUU beforehand if you do take it in and your rooted (but you said your on stock 2.3 so im assuming your not anyway)
Nope, all stock... I will look into returning it... it is a good phone and wouldn't mind it as a back-up phone.
Bump...
I still have my EVO Shift and the day before yesterday I did something to my phone to try and fix my led issue. It wasn't a major problem with it but something was obstructing the led making it hard to see when I got notifications. Well It started by me using a fine bristled brush to clean the little mesh earpiece screen with to clean over the led... it started to work and then made it worse. I then decided to just remove the mesh screen. I pried it out as gently as I could which made it easy to clean the obstruction from the led but as a very welcome side affect it also fixed my proximity sensor!!! The phone now functions fully again. So to all those willing to try it if your sensor is "broken" try removing the metal mesh part of the earpiece... just be very careful.
sooo, yeah. my wife has the t959v. the screen cracked months ago, replaced it with one from ebay, works fine. a few weeks ago, it was involved in an accident and needed yet another screen replacement; ergo, back to ebay i go. installed the new screen yesterday, turn it on, all is well. for a bit.
now, the phone isn't currently, nor has it ever been rooted; pure stock tmo us 2.3.6. during boot, the splash screens and boot animation are gorgeous and perfect in appearance. the recovery menu is exactly as expected. android boots as you'd want it to, and then the display will do one of the following:
-work properly (rare)
-automatically turn off, capacitive buttons still lit, touchscreen unresponsive - turning it "off" darkens the cap buttons, turning it back on flashes the screen on for a half-second, then off, with cap buttons still lit (common)
-graphical corruption ("solarized" colors, completely wrong colors, pixel vomit in essence) (fairly common)
-screen tinting, blue most often, followed by pale yellow, then greenish, then red (almost constant)
-screen inversion - the display will show as rotated 180 degrees; grabbing a framecap in ddms shows it right way up. touches are also inverse; you have to touch where the onscreen element would be if it were displayed properly instead of where the element is; e.g. a button on lower-left will display in the upper right, upsidedown, but the screen registers the button when you touch the lower-left portion of the screen. (quasi common, equally infuriating and hilarious)
none of these problems will show up in a screenshot at all.
i can reliably reproduce any of the above by simply adjusting the screen brightness. this will, quite literally, cycle through every possible defective display mode randomly for a split-second before moving on to a different one as long as you move the brightness slider.
MOST of these issues are transient and are either fixed (temporarily) or replaced with a different listed issue if you lock/unlock the display. it feels like a hardware issue what with the solarizing and color horrors, but is acting like a software issue, considering that recovery and boot are perfect and have never displayed any of these issues. i tried gently flexing and stressing the case in areas that might be a weak connection point, but can't get it to bug out that way.
in no way am i suggesting that i didn't screw something royally in the reconstruction stage, but i tore down and rebuilt that phone 4 times with identical results, so i can guarantee it's not some loose ribbon connector or zif socket.
i beg of you, great minds of xda, what the balls did i muck up this time? any hope for a fix? are there different panels, drivers, something?
thanks in advance
OK, if your screenshots appear normal, then your phone appears to be working correctly!
or at least it thinks it is we can conclude that it isn't the rom, kernel, or anything that you can blame the phone for going screwy.
Try buying another screen??
The ribbon connector might be broken?
yeah, these were what i figured what my options were. it just seems odd that the boot process and recovery menus have error-free displays while only the full android os doesnt. oh well, i'll probably just have to make a stink about it on ebay or something.
thanks for reading
You might try a fresh flash before getting a new screen to see if it is indeed a hardware issue. If you want to try that follow the second link in my signature. You will not need to flash bootloaders since you are currently on KJ6.
lumin30 said:
You might try a fresh flash before getting a new screen to see if it is indeed a hardware issue. If you want to try that follow the second link in my signature. You will not need to flash bootloaders since you are currently on KJ6.
Click to expand...
Click to collapse
hell, warranty's void at this point anyway, right? may as well thanks much!
welp, all went well, screen was perfect through the whole heimdall/recovery process, but the problems still exist in the os c'est la vie. at least my wife's phone is finally rooted, i suppose. thanks anyway!
Have you tried opening it back up and reconnecting?
yup, 4 times, but i guess one more wont hurt
[edit]
it definitely seems to be related (if not related, exacerbated by) changes to screen brightness. turning off autobrightness has helped minimize the issue, but it still presents itself semi-often during screen-off/on events. obviously nothing useful in logcat.
zero01101 said:
it definitely seems to be related (if not related, exacerbated by) changes to screen brightness. turning off autobrightness has helped minimize the issue, but it still presents itself semi-often during screen-off/on events. obviously nothing useful in logcat.
Click to expand...
Click to collapse
That's interesting and could very well be a hardware problem with the screen. You wouldn't see that in recovery as the OS isn't loaded to mess with the brightness in that mode.
Does it do it on-demand if you mess with the brightness slider?
stephen_w said:
Does it do it on-demand if you mess with the brightness slider?
Click to expand...
Click to collapse
you better believe it does. rapid fire cycles through every color until it can't take it anymore and turns off. if i take/refresh a screenshot through ddms and poke blindly at the screen at that point, it'll still take input which is a curious, difficult game to say the least.
zero01101 said:
you better believe it does. rapid fire cycles through every color until it can't take it anymore and turns off. if i take/refresh a screenshot through ddms and poke blindly at the screen at that point, it'll still take input which is a curious, difficult game to say the least.
Click to expand...
Click to collapse
It's that Pink Floyd screen. You're supposed to drop acid & watch the wall when that's going on. LOL j/j
Given that you're on a fresh ROM & the problem persists, I'm leaning toward a hardware issue man. Sorry.
stephen_w said:
It's that Pink Floyd screen. You're supposed to drop acid & watch the wall when that's going on. LOL j/j
Given that you're on a fresh ROM & the problem persists, I'm leaning toward a hardware issue man. Sorry.
Click to expand...
Click to collapse
as fun as that sounds, unfortunately i bet i'll end up just getting my wife a used phone on ebay or somewhere similar and using this one as a development monkey. i was assuming that it wasn't something i could fix but hoping otherwise... yeah, that worked out
I just started having this problem. It wasn't too bad at first, just the color changes, but then it started not showing a screen at all. Changed to three different roms, even back to the stock non-rooted KJ6 and gave up. Keeping it on a steady brightness is the only way to minimize the color changing. I thought your thread had a solution but...
I may try opening it up and fixing the ribbon. But otherwise I'll keep using it as long as I can tolerate it until an S3 or a new Nexus.
kristoper said:
I just started having this problem. It wasn't too bad at first, just the color changes, but then it started not showing a screen at all. Changed to three different roms, even back to the stock non-rooted KJ6 and gave up. Keeping it on a steady brightness is the only way to minimize the color changing. I thought your thread had a solution but...
I may try opening it up and fixing the ribbon. But otherwise I'll keep using it as long as I can tolerate it until an S3 or a new Nexus.
Click to expand...
Click to collapse
nawp, nothing even close to a solution here i did end up buying my wife a whole new replacement phone and turned the broken one into my api10 development device. for what it's worth, yeah, autobrightness off does help a bit for when the phone is actively displaying content, but after you put it to sleep/screen off and try to turn it back on, it's a crapshoot. for a few horrifying hours, the screen was upsidedown even in recovery/boot animation and would NOT flip back to right-side-up until i ran the battery completely flat.
is no fun, 'tis truth. sorry for your troubles.
If I have my phone face down on a counter when it rings, when I pick it up the screen is black. Not off, as I see some light, but basically dark.
I cannot see who is calling...can't get it to display.
This actually happens a lot other times. Just now, for example, I just picked it up, and turned it on with finger print. I placed it face down, and picked back up immediately...screen black.
If I happen to have it on and brush the screen across my side, it will go black.
The ringing is the realy annoying one.
Any suggestions? I'm thinking it has to do with something about the proximity sensor sensing the screen against something...but it should let it come on when it's not against something.
Is noone else having this problem? Every time my phone rings, it turns on but stays black. I never know who's calling unless I answer.
I don't know what to do with it. Very annoying.
Hoping someone has a suggestion.
You could disable auto dimming on your phone. Use Lux from Play store instead.
Planet X said:
You could disable auto dimming on your phone. Use Lux from Play store instead.
Click to expand...
Click to collapse
Do you mean Auto Brightness? If so, that is not the problem. I have it disabled and am using an app for brightness control...not automatic.
I cannot find anything in settings about 'auto dimming'.
Thanks for the suggestion though...
You're right. I mean Auto Brightness, it does Auto Dimming too . B.t.w. I don't have this issue.
Planet X said:
You're right. I mean Auto Brightness, it does Auto Dimming too . B.t.w. I don't have this issue.
Click to expand...
Click to collapse
I'm beginning to think I am the only one.
Another symptom which I am thinking is related. Sometimes when I touch my finger to the fingerprint button to wake the phone, it comes on with that dark screen for just a moment. It feels like the phone is busy, overloaded, or just slow. It will then come fully on. Also seems like maybe it is just in deep sleep and slow to wake up. If I turn it off and back on, it is instant.
I check memory and it always has just under 1.5 GB free.
I don't know what to think, but it is very annoying. I thought about chalking Huawei support, but I'm sureo they'd just say to hard reset.
I do have a lot of apps on the phone, but with that much free memory I wouldn't think that should be a problem.
Another interesting thing related to screen dark: I can have the setting for display to not turn off if no actdivity to 10 minutes, and it still goes off after less than a minute. (Going off is different from the topic of this thread where it is near black/dark, but not off).
I discovered this while trying to use Huawei backup. Thinking of doing a Factory Reset. Instructions say to not lock the screen, so I'm trying to keep screen on w/o my having to hold the phone the entire backup.
This overall topic is making me pretty unhappy with the phone, which I had thought was perfection when I started with it.
sigh...
I finally called Huwaei technical support this morning. They apparently know about this problem, and want me to send the phone back for repair. They expect me to be without a phone for two weeks while this is going on.
It speaks to the reason to not buy phones away from carriers, as anytime I had a problem with my Samsung, they would send out a replacement and then I would send back my old one and I would not have to be without a phone.
Pretty poor .
AN update In case anyone is following this for some reason...
Getting ready to send the phone in, I did another factory reset. I had got to wondering if maybe Gravity Box had been part of my problem. May be the case...not sure. But for now i'm not having the problem. I changed some of the settings on it when I reinstalled. I cancelled the return.
I've had the odd time when the screen is on, but not properly backlit. You can just about make out the screen, but then the backlight seems to rectify itself. It isn't just the Mate 9, but the P10 and probably other phones. Doubtful a hardware issue I'd have thought - rather a software glitch.
The P10 just got an update earlier this week (yet still with April security patches) but my Mate 9 hasn't had an update in months.
Didn't see this posted here yet, but forgive me if I missed it.
Trying to find out if anyone has seen or heard of any acknowledgement from Google regarding this. My new Pixel 3 (Verizon; non XL) since day 1 has had an annoying issue with the screen flashing when ambient screen engages. I have my settings with alwayson set to off, and new notifications set to on. If the screen is asleep and I get a text or any notification, the ambient screen wakes and will initially make the entire screen flash white very quickly.
I do not get a flash of the screen in any other scenario when the phones on, it only seems to be when the screens totally asleep and the ambient screen wakes. I can unlock the phone or hit the power button to fully wake the phone to my home screen with no flashing. Its not every single time, but its very often. I do notice sometimes when it doesn't flash the whole screen, the time or text on the ambient display will be at full brightness when it first wakes for a split second and then will go to the dim text Im used to seeing.
Replaced the phone through Verizon. Got another brand new one with the same exact problem. This one even flashes on reboot occasionally just before the white "Google" screen pops up. Google had me send them a bug report this time and are supposed to be having their dev team look at it.
WHY.
Mine did it once
Sent from my Pixel 3 using Tapatalk
I've also now noticed mine will flash in Instagram when I "like" something lol. Just the picture flashes within the app itself in that case, not the whole screen. Such a weird thing, that may have something to do with the app on the new pixel? I don't even know anymore.
I just saw the white flash. It was only for a few ms but it looked like a full brightness white flash on the whole screen. I had just set my phone down and I think the AOD was coming on.
Weird.
Yeah I have a feeling this is happening on way more devices than we're reading about. I hope it's addressed. Sometimes my notification audio cuts out real quick too. Hoping it's just all memory related.
I have this weird kind of screen flickering on my device as soon as I use the fingerprint area to turn the phone on. It is very faint and fast but its like static lines for half a second when the screen comes on??
Archangel said:
I have this weird kind of screen flickering on my device as soon as I use the fingerprint area to turn the phone on. It is very faint and fast but its like static lines for half a second when the screen comes on??
Click to expand...
Click to collapse
Strange, I haven't had any issues like that using the fingerprint reader or just hitting the power button. Mine are all directly related to ambient screen waking.
My Pixel 3 is doing the same thing when I unlock it. Flashes like taking a selfie... I have even looked for the selfie to no avail.
It does not do this regularly, very random.
edster00 said:
My Pixel 3 is doing the same thing when I unlock it. Flashes like taking a selfie... I have even looked for the selfie to no avail.
It does not do this regularly, very random.
Click to expand...
Click to collapse
Same here. Sometimes when I tap the screen to wake it up, it flashes. Just did it a minute ago before I wrote this.
Sent from my Pixel 3 using Tapatalk
I just charged the Pixel face down; during the charge I picked it up to check the progress and I got the screen flash ~2X out of 10.
edster00 said:
I just charged the Pixel face down; during the charge I picked it up to check the progress and I got the screen flash ~2X out of 10.
Click to expand...
Click to collapse
Report it to Google. I feel like it's something they're aware of (I hope) but support certainly isn't saying so if they are.
I saw a post on Android Police about bug trackers and read in some of the comments that people were having problem with screen flashing. Some of them said it was related to the always on display. Mine was flashing like white static lines. But it was only for half a second when you turn on the screen and it didnt happen every time, it was random. I turned off the AOD and it never happened again. Kinda sucks cause I like AOD. But that tells me it is a software problems and not hardware.
I turned off AOD too, for 1 day; the next day I turned AOD back on. I have not had a screen flash since (a few days now).
edster00 said:
I turned off AOD too, for 1 day; the next day I turned AOD back on. I have not had a screen flash since (a few days now).
Click to expand...
Click to collapse
Try rebooting. I bet it's still happening you just may not be noticing. I've had my AOD off for a while and as soon as I turn the new notifications option it comes back. Not every time but still often.
I'm having the same issue, doesn't happen all the time but I can reproduce it usually by unlocking the device, locking it then when ambient display comes on, unlock it and the screen flashes/flickers. I've only managed to do it with ambient screen set to always on.
I've RMA'd this morning so I'll report back when the new phone comes.
I hope you RMA's for other reasons too because it is likely that you will get a phone with the same flickering problem. I think it is a software issue esp since it goes away after we turn off AOD.
steslatt said:
I'm having the same issue, doesn't happen all the time but I can reproduce it usually by unlocking the device, locking it then when ambient display comes on, unlock it and the screen flashes/flickers. I've only managed to do it with ambient screen set to always on.
I've RMA'd this morning so I'll report back when the new phone comes.
Click to expand...
Click to collapse
Archangel said:
I hope you RMA's for other reasons too because it is likely that you will get a phone with the same flickering problem. I think it is a software issue esp since it goes away after we turn off AOD.
Click to expand...
Click to collapse
I just find it strange that people are having the flicker in different scenarios, like mine is only when ambient is set to always on but other people are having the issue when it's set to double tap etc. Anyway I guess I'll see when the new phone comes.
Sent from my Pixel 3 using Tapatalk
Yeah let us know please once you get the new phone. It seems like it is hit or miss with people so you might get lucky and avoid it.
steslatt said:
I just find it strange that people are having the flicker in different scenarios, like mine is only when ambient is set to always on but other people are having the issue when it's set to double tap etc. Anyway I guess I'll see when the new phone comes.
Sent from my Pixel 3 using Tapatalk
Click to expand...
Click to collapse
Quick update. My new phone arrived this morning and I've managed to get the screen to flash once so far where as my old one would do it 8 times out of 10. I feel like this is a poor display hardware problem rather than software.
I believe or rather am hoping that because it only happens when you turn on AOD that it is a software issue and not a hardware one. The only way something will be done is enough people complain on a bug tracker.
steslatt said:
Quick update. My new phone arrived this morning and I've managed to get the screen to flash once so far where as my old one would do it 8 times out of 10. I feel like this is a poor display hardware problem rather than software.
Click to expand...
Click to collapse