Database Users

Poosible to map start menu to a soft key?

I know you can map the start manu to any of the hard buttons but I would like to map it to one of the soft buttons under the screen.
I know how to map the soft buttons to any application but I'm not sure how the start menu is called.

In the "Buttons" setting at "2. Assign a program:" you have to scroll up the list to the entries in "<...>". Those are the various assignable system features. One of it is "<Start Menu>".
For instance I assigned "<Start Menu>" to the Voice Dialer button and
"<OK/Close>" to the Internet Explorer button - very handy....

I want to assign it to one of the soft keys, not one of the keys you can map in "buttos"

Hi everybody,
I made almost the same.
the pitty of this way, it's the hard it becomes to navigate with one hand.
The thing I try to changes is when I use the phone, to set up the arrow key to access to the "Call History" or the "Speed Dial numbers" like with the Blue Angel (QTEK9090).
Does somebody know how to do it?

I tried AEBPlus, which is a freeware app that allows you to map your harware buttons to up to launch up to 3 different apps each (one click for first app, 2 clicks for second, 3 clicks for third). BUT... its not yet designed for the Wizard, so it does not recognize the soft key buttons yet. It also does not recognize the Comms Button...
So when I installed, I mapped IE button to 1 click = "OK" and 2 clicks "IE" and the Messaging button as 1 click = "start" and 2 clicks = "Messaging"
For some reason it remapped my "Comms Button" to "IE" and as I cant see that button any more in "settings/buttons" I cannot change it back :shock: But I have "Comms" set up as one of my "Start menu" items, so I can get to it via the button I mapped to the start menu.
I e-mailed the designer to see if he plans to update it for the Wizard. The wizard is included on his compatibility matrix, so he may be planning to. If he does that and includes the "soft key buttons" and the "comms button" we would be set.
Perhaps anyone else thats interested could e-mail him too and see if he will update it for a "donation" from each of us..? Its Alexander at : [email protected]
Regards
Chris

try this....

Just load Smartskey. It gives you a lot of secondary functions for soft keys and buttons. I really like it because it has default settings to open the start menu on a long press of the left softkey button, and to do an ok/close on a long press of the right softkey button. It can also manage OMAPClock overclocking functions, if you drop a copy of that app in the same folder as Smartskey.

To ikarus,questions regarding to Batterystatus-->devicelock

Hi Ikarus:
I am using Batterystatus V1.04.203 Beta4 build0218.
I meet a very strange problem with the "Devicelock on wakeup" function, I am using WM6, while I am selected this option, when I press "Power" button which suppose to shut down the pannel,I saw pannel shut down and then immeditely turn on with "Screen Locked"!,i have to press "Power" button again to shut down pannel.
I didn't select the option for "Lock if display is Off and vice versa" and "black fix for 10s-bug".
The right behavior suppose to be: Shut down pannel after press "Power" button and press "Power" again to wakeup device and shows last menu with "DeviceLock".
Can someone tell me how to remove the devicelock for first pressing "Power" button? thanks a lot.

hm.. have a look at the intro-message of BS-Thread. There you can see something with DeviceLockOnWakeup..
Create under BatteryStatus-Registry-Key (see manual) a DWORD with name DeviceLockOnWakeup and value 1,
that is DeviceLockOnWakeup = 1
Enter the options and leave them. that's it.

Hi ikarus:
Great, it works, Thanks a lot!

Adding delays to the 4 buttons on the EVO?

If any of you programming geniuses out there can figure out a way to add a small delay to the 4 EVO buttons a lot of folks would be very grateful.
Those buttons are just way to sensitive and are constantly getting bumped. They need a small delay (option?) to make them a little less subject to accidental triggering.

not a problem for me

i see what you mean, but honestly, i prefer them nice and fast and responsive with occasional accidents. my $0.02.

It wouldn't help I think because it's usually like part of your hand that sits over them.

yeah this is a terrible idea

I don't think it's a terrible idea... like 10-15 times a day if I am holding the phone with my right hand, in landscape mode, parts of my palm or whatever seem to activate home or search. PITA

Just to be clear, are you wanting there to be a delay in between button presses so that you don't accidentally hit the buttons multiple times when you meant to hit them once? Or do you want the buttons to require a long-press in order to activate them?

Saturn2K said:
Just to be clear, are you wanting there to be a delay in between button presses so that you don't accidentally hit the buttons multiple times when you meant to hit them once? Or do you want the buttons to require a long-press in order to activate them?
Click to expand...
Click to collapse
for me, I'd just like for the instant-press to be disabled, and make a half-long-press, of sorts. Basically, to disable accidental 'brushes,' that could activate the buttons. It's not a huge problem honestly, but it sure does make me miss having REAL buttons. I've never been a fan of capacitive buttons, like on my laptop. A real, old-fashioned button always works better.

