Related
When I have my transformer docked the screen will not stay off after closing the lid. Initially it will turn off, but after a few seconds it will come back on. It seems as though something is waking the device. I have tried a few different settings, and trying it with the charger plugged in, and also unplugged. Anybody else have this problem, and more importantly, anyone have a solution?
mattsolberg said:
When I have my transformer docked the screen will not stay off after closing the lid. Initially it will turn off, but after a few seconds it will come back on. It seems as though something is waking the device. I have tried a few different settings, and trying it with the charger plugged in, and also unplugged. Anybody else have this problem, and more importantly, anyone have a solution?
Click to expand...
Click to collapse
check your time-out settings for screen and lock?
I have it set to time out after 10 minutes but my understanding was the screen should automatically shutoff and stay off when docked and closed. Am I wrong? Could it be a kernel issue? I'm using the Clemsyn kernel. OC'd to 1.4
mattsolberg said:
I have it set to time out after 10 minutes but my understanding was the screen should automatically shutoff and stay off when docked and closed. Am I wrong? Could it be a kernel issue? I'm using the Clemsyn kernel. OC'd to 1.4
Click to expand...
Click to collapse
In Applications -> Development. Is the option that says "Stay on when charging" turned on? That'll explain why. Since the dock is technically charging the tablet.
frosty5689 said:
In Applications -> Development. Is the option that says "Stay on when charging" turned on? That'll explain why. Since the dock is technically charging the tablet.
Click to expand...
Click to collapse
I was excited for a minute, hoped that might be it. But no, I don't have that option enabled. You're using the Netformer kernel? Maybe I will try flashing that. At worst it could rule out the kernel causing the problem.
mattsolberg said:
When I have my transformer docked the screen will not stay off after closing the lid. Initially it will turn off, but after a few seconds it will come back on. It seems as though something is waking the device. I have tried a few different settings, and trying it with the charger plugged in, and also unplugged. Anybody else have this problem, and more importantly, anyone have a solution?
Click to expand...
Click to collapse
Check your tablet is properly docked?
The magnet under the "+=" key on the dock will turn off the screen on the tablet ONLY when the tablet is properly docked. When the tablet is loosly docked (hard to describe but has happened to me) the magnet will have no effect on the tablet screen dimming. For example, if you disconnect the tablet and dock and place a magnet over the tablet (same area above "+=" on keyboard) nothing happens.
All sorts of dock issues happen to me when I force stop services or delete data related to dock services. Nothing has recovered the dock for me, except a complete factory reset. For example, I force stopped and deleted data on three services related to android & asus keyboard and the top row of keys no longer functioned until factory reset (e.g. wireless, bluetooth, pad disable, etc. through settings key and some audio controls). This might be a related issue if you are not on stock OS/ROM.
Good luck!
my tablet is docked properly but is still got the issue that the screen turns on even when the lid is closed .. it turns off first but recovers a few seconds later ..
Mine is exactly the same--the stay awake option is not checked, the tablet is docked correctly (slider is all the way to the right), and the tablet comes on while docked and charging. However, it does charge. I haven't timed it to see how long it takes vs undocked, or docked being used. I'm running unrooted, latest updates.
Bob Smith42 said:
Check your tablet is properly docked?
The magnet under the "+=" key on the dock will turn off the screen on the tablet ONLY when the tablet is properly docked. When the tablet is loosly docked (hard to describe but has happened to me) the magnet will have no effect on the tablet screen dimming. For example, if you disconnect the tablet and dock and place a magnet over the tablet (same area above "+=" on keyboard) nothing happens.
All sorts of dock issues happen to me when I force stop services or delete data related to dock services. Nothing has recovered the dock for me, except a complete factory reset. For example, I force stopped and deleted data on three services related to android & asus keyboard and the top row of keys no longer functioned until factory reset (e.g. wireless, bluetooth, pad disable, etc. through settings key and some audio controls). This might be a related issue if you are not on stock OS/ROM.
Good luck!
Click to expand...
Click to collapse
It was exactly what happened to me! Check if the dock button go until the end. This is made by docking well, not forcing the button. After that the screen went off has supposed.
Good luck.
no .. ich checked it twice .. i can't push it harder to dock it .. the switch is all the way to the right.
Is there any known app that can handle the switching forced by opening and closing the lid ?
I think this happened to me one time and caused a huge scare.
I had been shutting the lid of the TF and putting it in it's case...and having no problems.
But one time I did that, and it came back on and got VERY HOT and ran the battery to 0%!
I got lucky and just recharged it, but now, I shut it off everytime I'm going to put it in the case...you can't trust the shut-off-feature.
Got the exact same issue, screen is initially turning off but when you fully close the lid it turns on. It's got something to do with the touchpad (for me at least), because I've got no problems at all when you turn the touchpad off!
Can you guys try this too? Just turn the touchpad off and see wether the screen will turn on or not. Might get us closer to a fix.
Gibeon said:
Got the exact same issue, screen is initially turning off but when you fully close the lid it turns on. It's got something to do with the touchpad (for me at least), because I've got no problems at all when you turn the touchpad off!
Can you guys try this too? Just turn the touchpad off and see wether the screen will turn on or not. Might get us closer to a fix.
Click to expand...
Click to collapse
Same for me, i also had the feeling that it depends on the touchpad because when you reopen it you can see the cursor somewhere on the screen. Will try it later when i'm at home! Maybe we have to use something like a script to deactivate the touchpad when closing the lid.
greetings
Awesome ! this seems to work (tested it several times now).. i think there might be a way to react to the intents fired by closing and opening the lid so we can use them to turn off the touchpad.. ill check it out later but im not that experienced in android so maybe someone wants to help
EDIT: There is a status change in LogCat made by the WindowManager. Its called notifyLidSwitchChanged but there is nothing in the log while enabling or disabling the touchpad...
Maybe this related to problem?
I killed a few application services and deleted their data, while in settings. Afterwards my dock was not working correctly, e.g. keys were disabled and other strange effects.
I copied the 3.1 update from the web to flash and re-updated but this did *not* fix the problem. Next I did a factory reset and this solved my dock problems.
Maybe your tablet is missing some ASUS control bits for the dock? If you can afford a factory reset it might help. Good luck.
I'll try, I'm rooted so I'll just nandroid and revert to stock 3.1. I'm glad the touchpad "fixes" it atleast, means we all have the same issue.
Fixed
Thanks for posting this question as I thought I was the only one experiencing this issue.
The fix for me was found when Gibeon mentioned the touch pad. Once I read that I realized that the cursor was always displayed when I would open the case. Not sure of the reason. All I have to do is turn the touch pad off and it works fine.
I will try a factory reset/data wipe when I am ready but for now this works fine for me. Perhaps there is a away to fix this in the kernel (I have used both clemsyn/blades and netformer and had the issue with both) Thanks for the info!
I made a thread about this too a few days ago, I still have this problem and it drains my dock battery in only 3-4 hours. (and that's WITHOUT using the TF at all for those 3-4 hours)
Tested on mine and it is definitely the touch pad. Thanks for the help everyone. At least we've got a work around to use until a more permanent fix is achieved.
Would tasker be able to automatically shut down touch pad when screen is closed?
Sent from my GT-I9000 using XDA App
My screen randomly turns on and sits at the lock screen for a few seconds for no apparent reason. There are no pending notifications, etc. I assume there might be a rogue app causing this, but I don't have that many installed and even less apps doing any background tasks. Any idea on how to find the culprit?
I found this bug report where some apps are mentioned, but I'm not running any of them.
https://code.google.com/p/android/issues/detail?id=39625
On the Galaxy Nexus this issue was sometimes caused by a flaw in the micro-USB connector. I sincerely hope that is not the case with the Nexus 4.
I noticed that the phone wakes up whenever it reconnects to Wi-Fi. I was changing some router settings last night and I constantly saw the phone waking up shortly after the router rebooted. However, this is not the only scenario where it does it.
Mine has done the same, no idea why, only seen it the once, but it certainly happened, sitting three feet away from me, and suddenly Bingo! its on.
Mine wakes every few minutes. Certain apps (tasker, facebook etc) and syncing seem to cause it to happen more often but even if I disable most apps it still happens. I've been unable to identify the source with better battery stats. It happens bone stock and on CM10.1. I'm still getting better battery life than my GNexus but it's maddening.
Mine too. It will do it a few times in succession then be still for a while before starting again. No apps open and google sync off.
ludovicien said:
Mine too. It will do it a few times in succession then be still for a while before starting again. No apps open and google sync off.
Click to expand...
Click to collapse
So my Nexus 4 doesn't want to go to sleep.
- I have sleep set to 15 seconds
- Dream is off (just in case)
It just stays on. It doesn't matter if it's on the the lock screen or at the home screen. I'm guessing some app is keeping it awake. It just started last night, but I don't think I have installed any new apps. Maybe it from an update.
solved
My phone's screen also used to wake up randomly. it was very annoying, especially at midnight
finally, I found out the reason by using "Wakelock detector" app which is freely available in market.
here is XDA thread about WLD: WLD at XDA Thread
the cause of problem was ad Notification, it was holding "full wakelock" (you can see it in screenshot)
good Luck!
Refer Wakelock Detector at XDA
Ramdom screen wake up issue solved
Dear all,
I was experiencing random screen wake issue in my XOLO PLAY smartphone.
The problem was with the AppLock software. After upate is this issue appreard. Earlier AppLock was there and no issue was experienced.
I am writing to AppLock team to fix the bug.
:angel:
All the best
Regards
nitin5062
hcedillo said:
On the Galaxy Nexus this issue was sometimes caused by a flaw in the micro-USB connector. I sincerely hope that is not the case with the Nexus 4.
Click to expand...
Click to collapse
U made an account to post THIS only?
Been using NC with CM7 for over a year plus. Never any problems - until today. I haven't messed with any base settings for at least three months. The Nuance Swype and Dragon Trial app ran out today - the only thing that I messed with.
Was using it this afternoon on Google+ just cruising around. I put the NC down for about 20 minutes for an errand. Came back and I can't wake it up through the usual press of the "N". Long Press the N - no luck. Tap the Power button - no help. The only thing I could think to do was press and hold the Power button - nothing happened. Long press Power for about 15 seconds and I saw the screen flicker and the Cyanogen Mod green icon appear - like a normal start up. So the desktop arrives and I note that the Wi-Fi is turned off. Usually I have it set to autoconnect to my house router which it has faithfully done since forever. But Wi-Fi is turned off. I clicked it on and after a brief moment I see "Connecting..." up at the top of Wi-Fi Settings but every Access Point including the house router is "Not in Range". Eventually "Connecting..." turns into "Disconnected". Turn Wi-Fi off and then back on. No difference. I think that whatever caused the blowout earlier this afternoon has left the NC wi-fi system in some sort of in-between state.
Later on as I was working with this, I got up to answer the phone, came back and it's shut off again. I was able to re-engage it twice more after pressing this n' that trying to wake the Wi-Fi up. Once engaged it's fine. But as soon as you power down (or it blows up like earlier), Wi-Fi is disonnected, turned off and very hard to re-establish. Incidentally, all other Android devices, tablet, phones in the house off that router work just fine so I don't think it's a matter of a router issue.
Question: Is there a way to "reset" the Wi-Fi functions in the NC? I'm thinking some sort of hard reset is needed but I'm not sure.
Question: What would be my next step to figure out what is causing the unwanted shut down?
Thanks folks. If you need more info, I'm going to be around and will stay on top of this thread.
Hoibb
First that 'unwanted shutdown' is called SOD, Screen of Death. Very common with some devices and combination of apps. Do a little searching on that and you will get overwhelmed with info. Since you were not having it before, it must have something to do with that app or apps that you had to adjust recently. It is tied in with deep sleep and wifi.
Have you tried just forgetting the routers in your wifi list?
Edit: I just reread your post. How long have you had Google + installed? Did you recently just update that?
Edit2: Fortunately, for CM7 there is a patch that fixes SOD. If you want it, I can post a link.
Edit3: Here. Flash this with CWM. It will replace your wifi driver with a patched one that resists SOD.
Sent from my Nook HD+ running CM10.1 on Hybrid SD
Thank you and...
Lots of good information here. Google+ has been installed for at leat 6-9 months that I can recall. I could uninstall and reinstall, I guess. But...
It's seemed to have righted itself two days ago, so I haven't had a problem - until...
Last evening. I was doing some eMail using K-9 plus floating through Google+. And I put it down to go do something. Came back and it's still working (pulled up the desktop by clicking the "N") but the Wi-Fi is shut off again. Went to Wireless and Network Settings and what I see is "Wi-Fi" sitting on the words "Turning off...". Everything beneath it is greyed out. Decided to just leave it and see. Half hour or so later, it's still in a state of "Turning off...". I backed all the way out and did a restart. On restart, Wi-Fi is turned off so I hit the box to turn it on, it obeyed and went directly to my home router, signed in and I'm back on again.
As the evening progressed, what I got in the habit of doing is short-pressing the Power button to turn off the screen. I found I could reliably come back, wake it up and the Wi-Fi would start back up again on its own without intervention.
So until I get a chance to sort out all the stuff you gave me to do/patch, I'll try to just manually "sleep" the system. I have to study up more on what you said because the terminology and procedures, while probably very clear to most, are not exactly clear to me.
Thanks again for the info.
Hoib
leapinlar said:
First that 'unwanted shutdown' is called SOD, Screen of Death. Very common with some devices and combination of apps. Do a little searching on that and you will get overwhelmed with info. Since you were not having it before, it must have something to do with that app or apps that you had to adjust recently. It is tied in with deep sleep and wifi.
Have you tried just forgetting the routers in your wifi list?
Edit: I just reread your post. How long have you had Google + installed? Did you recently just update that?
Edit2: Fortunately, for CM7 there is a patch that fixes SOD. If you want it, I can post a link.
Edit3: Here. Flash this with CWM. It will replace your wifi driver with a patched one that resists SOD.
Sent from my Nook HD+ running CM10.1 on Hybrid SD
Click to expand...
Click to collapse
@leapin. I should have come back to post add info. My apologies. I believe I was able to resolve this a bit later. I looked at Juice Defender (free) and what it does. I uninstalled it. As soon as I did that, I suffered no more of these SOD problems. Been running great since June.
So was this the real SOD? Or was it Juice Defender setting the power profile in such a way that the Wi-Fi never got the signal to reawaken? What do you think?
Hoibb
Hoibb said:
@leapin. I should have come back to post add info. My apologies. I believe I was able to resolve this a bit later. I looked at Juice Defender (free) and what it does. I uninstalled it. As soon as I did that, I suffered no more of these SOD problems. Been running great since June.
So was this the real SOD? Or was it Juice Defender setting the power profile in such a way that the Wi-Fi never got the signal to reawaken? What do you think?
Hoibb
Click to expand...
Click to collapse
It could have been the real SOD being triggered by Juice Defender. Usually it is some app that triggers it (trying to use wifi while the device is in deep sleep), but the underlying problem is SOD. Some folks never experience an SOD.
Sent from my Nook HD+ running CM10.1 on emmc.
I just got my case today and my N7 doesn't always wake when I open the cover. I'd say it works about 80% of the time and it seems worse after the tablet has been sitting for a while. Almost as if it's sleeping too deeply to wake. A press of the power button fixes it but I'm wondering if anyone else is having this issue. If not, I need to think about whether I have a bad case or a defective tablet.
Sent from my Nexus 7 using xda app-developers app
Well what case have you got?
I have no such problem on my Portenzo hardback case.
RKight said:
I just got my case today and my N7 doesn't always wake when I open the cover. I'd say it works about 80% of the time and it seems worse after the tablet has been sitting for a while. Almost as if it's sleeping too deeply to wake. A press of the power button fixes it but I'm wondering if anyone else is having this issue. If not, I need to think about whether I have a bad case or a defective tablet.
Click to expand...
Click to collapse
On mine, if you lose WiFi connection while it is asleep it won't magnetic wake.
sfhub said:
On mine, if you lose WiFi connection while it is asleep it won't magnetic wake.
Click to expand...
Click to collapse
Same. WiFi on or off seems to work okay... WiFi on and searching is always touch and go for me. Hopefully it can be fixed pretty easily in software down the road... before it starts to actually bother me.
Noticed this on mine as well. Different than my 2012 model but not a real problem
Sent from my Nexus 7 using Tapatalk 4
RKight said:
I just got my case today and my N7 doesn't always wake when I open the cover. I'd say it works about 80% of the time and it seems worse after the tablet has been sitting for a while. Almost as if it's sleeping too deeply to wake. A press of the power button fixes it but I'm wondering if anyone else is having this issue. If not, I need to think about whether I have a bad case or a defective tablet.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I've found that it does actually wake up, eventually. I just tested it myself. When I got my Poetic slimline case, I was obviously messing with the Nexus 7 and it worked every time. I'd left the device sleeping (wifi set to not run during sleep, BT off), and when I grabbed it just now and opened the flap, nothing happened for almost 10 seconds. Crazy. However, it did eventually sleep/wake by itself. When I closed the cover and then opened it, it instantly awoke. So it seems like after the device has been sleeping for a while it just takes it a bit to wake up. Of course you can just hit the power button, too..
WilliamG said:
I've found that it does actually wake up, eventually. I just tested it myself. When I got my Poetic slimline case, I was obviously messing with the Nexus 7 and it worked every time. I'd left the device sleeping (wifi set to not run during sleep, BT off), and when I grabbed it just now and opened the flap, nothing happened for almost 10 seconds. Crazy. However, it did eventually sleep/wake by itself. When I closed the cover and then opened it, it instantly awoke. So it seems like after the device has been sleeping for a while it just takes it a bit to wake up. Of course you can just hit the power button, too..
Click to expand...
Click to collapse
With WiFi set to stay on during sleep it works fine even during very long sleeps, like overnight. It's almost a non-issue for me since I always have WiFi on and if I go out I just remember to toggle it off or turn on tethering on the trusty old N4.
negroplasty said:
With WiFi set to stay on during sleep it works fine even during very long sleeps, like overnight. It's almost a non-issue for me since I always have WiFi on and if I go out I just remember to toggle it off or turn on tethering on the trusty old N4.
Click to expand...
Click to collapse
Yeah. All I know is I have the wifi set to not run during sleep, and all seems fine, - just that it takes the Nexus a good number of seconds to come alive after it's been asleep a while.
I decided to wait patiently and see if it would wake on its own. It did but took a full 20 seconds. On my first gen N7, it woke instantly every time. Hopefully it's something they'll eventually fix.
Sent from my Nexus 7 using xda app-developers app
RKight said:
I decided to wait patiently and see if it would wake on its own. It did but took a full 20 seconds. On my first gen N7, it woke instantly every time. Hopefully it's something they'll eventually fix.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
lol should start a contest! Whose Nexus 7 2013 takes the longest to wake up?!
Same for me.
I noticed if WIFI is ON, or device is connecting to power/USB. The wake will works perfectly and instantly.
But if WIFI is OFF or not USB connection, the wake is not function after closed the cover for few seconds.
WilliamG said:
lol should start a contest! Whose Nexus 7 2013 takes the longest to wake up?!
Click to expand...
Click to collapse
mine...mine...
Last night (I timed) it took 30seconds.
This morning (1st wake of the day, didn't exactly timed) it was more than a minute.
USPS has had my replacement "out for delivery" since early yesterday ... but never made it.. talk about the
organization in trouble... I usually see the man parking his truck in the shade, taking his time.
hyperxguy said:
mine...mine...
Last night (I timed) it took 30seconds.
This morning (1st wake of the day, didn't exactly timed) it was more than a minute.
USPS has had my replacement "out for delivery" since early yesterday ... but never made it.. talk about the
organization in trouble... I usually see the man parking his truck in the shade, taking his time.
Click to expand...
Click to collapse
That's impressive! I'm sure it's a bug that affects all Nexus 7 2013 devices, but it's still lame.
For anyone having this issue, I found a thread on the Google product forums about this. That's apparently how they became aware of the other issues that have been reported. If you could, please post your problem in this thread: http://productforums.google.com/forum/m/#!category-topic/mobile/android-devices/8MTpqfFmw8Q
Sent from my Nexus 7 using xda app-developers app
Are we sure this is actually an issue? Based on the threads I'm reading about this, the cover only seems to wake the screen when you open it while things are running that would normally keep the N7 out of deep sleep. Isn't the tablet being able to enter deep sleep mode successfully a good thing?
The reason I say this is because a lot of you, including myself are reporting that when Wifi is off, and the tablet is unplugged, opening the cover won't wake the screen if it's been closed for a long time but it will after just short periods. This indicates deep sleep being entered successfully. If the cover is able to wake the screen in that mode, I'd be more worried that deep sleep mode isn't being entered successfully.
I guess the main question is: Is 4.3 along with the Nexus 7 hardware actually designed to only be able to be powered on by the power button itself during deep sleep? Do not services have to be running in the background constantly in order to allow something else to wake the screen? For example, in order for one of those 3rd party screen apps that use either proximity sensors, or light sensors or position sensors (shake) in order to wake your screen to work, all of the better ones I've seen not only require administrator permission, but also running background services.
In other words, they use the hardware sensors inside the Nexus 7 to wake the screen but also require some kind of additional resources running in the background. Which means resources being consumed. Smart covers also use hardware inside the N7 to wake the screen but without an app consuming resources in the background to so do. Which means NO resources consuming battery or memory, which is a good thing.
I'm not so sure I even WANT this fixed if it's going to mean my tablet has to have stuff running in the background in order for it to work. If Google can make it so that's not the case, then I have no problem with it. I could be completely wrong as well, I'm just speculating so if Google says it is actually a software bug then I guess I am.
omnius1 said:
Do not services have to be running in the background constantly in order to allow something else to wake the screen?
Click to expand...
Click to collapse
I guess that depends on the magnetometer chip they are using. If it can generate an async interrupt on a change in magnetic field, then that is one thing, if it has to be polled, that's something else. I don't find it too great a hardship to occasionally have to press the button, so if it is doing this to save more power, that suits me.
I think this thread is about all the "odd" things happening, specifically to the some 2013 Nexus 7 (some people don't have this problem).
I also have the 2012 N7 and the Nook HD+ with smart covers, both are running JB4.3.
Both can go into deep sleep and whatever (wifi on/off, things running or not) and will wake up in an instant as normal.
This is not normal !!
By the way, I received the replacement and similar results. I didn't expect it to fix the issue anyway as I think this is similar
to the tough issue with some N7s (I don't have this issue) which is a google problem.
A little off-topic about deep sleep... my Nook HD+ can sleep for a whole day and only take 1% of the battery.. best I've seen.
Edit: just in case somebody thinking about a ROM problem, I've tried multiple ROMs including stock.. all have same issue.
Moko smart cover is the best
It should wake up within a second, at worst, period. Ideally it'll wake up "almost instantaneously". There's something wrong.
I wish the mods would merge these two threads so the nonsense is at least in one place.
Mine sometimes will wake after a delay and will sometimes just sit and do nothing at all until I press the power button. It has turned on after a 30 second delay, after being idle all night, but has also completely failed to turn on after being idle for just five minutes. This thread is definitely aimed toward the odd inconsistences and what I indeed perceive to be a problem.
Sent from my Nexus 7 using xda app-developers app
I've googled and searched on xda but haven't been able to find much. So at night when I place my phone on the charger ask is good until it is completely charged.
The screen pops up telling me that I now have full charge and to disconnect charger. Bad thing is.....it doesn't go away..!!! Now I'm left with the screen lighting up the entire bedroom in the middle of the night.
Now this would bother me much but my girlfriend is now waking me err up in the middle of the night asking me to turn my screen off.
Please help!!!
Sent from my SM-N900V using Tapatalk
xtrandrix said:
I've googled and searched on xda but haven't been able to find much. So at night when I place my phone on the charger ask is good until it is completely charged.
The screen pops up telling me that I now have full charge and to disconnect charger. Bad thing is.....it doesn't go away..!!! Now I'm left with the screen lighting up the entire bedroom in the middle of the night.
Now this would bother me much but my girlfriend is now waking me err up in the middle of the night asking me to turn my screen off.
Please help!!!
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Go into Settings>Developer Options (if you have it enabled) and look at the "Stay Awake" option. Make sure it is unchecked. If it is checked, the screen will stay on when it is plugged in unless you manually turn it off. I am guessing this is checked for you and is why the screen stays on.
PrsnlCrcl said:
Go into Settings>Developer Options (if you have it enabled) and look at the "Stay Awake" option. Make sure it is unchecked. If it is checked, the screen will stay on when it is plugged in unless you manually turn it off. I am guessing this is checked for you and is why the screen stays on.
Click to expand...
Click to collapse
Thanks for the help but this is one of the first things I checked. This isn't the fix
Sent from my SM-N900V using Tapatalk
Root your phone and disable the full battery notification is that easy glad I could help
Sent from my SM-N900V using XDA Premium 4 mobile app
rayraycarter4 said:
Root your phone and disable the full battery notification is that easy glad I could help
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This may sound dumb.. but I can't figures out where that setting is.. would you please guide to to the correct location
Well it looks like I may have found a solution to my problem. Found an app called Batter Charged Silencer. Not in the Google play store. Will try it tonight and see what happens.
Sent from my SM-N900V using Tapatalk
Found a solution! PLEASE READ IN FULL
Hey man. I have a Note 3 and have the same problem. As you've probably discovered by now, the Battery Charged Silencer app does not work for our newer devices. In searching for alternatives, I found apps that provide an alarm for when the battery is fully charged. This was NOT what I had wanted, as I just wanted my light to go off when charged, but I figured this the best alternative (hear the alarm, unplug). HOWEVER, I discovered that one app in specific DOES NOT WORK AS IT IS SUPPOSED TO, and, because of this, my phone never lights up when fully charged!!! Go to the play store and get the free NEOADN FULL ALARM. I launched it once, disabled the notification bar selection because I didn't want that (so maybe do this just in case, and also leave the discharged amount option alone), picked a sound, and nothing mattered cause it never worked, never came on, and neither did my screen! One of the reviewers of this app said the app was crap cause it had to be launched each time to work. Maybe that's why it "works" for me, cause I activated it but then held my home button down and closed all apps (not thinking) and then realized it was a blessing! Just install, maybe configure how I said if needed, close your apps, and never worry about it again! (And don't ever update the app just in case they "fix" it). Hope this helps, let me know via email: [email protected]
xtrandrix said:
I've googled and searched on xda but haven't been able to find much. So at night when I place my phone on the charger ask is good until it is completely charged.
The screen pops up telling me that I now have full charge and to disconnect charger. Bad thing is.....it doesn't go away..!!! Now I'm left with the screen lighting up the entire bedroom in the middle of the night.
Now this would bother me much but my girlfriend is now waking me err up in the middle of the night asking me to turn my screen off.
Please help!!!
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
abracadavis said:
Hey man. I have a Note 3 and have the same problem. As you've probably discovered by now, the Battery Charged Silencer app does not work for our newer devices. In searching for alternatives, I found apps that provide an alarm for when the battery is fully charged. This was NOT what I had wanted, as I just wanted my light to go off when charged, but I figured this the best alternative (hear the alarm, unplug). HOWEVER, I discovered that one app in specific DOES NOT WORK AS IT IS SUPPOSED TO, and, because of this, my phone never lights up when fully charged!!! Go to the play store and get the free NEOADN FULL ALARM. I launched it once, disabled the notification bar selection because I didn't want that (so maybe do this just in case, and also leave the discharged amount option alone), picked a sound, and nothing mattered cause it never worked, never came on, and neither did my screen! One of the reviewers of this app said the app was crap cause it had to be launched each time to work. Maybe that's why it "works" for me, cause I activated it but then held my home button down and closed all apps (not thinking) and then realized it was a blessing! Just install, maybe configure how I said if needed, close your apps, and never worry about it again! (And don't ever update the app just in case they "fix" it). Hope this helps, let me know via email: [email protected]
Click to expand...
Click to collapse
Surprisingly the Batter Charged Silencer app did work for me. I've been good to go ever since. No more waking up to the girlfriend telling me to turn my phone off in the middle of the night