[Nexus 4 Q&A, Help & Troubleshooting] sarah_pdx:
Howdy,

Anyone out there with Cyanogen KitKat (CM11-M12) with USB OTG working on a nexus4?

I'm having trouble on my N4. I have a self-powered hub and an OTG cable, so I think I'm good hardware-wise. I'm having trouble with the kernel/software.

Here's where I started:

Device: Nexus 4

ROM name: Cyanogen

ROM version: 11-20141115-SNAPSHOT-M12-mako

Build number: cm_mako-userdebug 4.4.4 KTU84Q 7b9aa21a34 test-keys

Kernel version: 3.4.0-cyanogenmod-gd0183c8 ...

- Encrypted phone (if that matters)

Recovery: TWRP

What I've tried:

I first flashed (no cache or dalvik wipe) the non-CM franco r213 kernel. After seeing lots of odd colors and graphics I learned it wasn't built for CM. I reflashed the CM11-M12 zip and things were back to normal (but of course no OTG).

Next I flashed (no cache or dalvik wipe) the Hells Core b64 (hC-b64-CM) kernel. Ran fine, but no "USB Storage" section under "Settings->Storage". Maybe the more recent HellsCore kernels don't have OTG support? Seems like I saw an earlier version with "otg" in the name.

After watching a russian dude on youtube (https://www.youtube.com/watch?v=92WI3HdSUgo), it looked like he first flashed an older hells-core kernel with OTG support, then flashed a newer non-OTG kernel. Even after flashing the newer kernel OTG stayed working. So... I flashed (no cache or dalvik wipe) hells-Core_b47_4.4.4-cm11-OTG-justvarshney.zip. I booted it up and when I opened "Settings-Storage" I got an "Unfortunately, Settings has stopped" error. I flashed a newer hells core b64 kernel and the "Settings has stopped" behavior persisted (not surprising). I reflashed the cm11-M12 zip and got back to normal.

I tried flashing the older "fk r199-CM" franco kernel from ziddey's thread since it's for cyanogen. Booted up but got the same "Settings has stopped" error when opening "Settings->Storage". Reflashed cm11-M12 zip and got back to normal.

Poking around ziddey's devhost account I saw an "fk r200-CM" franco kernel. Tried that too. This time with cache/dalvik wipes. Same results as r199.

Tried a faux123 kernel (mako-kk-kernel-042m.zip) with cache/dalvik wipes. Weird colors (like non-CM fanco r213). Settings-Storage works, but doesn't show the USB section. Ran USB Host Diagnostics - unique code 503524. Attempted fix, rebooted, reran - unique code 503530. Reflashed cm11-m12 zip.

Tried SaberMod franco kernel r213.2 (http://xdaforums.com/nexus-4/development/kernel-sabermod-franco-kernel-r211-t2858561). No USB Section in Settings->Storage. USB Host Diagnostics 503555.

Tried flashing older CM11-M11 ROMs and then flashing zaclimon's SaberMod franco r213.2. Poked around with terminal app and didn't see a lot of the changes mentioned in ziddey's thread (init.mako.usbdisk.rc, handheld_core_hardware.xml, framework-res.apk, platform.xml, ...).

Questions:

Am I trashing my phone? I'm not super-experienced with flashing custom kernels. After the first few I've been wiping cache&dalvik each time. When I break things, everything seems okay after reflashing the CM11-M12 zip, but who knows...

Do I have to manually create/edit the files mentioned in ziddey's thread (init.mako.usbdisk.rc, handheld_core_hardware.xml, framework-res.apk, platform.xml, ...)? Should all that get done automatically in kernels with OTG support?

Is my CM11-M12 too new to work with the existing OTG kernels out there? I'd like to stay on M12 for the POODLE attack fix. Anyone else out there with CM11-M12 with OTG working on a nexus4?

Thanks for any tips/suggestions/comments or jokes!

Sarah