Database Info

Anyone have a Nexus S that's still restarting on it's own?

After the 2.3.2 update, I thought everything was fine. Guess not.
Phone restarted in the middle of a phone call. What the dilly yo

I manually updated to 2.3.2, but never did faced your problem.
I heard some did but before 2.3.2, as I think it shouldve been resolved by it.
Backup and softreset and see, recovery or so.

Happened to me yesterday. Oddly enough, this was the first time it happened, and was AFTER I installed the 2.3.2 update.

This is discussed in other threads already...
The 2.3.2 update does not address the random reboots, or the reboots during calls. Google is still working on a fix for that specific problem.
The problem seems to be really random overall...some people have it frequently, others not all, some rarely. I've only had it twice, and both times only while on 2.3.1.
If you search the forum here, you'll find a thread or two with links to the Google Help Forum topic where romainguy from Google talks about the problem.
EDIT: Apparently they've found the fix, according to this post: http://www.google.com/support/forum/p/Google+Mobile/thread?tid=1b777a366748b64f&start=194
Expect an OTA in a couple of weeks.

i had it only twice
but that was because i was overloading the poor thing, with trying to do too many things simultaneously
and when it can't cope with how fast i click around stuff, and how many apps i launch and use all at the same time, it just reboots
it's not hard to reproduce
just go like a maniac and start launching apps left and right, and pull up info, make a call, send SMS, browse the web, download stuff, etc, etc
and it'll reboot as soon as it hangs
it's like a SUPER Force Close

