Database Users

anyone know how to build from aosp?

im trying to learn how to build i am a complete noob to linux but i learn quick already installed ubuntu 11.04 and have jdk 5 already installed for froyo as i would like to make a 100% working froyo build. the repo sync is still running and after that i am installing sdk for linux i just need a starting point to making the roms and kernels into a flashable.zip and other pointers that would be helpful. any advice is welcomed thanks in advance
host Executable: acp (out/host/linux-x86/obj/EXECUTABLES/acp_intermediates/acp)
/usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/gcc/x86_64-linux-gnu/4.5.2/libstdc++.so when searching for -lstdc++
/usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/gcc/x86_64-linux-gnu/4.5.2/libstdc++.a when searching for -lstdc++
/usr/bin/ld: cannot find -lstdc++
collect2: ld returned 1 exit status
make: *** [out/host/linux-x86/obj/EXECUTABLES/acp_intermediates/acp] Error 1
i get this error when trying to "make"
fixed it have to use this sudo apt-get install gcc-multilib g++-multilib zlib1g-dev lib32z1-dev lib32ncurses5-dev gperf
compiling now

skater4690 said:
all the stuff you said...
Click to expand...
Click to collapse
You're trying to build an aosp rom for the vibrant with 2.2 code? You do know there's a reason we don't have a build like that, correct?
The closest aosp 2.2 we got was CM6 partially functioning. Besides, gingerbread is what people want.
Sent from my SGH-T959 using XDA App

geoffcorey said:
You're trying to build an aosp rom for the vibrant with 2.2 code? You do know there's a reason we don't have a build like that, correct?
The closest aosp 2.2 we got was CM6 partially functioning. Besides, gingerbread is what people want.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Yes that's what I'm gonna try to do whether everyone wants gb doesn't matter to me I'm doing it for myself and to learn

This is a great reference that got me started. A lot of basics are covered in rom building, and it might answer some questions you don't even know you have yet.
Good luck.
http://forum.androidcentral.com/hacking/6037-general-rom-faq.html

Br1cK'd said:
This is a great reference that got me started. A lot of basics are covered in rom building, and it might answer some questions you don't even know you have yet.
Good luck.
http://forum.androidcentral.com/hacking/6037-general-rom-faq.html
Click to expand...
Click to collapse
Thanks ill take a look at it when I get home I have a 15 page guide lol but ill look through that too never too much info

You might want to start with the CM7 source. Far as I know, that's the most stable code tree you can find for the Vibrant - the raw AOSP code will not work out of the box.
Starting from 2.2 AOSP you won't even know if it's a missing driver, bad compile, bug you introduced, bad build environment, etc when it doesn't work. Start with something that does work, and you can learn and try things out in a more controlled environment.

Saiboogu said:
You might want to start with the CM7 source. Far as I know, that's the most stable code tree you can find for the Vibrant - the raw AOSP code will not work out of the box.
Starting from 2.2 AOSP you won't even know if it's a missing driver, bad compile, bug you introduced, bad build environment, etc when it doesn't work. Start with something that does work, and you can learn and try things out in a more controlled environment.
Click to expand...
Click to collapse
Well I wanted to do a froyo build and I don't think there was much for cm6 on the vibrant
But if you wanna toss me a link for cm6 then ill give that a shot
Side note this is my 666 post lol

skater4690 said:
Well I wanted to do a froyo build and I don't think there was much for cm6 on the vibrant
But if you wanna toss me a link for cm6 then ill give that a shot
Side note this is my 666 post lol
Click to expand...
Click to collapse
I suggested CM7 because it works. Don't think CM6 ever did, very well, so it doesn't really tie in with my suggestion to start from a functional build..
Here's CM7 code checkout and build instructions: http://cmsgs.com/mediawiki/index.php?title=Building_and_Installing_Gingerbread_from_Source_vibrant
I can't find the CM6 code in my quick search, sorry.

