cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
xiao1
What's DOS?
Posts: 9
Registered: ‎11-21-2011
Location: United Kingdom
Views: 3,528
Message 1 of 13

Defy+ mb526 sometimes reboots itself several times

Defy+ sometimes reboots itself several times continuously

Its in my pocket and suddenly i hear a notification ring and check it, and its showing that the SD Card has been mounted meaning it was rebooted.

And it will keep rebooting 4 or 5 times.

However it has not done this in a few weeks now...

mortensa
What's DOS?
Posts: 1
Registered: ‎09-21-2011
Views: 3,528
Message 2 of 13

Re: Defy+ mb526 sometimes reboots itself several times

Hi

We have several defy's running and one of ours did the same. We sent it to motorola repair service and got the mainboard exchanged. Now awaiting the phone to get back, so we can test it.

xiao1
What's DOS?
Posts: 9
Registered: ‎11-21-2011
Location: United Kingdom
Views: 3,528
Message 3 of 13

Re: Defy+ mb526 sometimes reboots itself several times

Hi mortensa




Any News?

luuuciano
What's DOS?
Posts: 10
Registered: ‎03-15-2013
Location: Argentina
Views: 3,528
Message 4 of 13

Re: Defy+ mb526 sometimes reboots itself several times


The news is that Motorola continues selling hardware with serious issues when its used with 3g on...



And they just DO NOT CARE to really solve the customers issues, they just do not answer, or points the ball out.



A lawyer should send them to the court.

MotoAgent
MotoAgent
Posts: 2,132
Registered: ‎07-20-2012
Location: United Kingdom
Views: 3,528
Message 5 of 13

Re: Defy+ mb526 sometimes reboots itself several times





Hi luuuciano,



I can see that you are very frustrated, the solution to disable 3G does not look very appealling to me either.



Changing the SIM card usually helped.



Are you still experiencing this issue? How many SIM cards did you try?



Please let me know.



Cheers,



Nicole






 

CarlosJC
What's DOS?
Posts: 4
Registered: ‎04-25-2013
Location: Argentina
Views: 3,528
Message 6 of 13

Re: Defy+ mb526 sometimes reboots itself several times


Defy+ Random reboots.




I'm from Argentina and I've recently bought a Motorola Defy+ Phone. Unfortunately, the phone is suffering from very frequent random reboots (up to 15 times a day!). Its very very annoying...

 


Phone details:


   --- System version: 45.2.500.MB526.AmericaMovil.en.01


   --- Android version: 2.3.5


   --- Compilation number: 4.5.2-51_DFL-50



This is the logcat output just before one random reboot:



04-25 17:47:53.358  1377  1388 D WifiService: ACTION_SCREEN_ON -- Checked by Moto

04-25 17:47:53.366  1229  1229 W SSM     : no ack

04-25 17:47:53.389  1507  1507 D PowerProfileSvc: Receiver: Screen On

04-25 17:47:53.389  1507  1708 D PowerProfileSvc: Start: Received action: android.intent.action.batteryprofile.SCR_ON

04-25 17:47:53.389  1507  1708 D PowerProfileSvc: Algo:Run: current state --> 0Arg --> 2

04-25 17:47:53.397  1507  1708 D PowerProfileSvc: Algo:Run: new state is --> 0

04-25 17:47:55.858  1377  1381 I dalvikvm: Total arena pages for JIT: 11

04-25 17:47:55.866  1377  1381 I dalvikvm: Total arena pages for JIT: 12

04-25 17:48:00.272  3486  3512 D dalvikvm: GC_FOR_MALLOC freed 1300K, 52% free 3763K/7687K, external 3397K/3878K, paused 38ms

04-25 17:48:10.889  1448  1448 D RadioSignalLevel: Gsm Radio Signal level: 5

04-25 17:48:13.631  1377  1516 D dalvikvm: GC_EXPLICIT freed 1731K, 35% free 8003K/12295K, external 4729K/5568K, paused 99ms

04-25 17:48:14.631  1377  2588 I ActivityManager: Starting: Intent { cmp=lysesoft.andftp/.FTPTransferActivity (has extras) } from pid 3486

