[Working] Dual sim on/off toggle in LOS 14.1 - Xiaomi Redmi Note 3 Questions & Answers

Dual sim on/off toggle commits are merged into Linage os sources https://review.lineageos.org/#/c/163723/
i tried by adding some vendor files from Mi Max (hydrogen) MIUI N :silly:
just capy paste the following files system/framework and give necessary permissions and restart thats it
qti-telephony-common.jar
QtiTelephonyServicelibrary.jar
some how dual sim toggle is working in LOS 14.1 :fingers-crossed:
you can try if you want to

Thanks !
But it does not work with me (and the latest build of Lineageos). Tells me the sim card slots are empty and cannot activate them (but they are active ...)

Related

[Q] Compiled CM, No sound, No IMEI, No sim regcognize

I had compiled Cyanogenmod for my device. But
1) No sound but vibrate work.
2) No IMEI, no network no SIM card recognize.
Do I miss some library or firmware?

[ROM][MIUI][surya] Xiaomi.eu ROM for POCO X3 NFC

How to install Xiaomi.eu ROM for POCO X3 NFC [surya]
We will release fastboot ROM versions until TWRP for surya is released
TWRP is already released, we will make only RECOVERY version of our ROM from now..
Steps to install our ROM for FIRST TIME from China ROM (All your data and files on internal storage will be deleted!)
- Unlock your bootloader by Mi Unlock tool https://en.miui.com/unlock/
- Download our ROM zip file HERE
- Unpack downloaded zip file in the PC
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via USB cable
- Run fastboot installation script from unpacked zip according your PC operating system:
For Windows OS ./windows_fastboot_first_install_with_data_format.bat
For Linux ./linux_fastboot_first_install_with_data_format.sh
For MacOS ./macos_fastboot_first_install_with_data_format.sh
- After reboot its done (first boot may take up to 10min)
Steps to install UPDATE of our ROM (All your data and files on internal storage will NOT be deleted!)
- Download our ROM zip file STABLE
- Unpack downloaded zip file in the PC
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via USB cable
- Run fastboot installation script from unpacked zip according your PC operating system:
For Windows OS ./windows_fastboot_update_rom.bat
For Linux ./linux_fastboot_update_rom.sh
For MacOS ./macos_fastboot_update_rom.sh
- After reboot its done (first boot may take up to 5min)
Update via OTA:
Installation via OTA is currently not possible due to missing TWRP
Updater will notify you about new version and download it to your device for you
You have to copy it to your PC, unpack it and run fastboot_update_rom sctipt
Xiaomi.eu ROM features
Based on China Stable / Weekly builds (except POCOF1, HMNote6Pro, HMNote8T, HMNote9ProMax, HMNote9Pro_HMNote9S, HMNote9ProEU)
Enabled search gesture (swipe up) on the desktop
3way reboot menu (in dev settings)
Dark Mode (Night Mode) for all devices (In the dev settings except 9.x/10.x)
Removed ads in MIUI system apps
Face Unlock for all devices
Vertical clock widget on lockscreen
Steps counter in Assistant screen
More shortcuts on left lockscreen
Wake up gestures
AI preloading option in MIUI Lab
Fullscreen gestures
Option to auto-expand first notification
Notifications priority settings
More edit options in Gallery app
Enabled MiDrive in File Explorer
Added landscape mode for SMS app
Sunrise/Sunset in the weather app
Google apps support integrated
Removed 5GHz region restrictions
Confirm dials from call logs
Morning report on alarm at morning
More apps supported for AOD notifications
More styles for AOD screen
Raise to wake gesture
AOD notification received animation
Default volume control stream toggle
Tap fingerprint sensor to wake toggle
More Camera features
Double tap to lock screen
Battery AI scenes
Allowed disabling specific system apps
Importing theme .mtz from zhuti.xiaomi.com via ThemeManager
No useless Chinese bloatware apps
More free RAM due to less background processes
Unified flat style app icons for both system and 3rd party apps
Advanced menu with color icons
No any Chinese character under the full system
Mi Video, Mi Music, Mi Browser: No any useless Chinese content
No possibility to re-lock bootloader accidentally with flash any xiaomi.eu release
Added real 27 languages translation made by Official MIUI Fansites and MIUI Fans
Added EU T9 dialer support
Added charging sound switch
Added Screen-OFF animation
Optimized GPS settings for EU
Optimized Battery consumption
Optimized RAM consumption
Added 3D Touch to MI5S 3GB RAM version
Added GSMalphabet into SMS app options
Added more icons grid layout 4x5, 4x6, 4x7, 5x5, 5x6, 5x7 (depends on device)
SafetyNet passed (Google Pay)
Play Store Certified
Deodexed
Added automated tasks in Security app
Added game speed booster
Added erase module (magic elimination) to Gallery photo edit options
Fixed low volume sound via headphone
Charging screen
And more, and more made by our 9 years MIUI mods experience.
Enjoy..
As I know, Poco X3 doesn't have china rom, So should I understand as from Global rom?
can somebody confirm this eu rom is working properly?.
No, doesn'r. Flash runs normally but when you turn on your phone and are at that point, where you try to activate your device by connecting to your Wifi, it just turns off. Result, you can't pass that point.
Louis235 said:
No, doesn'r. Flash runs normally but when you turn on your phone and are at that point, where you try to activate your device by connecting to your Wifi, it just turns off. Result, you can't pass that point.
Click to expand...
Click to collapse
you mean during initial setup? device reboot itself or just Wi-Fi doesn't work?
Everything runs fine. At the initial startup you can't turn your wifi on and thus can't activate your device
Louis235 said:
Everything runs fine. At the initial startup you can't turn your wifi on and thus can't activate your device
Click to expand...
Click to collapse
And mobile data works?
No, but that's normal. At the very beginning I always have to connect to Wifi, then activate decice, then type in my Sim-Pin and then Data work as usual
Louis235 said:
No, but that's normal. At the very beginning I always have to connect to Wifi, then activate decice, then type in my Sim-Pin and then Data work as usual
Click to expand...
Click to collapse
ROM reuploaded.. try it now and check if Wi-Fi is OK now..
ingbrzy said:
ROM reuploaded.. try it now and check if Wi-Fi is OK now..
Click to expand...
Click to collapse
Thanks a lot fort your efforts. Just downloading
Is it working now?
Sent from my M2007J20CG using Tapatalk
Still that bug exists
Hi there,
Is this rom working properly? This is my first Xiaomi device and I don't want to mess it up
Louis235 said:
Still that bug exists
Click to expand...
Click to collapse
try install this boot.img via fastboot
Code:
fastboot flash boot boot.img
Now I have to flash Global Rom and stick to it, because next days I don't have that much time. But will come back to eu, because it's best Rom by far. Once again big thanks for your work
---------- Post added at 06:42 PM ---------- Previous post was at 06:41 PM ----------
ingbrzy said:
try install this boot.img via fastboot
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
Ok, will try directly
---------- Post added at 06:47 PM ---------- Previous post was at 06:42 PM ----------
Flash runs flawlessly. Boots normal, but bug still there
Download Link doesn´t work
ingbrzy said:
ROM reuploaded.. try it now and check if Wi-Fi is OK now..
Click to expand...
Click to collapse
The Download Link above doesn´t work. Can you please post the actial Link?
THX
Is it possible to remove google play services + store from the xiaomi.eu rom? I would very much like to run the phone without the google stuff, but don't know if that is possible.
Phone, contacts and message applications are from google or MI?
199999 said:
Phone, contacts and message applications are from google or MI?
Click to expand...
Click to collapse
Xiaomi.eu apps are always original MIUI ones and never from Google..
keenan316 said:
Xiaomi.eu apps are always original MIUI ones and never from Google..
Click to expand...
Click to collapse
Nice.

