Related
printf("Hello XDA!");
I haven't posted much, but I've spent a lot of time on these forums and flashed a few custom roms on my captivate as well. I'm a final-year computer science student and now I want to jump into the android source code.
I have some operating systems experience, I took the OS class at my university and ended up with a C (more due to external factors than the difficulty of the course).
Does anyone have any tips on where to start or how to make sense of the very large source distribution? I installed ubuntu, set up my repo, and downloaded the AOSP FroYo and Gingerbread sources. I think that, for my first project, as a way to learn about what goes into making a ROM, I want to post the AOSP FroYo source to the captivate and just have a pure AOSP build running on my phone. Can anyone point me to some resources or information to help me get started?
Thanks a lot!
how to create ROMs - http://forum.xda-developers.com/showthread.php?t=928955
and I think someone is already working on AOSP froyo - http://forum.xda-developers.com/showthread.php?t=951653
Actually I meant more like resources about how the android source is laid out, which source files to edit to make a custom rom, which source files control which parts of the phone, etc. I've already seen the guide you linked to putting together a custom ROM.
And even if someone is working on AOSP Froyo, I want to do this to learn about how the Android OS works so that I can go on to developing better ROMs
Hey guys, I have been looking for a jb miui ROM for this device and i cant find one, i know there are some ics miui ROMs, but i would really like a jb miui ROM.
There is one for the vibrant, can I use it for my Galaxy s 4G or can anyone port it to our device?
Vibrant MIUI JB ROM:
http://forum.xda-developers.com/showthread.php?t=2289234
Thanks
i'll build it when miui comes out with miui 4.2
airfluip1 said:
i'll build it when miui comes out with miui 4.2
Click to expand...
Click to collapse
Thank you i will be looking forward to it.
Beast said he would do it.
sent from me
that's been in my queue for a while along with aokp aries and paranoid android.
airfluip1 said:
i'll build it when miui comes out with miui 4.2
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2313073
Just because there are some homebrew ports doesn't mean that MIUI is 4.2 yet.
http://en.miui.com/download.html
Official Downloads
Author : MIUI Developer Team
Kernel : Android 4.1
Latest update : 3.6.21
Download : http://www.miui.com/download.html
Language : Chinese and English
Click to expand...
Click to collapse
Why does it matter ? We use unofficial ROMs anyway...
sent from me
That's like saying that since a car, airplane, and weed-whacker all run on gas, you should just put the same stuff in each. Actually, the unofficial ROMS is a more tenuous connection than my gas connection. It's more like saying that since a bullet train, horse, and diesel bus all run on fuel, the fuel which goes into each shouldn't matter. It's all fuel.
Hey, you could (please don't) use an unofficial Vibrant ROM too. That's unofficial. What's the difference? The difference is that it won't work. And might brick your phone. That's bad.
Our only current Aries kernel is 4.2.2 and still has issues. MIUI is still 4.1.2 and would introduce an entirely new set of issues tied into GPS, Bluetooth, and so forth if/when a 4.1.2 Aries kernel was compiled. Does that make it impossible? No. But it means that as the build impetus - when MIUI is 4.2 - has not happened yet... it's not a great use of time yet. Unless one of the devs wants it. In which case, MIUI being not-updated is something they don't need to be hammered over the head with.
http://forum.xda-developers.com/showthread.php?t=2313073
4.2.2?
Port. If YOU see source linked from that page so our devs could actually do something useful to build that...
Hi Theraze
I have to disagree with you.
Port is not a dirty word and most of our ROMs are actually ports and not built from source. Furthermore, MIUI ROM is usually ported and not built from source and only recently did Xiaomi open their sources for the public. Even more than that, both MIUI versions brought to us by Beast were ports from Nexus and not built from source.
Now, regarding the incompatibility between kernel & OS - if it works on Nexus, I assume the adjustments were made, so one can enjoy both 4.2.2 & MIUI benefits. There is no logical reason why it couldn't be ported to our beloved device.
sent from me
I'm not saying it can't be done. I'm saying that our build-from-source dev who asked you to let him know when it hit 4.2 hasn't had his request met.
Does that mean that someone (him or another dev) CAN'T port it? Nope. But it makes it a lot less likely that air can just pull the source in and compile it using the Aries bits if the buildable MIUI is still only 4.1.2 and our Aries is 4.2.2 instead.
Again, I think we're agreeing on the general bits... yes, this is possible. But airfluip1 asked to be notified when buildable MIUI was 4.2.2 and that's when he said he'd build it. Not port it.
I don't care if a ROM is ported or built from source.
I will try to play with porting it myself.
Hello xda members.
I've got a question regarding kernels. How is one to know which kernel will work with there particular ROM? Are they all somewhat compatible just to a matter of degree? Or do people just find one that sounds good and hope it works on there particular ROM?
I'm running aosb end of the line ROM and I'm real curious to try out kernels now.
Any insight world be greatly appreciated.
Thanks
There are pretty much 2 types of kernels.
CAF kernels - Used for CyanogenMod based ROMS
NON-CAF kernels - Used for AOSP / Stock
Find out if your ROM is CM based. If it is, Look in each kernel thread to see if it mentions CAF.
Hi,
This rom is based on CM so you need a kernel compatible with CM roms like (or tagged with "CAF"): http://forum.xda-developers.com/showthread.php?t=2551441 or http://forum.xda-developers.com/showthread.php?t=2661397...
Maybe there is one or two others, don't remember exactly.
ericv99 said:
I'm running aosb end of the line ROM and I'm real curious to try out kernels now.
Click to expand...
Click to collapse
Since you are running aosb which is CM based Rom you can try the above 2 given and also the elemental X for CAF based Roms
thank you guys. now to go check em out...
I know LiquidSmooth is based on Slim, which I believe is based on AOSP source. Either Slim is ported to our phone and Liquid is built on top of it, or Liquid, based on Slim, is ported to our phone (or they're both the same thing). Well, what stops someone who can take Slim and make it into LiquidSmooth, from basing it off of GPE instead?
Come to think of it, I've only seen ROMs based on GPE offer a couple tweaks. Nothing as extensive as something like LiquidSmooth. Can a GPE not be modified as extensively? Isn't it required to have its source posted due to the GPL or something?
dragontology said:
I know LiquidSmooth is based on Slim, which I believe is based on AOSP source. Either Slim is ported to our phone and Liquid is built on top of it, or Liquid, based on Slim, is ported to our phone (or they're both the same thing). Well, what stops someone who can take Slim and make it into LiquidSmooth, from basing it off of GPE instead?
Come to think of it, I've only seen ROMs based on GPE offer a couple tweaks. Nothing as extensive as something like LiquidSmooth. Can a GPE not be modified as extensively? Isn't it required to have its source posted due to the GPL or something?
Click to expand...
Click to collapse
GPE isn't aosp, it's Google play edition software. It isn't open sourced to be built off of. Think of it as more of a Sense or touchwiz interface than AOSP build. A GPE rom is built specific for each device it's operating on.
A GPE rom written for an HTC m8 will not work on a samsung galaxy s5, simply because the kernels are different. AOSP roms have the same kernel for all devices. That's mainly what would keep a developer from basing a rom off of a GPE code.
Slim is built AOSP source code, along with many other roms. Liquid chooses to use slimroms as a base, but it could choose to use CM, AOKP, or another AOSP base of their choosing. This doesn't apply to GPE.
GPE roms can be modified to do whatever the developer wants them to do. However, the whole point of GPE roms is to have a very fast, debloated close to stock experience. People looking for GPE roms aren't really looking for all the bells and whistles that go with highly modified stock or aosp roms.
Whoa... There is no such thing as a ROM that will run on both an HTC One M8 and a Samsung Galaxy S5. That isn't a valid limitation of GPE. Kernels are always device specific, too. You might get a universal kernel that works across variants of one phone, but I've never heard of a kernel, an aftermarket one anyway, that will run on devices across manufacturer lines. Then again, I don't follow kernels as closely as I have ROMs.
GPE isn't open source? That's news to me. I mean, I thought all Android builds had to provide source. I mean, rule #1 of XDA is don't ask for ETAs, but I saw a moderator demand source on a ROM "sooner than later." Not naming names because I'm sure the moderator was within rights, but it seemed to at least partially contradict the spirit of the famous rule.
dragontology said:
Whoa... There is no such thing as a ROM that will run on both an HTC One M8 and a Samsung Galaxy S5. That isn't a valid limitation of GPE. Kernels are always device specific, too. You might get a universal kernel that works across variants of one phone, but I've never heard of a kernel, an aftermarket one anyway, that will run on devices across manufacturer lines. Then again, I don't follow kernels as closely as I have ROMs.
GPE isn't open source? That's news to me. I mean, I thought all Android builds had to provide source. I mean, rule #1 of XDA is don't ask for ETAs, but I saw a moderator demand source on a ROM "sooner than later." Not naming names because I'm sure the moderator was within rights, but it seemed to at least partially contradict the spirit of the famous rule.
Click to expand...
Click to collapse
Ehh, GPE may be open sourced. I think Google has to release the information for it.
AOSP though definitely isn't as specific, the kernel has to be signed for each device but it's overall much easier to port the kernel over to another device.
kernels
The Linux kernel is a monolithic kernel and all device specific drivers are compiled in the binary unless they are stand alone modules. Android itself is open source, but it does NOT use the GPL v2 licence. The code for many of the drivers and other device-specific software is closed source and only available as binaries. XDA strictly enforces providing source code for kernels because that is a strict stipulation of GPL v2. A custom ROM generally doesn't require source code since many stock-derived ROMs don't begin with source code. Sense and GPE would be varieties that don't originate from source code.
Hey guys,
Just a quick question that I'm hoping someone can clear up for me. I have been flashing phones since the Vibrant and I seem to recall back then (and other phones I've had after such as the Sensation) devs would use the source of the firmware released from the manufacturer to create more stable roms and until that source was released there would be the possibility of the bugs.
I am coming from a Nexus 5 which I just used the stock rom since I wanted the OTA updates so it's been a while since I've flashed custom roms.
My question is, is the OPO the same way in the sense that in order to have more stable roms the source has to be released by CM in order to be more stable or is this a whole different beast where that isn't a necessity?
Thanks.
CM11S/CM12S is derived from the CM11/CM12 nightlies, all current ROMs are based on those CM sources, so all current ROMs are up to date. If you're flashing CM12 nightlies there's nothing extra that you need to do because firmware and modem is built in, but if you're flashing another custom ROM you need to flash the appropriate firmware and modem before flashing the ROM.
Oxygen is the exception to the above information, in the sense that it isn't based on CM. Flashing Oxygen will automatically flash the appropriate firmware, but if you want to revert back you need to flash the correct firmware/modem first.
Transmitted via Bacon
timmaaa said:
CM11S/CM12S is derived from the CM11/CM12 nightlies, all current ROMs are based on those CM sources, so all current ROMs are up to date. If you're flashing CM12 nightlies there's nothing extra that you need to do because firmware and modem is built in, but if you're flashing another custom ROM you need to flash the appropriate firmware and modem before flashing the ROM.
Oxygen is the exception to the above information, in the sense that it isn't based on CM. Flashing Oxygen will automatically flash the appropriate firmware, but if you want to revert back you need to flash the correct firmware/modem first.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks, I did not know that but it does clear some other things up.
One other question, when a Samsung (for example Galaxy S5) rom is leaked, developers will use the latest leak to update their roms but typically a rom won't be "stable" until it is based on the source that is released.
Is the OPO like that as well where the custom roms need to have a source released in order to do that (is this the google android source or CM source?), I guess I'm trying to find out the stability of the roms versus a stock rom and whether there will be more bugs in one or the other.
sahil04 said:
Thanks, I did not know that but it does clear some other things up.
One other question, when a Samsung (for example Galaxy S5) rom is leaked, developers will use the latest leak to update their roms but typically a rom won't be "stable" until it is based on the source that is released.
Is the OPO like that as well where the custom roms need to have a source released in order to do that (is this the google android source or CM source?), I guess I'm trying to find out the stability of the roms versus a stock rom and whether there will be more bugs in one or the other.
Click to expand...
Click to collapse
That's what I answered in my last reply. The CM nightlies are the source, all ROMs are built based on those nightlies (except for a couple). This phone is nothing like a Samsung or an HTC where the stock ROMs are different from the aosp ROMs or CM based ROMs. The stock ROM for this phone is the CM ROM. The stock source is always released, every single day.
Transmitted via Bacon
timmaaa said:
That's what I answered in my last reply. The CM nightlies are the source, all ROMs are built based on those nightlies (except for a couple). This phone is nothing like a Samsung or an HTC where the stock ROMs are different from the aosp ROMs or CM based ROMs. The stock ROM for this phone is the CM ROM. The stock source is always released, every single day.
Transmitted via Bacon
Click to expand...
Click to collapse
Got it! Thank you!!
timmaaa said:
That's what I answered in my last reply. The CM nightlies are the source, all ROMs are built based on those nightlies (except for a couple). This phone is nothing like a Samsung or an HTC where the stock ROMs are different from the aosp ROMs or CM based ROMs. The stock ROM for this phone is the CM ROM. The stock source is always released, every single day.
Transmitted via Bacon
Click to expand...
Click to collapse
Not exactly true. CM is AOSP BASED, but modified - sometimes quite a bit. In the case of CM12S - this is a ROM specific to the OnePlus One. It isn't the same as CM12. It is only for this specific phone, and has some features in it that are specific to this phone.
I'm not sure why anyone would want to install Oxygen OS, unless they have just been brainwashed by OP that CM is now bad. Well that and the fact that CM still hasn't released 12S, nor am I convinced that they ever will. They seem to be pretty terrible when it comes to keeping up with the commercial side of things... Very amateurish.
mhannigan said:
Not exactly true. CM is AOSP BASED, but modified - sometimes quite a bit. In the case of CM12S - this is a ROM specific to the OnePlus One. It isn't the same as CM12. It is only for this specific phone, and has some features in it that are specific to this phone.
Click to expand...
Click to collapse
I know that CM is essentially aosp, and CM11S/CM12S is 99% CM11/CM12, with just a couple of fancy apps thrown in on top to make it seem a bit different. It really is just like a milestone release of the main CM branch, a stable release.
Not Exactly.
Heisenberg said:
I know that CM is essentially aosp, and CM11S/CM12S is 99% CM11/CM12, with just a couple of fancy apps thrown in on top to make it seem a bit different. It really is just like a milestone release of the main CM branch, a stable release.
Click to expand...
Click to collapse
Not really. There are no apps of which I am aware that that put in the "S" release. But there are features specific to the needs of that device and to that user community that add value.
mhannigan said:
Not really. There are no apps of which I am aware that that put in the "S" release. But there are features specific to the needs of that device and to that user community that add value.
Click to expand...
Click to collapse
CameraNext, the custom lockscreen. Both apps that are unique to Cyanogen OS. I'm sure there are more but I don't run that ROM so I can't check. You can believe it or not, but Cyanogen OS is just CM with a few extra apps/features. Your lack of belief in it doesn't stop it from being true.