Database Develop

Install & run Android Marshmallow on the M7 - VanirAOSP ROM - UPDATED 4/24/16

There is a way to get Marshmallow on the HTC ONE Sprint M7, it's called VanirAOSP ROM. This is a great in most ways, and it's now my daily driver, but be very careful, I almost bricked my phone a few times in setting things up. Here are some tips from what I learned.
Installation instructions (learned from this video, other sources, and hard work):
1) Unlock bootloader.
2) Install custom recovery like TRWP. If you have an old version of TWRP, upgrade it using TRWP Manager or Flashify.
3) Download latest nightly ROM from http://www.emccann.net/nuclearmistake/VanirAOSPNightlies/m7spr/.
4) Download gapps. Biker57 suggests gapps from http://www.emccann.net/dho/5-Gapps/ as it's supposed to cause fewer force closes. I believe 60arm-DHO-GAPPs.zip is the correct file name.
5) Download SuperSU. Biker57 likes SuperSU v2.64 found here http://forum.xda-developers.com/showpost.php?p=64161125.
6) Copy all 3 downloads (in .zip format) to the phone (internal storage, like the TWRP folder)
7) Enter bootloader (volume down and power button), then select bootloader.
8) Backup the current ROM, just in case things go bad like they did for me.
9) From TWRP, enter advanced wipe and select system, data, cache, and dalvik cache. Do not select internal storage as you will lose your current backup and other zips if you do (there is an exception to this, as I did it, but I nearly bricked my phone). Now slide to wipe.
10) Go to install, and first select the ROM's zip. Then choose add more zips and select the gapps zip you downloaded. Next select SuperSU. Now slide to install.
11) Be patient during install.
12) Wipe dalvik cache.
13) Reboot to system (aka phone).
14) Enable Developer Options (if you want), by going to Settings->About and hitting Build Number many times until it's enabled.
Known issues and workarounds:
-Camera app force closes after taking a picture - the picture saves, so just reload Camera app. I've also had good luck using Z Camera then viewing the preview before hitting back to reenter the camera app.
-Stock dialer FCs randomly - Install another dialer app, like True Phone.
-Facebook and Facebook Messenger force closes - use mobile website, which actually isn't too bad, or try the instructions listed here.
-Flashlight turns off after 3 seconds - use the cameras flash instead.
Known issues with no good workarounds:
-FM Radio doesn't work.
-Bluetooth audio doesn't work for phone calls most of the time.
-Switching the battery mode causes the brightness to change randomly - don't ever switch away from balanced mode
Other stuff
-You can find more about the updates made to Vanir ROM here.
-It's risky to play around with the radio, but if you want to try it they are listed here.
-Intersted in supporting Varin, you can donate here.
Please let me know if I missed anything. And feel free to copy freely if it helps others.
***disclaimer - follow at your own risk. I'm not responsible for what might happen to your phone. This is only a cheat sheet, and it's for reference purposes only.***

First off, good tutorial. :good:
Vanir is a great ROM but this Sprint ROM still has a lot of bugs in it. I've used the first Vanir Marshmallow ROM to the most recent and a plethora of bugs have been squashed. But this ROM is still not DD ready, the camera , torch, gapps, browser and settings are broken. I am not saying this ROM is bad, just that its not fully ready yet. Depending on the dev, this rom should be DD ready in 2-3 weeks, they've been releasing more often now. Thank the developer if you know him but if you're the developer, thank you.
We should try to get the dev to see if they can put up a Vanir thread with change logs and the whole shebang.

