View Single Post
Posts: 2,225 | Thanked: 3,822 times | Joined on Jun 2010 @ Florida
#88
Originally Posted by Estel View Post
What the hell is /dev/tw14030-adc ?!
Off the top of my head, I think it's something to do with the battery, obviously, but I don't remember what. One of the watchdogs is at /dev/tw14030_wdt (as you can see in bootmenu, and in my /sbin/preinit boot-shell mod), but that's all I can say. Also, I THINK pali mentions tw14030 in the post where he posted his original getbootstate open-source backport+clone. Speaking of, I'm about to test pali's open source getbootstate. Wish me luck and such.

Coming back to this tho:
Originally Posted by Estel
1. Be sure that "USER" is our plain, everyday normal bootstate, cause You're obviously now getting "USER" bootstate.

....

Can anyone with access to desktop PC and device *not* affected by problem (Mentalist, I'm looking at You, cause others following this thread probably won't dare ) flash framebuffer kernel and check which bootstate is used during normal boot?
With R&D mode off and framebuffer running on power kernel 47, I can verify it looks like the correct/normal state is "USER". (Actually I think it's the correct state with R&D mode on too.)
 

The Following 2 Users Say Thank You to Mentalist Traceur For This Useful Post: