I have had experiences with gentoo and wish to try my hands at developing my own AOKP rom for a chinese tablet that is unsupported.
I am currently syncing my repo and wish to understand more before I proceed.
What will be the easiest way to get Android running if I compile AOKP? Given that the tablet runs ICS at the moment, will it work if I compile AOKP and port the existing kernel over?
I have also gotten my hands on the source codes for the tablet.
Do you have a device tree?
If not, first you should create one.
Then only you can compile android.
adil_ said:
Do you have a device tree?
If not, first you should create one.
Then only you can compile android.
Click to expand...
Click to collapse
I highly doubt that there is an existing device tree. Now comes the noob question: How can I check if there is an existing device tree???
Anyway, I have been extensively reading up on building android and gotten the AOKP sources and original manufacturer source. Am I right to say that as long as I can compile AOKP, I should be able to boot using an existing kernel??
As for the the two sources, should I copy over the original devices and hardware folder to the AOKP source before I build so as to ensure a compatible build???
tobyhund said:
I highly doubt that there is an existing device tree. Now comes the noob question: How can I check if there is an existing device tree???
Click to expand...
Click to collapse
Google.
Anyway, I have been extensively reading up on building android and gotten the AOKP sources and original manufacturer source. Am I right to say that as long as I can compile AOKP, I should be able to boot using an existing kernel??
Click to expand...
Click to collapse
No it is not right to say. While it is possible you will probably need to do extensive debugging along the way.
As for the the two sources, should I copy over the original devices and hardware folder to the AOKP source before I build so as to ensure a compatible build???
Click to expand...
Click to collapse
Depends on what source you are talking about. What source do you have exactly?
You could try my thread here: http://forum.xda-developers.com/showthread.php?t=1935162
It does have some nice links to.
I am still trying to get Jelly Bean on a device right now. I went from trying to port a JB ROM from a clone to just plain out compiling an AOSP ROM. I already got everything set up. I am even compiling a ROM right now. (full-eng). I figured that this was the option for all devices but being an idiot i started reading and the 10 options or so didnt include my device. It was nexus and samsung phones. Is there a way to compile AOSP or even Cm10.1 or AOKP for an Unsupported device? I am dying to find out and get this released!
Any help will be greatly appreciated!
The main thing is you will need a kernel to support the device. So you will have to track sown the kernel source code.
Wayne Tech Nexus
zelendel said:
The main thing is you will need a kernel to support the device. So you will have to track sown the kernel source code.
Wayne Tech Nexus
Click to expand...
Click to collapse
I have a kernel source code for it. This is it right here: https://github.com/leopesto/kernel_mtk6577
Can i build AOSP Jelly bean from that? And if so. how?
Droid Premium said:
I have a kernel source code for it. This is it right here: https://github.com/leopesto/kernel_mtk6577
Can i build AOSP Jelly bean from that? And if so. how?
Click to expand...
Click to collapse
Well you need to know it that is a JB kernel to begin with. Then I would look at the tut for building a kernel. Just a heads up. Most of the MTK so called kernel source is never the full and proper source code.
Wayne Tech Nexus
zelendel said:
Well you need to know it that is a JB kernel to begin with. Then I would look at the tut for building a kernel. Just a heads up. Most of the MTK so called kernel source is never the full and proper source code.
Wayne Tech Nexus
Click to expand...
Click to collapse
Well i have that one and a source code from a clone (TCL-S600). I am almost positive that that kernel will work. My goal is to either compile some sort of Jelly Bean ROM for this device or De-grade it to Gingerbread. The users on this device don't like ICS for multiple reasons so I am just trying to do what they asked. Any suggestions?
This is a project I started to work on an AOSP ROM for our Grand 2.
When it gets to boot successfully, I'll make a DevDB thread for it.
The Grand 2 and the Moto G share the same chipset, the Sanpdragon 400. I'm downloading it and applying a few patches to see if it works.
I'll upload my success/failure here.
This is also a request for devs to help.
you would have better luck porting the sgs3/4/5/note3/mega CM rom, because they were made by samsung.
even though they dont have the same cpu it would literally be easier to port cm from one of those devices than from a different OEM.
shabbypenguin said:
you would have better luck porting the sgs3/4/5/note3/mega CM rom, because they were made by samsung.
even though they dont have the same cpu it would literally be easier to port cm from one of those devices than from a different OEM.
Click to expand...
Click to collapse
I'm going to try it if my Moto G ROM port fails. But don't these devices have totally different CPUs? The only other Samsungs with this chip are the Tab 4 variants (a ported Tab 4 ROM won't work) and the S3 Neo+, which doesn't have any custom ROM.
shabbypenguin said:
you would have better luck porting the sgs3/4/5/note3/mega CM rom, because they were made by samsung.
even though they dont have the same cpu it would literally be easier to port cm from one of those devices than from a different OEM.
Click to expand...
Click to collapse
I'm going to try it if my Moto G ROM port fails. But don't these devices have totally different CPUs? The only other Samsungs with this chip are the Tab 4 variants (a ported Tab 4 ROM won't work) and the S3 Neo+, which doesn't have any custom ROM.
As you are a developer, can you help me if I use a CM ROM from the devices you mentioned? The patch applied only works for ROMs for the same CPU type. I don't think it will work in this case. And does a TouchWiz kernel work over an AOSP/CM ROM.
that was my point, that those devices are closer because it has teh name samsung on it than this does to the moto g with the same chipset.
the moto g roms dont boot on the moto g 4g, times have changed to where roms are VERY device specific. i mean CWM has to have 2 versions because teh 4.3 version wont even work on teh 4.4 version..
shabbypenguin said:
that was my point, that those devices are closer because it has teh name samsung on it than this does to the moto g with the same chipset.
the moto g roms dont boot on the moto g 4g, times have changed to where roms are VERY device specific. i mean CWM has to have 2 versions because teh 4.3 version wont even work on teh 4.4 version..
Click to expand...
Click to collapse
Okay. I'm trying the Mega 6.3's CM ROM, as the Mega is the closest Samsung phone to the Grand 2. Thanks.
shabbypenguin said:
that was my point, that those devices are closer because it has teh name samsung on it than this does to the moto g with the same chipset.
the moto g roms dont boot on the moto g 4g, times have changed to where roms are VERY device specific. i mean CWM has to have 2 versions because teh 4.3 version wont even work on teh 4.4 version..
Click to expand...
Click to collapse
Moto G ROM failed to boot. Though it passed the GALAXY GRAND 2 SM-G7102 thing at boot, it gives a flash of light and reboots the phone. Probably a result of using a TouchWiz kernel?
Failure will be uploaded later today.
My patch was about copying files from a Grand 2 ROM (TouchWiz used) to the new ROM.
IT FAILED. Trying on the Mega 6.3's CM build.
WaseemAlkurdi said:
Moto G ROM failed to boot. Though it passed the GALAXY GRAND 2 SM-G7102 thing at boot, it gives a flash of light and reboots the phone. Probably a result of using a TouchWiz kernel?
Failure will be uploaded later today.
My patch was about copying files from a Grand 2 ROM (TouchWiz used) to the new ROM.
IT FAILED. Trying on the Mega 6.3's CM build.
Click to expand...
Click to collapse
no its because you used a cm rom that wasnt made for this device. you cnat port roms like that you need to take teh device tree and fully make cm11 using that and compile it.
wat about miui??
shabbypenguin said:
no its because you used a cm rom that wasnt made for this device. you cnat port roms like that you need to take teh device tree and fully make cm11 using that and compile it.
Click to expand...
Click to collapse
Which I didn't ever understand. Can you help me?
Do you take the device tree thing as a file?
Is building CM from that harder than building a computer program using VB.NET, or harder?
Can you help me cuz I never built a ROM that way.
If it needs Linux, then I got it (32-bit Ubuntu and x86_64 Fedora), though Windows is better.
And thanks for patience with my dumb questions
shabbypenguin said:
no its because you used a cm rom that wasnt made for this device. you cnat port roms like that you need to take teh device tree and fully make cm11 using that and compile it.
Click to expand...
Click to collapse
http://xda-university.com/as-a-developer/getting-started-building-android-from-source
I found this thing. Can you help me by translating this to human-understandable form? Could you just carry out the steps and I'll test and do virtually everything you need to do as if you had the device in your two bare hands?
Or can you just give me instructions and I'll execute?
No.
building Cm is fairly straight forward if your device is officially supported, this device doesnt have anything. someone needs to download the source code for CM, grab my devices trees and add in all the missing info by studying the stock rom and comparing it to similar device. this can take anywhere from days to months, and even then some devices end up with stuff that is forever broken.
shabbypenguin said:
No.
building Cm is fairly straight forward if your device is officially supported, this device doesnt have anything. someone needs to download the source code for CM, grab my devices trees and add in all the missing info by studying the stock rom and comparing it to similar device. this can take anywhere from days to months, and even then some devices end up with stuff that is forever broken.
Click to expand...
Click to collapse
Thanks a lot.
So it needs a really experienced developer, whereas I am a Grade 10 student at school who knows no android programming. Sorry for wasting your precious time. But do you anyone who's willing to do it? I have school, and my parents do not let me give up schoolwork to porting a ROM.
Sorry but there isnt a bunch of peopel out there waiting for new phones to port CM to, how it works is someone with the phone ports cm and once it is considered good enough is submitted to be made official through their gerrit. then they have to become the maintainer of it and any code changes, updates etc have to be handled. its a lot of work. it doesnt need to be experienced, just a matter of fast learning as well as having a background in java/c really helps.
shabbypenguin said:
Sorry but there isnt a bunch of peopel out there waiting for new phones to port CM to, how it works is someone with the phone ports cm and once it is considered good enough is submitted to be made official through their gerrit. then they have to become the maintainer of it and any code changes, updates etc have to be handled. its a lot of work. it doesnt need to be experienced, just a matter of fast learning as well as having a background in java/c really helps.
Click to expand...
Click to collapse
Thanks. Do you have the a link to the vendor trees? I'll try to check them. But tell me how to compare them and where is the missing info to add. I'll do it. Fast learning is done while you tell me to compare. So, it's me downloading the device and vendor trees, then what? Your turn.
P.S. 1. Stuff that's forever broken came to happen with the Galaxy Star. It has a CM ROM, which boots, but has no audio, no ril, no camera, and broken menu/back keys.
2. Are you American? I was born there too! Nice coincidence!
BTW, which state are you from? I'm from Illinois.
In AOSP, SystemUI and Build.prop require the main effort. If they are ready, you pretty near?
Sent from my SM-G7102 using XDA Premium 4 mobile app
keshavt said:
In AOSP, SystemUI and Build.prop require the main effort. If they are ready, you pretty near?
Sent from my SM-G7102 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Not exactly. There's a lot of work to be done on ril, camera, Wi-Fi, and other hardware drivers, in addition to the kernel. I'm thinking about borrowing some files from the ill-fated CM build.
WaseemAlkurdi said:
Not exactly. There's a lot of work to be done on ril, camera, Wi-Fi, and other hardware drivers, in addition to the kernel. I'm thinking about borrowing some files from the ill-fated CM build.
Click to expand...
Click to collapse
What happened brother any progress
Sent from my SM-G900I using XDA Premium 4 mobile app
techmate98 said:
What happened brother any progress
Sent from my SM-G900I using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Have paused development because, when I asked him for a couple of files from his failed CM build, mukulsoni told me to wait a little because he was nearly done with his CM11 build.
WaseemAlkurdi said:
Have paused development because, when I asked him for a couple of files from his failed CM build, mukulsoni told me to wait a little because he was nearly done with his CM11 build.
Click to expand...
Click to collapse
great!!! so is his build working now
Hi everyone, i'm trying to build my first rom. I followed the building guide from xda-university. I want to build AOSP lollipop from source(no cm) for Huawei G630. I searched a lot on the forum and google but i cannot find the proper information. I synced the AOSP repo. But i need help with the device tree. There is none available out there as there is no AOSP-based rom available for it. So i am supposed to create the device tree by myself right? How do i do that?(or maybe...is it to difficult to do for a beginner like me? ) Any help is really appreciated.
Thanks!!
Or at least could someome point me to a forum where i can get help?
Thanks
Sent from my G630-U20 using XDA Free mobile app
MultiPDev said:
Or at least could someome point me to a forum where i can get help?
Thanks
Sent from my G630-U20 using XDA Free mobile app
Click to expand...
Click to collapse
Maybe this will help http://forum.xda-developers.com/showpost.php?p=35753229&postcount=2
Limbo045 said:
Maybe this will help http://forum.xda-developers.com/showpost.php?p=35753229&postcount=2
Click to expand...
Click to collapse
Thanks, but that is for devices with official cyanogenmod support
MAKE SURE YOUR PHONE IS ON OFFICIAL LATEST
Click to expand...
Click to collapse
But as i said, my device has no aosp rom available for it, hence I have to build aosp "from scrstch" (not based on another aosp rom). I can't find any information on how to do this.
Any idea on how to build an aosp rom for a new device?
hi everyone
i was going to try building a kernel for .131 rom but i couldnt find anything over on github
if any have it can you please share?
Here
hxxp://developer.sonymobile.com/downloads/xperia-open-source-archives/
You have success?
Does it work on e2312 (Aqua dual)?
Dell Schulz said:
You have success?
Click to expand...
Click to collapse
im working on it as a hobby on my free time
soo it wont be opertional anytime soon
https://github.com/sonyxperiadev/kernel-copyleft/commits/26.3.A.1.xxx
there's kernel repo for AOSP and opensource ROMs (https://github.com/sonyxperiadev/kernel)
and kernel-copyleft for Sony's "Stock" ROMs (https://github.com/sonyxperiadev/kernel-copyleft) ,
for additional drivers (e.g. FM/Bluetooth, etc.) you'll need the opensource driver tarball from https://developer.sonymobile.com/do...n-source-archive-for-26-3-a-1-33-26-3-b-1-33/