Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add problematic devices detection and supply a link to the KB article #2458

Closed
ameshkov opened this issue Jan 24, 2019 · 4 comments
Closed

Add problematic devices detection and supply a link to the KB article #2458

ameshkov opened this issue Jan 24, 2019 · 4 comments
Assignees
Milestone

Comments

@ameshkov
Copy link
Member

@ameshkov ameshkov commented Jan 24, 2019

This task consists of several parts actually.

  1. First of all, we need to update the KB article: https://kb.adguard.com/en/android/solving-problems/background-work Use the information from https://dontkillmyapp.com/ to make it up-to-date. @aalpatkina please assist with this.
  2. Second, detect the problematic devices (those with at least 3 downvotes on dontkillmyapp) and warn user that it might be necessary to do something to keep AdGuard in background. @AlikhanAliev how and when should we show this warning?
@ameshkov

This comment has been minimized.

Copy link
Member Author

@ameshkov ameshkov commented Feb 15, 2019

Let's try detecting when this issue happens and then show a notification.

@nkartyshov

This comment has been minimized.

Copy link
Contributor

@nkartyshov nkartyshov commented Mar 6, 2019

done

Test instruction for QA:

Test only on Huawei, Meizu, Xiaomi, OnePlus and Nokia

  1. Start protection
  2. Go to Android settings, find AdGuard, "force stop" it.

Expected result:
AdGuard must show notification about problem with battery saving methods

@roboderpy

This comment has been minimized.

Copy link

@roboderpy roboderpy commented Mar 11, 2019

Seems to work on Xiaomi, but it only display notification after you restart Adguard, which could get some users still confused. Consider to make something a bit more noticeable by the end user.

@ameshkov

This comment has been minimized.

Copy link
Member Author

@ameshkov ameshkov commented Mar 11, 2019

Seems to work on Xiaomi, but it only display notification after you restart Adguard, which could get some users still confused. Consider to make something a bit more noticeable by the end user.

Well, that was the idea -- we'd like to detect the issue first and not alarm users until it happens for the first time.

@zzebrum zzebrum closed this Mar 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.