Database Users

Fingerprint menu disappeared

Hi, I have recently installed COS 13 SNAPSHOT build and was working fine. I have restarted my phone and got stuck in a boot loop so I have installed latest COS 13 nightly after which fingerprint menu disappeared totally . I have installed turbo ROM after that (after wiping cos nightly) still no fingerprint menu. Anyway to restore the get it working .

getmmg said:
Hi, I have recently installed COS 13 SNAPSHOT build and was working fine. I have restarted my phone and got stuck in a boot loop so I have installed latest COS 13 nightly after which fingerprint menu disappeared totally . I have installed turbo ROM after that (after wiping cos nightly) still no fingerprint menu. Anyway to restore the get it working .
Click to expand...
Click to collapse
Just some ideas I have. Did you install mm firmware?
Otherwise, I have had FP menu disappear twice in the past. Both times it was after my FP sensor was exposed to some water, so essentially it was compromised. Maybe yours was damaged? I tried wiping and flashing and reflashing different ROMs and firmware and it came back about a week later. I believe the FP sensor finally dried and the water was gone from in there so it worked again. So I think when the sensor is damaged it is removed from settings as if it is not there.
Hope this helps.

Try cleaning credentials, maybe this helps.

JonnyAw said:
Just some ideas I have. Did you install mm firmware?
Otherwise, I have had FP menu disappear twice in the past. Both times it was after my FP sensor was exposed to some water, so essentially it was compromised. Maybe yours was damaged? I tried wiping and flashing and reflashing different ROMs and firmware and it came back about a week later. I believe the FP sensor finally dried and the water was gone from in there so it worked again. So I think when the sensor is damaged it is removed from settings as if it is not there.
Hope this helps.
Click to expand...
Click to collapse
What is mm firmware? I haven't installed it. I have installed twrp and flashed cos nighties on top.

getmmg said:
What is mm firmware? I haven't installed it. I have installed twrp and flashed cos nighties on top.
Click to expand...
Click to collapse
MM firmware is the driver package for marshmallow (android 6.0), it allows you to use fingerprint sensor. On the list of things to install for turbo rom Ordenkreiger did not put that you have to install it but it is required for fp sensor. If you check other cm13 based roms here most will be explicit about installing it.
Here is the link for the firmware for our device, just flash it before installing the roms and FP will work: https://www.androidfilehost.com/?fid=24533103863141329
It only needs to be installed once and then you never worry about it when installing other marshmallow roms. That is the same link given in other threads for our Zuk. Hope it works!

Tried flashing mm-firmware but still no fingerprint menu in setting.

does this works for nougat?
JonnyAw said:
MM firmware is the driver package for marshmallow (android 6.0), it allows you to use fingerprint sensor. On the list of things to install for turbo rom Ordenkreiger did not put that you have to install it but it is required for fp sensor. If you check other cm13 based roms here most will be explicit about installing it.
Here is the link for the firmware for our device, just flash it before installing the roms and FP will work: https://www.androidfilehost.com/?fid=24533103863141329
It only needs to be installed once and then you never worry about it when installing other marshmallow roms. That is the same link given in other threads for our Zuk. Hope it works!
Click to expand...
Click to collapse
or any alternative for nougat..

Goku027 said:
or any alternative for nougat..
Click to expand...
Click to collapse
xda is full of Zuk fingerprints problems.
it's a hardware problem. Most of members here suffer from damaged fingerprint.

Try nuclear ROM 1.0.1 beta no issue with finger print and calling no bug for zuk z1

Goku027 said:
or any alternative for nougat..
Click to expand...
Click to collapse
I serch in google and found this file for Nougat:
https://www.androidfilehost.com/?fid=745425885120705241
I try it (I had the same problem) and i FIXED it!!!
Simply download> Reboot in Recovery and Flash it.
:fingers-crossed:

thanks..it worked.
scraptchatella said:
I serch in google and found this file for Nougat:
https://www.androidfilehost.com/?fid=745425885120705241
I try it (I had the same problem) and i FIXED it!!!
Simply download> Reboot in Recovery and Flash it.
:fingers-crossed:
Click to expand...
Click to collapse
now my fingerprint sensor is back.

scraptchatella said:
I serch in google and found this file for Nougat:
I try it (I had the same problem) and i FIXED it!!!
Simply download> Reboot in Recovery and Flash it.
:fingers-crossed:
Click to expand...
Click to collapse
Thanks a lot, worked for me too, after flashing lineage os from cos 12 my finger print option disappeared too. Luckily I found this now every thing works again!

