still fingerprint issue in new update 
still fingerprint issue in new update . please fix in next update .
still fingerprint issue in new update
. please fix in next update .
Official LineageOS CM-14.1 (7.1.2)
- Thread starter cr3pt
- Start date
Heyyo, not it is not. You will need to either use AddonSU from the LineageOS extras download page and then enable it in developer options or download Magisk. SuperSU is technically another option but I don't like it since it's closed source and some Chinese company owns it so who knows if they are using malware or not...
Can you please elaborate? I'm unsure how it's not working. If you're having issues registering your FP then please wait ten seconds after getting to the part where it asks you to put your finger on the sensor. There's a bug where it takes about 10 seconds for the FP service to connect to the device settings as the first few attempts fail. After ten seconds it registers fingerprints fine.still fingerprint issue in new update
Network problem . I can't get Google OTP. Can't sign into gapps . Fingerprint issue . In last 2 updates
Heyyo, unfortunately I've noticed as well that sometimes switching from Oreo to Nougat causes this issue. I'd recommend flashing an official version EUI ROM and then flashing TWRP to recovery and then Format Data and then reflaahing a Nougat ROM... Unsure right meow of any other solution.
Yes it is. Older versions didn't have it but newer ones do.
I flashed Slim7 and it worked. Swtiched into LineageOS, and it do not work. Both are nougats.
New update do not solve problem. Does flashing EMUI and then doing backup (not flashing) back lineage os, will solve problem?
Last edited:
https://mirrorbits.lineageos.org/full/x2/20180318/lineage-14.1-20180318-nightly-x2-signed.zip
New Build is up! Look @ changelog on site...
New Build is up! Look @ changelog on site...
i did a fresh rom install, no magisk, only gapps, and CTS fails :/ wth?
In my case whenever cts fails! I update to latest version of magisk or I do install it manually..
I installed magisk v16- cts failed
installed magisk beta v16.2- cts failed
Any more tips? maybe i should flash kernel?
delete it please
---------- Post added at 09:18 AM ---------- Previous post was at 09:12 AM ----------
I was using it until last week and I was quite satisfied with it.
Battery was perfect, once i got 6 hours of sot in my using period, also 4 hours + was guaranteed for me.
ROM was completely stable but there was only one bug, that was zoom bug which is common in all nougat ROMs.
Even wireless display sharing was also working which don't work in any other I tried.
You should try RR official nougat final version that is made by @andr68rus
---------- Post added at 09:18 AM ---------- Previous post was at 09:12 AM ----------
Hey! You should change ROM!! If you want nougat with complete stability then go for RRI installed magisk v16- cts failed
installed magisk beta v16.2- cts failed
Any more tips? maybe i should flash kernel?
I was using it until last week and I was quite satisfied with it.
Battery was perfect, once i got 6 hours of sot in my using period, also 4 hours + was guaranteed for me.
ROM was completely stable but there was only one bug, that was zoom bug which is common in all nougat ROMs.
Even wireless display sharing was also working which don't work in any other I tried.
You should try RR official nougat final version that is made by @andr68rus
Flash this fix:I installed magisk v16- cts failed
installed magisk beta v16.2- cts failed
Any more tips? maybe i should flash kernel?
https://mega.nz/#!7BEEUQxC!F4j7UKj4K8xBXfztg9KdxG8UjEXGxOQ0whH62HKEGVs
https://mega.nz/#!PM0XySLK!9-y7LJTydfS0mVBPsETszcrCLPv10wog-2lJJNjULoY
Tapatalkkal küldve az én LEX820 eszközömről
Last edited:
Similar threads
- Poll
Top Liked Posts
-
There are no posts matching your filters.
-
118Install - if it's first time, make clean install!
Please report what don't work correct. If it's possible, please attach logcat!
https://github.com/LineageOS
Official LineageOS CM-14.1
https://download.lineageos.org/x2
Google Apps:
http://opengapps.org/ (recommended: ARM64, 7.1, micro)
SU-Addon: (Root)
https://download.lineageos.org/extras
TWRP-Recovery:
https://twrp.me/devices/leecolemax2.html
Changelog:
Look into github! It's too more for report here...
Best regards
Cr3pT
XDA:DevDB Information
Official LineageOS CM-14.1 (7.1.2), ROM for the LeEco Le Max 2
Contributors
cr3pt, Andr68rus, Tortel1210
Source Code: https://github.com/LineageOS
ROM OS Version: 7.x Nougat
Based On: LineageOS
Version Information
Status: Nightly
Created 2016-11-12
Last Updated 2017-05-2229Members there is no demanding, you want something done NOW or your WAY, pickup Development and do it yourself, or just be thankful someone is developing.
Thread Cleaned.21I redid the 13.0 kernel, and camera (Images+Video) is now working. It looks like video failing was due to a bad merge or something.
Over the past few days, the source has now been brought in to the Lineage tree and commonized with the Leeco Pro3 (codename zl1)
Device tree:
https://github.com/LineageOS/android_device_leeco_x2
https://github.com/LineageOS/android_device_leeco_msm8996-common
Kernel:
https://github.com/LineageOS/android_kernel_leeco_msm8996
I have some more testing to do, and there a few minor details to iron out, but official Lineage (13.0) builds may be coming soon18
One more post with super-propose how to fix camera in 14.1 and I close that topic. And one more about that reply I do this same.16
@cr3pt
While I don't disagree with you, the post above does hold some merit. It isn't your typical "das camera work nao?". It is actually not a bad suggestion to back port blobs for similar hardware and try to shoehorn them in. I mean, if they got another device working the same way, which holds the same hardware, it may be worth a shot. Unless of course, you have already tried that in which case you could simply say "I have already tried and it didn't work".
Again, I understand your frustration. If you feel that your thread could use a cleaning from the useless posts of people simply asking for camera status, let a moderator know and we will gladly step in to clean things up a bit. There is no need to threaten, particularly over a seemingly useful comment like that.
