DO NOT MERGE fix ratratchet when CID change right before RAT change.
There is a timing gap of updating CID and DataRAT when moving between cell from different RAT (e.g., move from EDGE to GPRS). In that case, cell ID remains the same when handling rat change, thus ratratchet will not report lower rate RAT for the purpose of battery-saving. As its hard to gurantee synchronous cell location change and RAT change, Frameworks will bypass ratratchet on the next RAT change event following CID change. This will fix the timeline issue but with some degree of performance regression when cell location change is not followed with an immediate RAT change. In that case, we still report lower rate RAT (only for the next RAT change) and update UI etc. Bug: 65695609 Test: ServiceStateTrackerTest.java Change-Id: Ia9cc52fa3c9cd3d6d1fc0ec08c929f52a5752755
Loading
Please register or sign in to comment