Tuesday, 21 March 2017

How to install Android O on Nexus 5X [bullhead] Dev Preview

Download and install Android Dev Preview for Nexus 5X.Android O but we’re really hoping it’ll become Android Oreo once it’s released).Introduces a number of new features and APIs to use in your apps. Here's are just a few new things for you to start trying in this first Developer Preview.
download- android-oreo
For the second year in a row, Google is making a developer preview for the next version of Android available in March, well ahead of its presumed consumer release in the fall. This one is codenamed “O,” and your guess is as good as mine as to what dessert the final version will be named after. It isn’t yet available for regular users to try out. Although developers can begin testing it right away, it’s best for most people to let things stabilize a bit more before they try it out. Developers can download it today.

Downloads





How to install Android O Dev Preview on Nexus 5X:

  1. Download the Android O image for Nexus 5X below, then unzip it to a safe directory.
  2. Connect your device to your computer over USB.
  3. Start the device in fastboot mode with one of the following methods:
    • Using the adb tool: With the device powered on, execute:
      adb reboot bootloader
    • Using a key combo: Turn the device off, then turn it on and immediately hold down the relevant key combination for your device. For example, to put a Nexus 5 ("hammerhead") into fastboot mode, press and hold Volume Up + Volume Down + Power as the device begins booting up.
  4. If necessary, unlock the device's bootloader using one of the following methods:
    • If you are updating a Nexus 5X or Nexus 6P device using the hammerhead or angler builds, update your fastboot tool to the latest available version (>=23.0.1), and then run this command:
      fastboot flashing unlock
    • If you are updating an older device, run this command:
      fastboot oem unlock

    The target device will show you a confirmation screen. (This erases all data on the target device.)
  5. Open a terminal and navigate to the unzipped Android O image for Nexus 5X.
  6. Execute the flash-all script. This script installs the necessary bootloader, baseband firmware(s), and operating system.
Once the script finishes, your device reboots and Android O image for Nexus 5X will installed. You should now lock the bootloader for security:

How to Lock bootloader 

  1. Start the device in fastboot mode again, as described above.
  2. Execute: 
    fastboot flashing lock
    or, for older devices, run
    fastboot oem lock
Locking bootloader will wipe the data on some devices. After locking the bootloader, if you want to flash the device again, you must run fastboot oem unlock again, which will wipe the data.

Labels: , , , ,

Android O is Here : Download Android O Dev Preview for for Nexus...

The O Developer Preview includes an updated SDK with system images for testing on the official Android Emulator and on Nexus 5X, Nexus 6P, Nexus Player, Pixel, Pixel XL and Pixel C devices. If you're building for wearables, there's also an emulator for testing Android Wear 2.0 on Android O may be Oreo.O-MG, the Developer Preview of Android O is here.
Here is the latest Android version dev preview i.e Android O.



So, today, I'm excited to share a first developer preview of the next version of the OS: Android O. The usual caveats apply: it's early days, there are more features coming, and there's still plenty of stabilization and performance work ahead of us. But it's booting :).

Over the course of the next several months, we'll be releasing updated developer previews, and we'll be doing a deep dive on all things Android at Google I/O in May. In the meantime, we'd love your feedback on trying out new features, and of course testing your apps on the new OS.
What's new in O?

Android O introduces a number of new features and APIs to use in your apps. Here's are just a few new things for you to start trying in this first Developer Preview:

Background limits: Building on the work we began in Nougat, Android O puts a big priority on improving a user's battery life and the device's interactive performance. To make this possible, we've put additional automatic limits on what apps can do in the background, in three main areas: implicit broadcasts, background services, and location updates. These changes will make it easier to create apps that have minimal impact on a user's device and battery. Background limits represent a significant change in Android, so we want every developer to get familiar with them. Check out the documentation on background execution limits and background location limits for details.


Notification channels: Android O also introduces notification channels, which are new app-defined categories for notification content. Channels let developers give users fine-grained control over different kinds of notifications — users can block or change the behavior of each channel individually, rather than managing all of the app's notifications together.





Notification channels let users control your app's notification categories

