I'd like to know what are the differencies between kernels for, for example, CM10 and stock manufacturer's JB. Can we use stock kernel to build something different from stock? I've found no info myself so I'd like to ask you for help.
nagato.fm said:
I'd like to know what are the differencies between kernels for, for example, CM10 and stock manufacturer's JB. Can we use stock kernel to build something different from stock? I've found no info myself so I'd like to ask you for help.
Click to expand...
Click to collapse
Different kernels have different features and performance, the vast majority of kernel threads will include an overview of the features it has. The difference between stock Jelly bean from the manufacture and CM10 is features, for example the CM10 kernel includes additional governors and io schedulers as well as many performance tweaks. And yes you can use the stock Android kernel as a starting point to create your own custom kernels.
Sent from my SCH-I535 using xda premium
shimp208 said:
Different kernels have different features and performance, the vast majority of kernel threads will include an overview of the features it has. The difference between stock Jelly bean from the manufacture and CM10 is features, for example the CM10 kernel includes additional governors and io schedulers as well as many performance tweaks. And yes you can use the stock Android kernel as a starting point to create your own custom kernels.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
So it's possible to use stock kernel sources to port CM, for example?
nagato.fm said:
So it's possible to use stock kernel sources to port CM, for example?
Click to expand...
Click to collapse
Yes, using the kernel source for your device is a important part of creating a fully functional Cyanogenmod port. I would recommend taking a look at this guide to porting Cyanogenmod for a new device wiki.cyanogenmod.org/w/Doc:_porting_intro.
Sent from my SCH-I535 using xda premium
shimp208 said:
Yes, using the kernel source for your device is a important part of creating a fully functional Cyanogenmod port. I would recommend taking a look at this guide to porting Cyanogenmod for a new device wiki.cyanogenmod.org/w/Doc:_porting_intro.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
One more question: what is platform source and where (or how) to get vendor files? Sorry, I've found no answers in google.
nagato.fm said:
One more question: what is platform source and where (or how) to get vendor files? Sorry, I've found no answers in google.
Click to expand...
Click to collapse
The platform source is the actual Cyanogenmod source code and is obtained by doing the following step during the build process:
Code:
$ repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
$ repo sync
I would recommend taking a look at this guide for an overview of the build process as well as this guide. Vendor files have to be pulled from your device they are proprietary files such as binaries, and other driver components that allow your device to function properly (Phone, camera, GPS, etc.). If you are using a Nexus series device binaries can be downloaded here. If you don't have a Nexus series device take a look at this guide to setting up vendor files and use this guide as a base to extract the proprietary files after you setup the vendor folders.
Related
Hi all,
say that I'd like to try a CM7 custom compilation (e.g., removes half of packages, ...) for the sake of learning, what steps do you suggest to get into?
Compiling a full debuggable ROM and test it in the Android emulator?
Could I test It along with SE kernel (e.g., with the latest)?
In the emulator should i to install the SE related packages in order to set up the Xperia HW emulation?
Cheers!
There's a package of scripts named kitchen, made of a member here that let you customize a rom. There is even a root method that we were talking about the other day.
https://github.com/dsixda/Android-Kitchen
Hi kissmyarch,
i meant bulid It from the sources, not through the kitchen way ;-)
Oook sorry then.
LoL take a rom add ur theme, choose ur fav apps! Choose ur modules! And ur done! Custom rom is ready!
You know, I don't think people (including me) want to make a "repack" of an existing ROM, but build their own from sources instead, galvic
LoL nevermind then! This is what happening lately on mini pro forums, I just revealed how its being done!
Ravencz said:
You know, I don't think people (including me) want to make a "repack" of an existing ROM, but build their own from sources instead, galvic
Click to expand...
Click to collapse
I agree with Ravencz, building from sources is more funny than cooking... the fact is that you find a tutorial on cooking in the forum (and it's simplistic as hell) and no an hint on how to port your own CyanogenMod on your mini pro... what a pity...
Hoping someone on the devs' side will read this post ;-D... Cheers!
First of all cyanogenmod is already a cooked rom! If u want to port cyanogenmod u've to open it and then make it compatible for mini pro and repack it!
But you dont want that so rename the thread how to create custom gingerbread rom!
then use Sources from AOSP rom! Then repack 'em! Thats how its done, kitchen just provides an enviorenment for this!
galvic said:
First of all cyanogenmod is already a cooked rom! If u want to port cyanogenmod u've to open it and then make it compatible for mini pro and repack it!
But you dont want that so rename the thread how to create custom gingerbread rom!
then use Sources from AOSP rom! Then repack 'em! Thats how its done, kitchen just provides an enviorenment for this!
Click to expand...
Click to collapse
I'm sorry, but that's not completely true. CyanogenMod has it's sources as well. Sure, you can download a clean build from their website, but you can also build CM on your own.
@galvic: CM doesn't seem a cooked ROM to me, since they provide the repository from which you could clone the sources. CM seems more a fork (with enrichments/improvements) of AOSP and cooking a CM isn't the same of building its source.
So the thread is correct, because if i fetch and edit the Gingerbread branch of CM source, actually i've built a custom CM7.
Instead of linking those megabytes of ROMs, shouldn't be better working on CM's branch and attach the related patches that brought to a custom CM ROMs, as patches for kernel modules and so on? Benefits of patches are small downloads size, learning what people do in making your beloved ROM, ... On the other side you've to set up a developer's environment, that is a bit expensive (Gingerbread sources are around 7 Gigabytes, if i'm not wrong).
I don't know if Gingerbread is the best choice with the unchangeable kernel that SE stuck on our smartphone, but say Gingerbread or Froyo or whatever the fix you've to make on a CM are (logically) the same until someone will make an hackish strike and take down that damned bootloader.
See you!
Ravencz said:
I'm sorry, but that's not completely true. CyanogenMod has it's sources as well. Sure, you can download a clean build from their website, but you can also build CM on your own.
Click to expand...
Click to collapse
Sorry but CM is also bult on sources of AOSP
galvic said:
Sorry but CM is also bult on sources of AOSP
Click to expand...
Click to collapse
Of course it is, but it's modified
Ravencz said:
Of course it is, but it's modified
Click to expand...
Click to collapse
So we should also modify them exclusively for mini pro, then it'll be called a perfect ROM?
thats what free-xperia project did, use miniCM resources!
galvic said:
So we should also modify them exclusively for mini pro, then it'll be called a perfect ROM?
Click to expand...
Click to collapse
Nope, compiling gives you control over things such as source code, compiling options/flags for optimization (say that our mini pros have ARMv6 processor, why having a ROM built for generic ARM architecture? It doesn't make any sense... that's the source-oriented GNU/Linux distro way as Gentoo: compiling kernel and all application for your machine in order to have best performances and responses), possibility of adding removing code (e.g. libraries, system applications) and so on.
Cooking let's you modify something pre-made and doesn't give you *full* control on it ;-)
If we've to take over the world, we've to do it in the proper way! :-D
Cheers
Edit: Now CM7 is stable, can we plz get custom kernels
Old:
Kernel Devs refrain from making custom kernels for CM7 because the CM team asked them not to, in the alpha stage of the development.
Today i asked Atinm if he could give the green light to the Devs, he replied:
atinm said:
Actually, we don't care if people run other kernels. We just say that we will not debug other people's kernels - so if you have bugs, you go to the kernel developer's threads. Same as on the other Galaxy phones. And there is more chance of your phone being unstable with each nightly when you are on a different kernel and we change the kernel.
Click to expand...
Click to collapse
to all kernel Devs, if possible plz make custom kernels for CM7
Many thnx
ragiut1 said:
Kernel Devs refrain from making custom kernels for CM7 because the CM team asked them not to, in the alpha stage of the development.
Today i asked Atinm if he could give the green light to the Devs, he replied:
to all kernel Devs, if possible plz make custom kernels for CM7
Many thnx
Click to expand...
Click to collapse
I have maked one ...
I just saw it
Thnx
not quite the place to post this but party on
I had scaling issues with the stock kernel so i'm looking forward to this.
Great to see this.
I have 2questions.
1. Once we have these kernels will we be be able to flash files to enable Samsung stuff like Samsung dive, camera etc
2. Will new kernels be able to incorporate files from stock rom to fix the Bluetooth issue.
Thanks
Sent from my GT-I9100 using xda premium
aalupatti said:
Great to see this.
I have 2questions.
1. Once we have these kernels will we be be able to flash files to enable Samsung stuff like Samsung dive, camera etc
2. Will new kernels be able to incorporate files from stock rom to fix the Bluetooth issue.
Thanks
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
1. No.
2. No. All coding at the moment. Atnim is waiting for the att gs2 source code at the moment.
Sent from my Insanity powered SGS2
Now CM7 is stable, can we plz get custom kernels
aalupatti said:
Great to see this.
2. Will new kernels be able to incorporate files from stock rom to fix the Bluetooth issue.
Click to expand...
Click to collapse
CM 7.1 Stable has working bluetooth, and it wasn't a kernel issue, it was a driver source problem, Cyanogen either cracked it ahead of everyone else, or, got access to the missing source code, either way, winning like Charlie Sheen.
I have added my i9100 CyanogenMod 7.1 kernel with BLN support.
Details available here.
ImWarped said:
CM 7.1 Stable has working bluetooth, and it wasn't a kernel issue, it was a driver source problem, Cyanogen either cracked it ahead of everyone else, or, got access to the missing source code, either way, winning like Charlie Sheen.
Click to expand...
Click to collapse
Correct, driver issues are not the same as the kernel.
I'd love to see some kernel supporting gpu oc-uv, it's a good feature for battery saving purposes imho.
vnvman said:
I'd love to see some kernel supporting gpu oc-uv, it's a good feature for battery saving purposes imho.
Click to expand...
Click to collapse
You can use siyah kernel.
Sent from my GT-I9100
Hi,
I'd like to create my custom rom to LWW. WHere can I found source for android used in this mobile?
I found kernel sources on developer sonymobile com
But where can I found rest?
Regards
ajesik said:
Hi,
I'd like to create my custom rom to LWW. WHere can I found source for android used in this mobile?
I found kernel sources on developer sonymobile com
But where can I found rest?
Regards
Click to expand...
Click to collapse
Start by editing stock ROM files, so that you can understand how Android works etc.
And of course, learn from mistakes.
Sent from my Xperia Live using xda premium
Thank you, but I'd like to ownload source code
There is no source. Just take stock ROM and then edit it as much as you want.
If you have stock ROM on your phone, just pull system folder via ADB and start editing.
Sent from my Xperia Live using xda premium
You can learn how to create a custom rom Here
i think you could get the CM source, don't think sony will release their sources.
http://wiki.cyanogenmod.com/wiki/Building_from_source
Does the galaxy player line have a github repo? I have picked to build an aosp gingerbread rom for an independent study at my school and the rules are that it has to be pure aosp and I figured that building from scratch would be the easiest way because touchwiz is deeply integrated into the software in the device. If I can't do it from the github, does anyone have experience for building aosp?
Sparx639 said:
Does the galaxy player line have a github repo? I have picked to build an aosp gingerbread rom for an independent study at my school and the rules are that it has to be pure aosp and I figured that building from scratch would be the easiest way because touchwiz is deeply integrated into the software in the device. If I can't do it from the github, does anyone have experience for building aosp?
Click to expand...
Click to collapse
which galaxy player ? the 4.0 and the 5.0 have cm9 and cm7 which are essentially aosp so you'll need to contact the developers...look at the development forum to see who they are
Its for the 5.0, the ROM I need to build can not already exist and must be a nexus-like ROM with gapps installed such as the nexus s gingerbread ROM. Nothing more nothing less and everything must work
Sparx639 said:
everything must work
Click to expand...
Click to collapse
that's the problem, the current cm7 rom has some issues and no one is working on them because cm9 is a bigger priority, you should ask gmillz for help as he seems one of the main 5.0 devs at the moment
I just want aosp such as the apex rom for the droid x or something similar, it cant be a cyanogenmod rom because those are already being worked on and I cant use generic ginger because its not mine and its not fully aosp
Try building AOSP from source. Use gmillz's device tree as it is the most stable atm. I'm also working on an experimental device tree which may or may not fix some issues so you could also use that if you want
Sent from my Nexus 7 using XDA Premium HD app
And this is for gingerbread without having cm7 or aokp tweaks?
Sent from my Galaxy Nexus using xda app-developers app
Sparx639 said:
And this is for gingerbread without having cm7 or aokp tweaks?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Oh right sorry. I didn't read your initial post properly. These github repos are for CM9. You can build CM7 pretty easily as it doesn't require any propriety files as hardware acceleration is not usually enabled in GB roms. Sorry for the confusion
I can't do any cyanogenmod Roms, it has to be a nexus like ROM. As in stock 2.3.3 you would find on the nexus s
Sparx639 said:
I can't do any cyanogenmod Roms, it has to be a nexus like ROM. As in stock 2.3.3 you would find on the nexus s
Click to expand...
Click to collapse
In that case try building AOSP gingerbread. I'm fairly certain that there are some instructions from Google on how to do so
Sent from my Nexus 7 using XDA Premium HD app
Thank you, I am really new so I don't completely understand googles directions for building aosp, the part I don't understand is how the kernel and ROM is built after you sync the repos. Don't you need drivers and to link the kernel with the ROM? It just doesn't make sense to me yet
Sent from my Galaxy Nexus using xda app-developers app
Sparx639 said:
Thank you, I am really new so I don't completely understand googles directions for building aosp, the part I don't understand is how the kernel and ROM is built after you sync the repos. Don't you need drivers and to link the kernel with the ROM? It just doesn't make sense to me yet
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Hello,
I want a github for the Galaxy Player 3.6.
Can you help me?
thank you
h2o64 said:
Hello,
I want a github for the Galaxy Player 3.6.
Can you help me?
thank you
Click to expand...
Click to collapse
You have to create the device tree by yourself mate
Sent from my HTC One S using Tapatalk 2
Excuse me in fact i wont to say "i search "
Sent from my YP-GS1 using xda app-developers app
Hello,
I did some research and I discovered that Player 3.6 has the same CPU as:
-Motorola DEFY + (MB526)
-Motorola Droid 2
However, the Defy + a:
- CyanogenMod + CWM: http://forum.xda-developers.com/showthread.php?t=1795647
and
- http://forum.xda-developers.com/showthread.php?t=1566861
And Droid 2: http://www.clockworkmod.com/rommanager/developers/droid2?name=Motorola% 202% 20Droid
Is that this could help to advance the device tree?
thank you
h2o64 said:
Hello,
I did some research and I discovered that Player 3.6 has the same CPU as:
-Motorola DEFY + (MB526)
-Motorola Droid 2
However, the Defy + a:
- CyanogenMod + CWM: http://forum.xda-developers.com/showthread.php?t=1795647
and
- http://forum.xda-developers.com/showthread.php?t=1566861
And Droid 2: http://www.clockworkmod.com/rommanager/developers/droid2?name=Motorola% 202% 20Droid
Is that this could help to advance the device tree?
thank you
Click to expand...
Click to collapse
It would need to have the same board, not only the same CPU, if it does have any other similar hardware then it may help.
Board ?
I saw this :
http://www.glbenchmark.com/phonedet...ro25&D=Samsung+Galaxy+Player&testgroup=system
and
http://www.glbenchmark.com/phonedet...sung+YP-G1+Galaxy+Player+4.0&testgroup=system
--> the Player 3.6 has the same board as the Player 4.0
Intressting ?
Update :
The Player Player 3.6 and 4.0 are almost identical except for the CPU and screen size!
Then the two might be able to help each other out such as graphics drivers/WiFi drivers etc.
I'm aware that there are custom kernels for 5.0 by rumirand and entropy,
but rumirand's kernel is not really 100% compatible with YP-GB70 (KOR) and this is the device that i currently have.
Unfortunately, even in Korea GP forum, there is absolutely no custom kernel for 5.0 (Tegrak Kernel exists for 4.0)
So i wanted to develop it on my own so i've been searching for instructions.
I've instaled ubuntu, installed bunch of stuffs.
but i have no idea how to start. all those guides were incoherent.
can somebody tell me some basic infos and things that i should know for developing YP-GB70 kernel?
I would advice starting with reading about linux kernel structure, how it works etc.
I would like to develop new kernel for 5.0 too
Send from samsung galaxy s wifi 5.0 running paranoidandroid.
search, search, search!
That's what I had to do. I now have a modified, compiled and running kernel with no prior experience. Follow that guide, look at the android site for setting up an environment, etc.
Then you need your source files + initramfs. I don't think samsung has released their initramfs source so you're going to need to find it elsewhere. Samsung stuff is also different than the nexus things that the android site refers to so you need to take bits and pieces of information from places and piece it together yourself. I recommend looking at other kernel builder's githubs too, I've modified others sources and have wound up with good results.
exodus454 said:
search, search, search!
That's what I had to do. I now have a modified, compiled and running kernel with no prior experience. Follow that guide, look at the android site for setting up an environment, etc.
Then you need your source files + initramfs. I don't think samsung has released their initramfs source so you're going to need to find it elsewhere. Samsung stuff is also different than the nexus things that the android site refers to so you need to take bits and pieces of information from places and piece it together yourself. I recommend looking at other kernel builder's githubs too, I've modified others sources and have wound up with good results.
Click to expand...
Click to collapse
yeah that's what i was doing. i managed to extract initramfs from the zimage but dont know what to do anymore :silly:
Do you have any idea if the initramfs is the same between your version and the rest of the world? You might be able to use an already extracted version.
Sent from my YP-G70 using xda premium
exodus454 said:
Do you have any idea if the initramfs is the same between your version and the rest of the world? You might be able to use an already extracted version.
Sent from my YP-G70 using xda premium
Click to expand...
Click to collapse
yes? i searched github but there weren't any for GB70 (there was g70)
So i just did it by myself, which took me around an hour. Everything was new to me so uploading GB70 initramfs to github took me like 30 mins.:silly:
my next step is to add cwm recovery to the kernel and it;s quite hard. most of the guides written in this forum are usually written for specific devices.
Before you start modifying the kernel, and i suggest you try compiling it to make sure your sources are good.
Sent from my SGP5 with XDA Premium
exodus454 said:
Before you start modifying the kernel, and i suggest you try compiling it to make sure your sources are good.
Sent from my SGP5 with XDA Premium
Click to expand...
Click to collapse
It can't be wrong. I got the zImage from Korean stock rom tar. But you are right. I gotta try decompiling and compiling to make sure
stylemate said:
It can't be wrong. I got the zImage from Korean stock rom tar. But you are right. I gotta try decompiling and compiling to make sure
Click to expand...
Click to collapse
Just a note..you can't decompile a kernel binary. The farthest you can go is extracting the initramfs from it. To get a kernel you would have to build it from source.
Sent from my HTC One S using Tapatalk 2
klin1344 said:
Just a note..you can't decompile a kernel binary. The farthest you can go is extracting the initramfs from it. To get a kernel you would have to build it from source.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
oops seems like i made a noobish term mistake there
i wanted to write unpack but thought that decompile can be used also. Thanks!