Help My D3 crashed with "BP panicked" error

[beowulf7]

I was using the weather applet on my Droid 3 and while doing so, a little terminal window appeared in the top half of the phone and the following lines were printed:

BP paniced

Into BP core dump mode

Trying to open USB ...

During this time, I was still kind of able to use the phone by moving between the different screens, but the screen was in sort of hyper mode and blinking/flashing rapidly. Then the phone just turned off. I turned it on and it rebooted normally. Has anyone encountered this yet? It's a bizarre error, but it doesn't appear that any data was lost.

 

[aostang]

I was using the weather applet on my Droid 3 and while doing so, a little terminal window appeared in the top half of the phone and the following lines were printed:

BP paniced

Into BP core dump mode

Trying to open USB ...

During this time, I was still kind of able to use the phone by moving between the different screens, but the screen was in sort of hyper mode and blinking/flashing rapidly. Then the phone just turned off. I turned it on and it rebooted normally. Has anyone encountered this yet? It's a bizarre error, but it doesn't appear that any data was lost.

Is this reproducible? Would like to know because this is the kind of "odd" behavior devs look for when trying to find exploits.

 

[beowulf7]

Is this reproducible? Would like to know because this is the kind of "odd" behavior devs look for when trying to find exploits.

Unfortunately, I cannot reproduce that error. While my phone has crashed a few times since I got it 3 weeks ago, this is the only time I saw the "BP paniced" error (I assume it's Motorola's typo for "panicked"). And it had never crashed before while I was using the weather app.

 

[maldroid]

I saw a wierd green squarewith a circuitboard happen like 3 times , screen went black. I was going to take it back in but i haven't seen it again that was sunday. Sounds similar to the op's description

 

[thebarbrr]

Unfortunately, I cannot reproduce that error. While my phone has crashed a few times since I got it 3 weeks ago, this is the only time I saw the "BP paniced" error (I assume it's Motorola's typo for "panicked&quot. And it had never crashed before while I was using the weather app.

This exact same thing happened on my brothers Droid3...but has not happened since...it would not stop so had to turn phone off ...was very weird..but your not alone..but he didn't have that weather app installed

 

[maldroid]

I saw a wierd green squarewith a circuitboard happen like 3 times , screen went black. I was going to take it back in but i haven't seen it again that was sunday. Sounds similar to the op's description

I rebooted it and I haven't been able to reproduce it as well, but it was definately a glitch of some sort

 

[beowulf7]

This exact same thing happened on my brothers Droid3...but has not happened since...it would not stop so had to turn phone off ...was very weird..but your not alone..but he didn't have that weather app installed

I see, thanks for confirming. So there's definitely a(nother) bug in the D3 that is causing it to go haywire. It's only happened to my phone once (so far).

 

[Jonny9797]

My friend has been complaining about this with his D3 for a week or two now, he says it has happened several times. Does anyone have any leads on what could be causing this? I personally have a D3 and have never seen this issue.

 

[beowulf7]

Wow, several times, that's bad. Jonny, can your friend reproduce this error at will? Mine only happened that one time (so far).

 

[Jonny9797]

Unfortunately no. He has yet to notice a pattern. He had no idea what it was, it finally happened with me around so he could show me, and that's when I posted. He said it has happened 4+ times. : / I am trying to think of any differences between his and mine (I haven't had this issue). We bought them at the same store on the same day. He uses Launcher Pro, I use ADW. He uses some wallpaper rotator that I don't. I'm sure there are a dozen other things, I will have to check next time I see him.

 

[ekyle]

I saw a wierd green squarewith a circuitboard happen like 3 times , screen went black. I was going to take it back in but i haven't seen it again that was sunday. Sounds similar to the op's description

I had the green square thing happen once. Only when I switched orientation on the lock screen or home screen. Reboot fixed it and it didn't result in any issues.

 

[Jonny9797]

I've had the green transitions thing too. It's a separate issue I believe. I am pretty sure I read somewhere else that green is the color used to clear the framebuffer, so that makes it seems like a graphics sync issue. My friend with the BP panic issue has had the green transitions as well, but I don't believe it ever coincided with the BP panic.

 

[maldroid]

I've had the green transitions thing too. It's a separate issue I believe. I am pretty sure I read somewhere else that green is the color used to clear the framebuffer, so that makes it seems like a graphics sync issue. My friend with the BP panic issue has had the green transitions as well, but I don't believe it ever coincided with the BP panic.

Thanks guys!!

 

[Jonny9797]

Andddddd I just got a BP panic error on *my* phone. It was just as a call was ending. The only other thing I noticed was that my phone said no signal as it was happening, although I should have had full bars. I was also charging at the time.

 

[studentbridges]

Andddddd I just got a BP panic error on *my* phone. It was just as a call was ending. The only other thing I noticed was that my phone said no signal as it was happening, although I should have had full bars. I was also charging at the time.

