FR265 - FR965 released

Shent-Aurkhan (SHN) over 2 years ago

hi mates,

just to let you know if you haven't been aware yet,

the new FR265 and FR965 have been released today (in France)

be ready to work on your resources folder,

according the spec,the 965 has 454x454 screen size, the first one.

and the 265 = 416x416,

both amoled touch screen.

happy coding!

_psx_ over 2 years ago

new resolution... work....

Do those devices require 4.2.X sdk?

Shent-Aurkhan (SHN) over 2 years ago in reply to _psx_

I can't tell, I see them on Garmin FR website,

on dev side, there is nothing at this moment, nothing on reference guide etc.

jim_m_58 over 2 years ago

DCR's 965 review https://www.dcrainmaker.com/2023/03/garmin-forerunner-965-in-depth-review.html

jim_m_58 over 2 years ago in reply to _psx_

I just updated devices in the SDK Manager, (including the f7) and if I try to use the 4.1.7 SDK in VS Code with the f7, I get

"ERROR: Device 'fenix7' requires an SDK version of 4.2.0 or greater to be compiled. The current SDK version is 4.1.7. Please update your SDK using the Connect IQ SDK Manager."

It works fine with the 4.2.1 SDK.

li2niu🏃🏻 over 2 years ago in reply to jim_m_58

I failed to find the memory limit for each app type only one key-value related

"appStorageCapacity": 10485760,

li2niu🏃🏻 over 2 years ago in reply to li2niu🏃🏻

...

jim_m_58 over 2 years ago in reply to li2niu🏃🏻

You seem to be looking in simulator.json. Look in compiler.json. And remember, the numbers you see are 4k higher than what's available to ciq apps themselves.

_psx_ over 2 years ago in reply to jim_m_58

yes I've noticed, the same with epix and probably all sup supporting systems 6

but maybe it's enough to change minimal version in json to allow 4.1.7

due to problem with memory with 4.2.1 I've installed only sdk without new devices and can use it (e.g. warning about unused vars at least)

flocsy🤠 over 2 years ago in reply to _psx_

Are you still seeing the compiled code size increase when you change from 4.1.7 to 4.2.1? I don't see anything like that. Can you try to make a short demo code that you can post that reproduces the problem? (I guess you won't see 5k difference with short code, but even 1 byte increase is strange and can help to us to find a possible workaround and to Garmin to find the bug and fix in the next version.

jim_m_58 over 2 years ago in reply to flocsy🤠

While it's not common, in the past there have been cases where the memory used by an app or available to an app has changed a small amount with a new X.x.x or x.X.x SDK. That's why you want to stay away from being too close to the edge of the memory limit in an app. Not a bug in the SDK, but a bug fix or something new.

Never seen a 5k difference though. I'm not seeing anything like that with my apps. I wonder if it might be something like different levels of optimizations.