github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-07 11:29:37 -05:00
Code Issues 1.1k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #596] Accessibility service: this service is malfunctioning #6848

New Issue
Closed
opened 2026-04-10 23:11:54 -05:00 by GiteaMirror · 45 comments
GiteaMirror commented 2026-04-10 23:11:54 -05:00
Owner
Copy Link

Originally created by @actuallymentor on GitHub (Sep 5, 2019).
Original GitHub issue: https://github.com/bitwarden/android/issues/596

My accessibility service (android 9) keeps breaking. When I go to the enable screen android notifies me that this service is malfunctioning.

Let me know if I can supply any useful debug data.

Originally created by @actuallymentor on GitHub (Sep 5, 2019). Original GitHub issue: https://github.com/bitwarden/android/issues/596 My accessibility service (android 9) keeps breaking. When I go to the `enable` screen android notifies me that `this service is malfunctioning`. Let me know if I can supply any useful debug data.
GiteaMirror commented 2026-04-10 23:11:56 -05:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Sep 5, 2019):

What type of device?

<!-- gh-comment-id:528570460 --> @kspearrin commented on GitHub (Sep 5, 2019): What type of device?
GiteaMirror commented 2026-04-10 23:11:57 -05:00
Author
Owner
Copy Link

@actuallymentor commented on GitHub (Sep 6, 2019):

Oneplus 3, Android 9 (stock).

<!-- gh-comment-id:528745711 --> @actuallymentor commented on GitHub (Sep 6, 2019): Oneplus 3, Android 9 (stock).
GiteaMirror commented 2026-04-10 23:11:57 -05:00
Author
Owner
Copy Link

@htfy96 commented on GitHub (Sep 14, 2019):

Also appears on my Zenfone 6 with stock Android 9. There's no icon at status bar in the presence of password box. Reabling Bitwarden in accessibility can fix this problem for a while, but the problem reappears after several minutes.

<!-- gh-comment-id:531514819 --> @htfy96 commented on GitHub (Sep 14, 2019): Also appears on my Zenfone 6 with stock Android 9. There's no icon at status bar in the presence of password box. Reabling Bitwarden in accessibility can fix this problem for a while, but the problem reappears after several minutes.
GiteaMirror commented 2026-04-10 23:11:59 -05:00
Author
Owner
Copy Link

@actuallymentor commented on GitHub (Sep 15, 2019):

Reabling Bitwarden in accessibility can fix this problem for a while, but the problem reappears after several minutes.

Confirming that this is the same for me. I can re-enable but after a time (unpredictable) it breaks again.

<!-- gh-comment-id:531552585 --> @actuallymentor commented on GitHub (Sep 15, 2019): > Reabling Bitwarden in accessibility can fix this problem for a while, but the problem reappears after several minutes. Confirming that this is the same for me. I can re-enable but after a time (unpredictable) it breaks again.
GiteaMirror commented 2026-04-10 23:12:00 -05:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 10, 2019):

@actuallymentor if you're using a OnePlus device go into the battery settings, battery optimisation, click on the three dots in the top right, click advanced optimisation then disable deep optimisation. This seems to have fixed this issue for me.

<!-- gh-comment-id:540490712 --> @ghost commented on GitHub (Oct 10, 2019): @actuallymentor if you're using a OnePlus device go into the battery settings, battery optimisation, click on the three dots in the top right, click advanced optimisation then disable deep optimisation. This seems to have fixed this issue for me.
GiteaMirror commented 2026-04-10 23:12:02 -05:00
Author
Owner
Copy Link

@actuallymentor commented on GitHub (Oct 10, 2019):

@vargbeaumont thanks for the tip!

if you're using a OnePlus

I am.

disable deep optimisation

Did it just now and will post back if it ends up breaking.

<!-- gh-comment-id:540759327 --> @actuallymentor commented on GitHub (Oct 10, 2019): @vargbeaumont thanks for the tip! > if you're using a OnePlus I am. > disable deep optimisation Did it just now and will post back if it ends up breaking.
GiteaMirror commented 2026-04-10 23:12:03 -05:00
Author
Owner
Copy Link

