Saturday, July 18, 2015

Finally Made Fly Snap Mobile to connect to ADB shell using USB cable

As part of my IoT/Home-Automation/Home-Monitoring exercises, I was exploring various low cost Android phones that do following:

  • GPS monitoring -- Tracking the Cars/kids/etc
  • Video Camera(s) -- for Video monitoring
  • BLE -- For any IoT
  • Have Android 4.4.2 and above
  • Have minimum 2 ARM cores and 512 MB Ram
I found/bought following Android phones are reasonable VFM for these purposes:
  • BQ S38  ( 50$ ) : 2-core-Cortex-A7, 512MB Ram, 4" IPS, GPS, No BLE , Android 4.4.2
  • Fly Snap ( 50$) : 4-core-SC7731, 512MB Ram, 4", GPS, No BLE , Android 4.4.2
Though I was able to connect BQ S38 via ADB from my Fedora-15, I am not able to connect the Fly-Snap to ADB-server. It seems there are some drivers for Windows at these links:
I could not use them, as I am not using windows and using Fedora-15 :(

I added following lines to /etc/udev/rules.d/52-android.rules:
SUBSYSTEM=="usb", SYSFS{idVendor}=="1782", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="1782" ATTR{idVendor}=="4012"  MODE="0666", OWNER="yyyy"

1782 and 4012 are takes from command 'dmesg'. Then as root, I issued 'udevadm control --reload-rules'.

But I was not able to connect Fly-Snap. So as another step, I added following line to ~/.android/adb_usb.ini

But Then I killed adb-server using 'adb kill-server' and 'adb start-server'. Now I am able to my Fly-Snap device.

No comments:

Post a Comment