[Q] Porting Rom for Nexus S to T959 - General Questions and Answers

Basically, I'm trying to port this rom to the Samsung Vibrant. I am using the latest Cyanogen Mod nightly as the base rom and following the tutorials for porting roms to other devices. I just want to make sure that I have properly checked everything, since I'd rather not test the rom on my device without community help. I've checked to make sure that the resolutions are similar, etc. My question is, is there anything I'm missing or anything that I should fix?

Related

Building AOKP roms from ground up tutorial?

Hello everyone,
My device is a galaxy tab 7 plus and we currently have a fully functional CM9 build working perfectly. I've been following a few guides on how to port AOKP to this device and non of the guides worked. I also read that cm9 and AOKP are one of the same. So if u get one to work the other should easily. But it doesn't seem to be working. So I figured maybe porting won't work. Maybe I have to build it from ground up. So are there any tutorials on how to do so? Or is there a way I can bring the RomControl menu to the current cm9 build?
MacZzang said:
Hello everyone,
My device is a galaxy tab 7 plus and we currently have a fully functional CM9 build working perfectly. I've been following a few guides on how to port AOKP to this device and non of the guides worked. I also read that cm9 and AOKP are one of the same. So if u get one to work the other should easily. But it doesn't seem to be working. So I figured maybe porting won't work. Maybe I have to build it from ground up. So are there any tutorials on how to do so? Or is there a way I can bring the RomControl menu to the current cm9 build?
Click to expand...
Click to collapse
you should double check the device can run AOKP, it may not even be supported. And building from the ground up is probably a little excessive
Well the devs in the galaxy tab 7 plus section ported cm9 and its working fine but there are only two devs and they both said they have no interest in making AOKP work on our device. The device shares the same hardware as the galaxy s2. I've compiled a couple of builds and mad a logcat and they all pointed at the audio drivers and some other problem. So far I couldn't get passed the boot screen... so I thought maybe I should stop trying to port but start trying to build. I mean I've seen so many devices that have lower specs then this device running aokp so I don't think specs are an issue here..
Sent from my GT-P6200 using xda premium

[Q] Porting Rom for Nexus S to T959

Basically, I'm trying to port this rom to the Samsung Vibrant. I am using the latest Cyanogen Mod nightly as the base rom and following the tutorials for porting roms to other devices. I just want to make sure that I have properly checked everything, since I'd rather not test the rom on my device without community help. I've checked to make sure that the resolutions are similar, etc. My question is, is there anything I'm missing or anything that I should fix?
Accidentally double posted: Can a mod delete this thread?
So, anyone willing to answer this question for me?

Questions about ROMs and Porting

So, Since the Cyanogenmod source is so big (I heard that it has 19GB), people like us who have gay as slow internet have no chance of even trying to cook a ROM for our unsupported devices.
Since I can't download the whole CM source and I see awesome ROM's out there, I Ported one ROM called Cyanfox (which was made for Samsung S2 i9100) to Samsung Infuse 4G using Beanstalk ROM as a base. I followed a guide which asks me to replace some folders and edit some files. It was walking fine. Then came an update to both the ROMs, Thinking that cince it is a update, it will have the updated apps and source, I tried porting them again but this time Beanstalk updated ROM as a base cause a bootloop while the Beanstalk old ROM works fine as a Base ROM.
Now what I don't get is, why is Beanstalk new ROM not working as a base? (Since the new Beanstalk ROM will have updated Source, I want to use that ROM as my base.)
And the second question is, what files does actually matter when you are Porting or cooking an Android ROM? (I mean like windows works on all kind of PC's all it needs is the drivers right? The drivers actually matter on windows)
And the 3rd question is can I update the source files somehow without downloading the whole 19GB CM source and if possible how?
The 4rth is, I heard from somewhere that boot.img is the file which separates the phones? Then why can't we just port ROM's by replacing boot.img since these two phone's are from the same vendor and it has likely specs. (Which is not possible I think)
I am really really a newbie to this thingies, I just wanted to clear out these things. Sorry for my noobness.
Thanks!

Issues with Porting ROM

Hi everyone,
I have recently went into a business of messing around custom ROMs for my good old LG Spirit 4g. I am trying to port some newer android version ROMs (e.g LOS 16) to my phone, but not experiencing much success. The question I have is what is the minimum to make ROM from another device to at least make it to bootscreen, where I probably could hook up some adb logcat and debug it futher? I am using builds from Moto G3 which is essentially an identical device in a different body, with a much wider developer support . I have tried to do some things already, using files from roms compatible with my phone:
- Replace kernel in boot.img
- Edit updater_script (usually has very little difference to one from LG)
Might look not sufficient, but that's what I was able to find online. Would really appreciate any help!

Unofficial ROMs vs original ROM maker

Hi all,
I see sometimes that there are unofficial ROMs made of official ROMs such as Paranoid Android, that support devices such as our own before the original ROM creator does.
Now I know nothing about making ROMs, I'm guessing there of course is specific firmware and drivers for our phone as one example, unique to us.
Is it a support question, as in the official makers could support another phone (easily?!), but don't, because they don't have the device to confirm it works fine or may carry a brick risk etc?
How hard is it to make an "unofficial" ROM that supports specific devices features/hardware? Is it a case of merging differnt device firmware with another kernel and testing? (I'm sure some will be mad at my naivety)
Sorry for the newb question.

Categories

Resources