Databases
StackOverflow2013
Postsdbo
POwidget force closes but logcat tells me nothing
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POwidget force closes but logcat tells me nothing
    primarykey
    data
    text
    <p>Hi I've created a home screen widget. it works great on my devices but crashes on other at (seemingly) random intervals, i tried to study the logcats that these users send me but i can't seem to find what is the error/exception that causes the force-closing</p> <p>here's 1 log for an example:</p> <pre><code> I/ActivityThread(29303): Publishing provider com.facebook.katana.provider.UserStatusesProvider: com.facebook.katana.provider.UserStatusesProvider I/ActivityThread(29303): Publishing provider com.facebook.katana.provider.PhotosProvider: com.facebook.katana.provider.PhotosProvider D/dalvikvm(29303): GC_FOR_MALLOC freed 3424 objects / 203960 bytes in 51ms D/dalvikvm(29303): GC_EXTERNAL_ALLOC freed 2369 objects / 136048 bytes in 58ms D/dalvikvm(29303): GC_FOR_MALLOC freed 875 objects / 52040 bytes in 73ms D/dalvikvm(29303): GC_FOR_MALLOC freed 1530 objects / 447680 bytes in 38ms D/dalvikvm( 86): GC_EXPLICIT freed 23778 objects / 1131048 bytes in 132ms I/Gmail (25020): MainSyncRequestProto: lowestBkwdConvoId: 0, highestHandledServerOp: 1804642, normalSync: true D/GTalkService( 196): [RosterMgr] roster not modified D/GTalkService( 196): [OtrMgr] OTR not modified D/AccelerometerListener( 167): orientation: horizontal D/PhoneApp( 167): updateProximitySensorMode: releasing... E/Sensors ( 86): CAPELLA_CM3602_IOCTL_ENABLE error (I/O error) I/power ( 86): *** set_screen_state 1 D/SurfaceFlinger( 86): Screen about to return, flinger = 0x1fe220 D/GoogleLoginService( 196): onBind: Intent { act=android.accounts.AccountAuthenticator cmp=com.google.android.gsf/.loginservice.GoogleLoginService } D/InCallScreen( 167): onResume()... D/PhoneApp( 167): disable status bar D/PhoneApp( 167): StatusBarManager.DISABLE_EXPAND D/InCallScreen( 167): - onResume: initial status = SUCCESS D/InCallScreen( 167): setInCallScreenMode: NORMAL D/InCallScreen( 167): syncWithPhoneState()... D/PhoneUtils( 167): dumpCallState(): D/PhoneUtils( 167): - Phone: Handler{44954ab8}, name = GSM, state = OFFHOOK D/PhoneUtils( 167): - FG call: ACTIVE isAlive true isRinging false isDialing false isIdle false hasConnections true D/PhoneUtils( 167): - BG call: IDLE isAlive false isRinging false isDialing false isIdle true hasConnections false D/PhoneUtils( 167): - RINGING call: IDLE isAlive false isRinging false isDialing false isIdle true hasConnections false D/PhoneUtils( 167): - hasRingingCall false hasActiveCall true hasHoldingCall false allLinesTaken false D/PhoneUtils( 167): - Ringer state: false D/InCallScreen( 167): updateScreen()... D/InCallScreen( 167): - updateScreen: updating the in-call UI... I/power ( 86): *** set_screen_state 1 D/PhoneApp( 167): updateWakeState: callscreen true, dialer false, speaker false... D/PhoneApp( 167): updateWakeState: keepScreenOn = false (isRinging false, isDialing false, showingDisc false) D/skia ( 86): purging 193K from font cache [8 entries] D/CallNotifier( 167): stopRing()... (OFFHOOK state) D/Ringer ( 167): stopRing()... D/Ringer ( 167): - stopRing: null mRingHandler! D/InCallScreen( 167): onPhoneStateChanged()... D/InCallScreen( 167): updateScreen()... D/InCallScreen( 167): - updateScreen: updating the in-call UI... D/PhoneApp( 167): updateWakeState: callscreen true, dialer false, speaker false... D/PhoneApp( 167): updateWakeState: keepScreenOn = false (isRinging false, isDialing false, showingDisc false) D/InCallScreen( 167): updateScreen()... D/InCallScreen( 167): - updateScreen: updating the in-call UI... D/AndroidRuntime(29278): Shutting down VM W/dalvikvm(29278): threadid=1: thread exiting with uncaught exception (group=0x4001d7f0) D/AccelerometerListener( 167): orientation: vertical D/PhoneApp( 167): updateProximitySensorMode: acquiring... I/power ( 86): *** set_screen_state 0 D/InCallScreen( 167): onPause()... D/InCallScreen( 167): dismissAllDialogs()... D/PhoneApp( 167): re-enable status bar </code></pre> <p>i believe that this block is where the force-close is done but i have no idea why:</p> <pre><code>D/AndroidRuntime(29278): Shutting down VM W/dalvikvm(29278): threadid=1: thread exiting with uncaught exception (group=0x4001d7f0) </code></pre> <p>usually the next line is a stack-trace or something but in this case i get nothing.</p> <p>please help me. I thank you in advance.</p> <p>Edit: eventually i realized i had to view the whole logcat directly (i tried alogcat for this log) and i found the problem that was simply NUllPointerExceptions that were not caught. once i caught these exceptions and dealt with their creators - everything was fine.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USRoyi Benyossef
    1. USRoyi Benyossef
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POwidget force closes but logcat tells me nothing
      1. This table or related slice is empty.
      1. VTUndeletion
    2. VO
      singulars
      1. POwidget force closes but logcat tells me nothing
      1. USRoyi Benyossef
      1. VTFavorite
    1. COWhats this null here: D/Ringer ( 167): - stopRing: null mRingHandler!
      singulars
      1. POwidget force closes but logcat tells me nothing
      1. USBlundell
    2. COTo be honest i am not sure but as i pointed out i found the error in the end, but 10x for trying.
      singulars
      1. POwidget force closes but logcat tells me nothing
      1. USRoyi Benyossef
    3. COYou should asnwer your own question and mark it answered. Rather than editing it. Keeps your stats up.
      singulars
      1. POwidget force closes but logcat tells me nothing
      1. USBlundell
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload