Database Develop

screen freezes when i wake my phone

Ever since i manually updated to frf91 sometimes when i try to wake my phone my screen freezes an i can't unlock it also when i try to power my phone back on it will vibrate 7 times an it wont come on. I guts take the battery out an put it back it to get my phone to turn back on. I've never had this problem until i manually updated my phone. I did a factory reset an it helped for a while but the problems come back. Has anyone had this problem an does anyone know how i can fix this? I'd really appreciate any help i can get

Help please

Is the bootloader unlocked?

this seems to be a common issue with FRF91, although most people's phones will unfreeze after a minute or two, does your backlight turn on and off when you press the power button?

Jep4444 said:
this seems to be a common issue with FRF91, although most people's phones will unfreeze after a minute or two, does your backlight turn on and off when you press the power button?
Click to expand...
Click to collapse
whether it unfreezes after a minute or two depends on what it's doing..there have been many times where i have to pull battery...........

rensky said:
whether it unfreezes after a minute or two depends on what it's doing..there have been many times where i have to pull battery...........
Click to expand...
Click to collapse
ya i have had to as well but most of the time it wakes just fine

No my bootloader is not unlocked an yea the backlight will come on but it won't unlock. Ive never tried waitin a min to see if it fixes itself i just usually pull the battery when it happens an sometimes when i try to turn my phone back on it does the 7 vibrating thing. Like i said before it never happened until frf91

I have an app called AutoKiller installed. It tweaks the Android system's inner memory management routines. it was set to something other than default. I changed it back to default, and haven't had a problem since. if you have this installed, maybe try and switch it to default settings.

Sounds like a data issue. A factory reset only wipes user data, You must wipe in recovery to wipe rom data. Also make sure you have the correct radio for the build especially coming from lower build. If that's the issue flash radio first to support the build. Then flash the rom.
Sent from my Nexus One using XDA App

How do u wipe in recovery? Yea im a newb lol

Also if i wipe in recovery will i still be on 2.2 or will i have to update to it again?

Sliding won't work anymore

Hey guys,
I could need a bit of help! It's now the third time I'm having this problem, don't ask me why. I've got the feeling that I read the whole forum here, but didn't find anything similiar.
The 1st time I didn't change anything (ok, rooted it, but nothing else)
The 2nd time I overclocked it slightly (~850-900 MHz)
Now I'm using MIUI.
But back to the problem:
I'm unable to use the keyboard, every time I'm sliding open the keyboard (even when it's turned off), it "crashes". The screen stops working or it freezes, the only way to turn it off is taking out the battery.
However, the bigger problem comes now: I'm barely able to restart it. It tries booting, but is restarting all the time or the screen is just turning on (in some angles you see that it is turned on but it's black). After many retries, it starts working, sometimes the bootloop is running 15min or i have to manually restart it 10 times or more. The strange thing is that the keyboard works fine, nevertheless I have to choose between using it opened (taking it with me becomes difficult ) or closed...
...the main problem now is flashing a new Rom, I'm currently trying it through the android sdk and adb, but using the power-button + x is easier
I don't think that I can solve the problem, I sent the device two times back (warranty till may 2012), but maybe someone here knows a bit more. My guess is that one of the sensors is broken, or some parts of the display that should manage the sliding process...
Anyway, thanks for your attention!
Web

If you already have Rom Manager, just click Reboot into Recovery..

inches0 said:
If you already have Rom Manager, just click Reboot into Recovery..
Click to expand...
Click to collapse
Tried to use one a time ago, but it wasn't working right....
However, now I'm not even able to boot it, the screen just flashes and turns off itself before trying to restart a few moments later....guess I lost my Milestone

Sbf back to stock?

taptaptouch said:
Sbf back to stock?
Click to expand...
Click to collapse
the computer isn't finding it anymore...I'll back up the data and try use my warranty... I hope that they don't complain about MIUI...
But I'm still not getting the point, why my mobile had these issues three times, although they "repaired" it twice...and nobody else is having the same problem

S4A Occasionally Won't Wake from Sleep

I can't figure out what's causing it. I don't have very many apps installed that didn't come with the phone, and any I did install were from the Play Store. I haven't done any modifications such as root to the device.
In order to bring it back to life, I have to either hold the power button down for 30 seconds to shut it down (or take out the battery) and power it back on.
Interestingly, if I have notifications waiting and the LED is flashing, that continues to flash even if the phone won't wake up.
I did 'disable' several of the bloatware apps in the app management area in Settings. I'm starting to think that must be what's causing it. Is there a particular bloatware app that should never be disabled? One that would cause this issue?
Other apps I've installed are things like Netflix, eBay, the app for my bank, and a TV-listings app. Pretty basic stuff. I don't think any of those would be the problem, would they?
Remaining battery doesn't appear to have an effect. It's happened with full battery and somewhat low battery.
'Services' that I use are Exchange push email and Gmail. I also have it Bluetooth synched to my car's hands-free thing.
Any help would be appreciated. Taking my phone out of my pocket to use it just to find that it's not responsive is very troublesome.
Thanks.
EDIT: For clarification, this is an AT&T version of the S4A.