@idavydov commented on GitHub (Oct 25, 2019):

I have the same problem. I tried to keep deep optimization, but select "don't optimize" next to bitwarden optimization settings (settings -> battery -> battery optimisation). Will report back if I still encounter the problem.

<!-- gh-comment-id:546363595 --> @idavydov commented on GitHub (Oct 25, 2019): I have the same problem. I tried to keep deep optimization, but select "don't optimize" next to bitwarden optimization settings (settings -> battery -> battery optimisation). Will report back if I still encounter the problem.
GiteaMirror commented 2026-04-10 23:12:04 -05:00
Author
Owner
Copy Link

@actuallymentor commented on GitHub (Oct 28, 2019):

Did it just now and will post back if it ends up breaking.

Confirming that even unoptimised it keeps crashing.

No other accessibility services have this issue currently.

<!-- gh-comment-id:546936865 --> @actuallymentor commented on GitHub (Oct 28, 2019): > Did it just now and will post back if it ends up breaking. Confirming that even unoptimised it keeps crashing. No other accessibility services have this issue currently.
GiteaMirror commented 2026-04-10 23:12:04 -05:00
Author
Owner
Copy Link

@SOLR4189 commented on GitHub (Nov 5, 2019):

Did somebody find a solution for this problem? I have the same problem

<!-- gh-comment-id:549924304 --> @SOLR4189 commented on GitHub (Nov 5, 2019): Did somebody find a solution for this problem? I have the same problem
GiteaMirror commented 2026-04-10 23:12:05 -05:00
Author
Owner
Copy Link

@Web-E commented on GitHub (Dec 18, 2019):

Same issue here as well, OnePlus 3 (android 9) + battery optimization turned off

<!-- gh-comment-id:567079286 --> @Web-E commented on GitHub (Dec 18, 2019): Same issue here as well, OnePlus 3 (android 9) + battery optimization turned off
GiteaMirror commented 2026-04-10 23:12:05 -05:00
Author
Owner
Copy Link

@AtjonTV commented on GitHub (Feb 22, 2020):

Same issue on HUAWEI P smart Z (STK-LX1) with EMUI 9.1 (Android 9).

<!-- gh-comment-id:589932036 --> @AtjonTV commented on GitHub (Feb 22, 2020): Same issue on HUAWEI P smart Z (STK-LX1) with EMUI 9.1 (Android 9).
GiteaMirror commented 2026-04-10 23:12:06 -05:00
Author
Owner
Copy Link

@onfire4g05 commented on GitHub (Jul 31, 2020):

Also can confirm this is happening on my Google Pixel 3 XL on the 11 Beta.

<!-- gh-comment-id:666899771 --> @onfire4g05 commented on GitHub (Jul 31, 2020): Also can confirm this is happening on my Google Pixel 3 XL on the 11 Beta.
GiteaMirror commented 2026-04-10 23:12:06 -05:00
Author
Owner
Copy Link

@MikeBishop commented on GitHub (Feb 17, 2021):

OnePlus 8 running Android 11 checking in, same issue.

<!-- gh-comment-id:780684162 --> @MikeBishop commented on GitHub (Feb 17, 2021): OnePlus 8 running Android 11 checking in, same issue.
GiteaMirror commented 2026-04-10 23:12:07 -05:00
Author
Owner
Copy Link

@quamok commented on GitHub (Apr 4, 2021):

Pixel 4 xl, android 11, same issue here also.

<!-- gh-comment-id:812949632 --> @quamok commented on GitHub (Apr 4, 2021): Pixel 4 xl, android 11, same issue here also.
GiteaMirror commented 2026-04-10 23:12:07 -05:00
Author
Owner
Copy Link

@Ankurjain30 commented on GitHub (May 16, 2021):

Hi Guys
I also starting developing one Accessibility service and just trying to get kind of event and getting service is malfunctioning on oneplus 8T. Did u able to resolve the issue somehow.

