Battery Conservation Vs Windows Battery Warning!!!! - MDA III, XDA III, PDA2k, 9090 General

Hay All
Don't know if anyone else has had this, but its been getting on my nervous. Basically, as any Xda user would probably already know, when ever the Xda battery gets a tad on the low side, say, 20% downwards, The OS starts harassing you and trying to "tell" you that your battery's lows. As a result, the Xda keeps powering on in order to "tell" you that its battery's are low, which uses yet MORE power, and because my XDA's in a leather case in my pocket, its starts pushing either hardware or screen buttons, and by the time you've pulled the xda out of your pocket, you've got every program installed running, the wireless is on, which sucks even MORE of your battery to the point its empty. Is their anyway to disable either the Xda turning on to "warn you" (not that you can do anything about it if your away from your charger) or just set the screen not to come on?
Any other idea's will be appreciated...
cheers all!...

You could use MortSaver with the option to lock your device on power on (Simple two button sequence press to unlock like a mobile phone...). I use it to stop the same thing happening during any message alert...

Related

Shut off when battery is low?

Last night i was using my phone right before going to bed. The battery was at about 18% or so left. I got up to get a glass of water then came back to plug the phone in to the outlet only to notice that the red led was not on. I pressed the power button and nothing would happen. The phone completely shut off without interaction. So I panicked a little and plugged to PC USB cable that was attached to my PC and nothing. wasn't detecting or anything. so I press and held the power button and plugged it in at the same time and it powered on again. Anyone know what could have happen?
Only time i faced this problem was when i tried to drain my battery completely. it wouldn't shut down on its own when it reached 0%, so i turned it off myself.. The next moment is wouldn't boot or charge also. Then i held the power button and it came back to life.. Don't know what the exact cause is though
d33f said:
Only time i faced this problem was when i tried to drain my battery completely. it wouldn't shut down on its own when it reached 0%, so i turned it off myself.. The next moment is wouldn't boot or charge also. Then i held the power button and it came back to life.. Don't know what the exact cause is though
Click to expand...
Click to collapse
Yea it kind of turned me off on the phone. But I still love it. anyone else have a similar issue like this? I'm hoping that it is the power management issue that some people are having as there is a quick fix with that. I was avoiding rooting or modding my phone, but I might just have to now.
i'm a noob so i don't know much about most of this, but this really sounds like the way my ipod functions if i let the battery "die." i can't imagine that any manufacturer making a phone with a non-removable battery doesn't have it set up to be rechargeable upon plug in.
1earful said:
i'm a noob so i don't know much about most of this, but this really sounds like the way my ipod functions if i let the battery "die." i can't imagine that any manufacturer making a phone with a non-removable battery doesn't have it set up to be rechargeable upon plug in.
Click to expand...
Click to collapse
Ye, furthermore i've read that this is cause but letting the battery ''die'' indeed, it takes time to charge it back up because when you let it die some kind of undervolting protecting is kicking in i guess and soon after it will start to charge

99% sure bricked [not bricked]

