Re: What modifications are necessary to create a fork that re-enables the home button
 

Ouch. Oh well, so much for that. I can't maintain an entire kernel branch.

Any idea what the rootfs change was for if the kernel change on its own was the only necessary and sufficient condition to changing the keymapping?

Is there any way that the kernel could be altered to push the way the power button is handled into the rootfs the same as keyboard keys?

Re: What modifications are necessary to create a fork that re-enables the home button
 

QFT!!!

I just want to mutil task! Unless I am missing something the only way to do that is back ALL the way to the home screen(which can be MANY key presses)

Losing this feature has made me go back to using Windows as without the ability to multi-task I feel like I'm using a I-phone :( Which I am very ashamed to say, as I was just bragging about how much better the TP2 w/android on it is...

If no one can hint on a way to multi-task I guess I will have to revert back...

EDIT- I did just find that I can remap the home key to end key, which helps, but only a little bit. From what I've seen there is no way(easy) to remap the long-press, please correct me if I'm wrong

Re: What modifications are necessary to create a fork that re-enables the home button
 

There is no way to remap long press without hacking the rootfs and the kernel.

Just keep your phone back if it's really that big of a deal!!!!!

There, hopefully that settles it.

Re: What modifications are necessary to create a fork that re-enables the home button
 

I think I found a way to do it!!! I'm gonna sign up for C and C++ classes and learn the role of developer, and then in my spare time work on a labor of love and get the freaking button fixed for everyone!!! I should be ready in a few years.... Honestly, if it's that much of a PITA for people, do something usefull and learn to code and do it yourself. I would personally love to have the functionality back, but the fact remains that no pissing and moaning by anyone is gonna change it, unless the developers want it done, and it appears they don't, so let it go. If you want full functionality, go get an Evo, Epic, D2, Incredible, etc, there are plenty out there to choose from. I can't at this point get a full droid and I still love my TP2 so I'm happy with whatever the developers come out with. If I don't like it, no one is forcing me to use it. Does the change make me smile and feel all warm and fuzzy inside, not really, but am I gonna piss and moan on a forum about it, while basically telling the developers who give up their free time to do this for nothing that they screwed up the port??? Not a chance in hell. Honestly if it was me doing the developing, I'd say the hell with it, don't want it, I'll keep the files to myself. The phone was made w/ WM on it. Because of guys like these developers, we're able to not only flash the phones to different ROMs, different radios, put different OS's on them, do all sorts of crap to make them just the way we want it. How bout a little respect for them and for all they've done for us so far. If they gave up on the project tomorrow, I'd still show them some thanks and appreciation for what they've given us to date!

Re: What modifications are necessary to create a fork that re-enables the home button
 

Fortunately, you don't really have to learn any programming to revert the change thanks to the magic of git. As I promised, I am working on creating the kernel exactly as it is for the main thread with just the button mapping reverted.

Since I am on NAND at the moment, I have no way to test this. I will be posting a zImage/modules here in about an hour when I get back from my meeting (unless it runs short or long).

Re: What modifications are necessary to create a fork that re-enables the home button
 

Indeed. What I'm curious about is going forward. How difficult is it going to be to maintain two trees? I guess since the changes are simple/trivial, it won't be too difficult...

Perhaps git is smart enough to pull a commit each time there's an update. I'll let you work that magic nate ;) Thanks again bro.

Re: What modifications are necessary to create a fork that re-enables the home button
 

That sounds like a plan, I just wonder if I can get a refund on my programming classes I signed up for, lol. I appreciate you taking the time to do this stuff, as although you may seem to think it's a piece of cake, I for one don't, and truly appreciate all that you and the others are doing. I can perform some surgical type procedures out in the field to save lives, but I'd be better off building a rocketship to go to mars than to try to do what you guys are doing!

Re: What modifications are necessary to create a fork that re-enables the home button
 

OK, anyone want to test out this and let me know. Edit: Didn't work. Trying something else :(

Re: What modifications are necessary to create a fork that re-enables the home button
 

Doesn't work for me... POWER is still POWER...

Redoin the steps, make sure I didn't screw anything up.

Re: What modifications are necessary to create a fork that re-enables the home button
 

Tested with rhod400 on neopeek vaniljeclair. The buttons act as they did before, both power and hangup buttons put the phone to sleep. Long press on both bring up the shutdown menu as well. I can install and retest on xdandroid if it makes a difference. I wanna say thanks for giving this a shot, it has bothered me to since the change lol