ZR4-Blinder M47-LI-ALP for me...Quote:
Originally Posted by RedRocket
Printable View
ZR4-Blinder M47-LI-ALP for me...Quote:
Originally Posted by RedRocket
I will dive :
blinder m-27 \ G 7 \ Lpp \ Li \ Al top Priority
The G-7 was directly bought from Croatia.
It took a while before the rear protection became a necessity ...wonder how leos learned
that they could shoot the rear ?
if I remember correctly the G7 was a duel head system only ,,the LPP is the clone from the G7 and G8Quote:
Originally Posted by Tman
I remember years ago seciurity gear hear in perth saun use to run it at that time ,,I think saun is here somewhere on the forum ,,but now he is over in the US ,,he once try to sell me a LPP and said that I would be upgrading my AL G8 ,,lucky for me I had my homework done and stuck with my AL G8
I got the lpp from saun Dgc, worked ok but they filled with water badly, sadly didn't know of any forums then
I never notice that the G7 was dual only.
I bought the Lpp from Alex in Vancouver , was easier for shipping cost + customs.
I switched to Li when the Truspeed arrived ...Lpp took a good year to find the solution.
It is me as Suave :
http://www.kmph.ca/forum/viewtopic.php?f=6&t=547
Quote:
Originally Posted by deano
like I say mate the LPP was a copy from the G7 and G8 ,,my G8 also did not jam the truspeed ,,unless there was an update that I never knew about ,,Quote:
Originally Posted by Tman
what amazed me more was at the same time owning the G8 I also purchased a conqourer M18 i picked it up for $100 ,,this infact did jam the truspeed , ,,what pi$$ed me off was that on purchase I got told it was future proof,,i never seen one update for the G8 and by then the G9 came out making the G8 useless ,, so much for a future proof jammer ,,,then the G9 rx came out another future proof jammer then the ALP ,,after my experience with jammers im guessing when it says future proof we only expect 3 to 4 years max,, am already guessing AL are working on a new product this keeps them ahead in the game
i will say BIG thanks to denise from AL he did send me out a free G9rx sample to test ,,for promoting there previous jammer the G8 on utube ,,, other wise i would of gone LI when the AL G8 became out of date as new guns did get introduced like the truspeed and poliscan..also when the first G9 came out this did not also jam the truspeed ,,until updates
1) Updating the ALP in some way where it's capable of running both the BT module and a traditional/hifi control set would be nice (or at some point a combined module). May kind of be a moot point with the graphical display though (assuming it's visible and not distracting). For laser the LED display is helpful (unfortunately not installed in my car yet due to mounting location issues) but for ALPConnect with current Apple iOS bluetooth issues, disconnecting and not getting alerted is problematic.
As far as why a combined bluetooth/control module setup would be nice, GPS without GPS antenna (which can be kind of unsightly) and logging of the alerts, plus it's a graphical display of sorts that can easily be removed from the car. If the connection dropped for any reason you still have the hifi system to loudly provide the alert.
2) Settings controls in the ALPConnect app rather than website + USB being the only way. From what I see earlier in the thread, first was iOS and stabilization of core features, then they targeted getting ALPConnect on Android with feature parity. Now that ALPConnect is out on Android perhaps this could be reexamined.
3) Firmware updates through ALPConnect would be a nice touch, although not as nice as the settings changes. I know Escort can do this through EL. I understand that ALP is a totally different product from a different company and the way the CPU was designed may not permit this.
Keep tuned... Several suggestions in this thread are already on the engineers plates to be implemented this year in future updates.
Will GPS radar lockout ever be possible through ALPConnect?
I know Fleming is litigating against Escort/Beltronics, but he appears to be doing so on the basis of radar detectors with GPS units actually built into them that handle the GPS logic and decision to lock out, and his patents seem to express similarly. From what I've been able to find, he hasn't sued the makers of the YaV1 app (granted, the developer of the app doesn't work for Valentine, but it does enable the Valentine1 for GPS lockouts), and I also haven't seen Escort Live or Escort Live capable (but non-GPS) radar detectors named in the suit.
I'm not an IP lawyer though, and I know it's a bit of a sensitive topic.
Cant discuss this at this time... SorryQuote:
Originally Posted by nydriver
Also remember that I am also a user and when you guys think of something that would make the ALP better, As a user myself I have most likely already thought of the same thing and most likely AL is already working on it but keep em coming. :)
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.
Hmmmm, that means to save your pennies lol--My wallet is openQuote:
Originally Posted by BestRadarDetectors
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.Quote:
Originally Posted by 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.Quote:
Originally Posted by awj223
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.
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.Quote:
Originally Posted by awj223
Are you saying that GPS will be standard on the ALP in the future? And possibly even required for advanced statistics?Quote:
Originally Posted by BestRadarDetectors
No, We would not force anyone into any options. GPS is an option and can easily be added if someone wants it.Quote:
Originally Posted by awj223
Cant wait for all the new options hahaha
https://imgflip.com/readImage?iid=21680670
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.Quote:
Originally Posted by BestRadarDetectors
BRD is V1 integration still on the table/any idea how far it would be if so?
Its on the table for 2015 but I dont have an ETA. SorryQuote:
Originally Posted by Tifosielia
Great now i am going to have to make more room for this gadget under my dash :) im in on this when it comes outQuote:
Originally Posted by BestRadarDetectors
I really hope this is on the roadmap. This is one feature I would happily pay extra for. Perhaps it could be offered as an optional 'in app' purchase if some profit sharing agreement could be worked out with the patent holder?Quote:
Originally Posted by nydriver
Got a really, really simple feature request. On the Hi-Fi Control Set, when the female voice announces Ka band, it slurs the last part of "Kay" and first part of "ay" together, which makes it much harder to distinguish from the K band. Yes, I've identified the alert sounds and can easily tell which is which, but other people who haven't heard these alerts yet might not be able to distinguish so easily.
How about making the voice sound more like the voices on the Redline and STiR+? As in "kay <pause> ay band"?
I didn't test the male voice to see if it has the same issue.
I would absolutely love it if ALPConnect included 'dash cam' functionality.
My windshield-mounted iPhone plays dual-duty as I drive-- in the foreground I'm running a dash cam app that records the road in front, and in the background I'm running ALPConnect. Problem is when I get an alert on ALP I have to switch apps to silence it and then switch back again to resume the dash cam.
ALP Feature's I would like to see added :)
-I wish a laser alert would get GPS tagged on the phone, So it could remind you 1mile of the enforcement zone next time you drive that road.
Similar to Trapster, but ALP and local to the phone
-LID count-down timer when being hit with laser
-Be able to disable radar alerts and still have laser alerts
-ON screen compass
This request is for a change to the Lidar Gun Model I.D. for the HiFi Voice option in the "Detailed" selection choice:Quote:
Originally Posted by BestRadarDetectors
As it is highly unlikely today that users will encounter a ProLaserII anymore in North America, the I.D. should be changed to LaserAtlanta !
Except CRM in Georgia ran into one not too long back on the RDF :)Quote:
Originally Posted by RedRocket
Requests? Ability to make changes via iOS user interface. :fat:
While that is a rare exception...which one are you far more likely to encounter today ?Quote:
Originally Posted by Jaguar
Making setting changes and firmware updates is already scheduled for Q3.Quote:
Originally Posted by wirelessandy
Has AL any plans yet to give Poliscan its own LID time, so it can be set higher than the handhelds for auto JTK.
This would ensure anyone running higher LID time does not accidentally JTG a handheld cause they have it set high for Poliscan
Also a Record&Detect mode so it will give alarms and record unknown and alarm to real
We have discussed both these suggestions.. The 2nd one would require changes to hardware but the first might be done in the future.Quote:
Originally Posted by shanetrainST
While this would be a nice feature, in a practical sense, I'm not sure it would be good to have. Remember, the goal should be to JTK as quickly as possible at all times. Unless the automated camera alerts sound completely different from the alerts for normal LiDAR guns (for example, by using a sound other than the siren noise used for the regular guns), such a feature is likely to lead to accidental JTG mistakes in the real world.Quote:
Originally Posted by shanetrainST
It already puts the driver in a sort of stressful situation when he or she gets an unexpected alert and must quickly brake and JTK ASAP. This adds yet another layer of decision making to someone under stress, which is not a good thing.
I wouldn't mind an alert sound for PoliScan that differs from a regular gun, given that Poliscan alerts tend to be either more urgent in nature (if you live in a Poliscan area) or more nuisance in nature (if you live here) than other alerts.
Yea, in essence you have to JTG a Poliscan to ensure successfully jam, if you kill to early and your in its detection zone, you get fined.. Would you take that risk???Quote:
Originally Posted by awj223
This is why it needs to be separate away from handhelds as the method required to jam it differs from a handheld
+1
time to rebait the hook
remember guys the poliscan only has min of 15 metres max 75 metre range
from my experience ,,,some cases its all over within the first 2 seconds thats both front and rear facing
hmm that shoots the earlier remarks, so we dont want to long jam time so lets get this right , only u guys over there has the experience to nail this