Saiboogu said:
I suggested CM7 because it works. Don't think CM6 ever did, very well, so it doesn't really tie in with my suggestion to start from a functional build..
Here's CM7 code checkout and build instructions: http://cmsgs.com/mediawiki/index.php?title=Building_and_Installing_Gingerbread_from_Source_vibrant
I can't find the CM6 code in my quick search, sorry.
Click to expand...
Click to collapse
Its cool Eugene has a nice cm6 rom but its not finished ill ask whoever made a aosp froyo rom for the fascinate for some pointers and cant do gb cause I set my jdk for froyo which uses jdk 5 I'm trying to learn everything all at once lol Linux and building Roms lol I'm familiar with how android works system files and such just needs tobhurry up so I can get out of work and get on doing some things

If you are trying to build a 100% working AOSP ROM for the vibrant you are waiting your time. Without source code for the drivers is not possible. Unless you know somebody that works in the development team in Samsung that can give you access to the source code you are out of luck...If you just want to mess around to learn then go for it...

[Q] Gingerbread to Honeycomb

First time posting, but been a follower of this site. I have managed to find things when needed but this time I could not find what I'm looking for, hence the post.
I have a color nook that I bought used from a guy at work. It has the CM7 mod installed in the internal memory version 2.3.3. It's been working find and I have no problem with it for over 6 mos now.
I was wondering what would be the easier way to upgrade from gingerbread to Honeycomb 3.0 or higher. Would it be like upgrading from stock to honeycomb.
Any directions to a guide would be greatly appreciated.
Thank you.
Manik

Do not use honeycomb. Its is completely unstable because it is just an SDK port. With no source code it isn't going to get any better.
You would spend your time better by upgrading to the latest cm nightly.
Sent from my LG Optimus V using Tapatalk

koopakid08 said:
Do not use honeycomb. Its is completely unstable because it is just an SDK port. With no source code it isn't going to get any better.
You would spend your time better by upgrading to the latest cm nightly.
Sent from my LG Optimus V using Tapatalk
Click to expand...
Click to collapse
Thanks for the advise.

[dev][wip]Porting android 4.1 sdk version

Hi,
i am working on a port of android 4.1 (jelly bean) for the play.
like we did with android 4.0
this is going to be easier to port as we can use most files from android 4.0
Nick

progress:
Just got sdk image, 4.1 is rally great on my computer!!!

you sir...are the best!

Sounds awesome as hell. But thought you needed moar moeny to keep developing? Or did you get it after-all?

Will this run better than ICS? and I'm assuming touchpads work? (whatever worked on ICS that is)

Here is a video in this thread showing improvements from ICS 4.0. It shows an increase in FPS and smoothness. http://forum.xda-developers.com/showthread.php?t=1736726
Sent from my R800i using xda premium

Here is the system dump for everyone who wants to port it
http://forum.xda-developers.com/showthread.php?p=27963070

hi,
i still need some money but i have almost enough.
got the system.img unpacked replaced some libs some /bin files and lot of /etc files
hanging on kernel logo (hanging, not rebooting) with logcat: netd1.0 starting

nickholtus said:
hi,
i still need some money but i have almost enough.
got the system.img unpacked replaced some libs some /bin files and lot of /etc files
hanging on kernel logo (hanging, not rebooting) with logcat: netd1.0 starting
Click to expand...
Click to collapse
I was getting the same error when porting.
Is there any specific kernel changes in 4.1?
Sent from R800x

I just looked around the forum, therw are already sdk ports for the one x and an ota update for the gnex. Pretty quick.
Gesendet von meinem Xperia Play mit Tapatalk 2

i was starting to port 4.1 too, and im really sure its a kernel problem.

Kernel isn't a problem.
Can be some libs or some missing files

idea
make the google now launching by using the search button on xperia play.
google search with simple typing on the search button and the google now with hold typing on the search button

you should ask to some help from doomlord

hi,
doomlord can't help as he is an kernel developer and i am kernel/rom developer
he doesn't know very much about developing for roms

It shouldn't be too long before CyanogenMod at least takes a stab at doing JB, so in addition to what nickholtus has already said he's working on, JB shouldn't take too long to make it to us. Given Google's numbering scheme, I would imagine that 4.1 isn't such a monumental change from 4.0 to merit a complete reworking.

