This Magisk Module is for the A2017U only. I've tested this on Magisk v13.5, 13.6, and 14.0 without issue, including no SafetyNet problems. Magisk v15 requires the files in post #8 (these files are for B32/B35 users only!!!)
It does the following:
Remove carrier label
Remove NFC icon
Remove roaming icon
Remove disable SIM icon, for dual SIM users
Change "4G" for HSPA+ connections to read "3G"
I've also redesigned the network type icon slightly to make it a bit better (hopefully?).
There are two options...the first is kind of a normal-looking version and the second has Verizon-themed LTE and EvDO icons. (see screenshots below for what these look like respectively)
Use at your own risk! Flash by adding the zip(s) to your Magisk modules section. All these do is make super small changes to the SystemUI_ZTE file so SafetyNet is still a go.
Option 1 (normal theme - B25 only): https://drive.google.com/open?id=0B-9yGc1czLlqZ1ZiZTlmUGRYX0U
Option 2 (Verizon-themed icons - B25 only): https://drive.google.com/open?id=0B-9yGc1czLlqWEVIRllPUURrV3c
For B32/B35 users on a Magisk version prior to v15, see post #3 below.
B32/B35 Modules Files
For B32/B35 users on a Magisk version v15 and greater, see post #8 below.
B32/B35 Modules Files
Enjoy!
Works great thanks!
B32 Modules
Hi...here are links to the B32 modules (only work for Magisk versions prior to v15. See post #8 for Magisk v15 and higher!!!)
Option 1: Normal icons
Option 2: Verizon-themed icons
If the links above give you any trouble, try opening them in an incognito tab and then downloading manually...Google Drive is finicky with ZIP files as it wants to "view" them I believe.
I tried the default icon pack, works, but the 3G image for HSPA+ was too small for my taste so I tried the Verizon version and... it looks exactly the same?
I don't suppose you could make an option that says exactly what it is such as HSPA+?
Cyrus D. said:
I tried the default icon pack, works, but the 3G image for HSPA+ was too small for my taste so I tried the Verizon version and... it looks exactly the same?
I don't suppose you could make an option that says exactly what it is such as HSPA+?
Click to expand...
Click to collapse
Hi! Let me know what you think of this one...it's the Verizon-themed icons but with 3G/HSPA showing for GSM 3G...
Version 2.0 (VZW)
flyer_andy said:
Hi! Let me know what you think of this one...it's the Verizon-themed icons but with 3G/HSPA showing for GSM 3G...
Version 2.0 (VZW)
Click to expand...
Click to collapse
You forgot the +, LOL.
It looks well done. Thanks. If I had a suggestion, it would be just to write HSPA/HSPA+/whatever it is, and forget about trying to squeeze it in under 3G.
Cyrus D. said:
You forgot the +, LOL.
It looks well done. Thanks. If I had a suggestion, it would be just to write HSPA/HSPA+/whatever it is, and forget about trying to squeeze it in under 3G.
Click to expand...
Click to collapse
Unfortunately ZTE calls UMTS, HSPA, and all the variants of HSPA the same thing ('4G' in the stock icons)...so I can only do one icon for these network types. I don't know how to hack the deeper stuff to have it differentiate, unfortunately...so we're stuck with only one icon for all of it and HSPA is the most accurate option, given the technologies currently in use IMO...
If I get better at the programming side maybe one of these days I'll try and make this mod better... but for now unfortunately I'm not sure how to make the icon change for the different 3G technologies...I could just do "H" but I've always not liked that to be honest!
Magisk v15 files (B32/B35 ONLY!!!)
So, looks like Magisk 15 has a different template for the modules. As a result, I've created new files for any v15 or higher users. Modules will fail to install if you use the older files with Magisk v15. These were originally developed for B32 but it appears they work fine on B35 as well as ZTE seems not to have made any changes to the SystemUI. But let me know of any issues with B35!!!
Here are the new files...Neither of these have the carrier label showing in the status bar as I assume most people don't want that...let me know if anyone wants that showing and I'll create two additional files with that option.
Verizon theme:
https://drive.google.com/open?id=1ZFafAa2MzGWESVt0U6KaMCeEFqsto-9M
Standard theme:
https://drive.google.com/open?id=1kHmaG00g-MKi-BM3bHZRBt341A-LoTqr
If the links above give you any trouble, try opening them in an incognito tab and then downloading manually...Google Drive is finicky with ZIP files as it wants to "view" them I believe.
Please let me know of any problems! Thanks!
I don't have an U (G here), but now that this "System UI tuner" app is on the Play store, I think you can achieve similar results. I have been looking for a way to get rid of unnecessary icons to just have the battety percentage, wifi signal and cell signal, and it works
Just a heads-up
Choose an username... said:
I don't have an U (G here), but now that this "System UI tuner" app is on the Play store, I think you can achieve similar results. I have been looking for a way to get rid of unnecessary icons to just have the battety percentage, wifi signal and cell signal, and it works
Just a heads-up
Click to expand...
Click to collapse
Thanks...I just checked it out. It looks like the only icon that the app can remove is NFC...I don't see any option to remove the carrier label, disabled SIM icon, or roaming icon.
Let me know if I've missed anything though...
Also, one of the main points of this module is to retheme the signal icons a bit...I've always thought the stock ZTE ones are kind of lame, to be honest...so I wanted to make something a bit nicer.
I'll keep the maintenance up of this for now, though I'm not sure if anyone uses it! But thanks for mentioning that app as I'm sure there may be some visitors to this thread that would prefer that option to a Magisk module.
Can you make a Verizon pack with the clock on the left?
hiperglyde said:
Can you make a Verizon pack with the clock on the left?
Click to expand...
Click to collapse
Like this? (see screenshot).
Here's the link to the module that'll do what's shown below. ALSO!!! This is B32 only...so if you've already updated to the new version released today (B35) then don't use this...I haven't yet gotten B35 so I can't provide updated modules for that yet...
@hiperglyde EDIT: Looks like this does work ok in B35 as well! Let me know if you run into any issues though and I'll redo it with the B35 raw file.
https://drive.google.com/open?id=1ioWcoxUQTT8t-JeXfJdugeuud2af8boI
Best,
Andy
they just changed the security patch, it should still work
Choose an username... said:
they just changed the security patch, it should still work
Click to expand...
Click to collapse
Sweet! Thanks for clarifying!!! I'll relabel the B32 as working for B35! Of course, in case ZTE snuck any little changes into the SystemUI_ZTE file and anybody runs into any issues let me know and I'll redo it!
flyer_andy said:
Like this? (see screenshot).
Here's the link to the module that'll do what's shown below. ALSO!!! This is B32 only...so if you've already updated to the new version released today (B35) then don't use this...I haven't yet gotten B35 so I can't provide updated modules for that yet...
@hiperglyde EDIT: Looks like this does work ok in B35 as well! Let me know if you run into any issues though and I'll redo it with the B35 raw file.
https://drive.google.com/open?id=1ioWcoxUQTT8t-JeXfJdugeuud2af8boI
Best,
Andy
Click to expand...
Click to collapse
Amazing, thank you!!!
flyer_andy said:
Hi...here are links to the B32 modules:
Option 1: Normal icons
Option 2: Verizon-themed icons
If the links above give you any trouble, try opening them in an incognito tab and then downloading manually...Google Drive is finicky with ZIP files as it wants to "view" them I believe.
Click to expand...
Click to collapse
Getting Magisk not activated error Magisk v15.3. B35
- Copying zip to temp directory
- Installing MAGISK-SimpleStatusBar-A2017U-B32.zip
! Magisk is not activated!... abort
Failed!
! Installation failed
JKSurf said:
Getting Magisk not activated error Magisk v15.3. B35
- Copying zip to temp directory
- Installing MAGISK-SimpleStatusBar-A2017U-B32.zip
! Magisk is not activated!... abort
Failed!
! Installation failed
Click to expand...
Click to collapse
Ughhhh! I'm really sorry! I had the post linked wrong in the original post as it relates to Magisk v15 and it was displaying the wrong files. The modules you were attempting to install were for lesser versions. Make sure the file names have "M15-" at the beginning when you download them and you'll know you've got the right ones...here is the correct link to post #8 for the Magisk v15 files...previously it was linking to post #3 which had the old files:
https://forum.xda-developers.com/showpost.php?p=75216804&postcount=8
Let me know if this works! I'm really sorry about that!
Worked. Love this mod. Thanks!
JKSurf said:
Worked. Love this mod. Thanks!
Click to expand...
Click to collapse
Great!!! Thanks for confirming!!!
Any chance to get this working with aosp?
Related
This thread is now deprecated, look for the all new 5 layouts Floating Multi Windows mod here:
http://forum.xda-developers.com/gal...-floating-multi-windows-t2820366/post54240351
What about minimizable, maximizable, resizable floating multi windows on your Mega?
Interested?
DISCLAIMER
I'm not responsible for anything that may happen, your Mega, your responsability . The mod works fine on mine but one never knows, so make sure you have a Nandroid backup in case.
WHERE ARE THE UPDATES?
If you had already installed the previous version (s) just scroll down until the update chapters by the end of this post...
MEGA 5.8 OWNERS
This mod has been tested on Mega 6.3 but it should work as well on Mega 5.8.
Follow the instructions, but DO NOT flash the Floating_Multi_Windows_I9200.zip since it's for the Mega 6.3 only.
If you want the full version on your Mega 5.8, upload your androidpolicy.jar and I'll mod it.
REQUIREMENTS
A rooted Mega I9200 or I9205 on JB 4.2.2, with a custom recovery (either CWM, or TWRP, or whatever) installed.
It works on both odexed and deodexed Roms, but odexed Roms will allow less features. It has been tested on XXUAMEE and I can't tell for sure whether it works on other Roms or not, but my guess is that it does. Please try and report (but don't forget to make a backup beforehands):silly:
MEGA 6.3 ON DEODEXED MJ2
DO NOT flash the Floating_Multi_Windows_I9200.zip attached here cuz it's not compatible with MJ2. Go to post #13, I've attached a MJ2 version there (it has been tested and it works, see post #14).
INSTALLATION
Using your favorite root browser navigate to /system/etc/permissions folder and find com.sec.feature.multiwindow.phone.xml.
Rename it com.sec.feature.multiwindow.phone.xml.bak (do not delete it, in case you want to revert back to static stock multi windows).
That's it for people on an odexed Rom, reboot. Now when you open an app you see an icon at the top right or at the top bottom, press it, the app switches to floating window view (I'll explain everything in a minute, let me finish this paragraph first).
For people on a deodexed Rom, flash in recovery the attached zip (if you are running MJ2 don't flash the zip attached here but the one in post #13), wipe cache and dalvik cache, reboot.
HOW DOES IT WORK?
As said above, now when you open an app you see an icon that enables you to switch to floating mode. In floating mode you see on the top bar a close, a maximize and a pin button, plus a minimize icon (for deodexed Roms only, the difference between odexed and deodexed Roms is that deodexed Roms get on top of the other features a minimize icon and a double tap feature while in floating mode).
The close and maximize icons speak by themselves. The pin button, press it, it becomes green and enables you to keep the floating window (s) allways on screen. With the pin button activated you can resize windows from the bottom, the left and the right.
Use the space between the pin and the other icons to drag and move the window to wherever it pleases you.
While in floating mode you can press the maximize icon, or double tap the center of the bar (deodexed Roms only), to get the window back to full screen mode.The minimize icon (deodexed Roms only) shrinks the window to a bar like on a computer.
Depending on your phone settings the Flash Bar may or may not work. If it still works then you can use it to launch apps directly in floating mode, and you don't need to have the pin activated to be able to rezise windows. What makes it work or not? Good question, when I first set up this mod on my phone it worked, but at one point it stopped and never came back. I have to investigate and well, you are free to investigate too, any help is highly appreciated...
Anyway, with or without Flash Bar you can have as many Floating Windows as you want, cool...:good:
YOU WANT TO GO BACK TO THE STOCK STATIC MULTI WINDOWS VIEWS?
No worries, just delete the .bak in the com.sec.feature.multiwindow.phone.xml and reboot. If you flashed the zip don't bother, it won't harm your phone since the editing I made doesn't work when com.sec.feature.multiwindow.phone.xml is active.
NOT ALL YOUR APPS DISPLAY IN FLOATING MODE?
The latest update (7 JULY 2014) takes care of that, just keep on reading
BUGS
1-When one changes screen orientation the floating windows are back to full screen size.
Solution:
change your phone's DPI. I changed mine to 195 and the bug is gone. Don't go below 193 as the systemui doesn't like it and would force close everytime the orientation changes.
2-Some apps that are natively multi windows enabled don't display nicely (they show a huge floating window). To tame them, one has to decompile the app, open res/values/dimens.xml and edit the app default and minimum sizes to have them to look as follows:
<dimen name="app_defaultsize_w">300.0dip</dimen>
<dimen name="app_defaultsize_h">200.0dip</dimen>
<dimen name="app_minimumsize_w">300.0dip</dimen>
<dimen name="app_minimumsize_h">200.0dip</dimen>
300 and 200 are the values I use but of course you can use other values that suit you better. The default size means the size the app has when it's opened in floating mode, and the minimum size means the smallest size you can resize/shrink it.
3-When an apk is minimized as a bar, if one opens a new apk and makes it float the first mimized apk has disappeared. It doesn't happen if two or more apks are open in floating mode and then minimized/maximized (I mean, in that case one can swith between minimize/maximize without loosing the other minimized apks), it happens only if a new apk is opened while one or more are minimized. I don't know if I explained it clearly but play a bit with the mod and you'll see what I mean...
Edit: 11 dec update (see below) more or less fixed this bug.
4-You tell me:cyclops:
UPDATE 11 DEC (Tested on deodexed I9200, but it should work for all 6.3 and 5.8 Mega models)
Today I decided to install the flash bar and some xmls permissions from the note 3, and see what would come out.
To my surprise it brought three interesting improvements.
1 - Multi instance, which means that one can open at the same time two or more windows of the same app (I could open up to 4 windows of the same app, not that I would really use it but just to say:cyclops.
Quite a handy feature if you want to compare two books, or two maps, or two pics or two whatever, but note that not all apps support multi instance, and note that for some apps one can't open two windows one after the other (one has to open one window of let's say app A, then app B, then one can open a second window of app A with the first app A still open).
2 - The disappearance of minimized bars is gone (still some random disappearing) when the windows are launched from the flash bar (but it still occurs when they are launched from somewhere else).
3 - The windows are resizable to a very small size, even smaller than the minimized bars (like 50x60, and don't need anymore to have the pin enabled to be resized.
No need to drag the apps from the flash bar, just touch them and they open in floating mode (set your prefered floating size with multi windows manager).
The 5 xmls files are attached below. This zip is not flashable, I did it intentionally in order one to know what files one pushes into one's phone, in case one day one wants to remove them. So you have to unzip first, and then manually copy the 5 xmls to your /system/etc/permissions folder, set perms to rw, r, r (644), reboot.
Careful!
One of these 5 files is called com.sec.feature.multiwindow.xml, and you may think that you already have it in your /system/etc/permissions folder. Well, you certainely have a file that has the same name, but it's not the same file (look at the weight). Rename your existing file com.sec.feature.multiwindow.xml.bak and then copy the new com.sec.feature.multiwindow.xml onto the folder.
A word about static stock multi windows
I tested these files in static stock multi windows (by renaming the com.sec.feature.multiwindow.phone.xml.bak to com.sec.feature.multiwindow.phone.xml, see above) and the multi instance works, plus there is a funky recent multi windows opened apps feature on the top of the flashbar, and a bookmark function on the bottom. Well, I found these features a bit wonky, but I didn't test too much so see by yourself if you feel like it.
Your flash bar doesn't show up, and you don't have the option anymore in your settings?
It's normal, it's because com.sec.feature.multiwindow.phone.xml has been renamed com.sec.feature.multiwindow.phone.xml.bak.
Rename it com.sec.feature.multiwindow.phone.xml, reboot. Go to display in your settings, enable the flashbar. Check that it appears. Rename again com.sec.feature.multiwindow.phone.xml to com.sec.feature.multiwindow.phone.xml.bak, reboot, your flash bar is still there (Note that you don't have the option to enable/disable it in the settings. You can force stop it from the applications section in the settings, but in that case it won't restart until you reboot).
UPDATE
I found a way to have that multi windows option to show in the settings all the time.
Since it's a heavy file I didn't upload it (my internet connection is dreadful) but if someone wants it then I'll upload it.
I'm a bit busy at the moment and I didn't test all the new features extensively, but if you do and find some tricks or fine settings/improvments please report here. Thanks in advance.:silly:
UPDATE 21 DEC (tested on Mega 6.3 XXUAMEE but it should work on all 6.3 Roms, and probably 5.8's)
It's a two layouts mode, which means that you will have the ability to switch between dual and cascade mode at the press of a button.
Go to your system/app folder and rename FlashBarService.apk to FlashBarservice.apk.bak (in case you need to get back to it if the mod is not compatible with your rom).
Flash the 2LayoutsFlashbarServiceMega.zip, wipe cache and dalvik cache, reboot.
Now open your FlashBar (the bar from where you launch the multi windows) and look at the top, you'll see two icons. That's it, one is for cascade mode, and the other for dual mode. When you press one it turns green, which means that the mode is activated.
If some windows disappeared and you want them back, or if you had too many windows opened in dual mode and want to put everything in order, press the cascade icon and they'll open in cascade mode (but it only works if the apps were still active, if they had been closed it obviously doesn't work).
If the FlashBarService fc, it means that it's not compatible with your rom. In this case delete the FlashBarService.apk from your system/app, remove the .bak you put at the stock one, reboot. If you want it for your rom, upload here your FlashBarservice.apk and your framework-res.apk and I'll mod it to make it two layouts enabled.
UPDATE 7 JULY 2014 (tested on Mega 6.3 DDUCNB1, it should work on other 6.3 Roms but it won't work on Mega 5.8. If you want it for your rom upload your FlashBarService.apk, services.jar, framework-res.apk and I'll mod it)
Here is a mod to make all your apps floating multi windows compatible.
I know that there are some apps here and there that do the same job but the advantage of this mod is that:
1-it works without any third part app which means that you'll save some ram and some battery,
2-with third apps when you install a new app you have to reboot to have that new app to show in the multi windows tray and to have the cascade/minimize icon to appear in full mode, whereas with this mod you don't need to reboot, the app shows straight away in the tray and so does the cascade/minimze icon.
Download AllAppsFloatingMultiWindowsMega6.3.zip, flash it from recovery, clean dalvik cache, reboot.
Bugs:
1-In dual mode, before to minimize a window press the pins from both apps to avoid the black screen issue (you'll understand what I mean when you get it).
If you get the black screen no worries, just maximize your windows, or press recents, or home, or settings, well press whatever takes you out from the black. And next time don't forget to pin both the windows before to minimize them:cyclops:...
2-You tell me...
WHAT'S NEXT?
I will mod some files to try to enable 5 layouts or Note 3's quad view, and I will try to add 2-3 things I have in mind. But no promises
YOU WANT TO HELP MAKE THIS MOD BETTER?
You are welcome!!!!!!!!!!!!
CREDITS
@rovo89 for the amazing Xposed Installer
@xperiacle cuz he was the one that found out that Samsung Roms are Floating Windows compatible
@THEDEVIOUS1 for porting the mod to the Galaxy Tab 7 Plus, and for all his help when I made my first Floating Windows mod for the Galaxy Grand
reserved
i will be following your project and testing everything ) thank you for this
will give feedback
i9205
yeah man you ROCK. Im on i9205 and it works perfect. thanks.
no problem in rotation screen for me for moment.
I tried to flash it but now i'm stuck on the samsung logo...
what should I do?
I'm using stock MJ2, deodexed, and TWRP...
-rename com.sec.feature.multiwindow.phone.xml to com.sec.feature.multiwindow.phone.xml.bak
-restart to TWRP
-wipe cache/dalvic
-flash the zip
-reboot
than stuck at samsung logo....
i04055 said:
I tried to flash it but now i'm stuck on the samsung logo...
what should I do?
I'm using stock MJ2, deodexed, and TWRP...
-rename com.sec.feature.multiwindow.phone.xml to com.sec.feature.multiwindow.phone.xml.bak
-restart to TWRP
-wipe cache/dalvic
-flash the zip
-reboot
than stuck at samsung logo....
Click to expand...
Click to collapse
I'm sorry to hear that you have issues...
The wiping must be done after the flash.
What you can do is go into recovery, wipe cache and dalvik, then reboot.
Anyway, that's strange since the zip is harmless. Which Mega do you have? I9200?
That could be an incompatibility with MJ2...
Or, did the zip download properly? When you are flashing it do you see some text on your screen?
Sometimes, since the zip contains a jar, one has to reboot twice. I don't know why but it's an issue that I have once in a while.
In the worst scenario, I mean if it still bootloops, then you'll have to restore your backup.
Good luck!
If you still don't manage to install it then it means that it's an incompatibility with MJ2, in that case upload your androidpolicy.jar and your framework-res.apk and I'll mod it.
unclefab said:
I'm sorry to hear that you have issues...
The wiping must be done after the flash.
What you can do is go into recovery, wipe cache and dalvik, then reboot.
Anyway, that's strange since the zip is harmless. Which Mega do you have? I9200?
That could be an incompatibility with MJ2...
Or, did the zip download properly? When you are flashing it do you see some text on your screen?
Sometimes, since the zip contains a jar, one has to reboot twice. I don't know why but it's an issue that I have once in a while.
In the worst scenario, I mean if it still bootloops, then you'll have to restore your backup.
Good luck!
If you still don't manage to install it then it means that it's an incompatibility with MJ2, in that case upload your androidpolicy.jar and your framework-res.apk and I'll mod it.
Click to expand...
Click to collapse
I tried to flash again than wipe cache/davic, but still no luck.
I use I9200, i don't see any error message when flashing the zip, try to restart several times but still stuck at samsung logo...
So I reflash the full rom than it back to normal.
Maybe it just not compatible with MJ2
i04055 said:
I tried to flash again than wipe cache/davic, but still no luck.
I use I9200, i don't see any error message when flashing the zip, try to restart several times but still stuck at samsung logo...
So I reflash the full rom than it back to normal.
Maybe it just not compatible with MJ2
Click to expand...
Click to collapse
Yep, I think it's the XXUAMEE androidpolicy.jar that doesn't fit MJ2.
Upload your androidpolicy.jar and your framework-res.apk, and I'll mod for you and for other MJ2 users.
OP updated.
The update can be used with all rooted Mega variants, deodexed or odexed, 6.3 and 5.8.
It brings amongst other multi instance but well, just have a look at the OP
Is it now support mj2 firmware?
Sent from my GT-I9200 using xda app-developers app
i04055 said:
Is it now support mj2 firmware?
Sent from my GT-I9200 using xda app-developers app
Click to expand...
Click to collapse
Nope, cuz nobody uploaded MJ2's framework-res.apk and androidpolicy.jar...
As I already said, if one wants this mod for a particular firmware (including Mega 5.8 inches) one has to upload those 2 files...
But that's in order to get the full mod. Otherwise it's possible to get 75 % of it by just renaming some files in the system/etc/permissions folder and adding some other files in the same folder, for any firmware on both Mega 6.3 and 5.8, see OP...
unclefab said:
OP updated.
The update can be used with all rooted Mega variants, deodexed or odexed, 6.3 and 5.8.
It brings amongst other multi instance but well, just have a look at the OP
Click to expand...
Click to collapse
tested and working perfectlyy .. you are the one
unclefab said:
Nope, cuz nobody uploaded MJ2's framework-res.apk and androidpolicy.jar...
As I already said, if one wants this mod for a particular firmware (including Mega 5.8 inches) one has to upload those 2 files...
But that's in order to get the full mod. Otherwise it's possible to get 75 % of it by just renaming some files in the system/etc/permissions folder and adding some other files in the same folder, for any firmware on both Mega 6.3 and 5.8, see OP...
By the way, I modded the flash bar (the bar from where one can launch multi windows apps), if someone is interested it's there:
http://forum.xda-developers.com/showthread.php?t=2567109
Click to expand...
Click to collapse
here are the files... just got a chance to use my comp after so long...
android policy : https://dl.dropboxusercontent.com/u/31220121/MJ2 FW/android.policy.jar
framework-res : https://dl.dropboxusercontent.com/u/31220121/MJ2 FW/framework-res.apk
MJ2
Ok mate, here it is
Please do report whether it works or not, for other people on MJ2 to know. Then if it works I'll update OP:good:.
Stay tuned, some more updates are on the way. I managed to have stock dual static multi windows and cascade/floating multi windows to work at the same time, and I'm currently working on enabling quad view and/or five layouts (no promises on those ones though, but I'll try my best:silly...
Edit;
confirmed working on MJ2 (see next post).
unclefab said:
Ok mate, here it is
Please do report whether it works or not, for other people on MJ2 to know. Then if it works I'll update OP:good:.
Stay tuned, some more updates are on the way. I managed to have stock dual static multi windows and cascade/floating multi windows to work at the same time, and I'm currently working on enabling quad view and/or five layouts (no promises on those ones though, but I'll try my best:silly...
Click to expand...
Click to collapse
confirm working....
Working perfect on my GTi9205 ...
Thanks mate ...
Post #13 works in my gt-i9205 good.tnx
Sent from my GT-I9205 using Tapatalk
thank you very much. Excellent yet so simple and elegant modification!
Can this be used on note 10.1 2014?
inertiaholic said:
thank you very much. Excellent yet so simple and elegant modification!
Can this be used on note 10.1 2014?
Click to expand...
Click to collapse
Probably, since it will have note 3 style multi windows, but I can't tell for sure (it hasn't been released yet).
I briefly tried a note 3 and I didn't see any floating option, but I know there are some mods like quad views (easy to implement on note 3, but not on mega )
Check note 3's forum, I think I saw something about floating windows...
thanks for the quick reply suitably named unclefab!
With note 3, yes mw etc easily created the floating window presumably on the back of the pen window feature, but not as elegant as yours or as universal as your where every window can be minimised etc. Indeed the multiwindow method is somewhat convoluted.
on my huawei ascend mate, i used the floating notifications plus xhalo windows but also somewhat iffy.
unclefab said:
Probably, since it will have note 3 style multi windows, but I can't tell for sure (it hasn't been released yet).
I briefly tried a note 3 and I didn't see any floating option, but I know there are some mods like quad views (easy to implement on note 3, but not on mega )
Check note 3's forum, I think I saw something about floating windows...
Click to expand...
Click to collapse
Working on att galaxy mega i527 .thanks
Sent from my SAMSUNG-SGH-I527 using XDA Premium 4 mobile app
*This module also works for any another device with Qualcomm Snapdragon chipset based, so feel free to test it on another device that have Magisk and recommend for your friends that want a better GPS experience and functionality.
The original gps.conf file present in any version of MIUI is very wrong, it has a lot of bad information and settings for the correct operation of the GPS and A-GPS. But on most Custom ROMs it was solved, however, I believe the changes I've made for a better optimization has the best results.
A little reflection tested and proven by myself: If you have a nice FW version with wrong gps.conf you won't have good results with the GPS, but if you have any FW version with gps.conf file correctly edited, maybe you might get better results.
Then we can finally conclude that, the Xiaomi Mi5 don't have any HW problem with GPS. What happens is that the firmware works in conjunction with the file.
There's not much difference with the default file included in LOS or other ROMs but let me explain about some of my relevant changes:
1 - Now basically the A-GPS data files are XTRA 3.0 files (It provides GPS, GLO and BDS assistance data) served over HTTPS with SSL and without # preceding the address lines while the default on MIUI ROMs was XTRA 2.0 (provides only GPS and GLO) served over HTTP without SSL, this allows an attacker to mount a MITM attack on the network level and modify the GPS assistance data while in transit.
2 - I switched the XTRA_VERSION_CHECK from 0 to 3 because it's obvious that xtra3grc.bin are XTRA 3.0 files.
3 - I included the address servers from pool.ntp.org as the main NTP server because it's global, the system will try finding the closest available servers for you
4 - I set SUPL_HOST google.com as default, before was qxwz.com on MIUI and this is an A-GPS server in China. Google server is more "Global" and can do the job very well.
5 - I updated the SUPL version from 2.0 to 3.0
6 - I changed the SUPL_MODE from 3 (so bad, this option doesn't even exist) to 0x2 (MSA), under normal circumstances, the MSA method is applicable to situation which the satellite signal is poor, to achieve a single positioning.
7 - Changed the value of GPS CAPABILITIES from 0x37 to 0x35 for correctly MSA mode functionality.
8 - Changed the LTE Positioning Profile Settings from 0 (RRLP) to 3 (LPP_User_Plane and LPP_Control_Plane)
9 - Changed the A-GLONASS Positioning Protocol from 0 to 0x4 (LLP Uplane)
The reason for the 8 and 9 changes is because SUPL 3.0 doesn't support RRC and RRLP anymore.
[Step By Step]
It's Magisk install-able, don't install it by TWRP but with Magisk instead!
1 - Go on Magisk > Modules > Click on "+" yellow button > Search and find this "optimizedgpsconf.zip" file (Now this one and only works fine for both Nougat and Oreo and also is correctly replacing the gps.conf file), long press on it and select open and after installed then reboot your device.
2 - Make sure your location settings is setup on mode "High accuracy"
3 - Skirt outdoors, can be in the yard of your house or anywhere else with a line of sight to the sky, download some Compass app on Google Play Store (I recommend the Compass Steel 3D) and then calibrate the compass.
4 - Stay in that outdoor place and download GPS Locker on Google Play Store and open the app and wait for the first time fix/lock. This is necessary and essential because the app will recognize some GPS satellites signals for the very first time.
*Note 1 - Location mode "Battery saving" is gone due to Google's location accuracy is now a binary setting.
*Note 2 - Consider using the GPS Locker app because it is much better than the GPS Test and GPS Data. You just need to open it once and wait for fix, then your gps signal is locked and when you close it the app keep awake running in the background. (press Cancel in "Unlock GPS on exit" message). GPS was made to work on outdoor places. For indoor/enclosed places such as inside of your house don't forget that, it will take a few minutes to fix. It drains more battery, but is required if you're an advanced user that use gps all the time.
Whenever I'm on the street I keep the GPS Locker and Cellular data open because I use Cerberus antitheft, so if I get mugged or if I lose my phone I can track him down and retrieve it.
I hope I've helped. Please, give me some feedback if it worked for you.
ianhughes74 said:
Guys let me tell you, I'm currently using the FW v7.10.12 with ViperOS v3.1.1 ROM and the gps.conf file edited by myself.
The original gps.conf file present in any version of MIUI is very wrong, it has a lot of bad information and settings for the correct operation of the GPS. But on most of Custom ROMs it was solved, however, I believe the changes I've made for a better optimization in my country have the best results.
A little reflection tested and proven by myself: If you have a nice FW version with wrong gps.conf you won't have good results with the GPS, but if you have any FW version with gps.conf file correctly edited, maybe you might get better results.
Then we can finally conclude that, the Xiaomi Mi5 don't have any HW problem with GPS. What happens is that the firmware works in conjunction with the file.
Extract the file "gps.zip" and copy the gps.conf file and paste and replace on the root>system>etc folder and then reboot your device.
Make sure your location settings is setup on mode high accuracy.
Download some Compass app on Google Play Store (I recommend the Compass Steel 3D) and then calibrate the compass.
Skirt outdoors, can be in the yard of your house or anywhere else with a line of sight to the sky, download GPS Locker on Google Play Store and open the app.
Please, give me some feedback if it worked for you.
Click to expand...
Click to collapse
Thanks a lot, Ian. Still haven't gotten around to try it, but will do it tomorrow morning and report back.
Just did a diff with the gps.conf included in LOS 14.1; there are some minor differences (I suspect much less than when compared with MIUI) but will try it anyway to see if it makes a a difference. Just for the record, I don't have terrible GPS performance (it takes a while to lock, and accuracy could be better) but any improvement would be welcome.
Just tried your gps.conf; copied it into /system/etc using TWRP, rebooted, recalibrated compass and cleared and updated AGPS (I used the "GPS Test" app). I'm using 7.9.22 dev firmware and LineageOS 14.1, latest build (10.24).
The performance for me was about the same than with the default LineageOS gps.conf, both in accuracy and 3D Lock time; I suspect the change might be more spectacular for MIUI users, so I'd give it a try if I had severe GPS problems. As I told before, my GPS performance is not great, but not terrible either.
Anyway, thanks a lot, @ianhughes74 for your work!
e_jim said:
Thanks a lot, Ian. Still haven't gotten around to try it, but will do it tomorrow morning and report back.
Just did a diff with the gps.conf included in LOS 14.1; there are some minor differences (I suspect much less than when compared with MIUI) but will try it anyway to see if it makes a a difference. Just for the record, I don't have terrible GPS performance (it takes a while to lock, and accuracy could be better) but any improvement would be welcome.
Just tried your gps.conf; copied it into /system/etc using TWRP, rebooted, recalibrated compass and cleared and updated AGPS (I used the "GPS Test" app). I'm using 7.9.22 dev firmware and LineageOS 14.1, latest build (10.24).
The performance for me was about the same than with the default LineageOS gps.conf, both in accuracy and 3D Lock time; I suspect the change might be more spectacular for MIUI users, so I'd give it a try if I had severe GPS problems. As I told before, my GPS performance is not great, but not terrible either.
Anyway, thanks a lot, @ianhughes74 for your work!
Click to expand...
Click to collapse
Yes, you're right. I made minor changes with the default file included in LOS.
Now basically the data files are served over HTTPS with SSL while the default was served over HTTP without SSL, this allows an attacker to mount a MITM attack on the network level and modify the GPS assistance data while in transit.
I switched the XTRA_VERSION_CHECK from 0 to 3 because it's obvious that xtra3grc.bin are XTRA 3.0 files.
And I includes the address pool.ntp.org as the main NTP server because it's global, the system will try finding the closest available servers for you. However, this is a dynamic IP server, so, a fixed time reference becomes more reliable, fast and secure. If your country have a NTP server with a static IP, please consider adding the address to the file.
But for now you can try to replace the lines to:
NTP_SERVER=cl.pool.ntp.org
NTP_SERVER_1=south-america.pool.ntp.org
NTP_SERVER_2=gpsntplpsc.duckdns.org
NTP_SERVER_3=time.izatcloud.net
But consider using the GPS Locker app because it is much better than the GPS Test and GPS Data. You just need to open it once and wait for fix, then your gps signal is locked and the app keep awake running in the background.
It drains more battery, but is required if you're an advanced user that use gps all the time. Whenever I'm on the street I keep the GPS Locker and Cellular data open because I use Cerberus antitheft, so if I get mugged or if I lose my phone I can track him down and retrieve it.
I hope I've helped.
Quick update: I was on 7.9.22 firmware before. Just to be sure, I flashed a newer FW (7.10.19) together with your gps.conf, and GPS lock times improved drastically! Accuracy also improved a good bit. Thanks a lot again!
I'll have to remember to copy your file over the default one each time I flash a LOS weekly, but it's worth it
can you please modify for indonesia? thx u
kemalafiantoro said:
can you please modify for indonesia? thx u
Click to expand...
Click to collapse
Please, edit by yourself. Open the file that I attached using Solid Explorer File Manager or ES File Explorer as Text Editor and replace the following lines below and then save the file.
NTP_SERVER=asia.pool.ntp.org
NTP_SERVER_1=id.pool.ntp.org
NTP_SERVER_2=0.id.pool.ntp.org
NTP_SERVER_3=1.id.pool.ntp.org
NTP_SERVER_4=2.id.pool.ntp.org
NTP_SERVER_5=3.id.pool.ntp.org
compatible for malaysia ?
Please provide the file for India.
Great work @ianhughes74 !
It really helped my gps signal on AEX rom, not that it was bad but now it's more consistent. Thanks a lot
Now only if we had someone who knows a thing or two about flashable zips to make this process more automated, but never the less, good job on the detailed guide and thanks for help
qiie95 said:
compatible for malaysia ?
Click to expand...
Click to collapse
Please, edit by yourself. Open the file that I attached using Solid Explorer File Manager or ES File Explorer as Text Editor and replace the following lines below and then save the file.
NTP_SERVER=asia.pool.ntp.org
NTP_SERVER_1=my.pool.ntp.org
NTP_SERVER_2=0.asia.pool.ntp.org
NTP_SERVER_3=1.asia.pool.ntp.org
NTP_SERVER_4=2.asia.pool.ntp.org
NTP_SERVER_5=3.asia.pool.ntp.org
Phillen13 said:
Please provide the file for India.
Click to expand...
Click to collapse
Please, edit by yourself. Open the file that I attached using Solid Explorer File Manager or ES File Explorer as Text Editor and replace the following lines below and then save the file.
NTP_SERVER=asia.pool.ntp.org
NTP_SERVER_1=in.pool.ntp.org
NTP_SERVER_2=1.in.pool.ntp.org
NTP_SERVER_3=1.asia.pool.ntp.org
NTP_SERVER_4=3.asia.pool.ntp.org
and for Italy please?
0ther said:
and for Italy please?
Click to expand...
Click to collapse
Please, edit by yourself. Open the file that I attached using Solid Explorer File Manager or ES File Explorer as Text Editor and replace the following lines below and then save the file.
NTP_SERVER=europe.pool.ntp.org
NTP_SERVER_1=it.pool.ntp.org
NTP_SERVER_2=0.it.pool.ntp.org
NTP_SERVER_3=1.it.pool.ntp.org
NTP_SERVER_4=2.it.pool.ntp.org
NTP_SERVER_5=3.it.pool.ntp.org
work wich oreo?
For everyone that needs a flashable zip of that *fantastic* mod, see below:
Here
Note that this is an Italian optimized version
If you want to use your gps.conf, just replace the file within the folder /system/etc inside the zip
It's magisk install-able, do not install it by twrp but with magisk instead!
thanks to Dusan for this!
sys01 said:
For everyone that needs a flashable zip of that *fantastic* mod, see below:
Here
Note that this is an Italian optimized version
If you want to use your gps.conf, just replace the file within the folder /system/etc inside the zip
It's magisk install-able, do not install it by twrp but with magisk instead!
thanks to Dusan for this!
Click to expand...
Click to collapse
Hi thanks for your reply, I just have to launch magisk and select this archive file to install it?
OT. Ciao compaesano
Inviato dal mio MI 5 utilizzando Tapatalk
toketin said:
Hi thanks for your reply, I just have to launch magisk and select this archive file to install it?
OT. Ciao compaesano
Inviato dal mio MI 5 utilizzando Tapatalk
Click to expand...
Click to collapse
Go on Magisk -> module -> click on "+" yellow button -> long press on that .zip file and select open
Then after it finishes click reboot and enjoy :fingers-crossed:
Ciao!
sys01 said:
Go on Magisk -> module -> click on "+" yellow button -> long press on that .zip file and select open
Then after it finishes click reboot and enjoy :fingers-crossed:
Ciao!
Click to expand...
Click to collapse
Ok thanks, it should works also under Lineage right?
Edit: flashed on Los and working fine, i've installed also gps locker with the autostart setting on the GPS turn on.
Inviato dal mio MI 5 utilizzando Tapatalk
I have installed your gps.conf file on my Mi5 running AospExtended ROM with 7.10.12 FW.
It didn't change a single thing. With or without the mod I am seeing satellites but signal is almost null. Only in VERY open spaces I am able to fix GPS.
This is the situation indoor compared to a Galaxy A5 2016.
I also have changed FW to 7.10.19, no profit
If I get next a window, it gets enough signal strenght to fix, but is still considerably less than the Samsung.
olivercervera said:
I have installed your gps.conf file on my Mi5 running AospExtended ROM with 7.10.12 FW.
It didn't change a single thing. With or without the mod I am seeing satellites but signal is almost null. Only in VERY open spaces I am able to fix GPS.
This is the situation indoor compared to a Galaxy A5 2016.
I also have changed FW to 7.10.19, no profit
If I get next a window, it gets enough signal strenght to fix, but is still considerably less than the Samsung.
Click to expand...
Click to collapse
Im in the same situation as yours
The thing i'll try to see if i can fix that is to revert back to 6.11.10 that is the last miui7 for mi5 (people says that GPS there is perfect)
if it'll wont work, then i'll try to clean flash with MiFlash some Stable MM roms and see
Background information:
Ever since Android Nougat roms came out, google started using the sim card to set the WiFi region code on the device, and for some countries, this completely breaks the WiFi functionality, some details about the subject here : WiFi_regional_problem_on_Android.
This was possible to fix on Nougat by following this tutorial : WiFi Country Problem Solving for AOSP, MIUI & others , but when Oreo roms started coming out, they we odexed out of the box, which meant to actually apply this fix you needed to deodex the rom and then apply the fix, a bit of headache.
Once Xposed became available for Nougat & Oreo, an xposed module was created that fixed the issue and allowed us to use WiFi normally : Wifi region fix
Recently, Pie based roms started showing up for the Z2, and with them came back the same WiFi issue, and while there's a sort of working Xposed solution, EDxposed, it works through magisk and atm does not support resources hooking, which means the xposed module can't work it's magic.
Solutions and Status:
I've been trying to find a fix for this, and I have followed various guides on the internet, but they don't seem to work.
First of all I've deodexed the /framewrok folder using TOAD (The open-source Android Deodexer), then have followed these suggested fixes.
Method 01 (Failed)
WiFi Country Problem Solving for AOSP, MIUI & others
Method 02 (Failed)
WiFi region fix for android N & O
These 2 methods required modifying the telephony-common.jar file
Method 03 (Failed)
wifi country code fix requires root
This method modifies the wifi-services.jar , which is the same way the xposed module works, so I'm hoping to focus on it, another method that uses the same method is on another forum, but basically offers the same directions MIUI wifi region fix
My problem with these 2 methods is the config files they show seem to use ".registers" command, while the files to modify for our Z2 use the ".locals" command, and from what I can see both define the number of variables we can use inside the ".method" with a slight difference, for example a ".registers 3" will allow you to use 4 total variables, like v0, v1, p0, p1, while ".locals 3" will allow you to use 4 of each variable, like v0, v1, v2, v3 and p0, p1, p2, p3. This is my personal observation, since I wasn't able to find any specific info on this matter using google.
Update: it seems this is related to how I was decompiling the jar file, if I used apktool with the -d switch, I get the files using the ".locals" version, but if I decompile using "BatchApkTool" i get the files using the ".registers" version, although making changes and recompiling/decompiling reflects the results in different ".registers" & ".locals" changes.
But there's still another difference, in those guides they show :
Code:
.method public setCountryCode(Ljava/lang/String;Z)V
.registers 9
const-string[COLOR="Blue"]/jumbo[/COLOR] v2, "WifiService"
and the fix is to add another line after that :
Code:
const-string[COLOR="blue"]/jumbo[/COLOR] v6, "US"
I'm not sure what is the /jumbo thing is, but it doesn't exist in our version of that file, in the Z2 file we have:
Code:
.method public setCountryCode(Ljava/lang/String;)V
.registers 5
.line 2174
const-string v0, "WifiService"
and my change was:
Code:
.method public setCountryCode(Ljava/lang/String;)V
.registers 6
.line 2174
const-string v0, "WifiService"
const-string v3, "US"
flashed the resulting file, but it's still not working, I really feel I'm close but still somehow doing something wrong, so any insights/guidance/help would be Very Much appreciated.
Update:
Working with wifi-service.jar didn't give any results, tried multiple modifications but once WiFi was gone, that was it, even airplane mode didn't allow me to see any networks, so I went back to work on telephony-common.jar , and there seems to be some progress.
Right now, if I use the modified version, put the phone in airplane mode and reboot, I'll have WiFi working as long as the phone remains in airplane mode, once airplane mode is disabled and the phone detects the sim, WiFi will stop working until I activate airplane mode again AND reboot.
I'll do more testing tomorrow, that's it for tonight.
Updates:
i'm currently stuck at the airplane mode & reboot point, which is achieved by doing the following changes in the MccTable.smali file inside telephony-common.jar :
.line 199
:cond_1
goto :goto_0
then comment out line 225
I feel I need to do something about the following part
.method private static setWifiCountryCodeFromMcc(Landroid/content/Context;I)V
in one thread it is suggested to change .locals 3 to .locals 13, but this is a useless change as it simply increases the number of variables the can be used and is not related to the "local" of the rom.
Maybe this will help you out. I'm using this to access 5GHz networks on Oreo/Pie
Yoxxel said:
Maybe this will help you out. I'm using this to access 5GHz networks on Oreo/Pie
Click to expand...
Click to collapse
Sorry for the late reply, and thanks for your suggestion, but it doesn't work.
Originally we could disable the auto region function by modding the code, but now even removing the entire method isn't enough, it seems there's something new to find out and learn, then we can stop this feature
Made a post here let's see if it gains any traction with the Ed Xposed people
ali6944 said:
Made a post here let's see if it gains any traction with the Ed Xposed people
Click to expand...
Click to collapse
Of EdXposed gets the resources hook function then it'll work, until then no.
Hi Guys, ANY recent update on the wifi regional problem in the Android pie?
So uh, this guy on the AOSP Extended thread posted this https://forum.xda-developers.com/showpost.php?p=79245747&postcount=157
just tried it with the same rom, it works just fine.
ali6944 said:
So uh, this guy on the AOSP Extended thread posted this https://forum.xda-developers.com/showpost.php?p=79245747&postcount=157
just tried it with the same rom, it works just fine.
Click to expand...
Click to collapse
I tried it, and it doesn't work for me, can you provide more details, like your device model?
I'm looking for the WiFi region fix, not 5ghz fix, is this the same for you?
ticktock666 said:
I tried it, and it doesn't work for me, can you provide more details, like your device model?
I'm looking for the WiFi region fix, not 5ghz fix, is this the same for you?
Click to expand...
Click to collapse
Yes, we're both looking to solve the same problem, from my understanding of the module thread, it sets your wifi code based on your device language, mine was US English, when i installed the module through magisk the last line of the output was (your wifi country code is set to US), the rebooted and it was working fine.
you might want to mess around with your device language and give it a try
i'm using a D6503 btw
ali6944 said:
Yes, we're both looking to solve the same problem, from my understanding of the module thread, it sets your wifi code based on your device language, mine was US English, when i installed the module through magisk the last line of the output was (your wifi country code is set to US), the rebooted and it was working fine.
you might want to mess around with your device language and give it a try
i'm using a D6503 btw
Click to expand...
Click to collapse
From what I was told by someone who understands code better than myself, this module modifies the /system/vendor/bcmdhd.cal and sets the ccode inside it from the ROM local, for example I was using great Britain English, so it was at to GB, but it didn't work. I've tried changing the code manually, but nothing I tried worked for now.
Someone in the extended aosp thread also reported the issue being fixed without using anything, so I'm downloading it to test, as I've been testing using the carbon ROM beta.
ticktock666 said:
From what I was told by someone who understands code better than myself, this module modifies the /system/vendor/bcmdhd.cal and sets the ccode inside it from the ROM local, for example I was using great Britain English, so it was at to GB, but it didn't work. I've tried changing the code manually, but nothing I tried worked for now.
Someone in the extended aosp thread also reported the issue being fixed without using anything, so I'm downloading it to test, as I've been testing using the carbon ROM beta.
Click to expand...
Click to collapse
Interesting, I'm back on CR oreo now and I wanted to check if it works on it so I can finally uninstall xposed, but it did not, i still remember booting AOSP Ex without magisk while flashing it for the first time after finding out about the module and having no wifi till after I flashed it. Let me know what you find!
ticktock666 said:
From what I was told by someone who understands code better than myself, this module modifies the /system/vendor/bcmdhd.cal and sets the ccode inside it from the ROM local, for example I was using great Britain English, so it was at to GB, but it didn't work. I've tried changing the code manually, but nothing I tried worked for now.
Someone in the extended aosp thread also reported the issue being fixed without using anything, so I'm downloading it to test, as I've been testing using the carbon ROM beta.
Click to expand...
Click to collapse
I wrote that script, but to be honest I didn't test it for every language.
Are you sure the module did output "Your ccode has been set to GB" ?
AFAIK Great Britain should be UK, not GB.
You could try to edit bcmdhd.cal manually and set CODE="UK" , save and reboot.
marcogiannetta said:
I wrote that script, but to be honest I didn't test it for every language.
Are you sure the module did output "Your ccode has been set to GB" ?
AFAIK Great Britain should be UK, not GB.
You could try to edit bcmdhd.cal manually and set CODE="UK" , save and reboot.
Click to expand...
Click to collapse
Yes the output was GB, and I checked the file too, it wasn't UK.
Somehow this issue is fixed in the latest aosp extended build, so I'm hoping the Dev will share his fix with us, and then maybe we'll be able to come up with a universal fix method that can be applied to any ROM.
ticktock666 said:
Yes the output was GB, and I checked the file too, it wasn't UK.
Somehow this issue is fixed in the latest aosp extended build, so I'm hoping the Dev will share his fix with us, and then maybe we'll be able to come up with a universal fix method that can be applied to any ROM.
Click to expand...
Click to collapse
I tried that magisk module on android pie cr7 (Xperia z3) and it changed the ccode to US, It didn't work for me (My phone language is English (United state)). You said that this issue was fixed on a custom ROM that you Installed. Can you upload your bcmdhd.cal file (in \system\vendor\firmware folder) to see the difference between yours and mine? maybe we can figured it out what causes this issue.
Tnx
Maxine76 said:
I tried that magisk module on android pie cr7 (Xperia z3) and it changed the ccode to US, It didn't work for me (My phone language is English (United state)). You said that this issue was fixed on a custom ROM that you Installed. Can you upload your bcmdhd.cal file (in \system\vendor\firmware folder) to see the difference between yours and mine? maybe we can figured it out what causes this issue.
Tnx
Click to expand...
Click to collapse
I saw your post in the aosp ex thread, but I'll share what info I have with you:
The region setting is something Google is doing even if the device has no SIM card in it, just getting the "emergency calls only" signal is enough to break WiFi.
I was getting help from @Darkonizer who builds and maintains the pie carbon ROM, and the best results we could get was this, you'll need to switch airplane mode on, enable WiFi, then switch airplane mode off. You'll have to do this every time you turn your WiFi off, it's not ideal, but you don't have to set the entire ROM region to US.
ticktock666 said:
I saw your post in the aosp ex thread, but I'll share what info I have with you:
The region setting is something Google is doing even if the device has no SIM card in it, just getting the "emergency calls only" signal is enough to break WiFi.
I was getting help from @Darkonizer who builds and maintains the pie carbon ROM, and the best results we could get was this, you'll need to switch airplane mode on, enable WiFi, then switch airplane mode off. You'll have to do this every time you turn your WiFi off, it's not ideal, but you don't have to set the entire ROM region to US.
Click to expand...
Click to collapse
Thanks. I know that method but it's kinda annoying to do that every time when wifi is turned off. I decided if the contributer of cr7.0 doesn't decompile that framework.jar , I'll do that by myself.
Is there any success with regional wifi issue? Is there any definite fix?
did it work @ali6944 ?
pls tell me it worked
Bro_toyota said:
did it work @ali6944 ?
pls tell me it worked
Click to expand...
Click to collapse
It unfortunately didn't work and I stopped looking into it after AEX Pie was stable enough for daily use, as the developer implemented a fix into the rom itself.
No description
What is normally in a /data/vendor/modem_fdr folder? I am trying to use this on another device and it doesn't have that folder.. My device has /data/vendor/modem_config it has all the mcfg_hw, mcfg_sw nd ver_info.txt. Is that the same thing?
removed
hardplastic said:
If VoLTE is working on your device, just leave it alone. It's unnecessary but only if you find the module no longer working, delete these two folders to reset.
No, configs won't store at /data since factory reset will wipe them all. I'm not sure if it's working on other devices. You need manual editing the module by adding mbn file if your device doesn't contain your carrier's, add the path on mbn_sw.txt and sign the zip
Click to expand...
Click to collapse
Volte isn't working, that's why I'm here.
I have used efstools to write my mbn to /nv/item_files - but one file keeps on restoring it's self to default -
/nv/item_files/ims/ims_user_agent. My carrier needs the header in this file for volte to work. It worked fine on Android 10 but not 11.
My device doesn't contain the folder /data/vendor/modem_fdr.
When I delete the files in /data/vendor/radio/ they come back when I reboot - so I'm guess that's what it is meant to do.
removed
hardplastic said:
Sounds like not good.
I haven't found the path on my phone, are you using Pixel 3/XL? It's not strict for my carrier to detect header, this device has preinstalled lots of mbn files from various carriers, which also contains my carrier, so all I need is to add the path to make it work. And that's how the module working.
Can you find your carrier from /vendor/rfs/msm/mpss/readonly/vendor/mbn/mcfg_sw/generic?
Click to expand...
Click to collapse
My phone is a Xiaomi Poco F2,
Yep I can find the path, my carrier is Telstra.
The path is slightly different on this device,
It's /vendor/rfs/mdm/mpss/readonly/vendor/mbn/mcfg_sw/generic so I modified the module to that. But still the header reverts.
The actual mbn file does have the correct header in, but ims_user_agent reverts in the /nv/item_files/ims/ - where does it revert it from?
removed
hardplastic said:
Sorry, I haven't used any Xiaomi devices nor MIUI. I guess I can't help you handle this issue. MIUI is completely different from AOSP, which has many deeply modification. Go ask some experts who knows to fix that. Good luck.
Click to expand...
Click to collapse
I'm running AOSP on this device!
Can anyone tell me if this works with any Portuguese carrier?? if not, @hardplastic can you add support for the 3 portuguese carriers?!
I saw the mbn_sw.txt but think that only Vodafone Portugal it's there, it misses two more carriers, NOS and MEO
removed
hardplastic said:
It seems like there's no configuration files for carriers you said above. So it won't work. I would like to update if you can provide them(*.mbn)
Click to expand...
Click to collapse
How can one aquire that?? From other phones that are compatible with VoLTE (prob every new android phone out there except the pixels ones)
removed
what the hell happened here?!
I see lots of discussion on rooting, unlocking bootloader, etc. But I am wondering if there is guide describing how to enable volte for tmobile? That is all I am looking for and I am really not savy/technical when it comes to phones. I have the dual SIM 850 emw and I really dont want to lose use of the phone when tmobile dumps 3g next month. Thank you
Found this. Sort of cryptic.
I used the dailer code on my Samsung to verify VoLTE was enabled, otherwise it doesn't show the setting or that it's even HD.
Apparently AT&T supports this device if your carrier drops the ball. Verify this though...
armodons said:
Thanks for pointing me in the right direction! I now have VoLTE and Wifi Calling working on my LMG820QM (on T-mobile).
I have the BPT variant of the LMG820QM, for which VoLTE and Wifi Calling does not work. After bootloader unlocking and rooting, I tried the above VolteFix-v1 but wanted Wifi Calling. Forcing the option to appear via a profile in Universal Enabler in the hidden menu* did not work and instead caused LG IMS to continuously crash.
*For those interested in the hidden menu, first create an empty folder named "enable_ue" in internal storage. Then go to the dialer and type *#546368#*820#. In Field Test > Universal Enabler you can "Create New Config" and manually enable VoLTE, ViLTE, VoWIFI, and ViWIFI. However, even though these options became enabled in *#*#4636#*#* they didn't seem to actually work.
Next, I tried to crossflash partitions from the US Open kdz but was unable to due to a size mismatch of the OP partition (among other problems).
Finally, since I had already extracted the OP partition from the US Open kdz (G820QM20f_00_NAO_US_OP_0402.kdz), I extracted files that looked relevant and copied them over using a root browser into /product/OP. After setting permissions and restarting, I now have working VoLTE and Wifi Calling!
The files are cust.prop [update: apparently not needed; my existing one worked just fine], all the files in config, and a few folders in priv-app [update: these are the apps for Wifi Calling!] not present in my phone's kdz (not sure which ones if any of these apks are actually needed but since it works I'm not going to experiment more). See attached for details.
Note: Since these files are from the US Open kdz, it will likely only work for US carriers. But the process can be repeated for other regions with the right kdz.
UPDATE: Replaced the attachment, had the wrong files in Config.
** Noticed that upon factory resetting the wrong default APNs are inserted. Had to factory reset on original files, have APNs setup correctly, then copy the attached files (did not copy over cust.prop this time and still worked).
Click to expand...
Click to collapse
Hello jdapp,
I was able to get VoLTE AND VoWIFI on Mint (T-mobile) with these instructions. I also posted what I did on Post 50. The files work for firmware 20 but if you need the ones for firmware 30 let me know.
Awesome thanks. Yes if I could get the firmware 30 files that would be great.
dahveedsolorzano said:
Hello jdapp,
I was able to get VoLTE AND VoWIFI on Mint (T-mobile) with these instructions. I also posted what I did on Post 50. The files work for firmware 20 but if you need the ones for firmware 30 let me know.
Click to expand...
Click to collapse
jdapp said:
Awesome thanks. Yes if I could get the firmware 30 files that would be great.
Click to expand...
Click to collapse
No problem, let me know how it goes.
So I have tried to do the bootloader unlock and flash but every time I get a Download fail: Sahara Fail: Q SaharaServer Fail: Process fail?
Any thoughts?