Related
hi all, anyone use microsoft mapcruncher to calibrate scanned maps? It seems that all information about calibration point are saved in a file .yum but I don't understand how the x and y point are saved. I would like to convert this file in a "standard" format like .map or .gmi, someone know if exists a tool to do that?
thanks
more info:
in the yum file this is the render area:
<RenderRegion>
<LatLon lat="1" lon="0" />
<LatLon lat="0" lon="0" />
<LatLon lat="0" lon="0.707142857142857" />
<LatLon lat="1" lon="0.707142857142857" />
</RenderRegion>
the value 0.707142857142857 is the height/width.
I think that the calibration point are declared like this:
<PositionAssociation pinId="1" associationName="p02">
<SourcePosition>
<LatLonZoom zoom="11">
<LatLon lat="0.30902099609375" lon="0.069183349609375" />
</LatLonZoom>
</SourcePosition>
<GlobalPosition>
<LatLonZoom zoom="16">
<LatLon lat="46.0798842712826" lon="10.1245450973511" />
</LatLonZoom>
</GlobalPosition>
</PositionAssociation>
the point seem the 0.30902099609375% and the 0.069183349609375% but this value 0.707142857142857?
thanks
Many users of Sabsa Prime posted they cannot update Facebook.
and.. maybe other apps also not available for update comes in. (Youtube, SuperSu, ... etc)
I have edited packages.xml on /data/local but some app still has problem.
(Problems with Google Apps might be solved with editing packages.xml and replacing apks. see EDIT 3 bottom)
You need uninstall those first and reinstall from market, will be fine :fingers-crossed:
How to Uninstall Apps on /system/app
1.
Install
Titanium Backup
com.keramidas.TitaniumBackup
OR
ROM Toolbox Lite
com.jrummy.liberty.toolbox
2.
Run it and GRANT it a Superuser access.
3.
Go for the Apps list.
on Titanium Backup
Tap Backup/Restore
OR
on ROM Toolbox Lite
Tap App Manager
then Tap All Apps
4.
App which its names written Red are on /system/app on apps list.
5.
Find app annoys you from being updated on market.
6.
Tap or long press its name then menu comes up.
7.
Press Uninstall
if you can't find, swipe left or right - it might be there.
8.
Wait until uninstall finishes...
9.
Reboot Your Phone NOW.
It's Done.
There's a one more step if you want to use them is:
Install them from market again.
Now, you can update apps.
The problem CANNOT be solved UNLESS the Developer puts correct apks(from market, UNTOUCHED) in their ROMs.
if not, and you install newer ROMs or somewhat from them, It'll annoy you again.
EDIT 1---------------------------------------------------------------------------------------------
for someone having poor(? disconnects too often) data reception,
please check this thread about build.prop Fast Dormancy:
t t p : / / forum.xda-developers.com/showthread.php?t=1684604
EDIT 2---------------------------------------------------------------------Sept. 21th, 2012
>> Oops, I forgot to tell reboot your phone. also, wrote about steps for titanium
EDIT 3------------------------------------------------------------------------Oct. 1st, 2012
>> Found something weired with Google apps by myself. so I edited again.
due to some reason you can't update or Install some Google apps like Google Play Service, etc.
1.
extract apks from gapps package 20120429
if you don't have it, Google it.
2.
go to recovery.
3.
mount /system/as writable.
4.
replace corresponding apks in system/app/
(Incldue MarketUpdater.apk: if you want to keep Play Store updated. and.. included Play Store App from gapps 20120429 IS OUTDATED.
DO NOT REPLACE GoogleBackupTransport.apk: this shares signature with the ROM's so do not replace it otherwise it will be NOT AVAILABLE on your phone.)
if you extracted the gapps package in folder gapps,
Shift-Click upper folder on tree view.
and open command window here
in command-prompt:
adb push /gapps /system/apps
Replacing apks done however you have more steps to do for replaced apks start working.
(optional)
you can unmount /system/ because you have finished replacing apks.
5.
mount /data/as writable.
6.
pull out packages.xml
in command-prompt:
adb pull /data/system/packages.xml
7.
open packages.xml in text editor
(IMPORTANT: DO NOT SAVE files on windows notepad or something else displays all of lines as single line because lack of UNIX support)
8.
Delete shared-user element has name=com.google.uid.shared.
then save.
you have to delete whole element this might look like:
<shared-user name="com.google.uid.shared" userId="10000">
<sigs count="1">
<cert index="1" />
</sigs>
<perms>
<item name="com.google.android.googleapps.permission.GOOGLE_AUTH.youtube" />
<item name="android.permission.INTERNET" />
<item name="com.google.android.providers.gmail.permission.WRITE_GMAIL" />
<item name="android.permission.WRITE_SYNC_SETTINGS" />
<item name="android.permission.BROADCAST_STICKY" />
<item name="com.google.android.googleapps.permission.ACCESS_GOOGLE_PASSWORD" />
<item name="com.google.android.googleapps.permission.GOOGLE_AUTH" />
<item name="android.permission.VIBRATE" />
<item name="android.permission.GET_ACCOUNTS" />
<item name="android.permission.MASTER_CLEAR" />
<item name="android.permission.SUBSCRIBED_FEEDS_WRITE" />
<item name="android.permission.ACCESS_DOWNLOAD_MANAGER" />
<item name="com.google.android.providers.gmail.permission.READ_GMAIL" />
<item name="android.permission.WRITE_CONTACTS" />
<item name="android.permission.READ_PHONE_STATE" />
<item name="com.android.providers.im.permission.WRITE_ONLY" />
<item name="android.permission.RECEIVE_BOOT_COMPLETED" />
<item name="com.google.android.gtalkservice.permission.SEND_GTALK_DATA_MESSAGE" />
<item name="android.permission.READ_CONTACTS" />
<item name="android.permission.READ_SYNC_SETTINGS" />
<item name="com.google.android.googleapps.permission.GOOGLE_AUTH.ALL_SERVICES" />
<item name="android.permission.WRITE_SETTINGS" />
<item name="android.permission.SUBSCRIBED_FEEDS_READ" />
<item name="android.permission.ACCESS_NETWORK_STATE" />
<item name="android.permission.WAKE_LOCK" />
<item name="com.android.providers.im.permission.READ_ONLY" />
<item name="android.permission.WRITE_SECURE_SETTINGS" />
<item name="com.google.android.googleapps.permission.GOOGLE_AUTH.YouTubeUser" />
<item name="android.permission.CALL_PHONE" />
<item name="com.google.android.gtalkservice.permission.GTALK_SERVICE" />
<item name="com.android.vending.INTENT_VENDING_ONLY" />
<item name="com.google.android.googleapps.permission.GOOGLE_MAIL_SWITCH" />
<item name="com.google.android.googleapps.permission.GOOGLE_AUTH.mail" />
</perms>
</shared-user>
Click to expand...
Click to collapse
9.
put packages.xml back to your phone.
in command-prompt:
adb push packages.xml /data/system/packages.xml
10.
set its permission rw-rw-r-- as it was.
in adb shell:
# chmod 664 /data/system/packages.xml
# chwon system.system /data/system/packages.xml
(optional)
to check permission has set:
# ls -e /data/system/packages.xml (if -rw-rw-r-- is okay first char is for a directory)
11.
Reboot Your Phone NOW.
It's Done.
Fails to install from Play store
AtomosVE said:
Many users of Sabsa Prime posted they cannot update Facebook.
and.. maybe other apps also not available for update comes in. (Youtube, SuperSu, ... etc)
I have edited packages.xml on /data/local but some app still has problem.
You need uninstall those first and reinstall from market, will be fine :fingers-crossed:
How to Uninstall Apps on /system/app
1.
Install ROM Toolbox Lite
com.jrummy.liberty.toolbox
2.
Run it and GRANT it a Superuser access.
3.
Tap App Manager
4.
Tap All Apps
Like Titanium, App which its names written Red are on /system/app on apps list.
5.
find app annoys you from being updated on market.
6.
Tap or long press its name then menu comes up.
7.
press Uninstall
8.
wait until uninstall finishes...
It's Done.
There's a one more step if you want to use them:
Install them from market again.
Now, you can update apps.
The problem CANNOT be solved UNLESS the Developer puts correct apks(from market, UNTOUCHED) in their ROMs.
if not, and you install newer ROMs or somewhat from them, It'll annoy you again.
Click to expand...
Click to collapse
After uninstalling the Facebook app, it fails to install again from market. It says invalid Update!! Please help.
mani4all said:
After uninstalling the Facebook app, it fails to install again from market. It says invalid Update!! Please help.
Click to expand...
Click to collapse
I believe you need to re-start your phone after Step 8. Then re-install from Market.
Oops, I forgot something..
mani4all said:
After uninstalling the Facebook app, it fails to install again from market. It says invalid Update!! Please help.
Click to expand...
Click to collapse
Oh, Forgot to tell rebooting your phone after uninstalled app. Hope you enjoy Facebook
Yowhy said:
I believe you need to re-start your phone after Step 8. Then re-install from Market.
Click to expand...
Click to collapse
Thanks for telling them reboot is need. I was forgot but Now, Corrected
If anyone has tried to use an OTG to back up with Titanium Backup you know that if you select a folder on your OTG drive Titanium Backup will say it's not writable even if you can write to it using other methods.
I was looking into this last night because I wanted to back up everything to my 64GB sd card using the meenova OTG adapter (http://www.meenova.com)
Anyway to be able to have TiBU write to it all you have to do is add a lne in an xml file.
YOU MUST BE ROOTED:
Go to /system/etc/permissions
open up platform.xml
look for the line
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_rw" />
and add the line
Code:
<group gid="media_rw" />
So now it will look like this:
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
Save the file, reboot and then fire up TiBu and navigate to the folder on your OTG drive and it will now work and the message saying it's not writable will be gone.
Anyone tried this?
I'm always a bit wary of unaccredited websites that ask for my credit card details and address... Did not purchase... If there were a PayPal option, that'd be different.
Jade Eyed Wolf said:
I'm always a bit wary of unaccredited websites that ask for my credit card details and address... Did not purchase... If there were a PayPal option, that'd be different.
Click to expand...
Click to collapse
You don't have to buy it. This process will work with any otg. But they are reputable. They had a huge kickstarter campaign and was reported on by a few of the sites (that's how I first found out about it)
Sent from my Nexus 7 using Tapatalk 4
GoClifGo05 said:
Anyone tried this?
Click to expand...
Click to collapse
Yes, I did and it works perfectly. But hey if you don't feel like I'm creditable and need a 2nd opinion then be my guest.. I don't really have the reputation of posting nonsense
Sent from my Nexus 7 using Tapatalk 4
I'm not calling you out at all! Lol don't get defensive. I just got my x today, DE and just reading around. Please don't take offense.
Sent from my DE Moto X
GoClifGo05 said:
I'm not calling you out at all! Lol don't get defensive. I just got my x today, DE and just reading around. Please don't take offense.
Sent from my DE Moto X
Click to expand...
Click to collapse
I'm not offended. I'm just saying.. If it didn't work I wouldn't have posted it. On Nexus devices using stick mount you don't need to do this but with the native otg with the moto x Titanium backup will say the folder on the otg drive is not writable.
Sent from my Nexus 7 using Tapatalk 4
Have an N7, got you. Well.... thanks for the tip.
Sent from my DE Moto X
Jade Eyed Wolf said:
I'm always a bit wary of unaccredited websites that ask for my credit card details and address... Did not purchase... If there were a PayPal option, that'd be different.
Click to expand...
Click to collapse
Wouldn't take my money. Hitting add to cart didn't do nothing.
Sent from my XT897 using XDA Premium 4 mobile app
graffixnyc said:
If anyone has tried to use an OTG to back up with Titanium Backup you know that if you select a folder on your OTG drive Titanium Backup will say it's not writable even if you can write to it using other methods.
I was looking into this last night because I wanted to back up everything to my 64GB sd card using the meenova OTG adapter (http://www.meenova.com)
Anyway to be able to have TiBU write to it all you have to do is add a lne in an xml file.
YOU MUST BE ROOTED:
Go to /system/etc/permissions
open up platform.xml
look for the line
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_rw" />
and add the line
Code:
<group gid="media_rw" />
So now it will look like this:
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
Save the file, reboot and then fire up TiBu and navigate to the folder on your OTG drive and it will now work and the message saying it's not writable will be gone.
Click to expand...
Click to collapse
If rooted and do like you described, then the apps like ES file manager can write file into SD card? Thanks.
Permission Denied
So I have root access and gave root permission to es file manager but whenever I try to save the file I'm unable to. What could be going on? What's going on?
Whenever I try this my whole system goes to hell. I end up having to reinstall system, not even deleting the line off the file and rebooting works.
On my Nexus 6 I have a Flash Drive connected via OTG, I am using StickMount to mount it in the file system, I can use it without any problem from TWRP, RootExplorer, Media Players, etc. The Flash drive is formatted using FAT32. When I try to configure Titanium Backup to use it as the destination folder for backup, I can get to the folder where the drive is mounted but the option "Use the current folder" is dimmed and I cannot press it to select the folder, please any help or guidance will be appreciated, thanks
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" > <group gid="sdcard_rw" /> <group gid="media_rw" /> </permission>
this line is unavailable but i found this one :
<permission name="android.permission.WRITE_MEDIA_STORAGE" > <group gid="sdcard_rw" /> <group gid="media_rw" /> </permission>
is it the same thing ???
falciatrice10 said:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" > <group gid="sdcard_rw" /> <group gid="media_rw" /> </permission>
this line is unavailable but i found this one :
<permission name="android.permission.WRITE_MEDIA_STORAGE" > <group gid="sdcard_rw" /> <group gid="media_rw" /> </permission>
is it the same thing ???
Click to expand...
Click to collapse
I have the same case. WRITE_MEDIA_STORAGE is in place as well as both permissions, and it doesn't solve the problem. Added WRITE_EXTERNAL_STORAGE tag, didn't help either.
I found a correct solution on ( SURPRIIISE! ) Titanium Backup Troubleshooting FAQ
31. External SD Card problems (This Folder is NOT Writeable)
Since Android 4.4 and above, the SDCard permissions have been changed on how it is granted to an application. A quick way to fix this is by using SDFix application.
There is an elegant way of giving TitaniumBackup write access to the external sdcard, without having to forfeit security (as in method 3 below). Since the time of Android 4.3, Google uses a very clean security-solution by giving apps that request write access to external SD, permission only to their own folder – not to the entire card! In order to get TitaniumBackup to work without compromising security, you can simply create a folder on the external sdcard,using the following folder-structure: /storage/extSdCard/Android/data/com.keramidas.TitaniumBackup/
If you already have existing backups, move them with a file-explorer from their current place to: /storage/extSdCard/Android/data/com.keramidas.TitaniumBackup/ Lastly, go to the preferences of TitaniumBackup, choose “Backup folder location” and choose the above specified folder.
Finish.
Click to expand...
Click to collapse
It works!
ShurV said:
I found a correct solution on ( SURPRIIISE! ) Titanium Backup Troubleshooting FAQ
It works!
Click to expand...
Click to collapse
Thank you! It works for me.:good:
Hi there!
I`m running an androidtv rom and i`d like to get the ui navigation sounds for Nexus player.
Thx so much.
well, I did some digging and found audio "ogg" files
"pano_blip_alt, pano_click, pano_error" under ui in media/audio folder under system...but when copied over to my rom nothing changes, so what file do I need to change to load them in my rom?
Thx!
Does anyone have any idea where to look?
You need to update audio_assets.xml in framework-res.apk to this:
Code:
<?xml version="1.0" encoding="utf-8"?>
<audio_assets version="1.0">
<group name="touch_sounds">
<asset id="FX_KEY_CLICK" file="pano_click.ogg" />
<asset id="FX_FOCUS_NAVIGATION_UP" file="pano_blip_alt.ogg" />
<asset id="FX_FOCUS_NAVIGATION_DOWN" file="pano_blip_alt.ogg" />
<asset id="FX_FOCUS_NAVIGATION_LEFT" file="pano_blip_alt.ogg" />
<asset id="FX_FOCUS_NAVIGATION_RIGHT" file="pano_blip_alt.ogg" />
<asset id="FX_KEYPRESS_STANDARD" file="KeypressStandard.ogg" />
<asset id="FX_KEYPRESS_SPACEBAR" file="KeypressSpacebar.ogg" />
<asset id="FX_KEYPRESS_DELETE" file="KeypressDelete.ogg" />
<asset id="FX_KEYPRESS_RETURN" file="KeypressReturn.ogg" />
<asset id="FX_KEYPRESS_INVALID" file="pano_error.ogg" />
</group>
</audio_assets>
Thx man....you are my savior.....love you!!!
update:
I used "Advanced_ApkTool_v4.2.0_By_BDFreak_2.2.1_2" to unpack...made the changes with notepad++, repacked and signed...flashed a zip file with twrp...but it get locked in bootloop...until i reflash the original file back in...glad i thought to make a backup...so now it`s back to normal...what gives?
When using apktool, you'll want to build with the -c option to carry over the signature from the original apk. Also, I'd use the -s option on decode so that it keeps the classes.dex intact. (No need to recompile those if you're just changing a resource.)
Thx so much...I don`t see where to enable those options....are they available on windows?
I just figured we`re talking about 2 different tools ...are you talking about this one?
Hi all.
First of all
I DO NOT PROVIDE ANY KIND OF SUPPORT. YOU ALONE RESPONSIBLE FOR ANY POSSIBLE ISSUES.
I wrote this post during my vacation. I know it could be quite handy, but unfortunately/thankfully my primary sources of money are completely aside from this findings.
I came to XDA from iOS jailbreak community and still believe that any findings have to be published if they allow to escape any kind of jail .
Sorry for any delays in my responses in PM and here, but i am really busy. In case somebody wants to share this info with other communities, feel free to do so.
Sorry for my EN
P.S.
all this small findings and adjustments would not be possible without @topjohnwu i have tried to rase a CR on github to enable a sub-function in Magisk for init.rc scripts injection through the existing magicg.rc but it was rejected. So any one who intrested in the same kind of projects please open an issue on Magis github page we really need *.rc injection as a part of Magisk module.
[/MENTION]
For the past couple of months I've been looking into finding the way to get an access to the Pixel 2 XL diag port.
As many of you know this feature is disabled by default on user builds. Thanks to @deeproot for his ROM. Because this is the only one userbuild ROM available right now with diag configuration. https://forum.xda-developers.com/pixel-2-xl/development/aosp-tamien-8-1-opengapps-t3727948
The only downside of this ROM is outdated version of the Android. To fix this unpleasant issue. I've took the init.taimen.diag.rc init script from the ROM and put it into the custom ROM. Later I have discovered couple of issues. First - dm-verity have to be disabled. Second - different ROMs dont play nice with instructions from init.taimen.diag.rc. (adb doesn't work properly).
With this being said I started to looking for a way to inject this instructions into Google Official ROM. Without touching the file system itself.
Unfortunately i haven't found the way make it via Magisk Modules. Because MagiskMount mount the module directory after init stage.
As many of you know Magisk injects init.magisk.rc into init.rc script. So ive decided to recompile the Magisk with the necessary init instructions. I simply updated init.magisk.rc with the following instructions. ( Thanks @topjohnwu for Magisk )
on property:sys.usb.config=diag,serial_cdev,rmnet_gsi,adb && property:sys.usb.configfs=1
start adbd
start port-bridge
on property:sys.usb.ffs.ready=1 && property:sys.usb.config=diag,serial_cdev,rmnet_gsi,adb && property:sys.usb.configfs=1
write /config/usb_gadget/g1/configs/b.1/strings/0x409/configuration "Default composition"
rm /config/usb_gadget/g1/configs/b.1/f1
rm /config/usb_gadget/g1/configs/b.1/f2
rm /config/usb_gadget/g1/configs/b.1/f3
rm /config/usb_gadget/g1/configs/b.1/f4
rm /config/usb_gadget/g1/configs/b.1/f5
write /config/usb_gadget/g1/idVendor 0x05C6
write /config/usb_gadget/g1/idProduct 0x9091
write /config/usb_gadget/g1/os_desc/use 1
symlink /config/usb_gadget/g1/functions/diag.diag /config/usb_gadget/g1/configs/b.1/f1
symlink /config/usb_gadget/g1/functions/cser.dun.0 /config/usb_gadget/g1/configs/b.1/f2
symlink /config/usb_gadget/g1/functions/gsi.rmnet /config/usb_gadget/g1/configs/b.1/f3
symlink /config/usb_gadget/g1/functions/ffs.adb /config/usb_gadget/g1/configs/b.1/f4
write /config/usb_gadget/g1/UDC ${sys.usb.controller}
setprop sys.usb.state ${sys.usb.config}
as a result I was able to open diag port when the following properties are set.
setprop property:sys.usb.configfs 1
sys.usb.config diag,serial_cdev,rmnet_gsi,adb
There are two files attached.
1) Magisk-v18-Taimen-Diag.zip - Modified version of the Magisk. I strongly recommend to install the original version when you finish to play with QXDM. Because I am not a SW developer at all. From the Word "COMPLETELY"
2) Pixel 2 Diag Port.zip - Module for Magisk to properly enable the Diag port on boot via
PHP:
setenforce 0
setprop sys.usb.configfs 1 && setprop sys.usb.config diag,serial_cdev,rmnet_gsi,adb
When you flash the Magisk via twrp and install the module you should be able to get an access to the diag port
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To activate VoLTE on you phone you have to install VoEnabler module and upload proper mcfg_sw.mbn for your MNO.
ive tested Russian MNOs on my phone using Nokia 8 mbn. Works fine for me.
3)Open PDC tool -> Load -> Choose proper MBN -> SetSelectedConfig -> Sub0 -> Activate.
About VoEnabler and other OS methods.
There are actually two methods to get VoLTE\VoWiFI on the phone from OS point of view (VoLTE and VoWiFI provisioned) in *#*#4636#*#* Phone info -> IMS Status.
1) install VoEnabler it performs setprop for Vo*** related parameters.
2)modify /data/user_de/0/com.android.phone/files/carrierconfig-com.android.carrierconfig-XXXXXXXXXXX.xml .
Parameters for xml file you can get from https://developer.android.com/reference/android/telephony/CarrierConfigManager
for example
PHP:
<boolean name="carrier_volte_available_bool" value="true" />
<boolean name="carrier_wfc_supports_wifi_only_bool" value="true" />
<boolean name="carrier_wfc_ims_available_bool" value="true" />
I use several SIM cards so for me it is more comfortable to use second method because this files configure phone module with different settings and it is easier to troubleshoot the issues
<?xml version='1.0' encoding='utf-8' standalone='yes' ?>
<carrier_config>
<package_version>2</package_version>
<bundle_data>
<string name="_carrier_settings_version_string">25099-3000000346</string>
<boolean name="carrier_volte_available_bool" value="true" />
<boolean name="carrier_wfc_supports_wifi_only_bool" value="true" />
<boolean name="carrier_wfc_ims_available_bool" value="true" />
<boolean name="display_hd_audio_property_bool" value="true" />
<boolean name="editable_enhanced_4g_lte_bool" value="true" />
<boolean name="hide_ims_apn_bool" value="false" />
<boolean name="remove_modify_call_capability" value="false" />
<boolean name="transmit_static_image" value="false" />
<boolean name="support_video_conference_call_bool" value="true" />
<boolean name="emergency_sms_support_bool" value="false" />
<boolean name="vowifi_call_quality" value="false" />
<boolean name="show_apn_setting_cdma_bool" value="true" />
<boolean name="carrier_rtt_downgrade_supported" value="false" />
<boolean name="allow_video_call_in_low_battery" value="true" />
<boolean name="world_phone_bool" value="true" />
<boolean name="carrier_rtt_upgrade_supported" value="false" />
<boolean name="hide_preferred_network_type_bool" value="false" />
<boolean name="show_static_image_ui" value="false" />
<boolean name="show_video_quality_ui" value="false" />
<boolean name="show_video_quality_toast" value="true" />
<string-array name="ratchet_rat_families" num="3">
<item value="1,2" />
<item value="7,8,12" />
<item value="3,11,9,10,15" />
</string-array>
<boolean name="apn_expand_bool" value="true" />
<boolean name="allow_adding_apns_bool" value="true" />
<boolean name="carrier_rtt_auto_upgrade" value="false" />
<boolean name="config_carrier_cs_retry_available" value="false" />
<boolean name="video_call_use_ext" value="true" />
<boolean name="show_cdma_choices_bool" value="true" />
<boolean name="carrier_rtt_supported_on_vtcalls" value="false" />
<boolean name="show_data_usage_toast" value="true" />
<boolean name="use_custom_video_ui" value="false" />
<boolean name="carrier_allow_deflect_ims_call_bool" value="false" />
<boolean name="config_hide_preview_in_vt_confcall" value="false" />
<boolean name="config_enable_display_14digit_imei" value="false" />
<boolean name="carrier_rtt_supported" value="false" />
<boolean name="show_call_session_event_toast" value="true" />
<string name="config_ims_package_override_string" value="com.google.android.ims" />
<string name="default_sim_call_manager_string" value="com.google.android.ims" />
</bundle_data>
</carrier_config>
Update 23/03/2019
Thanks to @topjohnwu work on Android Q i've updated the Magisk.zip with diag scripts enabled. Magisk-v18.2-f5f7fd91_Taimen_Diag.zip
The same approach the same steps.
That is true that Magisk module is not required, just disable enforcement and change the sys.usb.config settings.
Just be sure you are using correct drivers.
VoEnabler needs to be updated, not sure whether is works or not. VoLTE provisioning is disabled under "Phone Info"
I was able to open Phone Info app only through the "QuikShortcutMaker" app.
Because i modified /data/user_de/0/com.android.phone/files/carrierconfig-com.android.carrierconfig as well i am not sure what exactly activate the VoLTE. VoEnabler, or the file modification.
Also because TWRP was not able to decrypt the storage in my Phone i uploaded Magisk.zip to /tmp/ directory on my phone.
+ i installed the modified version of the Magisk on top of original canary build. Don;t know whether it important or not.
Update 14/04/2019
Android Q Beta 2 Magisk 19 attached.
Magisk-v19.0_Taimen_Diag
Magisk-uninstaller-20190413
Update 09/05/2019
I have forked Magisk repo. Now OTA updates should work for Taimen_Diag mod.
Testet on Android Q beta 3
App
https://github.com/AGagarin/magisk_files/blob/master/canary_builds/app-debug.apk
Zip
https://github.com/AGagarin/magisk_files/blob/master/canary_builds/magisk-debug.zip
For Drivers search for QUD.WIN.1.1 Installer-10037.3 Setup
For CA https://mt-tech.fi/en/modify-sony-xz-xzs-xz-premium-xz1-and-xz2-lte-a-band-combos/
For more information about PDC tool and mbn files https://forum.xda-developers.com/oneplus-5t/how-to/guide-volte-vowifi-german-carriers-t3817542
Command line tool to read\write EFS settings https://github.com/JohnBel/EfsTools
Confirmed by @pokkaf for Swisscom network (Switzerland) - https://forum.xda-developers.com/showpost.php?p=78592698&postcount=9
Airpil said:
Reserved
Click to expand...
Click to collapse
so this basically enables VOLTE on any carrier, regardless if the carrier supports device or not?? i am currently on cricket, and VOLTE works only on cricket phones and iphones, but not on any other phone even if they are capable of it....
i42o said:
so this basically enables VOLTE on any carrier, regardless if the carrier supports device or not?? i am currently on cricket, and VOLTE works only on cricket phones and iphones, but not on any other phone even if they are capable of it....
Click to expand...
Click to collapse
It allows you to control Qualcomm Chipset. And yes basically you can enable VoLTE you can try different MBN files. Or modify NV items directly via QXDM or EFStool.
Cricket - it is an ATT so you can try to apply mbn file for ATT from the Noki8 folder. Or chose existing ATT profile form the phone. Also there is a profile for Cricket in Pixel3 ROM. Pixel 3 has a different CPU but it might work.
If this method works on Walleye or only on Taimen?
jwchen119 said:
If this method works on Walleye or only on Taimen?
Click to expand...
Click to collapse
Ive tested this method on my Pixel 2 XL. But the changes ive done is quite minor (important but minor) init commands are standard.
So i wouldn't be surprised if it works on Pixel 2 as well.
Hey, just a quick question. I am from India.Currently, volte on works on jio network for pixel devices in india.
Google has still not enabled volte for major providers like airtel/ vodafone even on the latest pixels.
All major phones in india including Oneplus support volte on airtel/vodafone. Will this method work to enable volte ? Also, what are the risk factors ?
coolsid8 said:
Hey, just a quick question. I am from India.Currently, volte on works on jio network for pixel devices in india.
Google has still not enabled volte for major providers like airtel/ vodafone even on the latest pixels.
All major phones in india including Oneplus support volte on airtel/vodafone. Will this method work to enable volte ? Also, what are the risk factors ?
Click to expand...
Click to collapse
there are several mbn for VDF India and Airtel in the Nokia zip attached. Usually MBN file has a vendor signature but Pixel 2 doesn't check the mbn signatures so you can try to apply MBN files from the archive or from any other phone with the same Snapdragon 835 CPU and Generation (MSM8998). Risks .. just notice the previous active MBN in PDC most probably it will be WildCard. If the MBN replacement will not work for you, you can select previous MBN at any time.
Thanks a lot. Helped me to get VoLTE and WiFi Calling working on my Pixel 2 XL on Swisscom network (Switzerland).
Though it was a bit tricky to get the diag mode enabled so that my computer would recognize the Qualcomm modem. After installation of patched Magisk and of the Magisk module zip (Diag port) I also had to execute the "setprop" commands via Terminal on the phone. Plus the Magisk VoEnabler module needs to be active constantly for it to work after adding the mbn via the PDC tool.
Anyone try this in pixel 3?
pokkaf said:
Thanks a lot. Helped me to get VoLTE and WiFi Calling working on my Pixel 2 XL on Swisscom network (Switzerland).
Though it was a bit tricky to get the diag mode enabled so that my computer would recognize the Qualcomm modem. After installation of patched Magisk and of the Magisk module zip (Diag port) I also had to execute the "setprop" commands via Terminal on the phone. Plus the Magisk VoEnabler module needs to be active constantly for it to work after adding the mbn via the PDC tool.
Click to expand...
Click to collapse
Hey , sorry to bug ya again. I have voLTE by default via my carrier. What did you have to do to get wifi calling? Just upload an mbn file?
WiFi calling was enabled when I installed the mbn file from the Nokia 8 (see other thread). I suppose if your carrier supports WiFi calling with the Nokia 8, then it should work with the Pixel if you install the the Nokia's mbn file.
Will it work on one plus one???
pokkaf said:
WiFi calling was enabled when I installed the mbn file from the Nokia 8 (see other thread). I suppose if your carrier supports WiFi calling with the Nokia 8, then it should work with the Pixel if you install the the Nokia's mbn file.
Click to expand...
Click to collapse
Thanks. And you used which program? I've messed with qxdm before but not the other one mentioned.
Also , why not flash a debugging vendor in the future ? Allows access to ports and is safer than the magisk method.
Honestly, I can write all of that here but you could just as well read everything in the other thread. The program was the PDC tool which comes with the whole Qualcomm package.
And for the vendor image.... I don't know. If it's safer to use that, why not try it this way.
Xdevillived666 said:
Thanks. And you used which program? I've messed with qxdm before but not the other one mentioned.
Also , why not flash a debugging vendor in the future ? Allows access to ports and is safer than the magisk method.
Click to expand...
Click to collapse
Advanced PDC Tool to swap the mbn file.
Debugging vendor image cause th dm-verity failure and bootloop. Also there are no PDC\QXDM settings in Debugging image. to support Diag mode we have to have an access to the rmnet usb function.
https://android.googlesource.com/de...eo-m2-release/init.hardware.diag.rc.userdebug
VS
https://android.googlesource.com/device/google/wahoo/+/master/init.hardware.diag.rc.userdebug
pankspoo said:
Will it work on one plus one???
Click to expand...
Click to collapse
For one +1 you can use this guide to get an access to the QXDM
https://forum.xda-developers.com/oneplus-one/general/guide-unlock-aditional-bands-qualcomm-t2877031
for PDC you need to activate rmnet usb function so you may want to try this one
https://forum.xda-developers.com/showpost.php?p=77783004&postcount=3
also OnePlus 5 has the hidden menu. It might work for One+One as well
*#800# --> oneplus Logkit --> Function Switch --> enable VoLTE + VoWifi switch
*#801# ->> Activate Serial & l Full-port switch
pokkaf said:
Thanks a lot. Helped me to get VoLTE and WiFi Calling working on my Pixel 2 XL on Swisscom network (Switzerland).
Though it was a bit tricky to get the diag mode enabled so that my computer would recognize the Qualcomm modem. After installation of patched Magisk and of the Magisk module zip (Diag port) I also had to execute the "setprop" commands via Terminal on the phone. Plus the Magisk VoEnabler module needs to be active constantly for it to work after adding the mbn via the PDC tool.
Click to expand...
Click to collapse
can u pm link for pdc tool? I have qpst and qxdm but I cannot find pdc
Windows start menu > QPST > PDC tool
I will try again tomorrow but using your magisk and module on pixel 3 running du unofficial allowed diagnostic but could not do anything. Will take a look using stock rom and try again