TI updated my phone to android 13. But even though I tried many things, I couldn't find the wifi search. There was also A12 before the update, does anyone have similar problems?
Related
Hello,
i'm using the last RR Build (5.7.3) with CM Kernel and rooted.
I can't find the option to select the network operator manually.
With the original Oxygen OS i can search for network operators.
Please tell me where i can find the "scan menu" in RR or Cyanogenmod
Thanks
Mine's been missing for awhile. I thought it was due to the OxygenOS 3.2.4 OTA that I manually applied (which borked my Baseband and had to run old fixes to get it back). My original post regarding this is here.
So my question is this, what was the last OxygenOS you installed on your phone before the issue?
I installed and updated the OxygenOS before i changed to RR.
I think it was the 3.2.4 version of oxygenOS.
@matze3275 I know it took awhile to respond but I do know it's not OTA related it's something to do with a change that was made in CM13.
Is anyone facing issues with sending/receiving files in share it on Android pie
Using share it on pie for first time. It worked fine in Oreo fine.
The other device always get 'connectivity error' after they connect to my 5t under share it hotspot network
I tried with different devices Android/iOS, same message
Reinstall latest version of share it. No luck.
Appreciate your inputs.
Hi all,
As I have almost no mobile network where I live, I use the "wifi call" option of my Galaxy A3 2017 with an SFR rom (France) to make calls thanks to my wifi connection from my box.
I wanted to know if with a rom like lineage 16, crdroid 6, resurection 3.2.1, Hrom j6, I would still be able to make wifi calls thanks to this native option which is in the phone settings menu?
To be more precise, I am not talking about making wifi calls through applications like whatsapp or other.
A big thank you for your help
If I do not have answers it is because it is not possible or then I am not precise in my request!
Not really a custom rom per-se, but I know the H-rom A7 port does support WiFi calling (VoWIFI), as I use this myself. Port from the A7, debloated and updates the A320 to Pie. I have been using this for several months now with no significant issues. None of the LineageOS based ROM have VoWIFI, which seems to be most if the custom ROM for this phone. Haven't found anything else other than stock which supports VoWIFI, but happy to be corrected if there is. I am very pleased with H-Rom though, definitely would recommend it. http://forum.xda-developers.com/samsung-a-series-2017/development/rom-h-rom-a7-port-t3940532
thank you very much for your help.
Is this rom still developed because I only see one download link!
On the other hand I do not know at all this kind of rom, except for the passage in android 9, that it is the difference with the rom stock of the a3 2017 because before I used for another smartphone, roms like lineage or crdroid and I could remove all stock applications.
Thanks again for the help
As far I see OOS 11/12 doesn't work fine. And for me ColorOS looks moooore stable.
Is there a way to enable Android Auto on COS 12?
Maybe someone has investigated this issue...
Atantares said:
As far I see OOS 11/12 doesn't work fine. And for me ColorOS looks moooore stable.
Is there a way to enable Android Auto on COS 12?
Maybe someone has investigated this issue...
Click to expand...
Click to collapse
+1, i tried multiple ways to get it working. Systemizing the app using magisk systemize , when i connected to car, initial setup of android auto came, but later app crashes. Waiting for a solution
I was using custom roms for months/a year on my oneplus9pro, however approx 3 weeks ago certain apps such as banking and a secure code app I use for work stopped working due to root issues, my rom was not rooted, however it just seems any custom rom caused this error. I've been back on Oxygen OS for the time being and I am wondering now if this has been resolved or are people still getting the errors?
Thanks
Can you supply more Information, with the aim of someone more knowledgeable helping you out.
Which custom ROMs gave you the errors ( so that the issues can then be raised with them ).
All custom ROMs gave me the error. I had it with Android 13 custom ROM' and then I'd drop down to Android 12 and had the same errors. I googled it at the time and saw it was a global issue for all custom roms on oneplus etc, but not seen anything since.
I have a European Oneplus 9 pro. I just want to know if anyone else is able to use banking apps now?
I use T-Mobile banking and it's working. Are you passing safety net on those roms?
luckylui said:
I use T-Mobile banking and it's working. Are you passing safety net on those roms?
Click to expand...
Click to collapse
I believe that is the issue. Everything was fine and then one morning I got hit by these errors. I flashed a couple of ROMs and same errors. But if yours are working then hopefully mine will too. Are you on Android 13 or 12?
Dizzee87 said:
I believe that is the issue. Everything was fine and then one morning I got hit by these errors. I flashed a couple of ROMs and same errors. But if yours are working then hopefully mine will too. Are you on Android 13 or 12?
Click to expand...
Click to collapse
I'm on 12. Google search Universal Safety Net fix and install it through Magisk. That should do the trick and also enable Enforce Denylist then go into the Configure Denylist and enable your banking apps in there as well. Hope that helps! I have the 2127 T-Mobile 9pro converted to the 2125 Global version.
Dizzee87 said:
I was using custom roms for months/a year on my oneplus9pro, however approx 3 weeks ago certain apps such as banking and a secure code app I use for work stopped working due to root issues, my rom was not rooted, however it just seems any custom rom caused this error. I've been back on Oxygen OS for the time being and I am wondering now if this has been resolved or are people still getting the errors?
Thanks
Click to expand...
Click to collapse
I`m using First Direct / Tesco / Barclaycard . . NO Issuse
Dizzee87 said:
All custom ROMs gave me the error. I had it with Android 13 custom ROM' and then I'd drop down to Android 12 and had the same errors. I googled it at the time and saw it was a global issue for all custom roms on oneplus etc, but not seen anything since.
I have a European Oneplus 9 pro. I just want to know if anyone else is able to use banking apps now?
Click to expand...
Click to collapse
Check your drivers, someone earlier had
overlay drivers. They took them out and its working