Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 0b2b1968 authored by nadlabak's avatar nadlabak
Browse files

fix onStartCommand() not being called with null intent 

broken by this:
http://android.git.kernel.org/?p=platform/frameworks/base.git;a=commit;h=39792d2262352ae775091876d5488d2412a2ff92
acknowledged by Dianne here:
http://groups.google.com/group/android-developers/browse_thread/thread/d87fb390c13d141d/0968c394999f2967

this change will fix EAS sync and possible issues of other services

Change-Id: I38df6e638fb581635b97a00671d42f1489be4613
parent 0a3f4ff8

services/java/com/android/server/am/ActivityManagerService.java

+1 −1
Original line number Diff line number Diff line
@@ -8747,7 +8747,7 @@ public final class ActivityManagerService extends ActivityManagerNative 
                ServiceRecord.StartItem si = r.pendingStarts.remove(0);

                if (DEBUG_SERVICE) Slog.v(TAG, "Sending arguments to: "

                        + r + " " + r.intent + " args=" + si.intent);

                if (si.intent == null) {

                if (si.intent == null && N > 1) {

                    // If somehow we got a dummy start at the front, then

                    // just drop it here.

                    continue;