EvilTelephone said:
I can't figure out what's causing it. I don't have very many apps installed that didn't come with the phone, and any I did install were from the Play Store. I haven't done any modifications such as root to the device.
In order to bring it back to life, I have to either hold the power button down for 30 seconds to shut it down (or take out the battery) and power it back on.
Interestingly, if I have notifications waiting and the LED is flashing, that continues to flash even if the phone won't wake up.
I did 'disable' several of the bloatware apps in the app management area in Settings. I'm starting to think that must be what's causing it. Is there a particular bloatware app that should never be disabled? One that would cause this issue?
Other apps I've installed are things like Netflix, eBay, the app for my bank, and a TV-listings app. Pretty basic stuff. I don't think any of those would be the problem, would they?
Remaining battery doesn't appear to have an effect. It's happened with full battery and somewhat low battery.
'Services' that I use are Exchange push email and Gmail. I also have it Bluetooth synched to my car's hands-free thing.
Any help would be appreciated. Taking my phone out of my pocket to use it just to find that it's not responsive is very troublesome.
Thanks.
EDIT: For clarification, this is an AT&T version of the S4A.
Click to expand...
Click to collapse
maybe u can enable back all the apps that u have disabled and see if it happens anymore.
u mentioned "the phone won't wake up" and "not responsive". do u mean that the screen stayed off and u are unable to get the screen to be on?

cfchong said:
u mentioned "the phone won't wake up" and "not responsive". do u mean that the screen stayed off and u are unable to get the screen to be on?
Click to expand...
Click to collapse
That's right. None of the buttons wake the phone up or turn on the screen. I can tell the phone is still 'on' though. It's not like it got powered off in my pocket.

The advice you've got is sound - if you think it might be because of disabled apps, re-enable them all and see if it keeps happening. If it doesn't... well then you disable them one at a time until it starts happening again.
Then you come back to the forum again and let everyone know which app never to disable.
If it doesn't stop happening after re-enabling all the apps... well then my guess would be a faulty device. Can't think of any other logical reason for it to behave like that. So try the apps first, if that doesn't help, "return to sender".

EvilTelephone said:
That's right. None of the buttons wake the phone up or turn on the screen. I can tell the phone is still 'on' though. It's not like it got powered off in my pocket.
Click to expand...
Click to collapse
if enabling back all system apps do not resolve the problem, try disabling all user apps to test. one of your downloaded app may be the cause.

Alright, over the past month I've done a bunch of testing. Here are my results.
1. Re-enabling all the system apps didn't help.
2. I uninstalled all my user apps. Didn't help.
3. I completely reset the phone to stock settings and formatted all storage. That didn't help.
4. I figured maybe it was something with bluetooth since it seemed to happen after I used bluetooth devices. I disabled bluetooth completely. It didn't help.
I'm out of ideas for the moment. Could the phone just be bad? I would wonder why the issue only happens occasionally.
Thanks.

Start a chat with Samsung. They have always been good to me.
GT-i9295(i537) running SafeStrap

I have the same problem, is there any solution, thanks

ogbeate said:
I have the same problem, is there any solution, thanks
Click to expand...
Click to collapse
Solved, rom change and ready, do not turn off more

I have the same problem in i9500. I now live in China and have purchased an s2, s3 and now the s4 from China Unicom. I have successfully rooted and flashed new ROMS (latest HK stock firmware) on the S2 and S3. When I bought the s4, it worked fine. I immediately flashed the latest stock HK ROM using Odin 3.07, After flashing, the phone is unresponsive after going into deep sleep meaning that nothing happens when I press the power button. After a long press of the power button, the phone will re-boot. Sometimes I have to pull the battery. Again, this phone is totally stock. I haven't added any applications. I re-flashed the stock China Unicom formware and I took the phone to the Samsung Service facility and they did a new flash. Phone worked great. I take it home, flash the HK ROM with Odin...same results; phone is unresponsive after going into deep sleep. I return to the Samsung service store and they again flash the phone. Phone works fine. What are they doing that I'm not doing? Could the partition table get corrupted during my flash processes. Should I try another version of Odin? Should I try a PIT file and try that? I'm downloading the ROM's from SamMobile. Thanks in advance for any suggestions.
Edit: I fixed this problem by upgrading to 4.3 which brought it's own set of problems.

phone won't boot- just backlight

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

[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.