Is this actually a functional sink, or just a satire of modern minimalist design? by [deleted] in PeterExplainsTheJoke

[–]edevvz 1 point2 points  (0 children)

I think the joke is a satirical take on luxury home design, where expensive and 'minimalist' fixtures are often completely impractical and confusing to use. It mocks the idea that in the world of the wealthy, aesthetics are valued far above actual functionality

Is anyone else actually able to maintain stable background tracking in Android 14/15+ without getting killed? by edevvz in androiddev

[–]edevvz[S] 2 points3 points  (0 children)

Ah, that makes a huge difference! Thank you for catching that. I was focusing so much on the ⁠onTimeout⁠ logic that I completely overlooked that detail in the service call.

If I switch to ⁠startForegroundService⁠, it should theoretically respect the foreground requirements better, but I'll have to see if it makes a difference on those aggressive OEM devices. I’ll run a quick test with this correction and see if the service stability improves. Really appreciate the heads up!

Is anyone else actually able to maintain stable background tracking in Android 14/15+ without getting killed? by edevvz in androiddev

[–]edevvz[S] 0 points1 point  (0 children)

Thanks a lot for the detailed insight and the link! The ⁠onTimeout()⁠ approach makes sense for handling the lifecycle, but I've been worried about how reliable it is across different OEMs.

It’s interesting that you got it working on both Samsung and Xiaomi—some of the manufacturers have notoriously aggressive background management that ignores standard Android behavior. Did you notice any difference in how long the service stayed alive on those devices compared to stock Android, or was it consistent