Database Info

[Q] TF101 Screen won't turn on

Hi everyone, this is my first post here. Thanks in advance for any help that you folks can provide.
I've had the TF101 for about six months now, and it's been fine. I was using it yesterday on the train and all was good, but when I got home and took it out of my bag it didn't seem to start up. I thought it might have been a battery issue, so I let it charge overnight. Tried starting it up this morning and I got the same results. So I started looking in to other issues.
The tablet is definitely starting, adb will recognize it in its list of devices, and if I plug it in to my tv or desktop monitor w/ HDMI, I can see and interact w/ the Transformer UI (of course this is kind of painful since I have to do some guessing about where to put my fingers).
I had rooted it using rebound821's scripts and directions here, so tried an unroot to see if that was the problem. I ended up with the same results.
Does anyone here have any insights as to what the problem may be? I'm hoping to avoid sending it back to ASUS, so I'm fine w/ opening it up to look for loose cables.

So I thought that brightness might be the problem. Maybe it was set to 0 and I just wasn't seeing anything on my screen. Sadly, that doesn't seem to be the case.
I tried setting brightness at the path below to to 0, 50, 100.
/sys/devices/platform/pwm-backlight/backlight/pwm-backlight/brightness
Still no luck.
Has anyone encountered anything remotely similar to this (even if similar is just a dead screen)?

