Database Develop

[SOLVED, problem was java6] Can anyone help me edit the Launcher app from source?

I tried to PM some devs that I thought could help and didn't get a response back so maybe I can get a response here because it would seem that the devs are too busy.
Anyway... I am using Cyanogens source for Launcher and I opened it in Eclipse.
Then I go to Launcher.java and edit this to get nine screens:
Code:
static final int SCREEN_COUNT = 5;
static final int DEFAULT_SCREN = 2;
to
Code:
static final int SCREEN_COUNT = 9;
static final int DEFAULT_SCREN = 4;
then I open the layout-land and layout-port files and edit the Launcher.xml files with:
Code:
launcher:defaultScreen="4">
<include android:id="@+id/cell1" layout="@layout/workspace_screen" />
<include android:id="@+id/cell2" layout="@layout/workspace_screen" />
<include android:id="@+id/cell3" layout="@layout/workspace_screen" />
<include android:id="@+id/cell4" layout="@layout/workspace_screen" />
<include android:id="@+id/cell5" layout="@layout/workspace_screen" />
<include android:id="@+id/cell6" layout="@layout/workspace_screen" />
<include android:id="@+id/cell7" layout="@layout/workspace_screen" />
<include android:id="@+id/cell8" layout="@layout/workspace_screen" />
<include android:id="@+id/cell9" layout="@layout/workspace_screen" />
then I go back to Launcher and export an unsigned application package.
I then sign it with test keys (size is 1.82mb) and add it to an update.zip file.
I apply it and reboot.
and while booting up i get this in logcat:
Code:
01-12 15:22:03.622: INFO/jdwp(2943): Ignoring second debugger -- accepting and dropping
01-12 15:22:03.712: DEBUG/ddm-heap(2943): Got feature list request
01-12 15:22:04.072: INFO/ActivityThread(2943): Publishing provider com.android.globalsearch.SuggestionProvider: com.android.globalsearch.SuggestionProvider
01-12 15:22:10.132: INFO/ActivityThread(2943): Publishing provider com.android.launcher.settings: com.android.launcher.LauncherProvider
01-12 15:22:10.242: DEBUG/AndroidRuntime(2943): Shutting down VM
01-12 15:22:10.262: WARN/dalvikvm(2943): threadid=3: thread exiting with uncaught exception (group=0x4001e170)
01-12 15:22:10.262: ERROR/AndroidRuntime(2943): Uncaught handler: thread main exiting due to uncaught exception
01-12 15:22:10.302: ERROR/AndroidRuntime(2943): java.lang.Error: Unresolved compilation problems:
01-12 15:22:10.302: ERROR/AndroidRuntime(2943): The import com.android.internal.util.XmlUtils cannot be resolved
01-12 15:22:10.302: ERROR/AndroidRuntime(2943): XmlUtils cannot be resolved
01-12 15:22:10.302: ERROR/AndroidRuntime(2943): at com.android.launcher.LauncherProvider.<init>(LauncherProvider.java:49)
01-12 15:22:10.302: ERROR/AndroidRuntime(2943): at java.lang.Class.newInstanceImpl(Native Method)
01-12 15:22:10.302: ERROR/AndroidRuntime(2943): at java.lang.Class.newInstance(Class.java:1479)
01-12 15:22:10.302: ERROR/AndroidRuntime(2943): at android.app.ActivityThread.installProvider(ActivityThread.java:4213)
01-12 15:22:10.302: ERROR/AndroidRuntime(2943): at android.app.ActivityThread.installContentProviders(ActivityThread.java:4000)
01-12 15:22:10.302: ERROR/AndroidRuntime(2943): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:3959)
01-12 15:22:10.302: ERROR/AndroidRuntime(2943): at android.app.ActivityThread.access$2900(ActivityThread.java:118)
01-12 15:22:10.302: ERROR/AndroidRuntime(2943): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1872)
01-12 15:22:10.302: ERROR/AndroidRuntime(2943): at android.os.Handler.dispatchMessage(Handler.java:99)
01-12 15:22:10.302: ERROR/AndroidRuntime(2943): at android.os.Looper.loop(Looper.java:123)
01-12 15:22:10.302: ERROR/AndroidRuntime(2943): at android.app.ActivityThread.main(ActivityThread.java:4320)
01-12 15:22:10.302: ERROR/AndroidRuntime(2943): at java.lang.reflect.Method.invokeNative(Native Method)
01-12 15:22:10.302: ERROR/AndroidRuntime(2943): at java.lang.reflect.Method.invoke(Method.java:521)
01-12 15:22:10.302: ERROR/AndroidRuntime(2943): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791)
01-12 15:22:10.302: ERROR/AndroidRuntime(2943): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:549)
01-12 15:22:10.302: ERROR/AndroidRuntime(2943): at dalvik.system.NativeStart.main(Native Method)
01-12 15:22:10.312: INFO/dalvikvm(2943): threadid=7: reacting to signal 3
01-12 15:22:10.332: INFO/dalvikvm(2943): Wrote stack trace to '/data/anr/traces.txt'
01-12 15:23:58.992: INFO/Process(2943): Sending signal. PID: 2943 SIG: 9
So where did I go wrong?
Thanks.

I think the 9 pages is the source of your prob, but i think adv launcher can do that though.When you made the update was it a standalone update or did you put it in a rom?

ya bro, instead of doing all, just use advanced launcher. It allows u to change ur number of home screens straight from your phone with an easy to use UI.

Ace42 said:
I think the 9 pages is the source of your prob, but i think adv launcher can do that though.When you made the update was it a standalone update or did you put it in a rom?
Click to expand...
Click to collapse
it was a standalone update.
nephron said:
ya bro, instead of doing all, just use advanced launcher. It allows u to change ur number of home screens straight from your phone with an easy to use UI.
Click to expand...
Click to collapse
I've used the Adv Launcher but the reason for doing this is to see how much the Adv Launcher slows down the phone. I was skeptical at first but I used the Adv Launcher with 5 screens and did ten benchmarks and came up with an average of 14210. When I used the standard launcher and did the benchmark it came up with an average of 12005. A significant difference. So I am trying with a larger amount of screens. In this case 9. But it's not working. Should I try 7 and see if that works?
EDIT: Nope. Seven screens gave the same result.

Wow... no one? Seriously? In a forum with over a dozen devs?

It seems completely right to me what you did but it's been a time since I have done this. I don't think that your error is at modifying the source, I think this error has something to do with compilation.
How did you compile it? Did you build the complete source code?
I have to say I never saw this failure and it doesn't even make sense to me. Why the hell should the system throw an error _at runtime_ which says unresolved _compilation problems_? A little crazy
I compiled it just by checking out the whole android source and running make in the top directory of it. It needs some time, but after that everytime you change anything in the launcher and run make it needs just 2 minutes or so .
Sorry if you already know this I just want to make shure there isn't something fundamental going wrong
FYI: Some days ago I stumbled over this: http://code.google.com/p/android-launcher-for-sdk/ it's the 1.6 launcher ported to the sdk so it can be compile without compiling the source code. Credits go over to the guys who made Home++.