I had the same problem. And tried all the available options like updating mm firmware, Going back to COS 12.1, CM 13, LOS 14.1.... Nothing really worked. For some time finger print worked in COS12.1 and after a while it malfunctioned, and vibrated continuously. Then I have taken to the service center. There they have replaced the whole screen.( dont know the exact reason and the person delivered the mobile is too noob to ask). So what I mean is it is a hard issue upto my knowledge. If your mobile is covered in warranty, give it a try..

This file only makes a penguin logo appear when I boot my rr ROM. Did not provide the finger print option. Hope this does not mess with my phone. Is there any way to remove this thing I flashed?

lineage-14.1-20171031
I cannot find the fingerprint menu. Where should it be? The setup was interrupted and now I cannot find it.

Radhouene90 said:
xda is full of Zuk fingerprints problems.
it's a hardware problem. Most of members here suffer from damaged fingerprint.
Click to expand...
Click to collapse
Well my mic also not works in case i am recording but when i receive a call and put it on loudspeaker it works fine...
Anyone can tell what is that problem??

highdude said:
Well my mic also not works in case i am recording but when i receive a call and put it on loudspeaker it works fine...
Anyone can tell what is that problem??
Click to expand...
Click to collapse
this could be a software problem, what ROM are you using ?
As for my fingerprint, i changed it , it's working ..

Radhouene90 said:
xda is full of Zuk fingerprints problems.
it's a hardware problem. Most of members here suffer from damaged fingerprint.
Click to expand...
Click to collapse
Got my fingerprint working with the Dead Unicorns ROM, while it didn't work with lineage and nuclea.

lg-optimus said:
Got my fingerprint working with the Dead Unicorns ROM, while it didn't work with lineage and nuclea.
Click to expand...
Click to collapse
i tried it but id does not worked , so i bought a new one from ebay

Radhouene90 said:
this could be a software problem, what ROM are you using ?
As for my fingerprint, i changed it , it's working ..
Click to expand...
Click to collapse
I haven't changed my rom yet
My phone isn't even rooted
---------- Post added at 11:41 AM ---------- Previous post was at 11:40 AM ----------
highdude said:
I haven't changed my rom yet
My phone isn't even rooted
Click to expand...
Click to collapse
And i wanna root my phone any suggestions how to do that

Stability of latest update

Hi guys,
I'm still on 8.0 and wonder is it is worth to go to 8.1.0 October update now.
How stable is it?

I have no problems whatsoever. Using latest - october.
Sent from my Mi A1 using XDA Labs

Issue of charging . Device doesn't charge , have to restart everytime when you plug charger

technoatul10 said:
Issue of charging . Device doesn't charge , have to restart everytime when you plug charger
Click to expand...
Click to collapse
Not a global issue as no one else has reported such similar problem.

technoatul10 said:
Issue of charging . Device doesn't charge , have to restart everytime when you plug charger
Click to expand...
Click to collapse
Never happened to me.

Thanks guys
Rooted+magisk users, everything working well on stock rom?

October update is 100% stable, no charge issue.

I guess I need to reset my device then

Tbh, I think 8.1 is more stable than any 8.0 update! ?

More stable and faster than 8.0

October 2018 works fine for me with Magisk installed. No issues to report.

Only issue I've been having is with my GPS not getting a stable signal but it's been like that since the September update and I didn't get the impression that a lot of people have been dealing with the issue. Not sure what to do, if it's a hardware issue I could send it in for repair but I'd be out of a phone for a pretty long time.
Everything else in 8.1 has been very good. Very stable, decent battery life and overall smoother than it was on 8.0.

People were complaining about the GPS since the July or August update but so far I haven't had any issues with the GPS. Did hours of driving last week with the phone in the dashboard with google maps giving directions and it worked well.

Everything is fine but GPS.

ludditefornow said:
October 2018 works fine for me with Magisk installed. No issues to report.
Click to expand...
Click to collapse
May I know which patched boot.img you used to root and install magisk?
The one I found will remove root after each reboot. It gets worse when incompatible with the latest fingerprint unlock magisk module (black screen after first boot)

Raven_Yen said:
May I know which patched boot.img you used to root and install magisk?
The one I found will remove root after each reboot. It gets worse when incompatible with the latest fingerprint unlock magisk module (black screen after first boot)
Click to expand...
Click to collapse
I don't use a patched boot.img. I use standard boot.img.
I then booted into TWRP and loaded Magisk. I do not install TWRP. I then use this method https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation when I update.

December images up

I just noticed December's images are up for og pixel xl and pixel

Zehlek said:
I just noticed December's images are up for og pixel xl and pixel
Click to expand...
Click to collapse
Eh Zehlek, I am trying to update from the August Pie build. Do you think just flashing the system.img and vendor.img would work (like it was in the Nexus days)? I can't really be bothered going through the re-rooting .
Thanks.

