Develop Bugs

[Q] How Does the Android OS Work?

Disclaimer: I am only a flasher. I do, however, contribute to the forums, donate to devs and also use the paid version of good apps.
My question is: How does Android work on our phones?
You have hardware (HTC Incredible); you have a carrier (Verizon, in my case); you have an OS (Android, obviously); you have a radio; you have a ROM; you have a kernel; you have themes, you have skins and you have apps. How do all these pieces interact? Just curious.

This is a really good question that should be answered in laymen's terms. I'm surprised it hasn't been answered yet.

I also thought it would have been answered by now. However, I think the developers (who would be the best folks to answer this question) are busy working with the Gingerbread source code to build new ROMs for us.
This is what I have figured out so far but I'm not sure if my analysis is correct:
After selecting your hardware and carrier, the OS is the most important element. Most of us are currently on Froyo (2.2). I have seen some screen shots showing the OS version to be "2.2.1" but I am not sure why. Google (I think) has released the source code for Gingerbread (2.3) and the developers ("devs") are hard at work producing new ROMs as I post this.
I gather that it is best to stay away from trying out different radios ("basebands"). Most of us are using 2.15.00.07.28.
I think the ROM takes the OS and re-works the user interface by adding, removing and changing the various screens and "features" of the OS. For example: the ROM can be written to take out the stock music player and substitute a music player that the ROM developer prefers. I think this is called "baking in an app". I believe the ROM developer can also create an overall "look and feel" that can be quite different from the stock OS. For instance, the ROM can be "colored" in black and red (rather than the stock green) and the stock font can be changed to something the developer prefers. In other words, the ROM is what you see and use on a daily basis.
Now this is where things get a little fuzzy: the kernel. I think this is kind of a behind the scenes element that governs the performance of a ROM. It greatly affects things like battery life, time to charge the battery and the "speed" of the phone. The kernel is where the phone can be "over-clocked" and "under-volted" should you want to do those things. I gather that once you select a ROM, you can try different kernels without changing what the various screens look like on the phone. I believe this is the way most people do it (pick a ROM and try different kernels with it). I don't think the other way really works (pick a kernel and try different ROMs with the kernel).
Next comes themes and skins which really only affect what you see on the various screens without do anything about battery life or the speed of the phone. I haven't played with these much.
Finally, I forgot to put WALLPAPER on the list in the original post. I believe this only appears as a background image on the home screens.
If any reader sees errors in my layman's analysis, please, by all means jump in and correct me. Per my disclaimer in Post #1, I am just an ordinary user and this analysis could be flawed or incorrect in whole or in part.

Everytime I try to answer a question like this, I get too complex about it and leave more questions than answers. Then someone comes along and says "It's like Windows or Linux or MacOS on a PC", and that's that. Well they're right. Those OS's tell the PC's that they are PC's and essentially all OS's do the same things.
Here's my simplified new list:
1) Hardware on phone :: meaningless without OS
-- (android OS - or any other OS)
2) Linux kernel understands hardware like touchscreen, radios, I/O (drivers/modules). Of course it also understands how to schedule processes and all those "kernel tasks".
3) Libraries provide APIs (Application programming interface) to userspace code (like APPS).
4) Userspace (apps, scripts, libraries) provide user control over the phone.
--
Together they work in harmony (we hope) to make the phone realize it is a phone and allow us to use it as such. (well, a smartphone, so many things other than a phone).
Here's a simple example: You touch the phone icon which is in userspace, and it brings up the userspace phone app. As soon (or before) as you touch some buttons, dial a number, it is using the API to the driver in the kernel that actually understands the phone hardware/radio. Also userspace controls GUI which is also requiring API to some form of OPENGL API that is requiring device drivers that get the touchscreen/LCD display. and so on.
--- Hashi
PS: I realize there are a thousand things wrong with this representation, but hey, it's a start. Feel free to fix it up if you're inclined.

Define "the Google Experience"

