Anyone knows how to change "regulatory domain" on 2.0 rom ?
Need to change channels to see my offices rooter.
I checked now 1.9 and it can see this rooter.
Installed also cyanogenmod and changed under "regulatory domain" to 14 channels and can see my rooter.
Anyone knows how to change this manualy on 2.0 rom ?
Or which file is it, so I can maybe copy from 1.9 rom?
DeMar27 said:
Anyone knows how to change "regulatory domain" on 2.0 rom ?
Need to change channels to see my offices rooter.
I checked now 1.9 and it can see this rooter.
Installed also cyanogenmod and changed under "regulatory domain" to 14 channels and can see my rooter.
Anyone knows how to change this manualy on 2.0 rom ?
Or which file is it, so I can maybe copy from 1.9 rom?
Click to expand...
Click to collapse
Hi Demar, I'm currently on GR4, but it should be the same on TP2.
I just tested with my own setup, I set the wi-fi channel on the router to channel 13, and the phone was unable to connect.
Then I changed the property "ro.wifi.channels" in build.prop to 13. After a reboot it connected fine.
So it seems that's all you need to do, either edit or add the line
"ro.wifi.channels=14"
to your build.prop.
Yeah. I know this. I tried, but without results..
DeMar27 said:
Yeah. I know this. I tried, but without results..
Click to expand...
Click to collapse
Which kernel are you using? I'm on HP-RC4.
Problem solved.
I'm not sure with what ?
I changed following:
ro.product.locale.region=EU
ro.wifi.channels=14
And installed some script that I found on forum
No I can choose regulatory domain
Wifi channels enable for both 11g/11n networks
DeMar27 said:
Problem solved.
... installed some script that I found on forum
Click to expand...
Click to collapse
Hmm... What script do you mean?
Anyway, to enable last (14) channel for .11g, without the script,
you need to set "wifi_country_code=JP" in the "secure" table in the following database:
"/data/data/com.android.providers.settings/databases/settings.db".
(It may be easily done with RootExplorer and SQLite editor installed).
Also, it may help for 5GHz .11n too, by default (for USA) very few channels are available,
Most channels in .11n become active with EU code in the field above.
And, there is no need to reboot the phone after change - just switch WiFi off/on!
alanber said:
"/data/data/com.android.providers.settings/databases/settings.db"
Click to expand...
Click to collapse
In my case there is no .db file
But it's a Samsung Galaxy A5 (2017) of course...
Related
Hi!
I've put an app together (99% based on "Wireless Tether for Root Users") which allows tethering via USB. Clients need to support RNDIS - works fine with Microsoft Windows (tested with XP and 7) and Linux (OpenSuSE 11.1).
Zinx Verituse has ported the essential parts of the hero-kernel and cyanogen has introduced this feature in his latest rom. So, thanks Zinx for the patches and cyanogen for publishing on github.
Patches can be found here:
http://github.com/cyanogen/cm-kernel/commit/9fd56ebdb6aba91e9b17ddea490ec9b39a819112
http://github.com/cyanogen/cm-kernel/commit/1a57339f015c3bfa097cf1d3e82f3485a6652483
I've decided to create this app to give all rom-cooks the ability to use this feature without modifying system-services and/or system-apks.
What a cook needs to do: Patch your kernel and recompile - all other stuff is done by the app.
Download:
http://code.google.com/p/android-wired-tether/
Features:
* Tethering makes use of the mobile-data-connection (HSDPA/EDGE/GPRS) or WiFi-connection
* Uses correct domainname-servers - provided by your carrier or which are configured on the wifi-access-point you connect (even if the network changes => switch from 3g to wifi and vice versa)
* Allows to change the local-network (network/subnetmask)
Supported ROMs:
* CyanogenMod 4.2.3.1+
* Android Dev Phone 1
=> my kernel-update needs to be applied: http://code.google.com/p/android-wired-tether/downloads/list?q=Kernel
* ?
Have fun!
Harry
THX a lot for this app
sudo dhclient usb0 and there you go
Good work.
Alot of the hero roms were finally able to get wireless tethering for root working on, well, hero roms. i installed, but cant get it working. What patch should i use, im using Sense Hero1.3.3
Hi Harry,
I'm visiting from the CDMA Hero forum, in the hopes that you might have some pointers on how to get this to work on the rooted CDMA Hero?
When I looked at this project over at code.google.com, it seems like this requires 1.6, where the CDMA hero is running 1.5. Will this fact doom us to ever run wired tether at this point?
From what I can tell on my Hero, everything seems to run fine until after I allow root access for the app. It then gives me a FC when accessing the system settings (as it's the one referenced in the FC.)
Can I apply your kernel safely to my ROM? Thanks in advance for your help!!
doesnt seem to work with macs
kmartburrito said:
Hi Harry,
I'm visiting from the CDMA Hero forum, in the hopes that you might have some pointers on how to get this to work on the rooted CDMA Hero?
When I looked at this project over at code.google.com, it seems like this requires 1.6, where the CDMA hero is running 1.5. Will this fact doom us to ever run wired tether at this point?
From what I can tell on my Hero, everything seems to run fine until after I allow root access for the app. It then gives me a FC when accessing the system settings (as it's the one referenced in the FC.)
Can I apply your kernel safely to my ROM? Thanks in advance for your help!!
Click to expand...
Click to collapse
Did you try http://forum.xda-developers.com/showthread.php?t=443025?
I've been using the wired tether for the past week and have experienced some issues. Mainly, if the tether app isn't in the foreground, the process seems to randomly get restarted. This manifests as brief hiccups in internet access for the connected computer. Didn't experience this problem using WT4R (in bluetooth mode).
HW: Dream
App: wired-tether-1.0.apk
Kernel: adp 1.6 usbtether-r3
OS: Vista SP2
If I remember to, i'll post a log later tonight.
Could you please explain (or put in the first post) why use this while the current tether in Network Settings (CM4.2.x) works just fine?
Proxin said:
Could you please explain (or put in the first post) why use this while the current tether in Network Settings (CM4.2.x) works just fine?
Click to expand...
Click to collapse
If usb-tethering with cyanogenmod is working fine for you there is no reason why you should use this app. I've implemented just a few enhancements (using the correct domainname-servers, changing lan-config) - I don't know how cyanogen is doing this stuff (I don't use it).
The main-idea of this app was to bring usb-tethering to other roms (where system-settings can't be modified or roms which a pretty close to stock roms and heavily modified parts are not welcome). All you need for this is a modified kernel which can be easily done.
jashsu said:
I've been using the wired tether for the past week and have experienced some issues. Mainly, if the tether app isn't in the foreground, the process seems to randomly get restarted. This manifests as brief hiccups in internet access for the connected computer. Didn't experience this problem using WT4R (in bluetooth mode).
HW: Dream
App: wired-tether-1.0.apk
Kernel: adp 1.6 usbtether-r3
OS: Vista SP2
If I remember to, i'll post a log later tonight.
Click to expand...
Click to collapse
yes, please post your log.
harry_m said:
If usb-tethering with cyanogenmod is working fine for you there is no reason why you should use this app. I've implemented just a few enhancements (using the correct domainname-servers, changing lan-config) - I don't know how cyanogen is doing this stuff (I don't use it).
The main-idea of this app was to bring usb-tethering to other roms (where system-settings can't be modified or roms which a pretty close to stock roms and heavily modified parts are not welcome). All you need for this is a modified kernel which can be easily done.
Click to expand...
Click to collapse
Ah, it hadn't occurred to me that other roms might not yet have tethering.
Thanks for your contribution then!
Very good! Thank you!
Anyone have the usb drivers for Windows XP?
Thanks in advance!
Has anyone used this successfully with Dwang 1.13? When Cyanogen came out with USB tethering it practically rendered mounting my sdcard and adb unusable. But this would be nice to use.
Sorry...Here's the link for it all.
http://bit.ly/wDDT0
awesome app
hey dude thanks for this app. i have cyanogenmod 4.2.5 and i know usb tethering is enabled on there but i didnt know how to get it to work. this app made it easy and painless i just had to download htc sync for hero and it worked like a charm. love it..
Just wanted to jump in and say thanks. I'm using this in my newest build and it works like a charm. I couldn't remember the authors name so i came here to get it so I can give credit, so while I'm here I wanted to say good job, and thank you
iflyabeech said:
Has anyone used this successfully with Dwang 1.13? When Cyanogen came out with USB tethering it practically rendered mounting my sdcard and adb unusable. But this would be nice to use.
Click to expand...
Click to collapse
i am also using dwangs v1.13 and am interested in the usb tether. i am a newb to all of this so if anyone has used these two together please let me know.
yaz813 said:
i am also using dwangs v1.13 and am interested in the usb tether. i am a newb to all of this so if anyone has used these two together please let me know.
Click to expand...
Click to collapse
This does work on dwangs 1.13 ... however it broke the cell network I was unable to get cell signal or network so it did me no good. I am working on way to fix this but I have not done dev for any phone in a long time, so it may take me a while to find out what is doing this.
I found out the hard way that apparently the WPA2 implementation in Android is faulty. This means it can not connect to WPA2 secured APs which enforce strict specs:
https://forum.openwrt.org/viewtopic.php?id=25870
Would it be possible to fix that in CM ?
Cheers,
Karl
Android is using wpa_supplicant, it doesn't implement the protocols on its own.
So you are saying the bug is actually in wpa_supplicant ?
Should i try to make them aware of the problem ?
First time I hear that, although I have at home WPA2 personal and my Legend connects with it normally.
I have a WPA2 personal network both at home and at my dorm, and my HeroC has been able to connect to them fine no matter what ROM I've used (stock, Sense 2.1 custom ROMS, and CM6/7)
According to the openwrt link i posted above it seems to be a problem with the drivers on openwrt enforcing strict RFC compliance and the wpa_supplicant not sticking to it. So it might just be a problem for a specific setup.
However, the question now is if that should be fixed in android or if openwrt should relax its rules.
I just try to find out which community would be the right one to address...
Hey AliBa !
People at openwrt think its a problem of the TI wireless drivers, and that it could be fixed in CM:
This is not a problem with OpenWRT, hostapd, or wpa_supplicant (the latter two are the same project, and mostly written by one person). This is a bug with Android wifi drivers that do not properly follow spec.
The TI Wilink driver I referred to is particularly at fault, and disabling WMM on the router is a band-aid to the problem - not a fix or a real solution. wpa_supplicant is not even involved in this process since the Wilink driver generates the RSN on its own.
The people who need to address this are TI, not openwrt or CM or someone else (or CM can put in a patch to fix the TI Wilink driver, which is probably a good idea anyway).
Click to expand...
Click to collapse
https://forum.openwrt.org/viewtopic.php?id=25870
There are two RSN settings in tiwlan.ini:
Code:
RSNPreAuthentication
RSNExternalMode
...try setting latter to external.
Hey BlaY0 !
This .ini file is in the build tree, not on the phone, right ? Or can i set that on my phone ?
If its a part of the build files, do you think I should file a bug at CM ?
It's on the phone... /system/etc/wifi/tiwlan.ini. It's configuration file for driver itself.
Might be a noob-problem, but i am unable to write to the file.
I tried terminal emulator, su, vi /etc/wifi/tiwlan.ini, but its read-only.
Any other way i can try this ?
Use recovery to do that or you can use system overlay.
Sent from my HTC Legend
Tried switching the RSN..-config to external as mentioned, but it's not working here.
Hmm, anything else we can do ?
AliBa, are you sure you could not fix this ?
People at openwrt think it could be patched in CM:
https://forum.openwrt.org/viewtopic.php?id=25870
Cheers,
Karl
Yes, I'm sure I can't fix that.
If it's not caused by wpa_supplicant then there's nothing we can do. Sources for neither firmware nor kernel module are open sourced so there's no way to patch them.
Hey !
ali ba said:
Yes, I'm sure I can't fix that.
If it's not caused by wpa_supplicant then there's nothing we can do. Sources for neither firmware nor kernel module are open sourced so there's no way to patch them.
Click to expand...
Click to collapse
Too bad. Didnt know that some (?) kernel modules are closed source in android. What a shame !
Anyway, thanks for trying to help !
karl_k said:
Hey !
Too bad. Didnt know that some (?) kernel modules are closed source in android. What a shame !
Anyway, thanks for trying to help !
Click to expand...
Click to collapse
It's a royal PITA, and we all dislike HTC, Motorola, Samsung etc. for doing it. That said, the CM team do an unbelievable job of dealing with it as well as they do
karl_k said:
Too bad. Didnt know that some (?) kernel modules are closed source in android. What a shame !
Click to expand...
Click to collapse
Every Google device was as close to open source as possible with all kernel sources being released. It's companies like HTC that corrupt that whenever they can. For example they put code into the framework that would normally go into the kernel just to not having to release it.
Moreover, the sources for wl12xx were open sourced by TI using a BSD-like license. The even sadder problem is that HTC modified them and then deliberately removed those modifications (headers) from the kernel sources they released.
So its a dead end, and really nothing can be done about it?
Can't believe that!
Here's a flashable fix if you're getting a different MAC address on ICS when compared to GB.
It is caused by a missing symlink causing it to use a wrong firmware file.
update-ICS-MAC-fix.zip (488 KB)
Only tested on ROMs based on stock firmware.
just a question.... y are there duplicates of wifi firmware in etc/firmware and /ticonnectivity?
I would like to know which is the correct path that wifi will look for the firmware?
Correct path is \system\etc\firmware\ti-connectivity\
All xperia phones got this issue or partial to only arc
which config file defines firmware path I want to check for neo_v
what difference does it make if you have the wrong MAC Version being displayed?
@yacloo all of them, for example to fix it I used Arc file on NeoV
@SS4Serebii if your network checks mac address you will not be able to connect to your network and maybe something more
is this needed on a CM9 ROM ? and will this work on said ROM ?
SS4Serebii said:
what difference does it make if you have the wrong MAC Version being displayed?
Click to expand...
Click to collapse
As Zdune stated. Also, let's say there are 2 arcs with the incorrect MAC address issue (they have the same address), only one of them will be able to connect to a WiFi hotspot.
Punkid said:
is this needed on a CM9 ROM ? and will this work on said ROM ?
Click to expand...
Click to collapse
I cannot guarantee but CM9 should already have correct address.
Thanks Zdune and doomed!
I checked my mac address same as like on GB rom didn't changed
weird all stock roms aren't same
on my stock ics rom wifi firmware files are on \system\etc\firmware\ti-connectivity\
there is no wifi firmware \system\etc\firmware\
on dmesg firmware loading is ok
should I install this fix
If it didn't change then there's no need to use this fix.
I'm currently using ICS CM9, and i didn't see any of said item on the path given..
Hi,
I have an OnePlus 3T and apparently OpePlus simply took the default WiFi config file provided by Qualcomm. This means that while for 5GHz channel bonding is enabled, 2.4GHz connections only use 20MHz wide channels, whereas channel bonding would allow to use 40MHz (where supported by the router).
This problem can be remedied by editing the config file WCNSS_qcom_cfg.ini located in system/etc/wifi. However, I found it unpleasant to modify my system partition as Magisk would give me systemless root and Xposed. So I did a very simply Magisk Module to overcome this.
To my understanding, this configuration is the same for OP3 and OP3T - but can't say for sure.
EDIT: Download removed. Now in official Repo.
Thanks!
BTW: It's free. If you like it, hit the THANKS button. If you want to donate, please donate to @topjohnwu for making Magisk!
I have op3t with magisk 10.2 and pph's root, how can I test if this module is working as intended?
I tested it on a 1+3 and it seems to work. But I'm not sure how to test this properly. But the link speed is higher. I will do some more testing.
I did some further testing and it works. The link speed doubled. See the Screenshots.
What did you changed exactly?
Nvm found it
(O+3T here)
Thanks man, works wonderful!
gkillerx said:
What did you changed exactly?
Nvm found it
Click to expand...
Click to collapse
He changed the configuration value in the aforementioned file to this value.
Code:
gChannelBondingMode24GHz=1
dreinulldrei said:
Hi,
I have an OnePlus 3T and apparently OpePlus simply took the default WiFi config file provided by Qualcomm. This means that while for 5GHz channel bonding is enabled, 2.4GHz connections only use 20MHz wide channels, whereas channel bonding would allow to use 40MHz (where supported by the router).
Click to expand...
Click to collapse
Is this still the case with OOS 4.0.1? Can the module being used on OOS4?
Edit: gChannelBondingMode for 2.4 GHz is still 0 on OOS 4.0.1
Yes. It still works on Nougat. It's a preset file by Qualcomm and I doubt OP will change it. Just a guess though.
It does work even on the Nougat version of OOS. @dreinulldrei, you really should apply for the repo because this is a solid mod.
Shouldn't OnePlus be fixing this? :silly:
Jadelor said:
It does work even on the Nougat version of OOS. @dreinulldrei, you really should apply for the repo because this is a solid mod.
Click to expand...
Click to collapse
I applied for a repository, but so far no response from topjohnwu. Guess he's working on next release of Magisk.
I can confirm this works.
My WiFi speed almost doubled!
It's on the official repo now.
Hi Guys.
I have a small query regarding the module. Will it drain more battery...? Please share your feedback
Hello,
How to unistal this module to use the 5ghz wifi after the installation ?
Ordijules said:
Hello,
How to unistal this module to use the 5ghz wifi after the installation ?
Click to expand...
Click to collapse
Magisk modules are uninstalled using Magisk Manager. 5GHz wifi is untouched by the module and you can choose to use 5GHz even with it enabled.
Okay thanks you
Then can you say me how to reset the wifi because I can't use Internet in wifi 5ghz and I have unistall the module
Sorry for my strange english
dreinulldrei said:
It's on the official repo now.
Click to expand...
Click to collapse
Has the issue been fixed in OOS 4.0.3 or do we still need this module?
Uh.. why do I have the same problem on my Nexus 5X? I can only go up to 72Mbps in 2.4GHz mode. But I don't have that file in /system/etc/wifi
Hi,
I just got my Google WiFi 3-kit and it seems that the channel they work on (149) wasn't supported in my country (NL) so I made a simple Magisk module to change the region to [EU]
This 'fix' is simpy a change to "wifi-service.jar" which can be located in /system/framework/
Source: https://github.com/thomasvt1/extendwifi
DOWNLOAD
Updates v7
Update OOS to 4.5.10
Add support for Magisk v14.0
Special thanks to:
- https://forum.xda-developers.com/pixel/themes/mod-wifi-country-code-fix-root-required-t3558044
Would there be any benefit to flashing this if I'm in the US, or do they all have the NL flag?
The wifi region is selected based on the SIM in your phone. Most people won't need this, care, or notice.
Second, this is probably illegal since it changes your phone to use frequencies that are not allowed in the users home country. Is anyone going to get caught or in trouble for this? Unlikely. But it also won't be useful unless you've purchased hardware that broadcasts on frequencies not allowed in your country. IE, Google WiFi hasn't been released in Europe yet and doesn't officially follow EU frequency range. Which is why it's useful for @Thomasvt but not for anyone else.
@PokemonTotalWar: Long answer? No.
@PokemonTotalWar: For US users, probably not, except if you use channel 12/13 from the 2.4GHz spectrum. > https://en.wikipedia.org/wiki/List_of_WLAN_channels
@Raharazod Actually Google WiFi is released in the EU. (France, Germany and the UK) http://www.androidpolice.com/2017/06/26/google-wifi-may-coming-france-monday/ as for my country. All Apple products, and my laptop happily use the 5GHz network without any modification except my OnePlus 5.
Thomasvt said:
@Raharazod Actually Google WiFi is released in the EU. (France, Germany and the UK) http://www.androidpolice.com/2017/06/26/google-wifi-may-coming-france-monday/ as for my country. All Apple products, and my laptop happily use the 5GHz network without any modification except my OnePlus 5.
Click to expand...
Click to collapse
OH! I thought it was still pending release over here. Wasn't really keeping a close eye.
Well it shouldn't.
There ARE 5Ghz bands that are allowed in the EU, just not all of them. I was assuming that your module enabled ones that weren't otherwise allowed.
I've got my phone bootloop
Thomasvt said:
Hi,
I just got my Google WiFi 3-kit and it seems that the channel they work on (149) wasn't supported in my country (NL) so I made a simple Magisk module to change the region to [EU]
This 'fix' is simpy a change to "wifi-service.jar" which can be located in /system/framework/
Source: https://github.com/thomasvt1/extendwifi
DOWNLOAD
Updates v7
Update OOS to 4.5.10
Add support for Magisk v14.0
Special thanks to:
- https://forum.xda-developers.com/pixel/themes/mod-wifi-country-code-fix-root-required-t3558044
Click to expand...
Click to collapse
After installing module I've got my phone bootloop. May you define place for the original wifi-service.jar file during module installation.
Thanks, Kinger
Kinger1970 said:
After installing module I've got my phone bootloop. May you define place for the original wifi-service.jar file during module installation.
Thanks, Kinger
Click to expand...
Click to collapse
Just use 'magisk mount' and remove it from /magisk.
What O2OS are you running?
Thank you for quick response
Thomasvt said:
Just use 'magisk mount' and remove it from /magisk.
What O2OS are you running?
Click to expand...
Click to collapse
Thank you, restored system easily. Problem I'm not running O2OS system on phone I've crashed, installed on different phone by mistake.
Thank you, cheers!
I got another Problem on oreo closed beta 2.
After update from 4.5.14 my 5ghz wont connect with settings in router auto channel..
This means channels 36 above until 52 wont work.
If i sett a special channel like 52 above my 5ghz wifi connects to my op5..
Did OnePlus messed something up?
Located in Germany op5 A5000
Hi Dimontiman,
Have you tried with the official OxygenOS Open Beta 1? Since leaked closed beta 1 and 2 were not made for public and lots of bugs.
Did it give any errors when adding the module in Magisk?
If still doesn't work on official open beta 1, then perhaps an update to this module would be required perhaps.
keepasa said:
Hi Dimontiman,
Have you tried with the official OxygenOS Open Beta 1 (8.0)?
Click to expand...
Click to collapse
Yes both open beta 1 and xlosed beta 2
Same Wifi Problems
I do have a Oxygen (leaked build 1) version on my github: https://github.com/thomasvt1/extendwifi/tree/4.5.2 (just download as zip).
I haven't been able to get smali working yet with the open beta 1. I'm not sure if the closed beta one works on the open beta.
Edit: My version from git still does work with the open beta 1. Just tested.
Edit2: New updated version for Open Beta 1: https://github.com/thomasvt1/extendwifi/tree/O2_Open1 [just downoad zip and use in magisk]
Thomasvt said:
I do have a Oxygen (leaked build 1) version on my github: https://github.com/thomasvt1/extendwifi/tree/4.5.2 (just download as zip).
I haven't been able to get smali working yet with the open beta 1. I'm not sure if the closed beta one works on the open beta.
Edit: My version from git still does work with the open beta 1. Just tested.
Edit2: New updated version for Open Beta 1: https://github.com/thomasvt1/extendwifi/tree/O2_Open1 [just downoad zip and use in magisk]
Click to expand...
Click to collapse
Hey
Appreciate your work, what does your module change exactly?
Additional to OP
Dimontiman said:
Hey
Appreciate your work, what does your module change exactly?
Additional to OP
Click to expand...
Click to collapse
It changes just one file; https://github.com/thomasvt1/extendwifi/tree/O2_Open1/system/framework
And then just the setCountryCode method as per this guide;
https://forum.xda-developers.com/pixel/themes/mod-wifi-country-code-fix-root-required-t3558044
open beta is supported?
enskje said:
open beta is supported?
Click to expand...
Click to collapse
https://github.com/thomasvt1/extendwifi/archive/O2_Open1.zip
This is for Open Beta 1
Small update for Openbeta 1 - the region didn't apply every boot so I fixed that;
https://github.com/thomasvt1/extendwifi/archive/O2_Open1.zip
Thomasvt said:
Small update for Openbeta 1 - the region didn't apply every boot so I fixed that;
https://github.com/thomasvt1/extendwifi/archive/O2_Open1.zip
Click to expand...
Click to collapse
Hey can you update this version to magisk repo as i cant use the zip on magisk
Dimontiman said:
Hey can you update this version to magisk repo as i cant use the zip on magisk
Click to expand...
Click to collapse
Sorry the magisk repo version will only be the stable version of OxygenOS.
Maybe try a file explorer to select the zip, I know ES File Explorer works when using the 'file way' and not the 'normal android way'.
I hope this helps!
Thomasvt said:
Sorry the magisk repo version will only be the stable version of OxygenOS.
Maybe try a file explorer to select the zip, I know ES File Explorer works when using the 'file way' and not the 'normal android way'.
I hope this helps!
Click to expand...
Click to collapse
If i flash the zip from twrp, can stock be afterwards restored? I mean to uninstall