Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)
 

Thanks, that confirms what I was wondering. That means ACL has to compile a new recovery that uses the updated button mappings. I've looked through the recovery files, and this must be compiled into android.recovery because I can't find it being analyzed by any of the scripts.

Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)
 

'Is this with the current Mapping? Or the old ones?
'He will only have to recompile if they are the New ones... Which would be a waste of time when he goes back to the old keymapping.

Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)
 

to work as off current commit, you have to make key_end = key_home. So to keep the same key mapping, acl need to release updated ASR... with advanced menu hopefully... :_)

Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)
 

Since you all are working on the keys, is there a way to swap the POWER with END and I am guessing the END CALL "function" has to be fixed as well, that way you don't have to press POWER button to end a call? Not familiar with this but just throwing this out there...

Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)
 

yea man, that is what i'm all about. the way i have mine is home = end key; power = power key; endcall = mute button on back. If you DO NOT have mute button on back, then you will have to go to = accessibility in settings and set the end button to endcall INCALL as opposed to being able to go "home" during call... so as long as that's not the norm, I'll be cookin my shizit up like my rootfs was...

Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)
 

If it had END in the screen it would be even better, but I rather END CALL with END BUTTON rather than going HOME.. Can the MUTE button be used to go to HOME?

Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)
 

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? :angel4:

Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)
 

Well, he actually committed the change to the new ones the way XDAndroid on Haret is. I don't know if we plan to revert it back to the old way or not, but the way it sits on the git right now, we need to recompile recovery.

Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)
 

^^^^

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!).

Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)
 

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 ?