Android 5.1

[Jorge-Vieira]

The First Android 5.1 Screenshots Are Here With Wi-Fi And Design Upgrades

Ever since Android Lollipop’s launch last year, users all around have seen the gradual rollout of the software on their devices, and by now almost all major Android flagships are running on the update. Even though Lollipop brings a host of great features for users to enjoy, looks like Google’s eager to update Lollipop soon for us, even though the search engine giant has been particularly tight lipped about it. However, Google’s silence does not matter today, as some screenshots have popped up of Android 5.1, showing us what to expect from the next update.


http://cdn.wccftech.com/wp-content/uploads/2015/02/Android-5.1-Lollipop-new-design-elements2-635x1016.jpg


http://cdn3.wccftech.com/wp-content/uploads/2015/02/Android-5.1-Lollipop-new-design-elements-635x357.jpg


Leaked Android 5.1 Screenshots Show Several New Features On The Update Today’s leaks of Android 5.1 end up giving us some details on how things can be expected to work on the update. The first of these, as you can see in the image above relates to Wi Fi connectivity on the next update. By the looks of things, in Android 5.1, you’ll be able to switch Wi Fi and Bluetooth networks simply through the icons on notification center. You can see the sub menu options under the icon for each type of connectivity. Tapping on them will open up a range of networks that you can connect to, as shown in the image below.

http://cdn3.wccftech.com/wp-content/uploads/2015/02/Android-5.1-Lollipop-new-design-elements3-635x1016.jpg

http://cdn2.wccftech.com/wp-content/uploads/2015/02/Android-5.1-Lollipop-new-design-elements1-635x357.jpg

Apart from Wi Fi and bluetooth connectivity, videos posted by Android Police also end up highlighting design upgrades that can be expected from the next Android update. A video posted shows the clock app in the operating system that has some changes on board. Tabs for the alarm, stopwatch and the clock in Android 5.1 will be using animations now. All in all, it shows that perhaaps Google’s decided that the overall interface on Material Design has become a bit too dry an is looking to upgrade it for some changes. Android 5.1 might be coming next month so keep you eyes peeled for any updates and take a look at the video below. We’ll keep you updated in the meanwhile.


https://www.youtube.com/watch?feature=player_embedded&v=Wn_JZ7ZX80Q






Noticia:
http://wccftech.com/android-51-screenshots/#ixzz3SOTJUIHN

[Jorge-Vieira]

Google’s Attention To Detail Apparent As New Android 5.1 Features Pop Up

Slowly but surely Android 5.1 features have started to make their way across to us. After we shared some details about tiny design and wireless connectivity changes on the update with you yesterday, a tiny new feature of Android 5.1 has popped up again today. You can take a look at it in the video below.



https://www.youtube.com/watch?feature=player_embedded&v=99V1xy38OTQ


