Simple question: Does a custom kernel need to compatible with the ROM or the phone? - General Questions and Answers

Just want to know, when selecting a custom kernel, do I have to check if the custom ROM supports the kernel or if the phone model supports the kernel or if I have to check for both.
I dont know if this is a dumb question or not..but pls help..am noob

A phone's kernel - what is the go between of phone's ROM and phone's hardware - is a Linux port, a phone's ROM is Android OS customized by manufacturer.
The kernel provides the basic drivers what are used to communicate to phone's hardware. The ROM is basically an interpreter between the Android ( user ) and the kernel.
So the ROM must match kernel.

jwoegerbauer said:
A phone's kernel - what is the go between of phone's ROM and phone's hardware - is a Linux port, a phone's ROM is Android OS customized by manufacturer.
The kernel provides the basic drivers what are used to communicate to phone's hardware. The ROM is basically an interpreter between the Android ( user ) and the kernel.
So the ROM must match kernel.
Click to expand...
Click to collapse
Thanks alot!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Related

Could Virtualization Be The Solution To Android Rom Porting?

I think that a Virtualization Layer (Just a translater type thing) could be used so instead of modding the entire rom you could just mod the layer's code to point to whatever command the kernel would use. It would only work on newer devices but could it work???

[DICTIONARY] Android Terminology (AS SPECIFIC AS POSSIBLE ALREADY)

