startForeground() does not show my Notification

Question

I am trying to make my Service running in foreground. I tried to use this example (please look for the section "Running a Service in the Foreground"), but startForeground() does not actually show my notification. And no exceptions is thrown. To make it shown, I need to use NotificationManager like here explained. With NotificationManager my notification works, but i'm not sure that my Service is foreground after this "silent" call to startForeground().

What can be wrong?

EDIT: I just tested this sample project that should demonstrate startForeground(), but it does not work! I use API v7.0, I tested it both on emulator and real device (SE Xperia Neo). Notification does not appear.

EDIT2: if i try to call setForeground() then i got a warning setForeground: ignoring old API call.

I also tried to use startForegroundCompat() as described here, but effect is absolutelly the same. I check if my service is foreground using ActivityManager.RunningServiceInfo as described here, and I see that my service is not foreground.

Since you elected to not provide source code, it will be difficult to help you directly. [Here is a sample project](https://github.com/commonsguy/cw-android/tree/master/Notifications/FakePlayer) that uses `startForeground()` successfully. — CommonsWare, Jan 04 '12 at 12:57
I did not provide source code because of my code is exactly the same as in example i provided: http://goo.gl/xXIvc . Thanks for the sample project. — Dmitry Frank, Jan 05 '12 at 04:51
I tested this sample project, it does not work! I use API v7.0, i tested it both on emulator and real device (SE Xperia Neo). Notification does not appear. — Dmitry Frank, Jan 05 '12 at 05:06
The sample project works perfectly fine -- I just re-tested it on a Nexus One, Galaxy Nexus, Nexus S, HTC Desire S, and the "API v7.0" emulator. To start the service and display the `Notification`, press the "Start the Player" button. — CommonsWare, Jan 05 '12 at 12:28
@CommonsWare, thanks for your time. And, of course, i pressed the "Start the Player" button =). Very strange, but it does not work for me on SE Xperia Neo and and API v7.0 emulator. Tomorrow i will test it on some kind of Acer, but i think the problem is in some different place, but i have absolutely no idea what could be wrong. — Dmitry Frank, Jan 05 '12 at 15:44

score 147 · Accepted Answer · answered Sep 01 '12 at 14:25

147

I just noticed that startForeground() doesn't show the notification icon if the id parameter is set to 0...

startForeground(0, notification); // Doesn't work...

startForeground(1, notification); // Works!!!

I hope that it could help someone stuck on this.

answered Sep 01 '12 at 14:25

Luka Kama

1,596
1
11
7

12

and yet the documentation is woefully vague about what this id value even does... I am totally frustrated with the (IMO) poor documentation -_- – Herr Grumps Nov 06 '12 at 05:57
17

And I had **123** which didn't work, changed to 1 and it works! – Ravindranath Akila May 20 '13 at 03:01
4

@HerrGrumps The docs have been updated and now have a warning: "The integer ID you give to startForeground() must not be 0." (developer.android.com/guide/components/services.html). Better later than never =P – Bitcoin Cash - ADA enthusiast Nov 16 '14 at 21:49
Shaw's answer could also be an explanation for the notification not showing up. – Price May 17 '15 at 07:22
Note that this bug in Android has since been fixed. – Sam Dec 09 '16 at 18:16
2

Do not use too big integers like 1337 , 13377331 , 137 . Just use 0x3, 0x1 – Yasin Kaçmaz Jul 26 '17 at 01:06
1

@RavindranathAkila I also used 123, but changing to 1 still doesn't work :( – Hendy Irawan Jan 29 '18 at 16:53
1

I was using "0" and have been trying to fix this for days now. Android always surprises me, in a bad way :( – EvanBlack Sep 12 '18 at 09:38
F%#$ me! .... This had me stumped for almost a day – Chris Feb 16 '23 at 13:20

score 50 · Answer 2 · answered Mar 28 '15 at 09:36

50

in addition to the best answer. you should also check that have you called setSmallIcon. On my android phone, I cannot get what I expected without calling setSmallIcon

answered Mar 28 '15 at 09:36

Shaw

1,445
16
21

2

Worked for me as well – Nikaoto Dec 10 '17 at 12:05
3

Thanks for this. This isn't mentioned as required in the services documentation, but it certainly should be! – John Chrysostom Sep 11 '18 at 13:24
1

Android's official documentation covers 10% of the subject. – TheKalpit Jan 27 '19 at 19:44
2

+1 This answer is so useful, I spent all day trying to figure why the stupid notification didn't behave properly... – user000001 Mar 03 '19 at 13:55
2

This was my issue as well; without `setSmallIcon`, the notification just said ' is running'. Thanks for saving me time and pain! – aremmell Dec 13 '19 at 22:21
you saved my day! – Krishan Madushanka Apr 01 '21 at 08:20

score 2 · Answer 3 · answered Feb 20 '17 at 14:33

2

Is your service a started service or a bound service? I had the same issue with a bound service, but starting the service before binding it allowed me to call startForeground(int, notification) with and have the notification show up.

answered Feb 20 '17 at 14:33

Tunji_D

3,677
3
27
35

for desired-to-be-bounded `Service` best option would be to show notification/start foreground in `onCreate`, it will be called before binding (`onStartCommand` will be called soon and wiil get initial `Intent`, that too late for notifying/foreground). thanks for clue!! – snachmsm Sep 15 '21 at 21:24

score 1 · Answer 4 · answered Mar 17 '16 at 06:27

This might be an old thread, but I'd like to add what I just learned which is not mentioned yet:

It is possible that a Service is still alive after stopSelf() is called because there are Activity that have bound to the Service. As a matter of fact, the startForeground() is just not going to show the notification nor giving any exception in this circumstance.

score 1 · Answer 5 · answered Sep 07 '18 at 07:45

in my case there was no notification after startForeground(...) invoke because I used only .setSubText(...) for setting the message of it (because it is rendered with smaller font on most of devices). But some of devices Xiaomi Redmi Note 4 won't show any notification if You not set message by using .setContentText(...).

Hope that will help someone

score 0 · Answer 6 · edited Jul 09 '12 at 12:47

0

DMitry. I have just suffered your problem and found the cause.

If your app is changing state of a COMPONENT PackageManager.setComponentEnabledSetting()) Android removes the service from foregraound and its notification icon.

Bug reported at Nov, 2011

edited Jul 09 '12 at 12:47

Praveenkumar

24,084
23
95
173

answered Jul 09 '12 at 11:10

Shadowrun

1
1

1

Thanks for the reply, but my app do not change state of a COMPONENT, so this might be some other reason. – Dmitry Frank Jul 10 '12 at 10:35

startForeground() does not show my Notification

6 Answers6

Linked