Android doesn't do a good job of teaching people to expand notifications, so if you don't know how to do it it's confusing.
Obvious way to solve this is to allow swipe-to-dismiss. I initially had usability issues because I kept accidentally dismissing the thing, but it may be better for it to be easily dismissable. Dismissing the notification wouldn't turn off the underlying service, but there may be a simple callback that will do that.
Option 2 is to increase the priority of the notification even higher. This should automatically expand the notification more often, which would be an improvement.
You have to swipe-expand the notification, then hit cancel, because it's an 'active notification' that doesn't get swiped away.
See user story: https://www.reddit.com/r/LosAngeles/comments/2x1wws/my_app_metros_mobile_app_is_too_slow_mine_is_fast/cp27c5w
Android doesn't do a good job of teaching people to expand notifications, so if you don't know how to do it it's confusing.
Obvious way to solve this is to allow swipe-to-dismiss. I initially had usability issues because I kept accidentally dismissing the thing, but it may be better for it to be easily dismissable. Dismissing the notification wouldn't turn off the underlying service, but there may be a simple callback that will do that.
Option 2 is to increase the priority of the notification even higher. This should automatically expand the notification more often, which would be an improvement.