AllGamer said:
i had it only twice
but that was because i was overloading the poor thing, with trying to do too many things simultaneously
and when it can't cope with how fast i click around stuff, and how many apps i launch and use all at the same time, it just reboots
it's not hard to reproduce
just go like a maniac and start launching apps left and right, and pull up info, make a call, send SMS, browse the web, download stuff, etc, etc
and it'll reboot as soon as it hangs
it's like a SUPER Force Close
Click to expand...
Click to collapse
LOL!
I'm pretty sure my two reboots weren't under such extreme circumstances...phone just sitting idle for a while, got a phone call, call reboots 5-15 minutes into the middle of the call.
Even so, your experience makes me wonder if just tweaking the memory management on the phone with something like AutoKiller app might help those who are having the issue more often than others. (Note that autokiller is NOT a task killer, it's poorly named. It's a way to tweak the minfree settings on the phone and let the Android built-in system still handle what's killed or not.)

distortedloop said:
I'm pretty sure my two reboots weren't under such extreme circumstances...phone just sitting idle for a while, got a phone call, call reboots 5-15 minutes into the middle of the call.
Click to expand...
Click to collapse
ok... if that's the case, no, i've yet to see the phone reboot on its own
i've had some 30ish min calls and no reboot
P.S. this issue is covered in another topic tagged as [BUG] http://forum.xda-developers.com/showthread.php?t=880497
please continue on the original topic, thx
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

sms errors

Not sure if anyone else has experienced this issue, but the past few days my texts have not been able to be sent. I get some SMS error and some code number. It never happened until a few days ago when it started happening probably about once a day. I had been on bamf a few days before it started, flashed the new bamf to see if that fixed it and I'm still getting the errors. It only happens when I hit send.
Anyone else experience this or know whats the deal with it?

I had this issue. I think its mainly network issues still going on. What I did was flashed back to stock radio and ran a different rom. Fixed it right up. But yes its a known issue.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Yeah Had Same Thing Happen To Me. Running Bamf Stripped V.1.1

My Thunderbolt just started doing this around 7AM this morning. I could receive text messages but when I tried to reply I got SMS Error Cause Code: 97 Error Class: 2
This happened to me before when I had a Droid Eris. No one could figure out what was wrong...Verizon sent me a new (refurb) phone - but the same thing happened. Eventually they had to send my case to Engineering before it was fixed. (which was approx. two weeks)
Not only have I lost SMS/MMS, just about 10 minutes ago I no longer have network access...
Does anyone have any idea what might be causing this?
I did a battery pull, didn't help.
I also flashed back to stock from VirusROM. No changes...
Thanks in advance for any help you can offer!

I had this issue on Friday and Saturday but seems to have resolved itself yesterday (for me).

I've been having this issue for weeks now, but only on 3 contacts. Only way I can send messages to those 3 contacts is by sending messages directly to them, if I reply via the message thread then it fails. It's been driving me nuts.

I'm having this issue as well, sms code 105, error class 2. And it's only with 1 contact, happens once in a while with others but not too often. this 1 contact though it fails 100% of the time. Along with that my 3g will just randomly drop and it will say "no data connectivity", and I then have to cycle back to 3g. It's a big time PITA, thats for sure. Does anyone know if this is a network issue, or is it a phone radio issue?

I've noticed it has something to do with your facebook sync. If I have my favorite widget for a couple contacts set to text it automatically puts a +1 in front if the number and sms fails. If I go into the contact card it doesn't show the +1 though. Another thing I've noticed is if your in the actual message thread, hit menu, select more, and it should list recipients phone number as on option. I can select the one without the +1 but it won't default. Been having these problems on and off for about a month now with no solid fix....
Sent from my ADR6400L using XDA App

8737 texts

I just activated my N5 this afternoon (loving it!), but I keep getting these 8737 texts. I've had this happen on other phones running AOSP roms, but this is the first phone I've owned that natively runs stock Android and I wasn't expecting this. I'm on Sprint. Is anyone else getting these?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I'm thinking it's regarding voice mail.

nsxla said:
I'm thinking it's regarding voice mail.
Click to expand...
Click to collapse
Nope, didn't have any voicemail.
Sent from my Nexus 5 using Tapatalk

maxpower7 said:
Nope, didn't have any voicemail.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
No, it is a voice mail thing. Classic Sprint problem.
I think there is a setting or something that needs to enabled.

Definitely a Sprint voicemail issue. I had the same problem and it took a lot of work to fix it. Had to call Sprint and talk to a technician. He had me disable Google Voice integration. Then he had to create a voicemail account for me (because I haven't had Sprint voicemail since they first started the GV integration a couple years ago). Then, of course, I didn't actually have voicemail. I had someone call and leave a voicemail. Finally, I deleted the new voicemail and restarted my phone a couple times. The messages were finally gone!!! After I waited a few minutes to make sure no more messages would show up, I re-enabled Google Voice integration.
That was fun!

patrascu said:
Definitely a Sprint voicemail issue. I had the same problem and it took a lot of work to fix it. Had to call Sprint and talk to a technician. He had me disable Google Voice integration. Then he had to create a voicemail account for me (because I haven't had Sprint voicemail since they first started the GV integration a couple years ago). Then, of course, I didn't actually have voicemail. I had someone call and leave a voicemail. Finally, I deleted the new voicemail and restarted my phone a couple times. The messages were finally gone!!! After I waited a few minutes to make sure no more messages would show up, I re-enabled Google Voice integration.
That was fun!
Click to expand...
Click to collapse
I've only gotten a couple so far, so it's not a big deal. Hopefully it doesn't get worse and I don't have to go to that kind of extreme.

Samsung Galaxy S7 on Verizon - MMS won't work. Period.

I got the Galaxy S7 just over a week ago. MMS and picture text haven't worked from day one. Two days later I got Root. Still doesn't work. Went through every setting on every thread I could find. Flashed patches and fixes. Nothing. Tried multiple messaging apps, still get the same error "Invalid Destination Address". If it does accept a picture on a text, it shifts it to Group Conversations, but I can't send one. Period. I performed a full wipe and flashed a custom Rom. Still nothing. Has anyone found a real fix for this or is this a complete failure on Samsung's part? Thanks.

gardener101 said:
I got the Galaxy S7 just over a week ago. MMS and picture text haven't worked from day one. Two days later I got Root. Still doesn't work. Went through every setting on every thread I could find. Flashed patches and fixes. Nothing. Tried multiple messaging apps, still get the same error "Invalid Destination Address". If it does accept a picture on a text, it shifts it to Group Conversations, but I can't send one. Period. I performed a full wipe and flashed a custom Rom. Still nothing. Has anyone found a real fix for this or is this a complete failure on Samsung's part? Thanks.
Click to expand...
Click to collapse
Did you receive and install your two configuration texts from your carrier?
If not, give them a shout and ask them to send you then, sounds like the settings just aren't in place
Might be able to do it from their site, some let you send the settings to your phone

I didn't receive anything from Verizon. I can't remember having to do that before. I was the last customer of the night when I left, my whole set up felt rushed and the phone didn't show service until the next morning. I know the APN settings aren't right. I'll again and see if I can get someone.
Thanks!!!

You could try setting it up manually too if you prefer
https://apn.gishan.net/settings/1360_13_verizon_apn_settings_for_samsung_galaxy_s7.php
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Thank you for both replies, when I called tech support and asked about this directly, they discovered my phone had not been properly activated, the woman had it fixed in two minutes. This was the problem. Thank you again!

gardener101 said:
Thank you for both replies, when I called tech support and asked about this directly, they discovered my phone had not been properly activated, the woman had it fixed in two minutes. This was the problem. Thank you again!
Click to expand...
Click to collapse
Great! Pleased it was an easy fix

blank screen

hey guys,
any of you had an issue with the screen going blank and never coming back on until the watch is rebooted? ( I have ambient screen on)
everything is still functioning, phone detects it as connected, i get vibration for notifications and can even get screenshots from the watch using the android wear app.
using stock watchfaces, not installed anything yet, only setup android pay, since i only intend to use for notifications and android pay.
this is really frustrating, it's happened 4 times within the first 24 hours...

electric0ant said:
hey guys,
any of you had an issue with the screen going blank and never coming back on until the watch is rebooted? ( I have ambient screen on)
everything is still functioning, phone detects it as connected, i get vibration for notifications and can even get screenshots from the watch using the android wear app.
using stock watchfaces, not installed anything yet, only setup android pay, since i only intend to use for notifications and android pay.
this is really frustrating, it's happened 4 times within the first 24 hours...
Click to expand...
Click to collapse
if you can't touch and wake the device, you may need to send it for RMA. Do not waste time in testing, even it is a software issue. Let them fix it for you or simply replace it.

mcdull said:
if you can't touch and wake the device, you may need to send it for RMA. Do not waste time in testing, even it is a software issue. Let them fix it for you or simply replace it.
Click to expand...
Click to collapse
thanks, yeah that's what I was thinking too. just wondering if this was a common issue.
I'm based in hk too lol, just past the 7 day direct exchange period so i guess i'll just have to wait for a repair.

electric0ant said:
thanks, yeah that's what I was thinking too. just wondering if this was a common issue.
I'm based in hk too lol, just past the 7 day direct exchange period so i guess i'll just have to wait for a repair.
Click to expand...
Click to collapse
Common I dont know, but I have experienced the same thing several times over the last few days. Nothing before that

electric0ant said:
thanks, yeah that's what I was thinking too. just wondering if this was a common issue.
I'm based in hk too lol, just past the 7 day direct exchange period so i guess i'll just have to wait for a repair.
Click to expand...
Click to collapse
It is acceptable if the watch is loaded with many software. But not normal if it is freshly setup. You may try the official rom here and see if it is okay.

I have this problem now.
Screen sometimes starts working at random for a short while but goes back to blurry.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Mine also goes blank occasionally and only reboot helps, but it's so random, and maybe once a week? so I won't even bother sending for warranty because they might send it back saying that it's not happening to them.
Yesterday it happened while I was tracking my workout so that's a bummer but happily I was able to continue after reboot.
p.s.
I'm using always on display.