Re: Ofono CF states not always correct
Hi Jarko,
So actually they aren't both "active" at same time as
the logs show but
personally I don't really care as long as the results are consistent
regardless which API you use which is not the case at the moment as
querying through org.ofono.CallForwarding can give you different result
than using org.ofono.SupplementaryServices.
Ok, so I'm convinced we're not handling this properly. Based on your
testing and my own independent testing setting the Unconditional CF rule
does indeed 'hide' all other rules so they appear inactive.
So do you care to come up with a patch fixing this? Briefly thinking
about this I believe we can implement option 2 from your earlier email.
I'd rather play some tricks and not clear the cache unless really
necessary.
Regards,
-Denis