I saw in one of the tech blogs that the wifi teathering issue can be fixed by editing build.prop in custom los roms. Is it true. If so how.
wifi, wifi hotspot and tethering are working latest lineage os update.
Share it not working (lineage os 14.1)
If any one try app for hot spot tegering
Related
I know the wifi tether app was working on slidemeroot builds but not on cyanogen 6.0. Anyone know if this has been fixed for 6.1 and or which build of wi-fi tether would work cause mine still isn't.
I have previously used the Haxpresso ROM to make wifi calls because i get absolutely zero service where i live. I noticed the cm7 has wifi calling. But cm7's wifi still doesnt work for me even after RC4 and flashing the new radio. Bascially, i want a cyanogen rom with wifi calling. if you can help me install it in cm6 or get a permanent wifi fix for cm7, i will worship the ground you walk on. Please, i hate stock espresso. i want some CM goodness!
I haven't heard any news of people getting Wifi Calling to work with CM6.
Maybe you wanna just keep trying different Nightly's? Also, I didn't think my wifi was working either, but I restarted my phone with wifi on and after... well I think a while it started to pick up on networks.
do the wifi .lib files adapt over time? like, with multiple reboots, would the wifi problem eventually fix itself?
Since switching to a 5.0 stock based ROM (Cloudy or rooted stock), I've been having an issue with LAN only wifi networks. Basically, it will get immediately disabled by the OS if the attached wifi network does not have an internet connection. I remember there being a setting in 4.4 where you could disable this feature, but I don't see it as an option on 5.0. From my searching, it appears that this was resolved again in 5.1. Is there any way to disable that feature otherwise? I like 5.0 otherwise, and don't want to deal with the camera quality of AOSP. I looked for a relevant xposed module, but didn't have any luck.
I am facing some really frustrating WiFi issues in Lineage OS 17.1 nightly March 16th build on my Moto G3 osprey. I have been facing WiFi disconnection and slow WiFi speed issues on in the February build so I tried upgrading to March 16th build but it is still not fixed.
WiFi connects fine after the boot but after disconnecting it, WiFi status is showed as 'Saved' and it takes to several attempts to connect, even when it does the speed is awfully bad and the it disconnects at random times.
How can I fix this ? This is really frustrating.
I think I may be experiencing something similar to this, but not sure whether the culprit is the "WiFi Privacy Police" app I use. (The objective of which is to keep WiFi disabled unless you are in a location near a trusted access point)
I don't have issues like this on my OnePlus One running CM13. (And also using WiFi Privacy Police) But on my LG G4 on Lineage 14.1, it doesn't seem to want to connect after boot unless I manually go into WiFi settings.
Sometimes I don't even need to select an AP there, just opening the WiFi settings page seems to get it to connect most times.
There were times I saw WiFi disconnected after an extended sleep period but I haven't seen that issue for a while now. I'm on a March 7 build.
So I just updated my phone to the last (March 5th, 2018) update of Andriod 8.1 and now the wifi hotspot is no longer working. I can enable the hotspot, and devices can connect to the hotspot, but there's no internet access. My phone is unlocked but unrooted and I am absolutely sure that my plan supports tethering (double checked). This seems to be a bug in the new 8.1 update that came out about 5 months ago. Has anyone found a workaround or a fix to this problem?
Thanks for reading, I know a lot of people are having this problem and I'm hoping we can find a solution.
Had same exact issue on the Google Pixel XL (unlocked). Had just recently changed carriers to VZW. Long story short the last thing I tried was to delete the VZW APN, reboot phone, try hotspot once again an poof my hotspot connected devices had internet connection. Only real APN change I noticed was additional "bearers". It still working fine.