Installing OpenGAPPs inside Lineage OS android emulator 17.1 - General Questions and Answers

Hi, I am trying to install opengapps on lineage os android emulator 17.1
I followed the instruction at https://wiki.lineageos.org/emulator.html and built lineage_x86-64-eng and lineage_x86-eng.
I started the emulator with -writable-system and have root adb shell, but when I downloaded the 17.1 OpenGAPPs version and try to run the install.sh script provided, it fails with errors.
Any guide on how to do this? All the guides I have found requires a real phone where you login into TWRP recovery mode, which I read the android emulator does not have.

Look inside here:
Install GApps Manually
groups.google.com

The folder is completely different in that link than what I get with the opengapps zip file. For instance I extract the opengapps I get the following below: There is no folder structure like so only apks. I tried to install the apk with adb install and some of them give errors like:
[INSTALL_PARSE_FAILED_NO_CERTIFICATES: Failed to collect certificates from /data/app/vmdl1550377932.tmp/base.apk: META-INF/CERT.SF indicates /data/app/vmdl1550377932.tmp/base.apk is signed using APK Signature Scheme v2, but no such signature was found. Signature stripped?]
Am I supposed to unzip the apks manually and do adb push the folders I get doing so?
Code:
.
./zip-x86
./GApps
./GApps/dialerframework-common
./GApps/dialerframework-common/common
./GApps/dialerframework-common/common/etc
./GApps/dialerframework-common/common/etc/sysconfig
./GApps/dialerframework-common/common/etc/sysconfig/dialer_experience.xml
./GApps/dialerframework-common/common/etc/permissions
./GApps/dialerframework-common/common/etc/permissions/com.google.android.dialer.support.xml
./GApps/dialerframework-common/common/framework
./GApps/dialerframework-common/common/framework/com.google.android.dialer.support.jar
./GApps/packageinstallergoogle-all.tar.lz
./GApps/calsync-all.tar.lz
./GApps/dialerframework-common.tar.lz
./GApps/googletts-x86
./GApps/googletts-x86/nodpi
./GApps/googletts-x86/nodpi/app
./GApps/googletts-x86/nodpi/app/GoogleTTS
./GApps/googletts-x86/nodpi/app/GoogleTTS/GoogleTTS.apk
./GApps/calsync-all
./GApps/calsync-all/nodpi
./GApps/calsync-all/nodpi/app
./GApps/calsync-all/nodpi/app/GoogleCalendarSyncAdapter
./GApps/calsync-all/nodpi/app/GoogleCalendarSyncAdapter/GoogleCalendarSyncAdapter.apk
./GApps/googletts-x86.tar.lz
./GApps/packageinstallergoogle-all
./GApps/packageinstallergoogle-all/nodpi
./GApps/packageinstallergoogle-all/nodpi/priv-app
./GApps/packageinstallergoogle-all/nodpi/priv-app/GooglePackageInstaller
./GApps/packageinstallergoogle-all/nodpi/priv-app/GooglePackageInstaller/GooglePackageInstaller.apk
./open_gapps-x86-10.0-pico-20210515.zip
./gapps-remove.txt
./g.prop
./app_sizes.txt
./app_densities.txt
./LICENSE
./busybox-x86
./tar-x86
./Optional
./Optional/swypelibs-lib-x86.tar.lz
./Core
./Core/googlebackuptransport-all
./Core/googlebackuptransport-all/nodpi
./Core/googlebackuptransport-all/nodpi/priv-app
./Core/googlebackuptransport-all/nodpi/priv-app/GoogleBackupTransport
./Core/googlebackuptransport-all/nodpi/priv-app/GoogleBackupTransport/GoogleBackupTransport.apk
./Core/googlefeedback-all
./Core/googlefeedback-all/nodpi
./Core/googlefeedback-all/nodpi/priv-app
./Core/googlefeedback-all/nodpi/priv-app/GoogleFeedback
./Core/googlefeedback-all/nodpi/priv-app/GoogleFeedback/GoogleFeedback.apk
./Core/setupwizarddefault-x86.tar.lz
./Core/configupdater-all.tar.lz
./Core/backuprestore-all.tar.lz
./Core/googlecontactssync-all
./Core/googlecontactssync-all/nodpi
./Core/googlecontactssync-all/nodpi/app
./Core/googlecontactssync-all/nodpi/app/GoogleContactsSyncAdapter
./Core/googlecontactssync-all/nodpi/app/GoogleContactsSyncAdapter/GoogleContactsSyncAdapter.apk
./Core/defaultframework-common
./Core/defaultframework-common/common
./Core/defaultframework-common/common/etc
./Core/defaultframework-common/common/etc/permissions
./Core/defaultframework-common/common/etc/permissions/com.google.android.media.effects.xml
./Core/defaultframework-common/common/etc/permissions/com.google.android.maps.xml
./Core/defaultframework-common/common/framework
./Core/defaultframework-common/common/framework/com.google.android.maps.jar
./Core/defaultframework-common/common/framework/com.google.android.media.effects.jar
./Core/googlepixelconfig-common.tar.lz
./Core/setupwizarddefault-x86
./Core/setupwizarddefault-x86/nodpi
./Core/setupwizarddefault-x86/nodpi/priv-app
./Core/setupwizarddefault-x86/nodpi/priv-app/SetupWizard
./Core/setupwizarddefault-x86/nodpi/priv-app/SetupWizard/SetupWizard.apk
./Core/googlefeedback-all.tar.lz
./Core/setupwizardtablet-x86.tar.lz
./Core/carriersetup-all
./Core/carriersetup-all/nodpi
./Core/carriersetup-all/nodpi/priv-app
./Core/carriersetup-all/nodpi/priv-app/CarrierSetup
./Core/carriersetup-all/nodpi/priv-app/CarrierSetup/CarrierSetup.apk
./Core/gsfcore-all
./Core/gsfcore-all/nodpi
./Core/gsfcore-all/nodpi/priv-app
./Core/gsfcore-all/nodpi/priv-app/GoogleServicesFramework
./Core/gsfcore-all/nodpi/priv-app/GoogleServicesFramework/GoogleServicesFramework.apk
./Core/carriersetup-all.tar.lz
./Core/googlepartnersetup-all.tar.lz
./Core/gmscore-x86
./Core/gmscore-x86/nodpi
./Core/gmscore-x86/nodpi/priv-app
./Core/gmscore-x86/nodpi/priv-app/PrebuiltGmsCore
./Core/gmscore-x86/nodpi/priv-app/PrebuiltGmsCore/PrebuiltGmsCore.apk
./Core/vending-x86
./Core/vending-x86/nodpi
./Core/vending-x86/nodpi/priv-app
./Core/vending-x86/nodpi/priv-app/Phonesky
./Core/vending-x86/nodpi/priv-app/Phonesky/Phonesky.apk
./Core/setupwizardtablet-x86
./Core/setupwizardtablet-x86/nodpi
./Core/setupwizardtablet-x86/nodpi/priv-app
./Core/setupwizardtablet-x86/nodpi/priv-app/SetupWizard
./Core/setupwizardtablet-x86/nodpi/priv-app/SetupWizard/SetupWizard.apk
./Core/googlepixelconfig-common
./Core/googlepixelconfig-common/common
./Core/googlepixelconfig-common/common/etc
./Core/googlepixelconfig-common/common/etc/sysconfig
./Core/googlepixelconfig-common/common/etc/sysconfig/nexus.xml
./Core/googlepixelconfig-common/common/etc/sysconfig/pixel_experience_2017.xml
./Core/googlepixelconfig-common/common/etc/sysconfig/pixel_experience_2018.xml
./Core/googlepixelconfig-common/common/etc/sysconfig/pixel_2018_exclusive.xml
./Core/googlecontactssync-all.tar.lz
./Core/googleonetimeinitializer-all
./Core/googleonetimeinitializer-all/nodpi
./Core/googleonetimeinitializer-all/nodpi/priv-app
./Core/googleonetimeinitializer-all/nodpi/priv-app/GoogleOneTimeInitializer
./Core/googleonetimeinitializer-all/nodpi/priv-app/GoogleOneTimeInitializer/GoogleOneTimeInitializer.apk
./Core/extsharedgoogle-all.tar.lz
./Core/configupdater-all
./Core/configupdater-all/nodpi
./Core/configupdater-all/nodpi/priv-app
./Core/configupdater-all/nodpi/priv-app/ConfigUpdater
./Core/configupdater-all/nodpi/priv-app/ConfigUpdater/ConfigUpdater.apk
./Core/extservicesgoogle-all
./Core/extservicesgoogle-all/nodpi
./Core/extservicesgoogle-all/nodpi/priv-app
./Core/extservicesgoogle-all/nodpi/priv-app/GoogleExtServices
./Core/extservicesgoogle-all/nodpi/priv-app/GoogleExtServices/GoogleExtServices.apk
./Core/defaultetc-common.tar.lz
./Core/defaultetc-common
./Core/defaultetc-common/common
./Core/defaultetc-common/common/etc
./Core/defaultetc-common/common/etc/default-permissions
./Core/defaultetc-common/common/etc/default-permissions/opengapps-permissions-q.xml
./Core/defaultetc-common/common/etc/default-permissions/default-permissions.xml
./Core/defaultetc-common/common/etc/sysconfig
./Core/defaultetc-common/common/etc/sysconfig/google_build.xml
./Core/defaultetc-common/common/etc/sysconfig/google-hiddenapi-package-whitelist.xml
./Core/defaultetc-common/common/etc/sysconfig/google_exclusives_enable.xml
./Core/defaultetc-common/common/etc/sysconfig/google.xml
./Core/defaultetc-common/common/etc/permissions
./Core/defaultetc-common/common/etc/permissions/split-permissions-google.xml
./Core/defaultetc-common/common/etc/permissions/privapp-permissions-google.xml
./Core/defaultetc-common/common/etc/preferred-apps
./Core/defaultetc-common/common/etc/preferred-apps/google.xml
./Core/gmscore-x86.tar.lz
./Core/googleonetimeinitializer-all.tar.lz
./Core/extsharedgoogle-all
./Core/extsharedgoogle-all/nodpi
./Core/extsharedgoogle-all/nodpi/app
./Core/extsharedgoogle-all/nodpi/app/GoogleExtShared
./Core/extsharedgoogle-all/nodpi/app/GoogleExtShared/GoogleExtShared.apk
./Core/vending-x86.tar.lz
./Core/googlebackuptransport-all.tar.lz
./Core/backuprestore-all
./Core/backuprestore-all/nodpi
./Core/backuprestore-all/nodpi/priv-app
./Core/backuprestore-all/nodpi/priv-app/GoogleRestore
./Core/backuprestore-all/nodpi/priv-app/GoogleRestore/GoogleRestore.apk
./Core/gsfcore-all.tar.lz
./Core/googlepartnersetup-all
./Core/googlepartnersetup-all/nodpi
./Core/googlepartnersetup-all/nodpi/priv-app
./Core/googlepartnersetup-all/nodpi/priv-app/GooglePartnerSetup
./Core/googlepartnersetup-all/nodpi/priv-app/GooglePartnerSetup/GooglePartnerSetup.apk
./Core/defaultframework-common.tar.lz
./Core/datatransfertool-all
./Core/datatransfertool-all/nodpi
./Core/datatransfertool-all/nodpi/priv-app
./Core/datatransfertool-all/nodpi/priv-app/AndroidMigratePrebuilt
./Core/datatransfertool-all/nodpi/priv-app/AndroidMigratePrebuilt/AndroidMigratePrebuilt.apk
./Core/extservicesgoogle-all.tar.lz
./Core/datatransfertool-all.tar.lz
./bkup_tail.sh
./META-INF
./META-INF/MANIFEST.MF
./META-INF/com
./META-INF/com/google
./META-INF/com/google/android
./META-INF/com/google/android/updater-script
./META-INF/com/google/android/update-binary
./META-INF/CERT.RSA
./META-INF/CERT.SF
./unzip-x86
./installer.sh

