Shouldnt Samsung provide updates for the latest security patches like any other manufacturer?
My tqb has updqte from april 2018
Just a noob question
Google puts out monthly security patches. If you're on a Google device (i.e. Pixel XL) you'll get the monthly if you use their Project Fi service. As for everyone else the manufacturer decides when to create a new patch and then the carrier has to agree to release the patch. Some companies can take months before they put out a new patch.
farzii said:
Shouldnt Samsung provide updates for the latest security patches like any other manufacturer?
My tqb has updqte from april 2018
Just a noob question
Click to expand...
Click to collapse
If you haven't been paying attention, most Android vendors have a pretty sloppy OTA software update schedule. There are of course some exceptions, specially when it comes to the more popular phones. However, tablets, being the unloved child of the Android ecosystem, receive significantly less love and resources even from respectable vendors like Samsung. I own a 2014 Tab S1, and its security updates have always been few and far between. After two generations, it looks like the situation hasn't changed much.
Related
https://www.dropbox.com/s/bgce2efur8tq1ot/Screenshot_2017-05-13-17-13-44.png?dl=0 She said it was not compatible yet it got the wifi alliance http://www.wi-fi.org/content/search-page?keys=SM-A310F :confused: I think it's true because only the a5 2016 and a7 2016 got it but the a3 2016 hasn't?:crying:
Based on the existence of the certificate the update exists and is/was already under testing.
The only possible reason not to release it if they f*cked up the optimization of touchwiz for nougat like they did before a few times, resulting in failure to release updates to below flagship devices (like S4 mini).
The A36 is marketed as an ultra mid range device, so if it happens again despite their promises they could probably say goodbye to mid range buyers for once.
Let me explain: power users know Android. They (we) know that with every major update it's more and more optimized and less demanding on hardware, but Samsung seems to have a trouble following that trend with tw. They almost do the opposite, while people demand updates, and it's also in the interest of Google, so they have already warned manufacturers to do their best on the matter, specially Samsung after their past neglections. This topic has a great influence on our preferences and despite the other fields Samsung devices excelling in our eyes, it could change the situation. Now, most simple users choose devices based on our opinions. They ask us for advices. If I prefer Samsung devices, 100-150 people around me will prefer Samsung too based on my opinion; but if I prefer another brand instead, they will buy their devices instead. Now imagine how the numbers come with a lot more power users exisiting in the world, not just me.
The nougat update for A36 (having the broadest market amongst other A and J series devices thanks to it's handy size, yet powerful hw and quality housing) is a big opportunity to show us they have changed their attitude towards mid-range users, something people and Google are waiting for a long time, so they know it would be a disaster for them to back out from it in the final moments. I hope they won't.
I hope they release it but it explains why a7 and a5 2016 got nougat before the a3
link is broken
...if I get Nougat on my A3 2016...I won't ever enter this forum again.
Spreading negative information like this by pointing broken links as source is 3rd grade child stupidity.
It's not my fault if it doesn't work I saw it myself
Anyway if you want the link it's here https://www.dropbox.com/s/p9w3d54sk2fvguj/Screenshot_2017-05-18-18-20-37.png?dl=0. Next time don't swear at me.
arif8912 said:
Anyway if you want the link it's here https://www.dropbox.com/s/p9w3d54sk2fvguj/Screenshot_2017-05-18-18-20-37.png?dl=0. Next time don't swear at me.
Click to expand...
Click to collapse
These support guys don't know what they are saying... "I'm afraid it's not compatible" => there is no such thing. If they make a compatible build than it is compatible, simple as that. Also, when I've asked them, I got the response that IT IS GOOGLE WHO MAKES THE UPDATES, THEN THE CARRIERS REVIEW IT AND RELEASE IT. Yes, this is how it should be ideally if there would be a flexible hardware abstraction layer, but sadly it is Samsung who has to build the update after Google releases the source, and before carriers can deploy it... When I had to rate the conversation I wrote them that their support department has no access to proper information even about HOW updates work which is very troubling for conscious users who chose Samsung because of Android (+their quality hardware) and expect them to properly provide updates for their ultra mid range devices too, not just for their overpriced flagships.
http://www.samsung.com/tr/support/newsalert/100061 A3 2016 update got delayed to 29th may-2nd june
Verizon Z2 getting system update.
It's a fifty-something megabyte security update. :crying::crying:
Lol, I thought the same thing, good to have e the security update tho! ..... In February ?
What's bad about receiving a security update?
Well, a few things are disappointing about receiving a December security update in February.
December patch does not include protection for the Spectre vulverability.
Android Oreo has been available to OEMs for 6 months now and the Z2 Play - Motorola's second in line phone - is still waiting to receive an update.
... My watch just got updated to Oreo today. Did you hear that Lenovo? My watch! :silly:
Caldair said:
Well, a few things are disappointing about receiving a December security update in February.
December patch does not include protection for the Spectre vulverability.
Android Oreo has been available to OEMs for 6 months now and the Z2 Play - Motorola's second in line phone - is still waiting to receive an update.
... My watch just got updated to Oreo today. Did you hear that Lenovo? My watch! :silly:
Click to expand...
Click to collapse
Your watch runs Android Wear, not Android. There is a huge difference in the code required to be modified, doubly so because Android Wear watches are all essentially running one of two processors, have the same RAM and ROM, and have similar screens.
Phones have more options, between screen types and resolutions, RAM and ROM sizes (and types and manufacturers), CPUs and modems, and there is significant difference in software.
The fact it's February and December is just being released (even my unlocked Z2 play just received December security patch) is disappointing, but Oreo is being actively worked on and a speak test was already released. Six months isn't terrible for a major OS update, though in reality it's closer to a year and change (very early code is sent to manufacturers with P being out last September).
If producing cell phones were easy you'd be doing it yourself and the hundreds of crowd sourced companies would have been able to do it.
Sent from my SM-N950U using Tapatalk
Caldair said:
December patch does not include protection for the Spectre vulverability.
Click to expand...
Click to collapse
The arm A53 of the snapdragon 626 used into the moto z2 play is not affected by either of the two bugs and the related patches are useless!
Source: https://developer.arm.com/support/security-update: "Only affected cores are listed,*all other Arm cores are NOT affected." The arm A53 is not listed.
Inviato dal mio Moto Z2 Play utilizzando Tapatalk
_Dennis_ said:
Your watch runs Android Wear, not Android. There is a huge difference in the code required to be modified, doubly so because Android Wear watches are all essentially running one of two processors, have the same RAM and ROM, and have similar screens.
Phones have more options, between screen types and resolutions, RAM and ROM sizes (and types and manufacturers), CPUs and modems, and there is significant difference in software.
The fact it's February and December is just being released (even my unlocked Z2 play just received December security patch) is disappointing, but Oreo is being actively worked on and a speak test was already released. Six months isn't terrible for a major OS update, though in reality it's closer to a year and change (very early code is sent to manufacturers with P being out last September).
If producing cell phones were easy you'd be doing it yourself and the hundreds of crowd sourced companies would have been able to do it.
Sent from my SM-N950U using Tapatalk
Click to expand...
Click to collapse
While some of what you say about watches is true (similar processors and other hardware) they definitely run Android at their base. The version of android that Wear devices run may be pared down, but it is still Android. Android Wear is an app, effectively a skin/launcher for Android.
Saying they don't run Android is like saying my Nexus Player doesn't run Android because the Leanback Launcher looks different from the launcher on your phone.
Caldair said:
While some of what you say about watches is true (similar processors and other hardware) they definitely run Android at their base. The version of android that Wear devices run may be pared down, but it is still Android. Android Wear is an app, effectively a skin/launcher for Android.
Saying they don't run Android is like saying my Nexus Player doesn't run Android because the Leanback Launcher looks different from the launcher on your phone.
Click to expand...
Click to collapse
It would be closer to saying Android != FireOS except fireOS and Android are closer the Android and Android Wear.
A lot of code is removed in Android Wear vs Android (~950MB for pixel update, 350MB for Watch Sport).
The core is based on the same code, but it's not the same thing.
Sent from my SM-N950U using Tapatalk
Caldair said:
Well, a few things are disappointing about receiving a December security update in February.
December patch does not include protection for the Spectre vulverability.
Android Oreo has been available to OEMs for 6 months now and the Z2 Play - Motorola's second in line phone - is still waiting to receive an update.
... My watch just got updated to Oreo today. Did you hear that Lenovo? My watch! :silly:
Click to expand...
Click to collapse
So, sell it on swappa and get something that you'd be more satisfied with.
Slow updates from Motorola is no secret.
Hi guys, sorry I know it has been asked months ago but now the V30 / V30+ Oreo update is released, please can anyone let me know if Project Treble is enabled with it? Coming from a V20 with shocking, appalling update releases (Still on a 2017 security patch as I write this), this really is important. Many thanks.
No official Treble support by LG. Unofficial though (repartitioning and flashing treblelized LOS 15.1).
GrazzaD said:
Hi guys, sorry I know it has been asked months ago but now the V30 / V30+ Oreo update is released, please can anyone let me know if Project Treble is enabled with it? Coming from a V20 with shocking, appalling update releases (Still on a 2017 security patch as I write this), this really is important. Many thanks.
Click to expand...
Click to collapse
Treble doesn't matter in this regard.
LG has promised updates for V30 and G6 every 90 days (starting with Oreo) for THREE YEARS so they would be placed on Google's endorsed business program.
You will get that, with or without Treble. Treble will not make OEM/carrier push out updates and faster than they wish.
LG has NOT made similar promise with 2018 G7 and V35 (which launched with Oreo and has official Treble). So, will be interesting to see if they also get at-least 90 day updates.
Treble makes updates technically easier for OEM/carrier, but does not mandate them.
Whereas, Google's endorsed business program DOES mandate updates, and V30 will have updates with or without Treble.
Android Enterprise Recommended requirements
Security update support: 90-day security updates
Major update release support: Support current shipping release + one letter upgrade
Click to expand...
Click to collapse
See? Treble doesn't matter for updates.
So, now that V30 has Oreo we will get updates every 90 days, supposedly for THREE years.
ChazzMatt said:
Treble doesn't matter in this regard.
LG has promised updates for V30 and G6 every 90 days (starting with Oreo) so they would be placed on Google's endorsed business program.
You will get that, with or without Treble. Treble will not make OEM/carrier push out updates and faster than they wish.
LG has NOT made similar promise with 2018 G7 and V35 (which launched with Oreo and has official Treble). So, will be interesting to see if they also get at-least 90 day updates.
Treble makes updates technically easier for OEM/carrier, but does not mandate them.
Google's endorsed business program DOES mandate updates, and V30 will have updates with or without Treble.
Android Enterprise Recommended requirements
See? Treble doesn't matter for updates.
So, now that V30 has Oreo we will get updates every 90 days.
Click to expand...
Click to collapse
Check out https://www.android.com/enterprise/device-catalog/
Basically every LG phone is on that list by now (yes, also the G7 and V35).
But what im more annoyed by is that some LG low/mid end devices got an update to android 8.1.0, while the flagships are all stuck on 8.0.0
SGCMarkus said:
Check out https://www.android.com/enterprise/device-catalog/
Basically every LG phone is on that list by now (yes, also the G7 and V35).
But what im more annoyed by is that some LG low/mid end devices got an update to android 8.1.0, while the flagships are all stuck on 8.0.0
Click to expand...
Click to collapse
There's a difference between Android Enterprise Recommended Certification and just "Enterprise".
https://www.android.com/enterprise/recommended/
Stay current with updates
Android Enterprise Recommended helps ensure devices are up to date with regular security patches delivered within 90 days. Android Enterprise Recommended devices are also guaranteed to get at least one additional major OS update.
Click to expand...
Click to collapse
Security patches from device manufacturers delivered within 90 days, guaranteed for three years.
Click to expand...
Click to collapse
I quoted the specific Recommended requirements, like security updates every 90 days. Does just basic Enterprise have requirements?
Here's the Android Enterprise RECOMMENDED list, and G7 and V35 are not on there.
https://androidenterprisepartners.withgoogle.com/#!/results/browse-all/2
Thanks guys. LG made similar promises with the V20 and the update releases for my phone have been terrible. Really poor. My brother had a G5 and that's been even worse. I'll be switching to a Nokia (Treble enabled!).
GrazzaD said:
Thanks guys. LG made similar promises with the V20 and the update releases for my phone have been terrible. Really poor. My brother had a G5 and that's been even worse. I'll be switching to a Nokia (Treble enabled!).
Click to expand...
Click to collapse
Well, V20 isn't on Google's Enterprise Recommended program list. Neither is G5.
What does Nokia have that can even compare to the LG V30? Believe me, I looked at all the phones last year and V30 was the best, with too-big Galaxy Note coming in 2nd. Nokia has also dropped the headset jack and has no Qi wireless charging. At that point you might as well buy a Pixel 2 XL, which also comes in behind the premium features of the LG V30.
LG has to give at least security updates for three year's for the two phones on that Google Enterprise Recommended list -- V30 and G6 -- starting with Oreo. Every 90 days is the minimum, from what I can read. They can do more, if they wish.
So far, they have done it. We have 20A and 20B for US998. Europe H930 has had two Oreo releases. Canada H933 received their first Oreo update in May and are supposed to receive their 2nd this month, according to the carriers.
Custom ROMs from major dev groups of course have MONTHLY updates. V30 has several of those -- but I assume we are discussing official OEM/carrier updates?
OEMs/carriers will still release updates when they wish, even with Treble. Treble doesn't force them to release updates.
Whereas this commitment to Google's Enterprise Recommended program DOES force an OEM update schedule commitment for three years.
I think this was some of the reason for the delay in LG rolling out Oreo for V30... LG knows once Oreo is released, the regular updates have to start for all the variants in this program.
I'm not defending LG horrible update history for other devices. (Motorola is equally bad, for the last phone I owned.) But I'm curious to see how LG phones which do have Treble (V35, G7) fare vs. those which are on this Enterprise Recommended program and which don't have Treble (V30, G6). Hopefully, LG will improve on ALL current devices, but this Google Enterprise Recommended program holds their feet to the fire.
As Huawei Mate 10 pro was shipped with Android 8 last year I believe Mate 10 Pro also was a part of the Project Treble initiative. If that is so, is it correct to assume that we will soon see an OTA update for Android 9 to the Huawei Mate 10 Pro? And if so, does anyone know anything about the timeline? Like when can we expect to receive Android 9?
Project Treble is a major re-architecture in the way Android works. In essence, it separates the Android operating system (the Android 'framework') from the vendor Hardware Abstraction Layers ('HALs') that allow for the OS to work with the device's hardware
Click to expand...
Click to collapse
There have been a few OTA updates including safety patches until August 2019. So that is all good, but when I look in the "About Phone" in settings I am still on Android 8. As I am running this Mate 10 unrooted with a stock ROM I am really looking forward to Android 9 update, and have been checking frequently for new updates without luck.
Anyone knows more about this? Any set date or rumors about an upcoming update to Android 9 for the Mate 10 (pro)?
Currently there is Public beta going on if you are lucky for it to be available.
Date unknown. Probably sometime after the Mate 20 released.
Im in the same boat. Waiting for updates to alot of promised features
that are still lacking in the Mate 10. If Huawei released Android 8.1 for people outside of
China we would already have them.
Instead they are quick to release PUBG and GPU turbo fixes cause we would rather have that than updates for
Camera and Slow Mo 960fps etc.
Second beta was just released. Will update on Friday.
Information from the official Huawei forum in Serbia says that rollout of the official EMUI 9.0 for Mate10 Pro will start on December 14th.
So the Emui is equal to the Android version as in when Huawei update/bump their EMUI to 9.0 that means they will also bump the core to android 9?
Ok, probably just me that have read to much into the Project Treble an the separation of HAL. Since I first read about the HAL last year I kind of figured that the mobile devices that shipped with Android 8 would get a really timely bump to Android 9, like within weeks only after the android bump. So in my mind I kind of expected the roll out of new Android to be almost close to equal to the end of beta for Android 9.
On a semi related question, iirc the back story of the Project Treble was that Google wanted to address the fact that manufacturers did not commit to keep their Android devices updated, and that most of the manufacturers has a short life span of updates. Which combined lead to ie some bad press regarding vulnerability for many older Android devices, along with a less desirable user experiences with aging Android devices. Not to mention the lack of abilities to take advantage of all the newer software improvements that follows each Android update each fall. There have been a couple of Google initiatives prior to Project Treble, without hardly any traction and without Google being able to force manufacturers to stay committed.
So with the Project Treble Google did from what I can remember,make it mandatory for join the Project Treble for those who shipped their devices with Android 8. In my mind that translated to all kinds of things. Like Google putting down minimum requirements for number of updates manufacturers had to commit to, the speed of which they release updates etc.
However, did Google in fact put any of those requirements into Project Treble? Can we in fact look forward to having ie set number of supported updates from manufacturers in the future? Or will the big brands still be able to ignore their customer base rapidly and push forward with new models and focus their energy towards people updating their devices and buying the next year model rather then keeping their previous model with less overall waste, less economic impact and a more sustainable hardware update factor?
Treble means it would be much quicker and easier for oems to update to the newest version of Android, but it would still have to be the OEM making the update and pushing it out to your phone (unless it's an Android one or pixel phone I don't think Google themselves creates the updates)
There are no mandatory commitments to speed or number of updates, I think the only requirement was must be able to boot aosp (but unless your bootloader is unlocked you can't flash aosp anyway)
They will not release the 9 in the near future because they will launch mate 20 in less than a month.... they don't want to hurt sales.
avatar_ro said:
They will not release the 9 in the near future because they will launch mate 20 in less than a month.... they don't want to hurt sales.
Click to expand...
Click to collapse
Yeah but not the final version we need the beta at least ?
punkerEVO said:
Treble means it would be much quicker and easier for oems to update to the newest version of Android, but it would still have to be the OEM making the update and pushing it out to your phone (unless it's an Android one or pixel phone I don't think Google themselves creates the updates)
There are no mandatory commitments to speed or number of updates, I think the only requirement was must be able to boot aosp (but unless your bootloader is unlocked you can't flash aosp anyway)
Click to expand...
Click to collapse
Well if Google didn't take any steps to enforce manufacturers to actually keep updating they should keep their mouth shut about it later when we will see as usual that android devices are lagging behind in version numbers.
I really thought Google went balls in and was brave last last year with Project Treble and put down some new ground rules for their OEM's. But now it seems treble is just as weak hearted as the previous attempts from Google. Well I guess the solution is custom ROM's.
Manufacturers will never keep updating unless they are pressured to do so, they will always chase the sale of the next device and try to maximize profit rather then committing to last years hardware is up to date. So I guess project treble was a nice idea but google lacked the balls to actually lay down the law and demand dedication. Spineless. And to think they once lived by the catchphrase "don't be evil".
Can you test in Europe? I know that the next person in China is testing k.b 1500 users !?
---------- Post added at 08:31 PM ---------- Previous post was at 08:30 PM ----------
Sorry Google translator is not the best.
:laugh:
hondasoma said:
Can you test in Europe? I know that the next person in China is testing k.b 1500 users !?
---------- Post added at 08:31 PM ---------- Previous post was at 08:30 PM ----------
Sorry Google translator is not the best.
Click to expand...
Click to collapse
Beta test in Europe is already opened. 101 per country
Hey,
i asked myself a question. I was informed a few days ago from Oneplus Community Forum, that Oneplus rolls out the Updates in a 3 Month Circle. Dont know that before, just thinked this phone get fast Updates like my old Samsung Note 9 wich is, by the way, on January 2020 Security Patch. Oneplus is on November 2019.
So 2 Questions.
Im right, that OxygenOS is very near to Stock/Vanilla Android with just e few optimations etc ? So nothing overloaded like OneUi from Sammy ?
And is it rihgt, that the OP7TPro is a fully Project Treble supportet Phone ?
If these 2 Things are right, im very courious why they have such a bad Update politic. I mean not general Updates..my 7t Pro runs so far so good without any Bugs or else. I mean the Google Security Updates wich fill critical Security issues, along with the Google OS itself. Oh and i heard in the Communityforum, that Oneplus does this Job better back in the Days with OP6 Series for example. Is that right ?
Treasarion said:
Hey,
i asked myself a question. I was informed a few days ago from Oneplus Community Forum, that Oneplus rolls out the Updates in a 3 Month Circle. Dont know that before, just thinked this phone get fast Updates like my old Samsung Note 9 wich is, by the way, on January 2020 Security Patch. Oneplus is on November 2019.
So 2 Questions.
Im right, that OxygenOS is very near to Stock/Vanilla Android with just e few optimations etc ? So nothing overloaded like OneUi from Sammy ?
And is it rihgt, that the OP7TPro is a fully Project Treble supportet Phone ?
If these 2 Things are right, im very courious why they have such a bad Update politic. I mean not general Updates..my 7t Pro runs so far so good without any Bugs or else. I mean the Google Security Updates wich fill critical Security issues, along with the Google OS itself. Oh and i heard in the Communityforum, that Oneplus does this Job better back in the Days with OP6 Series for example. Is that right ?
Click to expand...
Click to collapse
Yes almost stock
No idea on the 2nd question
And there not the best for updates seems to be every 6 weeks or so
OnePlus are... Weird.
They run by this every 2 month update policy but here's the thing.
Lest take this as an example. It's end of January now, and February patch is a week or two away at tops, but they still release an update with January patch, instead of waiting that week or two and be fully in line with security patches.
OnePlus is probably closest to stock Except pixel phone. But I feel they are slowly drifting away form it, in my opinion, the implementation of OxygenOS is really poor.
And yes, this phone is 100% treble supported. (Which one would think would make updates fasters, but I guess not).
Could someone explain to me why the security updates are so important for some? What do they change for everyday user? (I'm asking seriously now, no hard feelings).
The only thing that needs fixing/updating asap for me is Horizon light, and this should be done much sooner. Apart from this everything is working fine, so I rather hesitate to update to not break something else, unless security update fixes the bugs, makes it more functional, faster or more battery friendly