Database Develop

How Hard?

im so in the mood to learn and make some roms....i wanted to ask can somoene help me by guiding me or maybe linking me to the right direction because i really want to customize roms...not too hard but to be able to tweak a bit on roms...pleae can someone help???

I'd recommend starting with going to the Android Open Source Project. They have full docs on how to download and compile the source code. Once you've successfully built a stock image you can start mixing and matching or tweaking code.
You can also Google things like "building froyo source" and such to find tutorials. Many of those will be for specific phones but the general principals are similar.
If you want to jump in the deep end Cyanogen's wiki has a tutorial on building Cyanogenmod from source.
Sent from my Nexus One using XDA App

ok thanks alot!

[Question] Gingerbread on Tattoo?

Hey guys,
Now that Gingerbread is out, I think most questions on people's minds are: Can it happen? What's needed?
Sent from my Tattoo using XDA App

I'm trying to do something about it stay tuned...

i just saw a youtube video about a wildfire running an early built,
so i thinks its not a matter of resolution.

I just hope the CM can be work on ROM.

We need AOSP sources before it can be built properly. The ones on Wildfire etc are just hacked together from an emulator image, and they run quite slowly. For the Tattoo, I'm a bit uncertain if it can be used with kernel 2.6.29, or if 2.6.32 or higher is required.

It will eventually - Froyo took a while but is here. But I can't wait for the new UI and it will be speedy if Google are telling the truth

I was WAITING for someone to ask this question
Anyway, fingers crossed

It has to be possible: http://androinica.com/2010/12/07/go...droinica+(Androinica+-++A+Google+Android+Blog)

I guess gingerbread will take some time to come on tattoo, but there is a full gingerbread theme for tattoo available here.

aliwaqas said:
I guess gingerbread will take some time to come on tattoo, but there is a full gingerbread theme for tattoo available here.
Click to expand...
Click to collapse
I guess it will be pretty soon, because Gingerbread AOSP is already available to create ROMs like fyodor's or spartm's, and Cyanogen is working on modded Gingerbread too already

gingerbread on tattoo would be GREAT
Sent from my HTC Tattoo using XDA App

@those who try to port 2.3 for tattoo: If you're successfull, plz change the icon for mobile data... it's just too tiny for our small screen!

the source code for the nexus one is out, i dont know how difficult it is to port it to another device but i hope someone tries it already

I'm trying to compile gingerbread, if somebody(or more) wants to collaborate making vendor files, we can put up a github start a collaborate rom for our tattoo
I've triend changed fyodor files, but for now i'm stuck (something wrong with libstagefright)
Somebody?

Aaroneke said:
I'm trying to compile gingerbread, if somebody(or more) wants to collaborate making vendor files, we can put up a github start a collaborate rom for our tattoo
I've triend changed fyodor files, but for now i'm stuck (something wrong with libstagefright)
Somebody?
Click to expand...
Click to collapse
Stuck when compiling or when booting?

