I’ve got my hands on a pair of Samsung Galaxy S4 GT-i9500 which I’d like to repair/renew, but their batteries are sadly bloated, and I’ve been unable to find replacements. The 3,7V 5,9Wh batteries are labelled as EB-LIDTIBA, but I’ve been unable to find any information about them. What’s more, their dimensions (60 mm × 44 mm × 4 mm) are smaller and do not correspond to the standard EB-B600 battery. Here’s a side-by-side comparison of the elusive *ED-LIDTIBA* battery on top of the commonly-mentioned *EB-B600B* battery.

Overnight, starting from a 100% charge, all apps closed, even from a fresh reboot, screen of course off, my phone (Redmi 6) ends up with a ~90% charge. I know this is abnormal, as my previous phone (Redmi 5A, with worn out battery) ends up with ~99% in the same situation. That's quite annoying to know that *something* needlessly drains my battery! I'm pretty sure it's due to some software bug. Encountering the issue as well on MIUI 10 and 11. I'd like to find out the culprit in order to fix the issue. What can I do?
For the record, my syslog receives the following two errors *a lot* (several per second): BoostFramework() : Exception_1 = java.lang.ClassNotFoundException: com.qualcomm.qti.Performance BoostFramework() Ux Perf : Exception = java.lang.ClassNotFoundException: com.qualcomm.qti.UxPerformance (then, just in case, I went to the Developer options and fully disabled logging, who knows! But it didn't fix the battery issue.)
Also for the record, I have already done a lot of googling about that battery drain issue, and tried the following fix: Go to "Settings > App > Permissions > Autostart" and disable everything (in my case I only had "Camera" enabled). Sadly, it didn't fix the issue.
**Update:** I've had run "Battery usage stats" during the day, and it reported me that the screen was most (like 90~95%, as I recall) using the battery, followed by a few % by the networks (cell, wifi). But here I just looked at "Battery usage stats" and it gave me interesting results: Screen 35%, Cell standby 31%, Wifi 24%… This is something I was also suspecting. It's highly possible the battery drain is caused by network (both cell and wifi) activity, which in turn could be caused by some software bug. Even though I made sure that no apps or widgets are running. What could I do to investigate further this path? Maybe there is some setting (possibly advanced) that could fix the issue?
**Update 2:** As suggested in the comments, I tried "airplane mode" (i.e. cell and wifi networks disabled) and it seems to solve the issue. I think that both, cell and wifi, cause battery drain. However, that adds an annoying handling step, and I cannot receive calls while in airplane mode. I wish I could avoid that extra handling. I usually don't use wifi, so I'll try disabling only wifi and see if it's sufficient. The MediaTek chipset of the Redmi 6 definitely seems to be a bad pick. This chipset forbids almost any custom ROM, and now I discover it's not energy-efficient at all for networks…
**Update 3:** Some feedback after an extensive period of testing. I can keep cell network and mobile data always on, turning the wifi off seems to be sufficient. Overnight, the battery goes down to barely 99%, it reaches 98% at the very worst… sometimes it even stays at 100% :) Coupled with a good mobile plan, I just keep the wifi always off, and no longer think about this issue :)

The menu appears to have been hidden on the more recent Android releases — currently on Android 14 the only per-app toggle the users are given is 'allow background usage' (app info → app battery usage). On my Oneplus 8T device the OS is actively stopping some apps designed to be running on the background at all times, such as Shizuku . On AOSP-based ROMs three settings used to be available for each app, the most permissive being 'unrestricted'. SystemUI Tuner didn't expose the menu. --- Using ADB is an acceptable answer as well.

