Hello everyone!
I’m trying to understand how the Amazon Prime Music app works and what permissions it requires. Let me explain:
Since the latest Android update, I’ve noticed that Amazon Music tells me I need to “install Google Play services” and that “the app won’t work without these services…”
Points to note:
- The app is not running when this warning appears (at least, I didn’t ask for it to be)
- This warning appears a few seconds after launching AAS
- The app works anyway, despite this warning
Here are the privacy settings configured for the app:
- Notifications enabled (Downloader, Playback controls, Google Play Services) + notification badge enabled
- Permissions limited to notifications only
- Version 26.4.1, installed from the Aurora Store
It is not the notifications that concern me.
I therefore have several questions:
- Is this app always launched in the background when AAS starts up?
- How can I check this?
Given that my phone can start to overheat abnormally when AAS is active, I wonder if this app is the cause…
Current hardware: Xperia 10 III
Software version: 5.0.0.77
Do you have any advice on how I can try to pinpoint the problem, or trace this app?
Thank you all, have a lovely day!
(Translated by DeepL from French)
you could delete the app and check if the overheating stops…
2 Likes
Hello, you can install crest and so you can see if any process from this app is running. Some ASS apps start with the first start from ASS, but you can stop it in settings/apps and the last Button. Or you use the terminal sudo appsupport-attach am force-stop <name of process>.Good luck
1 Like
I don’t get that warning. I also just allowed notifications.
If the app starts in the background together with AAS can be cecked in Sailfish settings in the Apps tab. If this option is turned off you won’t get notifications.
1 Like
@davidrasch : Thanks for the advice!
The test is so simple that I hadn’t thought to do it… I carried it out today and reinstalled it two hours later – not much difference really… The overheating issue might not be down to that… I’ll try running the test again at another time, when the overheating is really noticeable.
Since reinstalling, I’ve gone from version 26.4.1 to version 26.14
Since then, no more notifications on startup… Could it be because the version has been updated for Android 13? (I’d upgraded from 11 to 13 without changing or updating the apps)
@Cryx : Autostart settings are disabled, as is background execution. Only notifications remain 
@rdomschk : Thanks for this app!! It looks really great!
Well, now that I no longer get notifications on startup, there’s no longer any reason for Amazon to appear in the startup processes… and that’s indeed the case.
However, I’ve realised that WhatsApp is indeed running, and that it doesn’t have permission to start when AAS launches!
I’ll try uninstalling and reinstalling WhatsApp tomorrow, to see if the problem resolves itself in the same way as with Amazon Music…
Here are also a solution to close some ASS apps with one touch. You can also create a desktopapp in qCommand.
1 Like
Using Amazon Prime, esp. for music, sounds like a step in the wrong direction. Make sure you aren’t trapping yourself in a sunk cost fallacy.
The sunk cost fallacy is a purported error in reasoning in which past, irrecoverable investments—known as sunk costs—are treated as reasons for continuing a course of action, even when those past costs cannot be changed and are irrelevant to what is best going forward.
3 Likes
Sunken cost fallacy has nothing to do with this case.
Whatever you bought is yours regardless of subscription and you can still use most of the important services for free even without paying anything, or stop and continue from where you left off later without missing out anything.
I don’t think anyone in this planet has a prime subscription for their music service. It’s just another extra on top of free/faster shipping, extra deals, prime video, reading, games etc.
1 Like
But in that case you won’t get notifications - it’s explicitly ststed that notifications only work with background startup. (But I guess you will get it too when you actively start the app. May be enough for Amazon Music, but not for Apps like Messengers.)
1 Like
Today, the phone overheated.
At first glance, no connection with AAS. (On or off, same effect.) I was inside a building and had very poor reception. It stayed hot the whole time I was inside.
So I imagine the overheating is because the phone was desperately trying to pick up a signal. My phone might be the only one to blame… (maybe it’s taken a few too many knocks?)
All the updates have been applied to the offending apps (WhatsApp and Amazon Music) and from now on, they no longer start automatically when AAS boots up.
However, one thing to note: thanks to Crest, I was able to check that they are definitely closed when I close them manually. However, if I scroll back until the app closes, in that case, it remains in the background. Good to know!
Crest is great software!
I think the solution was found thanks to all of you !!
Translated with DeepL.com (free version)