Database Develop

[Q] Turn off failure

I've got an unbranded LT30p Skyfall and sometimes when it comes to turn it off it autorestarts and when you try to turn it off again it does correctly. Weird thing, isn't it?

Lol I'm having this issue on my tx. Thought I was the only one. Best thing to try first is do a clean wipe and the install it again, but I'm too lazy to do it, maybe you can give it a try.

tigre72 said:
I've got an unbranded LT30p Skyfall and sometimes when it comes to turn it off it autorestarts and when you try to turn it off again it does correctly. Weird thing, isn't it?
Click to expand...
Click to collapse
Used to happen in the old firmware, don't think it happens anymore on the newer one.

yeah, and i miss it.
I love the rebootoption that stock roms dont have on the power menu. Is is able to be implemented, because this "bug" does it and also you can have reboot on the status toggles bar...
One of only 2 "tricks" sony have missed to make a perfect rom.... guess what the other one is..

papped said:
Used to happen in the old firmware, don't think it happens anymore on the newer one.
Click to expand...
Click to collapse
I have mine updated when all the things about Miracast. I guess it's when all started.

My Xperia TX also got this problem.
When I turn off the power with USB connected to charger or something
normally it should be turn off and keeping charge the battery.
But it doesn't, it reboots again.
It doesn't happens when I using Xperia Arc S.
My firmware is the latest version, may be the problem didn't fixed in the new updates.

[Q] Screen not working after updating from 4.1.2 to 4.2.2

I updated my phone just recently and came across this major issue.
I used Sony's own tools for updating that leaves two options "Sony Companion" and "Sony Update Service".
Both giving the same results for my phone, even a full reinstall doesn't work.
When done updating you set your Xperia ZR back on as the software says.
It starts normally showing the Sony logo, Xperia logo and some Xperia animations.
When it gets to the lock screen and asks for your pin code to unlock your sim-card everything is fine.
Here it comes.
When setting your screen in standby and back on the touchscreen function is not working anymore.
Other buttons are working fine (power, volume, photo)
I talked to a Sony employee and he came to the conclusion that it's a Hardware defect, that sounds to me like a bad excuse.
The screen works the first time but not the second time it's turned on.
Looks to me like a software problem.
Are any others of you experiencing this problem with the Xperia ZR? Please, let me know below!
I don't have a solution yet or if you have a solution, let us/me know down here.
Thanks in advance!

It sounds like the firmwarepart with drivers four the touchscreen didn't bite. If it's anything like the 4.2.1-4.2.2 in HTC that part needs to get through.
Is there any way of restarting the process through companion?
Skickat från min HTC One via Tapatalk 2

A temporarily solution is to touch the screen when pressing the power button to turn on the screen.
Example: Touch with your left index finger on the screen and press power shortly as you normally do, then move your index finger over the screen.
But you have to do this every time you turn on the screen!

Ceremco said:
A temporarily solution is to touch the screen when pressing the power button to turn on the screen.
Example: Touch with your left index finger on the screen and press power shortly as you normally do, then move your index finger over the screen.
But you have to do this every time you turn on the screen!
Click to expand...
Click to collapse
Have you tried flashing the ftf file through flashtool?

djpeesh said:
Have you tried flashing the ftf file through flashtool?
Click to expand...
Click to collapse
No, I haven't tried that yet, because I'm not familiar with flashtool.

It's easy.
1. Do a search for flashtool and download the exe file.
2. Install it. Install the latest drivers by going to the install drivers menu in the program.
3. Download the ftf file on the android development section.
4. Save it in the c drive folder for flashtool-->>firmware
5. Press the big flash (lightning symbol)
6. Chose flash mode
7. Your firmware should show up. Choose the C5503 firmware.
8. It will tell you to turn off your phone and while plugging in, keep the back button pressed. Since the zr doesn't have a back button, hold the volume down button.
9. It should do everything automatically. You'll be on a new os. Reboot and you're done.
Sent from my C5503 using Tapatalk 2

