View Single Post
  #5 (permalink)  
Old 10-29-2010, 10:35 AM
arrrghhh's Avatar
arrrghhh
Testing Extraordinaire
Offline
 
Join Date: Mar 2007
Posts: 3,604
Reputation: 7360
arrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the community
Mentioned: 7 Post(s)
Tagged: 0 Thread(s)
Re: What modifications are necessary to create a fork that re-enables the home button

I'm thinking about taking this up with Mr. Stine. It's kinda wacky since our physical buttons wouldn't match, but in Android I think this makes the most sense...

End Call Button = HOME - including long press for HOME
Power Button = END CALL then POWER

Everything else can be left the same. Mute Button = SEARCH would be cool too, but only until we get the speakerphone sorted out

Unfortunately there is no one good solution that's going to make everybody happy - because the phone was designed for WinMo, and not all RHODs have the same keys. AT&T RHODs have a PTT key, and evidently not all RHODs have the mute button... So whatever we end up doing, someone will dislike it. However, it seems more logical to use what native Android devices use in Android, rather than what we're used to in WinMo. It'll all be a lot easier/clearer methinks when we reach the Vogue level - and the development is at a point where haret is no more
Reply With Quote
This post has been thanked 3 times.