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

**natemcnutty** · #**2091** (**permalink**) 03-25-2011, 12:19 AM

Quote:

Originally Posted by [ACL]

ahh fellas.. there was a reason why i didnt auto-build this. It was because i didnt test, so come on give me a break with all the questions. If you roll your own kernel, im going to assume you know how to fix it. Its a simple fix, anyone can roll back.

Ok, i think i missed what nate said earlier about deploying the navipad file. That does not sound like a bad idea to me. I say this because if anyone wants some whacky layout, we simply android update the file and viola. Problem solved. So navipad for everyone. With that said i will have to leave the kernel as is for now and the install script needs to be modded.

Ok on to business. Nate did you test the mtd parts you posted? sure it does not break wifi ?

anyone test the new ril on the old build ?

Thanks ACL. Yes, the mtdparts I posted are perfect and cause no issues with wifi. I posted a test NBH, arrrghhh test it out when I first posted those a few days ago. I'd love to hear feedback from others that are compiling their own right now, but it has been great for me for a few days so far. I flashed about 20 times the other day seeing how low I could go without running into the protected area, and that was what I ended up on.

As for the navipad, I just know stinebd added that to rootfs when we made the button map commit that I posted earlier. When I compiled the kernel with that commit but didn't update rootfs, I ended up with buttons not functioning, so I figured we needed to add the navipad file once that commit was made.

**natemcnutty** · #**2092** (**permalink**) 03-25-2011, 12:21 AM

Quote:

Originally Posted by Lmiller1708

^^^^

It looks like he is already going to revert back.
I talked with him earlier today too and is the path he was taking...

Reason being is with the new keymaps (like Haret) we will lose the "recent items menu" and not be able to turn on the screen by the top button (it will just end the call, very annoying!).

Thanks buddy, somehow I missed that post! I swear I've read every single post in this thread, but man have we been putting on the miles lately...

MassStash · #**2093** (**permalink**) 03-25-2011, 12:33 AM

[acl], currently on new ril old kernel and ev-er-reee thangs good

sorry if i helped in shmobing the forum, just tellin dudes ill be makin alt keymappin so they cant stop ASKING haha

**[ACL]** · #**2094** (**permalink**) 03-25-2011, 12:38 AM

Quote:

Originally Posted by natemcnutty

Thanks ACL. Yes, the mtdparts I posted are perfect and cause no issues with wifi. I posted a test NBH, arrrghhh test it out when I first posted those a few days ago. I'd love to hear feedback from others that are compiling their own right now, but it has been great for me for a few days so far. I flashed about 20 times the other day seeing how low I could go without running into the protected area, and that was what I ended up on.

As for the navipad, I just know stinebd added that to rootfs when we made the button map commit that I posted earlier. When I compiled the kernel with that commit but didn't update rootfs, I ended up with buttons not functioning, so I figured we needed to add the navipad file once that commit was made.

Cool.. so ill leave it up to you to add the navipad to the install script. Also i posted the recovery scripts so you can update that one as well. THey are slightly different but similar in many ways. (git is acting up actually so i dont know when they will be posted )

ALso if ur mtdparts are solid, then im committing.

**natemcnutty** · #**2095** (**permalink**) 03-25-2011, 12:48 AM

Quote:

Originally Posted by [ACL]

Cool.. so ill leave it up to you to add the navipad to the install script. Also i posted the recovery scripts so you can update that one as well. THey are slightly different but similar in many ways. (git is acting up actually so i dont know when they will be posted )

ALso if ur mtdparts are solid, then im committing.

Awesome. Just pushed the navipad part for /recovery/install-seq.sh. Also, there isn't anything I can do to help with the button mapping in recovery, right? That is something compiled into android.recovery?

As for mtdparts, it has been tested on rhod400 and rhod500 so far that I know of. I would assume all of them are the same, but you never know.

**[ACL]** · #**2096** (**permalink**) 03-25-2011, 01:02 AM

Quote:

Originally Posted by natemcnutty

Awesome. Just pushed the navipad part for /recovery/install-seq.sh. Also, there isn't anything I can do to help with the button mapping in recovery, right? That is something compiled into android.recovery?

As for mtdparts, it has been tested on rhod400 and rhod500 so far that I know of. I would assume all of them are the same, but you never know.

Cool.. mtd parts pushed .

now its building and testing time. if i have luck , then there should be new files on autobuild. still plenty to do since all i finished were kernel updates..

tiger2wander · #**2097** (**permalink**) 03-25-2011, 02:30 AM

@natemcnutty you can add initrd.gz to .gitignore file inside bootenv repo to lets git avoid it. (I see commit log which ur trying to avoid git to commit that binary file), Its global way to keep another user ignore that file from commit.

I use install-req.sh from andboot to install new system with latest kernel and everything, wifi still won't work, I'm going try the way suggested by nate, pull all the latest and try now with new mtdparts & new ril :P

@[ACL] r u still need new ril with old kernel?

**natemcnutty** · #**2098** (**permalink**) 03-25-2011, 02:52 AM

Quote:

Originally Posted by tiger2wander

@natemcnutty you can add initrd.gz to .gitignore file inside bootenv repo to lets git avoid it. (I see commit log which ur trying to avoid git to commit that binary file), Its global way to keep another user ignore that file from commit.

I use install-req.sh from andboot to install new system with latest kernel and everything, wifi still won't work, I'm going try the way suggested by nate, pull all the latest and try now with new mtdparts & new ril :P

@[ACL] r u still need new ril with old kernel?

Don't need to add it to git ignore because we aren't going to commit it anymore. ACL owns the git and I contribute and that's it. We aren't pushing the binaries anymore, so it doesn't matter.

For wifi, it has been working perfectly for me and others. Not sure what the issue is, but dmesg is your friend

vistazifta · #**2099** (**permalink**) 03-25-2011, 03:02 AM

Quote:

Originally Posted by tiger2wander

@[ACL] r u still need new ril with old kernel?

-thanks was gonna ask same thing^^^

-and just to make sure i understand, if we want to map our own keys we modify the navipad file and install it via advanced menu in recovery?

-with all the changes such as iff yes to my question above and the soon to be available switch to gsm ril via advanced recovery i believe the faq on page one is asking for an update lol if u guys r to busy with other sh1t then ask and i can try to write it up and have name insert it

tiger2wander · #**2100** (**permalink**) 03-25-2011, 03:11 AM

In the last build I have use install-req.sh to install android on NAND and tested keyboard again, seen model detected correctly by kernel and load correct keyboard map for it. Return to normal functionality

Still wait while charging using external charger done it job with my batt

About ril, I have create my androidupdate package include new ril & all app, data pre-configured to get phone ready to use right after install and its save a lots time!

Trying to compile latest busybox from source but still got error, any suggestion? I think it is required some more headers to build. I'm using LinuxMint (based on Ubuntu 10.10)

--
Best regard!
Uoc Nguyen