Anyone knows how to remap hardware keys. I have tried gravity box and xposed additions, but both don't work on oos 2.2.0. The standard button option in oos settings doesn't have much options. I want to enable long press back kills foreground applicant.
"Recent apps" then cross to "kill all" isn't enought for you?
Kéno40 said:
"Recent apps" then cross to "kill all" isn't enought for you?
Click to expand...
Click to collapse
"Kill all" & "enough" you see the contradiction. I don't have to explain you that, in the way android works, it isn't good to kill all apps.
I just want to kill foreground application. Besides also want to remap the other keys with functions that aren't native oos supported (like notifications pull down).
winesh said:
"Kill all" & "enough" you see the contradiction. I don't have to explain you that, in the way android works, it isn't good to kill all apps.
I just want to kill foreground application. Besides also want to remap the other keys with functions that aren't native oos supported (like notifications pull down).
Click to expand...
Click to collapse
On news android devices and quite powerfull ones, it's more "quit all" than "kill all". It seems really less agressive than before and I don't have any remorses using it.
Edit : maybe I'm wrong !
Kéno40 said:
On news android devices and quite powerfull ones, it's more "quit all" than "kill all". It seems really less agressive than before and I don't have any remorses using it.
Edit : maybe I'm wrong !
Click to expand...
Click to collapse
Haha you are terribly wrong. The power of new android devices has nothing to do with this.
The only thing that has been advanced over the years in terms of ram, is that app developers generally coded their apps better. Meaning sleep, stand by and closing without user interuption is done more efficiently.
Related
...and I don't mean 'minmize' like what pressing the home or back button does. (which merely puts it in the multitasker menu list, still open.)
I mean closing it like when you swipe it out of the menu list. (which are far as I can tell, seems to close it off enough to stop what it's doing and free up the memory it was using!)
Sometimes I want to just close an app since I know I won't be using it for a while and I want to conserve cpu/memory/battery - or merely manage the list of things in my multitask list. kinda like on Desktop. (you don't want every app on your pc open all at once, do you, do you?!) and I just want a simple way like on the desktop to close that app when I want to close it.
SO: Is there some app that can assign a custom screen gesture (like the lovely letter C for 'close') to perform 'fully exit current app' or some solution like that? I started to research, but couldn't seem to find one very quickly, so thought I'd ask here, at THE place to ask.
also I apologise for using things like Windows terms ('minimize'), i know that's not how it works in android. But you do know what I mean.
Thanks
This is a question that a lot of people ask when moving to Android and the answer simply is, forget about it.
Android handles processes and memory in a completely different way to Windows. When an app is "minimized" it obviously leaves a footprint in the memory, but it uses no CPU (unless it's a polling app or something that keeps alive for a specific purpose).
Just trust Android to handle memory management - it does a very good job of it.
If you really, really MUST do something about it then the best thing you can do is get something like Juice Defender (there's tons of similar apps) and make it kill apps periodically. Most apps that people use for this type of purpose are merely placebo, but if it makes you feel better then I guess it's serving a purpose.
Archer said:
This is a question that a lot of people ask when moving to Android and the answer simply is, forget about it.
Android handles processes and memory in a completely different way to Windows. When an app is "minimized" it obviously leaves a footprint in the memory, but it uses no CPU (unless it's a polling app or something that keeps alive for a specific purpose).
Just trust Android to handle memory management - it does a very good job of it.
If you really, really MUST do something about it then the best thing you can do is get something like Juice Defender (there's tons of similar apps) and make it kill apps periodically.
Click to expand...
Click to collapse
Thanks for your answer. I can sense you have wisdom and experience in your words there, but I want to probe a little further.
surely there can be an almost macro-like (again, windows terminology, sorry) functionality, that can be assigned to a gesture swipe that can emulate pressing home button, then swiping the bottom item away from the multitask menu? (which is always the one you just 'minimized')? Could an app like Tasker even do it?
i agree that good memory management is a beautiful thing, but there really should be manual control of closing apps, my reasons above are stated.
i wouldn't touch automatic time-based closing, i sometimes have saved states in apps and wouldn't want them closed when i don't want them closed.
Most apps that people use for this type of purpose are merely placebo, but if it makes you feel better then I guess it's serving a purpose.
Click to expand...
Click to collapse
you really think it's all placebo, and that say, running 50 apps in android with finite set amount of ram on the device is all fine simply due to memory management?
is me experiencing lag in some android apps (or battery draining faster than I'd like), then closing off several running apps in the multitask list, then noticing the problem go away, all placebo????? what about google maps, say?! I'd love a one-step swipe action to CLOSE google maps when I'm done with it, not having to press home button, then multitask button, then swipe away google maps. (I know when minimized it consumes nothing like it does when open, but I think still it consumes more than if it were fully closed...)
it's not just about memory. edit: and I already stated in addition, I often want to simply manage what I have open. this is a basic function in desktop OSes, I think it's time it came to mobile. if not officially, there surely must be some hack/tool to do it. :S
download a task killer app with a widget.
press home button and press the widget and you're done
If you're using AOKP based ROM then there is hold back to kill in Settings > ROM control > general UI
Sent from my GT-I9100 using 1st ROM
Hold homesçern key
Sent from my ST23i using xda app-developers app
jman2131 said:
download a task killer app with a widget.
press home button and press the widget and you're done
Click to expand...
Click to collapse
that's about 2/3 the way towards the current 3-step solution though :/.
Am I to be amazed that a function to put this simple task into a single gesture hasn't been done? or isn't possible? it HAS to be possible. Otherwise I'd be flabbergasted.
I have googled further and just can't seem to find something :|.
WAIT! I think I have! here. https://play.google.com/store/apps/details?id=com.goodmooddroid.gesturecontroldemo&hl=en it has a "kill task" function that you can set up a custom gesture for. it's a start.
however I'm getting a "ERROR! No ROOT permissions?" error despite being rooted with supersu and successfully using other root apps etc, so I've emailed the dev and hope I can get it working :S.
But still, it seems a little clunky the offering of custom gesture types. I can't set a nice curvy gesture defined by tracing it on the screen. oh well - it's a start.....
jootanen said:
If you're using AOKP based ROM then there is hold back to kill in Settings > ROM control > general UI
Click to expand...
Click to collapse
That seems the holy grail! too bad I'm on stock jb with plans for upgrading to CM .....
Hello everyone! I just got a brand new Galaxy Note 4 (Exynos) coming from a Galaxy S4. The "new' left softkey now triggers the Recents app instead of being a Menu (Options) key and that makes me sad. I'm not much of a multi-tasker, I'm not going to use it often, but I do like using the Options key in Chrome, picture galleries and basically everywhere since it's easier for me to reach it. I know most apps now have the "three dots" menu, but it's usually very high on the screen (hard to reach on a Note 4) and it's also non-intuitive. One can just press the left soft key with eyes closed, while you need to precisely see where you click if using app's "three dots". So I discovered that if I "hold" the left soft key, it would actually bring the Options menu, but I would like to swap the behavior. One press = Options, Hold = Recent.
I'm on a stock Kitkat 4.4.4 now, running ART, fully rooted. Can someone post(make) a CWM/TWRP .zip to address this problem?
PS: I tried to search for such feature here on the Themes and Apps section, but couldn't find a solution.
Thanks!
Look here: http://forum.xda-developers.com/showthread.php?t=2646304 and here: http://forum.xda-developers.com/showthread.php?t=2337229 I think that the logic is the same, look if there are similarities.
Yay, thanks! Indeed in "/system/usr/keylayout" there was a file called "Generic.kl" and inside of it #254 was called "APP_SWITCH". I changed that to "MENU", restarted and... the button now acts like a Menu key, just like on my old Galaxy S4. For some reason the "hold" function of this key changed to "S Finder" (a search app) and I would like to make it "APP_SWITCH" in order to fully accomplish my goal of swapping those two functions, but still I think now it's a little bit better since I really care more for the Option key, especially on this big screen where reaching the "three dots" menu in upper right corner is not that easy.
Remap buttons with "xposed additions"
Obviously, you need xposed installed.
ctrlaltdeln said:
Remap buttons with "xposed additions"
Obviously, you need xposed installed.
Click to expand...
Click to collapse
Yeah, I've heard somewhere about that, but I don't like Xposed to be honest. I don't live running lots of background processes and Xposed is a whole fremework.
ZeroCGTI said:
Yeah, I've heard somewhere about that, but I don't like Xposed to be honest. I don't live running lots of background processes and Xposed is a whole fremework.
Click to expand...
Click to collapse
It's not as bad as one would think.
Alot of them you could greenify(greenify can function as a xposed module or a stand-alone app), like Wanam.
Also, modules like greenify and boot manager would save you resources and would probably even-out with the resource demands of the framework.
IMO, Xposed is an absolute must-have for a device that's efficient, customized, and blazing fast.
Maybe. Still last time I checked it wasn't available for Samsung TouchWiz based ROMs on Lollipop. And I'm considering the opportunity to step up to the Lollipop upgrade finally and it won't be compatible anyway. I mean I surely can install it now, but I don't like the idea of getting used to it since I won't be able to use it once I upgrade to LP.
I think that you must change menu to app_switch
I'm using Greenify on 4.4. Some apps like Viber or keyboard are not hibernating automatically. We can force them to, with this zzz button in which case they hibernate all the time.
I find it would be the most useful not to use zzz but to have another "Force hibernation shortcut" that would instantly hibernate all listed apps, still allowing those existing 2 shortcuts which don't hibernate all.
I hope this concept is not wrong and that it can be done. If it is, please advise how to use it.
O
TimAnd said:
I'm using Greenify on 4.4. Some apps like Viber or keyboard are not hibernating automatically. We can force them to, with this zzz button in which case they hibernate all the time.
I find it would be the most useful not to use zzz but to have another "Force hibernation shortcut" that would instantly hibernate all listed apps, still allowing those existing 2 shortcuts which don't hibernate all.
I hope this concept is not wrong and that it can be done. If it is, please advise how to use it.
Click to expand...
Click to collapse
Thats an very interesting concept,and totally possible,this used to be present on older versions of greenify but it was removed because it closed apps when they were doing something important. also,Why are you hibernating your keyboard?
danx32 said:
Why are you hibernating your keyboard?
Click to expand...
Click to collapse
I'm hibernating keyboard just because it consumes power. That's so with SwiftKey and TouchPal which are great with swype/slide functions.
Built-in keyboard in 4.4 doesn't but I don't use it. Huawei phone has this power consumption warning and those 2 are regularly on the list.
TimAnd said:
I'm hibernating keyboard just because it consumes power. That's so with SwiftKey and TouchPal which are great with swype/slide functions.
Built-in keyboard in 4.4 doesn't but I don't use it. Huawei phone has this power consumption warning and those 2 are regularly on the list.
Click to expand...
Click to collapse
Swiftkey never been battery friendly,Unfortunately Currently The only solution is to use that ZZZ button until the developer fixes that,But that's gonna take awhile since he is currently focusing on Android N support.
I feel like this should be do-able in MacroDroid using a widget button and the Send Intent action... I have never tried using that particular action though, and seems I need to get a dump of the intents and look for the right one hehe, sounds like a sober job
Some info on Intent for Tasker.. not familiar with that app but assume is similar to MacroDroid...
Button Mapper on the Play Store:
https://play.google.com/store/apps/details?id=flar2.homebutton&hl=en
If your device is rooted, you have complete ability to remap the Bixby Button. You can disable the Bixby assistant, it does not need to be enabled for this to work. There are no compromises with this method. You can get rid of Bixby and program whatever single, double and long press actions you want.
If your device is not rooted, you can still remap Bixby using an experimental method. This method also works with Bixby disabled, and will allow you to map whatever actions you like to a single press or long press. It requires running a command in adb shell once. After this, the Bixby button can be remapped with Button Mapper. A slight inconvenience, but it works.
If you don't like the stuttering that occurs on Samsung devices with certain Accessibility features enabled, got to Advanced Options and select "Remap Bixby only"
Are you using the Accessibility framework to detect keypresses? If so, that does impact scrolling performance. I also am working on a keymapper for BIxby that doesn't use the Accessibility Framework, and it works very well. If you're not using Accessibility, and you don't have any performance impact, I'd be happy to test this out and provide feedback (and probably stop my work)
EDIT: Yep, looks like Accessibility is used here, which kills scrolling performance (lots of stutters) when you listen for keypresses. I shall continue my work.
Kev1000000 said:
Are you using the Accessibility framework to detect keypresses? If so, that does impact scrolling performance. I also am working on a keymapper for BIxby that doesn't use the Accessibility Framework, and it works very well. If you're not using Accessibility, and you don't have any performance impact, I'd be happy to test this out and provide feedback (and probably stop my work)
EDIT: Yep, looks like Accessibility is used here, which kills scrolling performance (lots of stutters) when you listen for keypresses. I shall continue my work.
Click to expand...
Click to collapse
I could do it without accessibility. I'm just piggybacking on accessibility service since the rest of the app uses it.
I wish Samsung would fix that stuttering. It's not even when you listen for key presses, even an empty accessibility service causes that stutter. OnePlus used to have the same issue and they fixed it with a system update.
That's actually not quite true in my testing. The config that causes the slowdown is...
android:canRequestFilterKeyEvents="true"
If you have that enabled, regardless of anything else, it causes stuttering. Setting that to false causes the stuttering to disappear.
Kev1000000 said:
That's actually not quite true in my testing. The config that causes the slowdown is...
android:canRequestFilterKeyEvents="true"
If you have that enabled, regardless of anything else, it causes stuttering. Setting that to false causes the stuttering to disappear.
Click to expand...
Click to collapse
I haven't checked on the latest update, but any accessibility service caused it when I last tested. It was not specific to any setting.
On AQF7 with that flag disabled, all scrolling returns to normal.
does the button remap work when in lockscreen ?
update: Yup, it stutters. even stuttering in Button Mapper setting page.
The stuttering with Accessibility has been there all along. It's not just with the key filter turned on (I am also on AQF7), it's there with bxActions and other accessibility-based apps I've tried that don't filter keys. But you are correct it's not every Accessibility Service. I have an Accessibility service on another app (DevCheck) that does not cause stuttering.
In the end, there's nothing I can do about that stuttering, it will probably be fixed if Samsung updates to Android 7.1.
I would like to focus on the remapping part and how it works. I can make a Bixby remap that doesn't need accessibility, but first I need feedback on how the remap stuff is working. I can't root my S8, so I'm doing this partially blind and I depend on others to test things. The non-root part works perfectly, but is not easy to set up, so I want to see what kinds of problems people run into and fix them before I push this out of beta.
Kev1000000 said:
Are you using the Accessibility framework to detect keypresses? If so, that does impact scrolling performance. I also am working on a keymapper for BIxby that doesn't use the Accessibility Framework, and it works very well. If you're not using Accessibility, and you don't have any performance impact, I'd be happy to test this out and provide feedback (and probably stop my work)
EDIT: Yep, looks like Accessibility is used here, which kills scrolling performance (lots of stutters) when you listen for keypresses. I shall continue my work.
Click to expand...
Click to collapse
Does your method need root?
flar2 said:
Does your method need root?
Click to expand...
Click to collapse
It does, yes. I would prefer your method if you could remove the need for accessibility, for sure.
I tested out as much as I could with your solution. Overall, things seem to work. Single, double, and long press all work. However, it doesn't reliably stay working. After screen off, or launching the camera, etc, it seems to stop working. If I relaunch Button Mapper, it works again.
@OP
Thanks for this.
I signed up so that you can do your work,
but hoping once your testing finished, you'd
remove the "Accessibility"!
samteeee said:
@OP
Thanks for this.
I signed up so that you can do your work,
but hoping once your testing finished, you'd
remove the "Accessibility"!
Click to expand...
Click to collapse
Yes, I'll probably just make a separate app, since everything else in Button Mapper is tied to Accessibility.
That'll be next week though, I'm out of town until next Wednesday.
Kev1000000 said:
It does, yes. I would prefer your method if you could remove the need for accessibility, for sure.
I tested out as much as I could with your solution. Overall, things seem to work. Single, double, and long press all work. However, it doesn't reliably stay working. After screen off, or launching the camera, etc, it seems to stop working. If I relaunch Button Mapper, it works again.
Click to expand...
Click to collapse
Relaunch, as in just opening the app, or do you have to go to the Bixby screen and tap the switch to turn it back on?
Do you have the "Screen off actions" setting enabled or disabled? It's on the Advanced Options screen.
flar2 said:
Yes, I'll probably just make a separate app, since everything else in Button Mapper is tied to Accessibility.
That'll be next week though, I'm out of town until next Wednesday.
Click to expand...
Click to collapse
That'll be awesome, Look forward to beta testing it!
flar2 said:
Relaunch, as in just opening the app, or do you have to go to the Bixby screen and tap the switch to turn it back on?
Do you have the "Screen off actions" setting enabled or disabled? It's on the Advanced Options screen.
Click to expand...
Click to collapse
Just opening the app, and more specifically, a warm launch of the app (the process was still live and not removed from memory).
I didn't adjust the screen off actions, so whatever your defaults are there was what I had set.
Thanks guys, this is the only button mapper which I could use without root, Bixby disabled.
I just pushed version 0.44, with some minor bug fixes and a new option to have smoother scrolling.
This new option can be toggled in Advanced Options->Experimental Options->Remap Bixby only. With this option enabled, you can remap Bixby without suffering from choppy scrolling. However, you will no longer be able to remap the volume buttons (because they require the Accessibility Service settings that cause choppy scrolling on Samsung phones).
Thanks, flar! Working well. Scrolling performance has returned to smooth.
One of the last issues I have is the "open recents" option is fairly slow to execute. I find using Accessibility Service that doesn't capture key events still maintains scrolling performance, but allows super quick "open recents" using Accessibility to call it.
Hmm, with this enabled, my battery life has significantly dropped and the phone is warm to the touch. Have you noticed any increase in battery life with this method? This may have existed before, I just didn't test it long enough to notice.
Hi everybody.
I ask how "Lock" an app in the recent apps.
So when you use "Erase All" option to clean the RAM this application does not close.
I can do this with android 7, but i dont find this option now.
I don't believe that "app locking" was ever a feature of clean Android. It is a must have feature for crippled systems with aggressive memory management like MIUI, but systems based on AOSP don't need it. To be honest I'm surprised that the button "clear all" is still present. For what purpose do you use it?
They clearly don't want you to use it any more which is any they moved it all the way to the left. It's placebo at this point. Best to leave it to the system.