djpeesh said:
It's easy.
1. Do a search for flashtool and download the exe file.
2. Install it. Install the latest drivers by going to the install drivers menu in the program.
3. Download the ftf file on the android development section.
4. Save it in the c drive folder for flashtool-->>firmware
5. Press the big flash (lightning symbol)
6. Chose flash mode
7. Your firmware should show up. Choose the C5503 firmware.
8. It will tell you to turn off your phone and while plugging in, keep the back button pressed. Since the zr doesn't have a back button, hold the volume down button.
9. It should do everything automatically. You'll be on a new os. Reboot and you're done.
Sent from my C5503 using Tapatalk 2
Click to expand...
Click to collapse
I'll try that :fingers-crossed:
Did you also try the update to 4.2.2?
It's still bugging me that they released it and it didn't work. (for my Sony Xperia ZR at least)

Great it worked!
I took flashtool from androxyde.github.io and I also took the firmware from there.
For me the first 3 times flashing went wrong, but it's nothing to worry about just reconnect the USB while pressing volume-down button and retry.
So I am now back to android 4.1.2 and the screen is working fine without any problems.
Thanks djpeesh!

I have the same problem but I don't want to revert to 4.1.2 is there another workaround? This is really stupid SONY says that an app can cause this but there is pretty much nothing on my device. I did a hard reset and it didn't help. I'll try something else to see if I can avoid the downgrade. I think everything started when I activated debugging mode.

Same happens with mine.At times I am not able to accept phones calls by sliding. i have to press the power button several times to switch off and on the screen and then it functions again

motodude said:
Same happens with mine.At times I am not able to accept phones calls by sliding. i have to press the power button several times to switch off and on the screen and then it functions again
Click to expand...
Click to collapse
I tried flashing 4.2.2 russian rom and it didn't work, tried 4.1.2 russian version, also didn't work. I'll try another ROM now and if it still doesn't work I'll go to where I bought it and I'm going to smash it in the sellers head (angry). I'm so disappointed in SONY.

andes83 said:
I tried flashing 4.2.2 russian rom and it didn't work, tried 4.1.2 russian version, also didn't work. I'll try another ROM now and if it still doesn't work I'll go to where I bought it and I'm going to smash it in the sellers head (angry). I'm so disappointed in SONY.
Click to expand...
Click to collapse
Please dont try this method, as this might brick your phone permanently and you might end up in jail.

motodude said:
Please dont try this method, as this might brick your phone permanently and you might end up in jail.
Click to expand...
Click to collapse
I managed to make the screen work again but then it stopped like before. I suspect that there might be a SIM card problem is your sim a genuine micro SIM or is it like mine a chopped mini one?

I sended my Xperia ZR back to sony, because I talked to a SONY employee about this and his answer was to send it back for repairs. After all **** installations that didn't work. At the look of it the frimware for the screen is not inplemented in the new 4.2.2 update. If you could rip the 4.1.2 screen frimware off and migrate it with the 4.2.2 update that could work, but that is a bit to advanced for me.

Ceremco said:
I sended my Xperia ZR back to sony, because I talked to a SONY employee about this and his answer was to send it back for repairs. After all **** installations that didn't work. At the look of it the frimware for the screen is not inplemented in the new 4.2.2 update. If you could rip the 4.1.2 screen frimware off and migrate it with the 4.2.2 update that could work, but that is a bit to advanced for me.
Click to expand...
Click to collapse
My screen didn't work even with a 4.1.2 official roms tomorrow I'm going to send it for repairs. It's really annoying to spend 500 dollars and have these stupid problems my HTC TOUCH HD is 5 years old and has never been repaired, still works the old beast, and this device is 10 days old and already is getting on my nerves.

andes83 said:
I managed to make the screen work again but then it stopped like before. I suspect that there might be a SIM card problem is your sim a genuine micro SIM or is it like mine a chopped mini one?
Click to expand...
Click to collapse
Yus, chopped one

