NAND Testing - 05-25 Update: New LK, Recovery.img, Kernel Updates through Recovery

[tiger2wander]

yeah, I have only one partition on my sdcard. If I have multiple partitions so I'll put it to the first one because of I see the hard coded in the init script that check and use only /dev/mmcblk0 and /dev/mmcblk0p1

But I still failed to boot up Android NAND version back to WM and HARET way now.

[[ACL]]

Modified the init script to the one i mentioned above.. seems to work fine for me so for those of you who had issues, give this a try and lets see if it works.

I also included emwe's patch from haret which got the old fb to do a higher framerate. Unfortunately it did nothing for us which still proves my theory that we are limited to 30fps right now until we find a way to deal with the possible vsync issue.

[pts69666]

Originally Posted by [ACL]

Modified the init script to the one i mentioned above.. seems to work fine for me so for those of you who had issues, give this a try and lets see if it works.

I get off in a half hour, if I don't pass out when I get home, I'll give it a try and let you know.

----EDIT-----

This time it did boot up. However on initial boot, when the device got to the home screen, it locked up and didn't want to do anything. I did reboot and other than a few issues getting the screen to stay on, everything seems to be working great. The boot animation is a little glitchy.

Quick question. Is it possible to recalibrate my screen after initial boot? When I try and do the screen calibration during initial boot, the scrolling text covers the boxes and I don't get an accurate calibration.

Many Thanks for all your hard work!

[[ACL]]

Originally Posted by pts69666

I get off in a half hour, if I don't pass out wgen I get home, I'll give it a try and let you know.

----EDIT-----

This time it did boot up. However on initial boot, wgen the device got to the home screen, it locked up and didn't want to do anything. I did reboot and other than a few issues getting the screen to stay on, everything seems to be working great. The boot animation is a little glitchy.

Quick question. Is it possible to recalibrate my screen after initial boot? Wgen I try and do the screen calibration during initial boot, the scrolling text covers the boxes and I don't get an accurate calibration.

Many Thanks for all your hard work!

Make sure you use the latest gralloc and lib. .35 fb is not forgiving and will show it when the libs dont match right.

[coolsilver]

Latest from the 3d thread?

[Lmiller1708]

Is anyone having any issues with not being able to get Root access?
If not it might just be my Rootfs or something else...
But I thought I would check first.

Edit: I had the wrong Rootfs...

[coolsilver]

I haven't had any trouble with titanium backup getting root

[[ACL]]

Originally Posted by coolsilver

Latest from the 3d thread?

yes.. soon it will be part o xdandroid since topaz main dev reported success with the .35 fb..

we are working on breaking the 30fps limit now.. bottom line is that if our 2d isnt smooth as a babys ass, then i dont want it on my phone..

[Lmiller1708]

ACL,

If you place "echo 50 >/sys/class/leds/lcd-backlight/brightness"
right before the mounting of the SD card in the initramfs then one can see what is going on and it is not needed in the Rootfs then.

[mpannen]

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},
};