{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
A little earlier today Google posted the Android 6.0.1 security updates for June to the AOSP changelog. Being the responsible Android citizen that it is (well, most of the time), Samsung has immediately followed suit with its own list of code updates. These are the issues that are problems for specific Samsung devices and their related software builds, or at least, the ones that have been addressed since the same security bulletin last month. As usual, they're limited to "major flagship models."
The list contains five items on top of the security patches mentioned by Google's own changelog: an external storage vulnerability, control through a locked device, a minor SIM lock issue, an email encryption configuration error, and a certificate signature bypass check for fingerprint readers. The problems ranged from high severity, allowing malicious app installations or possibly even total device control, to low severity, causing minor bugs and usability issues. Builds from Android 4.4 all the way through 6.0 were affected by different problems.
This bulletin is just documentation of the bugs themselves and the fact that the patches to repair them are ready. It will probably be several weeks or even months before they make it to phones... and it's almost certain that a good number of older devices won't ever be patched. And that's without taking the delay of carrier certification for OTA updates into account.
Source: http://security.samsungmobile.com/smrupdate.html
http://www.androidpolice.com/2016/06/06/samsung-posts-its-own-june-ota-security-bulletin-with-additional-vulnerabilities-fixed/
When are we getting this update to S7 Edge in India?
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Adobe has released a new version of its Flash Player for Android that fixes some critical security bugs. The new version of Flash, which, incidentally, is also available for Windows, Linux and OS X, fixes security vulnerabilities in Flash Player 11.1.115.6 and earlier versions for Android 4.x, and Flash Player 11.1.111.6 and earlier versions for Android 3.x and 2.x. These vulnerabilities, if exploited, could cause a crash and potentially allow an attacker to take control of the affected phone or tablet.
The update fixes two problems – the first is a memory corruption vulnerability in Matrix3D, a part of Flash which is used to determine the position and orientation of a three-dimensional object, that could lead to unauthorized code execution. The second vulnerability patched is an integer error that can lead to information disclosure.
Don’t Panic
Although these vulnerabilities are seen as critical, Adobe has rated them as “priority 2″ which means that there are currently no known exploits, and, based on previous experience, Adobe does not anticipate that exploits are imminent. As a result, Adobe is recommending users to install the update within the next 30 days.
The new update should be aviliable in the market but all of us know that in the market no adobe flash player for galaxy fit.
Any one upload new arm6 adobe player version ?
SOURCE : Kickedface
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you've ever used CyanogenMod, then you already know it comes bundled with ROM Manager. That's the case for one reason: so users can quickly and easily pull updates to the ROM. However, this presents a problem of sorts. CyanogenMod is completely open source, but ROM Manager isn't. Therefore, the team wanted an update solution that will allow CM users to pull the latest builds to their devices, but is still open source. So they made their own, which will replace ROM Manager in upcoming builds.
The new updater should be available in the latest nightlies (rolling out tonight). Once you flash, head into Settings > About to set your update preferences!
This is actually a rehash of an old version of the updater from CM5 and 6 (that seems like so long ago, doesn't it?) that has been updated to work with CM9/10 and beyond.
Since push notifications for updates require Google Apps framework, the CM updater won't actually include that functionality. What it will do, however, is automatically check for updates at user-defined intervals, and pull the update once something is available.
The updater will pull directly from get.cm, so you'll always be getting official CM builds directly from the source. As you can see, it can be customized to check for new stable builds, new nightlies, or all builds from either channel.
This will be a huge improvement over any other method of pulling updates (especially manually), so we're definitely looking forward to seeing it debut. As always, however, there's no official timeline as to when it may make its way into nightlies.
Finally it here the new android its neither KEY LIME PIE nor it is 5.0...
It is 4.4 ANDROID KIT-KAT
Lots of expectations
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Google's SVP Sundar Pichai has
just confirmed -- by way of a
photo -- that the next version of
Android is named KitKat (rather
than the rumored "Key Lime
Pie ") aka version 4.4. The exec
shared this geeky nugget on
both Google+ and Twitter, while
his company has updated the
Android developer site with a
page chronicling Android's
milestones so far. While details
are light at the moment, Google
teases its upcoming release with
the following line:
"It's our goal with
Android KitKat to
make an amazing
Android experience
available for
everybody."
Pichai also announced that there
are now over one billion
Android device activations,
surpassing the 900 million mark
back in May this year.
Click to expand...
Click to collapse
Though they dont gave more info but still this is huge announcement for android lovers
Sources:-
Google teases Android 4.4 as 'KitKat,' passes one billion Android activations
Kit Kat statue joins the crew at Google HQ | Android Central
Please use the thread we already have
Thread closed
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Simple Password Manager is an easy to use, ad free, Password Manager App which gives you full control over the encryption method and does not require any special permissions.
It has over 7,500 installs on Google Play, as on date, since May 2012, and recently I made some significant changes to the app, releasing version 2.0. You can store multiple username/passwords and only have to remember one strong Master Password. This is used to encrypt the other passwords securely using a key derivation function.
You can choose the number of bits and iterations and the key derivation function as per your security needs and phone processing power. For now, I have only enabled PBKDF2, since it is the best natively supported KDF, and you will get HMAC SHA1 variant till Android 7.1, and with SHA256 AND SHA512 in Android 8. Nevertheless, I can easily enable Blowfish or any other KDF supported on your device, if requested, and play to include Argon 2d in future updates.
I request you to try out the app, rate and review, and generally give me feedback to improve it. Do let me know what you like or dislike. Do you find it easy to use or confusing, etc.
Like app on Facebook!
I just updated this to version 2.05, which makes it much easier to get started with the app and is available in five languages - English, French, Spanish, Chinese (Simplified/Traditional), and Hindi... with Russian on its way.
So I was playing around in Verizon's ota server when I got a strange update to trigger. Software version is 21A. ... Security patch is more recent than the 20g version (June 2020 vs April 2020) .. I'm still playing around to see if there's any Android 10 OTAs they have stored. Is anyone else running this version or know anything about this update?
UPDATE: For anyone who is curious, I'm having excellent battery life on this build. I'm not sure why this OTA is unreleased... I'm assuming this will be the update that eventually bridges us to Android 10. When I first downloaded the update, I noticed it was larger than previous OTAs so I was really hoping it was Android 10.
If anyone wants to debug, test, or just have the latest security patch:
https://drive.google.com/file/d/1aPnc9gmQC_D8V46eQfYNFO365By8tP_-/view?usp=drivesdk
Or download it the way I did from Verizon's server:
https://cdn2.vzwdm.com/LG_G710VM_20g_21a_02.bin
Installation Instructions:
1. Be on latest Verizon firmware. (20g)
2. Download OTA file above.
3. Rename file to LGUP_FOTA.UP
4. Place directly onto the root of your internal storage (not in any folder, just directly in your internal storage)
5. Download Activity Launcher from Google Play
6. Type FOTA
7. Choose option one (should say test)
8. Let the OTA install to 100%, then reboot.
For root users who are curious, Magisk is working just fine on this build.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}