Closed remulasce closed 9 years ago
It also looks like I can get the service into a crashed sort of state.
The whole thing is super sketchy. You shouldn't rewrite stuff and expect it to be better... but this could sure use a rewrite.
(It's a single fucking file, you can do a proper slow refactor transition)
I think I got a repro on one issue, which is just the combination phone off / alert combination. Removed the code that shuts down if we've been out of network a while, since 'lost network' is a valid state to be in.
The nice thing is that the 'important icon' showed up but the thing didn't ring, so I knew that most of the app was functioning properly, just not the alert.
The notification still seems to be left in a werd state after you turn the device off and back on. Like the notification doesn't get updated any more but just stays up.
I think sometimes it loses foreground but doesn't disappear?
Service no longer shuts down / fails after periods of network disconnectivity. Shows how long it's been since update now.
Not like this issue was has anything to do with custom alert times or anything.
Testingish. I'm annoyed that it doesn't instantly refresh when you turn the screen on again.
I'm thinking, quicker update interval if we have no service.
Ok, quicker interval is in.
It's still up in the air how much stuff actually gets done in the background when the phone's off, but at least old predictions should still work.
User reports if she changes the alert time to any other time, she doesn't get the 'near arrival' alert.
I've also noticed that this happens to me sometimes.
Testing out the service and looking through code:
I don't feel like this solves all of the issues I've seen or heard from. But basically, the notify service was never supposed to ever go into production, and it's had hacks added on top of it to boot.