No ipv6 toggle? 3T - OOS 4.1 - OnePlus 3T Questions & Answers

i dont know whats happening, my 3t does not have the ipv6 toggle! (see attached)
i saw in a video, it suposed to be in the wifi settings
Ive already wiped the phone to factory, and installed OOS 4.1
Can anyone help?
regards!

I think it was removed in OOS 4.1.0, which is unfortunate since it dramatically improved my WiFi reliability... So much for "Improved WiFi connectivity," hope they bring it back in the next patch.

WTF is it with them. This perfect phone and better and better Oxygen Rom and they forget to put a feature that was discussed before many times. Bleah!

From what I understood, this was only included in OOS 4.0.3 to debug the WiFi connectivity issues. They appear to have fixed them, therefor this is no longer necessary.

Related

[Q] CM11 WiFi Connection Issue

Hey guys! I have only just joined XDA Developers so please excuse me if I have posted this thread in the wrong area. I have a Samsung Galaxy S Advance (GT-I9070) running stock Jellybean firmware (4.1.2 ITV) but as you all know the stock firmware for this device is full of bugs and freezes often. I successfully rooted my device and installed Team Canjica's CM10.2 ROM (4.3) from the thread on XDA Developers but the WiFi wasn't working. I then installed Maclaw's CM11 ROM (KitKat) because I thought that might solve the issue but it didn't. Here are the details:
Device scans for nearby wireless routers.
I type in the password for my home router.
Device saves router. "Saved, Secured" message displayed.
I tap on my home router in the list to connect.
Device says "Connecting" for a couple of seconds and then goes back to saying "Saved, Secured".
I browsed through the forums and some users suggested switching WiFi Frequency to Auto and turning off WiFi Optimisation but neither of those methods worked for me. The ROM was installed successfully and all other features are working properly so I don't think that is the issue. And my router settings are also alright since I am able to connect to it from my Nexus 7 (2013) properly. Can someone please provide me with a working solution for this issue? I will start receiving very high data usage bills soon because my data plan isn't unlimited. Thank you!
Is your ssid hidden (not broadcasted) by any chance? i had those troubles on hidden home network. Sometimes it worked after a while, sometimes it didn't. What helped me is to broadcast ssid for a moment, get connected with phone, remove broadcast (it will reboot router so phone will lose wifi for a moment). Then somehow it got connected normally
Sent from my SGS Adv. using xda-developers app.
idedItp from
I just checked my router settings and SSID Broadcast is enabled. I tried flashing OmniRom 4.3 thinking that this may be because of a problem with CyanogenMod but the problem still persists. Is there any additional kernel that I was supposed to install perhaps?
CyanogenMod 11 version ?
jeremymichaeldlima said:
I just checked my router settings and SSID Broadcast is enabled. I tried flashing OmniRom 4.3 thinking that this may be because of a problem with CyanogenMod but the problem still persists. Is there any additional kernel that I was supposed to install perhaps?
Click to expand...
Click to collapse
Which version CyanogenMod 11 are you using?
jeremymichaeldlima said:
Hey guys! I have only just joined XDA Developers so please excuse me if I have posted this thread in the wrong area. I have a Samsung Galaxy S Advance (GT-I9070) running stock Jellybean firmware (4.1.2 ITV) but as you all know the stock firmware for this device is full of bugs and freezes often. !
Click to expand...
Click to collapse
Just a detail to those who have not upgraded to JB stock and think it is impossible to use it without problems:
All bugs and freezes in Stock JB currently are perfectly finished.
I use STOCK, only with modified kernel (cocore 8.2) without freezes or bugs in months of use.
Enjoy the developer's work (cocafe), because without it JB probably would be impossible in SGA. However we have JB 100% functional and bug-free.
About KK and WIFI bugs:
The only KK (or based) ROM that used without WIFI bugs was RR 20140313.
In fact, the only issue is incall vol. in my experience.
WiFi Direct, Camera -> Panorama is laggy , Screen Recorder not working Not Tested
I also noticed that the battery is worse durability.
But I went back to JB Stock -- personal preference.
ADR USR said:
Just a detail to those who have not upgraded to JB stock and think it is impossible to use it without problems:
All bugs and freezes in Stock JB currently are perfectly finished.
I use STOCK, only with modified kernel (cocore 8.2) without freezes or bugs in months of use.
Enjoy the developer's work (cocafe), because without it JB probably would be impossible in SGA. However we have JB 100% functional and bug-free.
About KK and WIFI bugs:
The only KK (or based) ROM that used without WIFI bugs was RR 20140313.
In fact, the only issue is incall vol. in my experience.
WiFi Direct, Camera -> Panorama is laggy , Screen Recorder not working Not Tested
I also noticed that the battery is worse durability.
But I went back to JB Stock -- personal preference.
Click to expand...
Click to collapse
Actually I did try that method. Flashed Samsung's latest stock firmware I9070XXLQL (ITV) and then rooted and installed CoCore. To be honest overall performance was much better and UI smoothness was improved. But after a couple of days of regular usage with just a few basic applications such as a note taker, train arrival time, WhatsApp etc. the device started freezing up a couple of times a day again. I admit it worked much better than before but freezes and hangs were still quite frequent. Running OmniROM 4.3 now with no issues so far except for dialer FC, laggy panorama and non functional WiFi hotspot.
jeremymichaeldlima said:
Hey guys! I have only just joined XDA Developers so please excuse me if I have posted this thread in the wrong area. I have a Samsung Galaxy S Advance (GT-I9070) running stock Jellybean firmware (4.1.2 ITV) but as you all know the stock firmware for this device is full of bugs and freezes often. I successfully rooted my device and installed Team Canjica's CM10.2 ROM (4.3) from the thread on XDA Developers but the WiFi wasn't working. I then installed Maclaw's CM11 ROM (KitKat) because I thought that might solve the issue but it didn't. Here are the details:
Device scans for nearby wireless routers.
I type in the password for my home router.
Device saves router. "Saved, Secured" message displayed.
I tap on my home router in the list to connect.
Device says "Connecting" for a couple of seconds and then goes back to saying "Saved, Secured".
I browsed through the forums and some users suggested switching WiFi Frequency to Auto and turning off WiFi Optimisation but neither of those methods worked for me. The ROM was installed successfully and all other features are working properly so I don't think that is the issue. And my router settings are also alright since I am able to connect to it from my Nexus 7 (2013) properly. Can someone please provide me with a working solution for this issue? I will start receiving very high data usage bills soon because my data plan isn't unlimited. Thank you!
Click to expand...
Click to collapse
This means probably you have typed wrong password. Also check that in keyboard it capitalise first letter automatically. forget the network and connect again
WIFI not working with cm-11-20140521-UNOFFICIAL-janice and cm11.0_janice.nova.201406
Same wifi problem with cm-11-20140521-UNOFFICIAL-janice and cm11.0_janice.nova.20140601. Wifi not connecting even after giving the right password (used to work correctly with jb4.1.2 and still works with desktop) only showing saving and connecting wifi. Then the wifi connection is shown to be saved. If wifi does not work with cyanogenmod11, then what's the use of upgrading?
Is wifi is not working in any custom kitkat Rom?
Please suggest a solution.
Try couple times to connect. I remember sometimes I had to reconnect 2-3 times before it gets connection. And the problem with kernel was about WIFI not turning on at all, it was not even search SSIDs.

