Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

[BUG] Phone reboots during an active call + USB storage (apps2sd) full

OP americancrew

9th January 2011, 09:53 AM   |  #41  
ryan562's Avatar
Senior Member
Thanks Meter: 63
 
992 posts
Join Date:Joined: Feb 2010
Happened to me once this past week about ten minutes in to a phone call. Wifi was on.I'm also running modaco r3.

Sent from my Dell Streak using XDA App
9th January 2011, 10:34 AM   |  #42  
AllGamer's Avatar
Retired Forum Moderator
Flag buried under loads of work IRL
Thanks Meter: 1,580
 
11,521 posts
Join Date:Joined: May 2008
Donate to Me
More
i guess, i could say i was pretty lucky

i had a 30min interview using the SNS, with bluetooth on Bionix ROM

driving from small streets & highways during rush hour, and no drop call during the whole thing

oh, the SNS was streaming MP3 to my car via bluetooth before the phone call, and when the call ended, the music resumed
9th January 2011, 04:03 PM   |  #43  
Senior Member
Flag Los Angeles, CA
Thanks Meter: 315
 
3,152 posts
Join Date:Joined: Feb 2010
More
Quote:
Originally Posted by distortedloop

Just had it happen to me for the first time. I starred the issue;; but notice there's only 32 stars on it.

I've been unable to reproduce a phone reboot during a call. I've made several calls to my phone and it never has rebooted since that one time. I was hoping to catch a log entry on the phone.

The problem certainly seems random and inconsistent across users.

At least Google is aware of it, can reproduce it, and claims to be working on it (on the Help forum) despite not acknowledging the bug report yet.
9th January 2011, 05:26 PM   |  #44  
AllGamer's Avatar
Retired Forum Moderator
Flag buried under loads of work IRL
Thanks Meter: 1,580
 
11,521 posts
Join Date:Joined: May 2008
Donate to Me
More
what are the conditions to reproduce the reboot problem?

i'd like to avoid it if at all possible
10th January 2011, 02:58 PM   |  #45  
Senior Member
Flag Milton Keynes
Thanks Meter: 2
 
167 posts
Join Date:Joined: May 2005
More
The bug report has been declined at http://code.google.com/p/android/issues/detail?id=13674 so it doesn't look like they think it's a gingerbread problem.
10th January 2011, 03:06 PM   |  #46  
Junior Member
Thanks Meter: 0
 
6 posts
Join Date:Joined: Jan 2011
Quote:
Originally Posted by herman3101

The bug report has been declined at ... so it doesn't look like they think it's a gingerbread problem.

That's not exactly true. The close comment said:

Quote:

Although the Nexus One and Nexus S run pure Android, this issue tracker is not the place to report bugs for these devices. I am going to continue posting updates to this issue on the Google Mobile forum.

In the Google Mobile forum mentioned an official Google employee posted:

Quote:

Hey all,

So we've successfully reproduced this issue and are in the process of investigating with Samsung. I'll provide updates as soon as I have them.

-Ry Guy

So it seems there is a real problem. Google has confirmed and reproduced it, but have yet to confirm if it's software or hardware. However, by the number of people returning their devices and having the same problem again makes me think its a software issue.

On a personal note, I find if difficult to distinguish a bug in the Android software and a bug in software running on a "Pure Android experience device". Aren't they the same thing?
10th January 2011, 03:16 PM   |  #47  
Senior Member
Flag Teddington
Thanks Meter: 2
 
215 posts
Join Date:Joined: Jan 2009
More
Quote:
Originally Posted by andymason

I find if difficult to distinguish a bug in the Android software and a bug in software running on a "Pure Android experience device". Aren't they the same thing?

Yes. I know it might seem prissy of me, but after trialling WP7 on the HTC HD7 and giving it back, I was hoping Google would do a better job of keeping its dedicated user-base happy than to dismiss out-of-hand a forum teeming with irked early-adopters, simply because an employee (wrongly) felt there was a semantic reason not to reply to them there.

("sounds like someone's got a case of the mondays!" )
10th January 2011, 03:40 PM   |  #48  
Senior Member
Flag Los Angeles, CA
Thanks Meter: 315
 
3,152 posts
Join Date:Joined: Feb 2010
More
Quote:
Originally Posted by andymason

That's not exactly true. The close comment said:

In the Google Mobile forum mentioned an official Google employee posted:

So it seems there is a real problem. Google has confirmed and reproduced it, but have yet to confirm if it's software or hardware. However, by the number of people returning their devices and having the same problem again makes me think its a software issue.

I've posted a few times in this thread (on page 3) that I think the Google Help Forums are probably a better place to report issues these days. They seem to get a lot more attention than the bug reporting site. I even posted a link to the specific question/answer where Google ry_guy says they're aware of it.

I think we should focus future bug reports on any issue to BOTH Help and Code sites.

Quote:
Originally Posted by andymason

On a personal note, I find if difficult to distinguish a bug in the Android software and a bug in software running on a "Pure Android experience device". Aren't they the same thing?

I agree. I see a lot of "this isn't an Android problem replies and bug reports closed over there.

It's almost as confusing as the policy around here over what goes in the General section, and what goes in the Q&A section... LOL
11th January 2011, 06:29 AM   |  #49  
gogol's Avatar
Senior Member
Thanks Meter: 158
 
3,478 posts
Join Date:Joined: May 2005
One thing that I read there, all bug reports are using Android 2.3.1 ...

Anyone has this bug on 2.3?
11th January 2011, 02:11 PM   |  #50  
Senior Member
Flag Los Angeles, CA
Thanks Meter: 315
 
3,152 posts
Join Date:Joined: Feb 2010
More
Quote:
Originally Posted by gogol

One thing that I read there, all bug reports are using Android 2.3.1 ...

Anyone has this bug on 2.3?

It's a good question. Is there anyone who didn't rush to go to 2.3.1 and is actually on 2.3?

Actually, I've read in a couple of places people saying that they've done a factory reset "back to 2.3" and not experienced the problem since. I don't think a regular "factory reset" would change your build number...it's only supposed to wipe the /data partition, not re-write the /system one.

This is a serious bug, and Google is aware of it, we should get a fix pretty quickly.

Post Reply Subscribe to Thread

Tags
apps2sd, move application, problem, reboot, usb storage
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes