No calls / Text after deep sleep - Sony Xperia P, U, Sola, Go

Guyz,
I am facing a strange problem with SXS. My SXS works normally during the day time or when its in use till night till i go to bed. After i went to bed and woke up in the morning if somebody tries to call me they get message that my phone is off, if they try to text me it doesn't come to me and shows in pending to sender. At the sametime it shows me good network and no errors on screen or for signal.
I have tested it myself for past two days when i wokeup and instead touching my SXS i tried calling from my different phone and i got message saying its Switched off. then if i try to send text or try to make call everything starts to work normal.
At night i am keeping data, wifi, bluetoot off and screen to min. Is anybody else saw this behavior or facing this strange issue. Any remedies you guyz can suggest.
Btw i am on .75 stock rom, unrooted. Please help!!!

Maybe an app you installed have timer or something....
Try factory reset.
Sent from my LT26i using Tapatalk 2

I have Profile scheduler installed but even after immediate change in profile there is no change. I mean today only i have waited to see what happens when the profile change at say 9:00 am in morning but no difference still its saying switched off. And when i sent an sms to friend everything starts to work normal.

Only an app can do this.
You have to try factory reset first.
Sent from my LT26i using Tapatalk 2

i have this problem too (croatia, t mobile, sim unlocked)
also one guy in USA...
this may be factory fault..

Related

Serious Lag Problem

Hello XDA,
Third day with my GS3, and I've already noticed and had to face on what could be a hardware issue if no one else on here has experienced it.
So I went to bed at 2PM this afternoon, phone is running absolutely fine its at 62% battery. I woke up at 5:30PM and the battery was 59%. So I started browsing my phone, I already had some messages so I replied to them, then I went on Emgadget. I revieved a text and the phone froize up, it just does this really really long vibrate for about 6 seconds, no notification sound and then boom.. it all comes back, the notification appears in the bar but the phone still does not make a sound. Its not just messaging that causes this blip, if the phone is in this state receiving any notification including a call will freeze the phone up.
I've noticed that during the time the phone is doing this, it won't make sounds while you type on the keyboard. Everything, like system sounds, will just stand completely silent even after the phone has resumed functionality.
After around 5-10 minutes the phone will just seemingly return to normal behaviour, I could be in mid-text and suddenly the keyboard start making noise again. Please somebody really help me with this, I do hope its software.
Just to note, this is not the first time I've had this issue today. I've experienced it multiple times in the past three.
Sent from my GT-I9300 using XDA
jaaystott said:
Hello XDA,
Third day with my GS3, and I've already noticed and had to face on what could be a hardware issue if no one else on here has experienced it.
So I went to bed at 2PM this afternoon, phone is running absolutely fine its at 62% battery. I woke up at 5:30PM and the battery was 59%. So I started browsing my phone, I already had some messages so I replied to them, then I went on Emgadget. I revieved a text and the phone froize up, it just does this really really long vibrate for about 6 seconds, no notification sound and then boom.. it all comes back, the notification appears in the bar but the phone still does not make a sound. Its not just messaging that causes this blip, if the phone is in this state receiving any notification including a call will freeze the phone up.
I've noticed that during the time the phone is doing this, it won't make sounds while you type on the keyboard. Everything, like system sounds, will just stand completely silent even after the phone has resumed functionality.
After around 5-10 minutes the phone will just seemingly return to normal behaviour, I could be in mid-text and suddenly the keyboard start making noise again. Please somebody really help me with this, I do hope its software.
Just to note, this is not the first time I've had this issue today. I've experienced it multiple times in the past three.
Sent from my GT-I9300 using XDA
Click to expand...
Click to collapse
Did you try a factory reset or an a FW update?
cba1986 said:
Did you try a factory reset or an a FW update?
Click to expand...
Click to collapse
I had a firmware update the other day, nothing worked. Thinking of downloading the software from SamMobile and reflashing.

[Q] Wifi sometimes doesn't turn on