I'm glad this thread was started and the OP was done well. I've been using this ROM for a while and thought I'd pass along my thoughts and what works for me.
This rom has become my daily driver after learning how to fix a couple of issues. After the latest update of 2/18 the biggest issues of not having a cellular/data connection has been corrected. The only issues that remain for me at least are the camera and Facebook issues. Although the camera does force close it does so for me at least after the picture is taken and saved so it's all good for me. The Facebook issues are corrected by deleting a file in both the Facebook and Messenger file.
The following method works for me without boot loops or any other issues and hopefully will work for you too. I flash these all at the same time loaded in the order listed and don't forget to make a backup before you start just in case.
1 - Flash the 2/18 nightly just like you would any rom http://www.emccann.net/nuclearmistak...ghtlies/m7spr/
2 - flash the gapps found here http://www.emccann.net/dho/5-Gapps/ and select the 60arm file near the bottom.
3 - flash Super SU 2.64 found here http://forum.xda-developers.com/showpost.php?p=64161125 There are new versions, but the 2.64 has continued to work for me.
4 - Reboot
As I said earlier this works for me and I've used this method with their roms successfully a number of times. Good Luck !!

Thank the developer if you know him but if you're the developer, thank you.
Click to expand...
Click to collapse
I'm not the developer, and I don't know the developer. But I would thank him or her if I could. I'm just interested in running Marshmallow on the M7. I will update the original post as I learn more so I can hopefully help others.

anotherfakeusername said:
I'm not the developer, and I don't know the developer. But I would thank him or her if I could. I'm just interested in running Marshmallow on the M7. I will update the original post as I learn more so I can hopefully help others.
Click to expand...
Click to collapse
If you need help with thread stuff I can help, we should start a new thread completely and give it more of a ROM thread look with known bugs, work a rounds and honest opinions on it.

biker57 said:
3 - flash Super SU 2.64 found here http://forum.xda-developers.com/showpost.php?p=64161125
Click to expand...
Click to collapse
Since my device is already rooted, would I be best off to install Super SU from the Play Store, then allow the app to upgrade through TWRP?

anotherfakeusername said:
Since my device is already rooted, would I be best off to install Super SU from the Play Store, then allow the app to upgrade through TWRP?
Click to expand...
Click to collapse
I'm not the developer either... Just a happy ROM user
There have been some issues with certain SU not working correctly with 6.0. You can try that but I would advise you to try a proven SU version.

is Snapchat also broken
Sent from my HTC One using Tapatalk

SuperSU 2.65 through TWRP 3.0.0-0
anotherfakeusername said:
Since my device is already rooted, would I be best off to install Super SU from the Play Store, then allow the app to upgrade through TWRP?
Click to expand...
Click to collapse
I didn't install it from the Play Store, I just flashed this version (2.65) through TWRP 3.0.0-0 and it's working as expected :good:

Hello,
Flashing SuperSU through recovery is a better way, atleast for Marshmallow ROMs now. I'm using latest beta version (SuperSU v2.67) without any issues. It can be found in official SuperSU thread here.
As of camera issues, you can use 3rd party camera apps like Camera FV-5, ProShot or etc. Of course they cost few bucks but worth it. Issue doesn't solve totally in this ROM but app doesn't force close, instead freezes for few sec and then works again.
This ROM is my DD and faced no major issues so far. What I'm mostly missing is fast charge feature in kernel otherwise normally it takes plenty of hours to fully charge.
Kindly note; you have to flash gapps provided by the ROM developer. Other gapps like open gapps will endup with FC.
Thanks...
Best Regards

CRACING said:
Kindly note; you have to flash gapps provided by the ROM developer. Other gapps like open gapps will endup with FC.
Click to expand...
Click to collapse
I flashed the gapps provided by the ROM developer, but the Gmail app is force closing due to "unknown issue with Google Play services.".
Then I tried using USB OTG to read my sd card reader in TWRP, but TWRP won't mount it. The issue started right after I booted the ROM the first time; I know because I installed the ROM from my sd card using USB OTG.
I still want this to be my daily driver, because the software is so much faster that 4.3, but I'm not convinced yet.

anotherfakeusername said:
I flashed the gapps provided by the ROM developer, but the Gmail app is force closing due to "unknown issue with Google Play services.".
Then I tried using USB OTG to read my sd card reader in TWRP, but TWRP won't mount it. The issue started right after I booted the ROM the first time; I know because I installed the ROM from my sd card using USB OTG.
I still want this to be my daily driver, because the software is so much faster that 4.3, but I'm not convinced yet.
Click to expand...
Click to collapse
Their list of gapps is rather long......which one did you use and did you flash it with the rom

