Private internet access hasn't been working since OOS 2.1.1...Just updated to 2.1.2 and still, no joy. Anyone have a solution? P.I.A. states its an Oxygen OS issue. I'm currently using OpenVPN successfully with my P.I.A. credentials, but would prefer P.I.A.'s app. Tia...
im facing the same issue and am using OpenVPN. hopefully a future software update will fix this
Related
Has anyone tried the Android Beta program that is currently using the Fi network? If so, is the device you are using your daily device and is it stable enough for an only device user?
If you're concerned with network issues, I haven't experienced any (Just standard "N" bugs)
Sent from my Nexus 6P using Tapatalk
All good here. Been on N since release and have had no issues with service. Just your normal little things that come with a beta OS. The newest N build is very stable and is running as my daily.
Anyone running the latest beta (4)? How is it working with Fi, and what kind of mods have you done? (rooted, etc.)
I'm running the latest beta (4) and Project Fi is work pretty good. I'm also in an different country visiting. Rooted, Elite Kernel, CTTMOD, Adaway Host fix, Custom font, and viperforandroid.
Rtistique said:
I'm running the latest beta (4) and Project Fi is work pretty good. I'm also in an different country visiting. Rooted, Elite Kernel, CTTMOD, Adaway Host fix, Custom font, and viperforandroid.
Click to expand...
Click to collapse
I flashed the 4th beta yesterday and it's basically a finished product - only the occasional animation jank here and there. Absolutely no problems with Fi so far - again, seems like a finished product.
Only problem is I didn't wipe my phone, I just updated as though I was flashing a monthly security patch. As a result I'm still encrypted, which apparently means twrp doesn't work, so I'm not rooted, which I'm not too pleased about. If anyone has a solution to that I'll be very grateful, since I'm about to go back to marshmallow.
After updating to the latest version of the companion app (Version 2.0.0.137106828.gms), I've noticed that it can take upwards of 30 seconds to receive any notifications to my Moto 360 2nd Gen. I've tried clearing cache and data, uninstalling the companion app and reinstalling, restarting my phone and watch, resetting and pairing my watch again, and checking for watch updates all with no success. I ended up reverting to the previous version of Android Wear (Version 1.5.0.3329214.gms) and all of my problems have been solved.
When this has happened before, it was because a software update needed to come through to my watch. We know that 2.0 isn't set to launch until 2017, and I'm not willing to deal with this issue until then. I've attached a link to Android Wear Version 1.5.0.3329214.gms for those who share my problem.
http://www.apkmirror.com/apk/google...-wear-1-5-0-3329214-gms-android-apk-download/
*BAM* said:
After updating to the latest version of the companion app (Version 2.0.0.137106828.gms), I've noticed that it can take upwards of 30 seconds to receive any notifications to my Moto 360 2nd Gen. I've tried clearing cache and data, uninstalling the companion app and reinstalling, restarting my phone and watch, resetting and pairing my watch again, and checking for watch updates all with no success. I ended up reverting to the previous version of Android Wear (Version 1.5.0.3329214.gms) and all of my problems have been solved.
When this has happened before, it was because a software update needed to come through to my watch. We know that 2.0 isn't set to launch until 2017, and I'm not willing to deal with this issue until then. I've attached a link to Android Wear Version 1.5.0.3329214.gms for those who share my problem.
Great!! it is works for me! Thanks!
Click to expand...
Click to collapse
Has anyone tried the latest version (2.0.0.138705214)? I'm still sticking with my older version until I can verify that the bugs have been worked out. Comments in the Play Store are still giving mixed reviews of the latest version. I rely more on the good people of XDA and their opinions.
i have reinstalled brand new rom to my phone resurrection remix for oneplus 3. after reinstall my aps Android Wear is not working. with notice: this phone has been flashed with an unsupported configuration for companion. You must reflash it as signed user or unsigned/userdebug. What does it mean,? please help, i´m newbie. thank you. and yes, its a 2,0xxxx version
From everything I've read, the only fix is to go back to the Android Wear version I posted a link to. There doesn't seem to be an actual fix yet.
Synthi said:
i have reinstalled brand new rom to my phone resurrection remix for oneplus 3. after reinstall my aps Android Wear is not working. with notice: this phone has been flashed with an unsupported configuration for companion. You must reflash it as signed user or unsigned/userdebug. What does it mean,? please help, i´m newbie. thank you. and yes, its a 2,0xxxx version
Click to expand...
Click to collapse
You can change the buildprop from debuguser to user, if you want to continue using 2.0
If your phone is not rooted, the only possibility for now is to install the version 1.5 - you can find more information in this Google Group
I've been reading reviews on the Play Store of people having issues with WiFi Scanning turning on and off every 2-3 seconds. I'm having the same issue, but I attributed it to a software update I received for my S7. As previously mentioned, I rolled back to the 1.5.xxxxx update of Android Wear, so I can't imagine that would be the cause of my problem. I can't imagine it's just a coincidence though. Any one have any feedback on this?
Greetings. I've been trying to update my phone from SlimROM 6 to SlimROM 7, but after each install, I've noticed that the Tethering & Portable Hotspot feature is grayed out in the Settings menu (see attachment). The lack of this feature is a pretty big dealbreaker for me at the moment, so I've been staying back on Slim6 for awhile.
Initially, I thought the issue was with the ROM (SlimROM 7 beta 0.8 and below), but when other users reported they were having no issue with the feature, I started experimenting. I've tried multiple other 7.1.1 ROMs at this point, and the only one that allows me to access and use portable hotspots was OOS 3.5.6. Here are the steps I've tried so far to fix this:
Verify latest TWRP and try again
Install OOS 3.5.6 to ensure latest modem, then install Slim 7
Install Slim6 (with working hotspot), then dirty flash up to Slim7
Test LineageOS, AICP, XOS, and a few others (ROMs only, no GApps or anything else) to see if Slim7 was the issue
Bring phone completely back to stock, install OOS 2.2.0 and update to current, then reinstall TWRP and flash another ROM
None of these have provided any success, and at this point I've pretty much exhausted my knowledge base. Does anyone know what might be causing this, or have any other suggestions I might try?
I'm having the same issue, and it's really frustrating.
I'm on Resurrection Remix 5.8.0, running 7.1.1
Someone please find a solution!
avigloz said:
I'm having the same issue, and it's really frustrating.
I'm on Resurrection Remix 5.8.0, running 7.1.1
Someone please find a solution!
Click to expand...
Click to collapse
You will be happy to hear that, after an absurd amount of trial and error, I determined that the issue was with my carrier's provisioning, not my ROM or phone. Once I had that to go on, a bit of Googling found this excellent article, which details how to get tethering running again. I tried this yesterday evening, and it worked wonderfully. Not sure why my carrier has seen fit to disable tethering when I upgrade to 7.1.1, but this is a pretty straightforward workaround.
The only issue I've found with it so far, though, is that it reverts on new ROM flashes. I'm exploring creating a simple Magisk package as a more permanent fix, but this will at least get you going.
Ssayerr said:
You will be happy to hear that, after an absurd amount of trial and error, I determined that the issue was with my carrier's provisioning, not my ROM or phone. Once I had that to go on, a bit of Googling found this excellent article, which details how to get tethering running again. I tried this yesterday evening, and it worked wonderfully. Not sure why my carrier has seen fit to disable tethering when I upgrade to 7.1.1, but this is a pretty straightforward workaround.
The only issue I've found with it so far, though, is that it reverts on new ROM flashes. I'm exploring creating a simple Magisk package as a more permanent fix, but this will at least get you going.
Click to expand...
Click to collapse
Cheers man
Thanks so much.
I rolled back to oxygen is 4.5.14 ROM ...whos link is given by one plus support. From open beta 3.
Now I am facing problems
WiFi is not connecting to any device.
And no device found my hotspot..means my device is not visible to anyone on hotspot.
Please help me in that.
Yashvendra.singh.raghav said:
I rolled back to oxygen is 4.5.14 ROM ...whos link is given by one plus support. From open beta 3.
Now I am facing problems
WiFi is not connecting to any device.
And no device found my hotspot..means my device is not visible to anyone on hotspot.
Please help me in that.
Click to expand...
Click to collapse
This has been common. Take a look here (https://forum.xda-developers.com/oneplus-5/help/wifi-completely-broken-t3721004), some users like me have managed to solve the situation.
Yashvendra.singh.raghav said:
I rolled back to oxygen is 4.5.14 ROM ...whos link is given by one plus support. From open beta 3.
Now I am facing problems
WiFi is not connecting to any device.
And no device found my hotspot..means my device is not visible to anyone on hotspot.
Please help me in that.
Click to expand...
Click to collapse
After flashing the roll back version, you need to go to recovery and wipe everything(the third option in stock recovery).
lvints said:
This has been common. Take a look here (https://forum.xda-developers.com/oneplus-5/help/wifi-completely-broken-t3721004), some users like me have managed to solve the situation.
Click to expand...
Click to collapse
The problem has been solved after installing open beta3 on one plus 5.
I think the problem was only with that rom only.
Now my one plus 5 is working fine.?
As written here: https://forum.xda-developers.com/oneplus-5/how-to/guide-fix-fingerprints-wi-fi-failed-t3731059
You need to delete /data/misc/wifi/wpa_supplicant.conf. No need to wipe anything else.
Hi ,
I was running the limited release version via sideload and everything ran fine however now i have the version which is supposed to work on the OP5 it crashes whenever I open any app that uses it.
Has anyone had any susscess with it?