PPCGeeks

PPCGeeks (http://forum.ppcgeeks.com/index.php)
-   Android On TP2 Development (http://forum.ppcgeeks.com/forumdisplay.php?f=319)
-   -   NAND Testing - 05-25 Update: New LK, Recovery.img, Kernel Updates through Recovery (http://forum.ppcgeeks.com/showthread.php?t=134598)

MassStash 03-24-2011 05:27 PM

Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)
 
just saw that, 54 eh? good work bruddas

natemcnutty 03-24-2011 05:34 PM

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

Originally Posted by MassStash (Post 2073301)
just saw that, 54 eh? good work bruddas

Nah, only 1 commit. When you remove history of a file in git, it is recommended to force the push (especially if you have funky merge histories). This just "re-pushes" some of the previous commits. Then you set that file reference to expire and run garbage collection after it has been expired.

MassStash 03-24-2011 05:44 PM

Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)
 
ah, i see. learned bout git tweaks yesterday on my own. We going to get rid of the install-seq in there too?

also, vol buttons in ASR work for with latest kernel updates

update [acl], ril doesnt show up like before in ps. all there is is /system/bin/rild ????
new ril it is?

natemcnutty 03-24-2011 06:09 PM

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

Originally Posted by natemcnutty (Post 2073161)
When XDAndroid decided to change the button mappings, I looked into a program for Android that would let us re-assign the keys, and I wasn't able to find anything useful.

Also, if we made the button mapping commits, then we have to add the navi_pad keylayout copy to the install script for the rhod400/500.

OK, it doesn't look like you made the commit that changed the button mapping, so we don't have to mess with this yet. We will have to add the navi_pad keylayout if you do commit this one though: Commit in linux-msm in Linux on Qualcomm's MSM - Gitorious

Personally, my preference is for the button mapping we have now, but I know it is different than Haret which I guess has the potential for causing regression issues.

[ACL] 03-24-2011 07:00 PM

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

Originally Posted by natemcnutty (Post 2073309)
OK, it doesn't look like you made the commit that changed the button mapping, so we don't have to mess with this yet. We will have to add the navi_pad keylayout if you do commit this one though: Commit in linux-msm in Linux on Qualcomm's MSM - Gitorious

Personally, my preference is for the button mapping we have now, but I know it is different than Haret which I guess has the potential for causing regression issues.

Well being that we have a managed fork, its ok drifting away. After all our code drifter plenty already.

i cant get back on irc for some damn reason to find out if we need to recompile android so the keys are changed there. If so, then lets just do it on our end how it was. Looks like people like home op where power is.

MassStash 03-24-2011 07:00 PM

Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)
 
is this not what changed the keymapping?
Commit in linux-msm-rhod-nand in Linux on Qualcomm's MSM - Gitorious

as of current, compiling is necessary for key-mapping is desired, and i'm koo with that

natemcnutty 03-24-2011 07:26 PM

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

Originally Posted by MassStash (Post 2073324)
is this not what changed the keymapping?
Commit in linux-msm-rhod-nand in Linux on Qualcomm's MSM - Gitorious

as of current, compiling is necessary for key-mapping is desired, and i'm koo with that

Actually, that's a new commit that I haven't had a chance to test yet. I just compiled a new set of files, so I'll be looking at it in a few minutes.

Also, ACL, any chance we can commit the new mtdparts?
Code:

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

EDIT: Poop, I didn't look far enough down. Yes, you are right. The commit I referenced is in that, so we do need to add the navi_pad to recovery. I'll update the install-seq.sh on git for reference since that is what ACL uses in recovery.

I made the changes to the script in the recovery install and am booting up to test right now. I'll let you know how it goes in a little bit.

natemcnutty 03-24-2011 07:35 PM

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

Originally Posted by neopeek (Post 2073210)
Not verified by myself yet but will do soon if still necessarry

I am testing the rildarg changes right now. Will let you know if it works OK on CDMA with the force_cdma option turned off.

ACL, do you think I need the new RIL for this to work?

natemcnutty 03-24-2011 07:45 PM

Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)
 
OK, recovery doesn't respond to any buttons. Anyone else that is compiling right now able to confirm?

MassStash 03-24-2011 08:08 PM

Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)
 
nah, latest compile for me makes MORE buttons work for me lol vol buttons didnt work before the latest kernel updates, and now they do. you change anything? i changed key_end to key_home. turns out recovery doesnt work any buttons if there's no key_home because of acl made it look for key_home. so worked for me without notice of this broken part....

[acl], maybe they blocked irc.... haha


All times are GMT -4. The time now is 06:40 PM.

Powered by vBulletin® ©2000 - 2025, Jelsoft Enterprises Ltd.
©2012 - PPCGeeks.com


Content Relevant URLs by vBSEO 3.6.0