Not working with OPPO F9 about autostarter HOT 9 OPEN

@Thornith thanks for trying this out, unfortunately as mentioned this has not been tested on a vivo or oppo phone but I am welcome to any pull requests that support these phones or any other.

from autostarter.

Came across the same issue on OPPO R15 (OS 8.1.0).

from autostarter.

Not working on OPPO CPH1609
Android 6.0

from autostarter.

Not working for Oppo A3S (CPH1803), ColorOS - V5.2.1 . I Will update if I come across any other solution. Thanks for putting this library out.

from autostarter.

I've made a pull request for the Oppo Rx17 Neo (and Rx17 Pro) running ColorOS 5.2.
For these devices, the switch for "Allow Auto Start" is within the App Info itself (long press on your app icon).
https://drive.google.com/file/d/1zk7ThbM7eumnphtElRF9Zr9R-uuia9D4/view?usp=sharing
My fix is on a per device basis (value of Build.Product).
If the solution for your Oppo is this, check out PR #51 and if it gets merged, add your device into the list.

from autostarter.

Hey,
@Prometheus3k is headed the right way, but it can never really work on per-device basis. As long as we can assume that either the existing options work, or it's a different OS version that has the auto start option moved to App Info and there are no other options, the reasonable way is to allow AutoStarter for all Oppo devices and when resolving the known activities fails, send to user to App Info.

I'm going to do this in an app with 2M downloads and see what the users say.

Btw I have also checked the current application that manages all kinds of power saving thingamajigs on Oppos (com.coloros.oppoguardelf) and none of the activites available there are exported nor accessible without some special Oppo permissions. In other words: no third party app can do anything anymore. Good job Oppo, I hope you're proud.

from autostarter.

@NoHarmDan Yeah I had thought about this. I had originally put it in the existing try catch blocks, but it's quite an assumption that if none of the security packages are there, we launch app info. We could be taking the user there for no reason (if the switch isn't there).

The current issue is more accurately described as in Oppo RX17 Neo, Color OS 5.2, PhoneManager app (with Privacy Permission, Startup Manager) exists on device, but it cannot be launched. It requires some Oppo "oppo.permission.OPPO_COMPONENT_SAFE" permission?

But the switch does exist in the app info without need for permission.

This is quite a new behaviour with ColorOS. If we can get some more info about this new setup from Oppo, I'd be happy to generalise to default to app info if we can confirm this is not just a solution for this device. Can anyone here help verify?

Does anyone have an Oppo device, Color OS 5.2 (or higher) other than Rx17 Neo/Pro that can check if auto start is in app info (A, R, Reno, Find models)? As I understand it, there are several ColorOS version after 5.2 (6.x.x and 7). Color OS version history
Some folk here have mentioned some devices where the current library packages don't work, but don't mentioned the ColorOS versions for them. If they can verify Allow Auto start switch is in app info for their ColorOS that would be really helpful.

Color OS 7 device list

The Oppo devices I have are on loan so won't have them for much longer to test with.

from autostarter.

Well my point of view is that sending somebody to App Info for no reason is a lesser evil than having your app not working properly. 🤷

And the device I have at hand is the A1k with ColorOS V6.0.1 and auto start in App Info.

from autostarter.

@NoHarmDan perfect, thanks for checking it on ColorOS 6. Can safely say it's a forward trend so I'll update my PR.

Appreciate any posts for other ColorOS versions that have the switch in App Info (or not).

@Thornith
Oppo F9 is also ColorOS 6, Oppo F11 is upgradable to ColorOS 7

from autostarter.