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.

How safe is to Use Custom ROM

Hi, All
I saw lots of docs that says be careful before installing 3rd party apps. Because of security issues.
But what about of custom ROMS? We are installing the whole OS.
In installing Custom ROMS developers just gave URL to download ROMS or some application that installs these ROMS on phones?
We even dont know how these ROMS builds, what hidden applications will run in background
I am not here insulting gr8 developers efforts in creating these ROMS and rooting.
Just asking something what I feel. It will be great if some one answer this in positive way.
Also are we able to root wildfire now after 2.2 official upgrate as http://androidos.in/2011/05/we-will-no-longer-be-locking-bootloaders-on-our-devices-–-htc/?

No 2.2 root still. As forROMs your mostly ok, people are usally genuine and they takw much more effort than apps.
Sent from my HTC Wildfire using XDA App

custom roms
i would say they are stable enough for daily use like around 90-95% of the stuff in it works. that should be the case for the most popular aftermarket firmware of custom roms, cyanogenmod. for more info, visit: www.cyanogenmod.com

As for rooting hboot 1 - i have no clue as to what htc are going to do (feel free to sign using link below)
Sent from my GT-P1000 using XDA App

I don't get what sort of "positive discussion" you want on this topic. Yes, it is true, developers CAN implement hidden stuff and backdoors on their ROMs. So, what will you do about it? The answer is upto you if you trust the dev or not, and, if you are paranoid, dont use Custom ROMs. End of story. And if you still want to use Custom ROMs, then learn the Android OS, break down the ROM, analyze it and use it - or better still, make your own ROM and use it.

Take it easy
My friends,
I understand that this is an obvious question, but the responses seem quite harsh in my opinion..
the references of condoms and paranoia are funny to some but offensive to others and this leads to arguments which lead to rule breaking and well at the end of the day one may find himself/herself banned for only pointing out the obvious..
Remember that this is also an act of trolling which is not something that XDA tolerates..
So i advise all to avoid this kind of behaviour unless looking for some trouble.
On this note, Thread closed (also cleaned away the unnecessary posts)

[Q] Any benefit of CM7 over Others?

Just curious as everyone freaks out about cyanogenmod... what would be the benefit of running it over, say... Calkulin's rom? I have CM7/9 on my HP Touchpad, and I don't see anything major that differentiates it from normal android?

small and clean.

It's completely open-source (built off of the Android Open Source Project)
Many more options for customization
No need for "rooting"
Built-in theme manager
Consistent default user environment over multiple devices
There are many more of course, but those are some of my favorites. I mainly support it because I am a huge proponent of open-source software, and I enjoy the level of customization without "bloatware" from carriers or device manufacturers.
If you'd like to see a few more specific features, check out the wiki here: http://wiki.cyanogenmod.com/wiki/Features

While I admire the skill and time it takes the devs, I won't run the CM ROMs because it disables dialer codes, and if I want to update my PRL or baseband, I'm forced to install a different ROM to do so.
Sent from my SPH-D710 using XDA App

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

General No GAPPS for more freedom!

When I started installing modified ROMs a few years ago on my devices (Galaxy Y and the Nexus 5) it was to have more options than what the factory system didn't have by default.
Having all those apps that manufacturers install and Google's suite of apps didn't suit me either. Especially with new research revealing how various companies use apps to mine user data.
At the time of the Nexus 5 there were several ROM's available and if I wanted the Google applications installed I needed to install a "GAPPS" package. Otherwise I was free to use the system only with the essential AOSP applications.
Time passed and between the Nexus 5 and the Oneplus 9 Pro some movement happened and now most of the ROM's already come with the GAPPS package included in their builds.
Apparently on the Oneplus 9 Pro the only two actively supported options are LineageOS and crDroid and those that don't include GAPPS packages by default.
What happened? Why already include GAPPS in the build?
Is it for technical reasons, convenience? What is the reason for developers to take this attitude and not delegate the choice to users?
...

I hear you! I'd like to get away from Google as much as possible. I don't trust them.
I think that the way Android is nowadays, the AOSP ROMS are limited in the services they provide and many apps are written for the Google API's included with Gapps. If you don't install Gapps, many apps will not work with vanilla Android alone. You almost have to conpletely divorce yourself from all the Google API's and any apps that rely on them just to get away from Google.
What it amounts to is a spartan living on a phone that's de-Googled. You can only install apps from F-Droid and a couple other places if you want Google-freedom. It's a choice that you have to decide to live with.

I prefer installing MicroG to get around part of the problem with apps that need Google's api's. I'm currently using crDroid with MicroG and the bank apps have been working great. Just like the GPS that in other times was very difficult to use. But now with osmAnd+ it's much easier.
I also have my own Nextcloud server installed on a cheap VPS that I use for various services such as: synchronizing contacts, calendar, notes and newsreader. I also have a mail server. All with the help of the YunoHost project.
crDroid is an excellent ROM but it has some features from other projects that I would like to try out. But as now several developers decide to provide the GAPPS package already included in their builds, it becomes more difficult to make the change.

You just have to search around and find special builds of ROM's that meet your needs.
I'm on a shoestring budget, myself. I have a few Android devices/phones, and an Odroid XU4 SBC with a 4TB hard drive as a server. It's not much, but it covers my needs. LOL
Edit: OsmAnd is a great offline mapping app.

