Related
there is a new version of AE Button! The Button map application! Any experiences? Is there an improvement for the HD? Let´s test
Anyone tried?
I wish to know too =)
Is it free?
I have this registered.
The unregistered version is actually almost fully functioning and well worth trying.
I choose to register since I found the application useful and it seemed fair to pay the developer.
THANKS, for the new version alert. But, I suspect there is little new as the history details for this version are:
02.02.2009(v2.6.6):
Fixes:
Backlight works on HP 612c now
Languages:
Updated Traditional Chinese resources (thanks to Chow Yuh)
AE Button
I find this software very useful. It completely eliminates the need of locking/unlocking software for me.
I just set double or triple tap to answer and hang up keys. This will prevent accidental key press when taking HD out of pocket. To answer call, simple double/triple tap on answer key or simply slide on screen to answer (built-in screen lock will be unlocked during incoming call).
Set press and hold volume up to toggle wireless and down to toggle bluetooth.
This one single software solved all my screen locking + lack of buttons issues!! Believe me i tried touch lock pro, sensor lock, slide to unlock and what ever you can think of (I didnt like because I think its not really practical for me to be rolling phone 180 degrees or shaking back n fourth in meetings to answer a call.)...I know you guys may argue it has light sensors to unlock, but I'll be in meetings and presentations which might be low light conditions. I do not want to set very small for polling interval either. If you have tried all else, no harm in trying this.
if you guys face the same problem like me, this tiny software might be the right solution for you.
The best combination for me:
Gyrator2 (fine tuned based on my apps) + Lumos + AE Button Plus + Touch Response (for onscreen keypress only).
The only flaw that i could find to complain is that they should really change the icon...it looks like bread/potato/or whatever...
Headset Buttons
Hi there,
is this program able to capture the button press events from a headset wired/wireless?
What I'd like to achieve is, to switch to the next song in Mediaplayer as long there is no incoming or active call.
Is that possible?
Thx in Advance
Steve
noctifer said:
Hi there,
is this program able to capture the button press events from a headset wired/wireless?
What I'd like to achieve is, to switch to the next song in Mediaplayer as long there is no incoming or active call.
Is that possible?
Thx in Advance
Steve
Click to expand...
Click to collapse
Hi, I believe not. I understand the press events from headsets and bluetooth AVRCP are actually trapped in the hardware by HTC and by-pass the operating system and are sent directly to TF3D music or WMP.
If you check on the AEB plus site: http://ae.inc.ru/ it says the app is not for specific applications.
(Also: the AEB+ icon does look like a loaf of bread !!)
Will it allow me to remap the Home button on the Touch HD?
CorruptedSanity said:
Will it allow me to remap the Home button on the Touch HD?
Click to expand...
Click to collapse
Nope. All the others but not the home button.
I have:
1. volume up. 1 press = arrow up, 2 press = volume up, long press = plamp (flash light)
2. volume down. 1 press = arrow down, 2 press = volume down, long press = resco notes recorder (auto)
3. OK / back. 2 press = rotate screen 90 deg
I keep the long press on phone end and long press on phone start handled by the system.
Dave, thanks a lot and you have some very smart short cuts
I may very well adopt them too.
CorruptedSanity said:
Dave, thanks a lot and you have some very smart short cuts
I may very well adopt them too.
Click to expand...
Click to collapse
Thanks, but I'm needing a suggestion for replacing the flash light. Never used this now "for real" so I shall find something else for the long volume up press ...
I have almost identical settings but use the long up as a bluetooth toggle. This is a fantastic program and really eliminates one of the few shortcomings of this phone.
Cheesy Dave said:
long press = plamp (flash light)
Click to expand...
Click to collapse
do you know where i can get this plamp please?
P Lamp v1.5 http://pda.jasnapaka.com/plamp/
Question guys,
How do I map the call button to long press (like the smallest long press ever) to get the Start menu?
Thanks
Sorry, I don't understand what you want. Is "call button" the "end call" or "start call" ?
Dave, call button is the left-most button that answers/makes a call. If it were colored, it would have been green.
I want to short press it to start menu (heres the tricky part, I have Quick Menu as my start menu).
Basically I miss the Start button from my TyTn II (Kaiser) and the scroll on the top. I have managed to set the volume buttons as scroll up/down and want the start call button to imitate the start menu button when I long press it. But I want to long press it for as little time as possible. So say 1 second as opposed to 3 seconds.
I see. So, two points:
1. Get quick menu
2. Use a "short" long press
I asked because the green/start left button is assignable in the standard settings - button to the <start menu> but I don't know how to do this to quick menu. I guess if you make a short cut to quick menu and drop this somewhere in the Programs folder in windows (or a sub-folder) then the standard settings - button should find it OK.
But, for option 2 I have no idea. Instead of the "short" long press how about using AEB+ with a double press ?
Dave, I see from the options that you can set the delay. I guess this from the "Key Press timeout" menu where you can select units of time starting with 200ms to 900ms. I am guessing that 200ms of time needed for a long press would be the shortest longpress possible.
Any how, how to assign the green button to start menu? It doesnt work for me. I have it as 2 presses or 3 presses or long press for start menu but nothing happens.
one problem it works to rotate(volume up which i assigned) but as soon as i make a call or recieve a call it no longer works untill i soft reset???? im i missing a setting or something? i have duttys rom, please help! : ) thanks!
The power button on HD is in an inconvenient position and hard to press.
Is it possible to use any other button (like Vol-Down) to power off and on?
I tried AEButton, but it does not seem to have an option to "power-on".
Thanks
Power Off would be possible, however to Power On the device you always need to press the configured power button. This is since AEButton is a software solution and does not alter the hardware settings. Thus making it only run while Windows Mobile is on (by altering the Windows Settings), and since when the device is off WinMo isn't running, so it won't work while the device is off.
sank27 said:
The power button on HD is in an inconvenient position and hard to press.
Is it possible to use any other button (like Vol-Down) to power off and on?
I tried AEButton, but it does not seem to have an option to "power-on".
Thanks
Click to expand...
Click to collapse
It's supposed to be somewhat difficult ...
If you don't already know, virtually ALL power buttons are somewhat hard to press/use. It's supposed to be that way. If they were easier to press, you could easily power off your phone while it's in your pocket by accidentally hitting the volume up or down keys, or any other accidental push.
Peter
KilZone said:
Power Off would be possible, however to Power On the device you always need to press the configured power button. This is since AEButton is a software solution and does not alter the hardware settings. Thus making it only run while Windows Mobile is on (by altering the Windows Settings), and since when the device is off WinMo isn't running, so it won't work while the device is off.
Click to expand...
Click to collapse
I actually meant the state into which the device goes when you press the power button once (Sleep, suspend ... whatever that is called, although this state is sometimes called power-off), and not complete power-off (by holding the power button).
In this Sleep/Suspend, is it not possible to remap the button?
I mean that it is still able to receive calls in this state, so something is running. But not WinMo?
PeterHTC said:
If you don't already know, virtually ALL power buttons are somewhat hard to press/use. It's supposed to be that way. If they were easier to press, you could easily power off your phone while it's in your pocket by accidentally hitting the volume up or down keys, or any other accidental push.
Peter
Click to expand...
Click to collapse
You are right for accidental presses. However that can be taken care by assigning (if possible) a double press instead of single.
Oh, and I am sorry, I did not mean full power off, only sleep/suspend.
For PDAs, such a button placement may be ok, as you anyway have to use both hands to hold the PDA and take out/use the stylus.
But for this phone, single hand use is important. I dont use the stylus most of the time.
.
to power on with up/down control, change DefaultKeyLock to 0 in registry.
ucxoq said:
.
to power on with up/down control, change DefaultKeyLock to 0 in registry.
Click to expand...
Click to collapse
Thanks!! That's almost does it, but for the double press.
I added single press of Vol-Dn in AEB to Today Screen, and double press to a MortScript with PowerOff command.
Now to see if it accidentally comes on in the pouch...
On the latest CAB I downloaded the End button locks the screen and the power button minimizes all the programs. Is there any way to make the Power button lock the screen and the end button minimize all the programs, like it is in Win Mo? I got a T mobile TP2
The problem is that you would end calls with the lock button as well.
I see. There isn't some way they could code around this? That's weird that it's like that.
This note is from the WIKI.
Note: It's until now impossible to split 'End Call' and 'Power' function in the code, so this last function can't be linked to Power button without it being 'End Call' too. Thus for the ease of ending a call, this function is placed on the normal EndCall-button and Power button is 'Home'.
honestly I would find it easier to end calls with the power button anyway. So this seems like a perfectly good compromise to me.
I agree. I'd rather have the power button turn the backlight off than the end button. That's the most important. They should make an option or something where people can choose their preference.
i was coming to look for this. i dont mind having to end calls with the power button right now. ill be using standby and home more so id rather those be more natural.
j.action said:
honestly I would find it easier to end calls with the power button anyway. So this seems like a perfectly good compromise to me.
Click to expand...
Click to collapse
WHAAA???
You guys like ending a phone call using the power button??? Since when has that EVER been natural? (Other than on an Android device, where the power and the end call are the same button...) Ive had 5-6 HTC devices, don't think I ever recall thinking, "we should be using the power button to end a call.". On some HTC devices the power button isn't even very easy to access. Changing end call to the power button would be a disaster.
LOL
Reefermattness said:
WHAAA???
You guys like ending a phone call using the power button??? Since when has that EVER been natural? (Other than on an Android device, where the power and the end call are the same button...) Ive had 5-6 HTC devices, don't think I ever recall thinking, "we should be using the power button to end a call.". On some HTC devices the power button isn't even very easy to access. Changing end call to the power button would be a disaster.
LOL
Click to expand...
Click to collapse
for you. obviously we want it though. i would like the end call button to be on the end call button but i want sleep on the top and home key down below more.
having it end call when youre on a call and a home key button the rest of the time would be more ideal. i kinda wish this was the hd2 because the buttons on that would be make sense in android.
Reefermattness said:
WHAAA???
Click to expand...
Click to collapse
Can't stop the revolution!
Back in WinMo whenever I end a call I hit the big red button on the screen, then hit the power button to put it to sleep so I can put it in my pocket. Needless to say, being able to just double-tap the power button to accomplish the same thing would be great. The front buttons on the TP2 are so dainty it's annoying to press them honestly.
It's such a trivial thing, but I guess everyone's got their own reasons for wanting it. It would be nice to know how to swap the button assignments for myself even if it's not baked into the Rhodium builds directly.
I hit the 'power button' to turn off the screen more often than I hit the end button to 'end calls'. I rarely call. I'm a texter. Power button doing what it should > end button doing what it should.
andershizzle said:
I hit the 'power button' to turn off the screen more often than I hit the end button to 'end calls'. I rarely call. I'm a texter. Power button doing what it should > end button doing what it should.
Click to expand...
Click to collapse
thats my thoughts exactly. i think even people who make calls turn the phone on and off using the power button more than the end key. i understand how one would like it the way it is, which is why a solution to change it for us would be nice.
I agree
j.action said:
Can't stop the revolution!
Back in WinMo whenever I end a call I hit the big red button on the screen, then hit the power button to put it to sleep so I can put it in my pocket. Needless to say, being able to just double-tap the power button to accomplish the same thing would be great. The front buttons on the TP2 are so dainty it's annoying to press them honestly.
It's such a trivial thing, but I guess everyone's got their own reasons for wanting it. It would be nice to know how to swap the button assignments for myself even if it's not baked into the Rhodium builds directly.
Click to expand...
Click to collapse
I agree with you, whenever I try to press the EndCall button, I always fear of dropping the phone from my hand, Or if you hold the phone in your palm; you have twist your thumb all the way down, seems awkward.
I have a question ... wouldn't it be possible to reassign certain actions and not the default button functions to the hardware keys ?
On windows mobile, this seems to be possible with the rhodium keyboard controller ... it uses a modified driver to achieve that iirc ...
If someone could do that for android, we could assign "turn display off" to the power button, "home + end call" to the end key and so on ... or am I wrong ?
Sorry to double post/bump my question ...
But wouldn't it really be possible to just create a driver that is able to assign certain actions to the buttons instead of static button actions?
Or is this impossible under Android?
I would like to know about this me too...
i use the on screen button to end my calls and using the end key to turn backlight off its unnatural for me...
also it will be cool to have the screens template on end key button...
I actually agree with the idea of the power button ending a call - I hold my phone with my index finger on the top ( a habit I developed after having someone yank a phone away from me), so the power button would be very natural for hanging up as I remove the phone from my ear.
An option, or even info on the files to edit, would be awesome. Could it be as simple as a simple .conf file in the filesystem?
Reefermattness said:
WHAAA???
You guys like ending a phone call using the power button??? Since when has that EVER been natural? (Other than on an Android device, where the power and the end call are the same button...) Ive had 5-6 HTC devices, don't think I ever recall thinking, "we should be using the power button to end a call.". On some HTC devices the power button isn't even very easy to access. Changing end call to the power button would be a disaster.
LOL
Click to expand...
Click to collapse
um... it has been (semi) standard on 'dumb phones' for years that the end call button is also the power button.
that being said, i think the best idea is to have some kind of option so people can choose what they prefer. i think you can get used to either way, but it can be really frustrating if you go back and forth between winmo and android to have them be different.
millmanorama said:
um... it has been (semi) standard on 'dumb phones' for years that the end call button is also the power button.
that being said, i think the best idea is to have some kind of option so people can choose what they prefer. i think you can get used to either way, but it can be really frustrating if you go back and forth between winmo and android to have them be different.
Click to expand...
Click to collapse
Yes, on "dumb" phones, and android handsets the power button and the end call button are linked to the same button. The difference is, THESE BUTTONS ARE NOT ON THE TOP OF THE HANDSET. They are on the face of the phone, NEXT TO THE CALL BUTTON.
Like i have said before, switching the end call button to the power button on the Rhodium would be chaos. For the mass majority of users, making the end call button NOT end the call, is ridiculous, and confusing. If you were to go out, and buy an Android handset, you would not even have a power button other than the end call button.
Yes, the only way everyone will be happy, is if you can choose how you want the buttons mapped.
i was thinking not all android devices link the end call and standby buttons together, the nexus one and desire and legend all have them on the top. then when i looked up pictures, they had gotten rid of the send and end call buttons so of course they moved the stand by to the top. i wonder if you press that during a call, would it hand up.
Given that:
1) Power and End are tied together in android so that any button that does one also can do the other. (This is set in Settings-->Accessibility-->Power Button Ends Call).
2) The Power button is now Power/End, and no longer Home as of the Oct. 11 kernel.
3) There is no point in having two buttons that both bring up the power off/airplane mode/mute menu on a long press when no buttons bring up the Recent App List.
4) While it's currently possible to assign Home to End via the Spare Parts Menu, long pressing it still gives us the power off/airplane mode/mute menu instead of the Recent App List because its keycode hasn't changed.
5) During a phone call, while holding the phone one-handed, it's easier to hit the power button to end a call then it is to hit the end button.
I'd thus like to map the End button to Home by default so that long pressing it will bring up the recent app list while leaving power as both power(sleep) and end call. Before I submit a patch to do this, I'd like to poll the community of rhodium XDAndroid users as a whole on this change.
NOTE: I can't seem to edit my poll now that I've put it up. The first option in the poll at the top is the current behavior, the second option is the old behavior, and the third behavior is what I'm proposing.
There's actually a thread over on PPCG that is all about restoring the previous functionality. Power = home, end = power basically.
We talked about making long press end key as recent apps, but that would require changes to the Android base.
Nate seems pretty dedicated to support changes and pump out new kernels accordingly, and it is a pretty simple change if you have the code and don't mind building
arrrghhh said:
There's actually a thread over on PPCG that is all about restoring the previous functionality. Power = home, end = power basically.
We talked about making long press end key as recent apps, but that would require changes to the Android base.
Nate seems pretty dedicated to support changes and pump out new kernels accordingly, and it is a pretty simple change if you have the code and don't mind building
Click to expand...
Click to collapse
I'd prefer that it be part of the official git. Is there a reason why we need to have two buttons that do exactly the same thing in the official build?
in the andriod settings, theres an option to change what the 'end' button does. works fine with me.
pantherzfinest said:
in the andriod settings, theres an option to change what the 'end' button does. works fine with me.
Click to expand...
Click to collapse
That option doesn't fix the long press, only the short press.
arrrghhh said:
There's actually a thread over on PPCG that is all about restoring the previous functionality. Power = home, end = power basically.
We talked about making long press end key as recent apps, but that would require changes to the Android base.
Click to expand...
Click to collapse
Long press as recent apps works fine for me. This isn't a problem if it's done in the navi_pad.kl files for the various rhodiums by setting end to home as the default.
Nate seems pretty dedicated to support changes and pump out new kernels accordingly, and it is a pretty simple change if you have the code and don't mind building
Click to expand...
Click to collapse
Yes, I've already done it, but I dislike the idea of dealing with forks, whether mine or someone else's. Nate's change is also the opposite of what I'm suggesting and requires changes in both the kernel and the rootfs. Mine only requires changes in rootfs. In fact, now that I think about it, it would be pretty easy to set up via a new startup.txt option that init would pull from /proc/cmdline much the way it currently does the keyboard option.
F22 said:
Given that:
1) Power and End are tied together in android so that any button that does one also does the other.
2) The Power button is now Power/End, and no longer Home.
3) There is no point in having two buttons that are both Power and End on a short press when there isn't a Home button.
3) There is no point in having two buttons that both bring up the power off/airplane mode/mute menu when no buttons bring up the Recent App List.
4) While it's currently possible to assign Home to End via the Spare Parts Menu, long pressing it still gives us the power off/ menu instead of the Recent App List.
I'd thus like to map the End button to Home by default so that long pressing it will bring up the recent app list. Before I submit a patch to do this, I'd like to poll the community of rhodium XDAndroid users as a whole on this change.
NOTE: I can't seem to edit my poll now that I've put it up. The first option in the poll at the top is the current behavior, the second option is the old behavior, and the third behavior is what I'm proposing.
Click to expand...
Click to collapse
let me be the first to say DUH!!!
noodles21o2 said:
let me be the first to say DUH!!!
Click to expand...
Click to collapse
LOL, Yup. But in my defense, let me just that I tried to edit it -before- anyone had voted. Another forum that I had dealt with extensively in the past had allowed me to edit a poll as long as nobody had voted. This one doesn't. Once it's up you're stuck with it as is.
rootfs.img
I've made available a rootfs.img for rhodiums that maps the end key to home and returns the recent apps list if you do a long press. If you have the 210 (T-Mobile US TP2), the 300 (AT&T Tilt2), the 400 (Sprint TP2), the 500 (Verizon TP2) or the Nordic version of the 100, then it also has some other keymap/layout additions baked in too like a working SYM key.
This rootfs was built from the XDAndroid rootfs git and is up to date as of the date on the file (currently Nov. 15th).
Instructions
1) Download the file from here.
2) Unzip the file via the 7zip utility
3) Rename it to rootfs.img
4) Drop it into your android boot folder.
5) Restart your phone in Android.
6) Go to to Settings->Accessibility and check the box that says: Power Button Ends Call.
7) Enjoy your new keys.
F22 said:
I've made available a rootfs.img for rhodiums that maps the end key to home and returns the recent apps list if you do a long press. If you have the 210 (T-Mobile US TP2), the 300 (AT&T Tilt2), the 400 (Sprint TP2), the 500 (Verizon TP2) or the Nordic version of the 100, then it also has some other keymap/layout additions baked in too like a working SYM key.
This rootfs was built from the XDAndroid rootfs git and is up to date as of the date on the file (currently Nov. 15th).
Instructions
1) Download the file from here.
2) Unzip the file via the 7zip utility
3) Rename it to rootfs.img
4) Drop it into your android boot folder.
5) Restart your phone.
6) Enjoy your new keys
Click to expand...
Click to collapse
Thanks, but with your changes, the end key no longer ends calls! I had to revert back.
toadlife said:
Thanks, but with your changes, the end key no longer ends calls! I had to revert back.
Click to expand...
Click to collapse
LOL that's a good point. I couldn't figure out how to end the call either... other than hitting menu, then end call. Perhaps we need to get the N1 in-call screen..
Thanks for the Feedback!
toadlife said:
Thanks, but with your changes, the end key no longer ends calls! I had to revert back.
Click to expand...
Click to collapse
The power button was supposed to play double duty, acting as end call with a telephone call, and otherwise act as sleep on a short press. But arrrghhh informs me it isn't working. Thank you for testing this and reporting back. I'll look into it further when I get back later tonight.
End Call Problem Solved
F22 said:
The power button was supposed to play double duty, acting as end call with a telephone call, and otherwise act as sleep on a short press. But arrrghhh informs me it isn't working. Thank you for testing this and reporting back. I'll look into it further when I get back later tonight.
Click to expand...
Click to collapse
I've looked into this and found an incredibly easy solution. Simply click on Settings in your launcher, go to Accessibility, and then check the box that says:
Power Button Ends Call
It's that easy. Once that's done, during a call, pressing power will end the call instead of putting the phone to sleep. Furthermore, I've tested it on my own rhodium and it works. I've updated the instructions in post #9 to include this solution.
I'm running the latest Blazn build and have the end button set up to "home, then sleep" under the Spare Parts.
Long press on the power button brings up recent apps.
bonestock said:
I'm running the latest Blazn build and have the end button set up to "home, then sleep" under the Spare Parts.
Long press on the power button brings up recent apps.
Click to expand...
Click to collapse
Must not be running the newest kernel/rootfs then.
bonestock said:
I'm running the latest Blazn build and have the end button set up to "home, then sleep" under the Spare Parts.
Long press on the power button brings up recent apps.
Click to expand...
Click to collapse
Your kernel is over a month old. That was changed in the kernel on Oct. 11th. The power button no longer behaves as home. It's now sleep on a short press and brings up the power menu (shutdown/airplane mode/mute) on a long press for all newer installations as well as old installations that have updated their kernels.
I think it would be a mistake to make a short press of the end button not end a call. Likewise, but of lesser impact probably, you should be able to press the power button to perform some power related function. These are pretty universal buttons on all phones and if you can't end a call by pressing the end call button, well, I think you are going to have problems with a lot of normal users.
Great work by the way!
mrc13an said:
I think it would be a mistake to make a short press of the end button not end a call. Likewise, but of lesser impact probably, you should be able to press the power button to perform some power related function. These are pretty universal buttons on all phones and if you can't end a call by pressing the end call button, well, I think you are going to have problems with a lot of normal users.
Great work by the way!
Click to expand...
Click to collapse
I think what I'm going to submit is a new command line option for startup.txt that makes button 4 HOME/RecentApps instead of ENDCALL/PhoneOptions. This way people who are happy with the current behavior of the end key can continue to end their calls with it, while those of us who aren't, can add an additional "b4=HOME" argument to the command line and get the behavior that we desire as well.
These buttons are by no means universal. Many phones outside of Windows Mobile lack them, or have them sharing duties. Furthermore the "power-related function" that the power button currently performs within XDAndroid during a call is sleep/lock screen without ending the call, just as it does outside of a call. Is this in any way useful to anyone? Google decided it wasn't and the power button now acts as hangup during a telephone call on newer android phones. This makes a lot of sense given that it's a lot easier to press the power button if you're operating your phone one-handed then the end call key.
F22 said:
These buttons are by no means universal. Many phones outside of Windows Mobile lack them, or have them sharing duties. Furthermore the "power-related function" that the power button currently performs within XDAndroid during a call is sleep/lock screen without ending the call, just as it does outside of a call. Is this in any way useful to anyone? Google decided it wasn't and the power button now acts as hangup during a telephone call on newer android phones. This makes a lot of sense given that it's a lot easier to press the power button if you're operating your phone one-handed then the end call key.
Click to expand...
Click to collapse
Excellent points, I agree completely. As we discussed in IRC, I believe the best option is to have the buttons do what they say they do by default, so people used to WinMo don't have heart attacks.
However, the option of being able to choose which button does what from a startup.txt command is brilliant, and I think a perfect solution to the problem. That way people who know what they're doing and know what they want can change the behavior very easily.
DO EEEEEEEET
mrc13an said:
These are pretty universal buttons on all phones and if you can't end a call by pressing the end call button, well, I think you are going to have problems with a lot of normal users.
Click to expand...
Click to collapse
Not at all. My mom's new LG P500 actually lacks both Call and End Call Buttons. It has four buttons at the front just like TP2, but these are Menu, Home, Back and Search. Power Button acts only as Sleep by default. As far as I can see it's the same story with Desire.
I think that Power Button acting as End Call would be perfectly fine for the most users. Only because we have a button labeled End Call on TP2 doesn't mean that this button must end calls.
Hi all,
I'm trying to figure out if there's a way to lock an app in memory even if I push the back button?
I am locking 2-3 most frequently used apps from the "Recents" menu but that gets washed away when I press the "Back" button after being done with the respective app.
I know the best option would be to start pushing the "Home" button but over the years I developed a habit of pushing the "Back" button several times to go to home or once to close the app and it's very hard to change behavior now.
I'm on NitrogenOS (8.1) if it matters - stock kernel.
Cheers.
DonnyR said:
Hi all,
I'm trying to figure out if there's a way to lock an app in memory even if I push the back button?
I am locking 2-3 most frequently used apps from the "Recents" menu but that gets washed away when I press the "Back" button after being done with the respective app.
I know the best option would be to start pushing the "Home" button but over the years I developed a habit of pushing the "Back" button several times to go to home or once to close the app and it's very hard to change behavior now.
I'm on NitrogenOS (8.1) if it matters - stock kernel.
Cheers.
Click to expand...
Click to collapse
Unless the back button is programmed to kill an app, the app should stay in memory. So check the options for the back button and change it.
It is set to close app. Long press for kill. But still does not work.
If I assign to something else, then basic acknowledge functionality does not work...
DonnyR said:
It is set to close app. Long press for kill. But still does not work.
If I assign to something else, then basic acknowledge functionality does not work...
Click to expand...
Click to collapse
Check the long press duration and if possible lengthen it. Or assign double tap for kill and none for long press as an experiment and check.