There have been others with dead screens reporting what you are, at least I have read a few reports, I think they just had to get them RMA'd, I don't recall anyone 'fixing' a dead screen, especially if you still have adb and touch working then the screen itself and backlight seem to have broken completely- some have reported the backlight dying and thinking the screen was broken, but it was just the backlight (I guess in bright light they could see pixels working, but couldn't make out what was on the screen without the backlight). I still think they had to get it repaired either by Asus or by someone who was capable of doing internal repairs with replacement parts..sorry for your luck

Looks like I'll have to send it back. I took it into the brightest light I could find and couldn't see anything at all. Guess it's the screen and maybe the backlight too. I'm pretty disappointed this happened, the only thing I can think of is that the bag I had it in was hanging from the chair in front of me on the train and it was swaying a little, and that shouldn't be enough to dislodge a connection. Either that or just some freak hardware failure. Still, I guess it's not that common of an occurrence. Thanks for the reply, I'll slink off and try to get in touch w/ Asus now.

I have experience same
My TF101 broke in the same way, screen blank. Conected to tv I`ve got image digital touch work. I shut down my TF101 normaly and screen never go back to live again. Tablet was in a protective bag (when I trave by car), just no reason for not working ( no problem at screen, previously, screen perfect - no dead pixels)

Did you guys get this resolved? I had the EXACT same thing happen yesterday. Was working just fine. Put it in its sleeve, into a protective case, into a briefcase, got home and dead.
HDMI works. I tried to call Asus but they say i'm out of warranty.
Thanks in advance.

Must be something wrong with the connections that it decays over time. I've had mine since October last year and its been fine except for today when I brought it home it wouldn't work.
I was able to fix it though. I held it vertically with the bottom edge down and tapped it firmly on my desk a couple of times. The screen came back on. There is a strong possibility that this will happen again and my tap fix won't work, but it's working at the moment

Asus Transformer screen
elementalfire23 said:
Must be something wrong with the connections that it decays over time. I've had mine since October last year and its been fine except for today when I brought it home it wouldn't work.
I was able to fix it though. I held it vertically with the bottom edge down and tapped it firmly on my desk a couple of times. The screen came back on. There is a strong possibility that this will happen again and my tap fix won't work, but it's working at the moment
Click to expand...
Click to collapse
I had exactly the same problem discussed in this thread. I was also able to bring the screen of my TF101G to life by tapping it firmly on my desk with the bottom edge. It works for now. But it is certainly disconcerting to know that some connection in this rather expensive gadget are loose and all this can happen again. I guess I will not carry my transformer around any more - just leave it at home...

spokey said:
My TF101 broke in the same way, screen blank. Conected to tv I`ve got image digital touch work. I shut down my TF101 normaly and screen never go back to live again. Tablet was in a protective bag (when I trave by car), just no reason for not working ( no problem at screen, previously, screen perfect - no dead pixels)
Click to expand...
Click to collapse
Same problem here had my unlocked bootloader tf101 for awhile now, one of the first ones out... had a great life gave it to my girl when i got the transformer prime and the screen just went out yesterday, still goes in apx mode and still recognized by computer, screen just straight up died, think it's too late for a manufacture warranty, maybe ill look but think it's gonna be no dice... sucks obviously something in the design to make this happen to so many of them...

My TF101 appears to have a dead screen. I am rooted and running Revolver Custom Rom. When connected to my pc, I am able to recognize my device. My screen will not turn on so I cannot use recovery to go back to stock. I am set up to use ADB, however, I am not very knowledgable with ADB. I am convinced I have a bad screen and I am still under warranty. Is there a way to return the TF101 back to stock using ADB? If anyone can point me in the right direction, I can probably figure it out. Otherwise, I may just try and replace my screen and see how that works out. Thanks for the help.

My backlight died on Tuesday. Similar situation of working in the morning, headed into work with it in my bag, no brutal knocks or anything but one jolt just must of finished it off after a year and 2 weeks abuse (yes 2 weeks out of warrenty).
Going to attempt to take it apart this afternoon and play with the ribbon cable as reseating it has solved quite a few peoples problems.

Woo! It worked! Very happy chappy.
Sent from my SK17i using Tapatalk 2

Same thing happened too me, first time i sent it to service, but last time i opened it myself and pushed the connector for the screen thightly in place.. worked nicely
Sent from my Transformer TF101 using xda app-developers app

Screen goes derp
I don't know if I have the same problem or not.
Backstory: I own a Transformer TF101 that I got for my birthday from my girlfriend. It was meant for travel and bs'ing around at home. Took it into work and quickly realized that I could use this for work. That went over so well that the rest of the office became intrigued. Once these came on sale on groupon, the office manager went all in on 10. These are all refurbished transformers with docks.
They have all been handed out and I now have a transformer for home and work. Kind of nice...but I do a lot of site observation so using my personal transformer was a risk that I had to take all on my own (survived a 5' fall off of a parapet wall already).
The problem: From the first 5 minutes that I had the thing, the transformer screen went blank. I opened up google play to download a few apps that I could use for work. Scrolling down I saw some choppyness which I considered the processor/memory having issues loading everything on the screen. Before I knew it - boom blank screen. Rebooted and the loading screen stays on for 2 seconds before the screen goes blank. I can tell it's working because it plays a sound at start up. I can also tell the screen is lit up (it's like it's showing a grey screen because it can't show true black colors). If I hit the power button again it goes completely black. I hit the power button again and the screen flashes to the lock screen and immediately goes blank again. I could do this over and over and over again.
Anybody having the same problem? It's refurbished....I'm guessing apparently I got the dud.

I ran into pretty much the same problem. One morning, the tablet screen would just not turn on. Sometimes, it came on and immediately shutdown, but it is still on the "On" mode. Hit the power button again will bring it to the off mode. Toggle it one more time, sometimes, will turn on the screen a off again. I was able to get it back to work with a factory restore. However, it has the following problems.
1) As soon as I adjust the brightness, the screen will go off again. And there is nothing I can do to bring it back except another factory restore.
2) The screen will flicker (and sometimes produces some clicking sound) when charging with the screen on.

Looks like my TF101 is having same issue, screen gone off suddenly (hdmi shows up in TV fine)...I am going give a try on reseating the cable hoping it resolves the issue.
leonpr, is there some tips/things I have to make sure before attempting this. I found a guide here and another youtube video on this issue as a reference...
Thanks..

