Feature #161: Support the FrSky Sensor Hub Protocol
Hub channels seem to loose their source on resume of app
|Assignee:||Android Dashboard Developers||% Done:|
|Target version:||3.0 FrSky hub and sensors|
needs investigation. We had this issue before with non hub channels I think.
#2 Updated by Espen Solbu about 6 years ago
-- Last Thoughs first as probably most correct ---
hmm looking further, it might be that FrSkyServer.getChannel should use getHubEnabled() instead of _hubEnabled as this value might not have been pulled from settings yet. I am too tired to test though.
-- Previous Ramblings --
Are you thinking of #424? I think the reset() was causing that. (source channel got set to -1 (none))
What is "resume of app"? when re-entering from another app? or when going back to dashboard from another app, or switching models?
I would guess that there can be problems within the registerListenerForChannelUpdates() method or the FrSkyServer.getChannel(). These methods were very quickly modified to support hub channels, it might be that at a given point in time, the FrSkyServer.getChannel cannot access the hub or its channels? not yet instantiated when called?