04-25 17:48:14.717  1377  1853 W InputManagerService: Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@40a6ff00

04-25 17:48:14.803  3486  3486 D dalvikvm: GC_EXTERNAL_ALLOC freed 260K, 51% free 3786K/7687K, external 3763K/3878K, paused 33ms

04-25 17:48:14.842  1377  1406 I ActivityManager: Displayed lysesoft.andftp/.FTPTransferActivity: +198ms

04-25 17:48:15.147  1232  1232 D panic_daemon: bp panic!

04-25 17:48:15.772  1210  1251 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found

04-25 17:48:15.780  1210  1251 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found

04-25 17:48:15.788  1210  1251 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found

04-25 17:48:15.796  1210  1251 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found

04-25 17:48:15.803  1210  1251 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found

04-25 17:48:15.811  1210  1251 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found

04-25 17:48:16.296  1210  1251 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found

04-25 17:48:16.303  1210  1251 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found

04-25 17:48:16.311  1232  1232 D panic_daemon: ACM device enumerated!

04-25 17:48:16.311  1232  1232 D panic_daemon: BP panic ID read from the ICR register: #00000000

04-25 17:48:16.311  1232  1232 D panic_daemon: acquire wake_lock.

04-25 17:48:16.311  1232  1232 D panic_daemon: Tried to open ACM: /dev/ttyACM0 with error 13,

04-25 17:48:16.311  1210  1251 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found

04-25 17:48:16.311  1210  1251 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found

04-25 17:48:16.319  1210  1251 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found

04-25 17:48:17.311  1232  1232 D panic_daemon: ACM device opened successfully

04-25 17:48:17.342  1232  1232 D panic_daemon: Not found /data/panicreports/bp_panic.bin1 so create it

04-25 17:48:17.342  1232  1232 D panic_daemon: Opening /data/panicreports/bp_panic.bin1

04-25 17:48:17.342  1232  1232 D panic_daemon: Written BLUR HEADER to blur bp_panic.bin file

04-25 17:48:17.342  1232  1232 D panic_daemon: Written hash key to blur bp_panic.bin file

04-25 17:48:17.342  1232  1232 D panic_daemon: Written dump APR line to blur bp_panic.bin file

04-25 17:48:17.342  1232  1232 D panic_daemon: Writing in BP panic report for blur

04-25 17:48:17.358  1232  1232 D panic_daemon: Not found /data/panic/apr/bp_panic.bin20 so create it

04-25 17:48:17.358  1232  1232 D panic_daemon: Opening /data/panic/apr/bp_panic.bin20

04-25 17:48:17.366  1232  1232 D panic_daemon: PANIC DAEMON panic id (little endian) = 0x8100a

04-25 17:48:17.405  1232  1232 D panic_daemon: Failed to hash /tmp/bp_panic_message_primitive.bin

04-25 17:48:17.405  1232  1232 D panic_daemon: Read HASH key: c6d490c682bad11d4d8d7e0e577c73b8

04-25 17:48:18.077  1232  1232 D panic_daemon: Successfully gziped /tmp/bp_panic_message_primitive.bin

04-25 17:48:18.077  1232  1232 D panic_daemon: Open of /tmp/bp_panic_message_primitive.bin.gz succeeded

04-25 17:48:18.077  1232  1232 D panic_daemon: Written 9 bytes to apr bp_panic.bin file

04-25 17:48:18.077  1232  1232 D panic_daemon: Written 4 bytes to apr bp_panic.bin file

04-25 17:48:18.077  1232  1232 D panic_daemon: Converted string to upper case:EPU93_U_00.61.00

04-25 17:48:18.077  1232  1232 D panic_daemon: Written 23 bytes to apr bp_panic.bin file

04-25 17:48:18.077  1232  1232 D panic_daemon: Written beginning of BP panic primitive message: 24 bytes to apr bp_panic.bin file

04-25 17:48:18.077  1232  1232 D panic_daemon: Written HASH key: 16 bytes to apr bp_panic.bin file

04-25 17:48:18.077  1232  1232 D panic_daemon: Writting 152 bytes (apr data) to blur file

04-25 17:48:18.131  1232  1232 D panic_daemon: BP panic dump completed, ready to close ttyACM device

04-25 17:48:18.139  1232  1232 D panic_daemon: release_wake_lock.

04-25 17:48:18.139  1232  1232 D panic_daemon: notify bplogd.

04-25 17:48:18.139  1232  1232 D panic_daemon: Bplogd status socket is closed. Stop.

04-25 17:48:18.139  1232  1232 D panic_daemon: terminate display

04-25 17:48:18.139  1232  1232 D panic_daemon: Waiting for the gzip_thread join

04-25 17:48:18.139  1232  1232 D panic_daemon: Expected panic_daemon exit

Moto Sr Moderator
Moto Sr Moderator
Posts: 28,186
Registered: ‎02-02-2016
Location: US
Views: 3,528
Message 7 of 13

Re: Defy+ mb526 sometimes reboots itself several times


What troubleshooting steps have been tried? Have you done a Factory reset? If so, have you used the phone with NO applications installed to see if it is more stable? Have you tried replacing the SIM card? Have you tried running without an SD card?



Also, the error right before the reboot is seen here as well with HTC device;



 http://www.lysesoft.com/support/forums/viewtopic.php?t=68&p=424



 



Have you tried removing AndFTP? It may be cooincidental - but there are no 3G problems with Moto phones as you suggest. In the USA all phones operate on 3g 99% of the time. 


* Search box is your friend * I don't respond to PM if question belongs in forum
CarlosJC
What's DOS?
Posts: 4
Registered: ‎04-25-2013
Location: Argentina
Views: 3,528
Message 8 of 13

Re: Defy+ mb526 sometimes reboots itself several times


Thank you for your reply.



I've tried many many things, among them factory reset, removing and changing sdcard, etc. 



After reading a lot on the web, I've managed to understand a little bit more. The problem seems to be related to a software bug triggered by an event in the radio connection with my provider (Claro, Argentina).



Here is a strong hint: My phone starts with random reboots only in some places of the city. Unfortunately, when I'm at home (or in the neighborhood, a few blocks away from my house), random reboots are very very frequent (also, I've found that some spots in my house are worse than others!!). However, in most places the phone behaves normally: for example, at work (where I spend a lot of time) the phone NEVER reboots. 



A second hint: In the log I shared, the first "panic_daemon" line says "bp panic!" (times stamp 04-25 17:48:15.147). BP stands for "Baseband Processor"!! So, the fact is that the radio goes into "panic mode" triggering a reboot of the phone.



In a few hours (at home), I will try to catch the radio log in one of these "random reboots".

luuuciano
What's DOS?
Posts: 10
Registered: ‎03-15-2013
Location: Argentina
Views: 3,528
Message 9 of 13

Re: Defy+ mb526 sometimes reboots itself several times


Carlos, I think this happens on certain locations where is full of antennas, or maybe Claro do something that gets mad the phone mobile. I have Claro as phone provider and have the same issues on Córdoba downtown... a few km outhere 3g works ok.



But I live in downtown... so, Im forced to use the slooooower 2g! to not get more than 30 reboots at day...



I think Claro/Motorola knows something is brong, but just do not care?? the only people trying to see what happens (logs, etc) are the customers...

CarlosJC
What's DOS?
Posts: 4
Registered: ‎04-25-2013
Location: Argentina
Views: 3,528
Message 10 of 13

Re: Defy+ mb526 sometimes reboots itself several times


Luuuciano, thanks for your reply.



I'm confident that this is a well known issue for Google, Motorola and even Claro. It seems that they simply don't care... There are some official bugfixes around, but all of them for newer versions of Android....



The problem is related to several bugs first filled about five year ago (see, for example android issue #2845 http://code.google.com/p/android/issues/detail?id=2845)!! Actually, there is a very well known RIL (Radio Interface Layer) bug, in which the phone radio loose connexion and never re-acquires it. The crazy thing is that triggering a "reboot" is how android deals with this bug... The "Random reboots" bug is some kind of workaround to the "loosing connexion and never re-acquire it" bug... That's very sad...



It goes without saying that I am very disappointed with Motorola and how they handle this kind of things... I'm starting to feel very angry and I want my money back...