You guys are right. I had to flash Super SU through TWRP (which was a challenge at first without using the sc card and OTG cable).

anotherfakeusername said:
You guys are right. I had to flash Super SU through TWRP (which was a challenge at first without using the sc card and OTG cable).
Click to expand...
Click to collapse
Correct, they have to be flashed with the rom as I mentioned in post 3.

anotherfakeusername said:
I flashed the gapps provided by the ROM developer, but the Gmail app is force closing due to "unknown issue with Google Play services.".
Then I tried using USB OTG to read my sd card reader in TWRP, but TWRP won't mount it. The issue started right after I booted the ROM the first time; I know because I installed the ROM from my sd card using USB OTG.
I still want this to be my daily driver, because the software is so much faster that 4.3, but I'm not convinced yet.
Click to expand...
Click to collapse
As of error "Unknown issue with Google Play service", go to Settings -> Apps -> Google Play service -> click 3 dot button in the corner -> Uninstall updates. This should solve the problem.
As of OTG, I didn't tested it but usb connection from TWRP to pc for file transfor works fine.
Btw; You are right, ROM is indeed fast.
biker57 said:
Their list of gapps is rather long......which one did you use and did you flash it with the rom
Click to expand...
Click to collapse
Use 60arm-DHO-GAPPs.zip
anotherfakeusername said:
You guys are right. I had to flash Super SU through TWRP (which was a challenge at first without using the sc card and OTG cable).
Click to expand...
Click to collapse
Even if you install supersu from playstore, it ask to reboots to recovery to install supersu. But before you accept to reboot, you'll have to enable root access to apps in developer options. Otherwise supersu cannot reboot or go into recovery.
Anyhow, instead of going through all these, I simply flash supersu zip from recovery.

CRACING said:
As of error "Unknown issue with Google Play service", go to Settings -> Apps -> Google Play service -> click 3 dot button in the corner -> Uninstall updates. This should solve the problem.
Click to expand...
Click to collapse
Android won't let me uninstall the Google Play service update. I get blocked when trying. It claims the app is an active device administrator, but it's not listed when I click manage device administrator.

anotherfakeusername said:
Android won't let me uninstall the Google Play service update. I get blocked when trying. It claims the app is an active device administrator, but it's not listed when I click manage device administrator.
Click to expand...
Click to collapse
Deselect Android Device Manager. Later when you uninstall the update, reselect Android Device Manager.

Deselect Android Device Manager. Later when you uninstall the update, reselect Android Device Manager.
Click to expand...
Click to collapse
That worked to fix my calendar syncing issues! Thanks!
Is not updating Google Play service going to cause other problems?

anotherfakeusername said:
That worked to fix my calendar syncing issues! Thanks!
Is not updating Google Play service going to cause other problems?
Click to expand...
Click to collapse
No such problems noticed here. I use Google calendar but Android calendar also works fine.
May be you should try rebooting or wait for some time and try resync.

CRACING said:
No such problems noticed here. I use Google calendar but Android calendar also works fine.
May be you should try rebooting or wait for some time and try resync.
Click to expand...
Click to collapse
The problem isn't using Google calendar, the problem is syncing Google calendar. I tried waiting, rebooting, re-adding my account, and everything else, but that didn't help.
Only downgrading Google Play services worked, and then Google calendar synced right away.
Thanks for the suggestions. Hopefully as they update the ROM it'll get resolved more fully.

[ROM] Chinese Marshmallow ROM for ZTE Axon Elite (A2016) international

I was able to install Chinese ZTE Axon Elite (A2015) Marshmallow rom to my international version of Axon Elite (A2016). Wifi, mobile data network and calling works. All Google apps are working too, Chinese rom has google services installed but those are needed to be activated by allowing them run in a background. Only Chinese and English languages available, but system is working in your local language after installing More Locale 2 from Google Play.
This ROM is not rooted, so you need to install Super User in TWRP right after installing this ROM.