Screen won't turn on unless factory reset "fix"
My girlfriend has an ASUS TF101. If the brightness goes up to 60%, the screen is blanked (no backlight either) and the only way to get it to turn back on again is to hard reset. This coincidentally happened at the same time as an update from ASUS. After lots of Googling it does not appear to be related. I was hoping it was and installed several custom ROMS which all experienced the same issue.
As a temporary work around, until I get the guts & the money to be able to replace her tablet if I break it, I found and installed AutomateIt. I set a trigger so that when the screen is turned off, the brightness is set to 50%.
Why trigger when the screen is off instead of when the screen hits above 59%? If you have this same problem, hold the brightness and go all the way until the screen blanks and then still holding your finger on the screen, move it all the way to the left and you will notice that the screen did not come back on. Press the power button once to turn it off and then again to turn it on and you will see the screen at the lowest brightness setting.
So, with the trigger in place, if you accidentally (or one of your rotten kids intentionally:angel raises the brightness above the threshold, simply press the power once to turn off the screen and then press it again to turn the screen on.
Just a note, I ended up installing AutomateIt Pro, Available for $1.60 from the Play Market. The free version works fine, but my girlfriend has been struggling with this issue for a couple of months and after so many hard resets, the little app is more than worth the money.

Have you tried Power + Volume Down for 15 seconds, and then leaving it alone for one minute? It will cold boot. Try that and it may work. Just saying; Hope it will help

Sorry for the necro-bump but here's the actual solution.
Problem: The video cable inside the Transformer comes loose and just needs to be pushed back in.
I can't post a link since I don't have 10 posts yet so just search youtube for the following key words:
blank or no display issue on the asus transformer - fix
The user who posted the video is DoCWaSaBe

Tokyudo said:
Sorry for the necro-bump but here's the actual solution.
Problem: The video cable inside the Transformer comes loose and just needs to be pushed back in.
I can't post a link since I don't have 10 posts yet so just search youtube for the following key words:
blank or no display issue on the asus transformer - fix
The user who posted the video is DoCWaSaBe
Click to expand...
Click to collapse
Just fixed my blank display problem on a TF101 which is well out of warranty. Here is the link. I found the connector loose after dropping my TF101.
Thanks!
Fix lasted for a few days, now backlight dead, tried all cables again. No joy . I hate intermittent faults so ordered a Samsung Galaxy TabPRO 10.1.

[Q] screen disaster - random tinting, solarization, turns upside down

sooo, yeah. my wife has the t959v. the screen cracked months ago, replaced it with one from ebay, works fine. a few weeks ago, it was involved in an accident and needed yet another screen replacement; ergo, back to ebay i go. installed the new screen yesterday, turn it on, all is well. for a bit.
now, the phone isn't currently, nor has it ever been rooted; pure stock tmo us 2.3.6. during boot, the splash screens and boot animation are gorgeous and perfect in appearance. the recovery menu is exactly as expected. android boots as you'd want it to, and then the display will do one of the following:
-work properly (rare)
-automatically turn off, capacitive buttons still lit, touchscreen unresponsive - turning it "off" darkens the cap buttons, turning it back on flashes the screen on for a half-second, then off, with cap buttons still lit (common)
-graphical corruption ("solarized" colors, completely wrong colors, pixel vomit in essence) (fairly common)
-screen tinting, blue most often, followed by pale yellow, then greenish, then red (almost constant)
-screen inversion - the display will show as rotated 180 degrees; grabbing a framecap in ddms shows it right way up. touches are also inverse; you have to touch where the onscreen element would be if it were displayed properly instead of where the element is; e.g. a button on lower-left will display in the upper right, upsidedown, but the screen registers the button when you touch the lower-left portion of the screen. (quasi common, equally infuriating and hilarious)
none of these problems will show up in a screenshot at all.
i can reliably reproduce any of the above by simply adjusting the screen brightness. this will, quite literally, cycle through every possible defective display mode randomly for a split-second before moving on to a different one as long as you move the brightness slider.
MOST of these issues are transient and are either fixed (temporarily) or replaced with a different listed issue if you lock/unlock the display. it feels like a hardware issue what with the solarizing and color horrors, but is acting like a software issue, considering that recovery and boot are perfect and have never displayed any of these issues. i tried gently flexing and stressing the case in areas that might be a weak connection point, but can't get it to bug out that way.
in no way am i suggesting that i didn't screw something royally in the reconstruction stage, but i tore down and rebuilt that phone 4 times with identical results, so i can guarantee it's not some loose ribbon connector or zif socket.
i beg of you, great minds of xda, what the balls did i muck up this time? any hope for a fix? are there different panels, drivers, something?
thanks in advance

OK, if your screenshots appear normal, then your phone appears to be working correctly!
or at least it thinks it is we can conclude that it isn't the rom, kernel, or anything that you can blame the phone for going screwy.
Try buying another screen??
The ribbon connector might be broken?

yeah, these were what i figured what my options were. it just seems odd that the boot process and recovery menus have error-free displays while only the full android os doesnt. oh well, i'll probably just have to make a stink about it on ebay or something.
thanks for reading

You might try a fresh flash before getting a new screen to see if it is indeed a hardware issue. If you want to try that follow the second link in my signature. You will not need to flash bootloaders since you are currently on KJ6.

lumin30 said:
You might try a fresh flash before getting a new screen to see if it is indeed a hardware issue. If you want to try that follow the second link in my signature. You will not need to flash bootloaders since you are currently on KJ6.
Click to expand...
Click to collapse
hell, warranty's void at this point anyway, right? may as well thanks much!

welp, all went well, screen was perfect through the whole heimdall/recovery process, but the problems still exist in the os c'est la vie. at least my wife's phone is finally rooted, i suppose. thanks anyway!

Have you tried opening it back up and reconnecting?

yup, 4 times, but i guess one more wont hurt
[edit]
it definitely seems to be related (if not related, exacerbated by) changes to screen brightness. turning off autobrightness has helped minimize the issue, but it still presents itself semi-often during screen-off/on events. obviously nothing useful in logcat.

zero01101 said:
it definitely seems to be related (if not related, exacerbated by) changes to screen brightness. turning off autobrightness has helped minimize the issue, but it still presents itself semi-often during screen-off/on events. obviously nothing useful in logcat.
Click to expand...
Click to collapse
That's interesting and could very well be a hardware problem with the screen. You wouldn't see that in recovery as the OS isn't loaded to mess with the brightness in that mode.
Does it do it on-demand if you mess with the brightness slider?

stephen_w said:
Does it do it on-demand if you mess with the brightness slider?
Click to expand...
Click to collapse
you better believe it does. rapid fire cycles through every color until it can't take it anymore and turns off. if i take/refresh a screenshot through ddms and poke blindly at the screen at that point, it'll still take input which is a curious, difficult game to say the least.

zero01101 said:
you better believe it does. rapid fire cycles through every color until it can't take it anymore and turns off. if i take/refresh a screenshot through ddms and poke blindly at the screen at that point, it'll still take input which is a curious, difficult game to say the least.
Click to expand...
Click to collapse
It's that Pink Floyd screen. You're supposed to drop acid & watch the wall when that's going on. LOL j/j
Given that you're on a fresh ROM & the problem persists, I'm leaning toward a hardware issue man. Sorry.

stephen_w said:
It's that Pink Floyd screen. You're supposed to drop acid & watch the wall when that's going on. LOL j/j
Given that you're on a fresh ROM & the problem persists, I'm leaning toward a hardware issue man. Sorry.
Click to expand...
Click to collapse
as fun as that sounds, unfortunately i bet i'll end up just getting my wife a used phone on ebay or somewhere similar and using this one as a development monkey. i was assuming that it wasn't something i could fix but hoping otherwise... yeah, that worked out

I just started having this problem. It wasn't too bad at first, just the color changes, but then it started not showing a screen at all. Changed to three different roms, even back to the stock non-rooted KJ6 and gave up. Keeping it on a steady brightness is the only way to minimize the color changing. I thought your thread had a solution but...
I may try opening it up and fixing the ribbon. But otherwise I'll keep using it as long as I can tolerate it until an S3 or a new Nexus.

kristoper said:
I just started having this problem. It wasn't too bad at first, just the color changes, but then it started not showing a screen at all. Changed to three different roms, even back to the stock non-rooted KJ6 and gave up. Keeping it on a steady brightness is the only way to minimize the color changing. I thought your thread had a solution but...
I may try opening it up and fixing the ribbon. But otherwise I'll keep using it as long as I can tolerate it until an S3 or a new Nexus.
Click to expand...
Click to collapse
nawp, nothing even close to a solution here i did end up buying my wife a whole new replacement phone and turned the broken one into my api10 development device. for what it's worth, yeah, autobrightness off does help a bit for when the phone is actively displaying content, but after you put it to sleep/screen off and try to turn it back on, it's a crapshoot. for a few horrifying hours, the screen was upsidedown even in recovery/boot animation and would NOT flip back to right-side-up until i ran the battery completely flat.
is no fun, 'tis truth. sorry for your troubles.

Pixel randomly locks while in use, even in safe mode.

A few weeks after I got my Pixel I started experiencing random screen locks while I'm holding and using the phone.
I have it set to Auto lock after 1 minute of activity but this can happen sometimes immediately after unlocking with the finger print scanner. Ive only noticed it happening while on my hour train commute but that could just be because that's where I'm using it the most consistently.
I talked to Google support via chat and they suggested booting into safe mode to see if it's a third party app causing the issue. Ive currently been using safe mode for an hour and it has happened but only once when it first rebooted.
Has anyone else experienced this? I've contacted Google support again and will update if they find anything.
Thanks

I have experienced this several times. I can't pinpoint what's causing it. I'm just glad someone else is seeing this happen as well. Hopefully someone gets to the bottom of it.

I use an app "Always On" which has a "timeout" feature.
The app uses AMOLED ambient display to put a clock and notifications on the screen.
I use it when going to bed or at night. The timeout feature uses Device Administrator access and causes the screen to go fully off after a while. Sometimes the app causes the Devices Administrator requires password "error," definitely.
I will test more and report, but earlier in week I noticed screen go off as you describe, as I've noticed now and again too, and I realized it was maybe exactly 3 hours since I freshly set a 3 hr timeout in Always On. At that point I was using my phone when the device locked.
Hmm.
Sent from my sailfish using XDA Labs

wilsonic said:
A few weeks after I got my Pixel I started experiencing random screen locks while I'm holding and using the phone.
I have it set to Auto lock after 1 minute of activity but this can happen sometimes immediately after unlocking with the finger print scanner. Ive only noticed it happening while on my hour train commute but that could just be because that's where I'm using it the most consistently.
I talked to Google support via chat and they suggested booting into safe mode to see if it's a third party app causing the issue. Ive currently been using safe mode for an hour and it has happened but only once when it first rebooted.
Has anyone else experienced this? I've contacted Google support again and will update if they find anything.
Thanks
Click to expand...
Click to collapse
Maybe a magnet causing interference? http://www.androidheadlines.com/2016/11/the-google-pixel-and-pixel-xls-screens-react-to-magnets.html

tejasm1 said:
Maybe a magnet causing interference?
Click to expand...
Click to collapse
OMG you just blew my mind. This is definitely what it is. When I'm sitting on the train I have my satchel on my lap which has magnetic clasps. I'll remember to keep it away from there in future. THANK YOU SO MUCH! :good:

I know this is an old thready but this blew my mind too! I think my juul is causing it, as it has a magnet on the end to snap to the charger. Never would've put two and two together. Thank you!

P4xl - Same random screen locking symptoms, NOT MAGNET related.
All of the responses in this describe the symptoms of the problem I have with my Pixel4xl, but not the description of the cause.
I most DEFINITELY do not have any magnets within any proximity to my phone.
It only has an Otterbox case, and will often lock when being actively used, while behind held at least 6" from any other object (except my hands).
Is anyone else experiencing this (non-magnet related issue)?

djdole said:
All of the responses in this describe the symptoms of the problem I have with my Pixel4xl, but not the description of the cause.
I most DEFINITELY do not have any magnets within any proximity to my phone.
It only has an Otterbox case, and will often lock when being actively used, while behind held at least 6" from any other object (except my hands).
Is anyone else experiencing this (non-magnet related issue)?
Click to expand...
Click to collapse
Yes I have the same issue where the phone locks itself randomly on 4XL. No idea what's going on I have a fabric case... Very annoying it happens all the time

I also have the same issue on the Pixel 4. No case, I'm sitting on my couch, no magnet within 6 feet, no electronics other than a remote control, yet my phone just sometimes locks.

Yes I'm facing this issue on my Pixel 2 as well, and no magnets near me!! Can someone Please help?

Hey guys make sure your buttons arent stuck to the frame

It's happening to me too on my pixel 4 xl. Did anyone determine a cause?

Same issue, no case on it or any magnet nearby. It's super annoying.

I had the same issue on my Pixel XL. Didn't think twice about it since it was an older phone, probably a bug with new os/old phone. But i just upgraded to the Pixel 4a and the same thing is happening! Is it related to smart unlock? The weather? Mars in retrograde?

djared704 said:
Hey guys make sure your buttons arent stuck to the frame
Click to expand...
Click to collapse
Definitely not the cause for me.
In my Otterbox case, when pressed, the volume buttons cause the volume interface to appear (which isn't happening),
and the power button has a distinct click when pressed (and when held, activates the nfc card payment interface).
A good guess, but unfortunately isn't the cause, in my situation. ??

Mate 9 Calibration

Has an had any issues with screen calibration? Sometimes when I click on the screen it presses to the left of it. When I'm in the recents screen for my apps, it sometimes swipes away instead of selecting it, and I'm unable to consistently unlock the phone while it is charging. (Works like once in every 5 times) however, I'm on sure if that one is related.
Anyone have any ideas?

Which firmware are you on? I remember older firmwares were having a bit of a touch sensitivity isues.

Sammath said:
Which firmware are you on? I remember older firmwares were having a bit of a touch sensitivity isues.
Click to expand...
Click to collapse
I'm on MHA-L29C567B183. US version of the phone. Stock

Did you install a screen protector? Could be the reason for sensitivity issues. If not, I don't know. Maybe a factory reset Will help?

Sammath said:
Did you install a screen protector? Could be the reason for sensitivity issues. If not, I don't know. Maybe a factory reset Will help?
Click to expand...
Click to collapse
I removed the screen protector when I purchased it. I could do a factoru reset and see how it goes. Hopefully it's software related and not hardware related.

I do hope so as well then. I do have to say that the factory installed screen protector doesn't do this screen justice.

Sammath said:
I do hope so as well then. I do have to say that the factory installed screen protector doesn't do this screen justice.
Click to expand...
Click to collapse
I thought it was for protecting it in the box?
Mine had a lot of air bubbles in it so removed it right away.
My charger still has the plastic on it though xD

ante0 said:
I thought it was for protecting it in the box?
Mine had a lot of air bubbles in it so removed it right away.
My charger still has the plastic on it though xD
Click to expand...
Click to collapse
Lol, no, this phone comes with a screen protector pre installed .

The touch sensitity is definitely off a little. I have to swipe the notification bar sometimes twice for it to come down. I also get some missed taps but it's infrequent enough that it isn't a problem for me. I heard they started fixing touch latency and optimization in 5.1. Don't know if we will ever see it.

If you are not using the stock charger weird things can happen.

Alrighty update: Factory settings still yields the same results. It's not frequent enough to make me go crazy, but it's still roughly the same. I guess my real pet peeve is when I need to go to the app manager to return to an open app and it just closes out. I've lost a lot of information that way like recipes when cooking and etc.
What I really don't understand is the fingerprint sensor not working while it's charging. It doesn't matter what charger I use. It just doesn't respond most of the time (Sometimes it unlocks like it's suppose to)

Im using Quick Charger from SS and I have this problem too. It's nice to know this is a common issue, not only me. I dont have any issues with fingerprint when charging, just notice when the battery between 5-60% it's insensitive for me (maybe quick charge is working strongly in this range), "insensitive" here means when you press and hold any things on the screen, it'll "tap" it and open it instead, all pressing or sliding or zooming actions are normal, just dragging has issue. When the battery is 70% and above, it becomes normal and no more insensitive touch. Just that so I think I can bear this thing.

Xz premium freezing and resetting when i unlock it. Also no volume up, related?

Hey Guys so i have searched high and low for a solution and still can't figure out a fix. i've read on sony forums that other people experienced the same issue but can't find a fix. I got the phone second hand (risky i know but i took a gamble) and it already have android pie. At first it was working great and i was quite happy with the phone but as i started using it every now and then it would reset itself at random, even in my pocket, then it started freezing when i unlocked it and eventually reset and work again for a bit. from the start the volume up button was not working but i can deal with that. on other threads i have read that some people are having the exact same issue. Help is very much appreciated.
So far i've tried turning off fingerprint unlock, uninstalling apps, turning off auto brightness, turning off the code unlock, factory reset, flashing to android oreo, and running in safe mode and so far none of that has fixed the issue. (although it helped temporarily giving me false hope!)
i'm going to try flashing back to nougat as a last resort but am not going to have too much false hope. Thanks for reading and any help in advance!

leemo89 said:
Hey Guys so i have searched high and low for a solution and still can't figure out a fix. i've read on sony forums that other people experienced the same issue but can't find a fix. I got the phone second hand (risky i know but i took a gamble) and it already have android pie. At first it was working great and i was quite happy with the phone but as i started using it every now and then it would reset itself at random, even in my pocket, then it started freezing when i unlocked it and eventually reset and work again for a bit. from the start the volume up button was not working but i can deal with that. on other threads i have read that some people are having the exact same issue. Help is very much appreciated.
So far i've tried turning off fingerprint unlock, uninstalling apps, turning off auto brightness, turning off the code unlock, factory reset, flashing to android oreo, and running in safe mode and so far none of that has fixed the issue. (although it helped temporarily giving me false hope!)
i'm going to try flashing back to nougat as a last resort but am not going to have too much false hope. Thanks for reading and any help in advance!
Click to expand...
Click to collapse
You pretty much ruled out a software issue by reverting back to Oreo and all that.
Volume rocker isn't something that just fails on these phones, so that's suspicious to me.
In most cases freezing/rebooting is caused by a faulty current supply (battery) and distribution (conectors, cables, capacitors...), if the software issue is ruled out. Faulty screen, screen connector and cable can cause freezes, the phone itself doesn't freeze up, but the image on the screen does, so it looks like the entire phone freezed, but it didn't, just the screen. Again, this as well can be caused by bad power delivery to the screen.
I would take it apart, take a closer look at the board, connectors, possible corrosion and dirt on capacitors, and replace the battery since it probably hasn't been replaced ever, and it's now a fairly old phone, and second hand, god knows how was it charged and treated in general.
If you never opened a phone before, I wouldn't suggest you start with this one, it's not really "novice friendly". Take it to someone who does board level repairs.
My best bet would be the phone was opened and some service has been done on it, but not properly+bad battery/battery connection.
Volume rocker is very easy to mess up, if you don't reseat it well it can fail to register pushing the button.
There really isn't a simple straightforward answer to you issue, if the software is 100% ruled out, the board and battery needs to be checked out, specially if the phone was opened before.

Atrax2010 said:
You pretty much ruled out a software issue by reverting back to Oreo and all that.
Volume rocker isn't something that just fails on these phones, so that's suspicious to me.
In most cases freezing/rebooting is caused by a faulty current supply (battery) and distribution (conectors, cables, capacitors...), if the software issue is ruled out. Faulty screen, screen connector and cable can cause freezes, the phone itself doesn't freeze up, but the image on the screen does, so it looks like the entire phone freezed, but it didn't, just the screen. Again, this as well can be caused by bad power delivery to the screen.
I would take it apart, take a closer look at the board, connectors, possible corrosion and dirt on capacitors, and replace the battery since it probably hasn't been replaced ever, and it's now a fairly old phone, and second hand, god knows how was it charged and treated in general.
If you never opened a phone before, I wouldn't suggest you start with this one, it's not really "novice friendly". Take it to someone who does board level repairs.
My best bet would be the phone was opened and some service has been done on it, but not properly+bad battery/battery connection.
Volume rocker is very easy to mess up, if you don't reseat it well it can fail to register pushing the button.
There really isn't a simple straightforward answer to you issue, if the software is 100% ruled out, the board and battery needs to be checked out, specially if the phone was opened before.
Click to expand...
Click to collapse
Thanks for the comprehensive reply, so would system ui not responding also be due to the hardware? I just thought it was strange that some other people had posted pretty much the exact same issues.. I'll start looking around for someone to pull it apart for me. I've done some screen repairs on one phones but I'm not willing to screw this one up so I'll find an expert!

leemo89 said:
Thanks for the comprehensive reply, so would system ui not responding also be due to the hardware? I just thought it was strange that some other people had posted pretty much the exact same issues.. I'll start looking around for someone to pull it apart for me. I've done some screen repairs on one phones but I'm not willing to screw this one up so I'll find an expert!
Click to expand...
Click to collapse
Ofcoruse, mostly power delivery. If for example the cpu or the screen isn't getting correct voltage and power, it can missbehave or freeze up as a failsafe to prevent damage.
As I said, I would take a look at the board, and change the battery with a known good one, since I have spares lying arround, to eliminate that variable as well as software.
I presume you're not rooted and you're troubleshooting using oem firmwares. If not, all bets are off.
A faulty battery can be a culprit of many issues that look like software/ui issues, but they're not.
Make a full software repair with latest official version, if it fixes nothing, it's a hardware issue.

Atrax2010 said:
Ofcoruse, mostly power delivery. If for example the cpu or the screen isn't getting correct voltage and power, it can missbehave or freeze up as a failsafe to prevent damage.
As I said, I would take a look at the board, and change the battery with a known good one, since I have spares lying arround, to eliminate that variable as well as software.
I presume you're not rooted and you're troubleshooting using oem firmwares. If not, all bets are off.
A faulty battery can be a culprit of many issues that look like software/ui issues, but they're not.
Make a full software repair with latest official version, if it fixes nothing, it's a hardware issue.
Click to expand...
Click to collapse
Thanks very much, I'll give that a go first!
If it fails where and you are close to me (Melbourne Aus) how would you like a project?

I share with you my personal experience.
The phone is amazing, is very fast, efficient, amazing sound, amazing screen.
I have the same problem with the volume up bottom but in my case it was caused for a fall incident, I took it apart and I discovered there is one flex connector that goes from the mother board and is shared with the volume bottoms, the power- fingerprint sensor, the camera bottom, the lower speaker and the lower microphone.
In fact due to that fall I am having problems with the volume up bottom as I wrote, the lower microphone, the lower speaker and sometimes the fingerprint function does not work.
I think is still worth having the cel phone, I`ll search for the flex to fix it up
I think most of the description Zagreb does of your case can be adjusted to the reality of what is happening, I think is necessary a technical checking of the hardware.

I'M sorry, of course I meant buttons and not bottoms!

Freezing, unresponsive ui and volume buttons not working properly.
I've had this same issue for a few weeks tried hard resets safe mode, etc, nothing helped. So after much frustration searching forums to no avail I set to and tried a deeper investigation into my own device, I accessed the dev options and looked at power hungry services. The most hungry was Xperia home so I stopped it and low and behold my phone hasn't locked up since, still volume buttons are mostly not working but I'm not locked out any more.

Same here,
First randomly reboot, after factory reset randomly system UI failed constantly , very annoying.
Indeed button up volume is not working (properly).
Someone found solution for this? I already purchased a new battery.
@Chernob0g : how you disabled/stopped Xperia Home so I in meantime can use my phone.

Replaced battery, looks better now.
Volume up still not working, but freezing looks solved.