Related
Greetings, I'm running a fresh flash of CM7 (final) and I'm using the built-in VPN menus (not the openvpn build off of the market or it's settings apk).
Using either tap or tun (I've flipped the server to either), I get the following error from logcat:
Code:
read UDPv4 [ECONNREFUSED]: Connection refused (code=111)
I had this working in 6.1 and copied my same settings over, recreated the p12 file from the existing crts and keys (which I saved) and no dice. I even reverted to my nandroid backup of 6.1 to try it and make sure it wasn't blocked on the network or the server was bad and it would work so it's something in my 7.0 setup.
I saw that there was a bug for 7.0 submitted and it looks like support does exist in the stock CM kernel (I don't recall pushing tun.ko for 6.1, but it's very possible, I could revert one more time and check), so I don't think i need to recompile it (as noted here) specifically to acquire the module. Last, looking at the openvpn/CM wiki entry, I see an entry pertaining to this very error that seems to allude to a problem with the tun module (and I see an entry in the CM bug tracker about it as well), but when confronted with evidence that it's working in the file version, I'm again at a loss.
Any ideas (or any other information I should provide)?
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
Hello XDA,
Im back again with another personal project I'm having some issues with. First, a bit of explanation as to why I've chosen to attempt this.
I was running a heavily modified stock rom with nethunter 5.1.0 that was incredibly unstable, and eventually crashed right out on me (modified using root based apps so the crash was my fault) .
So I grabbed the CM13 snapshot for hammerhead, and layered on nethunter 3.0 (big fan since BT3), only to find out my wifi card isn't supported. On 5.1.0 I also had this issue
(see here http://forum.xda-developers.com)/showpost.php?p=64400679
which I managed to fix with a simple source build with a few extra options checked in menuconfig.
Sadly it doesn't seem to be quite that easy with CM13 and marshmellow.
I'm using the DWA160-b2 wifi adapter, which from my research, uses the rt2800usb chipset, which supposedly points to the rt5572 driver. So, I enabled the corresponding options in menuconfig , although I cant remember the exact wording at this moment (using winblows to write this, and not my linux) and I still have no life in my wifi card.
So, after even more research, I found out I should be able to cross-compile the required drivers using the arm-eabi tools. However, after trying I've come to the conclusion that there is no arm based config for this driver. So then I tried backports, and recieved an error about incomplete linux headers (I assume because of the chroot, because my headers are all installed).
Now finally my question:
How do I go about compiling this driver for arm? Or is there a know working arm driver for this particular card? As I have not come across one in my searching. Also please dont say get a new wifi card lol I have a few different usb wifi cards, all with the same issue (albeit different chipsets).
Are u trying to port kali kexec to cm13 kernel?
Sent from my fx-82MS with CM-CAF
Hi all,
After unlocking my phone which is a global version 64gb model, I had installed CM13. Wifi was working fine previously. After CM was installed I cannot get wifi to connect. It will show authentication failed and obtaining ip but won't obtain. It shows its mac address and scans wifi just fine. I can run wifi analyzers but it just won't connect. I have tried installing other roms, even installing the original roms and re-locking the device to stock with no success. I have reset my router and verified other devices can connect as well as trying other open wifi ssid's. I have also completely formating the whole phone and reinstalled roms from scratch, again no success. I have been searching through forums for about 2 weeks now and every recommendation has not worked. I love this phone but not having wifi is killing me. I am experiencing no other issues. One clue I do have which google is not providing answers to is the error i got when CM first installed and other times which i can't determine the scenarios to recreate which is
E:Unable to write to ums lunfile '/sys/module/g_android/parameters/file'
Unable to locate storage device.
Any help would be greatly appreciated.
Thanks Much
I have the same problem. I've installed CM 21.11 and gaaps stock via TWRP 3.0.2.0 and after this wi-fi can't authenticate. I did the same steps as topic starter and also tried different wi-fi settings in router and wi-fi without pass. Nothing helped
Please help! Any thoughts can be helpful.
I have exactly same issue as OP. I did everything like him and got no result.
Please help someone. I love my MI5 but i need wifi.
I have exactly the same issue and posted about it just a little earlier
http://forum.xda-developers.com/mi-5/help/wifi-connectivity-problem-t3517777
The difference being that the WiFi was working just fine even when I installed CM 13.1 for the first time. WiFi stopped to connect when I did a full Swipe in TWRP (all partitions).
It would be great if someone could help...
Try to give a chance to CM14.1 installed after a full wipe, I am using WiFi every day with wpa2 shared key and also radius auth 2.4 and. 5 GHz without problems and the overall performances are good
I have CM 14.1 at the moment and the problem is the same.
I'm no specialist but it doesn't seems to be a ROM related issue.
In this case I would try with stock MIUI after a full format and wipe, then in case of success again with CM14.1. Format is important because with encrypted data wipe isn't enough
matteo.gspace said:
In this case I would try with stock MIUI after a full format and wipe, then in case of success again with CM14.1. Format is important because with encrypted data wipe isn't enough
Click to expand...
Click to collapse
Thanks for your assistance.
Done that but didn't solve the issue...
I had the same problem, same symptoms.
I too flashed a new ROM and couldn't connect to any AP, I tried various ROMS, MIUI 7 & 8 and CM 13 & 14.1.
Though I think I found a solution (it worked for me ). I simply changed my MAC-adress and I was able to connect to my home WiFi.
I'm running CM 14.1-2016225-NIGHTLY-gemini on MI5.
This is what I did to fix my WiFi:
First prepare an new MAC-address. I personally don't know when a MAC-address is considered valid, so I just took one from an other device. I used the mac address of my previous mobile phone, which could connect to my router.
1. Disable WiFi.
3. Enable debugger settings (Setting>about Phone>Press build number repeatedly).
2. Enable root (Develepor settings>root access set to "Apps and ADB").
3. Open the file manager app.
4. Give the file manager app root access (menu>Settings(cog in lower left corner)>General settings>Access mode set this on "Root Access mode").
5. Now find the file root/etc/firmware/wlan/qca_cld/ and open wlan_mac.bin.
You should see something similar to:
Code:
Intf0MacAddress=XXXXXXXXXXXX
Intf1MacAddress=XXXXXXXXXXXX
END
6. Change the first to your new MAC-address, but first write down the old one, so you can change it back if this method doesn't work for you.
The last X of the next line should be a digit higher than the previous line. E.g:
Code:
Intf0MacAddress=957FDC328BF[B]4[/B]
Intf1MacAddress=957FDC328BF[B]5[/B]
END
(This MAC-address most likely won't work).
7. Save the file. You might need to press the save button a few times.
8. Check if the file has changed.
9. Check if you MAC-address has changed (Settings>WiFI>Configure-WIFI(cog in right upper corner)).
10. Enable WiFi.
I hope this works for everyone that has the same problem.
I'm on MIUI EU 8.1.70 Nougat then i fastboot flash or recovery mode to MIUI Global 8.1.2.0 Marshmallow WIFI NOT WORK
But,
I managed to get the wifi working again with edl mode flashing with MIUI Global 8.1.20.
I will try to move to CM again, maybe this time wifi will work..
Wish me luck, will post the result later
RESULT:
Not Worked.
---------- Post added at 12:03 PM ---------- Previous post was at 11:23 AM ----------
Pekkuky said:
I had the same problem, same symptoms.
I too flashed a new ROM and couldn't connect to any AP, I tried various ROMS, MIUI 7 & 8 and CM 13 & 14.1.
Though I think I found a solution (it worked for me ). I simply changed my MAC-adress and I was able to connect to my home WiFi.
I'm running CM 14.1-2016225-NIGHTLY-gemini on MI5.
This is what I did to fix my WiFi:
First prepare an new MAC-address. I personally don't know when a MAC-address is considered valid, so I just took one from an other device. I used the mac address of my previous mobile phone, which could connect to my router.
1. Disable WiFi.
3. Enable debugger settings (Setting>about Phone>Press build number repeatedly).
2. Enable root (Develepor settings>root access set to "Apps and ADB").
3. Open the file manager app.
4. Give the file manager app root access (menu>Settings(cog in lower left corner)>General settings>Access mode set this on "Root Access mode").
5. Now find the file root/etc/firmware/wlan/qca_cld/ and open wlan_mac.bin.
You should see something similar to:
Code:
Intf0MacAddress=XXXXXXXXXXXX
Intf1MacAddress=XXXXXXXXXXXX
END
6. Change the first to your new MAC-address, but first write down the old one, so you can change it back if this method doesn't work for you.
The last X of the next line should be a digit higher than the previous line. E.g:
Code:
Intf0MacAddress=957FDC328BF[B]4[/B]
Intf1MacAddress=957FDC328BF[B]5[/B]
END
(This MAC-address most likely won't work).
7. Save the file. You might need to press the save button a few times.
8. Check if the file has changed.
9. Check if you MAC-address has changed (Settings>WiFI>Configure-WIFI(cog in right upper corner)).
10. Enable WiFi.
I hope this works for everyone that has the same problem.
Click to expand...
Click to collapse
This method work, thanks a lot.
But, for me it's required a valid MAC-address
Pekkuky!
Thank you for your time sharing your knowledge on this topics many days old.
Awesome! You made my day. It work.
I just want to add my experience that might be useful for others.
I tried with a automatically generated MAC and it didn't work.
I followed your advice and repeated with a MAC address of an old e-reader and it worked instantly.
Thanks again!
Pekkuky, thanks a lot. Now I can use CM derived ROMs, great.
Later on after trying solution by Pekkuky, i have problem in turning on hotspot tethering and usb tethering. Anyone can confirm this or this is just me.
Hotspot tethering is working on mine. Before this fix it didn't.
Haven't tried usb tethering though.
Pekkuky said:
I had the same problem, same symptoms.
I too flashed a new ROM and couldn't connect to any AP, I tried various ROMS, MIUI 7 & 8 and CM 13 & 14.1.
Though I think I found a solution (it worked for me ). I simply changed my MAC-adress and I was able to connect to my home WiFi.
I'm running CM 14.1-2016225-NIGHTLY-gemini on MI5.
This is what I did to fix my WiFi:
First prepare an new MAC-address. I personally don't know when a MAC-address is considered valid, so I just took one from an other device. I used the mac address of my previous mobile phone, which could connect to my router.
1. Disable WiFi.
3. Enable debugger settings (Setting>about Phone>Press build number repeatedly).
2. Enable root (Develepor settings>root access set to "Apps and ADB").
3. Open the file manager app.
4. Give the file manager app root access (menu>Settings(cog in lower left corner)>General settings>Access mode set this on "Root Access mode").
5. Now find the file root/etc/firmware/wlan/qca_cld/ and open wlan_mac.bin.
You should see something similar to:
Code:
Intf0MacAddress=XXXXXXXXXXXX
Intf1MacAddress=XXXXXXXXXXXX
END
6. Change the first to your new MAC-address, but first write down the old one, so you can change it back if this method doesn't work for you.
The last X of the next line should be a digit higher than the previous line. E.g:
Code:
Intf0MacAddress=957FDC328BF[B]4[/B]
Intf1MacAddress=957FDC328BF[B]5[/B]
END
(This MAC-address most likely won't work).
7. Save the file. You might need to press the save button a few times.
8. Check if the file has changed.
9. Check if you MAC-address has changed (Settings>WiFI>Configure-WIFI(cog in right upper corner)).
10. Enable WiFi.
I hope this works for everyone that has the same problem.
Click to expand...
Click to collapse
I was really thinking I would have to throw away the phone. Love for you, really, worked flawlessly. Used this website to generate a MAC http://www.miniwebtool.com/mac-address-generator/
Pekkuky said:
I had the same problem, same symptoms.
I too flashed a new ROM and couldn't connect to any AP, I tried various ROMS, MIUI 7 & 8 and CM 13 & 14.1.
Though I think I found a solution (it worked for me ). I simply changed my MAC-adress and I was able to connect to my home WiFi.
I'm running CM 14.1-2016225-NIGHTLY-gemini on MI5.
This is what I did to fix my WiFi:
First prepare an new MAC-address. I personally don't know when a MAC-address is considered valid, so I just took one from an other device. I used the mac address of my previous mobile phone, which could connect to my router.
1. Disable WiFi.
3. Enable debugger settings (Setting>about Phone>Press build number repeatedly).
2. Enable root (Develepor settings>root access set to "Apps and ADB").
3. Open the file manager app.
4. Give the file manager app root access (menu>Settings(cog in lower left corner)>General settings>Access mode set this on "Root Access mode").
5. Now find the file root/etc/firmware/wlan/qca_cld/ and open wlan_mac.bin.
You should see something similar to:
Code:
Intf0MacAddress=XXXXXXXXXXXX
Intf1MacAddress=XXXXXXXXXXXX
END
6. Change the first to your new MAC-address, but first write down the old one, so you can change it back if this method doesn't work for you.
The last X of the next line should be a digit higher than the previous line. E.g:
Code:
Intf0MacAddress=957FDC328BF[B]4[/B]
Intf1MacAddress=957FDC328BF[B]5[/B]
END
(This MAC-address most likely won't work).
7. Save the file. You might need to press the save button a few times.
8. Check if the file has changed.
9. Check if you MAC-address has changed (Settings>WiFI>Configure-WIFI(cog in right upper corner)).
10. Enable WiFi.
I hope this works for everyone that has the same problem.
Click to expand...
Click to collapse
works like a charm
thanks mate, u saved my phone! :highfive:
using this website for generating an mac-adress too
http://www.miniwebtool.com/mac-address-generator/
Thanks Pekkuky for the trick. This problem appeared after flashing lineage os 14.1 using twrp. Then I tried different versions of global stable/developer roms (both fastboot and recovery) but nothing worked. Finally this trick worked Used the miniwebtool site for generating mac-address.
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.