[Galaxy S II Android Development] Chef_Tony:
while the topic of on screen buttons is still fairly recent:

everybody who has problems with the zip flash:

you can simply add the following line to /system/build.prop:

qemu.hw.mainkeys=0

on screen buttons should really be an option in this rom directly. i know, this is supposed to come without mods and be vanilla, but there is a difference between vanilla and nexus experience. on screen buttons are definitely nexus experience. they should be optional though as they take up valuable real estate on the screen and force most apps into an unusual resolution.

another option i would very much appreciate is to use the menu button as recent apps button, like it is with the galaxy nexus and here is why:

these days, when apps have the appropriate target sdk, they come with an actionbar and all menu options that do not fit go in the actionbar overflow, meaning all menu items are to be found on the top right of the display. with the s2 and its unnecessary legacy menu button, you see some menu items in the top right and if you want to see more, you have to press the menu button on the very bottom left of the device, which is incredibly un-ergonomic.

also, in many cases you don't even know there is a menu if you don't press the menu button on every given activity screen. i for one didn't know, how many system settings had sub-menus, because i was not informed through the 3 little dots in the top right. see these screenshots for correct actionbar overflow behaviour, which we never have with this rom (or f1nexus for that matter):

you’ll say: “tony, this is but a minor detail, nobody cares”

au contraire, this misbehaviour is visible in almost every app these days and spoils the nexus experience, in the play store, all google apps and practically all apps from the play store, that use the holo theme or any of its derivatives and here is what the android developers at google have to say on that topic:

http://android-developers.blogspot.de/2012/01/say-goodbye-to-menu-button.html

in conclusion:

sticking to the menu button makes most apps today look not super and not nexus. there should be an option to remap the menu button as recent apps button, thereby informing the system there is no menu button, which enables on screen menus through actionbar overflow.

it seems it is as simple as adding one line in the build.prop, so there shouldn't be a problem to make it a checkbox somewhere.

the same goes for the re-mapping of the menu button.

can anybody help me on that?

basically, what i want is:

menu -> recent apps

home -> home

back -> back

long press home -> nothing (or google now)

long press the other two buttons -> nothing (or custom, let's say camera etc.)

also, let's not forget about the other bugs, which i reported before and some others spread over this thread:

- face recognition not working in camera

- picasa web albums not showing in gallery, although sync activated

- gallery has no settings apparently in contrast to the gallery on f1nexus (which can enable picasa sync)

- non nexus button mapping (it should really be optional)

- slow usb transfer speeds

- no game controller support (sixaxis doesn't work, and when it is installed, not even active, rockstar games don't work, possibly has something to do with wrong button mapping in the system as well)

- wi-fi sleeps while the display is off. this was never the default option in any faryaab rom, so i didn't think to check the settings, now i apparently ran through my data plan quite fast. (this is not a bug, just odd and to warn other users.)

but on the plus side and to join the general pointless brown-nosing:

usb debugging with eclipse finally works with build 3.

that is a big up point for me, thank you on that one.