So, my S2 would occasionally overheat, then hotboot and just hang on the boot animation, so I would have to pull the battery.
This morning same thing happened so I pulled the battery, and I'm sure it burned out.
Main signs:
1: plugging into the wall, the phone just vibrates "on" every 3-4 seconds.
2: holding the power button to turn it on, it vibrates, then nothing.
3: holding volume buttons, it vibrates, flashes "samsung" then nothing.
4: i haven't tried download mode, but I wouldn't expect much.
I just wanna know if there's any way to access the internal memory, and try to pull off any files I can.
Luckily I did a nandroid backup yesterday, so I can get everything back to normal pretty quick, but getting everything I had saved would be nice.
Hi there cavemaneca...
From my experience with Samsung devices, I find that when they are in a state of very low charge their usability takes a ****. I have had this experience on 3 different Samsung devices, the Infuse (I997), the T-Mobile S989, and the (Vibrant?) Roommate's T-Mob Galaxy 4S phone. One particualr issue is that when the battery is in the red, and it is actively plugged into a charger, the touch screen becomes either completely non responsive at all, or the touchmove events get all corrupted in weird counter intuitive directions. This happens until the battery is around the yellow areas, somewhere like +15% or +20%.
I have also consistently encountered your specific issue, in which a Samsung phone, once drained dry, will not actually appear to be charging, but rather just give steady *buzz* *buzz* *buzz* for what seems to be an indefinite amount of time. This however, for myself, has always self corrected after some time. I suggest the following two parts to the solution:
1) Get a strong enough charger base plug thing. For lack of the appropriate lingo, I use either of the following:
This grey base charger from T-Mobile directly for androids with the extra usb port on board. Good charging rate...
OR
Your standard HTC charger base
2)Once you have gotten a strong charger connected directly to it., GO DO SOMETHING ELSE. I recommend Dark Knight Rises, Cabin In The Woods, possibly the new Todd Solondz film with Christopher Walken, or Ted. I would bet good money that when you return, your phone will have stopped vibing and will be nearly charged. It's happened to me on this phone way more often than I would care to admit...
Salutations!
99% sure your phone isn't bricked. Your phone vibrates and flashes the Samsung logo... It's not bricked. it might be a battery problem try a different battery or charger, i used a bad cable and it took forever for it to finally hold enough charge to boot up.
But yeah try getting into download mode... Connect into a computer holding +/- buttons, it should boot into it automatically.
Sent from my SGH-T989 using xda app-developers app
Whether you can go into download mode IS the sign if you are bricked or not. Though, it sounds like a battery issue.
Sent from the pink Unicorn from the Darkside.
Thanks for all of the replies!
This is my first Samsung device, I'm use to HTC devices that brick pretty easy.(had about 4 or so so far that bricked)
It turns out that out of the 2 micro-usb plugs I had on my desk, one wasn't plugged into the wall, so I thought it had been charging all night but it just ran it completely dead, coupled with the fact that it had frozen in a bootloop.
It took over an hour, but it's at least showing signs of life now (still says 0%). I guess my device just needed that day off...
Probably your charger, time to invest in a new one.
Sent from my SGH-T989 using xda app-developers app
It feels like it was yesterday that this was happening to me. Now if your phone boots up the logo and goes black to continue vobrating, your power button could be at fault.
Sent from my SGH-T989

[Q] Something Completely Strange... Seriously

Ok, So i have been pretty cautious with my GNII, but finally ran into my first issue....
I hate to say it, but im on Jedi X9 (although with custom theme, if that makes a difference) and after having absoulely zero issues thus far... i finally had my first Ohhhh S***** moment. Here is some Background...
After trying for almost an hour to get UPnPlay to read my Laptop (battery readings went from 13% to 6%) and finally deciding that my phone wasn't picking up the Laptop because the Wifi needed to be reset... and of course, after reseting the wifi, UPnPlay read my Laptop like a charm... Anyways, I decided to go smoke a cig and let my phone charge for a sec while i was doing so, and then this happened....
As i go to plug my phone into the stock charger, nothing happens... try to hit the power button.... nothing... unplug and tap power button nothing... try to switch sockets (top to bottom).... Nothing... change wall outlets completely... nothing.... Go into a different room and plug into a different outlet (in a different room)... nothing.... finally (after taking off my Otterbox-Defender Case) and pulling the battery... I put battery back in and plug phone into the wall... It starts to charge....
Still havent turned the phone back on....ok, just did and everything seems to be working fine (no bootloop)... recieved alerts (unread Emails/SMS/MMS)... but wow that was sorta a trip... NOT SURE WHY MY PHONE WASN"T CHARGING FOR THAT LITTLE INSTANCE OR WHY IT WENT FROM ~6% to 0% within what had to be just a few seconds (unless i was just abducted by aliens and had that whole time-lapse issue)....
Anyone else experience anything like this yet... ON ANY PRIOR DEVICE EVER???
I think I did once on my s2. But the phone was really dead and I got scared -_- . Since then I dont like it when the phone reaches 0% on my phone.
Sent from my SGH-T889 using xda app-developers app
Dito
Same thing happen to me on GSII. Long story short I was using my phone while it was charging, but it was still declining. I didn't think much of it until i was on zero for awhile. I wondered stupidly how long it could stay on zero while charging. Whole scenario was probably 20 min. Like an idiot I forgot and pulled the cord out on accident because I had also just put a file on and it instantly shut off. The phone was like vibrating weird. it would flash but turn off. I left it on a charger for hours, waiting waiting. And it just turned on. Lesson learned... Speaking of, just looked over and forgot I came on here because my GNII is stuck in bootloop hahaha. Gotta go
It is a good idea to watch your battery charge on modified ROMs and not allow the phone to go bellow 9 %..
That has always been my rule.
Keep the phone on the charger whenever you can, and also allow the devise to display the percentage battery
on the taskbar. This will allow you to keep an eye on how much energy is left.
maniep said:
It is a good idea to watch your battery charge on modified ROMs and not allow the phone to go bellow 9 %..
That has always been my rule.
Keep the phone on the charger whenever you can, and also allow the devise to display the percentage battery
on the taskbar. This will allow you to keep an eye on how much energy is left.
Click to expand...
Click to collapse
I usually let mine drains till 2-5% and then charge. I've been doing this since HD2 days and I never had any issue + getting great battery life.
Sent from my SGH-T889 using Tapatalk 2

[Q] auto Power on when charging

Hello everyone,
I have my old willy here on a drawer and i just remembered i could use it as a GPS tracker for my car in case some day (hopefully not) someone will try to take it away from me.
The plan is just to leave it hidden somewhere inside the vehicle and have it always on probably with a power bank connected too for when the battery drains. The powerbank itself is connected to the car power to start charging when the car is on.
There are tons of different apps to handle this so the problem isn't that. The problem is the "always on"... There are some periods when i only use my car once a week or less and even then it is not enough to charge the power bank completly. So there are times when the phone would be with no battery left and shuts down.
All i want is a way for it to auto power on when some charge is initiated (ie. the car is started and the battery starts charging). Simply put, is there any way for the phone to turn on when it is connected to a charger?
I have found some people that could acheive this by modifing the lpm file in /system/bin but that file is not present in my CM7 wildfire. This file controls the launch of that ugly battery screen that shows when we charge a phone if it is powered off, the replace that screen launch by a boot command. Where in our wildfire is that file present?
If it is not possible, how much time would you gess the battery will last beeing with the screen off? What cappacity of powerbank would be needed to last for, say, 2 weeks?
Thank you very much
mad.maximo said:
Hello everyone,
I have my old willy here on a drawer and i just remembered i could use it as a GPS tracker for my car in case some day (hopefully not) someone will try to take it away from me.
The plan is just to leave it hidden somewhere inside the vehicle and have it always on probably with a power bank connected too for when the battery drains. The powerbank itself is connected to the car power to start charging when the car is on.
There are tons of different apps to handle this so the problem isn't that. The problem is the "always on"... There are some periods when i only use my car once a week or less and even then it is not enough to charge the power bank completly. So there are times when the phone would be with no battery left and shuts down.
All i want is a way for it to auto power on when some charge is initiated (ie. the car is started and the battery starts charging). Simply put, is there any way for the phone to turn on when it is connected to a charger?
I have found some people that could acheive this by modifing the lpm file in /system/bin but that file is not present in my CM7 wildfire. This file controls the launch of that ugly battery screen that shows when we charge a phone if it is powered off, the replace that screen launch by a boot command. Where in our wildfire is that file present?
If it is not possible, how much time would you gess the battery will last beeing with the screen off? What cappacity of powerbank would be needed to last for, say, 2 weeks?
Thank you very much
Click to expand...
Click to collapse
Firstly, this is a pretty cool idea =)
Secondly you would need to work out how slowly the battery discharges. So say on idle with no screen time you get 2 days, with a stock the battery of say 1300mAh. In order to run two weeks you would need 7 full charges. So 7x1300mAh should be a 9100mAh battery.
Now as far as your power on is concerned its the recovery on htc devices that deal with charging while off and low power management as far as i know. So you could try look to the kernel or the clockworkmod source code for a way to power on or you could try make a device that activated the power button once the car engine was turned on, depressing it for say a full minute then releasing. When your android is already powered on the screen turning on will be the only side effect.
I will keep thinking =)
Sent from my nexus 7 using Tapatalk
You kinda answered my question. If that math is right, if I connect the phone to a 20000mAh powerbank I have a month of life to give it. I can live with that. Not the "cleanest" solution but not bad. I use the car at least once a week so....
If I hardwire it to the car battery which is 60000mAh it would last even longer
Some device to push the button would be too unpractical, it has to be a software solution like the one I talked about. People have done this in all of the samsungs and also I have seen in a Sony x10 mini, all done modifying the bootloader. Unfortunately, my knowledge about how to fiddle in bootloaders, kernels or source codes is laughable at best, so I need some kind of walk-through...
Imagine beeing able to hide it inside the sun visor with a little peek hole... Instant mugshot!
Sent through my Oneplus via tapatalk

