portable wifi hotspot - HTC Sensation

sooo i decided to try the portable hotspot function today and found out that everytime i went to the hotspot settings it force closes on me. I get the error " process com.android.settings has stopped unexpectedly)
anyone have this problem? or have any insight to fixing it?
i thought i disabled something but i went through and re enabled processes but nothing so far is working. im going to keep trying in the mean time.

I would backup your apps and do a factory reset. That should fix your issue.

Cosign Dubie - that's not normal behavior. Try turning off fast boot and restarting your phone and see if that helps first.

thanks, a backup and factory reset fixed it... everything is back to the way it was with mobile hotpot working again. really didnt want to have to do it but eventually i had to.

The Illest 619 said:
thanks, a backup and factory reset fixed it... everything is back to the way it was with mobile hotpot working again. really didnt want to have to do it but eventually i had to.
Click to expand...
Click to collapse
If your phone is rooted, does a factory reset unroots it?

No @ franca
sent from my Sensation on CM7 Alpha#10

Related

[Q] [ISSUE] freezes while phone is in stand-by and while using apps

hey all,
on friday I rooted my NS again to check out cm7 rc1. before i was totally stock @ 2.3.2. friday evening i wanted to show my iphone friends the nexus s with cm7. the first one took it and did take some photos. then he smiled and gave it back to me. force close: SORRY: Android.process(???) has stopped unexpectedly.
this error was looping all the thime. i pressed okay and one sec later it was there again. i tried to flash the rom again in recovery, but the error was still there. i did date and cash wipes and some factory resets and then the error was gone.
on sunday i was travelling home on train and suddenly the error was back. i tried again some wipes and then i deceided to restore my nandroid backup. so i was back on 2.3.2. during sunday afternoon and evening i got these errors:
- NS is freezing while it is in standby... if i grab the phone and want to unlock it but the display keeps black -> i have to put out the battery..
- NS is beside my keyboard and suddenly all four buttons are on. display is still black. unlock not possible--> battery again
- NS is freezing while using facebook or twitter app
today... i unrooted it again and went back to a nandroid (2.3.1) guided _here_.
after unrooted again NS wanted to update to 2.3.2 which i confirmed.
about to hours later the errors i explained came back.
am i the first one who bricked NS?
please give me some help how to get it back working correctly, because i love this phone so hard.
I did another factory reset and now the phone is hanging at the google Logo. The four buttons are powered.
This is looping, too.
Yesterday I tried some things to kill these errors. I did:
- factoy reset (in settings menu)
- fastboot erase userdata 2x
- wipe cache, wipe data, wipe devliak
Today the phone was with out a problem, but just a moment ago I wanted to unlock it by pressing the power button but the display didn't react as usal. It is still black and the only thing I can do is to take out the battery....
Last step I can do is to send it back to my girlfriends sister in US so that she can bringt it to Samsung US to get it serviced.
"bricking" the phones involves the phone not being able to turn on or do anything, period. your phone isnt a brick. after doing a "factory reset" you want to reflash whatever rom you are using. it seems like youre having problems with a bad app or some bad data.
thx simms22. i just flashed the newest cm7 nightly with rom manager (incl. wipe). i set up all my apps and 20 min later the error come.
to figure out if it is a bad app problem i do a factory reset now and won't log into google account and see if the error appears.
simms22 said:
it seems like youre having problems with a bad app or some bad data.
Click to expand...
Click to collapse
i did a factory reset and skipped google setup after first boot.
i just entered sim code and let nexus s in idel mode.. about 15 mins later the four buttons were lightened but i couldn't unlock the phone. battery out... and i could power it on.
so it's some kind of bad data problem? but how to find and/or clean this bad data? thx again for your help.
edit: I found a lot on google for "full wipe bad data". I'm reading now! But I may have to ask you something
edit2: in recovery (cwm3.0.0.5) I did: format system, format data, format cache and format sdcard. then i mounted usb and copied this nandroid 2.3.1 to it and flashed it. I booted and installed system update 2.3.2. now testing again without apps.
edit3: the hole day no problems. I only installed twitter and in the evening 2.3.3 manually. This morning again the phone was not unlockable. I had to take out the battery... on my way to work I did a wipe from stock recovery but shortly later the phone freezed while I used the slider to unlock it. oh man that sucks I thought it was fixed.
I make some coffee now and start google'ing. If you have some tipps, please throw them to me.
maybe reflashing radio?
stiefa00 said:
i did a factory reset and skipped google setup after first boot.
i just entered sim code and let nexus s in idel mode.. about 15 mins later the four buttons were lightened but i couldn't unlock the phone. battery out... and i could power it on.
so it's some kind of bad data problem? but how to find and/or clean this bad data? thx again for your help.
edit: I found a lot on google for "full wipe bad data". I'm reading now! But I may have to ask you something
edit2: in recovery (cwm3.0.0.5) I did: format system, format data, format cache and format sdcard. then i mounted usb and copied this nandroid 2.3.1 to it and flashed it. I booted and installed system update 2.3.2. now testing again without apps.
edit3: the hole day no problems. I only installed twitter and in the evening 2.3.3 manually. This morning again the phone was not unlockable. I had to take out the battery... on my way to work I did a wipe from stock recovery but shortly later the phone freezed while I used the slider to unlock it. oh man that sucks I thought it was fixed.
I make some coffee now and start google'ing. If you have some tipps, please throw them to me.
maybe reflashing radio?
Click to expand...
Click to collapse
are you using any of the custom kernels?
no, I'm using stock kernel and never flashed a custom kernel.
stiefa00 said:
no, I'm using stock kernel and never flashed a custom kernel.
Click to expand...
Click to collapse
im going to have you try wiping once again. wipe data/factory reset. only this time reupdate to android 2.3.3 right after the factory reset in recovery. dont boot after wiping, update after wipe, then reboot.
--> stock recovery -> wipe / factory reset -> reflashed update (ota2.3.3) -> testing now without installing apps
thanks simms!
Edit: the phone got a freeze while I wanted to unlock it -.-
Edit2: I'm testing now in airplane mode. Maybe the error doesn't come...
stiefa00 said:
--> stock recovery -> wipe / factory reset -> reflashed update (ota2.3.3) -> testing now without installing apps
thanks simms!
Edit: the phone got a freeze while I wanted to unlock it -.-
Edit2: I'm testing now in airplane mode. Maybe the error doesn't come...
Click to expand...
Click to collapse
im now thinking it might not software related. if it was software, a wipe and reupdate should have fixed it. maybe you should check into a warranty replacement. .
In airplane mode the error is there, too.
Okay thx 4 ur help. I'm starting a service request. Bad day -.-
Sent from my Nexus S using XDA App
stiefa00 said:
In airplane mode the error is there, too.
Okay thx 4 ur help. I'm starting a service request. Bad day -.-
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
the only other thing i can think of that might cause something like that after wiping is something bad on your "sd" storage. copy everything you need off your "sd" storage and try wiping that.
stiefa00 said:
edit2: in recovery (cwm3.0.0.5) I did: format system, format data, format cache and format sdcard. Then nandroid restore...
Click to expand...
Click to collapse
I think I allready did this? Or do you talk about this 1gb sd. If so, how to format this one?
Could I find something usefull with logcat?
Sent from my Nexus S using XDA App
According to this thread I think you will have to get it replaced:
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=44db6d8e31129d4c&hl=en
Holy sh** what an anoying link. -.-
BUT: thanks dude.. now I know waaazzz up

