There are Lott's of threads for porting for Rom's to any device..
But most of describes to use same android versions for base and port...
But i want try porting CM12 for Galaxy Core...
I am not a developer but still want to use Cm12 on my device .. So instead of asking some one i would love to port it by myself:thumbup:
hareshsangar said:
There are Lott's of threads for porting for Rom's to any device..
But most of describes to use same android versions for base and port...
But i want try porting CM12 for Galaxy Core...
I am not a developer but still want to use Cm12 on my device .. So instead of asking some one i would love to port it by myself:thumbup:
Click to expand...
Click to collapse
That is hard to do without a background in building from source and knowing some coding and kernel stuff. You don't have lollipop yet on that device so it will be even harded. You can't just copy some files. You need a device tree and modify the kernel and then build cm12 from source.
Thanks for taking time .. But i would if i can port CM11 at least
hareshsangar said:
Thanks for taking time .. But i would if i can port CM11 at least
Click to expand...
Click to collapse
Well I don't know about your device (it's basically the same for all Qcom device, I don't know about MTK). Porting by copying files is less reliable then building from source (well it's way easier). It's very very hard to solve bugs when copying files and if the base has bugs the port might be even more buggy.
Related
can anyone help me to learn a bit more than android!
I heared about compile form source and biuld form source...And I can't understand what diferences between compile from source and port! can U explain easily?
for example should I want to bring superOxygen Rom in my x10 , should I port it with cm as base or compile form source?!
thx
for short:
porting means you are making rom to your device from another device, you will be just moving libs, editing ramdisk, etc.
compiling from source means you make a complete rom from scratch including programming own drivers, libs in some situations.
If source is avaiable fot superOxygen then you can try compiling it yourself, but editing, or adding your drivers is necessary, and anyway its harder than porting, but gives better result in fact because you can program everything to make it work and you aren't dependant on binary files like in porting.
When porting, hardware should be close to one you have in your X10, because most things will not work when processor differs, wifi modules, gsm etc. You take files from any X10 rom and replace ones that are with same name in another rom (oxygen here).
Thanks very much man!
I took your advices...it was good advices but what is your idea about this:
If I port Superoxygen from Nexus1 for my x10 and (use stable AOSP as base) , then can I say I make a superOxygen Rom?
compiling from source is how much difficult?! I'm 17...! , I have a link that teach compile from source... Is it need some Knowledges that is impossible for me?!
heh, im 17 too and I don't have much knowledge, but looking on pcfighter(a gt540 developer) im impressed, hes 17 too and does a great job, so it depends on time spent and interests
when you port oxygen, you can just say that you ported and not made it. credits go to the maker and you for just making it work on x10
I'm looking now how to compile for gt540 but can't find any idea how to make it strict for gt540 compiling from source tutorials are mostly for nexus s and nexus 4g because most of are just remade of what you can find on official android developer page and its easier. For unsupported device its even harder, you have to work with what you already have and add it first to sources then ... more things to do. I'm beginner with that too, just pulled sources yesterday and looking how to make it work :] so don't expect so much help in this way :]. Just telling you overall how this looks
For compiling you need to know Java and C programing language.
Sent from my Xoom using Tapatalk
@mesaj! do you know c and gava programing languge?! ofcourse I worked c++ a little...
Thanks now I also know what the difference is.
In easy terminology. Compiling a ROM is building a ROM from the source code so it means you are building a ROM from the ground up. Porting a ROM to your phones means to take a ROM built for another phone and to get it working on yours. That's the simplest way to think of it. I have in my signature a guide for compiling a ROM. Oh and I'm newly 18
私のEVO 3Dから送信される。
Thanks for this thread
Thanks now I also know what the difference is.
Click to expand...
Click to collapse
Thanks for this thread
Click to expand...
Click to collapse
just press the thanks button if you like this thread
So i saw that in other devices fourms they ported the Sense 4.0 multitasking screen. But it's not working for all devices or builds.
So a dev/ or user has to port the code to our builds . I myself don't have the time to port it but i am looking forward to seeing this on out beloved device.
Here's the source thread. http://forum.xda-developers.com/showthread.php?t=1589963
Deonix said:
So i saw that in other devices fourms they ported the Sense 4.0 multitasking screen. But it's not working for all devices or builds.
So a dev/ or user has to port the code to our builds . I myself don't have the time to port it but i am looking forward to seeing this on out beloved device.
Here's the source thread. http://forum.xda-developers.com/showthread.php?t=1589963
Click to expand...
Click to collapse
It's quite easy I have this running now on my defy ...... U need to source code to apply no porting necessary
I will help you make one for yourself after my exams are done
There's already a thread that has a flashable zip that works for older nightlys.
it may look neat but it hardly promotes multitasking that the inbuilt ics carousel provides...you can barely see the next two open apps using the sense "multitasker"
Kayant said:
It's quite easy I have this running now on my defy ...... U need to source code to apply no porting necessary
I will help you make one for yourself after my exams are done
Click to expand...
Click to collapse
Thanks. I have exams as well ) i will try to port it. If i stumble i will let you know. Maybe i will like it.
Good luck on your exams.
Hey guys!
My device (the HTC One X for AT&T) currently has a CM9 and AOKP port. I really wanted to get started with developing though. I wanted to create a full AOSP ROM (directly from Google) just to learn the process and get my hands dirty with ROM development (I've already done quite a few mod packs and a kernel).
We have an open sourced CM9 device tree available. I've tried using that device tree for building the AOSP ROM but of course, it has errors because the AOSP source isn't CM9...
So what I'm asking is how can I use this CM9 device tree with a pure AOSP ROM? Like, how exactly do I edit the CM9 device tree so that it creates an AOSP ROM? I'm aware its no easy task, but if someone could point me in the right direction it would be greatly appreciated. I'm a noob when it comes to ROM development, I've never made one before haha I have compiled ROMs before, I maintain the AOKP nightlies for the HP Touchpad.
If someone could help me make this device tree work it would be awesome. Thanks!
P.S. Here is the tree in case someone wanted to look at it: https://github.com/vmagro/android_device_htc_evita
Delete cm.mk
Edit vendorsetup.sh (remove "cm_").
That is all you need to do, I believe.
Like you know, sync the AOSP source, include your device folder amd build.
Sent from my Galaxy Nexus using Tapatalk 2
mDroidd said:
Delete cm.mk
Edit vendorsetup.sh (remove "cm_").
That is all you need to do, I believe.
Like you know, sync the AOSP source, include your device folder amd build.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I found this thread and this is exactly what I'm doing. Would you be interested in answering my questions in exchange for a nice donation? I haven't had much luck getting help and being a single parent of three toddlers I really need to maximize my free time to work on this.
You also would have to delete any offending overlays from CM that are present within your device repo. As you compile you may run into errors which you could work through.
私のEVO 3Dから送信される。
dastin1015 said:
You also would have to delete any offending overlays from CM that are present within your device repo. As you compile you may run into errors which you could work through.
私のEVO 3Dから送信される。
Click to expand...
Click to collapse
Removing overlays doesnt work here. Have many issues regarding the kernel.
hey
Good luck
rohan32 said:
Hey guys!
My device (the HTC One X for AT&T) currently has a CM9 and AOKP port. I really wanted to get started with developing though. I wanted to create a full AOSP ROM (directly from Google) just to learn the process and get my hands dirty with ROM development (I've already done quite a few mod packs and a kernel).
We have an open sourced CM9 device tree available. I've tried using that device tree for building the AOSP ROM but of course, it has errors because the AOSP source isn't CM9...
So what I'm asking is how can I use this CM9 device tree with a pure AOSP ROM? Like, how exactly do I edit the CM9 device tree so that it creates an AOSP ROM? I'm aware its no easy task, but if someone could point me in the right direction it would be greatly appreciated. I'm a noob when it comes to ROM development, I've never made one before haha I have compiled ROMs before, I maintain the AOKP nightlies for the HP Touchpad.
If someone could help me make this device tree work it would be awesome. Thanks!
P.S. Here is the tree in case someone wanted to look at it: https://github.com/vmagro/android_device_htc_evita
Click to expand...
Click to collapse
Were you able to port aosp device tree from cm.Please tell me how ?
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.
Hi
Please build or port an Aosp rom to our great devices.
If somebody agree with me, please strengthen in it.
Thanks
zsolt
There are people working on CM and AICP ports. You can see here: http://en.miui.com/thread-407842-1-1.html
prismk said:
There are people working on CM and AICP ports. You can see here: http://en.miui.com/thread-407842-1-1.html
Click to expand...
Click to collapse
yes i know, i have seen these posts
thanks
If you already knew then why did you start a new thread?
Why do some people think that asking for a ROM will make it magically happen faster or something?
Sent from my Redmi Note 4 using Tapatalk
Do you use AOSP rom if that rom don't have fingerprint function (because RMN4 use FPC1035 with MTK TrustSonic enabled, it's so hard to port it unless Xiaomi release kernel source code) ?
Most people asking for porting rom from other devices but also demand porting rom have full functions working like original rom which impossible to make it happen...
longnt2007 said:
Do you use AOSP rom if that rom don't have fingerprint function (because RMN4 use FPC1035 with MTK TrustSonic enabled, it's so hard to port it unless Xiaomi release kernel source code) ?
Most people asking for porting rom from other devices but also demand porting rom have full functions working like original rom which impossible to make it happen...
Click to expand...
Click to collapse
Yep. As I said in the X20 kernel thread, it's only just the beginning because that's only generic X20 kernel source. ODM's *always* add their own hardware that is not covered by the original kernel source.
Typically, Camera and Sensor drivers were the most difficult to port (with blobs and reverse-engineering stock firmware). But TrustSonic sounds like it will be the biggest task.