From time to time (not always) I receive the following error message when I restart. It appears twice:
the application Samsung account (process.osp.app.signin) has stopped unexpectedly. Please try again.
In my accounts & sysnc Samsung account appears always as sync off, and I cant enable it. Is that normal?
I've got it as well. I assume its because the Samsung login servers are down or something.
Thanx for the reply. I thought this was also connected to a different problem. I am not getting the menu items in KIES to sync with the PC and a message telling this version cannot be updated. Maybe a different topic but nobody replied to my previous post. Thanx again.
Yes, I have gotten it when restaring with quick boot.
Sent from my Galaxy Tab 10.1 via Tapatalk
I get it too. Every time it happens I report it. Does anyone report force closes in here? I think the more reports the higher the priority is, hopefully they fix it soon.
Sent from my GT-P7510 using XDA Premium App
I am also getting it. It seems pretty common.
Sent from my GT-P7510 using XDA Premium App
lordwinkevin said:
I get it too. Every time it happens I report it. Does anyone report force closes in here? I think the more reports the higher the priority is, hopefully they fix it soon.
Sent from my GT-P7510 using XDA Premium App
Click to expand...
Click to collapse
Hopefully because I report it everytime as well. I thought I would have to return mine but I'm glad to see I'm not the only one getting this. Seems to happen when I boot with wi-fi on and it can't access it because the wi-fi is secure.
I get it every time..sometimes twice every time I boot.
It started today for me after installed rscovery and rooted.
I am getting the same error too when starting up sometimes, always comes up twice. Usually after the second reboot it doesn't happen.
same here
Yep... twice every time I turn on the tablet. It's super annoying. I report it every time; I hope they fix it at some point.
Also, I have the GoogleIO edition. Does it happen on retail too?
Yes. I have retail version. I rooted my devices and then unroted it. I read someone did the same? Did everyone in here rooted their device?
Sent from my GT-P7510 using XDA Premium App
Seen ONE TIME, on an unrooted retail unit (BB preorder, 32GB)
I get have seen the message maybe 5 times (2 messages each time). Unrooted retail Galaxy Tab 10.1 32GB Grey.
Same here, unrooted retail 32GB gray. Can't believe this happens as often as it does and wasn't addressed by Samsung before launch.
jeffdgr8 said:
Same here, unrooted retail 32GB gray. Can't believe this happens as often as it does and wasn't addressed by Samsung before launch.
Click to expand...
Click to collapse
second that....
I get this error all the time as well. To my memory when i first started using the tablet i never got it, im not sure though.
bradrobster said:
I get it every time..sometimes twice every time I boot.
Click to expand...
Click to collapse
I am also getting this. Twice usually. I also press report. I have the gray 32gb that was shipped unlocked, does this make a difference? I am also rooted.
First post here.
I receive this twice on every bootup. I emailed Samsung Support yesterday using the email [email protected]
Samsung Galaxy Tab 10.1
eric6b12 said:
First post here.
I receive this twice on every bootup. I emailed Samsung Support yesterday using the email [email protected]
Samsung Galaxy Tab 10.1
Click to expand...
Click to collapse
What did they say?
I get this too, twice on every boot. The message says you can restore to factory defaults, which will wipe out your accounts and resolve the issue temporarily until you add your samsung account again. This is why we didn't get this message when on first boot.
Related
Just trying to build some statistics as to how common this turning off problem is.
--------------------
PLEASE READ THIS BEFORE ANSWERING:
1) Obviously this is regarding the phone turning off on its own when its not due an empty battery.
2) Only answer with "no" if you've been using the phone for at least a week. If you've been using it for less and it hasnt turned off, answer with "No - but had it for less than a week".
--------------------
I just want to know before I send my phone to Amazon for replacement.
I've had it 8 days, so I clicked the 2nd "no". If I saw any hardware fault in a new device I'd immediately get onto the supplier for a replacement. Unless there's software at fault here (unlikely, but obviously possible) then I can't see the problem simply going away.
Hope you get it sorted mate.
Nope. Had the phone since may 6.
Sent from my GT-P1000 using XDA Premium App
Thx for the replies guys.
Keep the answers coming
No. Never unless the battrey is empty.
Sent from my GT-I9100 using XDA App
Touchwood, never and I've had the phone a few weeks now.
Had this problem last year with my new Desire, but returned it to HTC and they replaced the mobo without any problems.
Yep had it nearly 4 weeks and its went twice. Not in the last week or so though.
Sent from my GT-I9100 using XDA App
Everyone runs different apps and settings on their phones. Unless there's a specific hardware problem there's going be tons of variables to consider for those having reboot issues. I've had mine for six weeks and its never done anything wonky.
I returned my 1st one as it turned off a few times a day. Replacement has been fine.
Sent from my GT-I9100 using XDA App
Does reboot count as a yes?
I clicked yes but I am not 100% sure if this happened to me or not. Allow me to explain...
I was carrying it in my hand walking and I happened to look at the screen and it was showing the Samsung GT-i9100 splash screen seemingly for no apparent reason. When it went away it just went right back to where it was (no media card reading or anything).
It was strange to say the least but I have not seen it happen again since then and that was about a week ago and I have had the device for approx. 3 weeks now.
Does this sound like the same issue?
BarryH_GEG said:
Everyone runs different apps and settings on their phones. Unless there's a specific hardware problem there's going be tons of variables to consider for those having reboot issues. I've had mine for six weeks and its never done anything wonky.
Click to expand...
Click to collapse
Lightfunkyone said:
Does reboot count as a yes?
Click to expand...
Click to collapse
Oh sorry i forgot to mention this. No, reboots don't count as they're probably a software problem which can be fixed maybe with a new ROM or update or wtvr (i'm probably going to install another ROM eventually). And i'm not sure how a replacement will help with that, since I already have the KE7 firmware installed.
Just complete turn offs, cuz it might be a hardware problem, which can be solved by a replacement.
Thanks for the responses guys. Keep it up
Hmm, well i'm not really sure of anything, but that looks like a reboot to me. It might be that it turned off and you accidentally held the power button and turned it on, but since there was no card reading or anything, i think it's the "fast reboot" problem i've seen some people with on the forums. I hope it doesn't happen again
Well as the title says, I received a message that the 3.2. update was ready. I used the OTA update. The update happens in two parts.
Part 1. You get a message stating files need to be downloaded. After the download finishes, you are asked if you want to install. I said YES. The device reboots, applies the update. This takes a while. Then restarts.
Part 2. Upon restart, the tab immediately connects to the upgrade server again. Once more you are advised that there is an upgrade and that files need to be downloaded. After download, again the question do you wish to install. I said YES. Device reboots. Update is applied and ..... hangs at 21%. It has been there now for more than a half hour.
Really dont know what to do now. Help appreciated.
Edit:
Well, after having waited for what seemed an eternity, not knowing what to do, I pressed the power button until the Tab powered off. Then I prayed to the cosmos. Then I turned the Tab back on. It started applying the patch again, starting at 0% and running to 21% at high speed and, after a brief hesitation as sheep do when deciding to cross a dam, it crossed and completed the update.
Did you have more then 50% battery?
Sent from my GT-P7500 using Tapatalk HD
Mine updated just well with only one reboot. It even fixed the issue I had with the Swype keyboard (Russian numeric keys) after the last OTA upgrade some time ago. I also have the European version.
Sent from my GT-P7500 using XDA App
Nagarebozhi said:
Did you have more then 50% battery?
Sent from my GT-P7500 using Tapatalk HD
Click to expand...
Click to collapse
Yes, fully charged.
Problem solved by praying to the cosmos, see OP.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
you have a good luck.
First I had nothing but boot loops for an hour, then by some miracle, ICS finished installing. However, now i keep getting "refresh failed", and the tablet will lock up and restart itself. Should I drain the battery and let it die? What should I do to try and fix this?
mine is locking up and restarting too but only once every 30 minutes on average.... lol this is lovely.
This is driving me insane. My prime was perfect before this update. Right now it won't even boot, just bout boot loops. Already tried factory wipe too.
Sent from my Galaxy Nexus using Tapatalk
did you update via the OTA file some posted or did you download the update from asus directly through the tablet?
Directly through the tab, and I had a serial number too.
Sent from my Galaxy Nexus using Tapatalk
Getting the same thing.
Well someone from Asus development just sent me a pm asking for my serial number so they can look into it. I didn't contract them first. Hopefully something can be done. I love this tablet, but I have no use for a $500 paper weight
Sent from my Galaxy Nexus using Tapatalk
for now
just to help,
what you could do for now is downgrade by following the first part of this thread:
http://forum.xda-developers.com/showthread.php?t=1426280
I hope this will at least get it back to a working state.
let us know what happens
Hi everyone,
i don't know if someone already encountered this but sometimes my GS3 does not respond when i try to wake him up. (it's not turned off just standby). The screen stays black en nothing works. One time the screen did woke up but i couldn't unlock it because the touchscreen didnt work. It could not be turned off and the buttons didn't do anything! The only way for me to get out of this was a battery pull!
I did not root or modify anything on this phone because i like the stock samsung TW for the first time .
Did anyone else have this problem? And how did u solve this? Thank u.
Possibly due to an app you have installed.
Sent from my GT-I9300 using xda premium
dnlgee said:
Possibly due to an app you have installed.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Thank u i didn't thought of that. Is their an easy way to find out wich app this could cause? I still find it very weird. If an app is not compatible than it just shouldnt install intead of breakin the phone right? XD
This happened me last night as well. Couldn't do anything other than turn the phone off, and when it came back on it was fine again.
Unrooted as well. Would like to find out how I can prevent this from happening again?
if you are not sure about the root cause of the problem better factory reset your mobile
bala_gamer said:
if you are not sure about the root cause of the problem better factory reset your mobile
Click to expand...
Click to collapse
Yes, if it happens again than i will try that. But i already sent the unit back from were i ordered it. They will send me a new one because its their policy to send a new one if something happens in 2 weeks.
So i will see if it still occurs with the new one otherwise its one of my apps. Than i will install only a few apps and see what causes it. If it doesnt occur one more thime than the unit was faulty. Ill keep u guys updated.
chicoelnino said:
This happened me last night as well. Couldn't do anything other than turn the phone off, and when it came back on it was fine again.
Unrooted as well. Would like to find out how I can prevent this from happening again?
Click to expand...
Click to collapse
Did it happen once? My phone had it like 3 times so thats why i sent it back. But if it still occurs with my new phone than it must be one of the apps i got Luckily they got DOA policy. I asked if it includes ''the phone does not work as it should" and they said yes send it back u will get a new one yaay but now i have no phone
I had this. After a hard reset, multiple times, and configuring with no accounts (no samsaung account, no google, nothing), it still happened. I ended up returning the phone and I've not had a single problem since.
I think it was either faulty memory or a dodgy firmware flash (more likely). Either way, I didn't care to find out and now it's all good.
sama said:
I had this. After a hard reset, multiple times, and configuring with no accounts (no samsaung account, no google, nothing), it still happened. I ended up returning the phone and I've not had a single problem since.
I think it was either faulty memory or a dodgy firmware flash (more likely). Either way, I didn't care to find out and now it's all good.
Click to expand...
Click to collapse
Yes lucky i found this out early too.. Because after another week i wouldnt get a new one and now i get
Factory reset your phone.
Hope everything turns out alright.
My stock, never-rooted GT-I9300 (4.1.2, I9300BWELK1, JZO54K.I9300XXEMC2) is plagued by boot loop problems. It first started about 3 months ago, where the blue charge LED would suddenly come on and the phone would not wake from sleep. I pulled the battery, then when it was turned on it showed the initial S III logo, then the O2 logo followed by the glowing Samsung logo. Then repeated from the O2 logo endlessly. I pulled the battery again, then the next morning restarted it without the SIM or SD card in, and it had done a partial factory reset - i.e. lots of phone contacts were there with the texts, but all the settings had reverted to default. Later that day while on charge the same thing happened again, and I sent it away to O2 for repair.
When it returned, the same thing happened 6 weeks later although this time it was on when it froze and went straight to the O2/blue LED stage. Another repair (I'm fairly sure these 'repairs' were just factory resets...), and 6 weeks later exactly the same. Back to the O2 shop for another repair.
This time they replaced the 'main board' and when it came back it had a different Wi-Fi MAC address. This time only 6 days elapsed before the same fault arose again, and finally I was eligible for a replacement handset. This lasted 2 days before a boot loop condition occurred again! This time, being sure it couldn't be a hardware fault I tried my own /data and /cache wipe, which worked. I skipped all but the must-have apps, and I thought this was going to be stable but once more this past weekend the boot loop happened again (I've got my restoration procedure down to about 15 minutes thanks to the practice!)
I don't know what could be causing this and I'm fed up with resetting my phone. Are all S IIIs this unstable? I've never had a phone that required a factory reset within 18 months! When it is in the boot loop, I can access recovery and download modes, but safe-mode start-up has no effect.
The last remaining candidates I can think of are a problem with my SIM card, or a defect with my SD card... or an app. Can anyone suggest the best way to troubleshoot this? I'd really really rather not have to skip importing my settings as I have among other things many SSIDs I don't easily have access to re-create.
What ROM are you on? 4.1.2?
Sent from my GT-I9300 using Tapatalk 4
rootSU said:
What ROM are you on? 4.1.2?
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
Yes, 4.1.2. I don't recall this behaviour before I got the OTA update from 4.1.1 though
kernalk said:
Yes, 4.1.2. I don't recall this behaviour before I got the OTA update from 4.1.1 though
Click to expand...
Click to collapse
No, not all S3 owners experience this, a factory reset solves most of these issues however, if it doesn't, a trip to the Samsung service center will help.
I'd say it's probably a dodgy app, or some kind of unstable firmware update for your region/carrier, since hardware replacements didn't help with it.
Skander1998 said:
No, not all S3 owners experience this, a factory reset solves most of these issues however, if it doesn't, a trip to the Samsung service center will help.
I'd say it's probably a dodgy app, or some kind of unstable firmware update for your region/carrier, since hardware replacements didn't help with it.
Click to expand...
Click to collapse
Hmm. Thanks for the reply. I'm not sure I know anyone else with and S III on O2-UK but it seems to be news to O2, so I assumed it must be fairly rare.
I'm not sure about dodgy apps; testing them one app at a time isn't really feasible as it can take up to 6 or 7 weeks to fail judging by past performance. Are there any logs or similar that I can pull out somehow in the event of a boot loop? I've seen about logcats but I am not sure if this would be of use
Sent from my GT-I9300 using xda app-developers app
kernalk said:
Hmm. Thanks for the reply. I'm not sure I know anyone else with and S III on O2-UK but it seems to be news to O2, so I assumed it must be fairly rare.
I'm not sure about dodgy apps; testing them one app at a time isn't really feasible as it can take up to 6 or 7 weeks to fail judging by past performance. Are there any logs or similar that I can pull out somehow in the event of a boot loop? I've seen about logcats but I am not sure if this would be of use
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Everything to carries is "news".
I can't help with logs and whatnot, so I'll leave that to someone else.
You can always flash and downgrade to the older firmware that didn't give you a problem, if the problem persists, it is indeed an app.
Even when rooted, informative logs are nigh on impossible to get
Sent from my GT-I9300 using Tapatalk 4
rootSU said:
Even when rooted, informative logs are nigh on impossible to get
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
That doesn't fill me with confidence!
Thanks again for the replies. I'm not wild about downgrading. I liked the improvements! Is it possible to downgrade in a carrier supported way? Retaining warranty compliant has been rather useful in the past few months!
Sent from my GT-I9300 using xda app-developers app
You can flash any official via odin.
Sent from my GT-I9300 using Tapatalk 4
Well late Friday night it did it again. Not sure when exactly as I was asleep. Woke up in the middle of the night and went to check the time, Looked at my phone to find the blue LED on when it should have been red for charging or green for fully charged, and it was very hot - wouldn't turn on either. Pulled the battery but it kust went into the loop. I was away from home so I couldn't do any troubleshooting and had no choice but to wipe.
This time I didn't restore settings and the only apps I installed were SMS Backup & Restore and Puzzle Alarm (I know this isn't the culprit as I only started using it this week!). Gone are all my precious wifi SSIDs but otherwise I'm not sure I've noticed the difference.
So I'm now not connected to my work wifi, nor have I set up my work email or Lync - two of the things I use my phone for must after Facebook which I've also not reinstalled. Facebook mobile web is really hard to use by comparison.
By chance I popped into the O2 shop later that day and had the fortune to bump into a Samsung rep who had never heard of this and agreed that I was unfortunate to have these problems (how touching!) and suggested I speak directly to Samsung support rather than O2 which I will do this week. I will also contact O2 about a replacement SIM and look into replacing the SD too.
This is really silly. I'm not keen on downgrading the software because the first thing either Samsung or O2 will do is upgrade it again. Frankly at this point I'm fed up with the whole thing but I've got a year left on the contract and even a pretty much new handset like mine won't fetch enough.