I have an int'l unlocked G6 Plus on AT&T. After Tuesday night's Pie update, the hotspot won't turn on. Neither Wifi or Bluetooth hotspots work (although USB tether does). The slide switch won't activate. You move it to on and it pops immediately to off again. Tried resetting the networks, booting in safe mode, even had AT&T resend my access point (APN) settings. I've tried both 2.4 and 5Ghz settings. Still no luck. This worked fine under stock Oreo, and so far I haven't noticed any other issues with the Pie update.
Looking into the Android log across multiple attempts to activate the WiFi hotspot I consistently see the following entries:
01-24 09:30:47.230 2155 2860 D SoftApMetrics: Entitlemnt Failed0
01-24 09:30:47.235 2155 2860 I ActivityManager: START u0 {act=android.settings.TETHER_PROVISIONING_UI flg=0x10000000 cmp=com.android.settings/.TetherProvisioningActivity (has extras)} from uid 1000
01-24 09:30:47.281 2155 3240 I WifiService: stopSoftAp uid=1000
Since Soft AP is likely being used to create the hotspot, it appears there is an entitlement issue, which is consistent with the behavior I'm seeing. This is not a carrier (AT&T) constraint. It was introduced by the Pie upgrade. How do I convince Pie's Soft AP that I'm entitled to a hotspot??
New info - I tried a factory reset, but the problem persists. Also heard from another user on the Moto forum that he's having the same issue. Any info or suggestions, even other people who are or are not having the problem, would be helpful.
Looking into the Android log across multiple attempts to activate the WiFi hotspot I consistently see the following entries:
01-24 09:30:47.230 2155 2860 D SoftApMetrics: Entitlemnt Failed0
01-24 09:30:47.235 2155 2860 I ActivityManager: START u0 {act=android.settings.TETHER_PROVISIONING_UI flg=0x10000000 cmp=com.android.settings/.TetherProvisioningActivity (has extras)} from uid 1000
01-24 09:30:47.281 2155 3240 I WifiService: stopSoftAp uid=1000
Since Soft AP is likely being used to create the hotspot, it appears there is an entitlement issue, which is consistent with the behavior I'm seeing. This is not a carrier (AT&T) constraint. It was introduced by the Pie upgrade. How do I convince Pie's Soft AP that I'm entitled to a hotspot??
New info - I tried a factory reset, but the problem persists. Also heard from another user on the Moto forum that he's having the same issue. Any info or suggestions, even other people who are or are not having the problem, would be helpful.
Last edited:
Facebook
Twitter
Instagram