Android O also adds new visuals and grouping to notifications that make it easier for users to see what's going on when they have an incoming message or are glancing at the notification shade.


Autofill APIs: Android users already depend on a range of password managers to autofill login details and repetitive information, which makes setting up new apps or placing transactions easier. Now we are making this work more easily across the ecosystem by adding platform support for autofill. Users can select an autofill app, similar to the way they select a keyboard app. The autofill app stores and secures user data, such as addresses, user names, and even passwords. For apps that want to handle autofill, we're adding new APIs to implement an Autofill service.

PIP for handsets and new windowing features:

Picture in Picture (PIP) display is now available on phones and tablets, so users can continue watching a video while they're answering a chat or hailing a car. Apps can put themselves in PiP mode from the resumed or a pausing state where the system supports it - and you can specify the aspect ratio and a set of custom interactions (such as play/pause). Other new windowing features include a new app overlay window for apps to use instead of system alert window, and multi-display support for launching an activity on a remote display.

Font resources in XML: Fonts are now a fully supported resource type in Android O. Apps can now use fonts in XML layouts as well as define font families in XML — declaring the font style and weight along with the font files.

Adaptive icons: To help you integrate better with the device UI, you can now create adaptive icons that the system displays in different shapes, based on a mask selected by the device. The system also animates interactions with the icons, and them in the launcher, shortcuts, Settings, sharing dialogs, and in the overview screen.


Adaptive icons display in a variety of shapes across different device models.


Wide-gamut color for apps: Android developers of imaging apps can now take advantage of new devices that have a wide-gamut color capable display. To display wide gamut images, apps will need to enable a flag in their manifest (per activity) and load bitmaps with an embedded wide color profile (AdobeRGB, Pro Photo RGB, DCI-P3, etc.).

Connectivity: For the ultimate in audio fidelity, Android O now also supports high-quality Bluetooth audio codecs such as LDAC codec. We're also adding new Wi-Fi features as well, like Wi-Fi Aware, previously known as Neighbor Awareness Networking (NAN). On devices with the appropriate hardware, apps and nearby devices can discover and communicate over Wi-Fi without an Internet access point. We're working with our hardware partners to bring Wi-Fi Aware technology to devices as soon as possible.

The Telecom framework is extending ConnectionService APIs to enable third party calling apps integrate with System UI and operate seamlessly with other audio apps. For instance, apps can have their calls displayed and controlled in different kinds of UIs such as car head units.

Keyboard navigation: With the advent of Google Play apps on Chrome OS and other large form factors, we're seeing a resurgence of keyboard navigation use within these apps. In Android O we focused on building a more reliable, predictable model for "arrow" and "tab" navigation that aids both developers and end users.

AAudio API for Pro Audio: AAudio is a new native API that's designed specifically for apps that require high-performance, low-latency audio. Apps using AAudio read and write data via streams. In the Developer Preview we're releasing an early version of this new API to get your feedback.

WebView enhancements: In Android Nougat we introduced an optional multiprocess mode for WebView that moved the handling of web content into an isolated process. In Android O, we're enabling multiprocess mode by default and adding an API to let your app handle errors and crashes, for enhanced security and improved app stability. As a further security measure, you can now opt in your app's WebView objects to verify URLs through Google Safe Browsing.

Java 8 Language APIs and runtime optimizations: Android now supports several new Java Language APIs, including the new java.time API. In addition, the Android Runtime is faster than ever before, with improvements of up to 2x on some application benchmarks.

Partner platform contributions: Hardware manufacturers and silicon partners have accelerated fixes and enhancements to the Android platform in the O release. For example, Sony has contributed more than 30 feature enhancements, including the LDAC codec, and 250 bug fixes to Android O.

Labels: , , ,

Friday, 10 March 2017

CyanogenMod se transforma en LineageOS

Quien no uso la ROM de CyanogenMod? yo creo que muchos usuarios de teléfono celulares que tenemos la inquietud de actualizar Android en nuestros dispositivos alguna vez usamos esta ROM, que gracias a ella pudimos actualizar nuestros equipos, cuando los fabricantes dejaron de darle el soporte de actualización.

