{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreia4dhazd6ug3waspsmlfzsadlsqlj47sws2u47vw2cvofv74aaj6e",
    "uri": "at://did:plc:34cg4tn4iwemk3v5k3n3adwf/app.bsky.feed.post/3miiwc3ksnla2"
  },
  "path": "/t/question-regarding-compliance-with-f-droid-rules/34216#post_8",
  "publishedAt": "2026-04-02T08:10:07.000Z",
  "site": "https://forum.f-droid.org",
  "textContent": "That is clear  But the same DontKillMyApp and DroidStress are on F-Droid. My task is different. My mechanisms (in BackgroundWorkAround) are slightly different. I want to understand if it is possible to use such mechanisms in F-Droid, and therefore whether I can add such a library to my applications. For example, what about goAsync() + Thread.sleep(Long.MAX_VALUE) inside a receiver? And 10 wake locks for 3 seconds in a while true loop with a timeout of 0.33s? And what about sending a Broadcast to a static receiver every 7.5s and separating components into different processes? And is it allowed to perform mutual bind of services of one application in 2 different processes? And is it allowed to reset alarm every 30s? Therefore, I want to find out by trying to publish the BackgroundWorkAround applications on F-Droid.\n\nOn AOSP, there’s no need for such tricks, of course, but on MIUI, for example, it can be necessary.",
  "title": "Question regarding compliance with F-Droid rules"
}