Compiling i've managed this problem, but i changed some stuff and now i got it again, i'm trying to make new vendor files step by step using fyodor,..etc (and google ref) files just for reference, but it can take a while(if i'll get it working..)

[Q] How to get started making captivate roms

Hey Guys,
I'm a developer for a living, and I'm interested in possibly working on a custom rom for my captivate. I was doing some research on how to get started, but the stuff I found was for HTC phones and involved using a starter that only works for HTC stuff.
Where can I go to find information on doing this? I'm largely interested in trying to port gingerbread, but my understanding was that until we have the full source this wasn't really possible (at least for something actually useable on a daily basis). I see supercurio is working on gingerbread, so information specific to this would be really helpful.
Thanks guys, and sorry if this should have been put in the QA section, I figured it was related to development, and could possibly be a sticky if it leads to useful info.

Pretty broad question. First requirement, is obviously...learn java.
I'm not sure if there's any specific "HOW-TO CODE YOUR OWN CAPTIVATE ROM" threads anywhere; there's general information available on http://developer.android.com , but modifying ROM's depends on the device it was written for.
As far as porting gingerbread, it will be very difficult without source and will definitely require quite a bit of kernel work. For information specific on this, supercurio would be the one to ask. Of course, the IRC's are also a great place to get information.
By the way, welcome to XDA! And I commend your motivation to develop stuff for the community here.

http://forum.xda-developers.com/showthread.php?t=869614
Doc over in the I9000 forums has the above thread started. I look there.

geokhentix said:
Pretty broad question. First requirement, is obviously...learn java.
I'm not sure if there's any specific "HOW-TO CODE YOUR OWN CAPTIVATE ROM" threads anywhere; there's general information available on http://developer.android.com , but modifying ROM's depends on the device it was written for.
As far as porting gingerbread, it will be very difficult without source and will definitely require quite a bit of kernel work. For information specific on this, supercurio would be the one to ask. Of course, the IRC's are also a great place to get information.
By the way, welcome to XDA! And I commend your motivation to develop stuff for the community here.
Click to expand...
Click to collapse
Again, I am a developer for a living. I know Java, I'm not looking for coding tutorials. I'm looking for information specifically regarding the captivate.
As far as gingerbread, it sounds like what you are saying is that what people like supercurio are working on is not really gingerbread? More of a Frankenstein created with the sdk, mashing together 2.2 kernels and what has been released for 2.3?

lbbo2002 said:
http://forum.xda-developers.com/showthread.php?t=869614
Doc over in the I9000 forums has the above thread started. I look there.
Click to expand...
Click to collapse
Looking at that thread, it appears the roms being made are just edited versions of already compiled roms? Is samsung not required to post the full source of their roms?
I'm assuming the issue with starting with the original android source, is that we wouldn't have drivers for half of the hardware in the phone. Is the only choice then to load the already compiled drivers from the samsung builds into the rom?

epoplive said:
Again, I am a developer for a living. I know Java, I'm not looking for coding tutorials. I'm looking for information specifically regarding the captivate.
As far as gingerbread, it sounds like what you are saying is that what people like supercurio are working on is not really gingerbread? More of a Frankenstein created with the sdk, mashing together 2.2 kernels and what has been released for 2.3?
Click to expand...
Click to collapse
There are different levels of making ROMs IMO.
You can combine work from others and make your own ROM. This requires no coding experience. For instance, I took JH7_OTA, dropped in Atinms Voodoo 3 kernel, removed bloatware, added my own custom framework (icons), etc., signed it and flashed it.
Then there is the whole Kernel side of things that requires an entire development environment (Linux) and C/C++ programming skills. I'm trying to get to this point. You can start by downloading the source and building it in your own environment familiarizing yourself with the codebase.

Indeed. Packing a ROM and making the contents of the ROM are two different sides of the spectrum. Even some minor framework modifications can be performed by the most tech-inept, as long as they have a good resource to work off of.
epoplive said:
Again, I am a developer for a living. I know Java, I'm not looking for coding tutorials. I'm looking for information specifically regarding the captivate.
As far as gingerbread, it sounds like what you are saying is that what people like supercurio are working on is not really gingerbread? More of a Frankenstein created with the sdk, mashing together 2.2 kernels and what has been released for 2.3?
Click to expand...
Click to collapse
I was only prodding fun when I mentioned learning Java, just to break the ice. All I'm saying is trial and error is the best way to learn Android if you're already a decent programmer. Without knowing what the source code looked like before Samsung owned it, we don't really have a base environment to work off of, which means we are modifying work that was already modified from stock; which is why it will be pretty hard to find a lot of definitive coding information about the Captivate.
Supercurio isn't making a frankenstein 2.2-2.3 hybrid. The kernel is where all of the information about your hardware resides. Supercurio needs to take the Gingerbread kernel from the Nexus S, and modify it to run with our hardware. You can't run a 2.3 ROM without a 2.3 kernel; so we CAN'T use a 2.2 kernel to run full gingerbread; and since a 2.3 kernel doesn't exist for the Captivate, he is using the Nexus s's kernel as a base, or as a reference to merge the differences between the two, creating a kernel that will support the Nexus S ROM on a phone that isn't the Nexus S.
epoplive said:
Looking at that thread, it appears the roms being made are just edited versions of already compiled roms? Is samsung not required to post the full source of their roms?
I'm assuming the issue with starting with the original android source, is that we wouldn't have drivers for half of the hardware in the phone. Is the only choice then to load the already compiled drivers from the samsung builds into the rom?
Click to expand...
Click to collapse
Correct. We don't have the source code for Froyo yet for the Captivate(or an OTA for that matter ), a lot of ROM's being made are based off of the SGS I9000 2.2 source, and because we have that source, we have a pretty much fully functional "captivated" i9000 kernel.

geokhentix said:
Indeed. Packing a ROM and making the contents of the ROM are two different sides of the spectrum. Even some minor framework modifications can be performed by the most tech-inept, as long as they have a good resource to work off of.
I was only prodding fun when I mentioned learning Java, just to break the ice. All I'm saying is trial and error is the best way to learn Android if you're already a decent programmer. Without knowing what the source code looked like before Samsung owned it, we don't really have a base environment to work off of, which means we are modifying work that was already modified from stock; which is why it will be pretty hard to find a lot of definitive coding information about the Captivate.
Supercurio isn't making a frankenstein 2.2-2.3 hybrid. The kernel is where all of the information about your hardware resides. Supercurio needs to take the Gingerbread kernel from the Nexus S, and modify it to run with our hardware. You can't run a 2.3 ROM without a 2.3 kernel; so we CAN'T use a 2.2 kernel to run full gingerbread; and since a 2.3 kernel doesn't exist for the Captivate, he is using the Nexus s's kernel as a base, or as a reference to merge the differences between the two, creating a kernel that will support the Nexus S ROM on a phone that isn't the Nexus S.
Correct. We don't have the source code for Froyo yet for the Captivate(or an OTA for that matter ), a lot of ROM's being made are based off of the SGS I9000 2.2 source, and because we have that source, we have a pretty much fully functional "captivated" i9000 kernel.
Click to expand...
Click to collapse
Ah, thanks, that's pretty much the information I was looking for.

Onecosmic's ICS Port RC3 is up for i9000/b and vibrant and cappy will be very soon.

Code is back up, we're hosting there again now. Grooby's thread is not under control by us and anything he says/does is not condoned by onecosmic or his team.
We're up to rc3 now and the rom is much more stable than before, seems to be performing better and people are working on fixes for gps,it should be working soon. updates are on the google code pages here: http://code.google.com/p/ice-cream-sandwich-sgs/
The rom should now be flashable from anything,just wipe and flash.

Thanks, will give it a try
Sent from my SGH-T959 using XDA App

lol, hopefully someone is able to put up a new mirror for it.
xD
Seems like a very popular file.

CM t9 Dailer and cm launcher now as a flashable zip
Thread Link

This Rom is fast and smooth ,music player is perfect loving it, gallery work great too and there is a fix for root in the i9000 tread http://www.megaupload.com/?d=S67I9Q0L .front camera is still broken ,recorder.and brightness not working just those fews bugs to be fix and this rom is going to be one of the best ICS rom .great work onecosmic's..........

I really don't understand the vibrant dev community. Or maybe it's just a problem with xda in general the the belief that every single dev here is on his own to create his own grand master ROM and screw the rest (besides the big names like Cyanogen and others).
But when there is another perfectly good ROM out there, that is under active development and has already solved many of the major problems with the current code, and then someone forks the code and essentially starts over, it is a real tragedy.
"onecosmic," please work with the devs in this thread to improve the ICS build that already has months of work put into it, instead of creating your own:
http://forum.xda-developers.com/showthread.php?t=1362961

a2296455 said:
I really don't understand the vibrant dev community. Or maybe it's just a problem with xda in general the the belief that every single dev here is on his own to create his own grand master ROM and screw the rest (besides the big names like Cyanogen and others).
But when there is another perfectly good ROM out there, that is under active development and has already solved many of the major problems with the current code, and then someone forks the code and essentially starts over, it is a real tragedy.
"onecosmic," please work with the devs in this thread to improve the ICS build that already has months of work put into it, instead of creating your own:
http://forum.xda-developers.com/showthread.php?t=1362961
Click to expand...
Click to collapse
Taking nothing away from neobuddy or teamhacksung, onecosmic did have the first ICS for the Galaxy S posted.
http://forum.xda-developers.com/showthread.php?t=1338636

a2296455 said:
I really don't understand the vibrant dev community. Or maybe it's just a problem with xda in general the the belief that every single dev here is on his own to create his own grand master ROM and screw the rest (besides the big names like Cyanogen and others).
But when there is another perfectly good ROM out there, that is under active development and has already solved many of the major problems with the current code, and then someone forks the code and essentially starts over, it is a real tragedy.
"onecosmic," please work with the devs in this thread to improve the ICS build that already has months of work put into it, instead of creating your own:
http://forum.xda-developers.com/showthread.php?t=1362961
Click to expand...
Click to collapse
stop being a steve jobs

a2296455 said:
I really don't understand the vibrant dev community. Or maybe it's just a problem with xda in general the the belief that every single dev here is on his own to create his own grand master ROM and screw the rest (besides the big names like Cyanogen and others).
But when there is another perfectly good ROM out there, that is under active development and has already solved many of the major problems with the current code, and then someone forks the code and essentially starts over, it is a real tragedy.
"onecosmic," please work with the devs in this thread to improve the ICS build that already has months of work put into it, instead of creating your own:
http://forum.xda-developers.com/showthread.php?t=1362961
Click to expand...
Click to collapse
so you want onecosmic to stop working on the rom that allowed neo to even release ICS on the vibrant. Also he doenst have a vibrant, this rom is originally for the sgs and is ported over, hence why we need to flash another kernel. The problem with the vibrant community isnt the devs its the people like you that expect a rom that is 100 percent perfect and on top of that does your dishes and makes bacon
What you should do is go talk to neo about helping out with the rom instead of kanging cm and other applications. I swear his roms have more bloat on them then twiz.

a2296455 said:
I really don't understand the vibrant dev community. Or maybe it's just a problem with xda in general the the belief that every single dev here is on his own to create his own grand master ROM and screw the rest (besides the big names like Cyanogen and others).
But when there is another perfectly good ROM out there, that is under active development and has already solved many of the major problems with the current code, and then someone forks the code and essentially starts over, it is a real tragedy.
"onecosmic," please work with the devs in this thread to improve the ICS build that already has months of work put into it, instead of creating your own:
http://forum.xda-developers.com/showthread.php?t=1362961
Click to expand...
Click to collapse
LMAO, dude you're an idiot. I hope you brick your phone just because.

bearsfan85 said:
What you should do is go talk to neo about helping out with the rom instead of kanging cm and other applications. I swear his roms have more bloat on them then twiz.
Click to expand...
Click to collapse
Now that was uncalled for.
I understand that onecosmic was the first to build a functional ICS for the Galaxy S series, but that does not mean he has to be the only one. What's wrong with KANG'ing something? Neo isn't taking credit for anything, he's gave credit where credit was due.

I'm on neobuddy ics can i flash firs the rom and them the kernel or this rom uses a different partitions and i need to flash first the kernel reboot recovery flash rom/flash kernel and them reboot system
Sent from my SGH-T959 using xda premium

Passion v6 & v7 vs Onecosmic
What we want in this community is quality ROM's. No one has a monopoly on good ideas and we as users always benefit when we have more than one group working on competing ideas.
I tried and respect Neo's ICS Passion Roms. I've been using them since v5. v6 is a good daily ROM. v7 was too laggy for me.
Onecosmic's 4.0.3 ROM is much smoother. From the first boot. Brightness doesn't work. But everything else does.
For me, this demonstrates the value in alternatives.
Good work Onecosmic.

Try screen filter if you need to lower brightness
Sent from my SGH-T959 using XDA App

From my understanding, Neo's rom is still 2.X kernel while Onecosmic's is 3.X based. Different approaches I guess. Onecosmic is more than happy to help out with the Vibrant community, you just have to ask. I tried the latest and had an issue with the cpu staying on full blast and chewing up the battery so I went back to stock MIUI until he hammers a few other things out.

Nice way to turn a pretty thread in a flamewar, guys :/
Either way, does video recording works here?
And can I flash over Neo's ICS build or only over ICS?
I wish the OP was more informative...

So the OP says to first flash an ICS kernel.
Can I use the Vibrant ICS kernel here or do I use an i9000 one?

After installing this rom my phone will not reboot into recovery... is their a special way to get back into recovery?

Can anyone check if there mute/unmute issue present on this ROM ?

Anyone else have no service after flashing this?

Budding dev needs some help

Hello all. I've recently been trying to get into Android development, more specifically Kernel development. I've played around with some kitchens and looked at the GB kernel sources from Samsung and tweaked it around.
Previously I previously learned Java to a point where I can put basic lines down and also more advanced stuff but with a bit of help here and there.
I have one question though, what would be the recommended path for creating an ICS Kernel. My plan is to start of with something "stock" and build up but I'm not quite sure what to consider stock seeing as the S1 never got ICS officially. Would I have to use CM9's Kernel sources and if so where do I acquire them.
I also have a good understanding of Ubuntu and its terminal and have a functional idea of what I'm doing there.