Is There Any Easy Way That I Can Bypass Google Account. :confused:
from xda-developers http://ift.tt/2ak6jK5
via IFTTT
STATUSBAR
-Carrier Label
-DT2S on statusbar/lockscreen
-Quick Pulldown
-Battery icons
-Clock & Date customisation
-Network Traffic indicator
-status bar brightness control
NAVIGATION/RECENTS
-DT2S on navbar
-recents panel search bar toggle
-Clear all recents fab (top right/left/center,bottom right/left/center)
-Hardware buttons action( for HWnavkeys devices only)
-Longpress recents button to switch between apps
LOCKSCREEN
-Middle Lockscreen shortcuts(Custom apps)
-Quick unlock
-Music seek control when screen locked
-Volume rocker wake
-LockScreen Music Visualizer
-Music Visualizer custom colors
-LockScreen bottom shortcuts
NOTIFICATION DRAWER
-Customize quick settings tiles(add/delete/rearrange)
-Brightness slider toggle
-Advanced QS location tile
-Vibrate on touch
-Four tiles per row toggle
-toggle status bar icons
-Time contextual Headers
-Default Zephyr Header
- Disable Quick Settings in secured lockscreen
What else?
-viper4Android
-GESTURES (Hand Wave/Pocket mode)
-Heads-up toggle
-Dashboard switches
-LAYERS for theming
-Per app expanded desktop control
-Multi window mode
-light and dark theme toggle
-FORCE MOVE apps to SDCARD
-Download Speeds for your downloads
-Ability to pause/resume downloads
-Custom Ambient Display settings
-AppOps/Privacy Guard
How to flash? - Download the rom and gapps -Boot into recovery mode [TWRP] - Wipe System/Data/Dalvik Cache/Cache - Select both the ROM and [B]Gapps[B] zip file - Flash it!!! Reboot it!!! Enjoy it!!! :D |
PrinceTrishi(StarkDroid)
Sri Harsha
Akhil Narang
Adarsh-MR (designer)
AOSP-RRO(base rom)
BrokenRom
SAOSP-M
BenzoRom
AOSIP
SlimRoms
CyanogenMod
adb reboot bootloader
<boolean name="group_invites" value="true" />
<boolean name="video_call" value="true" />
<boolean name="video_calling" value="true" />
<boolean name="two_factor_auth" value="true" />
This guide only require you to be able to boot TWRP. You can follow this TWRP install guide and perform the installation of these .zip files AFTER step 8) (You must backup your system in case anything goes wrong, you will also need this backup to perform any future OTA, such as the one activating band 12). You can either stop there after installation, or proceed to the following steps if you want to have root access.
All .zip have to be installed using the TWRP "Install" function. You will need to download them on your phone or copy them on a SD card. You do not need to install all these packages at once. These scripts do not install anything, they only delete some files. You can extract them and open "update-binary" with your favorite text editor to see exactly what is done (always a good idea if you are concerned with your device security), and customize it if you wish.
This will only delete the apps in your system. If an update was performed, or if you used the app previously, the app and it's files may still be present on your device after running these scripts, but you can now uninstall them as any other app. This also means that you can rerun these scripts after a future OTA and this will not erase any app you reinstalled yourself.
Disable ads, block OTA and Amazon PARTIAL debloat "bluR1-Prime_AMZ-PARTIALdebloat-blockOTA.zip"
Disable ads, block OTA and Amazon FULL debloat "bluR1-Prime_AMZ-FULLdebloat-blockOTA.zip"
Google PARTIAL debloat "bluR1-Prime_GOOGLE-debloat.zip"
Mediatek PARTIAL debloat "bluR1-Prime_MTK-debloat.zip"
If my car is in the 2nd key position (Accessories, stereo, etc is ON) and the phone is connected via Bluetooth. If the car is then started, power cuts out for a second, the stereo reboots. On LL my phone would automatically reconnect after a couple of second, since the upgrade, something during the reconnect glitches. After this, I have to reboot the stereo AND the phone to get them to connect to each other properly. After exhausting many other options, I feel as though it is possible that the stereo reconnects "too early" in MM, causing some kind of BT error. I can turn off auto-reconnect on the stereo, and perhaps if I let MM handle it, it would be better. Anyway it seems like my STEREO is not reconnecting too early, but the PHONE is trying to connect to it too early. The stereo turns on so fast, I feel as though the phone didn't fully disconnect, causing some sort of glitch where I have to restart it. My car profile's exit task always runs successfully however Then I thought I had the perfect idea : I have a state profile (bluetooth connected to car stereo) with enter/exit tasks. My idea was to use the exit task, turn off BT, wait 5 seconds, and then turn it back on. |
20160729 10.30.04 P Inactive ID4 Car Profile 20160729 10.30.04 P Active ID17 Auto Off Unpaired Bluetooth 20160729 10.30.05 E Start ID0:0.0 TaskService 20160729 10.30.05 T Running ID-86 System 20160729 10.30.05 T Running ID5:2 Car Profile Exit 20160729 10.30.05 A OK ID-86.1 Anon.BT Voice Volume 20160729 10.30.05 T Running ID15:3 Anon 20160729 10.30.05 A OK ID-86.2 Anon.System Volume 20160729 10.30.05 T ExitOK ID-86 System 20160729 10.30.06 A OK ID5:2.1 Car Profile Exit.WiFi 20160729 10.30.06 A OK ID5:2.2 Car Profile Exit.Silent Mode 20160729 10.30.06 A OK ID5:2.3 Car Profile Exit.Media Volume 20160729 10.30.06 A OK ID5:2.4 Car Profile Exit.Notification Volume 20160729 10.30.06 A OK ID5:2.5 Car Profile Exit.com.intangibleobject.securesettings.plugin\n* **\n*!&$*;com.intangibleobject.securesettings.plug in.Activities.TabsActivity 20160729 10.30.13 A OK ID5:2.6 Car Profile Exit.Wait 20160729 10.30.13 A OK ID5:2.7 Car Profile Exit.Ringer Volume 20160729 10.30.13 T ExitOK ID5:2 Car Profile Exit 20160729 10.32.47 A OK ID15:3.1 Anon.Wait 20160729 10.32.47 P Inactive ID24 BT Raise Idle CPU 20160729 10.32.47 A OK ID15:3.2 Anon.Bluetooth 20160729 10.32.47 T ExitOK ID15:3 Anon 20160729 10.32.47 P Inactive ID17 Auto Off Unpaired Bluetooth 20160729 10.32.47 T Running ID26:4 CPU Down Idle 20160729 10.32.47 T Running ID16:5 Anon 20160729 10.32.47 A OK ID26:4.1 CPU Down Idle.CPU 20160729 10.32.47 A OK ID16:5.1 Anon.Bluetooth 20160729 10.32.47 T ExitOK ID16:5 Anon 20160729 10.32.47 A OK ID26:4.2 CPU Down Idle.CPU 20160729 10.32.47 T ExitOK ID26:4 CPU Down Idle 20160729 10.32.48 E Stop ID0:0.0 TaskService |
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
REMINDER If you're having issues and want to submit a report (Logcat) please make sure you are reporting from the stock kernel, not a modified kernel. Modified kernels can break or fix, even improve things. It depends. I can't get a full clue of the issue when you're not running the original kernel. |