ForgroundService affected by doze mode

Question

My Alarm App keeps being late, although I'm starting a ForegroundService from the BroadcastReceiver and the onCreate() of the Service gehts called in time, but the onStartCommand() is called with delay (sometimes), which I assume is coming from the phone falling into doze again before it can execute it...

As You can see from Log.d the Service is started in time and is calling the PlayerActivity in time - but this one is actually starting 1:40min later in this case. Plus the Service does not enter foreground and does not start streaming music before that random delay time has passed (maintenance window?)

How are we supposed to keep a device awake long enough to actually start the foreground service AND ENTER FOREGROUND in time?

I'm using setExactAndAllowWhileIdle() to call the AlarmReceiver - this works for a 100% of the cases perfectly. The delay happens after starting the service.

Should I start the service 15 minutes earlier to ensure it has entered foreground by the actual alarm time and actually start streaming music and calling the Activity at the avtual alarm time?

BroadcastReceiver

public class AlarmReceiver extends BroadcastReceiver {

@Override
public void onReceive(Context context, Intent intent) {

    Log.d("Ben", "Alarmreceiver HELLO");

    String label = context.getText(R.string.defaultLabel).toString();
    int id = 1909;

    Bundle extras = intent.getExtras();

    if (extras != null) {

// kill running alarm activity
        if (extras.containsKey("autoKill")) {

            Log.d("Ben", "AlarmReceiver killing running alarm NOW.");

            Intent bc = new Intent("PLAYER_STOP_SELF");
            LocalBroadcastManager.getInstance(context).sendBroadcast(bc);

            context.stopService(new Intent(context, StreamService.class));
            return;
        }

        label = extras.getString("label");
        id = extras.getInt("id");
    }

    Log.d("Ben", "AlarmReceiver ok!");


// CALC NEXT ALARM and start StreamingService...

    if (Build.VERSION.SDK_INT >= 26) {
        context.startForegroundService(new Intent(context, StreamService.class));
        context.startForegroundService(new Intent(context, CalcNextAlarmService.class));
        Log.d("Ben", "SDK >= 26 *** context.startForegroundServices");
    }
    else {
        context.startService(new Intent(context, StreamService.class));
        context.startService(new Intent(context, CalcNextAlarmService.class));
        Log.d("Ben", "SDK < 26 *** context.startServices");
    }
}

Service

@Override
public void onCreate() {


// initializing variables, shared preferences,... not shown

    Log.d("Ben", "StreamService calling PlayerActivity now...");

    startActivity(new Intent(this, PlayerActivity.class).addFlags(Intent.FLAG_ACTIVITY_NEW_TASK));

// NOTI AND FOREGROUND!
    Notification noti = createForegroundNotification();
    startForeground(ntfctnId, noti);
// It doesn't even get to here before the delay...
}

@Override
public int onStartCommand(Intent intent, int flags, int startId) {

    Log.d("Ben", "StreamService onStartCommand");

The according Log.d:

07-14 14:30:01.335 D/Ben: Alarmreceiver HELLO
07-14 14:30:01.364 D/Ben: AlarmReceiver ok! (label: Alarm 1 - id: 10001)
07-14 14:30:01.372 D/Ben: SDK < 26 *** context.startServices
07-14 14:30:01.378 D/Ben: StreamService calling PlayerActivity now...
07-14 14:31:41.116 D/Ben: StreamService onStartCommand
07-14 14:31:41.224 D/Ben: StreamService wakeLock.isHeld()
    StreamService wifiLock.isHeld()
    *** onStartCommand ELSE ***
07-14 14:31:41.227 D/Ben: preparing player - start streaming in 2 seconds...
07-14 14:31:41.365 D/Ben: wakeLock.isHeld()
    wifiLock.isHeld()
07-14 14:31:41.366 D/Ben: PlayerActivity.onCreate()
07-14 14:31:43.229 D/Ben: Start Streaming now! (normal alarm)
07-14 14:31:43.241 D/Ben: buffering
07-14 14:31:43.242 D/Ben: buffering
07-14 14:31:44.345 D/Ben: ready

The alarm works great in 95% of the used times, but SOMETIMES this dozing appears and starts the alarm 1-15 minutes late - I've been debugging this for more than 2 weeks now, rewrote the whole service and Receiver classes 2 times and start getting crazy, please help.

EDIT

I ended up using a wakeful BroadcastReceiver and a wakeful service (for all API < 26) which then takes care of calling the other services accordingly (what I did in the AlarmReceiver before - and still do for API >= 26)

So far it seems working fine - only on one of my test devices with Lineage running the alarm goes off late sometimes, on my own daily-use-phone I'm running Lineage too, but there it's just doing fine. Maybe the SGS 4 mini is just too old (I don't really believe this, but as long nobody complains I'll have to assume it's working as expected for them)

Thanks for your help @Elletlar.