cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
CaptainChaosMS
What's DOS?
Posts: 1
Registered: ‎02-16-2012
Location: Germany
Views: 300
Message 1 of 4

Defy+ regulary restarts if data is turned on

 Hi,
my Defy+ does also reboot. Let me explain what i already tryed.
i am a T-Mobile Germany user and have a data plan called Web`n`walk flat wich only allows for webtraffic eg ports 80/443 basicaly.
- I got the Handset replaced 2 times, however the handsets i got where not new they where "repaired" whatever that means. So i did not send mine and had to wait, actualy they replaced it at my door. So 3 different handset where the last one is the worst one. Anyway -> no difference.
- Under my contract i do have 2 SIM cards and i ask them to replace the older one with a new one so i tested 3 different SIM cards where the last once where n3 and n4 -> no difference
- delivered 2gb SD card, Samsung class2 8Gb, new Samsung 16 Gb class10, formated the 16Gb in the handset -> no difference
- 2.3.4 and 2.3.6 which i got some time at the second handset as OTA Update -> no difference
- 2 different MOTOBlur accounts -> no difference
- factory reset/cache wipe -> no difference
Even i experience the reboots strait after the factory reset within the start wizzard eg on the Screen where you turn on Data Usage.
- turn data connection to 2G only -> no difference
But now:
- if i turn off DataUsage keep the phone connection active and just stay on WiFi -> no reloads for hours/days

So what next ?
As the last handset keeped restarting at my house as well i connected it to the adb and capture some kernel logs.... the system dies with Kernel Panic and restarts.
Here we go with an example. It is just the panic lines and a bit above. I dont understand that mutch of linux kernel debugging however. I required i could do more logs. (only without root as the phone is on the 2.3.6 kernel ROM)


 


<pre>


02-16 19:52:01.613  1494  1515 D dalvikvm: GC_CONCURRENT freed 1576K, 43% free 5338K/9351K, external 2485K/2773K, paused 2ms+4ms
02-16 19:52:01.684  1494  2295 V SyncUpdateManager: Batching app ids: [20, 60, 70, 50, 40, 31, 80, 2, 5]; is secure: false
02-16 19:52:01.691  1494  2062 D WSBase  : processing request: sync/1/updates
02-16 19:52:01.707  1494  2062 I WSBase  : doRequest(): url: http://ws-cloud236-blur.svcmot.com:80/blur-services-1.0/ws/sync/1/updates/00003F5B40EC/4503600690315500?k=android&l=1000003f5b40ec&f=pb&p=163&h=5CROGubivKKHdhYvXTDRm1F2eVF&of
=0&ssl=0
02-16 19:52:03.770  1245  1245 D panic_daemon: bp panic!
02-16 19:52:03.809  1471  1471 D RadioSignalLevel: Gsm Radio Signal level: 5
02-16 19:52:04.270  1220  1291 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
02-16 19:52:04.277  1220  1291 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
02-16 19:52:04.285  1220  1291 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
02-16 19:52:04.293  1220  1291 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
02-16 19:52:04.309  1220  1291 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
02-16 19:52:04.316  1220  1291 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
02-16 19:52:04.949  1220  1291 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
02-16 19:52:04.957  1220  1291 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
02-16 19:52:04.973  1245  1245 D panic_daemon: ACM device enumerated!
02-16 19:52:04.973  1245  1245 D panic_daemon: BP panic ID read from the ICR register: #00000000
02-16 19:52:04.973  1245  1245 D panic_daemon: acquire wake_lock.
02-16 19:52:04.973  1245  1245 D panic_daemon: Tried to open ACM: /dev/ttyACM0 with error 13,
02-16 19:52:04.973  1220  1291 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
02-16 19:52:04.980  1220  1291 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
02-16 19:52:04.988  1220  1291 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
02-16 19:52:05.980  1245  1245 D panic_daemon: ACM device opened successfully
02-16 19:52:06.004  1245  1245 D panic_daemon: Not found /data/panicreports/bp_panic.bin1 so create it
02-16 19:52:06.004  1245  1245 D panic_daemon: Opening /data/panicreports/bp_panic.bin1
02-16 19:52:06.004  1245  1245 D panic_daemon: Written BLUR HEADER to blur bp_panic.bin file
02-16 19:52:06.004  1245  1245 D panic_daemon: Written hash key to blur bp_panic.bin file
02-16 19:52:06.004  1245  1245 D panic_daemon: Written dump APR line to blur bp_panic.bin file
02-16 19:52:06.004  1245  1245 D panic_daemon: Writing in BP panic report for blur
02-16 19:52:06.004  1245  1245 D panic_daemon: Not found /data/panic/apr/bp_panic.bin34 so create it
02-16 19:52:06.004  1245  1245 D panic_daemon: Opening /data/panic/apr/bp_panic.bin34
02-16 19:52:06.004  1245  1245 D panic_daemon: PANIC DAEMON panic id (little endian) = 0x81008
02-16 19:52:06.035  1245  1245 D panic_daemon: Failed to hash /tmp/bp_panic_message_primitive.bin
02-16 19:52:06.035  1245  1245 D panic_daemon: Read HASH key: 874e73b31bb329265155ac170caf7848
02-16 19:52:06.488  1245  1245 D panic_daemon: Successfully gziped /tmp/bp_panic_message_primitive.bin
02-16 19:52:06.488  1245  1245 D panic_daemon: Open of /tmp/bp_panic_message_primitive.bin.gz succeeded
02-16 19:52:06.488  1245  1245 D panic_daemon: Written 9 bytes to apr bp_panic.bin file
02-16 19:52:06.488  1245  1245 D panic_daemon: Written 4 bytes to apr bp_panic.bin file
02-16 19:52:06.488  1245  1245 D panic_daemon: Converted string to upper case:EPU93_U_00.60.03
02-16 19:52:06.488  1245  1245 D panic_daemon: Written 23 bytes to apr bp_panic.bin file
02-16 19:52:06.488  1245  1245 D panic_daemon: Written beginning of BP panic primitive message: 24 bytes to apr bp_panic.bin file
02-16 19:52:06.488  1245  1245 D panic_daemon: Written HASH key: 16 bytes to apr bp_panic.bin file
02-16 19:52:06.488  1245  1245 D panic_daemon: Writting 152 bytes (apr data) to blur file
02-16 19:52:06.504  1245  1245 D panic_daemon: BP panic dump completed, ready to close ttyACM device
02-16 19:52:06.512  1245  1245 D panic_daemon: release_wake_lock.
02-16 19:52:06.512  1245  1245 D panic_daemon: notify bplogd.
02-16 19:52:06.512  1245  1245 D panic_daemon: Bplogd status socket is closed. Stop.
02-16 19:52:06.512  1245  1245 D panic_daemon: terminate display
02-16 19:52:06.512  1245  1245 D panic_daemon: Waiting for the gzip_thread join
02-16 19:52:06.512  1245  1245 D panic_daemon: Expected panic_daemon exit