Anyone who has updated,,,have you noticed anything with the Dec update? Or just another security patch?

Archangel said:
Anyone who has updated,,,have you noticed anything with the Dec update? Or just another security patch?
Click to expand...
Click to collapse
Just the new search bar with the Google Assistant link and drawing program hidden in the Easter Egg.

jaytv said:
Just the new search bar with the Google Assistant link and drawing program hidden in the Easter Egg.
Click to expand...
Click to collapse
I heard for other devices (Pixel 2) the UI (At least on the home screen) has been much more fluid with the updated Pixel launcher. I would agree with this on the Pixel XL too now...I have far less stutters using navigation gestures and swiping right to go to the Discover feed. Good update!

This is really random, but after updating anyone else having an issue with the screen turning off when a right to far left of the screen is performed? Noticed it when I was swiping a word from far right of the screen to far left, and it turns the screen off. Does the same thing outside of the app. Checked the Gestures settings and couldn't find anything relevant. (Wiped data on upgrade) Any suggestions are appreciated!

chinesecooler said:
Eh Zehlek, I am trying to update from the August Pie build. Do you think just flashing the system.img and vendor.img would work (like it was in the Nexus days)? I can't really be bothered going through the re-rooting .
Thanks.
Click to expand...
Click to collapse
I'm not 100% sure I would ask @razorloves he is the expert on this one

chinesecooler said:
Eh Zehlek, I am trying to update from the August Pie build. Do you think just flashing the system.img and vendor.img would work (like it was in the Nexus days)? I can't really be bothered going through the re-rooting .
Thanks.
Click to expand...
Click to collapse
doubt it. you need the kernel too (boot.img). then you'd need to reflash twrp and magisk.
you also need new radio & bootloader img's.
what's so hard about re-rooting? you just have to flash twrp and magisk, right?

razorloves said:
doubt it. you need the kernel too (boot.img). then you'd need to reflash twrp and magisk.
you also need new radio & bootloader img's.
what's so hard about re-rooting? you just have to flash twrp and magisk, right?
Click to expand...
Click to collapse
Yeah figured that out. Initially I just flashed the two and it boot looped. Had to do the lot and reroot. :/

Archangel said:
Anyone who has updated,,,have you noticed anything with the Dec update? Or just another security patch?
Click to expand...
Click to collapse
Before the update, I had to manually enter my apn, but After December update, all my apn automatically work. I noticed better signal reception too. I don't know if it's the update related.

I liked it,
Rebooted after initial setup and fastbooted into twrp...
Installed king kernel 3.16
Installed magisk.
Perfection, battery lasts forever now. 5.5h sot is an daily thing, 3.5-4h if streaming pandora

Beta 5/RC1 of Q on deck!

Beta 5/RC1 of Q is officially in the on-deck circle for registered devices; I'm downloading it now for my 3a. (OTA). The big attraction for me - dark mode changes (I enabled dark mode with the previous beta).

PGHammer said:
Beta 5/RC1 of Q is officially in the on-deck circle for registered devices; I'm downloading it now for my 3a. (OTA). The big attraction for me - dark mode changes (I enabled dark mode with the previous beta).
Click to expand...
Click to collapse
Let us know if it boots without fuss

SketchyStunts said:
Let us know if it boots without fuss
Click to expand...
Click to collapse
Working fine here. My 3a restarted once after first boot but it's working fine now

What Issues?
baddesthad said:
Working fine here. My 3a restarted once after first boot but it's working fine now
Click to expand...
Click to collapse
No issues at all; just one quibble - no dark-mode launch animation (even though systemwide dark mode is still active, as I set it with beta 4). And I'm admitting it's a quibble. (It should be present if you have systemwide dark mode set.)

anyone know how to root on beta5??

jayxiao171735 said:
anyone know how to root on beta5??
Click to expand...
Click to collapse
With the latest Magisk Canary, I guess. Haven't tried it myself because latest Pie security patch works like a charm for my needs.

baddesthad said:
Working fine here. My 3a restarted once after first boot but it's working fine now
Click to expand...
Click to collapse
I would double check you didn't fall back to DP4. A reboot means it might have failed to boot to DP5 and falled back to DP4 slot.

Uzephi said:
I would double check you didn't fall back to DP4. A reboot means it might have failed to boot to DP5 and falled back to DP4 slot.
Click to expand...
Click to collapse
I was on the stock July update (phone is a week old) and this is the first developer preview update I received. The build number I have is below

Where is everyone getting beta 5? I only have beta 4 available.

