Alright, guys; I need some help. I previously had the classic all to well known problem with my digitizer, where I was missing about a half inch of touch input on my screen. I had gotten used to just rotating it to type, cause I was out of warranty, and I'm upgrading soon.However, more recently, I have developed a much bigger problem. My touch screen no longer works, AT ALL.
The issue first started when I attempted to install "Someone's ROM" with "That libs". I got screen fade-out that some other users reported, so I pulled the battery and flashed back to my EPinter's CM10 backup. After it had booted, I went to unlock the screen, and NOTHIN'. Not registering any presses or swipes what so ever. I then went into recovery and cleared everything, still nothing. Hooked it up to my PC, ran a FULL wipe (OS included), and flashed a fuitcake. After booting; still no touch screen. A helpful member of this forum suggested I try the PDS fix, so I did. Still left with the same result.
So, my question is... Is there any way that someone MUCH smarter than I can look at some type of statistic I can pull from my phone to see if there's a software problem causing this issue? And if so, is there any way I can retrieve said info with out being able to use the phone it's self? I really don't want to go the next 2 weeks with a flip phone. heh.
EDIT: If anyone can figure this out and get it fixed, I would be more than happy to donate.
Mast likely your digitizer is just broken!
Happens quite a lot on that phone.
They are not that expensive! (see for example http://www.amazon.com/Motorola-Screen-Digitizer-Replace-broken/dp/B004Z0UO8O)
If you can't change it yourself see if you find someone to do it.
Yup. Sounds more like a hardware issue since you already did all recommended procedures.
Sent from that Atrix.
Yeah, I figured as much. Just hard to accept that it's finally completely gone out on me. Especially since it happened at the exact second I tried flashing experimental, untested firmware. I am aware of how simple a digitizer replacement would be, but I don't want to spend $40 on a new one, when I'm about to dump another $300 into a new phone in two weeks, ya know?
To keep things simple, I had a cracked screen on the Ultra which was replaced last week. However now the phone screen is slow and unresponsive after about a minute of use (fast & like new after right turning on however).
Ive tried the mod tweak found here http://forum.xda-developers.com/showthread.php?t=2522657
As well as the thermal screen calibration here http://forum.xda-developers.com/showthread.php?t=2470070
There is no change with either mode. Cleaning with alcohol only works for a few minutes, and yes Ive removed the ASF for no change.
It should be noted that when booted at first minute or two, the touch inferface is quick and brilliant. After a minute or so it gets slower and remains so. Typing a text is a gruelling affair at that point,
Ran 4.3 android and updated to 4.4.4 and also no change in performance.
Does anyone have any ideas/ tips or pointers?
HELP!?!
An app with a memory leak?
Looks quite normal. RAM 1.1GB used; 600MB free.
Unless thats not what were talking about?
EDIT: might be up to something. using advanced kill on Go taskmanager EX and its seemed to do improve the situation in the short term. Will keep testing
Well got about that far thus far. The advanced kill works sometimes, but none of the apps look out of whack (from my basic knowledge anyhow)
Any help/ links in diagnosing a memory leak would be very appreciated.
Don't suppose you've got the Google now launcher? I had to uninstall as they introduced a memory leak in the last update.
Un updated it just in case.
Its tough as even watchdog lite isint detecting much. com.google.android.gms:snet at startup took 22% CPu but otherwise its steady.
Grr jezz I even did a factory reset to 4.4.4 and its still there. Would trying a custom rom help?
Well as an update manage to completely wipe and reinstall the OS. No change in performance however
Does anyone know if a faulty screen install could be to blame for this?
icehawk223 said:
Well as an update manage to completely wipe and reinstall the OS. No change in performance however
Does anyone know if a faulty screen install could be to blame for this?
Click to expand...
Click to collapse
Could well be, but i find it strange that it acts normal again after a reboot? That alone indicates that it's something wrong with the software. I still hold a finger on a process gone wild. Do you have Recovery installed? If yes, re-flash the ROM or flash something else and see if that solves it. I would personally flash a stock ROM and flash it with Flashtool so you don't have to root or void any warranties, and it'll be the simplest thing to do in case the screen is still acting weird after flash, and you want to get it checked out again (since it most certainly will be a hardware issue at that point).
So, fire up Flashtool, download a complete stock ROM (TFT), flash it, test it. Is it working fine now? Sweet. Keep using the ROM. Is it still the same thing? Contact the repair center again and tell them what's up and please do tell them that you've already done a factory reset, since that's the first thing they'll do themselves. Do not tell them about Flashtool or any other hacks or tweaks. They'll probably blame you if they think that you're an XDA user. "Oh, so you've been playing with it, and you bricked it and wanna fix it for free, bla bla".
Ask if they can open the device again and check that everything is fine and that you haven't received a faulty panel.
Ive actually did a complete tft flash of the original xperia ultra software. No change whatsoever vs previous state.
Im increasingly suspecting a hardware issue. Could it be a poorly plugged in cable? Its random chugging/ smooth response is completely confusing...
icehawk223 said:
Ive actually did a complete tft flash of the original xperia ultra software. No change whatsoever vs previous state.
Im increasingly suspecting a hardware issue. Could it be a poorly plugged in cable? Its random chugging/ smooth response is completely confusing...
Click to expand...
Click to collapse
Did you flash the exact same FTF that you've always used, or did you flash one from a different region? I would try the GPe ROM if i were you, just to be sure, but don't bother doing it if you're not rooted and ready to flash. Yes it can easily be a hardware issue, and you should probably contact Sony or your nearest service center.
As an update I tried installing a fresh tft flash of a different build but same issue.
Notably noticed that the notification light on the screen is not working at all, so currently looks like a hardware issue. Will keep updated for reference & visit a repair centre
My Verizon XT912 has done some strange things over the last few days. Firstly, when we went in to upgrade another phone, my service was interrupted about every 10 seconds or so, switching between 4g to 3g to no service and the only way to get it back was to restart the phone. Even then, the phone would only get signal for a few minutes, ultimately resulting in no service. Now, even on the stock rom, will not display a signal in an area where all of our other phones display full 4g signal (I have the triangle outline with the crossed circle) and the phone restarts when any app is selected, or even when left alone. I personally think something failed on the motherboard. What do you think?
I have the same phone and am having the same problem. I am pretty damn good with phones and have had a long time to mess with this one so know it pretty well. I have had this problem before and was able to fix it using RSD although I had to try many times. I tried a ton of different things and in the end have no idea what fixed it. I highly doubt it is a hardware problem, as when I fixed it the first time the phone was much faster than it had been in a long time. I am convinced it has to do with roms/partitions and the way the stock rom is flashed to it through fastboot. Right now I am once again for the 4th time stuck with this problem and when/if I come up with a better answer for you and other people I will make a thread with all the details I have about this specific problem and how to fix it because there are a lot. One thing I know is that anytime I have had this problem SU of any kind had serious issues, no matter what app (Superuser/SuperSU), or rom, or slot I was using, hence the theory it isn't inherently hardware related... that and the fact that I fixed it twice months ago, a couple days ago, and am stuck on it now. I hope to have some more info for you and everyone else on this soon as I haven't been able to find ANYTHING related to this so far after many many many hours of searching. If you or anyone else has anymore info on this or that might in some way help with this please post it here. I will be watching this thread for a while.
Okay, a dual question here. One specific and one general but they are both related and one will help the other. Hopefully if anyone provides good answers others will find this post useful. I have a Asus Zenfone Selfie which has begun boot-looping. The phone is rooted and has TWRP installed. Once in a while it boots up as far as the home screen, then sometimes only up to the Asus logo. I have flashed several different ROMs (stock and custom) and again, it boots up to the setup screen then only up to the Asus logo so I was assuming this must mean it's hardware related. However, I can boot into TWRP and stay there for hours with no bootlooping. If it were hardware then it should bootloop for TWRP too so it must be software related, right? One more thing: I usually flash in TWRP but many times it crashes during the flash process. Sometimes it does succeed with no issues though. On my PC I might be running some disk or RAM checking tools to see if there was a bad sector or track on my hard drive or a bad module... Yeah, I'm confused. Why is it bootlooping and what, if anything, can I do to fix it?
This leads to my general question. Over the past 20 years I have had several phones, many of which ended up bootlooping. I know the LG G4 & G5 had a hardware flaw that cased them to bootloop and I know screwy flashes can cause bootlooping. But what about all my phones? Some were new, well, only a year or two old, some were 6 or 7 years old. Some were Android, some were Windows Phone. Some were rooted, some were unrooted, some were stock, some were custom ROMs. Some had updated or recently got new apps installed, others hadn't had anything new in ages. Some were in use when they started bootlooping, some were just sitting there. Some had a full charge on the battery, some were close to empty. What can be done to prevent this? What can be done once it has started, especially with one of these newer phones that they STUPIDLY like to make with sealed in batteries. And the given button combination just reboots the phone - again. Depending on who I talk to (or where I read) they say one thing or the other. It's software related. Okay, how? Why? I know on my PC Windows will sometime crash and reboot just for the hell of it, but that's usually just MS fixing an issue with a PC that runs too smoothly. And when that happens, it can be fixed. As an aside to any software developers reading this, I know you may not want to take the time to rewrite everything to work on Linux but you could take a little bit and make your software work with WINE, just a thought guys.
Anyway, so if it's software related, what can really be done to fix it? I can understand the big companies may like it if your phone bootloops so you'll need to buy a new one, but there are tons of developers out there making great custom ROMs. I know they don't have the resources to really fix all the bugs but I assume they would do a better job than certain big companies right? And why would the software suddenly crash like that? Sometimes literally NOTHING is happening, so why the sudden desire to bootloop? What about hardware? Can't we design software to work around the flaw? I would think manufacturers would want to fix problems to make their products as good as they can be but from what we have seen, I guess not. If you read my list above, many of those phones have nothing in common except the bootlooping. So where is the error coming from? Is there really nothing that we can do?
Any ideas and explanations would be appreciated, as would any help on my more recent bootloop device the Asus Zenfone Selfie Z00UD/z00T. Just to mention, that is a newer phone. It may not be now but it bootlooped probably a little over a year ago. It takes me a while to get around to things sometimes, like writing a letter to post on a forum. I had in mind to take it to this one repair shop (they had to replace the USB charging port maybe 3 months before the bootlooping so I assumed there might be a connection) but when I finally got there they told me it was software related and wouldn't look at it. Also, I don't want to make it sound like all my phones bootloop. I have had many many phones that died due to other issues and many more that are still in use, even old ones. I just want to try to understand and grasp any common factors that cause some phones to bootloop, and to maybe use that knowledge to prevent future phones from bootlooping even if I can't repair the ones that already do.
Thanks for your time in reading this and in advance for your answers. If you googled your way here, I hope there is info here that can help you too.
Hi all,
Received my 1 iii yesterday, spent several hours setting it up, tweaking, testing, transferring files--and love it. Been an LG V-series user for the last six years, but with LG bowing out and having moved toward radiused corners, rounded glass, notches, etc. anyway--I'm very glad Sony is still out there making sane, non-compromised phones with basic features like microSD, no hole punch, and headphone jacks that are now treated as "niche" or "enthusiast".
BUT, unfortunately, having a very odd problem, and can't find any examples of anyone else having the issue... but it basically makes the phone unusable.
Literally any time the screen turns off--whether via pressing the power button, or via an inactiivty screen time out--the phone either shuts down, or restarts.
I've done a factory reset several times, tested it with fully restored apps/settings/personal data/etc., and totally un-restored, makes no difference--the issue always happens. So it's not the fault of any setting I altered, app I installed or disabled, etc.
I remember the first time I booted up the phone--but none of the factory reset times since then--that it said something about some setting being on to prevent battery wear from the phone being accidentally turned on during shipping. So maybe there's some bizarre setting somewhere that auto-shuts-down the phone when the screen turns off? Otherwise I'm at a total loss...
Thanks in advance for any help!!
Here is one of two reviews from Amazon about this phone:
"Got in the infinity reboot issue right out of the box...a $1200+ phone, very disappointed .
Got it today on the release. Then start setup and update. Not even until all set up finished, it restarted first time. Then again in just about 15mins. Overall been through restart 12 times. Try hard reset and all other methods, not helping. Return....."
So, unless you are the one who left this review...you are not alone! This type of stuff makes me so disappointed!
Sounds like the reviewer on Amazon was having a different problem. Mine stays on perfectly fine as long as one is interacting with it--only shuts down/restarts if the screen turns off.
Given the variety of software states in which the problem occurs--vlank setup, full set-up, safe mode--seems like a rare hardware issue. As long as it can be replaced with a correctly functioning unit quickly, it's still the phone I want...
If not, I guess I ride out my LG V50 till it dies, and then quit using smart phones...
Having to ship it in for warranty repair. Seems like almost certainly a hardware problem--sounds like I "won" the lemon lottery. A bummer, but not an indictment of the phone generally.
But I'm still really digging the phone--when it works. Did a video A/B with my LG V50, and while it didn't strike me as miles better--it definitely was when full-screen. Not having to look at rounded corners and a notch is worth a lot to me. With font and display set to smallest settings, *love* the look and roominess of the screen.
I agree with not wanting notches, or punch holes...this is why I am interested in this phone...PLUS I truly miss having a notification LED. However, so far the reviews from end users/owners...not the "pro" reviewers on YouTube..is leaning towards the negative! My last three phones have been from OnePlus. Currently on the 8T. I know many have started to slam OnePlus for their practice of late patches and higher prices...but I have not had even ONE problem with any of the OnePlus phones I've had! They just work. I've had the 6, 7-Pro, and now the 8T. There's nothing out there that even interests me any longer that doesn't overheat, or freeze, or have unnecessary dedicated assistant buttons??? Disgusted with them all. I just might have to take a harder look at Apple!!!!
Outside of what appears to be a truly random and uncommon hardware issue that's affecting mine per this thread--I actually really loved the 1 mk iii so far.
I haven't had overheating issues, camera seemed excellent, loved the hardware build quality, *LOVE* having a proper screen again (including no notches, aspect ratio, and tons of room w/ fonts and appearance set to smallest). I will never buy a phone that doesn't have microSD support, and access on this phone is awesome (no tool needed).
I wouldn't be too quick to write it off--especially not for the likes of Apple, who provide a hugely compromised, feature-removing, closed-ecosystem product at an inflated price for what you get.
Keep in mind--it's the internet, so you're going to far disproportionatly have people needing to discuss problems. Folks for whom nothing goes wrong--for any product--won't tend to seek out places like this to say so. So I wouldn't let a really small sample of issues unduly color your view...
Hi I have the exact same issue. Received mine on the 24th and transferred everything over from Oppo find X2 pro. Thought it was me at first when trying to wake but it rebooted. All fine until used in car QI base. After 20 minute drive picked it up and tried to wake only for the same thing to happen. Did this several times yesterday and this morning both on and off charge and while cool to touch. Very disappointing as expected more for something that cost nearly £1200! Like the phone a lot and prefer it over the Oppo but cannot find a way around this. A new 256k micro SD card also being used so have tried without this, without the EE sim and factory reset but still it happens. It's unusable as is so will have to be replaced, unless any suggestions?
Have had a few good Android phones from Huawei P20 pro, Mate 20X to current Oppo in recent times but never had an issue like this.
Having to swap back to the Oppo is very time consuming and exasperating!
Shame as this is a stunningly good phone.
Mikehbw said:
Hi I have the exact same issue. Received mine on the 24th and transferred everything over from Oppo find X2 pro. Thought it was me at first when trying to wake but it rebooted. All fine until used in car QI base. After 20 minute drive picked it up and tried to wake only for the same thing to happen. Did this several times yesterday and this morning both on and off charge and while cool to touch. Very disappointing as expected more for something that cost nearly £1200! Like the phone a lot and prefer it over the Oppo but cannot find a way around this. A new 256k micro SD card also being used so have tried without this, without the EE sim and factory reset but still it happens. It's unusable as is so will have to be replaced, unless any suggestions?
Have had a few good Android phones from Huawei P20 pro, Mate 20X to current Oppo in recent times but never had an issue like this.
Having to swap back to the Oppo is very time consuming and exasperating!
Shame as this is a stunningly good phone.
Click to expand...
Click to collapse
Forgot to say there are others on here with similar issue, under random reboot thread.
After sending in for "repair" and receiving it back with no improvement (but "repaired"), Sony has finally agreed I'm due a replacement unit. Have shipped my first unit off, due to arrive to them next Wednesday. Will hopefully receive a properly-functioning replacement soon thereafter... Agree that, if the phone didn't have this bizarre issue, it would be great--very close to what I want in a phone (versus the myriad options out there that don't offer what I want, and insist on absurd design choices I detest).
So, we'll see. Certainly frustrating to have an issue like this on a phone that costs more than plenty of computers...
(To be clear, I had the issue literally every time, from the beginning, regardless of what I had/hadn't set up, installed, sim card/no sim card, micro SD/no micro SD, etc.).
I have Xperia™1 III but the phone is really stable for me, no random reboot. I have only heating issue. Xperia™ XZ2 Premium hasn't heat like this phone. My phone is Hong Kong device
Most likely not what caused your issue...but...it is NOT a good idea to allow any backup to install all your previous apps from an "old" phone to a new one. I know it can be a major pain and very time consuming to install everything from scratch when setting up a new phone...however...when you allow a backup to flow freely onto a new phone you are allowing all the junk to come back also! It's up to you, but I always install everything from scratch and it may not be related but...I have owned many, many phones and NEVER had all the problems that so many have all across the board. Am I just lucky, or is it because I have so much experience with computers and know how to set things up properly? YMMV
jaseman said:
Most likely not what caused your issue...but...it is NOT a good idea to allow any backup to install all your previous apps from an "old" phone to a new one. I know it can be a major pain and very time consuming to install everything from scratch when setting up a new phone...however...when you allow a backup to flow freely onto a new phone you are allowing all the junk to come back also! It's up to you, but I always install everything from scratch and it may not be related but...I have owned many, many phones and NEVER had all the problems that so many have all across the board. Am I just lucky, or is it because I have so much experience with computers and know how to set things up properly? YMMV
Click to expand...
Click to collapse
I think you have been lucky
Like you I have never had a problem and been in IT since the early 80's but this isn't something that's has been moved over. Sadly, the phone behaves the same wether out of the box or fully migrated. In the PC world I saw something similar with overheating and poorly cooled AMD processors in the 90's and am wondering if this is a heat related component batch issue?
Sony need to get a grip on this sharpish or they will be looking at refunds, which is never good.
The reboots are caused by the fingerprint reader. My new phone would bootloop while fast charging if my one and only configuration after a factory reset was setting a fingerprint.
DO NOT SEND IT IN FOR A WARRANTY REPAIR - - IT WILL GET WORSE
Get a refund.
First, Sony sent it to SBE with FedEx Ground, which currently takes about 2 weeks.
Second, SBE returned it bricked and voided my warranty. They said I flashed it but I had sent it in new and unmodified. I didn't even think they returned my own phone back because it had a UK/EU label and destroyed firmware. Sony Support would no longer help me because I was no longer a customer. SBE insisted I was a firmware flasher that deserved nothing. I ran EMMA and it showed my phone IMEI, locked bootloader, and stock firmware.
I finally found somebody on Sony Support who would give me an RMA. Maybe it was their mistake, but I wasted no time shipping it back. I'm doing a credit card charge reversal if I get any more crap from Sony/SBE.
I have spoken to Sony UK tech support and they have confirmed there is a reboot issue with some1iii's. Apparently, second line technical support have identified the issue (software) and there will be a revision released to cure this. When pressed, they couldn't give me a date for this and were a little vague. I was advised to return to my supplier for a refund.
Not good on a phone costing £1200 and surprised they haven't got their act together more quickly. They seem to be struggling getting phones shipped presently and my supplier has confirmed a 14 day wait if I want to re-order. I don't know if this is just poor advanced planning by Sony UK or if this is a Sony global problem trying to get hold of the components for manufacture.
Despite all the issues, this phone still ticks all the boxes for me so have decided to wait for the dust to settle!
Good to know there's some awareness now on Sony's part of this issue, and a plan yo resolve it via software (?). If the second unit I get has the same issue, I guess I'll wait a bit for that aoftware resolution--but deeply hoping I won't have the issue again.
I will say, I believe I tested not registering any fingerprints on at least one of the numerous factory resets I tried, and I believe the issue still occurred--had seen threads of similar issues stemming from the fingerprint reader on other manufacturer's phones, so tried to rule it out...
The original phone I got back from SBE wasn't bricked, it just wasn't in any way improved. Fortunately Sony didn't make any weird claims that I'd done anything wrong (I wouldn't know how to mess with "rooting" or whatever--no interest/need to). It was delivered to Sonyin San Diego by FedEx today--so hoping my replacement unit ships in the next day or two...
Mikehbw said:
Despite all the issues, this phone still ticks all the boxes for me so have decided to wait for the dust to settle!
Click to expand...
Click to collapse
Agreed. With LG gone, I really want the Xperia 1 iii to pan out--only phone that has microSD, no notches/currves/radiused corners, a hogh-res screen, and a headphone jack. If I can't get one to work properly, I'll probably just buy another LG V50, second-hand.