"Unfortunately WiFi has stopped working" (Plentiful details included)

So I have the T-Mobile variant of the LG G4. I had it unlocked straight from the carrier a while ago and all seemed well. Recently I noticed a huge amount of battery drain and 4G LTE usage from T-Mobile's pre-installed apps--mainly com.tmobile.pr or something which is the "My Account" app (imagine being at 60% left with 27% of the drain having been an app and only 9% the screen. Yeah, it was that bad)
This I obviously found unacceptable, so I went ahead to try and uninstall the bloatware. Lo, much to my dismay, Tmobile has locked it down so you can't uninstall the bloatware, and you can only disable it. This alone irked me enough that I wasn't satisfied with just a disabling. I knew I wouldn't rest until I had obliterated it.
I've had plenty of android phones over the years and done my fair share of rooting and flashing ROMs and the like, but I hadn't touched that aspect of my G4 because I wanted a dependable device for school and I didn't want to mess around with it. I knew I'd have to root it to get rid of the tmobile bloatware so I went and did that using the Low effort root method (http://forum.xda-developers.com/g4/orig-development/root-tmo-vzw-intl-variants-soon-root-lg-t3164765). When this was done a lot of my background processes started to continuously crash. I decided to go ahead and put TWRP as the custom recovery and just go ahead and get some dependable 6.0 ROM, and I found a couple of them.
When I flashed the first ROM, the play store services were crashing so I found the google apps package for marshmallow and flashed that too. It seemed to fix the issue. Yet when I would click on my School's WiFi at the setup (which is WPA2 Enterprise) it would crash and say "Unfortunately WiFi has stopped working." I thought that perhaps I mucked something up in the flashing of the ROM, or that maybe there was an issue with the ROM in general, so I decided to just flash another ROM entirely (after factory resetting it all the way). Along the same time as this I found a slightly more modified and feature packed version of marshmallow by this lad here (http://forum.xda-developers.com/g4/development/h815-genisys-rom-1-0-classic-v10g-t3192649). I decided to go ahead and use this one since it had a h811 version there, that involved flashing a h815 and then flashing a patch.
The "Unfortunately WiFi stopped working" issue persisted, however. I found this odd. I then noticed that if I click any other network that ISN'T the WPA2 enterprise network my school is working that everything seems to work fine.
I went ahead and factory reset it all the way again in the hopes that would fix it. No luck.
I booted it to safe mode and tried to connect to the WiFi network from there. No luck.
I downloaded a third party WiFi app off cellular and tried to connect from there. No luck.
I can't enter the WiFi's name and try to enter directly because it crashes there too.
I can't "Forget" the network as it's never joined that network before so there's nothing to forget. It does let me enter the advanced options but a direct press causes it to crash.
So throughout ROMs and wipes and safe modes and all, this one issue has persisted, where my phone's WiFi will crash when it tries to connect to my school's WPA2 Enterprise network. I've tried plentiful fixes short of flashing back to a 5.0/5.11 stock (which I'm hesitant to do because I read something about phones bricking after they downgrade from Marshmallow using the .kdz files or something?).
I'd really appreciate any help that y'all can provide. I've read these forums for ages but this will be my first time making an account because I can't find anybody else with the same issue and its proving to be quite a pain.
tl;dr wifi isn't working with only one particular network and no fix I've tried under this sun has worked so far. help will be appreciated pls
Have you tried flashing this rom here --> http://forum.xda-developers.com/tmobile-g4/development/rom-g4-h811-xtreme-rom-v1-0-7-28-15-t3167667
I am using this one here and I have no issues using wifi. I cannot speak for the 6.0 roms because LG has not dropped the sources for the Tmo variant yet.
esjames said:
Have you tried flashing this rom here --> http://forum.xda-developers.com/tmobile-g4/development/rom-g4-h811-xtreme-rom-v1-0-7-28-15-t3167667
I am using this one here and I have no issues using wifi. I cannot speak for the 6.0 roms because LG has not dropped the sources for the Tmo variant yet.
Click to expand...
Click to collapse
I got the brown leather variant from Tmobile and it only says H811 as far as I can tell. Not sure of if its the "n" version or not.
I have not tried that rom but ill be sure to give it a go, hoping it will help solve the issue. I did some additional testing and can confirm the issue lies with all WiFi networks that employ WPA2 Enterprise security.
Will there be any issue with the Rom when downgrading from Android 6.0? I was reading about phone's bricking when trying to downgrade certain versions or bootloaders on the tmobile variants.
I'm pretty sure going back to stock 5.1 will be fine. The Tmo variant hasnt been upgraded to 6.0 yet and the ports don't update the bootstacks. Read here --> http://forum.xda-developers.com/tmobile-g4/development/global-marshmallow-6-0-port-to-h811-t3232760
Update: It seems that any Android 6.0 flash cuts off the ability to connect to Enterprise wireless networks. I went ahead and flashed to the debloated stock rom on the thread you mentioned, but it cut off the ability to record video. As such, I went for the xTreme version that you mentioned, and flashed the camera restores and all.
Everything works fine now as far as I can tell. I also got rid of the Tmobile applications draining the battery and all that. All should be well. Thanks again for the help

