Database Info

NeedHelp:screwed up my g1,cant finished boot

It just loop on the green sparkling robot.
What I did is just modifying TC5-RC8 update.zip with test key, and do the update as normal.
I've been using RC8 for couple days since it's been released and no problem.
After this problem occurd, I've tried to re-flash it to the origianl TC5-RC8 update.zip which released by JesusFreke. BUT the problem still.
My guess is flash recovery.img when booting due to some hardware issues.
Need Your Help.

I finally do a update to and old version of my modified TC5-RC8, the phone booted.
The bad news is I do recovered it to factory mode, so I need to login to Google account again.
Unfortunately, when I finished the Login, and ready to press "Finish setup" and move(dont know how to express in English that movement, the screen is open, what I do is close it so it covers the keyboard) the the screen, and exception occured: "com.google.process.gapps has stopped..."
Don't know whether google will check its own sign or not, im using the test key.
And, I can do adb shell, this is the ps:
# ps
ps
USER PID PPID VSIZE RSS WCHAN PC NAME
root 1 0 264 176 c00a5cd0 0000c36c S /init
root 2 0 0 0 c005bd28 00000000 S kthreadd
root 3 2 0 0 c004c12c 00000000 S ksoftirqd/0
root 4 2 0 0 c006e978 00000000 S watchdog/0
root 5 2 0 0 c0058b40 00000000 S events/0
root 6 2 0 0 c0058b40 00000000 S khelper
root 7 2 0 0 c0182558 00000000 S suspend/0
root 8 2 0 0 c0058b40 00000000 S kblockd/0
root 9 2 0 0 c0058b40 00000000 S kmmcd
root 10 2 0 0 c0058b40 00000000 S btaddconn
root 11 2 0 0 c0058b40 00000000 S btdelconn
root 12 2 0 0 c0058b40 00000000 S qmi
root 13 2 0 0 c003263c 00000000 D rpcrouter
root 14 2 0 0 c0058b40 00000000 S detection/0
root 15 2 0 0 c0032fb4 00000000 S krpcserversd
root 16 2 0 0 c007a964 00000000 S pdflush
root 17 2 0 0 c007a964 00000000 S pdflush
root 18 2 0 0 c007e8b4 00000000 S kswapd0
root 19 2 0 0 c0058b40 00000000 S aio/0
root 20 2 0 0 c0032fb4 00000000 S kadspd
root 21 2 0 0 c0058b40 00000000 S panel_on/0
root 22 2 0 0 c0151ff8 00000000 S mtdblockd
root 23 2 0 0 c0157d84 00000000 S USB mass_storag
root 24 2 0 0 c0058b40 00000000 S synaptics_wq
root 25 2 0 0 c020dfc0 00000000 S krfcommd
system 26 1 796 276 c0189f10 afe0b74c S /system/bin/servicemanager
root 27 1 1828 336 ffffffff afe0b50c S /system/bin/mountd
root 28 1 652 252 c0196e68 afe0c0bc S /system/bin/debuggerd
radio 29 1 7720 936 ffffffff afe0bdbc S /system/bin/rild
media 31 1 17304 3420 ffffffff afe0b74c S /system/bin/mediaserver
bluetooth 33 1 1164 716 c00a5cd0 afe0c69c S /system/bin/dbus-daemon
root 34 1 788 292 c01fb090 afe0b50c S /system/bin/installd
compass 36 1 1304 572 c0169014 afe0b74c S /system/bin/akmd
root 37 1 3324 148 ffffffff 0000e664 S /sbin/adbd
root 43 2 0 0 c01751d0 00000000 S mmcqd
root 359 1 66044 19428 c00a62ec afe0b874 S zygote
system 360 359 183032 25080 ffffffff afe0b74c S system_server
radio 392 359 106732 18708 ffffffff afe0c824 S com.android.phone
app_11 409 359 88092 12244 ffffffff afe0c824 S com.android.mms
app_4 430 359 87436 10576 ffffffff afe0c824 S com.google.android.talk
app_12 441 359 87988 11940 ffffffff afe0c824 S android.process.media
app_14 444 359 90068 11992 ffffffff afe0c824 S android.process.acore
app_18 463 359 93428 14788 ffffffff afe0c824 S com.android.calendar
app_22 475 359 87120 11456 ffffffff afe0c824 S com.android.alarmclock
app_16 487 359 87472 11300 ffffffff afe0c824 S com.google.android.gm
app_8 582 359 106360 15604 ffffffff afe0c824 S com.android.setupwizard
app_0 608 359 94940 15916 ffffffff afe0c824 S com.google.process.gapps
root 645 2 0 0 c0032dc8 00000000 D audmgr_rpc
root 687 37 724 320 c0049a2c afe0c4cc S /system/bin/sh
root 689 687 868 328 00000000 afe0b50c R ps
#
Click to expand...
Click to collapse

I do it again, said "The setup wizzard stopped unexpectly"

[Q] [Verified Android Trojan] Unknown app sends hidden sms to +493394991625