Changes:
Added modem files (modem.b00-modem.b22, modem.mdt) from international B06 NON-HLOS.bin.
Minor build.prop changes (e.g. changed English as default language).
Removed stock recovery.
Added Google Play, Google Contact sync, Google Calendar sync, Google Gmail, Google Exchange sync, Google Phone, More Locale 2.
Removed all possible Chinese ZTE bloatware (over 200MB). I had to leave Mi-Assistant so that it can be used for allowing apps running in a background (example Google Play, Super SU).
[*]Added stock Marshmallow boot animation and removed boot sound.
Features:
Latest Google Security patch
MiFavor UI 4.0 with new themes and fonts
Applications Avatar (I have no idea what it is)
Toolbox - including compass, noise test, ruler, protractor, level meter, paintings
Calendar, shows weather for five next days
New Desktop backup and recovery capabilities
Long screenshots
More system Sleep functions
Smoother UI animations
SMS two-finger zoom
New power limits
Enhanced ZTE lock screen
...and some more which might not be useful in other countries than China (please check more details from: http://www.myzte.cn/thread-270646-1-1.html)
Working:
Wifi, mobile network, mobile data, bluetooth.
Fingerprint scanning.
Google Play services + other Google apps are working too (like Calendar, Contacts sync), but must be activated in Mi-Assistant Auto-start manager and allowing permissions in apps. Please see attached images for example.
Bugs and limitations:
NFC doesn't work.
Only Chinese and English languages, but it is possible to use More Locale 2 app (included in ROM) to change locale settings. Then apps (and part of the system) are working on your defined language. On my opinion it works just like in B06. More Locale requires Root access and executing ADB command (app shows the needed command) to change locale.
Download (B15M beta, updated 09.09.2016):
Mega https://mega.nz/#!cRAXTbqQ!UYTEzWb4AH5yZbcI4fK_09QBM5TYgvCCMMl1uTijetE
Based on the tip from @martas.vavra, I removed stock Chinese recovery so TWRP is not deleted after installing this rom.
Working Super user can be downloaded here https://cloud.tapatalk.com/s/57550023717f4/SuperSU_V2.62-3.zip. Thanks again @martas.vavra.
Quick steps:
(optional) Backup all apps by using ZTE own backup/restore app. It's then possible to restore apps after rom installation.
Install TWRP+root by using the method by @acer73: http://forum.xda-developers.com/zte-axon/development/zte-axon-elite-a2016-twrp-root-t3237760
Copy ZTE_Axon_Elite_A2016_unofficial_B15M_09092016 to SD card.
Boot to TWRP recovery.
Do full backup in TWRP.
Do factory reset in TWRP.
Install ZTE_Axon_Elite_A2016_unofficial_B15M_09092016 from SD card in TWRP. NOTE! Status bar is not progressing at all when installation is ongoing! Don't panic. Just wait, it will complete.
Install Super User .zip again.
Reboot. Please be patient, first boot will take minutes to complete.
After first boot is complete, start Mi-Assistant and enable apps (Google Play, Google Contacts, SuperSU... etc) in Auto-run Manager.
Enable app permissions for Calendar, Contacts, Phone, SMS, Storage in Settings -> Apps, App permissions.
Reboot.
(optional) Restore apps by using ZTE own backup/restore app. ZTE has removed Backup/restore app but here's download link for backup/restore app from B12M: https://mega.nz/#!hZQ2HTbb!IvTJu17kjibXGSJBsRUutz0wwPZL0XlruDVAyExqsC8
Note to users: I'm not responsible if you brick your phone, so please be careful!

Thank you for your efforts! Great to hear that there are only minor bugs. :fingers-crossed:
Leaves me thinking about why ZTE does not provide this update by themselves if there are only few things needed to be adjusted in order to make this work...

There is a CM 13 for chinese Axon http://www.myzte.cn/thread-263527-1-1.html It should work

martas.vavra said:
There is a CM 13 for chinese Axon http://www.myzte.cn/thread-263527-1-1.html It should work
Click to expand...
Click to collapse
I am afraid it does not work, as @brainmaster already tried booting it - without success.
Please refer to his post here:
http://forum.xda-developers.com/showpost.php?p=66497035&postcount=5

This is great! Thanks a lot
GalaxyFan88 said:
I am afraid it does not work, as @brainmaster already tried booting it - without success.
Please refer to his post here:
http://forum.xda-developers.com/showpost.php?p=66497035&postcount=5
Click to expand...
Click to collapse
But maybe it will work using the same method the opener of the thread used! (aka replacing the radio). I don't know though...

Dapalm said:
This is great! Thanks a lot
But maybe it will work using the same method the opener of the thread used! (aka replacing the radio). I don't know though...
Click to expand...
Click to collapse
You can read here. Its not just about the radio partition.

Like already mentioned, when trying to add PIN lock, settings will force close. I also compared international B05 and Chinese marshmallow rom files and noticed differences on fingerprint modules and apps, so I believe we are out of luck here.

suunnittelija said:
Like already mentioned, when trying to add PIN lock, settings will force close. I also compared international B05 and Chinese marshmallow rom files and noticed differences on fingerprint modules and apps, so I believe we are out of luck here.
Click to expand...
Click to collapse
I think that copying that files, modules and apps would be possible, from one to another, won't you? I have no idea of how to doing it, but maybe it is easy for someone experimented in rom's modding.
@suunnittelija how about the batttery life?

Mononitoto said:
how about the batttery life?
Click to expand...
Click to collapse
Unfortunately I don't know, because I was testing this rom just half day. On that time I didn't notice battery drain. I returned back to B06 because my phone has to be password protected and I just can't live anymore without fingerprint scanner.

suunnittelija said:
Unfortunately I don't know, because I was testing this rom just half day. On that time I didn't notice battery drain. I returned back to B06 because my phone has to be password protected and I just can't live anymore without fingerprint scanner.
Click to expand...
Click to collapse
What would be necessary to do, to port fingerprint scanner etc to this rom?

Mononitoto said:
What would be necessary to do, to port fingerprint scanner etc to this rom?
Click to expand...
Click to collapse
Probably it's nothing to do with fingerprint scanner. I checked logcat file and settings will force close before that. Settings will force close right after trying to enable PIN code lock.
Code:
FATAL EXCEPTION: AsyncTask #3
Process: com.android.settings, PID: 8191
java.lang.RuntimeException: An error occurred while executing doInBackground()
at android.os.AsyncTask$3.done(AsyncTask.java:309)
at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:354)
at java.util.concurrent.FutureTask.setException(FutureTask.java:223)
at java.util.concurrent.FutureTask.run(FutureTask.java:242)
at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:234)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
at java.lang.Thread.run(Thread.java:818)
Caused by: java.lang.NullPointerException: Attempt to read from field 'int com.android.server.LockSettingsStorage$CredentialHash.version' on a null object reference
With cyanogenmod there has been similar issues with some devices and error has been caused by wrong baseband (https://forum.cyanogenmod.org/topic/118507-cant-enable-screen-lock/?page=3), which means that users have not been updating the baseband before updating the latest version of cyanogenmod. This might be the same issue, I used lollipop baseband to get this work.

I created new version based on latest Chinese B10M (previous was B09M):
https://mega.nz/#!1QgxVbza!9S0ugYNp3QmJvPxzNvcb2XB_YCsHygf3NPdohVisSg4
I don't know what kind of changes they have done for this version, but in our A2016 it has the same issues than previous version (security settings force closing etc.).

suunnittelija said:
I created new version based on latest Chinese B10M (previous was B09M):
https://mega.nz/#!1QgxVbza!9S0ugYNp3QmJvPxzNvcb2XB_YCsHygf3NPdohVisSg4
I don't know what kind of changes they have done for this version, but in our A2016 it has the same issues than previous version (security settings force closing etc.).
Click to expand...
Click to collapse
Continue your great work !

How to restore 5.0.1 ?

kacsa105 said:
How to restore 5.0.1 ?
Click to expand...
Click to collapse
Easiest and the best way is to take full twrp backup first before installing this rom. Then it can be restored in twrp and phone is restored to the state it was before.
If backup is not made, then stock B05 update.zip needs to be installed in recovery (in stock or twrp).
@kacsa105 pointed out that adb root method doesn't work anymore with B10M. I didn't notice it because I installed recovery + supe su in right after I installed B10M in twrp.
If you are now in stock Chinese recovery, then follow these steps to restore stock B05 in stock (Chinese) recovery:
1. download B05 from:
http://download.ztedevice.com/UpLoadFiles/product/643/6549/soft/2016042111364202.zip. Unzip it and find update.zip
2. place update.zip to phone internal SD card
3. shut down your phone
4. reboot to recovery: Press and hold Volume up button then Press and hold Power button. When ZTE logo appears, stop pressing Power button but continue pressing Volume up until it goes to recovery.
5. It should be now in stock Chinese recovery. You need to use volume up/down buttons and move it to the selection where is written something on Chinese but with letters SD (which means your internal SD card). Press Power button to select it.
6. Use vol down to navigate until you see update.zip and choose it with power button. If I remember correctly, you need to confirm Yes (it should be in English if I remember it correctly).
7. After it has been updated, recovery asks something again in Chinese. Don't change the selection, just use power button to select what it proposes, and system will boot.
Just wait until your phone boots back to system. If it keeps crashing, just power it down and reboot again to recovery. Recovery should be in English now. Then clear cache and dalvik (or was it factory reset?) and boot to system again.

Google play crashed, when download big data games. Solution pls

Are known any major issues with this ROM? Tired of Mi-sh*t, I'm thinking about install TWRP, make a backup and later this or CM. Is worth it?

hik4ru said:
Are known any major issues with this ROM? Tired of Mi-sh*t, I'm thinking about install TWRP, make a backup and later this or CM. Is worth it?
Click to expand...
Click to collapse
I'm not using this rom because PIN lock screen and fingerprint doesn't work (CM has these issues too). Then it has some China specific in the settings. Be careful when installing this B10 rom, you need to install twrp recovery + root again in recovery right after flashing this rom. Otherwise you will loose root and recovery is replaced by stock Chinese.
On my opinion this is not worth of flashing, you don't even notice major differences. In some devices Marshmallow has improved performance and battery life, but I didn't notice any difference. I'm using stock B06 (5.0.2) with xposed (+some modules installed) and I'm happy with it.
Of course this rom is fun to try if you want to test how Marshmallow will look in our device.

suunnittelija said:
I'm not using this rom because PIN lock screen and fingerprint doesn't work (CM has these issues too). Then it has some China specific in the settings. Be careful when installing this B10 rom, you need to install twrp recovery + root again in recovery right after flashing this rom. Otherwise you will loose root and recovery is replaced by stock Chinese.
On my opinion this is not worth of flashing, you don't even notice major differences. In some devices Marshmallow has improved performance and battery life, but I didn't notice any difference. I'm using stock B06 (5.0.2) with xposed (+some modules installed) and I'm happy with it.
Of course this rom is fun to try if you want to test how Marshmallow will look in our device.
Click to expand...
Click to collapse
How to flash recovery in recovery? I have tried to flash it via ADB, but there was stock recovery after reboot. And when I flash supersu zip the system won't boot.
Odesláno z mého ZTE A2016 pomocí Tapatalk

suunnittelija said:
I'm not using this rom because PIN lock screen and fingerprint doesn't work (CM has these issues too). Then it has some China specific in the settings. Be careful when installing this B10 rom, you need to install twrp recovery + root again in recovery right after flashing this rom. Otherwise you will loose root and recovery is replaced by stock Chinese.
On my opinion this is not worth of flashing, you don't even notice major differences. In some devices Marshmallow has improved performance and battery life, but I didn't notice any difference. I'm using stock B06 (5.0.2) with xposed (+some modules installed) and I'm happy with it.
Of course this rom is fun to try if you want to test how Marshmallow will look in our device.
Click to expand...
Click to collapse
What modules are you using with Xposed?
Enviado desde mi ZTE A2016 mediante Tapatalk

CM 14.1 sys profiles glitch, black screen with Notif, can't reach settings / launcher

I have been running CM 14.1 20161219 since that date, with few problems. Sometimes I enable an cm automobile system profile in the settings menu so I can easily get on the phone while driving or otherwise.
Yesterday I turned it on and forgot about it, and today I rebooted my phone while charging and I get a black screen with the <| back button on the bottom and my notifications and quick settings visible on the top. I can receive calls and toggle wifi and what not, but I cant reach the settings menu to switch back to the default profile (or the launcher for that matter). I have rebooted to recovery fine, but I dont want to reflash unless its necessary as it messes up my Authenticator settings on Steam, google, etc. Usually I turn those off before flashing new ROMs.
Hopefully there is a simple fix I can do from fastboot or recovery...
Thank you for any help.
- b

cm14 is dead; find a different rom...

wase4711 said:
cm14 is dead; find a different rom...
Click to expand...
Click to collapse
Yeah. I installed it before it was dead, and when I installed it it was working fine for a month or more ... until today. I was waiting for a couple revisions before I installed Lineage OS.
Regardless, when upgrading ROMS there are several steps I take beforehand that would benefit from fixing this bug first.
* backing up apps via TB
* Turning off steam multifactor in steam app
* Turning off google authenticator 2 factor temporarily
* backing up some of my data, just in case
* Trying to upgrade to Lineage OS using experimental dirty flash method
* Upgrading TWRP via the app before flashing my next ROM
* others
I ended up trying to flash LIneage OS in the 2 part methon of i.) flash experimental ROM, ii.) flash Lineago OS nightly. That didnt fix the problem with the Launcher and settings not working. And I was unable to do any of my pre-upgrade checklist.
I think there was something was messing with the Pixel Launcher, and I ended up whiping and reflashing the normal way. This was a real problem because I lost the ability to use my phone 3 hours before requiring Navigation to meet family across town. Not to mention having phone call access. I hope I don't randomly have this same problem with LIneage OS now since I was unable to solve... I will stop using that system profiles feature for the time being.

