AdrianLxM

I got that reproduced last night. It won't send the data right away if the setting is switched off, but it will at some point. There are actually two places...

We have similar things in other places as well, I guess (services working when there is nothing to do): As an example: in the CollectionServices the retryTimer and failoverTimer are...

I deleted the Idea how to fix the missing alert issue, here is another one: If bgReading.last() is null (no bg reading for current sensor or no sensor started), we...

I think you've quoted the wrong part (MissedReadingService will call OtherAlert not FileBasedNotifications) and it does also get triggered by itself (after a missed readings snooze time is over, ...)...

This strategy would make all the good work from @mgranberry adopting xDrip to Marshmallow useless, wouldn't it? The actual problem is where we preemptively exit the control flow and do...

I understand it like this: For bgSendQueue we just need the timer to start backfilling data once in a while in the background. Current data comes through without timers anyway....

@mgranberry > As long as it is cancelled it will have no influence on battery. I thought I've read (maybe even from you), that having a timer that will do...

@mgranberry, so that change would mean that while xDrip is running the phone will never be able to enter Doze mode. As I don't have Marshmallow devices (and probably won't...

@mgranberry at the moment it does not always call AlarmManager.setAlarmClock(). But this thread is about the discussion if we should change it back to always set it to 6 minutes...

Are there any conflicts with: https://github.com/StephenBlackWasAlreadyTaken/xDrip-Experimental/pull/154 ?