Related
hi i wanna build jellybean for my phone and i need help
please consider me a complete NOOB cause i barely got the kitchen running but it doesnt work with this phone so...
got it rooted with No Problem though
thanx to everyones work that got me this far
ps im running rooted stock rom willing to help as much as i can to get help just tell me what to do maybe we can help each other
...you can build your own rom, but maybe is better leave it on Skrilax_CZ
http://forum.xda-developers.com/showthread.php?t=2159708
then how will i learn?
CornholioGSM said:
...you can build your own rom, but maybe is better leave it on Skrilax_CZ
http://forum.xda-developers.com/showthread.php?t=2159708
Click to expand...
Click to collapse
ok so i went as far as downloading the JB source from AOSP
i have everything installed needed for the build
whats next? cause when i try to issue:
lunch full_asanti_c-userdebug
i get the following error:
build/core/product_config.mk:205: *** No matches for product "full_asanti_c". Stop.
** Don't have a product spec for: 'full_asanti_c'
** Do you have the right repo manifest?
It has to be properly ported to Photon Q first.
how?
Skrilax_CZ said:
It has to be properly ported to Photon Q first.
Click to expand...
Click to collapse
what are the steps to do that?
That's very specific for each platform - by simply making each feature working. You can use my CM10 device / vendor repos as a base.
I believe Cyanogenmod has an article in their wiki explaining how to build for a "new" device.. Even for a device that is already in the "lunch combo" you will still run into make errors without the right GCC compiler, kernel source, and proprietary files....
EDIT: Then once you get it to compile you also gotta create a "signed zip" with some more vodo... :/
Sent from my XT897 using Tapatalk 2
First off, I just want to say I don't mean to step on anyone's toes. Thanks for all the work so far from digitalhigh, bracketslash, santod040 and everyone who has posted information about or commits to the CM12 build tree. This is not my code, all I have done is disable enough stuff to get it to build and boot. A LOT OF STUFF IS BROKEN. This is intended for developers only right now. I will try to update the builds as I can but please don't expect true nightly builds.
DISCLAIMER: I am in no way responsible for malfunctioning or bricked devices if you run this software. If you do not agree to these terms, DO NOT DOWNLOAD. Again, this is seriously broken right now.
What doesn't work:
-Almost everything
What works:
-Wifi
-Touchscreen
-Sound
Changelog:
Merged (compare to build date)
Open (not in build yet)
Installation notes:
As I have yet to find a way to easily disable NFC for the builds, you will have to remove the /system/app/Nfc to stop those force closes. I just went to TWRP, mounted system, then ran "rm -rf /system/app/Nfc" to disable NFC for now.
Downloads:
2014-11-17: Download (Android File Host)
Edit: Please see bracketslash's thread for future downloads: http://forum.xda-developers.com/ver...ment/cm12-unofficial-unstable-builds-t2941198
bring it on bro
This saved me some time. Guess I'll see what I can do.
There was a new commit added to the open section that "adds dependency on device/qcom/sepolicy"
http://review.cyanogenmod.org/#/q/status:open+project:CyanogenMod/android_device_htc_m8,n,z
That was fast!
krazie1 said:
There was a new commit added to the open section that "adds dependency on device/qcom/sepolicy"
http://review.cyanogenmod.org/#/q/status:open+project:CyanogenMod/android_device_htc_m8,n,z
Click to expand...
Click to collapse
Thanks for info. I'll probably just wait on that one to get merged as so much is broken already. I doubt selinux will be the cause of frustration right now Also for anyone interested I made the following modifications to the cm12.0 branch to get this to build:
1) Created local_manifest.xml with muppeteers 12.0 branch
2) Commented out DotCase line in device/htc/m8/device.mk (has issues building)
3) Commented out ro.cwm.forbid_mount and ro.cwm.forbid_format lines in device/htc/m8/system.prop (too long)
4) Added missing overlay resources to main resources (copy the missing variables from build/overlay/frameworks/blah.xml to frameworks/blah.xml)
Ive been patiently waiting for cm12 on this beast
This should be in HTC one m8 original development not the Verizon section. If you want more attention and to help people out repose there
jake.99x3 said:
This should be in HTC one m8 original development not the Verizon section. If you want more attention and to help people out repose there
Click to expand...
Click to collapse
Given the intro post on the "original development" forums, I feel my topic is still more applicable in this section.
http://www.xda-developers.com/android/introducing-original-development-forums-for-more-devices/
djh816 said:
Given the intro post on the "original development" forums, I feel my topic is still more applicable in this section.
http://www.xda-developers.com/android/introducing-original-development-forums-for-more-devices/
Click to expand...
Click to collapse
Good point so then move it to android development. Cm is for all device variants not specifically verizon and won't get Much attention here.
jake.99x3 said:
Good point so then move it to android development. Cm is for all device variants not specifically verizon and won't get Much attention here.
Click to expand...
Click to collapse
While I agree it may not get as much attention, I still think this is the proper place. Android development (not m8 android development) is more for universal android projects or new code bases or ROMs for devices that don't have their own sub forum. That being said, this is a build of already existing code so it should go into a "development" section and given that I only plan to get this working on Verizon variant (as that's what I have) I avoided posting to the generic m8 sub forum. Mods can move as they feel fit but I think it belongs here Feel free to repost any info I have here though.
I'm trying to build and I'm getting stuck on the proprietary binaries.
Specifically this:
Code:
make: *** No rule to make target `vendor/htc/m8/proprietary/bin/adsprpcd', needed by `/home/build/cm12/out/target/product/m8/system/bin/adsprpcd'. Stop.
Any advice?
-xdadevelopers-user
xdadevelopers-user said:
I'm trying to build and I'm getting stuck on the proprietary binaries.
Specifically this:
Code:
make: *** No rule to make target `vendor/htc/m8/proprietary/bin/adsprpcd', needed by `/home/build/cm12/out/target/product/m8/system/bin/adsprpcd'. Stop.
Any advice?
-xdadevelopers-user
Click to expand...
Click to collapse
Hmm I didn't run into this. I just used the get-prebuilts command and didn't have any issue after. I followed these but modified for 12.0 branch:
http://forum.xda-developers.com/ver.../how-to-build-cm11-htc-one-m8-082714-t2860056
Just make sure your local_manifest.xml file has the 12.0 muppeteers branch as shown in example on page 6 of that thread.
djh816 said:
Hmm I didn't run into this. I just used the get-prebuilts command and didn't have any issue after. I followed these but modified for 12.0 branch:
http://forum.xda-developers.com/ver.../how-to-build-cm11-htc-one-m8-082714-t2860056
Just make sure your local_manifest.xml file has the 12.0 muppeteers branch as shown in example on page 6 of that thread.
Click to expand...
Click to collapse
@djh816
Hi compile ROM cm11 for a different device
Could you tell me which Java version are you using to build cm12, since you have just built cm12?
I tried to built cm12 yesterday and I got an error for Java so I installed OpenJDK7 and the it started building but I am getting a lot of non-device related error saying "internal compilation error"
I even tried removing all java version and re-installing OpenJDK7. Set alterantives too but no luck.
So please could you let me know which Java Version are you using for building cm12?
OpenJDK7 or Oracle/sun 7
Thanks
macs18max said:
@djh816
Hi compile ROM cm11 for a different device
Could you tell me which Java version are you using to build cm12, since you have just built cm12?
I tried to built cm12 yesterday and I got an error for Java so I installed OpenJDK7 and the it started building but I am getting a lot of non-device related error saying "internal compilation error"
I even tried removing all java version and re-installing OpenJDK7. Set alterantives too but no luck.
So please could you let me know which Java Version are you using for building cm12?
OpenJDK7 or Oracle/sun 7
Thanks
Click to expand...
Click to collapse
I started with clean ubuntu 14.04 lts x64 and added the packages from bracketslash's thread here. Then I just installed openjdk-7-jdk and openjdk-7-jre after that.
djh816 said:
While I agree it may not get as much attention, I still think this is the proper place. Android development (not m8 android development) is more for universal android projects or new code bases or ROMs for devices that don't have their own sub forum. That being said, this is a build of already existing code so it should go into a "development" section and given that I only plan to get this working on Verizon variant (as that's what I have) I avoided posting to the generic m8 sub forum. Mods can move as they feel fit but I think it belongs here Feel free to repost any info I have here though.
Click to expand...
Click to collapse
HTC One M7 has fully working CM12 build, and that is in ANDROID DEVELOPMENT SECTION The Op said that he has working CM12 rom for M8, you might ask him for advice, how to make your build more stable and with less bugs. That's my opinion anyways. You can check the build for M7 here http://forum.xda-developers.com/htc-one/development/5-0-lollipop-unofficial-cm12-android-5-0-t2943826 :good:
djh816 said:
Thanks for info. I'll probably just wait on that one to get merged as so much is broken already. I doubt selinux will be the cause of frustration right now Also for anyone interested I made the following modifications to the cm12.0 branch to get this to build:
1) Created local_manifest.xml with muppeteers 12.0 branch
2) Commented out DotCase line in device/htc/m8/device.mk (has issues building)
3) Commented out ro.cwm.forbid_mount and ro.cwm.forbid_format lines in device/htc/m8/system.prop (too long)
4) Added missing overlay resources to main resources (copy the missing variables from build/overlay/frameworks/blah.xml to frameworks/blah.xml)
Click to expand...
Click to collapse
You don't need to do all of that.
There's one commit and everything works just fine.... nothing's broken.
http://review.cyanogenmod.org/#/c/76760
...and you may just want to thank invisiblek in your original post. He's the only one that did all of the work to bring up the device.
Gunman84 said:
HTC One M7 has fully working CM12 build, and that is in ANDROID DEVELOPMENT SECTION The Op said that he has working CM12 rom for M8, you might ask him for advice, how to make your build more stable and with less bugs. That's my opinion anyways. You can check the build for M7 here http://forum.xda-developers.com/htc-one/development/5-0-lollipop-unofficial-cm12-android-5-0-t2943826 :good:
Click to expand...
Click to collapse
calling @santod040 for some cm love for m8vzw
munchy_cool said:
calling @santod040 for some cm love for m8vzw
Click to expand...
Click to collapse
if someone wants to make a donation to me, i will cherry pick a commit and brunch a completely working build (apart from universal cm issues).
ajrty33 said:
if someone wants to make a donation to me, i will cherry pick a commit and brunch a completely working build (apart from universal cm issues).
Click to expand...
Click to collapse
Welcome to XDA ..
Lollipop Red M8
The developer site is still listing KitKat as the newest build, so here are the links to the instructions to build Lollipop using the official source:
Lollipop 5.0: http://nv-tegra.nvidia.com/gitweb/?...a=blob_plain;f=README;hb=rel-st8-l-r1-partner
Lollipop 5.0.1: http://nv-tegra.nvidia.com/gitweb/?...a=blob_plain;f=README;hb=rel-st8-l-r2-partner
Cheers mate. It is still listing the 1.2.1 OTA as the latest but just by changing the branch url i was able to find the newest.
Lets hope for some more development on this device. I'm going to PM you soon - I will be building my own ROM and/or Kernel.
berryman13 said:
Cheers mate. It is still listing the 1.2.1 OTA as the latest but just by changing the branch url i was able to find the newest.
Lets hope for some more development on this device. I'm going to PM you soon - I will be building my own ROM and/or Kernel.
Click to expand...
Click to collapse
You do realize those are the links posted above. There is no need to switch branch names or search for the current files. Just click the one you want.
twistedumbrella said:
You do realize those are the links posted above. There is no need to switch branch names or search for the current files. Just click the one you want.
Click to expand...
Click to collapse
Of course, mate!
I was saying that I found the proper page by changing the URL to hb=rel-st8-l-r2-partner, before this thread was posted. So I appreciate you enlightening other folks about it!
berryman13 said:
Of course, mate!
I was saying that I found the proper page by changing the URL to hb=rel-st8-l-r2-partner, before this thread was posted. So I appreciate you enlightening other folks about it!
Click to expand...
Click to collapse
Even without already having the branch name, it's just a matter of going to http://nv-tegra.nvidia.com/gitweb/?p=manifest/android/binary.git;a=summary to find it
Hi, @twistedumbrella could you please spare a second to help (or point me in the right direction) I've successfully built Lollipop for my Oneplus One using Ubuntu, but when I try to set up first repo sync; well see below:
When I run: repo init -u git://nv-tegra.nvidia.com/manifest/android/binary.git -b rel-st8-l-r2-partner -m tlk/shieldtablet.xml
I get: fatal: manifest 'tlk/shieldtablet.xml' not available
fatal: remote github not defined in /home/diigimatrix/.repo/manifests/tlk/shieldtablet.xml
Please could you get me on my way. I love all your work and hope to gain further knowledge through your support.
Thanks in advance
Phil from Blackpool
diigibio said:
Hi, @twistedumbrella could you please spare a second to help (or point me in the right direction) I've successfully built Lollipop for my Oneplus One using Ubuntu, but when I try to set up first repo sync; well see below:
When I run: repo init -u git://nv-tegra.nvidia.com/manifest/android/binary.git -b rel-st8-l-r2-partner -m tlk/shieldtablet.xml
I get: fatal: manifest 'tlk/shieldtablet.xml' not available
fatal: remote github not defined in /home/diigimatrix/.repo/manifests/tlk/shieldtablet.xml
Please could you get me on my way. I love all your work and hope to gain further knowledge through your support.
Thanks in advance
Phil from Blackpool
Click to expand...
Click to collapse
I'm trying to figure out what's up with it now. I know when I synced it was r1, and tlk/shieldtablet.xml was valid.
Hopefully I can track down why it is coming back invalid in r2.
Thanks @twistedumbrella, glad in a way its not just me. Thought I was running the wrong command. . Happy New Year!
diigibio said:
Thanks @twistedumbrella, glad in a way its not just me. Thought I was running the wrong command. . Happy New Year!
Click to expand...
Click to collapse
Same to you. It updated ok but now I have to see if it'll re-init. It may be a delay on their end. The readme for the portable was up a week before the source.
Cool. I'll give it another try once I've finished work. Been a member for years and helped a lot in the old windows phone days. But thought enough of just relying on other people, time to start getting my hands dirty again. But new to building Android. Need to read up on manipulation of ROMs rather than just building a stock ROM. Any tips on tools to manipulate ROMs? Am i right by merging commits then build, then manipulate ROM? I will read up on it but just thought you might have some pointers. Thanks
diigibio said:
Cool. I'll give it another try once I've finished work. Been a member for years and helped a lot in the old windows phone days. But thought enough of just relying on other people, time to start getting my hands dirty again. But new to building Android. Need to read up on manipulation of ROMs rather than just building a stock ROM. Any tips on tools to manipulate ROMs? Am i right by merging commits then build, then manipulate ROM? I will read up on it but just thought you might have some pointers. Thanks
Click to expand...
Click to collapse
Best bet is to either find something you like and merge it or try to find something similar and recreate it to start. Once you get comfortable, then start coming up with your own.
Building from source is mostly Java for modifying with some C for drivers and such. Usually when you have a device configuration already set up, though, the C part is already done.
Just wanna say a big thanks to @twistedumbrella. I set up a new ubuntu build environment and I'm now compiling my first Android build for Nvidia Shield Tablet EU-LTE. No mods yet other than stock, but hopefully with time.
diigibio said:
Just wanna say a big thanks to @twistedumbrella. I set up a new ubuntu build environment and I'm now compiling my first Android build for Nvidia Shield Tablet EU-LTE. No mods yet other than stock, but hopefully with time.
Click to expand...
Click to collapse
Glad to hear it's all up and running. Best of luck!
twistedumbrella said:
Glad to hear it's all up and running. Best of luck!
Click to expand...
Click to collapse
Hi! I'm trying to compile but get error trying no find:
./packages/apps/UnifiedEmail/src
After repo sync, I don't have "src" directory for this package.
Thnx in advance.
entelekia said:
Hi! I'm trying to compile but get error trying no find:
./packages/apps/UnifiedEmail/src
After repo sync, I don't have "src" directory for this package.
Thnx in advance.
Click to expand...
Click to collapse
It looks like they are still working out a few issues with new updates. I don't maintain the source, so the only advice I can provide is to keep on eye on nvidia's gitweb for when they publish a solution (or occasionally sync and try over), or attempt to fix it yourself (which usually only works if there is an issue with the code, not code missing altogether).
Compiled! I have resynchronized all the project from scratch from git repository.
I'm going to test the compiled ROM in my tablet, but I suppose, I have to provide almost the essential pack of Google apps (basic providers and play services).
I think to flash *.img files, except recovery.img (I'm on TWRP), and then install from TWRP PA Gapps. Is this approach correct?
Thnx in advance and regards.
EDIT: No luck booting custom rom (TWRP nor stock recovery...)
Seem's like there's a new source three version out:
repo init -u git://nv-tegra.nvidia.com/manifest/android/binary.git -b rel-st8-l-r3-partner -m tlk/shieldtablet.xml
GethPrime said:
Seem's like there's a new source three version out:
repo init -u git://nv-tegra.nvidia.com/manifest/android/binary.git -b rel-st8-l-r3-partner -m tlk/shieldtablet.xml
Click to expand...
Click to collapse
Anyone managed to build this one yet? Its not working for me..
Hi. I've always been curious to try to build a new aosp based ROM.
I know java but I don't know CPP... Only a bit. Anybody thinks I could start something? Even in a team, of course. Where to start?
enryfantasy said:
Hi. I've always been curious to try to build a new aosp based ROM.
I know java but I don't know CPP... Only a bit. Anybody thinks I could start something? Even in a team, of course. Where to start?
Click to expand...
Click to collapse
First of all, it depends on how much you already know.
There are numerous guides on how to build another existing custom ROM. I'd start with those first to be a little familiar with how a project is handled, but you could always just look for guides for building one from scratch AOSP if you wanted to.
There are plenty of guides on the internet, and if you run into an issue, someone else has likely already asked about it and received an answer.
Elluel said:
First of all, it depends on how much you already know.
There are numerous guides on how to build another existing custom ROM. I'd start with those first to be a little familiar with how a project is handled, but you could always just look for guides for building one from scratch AOSP if you wanted to.
There are plenty of guides on the internet, and if you run into an issue, someone else has likely already asked about it and received an answer.
Click to expand...
Click to collapse
Thanks. I'll try to look for something over AOSP
You interested in teaming?
DOBBY0 said:
You interested in teaming?
Click to expand...
Click to collapse
i am same as the guy who started this thread. and fyi im interested in teaming.
You can hit my up on Hangouts and we can discuss some stuff. My name is Michael Stevens. Hers my G+ page https://plus.google.com/u/0/+MichaelStevens_DOBBY0/about
burakd0gan said:
i am same as the guy who started this thread. and fyi im interested in teaming.
Click to expand...
Click to collapse
^^^^^^^^^^^^^
I'd also be interested in learning how to manage/develop a custom rom. Let's get Team n00b started up
I´m bumping this topic though the last answer is over one month ago
Creating, managing a Custom ROM of any kind is very time consuming and some people will always expect you to release updates as fast as possible and to work for free Even if you´ve set up your developing environment ( I use Linux ), you will need a lot of patience and a hell of a PC to compile stuff without waiting too long.
If I were you I would think twice if I want to a) build a ROM for yourself only or b) also go through the pain of maintaining a thread, webspace and online support.
The Nexus forums are crowded with AOSP based ROMs and I don´t think that one thread more or less would matter. What I build for myself simply needs to be reliable without 1000x different Mods or Themes.
Since I barely have any time for this hobby anymore, I stick to a) only and even by doing so, I will also waste a lot of time since sometimes there are unforeseen consequences
Yes. That's what I ended too. It would take too much time and resources. I just stopped thinking about that (because my linux pc is very old, too) and used a good ROM.
Thanks!
Quick question
I'm trying to build M developer preview from AOSP. I'm currently syncing the repo with the command:
Code:
repo init -u https://android.googlesource.com/platform/manifest.git -b android-m-preview
After this is synced I will add my device to the appropriate folder with the code:
Code:
git clone https://android.googlesource.com/device/lge/hammerhead.git -b android-m-preview hammerhead
After this will I be able to compile and build?
Am I on the right track?
t3al said:
Quick question
I'm trying to build M developer preview from AOSP. I'm currently syncing the repo with the command:
Code:
repo init -u https://android.googlesource.com/platform/manifest.git -b android-m-preview
After this is synced I will add my device to the appropriate folder with the code:
Code:
git clone https://android.googlesource.com/device/lge/hammerhead.git -b android-m-preview hammerhead
After this will I be able to compile and build?
Am I on the right track?
Click to expand...
Click to collapse
Correct me if I'm wrong, but you can just add the device specific code on the manifest (by modifying .repo/manifest/default.xml)
F4uzan said:
Correct me if I'm wrong, but you can just add the device specific code on the manifest (by modifying .repo/manifest/default.xml)
Click to expand...
Click to collapse
I didn't add my device on the manifest. I followed another guide specifically for my phone and AOSP.
Now, I'm stuck at this:
Code:
Header: out/target/product/hammerhead/obj/include/gps.utils//loc_log.h
make: *** No rule to make target `hardware/qcom/gps/utils/log_util.h', needed by `out/target/product/hammerhead/obj/include/gps.utils//log_util.h'. Stop.
make: *** Waiting for unfinished jobs....
Header: out/target/product/hammerhead/obj/include/gps.utils//loc_cfg.h
I used the Preview binaries from Google.
Does this mean the latest blobs do not compile for M?
Edit: Found my answer here
Hello Moto G community!
I am a newbie to Android development but I have a will to learn and work hard. I would like to obtain help from developers while I embark on a mission to build a Android ROM for our beloved Moto G falcon.
What I already did:
1. Setup AOSP build environment from Android official tutorial and had a successful build of nougat 7.1.1
2. Currently, I have setup the build environment for lineage-os using this guide:
https://forum.xda-developers.com/chef-central/android/how-to-build-lineageos-14-1-t3551484
A Lineage 14.1 build is in progress as I write this and hopefully there will be no errors. I plan to flash it on my device and try it out personally to see for myself how well it turns out to be. *Done
Plan:
1. I wish to build an Android 8.x ROM eventually. Lineage is not ready yet, so I was thinking of going ahead with AOSP. Correct me if I am wrong.
2. If I do that, I will first have to build the falcon device tree. I will follow some tutorials for that but will need help here.
3. When I am done with that, I will start the building process and that is when the real work starts.
I will start building the device tree in 2-3 days and will post for help wherever required. I will keep this thread updated with my progress and resources as well.
Anybody who is willing to work with me on this project is welcome to do so. Send me a PM and we can be a team.
To moderators:
1. This is my first time creating a thread on XDA Forums. If I made a mistake, please let me know.
2. This is not just another Android Oreo thread. I plan to learn Android device development and coincidentally the time matches with Android O release. Possibly a good time to learn
My Devices:
Moto G (falcon) XT1033 India
Moto G4 Plus (athene) XT1644 US
this is great, good luck bro, i am waiting for android O :laugh::fingers-crossed:
Here comes the first one:
Lineage 14.1 arm-eng
Code:
[ 39% 13388/33953] Building with Jack: /media/viraj/Work/Android/Dev/android_lineage_14.1/out/target/common/obj/JAVA_LIBRARIES/framework_intermediates/with-local/classes.dex
FAILED: /bin/bash /media/viraj/Work/Android/Dev/android_lineage_14.1/out/target/common/obj/JAVA_LIBRARIES/framework_intermediates/with-local/classes.dex.rsp
java.lang.AssertionError: java.util.zip.ZipException: duplicate entry: jayce/com/android/internal/inputmethod/InputMethodSubtypeSwitchingController$ImeSubtypeListItem.jayce
at com.android.sched.vfs.WriteZipFS$ZipEntryOutputStream.writeEntryIfNeeded(WriteZipFS.java:350)
at com.android.sched.vfs.WriteZipFS$ZipEntryOutputStream.close(WriteZipFS.java:320)
at com.android.sched.vfs.VFSToVFSWrapper.dumpToDir(VFSToVFSWrapper.java:127)
at com.android.sched.vfs.VFSToVFSWrapper.dumpToDir(VFSToVFSWrapper.java:112)
at com.android.sched.vfs.VFSToVFSWrapper.dumpToDir(VFSToVFSWrapper.java:112)
at com.android.sched.vfs.VFSToVFSWrapper.dumpToDir(VFSToVFSWrapper.java:112)
at com.android.sched.vfs.VFSToVFSWrapper.dumpToDir(VFSToVFSWrapper.java:112)
at com.android.sched.vfs.VFSToVFSWrapper.dumpToDir(VFSToVFSWrapper.java:112)
at com.android.sched.vfs.VFSToVFSWrapper.close(VFSToVFSWrapper.java:99)
at com.android.sched.vfs.ReadWriteZipFS.close(ReadWriteZipFS.java:87)
at com.android.sched.vfs.GenericOutputVFS.close(GenericOutputVFS.java:56)
at com.android.jack.library.v0002.OutputJackLibraryImpl.close(OutputJackLibraryImpl.java:218)
at com.android.jack.Jack.run(Jack.java:742)
at com.android.jack.Jack.checkAndRun(Jack.java:412)
at com.android.jack.CommandLine.runJack(CommandLine.java:79)
at com.android.jack.api.v01.impl.Cli01CompilationTaskImpl.run(Cli01CompilationTaskImpl.java:85)
at com.android.jack.server.tasks.JackTask.handle(JackTask.java:188)
at com.android.jack.server.tasks.SynchronousServiceTask.handle(SynchronousServiceTask.java:49)
at com.android.jack.server.tasks.JackTaskRawOut.handle(JackTaskRawOut.java:34)
at com.android.jack.server.router.ContentTypeRouter.handle(ContentTypeRouter.java:86)
at com.android.jack.server.router.PartParserRouter.handle(PartParserRouter.java:95)
at com.android.jack.server.router.PathRouter.handle(PathRouter.java:68)
at com.android.jack.server.router.ContentTypeParameterRouter.handle(ContentTypeParameterRouter.java:88)
at com.android.jack.server.router.ContentTypeRouter.handle(ContentTypeRouter.java:86)
at com.android.jack.server.router.ContentTypeRouter.handle(ContentTypeRouter.java:86)
at com.android.jack.server.router.ContentTypeRouter.handle(ContentTypeRouter.java:86)
at com.android.jack.server.router.ContentTypeParameterRouter.handle(ContentTypeParameterRouter.java:88)
at com.android.jack.server.router.ContentTypeRouter.handle(ContentTypeRouter.java:86)
at com.android.jack.server.router.MethodRouter.handle(MethodRouter.java:69)
at com.android.jack.server.router.RootContainer.handle(RootContainer.java:51)
at org.simpleframework.http.core.RequestDispatcher.dispatch(RequestDispatcher.java:121)
at org.simpleframework.http.core.RequestDispatcher.run(RequestDispatcher.java:103)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.util.zip.ZipException: duplicate entry: jayce/com/android/internal/inputmethod/InputMethodSubtypeSwitchingController$ImeSubtypeListItem.jayce
at java.util.zip.ZipOutputStream.putNextEntry(ZipOutputStream.java:232)
at com.android.sched.util.file.OutputZipFile$CustomZipOutputStream.putNextEntry(OutputZipFile.java:150)
at com.android.sched.vfs.WriteZipFS$ZipEntryOutputStream.writeEntryIfNeeded(WriteZipFS.java:346)
... 34 more
Internal compiler error (version 1.2-rc4 'Carnac' (298900 f95d7bdecfceb327f9d201a1348397ed8a843843 by [email protected])).
java.util.zip.ZipException: duplicate entry: jayce/com/android/internal/inputmethod/InputMethodSubtypeSwitchingController$ImeSubtypeListItem.jayce.
Warning: This may have produced partial or corrupted output.
Couldn't find a solution to this not-so-rare problem.
I just re-ran
Code:
brunch falcon
and did not see that error again. It is not reproducible.
Now I am stuck at Out of Memory error for the same file. I tried reducing max-services for jack server in config file to 1.
I tried multiple heap sizes (2,4,6,8 GB) using -Xmx flag. No luck.
I am curious as to why AOSP built successfully and LOS is showing these errors. They both use jack-server right?
I will search for a solution for a few hours now. If anyone has any, please let me know.
Edit: Alright! I made a build without using ninja.
Code:
export USE_NINJA=false
brunch falcon
Took longer, but succeeded. It boots but SetupWizard stops after setting up Google account. Cannot bypass it to home. Deleting LineageSetupWizard in /system/priv-app using adb works.
See screenshot below.
This completes 1 task. I can start building the device tree tomorrow.
great still like this
Can you tell me size of source code ?? How long it will take to download source code
Trying to build aosp O today. Still syncing
FortoszoneID said:
Trying to build aosp O today. Still syncing
Click to expand...
Click to collapse
That is something! I'd like to test this build if you are successful.
Me too
Sent from my Moto G4 Plus using XDA-Developers Legacy app
Good step dude...
Just one request "Please focus to build Stable one rather then frequent unstable update"
I hope they do not abandon this project is very good
SunilSuni said:
Can you tell me size of source code ?? How long it will take to download source code
Click to expand...
Click to collapse
Source code should be somewhere between 20-40 GB
virajmalia said:
Source code should be somewhere between 20-40 GB
Click to expand...
Click to collapse
40 GB more likely