Related
Ok, first off, the email app is busted, fixed is included in the rooting instructions. MobileAP is now MIA. No icons on the launcher at boot. There is also a sweet new app that is like DeskClock. Its snappy.
Firmware: (Flash to anything JI6 First if you are not on it already)
http://www.ponack.net/designgears/I897_JJ4_JF6_JJ4_JJ4_UC_ATT_designgears.zip
Custom kernel:
http://forum.xda-developers.com/showthread.php?t=825025
Root Kit & Email fix:
http://www.ponack.net/designgears/jj4_root_emailfix.zip
Enjoy and thank Chainfire for hooking us up!
This is NOT available on samfirmware.com
HowTo root:
Downlad & extract jj4_root_emailfix.zip
Browse to contents from cmd/terminal
adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
adb shell
cd /data/local/tmp
chmod 0755 rageagainstthecage-arm5.bin
./rageagainstthecage-arm5.bin
(wait for you to get kicked from adb)
adb shell
mount -o rw,remount /dev/block/stl9 /system
exit
adb push su /system/bin/su
adb push busybox /system/bin/busybox
adb push sqlite3 /system/bin/sqlite3
adb push superuser.apk /system/app/superuser.apk
adb shell
cd /system/bin
chmod 4755 su
chmod 4755 busybox
chmod 4755 sqlite3
mount -o rw,remount /dev/block/stl9 /system
/system/bin/busybox --install -s /system/xbin
busybox chmod -R 0755 /system/xbin
reboot now
Click to expand...
Click to collapse
{
"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"
}
thank you sir
Thanks DG and Chainfire!! I was wondering when we would get another leak.
DG, when you releasing a new beta? I love version 9.1.3
Also, do we know of any other change logs from J16? (I'm sure we will find them out soon enough)
Thanks for this!! I'll try when i fix mine!
Gr8Danes said:
Thanks DG and Chainfire!! I was wondering when we would get another leak.
DG, when you releasing a new beta? I love version 9.1.3
Also, do we know of any other change logs from J16? (I'm sure we will find them out soon enough)
Click to expand...
Click to collapse
Seems mostly like bug fixes, more stripping out features for AT&T, this build is smoother, but seems hacked together in comparison to how clean JI6 was.
designgears said:
Seems mostly like bug fixes, more stripping out features for AT&T, this build is smoother, but seems hacked together in comparison to how clean JI6 was.
Click to expand...
Click to collapse
I think I will leave it to your hands to give us the best of both worlds.
Thanks DG!
let me fill this out so it's at least 10 characters
Kaik541 said:
oh, and since I've never been ungrateful of your stuff and I'm not one to be rude when something drops in my lap, let me say thank you. I'd enjoy it a bit more though if you could stop trying to stir up drama so much about something as trivial as a phone, haha
Click to expand...
Click to collapse
Kaik541, trying to turn me into the bad guy while you talk trash me and anything I do, is, well, childish...
You are done. (as in I am bringing in a mod to deal with your crap)
Not going to waist my time flashing this, the last one had some pretty nasty bugs, it was stable yes but a bit buggy, besides this one seems to be missing stuff, il stick with JPM until official comes around.
btw:kaik541 just add him to your ignore list, thats what i did last time >;D
thanks for the release, what method is this one supposed to be flashed with? odin or?
Thank you as always DG! Any changes to GPS? Will the next Cog be built with this?
so will this be used for future builds or will we be sticking with the previous beta release?
cant get anything to go am now doing a master clear
HI DG,
I am trying this out but I cant get very far, I was able to root and sideload with superoneclick, everything wants to FC, phone, messaging, yp mobile, ect... so I am reflashing with repartition selected (this was a REAL Bad idea) cant mount dbdata ectect, now flashing back to stock. THanks cant wait till COG X
huzzah JJ4!
InsaneJester17 said:
Thank you as always DG! Any changes to GPS? Will the next Cog be built with this?
Click to expand...
Click to collapse
GPS is the same, as for building Cognition on this, not sure... building it right now to see how it runs.
buddy17 said:
so will this be used for future builds or will we be sticking with the previous beta release?
Click to expand...
Click to collapse
not sure yet
mattbeau said:
HI DG,
I am trying this out but I cant get very far, I was able to root and sideload with superoneclick, everything wants to FC, phone, messaging, yp mobile, ect... so I am reflashing with repartition selected (this was a REAL Bad idea) cant mount dbdata ectect, now flashing back to stock. THanks cant wait till COG X
Click to expand...
Click to collapse
Ya, one-click root may not work with this... That is why I posted the tried and true manual way...
thanks DG!
A revolutionary leader LOL
ok no prob, i think I will try again later.
Thanks
@designgears: This should work with your CogKernel right?
Have you released your kernel as a separate ODIN flashable tar?
designgears said:
Downlad & extract jj4_root_emailfix.zip
Browse to contents from cmd/terminal
adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
adb shell
cd /data/local/tmp
chmod 0755 rageagainstthecage-arm5.bin
./rageagainstthecage-arm5.bin
(wait for you to get kicked from adb)
adb shell
mount -o rw,remount /dev/block/stl9 /system
exit
adb push su /system/bin/su
adb push busybox /system/bin/busybox
adb push sqlite3 /system/bin/sqlite3
adb push superuser.apk /system/app/superuser.apk
adb push EmailProvider.db /data/data/com.android.email/databases/EmailProvider.db
adb shell
mount -o rw,remount /dev/block/stl9 /system
/system/bin/busybox --install -s /system/xbin
cd /system/bin
chmod 4755 su
chmod 4755 busybox
chmod 4755 sqlite3
chmod 4755 /data/data/com.android.email/databases/EmailProvider.db
busybox chmod -R 0755 /system/xbin
reboot
Click to expand...
Click to collapse
I had to change up the steps a little but was able to get everything to work:
Downlad & extract jj4_root_emailfix.zip
Browse to contents from cmd/terminal
adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
adb shell
cd /data/local/tmp
chmod 0755 rageagainstthecage-arm5.bin
./rageagainstthecage-arm5.bin
(wait for you to get kicked from adb)
adb shell
mount -o rw,remount /dev/block/stl9 /system
exit
adb push su /system/bin/su
adb push busybox /system/bin/busybox
adb push sqlite3 /system/bin/sqlite3
adb push superuser.apk /system/app/superuser.apk
adb push EmailProvider.db /sdcard/EmailProvider.db
adb shell
mount -o rw,remount /dev/block/stl9 /system
cd /system/bin
chmod 4755 su
chmod 4755 busybox
chmod 4755 sqlite3
/system/bin/busybox --install -s /system/xbin
cp /sdcard/EmailProvider.db /data/data/com.android.email/databases/EmailProvider.db
chmod 4755 /data/data/com.android.email/databases/EmailProvider.db
busybox chmod -R 0755 /system/xbin
reboot
phone fc?
went back to jf6 OC... then put tar in pda slot and flashed w/o repartition.
As soon as it boots up, I get FC on phone... continuously..
am I doing something wrong?
SOLVED! Thanks to Alex240188
Alex240188 said:
here is what i have done and just tested as working
If you are using Supersu binaries ignore this step
***PHONE***
Apps > Settings > Developer Options > Root Access > Apps and ADB
***PC Command Prompt***
adb shell
su
***PHONE***
confirm SU popup on phone
*** PC Command Prompt***
Ctrl + C (to exit shell)
adb root
Code:
restarting adbd as root
adb shell
mount -o remount,rw /system
mount
look for this line (it will tell you if you have failed or successfully remounted)
Failed
Code:
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 [b][u]ro[/u][/b],seclabel,relatime,data=ordered 0 0
Success
Code:
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 [b][u]rw[/u][/b],seclabel,relatime,data=ordered 0 0
CTRL + C to exit from shell
adb push "yourfile.ext" /system/"whereyouwanttoputit"/
in my case
adb push test.txt /system/app/
{
"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"
}
after this initial setup and working point, all you should have to do to future mount as RW in adb is the following 2 commands
adb root
adb shell mount -o remount,rw /system
then when your finished
adb shell mount -o remount,ro /system
Click to expand...
Click to collapse
-------------------------------------------------------------------------------------------------------------------------------------
I have a problem making my windows 8 PC write on the /system partition of the nexus 4.
I've tried all of these:
Code:
***adb remount.... FAIL
***adb shell (enter)
mount (enter)
(saw where the system partition is located)
mount -o rw,remount /dev/block/mmcblk0p21 /system....FAIL
***mount -o rw,remount /dev/block/platform/msm_sdcc.1/by-name/system /system... FAIL
***adb root... FAIL
***called my mother and told her that she wasn't lying to me
The mount -o.... commands do make the system writable, but only on phone and not via PC.
"mount" gives me that /system is rw, but i still can't push files to /system so that means i can only modify /system from the phone itself (or from adb shell), so when i enter the shell, /system is mounted, but when i exit the shell, /system isn't mounted
What i want to do is to make "adb push (bla) /system" work, without going to recovery, nor shell.
I can give details if needed.
Thank you.
Try putting the phone into recovery mode first. Then run:
Code:
adb remount
adb push blahblah.bla /system/
Chromium_ said:
Try putting the phone into recovery mode first. Then run:
Code:
adb remount
adb push blahblah.bla /system/
Click to expand...
Click to collapse
thanks for reminding me... i've added in OP that i don't want to be in recovery, i want to do it while the phone is booted.
Sent from my Nexus 4
so anyone?
Riro Zizo said:
so anyone?
Click to expand...
Click to collapse
here is what i have done and just tested as working
If you are using Supersu binaries ignore this step
***PHONE***
Apps > Settings > Developer Options > Root Access > Apps and ADB
***PC Command Prompt***
adb shell
su
***PHONE***
confirm SU popup on phone
*** PC Command Prompt***
Ctrl + C (to exit shell)
adb root
Code:
restarting adbd as root
adb shell
mount -o remount,rw /system
mount
look for this line (it will tell you if you have failed or successfully remounted)
Failed
Code:
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 [b][u]ro[/u][/b],seclabel,relatime,data=ordered 0 0
Success
Code:
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 [b][u]rw[/u][/b],seclabel,relatime,data=ordered 0 0
CTRL + C to exit from shell
adb push "yourfile.ext" /system/"whereyouwanttoputit"/
in my case
adb push test.txt /system/app/
after this initial setup and working point, all you should have to do in the future to mount as RW is the following 2 commands
adb root
adb shell mount -o remount,rw /system
then you can
adb push blah.apk /system/app/
adb push bootanimation.zip /system/media/
then when your finished
adb shell mount -o remount,ro /system
Thanks a TON! I wouldn't have lived without doing that! I should put that in OP now...
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
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.
{
"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"
}
This guide almost halves the battery consumption on a Samsung Galaxy Tab S3/S4 with Android 8.0.
Compared for example with a Google Pixel C, the battery on a Samsung Galaxy Tab reduces significantly faster due to some unnecessary apps from Samsung and a questionable and very comprehensive tracking of user data.
This tutorial is very careful with deactivating apps and only covers the absolutely crucial apps. Other tutorials remove significantly more apps, but this has no effect on battery consumption.
Hint: Operating the Galaxy Tab S3 under Android 8 is highly recommended as the performance is 25%-50% faster than under Android 7.
1. Install the following Google apps to later remove the sluggish and battery consuming Samsung apps:
Gmail
Contacts
Clock
Calculator
2. Disable the following packages, which consume battery unnecessarily:
Code:
adb shell su -c pm disable com.samsung.android.app.clockpack
adb shell su -c pm disable com.samsung.android.calendar
adb shell su -c pm disable com.samsung.android.contacts[I] (* If you want to use the phone dialer, then don't disable this package!)[/I]
adb shell su -c pm disable com.samsung.android.email.provider
adb shell su -c pm disable com.samsung.android.providers.context
adb shell su -c pm disable com.samsung.android.rubin.app
adb shell su -c pm disable com.samsung.android.voc
adb shell su -c pm disable com.sec.android.app.clockpackage
adb shell su -c pm disable com.sec.android.app.popupcalculator
adb shell su -c pm disable com.sec.android.app.sbrowser
adb shell su -c pm disable com.sec.spp.push
3. Optional: Remove remaining bloatware
Code:
adb shell su -c pm disable com.android.providers.partnerbookmarks
adb shell su -c pm disable com.microsoft.office.excel
adb shell su -c pm disable com.microsoft.office.onenote
adb shell su -c pm disable com.microsoft.office.powerpoint
adb shell su -c pm disable com.microsoft.office.word
adb shell su -c pm disable com.samsung.android.ststub
adb shell su -c pm disable com.samsung.android.knox.containeragent
adb shell su -c pm disable com.samsung.android.knox.containercore
adb shell su -c pm disable com.samsung.knox.securefolder
adb shell su -c pm disable com.samsung.knox.securefolder.setuppage
adb shell su -c pm disable com.sec.enterprise.knox.attestation
adb shell su -c pm disable com.sec.enterprise.knox.cloudmdm.smdms
adb shell su -c pm disable com.sec.enterprise.mdm.services.simpin
adb shell su -c pm disable com.sec.enterprise.mdm.vpn
4. Optional: Disable more unnecessary apps
Code:
adb shell su -c pm disable com.sec.android.app.kidshome
adb shell su -c pm disable com.sec.android.emergencylauncher
adb shell su -c pm disable com.sec.android.widgetapp.samsungapps
adb shell su -c pm disable com.sec.android.widgetapp.webmanual
adb shell su -c pm disable com.sec.musicstudio
If anyone has any further tips, please contact me.
Thanks, rainman. May I ask, which app you are using above?
corwin_amber said:
Thanks, rainman. May I ask, which app you are using above?
Click to expand...
Click to collapse
It's GSam Battery Monitor Pro
Can't do this with unrooted devices right? Since it uses "su -c"?
Anyway "adb shell su -c pm disable" doesn't work on my Tab S3.
Tried "pm uninstall -k --user 0 <name of package>" and it works but it uninstalls it though.
Package Disabler pro for Samsung
Hi,
Same Problem with unrooted device here. Can not disable the mentioned apps by using adb from my computer. Completely uninstalling is a bit risky I guess.
Found an app called Package Disabler Pro for Samsung instead. Works on unrooted stock devices and disables every app you want. Just tick the checkbox near to it. If you can not find the mentioned packages by name use the search function on top.
Works great, but you have to pay for it. For me it is worth that.
https://play.google.com/store/apps/details?id=com.elmklmsamsung.batteryaddon
Edit: Read on another place that Samsung AASA Service has to be disabled running oreo. Works for me.
Every app from the OP can be disabled with this command, no root necessary: $ pm disable-user --user 0 PACKAGENAME
You find more here: https://forum.xda-developers.com/galaxy-tab-s3/how-to/debloat-unbloat-tab-s3-android-8-0-0-t3906338
ItsOnlyMeAgain said:
Hi,
Same Problem with unrooted device here. Can not disable the mentioned apps by using adb from my computer. Completely uninstalling is a bit risky I guess.
Click to expand...
Click to collapse
Possibly unrelated question..
My understanding is that if you uninstall an app, that modifies the /system partition, which would then fire dm-verity on next boot.
I also am at a loss as how the app can be truly uninstalled with the /system partition read only.
So does "pm uninstall..." actually uninstall on an unrooted device?
Thanks in advance for any clarification here.
-Pie