So I got the Oreo update yesterday and I noticed that Sprint Hub is running far more than it should and eating battery. I have to physically go in and force stop it. 8 noticed on a few forums that alot of people are having the same issue. Anyone have a fix for this or can tell me what it is exactly? I haven't seen anyone post a fix anywhere. I like the new features and update just have the Sprint Hub issue.
Solved! Go to Solution.
Over the next 12 hours, there will be an application update pushed to all Oreo OS devices in order to update App Spotlight. This was the application that was driving the Sprint Hub notification and causing concerns of excessive battery drain. The update will happen silently and automatically in the background, and it will not require user interaction.
The App Spotlight application can also be uninstalled if the customer chooses: Settings > Apps > App Spotlight > UnInstall
It Friday and y'all got me making videos!! Try this...
In this case, please try these steps:
Long hold the notification until it opens with about 20 notification settings that all appear to be turned off. Scroll down to the knee that says something like running in background. It should say "no sound". Open that up and click the bottom option of no sound or interruption and click that.
I'm having the exact same issue. Turning off the sound and notifications just means I just won't know when Sprint Hub is running and using battery, correct? We need an option to turn it on when needed and turn it off when not needed.
Hello KAAN2302. Please try these steps as a work around:
Go to Settings> Apps> Tap the top right three dots> Select show system Apps> Navigate to Sprint Hub, and tell the app to force quit.
Please let us know the outcome.
Turning off notifications doesn't do anything..it still comes back even after forcing it closed. The " disable" option is greyed out so that isn't an option.
Hi guys! Samsung is aware of the problems that the Oreo update has caused and is working to get it fixed. They have reached out to the developers and at this point and they are working on another update to fix the bug.