Hi,
After downloading dozens of apps from appbrain last night
I've noticed an unknown app sending a sms to +493394991625
30.7.2011 1 : 25 : 59 493394991625 1,00Stk. 1,00Stk. 0,20 EUR
from my htc wildfire S A510e in my service providers logs last night.
and looks like it's hiding and wiping traces by disabling storing sent sms messages and other notification settings.
Furthermore I noticed disabled Lookout security app update setting,
I've installed a bunch of popular malware detectors, let's see who wins...
Code:
$ ps
USER PID PPID VSIZE RSS WCHAN PC NAME
root 1 0 388 240 ffffffff 00000000 S /init
root 2 0 0 0 ffffffff 00000000 S kthreadd
root 3 2 0 0 ffffffff 00000000 S ksoftirqd/0
root 4 2 0 0 ffffffff 00000000 S watchdog/0
root 5 2 0 0 ffffffff 00000000 S events/0
root 6 2 0 0 ffffffff 00000000 S khelper
root 7 2 0 0 ffffffff 00000000 S async/mgr
root 8 2 0 0 ffffffff 00000000 S suspend
root 9 2 0 0 ffffffff 00000000 S sync_supers
root 10 2 0 0 ffffffff 00000000 S bdi-default
root 11 2 0 0 ffffffff 00000000 S kblockd/0
root 12 2 0 0 ffffffff 00000000 S kmmcd
root 13 2 0 0 ffffffff 00000000 S kondemand/0
root 14 2 0 0 ffffffff 00000000 S smd_tty
root 15 2 0 0 ffffffff 00000000 D rpcrouter
root 16 2 0 0 ffffffff 00000000 S krpcserversd
root 17 2 0 0 ffffffff 00000000 S qmi
root 18 2 0 0 ffffffff 00000000 S kadspd
root 19 2 0 0 ffffffff 00000000 S microp_work_q
root 20 2 0 0 ffffffff 00000000 S detect/0
root 21 2 0 0 ffffffff 00000000 S button/0
root 22 2 0 0 ffffffff 00000000 S detect/0
root 23 2 0 0 ffffffff 00000000 S button/0
root 24 2 0 0 ffffffff 00000000 S HS_GPIO_DETECT/
root 25 2 0 0 ffffffff 00000000 S HS_GPIO_BUTTON/
root 26 2 0 0 ffffffff 00000000 S khungtaskd
root 27 2 0 0 ffffffff 00000000 S kswapd0
root 28 2 0 0 ffffffff 00000000 S aio/0
root 29 2 0 0 ffffffff 00000000 S crypto/0
root 40 2 0 0 ffffffff 00000000 S panel_on/0
root 41 2 0 0 ffffffff 00000000 S diag_wq
root 42 2 0 0 ffffffff 00000000 S msm_serial_hs
root 43 2 0 0 ffffffff 00000000 S msm_serial_hs
root 44 2 0 0 ffffffff 00000000 S msm_serial_hs
root 45 2 0 0 ffffffff 00000000 S mtdblockd
root 52 2 0 0 ffffffff 00000000 S msm_hsusb
root 53 2 0 0 ffffffff 00000000 S usb_mass_storag
root 54 2 0 0 ffffffff 00000000 S gs_tty
root 55 2 0 0 ffffffff 00000000 S cypress_touch
root 56 2 0 0 ffffffff 00000000 S synaptics_wq
root 57 2 0 0 ffffffff 00000000 S ki_queue
root 58 2 0 0 ffffffff 00000000 S cm3628_wq
root 59 2 0 0 ffffffff 00000000 S kstriped
root 60 2 0 0 ffffffff 00000000 S binder
root 61 2 0 0 ffffffff 00000000 S l2cap
root 62 2 0 0 ffffffff 00000000 S krfcommd
root 63 1 300 140 ffffffff 00000000 S /sbin/ueventd
system 65 1 856 160 ffffffff 00000000 S /system/bin/servicemanager
root 66 2 0 0 ffffffff 00000000 S sd-qd
root 67 1 3940 348 ffffffff 00000000 S /system/bin/vold
root 68 1 3952 288 ffffffff 00000000 S /system/bin/netd
root 69 1 3260 216 ffffffff 00000000 S /system/bin/debuggerd
radio 70 1 14240 560 ffffffff 00000000 S /system/bin/rild
root 71 1 98644 22776 ffffffff 00000000 S zygote
media 72 1 44440 3164 ffffffff 00000000 S /system/bin/mediaserver
root 73 1 12344 780 ffffffff 00000000 S /system/bin/htcfs
bluetooth 74 1 1312 168 ffffffff 00000000 S /system/bin/dbus-daemon
root 75 1 880 268 ffffffff 00000000 S /system/bin/installd
keystore 76 1 1824 184 ffffffff 00000000 S /system/bin/keystore
root 77 1 840 148 ffffffff 00000000 S /system/bin/ipd
compass 79 1 3180 300 ffffffff 00000000 S /system/bin/akmd
root 81 1 1100 288 ffffffff 00000000 S /system/bin/htc_ebdlogd
root 87 81 2152 1664 ffffffff 00000000 S /system/bin/logcat2
root 116 2 0 0 ffffffff 00000000 D snd_rpc
system 118 71 246828 38828 ffffffff 00000000 S system_server
root 140 2 0 0 ffffffff 00000000 D audmgr_rpc
system 187 71 143140 26508 ffffffff 00000000 S com.android.systemui
app_11 209 71 131368 20700 ffffffff 00000000 S com.htc.android.htcime
radio 216 71 155760 26148 ffffffff 00000000 S com.android.phone
app_21 221 71 248620 51508 ffffffff 00000000 S android.process.acore
app_17 245 71 187440 24360 ffffffff 00000000 S com.google.process.gapps
root 431 2 0 0 ffffffff 00000000 S flush-0:17
root 552 2 0 0 ffffffff 00000000 S flush-179:0
root 803 2 0 0 ffffffff 00000000 D audmgr_rpc
app_126 981 1 5368 376 ffffffff 00000000 S ./smrsd
app_126 983 981 2140 1664 ffffffff 00000000 S /system/bin/logcat
root 1487 2 0 0 ffffffff 00000000 S flush-31:0
app_72 2482 71 113872 15820 ffffffff 00000000 S org.sipdroid.sipua
app_6 2534 71 193320 31532 ffffffff 00000000 S com.android.vending
app_101 2586 1 944 472 ffffffff 00000000 S logcat
app_86 3159 71 169616 20608 ffffffff 00000000 S com.lookout
app_101 3167 71 128972 18376 ffffffff 00000000 S com.antivirus
app_101 3203 3167 944 468 ffffffff 00000000 S logcat
app_86 3341 3159 1888 1412 ffffffff 00000000 S logcat
app_7 3404 71 147256 17180 ffffffff 00000000 S android.process.media
nobody 3635 71 146292 33480 ffffffff 00000000 S com.htc.launcher
app_21 3738 71 129612 20424 ffffffff 00000000 S com.android.htccontacts
app_52 3861 71 126588 16900 ffffffff 00000000 S com.android.mms
app_40 4468 71 127588 16696 ffffffff 00000000 S com.htc.cspeoplesync
app_121 4617 71 108112 14208 ffffffff 00000000 S com.zrgiu.antivirus
app_47 4631 71 107632 13392 ffffffff 00000000 S com.htc.wotaproviders
system 4784 71 107632 12704 ffffffff 00000000 S com.android.server.vpn:remote
app_122 4833 71 108588 14044 ffffffff 00000000 S com.netqin.antivirussc
app_130 4846 71 111336 15288 ffffffff 00000000 S com.trustmobi.MobiShield
app_12 4859 71 117108 22404 ffffffff 00000000 S com.htc.bgp
app_124 5059 71 111520 15684 ffffffff 00000000 S com.zoner.android.antivirus
app_27 5268 71 119504 15020 ffffffff 00000000 S com.google.android.googlequicksearchbox
app_58 5277 71 133176 20560 ffffffff 00000000 S com.htc.lmw
root 5317 2 0 0 ffffffff 00000000 S flush-7:8
root 5319 2 0 0 ffffffff 00000000 S loop8
root 5320 2 0 0 ffffffff 00000000 S kdmflush
root 5321 2 0 0 ffffffff 00000000 S kcryptd_io
root 5322 2 0 0 ffffffff 00000000 S kcryptd
root 5345 2 0 0 ffffffff 00000000 S flush-7:9
root 5348 2 0 0 ffffffff 00000000 S loop9
root 5349 2 0 0 ffffffff 00000000 S kdmflush
root 5350 2 0 0 ffffffff 00000000 S kcryptd_io
root 5351 2 0 0 ffffffff 00000000 S kcryptd
root 5373 2 0 0 ffffffff 00000000 S flush-7:10
root 5376 2 0 0 ffffffff 00000000 S loop10
root 5377 2 0 0 ffffffff 00000000 S kdmflush
root 5378 2 0 0 ffffffff 00000000 S kcryptd_io
root 5379 2 0 0 ffffffff 00000000 S kcryptd
root 5397 2 0 0 ffffffff 00000000 S flush-7:11
root 5401 2 0 0 ffffffff 00000000 S loop11
root 5402 2 0 0 ffffffff 00000000 S kdmflush
root 5403 2 0 0 ffffffff 00000000 S kcryptd_io
root 5404 2 0 0 ffffffff 00000000 S kcryptd
root 5421 2 0 0 ffffffff 00000000 S flush-7:12
root 5424 2 0 0 ffffffff 00000000 S loop12
root 5425 2 0 0 ffffffff 00000000 S kdmflush
root 5426 2 0 0 ffffffff 00000000 S kcryptd_io
root 5427 2 0 0 ffffffff 00000000 S kcryptd
root 5445 2 0 0 ffffffff 00000000 S flush-7:13
root 5448 2 0 0 ffffffff 00000000 S loop13
root 5449 2 0 0 ffffffff 00000000 S kdmflush
root 5450 2 0 0 ffffffff 00000000 S kcryptd_io
root 5451 2 0 0 ffffffff 00000000 S kcryptd
root 5466 2 0 0 ffffffff 00000000 S flush-7:14
root 5472 2 0 0 ffffffff 00000000 S loop14
root 5473 2 0 0 ffffffff 00000000 S kdmflush
root 5474 2 0 0 ffffffff 00000000 S kcryptd_io
root 5475 2 0 0 ffffffff 00000000 S kcryptd
app_63 5483 71 118580 20480 ffffffff 00000000 S com.google.android.gm
root 5501 2 0 0 ffffffff 00000000 S flush-7:15
root 5508 2 0 0 ffffffff 00000000 S loop15
root 5509 2 0 0 ffffffff 00000000 S kdmflush
root 5510 2 0 0 ffffffff 00000000 S kcryptd_io
root 5511 2 0 0 ffffffff 00000000 S kcryptd
root 5527 2 0 0 ffffffff 00000000 S flush-7:16
root 5539 2 0 0 ffffffff 00000000 S loop16
root 5540 2 0 0 ffffffff 00000000 S kdmflush
root 5541 2 0 0 ffffffff 00000000 S kcryptd_io
root 5542 2 0 0 ffffffff 00000000 S kcryptd
root 5550 2 0 0 ffffffff 00000000 S flush-7:17
root 5562 2 0 0 ffffffff 00000000 S loop17
root 5563 2 0 0 ffffffff 00000000 S kdmflush
root 5564 2 0 0 ffffffff 00000000 S kcryptd_io
root 5565 2 0 0 ffffffff 00000000 S kcryptd
app_56 5579 71 174784 28264 ffffffff 00000000 S com.htc.cs
root 5587 2 0 0 ffffffff 00000000 S flush-7:18
root 5603 2 0 0 ffffffff 00000000 S loop18
root 5604 2 0 0 ffffffff 00000000 S kdmflush
root 5605 2 0 0 ffffffff 00000000 S kcryptd_io
root 5606 2 0 0 ffffffff 00000000 S kcryptd
root 5650 2 0 0 ffffffff 00000000 S flush-7:19
root 5656 2 0 0 ffffffff 00000000 S loop19
root 5657 2 0 0 ffffffff 00000000 S kdmflush
root 5658 2 0 0 ffffffff 00000000 S kcryptd_io
root 5659 2 0 0 ffffffff 00000000 S kcryptd
root 5708 2 0 0 ffffffff 00000000 S flush-7:20
root 5712 2 0 0 ffffffff 00000000 S loop20
root 5713 2 0 0 ffffffff 00000000 S kdmflush
root 5714 2 0 0 ffffffff 00000000 S kcryptd_io
root 5715 2 0 0 ffffffff 00000000 S kcryptd
app_59 5856 71 109988 16604 ffffffff 00000000 S com.htc.recommend
root 5916 2 0 0 ffffffff 00000000 S flush-7:21
root 5919 2 0 0 ffffffff 00000000 S loop21
root 5920 2 0 0 ffffffff 00000000 S kdmflush
root 5921 2 0 0 ffffffff 00000000 S kcryptd_io
root 5922 2 0 0 ffffffff 00000000 S kcryptd
app_16 5993 71 107696 14992 ffffffff 00000000 S com.htc.htchubsyncprovider
app_20 6014 71 107808 16072 ffffffff 00000000 S com.htc.messagecs
app_28 6021 71 107924 16172 ffffffff 00000000 S com.htc.musicmarkeditems
app_128 6026 71 109936 15720 ffffffff 00000000 S com.opensystem.terminator
app_11 6044 71 136420 17812 ffffffff 00000000 S com.htc.android.htcime:provider
app_120 6091 71 109956 16904 ffffffff 00000000 S com.drweb:monitor
app_67 6117 71 122120 19548 ffffffff 00000000 S com.google.android.apps.maps:NetworkLocationService
app_12 6137 71 113356 18940 ffffffff 00000000 S com.htc.bg
app_138 6145 71 114012 20244 ffffffff 00000000 S com.mymobileprotection15
app_79 6164 71 109788 15888 ffffffff afd0c64c S br.com.bott.droidsshd
app_76 6177 71 121940 21804 ffffffff 00000000 S com.wefi.wefi
system 6235 71 113144 17280 ffffffff 00000000 S com.android.settings
app_79 6251 6465 1212 496 c00f98cc 00063324 S /data/data/br.com.bott.droidsshd/files/bin/dropbear
app_79 6252 6251 728 316 c0083920 afd0c4dc S -sh
app_79 6259 6252 876 300 00000000 afd0b58c R ps
app_79 6465 1 1212 180 c00f98cc 00063324 S /data/data/br.com.bott.droidsshd/files/bin/dropbear
root 9575 2 0 0 ffffffff 00000000 S flush-7:0
root 9581 2 0 0 ffffffff 00000000 S loop0
root 9582 2 0 0 ffffffff 00000000 S kdmflush
root 9583 2 0 0 ffffffff 00000000 S kcryptd_io
root 9584 2 0 0 ffffffff 00000000 S kcryptd
root 10019 2 0 0 ffffffff 00000000 S flush-7:1
root 10025 2 0 0 ffffffff 00000000 S loop1
root 10026 2 0 0 ffffffff 00000000 S kdmflush
root 10027 2 0 0 ffffffff 00000000 S kcryptd_io
root 10028 2 0 0 ffffffff 00000000 S kcryptd
root 10179 2 0 0 ffffffff 00000000 S flush-7:2
root 10185 2 0 0 ffffffff 00000000 S loop2
root 10186 2 0 0 ffffffff 00000000 S kdmflush
root 10187 2 0 0 ffffffff 00000000 S kcryptd_io
root 10188 2 0 0 ffffffff 00000000 S kcryptd
root 10293 2 0 0 ffffffff 00000000 S flush-7:3
root 10299 2 0 0 ffffffff 00000000 S loop3
root 10300 2 0 0 ffffffff 00000000 S kdmflush
root 10301 2 0 0 ffffffff 00000000 S kcryptd_io
root 10302 2 0 0 ffffffff 00000000 S kcryptd
root 10860 2 0 0 ffffffff 00000000 S flush-7:4
root 10867 2 0 0 ffffffff 00000000 S loop4
root 10868 2 0 0 ffffffff 00000000 S kdmflush
root 10869 2 0 0 ffffffff 00000000 S kcryptd_io
root 10870 2 0 0 ffffffff 00000000 S kcryptd
root 11330 2 0 0 ffffffff 00000000 S flush-7:5
root 11332 2 0 0 ffffffff 00000000 S loop5
root 11333 2 0 0 ffffffff 00000000 S kdmflush
root 11334 2 0 0 ffffffff 00000000 S kcryptd_io
root 11335 2 0 0 ffffffff 00000000 S kcryptd
root 11353 2 0 0 ffffffff 00000000 S flush-7:6
root 11360 2 0 0 ffffffff 00000000 S loop6
root 11361 2 0 0 ffffffff 00000000 S kdmflush
root 11362 2 0 0 ffffffff 00000000 S kcryptd_io
root 11363 2 0 0 ffffffff 00000000 S kcryptd
root 11376 2 0 0 ffffffff 00000000 S flush-7:7
root 11378 2 0 0 ffffffff 00000000 S loop7
root 11379 2 0 0 ffffffff 00000000 S kdmflush
root 11380 2 0 0 ffffffff 00000000 S kcryptd_io
root 11381 2 0 0 ffffffff 00000000 S kcryptd
app_56 13589 71 112512 17840 ffffffff 00000000 S com.htc.cs:remote
app_78 21827 71 117468 16508 ffffffff 00000000 S com.skype.raider
app_78 21917 21827 14616 10268 ffffffff 00000000 S /data/data/com.skype.raider/files/skypekit
root 22015 2 0 0 ffffffff 00000000 S iscan_sysioc
root 22016 2 0 0 ffffffff 00000000 S dhcp_sysioc
root 22017 2 0 0 ffffffff 00000000 S ap_sysioc
root 22018 2 0 0 ffffffff 00000000 S dhd_watchdog
root 22019 2 0 0 ffffffff 00000000 S dhd_dpc
root 22020 2 0 0 ffffffff 00000000 S dhd_sysioc
log 22021 1 708 152 ffffffff 00000000 S /system/bin/logwrapper
wifi 22023 22021 2480 744 ffffffff 00000000 S /system/bin/wpa_supplicant
app_101 24919 1 944 468 ffffffff 00000000 S logcat
app_101 26402 1 944 468 ffffffff 00000000 S logcat
dhcp 29044 1 900 212 ffffffff 00000000 S /system/bin/dhcpcd
app_101 29471 1 944 472 ffffffff 00000000 S logcat
app_123 29948 1 952 444 ffffffff 00000000 S /data/data/jp.ktinc.fastscan/fseng
app_125 31043 71 173488 42988 ffffffff 00000000 S com.morrison.applocklite
app_125 31056 31043 944 472 ffffffff 00000000 S logcat
app_125 31083 31043 944 468 ffffffff 00000000 S logcat
app_126 32496 71 146544 23948 ffffffff 00000000 S com.symantec.mobilesecurity
app_126 32763 32496 1588 1112 ffffffff 00000000 S logcat
$
Code:
Aug 1 15:54:12 freshclam[6026]: main.cvd is up to date (version: 53, sigs: 846214, f-level: 53, builder: sven)
Aug 1 15:54:12 freshclam[6026]: daily.cld is up to date (version: 13385, sigs: 166221, f-level: 60, builder: ccordes)
Aug 1 15:54:12 freshclam[6026]: bytecode.cld is up to date (version: 144, sigs: 41, f-level: 60, builder: edwin)
Code:
$ clamscan -r --bell --detect-pua=yes --heuristic-scan-precedence=yes sdcard16GB-virus
sdcard16GB-virus/google_*****.vcf: OK
sdcard16GB-virus/setup_3.0.5551.exe: OK
sdcard16GB-virus/pcsc_pcsc_00001.vcf: OK
sdcard16GB-virus/Android/data/com.google.android.apps.maps/cache/cache_its.m: OK
sdcard16GB-virus/Android/data/com.google.android.apps.maps/cache/cache_vts_tran_GMM.m: OK
sdcard16GB-virus/Android/data/com.google.android.apps.maps/cache/cache_its_ter.m: OK
sdcard16GB-virus/Android/data/com.google.android.apps.maps/cache/cache_vts_GMM.m: OK
sdcard16GB-virus/Android/data/com.google.android.apps.maps/cache/cache_r.m: OK
sdcard16GB-virus/Android/data/com.google.android.apps.maps/cache/cache_vts_labl_GMM.m: OK
sdcard16GB-virus/Android/data/.nomedia: Empty file
sdcard16GB-virus/svox/en-GB_ta.bin: OK
sdcard16GB-virus/svox/en-US_lh0_sg.bin: OK
sdcard16GB-virus/svox/fr-FR_ta.bin: OK
sdcard16GB-virus/svox/es-ES_zl0_sg.bin: OK
sdcard16GB-virus/svox/fr-FR_nk0_sg.bin: OK
sdcard16GB-virus/svox/it-IT_ta.bin: OK
sdcard16GB-virus/svox/es-ES_ta.bin: OK
sdcard16GB-virus/svox/en-GB_kh0_sg.bin: OK
sdcard16GB-virus/svox/it-IT_cm0_sg.bin: OK
sdcard16GB-virus/svox/en-US_ta.bin: OK
sdcard16GB-virus/svox/de-DE_gl0_sg.bin: OK
sdcard16GB-virus/svox/de-DE_ta.bin: OK
sdcard16GB-virus/download/DroidSSHdv06.apk: OK
sdcard16GB-virus/download/Apps_Installer_0.2.1.apk: OK
sdcard16GB-virus/download/org.mozilla.firefox.apk: OK
sdcard16GB-virus/download/com.wefi.wefi.apk: OK
sdcard16GB-virus/download/com.faststring.fastappinstaller.apk: OK
sdcard16GB-virus/download/de.schildbach.oeffi.apk: OK
sdcard16GB-virus/download/org.mozilla.firefox_beta.apk: OK
sdcard16GB-virus/google_******_00002.vcf: OK
sdcard16GB-virus/Quick Start Guide/20110413_Marvel_HTC_Italian_QSG.pdf: OK
sdcard16GB-virus/Quick Start Guide/20110414_Marvel_HTC_German_QSG.pdf.pdf: OK
sdcard16GB-virus/Quick Start Guide/20110413_Marvel_HTC_French_QSG.pdf: OK
sdcard16GB-virus/*********/Sipdroid-2.3.apk: OK
sdcard16GB-virus/sim_SIM_00001.vcf: OK
sdcard16GB-virus/sim_SIM_00002.vcf: Empty file
sdcard16GB-virus/pcsc_pcsc_00002.vcf: OK
sdcard16GB-virus/Safety Guide/20110406_Marvel_HTC_Italian_Safety-regulatory_guide.pdf: OK
sdcard16GB-virus/Safety Guide/20110325_Marvel_HTC_French_Safety-regulatory_guide.pdf: OK
sdcard16GB-virus/Safety Guide/20110324_Marvel_HTC_German_Safety-regulatory_guide.pdf: OK
sdcard16GB-virus/miren_browser/.cache/CacheList: OK
sdcard16GB-virus/miren_browser/.cache/databases/ApplicationCache.db: OK
sdcard16GB-virus/miren_browser/.cache/geolocation/CachedGeoposition.db: OK
sdcard16GB-virus/miren_browser/.cache/geolocation/GeolocationPermissions.db: Empty file
sdcard16GB-virus/miren_browser/imagecaches/rssIcon/3d87920807b05c46ee34b296fc331cdf.png: OK
sdcard16GB-virus/miren_browser/imagecaches/rssIcon/8a1f63f02b6f44fb91bd197dd5dfdc9e.png: OK
sdcard16GB-virus/miren_browser/imagecaches/rssIcon/a7e4cbd44379085999164a851497a8fa.png: OK
sdcard16GB-virus/miren_browser/imagecaches/rssIcon/39fbd541589b2ec6a36d872e02514412.png: OK
sdcard16GB-virus/miren_browser/imagecaches/rssIcon/3f7f3c517a020bf4836368e24830632f.png: OK
sdcard16GB-virus/miren_browser/.persist/webview_pictures/webview_0: OK
sdcard16GB-virus/DCIM/sample01.jpg: OK
sdcard16GB-virus/DCIM/sample07.jpg: OK
sdcard16GB-virus/DCIM/sample06.jpg: OK
sdcard16GB-virus/DCIM/sample09.jpg: OK
sdcard16GB-virus/DCIM/sample03.jpg: OK
sdcard16GB-virus/DCIM/.thumbnails/4-712AC800-2155097-480.jpg: OK
sdcard16GB-virus/DCIM/.thumbnails/2-9683FC85-3126664-480.jpg: OK
sdcard16GB-virus/DCIM/.thumbnails/2-3C600F01-2699282-480.jpg: OK
sdcard16GB-virus/DCIM/.thumbnails/2-92F65F82-3806217-480.jpg: OK
sdcard16GB-virus/DCIM/.thumbnails/4-4D34F029-7255294-480.jpg: OK
sdcard16GB-virus/DCIM/.thumbnails/2-C1F43D8A-4013455-480.jpg: OK
sdcard16GB-virus/DCIM/.thumbnails/2-58111224-2901259-480.jpg: OK
sdcard16GB-virus/DCIM/.thumbnails/4-9683FC85-3126664-480.jpg: OK
sdcard16GB-virus/DCIM/.thumbnails/4-58111224-2901259-480.jpg: OK
sdcard16GB-virus/DCIM/.thumbnails/2-4D34F029-7255294-480.jpg: OK
sdcard16GB-virus/DCIM/.thumbnails/2-712AC800-2155097-480.jpg: OK
sdcard16GB-virus/DCIM/.thumbnails/2-D37EF1ED-4197534-480.jpg: OK
sdcard16GB-virus/DCIM/.thumbnails/4-D37EF1ED-4197534-480.jpg: OK
sdcard16GB-virus/DCIM/.thumbnails/4-92F65F82-3806217-480.jpg: OK
sdcard16GB-virus/DCIM/.thumbnails/4-C1F43D8A-4013455-480.jpg: OK
sdcard16GB-virus/DCIM/.thumbnails/2-13D94E9B-1919498-480.jpg: OK
sdcard16GB-virus/DCIM/sample05.jpg: OK
sdcard16GB-virus/DCIM/sample04.jpg: OK
sdcard16GB-virus/DCIM/sample02.jpg: OK
sdcard16GB-virus/DCIM/sample08.jpg: OK
sdcard16GB-virus/background.log: OK
sdcard16GB-virus/User Manual/20110413_Marvel_HTC_German_UM.pdf: OK
----------- SCAN SUMMARY -----------
Known viruses: 1012338
Engine version: 0.97
Scanned directories: 38
Scanned files: 74
Infected files: 0
Data scanned: 153.86 MB
Data read: 227.97 MB (ratio 0.67:1)
Time: 79.317 sec (1 m 19 s)
What to do now?

