The edge 1040: An absolute disaster of bugs

Since i work in IT for a few years, i could tell, that complexity on the inside of software is often way way higher, then i seems.
But doesn't mean, that QA isn't important.

For example the sync problem: i have 4 rides synchronisated today (i think most via bluetooth on Android) without any problems. Which appreared on connect the moment i pressed safe. That could be a very specific problem to your wifi e.g. (when i had the fenix 5 i couldn't sync via wifi with the router from my isp. When i bought avm hardware it worked out of the box. Don't know why until today).

The sensor drop is an issue with a iq-field (there is another thread). That is a issue I can't understand, because without knowing the softwarte i would suggest, that iq apps only read data and that the rest of the system is running more or less in a sandbox, which just deliveres date. But somehow there is either a way, that iq-apps interfere with the os itself or the os has a bug with drops sensors, when data is delivered to iq-apps.

Since that is a really big bug, i would suggest to deactivate all iq-fields and apps temporarly and see if the other issues are fixed then.
When i had iq-field activated i change datafield, but when i changed to the map and back the field was changed back (changed one from distance to time). So it seems, like the iq features results in multiple mistakes.

Just to get me right. That IQ-Problem shouldn't exist in my opinion and i don't understand how that could pass QA, since it really is a core feature and not some special thing only a handfull of people use.

For Feedback Reasons:

• Random crashes (none for me)
• Random freezing on pull down menu (none so far)
• Refusing to sync rides today, WIFI and Bluetooth.  (no problems)
• Doesn't correctly show charging, when it is (works fine so far)
• Strava segment pops up even when set not to (not in use by me)
• Segment plays you lose sound when you exit or ride past it (didn't made segment today)
• If stopping activity on a segment, the summary map shows the segment, not the ride you did (no segment today)
• Di2, doesn't play tones for chainring shift next (no Di2 :( )
• Can't remove daily suggested workouts (no suggestions, since no vo2 max so far)
• ALL sensors dropped a few seconds into ride and wont reconnect no mater what i do (will have to try factory reset) (iq-problem)
• Sometimes really slow on front screen (can't relate so far)
• Twice now ive come to turn it on and its refused, having to hold the button down 30 seconds to get it to wake up. (always gets live when pushing for a short moment)

The latest version of the sdk is dated June 8th and says the 1040 devices are supported.  It looks to me like the Sdk is out but may have been just recently released.  If Garmin changed something in how the apps communicate to the sensors via connectiq, you would think it would behoove them to release the sdk earlier than later so developers have time to work on their apps to make a seamless transition but the problem could in be connectiq itself too.   Time will tell if this is an app problem or a connectiq problem.

Garmin flubs every product launch in significant ways.  They might be the best in the bike industry but that doesn't say a lot of about the quality of hardware or software we use.  Other companies have issues but the ones Garmin creates are severe.  The first touchscreens were terrible, even unusable in rain, which is a common occurrence in an outdoor sport.   The first gen Garmin pedals had bearing problems and vector 3s had the battery door debacle.  The edge 705 used gps to determine current speed and it was wildly inaccurate.  Those are just the instances I remember off the top of my head.

I disagree with the assessment that other companies all have issues of this magnitude.  Look at the vector 3 - they had to send new battery doors to everyone.  I can't even think of anything close to that bad in the last few years.

The root issue is that companies are so anxious to get the product out the door that they let quality slide a long way.  I'm not saying the 1040 is a disaster but it does seem like a major miss that connectiq apps don't work with sensors.   It is impossible to test every combination of sensor but no connectiq apps that access sensors are working.  That seems like a BIG miss, not a devil's in the details miss.

Why do I come back?  I think the edge is the best cycling computer when it works and once they work the kinks out, it will be fine, but it's hard to pay a premium for a product that needs months of development work before it's stable with a core tenant of it's functionality.

And this is the third generation of a product that's mostly been the same for years!  The 1030, 1030 plus and 1040 are all mostly the same computer.

 Having a disappointing experience with a device approaching $1000 leaves a bad taste in your mouth. I would have rather they said that connectiq isn't ready to go and disabled it as opposed to loading it my phone and finding out its broken 3 minutes into my first ride.

CIQ developers have responded to say that it's not them. 

Did bot had any sensors disconect, or major problem, only one bug with workout page, but nothing critical

The fact that you didn't have any problems is not a particularly useful data point for those of us who did.  Consider yourself lucky.  The device looks like it works for the most basic use cases, but many advanced features that users of older devices have come to rely on seem to have fundamental flaws.

That doesn't mean that they're arent problems.  Only that you've not experienced them.  Load a connectiq app that uses sensor data and report back.

Being able to use external sensors is a basic use case. If I wanted just speed and distance I'd buy the edge 130