Android 5.1 Will Allow You To Directly Unlock Device From Quick Settings Menu Another tiny detail uncovered about Google’s soon to be expected update is the ability to unlock your device directly from the Quick Settings menu. If Android Lollipop has made its way on your device, then you’ll know that unlocking it directly from the Quick Settings menu in the lock screen is not possible. Well, looks like folks over at Google are paying attention to the details, as this feature seems to have changed in Android 5.1. If you were paying close attention in the video above, then you’d have seen that swiping directly outside the menu will now let you unlock your device.
For those of you who didn’t watch the video, we’re here to tell you what happens in the short clip above. In Android 5.1, if you access the Quick Settings menu from the lock screen, and suddenly feel the urge to unlock your device, then all you need to do is swipe to the left in the area outside of it. If face detection has been enabled on your device then your smartphone/tablet will directly unlock without the need to enter a pin code. If it isn’t enabled, then you’ll be directed to the pin entry screen, where all that you’ll have to do is enter the pin to unlock your device. Android 5.1 (http://wccftech.com/android-51-screenshots/)Amd seems to be about the little things it would look like, as Google’s paid attention to other features such as connecting to Wi Fi and bluetooth networks through notification center, amongst other design upgrades.





Noticia:
http://wccftech.com/android-51-features-surface/#ixzz3SUuQCrOS

[Jorge-Vieira]

Android 5.1 announced, includes cross-platform HD Voice support

Google has announced Android 5.1 Lollipop, the latest update to its mobile OS, which comes with some improvements and new features. We have the usual stability improvements and performance-enhancing code supplements, but the new features might have you happy.


image: http://imagescdn.tweaktown.com/news/4/3/43977_04_android-5-1-announced-includes-cross-platform-hd-voice-support.jpg (http://www.tweaktown.com/image.php?image=imagescdn.tweaktown.com/news/4/3/43977_04_android-5-1-announced-includes-cross-platform-hd-voice-support_full.jpg)
http://imagescdn.tweaktown.com/news/4/3/43977_04_android-5-1-announced-includes-cross-platform-hd-voice-support.jpg

Android 5.1 now includes multi-SIM support, and cross-platform HD Voice support - depending on the network, of course. Google has also provided Device Protection, where Android will keep your smartphone safe from intruders, even if they perform a factory reset on your smartphone after they've stolen it. This new feature binds your Android 5.1-powered device to your Google account, unless you choose otherwise.

The latest version of Lollipop has an updated Quick Settings menu, giving you more granular control over things like Bluetooth and Wi-Fi network switching. The latest Android 5.1 update should be rolling out to Nexus 6 owners soon enough.




Noticia:
http://www.tweaktown.com/news/43977/android-5-1-announced-includes-cross-platform-hd-voice-support/index.html

[Jorge-Vieira]

Google Starts Releasing Android 5.1 Lollipop Update – See The Full Changelog

Recently, Google reflected in one of its blogs that the launch of the Lollipop Update was a complete overhaul visually and came with its own built in bugs and glitches. To overcome this situation which was present from the very day Lollipop was launched, Google needed an update to cancel out the vulnerable sensitivities. The update needs to be better enough to remove the sluggish behavior of the OS on the Nexus 6 which users have complained in the past weeks or so. Google faced the partial blame for the encryption of data in the storage box.
http://cdn.wccftech.com/wp-content/uploads/2015/03/moto-nexus-android-5.1-lollipop-update-635x394.jpg (http://cdn4.wccftech.com/wp-content/uploads/2015/03/moto-nexus-android-5.1-lollipop-update.jpg)
Google’s recent OS, Android 5.1 Lollipop has received its first foremost update which made its way to the supported devices like Motorola’s Nexus 6 and HTC built Nexus 9 tablet. There have been a few amendments made to the stock version of the Lollipop update which will also deter the entry of thieves in the storage category. Roll down below for more details for what does the update has to offer.
Android 5.1 Lollipop Update Offers Device Protection And More – Changelog In Detail The latest update to 5.1 Lollipop has brought more stability to its operating system disabling any crashing or lagging issues as well as enhanced performance upgrades. The update also included the support for devices with multi-Sim card options. Device protection from various unknown source applications has also been added to enable a more secure way to browse and download. There have been improvements made in the HD voice which are oriented towards supported devices and smartphones. The 5.1 update constitutes more than 14,000 changes in total considering its one of major releases so far. If you still have the dire need to know about them, check out this ‘changelog’ (https://paste.teknik.io/1010).


Android One market has been targeted considering the multiple Sim performance which by far is the most important part of the update for its users. Google confirms that the 5.1 Lollipop update will enable High Definition Voice on its own Nexus 6 devices which are running on Verizon and T-Mobile networks. This will be the major support considering the 5.1 update. For the time being, Verizon is still to get the Nexus 6 smartphone soon.
http://cdn4.wccftech.com/wp-content/uploads/2015/03/lock_down_your_phone_primary-100567275-large.jpg (http://cdn4.wccftech.com/wp-content/uploads/2015/03/lock_down_your_phone_primary-100567275-large.jpg)
Google To Introduce Activation Lock With 5.1 Lollipop Update There had been many speculations about the Activation lock on Android as that of Apple’s. Now, the time is here for Google to debut its Activation Lock. For people who are unaware of the Activation Lock, it acts as an anti-theft operation which bricks your phone when its stolen. The device protection allows your device to be locked even if anyone tries to hard reset it to default settings. Google claims that the Device Protection will have support on most of the smartphones and tablets which will have the Android 5.1 and higher. This is all for now folks, fire away the question in the comments if you have any.







Noticia:
http://wccftech.com/google-starts-releasing-android-51/#ixzz3U4FTW3DX

[Jorge-Vieira]

Manually Download And Install Lollipop 5.1 Update On Nexus 10, Nexus 5 And Nexus 7 – How To

Monday was the day when Google announced its biggest release, the Android Lollipop update to 5.1 for various devices. The Nexus series come in line to receive the update and then other major smartphones, if they’re lucky enough. Google rolled out some factory images of Nexus 5, Nexus 10 and Nexus 7 Wi-Fi running the Lollipop 5.1 update on its website. However, if you still cant wait to get the update on your Nexus device you can always install the OTA update. The images on the website will help you install the Update on your Nexus device. roll down for more details on how to do it.
http://cdn.wccftech.com/wp-content/uploads/2015/03/Nexus-6-Nexus-9-635x357.jpg (http://cdn2.wccftech.com/wp-content/uploads/2015/03/Nexus-6-Nexus-9.jpg)
The images can be downloaded from the website but are recommended for those people who have the technical know how of the complete process. The process will delete all of your data stored on the memory box so its better to back it up. To complete this process you need to know the risk involved and you can easily flash the latest version of Lollipop 5.1 to you Nexus device.


Install Lollipop 5.1 On Your Nexus Device

On your Windows computer, download and install the most recent version Android SDK. Two programs will be installed Fastboot and ADB. To access these files you have to open them through the command terminal on you windows PC as a slice of the development kit in software.
Put the SDK folder in the path provided by the steps below:- Open Properties by right clicking on My Computer- Open Advanced Sysytem Settings- Open System Properties >> Advanced >> Environment Variables- Select path in the Window then edit it and type the location where SDK is installed. Do remember to put a semi-colon to separate each entry.
The USB debugging on your device should be enabled. To do so, go to Settings >> About Phone >> Software Information
Build Number is to be tapped 7 times
Them go to Settings >> Developers Options. Check the USB debugging option
This is where you download the factory image for your Nexus variant. The links are provided below after this section of steps.
Extract image On Windows PC
Connect Device to PC via USB
Start your device in the fastboot mode



- Nexus 5, Android Lollipop 5.1 (https://dl.google.com/dl/android/aosp/hammerhead-lmy47d-factory-6c1ad81e.tgz)
- Nexus 7 Wi-Fi, Android Lollipop 5.1 (https://dl.google.com/dl/android/aosp/nakasi-lmy47d-factory-bc93dab8.tgz)
- Nexus 10, Android Lollipop 5.1 (https://dl.google.com/dl/android/aosp/mantaray-lmy47d-factory-63eade7f.tgz)

Nexus 5 has a different way to do it. You must press and hold down the volume up and volume down keys along with the power button when you power your Nexus 5 on. You can also use ADB to boot into the Fastboot mode. You can do this by powering on your device, go to command terminal and execute adb reboot bootloader. If needed, through your computer you must unlock your device’s bootloader by using the command terminal and launching ‘fastboot oem unlock’.


Find the path to the unzipped image file or directory using command terminal
Flash-all.bat should be executed which is part of the unzipped image. This scripture would install the basic baseband firmware/s, bootloader and operating system. This will only work when you have added that folder where Fastboot and ADB are installed to system path as shown in step 2
When you do this, lock the bootloader as recommended by Google for security. This can be done by booting your device when still connected to USB in fastboot mode. Then use the command terminal to execute the ‘fastboot oem lock’.

Even though these steps will install the Lollipop 5.1 version to your Nexus device we would still recommend you to wait for the final release for the OTA update. Installing the OTA update is a trouble free workout to upgrade your OS. If you have any question let us know in the comments.




Noticia:
http://wccftech.com/manually-download-install-lollipop-51-update-nexus-10-nexus-5-nexus-7/#ixzz3U4GRzYuX

[Jorge-Vieira]

New Multi-Windows Feature Could Increase Android's Appeal On PCs

http://media.bestofmicro.com/9/I/483750/gallery/maxresdefault_w_600.jpg (http://www.tomshardware.com/gallery/maxresdefault,0101-483750-0-2-12-1-jpg-.html)A small hint in an Android source code commit revealed that Google may be working on a multi-windows feature for a future version of Android. The developer's statement doesn't say too much about it other than mention the word "multiwindows," but this just adds to another hint back from October last year that also pointed to multi-windows coming to stock Android.
http://media.bestofmicro.com/9/L/483753/gallery/multi-window-feature-code_w_600.png (http://www.tomshardware.com/gallery/multi-window-feature-code,0101-483753-0-2-12-1-png-.html)Samsung has experimented with multi-windows on its tablets before, going from two to even four different apps running at the same time. The idea of showing multiple apps on a larger tablet screen would have made Android tablets more useful and more productive in the early stage of their life. It would have also solved the tablet app problem by using phone apps that would fit better on a smaller part of a large screen rather than being expanded to fit a 10" screen.
Samsung's multi-windows feature had two critical flaws, though. One was performance. Tablets seemed to slow down significantly when using multiple apps at the same time. However, it was never clear whether this was because of poor coding from Samsung, Android not being performance-optimized enough at the time, the processors not being fast enough to handle multi-windows, or a combination of all of these issues.
The second flaw with Samsung's multi-windows system was that it only worked with Samsung's apps, or apps that used Samsung's own SDK, in order to utilize the custom multi-windows APIs.http://media.bestofmicro.com/9/J/483751/gallery/samsung-multi_w_450.jpg (http://www.tomshardware.com/gallery/samsung-multi,0101-483751-0-2-9-1-jpg-.html)Google could be implementing this feature natively into Android at a time when Android has largely solved its performance issue thanks to the new runtime's Ahead-Of-Time compilation and other improvements over the years. Processors that are going into tablets are much faster as well, which should also help to run multiple apps at the same time.
Competitors such as Microsoft, Canonical, and likely Apple soon, too (with its rumored "iPad Pro" device), have used or will use multi-windows in their mobile operating systems as they become more mature and can work with more powerful hardware.
The question is how far Google is going to take this feature, and whether the company will make it so powerful that it could lead to Android becoming much more appealing as a PC operating system. Tablet sales have been stagnating or dropping lately, so perhaps Google will need to consider going into PCs with Android, as a more "advanced" operating system than Chrome OS.
http://media.bestofmicro.com/9/K/483752/gallery/chrome-apps_w_600.png (http://www.tomshardware.com/gallery/chrome-apps,0101-483752-0-2-12-1-png-.html)Google announced last year that Chrome OS will support Android apps, but it doesn't look like all Android apps can work by default, once Google modifies some code inside Chrome OS. Instead, so far we've only seen a handful of Android apps that have been pre-approved by Google for Chrome OS. If Google can't make all Android apps work inside Chrome OS, then perhaps Android could be more suited for the PC and as a competitor to Windows and Mac OS X, for those users who want to use an operating system that doesn't limit them to the Web.
Google will likely announce a new major version of Android at the next Google I/O event, along with the multi-windows feature.

Noticia:
http://www.tomshardware.com/news/android-multi-windows-feature-pcs,28721.html

[Jorge-Vieira]

Android 5.1 Update Picks Up Speed With Nexus 10 Getting Updated OTA

Android 5.1 has been here for some time now, with Google having launched the upgrade alongside Apple’s iOS 8.2 earlier this month. When it comes to the Android world however, an update release doesn’t necessarily translate to your device being updated at the same time. So while Android 5.1 is out here, many devices are yet to see an upgrade. But not the Nexus 10, as Google’s stock Android device has received the update.
http://cdn3.wccftech.com/wp-content/uploads/2015/03/Nexus-10-receives-Android-5.1-update-OTA.png (http://cdn3.wccftech.com/wp-content/uploads/2015/03/Nexus-10-receives-Android-5.1-update-OTA.png) Nexus 10 Starts Receiving Android 5.1 Update As Rollout Picks Up Pace The Nexus 10 seems to be Google’s favored gadget for Android’s most recent update. After the software giant first released file images for the software on the Nexus 10, the device has now started (http://www.youmobile.org/blogs/entry/Android-5-1-Lollipop-Update-is-Rolling-out-Over-the-air-to-Google-Nexus-10) to receive Android 5.1 updates over the air, as can be seen in the image above. Whats good to hear is that the update for Nexus 10 will be weighing in at a light 104 MB, so it really shouldn’t take a lot of time if you choose to upgrade your slate to Google’s latest.




http://cdn4.wccftech.com/wp-content/uploads/2015/03/Nexus-10-receives-Android-5.1-update-OTA1.png (http://cdn4.wccftech.com/wp-content/uploads/2015/03/Nexus-10-receives-Android-5.1-update-OTA1.png)
Android 5.1 will also bring several bug fixes, performance improvements and add on to the features that Google initiated with Lollipop’s massive upgrade last year. Material Design is expected to be refined further, giving it a more simplistic and minimal touch. In addition to this, its also expected to further improve performance on devices and further speed your device up particularly with 64 bit chipsets. So all Nexus 10 users out there should stay sharp, as Google’s over the air update for your device should be coming soon. So if you’re looking to update as soon as possible, make sure you have a Wi-Fi connection at hand and keep checking your device’s update section. And let us know if Android 5.1 changes anything for you in the comments section. Cheers.




Noticia:
http://wccftech.com/nexus-10-updated-android-51/#ixzz3V8ZCKgJV

[Jorge-Vieira]

Update HTC One M8 to Android 5.1 Lollipop CM 12.1 Custom ROM – How to

While CyanogenMod team is busy working on the official Android 5.1 Lollipop (http://wccftech.com/update-galaxy-s2-i9100-to-android-5-1/) based custom firmware for HTC One M8, you can already flash it on your device thanks to an XDA member. This is an unofficial version so please don’t go forward if you don’t have any previous experience of using all sorts of custom ROMs. Here are the steps to update HTC One M8 to Android 5.1 based CM 12.1 custom ROM.
http://cdn2.wccftech.com/wp-content/uploads/2014/08/a5.jpg (http://cdn2.wccftech.com/wp-content/uploads/2014/08/a5.jpg)
Prerequisites to update HTC One M8 to Android 5.1 CM 12.1:






Backup any important data (http://wccftech.com/how-to-backup-sms/) from your HTC One M8 as a complete wipe will be required during the flashing process.
Install USB drivers for your HTC device. Check out this link (http://wccftech.com/download-android-usb-drivers/).
Enable USB debugging option on your device: Settings > Development Options > USB debugging.
Ensure that your HTC One M8’s bootloader is unlocked (http://wccftech.com/unlock-htc-one-m8-bootloader/) and that you have a recovery tool like TWRP (http://wccftech.com/install-twrp-recovery-on-htc-one-m8/) or CWM.
Your device must be charged to at least 80% of power.

How to update HTC One M8 to CM 12.1 Android 5.1 lollipop: Required files: download CM 12.1 Android 5.1 Lollipop custom firmware for HTC One M8 from here (https://drive.google.com/file/d/0B5-28IyuIOoNdFE4a3ZyZGRzYzA/view) and extract the boot.img file. Also download the GApps (http://wccftech.com/download-latest-google-apps-android-1/) package for your device.
Here are the steps to help you update HTC One M8 to Android 5.1 based CM 12.1 custom firmware:


Connect your HTC One (http://wccftech.com/install-custom-recovery-and-root-htc-one-m9/) to your computer using a USB cable and copy the ROM and GApps zip files to your phone’s SD card root folder.
Copy / paste the boot.img file to the Android-sdk-windows\platform-tools directory.
Disconnect the USB (http://wccftech.com/latest-sony-xperia-z4-leaked-images/) cord and power off your HTC device.
Boot your device in the Bootloader mode by pressing and holding the Volume Down and Power keys.
Once in the Fastboot mode, navigate to android-sdk-windows\platform-tools directory on your computer and open command prompt with Shift + Right-click combo and click on the Open Command Prompt.
Type the following string into the window:

fastboot flash boot boot.img and press Enter.
Fastboot reboot - press Enter again.


Follow the onscreen instructions and select Bootloader > go to Recovery.
Once in recovery, perform wipe data task: from CWM recovery menu, select wipe data / factory reset and confirm the process.
Also perform wipe cache partition followed by wipe dalvik cache (from Advanced).
From recovery main menu, select install zip from sdcard followed by choose zip from sdcard. Locate the CM 12.1 Android 5.1 custom firmware file and confirm the flashing process.
Once the ROM is flashed successfully, repeat the above step but select GApps package this time.
Return back to main recovery menu and reboot your HTC One M8 (http://wccftech.com/samsung-galaxy-note-4-battery-test/) into the new custom ROM. First boot takes a good 5 minutes so please be patient.

Enjoy the new ROM with fresh looks of Lollipop (http://wccftech.com/lollipop-ota-update-galaxy-s6-edge-starts-seeding/).






Noticia:
http://wccftech.com/update-htc-one-m8-to-android-5-1-cm-12-1/#ixzz3XC8gkjLj

[Jorge-Vieira]

Official Android 5.1 Lollipop Now Available for Nexus 4 – Here’s How to Update

Google (http://wccftech.com/lg-to-make-upcoming-nexus-7/) has finally released the very latest Android 5.1 Lollipop update for the Nexus 4. Weighing in around 174 MB, the update carries the build number LMY47O.
Latest: Sony to Follow Xperia Z4 Release with a Completely Re-Designed Xperia Z5 in Q4 (http://wccftech.com/xperia-z4-and-sony-xperia-z5-launch-in-2015/) http://cdn4.wccftech.com/wp-content/uploads/2013/03/sph-l700.jpg (http://cdn4.wccftech.com/wp-content/uploads/2013/03/sph-l700.jpg)
Coming as regular incremental update bringing usual bug fixes, the latest Lollipop (http://wccftech.com/update-nexus-5-to-resurrection-remix-android-5-1/) version also cuts many troubles that 5.0 initially brought in. Official Android 5.1 Lollipop for Nexus 4 also brings in some performance improvements and new features like Device Protection. Google launched the Device Protection feature with Lollipop to help users protect their data in cases of stolen devices.
You can update Nexus 4 to official Android 5.1 Lollipop via the OTA. However, if your region is yet to get the Lollipop sweetness (http://wccftech.com/download-and-install-android-5-0-on-nexus-4-5-7-10/), you can manually upgrade your smartphone too. Simply click on the link shared below.





Official Android 5.1 on Nexus 4 link: You can install official Android 5.1 Lollipop for Nexus 4 from this link (http://android.clients.google.com/packages/ota/google_mako/e6789b4e57176ed28cd8b24747c134366b3908fc.signed-occam-LMY47O-from-LRX22C.e6789b4e.zip). Once you have downloaded the file, simply go through the usual steps you perform to flash the updates.
If you need any help, don’t forget to check our guide: How to Download and Flash Android 5.0 Lollipop on Nexus 4, 5, 7, and 10 (http://wccftech.com/download-and-install-android-5-0-on-nexus-4-5-7-10/). While it is oriented to Android 5.0 Lollipop update, you can use the steps for the current update too.







Noticia:
http://wccftech.com/install-official-android-5-1-on-nexus-4/#ixzz3XGgpHmBB

[Jorge-Vieira]

Update Galaxy S3 i9300 to CM 12.1 Android 5.1 Lollipop – How to
We shared with you CyanogenMod 12.1 (http://wccftech.com/update-htc-one-m8-to-android-5-1-cm-12-1/) custom firmware based on Android 5.1 Lollipop for HTC’s 2014 flagship. The Lollipop custom ROM is now also available for Samsung Galaxy (http://wccftech.com/update-galaxy-s4-i9505-to-android-5-1-cm12-1/) S3 I9300. Here is how to update Galaxy S3 I9300 to Android 5.1 Lollipop based CM 12.1.
http://cdn4.wccftech.com/wp-content/uploads/2013/03/S3-I747.jpg (http://cdn4.wccftech.com/wp-content/uploads/2013/03/S3-I747.jpg)
Prerequisites to update Galaxy S3 i9300 to Android 5.1 CM 12.1:






Create a backup (http://wccftech.com/how-to-backup-sms/) of all important data in your Galaxy device.

Download and install USB drivers for Samsung Galaxy S3 (http://wccftech.com/download-android-usb-drivers/)in your computer.
Enable USB debugging option by pressing Menu > Settings > Applications. Navigate and tap on Developer Options to ensure that USB Debugging is enabled.
Make sure that recovery tool like ClockworkMod recovery (http://wccftech.com/root-install-cwm-recovery-on-galaxy-s3-sch-i535-android-411-412/) is installed.
Ensure that your Samsung Galaxy S3 i9300 carries more than 80% of charge.

Update Galaxy S3 i9300 to Android 5.1: Files required: download the CM 12.1 Android 5.1 Lollipopcustom firmware from here (https://mega.co.nz/#%21XB5AWZBS%21tBuakZJh0nfQXGrJrGSyC_Z3-0uJC-mb1gnE4nyeUcc); also download the Google Apps (http://wccftech.com/download-latest-google-apps-android-1/). Save both files on PC.
Here are the steps to update Galaxy S3 i9300 to Android 5.1 based CyanogenMod 12.1:


Connect your Samsung Galaxy S3 I9300 to your computer using USB cable and copy the downloaded files to the SD card of your Galaxy device.
Disconnect the connection with PC and turn your Galaxy S3 off.
Boot in to custom recovery mode: press and hold Volume Up, Down and the Power buttons simultaneously until Samsung (http://wccftech.com/update-galaxy-s2-i9100-to-android-5-1/) logo shows up. Leave the keys for half a second and hold again. Use Volume keys to scroll and Power button to select – alternatively you can use Quick Boot app (https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot) to reboot your Android device in recovery mode.
Now perform Nandroid backup of your current ROM: select Backup and Restore > Backup. Go back to main recovery menu after backup process is done – very important step to restore back to current OS.
Data wiping tasks: select wipe data/factory reset > Yes. It will take a few minutes; once done, select wipe cache partition. Next tap on Advance > wipe Dalvik Cache to wipe Dalvik cache data too.
Select install zip from sdcard followed by choose zip from sdcard. Locate the Android 5.1 based CM 12.1 custom ROM file copied earlier and select it. Tap on yes to confirm installation and wait for the ROM installation to be completed.
Once installation process is finished successfully, repeat the above step but choose GApps file instead to install the Google apps package on your SGS3 I9300.
Return to main recovery menu now and select reboot system now to boot up into the latest CM 12.1 Android 5.1 Lollipop custom firmware for Samsung Galaxy S3 (http://wccftech.com/update-galaxy-s3-i9300-to-android-4-4-4/). It will take a bit of time during the first boot, so kindly be patient.
Ta da! Enjoy Lollipop on Galaxy S3.

How to restore: If you want to return to previous OS on your SGS3, boot into recovery, select backup and restore then restore your previous ROM by selecting it from the list.







Noticia:
http://wccftech.com/update-galaxy-s3-i9300-to-android-5-1-cm-12-1/#ixzz3XGis9liL

[Jorge-Vieira]

Update Samsung Galaxy Note 3 to Android 5.1 Lollipop Resurrection Remix – How to

Resurrection Remix (http://wccftech.com/update-nexus-5-to-resurrection-remix-android-5-1/) firmware is finally here for Samsung Galaxy Note 3 updating the device to the latest Android 5.1 Lollipop. Based on CM 12, Resurrection Remix is one stable and smooth custom ROM. Here is how to update Galaxy Note 3 N9005 to Android 5.1 Lollipop based Resurrection Remix.
http://cdn.wccftech.com/wp-content/uploads/2013/10/galaxy-note-3-versions.jpg (http://cdn.wccftech.com/wp-content/uploads/2013/10/galaxy-note-3-versions.jpg)
Resurrection Remix Android 5.1 Lollipop features:






Dark Material Theme
Quick-Smart pull down
Buttons
Battery mods
Heads up
Lock screen Shortcuts
Clock Color options
Status bar clock customization + second + fonts
Network traffic monitor
Toast animations
List view animations
Navigation bar dimensions
Add Weather display to status bar header
Quick unlock
Overall Speed up system
Amazing Battery Life (http://wccftech.com/fix-galaxy-s6-battery-issues/)
Brand new music and audio fx app from cyanogen
Included all cm 12 features

Prerequisites to update Galaxy Note 3 N9005 to Android 5.1 Lollipop:

Backup any important data (http://wccftech.com/how-to-backup-sms/) from your Samsung Galaxy Note 3 as a complete wipe will be required during the flashing process.
Enable USB debugging option on your device: Settings > Development Options > USB debugging.
Samsung Galaxy Note 3 N900 must be rooted (http://wccftech.com/root-galaxy-note-3-n9005-on-xxuend6-android-4-4-2/), unlocked and installed with a recovery tool like TWRP or CWM.
Your device must be charged to at least 60% of power.

Update Galaxy Note 3 N9005 to Android 5.1 custom ROM: Required files: download Resurrection Remix Android 5.1 Lollipop custom firmware (http://wccftech.com/update-galaxy-s3-i9300-to-android-5-1-cm-12-1/) for Galaxy Note 3 N9005 from here (https://www.androidfilehost.com/?fid=95916177934552313) and save it on your computer. Do not extract the contents. Also download the Google Apps Package for your Note 3 from here (http://wccftech.com/download-latest-google-apps-android-1/).


Connect Galaxy (http://wccftech.com/unfreeze-android-smartphone-tips/) Note 3 N9005 to your computer using a USB cable and copy the zip file to your phone’s SD card.
Disconnect the USB cord and power off your Samsung Galaxy (http://wccftech.com/fix-galaxy-s6-battery-issues/) Note 3.
Boot it into recovery mode by pressing and holding Volume Up + Home + Power buttons together.
Perform a Nandroid backup of your current OS: Backup > backup and restore on ClockworkMod recovery.
Wipe data task: from CWM recovery menu, select wipe data / factory reset and confirm the process. Then go on to wipe cache partition and wipe dalvik cache.
From recovery menu, select install zip from sdcard followed by choose zip from sdcard. Locate the Resurrection Remix Android 5.1 custom firmware (http://wccftech.com/update-htc-one-m8-to-android-5-1-cm-12-1/) and confirm the flashing process.
Once done, repeat the above step for installing Gapps on your smartphone.
After installation is done successfully, return back to main recovery menu and reboot your Note 3 N9005 into the new custom ROM. First boot takes a good 5 minutes so please be patient.

How to restore: If you want to return to previous OS on your Note 3, boot into recovery, select backup and restore then restore your previous ROM by selecting it from the list.
- Recommended: Fix “Root Access Possibly Lost” and “Root access missing” Error Messages on Android (http://wccftech.com/fix-missing-or-lost-root-access/)







Noticia:
http://wccftech.com/update-galaxy-note-3-n9005-to-android-5-1/#ixzz3XZcbFmC3

[Jorge-Vieira]

Android 5.1.1 Lollipop Coming Soon Possibly to Fix “Memory Leak” Issue

Google had only just beginning to roll out the official Android 5.1 (http://wccftech.com/install-official-android-5-1-on-nexus-4/) Lollipop update for Nexus smartphones and tablets in the last few weeks. However, it looks like we will be seeing another update very soon. Android 5.1.1 Lollipop has been confirmed by Google. The update was spotted running on the Nexus 9 and WiFi Nexus 7 (2013) devices on Google’s Android Audio Latency information page. 5.1.1 update is coming to fix the issues that 5.1 couldn’t, especially app crashes and device (http://wccftech.com/flash-android-5-1-on-nexus-5/) reboots.
http://cdn2.wccftech.com/wp-content/uploads/2014/11/Nexu-7-Nexus-9-Nexus-10-Android-5.0-Lollipop-AOSPA.jpg (http://cdn2.wccftech.com/wp-content/uploads/2014/11/Nexu-7-Nexus-9-Nexus-10-Android-5.0-Lollipop-AOSPA.jpg)
Android 5.1.1 lollipop for Nexus 9 and Nexus 7: Google had announced the very latest Android 5.1 Lollipop (http://wccftech.com/update-galaxy-note-3-n9005-to-android-5-1/) in March fixing earlier bugs and improving performance. The Android 5.1.1 update is expected to be released very soon for the Nexus devices. Build numbers LMY47S and LMY47W were seen powering the Nexus 9 and the Nexus 7 (2013), respectively. This update will likely be an incremental update for usual bug fixing. Considering there are reports of still some major bugs remained to be fixed, it could give us some context on why Google is sending out another update that close to the Android 5.1 Lollipop (http://wccftech.com/update-galaxy-s3-i9300-to-android-5-1-cm-12-1/).
Google has so far rolled out Android 5.1 Lollipop for Nexus 6, Nexus 7 2012 WiFi, Nexus 10, Nexus 4, Nexus 5, and some other devices (http://wccftech.com/fix-galaxy-s6-battery-issues/). Considering that Nexus 9 is still on the Android 5.0.1 Lollipop, the device is likely to see a direct update to Android 5.1.1 fixing all the major issues. Nexus 7 also received the update only a few days back.
Here is the Android 5.1.1 Lollipop LMY47S and LMY47W for Nexus 9 and Nexus 7 2013 screenshot:





http://cdn4.wccftech.com/wp-content/uploads/2015/04/nexus2cee_511-668x342-635x325.jpg (http://cdn.wccftech.com/wp-content/uploads/2015/04/nexus2cee_511-668x342.jpg)
Android 5.1 is packed with various little issues including quite a major memory leak bug. This problem is causing app crashes and performance lags in the devices (http://wccftech.com/qualcomm-reconsiders-chip-business-samsungs-snapdragon-due-patent-royalties/) updated to the Lollipop. Google is expected to release the next update quite soon to fix this issue. However, this is no confirmation that we will actually be seeing one in coming week or so as this could very well just be a sign of Google testing the update with no intention of rolling it out anytime soon. Unlikely, but you never know.
Android 5.1.1 will be fixing the memory leak issue along with other little bugs too. The update will stable the performance of devices and possibly improve battery (http://wccftech.com/fix-galaxy-s6-battery-issues/) life too.
– Source: Android Audio Latency (http://source.android.com/devices/audio/latency_measurements.html) VIA Android Authority (http://www.androidauthority.com/android-5-1-1-references-googles-site-601945/)







Noticia:
http://wccftech.com/android-5-1-1-lollipop-to-fix-memory-leak-issue/#ixzz3XfMRRBF9

[Jorge-Vieira]

Update Xperia Z2 to Android 5.1 Based Resurrection Remix – How to

Sony has managed to disappoint many with the latest release of Xperia Z4 (http://wccftech.com/sony-xperia-z4-images/). The design is pretty much the same as the Sony Xperia Z2 so many users would perhaps be holding on to that device. Which essentially means we need to keep updating you with latest stable ROMs to flash on your Xperia Z2. Here is the popular stable and fast Resurrection Remix custom firmware; follow these guides to update Xperia Z2 to Android 5.1 based Resurrection Remix (http://wccftech.com/update-nexus-5-to-resurrection-remix-android-5-1/) ROM.
http://cdn2.wccftech.com/wp-content/uploads/2014/01/Capture1.jpg (http://cdn2.wccftech.com/wp-content/uploads/2014/01/Capture1.jpg)
Resurrection Remix Android 5.1 Lollipop features:

Navigation Bar
Enable/Disable Navbar
Navbar Ring Switch
Navbar Ring Targets
Navbar Button Customization
Navbar Dimensions (Potrait & Landscape)

- Also, read: Galaxy S6 edge Tips to Help You Take the Best Out of Your Curved Phone (http://wccftech.com/galaxy-s6-edge-tips/)




Prerequisites to update Xperia Z2 to Android 5.1 Resurrection Remix:

Backup any important data (http://wccftech.com/how-to-backup-sms/) from your Sony Xperia Z2 as a complete wipe will be required during the flashing process.
Make sure ADB and Fastboot is configured on your PC.
Sony Xperia (http://wccftech.com/lg-g4-xperia-z4-gpu-benchmark-rumor-roundup/) Z2 must be rooted with unlocked bootloader and installed with a recovery tool.
Your device must be charged to at least 60% of power.

How to update Xperia Z2 to Android 5.1: Required files: download Resurrection Remix Android 5.1 Lollipop custom firmware for Xperia Z2 from here (https://www.androidfilehost.com/?fid=95916177934553117) and save it on your computer. Extract boot.img file. Also download Google Apps Package (http://wccftech.com/download-latest-google-apps-android-1/).


Connect your Xperia Z2 to your computer using a USB cable and copy the zip file and GApps to your phone memory’s root folder.
Copy the boot.img file to android-sdk-windows\platform-tools directory.
Switch off your Xperia (http://wccftech.com/xperia-z4-leaked-image-press-photo/) Z2 and enter Bootloader mode: press and hold the Volume Up button while connecting the phone with USB cable. Phone LED will turn blue indicating the Bootloader mode.
Once in the Fastboot mode, on your PC navigate to android-sdk-windows\platform-tools directory and open Command Prompt with Shift + Right-click > Open Command Prompt.
Type the following command and press Enter:

fastboot flash boot boot.img


Type the command and press Enter:

fastboot reboot


Enter in the Recovery Mode: switch on the phone while pressing the Volume Up button a few times.
Wipe data task: from CWM recovery menu, select wipe data / factory reset and confirm the process.
Also clean cache from wipe cache partition.
From recovery menu, select install zip from sdcard followed by choose zip from sdcard. Locate the Resurrection Remix Android 5.1 Lollipop (http://wccftech.com/android-5-1-1-lollipop-to-fix-memory-leak-issue/) custom firmware and confirm the flashing process.
Once done, return back to main recovery menu and reboot your into the new custom ROM.
First boot takes a good 5 minutes so please be patient.

Enjoy lollipop (http://wccftech.com/update-galaxy-note-3-n9005-to-android-5-1/) on your iconic Xperia Z2.









Noticia:
http://wccftech.com/update-xperia-z2-to-android-5-1/#ixzz3Xx7CVTfT

[Jorge-Vieira]

Update HTC One M7 to Android 5.1 Based TeamUB Custom ROM – How to

You can now update your HTC One (http://wccftech.com/latest-htc-m9-images/) M7 to the latest Android 5.1 Lollipop and enjoy its amazing features. This has become possible thanks to TeamUB custom firmware which is full of features and is one stable ROM too! Here is how to update HTC One M7 to Android 5.1 Lollipop based TeamUB custom ROM.
http://cdn4.wccftech.com/wp-content/uploads/2015/04/P1030274-940x705-635x476.jpg (http://cdn4.wccftech.com/wp-content/uploads/2015/04/P1030274-940x705.jpg)
- Also, read: Galaxy S6 edge Tips to Help You Take the Best Out of Your Curved Phone (http://wccftech.com/galaxy-s6-edge-tips/)




Prerequisites to update HTC One M7 to Android 5.1 TeamUB custom ROM:

Backup any important data (http://wccftech.com/how-to-backup-sms/) from your HTC One M7 as a complete wipe will be required during the flashing process.
Make sure ADB and Fastboot is configured on your PC.
Your device must be rooted with unlocked bootloader (http://wccftech.com/how-to-root-verizon-htc-one-and-install-cwm-twrp-recovery/) and installed with a recovery tool.
Your device must be charged to at least 60% of power.

How to update HTC One M7 to Android 5.1: Required files: download TeamUB Android 5.1 Lollipop custom firmware for HTC One from here (http://roms.abun880007.co.uk/cm/m7/cm-12.1-20150415-m7.zip) and save it on your computer. Extract boot.img file. Also download Google Apps Package (http://wccftech.com/download-latest-google-apps-android-1/).


Connect your One M7 to your computer using a USB cable and copy the zip file and GApps to your phone (http://wccftech.com/xperia-z4-ultra-and-xperia-z4-compact-spotted/) memory’s root folder.
Copy the boot.img file to android-sdk-windows\platform-tools directory.
Switch off HTC One M7 and enter Bootloader mode: press and hold the Volume Down and Power buttons.
Once in the Fastboot mode, on your PC navigate to android-sdk-windows\platform-tools directory and open Command Prompt with Shift + Right-click > Open Command Prompt.
Type the following command and press Enter:

fastboot flash boot boot.img


Type the command and press Enter:

fastboot reboot


Follow onscreen instructions and select Bootloader.
Enter in the Recovery Mode: switch on the phone while pressing the Volume Up button a few times.
Wipe data task: from CWM recovery menu, select wipe data / factory reset and confirm the process.
Also clean cache from wipe cache partition.
From advanced, clean the dalvik cache as well – optional.
From recovery menu, select install zip from sdcard followed by choose zip from sdcard. Locate the TeamUB Android 5.1 Lollipop (http://wccftech.com/android-5-1-1-lollipop-to-fix-memory-leak-issue/) custom firmware and confirm the flashing process.
Once done, return back to main recovery menu and reboot your into the new custom ROM.
First boot takes a good 5 minutes so please be patient.

Enjoy lollipop (http://wccftech.com/update-galaxy-note-3-n9005-to-android-5-1/) on your HTC One M7.
Relevant, Update HTC One M8 to Android 5.1 Lollipop CM 12.1 Custom ROM (http://wccftech.com/update-htc-one-m8-to-android-5-1-cm-12-1/)








Noticia:
http://wccftech.com/how-to-update-htc-one-m7-to-android-51-lollipop/#ixzz3Y1UEwFQg

[Jorge-Vieira]

Update Galaxy S3 I747 to Android 5.1 Based PAC-MAN – How to

Official Pac-Man custom firmware has now been released for Android 5.1 Lollipop (http://wccftech.com/android-5-1-1-lollipop-to-fix-memory-leak-issue/). Packed with a ton of features, Pac-Man has always remained one of a favorite custom ROM. Here is how to update Galaxy S3 I747 to Android 5.1 Lollipop based Pac-Man.
– Recommended: Some of the Galaxy S6 and S6 Edge Bugs and Fixes – Tips (http://wccftech.com/galaxy-s6-bugs-and-their-fixes/) http://cdn3.wccftech.com/wp-content/uploads/2013/02/carbon-rom-for-galaxy-s3.jpg (http://cdn3.wccftech.com/wp-content/uploads/2013/02/carbon-rom-for-galaxy-s3.jpg)
Prerequisites to update Galaxy S3 I747 to Android 5.1 Lollipop:

Backup any important data (http://wccftech.com/how-to-backup-sms/) from your Samsung Galaxy S3 SGH-I747 as a complete wipe will be required during the flashing process.
Enable USB debugging option on your device: Settings > Development Options > USB debugging.
Samsung Galaxy (http://wccftech.com/galaxy-s6-bugs-and-their-fixes/) S3 must be rooted, unlocked and installed with a recovery tool like TWRP or CWM.
Your device must be charged to at least 60% of power.

Note: this tutorial is focused on AT&T Samsung (http://wccftech.com/tether-galaxy-s6-and-galaxy-s6-edge/) Galaxy S3 SGH-I747; kindly do not try this guide on other Android (http://wccftech.com/android-l-vs-ios-8/) & Samsung (http://wccftech.com/fix-galaxy-s6-battery-issues/) devices.



How to update Galaxy S3 I747 to Android 5.1 PAC-MAN: Required files: download the PacMan Android 5.1 (http://wccftech.com/update-galaxy-s3-i9300-to-android-5-0/) Lollipop custom firmware for Galaxy S3 I747 from here (https://basketbuild.com/devs/pacman/d2att/Official) and save it on your computer. Also download GApps (http://wccftech.com/download-latest-google-apps-android-1/) package. Do not extract the contents.


Connect Galaxy S3 (http://wccftech.com/update-galaxy-s3-i9300-to-android-5-1-cm-12-1/) to your computer using a USB cable and copy the zip file to your phone’s SD card.
Disconnect the USB cord and power off your Galaxy S3 (http://wccftech.com/update-galaxy-s3-i747-to-android-4-4-4-slimkat/).
Boot it into recovery mode by pressing and holding Volume Up + Home + Power buttons together.
Perform a Nandroid backup of your current OS: Backup > backup and restore on ClockworkMod recovery.
Wipe data task: from CWM recovery menu, select wipe data / factory reset and confirm the process. Then go on to wipe cache partition and wipe dalvik cache.
From recovery menu, select install zip from sdcard followed by choose zip from sdcard. Locate the PAC-MAN Android 5.1 Lollipop custom firmware and confirm the flashing process.
Return back to main recovery menu and reboot your AT&T Samsung Galaxy (http://wccftech.com/how-to-enter-galaxy-s6-download-mode/) S3 into the new custom ROM. First boot takes a good 5 minutes so please be patient.

How to restore: If you want to return to previous OS on your SGS3, boot into recovery, select backup and restore then restore your previous ROM by selecting it from the list.
– Recommended: Fix “Root Access Possibly Lost” and “Root access missing” Error Messages on Android – How to (http://wccftech.com/fix-missing-or-lost-root-access/)









Noticia:
http://wccftech.com/update-galaxy-s3-i747-to-android-5-1-pacman/#ixzz3YgNPWYae

[Jorge-Vieira]

Update Galaxy Note 2 N7100 to Android 5.1.1 Lollipop Based TeamUB – How to

Samsung Galaxy Note 2 N7100 finally receives some Lollipop (http://wccftech.com/update-galaxy-note-3-n9005-to-android-5-1/) love as TeamUB custom firmware based on Android 5.1.1 is now available for the device. Filled with tons and tons of features, the ROM is quite stable – based on the reviews received on the ROM for other devices it has been made available for. Here is how to update Galaxy Note 2 N7100 to Android 5.1.1 Lollipop based TeamUB (http://wccftech.com/how-to-update-htc-one-m7-to-android-51-lollipop/).
– Recommended: Some of the Galaxy S6 and S6 Edge Bugs and Fixes – Tips (http://wccftech.com/galaxy-s6-bugs-and-their-fixes/) http://cdn2.wccftech.com/wp-content/uploads/2013/03/sphl9001.jpeg (http://cdn2.wccftech.com/wp-content/uploads/2013/03/sphl9001.jpeg)

TeamUB Android 5.1.1 Lollipop features:






OTA updates
Centre clock
Battery percent in the status bar
Network traffic indicator
Date settings
Listview animations
AOKP System animations
Lockscreen Shortcuts
Quixk settings Customization
Heads up notifications
Proximity speaker
Performance settings
Network Traffic
App circle sidebar
Clock fonts
Battery styles
Wakelock blocker
DSLV controller
Statusbar ticker
Apps to SD
Nav Bar height
Status bar double tap to sleep
Custom notification lights
Recent Panel settings
Privacy options
Fluid interface
Best battery improvements
All latest CM commits

Prerequisites to update Galaxy Note 2 N7100 to Android 5.1.1:

Backup any important data (http://wccftech.com/how-to-backup-sms/) from your Samsung Galaxy Note 2 as a complete wipe will be required during the flashing process.
Enable USB debugging option on your device: Settings > Development Options > USB debugging.
Samsung Galaxy (http://wccftech.com/galaxy-s6-bugs-and-their-fixes/) Note 2 must be rooted, unlocked and installed with a recovery tool like TWRP or CWM.
Your device must be charged to at least 60% of power.

Note: this tutorial is focused on Samsung (http://wccftech.com/tether-galaxy-s6-and-galaxy-s6-edge/) Galaxy Note 2 N7100; please do not try this guide on other Android (http://wccftech.com/android-l-vs-ios-8/) & Samsung (http://wccftech.com/fix-galaxy-s6-battery-issues/) devices.
How to update Galaxy Note 2 N7100 to Android 5.1.1 TeamUB: Required files: download the TeamUB Android 5.1 (http://wccftech.com/update-galaxy-s3-i9300-to-android-5-0/) Lollipop custom firmware for Galaxy Note 2 N7100 from here (http://roms.abun880007.co.uk/cm/n7100/) and save it on your computer. Also download GApps (http://wccftech.com/download-latest-google-apps-android-1/) package. Do not extract the contents.


Connect Galaxy Note (http://wccftech.com/update-galaxy-note-3-n9005-to-android-5-1/) 2 to your computer using a USB cable and copy the zip file to your phone’s SD card.
Disconnect the USB cord and power off your Galaxy Note 2 (http://wccftech.com/install-aokp-android-4-4-4-on-note-2-lte/).
Boot it into recovery mode by pressing and holding Volume Up + Home + Power buttons together.
Perform a Nandroid backup of your current OS: Backup > backup and restore on ClockworkMod recovery.
Wipe data task: from CWM recovery menu, select wipe data / factory reset and confirm the process. Then go on to wipe cache partition and wipe dalvik cache.
From recovery menu, select install zip from sdcard followed by choose zip from sdcard. Locate the TeamUB Android 5.1 Lollipop custom firmware and confirm the flashing process.
Return back to main recovery menu and reboot your Note 2 into the new custom ROM. First boot takes a good 5 minutes so please be patient.

– Recommended: Fix “Root Access Possibly Lost” and “Root access missing” Error Messages on Android – How to (http://wccftech.com/fix-missing-or-lost-root-access/)







Noticia:
http://wccftech.com/how-to-update-galaxy-note-2-n7100-to-android-5-1-1/#ixzz3YgNnnxe7

[Jorge-Vieira]

Guide to Downgrade Android Firmware From Lollipop to KitKat

Android 5.0 Lollipop (http://wccftech.com/android-5-1-1-lollipop-to-fix-memory-leak-issue/) is rolling out for every other device and we have been flooding you with all the stable and popular custom ROMs (http://wccftech.com/how-to-update-galaxy-note-2-n7100-to-android-5-1-1/) that we can find. However, not all are fans of this latest Material Design curtain over the KitKat. While appreciated for its simplicity and intuitiveness, there could be many for whom it’s rather hard to upgrade. Consider the tons of bugs and we are talking about many users who want to switch back. Worry not, as this guide is for you! Here is how to downgrade Lollipop to KitKat on Nexus devices (http://wccftech.com/update-galaxy-s3-i747-to-android-5-1-pacman/).
– Relevant: Flash Resurrection Remix Android 5.1 on Nexus 5 (http://wccftech.com/update-nexus-5-to-resurrection-remix-android-5-1/) http://cdn4.wccftech.com/wp-content/uploads/2015/02/Android-51-Lollipop-main.jpg (http://cdn4.wccftech.com/wp-content/uploads/2015/02/Android-51-Lollipop-main.jpg)
Prerequisites to downgrade Lollipop to KitKat:






Create a backup (http://wccftech.com/how-to-backup-sms/) of your device – MUST to-do step!
Make sure USB Debugging is enabled on your Nexus. You can enable from Settings > Developer Options > toggle USB Debugging on.
If you don’t see the Developer Option, go to About Phone and tap Build Number multiple times until you see the notification pop up.
Your Nexus (http://wccftech.com/galaxy-s6-vs-iphone-6-vs-htc-one-m9-vs-nexus-6/) should be charged up to at least 70%.
Your Nexus should have an unlocked bootloader.

How to downgrade Lollipop to KiKat: Required files: download the factory image for your Nexus from here (https://developers.google.com/android/nexus/images). Download ADB Tools (http://files.androidpit.info/content/adb-tools_treiber.zip) on your PC. Move the factory image file into ADB Tools folder and extract it.


Turn your Nexus off and enter into Fasboot mode: press and hold Power and the Volume Down keys to enter.

If you have a custom recovery installed, use the Volume buttons to select Recovery Mode and press the Power button to confirm.
In case of stock recovery, press the Power key followed by Volume Up button to when see the Android bot. Once in the Recovery Mode, you will be able to navigate with the Volume buttons and confirm with the Power key.


Once in the recovery, clear cache by scrolling down to wipe cache partition.
Also wipe data / factory reset; use Power key to confirm.
Next, connect your Nexus to your PC with a USB cable.
Open the ADB Tools folder. Locate the flash-all.bat file and double-click it.
The process will start now which will reboot your Nexus once it has been flashed with downgraded Android version.
Once you see the Nexus getting back up, setup the device like you usually do and ta da!

– Some of the Galaxy S6 Bugs and Their Fixes (http://wccftech.com/galaxy-s6-bugs-and-their-fixes/)






Noticia:
http://wccftech.com/how-to-downgrade-lollipop-firmware-on-nexus/#ixzz3YgOAK0VB

[Jorge-Vieira]

Guide to Update T-Mobile Galaxy S3 T999 to Android 5.1.1 CyanogenMod 12.1

Android 5.1.1 Lollipop (http://wccftech.com/android-5-1-1-lollipop-to-fix-memory-leak-issue/) is now out which means we are seeing some major custom ROMs getting the update too. You can now update your Samsung Galaxy S3 T999 to Android 5.1.1 based CyanogenMod 12.1 custom firmware. While you won’t see the official Android 5.1.1 update coming from T-Mobile, there is no reason why you shouldn’t update your phone via the custom means. Follow this guide to update Galaxy S3 T999 to CM12.1 Android 5.1.1 Lollipop custom ROM (http://wccftech.com/update-galaxy-s4-i9500-to-android-5-1-lollipop/).
– Recommended: Bugs Reported in Samsung Galaxy S6 and S6 edge and their Fixes (http://wccftech.com/galaxy-s6-bugs-and-their-fixes/) http://cdn4.wccftech.com/wp-content/uploads/2014/10/cyanogenmod-cid-mascot.jpg (http://cdn4.wccftech.com/wp-content/uploads/2014/10/cyanogenmod-cid-mascot.jpg)
Prerequisites to update Galaxy S3 T999 to CM12.1 Android 5.1.1:

Backup any important data (http://wccftech.com/how-to-backup-sms/) from your Samsung Galaxy S3 SGH-T999 as a complete wipe will be required during the flashing process.
Enable USB debugging option on your device: Settings > Development Options > USB debugging.
Samsung Galaxy S3 T999 must be rooted, unlocked and installed with a recovery tool like TWRP or CWM.
Your device must be charged to at least 60% of power.

Note: this tutorial is focused on T-Mobile Samsung Galaxy S3 SGH-T999; please do not try this guide on other Android (http://wccftech.com/lg-g4-benchmark-snapdragon-808-vs-snapdragon-810/) & Samsung (http://wccftech.com/fix-galaxy-s6-battery-issues/) devices.





How to update Galaxy S3 T999 to CM12.1 Android 5.1.1: Required files: download CyanogenMod 12.1 Android 5.1.1 custom firmware for Galaxy S3 from here (https://www.androidfilehost.com/?fid=96042739161892217) and save it on your computer. Do not extract the contents.


Connect Galaxy (http://wccftech.com/unfreeze-android-smartphone-tips/) S3 to your computer using a USB cable and copy the zip file to your phone’s SD card.
Disconnect the USB cord and power off your Galaxy S3 (http://wccftech.com/how-to-update-galaxy-s3-to-android-4-4-kitkat-based-cm-11/).
Boot it into recovery mode (http://wccftech.com/how-to-enter-galaxy-s6-download-mode/) by pressing and holding Volume Up + Home + Power buttons together.
Perform a Nandroid backup of your current OS: Backup > backup and restore on ClockworkMod recovery.
Wipe data task: from CWM recovery menu, select wipe data / factory reset and confirm the process. Then go on to wipe cache partition and wipe dalvik cache.
From recovery menu, select install zip from sdcard followed by choose zip from sdcard. Locate the CM12.1 Android 5.1.1 custom firmware and confirm the flashing process.
Return back to main recovery menu and reboot your T-Mobile Samsung Galaxy S3 into the new custom ROM. First boot takes a good 5 minutes so please be patient.

How to restore: If you want to return to previous OS on your SGS3, boot into recovery, select backup and restore then restore your previous ROM (http://wccftech.com/how-to-downgrade-lollipop-firmware-on-nexus/) by selecting it from the list.
– Recommended: Fix “Root Access Possibly Lost” and “Root access missing” Error Messages on Android – How to (http://wccftech.com/fix-missing-or-lost-root-access/)







Noticia:
http://wccftech.com/update-galaxy-s3-t999-to-cm12-1-android-5-1-1/#ixzz3YiTe0F5f

[Jorge-Vieira]

One M8 To Get Sense 7 UI and 5.1 Lollipop Update In August – Says HTC

HTC has replaced its flagship for the year with HTC M9 that comes fully loaded with all the features that M8 users can hope for. However, HTC has confirmed its HTC One M8 model to be upgraded with two of the most wanted features, the Sense 7 UI and Androids update to the latest 5.1 firmware. Both of these features will be debuted in August. So all those users who did not update their One M8 models to M9, are advised to wait a little longer to benefit from Sense 7 and Android Lollipop 5.1 update.
http://cdn2.wccftech.com/wp-content/uploads/2014/08/a4.jpg (http://cdn2.wccftech.com/wp-content/uploads/2014/08/a4.jpg)
The news was confirmed on Twitter by HTC UK that said, “The HTC One M8 will have a Software Update for Android Version 5.1 and Sense 7 in August 2015.” Previously, the HTC One M8 was updated to Lollipop in January that brought with it enhanced Material Design features and updated applications. Some of the new features include Notification Cards on lock screen, improved privacy and enhanced search privileges.
HTC One M8 To Get Sense 7 UI And Lollipop 5.1 Update In August HTC One M8’s update to the Lollipop 5.1 firmware will bring stability, enhanced functionality and performance improvements under the hood. An important addition will include HD voice on supported devices along with device protection. initially, the Android 5.1 upgrade started rolling out in March and a little late for HTC One M8 as of now. Lets talk about what HTC has in store for the upcoming update.
Sense 7 is packed with new features for HTC One M8 users, not to forget a smart launcher. The Smart Launcher displays preferred applications according to the location you’re in. The Sense 7 will bring joy to One M8 smartphone holders as HTC has supported new theme app and fonts, colors or other visual elements can also be customized. Along with enhanced UI, HTC has introduced ‘Morning Bundles’ which are packed with news categories and a person’s to-do list for the day. Morning Bundles are a great deal but as time goes, the preference shifts to Restaurant Bundles. the Restaurant Bundles are responsible to locate nearby places to eat and their menus.





http://cdn3.wccftech.com/wp-content/uploads/2015/03/HTC-Sense721-635x1129.png (http://cdn.wccftech.com/wp-content/uploads/2015/03/HTC-Sense721.png)

Image Courtesy: phonearena.com
Sense 6 and Sense 7 has minimal visual difference but the newer version corresponds to the Material Design better than the last gen version. We sure hope that M8 users will be joyed to see the change but as for now, a little wait till August will do no harm. As for now, lets hope HTC keeps to its word for the arrival of the Sense 7 and Android Lollipop 5.2 update. Do let us know i the comments, how you like the addition of Sense 7 in the HTC One M8.







Noticia:
http://wccftech.com/m8-sense-7-ui-51-lollipop-update-august-htc/#ixzz3Ys2oYq1q

[Jorge-Vieira]

Factory Images Of Android 5.1.1 Available For 2012, 2013 Nexus 7 Wi-Fi And Nexus 10

Good news! Nexus owners. Google is releasing factory images for various devices and they have already started to roll out on some of the devices. this time Google has spotted two devices, the Nexus 10 and Nexus 7. So if you have a 2012 or a 2013 Wi-Fi Nexus 7 device, you can upgrade its firmware to the latest version of Android lollipop.
http://cdn2.wccftech.com/wp-content/uploads/2014/10/Nexus-Family-635x325.jpg (http://cdn.wccftech.com/wp-content/uploads/2014/10/Nexus-Family.jpg)
The factory images of various devices helps a user to upgrade their device to the latest operating system. In this case, Google’s factory images for the 2012 and 2013 Wi-Fi Nexus 7 and Nexus 10 will enable devices to be updated t the recent and most latest firmware, the Android’s flavor of Lollipop version 5.1.1.Hence users might benefit from the latest update through various means. Lets head on to look at some of the details on these factory images by Google.
Nexus Devices Get Factory Images To Android 5.1.1 With Build Number LMY47V Google is rolling out factory images for the 2012 Wi-Fi versions of Nexus 7 with build number of ‘LMY47V’, apart fro this the 2013 Nexus 7 on Wi-Fi and the Nexus 10. Users will have more functionality and under the hood improvements in terms of software. If you wish to download factory images for the Nexus devices, you can download from the factory images with the corresponding model number re provided below. Flash them to your device and you will have the latest Android 5.1.1 in no time.







2012 Wi-Fi Nexus 7 – Android 5.1.1 Factory Image (Build LMY47V) (https://dl.google.com/dl/android/aosp/nakasi-lmy47v-factory-b48bd71d.tgz)
2013 Wi-Fi Nexus 7 – Android 5.1.1 Factory Image (Build LMY47V) (https://dl.google.com/dl/android/aosp/razor-lmy47v-factory-a58e6175.tgz)
Nexus 10 – Android 5.1.1 Factory Image (Build LMY47V) (https://dl.google.com/dl/android/aosp/mantaray-lmy47v-factory-91a865a6.tgz)

There is an option available for these device holders, who wish to upgrade their operating system to Android 5.1.1. Users can either directly flash these updates to their devices or wait for the original OTA (over the air) to arrive in the upcoming days or weeks. this is because it might be possible that the updated firmware through these factory images might have bugs to begin with. In the original update, hopefully they might be eliminated by Google.
(http://cdn.wccftech.com/wp-content/uploads/2014/10/2615109_Tinhte-Google-Nexus9-9.jpg)
http://cdn4.wccftech.com/wp-content/uploads/2014/10/2615078_Tinhte-Google-Nexus9-6-635x422.jpg (http://cdn2.wccftech.com/wp-content/uploads/2014/10/2615078_Tinhte-Google-Nexus9-6.jpg)
Do take note that data on your device will be completely wiped out when flashing these factory images, so do back up. If you did use these factory images to upgrade your firmware, let us know about any new features and your experience with Android’s latest version 5.1.1.







Noticia:
http://wccftech.com/factory-images-android-511-2012-2013-nexus-10-nexus-7-wifi/#ixzz3YuI93KEY

[Jorge-Vieira]

Install Android 5.1.1 On Nexus 7 And Nexus 10, Right Now!

As we mentioned earlier, Google has just release factory images of the 2012, 2013 Nexus 7 and Nexus 10. (http://wccftech.com/factory-images-android-511-2012-2013-nexus-10-nexus-7-wifi/) These factory images are used to upgrade the operating system from the current firmware to the latest Android 5.1.1 in the aforementioned Nexus devices. If you don’t know how to utilize these factory images then that’s what we’re here for. We will show you the general how-to to upgrade your Nexus OS to the latest Android 5.1.1 through these factory images.
(http://cdn2.wccftech.com/wp-content/uploads/2014/10/2615078_Tinhte-Google-Nexus9-6.jpg)
http://cdn4.wccftech.com/wp-content/uploads/2015/05/maxresdefault-635x357.jpg (http://cdn3.wccftech.com/wp-content/uploads/2015/05/maxresdefault.jpg)
Google is due to rolling out factory images for the Nexus 4, Nexus 5 and Nexus 6 which might take a while, expectantly soon. The Nexus 9 update has also not moved farther than the basic 5.0.1 and hopefully Google considers it to be part of the rolling out scheme as well. Even though some leaks have been found of Nexus 9 running on the latest 5.1.1 firmware but details on official release remain silent. Anyways, without further ado, lets get to updating your Nexus 7 and 10 to the latest Android version, 5.1.1.
Install Android 5.1.1 On Your Nexus 7 and Nexus 10 – How To To begin the upgrade process, you should first download the factory images to your required device. Here are the three factory images to different variant Nexus devices.


2012 Wi-Fi Nexus 7 Android 5.1.1 Factory Image (https://dl.google.com/dl/android/aosp/nakasi-lmy47v-factory-b48bd71d.tgz)
2013 Wi-Fi Nexus 7 Android 5.1.1 Factory Image (https://dl.google.com/dl/android/aosp/razor-lmy47v-factory-a58e6175.tgz)
Nexus 10 Android 5.1.1 Factory Image (https://dl.google.com/dl/android/aosp/mantaray-lmy47v-factory-91a865a6.tgz)

Step 1: Unzip the downloaded factory images for your device to a folder for later access. Lets say we unzipped the folder the Desktop on Mac. Locate the folder and type cmd to the address bar on Windows or launch terminal and chnage this folder with the one we saved on Mac, Chrome OS or Linus. Make sure the terminal is running inside the unzipped folder if you’re operating on a Mac.
Step 2: Your Nexus 7 or Nexus 10 should be bootloader unlocked for the operation to succeed, if its not, better do that first. The locked device will enable all of you data to be wiped away that also includes settings and user data. Next, you have to have adb bootloader installed on your Mac, Windows or whatever system you are running. Install it if you don’t have it. Assuming you installed the adb bootloader, type the command written below in the terminal of the adb Bootloader. Hit Enter.

adb reboot bootloader Type this In Fastboot:

fastboot oem unlock Hit Enter and follow the instructions you get on the screen of your Nexus and choose to erase the device. This will remove everything on the Nexus, this might a while.





http://cdn2.wccftech.com/wp-content/uploads/2015/05/Install-Android-L-Beta-on-Nexus-5-620x465.jpg (http://cdn2.wccftech.com/wp-content/uploads/2015/05/Install-Android-L-Beta-on-Nexus-5-620x465.jpg)
Step 3: This step will involve flashing the desired factory image to your Nexus device. Open the folder you unzipped containing the Android 5.1.1 factory image in step 1. In the address bar, type cmd and type the commands written below and press enter. On a Mac, you can either access the terminal by creating a shortcut through setting or by simply you can directly do it from the desktop as shown in the image below.
http://cdn2.wccftech.com/wp-content/uploads/2015/05/Screen-Shot-2014-10-17-at-11.52.31-AM-620x454.jpg (http://cdn2.wccftech.com/wp-content/uploads/2015/05/Screen-Shot-2014-10-17-at-11.52.31-AM-620x454.jpg)

When you click the ‘New Terminal At Folder’, copy paste the commands to install the update.

flash-all.bat All the necessary files will be flashed to your Nexus device to enable complete installation of the Android 5.1.1 update to your Nexus 7 or nexus 10. Mac or other computer users will type the following command. This command has a purpose to transfer all of the necessary files to your Nexus device.

sudo ./flash-all.sh Step 4: The files will be moved to your device and your Nexus device may restart. Don’t be surprised to see an Android bot and the moving logo, its part of the scheme. On a serious note: DO NOT UNPLUG OR POWER OFF YOUR DEVICE in this process, even though it may take ten minutes or so. When its done, the android will ask you to complete the setup. this is when you can uplug your device from the computer.
After this is done, enter your information and you’re all set to use Android’s latest flavor to Lollipop, the 5.1.1 upgrade. Do take note, if you are familiar with these terms and have tried flashing ROMs before, only then try to operate this. Else, for all the newbies, it is highly advised that you wait for the OTA (over the air) update that might arrive soon. Secondly, waiting for the OTA might be the best option since the update through factory images usually wipes all of your personal data. If you found this post helpful, do comment and give us your reviews.









Noticia:
http://wccftech.com/install-android-511-nexus-7-nexus-10/#ixzz3YxrWXaSP

[Jorge-Vieira]

How to Flash Resurrection Remix Android 5.1 Lollipop on Galaxy S3

There are reports that Samsung Galaxy S3 might not receieve the latest Android 5.1 Lollipop update. However, there are a ton of custom ROMs being made available to fill that gap. Here is how to flash feature-packed and very stable Resurrection Remix Android 5.1 Lollipop custom firmware on Samsung Galaxy S3 (http://wccftech.com/update-galaxy-s3-i9300-to-android-5-1-cm-12-1/).
http://cdn3.wccftech.com/wp-content/uploads/2013/03/i9305.jpeg (http://cdn3.wccftech.com/wp-content/uploads/2013/03/i9305.jpeg)
Resurrection Remix Android 5.1 features:

Navigation Bar
Navbar Button Customization
Navbar Dimensions(Potrait & Landscape)-Statusbar
Brightness Slider
Enable/Disable Show Notification Count
SuperUser Indicator Switch
Carrier Label, Switch, Colour
Quick PullDown Switch
Smart Pulldown Switch
Clock Customizations
Time & date
Clock Colour
Day & date Toogle
Center Clock/Right Clock Choice
Battery Bar customization
Battery Icon Customization(circle/landscape/Potrait and more)
Battery % Text
Network Traffic Indicator
Theme Chooser
RR exclusive PITCH BLACK THEME
Animations
Gestures
Optimizations to Improve Battery
ALL cm12 Features
and much more






Prerequisites to flash Resurrection Remix Android 5.1 on Galaxy S3:

Create a backup (http://wccftech.com/how-to-backup-sms/) of all important data in your Galaxy device.

Download and install USB drivers for Samsung Galaxy S3 (http://wccftech.com/download-android-usb-drivers/)in your computer.
Enable USB debugging option by pressing Menu > Settings > Applications. Navigate and tap on Developer Options to ensure that USB Debugging is enabled.
Make sure that recovery tool like ClockworkMod recovery (http://wccftech.com/root-install-cwm-recovery-on-galaxy-s3-sch-i535-android-411-412/) is installed.
Ensure that your Samsung Galaxy S3 i9300 carries more than 80% of charge.

Flash Resurrection Remix Android 5.1 custom ROM on Galaxy S3: Files required: download the Resurrection Remix Android 5.1custom firmware from here (https://www.androidfilehost.com/?fid=96039337900114366); also download the Google Apps (http://wccftech.com/download-latest-google-apps-android-1/). Save both files on PC.
Here are the steps to update Galaxy S3 i9300 to Resurrection Remix Android 5.1 Lollipop:


Connect your Samsung Galaxy S3 I9300 to your computer using USB cable and copy the downloaded files to the SD card of your Galaxy device.
Disconnect the connection with PC and turn your Galaxy S3 off.
Boot in to custom recovery mode: press and hold Volume Up, Down and the Power buttons simultaneously until Samsung (http://wccftech.com/update-galaxy-s2-i9100-to-android-5-1/) logo shows up. Leave the keys for half a second and hold again. Use Volume keys to scroll and Power button to select – alternatively you can use Quick Boot app (https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot) to reboot your Android device in recovery mode.
Data wiping tasks: select wipe data/factory reset > Yes. It will take a few minutes; once done, select wipe cache partition. Next tap on Advance > wipe Dalvik Cache to wipe Dalvik cache data too.
Select install zip from sdcard followed by choose zip from sdcard. Locate the Android 5.1 based Resurrection Remix custom ROM file copied earlier and select it. Tap on yes to confirm installation and wait for the ROM installation to be completed.
Once installation process is finished successfully, repeat the above step but choose GApps file instead to install the Google apps package on your SGS3 I9300.
Return to main recovery menu now and select reboot system now to boot up into the latest Android 5.1 Lollipop custom firmware for Samsung Galaxy S3 (http://wccftech.com/update-galaxy-s3-i9300-to-android-4-4-4/). It will take a bit of time during the first boot, so kindly be patient.
Ta da! Enjoy Lollipop on Galaxy S3.

How to restore: If you want to return to previous OS on your SGS3, boot into recovery, select backup and restore then restore your previous ROM by selecting it from the list.







Noticia:
http://wccftech.com/flash-resurrection-remix-android-5-1-on-galaxy-s3/#ixzz3ZBm24wmE

[Jorge-Vieira]

Update HTC One M7 to AICP Android 5.1.1 Lollipop Custom ROM – How to

You can now update your HTC One (http://wccftech.com/latest-htc-m9-images/) M7 to the latest Android 5.1.1 Lollipop and enjoy its amazing features. One of the best custom ROMs, Android Ice Cold Project (AICP) is now available for HTC One packing all the CM12 features. Here is how to update HTC One to Android 5.1.1 (http://wccftech.com/galaxy-s6-camera-update-isocell-raw-shooting/) Lollipop based AICP stable and fast custom ROM.
http://cdn3.wccftech.com/wp-content/uploads/2015/05/HTC-One-mini-2-Silver-grey-and-gold-635x464.jpg (http://cdn3.wccftech.com/wp-content/uploads/2015/05/HTC-One-mini-2-Silver-grey-and-gold.jpg)
– Also, read: Galaxy S6 edge Tips to Help You Take the Best Out of Your Curved Phone (http://wccftech.com/galaxy-s6-edge-tips/) AICP Android 5.1.1 lollipop features:






Almost all CM features
Proximity Call
Screenrecord
Add blocker
Notification FC Disabler
LCD Changer (persistent)
Gesture Anywhere
Recents Panel Settings
Omniswitch
App Circle Bar
Network Traffic on statusbar
Show CPU Info
Boot animation changer
CM Theme Engine
Slim Launcher
Slim’s Heads Up, with the ability to disable
QS Sync Tile
QS Screenshot Tile
QS Screenrecord Tile
QS Quick and Smart pull down
QS WiFi Detailed Tile View
QS Location Tile – Enable Advanced Settings

Prerequisites to update HTC One to AICP Android 5.1.1 custom ROM:

Backup any important data (http://wccftech.com/how-to-backup-sms/) from your HTC One M7 as a complete wipe will be required during the flashing process.
Make sure ADB and Fastboot is configured on your PC.
Your device must be rooted with unlocked bootloader (http://wccftech.com/how-to-root-verizon-htc-one-and-install-cwm-twrp-recovery/) and installed with a recovery tool.
Your device must be charged to at least 60% of power.

How to update HTC One to AICP Android 5.1.1: Required files: download AICP Android 5.1.1 Lollipop custom firmware for HTC One from here (http://dwnld.aicp-rom.com/) and save it on your computer. Extract boot.img file. Also download Google Apps Package (http://wccftech.com/download-latest-google-apps-android-1/).


Connect your One M7 to your computer using a USB cable and copy the zip file and GApps to your phone (http://wccftech.com/xperia-z4-ultra-and-xperia-z4-compact-spotted/) memory’s root folder.
Copy the boot.img file to android-sdk-windows\platform-tools directory.
Switch off HTC One M7 and enter Bootloader mode: press and hold the Volume Down and Power buttons.
Once in the Fastboot mode, on your PC navigate to android-sdk-windows\platform-tools directory and open Command Prompt with Shift + Right-click > Open Command Prompt.
Type the following command and press Enter:

fastboot flash boot boot.img


Type the command and press Enter:

fastboot reboot


Follow onscreen instructions and select Bootloader.
Enter in the Recovery Mode: switch on the phone while pressing the Volume Up button a few times.
Wipe data task: from CWM recovery menu, select wipe data / factory reset and confirm the process.
Also clean cache from wipe cache partition.
From advanced, clean the dalvik cache as well – optional.
From recovery menu, select install zip from sdcard followed by choose zip from sdcard. Locate the AICP Android 5.1.1 Lollipop (http://wccftech.com/update-nexus-4-to-android-5-1-1-lollipop/) custom firmware and confirm the flashing process.
Once done, return back to main recovery menu and reboot your into the new custom ROM.
First boot takes a good 5 minutes so please be patient.

Enjoy lollipop (http://wccftech.com/update-galaxy-note-3-n9005-to-android-5-1/) on your HTC One M7.
Relevant, Update HTC One M8 to Android 5.1 Lollipop CM 12.1 Custom ROM (http://wccftech.com/update-htc-one-m8-to-android-5-1-cm-12-1/)






Noticia:
http://wccftech.com/update-htc-one-to-aicp-android-5-1-1-aicp-custom-rom/#ixzz3ZRLnGknm

[Sardo]

Android 5.1.1 acabadinho de chegar ao meu Nexus 5 :)

[Jorge-Vieira]

Flash Android 5.1.1 AOSP Based AICP ROM on Galaxy Note 3 N900T – How to

Pure AOSP based and carrying popular CyanogenMod 12 (http://wccftech.com/update-galaxy-s4-i9505-to-android-5-1-cm12-1/) features, AICP Android 5.1.1 custom firmware is now available for T-Mobile Samsung Galaxy Note 3. Stable, smooth and carrying all CM12 components, here is how to update Note 3 N900T to Android 5.1.1 based AICP custom ROM (http://wccftech.com/update-note-4-n910f-to-android-5-1-1-aicp/).
– Recommended: Some of the popular Lollipop custom ROMs (http://wccftech.com/android-lollipop-custom-roms/) http://cdn4.wccftech.com/wp-content/uploads/2014/08/GhQyhHk1.png (http://cdn4.wccftech.com/wp-content/uploads/2014/08/GhQyhHk1.png)
AICP Android 5.1.1 Lollipop features:

Compiled from Android Ice Cold Project: AICP sources.
Version 9.0 Beta
Initial release
Android 5.1- R5
Old Layout
Proximity Call
Screenrecord
Add blocker
Notification FC Disabler
LCD Changer (persistent)
Gesture Anywhere
Recents Panel Settings
Omniswitch
App Circle Bar
Network Traffic on statusbar
Show CPU Info
Boot animation changer
CM Theme Engine
Slim Launcher
Slim’s Heads Up, with the ability to disable
QS Screenshot Tile
QS Screenrecord Tile
QS Quick and Smart pull down
QS WiFi Detailed Tile View
CM12 (http://wccftech.com/how-to-flash-cm12-1-on-xperia-z3/)features

Note: The link works with T-Mobile Samsung Galaxy Note 3 N900T. You can follow the steps with other Samsung Galaxy devices (http://wccftech.com/update-galaxy-s4-i9505-to-android-5-1-1-teamub/), but do not use this ROM zip file with any other device.





Before you update Note 3 N900T to Android 5.1.1 AICP ROM:

Backup any important data (http://wccftech.com/how-to-backup-sms/) from your Samsung Galaxy Note 3 as a complete wipe will be required during the flashing process.
Enable USB debugging option on your device: Settings > Development Options > USB debugging.
Samsung Galaxy Note 3 N900T must be rooted (http://wccftech.com/root-galaxy-note-3-n9005-on-xxuend6-android-4-4-2/), unlocked and installed with a recovery tool like TWRP or CWM.
Your device must be charged to at least 60% of power.

Steps to update Note 3 N900T to Android 5.1.1 AICP ROM: Required files: download AICP Android 5.1.1 (http://mirror3.aicp-rom.com/hltetmo/NIGHTLY/aicp_hltetmo_lp-9.0-NIGHTLY-20150602.zip) for T-Mobile Galaxy Note 3 N900T and save it on your computer. Do not extract the contents. Also download the Google Apps Package for your Note 3 from here (http://wccftech.com/download-latest-google-apps-android-1/).


Connect Galaxy (http://wccftech.com/unfreeze-android-smartphone-tips/) Note 3 N900T to your computer using a USB cable and copy the zip file to your phone’s SD card.
Disconnect the USB cord and power off your Samsung Galaxy (http://wccftech.com/fix-galaxy-s6-battery-issues/) Note 3.



Boot it into recovery mode by pressing and holding Volume Up + Home + Power buttons together.



Wipe data task: from CWM recovery menu, select wipe data / factory reset and confirm the process. Then go on to wipe cache partition and wipe dalvik cache.



From recovery menu, select install zip from sdcard followed by choose zip from sdcard. Locate the AICP Android 5.1.1 custom firmware (http://wccftech.com/android-lollipop-custom-roms/) and confirm the flashing process.
Once done, repeat the above step for installing Gapps on your smartphone.



After installation is done successfully, return back to main recovery menu and reboot your Note 3 N900T into the new custom ROM. First boot takes a good 5 minutes so please be patient.

– Recommended: Fix “Root Access Possibly Lost” and “Root access missing” Error Messages on Android (http://wccftech.com/fix-missing-or-lost-root-access/)







Noticia:
http://wccftech.com/update-note-3-n900t-to-android-5-1-1-aicp/#ixzz3cCFE7kOh

[Jorge-Vieira]

Sony’s Android 5.1 Rollout Strategy Still Leaves Many Devices Behind


Sony (http://hothardware.com/tags/sony) on Thursday confirmed that it's about to begin rolling out Google's (http://hothardware.com/tags/google) incremental Android 5.1 update to each of its Xperia devices that were previously upgraded to Android 5.0 (Lollipop (http://hothardware.com/tags/lollipop)). That's good news to owners of the more than half a dozen handsets and tablets that will see the update, though it's also a veiled way of leaving many other devices behind.

We'll start with the good. Devices that will see an update to Android 5.1 include the Xperia Z, Xperia Z1, Xperia Z2, Xperia Z3, Xperia ZL, Xperia ZR, Xperia Tablet Z, Xperia T2 Ultra, and Xperia C3. In addition, Sony says it will bump up the Xperia M2 and Xperia M2 Aqua direction to Android 5.1, which will roll out "a little after we've made the update available for the Xperia Z Series."


image: http://hothardware.com/ContentImages/NewsItem/33923/content/Xperia_ZR.jpg
http://hothardware.com/ContentImages/NewsItem/33923/content/Xperia_ZR.jpg


Sony claims it's "seen a fevered raft of feedback and requests for us to extend our Android Lollipop rollout to other products in the portfolio," and it's at that point the company mentions adding the Xperia M2 and Xperia M2 Aqua to the mix, in due time. What that also suggests is that all other devices in Sony's portfolio are stuck with whichever Android version they currently have.

That shouldn't be all that shocking if you've been paying attention to Sony's past comments. Back in March, the company said that its Xperia Z line would be the only devices see an update to Lollipop. Obviously those plans have changed somewhat with the addition of the Xperia M2 and Xperia M2 Aqua, but there's nothing to suggest that any more devices will be added to the list.




Noticia:
http://hothardware.com/news/sonys-android-51-rollout-strategy-leaves-many-devices-behind#MM82YjwyJt0BK7EQ.99

[Jorge-Vieira]

Paranoid Android 5.1.1 Lollipop Now Available for Sony Xperia Z2 – How to

Sony will seed out Android 5.1.1 Lollipop for Sony Xperia Z2 (http://wccftech.com/cm12-1-nightly-android-5-1-1-for-xperia-z2/) officially sometime before August. However, you don’t need to wait that long as your favorite custom ROM has just been made available for Xperia Z2. Paranoid Android 5.1.1 Lollipop is now available for the smartphone. O3 optimized, packed full of tweak, stable and smooth – here is how to flash Paranoid Android 5.1.1 on Z2.
http://cdn4.wccftech.com/wp-content/uploads/2014/02/Xperia-Z2-3.jpg (http://cdn4.wccftech.com/wp-content/uploads/2014/02/Xperia-Z2-3.jpg)
– Also, read: Galaxy S6 edge Tips to Help You Take the Best Out of Your Curved Phone (http://wccftech.com/galaxy-s6-edge-tips/)




Prerequisites to flash Paranoid Android 5.1.1 on Xperia Z2:

Backup any important data (http://wccftech.com/how-to-backup-sms/) from your Sony Xperia Z2 as a complete wipe will be required during the flashing process.
Make sure ADB and Fastboot is configured on your PC.
Sony Xperia (http://wccftech.com/lg-g4-xperia-z4-gpu-benchmark-rumor-roundup/) Z2 must be rooted with unlocked bootloader and installed with a recovery tool.
Your device must be charged to at least 60% of power.

Flash Paranoid Android 5.1.1 on Xperia Z2: Required files: download Paranoid Android 5.1.1 (http://www.infectedbuilds.net/downloads/sirius/aospa_lp/pa_sirius-5.1-20150614.zip) Lollipop custom firmware for Xperia Z2 and save it on your computer. Extract boot.img file separately.


Connect your Xperia (http://wccftech.com/update-xperia-z2-to-android-5-1/) to your computer using a USB cable and copy the zip file to your phone memory’s root folder.
Copy the boot.img file to android-sdk-windows\platform-tools directory.
Switch off your Xperia (http://wccftech.com/xperia-z4-leaked-image-press-photo/) Z2 and enter Bootloader mode: press and hold the Volume Up button while connecting the phone with USB cable. Phone LED will turn blue indicating the Bootloader mode.
Once in the Fastboot mode, on your PC navigate to android-sdk-windows\platform-tools directory and open Command Prompt with Shift + Right-click > Open Command Prompt.
Type the following command and press Enter:

fastboot flash boot boot.img


Type the command and press Enter:

fastboot reboot


Enter in the Recovery Mode: switch on the phone while pressing the Volume Up button a few times.
Wipe data task: from CWM recovery menu, select wipe data / factory reset and confirm the process.
Also clean cache from wipe cache partition.
From recovery menu, select install zip from sdcard followed by choose zip from sdcard. Locate the Paranoid Android 5.1.1 Lollipop (http://wccftech.com/android-5-1-1-lollipop-to-fix-memory-leak-issue/) custom firmware and confirm the flashing process.
Once done, return back to main recovery menu and reboot your into the new custom ROM.
First boot takes a good 5 minutes so please be patient.

Don’t forget to let us know if you liked the Android 5.1.1 based Paranoid Android custom firmware for Sony Xperia Z2.







Noticia:
http://wccftech.com/paranoid-android-5-1-1-for-xperia-z2/#ixzz3dVqqZOwb

[Jorge-Vieira]

Smooth and Fast Custom ROM Based on Android 5.1.1 for Galaxy S3 – How to

Android 5.1.1 Lollipop custom ROMs list is getting quite extensive. With more ROMs (http://wccftech.com/update-note-4-n910f-to-android-5-1-1-aicp/), we get the option of choosing only the stable and fast custom ROMavailable for our devices. Here is another of the popular and stable custom ROM based on Android 5.1.1 for Galaxy S3 i9300. crDroid is specifically popular for customization options that it offers you. Don’t forget to check our list of reader-favorite Lollipop custom ROMs (http://wccftech.com/android-lollipop-custom-roms/) for Samsung, HTC, Sony, LG and Nexus devices.
http://cdn.wccftech.com/wp-content/uploads/2013/02/carbon-rom-for-galaxy-s31-635x380.jpg (http://cdn.wccftech.com/wp-content/uploads/2013/02/carbon-rom-for-galaxy-s31.jpg)

crDroid Android 5.1.1 features: Volume panel timeout
Clear recents location
Heads up customization
Quick access button on expanded status bar
Swipe behavior
Touch outside behavior
Time out
Do not disturb
Blacklist
SlimRoms custom lockscreen shortcuts
Navbar on/off
Hardare keys on/off (in devices supported)
Power menu in navring targets
SlimPie controls with all working
Sound panel option om power menu
Superuser indicator (Notification, Statusbar icon or no indicator)
Force expanded notifications on expanded statusbar
Power menu and notifications tiles
Four tiles per row
Vibrate on tiles touch
Disable quick settings on secure lockscreen
Kill app back button configurable timeout
Ambient display as active display from OmniRom (http://wccftech.com/update-galaxy-s2-i9100-to-android-5-1/)





Prerequisites to flash Android 5.1.1 for Galaxy S3:

Create a backup (http://wccftech.com/how-to-backup-sms/) of all important data in your Galaxy device.

Download and install USB drivers for Samsung Galaxy S3 (http://wccftech.com/download-android-usb-drivers/)in your computer.
Enable USB debugging option by pressing Menu > Settings > Applications. Navigate and tap on Developer Options to ensure that USB Debugging is enabled.
Make sure that recovery tool like ClockworkMod recovery (http://wccftech.com/root-install-cwm-recovery-on-galaxy-s3-sch-i535-android-411-412/) is installed.
Ensure that your Samsung Galaxy S3 i9300 carries more than 80% of charge.

Flash Android 5.1.1 for Galaxy S3: Files required: download crDroid Android 5.1.1 Lollipopcustom ROM (https://www.androidfilehost.com/?fid=24052804347764054); also download the Google Apps (http://wccftech.com/download-latest-google-apps-android-1/). Save both files on PC.
Here are the steps to update Galaxy S3 i9300 (http://wccftech.com/update-galaxy-s3-to-lollipop-android-5-1-1/) to Android 5.1.1 based custom ROM:


Connect your Samsung Galaxy S3 I9300 to your computer using USB cable and copy the downloaded files to the SD card of your Galaxy device.
Disconnect the connection with PC and turn your Galaxy S3 off.
Boot in to custom recovery mode: press and hold Volume Up, Down and the Power buttons simultaneously until Samsung (http://wccftech.com/update-galaxy-s3-to-lollipop-android-5-1-1/) logo shows up. Leave the keys for half a second and hold again. Use Volume keys to scroll and Power button to select – alternatively you can use Quick Boot app (https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot) to reboot your Android device in recovery mode.
Now perform Nandroid backup of your current ROM: select Backup and Restore > Backup. Go back to main recovery menu after backup process is done – very important step to restore back to current OS.
Data wiping tasks: select wipe data/factory reset > Yes. It will take a few minutes; once done, select wipe cache partition. Next tap on Advance > wipe Dalvik Cache to wipe Dalvik cache data too.
Select install zip from sdcard followed by choose zip from sdcard. Locate the Android 5.1.1 based custom ROM file copied earlier and select it. Tap on yes to confirm installation and wait for the ROM installation to be completed.
Once installation process is finished successfully, repeat the above step but choose GApps file instead to install the Google apps package on your SGS3 I9300.
Return to main recovery menu now and select reboot system now to boot up into the latest Android 5.1.1 Lollipop custom firmware for Samsung Galaxy S3 (http://wccftech.com/update-galaxy-s3-i9300-to-android-5-1-1-custom-rom/). It will take a bit of time during the first boot, so kindly be patient.
Ta da! Enjoy Lollipop on Galaxy S3.

How to restore: If you want to return to previous OS on your SGS3, boot into recovery, select backup and restore then restore your previous ROM by selecting it from the list.







Noticia:
http://wccftech.com/android-5-1-1-for-galaxy-s3-custom-rom/#ixzz3eIMkgbWS

[Jorge-Vieira]

Fix Android 5.1.1 Battery Drain Issues – Android Tips

Android 5.1.1 Lollipop has just been with us for a few weeks and interwebs are already full of battery drain complaints. Battery issues are perhaps one of the most annoying problems as our latest smartphones (http://wccftech.com/android-lollipop-custom-roms/) aren’t really good at lasting for longer anyway. Add in these software bugs and you are left with a device that hardly even makes to a few hours, let along a full day.
http://cdn2.wccftech.com/wp-content/uploads/2015/06/Samsung-Galaxy-S6-635x421.jpg (http://cdn2.wccftech.com/wp-content/uploads/2015/06/Samsung-Galaxy-S6.jpg)
Considering this, we are compiling this list of Android 5.1.1 (http://wccftech.com/update-t-mobile-galaxy-s4-to-android-5-1-1/) battery fixes that you could try on your devices to get at least some relief. We are sure that by mixing one or two of these tips, you will see that your device lasts a little longer. In any case, you can always downgrade (http://wccftech.com/guide-to-downgrade-firmware-on-samsung-galaxy-devices/) at the end of the day – no? Don’t forget to share with us what tips worked for you and of course, your own tried and tested tips to help other readers.
Restart your device: You must be thinking what’s she talking about! But well, restarting fixes a lot of problems in a matter of seconds. Try it and try it often. Turn off your Android device (http://wccftech.com/android-5-1-1-for-galaxy-s3-custom-rom/) completely to help it get rid of all that heavy cache. Restarting can solve a long list of regular issues that we confront with our gadgets so make it a habit to restart your devices often.
See if some apps are being finicky with Android 5.1.1 battery: If restarting doesn’t fix Android 5.1.1 battery issues, you might want to consider checking out which of the apps that you are using on your Android phone are creating the problem. Often times, battery issues don’t arise because of your OS version but because how a particular app starts behaving roughly after an update. It’s always good to keep a check on what’s not working properly so you can reinstall those apps. From your Android 5.1.1 (http://wccftech.com/best-android-5-1-1-custom-rom-for-nexus-4/) device Settings, you can take a look at your applications and notice if there are any abnormalities in their usage patterns. If so, uninstall the problematic app(s) and reinstall back to see if Android 5.1.1 battery problems are fixed.
In case you can’t really point a finger at which app is causing issues, you can also boot your Android device into Safe Mode to check. To boot Galaxy into Safe Mode:


Power off your phone.
Press & hold power and volume down key.
When it boots up, let go of the power key keeping the volume down key pressed.
You will notice a Safe Mode text when you are in the mode.

Fix Android 5.1.1 battery with default software options: All the latest devices come with software features supporting power saving modes. Samsung’s ultra power saving mode is already quite popular in users because it really works! From Settings go to System > Battery and you will spot two default battery saving options: Power saving and Ultra power saving modes.
http://cdn.wccftech.com/wp-content/uploads/2015/04/Galaxy-S6-2.jpg (http://cdn.wccftech.com/wp-content/uploads/2015/04/Galaxy-S6-2.jpg)
These default features don’t affect your normal usage as they simply restrict background refresh and limit battery usage by slowing down processor. Yes, screen brightness would be a notch down but you will find a major boost in your battery’s life. You can use the second, Ultra power saving mode during those critical times when you need to save every drop of the juice to make it run just a little longer.





Turn off communications and other unnecessary services: This is of course not a fix but will help you save those last drops of battery when in need. Go to Settings and turn off connectivity options like Wi-Fi, Bluetooth, NFC, GPS, or even cellular data? Okay, don’t kill me but I am only recommending you to try it when in dire needs of saving battery.
Disable location services: Much like the above, location services also take a little of battery so keep these settings off too. You should always be careful about privacy (http://wccftech.com/fbi-hates-google-and-apple-for-encryption/) issues that location option creates for you so it’s good in any way. When an app or maps need location permission to perform their functions, go to Settings and enable them.
Battery charge cycle: It is recommended to let your device go through at least one charge cycle a month: i.e. charging the battery to 100% and then completely using it down to around 5%. Power cycling this way helps in getting accurate battery usage data and is good for your battery maintenance too.
Use a black wallpaper: Live wallpapers are never good for your smartphone (http://wccftech.com/root-g925fxxu2bofj-android-5-1-1-galaxy-s6-edge/)‘s battery life so stop using them if you want your battery to last longer. Choose a black wallpaper on your AMOLED display smartphones to save battery. Samsung’s devices don’t come with a default black paper but you can easily create one or find it online. On a Galaxy S6, go to Settings > Personal > Wallpaper > From Gallery, choose a black wallpaper. Thanks to how Samsung’s AMOLED screen consumes power, you will notice some difference in battery life after switching to a black paper.
<section> Make Android 5.1.1 battery run longer by disabling notifications: Receiving notifications for every single app is not only annoying but also eats up resources of both data, battery and the processing speed. Make efficient use of notifications and disable them for apps you don’t need notifications for.
Replace stock launchers: Some launchers in the Google Play Store (http://wccftech.com/google-play-store-2015-updates/) are popular for their skills of saving battery. Try Nova launcher instead of the default options to make your battery stick with you a little more.
Factory reset (sigh!): As always, it comes down to this! If absolutely nothing else works, factory reset your Android 5.1.1 (http://wccftech.com/android-5-1-1-for-nexus-5/) powered device to fix the issues. You can find reset options in your device’s Settings menu.
Bonus! You can also consider downgrading your software if Android 5.1.1 battery is really not working with you. Downgrading is not an easy process but would get you out of the mess that your smartphone is throwing at you. Also, consider extra battery for the devices that let you replace it or battery juice packs for those which don’t.
– For Nexus users, here’s how to fix battery, heating and performance issues (http://wccftech.com/fix-nexus-6-battery-heating-performance/) </section>






Noticia:
http://wccftech.com/fix-android-5-1-1-battery-issues/#ixzz3eIZ5SO1y (http://wccftech.com/fix-android-5-1-1-battery-issues/#ixzz3eIZ5SO1y)

[Jorge-Vieira]

Dear Google, Critical Android 5.x Battery Drain Bug is NOT a “Small” Priority

We already shared with you that Android Lollipop (http://wccftech.com/android-lollipop-custom-roms/) is facing some serious battery drain issues and how to try tackling these (http://wccftech.com/fix-android-5-1-1-battery-issues/). While the operating system’s latest iteration Android 5.1.1 was expected to bring in some fixes for the issue, it hasn’t been so.
– Recommended: Android 5.1.1 Battery Drain Fixes (http://wccftech.com/fix-android-5-1-1-battery-issues/) http://cdn.wccftech.com/wp-content/uploads/2015/07/Calibrating-Battery-635x210.jpg (http://cdn4.wccftech.com/wp-content/uploads/2015/07/Calibrating-Battery.jpg)
According to various media and user reports (https://code.google.com/p/android/issues/detail?id=165558), after upgrading to Android 5.x, users face various battery related issues including losing a big chunk of it over a period when user isn’t even using the Android device (http://wccftech.com/root-g920fxxu2bofl-android-5-1-1/). Android has never really been good with using resources intelligently and has always suffered with battery problems. However, Android 5.x battery drainage has taken the usual issue to another level.
While we are not sure when will this annoying Android 5.x battery bug be solved, we have shared with you some tips and fixes (http://wccftech.com/fix-android-5-1-1-battery-issues/) that may help in solving the issues of Android battery drain. Remember, that next iteration of Android is also expected to bring a fix to the memory leak issue (http://wccftech.com/android-5-1-1-lollipop-to-fix-memory-leak-issue/). Android 5.1.1 was also expected to fix this issue as well, however, it didn’t bring any consolation to the users with quite a many experiencing the issue.
Android 5.x battery bug reports: The battery bug is not only present in Android 5.x but also experienced by the users on the latest Android M developer preview (http://wccftech.com/how-to-root-nexus-5-on-android-m/) making it a very constant bug in Android iterations. Here are some reported Android 5.x battery issues over at issue tracker. As you can see all of the devices including latest flagships like Samsung Galaxy S6, Nexus devices, HTC, Motorola, Sony, and Chinese makes are also facing this problem.
– When mobile data (2G or 3G) is switched on, all the internet apps continue to consume battery and keep the mobile data active unless they are force stopped. On kitkat, this didn’t happen because apps stopped using mobile data whenever their transaction was over. But here in lollipop, they don’t seem to stop ever and cause a huge battery drain.
– Same bug for me. OnePlus One 5.0.2/5.1/5.1.1
– Cell in standby for me is the major cause of the battery drain on my Nexus 6 (http://wccftech.com/fix-nexus-6-battery-heating-performance/). This issue there was with Android 5.0 and is still here with 5.1.0.
– Nexus 4,android 5.1 LMY47O Massive battery drain by mobile radio active.






– Same issue galaxy s6 5.0.2
– HTC One M7 with Android 5.0.2. But with no Mobile Data active. Just normal GSM + Wifi.
– Samsung Galaxy S4 only 4h Battery lifetime
– Galaxy S4 on 100% battery KK 4.4.4 – 2% battery drain after 8 hrs while in sleep mode Galaxy S6 on 100% battery LP 5.1.1 – 6% battery drain after 8 hrs while in sleep mode
User are also pretty annoyed with how Google is handling this issue as “small” priority.
– This issue is one of the most voted android issues with almost 2000 stars now (fourth most starred open issue), and still google hasn’t acknowledged it yet, and seemingly hasn’t done anything to resolve it. AND THE PRIORITY IS SMALL !!!! WTF!!!?? OMG!!!???
– This is no longer small, looking at the number of affected users. WAKE UP GOOGLE! Not fixing this quickly, means lost of users.
It is not certain why Google isn’t taking this issue seriously, possibly because the Lollipop adoption rate is slow? Some suggest, this is one of the reasons why users aren’t quick at adopting latest Android builds. While Google focuses on bringing out Android M (http://wccftech.com/download-android-m-wallpapers-apps-apk-files-for-your-devices/), users will have nothing but to downgrade to earlier versions (http://wccftech.com/best-android-4-4-custom-roms/).







Noticia:
http://wccftech.com/android-5-x-battery-bug/#ixzz3eles8gBM

[Jorge-Vieira]

New Android Malware Discovered Every 18 Seconds

http://cdn.eteknix.com/wp-content/uploads/2015/04/malware-800x436.jpg
The G DATA’s Q1 2015 Mobile Malware Report (https://public.gdatasoftware.com/Presse/Publikationen/Malware_Reports/G_DATA_MobileMWR_Q1_2015_US.pdf) has revealed an alarming statistic which suggests a new piece of malware is released on the Android platform every 18 seconds. This staggering figure becomes even more disturbing when you consider the current Android market share exceeded 61%. Android mobiles and tablets have become extraordinarily popular mainly due to their affordable price point and intuitive touch interface. Unfortunately, those who aren’t technologically minded are quite susceptible to malware and phising scams. The findings from the report clearly show the increased activities of cybercriminals who feel the mobile market is their new target area.

“G DATA security experts identified and analysed 440,267 new malware samples in the first quarter of 2015. This represents an increase of 6.4 percent compared to the fourth quarter of 2014 (413,871). The number of malware strains rose by 21 percent compared to the first quarter of 2014 (363,153).”
Interestingly, the amount of financial malware equated to 50.3% and this could become a serious threat considering 50% of US customers, and 40% of EU smartphone owners use their phone to do online banking. Mobile devices are set to revolutionize the way we pay for products and can even transfer money on the go. However, if this trend continues, it won’t be long until consumers feel very unwilling to trust mobile banking apps. For example, the number of new malware programs rose by a colossal 21% compared to the first quarter of 2014.
It’s also difficult to clearly define what malware is on mobile operating systems. Free-to-play games are littered with adverts and some can direct you to suspicious websites. Even if they only direct you to another product, is that a form of unwanted marketing malware? Whatever the case, it seems like the success of Android has resulted in a larger scale of attacks.
Let us know if you use mobile banking and what do you make of these latest findings?
Thank you ITBusinessEdge (http://www.itbusinessedge.com/blogs/data-security/new-android-malware-found-every-18-seconds.html?google_editors_picks=true) for providing us with this information



Noticia:
http://www.eteknix.com/new-android-malware-discovered-every-18-seconds/

[f0N5]

Saiu o Lolipop para o E5 a semana passada.

Instalei e ate agora impecável.. fluido, bonito e pratico.

Tenho que o comparar com o moto g 5' que veio para ca esta semana tambem para ver se realmente compensa o facto de ser android "puro" :thumbsup:

[Viriat0]

Saiu o Lolipop para o E5 a semana passada.

Instalei e ate agora impecável.. fluido, bonito e pratico.

Tenho que o comparar com o moto g 5' que veio para ca esta semana tambem para ver se realmente compensa o facto de ser android "puro" :thumbsup:

Elahh tenho que actualizar o E5 aqui de casa.

Fon5 seu bêbado estás porreiro?

Abraço

[f0N5]

Esta tudo tranquilo :D

Eu tive que fazer 2 updates, um para preparação do download e outro do sistema operativo em si :)

[Sardo]

Ainda estou a saber é como é que o pessoal apanha estas coisa, têm de entrar no telemóvel como ficheiro .apk ou a simples visita a um site pode contaminar?

[Jorge-Vieira]

Customized Android Firmware Creates More Security Vulnerabilities, Researchers Find

Researchers Xiaoyong Zhou, Yeonjoon Lee, Nan Zhang, Muhammad Naveedy and XiaoFeng Wang discovered (http://www.cs.indiana.edu/%7Ezhou/files/sp14_zhou.pdf) vulnerabilities in customized Android firmware created by various device makers. The discovery shows that many OEMs create numerous vulnerabilities in Android software as they try to add new features or change core functionality of the Google-developed "stock" Android. The researchers mainly focused on vulnerabilities found in customized device drivers by using a tool of their own creation called "ADDICTED." The tool works in the following manner:

“ADDICTED performs dynamic analysis to correlate the operations on a security-sensitive device to its related Linux files, and then determines whether those files are under-protected on the Linux layer by comparing them with their counterparts on an official Android OS. In this way, we can detect a set of likely security flaws on the phone," said the researchers in their published abstract.
The researchers used the tool on three popular phones from Samsung and found that they could use the discovered vulnerabilities to take unauthorized pictures and screenshots, and even record the typed keys on the virtual keyboards.
Some of the flaws were found to exist on over 100 smartphone models and affected millions of users. The researchers also verified the security settings of device files on 2,423 factory images, and more than 1,000 of them were vulnerable. They reported the vulnerabilities to the affected companies before publishing their paper.
Another group of researchers also working on analyzing various Android firmware customizations share the previous group's findings, that customizations increase the attack surface and make the devices more vulnerable. (https://dl.acm.org/citation.cfm?id=2766519)

“By using different indicators and techniques, we showed that attack surface and information permeability are consistently worse on customized devices, as the addition of customization packages increases both the number of protected resources and the number of packages accessing those resources, violating both the 'least privileges' and the 'minimal trusted computing base' paradigms. At the very least, it increases misuse and creates a more complex environment which can mask problems and is more difficult to analyse," concluded the paper.
Many OEMs try to add as many features as possible on top of stock Android in order to differentiate from each other. Sometimes those features might not be implemented with security in mind, which could then make the devices more vulnerable to attacks and malware.
The device makers also often pre-install multiple third party apps (sometimes called "bloatware") on their phones, which can raise the level of risk for these devices.
If OEMs are going to customize Android smartphones to such a high degree, then they should at least consider the security implications for each new feature or app that they are adding to the devices they are selling for hundreds of dollars to their customers.



Noticia:
http://www.tomshardware.com/news/customized-android-firmware-security-vulnerabilities,29631.html

[Sardo]

É por essas e por outras que nada bate o Vanilla com um launcher em cima

[RCS_007]

:thumbsup:
Indeed Sardo, assim como a fluidez de um stock android.
Próximo telemóvel será em principio um Nexus 5 (2015).
Se eu digo que o meu G2 com a rom stock já é bem fluida imagino com um Nexus.
Damn nunca mais é Outubro.

[Jorge-Vieira]

Sony Rolling Out Android 5.1 To Xperia Z2 And Z3 Series, Others Will Soon Follow

http://media.bestofmicro.com/E/R/480051/gallery/android-lollipops_w_600.jpg (http://www.tomshardware.com/gallery/android-lollipops,0101-480051-0-2-12-1-jpg-.html)Sony has begun sending out the Android 5.1 Lollipop upgrade to the following devices: Xperia Z3, Xperia Z3 Compact, Xperia Z3 Tablet Compact, Xperia Z2 and Xperia Z2 Tablet. Along with all the Android 5.1 stock features, Sony has also added some enterprise features for business users.
Not all of these device owners will receive the update at the same time, as it will be a staggered rollout depending on each market. Sony has already updated some of these to Android 5.0 (http://www.tomshardware.com/news/xperia-z3-lollipop-upgrade-rollout,28845.html), so the Android 5.1 version won't bring too many new features for those devices, but it should be a major upgrade for the rest (from Android 4.4).
Sony has also added its own tweaks and improvements to the new upgrade:



Increased customization options – so you have even more control over the way volume, silent modes and your alerts function
Brand new LinkedIn integration – be more productive with intuitive contact synchronization in your Calendar
Camera improvements – with faster, more accurate Superior Auto Mode focus for great images, regardless of conditions
Enhanced enterprise support – with our latest Xperia in Business features for work
SmartWear integration – selfie snapping made that bit easier, with SmartWatch 3 as a remote shutter button

The enterprise support includes improved security measures; Sony's "advanced" Xperia Email, Calendar and Contacts apps; better LinkedIn integration; and bundled IT support.
The devices mentioned above won't be the only ones to get Android 5.1. A few others, such as the Xperia Z1, Xperia Z1 Compact and Xperia Z Ultra will also get the update shortly. Then, the Xperia T2 Ultra, Xperia C3, the original Xperia Z Series, and the Xperia M2 and Xperia M2 Aqua will get the Android 5.1 upgrade, as well.
Sony hasn't announced any major updates for its small budget E-series devices so far. This likely means that the Xperia E3, Xperia E4 and Xperia E4g, all of which came with Android 4.4 on board, could be stuck with their original firmware.

<iframe width="550" height="310" src="https://www.youtube.com/embed/o5I0PEUfqas" frameborder="0" allowfullscreen></iframe>

Xperia in Business





Noticia:
http://www.tomshardware.com/news/sony-android-5.1-upgrade-rollout,29648.html

[Jorge-Vieira]

Android 5.1.1 Custom ROM for Samsung Galaxy S5 – How to

You can now update your Samsung Galaxy S5 to the very latest Android 5.1.1 Lollipop based custom ROM (http://wccftech.com/tag/android-5-1-1-custom-roms). Maverick Android 5.1.1 is bloatware-free and ensures that you get faster performance from your flagship device. Stable and smooth, here is how to update Galaxy S5 G900T to Android 5.1.1 based Maverick custom firmware.
http://cdn.wccftech.com/wp-content/uploads/2014/02/galaxys5-2040-8_verge_super_wide-1-635x422.jpg (http://cdn.wccftech.com/wp-content/uploads/2014/02/galaxys5-2040-8_verge_super_wide-1.jpg)


Maverick Android 5.1.1 features:

Viper4andriod
Lspeed
Init.d tweaks
Prerooted no action
Using the sickness old root method rip to his work
Has Volte
Write to sd card
Call recording
App Ops
Kernel editor

Prerequisites to update Galaxy S5 G900T to Android 5.1.1 ROM:

Download and install USB drivers for Samsung Galaxy S5 G900T (http://wccftech.com/root-samsung-galaxy-s5-android-tips/).
Enable USB debugging mode from developer menu.
You should have a custom recovery tool (http://wccftech.com/galaxy-s5-recovery-mode-how-to/) like TWRP or CWM installed on your device
Backup any important data before going forward for the tutorial.
Ensure that your Samsung Galaxy S5 G900T carries more than 70% of charge.

Download Files

Download Maverick Android 5.1.1 (https://mega.nz/#%21dwNWlCIb%21-vJTjwxdRzaSEdiDtjXX_toqoBOZKAr0MgLb341mvaU)
Download Google Apps (GApps) (http://wccftech.com/download-latest-google-apps-android-1/)

How to update Galaxy S5 G900T to Android 5.1.1 Maverick:

Connect your Galaxy S5 to your computer and copy / paste the downloaded zip files to the SD root folder of your phone.
Disconnect and reboot your SGS5 into Recovery mode (http://wccftech.com/galaxy-s5-recovery-mode-how-to/): press and hold down the Volume Up button, alongside Home and the Power button, until the screen flashes. Release the three buttons then. After a few seconds of that, your phone will enter recovery mode.
Once in the recovery mode, select wipe data/factory reset > Yes to confirm your action. Wait for a few minutes until the phone wipes your data. Once done, go back to recovery menu and Wipe Cache Partition and then Wipe Dalvik Cache as well.
Select install zip from sdcard > choose zip from SD card. Locate the custom ROM file copied earlier by pressing the Power key. Once confirmed, the ROM installation will begin.
Repeat the above step by choose GApps file instead of the ROM file.
When GApps get installed, go back to the main recovery menu and select reboot system now to reboot the phone.
That’s it.

Enjoy Android 5.1.1 on your T-Mobile Samsung Galaxy S5 G900T.







Noticia:
http://wccftech.com/update-galaxy-s5-g900t-to-android-5-1-1/#ixzz3gvMxt992

[Jorge-Vieira]

Vicious Texting Exploit Turns 95% Of Android Devices Into Leak-Happy Zombies

Is your phone recording your voice right now? If you have an Android smartphone, you shouldn’t be so sure that it isn’t, given a discovery by a researcher from mobile security firm Zimperium (http://www.zimperium.com). The San Francisco-based company claims to have uncovered a method for attacking phones, known as Stagefright, which gives a hacker complete access to a smartphone running Google’s operating system – all without the user knowing. There hasn't been any indication that malicious parties have attempted to use the attack... yet.

The seriousness of the threat lies in the way it infiltrates your phone, according to Zimperium researcher Joshua Drake. The attacker hides the malware in a video and texts it to your phone. Look at the text, and your phone is potentially open to the hacker. According to Drake, you don’t even need to watch the video to trigger the malware; viewing the text could be all it takes to turn your phone into a zombie.


http://hothardware.com/ContentImages/NewsItem/34498/content/Android-malware.jpg


And that’s assuming that your phone is using a default messaging app. If your mobile phone is running Google’s Hangouts (http://hothardware.com/tags/hangouts) app, Drake asserts, you wouldn’t need to view the text for the malware to access your phone. That’s because the app will automatically process the video when it arrives. If the attacker has your phone number and your phone is one of the 95 percent of Android devices that are vulnerable to the attack (as estimate by Zimperium), your phone could become compromised.

Google (http://hothardware.com/tags/google) is aware of the situation and has already worked with Zimperium to get patches out to device makers and carriers, but here’s where patching the phones gets tricky. It’s up to them (and not Google) to implement the patches, which means patching your phone is out of Google’s control. If your carrier or device maker takes the threat seriously, your phone may already be patched or could be patched soon.

As scary as Stagefright sounds, the outgoing patches should resolve the problem. And, as Google points out, Android is already designed with certain protections for user data. If you haven’t already, make sure you phone’s software is up to date.

Noticia:
http://hothardware.com/news/vicious-texting-exploit-turns-95-of-android-devices-into-leak-happy-zombies

[Jorge-Vieira]

Vulnerability That Renders Android Devices Silent Discovered (http://www.hardocp.com/news/2015/07/29/vulnerability_that_renders_android_devices_silent_ discovered/)

We have discovered a vulnerability in Android that can render a phone apparently dead – silent, unable to make calls, with a lifeless screen. This vulnerability is present from Android 4.3 (Jelly Bean) up to the current version, Android 5.1.1 (Lollipop). Combined, these versions account for more than half of Android devices in use today. No patch has been issued in the Android Open Source Project (AOSP) code by the Android Engineering Team to fix this vulnerability since we reported it in late May.

Noticia:
http://www.hardocp.com/news/2015/07/29/vulnerability_that_renders_android_devices_silent_ discovered#.VboCavn0OTQ

[Jorge-Vieira]

Google Patches Android Stagefright MMS Exploit, Ships Update To Carriers

Earlier this week, we learned of a scary (http://hothardware.com/news/vicious-texting-exploit-turns-95-of-android-devices-into-leak-happy-zombies) piece of malware (http://hothardware.com/tags/malware) that can strike almost all Android (http://hothardware.com/tags/android) devices in use. As has become a theme of late, the exploit is trigged via a simple text message. While it's easy to assume that you'll be safe simply by not reading any unsolicited text messages from people you don't know, this bug can be effective enough to not even require you to open it.
If the attack is successful, the phone can be remotely accessed in full. That even includes being able to trigger the camera (http://hothardware.com/tags/camera) and microphone. Suffice to say, this is a serious bug, and while there's been no proof of it happening in the wild yet, it clearly needs to be patched as soon as possible.

http://hothardware.com/ContentImages/NewsItem/34544/content/Android_Army.jpg Given the severity of the bug, Google hasn't wasted time on coming up with a fix. Soon, Nexus users will be prompted to install the update, and carriers have also been given a copy. For those running non-official builds of Android or outdated ones, a patch is going to be soon released to the open source community.
With as many text message-related bugs to creep up (http://hothardware.com/news/a-little-text-string-can-now-take-out-iphone-messages) over this past year, it's clear that further protections have to be put into place. It's really quite bizarre to be able to gain entry to an entire device simply by sending a corrupt text message; years ago, some people might have thought you were crazy if you said such a thing were possible.



Noticia:
http://hothardware.com/news/google-patches-android-stagefright-mms-exploit-ships-update-to-carriers

[Jorge-Vieira]

How to Flash Stock Rooted Android 5.1.1 Custom ROM on Galaxy S5

Looking for rooted stock firmware for your Samsung Galaxy S5 (http://wccftech.com/samsung-galaxy-s6-vs-galaxy-s5/)? Follow this post to flash Android 5.1.1 Stock Rooted custom ROM on your Galaxy S5 G900T. This a pre-rooted firmware giving you stock experience on your S5. Stable and smooth, here is how to flash Stock Rooted Galaxy S5 custom ROM based on Android 5.1.1 Lollipop (http://wccftech.com/tag/android-5-1-1-custom-roms).
http://cdn.wccftech.com/wp-content/uploads/2015/07/section_0_product-635x334.png (http://cdn.wccftech.com/wp-content/uploads/2015/07/section_0_product.png)




Stock Rooted Android 5.1.1 features:

Android 5.1.1 Lollipop
Stock Samsung Firmware
Pre-Rooted

Prerequisites to update Galaxy S5 G900T to Android 5.1.1 ROM:

Download and install USB drivers for Samsung Galaxy S5 G900T (http://wccftech.com/root-samsung-galaxy-s5-android-tips/).
Enable USB debugging mode from developer menu.
You should have a custom recovery tool (http://wccftech.com/galaxy-s5-recovery-mode-how-to/) like TWRP or CWM installed on your device
Backup any important data before going forward for the tutorial.
Ensure that your Samsung Galaxy S5 G900T carries more than 70% of charge.

Download Files

Download Android 5.1.1 Stock Rooted custom ROM (https://www.androidfilehost.com/?fid=24052804347777315)
Download Google Apps (GApps) (http://wccftech.com/download-latest-google-apps-android-1/)

How to flash Galaxy S5 custom ROM based on Android 5.1.1:

Connect your Galaxy S5 to your computer and copy / paste the downloaded zip files to the SD root folder of your phone.
Disconnect and reboot your SGS5 into Recovery mode (http://wccftech.com/galaxy-s5-recovery-mode-how-to/): press and hold down the Volume Up button, alongside Home and the Power button, until the screen flashes. Release the three buttons then. After a few seconds of that your phone will enter recovery mode.
Once in the recovery mode, select wipe data/factory reset > Yes to confirm your action. Wait for a few minutes until the phone wipes your data. Once done, go back to recovery menu and Wipe Cache Partition and then Wipe Dalvik Cache as well.
Select install zip from sdcard > choose zip from SD card. Locate the custom ROM file copied earlier by pressing the Power key. Once confirmed, the ROM installation will begin.
Repeat the above step but choose GApps file instead of the ROM file.
When GApps get installed, go back to the main recovery menu and select reboot system now to reboot the phone.
That’s it.

Enjoy Android 5.1.1 Stock Rooted custom firmware on your T-Mobile Samsung Galaxy S5 G900T.









Noticia:
http://wccftech.com/flash-galaxy-s5-custom-rom/#ixzz3hSmIu6S8

[Jorge-Vieira]

New Android Vulnerability That Kills Devices Discovered

http://cdn.eteknix.com/wp-content/uploads/2015/07/android-hack-800x697.jpg
Following the discovery of the Stagefright vulnerability (http://www.eteknix.com/95-android-devices-vulnerable-dangerous-exploit/), another potentially dangerous Android hack has been found. The bug, uncovered by Trend Micro, can leave an Android device effectively dead, killing the screen and all communication functions, including calls, and can be found in Android 4.3 (Jelly Bean) up to the current Android 5.1.1 (Lollipop). Though it was first reported late-May of this year, there has not been a patch fix released through the Android Open Source Project (AOSP) code by the Android Engineering Team.
The fault can be exploited by either a malicious app or a phishing site, using a malicious MKV video file – much like Stagefright, which also used media files to compromise Android operating systems – designed to auto-start whenever the device boots.
As for the technical details, I’ll leave that to Trend Micro:

The vulnerability lies in the mediaserver service, which is used by Android to index media files that are located on the Android device. This service cannot correctly process a malformed video file using the Matroska (http://matroska.org/) container (usually with the .mkv extension). When the process opens a malformed MKV file, the service may crash (and with it, the rest of the operating system).
The vulnerability is caused by an integer overflow when the mediaserver service parses an MKV file. It reads memory out of buffer or writes data to NULL address when parsing audio data.
This wil cause the device to become totally silent and non-responsive. This means that:



No ring tone, text tone, or notification sounds can be heard. The user will have no idea of an incoming call/message, and cannot even accept a call. Neither party will hear each other.


The UI may become very slow to respond, or completely non-responsive. If the phone is locked, it cannot be unlocked.


http://cdn.eteknix.com/wp-content/uploads/2015/07/android-killer-1.png

<iframe width="640" height="390" src="https://www.youtube.com/embed/gjn5QTaQ0fk" frameborder="0" allowfullscreen></iframe>




Short of being careful and vigilant when downloading apps or visiting websites, the vulnerability will remain a potential threat until patched by Google.
Thank you Trend Micro (http://blog.trendmicro.com/trendlabs-security-intelligence/trend-micro-discovers-vulnerability-that-renders-android-devices-silent/) for providing us with this information.
Image courtesy of Ausdroid (http://ausdroid.net/wp-content/uploads/2013/11/Android-malware-hack.jpg).



Noticia:
http://www.eteknix.com/new-android-vulnerability-kills-devices-discovered/

[Jorge-Vieira]

Official PACman Android 5.1.1 Custom ROM Released – Here’s How to Install It

Did you check the custom ROMs based on Android 5.1.1 Lollipop (http://wccftech.com/update-note-3-to-android-5-1-1-euphoriaos/) we shared with you for Samsung Galaxy Note 3? Adding to that rich list of stable and popular custom firmwares is the PACman Android 5.1.1 custom ROM for Samsung Galaxy Note 3. Bringing gesture control lock screen and advanced keyboard options among a multitude of other features, this is an official release of the very famous custom firmware. Follow this guide to flash PACman Android 5.1.1 custom ROM on your Samsung Galaxy Note 3 LTE N9005.
http://cdn.wccftech.com/wp-content/uploads/2014/12/Samsung-Galaxy-Note-4-with-Android-5.0-Lollipop-with-refreshed-TouchWiz-Nature-UX-3.0-635x357.jpg (http://cdn.wccftech.com/wp-content/uploads/2014/12/Samsung-Galaxy-Note-4-with-Android-5.0-Lollipop-with-refreshed-TouchWiz-Nature-UX-3.0.jpg)
Note: The link works with Samsung Galaxy Note 3 LTE N9005. You can follow the steps with other Samsung Galaxy devices (http://wccftech.com/update-galaxy-s4-i9505-to-android-5-1-1-teamub/), but do not use this ROM zip file with any other device.




Before you update Galaxy Note 3 N9005 to PACman Android 5.1.1:

Backup any important data (http://wccftech.com/how-to-backup-sms/) from your Samsung Galaxy Note 3 as a complete wipe will be required during the flashing process.
Enable USB debugging option on your device: Settings > Development Options > USB debugging.
Samsung Galaxy Note 3 N9005 must be rooted (http://wccftech.com/root-galaxy-note-3-n9005-on-xxuend6-android-4-4-2/), unlocked and installed with a recovery tool like TWRP or CWM.
Your device must be charged to at least 60% of power.

Steps to update Galaxy Note 3 N9005 to PACman Android 5.1.1:Required files: download PACman Android 5.1.1 (https://s.basketbuild.com/filedl/devs?dev=pacman&dl=pacman/hlte/Official/pac_hlte-lp-mr1-Official-20150613.zip) for Galaxy Note 3 N9005 and save it on your computer. Do not extract the contents. Also download the Google Apps Package for your Note 3 from here (http://wccftech.com/download-latest-google-apps-android-1/).


Connect Galaxy (http://wccftech.com/unfreeze-android-smartphone-tips/) Note 3 N9005 to your computer using a USB cable and copy the zip file to your phone’s SD card.
Disconnect the USB cord and power off your Samsung Galaxy (http://wccftech.com/fix-galaxy-s6-battery-issues/) Note 3.



Boot it into recovery mode by pressing and holding Volume Up + Home + Power buttons together.



Wipe data task: from CWM recovery menu, select wipe data / factory reset and confirm the process. Then go on to wipe cache partition and wipe dalvik cache.



From recovery menu, select install zip from sdcard followed by choose zip from sdcard. Locate the PACman Android 5.1.1 custom firmware (http://wccftech.com/update-galaxy-s3-i9300-to-android-5-1-1-custom-rom/) and confirm the flashing process.
Once done, repeat the above step for installing Gapps on your smartphone.



After installation is done successfully, return back to main recovery menu and reboot your Note 3 N9005 into the new custom ROM. First boot takes a good 5 minutes so please be patient.

Let us know if you loved the latest release by PACman.
– Recommended: Fix “Root Access Possibly Lost” and “Root access missing” Error Messages on Android (http://wccftech.com/fix-missing-or-lost-root-access/)







Noticia:
http://wccftech.com/pacman-android-5-1-1-custom-rom/#ixzz3hlxe0IuB

[Jorge-Vieira]

Android DoS Vulnerability Affects 95% of Android Devices – Patch Released
According to a security research firm, a denial-of-service (DoS) vulnerability is present in Android 4.0.1 Jelly Bean through Android 5.1.1 Lollipop (http://wccftech.com/fix-android-5-1-1-battery-issues/) affecting roughly 95% of the Android devices.
http://cdn.wccftech.com/wp-content/uploads/2015/08/android-vulnerability.jpg (http://cdn.wccftech.com/wp-content/uploads/2015/08/android-vulnerability.jpg)
Android DoS vulnerability discovered and patchedSecurity researchers at Trend Micro have reported finding a second DoS vulnerability in Android’s mediaserver component. The group had discovered another vulnerability related to the mediaserver component which Google classified as “low severity” and hasn’t fixed yet. The latest Android vulnerability (CVE-2015-3823 (http://blog.trendmicro.com/trendlabs-security-intelligence/android-mediaserver-bug-traps-phones-in-endless-reboots/)) is triggered when mediaserver processes a malformed MKV video file causing an integer overflow. This overflow then sends the affected device to an endless loop when trying to read video frames. According to the security group, an attacker can exploit this Android vulnerability (http://wccftech.com/how-to-disable-flash-in-chrome/) by using one of the following two methods:


By making users install an app and then having mediaserver process a specially crafted MKV file via this app. This causes system to slow down until it has no battery left, continuing to loop until system resources or battery are exhausted.
In the second scenario, attacker could trick users into visiting a website containing malicious MKV file embedded into the HTML page which triggers the same action as above when the video file is played.

In this attack, service continues to loop even if the malicious app is terminated until system resources aren’t depleted. Attackers could also program the app to start at boot causing endless reboot loop for the affected device.





This endless reboot may render Android devices unusable unless the devices are opened in safe mode and the app is removed. Getting rid of the app is quite problematic. It may be difficult to locate the app once downloaded. Attackers may opt to keep it hidden and silent for a long time and only trigger the attack days or months later. Users may believe it is not installed and attribute the reboots to problems in the Android system. – Wish Wu, mobile threat response engineer at Trend Micro
Affecting around 95% of the Android devices, Google has patched this latest Android vulnerability (http://wccftech.com/android-security-flaw-950-million-users-at-risk/). However, due to fragmented ecosystem and dependency on carriers and OEMs, it will take a while to patch all the affected devices. Good news is that the security firm says it hasn’t spotted any attacks exploiting this vulnerability. However, with the exploit now being made public, users are at a greater risk of being affected by it. These Android vulnerabilities are easily exploited as only a specially crafted MMS message containing media file could affect the targeted device.
– Recommended: Get Rid of Adobe Flash Security Issues – Here’s How to Disable (http://wccftech.com/how-to-disable-flash-in-chrome/)






Noticia:
http://wccftech.com/android-dos-vulnerability/#ixzz3hvK3dAp9

[Jorge-Vieira]

Google Nexus Devices To Receive Monthly Security Updates From Now On

Android has found itself in the headlines these days for all the wrong reasons (http://wccftech.com/android-security-flaw-950-million-users-at-risk/), especially when it comes to security and data privacy. Keeping that negative limelight in mind, Google has taken a potential step that will ensure that its Nexus lineup of devices stays up to date when it comes to security patches and fixes, alongside the usual platform updates, of course.
http://cdn.wccftech.com/wp-content/uploads/2015/08/Unknown-635x340.jpg
Google claims that Android was forged with security in mind since day one. But lately, the Mountain View company’s mobile OS has been the target of a lot of major vulnerabilities, leaving the end user in harm’s way when it comes to their data. In fact, recently we’ve come across a bunch of different reports revealing how Android is left open to attack by ill-intentioned individuals. And the worst part is: millions of devices are affected, raising a lot of questions in terms of security and how safe Android actual is when it comes to daily usage.
But all of that changes today with Google’s major announcement regarding security updates.
Google has today revealed that it will now update its Nexus lineup of devices on a monthly basis with security patches, ensuring that users get the latest and greatest fixes from the company right on cue, without any sort of delay. And of course, the platform updates will be pushed alongside as well, so users get the latest features to enhance their user experience too.




Google also notes that it has pushed out the first ever security update of this kind today as an over the air (OTA) update for users in ownership of a Nexus device. The list of devices includes the following:


Nexus 4
Nexus 5
Nexus 6
Nexus 7
Nexus 9
Nexus 10
Nexus Player

As you can see from the list, most of the bases are covered. But if you’re in the ownership of an older device, for example, a Nexus S or a Galaxy Nexus, then you’re out of luck when it comes to these security updates. Besides, the aforementioned devices don’t get Android updates from Google anyway so it’s a good idea to upgrade to something more recent if you’re planning on staying behind a secure wall.
The company has also revealed that the security updates will be pushed out to AOSP (Android Open Source Project) so that different manufacturers can push them out for their Android powered devices.

At the same time, the fixes will be released to the public via the Android Open Source Project. Nexus devices will continue to receive major updates for at least two years and security patches for the longer of three years from initial availability or 18 months from last sale of the device via the Google Store.
It’s great to see Google taking such a step in terms of security. We really hope that this trend of pushing out security updates is soon picked up by other big name manufacturers as well. And we’re sure it will, as Samsung has also announced that it will push out monthly security updates for its Galaxy lineup of Android devices.







Noticia:
http://wccftech.com/nexus-devices-receive-monthly-security-updates/#ixzz3hyeVMJet

[Jorge-Vieira]

Stagefright Patches Beginning To Appear On Nexus Handsets, Some Samsung Smartphones

http://media.bestofmicro.com/5/A/514702/gallery/stagefright_v2_breakdown_w_600.png (http://www.tomshardware.com/gallery/stagefright_v2_breakdown,0101-514702-0-2-12-1-png-.html)
Last week, a devastating Heartbleed-level (http://www.tomshardware.com/news/stagefright-vulnerability-drm-android-heartbleed,29682.html) Android vulnerability was revealed, which could allow malicious hackers to send malware to any Android user, without any action being required from the user.
Today, some phones, such as the Nexus 5 (http://support.sprint.com/support/article/Find-and-update-the-software-version-on-your-Google-Nexus-5/WServiceAdvisory_542_GKB61196-dvc8040004prd?INTNAV=SU:DP:OV:UG:LgGoogleNexus5:Fi ndAndUpdateTheSoftwareVersionOnYourGoogleNexus5#%2 1/), Nexus 6 (http://support.sprint.com/support/article/Find-and-update-the-software-version-on-your-Nexus-6/WServiceAdvisory_542_GKB80765-dvc8540024prd?INTNAV=SU:DP:eek:V:UG:Nexus6:FindAnd UpdateTheSoftwareVersionOnYourNexus6#%21/), Galaxy S5 (http://support.sprint.com/support/article/Find-and-update-the-software-version-on-your-Samsung-Galaxy-S-5/WServiceAdvisory_542_GKB69808-dvc8080008prd?INTNAV=SU:DP:OV:UG:SamsungGalaxyS5:F indAndUpdateTheSoftwareVersionOnYourSamsungGalaxy# %21/), Galaxy S6 (http://support.sprint.com/support/article/Find-and-update-the-software-version-on-your-Samsung-Galaxy-S-6/WServiceAdvisory_542_GKB85263-dvc8870001prd?INTNAV=SU:DP:OV:UG:SamsungGalaxyS632 gb:FindAndUpdateTheSoftwareVersionOnYourSamsungGal axy#%21/), Galaxy S6 Edge (http://support.sprint.com/support/article/Find-and-update-the-software-version-on-your-Samsung-Galaxy-S-6-edge/WServiceAdvisory_542_GKB85094-dvc8870008prd?INTNAV=SU:DP:OV:UG:SamsungGalaxyS6Ed ge64gb:FindAndUpdateTheSoftwareVersionOnYourSamsun gGalaxy#%21/) and the Galaxy Note Edge (http://support.sprint.com/support/article/Find-and-update-the-software-version-on-your-Samsung-Galaxy-Note-Edge/WServiceAdvisory_542_GKB80001-dvc8540025prd?INTNAV=SU:DP:OV:UG:SamsungGalaxyNote 4:FindAndUpdateTheSoftwareVersionOnYourSamsungGala xy#%21/) will receive a patch for this vulnerability, but many more phones remain open to this attack. For now, the Samsung devices are only receiving this update on Sprint. The same devices on other carriers will continue to remain vulnerable until they also send the patches in an OTA update. Sprint was also the one to announce the update for the Nexus devices, but the update will likely be available for all Nexus 5 and Nexus 6 models.

The malware can be sent through apps that allow the automatic retrieval of MMS messages, which can include just about any instant messaging application these days that has SMS and MMS integration -- even Google's own Hangouts.
Part of the solution seems to be to disable the automatic retrieval of MMS messages from all of these apps, but considering that the Zimperium (http://blog.zimperium.com/experts-found-a-unicorn-in-the-heart-of-android/) researchers who found out about the Stagefright vulnerabilities haven't yet revealed all the information about it, it's not clear just how well that would work.
Ultimately, users can't be expected to remember to disable the automatic retrieval of MMS messages from all of their IMs, so the smartphone vendors will have to patch all the affected systems (which includes all of the existing versions of Android on the market, from Android 2.2 to Android 5.1.1).
Google released a patch for only the Nexus 5 and Nexus 6 today, and so far only Sprint has released the patch for the Galaxy Note Edge, Galaxy S5, Galaxy S6 and S6 Edge. All of these constitute a tiny percentage of the Android smartphone market, so much more needs to be done from all Android OEMs.
The Zimperium researchers are expected to discuss how the vulnerability works this week at the Black Hat conference. This should only put more pressure on OEMs to patch their devices before malicious hackers learn how to send malware to their users' devices by exploiting the vulnerabilities in Android's Stagefright media library.



Noticia:
http://www.tomshardware.com/news/stagefright-nexus-sprint-galaxy-patches,29759.html

[Jorge-Vieira]

Google, Samsung Pledge Monthly Security Updates For Their Devices

The Stagefright vulnerabilities seem to have kicked some sense (http://www.tomshardware.com/news/google-android-update-problem-fix,29042.html) into both Google and Samsung, because both companies will now start pushing security updates every month for their devices, over the air.
Google tried before to create the Update Alliance to fix an update situation that was even worse than it is today, but even if it succeeded to some degree, the plan itself was moderate at best. It offered only 18 months of updates for mobile devices, with no guidelines for how fast those updates should happen.
Plus, although most of the major manufacturers may upgrade their flagship devices for 18 months, not all devices at all price points benefit from such upgrades. Some may only receive one upgrade in their whole life cycle, or perhaps none at all.
Google and Samsung announced that they will try to improve the situation a little by pushing security updates every month to their devices from now on. Google has already pushed a patch (http://www.tomshardware.com/news/stagefright-nexus-sprint-galaxy-patches,29759.html) for the Stagefright vulnerabilities (http://www.tomshardware.com/news/stagefright-vulnerability-drm-android-heartbleed,29682.html), and some of Samsung's devices have started getting a similar patch as well. Samsung also said it's in discussions with carriers around the world to implement this faster, new update process (http://global.samsungtomorrow.com/samsung-announces-an-android-security-update-process-to-ensure-timely-protection-from-security-vulnerabilities/) that should allow their devices to become more secure.
Samsung has been pushing its devices in the enterprise market with the Knox security features, so it has a real profit incentive to make them as secure as possible. Otherwise, its devices would stop being taken seriously in the enterprise world, where Android devices already suffer from a bad image regarding their security.
What neither of the two companies said is how long they are going to provide these updates. Are the two companies willing to extend the time for which a device is getting security updates well beyond the time in which it gets OS updates? Or will the security updates stop as soon as the last scheduled OS update arrives on certain devices?
Ideally, we should be seeing OS updates for at least two years, considering that's how long the vast majority of smartphone owners keep their devices, so they should be fully supported in this time period. Security updates should probably be received for four years, to ensure that only a very small percentage of the smartphone owners would be vulnerable to critical security vulnerabilities.
Google and Samsung at least took a small step to improve the major problem with security updates on Android. Ultimately, it won't matter as much just how secure (http://www.tomshardware.com/news/android-lollipop-new-security-features,27974.html) the Android OS is if it can't be fixed on time when security vulnerabilities are inevitably found. We already know that customized Android software (http://www.tomshardware.com/news/customized-android-firmware-security-vulnerabilities,29631.html) only makes this problem significantly worse to manage, so for the Android ecosystem to become more secure overall, more OEMs will have to step up their game when it comes to security issues.



Noticia:
http://www.tomshardware.com/news/google-samsung-monthly-security-updates,29767.html

[Jorge-Vieira]

Fingerprint scanners on Android phones are far less secure than on iPhones


http://www.techspot.com/images2/news/bigimage/2015/08/2015-08-06-image-10.jpg


The Samsung Galaxy S5's fingerprint reader security vulnerabilities (http://www.techspot.com/news/56406-galaxy-s5-fingerprint-scanner-can-easily-be-fooled-hacked.html) were well documented over a year ago. But if you were hoping the world’s most popular Android device manufacturer had mended its exposure to easy hacks since then, recent Black Hat revelations (https://www.blackhat.com/us-15/briefings.html#fingerprints-on-mobile-devices-abusing-and-leaking) will come as a disappointing surprise.
During the esteemed and anxiety-inducing security convention, FireEye researchers Tao Wei and Yulong Zhang presented a summary of known issues (http://www.zdnet.com/article/hackers-can-remotely-steal-fingerprints-from-android-phones/) pertaining to mobile devices capable of recognizing fingerprints.
The Galaxy S5 and HTC One Max in particular fared poorly; both were vulnerable to a "fingerprint sensor spying attack" that could remotely lift prints from the phones because neither manufacturer fully lock down the sensor.
As the report points out, “the leakage of fingerprints is irredeemable”, so once hacked the target might lose control of passwords, personal data and, most vexing of all, mobile payment access for good. A seasoned cyber-criminal can also carefully cover their tracks so as to loot fingerprints from several smartphone users over a period of time.
Samsung, HTC and Huawei are now aware of the flaw and have already begun updating their software. Meanwhile, Apple's Touch ID sensor was deemed "far more secure" as it encrypts fingerprint data from the scanner.
"Even if the attacker can directly read the sensor, without obtaining the crypto key, [the attacker] still cannot get the fingerprint image," Zhang noted.
Hopefully, Google will take a page from Apple’s playbook when wrapping up Android M (http://www.techspot.com/news/60817-android-m-officially-unveiled-google-io.html), the platform’s first build endowed with native fingerprint capabilities.



Noticia:
http://www.techspot.com/news/61657-fingerprint-scanners-android-phones-far-less-secure-than.html

[Jorge-Vieira]

Android fragmentation: at least 24,093 distinct devices in the wild


http://www.techspot.com/images2/news/bigimage/2015/08/2015-08-06-image-18.jpg

Google’s developer dashboard (http://developer.android.com/about/dashboards/index.html) is perhaps the best indicator of Android fragmentation as it directly relates to its mobile operating system. An equally as important metric that often goes overlooked is just how many different devices make up the Android community.
An eye-opening report (http://opensignal.com/reports/2015/08/android-fragmentation/) from OpenSignal found that there are at least 24,093 distinct Android devices in the wild. That’s up from 18,796 unique devices last year and a huge increase from the 3,997 Android devices in circulation in 2012.
http://www.techspot.com/images2/news/bigimage/2015/08/2015-08-06-image-19.jpg
As OpenSignal brand strategist Samuel Johnston notes, the complexity is both good and bad (http://opensignal.com/blog/2015/08/05/android-fragmentation-2015/).
One of the perks, Johnston highlights, is that if you can imagine your dream phone, there’s a pretty good chance that someone, somewhere will have probably built it. Conversely, a huge pool of devices to choose from means the apps you install may not be optimized for your device’s screen size or features.
http://www.techspot.com/images2/news/bigimage/2015/08/2015-08-06-image-20.jpg
OpenSignal said it has also observed other trends over the past several years that were too broad to include under the fragmentation umbrella such as screen size, NFC prevalence and increases in CPU core count and included RAM.
Johnston singles out NFC prevalence as one interesting trend. The chart above shows the rapid adoption of NFC in Android devices between 2012 and 2013 before leveling off over subsequent years. The reason for this, he notes, is that the technology was expected to be revolutionary but it ultimately never took off.



Noticia:
http://www.techspot.com/news/61666-android-fragmentation-least-24093-distinct-devices-wild.html

[Jorge-Vieira]

Certifi-gate is the latest Android security scandal

Today's high-level Android vulnerability is called Certifi-gate (http://www.checkpoint.com/resources/certifigate/index.html). As you might have guessed, it gets its name from an underlying problem with the way the operating system handles digital certificates in the context of remote support tools (RSTs). The vulnerability can let an attacker gain full control over a victim's device.
Here's roughly how it goes. A bog-standard RST app will usually ask for a normal set of user permissions, but it also needs to install a plugin with elevated permissions so it can perform its tasks. While the RST is digitally signed by its vendor, the plugin needs to be signed by the device's OEM. Due to the coupling of these components, the app itself ends up gaining elevated permissions. Thus, an attacker can exploit a vulnerability in the RST to gain control over the device.
There are several problems with this approach. An OEM can carelessly sign a plugin without checking whether the underlying code is secure. If the application's vendor needs to update its plugin, it has to wait for the OEM to sign it again. Also, since Android doesn't have an app certificate revocation mechanism, a user with an older version of an app remains vulnerable until they install the latest version. Last but not least, the user has relatively little control over the plugin: it won't show an icon in the launcher since it's an exported service, and the Play Store won't indicate that a plugin required by an RST requires elevated permissions.
Check Point, the company that disclosed the vulnerability, has analyzed multiple remote support tools. It found that TeamViewer, RSupport, AnySupport, and CommuniTake are vulnerable. It has also built an app (http://play.google.com/store/apps/details?id=com.checkpoint.capsulescanner) that will scan your device for the vulnerability.



Noticia:
http://techreport.com/news/28781/certifi-gate-is-the-latest-android-security-scandal

[Jorge-Vieira]

Cortana headed for Android and iOS

http://www.fudzilla.com/media/k2/items/cache/d1e6eac87435b4d3315cd2a2b9d36266_L.jpg (http://www.fudzilla.com/media/k2/items/cache/d1e6eac87435b4d3315cd2a2b9d36266_XL.jpg)

Better than anything they have
Software giant Microsoft is onto a winner with its Cortana search and has plans to bring it to iOS and Android.

This means that the Bing powered search will no longer be an exclusive to Windows-based devices, but it also means that it could be the thing to drive users to Microsoft's less than stellar search engine.
Using the Android version of Cortana, the voice assistant feature will be able to replace Google Now as the default.
This will no doubt help make Cortana better integrated with the Android operating system, but even then there are some limitations.
Google Now can be activated by saying "OK Google", but voice activation for Cortana is not possible at the moment due to hardware limitations. This prevents Cortana from constantly listening for its activation phrase, but we reckon this is good enough.
Jobs knows how long it will take Redmond to get under the bonnet of iOS. Siri might be less useful than Cortana, but it is part of the Apple cult and many fanboys believe that it must be superior simply because it was released by Steve Jobs.



Noticia:
http://www.fudzilla.com/news/mobile/38427-cortana-headed-for-android-and-ios


A MS está a tentar com que a Cortana se torne em algo universal, mas devido a todas as limitações, seja de HW dos concorrentes que usam Android, seja de atraso nas linguagens disponíveis e também da própria utilidade que a Costana possa ter, é algo que se tem de aguardar para ver como vai ser a integração e adopção desta assistente digital.
Alguém utiliza isto?

[Jorge-Vieira]

Google’s Vulkan Will Make Android Gaming Faster and More Powerful



http://cdn.eteknix.com/wp-content/uploads/2015/08/vulkan-800x600.jpg
Google has announced that it is introducing low-overhead API Vulkan to its Android devices, bringing with it improved speed and graphics while reducing the load on the CPU.
“Even the most careful developers can hit unforeseen bottlenecks, in part because the drivers for some graphics processors may reorganize all of that data before it can actually be processed,” Shannon Woods, Shannon Woods for Google’s Android operating system, explained in a blog post (http://android-developers.blogspot.co.uk/2015/08/low-overhead-rendering-with-vulkan.html). “In order to address some of the sources of CPU overhead and provide developers with more explicit control over rendering, we’ve been working to bring a new 3D rendering API, Vulkan, to Android.”
Vulkan allows programmers to access the hardware of whichever Android device a game is running on, much in the same way as Apple’s Metal, giving them more flexibility and power to exploit while saving the processor much of its usual overhead.
“We’ll be working hard to help create, test, and ship Vulkan, but at the same time, we’re also going to contribute to and support OpenGL ES,” Woods added. “As a developer, you’ll be able to choose which API is right for you: The simplicity of OpenGL ES, or the explicit control of Vulkan. We’re committed to providing an excellent developer experience, no matter which API you choose.”
High-end Android smartphones and tablets released over the last six months – featuring Qualcomm’s Adreno 400-series GPUs and Nvidia’s Tegra K1 – should support Vulkan, with further hardware integration planned for future devices.
Thank you readwrite (http://readwrite.com/2015/08/10/android-vulkan-game-apps-developers) for providing us with this information.
Image courtesy of diit.cz (http://diit.cz/sites/default/files/vulkan_logo_800px.jpg).



Noticia:
http://www.eteknix.com/googles-vulkan-will-make-android-gaming-faster-powerful/


Uma excelente noticia para o Android :thumbsup:

[Jorge-Vieira]

Android privilege-escalation vulnerability affects 55% of devices

There must be a glitch in the Matrix. I feel like I'm writing the same news again and again. A pair of researchers from IBM's X-Force Application Security Research Team (http://www.ibm.com/security/xforce/) has discovered a set of vulnerabilities (https://securityintelligence.com/one-class-to-rule-them-all-new-android-serialization-vulnerability-gives-underprivileged-apps-super-status/) in Android and some popular app SDKs. The worst of the bugs can let a seemingly innocuous app run arbitrary code on the device, and it's present in Android versions 4.3 and above—affecting 55% of handsets worldwide. Check out the proof-of-concept video, where the Facebook app is replaced with Fakebook:


https://www.youtube.com/watch?v=VekzwVdwqIY


Both Google and the SDK makers have provided patches for their respective software, but as always, updates for non-Nexus devices must go through OEMs and carriers, so there's no word on when users will actually have fixes for their handsets. The researchers claim they have yet to see any exploits in the wild, but that could change at any moment.
The main vulnerability lies in how a piece of Android's code (specifically, the OpenSSLX509Certificate class) handles serialization (https://en.wikipedia.org/wiki/Serialization) during inter-process communication (IPC). A malicious app that needs no special permissions from the user can exploit the bug to inject malicious code into IPC requests. By doing so, the malicious app can gain system-level permissions.
The researchers also found similar vulnerabilities in some app SDKs. They surveyed 37,701 apps and discovered that a number of those were exploitable. Furthermore, the vulnerable apps all relied on the same set of six SDKs. The tools in question all misused a low-level toolkit called SWIG (http://www.swig.org/), which led to a code injection vulnerability similar to the one presented above. In this context, a malicious program could exploit a vulnerable app to gain the same level of permissions as the target, potentially gaining full access to that app's data and capabilities.
Full details of these exploits are available in IBM Security's research paper (http://www.usenix.org/system/files/conference/woot15/woot15-paper-peles.pdf).



Noticia:
http://techreport.com/news/28802/android-privilege-escalation-vulnerability-affects-55-of-devices

[Jorge-Vieira]

Google launches second patch for Stagefright bug (http://www.kitguru.net/gaming/security-software/matthew-wilson/google-launches-second-patch-for-stagefright-bug/)


Google has gone ahead and launched a second patch for the Stagefright bug in Android, which had the potential to affect hundreds of millions of Android devices. Google’s first attempt to fix the bug apparently failed to do so, but thanks to security firm, Exodus Intelligence, everything should now be patched up.
In a blog post, Exodus explained: “Around July 31st, Exodus Intelligence security researcher Jordan Gruskovnjak noticed that there seemed to be a severe problem with the proposed patch. Jordan proceeded to investigate whether his assumptions regarding its fallibility were well founded. They were”.
http://www.kitguru.net/wp-content/uploads/2015/08/android_logo-600x4001.gif (http://www.kitguru.net/wp-content/uploads/2015/08/android_logo-600x4001.gif)
As The Inquirer notes (http://www.theinquirer.net/inquirer/news/2419531/text-based-android-stagefright-attack-is-bad-news-for-950-million-users), Exodus initially got in touch with Google about a flaw in Android quite some time ago, though the company only just responded this week and issued a patch. In a statement sent to the news site (http://www.theinquirer.net/inquirer/news/2419531/text-based-android-stagefright-attack-is-bad-news-for-950-million-users), a Google spokesperson pointed out that “We’ve already sent the fix to our partners to protect users, and Nexus 4, 5, 6, 7, 9, 10 and Nexus Player will get the OTA update in the September monthly security update.”
This all follows Google’s recent announcement that it would be stepping up its security game with monthly patches and updates (http://www.kitguru.net/gaming/security-software/matthew-wilson/google-and-samsung-plan-monthly-security-updates-for-android/) for Nexus device users going forward. Samsung also announced a similar scheme (http://www.kitguru.net/gaming/security-software/matthew-wilson/google-and-samsung-plan-monthly-security-updates-for-android/) of its own for Galaxy users, though it did not say when it intended to start.



Noticia:
http://www.kitguru.net/gaming/security-software/matthew-wilson/google-launches-second-patch-for-stagefright-bug/

[Jorge-Vieira]

Android Won't Catch A Break Until Google Fixes The Update System

http://media.bestofmicro.com/1/J/461431/gallery/Untitled_w_600.png (http://www.tomshardware.com/gallery/Untitled,0101-461431-0-2-12-1-png-.html)Last week Google, Samsung, LG and other major smartphone manufacturers promised to patch (http://www.tomshardware.com/news/stagefright-nexus-sprint-galaxy-patches,29759.html) the Stagefright vulnerabilities promptly, and some of them have already started to send the fixes over the air. However, according to researchers from Exodus Intelligence, the patch itself isn't a great one and still allows attackers to exploit the Stagefright media library.
Researchers from Zimperium initially found the vulnerabilities (http://www.tomshardware.com/news/stagefright-vulnerability-drm-android-heartbleed,29682.html) in Android's Stagefright video library, which affected an estimated 950 million users, and reported the problem to Google four months ago.
Stagefright Saga Continues One of the patches for the "Google Stagefright 'tx3g' MP4 Atom Integer Overflow" vulnerability was only four lines of code. Researcher Jordan Gruskovnjak from Exodus Intelligence noticed something might be wrong with that patch, but couldn't verify it until devices began receiving it from Google.
After the patch was sent to the Nexus 5, the researcher managed to create an MP4 file that would bypass the patch, and he received a crash message, which points to some level of success.
Android 4.0 and later versions received support for a security feature called address space layout randomization (ASLR), which makes it much harder for attackers to insert malware into Android devices. However, its exploitation is not impossible for skilled hackers, and Exodus Intelligence believes the newly uncovered vulnerability in Google's patch will need to be fixed as well.
The company has already collaborated with Zimperium, the original discoverers of the Stagefright vulnerabilities, to cover the new bug in its Stagefright Detector app, which it recently launched.

“We've been in contact with Zimperium and are working with them to provide coverage for detection of this flaw through their Stagefright Detector app. They have been very responsive (more so than the affected vendor) and we plan to alert them of similar flaws we've recently discovered," said the company in a blog post (http://blog.exodusintel.com/2015/08/13/stagefright-mission-accomplished/).
Android Security, Forever Doomed? Ultimately, what this new vulnerability shows is that there will always be dangerous security bugs that could impact hundreds of millions of Android users (if not more as Android expands its market), and Google needs a serious rethink (http://www.tomshardware.com/news/google-android-update-problem-fix,29042.html) for how it can provide those updates. Otherwise, all of the sandboxes Google throws at Android's design might be irrelevant.

Apple, Microsoft and even the fragmented "Linux" ecosystem all have a much better security update model than Android has right now. In the Android ecosystem, the model seems to be companies fixing stuff whenever they feel like it, and if they feel like it. That's a model that certainly can't scale to billions of users -- not without leaving a majority of them always vulnerable to some bug or another.
The best update system Google has come up with recently -- and only because of a Stagefright-level vulnerability -- is to get a few more OEMs to agree to a monthly security update program. However, this solution is not enough to solve the bigger problem with Android security updates.
First off, none of those companies mentioned if all of their devices will receive updates in such a manner, and they didn't say for how long in their lifecycles this will happen. To make matters worse, in the U.S, they'll only send the updates through the carriers.
Second, only two OEMs, other than Google, agreed to set up this monthly security updates system. Therefore, it doesn't come close to being a total solution for the whole Android ecosystem.
Eventually, Google, as well as all of the OEMs, will have to agree to set up a system where Google controls all of the updates, no matter how much they hate the idea right now. The question is how many more Stagefright-level vulnerabilities will Android users have to endure until that finally happens?



Noticia:
http://www.tomshardware.com/news/android-update-system-needs-fixing,29848.html

[Jorge-Vieira]

Report: Stagefright patch doesn't fix 950 million vulnerable devices

The patch (http://techreport.com/news/28764/google-and-samsung-will-update-android-faster-after-stagefright) for Android's Stagefright vulnerability (http://techreport.com/news/28701/95-of-android-phones-vulnerable-to-stagefright-mms-exploit) won't actually protect your phone, some security researchers say. According to Jordan Gruskovnjak and Aaron Portnoy of Exodus Intelligence (http://blog.exodusintel.com/2015/08/13/stagefright-mission-accomplished/), a malformed MP4 file can still create a buffer overflow, a vulnerability that could then be used to compromise 950 million Android phones.
The Exodus blog post walks through the vulnerability. A function in libStagefright reads two values from an MP4 file's header, chunk_size and chunk_type, as 32-bit integers. If the header returns a value of 0x01 for chunk_size, then a 64-bit value is read from the MP4 instead. According to the researchers, if an MP4 is crafted with a chunk size of 0x1fffffff (or any other value outside the bounds of a 32-bit integer), a flaw in the Stagefright patch's boundary-checking code means it's still possible to cause a buffer overflow.
Exodus says it notified Google of its findings on August 7. The company asked Google for a timeframe for another fix, but has not received a response. Since the Stagefright vulnerabilities were originally reported to Google in April, and it's been more than 90 days since that original disclosure, Exodus has decided to make the results of its research public. For now, even patched Android devices appear to remain vulnerable to the bug.



Noticia:
http://techreport.com/news/28835/report-stagefright-patch-doesnt-fix-950-million-vulnerable-devices

[Jorge-Vieira]

Another High Risk Vulnerability Affects Android – From Gingerbread to Lollipop

Even the “another day, another Android security flaw” fails to express the disdain that users now have toward the long-ridiculed security system of Android.
http://cdn.wccftech.com/wp-content/uploads/2015/07/Android-danger-sign-e1427293501573-635x421.jpg (http://cdn.wccftech.com/wp-content/uploads/2015/07/Android-danger-sign-e1427293501573.jpg)
A new Android vulnerability (CVE-2015-3842) has now been identified that is caused by the operating system’s mediaserver component. Yep, again! A heap overflow in mediaserver’s Audio Policy Server affects almost all the Android versions from 2.3 Gingerbread to the very latest 5.1.1 Lollipop and enables a local application to execute arbitrary code with the privileges of the mediaserver process. Discovered by security researchers at Trend Micro, this high severity Android vulnerability could be remotely leveraged to install malware onto a target device using specially crafted messages.
We have seen several vulnerabilities identified in the mediaserver (http://wccftech.com/android-dos-vulnerability/) component of Android. This latest vulnerability involves a component called AudioEffect of mediaserver. Wish Wu of Trend Micro explained (http://blog.trendmicro.com/trendlabs-security-intelligence/mediaserver-takes-another-hit-with-latest-android-vulnerability/) that the security bug can be exploited by getting the victim to install an app that doesn’t require any permissions. He further notes how victim’s privacy could be at serious risk due to the involvement of mediaserver component that deals with everything from images to videos.





This attack can be fully controlled, which means a malicious app can decide when to start the attack and also when to stop. An attacker would be able to run their code with the same permissions that mediaserver already has as part of its normal routines. Since the mediaserver component deals with a lot of media-related tasks including taking pictures, reading MP4 files, and recording videos, the privacy of the victim may be at risk.
Researchers developed a proof-of-concept malicious app to demonstrate the capabilities of this high severity flaw. They tested this app on a Nexus 6 powered by Android 5.1.1 LMY47Z (http://wccftech.com/root-nexus-10-android-5-1-1-lmy47v-install-custom-recovery/). The malicious app, once installed, crashed the mediaserver component. If the app fails to crash the component, it will stop and run again.
Thankfully, the flaw has already been patched by Google. Trend Micro had reported the vulnerability on June 19 under Google’s new Android Security Rewards program. Wu also submitted the patch helping Google include it in its August security update. Security researchers said they aren’t aware of any active attacks exploiting this vulnerability.







Noticia:
http://wccftech.com/another-high-risk-android-security-vulnerability-discovered/#ixzz3jFFHfPOY

[Jorge-Vieira]

Galaxy S5 Receives Official Android 5.1.1 Update with Stagefright Fix – How to

Android Stagefright security update is now available for Samsung Galaxy S5. This is an important update coming to fix the Stagefright Android vulnerability (http://wccftech.com/another-high-risk-android-security-vulnerability-discovered/). With Stagefright vulnerability, all the attackers need is your mobile number to remotely execute malicious code using a specially crafted message. This is an extremely serious vulnerability as the target doesn’t need to do anything unlike in the spear-phishing attacks where victim falls to some trap. Google has now fixed the bug which means you should update your devices as soon as you receive the notification of this patch.
Samsung and T-Mobile are releasing this official update to users in multiple stages; users will start receiving the OTA notification in the coming days. However, if you want to flash this security update right away, here is how to manually do so.
http://cdn.wccftech.com/wp-content/uploads/2015/02/Android-51-Lollipop-main.jpg (http://cdn.wccftech.com/wp-content/uploads/2015/02/Android-51-Lollipop-main.jpg)




Note: This is an official Android 5.1.1 security update for T-Mobile Samsung Galaxy S5 model SM-G900T. Please do not try it on other variants. Flashing updates manually could void your device’s warranty; only proceed if you know the risks associated with the process.
Prerequisites to update Galaxy S5 to G900TUVU1FOG6 Android 5.1.1:

Create a backup (http://wccftech.com/how-to-backup-sms/) of all important data in your Galaxy device.
Download and install USB drivers for Samsung Galaxy S5 in your computer.
Enable USB debugging (http://wccftech.com/enable-usb-debugging-on-galaxy-s5/) option by pressing Menu > Settings > Applications. Navigate and tap on Developer Options to ensure that USB Debugging is enabled.
Ensure that your T-Mobile Samsung Galaxy S5 G900T carries more than 80% of charge.

How to flash G900TUVU1FOG6 Android 5.1.1 on Galaxy S5 to fix Stagefright:Files required: download G900TUVU1FOG6 Android 5.1.1 (http://www.sammobile.com/firmwares/download/52654/G900TUVU1FOG6_G900TTMB1FOG6_TMB/) for T-Mobile Galaxy S5. Also download Odin3 v3.10.6 for installation from here (http://androidhost.org/wZgTz). Unzip Odin; and unzip the official firmware file to get the .tar.md5 file.


Install Odin on your PC and launch it.
Switch your Samsung Galaxy S5 off and boot it in Download mode: press and hold Volume Down, Powerand Home buttons together.
Connect your SGS5 via a USB cable; when connected successfully, you will get a message in Odin saying Added!!. (In case you don’t get it, try another USB port. If that doesn’t help either, then re-install USB drivers).
Click on AP in Odin and locate the G900TUVU1FOG6 .tar.md5 file.
In Odin make sure to uncheck Re-Partition. Hit START.
When update installation is successfully completed, you will see your T-Mobile Samsung Galaxy S5 rebooting.

First boot takes a few long minutes so please be patient.







Noticia:
http://wccftech.com/flash-g900tuvu1fog6-android-5-1-1-on-t-mobile-galaxy-s5/#ixzz3jFHOcWaU

[Jorge-Vieira]

Trend Micro Finds MediaServer Vulnerability In Android, Affecting Most Devices

http://media.bestofmicro.com/0/U/519726/gallery/mediaserver-vulnerability_w_600.png (http://www.tomshardware.com/gallery/mediaserver-vulnerability,0101-519726-0-2-12-1-png-.html)Security researchers from Trend Micro uncovered yet another media-related (http://www.tomshardware.com/news/stagefright-vulnerability-drm-android-heartbleed,29682.html) vulnerability, this time in the MediaServer program. Attackers can exploit this vulnerability to run arbitrary code on the devices, giving it the same permissions as the MediaServer program itself.
The vulnerability affects all Android versions from Android 2.3 to Android 5.1.1, but Trend Micro stated that Google has already pushed a fix to the Android Open Source Project on August 1. Trend Micro made Google aware of the bug on June 19.
The security company also said that it hasn't seen any exploits of this vulnerability in the wild so far. However, knowing the big problem (http://www.tomshardware.com/news/android-update-system-needs-fixing,29848.html) the Android ecosystem has with updates, only a small part of the existing devices will fix this vulnerability in the future, while most of the others will remain vulnerable to it.
The attackers can use the vulnerability to ask Android users to install an app, which doesn't require any permission, making the user think it's safe. The attack can be fully controlled by the malicious hacker, who can start or stop it at any time.
The attacker's code gets the same permissions as the MediaServer program, which has the ability to perform many media-related tasks. This includes taking pictures, reading video files, recording video, all of which can put the user's privacy at risk.
According to the Trend Micro researchers, the attack can be quite stealthy, making it hard to detect and the attacker may not even trigger the attack for months after the device is infected.
The best course of action against this bug would be to upgrade your device once the patch is ready from your phone's manufacturer. If no such patch is received or you don't want to wait until then, Trend Micro's Mobile Security (https://play.google.com/store/apps/details?id=com.trendmicro.tmmspersonal.emea) app will also detect malicious apps that want to take advantage of this vulnerability.
The company also said users could reboot their devices in safe mode, and uninstall the malicious app from there if they have already detected it, but this method may prove too difficult for most users.



Noticia:
http://www.tomshardware.com/news/trend-micro-mediaserver-vulnerabilities-android,29871.html

[Jorge-Vieira]

Galaxy S4, Nexus 7, and HTC One M8 Receive Stagefright Lollipop Update

Considered as one of the high-risk security vulnerabilities (http://wccftech.com/another-high-risk-android-security-vulnerability-discovered/) discovered in Android operating system, carriers have started rolling out updates to fix the exploit. We shared with you yesterday a complete guide to manually flash Android 5.1.1 on Samsung Galaxy S5 (http://wccftech.com/flash-g900tuvu1fog6-android-5-1-1-on-t-mobile-galaxy-s5/) fixing the Stagefright vulnerability.
http://cdn.wccftech.com/wp-content/uploads/2015/08/stagefright-1024x500-635x310.jpg (http://cdn.wccftech.com/wp-content/uploads/2015/08/stagefright-1024x500.jpg)
Stagefright fix arrives for more devices today:Google and carriers are working to roll out this critically important security update as soon as possible. Stagefright bug allows attackers to take control of your data and steal data from the devices. In the latest run, Nexus 7, Samsung Galaxy S4 and the HTC One M8 have received the Stagefright exploit fix. These three updates have come from Verizon and Sprint. Here are the details about which devices are getting what update:






Samsung Galaxy S4 has received the LRX22C.I545VRUGOF1 Android 5.0.1 from Verizon to patch the bug; update also brings stability tweaks.
Android 5.1.1 incremental update from Verizon for Nexus 7 bringing all the Material Design goodies.
And, Sprint has rolled out Android 5.0 Lollipop update for HTC One M8 (http://wccftech.com/update-htc-one-m8-to-android-5-1-1-teamub/) to patch the exploit with no other changes.

Regardless of the serious risk that Stagefright poses Android users to, all these three (and other similar future updates for different devices) will be rolled out in multiple phases in different regions. Let us know if you have received the notification already on your devices. If you think you might have missed the notification, you can go to Settings > About Device > Software Updates > Check Now to confirm if you have got the update notification from your carrier. If you have indeed received the firmware update notification, click to download it. Once done, move forward with the installation. Make sure you charge your devices to at least 60% before starting the installation process.
Don’t forget to share if you have received the update on your devices. Please share your region, carrier, and device names for our readers to get a clue on when to expect this patch from their carrier.







Noticia:
http://wccftech.com/stagefright-fix-for-verizon-sprint-devices/#ixzz3jLmfDX4U

[Jorge-Vieira]

Update Galaxy S3 to PACMAN Android 5.1.1 Lollipop – How to

PACMAN custom firmware based on Android 5.1.1 Lollipop (http://wccftech.com/tag/android-5-1-1-custom-roms/) is now available for AT&T Samsung Galaxy S3 I747. While there is no hope of Lollipop coming to Galaxy S3, you can taste all the features and much more with this beautiful and stable custom ROM. Here are all the PACMAN Android 5.1.1 features for Samsung Galaxy S3 I747 followed by a complete guide to help you flash the custom ROM on your own smartphone.
http://cdn.wccftech.com/wp-content/uploads/2015/08/Header-635x173.png
Prerequisites to flash Android 5.1.1 on Galaxy S3 I747:

Backup any important data (http://wccftech.com/how-to-backup-sms/) from your Samsung Galaxy S3 SGH-I747 as a complete wipe will be required during the flashing process.
Enable USB debugging option on your device: Settings > Development Options > USB debugging.
Samsung Galaxy S3 must be rooted, unlocked and installed with a recovery tool like TWRP or CWM.
Your device must be charged to at least 60% of power.

Note: this tutorial is focused on AT&T Samsung Galaxy S3 SGH-I747; kindly do not try this guide on other Android (http://wccftech.com/flash-g900tuvu1fog6-android-5-1-1-on-t-mobile-galaxy-s5/) & Samsung (http://wccftech.com/fix-galaxy-s6-battery-issues/) devices.
http://cdn.wccftech.com/wp-content/uploads/2015/08/Features_List.png (http://cdn.wccftech.com/wp-content/uploads/2015/08/Features_List.png)




How to update Galaxy S3 I747 to Android 5.1.1 PACMAN:Required files: download the PACMAN Android 5.1.1 Lollipop (https://s.basketbuild.com/filedl/devs?dev=pacman&dl=pacman/d2att/Nightly/pac_d2att-lp-mr1-Nightly-20150818.zip) custom firmware for Galaxy S3 I747. and save it on your computer. Also download GApps (http://wccftech.com/download-latest-google-apps-android-1/) package. Do not extract the contents.


Connect Galaxy S3 to your computer using a USB cable and copy the zip file to your phone’s SD card.
Disconnect the USB cord and power off your Galaxy S3.
Boot it into recovery mode by pressing and holding Volume Up + Home + Power buttons together.
Perform a Nandroid backup of your current OS: Backup > backup and restore on ClockworkMod recovery.
Wipe data task: from CWM recovery menu, select wipe data / factory reset and confirm the process. Then go on to wipe cache partition and wipe dalvik cache.
From recovery menu, select install zip from sdcard followed by choose zip from sdcard. Locate the PACMAN Android 5.1.1 Lollipop custom firmware and confirm the flashing process.
Return back to main recovery menu and reboot your AT&T Samsung Galaxy S3 into the new custom ROM. First boot takes a good 5 minutes so please be patient.

How to restore: If you want to return to previous OS on your SGS3, boot into recovery, select backup and restore then restore your previous ROM by selecting it from the list.







Noticia:
http://wccftech.com/flash-android-5-1-1-pacman-on-galaxy-s3-i747/#ixzz3jY9HCdiR

[Jorge-Vieira]

Cortana speaks fluent Android

(http://www.fudzilla.com/media/k2/items/cache/f6e789f4e6c0e80d2a8a68b0f29d2f1a_XL.jpg)
Hands on: We just tried it
Microsoft promised Cortana was coming to Android, and this is now happening, at least for users in the USA.

Fudzilla was among the first thousand Android users to install and try this new piece of software. It is a 20MB download that installs rather quickly.
We were not surprised that Microsoft wants just about every possible detail you can imagine from your location, phone call list, SMS, photos, microphone to the Wifi and Bluetooth. They want to know everything probably to sell you better adds in addition to providing the smart assistant service.
Once you install the Cortana android application you will be asked to enter your Microsoft user name and password. After that you are good to go. We asked Cortana how long was the Golden Gate bridge and it knew the answer – 8980 feet or 2737 meters.
First time Cortana thought we asked it how long is to Golden Gate Bridge and we got a funny answer that it didn't think we can get there by car which was sort of true. We were 5979.1 miles away when we asked the question.

http://www.fudzilla.com/images/stories/2015/August/Cortana1.jpg
Cortana also knows that Angela Merkel is in Vienna today, we guess she asked the NSA as they tend to keep tabs on her. There were a few other things it knew. It gave us an answer about Microsoft stock that got up 1.9 percent to $41.27 while we wrote the story – clearly someone in Wall Street was betting on a positive review.
Swiping up the home button will ofer you a choice between Google Now and Cortana, until you set one of them as default application. We used both after each other and got similar results for the basic questions.
Cortana can tell you the ages of all the women from the Friends telly show and all the other important questions.
You can use Cortana to change your 3 PM appointment to 4PM. The only way we got it stumped was when we asked Cortana to tell us a joke.
http://www.fudzilla.com/images/Cortana3.jpg



Noticia:
http://www.fudzilla.com/news/mobile/38561-cortana-speaks-android-now

[Jorge-Vieira]

AMIDuOS Turns Two: Lollipop Support And A Price Change

AMI announced version 2.0 of its AMIDuOS software, bringing feature compatibility with the latest Android OS. AMIDuOS is software that runs Android in a virtual machine that can be used by consumers to run Android programs on a PC, or by programmers to develop and test apps.

AMI also shifted its pricing of these products in order to accommodate offering the older AMIDuOS V1.x (http://www.tomshardware.com/news/amiduos-android-windows,28543.html) software alongside the V2.0 software.
The primary features that version 2.0 offers are expanded support for Android 5.0.1 and 64-bit programs. Although the beta version (http://www.tomshardware.com/news/amiduos-android-lollipop-beta,29397.html) released last month first demonstrated these functions, v2.0 can be seen as a more stable solution. It is also more feature complete, moving to Lollipop 5.0.1, rather than the Lollipop 5.0 version used in the beta.
The latest version is also compatible with the Android ART runtime environment and hosts new APIs for Bluetooth LE, multi-networking, NFC and other standards. These improvements, in addition to AMIDuOS's typical A/V sync improvements, graphics improvements and audio improvements, makes it an even better tool for testing and developing Android applications.
Realizing that devices utilizing the 32-bit Android 4.x are still widely used, AMI opted to continue to sell V1.x of AMIDuOS alongside the version 2.0 release. This gives users a greater range of options when it comes time to test their applications. If required, both versions of AMIDuOS can be installed on the system side-by-side without any conflicts.
For users who have been using AMIDuOS for a long time and now want to try version 2.0, there's no need to break out your wallet. AMI opted to give anyone who purchased AMIDuOS v1.x prior to August 7, 2015 a free copy of version 2.0. This offer is available indefinitely, and users who download the latest AMIDuOS can continue using their older version, as well.
If you purchased AMIDuOS between August 7 and today, however, then you will not be eligible for a free copy of AMIDuOS v2.0. In order to continue to offer both products, AMI will continue to sell V1.x for $10 as it always has, and offer V2.x for $15.
The latest AMIDuOS is available now.

http://media.bestofmicro.com/L/C/478992/gallery/android-and-windows_w_300.png




Noticia:
http://www.tomshardware.com/news/amiduos-version-2,29929.html

[Jorge-Vieira]

Flash CM 12.1 Stable Android 5.1.1 on HTC One M7 – How to

The CM team started releasing stable builds of CyanogenMod 12.1 (http://wccftech.com/cm-12-1-android-5-1-1-stable-rom-for-nexus-4/) for various popular flagship devices last week. We already shared with you the links to flash CM 12.1 Nightlies on your smartphone, here is how you can now experience more stable performance with one of the most popular custom firmware for Android devices. Follow this guide to flash CM 12.1 Stable ROM on your HTC One M7.
http://cdn.wccftech.com/wp-content/uploads/2015/02/nexusae0_CyanogenMod-Logo-635x401.jpg (http://cdn.wccftech.com/wp-content/uploads/2015/02/nexusae0_CyanogenMod-Logo.jpg)
Prerequisites to update HTC One M7 to CM 12.1 Stable Android 5.1.1 ROM:

Backup any important data (http://wccftech.com/how-to-backup-sms/) from your HTC One M7 as a complete wipe will be required during the flashing process.
Make sure ADB and Fastboot is configured on your PC.
Your device must be rooted with unlocked bootloader (http://wccftech.com/how-to-root-verizon-htc-one-and-install-cwm-twrp-recovery/) and installed with a recovery tool.
Your device must be charged to at least 60% of power.

How to update HTC One to CM 12.1 Stable Android 5.1.1:Required files: download CM 12.1 Stable Snapshot (http://androidhost.org/bmHrD) file for HTC One M7 and save it on your computer. Also download Google Apps Package (http://wccftech.com/download-latest-google-apps-android-1/).
1- Connect your HTC One M7 to your computer using a USB cable and copy the zip file and GApps to your phone (http://wccftech.com/xperia-z4-ultra-and-xperia-z4-compact-spotted/) memory’s root folder.




2- Switch off your HTC One M7 and enter into Recovery mode: press and hold the Volume Down and Power buttons.
3- Select Backup and Restore to perform Nandroid Backup and then go back to main menu. Next, you must wipe data by selecting wipe data/factory reset.
4- Now, select Install zip from sdcard > choose zip from sdcard from the main recovery menu. Locate the CM 12.1 Stable Android 5.1.1 custom ROM for HTC One M7. Select and confirm.
5- When the CM 12.1 custom ROM is flashed, use the same method to install GApps. After you are done, select reboot system now to perform a normal boot. It will take some time to load all files as the first boot takes more time.







Noticia:
http://wccftech.com/how-to-flash-cm-12-1-stable-android-5-1-1-on-htc-one-m7/#ixzz3lE5ZirCn

[Jorge-Vieira]

Lollipop Graces One Out Of Five Android Devices As Marshmallow Comes To Town

It's been just over 10 months since Android 5.0 Lollipop (http://hothardware.com/tags/lollipop) was first made available to the general public, and in that time, it's found its way onto one out of every five Android (http://hothardware.com/tags/android) devices. If you'd prefer to take the glass half empty approach, you can point out that four out of five Android devices are still waiting for Lollipop, Marshmallow (http://hothardware.com/news/light-the-campfire-android-ms-name-is-marshmallow) be damned.

According to the data by Android Developers, Android 5.0 is installed on 15.9 percent of Android devices, while Android 5.1 (also Lollipop) adds another 5.1 percent. That comes out to an even 21 percent.


http://hothardware.com/ContentImages/NewsItem/35000/content/Lollipop.jpg


The majority of Android devices these days are rocking Android 4.4, otherwise known as KitKat. It holds a 39.2 percent share of the Android device market, followed by versions 4.1.x through 4.3 (Jelly Bean) at 31.8 percent, 2.3.3 through 2.3.7 (Gingerbread) at 4.1 percent, 4.0.3 through 4.0.4 (Ice Cream Sandwich) at 3.7 percent, and version 2.2 (Froyo) at 0.2 percent.

We know, rattling off a bunch of numbers is about as interesting as listing to someone describe how drunk they got the night before at a frat party, or recount how they got screwed by the river in a Texas Hold 'Em tournament after going all-in. It's the story behind the numbers that matter, which in this case is that the most prevalent version of Android is soon to be two generations old.

The issue of fragmentation is one that Google has yet to solve, perhaps because Google doesn't view it as a problem. After all, if you want to always have the latest and greatest version of Android, you can purchase a Nexus device or get into the third-party ROM scene.


http://hothardware.com/ContentImages/NewsItem/35000/content/marshmallow_android.jpg


Those options are of little consolation to Android device owners waiting for their handset maker and wireless carrier to dole out an update to Lollilop, which will still put them a generation behind once Marshmallow rolls out.

Speaking of which, Marshmallow is expected to be available to the general public by the end of the month. Despite the jump to Android 6.0, it's more of an incremental upgrade with a focus on bug fixes and other backend improvements.






Noticia:
http://hothardware.com/news/lollipop-graces-20-percent-of-android-devices-as-marshmallow-comes-to-town#ixzz3lHIX59F1

[Jorge-Vieira]

Android Stagefright Exploit Released To The Public

http://media.bestofmicro.com/5/A/514702/gallery/stagefright_v2_breakdown_w_755.png (http://www.tomshardware.com/gallery/stagefright_v2_breakdown,0101-514702-0-2-12-1-png-.html)Zimperium, the security company that initially found the vulnerabilities in Android's Stagefright media library (http://www.tomshardware.com/news/stagefright-vulnerability-drm-android-heartbleed,29682.html), promised on August 5 that it would release an open source exploit for testing purposes. The company has now released (https://blog.zimperium.com/the-latest-on-stagefright-cve-2015-1538-exploit-is-now-available-for-testing-purposes/) the exploit in the wild to get Android OEMs to hurry up and deliver the patches to their devices, but also to allow other security experts to test whether their devices are still vulnerable.
Exploit in the wild The publicly released exploit is not a "generic exploit," the company said, because it has only tested it on an older Nexus running Android 4.0.4. The Stagefright vulnerability used for the exploit has been neutered by Android 5.0's use of the GCC 5.0 compiler, which comes with integer overflow mitigation.
Zimperium's release of the exploit doesn't necessarily make it that much easier for attackers to exploit Stagefright, as other exploits have already been created that can even bypass Android's address space layout randomization (ASLR) protection, and there are likely to be more out there that we don't know about.
Upgrades still in poor shape So far only Google (Nexus devices), Samsung, and LG have promised monthly security updates (http://www.tomshardware.com/news/stagefright-nexus-sprint-galaxy-patches,29759.html) after the Stagefright vulnerabilities were first made public. However, a few other companies such as Motorola, HTC, Sony and others also started sending Stagefright patches for some of their devices.
The main problem here is that none of these companies are going to patch most of the exploitable devices, which includes all Android 2.3 devices and beyond, covering over 900 million smartphones and tablets. At best, the majority of the OEMs will upgrade their most popular devices from the past two years, and that's about it.
Because Google is not responsible with the updates for the Android ecosystem, that pits Android OEMs in a price race to the bottom, where the costs of developing new updates for smartphones gets discounted as unimportant, compared to other priorities such as using a better camera, processor or screen, or simply having a lower price than the competition. This situation may never be fixed (http://www.tomshardware.com/news/android-update-system-needs-fixing,29848.html) by itself until Google takes the whole responsibility upon itself (and the OEMs allow it to do that).

Initial quick-fixes not enough The Stagefright vulnerabilities were indeed a wake-up call for Google as well as some manufacturers but were unlikely to be big enough to make them consider a significantly improved upgrade system. After all, only three companies promised monthly security updates, and even they didn't say for how long that will be in place for certain devices, or whether all devices will be under the new update program.
Some apps such as Hangouts and Messenger have also been updated by Google to resist Stagefright exploits, considering the easiest way to attack a user is through an MMS or other video file sent to SMS or other messaging apps that have auto-retrieval of video files enabled.
However, this isn't the only way users can be attacked. They can also receive video files through the browser when visiting a website. Typically, the user would have to accept such a file, though, so the risk there is minimized.

Checking for Stagefright vulnerabilities To check whether you're still vulnerable, you can use Zimperium's Detector (http://www.tomshardware.com/news/zimperium-stagefright-vulnerability-detector-app,29770.html) app. The app now also checks against the bugs in the Stagefright library, which were unveiled shortly after the first Stagefright announcement was made by Exodus Intelligence (http://blog.exodusintel.com/2015/08/13/stagefright-mission-accomplished/). Patches for these latest bugs haven't been distributed to many devices yet, though, as they are set to arrive in the next batch of official upgrades from Android OEMs (which could be a few weeks for Google, LG and Samsung, or a few months for others).
Zimperium has also collaborated with Google to include the Detector app's logic into the Android Compatibility Test Suite (CST) to ensure that all new smartphones will be protected against these vulnerabilities.



Noticia:
http://www.tomshardware.com/news/android-stagefright-exploit-publicly-released,30056.html

[Jorge-Vieira]

Samsung Introduces Android 6.0 Security Feature in a Latest Lollipop Update

Google has been trying to push its partners to be more proactive in sending Android security updates to their consumers. Since the discovery of a major security threat, Stagefright (http://wccftech.com/new-stagefright-2-0-bugs-1-4-billion-android-users-at-risk/) which put over a billion of Android users at risk, there has been a lot of uproar from the users as well. As Apple leads the game when it comes to sending timely and consistent security updates and Microsoft, with its nascent Windows 10 Mobile, intends to take charge of OS updates (http://wccftech.com/microsoft-to-control-windows-10-mobile-updates/), all the eyes are then pinned at Android and how it moves forward to offer more mobile security and privacy to the users.
– Recommended: Samsung redesigns TouchWiz before releasing Android 6.0 Marshmallow (http://wccftech.com/galaxy-s6-android-6-marshmallow-screenshots/) http://cdn.wccftech.com/wp-content/uploads/2015/12/security-level_0.jpg
Samsung offers Marshmallow feature in Lollipop to improve Android security: Google’s OEM and carrier partners committed to send monthly security patches to their users, released by Google. Among these, Samsung also promised to keep its “high-end” devices up-to-date with security updates. However, it wasn’t until now that you could actually see Samsung being more proactive about it. After the Stagefright-episode, Google introduced a security feature in Android 6.0 Marshmallow (http://wccftech.com/fix-sd-card-as-internal-memory-on-android-6-issues/) that showed the date the device last received a security update, in order to put more pressure on its partners giving them public visibility. As reported (http://wccftech.com/googles-passive-aggressive-trick-to-improve-android-security/),

This security update date would let the users know when their devices last received the security update, promised by many manufacturers. While it is not an aggressive measure from Google to push mandatory monthly updates, the tactic will help put some light on those who are lagging behind in sending out these updates.
Advertisements


Latest Lollipop update rolled out to Samsung devices has now updated the About Phone section of the Settings menu which shows exactly the same Marshmallow feature – the date of last security patch delivered to a device. Folks at Android Central (http://www.androidcentral.com/new-samsung-lollipop-firmware-now-shows-your-android-security-patch-level) report that Samsung Galaxy S6 Edge+ builds (G928FXXS2AOK9) in Europe and Galaxy Note 5 (N920CXXU2AOK6) users in the Middle East have confirmed this new security addition.
Similar to Android 6.0 Marshmallow, the new Lollipop firmware on Samsung devices shows a field “Android security patch level,” showing a date when the phone last received a security update from Samsung. To confirm if you too have received this latest feature, go to Settings, and scroll down to About Phone. Don’t forget to let us know which Samsung device you own, if you too have received this update.
VIA (http://9to5google.com/2015/12/07/samsungs-android-lollipop-security-patch-information/)







Noticia:
http://wccftech.com/samsung-introduces-marshmallow-android-security-feature-in-lollipop/#ixzz3tev7WQgG

[Jorge-Vieira]

Multiple Motorola Devices Will Not Be Upgraded to Lollipop

http://i1.wp.com/www.eteknix.com/wp-content/uploads/2016/02/hero-droids-20160216.png?resize=521%2C428
These days we are being told that we need to install or swap out software and hardware all the time to keep it up to date. With everything from Windows Updates recommending a whole new operating system (http://www.eteknix.com/windows-10-now-recommended-update/) to a “security update” locking up your iPhones (http://www.eteknix.com/apple-releases-software-update-fix-error-53/). When I decided to try out Windows Mobile (when it was first released) I liked the OS, except that it didn’t support anything. To my surprise (or not as the case was) they decided that my handset would be one of the ones that wouldn’t get the Windows 8 Mobile upgrade, leaving my phone outdated and out supported. It would seem that Motorola made the same decision with the Droid Ultra, Maxx and Mini editions regarding the latest Lollipop update.
On their forums Motorola posted (https://forums.motorola.com/posts/5e90184773?commentId=1032966#) the following:

“We apologise that we will not be upgrading DROID Ultra/Mini/Maxx to Android Lollipop, as we had hoped. We know how important software upgrades are to our customers, and we’re very sorry that we are unable to provide the upgrade.”
In an attempt to bring back any customers upset by this those with the Ultra/Mini or Maxx handsets can upgraded to the DROID Turbo 2 for $524 or the DROID Maxx 2 for $334.
The worst part about all of this is that the upgrade was promised and now instead of delivering on that promise they want you to pay for a new handset. No doubt this is going to upset anyone with one of the mentioned headsets, are you one of those people and if so how do you feel about this?



Noticia:
http://www.eteknix.com/multiple-motorola-devices-will-not-be-upgraded-to-lollipop/

[Jorge-Vieira]

Lollipop Now Most Popular Version Of Android, Fluffy Marshmallow At Just 2.3 Percent


Comparatively speaking, there aren't a lot of Android (http://hothardware.com/tags/android) devices in the wild running Android 6.0 (http://hothardware.com/tags/android-60), otherwise known as Marshmallow (http://hothardware.com/tags/marshmallow). That's typically true of any snapshot of Android—the latest and greatest version finds its way onto just a small number of handsets while versions a generation or two old rule the roost. As of right now, pole position belongs to Android 5.x Lollipop.

It took Lollipop more than a year—16 months, to be exact—to leapfrog Android 4.4 KitKat for the top spot. But there it now sits, at least if combining the number of devices running Android 5.0 (16.9 percent) and Android 5.1 (19.2 percent). If you add the two together, Lollilop's share of the Android market is 36.1 percent, versus 34.3 percent for KitKat.


image: http://hothardware.com/ContentImages/NewsItem/36769/content/Android_Lollipop.jpg
http://hothardware.com/ContentImages/NewsItem/36769/content/Android_Lollipop.jpg


One thing to note is that these aren't exact figures. Google tallies the number of Android devices running different versions of its mobile operating system by collecting data over a seven-day period gathered from its Google Play Store app. That means Google's data is a reflection of devices that have checked into Google's servers. It leaves out some rooted devices, Amazon Fire tablets, and so forth.

While it's not a perfect accounting method, it's the best that's currently available. And as always, what it shows is that hardware manufacturers and wireless carriers are slow to adopt the latest version of Android. Marshmallow was made available to the general public five months ago, yet it's tied with Android 4.0 Ice Cream Sandwich for fifth place behind Android 2.3 Gingerbread, which debuted over five years ago.

It's a familiar trend and one that isn't likely to change so long as control of distributing Android builds remains in the hands of third parties. This is especially true of older devices—manufacturers don't have a lot of incentive to keep supporting dated phones—but even some newer phones are slow to adopt updated Android builds.

Do you own and Android device? If so, which one and what version of Android are you running?



Noticia:
http://hothardware.com/news/lollipop-now-most-popular-version-android-marshmallow-just-23-percent#TvEcEaAFV4jbA71b.99