This happens to me all the time too. I don't know if a half-long-press, short-press, or press-hold would really make any difference. I think I trigger the buttons in just about each of those ways accidentally daily. What I could see as a potential solution is a button lock app.. maybe gesture based and floats on top of any full screen apps? If only I was more cody, I would try my hand at making it..

Find the value or command that equals a long press and I can probably do it.

BuglessPete said:
Find the value or command that equals a long press and I can probably do it.
Click to expand...
Click to collapse
This is for 2.0, and it applies to hardware buttons. I'm not sure how the EVO deals with the buttons since they are capacitive touch buttons. And it may be different in 2.1 (and HTC for that matter). But it's a start:
From http://developer.motorola.com/docstools/library/Basics_of_Event_Management/
"Long Press Events
Prior to Android 2.0, detecting the long press was only available to UI elements by implementing the event listener OnLongClickListenerand registering the View with setOnLongClick(). In 2.0, support was added for a new event handler to detect long presses on hardware buttons.
Code:
@Override
public boolean onKeyLongPress(int keyCode, KeyEvent event) {
if (keyCode == KeyEvent.KEYCODE_CALL) {
// A long press of the call key.
// Do our work, returning true to consume it. By
// returning true, the framework knows an action has
// been performed on the long press, so will set the
// canceled flag for the following up event.
return true;
}
return super.onKeyLongPress(keyCode, event);
}
The callback is triggered by any key press-and-hold. To determine what key was pressed you need to test for a specific key code."​
I believe these are all of the key codes that would be returned: http://developer.android.com/reference/android/view/KeyEvent.html
Of interest:
Code:
public static final int KEYCODE_HOME
Since: API Level 1
Constant Value: 3 (0x00000003)
Code:
public static final int KEYCODE_SEARCH
Since: API Level 1
Constant Value: 84 (0x00000054)
Code:
public static final int KEYCODE_MENU
Since: API Level 1
Constant Value: 82 (0x00000052)
Code:
public static final int KEYCODE_BACK
Since: API Level 1
Constant Value: 4 (0x00000004)

thread moved to EVO General discussion

I too would really love to see some kind of hack that allowed for customizing the delays for these buttons. Even a 1 second delay option would be great. I accidentally brush those buttons several times a day.

[Q] onPause() by home button pressed send intent - delay

Hi
I have two activitys and have following use case:
If user presses in the first activityOne the home button, onPause() is called. In onPause() I'd like to send an intent to the second activity to launch it.
Technically it works, but there is a huge delay betwend pressing the home button and launching the activity, about 4-6 seconds. If I send the intent by any other button pressed, it switches immediately.
Is it possible to speed up the switching or is this a given android behavior?
Regards,
cloooned

its a pretty bad level of coding to start an intent when onpause is called. consider just pressing the home button of your phone to exit the app leads you to some other activity instead.
also onpause will only be called when the activity goes to background. it will take a bit of time to reach that point.

Since the key event has been removed from the home button in Android 4.x, it seems to be one of the few chances to catch the home button pressed event. One other possibility is to overwrite the launcher with the activity and change the launcher default settings, but this would go to far.

Android prohibits you from starting an activity (from an intent) within 5 seconds after the user presses the home button. All startActivity intents will be delayed and executed after this 5 second interval. It is bad practice to start a new activity when the home button is pressed since the home button is the users last resort to escape an application.

Back button close the current application ? How i can change that ?(not force close)

I made a video so you can understand it better
So ... as you can see pressing the back button close the application or something like that and pressing the home button to leave it will result in a smooth animation when re-entering it
is there a way so i can change that ? i really like the way how application open when i leave them with the home button

I can't watch the video right now, but I will assume you are not talking about long-pressing the back button.
I guess that is just how applications work. Home button let's them run in the background and back button closes them.
The only way you can change it is with xposed or a custom rom.
Edit: Changin the behavior will also take away the ability to use it for what it was intended: to go back.
You can assing it another function or disable it altogether, but either way, you will lose the back function of the button and will have to use the app integrated back buttons.

prologikus said:
I made a video so you can understand it better
So ... as you can see pressing the back button close the application or something like that and pressing the home button to leave it will result in a smooth animation when re-entering it
is there a way so i can change that ? i really like the way how application open when i leave them with the home button
Click to expand...
Click to collapse
From another source:
Back Key :
If you press Back Key, onPause(), onStop() and onDestroy() callbacks will called.
Activity will created again by system calls onCreate() callback, then onStart() and onResume() callbacks will be followed.
Home Key :
If you press Home Key, onPause() and onStop() callbacks will called.
Here Activity will restart by system calls onRestart() callback, then onStart() and onResume() callbacks will be followed.
Click to expand...
Click to collapse
The back key will quit the application while the home key will let it run. That are the main differences. That's why they act differently. If you still want it, I know that CM based roms support changing of the layout.

but how ? or how i can search ... i only found that some layout are in generic.kl but here is just a simple match up, keys with functions idk ..
OR this is writed in the app code ?