Anyone using Edge Remote with the 1030?

I use the remote 100% of the time, and I have the same issues. In my case at least It has to do with the phone connection. If you disable the connection it works perfectly.

My experience is similar to others’. What’s more, several other sensors (HRM band—Garmin’s, power meter—Vector 2, Di2—new BT-enabled D-Fly) will (sort of) disconnect with just two or three minutes of idleness (e.g., a quick nature break). Using them (pedaling, shifting, having one’s heart beat…) does not restore them to the display (nor the recorded data). One must go to the Sensors page and,one by one, select them and tap “Connect.” When you do so, they invariable connect very quickly—less than a second. This is in contrast to the time it take to recognizes a newly awakened sensor. That can take many seconds.

The same problems over here. Now winter is starting over here and using the touchscreen with gloves does not work at all, the remote becomes more important to switch screens. However randomly I get the red light flashing and the remote does not work at all.

There has been months and a few firmware updates. The remote is still buggy with the 1030. Is this being addressed ? Garmin, somebody home ???

We are continuing to work on remote issues.

Is there any type of REAL update on this? Meaning, any evidence that it can be fixed outside of a hardware compatibility issue (requiring a new remote)?
After 7 months, we have been patient enough. Those of us with a remote should be reimbursed $50.
I can verify on the latest 4.36 beta the issue still persists. The remote was fine for about 50 minutes then every few minutes it would alternate between not working with the blinking red light, then working again. Once I disconnect my phone, all is well.
I've tested a variety of phones and it always happens. The idea that Garmin can't replicate this is a complete joke.
The remote is NECESSARY for winter riding, and I shouldn't have to pick and choose between mobile device connectivity -OR- the remote.

I may need to raise a ticket with Garmin to ask the following, tho I fear they may tell me it's the first they've heard of it.
-Can those of us with the Edge Remote REALISTICALLY expect a fix for the Edge 1030?
-Has there been any real-world headway or root-cause discovery on this issue since the release of the 1030? A meaningful update aside from being 'aware' of the issue?
-If not, what will be done to reimburse us?

Shawn-Garmin, Thanks for contributing in the forums recently - is there anything you can provide on this, or if we can expect anything in the next public release?

Is there any type of REAL update on this? Meaning, any evidence that it can be fixed outside of a hardware compatibility issue (requiring a new remote)?
After 7 months, we have been patient enough. Those of us with a remote should be reimbursed $50.
I can verify on the latest 4.36 beta the issue still persists. The remote was fine for about 50 minutes then every few minutes it would alternate between not working with the blinking red light, then working again. Once I disconnect my phone, all is well.
I've tested a variety of phones and it always happens. The idea that Garmin can't replicate this is a complete joke.
The remote is NECESSARY for winter riding, and I shouldn't have to pick and choose between mobile device connectivity -OR- the remote.

I may need to raise a ticket with Garmin to ask the following, tho I fear they may tell me it's the first they've heard of it.
-Can those of us with the Edge Remote REALISTICALLY expect a fix for the Edge 1030?
-Has there been any real-world headway or root-cause discovery on this issue since the release of the 1030? A meaningful update aside from being 'aware' of the issue?
-If not, what will be done to reimburse us?

Shawn-Garmin, Thanks for contributing in the forums recently - is there anything you can provide on this, or if we can expect anything in the next public release?

+1

I would be very interested in an honest answer of Shawn, but the fact that Garmin was not able to solve this issue until now shows that apparently it‘s not possible to solve it...

I have the same issues with remote like guys here (connected android phone; ant+ speed and cadence sensor, remote and HRM or HRM-TRI belts). On 4.00 and last 4.36 it is pretty the sam

Shawn-Garmin: I can provide anything what would help to find the problem, just let me know...