Database Users

[PATCH 3.1][27-06-11] 100% Working 3g huawei compatible USB dongle

*I'm not updating it, but many users find this useful, so thread is kept as is for now*
Not sure if anyone got so far, to getting the honeycomb showing connection and selectable APN in settings?
anyways,
from my port of honeycomb to folio100, and now experiments with a500.. i got huawei dongle's running using the builtin functions.
you will need to have root'd your device. and this might break a system-update, if any of my files are updated during next OTA..
but back to the working 3G.
Working 3G USB dongles:
Do note, your modem version can be seen on its white label written with very small text.
some modems require zerocd (linuxtool) or commands executed in windows to disable the mass storage part of it. (search google for the commands)
* ZTE MF 639 (might need roaming enabled to get data working)
* Vodafone K3765-H
* Vodafone K3715
* Vodafone K3565 / Huawei E160
* Huawei E169
* Huawai E170
* Huawai E171
* Huawei E173
* Huawei E1550
* Huawei E1692
* Huawei E1750
* Huawei E1752
* Huawei E1820
* HUAWEI K3520
* HUAWEI K3565 -Rev 2
Download View attachment 3g-usb-stock1.zip for 3.0.1 stock release Acer_A500_1.141.01_EMEA_GEN3: (vermagic=2.6.36.3 SMP preempt mod_unload ARMv7)
Download View attachment 3g-acer31stock-usb.zip for 3.1 stock release Acer_A500_3.019.01_COM_GEN1 (vermagic=2.6.36.3-00005-g5dff38c SMP preempt mod_unload ARMv7)
HOWTO:
- first: Backup your /system/build.prop on the tablet , just copy the file to a safe place, as its important if you wish to do a online update later on.
- updated zip, so you can now install the zip as an "update" using ClockWorkMod/CWM if you got this installed.
- download the "system.zip" attached to this post.
- unpack all files to a temporary folder ie. C:\myfiles
- assuming you got adb running
* push files to your tablet with;
adb shell mkdir /data/local/temp
adb push C:\myfiles\system /data/local/temp/
* next run
adb shell
* then run all commands below in the shell
su -
mount -orw,remount /system (i forgot this line, ITS IMPORTANT)
cp -a /data/local/temp/* /system/
chmod 4755 /system/bin/pppd
chmod 4755 /system/bin/rild
chmod 755 /system/bin/rild.run
chmod -R 755 /system/etc/ppp
If you done these steps correctly, and you reboot.
you will now have a working 3G option in Settings -> wireless networks
so you can configure your APN now and connect to your 3G network.
and you got it all automated with honeycomb 3g! no terminal needed to start 3G!
HINTS
- Other reports are to remember to "Disable PIN" on the card.. I have no personal experience on this part, but check up on it, if its not working perfectly, or no data, but network is ok.
- I got reports back about enabling roaming to make it work, and also remember the story from Folio100 with 3G dongles..
so if you cannot get data connection at all, try to enable roaming and see if APN does not appear which matches your isp. maybe read you ISP website to confirm it.
- If you happen to remove the dongle, there is a solution (using as example gscript) to restart the ril daemon.
in a shell you can restart the ril-daemon if you reinsert the 3g usb dongle.
do it like this in the shell:
su -
stop ril-daemon
start ril-daemon
HOWTO FOR RESET'ing ,massstorage on Huawei modems.
tasmak said:
Insert modem into pc and wait for driver to install
check in device manager which com port is assignated to your modem
download putty
here the.earth.li/~sgtatham/putty/latest/x86/putty.exe
close every program related to modem
run putty
click serial below port number and then change port number to one previously founded
click open
write atz and press enter, modem should answer ok
write ati and press enter, modem should give name, type, etc
write AT^U2DIAG=0 and press enter, zero cd is now disabled
You need also put sim card from modem to any phone and disable pin checking.
Click to expand...
Click to collapse
Remember to press "thanks" if you find it useful

you forgot to say to remount the system to rw....

thor2002ro said:
you forgot to say to remount the system to rw....
Click to expand...
Click to collapse
i believe that line is even highlighted and commented as forgotten previously, so its there for sure..
you cannot miss it
or do you mean some other /system mount?

Looking forward to testing this. Mine is a Verizon Novatel Wireless, do you think this will work with it?

JackMetal said:
Looking forward to testing this. Mine is a Verizon Novatel Wireless, do you think this will work with it?
Click to expand...
Click to collapse
it would probably work, if you got the huawei dongles..
the major is if you need different kernel modules.. those are in the other thread if needed, i included those without -gxXXXX version info.. as thats the ones for the latest EU model update and works here.

Thanks Dexter. One question. Can these files be pushed using terminal emulator instead?
Sent from my A500 using Tapatalk

Yes,
this can of course be done in a terminal, if needed.
just forget the part with "adb",
but all the commands should be executed, and the files copied to a sdcard temporily and copy from that location to the /system

Dexter thanks. What Huawei modem do you recommend?
Sent from my A500 using Tapatalk

manfly9884 said:
Dexter thanks. What Huawei modem do you recommend?
Click to expand...
Click to collapse
i use a E1752 model myself, which i have disabled storage on, before using it on my tablets...

Thanks
Sent from my A500 using Tapatalk

this wil break the OTA ... because of the build.prop modifications...

thor2002ro said:
this wil break the OTA ... because of the build.prop modifications...
Click to expand...
Click to collapse
Correct, that is also mentioned in post #1.
custom build.prop can be made if the lines at the bottom are copied to your own version you got with a simple one-liner in a shell.
echo "picasso.3g=true
rild.libpath=/system/lib/libhuawei-ril.so
rild.libargs=-d /dev/ttyUSB2
ro.pad.features.modem=true " >>/system/build.prop
so it works on any new build.prop change..

Dexter_nlb said:
Correct, that is also mentioned in post #1.
custom build.prop can be made if the lines at the bottom are copied to your own version you got with a simple one-liner in a shell.
echo "picasso.3g=true
rild.libpath=/system/lib/libhuawei-ril.so
rild.libargs=-d /dev/ttyUSB2
ro.pad.features.modem=true " >>/system/build.prop
so it works on any new build.prop change..
Click to expand...
Click to collapse
got an idea.... make two scripts for applying and removing....
so we can maintain the OTA capability...

thor2002ro said:
got an idea.... make two scripts for applying and removing....
so we can maintain the OTA capability...
Click to expand...
Click to collapse
ill figure something out.. maybe an actual patch can be made?
i do know how to make the different update.zip's ... just got A500, so not sure what is possible and not, on this semi-blocked tablet..
but also know motorola mobiles, i have had my part of blocked devices, and do workarounds to make something work.
1 update.zip to install? and another to remove?

we dont have custom recovery working.... so update zip wont work... scripts or apk are the only choices i see...

thor2002ro said:
we dont have custom recovery working.... so update zip wont work... scripts or apk are the only choices i see...
Click to expand...
Click to collapse
no no, i dont talk CWM.. i use the builtin tegra recovery for the additional functions.. the recovery is very close to CWM, but uses the old htc way, and do have specific write command for writing images..
ill check it out soon.. a500 is still new to me, although tegra is not...

I know im probably not doing something right, i followed the steps, and when i tap mobile networks it force closes?

Good news. Thanks

manfly9884 said:
Thanks
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
wounderful work！
good point！

Any reason this wouldn't work on the asus transformer?

VoLTE and WiFi Calling Working on MetroPCS (and probably other T-Mobile MVNO's)

DISCLAIMER: This will only work on Android 8.0, and may not work on some versions of 8.0 depending on the security patch date. I'm using firmware version 47.A.1.16.20 with a security patch level of 2018/09/01.
I figured out how to get VoLTE and WiFi Calling to work on MetroPCS. The XZ1C works on T-Mobile because it recognizes T-Mobile specific SIM cards and loads the appropriate files when it detects one. For whatever reason, MetroPCS has SIM cards that don't provide a sim_config_id that the phone will recognize as being part of T-Mobile. The list of sim_config_id values that are recognized are contained in a file located within the APK /oem/overlay/com.sonymobile.customizationselector-res-305.apk. Within the APK, the file is located at /res/xml/configuration_selectors.xml. The xml contents are listed below:
Code:
<?xml version="1.0" encoding="utf-8"?>
<configurations>
<configuration config_id="408">
<sim_config_id>S264.1</sim_config_id>
<sim_config_id>S264.2</sim_config_id>
<sim_config_id>S264.3</sim_config_id>
<sim_config_id>S264.4</sim_config_id>
<sim_config_id>S264.5</sim_config_id>
<sim_config_id>S264.6</sim_config_id>
<sim_config_id>S264.7</sim_config_id>
<sim_config_id>S264.8</sim_config_id>
<sim_config_id>S264.9</sim_config_id>
<sim_config_id>S264.10</sim_config_id>
<sim_config_id>S264.11</sim_config_id>
<sim_config_id>S264.12</sim_config_id>
<sim_config_id>S264.13</sim_config_id>
<sim_config_id>S264.14</sim_config_id>
<sim_config_id>S264.15</sim_config_id>
<sim_config_id>S264.16</sim_config_id>
<sim_config_id>S264.17</sim_config_id>
<sim_config_id>S264.18</sim_config_id>
<sim_config_id>S8663.1</sim_config_id>
</configuration>
</configurations>
In order to get the MetroPCS SIM recognized, you need to add one line to the bottom of the list. This changes the code to the following:
Code:
<?xml version="1.0" encoding="utf-8"?>
<configurations>
<configuration config_id="408">
<sim_config_id>S264.1</sim_config_id>
<sim_config_id>S264.2</sim_config_id>
<sim_config_id>S264.3</sim_config_id>
<sim_config_id>S264.4</sim_config_id>
<sim_config_id>S264.5</sim_config_id>
<sim_config_id>S264.6</sim_config_id>
<sim_config_id>S264.7</sim_config_id>
<sim_config_id>S264.8</sim_config_id>
<sim_config_id>S264.9</sim_config_id>
<sim_config_id>S264.10</sim_config_id>
<sim_config_id>S264.11</sim_config_id>
<sim_config_id>S264.12</sim_config_id>
<sim_config_id>S264.13</sim_config_id>
<sim_config_id>S264.14</sim_config_id>
<sim_config_id>S264.15</sim_config_id>
<sim_config_id>S264.16</sim_config_id>
<sim_config_id>S264.17</sim_config_id>
<sim_config_id>S264.18</sim_config_id>
<sim_config_id>S8663.1</sim_config_id>
[COLOR="Red"][B] <sim_config_id>S8957.1</sim_config_id>[/B][/COLOR]
</configuration>
</configurations>
If you're on a different T-Mobile MVNO that supports VoLTE and WiFi Calling, but it's not working on your XZ1C, you can probably still get this to work. You'll need to figure out what sim_config_id to use using the following command:
Code:
adb shell getprop persist.sys.sim_config_ids
This should output a value similar to S8957.1. Use your value in the configuration_selectors.xml file.
You also need to change the overlay priority in the AndroidManifest.xml file. The normal overlay has a priority of 305. I changed mine to 310, but anything over 305 should work.
Code:
<?xml version="1.0" encoding="utf-8" standalone="no"?><manifest xmlns:android="http://schemas.android.com/apk/res/android" package="[B]your.package.name[/B]">
<overlay android:priority="310" android:targetPackage="com.sonymobile.customizationselector"/>
</manifest>
In order to modify this APK, I used apktool to decompile the original APK and compile the modified APK.
https://ibotpeaches.github.io/Apktool/
I followed the guide located here:
https://forum.xda-developers.com/showthread.php?t=2213985
Once the APK is built and signed, install it with adb
Code:
adb install yourapkhere.apk
This is an overlay file which works using RRO, so you need to give the file the proper permissions to run. Enter the following command:
Code:
adb shell cmd overlay enable --user 0 yourapkhere.apk
Reboot your phone and the overlay should be active.
Due to the way the phone works, you need to trick the phone into loading the correct modem binary file. It loads a default modem when it doesn't recognize a T-Mobile SIM. But it won't load the T-Mobile modem even if you install the APK. I ended up having to get an unactivated T-Mobile SIM and put that in the phone to trigger the switch. Once you trigger it, you'll get a popup saying that the phone needs to reboot to optimize for your network. After it reboots and loads the proper modem, you can shutdown, put in your MetroPCS SIM card and boot. That should do it.
There's one big caveat: This will only work on 8.0. The overlay permission model changed in 8.1+ so this change won't work on those ROM's. The fix is still good, but you'd need to use root to make the change. I'm sure there will be a way around this eventually, but I don't have one at the moment.
For more technical information, I tracked my progress trying to get my X Compact working on MetroPCS with VoLTE and WiFi Calling. There's a lot of information regarding the XZ1C in there that might be of interest.
https://forum.xda-developers.com/x-compact/how-to/trying-to-figure-how-to-enable-volte-t3877692
Theoretically, this should work for the XZ1, the XZ Premium (with proper files flashed), and possibly other Sony phones that contain the correct modem binary file. If you get it to work, please reply to the thread.

Here are some pictures showing the features working.

camdecoster said:
Here are some pictures showing the features working.
Click to expand...
Click to collapse
What program did you use to check if volte and wifi calling works or not?

Yevgen.A said:
What program did you use to check if volte and wifi calling works or not?
Click to expand...
Click to collapse
I didn't use a program, just the dialer. If LTE stays on during a call, that means VoLTE is working. A WiFi call will show the symbol seen in my picture.

Fix for Android 9?

echo124 said:
Fix for Android 9?
Click to expand...
Click to collapse
As mentioned in the OP, this fix only works on Android 8. If you're on 9, you'll have to root.

camdecoster said:
As mentioned in the OP, this fix only works on Android 8. If you're on 9, you'll have to root.
Click to expand...
Click to collapse
Great, how to apply after? Danke

echo124 said:
Great, how to apply after? Danke
Click to expand...
Click to collapse
You should be able to follow the same procedure, though you'll likely need to unlock the bootloader.

.

Forcing VoLTE support on Mi-A2 Pie [root] when carrier supports

Hello, Just a small hack that allows me to use the VoLTE that my provider points out is "only available on handsets purchased directly from them" (SFR in France). This got me thinking ==> If VoLTE works on their handsets and not mine then :
a) The carrier infrastructure supports VoLTE
b) The sim cards must be provisioned correctly
c) The difference would therefore be in the telephone configuration ==> I'm thinking build.prop config in their "special firmware"​
So looking through various forums - I came across the following:
https://forums.oneplus.com/threads/root-working-volte-on-stock-oxygen-3-1-0.480128/, https://forum.xda-developers.com/apps/magisk/module-v4-volte-enabler-t3649613 and https://source.android.com/devices/tech/config/carrier (to help understand what IMS is all about)
Here's what I added to the end of my build.prop [you will need root for this]:
Code:
#VoLTE - force the IMS into VoLTE provisioned mode on.
persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
If you don't want to do that directly in the build.prop you can do this directly from a debug shell
Code:
adb shell
$ su
# setprop persist.dbg.ims_volte_enable 1
# setprop persist.dbg.volte_avail_ovr 1
# reboot
Please note that this did indeed allow me to make/receive calls and use 4G at the same time.
I also see "HD 4G" logo appear to the left of my signal bars.
When I look at my phone config (dial *#*#4636#*#*) I see VoLTE as provisioned.
I think that these lines force the phone to use VoLTE - the risk is that this might break your 4G - you have been warned. I don't guarantee that this works for you.

Can an administrator place this in the https://forum.xda-developers.com/mi-a2/how-to forum please ?

I made this change with temporary root when i activated api for gcam, put this lines with temporary root and get OTA too

if yuou don't have root you can use *#*#86583#*#* . tested working on sfr too.

Tried that but that didn't work... This root build.prop stuff did... I have also added keys for video calling and VoWiFi but until I see those working I'm not keen to publish...

duxxyuk said:
Tried that but that didn't work... This root build.prop stuff did... I have also added keys for video calling and VoWiFi but until I see those working I'm not keen to publish...
Click to expand...
Click to collapse
VoWifi how? Whats the code?

I've got these lines on the back of my build.prop but it doesn't appear to work for me:
Code:
#WiFi calling
persist.data.iwlan.enable=true
persist.dbg.wfc_avail_ovr=1

rober788 said:
I made this change with temporary root when i activated api for gcam, put this lines with temporary root and get OTA too
Click to expand...
Click to collapse
How does a temporary root work? I can't find anything with Google.

Magisk module VoEnableer maybe the best chois.

Thanks for sharing.. it also works on mi a2 lite

Thanks, It works

[Guide] How to Enable Miracast for Pixel

Introduction
Few weeks ago, I got a Pixel 1 as my backup phone, when I try to connect it to the Microsoft Wireless Display Adapter, it couldn't find the Adapter.
I haven't used Android phones for a long time. In my mind, Android natively supports Miracast. After some searching, I was frightened to find that Google has removed Miracast from Android.
I was really disappointed because I often cast my Windows devices easily by using Miracast. My Projector has only two HDMI ports, one for HDMI cable, and one for Wireless Display Adapter. I can't add a Chromecast unless a HDMI switch is used.
One possible solution is to add a line "persist.debug.wfd.enable=1" in "build.prop" to enable WiFi-Display, but many people say that it doesn't work since Android N, the phone can discover WiFi-Displays but unable to cast.
Since Android framework is open source, I did some searching and found that some WiFi-Display related code still exists. Android 9 still keeps the WifiDisplayAdapter in DisplayManagerService, but removed WifiDisplay from MediaPlayerService, that's why we can discover WiFi-Displays but can't cast.
I recovered some code from AOSP history commits, fixed the build errors, and debugged on my Pixel, finally the Miracast can work on my Pixel.
If you also want Miracast to work on your Google phones, you can follow my steps, but first make sure your ROM is open source so that you can change and rebuild it.
If you have a Pixel 1 running the same version of system, you can simply replace some files in your system with the files I built.
If you have other Google phones or running different versions, you can apply my patch to AOSP, and build it by yourself. I have built the latest version for all Google Pixel phones, but I haven't tested except Pixel 1.
If your ROM is not open source, I will no longer be able to help, since MediaPlayerService may have been changed by your ROM, you may can't replace it with the AOSP version.
Prerequisites
Pixel running Android 9.0.0 build number PQ1A.181205.002.A1 or PQ1A.190105.004.
Bootloader unlocked.
adb and fastboot tools and drivers are working for your device.
Note & Disclaimer
These steps will change files in your system, your Pixel should run the exact same version of system. Pushing files to different versions of system may cause unknown problems.
Please check carefully before running each command, a mistaken operation may result in unable to boot up, or destroy your data, or even damage your phone.
If you are not sure about what these steps are doing, but still want to go ahead, please backup your phone firstly, you may not be able to recover your phone to its original state.
I have only tested on Pixel 1 with build number PQ1A.181205.002.A1 and PQ1A.190105.004, for other phones or versions, you should build and test on your own.
Basic Steps
Flash the same version of factory image for your phone.
Download the prebuilt files from https://github.com/sbjbs/android-wfd-patch
Add this line into "build.prop", without it, we will not be able to enable WiFi-Display:
Code:
persist.debug.wfd.enable=1
Replace some files in system:
Code:
system/lib/libaudioflinger.so
system/lib64/libaudioflinger.so
system/lib/libserviceutility.so
system/lib64/libserviceutility.so
system/lib/libmedia.so
system/lib64/libmedia.so
system/lib/libwilhelm.so
system/lib64/libwilhelm.so
system/lib/libandroid_runtime.so
system/lib64/libandroid_runtime.so
system/lib/libstagefright.so
system/lib64/libstagefright.so
system/lib/libstagefright_wfd.so
system/lib64/libstagefright_wfd.so
system/lib/libmediaplayerservice.so
If you have magisk installed, you can refer to Phoenix Wright's post:
Phoenix Wright said:
using "setprop" to set that property once is enough, no need to touch build.prop; given it's a "persist" property it'll be permanent.
using magisk to overlay them on /system
Click to expand...
Click to collapse
Some extra steps that you may need
Remove dm-verity metadata of system.img
The dm-verity can prevent us from changing the system, and what's more it has a forward-error-correction(FEC) feature, which can detect and correct some corrupted data.
I spend a lot of time on attempting to change the build.prop but fail again and again, it just always correct the file, and I can't enable wifi-display.
I don't know how to disable it. Since the error-correcting info should be stored in the dm-verity metadata, I just removed the dm-verity metadata from the stock system.img, and flash the system.img.
I will list the steps to remove dm-verity metadata, but if you can disable dm-verity entirely, that should work too.
For phones that have a vbmeta partition (like Pixel 2), seems you can flash an special vbmeta.img to disable AVB. You can build the empty vbmeta image by this command, but I don't have a device to test if it works:
Code:
avbtool make_vbmeta_image --flag 2 --padding_size 4096 --output vbmeta.img
For Pixel 1, we need to remove dm-verity metadata that attached to system.img, first convert the sparse system.img to an ext4 image:
Code:
simg2img system.img system.ext4.img
read the block count to calculate the system size:
Code:
od -j 1028 -An -N4 -tu system.ext4.img
for Pixel 1, it should be 516099. You also can read it by a Hex Editor, e.g., WinHEX in Windows, read 4 bytes starting from 1028 bytes, as a little-endian hex value.
so the real system partition size is 516099 * 4096 = 2113941504 bytes.
we need to set the data to zero after that position. It's important to do this, since we need to overwrite the metadata in that area, rather than just truncate the size of system.img.
next get the ext4 image size, for Pixel PQ1A.181205.002.A1, it should be 2147483648.
so we need to write 2147483648 - 2113941504 = 33542144 bytes：
Code:
dd if=/dev/zero of=system.ext4.img seek=2113941504 count=33542144 oflag=seek_bytes iflag=count_bytes
we also can use some other tools to do this, e.g., WinHEX in Windows. Open the file in in-place mode, and jump to 2113941504, and select it as the begin, and jump to the end, and select as the end, and fill the selection with all zero.
after that, flash the changed system.ext4.img to Pixel:
Code:
fastboot flash system system.ext4.img
Test that you can boot up normally. If not, check what's wrong and fix it.
Temporary boot up by TWRP image
We don't have to install TWRP, but just use it to temporary boot up, so that we can mount the system partition for writing. If you have TWRP installed, you can just boot to TWRP.
Download TWRP image for pixel, just need the twrp.img, we won't install the zip file.
boot your device to bootloader:
Code:
adb reboot bootloader
and boot by the twrp.img
Code:
fastboot boot twrp.img
after TWRP booted up, just leave it there, no need to unlock or input password, we will change the system by adb.
Mount system partition for writing.
In the current version of TWRP for Pixel (twrp-3.2.3-1-sailfish.img), its fstab has an entry for system partition, we can directly mount it.
Code:
adb shell mount /system
run mount to check if successfully mounted:
Code:
adb shell mount
you should see an entry like this:
Code:
/dev/block/sda34 on /system type ext4 (rw,seclabel,relatime)
If not, you should stop now, and check the above steps.
after mount, we can use adb to push files into system.

Hey guy,
You helped me a lot to understand why it was not working with Pie. I tried several custom ROMs + the official Pie and it was not working.
There is Wireless display option in quick settings but it' doesn't find my Microsoft Wireless Display Adaptor also.
I so downgrade to Oreo. With Oreo it works without any issue. (there is an option "allow Wireless display" to tick and then your miracast dongle will appear).
You did a great job to make it working on Pie. Congratulations. I will anyway stay on Oreo. I think google will change that (many people already complained i guess).
Jean Michel

jean_michmich said:
Hey guy,
You helped me a lot to understand why it was not working with Pie. I tried several custom ROMs + the official Pie and it was not working.
There is Wireless display option in quick settings but it' doesn't find my Microsoft Wireless Display Adaptor also.
I so downgrade to Oreo. With Oreo it works without any issue. (there is an option "allow Wireless display" to tick and then your miracast dongle will appear).
You did a great job to make it working on Pie. Congratulations. I will anyway stay on Oreo. I think google will change that (many people already complained i guess).
Jean Michel
Click to expand...
Click to collapse
Thanks for your reply!
I have tested on Pie on my Pixel, I often play online games while cast is on, and didn't meet any problems last week.
I also hope that Google will support Miracast again in the future, but it seems unlikely in the near future.
Google has abandoned it since Android 6 (source: Wikipedia), and now they're deleting unused source code related to wifi-display.
I'm more worried about that there will be more build errors and potential issues when we try to enable it for future Android versions.

sbjbs said:
Thanks for your reply!
I have tested on Pie on my Pixel, I often play online games while cast is on, and didn't meet any problems last week.
I also hope that Google will support Miracast again in the future, but it seems unlikely in the near future.
Google has abandoned it since Android 6 (source: Wikipedia), and now they're deleting unused source code related to wifi-display.
I'm more worried about that there will be more build errors and potential issues when we try to enable it for future Android versions.
Click to expand...
Click to collapse
OK it's getting more clear. You are right. Wikipedia says : "but support was dropped with Android 6.0 Marshmallow in 2015 in favor of Google's own proprietary Google Cast protocol.[15] Some manufacturers of Android devices step in and support Miracast through their software"
I'm not an "official android ROM" user.
I always use Pixel Dust custom ROM. For this custom ROM, Miracast was supported for Oreo but not for Pie (not yet).

jean_michmich said:
OK it's getting more clear. You are right. Wikipedia says : "but support was dropped with Android 6.0 Marshmallow in 2015 in favor of Google's own proprietary Google Cast protocol.[15] Some manufacturers of Android devices step in and support Miracast through their software"
I'm not an "official android ROM" user.
I always use Pixel Dust custom ROM. For this custom ROM, Miracast was supported for Oreo but not for Pie (not yet).
Click to expand...
Click to collapse
I used to be a ‘latest official ROM’ user
For custom ROMs, since they may have changed the framework, we can't replace files with AOSP version, but as long as they're open source, we can try to contribute to it.
Adding Miracast support in Android is not difficult, and many manufactures have their own support.
I hope your custom ROM will support Miracast for Pie in the near future.

Tested on Pixel 2 XL and working (for what it's worth, using "setprop" to set that property once is enough, no need to touch build.prop; given it's a "persist" property it'll be permanent). I built the .so files on my local aosp tree and I'm using magisk to overlay them on /system.

Hi @sbjbs
If I understand you right then you have patched the AOSP codebase. Would you mind sharing the repositories/commits on your GitHub? That would be highly appreciated. :good:
Regards
spezi
Sent from my Pixel 3 using XDA Labs

spezi77 said:
Hi @sbjbs
If I understand you right then you have patched the AOSP codebase. Would you mind sharing the repositories/commits on your GitHub? That would be highly appreciated. :good:
Regards
spezi
Sent from my Pixel 3 using XDA Labs
Click to expand...
Click to collapse
There's a link in the OP: https://github.com/sbjbs/android-wfd-patch/tree/master/patches/android-9.0.0

Phoenix Wright said:
Tested on Pixel 2 XL and working (for what it's worth, using "setprop" to set that property once is enough, no need to touch build.prop; given it's a "persist" property it'll be permanent). I built the .so files on my local aosp tree and I'm using magisk to overlay them on /system.
Click to expand...
Click to collapse
Great to hear that!
You method is simpler and more elegant, that's awesome!

Phoenix Wright said:
Tested on Pixel 2 XL and working (for what it's worth, using "setprop" to set that property once is enough, no need to touch build.prop; given it's a "persist" property it'll be permanent). I built the .so files on my local aosp tree and I'm using magisk to overlay them on /system.
Click to expand...
Click to collapse
Can you elaborate how you did use "magisk to overlay them on /system"?
I pushed them using adb as mentioned on github but it is stuck at Google splash screen. I've taimen BTW and am on Pixeldust ROM. It booted while writing this post but the screen was not responding to touch.
Nitin

nitin.chobhe said:
Can you elaborate how you did use "magisk to overlay them on /system"?
I pushed them using adb as mentioned on github but it is stuck at Google splash screen. I've taimen BTW and am on Pixeldust ROM. It booted while writing this post but the screen was not responding to touch.
Nitin
Click to expand...
Click to collapse
I made a module with the .so files I compiled: https://workupload.com/file/pd4EUBdw
Note that I can't vouch for this to work on your ROM, it works on taimen on stock 9.0 with January security patches though.

nitin.chobhe said:
Can you elaborate how you did use "magisk to overlay them on /system"?
I pushed them using adb as mentioned on github but it is stuck at Google splash screen. I've taimen BTW and am on Pixeldust ROM. It booted while writing this post but the screen was not responding to touch.
Nitin
Click to expand...
Click to collapse
Did you build the so files for your ROM from source? the patch has changed the interface of IMediaPlayerService, if anything else in your ROM is using IMediaPlayerService.h, you'd better rebuild and replace them.
that's why I uploaded the libwilhelm.so and libandroid_runtime.so, even though I didn't change the source code of them.

Phoenix Wright said:
I made a module with the .so files I compiled: https://workupload.com/file/pd4EUBdw
Note that I can't vouch for this to work on your ROM, it works on taimen on stock 9.0 with January security patches though.
Click to expand...
Click to collapse
Thanks!
sbjbs said:
Did you build the so files for your ROM from source? the patch has changed the interface of IMediaPlayerService, if anything else in your ROM is using IMediaPlayerService.h, you'd better rebuild and replace them.
that's why I uploaded the libwilhelm.so and libandroid_runtime.so, even though I didn't change the source code of them.
Click to expand...
Click to collapse
I tried building with my ROM but I got build errors related to OMX.h, I need to find a solution for them. Thanks anyways!
Nitin

Someone tries on Pixel 3? Thanks

It works perfectly ! I used the prebuilt files on the march build.
Do you know if we can force the 16/9 ratio ?
Thanks
edit : I will try with second screens !

this works a treat on my Pixel 3 XL (Stock Pie) just overlayed the files from Phoenix Wright using magisk and it works now....sweet thanks, now just need to figure out how to fool sky sports app into letting me cast.....

marshyrob said:
this works a treat on my Pixel 3 XL (Stock Pie) just overlayed the files from Phoenix Wright using magisk and it works now....sweet thanks, now just need to figure out how to fool sky sports app into letting me cast.....
Click to expand...
Click to collapse
Can you explain more how did you do?
Did you just flash the zip from Phoenix Wright in Magisk?

EMJI79 said:
Can you explain more how did you do?
Did you just flash the zip from Phoenix Wright in Magisk?
Click to expand...
Click to collapse
Yes just copied the .zip file from Phoenix Wright's post to my device then used the module install option in Magisk like if you are installing a module found in Magisk (use the plus sign to add your own .zip file instead and browse to the file you just saved) then reboot. Then i went to the cast option in settings - connected devices - connection preferences, there i could tick in the top right corner under the 3 dots "enable wireless display" and it showed my Panasonic TV, chose connected and boom it connected. Needed to enable the mirroring option on my Panasonic but this is a TV setting nothing to do with the phone, you might need to do a similar step based on your TV as they need to be able to see each other.

marshyrob said:
Yes just copied the .zip file from Phoenix Wright's post to my device then used the module install option in Magisk like if you are installing a module found in Magisk (use the plus sign to add your own .zip file instead and browse to the file you just saved) then reboot. Then i went to the cast option in settings - connected devices - connection preferences, there i could tick in the top right corner under the 3 dots "enable wireless display" and it showed my Panasonic TV, chose connected and boom it connected. Needed to enable the mirroring option on my Panasonic but this is a TV setting nothing to do with the phone, you might need to do a similar step based on your TV as they need to be able to see each other.
Click to expand...
Click to collapse
It did work today with my Sony television.
Thanks!

OMG!!! You made my week. Few hiccups tho....
Can anyone else confirm that Hulu and HBO go and Amazon prime . YouTube works.
Hulu and amazon I can log on but when it plays all you get is audio. Haven't tried Netflix I don't sub them.
HBO go as soon as I try to play a video it says this video cannot be played. If I disable the mirror it plays perfectly. Same thing with Hulu and prime. Disable the mirror an it works perfectly on my phone.

[GUIDE]Enable VoLTE for unsupported carriers

Hi Let me introduce tutorial, how to enable VoLTE/VoWiFi for some other carriers. All credits goes to @Airpil for his great work with enabling diag port for Pixel 2 phones and to @topjohnwu for his original Magisk project.
UPDATE:
Here is another way by @Vortuks , how to get things working.
Code:
https://github.com/stanislawrogasik/Pixel2XL-VoLTE-VoWiFi
ANOTHER UPDATE:
On Android 11 you can use module VoLTE_enabler_pixel_2_v1_1.zip, but you will myabe need to use SeLinux permissive module too.
BIG UPDATE:
use only on PIE
for android 10 use solution with PDC tool
I created new magisk module with everything needed for enabling VoLTE. Just install VoLTE_enabler_pixel_2_v1_1.zip and enjoy.
this will work only, if there is proper *.mbn for your provider
sometimes is needed to remove/add module after updating monthly updates
sometimes is needed to toggle off/on enhanced 4g LTE mode and go to airplane mode and back
Prerequizites:
your carrier have to support this feature
and you have to enable this feature on operator's side
PC with windows
you must have some luck
Prepare your PC:
google for QPST_2.7.474 and install it
install provided drivers (if they willn't work, google for better)
from provided nokia_mbn_files.zip find the right mcfg_sw.mbn for your carrier, if there isn't any mbn for your carrier, you can try another one, but without warranty
Prepare your phone:
backup everything, what you can especially EFS partition - just for sure
root your phone with provided Magisk.zip
boot up your phone
In Magisk Manager app find and install VoEnablermodule, restart phone
there will be new settings under Settings-Network & internet-Mobile network-Advanced
connect phone to PC and set to charge only mod
in terminal emulator run this commands (this will enable diagnostic port on phone):
Code:
su
setenforce 0
setprop sys.usb.configfs 1 && setprop sys.usb.config diag,serial_cdev,rmnet_gsi,adb
Next steps:
find PDC tool from installed QPST and open
select device from drop-down menu, if it is empty, you will have to reinstall/choose another driver
click load button and find prepared mcfg_sw.mbn file
now right-click on new loaded profile and select SetSelectedConfig - Sub0
and now button Activate
activate provided VoEnabler module via MagiskManager
restart device
and now, if you are lucky one, your VoLTE is working :victory:
Final steps:
if everything is working, you should reinstall original Magisk from twrp
Troubleshhoting:
99,9% of all problems comes with wrong driver
open windows device manager and try to choose another driver for HW like:
Qualcomm HS-USB Modem 9091
Qualcomm HS-USB Diagnostics 9091
Qualcomm HS-USB WWAN Adapter 9091
Is it working?
dial *#*#4636#*#*
Phone information-3dots-IMS service status
If IMS Registration: Registered and Voice over LTE: Available you won
after update with factory images you will have to re-do this steps
Confirmed carriers:
Czech T-mobile
VoLTE - yes
VoWiFi - no
Poland Orange(confirmed by @saperkus)
VoLTE - yes
VoWiFi - yes
Poland Play(confirmed by @saperkus)
VoLTE - yes
VoWiFi - yes
Telenor Bulgariawith Telenor Danemark mbn (confirmed by @pavel5044)
VoLTE - yes
VoWiFi - no
T-Mobile Hungary (Telekom)(confirmed by @hunfatal)
VoLTE - yes
VoWiFi - no
Downloads:
Code:
Drivers:
[url]https://mega.nz/#!oMEHTIbA!0g7ahr8r81Q3ue8LpEy-sfd7FTLEEQlGRi2CJfG_Kq0[/url]

somin.n said:
Hi Let me introduce tutorial, how to enable VoLTE/VoWiFi for some other carriers. All credits goes to @Airpil for his great work with enabling diag port for Pixel 2 phones and to @topjohnwu for his original Magisk project.
Prerequizites:
your carrier have to support this feature
and you have to enable this feature on operator's side
PC with windows
you must have some luck
Prepare your PC:
google for QPST_2.7.474 and install it
install provided drivers (if they willn't work, google for better)
from provided nokia_mbn_files.zip find the right mcfg_sw.mbn for your carrier, if there isn't any mbn for your carrier, you can try another one, but without warranty
Prepare your phone:
backup everything, what you can especially EFS partition - just for sure
root your phone with provided Magisk.zip
boot up your phone
In Magisk Manager app find and install VoEnabler module, restart phone
there will be new settings under Settings-Network & internet-Mobile network-Advanced
connect phone to PC and set to charge only mod
in terminal emulator run this commands (this will enable diagnostic port on phone):
Code:
setenforce 0
setprop sys.usb.configfs 1 && setprop sys.usb.config diag,serial_cdev,rmnet_gsi,adb
Next steps:
find PDC tool from installed QPST and open
select device from drop-down menu, if it is empty, you will have to reinstall/choose another driver
click load button and find prepared mcfg_sw.mbn file
now right-click on new loaded profile and select SetSelectedConfig - Sub0
and now button Activate
and now, if you are lucky one, your VoLTE is working :victory:
Final steps:
if everything is working, you should reinstall original Magisk from twrp
Troubleshhoting:
99,9% of all problems comes with wrong driver
open windows device manager and try to choose another driver for HW like:
Qualcomm HS-USB Modem 9091
Qualcomm HS-USB Diagnostics 9091
Qualcomm HS-USB WWAN Adapter 9091
Is it working?
dial *#*#4636#*#*
Phone information-3dots-IMS service status
If IMS Registration: Registered and Voice over LTE: Available you won
Downloads:
Code:
Drivers:
[url]https://mega.nz/#!oMEHTIbA!0g7ahr8r81Q3ue8LpEy-sfd7FTLEEQlGRi2CJfG_Kq0[/url]
Click to expand...
Click to collapse
Hi I am stuck at the terminal emulator step.
when i type in "setenforce 0" the terminal says "couldn't set enforcing status to '0' invalid argument"
i tried googling and tried some stuff but no luck.
Note: Is there something to do with the kernel coz i am on Sultan Kernel and not sure if its build for only enforcing or only permissive.
please get back to me ASAP.
thankyou

royroyal said:
Hi I am stuck at the terminal emulator step.
when i type in "setenforce 0" the terminal says "couldn't set enforcing status to '0' invalid argument"
i tried googling and tried some stuff but no luck.
Note: Is there something to do with the kernel coz i am on Sultan Kernel and not sure if its build for only enforcing or only permissive.
please get back to me ASAP.
thankyou
Click to expand...
Click to collapse
Hi, yeah, my mistake :angel: You have to use "su" command first to allow root access. Full command is:
Code:
su
setenforce 0
setprop sys.usb.configfs 1 && setprop sys.usb.config diag,serial_cdev,rmnet_gsi,adb
And please, don't quote full first post

somin.n said:
Hi, yeah, my mistake :angel: You have to use "su" command first to allow root access. Full command is:
And please, don't quote full first post
Click to expand...
Click to collapse
Yes sorry for replying over the OP.
Yes i knew already to use "su" inorder to grant supersu access, but this didnt work for me and i am not able to proceed. Husssshh..

royroyal said:
Yes sorry for replying over the OP.
Yes i knew already to use "su" inorder to grant supersu access, but this didnt work for me and i am not able to proceed. Husssshh..
Click to expand...
Click to collapse
Hmm, should work? Try to write it, not copy... Try the other command without changing enfonforcing, it is maybe not necessary.

somin.n said:
Hmm, should work? Try to write it, not copy... Try the other command without changing enfonforcing, it is maybe not necessary.
Click to expand...
Click to collapse
Tried to write as well as copying, also tried without the 1st command but no luck.. and as no one has tried this yet aslo not able to know if this is happening with my device only.

royroyal said:
Tried to write as well as copying, also tried without the 1st command but no luck.. and as no one has tried this yet aslo not able to know if this is happening with my device only.
Click to expand...
Click to collapse
Interesting try to restart your phone, open windows device manager, connect phone (now should be detected some new hw), open terminal and write commands and look, if some new hw was detected or if you have some new unknown devices in device manager. You should also look to Airpil's thread for some help.
Code:
[url]https://forum.xda-developers.com/pixel-2-xl/how-to/guide-qxdm-port-activation-pixel-2-xl-t3884967[/url]

somin.n said:
Interesting try to restart your phone, open windows device manager, connect phone (now should be detected some new hw), open terminal and write commands and look, if some new hw was detected or if you have some new unknown devices in device manager. You should also look to Airpil's thread for some help.
Click to expand...
Click to collapse
Will try this and update here

Successfully enable volte on my pixel2,Thanks!

Please provide carrier details in your post guys! With that being said, has anyone got it to work on Straight Talk (Verizon or ATT sim?)

Enable VoLTE for Vodafone in India
Vodafone in India has not provisioned the Pixel 2 till yet for VoLTE despite many people getting after them. A lot of noise was generated by users when Google pointed out that they had done what was required in the Android Pie updates.
Many thanks for this guide as it has helped me to enable VoLTE on my Pixel 2. On checking with *#*#4636#*#* it shows that VoLTE is now provisioned for voice. I now need to connect to any other phone where VoLTE is working and see if it indeed connects using VoLTE.
The only problem I had was in opening the port before using QPST. I had to type in the commands a second time in the terminal and then the port opened allowing me to proceed.

almightysiman said:
Successfully enable volte on my pixel2,Thanks!
Click to expand...
Click to collapse
Hi,
did u do it over the stock rom/kernel or on any custom kernel.
and can u post every step that u did to get it done.
currently i m on pure stock 9.0 pie with locked bootloader on february security patch.
this is my previous comment over the thread..
Hi I am stuck at the terminal emulator step.
when i type in "setenforce 0" the terminal says "couldn't set enforcing status to '0' invalid argument"
i tried googling and tried some stuff but no luck.
Note: Is there something to do with the kernel coz i am on Sultan Kernel and not sure if its build for only enforcing or only permissive.

royroyal said:
Hi,
did u do it over the stock rom/kernel or on any custom kernel.
and can u post every step that u did to get it done.
currently i m on pure stock 9.0 pie with locked bootloader on february security patch.
this is my previous comment over the thread..
Hi I am stuck at the terminal emulator step.
when i type in "setenforce 0" the terminal says "couldn't set enforcing status to '0' invalid argument"
i tried googling and tried some stuff but no luck.
Note: Is there something to do with the kernel coz i am on Sultan Kernel and not sure if its build for only enforcing or only permissive.
Click to expand...
Click to collapse
I am on du rom.you should type su before setenforce 0

Hadookie said:
Please provide carrier details in your post guys! With that being said, has anyone got it to work on Straight Talk (Verizon or ATT sim?)
Click to expand...
Click to collapse
I'm back overseas now, but while I was home for the holidays I used a Straight Talk ATT sim and had no problems using the MagiskHide Props module to manually add the lines from this module:
https://forum.xda-developers.com/apps/magisk/module-v4-volte-enabler-t3649613
It was somewhat inconsistent though. Seemed to only work with certain people I called. Also, I use Google Voice when I'm home, so that may account for the inconsistency.
I haven't tried the method outlined by the OP, though. I've had a solid setup for months now and I'm a bit hesitant to try anything that might kink it up.
Edit:
Now that I think about it, I never checked the IMS Registration to be sure, so I can't be sure if it was actually working, but it would show the "HD" calling icon on the dialer screen when connected, so I just assumed it was working.

Thank you for sharing this guide.
I can confirm, that VoLTE and VoWiFi is working fine in Orange Poland and PLAY (Poland). In case of PLAY, both services are disabled by default. You have to contact with service provider and ask them to enable WiFi Calling. By enabling it, VoLTE will be also enabled.

saperkus said:
Thank you for sharing this guide.
I can confirm, that VoLTE is working in Orange Poland and VoLTE and VoWiFi is working in PLAY (Poland). In case of PLAY, both services are disabled by default. You have to contact with service provider and ask them to enable WiFi Calling. By enabling it, VoLTE will be also enabled.
Click to expand...
Click to collapse
Any chance to get WiFi calling working on Orange PL?
And will this work at all on OG Pixel?

bige93 said:
Any chance to get WiFi calling working on Orange PL?
Click to expand...
Click to collapse
It seems, that I haven't been patient enough in case of Orange PL... I have redone the tests and was able to make VoWiFi to work. There's a need to reboot the device after swapping SIM cards. After reboot, VoWiFi works fine.
bige93 said:
And will this work at all on OG Pixel?
Click to expand...
Click to collapse
You're free to check it. I've checked on Nexus 5X and it didn't work at all.

saperkus said:
It seems, that I haven't been patient enough in case of Orange PL... I have redone the tests and was able to make VoWiFi to work. There's a need to reboot the device after swapping SIM cards. After reboot, VoWiFi works fine.
You're free to check it. I've checked on Nexus 5X and it didn't work at all.
Click to expand...
Click to collapse
Do I have to use some special ("diag") version of the Magisk as it says it the 1st post? Can't find 'magisk diag' for Sailfish.

bige93 said:
Do I have to use some special ("diag") version of the Magisk as it says it the 1st post? Can't find 'magisk diag' for Sailfish.
Click to expand...
Click to collapse
This is a modded version of Magisk, which gives an ability to enable diagnostic port (normally it can't be enabled). It was prepared for Pixel 2 XL, but it also works fine with Pixel 2. I can't tell, if you need to use this version or not. Install standard Magisk version and check if you can enable this port using provided commands. If not, then it's up to you to decide, if you want to check modded version of Magisk or not.

Has anybody tried to install the modified Magisk on android Q Beta yet? I am getting error 1, it doesn't install