Hey!
So I wanted to create a device tree for my device. An LG.
I know how to get those BoardConfig.mk Android.mk and those original mk files, but when I look at other device trees, they have a whole lot more. They have vendorsetup, extract-files.sh and some folder like Bluetooth, wifi, etc...
Do I include those is my tree? If so, how do I get them? I don't have a stock zip, LG doesn't provide one for some reason, just the source code to their kernel and firmware. Could I get it from there?
Thanks for reading! Hope to hear back soon!
Related
I am a linux user...
Anyone can share the howto or if there are any guides?
+1 bumping this thread
Second that...
http://www.koushikdutta.com/2009/08/build-configuration-for-t-mobile.html#links
He seems to have a script to compile the Kernel...
I don't know to what extent this would help us but it is a start. I dont quite know how the apps are installed on a new ROM....
It would be nice if someone can explain what is needed and what is optional in the kernel and some of the mods that other people are doing and how they integrate in the OS.
I see a lot of improvements in the new ROM's but no how-to on doing it your self. I thought that was the point of having open source OS.
I would quite like this as well =o)
Have made a bit of a start by following this:
http://source.android.com/download
Shows you how to get all the code and do a build.
I believe the next thing would be to pick the required files from the output folder of the build, dump the boot.img and replace the kernel with 32B or 32A one, add the Magic model config file (to ramdisk) and recreate the boot.img
Replace/Add any modules required like maybe wifi or bluetooth, then need to change the build.prop file and put it all in to update.zip and sign the file.
Haven't had time to test this out but seems kind of logical...maybe?
Hello!
I'm following the android.com tutorial, but I want to ask: how can I download the donut branch? There's no mention in the entire site about it... Also, the cyanomod's multitouch and so on, where does it come from? Is it made by himself or it's somewhere in the net?
Thanks
Learn how to use GIT to get the donut branch from here: http://android.git.kernel.org/
Proble is that it doesn't specify the donut project path
Is there a command to list all project paths? I can't seem to find it
L10nH34Rt said:
Proble is that it doesn't specify the donut project path
Is there a command to list all project paths? I can't seem to find it
Click to expand...
Click to collapse
Code:
git branch -a
in any local git directory
Ok, then so far I've downloaded the donut branch, and compiled too. What now?
1. how to create a ROM from the made files?
2. how to compile the kernel / how to replace the one created with the make command with the one I'm running on?
3. is there any option I can configure to fit my phone? (HTC Magic 32A)
4. how can I root my ROM?
thanks
there is this guide that i have found:
http://www.koushikdutta.com/2009/08/build-configuration-for-t-mobile.html
'make' finished with success but i can't find how to transform it into 'update.zip' file...
anyone?
It says that in the link you have posted yourself.
ok guys i am trying to compile Launcher2 from source i am running ubuntu 9.1, with eclipse(for jave ee) 3.5.1 and adt installed. i have downloaded the source from google. Launcher2 though is not sent when syncing repo, so i got the Launcher2 source from cyanogen. As far as i figure unless i missed something i should be able to click file > new project > android project. this brings up a window, click the bullet load from source choose the directory where Launcher2 is and choose API level 7 then click finish. it loads with 2 errors, cannot compile until build paths are fixed and that the folder "gen" isn't there. "gen" is an auto-generated folder by eclipse that follows after the source code to fix those errors, you either make a change or delete the gen folder. since the gen folder is auto-generated deleting it just forces the gen folder to be remade to make the compiler happy. when that happens approximately 184 errors occur(they were there all along) the gen files were just hiding them.
what i am trying to figure out is what i need to do to get this to compile? am i missing a step in the process? am i missing something? i've been banging my head against this wall for about 2 weeks looking for every possible angle that i can think of including putting Launcher2 into it's respective folder made by git and running make. it errored out. i'm at a loss and any kind of help would be greatly appreciated.
i would like to add, this is straight from cyanogens github no modifications and no changes. also no modifications or changes to any files aquired by repo. i'm just trying to compile a "stock" Launcher2, once i am able to compile that i will rercompile with any changes i might want to make.
Original post: forum.cyanogenmod.com/topic/41583-hello-hello-bug-cant-hear-caller/
It seems like I'm suffering from this bug
code.google.com/p/cyanogenmod/issues/detail?id=4681
although I found the commit
github.com/CyanogenMod/android_device_samsung_crespo/commit/49cb776c1a5d056c345d90465f8006ef23d947b0#libaudio/AudioHardware.cpp
which (hopefully) fixed this bug but the commit only merged into ics branch not gb branch (CM7).
I got cygwin and NDK set up, but I have no idea how exactly to compile libaudio.so module.
After selecting your target, enter:
Code:
make audio.primary.herring
from cygwin?
the target is the libaudio folder, right?
does it involve NDK?
I also need library file (libhardware_legacy.so, libcutils.so, libmedia.so, etc) isn't it? I have the files, where do I put those files?
gleenfield97 said:
from cygwin?
the target is the libaudio folder, right?
does it involve NDK?
I also need library file (libhardware_legacy.so, libcutils.so, libmedia.so, etc) isn't it? I have the files, where do I put those files?
Click to expand...
Click to collapse
Your target should be listed in the set of options before you begin building. In this case, it's crespo or crespo4g for the Nexus S or Nexus S 4G, respectively. If you need to build other modules, locate the Android.mk file for the module you want to build and locate the value under LOCAL_MODULE. The destination for the file(s) in question will be printed after the build is completed. What happens from there depends on what you intend to do with it.
Getting familiar with the build system will make things much more easier and faster for you in the long run.
Thanks for your guide.
Unfortunately, I still can't fully understand so I end up using the script provided by nicandris
forum.xda-developers.com/showthread.php?t=969266
instead of building the module, I build the whole rom.
I am in the process of gathering source from cm7 devices and piecing them together into a full source tree for cm7 on the doubleshot. I am currently using the extract-files.sh script to pull proprietary files from the stock rom of the doubleshot. This script uses the proprietary-files.txt file to pull the appropriate files from the /system folder in the rom.
My question is how do I know which files to pull from the rom? Since there is no source code available for the doubleshot, I am starting with the source of the closest device (htc pyramid) which is now in the cyanogenmod source tree.
I'm using the proprietary-files.txt from here but the problem with that is that it was intended for cm9. There is no source code available for the pyramid in cm7.
Assuming that there are no differences between the proprietary files for ics and gingerbread (highly unlikely), there are still differences between the pyramid and doubleshot. So if anyone knows what to do please let me know(I would think anyone with this knowledge would have already passed this point in development, i.e. kornyone, but it never hurts to ask right??)
Thanks in advance xda community
well a good start is replacing the entire folder entire system.bin and xbin, system.lib.hardware, system.lib.modules, boot.img, libhardwarelegacy.so, libsensorservice, libhtcril, libril, and thats all i could think of off my head. also next time post in general beccause it is still a question
Hi guys,
i'm currently owning a XZs and (i know it has a separate forum) i have trouble compiling AOSP for my xperia.
Since this subforum is a bit larger, maybe some of you can give me a hint. After i put the downloaded vendor folder in my repo and sync it
it get errors VQZip.h not found. This header is nowhere on my system as well the repo.
if i remove the folder /hardware/qcom/msm8998 folder, i can compile it but it does not boot.
I think that the vendor folder interferes with some headers from this folder. I'm following the official build guide and cannot see where i'm wrong.
Thank you for any help guys and also sorry for spamming your forums.
repo got updated today.
You can delete this thread.
jvarg said:
Hi guys,
i'm currently owning a XZs and (i know it has a separate forum) i have trouble compiling AOSP for my xperia.
Since this subforum is a bit larger, maybe some of you can give me a hint. After i put the downloaded vendor folder in my repo and sync it
it get errors VQZip.h not found. This header is nowhere on my system as well the repo.
if i remove the folder /hardware/qcom/msm8998 folder, i can compile it but it does not boot.
I think that the vendor folder interferes with some headers from this folder. I'm following the official build guide and cannot see where i'm wrong.
Thank you for any help guys and also sorry for spamming your forums.
Click to expand...
Click to collapse
EDIT:
build worked with the latest update.
https://transfer.sh/KCisC/boot.img
https://transfer.sh/O3W6i/system.img
https://transfer.sh/11fts8/userdata.img