2015 Moto X Pure on AT&T, and I have tethering included in my plan. Rooted/TWRPed but otherwise stock rom. Built-in wifi tethering does not work. Once activated the wifi network will be visible to other devices for a bit but it drops > 84% of packets
FoxFi (PDANet+), WiFi Tethering (from OpenGarden), WiFi Tether Router (from Fabio Grasso) all fail to work. FoxFi gives this error message:
Fail to activate hotspot: Fail to enable Hotspot. Please try again. If your phone is a supported model please also try rebooting first.
Error: ConnectivityService: Neither user 10255 nor current process has android.permission.CONNECTIVITY_INTERNAL
Click to expand...
Click to collapse
I just need something to work! How can either fix FoxFi, or get something on there that works?
Try adding this line to the end of your build prop...
net.tethering.noprovisioning=true
Make a backup of the original build prop beforehand. Once you add it, save it then restart...shouldnt need any apps, it should just work with the built in tether feature.
Works for me. Good luck.
Related
Hi Everybody,
I have an anoying problem: I can't get wifi tethering to work. Read millions of posts on XDA but still no results. I love android on my freaky winmo!
This is my status:
Running XDANDROID.2.2.1.AOSP.FRX03.21.11.10.FULL_PACKAGE
Settings -> Wireless -> Wifi -> switch on = OK
Settings -> Wireless -> Tethering -> Wifi Hotspot -> switch on = NOK.
It simply says 'error' and it also switches my Wifi off. After this switching on Wifi also fails and giving me the same message: error.
(PS all the menu's are in my native language and I just translated them directly to english. Haven't figured out yet how to switch everything to english)
I tried different kernels (and modules). The last one I tried:
zImage-2.6.27.46-01250-g8f8207c
modules-2.6.27.46-01250-g8f8207c.tar.gz
Remember I read something about wifi and Radio ROM on the phone, but I have not HardSPL-ed it yet. Is there a minimum Radio version required?
Anyway, Hope somebody can help me a bit. I am desperate .
Kind regards,
Mo
Rooted stock kk ROM with bionic & dalvik patches. When trying to turn on portable wifi hotspot, error and greyed out option.
Any hints? Is it the patches?
No /data/misc directory exists!
....and now wifi won't start at all!
Notgood.
Is there EAP-SIM support in OnePlus 2?
EAP-SIM is supported by my carrier (France/Free) to connect phone to nearby WiFi Hotspots automatically using mobile account identification.
There are some posts around here talking about this feature (here and there for example).
It is not provided in AOSP, the android issue #9329 is open since 2012 asking for it.
Apple, Samsung, LG, HTC, Sony... phones support it through custom OS or Android overlay.
So the real question is: Do Oxygen OS provide it?
EDIT/ANSWER :
It works fine. I've used it multiple times.
Carrier application (Free) says it supports it
I just received the phone yesterday and installed an application provided by my carrier to configure Visual Voice Mail (Messagerie Free).
The application can also configure EAP-SIM and said that the phone is compatible and I completed its configuration.
However I didn't had the change to test it (EAP-SIM).
I'll post a reply if I'm able to test it.
Connection occurs
I saw the phone connecting to an EAP-SIM WiFi Hotspot (FreeWiFi_Secure), however I couldn't confirm the connection was working (I was driving, so safefty first).
It seems to be working, I just have to confirm it (browse some website when connected to a EAP-SIM WiFi Hotspot).
It works
I can confirm it works.
I've used it multiple times.
So good news.
Hi everyone !
Are you SURE EAP-SIM is working on the Oneplus 2 (the 2, not the one).
I had the oneplus ONE and, yes, it IS working, "Messagerie Vocale Free" can configure Freewifi_secure for the phone.
But I now have the Oneplus TWO and "Messagerie Vocale Free" cannot configure it : It says it cannot configure EAP-SIM on Dual SIM phones, you have to configure it manually. And when trying to configure EAP-SIM manually.. it's not possible...
I'm talking about stock ROM (Oxygen OS 2.1.2)
Yea it works I'm on stock rom and AK kernel.
In Singapore I needed Eap Sim for my provider's free WiFi, so it kind of look like this
network={
ssid="SingTel WIFI"
key_mgmt=WPA-EAP IEEE8021X
eap=SIM
sim_num=1
priority=235
}
network={
ssid="Singtel WIFI"
key_mgmt=WPA-EAP IEEE8021X
eap=SIM
sim_num=1
priority=242
}
The settings were automatically disabled by the phone once added for some reason, I thought it didn't work and left the code there until one day I realize I was connecting to the WiFi through Eap Sim. Nt sure what I did in between that made it work. Perhaps restart or add only when WiFi is off or disable then enable background WiFi scan
Take note that there are two wpa_supplicant file. The correct one should have some WiFi AP already there if u have previously connected to any WiFi AP. The path should be system>data>misc>WiFi
I modified the file using fx file manager with the free root add-on. Which means u need to root ur phone in order to change the settings. ES file explorer didn't work for me
10/8/16:
I've upgraded to Paranoid 6.0.2, there is EAP-SIM option when connecting to Singtel WiFi however it will always result in "Authentication Problem".
I've tried many ways to fix it:
- Removing pmf = 1
- Setting DHCP back to lollipop
- Disable 1.2 and 1.1 TLS for compatibility
- Adding sim_num = 1 (will be removed by driver due to external_sim = 1)
All of them did not work for me.
The only one that did work was to use EAP-AKA instead of EAP-SIM. It even works for [email protected] too.
P"
Thanks all for your advices,
Here is the procedure for French FREE MOBILE + OP2 users
The correct file "wpa_supplicant.conf" is in System(root)/data/misc/wifi as Imk1988 said (so grateful to him btw)
(do not modify the other wpa_supplicant.conf file in System(root)/etc/wifi)
Add this line
network={
ssid="FreeWifi_secure"
key_mgmt=WPA-EAP IEEE8021X
eap=SIM
sim_num=1
priority=5
}
after rebooting, it's working like a charm
Conditions:
SIM FREE MOBILE in slot 1
OP2 rooted
Hi lmk1988,
I tried using your method for Singtel WiFi (using a Oneplus X on CM12.1) and it's not working I'm afraid. I could edit the file successfully, but I get a "WiFi connection failed" when I try to connect.
Will try again later!
(I'm wondering if it's just that CM doesn't support EAP-SIM at all...)
Unfortunately I'm using oneplus two (custom rom: SkyDragon v3.1 OOS2.2 and Boeffla 1.1-beta3) now.
Not really sure if it will work for oneplus X
Anyway do make sure u are modifying the correct file, there are two files with the same name.
And note that not all Singtel WiFi will work. It's funny it can be working on one day then not working the next. Kinda depends on time and place.
---------- Post added at 08:59 AM ---------- Previous post was at 08:27 AM ----------
Okay the issue seems to be from CM12.1 oneplus X
Take a look at bbs.zhiyoo.com/thread-9972195-1-1.html
(T.T I can't post links yet because under 10 post)
It's in Chinese but if you look at what they say for version 8
Code:
8.0更新:
回滚7.0版本的音频驱动设置
回声问题应该解决了
禁用EAP-SIM 设备本身不支持
It basically means
Code:
version 8.0:
Reverted Audio Driver to 7.0
Echo issue have been be fixed
[B]Restricted EAP-SIM setting, it is not supported[/B]
I'm not sure if it means CM12.1 for oneplus X does not support EAP-SIM, or does it mean oneplus X does not support EAP-SIM.
Try changing your ROM back to OOS and see if it works
I see.
Thanks man! I don't really know much about coding, etc., and finding out where everything us. Just kinda winging it by searching through forums and so on.
So really appreciate the help and the info! = )
I'm not sure if I'll try to switch back to the stock OS at the moment, found CM to be preferred at the moment. If I do, though, I'll let you know!
OK i seem to have this extremely bizzare wifi issue.
I can connect to wifi access points fine, if i turn off wifi and turn it back on i am unable to auto connect and have to re-enter credentials for it to connect. Before doing so i checked my wifi ap to see if my ap were listed and they were not.
If i re-enter everything is fine but having to do this to wifi ap is annoying. After i have entered and check the wifi ap files i can see the credentials are saved etc.
If i do not re-enter the credentials and restart the phone with wifi enabled it connects to AP fine.
If i leave wifi connected and connect to to wifi aps that require certs its fine also without the need to re-enter creds.
At first i thought maybe i had a corruption in the wifi config files but i dont see any, no duplicate aps at all, no fancy characters i can see.
Does anyone have any thoughts as my wifi config with aps is many years old and has a massive amount of APs listed.
It doesnt matter what ROM i try as soon as i restore all my APs the issues start, is there a way to bulk export, wipe wifi aps and re-import them all again?
Do wifi aps with spaces in or length cause issues with 5.1.1?
1 root ur phone if you are unrooted 2 download any build prop editor from playstore 3 change this line ro.securestorage.support=true to false in /system/build.prop 4 if it doesnt work try a different build prop editor cz the changes might not be sticking 5) hit the thanks button if it helped
dork997 said:
1 root ur phone if you are unrooted 2 download any build prop editor from playstore 3 change this line ro.securestorage.support=true to false in /system/build.prop 4 if it doesnt work try a different build prop editor cz the changes might not be sticking 5) hit the thanks button if it helped
Click to expand...
Click to collapse
ro.securestorage.support=false
already
This guide is for academic and development purposes only and should not be used to circumvent any contracts you have with you cell carrier.
You need to be rooted in order to enable wifi tethering.
Rooting and editing your stock image voids most warranties.
Follow this guide at your own risk. (I can't take responsibility for you braking your phone)
1. Install a Build.prop editor(this isn't mandatory but I find it makes things easier) I use this one: https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor&hl=en_US
2. add the following line to the build prop: net.tethering.noprovisioning=true
3. Reboot your phone
4. Profit
SAVED
dtb1987 said:
2. add the following line to the build prop: net.tethering.noprovisioning=true
Click to expand...
Click to collapse
Which section of the build prop did you put it in?
gargleblarg said:
Which section of the build prop did you put it in?
Click to expand...
Click to collapse
I normally put it at the end
dtb1987 said:
I normally put it at the end
Click to expand...
Click to collapse
Thanks, it works like a charm .
Note, if you are running Magisk, you shouldn't update the build prop directly, which modifies the system partition so you can no longer use an OTA update.
Use this Magisk function (on one line) in a shell file (any_name.sh) with execution permissions (755)...
resetprop net.tethering.noprovisioning true
Added to this directory...
/data/adb/service.d/
or if it doesn't work there, move to this directory...
/data/adb/post-fs-data.d/
I have not tested this myself, but it is how you are supposed to change build prop when using Magisk. Do your own research to make this work properly...
duh1 said:
Note, if you are running Magisk, you shouldn't update the build prop directly, which modifies the system partition so you can no longer use an OTA update.
Use this Magisk function (on one line) in a shell file (any_name.sh) with execution permissions (755)...
resetprop net.tethering.noprovisioning true
Added to this directory...
/data/adb/service.d/
or if it doesn't work there, move to this directory...
/data/adb/post-fs-data.d/
I have not tested this myself, but it is how you are supposed to change build prop when using Magisk. Do your own research to make this work properly...
Click to expand...
Click to collapse
You shouldn't OTA update a rooted phone to begin with because those updates don't account for changes you may have made. you should be downloading the updates from here: https://developers.google.com/android/images and flashing them manually
dtb1987 said:
You shouldn't OTA update a rooted phone to begin with because those updates don't account for changes you may have made. you should be downloading the updates from here: https://developers.google.com/android/images and flashing them manually
Click to expand...
Click to collapse
You can't run an OTA update on a modified boot image. You use Magisk to revert the boot image back to stock, run the update and re-root. Since it's a systemless root and you don't modify anything directly in the system image, therefore you don't have to revert back to stock system.
I was just offering a quick heads up for those who may be rooted with Magisk, on how to properly modify the build prop without modifying system directly. It's a good thing to learn since many times you'll have to modify those init scripts anyway.
How do I add it to magisk, I'm totally new to it.
Question: I currently have AT&T's (really lame) tethering plan, and my data plan is capped at 5GB data (for my business, AT&T does not offer an unlimited data plan with tethering). So I currently have the ability to turn on/off the Wifi hotspot setting in the phone Settings.
I just rooted the phone and did your update. To test success, I now have to change my plan to unlimited data (no tethering). When I do this, I should be able to still turn on/off the Wifi hotspot via the phone Settings (even though I no longer have the plan with the tethering feature)? Thank you.
issues with Android 10?
Hi, I followed these instructions and all is good.... But I'm stuck on Android 9, holding off on moving to Android 10 due to what I've read in other posts about this technique no longer working. Thought I'd check back to see if anyone has had success upgrading to Android 10 - and enabling wifi tethering via the technique mentioned above. Thanks.
Tethering on Android 10
This works for me on Android 10. It systemless-ly adds the
Code:
net.tethering.noprovisioning=true
line using the resetprop command, and it also runs
Code:
settings put global tether_dun_required 0
which prevents your phone from marking tethered data as such. This makes it harder for your carrier to throttle or block tethered data.
Just keep in mind that if your carrier really cares about tethering, they can still tell through TTL (for IPv4) or Hop Limit (for IPv6) whether or not the traffic is coming from your phone or an attached device. This can be circumvented by setting TTL/Hop Limit on the client devices to 65 before connecting to the hotspot.
DaBigGoog said:
This works for me on Android 10. It systemless-ly adds the
Code:
net.tethering.noprovisioning=true
line using the resetprop command, and it also runs
Code:
settings put global tether_dun_required 0
which prevents your phone from marking tethered data as such. This makes it harder for your carrier to throttle or block tethered data.
Just keep in mind that if your carrier really cares about tethering, they can still tell through TTL (for IPv4) or Hop Limit (for IPv6) whether or not the traffic is coming from your phone or an attached device. This can be circumvented by setting TTL/Hop Limit on the client devices to 65 before connecting to the hotspot.
Click to expand...
Click to collapse
Awesome - thank you!
saved
duh1 said:
Note, if you are running Magisk, you shouldn't update the build prop directly, which modifies the system partition so you can no longer use an OTA update.
Use this Magisk function (on one line) in a shell file (any_name.sh) with execution permissions (755)...
resetprop net.tethering.noprovisioning true
Added to this directory...
/data/adb/service.d/
or if it doesn't work there, move to this directory...
/data/adb/post-fs-data.d/
I have not tested this myself, but it is how you are supposed to change build prop when using Magisk. Do your own research to make this work properly...
Click to expand...
Click to collapse
I don't understand how to do this or what it means. I have root magisk on sm-a235f
Use this Magisk function (on one line) in a shell file (any_name.sh) with execution permissions (755)...
resetprop net.tethering.noprovisioning true