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
Related
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...
This module doubles the number of steps in volume adjustment for both media and in-call volume.
WARNING: Apparently doesn't work on all devices, for example OnePlus 3 according to this.
what about a collection thread for build prop tweaks to use in Magisk?
Thanks for the module. It's got a funny bump going louder until the middle of the scale, then getting suddenly significantly quieter again and going louder until the end, for media playback.
Bettik said:
Thanks for the module. It's got a funny bump going louder until the middle of the scale, then getting suddenly significantly quieter again and going louder until the end, for media playback.
Click to expand...
Click to collapse
Could be hardware/driver-dependant. I've used a (non-systemized) prop modification before on a tablet and it was pretty smooth.
time comes, good modules too :good:
Just a reminder for those who encounter problems. ro.config.vc_call_vol_steps=14
ro.config.media_vol_steps=30 won't work for all devices, such as OnePlus 3, at least on its official OxygenOS.
Once you change your media volume steps from default 15 to the 30, using the script above which is included in the module, on your OnePlus 3. The steps are increased, while it's just a loop. The volume drop back to the lowest again at the 16th step and totally silent at some steps bigger than 20.
BTW, the xposed module VolumeSteps+ won't work on OnePlus 3 either.
accidentally quoted OP instead of editing it.
changes couldn't be reseted after removing the system.prop or the module. Any thing to do?
chjun90 said:
changes couldn't be reseted after removing the system.prop or the module. Any thing to do?
Click to expand...
Click to collapse
Remove module, reboot. When asking for help, provide logs.
stangri said:
Remove module, reboot. When asking for help, provide logs.
Click to expand...
Click to collapse
i do that many times. i have removed the module days ago, but the chages still on my phone. i found the bug in all the modules with system.prop not only yours. thinking it's bugs of magisk v11.1.
chjun90 said:
i do that many times. i have removed the module days ago, but the chages still on my phone. i found the bug in all the modules with system.prop not only yours. thinking it's bugs of magisk v11.1.
Click to expand...
Click to collapse
Would be great if you had created an issue against Magisk on github then. Probably uninstalling magisk (from recovery) and re-installing it would start you with a clean slate.
Alternatively, there're unofficial builds of the next-gen magisk available, maybe they would fix the issue.
stangri said:
Would be great if you had created an issue against Magisk on github then. Probably uninstalling magisk (from recovery) and re-installing it would start you with a clean slate.
Alternatively, there're unofficial builds of the next-gen magisk available, maybe they would fix the issue.
Click to expand...
Click to collapse
i had
Is it compatible with the latest 11.6 magisk? Anyone tested?
Angelos N. said:
Is it compatible with the latest 11.6 magisk? Anyone tested?
Click to expand...
Click to collapse
11.0.0 version is and I have.
Angelos N. said:
Is it compatible with the latest 11.6 magisk? Anyone tested?
Click to expand...
Click to collapse
Causes systemui FC.
This is because of system.prop. I had this same issue when changing.
To 11.6.
ahrion said:
Causes systemui FC.
Click to expand...
Click to collapse
As evident from the screenshots below it works fine.
Care to post link to the github issue where 11.6 has broken system.prop support?
stangri said:
As evident from the screenshots below it works fine.
Care to post link to the github issue where 11.6 has broken system.prop support?
Click to expand...
Click to collapse
I had the same issue with my mods, removing system.prop fixed this issues. 11.6 broke resetprop for certain people. I don't see any issues on the GitHub for magisk, but I know this is an issue because me on my own mods and others have reported this same issue. I've tested it and that's what I have found.
It doesn't happen to all phones but I think it's a magisk issue with resetprop, something that was not an issue in 11.5.
ahrion said:
I had the same issue with my mods, removing system.prop fixed this issues. 11.6 broke resetprop for certain people. I don't see any issues on the GitHub for magisk, but I know this is an issue because me on my own mods and others have reported this same issue. I've tested it and that's what I have found.
It doesn't happen to all phones but I think it's a magisk issue with resetprop, something that was not an issue in 11.5.
Click to expand...
Click to collapse
I think you're making way to large assumptions here. From my experience, there's no issue with resetprop. This module and many others I've tried and use on v11.6, that utilises system.prop and resetprop work just fine.
Yes, when I tested your module my device wouldn't boot unless I removed the system.prop from the audmodlib. But I don't think that had anything to do with the system.prop itself, but rather what you'd put in it...
Didgeridoohan said:
I think you're making way to large assumptions here. From my experience, there's no issue with resetprop. This module and many others I've tried and use on v11.6, that utilises system.prop and resetprop work just fine.
Yes, when I tested your module my device wouldn't boot unless I removed the system.prop from the audmodlib. But I don't think that had anything to do with the system.prop itself, but rather what you'd put in it...
Click to expand...
Click to collapse
I'm not making assumptions. I'm literally telling you what issues I've experienced with my 9 modules and I'm not the only one It worked before 11.5/11.6 until I removed system.prop, which was the issue. The issue itself was not present before on previous versions. This was happening for me when upgrading to 11.6.
This is a reproduceable issue that was introduced once resetprop changes were introduced in 11.5/11.6 which did not occur before then, with the same exact zips updated to v3 module template. If you check the magisk release notes it CLEARLY states he made changes to resetprop. Which obviously confirms what I'm saying now.
Audmodlib lib has literally nothing in it that would bootloop your device. All it does is copy your system files into its own magisk folder. Nothing else. It makes ZERO edits to those files if you look at the code. The additional mods that edit audmodlib are what make edits to your existing device code.
I was just seeing if we could figure out a solution to this issue and to pinpoint why this is happening.
ahrion said:
I'm not making assumptions. I'm literally telling you what issues I've experienced with my 9 modules and I'm not the only one It worked before 11.5/11.6 until I removed system.prop, which was the issue. The issue itself was not present before on previous versions. This was happening for me when upgrading to 11.6.
This is a reproduceable issue that was introduced once resetprop changes were introduced in 11.5/11.6 which did not occur before then, with the same exact zips updated to v3 module template. If you check the magisk release notes it CLEARLY states he made changes to resetprop. Which obviously confirms what I'm saying now.
Audmodlib lib has literally nothing in it that would bootloop your device. All it does is copy your system files into its own magisk folder. Nothing else. It makes ZERO edits to those files if you look at the code. The additional mods that edit audmodlib are what make edits to your existing device code.
I was just seeing if we could figure out a solution to this issue and to pinpoint why this is happening.
Click to expand...
Click to collapse
I get it that you're trying to promote use of your own audmodlib template over the standard magisk template. Have you personally tried using *this* module *without* any other borked/broken modules? If so, please list the HW/SW (ROM, kernel, magisk and magisk manager versions, list of installed modules) combination which results in a bootloop.
PS. This is not a support thread for other broken modules.
Thats my first productive creation for XDA, so dont be to hard to me
I don't like to have features, which I never use, so I always disable or remove everythink i dont need.
On my custom roms I always diable the multi user mode by adding the following line to the build.prop:
Code:
fw.max_users=1
I was annoyed to edit this file after each ROM update.
So I created this module. It just adds the above mentioned line to the build.prop.
It is really simple, but now I don't need to edit the build.prop.
Maybe for someone this can be useful.
It works with:
- Android 6.x (Tested on OnePlus X and OnePlus 3 with CM13)
- Android 7.x (Tested on LOS 14.1 and OxygenOS 4.5.x)
v1.3: Update to Magisk Template 1400 (14.0).
Looks good but I would change the modid to something other than template. This is in the config.sh file and defines the folder it uses under /magisk. Anyways I used your zip as a template for my own build.prop edits that I will post shortly. I'll throw a little credit your way too.
Sorry, I was on vacation and than really busy...
@shinji257: Thank you for the hint. I changed it and uploaded the mod as v 1.1.
And actually I found already a similar magisk module created by user @FHC1998:
https://forum.xda-developers.com/apps/magisk/magisk-multiuser-enable-disable-t3552643
dima-82 said:
Sorry, I was on vacation and than really busy...
@shinji257: Thank you for the hint. I changed it and uploaded the mod as v 1.1.
And actually I found already a similar magisk module created by user @FHC1998:
https://forum.xda-developers.com/apps/magisk/magisk-multiuser-enable-disable-t3552643
Click to expand...
Click to collapse
That module probably still works (haven't updated it since posted) but the Magisk template is not updated.
My module does pretty much the same thing as yours, there is only one more line on the prop that I add.
fw.show_multiuserui=0
This disable all the UI and configurations sections for multiuser. Its not obligatory, but for me it makes sense to disable the interface aswell if you are disabling the function.
You can add that if the multiuser options keep showing even after disabling multiuser.
FHC1998 said:
That module probably still works (haven't updated it since posted) but the Magisk template is not updated.
My module does pretty much the same thing as yours, there is only one more line on the prop that I add.
fw.show_multiuserui=0
This disable all the UI and configurations sections for multiuser. Its not obligatory, but for me it makes sense to disable the interface aswell if you are disabling the function.
You can add that if the multiuser options keep showing even after disabling multiuser.
Click to expand...
Click to collapse
When I looked for the build.prop settings to disable multi user functionality I found the mentioned line as well.
But I cannot see any difference if I add it. At least it has not effect on my phone (OnePlus 3, CM13).
dima-82 said:
When I looked for the build.prop settings to disable multi user functionality I found the mentioned line as well.
But I cannot see any difference if I add it. At least it has not effect on my phone (OnePlus 3, CM13).
Click to expand...
Click to collapse
It depends on the device, I originally tested on a few, and some needed this line.
For instance, I tested your module on my device (ZenFone 2 laser) and it worked perfectly without the line, but on my friend's ZenFone 2 it kept showing the UI even though not allowing creating more users.
@dima-82 Module works great for me. I'm running a OP3T on offical LineageOS. All the multiuser stuff is gone from the settings and notification shade.
Sent from my ONEPLUS A3000 using Tapatalk
mp3deviant721 said:
@dima-82 Module works great for me. I'm running a OP3T on offical LineageOS. All the multiuser stuff is gone from the settings and notification shade.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Thanks for the feedback.
The official LineageOS for OP3T is Android 7.x? Nightly builds?
dima-82 said:
Thanks for the feedback.
The official LineageOS for OP3T is Android 7.x? Nightly builds?
Click to expand...
Click to collapse
The build I'm running is 7.1.1. Haven't tried 7.1.2 yet. Yes on the "nightly" build.
Sent from my ONEPLUS A3000 using Tapatalk
@dima-82,
Hello, I used your module to enable multi user mode, all I did is edited the file inside the .zip where the string to disable the multi user mode is located, and replaced it with the two strings to enable it.
Now I was wondering since this works, could I make a thread with the mod?
I would obviously credit You, and link to Your profile and this thread.
Here is the module on my device :silly:
dariomrk said:
@dima-82,
Hello, I used your module to enable multi user mode, all I did is edited the file inside the .zip where the string to disable the multi user mode is located, and replaced it with the two strings to enable it.
Now I was wondering since this works, could I make a thread with the mod?
I would obviously credit You, and link to Your profile and this thread.
Click to expand...
Click to collapse
Of course you can do.
But as mentioned in post #3 there was already a similar module. I think it does exactly what you need.
dima-82 said:
Of course you can do.
But as mentioned in post #3 there was already a similar module. I think it does exactly what you need.
Click to expand...
Click to collapse
Oh, I didn't see that, I will check if it does the exactly same thing (probably yes)...
---------- Post added at 03:06 PM ---------- Previous post was at 03:05 PM ----------
Just checked it out, and yes it does the exactly same thing
Please I need multiuser enable magisk module for Android 6
dima-82 said:
And actually I found already a similar magisk module created by user @FHC1998:
https://forum.xda-developers.com/apps/magisk/magisk-multiuser-enable-disable-t3552643
Click to expand...
Click to collapse
Here
Got bootloop after the install of this module.
Device: Zuk Z2
ROM: AEX 4.4
Unofficial Magisk 13.2 (170716)
I am running it on official Magisk 13.2 without any issues.
Did you also install other modules?
dima-82 said:
I am running it on official Magisk 13.2 without any issues.
Did you also install other modules?
Click to expand...
Click to collapse
Yes have other 5 modules
You installed / activated only this very one module and got a bootloop?
Before I created this module I edited the build.prop manually. And if you make a mistake there, you will get a bootloop as well.
May be your OS does not support this property.
I tested on my devices only, and it worked always.
Eventually you can try an other module from @FHC1998, which should do the same:
https://forum.xda-developers.com/showpost.php?p=71936097&postcount=3
jhobc said:
Got bootloop after the install of this module.
Device: Zuk Z2
ROM: AEX 4.4
Unofficial Magisk 13.2 (170716)
Click to expand...
Click to collapse
You could eventually try this mod:
https://forum.xda-developers.com/apps/magisk/module-single-user-mod-t3639486#post73160966 by @seebz
THIS PROJECT IS NO LONGER SUPPORTED.
Code:
# <Module name goes here>
## Copyright (C) 2017-2018, VR25 @ xda-developers
### License: GPL v3+
---
#### DISCLAIMER
This software is provided as is, in the hope that it will be useful, but without any warranty. Always read/reread this reference prior to installing/upgrading. While no cats have been harmed, I assume no responsibility under anything which might go wrong due to the use/misuse of it.
A copy of the GNU General Public License, version 3 or newer ships with every build. Please, read it prior to using, modifying and/or sharing any part of this work.
To prevent fraud, DO NOT mirror any link associated with this project.
---
#### DESCRIPTION
Hide USB Debugging notification, enable tethering, HDMI (& HDMI mirroring), and wireless display mirroring (Miracast). More features may come.
---
#### PRE-REQUISITES
- Magisk v15+
---
#### SETUP STEPS
1. Install/upgrade from Magisk Manager or custom recovery.
2. Reboot.
3. Go to Settings > Display > Cast > 3 dots; tick the "Enable wireless display" checkbox.
---
#### LINKS
- [Facebook Page](https://facebook.com/VR25-at-xda-developers-258150974794782/)
- [Git Repository](https://github.com/Magisk-Modules-Repo/<repo name goes here>/)
- [XDA Thread](https://forum.xda-developers.com/apps/magisk/module-miracast-tethering-enabler-adb-t3611335/)
---
#### LATEST CHANGES
**2018.10.4 (201810040)**
- Magisk 15+ support
- Set prop values aggressively.
You should note it's for marshmallow mainly. Doesn't work on Nougat for many devices. Untested on android O.
LazerL0rd said:
You should note it's for marshmallow mainly. Doesn't work on Nougat for many devices. Untested on android O.
Click to expand...
Click to collapse
I've tested only on Moto Z Play stock Nougat and LineageOS based ROMs. You may be right. Perhaps some manufacturers hardcode their ROMs to bypass this kind of modification. I don't have any other device to test this on. I'll post a poll to see how that goes. Thanks.
VR25 said:
I've tested only on Moto Z Play stock Nougat and LineageOS based ROMs. You may be right. Perhaps some manufacturers hardcode their ROMs to bypass this kind of modification. I don't have any other device to test this on. I'll post a poll to see how that goes. Thanks.
Click to expand...
Click to collapse
Well, ik on Nexus it doesn't work in any stock based Nougat ROM.
Will it work in Kitkat or Lollipop?
Raynelfss said:
Will it work in Kitkat or Lollipop?
Click to expand...
Click to collapse
Yes, but it may not work on some devices/ROMs. You should try and report back.
LazerL0rd said:
Well, ik on Nexus it doesn't work in any stock based Nougat ROM.
Click to expand...
Click to collapse
Yes. Miracast on LineageOS only work for now. (It's just fixed this problem, no magisk module, no editing build prop)
VR25 said:
After installing and rebooting, go to Settings > Display > Cast > Click the 3 dots > Enable Wireless Display > Done.
Now you can mirror your phone's screen to any Miracast supported device, such as TVs and Windows 10 PCs.
Note: this may not work on some devices/ROMs.
Click to expand...
Click to collapse
Is there a uninstaller incase it doesn't work on my phone? Running resurrection remix 7.1.2
n0013z said:
Is there a uninstaller incase it doesn't work on my phone? Running resurrection remix 7.1.2
Click to expand...
Click to collapse
Usually, this doesn't cause any issue in case it doesn't work. You can easily remove it from the Magisk Manager app. Alternatively, you can also mount magisk.img from recovery and delete the folder "magiskmiracast" inside /magisk.
Use this recovery flashable zip
https://forum.xda-developers.com/attachment.php?attachmentid=4081169&d=1489956274
to mount magisk.img to /magisk.
Miracast is working for me but only for some minutes I play videos, show some pictures and the screen freeze only in my Smartv.
I play videos and more with Allcast and it doesn't happen
Sent from my Moto G (5) Plus using XDA Labs
No luck for me
Oneplus 2 a 2003 rr 5.8.3
Not working on OP3T on OOS
Tried it and it kills magisk and xposed without mercy. Samsung galaxy on5 stock touchwiz 6.0.1
Shen Ron said:
Tried it and it kills magisk and xposed without mercy. Samsung galaxy on5 stock touchwiz 6.0.1
Click to expand...
Click to collapse
Something is wrong with TouchWiz.
So, do I need to be rooted? Or can it be flashed from stock recovery on my zte blade v7 lite (android 6.0) without damage being done? Also I do believe the device needs specific hardware, correct me if I'm wrong!?...
Has anyone tested this on OnePlus 3T?
gb_14 said:
Has anyone tested this on OnePlus 3T?
Click to expand...
Click to collapse
Heyyo, lol literally four posts above yours.
ThE_MarD said:
Heyyo, lol literally four posts above yours.
Click to expand...
Click to collapse
Oh yeah, sorry, I haven't noticed.
HTC One m9, bad boys one m9 nougat 4.1 rom.
I dont have a display option in the settings (probably because of sense)
Only have display and gestures but no cast option inside.
I installed on my S7 Edge Nougat ... But I did not find in any menu the options to activate. Has anyone had this problem? I also tried to test mirroring with an LG TV and could not.
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