Ever since the release of android, there's a boost in the requirements of people and the development is also upto the mark. ever year google is releasing its new api level of android. Now,the time came for us to discuss about the furthur api. Should google stop working on releasing a new api level greater than android p? Even Microsoft had stopped at windows 10 and started making windows 10 as most secure rather than working on new os like windows 11 or something....
Should google also start working on security and performance issues rather than working on a new api level amdroid?
Let me know. Thanks to the developers in advance :laugh:
sri_chandu said:
Ever since the release of android, there's a boost in the requirements of people and the development is also upto the mark. ever year google is releasing its new api level of android. Now,the time came for us to discuss about the furthur api. Should google stop working on releasing a new api level greater than android p? Even Microsoft had stopped at windows 10 and started making windows 10 as most secure rather than working on new os like windows 11 or something....
Should google also start working on security and performance issues rather than working on a new api level amdroid?
Let me know. Thanks to the developers in advance :laugh:
Click to expand...
Click to collapse
Windows is still doing feature updates, just stop the name game, and charging for major updates.
Sent from my perry_f using XDA Labs
After releasing an android api,within less than a year,new api level is being introduced and people just go behind the latest android version, leaving their existing device (even if the device is a flag ship) just only for the one reason...."latest android" ?
sri_chandu said:
After releasing an android api,within less than a year,new api level is being introduced and people just go behind the latest android version, leaving their existing device (even if the device is a flag ship) just only for the one reason...."latest android" ?
Click to expand...
Click to collapse
Issue is with manufacturers not wanting to implement updates.
Google is trying to mitigate that with treble, bypassing the manufacturers and updating the devices directly.
Sent from my perry_f using XDA Labs
Related
Updates for Android devices are always rolled by the gadget manufacturer, so every time Google introduces a new update we have to wait till the manufacturer of the device decides to roll it out, this obviously takes a lot of time and puts Android at a disadvantage against Apple and Microsoft.
For a Windows device irrespective of the manufacturer if Microsoft rolls out an update all can avail of that update through windows update. Android also being an open platform like Windows should be able to do the same.
If I have a software CD of Windows 7 I can install the software in any manufacturers PC and use it. I may just need to do some additional driver installation if required.
Why can't Android develop their platform to function in a similar manner so that once a new version of Android is released I can install it it any device and o fcourse put in the specific drivers to make it work if required.
With the approach of Microsoft looking very prominent now for both Smartphones and Tablets, this may just be a warning bell for Android, I hope they have their eyes and ears open.
Would be nice to know the views of others. As an Android user do you feel this would be a good step for Google?
kaus1108 said:
I may just need to do some additional driver installation if required.
Click to expand...
Click to collapse
The above is the key sentence in your post. The problem is that without the correct hardware drivers for your specific phone the OS may not be able to boot at all and will certainly have limited functionality - just look at the issues there are with trying to run leaded ICS / JB ROMs on phones that don't have an official version of the ROM available with the correct drivers yet.
The reason that Microsoft is able to push out a new OS and have it (mostly) work on any manufacturers PC, with any hardware, is that all the hardware manufacturers are given alpha/beta copies of Windows to test their hardware on and to allow them to build the drivers well in advance of the OS being released by the guys in Redmond.
Google don't do that. They release the OS immediately they have hardware support and compatibility for their devices - and let everybody else deal with the aftermath
windows is the opposite from open platform!
android is an open platform.
the phone makers are free to use android as they wish, they can decide if to upgrade or not.
google only realeses the source code.
XDA is there for providing the latest update.
My phone was supported by Samsung till Gingerbread. But I got jelly bean from XDA devs just after a week after the source code release.
But it does have some bugs which cannot be solved without Samsung's help.
But if you wanted the fastest OEM updates, buy a Nexus.
But 50% of the people are normal users who do not care about updates and new android versions.
Sent from my GT-S5830 using Tapatalk 2
SimonTS said:
The above is the key sentence in your post. The problem is that without the correct hardware drivers for your specific phone the OS may not be able to boot at all and will certainly have limited functionality - just look at the issues there are with trying to run leaded ICS / JB ROMs on phones that don't have an official version of the ROM available with the correct drivers yet.
The reason that Microsoft is able to push out a new OS and have it (mostly) work on any manufacturers PC, with any hardware, is that all the hardware manufacturers are given alpha/beta copies of Windows to test their hardware on and to allow them to build the drivers well in advance of the OS being released by the guys in Redmond.
Google don't do that. They release the OS immediately they have hardware support and compatibility for their devices - and let everybody else deal with the aftermath
Click to expand...
Click to collapse
Thank you for the response and I do agree with what you say and the key to it is that there are certain things that Microsoft do and Google don't and how it is going to impact users in the future.
I remember when I moved from Windows Vista to Windows 7 all the Vista drivers were functioning allright after installing Windows 7 and I have also faced situations where I did not have certain drivers but the PC still functioned on generic drivers provided in the Windows software.
Don't you feel it would be much better if Google just released a Jelly Bean OS and left it to us to install it and I am sure that based on devices already in the market those drivers can always be included in the OS and each phone would pick its own based on its hardware. Only the new devices would need new ones which Google may not be able to provide. If this were true today I would be installing JB in my Galaxy S3 and not have to wait for Sammy.
djbijo said:
windows is the opposite from open platform!
android is an open platform.
the phone makers are free to use android as they wish, they can decide if to upgrade or not.
google only realeses the source code.
Click to expand...
Click to collapse
No, Windows is quite open. Apple is the closed one.
Sent from my MB508 using xda premium
When windows phone 8 is released, will the new apps released be available for specifically WP8 or will they also be compatible with WP7.8?
AkashtheBruh said:
When windows phone 8 is released, will the new apps released be available for specifically WP8 or will they also be compatible with WP7.8?
Click to expand...
Click to collapse
I guess it will depend of the developer.
It depends on how they are built (what version of the runtime they target). Just as today, you can build an app for WP7.1 (or 7.5 if you prefer, a.k.a. Mango) and it will only run on Mango or later... or you can build an app with the 7.0 SDK (if you don't mind the limited APIs available) and it will run on all WP7 devices regardless of version. In the future, devs will have the option to target WP7+, or WP8 only. Obviously, the new APIs that are coming with WP8 will only be usable by WP8-exclusive apps.
GoodDayToDie said:
It depends on how they are built (what version of the runtime they target). Just as today, you can build an app for WP7.1 (or 7.5 if you prefer, a.k.a. Mango) and it will only run on Mango or later... or you can build an app with the 7.0 SDK (if you don't mind the limited APIs available) and it will run on all WP7 devices regardless of version. In the future, devs will have the option to target WP7+, or WP8 only. Obviously, the new APIs that are coming with WP8 will only be usable by WP8-exclusive apps.
Click to expand...
Click to collapse
ahh I understand, Well in your opinion, do you think that the windows phone 7.8 apps will be made or will they just be shunned altogether?
Given the way that Microsoft is being tight-fisted with the WP8 SDK, you're definitely still going to be getting almost all WP7 apps for the next month or three. After that... harder to say. There are still WP7.x devices being launched, so developers who wnat the maximum audience will continue to use the older SDK, but a lot of people are going to be lured by the power of those new APIs. XNA may make it easy to develop games, but people who want maximum performance and real DirectX access are going to be (of necessity, aside from homebrew) using the WP8 SDK.
Hi guys just sharing an opinion piece I wrote about the future of Android.
My current theory is that eventually Android could be replaced by Chrome OS, or merged and it could happen as soon as the next major update (5.0)
My article is here and I just wanted to get some input from you guys: my fellow Android Enthusiasts,
exekias said:
Hi guys just sharing an opinion piece I wrote about the future of Android.
My current theory is that eventually Android could be replaced by Chrome OS, or merged and it could happen as soon as the next major update (5.0)
My article is here and I just wanted to get some input from you guys: my fellow Android Enthusiasts,
Click to expand...
Click to collapse
doesn't sound all bad! interesting thoughts.. thanks
Sent From My Paranoid Nexusâ´
The Thanks Button Is There
To Stop Thanks Posts Filling
The Thread.. Use It!?
Nice piece... And that first picture inspires me to make a Chrome Launcher/Chrome OS Theme.
Also, I think android should just natively support web apps that use HTML5 or Unity or whatever the Chrome Browser supports naively as if they were android apps except the big upgrade/catch is that it runs it natively like an app without an internet connection. So maybe android will just become the chrome browser but also runs android apps (which Google will call something else so that they aren't hanging on to the android name anymore and people will no longer call it android).
I also don't understand anything HTML or Java so maybe impossible
Sent from my SCH-I500 using Tapatalk 2
Android MAY be MERGED with Chrome OS... but it will NEVER be REPLACED by it.
Chrome OS is based on the cloud, and our phones not allways have an internet connection.
Nope it will not be Chrome OS. Things will get merged eventually but Android will remain:good:
it is so frustrating that they release phones so often with no chance to really refines them. then there is google that puts out versions of android before developers get a chance to master or migrate fully to the latter.
i heard the new storage security in android 11 can cause hiccups like slow loading and crashes due to the new storage activity due to the new security rules.
should i stay on android 10 just like so many stayed on android 4.x.x for so long to keep compatibility
Mainline it to the main Linux repo
Use mobian END or
If you want android Get the upgraded LOS port to your device and port it to AOSP using the android mainline kernel (now with the last Linux you can use any android version you want), with mainline drivers like freedreno etc... (You can use drm-hwcomposer) END or
If you want your stock rom like OxygenOS extract the GSI of the newer model of your phone, decompile apks, edit files etc... To match your hardware and reenable lost features or disable feature with hardware requirements. To make sure everything is working fork LOS and call it, merge it with the prebuilt GSI and modify it to work lawless with stuff like enforced selinux.
I'm doing this with my OnePlus 6T, my hope is to have the last OxygenOS that work flawlessly on mainline kernel and upgrade it until the hardware is not good enough, then I'll just use mobian or buy a new phone.
Given that Android is comprised of multiple disjoint components, about two dozen of which are encompassed in Project Mainline/Treble/Google Play system updates/etc., now mostly simply referred to as "Google System updates"...
"One of Google's biggest efforts for Android in recent years is to make updating parts of the operating system easier, cutting out the middlemen wherever possible to deliver updates directly to customers. Originally referred to as Project Mainline, the system is now called "Google Play system updates" or sometimes "Google System updates."
These updates are downloaded and installed automatically by the Play Store, with the installation finalizing whenever you decide to reboot your phone. Generally speaking, the system is designed to go unnoticed, a goal that Google has achieved with relative success."
Click to expand...
Click to collapse
I have asked this key pertinent question of everyone I can ever since project Mainline/Treble had been announced way back for Android 10 and have yet to get _any_ answer whatsoever that has any basis in published facts from Google.
The question...
For the two dozen core modules covered in project Mainline, for how long does Google update them over Google Play Update services on Android 10+ phones?
The answer...
Is it finite?
Is it forever?
Is it arbitrarily finite?
For how long are the two dozen core modules updated over Google Play for any given Android X+ device?
GalaxyA325G said:
Given that Android is comprised of multiple disjoint components, about two dozen of which are encompassed in Project Mainline/Treble/Google Play system updates/etc., now mostly simply referred to as "Google System updates"...
I have asked this key pertinent question of everyone I can ever since project Mainline/Treble had been announced way back for Android 10 and have yet to get _any_ answer whatsoever that has any basis in published facts from Google.
The question...
For the two dozen core modules covered in project Mainline, for how long does Google update them over Google Play Update services on Android X+ phones?
The answer...
Is it finite?
Is it forever?
Is it arbitrarily finite?
For how long are the two dozen core modules updated over Google Play for any given Android X+ device?
Click to expand...
Click to collapse
The "project mainline" is misleading. Here when I tak about mainlining I'm talking about running android with a generic Linux kernel instead of the fork. So you can basically update the kernel to infinity and so port every android version you like.
So basically now I'm porting the OnePlus 6t to aosp using android-mainline as kernel with drm-hwcomposer. So anything forked or something.