Fingerprint sensor not working

Hi my A2 phone is on latest Android one pie (stock, no root, bootloader locked), its fingerprint not working since last night, and option for setting finger print disappeared... don't know why.
Any solution for this guys.

mralam92 said:
Hi my A2 phone is on latest Android one pie (stock, no root, bootloader locked), its fingerprint not working since last night, and option for setting finger print disappeared... don't know why.
Any solution for this guys.
Click to expand...
Click to collapse
Since it's stock ROM, try wiping cache from recovery. If that doesn't work, then factory reset ? (Backup data !)

Tianhe said:
Since it's stock ROM, try wiping cache from recovery. If that doesn't work, then factory reset ? (Backup data !)
Click to expand...
Click to collapse
Nothing helped, is it possible that OS is stop considering that FP hardware is exist because as per system tester app downloaded from play store it says no FP found in the device.

mralam92 said:
Nothing helped, is it possible that OS is stop considering that FP hardware is exist because as per system tester app downloaded from play store it says no FP found in the device.
Click to expand...
Click to collapse
Did you face the problem after updating the device or installing any app ?
Try booting into safe mode and check FP to rule out any interference by 3rd party app

Tianhe said:
Did you face the problem after updating the device or installing any app ?
Try booting into safe mode and check FP to rule out any interference by 3rd party app
Click to expand...
Click to collapse
Have no idea there are no extra apps apart from google...

