After a lot of issues i just ended up downgrading back to kitkat on my galaxyTab S8.4 wifi, from lollipop.
Issues i was experiencing were:
-totally unreliable battery meter & performance. - Could read 100%, and 10 mins later would read 5% and turn off.
-screen flicker - lines would flicker across the screen randomly, usually before the device crashed.
-Rebooting - the device would randomly reboot, but usually happened 3-4 times per hour, making the device useless.
-screen freeze - the touchscreen would stop working randomly, usually before it rebooted itself.
Ive just gone back to kitkat (voided my warranty in the process) and its still to be seen if downgrading resolves the battery issue, but already the screen flicker seems to be gone. Il update after a day or two use.
Very annoyed with Samsung for releasing an unusable update that rendered the tablet useless & the solution was to load a rom myself, voiding the warranty.
Have experienced absolutely none of the issues you refer to on my SM-T805.
Runs just fine for me.
Downgrading to KITKAT doesn't void your warranty.
ashyx said:
Have experienced absolutely none of the issues you refer to on my SM-T805.
Runs just fine for me.
Downgrading to KITKAT doesn't void your warranty.
Click to expand...
Click to collapse
I agree with ashyx , my tab s runs fine n dandy , sounds like you have a faulty unit schmintan
I don't know if your tablet has Knox, you can see status if you go under status in about device, usually, and see if it is "official" or not.
Far as what you did, before you went and loaded a ROM, I would have done a factory reset. Quite often, settings/apps brought over from a previous version cause issue. I don't care if the upgrade tells you too or not, read through the forums and you'll see it littered with people stating how they noticed a massive improvement after their upgrade once they factory reset. Yes, it does suck, but these days Android makes it very easy to do.
schmintan said:
After a lot of issues i just ended up downgrading back to kitkat on my galaxyTab S8.4 wifi, from lollipop.
Issues i was experiencing were:
-totally unreliable battery meter & performance. - Could read 100%, and 10 mins later would read 5% and turn off.
-screen flicker - lines would flicker across the screen randomly, usually before the device crashed.
-Rebooting - the device would randomly reboot, but usually happened 3-4 times per hour, making the device useless.
-screen freeze - the touchscreen would stop working randomly, usually before it rebooted itself.
Ive just gone back to kitkat (voided my warranty in the process) and its still to be seen if downgrading resolves the battery issue, but already the screen flicker seems to be gone. Il update after a day or two use.
Very annoyed with Samsung for releasing an unusable update that rendered the tablet useless & the solution was to load a rom myself, voiding the warranty.
Click to expand...
Click to collapse
Hi, have you solved The issue downvrading? I have The same problems you described.
same issues
White lines then crashes, battery life under 4 hours,
Sounds like a case of broken hardware or one seriously misbehaving application. And in general, if nothing works, I'd recommend to do a full factory reset of the tablet after the lollipop upgrade (erasing all of your data and settings of course). The only issue that concerns me about lollipop is the increase in battery drain at idle. You need to hunt down for the apps that keep your tablet awake. But spend a full battery charge in minutes? No way. Impossible. Get the tablet replaced.
I've been having the same issues. When I did a clean install, the tablet worked fine. However, as I install various apps, the issue begins again. I haven't been able to identify a particular app.
Going to try Marshmallow and see if it's more stable
If you both post your apps list that might be interesting see if you both share an app?
bigaloz said:
I've been having the same issues. When I did a clean install, the tablet worked fine. However, as I install various apps, the issue begins again. I haven't been able to identify a particular app.
Going to try Marshmallow and see if it's more stable
Click to expand...
Click to collapse
nope. no stable mm roms yet.
Well, I've upgraded to Marshmallow and whilst it took a few goes to get it up and running properly (problems with installing gapps) it's working fine (mostly) now.
I've only had it running for a day but it is much smoother and quicker than kitkat and lollipop. So far there hasn't been any random shutdowns. It's too early to say whether battery life is better.
The only problems I've had is the camera isn't working (haven't bothered to look for a fix yet) and auto rotation doesn't work all the time.
I'll keep you up to date on how things go but so far I'm very pleased with the upgrade. I might now upgrade my 10.5
schmintan said:
After a lot of issues i just ended up downgrading back to kitkat on my galaxyTab S8.4 wifi, from lollipop.
Issues i was experiencing were:
-totally unreliable battery meter & performance. - Could read 100%, and 10 mins later would read 5% and turn off.
-screen flicker - lines would flicker across the screen randomly, usually before the device crashed.
-Rebooting - the device would randomly reboot, but usually happened 3-4 times per hour, making the device useless.
-screen freeze - the touchscreen would stop working randomly, usually before it rebooted itself.
Ive just gone back to kitkat (voided my warranty in the process) and its still to be seen if downgrading resolves the battery issue, but already the screen flicker seems to be gone. Il update after a day or two use.
Very annoyed with Samsung for releasing an unusable update that rendered the tablet useless & the solution was to load a rom myself, voiding the warranty.
Click to expand...
Click to collapse
Hola, which procedure did you follow to downgrade OS to kitkat? I m right now on official Lollipop without root.
I had a notion that even if we downgrade to kitkat screen flicker will remain.
Awaiting your reply- thanks in advance
schmintan said:
Very annoyed with Samsung for releasing an unusable update that rendered the tablet useless & the solution was to load a rom myself, voiding the warranty.
Click to expand...
Click to collapse
If your issues are caused by Lollipop wouldn't everyone one else with Lollipop experience the same issues? I have absolutely none of the problems you mentioned and I have had Lollipop installed since it was first made available for this tab. Seems to me you more then likely have a hardware problem. You said you were going to update in a day or two but you haven't so far. I'm curious if downgrading solved your issues.
Sent from my SM-T800 using XDA-Developers mobile app
schmintan said:
After a lot of issues i just ended up downgrading back to kitkat on my galaxyTab S8.4 wifi, from lollipop.
Issues i was experiencing were:
-totally unreliable battery meter & performance. - Could read 100%, and 10 mins later would read 5% and turn off.
-screen flicker - lines would flicker across the screen randomly, usually before the device crashed.
-Rebooting - the device would randomly reboot, but usually happened 3-4 times per hour, making the device useless.
-screen freeze - the touchscreen would stop working randomly, usually before it rebooted itself.
Ive just gone back to kitkat (voided my warranty in the process) and its still to be seen if downgrading resolves the battery issue, but already the screen flicker seems to be gone. Il update after a day or two use.
Very annoyed with Samsung for releasing an unusable update that rendered the tablet useless & the solution was to load a rom myself, voiding the warranty.
Click to expand...
Click to collapse
i have found a fix for the white lines. but you need root
share the fix
zalso said:
i have found a fix for the white lines. but you need root
Click to expand...
Click to collapse
what is the fix? please share! i have root, i have the problem, and it is super irritating!
Fix
brio09 said:
what is the fix? please share! i have root, i have the problem, and it is super irritating!
Click to expand...
Click to collapse
here buddy http://forum.xda-developers.com/gal...-flicker-screen-freezes-t3374336#post66951302
I have the 8.4 and 10.5, both are stock running lollipop and neither device has had the issues you are having!
Sent from my SM-T800 using XDA-Developers mobile app
screen freeze + screen flickers bright flash bars
random reboot, screen freeze and crazy screen flickers with bright flash bars), which occurred when it had low battery
(may be not relevant but have also just given up on firefox for chrome!)
this seems to sum up my experience in the last week or so, I thought I was heading for some hardware failure but parallels what others are reporting....
SM-T705Y running 5.0.2 (LRX22G)
looks like update from 20th May which would be around when this started
Related
Perhaps not random, but possibly keyboard related. I believe I have experienced at least three, perhaps more reboots at various times. I just had one a minute ago when I opened my keyboard from a sleep state (dark screen). My lockscreen had what looked like a Droid X background which caught my attention, then after a couple of seconds, it rebooted.
As I mentioned, this has happened at least twice before, but always when I was trying to do something and (I believe) involving the keyboard. I've never had it reboot in the middle of anything, so the impact is negligible. Add to that how FAST the D3 reboots, it's a very minor annoyance. My old Tbolt used to do that as well, but the reboot time was probably three or four times as long, and it sometimes did it in the middle of something.
Has anyone else experienced this? If you have, sound off and perhaps we can get Moto's attention. If it's just me, then that's great news and I doubt I'll do anything about it since the impact is so minor.
It's hard not to notice since it makes the "Droid" noise when it reboots. Assuming you don't have the same sound assigned to a notification of course.
I noticed it yesterday once (and I just got the phone then too ;-; ), and it was while I was opening the camera app, I decided to open the keyboard for some reason (I don't know why), the phone locked up for a minute and then just rebooted. I also had a temporary lockup while opening up the keyboard while opening Handcent, but it regained responsiveness after about 15 seconds. For me it happens to be something to do with the keyboard while opening apps. We need more people to reproduce this problem so we can get down to the root cause :|
Got two droid 3`s in my house and haven't experience any random boots.
Sent from my DROID3 using XDA Premium App
Happened to me while talking on the phone a few times. Got a replacement and it happened again. Never with the keyboard though. Very troubling especially with the second handset.
I have experienced reboots with the camera and camcorder apps lagging, and just general issues with those apps anyway.
Sent from my DROID3 using XDA Premium App
I haven't had it happen since I originally posted until today. Today it rebooted in my pocket.
Perhaps it could just be a heat issue. I noticed that another thing along with my other conditions I posted was that the phone felt really hot.
Immolate said:
Perhaps not random, but possibly keyboard related. I believe I have experienced at least three, perhaps more reboots at various times. I just had one a minute ago when I opened my keyboard from a sleep state (dark screen). My lockscreen had what looked like a Droid X background which caught my attention, then after a couple of seconds, it rebooted.
As I mentioned, this has happened at least twice before, but always when I was trying to do something and (I believe) involving the keyboard. I've never had it reboot in the middle of anything, so the impact is negligible. Add to that how FAST the D3 reboots, it's a very minor annoyance. My old Tbolt used to do that as well, but the reboot time was probably three or four times as long, and it sometimes did it in the middle of something.
Has anyone else experienced this? If you have, sound off and perhaps we can get Moto's attention. If it's just me, then that's great news and I doubt I'll do anything about it since the impact is so minor.
It's hard not to notice since it makes the "Droid" noise when it reboots. Assuming you don't have the same sound assigned to a notification of course.
Click to expand...
Click to collapse
The Droid 3 has a dual core 1 ghz processor processor built inside which is why it starts up so fast. Its probably having these problems because of the new android OS gingerbread 2.3.2 because of how new this operating system is. The first phone designed with the new OS for verizon wireless was the sony xperia which produced surprisingly a very good battery life with the processer designed for gaming built inside that phone.this reminds me of the first droid on Verizon the Motorola Droid A855 where there where some flukes where it would freeze up every now and then. But there were updates that eventually solved the problem. Because this is a relatively new OS there is deffinittely going to be some flukes in the software and there will be updates to solve these most likely coming soon. And especially as more and more users are buying this phone.
justinsaunders57 said:
The Droid 3 has a dual core 1 ghz processor processor built inside which is why it starts up so fast. Its probably having these problems because of the new android OS gingerbread 2.3.2 because of how new this operating system is. The first phone designed with the new OS for verizon wireless was the sony xperia which produced surprisingly a very good battery life with the processer designed for gaming built inside that phone.this reminds me of the first droid on Verizon the Motorola Droid A855 where there where some flukes where it would freeze up every now and then. But there were updates that eventually solved the problem. Because this is a relatively new OS there is deffinittely going to be some flukes in the software and there will be updates to solve these most likely coming soon. And especially as more and more users are buying this phone.
Click to expand...
Click to collapse
1. Everyone knows that it's dual-core.
2. It runs Android 2.3.4. (Hence no root yet)
3. To the OP, no reboots. Had it since the 13th.
Sent from my DROID3 using XDA Premium App
I haven't seen another reboot since the 28th but I did have the odd experience last night of not being able to get a new wallpaper to take. In fact, I noticed that it had one of the stock wallpapers on it, the diagonal black and grey bars, but couldn't change it. Then this morning I thought about it and rebooted the phone. The last wallpaper I'd tried to change it to came up on reboot. Interesting but not alarming... unless it starts doing that frequently.
FYI I haven't noticed it running hot at any point.
Thanks for all the input everyone.
Probably seen it do it half a dozen times. IIRC it's not a full reboot, just the Android stack (i.e., same Linux kernel instance).
Have a logcat of one and don't seen anything that suggests where the problem is..just a whole bunch of "com.xxxxxx.xxxx has died" followed by normal restart log messages.
Odd that you all are experiencing this. I have not had a single reboot.
Sent from my DROID3 using XDA Premium App
This issue is starting to cause me a good bit of frustration. Most of the time it occurs when waking the phone (sliding out keyboard seems to make it particularly likely). Also seeing complete freezes now which require battery pull.
Phone is now more than 30 days old. It was purchased online. Anyone know the odds of getting a *NEW* (not refurbished) if attempting to return it now? I'm still pretty certain this is a software issue, but may try replacing it in the chance it isn't.
I went into wifi settings and chose to forget all the connections. No more random rebooted.
rustynutzz said:
I went into wifi settings and chose to forget all the connections. No more random rebooted.
Click to expand...
Click to collapse
I wouldn't count on that being the issue.
I've had the problem out in the field (not connected to WiFi) and have had random reboots as well.
Heres a tip for troubleshooting this issue which i 90% guarantee - factory reset your phones put zero apps on them and tweaks, use it for a week and see if u get a reboot.
Then each week after add a single tweak or app(install/uninstall/freeze), may take a yr for some of us since we can't seem to stop downloading random badly coded apps lol...
-smc
For me at least SMC, I've had random reboots from stock during the first week. I'm putting it down to bad software for now.
I usually get 1 a week, sometimes less.
tliebeck said:
This issue is starting to cause me a good bit of frustration. Most of the time it occurs when waking the phone (sliding out keyboard seems to make it particularly likely). Also seeing complete freezes now which require battery pull.
Phone is now more than 30 days old. It was purchased online. Anyone know the odds of getting a *NEW* (not refurbished) if attempting to return it now? I'm still pretty certain this is a software issue, but may try replacing it in the chance it isn't.
Click to expand...
Click to collapse
The same thing was happening to me, the whole rebooting and I went to Verizon for a replacement and got a refurbished DROID 3 Not a New :\
I really hope they fix this because its really bugging me. >:\
-eXsoR
Sent from my DROID3 using XDA App
I get a random reboot usually once a week or sometimes twice a week. It depends on how often I use my camera too.
Well I had a BSOD (a freeze to a black screen that could only be fixed by a bettery pull) a couple of days after my update to version 893. I ws hoping the upgrade would fix this. Has anyone else also had a BSOD after the 893 update?
--
I've been on .893 since the leaks were first discovered and I've had zero BSOD issues.
i have been running 5.7.893 (newer than the current OTA) for more than a month now and still experience an occasional BSOD, the frequency is reduced, but they still occur
PhilDX said:
i have been running 5.7.893 (newer than the current OTA) for more than a month now and still experience an occasional BSOD, the frequency is reduced, but they still occur
Click to expand...
Click to collapse
+1 same here
Geezer Squid said:
I've been on .893 since the leaks were first discovered and I've had zero BSOD issues.
Click to expand...
Click to collapse
Same here - no BSODs, and none of the other errors that others are experiencing.
in fact, the only problem with my BIONIC is self inflicted - I tried to force it back to stock (just to see if eFuse would trip) and now on boot I get a flash failed message, and can only boot the phone via the bootloader. But, other than that, All is well.
I installed the leak version. The only thing it made better on my bionic was the camera. Still having BSOD, and random 3g data drops.
Unfortunately, I gave in an bought the Razr. It seems alot smoother and faster. Just more fluid. Screen is better.
I installed the official OTA last night. I never got a BSOD before the update and I haven't gotten any since the update so far either.
Sad. Have had 3G drop out completely twice in one day since the update. Guess it's time to start hammering verizon for a different phone. Certainly not going to wait for the next update after how long this one took.
I never had the BSOD before the update, but just had it today after update. Completely stock before and after.
Depending on where you are located. A cold phone could be a problem. My friend's Iphone began BSOD when he would leave it in his car in 20(f) degree temps.
I have had BSOD several times but am now running 5.7.893 and think it's related to some kind of app interaction. About 3 weeks ago I did a factory reset, rooted and have been gradually putting apps back on for three weeks no BSOD. Just some thoughts.
I am stock and received the 55893 update. I expected it to fix the things it claimed to fix but it appears it has not. I still lose 4g often. More often than before. Sometimes it switches to 3g and sometimes I lose all connectivity. Before, it only would only switch to 3g and stay there. I also am getting reboots more often now. And by correcting that so-called high pitched whine, I have found that the audio volume for music has significantly decreased. Also, when charging the phone while off, the battery no longer reads accurately. It tells me the phone is at 20% and less than10 minutes later it is fully charged. WTH Motorola?
Sent from my Xoom using xda premium
cmjohns24 said:
I never had the BSOD before the update, but just had it today after update. Completely stock before and after.
Click to expand...
Click to collapse
Same boat. The phone won't wake up from sleep probably twice a day, and I'm forced to pull the battery. PITA.
Hi Everyone
Bit of help please.
Having problems over the last 20 days or so. The phone keeps powering down completely at random.
I had flashed No Root Stock Debloated/Deodexed N6 ViPER|Atmos Audiophile 1.6 and after a week the above started.
Fully wiped (including data) the N6 and re-installed from a OTG USB through TWRP. After a week the same random shut-downs began again.
Another full wipe and installed ver 1.7 from the above and within a couple of days the shutdowns started again.
Today thought a different ROM may be the answer. Full wipe and tried [MMB29U/Q][6.0.1][STOCK][OMNI][MOKEE][CMTE][LAYERS] FLUENCE HD9 and the shut-downs are still here.
Seems to be getting worse.
Not using layers or anything abnormal - nova launcher and popular apps, nothing strange. No Kernel optimizations.
Really stumped as to what I have done. Wondering if I have a HW fault rather than custom rom or apps. Going to un-root, lock the BL and give Google stock image a go, unless anyone has a suggestion.
TIA
Any water damage that you can think of? Any parts of the phone getting extremely hot?
You could try ordering a new battery, and see if that fixes the issue, as it is not a software issue.
I'm also having a similar issue, but it occurs when trying to open camera and having relatively low charges(%20). I could not pinpoint my issue exactly but generally complete shutdowns caused by battery problems(temperature, voltage, mis-feedback). Like flyeyes says it is probably a defected battery unit.
Grab some logcats or a crash message. Without them the only thing I can advise is that it is one of your apps causing it or a hardware issue.
Have you tried complete stock firmware from Google with no customizations? If so, does it happen then? If it happens on complete stock from Google you might be looking at a hardware issue. If it only happens on custom ROMS after you set them up, then it might be an inconsistency with whatever apps/changes you make to it.
Hi,
first of all sorry for my bad english and screenshots with german text .
The situation:
I have a total of two Tab S2 (T-813). The first is 4 years old, the second is less than 2 years old. The newer is now causing problems.
The reboots occur:
- When using the tablet. Definitely with a high load, but also sometimes with only light loads
- When it is charging
- completely random
Edit1: reboots are not related to the battery percentage
Edit2: never experienced a reboot while in TWRP.
I didn't really find anyone with the same problem on the Internet. It is not a boot loop. Sometimes you can use the tablet for hours/ days. Then again not at all, because it starts again after a minute. To narrow down the problem, I formatted both tablets and installed the same lineage version and firmware. Since it restarts, log files are unusable, right?
Is there any way to narrow down the error?
I suspect overheating, but I would like to know if I have any way to isolate the fault exactly. Maybe there is also another (hardware) forum, which can help better in this case, then I would also be grateful for a tip.
I would have no problem opening the tablet. I've already done this with my smartphones.
Thx for your time.
Solution:
It is an overheating problem if you have exactly the same problems as I had.
You can test it simply like this: fill a plastic bag with cold water and some icecubes. Use it like a pillow for your tablet so it can rest on the bag while you use it. I had no problems at all while doing this.
I send it to Samsung and they repaired it.
It's just as new now.
I actually have the same problem, just only when its at 15 or less battery
Hi.
Well, it sounds for me like a different problem, cause it's battery related. My battery is fine and I have reboots not related to battery status.
Have you tried anything (factory reset, newest lineage and firmware,...)?
Hi,
same here. A SM-T813 running LineageOS that started with random freezes and reboots about a week ago. Sometimes I can use it for about half an hour without problems, next time it reboots while rebooting ...
Seems to be completly random, only thing I noticed that it never reboots while in TWRP.
Cleared and reinstalled LineageOS, but didn't change anything. First time rebooted while still in the setup wizard, next time I could finish the wizard and install serveral apps before the next reboot.
Maybe a problem with the memory?
Yes, that is exactly the same.
I never experienced a reboot in TWRP. No problem with reinstalling lineage.
But while reinstalling Android, it reboots while configuring and while reinstalling apps.
The last days I could watch Amazon prime every evening. Now it reboots after a minute even without using it. I shut it off and hope it will work this evening again.
I have the same issue, sent it in for repair asked to flip battery and swap mainboard. Got it back. Worked a few days, then had random reboots again. I am 100% sure it is a battery issue, and when you get under a specific voltage, maybe when it gets under 30% or so, the chance for reboots rise dramatically, with high cpu or flash memory usage. It happens more often when doing a update in Google Play store for example. So totally have no idea, if Samsung flipped the battery or not, but this was my last Samsung product ever. I would assume there is an issue with too much current drain and then it reboots, and the battery used in them are not designed for the units properly.
same to me. i was on stock rom. never root or anything. and got random reboots most of them when i open google play or google chrome. now im on lineage and same. also i notice that the tablet didnt reboot until i install gapps. and the tablet never reboot on recovery or TWSR. reboots on high or low battery. and if it was overheating maybe the tablet will reboot on recovery. dont know its weird. i will try lineage with out gapps to see what happend.
just testing lineage without gapps no reboot. run browser and netflix with no problems. then i install youtube from aptoid store. and reboot start again. o unistall youtube and no reboot for now.
Same here. I have random reboots but also wifi disconnections (unable to reconnect until i reboot the device)...
Not evident cause...
Someone got a solution for this?
Have the same problem on my T813
You can find the solution for the problem I described at the end of the first post.
Mypixel 4xl sometimes randomly shuts down I think an app, may be responsible.
Ampere says my battery is good.
im bootloader unlocked running 12 beta.
but it was shutting down before 12 beta i wiped everything.
was fine for 2 weeks now its doing it again.
anyway to arrange apps by date,so i can see what may be causing this?
I would flash factory stock again and wait a while before installing any root apps. It may be hardware related, or battery connection related. Meanwhile keep an eye on battery temp. Any chance you were outside in the heat when the phone shut down? The other thing you could try would be to put it in safe mode. If it does it in safe mode it is more likely hardware.
So I have a similar problem after installing the latest security update... My phone pixel 4 xl was just fine prior, but now it will turn off randomly when the screen goes off (or is locked to turn the screen off). I can only turn the phone back on after I plug it in to a charger. Interestingly, the battery and phone will keep running and the battery will drain normally so long as I keep the screen/interaction active. Ideas? Thinking about flashing a custom ROM. This phone is stock and nothing has been done to it. I also reset to factory to see if that was the fix, but no joy. Help?
@Springcrime
If the problem remains after a factory reset, you very likely have a hardware issue. The two main battery related issues are 1) the battery connection issue (abnormal or stuck battery percentages) , and 2) the swollen battery issue (no wireless charging, back glass separation (it's not easy to see). Flashing a custom ROM will only add multiple variables that will not solve the problem over restoring the phone to factory stock like you have already. As a last ditch effort, you could flash the phone with a full image and letting it wipe (don't edit the flash-all.bat). If that doesn't fix it you probably need to starting thinking any warranty options, or repair.
v12xke said:
@Springcrime
If the problem remains after a factory reset, you very likely have a hardware issue. The two main battery related issues are 1) the battery connection issue (abnormal or stuck battery percentages) , and 2) the swollen battery issue (no wireless charging, back glass separation (it's not easy to see). Flashing a custom ROM will only add multiple variables that will not solve the problem over restoring the phone to factory stock like you have already. As a last ditch effort, you could flash the phone with a full image and letting it wipe (don't edit the flash-all.bat). If that doesn't fix it you probably need to starting thinking any warranty options, or repair.
Click to expand...
Click to collapse
Normally I'd agree with that advice, but this literally and noticeably occured immediately after installing the latest security update. As a test, I've been running the battery down with videos, so long as I ensure I don't manually lock or turn the screen off, the battery has drained normally. No crashes or shutdowns while actively using the phone. Wireless charging works fine, and no visible swelling. Any other ideas? I joined the beta 12 program for the hell of it to see if that changes anything... Currently waiting for the push to my phone so I can download it.
Springcrime said:
So I have a similar problem after installing the latest security update... My phone pixel 4 xl was just fine prior, but now it will turn off randomly when the screen goes off (or is locked to turn the screen off). I can only turn the phone back on after I plug it in to a charger. Interestingly, the battery and phone will keep running and the battery will drain normally so long as I keep the screen/interaction active. Ideas? Thinking about flashing a custom ROM. This phone is stock and nothing has been done to it. I also reset to factory to see if that was the fix, but no joy. Help?
Click to expand...
Click to collapse
Try disabling the screen lock.
Double check all security settings.
As for all updates, if the OS is running fast and stable... leave it be.
Pie and above are pretty secure unless you do something stupid. As you can see a malware forced factory reset be less trouble than an update induced one. In 7 years of using mostly outdated android OS's never once did I need to do a factory reset because of malware.
My current Pie load is over a year old running fast and stable. It hasn't been updated in over 1.5 years... and it won't be.
It's impossible to get BH to install the latest ROM, and even I don't wanna judging from Google crappy OTA updates.
I only update for security not anything else though.
blackhawk said:
Try disabling the screen lock.
Double check all security settings.
As for all updates, if the OS is running fast and stable... leave it be.
Pie and above are pretty secure unless you do something stupid. As you can see a malware forced factory reset be less trouble than an update induced one. In 7 years of using mostly outdated android OS's never once did I need to do a factory reset because of malware.
My current Pie load is over a year old running fast and stable. It hasn't been updated in over 1.5 years... and it won't be.
Click to expand...
Click to collapse
So far so good on the screen lock. I wonder if it has anything to do with the facial recognition feature (which I enabled at the same time after the update). We'll see how this goes!
Springcrime said:
So far so good on the screen lock. I wonder if it has anything to do with the facial recognition feature (which I enabled at the same time after the update). We'll see how this goes!
Click to expand...
Click to collapse
Meh, play with it. Usually you'll figure out what's going on... they are complicated little devils.