Hello,
In your experience what is the best Custom ROM in terms of Fingerprint Scanner reliability. Some ROMs I have tried, work pretty well for several hours and then Scanner is just hit or miss. It works only Around 20% of times. Things get worse during Night Light Mode on. Maybe there are no ROMs reliable enough in this regard?
Thanks.
Related
Hi guys, im the developer of Kilsswitch, an app that turn off the screen of your device when the case is closed.
You can find the apps thread here:
http://forum.xda-developers.com/showthread.php?t=988126
Ive been meaning to get some feedback from people using the more obscure devices, so if anyone has the app or participated in the beta a few weeks back, id like to hear about the results!
This is fantastic. I didnt even know I was looking for this. It works exactly as its supposed to. Im using Vegan 5.1.1 and a SwissGear slip case from Walmart.
And as a bonus the Adam's light sensor is perfectly placed to be used a power "button" of sorts. GReat work!
Great! What sensors are you using?
Also, i will release a new version by weeks end which integrates a new function - you will be able to run Killswitch using a day/ night schedule. I know this doesnt sound important, but it is.
ATM Killswitch is a hack - i built it for myself knowing full well that low quality sensors on many devices will have problems registering events in high-sensitivity environments (at night, for example, when ambient light levels can be low in peoples homes) .
My galaxy tab is an engineering sample with an excellent light sensor which works perfectly even when light levels are low, but many consumer products have really weak sensors that cant differentiate between low light levels.
For this reason i always recommend an activation delay of 6+ seconds to ensure redundancy.
With the schedule feature, Killswitch will allow people with weak sensors to disable some functionality at times when they know their sensors are not up to psr.
Any way to provide apk? Market is always flaky on mine.
I'm using the ambient light sensor at 1% sensitivity. I don't think the Adam has a proximity sensor. I don't have a use for the accelerometer sensor as I don't place my device facedown but can confirm that it works, and well I might add.
Full disclosure, I pirated your app to test, but will be buying it tomorrow on payday, for my device and the 3 others that I manage in my family. Thanks for the hard work, this is extremely useful.
Edit: Bought 2 copies so far. 1 for myself and 1 for the wife.
Ah, so a pay for app, I checked and also no demo. I'll try it once there is one, thanks for the effort.
15 minutes is more than enough to try it out - just put your finger over the light sensor!
Ive been considering a demo, but it would have to be seriously restricted or time-limited... hardly a demo.
Hey folks, I am Canadian that is looking to possibly import an MI5 but I figured I should find out a few things from you all that have been living with these phones for a while before buying.
Are there any hardware or software issues with the MI5 that I should be concerned about? I have a sony z3 compact right now and it's been infamous for vibration motors, headphone jacks, and screen failures. It also has no AOSP based daily drivers.
Development seems to be pretty active here, is that actually true? Are developers dropping off from this phone or is there still a steady amount of work being done?
From the lurking I've done it seems that unlocking, rooting and ROM installing is pretty easy. Are there any permanent dangers to doing these hacks (above and beyond the usual)?
I'm aware there is some camera quality issues on non-stock ROMs, is the camera still usable? How is the battery on custom ROMs?
Is there anything preventing this phone from being a daily driver when using a custom ROM like RR? Does the fingerprint sensor work on AOSP ROMs?
I am also aware of the radio bands the MI5 supports, I should be fine with that as my imported Z3 Compact has the same bands (as far as I can tell).
Edit: I was also wondering if the IR blaster works on custom ROMs!
Thanks for reading, answering and putting up with my ignorance. I'm just looking for some answers I couldn't find on this forum when I was searching yesterday.
Community is happy to help
1. Hardware wise you have to keep in mind the phone is fairly fragile. Low light performance of the camera is a bit poor. Audio out of the headphone jack isn't great on stock MIUI, but that can be fixed with Viper4Arise or any AOSP ROM. RAM management and general performance on MIUI is "ok" - but the phone is blazing fast on AOSP + CAF. There is no component that is prone to fail that I am aware of, but I have read of the occasional hard-brick triggered from nothing more than a reboot on custom ROMs - this can be solved by flashing stock ROM in EDL mode.
2. There seems to be a steady amount of development going on - we just got the drop on about 7 new ROMs in the last month. However, there are and have been developers leaving in favour of the One Plus 3, and development is only moderate compared to its forum.
3. It's fairly easy, but a bit frustrating getting the bootloader unlock from Xiaomi, as it usually takes about 5 days for the unlock to be approved and then 5 more days for it to actually work. There is also a possible driver issue on Windows which can prevent unlocking, so if you're stuck that's probably the case. Except for the above mentioned possible hard-brick there are no additional dangers, and dare I say less so than other phones I worked on.
4. The camera is usable on custom ROMs but considerably worse. Mainly there is a lot more noise in the photos, but detail remains high. Video recording seems to be broken on most AOSP ROMs, but alternative camera apps are apparently a work around. In my experience battery life is better on custom ROMs as they have functional Doze on Nougat, but not by much.
5. Fingerprint sensor works fine on custom ROMs, even better if you consider that you can wake + unlock your phone without pressing the button. There have been reports of some people experiencing slow fingerprint scanning on custom ROMs (3-4s). I use a custom ROM as my DD and I don't have any major issues except video recording that I haven't yet bothered to address.
I hope that this information finds you well. The Mi5 isn't perfect, but I'd be damned to say that a better phone exists for $200. The camera, battery life, performance, screen, audio, and design is good and there really isn't much to worry about.
xdadevet said:
Community is happy to help
1. Hardware wise you have to keep in mind the phone is fairly fragile. Low light performance of the camera is a bit poor. Audio out of the headphone jack isn't great on stock MIUI, but that can be fixed with Viper4Arise or any AOSP ROM. RAM management and general performance on MIUI is "ok" - but the phone is blazing fast on AOSP + CAF. There is no component that is prone to fail that I am aware of, but I have read of the occasional hard-brick triggered from nothing more than a reboot on custom ROMs - this can be solved by flashing stock ROM in EDL mode.
2. There seems to be a steady amount of development going on - we just got the drop on about 7 new ROMs in the last month. However, there are and have been developers leaving in favour of the One Plus 3, and development is only moderate compared to its forum.
3. It's fairly easy, but a bit frustrating getting the bootloader unlock from Xiaomi, as it usually takes about 5 days for the unlock to be approved and then 5 more days for it to actually work. There is also a possible driver issue on Windows which can prevent unlocking, so if you're stuck that's probably the case. Except for the above mentioned possible hard-brick there are no additional dangers, and dare I say less so than other phones I worked on.
4. The camera is usable on custom ROMs but considerably worse. Mainly there is a lot more noise in the photos, but detail remains high. Video recording seems to be broken on most AOSP ROMs, but alternative camera apps are apparently a work around. In my experience battery life is better on custom ROMs as they have functional Doze on Nougat, but not by much.
5. Fingerprint sensor works fine on custom ROMs, even better if you consider that you can wake + unlock your phone without pressing the button. There have been reports of some people experiencing slow fingerprint scanning on custom ROMs (3-4s). I use a custom ROM as my DD and I don't have any major issues except video recording that I haven't yet bothered to address.
I hope that this information finds you well. The Mi5 isn't perfect, but I'd be damned to say that a better phone exists for $200. The camera, battery life, performance, screen, audio, and design is good and there really isn't much to worry about.
Click to expand...
Click to collapse
Thank you so much for the detailed response! Greatly appreciated!
This all is reminding me of the fun I had with AOSP ROMs back on my Galaxy SIII, happy thoughts! (I've been stuck in Sony's software for too long!)
What is CAF?
Is the IR blaster working in AOSP-based ROMs?
TheHow7zer said:
Thank you so much for the detailed response! Greatly appreciated!
This all is reminding me of the fun I had with AOSP ROMs back on my Galaxy SIII, happy thoughts! (I've been stuck in Sony's software for too long!)
What is CAF?
Is the IR blaster working in AOSP-based ROMs?
Click to expand...
Click to collapse
It's a pleasure
Well then it's good to know they run brilliantly on the Mi5 (buttery smooth UI, and I get good numbers on benchmarks as testament, see attached pics).
CAF is short for Code Aurora Forums, a collection of companies that merge their updated driver code with the vanilla AOSP code from Google.
I don't know if the IR blaster works on AOSP as I currently don't have any devices on me to test it with. I could try this weekend when I get home.
Edit: I've since arrived home and can confirm the IR blaster works on AOSP. I used Anymote if you're interested.
AOD is a useless battery drain in comparison to ambient display
I wish they would switch to ambient..
Is there a way to get ambient on stock rom without root?
Doubt it.. maybe you can mimickor do it using tasker?
Have a look here...
AOD is not inherently bad for battery life, not if it is done properly and is on AMOLED.
Any black you see is not causing power to drain and if you haven't done anything silly with AOD wallpapers or anything like that then the battery life that the clock, date and notifications takes up is minimal anyway - an ambient display could actually end up being a bigger drain (again depending on how it is actually set up) as it requires the phone to process something every so often as well as lighting up some of the screen.
I think it would be nice to have both options to choose from, ambient or AOD
Lennyuk said:
AOD is not inherently bad for battery life, not if it is done properly and is on AMOLED.
Any black you see is not causing power to drain and if you haven't done anything silly with AOD wallpapers or anything like that then the battery life that the clock, date and notifications takes up is minimal anyway - an ambient display could actually end up being a bigger drain (again depending on how it is actually set up) as it requires the phone to process something every so often as well as lighting up some of the screen.
Click to expand...
Click to collapse
I second this as correct and will add that it also has been proven that the displayed images shift pixels as not to cause screen burn
winol said:
I think it would be nice to have both options to choose from, ambient or AOD
Click to expand...
Click to collapse
more options are always better but i had a OP5T for a few days and they only thing i truly miss on note 8 is that ambient display and fast and well placed fingerprint scanner on OP5T
ho and its face unlock is also blazingly fast
bloodomen2 said:
more options are always better but i had a OP5T for a few days and they only thing i truly miss on note 8 is that ambient display and fast and well placed fingerprint scanner on OP5T
ho and its face unlock is also blazingly fast
Click to expand...
Click to collapse
Totally agree and also the software significantly faster and less laggy on the 5T...
mikey_sk said:
Totally agree and also the software significantly faster and less laggy on the 5T...
Click to expand...
Click to collapse
i stayed with note8 only cus i love the camera and all its features more but OP5T was insanely fast and smooth also battery life were better
i hope Oreo update for note 8 speed things up and improve the battery
i didnt stay with modified clean android because its a bit boring and you need many apps to make up for all the missing samsung quirks and features
but main reason i didnt stay with the OP5T was that it didn't work as well as my note 8 when using the gear s3 and a helmet bt headset together
on note i have them both connected as phone and can switch the audio easily when calling
OP5T got the audio switching option in oreo update but he cant take 2 devices as phone and switch between them when calling
Sometimes the Fingerprint Scanner couldn't process my finger I think this happens only when the phone is hot. Anyone else has this problem?
IMHO it has always been a bit crap and needs 2 or 3 goes before it works.
Nope, never. Always fast and unlocks on the first go
at first (7.1) it was bad, but after some updates it has been pretty great honestly. Fast and responsive.
Hello,
although the developers are very active and we are getting there, my question is whether there's a ROM that is "complete" at the moment.
With that, I mainly mean the 100% working fingerprint sensor. With that, I mean a ROM that doesn't 100% brightness while using fingerprint reader and that has a functional fingerprint reader when screen is turned off (ie. wakes the phone)?
I am excited about the recent developments, however, I am just looking for a smooth experience for the time being
Thanks again to all the hard working developers.
At the moment, I think the only one that does not light up the screen (not tested by me) is Statix, BUT, apparently the screen needs to be at at least 40% brightness for the fingerprint scanner to work.
You can try all of these and chose the best one for you
(Lineage(18.1/19), OmniRom, StatixOS, ArrowOS (no longer supported, the unit of the maintainer ramdump-ed.))
I haven't tried Statix yet. Good time to try.
At the moment, I think the only one that does not light up the screen (not tested by me) is Statix, BUT, apparently the screen needs to be at at least 40% brightness for the fingerprint scanner to work.
Click to expand...
Click to collapse
Does this mean that fingerprint doesn't wake the phone either?
I currently have Los19, wasn't able to get 18.1 working. Haven't tried OmniRom, but I've tried ArrowOS and it wasn't bad.
Thanks for the pointers! Does anyone know what's the reason everyone is having problems with the scanner?