[APP] [4.3+] Hold Back To Kill [ROOT]

[elesbb]

Here is an app that allows you to hold your back button to kill the currently open application.

If popularity is high enough, I will update it with things like whitelist etc.

If you use a Samsung device, the only problem is that you can't show the MultiWindow bar anymore. I will work on a fix for it. I only made this because xposed doesn't work on Samsung Lollipop yet so this is what I wanted until it is. Once it works, I prolly won't ever touch this app again.

Thanks everyone!

UPDATE:

- Performance improvement

 

[Droidphilev]

useful, thanks for this!!!!

 

[onestoploser]

Great job! I've been missing this feature since I switched to Lollipop. Thanks!

 

[Droidphilev]

hi,

It seems to be working on CM12 but a little too good

Apps get killed right away when i press "back"whatever time-out i set in the settings.

 

[elesbb]

hi,

It seems to be working on CM12 but a little too good

Apps get killed right away when i press "back"whatever time-out i set in the settings.

I dont know i dont have cm12. i know cm12 has a default native option to hold back to kill maybe that is enabled?

 

[Droidphilev]

I dont know i dont have cm12. i know cm12 has a default native option to hold back to kill maybe that is enabled?

Hello, CM12 with standard navbar (3 buttons) doesn't have that setting. It s only implmented in roms with navbars with extra settings like opening an app etc etc

 

[ndg1988]

Having Trouble

I'm having a similar problem where even a single tap on the back button is closing the app. I have a rooted Galaxy S4 running Android 4.4

 

[elesbb]

Hello, CM12 with standard navbar (3 buttons) doesn't have that setting. It s only implmented in roms with navbars with extra settings like opening an app etc etc

I'm having a similar problem where even a single tap on the back button is closing the app. I have a rooted Galaxy S4 running Android 4.4

So this is happening when using the navbar and not the physical buttons?

It seems like the up action isn't being triggered. I could try to implement maybe a double click back to kill option. Ill try to debug on my 5.0 emulator that uses the navbar and see if i can figure anything out. Weird how that's happening.

 

[Droidphilev]

So this is happening when using the navbar and not the physical buttons?

It seems like the up action isn't being triggered. I could try to implement maybe a double click back to kill option. Ill try to debug on my 5.0 emulator that uses the navbar and see if i can figure anything out. Weird how that's happening.

hello again,

No, i dont use the navbar In cm12 (disabled) I use hardware buttons. If ndg1988 uses stock then he doesn't have a navbar so i guess he uses the hardware buttons too

 

[elesbb]

hello again,

No, i dont use the navbar In cm12 (disabled) I use hardware buttons. If ndg1988 uses stock then he doesn't have a navbar so i guess he uses the hardware buttons too

Hm, I truly don't know then. I really would need the device in hand to test with. I could try to do testing by sending you a file with loads of debug information in it. Would you mind that?

 

[ndg1988]

Good News

So this is happening when using the navbar and not the physical buttons?

It seems like the up action isn't being triggered. I could try to implement maybe a double click back to kill option. Ill try to debug on my 5.0 emulator that uses the navbar and see if i can figure anything out. Weird how that's happening.

I was just an idiot that assumed the activation time was in units of seconds, not milliseconds. This may be what most people are having trouble with. It works well now, so thank you and keep up the good work.

 

[elesbb]

I was just an idiot that assumed the activation time was in units of seconds, not milliseconds. This may be what most people are having trouble with. It works well now, so thank you and keep up the good work.

Haha okay good. Nice one It does say "milliseconds"

 

[Droidphilev]

Hm, I truly don't know then. I really would need the device in hand to test with. I could try to do testing by sending you a file with loads of debug information in it. Would you mind that?

no, but it will take a while. i need to test multirom on my device and i have have to finish the translation of an app first.

 

[phuphat1986]

Thanks mate

 

[leechseed]

Awesome - best thing that can happen to a rooted stock rom.

btw its labled "Main Activity" in App Drawer, not "Hold Back To Kill"

 

[elesbb]

no, but it will take a while. i need to test multirom on my device and i have have to finish the translation of an app first.

What delay are you setting for it in the settings?

Awesome - best thing that can happen to a rooted stock rom.

btw its labled "Main Activity" in App Drawer, not "Hold Back To Kill"

Yup. Realized that after releasing and didn't care too much about it. In the next update (if ever one would exist) i'll fix it.

 

[Droidphilev]

What delay are you setting for it in the settings?

I have tried 2, 3, 4 and 5 seconds

 

[leechseed]

Did you put in 2 or 2000? (check post #11)

 

[Droidphilev]

Did you put in 2 or 2000? (check post #11)

DAMNED!!!!!!!!!!!!!!!!!!!!!!!!!!

Thank you, leechseed! Was making the same mistake.

OP please forget all my postings. Working very well!!!

 

[elesbb]

Did you put in 2 or 2000? (check post #11)

I have tried 2, 3, 4 and 5 seconds

DAMNED!!!!!!!!!!!!!!!!!!!!!!!!!!

Thank you, leechseed! Was making the same mistake.

OP please forget all my postings. Working very well!!!

That is why I asked. I have it set to milliseconds because I have mine set to a value of 200 milliseconds

Love seeing everyone helping everyone. Thanks guys!!!