I think we're getting closer to the issue. I just had this happen on my D3, my phone was charging, I had the keyboard slid out, and was replying to a text as it was charging using Google Voice. Like Jonny, My phone was charging, but as I unplugged the charger from the wall (BUT NOT FROM THE PHONE), the signal went out and the error showed, then the phone rebooted.

I have noticed my signal disappearing other times, at the same time, my bluetooth disconnects, and the GPS stops working... But have not seen that error until tonight.

Hope this helps guys.

 

[ekyle]

I think we're getting closer to the issue. I just had this happen on my D3, my phone was charging, I had the keyboard slid out, and was replying to a text as it was charging using Google Voice. Like Jonny, My phone was charging, but as I unplugged the charger from the wall (BUT NOT FROM THE PHONE), the signal went out and the error showed, then the phone rebooted.

I have noticed my signal disappearing other times, at the same time, my bluetooth disconnects, and the GPS stops working... But have not seen that error until tonight.

Hope this helps guys.

I've had my signal drop several times. Once I was using Runkeeper to track a bike ride and all communications stopped working. They all came back on their own (with no error), but it's really annoying.

 

[Jonny9797]

I've had my signal drop several times. Once I was using Runkeeper to track a bike ride and all communications stopped working. They all came back on their own (with no error), but it's really annoying.

I have had the same issue several times as well - total communications loss without error. I usually end up rebooting. Very frustrating.

 

[imagramma]

I just received the same error as Beowulf7:
BP paniced
Into BP core dump mode
Trying to open USB

The phone flashed the error msg a few times then just shut off and rebooted. Appears to be fine now??

 

[ekyle]

I have had the same issue several times as well - total communications loss without error. I usually end up rebooting. Very frustrating.

Honestly, I'm just starting to expect this kind of weird behavior from Android. They must not go through the same QC that iPhones do :/

 

[aostang]

Honestly, I'm just starting to expect this kind of weird behavior from Android. They must not go through the same QC that iPhones do :/

Don't blame Android. Blame the manufacturers. They're the ones that pair the hardware and load up the bloat.

 

[beowulf7]

I guess this type of odd behavior is normal for Android phones? That's not very comforting to hear. This is my first smartphone, so I'm relatively new to Android.

 

[ekyle]

Don't blame Android. Blame the manufacturers. They're the ones that pair the hardware and load up the bloat.

This is true. I wish VZW would get a Nexus device. I'm guessing Google said no to the VZW branded apps so they won't sell it. Just a guess.

I guess this type of odd behavior is normal for Android phones? That's not very comforting to hear. This is my first smartphone, so I'm relatively new to Android.

It's not common, but some phones are quirky. Workarounds are typically simple and the problems that can't be fixed with workarounds are usually resolved the the OEMs with an update.

Android is my favorite mobile OS by far.

 

[imnotmikal]

Don't blame Android. Blame the carriers. They're the ones that load up the bloat.

Fixed.

 

[beowulf7]

...

It's not common, but some phones are quirky. Workarounds are typically simple and the problems that can't be fixed with workarounds are usually resolved the the OEMs with an update.

Android is my favorite mobile OS by far.

Yeah, the more complicated these phones get, the quirkier they will get. I guess it's like comparing an old car where only mechanical stuff can go wrong w/ a modern car, that has many electronics bugs.

My phone went weird on me again last Fri. evening. I was on the phone, using speaker, while driving. I finished driving, parked, and tried to turn the screen on, but it wouldn't turn on. The phone conversation was still going fine.

I ended my call (the other person hung up). My screen still wouldn't turn on. I could hear a very slight hiss/buzzing sound from the speaker. I held the power button for a while, but no response.

I then went in the glove box and took out the car charger and hooked it up to my phone and turned the car back on. About 30-60 sec. later, the phone booted up.

Wow, that was odd. In this particular case, GPS wasn't turned on, unlike the time before that I thought it was GPS-related. These little things make me a little nervous, but I guess that's the cost of having a powerful and feature-rich phone.

 

[ekyle]

Yeah, the more complicated these phones get, the quirkier they will get. I guess it's like comparing an old car where only mechanical stuff can go wrong w/ a modern car, that has many electronics bugs.

My phone went weird on me again last Fri. evening. I was on the phone, using speaker, while driving. I finished driving, parked, and tried to turn the screen on, but it wouldn't turn on. The phone conversation was still going fine.

I ended my call (the other person hung up). My screen still wouldn't turn on. I could hear a very slight hiss/buzzing sound from the speaker. I held the power button for a while, but no response.

I then went in the glove box and took out the car charger and hooked it up to my phone and turned the car back on. About 30-60 sec. later, the phone booted up.

Wow, that was odd. In this particular case, GPS wasn't turned on, unlike the time before that I thought it was GPS-related. These little things make me a little nervous, but I guess that's the cost of having a powerful and feature-rich phone.

There are only a few things about this phone that bother me. The signal quality seems to drop to 1X once in awhile, sometimes lose signal altogether (hasn't happened recently). My other phones didn't do that in my area. The blue tint with the camera flash. The GPS bug where it will occasionally not work and you need to turn off all location settings and turn them back on.

Still far better than my Thunderbolt though.