If that app really is a virus then it's very nasty :O
I recon you hard reset your whole phone. Backup your contacts, maybe sms, but not your apps of course, and simply reset your device =/.
This is an example of the ineffectiveness of todays antiviruses for android. They can detect, generally too late, but can't fix anything... Not much of an proper antivirus around for the time being, it's just fancy apps that don't do much and reassure people...

-Deleted Post-

my android trojan desaster recovery continued
crakeron said:
I recon you hard reset your whole phone. Backup your contacts, maybe sms, but not your apps of course, and simply reset your device
Click to expand...
Click to collapse
Not possible, the setup wizard after factory reset + reboot on this marvel HTC Wildfire S requires google + htc sense account access to have the google and htc apps configured and working correctly (there's a warning in the manual not to disable that),
and this will auto-restore all settings and apps to the desaster state far before you get the chance to disable the auto-restore and sync in settings, surely including the trojan,
You notice that behaviour first if you changed your wlan AP key for desaster recovery and a few minutes after setup wizard run your old wlan key is silently restored despite explicitly disabled sync + auto restore settings:
Code:
01.08.11 01:49:00 WLAN-Gerät Anmeldung gescheitert (2,4 GHz): ungültiger WLAN-Schlüssel. Name: htc.
01.08.11 01:48:48 WLAN-Gerät Anmeldung gescheitert (2,4 GHz): ungültiger WLAN-Schlüssel. Name: htc.
01.08.11 01:48:45 WLAN-Gerät angemeldet, WLAN wird mit voller Leistung reaktiviert (2,4 GHz).
01.08.11 01:38:52 Kein WLAN-Gerät mehr angemeldet, Stromverbrauch wird reduziert (2,4 GHz).
01.08.11 01:36:39 WLAN-Gerät Anmeldung gescheitert (2,4 GHz): ungültiger WLAN-Schlüssel. Name: htc.
01.08.11 01:36:28 WLAN-Gerät hat sich abgemeldet (2,4 GHz). Name: htc.
01.08.11 01:27:42 WLAN-Gerät angemeldet (2,4 GHz). Name: htc, Geschwindigkeit 54 Mbit/s.
01.08.11 01:27:42 WLAN-Gerät angemeldet, WLAN wird mit voller Leistung reaktiviert (2,4 GHz).
"ungültiger WLAN-Schlüssel" means invalid EAP-PSK, sorry avm.de is uncapable of english language.
The attackers possibly compromised my AVM fritzbox router, too, they tried to download a malware firmware image to it over the marvel (web management showed warning about failed firmware update yesterday morning) or the newly setup AVM VPN access is insecure , had to factory reset and reinstall the firmware for another desaster recovery,
but I don't know if they managed to have the device memory still compromised using one of the methods known by ip-phone-forum.de to debrand the product, etc.
And well, it's very hard to get a verified clean genuine firmware image file over a possibly compromised and redirecting router from a manufacturer not supporting https certificate auth or crypto signed software on his servers, had to verify sha1sums with another guy over phone before download the image to the box..
Another trojan verification evidence is that the hackers incoming phone/sms account +493394991625 where the sms was sent is no longer reachable or my provider has got wrong data in costs logs.
Code:
01.08.11 14:49:55 Internettelefonie mit [email protected] über sip.qsc.de war nicht erfolgreich. Ursache: Not Found (404)
01.08.11 14:49:41 Internettelefonie mit [email protected] über sip.12voip.com war nicht erfolgreich. Ursache: User not found (404)
Theres neither a way to remove marvel configuration data from your google account or htc sync account, this is absolutely not acceptable,
The only desaster recovery option this marvel accepts is to enable accept of official market apps only, so some apps from appbrain.com were hopefully left out from the auto-restore, is this rechecked?

OK, lets do a remote virus scan of the marvel wildfire S over WLAN (needs e.g. sshdroid app with sftp support running as ROOT ):
Code:
[email protected]:~/htc$ sshfs htc:/ /home/xxxxxxx/htc/sshfs -p xx -o ro,reconnect
[email protected]'s password:
[email protected]:~/htc$
[email protected]:~/htc$ #clamscan -r --bell --no-summary --infected --detect-pua=yes --heuristic-scan-precedence=yes sshfs/app-cache
[email protected]:~/htc$ ls -l sshfs
insgesamt 208
drwxr-xr-x 1 root root 0 1. Aug 04:03 acct
drwxr-xr-x 1 root xxxxxxx 60 1. Aug 04:03 app-cache
-rw-r--r-- 1 root root 460 1. Jan 1970 bootcomplete.rc
drwxrwx--- 1 xxxxxxx 2001 4096 1. Aug 21:11 cache
dr-x------ 1 root root 0 1. Aug 04:03 config
-rw-r--r-- 1 root root 1398 1. Jan 1970 cwkeys
drwxrwx--x 1 xxxxxxx xxxxxxx 4096 1. Aug 01:10 data
-rw-r--r-- 1 root root 118 1. Jan 1970 default.prop
drwxr-xr-x 1 root root 1600 1. Aug 18:47 dev
drwx------ 1 root root 4096 1. Aug 15:25 devlog
lrwxrwxrwx 1 root root 11 1. Aug 04:03 etc -> /system/etc
-rwxr-x--- 1 root root 107244 1. Jan 1970 init
-rwxr-x--- 1 root root 1677 1. Jan 1970 init.goldfish.rc
-rwxr-x--- 1 root root 5396 1. Jan 1970 init.marvel.rc
-rwxr-x--- 1 root root 20294 1. Jan 1970 init.rc
-rw-r--r-- 1 root root 11336 1. Jan 1970 logo.rle
drwxrwxr-x 1 root xxxxxxx 0 1. Aug 04:03 mnt
dr-xr-xr-x 1 root root 0 1. Jan 1970 proc
drwx------ 1 root root 0 16. Apr 19:08 root
drwxr-x--- 1 root root 0 1. Jan 1970 sbin
lrwxrwxrwx 1 root root 11 1. Aug 04:03 sdcard -> /mnt/sdcard
drwxr-xr-x 1 root root 0 1. Aug 04:03 sys
drwxr-xr-x 1 root root 4096 16. Apr 20:31 system
-rw-r--r-- 1 root root 0 1. Jan 1970 ueventd.goldfish.rc
-rw-r--r-- 1 root root 4311 1. Jan 1970 ueventd.rc
lrwxrwxrwx 1 root root 14 1. Aug 04:03 vendor -> /system/vendor
[email protected]:~/htc$
[email protected]:~/htc$ clamscan -r --bell --no-summary --infected --detect-pua=yes --heuristic-scan-precedence=yes sshfs/app-cache
xxxxx[email protected]:~/htc$ clamscan -r --bell --no-summary --infected --detect-pua=yes --heuristic-scan-precedence=yes sshfs/cache
[email protected]:~/htc$ clamscan -r --bell --no-summary --infected --detect-pua=yes --heuristic-scan-precedence=yes sshfs/data
[email protected]:~/htc$ clamscan -r --bell --no-summary --infected --detect-pua=yes --heuristic-scan-precedence=yes sshfs/mnt
[email protected]:~/htc$ clamscan -r --bell --no-summary --infected --detect-pua=yes --heuristic-scan-precedence=yes sshfs/sdcard
[email protected]:~/htc$ clamscan -r --bell --no-summary --infected --detect-pua=yes --heuristic-scan-precedence=yes sshfs/system
[email protected]:~/htc$
[email protected]:~/htc$ clamscan -r --bell --no-summary --infected --detect-pua=yes sshfs/app-cache
[email protected]:~/htc$ clamscan -r --bell --no-summary --infected --detect-pua=yes sshfs/cache
[email protected]:~/htc$ clamscan -r --bell --no-summary --infected --detect-pua=yes sshfs/data
[email protected]:~/htc$ clamscan -r --bell --no-summary --infected --detect-pua=yes sshfs/mnt
[email protected]:~/htc$ clamscan -r --bell --no-summary --infected --detect-pua=yes sshfs/sdcard
[email protected]:~/htc$ clamscan -r --bell --no-summary --infected --detect-pua=yes sshfs/system
[email protected]:~/htc$ fusermount -u /home/xxxxxxx/htc/sshfs
[email protected]:~/htc$
Maybe many files left out due to permissions and ro mount:
~# chown xxxxxxx.xxxxxx /home/xxxxxxx/htc/sshfs
chown: Zugriff auf „/home/xxxxxxx/htc/sshfs“ nicht möglich: Keine Berechtigung
The 3 installed EICAR Testfiles cannot be missed by clamav.
Some more console apps on the market like iptraf were helpful to track down the trojan if we got x-permissions at all from ssh.
I'm out of options for now, HTC Europe support has taken over the case, will report.

Just wanted to let You know the trojan is still on the device and active:
Today he moved one of the EICAR virus testfiles to the sipdroid app's space (is this possible without root?), Lookout reported it.

If you're rooted, why not do terminal
su
ls -la (virus listed)
chmod +000 the apk
reboot
rm -rf

woprr said:
Just wanted to let You know the trojan is still on the device and active:
Today he moved one of the EICAR virus testfiles to the sipdroid app's space (is this possible without root?), Lookout reported it.
Click to expand...
Click to collapse
Indirect said:
If you're rooted, why not do terminal
su
ls -la (virus listed)
chmod +000 the apk
reboot
rm -rf
Click to expand...
Click to collapse
i think he isnt on root..

Still, it is a valid option.

No. Rooting voids warranty. I've bought this product for fun not for having work with it.

Then I don't know what to tell you dude.

I'm just on my 5th try to factory reset the phone and using my google account without htc sense, hopefully it does not restore the trojan again, if it does, htc support has one week to fix it or the product is sent back to the seller, I should do this anyway, there much better phones.
Does not work, google is restoring the phone now, despite explicitly disabled sync settings.
What a crap!
HTC cannot fix that, problem with google, I'll try without setting up Google account access and using only googlemail par IMAP/SMTP access to get rid of the stored android phone sync data on google account.

woprr said:
I'm just on my 5th try to factory reset the phone and using my google account without htc sense, hopefully it does not restore the trojan again, if it does, htc support has one week to fix it or the product is sent back to the seller, I should do this anyway, there much better phones.
Does not work, google is restoring the phone now, despite explicitly disabled sync settings.
What a crap!
Click to expand...
Click to collapse
Seems your trojan is re-enabling those settings somehow, and a factory reset only wipes /data, therefore, the trojan must be in /system, which would only be possible if the device is rooted, try typing "su" in terminal emulator, or check if / is r/w in root explorer, if either of those are right, then your device is rooted, and you should install a custom recovery and wipe everything except /boot. (Note: make sure to have a ROM (should be .zip) on the root of you sdcard to flash after you wipe everything, otherwise, the device will not boot)

1. I've said I do not want root. rooting voids warranty, I've paid HTC and google to manage the Product for me.
2. I do not have root:
Code:
ssh htc -p 2222
$ su
su: permission denied
$ echo test > /system/test
cannot create /system/test: read-only file system
$

If you were rooted, you would learn to fix things like this and wouldn't need a warranty unless it was accidental damage and even then, you can easily unroot your device and put s-on. It's not impossible. People unroot their devices to send in for warranty all the time.

I've said I've not yet decided to keep the phone. There're better ones for little money more around. In Germany You can revoke contracts with online sellers and return within 2 weeks.

woprr said:
I've said I've not yet decided to keep the phone. There're better ones for little money more around. In Germany You can revoke contracts with online sellers and return within 2 weeks.
Click to expand...
Click to collapse
Just return it and get something else since you don't want to root. You could root though, remove the virus, then unroot, as if you never had it touched...I don't see what use xda is if you're an unrooted user anyway, many things here require it, and i'm not trying to be rude to you.

How can a virus get the privileges on android you assume it's got without root access?

The virus itself could be running an exploit to allow root privledges also, it doesn't need root to be sending texts, only just to install itself into /system. Although it could also be hiding in dalvik

An exploit ^^. Scenario?
Ok, factory reset and not setup google +htc sense account in first run setup wizard should do the trick.
The Phone should be clean now.
I'm setting up google mail with the standard mua app, not the gmail app.
BTW, I've found the settings option to delete the sync data from google servers:
I'ts under Settings->Privacy->Backup and Restore->Uncheck Automatic restore (Msgbox popup warning: "...erase all copies on google servers?") but leave Back up my setting checked, if all is setup then setup google account in phone and sync.
Let's see if this works...
Looks like. But I dont know if the data on google servers got overwritten or merged.
I'will know when re-enabling automatic restore...

Desire HD issues

The phone is an HTC Desire HD, Ginger.
I have tried downgrading the A version, following this tutorial:
http://forum.xda-developers.com/showthread.php?t=905003
but I cant get the # sign, meaning that I have root access.
This is what I get in cmd :
C:\FlashHD\Downgrade>adb push
1189 KB/s (15837 bytes in 0.0
C:\FlashHD\Downgrade>adb push
869 KB/s (9796 bytes in 0.011
C:\FlashHD\Downgrade>adb shel
C:\FlashHD\Downgrade>adb shel
C:\FlashHD\Downgrade>adb shel
$ ./data/local/tmp/fre3vo -de
./data/local/tmp/fre3vo -debu
fre3vo by #teamwin
Please wait...
Attempting to modify ro.secur
fb_fix_screeninfo:
id: msmfb
smem_start: 802160640
smem_len: 3145728
type: 0
type_aux: 0
visual: 2
xpanstep: 0
ypanstep: 1
line_length: 1920
mmio_start: 0
accel: 0
fb_var_screeninfo:
xres: 480
yres: 800
xres_virtual: 480
yres_virtual: 1600
xoffset: 0
yoffset: 0
bits_per_pixel: 32
activate: 16
height: 106
width: 62
rotate: 0
grayscale: 0
nonstd: 0
accel_flags: 0
pixclock: 0
left_margin: 0
right_margin: 0
upper_margin: 0
lower_margin: 0
hsync_len: 0
vsync_len: 0
sync: 0
vmode: 0
Buffer offset: 00000000
Buffer size: 8192
Does anyone have any idea why this happens? The phone has been unlocked (I dont know how because I took it to a store for that). I bought it in Japan (Softbank).
Or if you can not help, can you please copy paste this question into that thread? I do not have enough posts to do it and I dont want to post randomly to gather enough posts for that.
Thank you!

TUTORIAL: Remote Control Touch Screen

Do you want to activate the screen wirelessly, or play some music at your phone over SSH because you don't know where you left it?
THIS IS YOUR PLACE!!!
This tutorial will show you how to create a file, that simulates a keypress, swipe, button press.
You can even draw something, save a file of data, and then replay it so android draws the same something.
You can simulate somebody writing text with the default android keyboard, over SSH, etc.
The options are unlimited!
Let's start by the beginning: I will add a zip package with my working directory at my phone, all tools are included there.
The dropbear ssh server is included because it's practical because it can be turned on with your android terminal. You can also access the other tools using another ssh server.
The media player control is a very simple script that takes an argument and then translates it to the android "input keyevent" command.
And the low level screen events is what i'm going to talk about most.
From here on, this will be a tutorial that will focus on screen events
I will cover the following topics:
1) Understanding and getting screen events.
2) Simulating keypressess, creating and sending screen events.
3) Automating the tasks.
​
UNDERSTANDING AND GETTING SCREEN EVENTS
Android provides two commandline tools for managing screen events: getevent and sendevent.
These commands are kinda cryptic:
We'll take a look at the "getevent" command. This command outputs all events of a given device (or all if no device is given)
What i'll do is open a SSH session, and run the commands from my PC, so that it does not interfere with my fingers pressing the keyboard.
I just use getevent (hint, press Control+C to terminate the command and stop getting events):
Code:
[email protected]:/ # getevent
add device 1: /dev/input/event8
name: "compass_sensor"
add device 2: /dev/input/event7
name: "sec_touchkey"
add device 3: /dev/input/event6
name: "gyro_sensor"
add device 4: /dev/input/event5
name: "light_sensor"
add device 5: /dev/input/event4
name: "proximity_sensor"
add device 6: /dev/input/event3
name: "sii9234_rcp"
add device 7: /dev/input/event2
name: "sec_touchscreen"
could not get driver version for /dev/input/mice, Not a typewriter
add device 8: /dev/input/event1
name: "gpio-keys"
add device 9: /dev/input/event0
name: "max8997-muic"
You may notice the "add device X" number is not matching the /dev/input/eventX number. I will use the latter to refer to an event, as we will use this command a lot, believe me.
I will be only talking about devices 1, 2 and 7, i don't care about the rest.
/dev/input/event1 (gpio-keys): This are the hardware keys.
On my Samsung Galaxy SII, these keys are POWER, HOME, VOLUP, and VOLDOWN keys.
/dev/input/event2 (sec_touchscreen): is the touch-screen (they're not very creative at android developing department)
My galaxy has a screen of 480x800 (XY), this is important!.
/dev/input/event7 (sec_touckey): The touch keys.
On my Galaxy, i have the MENU and BACK buttons as touchkeys. This touchkeys are not part of the touchscreen, thats why its another device.
Note though that the touch_screen and the touck_keys devices ARE connected, i'll later have you remember this line.
The numbers of the devices may change from device to device, as not all phones have touchkeys, or a touch screen.
Well, now you know how to list the devices.
The next step is to see how each device works:
Device 1: HWKEYS
I recommend following these steps on your device, and comment any changes at this thread, thank you.
Let's try out short-pressing just the POWER button of our phone (or unlock button)
When i refer to short-pressing, i mean pressing and immediately releasing the button. You'll soon understand why.
Use getevent, press the key, and finish with Control + C.
Code:
[email protected]:/ # getevent /dev/input/event1
0001 0074 00000001
0000 0000 00000000
0001 0074 00000000
0000 0000 00000000
^C
130|[email protected]:/
WTF is this?! Yes, i said that too when i first saw this, (and you havent seen a swipe with 4 fingers yet, haha)
Well, let's go line by line:
0001 0074 00000001
This is a KEYDOWN line (sorry for using my own syntax here)
What can we observe? There are 3 fields, and all numbers.
The first field will always be 1 except in separator lines (see the second line)
The second field is the identifier for the POWER key.
The third field is a boolean value, it will be 1 when the key is pressed and 0 when it is released.
0000 0000 00000000
This is a simple separator, it it means android just processed everything ultil here.
0001 0074 00000000
This is a KEYUP line, as you can see, the identifier field is 1, the keycode field is 74, and the third boolean field is set to 0, what indicates the key is released.
0000 0000 00000000
And another separator so android process it.
^C
This is the Control+C character, it is used to terminate the running program in linux terminal.
Actually quite simple, isn't it? Lets take a look at the touchkeys device (it's simpler as the screen)
Device 7: MENU and BACK
Yes, android has set up a whole device driver only for 2 stupid keys.
Let's see them in action. I will first press the MENU key, and then the BACK key.
Note that now i use "getevent /dev/input/event7", and not event1.
Oh, i will make some comments on the output so you can see it more clear.
Code:
[email protected]:/ # getevent /dev/input/event7
0001 008b 00000001 [FD] KEYDOWN (8b)
0000 0000 00000000 [S] SEPARATOR
0001 008b 00000000 [FU] KEYUP (8b)
0000 0000 00000000 [S] SEPARATOR
0001 009e 00000001 [FD] KEYDOWN (9e)
0000 0000 00000000 [S] SEPARATOR
0001 009e 00000000 [FU] KEYUP (9e)
0000 0000 00000000 [S] SEPARATOR
^C
130|[email protected]:/ #
Wow, hex!!, the POWER button we pressed before, was also hex.
Remember that getevents are all in hex.
Explanation:
[FD] Is (in my syntax), a FINGERDOWN event, that means the finger touches the screen.
[FU] FINGERUP event, the finger leaves the screen.
Separator, processess the event.
The parentheses i put after the FU and FD events are the ID of the key.
Remember i told you that the touch_keys and touch_screen devices were connected?
I dont know why but the first fields of the non-separator events are also 1 (same as the HWKEYS)
You'l see that with touchscreen events this is different (it uses number 3 always)
Well, the syntax of the events in the touchkeys are the same as the hardware keys.
Actually, i consider this touch keys to be hardware, with the consideration that they only work when the screen is on.
Device 2: SCREEN TOUCHES AND SWIPES (The interesting part)
Now it's getting really interesting.
Let's get a simple tap somewhere random at the screen:
Code:
[email protected]:/ # getevent /dev/input/event2
0003 0039 0000024f [FD] FingerDown (24f)
0003 0035 00000163 [X] X coordinate
0003 0036 000001dd [Y] Y coordinate
// NOTE LINE
0000 0000 00000000 [S] Separator
0003 0039 ffffffff [FU] FingerUp (24f)
0000 0000 00000000 [S] Separator
^C
130|[email protected]:/ #
NOTE: At the NOTE LINE you MAY get 2 other events, 0030 and 003a. I have no idea what these two are for.
Besides, to simulate a click we don't need them, so if anyone know what these two events are, you're welcome to comment.
If you enable the Show touches & Pointer location, you see that it has some fields: PRS and SIZE,
Those are for pressure and size, of course, but i don't know if they have something to do with this 0030 and 003a.
Tip for those of you that are debugging: if you increase pressure, your finger's contact area with the device grows, as your sking gets down.
I realised this thinking of somebody pushing his face to a glass surface and somebody watching at the other side.​
NOTE 2: You are recommended to enable Settings -> Developer Options -> Show touches & Pointer location​
Understanding touchscreen events is more complicated. All buttons from HWKEYS and TOUCHKEYS, were quite simple: they only have a key identifier, and a boolean state: Pressed (1) or not pressed (0).
However, when we use the touchscreen, every single tap has the following elements (events):
[ID] Identifier (ill explain this in the double tap section)
[FD] Finger Down (The finger enters the screen)
NOTE: The third field at the figerdown event, is a sort of simple counter, across different taps, swipes, etc. I dont know yet when it is resetted, but for sure at reboot as this counter will probably reside in ram.​[X] Number of pixels counted from left side.
[Y] Number of pixels counted from top.
Separator / process trigger.
[FU] Finger Up (The finger exits the screen completely)
Another separator.
Notice that the 0030 and 003a events are not in my list. I've made a tool to simulate keypressess, and those two events are NEVER included, but my script works always. So something tells me these two events are worthless.
Introduction to swipe
With the pointer location enabled in settins, try swiping somewhere random.
As you may notice, you aren't perfect, so you can't draw a straight line.
Everytime your finger changes direction, a new point is added. this means that if you want to make a square, you would need 4 points, imagining all lines are straight.
If you take a close look at the screen, the POINTER LOCATION shows a colored dot, everytime you set some coordinates (this means, by a single click, or by a direction change with a swipe, or with a double tap it would make two dots).
I will unlock my screen with my finger, and then analyze the output of getevent:
Lets analize this simple swipe, and quicly move on to the last teorichal part: Multiple taps.
Code:
[email protected]:/ # getevent /dev/input/event2
0003 0039 000002ba [FD]
0003 0035 000000e6 [X]
0003 0036 00000290 [Y]
0003 0030 00000032 [?]
0003 003a 00000003 [?]
0000 0000 00000000 [S]
0003 0035 000000fb [X]
0003 0036 00000296 [Y]
0000 0000 00000000 [S]
0003 0035 00000120 [X]
0003 003a 00000004 [?]
0000 0000 00000000 [S]
0003 0035 00000161 [X]
0003 0036 00000292 [Y]
0003 003a 00000003 [?]
0000 0000 00000000 [S]
0003 0035 000001aa [X]
0003 0036 0000029a [Y]
0003 0030 00000018 [?]
0003 003a 00000001 [?]
0000 0000 00000000 [S]
0003 0039 ffffffff [FU]
0000 0000 00000000 [S]
^C
130|[email protected]:/ #
Take a look at the above code. You should already get the point, at every separator the events are processed.
You can use a separator to update coordinates (this includes when a finger enters the screen), and to release a finger (at the last coordinates inputted for that finger).
This that the 2nd to 5th block, only update the coordinates of the finger that is pressing the screen.
Multiple taps
Multiple taps introduces something new: Identificators [ID]
For this i will use the following: a thriple tap.
There is a order in which the fingers enter and leave the screen, while one finger is still pressed, another one can get pressed and released.
Lets see some code:
Code:
130|[email protected]:/ # getevent /dev/input/event2
0003 0039 000002c0 [FD]
0003 0035 00000057 [X]
0003 0036 00000129 [Y]
0000 0000 00000000 [S]
0003 002f 00000001 [ID] 1
0003 0039 000002c1 [FD]
0003 0035 00000169 [X]
0003 0036 000001bb [Y]
0000 0000 00000000 [S]
0003 002f 00000002 [ID] 2
0003 0039 000002c2 [FD]
0003 0035 000000de [X]
0003 0036 00000187 [Y]
0000 0000 00000000 [S]
0003 0039 ffffffff [FU] // NOTE 1
0000 0000 00000000 [S]
0003 002f 00000000 [ID] 0 // NOTE 2
0003 0039 ffffffff [FU]
0000 0000 00000000 [S]
0003 002f 00000001 [ID] 1
0003 0039 ffffffff [FU]
0000 0000 00000000 [S]
^C
130|[email protected]:/ #
Well, its actually quite simple. As there are multiple fingers, android adds ID's to this new fingers.
The default ID = 0, android doesn't know if you're gonna press 1 finger or 200, so it doesnt add a ID to the first.
The first finger's ID is always 0.
When you add a finger, android adds ID=1
If you release a finger, ID=0 is available again.
Important: When an ID is set, all actions that are processed, are affecting the finger of that ID, this means that if you set the coordinates 10 times in a row they will all affect that finger, until you specify another ID event. (You just learned to combine swipe with multiple touches)
Thats why at the line i marked with NOTE 1, there is no ID, because the first finger i released, was finger ID=2 (the last that touched the screen)
Important: When you release a finger, you MUST set an ID, because android only keeps track of the CID (Current ID), but not of the previus.
So if you release a finger, and then set some coordinates, they will affect an ID that is no longer pressed, and it could either do NOTHING, or output some error message
SIMULATING KEYPRESSESS, CREATING AND SENDING EVENTS
NOTE: When we use "getevent", we get some hex codes. When we use "sendevent" we have to use decimal values.
Why? I don't know, maybe bothering is the point. Anyway, it's like that, and we'll have to manage, right?
Sendevent takes the EXACT same input that getevent outputs, except that GETEVENT outputs [HEX]adecimal, and Sendevents wants [DEC]imal characters
To simulate the POWER button key, for one single click, it would take this steps:
STEP 1
STEP 2
STEP 3
Edit: I'm currently making the SENDEVENT TUTORIAL part, in about 2 hours it will be done.
Vote for newsworthy if you think it was!!!