Lineage OS 17.1 is based on Android 10.
Folder structure of OpenGApps for Android 10 is
{
"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"
}
How to install OpenGApps on Lineage OS is described in file updater-script located in folder /META-INF/com/google/android
Code:
ui_print(" ");
ui_print(" Gapps for Android 10");
ui_print(" By SagarMakhar");
ui_print(" ");
ui_print("- Mounting partitions.. ");
ifelse(is_mounted("/system_root"), unmount("/system_root"));
ifelse(is_mounted("/vendor"), unmount("/vendor"));
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system_root", "");
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/vendor", "/vendor", "");
ui_print("- Extracting files.. ");
package_extract_dir("system_root", "/system_root");
ui_print("- Setting up permissions.. ");
package_extract_file("permissions.sh", "/tmp/permissions.sh");
set_metadata_recursive("/tmp", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644);
run_program("/tmp/permissions.sh");
ui_print("- Unmounting partitions.. ");
run_program("/sbin/busybox", "umount", "/system_root");
run_program("/sbin/busybox", "umount", "/vendor");
ui_print("- Done ");
Simply transform these instructions into related ADB commands and run them.

Where did you get GAPPS-for-android-10 folder structure shown in that picture from?
The opengapps i downloaded from https://opengapps.org/ (pico edition x86) is nothing like that, there is a update-binary script basically just extract the busybox binaries to /tmp which runs the installer.sh which fails to initially run for me. The folder listing of what pico package has is shown in my above post.
There seems to be some sort of folder/permission difference with stock android and lineage I think because the script tries to write to folders that a stock emulator build of lineage_x86-eng does not have, /tmp being one, so I cannot run the script nor can I execute the commands manually because I still have permission denied issues even as root.
Is opengapps meant to really only work on some different android 10 distribution that is not lineage? I asked in #lineageos-dev and no answer.
Is there a way to remount / as writable? I can only seem to make /system writable, I think if I can get / to be writable, I can get the script to work.