<!-- gh-comment-id:841799327 --> @Ankurjain30 commented on GitHub (May 16, 2021): Hi Guys I also starting developing one Accessibility service and just trying to get kind of event and getting service is malfunctioning on oneplus 8T. Did u able to resolve the issue somehow.
GiteaMirror commented 2026-04-10 23:12:08 -05:00
Author
Owner
Copy Link

@KaiLCU commented on GitHub (Jul 21, 2021):

Identical problem on Poco F3 running MIUI 12.5 (Android 12)

<!-- gh-comment-id:884011457 --> @KaiLCU commented on GitHub (Jul 21, 2021): Identical problem on Poco F3 running MIUI 12.5 (Android 12)
GiteaMirror commented 2026-04-10 23:12:08 -05:00
Author
Owner
Copy Link

@rohitkhullar88 commented on GitHub (Aug 4, 2021):

Facing same issue in sending WhatsApp message using accessibility service but it crashes after 5 times working properly. Then I need to manually click 2 times back button to come back to my Original Android App after sending the message.

<!-- gh-comment-id:892871169 --> @rohitkhullar88 commented on GitHub (Aug 4, 2021): Facing same issue in sending WhatsApp message using accessibility service but it crashes after 5 times working properly. Then I need to manually click 2 times back button to come back to my Original Android App after sending the message.
GiteaMirror commented 2026-04-10 23:12:09 -05:00
Author
Owner
Copy Link

@maxwowpow commented on GitHub (Sep 19, 2021):

Redmi Note 9
Same message while trying to click the icon in quick settings.

<!-- gh-comment-id:922549652 --> @maxwowpow commented on GitHub (Sep 19, 2021): Redmi Note 9 Same message while trying to click the icon in quick settings.
GiteaMirror commented 2026-04-10 23:12:09 -05:00
Author
Owner
Copy Link

@AM-ElZaher commented on GitHub (Nov 17, 2021):

Same error on Xiaomi Mi 9T
Is there any fix soon?

<!-- gh-comment-id:971715940 --> @AM-ElZaher commented on GitHub (Nov 17, 2021): Same error on Xiaomi Mi 9T Is there any fix soon?
GiteaMirror commented 2026-04-10 23:12:10 -05:00
Author
Owner
Copy Link

@SudoNova commented on GitHub (Nov 24, 2021):

Same issue MiUI12.5.5 on Mi 10T (Android 11)

<!-- gh-comment-id:977668325 --> @SudoNova commented on GitHub (Nov 24, 2021): Same issue MiUI12.5.5 on Mi 10T (Android 11)
GiteaMirror commented 2026-04-10 23:12:10 -05:00
Author
Owner
Copy Link

@nri82 commented on GitHub (Jan 18, 2022):

Same here MIUI 12.5 android 11, Poco X3 NFC

Clear app data, reinstall, reboot did not solves this problem.

IMG_20220118_192711