Twin0ne said:
Do you want to activate the screen wirelessly, or play some music at your phone over SSH because you don't know where you left it?
THIS IS YOUR PLACE!!!
Click to expand...
Click to collapse
Welcome to XDA, This is a great way to "roll into to town" :good:
I've been planning to research getevent/sendevent command input for a while, ever since one of my tablet touchscreens decided to die, Mainly to simulate long pressing.
If you don't want to write to the /dev nodes directly you can always step up a level of abstraction and use the /system/bin/input commnd. Prior to jelly bean this used to only support KEYEVENT codes and text input. The JB version however now supports tap and swipe aswell.
Code:
/system/bin/input
usage: input ...
input text <string>
input keyevent <key code number or name>
input tap <x> <y>
input swipe <x1> <y1> <x2> <y2>
Here (androidxref) is a list of Valid KeyCodes for use with the keyevent parameter.
I've gone a bit nuts with a custom adb that I use so i've wrapped a lot of commnds into one word adb commands like "adb power" , "adb back" etc :laugh:
Once again thanks for sharing, low level android tricks are always welcome!

Very useful description thank you. I've found some other relevant info...
Adding -l to the command line of getevent adds the event names, also adding -d preserves the HID descriptor. A single touch event looks like this...
[email protected]:/ # getevent -d -l /dev/input/event2
EV_ABS ABS_MT_TRACKING_ID 00000071
EV_ABS ABS_MT_POSITION_X 0000020d
EV_ABS ABS_MT_POSITION_Y 00000160
EV_SYN SYN_REPORT 00000000
EV_ABS ABS_MT_TRACKING_ID ffffffff
EV_SYN SYN_REPORT 00000000 ​
Also, there is a description of the linux multi-touch protocol here: http://www.kernel.org/doc/Documentation/input/multi-touch-protocol.txt

