Sysprogs forums › Forums › VisualGDB › Amazon TV debugging
- This topic has 9 replies, 3 voices, and was last updated 10 years, 6 months ago by support.
-
AuthorPosts
-
April 28, 2014 at 15:46 #817John GabyParticipant
I am trying to debug my app on Amazon Fire TV which uses a network connection for ADB. When I try and debug, it gives me the error ‘The given path’s format is not supported.’ The following is the ‘ADB log’. Is there any way to make this work?
Thanks.
c:android-sdkplatform-toolsadb.exe devices
List of devices attached
192.168.0.141:5555 device
Command exited with code 0
c:android-sdkplatform-toolsadb.exe -s 192.168.0.141:5555 shell ps
USER PID PPID VSIZE RSS WCHAN PC NAME
root 1 0 480 344 ffffffff 00000000 S /init
root 2 0 0 0 ffffffff 00000000 S kthreadd
root 3 2 0 0 ffffffff 00000000 S ksoftirqd/0
root 6 2 0 0 ffffffff 00000000 S migration/0
root 10 2 0 0 ffffffff 00000000 S khelper
root 11 2 0 0 ffffffff 00000000 S suspend_sys_syn
root 12 2 0 0 ffffffff 00000000 S suspend
root 15 2 0 0 ffffffff 00000000 S irq/203-msmdata
root 16 2 0 0 ffffffff 00000000 S sync_supers
root 17 2 0 0 ffffffff 00000000 S bdi-default
root 18 2 0 0 ffffffff 00000000 S kblockd
root 19 2 0 0 ffffffff 00000000 S khubd
root 20 2 0 0 ffffffff 00000000 S irq/84-msm_iomm
root 21 2 0 0 ffffffff 00000000 S irq/84-msm_iomm
root 22 2 0 0 ffffffff 00000000 S irq/96-msm_iomm
root 23 2 0 0 ffffffff 00000000 S irq/96-msm_iomm
root 24 2 0 0 ffffffff 00000000 S irq/94-msm_iomm
root 25 2 0 0 ffffffff 00000000 S irq/94-msm_iomm
root 26 2 0 0 ffffffff 00000000 S irq/92-msm_iomm
root 27 2 0 0 ffffffff 00000000 S irq/92-msm_iomm
root 28 2 0 0 ffffffff 00000000 S irq/100-msm_iom
root 29 2 0 0 ffffffff 00000000 S irq/100-msm_iom
root 30 2 0 0 ffffffff 00000000 S irq/86-msm_iomm
root 31 2 0 0 ffffffff 00000000 S irq/86-msm_iomm
root 32 2 0 0 ffffffff 00000000 S irq/90-msm_iomm
root 33 2 0 0 ffffffff 00000000 S irq/90-msm_iomm
root 34 2 0 0 ffffffff 00000000 S irq/88-msm_iomm
root 35 2 0 0 ffffffff 00000000 S irq/102-msm_iom
root 36 2 0 0 ffffffff 00000000 S irq/102-msm_iom
root 37 2 0 0 ffffffff 00000000 S irq/98-msm_iomm
root 38 2 0 0 ffffffff 00000000 S irq/98-msm_iomm
root 39 2 0 0 ffffffff 00000000 S irq/243-msm_iom
root 40 2 0 0 ffffffff 00000000 S irq/243-msm_iom
root 41 2 0 0 ffffffff 00000000 S irq/269-msm_iom
root 42 2 0 0 ffffffff 00000000 S irq/269-msm_iom
root 43 2 0 0 ffffffff 00000000 S l2cap
root 44 2 0 0 ffffffff 00000000 S a2mp
root 45 2 0 0 ffffffff 00000000 S cfg80211
root 46 2 0 0 ffffffff 00000000 S rpciod
root 47 2 0 0 ffffffff 00000000 S modem_notifier
root 48 2 0 0 ffffffff 00000000 S smd_channel_clo
root 49 2 0 0 ffffffff 00000000 S smsm_cb_wq
root 51 2 0 0 ffffffff 00000000 S qmi
root 52 2 0 0 ffffffff 00000000 S nmea
root 53 2 0 0 ffffffff 00000000 S msm_ipc_router
root 54 2 0 0 ffffffff 00000000 S apr_driver
root 55 2 0 0 ffffffff 00000000 S kswapd0
root 56 2 0 0 ffffffff 00000000 S fsnotify_mark
root 57 2 0 0 ffffffff 00000000 S nfsiod
root 58 2 0 0 ffffffff 00000000 S cifsiod
root 59 2 0 0 ffffffff 00000000 S crypto
root 73 2 0 0 ffffffff 00000000 S mdp_dma_wq
root 74 2 0 0 ffffffff 00000000 S mdp_vsync_wq
root 75 2 0 0 ffffffff 00000000 S mdp_pipe_ctrl_w
root 76 2 0 0 ffffffff 00000000 S mdp_cursor_ctrl
root 77 2 0 0 ffffffff 00000000 S hdmi_hdcp
root 78 2 0 0 ffffffff 00000000 S irq/111-hdmi_ms
root 79 2 0 0 ffffffff 00000000 S dtv_work
root 80 2 0 0 ffffffff 00000000 S vidc_worker_que
root 81 2 0 0 ffffffff 00000000 S vidc_timer_wq
root 82 2 0 0 ffffffff 00000000 S smux_notify_wq
root 83 2 0 0 ffffffff 00000000 S smux_tx_wq
root 84 2 0 0 ffffffff 00000000 S smux_rx_wq
root 85 2 0 0 ffffffff 00000000 S smux_loopback_w
root 86 2 0 0 ffffffff 00000000 S k_hsuart
root 87 2 0 0 ffffffff 00000000 S diag_wq
root 88 2 0 0 ffffffff 00000000 S hsic_diag_wq
root 89 2 0 0 ffffffff 00000000 S hsic_2_diag_wq
root 90 2 0 0 ffffffff 00000000 S smux_diag_wq
root 91 2 0 0 ffffffff 00000000 S diag_cntl_wq
root 92 2 0 0 ffffffff 00000000 S diag_dci_wq
root 94 2 0 0 ffffffff 00000000 S kgsl-3d0
root 95 2 0 0 ffffffff 00000000 S spi_qsd.2
root 96 2 0 0 ffffffff 00000000 S usbnet
root 99 2 0 0 ffffffff 00000000 S mdm_bridge
root 100 2 0 0 ffffffff 00000000 S ks_bridge:1
root 101 2 0 0 ffffffff 00000000 S ks_bridge:2
root 102 2 0 0 ffffffff 00000000 S ks_bridge:3
root 103 2 0 0 ffffffff 00000000 S ks_bridge:4
root 104 2 0 0 ffffffff 00000000 S k_rmnet_mux_wor
root 105 2 0 0 ffffffff 00000000 S f_mtp
root 106 2 0 0 ffffffff 00000000 S file-storage
root 107 2 0 0 ffffffff 00000000 S uether
root 108 2 0 0 ffffffff 00000000 S kpsmoused
root 109 2 0 0 ffffffff 00000000 D dbs_sync/0
root 110 2 0 0 ffffffff 00000000 D dbs_sync/1
root 111 2 0 0 ffffffff 00000000 D dbs_sync/2
root 112 2 0 0 ffffffff 00000000 D dbs_sync/3
root 113 2 0 0 ffffffff 00000000 D kinteractiveup
root 115 2 0 0 ffffffff 00000000 S irq/662-msm-sdc
root 116 2 0 0 ffffffff 00000000 S binder
root 119 2 0 0 ffffffff 00000000 S mmcqd/0
root 120 2 0 0 ffffffff 00000000 S mmcqd/0boot0
root 121 2 0 0 ffffffff 00000000 S mmcqd/0boot1
root 122 2 0 0 ffffffff 00000000 S krfcommd
root 123 2 0 0 ffffffff 00000000 S msm-cpufreq
root 124 2 0 0 ffffffff 00000000 S rq_stats
root 125 2 0 0 ffffffff 00000000 S deferwq
root 126 2 0 0 ffffffff 00000000 D msm_dcvs/1
root 127 2 0 0 ffffffff 00000000 D msm_dcvs/2
root 128 2 0 0 ffffffff 00000000 D msm_dcvs/3
root 129 2 0 0 ffffffff 00000000 D msm_dcvs/4
root 130 1 384 200 ffffffff 00000000 S /sbin/ueventd
root 133 2 0 0 ffffffff 00000000 S jbd2/mmcblk0p18
root 134 2 0 0 ffffffff 00000000 S ext4-dio-unwrit
root 139 2 0 0 ffffffff 00000000 S jbd2/mmcblk0p20
root 140 2 0 0 ffffffff 00000000 S ext4-dio-unwrit
root 144 2 0 0 ffffffff 00000000 S jbd2/mmcblk0p1-
root 145 2 0 0 ffffffff 00000000 S ext4-dio-unwrit
root 146 2 0 0 ffffffff 00000000 S jbd2/mmcblk0p19
root 147 2 0 0 ffffffff 00000000 S ext4-dio-unwrit
system 264 1 1292 464 ffffffff 00000000 S /system/bin/servicemanager
root 265 1 4352 868 ffffffff 00000000 S /system/bin/vold
bluetooth 268 1 1720 1108 ffffffff 00000000 S /system/bin/dbus-daemon
system 270 1 2480 712 ffffffff 00000000 S /system/bin/qseecomd
root 271 1 11004 1704 ffffffff 00000000 S /system/bin/netd
root 272 1 6584 1872 ffffffff 00000000 S /system/bin/debuggerd
system 274 1 94712 9556 ffffffff 00000000 S /system/bin/surfaceflinger
root 275 1 466552 38836 ffffffff 00000000 S zygote
drm 276 1 17084 3480 ffffffff 00000000 S /system/bin/drmserver
media 277 1 60016 11488 ffffffff 00000000 S /system/bin/mediaserver
install 278 1 1460 828 ffffffff 00000000 S /system/bin/installd
keystore 279 1 2112 936 ffffffff 00000000 S /system/bin/keystore
root 283 1 28328 1036 ffffffff 00000000 S /system/bin/thermald
camera 287 1 7500 2232 ffffffff 00000000 S /system/bin/mm-qcamera-daemon
system 288 1 8288 2456 ffffffff 00000000 S /system/bin/cnd
system 291 1 2540 728 ffffffff 00000000 S /system/bin/mm-pp-daemon
nobody 294 1 2492 708 ffffffff 00000000 S /system/bin/rmt_storage
media_rw 295 1 3000 704 ffffffff 00000000 S /system/bin/sdcard
shell 296 1 8664 300 ffffffff 00000000 S /sbin/adbd
root 305 2 0 0 ffffffff 00000000 S k_gserial
root 306 2 0 0 ffffffff 00000000 S k_gsmd
root 308 2 0 0 ffffffff 00000000 S k_gbam
root 311 2 0 0 ffffffff 00000000 S gsmd_ctrl
root 366 2 0 0 ffffffff 00000000 S kworker/0:0
system 372 270 4584 520 ffffffff 00000000 S /system/bin/qseecomd
root 536 1 2280 168 ffffffff 00000000 S /system/bin/cecdaemon
root 635 2 0 0 ffffffff 00000000 S IPCRTR
root 636 2 0 0 ffffffff 00000000 S ipc_rtr_q6_ipcr
system 648 275 591692 55472 ffffffff 00000000 S system_server
root 718 2 0 0 ffffffff 00000000 S ehci_wq
root 720 2 0 0 ffffffff 00000000 S irq/337-hsic_pe
root 721 2 0 0 ffffffff 00000000 S ath6kl
log 734 1 1164 484 ffffffff 00000000 S /system/bin/logwrapper
wifi 736 734 3044 1808 ffffffff 00000000 S /system/bin/wpa_supplicant
amz_a28 791 275 486016 27088 ffffffff 00000000 S com.amazon.dcp:OSMetrics
amz_a3 820 275 479688 32704 ffffffff 00000000 S com.amazon.tv.ime
system 839 275 482312 24864 ffffffff 00000000 S com.amazon.bueller.notification
amz_a6 852 275 477268 21360 ffffffff 00000000 S android.process.acore
amz_a12 864 275 490304 27948 ffffffff 00000000 S com.amazon.device.logmanager
amz_a16 879 275 506216 27624 ffffffff 00000000 S com.amazon.client.metrics
system 889 275 473912 17820 ffffffff 00000000 S com.amazon.tz.webcryptotzservice
amz_a54 901 275 501108 31720 ffffffff 00000000 S com.amazon.tcomm
amz_a23 912 275 545304 36300 ffffffff 00000000 S com.amazon.whisperlink.core.android
amz_a9 939 275 481580 22244 ffffffff 00000000 S com.android.providers.downloads
amz_a42 953 275 485340 28076 ffffffff 00000000 S com.amazon.imp
amz_a5 966 275 480216 25096 ffffffff 00000000 S android.process.media
amz_a46 978 275 700796 122924 ffffffff 00000000 S com.amazon.tv.launcher
amz_a10 1005 275 473892 18276 ffffffff 00000000 S com.android.location.fused
amz_a43 1034 275 519172 39792 ffffffff 00000000 S com.amazon.kindle.cms
amz_a34 1115 275 488040 28912 ffffffff 00000000 S com.amazon.device.messaging:TPHService
amz_a0 1180 275 590720 79168 ffffffff 00000000 S com.amazon.venezia
amz_a46 1236 275 516744 37164 ffffffff 00000000 R com.amazon.tv.launcher:GlobalNavProcess
amz_a16 1278 879 1172 484 ffffffff 00000000 S logcat
amz_a26 1375 275 568308 66216 ffffffff 00000000 S com.amazon.avod
amz_a28 1394 275 491432 32964 ffffffff 00000000 S com.amazon.dcp:OTAService
bluetooth 1579 275 488488 22944 ffffffff 00000000 S com.android.bluetooth
system 1650 275 510600 46564 ffffffff 00000000 S com.amazon.bueller.settings
root 1700 1 6600 780 ffffffff 00000000 S /system/bin/mpdecision
bluetooth 1715 1 1340 708 ffffffff 00000000 S /system/bin/sh
bluetooth 1734 1715 2288 700 ffffffff 00000000 S /system/xbin/hciattach
root 1737 2 0 0 ffffffff 00000000 S irq/303-msm_hs_
root 1839 2 0 0 ffffffff 00000000 S hci0
log 1851 1 1164 484 ffffffff 00000000 S /system/bin/logwrapper
root 1854 1 1564 592 ffffffff 00000000 S /system/bin/btremoted
bluetooth 1855 1851 2780 1844 ffffffff 00000000 S /system/bin/bluetoothd
bluetooth 1958 1 1348 764 ffffffff 00000000 S /system/bin/sh
bluetooth 1969 1958 8372 1384 ffffffff 00000000 S /system/bin/abtfilt
root 2460 2 0 0 ffffffff 00000000 S kworker/u:0
root 2461 2 0 0 ffffffff 00000000 S kworker/0:2
amz_a6 3848 275 474084 18016 ffffffff 00000000 S com.amazon.device.controllermanager:BluetoothReceiver
root 3860 2 0 0 ffffffff 00000000 S khidpd_19490401
amz_a2 3921 275 474304 18444 ffffffff 00000000 S com.amazon.tv.device
amz_a32 3991 275 481776 22324 ffffffff 00000000 S com.amazon.device.gmo
root 4046 2 0 0 ffffffff 00000000 S kworker/0:1
amz_a28 4367 275 483952 29652 ffffffff 00000000 S com.amazon.dcp
system 4492 275 476192 22784 ffffffff 00000000 S com.qualcomm.wfd.service:wfd_service
dhcp 4573 1 1264 592 ffffffff 00000000 S /system/bin/dhcpcd
amz_a8 4624 275 474924 17988 ffffffff 00000000 S com.android.defcontainer
u0_a4 4676 275 482504 39500 ffffffff 00000000 S com.gabysoft.flippixaaa
root 5334 2 0 0 ffffffff 00000000 S migration/1
root 5335 2 0 0 ffffffff 00000000 S kworker/1:3
root 5336 2 0 0 ffffffff 00000000 S ksoftirqd/1
root 5344 2 0 0 ffffffff 00000000 S kworker/1:1
root 6019 2 0 0 ffffffff 00000000 S kworker/0:3
amz_a50 6301 275 556992 49420 ffffffff 00000000 S com.amazon.bueller.photos:slideshow
root 6313 2 0 0 ffffffff 00000000 S kworker/1:0
root 6362 2 0 0 ffffffff 00000000 S kworker/u:2
shell 6592 296 1332 708 c0108a6c 4035e9fc S /system/bin/sh
shell 6594 6592 1428 592 00000000 402a4dd8 R ps
amz_a50 8610 275 550104 59340 ffffffff 00000000 S com.amazon.bueller.photos
root 9923 2 0 0 ffffffff 00000000 S flush-179:0
amz_a37 14750 275 486516 30628 ffffffff 00000000 S com.amazon.device.settings:Settings
root 23895 2 0 0 ffffffff 00000000 R kworker/u:1
amz_a52 30009 275 483496 23952 ffffffff 00000000 S com.amazon.storm.lightning.services
shell 31056 296 1332 708 c0108a6c 401e89fc S /system/bin/sh
shell 31058 31056 1672 1120 c022fd74 40209194 S logcat
amz_a24 32366 275 488716 24680 ffffffff 00000000 S com.amazon.whisperplay.cds:cds_services
Command exited with code 0April 28, 2014 at 18:47 #3154ketParticipantHi,
If the device shows up for ADB, then it should be possible to debug the device. However more exotic Android-based devices can have issues with their images that can accidentally or deliberately break the debugging possibility.
Based on this error message, it is thrown by VisualGDB itself due to something unexpected during launch. The ADB log looks fine and does not contain anything unusual. Please go to Tools->Options->VisualGDB and enable verbose output from there. Then please look in the Output window and change the filter there to show output from VisualGDB Launcher Output, then give us this log.
Also, are you trying to debug com.gabysoft.flippixaaa or some other app? Does just deploying or launching the app (Android menu commands) without debugging work?April 28, 2014 at 20:00 #3155John GabyParticipantHmm, there does not seem to be a ‘VisualGDB’ option under Tools->Options.
Yes, I am debugging com.gabysoft.flipixaaa. I am able to install the app and debug the Java portion using Eclipse. The app mostly runs fine on the Amazon TV box, but there are some issues that I am trying to debug.
Thanks.
April 29, 2014 at 17:48 #3156ketParticipantHi,
Strange that the VisualGDB options do not appear, which version of VisualGDB are you using? However, the verbose option from the options does not make the log appear, it just adds a bit more detail. Do you have a VisualGDB Launcher Output log available from the Output window?
Java debugging and native debugging work differently, based on the current error it is too early to tell whether native debugging will work. The current error is probably something we can adjust to in VisualGDB, but we need to know at which stage of launching it happens.
April 30, 2014 at 02:54 #3157John GabyParticipantI am using version 2.7. After I dismiss the ‘Failed to start Android app’ dialog box, the Output window is empty.
April 30, 2014 at 04:17 #3158ketParticipantHi,
Much has changed about VisualGDB since version 2.7, including the global verbose option and the launcher log that we would really need to see in this case. It could also be that you are experiencing an issue in VisualGDB that was fixed in newer versions. Also, any change to VisualGDB we would make would be released in a 4.1r release or in the upcoming 4.2 version of VisualGDB.
Please contact our sales team for a license renewal quote or trial extension code, so you could try the latest VisualGDB version before renewing. You could also try to see if using the newest version released during your one year support period works, but if there are issues, then any change would be released in the new version of VisualGDB and that issue should be replicable with the latest release of VisualGDB.
April 30, 2014 at 13:47 #3159John GabyParticipantI would be willing to upgrade my version if I were sure that it would fix the problem. Installing a trial version is not very attractive because if it didn’t fix the problem, I would be stuck with a version that will time out. Do you know of anyone who has successfully used it with the Amazon Fire TV box?
Thanks.
April 30, 2014 at 17:58 #3160ketParticipantHi,
We usually hear what devices VisualGDB users are using if there any issues. As we have not heard of any users using the Amazon Fire TV box, that could mean two things. Unfortunately, there is no way of knowing until you try it out yourself with a newer version of VisualGDB.
If you switch to a trial, you will be able to still switch back to the old version of VisualGDB you were using before. Since VisualGDB 4.x has a newer project settings format, a back-up copy of your older settings will be made before converting. Also if there is an issue that we can fix within VisualGDB, then we would also likely have a fix out before your trial expires.
April 30, 2014 at 21:49 #3161John GabyParticipantWhat I have now works on most devices, and I am deathly afraid of screwing that up and not being able to go back. I think I might try installing on another computer first. Thanks for your help.
May 2, 2014 at 18:09 #3162supportKeymasterHi,
You can always revert back to VisualGDB 2.x (just replace the version number in the download URL on our website). Additionally you can backup the following directories:
%LOCALAPPDATA%VisualGDB
%APPDATA%VisualGDB
Your android tools directories
Your project directories
Registry ({HKLM, HKCU}SoftwareSysprogsVisualGDB)VisualGDB does not store anything critical anywhere else, so if things go wrong, you can simply recover those directories.
-
AuthorPosts
- You must be logged in to reply to this topic.