Re: NAND Boot Testing - 12-11: Panel power off and on now working!
 

update: loads to lockscreen, so far can't get screen to stay on??? strange

update2: got it working, but keeps turning screen off immediately... any ideas>?

Re: NAND Boot Testing - 12-11: Panel power off and on now working!
 

What I did was keep hitting the end button, slowly... then go to settings, display and check auto backlight control. It works fine for me know. :)

Re: NAND Boot Testing - 12-11: Panel power off and on now working!
 

Hey, I have another question. Sorry for being such a pest. I went and looked at the 3D thread to see what was going on there, and I saw quite a few files there. More then just the one .so file I was using. Which of those files are needed for us and where do we put them? This is just my curiosity getting the best of me. I still have the flickering screen on my boot animation and such.

Re: NAND Boot Testing - 12-11: Panel power off and on now working!
 

hmm, i have been trying this and i feel like i have everything right

tilt2.kb, rootfs.img, modules, and system.ext in an andboot folder in my storage card and then, the nbh in a folder with customRUU.exe. I flash and then it gets to the linux boot screen, after a couple lines go by, the screen fades out and dies and restarts. My battery says 100 percent when i flash back to windows

I have tried multiple module/nbh files and i have formatted my sdcard to fat32, no matter what i'm getting the same problem

anybody know what could be going wrong?

Re: NAND Boot Testing - 12-11: Panel power off and on now working!
 

I tried it out, i replaced the inits in the board-htcrhodium-panel.c with the new ones, but I am still having the same issues with the panel firing up. :(


What do these two entries do?

{0x6a17, 0x01},
{0x6a18, 0xff},

Here is exactly what I have for init:

nov_init_seq[] = {

/* EID es3 */
{0x5100, 0x00},
{0x1100, 0x01},
{REG_WAIT, 0x64},
{0x4e00, 0x00},
{0x180, 0x02},
{0x880, 0x00},
{0x2080, 0x33},
{0x2680, 0x78},
{0x2880, 0x3e},
{0x2980, 0x04},
{0x2c80, 0x22},
{0x2e80, 0x00},
{0xde80, 0x02},
{0x3a00, 0x55},
{0x3500, 0x00},
{0x4400, 0x00},
{0x4401, 0x00},
{0x5e00, 0x00},
{0x6a01, 0x00},
{0x6a02, 0x01},
{0x5301, 0x10},
{0x5500, 0x02},
{0x6a17, 0x01},
{0x6a18, 0xff},
{0x2900, 0x01},
{0x5300, 0x2c},
{0x5303, 0x01},
};

Re: NAND Boot Testing - 12-11: Panel power off and on now working!
 

I see there was an update to the repository, I will try this again with that update.

Re: NAND Boot Testing - 12-11: Panel power off and on now working!
 

Hmm not working for me, it seems that the screen hardly ever comes on, but the touch part of the screen still works. It fired up a few times but after that I couldn't even get a flicker.

I agree it is more consistent with autobacklight setting on.

I think my backlight may soon burn out because it still from time to time have a red washed out look like a fluorescent bulb not getting enough power to turn the gas to plasma.

Wirelessly posted (Opera/9.80 (Windows Mobile; Opera Mini/5.1.21594/22.401; U; en) Presto/2.5.25 Version/10.54)

I will be working on a new rootfs in about an hour. I'll put the backlight on command at the start of init so the screen stays on during boot.

Re: NAND Boot Testing - 12-11: Panel power off and on now working!
 

hey nate did you ever make the custom rootfs like f22 rootfs where the end key bring up recent apps and the helicoper veiw