[Samsung Gear 2] biktor_gj:
Okay, after 5 more days, I've been able to make the command line switching work with the 3.10 kernel (damn buffer overflows...)

Situation is as follows:

Kernel 3.10:

Video working

Normal boot / Recovery switching working

Audio Working

Bluetooth *should be* working (according to the kernel)

Power key working

Vibrator *should be* working

USB: Google has removed the Android USB driver, and now we should be using FunctionFS Gadget driver. FunctionFS is itself working, it's detected, it bringed up, and it persist on disconnects and reconnects. BUT, I can't manage to get ADB working over FunctionFS, as described in this post:

https://plus.google.com/111524780435806926688/posts/AaEccFjKNHE

EDIT : never mind the USB, install driver manually and now it will work.

Since they have also removed the RAM console, it's a bit hard for me to get a log. I managed to get a dmesg by removing the recovery and overwriting it with a script:

:: /sbin/recovery

#!/sbin/sh
mount /dev/block/mmcblk0p14 /system
cat /proc/version >> /system/findlog.txt
echo START >> /system/findlog.txt
find / >> /system/findlog.txt
echo DMESG >> /system/findlog.txt
dmesg >> /system/dmesg.txt
echo END >> /system/findlog.txt
umount /system"

I also have started making a device tree for the watch in cyanogenmod 11 source. I can't get it to show the recovery from there though (black screen), but since it's the first time I do this I've probably messed it up. Maybe it was writing to somewhere else instead of the framebuffer, since there's no adb, I can't debug it either...

Can you give me a little help?

I've uploaded 4 new files to mediafire: https://www.mediafire.com/folder/fldad5h2pbh12//Recovery tests

bootlog_310 > Boot log from working kernel

recoverytest.tar > Test recovery image with TWRP (the one from the screenshot). I picked this up from some other device and it boots and brings up ADB in 3.4 kernel and shows twrp on 3.10

kernel_310.tar > 3.10 kernel, should show up twrp when you enter recovery (and while it's at it it will show a beautiful android wear logo ;) I was bored)

kernel_34.tar > 3.4 kernel, you should get adb working with it but not much more

You'll have to reboot to bootloader and from there choose 'recovery' to get into the recovery partition!

First thing I need to get working again is ADB on 3.10 kernel, just to be able to debug the rest... but if you manage to get TWRP show fine I'd send you a million thank you too ;)

EDIT:

SORRY! I overlooked it!

ADB is indeed working, I just need to install the driver manually to make it work (when windows detects it as functionfs, select Android ADB driver).

The recovery image contains Cyanogenmod's recovery, which doesn't show in screen, but seems to be running...

EDIT Again:

I looked a little bit more, and there's a difference on how twrp runs and cm's recovery does it, regarding the display.

When recovery starts, it drops this in the kernel log:

panel is not in fb unblank state

This message comes from the LCD panel driver, but I have no idea on why it's saying this... any clues?

And edit again

rinato.tar in the same mediafire folder: CM11 device tree skeleton. Just that with the kernel and the recovery.fstab, but better than having to make all the files by hand ;)