Repeated freezes, possible SystemUI crash?

Hi all,
I have a VZW P3XL (required for work, otherwise I'd have the unlocked Google version) that's been suffering a LOT of crashes in the last few weeks. Usually it's while the phone is idle with the screen off, but it's occasionally happened while I'm actively using it, too. When it's happening while I'm using it, whatever app I'm in freezes completely; if I press the power button the screen turns off and then it's entirely unresponsive until I hold power to reboot. It's not seen by adb in this state. Once or twice when this has happened I've gotten a "SystemUI keeps not responding" message, but usually there's no message. When it happens while I'm not using it, it's just unresponsive with a black screen until I hold power to reboot. The issue has persisted through a factory reset/OTA sideload, which is about all I could think to do with a locked bootloader.
Anyone have any thoughts/suggestions for troubleshooting?
Pixel troubleshooting chat wasn't much help, not that I expected it to be. It's out of warranty so they're directing me to ubreakifix, saying they can "guarantee" it'll be fixed.
Oh, and they had me boot into safe mode and it happened again immediately.
I wonder if the battery's going bad? I've noticed that it tends to happen when the charge level is in the 60s or lower, and I don't think it's happened while plugged in (though I could be wrong about that). I wonder if there could be some sort of inconsistent voltage or something? Kind of a wild-ass guess.
chinly43 said:
Pixel troubleshooting chat wasn't much help, not that I expected it to be. It's out of warranty so they're directing me to ubreakifix, saying they can "guarantee" it'll be fixed.
Oh, and they had me boot into safe mode and it happened again immediately.
I wonder if the battery's going bad? I've noticed that it tends to happen when the charge level is in the 60s or lower, and I don't think it's happened while plugged in (though I could be wrong about that). I wonder if there could be some sort of inconsistent voltage or something? Kind of a wild-ass guess.
Click to expand...
Click to collapse
Battery is a good point and probably the best conclusion from the things you observed... (there where similar issues on the Nexus 6 iirc, after certain wear off the battery the OS got unstable as battery could no longer provide the amount of energy the CPU needed in specific demanding situations, replacement was the only option to get rid of the problem...)
It would help to check what's left from the design capacity of your battery, if it's near 70% of the original design capacity it's most likely the source for your issues and replacing it would most likely help, if you get a good quality replacement battery, otherwise it will do more harm than good...
Get AccuBattery from PlayStore, even the base version of the app gives you reliable information on your battery wear out, again the magic number is around 70% but there's plenty of information on the app itself regarding this matter!
Sent from my Google Pixel 3 XL using XDA Labs
Thanks for the advice, Sam; I'm trying, but it deteriorated further overnight and now only will stay on for 30 seconds at most, usually shorter, unless it's plugged into my laptop (and it doesn't pull enough voltage to charge in that case, it just drains more slowly). Either way, I appreciate the reply.
This must be a battery issue, it can't take a charge whatsoever now. 28% left until it's forever dead, 4XL arrives today.

Categories

Resources