Yes, that is why I started the threas calling FP maddeningly inconsistent, Some days there is virtually no battery use - other days it FP seems to run wild, using 3-4% of battery per hour - while running in the background!
I understand. I have poured, arguably, more time into PaaK than most people on this forum. I know the issues presenting people and being that I've developed Android ROMs and apps I also have a bit of insight on the shortcomings of both. Give my suggestions a try and let me know how it goes.
Ohhh right. Sorry I didn't interpret this right until now. I now understand you were saying: Try the things I suggest and you too might not have a problem anymore. I'm on it!
Another possibility I've noticed is that the battery drain requires you to have first completed a driving session with the car. If you just have it on but haven't driven with it, you won't really get it.
I totally understand. Google makes OS decision based on the majority. Automatically killing apps that are running in the background is usually a good thing, unless a user needs a particular app to always run in the background. Unfortunately, when it comes down to it, we have absolutely no say in how Google configures their OS the out of the box. On the plus side Apple doesn't even let PaaK run unless the app is in the background. At least PaaK on Android still works even if you kill (swipe away, not force stop) the app.
Most ?
Obviously, I can't out do you ??
That's awesome. And we absolutely appreciate having a direct channel to the development team. Please, keep the improvements coming.
Yes, been there, done that. At first I thought all my PaaK issues were resolved after implementing all the setting changes you suggested. It did work much better for a while, but then it started crapping out again. And random battery draining recurred. I can go 2, 3, 5 days with no issues and then I notice my phone is hot and dying. FP, every time.
No disappointment. The reason I didn't mention modules in this thread, like I normally do is because it's specifically about battery drain and not connectivity.
I think there is a reason we aren't allowed to. I asked about a lock status a couple years ago and was shot down. I'll bring it up though!That's awesome. And we absolutely appreciate having a direct channel to the development team. Please, keep the improvements coming.
If I may... Let's get a status indicator on the app, for showing whether the doors are currently locked or unlocked. I know it's available in the API! I'll open a feature request JIRA Issue
You have to create the user story and acceptance criteria here in order for it to get copy/pasted into JiraThat's awesome. And we absolutely appreciate having a direct channel to the development team. Please, keep the improvements coming.
If I may... Let's get a status indicator on the app, for showing whether the doors are currently locked or unlocked. I know it's available in the API! I'll open a feature request JIRA Issue
I'm actually going to start on a simple app that will do this. The APIs are all there, and it should be pretty simple.You have to create the user story and acceptance criteria here in order for it to get copy/pasted into Jira
I would toss in there that almost all other mfgs have this.
If there's any one thing I could have from FP this would be the highest priority on my list.
They need to give you guys more free reign. I'm sure the app would get much better!
Amen!They need to give you guys more free reign. I'm sure the app would get much better!
Tell them customers are requesting it, and direct them to this forum
