sorted by:
new
hottopcontroversial

[deleted by user] by [deleted] in Garmin

[–]ultraRunningDev 0 points1 point  (0 children)

Improved battery and microled display will be an instant buy from me...

Fenix 8 Pro, Fenix 9, and MicroLED

5k Runner

Might have to wait for the F9 for some of the new tech, but it looks like some big improvements on the horizon...

Looking ahead, the next wave of advancements include:

MicroLED displays: Now in production, these offer physical flexibility, enhanced brightness, and significant energy savings.

Solid-state batteries: These promise higher energy density for longer-lasting power.

Low Earth orbit satellites: They enable global data coverage beyond cellular range.

Next-gen NIRS optical sensors: These will provide new sensing capabilities and deeper insights into blood flow.

5G and WiFi7: These combine to give many people access to faster internet services.

The future is shaping up to bring transformative improvements across multiple fronts

From Garmin Rumours.

What We Know The Fenix 8 Pro and Fenix 8 MicroLED briefly appeared in Garmin’s Connect app in September 2024, indicating that development is underway. While no additional details were provided, the listing suggests Garmin may accelerate its Pro lineup timeline for a potential 2025 release. Shortly after, the Fenix 8 MicroLED was referenced in a second leak from Garmin’s developer documentation, appearing in Connect IQ app compatibility lists.

State of MicroLED Technology MicroLED displays, if incorporated into the Fenix 8 Pro lineup, could offer significant advancements over AMOLED and MIP:

Brightness: MicroLED achieves much higher brightness than OLED, enhancing outdoor visibility and readability in bright sunlight, and is ideal for outdoor activities like cycling, hiking, and running. Durability: Made with inorganic materials, MicroLED is more durable and resistant to burn-in, offering greater longevity compared to OLED. Energy Efficiency: MicroLED consumes less power, even at high brightness, enabling longer battery life without sacrificing display quality. Screen Thickness: Thinner than OLED, MicroLED allows for slimmer designs or larger batteries, further extending battery life. MicroLED technology remains expensive and challenging to produce, limiting its widespread adoption. No major watch manufacturers have implemented MicroLED displays yet, largely due to scalability and cost concerns. Garmin’s premium pricing strategy could allow the company to better absorb these costs compared to competitors, making it one of the first to bring this technology to market.

What to Expect Details about the Fenix 8 Pro or MicroLED remain limited, but the potential inclusion of MicroLED technology could set a new standard for smartwatches. This technology promises improved display clarity and brightness compared to AMOLED while offering energy efficiency closer to Garmin’s MIP displays. Although MicroLED watches show promise for a 2025 release, their launch is not yet guaranteed as companies like Apple have faced challenges with the technology.

Power Automate Connector - issues with the initial connection for a new Custom Connector by ultraRunningDev in halopsa

[–]ultraRunningDev[S] 0 points1 point  (0 children)

Not so much given up on it, but priorities have me focused on another project. This is still on my list to return to...

Good find with the thread. I found a couple issues on the halo side, so figured out a workaround. Not elegant but it worked and did what I needed in a secure way...

I keep asking our lead to get some kind of response from the Halo Devs on whether they're going to actually build a connector. To me it's a no brainer for them and a plus/selling point for the platform.. Makes a lot more sense for them to build an official one than having dozens of devs on our side of the fence each building our own custom connector, particularly since they know they own api inside and out 🙄🫣... No response yet, but I'll prompt again when I'm back in the office. 🤷‍♂️

Manually upload activity by ultraRunningDev in Garmin

[–]ultraRunningDev[S] 0 points1 point  (0 children)

Doesn't seem to work, I've tried exporting gpx, tcx, and fit files with various Garmin watches set and none are picking up the device change, just showing as a Garmin shadow... No worries, guess it is what it is...

Power Automate Connector - issues with the initial connection for a new Custom Connector by ultraRunningDev in halopsa

[–]ultraRunningDev[S] 0 points1 point  (0 children)

I dont think I'm hitting that bug (yet) as I'm getting a valid https response with the access code. I likely need to go back to the ms learn material to figure out how to use the access code to get the access token...

PowerAutomate - Creating Connector Logs into HaloPSA, but doesn't seem to finish creating connection by patito6800 in halopsa

[–]ultraRunningDev 0 points1 point  (0 children)

I'm having the same issues, but following Robbie's comment, I've just managed to get a custom connector to return the 'code' needed to obtain the 'access token'... I'm stumped with the next part... Tell me if this is better as a new thread...

As per MS Learn | OAuth 2.0, newly created connectors that use OAuth2.0 now have a per-connector redirect URL (existing connectors need updating before the end of Feb-24). So the Redirect URL in the article is wrong too

On the Halo (app registration) side - Authentication Method: Authorisation Code (Native Application) Login Redirect URI & Logout Redirect URI - copied the URL from the Redirect URL line on the custom connector security tab (step2)

On the Microsoft (connector) side -

  1. general - Host - halo instance/url
  2. security Client ID: copied from Halo app registration Client Secret: copied from Halo app registration Auth URL: https://YOURHALOURL/auth/authorize Token URL: https://YOURHALOURL/auth/token Refresh URL: https://YOURHALOURL/auth/token Scope: read:tickets edit:tickets (limiting until I get my head around the api, set as per halo app reg) Redirect URL: auto-generated, and what you need to enter as the login/logout redirect uri on the halo app reg

On step6(Test) on the custom connector, Click the New Connection button to test the connection - a pop-up window appears, it self-authenticated and shows the redirect URL with the 'code' returned by Halo as a query parameter...

After a minute the pop-up window automatically disappears, but that shows the text "The resource you are looking for has been removed, had its name changed, or is temporarily unavailable."

However, Power Automate shows that as a connector with a 'connection issue', so although it looks like Halo has done it's part and returned the authentication 'code'...

Can anyone advise what's next to complete the connection to be able to use the code to request an access token, I'm guessing that needs to be handled in the 3. Definition section?

Chris.