By the way, is anyone testing this on tilapia having occasional mobile data dropouts? I have one about once a day that is usually fixable by turning on airplane mode and turning it off again, but I'm not sure whether it's related to my patch, or just a coincidence (could be my mobile provider). I'm personally testing a patch using a wakelock timeout (as suggested by @sgt. meow), but I may not bother publishing it if no one else is having problems.
Update1:
So, after testing overnight, I've got 11h 50min unplugged, and baseband_xmm_power wakelock for 1h 7min (9.5%, 1666 locks), compared to 25min for PowerManagerService.Wakelocks. IMO this is still too much; it needs to be equal to or less than PowerManagerService.Wakelocks. I'm going to leave it in place for today to see if it solves my data dropouts, and if so, I'm going to reduce the timeout. It's currently 5 seconds; going to try reducing it to 0.5 seconds.
Update2
The patch doesn't seem to fix my data dropouts. If I keep having them, I'm going to test with mr1 for a few days to make sure it's my data provider. In the mean time, I've reverted to a25. I'm still interested in hearing other peoples' experiences.
Update1:
So, after testing overnight, I've got 11h 50min unplugged, and baseband_xmm_power wakelock for 1h 7min (9.5%, 1666 locks), compared to 25min for PowerManagerService.Wakelocks. IMO this is still too much; it needs to be equal to or less than PowerManagerService.Wakelocks. I'm going to leave it in place for today to see if it solves my data dropouts, and if so, I'm going to reduce the timeout. It's currently 5 seconds; going to try reducing it to 0.5 seconds.
Update2
The patch doesn't seem to fix my data dropouts. If I keep having them, I'm going to test with mr1 for a few days to make sure it's my data provider. In the mean time, I've reverted to a25. I'm still interested in hearing other peoples' experiences.
Last edited: