Related
Ok, I'm about at my wit's end on this. I'm trying to get Marshmallow with root access activated. I flash the firmware, activate it, verify everything works (i.e. voice calls), root it, then I'm unable to get voice calling back. LTE usually goes as well, but that's easy enough to fix. I've tried "Activate Phone" under Settings, and ##72786# with the dialer over 10 times on many installs without success. Doing a /data reset after root results in the initial setup going through, but no voice service. Importing build.prop from before rooting generally restores LTE but not voice.
Here's my general method:
Use Odin to flash a firmware, having tried with every firmware below. Some are rejected by the bootloader, I suppose attempting Nouget was ill-advised in retrospect, but most work fine:
Code:
07/09/2017 02:35 AM 2,339,073,264 G935PVPS4APK1_SPT4APK1_SPR_Sprint_USA_6.0
.1.zip
07/08/2017 05:23 PM 2,338,378,352 G935PVPU2APH7_G935PSPT2APH7_SPR.zip
07/08/2017 05:44 PM 2,415,317,465 G935PVPU4APL6_G935PSPT4APL6_SPR.zip
07/04/2017 06:02 AM 2,346,196,486 G935UUEU4API3_G935UOYM4API3_TMK.zip
06/29/2017 07:09 PM 2,393,582,382 SPR-G935UUES4AQC1-20170313090738.zip
07/04/2017 09:56 PM 2,333,204,698 SPR-G935UUEU2APEH-20160518091232.zip
07/05/2017 07:12 AM 2,332,915,504 SPR-G935UUEU2APG9-20160823142730.zip
07/05/2017 12:52 PM 2,346,196,486 SPR-G935UUEU4API3-20160909113048.zip
This activates on its own without any trouble. Sometimes I update the Profile/PRL, sometimes not.
Then I install Package Disabler and disable at minimum securitylogagent, but generally anything mentioned by any root guide and anything that looks squirrely to me.
Use Odin to flash g935a.tar
Use root.bat (I've modified it slightly over the various attempts. Mostly because someone put a reboot command in the middle of the script which introduced a race condition to finish the script before the system halted, with unpredictable results.)
Code:
adb wait-for-device
adb shell mount -o rw,remount /system
adb shell mount -o rw,remount rootfs /
adb push SuperSU-v2.74-2.img /data/su.img
adb push launch_daemonsu.sh /system/etc/launch_daemonsu.sh
adb install -r SuperSU-v2.74-2.apk
adb shell pm hide com.LocalFota
adb shell pm hide com.samsung.android.intelligenceservice
adb shell pm hide com.samsung.android.securitylogagent
adb shell pm hide com.samsung.sdm
adb shell pm hide com.samsung.syncservice
adb shell pm hide com.sec.android.diagmonagent
adb shell pm hide com.sec.android.fotaclient
adb shell pm hide com.sec.android.fwupgrade
adb shell pm hide com.sec.fwservice
adb shell pm hide com.ws.dm
adb shell pm hide com.wssyncmldm
adb shell < supersu.cmds
Code:
touch /system/xbin/su
chmod 0755 /system/xbin/su
chcon u:object_r:system_file:s0 /system/xbin/su
chmod 0700 /system/etc/launch_daemonsu.sh
chcon u:object_r:su_exec:s0 /system/etc/launch_daemonsu.sh
if [ `cat /system/etc/init.sec.boot.sh | grep daemonsu >/dev/null 2>&1; echo $?` -ne 0 ]; then
echo '/system/etc/launch_daemonsu.sh' >> /system/etc/init.sec.boot.sh
fi
sync
reboot
Then root works, I switch the CPU governor and modify the three lines of build.prop (or reinstate the pre-root version), and disable securestorage in build.prop as well (wifi password persistence fix). Maybe install xposed if I feel like wasting my time, although it does work perfectly. Upon a reboot LTE generally works, if not I update the APN settings on the older firmwares. Then I try activation, which fixes it if APN settings are disabled. But no voice. After a few attempts I'll reenable everything and try again (+/- a reboot), but it doesn't make a difference.
Any ideas? I seem to be having an unusual amount of trouble with this and I'm not sure why...
Having this exact problem. Dont know what to do
Edit:
Got myself back to stock with help from this thread
https://forum.xda-developers.com/showpost.php?p=76029292&postcount=12
look for the binary 5 google docs links in there if you just want to get back to stock and get text and voice working again
Hi,
I hope this is a thread that will soon be completely unnecessary.
Disclaimer: I have hardly any knowledge of bluetooth. I don't use it much either. I use WiFi tethering, I hardly ever call in my car (it is considered too dangerous and I agree), I have my music on SDcard.
So the reason for this post is not because I want "to tell" about bluetooth. The only reason is that multiple users sent me PMs asking questions about it.
To have it not too cluttered, and without the real bluetooth experts being able to give their valuable opinion in the forum, I created this post.
I downloaded a Cyanogenmod CM-13 6.0.1 (beta) ROM for the Asus Zenfone, and I downloaded the official 6.0.1 Asus ROM for the Zenfone.
The Asus Zenfone has an Intel(R) atom Z3560 CPU.
Our Joying has a Sofia x64 from the C3200 series, so there is a difference but programmaticaly they are the same. I can't find specifics on the used bluetooth chip set and of course the underlying MCU, in case of the Joying, is totally different.
So for those users who asked me and are brave enough to try for themselves I created two zips containing all necessary files AFAIK.
The CM13 file is of course the Cyanogenmod, the UL-Z00 is the official Asus one. The real system "stuff" in the Cyanogenmod is in general more a "fits all possible x86 architectures" build whereas brand specific ROMS are of course more tuned to the specific hardware.
I took these from the following links:
http://rootmygalaxy.net/install-cm13-on-zenfone-2/
http://rootmygalaxy.net/download-in...c550kl-android-6-0-1-marshmallow-beta-update/
https://www.asus.com/Phone/ZenFone_2_ZE551ML/HelpDesk_Knowledge/ (and likewise support pages for the variety of the models)
So again: If you are brave enough, try for yourself.
I hope some bluetooth expert can shine a light on this. Or better: That Joying or FYT fixes it.
I also downloaded another intel-MTCD (other MCU) head unit ROM, but it seems for 95% the same as the Joying 27 April first 6.0.1 ROM, so to me not worth the effort.
surfer63 said:
Hi,
I hope this is a thread that will soon be completely unnecessary.
Disclaimer: I have hardly any knowledge of bluetooth. I don't use it much either. I use WiFi tethering, I hardly ever call in my car (it is considered too dangerous and I agree), I have my music on SDcard.
So the reason for this post is not because I want "to tell" about bluetooth. The only reason is that multiple users sent me PMs asking questions about it.
To have it not too cluttered, and without the real bluetooth experts being able to give their valuable opinion in the forum, I created this post.
I downloaded a Cyanogenmod CM-13 6.0.1 (beta) ROM for the Asus Zenfone, and I downloaded the official 6.0.1 Asus ROM for the Zenfone.
The Asus Zenfone has an Intel(R) atom Z3560 CPU.
Our Joying has a Sofia x64 from the C3200 series, so there is a difference but programmaticaly they are the same. I can't find specifics on the used bluetooth chip set and of course the underlying MCU, in case of the Joying, is totally different.
So for those users who asked me and are brave enough to try for themselves I created two zips containing all necessary files AFAIK.
The CM13 file is of course the Cyanogenmod, the UL-Z00 is the official Asus one. The real system "stuff" in the Cyanogenmod is in general more a "fits all possible x86 architectures" build whereas brand specific ROMS are of course more tuned to the specific hardware.
I took these from the following links:
http://rootmygalaxy.net/install-cm13-on-zenfone-2/
http://rootmygalaxy.net/download-in...c550kl-android-6-0-1-marshmallow-beta-update/
https://www.asus.com/Phone/ZenFone_2_ZE551ML/HelpDesk_Knowledge/ (and likewise support pages for the variety of the models)
So again: If you are brave enough, try for yourself.
I hope some bluetooth expert can shine a light on this. Or better: That Joying or FYT fixes it.
I also downloaded another intel-MTCD (other MCU) head unit ROM, but it seems for 95% the same as the Joying 27 April first 6.0.1 ROM, so to me not worth the effort.
Click to expand...
Click to collapse
Will give this a try as soon as possible
Sent from my HUAWEI M2-802L using Tapatalk
I am going to have a try today and see what happens.
@surfer63
Is there anything in the joying server that is interacting with the Bluetooth core or the Joying BT app?
I have a funny feeling that something joying is turning the BT off if not using the Joying BT app, been doing this since android 6.0 after about 3mins.
sucks for people running apps that don't require the Joying BT app, eg Inet Truma Box for incar heating controlled with BT
So I started today putting together a batch ADB file to test the CM version of the BT for joying
I have completely run out of time to finish it and I wont be able to complete it till next week, there is quite a bit to go on it and i am not even sure it works, so if anyone want to continue with it, u can.
The ADB Files are not my work and i don't take credit for it, I only added the files and made the batch
This work is not complete and SHOULD NOT BE USED in its current state.
Attached is the half built BluetoothUpgrade Files
View attachment BluetoothUpdate.zip
Echo off
adb kill-server
adb connect %1
adb root
adb connect %1
adb shell mount -o rw,remount /system
adb shell mount -o rw,remount /system /system
adb shell mount -o rw,remount /
adb shell mount -o rw,remount / /
# Push New Files To SDcard (Should Be Finished)
adb push Bluetooth.apk /sdcard/
adb push BluetoothExt.apk /sdcard/
adb push BluetoothMidiService.apk /sdcard/
adb push btnvtool /sdcard/
adb push btsnoop /sdcard/
adb push MTP_WCD9306_Bluetooth_cal.acdb /sdcard/
adb push MTP_Bluetooth_cal_ZD550KL.acdb /sdcard/
adb push MTP_Bluetooth_cal_ZE550KL.acdb /sdcard/
adb push MTP_Bluetooth_cal_ZE600KL.acdb /sdcard/
adb push QRD_Bluetooth_cal.acdb /sdcard/
adb push QRD_SKUL_Bluetooth_cal.acdb /sdcard/
adb push bt_did.conf /sdcard/
adb push bt_stack.conf /sdcard/
adb push android.hardware.bluetooth.xml /sdcard/
adb push android.hardware.bluetooth_le.xml /sdcard/
adb push init.qcom.bt.sh /sdcard/
adb push libbluetooth_jni.so /sdcard/
adb push bluetooth.default.so /sdcard/
adb push libbt-vendor.so /sdcard/
adb push libbtnv.so /sdcard/
# Move The Original Files To OLD Files (List Not Finsished)
adb shell "su -c cp /system/Bluetooth/Bluetooth.apk /system/Bluetooth/Bluetooth.apk.old"
adb shell "su -c cp /system/Bluetooth/oat/x86/Bluetooth.odex /system/Bluetooth/oat/x86/Bluetooth.odex.old"
adb shell "su -c cp /system/Bluetooth/lib/libbluetooth_jni.so /system/Bluetooth/lib/libbluetooth_jni.so.old"
adb shell "su -c cp /system/BluetoothMidiService/BluetoothMidiService.apk /system/BluetoothMidiService/BluetoothMidiService.apk.old"
adb shell "su -c cp /system/BluetoothMidiService/oat/x86/BluetoothMidiService.odex /system/BluetoothMidiService/oat/x86/BluetoothMidiService.odex.old"
# Make New Directories (List Not Finished)
adb shell "mkdir /system/app/BluetoothExt/"
adb shell "mkdir /system/etc/acdbdata/"
adb shell "mkdir /system/etc/acdbdata/MTP/"
adb shell "mkdir /system/etc/acdbdata/MTP/msm8939-tapan-snd-card/"
adb shell "mkdir /system/etc/acdbdata/MTP/ZD550KL/"
adb shell "mkdir /system/etc/acdbdata/MTP/ZE550KL/"
adb shell "mkdir /system/etc/acdbdata/MTP/ZE600KL/"
adb shell "mkdir /system/etc/acdbdata/QRD/"
adb shell "mkdir /system/etc/acdbdata/QRD/msm8939-snd-card-skul/"
adb shell "mkdir /system/vendor/lib64"
# Set Permissions Of New Directories (List Not Finished)
adb shell "chmod 0755 /system/app/BluetoothExt/"
adb shell "chmod 0755 /system/etc/acdbdata/"
adb shell "chmod 0755 /system/etc/acdbdata/MTP/"
adb shell "chmod 0755 /system/etc/acdbdata/MTP/msm8939-tapan-snd-card/"
adb shell "chmod 0755 /system/etc/acdbdata/MTP/ZD550KL/"
adb shell "chmod 0755 /system/etc/acdbdata/MTP/ZE550KL/"
adb shell "chmod 0755 /system/etc/acdbdata/MTP/ZE600KL/"
adb shell "chmod 0755 /system/etc/acdbdata/QRD/"
adb shell "chmod 0755 /system/etc/acdbdata/QRD/msm8939-snd-card-skul/
adb shell "chmod 0755 /system/vendor/lib64"
# Copy The New Files To Locations (Should Be Finished, Not tested)
adb shell "su -c cp /sdcard/Bluetooth.apk /system/app/Bluetooth/Bluetooth.apk"
adb shell "su -c cp /sdcard/BluetoothExt.apk /system/app/BluetoothExt/BluetoothExt.apk"
adb shell "su -c cp /sdcard/BluetoothMidiService.apk /system/app/BluetoothMidiService/BluetoothMidiService.apk"
adb shell "su -c cp /sdcard/btnvtool /system/bin/btnvtool"
adb shell "su -c cp /sdcard/btsnoop /system/bin/btsnoop"
adb shell "su -c cp /sdcard/MTP_Bluetooth_cal.acdb /system/etc/acdbdata/MTP/MTP_Bluetooth_cal.acdb"
adb shell "su -c cp /sdcard/MTP_WCD9306_Bluetooth_cal.acdb /system/etc/acdbdata/MTP/msm8939-tapan-snd-card/MTP_WCD9306_Bluetooth_cal.acdb"
adb shell "su -c cp /sdcard/MTP_Bluetooth_cal_ZD550KL.acdb /system/etc/acdbdata/MTP/ZD550KL/MTP_Bluetooth_cal_ZD550KL.acdb"
adb shell "su -c cp /sdcard/MTP_Bluetooth_cal_ZE550KL.acdb /system/etc/acdbdata/MTP/ZE550KL/MTP_Bluetooth_cal_ZE550KL.acdb"
adb shell "su -c cp /sdcard/MTP_Bluetooth_cal_ZE600KL.acdb /system/etc/acdbdata/MTP/ZE600KL/MTP_Bluetooth_cal_ZE600KL.acdb"
adb shell "su -c cp /sdcard/QRD_Bluetooth_cal.acdb /system/etc/acdbdata/QRD/QRD_Bluetooth_cal.acdb"
adb shell "su -c cp /sdcard/QRD_SKUL_Bluetooth_cal.acdb /system/etc/acdbdata/QRD/msm8939-snd-card-skul/QRD_SKUL_Bluetooth_cal.acdb"
adb shell "su -c cp /sdcard/bt_did.conf /system/etc/bluetooth/bt_did.conf"
adb shell "su -c cp /sdcard/bt_stack.conf /system/etc/bluetooth/bt_stack.conf"
adb shell "su -c cp /sdcard/android.hardware.bluetooth.xml /system/etc/permissions/android.hardware.bluetooth.xml"
adb shell "su -c cp /sdcard/android.hardware.bluetooth_le.xml /system/etc/permissions/android.hardware.bluetooth_le.xml"
adb shell "su -c cp /sdcard/init.qcom.bt.sh /system/etc/init.qcom.bt.sh"
adb shell "su -c cp /sdcard/libbluetooth_jni.so /system/lib/libbluetooth_jni.so"
adb shell "su -c cp /sdcard/bluetooth.default.so /system/lib/hw/bluetooth.default.so"
adb shell "su -c cp /sdcard/libbt-vendor.so /system/vendor/lib/libbt-vendor.so"
adb shell "su -c cp /sdcard/libbtnv.so /system/vendor/lib64/libbtnv.so"
# Set Permission Of New Files (Should Be Finished, Not tested)
adb shell "su -c chmod 644 /system/app/Bluetooth/Bluetooth.apk"
adb shell "su -c chmod 644 /system/app/BluetoothExt/BluetoothExt.apk"
adb shell "su -c chmod 644 /system/app/BluetoothMidiService/BluetoothMidiService.apk"
adb shell "su -c chmod 644 /system/bin/btnvtool"
adb shell "su -c chmod 644 /system/bin/btsnoop"
adb shell "su -c chmod 644 /system/etc/acdbdata/MTP/MTP_Bluetooth_cal.acdb"
adb shell "su -c chmod 644 /system/etc/acdbdata/MTP/msm8939-tapan-snd-card/MTP_WCD9306_Bluetooth_cal.acdb"
adb shell "su -c chmod 644 /system/etc/acdbdata/MTP/ZD550KL/MTP_Bluetooth_cal_ZD550KL.acdb"
adb shell "su -c chmod 644 /system/etc/acdbdata/MTP/ZE550KL/MTP_Bluetooth_cal_ZE550KL.acdb"
adb shell "su -c chmod 644 /system/etc/acdbdata/MTP/ZE600KL/MTP_Bluetooth_cal_ZE600KL.acdb"
adb shell "su -c chmod 644 /system/etc/acdbdata/QRD/QRD_Bluetooth_cal.acdb"
adb shell "su -c chmod 644 /system/etc/acdbdata/QRD/msm8939-snd-card-skul/QRD_SKUL_Bluetooth_cal.acdb"
adb shell "su -c chmod 644 /system/etc/bluetooth/bt_did.conf"
adb shell "su -c chmod 644 /system/etc/bluetooth/bt_stack.conf"
adb shell "su -c chmod 644 /system/etc/permissions/android.hardware.bluetooth.xml"
adb shell "su -c chmod 644 /system/etc/permissions/android.hardware.bluetooth_le.xml"
adb shell "su -c chmod 644 /system/etc/init.qcom.bt.sh"
adb shell "su -c chmod 644 /system/lib/libbluetooth_jni.so"
adb shell "su -c chmod 644 /system/lib/hw/bluetooth.default.so"
adb shell "su -c chmod 644 /system/vendor/lib/libbt-vendor.so"
adb shell "su -c chmod 644 /system/vendor/lib64/libbtnv.so"
shanetrainST said:
So I started today putting together a batch ADB file to test the CM version of the BT for joying
I have completely run out of time to finish it and I wont be able to complete it till next week, there is quite a bit to go on it and i am not even sure it works, so if anyone want to continue with it, u can.
The ADB Files are not my work and i don't take credit for it, I only added the files and made the batch
This work is not complete and SHOULD NOT BE USED in its current state.
Click to expand...
Click to collapse
Nice work.
However, I would start with simply replacing the bluetooth.apk first.
And then the bluetooth.apk, the libbluetooth_jni.so and the bluetooth.default.so
Or did you already try that?
Note also that the "libbt-vendor.so" is seemingly a vendor library. Maybe you still need the original from Joying for the specific Intel vendor bluetooth stuff. On the other hand: the CM-13 is not hardware specific, so maybe it is more cross-compatible.
Going to try that soon thanks for tips, had a bit of time on my lunch break.
new batch file that replaces the three files u mentioned.
If anyone want to test it, file attached
I take zero responsibility if anything happens to your unit
To undo if it don't work just use root browser to delete the new files and rename the old files.
View attachment BluetoothUpdate2.zip
BluetoothHalfUpdate.bat
Echo off
adb kill-server
adb connect %1
adb root
adb connect %1
adb push Bluetooth.apk /sdcard/
adb push libbluetooth_jni.so /sdcard/
adb push bluetooth.default.so /sdcard/
adb shell mount -o rw,remount /system
adb shell mount -o rw,remount /system /system
adb shell mount -o rw,remount /
adb shell mount -o rw,remount / /
adb shell "su -c mount -o remount,rw /system"
adb shell "su -c cp /system/Bluetooth/Bluetooth.apk /system/Bluetooth/Bluetooth.apk.old"
adb shell "su -c cp /system/Bluetooth/oat/x86/Bluetooth.odex /system/Bluetooth/oat/x86/Bluetooth.odex.old"
adb shell "su -c cp /system/Bluetooth/lib/libbluetooth_jni.so /system/Bluetooth/lib/libbluetooth_jni.so.old"
adb shell "su -c cp /system/lib/hw/bluetooth.default.so /system/lib/hw/bluetooth.default.so.old"
adb shell "su -c cp /sdcard/Bluetooth.apk /system/app/Bluetooth/Bluetooth.apk"
adb shell "su -c cp /sdcard/libbluetooth_jni.so /system/lib/libbluetooth_jni.so"
adb shell "su -c cp /sdcard/bluetooth.default.so /system/lib/hw/bluetooth.default.so"
adb shell "su -c chmod 644 /system/app/Bluetooth/Bluetooth.apk"
adb shell "su -c chmod 644 /system/lib/libbluetooth_jni.so"
adb shell "su -c chmod 644 /system/lib/hw/bluetooth.default.so"
adb reboot
Thanks guys for taking the time to fix it.
Have you tested just a little bit? It works?
Not having much luck with mine, also missed a line of command in the shell that I will add later that mounts it
Every time I get ADB shell root, it connects for about 2seconds then kick me off. I am on the latest July rom
Sent from my iPhone using Tapatalk
So I updated
Bluetooth.apk
(Strange that it didn't produce a Bluetooth.odex on reboot)
Libbluetooth-Jni.so
Bluetooth.default.so
When unit boot's up it shows that Bluetooth sharing has crashed, not sure how to fix it
Must need more files replaced, anyone know a android Bluetooth expert? Would help heaps
So far the BT is broken and won't power on and the Joying app cannot use it but...
Anyone remember was Bluetooth tethering in the menu? Pic attached
{
"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"
}
Sent from my iPhone using Tapatalk
That's difficult to understand this with my knowledge at the moment.:crying:
shanetrainST said:
So I updated
Bluetooth.apk
(Strange that it didn't produce a Bluetooth.odex on reboot)
Libbluetooth-Jni.so
Bluetooth.default.so
Click to expand...
Click to collapse
That is because the odex can't be written to the read-only /system on startup. So it will be written to /data/app like any downloaded app.
Most probably you will find it at /data/app/com.android.bluetooth/oat/x86/base.odex
For the rest I don't have an answer.
I might just put back the original Bluetooth.apk
Just swap the Bluetooth.default.so first
Sent from my iPhone using Tapatalk
This is probably a silly suggestion and already been tried but not seen anything on the joying threads... has anyone tried a Bluetooth tethering manager for the tethering side?
I use this for connecting my phone to a tablet in car.
Bluetooth tethering manager
https://play.google.com/store/apps/details?id=com.tomlocksapps.bluetoothtetheringmanager
Sent from my SM-G920F using Tapatalk
Merlous said:
This is probably a silly suggestion and already been tried but not seen anything on the joying threads... has anyone tried a Bluetooth tethering manager for the tethering side?
I use this for connecting my phone to a tablet in car.
Bluetooth tethering manager
https://play.google.com/store/apps/details?id=com.tomlocksapps.bluetoothtetheringmanager
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
I've used that app and although it works fine I found it to be a bit slow.
I found the app the @doitright wrote a lot faster and it works fine and it's free
https://forum.xda-developers.com/an...elopment/bluetooth-settings-launcher-t3504526
If you want to read more head to my Q&A : https://forum.xda-developers.com/an...ts/intel-sofia-to-micro-tutorials-qa-t3616074
instead of swapping out apk's
try firmware from another device. joying uses realtek rtl8723a/rtk8723
check out
~5009_60/system/vendor/etc/bluetooth
~5009_60/system/vendor/etc/firmware/bt
/nvm_fs_partition/bluetooth
/system/bin/bt_vendor_test
???
edit said:
I've used that app and although it works fine I found it to be a bit slow.
I found the app the @doitright wrote a lot faster and it works fine and it's free
https://forum.xda-developers.com/an...elopment/bluetooth-settings-launcher-t3504526
If you want to read more head to my Q&A : https://forum.xda-developers.com/an...ts/intel-sofia-to-micro-tutorials-qa-t3616074
Click to expand...
Click to collapse
Thought you probably had but better safe than sorry! Thanks will check that one out.
Following your thread for when I get mine but just delayed it. Was ordering the single din 8" with 5.0.1 on but then they announced the newer cooler running one but it's on 6 and no 8" yet... was hoping this July 7th update might have solved more. Don't really need Bluetooth calling as I have side mounted exhausts and too loud really to talk and it's only a sheet of aluminium between the stereo and the outside so in the sun it will get rather hot...
Worse case will end up WiFi tethering.
Sent from my SM-G920F using Tapatalk
gtxaspec said:
instead of swapping out apk's
try firmware from another device. joying uses realtek rtl8723a/rtk8723
check out
~5009_60/system/vendor/etc/bluetooth
~5009_60/system/vendor/etc/firmware/bt
/nvm_fs_partition/bluetooth
/system/bin/bt_vendor_test
???
Click to expand...
Click to collapse
Thanks for the info
In the Joying 6.0 running OS I find there is this firmware file
vendor/etc/firmware/bt
-A11.Pbn
In the Joying 5.1 rom zip I found
vendor/etc/firmware/bt
-A00.pbn
-A10.pbn
-A11.pbn
Could anyone confirm what firmware file the 5.1 is running on
Could be as simple as swapping the A11.pbn for one of the other two.
A00.pbn seems to have the largest file size?? Not sure if it might be a fully featured firmware for the Realtek BT or it could be because they are using a few different variations of the RTL8723A
Will test tonight
Sent from my iPhone using Tapatalk
Getting very close to working out why Bluetooth disconnect and reconnect on apps that make their own Bluetooth connections without the Joying app.
This might be helpful for inet truma box aswell if it suffers the same issue.
The original problem was it would disconnect the apps Bluetooth after 3 and the the app would have to reconnect/disconnect/reconnect and then it would work fine.
I have started to rename some of the sys/app/ files as apk.old
I started renaming one at a time and got board and renamed a heap.
End result is my BT stays connected now and the app don't disconnect after 3mins of usages.
I think Joying turns the BT off if there is no device paired/connected via their Joying app, and one of the system apps takes care of it.
Tonight I will go back through and work out the culprit.
This has been a few month battle for me trying to figure out this issues, so happy it's not a driver or a Android core apk causing this
Sent from my iPhone using Tapatalk
shanetrainST said:
Getting very close to working out why Bluetooth disconnect and reconnect on apps that make their own Bluetooth connections without the Joying app.
This might be helpful for inet truma box aswell if it suffers the same issue.
The original problem was it would disconnect the apps Bluetooth after 3 and the the app would have to reconnect/disconnect/reconnect and then it would work fine.
I have started to rename some of the sys/app/ files as apk.old
I started renaming one at a time and got board and renamed a heap.
End result is my BT stays connected now and the app don't disconnect after 3mins of usages.
I think Joying turns the BT off if there is no device paired/connected via their Joying app, and one of the system apps takes care of it.
Tonight I will go back through and work out the culprit.
This has been a few month battle for me trying to figure out this issues, so happy it's not a driver or a Android core apk causing this
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Interesting and well done hopefully, I would have been the same as you with the impatience lol.
Sent from my SM-G920F using Tapatalk
{
"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"
}
The following steps activate the Google Voice Search with Google Assistant so that it can be used in a current Kodi 18 Nightly Build on a Fire TV.
The tutorial assumes that an alternative launcher, e.g. AppStarter, is used because Amazon Alexa voice search is completely replaced by Google Assistant. Xposed edge and HDXPosed must also be installed and activated. Before installing it is recommended to make a backup of the system and data partition via TWRP if you have connected an external sdcard. Many thanks to @SimLynks for some tips from his PlayFire modification.
If you want to use the complete Leanback Launcher with integrated Chromecast, then have a look at my more comprehensive guide: Link
This manual is only possible with a rooted device!
Tested on a Fire TV 4k box
Firmware 5.2.6.2
Instructions:
Unpack all zip files and copy all apk in the appendix to C:\adb\
1. Disabling unnecessary and Google Voice Recognition blocking Amazon apps
Code:
adb shell su -c pm disable com.amazon.advertisingidsettings
adb shell su -c pm disable com.amazon.device.sale.service
adb shell su -c pm disable com.amazon.tv.legal.notices
adb shell su -c pm disable com.amazon.tv.nimh
adb shell su -c pm disable com.amazon.tv.settings/com.amazon.tv.settings.tv.AppDisableService
adb shell su -c pm uninstall -k --user 0 com.amazon.vizzini
(Notice: Disable com.amazon.vizzini works too, but I noticed that the app reactivates itself from time to time.)
2. Customize build.prop
View attachment mod-build.prop.zip
Code:
adb shell su -c mount -o remount,rw /system
adb push C:\adb\mod-build.prop.sh /sdcard/
adb shell su -c sh /sdcard/mod-build.prop.sh
adb shell su -c rm /sdcard/mod-build.prop.sh
adb shell su -c mount -o remount,ro /system
3. Adjust permissions for voice recognition
View attachment tv_core_hardware.zip
Code:
adb shell su -c mount -o remount,rw /system
adb push C:\adb\tv_core_hardware.xml /sdcard/
adb shell su -c cp /sdcard/tv_core_hardware.xml /system/etc/permissions/tv_core_hardware.xml
adb shell su -c chmod 644 /system/etc/permissions/tv_core_hardware.xml
adb shell su -c chown root:root /system/etc/permissions/tv_core_hardware.xml
adb shell su -c rm /sdcard/tv_core_hardware.xml
adb shell su -c mount -o remount,ro /system
4. Install Open Google apps for Android TV
(If you already have the Google Apps installed, you can skip this and the next section.)
Download the matching zip file and copy it to the sdcard.
Open GApps for ARM (Fire TV sticks)
Open GApps for ARM64 (Fire TV boxes)
Copy the customized gapps-config.txt to the same directory as the GApps on the sdcard.
View attachment gapps-config.txt
Then install the GApps zip via TWRP and restart the device. Please don't sign up for Google Play Store yet!
5. Allow Google registration (NoTouchAuthDelegate)
View attachment Tv-NoTouchGsf.apk
Code:
adb shell su -c mount -o remount,rw /system
adb push C:\adb\Tv-NoTouchGsf.apk /sdcard/
adb shell su -c chmod 755 /system/app/NoTouchAuthDelegate/
adb shell su -c rm /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk
adb shell su -c cp /sdcard/Tv-NoTouchGsf.apk /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk
adb shell su -c chmod 644 /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk
adb shell su -c chown root:root /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk
adb shell su -c rm /sdcard/Tv-NoTouchGsf.apk
adb shell su -c mount -o remount,ro /system
6. Install Google app to enable voice recognition (com.google.android.katniss)
Now restart the device and then sign in to Google Play Store. Attention, the Google Play Store is a system app and therefore only appears in the AppStarter if the display of system apps is activated. Alternatively you can use my modified conFIREator.
Then search for and install the "Google" app on the Play Store. It'll take a while.
(Notice: The search does not work with the search button on the remote!)
7. Adjust the Xposed edge key configuration for the search button of the Fire TV remote
Activate the "Keys" in the Xposed edge and add the new KEYCODE_SEARCH key (simply press the search key on the Fire Remote for recognition).
Use "Single Click" with the activity "com.google.android.katniss\.search.SearchActivity" and leave "Long press" empty. This is the standard function, you first have to click and release the microphone, wait until the input is ready ("Speak Now" appears), and then press and hold the microphone and speak again.
(Notice: Alternatively you also can only link the action "Long press" with the activity "com.google.android.katniss\.search.SearchActivity". Then you have everything at the touch of a button: activate and speak. You should try it the way you like it best.)
Reboot for the last time.
That's all and now you can start the voice search by pressing and holding the search button in Kodi.
Google Assistant also now finds hits in Kodi (movies, tv shows, music), along with other sources such as YouTube, if Kodi already is running.
Once you have installed the PlayFire TV settings, you can choose which apps the Google Assistant is allowed to search for hits.
(Notice: The activation of the detection can take up to 5 seconds in individual cases, but usually it is very fast. Just hold down the search button and wait. But this is also the case on an Android TV.)
.
I hereby discontinue support for my Fire TV Guides and Apps. I've been a big fan of Fire TV devices for the last 2-3 years, but Amazon has now with each firmware further limited the possibilities of a configurable Android environment and even destroyed standard Android commands. This goes too far for me now.
I can recommend the following devices to anyone who wants to have a reasonable and much better Android TV experience, which I now use myself and am enthusiastic about:
Mi Box
Mi Box S
Sony Android TV (ATV3 platform, eg. XF7, XF8, XF9 or higher)
Will be trying this tomorrow, thankyou
Awesome a new project for tomorrow. Thanks for all your hard work.
rainman74 said:
{
"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"
}
The following steps installs the newest Leanback Launcher with Recommendations, Chromecast integrated, Daydream and activates the Google Voice Search with Google Assistant so that it also can be used in a current Kodi 18 Nightly Build on a Fire TV.
This is the most comprehensive and up-to-date transformation of a Fire TV into an Android TV device with almost all Google functionalities usable.
Amazon TV Launcher and Amazon Alexa voice search are completely replaced by Leanback Launcher and Google Voice Search. Xposed edge, XInstaller and HDXPosed must also be installed and activated. Before installing it is recommended to make a backup of the system and data partition via TWRP if you have connected an external sdcard. Many thanks to @SimLynks for some tips from his PlayFire modification and to @peleg for his wonderful [project] aftv2atv.
This manual is only possible with a rooted device!
Tested on a rooted Fire TV 4k box
Firmware 5.2.6.2
Instructions:
Unpack all zip files and copy all apk in the appendix to C:\adb\
1. Disabling unnecessary and blocking Amazon junk
Code:
adb shell su -c pm disable amazon.jackson19
adb shell su -c pm disable com.amazon.acos.providers.UnifiedSettingsProvider
adb shell su -c pm disable com.amazon.advertisingidsettings
adb shell su -c pm disable com.amazon.ags.app
adb shell su -c pm disable com.amazon.application.compatibility.enforcer
adb shell su -c pm disable com.amazon.application.compatibility.enforcer.sdk.library
adb shell su -c pm disable com.amazon.avod
adb shell su -c pm disable com.amazon.bueller.music
adb shell su -c pm disable com.amazon.bueller.notification
adb shell su -c pm disable com.amazon.bueller.photos
adb shell su -c pm disable com.amazon.client.metrics
adb shell su -c pm disable com.amazon.client.metrics.api
adb shell su -c pm disable com.amazon.communication.discovery
adb shell su -c pm disable com.amazon.device.sale.service
adb shell su -c pm disable com.amazon.device.software.ota
adb shell su -c pm disable com.amazon.device.software.ota.override
adb shell su -c pm disable com.amazon.device.sync
adb shell su -c pm disable com.amazon.device.sync.sdk.internal
adb shell su -c pm disable com.amazon.imp
adb shell su -c pm disable com.amazon.kindle.cms
adb shell su -c pm disable com.amazon.kor.demo
adb shell su -c pm disable com.amazon.logan
adb shell su -c pm disable com.amazon.metrics.api
adb shell su -c pm disable com.amazon.ods.kindleconnect
adb shell su -c pm disable com.amazon.recess
adb shell su -c pm disable com.amazon.tahoe
adb shell su -c pm disable com.amazon.tcomm.client
adb shell su -c pm disable com.amazon.tv.csapp
adb shell su -c pm disable com.amazon.tv.launcher
adb shell su -c pm disable com.amazon.tv.launcher/.ui.HomeActivity_vNext
adb shell su -c pm disable com.amazon.tv.legal.notices
adb shell su -c pm disable com.amazon.tv.nimh
adb shell su -c pm disable com.amazon.tv.settings/com.amazon.tv.settings.tv.AppDisableService
adb shell su -c mount -o remount,rw /system
adb shell su -c rm -r /system/priv-app/com.amazon.vizzini
adb shell su -c rm -r /system/priv-app/WhisperplayCore
adb shell su -c rm -r /system/priv-app/WhisperplayInstall
adb shell su -c mount -o remount,ro /system
(Notice: Amazon Alexa and Wisperplay will be completely deleted to make room on the system partition for Chromecast Integrated.)
2. Customize build.prop
View attachment 4481935
Code:
adb shell su -c mount -o remount,rw /system
adb push C:\adb\mod-build.prop.sh /sdcard/
adb shell su -c sh /sdcard/mod-build.prop.sh
adb shell su -c rm /sdcard/mod-build.prop.sh
adb shell su -c mount -o remount,ro /system
3. Adjust permissions for voice recognition
View attachment 4481936
Code:
adb shell su -c mount -o remount,rw /system
adb push C:\adb\tv_core_hardware.xml /sdcard/
adb shell su -c cp /sdcard/tv_core_hardware.xml /system/etc/permissions/tv_core_hardware.xml
adb shell su -c chmod 644 /system/etc/permissions/tv_core_hardware.xml
adb shell su -c chown root:root /system/etc/permissions/tv_core_hardware.xml
adb shell su -c rm /sdcard/tv_core_hardware.xml
adb shell su -c mount -o remount,ro /system
4. Install Open Google apps for Android TV
Download the matching zip file and copy it to the sdcard (I use version open_gapps-arm64-5.1-tvstock-20180423).
Open GApps for ARM (Fire TV sticks)
Open GApps for ARM64 (Fire TV boxes)
Insert this code to new "gapps-config.txt" and copy it to the same directory as the GApps on the sdcard.
Code:
forceclean
skipswypelibs
skipvendorlibs
GoogleAssistant
+extsharedstock
+keyboardstock
+provision
+packageinstallerstock
+webviewstock
+notouchauthdelegate
Include
gappspico
backdrop
#castreceiver
configupdater
googlebackuptransport
googlecontactsync
gsfcore
leanbacklauncher
overscan
secondscreenauthbridge
secondscreensetup
tvcustomization
tvetc
tvframework
tvgmscore
tvkeyboardgoogle
tvvending
tvwallpaper
tvwidget
Then install the GApps zip via TWRP and restart the device. Please don't sign up for Google Play Store yet!
5. Allow Google registration (NoTouchAuthDelegate)
View attachment 4481943
Code:
adb shell su -c mount -o remount,rw /system
adb push C:\adb\Tv-NoTouchGsf.apk /sdcard/
adb shell su -c chmod 755 /system/app/NoTouchAuthDelegate/
adb shell su -c rm /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk
adb shell su -c cp /sdcard/Tv-NoTouchGsf.apk /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk
adb shell su -c chmod 644 /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk
adb shell su -c chown root:root /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk
adb shell su -c rm /sdcard/Tv-NoTouchGsf.apk
adb shell su -c mount -o remount,ro /system
6. Install Google app to enable voice recognition (com.google.android.katniss)
Now restart the device and then sign in to Google Play Store.
Then search for and install the "Google" app on the Play Store. It'll take a while (I use current Google 2.2.0.138699360).
(Notice: The search in the Play Store does not work with the search button on the remote!)
7. Adjust the Xposed edge key configuration for the search button of the Fire TV remote
Activate the "Keys" in the Xposed edge and add the new KEYCODE_SEARCH key (simply press the search key on the Fire Remote for recognition).
Use "Single Click" with the activity "com.google.android.katniss\.search.SearchActivity" and leave "Long press" empty. This is the standard function, you first have to click and release the microphone, wait until the input is ready ("Speak Now" appears), and then press and hold the microphone and speak, then release.
More useful key assignments for the Leanback Launcher see attached photos:
View attachment 4488212View attachment 4488213View attachment 4488214View attachment 4488215
8. Install Android TV Settings modified for Fire TV
Once you have installed the aftv2atv Fire TV settings (better than the modified settings apk from PlayFire), you can choose which apps the Google Assistant is allowed to search for hits.
View attachment 4488216
Code:
adb shell su -c mount -o remount,rw /system
adb push C:\adb\TvSettings-2.1.1.apk /sdcard/
adb shell su -c cp /sdcard/TvSettings-2.1.1.apk /system/priv-app/TvSettings/TvSettings.apk
adb shell su -c chmod 644 /system/priv-app/TvSettings/TvSettings.apk
adb shell su -c chown root:root /system/priv-app/TvSettings/TvSettings.apk
adb shell su -c rm /sdcard/TvSettings-2.1.1.apk
adb shell su -c mount -o remount,ro /system
9. Finish
Reboot for the last time.
That's all and now you will boot directly in Leanback Launcher and start the voice search by pressing the search button in Leanback Launcher and Kodi.
Google Assistant also now finds hits in Kodi (movies, tv shows and music, if Kodi already is running), along with other sources such as YouTube, Spotify, etc. (directly install these apps from Google Play Store)
10. Optional: Access Amazon settings
If you still need to access the Amazon settings, you can install my modified conFIREator Settings app additionally (More details click here):
View attachment 4488238
Known issues
Although the cast receivers are displayed and found correctly, no device could connect. Looks like Google has something here against unlicensed cast receivers.
.
Click to expand...
Click to collapse
After step 5 your guide says install the google app, when i log into google and search for the app it wont let me install it ? i get error code 0
sconnyuk said:
After step 5 your guide says install the google app, when i log into google and search for the app it wont let me install it ? i get error code 0
Click to expand...
Click to collapse
Did you already have an older version installed? Then simply uninstall them before.
rainman74 said:
Did you already have an older version installed? Then simply uninstall them before.
Click to expand...
Click to collapse
brand new install of latest fire tv2 rom. clean slate and following your guide.
---------- Post added at 05:12 PM ---------- Previous post was at 05:11 PM ----------
ive just tried again, im up to instaaling gapps and waiting on optomising
---------- Post added at 05:14 PM ---------- Previous post was at 05:12 PM ----------
rainman74 said:
Did you already have an older version installed? Then simply uninstall them before.
Click to expand...
Click to collapse
no, ive just formatted and installed latest rom (fire tv2) and folowing as a clean slate.
---------- Post added at 05:15 PM ---------- Previous post was at 05:14 PM ----------
rainman74 said:
Did you already have an older version installed? Then simply uninstall them before.
Click to expand...
Click to collapse
can you tell me what i need to do after step 5 ? it says install google app but it isnt included in your guide ? thanks
sconnyuk said:
can you tell me what i need to do after step 5 ? it says install google app but it isnt included in your guide ? thanks
Click to expand...
Click to collapse
then sideload Google App 2.2.0
rainman74 said:
then sideload Google App 2.2.0
Click to expand...
Click to collapse
its asking for decription key ?
sconnyuk said:
its asking for decription key ?
Click to expand...
Click to collapse
Link with key
rainman74 said:
Link with key
Click to expand...
Click to collapse
Thanks for all the help but after i install that and go sign into google store, search google and try install i get error code 0 again, no matter what i try install i get trhe same error code, any idea ?
sconnyuk said:
Thanks for all the help but after i install that and go sign into google store, search google and try install i get error code 0 again, no matter what i try install i get trhe same error code, any idea ?
Click to expand...
Click to collapse
Code:
adb shell
chown -R media_rw:media_rw /data/media/
find /data/media/ -type d -exec chmod 775 {} ‘;’
find /data/media/ -type f -exec chmod 664 {} ‘;’4)
rainman74 said:
Code:
adb shell
chown -R media_rw:media_rw /data/media/
find /data/media/ -type d -exec chmod 775 {} ‘;’
find /data/media/ -type f -exec chmod 664 {} ‘;’4)
Click to expand...
Click to collapse
Thanks, im restoring my backup at the moment, what will this code do ? i dont get any reccomendations and i cant see any setting icons on my home screen either, will this fix those issues too ?
sconnyuk said:
Thanks, im restoring my backup at the moment, what will this code do ? i dont get any reccomendations and i cant see any setting icons on my home screen either, will this fix those issues too ?
Click to expand...
Click to collapse
restoring permissions, that is a possible solution for Error 0
rainman74 said:
restoring permissions, that is a possible solution for Error 0
Click to expand...
Click to collapse
no, restoring my backup from twrp. im going to give it 3rd and final go see if i can get it working
sconnyuk said:
no, restoring my backup from twrp. im going to give it 3rd and final go see if i can get it working
Click to expand...
Click to collapse
Best luck! I have tested my guide on 4 Fire TVs... I've never got Error 0.
rainman74 said:
Best luck! I have tested my guide on 4 Fire TVs... I've never got Error 0.
Click to expand...
Click to collapse
Ok, so i seem to have got a littel further this time, i can now install from playstore and reccomendations work (sometimes) but, i cannot see any settings icon ? and obviously my original settings are disabled.
Also i cant see my sideloaded apps anywhere or even know where to access them from ? can you shed any light on this for me please ?
sconnyuk said:
Ok, so i seem to have got a littel further this time, i can now install from playstore and reccomendations work (sometimes) but, i cannot see any settings icon ? and obviously my original settings are disabled.
Also i cant see my sideloaded apps anywhere or even know where to access them from ? can you shed any light on this for me please ?
Click to expand...
Click to collapse
Is it possible that you have not configured XInstaller correctly? Please send me screenshots of your XPosed modules and one screenshot of each XInstaller area. If the settings do not appear at the bottom of the launcher, you have not installed the Settings.apk correctly. Please scroll down in the launcher and take a screenshot.
To access all apps, press and hold the Menu key, then the app bar opens with all (even the non-leanback) apps. To do this, however, you must have configured all keys as specified in Xposed edge.
rainman74 said:
Is it possible that you have not configured XInstaller correctly? Please send me screenshots of your XPosed modules and one screenshot of each XInstaller area. If the settings do not appear at the bottom of the launcher, you have not installed the Settings.apk correctly. Please scroll down in the launcher and take a screenshot.
To access all apps, press and hold the Menu key, then the app bar opens with all (even the non-leanback) apps. To do this, however, you must have configured all keys as specified in Xposed edge.
Click to expand...
Click to collapse
Yes I've not configured xinstaller as I can't find the app xinstaller to launch. I have managed to get as far as installing settings and running all commands but I do not see any settings. If there was a way to select xinstaller I might be able to progress?
sconnyuk said:
Yes I've not configured xinstaller as I can't find the app xinstaller to launch. I have managed to get as far as installing settings and running all commands but I do not see any settings. If there was a way to select xinstaller I might be able to progress?
Click to expand...
Click to collapse
Launch the Xposed Installer
- Click on the three lines in the top left corner of the screen
- Click on Modules
- Click the check box to activate XInstaller (use Mouse Toogle for Fire TV)
Restart the Fire TV
Launch the Xposed Installer again
- Click on Modules again
- Click on XInstaller
In XInstaller click on XInstaller first
- Check Expert mode
- Press the back arrow
In the Installations page, in the "Enable" section, check the boxes for:
- Downgrading apps
- Installing unknown apps
- Then scroll down to the "Disable" section and check the boxes for:
- Checking signatures
- Checking signatures (F-Droid)
- Forward locking
- Verifying apps
- Checking SDK version
- Checking duplicated permissions
- Press the back arrow
In the Misc page, in the "Enable" section, check the box for:
- Debugging apps
- Then scroll down to the "Disable" section and check the boxes for:
- Checking permissions
- Verifying JAR
- Verifying signatures
- Checking Lucky Patcher
- Auto updating Google Play
Exit the program
rainman74 said:
Launch the Xposed Installer
- Click on the three lines in the top left corner of the screen
- Click on Modules
- Click the check box to activate XInstaller (use Mouse Toogle for Fire TV)
Restart the Fire TV
Launch the Xposed Installer again
- Click on Modules again
- Click on XInstaller
In XInstaller click on XInstaller first
- Check Expert mode
- Press the back arrow
In the Installations page, in the "Enable" section, check the boxes for:
- Downgrading apps
- Installing unknown apps
- Then scroll down to the "Disable" section and check the boxes for:
- Checking signatures
- Checking signatures (F-Droid)
- Forward locking
- Verifying apps
- Checking SDK version
- Checking duplicated permissions
- Press the back arrow
In the Misc page, in the "Enable" section, check the box for:
- Debugging apps
- Then scroll down to the "Disable" section and check the boxes for:
- Checking permissions
- Verifying JAR
- Verifying signatures
- Checking Lucky Patcher
- Auto updating Google Play
Exit the program
Click to expand...
Click to collapse
Thanks for that, its working now.
I have recomendations come up correctly, i can see and use my settings now and its now setup better than i had previously.
One question, how to make my sideloaded apps show on the homescreen ? or isnt this possible ?
Thanks for your help and for putting this together.
Before starting I wanted to thank @Supersonic27543 for the tutorial to disable system apps in Fire Os 5.6.1.0 and @Monkeybomb365 for the tutorial to remove the lockscreen ads.
THIS IS ONLY FOR FIRE OS 5.6.1.0 AND UP, BUT YOU CAN TRY TO DO IT IN OTHER VERSIONS AND COMMENT IF IT HAS WORKED.
REQUISITES:- ADB DRIVERS INSTALLED
- USB CABLE
- COMPUTER
- com.amazon.unifiedsharefacebook.apk DOWNLOAD Only for 4th/5th/6th/7th gen Fires.
Fires 4th/5th/6th/7th gen:
1. Enable usb debugging and connect the fire to the computer.
2. Copy the file com.amazon.unifiedsharefacebook downloaded previously and copy it to the internal storage (sdcard0) of the fire.
3. Open a command prompt and type:
Code:
adb shell pm install -r -d /sdcard/com.amazon.unifiedsharefacebook.apk
4. Reboot the fire.
5. Connect the fire again and in command prompt type:
Code:
- adb shell
- run-as com.amazon.unifiedsharefacebook
- pm hide com.amazon.kindle.kso
- exit
7. Without disconnecting the fire from the computer type in command prompt:
Code:
- adb shell settings put global LOCKSCREEN_AD_ENABLED 0
- adb shell settings put global ksoHash 0
8. Restart the fire and enjoy a tablet without lockscreen ads.
Fires 8th/9th gen:
1. Download latest mtk-su from here (Thanks @diplomatic :victory
2. Copy arm/mtk-su to your ADB folder
3. Open a CMD
4. Push mtk-su:
Code:
adb push mtk-su /data/local/tmp/mtk-su
5. Chmod it:
Code:
adb shell chmod 755 /data/local/tmp/mtk-su
6. Open an adb shell:
Code:
adb shell
7. CD to data/local/tmp:
Code:
cd data/local/tmp
8. Get root shell:
Code:
./mtk-su
9. Disable ads:
Code:
pm disable com.amazon.kindle.kso
10. Reboot:
Code:
reboot
If you use linux do the same process but using the terminal instead of the command prompt.
IF IT HAS WORKED PRESS THE THANK BUTTON!
IF YOU DO NOT UNDERSTAND OR THERE ARE ERRORS COMMENT
This method also removes the special offers icon that appears in the lower corner of the lock screen.
I do not have the one on the camera because I have disabled it and I have replaced it with google camera:
{
"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"
}
Rortiz2 said:
Before starting I wanted to thank @Supersonic27543 for the tutorial to disable system apps in Fire Os 5.6.1.0 and @Monkeybomb365 for the tutorial to remove the lockscreen ads.
THIS IS ONLY FOR FIRE OS 5.6.1.0 AND UP, BUT YOU CAN TRY TO DO IT IN OTHER VERSIONS AND COMMENT IF IT HAS WORKED.
REQUISITES:- ADB DRIVERS INSTALLED
- USB CABLE
- COMPUTER
- com.amazon.unifiedsharefacebook.apk DOWNLOAD
- Settings Database Editor DOWNLOAD
1. Enable usb debugging and connect the fire to the computer.
2. Copy the file com.amazon.unifiedsharefacebook downloaded previously and copy it to the internal storage (sdcard0) of the fire.
3. Open a command prompt and type:
Code:
adb shell pm install -r -d /sdcard/com.amazon.unifiedsharefacebook.apk
4. Reboot the fire.
5. Connect the fire again and in command prompt type:
Code:
adb shell run-as com.amazon.unifiedsharefacebook pm hide com.amazon.kindle.kso
6. Without disconnecting the fire from the computer install Settings Database editor but do not open it.
7. Type in command prompt:
Code:
adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
8. Open Settings Data Base Editor and where it says System Table press it and select Global Table.
9. Find the line that says:
"LOCKSCREEN_AD_ENABLED" "1"
10. Click on it and select edit value. Delete 1 and set to 0.
11. Restart the fire and enjoy a tablet without lockscreen ads.
If you use linux do the same process but using e terminal instead of the command prompt.
IF IT HAS WORKED PRESS THE THANK BUTTON!
IF YOU DO NOT UNDERSTAND OR THERE ARE ERRORS COMMENT
Click to expand...
Click to collapse
This is brilliant. Before, changing LOCKSCREEN_AD_ENABLED value only worked for a short while because the KSO app would overwrite the value when it synced with the other amazon related settings. With the app 'hidden' you're actually tricking the system, and amazon into thinking the lock screen ads were 'legitimately' removed. Though the app is hidden, it can no longer sync the settings because it's services have been disabled. This may actually really piss Amazon off. However, they won't be able to fix it without a huge amount of trouble, money and resources. ?
....
at step 2, this is what i keep getting. i was able to do step 3, but afraid the ads will return as i dont think step 2 was completed properly. thoughts ?
C:\Users\MixXx K>adb shell pm install -r -d /sdcard/com.amazon.unifiedsharefacebook.apk
pkg: /sdcard/com.amazon.unifiedsharefacebook.apk
Success
C:\Users\MixXx K>adb shell run-as com.amazon.unifiedsharefacebook pm hide com.amazon.kindle.kso
run-as: Package 'com.amazon.unifiedsharefacebook' is not debuggable
C:\Users\MixXx K>adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
@DragonFire1024 Can't this trick be used with other Amazon apps?
Adyatan said:
@DragonFire1024 Can't this trick be used with other Amazon apps?
Click to expand...
Click to collapse
I don't understand what you mean.
mixxxk said:
at step 2, this is what i keep getting. i was able to do step 3, but afraid the ads will return as i dont think step 2 was completed properly. thoughts ?
C:\Users\MixXx K>adb shell pm install -r -d /sdcard/com.amazon.unifiedsharefacebook.apk
pkg: /sdcard/com.amazon.unifiedsharefacebook.apk
Success
C:\Users\MixXx K>adb shell run-as com.amazon.unifiedsharefacebook pm hide com.amazon.kindle.kso
run-as: Package 'com.amazon.unifiedsharefacebook' is not debuggable
C:\Users\MixXx K>adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
---------- Post added at 07:19 AM ---------- Previous post was at 07:18 AM ----------
at step 2, this is what i keep getting. i was able to do step 3, but afraid the ads will return as i dont think step 2 was completed properly. thoughts ?
C:\Users\MixXx K>adb shell pm install -r -d /sdcard/com.amazon.unifiedsharefacebook.apk
pkg: /sdcard/com.amazon.unifiedsharefacebook.apk
Success
C:\Users\MixXx K>adb shell run-as com.amazon.unifiedsharefacebook pm hide com.amazon.kindle.kso
run-as: Package 'com.amazon.unifiedsharefacebook' is not debuggable
C:\Users\MixXx K>adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
---------- Post added at 07:21 AM ---------- Previous post was at 07:19 AM ----------
at step 2, this is what i keep getting. i was able to do step 3, but afraid the ads will return as i dont think step 2 was completed properly. thoughts ?
C:\Users\MixXx K>adb shell pm install -r -d /sdcard/com.amazon.unifiedsharefacebook.apk
pkg: /sdcard/com.amazon.unifiedsharefacebook.apk
Success
C:\Users\MixXx K>adb shell run-as com.amazon.unifiedsharefacebook pm hide com.amazon.kindle.kso
run-as: Package 'com.amazon.unifiedsharefacebook' is not debuggable
C:\Users\MixXx K>adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
Click to expand...
Click to collapse
@mixxxk What version of fire os are you using?
You have copied the apk in the internal memory (sdcard0)?
Adyatan said:
@DragonFire1024 Can't this trick be used with other Amazon apps?
Click to expand...
Click to collapse
@Adyatan Yes, here is a script that hides all amazon apps:
https://mega.nz/#!mtUVgYAL!q5svMvzgpkcH04B21UBc71KZ4m0Nex6lSw7liQljBO8
Sorry, xda was down this morning, didn't realize it posted that over and over.
I'm using 5.6.2.0
And yes, copied directly.
Rortiz2 said:
@mixxxk What version of fire os are you using?
You have copied the apk in the internal memory (sdcard0)?
Click to expand...
Click to collapse
mixxxk said:
Sorry, xda was down this morning, didn't realize it posted that over and over.
I'm using 5.6.2.0
And yes, copied directly.
Click to expand...
Click to collapse
mmm... What fire you have? HD10? HD8? 7 2015? 7 2017?
Duplicated Comment
HD8 2017
Rortiz2 said:
mmm... What fire you have? HD10? HD8? 7 2015? 7 2017?
Click to expand...
Click to collapse
Worked nicely on 5.4.0.0 on Fire 7 (2017, 7th Gen), thanks!
Sasco1st said:
Worked nicely on 5.4.0.0 on Fire 7 (2017, 7th Gen), thanks!
Click to expand...
Click to collapse
You can still disable system apps on 5.4.0.0.
Sent from my Amazon Jem using XDA Labs
mixxxk said:
HD8 2017
Click to expand...
Click to collapse
It seems that in the fire hd8 2017 running Fire OS 5.6.2.0 this method does not work.
Please report it in this forum:
https://forum.xda-developers.com/hd8...-t3820744/amp/
404 Page Not Found
Rortiz2 said:
It seems that in the fire hd8 2017 running Fire OS 5.6.2.0 this method does not work.
Please report it in this forum:
https://forum.xda-developers.com/hd8...-t3820744/amp/
Click to expand...
Click to collapse
mixxxk said:
at step 2, this is what i keep getting. i was able to do step 3, but afraid the ads will return as i dont think step 2 was completed properly. thoughts ?
C:\Users\MixXx K>adb shell pm install -r -d /sdcard/com.amazon.unifiedsharefacebook.apk
pkg: /sdcard/com.amazon.unifiedsharefacebook.apk
Success
C:\Users\MixXx K>adb shell run-as com.amazon.unifiedsharefacebook pm hide com.amazon.kindle.kso
run-as: Package 'com.amazon.unifiedsharefacebook' is not debuggable
C:\Users\MixXx K>adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
Click to expand...
Click to collapse
Same problem with Fire HD 10 (7th generation)
OS 5.6.2.0
jb17112 said:
Same problem with Fire HD 10 (7th generation)
OS 5.6.2.0
Click to expand...
Click to collapse
The HD 10 can be rooted. No need to use this method when you can delete the appropriate packages.
Sent from my Amazon Jem using XDA Labs
DragonFire1024 said:
The HD 10 can be rooted. No need to use this method when you can delete the appropriate packages.
Click to expand...
Click to collapse
Root isn't for everyone, especially those using apps that detect root and abort (banking, games, licensed/streaming content, payment, etc.). There are clever workarounds for those who enjoy the 80/20 rule: 80% managing device, 20% using for intended purpose. All my devices have root (and usually bootloader) permissions but I understand the consequences and use other gizmos for restricted content. Choose your poison wisely.
mixxxk said:
404 Page Not Found
Click to expand...
Click to collapse
Try reinstalling the apk unifiedsharefacebok and then in command prompt type:
adb shell id
If the "id" command output *does not* start with "uid=2000" you can disable system apps but if the output is uid 2000 you can not disable system apps.