[WFX] Android ADB 8.8

[mas912]

Excellent plugin.
Only one issue: can you handle the disconnects? For example, if debugged device turned off WiFi. Now TC is freezed in these situations :(

[jakubklos]

Excellent plugin.
Only one issue: can you handle the disconnects? For example, if debugged device turned off WiFi. Now TC is freezed in these situations

Does not happen to me . Anyway, there is nothing to do here. It must be network related. Your PC sockets do not recognize the device connection is down and this is how it behaves. There is no really way to deal with this. For me on Windows as soon as the device is unreachable (Wifi is off) the connection terminates instantly.

[jakubklos]

A new version has just been released:

4.0
- New: Auto connect for WiFI ADB support, works well with bookmarks - you create a new bookmark and then simply open the folder, it will automatically attempt to connect to that device (without Connect To Device) if not already connected
- New: Bookmarks support added (for WiFI ADB only) - Use F7 to create a new device bookmark (name it and then specify the connect to device value), in order to remove the bookmark do not use F8 (it will delete all your files in the device), rename to "." instead - that will clear renamed devices and also remove bookmarks
- Fix: Clear renamed device (rename to ".") fixed, data is saved

[Dreamer]

Can't remember IP:port after ADBwireless restarted.

Sorry, 4.0 doesn't have this problem.

[Dreamer]

Suggestion: SMS from PC.

[mas912]

Your PC sockets do not recognize the device connection is down and this is how it behaves. There is no really way to deal with this.

When wifi connection is down, "adb devices" returns empty output, so it can be detected at least by that way. I'll check 4.0 version.

[baturin]

Hello!

I have installed ADB plugin (different versions, 32 bit TC now on win8 x64, but some time ago on win7 x64 wit the same problem), it can see the android device connected via usb (SGSII), but I am not able to upload, rename, create folders anywhere (through ADB plugin). The device should be rooted properly (apps which require root are working smoothly).

What can be a reason of such behavior?
Thanks in advance!

[jakubklos]

Hello!

I have installed ADB plugin (different versions, 32 bit TC now on win8 x64, but some time ago on win7 x64 wit the same problem), it can see the android device connected via usb (SGSII), but I am not able to upload, rename, create folders anywhere (through ADB plugin). The device should be rooted properly (apps which require root are working smoothly).

What can be a reason of such behavior?
Thanks in advance!

Hi,
frankly I don't know. You should be able to make any changes on your sdcard.
It would be best if you send me your debug logs. That will tell me exactly what is going on there. Either it is permission based or there is some other problem...
Let me know

[jakubklos]

Proudly present the new version 4.5 with the backup and restore functionality. ICS is required for this feature and it works really nice.

It was only recently that I discovered ICS supports backup and restore without root required. The command line adb tool is quite complex and supports multiple parameters. That is why I decided a nice dialog with all the features and even a list of available packages to backup would be nice.

Hope you like. Enjoy!

[shaamt]

Proudly present the new version 4.5 with the backup and restore functionality. ICS is required for this feature and it works really nice.

It was only recently that I discovered ICS supports backup and restore without root required. The command line adb tool is quite complex and supports multiple parameters. That is why I decided a nice dialog with all the features and even a list of available packages to backup would be nice.

Hope you like. Enjoy!

I'm having problem with the backup system using my android HP as follows:

Model number: I9100
CPU: MTK6573
Android version: 4.0.9
Baseband version: I9100XXK13
Kernel version: 2.6.35.7-I9100
Build number: GT_I9100_01
Custom build version: 1341280728
ADB Devices: 0123456789ABCDEF

After clicking backup an error message will appear "Backup operation failure".
Do you have any suggestion or clues on the problem. BTW my phone is unrooted and there are no ways to root my phone other then to flash it. I was planning to do full backup before i flash it and your new 4.5 version seem to be the right candidate for the job. The backup log are as follows:

2012-10-10 16:10:09 [128C] Connecting to ADB server...
2012-10-10 16:10:09 [128C] Connected
2012-10-10 16:10:09 [128C] ADB Write: host:devices
2012-10-10 16:10:09 [128C] ADB Read: 0123456789ABCDEF device
2012-10-10 16:11:45 [128C] Connecting to ADB server...
2012-10-10 16:11:45 [128C] Connected
2012-10-10 16:11:46 [128C] ADB Write: host:transport:0123456789ABCDEF
2012-10-10 16:11:46 [128C] ADB Read: OKAY
2012-10-10 16:11:46 [128C] ADB Write: shell:ls -l "/"
2012-10-10 16:11:46 [128C] ADB Read: OKAY
2012-10-10 16:11:46 [128C] ADB Read Data: dr-x------ root root 2012-10-10 13:55 config
drwxrwx--- system cache 2012-10-10 12:13 cache
lrwxrwxrwx root root 2012-10-10 13:55 sdcard -> /mnt/sdcard
drwxr-xr-x root root 2012-10-10 13:55 acct
drwxrwxr-x root system 2012-10-10 13:55 mnt
lrwxrwxrwx root root 2012-10-10 13:55 vendor -> /system/vendor
lrwxrwxrwx root root 2012-10-10 13:55 d -> /sys/kernel/debug
lrwxrwxrwx root root 2012-10-10 13:55 etc -> /system/etc
-rw-r--r-- root root 3950 1970-01-01 07:30 ueventd.rc
-rw-r--r-- root root 0 1970-01-01 07:30 ueventd.goldfish.rc
drwxr-xr-x root root 2010-01-01 08:02 system
drwxr-xr-x root root 2012-10-10 13:55 sys
drwxr-x--- root root 1970-01-01 07:30 sbin
lrwxrwxrwx root root 1970-01-01 07:30 res -> /system/res
dr-xr-xr-x root root 1970-01-01 07:30 proc
-rw-r--r-- root root 7010 1970-01-01 07:30 meta_init.rc
-rwxr-x--- root root 25267 1970-01-01 07:30 init.rc
-rwxr-x--- root root 1677 1970-01-01 07:30 init.goldfish.rc
-rwxr-x--- root root 9618 1970-01-01 07:30 init.factory.rc
-rwxr-x--- root root 98352 1970-01-01 07:30 init
-rw-r--r-- root root 141 1970-01-01 07:30 default.prop
drwxrwx--x system system 2012-10-10 01:39 data
-rw-r--r-- root root 20964 1970-01-01 07:30 advanced_meta_init.rc
drwx------ root root 2012-08-09 12:59 root
drwxr-xr-x root root 2012-10-10 13:55 dev
2012-10-10 16:12:04 [0CE4] Connecting to ADB server...
2012-10-10 16:12:04 [0CE4] Connected
2012-10-10 16:12:04 [0CE4] ADB Write: host:transport:0123456789ABCDEF
2012-10-10 16:12:04 [0CE4] ADB Read: OKAY
2012-10-10 16:12:04 [0CE4] ADB Write: backup:-noapk:-noshared:-nosystem:-all
2012-10-10 16:12:04 [0CE4] ADB Read: closed
2012-10-10 16:12:14 [128C] Connecting to ADB server...
2012-10-10 16:12:14 [128C] Connected
2012-10-10 16:12:14 [128C] ADB Write: host:devices
2012-10-10 16:12:14 [128C] ADB Read: 0123456789ABCDEF device

Your help is greatly appreciated.

[jakubklos]

Proudly present the new version 4.5 with the backup and restore functionality. ICS is required for this feature and it works really nice.

It was only recently that I discovered ICS supports backup and restore without root required. The command line adb tool is quite complex and supports multiple parameters. That is why I decided a nice dialog with all the features and even a list of available packages to backup would be nice.

Hope you like. Enjoy!

I'm having problem with the backup system using my android HP as follows:

Model number: I9100
CPU: MTK6573
Android version: 4.0.9
Baseband version: I9100XXK13
Kernel version: 2.6.35.7-I9100
Build number: GT_I9100_01
Custom build version: 1341280728
ADB Devices: 0123456789ABCDEF

After clicking backup an error message will appear "Backup operation failure".
Do you have any suggestion or clues on the problem. BTW my phone is unrooted and there are no ways to root my phone other then to flash it. I was planning to do full backup before i flash it and your new 4.5 version seem to be the right candidate for the job. The backup log are as follows:

2012-10-10 16:10:09 [128C] Connecting to ADB server...
2012-10-10 16:10:09 [128C] Connected
2012-10-10 16:10:09 [128C] ADB Write: host:devices
2012-10-10 16:10:09 [128C] ADB Read: 0123456789ABCDEF device
2012-10-10 16:11:45 [128C] Connecting to ADB server...
2012-10-10 16:11:45 [128C] Connected
2012-10-10 16:11:46 [128C] ADB Write: host:transport:0123456789ABCDEF
2012-10-10 16:11:46 [128C] ADB Read: OKAY
2012-10-10 16:11:46 [128C] ADB Write: shell:ls -l "/"
2012-10-10 16:11:46 [128C] ADB Read: OKAY
2012-10-10 16:11:46 [128C] ADB Read Data: dr-x------ root root 2012-10-10 13:55 config
drwxrwx--- system cache 2012-10-10 12:13 cache
lrwxrwxrwx root root 2012-10-10 13:55 sdcard -> /mnt/sdcard
drwxr-xr-x root root 2012-10-10 13:55 acct
drwxrwxr-x root system 2012-10-10 13:55 mnt
lrwxrwxrwx root root 2012-10-10 13:55 vendor -> /system/vendor
lrwxrwxrwx root root 2012-10-10 13:55 d -> /sys/kernel/debug
lrwxrwxrwx root root 2012-10-10 13:55 etc -> /system/etc
-rw-r--r-- root root 3950 1970-01-01 07:30 ueventd.rc
-rw-r--r-- root root 0 1970-01-01 07:30 ueventd.goldfish.rc
drwxr-xr-x root root 2010-01-01 08:02 system
drwxr-xr-x root root 2012-10-10 13:55 sys
drwxr-x--- root root 1970-01-01 07:30 sbin
lrwxrwxrwx root root 1970-01-01 07:30 res -> /system/res
dr-xr-xr-x root root 1970-01-01 07:30 proc
-rw-r--r-- root root 7010 1970-01-01 07:30 meta_init.rc
-rwxr-x--- root root 25267 1970-01-01 07:30 init.rc
-rwxr-x--- root root 1677 1970-01-01 07:30 init.goldfish.rc
-rwxr-x--- root root 9618 1970-01-01 07:30 init.factory.rc
-rwxr-x--- root root 98352 1970-01-01 07:30 init
-rw-r--r-- root root 141 1970-01-01 07:30 default.prop
drwxrwx--x system system 2012-10-10 01:39 data
-rw-r--r-- root root 20964 1970-01-01 07:30 advanced_meta_init.rc
drwx------ root root 2012-08-09 12:59 root
drwxr-xr-x root root 2012-10-10 13:55 dev
2012-10-10 16:12:04 [0CE4] Connecting to ADB server...
2012-10-10 16:12:04 [0CE4] Connected
2012-10-10 16:12:04 [0CE4] ADB Write: host:transport:0123456789ABCDEF
2012-10-10 16:12:04 [0CE4] ADB Read: OKAY
2012-10-10 16:12:04 [0CE4] ADB Write: backup:-noapk:-noshared:-nosystem:-all
2012-10-10 16:12:04 [0CE4] ADB Read: closed
2012-10-10 16:12:14 [128C] Connecting to ADB server...
2012-10-10 16:12:14 [128C] Connected
2012-10-10 16:12:14 [128C] ADB Write: host:devices
2012-10-10 16:12:14 [128C] ADB Read: 0123456789ABCDEF device

Your help is greatly appreciated.

Hi,
is your device based on ICS (4.0+)? It does not seem to be. Previous versions do not support the backup command

[shaamt]

Hi,
is your device based on ICS (4.0+)? It does not seem to be. Previous versions do not support the backup command

I am using ICS 4.0.9 and not prior to ICS.

[jakubklos]

Hi,
is your device based on ICS (4.0+)? It does not seem to be. Previous versions do not support the backup command

I am using ICS 4.0.9 and not prior to ICS.

Weird, in that case you should try the adb command line tool itself if it works.
adb backup

If that works I have some work to do. If not it is ROM related.
Also, you may try to specify some package instead of all and toggle the options but the adb backup tool will tell us more

Let me know

[shaamt]

Weird, in that case you should try the adb command line tool itself if it works.
adb backup

If that works I have some work to do. If not it is ROM related.
Also, you may try to specify some package instead of all and toggle the options but the adb backup tool will tell us more

Let me know

adb backup -all
Result: unable to connect for backup

Thanks for your time.

[jakubklos]

Weird, in that case you should try the adb command line tool itself if it works.
adb backup

If that works I have some work to do. If not it is ROM related.
Also, you may try to specify some package instead of all and toggle the options but the adb backup tool will tell us more

Let me know

adb backup -all
Result: unable to connect for backup

Thanks for your time.

Yep, since your device ID is sort familiar it is a custom ROM (maybe CM - who knows). I guess you might try a different ROM or simply ask the team to fix this. Good luck