Lean angle issue? Calibration / Landscape Orientation

[architect]

I'm using an external Qstar 818XT GPS for my OnePlus One (custom ROM).

I notice my lean angle data is all off. It would all be in negative for the entire lap, or simple be wrong (max of 10 degrees lean). I'm using the "motorcycle" preset calibration. I'm not sure if I should calibrate instead or what's making the lean data wrong. I have mounted in landscape orientation almost flat (slight tilt up so I can see the screen).

Thanks! Great app.

[Harry]

The tilt needs to be 70 degree (90 is flat). As lean is derived from downforce measured, it is pretty sensible to even slightly wrong adjustments. It is best to verify you get a 0 for acceleration values when standing still. In case values shown are outside -0.05 and 0.05 G, please readjust.

In case it doesn't work, you have the option to calculate lean from GPS. Select a lap from Lap List, press Recalculate and Acceleration afterwards.

Harry

[architect]

Thanks. I'll use the "Acceleration" View to make sure the mount angle gives me a 0 in forces. I thought maybe the software couldn't tell that it's in landscape mode or something.

Second issue:

In all my lap details, the GPS sensor shows 1.0 Hz. However, I double check that my GPS is in fact connected and working via the GPS view and it clearly shows 5 Hz. I'm not sure why that is the case. Thanks.

[Harry]

Maybe you lost the connection to your external GPS while recording. Try again. Instead of trusting the Hz calculation in Lap Details, you may just divide the number of fixes by the lap's time in seconds. Calculating is a bit more complicated as it might seem initially as recordings can be compressed....

- Harry

[architect]

If I look at the LapTimerGPSRecDB, I'm getting only 1 fix per second.

I've tried the app on two different trackdays and same result on all laps.

Not sure how to trouble shoot this. Is there a way to disable/disconnect from the internal GPS just to see? Thanks for the help.

[Harry]

Please send a snapshot of the GPS View with the Qstarz connected. There is no reason it should not go to the database except the system is completely overloaded. You may try your configuration for a genuine Android installation to make sure there is no compatibility issue. Please make sure you have no GPS helper app active in addition.

Harry

[Harry]

Please add your complete system configuration too.

[architect]

I have attached the screenshots. If it means anything, if I switch away from the app and back into it, the GPS is disconnected and need to reconnect again. But I obviously don't do that when Ive set it up and riding.

[Harry]

Ok, this looks fine. What is your system configuration? Android make / model and android version? Next step will be to enable manual timing in LapTimer's Settings and create a short test run: with the sensor connected, start recording manually in Timer View. Drive a minute and stop again. Check GPS is still at 5 Hz and check the recording's update rate.

Please confirm you have disabled GPS helper apps too.

When LapTimer is sent to background it will always close all connections and sleep.

Harry

[architect]

Exodus Rom, Android 5.1.1, Phone Model A0001 (Oneplus One)

GPS helper apps are disabled (don't have one installed)

I have tried the manual timer test: Checked GPS view to show QStar at 5hz and then recorded down my street. However, it still shows 1Hz in lap details. You can see that it shows 179 fixes over 3 minutes (1/second).

With the Lean angle issue:

In Acceleration View-- even when after configuring properly in landscape view, as soon as I exit the view and immediately return, it defaults to portrait and the acceleration is all screwed up for a bit. I have to move the phone around again until it changes back into landscape mode. I am thinking that when I start recording, the app thinks it's in portrait mode still? The screenshot shows the map AFTER I have fixed the acceleration using GPS data.

Thanks.