Apps keep getting killed in the background

raxod502

other8026 I have no reason to believe that having root access to my device is related to this problem. Given that flashing the stock ROM (which reverts any modifications that may have been made by Magisk) does not change the behavior, what technical reason do you have to assert that root access is the cause?

de0u

raxod502 Given that flashing the stock ROM (which reverts any modifications that may have been made by Magisk) does not change the behavior, what technical reason do you have to assert that root access is the cause?

Did somebody assert that?

I think what other8026 wrote was not "You are having this problem because of root access". I think what other8026 meant is that the volunteers on the forum are primarily working to support users of unmodified GrapheneOS releases.

In general, the reason people root devices is to make modifications, and once a device's installation has been modified in unknown ways it is much harder to support.

raxod502

de0u The statement "If you've been rooting or otherwise messing with the official releases, we cannot help you with this issue" (especially the word cannot) implied to me that rooting was being blamed for this issue.

I'm really unsure of why rooting the device is considered different than any of the other hundreds of important modifications that can be made to it within the existing operating system. You don't know what apps people have installed, what permissions they've been granted, how all the system settings are configured, etc etc. (Although these are all things I would be more than happy to provide about my setup.)

Regarding the concern about how my device "has been modified in unknown ways" - the ways are certainly not unknown to me, and I'm happy to share exactly what modifications have been made. I simply use Magisk (or specifically this fork that adds GrapheneOS compatibility) to apply Trust User Certs, Block Ads, and (in the past but no longer) MagiskFrida and SafetyNet Fix.

I could believe that MagiskFrida could cause issues around process spawning (and indeed I've reported bugs around that to the module author), but I removed that module as a consequence. The other modules seem completely unrelated to app suspend/resume, and especially do not seem like they would be making persistent modifications to the system that would survive past the ROM being re-flashed.

de0u

raxod502 The statement "If you've been rooting or otherwise messing with the official releases, we cannot help you with this issue" (especially the word cannot) implied to me that rooting was being blamed for this issue.

Personally if somebody says "If A or B then C", I wouldn't transform that statement to "If A then C". What happened to the "or otherwise messing with the official releases" part of the statement?

raxod502 Regarding the concern about how my device "has been modified in unknown ways" - the ways are certainly not unknown to me [...]

You are 100% entitled to believe that the modifications you have made can't possibly be responsible for the unwanted result you are observing. And I think @other8026 is 100% entitled to restrict support efforts to devices running unmodified/unrooted GrapheneOS.

raxod502

de0u Please, I am not trying to start a fight. We don't need to litigate exactly what people should or should not have surmised from the language in specific comments.

All I'm here to do is to participate in a bug report. If the official response is that no bug reports from me are accepted, regardless of area, because of something unrelated that you don't like (i.e. that I've rooted my device), then that's the official response. I understand that as we do not have a commercial relationship this is perfectly within your right, any of my feelings aside.

If on the other hand it's claimed that the fact I've rooted my device is not unrelated, I would be overjoyed to know the reasoning for this, as it would help me troubleshoot or follow up with third-party developers.

de0u

raxod502 If the official response is that no bug reports from me are accepted, regardless of area, because of something unrelated that you don't like (i.e. that I've rooted my device), then that's the official response.

To be clear, no response from me is an official response.

Carlos-Anso

raxod502
If I understand correctly you have sideloaded an OS update and believe this resets everything that you may have changed with the various modules, while your device was rooted, back to default.

While this may be true there is also the possibility that some things were changed that are not reset by flashing an update.

As your problems appear somewhat unique theres a reasonable chance they stem from the somewhat unique modifications you have been making to your device.

Along with rooting, modifying settings in Developer options, making modifications via adb or disabling or denying permissions to system apps can all cause issues that may appear unrelated to those modifications. We strongly advise users to avoid doing these things.

Carlos-Anso

@raxod502 Another cause of your browsers loosing their state could be memory pressure. Particularly if you are on an older device with less RAM, have multiple profiles running, VPNs, apps which have persistent services running and/or wake regularly etc. Some apps are also particularly memory hungry.

Some of the hardening in GrapheneOS can cause apps to have higher memory use compared to other androids. Worth also considering that compared to your experiences on another OS.

If you have Dev options enabled can check in Running services

Ghoelian

The issue seems to have resolved itself the past few days. Spotify hasn't been paused unless I manually paused playback first, and it even goes on all night if I let it play a playlist on repeat.

Not sure what fixed it in the end, there have been several updates to Spotify and also 2 GrapheneOS updates I think.

« Previous Page