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..
Related
Data wont turn back on after shutting off WIFI sometimes unless rebooting phone. I have Cyanogenmod-7.1.0-Fscinate on my phone was wondering if anyone is having the same thing. Or is there a bug out there that needs fixed. I have tried turning it on Plane mod and off to see if that would turn it back on. And i also tired turn DATA enabled off and turned it back on but nothing had to reboot the and then it work any help please.
This has been a problem for some on mtd roms...I have never had much trouble witht it tho. My only advice is to never leave both wifi and data on at the same time...
Thanks I was just wondering I new to this but im catching on pretty fast and I love this site lot of information.
FWIW, this issue is fixed on RickS' 12.2 MIUI build. Not sure if his fix could also be applied to CM7? Maybe one of the CM maintainers/kangers could get with Rick about it to see how he fixed it.
Hey guys,
I know there has been a couple of posts like this that I have found through searching but none have actually found a solution, so instead of resurrecting a old thread I thought I would start a new one.
Basically I am having some issues with my new pebble blue (yey) S3 . I have found that sometimes when the phone is sleeping when I press the power button to bring it out of sleep the lock screen begins to hang. This is followed by a number of different things, the screen either glitches for a bit and then begins to work or it stays locked and needs a battery pull. As well as this I've found that randomly either when charging or not and the phone is sleeping it simply becomes unresponsive, staying on a black screen and needing a battery pull to fix (this has only occured a few times, the hanging lock screen occurs quite often).
I have done some searching and found little in the way of a solution or what the problem is, however I have found that when the lock screen hangs -if it begins to work again after glitching out the 'WIFI connected to ****' appears at the bottom of the screen. Anyway if anyone has any ideas or also recieves this problem I would really appreciate some help as it's driving me crazy and I'm unsure if it is a common S3 bug or a faulty handset, in which case I have limited time to RMA.
Cheers in advance
Hmm, sounds like a faulty phone to me. Try taking it back to get it exchanged for onother one. S3 was built to fly not crawl.
You'll want to go through a process of elimination to figure out when might be causing it.
Something you can try and test with (one at a time)
-turn on airplane mode
-turn off live wallpaper
-shut down all running tasks
-change your lock screen security method
-limit the number of widgets running on all the screens
-reduce the number of active screens
Probably other things you can try to pull out of the equation, but thats a good start
After looking up dial-a-phones returns policy it would seem that I have 28 days to return if the handset is faulty, so this atleast gives me some breathing room to try out any suggestions for fixes. I will begin to eliminate each of the suggested items above however as the lock screen problem is intermittent it make take a day so actually see if it has had an effect, which is annoying at the least.
On another note a numberupted of people are stating high battery life on their devices however mine doesn't seem to be as good and I do have power saving on as well as nfc etc. turned off. This makes me believe my handset could have a fault, but tbf I haven't allowed for a discharge to 5% and the recharging to 100% which I heare allows for optimisation of the battery.
EDIT**** I have changed the lock screen previously and found it had no effect on the problem and I do not have a live wallpaper in use.
Phone Freezing after reboot and auto wifi signal found on.
Same here, been happening the last few days after I installed Avast. Also, turning off and on the auto on wifi seemed to replicate the problem.
The phone will boot to the lock screen and freeze a bit, and sometimes the news ticker freezes, and then after unlocked, I try to turn off wifi signal has been found on the notification dropdown and then tries to auto connect to wifi, the phone will freeze up if I dont turn it off in time.
Once the auto wifi connect is off and reboots, then the phone will keep glitching up until it catches up processing alot of processes it was trying to do for about 1/2 hr. Also, if phone freezes up for too long, like after trying too many time of unlocking the screen while freezing up, the phone gets stuck at the lock screen and the phone almost overheated, in an area right below the battery. I had to pull the battery out to cool it off.
It seems to be a glitch in the auto wifi, especially if alot of resources are being used. Once Avast was on my phone about 1.5GB RAM is being used sometimes and since has really slowed the phone down. Going uninstall alot of apps.
JCrinage said:
Hey guys,
I know there has been a couple of posts like this that I have found through searching but none have actually found a solution, so instead of resurrecting a old thread I thought I would start a new one.
Basically I am having some issues with my new pebble blue (yey) S3 . I have found that sometimes when the phone is sleeping when I press the power button to bring it out of sleep the lock screen begins to hang. This is followed by a number of different things, the screen either glitches for a bit and then begins to work or it stays locked and needs a battery pull. As well as this I've found that randomly either when charging or not and the phone is sleeping it simply becomes unresponsive, staying on a black screen and needing a battery pull to fix (this has only occured a few times, the hanging lock screen occurs quite often).
I have done some searching and found little in the way of a solution or what the problem is, however I have found that when the lock screen hangs -if it begins to work again after glitching out the 'WIFI connected to ****' appears at the bottom of the screen. Anyway if anyone has any ideas or also recieves this problem I would really appreciate some help as it's driving me crazy and I'm unsure if it is a common S3 bug or a faulty handset, in which case I have limited time to RMA.
Cheers in advance
Click to expand...
Click to collapse
Same problem.
No problem if Wifi is switched off prior to sleep.
No problem if Wifi connection is still available.
Problem to lockscreen if Wifi connection is broken (move away from connected router).
Any suggestion?
sassorock said:
Same problem.
No problem if Wifi is switched off prior to sleep.
No problem if Wifi connection is still available.
Problem to lockscreen if Wifi connection is broken (move away from connected router).
Any suggestion?
Click to expand...
Click to collapse
Exactly the same here. Driving me crazy. I did root the phone using the Samsung Galaxy S3 Toolkit. I don't know if the problem also exists on non rooted devices.
S3 black screen after unlocking
Has there anyone experience S3's screen went on black? I have pebble blue S3 - GT-I9300. Cases when unlocking, answering an incoming call or attempting to turn off an
alarm? Mine happens when after unlocking the screen then it goes black and screen becomes unresponsive. It happens intermittently and even after 3 times of
reprogramming. I am now going to have it replaced. I am having a lot of troubles -- it exits on its own when im reading or composing an SMS; files were deleted after
restarting the unit, and an app opens up even not touching the scree. This is expensive and I am paying a lot just to experience this king of inconvenience.
DavidNieuwpoort said:
Exactly the same here. Driving me crazy. I did root the phone using the Samsung Galaxy S3 Toolkit. I don't know if the problem also exists on non rooted devices.
Click to expand...
Click to collapse
I also rooted my S3 a few days ago (with the S3 toolkit), and have had lots of problems with unresponsive lockscreens (I use PIN, because of exchange connection). It takes a few seconds or maybe up to as long a minute before I'm able to punch in the PIN-numbers. Before this the screen lights up but does not respond to input.
But the WiFi-connection issue might be what is the triggering factor, because after a boot it wotks just fine for several hours, if I'm not moving out of my current WiFi zone. First I thought it was either Secure Settings or Tasker that made my device lock up in this matter, but now as they are both uninstalled, the problem still occurs.
Are you running some kind of custom rom, or just the latest stock ROM, but rooted?
Flodas said:
I also rooted my S3 a few days ago (with the S3 toolkit), and have had lots of problems with unresponsive lockscreens (I use PIN, because of exchange connection). It takes a few seconds or maybe up to as long a minute before I'm able to punch in the PIN-numbers. Before this the screen lights up but does not respond to input.
But the WiFi-connection issue might be what is the triggering factor, because after a boot it wotks just fine for several hours, if I'm not moving out of my current WiFi zone. First I thought it was either Secure Settings or Tasker that made my device lock up in this matter, but now as they are both uninstalled, the problem still occurs.
Are you running some kind of custom rom, or just the latest stock ROM, but rooted?
Click to expand...
Click to collapse
Just the latest stock ROM but rooted. I've found out that turning off the wifi power safe mode fixes the problem for me. To do this:
- In the dailer enter *#0011#
- Press the menu key
- Select wifi
- Press the on/off button.
The wifi power safe mode will however be turned on during boot. So rebooting will set it back on.
*#0011# seems does the trick. But is annoying had to do this every time after power off (change battery, change Sim, flying).... Anyway to keep the setting?
I am also on stock Rom and rooted. Interested to know any non-rooted phone got this problem?
BTW. I found a quick (at least quicker than pull the battery) way to get out of the forzen lock screen (sometimes forgot to do the 0011 trick): press the power button (screen will Dim instead of OFF), then hold the home button for few seconds, as soon as you see the "menu" and "back" button lit up, the lock is un-freeze...
A permanent solution is appreciated for such an advance phone....
sassorock said:
*#0011# seems does the trick. But is annoying had to do this every time after power off (change battery, change Sim, flying).... Anyway to keep the setting?
Click to expand...
Click to collapse
Not that I know of.
Problem solved. For me anyway. Hope works for all of you having the same trouble.
My trouble begin with recent upgrade to LH3. My S3 was rooted by S3 toolkit v2.0. CWM installed was v4 something.
I un-rooted the phone. Uninstalled S3 toolkit v2.0. Re-installed the S3 Toolkit v5.0. Rooted the phone again (CWM become v6....).
I do not know it was CWM version caused the trouble or not. But my S3 is ok now.
I got it on my non-rooted phone, any additional solutions/suggestions? or service?
I found solution for problem . And my phone is working well. I downloaded rom file android 4.1.2 and flash my phone
JB 4.1.1 caused these WiFi issues on my phone
Jodatnia said:
I found solution for problem . And my phone is working well. I downloaded rom file android 4.1.2 and flash my phone
Click to expand...
Click to collapse
Exact opposite for me...never had the problem then since loading stock JB 4.1.1 with root I get lockups or freezes whenever WiFi is turned off or I leave my router's range. As soon as I disconnect from WiFi the whole phone freezes.
The *#0010# also locks up the phone when I turn off the WiFi power saving feature.
None of this happened before JB...and I replaced my phone with week via warranty due to this and the new phone does the exact same thing as soon as I upgraded to JB with root.
Any ideas?
Black screen / random reboot solution
Hi All,
I've had the black screen / random reboot issue for a few days. The only way to restore functionality on black screen lockup was to remove the battery.
I tried changing to Chrome browser and stopping the stock browser as suggested in some threads but it kept crashing.
I searched everywhere and most threads suggest a dodgy motherboard.
For me the issue was related to either a single PDF download via the stock browser or the fact I had quite alot of saved PDF files on my phone (S3 Stock firmware I9300XXELLA)
After deleting all the files listed in Internet downloads (look for Downloads with a green arrow Icon in apps) my trusty S3 has returned to normal. No black screen lockups, no hanging, runs like a dream!
I appreciate this may not solve everyones black sceeen issues but I haven't found any other thread with this solution. Hope it works for you.
Thanks,
Giz.
giz_zard said:
Hi All,
I've had the black screen / random reboot issue for a few days. The only way to restore functionality on black screen lockup was to remove the battery.
I tried changing to Chrome browser and stopping the stock browser as suggested in some threads but it kept crashing.
I searched everywhere and most threads suggest a dodgy motherboard.
For me the issue was related to either a single PDF download via the stock browser or the fact I had quite alot of saved PDF files on my phone (S3 Stock firmware I9300XXELLA)
After deleting all the files listed in Internet downloads (look for Downloads with a green arrow Icon in apps) my trusty S3 has returned to normal. No black screen lockups, no hanging, runs like a dream!
I appreciate this may not solve everyones black sceeen issues but I haven't found any other thread with this solution. Hope it works for you.
Thanks,
Giz.
Click to expand...
Click to collapse
Thanks for the tip...
Was this happening on JB for you? You mention stock firmware (not familiar with I9300)...so I am guessing it was ICS.
For me the issues are with JB and I had no files at all in the Downloads folder after a certain point when I wiped / formatted the SDCard...so I do not think my lockups were related to PDFs. But I did (and still do) have a ton of music and a lot of movies on the External MicroSD Card....and quite a few custom notification and ringtone MP3s on the Internal SDCard. Next time I load JB I will run it a few days with none of this media loaded....
Jodatnia said:
I found solution for problem . And my phone is working well. I downloaded rom file android 4.1.2 and flash my phone
Click to expand...
Click to collapse
For me this also worked. Resolved everything. (on i9300 int)
Boomer6345 said:
Thanks for the tip...
Was this happening on JB for you? You mention stock firmware (not familiar with I9300)...so I am guessing it was ICS.
For me the issues are with JB and I had no files at all in the Downloads folder after a certain point when I wiped / formatted the SDCard...so I do not think my lockups were related to PDFs. But I did (and still do) have a ton of music and a lot of movies on the External MicroSD Card....and quite a few custom notification and ringtone MP3s on the Internal SDCard. Next time I load JB I will run it a few days with none of this media loaded....
Click to expand...
Click to collapse
This is on JB 4.1.2, Phone had been updated to 4.1.2 for about a month. The issues started after a pdf download. Once all pdf's were deleted the handset works perfectly.
Giz
Hi guys,
I have tried to search for a solution but couldnt find anyone having the same issue....so here goes
I am using a stock Vodafone AU rom 4.0.4 which is rooted......rooted used to remove drop box, navigaton (or something like that) and other bloatware.
However, after rooting - when Wifi is turned on but not connected to any network i seem to have screen issues. No response at all - when i press power button it doesnt turn off just dims, i press it again and screen lights up but yet no response. When i turned wifi off - this issue doesnt seem to happen. Also when i turn it on and connnect to my home network - no issue. Only seems to happen when after rooting + when wifi on and not connected to network.
Has anyone encountered this issue? Any help suggestions would be appreciated.
PS. I have restored factory settings, reinstalled firmware via odin and gone thru all settings on the phone. But under the above mentioned conditions - this issue happens. Seemed with out rooting - phone had no issues for last 5 days.
Perhaps this forum could help.
I received a used Xperia Mini [ST15i] as a xmas present from my bro-in-law.
It has Android 2.3.4 – Kernel is 2.6.32.9-perf
Build is 4.0.2.A.0.62
It had a lot of his apps on and foolishly I went into application manager and deleted a whole lot of stuff when suddenly the phone went into what I originally thought was a Haptic Feedback loop.
I was unable to power off so I had to remove Battery and restart from there. The loop starts slowly with one or two vibrates every 10 seconds then it becomes rapid and settles into an almost clock like rythm, two vibration per second.
I tried to get into settings to turn off the haptic feedback indicator but it seems like for each vibration [or tick] , an invisible ‘enter’ has been pressed somewhere on the screen so the only way to get into settings is to press the ‘back’ button and at the same time press the ‘settings’ button to interrupt the loop and after 5 vibrations or so I am able get into the ‘settings’ menu and un-tick the Haptic indicator. The phone goes quiet but the ‘clock’ or what ever process is looping continues. It completely blocks me out from doing anything unless I can interrupt it via pressing the back button.
To try get over this, I have reloaded the complete 150mb software via sony update. Afterward the problem still persisted. I have done both factory resets and still the loop process continues.
Have I screwed the Kernel? Any help or advice would be great. The phone is locked .
Sorry for you but it's an hardware problem (related to touchscreen). You have to send you mobile back to Sony.
Mine had the same issue out of the box and I had it replaced. The guy in the store told me it affects some batches (don't know which ones).
Soda_47 said:
Sorry for you but it's an hardware problem (related to touchscreen). You have to send you mobile back to Sony.
Mine had the same issue out of the box and I had it replaced. The guy in the store told me it affects some batches (don't know which ones).
Click to expand...
Click to collapse
Thanks Soda. Just chatted with Sony. Luckily phone is still under warranty. Cheers
I'm happy to help
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.