stagpanther
New member
I don't even bother with the phone ap--maybe that's why I have no issues with it. ; )
Labradar
- Thread starter Brutus
- Start date
Doublehelix3216
New member
I should have been more clear and said "It works *FOR ME* 100% of the time".
That sucks that you are having problems, and I hope somebody figures it out. I agree that for a $600 device, the app needs to work with everyone, especially Samsung and Apple, who are the top two selling devices in the world.
I am now using a Google Pixel 2XL (as of July), but had a Samsung S7 Edge previously, and it worked fine on that phone as well. When it was first released, I had a heck of a time getting it to connect to the Samsung, then they upgraded the firmware, and everything was fine. With the first release, I had to try to reconnect over and over again, and sometime I could get it to connect, and other times I would give up after about 10-15 tries.
They just released a new firmware update in the last week or two. Did you try that one as well? I upgraded even though I was not having issues. (This is a Labradar device firmware upgrade, not a new version of the app.) I think this is the 3rd (or maybe 4th???) firmware upgrade since the release of the app.
I am pretty sure this is a hardware device issue, not an app issue. Maybe an older BT chip or a non-standard chip???
I personally love the app. I can arm from the app rather than the device, and see the data displayed much more easily from my phone than from the device. I like being able to review the data on my phone, etc.
It is also interesting to note how long it took them to release the app and the BT functionality. They promised it over and over again for well over a year before it finally saw the light of day. They were obviously having issues with it for a long time.
Hope you get things working soon.
@Doublehelix
Yeah I am running 1.2.3 rolled it back to 1.1.5 just to see if that helped, it did not. Reinstalled 1.2.3.
As long as the SD card gets the data I will just operate it on the unit like most of the people here do. I just find it irritating and my first impression of Labradars CS is that it sucks.
I am glad I bought mine from Brownells so that if I have any serious issues I won't have to deal with the distributor again. I got the impression that he doesn't really give a damn if it works or not and will find a way to blame something other than the product if it fails completely
Yeah I am running 1.2.3 rolled it back to 1.1.5 just to see if that helped, it did not. Reinstalled 1.2.3.
As long as the SD card gets the data I will just operate it on the unit like most of the people here do. I just find it irritating and my first impression of Labradars CS is that it sucks.
I am glad I bought mine from Brownells so that if I have any serious issues I won't have to deal with the distributor again. I got the impression that he doesn't really give a damn if it works or not and will find a way to blame something other than the product if it fails completely
stagpanther
New member
Really? When I call the US rep guy up I usually have trouble getting him off the phone after getting the information I need--and then some.
The reason I said that is because anytime a CS rep says oh our product is fine it is just that the Samsung and their bluetooth low energy mode that the problem it grates on my nerves. SAmsung has 25 % of the market in the USA. Ir seems the Labradar has problems connecting with some Apple phones, that is another 50 % of the market. That's a lot of devices to have problems yet the Labradar is not at fault .....right
That same Samsung bluetooth energy has no issues connecting to my cars hands free mode the remote speaker on my deck, my smart TV, my sound sytem amplifier or any of half a dozen toy drones which use a bluetooth controller.
I would preferred he just been hones and said , our firmware is a work in progress and at the moment it sucks for some users. I appreciate honesty.
The second reason I don't get a warm fuzzy from the guy is I asked him if he would like to participate in the thread on Accurate Shooter on this topic as a lot of manufacturers do. That way he could have addressed these issues not just for me but several other purchasers and potential purchasers. Reps from half a dozen companies participate in the forums and yes sometimes they get blasted but they hang in there fix their problems.
Sorry but this guy isn't RCBS or Hornady or even Jeff Block at On Target Software, that guy helped not only fix a problem he spent another 15 min on the phone giving me tips and pointers on the software and made sure I understood every item on the menu and how it worked .
That same Samsung bluetooth energy has no issues connecting to my cars hands free mode the remote speaker on my deck, my smart TV, my sound sytem amplifier or any of half a dozen toy drones which use a bluetooth controller.
I would preferred he just been hones and said , our firmware is a work in progress and at the moment it sucks for some users. I appreciate honesty.
The second reason I don't get a warm fuzzy from the guy is I asked him if he would like to participate in the thread on Accurate Shooter on this topic as a lot of manufacturers do. That way he could have addressed these issues not just for me but several other purchasers and potential purchasers. Reps from half a dozen companies participate in the forums and yes sometimes they get blasted but they hang in there fix their problems.
Sorry but this guy isn't RCBS or Hornady or even Jeff Block at On Target Software, that guy helped not only fix a problem he spent another 15 min on the phone giving me tips and pointers on the software and made sure I understood every item on the menu and how it worked .
stagpanther
New member
My unit tends to get buggy when the power level is low on the battery.
I keep not just one but two fully charged power banks with me when I go to the range now. My target cam application eats the battery on my tablet like it is a appetizer so now I have two reasons to carry power banks. Twenty bucks for a power bank is cheaper than a case of Duracells. I tried rechargeable AA's but they did not last an hour.
in my opinion Labradar 2.0 need three improvements
1. a better aiming system
2. ditch the AA's altogether and include a replaceable Lipo instead
3. A completely redesigned device application with better design and can connect.
Ever see a CE chrono using Digital Link? Labradar should shamelessly copy it's menus and options, that ap rocks with the exception of data export. It mangles data, I used to hand input the data from the ap rather than export it and try and unjumble it. Labradar needs to keep the SD card just as it is, that is the best part of the system so far for me and the real reason I am not returning it. As long as it has good data on the SD I can retro fit the other items.
Last edited:
Doublehelix3216
New member
Yeah, that does suck. I have heard from others about the arrogance of the LR team in general, although I have never experienced it in person. Customer service and attention to detail are the two most important things in keeping customer loyalty, and it sound like they have failed in both areas.
I have always said that someday soon, maybe after patents run their course, LR will have competition. Someone is going to do it better and cheaper, and then we will see who the arrogant one is.
I hope they get things worked out for you. As I mentioned earlier, I am 100% satisfied and happy with the product, but it does not make me proud when I hear how they are treating you and others.
I am not going to copy a personal email exchange onto a forum board but suffice to say my experience was completely different than yours. Of course I realize that this guy cannot fix what is essentially badly programmed software. However a simple "we are aware of this issue and are working on a new version" would have been nice to hear.
made a little case for mine yesterday afternoon. It had a padded interior, a removable tripod head, and enough extra storage room inside to hold the tripod head, 2 power packs and the USB cord. I used one of the tips provided earlier in the thread and attached a small piece of velcro to the outside of the case and each power pack to secure the pack to the case to prevent them from falling.
It is certainly not jewelry box quality but considering pretty much everything including the hardware came for scraps left over from old projects I am not going to complain. It is really sturdy and stable for use on a bench or shooting pad. The tripod head (Amazon $20) was purchased for the project allows easy adjustment and is really stable when locked in
Just for grins I tried to connect using the Samsung 6 and it connected 5 times in a row. No firmware on either the Labradar or the phone has changed since I last tried to connect. Go figure
I will still operate it without the ap just to be safe.
It is certainly not jewelry box quality but considering pretty much everything including the hardware came for scraps left over from old projects I am not going to complain. It is really sturdy and stable for use on a bench or shooting pad. The tripod head (Amazon $20) was purchased for the project allows easy adjustment and is really stable when locked in
Just for grins I tried to connect using the Samsung 6 and it connected 5 times in a row. No firmware on either the Labradar or the phone has changed since I last tried to connect. Go figure
I will still operate it without the ap just to be safe.
Last edited:
I'm at a (mostly) .50 BMG match this weekend. One guy has a new labradar.
He's having similar problems that I did getting it to trigger on the BMG rounds. Acoustically, I'm confident it's an incredibly loud round.
Anyway, I'd hope labradar is reading this. We discussed it might be a really poorly and incorrect manual (which is max sensitvity: 1, 5 or 8 (the manual says the range is 1-5, the labradar goes to 8)...
It's a great idea but either the user manual and interface (inhales like a serious vacuum) or there's some technical problem with the unit that labradar either can't figure out or is blowing it off.
He's having similar problems that I did getting it to trigger on the BMG rounds. Acoustically, I'm confident it's an incredibly loud round.
Anyway, I'd hope labradar is reading this. We discussed it might be a really poorly and incorrect manual (which is max sensitvity: 1, 5 or 8 (the manual says the range is 1-5, the labradar goes to 8)...
It's a great idea but either the user manual and interface (inhales like a serious vacuum) or there's some technical problem with the unit that labradar either can't figure out or is blowing it off.
I am going give mine a workout at the range next week. 2 trips planned , one center fire and one rimfire. I am going to try out the carpentry square trick for aiming and when burning some rimfire try arming and disarming with the ap to see if it drops out in the middle of strings. Assuming it is in a mood to connect that day.
I think the foundation of this unit is solid but on firmware and ap wise it is weak. Good news is software is easily fixable if they get some knowledgeable programmers to write good code.
I think the foundation of this unit is solid but on firmware and ap wise it is weak. Good news is software is easily fixable if they get some knowledgeable programmers to write good code.
stagpanther
New member
From the manual: "THE LABRADAR SHOULD BE PROTECTED FROM LARGE CALIBER WEAPONS WITH MUZZLE BRAKES. PLACE A BARRIER BETWEEN THE MUZZLE AND LABRADAR TO PROTECT THE SYSTEM."
What kind of error was your friend getting? Was it simply no data returned--but triggered--or did he get a white screen that basically said failure to acquire? Or did it just sit there with nothing happening at all?
I've never shot a 50 bmg--though I do have a few "big bangers" that can rock the unit with muzzle blast if placed too closely. When I first got my system I initially had frequent problems getting the unit to work--mostly due to my "getting a feel" for the appropriate positioning of the unit relative to the muzzle blast that is emitted from the weapon. The pressure wave from the muzzle blast--especially sideways/rearward ported brakes-- can be enough to "overwhelm" the unit if placed too closely.
Kinda --but at the hardware level all the unit is doing is emitting the doplar beam and "waiting to be told" it needs to acquire the flight of a projectile and track it.
I leave my unit set to "internal trigger" 12" projectile offset and trigger sensitivity 1 and it almost always works for every firearm as long as I get the relative positioning of the muzzle right. I haven't tried the external trigger connector cable input yet--maybe something like would help in the case of things like the 50 bmg.
I think I did use it once to track 17 hmr--but small fast moving bullets can be "dropped" so that the velocity distances reported don't make it out to 100 yds.
Last edited:
I was very pleased with the Labradar itself today. I tested it with the .260 tactical (w/o brake) and .223 today. I put the unit 12 inches to the left of my barrel and 12 inches behind the muzzle. I used my home made peep sight and aimed down my row of flags. All settings were default except for units of measure and rifle mode. I fired and recorded 60 shots total with no errors or missed shots. You can't ask for better than that.
Android ap started out working but crapped the bed at around the 40 round mark. I was arming and disarming between strings when it happened so no data was lost
Labradar has it's warts but if you want good reliable data and don't mind a bit of a learning curve it is the only game in town.
Just my opinion of course
Android ap started out working but crapped the bed at around the 40 round mark. I was arming and disarming between strings when it happened so no data was lost
Labradar has it's warts but if you want good reliable data and don't mind a bit of a learning curve it is the only game in town.
Just my opinion of course
Last edited:
stagpanther
New member
Ah grasshopper; and there you have it.
I'm a bit surprised you got it to acquire the bare muzzle (especially a 224) that much forward of the unit since typically device-less crowns send most of their report wave forward.