Took the time to download OpenGApps - Android 10 ( Pico ) - for x86. Noticed that the package indeed has a completely different structure than shown above:
Anyway, assumed your emulator's Android is rooted, it should be possible to install this package without an Android recovery because the scripts provided aren't EDIFY coded.
Actually don't have the time to deal with it more closely. May be i can do it in the foreseeable future ...

I just cheated and used bluestacks emulator, this has google apps preinstalled with root access. Thanks for the help though.

On the URL below you will find a script that will install open gapps in a emulator AVD using opengapps' install script.
The script wraps the opengapps script and mounts the various images on your system and you modify it from a chroot. No need to use adb.
Tested from API28 to API31 (ie Android 9 to Android 12)
Requires linux & superuser priveleges. The script may be adapted to work also on MacOS if someone adapts some of the commands.
All information here:
Install OpenGApps In Android Emulator (up to API31 / android 12 / S)
Install OpenGApps In Android Emulator (up to API31 / android 12 / S) - Readme.md
gist.github.com

Related

[TOOL]QtADB (AndroidManager for Linux, Windows and MacOS)

hello,
QtADB is window app based on adb.it lets you to copy,remove etc your files and apps from PC and Android Phone
This app is under developing so be tolerant for any bug...
visit QtADB website: http://qtadb.wordpress.com/
Features:
1. File manager
-copying files and dirs between phone and computer
-removing files and dirs
-creating new dir
-and other
2. App manager
-installing apps
-removing apps
-creating backup of apps with data
-restoring backups of apps with data
3. Shell
-opens android shell
4. Screenshot
-take screenshot of your device
-save screenshot to png file
5. Fastboot
-flash bootloader, radio and recovery
-boot recovery
6. Recovery
-nandroid backup/restore
-wipe data
-flash rom
-wipe battery stats
-fix uid mismatches
7. Reboot
-to bootloader
-to recovery
-normal reboot
8. Settings
-set font used by app
-set starting paths (or remember paths on exit)
-and other
9. Automatically detects phone (device, fastboot and recovery mode)
it requires installed AndroidSDK and busybox on phone (so and root)
linux and macOS version reguires installed Qt libraries(libqtgui4, libqt4-declarative and libqt4-network 4.7 version)(install it from synaptic or some similar app)
if you have connected phone but the file list is empty run with root permisions:
1)adb kill-server
2)adb start-server
or:
create file:
gksudo gedit /etc/udev/rules.d/51-android.rules
and insert this line:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
Ive got HTC Magic with Cyan6 and im testing everything on this. QtADB should work with every phone with busybox
if you have any suggestions/questions or you found any bug please let me know
{
"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"
}
More screenshots on official site
I am not responsible for damage done to your phone while using QtADB.
DOWNLOAD FROM OFFICIAL SITE
Do You miss fome feature that QtADB doesn't have? please post Your idea here: http://qtadb.uservoice.com/forums/87039-general
[size=+2]DO YOU HAVE SOME PROBLEMS WITH QTADB? PLEASE READ FAQ FIRST[/size]
If You like QtADB please consider donation:
What language is the windows version written in? Are the libraries able to be referenced from VS?
both versions are in c++ and this is the one source code compiled under windows and linux. it requires Qt libraries for VS
ps.i would like to add some screenshots but i have no permissions:/
where do i put the librays stuff?? im confused.... nvm i think i got it...
ok it says my phones connected for like 5seconds.. then it tells me to connect my phone.??
Nice app thanks!
wow this is AWESOME! thank you!
Looking good! Android management apps are really coming out of the woodwork now
I've attached a screenshot of my own Android manager 'Spot'
Crashes when i try to access a directory on the phone. Win 7 x64 and HTC Desire.
At the beginning, it looks great to use, but then I tried to open any directory, it crashed and forced close
it crashes after 2 - 3 seconds after opening
Windows 7 Pro - HTC Magic 1.5 with Sens UI - official
Acidmax: i dont know why you are having this issues.maybe its because you are using 64bit system...(i will support 64bit when app will be done)
cryshop: what phone?what OS?is phone rooted?which dir are you trying to open (on sdcard/in system).give me something information
crysu_x: "it crashes" has many meanings...what do you see?what error is appearing?what busybox do you have?you have to be more specific
the new version with new upgrades and fixes is almost ready so be patient
Works great for what i've used it for so far. Thank you sir.
@7ymekk : I'm using Windows 7 32bit and rooted HTC Legend.
I tried to open /system folder on the phone.
you know what??if you want to use my app please wait couple of days...i will end my new version and if you'll have the same issue i'll investigate it
how do you install it with ubuntu?
download first attach from first post and install libqtgui4 from synaptic
Hi, this is giving me segfault. I have installed both Sdk and libqtgui4. when i run "adb devices" i can see my tattoo attached.
I run the app, it asks me for the sdk path , then i point it to the "tools" subfolder under the sdk folder and then it segfaults.
This occurs even if i run it with root privileges.
Am i doing anything wrong?
Thanks in advance
if you are expecting some help you have to be more specific! what distro, what phone...the more informations-the better
7ymekk said:
if you are expecting some help you have to be more specific! what distro, what phone...the more informations-the better
Click to expand...
Click to collapse
Oops,
I'm working under Ubuntu 10.04 with a htc tattoo phone.
maybe this evening i will upload new version with screenshots and a lot improvements so i recommend to wait a little if you still will have those problems i will look into this

