Hi,
I'll keep this thread for future reference about Android Oreo 8.1
LineageOS 15.1 running on my Huawei P9 Lite ( VNS-L31 )
I'll keep update the second post with working list/features !
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LOS 15.1 for VENUS devices ( Huawei P9 Lite )
Currently working :
touchscreen
audio & headphones
video & screen recorder
sensors
lights & notification light
adb/usb/mtp
internal/external storage
hardware video decoder ( including 60fps on YouTube )
hardware composer ( means that there is no issue regarding graphics , it's running as smooth as on stock EMUI firmware )
Wi-Fi
GPS
Dual SIM with LTE data connectivity
DRM enabled - only L3 level
NFC ( thanks to A2L5E0X1 )
Fingerprint
BT
Offline charging
Not Working Yet :
USB-OTG
USB tethering
Camera & Flash
Will not be Fixed :
Selinux security - permissive
Encryption device
FM Radio
good to see something new
Hello, looks interesting! I wanted to ask if the sources are public or not.
A2L5E0X1 said:
Hello, looks interesting! I wanted to ask if the sources are public or not.
Click to expand...
Click to collapse
Thanks !
The kernel source will be public of course ... the rest of the source is my property, and I'll see in the future if it will be or not published !
Anyway I created my source from scratch having nothing in common with the previous developers ... as you can see there is no custom ROM with hwcomposer enabled !
But why are you interested in the source, are you a developer ? Thanks !
surdu_petru said:
Thanks !
The kernel source will be public of course ... the rest of the source is my property, and I'll see in the future if it will be or not published !
Anyway I created my source from scratch having nothing in common with the previous developers ... as you can see there is no custom ROM with hwcomposer enabled !
But why are you interested in the source, are you a developer ? Thanks !
Click to expand...
Click to collapse
Well i recently started a scratch tree for venus too, but its incomplete. I was interested on what sources your rom is based. If you need help with something i could look at it and try to help.
A2L5E0X1 said:
Well i recently started a scratch tree for venus too, but its incomplete. I was interested on what sources your rom is based. If you need help with something i could look at it and try to help.
Click to expand...
Click to collapse
Thanks !
At this time I use a source ( device tree & vendor blobs ) based on my own implementation !
So far in the short time. Impressive! I'm already looking forward to the first public rom. Gladly also to test.
ScanX said:
So far in the short time. Impressive! I'm already looking forward to the first public rom. Gladly also to test.
Click to expand...
Click to collapse
Sure, don't worry ... I'll need some beta testers before first Beta Release of LOS 15.1 !
Please, stay tuned and follow this thread ... it takes some time until I choose a few who want to test the new custom ROM !
Good work and looking forward. May our P9 lites last longer
this is really great and promising! we certainly look forward for the future developments!
Nice! Looking forward for BT compatibility. Did someone test it with VNS-L23 devices?
Thanks for the work!
Hi !
Today I made a new TWRP 3.2.3-0 needed for LOS 15.1 - It not has decrypt data support because LOS 15.1 will not enabled such things , instead I fixed CPU temperature patch & also LED is enabled while USB connected !
This new TWRP is supposed to be used ONLY with LineageOS 15.1 Android Oreo 8.1 !
PacaPaw said:
Nice! Looking forward for BT compatibility. Did someone test it with VNS-L23 devices?
Thanks for the work!
Click to expand...
Click to collapse
Please, can you send me via PM these two INFO from your device ?
adb shell cat proc/cmdline > cmdline_L23.txt
Click to expand...
Click to collapse
and also
adb shell getprop > getprop_L23.txt
Click to expand...
Click to collapse
You must be on EMUI 5.x Android Nougat with root enabled !
If previously commands not working , please try in this way :
adb shell
su
cat proc/cmdline > data/local/tmp/cmdline_L23.txt
getprop > data/local/tmp/getprop_L23.txt
exit
exit
adb pull data/local/tmp
Click to expand...
Click to collapse
And upload somewhere in order to send me the link via PM ! Thanks !
Hello again. Talking about nfc, i recently fixed it on my own trees. Feel free to pick my commits:
hi6250: build nxp nfc from src · hi6250-5/[email protected]
Common Device Tree for hi6250 devices. Contribute to hi6250-5/android_device_huawei_hi6250-common development by creating an account on GitHub.
github.com
system.prop: force load nfc_nci.nqx.default · hi6250-5/[email protected]
* instead of nfc_nci.hi6250
github.com
venus: import nfc configs · hi6250-5/[email protected]
* they are device specific because of the different nfc chips
github.com
A2L5E0X1 said:
Hello again. Talking about nfc, i recently fixed it on my own trees. Feel free to pick my commits:
hi6250: build nxp nfc from src · hi6250-5/[email protected]
Common Device Tree for hi6250 devices. Contribute to hi6250-5/android_device_huawei_hi6250-common development by creating an account on GitHub.
github.com
system.prop: force load nfc_nci.nqx.default · hi6250-5/[email protected]
* instead of nfc_nci.hi6250
github.com
venus: import nfc configs · hi6250-5/[email protected]
* they are device specific because of the different nfc chips
github.com
Click to expand...
Click to collapse
Thanks !
Do you know something about Bluetooth ? I didn't managed to enable it ... even if I already checked logcat & dmesg .... nothing really specifically about bluetooth !
Also you can cherry-pick the fix on TWRP for CPU temperature ... from here for your officially TWRP !
EDIT :
I guess we need also :
on init
# NXP HAL expects /dev/nq-nci
symlink /dev/pn544 /dev/nq-nci
on post-fs-data
mkdir /data/nfc 0755 nfc nfc
mkdir /data/vendor/nfc 0777 nfc nfc
mkdir /data/vendor/nfc/param 0777 nfc nfc
Click to expand...
Click to collapse
EDIT II:
Enabled , Thanks ! -
( unfortunately it still doesn't work, but I think it's pretty easy to fix ) - tomorrow if I have a little more free time I'll try to fix this !
surdu_petru said:
Thanks !
Do you know something about Bluetooth ? I didn't managed to enable it ... even if I already checked logcat & dmesg .... nothing really specifically about bluetooth !
Also you can cherry-pick the fix on TWRP for CPU temperature ... from here for your officially TWRP !
EDIT :
I guess we need also :
EDIT II:
Enabled , Thanks ! -
( unfortunately it still doesn't work, but I think it's pretty easy to fix ) - tomorrow if I have a little more free time I'll try to fix this !
Click to expand...
Click to collapse
Np.
No idea about bt.. Only thing i fixed is the BT crash by building the bcm hal and adding the bt_vendor config but here it fails loading the hci_module. About nfc you dont need the nq-nfc symlink because its already correct in the nfc config. And my device detects my nfc tag without problems. I can even write it..
Oh and thanks for the twrp fix!
Great news, I am really looking forward to installing it on my VNS-L21 with EMUI 5.0.4 and Android 7.0, as more and more apps stop supporting Android 7.0
A2L5E0X1 said:
Np.
No idea about bt.. Only thing i fixed is the BT crash by building the bcm hal and adding the bt_vendor config but here it fails loading the hci_module. About nfc you dont need the nq-nfc symlink because its already correct in the nfc config. And my device detects my nfc tag without problems. I can even write it..
Oh and thanks for the twrp fix!
Click to expand...
Click to collapse
Glad to hear that it's working well on your device. I guess that I did something wrong on my build, I'll check today later, thanks !
Fingerprint Fixed !
I just managed to fix the fingerprint ( it will working only to unlock your device and there will be no gesture functions like on stock EMUI ) .
EDIT:
As soon as I'll fix Bluetooth there will be out the first BETA release of LOS 15.1
Related
Hello !
Until this ROM will be ready, I opened this thread to keep you up to date with my progress
I just managed to enabled stock hwcomposer to run on Lineage OS 13.0 and also BT was fixed .
Here is a list with what its currently working so far :
Working :
- touchscreen, adb & mtp, camera (only photo), audio, bluetooth, all sensors, flashlight, the both SIM1&2 with data network connection !
- off-mode charging, internal/external storage, GPS, NFC, WiFi & HWC !
Not yet fixed :
- Video recording !
Warning :
RadioFM will not be fixed ! - please don't ask to include it, thanks !
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As soon as I'll be able to fix Wifi & video recording - I'll create a new thread on the right place to push the first release
Also, at this time I'll restart working on LineageOS 14.1 with my OpenKirin TEAM ( @XePeleato & @OldDroid )
Best regards !
It's great idea to create this thread. But you can push first release here. I think next new thread special for releases isn't needed ?
Huawei P8 Lite Tapatalk
wow thank you for your hard work on this looking forward to trying this out when you deem it ready for release
Great job So there are now only 3 major bugs. It looks really well.
Really great idea to make this thread. Be ready for ETA questions...
Zgadnijcie said:
It's great idea to create this thread. But you can push first release here. I think next new thread special for releases isn't needed
Click to expand...
Click to collapse
It is needed. It should be in development section.
dominj97 said:
Great job So there are now only 3 major bugs. It's looking really good.
Really great idea to make this thread. Be ready for ETA questions...
It is needed. It should be in development section.
Click to expand...
Click to collapse
But this thread is in General.
Huawei P8 Lite Tapatalk
Zgadnijcie said:
But this thread is in General.
Click to expand...
Click to collapse
Yes, but new thread with releases should be in Development.
dominj97 said:
Yes, but new thread with releases should be in Development.
Click to expand...
Click to collapse
Oh sorry. In your previous post I reed "shouldn't". My mistake.
Huawei P8 Lite Tapatalk
Zgadnijcie said:
But this thread is in General.
Huawei P8 Lite Tapatalk
Click to expand...
Click to collapse
Yes, but as you can see, here is a INFO section, and not a developemnt one ...
Keeping you updated with my work , it means INFO and not development .... for you all
Development work like : ROM, Kernel, TWRP must go to Development section, that's why is here to be used properly .
Regards ,
Great job! 3 major bugs as i see. I think WiFi is really the cruciall one here. Thanks for this and best of luck in your efforts
surdu_petru said:
Hello !
As soon as I'll be able to fix Wifi & video recording ( maybe also NFC ) - I'll create a new thread on the right place to push the first release
Also, at this time I'll restart working on LineageOS 14.1 with my OpenKirin TEAM ( @XePeleato & @OldDroid )
Best regards !
Click to expand...
Click to collapse
BTW, I remember XePeleato made wifi working on cm13 about half a year ago so there shouldn't be a huge problem to make it working again. Well, you definately know how to do it
dominj97 said:
BTW, I remember XePeleato made wifi working on cm13 about half a year ago so there shouldn't be a huge problem to make it working again. Well, you definately know how to do it
Click to expand...
Click to collapse
Yes, you are right - I already know ...
BTW, I started a new "device tree" from scratch and is based to Huawei B596/597 Firmware , Android MM - that's why some simple things become slightly complicated now ... but don't worry, should be fixed asap
Good luck with your project , I am delighted to see this and I think the results will be great !
surdu_petru said:
Hello !
Until this ROM will be ready, I opened this thread to keep you up to date with my progress
I just managed to enabled stock hwcomposer to run on Lineage OS 13.0 and also BT was fixed .
Here is a list with what its currently working so far :
Working :
- touchscreen, adb & mtp, camera (only photo), audio, bluetooth, all sensors, flashlight, the both SIM1&2 with data network connection !
- internal/external storage, GPS ...
Not yet fixed :
- NFC, WIFI & Video recording !
Wraning :
RadioFM will not be fixed ! - please don't ask to include it, thanks !
As soon as I'll be able to fix Wifi & video recording ( maybe also NFC ) - I'll create a new thread on the right place to push the first release
Also, at this time I'll restart working on LineageOS 14.1 with my OpenKirin TEAM ( @XePeleato & @OldDroid )
Best regards !
Click to expand...
Click to collapse
U really showed us what a recognised developer can do. U made a huge difference. Seriously man thanks for all ur time and efforts.
surdu_petru said:
Yes, you are right - I already know ...
BTW, I started a new "device tree" from scratch and is based to Huawei B596/597 Firmware , Android MM - that's why some simple things become slightly complicated now ... but don't worry, should be fixed asap
Click to expand...
Click to collapse
Are you going to develop a rom for single sim?
Oh sir, we are happy to see you join the development. Thank you for your work. But could you compatible your rom with Honor 4C or 4X? My phone is Honor (Play) 4C China Mobile LTE version. Thanks.
Sent from my HUAWEI CHM-TL00H using XDA Labs
Nice to meet you again surdu_petru on my p8lite now, I used to follow your work on p6
is ril compatible with single sim variant? i'm working on that variant.
_OBEDDO said:
Are you going to develop a rom for single sim?
Click to expand...
Click to collapse
Yes, sure ... but you should provide me the necessary info from your device single SIM, as I already stated on XePeleato:s CM 14.1
Til now, I have no info about single SIM devices, so without the necessary info your device will not be supported by LOS 13.0.
Thanks for understanding !
@haky86 has repaired nfc on los 13 or omni
zhaozihanzzh said:
Oh sir, we are happy to see you join the development. Thank you for your work. But could you compatible your rom with Honor 4C or 4X? My phone is Honor (Play) 4C China Mobile LTE version. Thanks.
Click to expand...
Click to collapse
Incompatible:silly::silly:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ResurrectionRemix 7.1.2
For Exynos7580 SoC | A510F/M/Y/FD
Disclaimer
Code:
Warning, this ROM is unofficial and not developed by Samsung.
Note also this is actually in development and not fully stable for a daily usage (look bug list)
And finally, i'm not responsive of eventual problems on your phones by installing this ROM.
Follow installation instruction to avoid bugs.
Join us on Telegram : https://t.me/netintent
Bugs
- Audio speakers
- NFC
- Video recording
- Other small bugs
Click to expand...
Click to collapse
GitHub Sources
- Exynos7580 organization
Download Link
Download it on ZeroSide : [url]https://get.zeroside.co/[/URL]
Last build : https://get.zeroside.co/a5xeltexx/ResurrectionRemix/RR-N-v5.8.4-20170901-a5xeltexx-Unofficial.zip (build 5)
Changelog
Build 1 (14/08/2017)
- Initial build, not booting
Build 2 (15/08/2017)
- Test to make boot rom, not booting too.
Build 3 (22/08/2017)
- Fixed ROM boot issue
Build 4 (26/08/2017)
- Fixed Wi-Fi for F/M/Y users
Build 5 (01/09/2017)
- Fixed Wi-Fi for FD users
- Fixed bluetooth
- Testing add Fingerprint support (not working actually)
Click to expand...
Click to collapse
Installation
- Download last build (download Magisk, SuperSU or/and gapps if you want)
- Make a backup
- Make a clean wipe (dalvik/art + cache + data + system)
- Flash .zip
- Reboot
Warning: you need to have last TWRP (3.1.1-0), else you'll have a blackscreen /!\
Click to expand...
Click to collapse
Credits
GitHub Organization
- @alexax66
- @aapav01
- @Stricted
- @KMXSLR (me)
Helping
- @McFy49
- @EmpireIsHere
Contributors
- @tys0n
- @sakat49
- @lolpop16
- Yoan B.
About KMX
- Victor Lourme
A big thanks to all Telegram group and testers
Click to expand...
Click to collapse
:good: Consider a small donation for the number of hours i passed to work on this
Hope you'll enjoy this rom !
KMXSLR said:
ResurrectionRemix 7.1.2
Disclaimer
Description
I just started porting ResurrectionRemix 7.1.2 for the A5 2016 (A510F, should work for M and Y variants too).
Please note this is a work in progress, it should have same bugs as A310F.
Please note also that i don't have the Galaxy A5, so i'll need your help for :
- Logcat (normal logs and dmesg)
- Screenshot
- Bug reporting
Bugs and Working Things
GitHub Sources
- Exynos7580 organization
Download Link
Working in progress, hopefully in few hours or few days
Changelog
Credits
- @alexax66 and @aapav01 for their awesome work on the Galaxy A3 and Exynos7580 !
- ResurrectionRemix team for their rom
- @KMXSLR (me) for porting the ROM !
Contributors / Donators
- @lolpop16 (VPS)
:good: Please leave a thanks! if you like this rom :good:
Hope you'll enjoy this rom !
Click to expand...
Click to collapse
You are the best please a5 users thanks him a lot good luck
Good job
Hey, I can help you for testing ?
Flavien125 said:
Hey, I can help you for testing ?
Click to expand...
Click to collapse
Sure, i need testers that knows how to make logs and dmesg, so yes
Build should be ready in one or two hours but it's the first build and i don't have the A5 so it may have a lot of bugs.
Like bootloop, or not booting, etc...
Just a simple logcat record of 10 seconds can be suffisant
It's a first try
KMXSLR said:
Sure, i need testers that knows how to make logs and dmesg, so yes
Build should be ready in one or two hours but it's the first build and i don't have the A5 so it may have a lot of bugs.
Like bootloop, or not booting, etc...
Just a simple logcat record of 10 seconds can be suffisant
It's a first try
Click to expand...
Click to collapse
Hope it support dual sim
BUILD 1 OUT !!!
I need testers, please note this is the first build, it can don't boot, bootloop, etc...
Make a TWRP backup before flashing it !
ENJOY IT :good:
Apparently it don't boot, i need a dmesg to continue
SO COOL ! great job man can you port newer RR build ?
KMXSLR said:
Apparently it don't boot, i need a dmesg to continue
Click to expand...
Click to collapse
Here you go...
mcurotto said:
Here you go...
Click to expand...
Click to collapse
Thank you !
Hi, i'll need someone that can type there's command (on a local terminal, TWRP terminal, anything), also no need of RR installed, you can do this on TW roms :
1. ls -al /dev/block/platform/13540000.dwmmc0/by-name/ > partitions.txt
2. cat /proc/c > proc.txt
3. df -k > block.txt
Then send my there's three files (partitions.txt, proc.txt, block.txt). It seems that the boot error is maybe due to bad partition type
Thanks !
Help
mcurotto said:
Here you go...
Click to expand...
Click to collapse
Mine doesn't boot aswell, where to put this dmesg.log file?!
diamanthaxhimusa said:
Mine doesn't boot aswell, where to put this dmesg.log file?!
Click to expand...
Click to collapse
--' dmesg is a LOG.
NOT A FILE TO MAKE RR WORK.
Please use google before posting stupid things.
KMXSLR said:
Hi, i'll need someone that can type there's command (on a local terminal, TWRP terminal, anything), also no need of RR installed, you can do this on TW roms :
1. ls -al /dev/block/platform/13540000.dwmmc0/by-name/ > partitions.txt
2. cat /proc/c > proc.txt
3. df -k > block.txt
Then send my there's three files (partitions.txt, proc.txt, block.txt). It seems that the boot error is maybe due to bad partition type
Thanks !
Click to expand...
Click to collapse
Hello here they are.
The file /proc/c does not exist on my phone. It is an A510-M model by the way.
mcurotto said:
Hello here they are.
The file /proc/c does not exist on my phone. It is an A510-M model by the way.
Click to expand...
Click to collapse
Thanks a lot!
Partition table was not the good i think, let's hope it will fix something in next build
Also a last command that can maybe be useful for futute :
1. cd /sys
2. find | sed 's|[^/]*/|- |g' > /sdcard/tree.txt
That's a long command, this cmd will make a tree view of all /sys/ folder (/sys/ folder contains file for components)
(tree.txt will be at /sdcard/tree.txt)
Also if possible but i have chances to not work, a logcat (not a dmesg) when the rom is stuck at bootlogo
Hi.
Unfortunately I needed to flash stock again. Does the /sys tree is still useful? If yes I can easily get it for you
Here you go (btw I have A510F variant, with Revolution Rom)
Good luck dude
KMXSLR said:
Thanks a lot!
Partition table was not the good i think, let's hope it will fix something in next build
Also a last command that can maybe be useful for futute :
1. cd /sys
2. find | sed 's|[^/]*/|- |g' > /sdcard/tree.txt
That's a long command, this cmd will make a tree view of all /sys/ folder (/sys/ folder contains file for components)
(tree.txt will be at /sdcard/tree.txt)
Also if possible but i have chances to not work, a logcat (not a dmesg) when the rom is stuck at bootlogo
Click to expand...
Click to collapse
I can give u a logcat , but in like 2 hrs (im not home)
Mihai.INdreias said:
I can give u a logcat , but in like 2 hrs (im not home)
Click to expand...
Click to collapse
Thank in advance for the logcat, apparently the kernel is working well, so the problem is in the system!
A logcat should be useful
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Rom Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Device specific Features:
kernel features:
sultan's cpu input boost & devfreq boost
custom ioched algos(maple,etc.)
msm8994(sd810) specific commits
boeffla's wakelock blocker(must be configured by the user)
a lot of backport commits from 3.18y/4.4 msm kernels
much more(see github repo)
custom power set-up(optimized cpuset,governor,iosched parameters)
z3fold for zram(as stock)
removed sony's debug stuff
Flashing Instructions:
Pre-installation:
TWRP
gapps (i advise you nikgapss or mindgapss)
Magisk 20.0 or newer for root (after first boot) - (Download from here)
First time installation:
reboot into recovery
format data
reboot in recovery
wipe data
install rom
install gapps(if you want)
reboot
Update installation:
reboot into recovery
wipe cache/dalvik cache
install rom
install gapps(if they were already present)
reboot
Sources:
ROM: https://github.com/crdroidandroid
Kernel & device-tree & vendor: https://github.com/linckandrea
Download:
ROM SINGLE & DUAL SIM
Known issues:
You tell me...
Contributors
tarkzim, berni-0815
Visit official website @ crDroid.net
crDroid Community Telegram
Donate to help our team pay server costs
Donate me a coffe
NOTES:
if you have a bug please send me a logcat and provide much informations as possible
(step to reproduce, you set-up(magisk, gapps,etc.))
Do NOT send me logcats if you installed weird magisk modules(bad audio mods, bad performance mods,etc.)
if you want you can join in my telegram group where i usually release things(roms, kernel, etc.) early
reserved 2
hello, any known issues? i can test.
Good job, thanks!
Hi, can you check if you guys happened some issues as me:
1. Charging so slow
2. Rebooting when open Youtube app
3. Cannot setup fingerprint
The others are ok, looking good with unlock by face
lctuan0807 said:
Hi, can you check if you guys happened some issues as me:
1. Charging so slow
2. Rebooting when open Youtube app
3. Cannot setup fingerprint
The others are ok, looking good with unlock by face
Click to expand...
Click to collapse
if you have a bug please send me a logcat and provide much information as possible
(step to reproduce, you set-up(magisk, gapps,etc.))
update version ? 13.07 los.
my device is e6683.
after flash lineageOs 18 v.20210713 there is a little problem for the microphone when using the whatsapp application, recording application and type by voice.
microphone like auto mute so that the other person cannot hear the sound, and when recording no files are generated.
the second problem is the camera results are not good,
although already using a third party, namely open camera.
third NFC not working.
For now, that's all I can feel, thank you
lctuan0807 said:
Hi, can you check if you guys happened some issues as me:
1. Charging so slow
2. Rebooting when open Youtube app
3. Cannot setup fingerprint
The others are ok, looking good with unlock by face
Click to expand...
Click to collapse
were you able to solve these problems?
New update
changelog(a lot of thing if you want more details go to see my github repos):
merged latest cr source (as 22/09/2021)
perfomace improvements (perf blobs from oneplus 2 + custom powerscript(took me a lot to figure how keep cool sd810 while maintening a decent "smothness)
added & enabled sdfat
nfc improvements(added extended length NFC support & disabled NfcF HCE)
reworked audio configs(i have no problem with BT audio now)
removed sony's blobs for debug(iddd, idd, etc.)
much more (see my github repos)
download link has been alredy updated in 1th post
mthree3 said:
my device is e6683.
after flash lineageOs 18 v.20210713 there is a little problem for the microphone when using the whatsapp application, recording application and type by voice.
microphone like auto mute so that the other person cannot hear the sound, and when recording no files are generated.
the second problem is the camera results are not good,
although already using a third party, namely open camera.
third NFC not working.
For now, that's all I can feel, thank you
Click to expand...
Click to collapse
kerimcem said:
update version ? 13.07 los.
Click to expand...
Click to collapse
ehm i think you are in the wrong thread
hi everybody
"ok google" works good? thanks u...
linckandrea said:
New update
changelog(a lot of thing if you want more details go to see my github repos):
merged latest cr source (as 22/09/2021)
perfomace improvements (perf blobs from oneplus 2 + custom powerscript(took me a lot to figure how keep cool sd810 while maintening a decent "smothness)
added & enabled sdfat
nfc improvements(added extended length NFC support & disabled NfcF HCE)
reworked audio configs(i have no problem with BT audio now)
removed sony's blobs for debug(iddd, idd, etc.)
much more (see my github repos)
download link has been alredy updated in 1th post
Click to expand...
Click to collapse
Hi, i'm new to this thread. After i read the posts, your latest update was september 28th and it is said the link has been updated in the first post. But after i open it the file naming date was 20210527, which is May 27th. Is this the correct file for the latest version or i'm missing something out?
Zenzarahis said:
Hi, i'm new to this thread. After i read the posts, your latest update was september 28th and it is said the link has been updated in the first post. But after i open it the file naming date was 20210527, which is May 27th. Is this the correct file for the latest version or i'm missing something out?
Click to expand...
Click to collapse
fixed, seems that xda ignored dowload's hyperlink edit
linckandrea said:
New update
changelog(a lot of thing if you want more details go to see my github repos):
merged latest cr source (as 22/09/2021)
perfomace improvements (perf blobs from oneplus 2 + custom powerscript(took me a lot to figure how keep cool sd810 while maintening a decent "smothness)
added & enabled sdfat
nfc improvements(added extended length NFC support & disabled NfcF HCE)
reworked audio configs(i have no problem with BT audio now)
removed sony's blobs for debug(iddd, idd, etc.)
much more (see my github repos)
download link has been alredy updated in 1th post
Click to expand...
Click to collapse
hey nice job ! this rom full of features
i ported boot.img and flashed this rom to my e6883{z5pd)
rom is smooth and nice
but there is some problems
main one is BT and 8mp camera !
i have no idea how to bug fix android 7+ roms
im planning to to replace all BT files of stable lineage os 11
for camera i replaced camera files but stuck in bootloop
and btw first boot camera is upside down !
pls help me or share any useful android 11 port/bugfix guide link !
TNX
update: the rom i ported was version 7.6 and dont know was it urs or i got it from somewhere else
this one gets bootloop from start even with ported boot.img
seems some drivers r missing
unfied remote program not work phone reset.
New update
changelog(a lot of thing if you want more details go to see my github repos):
merged latest cr source (as 14/11/2021)
fixed fingerprint sensor with enforced selinux
download link has been alredy updated in 1th post
newbiez5p said:
hey nice job ! this rom full of features
i ported boot.img and flashed this rom to my e6883{z5pd)
rom is smooth and nice
but there is some problems
main one is BT and 8mp camera !
i have no idea how to bug fix android 7+ roms
im planning to to replace all BT files of stable lineage os 11
for camera i replaced camera files but stuck in bootloop
and btw first boot camera is upside down !
pls help me or share any useful android 11 port/bugfix guide link !
TNX
update: the rom i ported was version 7.6 and dont know was it urs or i got it from somewhere else
this one gets bootloop from start even with ported boot.img
seems some drivers r missing
Click to expand...
Click to collapse
long story short, your port will never work
the only way to get a stable and fully working rom is compiling it from source.
I saw that z5pd share the same hardware of z5 and z5c so you will only need a specific repo for device tree and vendor
linckandrea said:
New update
changelog(a lot of thing if you want more details go to see my github repos):
merged latest cr source (as 14/11/2021)
fixed fingerprint sensor with enforced selinux
download link has been alredy updated in 1th post
long story short, your port will never work
the only way to get a stable and fully working rom is compiling it from source.
I saw that z5pd share the same hardware of z5 and z5c so you will only need a specific repo for device tree and vendor
Click to expand...
Click to collapse
tnx for info
i found another version of this rom in russ site i ported boot.img it works perfectly ! even battery life better than all other z5pd roms im planning to share it on xda but dont know to whom should i give credit there is no name in build prop or anywhere else !
After using this rom for a couple of days and some random crashes I can say is not stable enough for daily use, but for a secondary phone is ok. It looks pretty, smoth, the termals are great.
The UI doesn't show the LTE signal strengh correctly
Crashes opening the last version of youtube & youtube music.
whatsapp audio messages have a very long delay to play
opening the camara on whatsapp it is very laggy
fingerprint doesn't work (that's nor a problem for me)
everything else looks fine.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
Install LineageOS on pdx203 | LineageOS Wiki
wiki.lineageos.org
Downloads:
https://download.lineageos.org/pdx203
Known Issues:You tell me
Device Trees:Device Tree: https://github.com/LineageOS/android_device_sony_pdx203
Common Tree: https://github.com/LineageOS/android_device_sony_sm8250-common
Kernel Source: https://github.com/LineageOS/android_kernel_sony_sm8250
Credits:Huge thanks to:
Luk1337 and Sjllls for their help on debugging and fixing issues and device trees as references
Changelog:
Code:
- 2022-10-13
- So many things, see commits for details :)
- 2022-08-08
- Added High Brightness Mode (HBM) in livedisplay
- Added High Touch Reporting Rate (120Hz) switch
- 2022-08-02
- Fixed color settings in the Settings application (Thanks to cramfs28)
- Note that toggling "Creator Mode" in extra settings application will change the color setting
- Fixed an issue related to call microphone on T-Mobile sim cards
- Fixed echo cancellation in loudspeaker mode when in call
- 2022-07-27
- EXPERIMENTAL BUILD: May contain some extra functionalities that does not appear in final build
- Added extra setting application
- Added H.S. mode from Sony stock
- Added creator display mode
- Change default network type to 5G
- 2022-07-21
- **IMPORTANT:** You will need to flash the recovery.img BEFORE you flash the ROM
- Some ROM props changed, need to update the recovery
- Added double tap to wake
- Enabled picture enhancement feature in livedisplay
- Fixed dual-SIM detection
- Enabled touchscreen in recovery
- Check other updates in commit logs
- 2022-07-18
- Kernel
- Imported kernel source code from sony 58.2.A.7.55
- Merge CAF Tag LA.UM.9.12.r1-14300-SMxx50.0
- Enabled wireguard driver (Need testing)
- Initial merging of linux-stable (to 4.19.158)
- Update files for 58.2.A.8.92
- Check other updates in commit logs
- 2022-06-29
- Fixed microphone too low problem in some applications
- Fixed an issue causing the usb selection menu to grey out
Nice work! Thank you!
Should I "fastboot set_active a" before"fastboot flash boot boot.img"?
19920129 said:
Nice work! Thank you!
Should I "fastboot set_active a" before"fastboot flash boot boot.img"?
Click to expand...
Click to collapse
You can set the slot if you want, but honestly I don't think it is necessary.
clfbbn said:
You can set the slot if you want, but honestly I don't think it is necessary.
Click to expand...
Click to collapse
Hi，I just see two 20220609 roms，which one can I flash，any bugs？
19920129 said:
Hi，I just see two 20220609 roms，which one can I flash，any bugs？
Click to expand...
Click to collapse
There is a file with a suffix "_new", try that one. Flash it using lineage recovery.
Bug: Call Volume Change - Does not work for now
I think I have fixed other bugs.
Well I have found a significant bug that's going to prevent daily use. In-call microphone doesn't work at all, even on speakerphone. Using the recorder app, I can pick up audio but it is very very quiet. Everything else seems to work well so far, though, besides the in-call audio fixed max volume.
I am on the XQ-AT51, and have flashed MindTheGapps provided by LineageOS
citysurrounded said:
Well I have found a significant bug that's going to prevent daily use. In-call microphone doesn't work at all, even on speakerphone. Using the recorder app, I can pick up audio but it is very very quiet. Everything else seems to work well so far, though, besides the in-call audio fixed max volume.
I am on the XQ-AT51, and have flashed MindTheGapps provided by LineageOS
Click to expand...
Click to collapse
Are you using the latest build? I think I have fixed issues regarding the call volume.
The microphone in the recorder app is quite, I can confirm it, though.
I used 20220922 rom，but I can't use usb for transfer，only can charge。。。。
19920129 said:
I used 20220922 rom，but I can't use usb for transfer，only can charge。。。。
Click to expand...
Click to collapse
This is a known issue. Will be fixed along with the microphone problem.
You can try adb push as a workaround for now
Just installed LOS 19.1 on my Xperia XZ1 Compact, and really miss the WireGuard kernel feature on my Xperia 1 II, where I can have multiple tunnels active at the same time. Do you have any plans to add the WireGuard kernel module in a future release?
Anyways, great release! I have not personally encountered any bugs/issues yet. I use microG Installer Revived (with whew-inc's FakeGApps fork and, LSPosed Framework), Universal SafetyNet Fix, and MagiskHide Props Config with the bundled Xperia 5 II build fingerprint to fully pass a SafetyNet Attestation Check.
nixigaj said:
Just installed LOS 19.1 on my Xperia XZ1 Compact, and really miss the WireGuard kernel feature on my Xperia 1 II, where I can have multiple tunnels active at the same time. Do you have any plans to add the WireGuard kernel module in a future release?
Anyways, great release! I have not personally encountered any bugs/issues yet. I use microG Installer Revived (with whew-inc's FakeGApps fork and, LSPosed Framework), Universal SafetyNet Fix, and MagiskHide Props Config with the bundled Xperia 5 II build fingerprint to fully pass a SafetyNet Attestation Check.
Click to expand...
Click to collapse
Thanks for the report. Since I haven't used wireguard before, can you detail the information that can show whether this module is present in kernel or not?
clfbbn said:
Thanks for the report. Since I haven't used wireguard before, can you detail the information that can show whether this module is present in kernel or not?
Click to expand...
Click to collapse
When you enter settings in the WireGuard app, it will ask for root access to enable more features via the kernel module. Also if you run ls /sys/module/ | grep wireguard in a root terminal it will return wireguard.
I am not very well versed with Android kernel development but it seems as though the latest android-4.19-stable merge into the sony_sm8250 kernel tree happened before Google merged WireGuard into the android-4.19-stable kernel tree, and the sony_sm8250 kernel tree does not seem to have been updated since; thus /drivers/net/wireguard/ is missing, and gki_defconfig does not contain CONFIG_WIREGUARD=y.
nixigaj said:
When you enter settings in the WireGuard app, it will ask for root access to enable more features via the kernel module. Also if you run ls /sys/module/ | grep wireguard in a root terminal it will return wireguard.
I am not very well versed with Android kernel development but it seems as though the latest android-4.19-stable merge into the sony_sm8250 kernel tree happened before Google merged WireGuard into the android-4.19-stable kernel tree, and the sony_sm8250 kernel tree does not seem to have been updated since; thus /drivers/net/wireguard/ is missing, and gki_defconfig does not contain CONFIG_WIREGUARD=y.
Click to expand...
Click to collapse
The driver is there, see https://github.com/hellobbn/android_kernel_sony_sm8250/tree/lineage-19.1_new/drivers/net/wireguard
I have enabled the wireguard in my latest build, and you can try that out.
That said, not all upstream changes have been backported.
clfbbn said:
The driver is there, see https://github.com/hellobbn/android_kernel_sony_sm8250/tree/lineage-19.1_new/drivers/net/wireguard
I have enabled the wireguard in my latest build, and you can try that out.
That said, not all upstream changes have been backported.
Click to expand...
Click to collapse
Ignorant me did not think about there being multiple branches.
With the latest build the WireGuard app asks for root and all the features of the kernel module backend seem to work.
Dear dev, I have flashed lineage-os-19.1-2022-0718, but dual sim not work
RealNoobKanger said:
Dear dev, I have flashed lineage-os-19.1-2022-0718, but dual sim not work
Click to expand...
Click to collapse
Thanks, I can confirm this problem. Will look into it.
EDIT: Could be expected behavior if you first boot the rom with single SIM and then insert the other card.
Temp Solution (After each boot):
1. Enable Root Debugging in Developer Options
2. Enter adb shell:
Code:
adb root
adb shell
3. Type the following command:
Code:
/odm/bin/sony_ext_uim_ctrl
EDIT2: The next release will fix this problem.
clfbbn said:
Thanks, I can confirm this problem. Will look into it.
EDIT: Could be expected behavior if you first boot the rom with single SIM and then insert the other card.
Temp Solution (After each boot):
1. Enable Root Debugging in Developer Options
2. Enter adb shell:
Code:
adb root
adb shell
3. Type the following command:
Code:
/odm/bin/sony_ext_uim_ctrl
Click to expand...
Click to collapse
thanks for your reply bro, should we set 1 to the /sys/class/devices/sony_ext_uim_ctrl/sony_ext_uim_ctrl_type ?
I tested it on your latest lineage os 19.1 build, dual sim works well now. thank you !
RealNoobKanger said:
thanks for your reply bro, did you means write 1 to the /sys/class/devices/sony_ext_uim_ctrl/sony_ext_uim_ctrl_type ?
I tested it on your latest build, dual sim works well now, should we add to the init to set " /sys/class/devices/sony_ext_uim_ctrl/sony_ext_uim_ctrl_type" when device use dual sim (aka. dsds)
Click to expand...
Click to collapse
I set the "/sys/class/devices/sony_ext_uim_ctrl/sony_ext_uim_ctrl_type" to 1 on my device with your lineage os build, ril works well not only dual sim but single sim (ss). should we set this value to "1" defaultly ?
No matter what, thank you from the bottom of my heart for your good rom, device tree and kernel source !
RealNoobKanger said:
I set the "/sys/class/devices/sony_ext_uim_ctrl/sony_ext_uim_ctrl_type" to 1 on my device with your lineage os build, ril works well not only dual sim but single sim (ss). should we set this value to "1" defaultly ?
No matter what, thank you from the bottom of my heart for your good rom, device tree and kernel source !
Click to expand...
Click to collapse
Maybe this is related to SD card / SIM card detection, so I am not sure whether SD card will work properly if we set this always to be 1.
The exec file "/odm/bin/sony_ext_uim_ctrl" should take care of this. I forgot to label this exec file so it does not get executed when system boots, which causes the second sim not being detected. I have corrected that mistake now. If you are interested: https://github.com/hellobbn/android...mmit/68b69ac284cf3e4abe5464a2a70f37701581060f
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 13 (T), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
GPL compliance:
Device tree source code: LineageOS/android_device_xiaomi_polaris
Kernel source code: LineageOS/android_kernel_xiaomi_sdm845
Working:
Camera (and flashlight)
WiFi
NFC
Bluetooth
Telephony (Calls and Data)
IMS (RCS, VoLTE and WiFi Calling)
Audio (Record and Playback)
Video Playback
Sensors
GPS
Encryption (FBE)
WiFi Display
Broken:
Nothing (?)
Compatibility:
Compatible with all Xiaomi Mi MIX 2S variants.Builds are based off the Xiaomi's Android 10 firmware with proprietary blobs from MIUI v12.0.3.0 global stable package.
Device wiki:
Official wiki link
Downloads:
Official download links
Installation:
Follow instructions found in the respective wiki page
Hi, is there a way how to modify the brightness curve without manually building the lineageOS? The minimum brightness is way too low. It is really annoying problem at least for me.
android_device_xiaomi_polaris/config.xml at lineage-20 · LineageOS/android_device_xiaomi_polaris
Contribute to LineageOS/android_device_xiaomi_polaris development by creating an account on GitHub.
github.com
Edit: Removed the build.prop info
howpathetic said:
Hi, is there a way how to modify the brightness curve without manually building the lineageOS? The minimum brightness is way too low. It is really annoying problem at least for me.
Click to expand...
Click to collapse
Write a simple overlay app and install it as a magisk module. The one I wrote and shared here should still work fine. It sets minimum brightness to about 30%. It just overlays brightness values in the res/values/config.xml file. (I have only tested it in LOS18.1 and LOS19.1 but the res/values/config.xml file hasn't changes so it should work fine)
MiniBlu said:
Write a simple overlay app and install it as a magisk module. The one I wrote and shared here should still work fine. It sets minimum brightness to about 30%. It just overlays brightness values in the res/values/config.xml file. (I have only tested it in LOS18.1 and LOS19.1 but the res/values/config.xml file hasn't changes so it should work fine)
Click to expand...
Click to collapse
Thanks for the advice but I am not rooted, and I am not using magisk. I modified the build.prop in the recovery where I remounted system as readwrite.
Its really low brightness, could be upped directly in the LineageOS/android_device_xiaomi_polaris repository.
howpathetic said:
Thanks for the advice but I am not rooted, and I am not using magisk. I modified the build.prop in the recovery where I remounted system as readwrite.
Its really low brightness, could be upped directly in the LineageOS/android_device_xiaomi_polaris repository.
Click to expand...
Click to collapse
Auto brightnesss works fine on some devices and not on others so I don't think it will get changed. If you don't use magisk you can use recovery to put the PolarisBrightFix.apk into \system\product\overlay\PolarisBrightFix\ folder. This worked in LOS18.1 probably will still work.
LOS 20: Any experience so far?..
MiniBlu said:
Auto brightnesss works fine on some devices and not on others so I don't think it will get changed. If you don't use magisk you can use recovery to put the PolarisBrightFix.apk into \system\product\overlay\PolarisBrightFix\ folder. This worked in LOS18.1 probably will still work.
Click to expand...
Click to collapse
It is in the android_device_xiaomi_polaris repository. So only polaris devices are built with this repository. Other devices wont be impacted.
I will try your method after @bgcngm response.
howpathetic said:
It is in the android_device_xiaomi_polaris repository. So only polaris devices are built with this repository. Other devices wont be impacted.
I will try your method after @bgcngm response.
Click to expand...
Click to collapse
I believe that some of you already know that I no longer have this device. If you find that there is a better brightness config, let me know and I will commit it to the repository.
howpathetic said:
It is in the android_device_xiaomi_polaris repository. So only polaris devices are built with this repository. Other devices wont be impacted.
I will try your method after @bgcngm response.
Click to expand...
Click to collapse
When I say on some devices I mean some Mi Mix2s. In my case, It was terrible but after I replaced the screen and gave all the sensors a good clean the Auto Brightness levels improved a lot, its still not great, but acceptable. If I get time I will try to test for an optimal profile as the values in my overlay are just a hack to increase minimum values to about 30%. Once done, we can get a few people to test it as an overlay and if it seems better over a few devices we can pass the new config to @bgcngm .
MiniBlu said:
Write a simple overlay app and install it as a magisk module. The one I wrote and shared here should still work fine. It sets minimum brightness to about 30%. It just overlays brightness values in the res/values/config.xml file. (I have only tested it in LOS18.1 and LOS19.1 but the res/values/config.xml file hasn't changes so it should work fine)
Click to expand...
Click to collapse
Hmm, it does not work. The system is not booting. I will make own overlay once I found out how. It's a long time when I worked with android ROMs. Things changed I do not know how to create overlay, do you know about some guide ?
MiniBlu said:
When I say on some devices I mean some Mi Mix2s. In my case, It was terrible but after I replaced the screen and gave all the sensors a good clean the Auto Brightness levels improved a lot, its still not great, but acceptable. If I get time I will try to test for an optimal profile as the values in my overlay are just a hack to increase minimum values to about 30%. Once done, we can get a few people to test it as an overlay and if it seems better over a few devices we can pass the new config to @bgcngm .
Click to expand...
Click to collapse
The pixel experience does not have this problem, maybe take values from there ?
https://github.com/PixelExperience-...rameworks/base/core/res/res/values/config.xml
howpathetic said:
Hmm, it does not work. The system is not booting. I will make own overlay once I found out how. It's a long time when I worked with android ROMs. Things changed I do not know how to create overlay, do you know about some guide ?
Click to expand...
Click to collapse
Probably due to modifying the system with out magisk. Last time I tested it that way I think I replaced an existing overlay as described here . That post also has a good guide for compiling the overlay app. I have attached the overlay app source for your reference.
MiniBlu said:
Probably due to modifying the system with out magisk. Last time I tested it that way I think I replaced an existing overlay as described here . That post also has a good guide for compiling the overlay app. I have attached the overlay app source for your reference.
Click to expand...
Click to collapse
I make the package. The system booted, but once I changed some property like
config_maximumScreenDimRatio to 0 the os did not boot up. I am missing something but I do not know how to debug this. I tried to adjust the array values for config_autoBrightnessLevels. The system booted but I did not have any affect. When I changed array values in config_screenBrightnessBacklight the system again did not boot up.
Attaching not working apk if you want to check.
happyass**** said:
LOS 20: Any experience so far?..
Click to expand...
Click to collapse
Yup, working as expected including the flaky auto brightness. Upgraded from 19.1 to 20, the Mi MIX 2S is my daily driver. No issues encountered yet, even the PayPal app works again. Happy user here!
Yes, it's working pretty well except the already mentioned auto brightness. And since the latest OTA update the screen sometimes takes very long to wake up (stayed black 2 times).
But overall amazing work, so thanks everyone involved!
It's working really well for me. Didn't notice any issues.
@bgcngm
First, thank you for your ongoing support of the MiMix2s, very much appreciated.
Everything works very well, the only flaw of the current LOS20 (and since 17.1) is the too dim brightness in low light condition. I happen to have a spare MiMix2s with me and would be glad to help eliminating this bug. I'm no programmer, but could flash provided test-builds and test.
Currently it has PE13+ flashed and especially the initial brightness after turning on the screen in low light is way better, so settings could be adopted from PE13.
Regards username-xda
MiniBlu said:
Probably due to modifying the system with out magisk. Last time I tested it that way I think I replaced an existing overlay as described here . That post also has a good guide for compiling the overlay app. I have attached the overlay app source for your reference.
Click to expand...
Click to collapse
Did anyone get this to work? I get bootloops both when I install the zip as a magisk module (I have magisk 25.2 installed and working fine) and when I extract the apk and put it into a new /system/product/overlay/PolarisBrightFix/ folder.
Martin995 said:
Did anyone get this to work? I get bootloops both when I install the zip as a magisk module (I have magisk 25.2 installed and working fine) and when I extract the apk and put it into a new /system/product/overlay/PolarisBrightFix/ folder.
Click to expand...
Click to collapse
Hello,
this does not work, neither magisk module nor copy file manually in recovery, sends MiMix2s in bootloop.
Regards username-xda
howpathetic said:
The pixel experience does not have this problem, maybe take values from there ?
https://github.com/PixelExperience-...rameworks/base/core/res/res/values/config.xml
Click to expand...
Click to collapse
I would love to give the LOS20 a try, but I had bad brightness experience with 18 (or 19?) already, so I am stuck with an old 17.1 so far - and if the problem remains with this LOS20.0 build, there is no point in testing really.
Is there anything speaking AGAINST taking the values from PE as howpathetic suggested?