Related
I've been following the development of so-called ROMs for the Vibrant (and other SGS devices), but I have yet to see a single AOSP ROM. Even when Samsung released the original kernel sources for 2.1, there were no AOSP 2.1 ROMs. Why not? Is it because they don't know which BLOBs to pull for insertion or the proper vendor overlays?
Some developers have done great work with SGS kernels (especially supercurio and his Voodoo kernels ... eugene373's tend to always wipe the internal SD card unnecessarily ...). But, a kernel does not a ROM make ... therefore I ask, what is truly missing to build an AOSP ROM. I've gone through the sources, but I don't follow makefiles too well.
I know we have another month or so before Samsung is obligated to release their 2.2 kernel sources, but that should have no impact on 2.1 AOSP ROMs. Therefore, I ask "what is the hold up?" What is missing, and what might I contribute ...
Need 2.2 source code...
2.1 is a dead horse--why bother when 2.2/2.3 are out?
The reason to bother is to at least get AOSP running. Once its on 2.1, it'll be easier to get 2.2 AOSP running on it. But claiming 2.1 is a "dead horse" is the wrong path ... the real question still stands: after 9 months on the market their still are no AOSP ROMs.
MIUI
Now that vibrant 2.2 source is released ... we finally have a REAL AOSP port and my all time favorite from my old HD2 the MIUI.... so keep your heads up and wait for it to get finished.
Get a custom rom. There are so many good devs doing them don't waste your time on AOSP....... until they release the actual source code...... on April 22
sarim.ali said:
Now that vibrant 2.2 source is released ... we finally have a REAL AOSP port and my all time favorite from my old HD2 the MIUI.... so keep your heads up and wait for it to get finished.
Click to expand...
Click to collapse
Except, the 2.2 source for the Vibrant has not been released. The SGH-T959D that shows Froyo sources on Samsung's site is for the Canadian Fascinate, not the US T-Mobile Vibrant. Samsung has yet to release the 2.2 sources.
oka1 said:
Get a custom rom. There are so many good devs doing them don't waste your time on AOSP....... until they release the actual source code...... on April 22
Click to expand...
Click to collapse
Except the so-called "custom ROMs" are just modifications on the stock theme, a replacement kernel and a change of some of the supplied applications.
There is nothing close to a full "custom ROM" such as CyanogenMod or MIUI because we don't have Samsung's sources. What is passing for a "custom ROM" for the Vibrant are just repackaged files. It is akin to the "ROM cooking" that took place for the WinMo phones, not a truly ground-up build from source that is possible with Android.
EDT/Devs4Android has the MIUI build. From Source.
TW has a 2.2.1 in testing.
EDT has a 2.2.1 Beta released.
TW has a 2.3 AOSP in testing. From Source.
EDT has 2.2 AOSP in testing. From Source.
What you want is out there for you.
Watch the forums and reply when a call for Alpha testers is posted.
Hopefully it won't be long before you see a full TW/EDT/Devs4Android collaboration!
I think what the original poster is trying to ask (and I have the same question) is why were there never any real 2.1 AOSP, cyanogen5 for the vibrant. The source for 2.1 has been around for many months. Were some other proprietary bits missing, was the released source code such a mess that it was unbuildable, something else? With those questions in mind, why will things be any different when the 2.2 source comes out?
mattb3 said:
I think what the original poster is trying to ask (and I have the same question) is why were there never any real 2.1 AOSP, cyanogen5 for the vibrant. The source for 2.1 has been around for many months. Were some other proprietary bits missing, was the released source code such a mess that it was unbuildable, something else? With those questions in mind, why will things be any different when the 2.2 source comes out?
Click to expand...
Click to collapse
Yes, this is more towards what I was getting at. We do not have Samsung's kernel sources for 2.2. And, we do not have a Samsung provided vendor overlay.
When we receive these two pieces, then a true AOSP build will be possible. However, we do have the 2.1 kernel sources, so why wasn't a true AOSP build possible then? What was missing, and can we actually expect Samsung to release the overlay that's needed?
Actually, that's true. I know it was old but why didn't anyone build a 2.1 cyanogen or aosp rom? (Not to say its easy.)
Sent from my SGH-T959 using XDA App
A noob question, kindly can someone explain what is the vendor overlay stuff?
Many thanks!
Where have you been?
rpcameron said:
I've been following the development of so-called ROMs for the Vibrant (and other SGS devices), but I have yet to see a single AOSP ROM. Even when Samsung released the original kernel sources for 2.1, there were no AOSP 2.1 ROMs. Why not? Is it because they don't know which BLOBs to pull for insertion or the proper vendor overlays?
Some developers have done great work with SGS kernels (especially supercurio and his Voodoo kernels ... eugene373's tend to always wipe the internal SD card unnecessarily ...). But, a kernel does not a ROM make ... therefore I ask, what is truly missing to build an AOSP ROM. I've gone through the sources, but I don't follow makefiles too well.
I know we have another month or so before Samsung is obligated to release their 2.2 kernel sources, but that should have no impact on 2.1 AOSP ROMs. Therefore, I ask "what is the hold up?" What is missing, and what might I contribute ...
Click to expand...
Click to collapse
Dude theres been a true AOSP ROM for the Vibrant since like december and thats CM 6.1
Im running it now
rpcameron said:
I've been following the development of so-called ROMs for the Vibrant (and other SGS devices), but I have yet to see a single AOSP ROM. Even when Samsung released the original kernel sources for 2.1, there were no AOSP 2.1 ROMs. Why not? Is it because they don't know which BLOBs to pull for insertion or the proper vendor overlays?
Some developers have done great work with SGS kernels (especially supercurio and his Voodoo kernels ... eugene373's tend to always wipe the internal SD card unnecessarily ...). But, a kernel does not a ROM make ... therefore I ask, what is truly missing to build an AOSP ROM. I've gone through the sources, but I don't follow makefiles too well.
I know we have another month or so before Samsung is obligated to release their 2.2 kernel sources, but that should have no impact on 2.1 AOSP ROMs. Therefore, I ask "what is the hold up?" What is missing, and what might I contribute ...
Click to expand...
Click to collapse
For probably the same reason that many phones with non AOSP firmware running 1.5/1.6 did not bother with AOSP 1.5/1.6 when they were released around the time 2.1 source hit. Why bother developing at all for what is essentially an "out of date" OS.
The only people it seems who actively continue to develop for existing (as opposed to new) firmware are manufacturers and carriers. This stupidity should be left to the manufacturers who still do this.
One of the larger snags way back then (sits in his rocking chair on the porch) was a lack of understanding of the phones proprietary aspects and how to work around them. But we have a fairly clear understanding of Samsung's boot process now, and RFS can now easily be turned into a distant memory.
I would wager a guess that the apathy towards 2.1 will not repeat itself once we have 2.2 source widely available and the low level similarities between 2.2 and 2.3 should have Gingerbread being more than the experiment it currently is. It's been barely more than a week since Eugene's little present manifested and there are already proper and stable kernels available.
Keep in mind that the devs we do have, have done a phenomenal job of cleaning up, speeding up, and drastically enhancing our existing 2.2 release. And perhaps to the point where many will not really care, though I know many would still like to see CyanogenMod6/7 properly on this phone.
Master&Slave™ said:
Dude theres been a true AOSP ROM for the Vibrant since like december and thats CM 6.1
Im running it now
Click to expand...
Click to collapse
Um, that's not quite true. The CyanogenMod.com website lists 0 files available for download for either experimental or stable files. The CM6.1 you must be running is not a true CM build.
Also, CM is not AOSP, but rather AOSP with modifications.
phrozenflame said:
A noob question, kindly can someone explain what is the vendor overlay stuff?
Many thanks!
Click to expand...
Click to collapse
The vendor overlay tells the AOSP build system which proprietary files are needed from the device that are not available in source form. This includes things like GPS and video drivers, baseband firmware for wireless radios, &c.
hi everybody !
a month age i decided to compile a new rom for my Galaxy S absolutely from AOSP source ( branch 2.2.1_r1 ) after some compile-time problem and many painful steps to resolve ,eventually the rom successfully built and can boot it up flawlessly on emulator.
i create a nandroid backup of current rom and installed the compiled one. but i am facing new problem :
1- the phone successfully boots but after short while screen began
flicking several time and the phone go in deep sleep and never wakeup
( power button or menu button does not do any thing )
2- touch screen works only for some second that I can unlock the
phone
3- there is no network available
4- I have downloaded samsung opesource package for GT-I9000. it
contains a folder named 'platform' but when i merge these files to
AOSP , the compile process stops and fails again. if there any one can
help me which files from samsung source should i merge and how ? if
you now the answer and dont have spare time then some internet link or
online document is really useful .i have no problem studding and
reading and searching . reaching to target is my only hope .
I am really disappointed why there is not a good and complete step2step tutorial to compile an AOSP rom for galaxy s (GT-I9000) !!
such docs is available for phones like dell streak , desire , dream , magic , .... . i really want to to active these aspect on XDA forum and with help of all you ( mods and masters ) try to create such tutorial that any one in world can use to refer . i think XDA is the only reference on net to collect and create such help and document. please help me and leave PM or comment to agree ot disagree and from where can i start ?!! thank in advanced .
edit :
there is a google groups post that i send my question in Android-platform . if you prefer please join this group and active that post to ask any question related to 'galaxy s compile from source ' .
post located at http://groups.google.com/group/android-platform/browse_thread/thread/da5d6f18f3bd3c9b
OK, so here's the thing... I'm kind of new in the Android acknowledgement, so I hope that here will be the place where I will get my answers. So here's what I know...
At first I didn't know that Android was Java-based, using a modified Linux kernel which we all know it's C-based (entirely). After a while, I found that there were different firmwares (ROMs) from the original ones, called Stock ones and also different kernels. After reading lots of info about how things actually are, I've decided to root my stock and then I moved to a custom MIUI for my SGSII with a JB implementation. At first it was great, but I had some issues which left me disappointed. Then I moved on to the official MIUI (China - English one). Things got better after I got used to it. The major bugs disappeared, only small ones left and a few crashes, but in time most of them got fixed. Later it crossed my mind, "Why are there so many different kernels and which is the best one for my phone or ROM to be precise?" Well this is where I need your help. I've read some topics that siyah kernel is probably the best kernel, which fits the MIUI rom. The pointing of concrete kernels isn't the kind of answer I was actually searching for. To be honest, I need answers to questions like:
How many kernels are there ?
Which ones are safe ? (I've read that there are badly written ones, so yeah, it needs to be asked)
Statistically, which is the best kernel and is it for the MIUI rom ?
How can I tell that it's suitable for the MIUI rom ? (Since I've read that not all are)
What are the risks of changing the kernel?
How can you test the kernel's behaviour, an app which makes statistics in time or some other methods ?
Believe me, as annoying this topic might seem, lots of us (the newbie users) are burning up the google servers, just to find these answers. I'm really hoping for a reply spam with answers (if possible , spare the trolling ones). Thanks for reading my annoying topic, anyway
Since most of the source is available, basically anyone can build their own kernel at home, so it is hard to tell how many kernels are there.
what isn`t available as open source are most of the OEM-specific drivers. Samsung, for one, doesn`t make most of the drivers' source publicly available, so kernel developers have to make a binary kernel around the binary drivers and literally pray their work well together.
Siyah is safe, but I prefer the stock kernel (I like the stock ROM... go figure). The stock kernel is the only one that is sure to work properly with all the hardware in the phone, because it is the only built from sources for the drivers as well (read my previous paragraph).
Which ones are safe (other than stock and Siyah): you gotta try them for yourself, read other users' remarks and feedbacks, and so on.
Risks:
Very low. As long as the bootloader is good, if the kernel totally malfunctions, just reboot in download mode and flash something else.
Some app may work very well in one kernel and bomb in another. It may crash in some kernels. It is very empyrical.
The problem is that custom kernels don't undergo the same type of quality testing as stock kernels. Developers have very limited resources to do that, and some developers are more interested in having a short time-to-market than a quality product (well, many large corporations act like that as well). At the end of the day we - power users - are the beta testing and quality assurance teams for the kernel developers.
Hello
Here is a little question, is it possible to create a universal android rom.
Today, cyanogenmod allow us to have different flavour of android for many devices. But cyanogenmod is not universal and requires specific hacks for each device.
I know that Android is based on a linux kernel, that kernel should beallow an automatic detection of the devices specifications....
Moreover, Motorola initiates its Ara project. This new concept should be linked to an evolutive version of Android.
Is there anyway to see one day an android repository to upgrade and costumize your phone/phablet/tablet. With an essential package (OS) and options (launcher/Touchwiz....).
An universal evolutive OS should be a way to solve
- android fragmentation.
- security update
- Easy update without formatting your device
- OTA update for all devices (Samsung, Cube, HTC....) even for olders or chinese models
bart47 said:
Hello
Here is a little question, is it possible to create a universal android rom.
Today, cyanogenmod allow us to have different flavour of android for many devices. But cyanogenmod is not universal and requires specific hacks for each device.
I know that Android is based on a linux kernel, that kernel should beallow an automatic detection of the devices specifications....
Moreover, Motorola initiates its Ara project. This new concept should be linked to an evolutive version of Android.
Is there anyway to see one day an android repository to upgrade and costumize your phone/phablet/tablet. With an essential package (OS) and options (launcher/Touchwiz....).
An universal evolutive OS should be a way to solve
- android fragmentation.
- security update
- Easy update without formatting your device
- OTA update for all devices (Samsung, Cube, HTC....) even for olders or chinese models
Click to expand...
Click to collapse
I'm not going to be the one to say its impossible but its very unlikely. Different devices use different modems, kernels, and other system requirements. The CM team may be able to come up with something like that but you won't see it anytime soon if it happens. There are some ROMs out there that are in 1 big AROMA zip file and they all have the same features but the bases meet the requirements of the specific device.
bart47 said:
Hello
Here is a little question, is it possible to create a universal android rom.
Today, cyanogenmod allow us to have different flavour of android for many devices. But cyanogenmod is not universal and requires specific hacks for each device.
I know that Android is based on a linux kernel, that kernel should beallow an automatic detection of the devices specifications....
Moreover, Motorola initiates its Ara project. This new concept should be linked to an evolutive version of Android.
Is there anyway to see one day an android repository to upgrade and costumize your phone/phablet/tablet. With an essential package (OS) and options (launcher/Touchwiz....).
An universal evolutive OS should be a way to solve
- android fragmentation.
- security update
- Easy update without formatting your device
- OTA update for all devices (Samsung, Cube, HTC....) even for olders or chinese models
Click to expand...
Click to collapse
I doubt it's possibility. Different phones have different kernels/coding for hardware. All Android phones uses Linux kernel, but are coded differently, and that's why we have different/custom kernels. Phones/phablets/tablets have different UIs, which will result in larger updates. Furthermore, u said "essential package" which is hardly possible due to large file size and company issues. For example, Samsung has TouchWiz (and all it's bloatware ), while HTC has Sense (and the bloatwares ), and to stuff everything in a single ROM /Update, it's simply too much. (A update from Samsung would cost 100-300mb, and if what u say is true, OTA updates would cost 600mb~. (Take into account the stock Android launcher.)) I doubt Samsung would like this idea too. Companies like Samsung and HTC have their own launchers to differentiate themselves from others, and if consumers have a choice, they might use other launchers other than their own. (E.g. a Samsung user wants to use Sense, while preserving the Samsung hardware.) Though I would very much like to see this in the future, this is technically impossible. Hoped this explained your question.
Smack that thanks button If I helped!
Always make a nandroid backup before trying anything risky
Sent from my fabulous N7105 powered by Illusion ROM and Plasma Kernel.
Sent from dat small country called Singapore.
P.S. Quote my post for replies ASAP.
This is literally impossible, All devices would need to be designed to perform for that rom. Not only that but not a single one of those companies would agree to it. They'd actually attempt to make their own os before doing that, and the reasoning is simple, each company is in this race for themselves not as a team effort. For this to happen would be going the route of IOS, which android is not.
Sent from an Xposed LG-G2/LS-980
Hello XDA-Developers.
Some of my friends in the phone/wireless communications business (including a PhD) tell me that custom ROMs are unsafe and there could be written in the code spyware such as keyloggers that can steal your data and do other things of the sort in the background. Cyanogenmod (and AOKP maybe) seem to be pretty safe, and I am running it on my i897, but the Legend is not supported anymore and the latest official ROM I can get is Gingerbread on CM7, which is very slow and seems to have issues. However, I have found these UNOFFICIAL Cyanogenmod/AOKP ROMS made by others:
http://forum.xda-developers.com/showthread.php?t=2353659
http://forum.xda-developers.com/showthread.php?t=2222597
http://forum.xda-developers.com/showthread.php?t=1905588
http://forum.xda-developers.com/showthread.php?t=1562595
2.2 ROM
http://forum.xda-developers.com/showthread.php?t=866849
Note: Don't know if this matters, but all the ROMs save the last were not made by Recognised Developers.
These ROMs (I haven't tried some of them yet) run very smoothly on the Legend and are almost as good as a daily driver.
So can I trust these ROMs because they are based on CM/AOKP but are unofficial, or is the security compromised as it was unofficially done by a member? I would like answers from a technical point of view, not speculation such as 'devs usually have no intent', etc. Don't get me wrong, I may be paranoid, but I truly appreciate the amazing work that devs here are doing, but the possibility of security issues, especially with Linux and open source, is of my concern.
Hello all!
First time Android "developer" Cory here. I've been rooting phones and flashing all kinds of things for years now, but this is the first time I actually want to try to develop something.
First a quick introduction about my community and device. The Nubia Red Magic 3 has been pushed by all sorts of online personalities and tech companies, even XDA. It's a Chinese gaming phone with tons of power, and the first ever mechanical cooling system. However ...it's global release has been staggered by very, very poor firmware. It runs on Android 9 and lacks many features that leave global (English) customers feeling ripped off in some way.
I want to develop a stable, stock-based ROM for my community by learning how to take the good bits of the Chinese version of our devices ROM, and merge it with the "Gapps" compatible variant that we all know (and hate).
I've done lots of research online, and so far have only found a tool that lets me extract system.new.dat.br so I can change things like sounds and graphics. I don't know how to repack it.
There are lots of Google results for things that seem helpful, but turn out to be very outdated, sometimes by as much as 7 years. Also many links to tools are either dead or outdated (even here on XDA).
We (the Red Magic community) are desperate for a stable ROM that we can use daily, and I want to deliver that. I have ideas of where I want to start, but I can't find out how.
Thanks in advance for any and all guidance!
-------
Current checklist of To Do's:
Change system sounds (done)
Create stable, Interactive based kernel
Fix Chinese system translations
Debloat proprietary Chinese apps for global users
Implement stable launcher/replace permanent Chinese launcher
Integrate system Gapps into ROM
More to come.
Reserved