View Single Post
  #170 (permalink)  
Old 02-03-2011, 03:49 AM
manekineko's Avatar
manekineko
Regular 'Geeker
Offline
Threadstarter
 
Join Date: Jul 2009
Posts: 478
Reputation: 845
manekineko knows their stuffmanekineko knows their stuffmanekineko knows their stuffmanekineko knows their stuffmanekineko knows their stuffmanekineko knows their stuffmanekineko knows their stuff
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: READ BEFORE YOU POST SOMETHING ISN'T WORKING: Known issues affecting all builds 1

Quote:
Originally Posted by F22 View Post
When I polled the users on XDA a few months back, almost nobody liked the current setup, but those who didn't like the current setup were split between those favoring power as power with end as home, and those favoring end as power with power as home. The ratio was about 2:1 in favor of the former over the latter. Nevertheless those favoring the later possibility such as yourself were just as highly passionate regarding their preference. Even the devs were split on the issue, and that's probably why there hasn't been a decision to change the current status quo which next to nobody likes. We'd like to eventually make this all reassignable from within android's framework by the individual user at some point, just like short-cuts, but that's later down the road.
Yup, it'd be great to be able to see options for both camps down (home = top vs. home = end) the road in the official rootfs. I was using your home = end rootfs prior to rolling my own, and in the end it's mostly just picking your poison, either it's weird how you turn off the screen, or it's weird how you end calls.

It's really true that the current default setup makes nobody happy. It's supposed to be for the newbs but it just confuses them that there is no Home button by default, and even after Spare Parts they lose the key multitasking recent apps button.

Maybe you should make your home = end the default, and make the startup.txt option necessary for the current system that nobody likes.
Reply With Quote