YouTube app keeps getting enabled automatically

I have a fully updated stock 4/64 A2 with YouTube disabled (because I prefer NewPipe). Until a week or so ago, I did not have any problems keeping it disabled.
Now, it gets automatically enabled after an indeterminate amount (minutes? hours?) of time. I clear Storage for the app, disable it (whereby it is replaced by the factory version), and after some time it shows up in my app drawer and Play Store 'updates available' list again!
Can someone please help me exorcise the ghost from my machine?

Yeah this problem is annoying. Try disabling Google Partners Setup and Google One Time Init. So far it works for me

TechnoSparks said:
Try disabling Google Partners Setup and Google One Time Init.
Click to expand...
Click to collapse
Thanks for the response, but it didn't work for me. It stayed disabled for one whole day, but then came right back a few minutes ago.
Is there anything else I should try other than patiently waiting for official LineageOS 17?

sclip said:
I have a fully updated stock 4/64 A2 with YouTube disabled (because I prefer NewPipe). Until a week or so ago, I did not have any problems keeping it disabled.
Now, it gets automatically enabled after an indeterminate amount (minutes? hours?) of time. I clear Storage for the app, disable it (whereby it is replaced by the factory version), and after some time it shows up in my app drawer and Play Store 'updates available' list again!
Can someone please help me exorcise the ghost from my machine?
Click to expand...
Click to collapse
Root your phone and delete it from system.

