New Application Idea:
Physical button replacement Widget w/ assignable hot key and reaction.
You know how some speculate... Android probably can be ported to just about any device... and I say why not. But one problem I believe always exists.
Not all devices have the same button layout as standard current android devices.
Lets make a fix for that.
Please create a Physical button replacement widget with assignable hot-key and
reaction.
Requirements:
Android OS with widget installed and 1 Physical button minimum.
[ooops just realized there is a thread for app ideas... if mod wants me to move it there i can... sorry for inconvenience.]
Key Features:
-Devices with more than 1 physical button can also be assigned to.
-Widget becomes invisible but still on-screen when not in use (1x4 size) {similar to voice text's widget}
-Customizable reaction times or presses of hot button can be made
-Widget has Toggle for {[Contacts][Menu][End call]}
-Any configuration or single button press reaction can enable the home screen return and widget visibility
Application Scenario:
Android Assimiated onto an Iphone 3GS (OSX completely ripped out and Android ported on to replace it)
App is accessed through app drawer to set "Hot key-Physical button and reaction times" in this case "the home button", changed setting of widget to invisible unless hot key engaged and reaction times set
once set... back to desktop...
Long pressed on desktop... apply widget (1x4) to bottom of screen... invisible
Reaction of hotkey engagement.
Long press (3 sec hold) = (auto-home button/widget viewer)
Reaction: returns you to desktop home screen and widget toggles are now visible to see...
{[Contacts][Menu][End call]}
Of course Contacts acts like contacts app and menu, end call react like physical button scenarios
Double tap Hot-key = "Back button reaction"
Single tap Hot key = app menu button
I really believe if someone creates a widget like this... developers can hack other smartphone devices and assimilate other devices to run android easier.
Palm pre can have the single physical button now as hotkey.. etc etc too
This can translate future android builds to be simplified with less physical buttons causing more screen real-estate
Hopefully this can be a possibility.
All hail Android! Mwahahaha
[Sorry, Just realized there is a thread for app ideas... if mod wants me to move it i can do so... sorry for inconvenience]
Related
Hi, all. New Fuze owner, new XDA-Developers user. Thanks for all the great tips I've found here so far. These are great forums.
I recently installed AE Button Plus to see if I could improve the functionality of the hardware buttons. I have been able to add additional functions to a couple, but some haven't worked and I'm having a hard time mapping the buttons in the program list to the hardware. For example, the app lists App Button 1, App Button 2, App Button 3, App Button 4, and App Button 5, and as far as I can tell, these don't do anything. I also have Long Send and PPT (Hold) listed, neither of which is a separate button. (I also have Button #40C7, which I think is the PTT button I added to the registry manually a couple of weeks ago.) On the other hand, the Home and Back keys aren't listed at all.
For those of you who use the product, would you mind posting the following?
1. Which buttons (as well as softkeys, etc.) have you been able to remap?
2. For each button, what is it called in the program list?
3. For each button, have you been able to map all four functions (short press, long press, double tap, triple tap) to it?
4. Anything else you feel might be helpful?
I hope I have explained this is a way that makes sense. If not, please let me know.
Thanks very much in advance for any help you can give me.
hey, always kool 2 hear from new ppl (im kinda new myself!)
i have only tried 2 remap a couple of buttons but they have both worked for me.
1. Enter/Action:
-single press=press enter (call default handler)
-double press=press left softkey (helpfull for pressing the send key while texting)
-long press=flashlight (button lights up in dark and is quick)
2. Red phone button
-single press=taskfacade (hitting it does nothing more than the home key, so i made it into a taskmanager)
i didn't really find the need to remap anymore keys because of the default one's on the keyboard (internet, text message, email,and comm)
There are many buttons in the app that aren't on the phone. To Map the Home key, you have to Add Button (on the left soft key menu).
I map it to the Start Menu...which I have as QuickMenu. seriously, once you go Quick, you never go back.
Keep in mind, for some reason the Home key will ALWAYS go to the Today Screen, then do whatever you map it to in AEB...this is a known issue.
Good Luck!
I disabled the hard-volumekeys. I now use them as follows:
Up:
2x = enable bluetooth
3x = enable vibrate mode
hold = psShutXP
Down:
2x = close S2U2 (ilock)
hold = camera
Powerbutton (not with AEB-plus):
short: screen off
long: enable S2U2 (because I had several problems taking the phone out of my pocket with a warning the phone was powering off)
Left soft:
icontact
Right soft:
TomTom Navigator
I have tried to map the following:
Green Button
Single press = Press Green Button
Double press = Run application(Launch Manager)
Long press = Could not be mapped!
Red Button
Single press = Press Red Button
Double press = Task Manager
Long press = Could not be mapped!
The home button and the cancel button could not be mapped!!
all i did was remap the home button to open start menu (wm6.5) and the end key to actually end the program rather than minimize it
I'm on a custom rom (RRE WM 6.5 v4).
The PTT button on my Fuze by default on this ROM is customizable so I have that bring up Task Facade (a program switcher) on short press and hTorch on long.
AEB handles
volume up:
-short - vol up
-long - wifi on
volume down:
-short - vol up
-long - close dialup connection
Do you guys think AE button plus has a battery drain since it's always running? I've been running it for years, but now I'm trying to find sources of my battery drain.
has anyone else experienced significant lag in the pressing the button and it performing the task?
i only used the trial on an oem fuze rom and mapped the double push of the down key to the task manager and a single push to do the normal move down..it would lag horribly to do either task and i never could get the long press to work reliably..
i havent tried it on a cooked rom and never bought the full version due to these issues..
All buttons can be remapped except short home and short red I think, here's my setup and the config file.
(only deviations from default)
VolUp Long - SPB Now screen
VolDown Long - MemMaid Reclaim RAM
Home Twice - SPB My Menu
Home Long - Start Menu
Back Twice - force close
Back Long - task switch
Green once - SPB Dial Tab
Green twice - resco explorer
Green 3x/Long - classic dialer
Red Twice - Rotate screen
Red Long - display off (note that Long End Key app must be set to Lock in odrer for this key to be mappable)
It's got more features than my Artemis and there are still "keys" to be assigned
For the questions above - no battery drain noticed and no lag on Energy ROM 2
The culprit of your battery drain is most likely activesync running 24/7 or try another radio version, also some today plugins can cause serious drain (I tested SPB, iLauncher, Pocket Digital Clock, HomeScreen ++ and SPB Diary with no drain but I had some that ate my Raph's battery in just two days)
nik3r said:
All buttons can be remapped except short home and short red I think, here's my setup and the config file.
(only deviations from default)
VolUp Long - SPB Now screen
VolDown Long - MemMaid Reclaim RAM
Home Twice - SPB My Menu
Home Long - Start Menu
Back Twice - force close
Back Long - task switch
Green once - SPB Dial Tab
Green twice - resco explorer
Green 3x/Long - classic dialer
Red Twice - Rotate screen
Red Long - display off (note that Long End Key app must be set to Lock in odrer for this key to be mappable)
It's got more features than my Artemis and there are still "keys" to be assigned
For the questions above - no battery drain noticed and no lag on Energy ROM 2
The culprit of your battery drain is most likely activesync running 24/7 or try another radio version, also some today plugins can cause serious drain (I tested SPB, iLauncher, Pocket Digital Clock, HomeScreen ++ and SPB Diary with no drain but I had some that ate my Raph's battery in just two days)
Click to expand...
Click to collapse
has to be activesync 24-7...but I know that...too stubborn to get rid of it b/c it's so damn convenient. I just thought push mail was supposed to be efficient...
I'll keep using AE button plus. I recommend it all the time. GREAT program.
Restore Missing Buttons?
I have a Fuse with an HTC ROM and I am missing entries for all my buttons except "Button 1". Can this program restore my missing button entries?
Thx. James
i have this:
green once - idialer
green twice - spb call log
green long - HTC Action Screen
red once - red (standard)
red twice - spb insight
red long - quick list... this wont change to what i want
middle once - enter
middle button long - IM+
volume up once - Up
vol up twice - STart
vol up long - CommManager
vol down once - Down
vol down twice - SPB Menu
vol down long - Volume Screen - Then I am back to up up and down to change volume
I cannot figure out how to map home key - HELP????
Konradwalsh said:
I cannot figure out how to map home key - HELP????
Click to expand...
Click to collapse
All those who want to remap home, back and other keys, which AEButton doesn't process properly, look HERE.
The second version is almost finished and it has more options and can process double clicks like AEButton. I'll upload it in a day or two.
Hello XDA'ers,
I am wondering what the reason behind why the buttons (camera, power, green, red, etc.) in Android on HTC Vogue map to the various tasks they do? For example, the camera button is back, but why not the red button? Is this something hard set in Android and cannot be changed or did someone specifically set it up this way for a reason?
Secondly I am wondering if I create a new "keylayout file" (source.android.com/porting/keymaps_keyboard_input.html) or modify the default one in /system/usr/keylayout/qwerty.kl will I be able to change the mapping of these buttons?
Compared to the Win Mobile mapping, they button layout can take some getting used to,
but once you get used to it, it's actually a very cool layout, especially if you are right handed.
You can hold the phone in your left hand, and use your thumb to access the settings 'top button',
Use your ring-finger to always back-out or end an app
Green button for phone / initiating calls
Red button to end a call, sleep mode, or power off
I wish the d-pad had more use, but I'm always using the stylus, so barely use it.
Would love for the d-pad center key to maybe be the main power-off button.
Does_It_Matter said:
... It's actually a very cool layout.
...
I wish the d-pad had more use, but I'm always using the stylus, so barely use it.
Would love for the d-pad center key to maybe be the main power-off button.
Click to expand...
Click to collapse
I completely agree the current layout is a very cool layout indeed, but as I imagine most people on here like to tinker it may be interesting to know how to customize the button bindings.
I am not sure if its just a matter of changing the button layout file.
I looked at that qwerty.kl file in the android.tgz
It looks like its just a mapping file, and if you change the mapping, you change
buttons,
but doesn't that mean you're just re-mapping the button itself?
Not re-mapping its functionality?
I.e., if you remapped the camera button to the d-pad center, for example, then
the d-pad center would do all functions the camera button used to do,
and the camera button would do any functions the d-pad center would?
Seems like you'd actually have to change more code than just the .kl file?
i wrote this application for polaris, and with simple changes you can add the vogue setup...
With the advent of Nookie Froyo and rumors of CM7 only one thing makes me Pissed off as heck. HARD BUTTONS!!!!! Of course, we could map the volume buttons for these things, but I have a proposal/wish (Since I can't program --_--)
Is there anyone who could make a app so that long pressing a volume button would bring up or lower the volume, and tapping them slightly would trigger the back button or menu button? Or vice versa?
I think this would kill our needs for soft-keys or any annoying launcher stuff. Just a wish. tell me if this is possible plx
or... double tap them --_--
I don't program either, but I was just thinking about alternative methods too, since I find soft keys annoyingly unelegant as well. I like the remapping of the hard volume keys for long presses idea. Another option might be to take a play from the jailbroken iphone book where Activator can launch programs or perform system actions with gestures (swiping in from the top, or tapping the volume indicator box after voluming up/ down, etc) - sort of like how swiping left on the nook status bar goes back or how swiping down the left side of the screen in fbreader changes the brightness of the display. Could be a system wide action where swiping left at the bottom if the screen regardless of if the status bar is visible would go back while swiping right would invoke the menu...
Sent from my Nook Color (1Ghz oc kernel, Android 2.1)
hmm.. well, I guess I'll just have to stick with soft buttons for now. {presses the nook color home button to death}
Several Apps That I Use...
Have gestures that allow the functions that you folks mentioned. For example, Aldiko has a great brightness adjust by swiping down one side of the screen, and Dolphin HD has a lot of gesture-activated commands.
I'm not a programmer but some bright dev out there might be able to come up with the appropriate calls to allow gestures for volume - what about a poll?
I love the idea of softkeys. With it you can put bigger screens on smaller devices and they can disappear whenever needed to.
The main problem is that it's a 50/50% chance that they will disappear when I think that they should. With physical keys that's never an issue.
Movies, yes
Games, yes
Full screen applications, yes
etc.
What determines when the keys disappear and not? Is it up to the app creator? What can I do about it (I'm not rooted)?
They can't always disappear in full screen games. If the game needs a back button you would be stuck.
I assume there is something in there that tells it. Much like if an app does not have an on screen menu button (usually three dots), a menu button will be added to the lower right side of the portion of the screen where the soft keys are.
It's not there for all apps, only ones that don't have a menu button on screen. Not sure if this is declared by the app or if 4.4 can detect it somehow and show the button when needed.
fury683 said:
They can't always disappear in full screen games. If the game needs a back button you would be stuck.
I assume there is something in there that tells it. Much like if an app does not have an on screen menu button (usually three dots), a menu button will be added to the lower right side of the portion of the screen where the soft keys are.
It's not there for all apps, only ones that don't have a menu button on screen. Not sure if this is declared by the app or if 4.4 can detect it somehow and show the button when needed.
Click to expand...
Click to collapse
On my tablet (running 4.1) I get these dots you are talking about (but not in the lower right corner, they replace the ordinary softkeys)). That's all fine because they take less space (from what I remember) then the ordinary softkeys.
If it all comes down to having a back button in the app, why not implement that in the app?
I downloaded crazy taxi yesterday and those softkeys are annoying me as hell.
I ended up getting used to using LMT and just turn on expanded desktop to make the navigation keys go away. That way if LMT gives me any trouble...I just hit the power button and turn off expanded desktop and my navigation keys are back. (Gravity box to get that option in power menu.)
Hated pie at first...but used to it now.
Sent from my Moto X cellular telephone...
Coming from S2, I know it is long overdue lol, and got used to touch-style Home button, I would love to get back to home by just tapping instead of pressing Home button. Is it even possible?
Thanks.
re: home key
doanthaitu said:
Coming from S2, I know it is long overdue lol, and got used to touch-style Home button, I would love to get back to home by just tapping instead of pressing Home button. Is it even possible?
Thanks.
Click to expand...
Click to collapse
There are two ways that it can be done.
Once we have a proper custom recovery like twrp you can use the softkey mod
which has the option of adding three softkeys menu/home/back buttons on the
bottom of your screen, they look exactly like real softkeys and are transparent.
The other way to do it would take a bit of getting used to is
the mod which can re-assign the back and menu keys to be
the home key or basically any anything else and can be
configured for long press, double tap or single tap.
Some of the high end launchers already have this feature of
re-assigning keys built-in like the "Next launcher 3D shell".
The Next launcher even has option to replace the home key
by simply swiping up or down to replicate the home button's
default/normal single tap.
With the Next Launcher, we do not even need root or custom recovery.
Good luck!
I've used Go launcher free version forever and got used to swipe down anywhere to bring down notification, I wonder if TouchWiz has this function? With the phone of this size, this function is a must.
And I miss AOSP dialer, swipe left or right to go to next tab. Touchwiz's dialer has the tabs on the top, makes it impossible to use it 1 hand.