Database Users

[Q] ICS Screen Autorotate not working

The Official OTA 4.0.3 ICS update broke auto rotation. The rest of the thing is running smooth as butter, but no auto rotation and the switch isn't doing anything.
Anyone know of a fix to this? I had this prob with the leak but after rooting and reinstall leak from scratch it cured itself. This one isn't doing that.
Is there an app to set the orientation of the screen manually that i can use in the interim??
------------------------------------------
400+ Views later, i think quite a few people have this issue and are trying to find a solution to this.
So far, thank you networkdawg for your app suggestion for manually rotating the screen, however that is a paid for app with a few too many options for my need. I'm currently using Mantano Reader Free to rotate my screen.
https://play.google.com/store/apps/details?id=nl.fameit.rotate
------------------------------------------
Before i accidentally upgraded to the ICS leak, i had my old HC bootloader and was running Lightspeed flawlessly.
Does anyone know of a way to downgrade the bootloader back to HC so i can run a custom bootloader?
OR
a custom bootloader for ICS?
------------------------------------------
Ok so in the end i used jazzyjames' tutorial and blasted HC + HC Bootloader back onto my tab (accelerometer now working once more), rooted, ran Acer Recovery Installer and loaded Light Speed ICS once more.
Everything is working swimmingly. No issues and i got ICS running like a champ.
When the hardworking devs in the dev section have streamlined the ICS bootloader unlocker and installing of a custom recovery a little further, i may try the ICS bootloader once more. But for now, to just have a functional tab, im sticking with the old stuff a little longer.
Thanks Civato, Blackthund3r and jazzyjames for their excellent tools and tutorials. I could not have done it without their help.
------------------------------------------
Update May 08 2012
Did something new, reverted back to stock 3.2.1 (the Gen 2 that was used in Jazzy's revert tutorial), did an OTA upgrade to ICS Official. On first run everything worked.
The minute i rebooted, the accelerometer stopped working.
Followed Civato's tutorial down to the letter, got the custom ICS bootloader working with recovery. Ran like a charm.
Installed a custom ROM (Lightspeed), accelerometer was still not working.
MY TAKEAWAY ---- The accelerometer issues is not a problem with ICS itself, but related to the new chipset firmware and bootloader included with the ICS update. I could be wrong here.
Anyone have any other insights into this?
Back to HC bootloader once more (accelerometer working again) no dice with ICS bootloader :S

I'm not aware of any apps that will switch orientations, only lock it.
Have you tried switching the lock to off then rebooting to see if that resets it?
I have noticed the orientation check isn't as sensitive as it used to be so sometimes I have to wait a few extra seconds or orient the tablet a little more [than usual] to get it to switch over. But it does work.

I have the rotation problem also. As a workaround, I installed this and it works great, although manually.
https://play.google.com/store/apps/details?id=nl.fameit.rotate

veer01_42 I'd be interested in your review of that app if you use it and/or pay for it.

I have the same issue. I have a couple apps that are orientation locked and I can use them to rotate but it's very annoying. Hope this gets fixed soon

anyone try a factory reset to see if that fixed it

A factory reset fixed it for me
Sent from my PC36100 using XDA

Been factory resetting this thing all night, no beans at all.

With the 4.0.3 leak, after one reset it worked for me, but i never got it to repeat again. So don't go factory resetting your tab in a hurry if you know whats good for you, especially if your rotation is working.

Good app, lots of options, but for what i want, this app is too much and it puts an icon next to the clock for quick access, but you cant preset the orientations there. There are only three, locked, auto and whatever you have it in now.
To get to the other options, tap the notification and it brings up a menu with all the other orientations (over 10 of them) its too much for me. But its an extremely powerful app.
Not worth the money as a workaround to a stupid accelerometer.

Encountered the same issue. I was in Portrait mode, playing Draw Something, and suddenly it just rebooted and went into Landscape mode. After a factory reset, it is not fixed. Not sure where to go, but this is highly disappointing for a tablet I paid close to $500 for...

Try wipe cache, it works for me. All said methods in the forum doesn't work for my tablet though.

qpmzal said:
Try wipe cache, it works for me. All said methods in the forum doesn't work for my tablet though.
Click to expand...
Click to collapse
What cache?
Do you mean Pwr Button + Volume Up while toggling screen lock switch?
Or is it something else?

On some a500 that were rooted and accepted the ics ota, a few things got broken during the upgrade. Flash a stock rooted ice rom, but before you do go into recovery and and select backup an restore,click on toggle backup of internal storage. Then you should see enabled on the screen. Then do full reset in mounts and storage plus your normal wipe. This will fully format everything on your tab but sd . When you reflash the new ics rom everything should work fine.
You miss 100% of the shots you don't take....... ..Wayne Gretzky.......

Flash a stock rooted ice rom
Click to expand...
Click to collapse
You mean the 4.0.3 Leak, install that and then use the one click root tool available in the forum?
but before you do go into recovery and and select backup an restore,click on toggle backup of internal storage.
Click to expand...
Click to collapse
Are you talking about Installing the V3 ICS recovery or the original honeycomb?
Then you should see enabled on the screen. Then do full reset in mounts and storage plus your normal wipe. This will fully format everything on your tab but sd . When you reflash the new ics rom everything should work fine.
Click to expand...
Click to collapse
This is in the ICS V3 custom bootloader/recovery right?

variations on problem for different versions
More pieces to the puzzle.
I just downloaded and installed Acer_AV041_A500_1.041.00_WW_CUS1 (very close to stock OTA, but rooted) from XDA and applied it over the stock OTA I had received from Acer directly, Acer_AV041_A500_RV05RC01_PA_CUS1.
Under Acer_AV041_A500_1.041.00_WW_CUS1 screen rotation (and the error 26's) would not clear. I could not get the rotation to work at all, even with multiple reboots, and hard (pinhole) resets.
I restored to Acer_AV041_A500_RV05RC01_PA_CUS1 and rotation is back to it's unstable self, but at least a pinhole reset will clear it.

PSA: Configure your fingerprint scanner before flashing any ROM

Earlier today I was mucking about and decided to play around with the fingerprint scanner for the first time. When I went in to settings and clicked the fingerprint manager, I received an error stating that the scanner is borked, and to reset my device to fix it. Rebooting did not fix the issue.
Soon I found another person with the same issue, who said that he was able to fix it by flashing stock NJ7 via Odin. After a bit of chatter we realized that neither he nor I had set up the fingerprint scanner before flashing a ROM. We basically booted the phone and went straight to rooting it, and flashing ROMs on it.
I can confirm that re-flashing the stock ROM via odin allowed me to set up the scanner successfully, and that the functionality has not been affected by any subsequent ROM flashing.
I do not understand the mechanism behind why this happens, it is just my experience. Perhaps there is some sort of validation that is run the first time you use the scanner, making sure you are running official firmware, and then setting a flag somewhere? How then would that flag be saved for all subsequent rom flashes? Hidden partition or some ****? Hardware flag? I dunno I don't get it, but I figured out how to fix it by golly. Hopefully this helps someone else.
If any others can confirm the same issue, we may want to add this as a step in the rooting/romming how-to threads, so that others don't run into the same issue.
One good thing is that when I flashed stock via odin, it didn't wipe my data. I was able to then flash TWRP and then Dynamic Kat again, keeping all of my settings the whole way through. Ended up not being as much of a hassle as I thought it was going to be :good:

Thank you for sharing this, I have to say in my case it is not working now i did get the phone rooted and then added jovys rom then did my setup the fingerprint scanner worked for me, then i installed dynamic rom and then the later update of same rom and then the fingerprint scanner is no longer working for me there is a new update for the rom i am going to flash and see if it works now as in a previous version the bloat from samsu g had been removed and with jovys rom being stock rooted it was still there, so i am wondering if it has to do with some of the bloat from Samsung and it being removed that breaks the fingerprint scanner, i will report after i flash the new version of dynamic.

santos.moreno3 said:
Thank you for sharing this, I have to say in my case it is not working now i did get the phone rooted and then added jovys rom then did my setup the fingerprint scanner worked for me, then i installed dynamic rom and then the later update of same rom and then the fingerprint scanner is no longer working for me there is a new update for the rom i am going to flash and see if it works now as in a previous version the bloat from samsu g had been removed and with jovys rom being stock rooted it was still there, so i am wondering if it has to do with some of the bloat from Samsung and it being removed that breaks the fingerprint scanner, i will report after i flash the new version of dynamic.
Click to expand...
Click to collapse
I first noticed the problem while I was on Dynamic Kat 1.1 and thought the same thing, that it was something to do with the Sammy apps, but it still didn't work after updating to DK 1.2. I've had it both working and non-working whilst running the same ROM (1.2,) and the only thing different between the two instances was the fact that I configured it while I was in stock in one instance.

This is important information. Hopefully the devs will be able to fix this asap. Thanks!!

Wow thank you BotsOne! I'm having the same issue. I'll try this in the morning. Before I rooted, I set up the fingerprint scanner and it worked fine the I switched back to swipe, then rooted. After rooting I installed Jovys rom and lo it hasn't worked since. Does the lock screen have to be set to fingerprint scanner at the time of flashing roms or can you set it up once and move on from that point forward? Thanks again!

android242 said:
Wow thank you BotsOne! I'm having the same issue. I'll try this in the morning. Before I rooted, I set up the fingerprint scanner and it worked fine the I switched back to swipe, then rooted. After rooting I installed Jovys rom and lo it hasn't worked since. Does the lock screen have to be set to fingerprint scanner at the time of flashing roms or can you set it up once and move on from that point forward? Thanks again!
Click to expand...
Click to collapse
Honestly I'm not sure. We need a few more people with the same error to get to the bottom of what's going on here. I could be way off with my assumption. We need a bit more info.

Cool I'll try tomorrow and report back..

BotsOne said:
Earlier today I was mucking about and decided to play around with the fingerprint scanner for the first time. When I went in to settings and clicked the fingerprint manager, I received an error stating that the scanner is borked, and to reset my device to fix it. Rebooting did not fix the issue.
Soon I found another person with the same issue, who said that he was able to fix it by flashing stock NJ7 via Odin. After a bit of chatter we realized that neither he nor I had set up the fingerprint scanner before flashing a ROM. We basically booted the phone and went straight to rooting it, and flashing ROMs on it.
I can confirm that re-flashing the stock ROM via odin allowed me to set up the scanner successfully, and that the functionality has not been affected by any subsequent ROM flashing.
I do not understand the mechanism behind why this happens, it is just my experience. Perhaps there is some sort of validation that is run the first time you use the scanner, making sure you are running official firmware, and then setting a flag somewhere? How then would that flag be saved for all subsequent rom flashes? Hidden partition or some ****? Hardware flag? I dunno I don't get it, but I figured out how to fix it by golly. Hopefully this helps someone else.
If any others can confirm the same issue, we may want to add this as a step in the rooting/romming how-to threads, so that others don't run into the same issue.
One good thing is that when I flashed stock via odin, it didn't wipe my data. I was able to then flash TWRP and then Dynamic Kat again, keeping all of my settings the whole way through. Ended up not being as much of a hassle as I thought it was going to be :good:
Click to expand...
Click to collapse
Yes, I am quoting the entire op...
Give me some more evidence of this and I will edit the Root & Recovery Guide immediately... I have seen conflicting posts on this matter too... Also, is not clear if private mode does continue to work after rooting or not... Can anyone confirm... (without flashing any roms... from original unrooted to rooted) Private mode... does work or not??? (Private mode is not suppose to work after rooting... but some say it does work???)
Nice post! Come on people... help...

Before you back up your rom, disable fingerprint scanner and delete saved fingerprints. If you don't and you go do your backup and ever plan on using the scanner again on that backup, it won't work. One of the guys thinks it has to do with the fingerprints being encrypted so when you restore, it can't decrypt it and locks you out.
I can confirm personally that disabling it before you do your backup then flashing a new rom then restoring your old backup, the fingerprint scanner will still work. Just have to set it up again. But that is a whole lot easier then flashing stock with odin again and starting over.

inphamous36 said:
Before you back up your rom, disable fingerprint scanner and delete saved fingerprints. If you don't and you go do your backup and ever plan on using the scanner again on that backup, it won't work. One of the guys thinks it has to do with the fingerprints being encrypted so when you restore, it can't decrypt it and locks you out.
I can confirm personally that disabling it before you do your backup then flashing a new rom then restoring your old backup, the fingerprint scanner will still work. Just have to set it up again. But that is a whole lot easier then flashing stock with odin again and starting over.
Click to expand...
Click to collapse
I think this may be an additional problem for flashers, but not necessarily the same one I am addressing. The reason I say this is because I hadn't configured the scanner at all previous to when I discovered that mine didn't work, the error completely prevents me from opening the fingerprint manager. I couldn't even enable the fingerprint function to begin with. Does that make sense?
Not trying to argue just trying to make sure we are on the same page =)

Just noticed my fingerprint scanner isn't working. Wtf lol
Sent from my SM-N910T using Tapatalk

i notice this problem as soon as i flashed first rom the only way o get it working again is flashing back to stock odin but no matter what i do as soon as i flash a rom I get a error message ? here the post another member had the same problem
http://forum.xda-developers.com/note-4-tmobile/help/fingerprint-sensor-error-t2918069

inphamous36 said:
Before you back up your rom, disable fingerprint scanner and delete saved fingerprints. If you don't and you go do your backup and ever plan on using the scanner again on that backup, it won't work. One of the guys thinks it has to do with the fingerprints being encrypted so when you restore, it can't decrypt it and locks you out.
I can confirm personally that disabling it before you do your backup then flashing a new rom then restoring your old backup, the fingerprint scanner will still work. Just have to set it up again. But that is a whole lot easier then flashing stock with odin again and starting over.
Click to expand...
Click to collapse
Thats not entirely accurate.
I set up my stock rom with the FP scanner...backed up in twrp as usual and i have flashed 4 roms since then and had to set it up gain each time and never had a problem. Ive never disabled it once.
sent from Canada via my Note 4, 3, 2 or One X+

So what exactly must be done to preserve fingerprint scanner functionality before flashing a custom rom?

force70 said:
Thats not entirely accurate.
I set up my stock rom with the FP scanner...backed up in twrp as usual and i have flashed 4 roms since then and had to set it up gain each time and never had a problem. Ive never disabled it once.
sent from Canada via my Note 4, 3, 2 or One X+
Click to expand...
Click to collapse
Have you tried restoring a backup and using the scanner? That's when it breaks. I can flash roms fine without having to disable it, but it didn't work after I restored a rom that had it enabled. Locked out of it

JawjaBill said:
So what exactly must be done to preserve fingerprint scanner functionality before flashing a custom rom?
Click to expand...
Click to collapse
I can tell you my history. I setup the fingerprint scanner right away before flashing anything as it is a must have feature for me. Later, I flashed a couple different ROM's and never had an issue. Just had to setup the fingerprint again. So my guess is if you set it up before flashing any ROM, you should be good. At least I was. I haven't had to disable before flashing or anything like that.

COCODRILO45 said:
i notice this problem as soon as i flashed first rom the only way o get it working again is flashing back to stock odin but no matter what i do as soon as i flash a rom I get a error message ? here the post another member had the same problem
http://forum.xda-developers.com/note-4-tmobile/help/fingerprint-sensor-error-t2918069
Click to expand...
Click to collapse
force70 said:
Thats not entirely accurate.
I set up my stock rom with the FP scanner...backed up in twrp as usual and i have flashed 4 roms since then and had to set it up gain each time and never had a problem. Ive never disabled it once.
sent from Canada via my Note 4, 3, 2 or One X+
Click to expand...
Click to collapse
JawjaBill said:
So what exactly must be done to preserve fingerprint scanner functionality before flashing a custom rom?
Click to expand...
Click to collapse
inphamous36 said:
Have you tried restoring a backup and using the scanner? That's when it breaks. I can flash roms fine without having to disable it, but it didn't work after I restored a rom that had it enabled. Locked out of it
Click to expand...
Click to collapse
keitht said:
I can tell you my history. I setup the fingerprint scanner right away before flashing anything as it is a must have feature for me. Later, I flashed a couple different ROM's and never had an issue. Just had to setup the fingerprint again. So my guess is if you set it up before flashing any ROM, you should be good. At least I was. I haven't had to disable before flashing or anything like that.
Click to expand...
Click to collapse
And... We ALL agree that Private Mode is Not working...? Right... No Private Mode since rooting... Right? There is absolutely nobody with Private Mode still working after rooting...

TEKHD said:
And... We ALL agree that Private Mode is Not working...? Right... No Private Mode since rooting... Right? There is absolutely nobody with Private Mode still working after rooting...
Click to expand...
Click to collapse
I think once you root the KNOX counter gets tripped preventing private mode.

keitht said:
I think once you root the KNOX counter gets tripped preventing private mode.
Click to expand...
Click to collapse
Yeap I know... but there is this:
http://forum.xda-developers.com/galaxy-s5/development/mod-enable-private-mode-knox-0x1-t2904723
That almost nobody seems to know... It's actually possible to regain Private Mode after a tripped Knox... (Not impossible)

TEKHD said:
And... We ALL agree that Private Mode is Not working...? Right... No Private Mode since rooting... Right? There is absolutely nobody with Private Mode still working after rooting...
Click to expand...
Click to collapse
Well now....never tried it but just did and its working for me. Rooted, jovy23 deodexed stock, twrp.
The day i got my phone i odin'd update then installed twrp, then wiped everything but int & ext sdcard, rebooted to recovery, wiped again then flashed the deodexed stock rom.....just tested fingerprint unlock last night for the first time, no problems and just now tested private mode and again that works for me.
keitht said:
I think once you root the KNOX counter gets tripped preventing private mode.
Click to expand...
Click to collapse

[Q] [solved] GPS Not Working After Cyanogen Mod Install

Hi All,
I just got a new used Samsung Galaxy S4 on Sprint and brought it over to Ting (way, way, way cheaper). I got everything working with the stock ROM, including GPS, but I wanted to install Cyanogenmod, so I rooted it, flashed TWRP 7.8, and flashed the latest Cyanogenmod (snapshot M12), with Gapps, and a zip file with the Ting data XML files to get 3G and LTE working.
Everything seemed to work great, but then while driving I noticed that the GPS just did not get a lock. After trying for an hour, it still had nothing. I installed GPS Status and saw that it had no satellites. Clearing the GPS cache and re-downloading data with that app did not solve the problem. I tried GPS Doctor without success and the GPS fix equally without success.
I rebooted, then factory reset, then erased everything and flashed the latest CM nightly, all with no success.
I found some similar problems online at these places:
http://myblog-online.co.uk/2013/12/the-continuing-saga-of-my-galaxy-s4-custom-roms/
http://forum.cyanogenmod.org/topic/98811-gps-not-working-23rd-nightly/
http://forum.xda-developers.com/showthread.php?t=2172670
These are all old and none gave me anything that useful. Is it a GPS radio issue? Is there anything I can do?
I also just found this page: http://wiki.cyanogenmod.org/w/Known_Issues_page_for_d2lte, but it is for the S3, not sure what to make of it.
I made a nandroid backup of my stock rom, but then I copied it to my computer, and when I copied it back again it didn't work. TWRP failed to restore with the error "No partition selected for restore".
My plan now is to flash the stock rom with odin, confirm that GPS works there, and then try again, but this is becoming a huge time sink and I have a lot of other things to do.
Does anyone have any ideas how I can fix this? I am pretty sure it isn't a hardware issue.

MikeDacre said:
Hi All,
I just got a new used Samsung Galaxy S4 on Sprint and brought it over to Ting (way, way, way cheaper). I got everything working with the stock ROM, including GPS, but I wanted to install Cyanogenmod, so I rooted it, flashed TWRP 7.8, and flashed the latest Cyanogenmod (snapshot M12), with Gapps, and a zip file with the Ting data XML files to get 3G and LTE working.
Everything seemed to work great, but then while driving I noticed that the GPS just did not get a lock. After trying for an hour, it still had nothing. I installed GPS Status and saw that it had no satellites. Clearing the GPS cache and re-downloading data with that app did not solve the problem. I tried GPS Doctor without success and the GPS fix equally without success.
I rebooted, then factory reset, then erased everything and flashed the latest CM nightly, all with no success.
I found some similar problems online at these places:
http://myblog-online.co.uk/2013/12/the-continuing-saga-of-my-galaxy-s4-custom-roms/
http://forum.cyanogenmod.org/topic/98811-gps-not-working-23rd-nightly/
http://forum.xda-developers.com/showthread.php?t=2172670
These are all old and none gave me anything that useful. Is it a GPS radio issue? Is there anything I can do?
I also just found this page: http://wiki.cyanogenmod.org/w/Known_Issues_page_for_d2lte, but it is for the S3, not sure what to make of it.
I made a nandroid backup of my stock rom, but then I copied it to my computer, and when I copied it back again it didn't work. TWRP failed to restore with the error "No partition selected for restore".
My plan now is to flash the stock rom with odin, confirm that GPS works there, and then try again, but this is becoming a huge time sink and I have a lot of other things to do.
Does anyone have any ideas how I can fix this? I am pretty sure it isn't a hardware issue.
Click to expand...
Click to collapse
That's is pretty much what you have to do. Its go back to stock and get a lock there in maps. When you have a lock just go back to recovery and flash your custom ROM of choice. That is pretty much the only fix.
Sent from my GT-I9505G using XDA Free mobile app

ROMANTiC KiD said:
That's is pretty much what you have to do. Its go back to stock and get a lock there in maps. When you have a lock just go back to recovery and flash your custom ROM of choice. That is pretty much the only fix.
Sent from my GT-I9505G using XDA Free mobile app
Click to expand...
Click to collapse
Thanks ROMANTiC KiD,
Good to know that I am heading down the right path before I spend a lot of time on this.
Should I not erase everything when I flash the custom ROM? I am pretty sure last time I used TWRP advanced erase to clear everything on the phone before installing. Should I just do a regular factory reset in TWRP to install CM in order to keep GPS functionality?
Thanks!

MikeDacre said:
Thanks ROMANTiC KiD,
Good to know that I am heading down the right path before I spend a lot of time on this.
Should I not erase everything when I flash the custom ROM? I am pretty sure last time I used TWRP advanced erase to clear everything on the phone before installing. Should I just do a regular factory reset in TWRP to install CM in order to keep GPS functionality?
Thanks!
Click to expand...
Click to collapse
Yes sir you can factory reset in twrp just remember to back up your files first! And you should still retain GPS lock.
Sent from my GT-I9505G using XDA Free mobile app

ROMANTiC KiD said:
Yes sir you can factory reset in twrp just remember to back up your files first! And you should still retain GPS lock.
Sent from my GT-I9505G using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the confirmation. I did exactly that and I can confirm that it did indeed work.
Thanks so much for the help.

Hi all,
Sorry to resurrect an old thread, but I am having this issue and the stock firmware flash isn't solving the issue. It is all very odd because it doesn't actually retain any kind of lock after flashing. I'm following instruction on here, but after locking gps on stock, then going to CM I cannot get a fix. It either had a massive radius on Maps, or it just locks to my home or work location.
Since trying much more I have managed to get the occasional satellite lock via GPS Locker, but even then as soon as I move from either my house or work, it can't find anything to lock onto and just defaults to a static location.
Is there anything you would recommend? I have 2 Samsung GS4's and they both exhibit the same problem. I have also tried this on an S4 Mini, but that retained lock just fine. I'm really confused as to what to actually try. If you could recommend anything I'd be very grateful.
Again, I'm sorry to res an old thread, but no one has been replying to the one I started for this issue :/

Your problem may be that there is some new issue with the newer firmware. I had success by first flashing the *old* firmware (you can download it from my dropbox here: https://www.dropbox.com/s/o3f3ynyezyy4yw9/L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_HOME.tar.md5?dl=0) and then upgrading to the second to last firmware update for the GS4: which gives you Android 5 but without fixing the MMS bug.
After that I flash TWRP with Odin, and then do a full erase in TWRP followed by flashing the latest CM. That series of steps works for me every time, although I found that large changes to my physical location (e.g. flying to England from California) cause it to break again. I actually had to sit in a cafe in an English airport with my laptop out flashing my phone back to stock just so that I could use Google maps to get to my mother's house. It was pretty ridiculous. Because of that and other issues, I now just use stock. I hate it, but I do it anyway. Good luck.

New problem with Fingerprints

So I've been searching all the internet regarding my problem and found none to have my problem.
I was using popwiz rom and after a while my fingerprint sensor stopped working with the error "An error has occureed with the fingerprint sensor. If this message appears repeatedly, restart your device."
Because I needed my G900FQ, I ignored the issue for a while. Found S7 insanity which has a fingerprint bug and forgot about the problem.
Yesterday wanted to check out official MM for my S5, and had to reflash stock lollipop. Then I remembered my fingerprint problem so I tried to set it up. I kept getting that nasty error, tried deleting cache, tried deleting data with Titanium. Reflashed stock 2 times again, nothing worked. Until I was ready to give up and go to bed. Then it suddenly started working. Managed to set it up and activate fingerprint unlock.
Now is the bummer!
I CAN UNLOCK with fingerprint if waiting about 3 seconds after turning screen on.
I CANNOT ADD FINGER through settings, I get the nasty error message.
Tried to enter factory tests and under NormalScan button says Version 0.0.0.0 and in SensorInfo says Ready and stays that way.
I tried to enter factory tests very fast after unlocking with fingerprint and I got, only once and for a brief moment, the right Version and SensorInfo, and Normal Scan showed data and graph.
Now I will try to install official MM firmware with Odin.
Anyone has any ideas to what the cause may be ? And maybe a solution ?
Thanks in advance
L.E. I installed official MM firmware and now fingerprint sensor works when unlocking and adding fingers, but when I try to unlock my phone while it is connected to a power source I get the nasty error message again and prompts me for my backup password. Any advice would be deeply appreciated.

Flash a stock ROM and factory reset?

It seems you did not read the whole thread before suggesting me this...
I did that many times. Lollipop and MM official stock... Its like the sensor is not responding in some situations , but in other situations it does. And this seems to be pretty random..
*Detection* said:
Flash a stock ROM and factory reset?
Click to expand...
Click to collapse

laurent.siku said:
It seems you did not read the whole thread before suggesting me this...
I did that many times. Lollipop and MM official stock... Its like the sensor is not responding in some situations , but in other situations it does. And this seems to be pretty random..
Click to expand...
Click to collapse
It seems you don't even know what you typed, nowhere in your OP did you mention factory resetting and then flashing a stock ROM
Only that you flashed stock ROMs, flashing stock ROMs does nothing to reset anything and will leave behind bugs from the previous ROM if the issue is with an app / data etc
Before getting clever, read what you type

It's obvious that by flashing a stock rom over a custom one will leave bugs. Did full wipe (system, data, cache&dalvik, even phone internal sd) before flashing stock, every time. Thanks anyway..
*Detection* said:
It seems you don't even know what you typed, nowhere in your OP did you mention factory resetting and then flashing a stock ROM
Only that you flashed stock ROMs, flashing stock ROMs does nothing to reset anything and will leave behind bugs from the previous ROM if the issue is with an app / data etc
Before getting clever, read what you type
Click to expand...
Click to collapse

Well maybe next time add that fairly important info to your main post, instead of hoping everyone is psychic, and then throwing a hissy fit when they suggest something you have not stated you already tried.

FPS not working for me - OOS 3.0.2

Tried every possible thing, from all available forums, but in vain.
1. Dirty flashed
2. Full zip flashed
3. Patch zip flashed
4. TWRP clean flash (wiped system, data, cache, internal)
My fingerprint sensor is not working when I am trying register Fingerprint lock from Settings.
Error: Enrollment was not completed Fingerprint enrollment didn't work. Try again or use a different finger.
Please help, I am quite used to FPS for unlocking my device and now I'm stuck with this build.
Thanks for any help extended...

hardware issue. RMA it.

ludester said:
hardware issue. RMA it.
Click to expand...
Click to collapse
It worked on 2.2.1 Also, home button is working perfectly.

Deleted

It worked!!!!!
All I did was charge it to 100% . Don't know what was the reason.

Great now keep it away from moisture, damp or sweat hands.
Sent from my ONE A2005 using Tapatalk