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

[natemcnutty]

Originally Posted by vistazifta

-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

I haven't had a chance to test this, but if we were to do it through the navipad, you would swap these two:

key 116 POWER WAKE
key 107 ENDCALL WAKE_DROPPED

lol, some of this stuff like the navi_pad hasn't even been settled on or tested yet. If you want to write up FAQ stuff, please feel free and I'll put it up there. Not sure what you have in mind that is so out of date

[natemcnutty]

Originally Posted by tiger2wander

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

Busybox was a real pita for me to compile because it required a bunch of other stuff to compile too. Can't remember what I did when I did that.

[vistazifta]

Originally Posted by natemcnutty

I haven't had a chance to test this, but if we were to do it through the navipad, you would swap these two:

key 116 POWER WAKE
key 107 ENDCALL WAKE_DROPPED

lol, some of this stuff like the navi_pad hasn't even been settled on or tested yet. If you want to write up FAQ stuff, please feel free and I'll put it up there. Not sure what you have in mind that is so out of date

wasnt saying out of date just meant a little behind as u guys add new features right and left and keep reiterating old one all the time so im gonna go thru the thread again and try to c whats workin and whats not but heres an example of something that belongs there u wrote:
On first boot, hold Volume Up when prompted to get into recovery.
first of all u do u need to go into recovery? it seams to have installed fine directly on my rhod400.
second of all as mendion also before in big bold letters You can hold down the center of the screen to enter the recovery.

[tiger2wander]

Yeah, touch & hold center screen is easiest way to go into recovery mode for now
I have never able to get into recovery by hold Vol Up (its always return GPIO unmapped key )

Thanks ACL, him has bring native android experience to us!

But still can not use recovery until ACL push a new build :P LOL

[tiger2wander]

No need to build busybox by myeself, just go to: Index of /downloads/binaries/latest and grab busybox-armv5l or busybox-armv6l
I've just tested and both work well on Android.

[tiger2wander]

With latest code from Git I can not pull battery out while connected with charger to insert SIM card!
I will go back to old stable kernel to use test new ril soon.

[vistazifta]

Originally Posted by tiger2wander

With latest code from Git I can not pull battery out while connected with charger to insert SIM card!
I will go back to old stable kernel to use test new ril soon.

make sure it shows its charging first as i had same problem yesterday when my battery died and i booted off my friends evo battery an took his out and it went off and i realzied there was something wrong with my charger so plugged into usb

[tiger2wander]

I has that problem before and always make sure charger icon present on the notification bar. May be my cable has some problem and its sometime disconnected randomly :P

[m4f1050]

Originally Posted by natemcnutty

Everyone has their own opinion of how the buttons should be mapped out, but you will each have to modify arch/arm/mach-msm/msm-gpio-keys.c to change certain functions. This is why we were saying it would be much better to find a way to map/remap all of the buttons from userland.

That being said, unless you want to modify the kernel, you'll just have to wait for an updated recovery from ACL. Any chance we can get recovery on a git?

Well, I know *some* c++ so I am sure I can modify that, is there a way to put those modifications online and some service compile them for me? I have Ubuntu and Debian on my VM at home, what libraries do I need to download to compile these? Is there a wiki I can check it out?

[chunnel]

I have run the port via haret from the Project Android thread. That appears dead at this point. However, without Bluetooth capability this is not practical for me. Neither thread seems to have that working. So, do you see that as a possibility? Or has everyone given up on that working?