Requests for Future Improvements with the AL Priority

[Tifosielia]

How about ALP automatically records the last hits pulse train?
That way if one of us gets hit with something that IPT it can be sent to ALP to ensure its covered right away instead of having to go hunt the LEO down again in a special mode.

I'm not sure if ALP has the spare processing power to write the file while its being hit but by far that would be my #1 request.

I worry that certain guns could be updated and IPT at anytime. Does ALP have the ability to see a new pulse train and immediately calculate a counter pulse or does each pulse train have to be loaded into it.
I'm thinking it can work on the fly because DALA is random right? Someone who knows PM me I'm very curious about that.

[Holla]

Keep tuned... Several suggestions in this thread are already on the engineers plates to be implemented this year in future updates.

Hmmmm, that means to save your pennies lol--My wallet is open

[awj223]

How about ALP automatically records the last hits pulse train?
That way if one of us gets hit with something that IPT it can be sent to ALP to ensure its covered right away instead of having to go hunt the LEO down again in a special mode.

I'm not sure if ALP has the spare processing power to write the file while its being hit but by far that would be my #1 request.

I worry that certain guns could be updated and IPT at anytime. Does ALP have the ability to see a new pulse train and immediately calculate a counter pulse or does each pulse train have to be loaded into it.
I'm thinking it can work on the fly because DALA is random right? Someone who knows PM me I'm very curious about that.

For ALP Connect users, it could do even better: encrypt the data, then transmit the file to AL over the phone's data connection. That way, if there were a new gun variant out there, AL could look at the capture files and figure out pretty quickly whether there's a new threat out there. The problem, of course, is if there are too many false alarms, it gives AL a lot of junk to have to sift through.

Then there's another issue: say an ALP gets into the hands of a LEO. A malicious LEO. Someone who wants to annoy ALP users. How about making an ALP transmit the pulse train of something that's not even a LIDAR gun, to cause a lot of users false positives when they update their firmware?

Since there is no way to keep ALPs out of the hands of LEOs, there is no way to prevent this.

[Tifosielia]

Then there's another issue: say an ALP gets into the hands of a LEO. A malicious LEO. Someone who wants to annoy ALP users. How about making an ALP transmit the pulse train of something that's not even a LIDAR gun, to cause a lot of users false positives when they update their firmware?

Since there is no way to keep ALPs out of the hands of LEOs, there is no way to prevent this.

Well I don't see this issue, theres no way for any user to control what the ALP head does, the most we could do is forward the file to AL. And I don't think we should be sending them files all the time, just when one of us gets pulled over and the LEO says he got a lidar reading. you could go home and upload the file to the AL website.... We already upload stat files, why not expand the stat file if possible. Obviously AL could weigh who is sending it in, or more specifically BRD could personally forward them events from those of us who know what we're talking about.

The only reason to not do this is if ALP cant keep up processing wise... like against a Random Pulse Rate gun or something. I know these don't have the craziest processor by any means.

[awj223]

I think one of my requests is very simple: allow the user to reset the statistics. I've got a lot of junk statistics in there from testing, as well as K band falses (from before I turned K band off). It would be nice to just reset everything to zero so that I don't have to compare old and new statistics files to determine what I've been hit by (especially if I JTK before the gun ID is announced).

[BestRadarDetectors]

I think one of my requests is very simple: allow the user to reset the statistics. I've got a lot of junk statistics in there from testing, as well as K band falses (from before I turned K band off). It would be nice to just reset everything to zero so that I don't have to compare old and new statistics files to determine what I've been hit by (especially if I JTK before the gun ID is announced).

The statistics process will be redone in the future. Issue we have is the ALP does not have an internal clock. Adding GPS will enable the ALP more functionality and enhanced stats in the future since it will be able to store location, time and speed. We will also make stats more understandable for non GPS users as well. There is a lot of stuff on the plate for 2015. I know its hard to be patient but every change takes time and every minor change no matter how small requires everything to be tested over and over again.

[awj223]

The statistics process will be redone in the future. Issue we have is the ALP does not have an internal clock. Adding GPS will enable the ALP more functionality and enhanced stats in the future since it will be able to store location, time and speed. We will also make stats more understandable for non GPS users as well. There is a lot of stuff on the plate for 2015. I know its hard to be patient but every change takes time and every minor change no matter how small requires everything to be tested over and over again.

Are you saying that GPS will be standard on the ALP in the future? And possibly even required for advanced statistics?

[BestRadarDetectors]

Are you saying that GPS will be standard on the ALP in the future? And possibly even required for advanced statistics?

No, We would not force anyone into any options. GPS is an option and can easily be added if someone wants it.

[tawwwd]

Cant wait for all the new options hahaha

[awj223]

No, We would not force anyone into any options. GPS is an option and can easily be added if someone wants it.

Looks like I might have to get a GPS in the future though, if it enabled logging of time/location of each hit, that's very cool! You could even have the speed at which you were hit and the speed at which the JTK occurred.