So my setup is I take my phone to work and I charge it there while I work and listen to my music on it. Well, I just got this two days ago and it seems when its charging I can't get on the internet. It has a full HSPA+ signal. Restarting it fixes it for about 3 minutes while charging. If I put on airplane mode and take it off while charging, again it lasts for just a few minutes then no connection in apps/browser.
I've searched for some posts but haven't seen anything on this. Any ideas? I'm likely going to have to take it back to the store and show them my issue and try to get a new one because this sucks!
Thanks in advance.
Sent from my HTC Glacier using XDA App
Something like that happened to me once. I had full signal and HSPA data icon but I couldn't get a data, voice or GPS connection. I wasn't charging. After I reboot the phone everything was fine. Only happened once. I also sometimes get the data connection dropped while the voice connection has a strong signal, but in that case the data connection icon disappears from the status bar.
If I were you I'd backup whatever you have on your phone and do a factory reset to rule out any software affecting the phone. If you still get the problem I'd suspect it's a hardware issue and get it replace/repaired.
If you are on stock, try factory data/wipe reset. If you are rooted, install clockworkmod recovery, wipe cache/wipe davlik cache, fix_permissions. If above didn't help, probably a hardware issue, you need to get it replaced....
faux123 said:
If you are on stock, try factory data/wipe reset. If you are rooted, install clockworkmod recovery, wipe cache/wipe davlik cache, fix_permissions. If above didn't help, probably a hardware issue, you need to get it replaced....
Click to expand...
Click to collapse
if rooted and using a custom rom, there is also a possibility that the issue is caused by overclocking. Many overclocked devices lose connection to the mobile network with no discovered cause yet.
@dbannisterjr, if you have a way to reproduce this problem please let us know. If you are overclocking your device, try lowering the amount it is overclocked.
faux123 said:
If you are on stock, try factory data/wipe reset. If you are rooted, install clockworkmod recovery, wipe cache/wipe davlik cache, fix_permissions. If above didn't help, probably a hardware issue, you need to get it replaced....
Click to expand...
Click to collapse
+1 this is exactly what i was going to recommend
Related
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
So the past 2 days I've had an interesting problem, with even more interesting results.
Both mornings I've tried to use my GPS and it just hangs on trying to connect to it. The GPS says it's on, and I can toggle it off and back on again but it never finds any sats.
Yesterday I reboot the phone and it takes a while to boot the phone back up (most like the first time you boot after a fresh install), and when the phone came back online the GPS worked but all my bluetooth pairings were gone.
Today I have the same GPS problem so I reboot again, and again it takes a while to boot and so far I still have my bluetooth pairings, but I've been unable to connect to the devices, all my sound settings are back to the defaults, when I hold down the power button now the only option I have is Power Off, nothing else, when my screen times out and I hit power to bring it back on it goes right back to wherever I was, I don't see the lock screen anymore. And to top it all off my home button and my search button do not work.
What a mess, this phone is getting worse by the day, I'm actually starting to regret the purchase. I guess it's time to call it in and see what they say.
Edit: Forgot to add all my SMS messages were deleted as well.
Rooted? Have you done anything to it? That's definitely not normal but I guess you know that
Ya it's rooted and has nvflashed clockworkmod recovery installed. Rooted the day I got the phone and clockworkmod recovery has been installed for about a week.
I just tried clearing the cache partition, wiping Dalvik Cache, fixing permissions, and no change. Running a full backup via Titanium Backup now before I try a factory reset to see if that fixes it.
If that doesn't do it I'll try restoring a backup image from last week.
gohawks1 said:
Ya it's rooted and has nvflashed clockworkmod recovery installed. Rooted the day I got the phone and clockworkmod recovery has been installed for about a week.
I just tried clearing the cache partition, wiping Dalvik Cache, fixing permissions, and no change. Running a full backup via Titanium Backup now before I try a factory reset to see if that fixes it.
If that doesn't do it I'll try restoring a backup image from last week.
Click to expand...
Click to collapse
I would guess it's not the phone but the CWM made the mess. You probably want to try factory reset.
My Bluetooth settings and profiles randomly appear and disappear and I'm bone stock.
Well, factory reset got all my buttons working again, and my screen locks again. Since I'm back to stock now and have to re-setup everything now I think I'll go try out the Eaglesblood ROM and see how that goes.
1st-sometimes when switching from 2g or wifi back to 4g i cant get a connection even though i have 4 signal bars...the only cure is to reboot the phone...anybody have any ideas? And this happens in various locations.
2nd-started a few days ago..phone doesnt make a sound when i get email or sms but rings when someone calls..i reset the phone and sounds come back for a while and then it goes away again.
on cm7 7.1.0.1
1. Reset APN settings to default
2. Reboot into recovery, fix permissions, and wipe cache
3. Reboot and let it settle for 5 mins.
Good luck, let me know if it works.
dylyxcore said:
1. Reset APN settings to default
2. Reboot into recovery, fix permissions, and wipe cache
3. Reboot and let it settle for 5 mins.
Good luck, let me know if it works.
Click to expand...
Click to collapse
wipe cache partition or wipe dalvik cache?
nevermind...upon some research i did both
cache partition, davlik won't make any difference... throw me a thanks if it works!
dylyxcore said:
cache partition, davlik won't make any difference... throw me a thanks if it works!
Click to expand...
Click to collapse
give me a few days testing
issue seems to be better but had evi installed and think that had something to do with the notification sounds not working as they not work
Can anyone suggest a troubleshooting method without a factory reset. This is what I am experiencing:
Everytime I reboot the Sensation will boot up and go through the normal process. About 3 or 4 minutes it will just reboot. Often when this happens I note that I don't have to re-enter my pin (a clue?). This rebooting will go on repeatedly but eventually (if I leave the phone alone) I will at some point end up with the phone up and running.
There are no random reboots, it is only this situation that causes the problem and it's obviously some point 3 or 4 mins into the process that is causing the problem.
I've noticed that if I reboot to recovery and then select reboot from there it is usually successful.
I am s/off via wire trick method, and rooted. recovery is 4 ext and I am still on stock rom.
I'd like to find out what is happening at the point of the reboot, is there a good way to do this?
louiscar said:
Can anyone suggest a troubleshooting method without a factory reset. This is what I am experiencing:
Everytime I reboot the Sensation will boot up and go through the normal process. About 3 or 4 minutes it will just reboot. Often when this happens I note that I don't have to re-enter my pin (a clue?). This rebooting will go on repeatedly but eventually (if I leave the phone alone) I will at some point end up with the phone up and running.
There are no random reboots, it is only this situation that causes the problem and it's obviously some point 3 or 4 mins into the process that is causing the problem.
I've noticed that if I reboot to recovery and then select reboot from there it is usually successful.
I am s/off via wire trick method, and rooted. recovery is 4 ext and I am still on stock rom.
I'd like to find out what is happening at the point of the reboot, is there a good way to do this?
Click to expand...
Click to collapse
boot into recovery and wipe dalvik cache n then do a normal reboot n check wad happens
you can also make a nandroid backup n install a custom and check wheather the problem exisit by doing backup ull not loose ur data n u can return to stock again just by restoring the backup ... try and let me know
louiscar said:
Can anyone suggest a troubleshooting method without a factory reset. This is what I am experiencing:
Everytime I reboot the Sensation will boot up and go through the normal process. About 3 or 4 minutes it will just reboot. Often when this happens I note that I don't have to re-enter my pin (a clue?). This rebooting will go on repeatedly but eventually (if I leave the phone alone) I will at some point end up with the phone up and running.
There are no random reboots, it is only this situation that causes the problem and it's obviously some point 3 or 4 mins into the process that is causing the problem.
I've noticed that if I reboot to recovery and then select reboot from there it is usually successful.
I am s/off via wire trick method, and rooted. recovery is 4 ext and I am still on stock rom.
I'd like to find out what is happening at the point of the reboot, is there a good way to do this?
Click to expand...
Click to collapse
Hi,
Have you installed a new ROM recently?
Did you fully wipe the phone before you did this?
If not,try re-installing the ROM you are on.
No wipes.
You will not lose settings or data.
shrex said:
boot into recovery and wipe dalvik cache n then do a normal reboot n check wad happens
you can also make a nandroid backup n install a custom and check wheather the problem exisit by doing backup ull not loose ur data n u can return to stock again just by restoring the backup ... try and let me know
Click to expand...
Click to collapse
What I noticed is that the problem didn't exist when rebooting from ADB or fastboot either.
Anyway your suggestion so far looks promising. I've tried a normal restart from the phone and a battery change both of which would usually end up with the rebooting problem. Both of these tests haven't caused it so I'll keep testing but thanks for the suggestion.
What is does the Dalvik cache do and how would this have caused this kind of problem? I'm interested in the whys. The problem appeared soon after installing a couple of things as I remember and I did try to backtrack without much success.
malybru said:
Hi,
Have you installed a new ROM recently?
Did you fully wipe the phone before you did this?
If not,try re-installing the ROM you are on.
No wipes.
You will not lose settings or data.
Click to expand...
Click to collapse
No I've not installed any Roms, I'm on stock.
Revived thread - as it's happening again
I'd like to revive this thread - perhaps I should post a new one but since it's here ...
This problem has returned with a vengeance. It took me about 3 hours of fighting to get this phone to stop rebooting. It seems clearing the dalvik cache isn't a solution anymore (if it was in the first place).
What I've observed is that if I take the sd card out it doesn't reboot. When the card is in I have several shortcuts on one of my home screens which often will not refresh for ages (ie. android icons for anything moved to sd card). When the icons start to appear the reboot will happen shortly after. All the time I'm waiting for this to happen the phone is very sluggish.
I don't think this is an incompatible sd card but maybe it is, however, if I can get this to stop rebooting then all is ok till I attempt another reboot.
Ideally I'd like to track this down to find out if there is an app which is misbehaving. Are there any tools that can help me do that.
Any suggestions would be most welcome.
Backup all your data and do a factory reset
This problem might be due to 3rd party app as you phone without sd card dosent reboots
Might be some of ur app is seriously miss-behaving
After a factory rest install each app n check ( I know it's time consuming)
Hit thanks button if you find me helpful
sent from amazing HTC sensation using xda premium
shrex said:
Backup all your data and do a factory reset
This problem might be due to 3rd party app as you phone without sd card dosent reboots
Might be some of ur app is seriously miss-behaving
After a factory rest install each app n check ( I know it's time consuming)
Hit thanks button if you find me helpful
sent from amazing HTC sensation using xda premium
Click to expand...
Click to collapse
Yeah hoped to avoid that for 2 reasons. 1) It's a bummer 2) I won't know what the problem was / is.
I did do a factory reset after backing up data via my recovery. It seemed to be ok but I had nothing on SD at that point. I loaded a couple of apps and moved them to sd and it still didn't happen. The I restored the data and it was back to the same problem.
I may have to go with your suggestion but I'm going to lose some data as I can't back up selectively (so it seems).
Is there a logger I can use that starts at reboot. If I could find out exactly what it's doing when it decides to reboot I might nail the app?
louiscar said:
Yeah hoped to avoid that for 2 reasons. 1) It's a bummer 2) I won't know what the problem was / is.
I did do a factory reset after backing up data via my recovery. It seemed to be ok but I had nothing on SD at that point. I loaded a couple of apps and moved them to sd and it still didn't happen. The I restored the data and it was back to the same problem.
I may have to go with your suggestion but I'm going to lose some data as I can't back up selectively (so it seems).
Is there a logger I can use that starts at reboot. If I could find out exactly what it's doing when it decides to reboot I might nail the app?
Click to expand...
Click to collapse
hi
greetings
to find the problematic app might go tough you will have to install each and every app and check after that
try installing all the trustworthy apps before eg. file manager,fb,twitter,gmail etc then check once again ,after that install single app at a time
Everything was going so well. I received my perfect phone a couple days ago...unlocked it, installed cwm 6.0.4.4, and rooted it. Kept it stock and only flashed franco and Drummerjed's volume boost. Life was swell.
I decided I wanted to try the Dalvik optimization mod and in preparation booted into recovery to make a nandroid. I always wipe the cache/dalvik cache before making nandroids because they're made faster when I do this. Never had an issue. This time, however, after clicking to wipe the cache partition the system seemed to freeze, which was weird because on my N4 it clears the cache in a matter of seconds. I held the power button down to reboot the phone and immediately knew something was wrong when I was greeted by 3 warning signs in the notification bar. I then discovered that I have no cell service. I am also unable to access internal storage.
I imagine that I'm going to have to flash the factory image and start over, but I'm wondering if there's any way to avoid that? I'm also wondering why this happened so I can avoid reproducing this in the future. Does cache wiping take considerably longer on the N5, and did I interrupt the process by rebooting the phone?
Thanks so much for your help.
I think you did interupt the process by rebooting the phone. Wiping dalvik/cache does seem to take a lot longer on this phone than on other devices (the only other device I have to compare to is the Nexus 7 though). I would say to just let it sit while it does it's thing next time.
I did have a problem with not having cell service once after wiping dalvik/cache though. I just rebooting into recover and wiped again and my cell service was back. Give that a shot and see what happens.
ramdyc said:
I think you did interupt the process by rebooting the phone. Wiping dalvik/cache does seem to take a lot longer on this phone than on other devices (the only other device I have to compare to is the Nexus 7 though). I would say to just let it sit while it does it's thing next time.
I did have a problem with not having cell service once after wiping dalvik/cache though. I just rebooting into recover and wiped again and my cell service was back. Give that a shot and see what happens.
Click to expand...
Click to collapse
Thanks, ramdyc, wiping again worked. After rebooting, everything was back to normal (seemingly). Cache wipe on my N5 takes waaayyy longer compared to what I'm used to on N4...just gotta be patient with it!
If you are using TWRP, go into the settings and enable rm -rf and it will wipe instantly. (or something like that - forgot teh exact setting name)
If anyone reads this and wiping it again DOESN'T work, you can flash the stock cache.img via fastboot and you'll be good to go.
Synyster06Gates said:
If you are using TWRP, go into the settings and enable rm -rf and it will wipe instantly. (or something like that - forgot teh exact setting name)
If anyone reads this and wiping it again DOESN'T work, you can flash the stock cache.img via fastboot and you'll be good to go.
Click to expand...
Click to collapse
I'm using cwm. I actually just flashed the recently released touch version of it and wiping cache with it took mere seconds like it does on my N4. Thanks for your help, guys!