Maybe I'm missing something. People talk about The Google Experience a lot in this forum. For me that sounds like saying "I don't install programs on my PC because I like the pure Windows experience."
I guess for me, the Google Experience just means that AT&T doesn't get to molest my phone with their apps, weird settings or worst of all, imprint their name indelibly on the front of my phone. To a much lesser extent, it means that I don;t have to worry about TouchWiz.
Is there more to it than that? What does it mean to you?

For me, it means Android as Google designed it, rather than how manufacturers think it should be to separate their phones from the competition and it means an unlockable boot loader out of the box without having to register with the manufacturer. It also means no carrier pre installed apps except stuff necessary for the phone to operate on their network.
When you buy a PC, you don't get manufacturer customized versions of Windows. You get the same Windows no matter what system you buy, so manufacturers compete on hardware, extras, etc. Sure, manufacturers pre load apps on Windows installations, but the fundamental UI remains the same.
Unfortunately the only way to get Android the way Google designed it is to either get a Nexus, or get some cheap budget Android device that uses the stock UI because its hardware can't handle anything more than that.
It's a shame that for each new major version of Android, Google needs to issue a Google-experience de ice to showcase the raw vanilla UI, but alas that's reality.
Sent from my Galaxy Nexus using Tapatalk 2

You mean pure Android Experience.
But I agree with you on most counts.

Pure Google experience is just that, pure.. Foundation for customization. Everything is built on top, if you strip any android phone down to the bones you''ll get get pure android, AOSP sitting on top of the Kernel. Some like it, some don't, some prefer something else. That's the way I look and understand it maybe I'm wrong in thinking this way.

Most of the replies have focused on the Android experience. I think the Google experience can also mean that you use many of the Google services (search, reader, drive, gtalk, voice, etc). Using all of this is easier on an Android phone vs iOS because of the apps and single sign on.

Simply put, not only do carriers install apps and themes, such as their custom interfaces (touch wiz sense); but they go further into the operating system. They edit and tweak various code in the underlying OS (framework kernel mods), block stock features like AT&T removing the option to install non market apps. Install tracking software however invasive you allow yourself to believe it to be (carrier iq). Ultimately these developers for the carriers and manufacturers might not be as good as the Google developers. Having used a phone both with and without having carrier iq installed (og epic) i know it performed significantly faster sans the carrier code. Pure google is just that, the code and features that Google released, not touched by outside developers which a majority of its code is still in every spin off to be found. The question is does your potential rom enhance that experience or hinder the phone from what it performed stock.
Sent from my Sprint Galaxy Nexus
-Everything i post is opinion based on my experiences and should be taken a such.

dreamsforgotten said:
Simply put, not only do carriers install apps and themes, such as their custom interfaces (touch wiz sense);
Click to expand...
Click to collapse
Carriers do not install custom interfaces, the OEMs do. The carriers can decide the layout, color scheme, and features of the interface, but the skins and overlays are all on Samsung, HTC, Moto, etc. There was a regional carrier that had a phone with the stock Google experience on a device that was skinned on other carriers, so the carrier can also specify to remove the overlays as well.
As for what Google Experience is, look at stock ICS and that is the Google experience. Nothing on the phone that isn't coded by Google,except for a couple items from VZW on their Nexus, which are easily disabled and removed with no change in functionality. All apps come from Google that are installed, and if you want more features or functionality, you choose it from the market or elsewhere. You don't use other services if you don't want to, and you aren't forced to have them either.

Its more of a minimalist philosophy. Simplistically having nothing but the core functions I use, which happen to be a load of Google apps, is what its all about. Then having all that extra ram resources not wasted on crap and fully available to my usage needs only. Its the less is more theory, elegant yet functional on the basic core stuff.

RogerPodacter said:
Its more of a minimalist philosophy. Simplistically having nothing but the core functions I use, which happen to be a load of Google apps, is what its all about. Then having all that extra ram resources not wasted on crap and fully available to my usage needs only. Its the less is more theory, elegant yet functional on the basic core stuff.
Click to expand...
Click to collapse
This is pretty right on. I think you will find, generally, that the people who like stock Android like it because they subscribe, as Google does, to the design philosophy that less is more. Therein lies my problem with custom Android implementations, both at the OEM and open source level. So many of them throw in everything AND the kitchen sink. I find that pointless.
Sent from my Galaxy Nexus using Tapatalk 2

