Ultimate Fingerprint Scanner Thread - LeEco Le Max 2 Questions & Answers

I would like to consolidate all the discussion around Le Max 2 fingerprint scanner(FPS) here. It seems FPS has either hardware of software (driver) issues. Is there something LeEco can do release good working drivers in the latest stock rom so those people who has a dead FPS can revive the same?
It blows my mind that they put that hardware in this and it is of no use for many of us. Has anyone tried flashing older Roms that can revive this hardware?

It's hardware problem. Changing software does nothing.

Are there any diagnostic tools that can tell if these sensors are alive or recoverable?

Related

[Q] Dell streak G-sensor calibration failure

Hello! My problems are messed up g-sensor parameters, which can't be calibrated by using a fastboot menu method(as you can see on the pictures). I've read the post from HD2 forum, but I can't find AK8973Prms.txt to edit offset values(I've only found ecompass_ak8973s which I can't edit(opened as a text file appears blank)). My Rom is DSC v2.3.
How can I possibly manually calibrate offset values to calibrate my g-sensor?
I'm unsure how a post from the HD2 forums is supposed to help as no one here has attempted to do what you're attempting.
How is the sensor messed up?
1. Why HD2 forum posts:
I've searched all XDA forums about my problem, and the only one I found possibly helpful was posted on HD2 forum.
I assume in HD2 there is also AK8973 sensor, and I thought there could be similar method to manualy change the offset values.
Sorry If I got something wrong.
2. How is the sensor messed up:
g-sensor shows wrong acceleration values(which in this case doesn't care me a lot), but orientation values are messing the orientation of the screen- this is what my main problem is. I found some solution to this by means of resetting(or recalibrating) sensor through fastboot menu under *#301#. But I could not work out G-sensor out of range error.
This is why I am searching for another solution of this problem.
You didn't get anything wrong, except assuming the HD2 has the same sensor. It may in fact have that sensor, but it's in your best interests to delve a bit deeper and be positive both devices use the same hardware. Even then, as you're finding out, what works for one device may not work for another.
I'm not aware of anyone here who has ever had this issue, and thus I'm unaware of anyone who could fix it. You could try calling Dell, but after 2-1/2 years it's unlikely anyone is going to be of much help.
I understand that this issue has not been reported anywhere on this board, so I do not expect 'easy' answers. I do however ask for help from anyone on this forum. So far I know there are many brilliant developers, who make miracles to the Dell Streak 5 software. I believe that there must be somebody who knows where g sensor 'configuration' file is and how to edit it.
You see, I've tweaked my streak to the limits, and this is the only(very annoing) issue that i have with this phone. Maybe that's why it's so annoying.

Sensors only work un LP, HELP!!!

Well guys, my english is really bad so, i pasted the text what i posted in htcmania translated with google translate.
"First of all I must clarify that I am fully co desperate ... mostly because of not knowing what the **** is wrong with this phone.
I'm going to summarize everything.
A few weeks ago my mother told me that your screen is not rotated, then got into the menu of Samsung (* # 0 * #) to check that it was not a failure of the sensors and indeed it was, or seemed to be.
So far, all sensor data threw least the magnetometer and accelerometer. I tried everything, I integrate mobile disarmament, pass a neodymium magnet plate by carefully etc. Everything to do with the unit did. There was no other option for these sensors are damaged and most likely they were to touch plate change. Finally the phone could use so I will pay my S3 (which works perfectly) to my mother I stay with this as he gathered the money to buy a plate and change it.
Days later I started to lose my job ROM and the install CM12.1 got everything perfect and when you start the phone and turn perfectly broken screen, I was shocked, the first thing I thought is that perhaps CM12 using the front camera or other sensor to rotate the device, in order to assure lower the app CPU-Z to check the sensors and I find that the accelerometer data perfectly cast, lower Sensor Kinetics to make it a fabulous test and walked the other hand the magnetometer (compass) He never responded.
I thought, "Well I hit and walked out"
But it was not so fortunate who had since returning to Stock (4.3) I meet who do not respond, but I get confused the next day back to my job and under various Roms to try in my home-based CM10, 10.1 , 10.2, 11, 12.1 and a pair based on stock. Well. The accelerometer only I worked in 3 Roms, the 3 based on CM12.1.
And here most of my questions arises.
You likely they are to be a problem Soft?
If it were, returning to a stock should solve tried 4.1.1, 4.1.2, 4.3 and nothing.
But on the other hand I think if directly Hardware not work at all, that is because Lollipop works and not lower?
I want to clarify that it is no coincidence that works in Cm12.1 since I reinstalled and reinstalled and perfect furula (only the accelerometer)
You think? There is a possibility that there may be some partition where deleted files are communicating sensors? If so, I have possibilities to operate the accelerometer in all Roms and recover the magnetometer restoring those files?
HELP PLEASE NO LONGER DO BOYS."
The sensors only works in Roms based on CM12.1 (5.1.1)
I could run only the accelerometer in that roms, magnetometer never responded
How is posibble what the sensors works in CM Roms and not in Stock roms? Damn guys, I'll set fire to this phone.

Bluetooth settings fault Eonon G5153F + Malaysk ROM

Im running the Malaysk ROM for RK3188 on my Eonon GA5153F
Since flashing the Malaysk ROM my bluetooth settings keep reverting to default, carkit device name etc.
Even if I manage to change them and even hold the settings for a coupe of boots on rare occasions they always revert to carkit and the default pin.
This problem has repeated over 2 versions of the ROM and posting in the Malaysk RK3188 thread brought nothing useful in the way of info.
Anyone have any ideas or suggestions how to sort this out, its very annoying and I desperately need bluetooth handsfree back for work purposes.
Dont know if its relevant - I also have the GA5153F and although everything was fine with Malaysks 4.4. ROM - when i updated to his 5.1 version - bluetooth did not work until I changed the bluetooth adapter in Factory Settings to the non "b" version (same model number) since then it works great.
Yep, youll get nothing with the wrong adapter set.
Unfortunately this is a different fault.
Anybody?
I know others have suffered this problem, doesnt anyone have any other suggestions?
mindriot said:
Anybody?
I know others have suffered this problem, doesnt anyone have any other suggestions?
Click to expand...
Click to collapse
Get a Parrot BT. I am using a MKI9200. It is simple to install and call quality is 100x better.
m00n61 said:
Get a Parrot BT. I am using a MKI9200. It is simple to install and call quality is 100x better.
Click to expand...
Click to collapse
Im sure it is, but it doesnt help solve the real fault with the kit Ive already purchased, fitted, and seriously need to function as I regularly need to take calls when driving, Im a courier.
Frankly I didnt have any call quality issues when it was working, its the total lack of function thats a bit of an issue!
Is this a hardware fault? Is it a Rom fault? IS it a media board fault? IS it as simple as a file somewhere being over written or with bad permissions?
Non b worked for me but now I have no wifi
Sent from my SM-N915T using XDA-Developers mobile app
mindriot said:
Im sure it is, but it doesnt help solve the real fault with the kit Ive already purchased, fitted, and seriously need to function as I regularly need to take calls when driving, Im a courier.
Frankly I didnt have any call quality issues when it was working, its the total lack of function thats a bit of an issue!
Is this a hardware fault? Is it a Rom fault? IS it a media board fault? IS it as simple as a file somewhere being over written or with bad permissions?
Click to expand...
Click to collapse
It is essentially a manufacturer (software) issue. Malaysk has mentioned somewhere that Chinese developers messed up the BT stack. You must understand that these units use a plethora of BT boards from various suppliers AND in various HW revisions. Nobody will work on a universal BT service that accommodates all these boards. Your best bet, if you want to use the on-board BT, is to find a ROM that works, through trial and error, and stay with that one.
m00n61 said:
It is essentially a manufacturer (software) issue. Malaysk has mentioned somewhere that Chinese developers messed up the BT stack. You must understand that these units use a plethora of BT boards from various suppliers AND in various HW revisions. Nobody will work on a universal BT service that accommodates all these boards. Your best bet, if you want to use the on-board BT, is to find a ROM that works, through trial and error, and stay with that one.
Click to expand...
Click to collapse
Thanks I am aware of the hardware diversity. It is frustrating that these companies have a weak attitude to stability. However the original rom had functional Bluetooth, and the Malaysk rom is supposed to be based upon it, thats what is also frustrating.
I tried posting in the Malaysk thread but it was largely ignored, scoffed at and lost in all the noise.
Anyone else?

Is GPS on a P8 Lite really broken or is it software?

Hey, geniuses, I am curious about the behavior of a P8 Lite and hardware failure. It's well known that the Wifi and Bluetooth stop working and their functions are greyed out on the settings on the P8 Lite. But when the GPS is not greyed out and can be turned on and off, is that really also a hardware failure? Especially given that many people reported total loss of GPS function after upgrading from 5 to Android 6, I really wonder if there is a way to do some tests. Some people also reported similar experience on LG phones after upgrade. Are there gpio commands which would measure if voltage is going to the GPS chip or if any data are coming out? Is there a way to detect if the chip is actually functioning, but the antenna is compromised? I really really don't want to throw this phone away. I want to use it as a GPS device when biking. I tried downgrading to 5.0.1, unlocked the bootloader, upgraded back to 6, omitted google apps. Nothing seems to persuade GPS to show even a single sat. Are there any programs which interrogate the GPS chip?

Touchscreen and fingerprint not working on all stable Android 11 ROMs. Potential hardware problem?

Initially I was thinking I am facing a software issue - touchscreen (and fingerprint) not working after Android 11 upgrade. I've read pretty much all threads about flashing stable ROMs and I've tried the following 3 with no luck:
European
V12.0.11.0.RFQEUXM​
Global
V12.0.13.0.RFQMIXM (the latest , Aug 2021 patch)​
V12.0.3.0.RFQMIXM (the 'stable recovery' ROM, which theoretically fixes everybody's touch issues​
And I had no luck with either of these 3 - no touchscreen, no fingerprint. I tried fastboot, I tried MiFlash - the ROM gets flashed, but touchscreen does not work.
This is when I started thinking this may be a hardware problem. Also, mind you, the problem did not occur immediately after the Android upgrade, it just happened sporadically overnight.
And here is the interesting bit: when I open the phone and disconnect the the left flex cable (connecting to the SUB PCB) - then the touchscreen works! I saw someone with a similar issue on that video
, where they get the touchscreen to work when disconnecting the SUB flex cable. But that is not a permanent solution. Obviously, I can't keep it disconnected as that means no charging, no audio, no calls...
So I am wondering - could it still be a software/ROM issue? If not, should I be thinking about changing the SUB flex cable? Or the whole bottom PCB? Not sure if something funky is happening with voltages there. Local service center said I needed new touchscreen but I am not trusting their judgement.
Thoughts and anyone with similar issue?
Thanks!
Have you solved this problem?
I am having the same problem.

Categories

Resources