The "Battery history" chart is a Twizy specific feature, it's a battery cell state chart like the battery monitor in the web UI. It's currently bound to the wrong button though: the button "Energy statistics" should open another Twizy specific chart displaying power levels & energy usage over time. That chart doesn't seem to be available now… and currently the App immediately crashes after selecting a Twizy profile. And keeps crashing, see below. With actual data, the charts look like the example screen shots 2 & 3: https://dexters-web.de/faq#waskann Both charts could get supported generally, with some modifications. They currently need the Twizy specific historical data records (RT-BAT-P, RT-BAT-C, RT-PWR-Stats). The main issue is finding a suitable generalization for these. Twizy crash log excerpt: 2024-12-31 13:04:01.702 25409-25409 ApiWidget com.openvehicles.OVMS V onReceive: ApiEvent LoginComplete 2024-12-31 13:04:01.702 25409-25409 ApiWidget com.openvehicles.OVMS V updateAllWidgets: 1 instances 2024-12-31 13:04:01.956 25409-25409 AndroidRuntime com.openvehicles.OVMS D Shutting down VM 2024-12-31 13:04:01.957 25409-25409 AndroidRuntime com.openvehicles.OVMS E FATAL EXCEPTION: main Process: com.openvehicles.OVMS, PID: 25409 java.util.UnknownFormatConversionException: Conversion = 'End of String' at java.util.Formatter$FormatSpecifierParser.peek(Formatter.java:2647) at java.util.Formatter$FormatSpecifierParser.<init>(Formatter.java:2608) at java.util.Formatter.parse(Formatter.java:2563) at java.util.Formatter.format(Formatter.java:2510) at java.util.Formatter.format(Formatter.java:2464) at java.lang.String.format(String.java:3603) at com.openvehicles.OVMS.ui2.pages.HomeFragment.initialiseTabs(HomeFragment.kt:1081) at com.openvehicles.OVMS.ui2.pages.HomeFragment.update(HomeFragment.kt:1143) at com.openvehicles.OVMS.api.ApiObservable.notifyOneUpdate(ApiObservable.kt:73) at com.openvehicles.OVMS.api.ApiObservable.access$notifyOneUpdate(ApiObservable.kt:8) at com.openvehicles.OVMS.api.ApiObservable$NotifyOneHandler.handleMessage(ApiObservable.kt:91) at android.os.Handler.dispatchMessage(Handler.java:106) at android.os.Looper.loopOnce(Looper.java:201) at android.os.Looper.loop(Looper.java:288) at android.app.ActivityThread.main(ActivityThread.java:7924) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:936) Regards, Michael Am 31.12.24 um 12:29 schrieb Michael Geddes via OvmsDev:
The 12v works fine.
This is the othe one which I don't think is available.
//.
On Tue, 31 Dec 2024, 19:27 Developer From Jokela, <info@developerfromjokela.com> wrote:
Not sure about that error. I didn't change that view from old UI, just moved it to new UI. Maybe it's just not supported?
On 31. Dec 2024, at 13.13, Michael Geddes <frog@bunyip.wheelycreek.net> wrote:
That makes sense. It's was fine at topping off level.
Also this is a bit of a weird error here:
<1000012023.jpg>
Ir might be no data? //.
On Tue, 31 Dec 2024, 18:50 Developer From Jokela via OvmsDev, <ovmsdev@lists.openvehicles.com> wrote:
Seems like there was an issue with showing charging time estimations. Patched out in latest commit.
Developer From Jokela <info@developerfromjokela.com> kirjoitti 31.12.2024 kello 11.49:
Hmm, strange. Could you possibly get a stack trace? If it’s too hard, let’s hope I will find it in my own testing :)
- DFJ
Michael Geddes <frog@bunyip.wheelycreek.net> kirjoitti 31.12.2024 kello 4.35:
Font size looks all fixed, thanks.
For some reason when I click on the widget it opens the old look ovms still... is the old look still hidden somewhere?
Also if I start charging my car (not through the app), then whenever I switch to or open the app, the app crashes.
I'm just doing ac charging from a wallbox.
//.ichael.
On Tue, 31 Dec 2024, 06:48 Developer From Jokela via OvmsDev, <ovmsdev@lists.openvehicles.com> wrote:
Hi.
New update is released at https://github.com/openvehicles/Open-Vehicle-Android/tree/test-dfj-ui/latest.
Brief: - Quick actions customisable - Twizy UI fixes - Font size related issues should be gone (hopefully ;D)
- DFJ
van der Meijden, Chris <chris@arachnon.de> kirjoitti 30.12.2024 kello 13.12:
I like the design of the Mercedes Ne app. Don't need a one to one copy, but it has a good mixture between info and links, I think.
Am 30. Dezember 2024 11:29:37 MEZ schrieb Developer From Jokela <info@developerfromjokela.com>:
Hi.
What info would you like to be shown on main screen?
On 30. Dec 2024, at 11.16, Chris van der Meijden <chris@arachnon.de> wrote:
Also many thanks for the effort. The new design is not my cup of tea, but that is question of personal liking I suppose. For me the menu is far to present, whereas the information of the vehicle seems barely visible.
For the e-Up the climate control throws an error. "Fehler bei der Kommandoausführung".
Kind regards
Chris
Am Montag, dem 30.12.2024 um 15:20 +0800 schrieb Michael Geddes via OvmsDev: > Thanks for the update. In general I like the new > design. > > I've attached a screen shot. The list box items > need to resize for larger fonts to stop them > being all cut off. > > Also where does the "Unknown Vehicle model" come > from? > > <1000012000.jpg> > > I have a slightly larger font setting: > > > <1000012001.jpg> > > > > Also here: > > > <1000012002.jpg> > > ..where the labels are overlapping due to the > font size. > > And the ... here: > > > > <1000012003.jpg> > > > I'm also getting a crash when opening the > settings on the map. (App disappears. First time > it prompted to clear cache which I did) > > Is there a new widget? If I click on the widget > I see the old UI. > > //.ichael > > On Mon, 30 Dec 2024, 07:28 Developer From Jokela > via OvmsDev, <ovmsdev@lists.openvehicles.com> wrote: >> Hi Android users. >> >> I’ve recently redesigned UI for Android and it >> would need some testing. >> >> Here is the latest build available for UI >> redesign: >> https://github.com/openvehicles/Open-Vehicle-Android/tree/test-dfj-ui/latest >> >> Please report any issues, improvement >> suggestions, etc. >> >> Thank you! >> >> Br, DFJ >> >> _______________________________________________ >> OvmsDev mailing list >> OvmsDev@lists.openvehicles.com >> http://lists.openvehicles.com/mailman/listinfo/ovmsdev > _______________________________________________ > OvmsDev mailing list > OvmsDev@lists.openvehicles.com > http://lists.openvehicles.com/mailman/listinfo/ovmsdev
<Screenshot_20241230-115518_Mercedes-Benz_1.png>
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926