[TOOL]QtADB (AndroidManager for Linux, Windows and MacOS)

hello,
QtADB is window app based on adb.it lets you to copy,remove etc your files and apps from PC and Android Phone
This app is under developing so be tolerant for any bug...
visit QtADB website: http://qtadb.wordpress.com/
Features:
1. File manager
-copying files and dirs between phone and computer
-removing files and dirs
-creating new dir
-and other
2. App manager
-installing apps
-removing apps
-creating backup of apps with data
-restoring backups of apps with data
3. Shell
-opens android shell
4. Screenshot
-take screenshot of your device
-save screenshot to png file
5. Fastboot
-flash bootloader, radio and recovery
-boot recovery
6. Recovery
-nandroid backup/restore
-wipe data
-flash rom
-wipe battery stats
-fix uid mismatches
7. Reboot
-to bootloader
-to recovery
-normal reboot
8. Settings
-set font used by app
-set starting paths (or remember paths on exit)
-and other
9. Automatically detects phone (device, fastboot and recovery mode)
it requires installed AndroidSDK and busybox on phone (so and root)
linux and macOS version reguires installed Qt libraries(libqtgui4 and libqt4-network 4.6.2 or 4.6.3 version)(install it from synaptic or some similar app)
if you have connected phone but the file list is empty run with root permisions:
1)adb kill-server
2)adb start-server
or:
create file:
gksudo gedit /etc/udev/rules.d/51-android.rules
and insert this line:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
Ive got HTC Magic with Cyan6 and im testing everything on this. QtADB should work with every phone with busybox
if you have any suggestions/questions or you found any bug please let me know
{
"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"
}
More screenshots on official site
I am not responsible for damage done to your phone while using QtADB.
DOWNLOAD FROM OFFICIAL SITE
If You like QtADB please consider donation:
This is really nice
Awesome! i've been searching for something that works on Linux!
Nice work!
Worth having to install all the QTlibs. Very nice app!
I'm glad You like it
from download page (official site):
Linux x86 version (updated October 17th 2010. requires Qt 4.7 libraries: libqtgui4 and libqt4-network)
it needs only those 2 libraries

