Hi there,
Today I set up my machine to start building omni Rom for my Nexus 7 gsm (tilapia)
I followed the guide from the wiki for the Nexus 4 and changed it to suit the tilapia.
After I finished I got some errors about grouper Commons files missing so I guessed that the tilapia builds rely on the grouper(Nexus 7 wifi) and executed breakfast for grouper, too.
Afterwards the build started, however it gave me an error /warning to begin with
"device/asus/tilapia/omni.Dependencies file not found"
As mentioned before, the build started nevertheless.
Will this render my build useless or is it one of the warnings that might occur without harm?
If so, How can I fix it?
Sent from my Nexus 7 using xda app-developers app
Build got aborted with error 9, corresponding to lack of ram according to several reports on the Web,
Anyone got an answer for my first post before I launch the building process again with more assigned ram?
Sent from my GT-I9100 using xda app-developers app
punshkin said:
Build got aborted with error 9, corresponding to lack of ram according to several reports on the Web,
Anyone got an answer for my first post before I launch the building process again with more assigned ram?
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
I don't have an answer for that or Error 9, but if you get a bizarre error about the nVidia Keymaster, go into the Keymaster.cpp file, find the offending file, and add "utils/" where it references it. Its UniqueP.h that was tripping up my Grouper buidls (before I ran out of hard drive space). Just a heads up, since it seems to be a Tegra binary issue.
dibblebill said:
I don't have an answer for that or Error 9, but if you get a bizarre error about the nVidia Keymaster, go into the Keymaster.cpp file, find the offending file, and add "utils/" where it references it. Its UniqueP.h that was tripping up my Grouper buidls (before I ran out of hard drive space). Just a heads up, since it seems to be a Tegra binary issue.
Click to expand...
Click to collapse
Thank you, I got that error an hour into my 2nd build, and fixed it as described in this thread, before I saw your post, which also fixed that key master error you mentioned.
https://groups.google.com/forum/#!topic/android-building/b66T0PzDIiM
About 1h30 into my 3rd build I was once again killed by signal 9
This time I had 3gb ram (out of 4) assigned to my virtual box
Does anyone know how much ram is needed to successfully build 4.4? I still have left about 400mb I can assign to the virtual box. Is it possible to set up swap for virtual Ubuntu installations or is there a way to reduce the resources needed by Ubuntu itself?
Code:
Preparing output jar [/home/buildbox/android/omni/out/target/common/obj/APPS/WallpaperCropper_intermediates/proguard.classes.jar]
* Copying resources from program jar [/home/buildbox/android/omni/out/target/common/obj/APPS/WallpaperCropper_intermediates/classes.jar]
Docs droiddoc: /home/buildbox/android/omni/out/target/common/docs/api-stubs
collect2: error: ld terminated with signal 9 [Killed]
make: *** [/home/buildbox/android/omni/out/target/product/tilapia/obj/SHARED_LIBRARIES/libwebviewchromium_intermediates/LINKED/libwebviewchromium.so] Error 1
make: *** Waiting for unfinished jobs....
DroidDoc took 87 sec. to write docs to /home/buildbox/android/omni/out/target/common/docs/api-stubs
Sent from my GT-I9100 using xda app-developers app
punshkin said:
Thank you, I got that error an hour into my 2nd build, and fixed it as described in this thread, before I saw your post, which also fixed that key master error you mentioned.
https://groups.google.com/forum/#!topic/android-building/b66T0PzDIiM
About 1h30 into my 3rd build I was once again killed by signal 9
This time I had 3gb ram (out of 4) assigned to my virtual box
Does anyone know how much ram is needed to successfully build 4.4? I still have left about 400mb I can assign to the virtual box. Is it possible to set up swap for virtual Ubuntu installations or is there a way to reduce the resources needed by Ubuntu itself?
Code:
Preparing output jar [/home/buildbox/android/omni/out/target/common/obj/APPS/WallpaperCropper_intermediates/proguard.classes.jar]
* Copying resources from program jar [/home/buildbox/android/omni/out/target/common/obj/APPS/WallpaperCropper_intermediates/classes.jar]
Docs droiddoc: /home/buildbox/android/omni/out/target/common/docs/api-stubs
collect2: error: ld terminated with signal 9 [Killed]
make: *** [/home/buildbox/android/omni/out/target/product/tilapia/obj/SHARED_LIBRARIES/libwebviewchromium_intermediates/LINKED/libwebviewchromium.so] Error 1
make: *** Waiting for unfinished jobs....
DroidDoc took 87 sec. to write docs to /home/buildbox/android/omni/out/target/common/docs/api-stubs
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
I've seen it said that you must have 4gb available, but I don't know. I can do a Tilapia build for you after Xmas if you like.
Sent from my Nexus 10
Wow thank you, that's a very generous offer!
The purpose of my build would not justify the trouble it would mean to you.
I started in order to learn how to compile builds on my own (this is kinda achieved I guess?) and to get my hands on a build with the multi window feature cherry picked.
I am nevertheless grateful for your offer
Sent from my GT-I9100 using xda app-developers app
/edit
looking at the commit (https://gerrit.omnirom.org/#/c/1510/)
all changes are in one of these folders
core/java/android/
packages/SystemUI/
policy/src/com/android/internal/policy/impl/
services/java/com/android/server/
would running
make core/java/android/
make packages/SystemUI/
make policy/src/com/android/internal/policy/impl/
make services/java/com/android/server/
Click to expand...
Click to collapse
result in 4 zips i could flash onto an install of omnirom to achieve the desired changes?
or would it only output the corresponding files into the out folder and i'd have to find a way to prepare a flashable zip?
or is this an unfeasible idea that won't work?
punshkin said:
Wow thank you, that's a very generous offer!
The purpose of my build would not justify the trouble it would mean to you.
I started in order to learn how to compile builds on my own (this is kinda achieved I guess?) and to get my hands on a build with the multi window feature cherry picked.
I am nevertheless grateful for your offer
Sent from my GT-I9100 using xda app-developers app
/edit
looking at the commit (https://gerrit.omnirom.org/#/c/1510/)
all changes are in one of these folders
core/java/android/
packages/SystemUI/
policy/src/com/android/internal/policy/impl/
services/java/com/android/server/
would running
result in 4 zips i could flash onto an install of omnirom to achieve the desired changes?
or would it only output the corresponding files into the out folder and i'd have to find a way to prepare a flashable zip?
or is this an unfeasible idea that won't work?
Click to expand...
Click to collapse
I'm actually unsure. Those get compiled into apk's. Not sure if they can be compiled independently
Sent from my Nexus 10
EDIT: In theory you can, just don't know hte HOW. Anyway, I'll be building for Grouper once I get my new hard drive for Christmas So Tilapia's about 2-3 seconds extra to compile.
dibblebill said:
I'm actually unsure. Those get compiled into apk's. Not sure if they can be compiled independently
Sent from my Nexus 10
EDIT: In theory you can, just don't know hte HOW. Anyway, I'll be building for Grouper once I get my new hard drive for Christmas So Tilapia's about 2-3 seconds extra to compile.
Click to expand...
Click to collapse
Apparently it's working core is in the makes.
Hopefully this will work with less ram, I only have to find a way to get the files to their destination.
Well if that is the case and multi window is still a wip by then a tilapia build would greatly be appreciated
Sent from my GT-I9100 using xda app-developers app
punshkin said:
Apparently it's working core is in the makes.
Hopefully this will work with less ram, I only have to find a way to get the files to their destination.
Well if that is the case and multi window is still a wip by then a tilapia build would greatly be appreciated
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
I'll let you know once I get that drive installed/cloned. My current drive reported 200.6 KILObytes after attempting a Grouper build... Of free space So I think 80GB is just too small for more than one device.
dibblebill said:
I'll let you know once I get that drive installed/cloned. My current drive reported 200.6 KILObytes after attempting a Grouper build... Of free space So I think 80GB is just too small for more than one device.
Click to expand...
Click to collapse
Yip, a little low on free space. Is that 80gb for your whole system or just your building setup?
I have a dedicated virtual installation for building with 25gb ccache and it's close to 60gb total size
Sent from my GT-I9100 using xda app-developers app
punshkin said:
Yip, a little low on free space. Is that 80gb for your whole system or just your building setup?
I have a dedicated virtual installation for building with 25gb ccache and it's close to 60gb total size
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Story runs thus.
I run a custom desktop with a 2nd generation Intel i7 at 3.06GHz (quad-core, Hyperthreading), 12GB triple-channel XMP RAM, and a good graphics card. 1.5TB hard drive. I have WIndows 7 on that. I procured, in exchange for beer to an adult of legal age, a 80GB, 7200RPM notebook HDD which I put Linux on, and build on that. I'm replacing that 80GB drive with a new 3.5" 1TB drive. 64MB of cache. I plan to give it a ccache of around 50GB. Since I boot into a full Linux installation, I get to use the full power of that CPU and RAM, and boy does compilling Android kick that CPU's ass.
well my build core failed (no make file)
I added 16Gb swap and run over night and see what happens
I'm not done with this yet
Success!
after adding a 16gb swap partition the build finally finished
I wonder if I should share it with the community after verifying that it doesn't break devices.
I bet there are many people that would like to try the multi-window feature.
Do you think think the Omni "team" would be fine with me sharing my build?
Success!
after adding a 16gb swap partition the build finally finished
I wonder if I should share it with the community after verifying that it doesn't break devices.
I bet there are many people that would like to try the multi-window feature.
Do you think think the Omni "team" would be fine with me sharing my build?
punshkin said:
Success!
after adding a 16gb swap partition the build finally finished
I wonder if I should share it with the community after verifying that it doesn't break devices.
I bet there are many people that would like to try the multi-window feature.
Do you think think the Omni "team" would be fine with me sharing my build?
Click to expand...
Click to collapse
MOST definitely. I think its encouraged. Post your thread, formatted correctly, in Nexus 7/Android Devlopment (not original) for your device, I use mediafire as my host. See my thread for examples of simple formatting- I didn't get fancy. Then post a link to it in the Omni forum Device Mega List. Make sure to label it as unofficial.
dibblebill said:
MOST definitely. I think its encouraged. Post your thread, formatted correctly, in Nexus 7/Android Devlopment (not original) for your device, I use mediafire as my host. See my thread for examples of simple formatting- I didn't get fancy. Then post a link to it in the Omni forum Device Mega List. Make sure to label it as unofficial.
Click to expand...
Click to collapse
Alright, Here it is:
http://forum.xda-developers.com/showthread.php?p=48338988
I went with d-h.st as Hoster and posted to the Nexus 7 3G board, since the other ones are shared with Grouper.
Check it out and let me know, if there is something I missed
punshkin said:
Alright, Here it is:
http://forum.xda-developers.com/showthread.php?p=48338988
I went with d-h.st as Hoster and posted to the Nexus 7 3G board, since the other ones are shared with Grouper.
Check it out and let me know, if there is something I missed
Click to expand...
Click to collapse
for now i still have my skyrocket (deciding what to upgrade too ) but i wanted to share TeamRooks thread with you guys they are awesome devs and this thread is about 5 days worth of good reading and some learning
http://forum.xda-developers.com/showthread.php?t=1798056
Tweakecho said:
for now i still have my skyrocket (deciding what to upgrade too ) but i wanted to share TeamRooks thread with you guys they are awesome devs and this thread is about 5 days worth of good reading and some learning
http://forum.xda-developers.com/showthread.php?t=1798056
Click to expand...
Click to collapse
thank you, i just glanced over it but it seems very helpful
dibblebill said:
I'm actually unsure. Those get compiled into apk's. Not sure if they can be compiled independently
Sent from my Nexus 10
EDIT: In theory you can, just don't know hte HOW. Anyway, I'll be building for Grouper once I get my new hard drive for Christmas So Tilapia's about 2-3 seconds extra to compile.
Click to expand...
Click to collapse
Hey, do you have an idea how much additional hard drive space it's gonna take to build for grouper if i am already building for tilapia?
It thought that it shouldn't be much, since they are almost the same, but the tilapia folder in my outs folder is huge and if it's all gonna be copied into a separate grouper folder it's gonna be too much
punshkin said:
Hey, do you have an idea how much additional hard drive space it's gonna take to build for grouper if i am already building for tilapia?
It thought that it shouldn't be much, since they are almost the same, but the tilapia folder in my outs folder is huge and if it's all gonna be copied into a separate grouper folder it's gonna be too much
Click to expand...
Click to collapse
do you clear before you build again? make clobber will clean up your "out" with out killing your build times to bad as far as i can tell. All you need to do is get the proprietary blobs for the grouper from either CM or Google and let them place themselves in the Vendor/asus/ directory and then you can make breakfast grouper to pull down the needed repos. my grouper specific stuff is only ~70 MB so it wont be to bad for your Hard drive i don't think. so you'd have to pull down some other radio stuff extra is about all.
I do think doing the builds together will double the size of the output as now you will have an OUT/product/Grouper as well as a OUT/product/Tiliapia... but i'm just making assumptions
If anything you could build them one at a time.
I'm sure i'll be corrected by one of the real dev's if i'm wrong...
EDIT: did some digging in to all the directories and it looks like mose of the stuff is already there for tiliapia in my repo so you should have the grouper stuff too.... i think.. lol
Related
Everyone is allowed to make changes to the VMWare image and re-upload it. If you re-upload the VMWare image with the made corrections, post the download link(s) in this thread. I will update the first post.
If there is a AOSP Developer that is willing to make a complete tutorial, please make one that works and is up-to-date with 2.3.7
The more people we have working on making ROMs, the better.
This VMWare image is:
- Base: Ubuntu 10.04 LTS
- ICS ready
- Gingerbread ready
- Fully updated
- Eclipse with ADT Plugin
- Android Kitchen Integrated
PASSWORD: root
Latest changelog (Coming soon)
- Based on 10.04 LTS instead of 11.10
- Different approach
Download link:
Bypass 24h wait time, limit reached --> Solution? Reset your ip! In Belgium this is easy by restarting your modem/router. This may be different in other countries.
more mirrors will come!
Part 1
Part 2
Part 3
Image is extracted, where do I start?
Continue from this link
How to build 2.3.7 for Nexus S
This is just a snippet that may help you.
repo init -b android-2.3.7_r1 < /dev/null (This branch is ready to use with Nexus S and Nexus S 4G)
repo sync
source build/envsetup.sh
lunch full_crespo-userdebug
make -j8 (-j8 = for eightcores like 2600k, 2630QM / -j4 = for quads 2500K/2620M/Q6600 / -j2 for dual cores / ...)
Click to expand...
Click to collapse
Don't forget to add the vendor files of the device. You need to download the scripts as well of the driver binaries.
Click to expand...
Click to collapse
I tested a quick build. And it's working.
A virtual machine with limited RAM in order to compile AOSP? Definitively not a good idea. Why not dual boot? Sooooo easy to install the worst distro ever (*buntu).
This is awesome. My only problem is that I only have VMWare Workstation 7.
Super! Waiting for this
djjonastybe said:
Dear community,
I made a AOSP developer environment for VMWare Workstation 8 or latest VMWare Player (free).
You can use this VMWare image as a base to build AOSP ROMs. Imade it for those having trouble getting it to work or maybe if you don't have time to set it up properly. Well if you are downloading this you might have a good reason!
Anyway have fun!
If there are any errors let me know.
This VMWare image is:
- ICS ready
- Gingerbread ready
- Fully updated
Download link:
...uploading...
Click to expand...
Click to collapse
Who would have guessed that an android dev would have difficulty setting up a linux enviroment . . . go figure.
You do not have to be an Android Dev to compile Android. I haven't written a single line of code for Android and can compile AOSP 2.3.7 fine.
This is simply to save time. And if you have good enough hardware (like myself) compiling Android AOSP in a VM session works perfectly fine.
Most people that are into computers have a rocking system. I have 12GB ram, I dedicate 8 for my VM and the rest for my main OS (windows 7). Works fine, what's the issue?
Some people don't want to dual boot and sometimes a Linux distro doesn't support certain hardware or can't be installed.
I would appreciate it. THANKS
nice.....this could be very useful
Sent from my Nexus S using xda premium
FeaRThiS: Who would have guessed that an android dev would have difficulty setting up a linux enviroment . . . go figure.
Click to expand...
Click to collapse
You seem to be the only one against uploading this.
Guys I am still trying to upload it. I am splitting it in 700MB sizes. Crocko's uploadservice is down. I will upload it on depositfiles and multiupload
12,5%
@FeaRThiS just stated the obvious. I also think the first step to understand how to build an AOSP ROM is knowing how to setup the development environment.
I don't have anything against using a VMWare image. But, IMHO, considering the time for uploading/downloading the file, if you do the setup yourself (in VMWare or whatever), you should have already been compiling your ROM by now.
suksit said:
@FeaRThiS just stated the obvious. I also think the first step to understand how to build an AOSP ROM is knowing how to setup the development environment.
I don't have anything against using a VMWare image. But, IMHO, considering the time for uploading/downloading the file, if you do the setup yourself (in VMWare or whatever), you should have already been compiling your ROM by now.
Click to expand...
Click to collapse
Okay, its not useful for you two.
Next!
I like it and i will try it.
djjonastybe said:
You seem to be the only one against uploading this.
Guys I am still trying to upload it. I am splitting it in 700MB sizes. Crocko's uploadservice is down. I will upload it on depositfiles and multiupload
12,5%
Click to expand...
Click to collapse
I have nothing against it and it may even be useful in case of emergency when you can not access a linux machine, but as stated by @S suxeN the first step for any dev would be learning to create their own dev enviroment.
i didnt say that.
but the statement is right. Anyways i yet think this image is of great use, as you can always start from there, if u did something wront, what can always happen to nun-linux users.
I don't know anything about linux. Is Eclipse with ADT on here by any chance? If not, what IDE is there to develop with in this VM?
I didn't think that far. Eclipse is not installed.
But I will work on it for next release. For now you have to install it manually. I hope tomorrow evening the new vmware will be uploaded!
Hey guys, don't be so hard on the fella. He's doing us a great service in a way. Not all of us are able to bring laptops wherever we go, dual-boot, etc. I just downloaded this to my external drive that I use to keep my stuff on for work and it'll come in handy when I wanna test apps without worrying about nuking my phone.
Also, it helps that I can demo apps on the thing to co-workers on screen than using a phone. That way I won't have to worry about them screwing things up if they decided to 'explore.'
http://code.google.com/android/nexus/drivers.html#crespogwk74
Can someone help me with this? This has the binaries for the Nexus S.
Where do I place the scripts?
I have a vendor folder with several maps in it now. But I don't know what I have to do now.
I placed the 'vendor' folder in my working directory. But lunch isn't showing up crespo in the list.
These are my steps:
Building
I executed lunch. I realised I did not have crespo in the list. So next, I read the line 'Building for devices'.
Eventually I ended up here:
Building devices
Obtaining proprietary binaries
Starting with IceCreamSandwich, the Android Open-Source Project can't be used from pure source code only, and requires additional hardware-related proprietary libraries to run, specifically for hardware graphics acceleration.
Official binaries for Nexus S, Nexus S 4G, Galaxy Nexus, and PandaBoard can be downloaded fromGoogle's Nexus driver page, which add access to additional hardware capabilities with non-Open-Source code.
There are no official binaries for Nexus One, ADP2 or ADP1., ADP2 or ADP1.
Click to expand...
Click to collapse
I clicked the link and downloaded the GWK74 binaries.
Now then I read further:
Extracting the proprietary binaries
Each set of binaries comes as a self-extracting script in a compressed archive. After uncompressing each archive, run the included self-extracting script from the root of the source tree, confirm that you agree to the terms of the enclosed license agreement, and the binaries and their matching makefiles will get installed in the vendor/ hierarchy of the source tree.
Click to expand...
Click to collapse
I have the vendor hierarchy...
Do I have to put these files in:
my home folder/bin
OR
home folder/workingdirectory_name
Or what do I have to do now?
updated first post with small hint on how to download 2.3.7 for our Nexus S. Good luck!
yep, i think this is pretty awesome. for me, i'm not an android dev but i've dabbled with theming and porting mods from other phones to the epic 4G previously. i'd love to be able to start with a system ready to go and mess around with some guides to learn how to compile source, etc... thanks.
Nice image man, gonna give it a go later. Thought I'd put my word in the discussion , sure there lots of talented devs, but they have all got different hardware/software and time requirements. So this becomes a useful tool to add to the inventory.
The stock Webtop sucks in my opinion. A outstanding concept, but poorly executed.
I'm working right now in a "revamped version" of the stock one. I call it Xubuntop - A full XFCE4 desktop.
Xubuntu is originally a Ubuntu with XFCE4 environment and some optimizations. Check the original Xubuntu project (Google it)
I'm thinking in two versions: Lightweight and Full
Lightweight: flashed in Osh and ready to go!
Full: flashed in Osh and uses Webtop2sd to expand the internal disk space.
I know that many tried to do this and I warn you guys, I'm not rediscovering the wheel. It's just a "easy way" to get those extra applications using the Xubuntu as a base.
It will feature optimizations to make the environment as lightweight as possible, giving the CPU more room to process whatever you want to execute.
I'm working two weeks on this and maybe this will be ready Saturday, but I can't promise nothing
Maybe I'll need help to make the zip to use in CWM.
So... let's go back to work
I have a questions.
Is Xubuntop for cm7/9 roms or blur/stock roms ?
Will it be dependent on the broken/outdated Motorola packages?
By this I mean, will we be able to make full use of the repos to install newer versions of software that are dependent on newer versions these packages. (E.g. the latest verision of Chromium that I can get working now is version 4 due to its dependencies breaking webtop, even when apt-get has been fixed.)
xateeq said:
I have a questions.
Is Xubuntop for cm7/9 roms or blur/stock roms ?
Click to expand...
Click to collapse
Xubuntop should work fine with the Blur and Stock roms.
CM7/9 boots the Webtop from the Webtop2sd? If yes, then I guess the "full" version can work.
Ollonk said:
Will it be dependent on the broken/outdated Motorola packages?
By this I mean, will we be able to make full use of the repos to install newer versions of software that are dependent on newer versions these packages. (E.g. the latest verision of Chromium that I can get working now is version 4 due to its dependencies breaking webtop, even when apt-get has been fixed.)
Click to expand...
Click to collapse
In some parts, yes, it will be dependant.
My intention is to hold the core packages and add the lastest (and functional) repository with Arm support, 10.10 I guess.
The other alternative is get the source code and rebuild them in Arm architeture. This demmands a lot of work and I can't do it all by myself. But with more time and people, it can be done.
If it will run the latest available version of Chromium from the repositories (It was version 14 last time I checked) that's all I'm really concerned about. Good luck!
I guess it's impossible to squeeze a light version to fit inside the 0.8gb osh reserved space. Crap!
By the way, the system is more fluid than before. I'm trying to remove all non-essential packages right now.
With AT&T stock kernel (1Ghz) GtkPerf test run now in 13s. A huge difference.
Please give WebTop2SD a try to have a much bigger osh partition .
qaplus said:
Please give WebTop2SD a try to have a much bigger osh partition .
Click to expand...
Click to collapse
I'm using it since yesterday, only OSH it's impossible =(
The system have ~1gb right now
Edit:
I'm having a hard time trying to port the lastest Chromium-browser. I need to re-install ArchLinux in my desktop first and see if I can make it work there. I'll delay Xubuntop a bit trying to port it.
I did installed xfce4 after using webtop2sd. But i ended up with a lot of stuff laying around not used, i'd like some more integrated!
Night Walker! said:
I did installed xfce4 after using webtop2sd. But i ended up with a lot of stuff laying around not used, i'd like some more integrated!
Click to expand...
Click to collapse
Like what? aumix? Did you installed xfce4 or xfce4-desktop or even xubuntu-desktop?
I'm manually installing each software from the 'original' xubuntu distro to make sure we don't end with useless software. Is that what you want?
I'm a experienced C++ developer and I have some experience with Linux. Please let me know if you want some help.
Sent from my MB860 using XDA
mfragoso said:
I'm a experienced C++ developer and I have some experience with Linux. Please let me know if you want some help.
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Oh, that would be great! I'm trying to port the latest Chromium to ARM.
Do you have experience in cross compiling? I'm stucked on this...
Would this run any faster than the current webtop with xfce4 interface? My webtop functions, buts slow as hell off my sd card sometimes. Its a class 10 pny card.
Only on windows (we use windows CE and its variants at work) but let me know how we can work.
Sent from my MB860 using XDA
teeth_03 said:
Would this run any faster than the current webtop with xfce4 interface? My webtop functions, buts slow as hell off my sd card sometimes. Its a class 10 pny card.
Click to expand...
Click to collapse
Hmm, it should run a little bit faster, but not too much. I'm trying to implement swap.
mfragoso said:
Only on windows (we use windows CE and its variants at work) but let me know how we can work.
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Ok, I will =)
---
I'm working very hard to port the Chromium-browser 18.0.1025 (latest official), I've just bricked the webtop attempting to upgrade some core files... Not a problem... I was expecting this.
I'll not give up.
I broke my webtop so many times trying to get newer software to work that I just made a disk dump of a working partition that was configured how I want it. If I ever have problems, I just restore the disk dump, and within a few minutes I have everything working again.
this has me VERY excited, but XFCE still isn't lightweight enough IMHO.
What are your thoughts about Fluxbox? I remember having DamnSmallLinux on a 200mhz machine with 128MB of RAM, that was very responsive...
That said, we don't have a webtop subforum.
Which we really need, to collaborate efficiently.
Any ideas? This forum is way to frickin busy.
this is not to rush the devs, just asking, are they gonna wait till ( i really hope it actually hapens) jb update comes to us to start developing? couse i think our phone haves a lot more to give to us than the stock rom can, again i am not rushing the devs, just asking your oppinion, and since im kinda new to theese forums hardly think any dev is going to bother to even answer this thread
so im pretty much.asking your oppinion
this is just a question , please dont kill me
sent from the gray stuff inside my skull
demonoid phenomenom said:
this is not to rush the devs, just asking, are they gonna wait till ( i really hope it actually hapens) jb update comes to us to start developing? couse i think our phone haves a lot more to give to us than the stock rom can, again i am not rushing the devs, just asking your oppinion, and since im kinda new to theese forums hardly think any dev is going to bother to even answer this thread
so im pretty much.asking your oppinion
this is just a question , please dont kill me
sent from the gray stuff inside my skull
Click to expand...
Click to collapse
If you mean Custom Roms... we can't do anything until we can pack / unpack the boot.img/or recovery.img to make a custom recovery.
jeah thats right, i was wondering because my expirience with atrix 2 , previous to the ics update, i was using supercharger rom series, but again i understand that they got a leak to work on, and a bootstrap to flash the restores they where creating, and that stock leaked rom was awesome
sent from the gray stuff inside my skull
mattlgroff said:
If you mean Custom Roms... we can't do anything until we can pack / unpack the boot.img/or recovery.img to make a custom recovery.
Click to expand...
Click to collapse
Only for my own curiosity: what's prevents that ? The x86 arch ? or something else ?
Le_Poilu said:
Only for my own curiosity: what's prevents that ? The x86 arch ? or something else ?
Click to expand...
Click to collapse
Would be nice to know for sure. The current methods cannot find 'Android Magic'.
I'm looking forward to seeing this forum get some custom ROMs too...
Looks like progress is getting on with it now
Any updates on custom ROM making for this device?
I've followed the README from <link to Motorola's sourceforge for razr i, deleted because I'm a new user> , got to the final step, but now I'm stumped. What make target should I choose? 'make full_x86-eng' and 'make generic_x86' have no make rules. A simple 'make' generates a framework build error.
What do I have to do in order to get a bootable image (built from source) for the Razr i?
I'd appreciate any kind of advice. Thanks in advance.
PS: Many thanks Matt, turl1 and the other developers that worked on this device.
tiberiu24 said:
Any updates on custom ROM making for this device?
I've followed the README from <link to Motorola's sourceforge for razr i, deleted because I'm a new user> , got to the final step, but now I'm stumped. What make target should I choose? 'make full_x86-eng' and 'make generic_x86' have no make rules. A simple 'make' generates a framework build error.
What do I have to do in order to get a bootable image (built from source) for the Razr i?
I'd appreciate any kind of advice. Thanks in advance.
PS: Many thanks Matt, turl1 and the other developers that worked on this device.
Click to expand...
Click to collapse
You won't be able to build a full android system from that source. The most you can do is
Code:
$ . build/envsetup.sh
$ lunch generic_x86-eng
$ make [I]target[/I]
Where target is something like out/target/product/generic/system/bin/bluetoothd or bluetoothd
I am working on a device tree. Writing it from scratch isn't easy because there is no device I can base this on. No other x86 tree out there. And I still dont have a device. I did make threads requesting for a device but they got closed down. So once I have something built I'll make a new thread.
Sent from my GT-I9300 using xda app-developers app
hiemanshu said:
I am working on a device tree. Writing it from scratch isn't easy because there is no device I can base this on. No other x86 tree out there. And I still dont have a device. I did make threads requesting for a device but they got closed down. So once I have something built I'll make a new thread.
Click to expand...
Click to collapse
There's at least 10 device trees on the android-x86 project. And AOSP itself has a generic one, to build the x86 emulator platform. And I made a basic one to build recovery already, with support to generate the newer x86 boot image format.
Just saying
PS: I don't own the phone either
turl1 said:
There's at least 10 device trees on the android-x86 project. And AOSP itself has a generic one, to build the x86 emulator platform. And I made a basic one to build recovery already, with support to generate the newer x86 boot image format.
Just saying
PS: I don't own the phone either
Click to expand...
Click to collapse
Generic x86 and the razr I are too far apart. Also the android x86 ones are too far apart too (I am working on a android x86 tablet). I have already written more than 450 lines of the device tree by hand, and there is a lot more to go right now. I have patched bionic for x86 builds, I need to patch the build folder next, and even busybox needs patching, etc. I am now working on making a perfect set of the 3 important files, BoardConfing.mk, device.mk and proprietary-files.txt. My android x86 tree is a total of 181 lines (which in itself is twice the size of the trees on android-x86). Its fun, but really time consuming. Also the AOSP ones are generic ones, they will work on any system if you have all the correct drivers installed or compiled via the kernel, but Razr I needs the files to be pulled from the stock build, and it needs a lot of them, including kernel drivers.
-H
hiemanshu said:
Generic x86 and the razr I are too far apart. Also the android x86 ones are too far apart too (I am working on a android x86 tablet). I have already written more than 450 lines of the device tree by hand, and there is a lot more to go right now. I have patched bionic for x86 builds, I need to patch the build folder next, and even busybox needs patching, etc. I am now working on making a perfect set of the 3 important files, BoardConfing.mk, device.mk and proprietary-files.txt. My android x86 tree is a total of 181 lines (which in itself is twice the size of the trees on android-x86). Its fun, but really time consuming. Also the AOSP ones are generic ones, they will work on any system if you have all the correct drivers installed or compiled via the kernel, but Razr I needs the files to be pulled from the stock build, and it needs a lot of them, including kernel drivers.
-H
Click to expand...
Click to collapse
I'm playing a bit with AOSP 4.2 as I got some free time. This is what I found out so far:
bionic needed no patches. I seriously doubt it needs any on 4.1 (CM) either as recovery built fine.
build needed no patches either on both cases.
dalvik needed a 4-liner to build on AOSP (makefile fixes), I haven't tried to build it on CM
there's no busybox on AOSP, I patched the one on 4.1 already to be able to build recovery, it's all on CM Gerrit as you'd expect from a CM developer like myself
my tree is already 120 lines, as soon as you add the media decoder config and audio routing config you'll go over 180 lines
having proper drivers isn't enough, you need proper HALs too. And I haven't really looked, but I'd be surprised if you had to pull kernel drivers from the stock rom
turl1 said:
I'm playing a bit with AOSP 4.2 as I got some free time. This is what I found out so far:
bionic needed no patches. I seriously doubt it needs any on 4.1 (CM) either as recovery built fine.
build needed no patches either on both cases.
dalvik needed a 4-liner to build on AOSP (makefile fixes), I haven't tried to build it on CM
there's no busybox on AOSP, I patched the one on 4.1 already to be able to build recovery, it's all on CM Gerrit as you'd expect from a CM developer like myself
my tree is already 120 lines, as soon as you add the media decoder config and audio routing config you'll go over 180 lines
having proper drivers isn't enough, you need proper HALs too. And I haven't really looked, but I'd be surprised if you had to pull kernel drivers from the stock rom
Click to expand...
Click to collapse
1) bionic needs patching, patch already submitted to CM gerrit libdvm basically
2) build needs patching for the boot.img
3) dalvik has been patched
4) Odd, didn't notice that
5) Probably wont required pulling in kernel drivers, but would required pulling in the correct drivers for the defconfig
I'd be happy if you wanted to work together to get this working. PM me
hiemanshu said:
1) bionic needs patching, patch already submitted to CM gerrit libdvm basically
2) build needs patching for the boot.img
3) dalvik has been patched
4) Odd, didn't notice that
5) Probably wont required pulling in kernel drivers, but would required pulling in the correct drivers for the defconfig
I'd be happy if you wanted to work together to get this working. PM me
Click to expand...
Click to collapse
Let's continue talking on PM then
re. 2, I actually did need to patch build on AOSP after all . CM on the other hand, has BOARD_CUSTOM_BOOTIMG_MK from the tf tablets.
Hey I posted a rom over at droidrzr.com for use till aosp is ready. This should be enough till we get a jb leak
Sent from my XT890 using Tapatalk 2
Hi Folks
While I don't own a RAZR I , I have been Jaffing around with building CM10.1 and AOSP for x86, I've been getting in going on my FX8120, just need to sort the OpenGLES MESA drivers out.
Anyways I've got CM10.1 built for x86 using the mr1-staging branch ( I think it's been merged to cm10.1 ) and an edited mini-x86 device tree .
Busybox was a B**stard to build though, although on one of the branches there is an .config-minimal-x86 .config-full-x86, still needed tweaking tho.
I submitted my patches http://review.cyanogenmod.org/#/c/27377/ and http://review.cyanogenmod.org/#/c/27373/, however It seems x86 isn't top of cm's agenda.... or I'm missing something about assigning reviewers.
Obviously a base x86 build is only part of the story for you guys as you'll face all the regular problems that emedded devices have, not checked the specs for the RazR but I'm sure there's some binary blobs in your future,
Hack On Folks! :good:
Hi,
I've got Ubuntu Touch running on my Xoom, not perfectly. I have an LTE Xoom, but I'm building as if it is Wifi Only (I no longer have service on LTE).
Issues:
Font rendering in some places is unreadable.
Display settings have to be manually tweaked in /usr/bin/ubuntu-session to set GRID_UNIT_PX=10
Have not tested sound at all
Camera doesn't seem to work
Haven't tested GPS
Installation instructions:
reboot in recovery
wipe
install base Xoom (Wingray) Image: cm-10.1-20130228-UNOFFICIAL-wingray.zip md5: b1391ff076e67f68f89606c2ae349986
install the Ubuntu 12.10 Touch Preview, daily build quantal-preinstalled-phablet-armhf.zip*
reboot
use ubuntu_chroot to edit /usr/bin/ubuntu-session and set GRID_UNIT_PX=10
reboot
Fixed:
I'm able to connect to my wifi and use the internet via an adb (ubuntu_chroot shell), but apps including the browser used from the device don't seem to have connectivity.
*This download is a daily snapshot, the latest version may or may not work, I've only tested using the version from 20130228.
Reserve a spot for some more technical details.
Could i get a link? I would love to give this a try! :good:
mikedmor said:
Could i get a link? I would love to give this a try! :good:
Click to expand...
Click to collapse
PM with the link sent, when I get to 10 posts or get moderator approval, I'll edit the original post to include the download link.
Please keep me posted on how it goes. I'll try to document the steps I took to get it running soon (very minimal, just followed the official porting guide)
Just finished building it as I have seen Xoom support removed from the wiki yesterday. Did you unset CONFIG_ANDROID_PARANOID_NETWORKS to make apps work?
dreamcwli said:
Just finished building it as I have seen Xoom support removed from the wiki yesterday. Did you unset CONFIG_ANDROID_PARANOID_NETWORKS to make apps work?
Click to expand...
Click to collapse
I did not unset CONFIG_ANDROID_PARANOID_NETWORKS as it broke the build and I have not had time to investigate it further. Were you able to build with it unset? Is the networking in the apps working for you?
skippyishappy said:
I did not unset CONFIG_ANDROID_PARANOID_NETWORKS as it broke the build and I have not had time to investigate it further. Were you able to build with it unset? Is the networking in the apps working for you?
Click to expand...
Click to collapse
I comment several lines in the kernel source code so I can build it with the flag unset. I still can't fully boot Ubuntu Touch as the libraries used are not in the runtime path so I need to fix it. Will report here when I have time to work on it.
Good luck on the development
Sent from my GT-N7000 using Tapatalk 2
Thx dreamcwli and OP
This project sounds like it will be good for devs and enhanced users and it keeps the hopes of the xoom staying around for a few more years.
Keep up the work and give us hope.
Did you symlink libraries under /data/ubuntu/usr/lib/armeabihf to /system/lib to boot the system?
...
CBDSonline said:
Thx dreamcwli and OP
This project sounds like it will be good for devs and enhanced users and it keeps the hopes of the xoom staying around for a few more years.
Keep up the work and give us hope.
Click to expand...
Click to collapse
+1
dreamcwli said:
Did you symlink libraries under /data/ubuntu/usr/lib/armeabihf to /system/lib to boot the system?
Click to expand...
Click to collapse
I did no modifications to the ubuntu partition other than changing the GRID_UNIT_PX to make the layout fit the screen better. On my first attempt the screen was black, so I took a look using adb logcat and saw:
I/SurfaceFlinger( 1064): SurfaceFlinger is starting
I/SurfaceFlinger( 1064): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
E/libEGL ( 1064): eglGetDisplay:121 error 300c (EGL_BAD_PARAMETER)
E/libEGL ( 1064): eglInitialize:137 error 3008 (EGL_BAD_DISPLAY)
Click to expand...
Click to collapse
This made me suspect it was missing some binaries (the only ones I'm using are from the Google binaries page for the Wifi Xoom).
device/moto/wingray/device_base.mk is looking for the vendor directories which do not match the directories I had after extracting them.
mv vendor/moto/ vendor/motorola
mv vendor/motorola/stingray/ vendor/motorola/wingray
Click to expand...
Click to collapse
Then rebuild with brunch and the error was gone and the screen lit up with Ubuntu touch.
skippyishappy said:
I did no modifications to the ubuntu partition other than changing the GRID_UNIT_PX to make the layout fit the screen better. On my first attempt the screen was black, so I took a look using adb logcat and saw:
This made me suspect it was missing some binaries (the only ones I'm using are from the Google binaries page for the Wifi Xoom).
device/moto/wingray/device_base.mk is looking for the vendor directories which do not match the directories I had after extracting them.
Then rebuild with brunch and the error was gone and the screen lit up with Ubuntu touch.
Click to expand...
Click to collapse
I have updated the location path for proprietary blobs. What I got is linker.c can't load /system/lib/libubuntu_application_api.so. Did you use Ubuntu-specific tools to build it? I am on Arch Linux so I am thinking about it those tools make different result.
dreamcwli said:
I have updated the location path for proprietary blobs. What I got is linker.c can't load /system/lib/libubuntu_application_api.so. Did you use Ubuntu-specific tools to build it? I am on Arch Linux so I am thinking about it those tools make different result.
Click to expand...
Click to collapse
To setup my environment, I created a new VM using Ubuntu 12.04 LTS and followed the steps in "Set up your development environment" in the porting guide.
skippyishappy said:
To setup my environment, I created a new VM using Ubuntu 12.04 LTS and followed the steps in "Set up your development environment" in the porting guide.
Click to expand...
Click to collapse
Now this is interesting!!!! Xoom is not officially supported by canonical, a 14year old was trying to port it. Even if the device is not listed anymore you can send an email to canonical and tell that you will be the one to port it to xoom! Keep up the good work. i am willing to test your work! I have a UMTS_Everest xoom. If you are interested please PM the links to me
Cheers!
darksnoopy said:
Now this is interesting!!!! Xoom is not officially supported by canonical, a 14year old was trying to port it. Even if the device is not listed anymore you can send an email to canonical and tell that you will be the one to port it to xoom! Keep up the good work. i am willing to test your work! I have a UMTS_Everest xoom. If you are interested please PM the links to me
Cheers!
Click to expand...
Click to collapse
PM sent. The port itself has been trivial, at least getting it to boot. Easy to see why Canonical chose this path.
Very interested in this please pm me a link, I have a little knowledge of linux so I may be able to play around a bit.
slaming said:
Very interested in this please pm me a link, I have a little knowledge of linux so I may be able to play around a bit.
Click to expand...
Click to collapse
PM'd, I should be able to edit my original post with the download links now.
I can confirm developers have to use phablet-dev-bootstrap tools to build it now. With phablet-dev-bootstrap you will get additional components that are required for Ubuntu Touch. I will test how network going with my build.
Built it and working fine now. With CONFIG_ANDROID_PARANOID_NETWORK unset I can use browser and other network apps without problem. However the usability is not good at current stage.
How does one port ROMs to another phone? I'm looking to try and port Xylon to the Find 5.
Sent from my X909 using xda app-developers app
it's really not that difficult. just have to adjust some overlays, change some stuff in vendor and maybe grab the camera from CM if the changes haven't been made to that ROM.
if you are building from source:
Find the 4.2.2 source code of the ROM you want to port
Get the manifest.
Add the CM10.1 device/kernel tree and proprietary libs in the .repo/local_manifest/roomservice.xml
sync all the repos
(do whatever the source might need you to set up: EG paranoid android, need you to setup your device properly in vendor/pa/* files)
compile. Fix any problems(maybe missing files, etc)
you could try a non-4.2.2-based ROM to port, but you'll run into more incompatibility issues to fix
mbh87 said:
it's really not that difficult. just have to adjust some overlays, change some stuff in vendor and maybe grab the camera from CM if the changes haven't been made to that ROM.
Click to expand...
Click to collapse
So would you say just use this
http://forum.xda-developers.com/showthread.php?t=2232773
And the CM10 for our Oppo?
Sent from my X909 using xda app-developers app
newbcake said:
So would you say just use this
http://forum.xda-developers.com/showthread.php?t=2232773
And the CM10 for our Oppo?
Sent from my X909 using xda app-developers app
Click to expand...
Click to collapse
No, build from source since it's available.
mbh87 said:
No, build from source since it's available.
Click to expand...
Click to collapse
You mean Oppo's source or AOSP from Google? I presume AOSP
Sent from my X909 using xda app-developers app
assuming this is the one you want to port (it is using 4.2.2, so hopefully it'll be easier)
read their README: https://github.com/XYAOSP/buildscripts
use repo and checkout this manifest
https://github.com/XYAOSP/platform_manifest/blob/jb4.2/default.xml
use repo and sync all the repos
then see how I get the device specific files here? do the same https://git.ngvincent.com/projects/oppo-x909-cm10/wiki/Build#Get-device-specific-sources-and-build
then follow whatever instructions needed to build. if it uses CM based building (which i think they do here, then do
. build/envsetup.sh && brunch
select the find5 entry (if it;s not there, then do lunch, select find5, mka)
wait for it to fail. read error message. fix error message. repeat last 3 steps .. Google is your friend... learn to love google
---------------------------------------
you should try building CM10.1 first. there will hopefully be no errors, and you learn how to use brunch/lunch/breakfast / etc
https://git.ngvincent.com/projects/oppo-x909-cm10/wiki/Build
paperWastage said:
assuming this is the one you want to port (it is using 4.2.2, so hopefully it'll be easier)
read their README: https://github.com/XYAOSP/buildscripts
use repo and checkout this manifest
https://github.com/XYAOSP/platform_manifest/blob/jb4.2/default.xml
use repo and sync all the repos
then see how I get the device specific files here? do the same https://git.ngvincent.com/projects/oppo-x909-cm10/wiki/Build#Get-device-specific-sources-and-build
then follow whatever instructions needed to build. if it uses CM based building (which i think they do here, then do
. build/envsetup.sh && brunch
select the find5 entry (if it;s not there, then do lunch, select find5, mka)
wait for it to fail. read error message. fix error message. repeat last 3 steps .. Google is your friend... learn to love google
---------------------------------------
you should try building CM10.1 first. there will hopefully be no errors, and you learn how to use brunch/lunch/breakfast / etc
https://git.ngvincent.com/projects/oppo-x909-cm10/wiki/Build
Click to expand...
Click to collapse
Is there something wrong with the Xylon repo? I keep getting this:
Code:
Cannot fetch htc-msm8960/[some path here]
newbcake said:
Is there something wrong with the Xylon repo? I keep getting this:
Code:
Cannot fetch htc-msm8960/[some path here]
Click to expand...
Click to collapse
use google and your own intuition to help you (this is why you should build the Cm10.1 ROM first.... the knowledge you gain will help you)
most likely either github is down, or the path referencing it is invalid, or something......
but the question is, do we need htc-msm8960? most likely no, since the oppo kernel is self contained
^^^ all this comes from experience.... seriously, go build cm10.1 for the find 5 first
paperWastage said:
use google and your own intuition to help you (this is why you should build the Cm10.1 ROM first.... the knowledge you gain will help you)
most likely either github is down, or the path referencing it is invalid, or something......
but the question is, do we need htc-msm8960? most likely no, since the oppo kernel is self contained
^^^ all this comes from experience.... seriously, go build cm10.1 for the find 5 first
Click to expand...
Click to collapse
we probably dont need it, but a lot of ROMs make you download ALL their devices and corresponding files.
Well, I removed the HTC lines from manifest.xml (maybe not a good idea?) but anyway, it finished syncing after.
mbh87 said:
we probably dont need it, but a lot of ROMs make you download ALL their devices and corresponding files.
Click to expand...
Click to collapse
yeah... it's a problem with a simple fix.... if the error was something like "packages_mms_app", then it's a more serious problem.....
does removing that repo mask a larger problem? that's why I'm pushing for OP to start small first by building CM10.1, and learn the environment (instead of posting every single problem he encounters here, and asks for help)
I've only started playing with android source code in March/early april... and these are things that I've learned/picked up since then.
paperWastage said:
yeah... it's a problem with a simple fix.... if the error was something like "packages_mms_app", then it's a more serious problem.....
does removing that repo mask a larger problem? that's why I'm pushing for OP to start small first by building CM10.1, and learn the environment (instead of posting every single problem he encounters here, and asks for help)
I've only started playing with android source code in March/early april... and these are things that I've learned/picked up since then.
Click to expand...
Click to collapse
Understood. I'm syncing up the Cm10 now. Thanks!
Is is best to do this all on Linux, Mac, or Windows?
It isn't possible to do it on windows so one of the other two.
mbh87 said:
It isn't possible to do it on windows so one of the other two.
Click to expand...
Click to collapse
Cool thanks. I just "finished" my compile on my Mac 10.7.8 but there was something about gcc422 not found. I have the latest XCode installed along with Dev tools. So can anyone help cause I didn't see anything with a Google.
I presume a clean Ubuntu is preferred
Sent from my X909 using xda app-developers app
newbcake said:
Cool thanks. I just "finished" my compile on my Mac 10.7.8 but there was something about gcc422 not found. I have the latest XCode installed along with Dev tools. So can anyone help cause I didn't see anything with a Google.
I presume a clean Ubuntu is preferred
Sent from my X909 using xda app-developers app
Click to expand...
Click to collapse
it's preferable
even on ubuntu, you still have to get specific packages: need oracle version of jdk, not openjdk, need to remove some incompatible stuff
heres a guide for ubuntu 12.10
https://git.ngvincent.com/projects/oppo-x909-cm10/wiki/Android-setup
paperWastage said:
it's preferable
even on ubuntu, you still have to get specific packages: need oracle version of jdk, not openjdk, need to remove some incompatible stuff
heres a guide for ubuntu 12.10
https://git.ngvincent.com/projects/oppo-x909-cm10/wiki/Android-setup
Click to expand...
Click to collapse
I tried compiling CM10, and am even having problems with that. Google did not seem to help for this. Here is what I did:
I did the mka, then mka otapackage, and NOTHING is appearing. No zips at all.
Code:
hardware/qcom/media/mm-video/vidc/vdec/src/omx_vdec.cpp:9925:138: warning: format '%d' expects argument of type 'int', but argument 5 has type 'OMX_U32 {aka long unsigned int}' [-Wformat]
make: *** wait: No child processes. Stop.
That is the last fine before it gives me control of terminal again.
newbcake said:
I tried compiling CM10, and am even having problems with that. Google did not seem to help for this. Here is what I did:
I did the mka, then mka otapackage, and NOTHING is appearing. No zips at all.
Code:
hardware/qcom/media/mm-video/vidc/vdec/src/omx_vdec.cpp:9925:138: warning: format '%d' expects argument of type 'int', but argument 5 has type 'OMX_U32 {aka long unsigned int}' [-Wformat]
make: *** wait: No child processes. Stop.
That is the last fine before it gives me control of terminal again.
Click to expand...
Click to collapse
a few tips
typically, compilers only stop when there's an error, not warnings (unless you set flags like -Werror )
compiling is parallelized.... let's say you have a quad core, you can compile 4 projects simultaneously... when you have an error on the first make file, it stops.... but the other 3 projects will continue compiling and outputting logs until they're done (then the scheduler sees the first make file has an error, doesn't execute any more make builds and halts), so the last log file/line might not be showing you the error
For CM10.1, find5 is official now... you can just use brunch instead of breakfast/lunch & mka
paperWastage said:
a few tips
typically, compilers only stop when there's an error, not warnings (unless you set flags like -Werror )
compiling is parallelized.... let's say you have a quad core, you can compile 4 projects simultaneously... when you have an error on the first make file, it stops.... but the other 3 projects will continue compiling and outputting logs until they're done (then the scheduler sees the first make file has an error, doesn't execute any more make builds and halts), so the last log file might not be showing you the error
For CM10.1, find5 is official now... you can just use brunch instead of breakfast & mka
Click to expand...
Click to collapse
In essence, I scour the log for errors?
I just presumed as CM10 already existed on the Oppo Find 5, it would be an error-free compile.
newbcake said:
In essence, I scour the log for errors?
I just presumed as CM10 already existed on the Oppo Find 5, it would be an error-free compile.
Click to expand...
Click to collapse
you could source the log for errors
or just run the compile script again and again.... the scheduler will continue building other packages, but it'll come to a point where it can't build anything else without that broken package.... and hence, the error in the log will be obvious(since everything else is already built, no logs from them)
it should be an error-free compile, but sometimes things could happen (a small tweak in package/A gives some problems when compiling with package/B)
I would say, most likely there's some build package incompatibility in your system.