Zum Inhalt der Seite gehen
What is going on with #Amethyst? 🤔
https://friendica-leipzig.de/photo/media/474686 https://friendica-leipzig.de/photo/media/474687
#Amethyst
Uno
Think it's to allow notification updates while app is closed
MountainLion
I have notification off. I have never allowed that permission.
Uno
That's weird.
Vitor Pamplona
The app should never run in the background unless you had a video playing. Are you using graphene?
MountainLion
There is no video playing. Yesterday it ran 6 hours in the background. Yes, I am using Graphene.
Vitor Pamplona
Yeah, there is something wrong with Graphene. It looks like sometimes the OS doesn't send the pause notification to the app when you send it to the background. I am not sure how to solve this.
Chris
@c15a5a65 Can you raise awareness with the Graphene team on this issue? I have the exact same problem.
@final [GrapheneOS] 📱👁️‍🗨️
MountainLion
@b98ded4c
@Final
Final
I've alerted this but note certain situations lets apps still run. I'm not able to reproduce it. Also note minimizing the app =/= closing the app. They're different, you must use the recents screen.

Apps have to go out of their way and have a prominent notification / remain a foreground service and that stops it. Apps and foreground services can also re-start other apps (that's why the disable feature exists)

Anyways CCing so everyone else can see: @GrapheneOS
@GrapheneOS
Chris
Thank you! Whatever it is, the issue seems to be specific to GOS, not stock Pixel. @460c25e6 & @GrapheneOS need to talk. This has been wrecking havoc on battery life for too long.
@GrapheneOS @Vitor Pamplona
GrapheneOS
@c15a5a65986e7ab4134dee3ab85254da5c5d4b04e78b4f16c82837192d355185 This is not caused by GrapheneOS. This is how the app is choosing to work without Google Play installed.
@final [GrapheneOS] 📱👁️‍🗨️
GrapheneOS
@c15a5a65986e7ab4134dee3ab85254da5c5d4b04e78b4f16c82837192d355185 It's very clearly a bug in the app. It's not a problem in GrapheneOS or specific to GrapheneOS.
@final [GrapheneOS] 📱👁️‍🗨️
Dieser Beitrag wurde bearbeitet. (1 Monat her)
GrapheneOS
@c15a5a65986e7ab4134dee3ab85254da5c5d4b04e78b4f16c82837192d355185 The app doesn't behave the same without Google Play. Many GrapheneOS users use it without Google Play.
@final [GrapheneOS] 📱👁️‍🗨️
Vitor Pamplona
We have a version without Google play. That version also keeps running on the background. And it only happens on graphene.
GrapheneOS
@c15a5a65986e7ab4134dee3ab85254da5c5d4b04e78b4f16c82837192d355185 It doesn't. It's just where you have a lot of users on A15 QPR1 without Google Play. It's an app bug.
@final [GrapheneOS] 📱👁️‍🗨️
crimsonleaf363
What happened to the keyboard bug in Amethyst? It was about a year ago? You couldnt use OpenBoard or similar keyboards with Amethyst. I don't remember how the bug was fixed.

OpenBoard like keyboards and Amethyst about a year ago. Vitor said there was nothing titWasnt it last year happen last year?
GrapheneOS
@c15a5a65986e7ab4134dee3ab85254da5c5d4b04e78b4f16c82837192d355185 Apps using Compose had major keyboard entry bugs. It wasn't a bug in those keyboard apps.
@final [GrapheneOS] 📱👁️‍🗨️
GrapheneOS
@c15a5a65986e7ab4134dee3ab85254da5c5d4b04e78b4f16c82837192d355185 They're completely wrong. They're blaming GrapheneOS for a bug in the app. GrapheneOS doesn't change anything about how this works and the issue is specific to this app.
@final [GrapheneOS] 📱👁️‍🗨️
Vitor Pamplona
Then why the bug only happens on graphene?
GrapheneOS
@c15a5a65986e7ab4134dee3ab85254da5c5d4b04e78b4f16c82837192d355185 It doesn't. It's just where you have a lot of users on A15 QPR1 without Google Play. It's an app bug.
@final [GrapheneOS] 📱👁️‍🗨️
GrapheneOS
@c15a5a65986e7ab4134dee3ab85254da5c5d4b04e78b4f16c82837192d355185 Do you really think that such basic OS functionality doesn't work on GrapheneOS and yet it's only your app it impacts? We don't change any of this. It doesn't add up.
@final [GrapheneOS] 📱👁️‍🗨️
Vitor Pamplona
Yes. I have seen so many screenshots of the settings page that show apps running on the background when they shouldn't that I strongly believe there is a bug somewhere. Again, this never happens on stick and Samsung versions.
GrapheneOS
@c15a5a65986e7ab4134dee3ab85254da5c5d4b04e78b4f16c82837192d355185 You don't have an actual basis or evidence for claiming that this is a bug in GrapheneOS. You're jumping to that conclusion and we know it's highly unlikely to be the OS.
@final [GrapheneOS] 📱👁️‍🗨️
GrapheneOS
@c15a5a65986e7ab4134dee3ab85254da5c5d4b04e78b4f16c82837192d355185 It's likely that the majority of your users without Google Play are on GrapheneOS and that's why you get the issue reported from users on GrapheneOS, not anything else.
@final [GrapheneOS] 📱👁️‍🗨️
GrapheneOS
@c15a5a65986e7ab4134dee3ab85254da5c5d4b04e78b4f16c82837192d355185 We do not change how any of this works and it's the first time we've ever hearing anything about it, specific to a particular app. Not something which regularly happens.
@final [GrapheneOS] 📱👁️‍🗨️
Vitor Pamplona
The only thing I know is the fact that Graphene keeps running amethyst even though we have no background service. It affects other apps as well and it started about 6 months ago. And again, I have seen this bug dozens of times with different users. ALL of them are on graphene. We have many more users on stock and on Samsung versions and those NEVER detected it.
GrapheneOS
@c15a5a65986e7ab4134dee3ab85254da5c5d4b04e78b4f16c82837192d355185 Your app doesn't work the same way with and without Google Play. You're also talking about devices which aren't on Android 15 QPR1 or perhaps even Android 15 at all.
@final [GrapheneOS] 📱👁️‍🗨️
Vitor Pamplona
How do you know which devices the people that saw this are using? This has absolutely nothing to do with Google Play and you know it.
GrapheneOS
@c15a5a65986e7ab4134dee3ab85254da5c5d4b04e78b4f16c82837192d355185 You don't appear to have any actual reason for claiming this is a bug in GrapheneOS. Why is this only an issue with this one app and not anything else?
@final [GrapheneOS] 📱👁️‍🗨️
Vitor Pamplona
I have seen other apps with high background usage as well. This is not unique to Amethyst.
GrapheneOS
@c15a5a65986e7ab4134dee3ab85254da5c5d4b04e78b4f16c82837192d355185 It is unique to this app and isn't something which has been reported to us. We know that this functionality works fine and we know we don't change any of it whatsoever.
@final [GrapheneOS] 📱👁️‍🗨️
GrapheneOS
@c15a5a65986e7ab4134dee3ab85254da5c5d4b04e78b4f16c82837192d355185 Many apps change behavior when Google Play isn't present. Signal is an example with incredibly high impact on battery life without FCM. It's not an indication of any bug.
@final [GrapheneOS] 📱👁️‍🗨️
Vitor Pamplona
Yeah, but we don't do that. We don't have any service running when Google play is not present. It should have ZERO background usage at all times.
GrapheneOS
@c15a5a65986e7ab4134dee3ab85254da5c5d4b04e78b4f16c82837192d355185 Apps can still have background usage without defining any background services themselves. There are plenty of ways for apps to run in the background not just services.
@final [GrapheneOS] 📱👁️‍🗨️
Vitor Pamplona
Sure, but we pause the entire app when the app goes to the background. I personally reviewed this. Not only with us, but in all dependencies. And again, this only happens on graphene. We have no reports of any other Android os with this issue.
GrapheneOS
@c15a5a65986e7ab4134dee3ab85254da5c5d4b04e78b4f16c82837192d355185 Okay, and we have no reports of any other app with an issue. It's quite possible nearly all your non-Play users are on GrapheneOS. It really doesn't mean very much.
@final [GrapheneOS] 📱👁️‍🗨️
cloud fodder
i can confirm i see no background on stock pixel 6pro, but with graphene there is background. there is weirdness in these sockets in logcat
Vitor Pamplona
I think the OS either doesn't send the on pause call when the app is sent to the background or when you are sliding through apps it calls the on resume but never on pause to turn it off...
Vitor Pamplona
I am willing to bet it is a race condition involving the OS UI and the activity lifecycle.
GrapheneOS
@c15a5a65986e7ab4134dee3ab85254da5c5d4b04e78b4f16c82837192d355185 GrapheneOS doesn't change anything about this. It's just the standard Android 15 QPR1 behavior.
@final [GrapheneOS] 📱👁️‍🗨️
GrapheneOS
@c15a5a65986e7ab4134dee3ab85254da5c5d4b04e78b4f16c82837192d355185 Stock Pixel OS is slightly different from AOSP / other Android due to Pixel Launcher and Pixel SystemUI.
@final [GrapheneOS] 📱👁️‍🗨️
GrapheneOS
@c15a5a65986e7ab4134dee3ab85254da5c5d4b04e78b4f16c82837192d355185 Completely disabling animations on Android is incredibly buggy but in no way specific to GrapheneOS.
@final [GrapheneOS] 📱👁️‍🗨️
Vitor Pamplona
Yep, that's why I think that is the issue.
GrapheneOS
@c15a5a65986e7ab4134dee3ab85254da5c5d4b04e78b4f16c82837192d355185 GrapheneOS has the standard AOSP and Android behavior. The Pixel specific stuff isn't used elsewhere.
@final [GrapheneOS] 📱👁️‍🗨️
Vitor Pamplona
Yep, my point is that the AOSP has a bug.
GrapheneOS
@c15a5a65986e7ab4134dee3ab85254da5c5d4b04e78b4f16c82837192d355185 AOSP Launcher / SystemUI may behave differently from the Pixel forks but it doesn't imply it's a bug.
@final [GrapheneOS] 📱👁️‍🗨️
GrapheneOS
@c15a5a65986e7ab4134dee3ab85254da5c5d4b04e78b4f16c82837192d355185 You can see a bunch of issues filed by app developers about Android onPause closed as WONTFIX.
@final [GrapheneOS] 📱👁️‍🗨️
Vitor Pamplona
Then there is a bug in there that Google and Samsung fixed in their versions. Either way, the experience on graphene is taking the hit.
GrapheneOS
@c15a5a65986e7ab4134dee3ab85254da5c5d4b04e78b4f16c82837192d355185 Samsung doesn't have any OS based on Android 15 QPR1. They don't ship monthly/quarterly updates.
@final [GrapheneOS] 📱👁️‍🗨️
mrequeso 🧀
Just to add an anecdote, every version of GOS and non-Play Amethyst I've ever used across multiple devices has run media in the background even after app close. Force closing is the only way to stop it.
Chris
I'm on Android 15 GOS build 2025011500. Is is repeatable and present all the time.
GrapheneOS
@c15a5a65986e7ab4134dee3ab85254da5c5d4b04e78b4f16c82837192d355185 There's no indication that it has anything to do with GrapheneOS. Recommend starting by trying using exploit protection compatibility mode for the app as usual.
@final [GrapheneOS] 📱👁️‍🗨️
GrapheneOS
No, this is wrong. GrapheneOS does not change how this works and does not have issues with it. The bug is specific to your app and is not caused by GrapheneOS or specific to GrapheneOS. Your app relies on Google Play to work properly and works fine for users on GrapheneOS with sandboxed Google Play.
GrapheneOS
It does not work properly for users without Google Play in general, It's not specific in any way to GrapheneOS. Test on Android 15 QPR1 on any OS without Google Play. The only thing we can do is add a notice to the app explaining it doesn't work properly without Google Play due to an app bug.
Chris
I can confirm I'm running sandboxed Google Play on GOS with non Google Play Amethyst (fdroid version). Still runs in the background. See screenshot. https://friendica-leipzig.de/photo/media/474751
GrapheneOS
Use the Google Play variant of the app and see if that one works properly.
⇧