A fatal update

HanselPutra370 · December 5, 2017

I have just recently updated my OnePlus 3 software to it's latest version (OnePlus A3003_16_171116) and strange thing starts to happen.

Yes this update do boot my phone a lot faster, but all the problem that comes with it it's not worth it.

1. It drain the battery like a idk. I'm just using an kind of uber app thing and it drained my battery from 40 to 20 in a few minutes and the phone heats up a lot, this didn't happen on the old version of this software

2. The most important thing is, I CAN'T CONNECT TO MY MOBILE DATA. Nearly everytime i open up my phone, it will always say "mobile data has run out" then when visit my carrier web, i still got 9gb of frkn data. I have to restart my phone like 5 times to get it working. Also sometimes when i start my phone, there's no "mobile data has run out" message but it's simply won't connect to the internet. Anyone know a solution to this because i really need those mobile data. Thanks

Dujith · December 5, 2017

For the first question: After an update to a new OS version i find it useful to remove all my apps and reinstall them.

This worked for me in the past, with the side benefit of dumping apps i was not using anymore.

The second question: Oreo seems to have a data problem with certain carriers and certain phone models. Its a know bug and work is in progress.

Started with the Pixel and Nexus and now that more models are getting Orea it seems it is spreading. So likely something in the Oreo code.

HanselPutra370 · December 5, 2017

43 minutes ago, Dujith said:

For the first question: After an update to a new OS version i find it useful to remove all my apps and reinstall them.

This worked for me in the past, with the side benefit of dumping apps i was not using anymore.

The second question: Oreo seems to have a data problem with certain carriers and certain phone models. Its a know bug and work is in progress.

Started with the Pixel and Nexus and now that more models are getting Orea it seems it is spreading. So likely something in the Oreo code.

Thanks, I'll try the first one. Also the second answer seems to be the problem, thanks