irrenhaus said:
It seems completely right to me what you did but it's been a time since I have done this. I don't think that your error is at modifying the source, I think this error has something to do with compilation.
How did you compile it? Did you build the complete source code?
I have to say I never saw this failure and it doesn't even make sense to me. Why the hell should the system throw an error _at runtime_ which says unresolved _compilation problems_? A little crazy
I compiled it just by checking out the whole android source and running make in the top directory of it. It needs some time, but after that everytime you change anything in the launcher and run make it needs just 2 minutes or so .
Sorry if you already know this I just want to make shure there isn't something fundamental going wrong
FYI: Some days ago I stumbled over this: http://code.google.com/p/android-launcher-for-sdk/ it's the 1.6 launcher ported to the sdk so it can be compile without compiling the source code. Credits go over to the guys who made Home++.
Click to expand...
Click to collapse
As I mentioned in my original post, I used Cyanogen's github launcher source and made the modifications from there. Could it be the source?

You mentioned you opened it in eclipse.
I have a problem with that IDE because it modifies your files w/o your permission to what it thinks it is that you really need.
I'd suggest you revert your code, then edit it on gedit, and run "make launcher", and then push that to your phone. Other than that, the code looks alright

I did not much programming on adroid, but I know Java a bit ... Probably I am wrong, but the error message says, that the class com.android.internal.util.XmlUtils could not be found, i.e. the classloader is not able to locate this class, but this class is referenced from com.android.launcher.LauncherProvider. There are two possibilities: either a library containing the class com.android.internal.util.XmlUtils must be provided with the android launcher package, or it's already installed on the phone. Probably you need to package the application with the libs.