Personalmente lo probé en varios equipos y la verdad que revivía los equipos con la actualización, por ejemplo con un LG P500 Optimus que ya era muy antiguo, de hecho traí las primera versión de Android se pudo actualizar a Android 4.4 Kitkat gracias a CyanogenMod.

También muchos saben que ya no existe este proyecto llamado CyanogenMod, para muchos fue una sorpresa, pero para otros no tanto, ya que este proyecto se transformó o convirtió en uno nuevo que lleva el nombre de LineageOS donde se sigue desarrollando la ROM para muchos dispositivos.

LineageOS va en la versión 14.1 y está basado en Android 7 Nougat para traerles nuevas caracteríticas a muchos dispositivos móviles.

La ROM de LineageOS cubre a muchas marcas y modelos de teléfonos celulares, ya que cuenta con un buen equipo de desarrolladores y desde luego con una gran comunidad.

Para saber si tu dispositivo móvil se puede actualizar a Android 7 Nougat visita su página oficial.

Labels: , , , , , ,

Tuesday, 7 March 2017

Lava grand 2 un gama media con cámara de 13 megapixeles

Fabricantes de teléfonos celulares hay muchos, desde los más grandes como Samsung, LG, Motorola, Nokia y demás hasta los más pequeños y desconocidos procedentes de Asia y otros lados del mundo.

En este post vamos a hablar de una nueva marca que lleva el nombre de LAVA Smartphone o LAVA Mobile que nació en India, pero también fabrica sus productos en China y es una marca que poco a poco se está expadiendo a nivel mundial y a llegado a México desde hace un año.

Entre sus productos cuenta con smartphone, tabletas, y power bank pero en esta ocasión hablaremos sobre el teléfono celular Grand 2 que es un equipo de gama media con buenas características y sobre todo con su sistema operativo personalizado ofrece un plus al usuario final.

Características del LAVA Grand 2

  • Pantalla de 5.5" resolución 720 x 1280
  • Procesador Mediatek MT6735 a 1.3 GHZ Quad core
  • Cámara trasera de 13 MP y frontal de 8 MP (según con sensor de samsung)
  • Memoria Ram 3 GB y Rom de 16 GB
  • Batería de 3000 mAh
  • Dual sim o doble chip (puedes tener 2 números en el mismo teléfono celular)
  • Sistema operativo Star OS (basado en Android 5.1 Lollipop)  

Características tomadas desde la ejecución de apps para obtener información sobre el dispositivo como info droid, antutu benchmark y aida 64, (que en otro post compartiremos las capturas de pantalla) ya que en su página web oficial hay muy poca información sin tanta especificaciones.

Su grosor es de apenas 6.1 mm eque lo situa entre los más delgados y con el sistema operativo Star OS 2 con capa de personalización basado en Android 5.1 Lollopop que trae muchas funciones extras que facilitan ciertas actividades al usar el smartphone.

Ojalá que LAVA actualice el Star OS a Android 6.0 o 7.0, ya que es un buen equipo y creo que soportaría las actualizaciones.

Es un smartphone más a tomar en cuenta al momento de querer comprar uno nuevo.

Labels: , , , , , , , ,

Thursday, 26 January 2017

Download Supersu.zp and Su Removal.zip for Lineage os 14.1 [arm, arm64, x86]

You can download latest supersu.zip file for lineage os 14.1 to root lineageos 14.1 rom.There is also Supersu removal.zip file to unroot lineage os 14.1 roms.
Theses files will work on any lineage os 14.1 rom but make sure to download correct file according to your device structure.

Download Supersu for Lineage OS 14.1 rom

Name                              Version              File
su (arm)                           14.1                 addonsu-arm-signed.zip

su removal (arm)            14.1                 addonsu-remove-arm-signed.zip


su (arm64)                       14.1                 addonsu-arm64-signed.zip

su removal (arm64)        14.1                 addonsu-remove-arm64-signed.zip

su (x86)                             14.1                 addonsu-remove-x86-signed.zip

su removal (x86)              14.1                 addonsu-remove-x86-signed.zip



How to Enable Root Access In Lineage OS 14.1

