In case it is useful to anybody else: searchable device database for SDK 3.18

Hi,

I was getting fed up with guessing at stuff all the time, so I put together something to interrogate devices.xml and output it to an Excel sheet.

I've attached it here in case anybody else finds it useful.

It does the following:

1. Lists family names for resources directories etc.

2. Provides a table of the following attributes:

name
id
family
grouping
icon w, h
resolution w, h
number of colors in palette
list of ciq versions
watchface memory limit
watch-app memory limit
widget memory limit
datafield memory limit
background memory limit
glance memory limit
audio-content-provider-app memory limit

7455.Devices_3.18_PlusCompatibility.xlsx.zip

7455.deviceNamesWithMonkey.zip

ETA: ADDED THE FOLLOWING ITEMS:

1. "MANIFEST ENTRY" column allows you to select devices based on search and copy + paste into manifest.xml directly

2. Behaviour mapping lists behaviours ("ON_ENTER", "ON_SELECT" etc.) and the mode of accessing each (button, swipe)

3. List of data field layouts

ETA: ADDED THE FOLLOWING ITEMS

4. BPP of display

5. istouch

6. wifi_exclusions

ETA: COMBINED WITH DATA FROM COMPATIBILITY PAGE

ETA: Added in "buildDevices.zip" that has a string file with the device name for each device.

ETA : Updated device names zip to include monkey.jungle

Top Replies

jim_m_58 over 4 years ago +1

You'll also find details here:

https://developer.garmin.com/connect-iq/compatible-devices/

Not the memory limits, but width/height/colors/CIQ version. It's only ROW devices and not APAC.
lauroma over 4 years ago +1

Very nice! thanks!
hundsmiachn over 4 years ago +1

Really useful, thank you!

All Replies

0 jim_m_58 over 4 years ago

You'll also find details here:

https://developer.garmin.com/connect-iq/compatible-devices/

Not the memory limits, but width/height/colors/CIQ version. It's only ROW devices and not APAC.

0 lauroma over 4 years ago

Very nice! thanks!

0 9635560 over 4 years ago in reply to lauroma

Just uploaded an update that includes a few more bits and pieces.

0 hundsmiachn over 4 years ago

Really useful, thank you!

0 9635560 over 4 years ago in reply to 9635560

Just added "BPP" istouch and wifi_exclusions for each device.

0 9635560 over 4 years ago in reply to 9635560

OK, so now the Excel has been merged with all the data from https://developer.garmin.com/connect-iq/compatible-devices/

The first tab is devices.xml and the second tab is compatible devices.

Use "filter" searches to find what you need. Both sheets have XML generators to paste straight into manifest.xml

0 jim_m_58 over 4 years ago in reply to 9635560

But remember, in manifest.xml it says:

It's really add to set targets/permissions/etc with Eclipse, so this may not be something for beginners

0 9635560 over 4 years ago in reply to jim_m_58

Fair enough point, but I’d still beat you finding every device with a given capability with the spreadsheet than with compatible devices link!

It was nightmarish trying to hone my list based on clicking countless blue circles and hoping I saw the entry for what I needed...

Quite why Garmin can’t provide a better compendium of their own products beggars belief.

They _clearly_ not only have the data but (in the background) have it in a useful form.

0 jim_m_58 over 4 years ago in reply to 9635560

What I did back in 2005, was throw together a simple app that told me all I needs for a given device, where a huge amount of "has" statement, and it's things like does a device support SensorHistory, but also, which histories. It displays all the standard font and indicates white space above/below, etc. I'm at about 10 screens of info right now.

A new target comes out, I just add it and run in the sim.

The problem with a spread sheet is is becomes a maintenance issue when a new SDK comes out, and you get into issues with beta SDKs (as happened with 3.0.0 and 3.1.0) when there's a time where there are 2 active SDKS with different features.

0 9635560 over 4 years ago in reply to jim_m_58

The only reason this is a spreadsheet is that Garmin haven’t put their existing, well maintained, searchable, complete and accurate data into a similarly accessible form.

So I had to locate the JSON and parse it into Excel. Likewise, for devices xml

However, this is standard info that is essential for a lot of design purposes and absolutely _should_ be available to developers in a coherent and searchable form rather than the poxy Mickey-mouse clicker of compatible devices derived from it.

Compatible devices is laden with valuable info that I cannot obtain elsewhere but, frankly, it was less work to build a parser to make it readable than to click through the page that supplied the data for it.

This is unfortunately another case of marketing and style overcoming useful.