Hi Guys,
Some News: Ice Cream Sandwich source code now being pushed to git servers
http://www.androidcentral.com/ice-cream-sandwich-source-code-now-being-pushed-git-servers
Will the devs here start work on implementing ICS on the 10.1v when a build for tablets is released?
Regards
Oh please do. I really appreciate all the work that has gone in to porting 3.1 for us, but as it is it still has a lot of problems. ICS being open source, it should be less painful to get it on 10.1v and make it stable...right?
Depends, nothing is sure when it comes to ROM development, I learned that with time.
To me, the easiest way would be to get direct CM9 support or through the 10.1 tab.
Related
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.
i just looked at this video http://www.youtube.com/watch?v=j4NqT6u_ODk and started looking at honeycomb. When i first looked at the froyo video the the gingerbread video i noticed how fast our devs started working on the project i was just curious if this is already being worked on or if its even been seen thanks for any replys
AFAIK, the source hasn't been released yet. Supposed to be today.
Honeycomb is for tablets only. I don't think it will work on any phone.
pfrederickjr said:
Honeycomb is for tablets only. I don't think it will work on any phone.
Click to expand...
Click to collapse
from what ive heard it will be for phones as well
It's supposed to have some smartphone support...
http://www.engadget.com/2011/01/28/android-3-0-honeycomb-emulator-has-traces-of-smartphone-support/
Dude before we start hoping and dreaming for a honeycomb update to our phone why not lets see the gingerbread one get at least one stable release. Plus like others have said honeycomb is for tablets, for now.
From what i know, google is going to release android 3.0 as honeycomb for tablets and then later on work in and refine the smartphone side and release android 3.2 as honeycomb for smartphones.
Also, before we continue to build android updates for our hero we need a newer and more stable kernel.
S0be has been working on 2.6.35 and he's done a lot of good work, i'm pretty sure deca has also contributed to that as well and deca also maintains a 2.6.29.5 kernel.
S0be kernel
once that kernel is done then the likely hood of having honeycomb running on the hero is good.
By then there will be no devs left
--------
Sent from my Sprint SuperHero
Pocker09 said:
Also, before we continue to build android updates for our hero we need a newer and more stable kernel.
S0be has been working on 2.6.35 and he's done a lot of good work, i'm pretty sure deca has also contributed to that as well and deca also maintains a 2.6.29.5 kernel.
S0be kernel
once that kernel is done then the likely hood of having honeycomb running on the hero is good.
Click to expand...
Click to collapse
Notice: Don't take this as gospel truth, I'm not a rom modder, just a kernel hacker
The hard part in getting up and running on a new Android release has very little to do with the kernel. For the most part, the Kernelspace/Userspace APIs have stayed the same. Where the problems lie are in the Kernelspace Helper Libraries and their connection with userspace. We do not have the source code for all these libraries, which is why it's not just *POOF* it works every time a new android release comes out. My 2.6.35 kernel just means that any direct kernel dependence new android adds will be provided, but it does NOT solve these intermediary layers. There is, in fact, the possibility that a new android release won't be compatible with our libraries, and we'll be proper focked.
I am using Samsung Galaxy S android version 2.2, I want to update it to Ice Cream Sandwich 4.0 or which ever is available. I read the instructions but I did not understand anything from it. I am doing it for the first time so I want to know step by step details or if there is any video. I also want to know few things
1- Will android market work
2- Will the phone have lags or speed get slower in the video it did not but I want to know.
3- Will I get all feature of Ice Cream Sandwich
4- In future if company releases 4.0 for galaxy s can I roll back the changes and turn it back to the original version which was there and if yes then how??
I have never tried such thing so I want to be sure before I do it. It looks pretty good in the video.
Firstly, welcome to xda. There currently isnt a proper samsung version of ICS for the galaxy s. What there is are several custom roms people have made based on ics, which if you read through their posts you will see that most of them still have issues and/or bugs. If you check this out http://forum.xda-developers.com/showthread.php?t=1363593 these guys are getting closer every time to a full working version of ics for the galaxy s.
So, choices for you are wait until samsung release a full version of ics (which looks very doubtful) or flash the afore mentioned ics rom or flash a different rom that takes your fancy. Myself I am flicking between this http://forum.xda-developers.com/showthread.php?t=1344489 (my current rom) and saurom.
Once you decided what you wanna do, then let us all know and we will guide you in the right direction.
My advice is to stay on samsung based ROMs for now. ICS ports are still alpha, although some people are using them for everyday. On the other hand, most GB XXJV? and XWJW1 roms are running quite fast on the Galaxy S. Coming from 2.2 you will see a big difference going into 2.3.6.
My personal choice is SURFACE v8 (http://forum.xda-developers.com/showthread.php?t=1155776) with the IceCreamS theme (http://forum.xda-developers.com/showthread.php?t=1386990).
Good luck!
I would like to knw when the full working version of ICS is available so tht before I update I could assure myself being safe to update the phone. I am not waiting for Samsung update but I want a proper Rom which suits the phone
Samsung said it won't be releasing any official ICS on Galaxy S. So all ICS work is made by dev teams, using the ICS source code and ICS releases on similar hardware (Nexus S). Most (all?) ICS ROMs are based in teamhacksung ICS port. You can see them in the Development forum (OneCosmic, Surface v1, MyICS, ...)
Some devs will say that their roms are release-candidate, finished or even official, but be careful with this, the teamhacksung port is in alpha stage (build 11) (http://forum.xda-developers.com/showthread.php?t=1363593). Moreover, there is no public roadmap for an official version and the devs don't like to be asked on ETAs.
I suggest you to read that thread to see what is and is not working in each build. Also, you can get answers to most of your questions (except ETA) on the CM9 discussion thread in this forum (http://forum.xda-developers.com/showthread.php?t=1387937).
SO Is it safe now to update with current available roms or to wait till the final version releases without any bugs becoz I hv gone thru Q&A dept and der are lots of complains sleep problem headset recognition problem and many more
skhan33 said:
SO Is it safe now to update with current available roms or to wait till the final version releases without any bugs becoz I hv gone thru Q&A dept and der are lots of complains sleep problem headset recognition problem and many more
Click to expand...
Click to collapse
Given that you have no experience flashing custom ROMs, I would also have to suggest avoiding the alpha ICS builds right now. Things will probably go wrong, whether majorly or minorly, that you aren't accustomed to dealing with.
Wait until a stable version is available, or at the very least a beta. However, in the mean time, I would definitely recommend flashing to 2.3.6. As someone else already mentioned, it will be a nice upgrade over 2.2, and it's an easy way to learn the basics of flashing ROMs.
Good luck!
First get to Gingerbread and then go for ICS if you really want to.
Over the past couple of weeks I was inspired by all the work being done to port ICS over to the Galaxy Tab. My question is- where is the "original" source code coming from for the kernel?
What I am looking for is something equivalent to the GB kernel source code available on the Samsung open source site (opensource.samsung.com). Since there is more "stuff" available regarding the GB kernel on the Galaxy Tab, I got over the learning curve of how to build the whole thing from scratch using the kernel source from the Samsung web site, and the "system" source from source.android.com (branch 2.3.4_r1). I won't say my first build did a whole lot, but it did boot to a working Android desktop.
I know Samsung has not placed a kernel for ICS up there yet for the Galaxy Tab "classic"... but you can pull a Samsung kernel from source.android.com. I compiled and flashed that kernel.. and turned my tab into a soft brick. When I compared the CM9 source that is being used for the ICS port to the tab (Meld Diff Viewer is my best friend), it was VERY different from the kernel source I pulled from source.android.com.
My guess is the ports are based on a HC kernel from the Nexus S. Unfortunately, I can't post this question in the DEV forum to ask directly... I suppose that's my punishment for lurking without posting. ;-)
Appreciate any help on getting this answered.
Hi everyone!
I'm looking to become a future dev of the Samsung Captivate Glide, but as we're awaiting the official ICS from AT&T the forum right now is pretty dead. We have a project going but nobody to guide us, and we wish to compile CM9 or AOSP ICS. Would anyone take me in and teach me the basics of ROMing? I would greatly appreciate it! I have a Mac and Windows, I'm not sure if Linux is required :|
~Aquethys
the rom is the least of the worries to get dev going on your phone, getting the kernel going is the hard part. does your phone have the source code released?
I don't believe so, people in our ics port thread are saying we don't have a working ics kernel. We do have a gingerbread kernel though... :/
How would I start?
Sent from my SAMSUNG-SGH-I927R using xda premium
well you take parts from the GB kernel and apply it to parts from the AOSP kernel, and troubleshoot until it boots. then you troubleshoot all the other issues, there will be issues, then you can start doing fancy things like add cwm. then tweak the kernel....
start reading on kernels, ramdisk, rils, libs, and drivers, linux, compiling, AOSP, github repositories.
you might be ready to take on this task in 6 months.... minimum
dont take that as snooty, ive been on here over a year, and know jack squat about half the things i just told you to study. though i have no desire to build kernels myself. there is lots of great info scattered all over xda. but you will need an experienced dev, to port ICS. you need to know basic kernel modification stuff before trying to do something as big as porting a new android version from out your but.
automated compiling isnt as automated as it sounds.
Alright. What programs will I need to begin with? Hopefully an experienced dev can guide me, I'm not too good @ following guides/tutorials but I'll try my best!
Sent from my SAMSUNG-SGH-I927R using xda premium
EDIT: Made a dropbox account, hopefully you could guide me through the basics?
So, is this the source code for SGH-I927 you were talking about? I downloaded it, what do I do with it? Is it different for ICS and GB?