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.
Hi everybody,
After (to my knowledge) succesfully unlocking bootloader using Hasoon2000's Kit I used steps 1 to 8 (using http://forum.xda-developers.com/showthread.php?t=1598964) for the PrimoU to Root my phone. Then I installed CWM and make a backup of the build that I was using on my SDCARD.
LOG:
Code:
Starting recovery on Mon Aug 27 21:23:09 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 800)
ioctl(): blank: Invalid argument
ioctl(): blank: Invalid argument
ClockworkMod Recovery v5.8.3.1
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p22 (null) 0
2 /cache ext4 /dev/block/mmcblk0p28 (null) 0
3 /data ext4 /dev/block/mmcblk0p26 (null) 0
4 /misc emmc /dev/block/mmcblk0p17 (null) 0
5 /recovery emmc /dev/block/mmcblk0p21 (null) 0
6 /sdcard vfat /dev/block/mmcblk1p1 (null) 0
7 /system ext4 /dev/block/mmcblk0p25 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=GINGERBREAD
ro.build.display.id=cyanogen_primou-eng 2.3.7 GINGERBREAD eng.vivek.20120505.222219 test-keys
ro.build.version.incremental=eng.vivek.20120505.222219
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Sat May 5 22:22:37 IST 2012
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=vivek
ro.build.host=ubuntu
ro.build.tags=test-keys
ro.product.model=Full Android on Emulator
ro.product.brand=Android
ro.product.name=cyanogen_primou
ro.product.device=primou
ro.product.board=primou
ro.product.cpu.abi=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=unknown
ro.build.product=primou
ro.build.description=cyanogen_primou-eng 2.3.7 GINGERBREAD eng.vivek.20120505.222219 test-keys
ro.build.fingerprint=Android/cyanogen_primou/primou:2.3.7/GINGERBREAD/eng.vivek.20120505.222219:eng/test-keys
ro.cm.device=primou
keyguard.no_require_sim=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=HT23YTV21132
ro.bootmode=offmode_charging
ro.baseband=3831.17.00.18_M
ro.carrier=HTC-Dutch
ro.bootloader=1.17.0000
ro.hardware=primou
ro.revision=2
ro.emmc=1
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
fd: 10
ev: 1 114 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 115 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 115 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 116 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 116 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 114 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 115 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 115 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 115 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 115 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 115 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 115 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 115 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 115 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 115 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 115 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 115 1
fd: 10
ev: 0 0 0
fd: 10
ev: 1 115 0
fd: 10
ev: 0 0 0
fd: 10
ev: 1 116 1
fd: 10
ev: 0 0 0
After this I wanted to install CM9 or CM10 on my phone. Basically what I did is boot in bootloader->fastboot and I flashed the correct kernel supplied with the CM thread.
Code:
C:\HTCOneV\data>adb kill-server
C:\HTCOneV\data>adb remount
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\HTCOneV\data>adb push Kernels/Modules/system /system
error: device not found
C:\HTCOneV\data>adb reboot bootloader
error: device not found
C:\HTCOneV\data>fastboot flash boot Kernels/boot.img
sending 'boot' (2800 KB)... OKAY [ 2.177s]
writing 'boot'... OKAY [ 1.444s]
finished. total time: 3.621s
C:\HTCOneV\data>fastboot reboot
rebooting...
finished. total time: 0.217s
Then I rebooted into recovery, I followed the steps and now what happens is that each time I reboot my phone I get the HTC Screen with the red text (Developer blablabla) then a few seconds of the CM animation and after that the phone just freezes. I can use the power button to restart and +voldown to get into the CWM/bootloader but thats it.
I tried to use the recovery to get back, but while using that I get the same thing, the HTC Screen with the red text (Developer blabla) then a few seconds of the HTC 'brilliance' animation, but then it also freezes.
I did something wrong, but what? I would like to try another kernel like the KISS one, but would it work with the CM-ROM or would I have to pick another ROM instead? (and if so; could you appoint me one?)
Last; if I would go back to a stock rom; I wouldnt know which one to chose. What if my battery runs out, is it actually charging when hooked to my pc? Help! :crying:
Kind Regards,
Aphromode
Information about my BOOT:
*** UNLOCKED ***
PRIMOU PVT SHIP S-ON RL
HBOOT-1.17.0000
RADIO-3831.17.00.18_M
eMMC-boot
May 15 2012,10:28:15
IMAGE CRC:
osbl: 0x7F9959AF
amss: 0xD1F29E93
hboot: 0xE46C3327
boot: 0x1555E80C2
recovery: 0xC8BBA213
system: 0x2D30BFD9
Just dropped by to say the KISS kernel thread has kernel for CM too and I believe one they provided on CM thread is the same.
Try again maybe? did you wipe /system?
You have to use the KISS kernel. If you are using the latest kiss kernel, the problem might be that your phone can not handle the kernel that is overclocked by default. Try to use the previous version that boots at 1GHz. This issue was reported also by another user.
hlavicka82 said:
You have to use the KISS kernel. If you are using the latest kiss kernel, the problem might be that your phone can not handle the kernel that is overclocked by default. Try to use the previous version that boots at 1GHz. This issue was reported also by another user.
Click to expand...
Click to collapse
The Issue has been resolved, indeed it was the default overclocking that lead to the freezing.
Solution: Use the 1GHz kernel instead of the overclocked one.
[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!