Hello Everyone!
New Android HU owner over here, my head unit information below:
Specific for a Toyota Prado FJ120
Allwinner T8
Android Version: 8.1.0
MCU Version: T8.3.19-203-10-A46101-180726
System Version: V9.3.1_20181115.105802_TW2-FD
My problem is this, I have a USB TPMS system installed in the car, all internal sensors. The app it was shipped with works perfectly fine except that it keeps asking for permission to access the USB receiver each time I start the car. It does this every time even if I set it as default. Is there a way to have the default action stick even after reboots?
Everything is perfect except for this one annoying thing. Here's a photo of the actual head unit and the permission request that keeps popping up (can't post links yet so please replace the underscore with a "t", thanks!):
ht_ps://drive.google.com/file/d/1aYQiuufWGT40JDuMKo7Zv-gYPKNFZDDF/view?usp=sharing
ht_ps://drive.google.com/file/d/1_fzb91vY8XFKJN4PqHfUOMYiA0MHuX1D/view?usp=sharing
I had this problem with hal9k rom in my px5 unit and i found a setting but i don't remember where that does exactly that.
It was called "allow app permission to usb" or something like it and i added there the tpms app and never asked me again.
BlueChris said:
I had this problem with hal9k rom in my px5 unit and i found a setting but i don't remember where that does exactly that.
It was called "allow app permission to usb" or something like it and i added there the tpms app and never asked me again.
Click to expand...
Click to collapse
Thanks for replying BlueChris. Did you have to be rooted to have this setting? Half my setting are disabled and I can find this setting anywhere...
jsbautista08 said:
Thanks for replying BlueChris. Did you have to be rooted to have this setting? Half my setting are disabled and I can find this setting anywhere...
Click to expand...
Click to collapse
I don't know that..i am rooted obviously and i have no way to see that but when i will go to car i will see where this setting is exactly.
Can you root your device, what mcd and cpu it has?
Allwinner T8
Android Version: 8.1.0
MCU Version: T8.3.19-203-10-A46101-180726
System Version: V9.3.1_20181115.105802_TW2-FD
You need to search in xda how to root it, i cannot guide you in this because i got a px5 and my previous HU was with A3 T3.
A simple search here pointed me to
https://forum.xda-developers.c...4290/post75666826#post75666826
But if you find the correct thread better reask the same question there because there must by more knowledge.
jsbautista08 said:
Allwinner T8
Android Version: 8.1.0
MCU Version: T8.3.19-203-10-A46101-180726
System Version: V9.3.1_20181115.105802_TW2-FD
Click to expand...
Click to collapse
Hi jsbautista. Did you find a solution? I have exactly the same problem with the same system.
I finally found a solution for this annoying issue, I'll share it with you :
1) decompile the TPMS.APK using APK Easy Tool v1.57 (must have Java installed)
2) Open AndroidManifest.xml In 1-Decompiled APKs/TMPS directory and edit it adding red instructions (android:directBootAware="true") as below in order to make the app in direct boot aware that gives automatically the permission, you should tick it once, and the android head unit will save the permission setting for next boots :
<application android:allowBackup="true" android:debuggable="true" android:icon="@drawable/ic_launcher" android:label="@string/app_name" android:name="com.syt.tmps.TpmsApplication" androidersistent="true">
<activity android:directBootAware="true" android:exported="true" android:label="@string/app_name" android:launchMode="singleTask" android:name="com.tpms.view.TestActivity" android:theme="@style/customtitlebar"/>
<activity android:directBootAware="true" android:exported="true" android:label="@string/app_name" android:launchMode="singleTask" android:name="com.tpms.view.TpmsMainActivity" android:theme="@style/customtitlebar">
<intent-filter>
<action android:name="android.intent.action.MAIN"/>
<category android:name="android.intent.category.LAUNCHER"/>
</intent-filter>
<intent-filter>
<action android:directBootAware="true" android:name="android.hardware.usb.action.USB_DEVICE_ATTACHED"/>
</intent-filter>
<meta-data android:directBootAware="true" android:name="android.hardware.usb.action.USB_DEVICE_ATTACHED" android:resource="@xml/device_filter"/>
</activity>
3) Save the edited AndroidManifest.xml
4) Compile the apk using the same software
5) Copy the new TPMS.apk app found in 2-Recompiled APKs directory in your USB drive
6) Install the edited app in your android head unit
7) Launch the fresh installed apk and set it as default for the first run
8) Enjoooooy getting rid of this issue !!!!!
9) Share
sami lahmidi said:
I finally found a solution for this annoying issue, I'll share it with you :
1) decompile the TPMS.APK using APK Easy Tool v1.57 (must have Java installed)
2) Open AndroidManifest.xml In 1-Decompiled APKs/TMPS directory and edit it adding red instructions (android:directBootAware="true") as below in order to make the app in direct boot aware that gives automatically the permission, you should tick it once, and the android head unit will save the permission setting for next boots :
3) Save the edited AndroidManifest.xml
4) Compile the apk using the same software
5) Copy the new TPMS.apk app found in 2-Recompiled APKs directory in your USB drive
6) Install the edited app in your android head unit
7) Launch the fresh installed apk and set it as default for the first run
8) Enjoooooy getting rid of this issue !!!!!
9) Share
Click to expand...
Click to collapse
Thank you for the trick.
I haven't the same manifest... But i found in Hal9k rom an option that Always allow the USB connection.
Code:
<manifest*xmlns:android="http://schemas.android.com/apk/res/android"*android:versionCode="300"*android:versionName="3.0.0"*package="com.syt.tmps"*platformBuildVersionCode="19"*platformBuildVersionName="4.4.2-1456859">
<uses-sdk*android:minSdkVersion="15"*android:targetSdkVersion="17"/>
<uses-permission*android:name="android.permission.WRITE_SETTINGS"/>
<uses-permission*android:name="android.permission.READ_PHONE_STATE"/>
<uses-permission*android:name="android.permission.SYSTEM_ALERT_WINDOW"/>
<uses-permission*android:name="android.permission.RECEIVE_BOOT_COMPLETED"/>
<uses-permission*android:name="android.permission.VIBRATE"/>
<uses-permission*android:name="android.permission.BLUETOOTH"/>
<uses-permission*android:name="android.permission.BLUETOOTH_ADMIN"/>
<uses-permission*android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
<uses-permission*android:name="android.permission.ACCESS_NETWORK_STATE"/>
<uses-permission*android:name="android.permission.MOUNT_UNMOUNT_FILESYSTEMS"/>
<uses-permission*android:name="android.permission.READ_EXTERNAL_STORAGE"/>
<uses-permission*android:name="android.permission.GET_TASKS"/>
<uses-permission*android:name="android.permission.READ_LOGS"/>
<application*android:theme="@style/AppSelfTheme"*android:icon="@drawable/ic_launcher"*android:debuggable="true"*android:allowBackup="true">
<activity*android:label="@string/app_name"*android:name="com.syt.tmps.activity.TmpsMainActivity"*android:launchMode="singleTask"*android:screenOrientation="landscape"*android:configChanges="locale">
<intent-filter>
<action*android:name="android.intent.action.MAIN"/>
<category*android:name="android.intent.category.LAUNCHER"/>
</intent-filter>
<intent-filter>
<action*android:name="android.hardware.usb.action.USB_DEVICE_ATTACHED"/>
</intent-filter>
<meta-data*android:name="android.hardware.usb.action.USB_DEVICE_ATTACHED"*android:resource="@xml/device_filter"/>
</activity>
<service*android:name="com.tmps.service.TmpsService">
<intent-filter>
<action*android:name="com.android.ACTION_START_TMPS"/>
</intent-filter>
</service>
<receiver*android:name="com.syt.tmps.activity.BootReceiver">
<intent-filter>
<action*android:name="android.hardware.usb.action.USB_DEVICE_ATTACHED"/>
<action*android:name="android.intent.action.BOOT_COMPLETED"/>
<action*android:name="com.nwd.ACTION_BT_TEST"/>
</intent-filter>
</receiver>
</application>
</manifest>
Envoyé de mon SM-A405FN en utilisant Tapatalk
fredapied said:
Thank you for the trick.
I haven't the same manifest... But i found in Hal9k rom an option that Always allow the USB connection.
Code:
<manifest*xmlns:android="http://schemas.android.com/apk/res/android"*android:versionCode="300"*android:versionName="3.0.0"*package="com.syt.tmps"*platformBuildVersionCode="19"*platformBuildVersionName="4.4.2-1456859">
<uses-sdk*android:minSdkVersion="15"*android:targetSdkVersion="17"/>
<uses-permission*android:name="android.permission.WRITE_SETTINGS"/>
<uses-permission*android:name="android.permission.READ_PHONE_STATE"/>
<uses-permission*android:name="android.permission.SYSTEM_ALERT_WINDOW"/>
<uses-permission*android:name="android.permission.RECEIVE_BOOT_COMPLETED"/>
<uses-permission*android:name="android.permission.VIBRATE"/>
<uses-permission*android:name="android.permission.BLUETOOTH"/>
<uses-permission*android:name="android.permission.BLUETOOTH_ADMIN"/>
<uses-permission*android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
<uses-permission*android:name="android.permission.ACCESS_NETWORK_STATE"/>
<uses-permission*android:name="android.permission.MOUNT_UNMOUNT_FILESYSTEMS"/>
<uses-permission*android:name="android.permission.READ_EXTERNAL_STORAGE"/>
<uses-permission*android:name="android.permission.GET_TASKS"/>
<uses-permission*android:name="android.permission.READ_LOGS"/>
<application*android:theme="@style/AppSelfTheme"*android:icon="@drawable/ic_launcher"*android:debuggable="true"*android:allowBackup="true">
<activity*android:label="@string/app_name"*android:name="com.syt.tmps.activity.TmpsMainActivity"*android:launchMode="singleTask"*android:screenOrientation="landscape"*android:configChanges="locale">
<intent-filter>
<action*android:name="android.intent.action.MAIN"/>
<category*android:name="android.intent.category.LAUNCHER"/>
</intent-filter>
<intent-filter>
<action*android:name="android.hardware.usb.action.USB_DEVICE_ATTACHED"/>
</intent-filter>
<meta-data*android:name="android.hardware.usb.action.USB_DEVICE_ATTACHED"*android:resource="@xml/device_filter"/>
</activity>
<service*android:name="com.tmps.service.TmpsService">
<intent-filter>
<action*android:name="com.android.ACTION_START_TMPS"/>
</intent-filter>
</service>
<receiver*android:name="com.syt.tmps.activity.BootReceiver">
<intent-filter>
<action*android:name="android.hardware.usb.action.USB_DEVICE_ATTACHED"/>
<action*android:name="android.intent.action.BOOT_COMPLETED"/>
<action*android:name="com.nwd.ACTION_BT_TEST"/>
</intent-filter>
</receiver>
</application>
</manifest>
Envoyé de mon SM-A405FN en utilisant Tapatalk
Click to expand...
Click to collapse
Hi there, where exactly did you find the Hal9k rom option that Always allow the USB connection.
TIA.
sandpita said:
Hi there, where exactly did you find the Hal9k rom option that Always allow the USB connection.
TIA.
Click to expand...
Click to collapse
See pics (it's in French ):
Mod setup
Apps manager
USB apps..
{
"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"
}
Envoyé de mon SM-A405FN en utilisant Tapatalk
sami lahmidi said:
I finally found a solution for this annoying issue, I'll share it with you :
1) decompile the TPMS.APK using APK Easy Tool v1.57 (must have Java installed)
2) Open AndroidManifest.xml In 1-Decompiled APKs/TMPS directory and edit it adding red instructions (android:directBootAware="true") as below in order to make the app in direct boot aware that gives automatically the permission, you should tick it once, and the android head unit will save the permission setting for next boots :
<application android:allowBackup="true" android:debuggable="true" android:icon="@drawable/ic_launcher" android:label="@string/app_name" android:name="com.syt.tmps.TpmsApplication" androidersistent="true">
<activity android:directBootAware="true" android:exported="true" android:label="@string/app_name" android:launchMode="singleTask" android:name="com.tpms.view.TestActivity" android:theme="@style/customtitlebar"/>
<activity android:directBootAware="true" android:exported="true" android:label="@string/app_name" android:launchMode="singleTask" android:name="com.tpms.view.TpmsMainActivity" android:theme="@style/customtitlebar">
<intent-filter>
<action android:name="android.intent.action.MAIN"/>
<category android:name="android.intent.category.LAUNCHER"/>
</intent-filter>
<intent-filter>
<action android:directBootAware="true" android:name="android.hardware.usb.action.USB_DEVICE_ATTACHED"/>
</intent-filter>
<meta-data android:directBootAware="true" android:name="android.hardware.usb.action.USB_DEVICE_ATTACHED" android:resource="@xml/device_filter"/>
</activity>
3) Save the edited AndroidManifest.xml
4) Compile the apk using the same software
5) Copy the new TPMS.apk app found in 2-Recompiled APKs directory in your USB drive
6) Install the edited app in your android head unit
7) Launch the fresh installed apk and set it as default for the first run
8) Enjoooooy getting rid of this issue !!!!!
9) Share
Click to expand...
Click to collapse
Thank You sir. This worked perfectly for me.
comptechltd said:
Thank You sir. This worked perfectly for me.
Click to expand...
Click to collapse
can u share the tpms.apk that u have modified?
comptechltd said:
Thank You sir. This worked perfectly for me.
Click to expand...
Click to collapse
Could you kindly share step by step information, the information you shared can not be followed PLS, we need this TPMS help
sami lahmidi said:
I finally found a solution for this annoying issue, I'll share it with you :
1) decompile the TPMS.APK using APK Easy Tool v1.57 (must have Java installed)
2) Open AndroidManifest.xml In 1-Decompiled APKs/TMPS directory and edit it adding red instructions (android:directBootAware="true") as below in order to make the app in direct boot aware that gives automatically the permission, you should tick it once, and the android head unit will save the permission setting for next boots :
<application android:allowBackup="true" android:debuggable="true" android:icon="@drawable/ic_launcher" android:label="@string/app_name" android:name="com.syt.tmps.TpmsApplication" androidersistent="true">
<activity android:directBootAware="true" android:exported="true" android:label="@string/app_name" android:launchMode="singleTask" android:name="com.tpms.view.TestActivity" android:theme="@style/customtitlebar"/>
<activity android:directBootAware="true" android:exported="true" android:label="@string/app_name" android:launchMode="singleTask" android:name="com.tpms.view.TpmsMainActivity" android:theme="@style/customtitlebar">
<intent-filter>
<action android:name="android.intent.action.MAIN"/>
<category android:name="android.intent.category.LAUNCHER"/>
</intent-filter>
<intent-filter>
<action android:directBootAware="true" android:name="android.hardware.usb.action.USB_DEVICE_ATTACHED"/>
</intent-filter>
<meta-data android:directBootAware="true" android:name="android.hardware.usb.action.USB_DEVICE_ATTACHED" android:resource="@xml/device_filter"/>
</activity>
3) Save the edited AndroidManifest.xml
4) Compile the apk using the same software
5) Copy the new TPMS.apk app found in 2-Recompiled APKs directory in your USB drive
6) Install the edited app in your android head unit
7) Launch the fresh installed apk and set it as default for the first run
8) Enjoooooy getting rid of this issue !!!!!
9) Share
Click to expand...
Click to collapse
Thanks so much this worked like a charm for me.
comptechltd said:
Thank You sir. This worked perfectly for me.
Click to expand...
Click to collapse
Can u share the modified apk please
Pls can anyone send me the mod apk?
arampatla said:
Thanks so much this worked like a charm for me.
Click to expand...
Click to collapse
can u send me the mod apk pls?
sami lahmidi said:
I finally found a solution for this annoying issue, I'll share it with you :
1) decompile the TPMS.APK using APK Easy Tool v1.57 (must have Java installed)
2) Open AndroidManifest.xml In 1-Decompiled APKs/TMPS directory and edit it adding red instructions (android:directBootAware="true") as below in order to make the app in direct boot aware that gives automatically the permission, you should tick it once, and the android head unit will save the permission setting for next boots :
<application android:allowBackup="true" android:debuggable="true" android:icon="@drawable/ic_launcher" android:label="@string/app_name" android:name="com.syt.tmps.TpmsApplication" androidersistent="true">
<activity android:directBootAware="true" android:exported="true" android:label="@string/app_name" android:launchMode="singleTask" android:name="com.tpms.view.TestActivity" android:theme="@style/customtitlebar"/>
<activity android:directBootAware="true" android:exported="true" android:label="@string/app_name" android:launchMode="singleTask" android:name="com.tpms.view.TpmsMainActivity" android:theme="@style/customtitlebar">
<intent-filter>
<action android:name="android.intent.action.MAIN"/>
<category android:name="android.intent.category.LAUNCHER"/>
</intent-filter>
<intent-filter>
<action android:directBootAware="true" android:name="android.hardware.usb.action.USB_DEVICE_ATTACHED"/>
</intent-filter>
<meta-data android:directBootAware="true" android:name="android.hardware.usb.action.USB_DEVICE_ATTACHED" android:resource="@xml/device_filter"/>
</activity>
3) Save the edited AndroidManifest.xml
4) Compile the apk using the same software
5) Copy the new TPMS.apk app found in 2-Recompiled APKs directory in your USB drive
6) Install the edited app in your android head unit
7) Launch the fresh installed apk and set it as default for the first run
8) Enjoooooy getting rid of this issue !!!!!
9) Share
Click to expand...
Click to collapse
I got the recompiled file as is the method, however, I cannot get it installed on my android head. The installer show "App not installed". Plz help. Thx!
pro_desk said:
I got the recompiled file as is the method, however, I cannot get it installed on my android head. The installer show "App not installed". Plz help. Thx!
Click to expand...
Click to collapse
Can u send me the apk so i can try to install it or to find whats the problem? Email [email protected]
Or send it as a cloud file "google drive - one drive etc)"
Related
open dialer and enter this code *#*#8736364#*#*
if you use apk manager to decompile an apk and look inside AndroidManifest.xml
you can find all sorts of secret codes but be careful I found one that instantly does a factory format including the internal sd card.
example:
Code:
<intent-filter>
<action android:name="android.provider.Telephony.SECRET_CODE" />
<data android:scheme="android_secret_code" android:host="8736364" />
</intent-filter>
just enclose the numbers with *#*# before the numbers and #*#* after the numbers.
tried it and it didnt update Similar thing was posted in a different thread. Anyone able to get it to update?
it was about 10min before I got a notification that there was an update.
I tried it and think it works. I am unable to receive an update because I have my vibrant on att network. Do you know the correct device manager settings for t-mobile
Sent from my SGH-T959 using XDA App
Hi all!
I've updated from 4.3 to 4.4.2 Samsung Rom (tw). My case NB8.
Titanium Backup has stopped working. Shows the error "not enough space" when backing up to external sd card. Also, it shows that extsdcard is not writeable.
Here's the solution for i9505 to get it working, of course you need root to do that. It may work for other apps too and other phone models such i9500:
Edit file platform.xml in system/etc/permissions (make a backup first).
Search for this:
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
</permission>
Add this:
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
[COLOR="Green"][B]<group gid="media_rw" />[/B][/COLOR]
</permission>
Save changes and reboot.
Regards.
cybdani said:
Hi all!
I've updated from 4.3 to 4.4.2 Samsung Rom (tw). My case NB8.
Titanium Backup has stopped working. Shows the error "not enough space" when backing up to external sd card. Also, it shows that extsdcard is not writeable.
Here's the solution for i9505 to get it working, of course you need root to do that. It may work for other apps too and other phone models such i9500:
Edit file platform.xml in system/etc/permissions (make a backup first).
Search for this:
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
</permission>
Add this:
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
[COLOR="Green"][B]<group gid="media_rw" />[/B][/COLOR]
</permission>
Save changes and reboot.
Regards.
Click to expand...
Click to collapse
Lifesaver, cheers! Now if only there was a way for TB to restore all your apps without you having to click Install and Done on each one, this will take all day!
nrps1 said:
Lifesaver, cheers! Now if only there was a way for TB to restore all your apps without you having to click Install and Done on each one, this will take all day!
Click to expand...
Click to collapse
The pro version does not ask to install afaik. It installs all apps automaticly
Gesendet von meinem GT-I9505 mit Tapatalk
benni2903 said:
The pro version does not ask to install afaik. It installs all apps automaticly
Gesendet von meinem GT-I9505 mit Tapatalk
Click to expand...
Click to collapse
It looks to me like the ROM security itself, whenever I install anything it prompts for me to accept permissions etc, does this still apply?
If you are using the batch restore(?)(restore all backups + data) then it will not ask for every single app. TB just installs everything in the background
Gesendet von meinem GT-I9505 mit Tapatalk
benni2903 said:
If you are using the batch restore(?)(restore all backups + data) then it will not ask for every single app. TB just installs everything in the background
Gesendet von meinem GT-I9505 mit Tapatalk
Click to expand...
Click to collapse
Yes, you are right benni2903.
I hope that this thread can help to users that are upgrading to TW 4.4.2. I've spent over half an hour to find out where the problem was.
Regards
benni2903 said:
If you are using the batch restore(?)(restore all backups + data) then it will not ask for every single app. TB just installs everything in the background
Gesendet von meinem GT-I9505 mit Tapatalk
Click to expand...
Click to collapse
Strange, that is exactly what I chose and it was indeed asking for each one it needed to download (I assume). Oh well, I just flashed firmware and signed in on 1st boot and Google handled the rest instead!
nrps1 said:
Strange, that is exactly what I chose and it was indeed asking for each one it needed to download (I assume). Oh well, I just flashed firmware and signed in on 1st boot and Google handled the rest instead!
Click to expand...
Click to collapse
I don't configure my google account after a firm upgrade (if I deleted all data) until I've restored all apps using titanium. I install the free version from my external sd.
cybdani said:
Hi all!
I've updated from 4.3 to 4.4.2 Samsung Rom (tw). My case NB8.
Titanium Backup has stopped working. Shows the error "not enough space" when backing up to external sd card. Also, it shows that extsdcard is not writeable.
Here's the solution for i9505 to get it working, of course you need root to do that. It may work for other apps too and other phone models such i9500:
Edit file platform.xml in system/etc/permissions (make a backup first).
Search for this:
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
</permission>
Add this:
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
[COLOR="Green"][B]<group gid="media_rw" />[/B][/COLOR]
</permission>
Save changes and reboot.
Regards.
Click to expand...
Click to collapse
Many many thanks for sharing this!
It really did the trick!
I was about to rip my hair off, didn't know whether to ask the kernel developer or the titanium support first.
Also TB doesn't need internet connection ob startup for license check. Now I can also use TB again offline with full functionality
You saved my day
P.S. I'll hit the thanks buttons tomorrow,i spend all my thanks today for @ktoonsez awesome kernel
thank you! this saved me from pulling my hair out when i flashed a new rom!
cybdani said:
Hi all!
I've updated from 4.3 to 4.4.2 Samsung Rom (tw). My case NB8.
Titanium Backup has stopped working. Shows the error "not enough space" when backing up to external sd card. Also, it shows that extsdcard is not writeable.
Here's the solution for i9505 to get it working, of course you need root to do that. It may work for other apps too and other phone models such i9500:
Edit file platform.xml in system/etc/permissions (make a backup first).
Search for this:
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
</permission>
Add this:
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
[COLOR="Green"][B]<group gid="media_rw" />[/B][/COLOR]
</permission>
Save changes and reboot.
Regards.
Click to expand...
Click to collapse
Hi there - tried doing this fix using ES File Explorer - initially it wouldn't save so I coped the file out of original file path to internal SD to test and was able to save - tried pasting new file in and got error that the file system was read only (which was likely my original problem as suspected). How to I get around this, or change the file path location to writeable to simply save the original platform.xml?
Thanks,
~snowin
Disregard - I failed to see the little button where I could change permissions on the permissions folder Thanks for looking
---------- Post added at 06:08 PM ---------- Previous post was at 05:22 PM ----------
OK - so after re-booting my internal SD card seems to be "lost". A bunch of apps FC including titanium. I can access my external SD card using ES @ /storage/extsdcard but the /sdcard/ & storage/emulated are all blanks. Can someone point me in the right direction? I'm running ezkat 2.0 ROM for Note ii
snowin said:
Hi there - tried doing this fix using ES File Explorer - initially it wouldn't save so I coped the file out of original file path to internal SD to test and was able to save - tried pasting new file in and got error that the file system was read only (which was likely my original problem as suspected). How to I get around this, or change the file path location to writeable to simply save the original platform.xml?
Thanks,
~snowin
Disregard - I failed to see the little button where I could change permissions on the permissions folder Thanks for looking
---------- Post added at 06:08 PM ---------- Previous post was at 05:22 PM ----------
OK - so after re-booting my internal SD card seems to be "lost". A bunch of apps FC including titanium. I can access my external SD card using ES @ /storage/extsdcard but the /sdcard/ & storage/emulated are all blanks. Can someone point me in the right direction? I'm running ezkat 2.0 ROM for Note ii
Click to expand...
Click to collapse
Before to edit file, you need to mount system as RW. Then you can edit and save file. Root Explorer is better than es file explorer.
cybdani said:
Hi all!
I've updated from 4.3 to 4.4.2 Samsung Rom (tw). My case NB8.
Titanium Backup has stopped working. Shows the error "not enough space" when backing up to external sd card. Also, it shows that extsdcard is not writeable.
Here's the solution for i9505 to get it working, of course you need root to do that. It may work for other apps too and other phone models such i9500:
Edit file platform.xml in system/etc/permissions (make a backup first).
Search for this:
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
</permission>
Add this:
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
[COLOR="Green"][B]<group gid="media_rw" />[/B][/COLOR]
</permission>
Save changes and reboot.
Regards.
Click to expand...
Click to collapse
Hey thanks so much for the solution! Fixed my Umi Zero right up (now I can start tweaking , but I'm curious, how does this fix work? Thanks!
Hi there,
I've posted this already in the launcher 8 thread, but I guess it should've gone here from the start since it's a very specific nook question, so here goes:
I've rooted my nook and am running launcher 8 now, I am on 1.5.2 right now but I've tried newer versions too which still work with the old android system running on the nook. The latest 2.6 and 3.0 versions do not work.
I've ran into a problem though: I don't seem to be able to choose launcher 8 as the default launcher when I press the home button.
Is there anything I can do to solve this?
Some pictures attached just to make clear what my problem actually is.
schelleursli said:
Hi there,
I've posted this already in the launcher 8 thread, but I guess it should've gone here from the start since it's a very specific nook question, so here goes:
I've rooted my nook and am running launcher 8 now, I am on 1.5.2 right now but I've tried newer versions too which still work with the old android system running on the nook. The latest 2.6 and 3.0 versions do not work.
I've ran into a problem though: I don't seem to be able to choose launcher 8 as the default launcher when I press the home button.
Is there anything I can do to solve this?
Some pictures attached just to make clear what my problem actually is.
Click to expand...
Click to collapse
It appears from the photographs that your Nook is not recognizing Launcher8 as a launcher app, but instead as a regular app. Are you able to view Launcher8 from ReLaunch's app drawer?
Thanks for the reply, I guess you mean the "All applications" bit in ReLaunch? Then yes, it's there, thats how I start it at the moment.
I've already tried fiddling with the AndroidManifest.xml but I really don't know what I'm doing.
schelleursli said:
Thanks for the reply, I guess you mean the "All applications" bit in ReLaunch? Then yes, it's there, thats how I start it at the moment.
I've already tried fiddling with the AndroidManifest.xml but I really don't know what I'm doing.
Click to expand...
Click to collapse
Yes, "All applications" is ReLaunch's app drawer.
I don't know exactly how to fix this, but let me do some research, and I'll get back to you.
Check the intent-filter's in AndroidManifest.xml
You probably should see something like this:
Code:
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.HOME" />
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
You can also try through ADB shell:
Code:
am start -a android.intent.action.MAIN -c android.intent.category.HOME
and see what happens.
Renate NST said:
Check the intent-filter's in AndroidManifest.xml
You probably should see something like this:
Code:
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.HOME" />
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
You can also try through ADB shell:
Code:
am start -a android.intent.action.MAIN -c android.intent.category.HOME
and see what happens.
Click to expand...
Click to collapse
Thanks for that, I've tried fiddling with the Manifest but I always either get a non working application with an entry in the Home menu or a working application with no entry in the Home menu to choose as default.
If you feel like having a look, this is the default manifest that is in use by launcher 8: pastebin.com/K8BknQuk (I'm not allowed to post links yet)
I do not have the android sdk installed or anything prepared to run ADB on my nook, I'll look into that at some point if the manifest fiddling doesn't work out.
The AndroidManifest.xml looks fine, which is to be expected.
Maybe you "picked" the wrong application at some point?
That's all in /data/system/packages.xml
Check preferred-activities in there.
You can always delete that whole section, as long as you do it cleanly.
Thanks for the continued help. I've had a look at packages.xml preferred-activities looks like this:
Code:
<preferred-activities>
<item name="com.lx.launcher8/.AnallLauncher" match="100000" set="4">
<set name="com.bn.nook.home/.HomeActivity" />
<set name="com.lx.launcher8/.AnallLauncher" />
<set name="com.lx.launcher8/.Home" />
<set name="com.harasoft.relaunch/.Home" />
<filter>
<action name="android.intent.action.MAIN" />
<cat name="android.intent.category.HOME" />
<cat name="android.intent.category.DEFAULT" />
</filter>
</item>
</preferred-activities>
I can turn off my nook and turn it on again then launcher 8 starts by default, but if I press the "n" button on the nook and then press home on the touch-screen I still only get the choice between ReLaunch and the default nook Home. I've also tried completely resetting my device restoring an old unrooted backup then root it again and set it up from scratch, same problem.
I don't have my nook with me (lost it a few days ago) but I seems to remember seeing a nook manager app that can help program what buttons do what, including the N button. You may have to lose the pop up home/library/shop/search/glowlight/setting thing (you could delegate that function to long press N if you want.) but the app should properly program the N button to start up the launcher 8. I THINK it's the Nook Color Tool? I remember the appropriate app came with the 1337 ROM.
Deafcyclist said:
I don't have my nook with me (lost it a few days ago) but I seems to remember seeing a nook manager app that can help program what buttons do what, including the N button. You may have to lose the pop up home/library/shop/search/glowlight/setting thing (you could delegate that function to long press N if you want.) but the app should properly program the N button to start up the launcher 8. I THINK it's the Nook Color Tool? I remember the appropriate app came with the 1337 ROM.
Click to expand...
Click to collapse
Yep, that's Nook Touch Mod Manager. It comes pre-installed with NookManager and my 1337 ROM, but it can also be installed manually with some modified framework-related .jar files.
Thanks for the tip, sounds like a good workaround for now.
edit: I see I need a running build environment for that, will see if I can get this to work on my virtual machine.
edit2: got it working
Oh, the "n" button?
B&N has that hardwired to do some B&N specific intent.
This problem has been solved many different ways.
My solution is to patch where the problem is, com.android.internal.policy.impl.PhoneWindowManager (in android.policy.jar).
This just makes the "n" key a normal Home key.
Code:
apktool d android.policy.jar -o C:\AP
mergesmali /v C:\AP PhoneWindowManager.smali PhoneWindowManager$HomeButtonHandler.smali
apktool b C:\AP -o android.policy.jar
Check the mergesmali link in the signature, a zip of the patches is there too.
No it was the "Home" menu button you open by pressing the "n" button. But with Nook Touch Mod Manager I've managed to change the behaviour of said "Home" even though Launcher 8 still wasn't shown as a choice. Thanks for all the help.
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