motodude said:
Yus, chopped one
Click to expand...
Click to collapse
Well, that wasn't the problem anyway I just left mine in the repair shop, they tried to blame for messing up the software of the phone but I used only SONY official firmware, so let's see what they'll come up with next I hope they won't make me pay for repairs because this will be a very sad story.

andes83 said:
Well, that wasn't the problem anyway I just left mine in the repair shop, they tried to blame for messing up the software of the phone but I used only SONY official firmware, so let's see what they'll come up with next I hope they won't make me pay for repairs because this will be a very sad story.
Click to expand...
Click to collapse
Why are they saying that you have messed up with the software,in which firmware are you in.

motodude said:
Why are they saying that you have messed up with the software,in which firmware are you in.
Click to expand...
Click to collapse
I used only software from this page http://forum.xda-developers.com/showthread.php?t=2384512 and Sony Companion repair tool. I don't know what their problem was, probably just want to score some money or something.

I know this topic become legacy already, but how do u guys solve it? My xperia zr screen becomes crazy if overheat a bit. No matter what firmware used. Have to off screen and then on back. Very annoying.

[Q] Screen not waking up while on phone call

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.

[Q] HTC One Screen Problem

Hey guys,
I bought an HTC One about 15 days ago. Within 2-3 days of using it, I started getting problems with the display screen. I suppose this problem was seen by few people who owned the HTC One X but I couldnt find any useful solutions in those formums hence im posting here.
This is what happens:
1. Whenever I receive a call, the screen goes black and doesnot turn on until I hang up the call. This effectively makes the device useless as a phone, as I can't see who is calling and also during call I cannot access the screen.
2. Sometimes, there is a delay with the power button. When I press the power button, the touchscreen becomes responsive but the display doesn't turn on.
The problem is, if I factory reset the device, it starts working perfectly again!! Again after about 2 days it starts the same problems.
So I thought it was a software issue and so, I got s-off and installed the GPE Rom on the device. 7 days passed, no problems. On the 8th day, the same problem occured again. And as earlier, factory resetting solved the problem.
Is this a software issue, hardware issue or something else I dont know about?
I have taken a video of the device malfunctioning, but I don't know if I can post it as an attachment.
Thanks in advance!

anibjoshi said:
Hey guys,
I bought an HTC One about 15 days ago. Within 2-3 days of using it, I started getting problems with the display screen. I suppose this problem was seen by few people who owned the HTC One X but I couldnt find any useful solutions in those formums hence im posting here.
This is what happens:
1. Whenever I receive a call, the screen goes black and doesnot turn on until I hang up the call. This effectively makes the device useless as a phone, as I can't see who is calling and also during call I cannot access the screen.
2. Sometimes, there is a delay with the power button. When I press the power button, the touchscreen becomes responsive but the display doesn't turn on.
The problem is, if I factory reset the device, it starts working perfectly again!! Again after about 2 days it starts the same problems.
So I thought it was a software issue and so, I got s-off and installed the GPE Rom on the device. 7 days passed, no problems. On the 8th day, the same problem occured again. And as earlier, factory resetting solved the problem.
Is this a software issue, hardware issue or something else I dont know about?
I have taken a video of the device malfunctioning, but I don't know if I can post it as an attachment.
Thanks in advance!
Click to expand...
Click to collapse
upload it on youtube and post the link.
And something else. Make a factory reset again and then don't install any apps. Does the error also occure?

Im new to XDA forums and hence the site does not allow me to post URLS. However I have uploaded the video to youtube.
If you put 'HTC One screen problem Aniruddha Joshi ' in the youtube search box, you will find my video.
Im sorry I couldnt think of any other way
I did not install anything out of the ordinary. Just updated the existing google apps and installed facebook, twitter and whatsapp! No crazy apks or unknown apps.
Also, once I factory reset the phone, it starts working perfectly and there is no way to know the time after which it starts giving problems again. Once it was 3 hours, once it was a week.
So I don't have any way to check if some app is causing the problems.

