A more recent follow-up due to bug #1409694 ( reported by QA ). My comment #8 is incorrect, the original description is more accurate. The selection of which SIM is used for mobile-data is non-deterministic. If two SIMs are installed, sometimes SIM1 is selected, and sometimes SIM2.
As by default SIM2 is not enabled for 3G, if the second SIM is selected, this leads to a very poor user experience.
Note, the suggestion in comment #3, while at first glance a good idea, would be very difficult to implement due to the current intricacies of the MTK device plugin. As such, the original suggestion is still the best idea ( ie. change ofono to not self-power the ConnectionManager interface ).
A more recent follow-up due to bug #1409694 ( reported by QA ). My comment #8 is incorrect, the original description is more accurate. The selection of which SIM is used for mobile-data is non-deterministic. If two SIMs are installed, sometimes SIM1 is selected, and sometimes SIM2.
As by default SIM2 is not enabled for 3G, if the second SIM is selected, this leads to a very poor user experience.
Note, the suggestion in comment #3, while at first glance a good idea, would be very difficult to implement due to the current intricacies of the MTK device plugin. As such, the original suggestion is still the best idea ( ie. change ofono to not self-power the ConnectionManager interface ).