WiFi Calling Nightmare!!

So I am having a bit of a nightmare that I hope someone can help me with. I seem to have lost the option to enable WiFi calling... From anywhere. This option is totally missing from all settings panels.
Bit of background, I'm running a Quark with RR Nougat 8.5 (last release out) due to the fact that Oreo will not support encryption with TWRP, Nougat does.
Anyway I know I have seen the option to enable WiFi calling on my device but I cannot seem to locate it again. I have seen some other situations where this option has disappeared. Any help would be great appreciated. Thanks!

Question Wi-Fi stability issues

Even with the latest update as of May 2022, my new Tab A8 exhibits Wi-Fi stability issues not seen on the old Tab A7.
After leaving a connected tablet to sleep, Wi-Fi for some apps won't work and only a WiFi OFF + WiFi ON reset will restore connectivity.
Anyone else encountered this problem?
Same - it just won't stay on any network for long at all. It won't connect at all to my VirginMedia router saying 'couldn't get ip number'
Doesn't happen to me from what I've seen... Have Xfinity cable internet together with a Netgear router/modem.
Have you guys done all the system updates?
Yup, up to the latest from April. Tested on 2 devices and it's the same. Factory reset doesn't help.
I'm hoping that if not before, at least the Android 12 update will resolve this.
I just updated to Android 11 firmware update from last week - X200XXU1AVG1 - but the issue remains the same
On Build number RP1A.200720.012.X200XXU1AVC1, no updates I'm aware of. When this happens to me and I toggle wifi off and back on, no networks display. If I toggle airplane mode it they will appear again.
II'm in the USA, using an asus blue cave router.
What's everyone else using?
Anyone know what wifi chipset this tablet uses?
Got the update to Build number RP1A.200720.012.X200XXU1AVG1 it still occurs, and I'm also noticing bluetooth connection issues, both are cured by cycling airplane mode on and off.
Yeah... let's hope Android 12 includes fixes for this... really, the Tab A7 was a much better device with a nicer screen
KoMarCek said:
Yeah... let's hope Android 12 includes fixes for this... really, the Tab A7 was a much better device with a nicer screen
Click to expand...
Click to collapse
I reported the issue via Samsung members app with a bunch of screenshots,
SM-X205 is now getting Android 12 but nothing available yet for SM-X200. Will probably take a couple more days
OK now SM-X200 also got the first Android 12 update and the results are... BAD! Still the same issue and I'm quite done with Samsung for now. Unbelievable that they do not test the basic functionality well enough. I expected some WiFi driver updates under the hood but it seems they are oblivious to the fact Tab A8 has issues.
Had the issue one time since the 15th it's not solved but less frequent at least
What I notice now is that the wifi will turn off randomly. If turned back on it reconnects but shortly thereafter bluetooth dies and cycling airplane mode is required

