Speedtrap Alert for Android (Split from CamerAlert Thread re

Kremmen · Posted: Mon Dec 16, 2019 5:03 am Post subject:

Works perfectly OK via BT and exactly the same as CA in that respect.

It automatically fires up when it detects a BT connection and shuts down when the connection is lost. Both the auto start and stop are individual options.

Given the Specs banner issue, pending a CA update or a MaFt bespoke database I'm going to disable the banners. Don't need them, just the announcement of cameras.

What I haven't tested yet is the overspeed warning as I don't exceed 50 in the roadworks.

Next trip probably Wednesday but definately Thurs.

The second set of Specs near Maidenhead I just lift off the go pedal so CA does give me a couple of warnings until cruise control has me down to Satnav 50, just in time for the first camera. I'll do the same and see what happens.

I'm expecting a series of beeps. What would be nice is an overspeed alert option using TTS so you can your own warning.
_________________
DashCam:
Viofo A119 V3

M8TJT · Posted: Mon Dec 16, 2019 9:31 am Post subject:

The overspeed warning is a continuous series of beeps. Bit of a pain. I have raised this with Leo.

Kremmen · Posted: Mon Dec 16, 2019 12:17 pm Post subject:

He's cracked text to speech so he should be able to give us a free hand in what warning we want.

"Get that right foot off the loud pedal" (polite version)
_________________
DashCam:
Viofo A119 V3

MaFt · Posted: Mon Dec 16, 2019 1:35 pm Post subject:

MaFt · Posted: Mon Dec 16, 2019 1:37 pm Post subject:

MaFt · Posted: Mon Dec 16, 2019 1:40 pm Post subject:

Another app that I find useful is Velociraptor - it overlays the current road speed on your map/app. You can either use free data from Open Street Map or there are paid options to use TomTom's road speed data.

Kremmen · Posted: Mon Dec 16, 2019 1:44 pm Post subject:

I was hoping, subject to PGPSW being happy with a CA competitor, taking the current:

iGO [UK - Single file with all cameras]

and create a new database maybe:

SpeedTrap [UK - Single file with all cameras]

The only difference would be an extra column.

So Specs camera 202920 would change from:

-0.49636,51.49468,4,50,1,269

to:

-0.49636,51.49468,4,50,1,269,End

Other Specs cameras would be terminated with Start and/or Middle

I guess it doesn't have to be "End" but anything that can be picked up

(1,2,3) (S,M,E)

Whatever is easiest.
_________________
DashCam:
Viofo A119 V3

MaFt · Posted: Mon Dec 16, 2019 1:52 pm Post subject:

It's not really a competitor - CA is free. The access to the data would still be via a paid subscription - there's no difference to installing the database onto a Garmin or TomTom.

The only issue really is being able to submit new locations or verifications from a different app.

Leo_A · Regular Visitor Joined: Jan 10, 2017 Posts: 156

M8TJT · Posted: Mon Dec 16, 2019 2:18 pm Post subject:

Ignore this as Leo_A is on the scene, so take his word as gospel. But perhaps the bit in bold would be good.
The only thing that SpeedTrapAlert needs as far as SPECS is concerned is a marker to indicate the last in a series. This could be done as Kremmen suggests by another column, or as you suggest that you might be creating a separate database similar to the iGO .txt one, then it could be just to change the camera type from 4 to (say) 6. It does not require Start and Mid info.
What the app does is start and display the average calculation at the first SPECS, then resets the calculation on each subsequent camera. This of course leaves the calculation 'hanging' when you pass the last in the sequence.

It would also be extremely useful to include our dummy end specs as another category to 'perfect' the SPECS experience by cancelling calculation when you turn out of a SPECS zone as I know Leo is scratching his head about what to do if you leave a sequence 'in the middle'.

The developer 'tinkers' with the database a bit when it's imported to STA to get it into the format his app uses.

His codes for SPECS is Start = 10010 and End is 100011. He also has code 10030 for "fake speed camera" (Our dummies?)

M8TJT · Posted: Mon Dec 16, 2019 2:20 pm Post subject:

Hi Leo. Welcome to PGPSW foryms.
I think Kremmen and I have raised a bit of interest in STA here.
Thanks for the Time to cam mod in the beta.

Privateer · Posted: Mon Dec 16, 2019 2:41 pm Post subject:

Hi Leo_A,

to the forum! Thumbs Up

The ability to know END and Exit SPECS would be useful.

Could you speak with MaFt about allowing direct download of the database to your App, obviously handshaking with PGPSW security?

Could you also speak with MaFt about using the verifier database and also and K and M about adding tools for verifiers such as adding notes etc?

Finally, could you produce an iOS version? Wink

Regards,
_________________
Robert.
iPhone 6s Plus, iOS 14.0.1: iOS CamerAlert v2.0.7
TomTom GO Mobile iOS 2.3.1; TomTom (UK & ROI and Europe) iOS apps v1.29
Garmin Camper 770 LMT-D

Kremmen · Posted: Mon Dec 16, 2019 2:46 pm Post subject:

If this takes off then it will take the pressure off CA for those of us with Samsung phones either with or with the threat of Samsungs Android 10 (Q)

SpeedTrap has got lot's of potential and given we have been running CA and PND's for years with PGPSW data we have some experience to pass on.
_________________
DashCam:
Viofo A119 V3

	PocketGPS
	Web