[MOD] [APP] [HOW-TO] [ROM-CONFIGURATOR] Project Derp

*** Everything below this is User Information *** For Devs that want to know how to make their Rom ready for this read the second post ***
Download:
What it is?
You know the problem: You wanna flash a Custom Rom through CWM but you don´t like to do a Wipe, install this or install that feature. The solution for you is this application. It´s your decision what you want on your phone.
To be concrete: Make a hook on the things you want in your Rom, click on the generate button and flash your Rom through CWM. That´s it.
For now you can choose if you need:
... to Wipe your Device
... which kernel
... Swipe
... Samsung Apps
... Live Wallpapers
... Custom Sounds
HowTo:
1. Download & install "Galaxy SLC Rom Configurator"
2. Launch it and set your Values for your next Rom flash
3. Click on the Generate-File Button and ...
4. ... flash your favorite Rom through CWM
{
"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"
}
Supported Roms:
Sorry, for now there is no one. But it will change soon when the Devs read this post
Simply search for this image in your Fav Rom Thread
*** The Dev guide - HowTo include this feature to your Rom ***
The first thing you have to do is to create some new Folders in your flashable Rom.zip.
/romconfig/kernel/
/romconfig/samsung/
/romconfig/livewallpaper/
/romconfig/sounds/
/romconfig/fonts/
/romconfig/swype/
Click to expand...
Click to collapse
The updater-script (we will edit it later) will install the files within these folders when the user chose it in the Configurator App. This means for you: Place ALL Samsung apps in /romconfig/samsung/, all your extra fonts in /romconfig/fonts/ ... Delete all Samsung Apps in your normal /system/app or - like in our example - all Samsung apps will be installed, not depending on the user´s choice!
Especially the Samsung apps and the swype app must be readded after every upgrade of your Rom. For Example, your Rom was based on KPE and no on KPQ, you can´t use the Samsung Apps from KPE on KPQ. Ok?
A example folder structure is attached to this post, it´s usable for KPQ. You can place additional fonts you want in /romconfig/fonts/ the sounds you love in /romconfig/sounds/, your fav wallpaper in /romconfig/livewallpaper/. But DONT EDIT THE KERNELS!! OF COURSE YOU CAN CHANGE A STOCK KERNEL VERSION TO A NEWER ONE, CUSTOM KERNEL TO A NEWER ONE, BUT YOU CAN´T ADD MORE KERNELS THE USERS CAN NOT CHOOSE THEM WITHIN THE APP.
I had not the time to place kernels in the folders. So please:
/romconfig/kernel/stockkernel/ place the Stock Kernel
/romconfig/kernel/bamcustomkernel/ place Bam Custom kernel
/romconfig/kernel/teamutterchaos/ place Utterchaos Kernel
Keep the folders in mind, you have to place the paths in your updater-script later
If you want other stuff to be choosen (other Apps, other kernels...) in the App feal free to contact me
Next thing we have to modify is your Updater script. It´s very easy don´t panic. Just add the following lines in your code:
ifelse(
file_getprop("/sdcard/download/configfile.prop", "samsung.apps") == "true",
(
package_extract_dir("/romconfig/samsung", "/system/app");
),
( )
ifelse(
file_getprop("/sdcard/download/configfile.prop", "custom.sounds") == "true",
(
package_extract_dir("/romconfig/sounds", "/system/media/audio");
),
( )
ifelse(
file_getprop("/sdcard/download/configfile.prop", "extra.fonts") == "true",
(
package_extract_dir("/romconfig/fonts", "/system/fonts);
),
( )
ifelse(
file_getprop("/sdcard/download/configfile.prop", "live.wallpaper") == "true",
(
package_extract_dir("/romconfig/livewallpaper", "/system/app");
),
( )
ifelse(
file_getprop("/sdcard/download/configfile.prop", "app.swype") == "true",
(
package_extract_dir("/romconfig/swype", "/system/app");
),
( )
Click to expand...
Click to collapse
At the point where your kernel will be flashed
ifelse(
file_getprop("/sdcard/download/configfile.prop", "kernel.value1") == "true",
(
Place the code for flashing a Kernel here (Stock Kernel)
),
( )
ifelse(
file_getprop("/sdcard/download/configfile.prop", "kernel.value2") == "true",
(
Place the code for flashing a Kernel here (Team Utterchaos Kernel)
),
( )
ifelse(
file_getprop("/sdcard/download/configfile.prop", "kernel.value3") == "true",
(
Place the code for flashing a Kernel here (Bam Custom Kernel)
),
( )
Click to expand...
Click to collapse
And last but not least this where you want to wipe
ifelse(
file_getprop("/sdcard/download/configfile.prop", "wipe") == "true",
(
unmount("/system");
unmount("/datadata");
unmount("/cache");
unmount("/data");
run_program("/tmp/busybox", "mount", "-t", "auto", "/dev/block/stl9", "/system");
run_program("/tmp/busybox", "mount", "-t", "auto", "/dev/block/stl10", "/datadata");
run_program("/tmp/busybox", "mount", "-t", "auto", "/dev/block/stl11", "/cache");
run_program("/tmp/busybox", "mount", "-t", "auto", "/dev/block/mmcblk0p3", "/data");
),
(
unmount("/cache")
run_program("/tmp/busybox", "mount", "-t", "auto", "/dev/block/stl11", "/cache")
;
)
Click to expand...
Click to collapse
And the very last thing. To show your users that your Rom is moddable by this app place this picture somewhere in your Thread (Feel free to resize it):
If you have any problem (maybe my HowTo is bad at some times ) contact me via PM or post here. Any suggestions, contact me!
Reserved for future use
Awesome work brother
it's a good idea
thx fuss
another Nice work bro.....count Poseidon in...
Sent from my GT-I9003 using XDA App
I think for wiping we should format the partitions. But in your code there is only unmounting and mounting the partitions
As always, very good job, I think soon this will be a great app for more than our device
good job fuss
Nice work dude!! I knew we had to buy a phone to this guy!!
Thanks for the good effort, I would suggest that instead of "all samsung apps" it should list the samsung apps in sub menu so user can choose the apps selectively. Some samsung apps are indeed useful.
sgsI9003 said:
Thanks for the good effort, I would suggest that instead of "all samsung apps" it should list the samsung apps in sub menu so user can choose the apps selectively. Some samsung apps are indeed useful.
Click to expand...
Click to collapse
I allready PM fuss about that,and you are right maybe someone could make a new thread on the general section on what are the usefull samsung apps they want..Cause if all samsung apps+pre installed apps+custom sounds it will eat all the space on the phone...

[ROM][CM12.0] UNOFFICIAL CM12.0 for Tilapia

{
"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 is a preview of CM-12.0 built almost entirely from CM sources. The only thing I have done is merged the aosp device tree for lollipop into the cm-11.0 device tree because there isn't a branch in CM sources yet and a few modifications listed below in features.
Features
- Settings->About Phone->CyanogenMod updates uses wfhome.net servers (my builds)
Latest Build
-Nightly's are being built now.
Downloads
http://goo.gl/yb6G5N
Old Builds
http://goo.gl/3nST2x - Android File Host
Google Apps
http://forum.xda-developers.com/android/software/gapps-google-apps-flashable-package-t2930266
TWRP 2.8.3.0
http://teamw.in/project/twrp2/150
Known Issues
- Ensure the default APN is properly selected or it take longer for it to connect.
All changes can be viewed on the CyanogenMod gerrit except the device tree. Changes can be viewed on my github account until a cm-12.0 branch is created for our device.
Thanks to all who have developed CyanogenMod and TWRP as well as the device and kernel trees for the Nexus 7.
I'm using a modified version of @JulianXhokaxhiu CyanogenModOTA tools on my web server.
https://github.com/julianxhokaxhiu/CyanogenModOTA
Source
http://github.com/CyanogenMod
http://github.com/rjwil1086
many thanks . now downloading ,and i will feedback again.
rjwil1086 said:
- Mobile data is kinda slow and not working 100% of the time. I will investigate further tonight. Likely a RIL issue like the one I patched for AOSP.
Click to expand...
Click to collapse
I have another file rild-A5. Your file A9
getting stuck at boot image after google apps installed
Using Nexus 7 2012 mobile. installed rom but stops booting at boot animation. after i install google apps via twrp. any suggestions.
Thank You
mp3junkie said:
Using Nexus 7 2012 mobile. installed rom but stops booting at boot animation. after i install google apps via twrp. any suggestions.
Thank You
Click to expand...
Click to collapse
Mine did that once. I would try flashing CM12 without gapps first. If it boots then reboot into recovery and flash gapps. If that doesn't work, You may have to erase everything and reflash.
** DONT DO THIS UNLESS YOU CAN CONNECT TO YOUR PC AND ADB push or MTD mount in recovery **
I did the following when coming from CM11:
Code:
fastboot flash -w
fastboot format system
fastboot erase boot
then booted into recovery and copy the cm-12 zip and gapps zip back to the sdcard and flash.
pavik62 said:
I have another file rild-A5. Your file A9
Click to expand...
Click to collapse
Does your A5 rild work any better than the A9 compiled with CM-12? I just checked the rild fix I created for AOSP using Android 4.4.4 rild source and it says A9 just like the Android 5.0.1 rild source. I haven't tried flashing it over cm-12 yet. Not sure if it will improve it.
It didn't install through adb sideload. I had to push packages to tablet and to install through TWRP. Booted quite a long time for the first time but after that it works well. Works everything (or I didn't notice any not working things). A bit laggy though. But not too much.
infomenas said:
It didn't install through adb sideload. I had to push packages to tablet and to install through TWRP. Booted quite a long time for the first time but after that it works well. Works everything (or I didn't notice any not working things). A bit laggy though. But not too much.
Click to expand...
Click to collapse
I've noticed lollipop lags for a while then it eventually speeds up. I believe it has to do with the way the art compiler works.
great! I've been looking forward to this
Is it compatible with ann All-F2FS formated device though?
punshkin said:
great! I've been looking forward to this
Is it compatible with ann All-F2FS formated device though?
Click to expand...
Click to collapse
I don't think it is. I tried formatting data to f2fs and the tablet sat at the boot screen.
@rjwil1086 wow, I finally got myself to undertake a twelve-hour build time on my slowputer and start messing with cm device tree for tilapia and right after a first build I did find your thread good work, man, all thumbs up
@rjwil1086 thank you very much for share. Playing with the update script of your rom + using M-Kernel i was able to boot in a AllF2FS formated device. From a clean install it works like a charm at first boot!
@rjwil1086 thanks for make Lollipop version for tilapia. A question, size of system partition system is only 640MB is possible tu rise it? Actually I only have free 6,79MB with only Gapps installed. In i9300 version have no problem. Size of partition system is 1,20Gb
Enviado desde mi GT-I9300 mediante Tapatalk
thanks, the rom is fine
aneto said:
@rjwil1086 thank you very much for share. Playing with the update script of your rom + using M-Kernel i was able to boot in a AllF2FS formated device. From a clean install it works like a charm at first boot!
Click to expand...
Click to collapse
Nice, can you tell me what modifications you made to the ROM?
@rjwil1086 Thank you very much for make Lollipop version for tilapia. Could you support the operation on multirom?
taketans said:
Could you support the operation on multirom?
Click to expand...
Click to collapse
You can do it yourself by editing the update-script. Like this:
PHP:
assert(getprop("ro.product.device") == "tilapia" || getprop("ro.build.product") == "tilapia" || abort("This package is for device: tilapia; this device is " + getprop("ro.product.device") + "."););
#ifelse(is_mounted("/system"), unmount("/system"));
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "/system", "");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
set_metadata("/tmp/backuptool.sh", "uid", 0, "gid", 0, "mode", 0755);
set_metadata("/tmp/backuptool.functions", "uid", 0, "gid", 0, "mode", 0644);
run_program("/tmp/backuptool.sh", "backup");
unmount("/system");
#if is_mounted("/data") then
#package_extract_file("system/bin/otasigcheck.sh", "/tmp/otasigcheck.sh");
#package_extract_file("META-INF/org/cyanogenmod/releasekey", "/tmp/releasekey");
#set_metadata("/tmp/otasigcheck.sh", "uid", 0, "gid", 0, "mode", 0755);
#run_program("/tmp/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
#else
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/UDA", "/data", "");
package_extract_file("system/bin/otasigcheck.sh", "/tmp/otasigcheck.sh");
package_extract_file("META-INF/org/cyanogenmod/releasekey", "/tmp/releasekey");
set_metadata("/tmp/otasigcheck.sh", "uid", 0, "gid", 0, "mode", 0755);
run_program("/tmp/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
unmount("/data");
#endif;
Other lines should be left unchanged.
punshkin said:
Nice, can you tell me what modifications you made to the ROM?
Click to expand...
Click to collapse
Yes I can.
These are the 4 lines to find and replace in updater-script:
Code:
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "/system", "");
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/UDA", "/data", "");
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "/system", "");
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "/system", "");
And has to be replaced by:
Code:
run_program("/sbin/busybox", "mount", "/system");
run_program("/sbin/busybox", "mount", "/data");
run_program("/sbin/busybox", "mount", "/system");
run_program("/sbin/busybox", "mount", "/system");
In addition to modify updater-script is also necessary to flash a compatible All F2FS kernel like M-Kernel
All worked good, 3G no need RilFix, 3Mbits\sec. But not installed Minecraft, error! 0.10.4 version, and a few other..
Other exellent!
miracast
will be working miracast on CM12 in future?

[Guide] How to adb debug when "Revoke Usb Authorisation" not working

1. Use latest adb, download official here:
https://developer.android.com/studio/releases/platform-tools.html <-- "Adb devices" command to check the status
What I love to do is press "Start + R" paste this and press ok
%userprofile%\.android
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"
}
Copy and paste adbkey.pub to anywhere easy to work with you, rename it to "adb_keys"
Inside the zip there is the file contain "adb_keys", replace it. And flash it with twrp and you are done
https://goo.gl/apdvVj
Hi Doulc
I can't get this to work. I downloaded latest adb tools (version 27.0.1), copied, renamed, put into "adb keys updater.zip" and flashed with twrp. I still get:
Code:
C:\Users\bill>adb devices
List of devices attached
330080a7c356230b unauthorized
First I used existing key and it failed, so then I generated new keys:
Code:
C:\Users\bill>adb keygen %userprofile%\.android\adbkey
then again copied, renamed, put into "adb keys updater.zip" and flashed with twrp.
still doesn't work.
On my phone (Samsung J7-108 with latest axvy ROM-from yesterday, rooted with SuperSU) I only have 4 choices of how to connect USB to PC:
Transfer Files
Transfer Images
Connect a MIDI device
Charge this phone
default is "Transfer Files", but I also tried the other 3 options.
What do you suggest? PC is windows 10.
billeuze said:
Hi Doulc
I can't get this to work. I downloaded latest adb tools (version 27.0.1), copied, renamed, put into "adb keys updater.zip" and flashed with twrp. I still get:
Code:
C:\Users\bill>adb devices
List of devices attached
330080a7c356230b unauthorized
First I used existing key and it failed, so then I generated new keys:
Code:
C:\Users\bill>adb keygen %userprofile%\.android\adbkey
then again copied, renamed, put into "adb keys updater.zip" and flashed with twrp.
still doesn't work.
On my phone (Samsung J7-108 with latest axvy ROM-from yesterday, rooted with SuperSU) I only have 4 choices of how to connect USB to PC:
Transfer Files
Transfer Images
Connect a MIDI device
Charge this phone
default is "Transfer Files", but I also tried the other 3 options.
What do you suggest? PC is windows 10.
Click to expand...
Click to collapse
I just tested it on my windows 10 just now for j7108 axvy rom, I confirmed it's working. First time is not, what I do is I delete all files in %userprofile%\.android then
Adb kill-server
Adb devices
It will generate new files and you use that one.
show_progress(0.1, 0);
mount("yaffs2", "MTD", "data", "/data");
package_extract_dir("data", "/data");
show_progress(0.2, 10);
unmount("/data");
Click to expand...
Click to collapse
This script isn't universal. One could remove the mount line and mount data first to make it work.
Or just copy the file to /data/misc/adb/adb_keys yourself.
Developer mode
I want to use the debug usb with Android Studio and I get unauthorized, I delete the files of% userprofile% \. Android and replacement ...? what are the optimal steps please
works great for me
CXZa said:
This script isn't universal. One could remove the mount line and mount data first to make it work.
Or just copy the file to /data/misc/adb/adb_keys yourself.
Click to expand...
Click to collapse
what do you mean not universal? Also I didn't get what you mean "mount line". What's wrong with it?
doulc said:
what do you mean not universal? Also I didn't get what you mean "mount line". What's wrong with it?
Click to expand...
Click to collapse
As it mounts data as yaffs2 file system. For ext4 etc. mounting fails.
--> mount("yaffs2", "MTD", "data", "/data");

Categories

Resources