Hi I rooted my One I have viperRom installed and I used wifiTether to try and tether but its giving me an error. and no I dont have tethering plan! Any help?
jenra said:
Hi I rooted my One I have viperRom installed and I used wifiTether to try and tether but its giving me an error. and no I dont have tethering plan! Any help?
Click to expand...
Click to collapse
you don't need a plan:
1. open the tethering app
2. go to settings
3. select change device profile and check generic ICS/JB wlan0
4.enable wifi encryption---set your password
5. check the wifi driver reload. leave driver2 blank
6. then scroll down to mms clamping and check that and check routing fix--that's it it should work now.
Aldo101t said:
you don't need a plan:
1. open the tethering app
2. go to settings
3. select change device profile and check generic ICS/JB wlan0
4.enable wifi encryption---set your password
5. check the wifi driver reload. leave driver2 blank
6. then scroll down to mms clamping and check that and check routing fix--that's it it should work now.
Click to expand...
Click to collapse
Thanks i found this post and it explained that too http://forum.xda-developers.com/showthread.php?p=42950480#post42950480
thanks for the response
This will permanently enable LTE on the Nexus 4 running any Android 5.0 ROM. As long the hybrid radio is present, and a factory reset is not performed, LTE should remain enabled after reboots and ROM flashes.
Note: This mod also used to modify iptables to allow tethering over LTE on Canadian carriers, Bell, Rogers and Telus; however, these modifications are no longer necessary on Android 5.0. Nevertheless, please post if you have any problems tethering over LTE.
What it does
Flashes .33/1.04 hybrid radio
Modifies settings.db to permanently enable LTE
Requirements
Custom recovery (permanent or temporary)
Any Android 5.0+ ROM
LTE Band 4 (1700 MHz) AWS-enabled SIM and service provider
Installation
Download the installation ZIP found below to your device, flash from recovery, and reboot.
After flashing, enable your correct LTE APN.
Uninstallation
To help with restoring your device back to stock for OTAs, I have created an uninstaller. To uninstall, download the uninstaller ZIP below to your device, flash from recovery, and reboot.
FAQ
Will this work in my country, region, or territory, provider, etc?
The Nexus 4 is only compatible with LTE Band 4 1700 MHz. Please see the List of LTE networks to see if your provider operates LTE on Band 4 1700 MHz. If your provider does not operate LTE on Band 4 1700 MHz, this fix will not work for you.
How do I install this on my Nexus 4 running stock Android 5.0+?
Detailed instructions on on how to flash this on stock Nexus 4 running Android 5.0 can be found here.
I am running CM12 or CM12-based ROM; how do I get LTE to persist following reboots?
Currently, this fix does not allow LTE to persist on CM12 or CM12-based ROMs because, we speculate, how the ROMs are compiled and this is overriding the values in settings.db. After rebooting, enable LTE by dialing *#*#INFO#*#*, select Phone information, scroll down and select LTE/GSM/CDMA auto (PRL) from the drop-down.
Download & changelog
Before flashing, please remember to make a Nandroid backup. Also, please double check the MD5 hash of the ZIP. Additionally, you can download the .md5 file and have TWRP check it for you.
INSTALLER 2014/01/07 v2.11 - Downloadhttps://github.com/marcandrews/mako-lte-and-lte-hotspot-fix/releases/tag/2.11
Update updater-script to accept 5.0.1 and 5.0.2 ROMs
UNINSTALLER 2014/01/07 v2.11u - Downloadhttps://github.com/marcandrews/mako-lte-and-lte-hotspot-fix/releases/tag/2.11u
Update updater-script to accept 5.0.1 and 5.0.2 ROMs
All versions are also available on GitHub.
Special thanks
XanSama
#netfilter guys at freenode
morrislee
cg87
partylikeaninjastar
beerbaronstatic
ramjet73
Joshua Mr PC Repair
More about the enabling LTE via settings.db
As I alluded to back in July, the build.prop edits were never required to enabled LTE.
Code:
ro.telephony.default_network=9
ro.ril.def.preferred.network=9
These lines tell the phone which network mode to try after a factory reset. This is why some LTE-enabling methods asked you to factory reset to enabled LTE but who wants to factory reset just to enabled LTE. So if you're not resetting, these lines have no effect.
Code:
telephony.lteOnGsmDevice=1
This line was to allow the selection of LTE under Network Mode, but this menu is no longer available >4.3, so this line has no effect. It was only indirectly required because that selection menu allowed you to change the preferred_network_mode value in settings.db, and this is what enables LTE and allows it to stay enabled permanently following a reboot.
So if you can change the preferred_network_mode value directly, you do not need any build.prop edits, nor do you need the Network Mode selection menu. All you need is preferred_network_mode=9 and an LTE-enabled modem/radio. This is what my LTE-enabler accomplishes.
As for the discussion about LTE sticking after ROM flashes, settings.db is located on the data partition. ROM flashable zips rarely touch the data partition, and they also rarely flash a new modem, so as long as these two remain, and you have not wiped (because wiping clears the data partition, which in turn will clear the preferred_network_mode value), LTE will stick after a ROM flash. So basically, you only need to flash my LTE-enabler after wiping.
This mod also used to modify iptables to allow tethering over LTE on Canadian carriers, Bell, Rogers and Telus; however, these modifications are no longer necessary on Android 5.0. I will leave information on those modifications here:
More about the LTE tethering fix
Since the Nexus 4 LTE hack was discovered, people on networks other then T-Mobile have been struggling to enable tethering over LTE. Pre-4.3, the solution was an iptables script to allow LTE tethering through the firewall. This solution no longer works for 4.3+. I have updated the script to allow LTE tethering through the firewall in 4.3+. My LTE fix applies the following changes:
Code:
iptables -D natctrl_FORWARD -j DROP
iptables -t nat -A natctrl_nat_POSTROUTING -o rmnet_usb0 -j MASQUERADE
The other issue is that this script had to be run each and every boot. Placing the commands within an init.d script does not work because at the time init.d scripts are run in the boot, the natctrl_nat_POSTROUTING rule does not exist, so you cannot append to it. Even if you do create the rule and append to it, the changes will be overwritten when the rules are set later in the boot. The solution is to run the commands within a delayed subshell that alters the firewall after the rules are set. This is what my LTE fix does:
Code:
(
sleep 15
iptables -D natctrl_FORWARD -j DROP
iptables -t nat -A natctrl_nat_POSTROUTING -o rmnet_usb0 -j MASQUERADE
)
More information on GitHub.
It's weird. I have 4g lte after flashing this over Paranoid android latest rom. I changed APN to fast.t-mobile.com. But:
1. My speedtest.net app only shows server 50km and further away. Not location Bay Area where I live.
2. There is no option to change Network mode.
sieudaochich said:
It's weird. I have 4g lte after flashing this over Paranoid android latest rom. I changed APN to fast.t-mobile.com. But:
1. My speedtest.net app only shows server 50km and further away. Not location Bay Area where I live.
2. There is no option to change Network mode.
Click to expand...
Click to collapse
Interesting.
1. I have no issues with GPS. Is GPS working in other apps?
2. Can you post your build.prop? Apparently Network mode is missing from the latest PA. To get around this, dial *#*#INFO#*#*, select Phone information, scroll down and select LTE/GSM/CDMA auto (PRL) from the drop-down.
I hope this helps.
LTE tethering has always worked for me on tmobile, no matter what app I use....not sure why this would be needed?
hp420 said:
LTE tethering has always worked for me on tmobile, no matter what app I use....not sure why this would be needed?
Click to expand...
Click to collapse
Not everyone is on T-Mobile, and the fact is that people have been struggling with tethering over LTE with the Nexus 4 long before T-Mobile even had their LTE network.
Thanks for your work *child. I'm on Rogers and tethering over LTE does not work for me using the 33_84hybridLTE_enablerV2.zip file. I'll let you know how I fare....
Update: Your tethering fix does appear to work. Thanks! All settings are retained after reboot and power down scenarios. Wi-Fi and BT tethering both work, but the BT tethering is extremely slow. I'm not sure why this is but it works. Regardless, your fix was definitely the ticket!
I am running a N4 with CM 10.2 August 21st nightly and Franco 176 JSS kernel. I am on Rogers LTE in Canada.
Tethering tested on N7 32GB v1 running stock JB 4.3
Glad it worked out for you!
Perfect!
This finally fixed all my tehtering problems on rogers. Thanks a lot!!
I'm working on an update. Just waiting for the next CM Nightly to test, and then I'll upload it.
*child said:
I'm working on an update. Just waiting for the next CM Nightly to test, and then I'll upload it.
Click to expand...
Click to collapse
What's planned in your update?
WK446 said:
What's planned in your update?
Click to expand...
Click to collapse
Fix permissions on the init.d script, set ro.telephony.default_network and ro.ril.def.preferred.network to 10 (instead of 9), conditional build.prop edits to prevent duplicate entries, and an uninstaller.
Sounds great *child!
doesn't work for me on t-mobile sadly, i'm on the latest PA...sends me straight to the t-mobile tether block page
You Sir are my hero! Been myself trying to fix this. I applied your fox differently though. I used the process here: http://hippowise.com/how-to-fix-lte-wifi-tethering-for-the-nexus-4/ then just replaced the script worth your two lines and presto, LTE tether works now on Fido. I'm on a Stock ROM BTW.
Thanks again.
*child said:
About the LTE tethering fix
Since the Nexus 4 LTE hack was discovered, people on networks other then T-Mobile have been struggling to enable tethering over LTE. Pre-4.3, the solution was an iptables script to allow LTE tethering through the firewall. This solution no longer works for 4.3. I have updated the script to allow LTE tethering through the firewall in 4.3. My LTE fix applies the following changes:
Code:
iptables -D natctrl_FORWARD -j DROP
iptables -t nat -A natctrl_nat_POSTROUTING -o rmnet_usb0 -j MASQUERADE
The other issue is that this script had to be run each and every boot. Placing the commands within an init.d script does not work because at the time init.d scripts are run in the boot, the natctrl_nat_POSTROUTING rule does not exist, so you cannot append to it. Even if you do create the rule and append to it, the changes will be overwritten when the rules are set later in the boot. The solution is to run the commands within a delayed subshell that alters the firewall after the rules are set. This is what my LTE fix does:
Code:
(
sleep 15
iptables -D natctrl_FORWARD -j DROP
iptables -t nat -A natctrl_nat_POSTROUTING -o rmnet_usb0 -j MASQUERADE
)
Now why tethering works over some networks, mainly T-Mobile, and not others is beyond me.
Click to expand...
Click to collapse
caaznkid said:
doesn't work for me on t-mobile sadly, i'm on the latest PA...sends me straight to the t-mobile tether block page
Click to expand...
Click to collapse
Since the website actually loads, sounds like tethering is working perfectly. It's just that T-Mobile has blocked tethering. T-Mobile may be blocking non-mobile browsers. You need to use a proxy or change your user agent. Google is your friend.
djsherif said:
You Sir are my hero! Been myself trying to fix this. I applied your fox differently though. I used the process here: http://hippowise.com/how-to-fix-lte-wifi-tethering-for-the-nexus-4/ then just replaced the script worth your two lines and presto, LTE tether works now on Fido. I'm on a Stock ROM BTW.
Click to expand...
Click to collapse
Yes, if you're on a rooted stock with no init.d support, your only option is to either manually apply the tethering fix via Terminal Emulator after each boot, or use Script Manager to automatically do it for you at boot. Anyway, I'm happy that it has worked for you.
Hi what network is number 10? , because i think lte is 24..
*child said:
Fix permissions on the init.d script, set ro.telephony.default_network and ro.ril.def.preferred.network to 10 (instead of 9), conditional build.prop edits to prevent duplicate entries, and an uninstaller.
Click to expand...
Click to collapse
Question from a noob
Hi All, what exactly is a "LTE tethering"? I know about the "Portable Wi-Fi hotspot" feature in Nexus 4 but I think that feature doesn't care if our phone gets the Internet access through LTE or H+ or H.
Thanks a lot for this, fixed my tethering issues on 4.3. LTE and 3G/H+ WiFi tethering works great. (Rogers Canada).
portis said:
Hi what network is number 10? , because i think lte is 24..
Click to expand...
Click to collapse
If you dial *#*#INFO#*#*, select Phone information, and expand the drop-down, you will see that the first item in the list is WCDMA preferred (=0), the last item is Unknown (=12), and the third-to-last item is LTE/GSM/CDMA auto (PRL) (=10). There is no 24th value in the list. It does not really matter anyway as these to build.prop edits only come into effect after a factory reset, which is necessary. Only the Network mode setting matters.
dxxvi said:
Hi All, what exactly is a "LTE tethering"? I know about the "Portable Wi-Fi hotspot" feature in Nexus 4 but I think that feature doesn't care if our phone gets the Internet access through LTE or H+ or H.
Click to expand...
Click to collapse
Yes, LTE tethering is the same as Portable Wi-Fi hotspot. I am not exactly sure, but I think that because the Nexus 4 was never meant to have LTE, the firewall rules for tethering through LTE were never added, therefore blocking the transfer of data between the LTE and Wi-Fi radios. I really have no idea why LTE tethering still works without these firewall edits on T-Mobile, and not on others like Rogers.
I hope this sheds some light on the situation.
Hi. When I changed in settings network mode to 2G only, signal icon started to flicker. After reboot I have no signal at all (it is impossible to call, send/receive SMS, use data connection etc.). In info (*#*#4636#*#*) preferred mode is set to "WCDMA preferred" and I cannot change it - I can chose another value from list but changes are not saved.
In settings phone says that none of SIM cards are inserted - but I can now access SIM 1 settings. However, everything is blocked and beneath the network type there is a description: "Invalid Network Mode (-1). Ignore.".
It happend when I was on latest official CM 13.0 nightly but this is probably not ROM's fault. Problem didn't disappear after clean flash, after restore or even after flashing whole set of images with official MiFlash tool.
After some research I found that setting ro.telephony.default_network from 22,22 to 10,10 should work, as 10 is for "LTE/GSM auto" when 22 is incorrect value. Separated by comma for two SIM slots. Ok, so I tried to edit build.prop with some apps without luck - access denied (rooted). I tried to mount system rw from Root explorer - nothing happens, still ro. From ADB - no, "dev/block/bootdevice/by-name/system is read-only". I even tried to change SELinux to permissive but still nothing
Every idea is welcome, I just need to get my phone to work as a phone again
Tether used to work fine on Nougat, then in Oreo and Pie, google baked-in the inability to add "dun" to an apn whether existing or new, resulting in an error message of "carrier does not allow apns of type dun." This resulted in a really slow, erratic tether function in the ROMs I tried.
Anyone found a ROM, or kernel, or know of a dev that is actively adding the same functionality as was present on Nougat--that is, tethering worked properly out of the box, or adding dun to the apn makes it work properly? I know for a fact that SOME Oreo and Pie ROMs now allow one to add the dun parameter to the apn, but it still didn't make tethering fast and stable like before.
lineageos
I'm a little surprised no one else has weighed in on this--it is as if @namanjr and I the only ones who have an interest in tethering.
namanjr said:
lineageos
Click to expand...
Click to collapse
Incorrect.
Neither LOS 15 (Oreo) nor LOS 16 (Pie) tether as well as Nougat, and neither allow the dun parameter to be written into the APN. Their tether speed is less than 1/10 of the speed with Nougat.
Furthermore, using either one of them will probably result in the downgrade "Encryption Unsuccessful" error in attempting to re-flash Nougat, meaning that the only way to downgrade is to format interior storage.
pbergonzi said:
Incorrect.
Neither LOS 15 (Oreo) nor LOS 16 (Pie) tether as well as Nougat, and neither allow the dun parameter to be written into the APN. Their tether speed is less than 1/10 of the speed with Nougat.
Furthermore, using either one of them will probably result in the downgrade "Encryption Unsuccessful" error in attempting to re-flash Nougat, meaning that the only way to downgrade is to format interior storage.
Click to expand...
Click to collapse
You have to use the CLI tools or edit the xml with all the APN.
Try "settings put global tether_dun_required 0" in adb shell or terminal emulator.
Something like "settings put global tether_dun_apn APNHERE" would manually add a APN+DUN if you know the input format of the command. Just turn data off and on after and test hotspot.
namanjr said:
You have to use the CLI tools or edit the xml with all the APN.
Try "settings put global tether_dun_required 0" in adb shell or terminal emulator.
Something like "settings put global tether_dun_apn APNHERE" would manually add a APN+DUN if you know the input format of the command. Just turn data off and on after and test hotspot.
Click to expand...
Click to collapse
I've tried "put global..." in one or two other roms, with no success.
One of the other roms would also allow editing the APN, but even with the dun parameter, it didn't perform properly.
Did you do this to your own rom and see an effective before and after?
pbergonzi said:
I've tried "put global..." in one or two other roms, with no success.
One of the other roms would also allow editing the APN, but even with the dun parameter, it didn't perform properly.
Did you do this to your own rom and see an effective before and after?
Click to expand...
Click to collapse
I edited /system/etc/apns-conf.xml manually. Copy and paste your existing APN and change the name, then edit it to allow tethering. You will loose changes when updating unless you make a backup script for it, a magisk module, or get you or a dev to add it to a rom.
namanjr said:
I edited /system/etc/apns-conf.xml manually. Copy and paste your existing APN and change the name, then edit it to allow tethering. You will loose changes when updating unless you make a backup script for it, a magisk module, or get you or a dev to add it to a rom.
Click to expand...
Click to collapse
Thanks. If I decide to upgrade to pie again, I will do this.
Dirty Unicorns V13 (Pie)
ZVNexus said:
Dirty Unicorns V13 (Pie)
Click to expand...
Click to collapse
Thank you. Can you tell me or show a screenshot of your tether download speed with (and/or without) the DU rom or with the dun parameter in/absent from the apn, illustrating the difference in quality?
I am lax to immediately install another P rom knowing that if I need to come back to N, there is extra work/risk involved.
Hey, I've also been struggling in this boat for a few months now. Went from a nexus 6p with Los 14.1 to the oneplus 3t. Only rom available at the time was 15.1 , which I remember kind of sucked when it first came out the gate on the nexus 6p, so I was hesitant to use it. Quickly ran into this issue where the tethering speed was dramatically terrible. For months I've just assumed it was the oneplus 3t's fault. Maybe the radio is weaker, or my carrier doesn't approve of this Chinese import versus the other...
I bounced between Stock, Ice Cold, and Los trying to find the best settings for the best result. With my carrier (tmo) the trick was to make a new apn and set it up to use a different address, meant for devices without lte support. "epc.tmobile.com" . This immediately made everything fast again, however it sort of pipelines any tethering activity. So like it would have the good expected transfer rate with one thing, but if you tried to load anything else, that thing would hang until the first thing finished transferring.
I'm glad I finally caught wind of this question/thread. It's relieving to know that it's just because google f***ed with something in oreo and pie, and not that Los suddenly updated into inconvenience. I'm going to try Dirty Unicorns 13 as ZVNexus suggested, and will report back to you with results. Also if any of you can help better articulate this 'global dun 0 apns-conf.xml trick' for me that'd be great and I'll gladly try that out and give results. I flashed magisk and navigated to the apns-conf.xml file just to be suddenly reminded I have no idea what on earth I'm looking at.
** Dirty Unicorns 13 Result
A big maybe? Tmobile out of the box shoots down tethering speed to ~70 kb/s . I usually use the TTL trick to work around this, but that requires I set/use any APN protocol to IPv4. For whatever purposes, the version I tried (du_oneplus3-v13.0-20190109-0432-RC) doesn't allow you to edit the initial APN settings, however I can see that it has "dun" listed in the types. Inconvenient, but I figured whatever I'll just make my own BUT NO. It won't let you save a new APN with dun anywhere in the types. So in the end I can't give any solid result, sorry. If it means anything the upload speed was good, so this could be an issue exclusive to my carrier.