stevew84 said:
Where is everyone getting beta 5? I only have beta 4 available.
Click to expand...
Click to collapse
OTA here

Uzephi said:
OTA here
Click to expand...
Click to collapse
Are you already on Q4? That update is small.
I'm flashing the June stock image since the July one has an issue with the Q OTA.

stevew84 said:
Are you already on Q4? That update is small.
I'm flashing the June stock image since the July one has an issue with the Q OTA.
Click to expand...
Click to collapse
That's where I screwed up initially. Pie with July security patch... Took OTA beta 4 which had June's patch. This was withing a hour of buying it lol.

SketchyStunts said:
That's where I screwed up initially. Pie with July security patch... Took OTA beta 4 which had June's patch. This was withing a hour of buying it lol.
Click to expand...
Click to collapse
I went to the June image and now there is no Q beta available...even though I'm enrolled in the beta program. Weird. I've had the beta previously.
EDIT: got it. thanks.

stevew84 said:
Are you already on Q4? That update is small.
I'm flashing the June stock image since the July one has an issue with the Q OTA.
Click to expand...
Click to collapse
Yes, I went from Q4 to Q5. Needed a reboot as update was stuck at optimizing apps for over 30 minutes.

OTA in Both Caases
Uzephi said:
Yes, I went from Q4 to Q5. Needed a reboot as update was stuck at optimizing apps for over 30 minutes.
Click to expand...
Click to collapse
Beta 4 (via OTA) from default Pie two days ago, and beta 5/RC1 (from beta 4) today (also via OTA). I don't have the proper cables to connect to my PC (all my cables with the proper end at the PC end, can't connect to my 3a - because they are - at the phone end - USB-B - not USB-C; if I had even a USB-to-USB cable, I would not be in this pickle).

PGHammer said:
Beta 4 (via OTA) from default Pie two days ago, and beta 5/RC1 (from beta 4) today (also via OTA). I don't have the proper cables to connect to my PC (all my cables with the proper end at the PC end, can't connect to my 3a - because they are - at the phone end - USB-B - not USB-C; if I had even a USB-to-USB cable, I would not be in this pickle).
Click to expand...
Click to collapse
So basically you like to live dangerously....I can respect that :good:

Actually.....
SketchyStunts said:
So basically you like to live dangerously....I can respect that :good:
Click to expand...
Click to collapse
I live more dangerously testing Windows (which I have been doing since Windows 95 - the original one). Rather amusingly, I've been more conservative (if not downright chicken) when it comes to the phone side of operations - mostly because I've had to. Remember - until Q, Android beta testing was a lot more closed than the same for Windows. Heck - even with Q, where is the most OPEN portion of the testing program? Easily explained - the Pixels. Every Pixel ever built - from the first one to the current one - can- and could - opt-in to it. Problem - until now, Pixels were chained to a limited set of providers. (In the United States, a grand total of two - Verizon and Google itself (via Fi).) The 3a and 3aXL changed that - as long as you had a nano-SIM, and $479USD (at worst), you could get a Pixel and activate it. I'm not on Verizon - I'm not on a Big Four carrier, either. What carrier am I on? Tracfone - an MVNO. (Tracfone uses the towers of all of the Big Four carriers; with the S7 - the phone my SIM came out of, I used the towers of T-Mobile AKA the Uncarrier.) Since I've had the opportunities, I've paid it back, and paid it forward (when and where possible). The Pixel 3a makes it possible - so why not? However, I don't recommend it due TO that it lets me pay it forward - quite aside from that, the Pixel 3a - merely as a mainstream/midrange user - is the best-used and best-supported such new phone. THAT is why I recommend it.
#teampixel #whatcamera?

xFirefly93 said:
With the latest Magisk Canary, I guess. Haven't tried it myself because latest Pie security patch works like a charm for my needs.
Click to expand...
Click to collapse
sorry, this method seems doesn't work, when I use Magisk canary to create the patched boot img, it said that failed to build....any solutions for that?

jayxiao171735 said:
sorry, this method seems doesn't work, when I use Magisk canary to create the patched boot img, it said that failed to build....any solutions for that?
Click to expand...
Click to collapse
Ask John over at Twitter.