[Q] Network Problem? Phone Problem?

I recently bought a rooted Nexus s (GSM), and everything was fine until I powered off the phone. When I re-powered the phone, the mobile data didn't work, and the phone kept harassing me with the notification "sorry! the process com.android.phone has stopped unexpectedly" and made me force close it. and when I do press force close, the notification would pop up again instantaneously until I got tired of it and ripped the battery out.
The phone is currently running on NSCollab-1.0.35 ROM.
I tried hard-resetting the phone, but when I try to do it (via hard key reset and through settings->privacy-> etc) it would get stuck on the black google boot page and wouldn't budge. I can't even get to the recovery page.
I also tried to flash clockworkmod, then fix the permissions, and then reboot the phone, but that also failed.
The only way to stop the phone from harrassing me with the sorry notifications is to put it in airplane mode.. which certainly does not help my case. Please help! I will be eternally grateful.
Ok the reason this is happening is because you used the "switch from 3G to 2G" widget. You should've read the bugs when you downloaded the nscollab. Btw I use nscollab and I love it.
I fixed it by just wiping cache and just reinstalling the ROM.
acesofbelkan said:
Ok the reason this is happening is because you used the "switch from 3G to 2G" widget. You should've read the bugs when you downloaded the nscollab. Btw I use nscollab and I love it.
I fixed it by just wiping cache and just reinstalling the ROM.
Click to expand...
Click to collapse
yes, wow. I did do that. I see, I screwed up. Thank you so much!
acesofbelkan said:
Ok the reason this is happening is because you used the "switch from 3G to 2G" widget. You should've read the bugs when you downloaded the nscollab. Btw I use nscollab and I love it.
I fixed it by just wiping cache and just reinstalling the ROM.
Click to expand...
Click to collapse
well, I'm trying to wiping cache, but I can't even get to the recovery mode...

[Q] Unfortunately, com.keyguard has stopped [black screen]

