not my artical just found it orig web page
androidandmeDOTcom/2010/04/news/android-2-2-is-coming-what-features-do-you-want/
replace dot = .
Android 2.2 is coming. What features do you want?
By Taylor Wimberly on Apr 20267
The majority of Android phones are still running an outdated firmware, but that hasn’t slowed Google from advancing their mobile operating system. Everyone knows the next version of Android (codenamed Froyo) is on the way and the rumors (1, 2) are beginning to pick up that the Nexus One will receive it soon.
Based on the data from our analytics reports it appears Google has already begun testing on their next firmware – Android 2.2. Google engineers have routinely given codenames to future builds of Android (Eclair, Froyo, Gingerbread, etc.), but they don’t receive a point release till they are finalized and nearing distribution.
We have shared this reporting data before and people are always quick to point out that it can be easily faked, but I have spoke with additional sources familiar with the matter who confirmed Android 2.2 is currently being tested.
The feature set for Android 2.2 was frozen long ago, but it remains mostly unknown. Google decided last year that they would no longer publish public roadmaps for future versions of Android. Based on the information we can gather, it appears Android 2.2 will mainly focus on performance enhancements.
Some of the rumored features for Android 2.2 include:
•JIT compiler
•Free additional RAM
•OpenGL ES 2.0 enhancements
•Flash 10.1 support
•Fixed problem with “crazy screen” / Resolution of cross multitouch
•Activation of Color Trackball
•Enable FM radio
Some of these features are plausible and others we have no clue.
The JIT compiler has already been confirmed by Google and we expect to find out new details during Google I/O. Android engineers will be leading a discussion that informs devs how to test and tune their apps to work with the new compiler.
Additional free RAM should come thanks to the new Linux kernel being used in Froyo. Google is moving from 2.6.29 to the newer 2.6.32 which makes it possible to address the extra RAM. This has already been done in custom ROMs like CyanogenMod so expect this feature for sure.
I’m no expert on OpenGL, but it has long been rumored that Froyo (or a future build) will add new APIs to the Android NDK which will let Java devs have full access to the OpenGL ES 2.0 library.
Flash 10.1 is coming in the first half of the year. It is entirely possible it could be tied to a future Android firmware and be included with an OTA update.
We have already addressed the HTC touch sensor issues. It sounds like a future software update could be used to clean this up a little.
Multicolor trackball notifications are definitely coming. Android hackers like ChainsDD have already unlocked this feature for users of custom ROMs. Google advertised the multicolor trackball during its launch of the Nexus One, but the feature was cut from the final Android 2.1 build.
When it comes to the FM radio, I have no idea. Other HTC phones on a similar Snapdragon platform (Desire and Incredible) include the FM radio so it’s not out of the question that the N1 has it too.
I spoke with Google’s Eric Tseng during CES and he told me there were many secrets left in the Nexus One that we would discover later.
When is it Android 2.2 coming out?
Circle May 19th on your calendar. This is the opening day of Google I/O and I’m anticipating the release of Android 2.2 (and maybe the Flash 10.1 beta) will be tied to this event. Google has provided every developer attending the event a free Droid or Nexus One, so it is possible to see a simultaneous release on both devices.
I’m really curious how first generation devices are going to play with this release. We are expecting most phones to receive Android 2.1 this month, so it will be interesting to see how Froyo fits in. Some of the Android engineers have been talking about Froyo on the Google boards and it is unclear if the HTC Dream and Magic will be able to support it since they only have 192 MB of RAM.
p.s. if in wrong spot please move it im a tootal newb
Sprint has announced some maintenance release updates for the LG Optimus S and Samsung Galaxy Tab. Both updates will be sent out in stages so there is no mad rush to get them download but if you own either device you'll want to check out the change logs to see if anything applies. You'll find those by hitting the source links and if you're not feeling that you can just look past the break, they're listed there as well
Samsung Galaxy Tab Maintenance Release - EA24
Enhancements/Fixes:
* New drivers for LCD supplier
* QIK software update to 0.04.77 (will overlay existing version)
* Exchange email fixes
Important Notes:
* Software version is: Baseband S100.08 S.EA24, Build SPH-P100.EA24
* Download and install time is approximately 5 minutes
* Released in stages with 100% of devices having received the update within 4 days
* Refer to the Samsung Galaxy Tab Maintenance Release blog for install instructions
***Credit goes to android central*****
Does anyone know if this breaks root?
Anyone know if it locks the bootloader?
Anyway we can grab a modem.bin from this update?
Sent from my SPH-P100 using XDA App
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.
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
Today, L04C567B396 appeared on FF, the third update in a month time with no approval for installation for the earlier B394 so far.
With this updae comes two additions and one improvement to the EMUI features plus a new June google security patch.
Again, with this update a hope of eminent EMUI 8 (Oreo) is lost at least for a couple of months if not impossible any time soon in my opinion.
Let's hope that my guess is wrong.
Tell me what do you think in the comments below.
Anyways here's the B396 changelog:
This update reduces Phone Manager's cleanup time to less than one minute, and adds more scenarios to support the one-touch split-screen feature.
[Dual windows]
Adds a button in the Recent apps cards. Touch it to split the screen. This operation is only available for apps that support the split-screen feature.
[System]
Optimizes Phone Manager's cleanup speed and scope. A single cleanup can now be completed in less than one minute.
Optimizes data usage management by allowing you to specify the start date of your data plan.
[Call]
Optimizes Quick calling by enabling speaker mode by default. Press and hold the volume down button to enable Quick calling.
[Security]
Integrates Google security patches released in Jun 2018 for improved system security.
----------------
Update 1: Honor skipped B394 to B395 and stated seeding.
Nitrowarez.
Sent from my FRD-L04 using Tapatalk
Who cares? By the time it's approved it'll be end of July possibly August. Chris (head Dev at honor USA) says they have no control over when it gets approved. We are getting Oreo, and he's getting responses from the beta group about the bootloader issue to give to the higher ups.
agraceful said:
Who cares? By the time it's approved it'll be end of July possibly August.
Click to expand...
Click to collapse
I was thinking the same.
Honor support told me we would get it 'very soon' 2 months ago and its likely another two months if they have only just started alpha/beta testing.
Not sure I agree that is 'very soon'.
Personally I'd prefer lineageos so we get future support, but haven't read the other threads to understand why dev support is limited.
Perhaps 'Chris' can release the kernel source for Oreo on the Honor 8, so others can start development in parallel with Honor, or release the camera blobs or whatever is stopping the camera's working.
I think we better stop creating new threads for each patch for specific model .,. its getting really boring.,., i myself created several threads for the patches but no charm now.., especially after oreo in tow..,
admins if we could join all the threads under patch update.,
SSyar said:
I think we better stop creating new threads for each patch for specific model .,. its getting really boring.,., i myself created several threads for the patches but no charm now.., especially after oreo in tow..,
admins if we could join all the threads under patch update.,
Click to expand...
Click to collapse
I guess I'll make it. Hopefully it works out well
xsacter said:
I guess I'll make it. Hopefully it works out well
Click to expand...
Click to collapse
Hope so?
scoobydu said:
Hope so?
Click to expand...
Click to collapse
Yea because some people might not like the idea, including admins
xsacter said:
Yea because some people might not like the idea, including admins
Click to expand...
Click to collapse
Ok.