lightningdude said:
It shouldn't be too long before CyanogenMod at least takes a stab at doing JB, so in addition to what nickholtus has already said he's working on, JB shouldn't take too long to make it to us. Given Google's numbering scheme, I would imagine that 4.1 isn't such a monumental change from 4.0 to merit a complete reworking.
Click to expand...
Click to collapse
I hope OP's successful as I'd flipping love to get a JB ROM on my phone with its supposed speed increase.
Although, I'm still waiting on this magic Linaro stuff which doesn't look like it'll deliver

We will be able to get JB working as well (if not better) than ICS once official source code is released mid July

i am porting the galaxy nexus version now.
as it is better then the sdk (leaked ota build)

nickholtus said:
i am porting the galaxy nexus version now.
as it is better then the sdk (leaked ota build)
Click to expand...
Click to collapse
Awesome

Trying to port JB ROM

Hey guys.
I am new to android developing.
I started by porting the CM10.1 ROM from HTC Desire, but my phone is stuck at the Huawei logo when it boots up.
I can still flash another ROM, but that is not the problem.
I want to know how to fix this. I want it to go past the Huawei Logo.
By the way, I used this procedure: http://forum.xda-developers.com/showthread.php?t=1598713 and I used Aurora ICS 5.0 for the base ROM. I know it doesn't have the same version of android, but there is no reason I shouldn't be experimenting like this.
Can anyone help?
Thanks.

rqmok said:
Hey guys.
I am new to android developing.
I started by porting the CM10.1 ROM from HTC Desire, but my phone is stuck at the Huawei logo when it boots up.
I can still flash another ROM, but that is not the problem.
I want to know how to fix this. I want it to go past the Huawei Logo.
By the way, I used this procedure: http://forum.xda-developers.com/showthread.php?t=1598713 and I used Aurora ICS 5.0 for the base ROM. I know it doesn't have the same version of android, but there is no reason I shouldn't be experimenting like this.
Can anyone help?
Thanks.
Click to expand...
Click to collapse
Delete phone.apk and try it?
Sent from my U8800-51

You can't port CM10.1 ROM to ICS ROM as base. That is inpossible.

I know
Mlopik said:
You can't port CM10.1 ROM to ICS ROM as base. That is inpossible.
Click to expand...
Click to collapse
I know, but it is not completely impossible.
I also tried to port it with CM10.1 that you are trying to fix, but I still get the same thing.
I will setup logcat and upload the information here.
Thanks.

Need to ask something
Hey again.
I haven't had time to do anything to my phone yet.
I am replying to ask if there is an awesome tutorial out there that could help me with this porting?
Currently, to port my ROM, I replaced files in port ROM from base ROM. Should I replace files in base ROM from port ROM?
Thanks for the help.

Hi Again
Hello.
I found out that there was a problem with the base ROM.
I have ported CM10.1 from U8800! Yaay!
But there are four things that are not working:
- WiFi
- Bluetooth
- Cam Recording
- Sound
Can you guys tell me how to fix the audio? In the logcat, it says that there is no sound output.
Thanks

CatLog results
Hey guys.
I've got the log attached to this reply. Have a look at the audio events and see what is wrong. I can't figure it out by myself.
Thanks

When will you releasing it fully functional?

