Hi,
My Xperia gave an OTA Update and said it improves battery life and enhanced user experience.
After the update the screen rotation is all messed up. The screen settings are wrong. Worst of all, even after turning it off, the games are also not working right (probably because of wrong readings).
I have also tried *#*#7378423#*#* and tried to callibrate.. but of no avail.
Also the screen goes blank adn pressing the power button does not respond for a while.
Any idea how this update can be rolled back.. The phone is a mess now which is especially bad cause I was loving the experience so far. :S
Any help..
Bump..
Ive also done a factory reset and also updated via Sony PC Companion..
No use.. Im guessing Im the only one whose phone was updated from SONY yesterday to deliberately make me hate it .. :S
majidaziz said:
Hi,
My Xperia gave an OTA Update and said it improves battery life and enhanced user experience.
After the update the screen rotation is all messed up. The screen settings are wrong. Worst of all, even after turning it off, the games are also not working right (probably because of wrong readings).
I have also tried *#*#7378423#*#* and tried to callibrate.. but of no avail.
Also the screen goes blank adn pressing the power button does not respond for a while.
Any idea how this update can be rolled back.. The phone is a mess now which is especially bad cause I was loving the experience so far. :S
Any help..
Click to expand...
Click to collapse
Flash new firmware with flashtool...
yup did that.. finally to get rid of sony's stupid update and it worked..
Thankfully the phone is back as good as it was and does not lag on unlocking like it had started to do so.
One small problem, the rotate screen does not work sometimes, when I restart it it works. But atleast its not giving crazy readings like it was with SONY update.
majidaziz said:
One small problem, the rotate screen does not work sometimes, when I restart it it works. But atleast its not giving crazy readings like it was with SONY update.
Click to expand...
Click to collapse
Did you recalibrate from service menu after the final flashing? Just an idea..
no not really.. it started to work fine after flashing of the original software (4.3)
I DID however tried my best to recalibrate from Service menu BEFORE flashing i.e with the updated software patch from Sony.. but it didnt work. Every time I recalibrated on Flat surfaces, it said calibration successful.. but after a min or two wehn using the phone. all of a sudden they went bonkers again
After a day like that the readings stopped showin..?? I thought the phones hardware went bust .. but apparently a software issue..
Related
today is third day of using z1 but i haven't restarted or shutdown the phone ever since its first reboot after firmware update.
just a while ago my z1 was acting up, slow and buggy and stuff so i thought i might need to restart the phone because z1 has no memory clean up features like samsung phones do. (let me know if there is )
so i went ahead and turned the device off, waited about 5 seconds then turned it back on. Sony logo was up for about 2 seconds then screen goes to black but only back light is on. I waited thinking it is part of booting process but it took way too long.
i did hard reset by pressing power+vol up and turned it on again, problem still exists, only back light was on.
i had to do hard reset the phone for 6 freakin times, worrying about having to send this phone out to sony service center for weeks or wait for bell to stock their inventory which has no ETA i think, then it finally boot into colorful wave screen. that was the longest 5 minutes i experienced this year for sure!
i turn it back off and on thrice more to see if it happens again but it boot up just fine without no glitch. (colorful wavy screen kicks in right after sony logo)
anyways did anyone experienced the same thing? it looks like it's sort of software related problem, existed since Xperia Z, I can't believe sony didn't implemented fix for this [email protected] for Z1.
FYI my Z1 is from Bell(c6906), SN starts with BH900
choihan06 said:
today is third day of using z1 but i haven't restarted or shutdown the phone ever since its first reboot after firmware update.
just a while ago my z1 was acting up, slow and buggy and stuff so i thought i might need to restart the phone because z1 has no memory clean up features like samsung phones do. (let me know if there is )
so i went ahead and turned the device off, waited about 5 seconds then turned it back on. Sony logo was up for about 2 seconds then screen goes to black but only back light is on. I waited thinking it is part of booting process but it took way too long.
i did hard reset by pressing power+vol up and turned it on again, problem still exists, only back light was on.
i had to do hard reset the phone for 6 freakin times, worrying about having to send this phone out to sony service center for weeks or wait for bell to stock their inventory which has no ETA i think, then it finally boot into colorful wave screen. that was the longest 5 minutes i experienced this year for sure!
i turn it back off and on thrice more to see if it happens again but it boot up just fine without no glitch. (colorful wavy screen kicks in right after sony logo)
anyways did anyone experienced the same thing? it looks like it's sort of software related problem, existed since Xperia Z, I can't believe sony didn't implemented fix for this [email protected] for Z1.
FYI my Z1 is from Bell(c6906), SN starts with BH900
Click to expand...
Click to collapse
Try doing a wipe then repair with PC companion. If that doesn't work, take it back and get it replaced. I've have my Z1 for about 3 weeks now and haven't had any issues.
It's probably a defect unit. I'd take it back as soon as possible.
I just wanted to let you know that with xposed gearbox you can add a kill app button like on Samsung phones .
The kill app button will be in the recent section . Really handy.
aridoasis said:
Try doing a wipe then repair with PC companion. If that doesn't work, take it back and get it replaced. I've have my Z1 for about 3 weeks now and haven't had any issues.
Click to expand...
Click to collapse
never had problem after the first incident... i still have few days until exchange deadline so will see how it goes! thanks for your advice!
Lucian5800 said:
It's probably a defect unit. I'd take it back as soon as possible.
Click to expand...
Click to collapse
hopefully not.. even if it's defect i won't be able to replace it right away because the place i bought the phone from has no more z1 in stock.. plus i can't show them what happened because it's working just fine now.
SweFox said:
I just wanted to let you know that with xposed gearbox you can add a kill app button like on Samsung phones .
The kill app button will be in the recent section . Really handy.
Click to expand...
Click to collapse
what's xposed gearbox? is it a MOD?
Actually Android is pretty good at handling background processes on its own. Regularly killing Apps will just make your phone feel slower because it has to reload Apps instead of directly opening them out of the RAM.
I think you just experienced a software hiccup, if it is not happening again I would not worry about it too much.
Is power + Vol up the same function as the red reset button under the sim card cover?
I had the same problem after I had changed a setting - optimised backlight. When I changed the setting back the problem went away. The setting seems to have been removed on 257
Sent from my C6903 using XDA Premium 4 mobile app
Hi,
I have a brand new Xperia SP, manufactured on 2013/W50, so it's really new. It contains the latest stock firmware.
After I start or answer a call and put the phone to my ears, it's screen doesn't came back and remains off until the call is ended by the other party. No matter if I'm moving the phone away from my head, not even the hard buttons are turning the screen back on. The touchscreen is not working either. It's just stuck as if it's near to my head. I can't even hang up the call...
It happens about 80% of time. Sometimes it works as expected without any problems. Happens more often when having an incoming call after a longer period (30+ mins) or if the call takes more than 1 minute (auto screen disable time?).
As a workaround, I turned on the function that power button hangs up call, but I cannot use my touchscreen while call.
I checked the proximity sensor with the phone's diagnostic function and with cpu-z and the sensor is just working fine 100% of the time.
Is it a known bug or a hardware problem? Does it have a workaround?
hmmm
carlosmeldano said:
Hi,
I have a brand new Xperia SP, manufactured on 2013/W50, so it's really new. It contains the latest stock firmware.
After I start or answer a call and put the phone to my ears, it's screen doesn't came back and remains off until the call is ended by the other party. No matter if I'm moving the phone away from my head, not even the hard buttons are turning the screen back on. The touchscreen is not working either. It's just stuck as if it's near to my head. I can't even hang up the call...
It happens about 80% of time. Sometimes it works as expected without any problems. Happens more often when having an incoming call after a longer period (30+ mins) or if the call takes more than 1 minute (auto screen disable time?).
As a workaround, I turned on the function that power button hangs up call, but I cannot use my touchscreen while call.
I checked the proximity sensor with the phone's diagnostic function and with cpu-z and the sensor is just working fine 100% of the time.
Is it a known bug or a hardware problem? Does it have a workaround?
Click to expand...
Click to collapse
I have the same problem. It is one of the few bugs in 12.0.a.2.254 build. Guys using unofficial release of 4.3 are not facing such problems. I suggest you to wait for the official 4.3 update which will be released soon according to SONY. :good:
really?
madhukarmohan said:
I have the same problem. It is one of the few bugs in 12.0.a.2.254 build. Guys using unofficial release of 4.3 are not facing such problems. I suggest you to wait for the official 4.3 update which will be released soon according to SONY. :good:
Click to expand...
Click to collapse
thanks!
so, this is surely a known bug in the 254 firmware? I'm just wondering because I asked this on other xperia sp forums but no users complained about it.
is there a workaround for it?
yes
carlosmeldano said:
thanks!
so, this is surely a known bug in the 254 firmware? I'm just wondering because I asked this on other xperia sp forums but no users complained about it.
is there a workaround for it?
Click to expand...
Click to collapse
Yeah, few r experiencing that. i hv seen complaints in sony blog and here too. I asked this question few days back. but, I didnt get reply.
I experienced this problem once.I think it was fixed after performing a SEUS repair...Not sure though :silly:...
Try performing a factory data reset on even reset app datas
thx
UltraWelfare said:
I experienced this problem once.I think it was fixed after performing a SEUS repair...Not sure though :silly:...
Try performing a factory data reset on even reset app datas
Click to expand...
Click to collapse
thanks to both of you, I'll do factory reset and repair via PC software, and some more factory resets. that should solve the problem.
I'm wondering why an out-of-the-box phone needs a reset, but let's see
carlosmeldano said:
thanks to both of you, I'll do factory reset and repair via PC software, and some more factory resets. that should solve the problem.
I'm wondering why an out-of-the-box phone needs a reset, but let's see
Click to expand...
Click to collapse
Don't forget to backup.First of all clear the data of the Settings -> Apps(or reset them)
UltraWelfare said:
Don't forget to backup.First of all clear the data of the Settings -> Apps(or reset them)
Click to expand...
Click to collapse
thanks. I won't backup as I installed only a few apps and the phone is almost factory state. but I'll do everything else.
hope it works. thanks to all, I'll report the results.
carlosmeldano said:
thanks. I won't backup as I installed only a few apps and the phone is almost factory state. but I'll do everything else.
hope it works. thanks to all, I'll report the results.
Click to expand...
Click to collapse
I hope everything goes fine
no success
I reset applications, did a factory reset, reinstalled phone's software with sony pc application, checked after each step, but no success...
sometimes working, sometimes not (mostly not) but the proximity sensor works fine.
out of ideas...
carlosmeldano said:
I reset applications, did a factory reset, reinstalled phone's software with sony pc application, checked after each step, but no success...
sometimes working, sometimes not (mostly not) but the proximity sensor works fine.
out of ideas...
Click to expand...
Click to collapse
Bring it to a sony service(or how's it called to your country)
it seems it's related to deep sleep. when I am called after the phone was left for 30+ minutes, it's more willing to not turning on the screen, but it turns it on after a while if having a long call. when I start the call, it mostly works. not always, but most of the time.
so it seems it's not sensor-related but something like the software is bugging.
what I don't really understand, why the hardware buttons are disabled while phoning when the phone is put to the face. it'd be enough to code that power button turns on/off the screen no matter what the proximity sensor says. I'd program it like that as a backup solution.
I wouldn't send it for repair, here in Hungary I always hear that mobile phone services just reinstall software and don't care about testing or finding the problem (if not deterministic), and do it again and again while you get tired and accept the failure. yes, it's sad but in the time of MNCs, the user doesn't matter at all after bought the product.
carlosmeldano said:
it seems it's related to deep sleep. when I am called after the phone was left for 30+ minutes, it's more willing to not turning on the screen, but it turns it on after a while if having a long call. when I start the call, it mostly works. not always, but most of the time.
so it seems it's not sensor-related but something like the software is bugging.
what I don't really understand, why the hardware buttons are disabled while phoning when the phone is put to the face. it'd be enough to code that power button turns on/off the screen no matter what the proximity sensor says. I'd program it like that as a backup solution.
I wouldn't send it for repair, here in Hungary I always hear that mobile phone services are just reinstall software and don't care about testing or finding the problem (if not deterministic), and do it again and again while you get tired and accept the failure. yes, it's sad but in the time of MNCs, the user doesn't matter at all after bought the product.
Click to expand...
Click to collapse
Try flashing custom firmware(not sure if it will work try it)...
If it doesn't work again then it's a hardware fault and not a software bug
UltraWelfare said:
Try flashing custom firmware(not sure if it will work try it)...
If it doesn't work again then it's a hardware fault and not a software bug
Click to expand...
Click to collapse
yes, that's another option. the other option is to cry off from purchase (I can do it within a week), they return the money, and I buy another one. I'll see as this is not that disturbing problem and I have no other problems with the phone like wifi bug or anything else.
someone said it's a bug so I hope 4.3 next month will solve it.
Hello.
When i didnt think it could be any worse, well then it got worse
https://www.youtube.com/watch?v=3GhXc2kRmMo&feature=youtu.be
Well i updated to 14.4.A.0.108 and my phone is really weired after that. This is one of the things happening. And yes i tried to wipe and flash fresh. And also with no screen protector on. If i turn on screen and then turn it off and on again this usually doesent happen. But if i just turn it on to swipe, this happens almost every time now.
I tried to wipe the phone reverting to the .761 firmware and even .757 but this is still present. If i do the screen diagnostics it works like it should. This happens as said after waking the screen up. But if i just turn the screen back off and then on again then this isnt happening.
So the newest update must have caused something i cant get rid of since i didnt have this issue when i was on .761. I tried a custom rom aswell, same issue.
Im lucky my OnePlus One phone is on its way atm. Because i dont see anyway of saving this phone now.
As title said, this happened more frequently these few days, i'm not sure if this is software failure or hardware getting old as i didnt install any new thing to my Z1 these few days.
My phone is on iHackers v5.1 and trinity kernel v3.0, would they cause the failure?
I hope i can fix it fast as i'm on exam these days, but i wont like to simply flash an ftf to cover everything as i cant live with the stock Z1...
Thx guys
I get the same issue on my Z1 (stock fw but rooted). Screen wont turn on from sleep. I used to hold power and VolUp to force phone to turn off but I find it comes back after a while. I just put it down to my phone being a piece of ****.
I assume a wipe/different ROM will fix it but I'm just gonna wait and get rid of the phone in a couple of months.
I did try putting a Logcat viewer on to see if I could track down what did it but I couldn't be bothered trawling through every log entry.
Really disappointed with this phone.
cyberguru said:
I get the same issue on my Z1 (stock fw but rooted). Screen wont turn on from sleep. I used to hold power and VolUp to force phone to turn off but I find it comes back after a while. I just put it down to my phone being a piece of ****.
I assume a wipe/different ROM will fix it but I'm just gonna wait and get rid of the phone in a couple of months.
I did try putting a Logcat viewer on to see if I could track down what did it but I couldn't be bothered trawling through every log entry.
Really disappointed with this phone.
Click to expand...
Click to collapse
I know how to force reboot it but u are still f**ked when u rely your phone on alarm clock.
Looks like i fixed it anyway, need to change cpu governor
I may be the lucky one whose screen didn't start to peel off yet,but f*ck me this phone is starting to really piss me off.
Everything worked well after I have gone to SLiMM 1.4(way before) and as I was upgrading SLiMM versions it was slower and slower to the point where the phone is unusable!
So I thought,let's try to do a good old phone reset,reflash the ROM and go from the beginning.
I restored the apps,rebooted the phone and it was STILL painfully slow,so I resetted it again but this time restoring half the apps and half the Xposed modules I have used before.
It improved a tiny bit but nothing significant.
So I thought it is finally time to unlock the bootloader and see if there is any good AOSP ROMs,as the first one I tried was AOSP 7.1.1.
Fastest ROM I have used by far,the biggest problem,my device gets very hot from loading Messenger and jumping back to Snapchat and in AOSP 7.1.1 it would stop charging the phone because of the high temperature and this was quite a big issue.
So after using it for 2 weeks,I couldn't handle the charging thing anymore,so next best thing was Sony Concept ROM.
I install the ftf,goes well,install the recovery,install DRM fix,SuperSU and Xposed.
After rebooting I notice that Xposed didn't install properly so I jump back and flash it again,and the problem now was it would get like VERY VERY hot(you couldn't touch it) when it came to the "Android is starting" screen and of course the device started rebooting itself because it was way too hot.
So what I did was put the phone on a bag of f*cking ice to keep it cool,and it FINALLY passed that screen,only to find out a second later it returned to the bootanimation and gone into a bootloop.
Now I reflashed the ftf,but before even booting the ROM for the first time I flashed recovery,Xposed,SuperSU and the DRM fix.
It booted up fine,so I started to restore my apps and everything went well until I rebooted my device to find out it doesn't want to log in to Snapchat,the app I use very often.
So I flashed Magisk,systemless Xposed just that I can hide the root from it and disable Xposed just to log in to my account.
Even that didn't work so fine I'll try it next day.
So I decide to reboot the phone quickly and it has gone into the "Android is starting" screen and shut off in the half of the process. F*cking pissed.
I cool the phone down,boot it up,wait for it to finish and when it was close to finishing it has gone into a bootloop,and wiping cache doesn't solve it.
It is currently in a bootloop as we speak.
I really do like the phone but why is it behaving so badly? I do not know if someone had a similar experience as I did.
If anyone could give me a suggestion to make my phone stable and functional,please write a post since I need my phone to work.
Flash original android rom/kernel to the device to make device fully stock. Once it is back to stock, if problems still continue i recomend sell device and buy new one.. On my xperia, display stopped working out of blue, replaced it and my camera became blurry and vibration motor stopped working... Opened it again, fixed vibration motor, now it waits another opening to replace battery and camera lens... Disaster, but hey, device is great in hw department..
Strmy said:
Flash original android rom/kernel to the device to make device fully stock. Once it is back to stock, if problems still continue i recomend sell device and buy new one.. On my xperia, display stopped working out of blue, replaced it and my camera became blurry and vibration motor stopped working... Opened it again, fixed vibration motor, now it waits another opening to replace battery and camera lens... Disaster, but hey, device is great in hw department..
Click to expand...
Click to collapse
I forgot to mention,every time I said reset the phone I actually did flash the stock ftf and set it up all on my own,but whatever.
I guess it is just bad luck.
Dinkec27 said:
I forgot to mention,every time I said reset the phone I actually did flash the stock ftf and set it up all on my own,but whatever.
I guess it is just bad luck.
Click to expand...
Click to collapse
Jebiga mi Hrvati imamo lose srece sa mobitelima hahah
More luck next time
Dinkec27 said:
I forgot to mention,every time I said reset the phone I actually did flash the stock ftf and set it up all on my own,but whatever.
I guess it is just bad luck.
Click to expand...
Click to collapse
internal memory is failing.
bookworth said:
internal memory is failing.
Click to expand...
Click to collapse
Awesome
bookworth said:
internal memory is failing.
Click to expand...
Click to collapse
Dinkec27 said:
Awesome
Click to expand...
Click to collapse
Exactly, I suggest the same issue. I had exactly the same problem on my Xperia T, it became slower, slower, incredibly slow after three years so I couldn't even flash anything using flashtool - it was showing many errors. Even after factory resetting the phone, it was booting and setting up for like... two hours or more, becoming VERY hot but it finally booted, still was very slow.
Two solutions - warranty or selling it.
romcio47 said:
Exactly, I suggest the same issue. I had exactly the same problem on my Xperia T, it became slower, slower, incredibly slow after three years so I couldn't even flash anything using flashtool - it was showing many errors. Even after factory resetting the phone, it was booting and setting up for like... two hours or more, becoming VERY hot but it finally booted, still was very slow.
Two solutions - warranty or selling it.
Click to expand...
Click to collapse
It just doesn't make sense to me that the internal memory could be failing just under a year...
I cannot go for warranty since I voided it with unlocking the bootloader,and selling it is not an option because I am on a contract currently and I can only sell it once it expires and then get a new phone to renew my contract.
If it is internal memory,it is a second tine in a row,before I had the Galaxy S3 and it had the same symptoms,it looks like I'm prone to internal memory failures lol
Is there a way I can test the internal memory?