Closed remulasce closed 9 years ago
It's the TripList update.
I just slowed the expensive GetLocation calls to every 30 seconds. It's still slow.
Looks like hitting LocationService for priority is beating it up. Don't know if it's the gps location, or if it's trying to translate stopnames, or what.
LAMetroUtil parsearrivals bangs up getLocation every PredictionManager update. I don't know why that hangs the UI, but I guess it does?
Well location gets cached now. It's a bit better, still not great.
There was a reversion (there's a better term for that) in that we were getting Location for every trip every time the trip was generated, instead of every x seconds like we'd done for location priority. But that's not the issue.
"Regression"
It's not just MetroApp. It's all apps on my computer with my phone.
Might have something to do with CyanogenMod ROM throwing a ton of exceptions all the time.
I don't know if I'm sending too much logcat or what, but it's super slow.