<!-- gh-comment-id:1015590624 --> @nri82 commented on GitHub (Jan 18, 2022): Same here MIUI 12.5 android 11, Poco X3 NFC Clear app data, reinstall, reboot did not solves this problem. ![IMG_20220118_192711](https://user-images.githubusercontent.com/18355195/149978814-61bd8782-e6ee-4e5d-82f3-f845df1c160f.jpg)
GiteaMirror commented 2026-04-10 23:12:10 -05:00
Author
Owner
Copy Link

@HydroFerret commented on GitHub (Mar 28, 2022):

No go on Poco X3 Pro. Whats the deal yo?

<!-- gh-comment-id:1080443823 --> @HydroFerret commented on GitHub (Mar 28, 2022): No go on Poco X3 Pro. Whats the deal yo?
GiteaMirror commented 2026-04-10 23:12:11 -05:00
Author
Owner
Copy Link

@EMREOYUN commented on GitHub (Jun 29, 2022):

The same happens on Huawei P Smart 2018 with EMUI 9.1 (Android 9)

<!-- gh-comment-id:1170356543 --> @EMREOYUN commented on GitHub (Jun 29, 2022): The same happens on Huawei P Smart 2018 with EMUI 9.1 (Android 9)
GiteaMirror commented 2026-04-10 23:12:11 -05:00
Author
Owner
Copy Link

@nri82 commented on GitHub (Jun 30, 2022):

Okay I found a simple solution.

Just give auto start permission and then problem solved.

Screenshot_20220630_073231

<!-- gh-comment-id:1170751419 --> @nri82 commented on GitHub (Jun 30, 2022): Okay I found a simple solution. Just give auto start permission and then problem solved. ![Screenshot_20220630_073231](https://user-images.githubusercontent.com/18355195/176593376-bb4cfc2c-c000-48e3-bf45-9989b1c6689b.jpg)
GiteaMirror commented 2026-04-10 23:12:12 -05:00
Author
Owner
Copy Link

@blakeNaccarato commented on GitHub (Jun 30, 2022):

@nri82 What phone and OS version are you running? I don't see that exact interface on my Pixel 3a running Android 12 (Build SP2A.220505.006). I wonder if there's a similar permission that goes by a different name?

<!-- gh-comment-id:1171380270 --> @blakeNaccarato commented on GitHub (Jun 30, 2022): @nri82 What phone and OS version are you running? I don't see that exact interface on my Pixel 3a running Android 12 (Build SP2A.220505.006). I wonder if there's a similar permission that goes by a different name?
GiteaMirror commented 2026-04-10 23:12:12 -05:00
Author
Owner
Copy Link

@nri82 commented on GitHub (Jun 30, 2022):

@nri82 What phone and OS version are you running? I don't see that exact interface on my Pixel 3a running Android 12 (Build SP2A.220505.006). I wonder if there's a similar permission that goes by a different name?

Poco X3 NFC, android 11, MIUI 12.5. in short you need to give auto start permission but I don't know it's works or not on your situation.

<!-- gh-comment-id:1171414862 --> @nri82 commented on GitHub (Jun 30, 2022): > @nri82 What phone and OS version are you running? I don't see that exact interface on my Pixel 3a running Android 12 (Build SP2A.220505.006). I wonder if there's a similar permission that goes by a different name? Poco X3 NFC, android 11, MIUI 12.5. in short you need to give auto start permission but I don't know it's works or not on your situation.
GiteaMirror commented 2026-04-10 23:12:13 -05:00
Author
Owner
Copy Link

@EMREOYUN commented on GitHub (Jul 1, 2022):

Okay I found a simple solution.

Just give auto start permission and then problem solved.

@nri82 Autostart is not a thing on Huawei

<!-- gh-comment-id:1172093238 --> @EMREOYUN commented on GitHub (Jul 1, 2022): > Okay I found a simple solution. > > Just give auto start permission and then problem solved. @nri82 Autostart is not a thing on Huawei
GiteaMirror commented 2026-04-10 23:12:14 -05:00
Author
Owner
Copy Link

@nri82 commented on GitHub (Jul 1, 2022):

Okay I found a simple solution.
Just give auto start permission and then problem solved.

@nri82 Autostart is not a thing on Huawei

Yes I noticed that my solution is working on Xiaomi MIUI sorry for this situation.

<!-- gh-comment-id:1172217707 --> @nri82 commented on GitHub (Jul 1, 2022): > > Okay I found a simple solution. > > Just give auto start permission and then problem solved. > > @nri82 Autostart is not a thing on Huawei Yes [I noticed that](https://dontkillmyapp.com/huawei) my solution is working on Xiaomi MIUI sorry for this situation.
GiteaMirror commented 2026-04-10 23:12:14 -05:00
Author
Owner
Copy Link

@Web-E commented on GitHub (Jul 1, 2022):

How about using some Automator like "Tasker" to autostart the the app, say at interval of 1 hour. That might work.
I no longer face this issue as I moved form OP3 to OP8

<!-- gh-comment-id:1172222774 --> @Web-E commented on GitHub (Jul 1, 2022): How about using some Automator like "Tasker" to autostart the the app, say at interval of 1 hour. That might work. I no longer face this issue as I moved form OP3 to OP8
GiteaMirror commented 2026-04-10 23:12:15 -05:00
Author
Owner
Copy Link

@EMREOYUN commented on GitHub (Jul 1, 2022):

How about using some Automator like "Tasker" to autostart the the app, say at interval of 1 hour. That might work.
I no longer face this issue as I moved form OP3 to OP8

@Web-E Huawei also does not like these "Automators" and eventually kill those as well.

<!-- gh-comment-id:1172268924 --> @EMREOYUN commented on GitHub (Jul 1, 2022): > How about using some Automator like "Tasker" to autostart the the app, say at interval of 1 hour. That might work. > I no longer face this issue as I moved form OP3 to OP8 @Web-E Huawei also does not like these "Automators" and eventually kill those as well.
GiteaMirror commented 2026-04-10 23:12:15 -05:00
Author
Owner
Copy Link

@MikeBishop commented on GitHub (Jul 1, 2022):

It will vary for different phones. On the latest OnePlus software, you go to Settings > Apps > Auto launch, find the app you want to allow, and turn it on.

<!-- gh-comment-id:1172362682 --> @MikeBishop commented on GitHub (Jul 1, 2022): It will vary for different phones. On the latest OnePlus software, you go to Settings > Apps > Auto launch, find the app you want to allow, and turn it on.
GiteaMirror commented 2026-04-10 23:12:16 -05:00
Author
Owner
Copy Link

@David263 commented on GitHub (Jul 21, 2022):

Using Tasker to solve this problem probably won't work. Tasker has the same problem.

<!-- gh-comment-id:1191342203 --> @David263 commented on GitHub (Jul 21, 2022): Using Tasker to solve this problem probably won't work. Tasker has the same problem.
GiteaMirror commented 2026-04-10 23:12:16 -05:00
Author
Owner
Copy Link

@sameert89 commented on GitHub (Dec 15, 2022):

Android 12 MIUI, same problem. Not just this app some other apps' accessibility is broken.

<!-- gh-comment-id:1353588901 --> @sameert89 commented on GitHub (Dec 15, 2022): Android 12 MIUI, same problem. Not just this app some other apps' accessibility is broken.
GiteaMirror commented 2026-04-10 23:12:17 -05:00
Author
Owner
Copy Link

@Turab commented on GitHub (Jan 31, 2023):

1- Force stop the application
2- Enable auto start
3- Enable battery saver first, then disable again.
4- Now enable accessibility again.

This solved the problem for MIUI 13 Android 12. The reason for this malfunction is;

1- Google is trying to cripple call recording apps and constantly limiting the use of Accessibility API
2- Some of the vendors like Xiaomi and Samsung kill background applications too often to "save" battery and this breaks how the app works.

By the way, although everything is working smoothly, Bitwarden fails to autofill password fields which open only numpad for entry.

<!-- gh-comment-id:1410378466 --> @Turab commented on GitHub (Jan 31, 2023): 1- Force stop the application 2- Enable auto start 3- Enable battery saver first, then disable again. 4- Now enable accessibility again. This solved the problem for MIUI 13 Android 12. The reason for this malfunction is; 1- Google is trying to cripple call recording apps and constantly limiting the use of Accessibility API 2- Some of the vendors like Xiaomi and Samsung kill background applications too often to "save" battery and this breaks how the app works. By the way, although everything is working smoothly, Bitwarden fails to autofill password fields which open only numpad for entry.
GiteaMirror commented 2026-04-10 23:12:17 -05:00
Author
Owner
Copy Link

@ameerhamza6733 commented on GitHub (Jun 20, 2023):

Okay I found a simple solution.

Just give auto start permission and then problem solved.

Screenshot_20220630_073231

Yes, its work

<!-- gh-comment-id:1598036469 --> @ameerhamza6733 commented on GitHub (Jun 20, 2023): > Okay I found a simple solution. > > Just give auto start permission and then problem solved. > > ![Screenshot_20220630_073231](https://user-images.githubusercontent.com/18355195/176593376-bb4cfc2c-c000-48e3-bf45-9989b1c6689b.jpg) Yes, its work
GiteaMirror commented 2026-04-10 23:12:18 -05:00
Author
Owner
Copy Link

@David263 commented on GitHub (Jun 20, 2023):

Sometimes Accessibility service fails for me, but when using Tasker, not Bitwarden. Also, I can't find this AutoStart option in my app info screen, or in the Permissions Manager. Android 11, running on a TCL A3. The Tasker people say it's due to a complicated bug in Android, best as I understand them.

<!-- gh-comment-id:1599510029 --> @David263 commented on GitHub (Jun 20, 2023): Sometimes Accessibility service fails for me, but when using Tasker, not Bitwarden. Also, I can't find this AutoStart option in my app info screen, or in the Permissions Manager. Android 11, running on a TCL A3. The Tasker people say it's due to a complicated bug in Android, best as I understand them.
GiteaMirror commented 2026-04-10 23:12:18 -05:00
Author
Owner
Copy Link

@jf8989 commented on GitHub (Aug 12, 2023):

Hi there. Thank you for clarifying what the issue is. Regarding any accessibility service, it's just impossible to re-enable them automatically if they either malfunction and/or are turned off, isn't it? At least without user interaction, I believe it's impossible to do so, am I right? Now, when you say "enable and disable battery saver", do you mean we ought to do that with the global battery saver or just within the app's settings? I've been experiencing the same issue on my Xiaomi 13 / Android 12 (RemiNote9). But I do wonder whether this malfunction would also happen on Android 13+. Androi 9 seems to be fine, but I yet have to test Android 10, and 11.

<!-- gh-comment-id:1675563494 --> @jf8989 commented on GitHub (Aug 12, 2023): > Hi there. Thank you for clarifying what the issue is. Regarding any accessibility service, it's just impossible to re-enable them automatically if they either malfunction and/or are turned off, isn't it? At least without user interaction, I believe it's impossible to do so, am I right? Now, when you say "enable and disable battery saver", do you mean we ought to do that with the global battery saver or just within the app's settings? I've been experiencing the same issue on my Xiaomi 13 / Android 12 (RemiNote9). But I do wonder whether this malfunction would also happen on Android 13+. Androi 9 seems to be fine, but I yet have to test Android 10, and 11.
GiteaMirror commented 2026-04-10 23:12:19 -05:00
Author
Owner
Copy Link

@David263 commented on GitHub (Aug 12, 2023):

Unfortunately, I'm not an expert on how the Android accessibility service is programmed, or any of Android, for that matter. I'm just a user of Tasker and Bit Warden (and a retired professional software engineer) and not happy with the mixed uses of the accessibility service. Android wants accessibility service to be just for disabled people, but there are certain apps, like Tasker and Bit Warden, that want to be helpful by making devices more useful for everyone. Ideally, Android should provide an "internal" or "advanced" service for such Apps, separate from accessibility service. We need one or two more Permission categories, probably. But only Android developers can help, and they seem unwilling to. Developers of apps like Tasker and Bit Warden must kludge together solutions to get around current Android limitations. The situation is unfair, but not an unusual one in software development history.

<!-- gh-comment-id:1675790923 --> @David263 commented on GitHub (Aug 12, 2023): Unfortunately, I'm not an expert on how the Android accessibility service is programmed, or any of Android, for that matter. I'm just a user of Tasker and Bit Warden (and a retired professional software engineer) and not happy with the mixed uses of the accessibility service. Android wants accessibility service to be just for disabled people, but there are certain apps, like Tasker and Bit Warden, that want to be helpful by making devices more useful for everyone. Ideally, Android should provide an "internal" or "advanced" service for such Apps, separate from accessibility service. We need one or two more Permission categories, probably. But only Android developers can help, and they seem unwilling to. Developers of apps like Tasker and Bit Warden must kludge together solutions to get around current Android limitations. The situation is unfair, but not an unusual one in software development history.
GiteaMirror commented 2026-04-10 23:12:19 -05:00
Author
Owner
Copy Link

@David263 commented on GitHub (Aug 12, 2023):

It seems to me that one such kludge is to run a separate service or app that monitors the accessibility service and re-enables it when Android decides to stop it or to block permission to use it. Such a service only needs to run once every few seconds.

<!-- gh-comment-id:1675791889 --> @David263 commented on GitHub (Aug 12, 2023): It seems to me that one such kludge is to run a separate service or app that monitors the accessibility service and re-enables it when Android decides to stop it or to block permission to use it. Such a service only needs to run once every few seconds.
GiteaMirror commented 2026-04-10 23:12:20 -05:00
Author
Owner
Copy Link

@jf8989 commented on GitHub (Aug 12, 2023):

It seems to me that one such kludge is to run a separate service or app that monitors the accessibility service and re-enables it when Android decides to stop it or to block permission to use it. Such a service only needs to run once every few seconds.

Well, as far as I'm concerned, it's impossible to re-enable an accessibility service without user interaction after it has been turned off. Nevertheless, I don't know if it's possible to automatically fix it if the problem is that it is malfunctioning while still being on. In this case, theoretically, one should be able to do something in order to automatically repair the malfunction. Maybe a work manager could fix it. I'm sure it's possible to monitor the service state at the least. I can't believe no one has found a workaround. Or maybe they have and haven't shared it yet.

<!-- gh-comment-id:1675887378 --> @jf8989 commented on GitHub (Aug 12, 2023): > It seems to me that one such kludge is to run a separate service or app that monitors the accessibility service and re-enables it when Android decides to stop it or to block permission to use it. Such a service only needs to run once every few seconds. Well, as far as I'm concerned, it's impossible to re-enable an accessibility service without user interaction after it has been turned off. Nevertheless, I don't know if it's possible to automatically fix it if the problem is that it is malfunctioning while still being on. In this case, theoretically, one should be able to do something in order to automatically repair the malfunction. Maybe a work manager could fix it. I'm sure it's possible to monitor the service state at the least. I can't believe no one has found a workaround. Or maybe they have and haven't shared it yet.
GiteaMirror commented 2026-04-10 23:12:20 -05:00
Author
Owner
Copy Link

@jf8989 commented on GitHub (Aug 12, 2023):

Now that I think about it, it'd make sense to be cautious not to share the workaround because android developers would just patch it. I mean, clearly they have no intention of prioritizing continuity on Android services in general.

<!-- gh-comment-id:1675890090 --> @jf8989 commented on GitHub (Aug 12, 2023): Now that I think about it, it'd make sense to be cautious not to share the workaround because android developers would just patch it. I mean, clearly they have no intention of prioritizing continuity on Android services in general.
GiteaMirror commented 2026-04-10 23:12:21 -05:00
Author
Owner
Copy Link

@David263 commented on GitHub (Aug 12, 2023):

Over at least the past year, the Tasker developer has frequently posted supposed fixes for the problem that restarting Android or installing a new version sometimes stops the accessibility service, including his creating a separate app that the user installs. None of these fixes have worked perfectly for me, although some have helped. I agree that it may not be ethical to publicize a fix, since it currently seems against the wishes of the Android developers. As I said, there needs to be a new and separate service for apps like Tasker and Bit Warden to give them the ability to do what they need to do.

<!-- gh-comment-id:1675939666 --> @David263 commented on GitHub (Aug 12, 2023): Over at least the past year, the Tasker developer has frequently posted supposed fixes for the problem that restarting Android or installing a new version sometimes stops the accessibility service, including his creating a separate app that the user installs. None of these fixes have worked perfectly for me, although some have helped. I agree that it may not be ethical to publicize a fix, since it currently seems against the wishes of the Android developers. As I said, there needs to be a new and separate service for apps like Tasker and Bit Warden to give them the ability to do what they need to do.
GiteaMirror commented 2026-04-10 23:12:21 -05:00
Author
Owner
Copy Link

@jf8989 commented on GitHub (Aug 12, 2023):

Over at least the past year, the Tasker developer has frequently posted supposed fixes for the problem that restarting Android or installing a new version sometimes stops the accessibility service, including his creating a separate app that the user installs. None of these fixes have worked perfectly for me, although some have helped. I agree that it may not be ethical to publicize a fix, since it currently seems against the wishes of the Android developers. As I said, there needs to be a new and separate service for apps like Tasker and Bit Warden to give them the ability to do what they need to do.

I totally agree with you. Not only would it be unethical, it'd also be a problem to the one that found the fix because Android would take a look and patch it. If I found a fix, I wouldn't want to let Android know. I mean, I understand their posture on this matter; nevertheless, like you well said, they should at least allow some apps to use an unrestricted type of service that let's them do what they are intending to do. I agree 100%. If anyone would like to create an entire new mobile OS, please let me know so we can team up because I'm tired of Android...he he.

<!-- gh-comment-id:1675942151 --> @jf8989 commented on GitHub (Aug 12, 2023): > Over at least the past year, the Tasker developer has frequently posted supposed fixes for the problem that restarting Android or installing a new version sometimes stops the accessibility service, including his creating a separate app that the user installs. None of these fixes have worked perfectly for me, although some have helped. I agree that it may not be ethical to publicize a fix, since it currently seems against the wishes of the Android developers. As I said, there needs to be a new and separate service for apps like Tasker and Bit Warden to give them the ability to do what they need to do. I totally agree with you. Not only would it be unethical, it'd also be a problem to the one that found the fix because Android would take a look and patch it. If I found a fix, I wouldn't want to let Android know. I mean, I understand their posture on this matter; nevertheless, like you well said, they should at least allow some apps to use an unrestricted type of service that let's them do what they are intending to do. I agree 100%. If anyone would like to create an entire new mobile OS, please let me know so we can team up because I'm tired of Android...he he.
GiteaMirror commented 2026-04-10 23:12:22 -05:00
Author
Owner
Copy Link

@andymarden commented on GitHub (Feb 3, 2024):

Had this issue myself with poco F3, miui 14 and bitwarden.

Autostart (once I be found the setting which moved) didn't fix it, Bitwarden still shows it is malfunctioning.

Tried to lock the app but there is this bug on the recent apps and 3rd party launchers in the menu when you long press dues but sure.

Eventually found it (miui seen to have a competition at each release to move a setting to the most obscure place possible).

That works - is you lock Bitwarden in memory, the accessibility is fixed.

Why that should error out is this is but dry must, in itself, be a bug.

Locking the app (not too be confused with lock app which is completely different ffs) can now be found under Security -> Boost Speed -> Lock Apps.

Can I just say how much I enjoy, in this screen, the fact that the apps are listed in NI discernable order. And just wtf has Boost Speed got to do with Security?

It's as if they are trying to make it impossible to find and, if you are lucky enough to stumble across it, unnecessarily awkward to use. Jesus, Xiaomi..

Still - that's how I got it working.

<!-- gh-comment-id:1925478854 --> @andymarden commented on GitHub (Feb 3, 2024): Had this issue myself with poco F3, miui 14 and bitwarden. Autostart (once I be found the setting which moved) didn't fix it, Bitwarden still shows it is malfunctioning. Tried to lock the app but there is this bug on the recent apps and 3rd party launchers in the menu when you long press dues but sure. Eventually found it (miui seen to have a competition at each release to move a setting to the most obscure place possible). That works - is you lock Bitwarden in memory, the accessibility is fixed. Why that should error out is this is but dry must, in itself, be a bug. Locking the app (not too be confused with lock app which is completely different ffs) can now be found under Security -> Boost Speed -> Lock Apps. Can I just say how much I enjoy, in this screen, the fact that the apps are listed in NI discernable order. And just wtf has Boost Speed got to do with Security? It's as if they are trying to make it impossible to find and, if you are lucky enough to stumble across it, unnecessarily awkward to use. Jesus, Xiaomi.. Still - that's how I got it working.
GiteaMirror commented 2026-04-10 23:12:22 -05:00
Author
Owner
Copy Link

@vvolkgang commented on GitHub (Jun 20, 2024):

Issue migrated to https://github.com/bitwarden/mobile/issues/596

<!-- gh-comment-id:2181551297 --> @vvolkgang commented on GitHub (Jun 20, 2024): Issue migrated to https://github.com/bitwarden/mobile/issues/596
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#6848
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?