Thank you very much for this thread.
This helps me better understand how Android works. :good:
And I have chance to use Touch "simulation"...
http://forum.xda-developers.com/showpost.php?p=54953993&postcount=701
Best Regards

Only as info or example...
Code:
adb shell sendevent /dev/input/event3 3 57 0
adb shell sendevent /dev/input/event3 3 53 4
adb shell sendevent /dev/input/event3 3 54 326
adb shell sendevent /dev/input/event3 3 48 28
adb shell sendevent /dev/input/event3 0 2 0
adb shell sendevent /dev/input/event3 0 0 0
adb shell sendevent /dev/input/event3 3 57 0
adb shell sendevent /dev/input/event3 3 53 4
adb shell sendevent /dev/input/event3 3 54 327
adb shell sendevent /dev/input/event3 3 48 32
adb shell sendevent /dev/input/event3 0 2 0
adb shell sendevent /dev/input/event3 0 0 0
adb shell sendevent /dev/input/event3 3 57 0
adb shell sendevent /dev/input/event3 3 53 5
adb shell sendevent /dev/input/event3 3 54 327
adb shell sendevent /dev/input/event3 3 48 48
adb shell sendevent /dev/input/event3 0 2 0
adb shell sendevent /dev/input/event3 0 0 0
adb shell sendevent /dev/input/event3 3 57 0
adb shell sendevent /dev/input/event3 3 53 6
adb shell sendevent /dev/input/event3 3 54 327
adb shell sendevent /dev/input/event3 3 48 49
adb shell sendevent /dev/input/event3 0 2 0
adb shell sendevent /dev/input/event3 0 0 0
adb shell sendevent /dev/input/event3 3 57 0
adb shell sendevent /dev/input/event3 3 53 8
adb shell sendevent /dev/input/event3 3 54 328
adb shell sendevent /dev/input/event3 3 48 51
adb shell sendevent /dev/input/event3 0 2 0
adb shell sendevent /dev/input/event3 0 0 0
adb shell sendevent /dev/input/event3 3 57 0
adb shell sendevent /dev/input/event3 3 53 9
adb shell sendevent /dev/input/event3 3 54 329
adb shell sendevent /dev/input/event3 3 48 52
adb shell sendevent /dev/input/event3 0 2 0
adb shell sendevent /dev/input/event3 0 0 0
adb shell sendevent /dev/input/event3 3 57 0
adb shell sendevent /dev/input/event3 3 53 11
adb shell sendevent /dev/input/event3 3 54 330
adb shell sendevent /dev/input/event3 3 48 53
adb shell sendevent /dev/input/event3 0 2 0
adb shell sendevent /dev/input/event3 0 0 0
adb shell sendevent /dev/input/event3 3 57 0
adb shell sendevent /dev/input/event3 3 53 13
adb shell sendevent /dev/input/event3 3 54 331
adb shell sendevent /dev/input/event3 3 48 54
adb shell sendevent /dev/input/event3 0 2 0
adb shell sendevent /dev/input/event3 0 0 0
adb shell sendevent /dev/input/event3 3 57 0
adb shell sendevent /dev/input/event3 3 53 18
adb shell sendevent /dev/input/event3 3 54 332
adb shell sendevent /dev/input/event3 3 48 54
adb shell sendevent /dev/input/event3 0 2 0
adb shell sendevent /dev/input/event3 0 0 0
adb shell sendevent /dev/input/event3 3 57 0
adb shell sendevent /dev/input/event3 3 53 28
adb shell sendevent /dev/input/event3 3 54 333
adb shell sendevent /dev/input/event3 3 48 54
adb shell sendevent /dev/input/event3 0 2 0
adb shell sendevent /dev/input/event3 0 0 0
adb shell sendevent /dev/input/event3 3 57 0
adb shell sendevent /dev/input/event3 3 53 54
adb shell sendevent /dev/input/event3 3 54 336
adb shell sendevent /dev/input/event3 3 48 55
adb shell sendevent /dev/input/event3 0 2 0
adb shell sendevent /dev/input/event3 0 0 0
adb shell sendevent /dev/input/event3 3 57 0
adb shell sendevent /dev/input/event3 3 53 63
adb shell sendevent /dev/input/event3 3 54 336
adb shell sendevent /dev/input/event3 3 48 56
adb shell sendevent /dev/input/event3 0 2 0
adb shell sendevent /dev/input/event3 0 0 0
adb shell sendevent /dev/input/event3 3 57 0
adb shell sendevent /dev/input/event3 3 53 74
adb shell sendevent /dev/input/event3 3 54 336
adb shell sendevent /dev/input/event3 3 48 56
adb shell sendevent /dev/input/event3 0 2 0
adb shell sendevent /dev/input/event3 0 0 0
adb shell sendevent /dev/input/event3 3 57 0
adb shell sendevent /dev/input/event3 3 53 89
adb shell sendevent /dev/input/event3 3 54 336
adb shell sendevent /dev/input/event3 3 48 57
adb shell sendevent /dev/input/event3 0 2 0
adb shell sendevent /dev/input/event3 0 0 0
adb shell sendevent /dev/input/event3 3 57 0
adb shell sendevent /dev/input/event3 3 53 101
adb shell sendevent /dev/input/event3 3 54 336
adb shell sendevent /dev/input/event3 3 48 59
adb shell sendevent /dev/input/event3 0 2 0
adb shell sendevent /dev/input/event3 0 0 0
adb shell sendevent /dev/input/event3 3 57 0
adb shell sendevent /dev/input/event3 3 53 115
adb shell sendevent /dev/input/event3 3 54 335
adb shell sendevent /dev/input/event3 3 48 59
adb shell sendevent /dev/input/event3 0 2 0
adb shell sendevent /dev/input/event3 0 0 0
adb shell sendevent /dev/input/event3 3 57 0
adb shell sendevent /dev/input/event3 3 53 131
adb shell sendevent /dev/input/event3 3 54 335
adb shell sendevent /dev/input/event3 3 48 60
adb shell sendevent /dev/input/event3 0 2 0
adb shell sendevent /dev/input/event3 0 0 0
adb shell sendevent /dev/input/event3 3 57 0
adb shell sendevent /dev/input/event3 3 53 146
adb shell sendevent /dev/input/event3 3 54 334
adb shell sendevent /dev/input/event3 3 48 61
adb shell sendevent /dev/input/event3 0 2 0
adb shell sendevent /dev/input/event3 0 0 0
adb shell sendevent /dev/input/event3 3 57 0
adb shell sendevent /dev/input/event3 3 53 162
adb shell sendevent /dev/input/event3 3 54 334
adb shell sendevent /dev/input/event3 3 48 61
adb shell sendevent /dev/input/event3 0 2 0
adb shell sendevent /dev/input/event3 0 0 0
adb shell sendevent /dev/input/event3 3 57 0
adb shell sendevent /dev/input/event3 3 53 179
adb shell sendevent /dev/input/event3 3 54 333
adb shell sendevent /dev/input/event3 3 48 62
adb shell sendevent /dev/input/event3 0 2 0
adb shell sendevent /dev/input/event3 0 0 0
adb shell sendevent /dev/input/event3 3 57 0
adb shell sendevent /dev/input/event3 3 53 197
adb shell sendevent /dev/input/event3 3 54 333
adb shell sendevent /dev/input/event3 3 48 62
adb shell sendevent /dev/input/event3 0 2 0
adb shell sendevent /dev/input/event3 0 0 0
adb shell sendevent /dev/input/event3 3 57 0
adb shell sendevent /dev/input/event3 3 53 216
adb shell sendevent /dev/input/event3 3 54 333
adb shell sendevent /dev/input/event3 3 48 63
adb shell sendevent /dev/input/event3 0 2 0
adb shell sendevent /dev/input/event3 0 0 0
adb shell sendevent /dev/input/event3 3 57 0
adb shell sendevent /dev/input/event3 3 53 232
adb shell sendevent /dev/input/event3 3 54 333
adb shell sendevent /dev/input/event3 3 48 64
adb shell sendevent /dev/input/event3 0 2 0
adb shell sendevent /dev/input/event3 0 0 0
adb shell sendevent /dev/input/event3 3 57 0
adb shell sendevent /dev/input/event3 3 53 252
adb shell sendevent /dev/input/event3 3 54 333
adb shell sendevent /dev/input/event3 3 48 64
adb shell sendevent /dev/input/event3 0 2 0
adb shell sendevent /dev/input/event3 0 0 0
adb shell sendevent /dev/input/event3 3 57 0
adb shell sendevent /dev/input/event3 3 53 270
adb shell sendevent /dev/input/event3 3 54 334
adb shell sendevent /dev/input/event3 3 48 64
adb shell sendevent /dev/input/event3 0 2 0
adb shell sendevent /dev/input/event3 0 0 0
adb shell sendevent /dev/input/event3 3 57 0
adb shell sendevent /dev/input/event3 3 53 290
adb shell sendevent /dev/input/event3 3 54 335
adb shell sendevent /dev/input/event3 3 48 64
adb shell sendevent /dev/input/event3 0 2 0
adb shell sendevent /dev/input/event3 0 0 0
adb shell sendevent /dev/input/event3 3 57 0
adb shell sendevent /dev/input/event3 3 53 373
adb shell sendevent /dev/input/event3 3 54 335
adb shell sendevent /dev/input/event3 3 48 64
adb shell sendevent /dev/input/event3 0 2 0
adb shell sendevent /dev/input/event3 0 0 0
adb shell sendevent /dev/input/event3 3 57 0
adb shell sendevent /dev/input/event3 3 53 451
adb shell sendevent /dev/input/event3 3 54 332
adb shell sendevent /dev/input/event3 3 48 54
adb shell sendevent /dev/input/event3 0 2 0
adb shell sendevent /dev/input/event3 0 0 0
adb shell sendevent /dev/input/event3 3 57 0
adb shell sendevent /dev/input/event3 3 53 463
adb shell sendevent /dev/input/event3 3 54 332
adb shell sendevent /dev/input/event3 3 48 42
adb shell sendevent /dev/input/event3 0 2 0
adb shell sendevent /dev/input/event3 0 0 0
adb shell sendevent /dev/input/event3 3 57 0
adb shell sendevent /dev/input/event3 3 53 470
adb shell sendevent /dev/input/event3 3 54 330
adb shell sendevent /dev/input/event3 3 48 32
adb shell sendevent /dev/input/event3 0 2 0
adb shell sendevent /dev/input/event3 0 0 0
adb shell sendevent /dev/input/event3 3 57 0
adb shell sendevent /dev/input/event3 3 53 470
adb shell sendevent /dev/input/event3 3 54 330
adb shell sendevent /dev/input/event3 3 48 0
adb shell sendevent /dev/input/event3 0 2 0
adb shell sendevent /dev/input/event3 0 0 0
I have created simple Batch file... *.bat
I can unlock Screenlock/Screensaver with this...
Tested on my S8600 with I9001 Firmware... because unsupported Hardware and Touch not working yet....
Also on I8150 tested successfully... because taken from I8150...
Here Log, which I have converted into Dec Values by my little brain... line by line...
Code:
getevent /dev/input/event3
0003 0039 00000000
0003 0035 00000004
0003 0036 00000146
0003 0030 0000001c
0000 0002 00000000
0000 0000 00000000
0003 0039 00000000
0003 0035 00000004
0003 0036 00000147
0003 0030 00000020
0000 0002 00000000
0000 0000 00000000
0003 0039 00000000
0003 0035 00000005
0003 0036 00000147
0003 0030 00000030
0000 0002 00000000
0000 0000 00000000
0003 0039 00000000
0003 0035 00000006
0003 0036 00000147
0003 0030 00000031
0000 0002 00000000
0000 0000 00000000
0003 0039 00000000
0003 0035 00000008
0003 0036 00000148
0003 0030 00000033
0000 0002 00000000
0000 0000 00000000
0003 0039 00000000
0003 0035 00000009
0003 0036 00000149
0003 0030 00000034
0000 0002 00000000
0000 0000 00000000
0003 0039 00000000
0003 0035 0000000b
0003 0036 0000014a
0003 0030 00000035
0000 0002 00000000
0000 0000 00000000
0003 0039 00000000
0003 0035 0000000d
0003 0036 0000014b
0003 0030 00000036
0000 0002 00000000
0000 0000 00000000
0003 0039 00000000
0003 0035 00000012
0003 0036 0000014c
0003 0030 00000036
0000 0002 00000000
0000 0000 00000000
0003 0039 00000000
0003 0035 0000001c
0003 0036 0000014d
0003 0030 00000036
0000 0002 00000000
0000 0000 00000000
0003 0039 00000000
0003 0035 00000036
0003 0036 00000150
0003 0030 00000037
0000 0002 00000000
0000 0000 00000000
0003 0039 00000000
0003 0035 0000003f
0003 0036 00000150
0003 0030 00000038
0000 0002 00000000
0000 0000 00000000
0003 0039 00000000
0003 0035 0000004a
0003 0036 00000150
0003 0030 00000038
0000 0002 00000000
0000 0000 00000000
0003 0039 00000000
0003 0035 00000059
0003 0036 00000150
0003 0030 00000039
0000 0002 00000000
0000 0000 00000000
0003 0039 00000000
0003 0035 00000065
0003 0036 00000150
0003 0030 0000003b
0000 0002 00000000
0000 0000 00000000
0003 0039 00000000
0003 0035 00000073
0003 0036 0000014f
0003 0030 0000003b
0000 0002 00000000
0000 0000 00000000
0003 0039 00000000
0003 0035 00000083
0003 0036 0000014f
0003 0030 0000003c
0000 0002 00000000
0000 0000 00000000
0003 0039 00000000
0003 0035 00000092
0003 0036 0000014e
0003 0030 0000003d
0000 0002 00000000
0000 0000 00000000
0003 0039 00000000
0003 0035 000000a2
0003 0036 0000014e
0003 0030 0000003d
0000 0002 00000000
0000 0000 00000000
0003 0039 00000000
0003 0035 000000b3
0003 0036 0000014d
0003 0030 0000003e
0000 0002 00000000
0000 0000 00000000
0003 0039 00000000
0003 0035 000000c5
0003 0036 0000014d
0003 0030 0000003e
0000 0002 00000000
0000 0000 00000000
0003 0039 00000000
0003 0035 000000d8
0003 0036 0000014d
0003 0030 0000003f
0000 0002 00000000
0000 0000 00000000
0003 0039 00000000
0003 0035 000000e8
0003 0036 0000014d
0003 0030 00000040
0000 0002 00000000
0000 0000 00000000
0003 0039 00000000
0003 0035 000000fc
0003 0036 0000014d
0003 0030 00000040
0000 0002 00000000
0000 0000 00000000
0003 0039 00000000
0003 0035 0000010e
0003 0036 0000014e
0003 0030 00000040
0000 0002 00000000
0000 0000 00000000
0003 0039 00000000
0003 0035 00000122
0003 0036 0000014f
0003 0030 00000040
0000 0002 00000000
0000 0000 00000000
0003 0039 00000000
0003 0035 00000175
0003 0036 0000014f
0003 0030 00000040
0000 0002 00000000
0000 0000 00000000
0003 0039 00000000
0003 0035 000001c3
0003 0036 0000014c
0003 0030 00000036
0000 0002 00000000
0000 0000 00000000
0003 0039 00000000
0003 0035 000001cf
0003 0036 0000014c
0003 0030 0000002a
0000 0002 00000000
0000 0000 00000000
0003 0039 00000000
0003 0035 000001d6
0003 0036 0000014a
0003 0030 00000020
0000 0002 00000000
0000 0000 00000000
0003 0039 00000000
0003 0035 000001d6
0003 0036 0000014a
0003 0030 00000000
0000 0002 00000000
0000 0000 00000000
I am using old Android Version, where only input text and input keyevent is supported...
I can't install Android 4.x during incompatibility on my GT-S8600 yet...
Best Regards