VoWiFI + VoLTE on LineageOS17.1 OP3(T) on T-Mobile (Germany) and possibly more

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.

SD Card + 2 sim hack Bypass solution

Greeting
I've a problem in my Note 9 device
Not allowing to USE 2 SIM card + SD Card hack
it works fine but an error/blocking message from Samsung "There seems to be something in your SIM card tray slot that doesn't belong there, Check it and try again"
Any solutions ?
Tweaks: bypass MicroSD/Sim2 tray lock
So as most of you know, in latest Oreo firmwares Samsung added a check to prevent using both Sim2/MicroSD at same time in one slot (screenshot in attachments), fortunately this lock is pretty much easy to bypass, do this:
Decompile services.jar, open /com/android/server/StorageManagerService.smali class and in it search for isSimSdBlock() method. It should look like this:
Once you found it, all you have to do is to make sure the method always returns false, so basically all you need to do is to replace the whole method code inside to match this:
Code:
Recompile services.jar, push it on your device, profit
Credits to @corsicanu for the finding, don't forget to credit him if you're gonna use this little tweak on your project
Only solution i found but don't understand what is serviecs.jar where i can find it in my phone

How to keep VoLTE compatibilty with AOSP for XZ1 (USA)

Same tricks with a bit little bit of a different story to get VoLTE functioning on an AOSP build. First you'll want to read this post to get an idea of how to bundle the XZ1 Compacts Modem and OEM partition .imgs for an XZ1. Please be familiar with the setup of software to flash your device safely and properly (insert usual disclaimer here for those who are fresh to the procedure).
First step: gather modem_X-FLASH-ALL-C93B.sin & oem_X-FLASH-CUST-C93B.sin from the XZ1 Compact for the US (Customized build, not a carrier specific one; if you want, you can try other builds depending on your region/country or for RX/TX testing). Gather an XZ1 bundle for your model (most recent firmware available).
Second step: delete corresponding modem.sin and oem.sin from the XZ1 build and place the two gathered from the XZ1 Compact into the XZ1 build. Creating seperate folders not nested within the firmware/Downloads/ directory helps keep things organized during the swap. Keep in mind, build versions should be the same as should the Android version.
Third step: bundle and flash the build.
Fourth step: boot the device with the SIM inserted and it will provision the modem with the carriers configuration (if there is one).
Fifth step: dial *#*#4636#*#* and select the active SIM slot change Prefered Network Type to LTE only (note you may have to enable/disable airplane mode to establish a connection).
At this point you should be able to make a call and the Dialer will state the call is in HD. If not, sometimes the Prefered Network Type will revert upon first provisioning, check that it hasn't and if so set it back to LTE only (it may take a minute or two to register with the network).
Once you have confirmed and established VoLTE for calling you can proceed to install an AOSP build.
TWRP is recommended for any build containing Customization Selector and Xperia Parts; boot into recovery and install whichever build you decide.
Sixth step: after flashing your build.zip of choice do not reboot. You'll want to make sure to remove the following two apps before first boot into the newly flashed system. At the main TWRP recovery menu tap Mount and check off System, back at the main menu tap Advanced and tap Terminal, type:
cd /system/system_ext/priv-app
and then type:
rm -Rf CustomizationSelector XperiaParts
*probably not necessary, but do it anyway: go back to the main menu and tap wipe and tap advanced and wipe Dalvik and Cache only.
Seventh Step: boot into the build of your choice and you will notice the System is not resetting upon SIM detection on first boot. Once you are finished with initial setup return to the Testing/Phone Info/Network Configuration app ( *#*#4636#*#* ) and set your Prefered Network Type back to LTE (again, you may have to enable/disable airplane mode to establish a connection). From boot it is normal for a brief network connection to disconnect and re-establish after a minute, at which point it doesn't disconnect again unless there are other network issues in the area.
Caution: for those who have more than one device or SIM slot and switch their sim card from one to the other. Once carrier provisioning is triggered again for another IMEI the configuration will not be able to be provisioned again with the XZ1 AOSP build (until @derf elot or whomever the dev is that authored the apps removed fixes how the modem is provisioned and which configs it has to choose from). Erasing oem and modem via fastboot and reverting back to the stock build (without the partition swap) followed by the above is the only way to return it back to a functional state with the carrrier for AOSP.

Categories

Resources