LibertyMarine said:
upload it on youtube and post the link.
And something else. Make a factory reset again and then don't install any apps. Does the error also occure?
Click to expand...
Click to collapse
Im new to XDA forums and hence the site does not allow me to post URLS. However I have uploaded the video to youtube.
If you put 'HTC One screen problem Aniruddha Joshi ' in the youtube search box, you will find my video.
Im sorry I couldnt think of any other way
I did not install anything out of the ordinary. Just updated the existing google apps and installed facebook, twitter and whatsapp! No crazy apks or unknown apps.
Also, once I factory reset the phone, it starts working perfectly and there is no way to know the time after which it starts giving problems again. Once it was 3 hours, once it was a week.
So I don't have any way to check if some app is causing the problems.

anibjoshi said:
Im new to XDA forums and hence the site does not allow me to post URLS. However I have uploaded the video to youtube.
If you put 'HTC One screen problem Aniruddha Joshi ' in the youtube search box, you will find my video.
Im sorry I couldnt think of any other way
I did not install anything out of the ordinary. Just updated the existing google apps and installed facebook, twitter and whatsapp! No crazy apks or unknown apps.
Also, once I factory reset the phone, it starts working perfectly and there is no way to know the time after which it starts giving problems again. Once it was 3 hours, once it was a week.
So I don't have any way to check if some app is causing the problems.
Click to expand...
Click to collapse
after seeing your video, I am even more confused. I really don't know what could cause this problem. But the fact, that I didn't have this issue and almost no other person too, makes me think about a hardware defect. But the randomness and that it only occures after several days don't support this theory. So the only thing we can do about his is basic troubleshooting.
- 1) Try to flash Cyanogenmod and try this mod for several days
- 2) Try another Rom, for example: Omni Rom
- 3) Try to use a different Kernel for GPE stock.
- 4) Use a RUU that matches for you
Sorry, I don't have any other ideas left! But after this troubleshooting we may get new information or gain some knowledge that allows us to determine the cause of this error more exactly!

anibjoshi said:
Hey guys,
I bought an HTC One about 15 days ago. Within 2-3 days of using it, I started getting problems with the display screen. I suppose this problem was seen by few people who owned the HTC One X but I couldnt find any useful solutions in those formums hence im posting here.
This is what happens:
1. Whenever I receive a call, the screen goes black and doesnot turn on until I hang up the call. This effectively makes the device useless as a phone, as I can't see who is calling and also during call I cannot access the screen.
2. Sometimes, there is a delay with the power button. When I press the power button, the touchscreen becomes responsive but the display doesn't turn on.
The problem is, if I factory reset the device, it starts working perfectly again!! Again after about 2 days it starts the same problems.
So I thought it was a software issue and so, I got s-off and installed the GPE Rom on the device. 7 days passed, no problems. On the 8th day, the same problem occured again. And as earlier, factory resetting solved the problem.
Is this a software issue, hardware issue or something else I dont know about?
I have taken a video of the device malfunctioning, but I don't know if I can post it as an attachment.
Thanks in advance!
Click to expand...
Click to collapse
Try flashing a Sense ROM, like ARHD or MaximusHD?
Enviado de meu HTC One usando Tapatalk

