[Glass General] DA6030:
So, I just got my Recon Jet (the self-declared "most powerful wearable computer" running Android 4.1, without Google services), and started doing some basic poking around. What would people like to know?

So far my basic impression is that I feel like I'm using a flagship smartphone running feature-phone software. All the specs are awesome, but the device does almost nothing out of the box, and there are no apps yet. The entire time I'm wearing it, it's like the device is screaming SOMEONE PLEASE MAKE A CUSTOM ROM WITH GOOGLE GLASSWARE SUPPORT.

Anywho, on to the nerdy stuff.

I didn't have the guts to try a fastboot oem unlock, so I didn't get very far in fastboot:

>fastboot -i 0x2523 getvar all
(bootloader) product: Jet_Fastboot
(bootloader) cpu: OMAP4430
(bootloader) cpurev: ES2.3
(bootloader) secure: GP
(bootloader) serialno: **redacted**
(bootloader) userdata_size: 6501231 KB
(bootloader) Flash Slot: EMMC(1)
all:
finished. total time: 0.031s

>fastboot -i 0x2523 oem ?
...
FAILED (remote failure)
finished. total time: 0.016s

>fastboot -i 0x2523 reboot
rebooting...
finished. total time: 0.000s

In ADB, without root, also didn't find too much interesting, but then again wasn't looking for anything in particular.

shell@android:/ $ df
df
Filesystem Size Used Free Blksize
/dev 306M 32K 306M 4096
/mnt/asec 306M 0K 306M 4096
/mnt/obb 306M 0K 306M 4096
/system 503M 237M 266M 4096
/data 6G 255M 5G 4096
/cache 251M 24M 227M 4096
/factory 314M 179M 135M 4096
/storage/sdcard0 6G 255M 5G 4096

shell@android:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name

179 0 7634944 mmcblk0
179 1 128 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 128 mmcblk0p3
179 4 384 mmcblk0p4
179 5 327680 mmcblk0p5
179 6 16 mmcblk0p6
179 7 8192 mmcblk0p7
259 0 8192 mmcblk0p8
259 1 524288 mmcblk0p9
259 2 262144 mmcblk0p10
259 3 6501232 mmcblk0p11

shell@android:/ $ ls -al /dev/block/platform/omap/omap_hsmmc.1/by-name
block/platform/omap/omap_hsmmc.1/by-name <
lrwxrwxrwx root root 2015-04-18 21:04 boot -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-04-18 21:04 bootloader -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-04-18 21:04 cache -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-04-18 21:04 crypto -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-04-18 21:04 efs -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-04-18 21:04 misc -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-04-18 21:04 recovery -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-04-18 21:04 system -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-04-18 21:04 ubootenv -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-04-18 21:04 userdata -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-04-18 21:04 xloader -> /dev/block/mmcblk0p1

shell@android:/ $ ls
ls
acct
cache
charger
config
d
data
default.prop
dev
etc
factory
init
init.goldfish.rc
init.omap4jetboard.rc
init.omap4jetboard.usb.rc
init.rc
init.trace.rc
init.usb.rc
mnt
proc
res
root
sbin
sdcard
storage
sys
system
ueventd.goldfish.rc
ueventd.omap4jetboard.rc
ueventd.rc
vendor

Note that Recon devices do not use a VendorID recognized by standard adb and fastboot, so you will have to take extra steps to use these tools.

Specifically, to use ADB, you will need to modify (or create) an adb_usb.ini file containing 0x2523, and fastboot will have to use the -i option.

Users on the sparsely-used Recon forums (addressing almost exclusively Recon's previous generation of products) report being able to sideload APKs, but I can't think of any apps I would like on my face that don't rely on Google Play Services. Any suggestions?

Mods, please feel free to move this to the appropriate forum for Recon Jet, as soon as one exists. Until then, this seemed to me like the best place.