I'm getting this build error when trying to compile CM-11.0. When this error occurs, I can try compiling again (brunch hammerhead) and the error will go away but pop up in another section as you can see in the pastebin. I've setup another directory where I re-synced the stock cm-11.0 repo and was able to complete the build. Upon installing the phone failed to boot, so I'm not sure what happened there (I think it was my proprietary files). The only changes I've made to the stock cm version are I've forked frameworks_base, apps_Settings, and the android manifest. I've been able to compile with the forks in the past, but when I forked the android manifest that's when this error started popping up.
Windows 8.1
VMWare : Ubuntu 13.10
Java : Initially was using Oracle version 7 but switched to openjdk 6 to try and troubleshoot
http://pastebin.com/rcPuGnXT
Solved: I've solved this issue but don't know why it was occurring in the first place. It was due to my lack of understanding of repo and git. When I was fetching and and merging the upstream changes, I wasn't committing and pushing those back to my forked repo. Once I did that everything went back to normal.
Related
Hi.
I want to compile a kernel driver (gator) for a nexus 5 and 5 devices.
I want to compile just the kernel, not the whole system, i know how to repack the kernel in the boot.img and upload to the device, that's not an issue.
I checked out the right kernel branch and extra binaries (i have the whole repo really for android platform development).
The insturctions in source.google.com are pretty ****ty and probably not up to date since they do not work.
Also if i try to use
Code:
$ git checkout [commig_hash]
where commit_hash is the hash i take from the kernel version in the "about" screen of my phone (official nexus 4 image) i get a reply that this commit does not exist.
There for it's probably a hash from googles private repo and not the public one.
Anyone knows how i can get the right hash\branch\tag for my image (one for 4.2.2 and one for 4.3).
Can someone explain why no Cm13 for d850 but for every other carrier? Use to be ATT always gets updates first.
Link to download
https://www.androidfilehost.com/?a=show&w=files&flid=42910
Link to thread
http://forum.xda-developers.com/lg-g3/general/cm13-lg-g3-test-builds-t3245744
underscorenorm said:
Link to download
https://www.androidfilehost.com/?a=show&w=files&flid=42910
Link to thread
http://forum.xda-developers.com/lg-g3/general/cm13-lg-g3-test-builds-t3245744
Click to expand...
Click to collapse
is it reliable ?
I need the external SD card, and Marshmallow is kinda weird with formatting as internal right now, so I didn't use it long, -I didn't any improvements to battery life either, so I wouldn't say it's great right now, but there are a few ROMs out there based on cm13.
FawkiDied said:
is it reliable ?
Click to expand...
Click to collapse
It's not that difficult...
Update:
Have built and posted CM13 ROM for d850 with working GPS. See this thread.
It's not terribly difficult to build your own "unofficial" CM13 ROM image for the d850. I did it this morning (12/19). I was surprised that most everything works, more or less, except for GPS which is still dead as a doornail.
The only difficult part of building CM yourself is the initial setup of a build environment. After that, any time you want the latest-and-greatest you just sync the environment to the latest changes, which takes maybe a minute, and then start the build – which can take a couple/few hours. Best done last thing before you go to bed. Cyanogenmod has good instructions here: https://wiki.cyanogenmod.org/w/Build_for_d850. When you follow the instructions to build CM-12.1 just substitute CM-13.0.
A few hints:
Your version of java
The CM13 build will fail with anything other than Oracle Java 1.7.xxx. No, it will not build with 1.8. No, it will not build with 1.6. No, it will not build with open openjdk or icedtea anything. I had to uninstall Oracle Java 1.8 to prevent its being used by default even though I had manually specified to use Oracle Java 1.7.
The vendor blobs
The instructions will say at one point to extract the vendor proprietary blobs from your current version of CM13. Huh? Not too helpful there. Use the blobs that TheMuppets has pulled together on github. https://github.com/TheMuppets/proprietary_vendor_lge/tree/cm-13.0. Additional hint: It's a whole lot easier to download the zip than it is to set up a proper git environment to retrieve them. Using git is like taking a howitzer out to hunt rabbits, in this case.
Installing
Copy the newly created .zip image from $OUT to your phone storage by your favorite means. Also copy over a version of gapps for CM13 (Android 6). First, manually wipe system. Then flash your new CM13 image and a CM13 compatible version of gapps at the same time. If you don't then the upgrade from 12.1 to 13 will fail when CM13 starts. Apparently Google Play Store is launched, and if it is not CM13 (Android 6) compatible it will repeatedly abort during the upgrade process. You can find several configurations of gapps for CM13 here: http://opengapps.org/. The "mini" for Android 6 works great for me. If you do this then it seems possible to do the upgrade "dirty"; that is, wiping cache and delvik but not apps and data. That saves a whole lot of time not having to restore that stuff. (Yeah, I can hear the incoming rounds now.)
Rebuilding after first build
I didn't use ccache at first, hoping to avoid additional complexity the first few builds. However, it works great, reducing rebuild time to just over ten minutes on subsequent builds after its first use. Use ccache.
Also, I created a super-simple shell script to initiate a rebuild. It's run from android/system/
Code:
#!/bin/bash
# sync with repository and initiate rebuild using ccache
# see https://wiki.cyanogenmod.org/w/Build_for_d850
repo sync
source build/envsetup.sh
breakfast d850
export USE_CCACHE=1
prebuilts/misc/linux-x86/ccache/ccache -M 50G
croot
brunch d850
echo "end of rebuild script"
Good luck, and let's hope a maintainer for cm13 d850 shows up soon!
Hello, can someone give me a hint, howto build Lineage (based on the work of @SyberHexen) on my own?
I think the most work is done, but I wan't to dig a bit deeper into it.
I know there are several guides, specific to one device but I don't know how to include the sources of SyberHexen.
Thanks!
Setup your build environment with Java and all the required packages. Setup repo and grab the source code. Clone the device, kernel and vendor trees. Go through the steps to initialize your build system then build the ROM.
hello i was looking for a samsung G928G S6 (Edge plus) kernel that has a drivedroid support but i was unable to find one.
since i am familiar with linux system i decided to try and build my first kernel.
i downloaded a stock kernel source from
https://opensource.samsung.com/uploadSearch?searchValue=g928
and other custom lineage os kernel from github
https://github.com/universal7420/android_kernel_samsung_universal7420
following this guide
https://forum.xda-developers.com/galaxy-s6/general/guide-how-to-build-samsung-kernel-july-t3429355
and this guide.
https://forum.xda-developers.com/an...erence-how-to-compile-android-kernel-t3627297
this are the steps that i did
export CROSS_COMPILE=$(pwd)/bin/aarch64-linux-android-
export ARCH=arm64 && export SUBARCH=arm64
when i came to make clean step i was getting this error
aarch64-linux-android-4.9/bin/aarch64-linux-android-gcc: No such file or directory
i noticed in my toolchain folder aarch64-linux-android-gcc was missing
so i downloaded some other toolchains until i found one that has gcc
moving to next steps
make clean
make mrproper
make exynos7420-zenlte_defconfig based on stock kernel and
make lineageos_zenlte_defconfig based on lineage os kernel
when i did the make -j$(nproc --all) i get this error
make: *** [Makefile:552: scripts] Error 2 and when i checked in Makefile line 552 i found this
$(Q)$(MAKE) $(build)=$(@)
i get this error everytime i try. i use Arch linux i tried in Ubuntu same thing
Cool How about Kali-linux mod did you check it?
We have Kali-Linux mod for S6 it has drive-droid build-in
Johannes89 said:
Cool How about Kali-linux mod did you check it?
We have Kali-Linux mod for S6 it has drive-droid build-in
Click to expand...
Click to collapse
i tried it yesterday but it hangs on creating image since my device is s6 edge+ not s6
Try to create img file from other source like windows or other program and move it to your phone
so i followed your advice and tried to build on windows 10 ubuntu from their store (though i hate using windows) and it was a success. i patched drivedroid stuff in the kernel
i build one from samsung official kernel and boom! drivedroid works , after a minute i experience some never ending bootloops , in 30 seconds i can use my phone after that it boots again, the loop never ends.
i clone another kernel the lineage one , after spending the whole day building , failing ,errors , bugs, electricity issue and stuff ,
I HAVE FINALLY HAVE A DEVICE THAT WORKS NO BOOTLOOPS AND DRIVEDROID IS WORKING. though the lineage os rom has some camera problems . But yeah it was a good day
Device tree: https://github.com/Bush-cat/android_device_samsung_gts7xlwifi
Kernel tree: https://github.com/Bush-cat/android_kernel_samsung_gts7xl
Vendor tree: WIP
Common tree: https://github.com/Bush-cat/android_device_samsung_gts7xl-common
Rom source: https://github.com/LineageOS/android/tree/lineage-18.1
Build Error: https://del.dog/motuxyrevi
Problem: hiddenapi.cc:58] No boot DEX files specified. I checked the hiddenapi.cc code and it shouldn't need dex files because it's only needed for encode. All stubs files were created successfully.
(don't look at my messy commits, I will clean them when I get a good build)
steps I tried: remove the boot dex if from hiddenapi; compile los 17.1; differrent Linux Systems (ubuntu 20.04 running in wsl2, native ubuntu 20.04, Linux mint 20.1), lots of try and error in the board config
I feel so stupid rn, the fix was changing the base makefiles, I probably removed one sometime to fix another error but now it's working
Bushcat said:
I feel so stupid rn, the fix was changing the base makefiles, I probably removed one sometime to fix another error but now it's working
Click to expand...
Click to collapse
What makefile did you replace (I have same issue)
Idk anymore, I think boardconfig