Hey there!
Today I decided to turn an old Raspberry Pi 4B 8GB I had lying around into an Android TV box. I used this guide to install it, and it installed smoothly. There were no apps on it whatsoever, so I wanted to download the Play Store to download at least YouTube. After a bit of searching on the LineageOS website I came across a link to the Android TV 13 GApps (from here). I flashed them as the instructions stated on the website with the image, however after finishing the setup I get a (fairly nice) picture instead of a regular home screen. What gives?! If possible, I would prefer to stay on ATV 13.
{
"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"
}
Exact file I downloaded
Thanks in advance.
EDIT: same issue on adrod 12
EDIT 2: seems to be an issue with the new version of MindTheGapps for ATV. downloading an older version worked perfectly
I have that same problem, anyone has done this right?
kanoeyes said:
I have that same problem, anyone has done this right?
Click to expand...
Click to collapse
see edit of original message
The method provided by TYK can solve this problem for you:
1. Download 7-Zip and Notepad++.
2. Open the MinTheGapps 13.0.0 .zip file with 7-Zip and drag out "update-binary".
3. Use Notepad++ to modify "update-binary" and confirm that it is in UNIX format.
4. Drag "update-binary" back into the .zip file (overwrite it).
Fix "update-binary":
Code:
...
ui_print "Copying files"
cp --preserve=a -r ./system/* "${SYSTEM_OUT}/"
if [ -n "$PRODUCT_BLOCK" ]; then
cp --preserve=a -r ./product/* /product
fi
if [ -n "$SYSTEM_EXT_BLOCK" ]; then
cp --preserve=a -r ./system_ext/* /system_ext
fi
##########
#Add:
##########
ui_print "Copying product files to ${SYSTEM_OUT}/product"
cp --preserve=a -r ./product/* "${SYSTEM_OUT}/product/"
ui_print "Copying system_ext files to ${SYSTEM_OUT}/system_ext"
cp --preserve=a -r ./system_ext/* "${SYSTEM_OUT}/system_ext/"
##########
rm -rf "${SYSTEM_OUT}/product/priv-app/TVLauncherNoGMS"
rm -rf "${SYSTEM_OUT}/product/priv-app/TVRecommendationsNoGMS"
rm -rf "${SYSTEM_OUT}/priv-app/PackageInstaller"
...
Of course, you can also directly use the modified file provided by him：https://disq.us/url?url=https://drive.google.com/file/d/1sVUGlXqF1-DCQg-cyZkSf-XVkIAL9tlB/view?usp=sharing:rgW_nThP7DCNHw3tZ0-5anGky44&cuid=4806155
More processing progress：https://disq.us/url?url=https://forum.xda-developers.com/t/dev-rom-unofficial-lineageos-20-android-13-for-raspberry-pi-4-b.4516545/page-3#post-88042215:ftUqKcH_-Lhh-deaaDACyIjSOdU&cuid=4806155
This may be related to the limitation of lineageos.
Related
After searching about how to change their icon in the toolbar (battery, signal icon) and I finally succeeded in GAZZY. me and the results are quite satisfactory.
Well this time I'll share a little way here,
previous first download icon here
1. Open CMD and Dir to the position of ADB located.
2. Type the command adb pull / system / framework / framework-res.apk C: /
C: / means to file its framework-ress.apk akasi in the copy on drive C, please see the file does not exist or if there is further to the next.
3. Extrack file icon that you have downloaded earlier into any place,
4. Open-framework res.apk with winrar / winzip but not in Extrack, then please go to the framework directory-res.apk \ res \ drawable-ldpi there will be seen there are a lot of image file format. Png is as an icon on the Toolbar GAZZY.
{
"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"
}
5. after that ADD file icon. png which had been downloaded into that directory res \ drawable-ldpi
6. after that you can close windows winrar / winzip you,
7. In an GAZZY still connected to the PC type the command from CMD
THIS TYPE
adb devices (to see if GAZZY already connected or not)
adb push-res.apk framework / sdcard
adb shell
$ Su / / if it is a hash mark just skip this
# Mount-o remount, rw-t yaffs2 / dev/block/mtdblock4 / System (Enter)
# Mv / system / framework / framework-res.apk / system / framework / framework-res.apkq (Enter)
# Cat / sdcard / framework-res.apk> / system / framework / framework-res.apk (Enter)
# Reboot (Enter)
Click to expand...
Click to collapse
8. See the results
Failure is not my responsibility, please be careful
tutorial By cyber campus
Can one of the authors of the 3 themes that have been made for the XOOM grace the community with a quick down and dirty howto?
What Scripts are needed?
What tools do you use?
Steps to open APK
Steps to repackage APK
Do we need to sign it? If so how?
Before I get flamed:
I have google'ed and there are allot of tutorials for others devices but I would like to see a tried and true method for the XOOM - with the current state of things (backup options) I am not feeling very adventurous so I would rather get some info from those whom have it down and a good process, Ideally this would get sticky so we would have a point of reference for future authors.
So if you have a few mins. today can you jot down the steps above and we can start to compile a nice howto?
Thanks,
----- My trial and errors -----
I will do a small modification to the SystemUI.apk to change the 3 icons on the bottom left launcher.
** Assumptions: Reader is using a Intel Mac, and has SDK and mac ports installed.
Download APKManager as suggested
Install SOX - for mac
Code:
sudo port install sox
APK Manager only comes in two flavors that I found, Windows and Linux, take the Linux one and build any other packages we might need
Code:
sudo port install p7zip
sudo port install optipng
Remove supplied optipng and aapt tools as they were compile for linux and are in ELF format so we can't exec them but we have our own now.
create a directory to work from
Code:
mkdir mytheme
Copy the script and the other fold in to your workspace:
Code:
cp -r Script.sh other ../mytheme
Enter your workspace and extract SystemUI.apk
Code:
cd ../mytheme
don't forget to make Script.sh and stuff other executable
chmod +x (or 755) Script.sh
chmod +x (or 755) -R other/*
./Script.sh
choose option 0
type: /system/app/SystemUI.apk
choose option 1
open a new tab
cd ../mytheme
cd out
Now you have a extracted / decompiled version of the systemui.apk that you can modify.
More to come...
Modify SystemUI.
Download APKManager. It is pretty self explanatory.
Okay,
So I finished my theme tutorial and as the post above stated it was very simple to follow along, I will update the first post and finish off the tutorial so others can learn,
Here is an image of my finial change, I used some icons from Gnome to change the 3 bottom left buttons as I think the theme shipped w/ xoom is good just those darn buttons are not very good looking.
Shot:
{
"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"
}
Those icons look really slick...
Sent from my Nexus S using XDA App
njstisforall said:
Those icons look really slick...
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Thanks,
Here is the SystemUI.apk
MD5 (SystemUI.apk) = 8c998de760fa36bd7b447538f48dc96c
first time distributing so backup yours just in case I did it wrong
adb pull /system/app/SystemUI.apk .
adb push ~/Downloads/SystemUI.apk /system/app/
Cheers,
where do I do this step:
Remove supplied optipng and aapt tools as they were compile for linux and are in ELF format so we can't exec them but we have our own now.
I figured it out
Hi!
I used a few days with much pleasure the Huawei MediaPad X1, imported from HK.
Framework I use on my Galaxy Note 2 beaucou with satisfaction. But can not be installed on the X1.
Here are two screenshot, albeit in French.
If someone has an idea, thank you in advance.
Note that I've ticked the box to accept the unknown sources.
{
"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"
}
Try this version (FAQ, post #7):
http://forum.xda-developers.com/showthread.php?p=52292102
Also make sure to read post #8 once you install the framework successfully, since you're using a Huawei device.
Ok I'll see it in effect. Thank you
EDIT
I don't know how to disable the resources API in the Xposed Installer settings.
And content of Number 8 link is not reassuring. I would not make fatal error or transform my new toy in gasworks.
HI, look the shot,
Files already exists.
Fone rooted???
Ask here
Xposed FAQ / Known issues
elpabar said:
Ok I'll see it in effect. Thank you
EDIT
I don't know how to disable the resources API in the Xposed Installer settings.
And content of Number 8 link is not reassuring. I would not make fatal error or transform my new toy in gasworks.
Click to expand...
Click to collapse
Open the Xposed installed, go to "Settings" and tap "Disable resource hooks".
blogodoblogodo said:
...
Fone rooted???
...
Click to expand...
Click to collapse
As I said, I used it on my Galaxy Note 2.
GermainZ said:
Open the Xposed installed, go to "Settings" and tap "Disable resource hooks".
Click to expand...
Click to collapse
Thanks! I checked this box, and it makes no difference unfortunately.
elpabar said:
I checked this box, and it makes no difference unfortunately.
Click to expand...
Click to collapse
Did you try installing the framework via your (custom) recovery?
Never tried it, and am not very comfortable with the recovery mode.
I do not even know operate on this model which button during startup.
Hi, I use 7d-504l.
I succed to be enable to activate xposed .
For Xposed Framework ver2.5.1 limited.
I use su ,onboot script by SManager as,
#!/system/bin/sh
mount -o rw,remount /system
chattr -i -R /system
rm /system/set_immutable.list
chattr -i /system/buld.prop
chattr -i /system/bin/app_process
chattr -i /system/bin/app_process.orig
I confirmed to work the latest version of GravityBox,Xblast,advanced power management7.0a.
Sent from my MediaPad X1 7.0
I correct , because of build.prop misspelled.
#!/system/bin/sh
mount -o rw,remount /system
chattr -i -R /system
rm /system/set_immutable.list
chattr -i /system/build.prop
chattr -i /system/bin/app_process
chattr -i /system/bin/app_process.orig
Hi everyone,
I wanna build old version of Xposed, for Android SDK 16-19, then have tried to compile Xposed fw for hundreds time but still failed.
Environment: Ubuntu 15.10 x64 | tools: JDK 1.6, libc6 ....
AOSP: JZO54L / android-4.1.2_r2 /Jelly Bean ("make app_process" have been run successfully).
My steps:
- Download AOSP into /opt/android/aosp
- XposedBridge.jar: Download Xposed Installer here repo[dot]xposed[dot]info/module/de.robv.android.xposed.installer and detach jar from apk. Put it to /opt/out/java
- Download XposedTools source from github into /opt/xposed/ then make build.conf file:
Quote:
[General]
outdir = /opt/out
[Build]
# Please keep the base version number and add your custom suffix
version = 58
# makeflags = -j4
[GPG]
sign = release
user = 852109AA!
# Root directories of the AOSP source tree per SDK version
[AospDir]
16 = /opt/android/aosp
# SDKs to be used for compiling BusyBox
# Needs github[dot]com/rovo89/android_external_busybox
[BusyBox]
- To integrate Xposed to AOSP, I tried following 2 ways in the instruction (local manifest and manual cloning)
+ local manifest: link [XposedTools]/local_manifests/xposed_sdk16.xml to [aosp]/.repo/local_manifests/ then run repo sync.
+ manual cloning: remove [aosp]/build; clone github[dot]com/rovo89/platform_build/ to replace; clone github[dot]com/rovo89/Xposed into [aosp]/framework/base/cmds/xposed
- Go back to [XposedTools] and run ./build -t x86:16
>>output: cd /opt/android/aosp && . build/envsetup.sh >/dev/null && lunch full_x86-user >/dev/null && make -j4 TARGET_CPU_SMP=true xposed
The result I received is a big "app_process_xposed" file (~ 270-350 KBs), it size is as many times as the origin app_process file (~20 KBs). I think there are somethings wrong. I open them by 7z and see some differences:
{
"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"
}
I may did some mistakes in these steps. Could you please give me any advice?
Thank so much!
{
"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"
}
Introduction:
After I see official support for LineageOS 18.1 for Xiaomi Mi 10T / Mi 10T Pro / Redmi K30S Ultra and try Flashing instructions I success install LineageOS 18.1 on my Xiaomi Mi 10T phone. (Thanks to @SebaUbuntu and @Ramyski )
My next step is to install microG from NanoDroid with Magisk, but this ROM use Android 11 and need to manual make Signature Spoofing for microG.
Before start to make Signature Spoofing package I use:
Xiaomi Mi 10T/PRO device
USB cable
Computer
Tools on Linux (adb,unzip,zip,java 11)
Steps for make Signature Spoofing package:
1. Open linux console pressing CTRL+ALT+T and make working directory
Bash:
mkdir spoof_pkg
cd spoof_pkg
2. Download haystack-11-attempt, DexPatcher-tool and NanoDroid-microG.
Bash:
wget https://gitlab.com/oF2pks/haystack/-/archive/11-attempt/haystack-11-attempt.zip
wget https://github.com/DexPatcher/dexpatcher-tool/releases/download/v1.8.0-beta1/dexpatcher-1.8.0-beta1.jar
wget https://downloads.nanolx.org/NanoDroid/Stable/NanoDroid-microG-23.1.2.20210117.zip
3. Setup build environment
Bash:
unzip haystack-11-attempt.zip
mv haystack-11-attempt build
cp dexpatcher-1.8.0-beta1.jar build
cd build
4. Connect phone with USB and pull file services.jar
Bash:
adb pull /system/framework/services.jar
5. Run Dex Pathcher
Bash:
java -jar dexpatcher-1.8.0-beta1.jar -a 11 -M -v -d -o ./ services.jar 11-hook-services.jar.dex 11core-services.jar.dex
zip -u services.jar classes*.dex
6. Rebuild package spoof_AVDapi30.zip
Bash:
cp -f "spoof_AVDapi30.zip.ONLY'MAGISK&ANDROID-STUDIO" ../spoof_AVDapi30.zip
mkdir -p system
mkdir -p system/framework
cp services.jar system/framework/
zip -u ../spoof_AVDapi30.zip system/framework/services.jar
cd ..
Instalation of Magisk modules on phone:
1. Copy Magisk modules (NanoDroid-microG-23.1.2.20210117.zip and repacked package spoof_AVDapi30.zip ) on Phone internal memory (eg. Download)
NanoDroid-microG-23.1.2.20210117.zip
spoof_AVDapi30.zip (repacked for Mi 10T)
2. Finally start Magisk and under Modules add first NanoDroid-microG then reboot phone. After reboot phone start Magisk and add module spoof_AVDapi30.zip and restart phone.
Result on my phone is :
Enjoy in signature spoofing on Xiaomi Mi 10T.
Thanks, I'm waiting for official lineageos build from microg...
laolang_cool said:
Thanks, I'm waiting for official lineageos build from microg...
Click to expand...
Click to collapse
Great news, You can download lineageos build with mircog.
Link: apollon. Enjoy
war4head said:
Great news, You can download lineageos build with mircog.
Link: apollon. Enjoy
Click to expand...
Click to collapse
Thank you for the info, yes I have noticed it, but the building would have nfc and cpu issue at that time when building, so I will wait for the next build.
And switching to different rom on apollo is a real pain for me, since I need to backup and format the whole data partition...