[natemcnutty]

OK, I apologize in advance for this massive multi-quote. My wife took over the entire night last night, I am just now getting a chance to flash to this. I figured I'd answer a bunch of questions before I start some testing

Originally Posted by m4f1050

Kewl! Thanks!

Booting with new modules now...

Also, what's the deal with all them FSCK0000.REC files? I have been shutting the phone down propperly, seems to be on boot time..?

EDIT: It booted, screen on, came up to lockscreen and in portrait mode!

Trying the screen off and back on....

Noticed LauncherPro restarting one more time than usual...usually it does it twice, did it 3 times now...

Power button acts as HOME button. END button doesn't power off screen...

Auto Brightness lowers the brightness to lowest but screen stays on.

It is very fast and responsive!!!

Should I download the lcd app from market to switch from 210/240?

The FSCK files can be deleted by putting a custom command in the user.froyo.conf. If we can't even use them, I can program it to just delete them in the rootfs just to keep it clean as long as we can't use them for anything.

For the HOME/POWER Button stuff, I'm tired of trying to deviate from what the developers have decided. I personally think we need to find a way to move the mappings into userland, and F22 was looking into that last I heard. He has a thread over at XDA about it.

LCD Density should already be set to 240 in tinboot. Not sure how you are managing to get it back down to 210. Check Tinboot here: tinboot/tinboot2.S - tinboot-linux-msm in Tinboot for linux-msm - Gitorious

Originally Posted by [ACL]

damn fsck on boot causes this. I get them randomly myself but i havent payed much attention to em. I guess now is a good time right . The power down isnt working 100% so that may be the root cause.

Thanks

Is there anything useful we can pull from the FSCK? I didn't think there was, but I figured I'd ask

Originally Posted by m4f1050

No, it's the same, Im just asking if it's possible. But yeah, Haret does the same.

LCD DENSITY app from Market works great. Switched my density to 240. Used to that one...

Upon restart the phone was a bit slow at beginning, I guess it's a hit-n-miss deal?

EDIT:

Well, the screen now turns off with the END button. I used SPARE PARTS and set the phone to SLEEP when I press END. I had it going to HOME because POWER used to sleep phone...

I wonder if you have a custom command somewhere that is changing the lcddensity back to 210, because on Haret, almost every startup.txt I've seen has 240 programmed in, and the launcher utilities set that too.

For all the issues with the HOME and END key, I would recommend making sure you are using the latest NAND RootFS. I'm just finishing up some testing on a new RootFS I just compiled, and I should be updating the first in a few hours as well.

Originally Posted by MassStash

manually editting the msm-gpio-keys.c, what is the change to make?

static struct gpio_keys_button rhodium_button_table[] = {
/*KEY GPIO ACTIVE_LOW DESCRIPTION type wakeup debounce*/
{PWRK, 83, 1, "Power button", EV_KEY, 1, 0},

change 83 to 18?

Don't change the buttons, just change what they do. Make sure #define PWRK KEY_HOME is set, then change KEY_POWER is changed back to PWRK. Then, for RootFS, you need to add # before the 3rd line for your keyboard layout in init (it's the line for navi pad).

At least I believe that is all we have to do because it has been a while since I looked at that, and newer updates kept breaking the git reverts that I was doing.

Originally Posted by guruvince

So USB tethering works with this build? Please elaborate all steps to get this working. Does this mean that USB is fully functional?

This has the same USB functionality as Haret has. We had the commit first, tested it, and then moved it to Haret. I cannot comment on USB tethering as I have not tried it yet, but ADB works great, reading the SD card works, and I know Windows sees the device as a modem, but the drivers don't install properly on first plugin.

Originally Posted by MassStash

somethings weird, havent changed anything myself, running nates 1-7 mods and flashed rhodimg, keymapping gives me garbage for fn anything

Just an FYI, the keyboard mapping is done by the RootFS, and the 1/7 package I put up is just a zip of the files directly from the autobuild.

Originally Posted by pts69666

That is odd... I wonder if it still has the keymapping override programmed in. Try making a .kb file and seeing if it gives you a different keymap and if it helps at all. Otherwise, I have no idea. It works great for me.

Yes, the .kb override is still in there. I do have a test rootfs that I'm working with that cleaned up the code for it. It seems to be working for me, but I haven't released it yet.

Originally Posted by Andr3Wcz

Are headphones working with nand android? Thanks a lot for your work!

Nope, but I have a ton of dumps from Haret for it. I'm trying to wrap some other stuff up and figure out what is going on there to see if we can come up with something. It's on the list of things to work on for sure

Originally Posted by aalim

links to 22/12 files has been removed ??

I didn't delete it, so someone reported it as copyrighted material... I'll be building a new full package here in a few minutes, and I'll push it through pixelpipe this time