modhatter6811
Android Enthusiast
hey modhatter,
the recovery patch file is just a leftover remnant, it doesnt actually do anything. its removed in the updated zip files im working with, just ignore it. the only thing that wont let you get back to recovery through adb is the fact that the phone freezes up from services dying and dex2oat stalling, so you have to be quick with what you try to do.
on another related note:
from what i gather, the big problem around the display is the fact that I am using phenom's cm11 kernel(which is amazing by the way ), which probably uses caf display drivers? (i have no clue, just what i read on the interwebz.) people are saying that we would need to revert to aosp style display drivers in kernel to get output on the screen, if anyone can shed some more light on that and is good with kernel work please lemme know.
I'm not too familiar with kernels either, but I'm learning as fast as possible. The kitchen just isn't enough for this kind of work. (Sounds like its high time that I install Ubuntu) I'll see what kind of info I can pull about drivers and how surfaceflinger operates, and report back any useful info that I can muster up.
Edit: I think this is worth a quick glance. Its that thing rbheromax was referring to, about ADB complaining about libs, and at the end, it even gives a string. This was in eclipse I'm guessing. Running parts of android L [url/http://stackoverflow.com/questions/21845358/android-emulator-cant-be-started/]java - Android emulator can't be started - Stack Overflow[/url]