Hi,
what i understand so far.
for each device you have different "targets" to simulate e.g. the press/hold of a key. Actually i found it for my device and managed to simulate my hardware/soft keys with tasker-run shell and sendevent...
Question1: how do key-remapper handle that ? Do they question the system e.g. what device the menu-key is ?
But more important to me is Question2: How can i simulate CTRL-C assuming that it is copy (and CTRL-V,CTRL-a) for a floating addition for my soft keyboard. I already managed to have a taker-scene, which floats as an overlay an by pressing my button called "test" the scene(overlay) hides and i can simulate a (sequence of keys or i can sendevent-stuff)...and there i would call Select-All,copy,paste.... Any idea (and no, the standard bar popping up when editing text with these functions does not pop up with swiftkey or in other situations i might want to use that). The keyboard "programmer keyboard" has this as buttons..so the function must be there somewhere...
In short: how to emulate CTRL-C ?

I need to emulate a swipe up and down the side of my screen, in a single touch. I'm trying to go from x=1350 y=1350 to x=1350 y=750 and back down to x=1350 y=1350
I can do this in two distinct touches with:
input swipe 1350 1350 1350 750
input swipe 1350 750 1350 1350
But I need it completed in one single touch, so I'm trying to use sendevent for the first time. I thought this would get me there, but I'm not doing something right:
sendevent /dev/input/event1 3 57 0
sendevent /dev/input/event1 3 53 1350
sendevent /dev/input/event1 3 54 1350
sendevent /dev/input/event1 0 2 0
sendevent /dev/input/event1 0 0 0
sendevent /dev/input/event1 3 57 0
sendevent /dev/input/event1 3 53 1350
sendevent /dev/input/event1 3 54 750
sendevent /dev/input/event1 0 2 0
sendevent /dev/input/event1 0 0 0
sendevent /dev/input/event1 3 57 0
sendevent /dev/input/event1 3 53 1350
sendevent /dev/input/event1 3 54 1350
sendevent /dev/input/event1 0 2 0
sendevent /dev/input/event1 0 0 0
When I do this, I don't get any swipe at all, and my touchscreen gets extremely laggy, then unresponsive to single taps or swipe gestures...but double taps work.
I need to reboot by Vol Down + Power to rescue the device.
Sent from my S6 Edge+ g928c
BobCatRom

trevd said:
I've been planning to research getevent/sendevent command input for a while, ever since one of my tablet touchscreens decided to die, Mainly to simulate long pressing.
Click to expand...
Click to collapse
Were you able to simulate a long press? I'm currently stuck on that with my project. I want to simulate a long press in Chrome so I can open the share dialog for a link and extract the URL. I was hoping to be able to do this through the Accessibility service but it seems long press isn't supported. Thanks!

MTCD_XRC sofia3gr 1Gb RAM 6.0.1 apps being killed?

Hi all,
I've purchased the above head unit (Will post specs below) and thought I'd give the 1Gb RAM unit a try, I've played about with android for a long time so already knew 1Gb was light, but I got it cheap (Always the problem!).
So I've got a Hizpo (I know that's a bundler) unit, so actual specs are:
Android 6.0.1
A-MEDIA AUTO (1024x600)
Baseband: SF3GR_M-26.3
Kernel: 3.14.0+ [email protected] #55
Build number: sofia3gr_car_64-userdebug
MCU: MTCD_XRC_V2.58_1
Memory: 918MB
Now this seems to be quite up to date, new Android, new MCU version and kernel. It boots pretty quickly and also apps do load quite quickly too, even google maps.
The problem I have is that apps suddenly close without warning and without error. So for example I open google maps, choose directions, and go to start navigation and suddenly it closes. No normal app has crashed message or anything like that.
So my suspicion is this is some kind of task killer running, killing apps that are trying to consume too much memory or CPU. I know the stock rom has something like this as I have a 'rocket' icon I can click and it shows how much ram it has managed to free up. I'm suspecting there is a background service doing this periodically and killing things, but being a bit over-ambitious! So far I'm not consuming anywhere near the full RAM, whenever I've checked I've had around 600MB free at any one time and the unit isn't going really laggy or anything I'd expect, so I think it's just the task killer getting in the way.
Does anyone have anything similar, or have found what is killing tasks off like this?
I'm trying to get adb over wireless working, initially this hasn't worked but I've got another couple of ways to try first to get adb debugging.
Any suggestions please?
(And yes I know, moving to a 2Gb board would be simplest option, but cost is an issue!)

Hi Andy,
I recently bought exactly the same unit off an eBay seller 'stereo_eu'.
My unit behaves exactly the same a yours - BADLY!
First problem occured when the apparent UK stock unit took 3 weeks to arrive from China, and eBay removed the sellers items for an unspecified infringement.
After fitting, it does exactly as you described, and other nonsense.
I found a MCU version V2.60 which installed correctly but made no difference.
I then contacted the seller who sent me a link to an update.zip package, which turned out to be a
corrupt .zip file, (new4_sofia_6.0_wifi(20170915).zip) and put my unit into a V6.1.2 recovery mode loop.
I managed to recover it with a V5.1.1 Lolipop version found on here, and it's better than the stock 6.0.1
software, but still has it's problems.
They seem totally unwilling to link to a 'non corrupt' update file, and have asked me to send the unit back (to China) for replacement, which I have declined, and requested a return to their UK address, and a refund.
Not impressed at all so far . . . . . . . .

Well, I'm not saying the units are junk, I'm relatively happy as I can still use my phone for navigation, so not a total loss, but I like tinkering with android (I'm a former android dev) so figuring out what's going on is what I'm aiming to do.
I've now installed root (SuperSu) and doing adb shell I can gain root and get through the filesystem to see what's going on. adb logcat didn't show anything interesting as I thought it might, I've also confirmed that "Sofia-1-C9-Server-V1.0.apk" does not exist on this head unit, however when you turn the ignition off it shows "Shutting Down" and goes into a sleep mode which does a similar thing and kills all background services, etc which again don't get restarted after powering back on.
I've got a bit of logcat output when I launched maps, and in the process of launching maps the music playing in the background stopped, but noting in the log seems to indicate why:
11-23 19:27:37.209 1417 4469 E Settings: getIntForUser name:location_mode value:3
11-23 19:27:37.217 1417 4469 E Settings: getIntForUser name:location_mode value:3
11-23 19:27:37.227 1417 4469 E Settings: getIntForUser name:location_mode value:3
11-23 19:27:37.231 1417 4469 E Settings: getIntForUser name:location_mode value:3
11-23 19:27:37.239 1417 4469 E Settings: getIntForUser name:location_mode value:3
11-23 19:27:37.243 1417 4469 E Settings: getIntForUser name:location_mode value:3
11-23 19:27:37.244 1417 4469 I GCoreUlr: Successfully inserted 1 locations
11-23 19:27:37.254 1417 4469 E Settings: getIntForUser name:location_mode value:3
11-23 19:27:37.257 1417 4469 E Settings: getIntForUser name:location_mode value:3
11-23 19:27:38.190 1417 1417 I GeofencerStateMachine: sendTransitions: location=Location[fused 0.0,-1.1 acc=6 et=+20m47s600ms alt=82.6459732055664 vel=0.0 bear=171.0 {Bundle[mParcelledData.dataSize=356]}]
11-23 19:27:39.284 575 731 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.android.launcher/com.android.launcher2.Launcher (has extras)} from uid 1000 on display 0
11-23 19:27:39.484 575 743 E WifiConfigStore: makeChannelList age=3600000 for "MYWIFIHERE"WPA_PSK max=6 bssids=1
11-23 19:27:39.485 575 743 E WifiConfigStore: has my:mac:adress:here freq=2412 age=2902 ?=true
11-23 19:27:39.487 575 743 D WifiStateMachine: starting scan for "MYWIFIHERE"WPA_PSK with 2412
11-23 19:27:39.534 831 1054 I OpenGLRenderer: Initialized EGL, version 1.4
11-23 19:27:39.588 575 743 E WifiConfigStore: updateConfiguration freq=2412 BSSID=my:mac:adress:here RSSI=-73 "MYWIFIHERE"WPA_PSK
11-23 19:27:39.663 831 1054 V RenderScript: 0xde54d000 Launching thread(s), CPUs 4
11-23 19:27:39.701 575 743 E WifiConfigStore: updateSavedNetworkHistory(): try "MYWIFIHERE"WPA_PSK SSID="MYWIFIHERE" MYWIFIHERE [WPA2-PSK-CCMP][ESS] ajst=0
11-23 19:27:39.702 575 743 E WifiConfigStore: got known scan result my:mac:adress:here key : "MYWIFIHERE"WPA_PSK num: 1 rssi=-72 freq=2412
11-23 19:27:39.706 575 743 E WifiConfigStore: writeKnownNetworkHistory() num networks:3 needWrite=false
11-23 19:27:40.140 831 1054 W OpenGLRenderer: Incorrectly called buildLayer on View: ShortcutAndWidgetContainer, destroying layer...
11-23 19:27:40.140 831 1054 W OpenGLRenderer: Incorrectly called buildLayer on View: ShortcutAndWidgetContainer, destroying layer...
11-23 19:27:42.594 575 743 E WifiConfigStore: updateConfiguration freq=2412 BSSID=my:mac:adress:here RSSI=-72 "MYWIFIHERE"WPA_PSK
11-23 19:27:43.938 1417 1417 I GeofencerStateMachine: sendTransitions: location=Location[fused 0.0,-1.1 acc=6 et=+20m52s603ms alt=82.55806732177734 vel=0.0 bear=171.0 {Bundle[mParcelledData.dataSize=356]}]
11-23 19:27:44.607 4505 4514 W CursorWrapperInner: Cursor finalized without prior close()
11-23 19:27:45.602 575 743 E WifiConfigStore: updateConfiguration freq=2412 BSSID=my:mac:adress:here RSSI=-73 "MYWIFIHERE"WPA_PSK
11-23 19:27:48.240 1417 1417 I GeofencerStateMachine: sendTransitions: location=Location[fused acc=6 et=+20m57s609ms alt=82.54087829589844 vel=0.0 bear=171.0 {Bundle[mParcelledData.dataSize=356]}]
11-23 19:27:48.609 575 743 E WifiConfigStore: updateConfiguration freq=2412 BSSID=my:mac:adress:here RSSI=-73 "MYWIFIHERE"WPA_PSK
11-23 19:27:51.616 575 743 E WifiConfigStore: updateConfiguration freq=2412 BSSID=my:mac:adress:here RSSI=-73 "MYWIFIHERE"WPA_PSK
11-23 19:27:52.231 1417 4564 E Settings: getIntForUser name:location_mode value:3
11-23 19:27:52.234 1417 4564 E Settings: getIntForUser name:location_mode value:3
11-23 19:27:52.242 1417 4564 E Settings: getIntForUser name:location_mode value:3
11-23 19:27:52.246 1417 4564 E Settings: getIntForUser name:location_mode value:3
11-23 19:27:52.251 1417 4564 E Settings: getIntForUser name:location_mode value:3
11-23 19:27:52.257 1417 4564 E Settings: getIntForUser name:location_mode value:3
11-23 19:27:52.258 1417 4564 I GCoreUlr: Successfully inserted 1 locations
11-23 19:27:52.266 1417 4564 E Settings: getIntForUser name:location_mode value:3
11-23 19:27:52.268 1417 4564 E Settings: getIntForUser name:location_mode value:3
11-23 19:27:53.206 1417 1417 I GeofencerStateMachine: sendTransitions: location=Location[fused acc=6 et=+21m2s613ms alt=82.54087829589844 vel=0.0 bear=171.0 {Bundle[mParcelledData.dataSize=356]}]
11-23 19:27:53.506 575 840 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.microntek.navisettings/.MainActivity bnds=[315,104][450,277] (has extras)} from uid 10013 on display 0
11-23 19:27:53.586 4576 4576 E art : setrlimit(RLIMIT_CORE) failed for pid 4576: Operation not permitted
11-23 19:27:53.596 575 2496 I ActivityManager: Start proc 4576:com.microntek.navisettings/u0a59 for activity com.microntek.navisettings/.MainActivity
11-23 19:27:53.764 4576 4576 W System : ClassLoader referenced unknown path: /system/app/MTCNaviSettings/lib/x86
11-23 19:27:53.883 575 2263 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x30220000 pkg=com.google.android.apps.maps cmp=com.google.android.apps.maps/com.google.android.maps.MapsActivity} from uid 10059 on display 0
11-23 19:27:54.050 575 587 I art : Background partial concurrent mark sweep GC freed 13790(926KB) AllocSpace objects, 2(40KB) LOS objects, 27% free, 10MB/14MB, paused 3.709ms total 112.505ms
11-23 19:27:54.071 185 185 W hwcomposer: zone is small ,LCDC can not support
11-23 19:27:54.159 4214 4225 I art : Background sticky concurrent mark sweep GC freed 5640(458KB) AllocSpace objects, 9(744KB) LOS objects, 4% free, 38MB/40MB, paused 6.416ms total 63.265ms
11-23 19:27:54.309 4214 4214 I System.out: DEBUG getting preferred mode DRIVE
11-23 19:27:54.338 4590 4590 E art : setrlimit(RLIMIT_CORE) failed for pid 4590: Operation not permitted
11-23 19:27:54.345 575 813 I ActivityManager: Start proc 4590:com.google.process.gapps/u0a10 for content provider com.google.android.gsf/.settings.GoogleSettingsProvider
11-23 19:27:54.348 4214 4214 I System.out: DEBUG getting preferred mode DRIVE
11-23 19:27:54.432 575 2495 D Sensors : activate handle=5,enabled=1
11-23 19:27:54.432 575 2495 E Sensors : HALpen of failed with 'No such file or directory' (2)
11-23 19:27:54.432 575 2495 E Sensors : HALpen of failed with 'No such file or directory' (2)
11-23 19:27:54.433 575 2495 E Sensors : HALpen of failed with 'No such file or directory' (2)
11-23 19:27:54.433 575 2495 E Sensors : HALpen of failed with 'No such file or directory' (2)
11-23 19:27:54.433 575 2495 E Sensors : HALpen of failed with 'No such file or directory' (2)
11-23 19:27:54.433 575 2495 E Sensors : HALpen of failed with 'No such file or directory' (2)
11-23 19:27:54.433 575 2495 E Sensors : HALpen of failed with 'No such file or directory' (2)
11-23 19:27:54.433 575 2495 E Sensors : HALpen of failed with 'No such file or directory' (2)
11-23 19:27:54.433 575 2495 E Sensors : HALpen of failed with 'No such file or directory' (2)
11-23 19:27:54.433 575 2495 E Sensors : HALpen of failed with 'No such file or directory' (2)
11-23 19:27:54.433 575 2495 E Sensors : HALpen of failed with 'No such file or directory' (2)
11-23 19:27:54.447 575 853 E Sensors : HALpen of failed with 'No such file or directory' (2)
11-23 19:27:54.447 575 853 E Sensors : HALpen of failed with 'No such file or directory' (2)
11-23 19:27:54.447 575 853 E Sensors : HALpen of failed with 'No such file or directory' (2)
11-23 19:27:54.468 575 2453 D Sensors : activate handle=3,enabled=1
11-23 19:27:54.468 575 2453 E Sensors : HALpen of failed with 'No such file or directory' (2)
11-23 19:27:54.468 575 2453 E Sensors : HALpen of failed with 'No such file or directory' (2)
11-23 19:27:54.468 575 2453 E Sensors : HALpen of failed with 'No such file or directory' (2)
11-23 19:27:54.554 4590 4590 W System : ClassLoader referenced unknown path: /system/priv-app/GoogleServicesFramework/lib/x86
11-23 19:27:54.582 4214 4232 I System.out: DEBUG getting preferred mode DRIVE
11-23 19:27:54.590 4590 4590 I GservicesProvider: Gservices pushing to system: true; secure/global: true
11-23 19:27:54.609 4214 4214 I Choreographer: Skipped 36 frames! The application may be doing too much work on its main thread.
11-23 19:27:54.626 575 743 E WifiConfigStore: updateConfiguration freq=2412 BSSID=my:mac:adress:here RSSI=-74 "MYWIFIHERE"WPA_PSK
11-23 19:27:54.872 4590 4590 I GoogleHttpClient: GMS http client unavailable, use old client
11-23 19:27:54.933 575 2495 E Sensors : HALpen of failed with 'No such file or directory' (2)
11-23 19:27:54.933 575 2495 E Sensors : HALpen of failed with 'No such file or directory' (2)
11-23 19:27:54.933 575 2495 E Sensors : HALpen of failed with 'No such file or directory' (2)
11-23 19:27:54.977 1417 1417 I GeofencerStateMachine: sendNewLocationAvailability: availability=LocationAvailability[isLocationAvailable: true]
11-23 19:27:54.994 1417 1417 I GeofencerStateMachine: sendNewLocationAvailability: availability=LocationAvailability[isLocationAvailable: true]
Click to expand...
Click to collapse
List of apps in /system/app
[email protected]_car:/system/app # ls
Bluetooth
BluetoothMidiService
Browser
Calendar
CaptivePortalLogin
CertInstaller
DeskClock
DocumentsUI
ExactCalculator
Galaxy4
Gallery2
Gmail2
GooglePinyinIME
HCTBlueTooth4
HCTBtMusic4
HCTCarTouch
HCTUpdateService
HTMLViewer
HoloSpiralWallpaper
KeyChain
LatinIME
LiveWallpapers
LiveWallpapersPicker
MTCAPKInstall
MTCAVIN
MTCAmpSetup
MTCBackView
MTCCarCD
MTCCivicUSBIPOD
MTCControlInfo
MTCControlSettings
MTCDVD4
MTCFactorySettings
MTCFileBrowser4
MTCIpod4
MTCMovie4
MTCMusic4
MTCNaviSettings
MTCRadio4HCT
MTCSYNC
MTCScreenClock
MTCTV
MTCTpms
MTCTravel4
MTCWheelStudy
Maps
Music
NoiseField
OpenWnn
PacProcessor
PhaseBeam
PicoTts
PrintSpooler
Provision
RFTest
Stk
SuperSU
UserDictionaryProvider
WAPPushManager
webview
Click to expand...
Click to collapse
So I'm now onto debugging a bit closer, any extra info anyone can provide would be welcome!