Bluetooth will not enable - S10

Hi all! I was wondering if any of you guys have seen this issue before. I have an old Galaxy S10 that I wanted to resurrect for emulation and forgot the reason why I stopped using it was because the Bluetooth functionality, once toggled on, would look like it's trying to turn itself on but never enables.
I've tried:
Installing all updates
Resetting network settings
Clearing Bluetooth app cache / pairings
Wiping the system cache partition
Factory resetting
Re-flashing current and past firmwares
I was able to get Bluetooth to enable and function normally by random after re-flashing the firmware but would quit after 5-10 minutes.
On the S10 and my current phone Pixel 4a (with functional Bluetooth) I went into Developer options to check currently running services to compare. On the 4a the Bluetooth process is listed as having 1 process and 7 services, whereas on the S10 there were only 2 services and were missing services such as SapService, HidDeviceService, BluetoothPbapService, GattService. (I can post in an edit which services are failing to run on the S10 if need be). The Bluetooth process on the S10 will only show up once Bluetooth is toggled even though it doesn't enable, but will stop running, then start running again, rinse and repeat.
So that being said, is this a hardware issue that I'm SOL with? Are there any other remedies that I could try?
Any input would be appreciated. Thanks!
First off, which S10 do you have... Exynos/Snapdragon makes a big difference, but knowing the model number helps a lot in general as well.
What firmware are you on now?
On my 973U (ie, Snapdragon) I have 1 process and 7 services right now (with BT turned on)... on Oreo with January security (I have stayed off A12 because of many reports of issues on it). I can provide more detail later if needed, as well.
.
schwinn8 said:
First off, which S10 do you have... Exynos/Snapdragon makes a big difference, but knowing the model number helps a lot in general as well.
What firmware are you on now?
On my 973U (ie, Snapdragon) I have 1 process and 7 services right now (with BT turned on)... on Oreo with January security (I have stayed off A12 because of many reports of issues on it). I can provide more detail later if needed, as well.
Click to expand...
Click to collapse
I have an SM-G973U (CCT) running G973USQU6GUJ3, which I believe is the last version of Android 11. I've tried Android 10 and 9 firmwares (can't recall which ones) and I've been having the same issue regardless, which makes me think it could be hardware-based.
In a couple of hours I can edit this post with the two processes that do run, if need be.
Made a mistake - my phone is 975U but that shouldn't matter.
I'm on G975U1UES6GUL1 which I believe is a later version than what you have... but I don't think that will fix anything for your issue. I was on GUL before, and everything worked fine then.
I'd say start off bone-stock after an ODIN and see if it works there (ie, don't download anything, if you can avoid it). Maybe some app you have is killing the BT? But if it doesn't work there, then yes it could just be a hardware thing... disappointing for sure.

Categories

Resources