Hi folks,
I have had this issue a few times now, basically when I try to tun wifi on using the quick settings tile it doesn't come on, if I then go into settings-wifi & try to turn it on using the toggle the toggle moves but doesn't change to the blue colour or say it is on, it just goes a light blue colour, if I then back out of settings & try again the toggle is back to off. I then basically have to turn the phone off & then back on (the quick boot feature in developer settings doesn't do anything) & when it boots up wifi is on.
Anybody else had this issue? The phone is getting replaced in a few days due to gap issues, over heating & camera lens not being centred anyway but just though I would check.
Cheers.
No one else have this issue?
BanziBaby said:
No one else have this issue?
Click to expand...
Click to collapse
I had this issue on .55 firmware. Haven't noticed it on .69 yet.
Cheers for the reply Jackos.
I had it both on the .55 firmware as well as the .69 firmware, have done factory reset etc but it still happens every few days, really stumped by it.
BanziBaby said:
Cheers for the reply Jackos.
I had it both on the .55 firmware as well as the .69 firmware, have done factory reset etc but it still happens every few days, really stumped by it.
Click to expand...
Click to collapse
I think I saw someone posting this issue at Sony Support Forums, let's hope they fix this in the next firmware revisions.
I'll keep you posted if this happens to me again on .69.
I have this happening to me, on .69 fw. Normally a restart will do.
Sent from my D6503 using XDA Premium 4 mobile app
@Jackos Cheers for keeping us posted mate
@pohsze Yeah mate, only way I have found so far to resolve it is to power off then back on, strange thing is wifi is on when phone finishes booting lol.
I have the exact same problem and I am on .55.
Sometimes I can't even turn Wifi off so I have to reboot. It is really weird because I don't know what triggers the bug.
I almost decided to return the phone but it is hard to recreate the error, and a reboot fixes it so I don't know if my phone company will accept the bug.
Since others have the same problem I hope they fix it in the new updates. Will come back when the .69 is released here.
I have same problem - switching in & out of AIrport mode cleared it.
I have the same problem.
First time I encountered it this morning.
Not sure from when wifi was not working for me.
In wifi settings no networks were shown.
Turning on wifi button would go light blue . . . but nothing would happen.
I selected Airport mode. Waited a moment. Then exited Airport mode . . . and wifi started working.
I'm on firmware .55
BanziBaby said:
Hi folks,
I have had this issue a few times now, basically when I try to tun wifi on using the quick settings tile it doesn't come on, if I then go into settings-wifi & try to turn it on using the toggle the toggle moves but doesn't change to the blue colour or say it is on, it just goes a light blue colour, if I then back out of settings & try again the toggle is back to off. I then basically have to turn the phone off & then back on (the quick boot feature in developer settings doesn't do anything) & when it boots up wifi is on.
Anybody else had this issue? The phone is getting replaced in a few days due to gap issues, over heating & camera lens not being centred anyway but just though I would check.
Cheers.
Click to expand...
Click to collapse
Hey I get it sometimes too, just press and hold on the wifi icon and then manually turn wifi on in the wifi settings, works fine after that. Just a minor bug.
I have also experienced the exact same problem on the newest firmware. Only happened once, and going in to the actual WiFi settings didn't solve it, since the button turned light blue as described. Strangely after a little while when the phone was inactive it started working all by itself.
Phones:
Samsung Galaxy S I9000
Asus Padfone 2
Sony Xperia Z2
____________________________
Android user since mid 2010
Same issue
Hello all,
I have the same problem when I tried to turn Wifi on by accessing Quick Settings and pressing Wifi button.
It works again after 10-15 times pressing Wifi icon.
It just happened last few days and I didn't have any system update recently.
Im also having the same issue. Anyone managed to get a fix for this?
Same issue
Im also having the same issue.
Anyone had a solution for this :/ ?
I don't think i have this issue yet since I just got the phone, but I remember when I setup my wifi connection there was an option to enable/disable wifi based on location. Could it be that the phone's GPS location hasn't update yet and think you are close to your wifi location thus won't let you turn on? May be disable this feature and report back if you guys still have this issue.
I am on .167 and this is happening to me more and more often it seems like it is getting worse. If I go into settings/wifi I get a white screen that says tunring wifi on and no further change. This usually starts occurring 18 hours or so after I reboot. It looks like no one has any idea what is wrong.
Fred
I have this same issue, a restart fixed this fora couple of days but now it seems the Wifi wont start up at all
Still had some warranty so returned the phone at the store that I bought it at.
Had the issue from the moment I got the phone from my gf (she has a new one) and did a factory reset.
After that I have flashed 3 different versions on it and for all the WiFi didn't work.
Let's see what happens after I get the phone back..

[Q] S3 Freezing, Unfortunately X has stopped

Hi guys,
I am having a very frustrating problem with my S3. I had the google.process.gapps stopping randomly for a few days, but that wasn't more than an annoyance. Last night, my battery run out and when I plugged my S3 it in and turned it on, all hell broke loose. Starting with the lock screen I have been getting non-stop "Unfortunately X has stopped" with X being anything from LogsProvider, NfcService, ContextProvider, SysScope and the already mentioned google.process.gapps. As long as I stay on the lock screen I can click these away...eventually. If I try to go into Settings or in the normal screen I get another batch of those messages, but this time the SysScope one, just keeps coming and coming and coming, so that I can't do absolutely anything. I have tried the same in Safe Mode but there wasn't any change.
Please tell me there is something I can do, other than a factory wipe.
CoolBreeze83 said:
Hi guys,
I am having a very frustrating problem with my S3. I had the google.process.gapps stopping randomly for a few days, but that wasn't more than an annoyance. Last night, my battery run out and when I plugged my S3 it in and turned it on, all hell broke loose. Starting with the lock screen I have been getting non-stop "Unfortunately X has stopped" with X being anything from LogsProvider, NfcService, ContextProvider, SysScope and the already mentioned google.process.gapps. As long as I stay on the lock screen I can click these away...eventually. If I try to go into Settings or in the normal screen I get another batch of those messages, but this time the SysScope one, just keeps coming and coming and coming, so that I can't do absolutely anything. I have tried the same in Safe Mode but there wasn't any change.
Please tell me there is something I can do, other than a factory wipe.
Click to expand...
Click to collapse
Do a factory wipe.
As above, try a wipe first -but letting your battery run out can corrupt a partition. You may need to reflash your firmware.
Sent from my GT-I9300 using Tapatalk

Screen turning on repeatedly

Hey everyone!
I picked up a Gear S about a week ago and until today, I've had no problems. I took the watch off charge this morning and everything was working as fine, used some apps etc, no issues. Then I checked my phone for updates and saw that the Gear Manager app had an update and I installed it. Since then, the screen on my Gear S has been constantly turning on and off. It will turn for about 9 seconds, then switch off and back on 2 seconds later. Turning the screen on manually works but everything is pretty much frozen. I can periodically get as far as the pedometer (because there's an icon for it on the home screen) or to the Apps menu but no further and then the screen will switch itself off.
I'm not sure whether an update to the Gear Manager app should affect the watch itself but I know that when I wiped my phone a few days ago and went to set up the Manager again, it factory reset the watch so I assume there is a direct connection between the software. I've tried disabling both Bluetooth and the remote connection to check if Gear Manager is causing the screen to behave strangely but it's still turning on and off. It's impossible to do a soft reset through the Gear S itself as the screen switches off before I can get to settings and I've tried doing a hard reset but nothing works.
I tried searching on Google for anyone having similar issues and the only thread I can find was posted on Android Central (yesterday I think) with a few people saying that they're having the same problem which makes me thing that the update to Gear Manager is the issue.
Edit: The only screen that doesn't seem to be affected is the PIN lock screen. Screen switches off there as normal and does not come back on.
Edit 2: I've never reset the Gear S before (and I only noticed the factory reset mentioned above after it was finished) but when I attempt to do a hard reset, the watch just reboots as normal without anything happening and all info / data is still there. I presume this really shouldn't be the case?
UPDATE: I'm an idiot / Samsung's instructions on how to do a hard reset are awful.
I decided to Google how to do a hard reset and discovered that when in the Recovery Menu, you need to hold down the Power button to choose an option (Samsung's instructions just tell you to press the Power button until you highlight what you want and I assumed it would automatically choose that after a few seconds because the phone would restart for me). Watch is now factory reset and so far the screen issue appears to be resolved. Another four hours of transferring music it is then.
@BOZG can you post a link to that thread?
I have the Same problem. Sometimes changing a clock face or installing/uninstalling a program seems to make it stop. I have yet to find a good consistent solution. Restarts etc. don't help. Hard reset will fix it but last time I just changed settings on and off and powered the phone on and off and eventually it stopped.
It seems related to when the phone is connected remotely over a cell network. I have the AT&T unlocked with a T-Mobile regular line, not the wearable line since I have a 5 for $100 business plan and the 5th line was not being used. Doubt that makes a difference though.
Followup:
Just now I had the watch off and charged to 100%. Powered up with phone off. Same issue. Watch face loads, the hands change to the current time, then it slides down the screen and looks like a reload because when it comes back up the time isn't correct. The hands reset to the right time. This happens a few times. I power the phone up. Bluetooth connects. I open the gear manager on the phone and it stops.
Will try to repost if that's repeatable. I hope they fix it because it burns quite a bit of battery when it happens. It gets warm so it's running the CPU a lot whatever it is.
allow to power down
BOZG said:
Hey everyone!
I picked up a Gear S about a week ago and until today, I've had no problems. I took the watch off charge this morning and everything was working as fine, used some apps etc, no issues. Then I checked my phone for updates and saw that the Gear Manager app had an update and I installed it. Since then, the screen on my Gear S has been constantly turning on and off. It will turn for about 9 seconds, then switch off and back on 2 seconds later. Turning the screen on manually works but everything is pretty much frozen. I can periodically get as far as the pedometer (because there's an icon for it on the home screen) or to the Apps menu but no further and then the screen will switch itself off.
I'm not sure whether an update to the Gear Manager app should affect the watch itself but I know that when I wiped my phone a few days ago and went to set up the Manager again, it factory reset the watch so I assume there is a direct connection between the software. I've tried disabling both Bluetooth and the remote connection to check if Gear Manager is causing the screen to behave strangely but it's still turning on and off. It's impossible to do a soft reset through the Gear S itself as the screen switches off before I can get to settings and I've tried doing a hard reset but nothing works.
I tried searching on Google for anyone having similar issues and the only thread I can find was posted on Android Central (yesterday I think) with a few people saying that they're having the same problem which makes me thing that the update to Gear Manager is the issue.
Edit: The only screen that doesn't seem to be affected is the PIN lock screen. Screen switches off there as normal and does not come back on.
Edit 2: I've never reset the Gear S before (and I only noticed the factory reset mentioned above after it was finished) but when I attempt to do a hard reset, the watch just reboots as normal without anything happening and all info / data is still there. I presume this really shouldn't be the case?
Click to expand...
Click to collapse
I left mine to use up all the battery,then when it switched off, i left for 2 days and when i switched back on... all fine again.
theroblog.com said:
@BOZG can you post a link to that thread?
I have the Same problem. Sometimes changing a clock face or installing/uninstalling a program seems to make it stop. I have yet to find a good consistent solution. Restarts etc. don't help. Hard reset will fix it but last time I just changed settings on and off and powered the phone on and off and eventually it stopped.
It seems related to when the phone is connected remotely over a cell network. I have the AT&T unlocked with a T-Mobile regular line, not the wearable line since I have a 5 for $100 business plan and the 5th line was not being used. Doubt that makes a difference though.
Followup:
Just now I had the watch off and charged to 100%. Powered up with phone off. Same issue. Watch face loads, the hands change to the current time, then it slides down the screen and looks like a reload because when it comes back up the time isn't correct. The hands reset to the right time. This happens a few times. I power the phone up. Bluetooth connects. I open the gear manager on the phone and it stops.
Will try to repost if that's repeatable. I hope they fix it because it burns quite a bit of battery when it happens. It gets warm so it's running the CPU a lot whatever it is.
Click to expand...
Click to collapse
samsung gear s screen on and off..looping
There you go. Not much to read there though as it's just me and OP. The problem re-emerged for me after a few days again so I was forced to do another hard reset to actually use the watch. I noticed it when I woke up in the morning and noticed that another update had been pushed to the Gear app. That's twice now that this has happened shortly or immediately after the Gear app was updated.
I haven't been able to uninstall an app / change clock face to see if it works as the watch is completely unusable when it happens to me. The Gear app registers that it's connected but it's impossible to change anything from there either and if I turn the watch off and back on again, the Gear app will no longer connect.
petethepete2000 said:
I left mine to use up all the battery,then when it switched off, i left for 2 days and when i switched back on... all fine again.
Click to expand...
Click to collapse
Not sure if I've actually tried letting the battery drain. I'll try that the next time it happens (if it happens).
I had the same problem after the update, a reboot didn't solve the problem. Eventually the battery drained. After a recharge most is fine but I never know which watch face will suddenly appear.
Same issue again. Didn't see the Gear app updating but there was an update released the day before. Going to switch off auto-updates and see if it definitely the problem. Just seems too coincidental that this problem starts right after an update is released for the Gear App.
petethepete2000 said:
I left mine to use up all the battery,then when it switched off, i left for 2 days and when i switched back on... all fine again.
Click to expand...
Click to collapse
Started doing it again yesterday so let the battery die and charged it fully and it didn't help. Left it on the box overnight and brought it to a Samsung Service Centre this morning and of course it was working again when I took it out of the box! Left it with them anyway so I'll see what happens.
I've had my Gear S a few weeks and it has also started doing this, I will give some of the suggestions here a go.....
EDIT: So opening the Gear Manager App once Bluetooth was connected brought my Gear S back to life. Phew!
It's only entered this state after I turned it off at night and then turned it back on in the morning - so it had been off roughly 8 hours. Upon turning it on the screen would cycle from the right time and notification numbers and the wrong time and wrong notification numbers too off again.
@ BOZG - Just wondering if you got your S back yet and if so, were they able to tell you what was causing this on/off problem. Mine just started doing it yesterday.
Also, how did you find the "Samsung Service Centre"?
holding the screen seems to cause it...
Had to send mine to Samsung for a new charging cradle and they updated the software to latest, when i got it back it seemed fine. Then i was messing about with it and was holding the screen to my chest for a while and that seemed to cause it to happen. It seems to be the screens gets too much activation and it flips out. I think this is what started the problem last time it happened.1
Switching to power saving mode seems to fix it for me... have to wait until it gets low on battery and when the low bat warning comes on, switch then... leave for a bit then switch back to normal.
I called Samsung Thursday and they sent me a UPS label and told me to send the watch, charging cradle and AC charging cord back in for service. She told me it takes about 7-14 days. We shall see.
Happy to have found this. </rant>I'm starting to get enough of this Samsung stuff. I had the note 2 and now I have the note 4 and gear S. That is mote then 1000 euro of equipment. And today when I tried the restore to fix this, both the phone and the watch rebooted. Crazy that they can not build good software and hardware for this price. </rant>
To me it seems that is freezes somehow when this happens. It kept jumping back to 22:10 time and changed to the watch-face and settings keep rolling back. It seems to happen to me, when the watch is off for some hours. The samsung way... no update to fix this.
solved for me
hi first of all sorry if i do any mistakes because English is not my language
i had similar problem and i found the solution at least in my case . THE PROBLEM IS NOT WITH THE GEAR S
all was ok using 4.4.2 kitkat on my note 3 before few months i upgrade with lollipop 5 official from sammobile via odin
from that moment the problems begin with the reconnection of the gear with the note
long time to connect and no auto reconnection only manual by turning off-on the bluetooth
i was boring to do format to the note3 so i left it as it
few weeks ago probably of gear manager update the gear start freezing and the screen turning on and off
first i do a factory reset and the gear was ok for a while but after it do the same but the next time the screen was not ok the colors was different so i send to service in Athens
the service in Athens is very fast and very helpful , is one of the reasons that i will difficult go with other manufacture , so they return me the gear saying that they change the motherboard and now there is new imei
but the gear that they send me was brand new except the band and the box. BUT after some time the same problem ..... i call them and they tell me to send it back so i send it and i receive it again but this time the say that the watch is ok
GUESS NOW .... i turn it on and after a while of the connection with my note AGAIN the same problem the screen on and off and freezing plus was overheat underneath
i was ready to call them and to say few words but they was closed ..... then i search the net and i found this post and i thing probably is not the gear the problem ,no hardware problem, i decide to do a test
i download the last working rom to my phone 4.4.2 and magically the problem disappears .... but now there is a software update on my phone lollipop 5 so i do the update and i was ready if the phone cause again the same problem
to return and stay with 4.4.2 But now all is ok the problem solved .... now is more of 24h and all are ok
i hope this will work for you also
Same problem
I have the same issue exactly - Note 4 with latest lollipop upgrade - it is very frustrating......I don't particularly want to have to move back an OS just to use the watch !
JALUK said:
I have the same issue exactly - Note 4 with latest lollipop upgrade - it is very frustrating......I don't particularly want to have to move back an OS just to use the watch !
Click to expand...
Click to collapse
Ok but doing a downgrade and all working ok you can do update again.... i am not with 4.4.2 i went to the latest 5.0 for me now and all are ok.
Maybe something was wrong with the update procedure.
UPDATE
the touch function of the 2nd gear stop working so i send it back and they send me new device
for a few days all was ok . But today when i restart the phone while the gear was disconnected the problem with screen turning on repeatedly appears again .
for sure is not problem of the gear , this is the 3rd device in my hands, something is wrong with the gear manager software .
i have also reconnection problems .... if the phone is far away and they lost Bluetooth connection the most of the times i must reconnect manually , the gear say disconnected but the note think is still connected
I wonder has anyone tried to reset the watch as a stand alone device and see if the problem happens? I know you might lose a lot of the blue tooth functionality but I think I will test it and see if the problem still happens.

S voice Problem

It's a few days that I'm not able to use s voice, from my gear s, to start new call, send new messages etc....
once s voice is started and I say something like "send message to ...." the app closes and the watch returns on the clock screen.
I restored to factory default, flashed the newest firmware, restored the phone....but nothing
Someone is facing the same problem?
Actually i'm facing the same problem... found any solution?
UPDATE:
I found that it's something about the Contacts. If you try to make a call, send a message or ask information about any person in your Gear S contact list, S Voice will just close and return to the clock screen. If you try to make a call by saying the actual phone-number it will work. Same for messages.
I'm still trying to figure out whats the problem. Already did a Factory reset to the Gear S two times without restoring any info and still not working. I'm gonna try to pair the Gear S with another device to check if the problem is not the pone (i don't think so...)
The same for me didn't figured out what is the cause of the problem...factory reset for both phone and smartwatch several times but didn't solved the problem... Sometimes works fine and sometimes not... Now it started to switch from a screen to another : black screen, watch, menu and so on until the battery is completely drained.... I though it was for the note 3 bluetooth's bug, but the various problems persist even with it turned off..
Most confused than ever
Inviato dal mio SM-N9005 utilizzando Tapatalk

Categories

Resources