Database Info

Turn off Fully Charged notification

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.

Random shutdown solution!

Random shut down solution! At least for me.
My phone shuts down pretty much 2-5 times a day since i got it. No matter what I do to it. But I tried the app, load monitor and enabled WAKE LOCK and my phone hasnt rebooted in 4 days!
Anyone else had similar experience.
Sent from my SAMSUNG-SGH-I897 using XDA App

Umm, not meant in an asshat way at all man, but your real solution is to take that sucker back. I wouldn't put up with that at all. Bad phone. Just my opinion.
From a phone on an app

I have to agree with the post above mine. I believe it's a hardware issue and that you should return it for another one. I have two captivates and neither I've of them have ever had the random shutdown issue.

Truth is, the phone is bad. Ask for a warranty replacement. I went through 2 phones until I got a good one with no issues. A perfectly good working phone should never randomly shut off as mine were doing before (4-10 times a day) Even setting Set-CPU to 1000mhz 100% of the time didn't fix the other phones I had. Hell, even leaving the screen on the entire time one of them still shut off once.

Others have found that the "wake lock fix" has not worked (although it initially seemed promising). If your shutdowns recur, exchange the unit. That's been the only remedy to date.

Did you have set cpu installed? That's what happened to me after installing set cpu. Sometimes it would lock up after the screen went off & sometimes it would just reboot randomly. I got around this by setting the min clock speed to 200mhz. I think set cpu sometimes undervolts the cpu when scaling especially at 100mhz & at 1000mhz when the screen is off. If it did that stock then I would definitely return that pos! Wake lock will kill your battery life.
Sent from my SAMSUNG-SGH-I897 using XDA App

Well we will see. I was in the process of a rma and just got the phone last night.
I see if the new one has any issues. By the way this will be my 4 th phone(3 through the first month, this one through rma). So the get another phone idea kind of sucks.
Just a curser glance at the back of the rma phone and I can see its different. So maybe I'll get lucky on it.
Sent from my SAMSUNG-SGH-I897 using XDA App

. .

Same here, I'm in Australia, I bought the phone from the US, It used to shutdown 3 - 5 times a day, especially when it's fully charged. Wiped the phone (Internal and external) and now it's solid stable. no special apps or settings or whatsoever. It's a little bit weird though.

I think the problem may be from the phones overcharging. Mine was brand new and I left it on the charger overnight then took it off the charger in the morning and when I came home from work it was powered off. It may be a safety feature built into the phone and not a defect. I had it happen to me twice when I didn't take it to work with me after charging it all night the night before.
Sent from my SAMSUNG-SGH-I897 using XDA App

I leave mine plugged in all the time overnight and it has Never booted off
Sent from my SAMSUNG-SGH-I897 using Tapatalk

galaxyjeff said:
I think the problem may be from the phones overcharging. Mine was brand new and I left it on the charger overnight then took it off the charger in the morning and when I came home from work it was powered off. It may be a safety feature built into the phone and not a defect. I had it happen to me twice when I didn't take it to work with me after charging it all night the night before.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I thought the same, but last night I forgot it on the charger with no problems at all, No shutdowns... Strange...