Nearly three years ago I have asked [this question](https://android.stackexchange.com/q/69477/20449) . It brought certain attention, but no answer. Of course there is no change in Nexus behavior and device discharges its battery up to 30-50 times faster when completely turned of than when it is turned on, but not used at all. To my complete surprise, after these nearly three years I have notice the very same behavior in many more mobile devices, irrespective of device type, manufacturer or even operating system. Recently I noticed this in: - Sony Xperia E, - Apple iPad Mini (first edition), - Microsoft Lumia 640 and 650. Is there any consistent theory or answer, why it is happening? Why device drains battery at all, when it is (should be) completely turned off? And why the discharge rate is so enormously1 high? I'm looking for an answer at least partially proven or grounded on some verifiable facts. Spy theories -- that it is due to fact that completely turned off device sends a lot of information to Google / Facebook / Apple / Microsoft / US Government -- are quite out of scope of this question. 1I'd say that even absurdly high, given the fact that device completely turned off can't stand more than 24 hours while turned on, but unused at all (lying on shelf) can last up to a week or at least a few days.

I have used the adb shell dumpsys battery command on my phone. It delivers the following results (posted on the image). Most of the terms, I can understand but not the charge counter. What does it indicate and why does it decrease whenever I connect my phone to the USB cable? What is the significance of charge counter for battery? I tried googling but cant find the answers. " class="img-fluid rounded" style="max-width: 100%; height: auto; margin: 10px 0;" loading="lazy">

I am interested in understanding the charging capabilities of the Google Pixel 9a. Specifically, I would like to know the maximum wattage it supports for both wired and wireless charging.

I brought 'Moto G24 Power' smartphone 2 days back. From day one it is overheating evening when I am doing basic tasks. I brought it from Flipkart online. There is no return, only repair from service center. Is there any heating problem with this model or is it an hardware issue? What should I do?

I am trying to get battery info in Termux. I granted android.permission.DUMP and android.permission.PACKAGE_USAGE_STATS via ADB for com.termux (Termux app) Then I opened Termux and types in /system/bin/dumpsys battery. It displays this error message:

Can't find service: battery

and exits with code 0. I can confirm that I can get those info via ADB using the same command (e.g. getting battery level with /system/bin/dumpsys battery | grep level) Am I missing some permissions for Termux app? Or are there some more fixes? Please help. Edit: I am aware of the existence of termux-battery-status command in Termux. It's output is not too informative. So I will not accept answers telling me to use the command.

On my Moto G22 running Android 12.0, with the stock "Clock" app (com.google.android.deskclock Version 7.10), when I set an alarm or a timer while battery saver mode is switched on, the Clock app issues a warning: > Battery saver may degrade your alarm experience. I always use battery saver (unless my phone is charging), and neither the alarm nor the timer has ever failed me. How exactly may battery saver "degrade [my] alarm experience"? Does it affect some fancy features that I don't use? Or is this warning essentially incorrect? I found [several](https://www.boards.ie/discussion/2058250500/alarm-clock-battery-saver-may-have-degrade-your-battery-experience) [web](https://www.reddit.com/r/GalaxyS23/comments/128mpj6/battery_saver_may_degrade_your_alarm_and_timer/?rdt=36755) [results](https://brainly.com/question/32168966) , none of which were helpful.

I usually disconnect my cellphone from the charger some time after it's fully charged because I'm afraid the battery could lose capacity over time if I don't. However, I believe modern electronics should be able to handle this kind of scenario and automatically stop charging the battery once it's full. Does this apply to modern Android phones? Or do I need to continue disconnecting it all the time?

Device : Moto X Play ( Rooted, Stock, Android 6.0.1, msm8916 Board, XT1562) ## Why do I want to limit charging ? ( Let's leave out whether my reasons are valid or not and accept that I **want** to, if you disagree with my reasons) To improve the longevity of battery , I wish to limit charging when it reaches 90%, as explained here https://android.stackexchange.com/q/156526/131553 ## Is it possible? Yes, at least on my previous device Honor 6, as brought out here https://android.stackexchange.com/q/92413/131553 , with two different ways of doing it I have tried unsuccessfully to identify the file responsible in which changing values would limit charging ## I am looking for the system file responsible for stopping charging, with it's true path (without symlinks) (as I saw on on my previous device, locating the path of file was a big challenge after identifying it) ----------

By battery insertion I mean current flowing on the battery pins, **not** the micro USB port. **Description** The phone in question is a Samsung Galaxy Xcover 4, the **bootloader** is **unlocked**, and I have **root access**. Its intended purpose is as a kiosk device that will be sealed inside an external hard plastic enclosure. This means that the power button is unavailable for booting the phone. The phone is powered directly from the wall by means of a custom-made battery eliminator PCB, and I need the micro USB port for host mode UART communication, which means it will never be charged/powered via the micro USB port. **What has been attempted so far** As mentioned, the device is rooted, so I've tried modifying the BOOT partition image and flashing an updated one. The modifications I've been looking at pertains to the program /init in the root directory. and its associated /init.rc /init.samsungexynos7570.rc /... files. For example, I was able to make the phone boot upon receiving charge via the USB port by overwriting the contents of the file /system/bin/lpm with the script #!/system/bin/sh echo b > /proc/sysrq-trigger because /system/bin/lpm is referenced in a service specified in the charging section of /init.rc. I was also able to make it boot via USB port charging by removing the existing "on charge" triggers in the init.*.rc files, and simply adding on property:ro.bootmode=charger: trigger late-init For more details about what I did, see this link . But this is **not a solution for me** because I want to make it boot simply by powering the battery pins, not the micro USB port (which is preoccupied with being in host mode, so it definitely can't be charged). **Further thoughts** However, since modifying the /init.rc file changed its behaviour even while "off" (i.e. it now boots upon micro USB charging as opposed to not), this seems to tell me that the phone is never really completely off when "off", and that the /init program is constantly running as long as there is enough charge on the battery pins (please derail this thought train asap if this is completely wrong). Which would mean the kernel and the /init program should start automatically when there's sufficient charge on the battery pins. So my thinking was to simply add something along the lines of trigger late-init or start (where *my_service* for example could be the lpm script I mentioned above) in an early init trigger stage, so that it would boot simply by virtue of the /init program running. But so far I've had no luck. Does anyone know whether something like this would possible? Thanks for your time.

I have a Moto G phone. I'm using LineageOS. Yesterday I notice my phone went dead. When I press power button, a white light in the camera flashes three times, which I understand to be no battery. It did have enough battery though. When I connect the phone to charge (using PC), the 0% battery charging screen shows up. But it's stuck there at 0%. I can get to the boot menu (power button and volume down), which shows me "battery low", but when trying to boot recovery or any option, the phone restarts but is again stuck at low battery. My guess is that the battery is gone. Since it cannot be charged, the OS doesn't have the power to load anything. However, it should load when the phone is connected and "charging". Perhaps the problem is not the battery itself but the phone recognising that the battery **does have enough charge**. Is this possible? Anyway, any idea is more than welcome.

I've recently found my old Galaxy S6 in a drawer, where it's been sitting for the last ~1.5 years. In that time, the battery has swollen very badly, pictures below: I need to so something about the phone, as I feel it might be a fire hazard to keep this at home especially when I'm not present during the day. Naturally I'm not going to attempt to charge the battery or turn the phone on in this state. I would like to remove the battery and take it to a recycling/ewaste collection point. I'd make sure to take precautions when removing the battery to avoid puncturing it or applying pressure, but with this level of swelling, is just handling the phone/battery dangerous? If so, I could instead take it to a technician to remove the battery or just recycle the entire phone - but I'd still need to carry the phone there, obviously, so some risk would remain. Is there a risk of a sudden explosion or fire without warning?

I have a phone whose battery is dying at 80%. How can I calibrate Android so that it's aware of the actual battery capacity? I have root access. To be clear, I'm not asking to increase the capacity or re-calibrate the battery itself, only make a change to Android so it can reflect the actual battery capacity. I'm pretty sure the battery is fake since even when it was brand new it would die at 30%, so I have no expectations of getting more life out of the battery itself.

I downloaded an app [Phone INFO](https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo) which shows a number of stats, particularly "Battery Discharge Cycles". I want to know if this number is being retrieved from the battery (i.e. it's just the number of cycles for the current battery) or the phone (i.e. it's the sum of the cycles across all batteries the phone has contained). In other words, if I insert a brand new battery, should I expect the count to drop to zero? Context: I have a Samsung S6, which doesn't allow easily changing the battery. I went to a phone repair shop to have the battery replaced. I left it there for the day and did not observe the process of replacement. Now I suspect that I was scammed and the battery has not been changed. I want to confront the shop and use the cycle count (which is still very high) as evidence, so I'm checking my understanding first.

So after replacing the battery in my One (M8) with a new one from eBay, the notification light just blinks orange when charging. When swapping back to the battery before replacement, it, at least, shows a battery charging screen. What am I doing wrong? I've heard something about 'deep discharge' where it needs to be on the flashing light for 15 to 30 minutes to actually start charging or something like that. Is this new battery a dud? Should I keep charging it? Really don't know what to do at this point... Update! I reseating the battery connector on the motherboard and now it's a solid red light when plugged in! Hooray! When pressing the power button, though, nothing is shown on the screen. It's still all black. I just now replaced the screen, since I broke the LCD below the glass last time I tried to take it apart.

My G2 Android used to last an entire day without charge for the past year. Now it appears that it gets to very low energy at about halfway through the day. Is there something like coconutBattery (Mac) for the Android? > With coconutBattery you are always aware of your current battery health. It shows you live information about the battery in your Mac, iPhone and iPad. I am essentially looking for original Design Capacity (ie. 6900 mAh) and now the Current capacity (6559 mAh).

I've recently completed a screen replacement on my Galaxy S20 FE. I got a new screen pre-installed on a frame, so the repair was to basically transplant all the internal components into the new frame. I followed this iFixit guide . One of the steps was to remove the battery for installation in the new frame. I soaked it in isopropyl alcohol and let it sit a few minutes. Aftewards I used a pick and the flat side of a plastic spudger to pry at the battery from the lower right side (looking from above): It wasn't too hard but it did take a few minutes and a few attempts. Afterwards, this is what the side of the battery I pried at looked like: and zoomed in a bit: **The question:** I know lithium ion batteries can be dangerous if damaged - do I need to be concerned about using this battery in my new frame? I reused it because the phone had been used for one year prior to this repair and the battery has 200 cycles, so it hasn't aged much yet. I suspect I'm overthinking this but I've seen spectacular videos of charged lithium batteries catching fire when damaged and I'm feeling uncertain now.

How can I keep "Battery Saver" enabled, even when my device is charging? I travel a lot on multi-day excursions where I don't have access to power, so I charge my phone with a battery bank. It seems silly that Android automatically disables "Battery Saver" mode when my phone is charging. Just because my phone is charging doesn't mean I'm not interested in saving power. How can I force "Battery Saver" mode to remain enabled, even when charging my Android device? Ideally I'd like to do this without installing any closed-source software.