Just want to ask something about porting roms... - Android Q&A, Help & Troubleshooting

Hello everyone.
Im new here.
I just want to ask something.
When porting roms can my base ROM and my port ROM have different android version?
Looking forward to having responses
P/s: sorry for bad engrisk )

XdaNeko said:
Hello everyone.
Im new here.
I just want to ask something.
When porting roms can my base ROM and my port ROM have different android version?
Looking forward to having responses
P/s: sorry for bad engrisk )
Click to expand...
Click to collapse
It has been a looong time since I knew about those things but if I remember your base ROM should have that same Android version as your port ROM.
And if you want an advice, please consider building a ROM from source. Troubleshooting is hell with ported ROMs. Building ROM is scary because it has commands that you don't know yet, but it's way more easy than porting. Trust me.
Here is a guide on how to build ROM from source :
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763

@XdaNeko
It's NOT the version of Android what does matter. If that would be the case then an upgrade via OTA never would be possible.
A Stock ROM always at 100% matches phone's hardware ( CPU, GPU, RAM, storage memory, etc.pp ) - it's built by OEM's / Carrier's R&D department, the guys who know best of.
Whereas a Custom ROM necessarily does NOT because it gets built by 3rd-party companies/programmers associations - who think they can do it better, but don't always have the specific Android device at hand.

Related

[Q] AOSP or true custom ROM

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

Little clearing about ROM names

Hi,
Can someone make clear to me as a noobie what are the differences between "cores" of the ROMs?
I see there are most favourite ones like "XWLP9" and "AOKP" - what are the differences between them? I see AOKP has more updates from kernel and maybe some other things in addons? Besides XWLP9 seems to me more stable but I only observe rom peoples comments and replys so can someone tell me which ROM core I should be focused on when choosing ROM? Some advices, experiences what you have with them - ADVANTAGES and DISADVANTAGES maybe or something ... I see there are roms like these two from what I want to choose:
http://forum.xda-developers.com/showthread.php?t=1436817
http://forum.xda-developers.com/showthread.php?t=1513150
Thank you for all your advices ...
Drahy said:
Hi,
Can someone make clear to me as a noobie what are the differences between "cores" of the ROMs?
I see there are most favourite ones like "XWLP9" and "AOKP" - what are the differences between them? I see AOKP has more updates from kernel and maybe some other things in addons? Besides XWLP9 seems to me more stable but I only observe rom peoples comments and replys so can someone tell me which ROM core I should be focused on when choosing ROM? Some advices, experiences what you have with them - ADVANTAGES and DISADVANTAGES maybe or something ... I see there are roms like these two from what I want to choose:
http://forum.xda-developers.com/showthread.php?t=1436817
http://forum.xda-developers.com/showthread.php?t=1513150
Thank you for all your advices ...
Click to expand...
Click to collapse
Google is your friend.
XWLP9 is the latest stock/official ROM version from Samsung for the SGS2 (GT-I9100).
So, these kind of ROMs are based on Samsung stock ROMs ... with some customizations (e.g. rooted, some removed bloatware, some custom themes/mods, etc.).
The other kind of custom ROMs have AOSP (Android open source project) or ASKP (Android open kang project).
So, they are either on pure Google Android OS or Linux. Usually there is a team of developers who share their parts/versions in binaries and as source code.
The kernel is kind of "core" of the firmware.
Every ROM contains its own kernel, as this is a basic part of the firmware ... and the phone can't work without it.
You can also flash other (custom) kernels on a ROM.
But not every kernel is compatible with every ROM.
OK thank you I read about these two a lot i needed some experienced opinion and clearing it up for me.
What I basically needed was opinions about these two versions from experienced users. If non oficial and trully open made ROM is better and in what ways or is it better to stay on oficial ones etc. This is what i wanted most from this thread ...

Building a ROM from scratch, guide?

