I am new here, and I am very confuse about kernel.
I know what ROM is, and the benefit of custom ROM. But I am not sure about kernel. What is it exactly? Please give me a simple explanation.
Is the kernel included in rom when I install a custom rom?
Beside THat i don't have the ability to unlock bootloader coz manuf above 29 w11a32 so what is the issue.
and i think kernel is the reason that coz my phone soft brick more than a time coz this what is called kernel any help ???
1st: Hi, and welcome to the forum hope you enjoy your stay
2nd. Ok, a kernel is what the phone manages its power from. it controls the power and battery on your phone.
press the thanks button if i helped
hello..
you should have searched and read before asking.. i mean i am also new but i have successfully learnt what a 'noob' can maximally know like about roms, kernels. etc..
refer to this very guide... it will give all answers required by you related to kernel roms bootloader etc..... hopefully..
http://forum.xda-developers.com/showthread.php?t=1590266
and about the bootloader thing... its just that its not recommended to unlock it after 11w29 series..
These phones ship with a revamped chipset configuration having the security hole the boot loader unlock uses effectively closed. This means that upon unlocking the boot loader your phone will end up as a hard brick - and you will have NO means to revive the phone yourselves. You either have to send it off to Sony Ericsson for repair (recommended solution) or find a phone repair shop being able to resurrect shot devices!
refer to the foll thread:
http://forum.xda-developers.com/showthread.php?t=1481630
kernel is something like bridge between HW and the SW. SW (ROM, apps,...) communicates with HW (camera, display, digitizer,...) through kernel
if you want some more info, look here
Hi, welcome to XDA!
The X8 phone runs Android.
Android is a Google led variation of Linux kernel.
Linux is an Open Source (a share and share a like philosophy) kernel that can run on pretty much anything. It is like the engine of a car (though I wouldn't take the analogy too far).
On top of the Kernel, various layers of software are placed to either form a desktop environment, a server environment, the X8 stock software or any other Android phone. (Like the differing body shapes of cars, though again I would not take the analogy past this loose interpretation! )
This software consists of things like drivers (enabling inputs such as the touchscreen to interact with the Kernel) through to your homescreen, through to Apps you download.
So to recap, the Kernel is the core of the phone's software and any collection of software on top of the kernel is known as a ROM! They are not entirely separate though and very much linked together, joined at the hip, so to speak.
The phone when you buy it comes with a Kernel and ROM, both created by Sony Ericsson from the software (code) that Google provides, they customise it the way they feel is best for the look they want from their phones.
If you want a different look or feel, a custom ROM (a ROM not created by SE but another team of people who create software, known as developers!) is a good option.
A custom Kernel goes that one step further and allows for greater tweaking on the part of the developers. Some ROMS require a custom kernel for parts of the ROM software to work properly.
Hope that helps
Hi nlao,
Welcome to the community.
Please take some time to Introduce Yourself and read FORUM RULES.
Hope you enjoy your stay here, and help others in the future.
Have you already learned what kernel is and its benefits?
For me : Kernel = BIOS and ROM is windows
Sent from my X8 running nAa and D_d piece of art called MiniCM9
CosminAdriaan said:
For me : Kernel = BIOS and ROM is windows
Click to expand...
Click to collapse
Whilst I like the analogy its not so accurate as Windows has a Kernel too! When using either windows or Linux on a PC you have this basic model:
BIOS --> Kernel --> Software Collection
A somewhat detailed but better written explanation than I could achieve can be found at History of GNU, Linux and Gnome, the relevant section has been pasted below:
"A fundamental misunderstanding is the relationship between Linux and operating systems. Linux is the low level code that interacts with and controls the hardware of the computer (whether it is an Intel 486, Pentium, Sun Sparc, or a Merced). This is the kernel of the operating system, providing routines to help applications talk to each other, allowing many applications to share the CPU at the same time, and managing the use of memory, allowing many different applications to run at the same time without interfering with other applications. Linus Torvalds wrote the first Linux kernel in 1991 and it continues to be actively developed today by Linus and a core team of international developers.
While the kernel is crucial, it is the larger suite of software that sits on top of the kernel that provides the functional operating system."
---------- Post added at 10:36 AM ---------- Previous post was at 10:32 AM ----------
deedii said:
Hi nlao,
Welcome to the community.
Please take some time to Introduce Yourself and read FORUM RULES.
Hope you enjoy your stay here, and help others in the future.
Have you already learned what kernel is and its benefits?
Click to expand...
Click to collapse
Hi deedii, thanks for the Hi! I have posted a little hi message! I have been using Linux for years and have played about with custom kernels for my PC but am new to Android hacking as it has its own nuances and is different to something like Debian!
I got now What is the kernel mean. thanks to all of u for ur replies.
there's so many ROM that i can't flsh it on my phone due to kernel and i think to flash kernel u have to unlock bootloader. and manufacture of my phone doesn't support unlock coz will make a hard brick . for instance i want to flash prime hd8 i tried but it coz a soft brick>>>>>???? what to do
nlao said:
Hi deedii, thanks for the Hi! I have posted a little hi message! I have been using Linux for years and have played about with custom kernels for my PC but am new to Android hacking as it has its own nuances and is different to something like Debian!
Click to expand...
Click to collapse
what flavor do you use dude?
Related
XDA has a wealth of info, but it does seem to assume that you are already pretty knowledgeable about many of the subjects. I'm brand new to this. I've been reading a lot, but still feel like I'm missing some basics. One question I can't seem to find an answer to is: What's the difference between a Kernel and a ROM? TIA for educating me
Espaa Valorum said:
XDA has a wealth of info, but it does seem to assume that you are already pretty knowledgeable about many of the subjects. I'm brand new to this. I've been reading a lot, but still feel like I'm missing some basics. One question I can't seem to find an answer to is: What's the difference between a Kernel and a ROM? TIA for educating me
Click to expand...
Click to collapse
A ROM is a collection of all your services, phone, sms, bluetooth, applications etc. bundled in a flashable zip or sometimes odin flashable packages. Think of it as a customized operating system. Which it is. Some are themed, some are not.
One thing that every ROM has included is a kernel. The kernel is the interface between your gui (You basically) and the hardware of the phone. The "brains" as it were. When you touch a widget (or whatever) on your screen and something cool happens it's because said widget passed a request for action and the kernel tells the hardware involved to get busy.
Oversimplified, but I hope it clarifies some.
It's not the greatest metaphor, but a ROM is Windows, and a Kernel is your BIOS.
MikeyMike01 said:
It's not the greatest metaphor, but a ROM is Windows, and a Kernel is your BIOS.
Click to expand...
Click to collapse
heading in the right direction but a bit off.
The kernel is the operating system.
The rom is a collection of software that includes user gui and some of the software for hardware to operating system interface.
Windows is actually both a kernel and user gui.
A bios is nether - usually bios is just hardware firmware - but sometimes contain a few other things as well.
The best example from a pc would be a linux distro such as ubuntu - the desktop environment gui ubuntu/gnome would be the " rom " and actual linux operating system running underneath is the kernel.
Alright, thanks for the explanations, it is a little clearer now.
When i got my phone i did the OTA update to JH7, rooted, installed Clockwork and did a ROM backup. So i have that backup saved. I want to try some other tweaks and such that i see mentioned around here all the time, but i wanted to make sure i understood the various pieces before i start messing with it all any further. So having the ROM backup, i should be always be able to get back to the state of the phone at that point right? (I understand it does not include pictures and messages and such.)
I guess what i haven't been able to find is a newbie guide that explains how to start at stock, what steps to take, what to actually do with the backup, how to restore etc. So i'm trying to learn. Thanks for the replies, it helps!
No. going back that way will not always work.
Make sure you can get into download mode, recovery mode, and that your computer is recognizing your device.
If you are flashing roms, at some point you will need odin so this is essential that you can get that to recognize your device in download mode to flash back to stock when something goes awry.
Sent telepathically using vulcan mind meld app.
I was able to get into recovery mode. I did the rooting through an update.zip. My computer also sees my device fine. I used ADB to communicate with it (and remove the market restriction.) I'm on a Linux box, and it seems that Odin is a Win app?
Technically windows has a kernel too, most people just don't talk about it.
Hence the ROM being the whole package as mentioned above is a good metaphor
Sent from my SAMSUNG-SGH-I897 using XDA App
More kernely details
I hate to revive an old thread, but this one is exactly on a topic I am currently researching. Being a noob I have read a lot over the past couple of weeks but am still a little confused about this whole kernel thing.
I know what the kernel does. What confuses me is that I have seen several references (including in this thread) that a ROM will always include a kernel. If that is the case, why is it that some ROMS state "does not come with a kernel" and ask you to flash the "kernel of your choice".
With this in mind I would like to know:
-How can I tell what kernel I am running? Is it the "build number"?
-Since the kernel does not present anything the user actually sees, how could you possibly choose a kernel and like one over the other?
Thanks!
think of it this way...
the rom is a car (the whole thing)
the kernel is the engine (engines have performance options or economy options)
the build (eg 2.1 /2.1 /2.2.1 or 2.3.3 is like the model of car shape, options ect)
the theme is the interior and exterior options. (the looks)
add-on zips such as dialers/battery mods are like aftermarket accessories.
- copyright tristyn russelo 2011
Click to expand...
Click to collapse
to tell what kernel you are on;
menu button > settings >about phone > kernel
to know about each kernel go to the XDA > Captivate > Development area look for [Kernel] at the beginning of each thread. look at the options, read the options, research the options
also there IS visible features of the kernel if it has ClockworkMod Recovery built into it. with this you dont need ROM manager or the update.zip method of Clockwork Mod Recovery (aka CWM)
see the CWM onix kernel idiot guide in my sig.
and check out the XDA wiki for ClockworkMod Recovery. "i started it"
also check out the http://Capfaq.com
TRusselo said:
think of it this way...
the rom is a car (the whole thing)
the kernel is the engine (engines have performance options or economy options)
the build (eg 2.1 /2.1 /2.2.1 or 2.3.3 is like the model of car shape, options ect)
the theme is the interior and exterior options. (the looks)
add-on zips such as dialers/battery mods are like aftermarket accessories.
- copyright tristyn russelo 2011
Click to expand...
Click to collapse
Click to expand...
Click to collapse
That's a great explanation, thanks!
Thanks, Tristyn for that analogy. So my question is, can you just use a "Kernel"? By Tristyn's analogy, it appears that just the kernel is useless as you can't drive a car that only includes the engine (ie: you need the wheels and the frame, etc.).
What? if you flash just a kernel it doesn't delete the framework? It's just like swapping the engine in a car.
Yes if you SOMEHOW only had a kernel installed you get a boot error and it would probably give you the "phone...!....pc" screen.
i added that analogy to my new users guide the other day but expanded...
- "A ROM" is like "a car" nothing in specific but a body, wheels, engine, and paint. a general standard vehicle.
- "Each ROM" or each developer is like an auto maker. Each has their own style, options, focus and customer base. Some are luxury, others economy and some are fully loaded! Some are fully packed and heavy and others are base models and very light. You get to get to choose what you like or need, and for once "price is no object" (donating is appreciated) But you almost always get a whole car!
- "Framework" or "Build" - is like the frame of a car, you cant put SUV parts in a Honda. It just won't work unless you rebuild from scratch (and if you can do that, you would laugh at this analogy!) Parts / Kernels / Mods must be compatible with that framework and that framework must be compatible with your phone.
- "Rooting" or getting a "rooted ROM" is like getting the keys and permission to change ANYTHING in your car! But you dont have a warranty anymore!
- "The Kernel" is like the engine and power systems, it is the "software" engine, it does work and ties all the components together. And engines can be upgraded and tuned up for performance or down for economy!
- The theme is like the paint job. pure looks and enjoyment!
- Other dialers, meta-morphs, mods ect are all after market fun changes, once again only looks not usually any more function.
- The launcher (no rooting or romming needed) is alot like your interior, its the seat you sit in and the controls you touch 75% of the time, until you dig through your glove box or fuse box (back to rom)
Click to expand...
Click to collapse
TRusselo said:
i added that analogy to my new users guide the other day but expanded...
Click to expand...
Click to collapse
Haha very nice Tru! I love it
Sorry to ask repeative questions of Kernel & m0d,
but i failed to understand few Things
1. Whenever we are installing a m0d {like cyanogen, oxygen, etc} iS iT necessary to install another kernel ??? oR can we just run on Stock kernel
2. if we install another kernel can we get back our stock kernel ?
3. Do m0ds come pre-installed wid kernel or do we need to install them seprately.
4. h0w would i know that which kernel is made for which rom ???
If you go to CyanogenMod 7 for Captivate Q&A ( gotta love the search function ) and read the devs OP pretty much all your questions will be answered, infact any rom you care to flash if you read the devs OP they will spell out what you are asking for.
Custom ROM and then a custom Kernel. Is it possible?
Well, I'm a bit confused. Consider this:
I flash the phone with CM7(say). Here I'm assuming that CyanogenMod comes with its own kernel. My question is: Can I flash a custom kernel on top of this setup? and what difference does it make?
One can also think the other way round. I have flashed my phone with a custom kernel. Successively I flash CM7 on to my phone. What happens then? Is the original custom kernel wiped out to be over-written by CM7 kernel? What can be done to keep it intact? Please people solve this dilemma...
saurabh.khare1000 said:
Well, I'm a bit confused. Consider this:
I flash the phone with CM7(say). Here I'm assuming that CyanogenMod comes with its own kernel. My question is: Can I flash a custom kernel on top of this setup? and what difference does it make?
One can also think the other way round. I have flashed my phone with a custom kernel. Successively I flash CM7 on to my phone. What happens then? Is the original custom kernel wiped out to be over-written by CM7 kernel? What can be done to keep it intact? Please people solve this dilemma...
Click to expand...
Click to collapse
It's not really a dilemma. You can flash any appropriate kernel that you want. Flashing CM7 again will give you the CM7 kernel. Simply reflash your other kernel.
My post here explains why you may want to switch
http://forum.xda-developers.com/showthread.php?p=26110276
Swyped from my ICS Samsung Captivate
Hello all.
This is my very first post here. So, first of all I want to say many thanks to all developers/members on this forum. Big thanks for sharing knowledge, for doing great investigations and so on.
And right now... questions...
I recently bought Sony Xperia X8. This is my first Android device (I helped my friends with these ones, but just to reflash using manufacturer steps, or configuring devices, not customizing) with which I can do anything I want. I read a lot information about this device and need to clear some things... So, lets start:
(Just for note: I 'm an experienced linux programmer/developer/user, so I have a lot of experience and need just some specific things)
1. What is bootloader in meaning of specific device. Is this something like plain Grub, but just hardware-related? Or it is something like BIOS in PCs meaning?
2. What does ROM file contains? Is that just list of packages and platform-related things excluding kernel, loader and etc, or ROMs contains kernel also? I saw post where someone said "I use xxxx kernel with xxxx ROM", and another post where someone said "This ROM contains xxx kernel". What is the right one?
3. I saw three types of flashes around the forum: "ftf", "sin" and "img". What is the difference between them? Which ones are better (prefferable)?
4. All ROMs which I tried have same issue: Reboot while using ad-hoc wi-fi and activating lockscreen (trying wipes, formating, flash from stock). Can someone, who used stable version of "Cyanogen Mod 7.1.0 stable" confirm is this bug fixed here or not? WiFi is very important for me, especially ad-hoc. (I just want to wait some time 2~3 weeks to see if device working fine and no any defects occur, before I void my warranty by unlocking bootloader)
5. I saw a lot of reviews for different ROMs so I can't just choose one... Maybe someone will suggest me some stable ROM with 100% working wifi based on 2.2 (or 2.3)
Any comments/advices/explanations are greatly appreciated.
P.S. Sorry me for my bad english, I'm originally from Ukraine.
hello..
i'm newbie too in this forum,maybe you must search all answer of your qustion in general forum not in subforum here or try to go to cyanogen forum.
just sugestion,i sugest you to use froyobread rom or froyopro i (2.2.x both) if you want wifi work good in your device ( cause there any wifi bugs in other rom's,actually in 2.3.x rom).
The bootloader it can be locked again
Sent from my X8 using XDA Premium App
dotsen9 said:
The bootloader it can be locked again
Click to expand...
Click to collapse
Yes, I know, but if subject will die during using custom ROM because of some factory defects (believe me, today quality of products is very low level, especially here, in Ukraine) can be situation when I will not be able to return to stock firmware. Anyway, thanks... and still waiting for some explanations.
zieaditya said:
hello..
i'm newbie too in this forum,maybe you must search all answer of your qustion in general forum not in subforum here or try to go to cyanogen forum.
just sugestion,i sugest you to use froyobread rom or froyopro i (2.2.x both) if you want wifi work good in your device ( cause there any wifi bugs in other rom's,actually in 2.3.x rom).
Click to expand...
Click to collapse
Hmm, I have same issues with the wifi even on 2.2 froyo pro, floyo and others, so I thinking about custom kernels, just need to someone confirm what it will solve problem.
By the way, I got questions which I posted here during search forum, so there aren't answers which I need. I really need some technical details about that. Maybe I will be able to help developers with some improvements. Just need to know more about android (coz I have a lot of linux experience - building linux from scratch, optimization, developing, debugging, etc)
Thanks anyway for your attention.
P.S. Offtop... What do I need to do so moderators will permit me to post in <5 min? Coz now working a restrictions for newbies.
You need at least 10 posts here on forum...,;-)
Sent from my X8 using XDA App
1. The bootloader is a special software, that is loaded by the firmware and loads the kernel itself.
This doesn´t only exists on Android, every OS has a bootloader.
2. The ROMs and the kernels are different to flash, the only ROm that "includes" a kernel is the official Android 2.1, which can be flashed with flashtool.
What flashtool is, and what you can do with it, can be read in the X8 FAQ-thread.
3. have a look at the FAQ-thread again....you will find something.
4. GingerDX should have working ad-hoc Wi-Fi, as this is also inportant for DX, especially on WEP.
CM 7.1.0 is still under development, as it´s based on the FXP ROM.
5.I´d suggest you GingerDX+LinuxDX, this combination is smooth like a baby´s ass and as fast as hell!
And everything is working!(Well, maybe there are some bugs, but I´m using this for a few months now and I didn´t found anything that does absolutely NOT work.
codfreak said:
1. The bootloader is a special software, that is loaded by the firmware and loads the kernel itself.
This doesn´t only exists on Android, every OS has a bootloader.
Click to expand...
Click to collapse
I know what is bootloader. I asked is the bootloader in the current context something like software thing (GRUB, LILO, NTLDR, bootrecord if you want) OR it is something like hardware-specific BIOS alternative? This is the question.
codfreak said:
2. The ROMs and the kernels are different to flash, the only ROm that "includes" a kernel is the official Android 2.1, which can be flashed with flashtool.
What flashtool is, and what you can do with it, can be read in the X8 FAQ-thread.
Click to expand...
Click to collapse
What is flashtool I know too. So all ROMs, excepting Stock does not include kernel. Clearly, thanks.
codfreak said:
4. GingerDX should have working ad-hoc Wi-Fi, as this is also inportant for DX, especially on WEP.
CM 7.1.0 is still under development, as it´s based on the FXP ROM.
5.I´d suggest you GingerDX+LinuxDX, this combination is smooth like a baby´s ass and as fast as hell!
And everything is working!(Well, maybe there are some bugs, but I´m using this for a few months now and I didn´t found anything that does absolutely NOT work.
Click to expand...
Click to collapse
Will give it a try... Thanks!
You are a linux programmer?guys we might have a new developer in few months
Everything you need you can ask me via PM
Hi
I`m also have WiFi problems with Froyo Pro v1 and v1.1.
Froyobread 23b works fine.
Looking for a 2.2 rom still in developmen with a working WiFi!!!!
Please!!!
any answer?????'
Use the search button before you make a thread!
i haven't found anything about the x8
lucasiumej said:
i haven't found anything about the x8
Click to expand...
Click to collapse
And chances are that you won't find a tutorial about how to cook a ROM for the X8.
In theory you have all the information you're possibly looking for around in the General Android Forums section as well as in the Chef section.
To build from scratch you need the Android SDK/NDK, the Android source code (you're most likely looking for the CM7 git sources), a kitchen, maybe Eclipse (the Integrated Development Environment) and a whole lot of coding experience to tackle the task. EDIT: You also need: A computer featuring a CPU supporting 64-Bit, a 64-Bit Linux distro (i.e. Ubuntu or Linux Mint in their x86_64 edition) and AT LEAST 8GB RAM to successfully compile Gingerbread/ICS.
The easier task might be to mod a existing ROM (of course ONLY with the express permission of the author of the ROM as well as of all other developers whose modules you are using), but even this requires a solid knowledge about what you're doing.
Oh, and you also need a phone where you can test out your ROM creation (just because it works in the SDK Emulator does not mean it works on the real device), and you need to be able pull your phone back out of "bad flash" in case your ROM or Kernel creation bricked your phone.
In short, the answer to your question is nothing more than reading up on lots of stuff and adapting things to the specifics of the X8 and porting a whole lot of stuff to make it work with the X8 (you know, the vanilla AOSP sources don't come with X8 drivers to support camera and so on).
As B.Jay said You need a looooooooooooooooooot of patience because every time something will go wrong. Also you must know how to analyze logs from terminal. It's really complicated stuff.
eagleeyetom said:
You need a looooooooooooooooooot of patience because every time something will go wrong.
Click to expand...
Click to collapse
LOL...
Yeah, welcome to the fabulous world of open source software where there are always surprises upon invoking "make"
you have to become einstien of android if you want to make a rom!! lol
freshy wanna cook a rom..??
yeah U have learn from modify rom first
and when u aready know what the stuff very well
that is u r ready...
Or you could use ROMMODGEN.com
Sent from my X8 using xda premium
Why do you need 8 Gb of ram?
I was able to compile CM7 with 1,5 GB of RAM on virtual machine. It was compiling for about 4 hours + time to fix errors 8GB of RAM is needed to compile ICS, because it's a beast There's one rule - more RAM, quicker result for magic "make" command
Hi guys, I've come to the conclusion no one can answer my previous thread, so I'm starting a new one, asking a different question.
Can our phones just run stock Android? I mean, does Android support all our drivers? If it does, I may be tempted to just use that instead.
thanks.
YES .... BUT!
The answer is yes, BUT, I suggest you start reading about what Android actually is and the workings of this OS.
Then you will discover the possibilities yourself and within no time have the phone just the way you like it
If you would have read the forum you would have already had an answer to your own question.
Think before you act my friend.
There are AOSP and AOSP based roms for our device, whatever you want. You will find out what this means!
On this forum some useful threads:
http://forum.xda-developers.com/showthread.php?t=2232085
When I google for "What is Android custom rom AOSP" I get these links for you to start of with, do not forget, google is your friend in your search for answers
http://highonandroid.com/android-roms/what-is-aosp/
http://android.stackexchange.com/qu...ifference-between-an-aosp-rom-and-a-stock-rom
http://www.androidpolice.com/2010/05/01/custom-roms-for-android-explained-and-why-you-want-them/
Thanks Robin>Hood!
I neglected to mention that my phone is actually a customized China-only Xperia SP running on China Mobile's proprietary 4G network. It is called the Xperia SP M35t, and with the exception of more ROM (16 vs. 8)? and I'm assuming a chip that allows it to run to the LTE variant network.
Obviously I'm hoping that it would have no bearing on this conversation, and an AOSP ROM would be able to have all required drivers to run my phone properly. That I guess is the crux of my question.
I believe the Chinese Xperia SP is unique, You can't run other Android version besides the stock one.
Thanks cachanilla86! I guess I'll have to wait till a ROM comes out. Thanks!
MCChang said:
Thanks cachanilla86! I guess I'll have to wait till a ROM comes out. Thanks!
Click to expand...
Click to collapse
It depends what you mean by stock Android. You can't just download AOSP, compile it and flash it.
You CAN download Android source code from CodeAurora, compile that with a few minor tweaks and it will work (see my recaf project). I think it even has support for the Chinese LTE variant (I read something about it in code comments) but I didn't look at it as it didn't interest me, I obviously have no way to test it.
Thanks adfad666. I don't think I'm quite ready for any programming, minor tweak or otherwise. I'll just wait for someone to create a ROM for the Chinese Xperia.
Good Afternoon, people.
I am brazilian and I have a smartphone that did not get into US and European market. It's name is "Motorola D3" and the number associate to it is "XT920".
Motorola Brazil were suposed to provide de newest rom for this device (marketing promissess). It took they almost 1 year to launch the Android Kitkat version 4.4.2.
The problem is: We want the Cyanogenmod in our device and all the newest ROM's.
That been said, I start to study to try yo port or Build a AOSP ROM to XT920 and, therefore, a CM11.
No threads on "how to port / build" a rom for a New device went trhough this problem. This device runs as a Mediatek MTK6577. I've seen that the kernel for this processor was released, but I don't know how to handle the kernel with the device and ROM properly.
Another doubt is: what is the difference between port and build a ROM? I've seen videos of porting and building and it is not clear to me.
I have reached the point where I have to download the drivers, but, in the tutorial the person was dealing with a NEXUS, wich is much easier to build, since it have a native android support.
Anyway, I want to keep this project going, and I really need some help with this questions.
Thankyou
digo_santista said:
This device runs as a Mediatek MTK6577.
Click to expand...
Click to collapse
You're screwed. MTK devices are extremely nightmarish to work with. Their kernel source is a mess and the platform source is an even bigger mess.
Even people who have had access to a complete OEM source code tree for an MT6589 device didn't succeed in getting the hacks to play nice with an AOSP source tree.
Android One has helped somewhat with devices that are released as part of the One program, but non-One MTK devices are still a nightmare.
The process of doing an AOSP bringup for a new device isn't particularly well defined because it is different for every device in existence. The only way to learn is by doing.
It helps a lot if a device with a similar chipset to yours is supported by whatever project you're trying to work with - for example most mid-to-high-end Qualcomm chipsets are not very difficult to work with. But MTK devices were nearly impossible to support with AOSP-derivative projects prior to One, and even after One, it seems like only Android One devices are "clean" enough to leverage Google's improvements to MTK support.
:/ should I waste more time or just drop it?
Entropy512 said:
You're screwed.
Click to expand...
Click to collapse
What should I do? I just quit without trying? I understand that this is a huge problem. But, if I decide to take the chalenge, is there a chance to succeed?
I am trying to figure this out and I didn't found an answer to this question: can I use the kernel that is packed with my stock ROM (provided by motorola) to build or port a CM11 ROM?
Sorry to bother, but I is really keeping me up at night
Regards,
Cassio Rodrigo