Original Post : linkedin.com/pulse/google-android-guys-here-idea-you-prashantha-mundkod
Today, I have some business ideas for Google Android guys..
Idea
A tool (a desktop tool and/or android app tool ) for creating ROM and installing stock android.
This tool basically does 3 major tasks.
1. Reads hardware information of an Android device through the desktop/android tool and creates a stock android ROM for that device.
2. Creates a super user , roots the device , installs the ROM created in step 1.
3. Provides an option to keep/remove the super user after the installation based on user sophistication.
(Alternatively, tool will install a generic stock android and then look for appropriate drivers for the device after the installation)
Why do we need a tool ?
Here is what I found while playing around with stock android.
1. Majority of handset manufacturers simply don't bother provide updates . Even if they do, its ridiculously delayed.
2. The UI created by most manufacturers is not innovative or user friendly. They are loaded with ridiculous amount of bloatware. Since they don't bother to provide timely updates either, end user is stuck with an older version of Android regardless of device's capability to support newer versions of android.
3. For an average user, there is no simple way to install a stock android . Users are in mercy of tech forums and developers who volunteer to create custom ROM. Expecting a ROM from volunteers for all devices out there is unrealistic . Trusting those ROMs is another biggest concern as well. Despite the volunteer efforts , installing a stock android ROM still needs some level of IT knowledge , not the cup of tea of an average android user.
4. There is no generic stock android ROM. Reason perhaps is that, creating a package with drivers for thousands of manufacturers would be practically not feasible as the package size would be enormous.
User Experience
An end user who wants a stock android doesn't need to be an IT guy and the tool should be simple to user. Example : Click a button that would read hardware and create the package, next user interaction is a prompt asking the user to install the stock android ROM. All other user interactions such as retaining super user etc is an an option for advanced users.
Manufacturers
Any custom UI or App package a manufacturer wants to push for their device should be updated as App package from manufacturer over a pure android . (Example : Once user install the stock android, manufacturers like Samsung, can push their app like Galaxy gifts etc as a package. )
This would shorten the development cycle for manufacturers as well. Thus updating Android for their device becomes purely a app package for an android version , rather than individual device.
Advantages
For users, clearly the benefit is the ability to have most updated software and experience of pure android and freedom from abandonment of device from manufacturers.
For Google (and Android as a platform ), one of the biggest competitive disadvantage is , its fragmentation. One of the reason for fragmentation is that, for a large number of devices, simply there is no easy way to update the software. The tool could help solve fragmentation issues.
The tool may be included as part of Google's attempt for Android One initiative. Certainly , no explanation is necessary on how it benefits Google from having one single version of android in all (or at-least as many devices as possible) android devices.
For now, that's it . When i am free, I will post the details on how exactly they should do it .
Experts... What do you think ?
Disclaimer : Views expressed are my own.
Related
i do not have much knowledge on android phones and from looking on the internet there is a lot of tutorials and information but they seem to be specific for a certain phone, like the HTC's for example.
the phone i currently have was purchased from chinavasion.com and it is a phone they have built themselves and have done so very well, i believe it contains hardware from different existing mobile phones and it runs on android v1.6.
i am really wanting to update my phone now and my biggest problem is that there is little internal memory on the phone and i am wanting to be able to save applications onto the SD card which i believe you can on android v2.2, i have heard about rooting but i am very unsure how to do it and whether it would be worth it.
any information on how to update this phone or rooting this would be very much appreciated,
thankyou.
this is the information given by the manufactured/wholesaler
* Qualcomm 7227 CPU is the same chip found in the Motorola Devour Android Phone.
* Though hacking the firmware voids the warranty, Qualcomm 7227 CPU supports all leading mobile operating systems including Android, Symbian S60, and Windows Mobile.
Note: The Android OS version on this cell phone cannot be upgraded or flashed and any attempts to modify the default OS will void the warranty. As a wholesaler, Chinavasion provides no software support, advice, or training regarding the Android operating system and software.
I would also like to have such update!
This phone is also knows under name "TWM T1" (Taiwan mobile), but that version also have donut ROM
There are nice treads in mobile01.com forum about Rooting and APP2SD
Using their instructions, I rooted, managed to install APP2SD and Google Apps on phone, so it's now much more useful than before.
Hello,
First off, apologies if I have posted this in the incorrect forum.
The company I work for is looking to update one of it's product lines and has been toying with the idea of using Android as a development platform. Up until now the philosophy has always been to develop simple, bespoke embedded software that provides only the functionality that is needed at the time. The device itself will be a medical device, and as such will have no telephony requirements (and associated things like contacts, calander and the large majority of the pre-installed Android apps).
I have read, and understand it is possible to re-compile Android from source and remove all of these non-required functionality. My question is really if that is worth doing? i.e. stripping out all un-needed applications that get build into a stock ROM. Or would it be a more efficient to use some form of OTS embedded Linux platform?
Something in Android 4.0 that does seem to be useful is the support for Bluetooth HDP.
Kind Regards,
Simon
Well there are other devices that aren't phones that use Android. Take the motoactv for example. It's a fitness watch that runs a stripped version of Android, but it's still Android and applications can still be programmed and installed to it.
Hello World ! I have identified a need for a smaller tablet and have begun the process to request information about how to have the hardware designed and manufactured. But as we all know, hardware is only half of the equation - the other half is the software. So I have a question for you:
What would the ideal software configuration for an Android-based LTE-enabled TABLET (with SIM card), suitable for ROM developers ?
I have (a little) previous experience (as an end-user) with replacing the manufacturer/carrier ROM for my HTC Desire with the CyanogenMod ROM. That, coupled with my years of experience as a developer (pre-Internet) allow me to at least be aware that there are layers of software from bootup, to device drivers, to OS, etc.
I would like this community to help define (or point me at some documentation) what those specific layers are, which package(s) should be used at each level, up to the point of being able to get into the Google Play Store.
I am not interested in which apps should be discussed - that's the end-user's problem.
Thanks,
Steven.
Dream software config for Android Tablet ROM developers ?
Hey all, hoping to get some visibility & feedback here ...
Steven.
StevenCShearer said:
Hello World ! I have identified a need for a smaller tablet and have begun the process to request information about how to have the hardware designed and manufactured. But as we all know, hardware is only half of the equation - the other half is the software. So I have a question for you:
What would the ideal software configuration for an Android-based LTE-enabled TABLET (with SIM card), suitable for ROM developers ?
I have (a little) previous experience (as an end-user) with replacing the manufacturer/carrier ROM for my HTC Desire with the CyanogenMod ROM. That, coupled with my years of experience as a developer (pre-Internet) allow me to at least be aware that there are layers of software from bootup, to device drivers, to OS, etc.
I would like this community to help define (or point me at some documentation) what those specific layers are, which package(s) should be used at each level, up to the point of being able to get into the Google Play Store.
I am not interested in which apps should be discussed - that's the end-user's problem.
Thanks,
Steven.
Click to expand...
Click to collapse
A ROM, for those who don't know, is an operating system build that runs on your device with basic applications such as an address book, calendar, camera, etc.
A major advantage of Android smartphones is that they can be operated by third-party systems and not only with the original ROM. Custom ROMs replace the pre-installed version of Android on devices. The substitution is made by a variation of the AOSP, adapted by volunteers with 'too much free time'.
These volunteers often work more frequently than the manufacturer itself – at least when it comes to updates.
AOSP?
AOSP means Android Open Source Program. It is a version of the open source code of Android, developed by Google in its consortium of brands to offer a pure version of the system, which is available to anyone. It can be modified by developers without the need to follow standards of Google applications.
Thanks to this project, the birth of custom ROMs like CyanogenMod, Paranoid Android, MIUI and others have come about.
Advantages of custom ROMs
System upgrade for older smartphones
Many Android owners already know this problem: the smartphone is already a year old but the manufacturer hasn't released updates to the device. The new versions of Android are not only interesting because they bring new features but also because they fill security gapps.
Third party firmware uses the official codification of Android as well as a compatible driver for smartphones. This keeps everyone up-to-date on the newest version of Android. And it's not difficult for a custom ROM to be more updated than the original firmware
The smartphone is faster
One of the biggest advantages of using custom ROMs is your smartphone will be faster. Themes and applications preinstalled by the manufacturer are reduced to almost nothing. This saves a lot of memory space and increases the device's performance.
Customization options galore
Custom ROMs not only bring the latest version of Android but also give you many customization options. The possibilities are almost limitless.
You have root access (administrative)
With root access, you have control over all of the functions of your device. With the original Android, some functions are hidden. Now the modified firmware gives you unlimited access to all the features of your smartphone. Furthermore, backups are performed more easily.
Ideal for purists
Since custom ROMs are based on the 'Android Open Source Project' they are enriched with more functions and the appropriate driver by the team behind the community firmware. So if you bought a less stocky Android device like a Sony or Samsung you can still get a stocky experience.
Disadvantages
Custom ROMs are wonderful but before you decide to change your device's original firmware you should familiarize yourself with the disadvantages of the process.
They void the warranty
If your phone is still under warranty, you could have the possibility of voiding it if you decide to install a custom ROM. There are just a few manufacturers that will tolerate changes to the device system. Xiaomi is one of them.
They're a lot of work
Custom ROMs are perfect for those who love a good challenge. But if this doesn't sound like you then you won't like custom ROMs. Between updates, the system root and unstable versions of a device, your patience could reach its limits.
The lack of Google applications
Third-party firmware comes with very few Google apps. The Play Store applications have to be installed again. The Google apps that you will need to install again can be found on the site.
Credits @ SHAHJADE ALAM
Devendar Reddy D said:
A ROM, for those who don't know, is an operating system build that runs on your device with basic applications such as an address book, calendar, camera, etc.
A major advantage of Android smartphones is that they can be operated by third-party systems and not only with the original ROM. Custom ROMs replace the pre-installed version of Android on devices. The substitution is made by a variation of the AOSP, adapted by volunteers with 'too much free time'.
These volunteers often work more frequently than the manufacturer itself – at least when it comes to updates.
AOSP?
AOSP means Android Open Source Program. It is a version of the open source code of Android, developed by Google in its consortium of brands to offer a pure version of the system, which is available to anyone. It can be modified by developers without the need to follow standards of Google applications.
Thanks to this project, the birth of custom ROMs like CyanogenMod, Paranoid Android, MIUI and others have come about.
Advantages of custom ROMs
System upgrade for older smartphones
Many Android owners already know this problem: the smartphone is already a year old but the manufacturer hasn't released updates to the device. The new versions of Android are not only interesting because they bring new features but also because they fill security gapps.
Third party firmware uses the official codification of Android as well as a compatible driver for smartphones. This keeps everyone up-to-date on the newest version of Android. And it's not difficult for a custom ROM to be more updated than the original firmware
The smartphone is faster
One of the biggest advantages of using custom ROMs is your smartphone will be faster. Themes and applications preinstalled by the manufacturer are reduced to almost nothing. This saves a lot of memory space and increases the device's performance.
Customization options galore
Custom ROMs not only bring the latest version of Android but also give you many customization options. The possibilities are almost limitless.
You have root access (administrative)
With root access, you have control over all of the functions of your device. With the original Android, some functions are hidden. Now the modified firmware gives you unlimited access to all the features of your smartphone. Furthermore, backups are performed more easily.
Ideal for purists
Since custom ROMs are based on the 'Android Open Source Project' they are enriched with more functions and the appropriate driver by the team behind the community firmware. So if you bought a less stocky Android device like a Sony or Samsung you can still get a stocky experience.
Disadvantages
Custom ROMs are wonderful but before you decide to change your device's original firmware you should familiarize yourself with the disadvantages of the process.
They void the warranty
If your phone is still under warranty, you could have the possibility of voiding it if you decide to install a custom ROM. There are just a few manufacturers that will tolerate changes to the device system. Xiaomi is one of them.
They're a lot of work
Custom ROMs are perfect for those who love a good challenge. But if this doesn't sound like you then you won't like custom ROMs. Between updates, the system root and unstable versions of a device, your patience could reach its limits.
The lack of Google applications
Third-party firmware comes with very few Google apps. The Play Store applications have to be installed again. The Google apps that you will need to install again can be found on the site.
Credits @ SHAHJADE ALAM
Click to expand...
Click to collapse
A custom rom is anything that is not stock from a manufacturer first off, you can have modified stock rom and it is a custom one bc you modified it. What you are talking about here is a source built rom with heavy modifications. Secondly they do not void your warranty. Tripping knox or bootloader security voids your warranty. And this does not always occur when rooting and you can reset that flag most of the time and flash stock firmware before sending your phone back in for warranty.
I am a retired programmer with too much time on my hands; as such, I wrote a complaint to a regulatory body about how I can't install the operating system I want on my device because it will render it unusable (if I can't call for help on a phone because of drivers, what good is it?). I received a response requesting an interview with an officer who specializes in anticompetition cases and I would like to make sure I have my eggs all in one basket.
The current mobile phone market I liken to the desktop OS market of the 90s, where you had companies like Xerox, Microsoft, IBM, and so on; in the 90s, there were antitrust lawsuits where a particular company was accused of intentionally creating barriers to customers seeking to install software by other companies on personal computers. Obviously, that was settled in the 2000s, but IMO it did appear to make a positive change even if we are still fighting against IE. This may not be relevant, but that's what my mind went to when I realized I couldn't uninstall the Play Store.
Nobody uses "cellular telephones" as telephones anymore; instead, they are mobile computers. Computers in the 80s/90s had plenty of OS options (you may recall using OS/2 or BSD), but you can't do that with mobile computers... is that a good thing?
In my retirement, I'd like to develop and build a mobile phone operating system that is not android (nor lineageOS); this would either be Linux or BSD-based with a simple package manager, but the user would have the option to compile their own software also. This would ideally *not* hinder the underlying function of the device (i.e. telephony), but I don't see how manufacturers could be compelled to provide binary drivers. The current mobile market makes it obviously a very high barrier to entry for any who want to develop new operating systems for mobile computers. Is this anticompetitive? Perhaps not, but I'd like to hear some opinions and if you would kindly point me towards some resources I would appreciate it.
IMO the OS is not the problem - a command line based OS can be written by any talented student nowadays - preferably in C++, yes there are enough templates on the Internet, it is the device drivers what have to fit the hardware that make the whole thing difficult. I know that some OEMs put their device drivers' source code to the public.
jwoegerbauer said:
IMO the OS is not the problem - a command line based OS can be written by any talented student nowadays - preferably in C++, yes there are enough templates on the Internet, it is the device drivers what have to fit the hardware that make the whole thing difficult. I know that some OEMs put their device drivers' source code to the public.
Click to expand...
Click to collapse
To install a new OS on a phone, the phone must first be booted into a bootloader such that the 'image' of the OS can be loaded. The image for the OS should be built with the drivers present such that when booting, the OS kernel can load the relevant drivers as it probes the hardware in the phone, and then the software installed on the user layer can access that hardware through the relevant system calls. How possible is it for the bootloader to load a custom OS in the general sense? The majority of instructions I find are on enthusiast/developer websites with the actual manufacturers giving basically no input (that is to say, I haven't seen on manufacturer's websites or instruction manuals where they give instructions for booting your choice of OS).
Would it be fair to say that mobile developers, like Google/Samsung/LG/Amazon/etc are restricting users from being able to install their own OS on their device? Is driver access a reasonable thing to ask for?
Again, I'm retired, so I have time on my hands, but I'm old and there's realistically not a lot of that time left. I don't want to try developing my own BSD-based mobile OS if there's no way for me to install it on my own devices; that effort could go into another project if it is otherwise wasted. I suppose it is worth asking whether I should bother returning the bureau's request for an interview.