An app for SDK 3.2 and 3.1?

I have developed watchface for SDK 3.2 as it shows Solar charging Intensity for solar models.

I am getting requests from potential users with older watch like fenix 5 (SDK 3.1) as they love animation (it is not related to the solar charging) on the watch face to develop SDK 3.1 compatible version.

For SDK 3.2 it is easy to detect does watch model supports or not solar charging and displays or not solar charging indicator.

But watchface compiled for 3.2 is not compatible with older models.

I think it should be possible to avoid developing two dedicated versions of the very similar watch faces just to be compatible with 3.2 and 3.1.

Please point me in the right direction how to redevelop app to be compatible with SDK 3.1 and 3.2?

Top Replies

All Replies

0 jim_m_58 over 3 years ago

I use 3.2 to build everything today, including things that run on devices that have CIQ 1.x. And use some 3.2 functionality when available, including solarIntensity.

Are you setting a min of 3.2.x in the manifest or something?

0 Bodya over 3 years ago in reply to jim_m_58

Yes, I set 3.2 in the manifest as I am decided it's required to have access to sysStats.solarIntensity?

It seems your reply points me to set 3.1 in the manifest and use some technics like:

		var sysStats = System.System.getSystemStats();
    	
    	if(sysStats has :solarIntensity){
    		System.println("It has solarIntensity !!!");
    	}

0 jim_m_58 over 3 years ago in reply to Bodya

I think I have 1.2 in the manifest for all my apps, and then include specific targets to limit that. I have a couple that are only CIQ 2 and above, so I simply don't have any CIQ 1 targets.

After that, with jungles or "has" control specific things.

So a class variable like this:

var hasSolarInt=false;

that I set in initialize like this:

hasSolarInt=(System.getSystemStats() has :solarIntensity);

and then use with

if(hasSolarInt) {

}

0 Bodya over 3 years ago in reply to jim_m_58

Thanks a lot! Doing these changes right now to significantly extend range of supported devices!

0 Travis.ConnectIQ over 3 years ago

One additional note about solarIntensity that you may have missed if you didn't look at the documentation...

A Toybox::Lang::Number value from 0-100 that describes the solar sensor's charge efficiency, if available. Will be set to null if the device doesn't support solar or a negative number when the device is not currently charging.

You need to check the solarIntensity value is not null to know for sure that solar charging is supported.

var systemStats = System.System.getSystemStats();

if ((systemStats has :solarIntensity) && (systemStats.solarIntensity != null)) {
    System.println("It has solarIntensity !!!");
}

0 Bodya over 3 years ago in reply to Travis.ConnectIQ

thank you, I have noticed null value for non solar devices, and my own experiments with f6X Pro Solar show this value never going to negative. For the f6X Pro Solar it is all the time [0 - 100].

0 Travis.ConnectIQ over 3 years ago in reply to Bodya

Bodya said:
For the f6X Pro Solar it is all the time [0 - 100].

Don't assume that just because you've never seen it go negative that it is always non-negative.

0 Bodya over 3 years ago in reply to Travis.ConnectIQ

What are conditions to have it negative? I am curious to use it for some visualisation for the watch face.

0 jim_m_58 over 3 years ago in reply to Bodya

I'm seeing it negative on a WF right now, and I'm thinking two possibilities: (-1)

1) It's before sunrise

2) the battery is over 99%, so it wouldn't be doing anything..

0 jim_m_58 over 3 years ago in reply to jim_m_58

So, it goes negative when the battery level is 99% or higher. Makes sense as in the doc is says when it's not charging it will be negitive. I thought a lack of sun (being before sunrise) might do it too, but I don't think so.