Oh and process listing
[email protected]_car:/system/app # ps
USER PID PPID VSIZE RSS WCHAN PC NAME
root 1 0 3060 528 SyS_epoll_ f7795b80 S /init
root 2 0 0 0 kthreadd 00000000 S kthreadd
root 3 2 0 0 smpboot_th 00000000 S ksoftirqd/0
root 5 2 0 0 worker_thr 00000000 S kworker/0:0H
root 6 2 0 0 worker_thr 00000000 S kworker/u8:0
root 7 2 0 0 rcu_gp_kth 00000000 S rcu_preempt
root 8 2 0 0 rcu_gp_kth 00000000 S rcu_sched
root 9 2 0 0 rcu_gp_kth 00000000 S rcu_bh
root 10 2 0 0 smpboot_th 00000000 S migration/0
root 11 2 0 0 worker_thr 00000000 S kworker/0:1
root 12 2 0 0 smpboot_th 00000000 S watchdog/0
root 13 2 0 0 smpboot_th 00000000 S watchdog/1
root 14 2 0 0 smpboot_th 00000000 S migration/1
root 15 2 0 0 smpboot_th 00000000 S ksoftirqd/1
root 17 2 0 0 worker_thr 00000000 S kworker/1:0H
root 18 2 0 0 worker_thr 00000000 S kworker/1:1
root 19 2 0 0 smpboot_th 00000000 S watchdog/2
root 20 2 0 0 smpboot_th 00000000 S migration/2
root 21 2 0 0 smpboot_th 00000000 S ksoftirqd/2
root 23 2 0 0 worker_thr 00000000 S kworker/2:0H
root 24 2 0 0 worker_thr 00000000 S kworker/2:1
root 25 2 0 0 smpboot_th 00000000 S watchdog/3
root 26 2 0 0 smpboot_th 00000000 S migration/3
root 27 2 0 0 smpboot_th 00000000 S ksoftirqd/3
root 28 2 0 0 worker_thr 00000000 S kworker/3:0
root 29 2 0 0 worker_thr 00000000 S kworker/3:0H
root 31 2 0 0 rescuer_th 00000000 S khelper
root 32 2 0 0 vdump_thre 00000000 S vdump Thread
root 33 2 0 0 console_th 00000000 S kconsole
root 34 2 0 0 rescuer_th 00000000 S writeback
root 35 2 0 0 ksm_scan_t 00000000 S ksmd
root 36 2 0 0 rescuer_th 00000000 S bioset
root 37 2 0 0 rescuer_th 00000000 S kblockd
root 38 2 0 0 hub_thread 00000000 S khubd
root 54 2 0 0 fmdev_fifo 00000000 S iui_fm
root 55 2 0 0 ion_heap_d 00000000 S system-heap
root 56 2 0 0 mvpipe_dev 00000000 S ion_secvm_handl
root 57 2 0 0 irq_thread 00000000 S irq/303-rk818
root 58 2 0 0 rescuer_th 00000000 S rk81x_otg_work
root 59 2 0 0 rev_thread 00000000 D rev_thread
root 60 2 0 0 rockchip_f 00000000 S fb-vsync
root 61 2 0 0 kthread_wo 00000000 S rockchip-fb
root 62 2 0 0 cpufreq_in 00000000 S cfinteractive
root 63 2 0 0 irq_thread 00000000 S irq/320-car-rev
root 64 2 0 0 irq_thread 00000000 S irq/321-car-acc
root 65 2 0 0 rescuer_th 00000000 S rk81x-battery-w
root 66 2 0 0 rescuer_th 00000000 S car_wq
root 67 2 0 0 rescuer_th 00000000 S goodix_wq
root 89 2 0 0 kswapd 00000000 S kswapd0
root 90 2 0 0 fsnotify_m 00000000 S fsnotify_mark
root 91 2 0 0 rescuer_th 00000000 S crypto
root 105 2 0 0 rescuer_th 00000000 S bl_wq
root 106 2 0 0 irq_thread 00000000 S irq/40-rga
root 107 2 0 0 vnvm_serve 00000000 S vnvm
root 108 2 0 0 mvpipe_dev 00000000 S VUSB_SE_FE_MEX_
root 109 2 0 0 worker_thr 00000000 S kworker/u9:0
root 110 2 0 0 down_inter 00000000 S vsec
root 111 2 0 0 rescuer_th 00000000 S idi_error_work_
root 112 2 0 0 irq_thread 00000000 S irq/110-vpu.177
root 113 2 0 0 irq_thread 00000000 S irq/111-vpu.177
root 114 2 0 0 irq_thread 00000000 S irq/38-hevc.178
root 115 2 0 0 rescuer_th 00000000 S dwc2
root 116 2 0 0 rescuer_th 00000000 S uether
root 117 2 0 0 rescuer_th 00000000 S adv_wq
root 118 2 0 0 rescuer_th 00000000 S dm_bufio_cache
root 120 2 0 0 mmc_queue_ 00000000 S mmcqd/0
root 121 2 0 0 mmc_queue_ 00000000 S mmcqd/0boot0
root 122 2 0 0 mmc_queue_ 00000000 S mmcqd/0boot1
root 123 2 0 0 mmc_queue_ 00000000 S mmcqd/0rpmb
root 124 2 0 0 worker_thr 00000000 S kworker/2:2
root 125 2 0 0 rescuer_th 00000000 S binder
root 126 2 0 0 intel_adc_ 00000000 S adc-thread
root 127 2 0 0 oct_thread 00000000 S OCT Thread
root 128 2 0 0 rescuer_th 00000000 S dvd_wq
root 129 2 0 0 irq_thread 00000000 S irq/108-dsp_int
root 130 2 0 0 irq_thread 00000000 S irq/107-dsp_int
root 131 2 0 0 irq_thread 00000000 S irq/99-dsp_int3
root 132 2 0 0 rescuer_th 00000000 S ipv6_addrconf
root 133 2 0 0 rescuer_th 00000000 S fuel_gauge.187
root 134 2 0 0 mmc_queue_ 00000000 S mmcqd/1
root 136 2 0 0 rescuer_th 00000000 S deferwq
root 139 2 0 0 worker_thr 00000000 S kworker/u8:4
root 140 2 0 0 irq_thread 00000000 S irq/283-jack_ir
root 141 2 0 0 irq_thread 00000000 S irq/284-button_
root 142 2 0 0 rescuer_th 00000000 S f_mtp
root 143 2 0 0 rescuer_th 00000000 S setExposure_que
root 144 2 0 0 rescuer_th 00000000 S measurement_que
root 145 2 0 0 rescuer_th 00000000 S bat_hal-0
root 148 1 2540 124 poll_sched f7712b80 S /sbin/ueventd
root 151 2 0 0 worker_thr 00000000 S kworker/0:1H
root 152 2 0 0 worker_thr 00000000 S kworker/1:1H
root 153 2 0 0 kjournald2 00000000 S jbd2/mmcblk0p14
root 154 2 0 0 rescuer_th 00000000 S ext4-rsv-conver
root 157 2 0 0 worker_thr 00000000 S kworker/2:1H
root 159 2 0 0 kjournald2 00000000 S jbd2/mmcblk0p15
root 160 2 0 0 rescuer_th 00000000 S ext4-rsv-conver
root 164 2 0 0 kjournald2 00000000 S jbd2/mmcblk0p13
root 165 2 0 0 rescuer_th 00000000 S ext4-rsv-conver
logd 166 1 14856 2436 sigsuspend f76e3b80 S /system/bin/logd
root 167 1 11644 912 hrtimer_na f7675b80 S /system/bin/vold
root 172 2 0 0 kauditd_th 00000000 S kauditd
root 182 1 2932 304 SyS_epoll_ f7758b80 S /sbin/healthd
root 183 1 4308 708 SyS_epoll_ f772ab80 S /system/bin/lmkd
system 184 1 4116 660 binder_thr f7744b80 S /system/bin/servicemanager
system 185 1 61108 3840 SyS_epoll_ f770fb80 S /system/bin/surfaceflinger
root 186 1 2284 0 hrtimer_na f77dfb80 S /sbin/watchdogd
radio 187 1 5648 660 SyS_epoll_ f779cb80 S /system/bin/rpcServer
shell 193 1 4328 672 n_tty_read f7731b80 S /system/bin/sh
radio 194 1 16412 940 hrtimer_na f775bb80 S /system/bin/rild
radio 195 1 16156 800 hrtimer_na f76cbb80 S /system/bin/rild
root 196 1 17884 1468 hrtimer_na f773fb80 S /system/bin/netd
root 198 1 4936 968 __skb_recv f773bb80 S /system/bin/debuggerd
drm 199 1 25160 1428 binder_thr f773bb80 S /system/bin/drmserver
media 200 1 139544 3632 binder_thr f7705b80 S /system/bin/mediaserver
root 201 1 4216 1028 unix_strea f76afb80 S /system/bin/installd
keystore 204 1 7692 1144 binder_thr f7766b80 S /system/bin/keystore
system 205 1 7960 780 binder_thr f76fbb80 S /system/bin/pluginservice
system 206 1 4276 684 atdev_ioct f7768b80 S /system/bin/startIpcsd
radio 207 1 6536 632 fmdev_fifo f76ecb80 S /system/bin/fmd
gps 208 1 4328 724 sigsuspend f7678b80 S /system/bin/sh
root 209 1 827376 32696 poll_sched f772eb80 S zygote
system 210 1 7364 1056 binder_thr f775cb80 S /system/bin/gatekeeperd
root 211 1 4240 616 hrtimer_na f7738b80 S /system/xbin/perfprofd
root 214 1 8100 1076 poll_sched f76fdb80 S /system/vendor/bin/crashlogd
root 215 1 6560 944 devkmsg_re f773bb80 S /vendor/bin/log-watch
root 218 2 0 0 worker_thr 00000000 S kworker/3:1H
root 221 1 3876 212 __skb_recv f76dab80 S daemonsu:mount:master
root 229 2 0 0 kjournald2 00000000 S jbd2/mmcblk0p5-
root 230 2 0 0 rescuer_th 00000000 S ext4-rsv-conver
root 247 1 7228 416 __skb_recv f76dab80 S daemonsu:master
root 252 2 0 0 rescuer_th 00000000 S cfg80211
gps 256 208 21528 2016 futex_wait f731fb80 S /system/bin/lbsd
radio 259 1 8300 732 nvmdev_ioc f76e9b80 S /system/bin/nvm_useragent
radio 262 1 15060 628 hrtimer_na f7783b80 S /system/bin/rpc-daemon
shell 263 1 10392 352 poll_sched f7761b80 S /sbin/adbd
root 327 2 0 0 irq_thread 00000000 S irq/289-gnss_wa
root 329 2 0 0 irq_thread 00000000 S irq/291-gnss_er
root 395 2 0 0 irq_thread 00000000 S irq/293-wlan_ir
root 532 1 4328 716 sigsuspend f7675b80 S /system/bin/sh
root 541 532 5316 860 __skb_recv f76dab80 S /system/vendor/bin/logcatext
system 575 209 898040 83068 SyS_epoll_ f772eb80 S system_server
root 701 2 0 0 mvpipe_dev 00000000 S VUSB_SE_FE_LINK
root 702 2 0 0 n_tty_read 00000000 S VUSB_SE_FE_LINK
root 703 2 0 0 msleep 00000000 D VUSB_SE_FE_MODE
root 736 2 0 0 rescuer_th 00000000 S vs-2
wifi 765 1 8788 2172 poll_sched f7509b80 S /system/bin/wpa_supplicant
media_rw 787 167 7896 912 inotify_re f7747b80 S /system/bin/sdcard
radio 800 209 696084 36216 SyS_epoll_ f772eb80 S com.android.phone
u0_a21 817 209 733912 46884 SyS_epoll_ f772eb80 S com.android.systemui
u0_a13 831 209 706448 53000 SyS_epoll_ f772eb80 S com.android.launcher
root 851 2 0 0 worker_thr 00000000 S kworker/3:2
media_rw 987 167 8156 716 inotify_re f778db80 S /system/bin/sdcard
u0_a76 1081 209 668624 25904 SyS_epoll_ f772eb80 S com.android.smspush
root 1123 2 0 0 worker_thr 00000000 S kworker/u9:2
u0_a9 1190 209 668636 26560 SyS_epoll_ f772eb80 S com.android.externalstorage
u0_a22 1336 209 953040 30864 SyS_epoll_ f772eb80 S com.google.android.googlequicksearchbox:interactor
u0_a43 1350 209 703316 48884 SyS_epoll_ f772eb80 S com.android.inputmethod.latin
system 1385 209 672148 28020 SyS_epoll_ f772eb80 S android.microntek.canbus
u0_a10 1417 209 845516 74952 SyS_epoll_ f772eb80 S com.google.android.gms.persistent
root 1431 1 4328 560 sigsuspend f772eb80 S /system/bin/sh
u0_a8 1438 209 681944 38376 SyS_epoll_ f772eb80 S android.process.media
u0_a10 1492 209 685848 32932 SyS_epoll_ f772eb80 S com.google.process.gapps
root 1497 1431 85112 360 poll_sched 40190422 S /system/bin/adb-ec
root 1503 2 0 0 rescuer_th 00000000 S vs-0
root 1530 1 4328 712 poll_sched f76adb80 S /system/bin/sh
u0_a10 1619 209 1046992 102860 SyS_epoll_ f772eb80 S com.google.android.gms
u0_a10 1708 209 825364 50108 SyS_epoll_ f772eb80 S com.google.android.gms.unstable
bluetooth 1752 209 719936 30080 SyS_epoll_ f772eb80 S com.android.bluetooth
root 1777 2 0 0 irq_thread 00000000 S irq/286-btif_mu
root 1778 2 0 0 irq_thread 00000000 S irq/288-btip_wa
root 1846 247 6196 416 __skb_recv f76dab80 S daemonsu:10087
u0_a60 2067 209 671340 30384 SyS_epoll_ f772eb80 S com.microntek.radio
system 2120 209 668872 29716 SyS_epoll_ f772eb80 S com.intel.soundprofile
u0_a39 2171 209 674544 31632 SyS_epoll_ f772eb80 S com.hct.screenbutton
u0_a40 2188 209 670856 27088 SyS_epoll_ f772eb80 S android.rockchip.update.service
u0_a37 2393 209 668748 25720 SyS_epoll_ f772eb80 S com.microntek.bluetooth
root 2893 247 7228 388 __skb_recv f76dab80 S daemonsu:10086
root 3090 1 649972 19408 futex_wait f76ceb80 S app_process
shell 3349 263 4328 1348 sigsuspend f7736b80 S /system/bin/sh
shell 3437 3349 3876 1164 poll_sched f778eb80 R su
root 3441 247 9292 484 __skb_recv f76dab80 S daemonsu:0
root 3443 3441 9548 944 poll_sched f76dab80 S daemonsu:0:3437
root 3549 3443 4328 1576 sigsuspend f7653b80 S tmp-mksh
root 3772 2 0 0 worker_thr 00000000 S kworker/1:0
root 3776 2 0 0 worker_thr 00000000 S kworker/0:0
u0_a85 3782 209 835136 72712 SyS_epoll_ f772eb80 S info.kfsoft.android.MemoryIndicator
shell 3913 263 4148 1364 __skb_recv f76e6b80 S logcat
root 3933 2 0 0 worker_thr 00000000 S kworker/u8:1
system 3972 209 726988 64328 SyS_epoll_ f772eb80 S com.android.settings
root 4013 2 0 0 worker_thr 00000000 S kworker/1:2
root 4014 2 0 0 worker_thr 00000000 S kworker/0:2
u0_a7 4019 209 669884 27748 SyS_epoll_ f772eb80 S com.android.defcontainer
root 4065 2 0 0 worker_thr 00000000 S kworker/u9:1
u0_a17 4069 209 934572 110068 SyS_epoll_ f772eb80 S com.android.vending
root 4115 2 0 0 worker_thr 00000000 S kworker/2:0
root 4136 2 0 0 worker_thr 00000000 S kworker/3:1
root 4180 3549 4224 1140 0 f776cb80 R ps
Click to expand...
Click to collapse

