In all the available MIUI ROMs for our device there is no option of Network Mode (so cannot switch to 2G).
I have tried some things with Settings.apk (decompiling and changing the xmls) to enable this option but recompiling MIUI Settings.apk is not moving further throwing exception of making the apk (actually the problem was with the apktool available)
Need help in this. Everything in MIUI is good for the basic usage and the only problem facing is with this 2G option (Network Mode) unavailablity.
Related
Excuse my ignorance (and double post), but...
Installed the Stock Samsung Deodexed XXKH3 2.3.4 ROM and it worked a treat. Was wanting to customise/optimise it further, and my understanding was that you:
Open with 7zip or unzip directory
Delete apks
Optimise pngs
Close archive/zip
Sign and install
All my apps are working fine (not actually gotten to optimising the pngs yet) but finding that:
MTP no longer works
No (power button) menu options for airplane mode and data network
And there's no option even in unrooted stock for using mass storage?!
Any suggestions?
At a guess it look like it might have been the deletion of the SetupWizard.apk, though still looking to confirm.
I'm on a virtual provider in my country and roaming on the 'main' provider. This isn't real roaming, but I still have to enable the roaming option in Android.
I've worked with CM ROMs and there's an option named 'National Data Roaming'. This is exactly what I need; no roaming in my own country but still roaming when I travel abroid (real roaming).
I want to add this to a non-CM ROM that I have on my phone now.
I tried the "spn-conf.xml" hack, and added the MCC/MNC of my virtual provider with a fake_home_on the main provider. Doesn't work, looks like the spn-conf is completely ignored in MIUI, stock HTC ROM and another ROM. But it isn't, because when I give this MCC/MNC combo an other spn name, than this new name appears in the mobile network list. So it DOES read the spn-conf.xml file, but DOESN'T fake home on the network...
After that I saw an patched framework.jar on MoDaCo: http://android.modaco.com/topic/342267-universal-mvno-patch/
But there is no framework.jar for a MIUI ROM. I don't now how to patch it myself.
So, what are the other option to tell MIUI that I'm NOT roaming? It isn't specific MIUI only, if I figure out a method then it will work for every ROM I think.
Hello?? Someone?
Or is this something for the developers forum?
I understand that this ROM was put together mainly for Lexmazter's personal use, so thanks for making it available for us all.
I have been testing it for some time now and decided to post a couple of things I have noticed so far. Maybe some of these points could be added to the first post's FAQ in the development section (if they are of any use)?
WiFi patch: http://forum.xda-developers.com/showthread.php?t=1579585
---
This one was a necessity for me, otherwise the WiFi simply silently died/froze after being idle for some time.
Couldn't erase SD card (Settings --> Storage --> Erase SD card)
---
I managed to fix it by copying vold from DSC ROM and replacing the old one (/system/bin).
I got the idea from: https://code.google.com/p/cyanogenmod/issues/detail?id=4004 (comments 7-9)
Useless/detrimental(?) entries in Build.prop:
---
ro.telephony.default_network=0
ro.ril.hsxpa=2
ro.ril.gprsclass=12
ro.ril.enable.amr.wideband=1
I had to nuke those entries to get the phone working & staying in 2G, even after a reboot. Is there actually any reason to force the phone to use 3G when it only seems to override the settings that the user could do in Settings --> Wireless & networks --> Mobile networks? The existence of ro.ril.enable.amr.wideband=1 broke making/receiving phone calls in 2G.
The FCing menu in settings + the non-working reboot option:
---
Settings --> CyanogenMod settings --> Display --> Automatic backlight --> Edit other levels... causes a FC. Reboot phone --> Recovery does not work. These are purely cosmetic things, but they could just be removed as they're doing nothing anyway. Basically what lordmorphous did in: http://forum.xda-developers.com/showpost.php?p=24550723&postcount=43
However, I guess that because this ROM uses theming, the framework-res.apk would be needed to be decompiled etc.. in a proper fashion?
I would love to see more versions and possible improvements of this ROM. For me things like being as close to 2.3.7 as possible + CM's permissions management alone make this a keeper.
Merely_an_observer said:
I understand that this ROM was put together mainly for Lexmazter's personal use, so thanks for making it available for us all.
I have been testing it for some time now and decided to post a couple of things I have noticed so far. Maybe some of these points could be added to the first post's FAQ in the development section (if they are of any use)?
WiFi patch: http://forum.xda-developers.com/showthread.php?t=1579585
---
This one was a necessity for me, otherwise the WiFi simply silently died/froze after being idle for some time.
Couldn't erase SD card (Settings --> Storage --> Erase SD card)
---
I managed to fix it by copying vold from DSC ROM and replacing the old one (/system/bin).
I got the idea from: https://code.google.com/p/cyanogenmod/issues/detail?id=4004 (comments 7-9)
Useless/detrimental(?) entries in Build.prop:
---
ro.telephony.default_network=0
ro.ril.hsxpa=2
ro.ril.gprsclass=12
ro.ril.enable.amr.wideband=1
I had to nuke those entries to get the phone working & staying in 2G, even after a reboot. Is there actually any reason to force the phone to use 3G when it only seems to override the settings that the user could do in Settings --> Wireless & networks --> Mobile networks? The existence of ro.ril.enable.amr.wideband=1 broke making/receiving phone calls in 2G.
The FCing menu in settings + the non-working reboot option:
---
Settings --> CyanogenMod settings --> Display --> Automatic backlight --> Edit other levels... causes a FC. Reboot phone --> Recovery does not work. These are purely cosmetic things, but they could just be removed as they're doing nothing anyway. Basically what lordmorphous did in: http://forum.xda-developers.com/showpost.php?p=24550723&postcount=43
However, I guess that because this ROM uses theming, the framework-res.apk would be needed to be decompiled etc.. in a proper fashion?
I would love to see more versions and possible improvements of this ROM. For me things like being as close to 2.3.7 as possible + CM's permissions management alone make this a keeper.
Click to expand...
Click to collapse
Hi and thanks for the feedback, i would like to begin with the first things.
WiFi patch is not needed if you are using LXdroid Rom 0.2 and baseband 366, i was using it like that a lot and i didn't had any issues with the WiFi...
--
As for erase SD card, i never really tested that feature, but for all i know, it should work just fine...
--
Those useless/detrimental build.prop you put there were left there from the original build.prop of CM7, you can override those settings from Settings, i can assure you that ro.ril.enable.amr.wideband=1 does not break 2G calls as i was most of the time on 2G to save battery, i had the option in power widget to change it ti 3G when i needed internet connection.
The framework-res.apk you provided there will be include in the next update, i think i'm going to release one with small fixes soon.
The framework-res.apk doesn't need to be decompiled in a proper manner, you can use any archiver you like and change the insides of it .
To keep away from any other problems, if you upgraded from 2.3.3 or any other ROM besides CM7 based ones, make sure you fully wipe everything, from dalvik to factory reset from recovery and factory reset from dell (white letters).
--
Will try to update, but it will be only with small fixes
I have recently been trying to flash and root my NEXUS 6 device to try and get VoLTE to work on it ; The instructions I received (at a high level) involved flashing the device with a custom ROM (I have tried LMY47D, LMY47M and LYZ28K) , rooting It, updating the qcril.db (to include my MCC/MNC) , updating the apns-conf.xml (to add my IMS APN) and finally modifying the framework-res.apk to enable the 'config_carrier_volte_available' flag for my MCC/MNC.
After doing all the above, I can confirm that I am now seeing the extra option in SETTINGS->MORE->MOBILE NETWORKS called 'Enhanced 4G LTE Mode' which I have enable along with the extra config that can be done from the *#*#4636#*#* menu.......Unfortunately , my device does not try to REGISTER with the IMS network nor do I see any extra settings on the phone (like IMS calling) to configure IMS specific settings. I have checked the android logs and can see the UE is successfully loading the IMPI,IMPU,DOMAIN and P-CSCF from the ISIM Module however nothing seems to happen.
My one observation is that my added APN (in the apns-xml file) does not show up in APN settings and I have to manually add the IMS APN., so my suspicion is that perhaps I am either not setting this properly or perhaps there is more to all this....Therefore I would like to present this challenge to the clever brains in this forum and would appreciate any guidance that I can get,
Recently I had some bad experiences with bad reception.
At the place of my new girlfriend is very bad GSM and LTE reception. At her place of residence I could not be reached with my OP3T and I could not make outgoing calls. When I called her from home, our conversations were interrupted every few minutes.
Neither with T-Mobile (company card) nor with my Netzclub+ Sponsored card could I make any real phone calls. When I recently gave her a Oneplus 3 I decided to make both devices (+my OP3T) fit for VoWifi and VoLTE.
The goal was that it should work with Lineage 17 for microg.
I have seen here some instructions that helped. There was always just a little something missing to make it work.
Below are the steps necessary to get VoWIFI and VoLTE for T-Mobile up and running:
No root solution required, no bootloader unlock required.
Ony TWRP needs to be installed.
1. Install QPST, (have used 2.7.460)
2. Install Quallcomm Diag Driver, i used 1.1 (have used 10037.3)
3. Extract modem firmware via TWRP (system/etc/firmware, or use mine from download link)
4. Enable adb root in developer settings
5. Enable USB Debugging and connect to device via adb
adb devices (check if device is shown)
adb root
adb shell
setprop sys.usb.config diag,serial_smd,rmnet_ipa,adb
6. Open PDC from QPST with admin rights and choose phone
7. Rightclick on "Overseas..." and deactivate for Sub0 and Sub1
8. Remove the "Overseas..." completely (select it and click remove)
9. Rightclick on "H3G Denmark Commercial" and set config for Sub0 and Sub1
10. Rightclick on the profile again (currently pending state) and select activate a few times until Sub0 and Sub1 are active
11. Modify Build.prop (system/build.prop)
Extract with TWRP and modify locally and add this new block underneath
block #VENDOR_EDIT
[...]
#VOLTE
persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=1
persist.dbg.wfc_avail_ovr=1
persist.radio.rat_on=combine
persist.radio.data_ltd_sys_ind=1
persist.radio.data_con_rprt=1
persist.radio.calls.on.ims=1
persist.sys.cust.lte_config=true
ro.radio_gpri=1
ro.amrwb_gpri=1
persist.data.iwlan=1
#end
[...]
Overwrite the original build.prop with your new one and chmod 0644 (both using
using TWRP File Manager) the file.
12. Put VoWIFI + VoLTE simcard into Slot 1 of sim tray.
13. In Lineage enable VoLTE and Wifi Calling (enable prefer wifi)
To check:
After step 13 wait 20 seconds until sip registration with provider completed, then dial USSD code *#*#4636#*#* to open Field test
Open "Phone information" and check ims registration state
Ims registration=registered means you had success
The provider profile change is done at the EFS partition and stay there until you restore this one via twrp.
If Wifi is off VoLTE is used automatically, sadly Lineage OS 17.1 does not have a VoLTE indicator. But you notice that LTE stays on during call and that there is no delay now.
Without VoLTE there was a 3 seconds delay to switch from LTE to 3G/2G to make the call.
If you call via VoWIFI a new Wifi Icon is displayed in Call window.
Sometimes VoLTE gets preferred over VoWifi, although in wifi call you have set wifi call is prio.
Not sure yet what triggers this.
If you use Volte OpenMarket Commercial profile VoLTE + IMS Video call works, but not VoWIFI. So for us Denmark profile is perfect.
VoLTE also works with Netzclub (O2) card in slot one, but not VoWIFI. Could work with switching to o2 IMS apn (not tested yet since i only plan to use it for telekom currently).
I read that only slot 1 supports VoLTE and VoWIFI (chipset related) which may not be true since during the process i had a condition with VoLTE working in both sim slots (+ ims registred for both). This happened when i loaded the "Idea..." profile for testing purposes. Somehow it triggered a connection crash and did not change the profile but enabled VoLTE for both cards (this time t-mobile volte working in slot 2, netzclub+ volte working in slot 1). But since VoWIFI did not work i loaded Denmark once again and now only slot 1 worked again.
Now it is even possible to activate airplane mode and to call with T-Mobile number via Wifi.
Really cool.
https://mega.nz/file/NUcUxYRR#V2sWJuHSYxHJOuh0vAK-j5777mpT3c6sMyNr24JEwjM
Edit 2020-Oct-03:
Temporary magisk installation no longer required with latest lineage os 17.1 / lineage os 17.1 microg.
Just enable adb root in developer option, and in adb shell type "adb root"
Also attached mbn files only work for 3t, will update download link soon to contain 3 files, too
Can confirm, works on NOS 11 without using *#*#4636#*#*#. No VoLTE logo on the Status Bar, but it has the HD Sign when calling on Google Phone. Thanks for the guide!
thes3usa said:
Can confirm, works on NOS 11 without using *#*#4636#*#*#. No VoLTE logo on the Status Bar, but it has the HD Sign when calling on Google Phone. Thanks for the guide!
Click to expand...
Click to collapse
Would you tell which provider u use? also t-mobile germany?
zezinho7 said:
Would you tell which provider u use? also t-mobile germany?
Click to expand...
Click to collapse
Nope, I'm from Sri Lanka and I use the only provider that gives VoLTE. I had to google which option works with my Carrier, which was "VoLTE_OpenMKT....". Basically works with any carrier that provides VoLTE, a google search is needed to find which description to enable and if you can't, you need to test which ones are required for VoLTE.
Just me dropping by saying this was super helpful!
Running an OP3 on LOS 18.1. Wanted to avoid going back to OOS 9.0.6.
Enabled VoLTE on jaMobil! (T-Mobile Germany Network). I used the "Volte_OpenMkt-Commercial-CMCC" profile.
My profiles were fairly empty - not a single European Country name in the profiles. But worked Thanks again.
EDIT: Since I used the OpenMkt Profile I got everything but VoWifi working. But I don't have any country-specific profiles. Can I load yours somehow?
Ive had this issue and ive found just changing the build.prop locally on the device - Using TWRP
# Debug Options
persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=1
persist.dbg.wfc_avail_ovr=1
# Radio Options
persist.radio.rat_on=combine
persist.radio.data_ltd_sys_ind=1
persist.radio.data_con_rprt=1
persist.radio.calls.on.ims=1
Does the trick
Hallo, I have a problem with the device profiles for the modem. In the firmware there are the mbn-files in /system/etc/firmware/mbn_ota in two directories: mcfg_sw and mcfg_sw_NoCDMA. In QPST I can see the profiles from mcfg_sw, but not the ones from mcfg_sw_NoCDMA which are needed to use the op3 with the german telekom. What am I doing wrong? Trying to install the files via QPST also doesn't work, by using the load button I can choose a file, but the profile does not appear in the profiles.
Would perhaps sombody here who could explain the complete mechanism depending the mbn files in the firmware directory and the profiles shown in QPST?
Thank you very much in advance!
PS: VoLTE worked for a couple of days with the profile CMCC_Volte_OpenMkt-Commercial, but unfortunately the german telekom changed something, so it doesn't work anymore.
felixchris said:
Just me dropping by saying this was super helpful!
Running an OP3 on LOS 18.1. Wanted to avoid going back to OOS 9.0.6.
Enabled VoLTE on jaMobil! (T-Mobile Germany Network). I used the "Volte_OpenMkt-Commercial-CMCC" profile.
My profiles were fairly empty - not a single European Country name in the profiles. But worked Thanks again.
EDIT: Since I used the OpenMkt Profile I got everything but VoWifi working. But I don't have any country-specific profiles. Can I load yours somehow?
Click to expand...
Click to collapse
were you succesful enabling volte/vowifi in the meantime? I'm not able to make it working ...
accuphase said:
were you succesful enabling volte/vowifi in the meantime? I'm not able to make it working ...
Click to expand...
Click to collapse
Switched to a OP 9 Pro in the meantime. But as i have said. VoLTE worked vor me. VoWifi not.