Enable/disable single SIM via command - Wileyfox Swift 2 Questions & Answers

After unsuccessfully searching the web for a solution, I'm now hoping here for help.
My problem: I want to enable/disable a single SIM (SIM1 or SIM2 only) via command, so i can automate it via tasker
I'm running LineageOS 14.1 (20171121)
Thanks in advice!

Related

[Q] Anycut Commands

Team,
I have tried searching for this but no help
I am using S3 box standard no modifications. with 4.1.2
I downloaded the Anycut & installed it. When trying to create my own shortcut I get asked following
Action
Data
Type
I am a novice & have no idea about this. I am trying to create a shortcut to
phone / Settings / call forwarding / voice call / always forward
Any help will be highly appreciated.
VRF

[Q] Toggle Location Services Through Shell On Marshmallow

Hi,
I used to have a a tasker profile which I used on lollipop that toggled location services through this shell code.
settings put secure location_providers_allowed gps
I know this doesn't work in marshmallow so I found another line of code that some have said works with toggling mobile data by defining the context.
su*-cn u:r:system_app:s0
But when put with the location services code it still doesn't work. And I have SuperSU 2.68 flashed.
Maybe it is a different context for location services?
Does anyone have any more knowledge on this or a fix?
Kind Regards
Andrew
Need the same thing
vazersecurity said:
Need the same thing
Click to expand...
Click to collapse
Hello,
need this too... Any help would be appreciated !

[HELP] Use amazfit pace with broken touch as Watch only? :confused:

Hello guys!
I think the touchscreen of my amazfit pace is broken. I've tried to unbrick it many times, flashed many different roms and even some custom recoverys; but the touch is just not working.
Is there a way to delete / deactivate all functions like wifi, bluetooth etc. and some "apps" in order to just use it as a watch and extend the battery life? When it is coupled with the phone, it stills shows notifications etc, which is very annoying...
Hope you can help!
Thank you!
hi there
im not sure if its works but you just try it our since your watch already left no option
- search in the forum here to download 'android sdk''
- connect watch to computer (with installed android sdk)
- open power shell or command prompt (cmd) and go to location where you extract the file eg c:\sdk
- type "adb shell pm list packages" and you get a list of all installed packages
- type "adb uninstall "package-name" to uninstall ---> replace this "package-name" with the shown exact package name
- the package name seem much self explainable but un-install at your own risk and may result your watch total gone RIP.
FLEXITRON said:
Hello guys!
I think the touchscreen of my amazfit pace is broken. I've tried to unbrick it many times, flashed many different roms and even some custom recoverys; but the touch is just not working.
Is there a way to delete / deactivate all functions like wifi, bluetooth etc. and some "apps" in order to just use it as a watch and extend the battery life? When it is coupled with the phone, it stills shows notifications etc, which is very annoying...
Hope you can help!
Thank you!
Click to expand...
Click to collapse

change system settings from script

Goodmorning everyone,
If possible, I would like to be able to change system settings via script or cmd command.
I'll explain.
I have a xiaomi mi 9 t dual sim, sim 1 is default for calls and sim 2 for internet.
I need to use the internet even in a call, so I would like to change the default sim for internet from sim 2 to sim 1 during the call.
I can do automation with macroandroid or similar, but I need to run a script that does the switch.
it's possible?
Thanks
if u r using miui that is easy to do via Settings,
and below is 2nd way, worked for many roms
need root and termux.
$ su
$ settings list global |grep sim
multi_sim_data_call=1
multi_sim_sms=1
multi_sim_sms_prompt=1
multi_sim_voice_call=2
ok,now change to 2nd sim
$ settings put multi_sim_data_call 2
back to 1st
$ settings put multi_sim_data_call 1
different roms may have different key value.

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.

Categories

Resources