[TouchPad Q&A, Help & Troubleshooting] EricBlade:
I woke up this morning to it's alarm, shut the alarm off, and the device immediately went out to lunch, popped up a "Launcher is not responding, Wait/Close" box, and froze. When it rebooted, it Bluetooth connected to my PC all the way across the house, and that worked. It took it several minutes to connect to Wifi, though.

Now, time to try to figure out how to install the newest one :) Weeee!!!!

Hoping this will work out easily, so I can switch up my daughter to Android now.. but I need to find some good parental control software too.

Flintman's recovery is definitely different than the old one I had. It's ADB Sideload doesn't work -- I used sideload to load Flintman's recovery from my old recovery, since he said it's absolutely required now. Once I found the Sideload option in his recovery, I started it up, but adb sideload responds only with "error: closed".

* update: fixed "error: closed" by doing "adb usb" which says "restarting in USB mode" .. this is a new thing to me, I guess that means it's now using USB to find the device directly, rather than having it connect via a TCP socket, as cwm did? alright. it's loading.. but it's extremely slow compared to loading on my old recovery. Not a big deal, though. A somewhat bigger deal, is that the recovery goes to black screen when the sideload gets to about 40%, and touching anything to attempt to see what it's status is cancels the sideload .. so I don't seem to have any way of knowing for sure when it's complete. ... and once it gets up to about 60%, the sideload crashes with "failed to read command" ...

* ... and after failing that sideload, the android system is completely hosed and will not start. It flashes some blue lines, then the Evervolv logo, blue lines, black screen, and halts.

I can reload the December 23rd release, and the system works. Flintman's TWRP refuses to install anything newer, erroring that it couldn't run the updater binary. I reloaded CWM and it loaded the January 9 image, and the tablet is running again.

* further edit -- somewhere along the line, the volume table got all sorts of jacked or something. I tried to reset up everything with Tailor, it kept complaining that fsck was failing on the android filesystems.. so i deleted all the Android filesystems, then loaded TPToolbox, and did a complete reset, and created the partitions from scratch. Installed my formerly working 4.4.4 with TPToolbox, then loaded the 1-15 build with the CWM recovery, and it is just now booting up, and going through it's "Android is upgrading..." stuff.

... ok, hour or so spent letting it restore, seems to be running quite nicely. going to test out my apps and bluetooth and stuff next. It's noticeably faster, although possibly somewhat jerkier, than the previous releases. logcat is spamming a lot of stuff about "Data not connected!! Set no data type icon / Roaming", but other than that, it's surprisingly quiet. Here's an odd one:

"Setting airplane_mode_on has moved from android.provider.Settings.System to android.provider.Settings.Global, returning read-only value" ... and now the launcher is completely locked up. no clue what happened. all i did was turn the display on. :-S

... after it rebooted, it's working great, except Bluetooth, which won't connect to anything at all. My PC can see it, it can see the PC, it can see all 3 of my BT keyboards, it won't connect to any of them. The Bluetooth is also not recognizing my Mac Mini, or my Dell laptops, or my other Android devices. The Mac and Laptop can see the TouchPad. The other Android devices cant even find it.