1.Download  Super su.zip and place it in your device memory.
2.Then reboot your device into recovery mode.

3.Tap on “Install” in recovery mode and the select Super su v2.68.zip from your memory where you pasted it in 1st step.
4.Now After selecting the .zip file do “Swipe to confirm flash” at the bottom of the screen.
5.Once Flashed the Super su vxxx.x.zip files reboot your device. Done!

Labels: , , ,

Saturday, 21 January 2017

How to Build Lineageos rom for any android device Easily ! {Full guide}

Introduction

These instructions will hopefully assist you to start with a stock android device, unlock the bootloader (if necessary), and then download the required tools as well as the very latest source code for LineageOS (based on Google’s Android operating system) for your device. Using these, you can build both LineageOS and LineageOS Recovery image from source code, and then install them both to your device.
It is difficult to say how much experience is necessary to follow these instructions. While this guide is certainly not for the very very very uninitiated, these steps shouldn’t require a PhD in software development either. Some readers will have no difficulty and breeze through the steps easily. Others may struggle over the most basic operation. Because people’s experiences, backgrounds, and intuitions differ, it may be a good idea to read through just to ascertain whether you feel comfortable or are getting over your head.
Remember, you assume all risk of trying this, but you will reap the rewards! It’s pretty satisfying to boot into a fresh operating system you baked at home :). And once you’re an Android-building ninja, there will be no more need to wait for “nightly” builds from anyone. You will have at your fingertips the skills to build a full operating system from code to a running device, whenever you want. Where you go from there– maybe you’ll add a feature, fix a bug, add a translation, or use what you’ve learned to build a new app or port to a new device– or maybe you’ll never build again– it’s all really up to you.

What you’ll need

  • A android device
  • A relatively recent 64-bit computer (Linux, OS X, or Windows) with a reasonable amount of RAM and about 100 GB of free storage (more if you enable ccache or build for multiple devices). The less RAM you have, the longer the build will take (aim for 8 GB or more). Using SSDs results in considerably faster build times than traditional hard drives.
  • A USB cable compatible with your device (typically micro USB)
  • A decent internet connection & reliable electricity :)
  • Some familiarity with basic Android operation and terminology. It would help if you’ve installed custom roms on other devices and are familiar with recovery. It may also be useful to know some basic command line concepts such as cd for “change directory”, the concept of directory hierarchies, that in Linux they are separated by /, etc.
Let’s begin!

Build LineageOS and LineageOS Recovery

Note: You only need to do these steps once. If you have already prepared your build environment and downloaded the source code, skip to Prepare the device-specific code

Install the SDK

If you haven’t previously installed adb and fastboot, you can download them from Google. Extract it using: unzip platform-tools-latest-linux.zip -d ~
Now we have to add adb and fastboot to our path. Open ~/.profile and add the following:
# add Android SDK platform tools to path
if [ -d "$HOME/platform-tools" ] ; then
PATH="$HOME/platform-tools:$PATH"
fi
Then, run source ~/.profile to update your environment.

Install the build packages

Several packages are needed to build LineageOS. You can install these using your distribution’s package manager.
You’ll need:
bc bison build-essential curl flex g++-multilib gcc-multilib git gnupg gperf lib32ncurses5-dev lib32readline-gplv2-dev lib32z1-dev libesd0-dev
liblz4-tool libncurses5-dev libsdl1.2-dev libwxgtk2.8-dev libxml2 libxml2-utils lzop pngcrush schedtool squashfs-tools xsltproc zip zlib1g-dev
imagemagick
For Ubuntu 15.10 (wily) and newer, substitute:
  • lib32-readline-gplv2-dev → lib32readline6-dev
For Ubuntu 16.04 (xenial) and newer, substitute:
  • libwxgtk2.8-dev → libwxgtk3.0-dev

Java

Different versions of LineageOS require different JDK (Java Development Kit) versions.
  • LineageOS 11.0-13.0: OpenJDK 1.7 (install openjdk-7-jdk) - for Ubuntu 16.04 and newer, you can obtain OpenJDK 1.7 from the openjdk-r PPA.
  • LineageOS 14.1: OpenJDK 1.8 (install openjdk-8-jdk)