Are there any guides that show the user how to create a rom from scratch? I've seen multiple guides on creating a rom but they do so using the kitchen. I would prefer something that shows how to make a rom without a crutch.
please help
HydrogenPeroxide said:
Are there any guides that show the user how to create a rom from scratch? I've seen multiple guides on creating a rom but they do so using the kitchen. I would prefer something that shows how to make a rom without a crutch.
Click to expand...
Click to collapse
I would say the best way to make a ROM from scratch is to compile it from source. If your interested in learning how to compile a ROM from source I would recommend taking a look at this guide to building Jelly Bean from source, as well as Google's offcial documentation on building Android from source. Additionally this guide on Zip Based ROM tweaking is a good guide to take a look at. Let me know if you still have any questions .
HydrogenPeroxide said:
Are there any guides that show the user how to create a rom from scratch? I've seen multiple guides on creating a rom but they do so using the kitchen. I would prefer something that shows how to make a rom without a crutch.
Click to expand...
Click to collapse
Normally all device forums have tutorials on how to compile ROM from source(if someone has already compiled it).
If no development has yet started for your phone then you you need to create the device tree which is tough. Otherwise just google . There are lots of tutorials lying on xda.
shimp208 said:
I would say the best way to make a ROM from scratch is to compile it from source. If your interested in learning how to compile a ROM from source I would recommend taking a look at this guide to building Jelly Bean from source, as well as Google's offcial documentation on building Android from source. Additionally this guide on Zip Based ROM tweaking is a good guide to take a look at. Let me know if you still have any questions .
Click to expand...
Click to collapse
Thanks, I didn't even know there was an official guide
I'm wanting an AOSP ROM on my s5 g901f but there is no support at all. Could someone point me in the right direction? I'd like to have a go and have looked up porting but I don't think that is the way to go. If somebody could give me the steps what I need to do for this modal I will research.
Could I use the cm for note 4 as it has similar specs, ie
805, 420 etc. Or s5 g900 as a base ROM? Or would I need to build from scratch?
There is only one custom ROM for g901f and that's touchwiz so somebody please help before I go insane. Touchwiz really is that bad
Up for this. Really interested especially for us who has not so good programming skills
mikey187lfc said:
I'm wanting an AOSP ROM on my s5 g901f but there is no support at all. Could someone point me in the right direction? I'd like to have a go and have looked up porting but I don't think that is the way to go. If somebody could give me the steps what I need to do for this modal I will research.
Could I use the cm for note 4 as it has similar specs, ie
805, 420 etc. Or s5 g900 as a base ROM? Or would I need to build from scratch?
There is only one custom ROM for g901f and that's touchwiz so somebody please help before I go insane. Touchwiz really is that bad
Click to expand...
Click to collapse
Let's see if I can point you in the right direction! Because of the differences in specs between your S5 Plus and the regular S5 you can't use that to port ROM's. For the Note 4 idea, since you only have a Touchwiz ROM as your base (The one from your S5 Plus) it won't work properly for the port ROM (CM12 Note 4). I would recommend looking at compiling CM12 for your device, which I would recommend taking a look at this guide here. Let me know if you have any questions be happy to help you out.

Android Lollipop 5.0 ROM on Low and Mid End Devices

I have an idea. My idea is a Custom ROM for Mid end and Low end devices based on Android Lollipop 5.0 but I cannot Port Roms. I Need You. I Need People who can Port Roms.
First I think that the Rom Must have very many stable Performance tweaks because the Rom should be Runs speedy like a SlimRom.
The kernel are a normal custom Kernel with dualboot options. I am still working on a Kernel what Runs with no lags, no bugs and it Runs very speedy and who can works on unlimited systems (dualboot,quadboot,...).
I have Not many ideas, please give me ideas who can idealized.
We can be a large and a good Team :highfive: .
Sorry for my Bad english.
Thanks from Germany
P.S Android Lollipop have Google Not bring it out but When it bring it out then We can porting the rom. We Need many ideas. Please share that on all people who can porting Roms or have many ideas
For kernel build you can ask airidosas252
he made one for kitkat an another for jellybean.
kalel29 said:
For kernel build you can ask airidosas252
he made one for kitkat an another for jellybean.
Click to expand...
Click to collapse
Thank you very much for this tip he Must only answer it
i Need people who can Port roms please share this project

How do I Build an Android rom for New Device?

I want to learn how to build a rom for an new device that no one has created a custom rom for. I am kinda new at this. But I want to learn how. I is there a full on guild or something on how to do it... I want to know. There are devices out there that have to custom roms yet that I would like to build for. I would like to use AOSP to build a clean fresh pure Android rom. Those devices I want to build for have the right specs to run a newer Android version but the developers did not realse an update for. I really would like to learn how to build/create my own Android rom from scratch... Learn how to build a kernel, bootloader, etc. to help the rom run right. Can anyone help?
http://forum.xda-developers.com/showthread.php?t=1272270
Thanks me if it helps you
@jakeh9777
Read this http://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
Especially post #4 and below
Thanks!
My only problem is where do I get a device tree and all the files for the device? I am wanting to build roms for devices that no one else build roms for yet. So it is going to be hard to customize roms for those devices without any roms in the first place. I know how to download source but I can't build it a rom from it. I just want to support devices that no one else has but the ones people want still... And some of them aa silde out qwerty keyboards. Can I get some more easier instite... I better at learning physically, so a video will be good too.
P.S. I can't get a device tree from CM if the device is not been added... That is why I said these devices don't have roms yet.

Categories

Resources