Related
I know theres a poll on issues etc and rebooting is mentioned, but I feel it was too early to poll and people could have voted and had a reboot after...
So question is..... has your phone rebooted? Or just fine?
Also if you could mention how long you had it that would be great....
I just want to know exactly who is having reboots and who hasn't..
Not once on its own.
Sent from my LG-P999 using XDA Premium App
None so far.
None so far.
Zero.
Sent from my LG-P999 using XDA App
LOTS of reboots
I have had about 20 in two weeks. I am CURRENTLY getting CONTINUOUS reboots.
It had the LG logo and thinking bar, underneath it said "System checking". Now it has rebooted non-stop (6 times so far as I'm typing).
New phone should arrive on my doorstep within the next hour or so... fingers crossed.
once that I know of. No idea why. It just rebooted while on my desk idle.
In the one week I had the phone (preroot), never. Even after rooting it, never.
Haven't had any issues with mine.
Had 3 reboots in 5 days on my old phone. Nothing yet on new one so far. It has been 3 days. I noticed my old phone was alot hotter than this one. Possibly a hardware issue after all.
Guys, try to turn off gps, I did that and I have 0 reboot and 0 shut down today, I had a lot of reboots and phone turning off by itself before that. I'll see what happens when I charge it tonight and I'll let u guys know.
Sent from my LG-P999 using XDA App
Theres got to be something thats causing it.
results don't look so good..
Hmmm prerooted I had maybe one and some freezing and lag..
rooted no reboots except running eaglesblood rom and experimental kernel with pauls lag apparentky too much going on there. .
If your phone is rebooting constantly don't even waste your time return it for a new unit. The att galaxy s had the same prob and everyone waited for a fix only to find out it was hardware related....if your in the 14 day window don't even waste your time and end up with a refurb
Sent from my LG-P999 using XDA App
I bought my g2x a day after launch. For a few days, I didn't experience any reboots. After that they starting happening but not too often. Eventually (by yesterday), it was happening more often. Somewhere in that time frame I did a factory reset to try to improve battery life.
I called tmobile support yesterday and they made do another factory reset and not install any apps. It has been 16 hours without a reboot but that doesn't prove anything, really. First, it doesn't necessarily happen every day. Second, without any non-default apps installed, it may not be taxing the device enough. Third, even if it is an app's fault, it may not be directly the apps fault. Am I supposed to run no apps if that turns out to be the problem?
They will be calling back at three and I'm going to try to push them for a replacement. I'm also having reception issues and the battery could certainly last longer.
None here, gps is not turned off
Sent from my LG-P999 using XDA Premium App
I am on my 5th G2X... with a build date of 4/3/2011 and I have not had a reboot as of yet with GPS turned on. This has also been the best phone out of all those 5, I have a week left and if I experience problems I will be taking it back. As somoene said dont waste your time your better off returning it then waiting for a fix.
Berat said:
I am on my 5th G2X... with a build date of 4/3/2011 and I have not had a reboot as of yet with GPS turned on. This has also been the best phone out of all those 5, I have a week left and if I experience problems I will be taking it back. As somoene said dont waste your time your better off returning it then waiting for a fix.
Click to expand...
Click to collapse
Any advice on what to tell them so they'll take it back? The tmobile phone tech wants me to prove that it isn't an app...
none so far got it on May 3rd..
oldbustedjorn said:
Any advice on what to tell them so they'll take it back? The tmobile phone tech wants me to prove that it isn't an app...
Click to expand...
Click to collapse
I just took it to the store, told them the problems I was having mentioned the reboots, screen bleed, and data connection issues. Told them I was within the 14days and that Customer Care told me to come to the store and try and get a working phone. I wouldnt talk about the reboots as it may not happen in store if you have screen bleed its easier that way cause you can prove that.
Did you buy it in store, online or over the phone?
This is for stock unrooted peeps.
Anyone that has had reboot problems on their thunderbolts, still experiencing them after updating?
Wife's tbolt starting rebooting a couple times a day about a week ago. Did the update friday night and has rebooted twice since then. Thinking it might be hardware related if others have had their reboots fixed.
Probably going to call verizon next time it does this to try and get a replacement.
I've had only one that I've noticed so far, but that makes it less than the 3-4 daily I noticed with the most recent leak prior (mr2.5 thingee)
No reboots for me since the update. Of course Verzion only claimed this OTA would reduce the number of reboots not do away with them. I hope for you that they don't try to pull then when you ask for a new unit.
Start over from scratch do an app backup...uninstall all apps restart phone try favorite app first give couple hours or a day. slowly put apps back on right down time and date each app installed .doing this is a p.i.t.a .....some apps dont play nicely with others ...plus you dont want a p.o.s.reman phone....anyways this might take a couple of days.....sometimes verizon wont shoot from the hip and just replace .. reason i say this for a while 1st thing they do is hard reset phone and start over ...more or less have to prove problem make sure everytime u call have them note the account....lets see 10 imagios 6 collasped buttons 4 bluetooth failures .....fun fun...nothings easy with verizon
Look at it this way you could be stuck with a really start over flashing firmware with a windows phone cause hard reset sucks [email protected]#$
Sent from my ADR6400L using XDA App
scottthreet32 said:
Start over from scratch do an app backup...uninstall all apps restart phone try favorite app first give couple hours or a day. slowly put apps back on right down time and date each app installed .doing this is a p.i.t.a .....some apps dont play nicely with others ...plus you dont want a p.o.s.reman phone....anyways this might take a couple of days.....sometimes verizon wont shoot from the hip and just replace .. reason i say this for a while 1st thing they do is hard reset phone and start over ...more or less have to prove problem make sure everytime u call have them note the account....lets see 10 imagios 6 collasped buttons 4 bluetooth failures .....fun fun...nothings easy with verizon
Look at it this way you could be stuck with a really start over flashing firmware with a windows phone cause hard reset sucks [email protected]#$
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
she has no different apps than me and I don't have reboots. We'll give it a couple of days, start calling in and creating the history. New customer, I'm sure they would hate to lose us already...
jump ship and pay up the @#% to leave your stuck unless under 15 days then your stuck again because where you came from sucked plus to boot anywhere else is gonna what a deposit ....just because your phones not rebooting with same apps ...the phone is man made #$& happens the other phone might have hardware problems ok prove it...do what i said and track
Sent from my ADR6400L using XDA App
Had a few here, better but still angers me.
Sent from my ADR6400L using XDA Premium App
same story -- i'm still getting them occasionally but not as often. I was all excited about the update, but a few hours after it installed I was browsing the web and - bam - reboot. It's like a slap in the face. I've also been having a serious problem with my TB just discharging itself overnight... while plugged into the wall charger. I wake up and it has a completely dead battery which is a major PITA, doubly so because I use it as my alarm clock.
My TB has been up since the update on Friday. It used to reboot multiple times a day. Hope this lasts for me.
I'm stock and unrooted.
Sent from my ADR6400L using XDA App
nrfitchett4 said:
This is for stock unrooted peeps.
Anyone that has had reboot problems on their thunderbolts, still experiencing them after updating?
Wife's tbolt starting rebooting a couple times a day about a week ago. Did the update friday night and has rebooted twice since then. Thinking it might be hardware related if others have had their reboots fixed.
Probably going to call verizon next time it does this to try and get a replacement.
Click to expand...
Click to collapse
I have never had a reboot and I have been rooted since a week after owning the TBolt... I guess just lucky
Haven't had a reboot since memorial day weekend.
Never had a reboot before or after the update....I just bought my Tbolt two weeks ago, maybe they corrected the rebooting issues with the current hardware?? I mean if users are still rebooting after the update maybe its not software...
I've been really really lucky here I guess. I bought my Thunderbolt about a week after it came out and have had maybe 3-4 reboots since then. I have gone through a few roms/kernals/radios but never any issues. It must just be a hit/miss thing with hardware to be honest. Either that or the network, I'm in West Lafayette maybe our network is just far superior
The only gripe I have had is shutdowns, which IMO are more annoying because I can't just turn it back on, I have to pull the battery and wait a couple minutes before putting it back in and then waiting another minute before it responds to the power button to turn it back on again.
All in all I am happy with it compared to all others complaints on reboots. I would rather have a small number of reboots/shutdowns than a refurbished phone with possibly more issues.
I've been rebooting still like CRAZY. Before and after the update. I got on Verizon and received my phone on Thursday. It was rebooting over and over and over... I noticed it happened if I left wifi coverage at work or home. Even after the update, same thing! Rebooting over and over like no tomorrow.
I noticed that with LTE on it would loose connectivity all together until I manually rebooted. If I was on Edge or 3G it would stay up longer. I have since then turned off LTE and it has been fine, but still reboots every few hours.
kendive said:
I have never had a reboot and I have been rooted since a week after owning the TBolt... I guess just lucky
Click to expand...
Click to collapse
I have had 1 reboot after having mine for over a month or so now. Been rooted since day 1 and have changed radios multiple times along with ROMs/Kernels. I guess we are both lucky?
Never once had a reboot. Custom rom since day one though. Stock sucks.
On a helpful side though. Always best to do a hard reset after a update. I know its a pain but it is the best solution normally.
Sent from my Thunderbolt using XDA Premium App
Has anyone else came across the screen of death (random shutdown when idle and requires long pressing power to turn back on) with their Galaxy Tab 7+? I have this problem everyday and it seems like other Samsung phones had similiar problems like this one.
Does anyone know if there is a way to fix this? Supposively it may be a problem with the Wifi or reading the SD card when idle.
Sent from my GT-P6210 using xda premium
I Did a factory rest and haven't had one in two Weeks.
I did a factory reset last night and still have the same problem. Did you do a factory reset under "Settings > Privacy > Factory Reset"?
Didn't change a thing for me.
Sent from my GT-P6210 using xda premium
I occasionally get reboots, I can hear the sound when its in my pocket. Likely due to set cpu. My min is 500. I hear its related to on demand setting. I may uninstall if it persists.
the SOD issues is a known issue on some units.
While some units have it very frequently others don't.
The one i got from Fry's (and returned) had it.
The 3G version one i got from ipmart.com doesn't have it.
It seems like it may have something to do with the SD card reading. I removed mine and haven't had a problem since.
Sent from my GT-P6210 using xda premium
I take that back, just got SoD again. I'm really considering exchanging this for another one
Sent from my GT-P6210 using xda premium
charmartist said:
I did a factory reset last night and still have the same problem. Did you do a factory reset under "Settings > Privacy > Factory Reset"?
Didn't change a thing for me.
Sent from my GT-P6210 using xda premium
Click to expand...
Click to collapse
No I did mine from recovery. Power and the volume button closest to power. Select factory reset. I believe they are slightly different, but I am not positive of that. If that doesn't help, I'd return it if possible and get a different one. Here in the states most return periods have been extended Into January. Good luck.
Another thing you can try is using Odin to flash the retail ROM for the 6210 that is posted in the development section. I have had to do that several times trying to get cwm sorted, that may have fixed it. That's a good way of reloading the code, because I did get the sod several time prior to my first brick. After reloading the code, I forgot the problem even existed. Again good luck
charmartist said:
Has anyone else came across the screen of death (random shutdown when idle and requires long pressing power to turn back on) with their Galaxy Tab 7+? I have this problem everyday and it seems like other Samsung phones had similiar problems like this one.
Does anyone know if there is a way to fix this? Supposively it may be a problem with the Wifi or reading the SD card when idle.
Sent from my GT-P6210 using xda premium
Click to expand...
Click to collapse
I have had two Tab 7+ from Amazon. Both had the SOD problem. I returned both and now I will either wait until there is a fix from Samsung or will look for another tab.
I got them 2-3 times per day on my first unit...I exchanged it once Best Buy got another in stock and haven't had any issues at all. So yeah...if you're getting the SODs, exchange it if you can.
I had this too! I immediately asked for it to be returned. I didn't spend so much money on a device that randomly shuts down. Sending it back today..
I have only had one random reboot (that I know of). I have, however, had some apps like Marketplace crash on me at least a couple dozen times. I always have to manually reboot to fix it.
Quick update guys, I exchanged it today at Best Buy and just got done updating the firmware through Samsung Kies. We'll see how this one goes; I'll keep everyone posted.
Just wanted to let everyone know that I havent had a SoD since I exchanged it and the battery lasts longer also. So far so good, I'm glad I didnt keep the other one.
Sent from my GT-P6210 using xda premium
Well, i guess i spoke too soon. I updated the firmware tonight. Since then Ive had 2 random reboots.
GaresTaylan said:
Well, i guess i spoke too soon. I updated the firmware tonight. Since then Ive had 2 random reboots.
Click to expand...
Click to collapse
If you can, go for an exchange. Don't keep a defective item unless you have to. Samsung has warranty on it though I believe.
Sent from my GT-P6210 using xda premium
Im chalking my random reboots up to setcpu. Had 2 in 10 minutes. Removed set cpu none since. PROBABLY need a custom kernel.
chrisrotolo said:
Im chalking my random reboots up to setcpu. Had 2 in 10 minutes. Removed set cpu none since. PROBABLY need a custom kernel.
Click to expand...
Click to collapse
What were your SetCPU settings?
Any screen-off profile with a maximum limit less than 800 MHz WILL cause SoDs until the kernel can get patched.
removed all profiles. just 500 min 1.1 max
Finally gave up and returned mine. I had just updated to the latest firmware, did a factory reset and 4 hours later got 2 back to back SOD's. This was the last day I could return it to Best Buy and luckily they had 1 left. Charging the new one right now.
Lack of a better subject description the only thing I can describe it as is possessed. I've never had this problem before. Searched various different keywords and couldn't find anything. So if this is a repost then I apologize.
I have a Samsung Galaxy S3 from Verizon white 32gb. Never been rooted. Around the time Verizon pushed out the last update for the phone it's been acting strange since the update and it's progressively gotten worse. It's almost made purchases for me while I'm browsing google play it'll randomly press areas and randomly click buy at times. Or I'm trying to text someone and it'll either type something on it's own or start trying to delete/lock/resend, etc messages. It starts up s voice randomly too.
So basically it's like having a set of ghost fingers/hand trying to control my phone while I'm trying to control it and the ghost is winning and I'd rapidly hit the home button to exit out of whatever I was trying to do. If the screen is on and unlocked it'll do the same thing even if I'm not touching it but this is maybe 1 out of 5 times compared to the while I'm trying to actively use my phone it'll be 1 out of 2.
Temporary fixes have been to just restart the phone and at first it would only occur every couple days and then once a day and now every few hours to every few minutes. Anyone have any suggestions on what I can do? Any tips would be greatly appreciated. Thanks!
All you have available right now is factory data reset or refurb. If don't fix reflash the latest available stock software via Odin or root and unlock it and flash anything. Can even root stock and have access to better apps.
Try a factory reset if you haven't.
Sent from my SCH-I535 using xda premium
I have now tried a factory reset and while it took longer than just a few minutes to go all psychotic on me it still happened. Thanks for the tips! Any other suggestions? refurb is the last option I want to take I've received too many defective refurb phones and I don't think I can deal with anymore. I can try root I suppose but if there's any other suggestions I should try prior I'm open!
Thank you thank you!
If i were in your position I would try to Odin back to the stock rom you had before the update. There is a sticky in the development section that tell you how to do that and much more
Sent by one of my many Anthromorphic Personifications
elayn said:
I have now tried a factory reset and while it took longer than just a few minutes to go all psychotic on me it still happened. Thanks for the tips! Any other suggestions? refurb is the last option I want to take I've received too many defective refurb phones and I don't think I can deal with anymore. I can try root I suppose but if there's any other suggestions I should try prior I'm open!
Thank you thank you!
Click to expand...
Click to collapse
It sounds defective. I'd take it back.
What you are describing happened to my Droid Incredible a few times: it appeared that someone else was creating random tap events on my phone. Turned out to be a slightly dirty and/or stuck optical trackball - once that was cleaned (easy), everything was back to normal.
Now, the Galaxy S III does not have a trackball. I don't see a direct correlation with my Incredible, but the symptoms you describe are oddly similar: perhaps try cleaning your various pushable keys, just in case?
Might install and run Symantec Antivirus just for a final check, then call Verizon Support if it's still happening and perhaps see what they can offer.
- ooofest
Replace your device. The touchscreen encoder is bad. If your screen is clean, never got wet, and is pressing random areas - and a factory reset or Odin doesn't work - this is most likely the case. You could try to convince them to give you a new one at the store by telling them you don't want to wait or something.
Also download the app multitouch visualizer and run it when it's flaking out. You will be able to see the "screen press" activity.
adoublearonn said:
Replace your device. The touchscreen encoder is bad. If your screen is clean, never got wet, and is pressing random areas - and a factory reset or Odin doesn't work - this is most likely the case. You could try to convince them to give you a new one at the store by telling them you don't want to wait or something.
Also download the app multitouch visualizer and run it when it's flaking out. You will be able to see the "screen press" activity.
Click to expand...
Click to collapse
Because the device is so new you have a very good chance of getting a new replacement. I had something happen to my GNEX and they replaced it with a new phone no refurb.
Thank you all very much for your tips and advice! I stopped by the Verizon store today. Twice actually. It was a no go. First off they won't replace my phone with anything but a refurb (which is standard policy anyway) but the second part which is really irritating is that the phone was driving me insane till I went into the verizon store while waiting for a tech it kept acting odd then when the tech got my phone it functioned correctly. So since they couldn't replicate the problem they said they can't offer me a replacement. As soon as I got into the car it started happening again I ran into the verizon store and they said I had to wait for a tech again so I put my name in and waited had a different tech and of course as soon as he tested the phone it wasn't acting odd anymore so once again couldn't replicate.
Maybe my phone really is possessed.. but then again it's been my luck with past phones as well if they have issues they refuse to happen in store so I got my replacements via 611 tech support. So I called 611 and they said they never heard of the issue and that I should wait for update.
elayn said:
Thank you all very much for your tips and advice! I stopped by the Verizon store today. Twice actually. It was a no go. First off they won't replace my phone with anything but a refurb (which is standard policy anyway) but the second part which is really irritating is that the phone was driving me insane till I went into the verizon store while waiting for a tech it kept acting odd then when the tech got my phone it functioned correctly. So since they couldn't replicate the problem they said they can't offer me a replacement. As soon as I got into the car it started happening again I ran into the verizon store and they said I had to wait for a tech again so I put my name in and waited had a different tech and of course as soon as he tested the phone it wasn't acting odd anymore so once again couldn't replicate.
Maybe my phone really is possessed.. but then again it's been my luck with past phones as well if they have issues they refuse to happen in store so I got my replacements via 611 tech support. So I called 611 and they said they never heard of the issue and that I should wait for update.
Click to expand...
Click to collapse
Or Odin stock firmware instead of waiting. Can Odin without root.
prdog1 said:
Or Odin stock firmware instead of waiting. Can Odin without root.
Click to expand...
Click to collapse
I'll give that a try tomorrow morning and hope it works. I'll check in either way. Thanks!
Take a look at this, and look into this virus some more:
blog.lookout.com/blog/2010/12/29/geinimi_trojan/
I did some research and someone said those are the symptoms of the virus...
Sent from my SCH-I535 using xda app-developers app
It's Verizon, some tech there is having fun with the remote capabilities of the new OTA.
Alrighty, took longer than expected but I did manage to do Odin stock firmware. It fixed the problem or so I thought for 48 hours but then it returned. Now a new problem has come up and the battery is draining at alarming speeds.. I will have phone at 80% when I go to sleep and when I wake up 3 hours later the battery is completely dead. No new apps, nothing draining in the background. I'm at a loss. Anyone have any other advice? Or are my only options now to throw the phone out the window or try to root it.
elayn said:
Alrighty, took longer than expected but I did manage to do Odin stock firmware. It fixed the problem or so I thought for 48 hours but then it returned. Now a new problem has come up and the battery is draining at alarming speeds.. I will have phone at 80% when I go to sleep and when I wake up 3 hours later the battery is completely dead. No new apps, nothing draining in the background. I'm at a loss. Anyone have any other advice? Or are my only options now to throw the phone out the window or try to root it.
Click to expand...
Click to collapse
You wrote in a previous post that you went into the Verizon store... don't do that, ever... just call them.. tell them what it's doing and that you have tried a factory reset. They will overnight you a new/refurbished phone.
I had problems with mine as well and after fighting with the tool they call a manager I called 611 from the parking lot and after the hold time I had tech support on the phone and had a new replacement on the way 5 minutes later..
Just my 2 cents.
BiasedThunder said:
You wrote in a previous post that you went into the Verizon store... don't do that, ever... just call them.. tell them what it's doing and that you have tried a factory reset. They will overnight you a new/refurbished phone.
I had problems with mine as well and after fighting with the tool they call a manager I called 611 from the parking lot and after the hold time I had tech support on the phone and had a new replacement on the way 5 minutes later..
Just my 2 cents.
Click to expand...
Click to collapse
Thanks for the tip but if you read through the whole post. I did default to calling 611 like I usually do and they wouldn't do anything about it. Yes, I did tell em I did the factory reset. It's not the first time I had a phone replaced through 611 I've gone through maybe 10+ replacements on one of my past phones because they kept sending me a defective one over and over again. I did call 611 again since you suggested it but I was told the same exact thing as last time.
I had this happen a few times with my phone before the update verizon pushed (stock, rooted). I would end up pulling the battery to get it to stop. Hasn't happened to me in a while though. Now i'm running JellyWiz RLS12
so yesterday my unlocked T-Mobile HTC One S got bricked, before you ask i never touched the ROM of the device, it was pure stock HTC One S with a lot of apps.
basically it entered into a strange loop: first the T-Mobile greeting message appeared and then the HTC One S logo, over and over and over again. the only thing that i could do was to power button + volume down and do a factory reset.
This happened one day after i updated its firmware OTA, and in the same day that i downloaded a free app called AutomateIt.
i'm only upset about the fact that i lost the pictures and vids that i took in the 6 weeks owning it, but i am worried that if it did this once, it could do it again so i need to know if this is something common to Androids, my One S or something else.
Very strange!!!
Root the phone and make a nandroid backup. Stock Rom's sucks!!!
Sent from my HTC One S using xda app-developers app
Warmo said:
so yesterday my unlocked T-Mobile HTC One S got bricked, before you ask i never touched the ROM of the device, it was pure stock HTC One S with a lot of apps.
basically it entered into a strange loop: first the T-Mobile greeting message appeared and then the HTC One S logo, over and over and over again. the only thing that i could do was to power button + volume down and do a factory reset.
This happened one day after i updated its firmware OTA, and in the same day that i downloaded a free app called AutomateIt.
i'm only upset about the fact that i lost the pictures and vids that i took in the 6 weeks owning it, but i am worried that if it did this once, it could do it again so i need to know if this is something common to Androids, my One S or something else.
Click to expand...
Click to collapse
Did you let the phone die? the phone don't like to do that. Get Dropbox or Google+ that will sync your pictures online.
The same happened with my stock htc one s 4.0.4 twice! I figured out that when you have more than 15-20 saved wlans, you have connected to in the past, in your wifi-list your phone ends up in a bootloop. I didn't manage to rescue any data even not with adb.. clearing the cache and so on. probably you used any automatic wifi functionality from automatelt.
-janboy- said:
The same happened with my stock htc one s 4.0.4 twice! I figured out that when you have more than 15-20 saved wlans, you have connected to in the past, in your wifi-list your phone ends up in a bootloop. I didn't manage to rescue any data even not with adb.. clearing the cache and so on. probably you used any automatic wifi functionality from automatelt.
Click to expand...
Click to collapse
now thats interesting, my phone is also 4.0.4, and yes i did have ~20 saved WLAN's, i can't figure how wlan would have any connection to a bootloop, but then again i dont know anything about programming.
so you always delete the wlans once you are done using them? after you found out did it brick again?
Warmo said:
now thats interesting, my phone is also 4.0.4, and yes i did have ~20 saved WLAN's, i can't figure how wlan would have any connection to a bootloop, but then again i dont know anything about programming.
so you always delete the wlans once you are done using them? after you found out did it brick again?
Click to expand...
Click to collapse
yes, I take care that I don't have more than 5-10 in my list. since that it didn't brick again. but a few days ago I had ~10 in my list and it suddenly restarted again while I was in the wifi list screen and I was like pleeeaassse no bootloop! but fortunately it was no bootloop but my whole wifi list was reset. it must be an error in htc's software.. so we can only wait for updates..
I've had this happen with other Android devices, it's generally some rogue app that screws up the device and only a factory reset will clear it. I've never had more than 3 or 4 wifi points saved so can't comment on that as a possible cause.
It's not 'bricked' by the way, just slightly fubar'd
-janboy- said:
The same happened with my stock htc one s 4.0.4 twice! I figured out that when you have more than 15-20 saved wlans, you have connected to in the past, in your wifi-list your phone ends up in a bootloop. I didn't manage to rescue any data even not with adb.. clearing the cache and so on. probably you used any automatic wifi functionality from automatelt.
Click to expand...
Click to collapse
You are not the only one. I also encountered the same thing because of too much wlan connections and the only thing i could do is run into bootloader and restore factory settings, since i don't have a nandroid backup because i'm not rooted.. fortunately i synced my pictures thru dropbox, and a backup of sms in gmail.. but i don't know why it is happening to us, so this issue isn't an individual case..
Sent from my HTC One S4 using xda-developers app