Should I Keep My Moto 5g Plus Plugged In Overnight

A Moto G5 Plus device (Android 8.1.0) was charging and performing normally with a healthy battery response.

One morning, instead of being at 100% (expected afterwards charging all nighttime), the telephone reported 61% (unexpected after charging all night). This was with the aforementioned charger I always use, which is the ane that came with the telephone. I likewise tried different chargers and cables, but at that place was no deviation in symptoms.

Settings > Battery reports that the phone is charging, just the reported charging pct does not increase at all. And so if I plug it in at night with 42%, it says 42% again in the morning.

The device is discharging at a normal rate. In other words, given a certain level of charge, and not plugged-in, the battery lasts a normal/long/expected amount of fourth dimension (many hours with just a few battery percentage points downwardly).

Theory of Cause: Non Slow Reject

Because of the suddenness and severity of the difference between the former and current observations, the likelihood of this being attributable to unproblematic wear on the battery seems unlikely. That leaves a software problem as a more likely crusade. A sudden hardware failure could too be the cause, only information technology seems less likely that a sensor of a sudden failing is less likely than fallout from a software update.

1. Clear Enshroud

Action

I read that clearing cache could help, so I tried that past doing the post-obit:

1. Press Power and Volume Downwards and hold a long time until you run into the screen have a "weird menu" thing
2. Press and release Book Down until y'all run into Recovery Style, and so press Power. You'll come across an Android on it'southward back with a triangle/assertion mark.
3. Hold the Power push button and then press and release Volume Upward then release all buttons. You lot should run across a listing of deportment.
4. Use Volume Down to ringlet to wipe cache partition, so press and release Power to activate.
5. Use Volume Downward to gyre to reboot system now, and so printing and release Power to reboot.

Upshot: No Alter

Symptoms seem to persist equally earlier: while plugged in and while the phone reports that it is charging, the percentage reported does not increase.

Diagnostics

Because I'm an Android developer, I take admission to Logcat in Android Studio. I meet this reported periodically in the logs:

POWER_SUPPLY_VOLTAGE_NOW=4394353, POWER_SUPPLY_CHARGE_RATE=Normal, POWER_SUPPLY_HEALTH=Good, POWER_SUPPLY_CURRENT_NOW=124510, POWER_SUPPLY_PRESENT=1, SUBSYSTEM=power_supply, POWER_SUPPLY_TEMP=302, SEQNUM=3965, Action=change, POWER_SUPPLY_NAME=bombardment, POWER_SUPPLY_STATUS=Charging, POWER_SUPPLY_CHARGE_COUNTER=3038000, POWER_SUPPLY_CAPACITY=32, DEVPATH=/devices/soc/qpnp-smbcharger-17/power_supply/battery}

This is with the USB cable is plugged into a calculator, of course.

The POWER_SUPPLY_VOLTAGE_NOW value ranges from 4394xxx upwardly to 4397xxx, indicating the PC is offering a slightly different voltage over time or that the phone reads the voltage slightly unlike (0.07%), which seems normal.

The POWER_SUPPLY_CURRENT_NOW value ranges from 91xxx to 354xxx, simply mostly is around 112xxx. This variability probably has to practise with how much activeness is going on in the phone and whether the screen is on. This as well seems normal.

The POWER_SUPPLY_TEMP value started at 317 (when I outset started logging) to 275 (after an hour). I'm not sure what this change (-13%) means, if anything. Probably because the screen was on before in the log and mostly off after in the log.

The rest of the fields seem not to be changing over time.

2. Lower Temperature

Activeness

Knowing that some phones have had issues with getting too hot while charging, I thought that peradventure this was an aggressive safety affair that was being incorrectly triggered. The telephone was NOT getting even slightly warm when charging, just I thought I'd put it in the freezer while being charged. I put it in the freezer for an hr or two with the cord attached, and the phone "on".

Upshot: Improved, But Not Resolved

Afterward charging the telephone in the freezer, the phone did show a higher battery percent. The reported per centum was erratic, though. It jumped around from the 90% range to the xxx% range. The reported percentage changed as I plugged it into the charger and removed it from the charger.

3. Plugged in While Off

Activity

To reduce the number of programs active during charging, I powered the telephone off and left it connected to the PC. Based on the PC's reaction to the USB connection, I can tell that there's still some kind of processing going on in the device, but I thought it might brand a difference. The device reported 32% at the start. It indicated that the device was charging.

Event: Same Symptoms

Afterwards leaving the device connected for an hour, it still reported 32%, and then the main symptom of this question persisted, fifty-fifty if the charging activity was undertaken while the device was "powered off".

four. Safe Fashion

