LapTimer v20.1 announcement (iOS and Android)

All announcements that are outdated are moved here.
User avatar
Harry
Site Admin
Site Admin
Posts: 8989
Joined: Sun Sep 12, 2010 10:32 am
Location: Siegum, Germany
Has thanked: 98 times
Been thanked: 378 times
Contact:

LapTimer v20.1 announcement (iOS and Android)

Postby Harry » Tue Sep 27, 2016 1:21 pm

Dear friend of LapTimer,

I plan to release LapTimer v20.1 for both iOS and Android in about a week. Please find a heads up on the changes you can expect below. The reason I post early on this update are the changes on technical level I had to apply. Especially for Android, the development tool chain has been replaced by Google's latest technology. As LapTimer is a very complex product, an update like this may introduce unforeseeable problems not detected during our extensive testing. So in case you install 20.1 early, please watch out for issues and report them back! In case you are risk averse, please wait a week before updating ;-).

Changes in version 20.1

This release includes new functionality, bug fixes and other improvements.
For both Android and iOS, this version includes significant changes on technical
level. Although we did extensive testing, the may lead to unexpected behavior or
instabilities. Please report any issue you see!

New functionality

‣ Added speed based Performance testing support [GrandPrix]
    new Performance View
    performance recordings show speed chart by default
    adjusted reference handling
‣ Added an Expert Setting to increase bitrate for hardware accelerated overlays [Android]
‣ Added check for updated store version - prompts user to update
‣ GPS View starts up with current status (instead of last / top)
‣ Simplified Settings (e.g. removed Stop/Go Mode)
‣ Improved horizontal acceleration gadget to show longitudinal acceleration if dominant
‣ Added a video distribution function (e.g. to Gallery, Photos, YouTube) [Android]
‣ Improved Data Recording Preview [iOS]

Compatibility improvements

‣ Improved compatibility for Android M [Android]
‣ Migrated development tool chain to Android Studio [Android]
‣ Improved iOS10 compatibility [iOS]
‣ Fixed WiFi sensor connection for iOS10 [iOS]
‣ Fixed Load Track assistant for iPads / iOS10 [iOS]

Other bug fixes and improvements

‣ Added Samsung S5 default plane offsets [Android]
‣ Fixed missing gadget dimming and coloring for best / last [iOS]
‣ Improved localizations
‣ Improved selection of views in Drawer menu [Android]
‣ Fixed sound initialization (beeps and ticks) [Android]
‣ Fixed lap index numbering in Lap Information dialog
‣ Remove tracing for LapTimer (will be done using Buddy in the future) [Android]
‣ Improved detection of manual and automatic laps
‣ Fixed a rotation issue
‣ Fixed Speed Chart configuration dialog
‣ Fixed crash when sending trace logs, renamed "log" to "trace" in general
‣ Fixed display of GPS speed in Speed Charts [Android]
‣ Fixed layout of Export dialog [Android]
‣ Improved Status Gadget layout [Android]
‣ Improved interpolation routines and data storage
‣ Improved VBOX Sport integration [GrandPrix, iOS]
‣ Improved BT1A integration [Android]
‣ Fixed a minor bug in Bluetooth Low Energy sensor detection [iOS]
‣ Fixed a bug in editing checklists [iOS]
‣ Fixed transfer of overall distance for Hall of Fame entries [Android]

Thanks for your support,

- Harry


Image Image Image Image
ereynold60
20 or more Posts ★★★
20 or more Posts ★★★
Posts: 47
Joined: Fri Mar 13, 2015 9:31 pm
Been thanked: 1 time

Re: LapTimer v20.1 announcement (iOS and Android)

Postby ereynold60 » Sat Oct 29, 2016 9:16 pm

What is the implication of "LG G3 being blacklisted for NMEA" in the v20.1.3 update? I have an LG G3, but I use an XGPS160 at 10Hz. How will I be affected by the 20.1.3 update?


User avatar
Harry
Site Admin
Site Admin
Posts: 8989
Joined: Sun Sep 12, 2010 10:32 am
Location: Siegum, Germany
Has thanked: 98 times
Been thanked: 378 times
Contact:

Re: LapTimer v20.1 announcement (iOS and Android)

Postby Harry » Sat Oct 29, 2016 9:28 pm

No impact.

The problem is with the LG G3's internal GPS. It looks like the NMEA stream generated by the LG is often corrupted. Probably some buffer overflow. LapTimer uses the NMEA stream usually instead of Android's location service. It comes with more details. This is where the black lists hits in. For black listed devices, LapTimer will use the Android location service instead of accessing NMEA.

For external sensors, the black list is not relevant. LapTimer will use the XGPS's NMEA stream as usual.

- Harry


Image Image Image Image

Return to “Outdated”

Who is online

Users browsing this forum: No registered users and 2 guests