riavvio improvviso s2

[kitomobile]

Riferendomi a chi ha il problema, riuscite a verificare se avete /system pieno?

[Matthew_]

Originariamente inviato da Matthew_
Ragazzi scusate ma non ho avuto modo di leggere tutto il 3d essendo abbastanza lungo..
volevo segnalare che è da 3 giorni che una volta al giorno mi si riavvia da solo..ho la 2.3.6 ufficiale aggiornata a metà gennaio e i permessi root ottenuti sempre intorno a quei giorni..com'è possibile che solo adesso riscontro questi problemi?


Inviato dal mio GT-I9100 usando Androidiani App

usa catlog che c'è nel market per localizzare l'errore che poi porta al crash del sistema.

L'ho scaricato e sta facendo la scansione..per me è arabo tutto quello che sta registrando..


Inviato dal mio GT-I9100 usando Androidiani App

[Matthew_]

Riferendomi a chi ha il problema, riuscite a verificare se avete /system pieno?

Dove lo vedo?


Inviato dal mio GT-I9100 usando Androidiani App

[kitomobile]

Prova con "Quick System Info", ha la voce relativa alla partizione system

[Darèios89]

Scusate ho avviato catlog e sta facendo la scansione, è una cosa lunga mi pare di capire vero? Spunta eventualmente un messaggio o qualcosa che mi fa capire che è quello che causa i riavvio?

Invece con Quick System vedo lo storage pieno, su 500 mega, è libero solo 1 mega....O_o...come libero lo spazio? Per me sarà quello il problema, come svuoto system kitomobile? Grazie.

[kitomobile]

per liberare spazio bisogna essere root, vai in /system/app e togli qualche app di sistema inutile come ad esempio gazzetta e corriere

[nemerov]

allora stamattina ho registrato con catlog...
Il mio lavoro al service di un'azienda che vende sistemi di telecontrollo, mi porta a debuggare dal mattino alla sera; ma in questo caso fatico ad interpretare i messaggi, a parte alcuni abbastanza evidenti...

Questo è stato raccolto prima di una riavvio...il log si è chiuso quando il cell si è riavviato....

02-14 10:22:06.715 V/webview (13776): singleCursorHandlerTouchEvent -getEditableSupport FASLE
02-14 10:22:07.325 V/traffic (11638): udpate traffic
02-14 10:22:07.330 D/NetTrafficLogic(11638): daoImpl 221: device_index: 0
02-14 10:22:07.330 D/NetTrafficLogic(11638): daoImpl 224: device_device: CELL [rmnet0, pdp0, ppp0, pdp_ip0, wimax0, vsnet0, ccinet0, ccmni0]

02-14 10:22:07.330 D/NetTrafficLogic(11638): daoImpl 226: device_r: 0

02-14 10:22:07.330 D/NetTrafficLogic(11638): daoImpl 227: device_t: 0

02-14 10:22:07.330 D/NetTrafficLogic(11638): daoImpl 174: LastTraffic: 0 : 0

02-14 10:22:07.550 D/NetTrafficLogic(11638): logic 152: 0 : 0

02-14 10:22:07.550 D/NetTrafficLogic(11638): logic 160: 0 : 0

02-14 10:22:07.550 D/NetTrafficLogic(11638): logic 173:[CELL[rmnet0, pdp0, ppp0, pdp_ip0, wimax0, vsnet0, ccinet0, ccmni0]: (0/0)]

02-14 10:22:08.214 W/PowerManagerService(10900): Timer 0x7->0x3|0x0

02-14 10:22:08.214 E/lights (10900): write_int: path /sys/devices/virtual/misc/melfas_touchkey/brightness, value 2

02-14 10:22:08.214 I/PowerManagerService(10900): Ulight 7->3|0

02-14 10:22:08.214 D/PowerManagerService(10900): setLightBrightness : mButtonLight : 0

02-14 10:22:09.815 I/InputReader(10900): dispatchTouch::touch event's action is 0, pending(waiting finished signal)=0

02-14 10:22:09.815 I/InputDispatcher(10900): Delivering touch to current input target: action: 0, channel '40934500 com.facebook.katana/com.facebook.katana.activity.faceweb.FacewebChrome Activity (server)'

02-14 10:22:09.820 E/lights (10900): write_int: path /sys/devices/virtual/misc/melfas_touchkey/brightness, value 1

02-14 10:22:09.820 I/PowerManagerService(10900): Ulight 3->7|0

02-14 10:22:09.820 D/PowerManagerService(10900): setLightBrightness : mButtonLight : 118

02-14 10:22:10.070 I/InputReader(10900): dispatchTouch::touch event's action is 1, pending(waiting finished signal)=0

02-14 10:22:10.070 I/InputDispatcher(10900): Delivering touch to current input target: action: 1, channel '40934500 com.facebook.katana/com.facebook.katana.activity.faceweb.FacewebChrome Activity (server)'

02-14 10:22:10.080 V/webview (13776): singleCursorHandlerTouchEvent -getEditableSupport FASLE

02-14 10:22:11.575 E/lights (10900): write_int: path /sys/devices/virtual/misc/melfas_touchkey/brightness, value 2

02-14 10:22:11.575 W/PowerManagerService(10900): Timer 0x7->0x3|0x0

02-14 10:22:11.575 I/PowerManagerService(10900): Ulight 7->3|0

02-14 10:22:11.575 D/PowerManagerService(10900): setLightBrightness : mButtonLight : 0

