Related
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.
[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]
Hey guys!
I'm searching around and I couldn't find a way to root SM-R500 Samsung Galaxy Watch Active (Tizen 4.0.0.3). I found a lot of firmware on different websites, but I couldn't find a rooted one. Any suggestions ...
Thanks
Depend what you expect...
Factory/Service Firmware called Combination Firmware is rooted...
I am using Combination Firmware as base... as Engineer sboot.bin (Bootloader) Engineer Kernel is inside...
From Stock Firmware only rootfs.img is modified... to have su Binary...
Problem...
SM-R500 nor other Galaxy variant tested...
Sugestion for you...
Flash Combination Firmware to see what kind of Root you can expect...
I could help you to modify Firmware Files... but OWN RISK...
Best Regards
adfree said:
Depend what you expect...
Factory/Service Firmware called Combination Firmware is rooted...
I am using Combination Firmware as base... as Engineer sboot.bin (Bootloader) Engineer Kernel is inside...
From Stock Firmware only rootfs.img is modified... to have su Binary...
Problem...
SM-R500 nor other Galaxy variant tested...
Sugestion for you...
Flash Combination Firmware to see what kind of Root you can expect...
I could help you to modify Firmware Files... but OWN RISK...
Best Regards
Click to expand...
Click to collapse
I don’t mind to give it a try. Please share what you have?
Sorry.
I waste tooo much time with Tizen...
I have limited time... and energy...
The long way is here:
https://forum.xda-developers.com/smartwatch/gear-s3/gear-s3-android-wear-port-wip-t3584588
Somewhere inside this Thread are infos how to play with rootfs.img...
The "faster" way for you or both of us... is.
Flash Combination Firmware for SM-R500 to see if this is what you want...
Code:
COMBINATION-FT40_R500XXU1ASA5.tar.md5
COMBINATION-FT40_R500XXU1ASG1.tar.md5
These 2 FT40 seems leaked and available... maybe somewhere in public...
I am too lazy to search for you.
TRy hard enough and in 2 days you can pm me... if you not able to find it...
Maybe I will upload for you...
But again.
What kind of magic you expect from Rooting of your SM-R500?
So I can make decission to help you... or maybe waste my time with other things.
Best Regards
Edit 1.
Code:
COMBINATION-FT40_R500XXU1[B]ASA5[/B].tar.md5
ASA5 I have on my HDD... I could upload...
Edit 2.
Uupsi.. I have both FT40...
Still no idea if somewhere public Link available...
Edit 3...
Lesson 1.
https://forum.xda-developers.com/showpost.php?p=73503787&postcount=150
You "need" netOdin Tool for Flashing Firmware...
I will upload for you:
Code:
COMBINATION-FT40_R500XXU1ASA5.tar.md5
Need some time for upload...
Plese remember:
Own risk!
Best Regards
---------- Post added at 04:28 AM ---------- Previous post was at 03:35 AM ----------
Code:
COMBINATION-FT40_R500XXU1ASA5.tar.md5
https://www.file-upload.net/download-13786815/COMBINATION-FT40_R500XXU1ASA5.tar.md5.7z.html
Own risk!
Best Regards
adfree said:
Sorry.
I waste tooo much time with Tizen...
I have limited time... and energy...
The long way is here:
https://forum.xda-developers.com/smartwatch/gear-s3/gear-s3-android-wear-port-wip-t3584588
Somewhere inside this Thread are infos how to play with rootfs.img...
The "faster" way for you or both of us... is.
Flash Combination Firmware for SM-R500 to see if this is what you want...
Code:
COMBINATION-FT40_R500XXU1ASA5.tar.md5
COMBINATION-FT40_R500XXU1ASG1.tar.md5
These 2 FT40 seems leaked and available... maybe somewhere in public...
I am too lazy to search for you.
TRy hard enough and in 2 days you can pm me... if you not able to find it...
Maybe I will upload for you...
But again.
What kind of magic you expect from Rooting of your SM-R500?
So I can make decission to help you... or maybe waste my time with other things.
Best Regards
Edit 1.
Code:
COMBINATION-FT40_R500XXU1[B]ASA5[/B].tar.md5
ASA5 I have on my HDD... I could upload...
Edit 2.
Uupsi.. I have both FT40...
Still no idea if somewhere public Link available...
Edit 3...
Lesson 1.
https://forum.xda-developers.com/showpost.php?p=73503787&postcount=150
You "need" netOdin Tool for Flashing Firmware...
I will upload for you:
Code:
COMBINATION-FT40_R500XXU1ASA5.tar.md5
Need some time for upload...
Plese remember:
Own risk!
Best Regards
---------- Post added at 04:28 AM ---------- Previous post was at 03:35 AM ----------
Code:
COMBINATION-FT40_R500XXU1ASA5.tar.md5
https://www.file-upload.net/download-13786815/COMBINATION-FT40_R500XXU1ASA5.tar.md5.7z.html
Own risk!
Best Regards
Click to expand...
Click to collapse
Sorry for the late reply and thank you adfree for your effort, but I already have and tested the combination firmware and It is not what I'm looking for! Now I'm trying to figure the pinout so I can connect it directly.
Done first attempt with DSL1 Firmware...
Waiting for feedback...
Meanwhile...
A
To enable Root access... SDB Tool required...
Code:
sdb root on
A.1
To enable su from Shell...
Additional steps required...
Code:
sdb root on
sdb shell
mount -vo remount,rw /
chmod -v +sx /usr/bin
Code:
sdb root off
Then you can su from shell...
Code:
su
then it asks for password... password is:
Code:
tizen
B
To check if you can now play with rootfs.img "on the fly"...
Code:
sdb root on
Or you have enbled the other way...
Code:
sdb shell
Code:
mount -vo remount,rw /
Now you can for instance delete poweron poweroff Animation... you can do more but this is safe... nothing will explode.
Code:
sdb root on
Switched to 'root' account mode
sdb shell
sh-3.2# cd /usr/share/edje
sh-3.2# ls -a1l
total 1280
drwxr-xr-x 5 root root 4096 Jun 27 2019 .
drwxr-xr-x 131 root root 4096 Jun 27 2019 ..
-rw-r--r-- 1 root root 322470 Apr 19 2019 360x360_PowerOff.edj
-rw-r--r-- 1 root root 227171 Apr 19 2019 360x360_PowerOn.edj
-rw-r--r-- 1 root root 6065 Apr 19 2019 csc-ani.edj
-rw-r--r-- 1 root root 6221 Apr 19 2019 factory-reset-util.edj
drwxr-xr-x 2 root root 4096 Jun 27 2019 images
drwxr-xr-x 2 root root 4096 Jun 27 2019 include
-rw-r--r-- 1 root root 295340 Apr 19 2019 poweroff.edj
-rw-r--r-- 1 root root 411726 Apr 19 2019 poweron.edj
-rw-r--r-- 1 root root 5656 Apr 19 2019 voice-control-elm.edj
drwxr-xr-x 2 root root 4096 Jun 27 2019 xwalk
Code:
rm poweron.edj
and/or
Code:
rm poweroff.edj
Be carefully what you remove or replace...
Best Regards
Seems to work... DSL1 rooted... tested in coop with:
Code:
COMBINATION-FT40_R500XXU1[B]ASL2[/B]
For some dump action I need some infos about partition layout...
Code:
[B]cat /proc/partitions[/B]
Example output from SM-Z130H and SM-R760...
Code:
major minor #blocks name
7 0 10052 loop0
7 1 17408 loop1
254 0 146152 zram0
179 0 3817472 mmcblk0
179 1 1024 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 1024 mmcblk0p6
179 7 1024 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 9216 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 2048 mmcblk0p12
179 13 2048 mmcblk0p13
179 14 8192 mmcblk0p14
179 15 8192 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 8192 mmcblk0p17
179 18 8192 mmcblk0p18
179 19 4096 mmcblk0p19
179 20 2048 mmcblk0p20
179 21 32768 mmcblk0p21
179 22 131072 mmcblk0p22
179 23 2641920 mmcblk0p23
179 24 917504 mmcblk0p24
179 96 512 mmcblk0rpmb
179 64 4096 mmcblk0boot1
179 32 4096 mmcblk0boot0
179 128 7749632 mmcblk1
179 129 7748608 mmcblk1p1
Code:
sh-3.2# ls -l /dev/disk/by-partlabel
total 0
lrwxrwxrwx 1 root root 15 Apr 6 09:52 boot -> ../../mmcblk0p8
lrwxrwxrwx 1 root root 15 Apr 6 09:52 cm -> ../../mmcblk0p7
lrwxrwxrwx 1 root root 15 Apr 6 09:52 cpnvcore -> ../../mmcblk0p3
lrwxrwxrwx 1 root root 15 Apr 6 09:52 csa -> ../../mmcblk0p2
lrwxrwxrwx 1 root root 16 Apr 6 09:52 csc -> ../../mmcblk0p11
lrwxrwxrwx 1 root root 16 Apr 6 09:52 module -> ../../mmcblk0p10
lrwxrwxrwx 1 root root 15 Apr 6 09:52 param -> ../../mmcblk0p6
lrwxrwxrwx 1 root root 15 Apr 6 09:52 ramdisk1 -> ../../mmcblk0p5
lrwxrwxrwx 1 root root 15 Apr 6 09:52 ramdisk2 -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 15 Apr 6 09:52 recovery -> ../../mmcblk0p9
lrwxrwxrwx 1 root root 16 Apr 6 09:52 rootfs -> ../../mmcblk0p14
lrwxrwxrwx 1 root root 16 Apr 6 09:52 steady -> ../../mmcblk0p15
lrwxrwxrwx 1 root root 16 Apr 6 09:52 system-data -> ../../mmcblk0p12
lrwxrwxrwx 1 root root 15 Apr 6 09:52 tup -> ../../mmcblk0p1
lrwxrwxrwx 1 root root 16 Apr 6 09:52 user -> ../../mmcblk0p13
Code:
sh-3.2# ls -l /dev/disk/by-label
total 0
lrwxrwxrwx 1 root root 16 Apr 6 09:52 modules -> ../../mmcblk0p10
lrwxrwxrwx 1 root root 10 Apr 6 09:52 ramdisk -> ../../ram0
lrwxrwxrwx 1 root root 15 Apr 6 09:52 ramdisk-recovery -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 16 Apr 6 09:52 rootfs -> ../../mmcblk0p14
lrwxrwxrwx 1 root root 16 Apr 6 09:52 tizen -> ../../mmcblk0p13
Code:
sh-3.2# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 320K 1 loop /opt/share/zoneinfo
loop1 7:1 0 13.6M 1 loop /usr/share/locale
zram0 254:0 0 279.3M 0 disk [SWAP]
mmcblk0rpmb 179:24 0 512K 0 disk
mmcblk0boot0 179:8 0 4M 1 disk
mmcblk0boot1 179:16 0 4M 1 disk
mmcblk0 179:0 0 3.7G 0 disk
|-mmcblk0p1 179:1 0 32M 0 part
|-mmcblk0p2 179:2 0 8M 0 part /csa
|-mmcblk0p3 179:3 0 2M 0 part
|-mmcblk0p4 179:4 0 20M 0 part
|-mmcblk0p5 179:5 0 8M 0 part
|-mmcblk0p6 179:6 0 8M 0 part
|-mmcblk0p7 179:7 0 3M 0 part
|-mmcblk0p8 259:0 0 16M 0 part
|-mmcblk0p9 259:1 0 16M 0 part
|-mmcblk0p10 259:2 0 16M 0 part /usr/lib/modules
|-mmcblk0p11 259:3 0 190M 0 part /opt/system/csc
|-mmcblk0p12 259:4 0 158M 0 part /opt
|-mmcblk0p13 259:5 0 1.9G 0 part /opt/usr
|-mmcblk0p14 259:6 0 1.3G 0 part
| `-rootfs 253:0 0 1.2G 1 crypt /
`-mmcblk0p15 259:7 0 256K 0 part
Thanx in advance.
Best Regards
Here the answer.
Thanx. :good:
SM-R500 DSL1
Code:
sh-3.2# cat /proc/partitions
major minor #blocks name
1 0 20480 ram0
1 1 20480 ram1
7 0 34240 loop0
7 1 384 loop1
254 0 284980 zram0
179 0 3817472 mmcblk0
179 1 8192 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 512 mmcblk0p4
179 5 512 mmcblk0p5
179 6 28160 mmcblk0p6
179 7 20480 mmcblk0p7
259 0 8192 mmcblk0p8
259 1 2048 mmcblk0p9
259 2 6144 mmcblk0p10
259 3 3072 mmcblk0p11
259 4 18432 mmcblk0p12
259 5 18432 mmcblk0p13
259 6 10240 mmcblk0p14
259 7 4096 mmcblk0p15
259 8 194560 mmcblk0p16
259 9 172032 mmcblk0p17
259 10 1873408 mmcblk0p18
259 11 1439744 mmcblk0p19
259 12 256 mmcblk0p20
179 24 512 mmcblk0rpmb
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
Code:
sh-3.2# ls -l /dev/disk/by-partlabel
total 0
lrwxrwxrwx 1 root root 16 Feb 8 11:11 afpc -> ../../mmcblk0p15
lrwxrwxrwx 1 root root 16 Feb 8 11:11 boot -> ../../mmcblk0p12
lrwxrwxrwx 1 root root 16 Feb 8 11:11 cm -> ../../mmcblk0p11
lrwxrwxrwx 1 root root 15 Feb 8 11:11 csa -> ../../mmcblk0p1
lrwxrwxrwx 1 root root 16 Feb 8 11:11 csc -> ../../mmcblk0p16
lrwxrwxrwx 1 root root 15 Feb 8 11:11 module -> ../../mmcblk0p5
lrwxrwxrwx 1 root root 16 Feb 8 11:11 nad_fw -> ../../mmcblk0p14
lrwxrwxrwx 1 root root 15 Feb 8 11:11 nad_refer -> ../../mmcblk0p3
lrwxrwxrwx 1 root root 15 Feb 8 11:11 param -> ../../mmcblk0p9
lrwxrwxrwx 1 root root 15 Feb 8 11:11 ramdisk1 -> ../../mmcblk0p8
lrwxrwxrwx 1 root root 15 Feb 8 11:11 ramdisk2 -> ../../mmcblk0p7
lrwxrwxrwx 1 root root 16 Feb 8 11:11 recovery -> ../../mmcblk0p13
lrwxrwxrwx 1 root root 16 Feb 8 11:11 rootfs -> ../../mmcblk0p19
lrwxrwxrwx 1 root root 15 Feb 8 11:11 smsn -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 16 Feb 8 11:11 steady -> ../../mmcblk0p20
lrwxrwxrwx 1 root root 16 Feb 8 11:11 system-data -> ../../mmcblk0p17
lrwxrwxrwx 1 root root 15 Feb 8 11:11 tup -> ../../mmcblk0p6
lrwxrwxrwx 1 root root 15 Feb 8 11:11 tyd -> ../../mmcblk0p2
lrwxrwxrwx 1 root root 16 Feb 8 11:11 up_param -> ../../mmcblk0p10
lrwxrwxrwx 1 root root 16 Feb 8 11:11 user -> ../../mmcblk0p18
Code:
sh-3.2# ls -l /dev/disk/by-label
total 0
lrwxrwxrwx 1 root root 15 Feb 8 11:11 ramdisk -> ../../mmcblk0p8
lrwxrwxrwx 1 root root 15 Feb 8 11:11 ramdisk-recovery -> ../../mmcblk0p7
lrwxrwxrwx 1 root root 16 Feb 8 11:11 tizen-csc -> ../../mmcblk0p16
lrwxrwxrwx 1 root root 16 Feb 8 11:11 tizen-rootfs -> ../../mmcblk0p19
lrwxrwxrwx 1 root root 16 Feb 8 11:11 tizen-system-da -> ../../mmcblk0p17
lrwxrwxrwx 1 root root 16 Feb 8 11:11 tizen-user -> ../../mmcblk0p18
Code:
sh-3.2# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 33.4M 1 loop /usr/share/locale
loop1 7:1 0 384K 1 loop /opt/share/zoneinfo
mmcblk0 179:0 0 3.7G 0 disk
|-mmcblk0p1 179:1 0 8M 0 part /csa
|-mmcblk0p2 179:2 0 2M 0 part
|-mmcblk0p3 179:3 0 1M 0 part
|-mmcblk0p4 179:4 0 512K 0 part
|-mmcblk0p5 179:5 0 512K 0 part
|-mmcblk0p6 179:6 0 27.5M 0 part
|-mmcblk0p7 179:7 0 20M 0 part
|-mmcblk0p8 259:0 0 8M 0 part
|-mmcblk0p9 259:1 0 2M 0 part
|-mmcblk0p10 259:2 0 6M 0 part
|-mmcblk0p11 259:3 0 3M 0 part
|-mmcblk0p12 259:4 0 18M 0 part
|-mmcblk0p13 259:5 0 18M 0 part
|-mmcblk0p14 259:6 0 10M 0 part
|-mmcblk0p15 259:7 0 4M 0 part
|-mmcblk0p16 259:8 0 190M 0 part /opt/system/csc
|-mmcblk0p17 259:9 0 168M 0 part /opt
|-mmcblk0p18 259:10 0 1.8G 0 part /opt/usr
|-mmcblk0p19 259:11 0 1.4G 0 part /
`-mmcblk0p20 259:12 0 256K 0 part
mmcblk0boot0 179:8 0 4M 1 disk
mmcblk0boot1 179:16 0 4M 1 disk
mmcblk0rpmb 179:24 0 512K 0 disk
zram0 254:0 0 278.3M 0 disk [SWAP]
Code:
mmcblk0p1 CSA
mmcblk0p2 TYD
mmcblk0p3 NAD_REFER
mmcblk0p4 SMSN
mmcblk0p5 MODULE
mmcblk0p6 TUP
mmcblk0p7 RAMDISK-RECOVERY
mmcblk0p8 RAMDISK
mmcblk0p9 PARAM
mmcblk0p10 UP_PARAM
mmcblk0p11 CM
mmcblk0p12 BOOT
mmcblk0p13 RECOVERY
mmcblk0p14 NAD_FW
mmcblk0p15 AFPC
mmcblk0p16 CSC
mmcblk0p17 SYSTEM-DATA
mmcblk0p18 USR
mmcblk0p19 ROOTFS
mmcblk0p20 STEADY
mmcblk0boot0 BOOT0
mmcblk0boot1 BOOT1
mmcblk0rpmb RPMB --->protected... NOT readable
mmcblk0 Full 4 GB eMMC
Best Regards
SM-R500 DSL1 summary for dd action... dump partitions... :angel:
We have 20 partitions p1 - p20
+ 3 additional
We are writing to USR partition p18... remember limited space... ca, 1500 MB free
Code:
dd if=/dev/mmcblk0boot0 of=/opt/usr/media/bootloader0.bin
dd if=/dev/mmcblk0boot1 of=/opt/usr/media/bootloader1.bin
[COLOR="Red"][B]dd if=/dev/mmcblk0rpmb of=/opt/usr/media/rpmb.bin[/B][/COLOR]
dd if=/dev/mmcblk0p1 of=/opt/usr/media/csa.bin
dd if=/dev/mmcblk0p2 of=/opt/usr/media/tyd.bin
dd if=/dev/mmcblk0p3 of=/opt/usr/media/nad_refer.bin
dd if=/dev/mmcblk0p4 of=/opt/usr/media/smsn.bin
dd if=/dev/mmcblk0p5 of=/opt/usr/media/module.bin
dd if=/dev/mmcblk0p6 of=/opt/usr/media/tup.bin
dd if=/dev/mmcblk0p7 of=/opt/usr/media/ramdisk-recovery.bin
dd if=/dev/mmcblk0p8 of=/opt/usr/media/ramdisk.bin
dd if=/dev/mmcblk0p9 of=/opt/usr/media/param.bin
dd if=/dev/mmcblk0p10 of=/opt/usr/media/up_param.bin
dd if=/dev/mmcblk0p11 of=/opt/usr/media/cm.bin
dd if=/dev/mmcblk0p12 of=/opt/usr/media/boot.bin
dd if=/dev/mmcblk0p13 of=/opt/usr/media/recovery.bin
dd if=/dev/mmcblk0p14 of=/opt/usr/media/nad_fw.bin
dd if=/dev/mmcblk0p15 of=/opt/usr/media/afpc.bin
dd if=/dev/mmcblk0p16 of=/opt/usr/media/csc.bin
dd if=/dev/mmcblk0p17 of=/opt/usr/media/system-data.bin
[COLOR="Red"][B]dd if=/dev/mmcblk0p18 of=/opt/usr/media/usr.bin[/B][/COLOR]
[COLOR="Red"][B]dd if=/dev/mmcblk0p19 of=/opt/usr/media/rootfs.bin[/B][/COLOR]
dd if=/dev/mmcblk0p20 of=/opt/usr/media/steady.bin
Red marked Commands...
rootfs to dump is not really usefull... remember free space...
usr is written to usr partition... so never possible to dump in 1 step...
rpmb read protected,,, found no way on Wearables...
To pull all files from Media folder...
Code:
sdb pull /opt/usr/media/
Or pull file by file with filename... example:
Code:
sdb pull /opt/usr/media/[B]csa.bin[/B]
Best Regards
To dump "whole" eMMC...
Limitation we have only maximum 1,8 GB... so we have tiny problem to put whole 4 GB...
To check free space...
Example taken from my SM-R760...
Code:
sh-3.2# df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 1.3G 1.1G 200M 84% /
devtmpfs 340M 0 340M 0% /dev
/dev/mmcblk0p14 1.3G 1.1G 200M 84% /
/dev/mmcblk0p12 139M 85M 51M 63% /opt
/dev/mmcblk0p10 14M 253K 13M 2% /usr/lib/modules
tmpfs 352M 24K 352M 1% /dev/shm
tmpfs 352M 2.6M 349M 1% /run
tmpfs 352M 0 352M 0% /sys/fs/cgroup
tmpfs 352M 60K 352M 1% /tmp
/dev/loop0 384K 384K 0 100% /opt/share/zoneinfo
/dev/loop1 34M 34M 0 100% /usr/share/locale
/dev/mmcblk0p11 183M 101M 80M 56% /opt/system/csc
/dev/mmcblk0p2 6.8M 1.2M 5.0M 20% /csa
/dev/mmcblk0p13 1.9G 120M 1.8G 7% /opt/usr
tmpfs 71M 80K 71M 1% /run/user/5001
tmpfs 71M 0 71M 0% /run/user_ext/5001
/dev/mmcblk0p13 1.9G 120M 1.8G 7% /opt/usr/media
/dev/mmcblk0p13 1.9G 120M 1.8G 7% /opt/usr/apps
/dev/mmcblk0p13 1.9G 120M 1.8G 7% /opt/usr/home/owner/media
/dev/mmcblk0p13 1.9G 120M 1.8G 7% /opt/usr/media
sh-3.2# df -a
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 1298824 1064480 204612 84% /
devtmpfs 347224 0 347224 0% /dev
none 0 0 0 - /proc
sysfs 0 0 0 - /sys
/dev/mmcblk0p14 1298824 1064480 204612 84% /
/dev/mmcblk0p12 141376 86868 51276 63% /opt
/dev/mmcblk0p10 13847 253 13287 2% /usr/lib/modules
securityfs 0 0 0 - /sys/kernel/security
smackfs 0 0 0 - /sys/fs/smackfs
tmpfs 359712 24 359688 1% /dev/shm
devpts 0 0 0 - /dev/pts
tmpfs 359712 2628 357084 1% /run
tmpfs 359712 0 359712 0% /sys/fs/cgroup
cgroup 0 0 0 - /sys/fs/cgroup/systemd
pstore 0 0 0 - /sys/fs/pstore
cgroup 0 0 0 - /sys/fs/cgroup/net_cls
cgroup 0 0 0 - /sys/fs/cgroup/cpu,cpuacct
cgroup 0 0 0 - /sys/fs/cgroup/freezer
cgroup 0 0 0 - /sys/fs/cgroup/memory
debugfs 0 0 0 - /sys/kernel/debug
tmpfs 359712 60 359652 1% /tmp
configfs 0 0 0 - /sys/kernel/config
/dev/loop0 384 384 0 100% /opt/share/zoneinfo
/dev/loop1 34176 34176 0 100% /usr/share/locale
/dev/mmcblk0p11 187373 102462 81020 56% /opt/system/csc
/dev/mmcblk0p2 6907 1218 5117 20% /csa
/dev/mmcblk0p13 1936976 122612 1797980 7% /opt/usr
tmpfs 71940 80 71860 1% /run/user/5001
tmpfs 71940 0 71940 0% /run/user_ext/5001
/dev/mmcblk0p13 1936976 122612 1797980 7% /opt/usr/media
/dev/mmcblk0p13 1936976 122612 1797980 7% /opt/usr/apps
vip_cgroup 0 0 0 - /sys/fs/cgroup/vip
/dev/mmcblk0p13 1936976 122612 1797980 7% /opt/usr/home/owner/media
/dev/mmcblk0p13 1936976 122612 1797980 7% /opt/usr/media
Taken from here:
https://opensource.com/article/18/7/how-check-free-disk-space-linux
First attempt:
Code:
dd if=/dev/mmcblk0 of=/opt/usr/media/full4GB_eMMC.bin
dd stopps if usr partition is full...
Could lead to sideeffect...
But could be enough to pull result...
Code:
sh-3.2# dd if=/dev/mmcblk0 of=/opt/usr/media/full4GB_eMMC.bin
dd: writing to `/opt/usr/media/full4GB_eMMC.bin': [COLOR="Red"][B]No space left on device[/B][/COLOR]
3596569+0 records in
3596568+0 records out
1841442816 bytes (1.8 GB) copied, 151.265 s, 12.2 MB/s
Code:
sh-3.2# df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 1.3G 1.1G 200M 84% /
devtmpfs 340M 0 340M 0% /dev
/dev/mmcblk0p14 1.3G 1.1G 200M 84% /
/dev/mmcblk0p12 139M 83M 53M 61% /opt
/dev/mmcblk0p10 14M 253K 13M 2% /usr/lib/modules
tmpfs 352M 24K 352M 1% /dev/shm
tmpfs 352M 2.5M 349M 1% /run
tmpfs 352M 0 352M 0% /sys/fs/cgroup
tmpfs 352M 60K 352M 1% /tmp
/dev/loop0 384K 384K 0 100% /opt/share/zoneinfo
/dev/loop1 34M 34M 0 100% /usr/share/locale
/dev/mmcblk0p11 183M 101M 80M 56% /opt/system/csc
/dev/mmcblk0p2 6.8M 1.2M 5.0M 20% /csa
[COLOR="Red"][B]/dev/mmcblk0p13 1.9G 1.9G 0 100% /opt/usr[/B][/COLOR]
tmpfs 71M 80K 71M 1% /run/user/5001
tmpfs 71M 0 71M 0% /run/user_ext/5001
[COLOR="Red"][B]/dev/mmcblk0p13 1.9G 1.9G 0 100% /opt/usr/media
/dev/mmcblk0p13 1.9G 1.9G 0 100% /opt/usr/apps
/dev/mmcblk0p13 1.9G 1.9G 0 100% /opt/usr/home/owner/media
/dev/mmcblk0p13 1.9G 1.9G 0 100% /opt/usr/media[/B][/COLOR]
Code:
sdb pull /opt/usr/media/full4GB_eMMC.bin
pulled full4GB_eMMC.bin 100% 1756MB
1 file(s) pulled. 0 file(s) skipped.
/opt/usr/media/full4GB_eMMC.bin 552 KB/s (1841442816 bytes in 3255.896s)
Pull seems 1 hour...
Best Regards
Code:
sh-3.2# dd if=/dev/mmcblk0 | gzip > /opt/usr/media/full4GB_eMMC.bin.gz
gzip: stdout: No space left on device
Creates corrupt/unfinished archive file... but have 2200 MB inside... few more as uncompressed...
Better we split... and find other way for user partition...
.
.
.
Best Regards
Maybe found something...
Code:
sdb shell dd if=/dev/mmcblk0boot1>testme11.bin
sdb shell dd if=/dev/mmcblk0boot0>testme11more.bin
sdb shell dd if=/dev/mmcblk0rpmb>testme11moreAA.bin
Now need more time for next attempt...
Code:
sdb shell dd if=/dev/mmcblk0>FULLeMMCoverSDB_WiFi.bin
4 GB !
IMHO 1 - 2 hours...
Best Regards
Rooted SM-R500 DSL1 Firmware is here:
https://forum.xda-developers.com/showpost.php?p=81762345&postcount=838
If Questions... better ask BEFORE...
Best Regards
Hmmm... I don't know why...
But if I direct dump to PC... then additional crap is written...
2 Bytes...
Code:
0D0D
I have Tizen handset... SM-Z130H... with Tizen 2.4...
Here this work as it seems, tested with Command:
Code:
sdb shell dd if=/dev/mmcblk0boot1>Z1_boot1.bin
This partition is ever empty... contains only 00... so IMHO good reference...
But my Z1 is connected via USB cable...
No idea if 0D0D cames because some TCP problem...
Best Regards
With SM-R760 we have luck...
Combination Firmware not mandatory for Tizen 4 Root...
Only RAMDISK taken from Combination Firmware...
Maybe this is also working for SM-R500... need to be tested.
Attached is ramdisk.img from FT40 ASL2 for SM-R500...
Best Regards
I0T said:
Hey guys!
I'm searching around and I couldn't find a way to root SM-R500 Samsung Galaxy Watch Active (Tizen 4.0.0.3). I found a lot of firmware on different websites, but I couldn't find a rooted one. Any suggestions ...
Thanks
Click to expand...
Click to collapse
Hey there! Could you finally root the SM-R500? Is it still alive? Have the same model here... I used to root all Samsung I had but this is my very first watch so I do not want to mess it yet without anyone proofs
Your Firmware Version?
I have only rooted DSL1 for SM-R500...
Best Regards
adfree said:
Your Firmware Version?
I have only rooted DSL1 for SM-R500...
Best Regards
Click to expand...
Click to collapse
Hi adfree, It seems DSL1, lastest Samsung update.. I have read about combination firmwares etc.. but not tired anything without being sure cause is the most expensive watch i ever bought..
The most combinations firms seems for others than R500, I don't know either about knox on watch if will be tripped too and will left samsung pay useless or it works different than phones..
Yesterday I downloaded all tizen SDK tools etc... and sideloaded tpk apps to watch, they install but could not run them propperly.. but I guess all this is about to test yet as it is a "new watch" ...sorry my ignorance but I come from a LG watch from 2015 omg I had to update myself... xD
Thank you and have a nice day !
@Albayeah
Sorry.
In main I am talking with my self... about Rooting...
No idea why user not confirm in public...
I know he used the old method with Combination Firmware first... then my rooted rootfs,img...
The new way... is to flash only RAMDISK from Combination Firmware, then my rooted files.
So Round 1:
with netOdin
https://forum.xda-developers.com/showpost.php?p=81799723&postcount=15
Round 2.
with netOdin
IGNORE the Combination Firmware files
https://forum.xda-developers.com/showpost.php?p=81762345&postcount=838
Only this:
https://www.file-upload.net/download-13891175/2020_DSL1_smR500_ROOT_v1.7z.html
Own Risk!
But I am 99,9 % sure this is working. :angel:
Best Regards
adfree said:
@Albayeah
Sorry.
In main I am talking with my self... about Rooting...
No idea why user not confirm in public...
I know he used the old method with Combination Firmware first... then my rooted rootfs,img...
The new way... is to flash only RAMDISK from Combination Firmware, then my rooted files.
So Round 1:
with netOdin
https://forum.xda-developers.com/showpost.php?p=81799723&postcount=15
Round 2.
with netOdin
IGNORE the Combination Firmware files
https://forum.xda-developers.com/showpost.php?p=81762345&postcount=838
Only this:
https://www.file-upload.net/download-13891175/2020_DSL1_smR500_ROOT_v1.7z.html
Own Risk!
But I am 99,9 % sure this is working. :angel:
Best Regards
Click to expand...
Click to collapse
Many thanks! I am going to save your files by the moment because I am still afraid of messing something definetly on the watch with no reverse..
Maybe I have to do more research..
I hope I dont bother you with my questions but if you already rooted.. could you use samsung apps as usual..? Like samsung health, samsung pay.. won't prompt a security message or disable any functions, any apps..?
Sorry cause i am kinda confused with that details..
On phone I use Samsung apps hiding with magisk etc... cause it is rooted but it is Android, but what about watch with tizen and no magisk..? Will disable the apps just like in the phone, or is it knox unrecoverable? :silly:
Sorry for my inexperience maybe all this sounded silly to you XDD
Best wishes to all on these hard times :good: