Android widget

[kennelh]

I haven't posted here in a while so thought I'd post an update. I'm still occasionally working on the app, but I'm in a "holding pattern" waiting for Ford to OK the public API. I'd been told end of Q1 but it's still pending approval of the terms by the legal folk.

I took a road trip this month so decided to use the opportunity to see how frequently DCFC data updates. I modified the app to request this once every 30-ish seconds once it detects DCFC is happening and was surprised to see the car does upload data about that frequently. I'm hoping Ford exposes this in the public API as I could then add a "live" charging data view in the app/widget.

I also received a request to have the widget display info about the diesel exhaust fluid status. If you have a diesel, please send me a copy of your log file via DM so I can gather more info on the meaning of the JSON status values.

Sponsored

 

[kennelh]

Uploaded version 2023.07.11 to GitHub and Play Store. No major updates for most F-150 owners, however it's possible that you will need to add your vehicle again under "Manage Vehicles" since the underlying database changed and it may erase that info.

If you own a diesel F-150, however, you can now see the status of your DEF by tapping on "LV Battery"; you can see both the DEF range and DEF level (whatever that is). This is sort of experimental since I've only had one owner to test with, so if you notice something odd send me a DM.

If you own a Lightning, there should be a release in a few days which will allow you to see power/energy updates every 30 seconds while DCFC. The catch is you'll need to manually refresh once you plug in; otherwise it will only detect on the next scheduled refresh.

 

[kennelh]

This is a heads-up for version 2023.07.25 which will upload shortly to GitHub only. If feedback is good then I'll also push to the Play Store, but in case this release turns out to be ? I didn't want to mess too many users up. I haven't found any issues, but YMMV. Just in case, back up your setting first.

If you don't own a Lightning, you may want to skip this update since there's nothing new otherwise.

This is the first attempt at the DC fast charge log viewer; I'm fairly pleased with it but open to feedback and bug reports. You will need to enable the three DCFC settings for it to work; you'll then see a "Display DCFC info" entry in the three-dot menu once there is session data. You won't see anything real-time, only after you finish charging (that maybe a future option, but do test it I really need log files since I won't be DCFC anytime soon).

I'm looking for feedback in particular after you do multiple charging sessions, to make sure the data for each individual session shows up correctly.

 

[2022Bruce_L]

What is the differences between this and Ford Pass? Just joining the chat and not sure. Thanks.

 

[kennelh]

What is the differences between this and Ford Pass? Just joining the chat and not sure. Thanks.

There's a description in the first post, but the TL;DR explanation is this is an Android app which shows a widget on your phone's desktop which displays some useful info. It complements info you can find in FordPass without having to actually open that app.

 

[2022Bruce_L]

There's a description in the first post, but the TL;DR explanation is this is an Android app which shows a widget on your phone's desktop which displays some useful info. It complements info you can find in FordPass without having to actually open that app.

Very cool! Thank you for the bullet points.

 

[kennelh]

Uploaded version 2023.08.14 to GitHub. You will need to sideload this.

Yesterday I released version 2023.08.13 to GitHub which included fixes for displaying notifications and (drumroll) real-time DC Fact Charging data under "View DCFC Logs". You didn't receive a notification because with the changes I made to notifications, I broke the update notification. 2023.08.14 should fix that.

 

[kennelh]

Uploaded version 2023.08.17 to GitHub and Play Store. The changes are applicable to Lightning owners, as it is an attempt to make the "View DCFC log" activity easier to use.

 

[DcnPat]

Uploaded version 2023.08.17 to GitHub and Play Store. The changes are applicable to Lightning owners, as it is an attempt to make the "View DCFC log" activity easier to use.

Has the issue with Ford locking accounts been resolved?

 

[kennelh]

Has the issue with Ford locking accounts been resolved?

I have not heard from anyone this this year (2023) about their account being locked. I've suspected it was caused by some other app or website, but there's no way to confirm conclusively.

I have (finally) got access to the beta of the public API, but no word on when that will go live.

My advice continues to be create a second Ford account linked to your vehicle and use that for the app. If it should get locked out, your original account should still work.

 

[JJSnell]

This looks awesome.
Just tried it and got a crash error.
This is 2023.08.17 on a Samsung S21 Ultra.

 

[Jersey devil]

This looks awesome.
Just tried it and got a crash error.
This is 2023.08.17 on a Samsung S21 Ultra.

Had the same issue. After I uninstalled the older version and installed the latest one it seems to be working fine

 

[JJSnell]

Had the same issue. After I uninstalled the older version and installed the latest one it seems to be working fine

Okay thanks. Mine was a fresh install. It never had a previous version. Have been talking to Kenneth behind the scenes and he is looking into it.

 

[camattin]

So I'd thought everything was good with the widget on my phone but I was living a lie. ?

I've downloaded the latest GitHub release, cleared cache and data, but it's still crashing.

Chrome on the phone isn't letting me attach the log, but it's not that large, so here we go

--------- beginning of crash
08-19 19:11:52.303 31581 31603 E AndroidRuntime: FATAL EXCEPTION: DefaultDispatcher-worker-3
08-19 19:11:52.303 31581 31603 E AndroidRuntime: Process: com.example.khughes.machewidget, PID: 31581
08-19 19:11:52.303 31581 31603 E AndroidRuntime: android.view.ViewRootImpl$CalledFromWrongThreadException: Only the original thread that created a view hierarchy can touch its views.
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at android.view.ViewRootImpl.checkThread(ViewRootImpl.java:11586)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at android.view.ViewRootImpl.requestLayout(ViewRootImpl.java:2648)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at android.view.View.requestLayout(View.java:27623)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at android.view.View.requestLayout(View.java:27623)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at android.view.View.requestLayout(View.java:27623)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at android.view.View.requestLayout(View.java:27623)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at android.view.View.requestLayout(View.java:27623)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at android.view.View.requestLayout(View.java:27623)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at android.view.View.requestLayout(View.java:27623)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at androidx.appcompat.widget.ActionMenuPresenter.updateMenuView(ActionMenuPresenter.java:228)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at androidx.appcompat.view.menu.MenuBuilder.dispatchPresenterUpdate(MenuBuilder.java:292)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at androidx.appcompat.view.menu.MenuBuilder.onItemsChanged(MenuBuilder.java:1065)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at androidx.appcompat.view.menu.MenuBuilder.onItemVisibleChanged(MenuBuilder.java:1104)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at androidx.appcompat.view.menu.MenuItemImpl.setVisible(MenuItemImpl.java:671)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at com.example.khughes.machewidget.MainActivity$onCreateOptionsMenu$1.invokeSuspend(MainActivity.kt:233)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at kotlinx.coroutines.internal.LimitedDispatcher.run(LimitedDispatcher.kt:42)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:95)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     Suppressed: kotlinx.coroutines.DiagnosticCoroutineContextException: [StandaloneCoroutine{Cancelling}@ba92612, Dispatchers.IO]

 

[kennelh]

So I'd thought everything was good with the widget on my phone but I was living a lie. ?

I've downloaded the latest GitHub release, cleared cache and data, but it's still crashing.

Chrome on the phone isn't letting me attach the log, but it's not that large, so here we go

--------- beginning of crash
08-19 19:11:52.303 31581 31603 E AndroidRuntime: FATAL EXCEPTION: DefaultDispatcher-worker-3
08-19 19:11:52.303 31581 31603 E AndroidRuntime: Process: com.example.khughes.machewidget, PID: 31581
08-19 19:11:52.303 31581 31603 E AndroidRuntime: android.view.ViewRootImpl$CalledFromWrongThreadException: Only the original thread that created a view hierarchy can touch its views.
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at android.view.ViewRootImpl.checkThread(ViewRootImpl.java:11586)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at android.view.ViewRootImpl.requestLayout(ViewRootImpl.java:2648)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at android.view.View.requestLayout(View.java:27623)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at android.view.View.requestLayout(View.java:27623)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at android.view.View.requestLayout(View.java:27623)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at android.view.View.requestLayout(View.java:27623)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at android.view.View.requestLayout(View.java:27623)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at android.view.View.requestLayout(View.java:27623)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at android.view.View.requestLayout(View.java:27623)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at androidx.appcompat.widget.ActionMenuPresenter.updateMenuView(ActionMenuPresenter.java:228)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at androidx.appcompat.view.menu.MenuBuilder.dispatchPresenterUpdate(MenuBuilder.java:292)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at androidx.appcompat.view.menu.MenuBuilder.onItemsChanged(MenuBuilder.java:1065)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at androidx.appcompat.view.menu.MenuBuilder.onItemVisibleChanged(MenuBuilder.java:1104)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at androidx.appcompat.view.menu.MenuItemImpl.setVisible(MenuItemImpl.java:671)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at com.example.khughes.machewidget.MainActivity$onCreateOptionsMenu$1.invokeSuspend(MainActivity.kt:233)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at kotlinx.coroutines.internal.LimitedDispatcher.run(LimitedDispatcher.kt:42)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:95)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664)
08-19 19:11:52.303 31581 31603 E AndroidRuntime:     Suppressed: kotlinx.coroutines.DiagnosticCoroutineContextException: [StandaloneCoroutine{Cancelling}@ba92612, Dispatchers.IO]

Is this the version I uploaded today (2023.08.19)?

Sponsored