I am on 3.4.3-11 and the phone is pretty good, but sometimes when i starts google maps, the phone becomes unresponsive sometimes i can close it, but sometimes it reboots the phone. Does anyone has a solution for that? As i remember i dont had the problem on eclair?
Root your phone, delete/rename the maps.apk that is in system/app/ folder and download a new one from the market.
It is already rooted so i will try it. I experienced it with other versions of froyo. The maps is already updated, should i uninstall the updates before deleting the apk? I will write back but it usually takes a half day before producing the slowdown and freezing. Did you experienced the issue and deleting the apk and installing a new one from the market solved it?
vick33 said:
It is already rooted so i will try it. I experienced it with other versions of froyo. The maps is already updated, should i uninstall the updates before deleting the apk? I will write back but it usually takes a half day before producing the slowdown and freezing. Did you experienced the issue and deleting the apk and installing a new one from the market solved it?
Click to expand...
Click to collapse
In my case starting maps resulted in extremely slow performance, so I uninstalled the updates through market and renamed the apk with root explorer. After that I installed maps through market and now everything is working perfect. I have had the same maps problem on all the froyo versions.
It was the same for me. Somtimes i can close the maps, but sometimes i had to remove the battery or the phone rebooted itself. I will write back if the problem occures again, but either way thanks for your help!
What connection are you using? Slow connection can often freeze connection based applications, but not cause reboot though.
Deleting and reinstalling the maps application did not help. It was good for 8 hours, but after it the slowdowns appeared again. The CPU usage was not high at all, but the io wait was. This is what top prints out:
Code:
$ $top -n 1
User 12%, System 22%, IOW 65%, IRQ 0%
User 16 + Nice 23 + Sys 73 + Idle 0 + IOW 211 + IRQ 0 + SIRQ 0 = 323
PID CPU% S #THR VSS RSS PCY UID Name
10962 10% S 23 194340K 24660K bg app_58 com.google.android.gm
1388 4% S 70 336836K 61732K fg system system_server
671 4% S 1 0K 0K fg root mmcqd
10713 4% S 11 162220K 13992K bg app_24 com.motorola.blur.home.newsstatus
11049 3% R 1 856K 392K fg app_93 top
353 3% D 1 0K 0K fg root kswapd0
1119 2% S 1 0K 0K fg root kjournald
1608 1% S 29 190900K 13588K bg app_39 com.google.process.gapps
9937 0% S 14 174704K 19816K bg app_113 com.rechild.advancedtaskkiller
1453 0% S 1 1992K 320K fg wifi /system/bin/wpa_supplicant
1259 0% S 1 6068K 1824K fg root /system/bin/vpnclientpm
203 0% S 1 0K 0K fg root kblockd/0
219 0% S 1 0K 0K fg root cpcap_irq/0
279 0% S 1 0K 0K fg root ksuspend_usbd
284 0% S 1 0K 0K fg root khubd
311 0% S 1 0K 0K fg root kmmcd
318 0% S 1 0K 0K fg root bluetooth
352 0% S 1 0K 0K fg root khungtaskd
355 0% S 1 0K 0K fg root aio/0
356 0% S 1 0K 0K fg root ecryptfs-kthrea
358 0% S 1 0K 0K fg root crypto/0
457 0% S 1 0K 0K fg root kxtf9_wq
497 0% S 1 0K 0K fg root mtdblockd
521 0% S 1 0K 0K fg root klink_driver_wq
539 0% S 1 0K 0K fg root usb_mass_storag
547 0% S 1 0K 0K fg root qtouch_obp_ts_w
556 0% S 1 0K 0K fg root bu52014hfv_wq
562 0% S 1 0K 0K fg root als_wq
594 0% S 1 0K 0K fg root bridge_work-que
595 0% S 1 0K 0K fg root bridge_recovery
601 0% S 1 0K 0K fg root w1_bus_master1
610 0% S 1 0K 0K fg root kstriped
612 0% S 1 0K 0K fg root kondemand/0
632 0% S 1 0K 0K fg root als_wq
646 0% S 1 0K 0K fg root usbhid_resumer
649 0% S 1 0K 0K fg root binder
666 0% S 1 0K 0K fg root krfcommd
668 0% S 1 0K 0K fg root dsi
703 0% S 1 0K 0K fg root mmcqd
725 0% S 1 0K 0K fg root pvrflip/0
730 0% S 1 0K 0K fg root ksuspend_usb_ip
731 0% S 1 0K 0K fg root kipcd
1109 0% S 1 0K 0K fg root kjournald
1129 0% S 1 0K 0K fg root kjournald
1132 0% S 1 0K 0K fg root flush-179:32
1143 0% S 1 0K 0K fg root kjournald
1 0% S 1 300K 252K fg root /init
1161 0% S 1 0K 0K fg root gannet
1173 0% S 1 0K 0K fg root smodule
1180 0% S 1 832K 84K fg root /system/bin/smoduled
1222 0% S 4 3312K 152K fg shell /sbin/adbd
1223 0% S 1 1036K 80K fg root /system/bin/ecckeyd
1225 0% S 1 716K 68K fg system /system/bin/servicemanager
1226 0% S 3 3648K 132K fg root /system/bin/vold
1227 0% S 3 3644K 128K fg root /system/bin/netd
1228 0% S 1 576K 48K fg root /system/bin/debuggerd
1231 0% S 8 18508K 436K fg radio /system/bin/rild
1233 0% S 1 788K 84K fg root /system/bin/usbd
1234 0% S 1 716K 76K fg radio /system/usr/bin/nvm_daemon
1237 0% S 7 7172K 140K fg radio /system/bin/gkisystem
1238 0% S 3 3312K 132K fg radio /system/bin/rild_tcmd
1239 0% S 1 1248K 128K fg mot_accy /system/bin/battd
1242 0% S 1 114524K 8804K fg root zygote
1243 0% S 9 35280K 1776K fg media /system/bin/mediaserver
1244 0% S 1 1176K 84K fg bluetoot /system/bin/dbus-daemon
1245 0% S 1 776K 128K fg root /system/bin/installd
1247 0% S 1 1528K 72K fg keystore /system/bin/keystore
1248 0% S 1 736K 80K fg radio /system/xbin/ssmgrd
1250 0% S 2 14220K 416K fg mot_tcmd /system/bin/tcmd
1251 0% S 1 1256K 128K fg radio /system/usr/bin/panic_daemon
1252 0% S 1 196K 36K fg compass /system/bin/akmd2
1254 0% S 2 3304K 284K fg radio /system/usr/bin/brcm_guci_drv
1256 0% S 1 1088K 112K fg mot_tpap /system/bin/secclkd
1260 0% S 1 584K 60K fg nobody /system/bin/RescueStarter
1261 0% S 7 17296K 536K fg radio protocol_driver
1262 0% S 9 10308K 256K fg radio location
1263 0% S 4 4172K 104K fg radio opprofdaemon
1283 0% S 1 660K 72K fg bluetoot /system/bin/hciattach
1427 0% S 1 0K 0K fg root sdio_wq
1429 0% S 1 0K 0K fg root tiwlan_wq
1450 0% S 12 166968K 14436K fg app_14 com.motorola.blur.providers.contacts
1471 0% S 10 176212K 18296K fg app_13 com.android.inputmethod.latin
1476 0% S 26 191948K 15844K fg radio com.android.phone
1479 0% S 35 235820K 17688K fg app_14 com.motorola.blur.service.main
1480 0% S 21 172160K 15792K fg app_26 com.motorola.blur.service.blur
1487 0% S 12 220628K 25304K fg app_24 com.motorola.blur.home
1491 0% S 6 150316K 9060K fg system com.motorola.atcmd
1493 0% S 7 152692K 11392K fg app_20 com.motorola.batterymanager
1506 0% S 7 159528K 11216K fg app_30 com.nuance.android.vsuite.vsuiteapp
1534 0% S 6 150388K 9184K fg system com.motorola.inpocket
1535 0% S 7 160144K 15524K fg app_72 com.motorola.PerformanceManager
1537 0% S 8 152736K 9740K fg app_78 com.motorola.usb
1664 0% S 7 155140K 10944K fg app_73 android.tts
1815 0% S 1 0K 0K fg root loop0
1819 0% S 1 0K 0K fg root kdmflush
1831 0% S 1 0K 0K fg root kcryptd_io
1832 0% S 1 0K 0K fg root kcryptd
2052 0% S 1 0K 0K fg root loop1
2055 0% S 1 0K 0K fg root kdmflush
2056 0% S 1 0K 0K fg root kcryptd_io
2057 0% S 1 0K 0K fg root kcryptd
2125 0% S 1 0K 0K fg root loop2
2128 0% S 1 0K 0K fg root kdmflush
2129 0% S 1 0K 0K fg root kcryptd_io
2130 0% S 1 0K 0K fg root kcryptd
2151 0% S 1 0K 0K fg root loop3
2154 0% S 1 0K 0K fg root kdmflush
2155 0% S 1 0K 0K fg root kcryptd_io
2156 0% S 1 0K 0K fg root kcryptd
7904 0% S 6 150648K 9140K bg app_50 com.svox.pico
8443 0% S 1 760K 92K fg dhcp /system/bin/dhcpcd
8998 0% S 6 150540K 9136K bg app_34 com.android.defcontainer
9006 0% S 6 152416K 9356K bg app_115 com.menny.android.anysoftkeyboard
9412 0% S 9 173572K 16776K bg system com.android.settings
9703 0% S 6 156128K 9772K bg app_3 com.android.calendar
9732 0% S 8 153824K 10720K bg app_4 android.process.media
9758 0% S 6 150564K 9140K bg app_18 com.motorola.btlowbattery
9839 0% S 6 155300K 9528K bg app_14 com.motorola.blur.contacts.data
10136 0% S 6 150872K 9600K bg app_53 com.motorola.android.datamanager
10143 0% S 7 151952K 9416K bg system com.motorola.process.system
10158 0% S 6 150932K 9388K bg app_41 com.motorola.nabsync
10183 0% S 6 150544K 9112K bg app_92 com.motorola.globalunplug
10191 0% S 6 151700K 9588K bg app_17 com.motorola.android.syncml.service
10650 0% S 12 174768K 11448K bg app_140 com.google.android.apps.maps:NetworkLocationService
10665 0% S 7 153296K 9552K bg app_105 net.rgruet.android.g3watchdog
10673 0% S 6 153700K 9236K bg app_24 com.motorola.togglewidgets
10679 0% S 9 159908K 10400K bg app_24 com.motorola.blur.friendfeed
10689 0% S 8 165296K 9964K bg app_24 com.motorola.blur.contacts
10699 0% S 10 172128K 10496K bg app_24 com.motorola.blur.weather
10706 0% S 9 191972K 10780K bg app_24 com.motorola.blur.quickcontact
10720 0% S 6 158148K 9684K bg app_24 com.motorola.blur.home.other
10727 0% S 7 156504K 9632K bg app_24 com.motorola.blur.home.message
10734 0% S 6 160932K 10504K bg app_116 com.maxmpz.audioplayer
10743 0% S 9 156112K 13168K fg app_93 jackpal.androidterm
10758 0% S 7 152504K 9448K bg app_101 com.noshufou.android.su
11022 0% S 1 648K 156K fg app_93 /system/bin/sh
1160 0% S 1 0K 0K fg root gannet_queue/0
2 0% S 1 0K 0K fg root kthreadd
3 0% S 1 0K 0K fg root ksoftirqd/0
4 0% S 1 0K 0K fg root watchdog/0
5 0% S 1 0K 0K fg root events/0
6 0% S 1 0K 0K fg root khelper
9 0% S 1 0K 0K fg root async/mgr
12 0% S 1 0K 0K fg root suspend
199 0% S 1 0K 0K fg root sync_supers
201 0% S 1 0K 0K fg root bdi-default
207 0% S 1 0K 0K fg root omap_serial
215 0% S 1 0K 0K fg root omap2_mcspi
So the case is someting polling the IO so fast that even system processes starve. Then i tried to get what are the exact processes using so much io. under linux i can do that, and no wonder it works under android too:
echo 1 > /proc/sys/vm/block_dump ; cat /proc/kmsg ; echo 0 > /proc/sys/vm/block_dump
During normal opareation kjournald, and flush-179:32 are the only processes using io wrting logs to mmcblk1p25, but when the phone starts to lag a couple process starts to read mmcblk1p21(the sytem) like hell. This is just a short example:
Code:
<7>[46906.785827] er.ServerThread(1396): READ block 33756 on mmcblk1p21 (8 sectors)
<7>[46906.786437] er.ServerThread(1396): READ block 33804 on mmcblk1p21 (8 sectors)
<7>[46906.786773] er.ServerThread(1396): READ block 33820 on mmcblk1p21 (56 sectors)
<7>[46906.787445] pal.androidterm(10743): READ block 33540 on mmcblk1p21 (8 sectors)
<7>[46906.787994] pal.androidterm(10743): READ block 33588 on mmcblk1p21 (64 sectors)
<7>[46906.803344] pal.androidterm(10743): READ block 591296 on mmcblk1p21 (40 sectors)
<7>[46906.804077] pal.androidterm(10743): READ block 591344 on mmcblk1p21 (8 sectors)
<7>[46906.804626] pal.androidterm(10743): READ block 591360 on mmcblk1p21 (16 sectors)
<7>[46906.804962] pal.androidterm(10743): READ block 591416 on mmcblk1p21 (16 sectors)
<7>[46906.818817] Binder Thread #(1556): READ block 606582 on mmcblk1p21 (16 sectors)
<7>[46906.819244] Binder Thread #(1556): READ block 606614 on mmcblk1p21 (32 sectors)
<7>[46906.819824] Binder Thread #(1556): READ block 606686 on mmcblk1p21 (136 sectors)
<7>[46906.820404] Binder Thread #(1556): READ block 606822 on mmcblk1p21 (2 sectors)
<7>[46906.828674] ConnectivityThr(1416): READ block 215246 on mmcblk1p21 (32 sectors)
<7>[46906.829254] ConnectivityThr(1416): READ block 215286 on mmcblk1p21 (40 sectors)
<7>[46906.829803] ConnectivityThr(1416): READ block 215334 on mmcblk1p21 (64 sectors)
<7>[46906.830139] ConnectivityThr(1416): READ block 215406 on mmcblk1p21 (16 sectors)
<7>[46906.830657] ConnectivityThr(1416): READ block 215430 on mmcblk1p21 (8 sectors)
<7>[46906.831207] ConnectivityThr(1416): READ block 215478 on mmcblk1p21 (24 sectors)
<7>[46906.840393] Binder Thread #(1556): READ block 606826 on mmcblk1p21 (8 sectors)
<7>[46906.853302] WebViewCoreThre(9943): READ block 285914 on mmcblk1p21 (136 sectors)
<7>[46906.862487] WebViewCoreThre(9943): READ block 285698 on mmcblk1p21 (8 sectors)
<7>[46906.881317] Binder Thread #(1556): READ block 214730 on mmcblk1p21 (8 sectors)
<7>[46906.881927] Binder Thread #(1556): READ block 214746 on mmcblk1p21 (24 sectors)
<7>[46906.882446] Binder Thread #(1556): READ block 214866 on mmcblk1p21 (8 sectors)
<7>[46906.887115] ConnectivityThr(1416): READ block 582618 on mmcblk1p21 (216 sectors)
<7>[46906.887695] ConnectivityThr(1416): READ block 582836 on mmcblk1p21 (40 sectors)
<7>[46906.907348] ConnectivityThr(1416): READ block 16492 on mmcblk1p21 (24 sectors)
<7>[46906.907989] ConnectivityThr(1416): READ block 16518 on mmcblk1p21 (50 sectors)
<7>[46906.923339] ConnectivityThr(1416): READ block 314154 on mmcblk1p21 (32 sectors)
<7>[46906.923950] ConnectivityThr(1416): READ block 314210 on mmcblk1p21 (200 sectors)
<7>[46906.938934] ConnectivityThr(1416): READ block 557382 on mmcblk1p21 (12 sectors)
<7>[46906.943695] WebViewCoreThre(9943): READ block 286404 on mmcblk1p21 (160 sectors)
<7>[46906.954528] WebViewCoreThre(9943): READ block 284516 on mmcblk1p21 (8 sectors)
<7>[46906.955291] WebViewCoreThre(9943): READ block 284526 on mmcblk1p21 (192 sectors)
<7>[46906.971923] WebViewCoreThre(9943): READ block 288636 on mmcblk1p21 (2 sectors)
<7>[46906.977264] ConnectivityThr(1416): READ block 557374 on mmcblk1p21 (8 sectors)
<7>[46906.983459] wpa_supplicant(1453): READ block 22688 on mmcblk1p21 (24 sectors)
<7>[46906.984161] wpa_supplicant(1453): READ block 22714 on mmcblk1p21 (232 sectors)
<7>[46906.996124] Binder Thread #(1556): READ block 313806 on mmcblk1p21 (80 sectors)
<7>[46906.996704] Binder Thread #(1556): READ block 313894 on mmcblk1p21 (32 sectors)
<7>[46907.009613] Binder Thread #(1556): READ block 582884 on mmcblk1p21 (256 sectors)
<7>[46907.022583] Binder Thread #(1556): READ block 109822 on mmcblk1p21 (168 sectors)
<7>[46907.031280] Binder Thread #(1556): READ block 583880 on mmcblk1p21 (232 sectors)
<7>[46907.044342] Binder Thread #(1556): READ block 591336 on mmcblk1p21 (8 sectors)
<7>[46907.044799] Binder Thread #(1556): READ block 591352 on mmcblk1p21 (8 sectors)
<7>[46907.045318] Binder Thread #(1556): READ block 591376 on mmcblk1p21 (8 sectors)
<7>[46907.045654] Binder Thread #(1556): READ block 591432 on mmcblk1p21 (48 sectors)
<7>[46907.046234] Binder Thread #(1556): READ block 591488 on mmcblk1p21 (52 sectors)
<7>[46907.059722] Binder Thread #(1556): READ block 215502 on mmcblk1p21 (72 sectors)
<7>[46907.060150] Binder Thread #(1556): READ block 215576 on mmcblk1p21 (40 sectors)
<7>[46907.066314] Binder Thread #(1556): READ block 606430 on mmcblk1p21 (8 sectors)
<7>[46907.066925] Binder Thread #(1556): READ block 606494 on mmcblk1p21 (88 sectors)
<7>[46907.067260] Binder Thread #(1556): READ block 606646 on mmcblk1p21 (40 sectors)
<7>[46907.083068] pal.androidterm(10743): READ block 606422 on mmcblk1p21 (8 sectors)
<7>[46907.084655] WebViewCoreThre(9943): READ block 288894 on mmcblk1p21 (256 sectors)
<7>[46907.098815] WebViewCoreThre(9943): READ block 280340 on mmcblk1p21 (72 sectors)
<7>[46907.099639] WebViewCoreThre(9943): READ block 280414 on mmcblk1p21 (56 sectors)
<7>[46907.105194] WebViewCoreThre(9943): READ block 283472 on mmcblk1p21 (24 sectors)
<7>[46907.113708] WebViewCoreThre(9943): READ block 280566 on mmcblk1p21 (16 sectors)
<7>[46907.114410] WebViewCoreThre(9943): READ block 280814 on mmcblk1p21 (88 sectors)
<7>[46907.119415] WebViewCoreThre(9943): READ block 280470 on mmcblk1p21 (88 sectors)
<7>[46907.132141] WebViewCoreThre(9943): READ block 283048 on mmcblk1p21 (168 sectors)
<7>[46907.140594] WebViewCoreThre(9943): READ block 623044 on mmcblk1p21 (12 sectors)
<7>[46907.149017] WebViewCoreThre(9943): READ block 282172 on mmcblk1p21
after i restart the phone i cannot get the error for at least 8 hours. It has to be something with the data connections but i can get the problem on wifi and on 3g too... So i am clueless Anyone has any idea?
I have the same problem. Reinstall the app didn't help.
Related
Just thought i would post a dump of my TOP command, might help with trying to see what is running from a native command line point of view:
User 10%, System 3%, IOW 4%, IRQ 0%
User 35 + Nice 0 + Sys 12 + Idle 279 + IOW 14 + IRQ 0 + SIRQ 0 = 340
PID CPU% S #THR VSS RSS PCY UID Name
194 4% S 10 43520K 10980K fg media /system/bin/mediaserver
450 2% S 8 720632K 30656K fg system com.android.systemui
1286 2% R 1 1032K 436K fg root top
312 1% S 66 810236K 60492K fg system system_server
102 0% S 1 0K 0K fg root kondemand/0
1 0% S 1 744K 412K fg root /init
718 0% S 4 4184K 480K fg root /system/bin/mpdecision
474 0% S 19 652204K 29196K fg radio com.android.phone
12 0% S 1 0K 0K fg root suspend_sys_syn
13 0% S 1 0K 0K fg root suspend
14 0% S 1 0K 0K fg root irq/344-pm8058-
15 0% S 1 0K 0K fg root irq/347-pm8901-
16 0% S 1 0K 0K fg root sync_supers
17 0% S 1 0K 0K fg root bdi-default
18 0% S 1 0K 0K fg root kblockd/0
20 0% S 1 0K 0K fg root khubd
21 0% S 1 0K 0K fg root kseriod
22 0% S 1 0K 0K fg root kmmcd
23 0% S 1 0K 0K fg root rpciod/0
25 0% S 1 0K 0K fg root modem_notifier
26 0% S 1 0K 0K fg root smd_channel_clo
27 0% S 1 0K 0K fg root rpcrouter
28 0% S 1 0K 0K fg root apr_driver
29 0% S 1 0K 0K fg root rmt_storage
30 0% S 1 0K 0K fg root charm_queue
31 0% S 1 0K 0K fg root irq/390-charm s
32 0% S 1 0K 0K fg root k3dh_hr_wq
33 0% S 1 0K 0K fg root k3g_wq
34 0% S 1 0K 0K fg root proximity_als/0
36 0% S 1 0K 0K fg root synaptics_wq
37 0% S 1 0K 0K fg root irq/317-synapti
38 0% S 1 0K 0K fg root did_dload_wq
39 0% S 1 0K 0K fg root kswapd0
40 0% S 1 0K 0K fg root aio/0
42 0% S 1 0K 0K fg root nfsiod
43 0% S 1 0K 0K fg root kslowd000
44 0% S 1 0K 0K fg root kslowd001
45 0% S 1 0K 0K fg root crypto/0
63 0% S 1 0K 0K fg root mdp_dma_wq
64 0% S 1 0K 0K fg root mdp_vsync_wq
65 0% S 1 0K 0K fg root mdp_pipe_ctrl_w
66 0% S 1 0K 0K fg root mdp_cursor_ctrl
67 0% S 1 0K 0K fg root hdmi_hdcp/0
69 0% S 1 0K 0K fg root irq/111-hdmi_ms
70 0% S 1 0K 0K fg root vidc_worker_que
71 0% S 1 0K 0K fg root vidc_timer_wq
72 0% S 1 0K 0K fg root kgsl-3d0/0
74 0% S 1 0K 0K fg root kgsl-2d0/0
76 0% S 1 0K 0K fg root kgsl-2d1/0
78 0% S 1 0K 0K fg root scsi_tgtd/0
87 0% S 1 0K 0K fg root k_otg
88 0% S 1 0K 0K fg root k_gserial
89 0% S 1 0K 0K fg root k_gserial
90 0% S 1 0K 0K fg root file-storage
91 0% S 1 0K 0K fg root diag_wq
92 0% S 1 0K 0K fg root diag_sdio_wq
93 0% S 1 0K 0K fg root kthread_lg_diag
94 0% S 1 0K 0K fg root kpsmoused
95 0% S 1 0K 0K fg root max17040_fuel_g
97 0% S 1 0K 0K fg root msm_charger_eve
99 0% S 1 0K 0K fg root msm_adc
100 0% S 1 0K 0K fg root irq/210-tsens
101 0% S 1 0K 0K fg root kstriped
104 0% S 1 0K 0K fg root kconservative/0
106 0% S 1 0K 0K fg root irq/290-msm-sdc
107 0% S 1 0K 0K fg root binder
108 0% S 1 0K 0K fg root l2cap
109 0% S 1 0K 0K fg root a2mp
110 0% S 1 0K 0K fg root krfcommd
111 0% S 1 0K 0K fg root msm-cpufreq/0
113 0% S 1 0K 0K fg root rq_stats
114 0% S 1 0K 0K fg root mhl_sii9244_wq
115 0% S 1 0K 0K fg root irq/286-mhl_int
116 0% S 1 0K 0K fg root fsa8008/0
118 0% S 1 0K 0K fg root lge_isa1200/0
120 0% S 1 652K 172K fg root /sbin/ueventd
121 0% S 1 0K 0K fg root mmcqd
122 0% S 1 0K 0K fg root mmcqd
124 0% S 1 0K 0K fg root jbd2/mmcblk0p27
125 0% S 1 0K 0K fg root ext4-dio-unwrit
127 0% S 1 0K 0K fg root jbd2/mmcblk0p22
128 0% S 1 0K 0K fg root ext4-dio-unwrit
162 0% S 1 0K 0K fg root jbd2/mmcblk0p30
163 0% S 1 0K 0K fg root ext4-dio-unwrit
166 0% S 1 0K 0K fg root jbd2/mmcblk0p12
167 0% S 1 0K 0K fg root ext4-dio-unwrit
170 0% S 1 0K 0K fg root jbd2/mmcblk0p28
171 0% S 1 0K 0K fg root ext4-dio-unwrit
174 0% S 1 0K 0K fg root jbd2/mmcblk0p31
175 0% S 1 0K 0K fg root ext4-dio-unwrit
177 0% S 1 0K 0K fg root jbd2/mmcblk0p23
178 0% S 1 0K 0K fg root ext4-dio-unwrit
188 0% S 1 868K 276K fg system /system/bin/servicemanager
189 0% S 3 3920K 628K fg root /system/bin/vold
190 0% S 3 3924K 588K fg root /system/bin/netd
191 0% S 1 732K 268K fg root /system/bin/debuggerd
192 0% S 2 8196K 1596K fg lgdrm /system/bin/lgdrmserver
193 0% S 1 611240K 33416K fg root zygote
196 0% S 1 1308K 704K fg bluetoot /system/bin/dbus-daemon
197 0% S 1 868K 316K fg root /system/bin/installd
198 0% S 1 1800K 436K fg keystore /system/bin/keystore
199 0% S 1 880K 268K fg system /system/bin/atd
205 0% S 1 1128K 436K fg compass /system/bin/ami304d
207 0% S 1 860K 300K fg root /system/bin/qrngd
219 0% S 7 14276K 2728K fg radio /system/bin/rild
220 0% S 11 11596K 640K fg radio /system/bin/qmuxd
221 0% S 5 5532K 788K fg root /system/bin/netmgrd
222 0% S 5 5632K 864K fg radio /system/bin/qmiproxy
223 0% S 4 3428K 180K fg shell /sbin/adbd
224 0% S 4 7000K 324K fg nobody /system/bin/rmt_storage
231 0% S 4 10932K 1628K fg system /system/bin/hdmid
232 0% S 6 8312K 1164K fg system /system/bin/time_daemon
248 0% S 1 0K 0K fg root flush-179:0
282 0% S 1 1112K 444K fg system /system/bin/qcks
293 0% D 1 0K 0K fg root rpcrotuer_smd_x
294 0% S 1 0K 0K fg root krpcserversd
295 0% D 1 0K 0K fg root krmt_storagecln
300 0% D 1 0K 0K fg root krmt_storagecln
307 0% D 1 0K 0K fg root sdio_al_wq
308 0% D 1 0K 0K fg root sdio_al_wq
342 0% S 1 0K 0K fg root ksdioirqd/mmc4
343 0% S 1 0K 0K fg root sdio_xprt
344 0% S 1 0K 0K fg root sdio_cmux
345 0% D 1 0K 0K fg root rpcrotuer_sdio_
346 0% S 1 0K 0K fg root sdio_cdemux
347 0% S 1 0K 0K fg root ksdioirqd/mmc1
348 0% S 1 0K 0K fg root sdio_dmux
350 0% D 1 0K 0K fg root krmt_storagecln
351 0% D 1 0K 0K fg root krmt_storagecln
352 0% S 1 0K 0K fg root sdio_debug_ch_w
407 0% S 3 8308K 1144K fg system /system/bin/ATFWD-daemon
461 0% S 11 627660K 27072K bg app_94 com.yahoo.mobile.client.android.mail
469 0% S 11 632156K 26772K fg app_46 com.android.inputmethod.latin
475 0% S 10 632864K 25796K fg app_34 com.nuance.android.vsuite.lg_p930
478 0% S 7 621380K 21168K fg lg_fota com.lge.omadmclient
481 0% S 8 622048K 23096K fg app_61 com.jungle.app.fonts
485 0% S 7 620648K 20392K fg bluetoot com.broadcom.bt.app.system
526 0% S 9 638252K 23172K fg app_38 com.android.music
536 0% S 8 622396K 21708K bg app_72 com.android.providers.calendar
550 0% S 25 668692K 35564K fg app_36 com.google.process.gapps
551 0% S 9 658388K 23948K bg app_41 android.process.media
573 0% S 10 661444K 41532K bg app_12 android.process.acore
634 0% S 8 625924K 23052K bg app_104 com.facebook.katana
682 0% S 8 650856K 29124K bg app_50 com.lge.email
719 0% S 10 12416K 1164K fg root /system/bin/thermald
734 0% D 1 0K 0K fg root koemrapiclientc
751 0% S 8 624080K 23188K bg app_58 com.google.android.gm
792 0% S 1 0K 0K fg root flush-179:32
796 0% S 7 621192K 22588K fg app_99 com.lge.clockweatherschedulewidget
818 0% S 8 623500K 20528K bg system com.android.settings
829 0% S 9 683276K 39352K fg app_90 android.process.acore
834 0% S 8 670692K 23572K bg app_39 com.android.mms
868 0% S 1 0K 0K fg root loop0
869 0% S 1 0K 0K fg root kdmflush
881 0% S 1 0K 0K fg root kcryptd_io
882 0% S 1 0K 0K fg root kcryptd
887 0% S 1 0K 0K fg root loop1
888 0% S 1 0K 0K fg root kdmflush
889 0% S 1 0K 0K fg root kcryptd_io
890 0% S 1 0K 0K fg root kcryptd
933 0% S 7 621784K 20020K bg app_18 com.quoord.tapatalkxda.activity
940 0% S 7 620976K 19600K bg app_5 com.qualcomm.wiper
948 0% S 7 620608K 18896K bg system com.qualcomm.privinit
964 0% S 7 621788K 20920K bg app_112 com.lge.app.richnote
982 0% S 7 622452K 21948K bg app_69 com.pelmorex.WeatherEyeAndroid
996 0% S 9 628084K 22452K bg lg_fota com.lge.omadmclient:remote
997 0% S 7 621576K 19512K bg app_48 com.lge.osp
1011 0% S 7 621996K 20520K bg system com.lge.hiddenmenu
1028 0% S 9 631272K 21944K bg app_56 com.google.android.partnersetup
1044 0% S 8 621776K 20352K bg app_65 com.lge.drmservice
1091 0% S 7 620780K 18836K bg lg_fota com.lge.Dracula
1099 0% S 7 621820K 19504K bg app_78 com.rsupport.rs.activity.lge
1107 0% S 7 621444K 21716K bg app_83 com.lge.clock
1114 0% S 8 629272K 24848K bg app_96 com.netqin.aotkiller
1121 0% S 8 624992K 23612K bg app_17 com.keramidas.TitaniumBackup
1131 0% S 7 631116K 23200K bg app_43 com.google.android.apps.maps:FriendService
1139 0% S 17 649908K 28372K bg app_43 com.google.android.apps.maps:NetworkLocationService
1154 0% S 8 625564K 27120K bg app_19 com.skype.raider
1174 0% S 7 623852K 21608K bg app_0 com.noshufou.android.su
1183 0% S 7 622236K 22920K bg app_85 com.mediawoz.goweather
1191 0% S 11 663228K 24768K bg app_85 com.mediawoz.goweather:remote
1232 0% S 1 796K 336K fg shell /system/bin/sh
1235 0% S 1 796K 336K fg root sh
1265 0% S 7 620936K 19360K bg app_63 com.antutu.CpuMasterFree
1272 0% S 1 796K 336K fg root sh
1285 0% S 1 796K 336K fg root sh
1318 0% S 8 626140K 20564K bg app_71 com.lge.sizechangable.calendar
1020 0% S 7 620772K 20172K fg system com.lge.providers.packageconfig
2 0% S 1 0K 0K fg root kthreadd
3 0% S 1 0K 0K fg root ksoftirqd/0
4 0% S 1 0K 0K fg root migration/0
7 0% S 1 0K 0K fg root events/0
9 0% S 1 0K 0K fg root khelper
10 0% S 1 0K 0K fg root async/mgr
11 0% S 1 0K 0K fg root pm
Okay so i have been looking all over the forums for help with my issue for the last like 6 hours and i have found stuff that is relevant but i have a weird twist.
I was installing google voice on the latest miui build for the t-mobile G2 and the device froze soo I restarted it causing this nightmare to begin.
I can not get back into android the phone freezes on the HTC screen, however i can get into fastboot which I can then use to get into clockworkmod recovery. At that point however I run into a problem, clockworkmod recovery can't mount anything including my SD card. I tried reformatting the card in clockworkmod and outside of it and no go. My device is S-OFF and when its in fastboot i can connect it to my computer and execute fastboot commands but i don't have a nandroid backup to recover the img files from for a manual reinstall from fastboot.
Any information i can give you to help i will try to get and if i am confused about something please correct me I am kinda new to all of this so I could very easily be confused about something.
[Solution]
Yay I fixed it! Well kinda... I figured out a work around for the emmc problem using an SD card to take its place.
Okay so the break down of the problem was that my phone would not boot into android but i still had clockworkmod and fast boot. When I went into clockworkmod I got the cache errors and it couldnt mount anything including my SD card. If i adb into the device from clockworkmod and typed:
cd ls /dev/block/
i got this if i didnt have an sdcard
loop0 loop2 loop4 loop6 platform
loop1 loop3 loop5 loop7
and when i did have one in i got this
loop0 loop2 loop4 loop6 mmcblk0 platform
loop1 loop3 loop5 loop7 mmcblk0p1
~ # cat /proc/kmsg | grep mmc0
came up with this
<3>[ 4.155456] mmc0: No card detect facilities available
<6>[ 4.156005] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 4.156280] mmc0: Platform slot type: MMC
<6>[ 4.156402] mmc0: 4 bit data mode disabled
<6>[ 4.156646] mmc0: 8 bit data mode enabled
<6>[ 4.156799] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 4.157043] mmc0: Slot eject status = 0
<6>[ 4.157165] mmc0: Power save feature enable = 1
<6>[ 4.157318] mmc0: DM non-cached buffer at ffa0c000, dma_addr 0x2ae95000
<6>[ 4.157562] mmc0: DM cmd busaddr 0x2ae95000, cmdptr busaddr 0x2ae95300
<3>[ 4.279235] mmc0: error -110 whilst initialising MMC card
and i was basically told that the eMMC went was busted and i was screwed but then i found this: http://tjworld.net/wiki/Android/HTC/Vision/LinuxAnalysis
Its basically a break down of the partition tables of the eMMC and when i saw that the block name for the eMMC was the same as what my SD card was showing up as in the /dev/block directory i decided to attempt to recreate the partition table for the eMMC on my SD card and see if i could use it as a eMMC replacement
So i went back into the device with adb typed 'fdisk /dev/block/mmcblk0' deleted the current partition and started to recreate the partition tables on my sd card exactly like they were on the eMMC. My SDCard partition table looks like this:
Disk /dev/block/mmcblk0: 7948 MB, 7948206080 bytes
4 heads, 16 sectors/track, 242560 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Code:
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 16 500 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 16 18 64 45 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 18 159 4500 46 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 159 242560 7756840+ 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 159 1097 30000 49 Unknown
/dev/block/mmcblk0p6 1097 1487 12500 50 Unknown
/dev/block/mmcblk0p7 1488 1552 2048 51 Unknown
/dev/block/mmcblk0p8 1552 1648 3072 52 Unknown
/dev/block/mmcblk0p9 1648 1712 2048 53 Unknown
/dev/block/mmcblk0p10 1712 1744 1024 54 Unknown
/dev/block/mmcblk0p11 1744 1776 1024 56 Unknown
/dev/block/mmcblk0p12 1776 2050 8751+ 55 Unknown
/dev/block/mmcblk0p13 2050 2146 3072 4a Unknown
/dev/block/mmcblk0p14 2146 2242 3072 4b Unknown
/dev/block/mmcblk0p15 2242 2274 1024 74 Unknown
/dev/block/mmcblk0p16 2274 2554 8957+ 75 Unknown
/dev/block/mmcblk0p17 2554 2562 256 76 Unknown
/dev/block/mmcblk0p18 2563 2595 1024 47 Unknown
/dev/block/mmcblk0p19 2595 2627 1024 34 Unknown
/dev/block/mmcblk0p20 2627 2667 1280 36 Unknown
/dev/block/mmcblk0p21 2667 2939 8701 71 Unknown
/dev/block/mmcblk0p22 2939 3067 4096 48 Unknown
/dev/block/mmcblk0p23 3067 3075 256 73 Unknown
/dev/block/mmcblk0p24 3076 3084 256 31 Unknown
/dev/block/mmcblk0p25 3084 16388 425726+ 83 Linux
/dev/block/mmcblk0p26 16388 58948 1361920+ 83 Linux
/dev/block/mmcblk0p27 58948 65502 209715+ 83 Linux
/dev/block/mmcblk0p28 65502 66142 20480 19 Unknown
Then I ran the following commands:
mke2fs /dev/block/mmcblk0p25
mke2fs /dev/block/mmcblk0p26
mke2fs /dev/block/mmcblk0p27
at this point i was able to mount the system, cache, and data directories from clockworkmod which was all good but i didnt have any android rom installed on any of these directories and at this point my sd card was being used as the main drive for the phone so clockworkmod couldnt mount it and i had no way to load a rom from it...
Soo... back into adb and i ran 'fdisk /dev/block/mmcblk0' and added another partion to the table that was 1gb in size and marked as fat32. Then on my computer made an image an sd card pushed it to the device and ran 'dd if=/data/sdcard.img of=/dev/block/mmcblk0p29' then 'mount /dev/block/mmcblk0p29 /sdcard' and wala clockworkmod detects the SD Card partition. I pushed down the cyanogenmod rom to the now mounted SD Card partition go to clockworkmod and install the zip file from there and reboot the device.
The end result is that my phone doesnt recognize that there is an SD Card pluged in because its using it as if it was the eMMC but it works! im back up and running again!
I know this is all jumbled when i get more time i will go through and try to clean it up and make the instructions a little more straight forward but i hope this helps some of you out there with bricked G2s... apparently it is possible to use your sdcard as a eMMC replacement
CollegeBound1987 said:
Okay so i have been looking all over the forums for help with my issue for the last like 6 hours and i have found stuff that is relevant but i have a weird twist.
I was installing google voice on the latest miui build for the t-mobile G2 and the device froze soo I restarted it causing this nightmare to begin.
I can not get back into android the phone freezes on the HTC screen, however i can get into fastboot which I can then use to get into clockworkmod recovery. At that point however I run into a problem, clockworkmod recovery can't mount anything including my SD card. I tried reformatting the card in clockworkmod and outside of it and no go. My device is S-OFF and when its in fastboot i can connect it to my computer and execute fastboot commands but i don't have a nandroid backup to recover the img files from for a manual reinstall from fastboot.
Any information i can give you to help i will try to get and if i am confused about something please correct me I am kinda new to all of this so I could very easily be confused about something.
Click to expand...
Click to collapse
Are you saying you don't have a nandroid at all? You can always flash a new recovery image via fastboot using the command:
Code:
fastboot flash recovery <path to recovery image>recovery.img
From there you can reboot into recovery via fastboot (fastboot reboot recovery) and then you should be able to flash a ROM or restore a backup (if you've got one).
I would recommend trying 4EXT Recovery by Madmaxx82. It's based on CWM, but has more options and great support. Here's the thread: http://forum.xda-developers.com/showthread.php?t=1377754
Ditamae said:
Are you saying you don't have a nandroid at all? You can always flash a new recovery image via fastboot using the command:
Code:
fastboot flash recovery <path to recovery image>recovery.img
From there you can reboot into recovery via fastboot (fastboot reboot recovery) and then you should be able to flash a ROM or restore a backup (if you've got one).
I would recommend trying 4EXT Recovery by Madmaxx82. It's based on CWM, but has more options and great support. Here's the thread: http://forum.xda-developers.com/showthread.php?t=1377754
Click to expand...
Click to collapse
i already tried to flash a new recovery image but it was just a reflash of CWM which seems to be unable to mount anything on the device including the sd card which will mount in fastboot. I didnt however know that there was an alternative recovery image i will give that a try see if i have any better luck.
this is what i keep getting i tried to install the img file in the zip and the zip itself neither seemed to work
Julies-MacBook-Pro:~ Julie$ /Users/Julie/Desktop/android-sdk-macosx/platform-tools/fastboot flash recovery /Users/Julie/Downloads/vision_pre_rc1_testing/recovery.img
sending 'recovery' (5158 KB)...
FAILED (status malformed (1 bytes))
finished. total time: 0.000s
Julies-MacBook-Pro:~ Julie$ /Users/Julie/Desktop/android-sdk-macosx/platform-tools/fastboot flash recovery /Users/Julie/Downloads/vision_pre_rc1_testing.zipsending 'recovery' (5305 KB)...
FAILED (status malformed (1 bytes))
finished. total time: 0.000s
Julies-MacBook-Pro:~ Julie$
http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
download the cwm recovery.img from the link and try again (3.0.2.4 is very stable)...
did you try to insert a different sdcard? maybe your sdcard is broken and it has nothing to do with recovery...
CollegeBound1987 said:
Okay so i have been looking all over the forums for help with my issue for the last like 6 hours and i have found stuff that is relevant but i have a weird twist.
I was installing google voice on the latest miui build for the t-mobile G2 and the device froze soo I restarted it causing this nightmare to begin.
I can not get back into android the phone freezes on the HTC screen, however i can get into fastboot which I can then use to get into clockworkmod recovery. At that point however I run into a problem, clockworkmod recovery can't mount anything including my SD card. I tried reformatting the card in clockworkmod and outside of it and no go. My device is S-OFF and when its in fastboot i can connect it to my computer and execute fastboot commands but i don't have a nandroid backup to recover the img files from for a manual reinstall from fastboot.
Any information i can give you to help i will try to get and if i am confused about something please correct me I am kinda new to all of this so I could very easily be confused about something.
Click to expand...
Click to collapse
Have you read this particular thread?
http://forum.xda-developers.com/showthread.php?t=1039504&page=2
Ditamae said:
Have you read this particular thread?
http://forum.xda-developers.com/showthread.php?t=1039504&page=2
Click to expand...
Click to collapse
i run into this error
md5sum: can't open '/dev/block/mmcblk0p27': No such file or director
~ # cd /dev/block/
/dev/block # ls
loop0 loop2 loop4 loop6 mmcblk0 platform
loop1 loop3 loop5 loop7 mmcblk0p1
"adb shell ls /dev/block" whats your output? are the partitions listed?
http://forum.xda-developers.com/showpost.php?p=13895268&;postcount=48
to check your emmc
hoffmas said:
"adb shell ls /dev/block" whats your output? are the partitions listed?
http://forum.xda-developers.com/showpost.php?p=13895268&;postcount=48
to check your emmc
Click to expand...
Click to collapse
Julies-MacBook-Prolatform-tools Julie$ /Users/Julie/Desktop/android-sdk-macosx/platform-tools/adb shell ls /dev/block
loop0 loop2 loop4 loop6 mmcblk0 platform
loop1 loop3 loop5 loop7 mmcblk0p1
~ # cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
cat: can't open '/sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name': No such file or directory
~ # cat /proc/kmsg | grep mmc0
<3>[ 4.155456] mmc0: No card detect facilities available
<6>[ 4.156005] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 4.156280] mmc0: Platform slot type: MMC
<6>[ 4.156402] mmc0: 4 bit data mode disabled
<6>[ 4.156646] mmc0: 8 bit data mode enabled
<6>[ 4.156799] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 4.157043] mmc0: Slot eject status = 0
<6>[ 4.157165] mmc0: Power save feature enable = 1
<6>[ 4.157318] mmc0: DM non-cached buffer at ffa0c000, dma_addr 0x2ae95000
<6>[ 4.157562] mmc0: DM cmd busaddr 0x2ae95000, cmdptr busaddr 0x2ae95300
<3>[ 4.279235] mmc0: error -110 whilst initialising MMC card
CollegeBound1987 said:
<3>[ 4.279235] mmc0: error -110 whilst initialising MMC card
Click to expand...
Click to collapse
hm doesn´t look good... but to be sure i would swap to http://webchat.freenode.net/?channels=g2root and post is there again...
my knowledge is not good enough to go further
i think the issue has something to do with the missing block partitions is there anyway to recreate them?
Brick phone fix
I found a fix/workaround using an SD Card as an eMMC replacement i posted the information in the first post i hope this helps some of you peoples out there with bricked phones
That's incredible work there. Too bad about the sd but at least you didn't have to buy a new phone!
i figure that i could make one of the user partitions larger so that the phone can utilize the 8gb card it will just think its internal storage
good to hear
...but how is the performance? i can imagine you won´t be able to run sense roms anymore, or am i wrong?
hoffmas said:
good to hear
...but how is the performance? i can imagine you won´t be able to run sense roms anymore, or am i wrong?
Click to expand...
Click to collapse
I am currently running miui with out much of a problem but it does hang a little when its installing programs from the market place and programs like titanium backup and rom manager dont seem to work on the device because it doesnt recognize that you have an sd card in but i am trying to find a fix for that right now...
Is there any way I can do this as my emmc works just it dosnt detect my sdcard wen its plugged in. But in my storage settings it jus gives me the option to erase the sdcard and that's it so if I can do wat you did but just reversed to push the sdcard pation to my emmc so that it can read my actual sd card or try this link I fount to recreat the partions. And flash them with this tool http://faq.riffbox.org/index.php?action=artikel&cat=10&id=53&artlang=en just I dnt kno how to use it ...yu know
Sent from my T-Mobile G2 using XDA
~ # fdisk /dev/block/mmcblk0
fdisk: can't read from /dev/block/mmcblk0
This is what I keep getting in adb.
Any help? I tried your way but it's soo difficult for me.
Mb a step by step procedure. I really think this is the only way to solve the emmc problem we have.
raza1 said:
~ # fdisk /dev/block/mmcblk0
fdisk: can't read from /dev/block/mmcblk0
This is what I keep getting in adb.
Any help? I tried your way but it's soo difficult for me.
Mb a step by step procedure. I really think this is the only way to solve the emmc problem we have.
Click to expand...
Click to collapse
I thought fdisk only applies to FAT partitions (fat32, etc).
what about this instead :
busybox df -hm
For example on my phone that would show:
Code:
Filesystem Size Used Available Use% Mounted on
tmpfs 183.2M 60.0K 183.1M 0% /dev
tmpfs 183.2M 0 183.2M 0% /mnt/asec
tmpfs 183.2M 0 183.2M 0% /mnt/obb
/dev/block/mmcblk0p25
549.2M 245.2M 304.0M 45% /system
/dev/block/mmcblk0p26
1.0G 414.1M 659.7M 39% /data
/dev/block/mmcblk0p27
295.3M 4.7M 290.5M 2% /cache
/dev/block/mmcblk0p28
20.6M 12.6M 8.0M 61% /devlog
/dev/block/mmcblk1p2 2.0G 323.9M 1.7G 16% /sd-ext
/dev/block/mmcblk1p2 2.0G 323.9M 1.7G 16% /data/app
/dev/block/mmcblk1p2 2.0G 323.9M 1.7G 16% /data/app-private
/dev/block/vold/179:65
12.7G 4.8G 7.9G 38% /mnt/sdcard
/dev/block/vold/179:65
12.7G 4.8G 7.9G 38% /mnt/secure/asec
Edit: though I tried fdisk myself (I'm currently booted into the phone though, not sure if you're calling that from recovery or what)
Code:
[email protected]:/ # fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 275200.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Warning: deleting partitions after 60
Command (m for help): p
Disk /dev/block/mmcblk0: 2254 MB, 2254438400 bytes
1 heads, 16 sectors/track, 275200 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 63 500 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 63 71 64 45 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 71 634 4500 46 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 634 275456 2198583 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 634 4384 30000 49 Unknown
/dev/block/mmcblk0p6 4384 5946 12500 50 Unknown
/dev/block/mmcblk0p7 5946 6202 2048 51 Unknown
/dev/block/mmcblk0p8 6202 6586 3072 52 Unknown
/dev/block/mmcblk0p9 6586 6842 2048 53 Unknown
/dev/block/mmcblk0p10 6842 6970 1024 54 Unknown
/dev/block/mmcblk0p11 6971 7098 1024 56 Unknown
/dev/block/mmcblk0p12 7099 8192 8751+ 55 Unknown
/dev/block/mmcblk0p13 8193 8577 3072 4a Unknown
/dev/block/mmcblk0p14 8577 8961 3072 4b Unknown
/dev/block/mmcblk0p15 8961 9089 1024 74 Unknown
/dev/block/mmcblk0p16 9089 10208 8957+ 75 Unknown
/dev/block/mmcblk0p17 10209 10240 256 76 Unknown
/dev/block/mmcblk0p18 10241 10369 1024 47 Unknown
/dev/block/mmcblk0p19 10369 10497 1024 34 Unknown
/dev/block/mmcblk0p20 10497 10657 1280 36 Unknown
/dev/block/mmcblk0p21 10657 11744 8701 71 Unknown
/dev/block/mmcblk0p22 11744 12256 4096 48 Unknown
/dev/block/mmcblk0p23 12257 12288 256 73 Unknown
/dev/block/mmcblk0p24 12289 12544 2047 26 Unknown
/dev/block/mmcblk0p25 12545 83968 571391+ 83 Linux
/dev/block/mmcblk0p26 83969 223616 1117183+ 83 Linux
/dev/block/mmcblk0p27 223617 262016 307199+ 83 Linux
/dev/block/mmcblk0p28 262017 264672 21247+ 19 Unknown
/dev/block/mmcblk0p29 264673 264704 256 23 Unknown
/dev/block/mmcblk0p30 634 4384 30000 49 Unknown
/dev/block/mmcblk0p31 4384 5946 12500 50 Unknown
/dev/block/mmcblk0p32 5946 6202 2048 51 Unknown
/dev/block/mmcblk0p33 6202 6586 3072 52 Unknown
/dev/block/mmcblk0p34 6586 6842 2048 53 Unknown
/dev/block/mmcblk0p35 6842 6970 1024 54 Unknown
/dev/block/mmcblk0p36 6971 7098 1024 56 Unknown
/dev/block/mmcblk0p37 7099 8192 8751+ 55 Unknown
/dev/block/mmcblk0p38 8193 8577 3072 4a Unknown
/dev/block/mmcblk0p39 8577 8961 3072 4b Unknown
/dev/block/mmcblk0p40 8961 9089 1024 74 Unknown
/dev/block/mmcblk0p41 9089 10208 8957+ 75 Unknown
/dev/block/mmcblk0p42 10209 10240 256 76 Unknown
/dev/block/mmcblk0p43 10241 10369 1024 47 Unknown
/dev/block/mmcblk0p44 10369 10497 1024 34 Unknown
/dev/block/mmcblk0p45 10497 10657 1280 36 Unknown
/dev/block/mmcblk0p46 10657 11744 8701 71 Unknown
/dev/block/mmcblk0p47 11744 12256 4096 48 Unknown
/dev/block/mmcblk0p48 12257 12288 256 73 Unknown
/dev/block/mmcblk0p49 12289 12544 2047 26 Unknown
/dev/block/mmcblk0p50 12545 83968 571391+ 83 Linux
/dev/block/mmcblk0p51 83969 223616 1117183+ 83 Linux
/dev/block/mmcblk0p52 223617 262016 307199+ 83 Linux
/dev/block/mmcblk0p53 262017 264672 21247+ 19 Unknown
/dev/block/mmcblk0p54 264673 264704 256 23 Unknown
/dev/block/mmcblk0p55 634 4384 30000 49 Unknown
/dev/block/mmcblk0p56 4384 5946 12500 50 Unknown
/dev/block/mmcblk0p57 5946 6202 2048 51 Unknown
/dev/block/mmcblk0p58 6202 6586 3072 52 Unknown
/dev/block/mmcblk0p59 6586 6842 2048 53 Unknown
/dev/block/mmcblk0p60 6842 6970 1024 54 Unknown
Partition table entries are not in disk order
---------- Post added at 07:54 AM ---------- Previous post was at 07:46 AM ----------
Gave it a shot under 4EXT recovery as well, shows output (numbers slightly different than when in boot, but close)
Code:
~ # fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 275456.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Warning: deleting partitions after 60
Command (m for help): p
Disk /dev/block/mmcblk0: 2256 MB, 2256535552 bytes
1 heads, 16 sectors/track, 275456 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 63 500 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 63 71 64 45 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 71 634 4500 46 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 634 275456 2198583 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 634 4384 30000 49 Unknown
/dev/block/mmcblk0p6 4384 5946 12500 50 Unknown
/dev/block/mmcblk0p7 5946 6202 2048 51 Unknown
/dev/block/mmcblk0p8 6202 6586 3072 52 Unknown
/dev/block/mmcblk0p9 6586 6842 2048 53 Unknown
/dev/block/mmcblk0p10 6842 6970 1024 54 Unknown
/dev/block/mmcblk0p11 6971 7098 1024 56 Unknown
/dev/block/mmcblk0p12 7099 8192 8751+ 55 Unknown
/dev/block/mmcblk0p13 8193 8577 3072 4a Unknown
/dev/block/mmcblk0p14 8577 8961 3072 4b Unknown
/dev/block/mmcblk0p15 8961 9089 1024 74 Unknown
/dev/block/mmcblk0p16 9089 10208 8957+ 75 Unknown
/dev/block/mmcblk0p17 10209 10240 256 76 Unknown
/dev/block/mmcblk0p18 10241 10369 1024 47 Unknown
/dev/block/mmcblk0p19 10369 10497 1024 34 Unknown
/dev/block/mmcblk0p20 10497 10657 1280 36 Unknown
/dev/block/mmcblk0p21 10657 11744 8701 71 Unknown
/dev/block/mmcblk0p22 11744 12256 4096 48 Unknown
/dev/block/mmcblk0p23 12257 12288 256 73 Unknown
/dev/block/mmcblk0p24 12289 12544 2047 26 Unknown
/dev/block/mmcblk0p25 12545 83968 571391+ 83 Linux
/dev/block/mmcblk0p26 83969 223616 1117183+ 83 Linux
/dev/block/mmcblk0p27 223617 262016 307199+ 83 Linux
/dev/block/mmcblk0p28 262017 264672 21247+ 19 Unknown
/dev/block/mmcblk0p29 264673 264704 256 23 Unknown
/dev/block/mmcblk0p30 634 4384 30000 49 Unknown
/dev/block/mmcblk0p31 4384 5946 12500 50 Unknown
/dev/block/mmcblk0p32 5946 6202 2048 51 Unknown
/dev/block/mmcblk0p33 6202 6586 3072 52 Unknown
/dev/block/mmcblk0p34 6586 6842 2048 53 Unknown
/dev/block/mmcblk0p35 6842 6970 1024 54 Unknown
/dev/block/mmcblk0p36 6971 7098 1024 56 Unknown
/dev/block/mmcblk0p37 7099 8192 8751+ 55 Unknown
/dev/block/mmcblk0p38 8193 8577 3072 4a Unknown
/dev/block/mmcblk0p39 8577 8961 3072 4b Unknown
/dev/block/mmcblk0p40 8961 9089 1024 74 Unknown
/dev/block/mmcblk0p41 9089 10208 8957+ 75 Unknown
/dev/block/mmcblk0p42 10209 10240 256 76 Unknown
/dev/block/mmcblk0p43 10241 10369 1024 47 Unknown
/dev/block/mmcblk0p44 10369 10497 1024 34 Unknown
/dev/block/mmcblk0p45 10497 10657 1280 36 Unknown
/dev/block/mmcblk0p46 10657 11744 8701 71 Unknown
/dev/block/mmcblk0p47 11744 12256 4096 48 Unknown
/dev/block/mmcblk0p48 12257 12288 256 73 Unknown
/dev/block/mmcblk0p49 12289 12544 2047 26 Unknown
/dev/block/mmcblk0p50 12545 83968 571391+ 83 Linux
/dev/block/mmcblk0p51 83969 223616 1117183+ 83 Linux
/dev/block/mmcblk0p52 223617 262016 307199+ 83 Linux
/dev/block/mmcblk0p53 262017 264672 21247+ 19 Unknown
/dev/block/mmcblk0p54 264673 264704 256 23 Unknown
/dev/block/mmcblk0p55 634 4384 30000 49 Unknown
/dev/block/mmcblk0p56 4384 5946 12500 50 Unknown
/dev/block/mmcblk0p57 5946 6202 2048 51 Unknown
/dev/block/mmcblk0p58 6202 6586 3072 52 Unknown
/dev/block/mmcblk0p59 6586 6842 2048 53 Unknown
/dev/block/mmcblk0p60 6842 6970 1024 54 Unknown
Partition table entries are not in disk order
Command (m for help):
If it can't read the eMMC block at all, then quite possibly it's dead/corupt, and there ain't no coming back from that.
kbeezie said:
I thought fdisk only applies to FAT partitions (fat32, etc).
what about this instead :
busybox df -hm
For example on my phone that would show:
Code:
Filesystem Size Used Available Use% Mounted on
tmpfs 183.2M 60.0K 183.1M 0% /dev
tmpfs 183.2M 0 183.2M 0% /mnt/asec
tmpfs 183.2M 0 183.2M 0% /mnt/obb
/dev/block/mmcblk0p25
549.2M 245.2M 304.0M 45% /system
/dev/block/mmcblk0p26
1.0G 414.1M 659.7M 39% /data
/dev/block/mmcblk0p27
295.3M 4.7M 290.5M 2% /cache
/dev/block/mmcblk0p28
20.6M 12.6M 8.0M 61% /devlog
/dev/block/mmcblk1p2 2.0G 323.9M 1.7G 16% /sd-ext
/dev/block/mmcblk1p2 2.0G 323.9M 1.7G 16% /data/app
/dev/block/mmcblk1p2 2.0G 323.9M 1.7G 16% /data/app-private
/dev/block/vold/179:65
12.7G 4.8G 7.9G 38% /mnt/sdcard
/dev/block/vold/179:65
12.7G 4.8G 7.9G 38% /mnt/secure/asec
Edit: though I tried fdisk myself (I'm currently booted into the phone though, not sure if you're calling that from recovery or what)
Code:
[email protected]:/ # fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 275200.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Warning: deleting partitions after 60
Command (m for help): p
Disk /dev/block/mmcblk0: 2254 MB, 2254438400 bytes
1 heads, 16 sectors/track, 275200 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 63 500 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 63 71 64 45 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 71 634 4500 46 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 634 275456 2198583 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 634 4384 30000 49 Unknown
/dev/block/mmcblk0p6 4384 5946 12500 50 Unknown
/dev/block/mmcblk0p7 5946 6202 2048 51 Unknown
/dev/block/mmcblk0p8 6202 6586 3072 52 Unknown
/dev/block/mmcblk0p9 6586 6842 2048 53 Unknown
/dev/block/mmcblk0p10 6842 6970 1024 54 Unknown
/dev/block/mmcblk0p11 6971 7098 1024 56 Unknown
/dev/block/mmcblk0p12 7099 8192 8751+ 55 Unknown
/dev/block/mmcblk0p13 8193 8577 3072 4a Unknown
/dev/block/mmcblk0p14 8577 8961 3072 4b Unknown
/dev/block/mmcblk0p15 8961 9089 1024 74 Unknown
/dev/block/mmcblk0p16 9089 10208 8957+ 75 Unknown
/dev/block/mmcblk0p17 10209 10240 256 76 Unknown
/dev/block/mmcblk0p18 10241 10369 1024 47 Unknown
/dev/block/mmcblk0p19 10369 10497 1024 34 Unknown
/dev/block/mmcblk0p20 10497 10657 1280 36 Unknown
/dev/block/mmcblk0p21 10657 11744 8701 71 Unknown
/dev/block/mmcblk0p22 11744 12256 4096 48 Unknown
/dev/block/mmcblk0p23 12257 12288 256 73 Unknown
/dev/block/mmcblk0p24 12289 12544 2047 26 Unknown
/dev/block/mmcblk0p25 12545 83968 571391+ 83 Linux
/dev/block/mmcblk0p26 83969 223616 1117183+ 83 Linux
/dev/block/mmcblk0p27 223617 262016 307199+ 83 Linux
/dev/block/mmcblk0p28 262017 264672 21247+ 19 Unknown
/dev/block/mmcblk0p29 264673 264704 256 23 Unknown
/dev/block/mmcblk0p30 634 4384 30000 49 Unknown
/dev/block/mmcblk0p31 4384 5946 12500 50 Unknown
/dev/block/mmcblk0p32 5946 6202 2048 51 Unknown
/dev/block/mmcblk0p33 6202 6586 3072 52 Unknown
/dev/block/mmcblk0p34 6586 6842 2048 53 Unknown
/dev/block/mmcblk0p35 6842 6970 1024 54 Unknown
/dev/block/mmcblk0p36 6971 7098 1024 56 Unknown
/dev/block/mmcblk0p37 7099 8192 8751+ 55 Unknown
/dev/block/mmcblk0p38 8193 8577 3072 4a Unknown
/dev/block/mmcblk0p39 8577 8961 3072 4b Unknown
/dev/block/mmcblk0p40 8961 9089 1024 74 Unknown
/dev/block/mmcblk0p41 9089 10208 8957+ 75 Unknown
/dev/block/mmcblk0p42 10209 10240 256 76 Unknown
/dev/block/mmcblk0p43 10241 10369 1024 47 Unknown
/dev/block/mmcblk0p44 10369 10497 1024 34 Unknown
/dev/block/mmcblk0p45 10497 10657 1280 36 Unknown
/dev/block/mmcblk0p46 10657 11744 8701 71 Unknown
/dev/block/mmcblk0p47 11744 12256 4096 48 Unknown
/dev/block/mmcblk0p48 12257 12288 256 73 Unknown
/dev/block/mmcblk0p49 12289 12544 2047 26 Unknown
/dev/block/mmcblk0p50 12545 83968 571391+ 83 Linux
/dev/block/mmcblk0p51 83969 223616 1117183+ 83 Linux
/dev/block/mmcblk0p52 223617 262016 307199+ 83 Linux
/dev/block/mmcblk0p53 262017 264672 21247+ 19 Unknown
/dev/block/mmcblk0p54 264673 264704 256 23 Unknown
/dev/block/mmcblk0p55 634 4384 30000 49 Unknown
/dev/block/mmcblk0p56 4384 5946 12500 50 Unknown
/dev/block/mmcblk0p57 5946 6202 2048 51 Unknown
/dev/block/mmcblk0p58 6202 6586 3072 52 Unknown
/dev/block/mmcblk0p59 6586 6842 2048 53 Unknown
/dev/block/mmcblk0p60 6842 6970 1024 54 Unknown
Partition table entries are not in disk order
---------- Post added at 07:54 AM ---------- Previous post was at 07:46 AM ----------
Gave it a shot under 4EXT recovery as well, shows output (numbers slightly different than when in boot, but close)
Code:
~ # fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 275456.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Warning: deleting partitions after 60
Command (m for help): p
Disk /dev/block/mmcblk0: 2256 MB, 2256535552 bytes
1 heads, 16 sectors/track, 275456 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 63 500 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 63 71 64 45 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 71 634 4500 46 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 634 275456 2198583 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 634 4384 30000 49 Unknown
/dev/block/mmcblk0p6 4384 5946 12500 50 Unknown
/dev/block/mmcblk0p7 5946 6202 2048 51 Unknown
/dev/block/mmcblk0p8 6202 6586 3072 52 Unknown
/dev/block/mmcblk0p9 6586 6842 2048 53 Unknown
/dev/block/mmcblk0p10 6842 6970 1024 54 Unknown
/dev/block/mmcblk0p11 6971 7098 1024 56 Unknown
/dev/block/mmcblk0p12 7099 8192 8751+ 55 Unknown
/dev/block/mmcblk0p13 8193 8577 3072 4a Unknown
/dev/block/mmcblk0p14 8577 8961 3072 4b Unknown
/dev/block/mmcblk0p15 8961 9089 1024 74 Unknown
/dev/block/mmcblk0p16 9089 10208 8957+ 75 Unknown
/dev/block/mmcblk0p17 10209 10240 256 76 Unknown
/dev/block/mmcblk0p18 10241 10369 1024 47 Unknown
/dev/block/mmcblk0p19 10369 10497 1024 34 Unknown
/dev/block/mmcblk0p20 10497 10657 1280 36 Unknown
/dev/block/mmcblk0p21 10657 11744 8701 71 Unknown
/dev/block/mmcblk0p22 11744 12256 4096 48 Unknown
/dev/block/mmcblk0p23 12257 12288 256 73 Unknown
/dev/block/mmcblk0p24 12289 12544 2047 26 Unknown
/dev/block/mmcblk0p25 12545 83968 571391+ 83 Linux
/dev/block/mmcblk0p26 83969 223616 1117183+ 83 Linux
/dev/block/mmcblk0p27 223617 262016 307199+ 83 Linux
/dev/block/mmcblk0p28 262017 264672 21247+ 19 Unknown
/dev/block/mmcblk0p29 264673 264704 256 23 Unknown
/dev/block/mmcblk0p30 634 4384 30000 49 Unknown
/dev/block/mmcblk0p31 4384 5946 12500 50 Unknown
/dev/block/mmcblk0p32 5946 6202 2048 51 Unknown
/dev/block/mmcblk0p33 6202 6586 3072 52 Unknown
/dev/block/mmcblk0p34 6586 6842 2048 53 Unknown
/dev/block/mmcblk0p35 6842 6970 1024 54 Unknown
/dev/block/mmcblk0p36 6971 7098 1024 56 Unknown
/dev/block/mmcblk0p37 7099 8192 8751+ 55 Unknown
/dev/block/mmcblk0p38 8193 8577 3072 4a Unknown
/dev/block/mmcblk0p39 8577 8961 3072 4b Unknown
/dev/block/mmcblk0p40 8961 9089 1024 74 Unknown
/dev/block/mmcblk0p41 9089 10208 8957+ 75 Unknown
/dev/block/mmcblk0p42 10209 10240 256 76 Unknown
/dev/block/mmcblk0p43 10241 10369 1024 47 Unknown
/dev/block/mmcblk0p44 10369 10497 1024 34 Unknown
/dev/block/mmcblk0p45 10497 10657 1280 36 Unknown
/dev/block/mmcblk0p46 10657 11744 8701 71 Unknown
/dev/block/mmcblk0p47 11744 12256 4096 48 Unknown
/dev/block/mmcblk0p48 12257 12288 256 73 Unknown
/dev/block/mmcblk0p49 12289 12544 2047 26 Unknown
/dev/block/mmcblk0p50 12545 83968 571391+ 83 Linux
/dev/block/mmcblk0p51 83969 223616 1117183+ 83 Linux
/dev/block/mmcblk0p52 223617 262016 307199+ 83 Linux
/dev/block/mmcblk0p53 262017 264672 21247+ 19 Unknown
/dev/block/mmcblk0p54 264673 264704 256 23 Unknown
/dev/block/mmcblk0p55 634 4384 30000 49 Unknown
/dev/block/mmcblk0p56 4384 5946 12500 50 Unknown
/dev/block/mmcblk0p57 5946 6202 2048 51 Unknown
/dev/block/mmcblk0p58 6202 6586 3072 52 Unknown
/dev/block/mmcblk0p59 6586 6842 2048 53 Unknown
/dev/block/mmcblk0p60 6842 6970 1024 54 Unknown
Partition table entries are not in disk order
Command (m for help):
If it can't read the eMMC block at all, then quite possibly it's dead/corupt, and there ain't no coming back from that.
Click to expand...
Click to collapse
Yeah I think I have to replace the 'motherboard' totally with one out off a phone with a broken glass or something.
I'll keep searching for a software solution first.
[DEVS & EXP-USERS ONLY] HTC One X - High I/O wait. Same issue as the N7. (confirmed)
This little thread aims at getting some information about an issue I thought for months I am alone with.
Since I got my One X, stock or running custom stuff, my phone always gets sluggish far far beyond the point of being useable if I fill my /data partition with too much data (~1GB free triggers it usually), or move large files around in it (dd'ing some zeros onto it triggers it too).
No kind of rebooting, cache wiping, or anything else will fix it permanently. The lags will be back after a very short while once you experienced them.
Vodafone told me to RMA the phone (it was only software branded), but If you know me, then you know that I am lazy in these kinds of things and since I thought I was the only one and a wipe of /data fixed it every time for a short period, I didn't do it.
Yeah I know. Lazy b*tch.
A few hours ago 'Aux' who had complained about a very sluggish phone a few times already joined IRC and described his problem in more detail and I suddenly made the connection in my mind between my issue and his. He then allowed me to debug that stuff, and I came up with the exact same issue I am facing continuously:
High I/O waits while writing/reading from /data.
This thread aims at gathering intel on this issue. Do not answer here with pointless questions or howto...? stuff.
Ah btw: No, one lag after unlocking the phone is not the issue I am talking about. I mean: ~1-10 fps on the launcher, app opening takes minutes (games) & still lags like hell and downloading apps in the market is close to impossible. (~10byte p second)
So if you don't experience this, don't post logs. I am serious, I will report anyone who wastes my time on that.
To check if your phone suffers from this, run 'top'
if it shows something like this:
Code:
User 2%, System 1%, [COLOR="Red"][B]IOW 74%[/B][/COLOR], IRQ 0%
User 34 + Nice 0 + Sys 18 + Idle 263 + IOW 902 + IRQ 0 + SIRQ 1 = 1218
PID PR CPU% S #THR VSS RSS PCY UID Name
2061 0 1% S 13 471140K 32956K fg u0_a75 com.google.android.apps.reader
519 1 0% S 73 559264K 58024K fg system system_server
1035 1 0% S 20 512864K 63100K fg u0_a86 com.anddoes.launcher
2265 1 0% R 1 1132K 500K root top
[COLOR="red"][B] 105 0 0% D 1 0K 0K root mmcqd/0[/B][/COLOR]
898 1 0% S 14 483120K 60344K fg u0_a39 com.android.systemui
882 0 0% S 1 2768K 1488K wifi /system/bin/wpa_supplicant
435 0 0% S 1 0K 0K root kworker/0:2
173 1 0% S 11 29644K 10104K fg system /system/bin/surfaceflinger
[B][COLOR="red"] 123 1 0% D 1 0K 0K root jbd2/mmcblk0p15[/COLOR][/B]
879 0 0% S 1 0K 0K root irq/340-wl12xx
run 'vmstat', if it looks like this
Code:
procs memory system cpu
r b free mapped anon slab in cs flt us ni sy id wa ir
0 [COLOR="Red"]3[/COLOR] 29488 64232 261024 45956 1788 2723 0 22 0 29 99 [COLOR="red"]96[/COLOR] 0
0 [COLOR="red"]2[/COLOR] 29488 64284 261056 45952 620 905 0 1 0 4 99 [COLOR="red"]99[/COLOR] 0
1 [COLOR="red"]6[/COLOR] 29556 64284 261056 45908 472 755 0 1 0 4 99 [COLOR="red"]99[/COLOR] 0
3 [COLOR="red"]3[/COLOR] 29496 64284 261056 45908 454 680 0 0 0 1 99 [COLOR="red"]99[/COLOR] 0
0 [COLOR="red"]8[/COLOR] 29436 64284 261056 45904 462 767 0 4 0 4 99 [COLOR="red"]98[/COLOR] 0
3 [COLOR="red"]4[/COLOR] 31300 64328 261328 45840 2177 4151 0 50 0 15 99 [COLOR="red"]92[/COLOR] 0
and if 'cat /proc/fs/jbd2/mmcblk0p15-8/info' looks like this too:
Code:
cat /proc/fs/jbd2/mmcblk0p15-8/info
649 transaction, each up to 2196 blocks
average:
0ms waiting for transaction
1460ms running transaction
[B][COLOR="Red"] 16544590ms transaction was being locked[/COLOR][/B]
0ms flushing data (in ordered mode)
710ms logging transaction
603582us average transaction commit time
100 handles per transaction
7 blocks per transaction
8 logged blocks per transaction
Then you are most likely affected.
What I need from you:
Everything the above commands throw out as well as the following:
Code:
echo 1 > /proc/sys/vm/block_dump ; cat /proc/kmsg ; echo 0 > /proc/sys/vm/block_dump
(this is very spammy, you might want to add '> file.log' to the kmsg part)
-----
iostat
-----
iostat -kd 5
(keep it running for about 30 seconds)
-----
cat /proc/meminfo
-----
cat /proc/diskstats
This issue is the same I am facing on my N7. ~2.5Gb free will trigger a very poor performance on the N7 as well, so we have found a general bug in one of the used components (hardware if it's the same, the jbd journaling system, ... )
To figure out what this is exactly I need as much intel as you can gather if your device is in such a state.
I will attach my findings, this thread and all logs gathered on the already existing bug report for the N7 @google. (since it is more likely to get an answer out of them than it is to get one from HTC, sadly)
If you have a N7 facing the same issue:
Attach the logs here too, but please specify that they are from a N7.
It didn't happened to me while using my htc one x (probably because I don't fill the data partition). But I'm sure that low storage makes my nexus 7 slower and laggier(tested it). I hope you can find a solution to that. I will post logs tomorrow because I don't have time right now.
Temporary fix found:
1. Reboot to CWM.
2. Nandroid backup.
3. Factory reset/format data.
4. Nandroid restore.
And HOX back to normal! You can write lots more of data! Incredible!
It would be nice if guys with N7 tested.
So here is my commands output, hope it helps
EDIT: oups, I thought you need only these 3 commands, I didn't read your post to the end, will post the other commands tomorrow
TOP
Code:
User 5%, System 6%, IOW 0%, IRQ 0%
User 17 + Nice 0 + Sys 20 + Idle 279 + IOW 0 + IRQ 0 + SIRQ 0 = 316
PID PR CPU% S #THR VSS RSS PCY UID Name
4480 0 5% R 1 1100K 468K fg app_27 top
571 0 3% S 86 409676K 74528K fg system system_server
4200 0 2% S 14 302320K 49804K fg app_27 jackpal.androidterm
4460 0 1% S 1 0K 0K fg root kworker/0:2
897 0 0% S 13 308828K 65552K fg system com.android.systemui
39 0 0% S 1 0K 0K fg root kworker/u:1
145 0 0% S 33 192540K 9800K fg media /system/bin/mediaserver
142 0 0% S 10 33188K 13436K fg system /system/bin/surfaceflinger
885 0 0% S 1 2716K 1224K fg wifi /system/bin/wpa_supplicant
23 0 0% S 1 0K 0K fg root sync_supers
24 0 0% S 1 0K 0K fg root bdi-default
25 1 0% S 1 0K 0K fg root kblockd
26 0 0% S 1 0K 0K fg root irq/114-tegra_s
27 1 0% S 1 0K 0K fg root spi_tegra-1
28 1 0% S 1 0K 0K fg root irq/125-tegra_s
29 1 0% S 1 0K 0K fg root spi_tegra-3
30 0 0% S 1 0K 0K fg root khubd
31 1 0% S 1 0K 0K fg root irq/118-tps8003
32 1 0% S 1 0K 0K fg root tps65200
33 1 0% S 1 0K 0K fg root rpciod
34 0 0% S 1 0K 0K fg root kworker/0:1
35 1 0% S 1 0K 0K fg root cpu-tegra
36 1 0% S 1 0K 0K fg root cpu-tegra3
37 1 0% S 1 0K 0K fg root cpu-tegra3-plug
38 1 0% S 1 0K 0K fg root baseband_xmm_po
40 1 0% S 1 0K 0K fg root htc_simhotswap
41 1 0% S 1 0K 0K fg root charger_ctrl_ti
42 1 0% S 1 0K 0K fg root batt_timer
43 1 0% S 1 0K 0K fg root khungtaskd
44 1 0% S 1 0K 0K fg root kswapd0
45 1 0% S 1 0K 0K fg root fsnotify_mark
46 1 0% S 1 0K 0K fg root nfsiod
47 1 0% S 1 0K 0K fg root crypto
63 1 0% S 1 0K 0K fg root tegradc.0/a
64 1 0% S 1 0K 0K fg root tegradc.0/b
65 1 0% S 1 0K 0K fg root tegradc.0/c
66 0 0% S 1 0K 0K fg root irq/223-host_sp
67 1 0% S 1 0K 0K fg root nvhdcp1
68 1 0% S 1 0K 0K fg root tegradc.1/a
69 1 0% S 1 0K 0K fg root tegradc.1/b
70 1 0% S 1 0K 0K fg root tegradc.1/c
71 1 0% S 1 0K 0K fg root mhl_sii9234_wq
72 1 0% S 1 0K 0K fg root nct1008
73 1 0% S 1 0K 0K fg root vib
74 1 0% S 1 0K 0K fg root cable_detect
82 1 0% S 1 0K 0K fg root fsl_tegra_udc
83 1 0% S 1 0K 0K fg root f_mtp
84 1 0% S 1 0K 0K fg root file-storage
86 0 0% S 1 0K 0K fg root irq/393-synapti
87 1 0% S 1 0K 0K fg root cm3629_wq
88 1 0% D 1 0K 0K fg root kinteractiveup
89 1 0% S 1 0K 0K fg root kn3ocold
90 1 0% S 1 0K 0K fg root led
91 1 0% S 1 0K 0K fg root led_powerkey
103 1 0% S 1 0K 0K fg root binder
104 1 0% S 1 0K 0K fg root hd-audio0
105 0 0% S 1 0K 0K fg root mmcqd/0
106 0 0% S 1 0K 0K fg root irq/77-tegra_ac
107 0 0% S 1 0K 0K fg root irq/77-tegra_ac
108 1 0% S 1 0K 0K fg root detect
109 1 0% S 1 0K 0K fg root button
110 1 0% S 1 0K 0K fg root HS_PMIC_DETECT
111 1 0% S 1 0K 0K fg root HS_PMIC_BUTTON
112 1 0% S 1 0K 0K fg root HS_GPIO_DETECT
113 1 0% S 1 0K 0K fg root HS_GPIO_BUTTON
114 1 0% S 1 0K 0K fg root poke_queue
115 1 0% S 1 0K 0K fg root rq_stats
116 0 0% S 1 324K 184K fg root /sbin/ueventd
119 0 0% S 1 0K 0K fg root kworker/u:2
120 0 0% S 1 0K 0K fg root jbd2/mmcblk0p12
121 1 0% S 1 0K 0K fg root ext4-dio-unwrit
122 0 0% S 1 0K 0K fg root jbd2/mmcblk0p15
123 1 0% S 1 0K 0K fg root ext4-dio-unwrit
124 0 0% S 1 0K 0K fg root jbd2/mmcblk0p13
125 1 0% S 1 0K 0K fg root ext4-dio-unwrit
126 1 0% S 1 0K 0K fg root jbd2/mmcblk0p3-
127 1 0% S 1 0K 0K fg root ext4-dio-unwrit
128 0 0% S 1 0K 0K fg root jbd2/mmcblk0p18
129 1 0% S 1 0K 0K fg root ext4-dio-unwrit
130 1 0% S 1 0K 0K fg root jbd2/mmcblk0p19
131 1 0% S 1 0K 0K fg root ext4-dio-unwrit
Vmstat
Code:
procs memory system cpu
r b free mapped anon slab in cs flt us ni sy id wa ir
2 0 67328 119288 326872 37496 201 448 0 13 0 8 80 0 0
0 0 67328 119252 326876 37496 224 398 0 19 0 5 77 0 0
0 0 66820 119164 327452 37396 680 1076 0 21 0 15 99 0 0
0 0 66820 119180 327452 37388 188 267 0 10 0 6 86 0 0
0 0 66820 119252 327560 37388 264 517 0 14 0 16 73 0 0
0 0 66820 119252 327576 37388 185 376 0 14 0 6 81 0 0
0 0 66820 119252 327504 37388 233 400 0 15 0 6 82 0 0
1 0 68928 119252 325308 37388 205 399 0 16 0 6 80 0 0
0 0 68928 119252 325312 37388 252 614 0 12 0 11 80 0 0
0 0 68928 119252 325340 37380 245 385 0 10 0 9 81 0 0
0 0 68928 119252 325344 37376 245 408 0 8 0 7 88 0 0
3 0 68928 119252 325344 37376 256 340 0 11 0 14 78 0 0
2 0 68928 119252 325344 37376 283 411 0 10 0 13 81 0 0
0 0 68928 119252 325344 37376 227 421 0 10 0 7 85 0 0
0 0 68928 119252 325348 37376 230 399 0 12 0 11 79 0 0
0 0 68928 119252 325348 37376 201 405 0 11 0 7 85 0 0
1 0 68928 119252 325348 37376 215 392 0 10 0 10 83 0 0
0 0 68928 119252 325352 37376 221 399 0 11 0 8 83 0 0
0 0 68928 119252 325352 37376 202 378 0 12 0 7 84 0 0
0 0 68928 119252 325404 37376 253 793 1 16 0 11 75 1 0
procs memory system cpu
r b free mapped anon slab in cs flt us ni sy id wa ir
0 0 68928 119264 325372 37380 216 409 0 7 0 11 84 0 0
2 0 68928 119264 325376 37380 195 424 0 18 0 6 79 0 0
0 0 68928 119264 325376 37380 207 406 0 11 0 6 86 0 0
0 0 68928 119264 325376 37380 211 400 0 15 0 2 86 0 0
0 0 69672 118380 325484 37380 618 1261 0 38 0 16 49 0 0
2 0 69176 119304 325500 37380 328 787 0 14 0 9 77 0 0
cat /proc/fs/jbd2/mmcblk0p15-8/info
Code:
971 transaction, each up to 2196 blocks
average:
0ms waiting for transaction
370ms running transaction
0ms transaction was being locked
0ms flushing data (in ordered mode)
10ms logging transaction
6714us average transaction commit time
211 handles per transaction
5 blocks per transaction
6 logged blocks per transaction
I'll start by saying I don't have any logs to share. But I experienced the same thing after filling my phone with music. I was overseas and had a useless phone for a week.
Although you said it only seemed to affect your phone, my serial starts with HT23MW, could be from the same batch of phones?
While reading op I recall just saw someone asking JBQ on a Android Building's 4.1.2 in AOSP discussion..
any changes to address this problem?
"Nexus 7 slow when less than 3GB free "
http://productforums.google.com/forum/#!msg/mobile/loqbCbKVMWE/veH_7NAk-YgJ
- show quoted text -
Click to expand...
Click to collapse
I then went back there and follow up the link above..
By reading into the discussion thread at least we can confirmed that Google is working on it and the issue still left un-fix on JRO03S...
:angel:
Tabtoub said:
So here is my commands output, hope it helps
EDIT: oups, I thought you need only these 3 commands, I didn't read your post to the end, will post the other commands tomorrow
TOP
Vmstat
cat /proc/fs/jbd2/mmcblk0p15-8/info
Click to expand...
Click to collapse
Now look into the op, do you see the part where I say you shouldn't post here if you don't have those lags?
Now look again at the op, and check your logs with the one posted, especially the red parts. You notice something?
Thanks for posting logs with no issue present.
fizzlington said:
I'll start by saying I don't have any logs to share. But I experienced the same thing after filling my phone with music. I was overseas and had a useless phone for a week.
Although you said it only seemed to affect your phone, my serial starts with HT23MW, could be from the same batch of phones?
Click to expand...
Click to collapse
Mine is a HT23JW, though I really doubt that it is a hardware issue, or at least not solely a hardware issue.
i am not able to post logs at the moment, but wish to add my experiences to this topic.
Since getting my HOX, i had issues when transferring large amounts of data (music) to the phone. As has been said above, the phone becomes unresponsive, heats up and basically doesn't work until you either: a) wait 24-36hrs with it on charge b) refresh a rom from a nandroid
I moved to custom roms on day 2 of owning the HOX and was most disappointed to see it happen again. I have come up with this workaround to copy music to the phone:
1. mount as usb drive
2. copy as much data as you like over usb
3. after transfer, right click on the usb icon near the clock (in windows) and eject the usb drive from the computer
4. Without ending usb transfer mode on the phone, reboot it.
bizarrely, this stops the lag phase after music transfer. I've been able to do this 4 times successively now without running into the issue. I have no idea why this is???
zombiefly said:
i am not able to post logs at the moment, but wish to add my experiences to this topic.
Since getting my HOX, i had issues when transferring large amounts of data (music) to the phone. As has been said above, the phone becomes unresponsive, heats up and basically doesn't work until you either: a) wait 24-36hrs with it on charge b) refresh a rom from a nandroid
I moved to custom roms on day 2 of owning the HOX and was most disappointed to see it happen again. I have come up with this workaround to copy music to the phone:
1. mount as usb drive
2. copy as much data as you like over usb
3. after transfer, right click on the usb icon near the clock (in windows) and eject the usb drive from the computer
4. Without ending usb transfer mode on the phone, reboot it.
bizarrely, this stops the lag phase after music transfer. I've been able to do this 4 times successively now without running into the issue. I have no idea why this is???
Click to expand...
Click to collapse
I believe that's what I do when I add my music. And haven't had any lag but also.may not have enough on there.
Also, I have a Nexus 7 and TeamViewer if you want to check anything out with the N7
Sent from my EVO using Xparent SkyBlue Tapatalk 2
i had it only once in the past and it never appeared again
also i have it BIG TIME ON MY N7 although the N7 is in general extremely slow in IO
From the symptoms it looks like TRIM is not working.
With ext4 filesystems we need a mount option "discard" to enable this. Of course it's only really affective if we mount using this every time since a format.
Confirmed, it's exactly the same issue as the "Nexus 7 - issue".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can confirm this issue, when you have <1GB of free space available. I didnt pull up terminal to see how bad the IO was, but the UI was crawling. Almost didnt need to, knew it was this issue.
Ill try and pull a log later...
I've compiled fstrim for Android and packaged it inside APK with nice GUI. You can find LagFix tool here. It is much better then backing up and formatting /data. And A LOT faster too!
Permission Denied in app ._. Lags are still available.. -_- especially while typing or something else...
Gesendet von meinem HTC One X mit Tapatalk 2
One-X-master said:
Permission Denied in app ._. Lags are still available.. -_- especially while typing or something else...
Gesendet von meinem HTC One X mit Tapatalk 2
Click to expand...
Click to collapse
Yes, I'm very sorry for not testing on Sense ROMs. I'll fix Sense issue ASAP, but it will take some time to backup and flash few ROMs.
AuxLV said:
Yes, I'm very sorry for not testing on Sense ROMs. I'll fix Sense issue ASAP, but it will take some time to backup and flash few ROMs.
Click to expand...
Click to collapse
Yes ok thank you not a big deal can wait...it's spot to see that there are such fixes ready
Gesendet von meinem HTC One X mit Tapatalk 2
One-X-master said:
Yes ok thank you not a big deal can wait...it's spot to see that there are such fixes ready
Gesendet von meinem HTC One X mit Tapatalk 2
Click to expand...
Click to collapse
In app thread AlexNone notes that chmod did not work and he pasted log. Do you experience the same issue?
I had the same problem on occasion - 100% IOWAIT and the fix was to factory reset and restore from backup. Usually happened after numerous upgrades of the same ROM (so no full wipe for a while but a lot of IO on /system). I also suspected trim/discard was not working, but I thought our phones didn't have anything like that and suspected filesystem corruption.
I also experienced FS corruption that triggered the same behaviour - fsync and journaling is there for a reason and a popular "tweak" is to disable it - bad, bad, bad for consistency...
Btw I just ran LagFix - worked fine, but I was surprised that a second pass trimmed a lot on /data again - about 50% what the first run did... subsequent runs did nothing as expected. (and it worked on a Sense ROM for me ) EDIT: looks like it didn't work after all? After reboot it just trims again the ~same amount of bytes... (nonsensical on /system)
AuxLV said:
In app thread AlexNone notes that chmod did not work and he pasted log. Do you experience the same issue?
Click to expand...
Click to collapse
The is trying to give permssions in data and then the folder where the files are right? The problem is it is always giving me permission denied because fstrim is not working or so...
Gesendet von meinem HTC One X mit Tapatalk 2
Hey,
My stick has been a PITA lately, slow and sluggish with SPMC.
System Info has the currant free mem dropping to 20-30mb and all I have running and installed is SPMC & Llama.
My surprise was Kodis System Info shows the device as only having 494 RAM! Never thought to check before!
I had to double check this as was sure it shipped with 1GB, Amazon site's specs confirm it.
Can someone with a UK pre-ordered FTVstick confirm this for me, I want to make sure its an issue with SPMC reading it wrong.
My FTVBox with the same SPMC reads it 19xx which would be right for the 2GB it ships with.
Im gonna stick a proper app on it later to see what it reads in case it i a SPMC issue.
TIA
adb shell cat /proc/meminfo
shows:
MemTotal: 506260 kB
MemFree: 13728 kB
Buffers: 11956 kB
Cached: 80888 kB
SwapCached: 0 kB
Active: 383912 kB
Inactive: 50468 kB
adb shell top -m 10
will show you which process uses CPU cycles
Cheers for the command!
Heres my stats:
MemTotal: 506260 kB
MemFree: 20144 kB
Buffers: 7704 kB
Cached: 42768 kB
SwapCached: 0 kB
Active: 413900 kB
Inactive: 24640 kB
Active(anon): 388796 kB
Inactive(anon): 220 kB
Active(file): 25104 kB
Inactive(file): 24420 kB
Unevictable: 684 kB
Mlocked: 0 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 388776 kB
Mapped: 27840 kB
Shmem: 264 kB
Slab: 20008 kB
SReclaimable: 5052 kB
SUnreclaim: 14956 kB
KernelStack: 7864 kB
PageTables: 9200 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 253128 kB
Committed_AS: 4895500 kB
VmallocTotal: 483328 kB
VmallocUsed: 30768 kB
VmallocChunk: 416708 kB
User 1%, System 2%, IOW 0%, IRQ 0%
User 7 + Nice 0 + Sys 16 + Idle 585 + IOW 0 + IRQ 0 + SIRQ 0 = 608
PID PR CPU% S #THR VSS RSS PCY UID Name
2543 1 3% S 57 750496K 193888K bg u0_a1 com.semperpax.spmc
26012 1 0% R 1 1200K 504K shell top
29 0 0% S 1 0K 0K root ksmd
25132 1 0% S 32 498708K 19444K bg u0_a2202 com.amazon.storm.lightning.servic
s
6 0 0% S 1 0K 0K root migration/0
7 1 0% S 1 0K 0K root migration/1
8 1 0% S 1 0K 0K root kworker/1:0
9 1 0% S 1 0K 0K root ksoftirqd/1
10 1 0% S 1 0K 0K root khelper
11 1 0% S 1 0K 0K root netns
And heres my FireTV Box
MemTotal: 1993512 kB
MemFree: 595880 kB
Buffers: 104304 kB
Cached: 741024 kB
SwapCached: 0 kB
Active: 603528 kB
Inactive: 568520 kB
Active(anon): 327784 kB
Inactive(anon): 316 kB
Active(file): 275744 kB
Inactive(file): 568204 kB
This still says to me its only got 512 RAM whereas the FTVBox has 2GB?
Look up dedicated memory and shared memory to get a better explanation. The Fire TV stick shares its memory for graphics and the system. It has 1gb of memory 512mb for the system and 512mb for grapics. This is normal on systems where graphics cards do not have their own dedicated memory, so inside Kodi it will only show system memory.
porkenhimer said:
Look up dedicated memory and shared memory to get a better explanation. The Fire TV stick shares its memory for graphics and the system. It has 1gb of memory 512mb for the system and 512mb for grapics. This is normal on systems where graphics cards do not have their own dedicated memory, so inside Kodi it will only show system memory.
Click to expand...
Click to collapse
Ahh now that makes sense.
I hadn't read that it was shared memory. Cheers for that.
God I wish we had root so I could disable all the Amazon crap. If I hadnt got it for £19 I would've splashed out for the box, it just flies!
Hi, my battery works normally (48 hrs), but if i make a call from Contacts , the battery lasts about 16 hours. If reboot, the problem is solved. I have images but i can't attach them. Thank you.
Wearable-report
Build: M1D64T
Build fingerprint: 'Sony/tetra/tetra:6.0.1/M1D64T/3508863:user/release-keys'
Bootloader: TETRA_Release_118
Radio: BCM23550_14100_04
Network: (unknown)
Kernel: Linux version 3.10.17+ ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Thu Nov 3 17:34:00 CET 2016
------ UPTIME MMC PERF (/sys/block/mmcblk0/) ------
stat: 9856 3958 824554 26170 3360 2445 53441 11030 0 16410 37040
stat: read: 16131KB/s write: 2480KB/s
mmcblk0boot0/stat: 2 0 16 0 0 0 0 0 0 0 0
mmcblk0boot0/stat: read: 0KB/s write: 0KB/s
mmcblk0boot1/stat: 2 0 16 10 0 0 0 0 0 10 10
mmcblk0boot1/stat: read: 819KB/s write: 0KB/s
mmcblk0p24/stat: 54 1770 14592 330 0 0 0 0 0 270 320
mmcblk0p24/stat: read: 22639KB/s write: 0KB/s
mmcblk0p26/stat: 4 3 56 10 0 0 0 0 0 10 10
mmcblk0p26/stat: read: 2867KB/s write: 0KB/s
mmcblk0p30/stat: 24 72 756 0 10 2 96 0 0 0 0
mmcblk0p30/stat: read: 0KB/s write: 0KB/s
mmcblk0p31/stat: 7065 470 597274 18630 0 0 0 0 0 8850 18610
mmcblk0p31/stat: read: 16414KB/s write: 0KB/s
mmcblk0p32/stat: 2699 1643 211796 7200 2880 2443 53345 10970 0 9660 18040
mmcblk0p32/stat: read: 15061KB/s write: 2489KB/s
------ MEMORY INFO (/proc/meminfo) ------
MemTotal: 460620 kB
MemFree: 21148 kB
Buffers: 3456 kB
Cached: 159136 kB
SwapCached: 4 kB
Active: 168824 kB
Inactive: 167808 kB
Active(anon): 88600 kB
Inactive(anon): 88856 kB
Active(file): 80224 kB
Inactive(file): 78952 kB
Unevictable: 1592 kB
Mlocked: 0 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 460620 kB
LowFree: 21148 kB
SwapTotal: 32764 kB
SwapFree: 30552 kB
Dirty: 16 kB
Writeback: 0 kB
AnonPages: 175696 kB
Mapped: 121496 kB
Shmem: 1788 kB
Slab: 25936 kB
SReclaimable: 11508 kB
SUnreclaim: 14428 kB
KernelStack: 5048 kB
PageTables: 10804 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 263072 kB
Committed_AS: 7012588 kB
VmallocTotal: 532480 kB
VmallocUsed: 80148 kB
VmallocChunk: 382980 kB
CmaFree: 12676 kB
CmaA(active): 0 kB
CmaA(inactive): 4 kB
CmaF(active): 16 kB
CmaF(inactive): 0 kB
CmaUnevictable: 0 kB
ContigAlloc: 3688 kB
------ CPU INFO (top -n 1 -d 1 -m 30 -t) ------
User 17%, System 22%, IOW 0%, IRQ 0%
User 37 + Nice 1 + Sys 49 + Idle 132 + IOW 0 + IRQ 0 + SIRQ 0 = 219
PID TID PR CPU% S VSS RSS PCY UID Thread Proc
1701 1701 1 9% R 2372K 932K fg shell top top
91 91 1 6% S 0K 0K fg root irq/411-2-0028
459 538 0 5% R 680248K 71456K fg system PhotonicModulat system_server
121 121 0 4% S 1036K 372K fg root ueventd /sbin/ueventd
459 488 0 3% R 680248K 71456K fg system PowerManagerSer system_server
788 788 0 2% S 401304K 29808K fg u0_a2 earable.ambient com.google.android.wearable.ambient
661 783 0 1% S 514612K 75568K fg u0_a3 SpeechThread com.google.android.wearable.app
157 174 0 1% S 35040K 4156K fg system DispSync /system/bin/surfaceflinger
459 468 0 0% R 680248K 71456K fg system HeapTaskDaemon system_server
157 184 0 0% S 35040K 4156K fg system surfaceflinger /system/bin/surfaceflinger
673 673 0 0% R 437216K 47556K fg u0_a15 rable.watchface com.sonymobile.wearable.watchface
459 478 0 0% S 680248K 71456K fg system Binder_1 system_server
459 863 0 0% S 680248K 71456K fg system Binder_A system_server
24 24 0 0% R 0K 0K fg root kworker/0:1
459 506 0 0% S 680248K 71456K fg system SensorService system_server
157 181 0 0% S 35040K 4156K fg system EventThread /system/bin/surfaceflinger
459 529 0 0% S 680248K 71456K fg system UEventObserver system_server
98 98 0 0% S 0K 0K fg root cfinteractive
160 469 0 0% S 13128K 1324K fg root netd /system/bin/netd
154 154 0 0% S 1700K 176K fg root healthd /sbin/healthd
157 531 0 0% S 35040K 4156K fg system Binder_3 /system/bin/surfaceflinger
25 25 1 0% S 0K 0K fg root kworker/1:1
8 8 1 0% S 0K 0K fg root rcu_preempt
157 173 0 0% S 35040K 4156K fg system Binder_1 /system/bin/surfaceflinger
459 459 0 0% S 680248K 71456K fg system system_server system_server
58 58 1 0% S 0K 0K fg root kswapd0
661 661 0 0% R 514612K 75568K fg u0_a3 id.wearable.app com.google.android.wearable.app
459 861 0 0% S 680248K 71456K fg system Binder_8 system_server
43 43 1 0% S 0K 0K fg root i2c_master_rese
46 46 1 0% S 0K 0K fg root i2c_master_rese
[top: 1.434s elapsed]