How to close apps?

Mudita Products
21

Thank you for the detailed answer. I’m glad the bug has been found, I hope this can be fixed for the next update.

The vision/display settings I am able to access through Activity Launcher. There is no issue with that. The issue is specifically the bug has broken the accessibility permission.

You open the app → the feature that you need sends an intent to the system to use the accessibility permission (for example to lock the screen) → dialog pops up that asks user do u want to give permission to this app → users accepts or declines it.

In current 1.2.0 the dialog doesn’t show at all, it just redirects the user to the “accessibility settings” which is really completely different thing.

So this is the thing we’re asking to be fixed.

The thing is that permission was available in v1.1.1. So I don’t believe it’s an issue of causing instabilities at all. Simply it was a bug that was missed during testing.

It is obvious from the other hidden settings that haven’t been re-skined for MuditaOS-K UI. They haven’t been hidden because they’re useless, they’ve been hidden because Android has tons of features and it takes a long time to re-skin all of them and I know that your team is small and doesn’t have the resources to do all of this quickly.

It would be nice for these to be put under a menu “extras” instead of hiding them. They’re still useful even if they are not with the pretty UI. We’re not looking at them everyday, but the idea is you edit a setting and you forget it. But when that setting dialog window has been hidden, it’s annoying.

And yes we do appreciate that Mudita has gone through the trouble of optimizing the settings to work with E-ink displays and scrolling has been changed to be paginated, but the approach of hiding features have caused issues like notifications (even system ones like alarm and messages) to keep vibrating when the phone is silenced and vibrations are off. Or the dialog for selecting the network manually and many others.

The point I’m trying to make is that we do understand the philosophy of the minimal design, minimal software. But Android has many QOL features that make the device easier and faster to use with shortcuts/automation. What’s more minimal that spending even less time on my phone :smiley: ?

And the scenarios I mentioned are just basic ways on how people use the accessibility permission, it is mostly used from people that suffer from mobility or vision disabilities because with it you can use magnifiers, talk-back, and automate things. For example to turn of mobile data it takes 5-6 buttons taps to disable it. With keymapper I can make a shortcut that does it 1 step. (I know i can turn it off with the offline switch, but I’m talking about scenarios that I only want to turn off mobile data and not wifi/bt etc).

Hope this helps to clarify the situation.

Thanks!

4 Likes
22

Any updates on the kill apps feature? Is the current workaround only to install another app?

2 Likes
23

Accessibility service permission is still broke for me on 1.3.0

1 Like
26

@urszula any update?

2 Likes
27

@michalplaza Unfortunately, there has not been a decision yet.

28

@urszula it’s my turn to ask: any updates? I feel like there is a major power saving issue, since some apps are rapidly draining the battery. It’s really annoying to go in the management menu and check every app to see if it’s still running, then force it to close.

1 Like
29

In the meantime KillApps has been updated several times, and it comfortably lists all the running apps.

https://apkpure.com/killapps-close-all-apps/com.tafayor.killall

3 Likes
30

I recommend installing it from the Aurora Store, so it auto-updates. Version numbers are up to par.

https://auroraoss.com/

Kind regards,

Marco

2 Likes
31

Does the issue with accessibility permissions still prevent apps form being closed as Gezimos described earlier in this thread?

1 Like
32

No, this has been fixed with the OS update 1.4.0. So KillApps can now be used without problems.

1 Like
33

Can confirm, but I can only kill user apps on my unrooted Kompakt. Is that the same for you, @YYZ (as I have downloaded it from the Aurora store)?

1 Like
34

I have never tried to kill system apps, because it’s like Russian roulette. But assuming from what you wrote, it doesn’t work ?

1 Like
35

No, indeed. Only user apps are listed, just checked. I was mistaken when I said it was because the device rooted isn’t, the reason I can’t select system is because I’m using the free version and killing system apps is only available in the paid version (which, to the best of my knowledge, isn’t possible using an spoofed session in Aurora). BTW, on opening KillAll a popup showed up, advising me to download Baxa as successor to KillAll? Have you come across that as well?

1 Like
36

@YYZ

Baxa seems all but E-ink friendly, so I’ll stick with KillAll and killing user apps should indeed be the safer way to free up some memory.

1 Like
37

Not yet, but I know that Baxa is made by the same team.

There are several apps that were free in previous versions, but now they must be purchased although they have some disadvantages.

1 Like
38

Kill app has some questionable permission requests. view and control screen - read all content, and display all content over other apps. or am I missunderstanding the context

2 Likes
39

That’s the workaround that KillAllApps uses to stop the apps. It doesn’t work as a “clear” button in Android Recents.
Android doesn’t allow third-party apps to stop/clear apps from memory. So what KillAllApps does:

  • Goes to every app
  • Longpress on them
  • Taps on App info
  • Taps on Stop app

That’s why it takes so long for all apps. You just don’t see what it’s doing, but that’s what happens on the background.

3 Likes
40

interesting, thank you for the expaination

2 Likes
41

Not yet- we are in the process of updating the roadmap, so stay tuned.

2 Likes