jubeh said:
You mentioned you opened it in eclipse.
I have a problem with that IDE because it modifies your files w/o your permission to what it thinks it is that you really need.
I'd suggest you revert your code, then edit it on gedit, and run "make launcher", and then push that to your phone. Other than that, the code looks alright
Click to expand...
Click to collapse
I don't think i have my Ubuntu 9.10 set up correctly.
I run "make launcher" and i get:
make: *** No rule to make target `launcher'. Stop.
Okay... I followed the directions from http://source.android.com/download and then:
cd ~/mydroid
make launcher
and got this back:
[email protected]:~/mydroid$ make launcher
build/core/product_config.mk:261: WARNING: adding test OTA key
============================================
TARGET_PRODUCT=generic
TARGET_BUILD_VARIANT=eng
TARGET_SIMULATOR=
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=
============================================
frameworks/policies/base/PolicyConfig.mk:22: *** No module defined for the given PRODUCT_POLICY (android.policy_phone). Stop.
[email protected]:~/mydroid$ make launcher
build/core/product_config.mk:261: WARNING: adding test OTA key
============================================
TARGET_PRODUCT=generic
TARGET_BUILD_VARIANT=eng
TARGET_SIMULATOR=
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=
============================================
frameworks/policies/base/PolicyConfig.mk:22: *** No module defined for the given PRODUCT_POLICY (android.policy_phone). Stop.
[email protected]:~/mydroid$
Click to expand...
Click to collapse
edit: Using our mutual friend Google, I stumbled onto this:
http://translate.google.com/transla...om.ubuntu:en-US:official&hs=XuU&sa=N&start=10
so hopefully it will work. this is starting to become a pain in the butt!
edit: THIS IS STARTING TO PISS ME OFF! IT'S ONE THING AFTER ANOTHER. Have anybody seen this? I had to install java 5 because 6 is unsupported.
So I tried
sudo apt-get install git-core gnupg sun-java5-jdk flex bison gperf libsdl-dev libesd0-dev libwxgtk2.6-dev build-essential zip curl libncurses5-dev zlib1g-dev
Click to expand...
Click to collapse
which got me:
E: Couldn't find package sun-java5-jdk
so I installed sun-j2re1.5_1.5.0+update22_i386.deb.
now I get this when I try it:
[email protected]:~/mydroid$ java -version
java version "1.5.0_22"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_22-b03)
Java HotSpot(TM) Client VM (build 1.5.0_22-b03, mixed mode, sharing)
[email protected]:~/mydroid$ make
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=1.6
TARGET_PRODUCT=generic
TARGET_BUILD_VARIANT=eng
TARGET_SIMULATOR=
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=Donut
============================================
************************************************************
You are attempting to build with the incorrect version
of javac.
Your version is: javac 1.6.0_0.
The correct version is: 1.5.
Please follow the machine setup instructions at
http://source.android.com/download
************************************************************
build/core/main.mk:121: *** stop. Stop.
Click to expand...
Click to collapse

what are you building? eclair?
it should be good enough to create a generic launcher.
Try from your android directory:
Code:
$. build/envsetup.sh
$lunch
and then select any build type, and then
Code:
make launcher (maybe case sensititve, try make Launcher?)

jubeh said:
what are you building? eclair?
it should be good enough to create a generic launcher.
Try from your android directory:
Code:
$. build/envsetup.sh
$lunch
and then select any build type, and then
Code:
make launcher (maybe case sensititve, try make Launcher?)
Click to expand...
Click to collapse
now i'm getting
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=1.6
TARGET_PRODUCT=generic
TARGET_BUILD_VARIANT=eng
TARGET_SIMULATOR=
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=Donut
============================================
************************************************************
You are attempting to build with the incorrect version
of javac.
Your version is: javac 1.6.0_0.
The correct version is: 1.5.
Please follow the machine setup instructions at
http://source.android.com/download
************************************************************
build/core/main.mk:121: *** stop. Stop.
Click to expand...
Click to collapse
java version "1.5.0_22"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_22-b03)
Java HotSpot(TM) Client VM (build 1.5.0_22-b03, mixed mode, sharing)
Click to expand...
Click to collapse
nvm. I finally got it. Thanks everybody.
I love Google.

update
Hi,
sorry for updating that topics as it looks resolved but I am currently facing the same problems. Which means, when I try to do a make, to build my Eclair Android version :
$ make launcher
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=2.1-update1
TARGET_PRODUCT=generic
TARGET_BUILD_VARIANT=eng
TARGET_SIMULATOR=false
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=ECLAIR
============================================
Checking build tools versions...
************************************************************
You are attempting to build with the incorrect version
of java.
Your version is: java version "1.6.0_0".
The correct version is: 1.5.
Please follow the machine setup instructions at
************************************************************
build/core/main.mk:111: *** stop. Stop.
[[email protected] mydroid]$ java -version
java version "1.6.0_0"
OpenJDK Runtime Environment (IcedTea6 1.6) (fedora-31.b16.fc12-i386)
OpenJDK Client VM (build 14.0-b16, mixed mode)
I've installed:
jdk-1_5_0_22-linux-i586.bin
java_ee_sdk-5_08-linux-nojdk.bin
but it still looks like I'm the 1.6 java version...
What can I do to fix this? Thank you

COMPILE From Source For Any Phone On Linux Distros [BUILD ENVIRONMENT TO COMPILE]

{
"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 guide to Compile From any CyanogenMod and CyanogenMod Source-Based source for Any Phone. This guide is for linux , Ubuntu etc.​
What you’ll need
A Phone Which runs Android
A relatively recent computer (Linux, OS X, or Windows) w/a reasonable amount of RAM and storage. The less RAM you have, the longer the build will take. Using SSDs results in faster builds than traditional hard drives.
A micro USB cable
A decent Internet connection & reliable electricity
Some familiarity with basic Android operation and terminology. It would help if you’ve installed custom roms on other devices and are familiar with what a recovery image such as ClockworkMod is, for example. It may also be useful to know some basic command line concepts such as cd for “change directory”, the concept of directory hierarchies, that in Linux they are separated by /, etc.
Note:
You want to use a 64-bit version of Linux. According to Google, 32-bit Linux environment will only work if you are building older versions prior to Gingerbread (2.3.x)/CyanogenMod 7.
Using a VM allows Linux to run as a guest inside your host computer-- a computer in a computer, if you will. If you hate Linux for whatever reason, you can always just uninstall and delete the whole thing. (There are plenty of places to find instructions for setting up Virtualbox with Ubuntu, so I’ll leave it to you to do that.)
Click to expand...
Click to collapse
So let’s begin!​
Build ROM and ClockworkMod Recovery
​
Prepare the Build Environment
Note:
You only need to do these steps the first time you build. If you previously prepared your build environment and have downloaded the CyanogenMod source code for another device, skip to Next Post.
Click to expand...
Click to collapse
Install the SDK
If you have not previously installed adb and fastboot, install the Android SDK. "SDK" stands for Software Developer Kit, and it includes useful tools that you will can use to flash software, look at the system logs in real time, grab screenshots, and more-- all from your computer.
Helpful Tip!
While the SDK contains lots of different things-- the two tools you are most interested in for building Android are adb and fastboot, located in the /platform-tools directory.
Click to expand...
Click to collapse
Install the Build Packages
Several "build packages" are needed to build From Source. You can install these using the package manager of your choice.
Helpful Tip!
A package manager in Linux is a system used to install or remove software (usually originating from the Internet) on your computer. With Ubuntu, you can use the Ubuntu Software Center. Even better, you may also use the apt-get install command directly in the Terminal. (Learn more about the apt packaging tool system from Wikipedia.)
Click to expand...
Click to collapse
For 32-bit & 64-bit systems, you'll need:
Code:
git-core gnupg flex bison gperf libsdl1.2-dev libesd0-dev libwxgtk2.8-dev squashfs-tools build-essential zip curl
libncurses5-dev zlib1g-dev openjdk-6-jre openjdk-6-jdk pngcrush schedtool
For 64-bit only systems, get these:
Code:
g++-multilib lib32z1-dev lib32ncurses5-dev lib32readline-gplv2-dev gcc-4.7-multilib g++-4.5-multilib
For Linux Mint, you'll need:
Code:
libc6-dev x11proto-core-dev libx11-dev libgl1-mesa-dev mingw32 tofrodos python-markdown libxml2-utils
Create the directories
Code:
mkdir -p ~/bin
Install the repo command
Enter the following to download the "repo" binary and make it executable (runnable):
Code:
curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
Put the ~/bin directory in your path of execution
Make sure that the ~/bin directory you just created is in your path of execution so that you can easily run the repo command even when you're not in ~/bin. Assuming you are using the BASH shell, the default in recent versions of Ubuntu, you can set it like this:
Code:
export PATH=${PATH}:~/bin
Helpful Tip!
You can make this change to the path permanent for all future Terminal sessions:
Code:
gedit ~/.bashrc
This will launch a graphical text editor. Enter
Code:
export PATH=${PATH}:~/bin
on its own line, then save the file.
Click to expand...
Click to collapse
Initialize the source repository
Make a Folder to Download the Sources and cd to it. For That:
Code:
mkdir -p ~/Source
Code:
cd Source
Enter the following to initialize the repository:
REPOSITORY'S OF FAMOUS ROMS (Select One)
PAC-Man :
Code:
repo init -u git://github.com/PAC-man/android.git -b cm-10.2
CM 11.0 :
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
CM 10.1 :
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2
CM10 :
Code:
repo init -u git://github.com/CyanogenMod/android.git -b jellybean
Click to expand...
Click to collapse
Download the source code
Code:
repo sync
Helpful Tip!
The repo sync command is used to update the latest source code from CyanogenMod and Google. Remember it, as you can do it every few days to keep your code base fresh and up-to-date.
Click to expand...
Click to collapse
Get prebuilt apps
Code:
cd ~/Source/vendor/cm
Code:
./get-prebuilts
How To Compile is there on next post ​

Prepare the device-specific code
After the source downloads, type:
Code:
. build/envsetup.sh
Then Do This
Code:
breakfast ******
Where ***** is the codename for your device
MAKE SURE YOUR PHONE IS ON OFFICIAL LATEST CYANOGENMOD ROM
Click to expand...
Click to collapse
Helpful Tip!
If you get a command not found error for lunch, be sure you’ve done the “. build/envsetup.sh” command from ~/Source. Notice there is a period and space (“. ”) in that command.
Click to expand...
Click to collapse
Extract proprietary blobs
Now ensure that your Phone is connected to your computer via the USB cable and that you are in the ~/Source/device/***/***** directory (you can cd ~/Source/device/***/****** if necessary). Run as Root if on Debian using sudo. Then run the this script:
Code:
./proprietary-files.sh
or
Code:
./extract-files.sh
Here ***** is Device codename and *** is the Phone Company like Samsung or HTC
For Example if my phone is note 2 then this will be the device path : ~/Source/device/Samsung/n7100
Click to expand...
Click to collapse
You should see the proprietary files (aka “blobs”) get pulled from the device and moved to the right place in the vendor directory. If you see errors about adb being unable to pull the files, adb may not be in the path of execution
Note:
It’s important that these proprietary files are properly extracted and moved to the vendor directory. Without them, CyanogenMod will build without error, but you’ll be missing important functionality, such as the ability to see anything!
Click to expand...
Click to collapse
Turn on caching to speed up build
Code:
export USE_CCACHE=1
Start the build
Code:
cd ~/Source
brunch *****
Here ***** is the Phone Codename
Helpful Tip!
If the build doesn't start, try lunch and choose your device from the menu. If that doesn't work, try breakfast and choose from the menu. The command make ***** should then work.
Click to expand...
Click to collapse
If the build breaks...
If you experience this not-enough-memory-related error...
Code:
ERROR: signapk.jar failed: return code 1make: *** [out/target/product/n7100/cm_n7100-ota-eng.root.zip] Error 1
...you may want to make the following change to This File : system/build/tools/releasetools/common.py
Change: java -Xmx2048m to java -Xmx1024m or java -Xmx512m
Then start the build again (with brunch).
If you see a message about things suddenly being “killed” for no reason, your (virtual) machine may have run out of memory or storage space. Assign it more resources and try again.
Install the build
Assuming the build completed without error (it will be obvious when it finishes), type:
Code:
# cd $OUT
in the same terminal window that you did the build. Here you’ll find all the files that were created. The stuff that will go in /system is in a folder called system. The stuff that will become your ramdisk is in a folder called root. And your kernel is called... kernel.
But that’s all just background info. The two files we are interested in are (1) recovery.img, which contains ClockworkMod recovery, and (2) cm-[something].zip, which contains ROM.
Install ROM
Back to the $OUT directory on your computer-- you should see a file that looks something like:
Code:
cm-10-20120718-UNOFFICIAL-***.zip
Here *** is the phone codename
Now you can flash the ...zip file above as usual via recovery mode. (Be sure you have backed up any previous installation before trying your new build.)
Feedbacks to this guide ​
tommyjt24 said:
I got my build working!
Great tutorial by the way!
Tom
Click to expand...
Click to collapse
sevenup30 said:
Well i finally sucessfully build.
thank you for your help
Click to expand...
Click to collapse
AndyFox2011 said:
Works like a charm, used it a while ago too set up on 12.10
Click to expand...
Click to collapse
sswb27 said:
Compiling cm10.1 worked great for my sgs3 d2tmo.Thank's for the tutorial it's been fun setting this up.
Click to expand...
Click to collapse
matt95 said:
really really good guide, very detailed and precise.
Click to expand...
Click to collapse
Koetermann said:
Hi there,
I was finally able to compile Cyanogenmod from source.
So, thanks for your guide an your support.Thanks a lot.
Regards Koetermann
Click to expand...
Click to collapse
AndyFox2011 said:
Used your guide again to setup my PC for building! Worked like a charm on 11.04
Click to expand...
Click to collapse
Melch1zedeK said:
thanks for post this, great and simple guide for n00bs (like me)
Click to expand...
Click to collapse
VipSaran said:
This tutorial ROCKS! :good: . Successfully built i9300 starting from fresh ubuntu 12.10 installation w/o even a hickup
Click to expand...
Click to collapse
Read the Below Command Before Asking question regarding Device tree : Credit @speed_bot
HTML:
#include
#include /ps my own header/
main()
{
int device tree,rom;
for((device==1) || (device tree =1))
printf("you can build a rom");
else
printf("you cant :P");
}

Great guide!
I want to build cm10.1 for x10 mini and I have to modify
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="teamhacksung/buildscripts" path="buildscripts" remote="github" revision="jellybean">
<copyfile dest="build.sh" src="build.sh" />
</project>
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_device_samsung_n7000" path="device/samsung/n7000" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_device_samsung_galaxys2-common" path="device/samsung/galaxys2-common" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_kernel_samsung_smdk4210" path="kernel/samsung/smdk4210" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="jellybean" />
</manifest>
right? So, how can I do that? What should I change it into? Thanks

pongnamu said:
Great guide!
I want to build cm10.1 for x10 mini and I have to modify
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="teamhacksung/buildscripts" path="buildscripts" remote="github" revision="jellybean">
<copyfile dest="build.sh" src="build.sh" />
</project>
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_device_samsung_n7000" path="device/samsung/n7000" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_device_samsung_galaxys2-common" path="device/samsung/galaxys2-common" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_kernel_samsung_smdk4210" path="kernel/samsung/smdk4210" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="jellybean" />
</manifest>
right? So, how can I do that? What should I change it into? Thanks
Click to expand...
Click to collapse
You can Pm Freexperia for that.
i dont know every android phone's code
i know about freeexperia because i own a xperia mini myself

mithun46 said:
Code:
sudo apt-get install git-core gnupg flex bison gperf build-essential zip curl zlib1g-dev zlib1g-dev:i386 libc6-dev lib32ncurses5-dev ia32-libs x11proto-core-dev libx11-dev:i386 libreadline6-dev:i386 lib32z-dev libgl1-mesa-glx:i386 libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown libxml2-utils xsltproc readline-common libreadline6-dev libreadline6 lib32readline-gplv2-dev libncurses5-dev lib32readline5 lib32readline6 libreadline-dev libreadline6-dev:i386 libreadline6:i386 bzip2 libbz2-dev libbz2-1.0 libghc-bzlib-dev lib32bz2-dev libsdl1.2-dev libesd0-dev squashfs-tools pngcrush schedtool libwxgtk2.6-dev python
​
Click to expand...
Click to collapse
M getting error
[email protected]:~$ sudo apt-get install git-core gnupg flex bison gperf build-essential zip curl zlib1g-dev zlib1g-dev:i386 libc6-dev lib32ncurses5-dev ia32-libs x11proto-core-dev libx11-dev:i386 libreadline6-dev:i386 lib32z-dev libgl1-mesa-glx:i386 libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown libxml2-utils xsltproc readline-common libreadline6-dev libreadline6 lib32readline-gplv2-dev libncurses5-dev lib32readline5 lib32readline6 libreadline-dev libreadline6-dev:i386 libreadline6:i386 bzip2 libbz2-dev libbz2-1.0 libghc-bzlib-dev lib32bz2-dev libsdl1.2-dev libesd0-dev squashfs-tools pngcrush schedtool libwxgtk2.6-dev python
[sudo] password for jolly:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package lib32bz2-dev is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
Package lib32ncurses5-dev is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
Package lib32readline-gplv2-dev is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
Package lib32readline5 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
Package lib32readline6 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
Package ia32-libs is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'lib32ncurses5-dev' has no installation candidate
E: Package 'ia32-libs' has no installation candidate
E: Unable to locate package lib32z-dev
E: Package 'lib32readline-gplv2-dev' has no installation candidate
E: Package 'lib32readline5' has no installation candidate
E: Package 'lib32readline6' has no installation candidate
E: Package 'lib32bz2-dev' has no installation candidate
E: Unable to locate package libwxgtk2.6-dev
E: Couldn't find any package by regex 'libwxgtk2.6-dev
Click to expand...
Click to collapse
​

dewanshu93 said:
M getting error
Click to expand...
Click to collapse
sorry for my mistake
u should enter it in package manager and install them all

Your local_manifest.xml is incorrect for compiling CM10.1.

chasmodo said:
Your local_manifest.xml is incorrect for compiling CM10.1.
Click to expand...
Click to collapse
The Below Manifest is for Compiling CM10. Not CM10.1

Good effort though
Sent from my GT-N7000 using xda app-developers app

The issue with guides like these is they are specific to one version of Ubuntu. I successfully build Android on gentoo, which has about as little in common with Ubuntu as possible. Hence we prefer to go for guides which, where possible, teach the reasoning, rather than the method.
For building CM, this might be worthwhile merging into the "how to build android from source" one?
Unfortunately this guide isn't usable for most people, as it relies on the hacksung build scripts, so you can only build for certain devices...
What might be better is a guide on using roomservice via lunch, to build for any device?

pulser_g2 said:
The issue with guides like these is they are specific to one version of Ubuntu. I successfully build Android on gentoo, which has about as little in common with Ubuntu as possible. Hence we prefer to go for guides which, where possible, teach the reasoning, rather than the method.
For building CM, this might be worthwhile merging into the "how to build android from source" one?
Unfortunately this guide isn't usable for most people, as it relies on the hacksung build scripts, so you can only build for certain devices...
What might be better is a guide on using roomservice via lunch, to build for any device?
Click to expand...
Click to collapse
i said in starting This is based for Galaxy Note 1 But You can edit to make for your phone

I'd guess this is a step by step guide for people with this device as others have said and it is very specific. What would be useful is if you did it in steps and was more generic, say when you set up your environment you tell the reader to check for himself in device forums for a devs source code to be able to try. and if that is too difficult to explain then you may have to explain the principle for the people with little to no knowledge of building what they are doing instead of type this and paste that. great idea, but needs much improvement in actual teaching. also if someone had the knowledge to edit to make it for their own phones then they wouldn't need to use this guide in the first place.

Thanks for this nice guide! Thanks +1 for you! :good:

For some reason the CM repo isnt syncing in the folder I want it to.
Code:
mkdir ~/cm10
cd ~/cm10
repo init -u git://github.com/CyanogenMod/android.git -b jellybean
repo sync -j16
It just spits everything in the home directory (~/) and the working folder I wanted everything in (~/cm10) is empty.
Any idea what the hell I'm doing wrong?
Edit: Well I got it to sync in the folder I wanted it to finally. I had to
Code:
rm -rf ~/.repo
first before it would initialize in my cm10 folder. Absolutely bizarre...

@OP
You might wanna change "CopyPasta" to "Copy-Paste".

i made it for fun

Oh okay then. But to me, it seems a bit...err...unprofessional. No offense intended.

mithun46 said:
sorry for my mistake
u should enter it in package manager and install them all
Click to expand...
Click to collapse
Using aptitude I've got this:
[email protected]:~$ sudo aptitude install git-core gnupg flex bison gperf build-essential zip curl zlib1g-dev zlib1g-dev:i386 libc6-dev lib32ncurses5-dev ia32-libs x11proto-core-dev libx11-ddev:i386 lib32z-dev libgl1-mesa-glx:i386 libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown libxml2-utils xsltproc readline-common libreadline6-dev libreadline6 lib32readline-gplv2-dev libncurses5-dev lib32readline5 lib32readline6 libreadline-dev libreadline6-dev:i386 libreadline6:i386 bzip2 libbz2-dev libbz2-1.0 libghc-bzlib-dev lib32bz2-dev libsdl1.2-dev libesd0-dev squashfs-tools pngcrush schedtool libwxgtk2.6-dev python
Keine Kandidatsversion für lib32ncurses5-dev gefunden
Keine Kandidatsversion für ia32-libs gefunden
Es konnte kein Paket gefunden werden, dessen Name oder Beschreibung auf »lib32z-dev« passt.
Keine Kandidatsversion für lib32readline-gplv2-dev gefunden
Keine Kandidatsversion für lib32readline5 gefunden
Keine Kandidatsversion für lib32readline6 gefunden
Keine Kandidatsversion für lib32bz2-dev gefunden
Keine Kandidatsversion für libwxgtk2.6-dev gefunden
Keine Kandidatsversion für lib32ncurses5-dev gefunden
Keine Kandidatsversion für ia32-libs gefunden
Es konnte kein Paket gefunden werden, dessen Name oder Beschreibung auf »lib32z-dev« passt.
Keine Kandidatsversion für lib32readline-gplv2-dev gefunden
Keine Kandidatsversion für lib32readline5 gefunden
Keine Kandidatsversion für lib32readline6 gefunden
Keine Kandidatsversion für lib32bz2-dev gefunden
Keine Kandidatsversion für libwxgtk2.6-dev gefunden
Die folgenden NEUEN Pakete werden zusätzlich installiert:
bison flex g++-4.7-multilib{a} g++-multilib gcc-4.7-multilib{a} gcc-multilib{a} ghc{a} git{a} git-core git-man{a} gperf lib64gcc1{a} lib64gomp1{a} lib64itm1{a} lib64quadmath0{a}
lib64stdc++6{a} libasound2-dev{a} libaudiofile-dev{a} libavahi-client-dev{a} libavahi-common-dev{a} libbison-dev{a} libbsd-dev{a} libbz2-dev libc6-amd64{a} libc6-dev-amd64{a}
libcaca-dev{a} libdbus-1-dev{a} libesd0-dev libffi-dev{a} libfl-dev{a} libghc-bzlib-dev libglib2.0-dev{a} libgmp-dev{a} libgmpxx4ldbl{a} liblzo2-2{a} libncurses5-dev libpcre3-dev{a}
libpcrecpp0{a} libpng12-dev{a} libpulse-dev{a} libreadline-dev libreadline6-dev libsdl1.2-dev libslang2-dev{a} libtinfo-dev{a} mingw32 mingw32-binutils{a} mingw32-runtime{a} pngcrush
python-markdown python-pygments{a} schedtool squashfs-tools tofrodos xsltproc
Die folgenden Pakete werden ENTFERNT:
ca-certificates-java{u} libatk-wrapper-java{u} libatk-wrapper-java-jni{u} tzdata-java{u}
0 Pakete aktualisiert, 55 zusätzlich installiert, 4 werden entfernt und 0 nicht aktualisiert.
103 MB an Archiven müssen heruntergeladen werden. Nach dem Entpacken werden 425 MB zusätzlich belegt sein.
Möchten Sie fortsetzen? [Y/n/?] y
Running Kubuntu 12.10, KDE 4.9.4

try to use stock package manager

mithun46 said:
try to use stock package manager
Click to expand...
Click to collapse
Isn't "apt" the "stock" package manager in (K)Ubuntu?
But I've another question @mithun46: Is it possible, that your guide only works on a 64bit edition of ubuntu? So that 32bit installations ain't supported?

[GUIDE] How to build CM from source

Hello Guys,
In this guide i will quickly show you how to build CyanogenMod from source.
Step 1)
You will need to install Java6 (Not Java 7 or Java 5 there are not compitable)
Do the following:
sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-java6-installer
Click to expand...
Click to collapse
Step 2)
For faster building settup your ccache by editing bashrc:
Make a folder in your home directory callled ccache
gedit ~/.bashrc
Add these 2 lines at the end of the file:
export USE_CCACHE=1
export CCACHE_DIR=ccache
Click to expand...
Click to collapse
Step 3)
Getting the repo tool (if this is not working for the first time try this step again!)
mkdir ~/bin
PATH=~/bin:$PATH
curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
Click to expand...
Click to collapse
Step 4)
Make a working directory for your build!
mkdir -p ~/android/system
cd ~/android/system
~/bin/repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2
If you are building CM10.1 use this source ~/bin/repo init -u git: https://github.com/CyanogenMod/android.git -b cm-10.1
Click to expand...
Click to collapse
Step 5)
Local manifest setup:
mkdir .repo/local_manifests
touch .repo/local_manifests/local_manifest.xml
gedit .repo/local_manifests/local_manifest.xml
then a window will open paste this in the window and save it then close the window
Click to expand...
Click to collapse
CYANOGENMOD 10.2 LOACAL MANIFEST
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="cmorlok/android_kernel_samsung_p5" path="kernel/samsung/p5" revision="refs/heads/cm-10.2" />
<project name="cmorlok/android_device_samsung_p4-common" path="device/samsung/p4-common" revision="refs/heads/cm-10.2" />
<project name="cmorlok/android_device_samsung_p5" path="device/samsung/p5" revision="refs/heads/cm-10.2" />
<project name="cmorlok/android_device_samsung_p5wifi" path="device/samsung/p5wifi" revision="refs/heads/cm-10.2" />
<project name="cmorlok/proprietary_vendor_samsung" path="vendor/samsung" revision="refs/heads/cm-10.2" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" />
</manifest>
CYANOGENMOD 10.1 LOACAL MANIFEST
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="cmorlok/android_kernel_samsung_p5" path="kernel/samsung/p5" revision="refs/heads/cm-10.1" />
<project name="cmorlok/android_device_samsung_p4-common" path="device/samsung/p4-common" revision="refs/heads/cm-10.1" />
<project name="cmorlok/android_device_samsung_p5" path="device/samsung/p5" revision="refs/heads/cm-10.1" />
<project name="cmorlok/android_device_samsung_p5wifi" path="device/samsung/p5wifi" revision="refs/heads/cm-10.1" />
<project name="cmorlok/proprietary_vendor_samsung" path="vendor/samsung" revision="refs/heads/cm-10.1" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" />
</manifest>
Step 6)
Syncing the repo:
cd ~/android/system
~/bin/repo sync
This can take a long long long time (depends on your pc specs)
Click to expand...
Click to collapse
Step 7)
When syncing is done do the following:
You need to do this otherwise you will get errors when building.
cd ~/android/system/vendor/cm
./get-prebuilts
Click to expand...
Click to collapse
Step 8)
Building CyanogenMod:
cd ~/android/system
source build/envsetup.sh
lunch
brunch p5wifi (For P5 use the following: brunch p5)
Click to expand...
Click to collapse
Credits:
Android open source page
Cyanogenmod WIKI
C-o-M
Kingbabasula
Good luck with building if you have any questions errors post them here and we will help you out!

safariking said:
You will need to install Java6 (Not Java 7 or Java 5 there are not compitable)
Do the following:
sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-java6-installer
Click to expand...
Click to collapse
Quick question: The CM build site recommends openjdk whereas the build process seems to complain about using non-oracle/sun jdk.
What's the actual jdk we should be using to build?

I always use java 6 no problems here
Sent from my GT-P7310 using xda app-developers app

safariking said:
I always use java 6 no problems here
Click to expand...
Click to collapse
I guess the question is: which one is the 'right' one to use?

I say java 6 i have seen that a lot of users here on xda are using it
Sent from my GT-I9105P using xda app-developers app

hdd space
Hi,
what's the hdd space needed for syncing the 10.2 repo?
Thanks.

Almost 10GB i recommend you to have a total disk space of 100 GB
Sent from my GT-I9105P using xda app-developers app

safariking said:
Almost 10GB i recommend you to have a total disk space of 100 GB
Sent from my GT-I9105P using xda app-developers app
Click to expand...
Click to collapse
damn, so my 12 GB vmware allocated hdd is not enough
Thanks.

No
Sent from my GT-I9105P using xda app-developers app

combat2k said:
Hi,
what's the hdd space needed for syncing the 10.2 repo?
Thanks.
Click to expand...
Click to collapse
Empty tree: 8GB
Populated tree: 16GB
Post build: 34GB

question
why do I get something like below:
object e76efdd7b342577c40aa271fa5ded9d66a783a9b
type commit
tag v1.12.4
tagger Conley Owens <[email protected]> 1380645867 -0700
repo 1.12.4
gpg: Signature made Ma 01 oct 2013 19:44:27 +0300 EEST using RSA key ID 692B382C
gpg: Can't check signature: public key not found
error: could not verify the tag 'v1.12.4'
when calling ~/bin/repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2
There is something wrong with tag 1.12.4? Or something to add to configuration?
Thanks...

combat2k said:
why do I get something like below:
object e76efdd7b342577c40aa271fa5ded9d66a783a9b
type commit
tag v1.12.4
tagger Conley Owens <[email protected]> 1380645867 -0700
repo 1.12.4
gpg: Signature made Ma 01 oct 2013 19:44:27 +0300 EEST using RSA key ID 692B382C
gpg: Can't check signature: public key not found
error: could not verify the tag 'v1.12.4'
when calling ~/bin/repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2
There is something wrong with tag 1.12.4? Or something to add to configuration?
Thanks...
Click to expand...
Click to collapse
i found a solution here for the error that you are seeing : http://www.marshut.com/wrrts/repo-release-1-12-4.html
use the below command, this worked for me today.
curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo

Try noparse-tags and code:
Code:
[PLAIN]curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo[/PLAIN]

Hmm I had the same issue, but the above fixes didnt work for me. Finally used
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2 --no-repo-verify
and it worked.

what should I choose for lunch - step 8? it displays a list with 105 options, and... no hint about my p7300..
Thanks.

What I still don't unterstand at all is, how I can get the sources of e.g. C-o-M'S CM10.1.2 and CM10.1 nightly 2013-Aug-06 to compare it?
In Windows I used to use Total Commander to compare two folders, is there also a similar tool in Linux?

How To Guide How to compile the OmniROM for the ASUS Zenfone 8

How to compile the OmniROM for the ASUS Zenfone 8
Update 14.11.2022 /bs
This HowTo is about how to compile the OmniROM 12 for the ASUS Zenfone 8 -- see How to compile the OmniROM 13 for the ASUS Zenfone 8 for how to compile the OmniROM 13 for the ASUS Zenfone 8.
Correction
There was a spelling error in the name of the command to list all available targets : the command name is breakfast
Compiling the CustomROM OmniROM from within Linux is a very simple and straight forward process -- the developer for the OmniROM did a really amazing good job setting up the build environment for the OmniROM.
But some information are missing in the instructions (at least I did not found them ...)
Therefor I document here what I did to compile the OmniROM for the ASUS Zenfone 8 on my Linux notebook:
First install the neccessary tool called "repo" to maintain the repositories for the OmniROM ; see here https://gerrit.googlesource.com/git-repo/
Next create a new directory on your PC; switch to that directory, and initialize the necessarry repositories like described in the section "Getting Started" here: https://github.com/omnirom/android :
Note [29.07.2022]:
The repositories for the branch android-12.0 are somehow outdated with the security patch level from February 2022 . To get the code with the security patch level from June 2022 use the repositories for the branch android-12.1.
Bash:
repo init -u https://github.com/omnirom/android.git -b android-12.1
# Then to sync up:
repo sync
Be aware that the repositories need about 140 GB disk space so this will take a while.
Please note that I did not install any additional tool to compile the CustomROM for android - everything neccessary was installed by synching the repositories.
When the download is finished you must add the repositories for the vendor and device tree for your phone to the manifests in the local repositories.
This should be done in the file .repo/local_manifests/local_manifest.xml . For the ASUS Zenfone 8 the file should look like this:
Code:
[[email protected] /data/develop/android/OmniROM]$ cat .repo/local_manifests/local_manifest.xml
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="DonkeyCoyote"
fetch="https://github.com/DonkeyCoyote" />
<project path="device/asus/zenfone8" name="android_device_asus_zenfone8" remote="omnirom" revision="android-12.0" />
<project path="vendor/asus" name="proprietary_vendor_asus" remote="DonkeyCoyote" revision="android-12.1" />
</manifest>
After updating the file local_manifest.xml do another
Bash:
repo sync
to sync the added repositories. This time the download will be faster because only the two additional repos will be downloaded.
Now you can start the build with these commands:
Bash:
. build/envsetup.sh
brunch omni_zenfone8-user
in the directory with the downloaded repositories (use the command "breakfast" instead of "brunch" to see other possible targets)
Note that the first time the compile process will take 4 hours or more. And keep in mind that the compile process will need additional 140 GB for the temporary output files.
If everything is fine there will be a ZIP file with your own CustomROM image in the directory ./out/target/product/zenfone8/ when the compile script is done, e.g:
Code:
[[email protected] /data/develop/android/OmniROM]$ ls -ltr out/target/product/zenfone8/omni-12-20220621-zenfone8-HOMEMADE.zip
-rw-rw-r--. 25 xtrnaw7 xtrnaw7 1253703465 Jun 25 10:03 out/target/product/zenfone8/omni-12-20220621-zenfone8-HOMEMADE.zip
[[email protected] /data/develop/android/OmniROM]$
That image can now be installed on the Zenfone 8 using the LineageOS Recovery or TWRP.
Notes
[Update 29.07.2022]
In case you want to rename the directory with the repositories for OminROM:
Be aware that the make scripts for the OmniROM will create some absolute links in the repo directories in ./out. Therefor you must recreate these links after renaming the directory.
How to create an OmniROM image with MicroG
To create an OmniROM image with MicroG these additional steps are neccesarry:
Add the repo with the prebuild MicroG apks, android_prebuilts_prebuiltapks, to your local_manifests.xml file, e.g:
Code:
[[email protected] /data/develop/android/OmniROM]$ cat .repo/local_manifests/local_manifest.xml
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="DonkeyCoyote"
fetch="https://github.com/DonkeyCoyote" />
<project path="device/asus/zenfone8" name="android_device_asus_zenfone8" remote="omnirom" revision="android-12.0" />
<project path="vendor/asus" name="proprietary_vendor_asus" remote="DonkeyCoyote" revision="android-12.1" />
<project path="vendor/microg" name="android_prebuilts_prebuiltapks" remote="omnirom" revision="android-12.0" />
</manifest>
[[email protected] /data/develop/android/OmniROM]$
Do another repo sync to download the repository for MicroG:
Code:
repo sync
and create the CustomROM using these instructions:
Code:
export ROM_BUILDTYPE=MICROG
brunch omni_zenfone8-user
This will create an OmniROM Image with MicroG already installed, e.g:
Code:
[[email protected] /data/develop/android/OmniROM]$ ls -ltr out/target/product/zenfone8/omni-12-20220621-zenfone8-MICROG.zip
-rw-rw-r--. 25 xtrnaw7 xtrnaw7 1253703465 Jun 25 10:03 out/target/product/zenfone8/omni-12-20220621-zenfone8-MICROG.zip
[[email protected] /data/develop/android/OmniROM]$
Update 29.09.2022 /bs
There seems to be a bug or feature in the scripts to compile OmniROM:
Old versions of the ZIP file with the image in the output directory will always be overwritten or replaced with the current image, e.g.:
Code:
[ OmniRomDev - [email protected] /data/develop/android/test ] $ ls -l /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220*zip
-rw-rw-r--. 20 xtrnaw7 xtrnaw7 1256445293 Sep 27 18:12 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220728-zenfone8-MICROG.zip
-rw-rw-r--. 20 xtrnaw7 xtrnaw7 1256445293 Sep 27 18:12 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220729-zenfone8-MICROG.zip
-rw-rw-r--. 20 xtrnaw7 xtrnaw7 1256445293 Sep 27 18:12 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220804-zenfone8-MICROG.zip
-rw-rw-r--. 20 xtrnaw7 xtrnaw7 1256445293 Sep 27 18:12 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220809-zenfone8-HOMEMADE.zip
-rw-rw-r--. 20 xtrnaw7 xtrnaw7 1256445293 Sep 27 18:12 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220810-zenfone8-MICROG.zip
-rw-rw-r--. 20 xtrnaw7 xtrnaw7 1256445293 Sep 27 18:12 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220820-zenfone8-MICROG.zip
-rw-rw-r--. 20 xtrnaw7 xtrnaw7 1256445293 Sep 27 18:12 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220828-zenfone8-MICROG.zip
-rw-rw-r--. 20 xtrnaw7 xtrnaw7 1256445293 Sep 27 18:12 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220904-zenfone8-MICROG.zip
-rw-rw-r--. 20 xtrnaw7 xtrnaw7 1256445293 Sep 27 18:12 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220911-zenfone8-MICROG.zip
-rw-rw-r--. 20 xtrnaw7 xtrnaw7 1256445293 Sep 27 18:12 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220918-zenfone8-MICROG.zip
-rw-rw-r--. 20 xtrnaw7 xtrnaw7 1256445293 Sep 27 18:12 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220927-zenfone8-MICROG.zip
[ OmniRomDev - [email protected] /data/develop/android/test ] $
[ OmniRomDev - [email protected] /data/develop/android/test ] $ cksum /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220*zip
592627598 1256445293 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220728-zenfone8-MICROG.zip
592627598 1256445293 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220729-zenfone8-MICROG.zip
592627598 1256445293 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220804-zenfone8-MICROG.zip
592627598 1256445293 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220809-zenfone8-HOMEMADE.zip
592627598 1256445293 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220810-zenfone8-MICROG.zip
592627598 1256445293 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220820-zenfone8-MICROG.zip
592627598 1256445293 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220828-zenfone8-MICROG.zip
592627598 1256445293 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220904-zenfone8-MICROG.zip
592627598 1256445293 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220911-zenfone8-MICROG.zip
592627598 1256445293 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220918-zenfone8-MICROG.zip
592627598 1256445293 /data/develop/android/OmniROM/out/target/product/zenfone8/omni-12-20220927-zenfone8-MICROG.zip
[ OmniRomDev - [email protected] /data/develop/android/test ]
Update 03.11.2022 /bs
When compiling aborts with error messages like these
Code:
error: vendor/qcom/opensource/interfaces/wifi/supplicant/aidl/Android.bp:16:23: unrecognized property "versions_with_info"
error: vendor/qcom/opensource/interfaces/bluetooth_audio/aidl/Android.bp:17:23: unrecognized property "versions_with_info"
Do a forced repo sync:
Bash:
repo sync --force-sync
and start the compile process again .

Trying to compile LineageOS 18.1 for discontinued SM-T713

I've been following the instrucsions from here:
[GUIDE/HOW-TO] Building LineageOS for an Unsupported Device
Foreword: This is my own notes I created to build LOS for my device (SM-T713 or gts28vewifi). After reading this, I encourage you to create your own notes as it will help you better understand the build process. I followed the official guide...
forum.xda-developers.com
To try and compile LOS 18.1, and I am using this manifest:
local_manifests/gts28vewifi.xml at lineage-17.1 · team-infusion-developers/local_manifests
Contribute to team-infusion-developers/local_manifests development by creating an account on GitHub.
github.com
And i am getting this error. Wondering if anyone has any insight into how to get past this. Thanks in advance:
[100% 182/182] out/soong/.bootstrap/bin/soong_build out/soong/build.
FAILED: out/soong/build.ninja
out/soong/.bootstrap/bin/soong_build -t -l out/.module_paths/Android
.bp.list -b out/soong -n out -d out/soong/build.ninja.d -globFile ou
t/soong/.bootstrap/build-globs.ninja -o out/soong/build.ninja Androi
d.bp
error: hardware/samsung/hidl/power-libperfmgr/Android.bp:22:1: "andr
[email protected]" depends on undefi
ned module "libperfmgr"
Module "[email protected]" is de
fined in namespace "." which can read these 1 namespaces: ["."]
Module "libperfmgr" can be found in these namespaces: ["hardware/goo
gle/pixel"]
17:31:32 soong bootstrap failed with: exit status 1

@thefanum,
While it's nice to follow the provided instructions, one of the main problems with them is that they get out of date if not updated periodically.
Specifically these commits made March 14, 2023.
https://review.lineageos.org/q/git-lfs
require that git-lfs be installed on the host computer now otherwise the compiler will stop and webview.apk won't get installed properly in the rom.
So if you are running a Debian style distro, then you need
Bash:
# install git-lfs
sudo apt install git-lfs
# cd into LineageOS code directory
cd ~/18.1
# tell build system we have git-lfs
repo init --git-lfs
# get rid of old webview
rm -rf external/chromium-webview/prebuilt/*
rm -rf .repo/projects/external/chromium-webview/prebuilt/*.git
rm -rf .repo/project-objects/LineageOS/android_external_chromium-webview_prebuilt_*.git
# sync everything
repo sync --force-sync
Compiling the next version of Android always requires some code changes. That is, using 17.1 code and trying to build 18.1 will never work.
I've already done 99.9% of the work for T713 because the T813 and T713 share the same common code trees. Since there were no code changes from 17.1 to 18.1 for the device specific tree
https://github.com/retiredtab/android_device_samsung_gts210vewifi
and assuming none are needed for the gts28vewifi tree, then you can use the 17.1 existing tree with MY manifest from
https://github.com/retiredtab/LineageOS-build-manifests/tree/main/18.1
That is, your version of my 181-gts210vewifi.xml should look like
XML:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- Samsung Device Trees -->
<project name="team-infusion-developers/android_device_samsung_gts28vewifi" path="device/samsung/gts28vewifi" remote="github" revision="lineage-17.1" />
<project name="retiredtab/android_device_samsung_gts210vewifi" path="device/samsung/gts210vewifi" remote="github" revision="lineage-18.1" />
<project name="retiredtab/android_device_samsung_msm8976-common" path="device/samsung/msm8976-common" remote="github" revision="lineage-18.1" />
<!-- Samsung MSM8976 Kernel -->
<project name="syphyr/android_kernel_samsung_msm8976" path="kernel/samsung/msm8976" remote="github" revision="lineage-16.0" />
<!-- Vendor Trees (for all devices) -->
<project name="retiredtab/proprietary_vendor_samsung_msm8976" path="vendor/samsung" remote="github" revision="lineage-18.1" />
<!-- Samsung Hardware Repo -->
<project path="hardware/samsung" name="LineageOS/android_hardware_samsung" remote="github" revision="lineage-18.1"/>
<!-- Dependencies -->
<project path="external/sony/boringssl-compat" name="LineageOS/android_external_sony_boringssl-compat" remote="github" revision="lineage-18.1"/>
<project name="LineageOS/android_hardware_sony_timekeep" path="hardware/sony/timekeep" remote="github" revision="lineage-18.1" />
</manifest>
In theory, this should yield an equivalent 18.1 T713 build with the same functionality as my 18.1 T813 build.
I suggest you follow my 18.1 build specific instructions at
https://github.com/retiredtab/Linea...ob/main/18.1/181-gts210vewifi-build-guide.txt
One person on xda has followed them and created their own 18.1 T813 private builds.
I'll also make 3 suggestions during your build phase.
1. Make an "eng" build so that adb logcat starts right away so you can see log messages on your console. Once everything works, you can then build the "userdebug".
Bash:
# j4 means 4 threads. If you have 6 core, 12 thread CPU, then change this to 12.
TARGET_BUILD_TYPE=debug TARGET_BUILD_VARIANT=eng make -j4 bacon
2. My publicly released 18.1 T813 is selinux enforcing. There's no guarantee that the rules I wrote will work 100% with the T713 so you should revert/undo this commit
https://github.com/retiredtab/andro...mmit/687691a81e028d002919f9f1d069b5b0c9d72512
so that the build is permissive. Once everything works, then you can enforce the build.
3. You will need at least 16GB DRAM to make this 18.1 64 bit build. The more the better.

thefanum said:
Code:
[100% 182/182] out/soong/.bootstrap/bin/soong_build out/soong/build.
FAILED: out/soong/build.ninja
out/soong/.bootstrap/bin/soong_build -t -l out/.module_paths/Android
.bp.list -b out/soong -n out -d out/soong/build.ninja.d -globFile ou
t/soong/.bootstrap/build-globs.ninja -o out/soong/build.ninja Androi
d.bp
error: hardware/samsung/hidl/power-libperfmgr/Android.bp:22:1: "andr
[email protected]" depends on undefi
ned module "libperfmgr"
Module "[email protected]" is de
fined in namespace "." which can read these 1 namespaces: ["."]
Module "libperfmgr" can be found in these namespaces: ["hardware/goo
gle/pixel"]
17:31:32 soong bootstrap failed with: exit status 1
Click to expand...
Click to collapse
The above error is because you are trying to use the 17.1 tree and compiling 18.1 and you are not picking up the 18.1 tree at
https://github.com/LineageOS/android_hardware_samsung/commits/lineage-18.1
If you look at the March 18, 20 and 21, 2021 changes, that's where they added libperfmgr.

retiredtab said:
@thefanum,
While it's nice to follow the provided instructions, one of the main problems with them is that they get out of date if not updated periodically.
Specifically these commits made March 14, 2023.
https://review.lineageos.org/q/git-lfs
require that git-lfs be installed on the host computer now otherwise the compiler will stop and webview.apk won't get installed properly in the rom.
So if you are running a Debian style distro, then you need
Bash:
# install git-lfs
sudo apt install git-lfs
# cd into LineageOS code directory
cd ~/18.1
# tell build system we have git-lfs
repo init --git-lfs
# get rid of old webview
rm -rf external/chromium-webview/prebuilt/*
rm -rf .repo/projects/external/chromium-webview/prebuilt/*.git
rm -rf .repo/project-objects/LineageOS/android_external_chromium-webview_prebuilt_*.git
# sync everything
repo sync --force-sync
Compiling the next version of Android always requires some code changes. That is, using 17.1 code and trying to build 18.1 will never work.
I've already done 99.9% of the work for T713 because the T813 and T713 share the same common code trees. Since there were no code changes from 17.1 to 18.1 for the device specific tree
https://github.com/retiredtab/android_device_samsung_gts210vewifi
and assuming none are needed for the gts28vewifi tree, then you can use the 17.1 existing tree with MY manifest from
https://github.com/retiredtab/LineageOS-build-manifests/tree/main/18.1
That is, your version of my 181-gts210vewifi.xml should look like
XML:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- Samsung Device Trees -->
<project name="team-infusion-developers/android_device_samsung_gts28vewifi" path="device/samsung/gts28vewifi" remote="github" revision="lineage-17.1" />
<project name="retiredtab/android_device_samsung_gts210vewifi" path="device/samsung/gts210vewifi" remote="github" revision="lineage-18.1" />
<project name="retiredtab/android_device_samsung_msm8976-common" path="device/samsung/msm8976-common" remote="github" revision="lineage-18.1" />
<!-- Samsung MSM8976 Kernel -->
<project name="syphyr/android_kernel_samsung_msm8976" path="kernel/samsung/msm8976" remote="github" revision="lineage-16.0" />
<!-- Vendor Trees (for all devices) -->
<project name="retiredtab/proprietary_vendor_samsung_msm8976" path="vendor/samsung" remote="github" revision="lineage-18.1" />
<!-- Samsung Hardware Repo -->
<project path="hardware/samsung" name="LineageOS/android_hardware_samsung" remote="github" revision="lineage-18.1"/>
<!-- Dependencies -->
<project path="external/sony/boringssl-compat" name="LineageOS/android_external_sony_boringssl-compat" remote="github" revision="lineage-18.1"/>
<project name="LineageOS/android_hardware_sony_timekeep" path="hardware/sony/timekeep" remote="github" revision="lineage-18.1" />
</manifest>
In theory, this should yield an equivalent 18.1 T713 build with the same functionality as my 18.1 T813 build.
I suggest you follow my 18.1 build specific instructions at
https://github.com/retiredtab/Linea...ob/main/18.1/181-gts210vewifi-build-guide.txt
One person on xda has followed them and created their own 18.1 T813 private builds.
I'll also make 3 suggestions during your build phase.
1. Make an "eng" build so that adb logcat starts right away so you can see log messages on your console. Once everything works, you can then build the "userdebug".
Bash:
# j4 means 4 threads. If you have 6 core, 12 thread CPU, then change this to 12.
TARGET_BUILD_TYPE=debug TARGET_BUILD_VARIANT=eng make -j4 bacon
2. My publicly released 18.1 T813 is selinux enforcing. There's no guarantee that the rules I wrote will work 100% with the T713 so you should revert/undo this commit
https://github.com/retiredtab/andro...mmit/687691a81e028d002919f9f1d069b5b0c9d72512
so that the build is permissive. Once everything works, then you can enforce the build.
3. You will need at least 16GB DRAM to make this 18.1 64 bit build. The more the better.
Click to expand...
Click to collapse
You're the man! Thanks so much for your help here.
I'm on it!