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...
Related
Hi all.
I installed cm13 on my mi5 pro yesterday. Looking good so far. I only have minor issues. The first and most important is I can't swap the back and recent button. I've already got used to miui method ( back on the right, recent button on the left).
How can I change them on cm13? Unfortunately closed+gravity can't help me, because after installing them my banking app (Barclay's) thinks that my phone is rooted and closes with an FC. I've also tried the buttons on the screen option, but in this way I lose screen size, though I can change the buttons I believe.
The other small issue is that I don't really like the menu in this alphabetical order system. Can I use something else instead? Like what is in Nova launcher, just a normalenu, nothing else.
Thanks for the help in advance.
Cheers!
the first issue is related to kernel... when cm will be based on the kernel released from xiaomi, the problem will be solved. don't worry, developers are working on it
I found the a method and it is working:
https://www.androidfilehost.com/?fid=457084094631642269
GrooveHero said:
Hi all.
I installed cm13 on my mi5 pro yesterday. Looking good so far. I only have minor issues. The first and most important is I can't swap the back and recent button. I've already got used to miui method ( back on the right, recent button on the left).
How can I change them on cm13? Unfortunately closed+gravity can't help me, because after installing them my banking app (Barclay's) thinks that my phone is rooted and closes with an FC. I've also tried the buttons on the screen option, but in this way I lose screen size, though I can change the buttons I believe.
The other small issue is that I don't really like the menu in this alphabetical order system. Can I use something else instead? Like what is in Nova launcher, just a normalenu, nothing else.
Thanks for the help in advance.
Cheers!
Click to expand...
Click to collapse
For the drawer style you can change that in the launcher's settings. Long press a free spot on your home screen, then press settings and change style to "compact".
This swaps the two capacitive buttons around to xiaomi setup instead of Google
you can also find it on this url: https://store.shade.sh/mi5/ from the unofficial cm13 weekly build thread if you do not wish to download it from myself
Thank you guys its working like a miracle.
Now I have another problem, but this time it looks massive.
So my problem is that cm13 is pre rooted when you install it. Well, I have no problem with it, but unfortunately my banking app ( Barclay's) has. I can't use it, because it says rooted device not supported. I've already checked developer options, and root access is disabled, but this doesn't help, I still have issues with the app. I tried flash SuperSU+binaries from twrp, opened app after flash and use full unroot, same problem, banking app thinks my phone is still rooted. I'm thinking about trying out the slim (aosp based) ROM if I can't find any working method.
Can you guys help me with this?
Thank you one again
GrooveHero said:
Thank you guys its working like a miracle.
Now I have another problem, but this time it looks massive.
So my problem is that cm13 is pre rooted when you install it. Well, I have no problem with it, but unfortunately my banking app ( Barclay's) has. I can't use it, because it says rooted device not supported. I've already checked developer options, and root access is disabled, but this doesn't help, I still have issues with the app. I tried flash SuperSU+binaries from twrp, opened app after flash and use full unroot, same problem, banking app thinks my phone is still rooted. I'm thinking about trying out the slim (aosp based) ROM if I can't find any working method.
Can you guys help me with this?
Thank you one again
Click to expand...
Click to collapse
Root cloak via xposed maybe? Not sure if still supported though!
Harrynowl said:
This swaps the two capacitive buttons around to xiaomi setup instead of Google
you can also find it on this from the unofficial cm13 weekly build thread if you do not wish to download it from myself
Click to expand...
Click to collapse
great! thank you very much!
Harrynowl said:
Root cloak via xposed maybe? Not sure if still supported though!
Click to expand...
Click to collapse
Tried out this method, but as soon as I tried to start banking app, it closed with an fc. Yes I remember now, that was the problem few days back.
Hm...I can't think anything else..
GrooveHero said:
Tried out this method, but as soon as I tried to start banking app, it closed with an fc. Yes I remember now, that was the problem few days back.
Hm...I can't think anything else..
Click to expand...
Click to collapse
I'm unsure, sorry!
GrooveHero said:
Tried out this method, but as soon as I tried to start banking app, it closed with an fc. Yes I remember now, that was the problem few days back.
Hm...I can't think anything else..
Click to expand...
Click to collapse
Try using shade.sh's userbuilds. They are built without built in root. They are under the category "userbuilds" on his website.
Success!
I had to install aosp to to realize what's the problem here. After I did that the same problem happened.: Banking app says my phone is rooted. So I tried doing the same methods on aosp what I did on cm13, except Xposed+gravity because I knew my apps gonna FC. So I tried safe unroot apk from play store, no luck. I also tried this app the night before.
Then i thought maybe I should enable root in developer options, because yesterday morning with this was a half success, Barclays mobile banking app( debit card) said, the device is rooted, I touched ok, then it started without any problems. It was only half success, because the other app Barclaycard (credit card) didn't work, same problem: the phone is rooted. So I tried out the following, and that was the complete success:
Enabled root access for apps only in dev options than i started safe unroot from play->everything's working like a charm.
Thank you guys for help!
This is what I get from the built-in camera app of my about one week old XP. Drives me nuts. I have defrosted all the bloatware I had freezed with Titanium, because I thought that may have been the reason. But it wasn't. I have tried with a third party camera app from Play Store, and that works without problems. So does the Snapchat camera. So it's nothing hardware, it's something that ties up the app. I have tried to reset the camera app, wipe data for the app and wipe dalvik and regular cache from TWRP. Any ideas what else I can do?
Could you find any solution?
Apart from using a third party app, not so far.
i have same problem
how to fix it? still waiting
I think it's the rooting with Magisk! I will see if I can find the developer. Have you two rooted?
Oh, it's not the rooting in itself, it must be Magisk. I have now rooted with SR2-SuperSU-v2.79-SR2-20170103215521.zip, and that worked as it should. No camera malfunctions.
I have reported it in the Magisk forum.
I have done a full repair using xperia companion and it still won't work. I believe Magisk is still installed, but I've already tried uninstalling it so how would I make sure?
Once you've unlocked the bootloader, it must be unlocked in order to use the stock camera app on an official ROM
use custom kernel to fix the problem
nieXas said:
use custom kernel to fix the problem
Click to expand...
Click to collapse
The problem is that the camera doesnt work with a RE-LOCKED bootloader , flashing a custom kernel is not possible with a LOCKED/RELOCKED bootloader.
Hi guys..
I have recently rooted (supersu) my j7 prime g610f (7.0) after installing dm-veriry pypass and twrp and then flashed xpoosed framework and tried aome moudles out and everything seemed to be fine .
Untill i rebooted to activate a moudle and i found that the lock screen doesnt want to unlock although the pin is right( just stands still for 2 seconds and then screen turns off and i repeated the process and same thing ) ..
I managed to unlock my phone through the website and tried other lock methods and i found that every method isn't responding aswell !
I then disabled all the models and denies all root access apps and rebooted and same thing happens.
I really need some help as i cant leave my phone unlocked.
Thx.
Bassem AbdullMonem said:
Hi guys..
I have recently rooted (supersu) my j7 prime g610f (7.0) after installing dm-veriry pypass and twrp and then flashed xpoosed framework and tried aome moudles out and everything seemed to be fine .
Untill i rebooted to activate a moudle and i found that the lock screen doesnt want to unlock although the pin is right( just stands still for 2 seconds and then screen turns off and i repeated the process and same thing ) ..
I managed to unlock my phone through the website and tried other lock methods and i found that every method isn't responding aswell !
I then disabled all the models and denies all root access apps and rebooted and same thing happens.
I really need some help as i cant leave my phone unlocked.
Thx.
Click to expand...
Click to collapse
1) Easiest way is to wipe and restore a backup in TWRP from when your device was working properly if you've hopefully already made one.
2) Another option is to boot into TWRP and go into file manager and delete the folders of the Xposed Modules you installed that you think might be causing the problem(in "/data/app/", "/data/data/, etc)". Then reboot and see if that fixed the problem. You have to be very careful when installing Xposed mods, especially when they're meant to tweak the system in some way, that they are actually meant for your device, particularly with Samsung Touchwiz devices that have heavily modded software.
3) Make sure that you're using the correct Xposed version for Samsung too, as this can cause problems with properly booting up the device.
4) Last case scenario you might want to consider wiping and reflashing your rom. Then at least you can make sure your touchscreen digitizer still works and can redo everything one at a time to see what's causing the problem.
I hope one of these suggestions helps.
Sent from my SM-N920T using Tapatalk
bogarty said:
1) Easiest way is to wipe and restore a backup in TWRP from when your device was working properly if you've hopefully already made one.
2) Another option is to boot into TWRP and go into file manager and delete the folders of the Xposed Modules you installed that you think might be causing the problem(in "/data/app/", "/data/data/, etc)". Then reboot and see if that fixed the problem. You have to be very careful when installing Xposed mods, especially when they're meant to tweak the system in some way, that they are actually meant for your device, particularly with Samsung Touchwiz devices that have heavily modded software.
3) Make sure that you're using the correct Xposed version for Samsung too, as this can cause problems with properly booting up the device.
4) Last case scenario you might want to consider wiping and reflashing your rom. Then at least you can make sure your touchscreen digitizer still works and can redo everything one at a time to see what's causing the problem.
I hope one of these suggestions helps.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Unfortunately i dont hace a backup but i noticed something that the problem is a delay in responding to my pin , and i notice that the cpu usage goes 3% to 35% when i unlock my phone usinv the pin ... i managed to unlock it by entering the pin and tapping in the screen few times to keep it lit and prevent it from sleeping .. any ideas foe that delay or cpu usage ?
Bassem AbdullMonem said:
Unfortunately i dont hace a backup but i noticed something that the problem is a delay in responding to my pin , and i notice that the cpu usage goes 3% to 35% when i unlock my phone usinv the pin ... i managed to unlock it by entering the pin and tapping in the screen few times to keep it lit and prevent it from sleeping .. any ideas foe that delay or cpu usage ?
Click to expand...
Click to collapse
Truthfully, your best bet while you have your device up and running is to backup all your apps and data with something like Titanium Backup or even sync them with the Samsung Cloud. The cloud reinstalls everything and sets your device configuration back to the way it was. Then, if you have a custom rom installed, wipe it in TWRP and reinstall it. If you're running stock, then don't wipe. Just go to the Sammobile website, download the latest firmware for your specific device and reflash it to the device with Odin. This generally fixes all system problems with a device, while preserving your app data.
Alternately, you can also try searching XDA for kernels that are made for your device that have a higher performance and try installing one of those to see if anything improves. As far as the screen going off early too, you can always check in "Settings/Display/Screen Timeout" to see what it's set for and change it to the max screen on time. It really sounds like you may have broke something system wise with Xposed or an Xposed module though, which is very easy to do, so I would really recommend starting over fresh. If you're on stock especially, as you really have nothing(data wise) to lose.
Sent from my SM-N920T using Tapatalk
I used the fingerprint sensor with no problem after rooting with magisk 17.6 (i think). But all of a sudden it wasn't working in any apps, including magisk manager but still works on my phone's lock screen. When i go to turn on fingerprint authentication for say lastpass or magisk manager it just says fingerprint failed without the opportunity to check my fingerprint like it usually does. Updated to magisk 18, same issue. Also tried a complete unroot and re-root and still not working. Even when i was no longer rooted the issue still occurred. Using a huawei p10(vtr-l29) on android 8.0.0.376(C432).
TIA
EDIT: heres the logcat of what happens when i try enable fingerprint authentication in magisk manager https://1drv.ms/t/s!Aqd1jJ_Y63Gpg7d9GM2_6ZRtB3ZXiA
Hi, I lost the finger print just now after updating to Magisk 18...
Ok, it is OK now, just after a reboot..
Zzrman said:
Hi, I lost the finger print just now after updating to Magisk 18...
Ok, it is OK now, just after a reboot..
Click to expand...
Click to collapse
I've got it fixed now, had to do a factory reset and update to 8.0.0.382. After that I had a safety net CTS mismatch so I had to change the device fingerprint to pixel 3 with the props module via shell
I have the same issue, but to be honest i am kind of lost with your explanation- Can you be more specific, please?
aalmeida1972 said:
I have the same issue, but to be honest i am kind of lost with your explanation- Can you be more specific, please?
Click to expand...
Click to collapse
It was a while ago so I can't remember what I did. Just backup your phone, restore stock recovery and factory reset device. Then start over.
Have a new phone now so can't be of much help sorry
Hi, I'm on latest Android 11 beta, my Google camera app sudden stop working and won't open again since then, my flash light grey out as well and i tried every method (clean cache, factory reset, safe mode) but nothing fix it.
Anyone else having this issue? I saw many people having this issue on Google camera playstore app review page, but till now no solution at all or fix by Google yet? Omg
keanyiap said:
Hi, I'm on latest Android 11 beta, my Google camera app sudden stop working and won't open again since then, my flash light grey out as well and i tried every method (clean cache, factory reset, safe mode) but nothing fix it. Anyone else having this issue? I saw many people having this issue on Google camera playstore app review page, but till now no solution at all or fix by Google yet? Omg
Click to expand...
Click to collapse
Could be a hardware issue. I know you said you tried everything but did you try another camera app? Fastboot flash back to 10? Don't dirty flash, let it wipe data. If it persists afterwards and the other camera app did the same thing, you may want to explore any warranty you may have.
v12xke said:
Could be a hardware issue. I know you said you tried everything but did you try another camera app? Fastboot flash back to 10? Don't dirty flash, let it wipe data. If it persists afterwards and the other camera app did the same thing, you may want to explore any warranty you may have.
Click to expand...
Click to collapse
I try others camera apps and all just allow me to use front camera instead of rear camera, might try to flash back to 10, will see how it goes... I don't think its a hardware issue cause all of sudden i saw lot people comment on playstore review regarding this issue