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

**arrrghhh** · #**1951** (**permalink**) 03-21-2011, 02:27 PM

Quote:

Originally Posted by pts69666

I am having only a few issues with this build myself. (sorry if issues have been reported in past, haven't been keeping up with thread since I've had to actually do work at work, now im on day shift =P )

First off, is this build still effected by the time sync issues?

Second, it seems my keymaps are a little off. The arrow keys are a bit off and I can't use fn+keys for punctuation.

Other than that, its just things you guys already know about, such as waking from standby. =P

BTW, I have a RHOD400.

Might be best to at least search before posting, as the FN keys (and keymaps in general) are not yet working but are being hashed out.

Also, I would assume it's still effected by the time drift - although I haven't specifically tested for it, I don't see why it would just disappear

. Clocksync is still the best remedy for that, until we figure out the root cause (which we may never, seems we don't have a hardware clock to speak of...)

**natemcnutty** · #**1952** (**permalink**) 03-21-2011, 02:34 PM

Quote:

Originally Posted by arrrghhh

Might be best to at least search before posting, as the FN keys (and keymaps in general) are not yet working but are being hashed out.

Also, I would assume it's still effected by the time drift - although I haven't specifically tested for it, I don't see why it would just disappear

. Clocksync is still the best remedy for that, until we figure out the root cause (which we may never, seems we don't have a hardware clock to speak of...)

Yeah, time is still an issue, but key maps should not be. We have had that working for a while. The only thing I can think of is maybe the installer in recovery is not doing the detection. I'm looking into it right now.

**Lmiller1708** · #**1953** (**permalink**) 03-21-2011, 02:49 PM

Quote:

Originally Posted by natemcnutty

Yeah, time is still an issue, but key maps should not be. We have had that working for a while. The only thing I can think of is maybe the installer in recovery is not doing the detection. I'm looking into it right now.

I'm starting to think the install-seq is bombing out for some reason... Not too sure. Could be why WIFI isn't working too... Or was that fixed?

**arrrghhh** · #**1954** (**permalink**) 03-21-2011, 02:51 PM

Quote:

Originally Posted by Lmiller1708

I'm starting to think the install-seq is bombing out for some reason... Not too sure. Could be why WIFI isn't working too... Or was that fixed?

Quote:

Originally Posted by natemcnutty

Yeah, time is still an issue, but key maps should not be. We have had that working for a while. The only thing I can think of is maybe the installer in recovery is not doing the detection. I'm looking into it right now.

Hrm, I need to give the newest another run methinks.

I tried the newest as of last night, and wifi was broken and IIRC so was the keymaps... I'll try it again when I get home (hopefully).

**[ACL]** · #**1955** (**permalink**) 03-21-2011, 03:09 PM

Quote:

Originally Posted by Lmiller1708

I'm starting to think the install-seq is bombing out for some reason... Not too sure. Could be why WIFI isn't working too... Or was that fixed?

wifi was fixed. It was because the sysinit.sh was bombging out.

**natemcnutty** · #**1956** (**permalink**) 03-21-2011, 03:38 PM

Quote:

Originally Posted by [ACL]

wifi was fixed. It was because the sysinit.sh was bombging out.

Well, I have some good news and some bad news. Starting with the good news:

I've been testing new placements for mtdparts, and I think I have regained a ton of space for us

Can someone please try these for the mtdparts?

Code:

mtdparts=msm_nand:0x4800000@0x0(protected),0x800000@0x4800000(recovery),0x0A000000@0x5000000(system),0xF000000@0xF000000(userdata),0x2000000@0x1E000000(cache)

The bad news:

I just tested grabbing the latest files from autobuild, and I'm having all sorts of issues. Edit: I forgot /sdcard causes issues, so that problem is my own fault. One thing I noticed is since recovery is first in the init, I can't install using install-seq.sh unless recoveryinstall.tgz is not on the sd card which then means I can't install it through the install-seq.sh.

So at this point, I think we might want to swap the order of install-seq.sh script and recovery, and then maybe someone else with a rhod500 can test recovery and let me know if it is working for them.

**[ACL]** · #**1957** (**permalink**) 03-21-2011, 04:26 PM

Quote:

Originally Posted by natemcnutty

Well, I have some good news and some bad news. Starting with the good news:

I've been testing new placements for mtdparts, and I think I have regained a ton of space for us

Can someone please try these for the mtdparts?

Code:

mtdparts=msm_nand:0x4800000@0x0(protected),0x800000@0x4800000(recovery),0x0A000000@0x5000000(system),0xF000000@0xF000000(userdata),0x2000000@0x1E000000(cache)

The bad news:

I just tested grabbing the latest files from autobuild, and I'm having all sorts of issues. Edit: I forgot /sdcard causes issues, so that problem is my own fault. One thing I noticed is since recovery is first in the init, I can't install using install-seq.sh unless recoveryinstall.tgz is not on the sd card which then means I can't install it through the install-seq.sh.

So at this point, I think we might want to swap the order of install-seq.sh script and recovery, and then maybe someone else with a rhod500 can test recovery and let me know if it is working for them.

yeah, but i thought we agreed to kill the script anyways? i was about to just removed it from the server :-p ..

what issue are you having with the recovery ?

**natemcnutty** · #**1958** (**permalink**) 03-21-2011, 04:27 PM

Quote:

Originally Posted by [ACL]

yeah, but i thought we agreed to kill the script anyways? i was about to just removed it from the server :-p ..

what issue are you having with the recovery ?

Can't get into it, but you were saying that's because we changed /sdcard to /mnt/sdcard and /sdcard is made during init. I'm looking at editing that right now to see if I can get into recovery again.

**Lmiller1708** · #**1959** (**permalink**) 03-21-2011, 04:35 PM

Quote:

Originally Posted by [ACL]

yeah, but i thought we agreed to kill the script anyways? i was about to just removed it from the server :-p ..

what issue are you having with the recovery ?

Kill the script. No real need for it.

Nate,
Not sure what your problems are... But when I was trying to make the MTDParts like you are now you have to format the partitions in the correct order. MTD1 - MTDn...

I'm guessing that you have all sorts of rw errors once you tired to go back to the original... This can be corrected by changing the order of erasing like i just posted above.

Our initial install script should be put together this way also.

EDIT: ALSO Nate if you want to test these MTDparts out we might need to look at how the NBH is being created again.
Might have to go back to what the Vogue is using...
Just a hunch I have

, but I have not had enough time to look at it.

This was my latest MTDParts:

Code:

mtdparts=msm_nand:0x3000000@0x0(boot),0x800000@0x3000000(recovery),0x8C00000@0x3800000(system),0x10800000@0xC400000(userdata),0x2000000@0x1CC00000(cache)

They work... but WIFI does not! ACL said it's because we could be writing over the place where that stuff is stored...

**[ACL]** · #**1960** (**permalink**) 03-21-2011, 04:37 PM

Quote:

Originally Posted by natemcnutty

Can't get into it, but you were saying that's because we changed /sdcard to /mnt/sdcard and /sdcard is made during init. I'm looking at editing that right now to see if I can get into recovery again.

we have 2 options. One is to mkdir sdcard right before recovery is requested and the remove it when done so android will be happy.

or leave the mkdir /sdcard as is, and remove it right before exec init.android is called. both need to be tested i suppose.