Working on JB
Djuganight said:
When will you releasing it fully functional?
Click to expand...
Click to collapse
I have just ported the Jelly Bean from u8800pro to u8800non-pro, so I will be working on this ROM.
Seriously, I have no idea when I will be releasing a fully functional ROM. Because I have my studies as well, so I don't get much time to work on the ROM.
The audio is working in this ROM (wasn't working in the previous port),
The things that are currently not working are:
- WiFi
- Bluetooth
- Video Recording
I will try my best to do as much as possible.
I am new at building android ROMs, so please don't expect too much from me
I will be needing some help from other developers as well.
Do you think I should make a thread for this? or is there already enough not-fully functional JB ROMs there?
Thanks.:good:

Lololololol ridiculous!
Another porting, same issues...
How many are now? 4, 5 Jelly beans?
Ooo man, some times is just better to stay quiet....

Djuganight said:
Lololololol ridiculous!
Another porting, same issues...
How many are now? 4, 5 Jelly beans?
Ooo man, some times is just better to stay quiet....
Click to expand...
Click to collapse
I know how you feel. I also feel that way.
I would like to build Jelly Bean from source, like Blefish is doing right now, but I need a 64bit computer for that (mine is only 32bit. Unless there is a hack for this, I can't build from source.
I think everyone is going to start porting Jelly Bean ROMs until one starts working. :silly:

Everyone is porting the rom with the intention of making ir fully working and then abandon development. Why don't you and others continue the work that is already done instead of making a new port which will end up like the others.
Like your are having compatibility issues due to your 32bit computer, perhaps our device is incompatible with JB...

Djuganight said:
Everyone is porting the rom with the intention of making ir fully working and then abandon development. Why don't you and others continue the work that is already done instead of making a new port which will end up like the others.
Like your are having compatibility issues due to your 32bit computer, perhaps our device is incompatible with JB...
Click to expand...
Click to collapse
U8800 is compatible with JB.

Djuganight said:
Everyone is porting the rom with the intention of making ir fully working and then abandon development. Why don't you and others continue the work that is already done instead of making a new port which will end up like the others.
Like your are having compatibility issues due to your 32bit computer, perhaps our device is incompatible with JB...
Click to expand...
Click to collapse
Our device will remain compatible with every new android untill android will be using some new architecture of processor, so "sometimes it's better to stay silent".
OP, abandon your trials of getting a working JB using copy-paste ports. It can be only ported from source.
P.S.: just install ubuntu x64 and try to build something like CWM recovery out of forumber's source. If it builds, you can build anything you want. Today's computers know how to emulate x64. I'm myself using an old pentium d 820 (i386, sse2 and that's all) and I can build.

Mlopik said:
U8800 is compatible with JB.
Click to expand...
Click to collapse
That I don't know for sure but I believe our is. But why 4 or 5 JB around, all with exactly same issues
Now I and others also pick up a JB Rom, mod it here and there and then instead of 4/5 roms we can have dozens. Then again non working well. This makes sense?

Djuganight said:
That I don't know for sure but I believe our is. But why 4 or 5 JB around, all with exactly same issues
Now I and others also pick up a JB Rom, mod it here and there and then instead of 4/5 roms we can have dozens. Then again non working well. This makes sense?
Click to expand...
Click to collapse
It's still same ROM with other features.. It isn't simply fix Wi-Fi without source.

Djuganight said:
That I don't know for sure but I believe our is. But why 4 or 5 JB around, all with exactly same issues
Now I and others also pick up a JB Rom, mod it here and there and then instead of 4/5 roms we can have dozens. Then again non working well. This makes sense?
Click to expand...
Click to collapse
Because most of devs or those who like to be called developers don't have required knowledge and then leave the project as an excuse.
Honestly I have no hope that we can see a JB rom fully functional.

dark_vader said:
Because most of devs or those who like to be called developers don't have required knowledge and then leave the project as an excuse.
Honestly I have no hope that we can see a JB rom fully functional.
Click to expand...
Click to collapse
Why you don't make some for android yourself? if it's so simply.

nagato.fm said:
Our device will remain compatible with every new android untill android will be using some new architecture of processor, so "sometimes it's better to stay silent".
OP, abandon your trials of getting a working JB using copy-paste ports. It can be only ported from source.
P.S.: just install ubuntu x64 and try to build something like CWM recovery out of forumber's source. If it builds, you can build anything you want. Today's computers know how to emulate x64. I'm myself using an old pentium d 820 (i386, sse2 and that's all) and I can build.
Click to expand...
Click to collapse
So I can install ubuntu x64 on my x86 laptop? Are you talking about a virtual machine or installing ubuntu x64 on the actual laptop?
And as for others: Instead of saying that JB is not compatible with our device and all that sh*t, why don't you encourage me and give me some solutions.
Anyways, I am not posting this JB ROM until it's fully functional, because I might stop development as well (getting interested in firefox os).

