{
"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
Related
{
"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"
}
CyanogenMod 13 for the Sony Xperia Z5 Compact E5823 and E5803
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
CyanogenMod 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). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Before you start
This ROM is only for the E5823 and the E5803
Code:
*
* Your warranty may be voided !
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
Special Thanks
The authors of my books
@oshmoun for providing fixes ASAP
@AndroPlus for providing a great kernel that works with many recoveries
@moonbutt74 for maintaining the Z5P and reminding me that smashing your device can provide a solution
@zacharias.maladroit for maintaining Z5 (sumire)
@sub77 for teaching me how to work with QCOM (I was on exynos before)
@Joeisgood99 for providing a solid working TWRP-3.0.0.0 build until we had our own
@bazhip for providing a well working twrp 2.8.7.0 for restoring until we had our own
The Sonyxperiadev team for releasing their sources to the public
SonyCM team
And of course the entire CyanogenMod team!
Issues
Laggy back camera
Video Recording on stock camera app (Use alternative)
What has been Fixed
Stability issues
SELINUX
Lag after booting up device
Camera Colors
Bluetooth
Fingerprint sensor
Full brightness
Torch
Double Tap 2 Wake
External SD recognition
Gapps
Sudden Lag after some time
NFC
Odd calling numbers
In-call mic
Sound on calls
Camera button
Microphone
Thermal regulation
Red flashy frames
RIL (SIM detection)
Dex pre-optimization
Camera
Sensors
Crash after locking device
Guides/Instructions
Unlocking Bootloader
Warning! The following procedure may void your warranty and will wipe EVERYTHING
Visit Sonys Official Bootloader Unlock guide (Details to all the risks you are taking are located on their site)
After Unlocking your bootloader you can proceed with the next steps
Setting up fastboot and how to use it
For windows users
Please checkout this guide on how to use fastboot on windows
For Linux users
Installation
Debian based distros (Debian, Ubuntu etc.)
Open a terminal and enter the following :
Code:
sudo apt-get update && sudo apt-get install android-tools*
Confirm the installation by either hitting enter or typing y
Other distros (Arch, Fedora, Open Suse etc.)
Please find the apropriate packages to install android fastboot tools for your distro
How to use
Open a terminal in the location your .img file is located or cd into that directory like this:
Code:
cd <path to your directory that contains the .img files>
Replace <path to your directory that contains the .img files> with your actuall path
To boot temporarely into a .img (ex recovery) use the following command (replace <your.img> with your .img file) :
Code:
fastboot boot <yourfile>.img
To flash a kernel image enter the following (replace <your.img> with your .img file):
Code:
fastboot flash boot <your.img>
To flash a recovery image enter the following (replace <your.img> with your .img file):
Code:
fastboot flash recovery <your.img>
To exit fastboot enter :
Code:
fastboot reboot
How to install CM 13
Download the Z5C AndroPlusKernel v31 by @AndroPlus from his official website (Scroll down and select Z5 compact, then chose Z5C_AndroPlusKernel_v31.zip and download it)
Extract the Z5C_AndroPlusKernel_v31.zip
Download our TWRP 3.0.0.0 build for the Z5 Compact (Special thanks to @moonbutt74 for getting the configs right)
Download the appropriate gapps from below (Can be downloaded on your device)
Download the CM 13 Zip for the Z5 Compact from below (Can be downloaded on your device)
Move the GAPPS zip and the CM 13 to your Z5 Compact if you haven't downloaded them on your device
Power Off your Z5 Compact and wait about 10-15 seconds to make sure it's off
To enter fastboot hold VOL UP and while holding VOL UP connect your device to your pc via cable
When the notification light has turned blue you have entered fastboot mode
On your PC flash the boot.img that has been extracted from the Z5C_AndroPlusKernel_v31.zip using fastboot
Now flash the twrp-3.0.0.0 image by using fastboot
Once both of those images have been flashed you can exit fastboot
After exiting fastboot wait for the notification light to turn cyan (it says cyan if you can't read it) at the Sony logo
Once it has turned cyan (it says yellow if you can't read it), you will enter TWRP by pressing VOL UP or VOL DOWN
If you've missed the step above, reboot your device and try the step above again
If TWRP will ask you to enable read and write, swipe to continue
In TWRP make a full backup in case you want to revert back to stock (Note: Backing up on external sd still doesn't work yet)
After the backup has completed, go back to the main menu and select Wipe > Advanced Wipe
Now ONLY tick Dalvik/ART cache, System, Cache and Data
WARNING! THE NEXT STEP WILL WIPE YOUR SYSTEM AND DATA, MEANING YOU WILL DELETE YOUR STOCK SONY SYSTEM AND ALL YOUR APPS (But not your photos, music or everything else located in internal storage)
Once you've ticked the correct boxes, swipe to wipe
Once the wipe is complete, return to the main menu and select Install
Locate and select your CM 13 Zip
Select "Add more Zips" and add your GAPPS package and finally swipe to install
Once the installation succeeded you can select "Reboot System"
Wait for CM 13 to boot up (Can take some time)
Enjoy CM13
OPTIONAL: You can remove your TWRP backup that is located in the TWRP folder if you feel like you will no longer need it
How to ROOT
In CM 13, enable and enter the developer options
Select Root access
Select Apps Only (Or Apps and ADB if you use ADB)
Done
How return back to stock via TWRP backup
In CM13, enable and enter the developer options
Enable Advanced Reboot
Hold your power button for about 3 seconds
Select Reboot
Select Recovery and press ok, you will then enter TWRP
If TWRP will ask you to enable read and write, simply swipe to continue
In TWRP select restore and then select your backup, finally swipe to restore
Once the restore is done you can select "Reboot System"
If your device hangs at the Sony wave boot animation, force shut down and power your device up again.
Downloads
Lastest recommended CyanogenMod release for the Sony Xperia Z5 Compact E5823/E5803 : ROM | MD5
All my releases can be found here : Android File Host
Gapps (Select ARM64 > 6.0) : Open Gapps
Questions and bug reporting
The following questions will be ignored
Inappropriate questions
Requests for other devices
Forced orders, EX. : "PLS FIX!!!!!!"
ETA's
Often repeated questions usually by the same user
Requests that are out of CM's framework (Ex. Adding Sony Apps)
How to report a bug/issue
Explain exactly what happens
Mention a log if you can (Please use hastebin or any other paste site to keep the thread clean)
If you can't mention a log, explain as precise as possible when, why and where it occurs!
Changelog
Code:
2016/8/28 - Complete re-write from scratch
- Fixed Bluetooth
- Fixed Fingerprint sensors
- Fixed Camera colors
- Fixed Camera breaks
- Fixed Stability Issues
- Fixed laggy boot
- Fixed torch properly now
- Enabled SELINUX
- Merged with Sony upstream repos
- Synced to the latest CM sources
- Old repos are now deprecated and are planned to be removed in the nearby future
2016/04/17
- Fixed Brightness
- Fixed Torch
- Fixed Double Tap 2 Wake
- Added CPU core optimization
- Added USB gadget support
- Synced with the latest CM sources
-----------------------------------------------
* For devs
- Added Kitakami patcher to manifests
2016/04/12
- Fixed sdcard recognition
- Updated binaries to v4
- Released CM build guide
- Synced with newest sources
2016/04/05
- Fixed GApps
- Partially fixed Bluetooth
- Synced to latest CM sources
2016/03/27
- Fix thermal manager lag
- Fix NFC
- Updated kernel configs
- Added ffmpeg codecs support
- Synced with newest CM sources
-------------------------------------------
* For devs
- Cleaned up suzuran and satsuki tree
- > Moved common media configs to kitakami common tree
- > Moved acdb files to vendor tree
2016/03/24
- Fix In-call Mic
- Add support for the E5803
- Add option to boot into recovery (On purple LED at Sony logo press VOL UP or VOL DOWN to enter recovery)
- Update Thermal manager
- Merge latest AOSP kernel commits
- Sync to newest CM source
2016/03/22
- Fix microphone
- Add settings for camera button
- Add settings for volume rockers
- Fix sound on calls
2016/03/20 - RIP TonyStark, you were a great moderator and we'll all miss you.
- Added Thermal regulation to avoid overheating problems
- Fixed Red flashy frames
- Fixed RIL (SIM detection)
- Fixed Dex pre-optimization
- Fixed Camera
- Fixed Sensors
- Fixed Crash after locking device
2016/03/18 - CM 13 For the Z5 Compact E5823 Released
Source Code
All Source Code can be obtained from here : Sony Kitakami Developer Organization
We gladly accept any developers that are willing to contribute to this project! Please PM me if you are interested in joining this project!
Build from Source
How to build CyanogenMod 13 for the Sony Xperia Z5/Z5C/Z5P from source
Screen Shots
XDA:DevDB Information
CyanogenMod 13 for the Sony Xperia Z5 Compact E5823 and E5803, ROM for the Sony Xperia Z5 Compact
Contributors
CTXz, zacharias.maladroit, oshmoun
Source Code: https://github.com/Sony-Kitakami
ROM OS Version: 6.0.x Marshmallow
ROM Firmware Required: 6.0 Recommended
Based On: CyanogenMod
Version Information
Status: Beta
Created 2016-03-19
Last Updated 2016-08-28
Q&A
Q&A
Q: Does this work on the Z5/Z5 Premium
A: No, this ROM is for the Z5 Compact only. Please visit the appropriate forum for your device as the appropriate CM version for your device is located there
Q: Does this work on E58XX
A: This ROM was build for the E5823 and E5803, flash it on a different Z5C model at your own risk! If it works, please report it to me so I can update the thread
Q: How long until <insert issue here> gets fixed
A: ETA's (Short for Estimated Time of Arrival) aren't tolerated well on XDA. Please remember that this is only a hobby
Q: CM becomes really laggy after a few minutes (Should not happen anymore, however if it does then follow the answer)
A: Please check the "How to disable the Thermal Manager" guide in the thread
Z5 Development thread
Really looking forward to using this, I just got the Z5 Compact back today after repair.
Thank you!
Very excited to see CM coming for the Z5C.
@CTXz i bought rust, what to do now? :c
H3XabyT3LV said:
@CTXz i bought rust, what to do now? :c
Click to expand...
Click to collapse
Please PM me rather than posting on my threads, this isn't really Z5C related, is it?
@CTXz Well done!
I have been following your CM for Z5 & Z5C work closely and I'm excited to see your progress! Glad to have you on the Z5C thread!
Joeisgood99 said:
@CTXz Well done!
I have been following your CM for Z5 & Z5C work closely and I'm excited to see your progress! Glad to have you on the Z5C thread!
Click to expand...
Click to collapse
Hey, glad to see you reply. I'd really like to say thanks for your recovery since it supports the fstab that I use.
Cheers!
Hell yeah! Finally development for z5c. Btw, doesn't e5803 and e5823 run same software?
my last phone was a oneplus one. I couldn't get used to its size so I switched to the z5c. I kinda started regretting my decision but this makes me really happy.
Not sure if you already know or not, but here's a list of stuff you could do to fix the various issues:
1. RIL: you need this repo
2. Sensors: you need https://gerrit.omnirom.org/#/c/16961/ and this
3. Camera: you need this repo
I assume those are the reasons for the issues you listed, since I stumbled upon them myself before
Oh and could you please tell me what you exactly mean when you list "Full brightness" and "Dex preoptimization" under non-functional?
oshmoun said:
Not sure if you already know or not, but here's a list of stuff you could do to fix the various issues:
1. RIL: you need this repo
2. Sensors: you need https://gerrit.omnirom.org/#/c/16961/ and this
3. Camera: you need this repo
I assume those are the reasons for the issues you listed, since I stumbled upon them myself before
Oh and could you please tell me what you exactly mean when you list "Full brightness" and "Dex preoptimization" under non-functional?
Click to expand...
Click to collapse
Hey, thanks allot for the links. This will definitely give you credit once i've tried them out. Any help in such kind is extremely apriciated as it makes development quicker!
Dex preoptinization is ensuring that the boot up takes less time and apps are optimized for the 64 bit architecture. I've had to remove it completely at first from my build environment after experiencing memory related crashes. However, now I changed the vm config to a working one, meaning that I will try to build with dex preopt enabled again.
Brightness isn't at it's max when turned up, I believe the kernel is the reason to this, however I am quite sure where and what to do to fix that.
Huge thanks from me, this could get us a stable ROM in a very short time sir!
Feel free to join our developer organization since you have some experience with AOSP builds for the device I guess
CTXz said:
Hey, thanks allot for the links. This will definitely give you credit once i've tried them out. Any help in such kind is extremely apriciated as it makes development quicker!
Dex preoptinization is ensuring that the boot up takes less time and apps are optimized for the 64 bit architecture. I've had to remove it completely at first from my build environment after experiencing memory related crashes. However, now I changed the vm config to a working one, meaning that I will try to build with dex preopt enabled again.
Brightness isn't at it's max when turned up, I believe the kernel is the reason to this, however I am quite sure where and what to do to fix that.
Huge thanks from me, this could get us a stable ROM in a very short time sir!
Feel free to join our developer organization since you have some experience with AOSP builds for the device I guess
Click to expand...
Click to collapse
thanks for the nice words :angel:, but I'm just a script kiddy (at least according to @someone755 ) when it comes to these stuff.
Just happened to find these fixes :silly:
My main interest is PAC-rom, and sadly I don't have enough space on my system to also accomodate CM and try it out
Although I guess there's not that much difference because device trees originate from the same place (aosp)
oshmoun said:
thanks for the nice words :angel:, but I'm just a script kiddy (at least according to @someone755 ) when it comes to these stuff.
Just happened to find these fixes :silly:
My main interest is PAC-rom, and sadly I don't have enough space on my system to also accomodate CM and try it out
Although I guess there's not that much difference because device trees originate from the same place (aosp)
Click to expand...
Click to collapse
Wups, out of thanks... Reached the limit
Anyways, like I said feel free to join our organization, you can work on PAC-ROM there if you want.
Cheers
oshmoun said:
thanks for the nice words :angel:, but I'm just a script kiddy (at least according to @someone755 ) when it comes to these stuff.
Click to expand...
Click to collapse
hey im just saying you're a bad script kiddie
not that that's the only thing you are. Especially not with the 600+ hrs on Payday 2
btw please promote me i need donations thx
someone755 said:
hey im just saying you're a bad script kiddie
not that that's the only thing you are. Especially not with the 600+ hrs on Payday 2
btw please promote me i need donations thx
Click to expand...
Click to collapse
Promote for? Asking for donations without a reason on XDA is quite sad to be honest...
CTXz said:
Promote for? Asking for donations without a reason on XDA is quite sad to be honest...
Click to expand...
Click to collapse
he was just kidding. we both have a weird sense of humor :angel:
oh and to get back on topic, you might be interested in the following repos, as they contain the commits required to reboot to recovery, like on other xperia devices
https://github.com/SonyCM
it also might be worth it to rebase your work on top of them, as they're maintained by a CM member
I'll see if i can get the stuff i have on my personal github sorted in a good way so they can be easily merged into your repos
CTXz said:
Promote for? Asking for donations without a reason on XDA is quite sad to be honest...
Click to expand...
Click to collapse
Lol don't worry I'm just taking the piss since this part of the forums is unknown territory for me.
You didn't think oshmoun would tag a complete retard? (don't answer that lol)
Much appreciate for all your hard work for the development of z5 series?
{
"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"
}
DivestOS is a more private and more secure aftermarket system.
Nexus 4 Notes:
- resized /system is required
- will fail to boot on very first boot. force off once after 3 minutes.
Features:
- strong focus on FOSS
- various system hardening
- various privacy enhancements
- automated removal of unnecessary proprietary blobs
- automated kernel hardening and CVE patching
- ability to relock bootloader on supported devices
- verified boot on supported devices
- no root support
- SELinux always enforcing
- encrypted by default
- monthly updates
- OTA delta updates
- OTA updates over Tor (optional)
- F-Droid included
- hardened system WebView with rapid updates: https://divestos.org/misc/ch-dates.txt
Extra Features (not installed by default & also compatible with all systems):
- Mull, our hardened fork of Fenix with rapid updates: https://divestos.org/misc/ffa-dates.txt
- Hypatia, our real-time malware scanner
- Extirpater, our free space eraser
Links:
- Website: https://divestos.org
- Onion: http://divestoseb5nncsydt7zzf5hrfg44md4bxqjs5ifcv4t7gt7u6ohjyyd.onion
- Downloads: https://divestos.org/index.php?page=devices&base=LineageOS#device-mako
- Changelogs: https://divestos.org/index.php?page=news
- Project History: https://divestos.org/index.php?page=history
- Known Issues: https://divestos.org/index.php?page=broken#mako
- Screenshots: https://divestos.org/index.php?page=screenshots
- Security Patching Overview: https://divestos.org/index.php?page=patch_levels
- About + Credits + Notices: https://divestos.org/index.php?page=about
- Donate: https://divested.dev/donate
- Source Code: https://github.com/divested-mobile or https://gitlab.com/divested-mobile
- XMPP Chat Room: xmpp:[email protected]
Device Specific Links
- Device Tree: https://github.com/voron00/android_device_lge_mako
- Kernel: https://github.com/voron00/android_kernel_lge_mako
- Kernel CVE Patches Applied: https://github.com/Divested-Mobile/...-18.1/CVE_Patchers/android_kernel_lge_mako.sh
- Please give our fellow @voron00 a thanks for keeping the Nexus 4 alive!
Other Bits:
- Good and bad feedback is welcomed. Else how can we improve?
- If you find a bug, please report it below or via GitHub/GitLab.
- Testing/Translations/Code contributions are gratefully appreciated.
Important Notes for New Users:
- Please make a backup of your device and copy it to another computer.
- You must wipe before installing this OS.
- This OS has userdata encrypted by default
- You are intended to relock your bootloader with this OS (if your device is marked supported for that).
DivestOS does *not* support the following:
- Google Apps (OpenGAPPS)
- DRM (Widevine)
- alternative recoveries (TWRP)
- root (Magisk)
- runtime modification frameworks (Xposed or theme engines)
All downloads are GPG signed with the following key:
Code:
#B874 4D67 F9F1 E14E 145D FD8E 7F62 7E92 0F31 6994
-----BEGIN PGP PUBLIC KEY BLOCK-----
mDMEXupIxBYJKwYBBAHaRw8BAQdAC1RiTvrqJaAQ4FIHsxX+gzEgdT4mspISS+p0
y847Nge0SERpdmVzdE9TIFJlbGVhc2UgU2lnbmluZyAoMjAyMCAjMSkgPHN1cHBv
cnQrcmVsZWFzZXNpZ25pbmdAZGl2ZXN0b3Mub3JnPoiQBBMWCAA4FiEEuHRNZ/nx
4U4UXf2Of2J+kg8xaZQFAl7qSMQCGwMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AA
CgkQf2J+kg8xaZR1BgEAwwLVVsG7kbp8M3GTV987XpVl5cZeTtDc/g+66briCHUB
APiuH/dk8eRnhFnq4Up2/j7uD/8FtSvxPbHiz6t1MdgB
=VzP2
-----END PGP PUBLIC KEY BLOCK-----
Hello DivestOS,
1 - Do you need to reparation internal memory with Clamor's script before flashing this rom ?
2 - Is it set to permissive like in the latest voron00's LineageOS release or to enforcing by default ?
3 - Can you update it via OTA ?
4 - Does it drain battery when the phone is switched off ?
Thanks
kjsu0 said:
Hello DivestOS,
1 - Do you need to reparation internal memory with Clamor's script before flashing this rom ?
2 - Is it set to permissive like in the latest voron00's LineageOS release or to enforcing by default ?
3 - Can you update it via OTA ?
4 - Does it drain battery when the phone is switched off ?
Thanks
Click to expand...
Click to collapse
1. Yes for the 17.1 build, there is however a 16.0 and 15.1 build available that doesn't need repartitioning.
2. No, DivestOS is *always* enforcing. DivestOS will never ever release a build with permissive SELinux.
3. Yes, DivestOS offers OTA updates for every device since 2017/05/30.
4. When the phone is asleep, no. When the phone is powered off, no.
mako was my daily driver for all of 2019, it was a solid experience despite the age of the hardware.
it was a solid experience despite the age of the hardware
Click to expand...
Click to collapse
I agree, this phone is amazing, never age ...
I got it working on my phone.
I used Clamor's script and everything went almost smooth but have two more questions:
1 - Is it normal that signature can't be verified when installing via twrp ?
2 - On first boot-up rom got stuck on divestos splash screen and didn't want to load entire OS...
I rebooted the phone and on second try it started without any problem and greeted with configuration screen, is that ok ?
kjsu0 said:
I agree, this phone is amazing, never age ...
I got it working on my phone.
I used Clamor's script and everything went almost smooth but have two more questions:
1 - Is it normal that signature can't be verified when installing via twrp ?
2 - On first boot-up rom got stuck on divestos splash screen and didn't want to load entire OS...
I rebooted the phone and on second try it started without any problem and greeted with configuration screen, is that ok ?
Click to expand...
Click to collapse
1. It is not recommended to use TWRP with DivestOS, except for a select few devices. You are intended to use the DivestOS recovery.
2. That is expected, it is a known issue. It occurs due to the modem failing to start after the data partition is encrypted for the first time. The workaround is to wait 5 minutes on the very first boot, power it off, then reboot it. All should be OK after.
@voron00 Are you going to release LOS 17.1 (w/ March security patches) as well? Or 16.0 is a better option for mako in your opinion?
Click to expand...
Click to collapse
16.0 is better.
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/rom-unofficial-lineageos-16-0-mako.3758779/post-84653653
It loooks like @varon00 will continue to support only 16, will it impact divestos 17 releases ?
I'm not sure about @voron00 's reasoning to not make 17.1 builds.
But DivestOS 17.1, based on their sources has been fully functional by my standards for nearly a year now.
17.1: Initial bringup · Divested-Mobile/[email protected]
- See items marked with '17REBASE'
github.com
I redid everything again, used fastboot to flash recommended recovery and sideloaded rom from there again. The only downside are apps for banking that require ggle. Do you have any recommendation on that, should I go with open gapps ?
@kjsu0 please kindly read through the divestos.org website. Most of the questions you are asking are all already documented there.
DRM, such as Widevine, is not supported on DivestOS.
Root, such as Magisk, is not supported on DivestOS.
Runtime modification frameworks, such as Xposed, are not supported on DivestOS.
Google Apps, such as Open GApps, are not supported on DivestOS.
Any extra flashable ZIP modifications are not supported on DivestOS.
DivestOS has a strong focus on security, privacy, and freedom. Most of those things are not compatible with our ideals.
This looks like a great project, SkewedZeppelin.
I love the increased privacy focus and built-in OTA support.
I have a question about the custom hosts file. I know DivestOS doesn't recommend using root, but what if we prefer other options like AdAway to manage the hosts file instead?
I'm definitely going to flash DivestOS on the mako. Probably will go with 17.1 instead of the 18 build for now.
Thanks again for starting and maintaining this project!
aospray said:
I have a question about the custom hosts file. I know DivestOS doesn't recommend using root, but what if we prefer other options like AdAway to manage the hosts file instead?
Click to expand...
Click to collapse
DivestOS includes a fairly extensive HOSTS file. Assuming you do not install (m)any proprietary apps and use Mull/Fenix/Bromite with uBlock Origin there should be no visible ads or telemetry phoning home.
As DivestOS does not support root, AdAway is incompatible.
If you want more domains blocked you can use DNS66, however it functions using a local VPN, so you won't be able to use any other VPN apps such as Orbot.
I flashed 17.1 a few hours ago. I did run into the splash screen first boot bug that kjsu0 encountered. I think this should be noted in the first post or on the DivestOS website so people don't get confused, but other than that it's working pretty good so far. Thanks for all your work, SkewedZeppelin!
I looked at the hosts file for DivestOS and I feel like there might be too many sources. I also prefer personalDNSfilter over DNS66 since it has CNAME uncloaking built-in. I guess I'll just use Adguard DNS for private DNS as an alternative.
Calling/data on the latest 18.1 build works thanks to a recent fix from @voron00!
18.1 should now be daily drivable.
@SkewedZeppelin - Could you add the following patch to your rom?
https://android-review.googlesource.com/c/platform/frameworks/base/+/147266/1/packages/SystemUI/src/com/android/systemui/statusbar/policy/DeadZone.java
I've recently experienced the dreaded navigaton bar deadzone issue as described here: https://forum.xda-developers.com/t/wip-fix-dead-navbar-workarounds-and-fixes.3243822/
Edit - Looks like the patch was added a long time ago to AOSP... I guess my mako is finally showing its age.
To anyone who's wondering - DivestOS is still being actively updated. Last update was July 30th.
Thanks to OP for supporting mako to this date. Never thought Android 11 will work this flawlessly in 2012 device.
Wondering if we can get A12 and Material YOU, but then again, it will have serious UI performance problems
Hello DivestOS:
First of all, thank you very much for still supporting Nexus 4 today. I read your post and I still don’t quite understand some points. I would like to ask:
1. What are the specific steps for "resized /system"?
2. After installing Divest OS, can I install other applications on it
at will? Such as: Facebook,Whatsapp.......
3. If it feels inappropriate, can I install another ROM freely?
Please forgive my ignorance, cos I just started to touch the flashing and knowing that Nexus 4 is still supported by community, so I want to try it
Thank you again!
2021redmi2fans said:
Hello DivestOS:
First of all, thank you very much for your team that is still supporting Nexus 4 today. I read your post and I still don’t quite understand some points. I would like to ask:
1. What are the specific steps for "resized /system"?
2. After installing Divest OS, can I install other applications on it
at will? Such as: Facebook,Whatsapp.......
3. If it feels inappropriate, can I install another ROM freely?
Please forgive my ignorance, cos I just started to touch the flashing and knowing that Nexus 4 is still supported by community today, so I want to try it
Thank you again!
Click to expand...
Click to collapse
1. you can use @voron00's repartition script https://drive.google.com/file/d/1GNbxlqG78WYOeXBxgmfGgMmsf02KMVOX/view or @Clamor's script https://forum.xda-developers.com/t/repartition-nexus-4-repartition-mako-8gb-16gb-ua-twrp.3844383/
2. yes, you can install Aurora Store from F-Droid in order to install such proprietary apps
3. of course, just flash another recovery from fastboot and flash any ROM as you please
SkewedZeppelin said:
1. you can use @voron00's repartition script https://drive.google.com/file/d/1GNbxlqG78WYOeXBxgmfGgMmsf02KMVOX/view or @Clamor's script https://forum.xda-developers.com/t/repartition-nexus-4-repartition-mako-8gb-16gb-ua-twrp.3844383/
2. yes, you can install Aurora Store from F-Droid in order to install such proprietary apps
3. of course, just flash another recovery from fastboot and flash any ROM as you please
Click to expand...
Click to collapse
Okay, got it, thank you, please keep working hard, and may God bless !
Very nice, cool to see Android 11 on the ole Nexus 4.
However the lack of microG signature spoofing is a deal-breaker for me.
Fif_ said:
Very nice, cool to see Android 11 on the ole Nexus 4.
However the lack of microG signature spoofing is a deal-breaker for me.
Click to expand...
Click to collapse
I have no short term plans of including microG.
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
{
"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 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?