Create the directories

You’ll need to set up some directories in your build environment.
To create them:
$ mkdir -p ~/bin
$ mkdir -p ~/android/system

Install the repo command

Enter the following to download the repo binary and make it executable (runnable):
$ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo

Put the ~/bin directory in your path of execution

In recent versions of Ubuntu, ~/bin should already be in your PATH. You can check this by opening ~/.profile with a text editor and verifying the following code exists (add it if it is missing):
# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
PATH="$HOME/bin:$PATH"
fi
Then, run source ~/.profile to update your environment.

Initialise the LineageOS source repository

Enter the following to initialize the repository:
$ cd ~/android/system
$ repo init -u https://github.com/LineageOS/android.git -b cm-13.0

Download the source code

To start the download of the source code to your computer:
$ repo sync
The Lineage manifests include a sensible default configuration for repo, which we strongly suggest you use (i.e. don’t add any options to sync). For reference, our default values are -j 4 and -c. The -j 4 part means that there will be four simultaneous threads/connections. If you experience problems syncing, you can lower this to -j 3 or -j 2. -c will ask repo to pull in only the current branch, instead of the entire CM history.

Note: This may take a while, depending on your internet speed. Go and have a beer/coffee/tea/nap in the meantime!


Tip: The repo sync command is used to update the latest source code from LineageOS and Google. Remember it, as you can do it every few days to keep your code base fresh and up-to-date.

Get prebuilt apps (Lineage 11 and below)

To download the prebuilt apps, run:
$ cd ~/android/system/vendor/cm
$ ./get-prebuilts
You won’t see any confirmation- just another prompt. But this should cause some prebuilt apps to be loaded and installed into the source code. Once completed, this does not need to be done again.

Prepare the device-specific code

After the source downloads, ensure you’re in the root of the source code (cd ~/android/system), then type:
$ source build/envsetup.sh
$ breakfast manta
This will download your device’s device specific configuration and kernel.

Important: Some maintainers require a vendor directory to be populated before breakfast will succeed. If you receive an error here about vendor makefiles, jump down to Extract proprietary blobs. The first portion of breakfast should have succeded, and after completing you can rerun breakfast

Extract proprietary blobs

Now ensure your device is connected to your computer via the USB cable, with ADB and root enabled, and that you are in the ~/android/system/device/samsung/manta folder. Then run the extract-files.sh script:
$ ./extract-files.sh
The blobs should be pulled into the ~/android/system/vendor/samsung folder. If you see “command not found” errors, adb may need to be placed in ~/bin.

Turn on caching to speed up build

You can speed up subsequent builds by running:
$ export USE_CCACHE=1
and adding that line to your ~/.bashrc file. Then, specify the maximum amount of disk space you want cache to use by typing this from the top of your Android tree:
$ prebuilts/misc/linux-x86/ccache/ccache -M 50G
where 50G corresponds to 50GB of cache. This needs to be run once. Anywhere from 25GB-100GB will result in very noticeably increased build speeds (for instance, a typical 1hr build time can be reduced to 20min). If you’re only building for one device, 25GB-50GB is fine. If you plan to build for several devices that do not share the same kernel source, aim for 75GB-100GB. This space will be permanently occupied on your drive, so take this into consideration. See more information about ccache on Google’s Android build environment initialization page.

Start the build

Time to start building! Now, type:
$ croot
$ brunch manta
The build should begin.

Install the build


Assuming the build completed without errors (it will be obvious when it finishes), type the following in the terminal window the build ran in:
$ cd $OUT
There you’ll find all the files that were created. The two files we’re interested in are:
  1. recovery.img, which is the LineageOS recovery image.
  2. lineage-13.0-20170122-UNOFFICIAL-manta.zip, which is the LineageOS installer package.

Success! So… what’s next?

You’ve done it! Welcome to the elite club of self-builders. You’ve built your operating system from scratch, from the ground up. You are the master/mistress of your domain… and hopefully you’ve learned a bit on the way and had some fun too.

Labels: , ,

Tuesday, 10 January 2017

Which Gapps I install on Lineage os 6.0 and 7.1 ?

