Is my device faulty?

Peraklo
3 days ago

Recently purchased my 1050, and while kinda shocked by the weight of it (compared to my 530), in general i was impressed. Well, until yesterday when i had my 1st long ride (audax of 1000km).

the problems i have faced:

1. mid ride reboots 1-2 times

2. unresponsive touch screen

3. Partially unresponsive touch screen (i could tap it to get the “end ride” prompt, but swiping between data screens did not work)

4. Freezing of the device in Battery save mode (which may be due to using that mode in combination with Varia 515 on a busy road)

5. Tones and sound were set all the way left (i guess that should be muted) and still i had a very loud warning when my Varia disconnected.

it was said that 1050 software was well polished, but this doesnt look like it, especially for the premium price.

all touching was without gloves, firmware wa updated to the latest.

please advise.

thanks

i did not pause or break the ride, it was recorded in full while recharging the device as needed.

  • 0 3 days ago

    Others will comment with more authority as I don't have a 1050 but I note the 1050 (production & beta) forums are full of 1050 users with similar issues as your list, you might scan them.

    I have had a 1040 (non-solar) for 2.5 years and think it is ideal for my Audax, I can get 90+ hours from the battery, but I don't use any of the "connected" or battery intensive features, I just follow a course and record the ride.  The 1040 & 1050 share software and the 1040 forums have their own chorus of issues but perhaps not as many and I am either just lucky or my use case is less demanding as I don't see most of the issues reported, In fact I have recently, rashly commented publicly that I consider my 1040 is now perfect (due to items in a recent beta release) and I am considering not taking any more releases to guard against introduction of new issues. Good luck with the Audax.

  • 0 3 days ago

    Hi,

    your device is as faulty as all the others. I struggle with the 1050 for ultracycling as well with more or less all the above mentioned reasons.  Especially the Battery-Save-Mode crashes are of a real concern for me. And even if it works, its only half usefull due to reduced functionality (display does not wake up to give turn alarms).

    Garmin should really focus on usability and stability instead of introducing new features all the time. 

  • 0 3 days ago in reply to L.Rouge

    I wouldn't count my usage as demanding i guess, i also mostly record the ride and follow the course(s).

    Of the connected stuff though, i do have my iPhone connected for the notifications, Varia, HR strap and cadence sensor. Also, hoping to add the power meter to the combination soon.

    Still, most of the mentioned should ONLY affect the devices battery, not the basic touchscreen functionality.

    I will look into other's posts too, thanks.

  • 0 2 days ago

    Since firmware 12.16 (and currently also with the 13.xx beta software releases), my Garmin 1050 runs very stable. It has some non-critical bugs (auto brightness, auto zoom, …) but overall, I have no reboots at all. Sensors connect quickly and never loose connection, my Smartphone is also connected düring my rides. The display is much better than the one of my 1040, and my 1050 runs also more stable than my 1040 with the latest firmware. 

    I can only recommend to contact Garmin support. They will probably ask you to upload your Garmin folder of your device, so they can analyse the situation of it.

  • 0 2 days ago in reply to Peraklo

    With my first Garmin a long long time ago (a 200 I think) the battery would not even last for a 200km  audax ride (I am slow) so I have always minimised processor / battery load by disabling anything I don't really need or use. Many users like me don't have a lot of issues but other users have more than their fair share, almost 50 years in IT suggests to me that many Garmin problems have the "smell" of processor (or some component / feature eg comms) overload. Touch screen lagging etc is an indication of too much else happing on the device. Thus I go through ALL the settings for every new device and by default disable them (where possible) until I determine I really need it. You have to decide what you really need and accept that this will increase processor / battery use. Even if you are not "using" some feature just having it enabled my use resources.

    An example, I do a bit of indoor rides using the garmin to "follow a course" ( I did the 2019 Paris-Brest-Paris 1200 several times during COVID lockdowns), I don't have wi-fi in my garage but if I leave the wi-fi enabled on the garmin (but not connected to anything) I will get a consistent and significant increase in sensor dropouts, thus I have it disabled by default.

    There is also the possibility that something might be "faulty" with some devices so a call to support might help, they don't have the tools to debug anything but are the first step in getting a replacement if that is indicated.

  • 0 2 days ago in reply to L.Rouge

    While i agree with you on some unnecessary stuff loading the CPU, it should not be "overloading" it... i mean, if you advertise the device as 20h capable with "everything on", i shouldn't have to disable some random prompt or feature just to be able to use the screen. Would you buy a smartphone for which disabling the Whatsapp notifications is mandatory if you want 100% touchscreen functionality?

    Too much else happening in the background is simply a sign of poor SW optimization, but i guess we are used to it by now from Garmin. Pushing the GarminPay into a cycling computer but not making sure that basics work 100% ok, i mean come on...