</pre>


 


02-16 19:52:06.512  1245  1245 D panic_daemon: release_wake_lock.
02-16 19:52:06.512  1245  1245 D panic_daemon: notify bplogd.
02-16 19:52:06.512  1245  1245 D panic_daemon: Bplogd status socket is closed. Stop.
02-16 19:52:06.512  1245  1245 D panic_daemon: terminate display
02-16 19:52:06.512  1245  1245 D panic_daemon: Waiting for the gzip_thread join
02-16 19:52:06.512  1245  1245 D panic_daemon: Expected panic_daemon exit


or another one they all look similar in my eyes.


<pre>


02-16 20:34:47.124  1893  1893 I CacheUpdateRuleCheckerS: Suggested Contacts/Data cache update already pending (ignoring this request)
02-16 20:34:47.159  1893  2123 I RuCkHd/TextRuleCheckerS: Stopping service
02-16 20:34:49.296  2385  2385 D Gps     : onLocationChanged. Accuracy: 364.04343
02-16 20:34:51.835  2385  2385 D Gps     : sendFakeNMEA
02-16 20:34:51.843  2385  2397 E NaviKernel: Unmatched position
02-16 20:34:52.273  2385  2385 D Gps     : onLocationChanged. Accuracy: 364.04343
02-16 20:34:53.265  2385  2385 D Gps     : onLocationChanged. Accuracy: 364.04343
02-16 20:34:54.273  2385  2385 D Gps     : onLocationChanged. Accuracy: 364.04343
02-16 20:34:54.327  2115  2115 D dalvikvm: GC_EXPLICIT freed 75K, 49% free 2615K/5123K, external 2357K/2773K, paused 32ms
02-16 20:34:55.296  2385  2385 D Gps     : onLocationChanged. Accuracy: 364.04343
02-16 20:34:55.312  1385  1507 I TelephonyRegistry: notifyServiceState: 0 home domestic Telekom.de Telekom.de 26201  UMTS CSS not supported -1 -1RoamInd: -1DefRoamInd: -1EmergOnly: fals
02-16 20:34:55.320  1470  1470 D PollingManager: phone state: 0 home domestic Telekom.de Telekom.de 26201  UMTS CSS not supported -1 -1RoamInd: -1DefRoamInd: -1EmergOnly: false
02-16 20:34:55.320  1455  1455 D RadioSignalLevel: Gsm Radio Signal level: 5
02-16 20:34:55.320  1455  1455 D StatusBarPolicy: ERI alert sound is disabled.
02-16 20:34:55.343  1385  1421 D ConnectivityService: Radio access technology (RAT) change - updating network settings
02-16 20:34:55.351  1385  1421 V NetworkStateTracker: Setting TCP values: [64000,128000,256000,4096,16384,110208] which comes from [net.tcp.buffersize.umts]
02-16 20:34:55.359  1385  1537 I TelephonyRegistry: notifyDataConnection: state=2 isDataConnectivityPossible=true reason=nwTypeChanged interfaceName=rmnet0 networkType=3
02-16 20:34:55.390  1385  1396 D MobileDataStateTracker: default Received state= CONNECTED, old= CONNECTED, reason= nwTypeChanged, apnTypeList= default
02-16 20:34:55.390  1385  1396 D NetworkStateTracker: setDetailed state, old =CONNECTED and new state=CONNECTED
02-16 20:34:55.390  1467  1467 D PhoneApp: [NotificationMgr] updateNetworkSelection()...state = 0 new network
02-16 20:34:55.398  1467  1467 D PhoneApp: [NotificationMgr] hideDataDisconnectedRoaming()...
02-16 20:34:55.413  1920  1920 D NetStatUtils: Receive a broadcast: android.intent.action.ANY_DATA_STATE
02-16 20:34:55.413  1920  1920 D NetStatUtils: Received android.intent.action.ANY_DATA_STATE broadcast - state = CONNECTED, unavailable = false
02-16 20:34:55.437  1729  1729 I TransactionService: MMS-STATUS - start transaction service, app version=STABLE4.5.user.4.5.1-134_DFP-231.2.3.6.Blur_Version.45.0.2310.MB526.T-Mobile.en.
alse) (config=false)
02-16 20:34:55.445  1920  1920 D NetStatUtils: The APN name is: internet.t-mobile and the interface is: rmnet0
02-16 20:34:55.445  1729  1729 I SmsReceiverService: MMS-STATUS - start sms receiver service, app version=STABLE4.5.user.4.5.1-134_DFP-231.2.3.6.Blur_Version.45.0.2310.MB526.T-Mobile.en
false) (config=false)
02-16 20:34:55.445  1920  1920 D NetStatUtils: This APN has been recorded before yet.
02-16 20:34:55.445  1765  1765 D NAB-SYNC: NABService@ : GPRS state previous = 2 new = 2
02-16 20:34:55.445  1920  1920 D NetStatUtils: This APN has been active yet. the corresponding interface is: rmnet0
02-16 20:34:55.922  1240  1240 D panic_daemon: bp panic!
02-16 20:34:56.265  2385  2385 D Gps     : onLocationChanged. Accuracy: 364.04343
02-16 20:34:56.554  1215  1302 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
02-16 20:34:56.570  1215  1302 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
02-16 20:34:56.570  1215  1302 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
02-16 20:34:56.577  1215  1302 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
02-16 20:34:56.585  1215  1302 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
02-16 20:34:56.593  1215  1302 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
02-16 20:34:57.077  1215  1302 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
02-16 20:34:57.085  1215  1302 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
02-16 20:34:57.101  1240  1240 D panic_daemon: ACM device enumerated!
02-16 20:34:57.101  1240  1240 D panic_daemon: BP panic ID read from the ICR register: #00000000
02-16 20:34:57.101  1240  1240 D panic_daemon: acquire wake_lock.
02-16 20:34:57.101  1240  1240 D panic_daemon: Tried to open ACM: /dev/ttyACM0 with error 13,
02-16 20:34:57.101  1215  1302 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
02-16 20:34:57.109  1215  1302 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
02-16 20:34:57.117  1215  1302 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UDEV_LOG' not found
02-16 20:34:57.273  2385  2385 D Gps     : onLocationChanged. Accuracy: 364.04343
02-16 20:34:58.101  1240  1240 D panic_daemon: ACM device opened successfully
02-16 20:34:58.132  1240  1240 D panic_daemon: Not found /data/panicreports/bp_panic.bin1 so create it
02-16 20:34:58.132  1240  1240 D panic_daemon: Opening /data/panicreports/bp_panic.bin1
02-16 20:34:58.132  1240  1240 D panic_daemon: Written BLUR HEADER to blur bp_panic.bin file
02-16 20:34:58.132  1240  1240 D panic_daemon: Written hash key to blur bp_panic.bin file
02-16 20:34:58.132  1240  1240 D panic_daemon: Written dump APR line to blur bp_panic.bin file
02-16 20:34:58.132  1240  1240 D panic_daemon: Writing in BP panic report for blur
02-16 20:34:58.132  1240  1240 D panic_daemon: Not found /data/panic/apr/bp_panic.bin46 so create it
02-16 20:34:58.132  1240  1240 D panic_daemon: Opening /data/panic/apr/bp_panic.bin46
02-16 20:34:58.140  1240  1240 D panic_daemon: PANIC DAEMON panic id (little endian) = 0x801df
02-16 20:34:58.163  1240  1240 D panic_daemon: Failed to hash /tmp/bp_panic_message_primitive.bin
02-16 20:34:58.163  1240  1240 D panic_daemon: Read HASH key: 8bbe03e45b92da896915807ee11830a3
02-16 20:34:58.585  1240  1240 D panic_daemon: Successfully gziped /tmp/bp_panic_message_primitive.bin
02-16 20:34:58.585  1240  1240 D panic_daemon: Open of /tmp/bp_panic_message_primitive.bin.gz succeeded
02-16 20:34:58.585  1240  1240 D panic_daemon: Written 9 bytes to apr bp_panic.bin file
02-16 20:34:58.585  1240  1240 D panic_daemon: Written 4 bytes to apr bp_panic.bin file
02-16 20:34:58.585  1240  1240 D panic_daemon: Converted string to upper case:EPU93_U_00.60.03
02-16 20:34:58.585  1240  1240 D panic_daemon: Written 23 bytes to apr bp_panic.bin file
02-16 20:34:58.585  1240  1240 D panic_daemon: Written beginning of BP panic primitive message: 24 bytes to apr bp_panic.bin file
02-16 20:34:58.585  1240  1240 D panic_daemon: Written HASH key: 16 bytes to apr bp_panic.bin file
02-16 20:34:58.585  1240  1240 D panic_daemon: Writting 152 bytes (apr data) to blur file
02-16 20:34:58.609  1240  1240 D panic_daemon: BP panic dump completed, ready to close ttyACM device
02-16 20:34:58.617  1240  1240 D panic_daemon: release_wake_lock.
02-16 20:34:58.617  1240  1240 D panic_daemon: notify bplogd.
02-16 20:34:58.617  1240  1240 D panic_daemon: Bplogd status socket is closed. Stop.
02-16 20:34:58.617  1240  1240 D panic_daemon: terminate display
02-16 20:34:58.617  1240  1240 D panic_daemon: Waiting for the gzip_thread join
02-16 20:34:58.617  1240  1240 D panic_daemon: Expected panic_daemon exit