Archpope said:
Maybe I'm missing something. People talk about The Google Experience a lot in this forum. For me that sounds like saying "I don't install programs on my PC because I like the pure Windows experience."
I guess for me, the Google Experience just means that AT&T doesn't get to molest my phone with their apps, weird settings or worst of all, imprint their name indelibly on the front of my phone. To a much lesser extent, it means that I don;t have to worry about TouchWiz.
Is there more to it than that? What does it mean to you?
Click to expand...
Click to collapse
Google Experience:
GSM Quad/Pentaband
Completely Unlocked (fastboot oem unlock)
No bloatware or custom skins
Instantly getting the newest Android version
----
This is basically what defines the "Google Experience"
There are also many specific things about the phone that add to the Google Experience.

oldblue910 said:
This is pretty right on. I think you will find, generally, that the people who like stock Android like it because they subscribe, as Google does, to the design philosophy that less is more. Therein lies my problem with custom Android implementations, both at the OEM and open source level. So many of them throw in everything AND the kitchen sink. I find that pointless.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
It actually goes with Google's whole design. Ever notice how most Google services like Gmail are functional but not really flashy so much and sometimes a tad bland, like Gmail for many years in the beginning. More about simple to use rather than fancy and fully loaded. This is slowly changing though.

In my opinion, having a Nexus device is a much better experience than using a device that has had an AOSP ROM ported or kanged. I can't remember which phone(s) it was but I remember a carrier adding apps to an AOSP ROM as well as another one themeing their overlay to look like it AOSP. Lame.
Sent from my Galaxy Nexus using Tapatalk 2

DeezNotes said:
In my opinion, having a Nexus device is a much better experience than using a device that has had an AOSP ROM ported or kanged. I can't remember which phone(s) it was but I remember a carrier adding apps to an AOSP ROM as well as another one themeing their overlay to look like it AOSP. Lame.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
The HTC G2 (great phone BTW) and LG G2X both ran stock Android builds, but they were loaded up with T-Mobile bloatware. Maybe those are the phones you were thinking of?

Google Experience to me:
Turning a phone on without having to see a app draw full of apps that are trial versions or just plain bloat (Verizon loads Tunewiki on my Thunderbolt by default, I will never touch this app but unless I root there is absolutely no way to remove it, it will inevitably launch and eat up my resources, not cool).
Not seeing some OEM skin. I like android's stock look, I like that I can get different launchers to change it up a bit but stock android is still the best to me. If I need extra features there is always the Play store, where I can download what I WANT, not be forced to have widgets out of the ass that I will never use.
I really feel like I could go on forever but I will stop there and just get to the point, when I turned on my Nexus I saw an open canvas, there was nothing on it but I could see the potential. If I wanted to keep it to only a few apps I could, if I wanted to load it with features and apps and go the whole 9 yards I also could. Basically to me the "Google Experience" is choice. Being able to turn the phone on and just do what I want with it without being told you have to use this skin or you have to have these apps preinstalled. Yes I know I can root (And always do) to remove the bloat but that doesn't remove the OEM skin (Unless I install a kanged AOSP ROM which almost always have a bug or two) but why should I have to? This is my phone, right? I just payed up to $700 to own it, I should be able to do what I want with it from the get go, and make it mine.
Sadly, not enough people see Android for what it is. The see bloated up phones, that run slow 2 months down the road, they see 4 different "Versions (OEM skins)" of Android and don't know which is which. They don't experience Android as it was meant to be experienced, which to me is way better than any iProduct could ever be.

For me the Pure Google Experience means being a good 'lil soldier and using my phone in such a way that adds useful info to their databases.

My Google Experience :
US first
Rest of the world : months later