LibertyMarine said:
after seeing your video, I am even more confused. I really don't know what could cause this problem. But the fact, that I didn't have this issue and almost no other person too, makes me think about a hardware defect. But the randomness and that it only occures after several days don't support this theory. So the only thing we can do about his is basic troubleshooting.
- 1) Try to flash Cyanogenmod and try this mod for several days
- 2) Try another Rom, for example: Omni Rom
- 3) Try to use a different Kernel for GPE stock.
- 4) Use a RUU that matches for you
Sorry, I don't have any other ideas left! But after this troubleshooting we may get new information or gain some knowledge that allows us to determine the cause of this error more exactly!
Click to expand...
Click to collapse
The original device shipped with sense Rom. I flashed GPE to check if it was a software fault. But no luck. It gave the same problem although significantly later(about a week after I flashed it).
One more thing, I hope this gives some more information..
One time, I had rooted the device and installed a custom recovery. The phone was then working perfectly for about 4-5 days. and then later when I went ahead and unrooted the device, it immediately started giving problems. So I rooted it again hoping that the problem will go away, but no luck...the problem persisted. So, I had no option than to factory reset again, at which point it started working perfectly again.
This is all so bizarre, I have never seen something like this happen
This is just a theory, but is it possible that there is a problem with the hardware which gets triggered only on certain conditions, like some interrupt, or flag or something like that?
So until those conditions are not met, the device runs perfectly, and when they are, it starts giving issues.
Thats all i can think of as the reason.

well its clearly something youre installing if it is occuring after a few days, a root app which controls your sensor or brightness probably, do you have apps of that nature?

IINexusII said:
well its clearly something youre installing if it is occuring after a few days, a root app which controls your sensor or brightness probably, do you have apps of that nature?
Click to expand...
Click to collapse
No I rooted the device but did not install any root apps...i unrooted the device to install the GPE Rom(not necessary i know, but it seemed like a proper way) and found that it started giving problems immediately. Can non-root regular apps also cause such problems? I had installed only a limited number of apps anyway, updated the pre installed apps, facebook, twitter, whatsapp, some games..thats it..nothing wierd..

