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.
Related
AOKP JB Rom with Stock ICS Kernel
The one on rombot is a couple of days old so I have updated with one I build on 10/16.
Built from Hashcode and DHackers source. Give thanks to them!
Read this thread on how to install and thank Hashcode: http://forum.xda-developers.com/showthread.php?t=1886935
Link to Droid 4 folder with some roms, inverted gapps, safestrap, tools, etc:
https://www.dropbox.com/sh/mhmmrku5e4x8boj/hbd5BE-Nae or here: http://d-h.st/users/jsnweitzel
Use safestrap 3.05
Android 4.1.2
Working Camera now, no flash though.
As usually doing this stuff can break your device.
Thanks for this! Just finished DLing. Going to back up and test it out.
russia. megafon. No connection to the Internet. To create APN does not change anything.
hows the battery life?
For some reason every time I download the ROM then try to either install it safe-side on Safestrap 2.11 it won't open. I also notice that I'm unable to open the archive on my computer as thought the file is corrupt?
I just updated the op with a build I did this morning.
hi, i just flashed this ROM but i noticed my pictures from my SD card isn't showing up in my gallery, I tried googling it and its supposed to be a known issue for jellybean, i tried a few different things but nothing worked so now i'm using Quickpic.
but is there a way to connect the Quickpic app to the camera app or a way for the stock gallery app to rescan for all the pictures?
I don't seem to be having any trouble with reading my pics from the external sdcard.
The keyboard lights don't come on after the phone wakes up.
AOKP GSM edition, stock kernel. works fine.
http://d-h.st/rFH
olegfusion said:
AOKP GSM edition, stock kernel. works fine.
http://d-h.st/rFH
Click to expand...
Click to collapse
I didn't get mobile data with your build until editing build.prop.
Code:
--- build.pbak
+++ build.prop
@@ -139,7 +139,7 @@
# could use this property too. IKMAIN-732
#1 this is verizon wireless globle phone
#0 this is not verizon wireless globle phone
-ro.mot.phonemode.vzwglobalphone=0
+ro.mot.phonemode.vzw4gobalphone=1
# END Motorola, nfjb73, 21-jun-2010, IKMAIN-732
# BEGIN Motorola, nfjb73 23-jun-2010, IKMAIN-624
@@ -325,8 +325,7 @@
ro.cdma.subscribe_on_ruim_ready=true
persist.sys.moto_oem_telephony=false
persist.sys.moto_imsi_fix=false
-ro.config.not_world_phone=true
-
+ro.config.not_world_phone=false
#
# ADDITIONAL_BUILD_PROPERTIES
#
@@ -357,3 +356,13 @@
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
+
+ro.ril.hsxpa=3
+ro.ril.gprsclass=12
+ro.ril.hep=1
+ro.ril.enable.dtm=1
+ro.ril.hsdpa.category=28
+ro.ril.enable.a53=1
+ro.ril.enable.3g.prefix=1
+ro.ril.hsupa.category=7
+
Not sure the ro.ril settings were absolutely needed. But no APNs showed up until I changed the world mode settings.
Also something is wrong with your keymap. The capslock and OK buttons don't do anything in Connectbot. OK should be DPAD Enter. CapsLock could be ALT, since it's not really needed for itself. (Shift-Shift is already caps lock after all.)
I don't think the caps lock and ok key work in any of the jb roms. You can double click the shift key for all caps. Anyone have them working?
Never mind the build.prop settings, they may be a red herring. It looks like every other reboot, data fails because the RIL is unable to read the IMSI because the SIM card isn't ready yet when it tries.
I've also found that I can successfully reset the RIL and get data working by going into Airplane mode, then in a root shell kill the existing rild, which forces it to restart. After it restarts toggle back out of Airplane mode and data is working.
Back to keymaps - also the arrow keys are all set to the wrong directions. I've manually edited my omap4-keypad.kl file to fix these issues.
jsnweitzel said:
I don't think the caps lock and ok key work in any of the jb roms. You can double click the shift key for all caps. Anyone have them working?
Click to expand...
Click to collapse
After I straightened out the arrow keys, the OK key started working as usual in Connectbot. It must have been looking for a particular layout and giving up when it didn't see what it expected.
I've found that setting CapsLock to Alt doesn't actually do anything useful, probably because nothing in the Keymaps file has anything defined for its Alt position.
Oh, and the CapsLock key wasn't working because the file had "CAPS" but the correct keyword is "CAPS_LOCK" - so it's working for that on mine now.
The SYM key used to bring up a dialog box with special characters, now it just brings up a dialog to select Input Method. That appears to be a JB-specific thing. Makes it pretty useless.
highlandsun said:
After I straightened out the arrow keys, the OK key started working as usual in Connectbot. It must have been looking for a particular layout and giving up when it didn't see what it expected.
I've found that setting CapsLock to Alt doesn't actually do anything useful, probably because nothing in the Keymaps file has anything defined for its Alt position.
Oh, and the CapsLock key wasn't working because the file had "CAPS" but the correct keyword is "CAPS_LOCK" - so it's working for that on mine now.
The SYM key used to bring up a dialog box with special characters, now it just brings up a dialog to select Input Method. That appears to be a JB-specific thing. Makes it pretty useless.
Click to expand...
Click to collapse
Can you email me these changes so that I can merge them into the mainline? Or feel free to submit a pull request on github?
highlandsun said:
Never mind the build.prop settings, they may be a red herring. It looks like every other reboot, data fails because the RIL is unable to read the IMSI because the SIM card isn't ready yet when it tries.
I've also found that I can successfully reset the RIL and get data working by going into Airplane mode, then in a root shell kill the existing rild, which forces it to restart. After it restarts toggle back out of Airplane mode and data is working.
Back to keymaps - also the arrow keys are all set to the wrong directions. I've manually edited my omap4-keypad.kl file to fix these issues.
Click to expand...
Click to collapse
On the RIL settings for GSM:
I can enable the new build.prop values DHacker has been working on which add the same data toggles specifically for these fixes. Allows the user to enable/disable certain RIL features via settings until it works right.
Hashcode said:
Can you email me these changes so that I can merge them into the mainline? Or feel free to submit a pull request on github?
Click to expand...
Click to collapse
PM'd you the diff. Let me know if you'd prefer it some other way.
Hashcode has put a new build up here: http://goo.im/devs/Hashcode/maserati/aokp/STOCK-JB-aokp_maserati_unofficial_Oct-18-12.zip
Haven't found a changelog. Anyone tried this on GSM yet. Does it work, or do we have to wait for Olegfusion to do his magic?
Lum_UK said:
Hashcode has put a new build up here: http://goo.im/devs/Hashcode/maserati/aokp/STOCK-JB-aokp_maserati_unofficial_Oct-18-12.zip
Haven't found a changelog. Anyone tried this on GSM yet. Does it work, or do we have to wait for Olegfusion to do his magic?
Click to expand...
Click to collapse
Hope in the changelog the earpiece volume is fixed, it is way too low. I end up having to put people on speaker phone just to hear them.
Just wanted to give this thread a bump and say THANK YOU to jsnweitzel for throwing these new builds out and feeding my crack flashing addiction!
Unofficial CyanogenMod 10.2 for the Kindle Fire HD 8.9 LTE
THIS THREAD IS SPECIFIC TO THE LTE VARIANT OF THE KINDLE FIRE HD 8.9". IF YOU HAVE A STANDARD 8.9" MODEL USE THIS THREAD:
http://forum.xda-developers.com/showthread.php?t=2388352
*** USE AT YOUR OWN RISK! WHILE I TRY MY BEST TO PROVIDE WORKING KERNELS/ROMS, I AM NOT RESPONSIBLE IF THIS SOFTWARE OR ANYTHING I'VE WORKED ON SUDDENLY FRIES YOUR DEVICE. ***
**** I DO NOT OWN THE LTE VARIANT OF THE KINDLE FIRE HD 8.9", SO THIS ROM WILL BE A WORK IN-PROGRESS. IF YOU'RE THE EASILY FRUSTRATED TYPE, YOU MAY WANT TO HOLD OFF. ****
BEFORE YOU BEGIN MAKE SURE YOU HAVE A 2ND-BOOTLOADER INSTALLED CORRECTLY AND CAN SEE THE BLUE LOGO DURING BOOTUP:
http://forum.xda-developers.com/showthread.php?t=2128175
LTE MODEL Download Information:
[LATEST][08/07 #3] BETA CM10.2 + 3.0.50+ KERNEL
Mirror 1: http://goo.im/devs/Hashcode/jemlte/cm10.2/cm-10.2-20130807-UNOFFICIAL-jemlte.zip
md5sum: d499384a940dffb3ca7e6ac512fcf370
Older builds can be found in the same folder on goo.im:
http://goo.im/devs/Hashcode/jemlte/cm10.2/
Download Google Apps:
http://goo.im/devs/Hashcode/gapps
(For Android 4.3)
PLEASE BE SURE TO WIPE SYSTEM & DATA/CACHE (FACTORY RESET) WHEN COMING FROM AMAZON STOCK SOFTWARE.
(It's the "Wipe" button and then "System" and then "Factory Reset" button in TWRP -- this does NOT clear your sdcard space)
Be aware that the "sdcard" space has changed slightly from ICS to JB4.2. You will find your stock amazon OS files in /data/media/ or "sdcard" on the Stock OS. But CM10.1 will create a sub directory "/data/media/0" and call that "sdcard". And in TWRP it will also use "data/media/0" as "sdcard". This has to do with multi-user settings. So when placing files on the "sdcard" be sure to check both locations before wondering why that file is missing.
CHANGES:
[08/04] First CM10.2 build for Jem LTE
[07/31] Added RIL setup for LTE
[07/31] First CM10.2 build for Jem
FEATURES:
3.0.50 kernel (up from a stock 3.0.21 kernel). This includes updates from Texas Instruments, Google and Kernel.org.
PowerVR Graphics Drivers: DDK [email protected] for Android (Jellybean compatible)
Updated bltsville libs to 2.2.2.0 (this is partial screen update code which enables smoother / faster screen draws)
Audio
Camera
Wifi
Bluetooth
Sensors
HWAcceleration
HD Codecs for YouTubeHD and Netflix
HDMI video out is now correct and work across several resolutions. YMMV
DEVS
BUILDING THIS ROM:
First, read through Google's Android website about "how to setup a build environment":
http://source.android.com/source/initializing.html
[ COMING SOON ]
SCREEN SHOTS:
FOR BUGS / TROUBLESHOOTING:
I need the output from:
adb logcat -b radio > logcat-radio.txt
SAME BUGS AS THE STANDARD VERSION OF KINDLE FIRE HD 8.9"
CURRENT KNOWN ISSUES:
Benchmarks are quite LOW at the moment due to lack of bionic optimizations for OMAP in 4.3. This will probably get worked out over time. DONT COMPLAIN ABOUT BENCHMARKS. YOU HAVE BEEN WARNED.
When long pressing icons in landscape mode to move them, etc the screen will flip upside down for a moment and right itself. This causes the action to be aborted.
Rotation selection in games is hit and miss. Some work perfectly and some like to flip the device upside down. Still debugging what is causing this.
AUDIO: Any decoder which uses Dolby surround current has a lower volume than the rest of the system (Netflix, Google Movies, etc). It's a WIP.
3D Performance: Is only OK. Needs some troubleshooting and perhaps kernel cleanup. Work-In-Progress.
Sensors: Testing various sensors, gyro seems 90 degrees off, etc.
I don't have an LTE version so this is not enabled in current builds.
Great news! Thank you very much.
logcat-radio as you request.
logcat-radio in attachment.
I get it on stock rom.
Thank you.
No LTE setting
Intalled.
But i can't find LTE setting.
GPS not work too.
Bluetooth can't turn on.
tethien said:
Intalled.
But i can't find LTE setting.
Click to expand...
Click to collapse
Same here. Don't have mobile data options under "setting-data usage".
But still many thanks to hashcode! ...and willing to continue testing.
logcat-radio get on this rom
in attachment
I found some issues with my first build and I'll be putting up #2 here in a bit once I iron out some other changes I currently have going.
Hashcode said:
I found some issues with my first build and I'll be putting up #2 here in a bit once I iron out some other changes I currently have going.
Click to expand...
Click to collapse
Sweet!
Updated OP w/ test #2:
LTE MODEL Download Information:
[LATEST][08/06] BETA CM10.2 + 3.0.50+ KERNEL
Mirror 1: http://goo.im/devs/Hashcode/jemlte/cm10.2/cm-10.2-20130806-UNOFFICIAL-jemlte.zip
md5sum: d2d0be88c07ca9623d3b87e03797a33e
This ROM has a few notable changes:
- It's using the new sensor hardware layer (from source!) which is almost -- but not quite done. So for now, the ambient light sensor doesn't work. All other sensors work. Tho, the gyro still has mixed X and Y axis.
- I did some comparisons to the regular JEM build and noted that rild, the gsm permissions, MMS.apk and Phone.apk are in this build. Obviously, once things start working, I'll want to remove some of that as it doesn't apply but for now thats a good sign.
I need a new logcat -b radio of this build.
Tks god now I can post -_-
Thank you @Hashcode for trying to build rom for us
I follow topic every hour and I have some infomation for you:
-Your first LTE build has nothing about mobile network.
-Your second one has a setting named: emegency alert and setting about which situation and action.
-The Messenger app can't send a messenger to another number.
-No sign of mobile signal, nothing, no data roaming on off, no apn etc ...
-Call at lockscreen doesn't work.
I've tried many rom, but the rom that LTE network worked is stock 8.1.4 that has APN adding option (I'm living in Vietnam so I used local network operator here). The Stari-rom doesn't has APN option but still has network system and can recieve sms.
/// I've just tried to install your 8.4.3 stock rom zip, ithe 3G network worked
Thanks for the input. Did you by chance get the output from "adb logcat -b radio > logcat-radio.txt"?
Sent from my XT926 using Tapatalk 2
installed 0806 rom. still no mobile data options under "Settings - Data usage"
however, under "Settings - more...", there is line saying "cell Broadcasts".
i'm away from home on a business trip. will do the logcat once getting back to the bay area.
thanks a lot, hashcode!
Logcat radio from 0806 rom
As you request.
Thank.
Updated the OP with a new TEST build:
LTE MODEL Download Information:
[LATEST][08/07 #3] BETA CM10.2 + 3.0.50+ KERNEL
Mirror 1: http://goo.im/devs/Hashcode/jemlte/cm10.2/cm-10.2-20130807-UNOFFICIAL-jemlte.zip
md5sum: d499384a940dffb3ca7e6ac512fcf370
CHANGES:
Fixed the overlay so that mobile data is supported by the OS
Using CM apns.conf file now (it includes the 2x ATT entries from the stock file)
Changed from a "phone" style build to a tablet + mobile data set of packages (No Dialer / MMS)
Need a new: adb logcat -b radio > logcat-radio.txt
Thanks!
The new rom has a Mobile networks settings, but no signal. Maybe this park is for the smartphone hardware and not for tablets. Cuz I see Network Operater doesn't show up at status bar, just a triangle with nothing. And when I was in the network operations setting, it scan for network, manage mobile plan doesn't recognize sim (the stock 8.4.3 does). Or maybe it just setup for AT&T network?
I don't know why I can't get the log file, my computer does recognize as ADB, but when I tried to log, it said waiting for device.
Your rom is improved every update ^^
thanks for your work, bro.
logcat radio from 0807 ROM
waiting your new rom!
gamer941 said:
The new rom has a Mobile networks settings, but no signal. Maybe this park is for the smartphone hardware and not for tablets. Cuz I see Network Operater doesn't show up at status bar, just a triangle with nothing. And when I was in the network operations setting, it scan for network, manage mobile plan doesn't recognize sim (the stock 8.4.3 does). Or maybe it just setup for AT&T network?
I don't know why I can't get the log file, my computer does recognize as ADB, but when I tried to log, it said waiting for device.
Your rom is improved every update ^^
thanks for your work, bro.
Click to expand...
Click to collapse
You must enable "USB debugging" under "Developer option" before run adb command.
Go to Setting/About tablet the press 7 time to "Build number" line. "Developer option" will appear on left menu.
tethien said:
You must enable "USB debugging" under "Developer option" before run adb command.
Go to Setting/About tablet the press 7 time to "Build number" line. "Developer option" will appear on left menu.
Click to expand...
Click to collapse
Oh that's it
I just a newbie started to use android :victory:
tethien said:
waiting your new rom!
Click to expand...
Click to collapse
I'm seeing lines like this in your radio logcat:
W/use-Rlog/RLOG-RIL_VDR( 134): ril_oem.c:194 Failed to set mtu::rc=1,0, cmd=[echo 1400 > /sys/class/net/rmnet0/mtu]
E/use-Rlog/RLOG-RIL_ODL( 134): pktio.c:271 cant open device: device=/dev/ttyUSB0, errno=13
Can you check the following in adb and post it for me?
ls -l /sys/class/net/
ls -l /dev/ttyUSB*
Thanks
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.
The S2 wifi blobs have now been incorporated into the Aug 25 17.1 builds.
Please take 10 minutes to read all of post #1 and #2. lpedia and I have spent 5 days troubleshooting this together and want to present our wifi findings. DO NOT USE this thread to report any other problems, it's only for exynos5433 S2 tablet wifi. If this is unreasonable, then stop reading. Thank you.
If your device's wifi is not connecting after a restart and/or wake from sleep, and/or dropping out at random, this could be because the 17.1 code is using Samsung Galaxy S6 wifi blobs instead of its stock S2 wifi blobs. This commit was made in 17.1 at
gts2: Import Galaxy S6 BCM4358 firmware · universal5433/[email protected]
@lpedia has confirmed that LineageOS 17.1 on his T710 has the wifi problems when using S6 blobs, but not after the S6 blobs have been replaced with stock S2 blobs. This appears to fix both non-connection at boot and not reconnecting on wake from sleep. Random dropouts are less common and were not seen during the limited testing, so it's not certain that they're gone.
FAQ
Q1. Will changing from S6 wifi blobs solve all my wifi no reconnect or disconnect problems?
A1. This has only been tested on the T710, and there's no guarantee it will help the other devices. If you want to try, follow the instructions below. Before you try, make sure to back up all your data. The following should write the stock S2 blobs to the /system partition only, but if you make a mistake you could lose your data! Back up first.
It's an easy test to see if the stock S2 blobs will help or not. If your current rom does not connect to wifi after a restart, try our proposed solution. Before you do, reboot your current rom 5 times in a row. After each reboot, see if your wifi connects. After you install stock S2 blobs, reboot your device again 5 times in a row and see if wifi connects. This will easily tell you if the S2 stock blobs have solved this one particular problem or not.
As for wifi not connecting after long/deep sleep, you should notice over 2 or 3 days if wifi connects or not after deep sleep.
Q2. Will this work on SM-T710, SM-T810, etc?
A2. Same answer as A1. It should work on any S2 tablet exynos5433 device that uses the S6 wifi blobs that are the default in 17.1 or Android 10. These instructions are only for exynos5433 devices.
As the thread grows bigger, you can see who is responding back with either positive or negative feedback and what model they have.
Q3. Will this work on RR, Havoc or LineageOS (Android 10 or 17.1)?
A3. The instructions below replace the S6 blobs with the original stock S2 blobs. The instructions provided should work regardless if it's Havoc, RR or LineageOS. All these variant OSes share the same repo (i.e. code and blobs) on github.
Q4. Is this post relevant to Android 9 or LineageOS 16.0?
A4. NO. The github repos show that Android 9 or LineageOS 16.0 used the stock S2 wifi blobs. This was changed to S6 wifi blobs in Android 10 or LineageOS 17.1. I don't know why it was changed to S6 blobs as I'm not involved with that change.
Q5. Why do I need my model and code name?
A5. In order to follow the instructions below, you need to know your model number and it's code name. The model number or device name is settings, about tablet.
You can find the code name at (scroll almost all the way down to the bottom)
Samsung
This is the Team Win website and the official home of TWRP! Here you will find the list of officially supported devices and instructions for installing TWRP on those devices.
twrp.me
For example, SM-T710 is gts28wifi.
Q6. Does it matter if my wifi is 2.4Ghz or 5Ghz or a mix of both?
A6. When reporting back to us, please state whether your network is 2.4Ghz only, 5Ghz only, or a mix of 2.4Ghz and 5Ghz. In addition, if its a mix, please let us know if it's one wifi network (same ssid) or two separate wifi networks. That is, 2.4Ghz is one ssid and 5Ghz is another ssid.
Q7. If this works, how will this be fixed for the next release of code and the future?
A7. If enough people say it fixes their wifi problems, I can submit a git pull request to Anan to revert the S6 wifi blobs back to S2 wifi blobs.
Instructions
1. Make sure adb debugging is enabled in developer options. To enable developer options, tap settings, about tablet, build number 7 times until it says developer options unlocked. Go back to settings, system, advanced, developer options, enable android debugging and rooted debugging.
Note if you are running Magisk, see posts regarding Magisk if you cannot see rooted debugging.
2. You will need git. There are instructions and download links for installing git on Windows, MacOS, and Linux at Git Guides - install git | GitHub.
3. After you install git, follow the instructions exactly below.
Bash:
# make temporary vendor directory
mkdir temp
# cd to that directory
cd temp
# git the 16.0 stock drivers
git clone https://github.com/universal5433/proprietary_vendor_samsung -b lineage-16.0
# change directory to proprietary_vendor_samsung/<your device>/proprietary/system/vendor/etc
# or if Windows, to proprietary_vendor_samsung\<your device>\proprietary\system\vendor\etc
# where "<your device>" is your device's code, for example gts28wifi for the T710:
cd proprietary_vendor_samsung/gts28wifi/proprietary/system/vendor/etc
# start adb root
adb root
# remount /system as rw (it's read only by default)
adb remount
# start adb shell
adb shell
# delete S6 blobs from wifi directory
cd /system/vendor/etc/wifi
rm bcm*
rm nvr*
# There should be only .conf files left now
ls -al
exit
# you should be back at your desktop terminal prompt now
# now push all stock drivers to /system/vendor/etc/wifi
adb push wifi /system/vendor/etc
# check to make sure it got pushed okay
adb shell ls -al /system/vendor/etc/wifi
# now reboot Android
adb reboot
If the above does not work for you, or if it causes other problems, just reflash the last rom. That will overwrite the /system partition and everything will be restored.
If you do try this, please report back to this thread about whatever happened and include your device and what wifi network you are running.
Reserved.
Thanks for the instructions!
I had to boot my T810 (gts210wifi) into TWRP and mount /system from there before adb root and adb remount was possible. Everything else worked as described.
Observations after 5 reboots: WiFi available after reboot each time! Much better than before!
I will observe it now for a while regarding wifi-off after sleep or sporadical wifi-off.
Btw. for the random reboots of the unmodified linageos17.1 (ripee) I'm pinging my DNS-server all 2mins using Tasker. Fixed reboots since 2 month at least on my system.
Yogi555 said:
I had to boot my T810 (gts210wifi) into TWRP and mount /system from there before adb root and adb remount was possible.
Click to expand...
Click to collapse
The above might be due to you not having adb root enabled in developer options. I will update the instructions to make sure that's enabled.
Strangely the setting seems not there in my system. But I remember that in some system its available. Can the installed Magisk be the reason?
Yogi555 said:
Strangely the setting seems not there in my system.
Click to expand...
Click to collapse
It's there.
Short update: The S2 wifi blobs are a huge improvement. With S6 blobs I had reliable dropoffs at medium router-signal combined with heavy wifi-load (no dropoffs with full router signal). With the S2 blobs no single dropoff even at weak router-signal and heavy wifi-load for several hours now.
Again, to enable developer options, tap settings, about tablet, build number 7 times until it says developer options unlocked. Go back to settings, system, advanced, developer options, enable android debugging and rooted debugging.
As I said earlier, the routed debugging option is missing in my developer-options (with installed Magisk). Everything else is looking identical to the attachement of post 6. But maybe we should not cover this thread with the different ways to adb root. The really important thing is that the proposed fix works really great! At least for me and hopefully for everybody else who is willing to try it
Yogi555 said:
As I said earlier, the routed debugging option is missing in my developer-options (with installed Magisk). Everything else is looking identical to the attachement of post 6. But maybe we should not cover this thread with the different ways to adb root. The really important thing is that the proposed fix works really great! At least for me and hopefully for everybody else who is willing to try it
Click to expand...
Click to collapse
Thanks, @Yogi555! It's great to know that replacing the blobs works on one of the other S2 models! We could only test it on gts28wifi (T710).
@Yogi555, about the Rooted debugging option: my T710 doesn't show that option, either, and I think it's because I have Magisk installed (@retiredtab doesn't).
If the device is not rooted, "adb root" temporarily restarts the adbd daemon on the device as root (there's a timeout period after which it will remove root access again).
I'm guessing that if the device is rooted, that isn't necessary - because adbd is probably already running as root . The Rooted debugging option is therefore unnecessary, and isn't shown.
In either case, when you do "adb root" on the PC, there should be a prompt on the device asking you if you want to allow access. Did you see the prompt? If you don't explicitly allow it, root access won't be given.
Also, "adb root" works on Windows (for an account that's in the Administrators group) without needing to be Run As Administrator, but I think Linux requires the command to be run as root (eg, sudo adb root).
Update2: after the night the T810 with S2 blobs was immediately connected to wifi this morning. Great!
Regarding "adb root" with Magisk: I'm running it from Win10 PC. Independent if normal commandline or commandline as administrator - after "adb root" there is no output at all, but a sound like connecting or disconnecting a device. After "adb remount" next, an error is displayed:
Not running as root. Try "adb root" first.
remount failed
Maybe my adb is too old (version 1.0.40)
However "adb reboot recovery" works and "adb root" then in TWRP as well. So strange, but no problem
Yogi555 said:
Update2: after the night the T810 with S2 blobs was immediately connected to wifi this morning. Great!
Regarding "adb root" with Magisk: I'm running it from Win10 PC. Independent if normal commandline or commandline as administrator - after "adb root" there is no output at all, but a sound like connecting or disconnecting a device.
Click to expand...
Click to collapse
Did you check the device to see if it's prompting you to allow this access? The prompt times out fairly quickly, so you might not see it if you don't check straight away. It does give a notification sound.
The prompting came yesterday at the very beginning of the activity and I allowed it (including the always checkbox). "adb device" shows the device id.
I don't understand why you'd see anything different from what I see. I use a Windows PC, I have Magisk (version 23.0) installed on the T710, and have previously allowed adb root access "always".
What I see is this:
Code:
> adb version
Android Debug Bridge version 1.0.41
Version 31.0.2-7242960
> adb root
adbd is already running as root
> adb remount
remount succeeded
> adb root
gts28wifi:/ #
I think there could be something wrong with your Magisk configuration. What version is it?
Downloaded adb version 1.0.41. Now I get "ADB Root access is disabled by system setting - enable in Settings -> System -> Developer options"
Updated Magisk from 20.4 to 22.1. and App to 23.0 => No difference :-(
In Magisk App adb is not listed in Superuser-tab. Can I add it somehow?
Yogi555 said:
Downloaded adb version 1.0.41. Now I get "ADB Root access is disabled by system setting - enable in Settings -> System -> Developer options"
Updated Magisk from 20.4 to 22.1. and App to 23.0 => No difference :-(
In Magisk App adb is not listed in Superuser-tab. Can I add it somehow?
Click to expand...
Click to collapse
I think I know what's going on now.
I've just uninstalled Magisk, and (after the enforced reboot) I can now see the "Rooted debugging" setting in Settings > System > Developer Options > Debugging.
Mine was ON, but had been hidden by Magisk's presence, as I suspected.
If you uninstall Magisk, I think you will find that your "Rooted debugging" is OFF. If so, turn it on, then try "adb root" etc. You don't need to root the device in order to use adb root functions. If you want the device to be rooted, by all means re-install Magisk - but with that setting still ON.
I'll be very interested to hear what happens.
The simplest way to check that adb root has actually given you root access is to "adb shell". The prompt will end in a "#" if the shell's running as root. As mentioned in an earlier post.
Want to also quickly confirm in here that the S2 Blobs are working real fine for me as well.
lpedia said:
I think I know what's going on now.
I've just uninstalled Magisk, and (after the enforced reboot) I can now see the "Rooted debugging" setting in Settings > System > Developer Options > Debugging.
Mine was ON, but had been hidden by Magisk's presence, as I suspected.
Click to expand...
Click to collapse
I've just re-installed Magisk and proved to myself that Magisk 23 is hiding the setting. I found that Magisk 22 didn't hide it - I re-installed using a version 22 zip that I had on hand, checked the "Rooted debugging" setting, which was still visible, then updated to Magisk 23 via the app. After the reboot, the setting had disappeared again.