Actually, there was CIQ3 FW for the 645m released at the Summit, but it's now back to 2.4.x in production FW. :(
With the F5 devices, one thing I did notice is a few WFs that use Activity.Info.currentLocation hadn't added the positioning permission, so there were posts about not being able to see sunrise/set, etc, so hopefully the beta FW will catch that kind of thing before 3.0.1 is released
Jim thanks for the reminder on the FR645(m). The summit was long enough ago, and that beta was never posted in the forums that I forgot about it.
I have noticed one thing with the latest FW for the FR935 is that when I use the oneshot position. That watch no longer caches the position and gives the last known position. Instead it waits until the status is poor or better. This is not necessarily a bad thing just different than past FWs.
I am also seeing some odd behavior with my radar app in that one data source immediately gives error 0, but the other works fine. The previous FW both worked fine. The same URL works in the simulator. I gave some troubleshooting to do tomorrow.
Anyway, happy to see some more Betas get released.
Actually, the thing with one_shot looks like a fix to me. (I think I first saw it on the va a 2-3 years back). When you specify one_shot, to me, it should always fire up GPS and gets the current location. Returning "last" was a problem if you'd changes locations where you don't want last, but you really want current (WU was good example, as my widget asks for data from the closest PWS when GPS is used).
if you don't mind last, you can get current from Activity.Info.currentLocation. And if that's null (It's no longer cached), then fire up GPS.
For me, I changed one_shot to continuous, and in the call back, when I get an accuracy above last, I turn off GPS. It was kind of a pain, and to me, a way to work around a bug....
for the error 0, there's a thread by r.485 about auto migration, where he was hearing of that on f5 plus devices with a makeImageRequest, so whatever was involved (it was a Brian post to look for), wasn't fixed for the 3.0.0 beta FW is my guess...
Jim, I agree it seems like a fix. That is why I said it may not be a problem, just different. Deep down I would like one shot to work like you describe. I just have been leveraging the "last" for a while. I may have to rethink what I am doing.
As far as the error code 0, I saw that thread, but I don't thing that is that case. The same function works fine sending the image request to Weather Underground, but changing just the URL to Aeris Weather always fails. If it was makeImageRequest issue then I would expect both services to fail.
It's a way you use a native map and with a CIQ device app can place things on it, like the polyline and markers, using their locations on the map (lat/lon).
Yep, this use case I understand, but having access to persistent content will give us more possibilities. I asked because once I first read promo to CIQ3 I hoped I will be able to load course or waypoints to CIQ app, do some processing and then render them somehow. Maybe next time. :)
Well after doing some digging around some old posts, Garmin finally got around to fixing the bug in oneshot position requests that returned the Last Known position. Since I was making use of that to minimize time in the watch faces. So the observed behavior while different, is the one I should have been getting before. I have now figured out a better work around to keep the same functionality for my app.
In doing my testing in the simulator, I figured out the cause of my 0 errors with one provider. It turned out my account had expired. Once I fixed that both services work fine again. The weird thing is the simulator returned a 404 error, but the watch returned 0. Go figure.
The new beta which came out today for the FR 935 and F5/F5s upped the CIQ version from 3.0.0 in 9.72 to 3.0.1 in 9.73. I am going to go out on a limb and say first production release of CIQ3 is soon. ;)
Thanks for updating the thread, sabeard ! There are device firmware releases coming fast and furious, so most of our attention has been helping to validate that everything is working correctly. :)
