Related
I've noticed that I seem to be missing a few updates that I expected I'd be one of the first in line for as a Nexus 4 owner.
Firstly, the Master Key vulnerability fix doesn't seem to have reached my phone. At least, according to Bluebox security scanner
Secondly, I still have no visibility of the new Google Maps redesign
My phone is a generic operator free Nexus 4 running stock (custom kernel though). Anybody else still waiting, or have I fallen off the automatic updates conveyor belt so far?
Where are you from? App updates from Google reach different parts of the world at different times.
thisisgil said:
I've noticed that I seem to be missing a few updates that I expected I'd be one of the first in line for as a Nexus 4 owner.
Firstly, the Master Key vulnerability fix doesn't seem to have reached my phone. At least, according to Bluebox security scanner
Secondly, I still have no visibility of the new Google Maps redesign
My phone is a generic operator free Nexus 4 running stock (custom kernel though). Anybody else still waiting, or have I fallen off the automatic updates conveyor belt so far?
Click to expand...
Click to collapse
We are sailing in the same boat. Rooted with only custom recovery rest stock.
vanmarek said:
Where are you from? App updates from Google reach different parts of the world at different times.
Click to expand...
Click to collapse
Based in the UK. If you've had the vulnerability patch already, did it come in the form of an app download or an ota update?
I'm in the UK and had the Maps update the day it was released.
thisisgil said:
Based in the UK. If you've had the vulnerability patch already, did it come in the form of an app download or an ota update?
Click to expand...
Click to collapse
Google hasn't released a patch for the vulnerability that's why you haven't gotten it. All they have done so far is release the code to their OEM's so they can patch their individual versions of Android. More than likely Nexus devices will get the patch in the 4.2.3 OTA whenever it gets released. In teh mean time their is an app in the Playstore, ReKey, that will address the vulnerability. Or you could just turn off install apps from unknown sources in the security settings which will also take care of the issue temporarily.
As for the other app updates they can take up to 2 weeks to deploy to all phones.
Had the Nexus 6P - but even with Franco kernel and normal use battery life wasn't long enough. Saw the release of the S7 Edge unlocked which was great so I went and picked it up from best buy last night. Big reason is the monthly update cycle and keeping everything patched from a security standpoint without the Verizon bloat and slow release cycles.
Went to check the patch level and saw "Android security patch level: May 1, 2016". Checked for updates and are none.
Anyone else experiencing this? Appears to be missing June for sure and the newly released July security patches.
kennedyd013 said:
Had the Nexus 6P - but even with Franco kernel and normal use battery life wasn't long enough. Saw the release of the S7 Edge unlocked which was great so I went and picked it up from best buy last night. Big reason is the monthly update cycle and keeping everything patched from a security standpoint without the Verizon bloat and slow release cycles.
Went to check the patch level and saw "Android security patch level: May 1, 2016". Checked for updates and are none.
Anyone else experiencing this? Appears to be missing June for sure and the newly released July security patches.
Click to expand...
Click to collapse
Yeah mine has the same update. Does yours have the briefing feed on the left of your home screen? I noticed mine doesn't like the carrier ones do.
Same here..
Alaris said:
Yeah mine has the same update. Does yours have the briefing feed on the left of your home screen? I noticed mine doesn't like the carrier ones do.
Click to expand...
Click to collapse
Yep - same with me - no briefing feed when you swipe left - nothing there.
Wonder whats happening - would hope Samsung provides updates to their own phone.. ?
I'm guessing it's because the phone just came out that they haven't released an update with the latest security patches yet. They probably have to set up their update servers for this new phone and a bunch of other behind the scenes stuff to get updates rolling. I would assume that it will get something within the next couple weeks and then continue to keep up with the other variants.
Does this variant of the S7 Edge have an unlocked bootloader?
No unlocked bootloader - just not tied to an individual carrier i.e. verizon, etc. with the extra bloatware.
Still no updates yet to the SM-G935U.
Ended up returning it and going back to my Nexus - no updates really sucks.
Has anyone figured out how to get briefing on the left screen. I used that a lot and i can't get it to work. Even went to the play store and Samsung store, got briefing but it won't let me enable it on the home screen settings...?
I've gone round and round with Samsung support about this particular unlocked device. The bottom line is that they are saying OTA updates for these devices might not be available because those are normally pushed through the carrier. They suggested to use their Smart Switch tool to apply updates. Even though this is a terrible idea and they should use OTA (with the invention of non-carrier WiFi these days ), I checked using this tool and surprise... there were no updates available.
I'll spare everyone the entire conversation, but this is how it ended:
"We understand. If you have an unlocked the latest updates for firmware and security can be done through Smart Switch. If you have checked for an update using Smart Switch and there aren't any currently available, we couldn't speculate on when that may change. In many cases this wouldn't be delivered OTA because OTA updates are normally pushed by carriers. Unlocked devices may not be able to get updates directly from the carrier currently being used. ^Jay"
Mine just updated today with the August 1st security patches. If had to guess, they waited until the Olympics were over since they handed these unlocked devices out to every athlete in attendance and they didn't want them receiving updates during the event.
Hopefully now that the unlocked models have received their first update, they will continue to get regular updates at the same time as other variants.
just checked for update - 164.13 mb ) ( g935v flashed to g935u)
Interesting
secsquirl said:
Mine just updated today with the August 1st security patches. If had to guess, they waited until the Olympics were over since they handed these unlocked devices out to every athlete in attendance and they didn't want them receiving updates during the event.
Click to expand...
Click to collapse
Thanks for posting this one, thats good to hear. I wonder if they will proceed further. Good to hear Samsung's infrastructure will support updates in the future. I wonder if its only for security patches or if they will do incremental updates to OS as well, like Android N for example.
Just got this tonight. I didn't have automatic update turned on but I checked and this showed up. Idk if i should do it or not.
I'm on T-Mobile with the SM-G935U. I got the update a few weeks ago and now it shows the Aug 1,2016 Android security update.
As far as root and bootloader unlock should i not do the update or just go for it?
Can the sm-g935U be flashed using DFS Tools? Does these codes bring up the diag menu?
##3424#
###366633#
Can someone please try those codes and see if the diag menu shows.
Thanks
PapaDocta said:
Can the sm-g935U be flashed using DFS Tools? Does these codes bring up the diag menu?
##3424#
###366633#
Can someone please try those codes and see if the diag menu shows.
Thanks
Click to expand...
Click to collapse
Those codes don't bring up anything. Neither does *#0*# - I'm still on the damned May 1, 2016 Security update and it doesn't seem to think I need one.
I hear Verizon and Google have released a ota of the Sept security patch for Verizon's pixels yesterday.. if you have a Verizon be sure to check for update manually in settings, about phone, software update..
I saw it on my Pixel XL this morning but not on my wife's Pixel. I have no details except the size of ~55MB since that is all that shows. It is not available for download in the OTA images or the factory images section. I assume it will not work over the standard OTA mechanism since the phones are rooted, and I have no interest in taking the patch blindly anyways.
The september 2017 Security Patch should have been released already. But due to some reasons, Google has delayed the upcoming monthly security update. The reason for the delay could be the release of a new stable Android 8.0.0 Oreo firmware update for Google Pixel and Nexus phone. Under the AOSP project, Google released 3 sets of monthly updates. One for the latest Android 8.0 Oreo, another for 7.1 Nougat, and finally the Marshmallow. Today, the Google Pixel XL device is receiving the September 2017 security patch OTA.
The first Google devices to receive the September 2017 Security Patch are the Unlocked Pixel XL 128 GB on AT&T and Verizon. That means, the US carriers shall receive the OTA update before the global roll out. The international variant of Pixel, Pixel XL, Nexus 6P, and Nexus 5X may receive the next security patch as soon as today. So stay tuned as we will list the update here.
The OTA update for AT&T Pixel XL brings the firmware build number OPR3.170623.007 dated September 5th 2017 level based on Android 8.0.0 Oreo. This an upgrade over the previous OPR6.170623.012 August 5th 2017 8.0.0 Patch.
This September OTA update comes in a very small OTA package. It weight about 50.61 MB in size. The changelog states the following.
This update fixes critical bugs and improves the performance and stability of your Pixel XL. If you download updates over the cellular network or while roaming, additional charges may apply. Update size 50.6 MB
Note: Google Pixel XL users have reported that the OTA notification shows that it is based on Android 7.1.2 Nougat, whereas the Pixel devices are already running 8.0.0 Oreo. However, upon update, the Android version is based on 8.0.0 Oreo and September 2017 security patch level. So it could be an error from Google’s side.
Download Google Pixel (XL) September 2017 Security Patch OTA update
One of the users for Google Pixel XL have managed to capture the latest OTA update from the LogCat file. September 2017 security patch.
AT&T Google Pixel XL 128 GB | OTA Download | google_marlin_marlin
Verizon carrier Pixel XL | OTA download |
8.0.0/OPR3.170623.007 from 8.0.0/OPR6.170623.012
Android 8.0 – Oreo for Pixel XL
Official factory images
Official full OTA images
Build for Global, Bell, Telus, Telstra, TMoUS, Sprint, USCC, Rogers/Fido
Android 8.0 – Oreo for Pixel
Official factory images
Official full OTA images
Build for Global, Bell, Telus, Telstra, TMoUS, Sprint, USCC, Rogers/Fido
Soon the official factory images for September 2017 Security Patch will show up. Also, download OTA update image from above and install it via ADB sideload method.
What's in the security patch
There are 30 issues resolved in the security patch dated 2017-09-01 and 51 in the 2017-09-05 one. Google notes that the two security patch level strings provide “Android partners with the flexibility to more quickly fix a subset of vulnerabilities that are similar across all Android devices.”
Google devices will receive the latter patch, while devices from other manufacturers will also feature OEM-specific fixes. This month’s bulletin also includes a new section that lists patches that are specific to Google devices.
Vulnerabilities range from moderate to critical, with the most severe possibly enabling remote code execution when browsing, using email, or MMS. However, Google notes that there are no reports of customers being affected by these security issues.
Still not interested? Some people are willing to give up root for a little while in order to improve their security... Only someone who thinks having root 24/7 is better than improving security is something different.. I know with this patch it stops people from remotely controlling you're device... I think if I was rooted I'd unroot and add this security protection...
Pixelxluser said:
Still not interested? Some people are willing to give up root for a little while in order to improve their security... Only someone who thinks having root 24/7 is better than improving security is something different.. I know with this patch it stops people from remotely controlling you're device... I think if I was rooted I'd unroot and add this security protection...
Click to expand...
Click to collapse
If someone is rooting, why not apply the update and reroot. We all do that every month. I just did mine for this update. I get the loss of security if you root but you dont need to give up root to update.
Pixelxluser said:
The first Google devices to receive the September 2017 Security Patch are the Unlocked Pixel XL 128 GB on AT&T and Verizon. That means, the US carriers shall receive the OTA update before the global roll out.
The OTA update for AT&T Pixel XL brings the firmware build number OPR3.170623.007 dated September 5th 2017 level based on Android 8.0.0 Oreo. This an upgrade over the previous OPR6.170623.012 August 5th 2017 8.0.0 Patch.
AT&T Google Pixel XL 128 GB | OTA Download | google_marlin_marlin
Click to expand...
Click to collapse
I would like to know where you copied & pasted this info since at&t does not sell the pixel, so, I can't see them releasing a ota.
Last I knew, google controls this
Sent from my Pixel using XDA-Developers Legacy app
I was rooted on Oreo and updated to this new build and my service still sucks? I'm right next to a cell tower and my phone is going from -64 to -80dbm and its making my battery tank. I'm about to go back to 7.1.2.
I think a big misconception is trying to pull people away from improving their own security and safety by using the whole oh you will lose root if you do that and may lock you're bootloader.. just because you personally don't care about you're own safety doesn't mean you should try to prevent someone else from improving their own safety.. come on the fact is it's just root you will be fine to live without it for a little while it's not going to hurt you to give it up for a few...
And another thing is all the new pixels and Pixel XL are gonna come preinstalled with these new security patchs so you all might as well get used to it...
I don't understand why Google doesn't post these on their website immediately. I have a Pixel on Verizon and have no way of accessing it until they finally publish the update to their site or zi just start receiving it. It's always this awkward way with a lot if confusion. It would also be nice if they fixed the few small bugs in Oreo (i.e. picture in picture mode causing reboots when you turn the screen off/back on). It's just a little annoying.
The Sept security patch also fixes a Bluetooth problem. It's recommend to update to any software with Sept security patch and later security patch
Google is still working on getting the September security patches out the door, but it has posted a security bulletin detailing the changes. Several of the flaws noted in the bulletin are part of an enormous Bluetooth vulnerability discovered by Armis Labs, which bills itself as an IoT security firm. The "BlueBorne" attack exposes billions of Android devices to complete takeover by hackers, but it's not only Android. The same flaw exists in Windows, Linux, and some versions of iOS.
BlueBorne is dangerous because most devices have Bluetooth active even when it's not actively being used, and an attacker does not need to pair with the target device to completely take it over. There are eight vulnerabilities listed by Armis, four of which are critical (though Google's classifications differ). The most severe issues are the two remote code executions, which allow an attacker to completely own a device without the user even knowing. These flaws are present in the Bluetooth Network Encapsulation Protocol (BNEP) service, which is used for internet sharing and networking.
You don't even need an internet connection to infect a device, and the Android demo above is wild. If one of the affected devices has Bluetooth on, it's a target. The attacker can gain complete control of the phone to launch any app, install malware, and exfiltrate data. Armis estimates that about 8 billion devices are vulnerable, including 2 billion Android phones, tablets, set top boxes, and watches. There are another 2 billion Windows devices and around 1 billion iOS phones and tablets affected. BlueBorne doesn't work on iOS 10, so the damage is mitigated there.
BlueBorne vulnerabilities in the security bulletin
Most of the vulnerabilities in Android reported by Armis affect all recent builds of the OS, so Google is adding a lot of patches to AOSP. It's up to OEMs to push those out to devices, though. Anything with a patch level of September 1st, 2017 or later will have the necessary fixes. It's going to take time for this patch to roll out, and in the meantime, there are a lot of vulnerable devices.
This was took from Android polices website
It's also recommend that the devs here on xda get rid of the software which is vuneralable to theses problems.. it doesn't really show good faith of a Dev if they know there's security problems in the roms but yet keep them posted for someone to download and install...
Pixelxluser said:
It's also recommend that the devs here on xda get rid of the software which is vuneralable to theses problems.. it doesn't really show good faith of a Dev if they know there's security problems in the roms but yet keep them posted for someone to download and install...
Click to expand...
Click to collapse
Boring.......
Pixelxluser said:
It's also recommend that the devs here on xda get rid of the software which is vuneralable to theses problems.. it doesn't really show good faith of a Dev if they know there's security problems in the roms but yet keep them posted for someone to download and install...
Click to expand...
Click to collapse
Do you even know what the ... ah not worth it
Sent from my Pixel using XDA-Developers Legacy app
My X Style Pure (2015) was updated last Fall to the first version of Nougat (7.0) and has received nothing since October 2017. Moto/Lenovo isn't going to update the OS any further. I'd assumed that I'd still get the monthly security updates.
I know I can use an unofficial ROM to get the phone to Oreo. But will I get security updates? Is the carrier (Verizon) responsible or Moto/Lenovo? Would I have to do it myself, and if so, how?
Just curious as I don't think I've ever seen an answer to this.
The manufacturer is responsible for security updates for as long as they support the device. This assumes that there is no carrier interference with the process: something quite common in the US. Since this device is no longer supported, neither Lenovo nor the carrier is responsible for providing further updates. That now falls to the developer of the custom ROM you choose to use. Most developers are good about providing security updates, but they aren't required to do so either, unlike Lenovo or the carrier.
That's good to know--and a practice that needs to change. I think that the phone manufacturer should continue providing those updates far longer than they do.
TheHarbinger said:
That's good to know--and a practice that needs to change. I think that the phone manufacturer should continue providing those updates far longer than they do.
Click to expand...
Click to collapse
LoL...I agree but in the Android ecosystem, it is unlikely to change. You want consistent regular timely updates for at least 2 years on date of release, then a Google phone (Pixel devices) is the only way to go. Ultimately, it is all about getting people to upgrade and therefore increasing profit. While batteries being "built in and not user replaceable" does lead to slimmer devices, it also means people will upgrade more as their battery life depletes over time. It seems there are a lot of people experiencing sudden battery problems shortly after 2 years on the MXPE. Strange...
Does anyone know how often OnePlus updates software? I have a bunch of Tile Pro trackers and they don't work on the current software version. Both Tile and OnePlus acknowledge there is a Bluetooth problem on the OnePlus side. OnePlus said the fix would be in the next software release but they don't say when that will happen. If it won't happen for a few months I might try a another rom.
https://forum.xda-developers.com/oneplus-6t/how-to/t-mobile-6t-to-international-t3888307
Just convert it. Takes 30 minutes total. I did it and havent looked back.
I was hoping to avoid the conversion. I will see if it gets fixed on the next OTA. If not it will go international.
OldTacoman said:
Does anyone know how often OnePlus updates software? I have a bunch of Tile Pro trackers and they don't work on the current software version. Both Tile and OnePlus acknowledge there is a Bluetooth problem on the OnePlus side. OnePlus said the fix would be in the next software release but they don't say when that will happen. If it won't happen for a few months I might try a another rom.
Click to expand...
Click to collapse
Once the international gets updated, wait about a month and that's when you'll see the T-Mobile update.