sclip said:
Thanks for the response, but it didn't work for me. It stayed disabled for one whole day, but then came right back a few minutes ago.
Is there anything else I should try other than patiently waiting for official LineageOS 17?
Click to expand...
Click to collapse
Edit: I just remembered you are waiting for LOS. Means you are most probably do not care about system partition modification. If that is the case, the suggestion above was right. Get root, then Delete it from /system/app
That is one persistent ghost. Are you rooted with Magisk? I could make a simple module that effectively makes the YouTube app directory under /system become empty

TechnoSparks said:
...
Click to expand...
Click to collapse
I'm completely stock, fully updated (no BL unlock or root, etc.). I was hoping to enjoy the benefits of the Android One program (no Xiaomi/Google bloatware, timely security updates) until [OFFICIAL] LOS comes out (mostly because I really like PrivacyGuard and AFWall+ (with root)).
For some reason, the official version of LOS16 didn't come out at all; I'm eagerly awaiting @rcstar6696 to whip up official LOS17.
In addition to Google Partners Setup and Google One Time Init, I have also disabled the two Android Setup apps. Let's hope this one does the trick. I'll report back if it doesn't.
EDIT: So that didn't work; the YouTube app is back again. The two Android Setup apps are showing as enabled as well.

Well at this point i recommend for you to unlock BL and whip Magisk to the stock ROM. Enable systemless hosts in magisk, then I will give you the detailed steps & files to put in the systemless hosts directory. I will get back to you as soon as i could
Having BL unlocked and Magisk installed won't hurt your Android One experience (i am using the same setup). However, updating over OTA would be a bit hassle as you will have to Restore Images from Magisk manager, update, and install Magisk to the other slot. A mild inconvenience, but you get to retain the original device's software and feel

TechnoSparks said:
…
Click to expand...
Click to collapse
Thanks for the offer to help :good:, but I think I'll mess around with the phone once stable Android 10 shows up for it, be it stock or LOS.
In the meantime, I have hidden the YouTube icon from my app drawer. Out of sight, out of mind. Take that, Google!

I use this method, woks without root
https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/amp/

Lautaro Mondaca said:
I use this method, woks without root
https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/amp/
Click to expand...
Click to collapse
This is really cool, thanks for sharing!
---------- Post added at 03:09 AM ---------- Previous post was at 03:04 AM ----------
sclip said:
Thanks for the offer to help :good:, but I think I'll mess around with the phone once stable Android 10 shows up for it, be it stock or LOS.
In the meantime, I have hidden the YouTube icon from my app drawer. Out of sight, out of mind. Take that, Google!
Click to expand...
Click to collapse
Okay! [emoji16]

Lautaro Mondaca said:
…
Click to expand...
Click to collapse
Thanks a lot, I used this method a couple of times to debloat MIUI and completely forgot about it! Begone, YouTube and Chrome!