Tag: Android

So, I had noticed that only one of the three tablets had updated to a different build number… after fighting with them for a while, I figured out how to get them all up to what the updater service is claiming to be the latest release.

First, I had to force the update that was currently on the two lesser versions (1.0.1). To do this, I had to download the update, by telling the server that I had the previous version:

[on PC, visit]

After getting the update–1.0.1.zip–renamed it as update.zip, and pushed it to /sdcard via adb; rebooted tablet, RKUpdateService recognized an update file was there and asked to do the work. Tablet “upgraded” to build 1.0.1; after reboot, tablet asks to clear the old file–yes!–then hits the update server to see that 1.0.2 is available.

…I would have sworn that I had seen somewhere that there were newer builds, but I think the forum thread I read that on has gotten confused and is talking about more than one model of RCA tablet…

…anyway, the update server doesn’t respond well to changing that address above to any other version number, and the update app states that 1.0.2 is the latest. Logcat readout has RKUpdateService saying “no find remote update package…”

…so, I dunno. Maybe 1.0.2 is the latest–but I’m not sure… I noticed when I told the server a different model number I got it’s builds out of order… When I told it I was running 1.0.0 on the RCT6378W2, it gave me 1.0.2; when I told it I was running 1.0.1 it gave me 1.0.3–telling it 1.0.2 or any higher variation didn’t yield anything.

…just some geeky info… call this post a work-in-progress (that I may or may not re-visit)

USB drivers for ADB, etc… Just grab the latest generic Google USB drivers – http://developer.android.com/sdk/win-usb.html#download

after driver has installed, create/edit the ‘%USERPROFILE%\.android\adb_usb.ini’ file… (the value we’re adding is the Vendor ID — 0x2207)


# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x2207

…and, bingo! adb access!

If side-loading apps, go into settings->Apps, and start moving things over to “NAND FLASH”… apps seem to like going into the “Internal Storage” [/data] area which is apparently supposed to be reserved for the system/pre-loaded apps–space here is quite limited. “NAND FLASH” area [/sdcard], however, is roughly 5GB of open space.