This post has been thanked 1 times. |
|
||||
Can anyone tell me how to permanently lock this phone? I am really tired of the screen waking up and end up calling my boss or any other random person that may have called me last. I just want all the buttons off except one at the top.
Sent from my HTC Touch Pro 2 on Android with Tapatalk Pro. |
|
||||
Re: NAND Boot Testing - 11-29: New Framebuffer, gralloc, and libGLES
I guess I haven't tested the NAND builds in a while, do they not wake up to the lock screen? Mine always wakes to that lock screen, so no chance of calling people...
|
|
||||
Re: NAND Boot Testing - 11-29: New Framebuffer, gralloc, and libGLES
They do but sometimes it shows the home screen for a couple seconds before the lock screen. Also the Windows (menu) button seems to bypass the lock screen completely and being beside the Send key it ends up calling whoever is first in the call log.
|
|
||||
Re: NAND Boot Testing - 11-29: New Framebuffer, gralloc, and libGLES
Great, thank you sooo much, natemcnutty!
I'm trying and will report back if it work. This is what I have searched for a looong time ago but not luck till seen your link
__________________
No money, no honey!
--- Motoroi XT720 - MIUI 1.10.21-t2w - [OC 1Ghz very fast & smooth] - CM-7.1.0-11.10.12-ODEX-XT720-J.Y.Daddy |
|
||||
Re: NAND Boot Testing - 11-29: New Framebuffer, gralloc, and libGLES
finally fixed the panel power issue.. its a little buggy since its just goes off randmly right now .. but i'll work it out. I havent committed it yet but will soon..
nate: bzo was able go the the panel init dump from haret. This is his trace pastebin - rhod400 mddi init trace - post number 2015886 This is what i added to the panel code for now for the init to work #define REG_WAIT (0xffff) struct nov_regs { unsigned reg; unsigned val; } nov_init_seq[] = { {0x5100, 0x00}, {0x1100, 0x01}, {REG_WAIT, 0x64}, {0x4e00, 0x00}, {0x3a00, 0x05}, {REG_WAIT, 0x1}, {0x3500, 0x02}, {0x4400, 0x00}, {0x4401, 0x00}, {0x5e00, 0x00}, {0x6a01, 0x00}, {0x6a02, 0x01}, {0x5301, 0x10}, {0x5500, 0x02}, {0x6a17, 0x01}, {0x6a18, 0xff}, {0x2900, 0x01}, {0x5300, 0x2c}, {0x5303, 0x01}, }; struct nov_regs nov_deinit_seq[] = { {0x2800, 0x01}, {0x5300, 0x28}, {0x5500, 0x00}, {0x5300, 0x08}, {0x5e03, 0x08}, {0x5300, 0x00}, {0x1000, 0x01}, }; static int htcrhod_mddi_client_init( struct msm_mddi_bridge_platform_data *bridge_data, struct msm_mddi_client_data *client_data) { int i; unsigned reg, val; client_data->auto_hibernate(client_data, 0); for (i = 0; i < ARRAY_SIZE(nov_init_seq); i++) { reg = cpu_to_le32(nov_init_seq[i].reg); val = cpu_to_le32(nov_init_seq[i].val); if (reg == REG_WAIT) msleep(val); else client_data->remote_write(client_data, val, reg); } client_data->auto_hibernate(client_data, 1); return 0; } static int htcrhod_mddi_client_uninit( struct msm_mddi_bridge_platform_data *bridge_data, struct msm_mddi_client_data *client_data) { int i; unsigned reg, val; for (i = 0; i < ARRAY_SIZE(nov_init_seq); i++) { reg = cpu_to_le32(nov_deinit_seq[i].reg); val = cpu_to_le32(nov_deinit_seq[i].val); client_data->remote_write(client_data, val, reg); } return 0; } Edit : i committed the code and autobuild already has something for you guys to test. with the panel out of the way and frame-buffer all set. I can finally attack the head-set crap and then work with bzo on camera.. almost there. Last edited by [ACL]; 12-11-2010 at 05:37 AM. |
This post has been thanked 4 times. |
|
||||
Wirelessly posted (Opera/9.80 (Windows Mobile; Opera Mini/5.1.21594/22.401; U; en) Presto/2.5.25 Version/10.54)
Quote:
|
This post has been thanked 2 times. |
|
||||
Wirelessly posted (Vogue: Mozilla/5.0 (Linux; U; Android 2.2.1; en-us; MSM Build/FRX03) AppleWebKit/533.1 (KHTML, like Gecko) Version/4.0 Mobile Safari/533.1)
Great news ACL! Good job! Question... might be a dump one but when do the drivers get added in (like the MTD drivers). Are they in the zimage or are the in the modules folder. Thanks!
__________________
|
|
||||
Re: NAND Boot Testing - 11-29: New Framebuffer, gralloc, and libGLES
Downloading the autobuild now... *bounces around room excited*
Have a thousand thanks. EDIT: Screen does power down as expected. Again doesn't power on once loaded. :/ At first my screen was a shade of red.... it was creepy. Left it sit. Turning on correctly, bad ghost of top notification bar along bottom edge of launcher pro bar. Turned on and off and all ok again. I'm not sure my libGLES is working because the boot animation flashes and tears as before. Graloc seems to be ok according to logcat. Nope back to not turning on... yet the screen reacts even though it is off..... ooookay.... lol Last edited by coolsilver; 12-11-2010 at 12:13 PM. |
This post has been thanked 1 times. |
|
||||
Re: NAND Boot Testing - 11-29: New Framebuffer, gralloc, and libGLES
Quote:
Hmm.. so there may be different panel types for the rhod. We will need to dump from haret to see what panels are around. Hard part will be figuring out who has what pannel :-\ screen should not tear at all.. make sure you use the latest lib and gralloc (29/30). Last edited by [ACL]; 12-11-2010 at 02:11 PM. |
This post has been thanked 1 times. |
|
|
|