Hi guys, xda-developers have a whole lot of newbies at Android, and when they come across ROMs or something, they have terms that they don't understand, so I make a thread for them to understand the terms. Please delete this if there is one already, and please correct me if I'm wrong, also help me add more terms, you guys will get a thanks and a shoutout in the post. Here I use the term "device" for all Android phones and tablets.
General (incl. Linux, Android, etc) terms:
- Odexed: A ROM that all the system apks has an .odex file that contains stuff about the apk. It is used to save some storage in most of stocks.
- Deodexed: A ROM that all the system apks has their own stuff in their own apk, not reliabling on the .odex files to save storage.
- Wiping: Self-explanatory. Every time you flash a ROM you need to wipe away all the stuff of the old things, and bringing the modified stuff back to normal and then you can replace it (if not it will conflict and stucks)
- Xposed: A framework for modding without the hassle of editing any apks. Uses modules to mod. Kinda cool.
- Terminal: The Terminal of Linux. You can say it's like Windows' Command Prompt. You guys can reach the terminal shell within Android with Terminal Emulator (Play Store please, it's free), it still uses Linux's commands, it's also used by Complete Linux Installer to host a VNC server and run Linux distros on it, and you guys can also install BusyBox to extend the Android Terminal shell as the Android Terminal shell is not the same as Linux's, so BusyBox to the help! Unleash your inner geek!
- BusyBox: You guys gotta know this, right? It's a executable contains most Linux/Unix commands, ie. In your Wi-Fi router, there is a very small 3MB flash, and there are Linux/Unix commands in it. They uses BusyBox to narrow down the size as BusyBox is very small in size but contains most Linux/Unix commands. And we also can install single packages, instead of using the whole thing.
- Recovery: A "secret" menu thingy, reached by holding a combination. It's where you can do basic crap like factory resetting your phone, applying update.zip (OTA updates) (stock), in custom recoveries, you can do a lot more stuff.
- Flash: Writing an official Android firmware (kernel, system, baseband, etc. of stock files) to your device. We have ODIN for Samsung, Flashtool for Sony (that's all I know)
- ROM: The Android firmware in your device.
- Radio: The radio firmware, you need it to connect to Internet.
- Kernel: The core of every OS, and here, we're based on Linux. And if your bootloader is unlocked, you can replace it. Simple.
- Soft-brick a.k.a Bootloop: You got stuck in the logo or it keeps looping the boot sequence.
- Bootloader: What Android (and every OS) uses to make the core reads and loads the OS.
- Unlocked/Locked Bootloader: The state of the bootloader. Unlock the bootloader makes the Android kernel replaceable, and make the core reads it as a valid Android kernel. Locked bootloader only reads the stock kernel as valid to boot. Usually unlocking the bootloader voids your warranty.
- Root: The work to gain full control. You guys know Linux, it come with root, but on Android, Google disabled it, so we gotta enable it, and use an app like SuperSU to control and manages it. In the old days, rooting usually needs to unlock the bootloader, so you gonna void the warranty of the phone. But now, we can root with out unlocking the bootloader, which we can keep the warranty!
- Hard-brick: Basically, your device becomes a battery-powered paper holder. (And it CANNOT be saved unless: you buy a new phone or you go and change the mainboard)
Recovery-related terms:
- Stock Recovery: Just too bullcrap, only usable for stock OTA updates (apply update.zip) and factory resetting your devices.
- Custom Recovery: A customized recovery (self-explanatory) and it can do more than the stock recovery, like installing ROMs, flash stuff, etc. Two well-known custom recoveries are ClockworkMod and TeamWin Recovery Project. There are less-known variants of them like PhilZ, ClockworkMod Touch, due to their compatibility to less phones.
- ClockworkMod Recovery (CWM, or CWM Recovery for short): A custom recovery for Android devices. Not just factory resetting your devices, it can also clear cache, do crap in it and install custom ROMs
- TeamWin Recovery Project (TWRP or TWRP Recovery for short): Same as CWM but more user-friendly with touch controls, and also can flash more than one zip at once, and other stuff. But we have CWM Touch to compete with TWRP in the user-friendly-ness!
Sony-related terms:
- TA Partition: Trim Area Partition, where Sony's DRM keys for Sony's patented stuff to run. When you unlock your bootloader, the TA Partition will be erased. You will lose Sony's technologies like Bravia Engine,... if the TA Partition is erased.
HTC-related terms:
- S-ON and S-OFF: Basically, it's a extra protection layer staying under the bootloader. S-OFF means you can fully operates the device, like a simple unlock of the bootloader. But in HTC, to have full control, you have to S-OFF too, and I remember it also voids your warranty.
Samsung-related terms:
- Knox: Samsung's new protection like HTC's S-ON, it will become 0x1 ("Custom" state) if you flash a custom ROM. When it becomes 0x1, your warranty is voided.
- Flash counter: If you flash 1 custom ROM or a ROM with ODIN, it will becomes 1. And as soon as it becomes 1, you will trip Knox, and your warranty is voided. You can reset this with a Gingerbread ROM (official, everything included).
ROM-related terms:
- Stock ROMs: The Android firmware shipped with your phone, full of bloatware (in my opinion) and better be replaced with a custom one.
- Custom ROM: An Android firmware has been changed and modded by developers. Usually based on these three kernels:
+ Stock (Normal Kernel)
+ CyanogenMod (CyanogenMod kernel for modding)
+ AOKP (AOKP kernel I remember)
- AOSP: Android Open Source Project, the source code of Android released by Google Inc. and most major aftermarket ROMs based on it. (also stocks too, no AOSP, no Android)
- CyanogenMod: An aftermarket Android firmware, official releases based on AOSP, very customisable, very smooth and it's better than stock ROMs to use daily because of the smoothness of AOSP.
- AOKP: Android Open Kang Project, also an aftermarket Android firmware, has a lot of features (even more than CM) but the small bit of lag due to the features makes it not very comfortable to use daily.
- ParanoidAndroid: Again, another aftermarket firmware, like AOKP, has a lot of features and other crap. And it has a cool thing: Pie Control. Basically navbar in a pie chart thingy.
*ALL THOSE ROMS ABOVE ALL BASED ON CYANOGENMOD, EXCEPT FOR ITSELF, WHICH BASES ON AOSP*
CyanogenMod (CM for short)-related terms:
- Theme Engine: A theme engine of CM, presents since CM9 (I remember - Trebuchet is CM's own launcher since then so yeah) which applies custom themes, they themes from the icons to the status bar icons. Pretty freaking sick. I use stock in my Acro HD, and CM in my Arc S, and I miss that kind of modding the theme of my phone.
ParanoidAndroid (PA for short)-related terms:
- Pie Control: As explained above, a navbar in a pie chart thingy, which helps a lot I mean. I used PA once, and that is sick. PA ROMs are cool. They have CM's features and some of their stuff. Sick as crap. So cool. Just full awesome.
Debug-related terms:
- ADB: Android Debug Bridge, a debug tool for developers to "hook" themselves up to the device. It can do a basic Android device can do: install, uninstall, take a logcat of the device, etc. Some commands:
+ adb devices: list the devices (under the serial) connected and recognized.
+ adb logcat: take a logcat of your device in realtime, press Ctrl+C to stop.
+ adb install: install Android APKs to your phone, adb uninstall is vice-versa.
+ adb push: copy a file to your device.
+ adb pull: take a file from your device and copy it to your PC.
+ fastboot flash (image): flash a kernel to your device.
+ fastboot boot (image): boot an image (usually for a recovery) without flashing it onto your phone, for backing up a fully stock ROM with stock recovery (mostly).
Okay. It's the end of it for now. Please press thanks if it helped you, and please add me stuff if I missed anything, also correct me if I'm wrong. Thanks! I love Android, and I always will.
NOTE: NO APPLE FANBOYS HERE PLEASE! REMEMBER, I LOVE ANDROID, AND I ALWAYS WILL
NOTE 2: TERMINAL AND BUSYBOX ARE LINUX'S TERMS, NOT ANDROID'S BUT THEY ARE RELATED SO IT'S STILL BEING LISTED HERE AS IT'S STILL PART OF ANDROID ANYWAY
Sent and edited from my Acro HD and my Arc S via XDA Premium 4 app, and my PC through Chrome.
ChiefDoraemon said:
Hi guys, xda-developers have a whole lot of newbies at Android, and when they come across ROMs or something, they have terms that they don't understand, so I make a thread for them to understand the terms. Please delete this if there is one already, and please correct me if I'm wrong, also help me add more terms, you guys will get a thanks and a shoutout in the post. Here I use the term "device" for all Android phones and tablets.
General:
- ROM: The Android firmware in your device.
- Radio: The radio firmware, you need it to connect to Internet.
- Soft-brick a.k.a Bootloop: You got stuck in the logo or it keeps looping the boot sequence.
- Bootloader: What Android (and every OS) uses to make the core reads and loads the OS.
- Unlocked/Locked Bootloader: The state of the bootloader. Unlock the bootloader makes the Android kernel replaceable, and make the core reads it as a valid Android kernel. Locked bootloader only reads the stock kernel as valid to boot. Usually unlocking the bootloader voids your warranty.
- Hard-brick: Basically, your device becomes a battery-powered paper holder.
HTC-specific stuff:
- S-ON and S-OFF: Basically, it's a extra protection layer staying under the bootloader. S-OFF means you can fully operates the device, like a simple unlock of the bootloader. But in HTC, to have full control, you have to S-OFF too, and I remember it also voids your warranty.
Samsung-specific stuff:
- Knox: Samsung's new protection like HTC's S-ON, it will become 0x1 ("Custom" state) if you flash a custom ROM. When it becomes 0x1, your warranty is voided.
- Flash counter: If you flash 1 custom ROM, it will becomes 1. And when it becomes 1, you will trip Knox, and your warranty is voided.
Okay. It's the end of it for now. Please press thanks if it helped you, and please add me stuff if I missed anything, also correct me if I'm wrong. Thanks!
Click to expand...
Click to collapse
I feel like something like this has to exist already. Granted I'm not on the lookout for it because these terms aren't foreign to me. Nevertheless, if something like this doesn't exist, I suppose it would be a good sticky to have somewhere on the forums so that people can have a quick glossary of jargon to access. I mean, yeah, people can just Google it too, but ya know... keeping people on the site is important n stuff.
Android Terminology
Thanks mate, way to go helping the noobies out. Even though I am familiar with these terms, its always a good refresher.:good:
This is still helpful, thanks!
Mithraeum said:
This is still helpful, thanks!
Click to expand...
Click to collapse
DvDev said:
Thanks mate, way to go helping the noobies out. Even though I am familiar with these terms, its always a good refresher.:good:
Click to expand...
Click to collapse
Thanks guys! Add more terms for me! Just helping the noobies folks!
Thanks for sharing this useful info.
Guys, please hit the thanks button instead of spamming the thread with thanks posts.
Great job
would be nice also to explain the
TWRP
Flashing
Recovery
Thanks a lot
alexmforero said:
Great job
would be nice also to explain the
TWRP
Flashing
Recovery
Thanks a lot
Click to expand...
Click to collapse
Sure! Adding it right now.

[GUIDE][NOOBS]All For Android👀 📱

Hey , Guys this Thread Is Specially Made for Noobs. With All Info For Android.
So , Let's Directly go to Topic
Firstly What Is Android?
• a robot with a human appearance.
•an open-source operating system used for smartphones and tablet computers which is based on Linux Os.
Source- Google
_____________________________
Version Of Android
Cupcake:
Android 1.5
Donut:
Android 1.6
Eclair:
Android 2.0
Android 2.1
Froyo:*(short for "frozen yogurt") & The Most successor Veraion
Android 2.2
Gingerbread:
Android 2.3
Honeycomb:
Android 3.0
Android 3.1
Android 3.2
Ice Cream Sandwich:
Android 4.0
Jelly Bean:
Android 4.1
Android 4.2
Android 4.3
KitKat:
Android 4.4
Lollipop:
Android 5.0
Android 5.1
Source-android.stackexchange
______________________________
What is Root?
★In Simple Word Rooting Means gives Read-Write[RW] permission on System Dictionary.★
Rooting*is the Android*equivalent of jailbreaking, a means of unlocking the operating system so you can install unapproved (by Google) apps, update the OS, replace the firmware, overclock (or underclock) the processor, customize just about anything, and so on.
Source- Google
______________________________
What is Recovery?
A combination of key presses (or instructions from a*command line) will boot your phone to recovery, where you can find tools to help repair (recover) your installation as well as install*official OS updates.
Source-Android A to Z
_____________________________
What is Bootloader?
•Every Android phone has a bootloader that instructs the operating system kernel to boot normally. But you need to understand one thing here that as Android OS is an open source OS and is available on a variety of different hardware, every manufacturer has their own version of bootloader specific for the hardware present in it’s environment.
Source-addictivetips.com
____________________________
★Advance Section★
1. Bootloop - Bootloop means your phone doesn't but up right, it's just starting and starting and nothing happens, or it's starting and shutting down and starting again. It just means your phone makes a loop while booting.
2. Brick - Brick means your phone can't boot up and you can only recover it with for example flash the stock rom. But there are different bricks for example soft bricks (for example bootloops) and hard bricks (for example doing and over the air=ota update when bootloader is unlocked). There are some other bricks and examples as well.
There Are Two Types of Bricks
1.Soft Brick - you can still turn your phone on but it doesnt really start (bootloop i think is a kind of soft brick. )
this kind of brick can be fixed through softwares like flashtool.
2. Hard Brick - you can't turn your phone on and it doesnt really start, you don't get any response from it.
Click to expand...
Click to collapse
3. Fastboot - Fastboot mode is used to flash a kernel if the bootloader is unlocked. With fastboot you flash a boot.img for your device, for example a kernel for a specific rom
Source - from( XDA)
_____________________________
What is Nandroid?
the type of permanent storage memory that your device uses, and Android. A*Nandroid*backup is a de-facto (by the hacking community) standard directory structure for backing up a perfect mirror image of your Android device.
Source - Google
_____________________________
What is Kernel ?
is a “deeper” line of code that rests beneath the surface, so to speak. It tells the software how to interact with the hardware.
____________________________
What is Custom Rom?
A*custom ROM replaces your device's Android operating system — normally stored in read-only memory — with a new version of the Android operating system.
Some Famous Custom Roms Are
°Cyanogen Mod
° Pac-Man
etc...
___________________________
What is Flashing?
Flashing is a process in which system's update Any Kind of files like Apps , System file etc...
___________________________
This Things Might Confused Many People But for Development of Android.
You Have To Totally Know This Types Of Things.
Good info for noobs:thumbup:
suresh.anthati said:
Good info for noobs:thumbup:
Click to expand...
Click to collapse
Thanks Dude

[Completed] Why Android OS is limited to device model number?

In PC,laptops there is one copy of OS(windows, linux) which work on different company, model,etc. devices
So why there in Android OS there is different ROM for every device and ROM is limited to device model number
praveensingh569 said:
In PC,laptops there is one copy of OS(windows, linux) which work on different company, model,etc. devices
So why there in Android OS there is different ROM for every device and ROM is limited to device model number
Click to expand...
Click to collapse
Hi,
In a nutshell: each OEM use different frameworks, systemUI,... (+ closed-sources) devices have different kernels, drivers, libs, modules...

I'm just curious I don't know much about phones in general, just a question

Why isn't it as easy as on the pc ? on pc you just download the OS you want , you make it bootable with a program like Rufus (in a USB drive) you plug the USB on the pc/laptop, you follow the instructions and done. on smartphones/ tablets its too complicated you have to download a custom recovery , and why every rom is not compatible with every smartphone/ tablet?
andreas_xs said:
Why isn't it as easy as on the pc ? on pc you just download the OS you want , you make it bootable with a program like Rufus (in a USB drive) you plug the USB on the pc/laptop, you follow the instructions and done. on smartphones/ tablets its too complicated you have to download a custom recovery , and why every rom is not compatible with every smartphone/ tablet?
Click to expand...
Click to collapse
Installing custom roms and custom recovery maybe complicated at first but once u get the hang of it it wouldn't be as complicated anymore
As with the Android ROM it consists not only of the operating system software ( bootloader, Linux kernel & Android Framework ) but also of a wealth of drivers & APIs, what are tailored to Android device's hardware and its interfaces. Hence it should be clear that not every available Android ROM will flawlessly run on every Android device: thousands of different brands and models of Android devices are on the market, all have different features.
Installing an incompatible ROM, in the best case, makes components of your Android device unavailable ( they are simply not working ), in the worst case, you might "softbrick" the Android device ( it won't even start up ).

Categories

Resources