Might be a Screen-Off max. frequency issue. Like the phone gets only 500Mhz in sleep mode at maximum. Which is to low for an incoming call. Could you install a app like Android Tuner or Trickster Mod to check your Screen-Off Max frequency. If it`s that low, set it to ~1000Mhz.

anibjoshi said:
The original device shipped with sense Rom. I flashed GPE to check if it was a software fault. But no luck. It gave the same problem although significantly later(about a week after I flashed it).
One more thing, I hope this gives some more information..
One time, I had rooted the device and installed a custom recovery. The phone was then working perfectly for about 4-5 days. and then later when I went ahead and unrooted the device, it immediately started giving problems. So I rooted it again hoping that the problem will go away, but no luck...the problem persisted. So, I had no option than to factory reset again, at which point it started working perfectly again.
This is all so bizarre, I have never seen something like this happen
This is just a theory, but is it possible that there is a problem with the hardware which gets triggered only on certain conditions, like some interrupt, or flag or something like that?
So until those conditions are not met, the device runs perfectly, and when they are, it starts giving issues.
Thats all i can think of as the reason.
Click to expand...
Click to collapse
That is very stange indeed. As I don't know any other causes for this error than:
Underclocked CPU or/and GPU on screen off
Root application that controls the brightness
Hardware issue(But what would cause this???)
I can only advice you:
Since you are S OFF, take a RUU, and follow this guide and ****ing set back your device back to stock! Don't root it! Don't use custom kernels. Don't install any strange apps that may control your display brightness. SERIOUSLY! Don't install an app that controls brighness even if it works on a friends phone! Just don't!
And if you still get this issue: It is a hardware issue! If you followed step by step the instruction and if you did everything I told you to do, it HAS to be a hardware issue! The fact that the error didn't appear on GPE that fast is caused by the lower performance requierement by GPE! So I seriously have doubt that this issue is caused by a hardware defect. But it isn't impossible for sure. I just have the impression that you changed some system files and you didn't know what you were doing. This is NOT against you, but it seems to be a reasonable possibility because a factory doens't reset the /system partiton.
P.S.
I'd be very kind if you hit the thanks button since we, the community, are really trying to help you.

LibertyMarine said:
That is very stange indeed. As I don't know any other causes for this error than:
Underclocked CPU or/and GPU on screen off
Root application that controls the brightness
Hardware issue(But what would cause this???)
I can only advice you:
Since you are S OFF, take a RUU, and follow this guide and ****ing set back your device back to stock! Don't root it! Don't use custom kernels. Don't install any strange apps that may control your display brightness. SERIOUSLY! Don't install an app that controls brighness even if it works on a friends phone! Just don't!
And if you still get this issue: It is a hardware issue! If you followed step by step the instruction and if you did everything I told you to do, it HAS to be a hardware issue! The fact that the error didn't appear on GPE that fast is caused by the lower performance requierement by GPE! So I seriously have doubt that this issue is caused by a hardware defect. But it isn't impossible for sure. I just have the impression that you changed some system files and you didn't know what you were doing. This is NOT against you, but it seems to be a reasonable possibility because a factory doens't reset the /system partiton.
P.S.
I'd be very kind if you hit the thanks button since we, the community, are really trying to help you.
Click to expand...
Click to collapse
Agreed, trying following the guide and if it doesn't work make it s-on and send it to HTC for them to give a look.
Sent from my HTC One

LibertyMarine said:
That is very stange indeed. As I don't know any other causes for this error than:
Underclocked CPU or/and GPU on screen off
Root application that controls the brightness
Hardware issue(But what would cause this???)
I can only advice you:
Since you are S OFF, take a RUU, and follow this guide and ****ing set back your device back to stock! Don't root it! Don't use custom kernels. Don't install any strange apps that may control your display brightness. SERIOUSLY! Don't install an app that controls brighness even if it works on a friends phone! Just don't!
And if you still get this issue: It is a hardware issue! If you followed step by step the instruction and if you did everything I told you to do, it HAS to be a hardware issue! The fact that the error didn't appear on GPE that fast is caused by the lower performance requierement by GPE! So I seriously have doubt that this issue is caused by a hardware defect. But it isn't impossible for sure. I just have the impression that you changed some system files and you didn't know what you were doing. This is NOT against you, but it seems to be a reasonable possibility because a factory doens't reset the /system partiton.
P.S.
I'd be very kind if you hit the thanks button since we, the community, are really trying to help you.
Click to expand...
Click to collapse
I will definitely follow your guide and try to troubleshoot the problem. I hope its not some hardware defect and I dont have to send the device to HTC. I've heard those guys are poor at customer service
Thanks a lot, you've been a great help!
Btw, I was trying to find that Thanks button since the first day, I just couldn't figure out where it was. I just did.
Thanks again

Yup try installing kernel and custom rom.
Remove the case and try ( i know this is stupid thing but can give it a try)

Jvov said:
Agreed, trying following the guide and if it doesn't work make it s-on and send it to HTC for them to give a look.
Sent from my HTC One
Click to expand...
Click to collapse
Thanks for your help buddy! I really appreciate it!

anibjoshi said:
I will definitely follow your guide and try to troubleshoot the problem. I hope its not some hardware defect and I dont have to send the device to HTC. I've heard those guys are poor at customer service
Thanks a lot, you've been a great help!
Btw, I was trying to find that Thanks button since the first day, I just couldn't figure out where it was. I just did.
Thanks again
Click to expand...
Click to collapse
Thanks ! That's awesome and gives so much motivation! If you find out that you have a hardware defect and that you have to send it to HTC, I'll give you some information how to deal with those guys that you get your warranty.

[Q] Incredible slow, frequently frozen Xperia SP - What to do..

Hey guys,
I've upgraded from a Xperia Arc to a Xperia SP, hoping for a speed upgrade, going from a 1.0Ghz single core to a 1.5ghz dual core. (a Z(1) was not an option). Strangely, out of the box, the thing felt kinda slow/laggy but I thought "let's give it a try".
Now almost two months later, things haven't been any better. In fact, it regularly freezes completely and while writing this post, I can't even turn it on anymore. I closed the screen, but it doesn't goes on anymore (with 83% battery) .. But that's a different issue.
I'm really hoping what could fix this issue. I'm preparing for a factory reset, let's hope that fixes everything. Yet I'd ask: What more can I do than a complete factory reset. (Does it matters doing a factory reset from inside the phone (@ options > security/storage), the boot loader, or when it's connected to my PC?
I hope someone knows a solution!
Wish I could upgrade to Cyanogenmod, but that would void my warranty (right?), which is absolutely not an option.
Thanks!

Suggestions
First of all,
Are you on Android 4.3 or 4.1.2?
If you are on 4.3, it is expected to be a little laggy or buggy (No offence intended)
For this, what you could do is wait for a new update or downgrade to 4.1.2.
There is also another fix to make your phone a little less laggy.
For that you need to root your phone and edit the build.prop.
Second of all, you can try CyanogenMod without voiding your warranty.
For that you have to backup your TA and then unlock the bootloader. That is how you can use CyanogenMod and then again restore your TA when you are going to a Sony Centre or something like that.
A factory reset may solve somethings but not all. :crying:

Just factory resetted and it freezes on pretty much everything I do.. Just a simple swipe down to open the notification bar freezes the phone for about 2 seconds. Even a Nokia 3310 could handle these simple tasks quicker.. :s
Oh and I'm on 4.3 right now.

Blackvibes said:
Just factory resetted and it freezes on pretty much everything I do.. Just a simple swipe down to open the notification bar freezes the phone for about 2 seconds. Even a Nokia 3310 could handle these simple tasks quicker.. :s
Oh and I'm on 4.3 right now.
Click to expand...
Click to collapse
Flash 4.1.2. I got no lags what so ever

Nanostray said:
Flash 4.1.2. I got no lags what so ever
Click to expand...
Click to collapse
I updated from 4.1.2 to 4.3 in the hope it got better, but it got worse. However, 4.1.2 was a pain in the ass to, where it hangs all the time, taking the keyboard to show up a few seconds (@ SMS / playstore / else) (default and Swiftkey) or just opening the notification tray..
So simply flashing 4.1.2. would not solve it, I'm afraid.

Blackvibes said:
I updated from 4.1.2 to 4.3 in the hope it got better, but it got worse. However, 4.1.2 was a pain in the ass to, where it hangs all the time, taking the keyboard to show up a few seconds (@ SMS / playstore / else) (default and Swiftkey) or just opening the notification tray..
So simply flashing 4.1.2. would not solve it, I'm afraid.
Click to expand...
Click to collapse
Maybe use another tft of the .254 than the one you used this time?

Nanostray said:
Maybe use another tft of the .254 than the one you used this time?
Click to expand...
Click to collapse
I'm kinda unsure what you mean. I'm currently on 4.3 -> .266 (build number right?). This one is still unrooted and, even though someone spoke about backing up the TA, since this is not my phone, but my girlfriend's, I'm not sure if I want to dare that.
If it was my owns, that wouldn't be a problem..

Blackvibes said:
I'm kinda unsure what you mean. I'm currently on 4.3 -> .266 (build number right?). This one is still unrooted and, even though someone spoke about backing up the TA, since this is not my phone, but my girlfriend's, I'm not sure if I want to dare that.
If it was my owns, that wouldn't be a problem..
Click to expand...
Click to collapse
backing up TA means unlocking your bootloader so you can flash a custom kernel. 4.3 is indeed .266, but in my opinion you better flash a 4.1.2 stock rom (build number .254)

intolerable
Here the same thing, updated to version 4.3 and the bugs started ... When my phone battery was charging the night, the screen would shut down and forced me to use the physical reset button. Doomlord installed Kernel 0.5, was even worse, I'm thinking of going back to 4.1, even with the bugs it had, I could still use the phone ...

Let me tell you something,many of my friends that using sony,they will complained something was wrong like self restart,becoming typo while charging(touchscreen loses accuracy) and laggy+freezing when they was bought it not more than 2 weeks,and then they don't feel these problem anymore after about 2 months,i think you should go to sony service center,1.3 Ghz dualcore shouldn't freezing,it might a hardware problem or buggy software,hope this help,dont forget to click thanks sorry im just need thanks
Sent from my N986 using xda premium