I can't do anything once it boots.
Factory reset lets me get through the setup process, but no home screen or anything..
reboot leads to "Unfortunately, com.keyguard has stopped" and keeps popping up. literally stuck.
Rooted 4.4 out of the blue this morning bootlooped when I turned my phone on this morning.
No xposed, ART enabled.
Again, factory reset from stock recovery gets me nowhere. Is there a way I can completely wipe whatever is causing this? Still no FXZ for 4.4 right?
Droid Maxx
Others have fixed issues by putting the 4.4 update zip on their sd card and running it again, repairing system files and keeping user data. Possible?
YoungSkeezy said:
I can't do anything once it boots.
Factory reset lets me get through the setup process, but no home screen or anything..
reboot leads to "Unfortunately, com.keyguard has stopped" and keeps popping up. literally stuck.
Rooted 4.4 out of the blue this morning bootlooped when I turned my phone on this morning.
No xposed, ART enabled.
Again, factory reset from stock recovery gets me nowhere. Is there a way I can completely wipe whatever is causing this? Still no FXZ for 4.4 right?
Droid Maxx
Click to expand...
Click to collapse
Here is the fxz: https://dl.dropboxusercontent.com/u....4-SU2-3-15-release-keys-cid2-Verizon-US_.zip
Extract the files, put your phone in fastboot mode, run the flashall.bat
YoungSkeezy said:
I can't do anything once it boots.
Factory reset lets me get through the setup process, but no home screen or anything..
reboot leads to "Unfortunately, com.keyguard has stopped" and keeps popping up. literally stuck.
Rooted 4.4 out of the blue this morning bootlooped when I turned my phone on this morning.
No xposed, ART enabled.
Again, factory reset from stock recovery gets me nowhere. Is there a way I can completely wipe whatever is causing this? Still no FXZ for 4.4 right?
Droid Maxx
Click to expand...
Click to collapse
Factory data reset doesn't reload the OS as far as I know I have ran a FDR and not lost root. It deletes all user data like apps downloaded and pictures etc. So it won't fix an OS error only an FXZ does that. It basically strips all the stuff you downloaded to factory settings but doesn't reinstall the OS.
Did you have SS inistalled and not make a backup or did you not have SS installed. If you can get to SS you could load a backup if you had one.
Yeah ended up using that. Just happy to have a working device again despite no root anymore lol
Thanks a ton guys
Sent from my XT1080 using XDA Premium 4 mobile app

[URGENT] Every reboot results in a factory reset

So today my droid started messing up, home and recents button didnt work. Google play store and whatnot couldnt access data, the signal status bar at the top was just grey.
So i factory reset it. During the reset it just sat there on the little screen with the spinning hexball thing for like an hour so i shut the phone off. Now every time the phone boots it just tries to wipe it again unless i go into the boot menu and hit normal boot.
Running stock rom and whatnot, but im rooted.
I know that theres a flag somewhere that it reads on boot saying to wipe it, but dang if i know what to change.
Thanks in advance
Well i unrooted my phone and tried to let it redo the factory reset again, and it still just wont do anything.
jombo2323 said:
home and recents button didnt work
Click to expand...
Click to collapse
When this happens to me, it's because of a bad flash and a factory reset won't fix it. I would suggest reflashing stock...
coolloser said:
When this happens to me, it's because of a bad flash and a factory reset won't fix it. I would suggest reflashing stock...
Click to expand...
Click to collapse
I dont have a custom recovery or an unlocked bootloader.
I managed to get the problem sorted out through some unrooting and some non stock system file deletion. Installed safestrap and got blurry hd running on it now.
Thanks.

Wifi wont turn on?

Wondering if anyone else is having this issue.. I just got my S7 yesterday and i was backing up some files onto it.. Fast forward today in the morning and my wifi will no longer turn on.. I tried factory reset and clearing the cache, but that doesnt work..
Revu said:
Wondering if anyone else is having this issue.. I just got my S7 yesterday and i was backing up some files onto it.. Fast forward today in the morning and my wifi will no longer turn on.. I tried factory reset and clearing the cache, but that doesnt work..
Click to expand...
Click to collapse
go in recovery clear cache if that didnt work factory reset...if that doesnt work i have no idea what you can do..some say BT is making problems turn it off..
brane871 said:
go in recovery clear cache if that didnt work factory reset...if that doesnt work i have no idea what you can do..some say BT is making problems turn it off..
Click to expand...
Click to collapse
Yep, that was the first thing I tried, clearing the cache and factory reset, but no go. My last option was to re-flash the stock rom.. Took awhile to find the rom since I have the Canadian variant, with SM-G930W8. Re-flashed and got the wifi working again!

Categories

Resources