jayxiao171735 said:
sorry, this method seems doesn't work, when I use Magisk canary to create the patched boot img, it said that failed to build....any solutions for that?
Click to expand...
Click to collapse
I posted this in another thread you asked this question in, but I figured it would be good to post here to for the benefit of others.....
I found this on the latest Magisk Canary build thread.
tysj said:
Problem they're having is that it isn't outputting the patched boot.img as it says it is. I'm running to the same issue on my Pixel 3.
EDIT:
Somehow got it to work. Uninstalled Magisk Manager, re-downloaded again from the OP, decided to update Magisk Manager from the app, then tried patching the boot.img again which finally work. Flash the patched_boot in fastboot and all is well.
Click to expand...
Click to collapse
So it sounds like there is so issue with the Magisk Manager - either the user wasn't really on the latest build, or there is some sort of permission issue with writing files, etc. But it seems that reinstalling the manager fixes the issue and you should be able to get Magisk to modify the stock boot.img file as normal.

just got a new 10 update?..

Anybody install this yet?

jimlightner said:
Anybody install this yet?
Click to expand...
Click to collapse
I have been running 10.3 for a while and I am t-mobile locked but converted to International. Everything is smooth other than Gpay is not working and Playstore is not certified. This is because I am t-mobile variant.

jimlightner said:
Anybody install this yet?
Click to expand...
Click to collapse
Yes! I've been installed for a few weeks. All perfect.
Enviado desde mi ONEPLUS A6013 mediante Tapatalk

I too got a push update notification. My question is this, can I update through the regular method as it's a full update or do I need to flash?
Originally t mobile variant I rebranded to international and sim unlocked. Also flashed to 9.0.17 and rooted via magisk. Any insight would be appreciated as I have heard improper updating can result in a brick. Thanks in advance

BoSavageYo said:
I too got a push update notification. My question is this, can I update through the regular method as it's a full update or do I need to flash?
Originally t mobile variant I rebranded to international and sim unlocked. Also flashed to 9.0.17 and rooted via magisk. Any insight would be appreciated as I have heard improper updating can result in a brick. Thanks in advance
Click to expand...
Click to collapse
Just do a local upgrade. Just follow the guide to save root.

jimlightner said:
Anybody install this yet?
Click to expand...
Click to collapse
Everybody has installed it... It's been out for days

Went for it yesterday. With an "ultimate guide" here on forum. I was 9.0.17 rooted with twrp description problems. So I downloaded update (1.8Gb) from official One+ site. And did local update, and all the steps to keep root. After finally booting up I got message that Magisk Manager stopped working, but everything was fine. So cleared app temp memory, and settings (for Magisk only) and next boot everything was ok.

Nope... 100% stock, 9.0.17 is ROCK solid, g-pay, samsung pay work perfectly & there really isn't anything in 10 I can't live without yet. So, I
see no need to update for now.

I'm also not updating yet, at least until they fix the keyboard offset issue and other things I've read about.
Luckily you can just freeze the system update app with Titanium.

sssarg said:
I'm also not updating yet, at least until they fix the keyboard offset issue and other things I've read about.
Luckily you can just freeze the system update app with Titanium.
Click to expand...
Click to collapse
There is no keyboard offset issue and so therefore it's never getting fixed. Designs can change, but there isn't going to be a fix for something that isn't a problem.

Causical said:
There is no keyboard offset issue and so therefore it's never getting fixed. Designs can change, but there isn't going to be a fix for something that isn't a problem.
Click to expand...
Click to collapse
Judging by all the people complaining about the empty space under the keyboard it does seems to be a problem, though.

sssarg said:
Judging by all the people complaining about the empty space under the keyboard it does seems to be a problem, though.
Click to expand...
Click to collapse
There is a Magisk module to deal with that (immersive gestural Navigation for Android 10), and an adb command to change the size of the space. It's a deliberate thing from Google so they'll perhaps remove it later or no but staying with Pie just for that.....

Causical said:
There is no keyboard offset issue and so therefore it's never getting fixed. Designs can change, but there isn't going to be a fix for something that isn't a problem.
Click to expand...
Click to collapse
It's not a bug, it's there for the swipe gesture, so that way you won't swipe the keypad when using gestures
Sent from my LG-G8 using Tapatalk

Question of the day. I've been waiting to do the A10 update for the issues it showed on the first days. I'm on a converted 6T from TMo, running 9.0.17. my major concern is the GPay thing I use it a lot. But researching here there's a way to make it work if I root the device. So can I update to 10.3.0 then root to get the GPay issue resolved with the Hide module on magisk? Or should I root on Pie then update?

phillymade said:
It's not a bug, it's there for the swipe gesture, so that way you won't swipe the keypad when using gestures
Sent from my LG-G8 using Tapatalk
Click to expand...
Click to collapse
This is pretty bad ux experience, and with the amount of complaints it seems and accidental keypress possibly when swiping is much better than losing all the text and keyboard closing with an accidental touch. At least give us the option to move it down, without having to go into ADB and setting an offset that then interferes with the way all apps render.