So I've asked in other places but nor response. I'm trying to build lollipop dream and this is the error I get. "build/core/product_config.mk:222: *** can not locate config makefile for product " cm_bacon". Stop. Don't have product spec for cm_bacon" I tried to create a full_bacon.mk based of the one that the team provided for their github, but its as if the computer doesn't recognize it. I'm still getting the same error code even if I rename the full_bacon.mk to cm_bacon.mk. any help?
Affichage des articles dont le libellé est building. Afficher tous les articles
Affichage des articles dont le libellé est building. Afficher tous les articles
dimanche 8 février 2015
samedi 7 février 2015
Building for one topic
I'm trying to create a build of lollipop dream, and every time I try to compile I get "build/core/product_config.mk:222: *** can not locate config makefile for product " cm_bacon". Stop. Don't have product spec for cm_bacon" I tried to create a full_bacon.mk based of the one that the team provided for their github, but its as if the computer doesn't recognize it. I'm still getting the same error code even if I rename the full_bacon.mk to cm_bacon.mk. any help?
mardi 3 février 2015
[Q] Help with building a ROM from OEM source WIKO FIZZ (MT6572) topic
Beloved community. I need your help.
Scenario: The Wiko FIZZ of my GF stopped working out of the blue. Several searches online found me some threads with frustrated users.
What i think i could do: Reboot to recovery --> Wipe data --> all good. -->WASN'T!!
So i started looking for a factory image i could flash. Apparently Wiko has oneclicktools for almost all of their smartphones to get them back to factory state. Not so for the FIZZ. I came across a collection of Factory images and again, the FIZZ was missing.
So i came across this site: http://www.wikogeek.com/
They provide source code to everybody who wants to do developement with his WIKO.
My final questions to you:
1. This is only the source for the Kernel or am i wrong?
2. Can i build the kernel according to all the nice guides out here or do i have to care about something special? (recommending a specific guide?)
3. Once i got my Kernel ready. Could i take any ROM, made for MT6572-Devices and get the FIZZ running again?
4. Is there anything else i should try before messing with such stuff in order to get the FIZZ running again?
Thank you much ;)
Scenario: The Wiko FIZZ of my GF stopped working out of the blue. Several searches online found me some threads with frustrated users.
What i think i could do: Reboot to recovery --> Wipe data --> all good. -->WASN'T!!
So i started looking for a factory image i could flash. Apparently Wiko has oneclicktools for almost all of their smartphones to get them back to factory state. Not so for the FIZZ. I came across a collection of Factory images and again, the FIZZ was missing.
So i came across this site: http://www.wikogeek.com/
They provide source code to everybody who wants to do developement with his WIKO.
My final questions to you:
1. This is only the source for the Kernel or am i wrong?
2. Can i build the kernel according to all the nice guides out here or do i have to care about something special? (recommending a specific guide?)
3. Once i got my Kernel ready. Could i take any ROM, made for MT6572-Devices and get the FIZZ running again?
4. Is there anything else i should try before messing with such stuff in order to get the FIZZ running again?
Thank you much ;)
lundi 2 février 2015
Distributed rom building and/or distribution system topic
Hi guys!
I had this thought recently when using my mediafire account- it sucks... probably it doesn't suck more than average filehosting account, but still...
The idea (in fact two of them) I came up is the following:
Distribute evrything via bittorrent :)
For now I can't see any major downsides of the concept - but I think it'll be most useful for bigger distributions that build daily builds and/or support many phones. It could considerably ease the load on their uplinks thanks to the way bt works.
How I imagine it to work:
The person who would like to contribute would downoad the client, install it on his server/pc, register to the central repository, and in the end set a few config options (bandwidth he wants to contribute, how much disk space, and to what projects/phones/developers) and that's it. The client would then ask the central repo for some torrents to mirror and it'll run by itself (periodically asking the repo for new downloads or removals) - hopefully without any maintanance ever needed.
I imagine "the client" to be as simple as possible - maybe even a one shell script using curl to communicate with the repo. And of course some torrent client - if the project develops, support for many clients (and windows) can be added.
The server would do all the thinking as it'd have the most complete information about the entire "pool" - how much space is available to which projects, how many dowloads of each torrent there are etc. so it'd be easier for it to decide who should mirror what (of course within their defined filters). But in the beginning I don't think it would have to be very complicated either - if more clients connect, the algorithm can be made smarter.
The thing is - many of your users would be happy to contribute in some way to rom development, but usually they lack the skill necessary. But they could contribute hardware/bandwidth, especially that it doesn't require any effort from them and gives them the satisfaction of contributing.
The other thing is distributed build system based on similar principles: provide people with a configured VM image of a building system for various virtualization technologies and operating systems and that's it. The initial setup would be made as simple as possible for the end user. Having one vmimage would guarantee that everybody has consistent build environments.
This would of course be useful only to large android rom distributions that support multiple devices - building 20+ nightlies/a day (and distributing them) can be quite a challenge and requires considerable processing power and bandwidth, but if they had a farm of build servers (even small), this wouldn't be a problem and they could commit their hardware for pure development/debuging efforts.
Of course the system would inform the developer if his build failed somewhere and provided a log, so that he (or a person responsible) can investigate. The system could also do some automated recovery, i.e.: build fails -> clean ccache and rebuild, if fails, restart on another machine and if this fails, inform the developer. The system could also detect a faulty build machine (that fails some builds that run successfuly elsewhere) and exclude it from the pool (and of course send an email to machine owner). And of course ready builds would be reported to the repo server and distributed via torrent.
The whole trick is that for both distribution and compilation none individual contribution has to be large - users can dedicate 1GB of mirror space and it'll allow to host 4-5 rom builds. For build machines, they don't need to have a 6-core monster because it doesn't matter if it builds 1,2 or 3 hours as long as it builds (my 4x3.2GHz machine builds a rom in <90mins). What's more, they don't have to run those severs 24/7 - the system will know which machines are always on and which are not and distribute the load taking this information into account.
When the community grows beyond some critical mass, the system will work despite people droping in and out of the "grid"...
Just a loose idea... :) Tell me what you think.
I had this thought recently when using my mediafire account- it sucks... probably it doesn't suck more than average filehosting account, but still...
The idea (in fact two of them) I came up is the following:
Distribute evrything via bittorrent :)
For now I can't see any major downsides of the concept - but I think it'll be most useful for bigger distributions that build daily builds and/or support many phones. It could considerably ease the load on their uplinks thanks to the way bt works.
How I imagine it to work:
The person who would like to contribute would downoad the client, install it on his server/pc, register to the central repository, and in the end set a few config options (bandwidth he wants to contribute, how much disk space, and to what projects/phones/developers) and that's it. The client would then ask the central repo for some torrents to mirror and it'll run by itself (periodically asking the repo for new downloads or removals) - hopefully without any maintanance ever needed.
I imagine "the client" to be as simple as possible - maybe even a one shell script using curl to communicate with the repo. And of course some torrent client - if the project develops, support for many clients (and windows) can be added.
The server would do all the thinking as it'd have the most complete information about the entire "pool" - how much space is available to which projects, how many dowloads of each torrent there are etc. so it'd be easier for it to decide who should mirror what (of course within their defined filters). But in the beginning I don't think it would have to be very complicated either - if more clients connect, the algorithm can be made smarter.
The thing is - many of your users would be happy to contribute in some way to rom development, but usually they lack the skill necessary. But they could contribute hardware/bandwidth, especially that it doesn't require any effort from them and gives them the satisfaction of contributing.
The other thing is distributed build system based on similar principles: provide people with a configured VM image of a building system for various virtualization technologies and operating systems and that's it. The initial setup would be made as simple as possible for the end user. Having one vmimage would guarantee that everybody has consistent build environments.
This would of course be useful only to large android rom distributions that support multiple devices - building 20+ nightlies/a day (and distributing them) can be quite a challenge and requires considerable processing power and bandwidth, but if they had a farm of build servers (even small), this wouldn't be a problem and they could commit their hardware for pure development/debuging efforts.
Of course the system would inform the developer if his build failed somewhere and provided a log, so that he (or a person responsible) can investigate. The system could also do some automated recovery, i.e.: build fails -> clean ccache and rebuild, if fails, restart on another machine and if this fails, inform the developer. The system could also detect a faulty build machine (that fails some builds that run successfuly elsewhere) and exclude it from the pool (and of course send an email to machine owner). And of course ready builds would be reported to the repo server and distributed via torrent.
The whole trick is that for both distribution and compilation none individual contribution has to be large - users can dedicate 1GB of mirror space and it'll allow to host 4-5 rom builds. For build machines, they don't need to have a 6-core monster because it doesn't matter if it builds 1,2 or 3 hours as long as it builds (my 4x3.2GHz machine builds a rom in <90mins). What's more, they don't have to run those severs 24/7 - the system will know which machines are always on and which are not and distribute the load taking this information into account.
When the community grows beyond some critical mass, the system will work despite people droping in and out of the "grid"...
Just a loose idea... :) Tell me what you think.
vendredi 30 janvier 2015
(Q) Building automated script for Android game topic
Hello there,
First I will apologize if I'm in the wrong thread, but from what I read that's the place to ask the question I have :)
To get to the pint:
I would like to write a script for an android game, which will execute certain actions in the game. I'm talking about a strategy game so the script will make attacks in a loot, thus saving enormous amounts of time if I do it by hand.
I've seen a script like that but I can't get my hands on it, so I've decided to look into writing my own.
Here comes the fun part: I'm a total noob in writing any codes :(, but I'm a fast learner.
So far I've realized that because the game runs on servers, I'll need to open the source code of the game to extract the commands that the game is using for each action. Than compile a script that will execute that same action (sending it to the server) from my behalf (using my account information) and than put this action into a loop for as many times I would like to (think that would be the easiest part compared to everything else)
I would really appreciate it if someone can point me in the right direction as far as what to read and what to use to do all of that.
Thank you Much in advance!
Shlevy
Sent from my SM-N900R4 using XDA Free mobile app
First I will apologize if I'm in the wrong thread, but from what I read that's the place to ask the question I have :)
To get to the pint:
I would like to write a script for an android game, which will execute certain actions in the game. I'm talking about a strategy game so the script will make attacks in a loot, thus saving enormous amounts of time if I do it by hand.
I've seen a script like that but I can't get my hands on it, so I've decided to look into writing my own.
Here comes the fun part: I'm a total noob in writing any codes :(, but I'm a fast learner.
So far I've realized that because the game runs on servers, I'll need to open the source code of the game to extract the commands that the game is using for each action. Than compile a script that will execute that same action (sending it to the server) from my behalf (using my account information) and than put this action into a loop for as many times I would like to (think that would be the easiest part compared to everything else)
I would really appreciate it if someone can point me in the right direction as far as what to read and what to use to do all of that.
Thank you Much in advance!
Shlevy
Sent from my SM-N900R4 using XDA Free mobile app
dimanche 25 janvier 2015
[HELP] Building CM12 'No ~/android/system/vendor/cm' topic
Hi there, I'm extremely new to building a ROM or even to git and other stuff and am now trying to learn to build ROM. I have downloaded the cm12 sources for now, and trying to learn how it works, but seems to have stuck at a location.
I have been following the cm build page instructions for now from this page, and have done following stuff until now:
Now when I get to the get prebuilt apps, and I run cd ~/android/system/vendor/cm, I get the
I tried opening the location manually, but I find no "vendor" folder under the "android/system" folder. However, there is a "vendor" folder under "android" and that "vendor" consists of folders like "cm", "cyngn" and "sony", where "sony" is related to My phone.
Under system I have folders like "core", "extras", "keymaster", "media", "netd", "qcom", "security" and "vold".
Before You say that I might have not done repo sync properly, it did complete properly. I have attached the image of completion of first time the repo sync was complete. Then a log of second time when the repo sync was done to get the device specific related stuff. I used the -f since the download of source had been interrupted due to the error "error: Exited sync due to fetch errors".
Also, don't know if it matters, but I have built a ROM before on the same system, but it was by following the instructions as posted to do. The sources were all coded to suit My phone, and all I was doing was "repo sync" and building the ROM via source with commands build/envsetup.sh
and breakfast nozomi and used to get a working build.
So please help Me out where I went wrong as I do want to learn to how to build a ROM.
I have been following the cm build page instructions for now from this page, and have done following stuff until now:
- Make folders:
Code:
mkdir -p ~/bin
$ mkdir -p ~/android/system - Installed the repo command and entered the following to download the "repo" binary and make it executable (runnable):
Code:
$ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo - Put the ~/bin directory in your path of execution
- Initialize the CyanogenMod source repository and initialized the repository:
Code:
$ cd ~/android/system/
$ repo init -u https://github.com/CyanogenMod/android.git -b ics - Downloaded the source code
Code:
$ repo sync -j4 -f -c - Get prebuilt apps
Code:
$ cd ~/android/system/vendor/cm
Now when I get to the get prebuilt apps, and I run cd ~/android/system/vendor/cm, I get the
Code:
cd ~/android/system/vendor/cm bash: No such file or directoryUnder system I have folders like "core", "extras", "keymaster", "media", "netd", "qcom", "security" and "vold".
Before You say that I might have not done repo sync properly, it did complete properly. I have attached the image of completion of first time the repo sync was complete. Then a log of second time when the repo sync was done to get the device specific related stuff. I used the -f since the download of source had been interrupted due to the error "error: Exited sync due to fetch errors".
Also, don't know if it matters, but I have built a ROM before on the same system, but it was by following the instructions as posted to do. The sources were all coded to suit My phone, and all I was doing was "repo sync" and building the ROM via source with commands build/envsetup.sh
and breakfast nozomi and used to get a working build.
So please help Me out where I went wrong as I do want to learn to how to build a ROM.
samedi 24 janvier 2015
[GUIDE] Building independent system apps from Lollipop source for OnePlusOne topic
#This is a simple guide to download, modify and build system apps on CM12.0 based Blisspop fork for bacon device (OnePlusOne)
#Last edited: 2015-01-23
Was trying to modify some system app functionalities and it turns out the methods of decompiling - modify smali - recompiling did not work well. So had to try building from source. After three days of trials and errors, I succeeded in building the desired system apps without having to compile the entire rom. There is a similar guide on XDA-University, and also the same guide I went to for answers first. But that is largely out-dated, so I'm not going to cover it here. Most of the readings I did was on XDA and CM Wiki, so I thought I'd post my findings here as a way of appreciation, and hopefully will reduce the amount of research for folks with similar needs.
For people who want to build entire Lollipop rom from source, GRMrGecko wrote an excellent guide here:
http://forum.xda-developers.com/onep...s-one-t2947949
And to make things easier, I'm going to use bits from GRMrGeCko's guide so readers of this thread won't need to jump to other links to figure out exactly how.
So, how do you build system apps without having to build the entire rom?
1. Establishing android develop environment. Install 64bit version of Unbutu, I used the iso with 'AMD64" in it, and the version is 14.04. Make sure you allocate more than 60G for source code and building - those tend to take significant storage. In my case, I was using an Asus 1215T laptop, with an ancient single core AMD CPU, and 2G memory, plus 500G hard disk.
Once installed, ctrl+alt+T to open the terminal and Install the following items via apt-get:
sudo apt-get install bison build-essential curl flex git gnupg gperf libesd0-dev libncurses5-dev libsdl1.2-dev libwxgtk2.8-dev libxml2 libxml2-utils lzop openjdk-6-jdk openjdk-6-jre pngcrush schedtool squashfs-tools xsltproc zip zlib1g-dev g++-multilib gcc-multilib lib32ncurses5-dev lib32readline-gplv2-dev lib32z1-dev
As per the instructions on the wiki for building CM, if you use a 32bit system, do not install g++-multilib gcc-multilib lib32ncurses5-dev lib32readline-gplv2-dev lib32z1-dev.
#Install the latest version of Java's development kit using the following:
sudo apt-get install openjdk-7-jdk
#Install the Android Development Kit using the following.
sudo apt-get install android androidsdk-uiautomatorviewer android-copyright android-src-vendor android-emulator android-tools-adb android-headers android-tools-adbd androidsdk-ddms android-tools-fastboot androidsdk-hierarchyviewer android-tools-fsutils androidsdk-traceview
#Then, install repo:
mkdir -p ~/bin
curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
reboot your system or use the following in terminal to load the .profile file again:
. ~/.profile
2. make a folder (any name would do) to store the code. Go into the folder (i.e. cd /home/uersername/BlissPop) and get the source code:(you'll only get the latest main branch this way - I suppose. All commands in terminal console have assumed that the source code root folder is current folder)
repo init -u https://github.com/TeamBliss-LP/android.git -b lp5.0
repo sync
#Note: this will download the specified branch lp5.0 (lollipop 5.0 of Blisspop) onto your local drive. The source as of Jan. 23, 2015 is 10+GB, so be patient and try different vpn connections to get the most desirable speed. It took me overnight to download the source code.
3. Build
#Note: This is the tricky part. The existing documentation of Blisspop or other similar open source project does not explicitly explain whether you need to sync full project tree to be able to just compile specific modules (i.e. Source Folder/packages/apps/Email). After experimentation, the answer is a most definite yes. The reason is that system apps usually have many framework-level dependencies, which means downloading the entire source code is the safest way to ensure a successful build. However, you don't need to build the entire rom, or firmware, which takes hours on a single core Asus 1215T.
#To compile specific system apps. After repo sync
a) initiate build environment
. build/envsetup.sh
breakfast bacon
#Note, if you encounter device tree related errors in build steps below, try repeating the above two steps, and run repo sync after breakfast bacon. This, according to CM documentation, will download the specific device tree into the local repository.
b) build the specific app and all its dependencies
#go into the app folder (i.e. cd /home/username/Blisspop/packages/apps/Email)
mma
# Wait until the compilation is over, this on a single core AMD Asus 1215T takes about 2-3 minutes.
#The compiled and signed app should be in out/product/bacon/Email folder. Ready to be copied and flashed using root explorer in your OnePlus's system/app folder.
#When rebuild an app after mma has been executed at least once, no need to build all dependencies, hence:
#go into the app folder (i.e. cd /home/username/Blisspop/packages/apps/Email)
mm
#Last edited: 2015-01-23
Was trying to modify some system app functionalities and it turns out the methods of decompiling - modify smali - recompiling did not work well. So had to try building from source. After three days of trials and errors, I succeeded in building the desired system apps without having to compile the entire rom. There is a similar guide on XDA-University, and also the same guide I went to for answers first. But that is largely out-dated, so I'm not going to cover it here. Most of the readings I did was on XDA and CM Wiki, so I thought I'd post my findings here as a way of appreciation, and hopefully will reduce the amount of research for folks with similar needs.
For people who want to build entire Lollipop rom from source, GRMrGecko wrote an excellent guide here:
http://forum.xda-developers.com/onep...s-one-t2947949
And to make things easier, I'm going to use bits from GRMrGeCko's guide so readers of this thread won't need to jump to other links to figure out exactly how.
So, how do you build system apps without having to build the entire rom?
1. Establishing android develop environment. Install 64bit version of Unbutu, I used the iso with 'AMD64" in it, and the version is 14.04. Make sure you allocate more than 60G for source code and building - those tend to take significant storage. In my case, I was using an Asus 1215T laptop, with an ancient single core AMD CPU, and 2G memory, plus 500G hard disk.
Once installed, ctrl+alt+T to open the terminal and Install the following items via apt-get:
sudo apt-get install bison build-essential curl flex git gnupg gperf libesd0-dev libncurses5-dev libsdl1.2-dev libwxgtk2.8-dev libxml2 libxml2-utils lzop openjdk-6-jdk openjdk-6-jre pngcrush schedtool squashfs-tools xsltproc zip zlib1g-dev g++-multilib gcc-multilib lib32ncurses5-dev lib32readline-gplv2-dev lib32z1-dev
As per the instructions on the wiki for building CM, if you use a 32bit system, do not install g++-multilib gcc-multilib lib32ncurses5-dev lib32readline-gplv2-dev lib32z1-dev.
#Install the latest version of Java's development kit using the following:
sudo apt-get install openjdk-7-jdk
#Install the Android Development Kit using the following.
sudo apt-get install android androidsdk-uiautomatorviewer android-copyright android-src-vendor android-emulator android-tools-adb android-headers android-tools-adbd androidsdk-ddms android-tools-fastboot androidsdk-hierarchyviewer android-tools-fsutils androidsdk-traceview
#Then, install repo:
mkdir -p ~/bin
curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
reboot your system or use the following in terminal to load the .profile file again:
. ~/.profile
2. make a folder (any name would do) to store the code. Go into the folder (i.e. cd /home/uersername/BlissPop) and get the source code:(you'll only get the latest main branch this way - I suppose. All commands in terminal console have assumed that the source code root folder is current folder)
repo init -u https://github.com/TeamBliss-LP/android.git -b lp5.0
repo sync
#Note: this will download the specified branch lp5.0 (lollipop 5.0 of Blisspop) onto your local drive. The source as of Jan. 23, 2015 is 10+GB, so be patient and try different vpn connections to get the most desirable speed. It took me overnight to download the source code.
3. Build
#Note: This is the tricky part. The existing documentation of Blisspop or other similar open source project does not explicitly explain whether you need to sync full project tree to be able to just compile specific modules (i.e. Source Folder/packages/apps/Email). After experimentation, the answer is a most definite yes. The reason is that system apps usually have many framework-level dependencies, which means downloading the entire source code is the safest way to ensure a successful build. However, you don't need to build the entire rom, or firmware, which takes hours on a single core Asus 1215T.
#To compile specific system apps. After repo sync
a) initiate build environment
. build/envsetup.sh
breakfast bacon
#Note, if you encounter device tree related errors in build steps below, try repeating the above two steps, and run repo sync after breakfast bacon. This, according to CM documentation, will download the specific device tree into the local repository.
b) build the specific app and all its dependencies
#go into the app folder (i.e. cd /home/username/Blisspop/packages/apps/Email)
mma
# Wait until the compilation is over, this on a single core AMD Asus 1215T takes about 2-3 minutes.
#The compiled and signed app should be in out/product/bacon/Email folder. Ready to be copied and flashed using root explorer in your OnePlus's system/app folder.
#When rebuild an app after mma has been executed at least once, no need to build all dependencies, hence:
#go into the app folder (i.e. cd /home/username/Blisspop/packages/apps/Email)
mm
Inscription à :
Articles (Atom)