Devices randomly shutting completely down; Won't power on w/o connecting to charger

[JujutsukaJohnny]

I have two Note 10.1 2014 Edition tablets (both SM-P600's), that are both experiencing the same issue. They will shut off completely at any given time and will not respond to any attempts to power them back on until connected to a charging cable. After that, they will power back on normally, though sometimes they date will be reset back to December 2011.

One of them is rooted and running Lineage OS v14.1-20170413-NIGHTLY-n1awifi and the other is not rooted and running the stock Samsung build, updated to the most recent version pushed out by Samsung (I'd list it, but I don't have it with me at the moment.) Aside from both being the same model, I have replaced the batteries in both with NewPower99 batteries from Amazon, the rooted tablet twice. The rooted tablet started doing it about a year after replacing the battery the first time, and the un-rooted tablet started doing it almost immediately after replacing it's battery. As you might think, my first thought was the batteries, so I took the tablets to the Batteries Plus store and they said that they tested them and they were both fine. I don't know what sort of test(s) they ran, though. I've completely reloaded them both a few times, always leaving the one un-rooted and stock ROM, so I'm not too sure it's a software issue. And, I've reseated the batteries on both, and replaced the internal ribbon cable and the USB charge port on the rooted tablet.

Aside from it happening at random times, there is no rhyme, reason, or pattern that I can find. The batteries on both will charge completely to 100% at what I consider a normal pace, and neither seems to lose power any faster or slower than normal. The shutdowns can happen at any point in discharging, and with any combination of components powered on (GPS, wifi, bluetooth, etc). Sometimes it will be days between occurances, sometimes it will be multiple times within an hour. The only consistencies are that they will not power back on at all until I plug in a charger, and that they don't seem to do it if I keep them plugged in. Unfortunately, with the fragility of the USB port, I don't like doing that. I've used the stock cables and chargers that came with them, as well as many, many different brands of chargers, cables, and external batteries.

I installed the SystemPanel app from NextApp, Inc on the rooted tablet, so I can get to whatever logs or diagnostics it has, but I have no idea where to even begin with that. I've seen a few people post reviews of the batteries on Amazon with similar complaints, but haven't seen any response or solution yet. Does anyone here have any suggestions? If there's any more information that might help, just ask!

Thanks in advance!

 

[Ozark_8125]

I just came on here to look for the same thing on my tablet. I had recently replaced the battery with one off of amazon for about $30 that had good reviews, but then had the immediate shut down issues like you have. I noticed it happens when the screen brightness is anywhere near bright, which made me think it was a battery not able to supply necessary current. If screen brightness was down, it worked pretty well. Since the shutdown was happening so immediately, I wasn't able to get anything off of a logcat, so thought I would try adb from my pc. Well, after an hour at full brightness, it still hadn't shutdown. The moment I pulled the usb though, it died. Nothing noticeable was going on in the logcat when it shutoff that I could see. Suspecting I got a bad replacement battery, I took it to a local batteries plus store that does battery replacements and it did exactly the same thing. It's possible that their battery and the one I got off of Amazon were both bad, but seems like a stretch to me. I just don't feel like spending the money for an actual OEM replacement to make sure. I'm hoping we get some good tablet love this Oct when Google does their conference & new Pixel announcement...

 

[Ozark_8125]

Actually, I was able to reproduce the error while running adb logcat over tcp... but I don't think anything interesting is in here. Basically, running a game (bejeweled), turn screen on full brightness, and then death. Only thing I see that may or may not be of use is 'Draper will always be unthrottled!' Maybe someone more experienced can look??

I/wrap_printf(22859): [ETN]Draper: Show Draper Ad: Game_Start
I/wrap_puts(22859): [ETN]Draper: Ad Not Available
I/wrap_puts(22859): [ETN]Draper: Preload Unavailable
I/wrap_printf(22859): [ETN]Draper: Preload placement:Game_Over
D/PCSP    (22859): INFO: MarketingComponent::LoadAd() called. PlacementName: 'Game_Over'
D/PCSP    (22859): WARN: Using Default Marketing Throttle implementation. Draper will always be unthrottled!
D/PCSP    (22859): DEBUG: Draper is not throttled, making request to draper
D/PCSP    (22859): DEBUG: Draper Calling: https://draper-staging.popcap.com/2/bejeweled-premium/android/en/Game_Over/?AgeVerified=FALSE&Consecutive_Games=1&Country=US&Currency=USD&DaysSinceInstall=744&Game_Mode=Diamond&Games_Per_Session=3&HD_Device=TRUE&HasNoAds=FALSE&HasPoker=FALSE&LstSessDays=1&Session_Length=59667&Time_Since_Ad=19&artres=high&build=1.0.295&device=tablet&uuid=4e8ff857d264eac4&xp=726450
D/NetworkerJNI(22859): Making GET request to: https://draper-staging.popcap.com/2/bejeweled-premium/android/en/Game_Over/?AgeVerified=FALSE&Consecutive_Games=1&Country=US&Currency=USD&DaysSinceInstall=744&Game_Mode=Diamond&Games_Per_Session=3&HD_Device=TRUE&HasNoAds=FALSE&HasPoker=FALSE&LstSessDays=1&Session_Length=59667&Time_Since_Ad=19&artres=high&build=1.0.295&device=tablet&uuid=4e8ff857d264eac4&xp=726450
D/EnterpriseController( 2227): netId is 0
D/Netd    ( 2227): getNetworkForDns: using netid 502 for uid 10188
I/art     (22859): Background partial concurrent mark sweep GC freed 158853(7MB) AllocSpace objects, 11(512KB) LOS objects, 52% free, 14MB/30MB, paused 1.074ms total 197.102ms
D/GameHelper(22859): GameHelper: isSignedIn
D/GameHelper(22859): GameHelper: GameHelper isSignedIn return
D/Bejeweled3Activity(22859): Bej3activity isSignedIn return
D/GameHelper(22859): GameHelper: isSignedIn
D/GameHelper(22859): GameHelper: GameHelper isSignedIn return
D/Bejeweled3Activity(22859): Bej3activity isSignedIn return
D/GameHelper(22859): GameHelper: isSignedIn
D/GameHelper(22859): GameHelper: GameHelper isSignedIn return
D/Bejeweled3Activity(22859): Bej3activity isSignedIn return
D/GameHelper(22859): GameHelper: isSignedIn
D/GameHelper(22859): GameHelper: GameHelper isSignedIn return
D/Bejeweled3Activity(22859): Bej3activity isSignedIn return
D/GameHelper(22859): GameHelper: isSignedIn
D/GameHelper(22859): GameHelper: GameHelper isSignedIn return
D/Bejeweled3Activity(22859): Bej3activity isSignedIn return
V/AlarmManager( 2906): waitForAlarm result :8
V/BroadcastQueue( 2906): [background] Process cur broadcast BroadcastRecord{5cf5288 u0 null} DELIVERED for app ProcessRecord{1f4a8879 12910:com.android.chrome/u0a179}
D/ActivityManager( 2906): startService callerProcessName:com.android.chrome, calleePkgName: com.android.chrome
I/ActivityManager( 2906): Killing 13069:com.android.chrome:sandboxed_process0/u0a179i0 (adj 12): cached #6
I/ActivityManager( 2906): Killing 30901:com.android.calendar/u0a107 (adj 15): empty #39
W/libprocessgroup( 2906): failed to open /acct/uid_10179/pid_13069/cgroup.procs: No such file or directory
I/ActivityManager( 2906): Killing 18995:com.samsung.android.providers.context/u0a5 (adj 15): SPC_empty #40
I/ActivityManager( 2906): Killing 10689:pl.solidexplorer2/u0a149 (adj 15): cached #5
I/ActivityManager( 2906): Killing 5847:com.google.android.apps.wallpaper/u0a170 (adj 15): empty #37
I/ActivityManager( 2906): Killing 27439:com.evernote/u0a200 (adj 15): empty #38
W/ActivityManager( 2906): Scheduling restart of crashed service com.samsung.android.providers.context/.ContextService in 5740164ms
I/ActivityManager( 2906): Killing 5199:com.samsung.android.nearby.mediaserver/u0a67 (adj 15): empty #35
I/ActivityManager( 2906): Killing 8564:com.google.android.gm/u0a169 (adj 15): empty #36

 

[thebadwrench]

I experienced the same problem in my tablet after replacing the battery. What it comes down to is a cheap aftermarket battery incapable of handling the power the tablet demands when the CPU is working hard (i.e. gaming, streaming video etc.).

I did find a way to make the tablet quit shutting down randomly. Install 3c toolbox or Kernel Auditor and lower your CPUs max output. If I remember correctly the CPU maxes out at 1.9Ghz. Set it to something like 1.6Ghz (may vary depending on battery) and problem solved! Shutting off a single core will also work. Obviously, the tablet will need to be rooted for this.

I did this in my tablet for over a year before the tablet finally croaked and I had to get a new one.