Activity

Although since charging with the device "off" didn't help, I didn't have much confidence in this action improving things, but wondered if the USB Logcat debugging would piece of work and possibly testify some diagnostics.

1. Printing and hold Power until on-screen card shows Power off.
2. Touch and hold Power off until Reboot to safe fashion shows on screen.
3. Affect OK (device begins restarting).

Result: Same Symptoms

Leaving the device, while in safe fashion, connected to the PC for an hour, it remained at 32%. The Android Studio Logcat did provide this a possible clue No service published for: batterystats:

          2019-05-15 19:23:52.186 2682-2682/? East/AndroidRuntime: Fault reporting WTF     coffee.lang.NullPointerException: Try to invoke interface method 'boolean android.app.IActivityManager.handleApplicationWtf(android.bone.IBinder, java.lang.Cord, boolean, android.app.ApplicationErrorReport$ParcelableCrashInfo)' on a null object reference         at com.android.internal.os.RuntimeInit.wtf(RuntimeInit.java:332)         at android.util.Log$one.onTerribleFailure(Log.java:117)         at android.util.Log.wtf(Log.java:481)         at android.util.Log.wtf(Log.java:471)         at android.app.SystemServiceRegistry.onServiceNotFound(SystemServiceRegistry.coffee:1085)         at android.app.SystemServiceRegistry$StaticServiceFetcher.getService(SystemServiceRegistry.java:1037)         at android.app.SystemServiceRegistry.getSystemService(SystemServiceRegistry.java:962)         at android.app.ContextImpl.getSystemService(ContextImpl.java:1682)         at com.android.internal.os.PowerProfile.getBatteryCapacity(PowerProfile.java:463)         at com.android.internal.bone.BatteryStatsImpl.setPowerProfileLocked(BatteryStatsImpl.java:8983)         at com.android.server.am.BatteryStatsService.<init>(BatteryStatsService.java:175)         at com.android.server.am.ActivityManagerService.<init>(ActivityManagerService.coffee:2954)         at com.android.server.am.ActivityManagerService$Lifecycle.<init>(ActivityManagerService.java:2853)         at coffee.lang.reverberate.Constructor.newInstance0(Native Method)         at java.lang.reflect.Constructor.newInstance(Constructor.java:334)         at com.android.server.SystemServiceManager.startService(SystemServiceManager.java:96)         at com.android.server.SystemServer.startBootstrapServices(SystemServer.coffee:539)         at com.android.server.SystemServer.run(SystemServer.java:407)         at com.android.server.SystemServer.main(SystemServer.coffee:285)         at java.lang.reverberate.Method.invoke(Native Method)         at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)         at com.android.internal.os.ZygoteInit.master(ZygoteInit.java:791) 2019-05-15 19:23:52.187 2682-2682/? East/AndroidRuntime: Original WTF:     android.util.Log$TerribleFailure: No service published for: batterystats         at android.util.Log.wtf(Log.java:476)         at android.util.Log.wtf(Log.coffee:471)         at android.app.SystemServiceRegistry.onServiceNotFound(SystemServiceRegistry.coffee:1085)         at android.app.SystemServiceRegistry$StaticServiceFetcher.getService(SystemServiceRegistry.java:1037)         at android.app.SystemServiceRegistry.getSystemService(SystemServiceRegistry.java:962)         at android.app.ContextImpl.getSystemService(ContextImpl.coffee:1682)         at com.android.internal.os.PowerProfile.getBatteryCapacity(PowerProfile.java:463)         at com.android.internal.os.BatteryStatsImpl.setPowerProfileLocked(BatteryStatsImpl.java:8983)         at com.android.server.am.BatteryStatsService.<init>(BatteryStatsService.java:175)         at com.android.server.am.ActivityManagerService.<init>(ActivityManagerService.java:2954)         at com.android.server.am.ActivityManagerService$Lifecycle.<init>(ActivityManagerService.java:2853)         at java.lang.reverberate.Constructor.newInstance0(Native Method)         at coffee.lang.reflect.Constructor.newInstance(Constructor.java:334)         at com.android.server.SystemServiceManager.startService(SystemServiceManager.java:96)         at com.android.server.SystemServer.startBootstrapServices(SystemServer.java:539)         at com.android.server.SystemServer.run(SystemServer.coffee:407)         at com.android.server.SystemServer.primary(SystemServer.coffee:285)         at coffee.lang.reflect.Method.invoke(Native Method)         at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)         at com.android.internal.os.ZygoteInit.primary(ZygoteInit.java:791)      Caused by: android.os.ServiceManager$ServiceNotFoundException: No service published for: batterystats         at android.bone.ServiceManager.getServiceOrThrow(ServiceManager.java:75)         at android.app.SystemServiceRegistry$17.createService(SystemServiceRegistry.java:319)         at android.app.SystemServiceRegistry$17.createService(SystemServiceRegistry.coffee:316)         at android.app.SystemServiceRegistry$StaticServiceFetcher.getService(SystemServiceRegistry.java:1035)         at android.app.SystemServiceRegistry.getSystemService(SystemServiceRegistry.java:962)          at android.app.ContextImpl.getSystemService(ContextImpl.java:1682)          at com.android.internal.os.PowerProfile.getBatteryCapacity(PowerProfile.coffee:463)          at com.android.internal.bone.BatteryStatsImpl.setPowerProfileLocked(BatteryStatsImpl.java:8983)          at com.android.server.am.BatteryStatsService.<init>(BatteryStatsService.java:175)          at com.android.server.am.ActivityManagerService.<init>(ActivityManagerService.java:2954)          at com.android.server.am.ActivityManagerService$Lifecycle.<init>(ActivityManagerService.java:2853)          at java.lang.reflect.Constructor.newInstance0(Native Method)          at java.lang.reflect.Constructor.newInstance(Constructor.java:334)          at com.android.server.SystemServiceManager.startService(SystemServiceManager.coffee:96)          at com.android.server.SystemServer.startBootstrapServices(SystemServer.coffee:539)          at com.android.server.SystemServer.run(SystemServer.coffee:407)          at com.android.server.SystemServer.chief(SystemServer.java:285)          at coffee.lang.reflect.Method.invoke(Native Method)          at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)          at com.android.internal.bone.ZygoteInit.principal(ZygoteInit.coffee:791)  2019-05-15 19:23:52.187 2682-2682/? D/BatteryStatsImpl: Reading daily items from /data/system/batterystats-daily.xml                  