That's way over my head!
V5.11 is much better, but it wont play music, or nav sounds randomly, but the radio sounds always work?
I've put it back on V6.0.1 to get the music back, but nav randomly shuts down again.
I'm back to square one.
The seller has agreed to shipping back to Germany for full refund though.
It might be a good option!

OK, next steps now I've not identified a specific task killer is looking into Dalvik cache and VM settings, as perhaps these are too lean and causing the apps to run out and die like that (Still no message seeming to indicate this though).
Anyone any thoughts on tweaking these settings on a head unit? I'll grab my current values and my suggested ones for reference shortly.
--EDIT--
Ah, Dalvik was pre-4.0 and these are 6.0 Marshmallow so do the dalvik cache tweaks still do anything or do I need to look for ART tweaks instead?

still on 5.11 here, looks like disabling 'media audio' under bluetooth settings on my phone allows the head unit to route the music player to the speakers again, not sure why it was letting the radio audio through and not the music audio?

Am trying to get the Marshmallow release working so unfortunately not wanting to revert back to 5 or earlier.
However I'm making progress on 6.x
I believe it's the lowmemorykiller/ART that's getting in the way here, perhaps being set to be too aggressive at larger memory sizes.
I've installed a minfree memory kernel lowmemorykiller (it's easier than tweaking the params from adb shell) - App is "AutoKiller Memory Optimizer". I've not used any of it's other functions as this was the main one I wanted.
So after tweaks I'm running with:
Code:
cat /sys/module/lowmemorykiller/parameters/minfree
2754,5508,7344,13770,16065,18360
So far, running navigation (Google Maps) and then swapping back and forward to music and back, maps didn't close itself at all.
For some reason, music was stopping when switching to maps but I think that's more of an audio routing issue to look into, but so far it doesn't appear to be aggressively killing applications that have focus.
Some more logs that are interesting:
Code:
11-27 18:52:28.530 598 611 I art : Background partial concurrent mark sweep GC freed 21273(1447KB) AllocSpace objects, 3(60KB) LOS objects, 26% free, 11MB/15MB, paused 5.265ms total 141.023ms
11-27 18:52:31.112 6084 6095 I art : Background sticky concurrent mark sweep GC freed 2542(492KB) AllocSpace objects, 0(0B) LOS objects, 0% free, 11MB/11MB, paused 25.845ms total 89.939ms
11-27 18:52:31.185 6084 6095 I art : Background partial concurrent mark sweep GC freed 2011(210KB) AllocSpace objects, 0(0B) LOS objects, 24% free, 12MB/16MB, paused 11.725ms total 71.330ms
-- then after also launching music --
11-27 18:57:16.780 6235 6246 I art : Background sticky concurrent mark sweep GC freed 24160(1164KB) AllocSpace objects, 9(1440KB) LOS objects, 18% free, 12MB/15MB, paused 1.401ms total 112.708ms
11-27 18:57:16.833 6084 6095 I art : Background partial concurrent mark sweep GC freed 27088(1805KB) AllocSpace objects, 30(1196KB) LOS objects, 7% free, 49MB/53MB, paused 3.415ms total 310.197ms
I've also discovered some additional items when debugging, relating to standby, memory and the microntek applications but I'll post to a separate thread as will try and keep this thread on-track.
I'll report back after more extensive testing.

FIX/SOLVED
OK, after 30 minute drive this morning, I've had no app crashes or exits at all, ran maps with navigation and had FM radio on all the way, switched between apps using hard and soft back/keys, no problems, so I'm going to call this one the fix!
So the steps:
Root it
Install "AutoKiller Memory Optimizer" by MobiWIA Kft.
In AutoKiller switch everything OFF but then use the CHANGE button on main screen, set it to MODERATE (Or experiment with different ones)
Remember that needs set after full reboot (standby is fine) unless you add it to autostart at boot.
@Qwertyco I'd go back up to 6 and try the above, might solve the issues for you!

Cheers Andy.
After playing with 5.11 for a few days, it's become apparent that It has sound routing problems whenever
there's a Bluetooth connection to my phone. (Moto G5 on Android 7). The only way I can get music or nav
sound (radio is always Ok!) is to have the connection as 'Internet sharing only', no phone or contacts or A2DP.
It also needs regular rebooting to achieve this, as returning from sleep sometimes messes with the sound routing as well.
I'm going to try going back to 6.0.1, and try the new HIZPO 2017.09.15 update file first before I try your fix.

I updated back to 6.0.1, and tried the HIZPO 2017.09.15 update file, and it just aborted the update after 5 seconds.
I'll have a look at it and try again another time.

I'm back, not used the car for a while, so not had a chance to play.
Andy, what's the rooting procedure, if you don't mind?

Hi, no problem same here as the car has been dead for a while here unfortunately!
I've written a lot of the info up at my blog http://www.thebmwz3.co.uk/2017/11/hizpo-android-car-head-unit-mtcdxrc.html
But rooting is:
* Go into factory settings in Settings menu
* type adbon into the password box and click OK
Try at that point, you should be able to get adb working over wifi. If not, install a terminal app to the head unit and then type "setprop persist.adb.tcp.port 5555" and then reboot the unit. You should then be able to adb over wifi.
Then you can root it using the root procedure at https://hvdwolf.github.io/Joying-RootAssistant/rooting.html and I used the file SuperSU-Joying-Intel-v2.82SR1-patch2.zip which worked first time.

Thanks to Andy and others, I've gone back to Android 6.01 and rooted the thing, followed Andy's tips and it seems to be running fairly smoothly for the first time ever.
I've done all this with the unit on the workbench (coffee table) as it's cold outside!
I can't test the sat nav indoors, but it seems to start up and keep running now.
My mission is to get it to do everything I want it to do before it goes back in the car.
Currently struggling with getting it to auto-tether to my phone Bluetooth, and getting apps to autostart at boot.
I can't seem to find any mention of autorun in the software, and the many autorun apps I've tried don't autorun at boot!

Hey m8, glad you're getting there. It's been in my car for quite a few months now, running smoothly!
So, for the auto-tethering bluetooth I've done this:
Get BluetoothTethering.apk from 'doitright' at https://forum.xda-developers.com/an...elopment/bluetooth-settings-launcher-t3504526 (Don't get blueballs, we don't need it) and follow the instructions to install it onto our headunits (i.e. the bit in the terminal/code block where you write it to /system/priv-app/). I've followed those instructions and my phone (HTC One M8) and car bring their bluetooth up and tether perfectly each time now.
Autorun at boot/wake-up is still a little challenging, however the trick is the one that BluetoothTethering.apk uses above, installing the app into priv-app lets it keep running in the background/at wakeup so the key is there, I've just never bothered to really go further into it.
To do the low-mem-killer settings, since our units don't reboot often I just do that manually, as there isn't an rc.local or bootup script that I've located that I can chain those commands into, but then again I've not tried very hard as it's working for me now!
I use Waze, Google Maps, Music, Radio all swapping between them without crashes. Sure it's not the fastest thing in the world but it works

Thanks Andy, I'll have a go at the tethering app.
The two apps I want to autostart are a night screen dimmer and a speed sensitive volume controller. The priv-app location may well solve that.!
I'll report back.....

Those sound interesting apps, which ones are you using as I'm always on the lookout for decent addons!
Also just be careful having more and more apps running in the background, we've not got a huge amount of RAM/Processor to play with!

well the Bluetooth is now auto connecting, many thanks again to Andy.
After an abortive attempt on my windows 10 laptop, I finally got the ADB to work from my old windows 7 PC over WiFi.
Playing about with these two at the moment:
This:
https://play.google.com/store/apps/details?id=net.codechunk.speedofsound&hl=en
and this:
https://play.google.com/store/apps/details?id=com.urbandroid.lux&hl=en
I just realised I seem to be working without using the "AutoKiller Memory Optimizer", as if it doesn't autostart on boot, I've not been manually starting it?

Thanks @Qwertyco I'll take a look at those two apps.
The autokiller optimizer, once it's ran once, those settings will stick until a full hard reboot/power disconnect not just standby when you turn ignition off, so chances are that's why it's kept working for you so far.

Update:
After doing all the stuff Andy sugested, it's running much better now, and rarely does anything random or unexpected anymore.
I's still anoying me in various ways though, the main thing being that everytime it starts up the music palyer plays the first track of the first album EVERYTIME! This happens to be AC/DC - Hells Bells, which is wearing a bit thin now. It rarely does an 'quick resume' and almost always takes a full boot time to start playing music.
Any Ideas out there?