</pre>


BTW there are Threats in a germany Forum about the same behaviour http://www.android-hilfe.de/motorola-defy-plus-forum/150284-neustart-des-defy.html and one in eh XDA Developers Forum http://forum.xda-developers.com/showthread.php?t=1336331
 

Mto
Bit Torrent
Posts: 921
Registered: ‎07-10-2010
Location: United Kingdom
Views: 300
Message 2 of 4

Re: Defy+ regulary restarts if data is turned on

From the contact center, do you have an incident number in the format 11XXXX-0XXXXX? If not, could you send me your phone's IMEI as private message?


Does it also reboot when you use other apps or the internet browser, or only when you use Navigon Select?


Are you able to try it with a simcard with unrestricted mobile access, i.e. no ports blocked? 


 


My guess:


The problem could be Navigon online license check when you start the app.


From my experience, Navigon does not start when no data connection is present, as it's needed for said license check.


What could also be possible is, that if there's no data connection at all, Navigon select uses some kind of offline mode and starts normally.


When you have a data connection, but all ports are blocked but 80 and 443, Navigon may think there is a full internet connection, but in fact license check might be blocked, leading to unpredictable results.

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

Re: Defy+ regulary restarts if data is turned on


It is the first post with logs of a defy plus reboot... someone that knows about android will find it useful I think, and will try to solve problems on defy+/android devices...

Instead that you point out another app, that a lot of people having the same issue on defy+ DO NOT have?



PLEASE. MOTOROLA HAS TO PAY ANDROID KERNEL DEVELOPERS TO FIND A SOLUTION AND SUBMIT A FIX. Then do a phone software upgrade.



If not, motorola continues selling hardware with serious issues, and should be sent to court.



Defy plus just DO NOT WORK PROPERLY when using 3g!

MotoAgent
MotoAgent
Posts: 2,132
Registered: ‎07-20-2012
Location: United Kingdom
Views: 300
Message 4 of 4

Re: Defy+ regulary restarts if data is turned on


Hi luuuciano,



This thread is over a year old. I am not sure that reviving it will help. Lets keep the discussion to the threads you already posted in.



I am locking this thread now.



Any questions about this, please send me a PM.



Cheers,



Nicole