rqmok said:
So I can install ubuntu x64 on my x86 laptop? Are you talking about a virtual machine or installing ubuntu x64 on the actual laptop?
And as for others: Instead of saying that JB is not compatible with our device and all that sh*t, why don't you encourage me and give me some solutions.
Anyways, I am not posting this JB ROM until it's fully functional, because I might stop development as well (getting interested in firefox os).
Click to expand...
Click to collapse
First of all,your CPU must support x64,If it supported,you can install x64 to you computer.
If you want install x64 system in virtual machine (like VirtualBox),you CPU must support VT-x or AMD-V (virtualization).
You can check virtualization and x64 support via SecurAble;
http://securable.en.softonic.com

Porting AOSP 4.2.2 to mako?

Since there's no tagged release here: https://android.googlesource.com/device/lge/mako/ for 4.2.2 yet, I was trying to use the device/lge/mako files in a checked out 4.2.2_r1 branch to build, but it's not working. I've already successfully built 4.2.1_r1 numerous times. Is this the correct way to go about it?
I'm new to building aosp so I was hoping someone could point me in the right direction on this. I'd like to get a working 4.2.2 aosp rom and then start cherry picking stuff from CM and AOKP.
Thanks :good:

Well, I never messed with aosp much, but it would probably be easier to pull the cm10.1 tree for 4.2.2
Sent from my Nexus 4 @1.5 GHz on Stock 4.2.1

inh said:
Since there's no tagged release here: https://android.googlesource.com/device/lge/mako/ for 4.2.2 yet, I was trying to use the device/lge/mako files in a checked out 4.2.2_r1 branch to build, but it's not working. I've already successfully built 4.2.1_r1 numerous times. Is this the correct way to go about it?
I'm new to building aosp so I was hoping someone could point me in the right direction on this. I'd like to get a working 4.2.2 aosp rom and then start cherry picking stuff from CM and AOKP.
Thanks :good:
Click to expand...
Click to collapse
honestly, IMHO you're better off waiting a few days. In my experience, you'll get it ported over after spending countless hours working on it, then within 6 hours the updated source will be pushed lol
I'd love a nice pure aosp 4.2.2 to check out too, but I really think it's better to wait

hp420 said:
honestly, IMHO you're better off waiting a few days. In my experience, you'll get it ported over after spending countless hours working on it, then within 6 hours the updated source will be pushed lol
I'd love a nice pure aosp 4.2.2 to check out too, but I really think it's better to wait
Click to expand...
Click to collapse
I mainly just want to do it for the experience. Having a clean AOSP 4.2.1 image was nice, and a 4.2.2 one would be better, but I'm still trying to learn my way around the android build system. I'm sure 30 minutes after I get it working google will push the source but that's ok because I'll know what the differences are by then

easiest way is to add the hardware and device paths back to the manifest here's an example of the syntax
<project path="hardware/qcom/camera" name="platform/hardware/qcom/camera" groups="qcom" revision="jb-mr1-release" />
"revision=jb-mr1-release" is one of the tags you can use to checkout the last working aosp branch
this will build you a "franken-ROM" like what the rest of us are building right now but like someone mentioned its better to just wait for aosp to add the source back if you are not to familiar with the build system
if you choose to go ahead and build anyway which you probably will you will need to hack the qcom/display/libexternal/external.cpp file to get past a compiler error in that file lines 449-456 need to read like
if(mFd == -1)
return false;
struct mdp_display_commit ext_commit;
memset(&ext_commit, 0, sizeof(struct mdp_display_commit));
ext_commit.flags = MDP_DISPLAY_COMMIT_OVERLAY;
if (ioctl(mFd, MSMFB_DISPLAY_COMMIT, &ext_commit) == -1) {
ALOGE("%s: MSMFB_DISPLAY_COMMIT for external failed, str: %s",
__FUNCTION__, strerror(errno));
hope this helps .........

It does, thank you!