Nouty said:
When I started installing modified ROMs a few years ago on my devices (Galaxy Y and the Nexus 5) it was to have more options than what the factory system didn't have by default.
Having all those apps that manufacturers install and Google's suite of apps didn't suit me either. Especially with new research revealing how various companies use apps to mine user data.
At the time of the Nexus 5 there were several ROM's available and if I wanted the Google applications installed I needed to install a "GAPPS" package. Otherwise I was free to use the system only with the essential AOSP applications.
Time passed and between the Nexus 5 and the Oneplus 9 Pro some movement happened and now most of the ROM's already come with the GAPPS package included in their builds.
Apparently on the Oneplus 9 Pro the only two actively supported options are LineageOS and crDroid and those that don't include GAPPS packages by default.
What happened? Why already include GAPPS in the build?
Is it for technical reasons, convenience? What is the reason for developers to take this attitude and not delegate the choice to users?
...
Click to expand...
Click to collapse
It's primarily for user convenience. Not many people are willing to use MicroG services because of it's unreliability

Nouty said:
When I started installing modified ROMs a few years ago on my devices (Galaxy Y and the Nexus 5) it was to have more options than what the factory system didn't have by default.
Having all those apps that manufacturers install and Google's suite of apps didn't suit me either. Especially with new research revealing how various companies use apps to mine user data.
At the time of the Nexus 5 there were several ROM's available and if I wanted the Google applications installed I needed to install a "GAPPS" package. Otherwise I was free to use the system only with the essential AOSP applications.
Time passed and between the Nexus 5 and the Oneplus 9 Pro some movement happened and now most of the ROM's already come with the GAPPS package included in their builds.
Apparently on the Oneplus 9 Pro the only two actively supported options are LineageOS and crDroid and those that don't include GAPPS packages by default.
What happened? Why already include GAPPS in the build?
Is it for technical reasons, convenience? What is the reason for developers to take this attitude and not delegate the choice to users?
...
Click to expand...
Click to collapse
in my opinion it doesn't make sense to build a rom without google apps because all roms have google services in them (since these are also used in the background for updates "project mainline") since android 10

If you're truly into de-Google-ifying, I'd start with /e/ OS.

ArmashOnXDA said:
It's primarily for user convenience. Not many people are willing to use MicroG services because of it's unreliability
Click to expand...
Click to collapse
ChrisFeiveel84 said:
in my opinion it doesn't make sense to build a rom without google apps because all roms have google services in them (since these are also used in the background for updates "project mainline") since android 10
Click to expand...
Click to collapse
Okay, that's more convenient. But it is also not difficult for the user to add one more .zip or a reboot-to-recovery to perform just one more installation. Many already do this to install Magisk.
I think not including GAPPS in the build provides one more option for all users. Users who want it can choose which GAPPS package to install. From "Full stock" to "Core".

primarily for user convenience = care for user inability
romchefs dish-up what users want

If you care about deGoogle and hardening a ROM called DivestOS is also a choice https://divestos.org/pages/devices#device-lemonadep Never tried it tho ur on ur own

Tom Mix said:
primarily for user convenience = care for user inability
romchefs dish-up what users want
Click to expand...
Click to collapse
TrumpXi said:
If you care about deGoogle and hardening a ROM called DivestOS is also a choice https://divestos.org/pages/devices#device-lemonadep Never tried it tho ur on ur own
Click to expand...
Click to collapse
I understand the good intention of the developers to want to include and facilitate the integration of lay users in the world of custom ROMs. But you can already see that it is better to teach how to do it than to "deliver it ready".
I took a look at DivestOS but the point I want to make is that not including the GAPPS package opens up a much wider range of options for all users.
DivestOS also doesn't provide many of the features you might find in other ROMs.

Every individual learns at a different rate and level. Trying to teach one message at a time is not the most efficient way to teach. If someone is interested in installing a custom ROM, they should start with Google search and get questions answered one at a time. When you put forth a serious effort to learn how to accomplish something, you retain more in memory and don't have to ask the same question again. Then if you don't like the first ROM you installed, you are more prepared to flash the second one.... Thinking out loud here.

once the idea of a custom rom was a very different one:
have control and the freedom of choice.
nowadays so called 'custom-roms' already include gapps
what a farce
[OFFTOPiC] i try to analyse if licenses are violated by
distributing 'custom-roms' including gapps.
[iLLEGAL] [LEGAL] GApps including Custom ROMs [QUESTiON] [DiSCUSSiON]
hello world unfortunately one sees more and more so called 'custom roms' including GApps by default 🤷‍♂️ this brings up a question: is this legal? as an example reading: Google apps are the proprietary Google-branded applications that come...
forum.xda-developers.com
but no one is interested at all
and so far i can understand the licence
it is not allowed, maybe can someone from
this topic help to clarify[/OFFTOPiC]

Nouty said:
When I started installing modified ROMs a few years ago on my devices (Galaxy Y and the Nexus 5) it was to have more options than what the factory system didn't have by default.
Having all those apps that manufacturers install and Google's suite of apps didn't suit me either. Especially with new research revealing how various companies use apps to mine user data.
At the time of the Nexus 5 there were several ROM's available and if I wanted the Google applications installed I needed to install a "GAPPS" package. Otherwise I was free to use the system only with the essential AOSP applications.
Time passed and between the Nexus 5 and the Oneplus 9 Pro some movement happened and now most of the ROM's already come with the GAPPS package included in their builds.
Apparently on the Oneplus 9 Pro the only two actively supported options are LineageOS and crDroid and those that don't include GAPPS packages by default.
What happened? Why already include GAPPS in the build?
Is it for technical reasons, convenience? What is the reason for developers to take this attitude and not delegate the choice to users?
...
Click to expand...
Click to collapse
What happened? Mostly quality went to quantity. Back then ROMs were actual ROMs instead of these trash copy paste propaganda called AOSP.
Cant wait for the reports and triggered people.