Hey Xda'ers, I have this weird (and really frustrating ) problem with my Xperia Z, when it enters Deep Sleep mode, sometimes it won't come back (won't turn on the screen & wake up.) I keep tapping the status bar (got CM11 Nightly & tap to wake option enabled) and hitting the power button to wake up, but it never does, then it just reboots.
The only workaround i've found it's to implement a partial wakelock so the cpu keeps running even if the screen is off, but thats eating my battery away. I Bought the phone a month ago and since its arrive, has this problem, i know it's a software problem cause if it wasn't, then there would be no workaround like the cpu kept running all the time (or at least my noob brain figures that out ). it's been really frustrating. the most frustrating part is not finding ANYWHERE on the internet (not even here on XDA) any resemblance to the same problem im facing, they are all different kinds of rebooting problems, but not even one the same as mine, it means my problem it's really new or special, or i'm not looking up really well, anyways it's been so frustrating for me this month, cause i repeat, since it arrived it has this problem.
First i thought it was a Wifi Problem, cause it happens when i get a notification meanwhile is asleep (i've seen it happen more often but it happens with or without a notification too.) and the screen off; When i try to wake up to see the notification, the problem triggers and it wont wake up, so i installed "Advanced Wifi Lock" (I saw a thread with a similar problem but with an Xperia Pad of some girl on the Sony Mobile Forums, and one guy posted this solution as the only workaround he had found to the same problem.) and the problem was solved.
But then i realized that it was eating my battery, so i changed to "Wakelock Power Manager" (cause i read it was a lighter weigh solution than "Advanced WiFi Lock") and there, there is this option for the implementation of various degrees of wake lock, since i thought it was a wifi problem, i turned on the "WiFI_Mode_Hi_Perf" which is a wakelock that keeps the wifi running in a high performance mode even while in deep sleep, i thought this was a lighter solution to my problem, but then the deep sleep reboot problem started again :crying:. so i tried increasing the level of wakelock to a "Partial_Wake_Lock" which is a wakelock that keeps the CPU running even while the screen is off, but this wakelock won't let the phone enter in a deepsleep mode, so it's the "Advanced Wifi Lock" problem all over again. Battery Drain . And this pisses me off, cause my battery, that should have a more than 14 life hours, just have those with a 4-5 hours of screen on time with a mild use of whatsapp and facebook.
I don't know what to do, i've tried flashing other Stock Firmwares, 4.1, 4.2, 4.3, 4.4, reflashing the original (was a 4.1 "10.1.1.a.1.307 customized hk"),, rooting and flashing roms, and the problem persists. I left CM11 on cause i like it and i don't think it has anything to do with the rom or firmware cause i've tried so many already.
Finally, over a month of trials and reading and so, so, so, but SO much frustration, i come to you guys, i don't know what to do anymore, Please Help .
Just bumping with some screenshots with details about my phone, i guess it will be easier to solve the problem, if posible, somehow. Muy Xperia Z is a 6603 model btw.
Note: I set the minimun CPU frecuency to 486 because i had the weird "buzz" sound problem sometimes with whatsapp & messenger notifications, & found that solution here over the forums, anyways, the problem was there way before that change.
I ask for some help again developers, i didn't wanted to start a help thread before i did my research & exhausted all my options, but i've done everything i could, & still got no solution, hope the screenshots help .
Sent from my Xperia Z using XDA Free mobile app
I had the same thing, and mine was fixed with increasing my minimum CPU speed to 384. Runs like a dream now!
I know you'v said you've tried a whole load of different roms but have you tried any different kernels? Mine seemed to come up only when using certain kernels.
i had the CPU running on 384 since i bought it, i only recently changed cause of the buzz problem, & no, i haven't tried different kernels, only different roms, i don't know how to flash a kernel only.
What kernel do you have? & Just to be sure, you had the same rebooting problem when it went to deep sleep mode right?
Thanks for answering.
Sent from my Xperia Z using XDA Free mobile app
I haven't got a solution but get the same problem on the stock 4.4.2 kernel, intermittently between once a day and every other day, so I can live with it. As I recall the problem was more frequent until I got rid of a legacy app which put the phone to sleep when I shut the case, and was supposed to wake it up when the case was opened (which didn't always happen and about half the time I couldn't wake the screen with the on-button either, only reboot). It was a battery hog too. Running the CPU faster (up to 904??) didn't help, though.
mervluk said:
I haven't got a solution but get the same problem on the stock 4.4.2 kernel, intermittently between once a day and every other day, so I can live with it. As I recall the problem was more frequent until I got rid of a legacy app which put the phone to sleep when I shut the case, and was supposed to wake it up when the case was opened (which didn't always happen and about half the time I couldn't wake the screen with the on-button either, only reboot). It was a battery hog too. Running the CPU faster (up to 904??) didn't help, though.
Click to expand...
Click to collapse
With once a day or every other day i could live with it too, i guess it's worth to let the phone deep sleep and save more battery even tho it reboots once a day or sometimes none, the battery saving should be greater than the annoyance, i hope mine was like that, but as soon as i release the cpu wakelock & let the cpu get into deep sleep, the problem begins, i get like 10 reboots in a day, and if only the reboots just happened when i weren't looking, but no, they barely happen this way, it happens when i try to use it and i notice it won't wake up, it's a really weird problem, & i find it very weird that no one has it. (you two guys are the first that i know have this kind of problem, and still, it's slightly different, for the number of reboots at least.) although it's good to know finally someone has the same issues as me, though i don't have high hopes since you told me you haven't found a solution.
I wanna try flashing a different kernel as orangejuice43 said, but i don't know how, or any compatibility issues with the rom i have (CM11 Nightly), sides, i don't know which kernel would be good to try.
Thanks for answering!
Flashed succesfully "Lightning Kernel v. 8.0" for CM11, will test for a few hours or days hopefully, if reboot comes i'll notify you guys, so far this is the first "new" solution i try.
After less than two hours of flashing the "Lightning v. 8.0" Kernel and the partial wakelock off, the reboot problem happened again, no solution yet, and have the wakelock up again.
Anyone having the same issues? anyone with another suggestions or fixes? bummed down here .
Jorge Plascencia said:
After less than two hours of flashing the "Lightning v. 8.0" Kernel and the partial wakelock off, the reboot problem happened again, no solution yet, and have the wakelock up again.
Anyone having the same issues? anyone with another suggestions or fixes? bummed down here .
Click to expand...
Click to collapse
Flash another ROM...
TapaTalked from my Xperia™ Z (C660²) running Ultimate PureXZ Ultra!
That's a shame, I'm using lighning v8 and my problem is sorted. Sorry I can't be of much more help... lets hope a more knowledgeable person may be able to contribute for you.
Have you got an app like Trickster MOD installed to control the Kernel etc? might give you more of an insight as to what's going on. If you set a governor that keeps your Z from going into deep sleep it may be a bit better for your battery life than the wakelock solution...
This might help for information about Kernels
http://forum.xda-developers.com/galaxy-s2/general/ref-kernel-governors-modules-o-t1369817
Sorry for the late reply, i was on a trip so i couldn't actually test & give any feedback.
I downloaded Trickster Mod for my lightning kernel but all i could understand (after reading the post orange kindly shared.) was that every governor has this different settings that mod the cpu functionality & can be picked to adapt your own needs, i really doubt that any of them help with my problem, but as orange suggested, one may be a better choice compared to the wakelock fix i have used lately. i learned that since i flashed the lightning kernel, my governor was Interactive all this time, i really didn't noticed any battery drain or saving, i felt it just the about the same as before with the stock CM11 kernel.
a new question is, which kernel has the option or the setting for keeping the cpu awake? cause i didn't read any of them did this, or at least i didn't understood that any of them did this. anyways, that would be only another work around for the deep sleep reboot problem.
I though, read something interesting about frequencies and voltage of the cpu on the Thread, this:
Q. "Well i have set my favorite governor as screen-on governor and another one as screen-off governor. Why the hell is the phone not waking up after deep sleep. I need to force-restart the phone by pressing power button for about 10 secs. Is it a sleep-of-death?"
A. Yes it is. Do not use two governors as screen-on & screen-off govs, if they both have an upper frequency limit for screen-off state.
Didn't get it? Examples for Wrong combinations: (screen-on:screen-off):-
ondemandX:smartassV2
Examples for right combinations:-
ondemand:smartassV2, lulzactive:smartassV2
Click to expand...
Click to collapse
The Question resembles just exactly what my problem is, my phone enters into deep sleep and then it won't wake up, the only difference is that i don't have to force restart it, it just. when i try to wake it up, restarts itself, with no need of long pressing the power button, and sometimes, i just find that the phone is off, and then i do have to start it by long pressing the power button (plain old power on.), but that brings me another question, isn't that maybe the problem is on the frequency & voltage side of my CPU? maybe the stock kernel (not CM11, and for the matter CM11 too, cause the problem persists, even with lightning kernel...) came with a rare code line or something? i dunno, im just wondering, maybe it doesn't make sense, but its just that the question and problem stated there on the thread about governors and kernel settings, resembles very much what my problem is.
I hope someone can orient me about this or make a mental link with something (maybe) wrong about my kernel or phone, could it be hardware? :crying: . I don't know, maybe i should try another kernel? maybe i should go back to Stock ftf and try another kernel? any suggestions or long shots are apreciated.
Thanks for the replies, & sorry for all the descriptions and text, it maybe kind of boring -_-.
Adding another detail that i may have not mentioned, the problem NEVER happens while plugged in, (don't know if phone has a setting preventing deep sleep while plugged in, if it does, that may be the cause )
Update: just flashed AOKP ROM (jellybean 4.3 version) will test for a few hours or mins till the problem arises again... (lost all my Xposed modules & settings :crying: .)
Update 2: After less than 2 hours again, around the 1:30-1:45 hours time, reboot problem happened. getting sick of trying...
Update 3: Just flashed AOKP ROM (Kitkat 4.4 version). less than 15 min into the flash, reboot happened... help...
will flash Paranoid Android 4.4 Later.
Update 4: Flashed Paranoid Android 4.4, nearly 2 hours of deep sleep and 2:14 hours of total on time, reboot occured, was getting high hopes about this ROM, but as i said on my first post, i don't think it has anything to do with the ROM- Side note: PA is really cool, im sticking with it. and hoping anyone still answers with some fix or advice. thanks for reading.
Jorge Plascencia said:
Adding another detail that i may have not mentioned, the problem NEVER happens while plugged in, (don't know if phone has a setting preventing deep sleep while plugged in, if it does, that may be the cause )
Update: just flashed AOKP ROM (jellybean 4.3 version) will test for a few hours or mins till the problem arises again... (lost all my Xposed modules & settings :crying: .)
Update 2: After less than 2 hours again, around the 1:30-1:45 hours time, reboot problem happened. getting sick of trying...
Update 3: Just flashed AOKP ROM (Kitkat 4.4 version). less than 15 min into the flash, reboot happened... help...
will flash Paranoid Android 4.4 Later.
Update 4: Flashed Paranoid Android 4.4, nearly 2 hours of deep sleep and 2:14 hours of total on time, reboot occured, was getting high hopes about this ROM, but as i said on my first post, i don't think it has anything to do with the ROM- Side note: PA is really cool, im sticking with it. and hoping anyone still answers with some fix or advice. thanks for reading.
Click to expand...
Click to collapse
It's look like the battery is damaged or something...
TapaTalked from my Xperia™ Z (C660²) running Ultimate PureXZ Ultra!
androidfreak70 said:
It's look like the battery is damaged or something...
TapaTalked from my Xperia™ Z (C660²) running Ultimate PureXZ Ultra!
Click to expand...
Click to collapse
That sounds good cause the problem only happens when the phone is unplugged, but then again, what does it have to do with the CPU lock? the problem solves when i have a wakelock for the CPU, if the battery was damaged, probably it wont matter if the CPU is on or in deep sleep, it would just reboot randomly still, but that has never happened.
tldr: But CPU wakelock solves the rebooting problem, doesn't make sense.
Jorge Plascencia said:
That sounds good cause the problem only happens when the phone is unplugged, but then again, what does it have to do with the CPU lock? the problem solves when i have a wakelock for the CPU, if the battery was damaged, probably it wont matter if the CPU is on or in deep sleep, it would just reboot randomly still, but that has never happened.
tldr: But CPU wakelock solves the rebooting problem, doesn't make sense.
Click to expand...
Click to collapse
There is nothing called *CPU lock* wake lock is not preventing the phone from waking up.
Wake lock is the apps which wake the phone from the deep sleep mode. Like WhatsApp. When you get a message the phone will wake up from deep sleep.
You cannot lock the CPU.
Anyway. Your primary problem seems with the battery because many people reporting while they unplug the phone it will reboot or turn off. So changing the battery may help.
TapaTalked from my Xperia™ Z (C660²) running Ultimate PureXZ Ultra!
androidfreak70 said:
There is nothing called *CPU lock* wake lock is not preventing the phone from waking up.
Wake lock is the apps which wake the phone from the deep sleep mode. Like WhatsApp. When you get a message the phone will wake up from deep sleep.
You cannot lock the CPU.
Anyway. Your primary problem seems with the battery because many people reporting while they unplug the phone it will reboot or turn off. So changing the battery may help.
TapaTalked from my Xperia™ Z (C660²) running Ultimate PureXZ Ultra!
Click to expand...
Click to collapse
Yes i understand that's what "wakelock" means, what i meant, it's that i have this app called Wakelock Power Manager, and in that app, i got this "Partial_Wake_Lock" on, & that's the only way around i could find for the problem, on the description of this option it says "Ensures the CPU is running even if screen is off." so that's what i meant when i said i had a CPU lock or wakelock, sorry if i didn't made myself understand.
regarding your suggestion, i don't know, i don't wanna spend more money on a "maybe" solution, i've already spent quite a lot buying this phone, and had a bad experience trying other common solutions as replacing the sim card with a new one, didn't solved anything. i would like to be sure that is the problem before spending more bucks on this.
Thanks for the reply.
Jorge Plascencia said:
Yes i understand that's what "wakelock" means, what i meant, it's that i have this app called Wakelock Power Manager, and in that app, i got this "Partial_Wake_Lock" on, & that's the only way around i could find for the problem, on the description of this option it says "Ensures the CPU is running even if screen is off." so that's what i meant when i said i had a CPU lock or wakelock, sorry if i didn't made myself understand.
regarding your suggestion, i don't know, i don't wanna spend more money on a "maybe" solution, i've already spent quite a lot buying this phone, and had a bad experience trying other common solutions as replacing the sim card with a new one, didn't solved anything. i would like to be sure that is the problem before spending more bucks on this.
Thanks for the reply.
Click to expand...
Click to collapse
Well yeah that's right. I suggest you to wait for others. I may be wrong.
TapaTalked from my Xperia™ Z (C660²) running Ultimate PureXZ Ultra!
Jorge Plascencia said:
regarding your suggestion, i don't know, i don't wanna spend more money on a "maybe" solution, i've already spent quite a lot buying this phone, and had a bad experience trying other common solutions as replacing the sim card with a new one, didn't solved anything. i would like to be sure that is the problem before spending more bucks on this.
Thanks for the reply.
Click to expand...
Click to collapse
Just a thought: are you sure it's not a misbehaving app? I'd start with the obvious suspects, those that run in the background or make regular checks, and find tb's freeze facility invaluable; not least your Wakelock monitor, perhaps!
mervluk said:
Just a thought: are you sure it's not a misbehaving app? I'd start with the obvious suspects, those that run in the background or make regular checks, and find tb's freeze facility invaluable; not least your Wakelock monitor, perhaps!
Click to expand...
Click to collapse
About the misbehaving app, i really don't think so, as i said in my first post, the problem was already there 1 hour after unboxing, it could be a stock app, but im not sure how to 'find' it. and about the rest, sorry but i didn't understood could you be more clear (noobier) please? ha, thanks in advance!
Jorge Plascencia said:
About the misbehaving app, i really don't think so, as i said in my first post, the problem was already there 1 hour after unboxing, it could be a stock app, but im not sure how to 'find' it. and about the rest, sorry but i didn't understood could you be more clear (noobier) please? ha, thanks in advance!
Click to expand...
Click to collapse
If you are saying after 1 hour of unboxing so I think you need to talk with the seller. Maybe you will get another Z.
TapaTalked from my Xperia™ Z (C660²) running Ultimate PureXZ Ultra!
I noticed my battery was draining pretty quickly. I started looking and android system was the culprit. I drilled down further and system_server was using a lot of cpu time. Is this something I can adjust?
Sent from my SM-N910A using Tapatalk
I feel like that process could be a multiple of things and not just one simple thing you can tune or turn off. Have you tried using an app like wakelock detector(root) or cpu spy to try and narrow down the issue to perhaps a certain app causing the issue? Try out greenify to hibernate certain apps if you find them.
Otherwise I found this in another this in another post if that doesn't help you out that you could try...but I'd take and find the culprit first and foremost:
"Developer options > Background process limit > At most 4 processes"
I have wakelock detector installed. I will put cpu spy on.
After digging deeper in wakelock detector I found 2 apps with over 400 wakelocks each. The next closest was only 70. Facebook and Facebook messenger. They have been greenified till I decide whether i am going to uninstall then
Sent from my SM-N910A using Tapatalk
Any way to dig into System_Server?
Good day folks. I've also noticed System_Server severely draining the battery on my Galaxy S5 (2-3% per hour, when it's normally .75%/hour). In the past few weeks, the top Kernel Wakelocks and "Process" wake time (reported by BBS) have been System_Server, Time_Daemon (which I can't find ANY info about), and WakelockManagerTimeout (likewise - no useful info, literally only SIX results on Google). I've also seen "IPC_###_Event0" every now and then, where ### is a Process ID. When I check the PID via Terminal (Cat /proc/*PID*/cmdline) the PID ends up belonging to "System_Server".
To make a Windows comparison, it looks like System_Server is "RunDLL32" or "SVCHost", wherein, numerous processes can "hook" into "System_Server" and are thus disguised behind that process name. Is there anyway to dig deeper into "System_Server" to find the ACTUAL process/service that is causing all these wakelocks? I've also tried GSam Battery Monitor (thanks to - this post) and WLD (Wake Lock Detector) but the most granular any of them get is just "System_Server". As far as I can tell, this did not start as of newly installed software, but it could certainly be due to an update to an existing program. Whatever the cause, though, I need to find out, because a dead phone is useless
Merry Christmas, Happy Holidays
SolidSnakex128 said:
Good day folks. I've also noticed System_Server severely draining the battery on my Galaxy S5 (2-3% per hour, when it's normally .75%/hour). In the past few weeks, the top Kernel Wakelocks and "Process" wake time (reported by BBS) have been System_Server, Time_Daemon (which I can't find ANY info about), and WakelockManagerTimeout (likewise - no useful info, literally only SIX results on Google). I've also seen "IPC_###_Event0" every now and then, where ### is a Process ID. When I check the PID via Terminal (Cat /proc/*PID*/cmdline) the PID ends up belonging to "System_Server".
To make a Windows comparison, it looks like System_Server is "RunDLL32" or "SVCHost", wherein, numerous processes can "hook" into "System_Server" and are thus disguised behind that process name. Is there anyway to dig deeper into "System_Server" to find the ACTUAL process/service that is causing all these wakelocks? I've also tried GSam Battery Monitor (thanks to - this post) and WLD (Wake Lock Detector) but the most granular any of them get is just "System_Server". As far as I can tell, this did not start as of newly installed software, but it could certainly be due to an update to an existing program. Whatever the cause, though, I need to find out, because a dead phone is useless
Merry Christmas, Happy Holidays
Click to expand...
Click to collapse
Hi, i now it is a long time ago but i have the same problem with cm13 now. You find the culprit?
greets
bauita said:
Hi, i now it is a long time ago but i have the same problem with cm13 now. You find the culprit?
greets
Click to expand...
Click to collapse
Good day Bauita - Unfortunately, I didn't find the culprit programmatically. What I noticed, though, was that the drain only occurred while I was at the office, and I also noticed that my phone was frequently bouncing between the actual cell network and a network extender (identified by this: http://forums.androidcentral.com/verizon-samsung-galaxy-s4/307371-little-house-icon.html). I checked around and discovered that our IT department had been testing an extender and left it running accidentally - once they turned it off, my phone stuck with the regular Verizon network and it's been fine since.
So... in your case, you may need to discover a way to look inside System_Server, unfortunately. Good luck and please post back if you do (my apologies for not coming back when I figured it out on my end).
I'm sorry for bumping a ~2 year old topic, but from my googling, this one is the only one that has come closest to nailing this system_server problem. Everywhere you look, people are having the same issues (at least on the surface) but we're all scratching our heads with no apparent way to glean any additional information.
My phone (HTC One M8) has been driving me up the wall with this issue. A few things that I've noticed or think may contribute:
- I live in an area of poor-to-no signal (although my phone performs just as poorly in conditions with good signal)
- I have a terrible Netgear router at home that has this manufacturing defect where the signal is exceptionally weak (but again, the problem persists elsewhere)
- The problem displays on and off, but if my phone has been on for more than a couple of days, it shows up more frequently.
- If I'm in a car (riding as passenger of course), I believe I've noticed my phone lagging more often if I leave the WiFi on and allow it to try and connect to open hotspots as they fly by.
The problem for me specifically shows as heavy lagging in display and input. Even pressing the power button, the screen may not turn off until whatever extremely important thing this is has finished. Interestingly, using my phone right now and listening to music, I've noticed that the music somehow keeps playing despite the lag, as if it's given priority even over input?
But I'd like to look at the internals a little deeper here. According to Systempanel, system_server is the lowest-level process running in the Android VM. My hope is that would make this easier to debug, however as it was pointed out earlier, the exact problem could still really be anything. I'll try to study up more on debugging and see if I can maybe crack this, and even make an app/library to aid other frustrated users.
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