02-14 10:22:12.254 I/InputReader(10900): dispatchTouch::touch event's action is 0, pending(waiting finished signal)=0

02-14 10:22:12.254 I/InputDispatcher(10900): Delivering touch to current input target: action: 0, channel '40934500 com.facebook.katana/com.facebook.katana.activity.faceweb.FacewebChrome Activity (server)'
02-14 10:22:12.254 E/lights (10900): write_int: path /sys/devices/virtual/misc/melfas_touchkey/brightness, value 1

02-14 10:22:12.254 I/PowerManagerService(10900): Ulight 3->7|0

02-14 10:22:12.254 D/PowerManagerService(10900): setLightBrightness : mButtonLight : 118

02-14 10:22:12.405 D/dalvikvm(11279): GC_EXPLICIT freed 244K, 51% free 2733K/5511K, external 0K/0K, paused 57ms
02-14 10:22:12.480 I/InputReader(10900): dispatchTouch::touch event's action is 1, pending(waiting finished signal)=0

02-14 10:22:12.480 I/InputDispatcher(10900): Delivering touch to current input target: action: 1, channel '40934500 com.facebook.katana/com.facebook.katana.activity.faceweb.FacewebChrome Activity (server)'

02-14 10:22:12.480 V/webview (13776): singleCursorHandlerTouchEvent -getEditableSupport FASLE

02-14 10:22:12.990 F/<unknown>(10900): stack corruption detected: aborted
02-14 10:22:13.005 F//system/bin/tvoutserver( 9800): stack corruption detected: aborted

02-14 10:22:13.015 I/ServiceManager( 2579): service 'tvout' died

02-14 10:22:13.175 I/(14557): TvOutService daemon start!

02-14 10:22:13.200 I/ServiceManager( 2579): service 'permission' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'SurfaceFlinger' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'clipboardEx' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'sensorservice' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'entropy' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'power' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'batteryinfo' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'usagestats' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'telephony.registry' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'tvoutservice' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'uimode' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'usb' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'package' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'activity' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'meminfo' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'cpuinfo' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'audio' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'diskstats' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'appwidget' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'account' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'backup' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'AtCmdFwd' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'MhlRcp' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'Hdmi' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'motion_recognition' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'bt_fm_radio' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'FMPlayer' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'samsung.theme_service' died
02-14 10:22:13.200 I/ServiceManager( 2579): service 'content' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'battery' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'hardware' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'vibrator' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'alarm' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'window' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'bluetooth' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'bluetooth_a2dp' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'bluetooth_hid' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'application_policy' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'eas_account_policy' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'roaming_policy' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'misc_policy' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'device_policy' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'statusbar' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'clipboard' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'network_management' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'input_method' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'netstat' died
02-14 10:22:13.200 I/ServiceManager( 2579): service 'wifi' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'connectivity' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'throttle' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'accessibility' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'mount' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'usbstorage' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'encrypt' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'notification' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'datarouter' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'hdmi' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'devicestoragemonitor' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'location' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'search' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'dropbox' died

02-14 10:22:13.200 I/ServiceManager( 2579): service 'wallpaper' died

02-14 10:22:13.200 I/ActivityThread(13776): Removing dead content provider: settings

02-14 10:22:13.200 I/ActivityThread(11764): Removing dead content provider: settings

02-14 10:22:13.200 I/ActivityThread(11729): Removing dead content provider: settings

02-14 10:22:13.200 I/ActivityThread(11720): Removing dead content provider: settings

02-14 10:22:13.200 I/ActivityThread(11624): Removing dead content provider: settings

02-14 10:22:13.200 I/ActivityThread(11577): Removing dead content provider: settings

02-14 10:22:13.200 I/ActivityThread(11497): Removing dead content provider: settings

02-14 10:22:13.200 I/ActivityThread(11194): Removing dead content provider: settings

02-14 10:22:13.200 I/ActivityThread(11120): Removing dead content provider: settings

02-14 10:22:13.200 I/ActivityThread(11146): Removing dead content provider: settings

02-14 10:22:13.200 I/ActivityThread(11035): Removing dead content provider: settings

02-14 10:22:13.200 I/ActivityThread(11017): Removing dead content provider: settings

02-14 10:22:13.200 I/ActivityThread(11026): Removing dead content provider: settings

02-14 10:22:13.205 I/ActivityThread(11065): Removing dead content provider: settings

02-14 10:22:13.205 I/ActivityThread(11083): Removing dead content provider: settings

[Darèios89]

Ah ma quindi per usarlo dovrei avviare il programma per il log e lasciarlo avviato finchè non si riavvia? E poi se ti si spegne come fai ad avere il log salvato? Ricordo che c' è un opzione salva log....Sembrerebbe essere un problema con lo stack in system....

[nemerov]

Ah ma quindi per usarlo dovrei avviare il programma per il log e lasciarlo avviato finchè non si riavvia? E poi se ti si spegne come fai ad avere il log salvato? Ricordo che c' è un opzione salva log....Sembrerebbe essere un problema con lo stack in system....

guarda aggiungi l'widget sulla home e quando clicchi inizia a registrare ( avrai un pallino rosso sullo stesso e il simbolo sulla barra in alto ); lui registra, quando si riavvia come si vede nel mio log si chiudono tutte le applicazioni; quando si riaccende troverai il file .txt nella cartella che ha creato...l'applicativo scrive fino a che è "vivo"...il file txt sono comodi in tal senso....ora sta a riuscire a capire cosa provoca i crash....

[menonino]

fai una prova freezando il tvoutserver con titanium backup.