| Note |
|---|
For other handsets which are unknown compatibility, it may be worth checking https://dontkillmyapp.com/problem then major offending vendors include Nokia, Xiaomi, OnePlus, Samsung or Huawei . The best solution however is to do some basic testing. |
...
| Brand | Model Name | Compatibility Issue | App/Device Affected | Reference Issue | Issue Fixed | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Huawei | P Smart (FIG-LX1) | User A user reported a battery 30% draining with the pRMT app substantially, heavier | pRMT |
| Not sure it is anything beyond the expected level of battery drainage. | ||||||||
| Sony | Xperia | Scanning issues with this phone's camera & some problem problems with the QR code or library | pRMT, aRMT |
| Fixed: (this should no longer be a problem on the new QR Code) | ||||||||
| Samsung | A6 | Phone The phone was reportedly not receiving notifications even though we have acknowledgements in Firebase | aRMT |
| Fixed: Turns out it was reported as a Mistake. It was not an A3 but a Huawei 10 phone which is also now receiving the notifications so seems no issue here really. Still not sure about the A6 though. A3 and S6 reported in RSD-158 are both working | ||||||||
| Xiaomi | mi A1, note4 | aRMT notifications doesndon't sound | aRMT | ||||||||||
| Nokia | 8.3 5G | pRMT is not working or being reaped by the app resource monitor. Nokia 8.3 5G running Android 12. From what I can see on the FTP server and from Googling, I think this phone has a similar issue to Huawei phones where the battery saving and other built-in software kills the app. It looks like there is not an awful lot that can be done about it (see https://dontkillmyapp.com/nokia) (Reported by Isabel YorkeIY, AIMS2TRIALS) | pRMT | ||||||||||
Potential Fixes
For Huawei Devices
...
Starting Jan 2019, FCM will not deliver messages to apps which were put into background restriction by the user (such as via: Setting -> Apps and Notification -> [appname] -> Battery). Once your app is removed from background restriction, new messages to the app will be delivered as before. In order to prevent lost messages and other background restriction impacts, make sure to avoid bad behaviors listed by the Android vitals effort. These behaviors could lead to the Android device recommending to the user that your app be background restricted. Your app can check if it is background restricted using: isBackgroundRestricted().
Thus make sure to remove the aRMT (and pRMT too) from the background restriction in the android device otherwise they will not be able to receive Notifications.
...