Ever faced problem while downloading gapps for lineageos i.e which gapps you should download for your device don’t worry we will show you how to select correct gapps for your device.Android Phones have become a great part of all our lives And it’s hard for us now to imagine our life without Android Phones.
One of the main reason of success for Android is its versatility, that is the ability to customize the whole device like you wish. People are now more interested in having custom ROMs on their device and experiment new looks and features on their phone.
which version to install?
CyanogenMod is one of the world’s most favorite Android Custom ROM. And all people who love to have custom ROMs on their phone must have heard about “Gapps” at least once in their journey, and this article is all about the different versions of Google Apps.


ARM64 – For 64-bit devices
There are 4 types of Platforms for which Gapps are made, you need to download the correct version of google apps according to your device type. Don’t get confused we have made it easy for you to understand, below is the way to find which version of Gapps you need to download for your Phone.
ARM – For 32-bit DevicesARM64 means the devices that are running 64 bit operating system/processor.
ARM means the device that are running 32 bit operating system/processor.
x86 x86_64for Intel Smartphones like Zenphone .
This is a very uncommon, these are used in some android emulators
Most of the Devices are 32-Bit, So if you are confused about your device configurations, then you can try the Gapps for ARM platform. And to install Gapps on your Device, Just download the Gapps.zip file and place it on your external or internal storage of phone, go to your custom recovery and clear cache and Dalvik cache and flash the zip file. So, now lets get into the download links table. Choose the correct android version and then choose your device type and package type to download gapps for your device. And if you are confused about the package name of Gapps, read the detailed explanation of each device pack below the download table.
Following are few famous Android smartphones along with information regarding their processor’s architecture pattern.
MAUNFACTURER                                 SMARTPHONE                         ARCHITECTURE
SAMSUNG                                           GALAXY S5, NOTE 4/3                        ARM
                                                              GALAXY S2 OR S3
Google (LG)                                        Nexus 5                                             ARM
Samsung                                              Galaxy S7, Galaxy S6                        ARM64
Google (LG/Huawei)                          Nexus 6P,Nexus 5X,Pixel                  ARM64
Sony                                                     Xperia Z2                                           ARM
Oppo                                                     OnePlus One                                     ARM
OnePlus                                                OnePlus 2,OnePlus 3                        ARM64                                                                                   OnePlus 3T
As the ARM64 aka x64 architecture is backward compatible, so it’s fine to install ARM aka 32-bit apps on it.
  • ARM on ARM device: OK.
  • ARM64 on arm device: Not compatible.
  • ARM on the ARM64 device: OK.
  • ARM64 on the ARM64 device: OK.
If your device is not present in the table above, then use Droid Hardware info app to figure out the correct architecture for your Android phone.

DOWNLOAD

After installing, open it up and tap on device information tab. It will display all the details regarding your phone, including the correct architecture of your phone from ARM ARM64 or x86.
It will also display Android OS along with SDK version of your phone. You can use it to figure out right DPI (Dots per inch) of your phone. Droid hardware info app is a very helpful app; it is recommended to keep a check on whats going on under the hood of your phone. There are other tools like it but it, seemed to be the best tool for figuring out right architecture of Android phone


Download gapps for lineageos roms


How to install Google Apps on Any Android Phone

Installing Gapps on any Android Phone is pretty Easy and common to most of the Android phones. If you don’t know how to do it properly or have any confusion in your mind, Follow the below-given steps to install Google Apps on your Phone.
Step 1: Download the suitable package for your Phone from the links we had given above, And place it in the internal or external storage of your phone.
Step 2: Get into Custom Recovery mode (CWM, TWRP or any recovery that your phone has), if you don’t know how to get to recovery mode, you can easily get there by using Quickboot app.
Step 3: When you got to your recovery, Go to “Wipe” and wipe cache and Dalvik cache.
Step 4: Now select Install/Flash (according to your recovery) And locate the Gapps.zip file downloaded, And flash it.
Step 5: After the Flashing process is finished, again go to wipe and wipe your cache and Dalvik cache, And then select “Reboot” to restart your phone with all the Google applications installed.

Labels: , , ,