Saturday, 8 February 2014

ROM Porting By Me (Why its not possible)

ROM Porting By Me (Why its not possible)

I think many of you still needs to read this..
These words were posted by "Cheatman" - KyleOpen ROM Developer
I am/was getting many PMs regarding this and even i posted there responses to my threads also but still i am getting requests and all...
You must read this....
Thanks to Cheatman to save my time 

---Edited words---

"Ok guys, I'd like to clarify some things about JB porting. To make this happen there is at least one of the following two things that must happen:

1. We must find a *similar* (best case scenario) phone with dual sim and JB. It HAS to be a Samsung phone. If it's not Samsung, all kinds of problems and development drawbacks will happen, so it'll take forever to port.

2. The CM10/AOSP teams have to build generic dual-sim support into their sources. Sadly, this is very complicated and will not likely happen any time soon. It is complicated because Micromax, HTC, Karbonn, Spice, Samsung and Sony use different CODE to handle dual-sim functionality. This is why google is important for Android. Without it, everyone does whatever they want, if they don't have a reference architecture. And Google did not implement (fully) the dual-sim architecture for Android. Thus, everyone does what they want.

Do not assume that any ROM of a device with dual SIM and JB can be ported. It has to have similar hardware (for driver compatibility), be made by the same manufacturer (because we need the same implementation of dual-sim) and must have the kernel source released (so I can look at it and try to port a working kernel for our device).

I'm still looking for new stuff and improvements to add to the ROM. Right now about all of the features that I want are already included either as add-ons or part of the ROM itself. That said, I'm looking for stuff that fit ALL OF the following criteria:
Features that are of general interest or bring new functionalists. Things like audio, video, memory, SD and speed tweaks. Driver improvements, better speed etc.
Features that are generally useful. If you think that I'll include OTG in the kernel (and work my a$$ off!) just because you have a USB host cable around the house and would like to test it, think again. Generally useful stuff include those aspects of the ROM that everyone uses, such as WiFi and the touchscreen. Exotic stuff will never be included.
Features that are easy to implement. This is a so and so criterion, because easy to include stuff (such as the CSC mods) will always be included even if they are exotic and not useful to many people. But, the easier it is to implement, the more likely I will include the feature in the ROM. I am a very lazy guy, although most of you would probably not think so.
The mods have to be available for inclusion in third party ROMs (some mods can only be downloaded directly from threads and it's not allowed by their creators to include them in ROMs). So please read full description and check if I can include it in the ROM.
Features that you tested before you report them, whenever possible. It really grinds my gears when I test a reported mod only to find it soft-bricks my phone. It's true that I can restore it in about one hour even when not at my PC, but it's still very annoying )


No comments:

Post a Comment