Related
Hello Everyone!
Let me start off by reaching out to the XDA Administrative staff. I would like to thank you for keeping this awesome place in operation. Without you, and the XDA community, I'm not sure Android development would be as vibrant. Also, if this thread is in the wrong location, please shift it to where you would like it.
I am an Android user, not a developer, and I feel the future of the Android OS is not headed where I want it to. I'm writing this post to see if anyone has any further thoughts on the matter.
Google is marketing Android as an Open Source OS. You are able to download the source, modify it as you wish, and then build it. If you are running a vanilla build of Android (i.e. Nexus S) you are able to alter your experience as you see fit. The issue I foresee isn't the fragmentation of the Android versions (which is still debated as an issue), but rather the fragmentation of the user experience.
When an end-user purchases a handset from most major carriers, they receive an Android device. Between different handsets, and carriers, the features that are available to a single user can vary exponentially (i.e. the inability to install APK files, bypassing the market, on AT&T devices). This device is still based on Android, but is it still Android?
I have no problem with manufacturers adding their own code to the Android system, as long as the core functionality is kept the same. When you begin to alter the basic functionality of the system, at what point is it no longer Android? Linux Mint is derived from Ubuntu, but it is no longer Ubuntu. The system is a derivative of Ubuntu. If the base of the OS is going to be altered drastically (by manufacturer or by request of carrier) it needs to be known that the device is not Android.
As I am most familiar with HTC Android devices, I will use HTC SenseUI as an example (although, as I think about this more it may not be the best example). The core functionality of the HTC devices is similar, but not entirely the same. Most of the default applications (Browser, Contacts, Dialer) have been altered to what HTC feels is more atheistically pleasing. However, these features are additions. They are not removing functionality from the device.
With my HTC Evo (by default) there are core functionalities removed. Without rooting my device, I am unable to tether via WiFi. Even when rooting, if I want to keep the 4G experience, I need to install a third party application to tether instead of simply using the functionality that was supposed to be built in to Android. Why? Sprint has decided to bake their own hotspot functionality into the core of the OS. Yet to use it, I am required to pay an extra $30 fee on top of my [i/unlimited[/i] data plan. I am not knocking Sprint, here. As long as I have used their service, I’ve had nothing but stellar performance and the price point is perfect.
I feel with this core functionality removed, my Evo is no longer Android. It’s simply Android-based, an Android derived OS. The problem with these manufacturers, and their Android-derived operating system, is the lack-luster experience the consumers get with the product.
I started my Android experience on an HTC CDMA Hero. It took me eight months to get any major software upgrades (The device ran Android 1.5 from factory). Why? Because it was taking so long for manufacturers to bake their Features into the OS. If I was not a techie, I feel this experience would have pushed me away from the Android platform. I fear this fragmentation that is occurring could be the downfall of the Android platform.
I want to be able to buy a device. I want to be running the newest version of Android. If I do not like the ROM that came on the phone, I want to be able to change that. But I do not want to purchase a phone with all of this baked in garbage, or aesthetic features that require me to wait long periods of times for my device to be upgraded to the newest version of Android. And, I hope that I am not the only person to feel this way.
So here is my idea, pending input from the Android community of course: An open letter, with a petition, to all members of the OHA requesting for Android devices to be Android! Unadulterated Android OS from Google (With minor modifications to ensure specific hardware is working properly). Requesting that we are given access to the entire device, that we paid for, without having to exploit the operating system to obtain the ability to modify it as we see fit. If a manufacturer, or carrier, does not wish to comply with this, they will not be able to market the device as being Android. Rather, the device is based on Android.
Honestly, I’m not sure what I am looking to accomplish. Maybe, just so they know we are just as interested in Android as they are. And that we want nothing but for Android to succeed. Or maybe, that we support Android being open source, but not being heavily modified to the point where it’s a bastardized.
What do you think?
Tim, I support you in your belief that carriers, not manufacturers, are taking the wrong turn by messing with the full functionality that people pay a hefty price to OWN!
Do we truly OWN what we paid for, or are paying for? I don't believe so, for example, the SAMSUNG Vibrant t959, aka the Samsung Galaxy S i9000, same phone but the carriers decided to have certain features removed from the phone, not be MADE without these features, the FM radio HW and the FFC. Many people know these features were REMOVED, due to the leftover molding and other " skeletons"! Would anyone want to have a carrier when they know that they don't want there customers to have the FULLEST experience, like it was meant to be?
Sent from my HTC MyDesireHD 4G!
I would also like to share with you that MANUFACTURERS creating these "skins", I'm going to use HTC Sense for my example, is actually NOT a bad thing at all!
HTC Sense has opened a huge amount of rich content and functionality to there users immensely! HTC Hub, HTC Locations for example! All these add ons are very useful to users and does NOT restrict the full functionality but yet BOOSTS its functionality!
Unfortunately though, carriers decide to take these hearty and supreme names and totally rip it apart by taking away functionality, features, and the most...a good user experience! For example, my phone..the HTC MyTouch 4G aka the HTC Glacier. I received it with something called Sense on it, but any owner knows that is NOT Sense! That is not HTC Sense! After burying myself in the bowels of my new phone, I now have a HTC Desire HD Rom on it that will stay on it until I get the new HTC Sense 2.3 update! The full HTC Sense is a good thing and I strongly believe its worth waiting for!
Sent from my HTC Glacier
I agree, but believe Android is a growing mobile OS. If Google did not push their mobile OS (and let manufactures do what they want). Android probably would not have last against the competition. Its all a survival of the fittest situation. Some people are going to make use of their phones others aren't. Too bad bloatware has been the success for some Android phones. Glad someone else noticed this. Thank you for your thread.
The fact that Android is open source will inevitably have benefits and downfalls.
Benefits being that carriers and manufacturers can add cool stuff. Downfalls being that they can remove good or add awful stuff.
However Google can't have double standards. If it's open source, it's open source, for better or for worse.
An advantage of OEMs participating is that more parties are contributing to coding for android. More innovative ideas are potentially contributed.
For techies this is particularly awesome as we can port awesome features that perhaps weren't designed for our phone and disable lame restrictions. By this way we potentially can have all software benefits of more than one company brand etc.
Being an ordinary consumer in this context can suck.
Tim, while I understand your frustration (trust me, I've felt similar over the past few months), I don't fully agree.
The heart of Android is that it is Open. Open Source is a part of the openness that envelops Android, but what is meant by "Android is open" is so much more. OEM's skinning their devices is part of it; carriers stuffing devices full of their crapware is part of it; heck, even manufacturers/carriers limiting devices' use in one form or another is technically part of it. I think that Google's model with Android is that people can use in whatever way they see fit (except, you know, literally stealing it and claiming that they made and own it) and adapting it to be the OS that they want. Android gives people the freedom to do with it what they like.
I think that Google hopes that carriers, OEMs and everyone else will use it for the better and add to the functionality and maybe even contribute to the Open Source project and thus to the greater Android community and the vision thereof. Sadly, it is not always the case and then you get situations where a carrier or an OEM will limit a device in some way for a quick buck (your example of tethering on the EVO being a good one). I think that what AT&T did/does on their Android devices is as a final product a good example of what Android is not intended to be, but their actions are, technically, still in the spirit of Android.
The way I see Android, it is about the freedom to do whatever you like. Android is then also more for the thinking person as there are literally hundreds of devices to choose from and each one has strengths and weaknesses when compared to the rest. You as a user need to consider what it is that you want from your device and then select the device that is the most suited to your needs.
I want to be able to buy a device. I want to be running the newest version of Android. If I do not like the ROM that came on the phone, I want to be able to change that. But I do not want to purchase a phone with all of this baked in garbage, or aesthetic features that require me to wait long periods of times for my device to be upgraded to the newest version of Android. And, I hope that I am not the only person to feel this way.
Click to expand...
Click to collapse
You are not the only person that feels that way, I feel the same, which is why I've decided to get myself a Nexus S. It's tricky to get it to this country, but it'll be worth it. I realise that you're on Sprint which means that a Nexus device won't work, correct? A better petition IMO, would be to petition Google to release CDMA versions of their devices.
Sorry to say, but 4G is not derived from android. The phone itself will always support it, harware wise. So, what are you saying? /: Who are you complaining to? ROM chefs for not managing to make the 4G fully functional?
totally agree with you
he is complaining about gimped devices being marketed as android devices. to sum up what i think his messages is; a device should not be called an android device if it is not fully capable of all it's natively supported features, wireless tether, root access etc. but rather should be called android based device.
Good idea but never going to happen. This is driving me away from this platform...
Sent from my SGH-T959 using XDA App
I'm curious as to what functionality we can get by simply rooting. I'm not seeing the huge deal I may be missing something so I'm asking
Sent from my Incredible using XDA App
To me, they should just change the launcher and add their own apps in (NOT replacing) and not touch other stuffs already. If totally not changing the OS makes them look alike. To me, thinking about Windows phone 7 in the future. Imagine seeing so many people holding a phone that has the totally same UI, its like seeing a Sony Ericsson X10 and a HTC Desire totally same except that the casing is different.
Technically, the fact that its open source is supposed to help the majority of OEMs, and in turnfilter down to end users as price cuts/ feature enhancements.
But premium features are premium features. You want some kind of 4g? You wont be getting it from end users at xda - it will come from manufacturers who build the radios and APIs into the device.
Android is a very modular os... if you want something all you have to do is a bit of research and buy the device that fits you best. If you go with one of the other systems you will simply have less choice. That is why android is cool.
aint gonna happen guys, doesnt make good business sense to make a device that does everything, why sell one model when you can sell two!
you can pick up any device out there and say, "wouldnt it be cool if it had VGA out or HD camera or x y z", they wont do it, and the same goes for the OS as well.
Open source has an inherant flaw, and that is its fragmentation, everyone believes it should be going in a direction they would like (including yourself). at the moment its not suffered as much as its desktop cousins probably because of its market place keeping one common aspect through all devices but give it time and you will be right, it will lose its "android" identification
If you want an alternative and a device that keeps its personality then get an Iphone or a new WP7 device at least until they crack that wide open too. Its a bit ironic really that WM may well suck but its very customizable and has been consistant throughout the ages
evo4gnw said:
he is complaining about gimped devices being marketed as android devices. to sum up what i think his messages is; a device should not be called an android device if it is not fully capable of all it's natively supported features, wireless tether, root access etc. but rather should be called android based device.
Click to expand...
Click to collapse
But that's just the thing isn't it? Android can probably support ANYTHING. But because of that, you aren't supposed to release hardware that isn't as flexible? That to me.. is just looney.
Hello,
Im currently writing an academic paper on android and openness in my master's programme. If all goes well, it will be submitted for a conference soon.
I'm looking for your opinions on having an android device open for operating system level modifications or not. As you may know, some phones have a signed bootloader such as the Motorola Milestone, t-mobile g2 (who made the phone reinstall stock OS when breached), and probably many others. Google however, make their devices open, even though they are sold as consumer devices. Many others do not bother to install circumvention mechanics.
Obviously, the people here will be biased towards allowing modification to the OS, therefore, i would like to get a discussion going, to discern what problems and possibilities you see in the long run for hardware manufacturers.
1. Does the possibility of making OS level modifications affect your willingness to purchase an android product? i.e. do you check if it can be modified before buying? And how much of an impact does it make on your desicion?
2. Why do you think hardware manufacturers put in measures to prevent custom android OS builds to be installed? Put on the corporate hat and try to see their strategy.
3. Do you think manufacturers have anything to gain by making devices open and free for modification, with source code for drivers and the like publically available?
I would really appericiate your opinions and discussion!
1. Does the possibility of making OS level modifications affect your willingness to purchase an android product? i.e. do you check if it can be modified before buying? And how much of an impact does it make on your desicion?
As a beginner app developer, this has yet to bother me. I do enjoy being able to add apps that add functionality to my phone but I haven't bothered to get down into the "root" area. So no I do not check nor does it impact my decision...I own a Samsung fascinate by the way
2. Why do you think hardware manufacturers put in measures to prevent custom android OS builds to be installed? Put on the corporate hat and try to see their strategy.
My opinion on measures to prevent changes is all about PR and performance. If enough people hacked a phone and the hack caused the phone to work below is ability then the only news report you will see is the phone sucks.
3. Do you think manufacturers have anything to gain by making devices open and free for modification, with source code for drivers and the like publically available?
This is also a give and take if question 2 is not of a concern to them, then its def a gain for the company and to all of the developers out there that do search for the best phone and nick pick around until they find it.
Are there enough of those kind of people out there to affect a companies buttom line. Maybe not yet but in another couple of years who knows.
1. Does the possibility of making OS level modifications affect your willingness to purchase an android product? i.e. do you check if it can be modified before buying? And how much of an impact does it make on your desicion?
It hasnt yet been a deciding factor on which device to get, primarily because sooner or later they all get cracked open.
2. Why do you think hardware manufacturers put in measures to prevent custom android OS builds to be installed? Put on the corporate hat and try to see their strategy.
One reason could be that the carriers demand it as a way to keep any revenue that they get from the preinstalled bloatware.
3. Do you think manufacturers have anything to gain by making devices open and free for modification, with source code for drivers and the like publically available?
The percentage of people that actually tinker in this area is very slim, so the manufacturers most likely don't see that as a big market opportunity.
Don't have any answers, but would like to read your paper when done...sounds interesting and a Masters Thesis is always fun to read! LOL
It's not a thesis, just a short article. I might make a survey for it but I need to ask the right questions.
Not all devices get fully customized, root is common, but in my phone for example it is not possible to load a custom kernel, as the bootloader checks for signed code (Motorola's secret key). There's been a massive uproar from the owners of the Milestone, as people didn't expect to be hustled like that when getting an android phone. The main problem is of course, that Motorola takes a long time to release updates. Even as of today, Froyo has still not been released for my phone by Motorola.
While I am not sure about it, I suspect Sony Ericsson X10i owners are in the same boat, and they will get a really rotten deal, seeing as 2.1 has been officially declared the last version the device will recieve. Yet, an enthusiast could release a perfectly fine version of 2.3 if the phone accepted custom firmware and he had access to drivers etc.
So basically, you buy a piece of hardware that is very capable, but The Company decides for you which software you could run.
Imagine if you bought a Windows Vista PC right before Windows 7 was released, and the only way you could get Windows 7 on it was if that particular PC manufacturer released an official update containing all it's bloatware and applications you don't want. Since the update needs to go through all kinds of verifications and approvals, it might be delayed for a half a year, or maybe 9 months, after the new OS release. Why do we accept this on our phones and tablets?
Hi,
1. Does the possibility of making OS level modifications affect your willingness to purchase an android product? i.e. do you check if it can be modified before buying? And how much of an impact does it make on your desicion?
For me personally, yes, most definately. I like to be able to get in and play, see how things work, change stuff. And i think custom ROMs IMO are a big drawcard of Android.
2. Why do you think hardware manufacturers put in measures to prevent custom android OS builds to be installed? Put on the corporate hat and try to see their strategy.
To try and ensure the device works as they want it to. Minimise support costs etc.
3. Do you think manufacturers have anything to gain by making devices open and free for modification, with source code for drivers and the like publically available?
Definately. Encourages improvement of existing features, and development of new stuff beyond the manufacturers initial product scope, which can be integrated in future products.
Android OS its self is an example of this - the developer community is writing apps, logging bugs, and contributing code to the benefit of future releases of Android, which in turn benefits device manufacturers.
- jc
my two cents
1. Does the possibility of making OS level modifications affect your willingness to purchase an android product? i.e. do you check if it can be modified before buying? And how much of an impact does it make on your decision?
>> Personally, I feel like the ability to modify my phone at the core level is something I as a power user can use to tailor my phone's experience in the way I need to make it the most efficient device it can be. This is especially necessary as my phone is my primary connectivity device (I really only use my laptop for things the phone just really isn't capable of handling yet, such as video conversion)
2. Why do you think hardware manufacturers put in measures to prevent custom android OS builds to be installed? Put on the corporate hat and try to see their strategy.
I think this is less the decision of the manufacturers and more of the carriers themselves. This really is because each device has to be tailored to be sold to the average user, rather than power users (read: 85-90% of people who will read this reply) and as a result is designed with an experience in mind. To the suits, anyone who take a phone that is supposed to have a specific experience in mind, and changes that, it becomes a different phone, and anyone who looks at that phone will see that. This means, TMo/HTC can't sell a G2, because everything that my office mates will see when they look at my phone is my android customizations, not a G2. my office mate, who is shopping for a phone, can get an android phone anywhere... but they can only get a /G2/ from TMo/HTC. Similarly, if I like my G2 experience, when i get a new phone, i will be more inclined to continue enjoying that experience with a G3, rather than buying any on sale android phone and making it just like my last one. Hence the need to have a G2 experience on every G2 phone. Just my 2 cents. I am not a businessman, lawyer, or doctor.
3. Do you think manufacturers have anything to gain by making devices open and free for modification, with source code for drivers and the like publically available?
Yes, but nowhere near as much as they can get by keeping their cards close to their hand. see my answer to number 2.
This is a preemptive note about posting any new threads asking "when will honeycomb come to the gTablet?" or "why can't we do this because the Nook has it?" or "why isn't the sky blue today?"
Honeycomb is not available for the gTablet yet for the following reasons:
1. source hasn't even been released by Google yet
2. any port based on the SDK doth not a Honeycomb ROM make
3. we do not even have libraries (or source) from nVidia for Gingerbread yet
Until we have source from Google and nVidia, we won't have workable Honeycomb. There will be some ports, but until one of the above happens, we are not going to be getting Honeycomb. Best case is 30 days from now (roughly the end of March).
Any post asking about Honeycomb will be promptly closed and/or deleted.
This isn't about discouraging discussion about Honeycomb on the gTablet - it's about stopping the endless flaming and abuse and posting and complaining about something that has been answered multiple times - thus taking away from other progress and endeavors.
UPDATE 3/18/11 - We now have access to the Gingerbread libs needed for hardware acceleration, but in order to use them a complete rework of the github repo is required and a year's worth of merges and cleanups would need to be done. Slow going and no ETA.
UPDATE 4/12/11 - http://www.androidcentral.com/nvidia-stop-supporting-harmony-platform-past-froyo
UPDATE 4/13/11 - http://developer.nvidia.com/tegra/forum/honeycomb-harmony#comment-6191
UPDATE 13 APRIL 2011
A lot has been read into a very short post about a Tegra development kit. I'd like to clear up a few points.
First, nothing changes in what we’re delivering to the open source community or customers. NVIDIA will continue to post the Tegra kernel to kernel.org and publish our Android code to our public git servers. Additionally, we will continue to make our BSP (codecs, GPU driver etc) available to all our hardware partners. We will continue to do this and nothing about these processes has changed.
For our partners' Android devices, NVIDIA provides support until the hardware partner chooses to no longer support the device. So, for instance, NVIDIA will support the Xoom on all versions of Android Motorola requests until Motorola ceases to support the Xoom. The same goes for ViewSonic with the G-Tablet, Notion Ink with the Adam, Acer with the Iconia, LG with the Optimus 2X and so on.
In relation to my original reply, that was a response to a specific question about a Tegra 250 Development Kit. Given the confusion, we will work with owners of Tegra 250 Development Kits individually to determine their needs. The term "Harmony" is an internal codename for the Tegra 250 Development Kit. It is not a tablet reference design. Each shipping tablet is a custom design with varying hardware components and requires a custom OS image from the OEM who made the tablet.
Finally, while we cannot support or give out third party peripheral drivers or provide the Android 3.0 source before Google does, we do want to explore whether we can assist the open source ROM makers. We will be reaching out to them today.
UPDATE 5/10/11 - There is now a pretty hacked together port of HC that has been ported to the gTablet - it is a mashup of other, authorized by Google tablets which have stock HC on them, and thrown together for Vega, Adam and gTablet. A lot doesn't work; it is not feature perfect..... it is only recommended for testing type users who are familiar with nvflash etc. and it is not built from source specifically for our devices. It is by no means official, nor is it what would probably be called "stable" - but it is as close as we've come to HC on the gTablet. Here is the post that has more information: http://forum.xda-developers.com/showthread.php?t=1065220
UPDATE 5/10/11 - Per Google I/O's Fireside chat today there will be no Honeycomb source released. Ever. You'll have to wait for Ice Cream Sandwich which will be out in Q4 2011.
UPDATE 5/14/11 - The ADAM/VEGA/ZPAD/GTAB port of the mashup Transformer/Iconia/Xoom Honeycomb systems is coming along nicely. See the above thread for more information. Good work to the devs involved in that project.
I have the 2012 Note 10.1 for personal use and have come to the unfortunate resolution that Android just isn't going to cut it from a business perspective. I am not putting the full blame on either the manufacturers or Android itself but without timely updates to a specific platform, I can not justify the use of these in a production environment. There is no way company can justify replacing their hardware yearly, or regularly, in order to get the latest features and security fixes that are provided in updates. Ignoring the additional features for the time being, from a security stand point there has to be a way to patch the devices in a timely manner. The additional features being provided drives the developers to migrate to the newer operating systems and leaving the old systems behind. A lot of times this creates a huge disadvantage in the fact you can run a particular application on one Android device but is unsupported on another.
Now to be fair. I am focusing on Android in this post but have tested Microsoft and iPad devices as well. All have certain advantages and disadvantages but the clear loser so far has been Android. If Android is going to survive in the business world, the manufacturers are going to have to step up and maintain their products actively for at least the full two years of their life expectancy.Android itself will have to hold the manufacturers accountable for keeping their devices maintained. From a personal use perspective, I think it is a great platform and love my Note 10.1. Would I like to see it get updated, I would love to see 4.4.2 on the device to allow me to run application I need that are no longer compatible with 4.1.2. However, I require vulnerability patches in a timely manner and that just isn't happening.
My last job had hired a full time developer to build a custom ROM and patch or update when needed for all the tablets being used on the floor. This approach worked for them because there was only one model in use across all departments.
You should blame Samsung for the late major update for GT-N80XX.
Android actively pushing regular update (minor & major).
Actually Samsung also pushing regular update, but it's only 1 major update (ICS to JB) & some minor/security updates.
If a business used the nexus tablets, they wouldn't have this problem.
theatomizer90 said:
If a business used the nexus tablets, they wouldn't have this problem.
Click to expand...
Click to collapse
Not necessarily true. Most current android version is 4.4.4 while my N7 LTE still sits at 4.4.3 with no update even spoken of. So if a business has data enabled tablets, they're still behind current version.
What OP posted doesn't really apply to large businesses. Between KNOX and other third party equivalents sensitive data is sandboxed and doesn't rely on the core B2C version of the OS to protect it. As much as Google may see Android's potential in the business environment no one I know in IT at a bunch of Fortune 1K companies is looking at mobile OS's (either Android or iOS) to replace desktop/laptops as "standard" issue. Tablet and smartphone apps have niche opportunities (commercial pilot manuals and logs, flight attendant passenger service tools, gate agent/hotel staff roaming terminals, sales people inventory access, remote staff automated forms, etc.) but migrating the entire enterprise to mobile architecture just doesn't make sense. So Android can't lose anything it never had and, outside Google's wishes, isn't seriously considered for. The lack of Chromebook adoption by the enterprise demonstrates their disinterest.
BarryH_GEG said:
What OP posted doesn't really apply to large businesses. Between KNOX and other third party equivalents sensitive data is sandboxed and doesn't rely on the core B2C version of the OS to protect it. As much as Google may see Android's potential in the business environment no one I know in IT at a bunch of Fortune 1K companies is looking at mobile OS's (either Android or iOS) to replace desktop/laptops as "standard" issue. Tablet and smartphone apps have niche opportunities (commercial pilot manuals and logs, flight attendant passenger service tools, gate agent/hotel staff roaming terminals, sales people inventory access, remote staff automated forms, etc.) but migrating the entire enterprise to mobile architecture just doesn't make sense. So Android can't lose anything it never had and, outside Google's wishes, isn't seriously considered for. The lack of Chromebook adoption by the enterprise demonstrates their disinterest.
Click to expand...
Click to collapse
Not sure if I totally agree with the application only being a niche market. I work for a call center and find that the tablets are becoming an indispensable tool. We have people walking the floor with these devices and using them to keep track of various statistics as well as using them to report potential issues. The ability to pull up data about current client information to respond in an almost instant manner has shaped things drastically. Having a sandbox is really great for protecting certain information, such as email, etc.. but can not protect the device data in flux, such as web browser content. If the system is compromised and access to the file system is obtained then all the data previously obtained becomes available to the attacker. Some measure can be made such as requiring Citrix as your primary form of connectivity but you are only pushing the security back to another device. The focus of this article was to point out the shortcomings of the this tablet as it pertains to the lack of updates.
Don't get me wrong, I truly love Android and will continue to use it as a personal device. However, there is no way I can risk releasing these devices into a production environment without the proper support. And yes, I blame the manufacturer for release and forget, and I blame Android for not enforcing the manufactures to keep these update. It is crucial to both parties to work together and produce something that is not just desirable but maintained for a reasonable amount of time. If Android could come up with a way to provide updates to devices directly and bypass the manufacturer they would have an unbeatable platform.
Zeab said:
Not sure if I totally agree with the application only being a niche market. I work for a call center and find that the tablets are becoming an indispensable tool. We have people walking the floor with these devices and using them to keep track of various statistics as well as using them to report potential issues. The ability to pull up data about current client information to respond in an almost instant manner has shaped things drastically. Having a sandbox is really great for protecting certain information, such as email, etc.. but can not protect the device data in flux, such as web browser content. If the system is compromised and access to the file system is obtained then all the data previously obtained becomes available to the attacker. Some measure can be made such as requiring Citrix as your primary form of connectivity but you are only pushing the security back to another device. The focus of this article was to point out the shortcomings of the this tablet as it pertains to the lack of updates.
Don't get me wrong, I truly love Android and will continue to use it as a personal device. However, there is no way I can risk releasing these devices into a production environment without the proper support. And yes, I blame the manufacturer for release and forget, and I blame Android for not enforcing the manufactures to keep these update. It is crucial to both parties to work together and produce something that is not just desirable but maintained for a reasonable amount of time. If Android could come up with a way to provide updates to devices directly and bypass the manufacturer they would have an unbeatable platform.
Click to expand...
Click to collapse
Anytime a serious security breach that can be used from without to effect changes on a device have come to light I have seen updates come out on all my tablets and phones, which is blessedly rare. Android does not operate in the way you are thinking. There is no need to constantly shove out security updates like windows. The system is pretty well secure unless you unsecure it yourself, new versions of the OS usually just add functions, however there is a current (when is there not?) RUMOR of a adobe bug on all versions of android lower than 4.0. Personally I still prefere windows for business simply because of ease of function and with baytrail cpu's and even more promising hardware coming this year I find no reason not to use windows for hard business needs if your business can benefit from tablet use. There are a plethora of cheap windows tablets coming and the current hp omni 10 is powerful enough to suit any light tablet buisness needs for just 299.00 if your business needs more power pay the premium for a surface pro with a full on i3,5,7 cpu fully capable of doing the work of a high end laptop. All that said, I feel Android is if anything more secure than a windows machine. Nothing comes in unless you invite it. Updates not needed until such time as Android can add base functionality in the realm of windows 7, and it is close imho.
Check the trends
Have to agree with Zeab. The university I work for is now supporting apple mobile devices but not android. And despite my having pressured for some support, what support is was for android devices is disappearing. Why ?
Android from one device to the next is different enough to make support difficult if not impossible. Providing advice on connections to secure servers and use of common software falls foul of the same issue.
Android device manufacturers have attempted to sequester their market by creating difference, but all they'll achieve is failure. Add to that the early obsolescence they have engineered and android is dying, even as its market share grows!
We now as a family have windows, apple and android devices. If I include TVs and media devices the list lengthens. The only option that provides continuity of operating system and software, and longer term support with updates is Apple. Given the way Microsoft has gone off the rails with windows 8.1 (I really do believe that OSs should make my computing experience easier, not harder), I think we will be going Apple in the future.
Maybe I'm the only one, but I am a long-time fan of the now-dead WebOS, (formerly PalmOS). Back in 2011-2013, I probably had 6 or 7 different WebOS phones, and found the hardware and the software to be superior in user experience than any others. The problem was that that was the big explosion era for Android and IOS, so WebOS got pretty overshadowed, and HP, (the new owners at the time), decided to axe any further development, and ended up selling the OS to LG, who has developed it further for TVs and stuff, (I don't have all of the technical details straight, but that's a superficial summary). Anyway, recently, out of nostalgia, I pulled out an old Veer, and bought a new Pre 2, and went back into the WebOS forums realm to get a fix of my old favorite, and I was pleasantly surprised to see the work of the community to keep WebOS alive. There is an archive of hundreds of app files available on ftp, (all abandonware available for free - even the paid apps from HP catalog), ongoing development of apps and patches to keep WebOS working with all of the changes in technology, (including updates to Preware - the unofficial dev app catalog, started way back then), and LuneOS, an open developers version of WebOS, which can be built for modern phones, and which was just updated - https://pivotce.com
I think the XC is a perfect candidate for LuneOS, being small, currently affordable, (one upside to the short lifespan of official support), and having pretty good specs. Plus, there's already plenty of foundational development needed for supporting porting, (Lineage, AOSP, and even a partly-working Halium - https://github.com/Halium/projectmanagement/issues/103). For anyone familiar with building/porting, the work needed to be done to build LuneOS for XC is minimal.
My problem(s): I am not familiar with building/porting. I am happy to test and learn, but I also currently don't have any regular access to a Linux computer, and even if I did, it would take me a looonng time to figure out from scratch what someone else could probably do in no time, since all of the elements are in place, (I checked with WebOS devs, and they said with what's available, building for XC is '... mostly a matter of configuration').
So, anybody out there with an XC want to do a build for us?
@harryharryharry @oshmoun ...?
Sorry, I'm not even remotely close to having the capabilities to pull a stunt like this, I think I'm currently in the same boat as you (minus the linux part)
Having said that, here's hoping someone more knowledgeable jumps in and picks up this interesting project. I'm willing and able to test and provide feedback as well of course.