[ANSWER] -_/*~Kernel~*\_-

There are many explanations that people will tell you to the answer to the "what is a kernel?" Like this great one from Omnicide
Spoiler
Omnicide said:
The best way i seen it put was, think of the kernel as the engine and the rom as the body of the car. The body of the car (rom) just makes the car look nice and user friendly. Now when we talk about the engine (kernel) simply put red lining the engine will get you to go fast but burn gas. Keeping the rev down low will make you run slower but saving lots of gas. Thats just one way to look at it, rpms being the cpu.
Click to expand...
Click to collapse
or this great one from androidcentral.com
Spoiler
What is a kernel? If you spend any time reading Android forums, blogs, how-to posts or online discussion you'll soon hear people talking about the kernel. A kernel isn't something unique to Android -- iOS and MacOS have one, Windows has one, BlackBerry's QNX has one, in fact all high level operating systems have one. The one we're interested in is Linux, as it's the one Android uses. Let's try to break down what it is and what it does.
Android devices use the Linux kernel, but it's not the exact same kernel other Linux-based operating systems use. There's a lot of Android specific code built in, and Google's Android kernel maintainers have their work cut out for them. OEMs have to contribute as well, because they need to develop hardware drivers for the parts they're using for the kernel version they're using. This is why it takes a while for independent Android developers and hackers to port new versions to older devices and get everything working. Drivers written to work with the Gingerbread kernel on a phone won't necessarily work with the Ice Cream Sandwich kernel. And that's important, because one of the kernel's main functions is to control the hardware. It's a whole lot of source code, with more options while building it than you can imagine, but in the end it's just the intermediary between the hardware and the software.
When software needs the hardware to do anything, it sends a request to the kernel. And when we say anything, we mean anything. From the brightness of the screen, to the volume level, to initiating a call through the radio, even what's drawn on the display is ultimately controlled by the kernel. For example --when you tap the search button on your phone, you tell the software to open the search application. What happens is that you touched a certain point on the digitizer, which tells the software that you've touched the screen at those coordinates. The software knows that when that particular spot is touched, the search dialog is supposed to open. The kernel is what tells the digitizer to look (or listen, events are "listened" for) for touches, helps figure out where you touched, and tells the system you touched it. In turn, when the system receives a touch event at a specific point from the kernel (through the driver) it knows what to draw on your screen. Both the hardware and the software communicate both ways with the kernel, and that's how your phone knows when to do something. Input from one side is sent as output to the other, whether it's you playing Angry Birds, or connecting to your car's Bluetooth.
It sounds complicated, and it is. But it's also pretty standard computer logic -- there's an action of some sort generated for every event. Without the kernel to accept and send information, developers would have to write code for every single event for every single piece of hardware in your device. With the kernel, all they have to do is communicate with it through the Android system API's, and hardware developers only have to make the device hardware communicate with the kernel. The good thing is that you don't need to know exactly how or why the kernel does what it does, just understanding that it's the go-between from software to hardware gives you a pretty good grasp of what's happening under the glass. Sort of gives a whole new outlook towards those fellows who stay up all night to work on kernels for your phone, doesn't it?
. You probably didn't get it at all, so let me tell you what a kernel is in about 17 words. A kernel is "what makes the phone work, and connects the hardware (camera, storage, etc.) And the software (the Rom)."
I don't want to be thanked for this, thank omnicide, and androidcentral.com for the great explanations.
~~~~~~~~~~~~~~~~~~~~~
Samsung galaxy s2
Rom: Jedi knight 6
kernel: Jedi kernel 2
~~~~~~~~~~~~~~~~~~~~~
And you thought celebrities weren't smart! =P

Kernel can correlate to brains function in the human body meaning the manager of the perishing body.
Or the manager of the resources available.
Or the manager of the body.
Sent from my SAMSUNG-SGH-T989 using xda premium

I flashed JB Jedi 2 which came packed with a rom while it works great I wonder what will happen if I want to switch back to a different Rom will it be compatible with the kernel it installed?

All roms install their own default kernel each time you flash them.
They are usually chosen by the rom's Dev for good reasons (usually stability) .
It's up to you if you then choose to replace the included kernel with one of your own choosing.
At that point you should think twice about posting glitches you encounter on the ROM developer's forum because you have now changed a fundamental component of his work which is not of his choosing. It would be kind of rude to clutter his thread with problems that may be caused by the replacement kernel.
Feel free to push the envelope, just make a backup first then post problems to the kernel's thread.

Ohh ok I really didnt know that as some roms I have downloaded are 90mb some are like 330mb does that mean they are all compressed in different ways?

davcohen said:
Ohh ok I really didnt know that as some roms I have downloaded are 90mb some are like 330mb does that mean they are all compressed in different ways?
Click to expand...
Click to collapse
No. Some ROMSs gave more data or bloat. Slim ROMs, are well, slim. Leaks, like, Jedi jelly, tend to be pretty big, due to all the bloat they have.

LoopDoGG79 said:
No. Some ROMSs gave more data or bloat. Slim ROMs, are well, slim. Leaks, like, Jedi jelly, tend to be pretty big, due to all the bloat they have.
Click to expand...
Click to collapse
Bloat = the stuff, APKs in this case, someone decided are not necessary.

New Android feature suggestions...

Is there someplace people can go to make requests for new Android features? (Someplace were developers might actually see it and perhaps implement the requests?)
I have had ideas for several features that I think would make my Android devices (I have owned about 6) far better...
- One of my ideas was the ability for more than one Bluetooth device (ie: wireless headphone/earphones) to be able to connect to a single Android device at the same time. I go running, hiking, etc... When I go alone, I often listen to music. It would be great if when I run with someone else, if they could listen to the music I am playing on my Android device at the same time I am.
- I have changed ROMs many times, but when I do, it is always a pain to have to setup (or recreate) my music playlists on the new ROM. Many (not all) Android music players seem to allow users to import music playlists that have been created on PCs or whatever. None of the music players or the Android OS itself seem to allow me to save a music playlist as a file (ie: export) that I can reload later, use on another device, or give to someone else.
- None of the Android ROMs I have come across seem to provide a (relatively easy) way to change the the the resolution (LCD density) so that I can make images and text larger or smaller on my display. This is something that is very easy to do (change a setting and hit save/apply) on every PC I have ever owned, but the few ROMs that seem to allow this seem to have a complex procedure for doing it.
- Ability to put Widgets in folders (on the desktop). I like widgets. I sometimes even like the UI of a widget better than the associated app. (Sometimes widgets provides a nice condensed view of the information/features, or provide simple capabilities like a switch to turn on/off a feature without launching menus and digging through them.) Unfortunately the Android OS (or the "Home" apps that currently exist) does not (do not) allow widgets to be put into a folder on the desktop. I would like this feature for many reasons. 1) The folder could limit the widget from consuming battery or system resources until the folder was opened. That way widgets would not use up my battery or CPU cycles until I opened the folder and looked at them.
- It would be great to have a "magnifying glass" (zoom feature) that I could use to make any specific area on the display larger (so that if I'm having trouble seeing something small on the display, I can magnify it large enough to see it).
I have more ideas, but those are just a few of the things I think would make Android devices better. Feel free to add your own suggestions to this list.

Pretty good ideas as far as magnifying just pinch to zoom in that specific area or double tap. I believe there are apps to backup a music playlist the bluetooth idea is actually kind of cool
Sent from my SPH-L900 using xda app-developers app

mediawiz said:
Is there someplace people can go to make requests for new Android features? (Someplace were developers might actually see it and perhaps implement the requests?)
I have had ideas for several features that I think would make my Android devices (I have owned about 6) far better...
- One of my ideas was the ability for more than one Bluetooth device (ie: wireless headphone/earphones) to be able to connect to a single Android device at the same time. I go running, hiking, etc... When I go alone, I often listen to music. It would be great if when I run with someone else, if they could listen to the music I am playing on my Android device at the same time I am.
- I have changed ROMs many times, but when I do, it is always a pain to have to setup (or recreate) my music playlists on the new ROM. Many (not all) Android music players seem to allow users to import music playlists that have been created on PCs or whatever. None of the music players or the Android OS itself seem to allow me to save a music playlist as a file (ie: export) that I can reload later, use on another device, or give to someone else.
- None of the Android ROMs I have come across seem to provide a (relatively easy) way to change the the the resolution (LCD density) so that I can make images and text larger or smaller on my display. This is something that is very easy to do (change a setting and hit save/apply) on every PC I have ever owned, but the few ROMs that seem to allow this seem to have a complex procedure for doing it.
- Ability to put Widgets in folders (on the desktop). I like widgets. I sometimes even like the UI of a widget better than the associated app. (Sometimes widgets provides a nice condensed view of the information/features, or provide simple capabilities like a switch to turn on/off a feature without launching menus and digging through them.) Unfortunately the Android OS (or the "Home" apps that currently exist) does not (do not) allow widgets to be put into a folder on the desktop. I would like this feature for many reasons. 1) The folder could limit the widget from consuming battery or system resources until the folder was opened. That way widgets would not use up my battery or CPU cycles until I opened the folder and looked at them.
- It would be great to have a "magnifying glass" (zoom feature) that I could use to make any specific area on the display larger (so that if I'm having trouble seeing something small on the display, I can magnify it large enough to see it).
I have more ideas, but those are just a few of the things I think would make Android devices better. Feel free to add your own suggestions to this list.
Click to expand...
Click to collapse
Great ideas. I use Google Music to set up my playlists with my music on my desktop at home. No matter if I'm at work, over a friends house, or switching roms on my phone, as soon as I download google music, all my playlists and music is right at my fingertips.
As far as resolution changing, I would suggest Carbon Rom as you can change your density in less than a minute, and that's mostly because you have to reboot twice, but there are no force close issues or any of that.
As far as features go, I would like to see recovery feature addition:
The thing I hate the most about switching roms is having to log in to 15 different accounts again. I wish TWRP would construct a feature that allows me to carry over my sign in information for standard apps (Facebook, Webex, GroupME, etc.) that most people use.
Or perhaps, a ROM that offered three different login slots that attempted to log into every app that I restore using those slots first and if login is unsuccessful, THEN prompt me to enter login information.
Just a suggestion that would allow the end-user to streamline setting up his/her rom. What do you guys think?
PS: I think the multi-bluetooth device feature would be sweet as well. I have a couple of computers at home that I use my Note to control, it would be nice to have the option to control any given device in an instance.

As for resolution, that's much more easier said than done, since some apps would have to be rebuilt from the ground, or at least would have to individually be written and flashed for said resolution.
However, if there are a few apps that you really want to change (like for me, G-Mail, Chrome, XDA, gReader, etc), you really need to check out XPosed, honestly, I don't know if I'll ever buy a device that doesn't support it or something similar. It features on the fly resolution/DPI adjustments per app, one of the greatest MODs ever brought to Android, hands down.

The Note2 does what I need it to once rooted. I would like to see better prices and data first. Why have the next great thing when you pay out the ass and don't have equal speed?
I would like to see Android updates that actually make me want them, like better codex, performance, UI functions, etc. Some updates don't really seem like updates, like when Ubuntu releases a new version but you do the same thing as before, and you are left wanting more.

daswahnsinn said:
The Note2 does what I need it to once rooted. I would like to see better prices and data first. Why have the next great thing when you pay out the ass and don't have equal speed?
I would like to see Android updates that actually make me want them, like better codex, performance, UI functions, etc. Some updates don't really seem like updates, like when Ubuntu releases a new version but you do the same thing as before, and you are left wanting more.
Click to expand...
Click to collapse
I agree somewhat. However, I think that the 4.2.2 roms with Linaro are noticeably faster than other 4.2.2 roms without it. Carbon is much faster without me having to use apps like Pimp My Rom and Lag Reducer without compromising my battery performance.
Halo is also another great custom feature that may one day rival the stock multi-window feature.
I also like the profile triggers built into Carbon, bluetooth and wifi triggers are wonderful, hopefully we can get some GPS triggers, then we will really be in business lol.
All in all, I agree with you though, we need some REAL POWER behind these updates. But I'm sure devs would say "Let's get some real CASH behind the devs and you guys will see some POWER!!" **Gotta look at it from both sides**
Great input guys. Let's keep it going!!!

lightning launcher has the widget in folder capabilities. It's my daily launcher
just saying.....
Sent from my SPH-L900 using xda premium

Need the Android equivalent to iMessage.
Desperately needed and no, Google Hangouts (in its current state ) is not the answer.
Sent from my SGNote 2!

[email protected] said:
I agree somewhat. However, I think that the 4.2.2 roms with Linaro are noticeably faster than other 4.2.2 roms without it. Carbon is much faster without me having to use apps like Pimp My Rom and Lag Reducer without compromising my battery performance.
Halo is also another great custom feature that may one day rival the stock multi-window feature.
I also like the profile triggers built into Carbon, bluetooth and wifi triggers are wonderful, hopefully we can get some GPS triggers, then we will really be in business lol.
All in all, I agree with you though, we need some REAL POWER behind these updates. But I'm sure devs would say "Let's get some real CASH behind the devs and you guys will see some POWER!!" **Gotta look at it from both sides**
Great input guys. Let's keep it going!!!
Click to expand...
Click to collapse
See I like Touchwiz and the stock UI bs and want more of these mods to make into a stock ROM, sometimes I wish Sammy read these types of forums.

Dual Booting Anyone? are we there yet?

i know that there are Kernels that can do this, its possible and can be done but is this an issue, a solution, something to look forward, something to think about, or give deep try in developing and making it a reality like Roms, or is it dead, its not a thing? people are now satisfied with what they have as custom/Stock Roms with kernels, MODS, Open Source scripts that yu can mess up with, themes, Root Apps, Are we done?
upgrading became the big fuss when rooting became public, a simple easy code/binaries/ETC that you could alter and get Admin rights anyone can do it now (DEVS, ELITE/PRO/EXP/AVERAGE ANDROID USERS) for the average user its an app from the Play store and ROOT allows you to control/modify the whole package not just the basic/average using
4 years LATER and we have Root like anyother app, yes we have come so far but what do we have in store, Windows official 1.0 to windows 8 all those versions they have reinvented, developed, innovation has been found sure they they dont have a clean sheet but they done as much with little time as they could
has anyone noticed that since Gingerbread we have not incoporated any major updates, features, developments, Big changes, Android 4.x.x has just being polishing, cleaning up the mess, getting rid of major bugs, Big Fixes, new theme, stable enough, added some few minor tweaks and called it Jelly Bean (am not hatin on Google and everyone who has contributed to ICS/JELL BEAN THEY DESERVE CREDIT/THANKS FOR THEIR HARDWORK THEY PUT IN IT) Google Open Source Linux based Android OS and we are done
iguess its time to focus on Security since it has been a big issue (the elephant in the room) So CALLED IRRELEVANT nobody wants to deal with it, although Google has tried eliminating this threats/virus/malware they still haVE alot of work to do APPL IS PRO AT THAT(take_notes_google)
Security Vs Rooting is the new topic in CM (iwont get into that too much look it up yourself) how will they deal with it IDONT_KNOW, other than that i would Say that we are done with developing Firmware, features, games, Apps, Roms, Kernels, wateva Android includes that can utilize the 1.9/2GHZ, KILLA GPU, Processors that will continue to upgrade push the mobile to the limit/beyond and maybe one day compete with Desktop/laptop GPU/CPU's
KILLA hardware/SPECS THAT we are not using it to the fullest, playing angry birds, instagram, playin music, making a call/text does not utilize anything just takes 1-10% CPU and Zero Ram
if one day we can replace Ram(mobile) or even desktop, with something else that would be awsome until then we have nothing to show off to APPL Fanboys