It happens to my Samsung S Vibrant and I *think* I can reliably reproduce the issue, at least on my phone.
Steps:
1. Go to a spot where you know it has failed, for me this is my office because it has bad reception and it seems to only shutdown for me when there is bad reception.
2. Make sure 3G is turned on and open an application that uses data.
3. Wait for the phone to sleep, do not hit the power button or anything to make it sleep (not sure if this step matters)
4. Wait ~30 mins without touching the phone (You can play music with it while this is happening if you want, the music will stop to let you know it's failed)
5. Try to wake up your phone, it is now dead.
I'm not sure this will work for everyone but last night I could reproduce 3 shutdowns in an hour and a half. And reproduced about 7 shutdowns yesterday when my phone only usually shuts down ~2 times a day.
I'm testing out all kinds of software permutations (disabling stuff, installing things like Captivate Keep Alive). Nothing has worked so far, my guess right now is that the problem lies in the Pattern Unlock feature so I have disabled it, I read that on a forum somewhere.
My guess is that if you have too much running in the background it might take up too much cpu or ram so that when the phone tries to come out of sleep it can't get enough CPU power to come out of sleep and therefore gets stuck in a kind of limbo. This theory could then be releated to the SetCPU problem when you set the CPU too low when it sleeps the issue occurs.
Moral of the storey is I have no idea what's going on, but please post if this works or doesn't work. Maybe it will shed some light on the issue, or you can tell me I'm wrong so I can give up. Let me know if you have Pattern Unlock enabled...
Luckily I'm not past the 30 day mark and I'm exchanging for a new Vibrant tonight. Wish me luck!
UPDATE: It's not the fault of Pattern Unlock, just reproduced the issue with it turned off.
UPDATE #2: Got my second Vibrant, just reproduced the issue within 30 mins of getting into work in the morning.

My Captivate used to shut off once every 2 weeks. Now it's doing it 4 times a day. However, I just found this app:
http://uk.androlib.com/android.application.org-bluesteel-cka-qxnim.aspx
Looks promising. I hope this works.

My wife's stock Captivate has been doing this for a week or two (our phones are about 6 weeks old). My rooted Captivate has -not- been doing it. We both have the same "plug it in all night" charging pattern. Hers will be going back shortly.

Jack45 said:
Others have found that the "wake lock fix" has not worked (although it initially seemed promising). If your shutdowns recur, exchange the unit. That's been the only remedy to date.
Click to expand...
Click to collapse
Tha'ts not true.
My phone was working fine. Then I rooted it. Then I started sideloading bunch of apps. Randon shutdown started to happen. I started tracing back and deleted apps one by one. Didn't work. Replacing the phone was out of the question because I live in Canada and bought the AT&T phone cash off a seller.
SOLUTION:
if you have had SetCPU (or overclock app) and had it to anything to your phone, this is what you got to do.
Run the SetCPu again, and make sure that you do Max 200mhz and Min 200mhz.
Reboot the phone.
Then go into SetCPU, disable autodetect. Then uninstall app.
No more random shutdowns.
It is NOT a hardware issue.

I can confirm that the App stops my phone from shutting down.. unfortunately I have to set it to 65% charge for it to work (whereas others can leave it on default 80%).

Found my issue, it was happening when my phone was jumping between the 850 mhz band and the 1900 mhz band. It would freeze and only happen in areas of bad signal. Locked it on to the 850 mhz band and havent had a freeze since.
100 hours of uptime and counting
http://forum.xda-developers.com/showpost.php?p=8612667&postcount=386
I have also heard that some phones experience the issue when fully charged and that putting a wake lock on your phone with captivate keep alive will solve the problem. These are two independant issues.

i'm not really that knowledgeable about how the phone interacts with different bands, but i'm trying to fix this problem as well and i'll try anything. are there any side/adverse affects to locking it onto a single band?

Has anyone tried removing the sim? to see if it still turns off?
The problem im having is when its near full and goes to sleep i need to turn it back on (like it shuts off) but i tried removing the sim and has not had this problem

[Q] This auto-dim "bug" is completely unacceptable...and is driving me beserk

[Q] This auto-dim "bug" is completely unacceptable...and is driving me beserk
Basically, if I turn autodim off and turn the brightness up over 50%, the screen shuts off and when I press power to wake, flashes for 1/10 of a second and then turns off. The only way I can use my tablet with brightness over 50% is when it is plugged in.
How has this not been fixed yet? It's got to be a software issue right? This is completely and totally ridiculous.

Chief85 said:
Basically, if I turn autodim off and turn the brightness up over 50%, the screen shuts off and when I press power to wake, flashes for 1/10 of a second and then turns off. The only way I can use my tablet with brightness over 50% is when it is plugged in.
How has this not been fixed yet? It's got to be a software issue right? This is completely and totally ridiculous.
Click to expand...
Click to collapse
I don't have this problem. I use it at 75-100% most of the time on battery.

I have zero idea what it could possibly be. I'm on the verge of returning and just washing my hands of this thing. It's a shame because the Galaxy Tab will definitely be at a higher price point.

exchange it. Something is wrong. No one else is reporting this issue. I've had my ft stock, running Paul's rom and prime, and all the different kernels. No such problem. Sounds like a hardware fault.

crater said:
exchange it. Something is wrong. No one else is reporting this issue. I've had my ft stock, running Paul's rom and prime, and all the different kernels. No such problem. Sounds like a hardware fault.
Click to expand...
Click to collapse
This.
I get that people can get frustrated when something's wrong but the store should always be the first point of call if you've got a problem. If you get it exchanged and it still has an issue, THEN you get to post about it and complain. Even so, at least post in the right forum...

I have this problem and I've seen 2-3 other people with it, so its not that common by the looks of it. I tried to find a solution but I am RMAing mine as there isnt a fix at the moment.

cpalmer98 said:
I have this problem and I've seen 2-3 other people with it, so its not that common by the looks of it. I tried to find a solution but I am RMAing mine as there isnt a fix at the moment.
Click to expand...
Click to collapse
tryed to mimic the issue here and it does not have that issue, its gotta be a bad unit. these things happen , it just sucks when it happens to u

Random Reboots.. any new info?

Hi everyone.. I searched a bit but couldn't come up with any more answers so I'm wondering if I missed something.
I've had my TF since like May, and for as long as I've had it, I've had this issue.
No matter what kernel or Rom or anything, my TF always randomly reboots ONLY when my screen is shut off and the wireless is left on. It doesn't reboot if I'm using it, and the only way to make it not happen is to turn on airplane mode when I'm done with it.
Its not a big deal, but it is annoying, especially if I leave it in the living room and forget airplane mode. Then whoever is in there gets to watch my TV constantly and randomly reboot every few minutes.
Its just more annoying than anything. Id love to just keep wifi active so it automatically connects when I turn the screen on.
Other than this, my TF has been flawless for like 6 months
Thanks if anyone has any information!

I've suffered through the same issue with my 16gb TF. By any chance do you have your pattern lockscreen turned on? Can't quite remember where, but I read that having it stops the reboots.
I tried it on mine and haven't had one since...but it's only been a day or 2. Can anyone confirm if the lockscreen stops or limits the issue?

avlon said:
I've suffered through the same issue with my 16gb TF. By any chance do you have your pattern lockscreen turned on? Can't quite remember where, but I read that having it stops the reboots.
I tried it on mine and haven't had one since...but it's only been a day or 2. Can anyone confirm if the lockscreen stops or limits the issue?
Click to expand...
Click to collapse
Wow, ill have to give this a try. I've never used the pattern lockscreen.

random reboots
I get this after about an hour of use. If I sitch it off via the button then when I press it again it reboots. If I just let th TF switch itself off (after 5 mins) it switches on normally when I press the start button.

I also had similar problems with my wife's TF, it rebooted randomly just about anytime (not just with screen off), apps crashing randomly. When I returned it to the store where I bought it, they immediately replaced it with a new one that doesn't suffer any of those problems.
If you have such problems, I'd recommend taking it back to the store for repair, because that is definitely not the expected behavior.

unfortunately the lock screen thing didn't work
Can't really take the thing back, I've had it for months.... fortunately this is the only issue I have... I can live with it. Its purely an annoyance that doesn't affect me when using it...

Atrix 2 dying in sleep (freezing)

Hi all
Sometimes, my Atrix 2 will just freeze when the screen is off, and obviously won't come back on until the battery is pulled and reinserted. (draining it at the same time). It seems to have happened the most when airplane mode was turned on.
I'm afraid all this battery pulling will make the cover loose.
Does it happen with anyone of you?
thanks
EDIT: I'm on 2.3.6 stock, non root.

thenext1 said:
Hi all
Sometimes, my Atrix 2 will just freeze when the screen is off, and obviously won't come back on until the battery is pulled and reinserted. (draining it at the same time). It seems to have happened the most when airplane mode was turned on.
I'm afraid all this battery pulling will make the cover loose.
Does it happen with anyone of you?
thanks
EDIT: I'm on 2.3.6 stock, non root.
Click to expand...
Click to collapse
I have never experienced such a problem... So it just freezes while it sleeping? I have one idea but it's kind of stupid, there is an option under display, that says lock in pocket. Try unchecking that, I've had other people tell me that their phone freezes up afterwards...

You might have to do a warranty exchange.
Sent from my MB865 using xda premium

tmease1 said:
You might have to do a warranty exchange.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I've written "drain" but it's not much of a drain - from 100 to 60% in a whole night. A true drain would be with the phone going from full to empty in a couple hours and getting very hot in the process.
I think the phone locks up for some reason during sleep and the cpu never goes into low power mode. As far as I can remember, this has happened only when it was bedtime, with the phone already put in airplane mode, and never in the long standby hours of the day while I work.
I hope this has something to do with software, and not hardware.
(A warranty replacement is out of question, as I'm not from the US...)
I'll try posting in the motorola forum, too.

100-60 overnight is a bit on the high side for drain if you are not using the phone. I would do a warranty swap.

thenext1 said:
I've written "drain" but it's not much of a drain - from 100 to 60% in a whole night. A true drain would be with the phone going from full to empty in a couple hours and getting very hot in the process.
I think the phone locks up for some reason during sleep and the cpu never goes into low power mode. As far as I can remember, this has happened only when it was bedtime, with the phone already put in airplane mode, and never in the long standby hours of the day while I work.
I hope this has something to do with software, and not hardware.
(A warranty replacement is out of question, as I'm not from the US...)
I'll try posting in the motorola forum, too.
Click to expand...
Click to collapse
It's probably something to do with the CPU govener. Try rooting, install bootstrap, then flashing the deodexed version of 2.3.6 found here. Just be sure to flash as a backup by placing it in \sdcard\clockworkmod\backup\. Select restore in clockwork and it should be there.
See if that gets rid of the problem You don't mid rooting right

Yes I mind rooting! Sorry!
I was just seeking for your experience, to know if you did by chance notice this behaviour/glitch... you keep telling me to do an exchange but it's obvious it's not an option for me, as you can see from the flag under my user name. Otherwise I would have got me a new atrix already. (Because of other minor annoyances)
I once had an acer liquid that started getting nuclear-fusion-hot and discharged in 2 hours each time, without the software taking a hit. Now that was hardware related.
As to my atrix2, I am sure it's not hardware related, because it happens only sometimes and in certain circumstances. One time, I turned it off and back on 5 secs after and it was already frozen. No way, we're not talking of hardware fault here.

Thats major drain overnight! I leave my phone on overnight and generally get about 1% drain per hour.
Sent from my MB865 using XDA App

WTF, either I can't speak my mind, or you don't read my posts!
It's not that I get a 40% drain every night. In fact I got it only once, last night, when I decided to leave the phone in deep coma after I found it unresponsive after just a few minutes it was turned off and in airplane mode (the time of brushing teeth and coming back to bed, FYI). In that circumstance I got the 40% drain, but otherwise i get a normal 5% drain like yours.
This thread is not on the battery drain, but on finding what causes the phone freezing while screen-off.
Thank you.

I have never heard of this happening on the A2.
When the phone freezes up, does it get hot at all? It's possible that your problem is hardware-related, but the only way to be sure of that is to make sure that it's not software-related...
It may possibly be one of the apps that you're using. If you're OK with it, then I highly recommend to begin with a hard reset. I write down all of the apps that I know I will need and then I reinstall them after the reset, then if I realize I need to use an app I don't have I install it.
Another thing to try is flashing the fxz. This will clear every single bit of data on your phone and reinstall stock 2.3.4. Then you can update to 2.3.6 and gradually regain your (necessary) apps as with the hard reset.

Sounds kinda like these reported bugs below:
http://forum.xda-developers.com/showpost.php?p=21817704&postcount=36
and
http://forum.xda-developers.com/showpost.php?p=21819590&postcount=37

thenext1 said:
WTF, either I can't speak my mind, or you don't read my posts!
Click to expand...
Click to collapse
You must not be able to communicate your thoughts very well then cause the post I responded to didn't make any mention of the fact it only happened once. And your first post said it happens "sometimes", meaning more than once. Sorry guy, i'm not a mind reader.
thenext1 said:
I've written "drain" but it's not much of a drain - from 100 to 60% in a whole night.
Click to expand...
Click to collapse
thenext1 said:
This thread is not on the battery drain, but on finding what causes the phone freezing while screen-off.
Click to expand...
Click to collapse
I know what the thread is about, but you chose to share your experience with the battery draining issue not only in the first post but also in the once I quoted above which led me to believe this thread was about that as well so that's what I chose to respond to.
Thanks

kirkgbr said:
Sounds kinda like these reported bugs below:
http://forum.xda-developers.com/showpost.php?p=21817704&postcount=36
and
http://forum.xda-developers.com/showpost.php?p=21819590&postcount=37
Click to expand...
Click to collapse
Yeah, sounds like that. What did you do to overcome it?
Do you use airplane mode at all?

916x10 said:
You must not be able to communicate your thoughts very well then cause the post I responded to didn't make any mention of the fact it only happened once. And your first post said it happens "sometimes", meaning more than once. Sorry guy, i'm not a mind reader.
I know what the thread is about, but you chose to share your experience with the battery draining issue not only in the first post but also in the once I quoted above which led me to believe this thread was about that as well so that's what I chose to respond to.
Thanks
Click to expand...
Click to collapse
I think I made sufficiently clear that the draining was secondary to the freezing issue, and, in turn, that the freezing issue happened only sometimes... which, in my (surely flawed) understanding, is more often not the case than it is.
Anyways no problem man!

thenext1 said:
Yeah, sounds like that. What did you do to overcome it?
Do you use airplane mode at all?
Click to expand...
Click to collapse
Not sure what fixed it. I have done a couple things since then.
1.) Rooted <- not sure how this could fix a problem like this.
2.) Froze several apps with Titanium Backup. <- This one makes the most sense.
I never use airplane mode.

The other user (dk-v1) says that his softkey lights come on while the screen stays black.
I don't remember about the lights, probably one time they turned on, but don't remember right now.
About the black screen, I'm not sure what he means, but mine stays black and with backlight off.

From reading the OP...I would suspect that it could be an app that is trying to sync while in airplane mode. I would try troubleshooting (uninstalling one by one to see if the problem goes away) apps that sync, preferably the ones you installed. But if it still persists do a factory reset and start over. Good luck man!!!

my wife actually started having this problem with her inspire recently. I tracked it down to the no led app she was using. deleted it and everything has been fine since. so your issues could most definitely be app related.

thenext1 said:
I think I made sufficiently clear that the draining was secondary to the freezing issue, and, in turn, that the freezing issue happened only sometimes... which, in my (surely flawed) understanding, is more often not the case than it is.
Anyways no problem man!
Click to expand...
Click to collapse
I never said it was the primary issue......u said this thread wasnt about the draining issue, but since u brought it up in your op and subsequent posts its clear it was an issue so when somebody responds to one of the issues you're having, don't be a douchebag about it by saying "thats not what this thread is about". Trying to insult me by insenuating I don't read before I respond is no way to show appreciation for my attempt at helping you. It seemed you were under the impression that a 40% discharge overnight wasnt a major drain so I shared with you my experience thinking it would put yours into perspective.
But apparently explaining my thought process and posting your own quotes for you to see how/why I'd think what I thought isnt enough to knock you off your high horse so I'm over it, carry on. If you feel the need to respond any further you can pm me, no sense cluttering the thread any further.
Sent from my MB865 using XDA App