garmin R10 not detecting shots from woods and driver

Its very unlikely that a driver will read more than 150 using almost golf balls.

You can check the ball speed, it will probably be 100-110 mph compared to 130-150 using real golf balls (depending on Your club speed).

My normal club speed is approx 90 mph which gives a ball speed of approx 130 mph, and carry of approx 200 yards.

Ball speed of 100 should be 60-80 yds shorter distance, and thus the almost balls will result in a carry of approx 120-140 yds for me.

Probably on the low end as low launch angle and low ball speed will not give a great carry.

Same issues for me. I use mine outside with a net.  Mine used to read drives almost 99% of the time,  now, sometimes it only picks up about 40-50%. It's kind of hit or miss, sometimes it will read 10 drives in a row then only read every 4th or 5th drive.on the next 30-40 shots.. Note, this is only with my driver (swing speed 85 MPH/ Ball speed 120). All other irons (p -3), hybrids  and fairway woods are still read 99% of the time.

Having the exact same issue.  Mostly has problems in Awesome Golf though.  It will work flawlessly for 15 shots then I will miss the next 5 shots, reset, move the garmin closer or back further, check alignment, etc. It's extremely frustrating when you are playing well and in the zone and you flush 3 shots in a row that don't register then shank one and of course, it reads that one.  Without a doubt, it seems like it always reads the worst-struck ball of multiple attempts.  I do not have nearly as many detection problems in HTH or E6 connect.  (although HTH does not seem as accurate) I was wondering if a software update forced this because it was extremely reliable up until late. 

Any fix for this? My friend tried to hit some shots. Iron were fine but almost none of his dribers were caught - or he had a dsiplayed Club head speed of 160mph!?..

Measure the distance from R10 unit to ball, and enter same distance in the app. This has to be accurate, and I would not go lower than 7 feet (2,1 m).

That is the issue..

I actually carry chalk and a 7ft string with me to Mark the hitting Spot + distance to the r10.

Trying to Set it up perfect so it cant be the Setup - I would say. Surface is flat, so also no Hight difference 

Tried Lifting the back lag, also no sucess

Your problems could be addressed in this post:

https://forums.garmin.com/outdoor-recreation/golf/f/approach-r10/314104/r10-not-picking-up-driver-and-woods-this-is-why

Quicken your your backswing and/or don't pause at the top