Seeing batterystats, above, led me to run the following command:

          adb crush dumpsys batterystats > c:\my\tmp\batterystats.txt                  

That generated a file with over 46,000 lines. At that place'southward apparently a way to analyze that data, just I haven't figured that out (yet?). More than detail is on this folio on the Android Programmer site.

five. Overnight Freezer w/Device Off

Activeness

The device was powered off, plugged in, showed as charging at 32%, and then placed in the freezer. The side by side solar day, the device was placed in a sealed bag at room temperature and let to naturally warm upwardly.

Issue: Still No Charging

The device was started normally and showed 32% (same per centum, no charge was reported). Repeatedly plugging/unplugging the PC USB did non cause the reported percentage to modify. Repeatedly plugging/unplugging the 110 USB ability adapter did not cause the reported percentage to change.

This was unexpected, since earlier it seemed that a reduced temperature acquired charging to occur. This could have been because the telephone was "off" or it could have been that the earlier low temperature charging was coincidence.

Beneath is the battery usage diagram for the last few days while this problem has been going on. You can see the erratic changes, indicating that the percentage is inaccurate. The span without data is when the phone was "off":

half-dozen. Allow Discharge

Activity

Through all of these steps, the device was typically plugged in. The next activity I inadvertently tried (due to not being in a place where power was bachelor), was to allow the phone to run without power connected.

Consequence: Erratic Accuse Percentage

Later on Not existence connected to ability, the charge percentage stayed at 32% for around 6 hours, then the next time I looked, the accuse percentage was unexpectedly shown every bit 93%. Then without a power connection, the telephone significantly increased it'south reporting of battery percentage as shown in the epitome below.

Over the adjacent 3 days, without significant charging, the battery proved to exist very healthy. I plugged the device into my figurer one time for a few minutes to interact with Android Studio and the percent dropped from 65% to 0% instantly. When I unplugged the device, it immediately shutdown. When I turned it on again, it showed 65% once more (run across spike in the graph, beneath).

Discussion

Given that the device ran for three days without charging, i must conclude that the battery itself is healthy.

Given that the device runs for a very long time afterward beingness plugged in indicates that charging going on, the bombardment is picking upward a charge, fifty-fifty though the reported percent does not increase.

Also, given that the battery is successfully picking up a accuse indicates that information technology's not the cablevision, the adapter, lint in the micro USB plug, or annihilation like that.

So something almost the ability of the device to reflect proper level of accuse remaining is "broken".

QUESTION:

Is there an activeness or set of deportment I tin can take to get the device to resume normal reflection of percent charge remaining?

Source: https://android.stackexchange.com/questions/212482/how-can-i-fix-a-charging-problem-on-moto-g5-plus

Posted by: wheelerdill1989.blogspot.com

Share this post