Buy an iPhoneAny solutions??
If I buy an iPhone I would have to trade the mme for a horse and buggy so the technology would be from same era.Buy an iPhone
Unfortunately outside of that there is not a lot you can do. Not sure if you have journeys turned on or not, but you can defiantly shut that off. With it turned on its running your phones GPS the entire time, which is stupid the car has its own....
What phone and Android version are you running? If you don't have your permissions correct it will continuously kill the background activity and the app will then relaunch. Make sure that you have disabled all power save features for the FP app. You can DM me if you need help.My fordpass app is killing my battery. If I put it to sleep my PAAK doesnt work unless I run the app. Any solutions??
Worst suggestion ever! I assume you also use Apple maps to make a right into the ocean or off cliffs?Buy an iPhone
Don't be so hard on your Mach E. Still, end of the day, there has been more Android related problems that iOS problems on this and other Mach E sites. I get that here are more Android OS phones out there - but still.If I buy an iPhone I would have to trade the mme for a horse and buggy so the technology would be from same era.
Have a note 20 ultra. It constantly pops up fordpass trying to use as key or something like that. Seems that when my wife takes car my phone tries to connect and never stops.What phone and Android version are you running? If you don't have your permissions correct it will continuously kill the background activity and the app will then relaunch. Make sure that you have disabled all power save features for the FP app. You can DM me if you need help.
I have about 3% usage daily from FP on a Pixel 6 Pro / Android 12
Worst suggestion ever! I assume you also use Apple maps to make a right into the ocean or off cliffs?
So it's normal for the FP app to stay running in the background and say "Attempting to connect to the car". This is for PaaK so that when you approach the car it will work. I looked at the code and it's programmed to prevent it from being killed. The problem is when the OS attempts to kill the app. This can cause a vicious cycle where the phone kills it, the app re-launches and it just goes on and on.Have a note 20 ultra. It constantly pops up fordpass trying to use as key or something like that. Seems that when my wife takes car my phone tries to connect and never stops.
Had iphone 1-6, switched then and have never looked back. There's tons of threads of it doing same thing to iPhone.Ya, known issue with Android..
And hey, don't knock iPhones till you try one. I've used android since the first smart phone came out. I switched over to Apple last year, and I must say I actually enjoy it. Is it as customizable, absolutely not, but your security/privacy is on lock down compared to Android. I also like how their app store breaks down every aspect of what the applications have access too and what it does.
And... in the past 10 days, 2% of my battery usage and I use 100% PAAK Plus I also use journeys so I'm sure that would be lower if I had it off.
The weird thing is yesterday the useage was 3% , today its 37%. 3 days ago it was 60% I'll try your suggestions.So it's normal for the FP app to stay running in the background and say "Attempting to connect to the car". This is for PaaK so that when you approach the car it will work. I looked at the code and it's programmed to prevent it from being killed. The problem is when the OS attempts to kill the app. This can cause a vicious cycle where the phone kills it, the app re-launches and it just goes on and on.
Go into the power management settings on the phone and turn off any for the FP app and then go into the app settings and make sure FP is not optimized.
It shouldn't flash the notification, it should just stay as a persistent notification.
So I want background app checked correct??So it's normal for the FP app to stay running in the background and say "Attempting to connect to the car". This is for PaaK so that when you approach the car it will work. I looked at the code and it's programmed to prevent it from being killed. The problem is when the OS attempts to kill the app. This can cause a vicious cycle where the phone kills it, the app re-launches and it just goes on and on.
Go into the power management settings on the phone and turn off any for the FP app and then go into the app settings and make sure FP is not optimized.
It shouldn't flash the notification, it should just stay as a persistent notification.