Database Info

[ROM][UNOFFICIAL][7.1.2][nx551j] LineageOS 14.1 for Nubia M2 [17/09/2018]

{
"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:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 7 (nougat), 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.
What works:
Calls/SMS/Mobile data
Wifi
Bluetooth
GPS
Camera (Photo/Video/Flashlight)
Audio
Fingerprint sensor
DT2W
Keydisabler
Notification LED
Torchlight
Broken
You tell me
Source code:
device tree: https://github.com/HighwayStar/android_device_nubia_nx551j
device-common: https://github.com/HighwayStar/android_device_nubia_msm8953-common
kernel: https://github.com/HighwayStar/android_kernel_nubia_msm8953
vendor: https://github.com/HighwayStar/android_vendor_nubia
Clean code with kernel rebased on top of latest caf nougat msm8953 tag. Warning! this rom uses forceencrypt flag for /data partition, same as global stock rom. If you coming from Chinese ROM or other not encrypted /data ROM your first boot can take long. Do not reboot while encrypting, or you will lost all your data. It's recommend to make backup.
Download
2018-09-17
Fixed headset detection issue
Updated Lineage code
gdrive: lineage-14.1-20180917-UNOFFICIAL-nx551j.zip
mailru: lineage-14.1-20180917-UNOFFICIAL-nx551j.zip
Previous versions:
2018-08-22
Moved to common device tree with Nubia Z11 mini s nx549j
Removed unused camera libraries
Fixed Neocharge in offline-charging mode
Updated Lineage code
gdrive: lineage-14.1-20180822-UNOFFICIAL-nx551j.zip
mailru: lineage-14.1-20180822-UNOFFICIAL-nx551j.zip
2018-07-20
* Fixed Google camera crash in HDR+ mode in low-light conditions
* Fixed color "jumps", "blinks", "grayish color" in all HAL3 apps
* Looks like fully working HAL3 mode here
gdrive: lineage-14.1-20180720-UNOFFICIAL-nx551j.zip
mailru: lineage-14.1-20180720-UNOFFICIAL-nx551j.zip
2018-07-16
* Test build with opensource camera HAL. It enables HAL3 mode, but may also add some issues, please test if camera apps you are using is still working fine. Google camera mods working too, with HDR+ in Nexus 5X or Nexus 6P mode(tested with MGC_5.1.018.177624777-41364271.apk (BSG, 2018-07-12) version)
gdrive: lineage-14.1-20180716-UNOFFICIAL-nx551j.zip
mailru: lineage-14.1-20180716-UNOFFICIAL-nx551j.zip
2018-07-10
* Fixed phone crash when using dual sim.
* Set LTE mode on first run to allow to use mobile data for setup
* Added thermal daemon configs to control device temperature
gdrive:lineage-14.1-20180710-UNOFFICIAL-nx551j.zip
mailru: lineage-14.1-20180710-UNOFFICIAL-nx551j.zip
2018-07-09
* Fixed Phone app crash on Enable/Disable Airplane mod
* Fixed torchligh
* Fixed notification LED. Now buttons backlight red leds blinking on notification
gdrive: lineage-14.1-20180709-UNOFFICIAL-nx551j.zip
mailru: lineage-14.1-20180709-UNOFFICIAL-nx551j.zip
2018-07-04
Fixed high CPU load and high CPU frequencies issue
Removed FM Radio app
Added LTE option to SIM network menu
Fixed call recording
Fixed displayed battery capacity
gdrive: lineage-14.1-20180704-UNOFFICIAL-nx551j.zip
mailru: lineage-14.1-20180704-UNOFFICIAL-nx551j.zip
2018-07-02
Initial build
gdrive: lineage-14.1-20180702-UNOFFICIAL-nx551j.zip
mailru: lineage-14.1-20180702-UNOFFICIAL-nx551j.zip
To install this you have to install TWRP first. I can recommend this version, built with same kernel as ROM. nx551-twrp-3.2.1.img
If you want to use google apps use ARM64 Android 7.1 opengapps package https://opengapps.org/.
If you need root use Lineage addonsu or Magisk
XDA:DevDB Information
[ROM][UNOFFICIAL][7.1.2][nx551j] LineageOS 14.1 for Nubia M2 [17/09/2218], ROM for all devices (see above for details)
Contributors
highwaystar_ru
Source Code: https://github.com/HighwayStar/android_kernel_nubia_msm8953
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOs
Version Information
Status: No Longer Updated
Created 2018-07-02
Last Updated 2018-09-17

Thanks for the work you've done. In the future, plan to go to the official assembly?

Big thanks.

LuigeUA said:
Thanks for the work you've done. In the future, plan to go to the official assembly?
Click to expand...
Click to collapse
Yes, code is done as clean as possible way to be able to go official. To go official it has to be rebased to oreo first. It should be not that hard now.

I can not adjust my fingerprint, go to my home screen when scanning

LuigeUA said:
I can not adjust my fingerprint, go to my home screen when scanning
Click to expand...
Click to collapse
Had this issue too. Have not found fix yet. Workaround is to setup one fingerprint on first boot, it not goes home here. Second fingerprint can be added anytime later, , there is no such issue with second and later fingeeprints.

Hello,
Sorry for the noob question, but I cannot install the ROM because I receive an error while installing. Something like "this ROM cannot be installed because it is for device nx551j device and yours is NX551J"
How can I change this parameter?
Thank you for your help.

estuardo4 said:
Hello,
Sorry for the noob question, but I cannot install the ROM because I receive an error while installing. Something like "this ROM cannot be installed because it is for device nx551j device and yours is NX551J"
How can I change this parameter?
Thank you for your help.
Click to expand...
Click to collapse
Please install twrp from the first post. It should help.

Api
Hi , amazing work bringing nougat for us , thanks...
I'm testing for few hours and i tried many camera apps without lucky.. tried to enable camera2api for gcam and get force stopped in all cameras , could you help me ?
Another question is , will you bring future updates by OTA ?
Thanks a lot , wonderfull job.

estuardo4 said:
Hello,
Sorry for the noob question, but I cannot install the ROM because I receive an error while installing. Something like "this ROM cannot be installed because it is for device nx551j device and yours is NX551J"
How can I change this parameter?
Thank you for your help.
Click to expand...
Click to collapse
it only works with the twrp that is for download on the linage rom downloadpage ,had the same issue.
i did flash the twrp that is advised and did work perfectly.

rolandvb said:
it only works with the twrp that is for download on the linage rom downloadpage ,had the same issue.
i did flash the twrp that is advised and did work perfectly.
Click to expand...
Click to collapse
Is there other way to install? Yesterday I flashed the persistance.img posted by Mauronofrio without problems and now, for the life of me, I can't get my Win10 machine to recognize my device. I uninstalled, restarted with the option of not checking for signature files, installed, nothing. Uninstalled and installed old drivers and nothing. Uninstalled and installed the newest versions from Google and nothing. My win10 pc can't recognize my Nubia
And yes, I tried to make a working USB live image with FWUL but I don't have the technical knowledge to know whats going on and why I can't use it with my Nubia.

Did test this android 7.1 OS this evening, and there are some bugs,the camera did not work on my phone and goty black screen,with other app camara did work
fingerprintscanner did not work properly and could not remove or add fingerprints ,also phone sometimes loses and has to search again for 4g network while using phone
and got symcard message while sym alreddy did work.
hope you can do something about these issues.
i can say the phone is a lot faster an snappyer compaired to all other roms i did test
it would be great if android 8 will come available with this OS, this will make this phone a up to date phone for a bargain!
I think the M2 will even be faster on android 8
afther testing and tryed to restore my older rom i just backed up my the phone it did not boot and ended with a bick
i did restart phone in twrp and did flash the twrp i did use before and everything was ok again.
So the`re seem to be TWRP ussues between different versions, i did use the original twrp that was relased by TWRP app

First, thanks for the good work. I have found a serious bug, there is no processor frequency control and it is always full. Then heat the phone and drain the battery.

bumperiano said:
First, thanks for the good work. I have found a serious bug, there is no processor frequency control and it is always full. Then heat the phone and drain the battery.
Click to expand...
Click to collapse
Yes, something broken here, will check it out.

The processor constantly operates at the maximum frequency. The battery capacity is 3000 mA/h and not 3630.

Woah great work! Will be running this as soon as that CPU util bug is squashed Just a thought, you've posted this in the general Android misc thread although we have our own dedicated sub-forum, any chance of moving it there? Might get better visibility? https://forum.xda-developers.com/t/zte-nubia-m2

estuardo4 said:
Is there other way to install? Yesterday I flashed the persistance.img posted by Mauronofrio without problems and now, for the life of me, I can't get my Win10 machine to recognize my device. I uninstalled, restarted with the option of not checking for signature files, installed, nothing. Uninstalled and installed old drivers and nothing. Uninstalled and installed the newest versions from Google and nothing. My win10 pc can't recognize my Nubia
And yes, I tried to make a working USB live image with FWUL but I don't have the technical knowledge to know whats going on and why I can't use it with my Nubia.
Click to expand...
Click to collapse
i confirm the issue that the phone is not recognized in windows 10 ,you can see the partitions but when opening there is nothing so see and empty while it is not and no files can be added.
this is a good start but at the moment this rom is not realy a usable rom, also very strange that it only can be flashed with the twrp provided. you get error 7 and also the message this rom is not suitable
for this phone and i am using the original TWRP provided bij TWRP itself. i don`t want to reflash my phone between different twrp versions to be able to restore my phone.
i had the official TWRP installed and did not work with this rom, so i think this must be corrected to and be compatable with the original released twrp , by twrp.
the twrp provided on the rom downloadpage also does load very slow and takes 3 times longer to load.

LuigeUA said:
The processor constantly operates at the maximum frequency. The battery capacity is 3000 mA/h and not 3630.
Click to expand...
Click to collapse
The battery capacity is 3630 and not 3000

mauronofrio said:
The battery capacity is 3630 and not 3000
Click to expand...
Click to collapse
I know, but Kernel Adiutor showing 3000 mah

LuigeUA said:
I know, but Kernel Adiutor showing 3000 mah
Click to expand...
Click to collapse
nubia ui stock also shows 3000. Do not worry about that.

[UNOFFICIAL][20191230] LineageOS 17.0 for UMIDIGI F1 [Android 10]

Introduction
This is my port of LineageOS 17.0 for the UMIDIGI F1, with things mostly working as they are expected to. This ROM depends on the official vendor image, so please be sure you are on the latest official build before flashing this ROM onto your device. Also, since these MTK devices often come with some strange variants, please be aware that your lineage may vary.
Known Bugs
- VoLTE does not work (and probably won't work on any MTK device with custom ROMs any time soon) due to MTK's proprietary extensions.
- (Fixed since 20191230) Sometimes data connection can be randomly lost during reconnections. This can be fixed by either a reboot or `pkill phone` in a root shell (terminal).
Flashing Instructions
1. You MUST flash my TWRP port available here before trying to install the ROM
2. Reboot into TWRP, wipe data (no format needed), then install the ROM zip
3. Install anything else you would like (Magisk, OpenGAPPs, etc. OpenGAPPS beta for Android 10: https://sourceforge.net/projects/opengapps/files/arm64/beta/)
4. Reboot into system and enjoy.
Downloads
20191230-1: https://www.androidfilehost.com/?fid=4349826312261687930
20191105-1: https://www.androidfilehost.com/?fid=4349826312261619909
Source code
Device tree available at https://github.com/PeterCxy/android_device_umidigi_F1
Kernel source code is not available from UMIDIGI, unfortunately.
Screenshots (with OpenGAPPS beta)
{
"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"
}

What do you mean by "This ROM depends on the official vendor image" Do I need to flash the latest firmware from Umidigi, then flash Lineage?

Lolithetrolli said:
What do you mean by "This ROM depends on the official vendor image" Do I need to flash the latest firmware from Umidigi, then flash Lineage?
Click to expand...
Click to collapse
Actually I don't think there is much change in umidigi's firmware so you are probably fine with pretty much any vendor image. I am on the September vendor image which shows as 20190724

While I enjoy your effort for the port it's really rough around the edges. Settings randomly crash, NFC randomly crashes, there's no difference between default dark mode and black dark mode, it lacks accents other than default, after enabling developer settings numbers appear on the left hand side of the status bar, and GAPPS doesn't even have android 10 available yet. Again, thanks for the port, but it's not for me.

Lolithetrolli said:
While I enjoy your effort for the port it's really rough around the edges. Settings randomly crash, NFC randomly crashes, there's no difference between default dark mode and black dark mode, it lacks accents other than default, after enabling developer settings numbers appear on the left hand side of the status bar, and GAPPS doesn't even have android 10 available yet. Again, thanks for the port, but it's not for me.
Click to expand...
Click to collapse
Somehow I'm using it without any random crashes... Are you sure you have tested on the latest firmwares from umidigi? And are you sure you have wiped data properly? If those crashes only happen for you and not for me, then without logs it's simply impossible for me to fix anything.
And OpenGAPPS has beta version for Android 10, check it out at https://sourceforge.net/projects/opengapps/files/arm64/beta/
On the accent color thing, please wait until LineageOS 17 ports every feature over. For now having most things working is the primary focus.

Thanks for bringing a new life to an already awesome device! I was thinking on changing device due to lack of support, but now I'm surely sticking around! I have a couple of questions tho:
- Is it possible to add tweaks to this kernel? Like 2DTW, F2FS and maybe some more performance/battery gains? Or maybe upgrade it, like to 4.9?
- What about performance in games and/or more demanding tasks? I noticed this on all the GSI's that I tried, because they weren't optimized for the device, and it got hot easily.
Thanks once again for making this dream a reality! I Will test this along with your recovery when I can! Cheers!

SnapTheRipper said:
Thanks for bringing a new life to an already awesome device! I was thinking on changing device due to lack of support, but now I'm surely sticking around! I have a couple of questions tho:
- Is it possible to add tweaks to this kernel? Like 2DTW, F2FS and maybe some more performance/battery gains? Or maybe upgrade it, like to 4.9?
- What about performance in games and/or more demanding tasks? I noticed this on all the GSI's that I tried, because they weren't optimized for the device, and it got hot easily.
Thanks once again for making this dream a reality! I Will test this along with your recovery when I can! Cheers!
Click to expand...
Click to collapse
This seems to be built with stock kernel. As there is no kernel source released, the addition to kernel mods is not currently available.

mrmazak said:
This seems to be built with stock kernel. As there is no kernel source released, the addition to kernel mods is not currently available.
Click to expand...
Click to collapse
Well I found some P60 sources from Nokia, idk if it could be useful...
https://github.com/nokia-dev/android_kernel_nokia_mt6771
Amdroid Pie:
https://github.com/nokia-dev/android_kernel_nokia_mt6771/tree/android-9.0

SnapTheRipper said:
Thanks for bringing a new life to an already awesome device! I was thinking on changing device due to lack of support, but now I'm surely sticking around! I have a couple of questions tho:
- Is it possible to add tweaks to this kernel? Like 2DTW, F2FS and maybe some more performance/battery gains? Or maybe upgrade it, like to 4.9?
- What about performance in games and/or more demanding tasks? I noticed this on all the GSI's that I tried, because they weren't optimized for the device, and it got hot easily.
Thanks once again for making this dream a reality! I Will test this along with your recovery when I can! Cheers!
Click to expand...
Click to collapse
It is not technically impossible, but it would require a LOT of effort to reverse-engineer an entire kernel by piecing together open-source components from other manufacturers, and many of these vendors using MTK SoCs do not have open-source kernel just like Umidigi, though it's technically illegal to do so. I'm definitely not going to do this any time soon.

PeterCxy said:
It is not technically impossible, but it would require a LOT of effort to reverse-engineer an entire kernel by piecing together open-source components from other manufacturers, and many of these vendors using MTK SoCs do not have open-source kernel just like Umidigi, though it's technically illegal to do so. I'm definitely not going to do this any time soon.
Click to expand...
Click to collapse
Now I'm lost ? don't get me wrong, I didn't started yet to develop, but if Umidigi has an "open source" kernel, could it be decompiled somehow from the stock firmware?

SnapTheRipper said:
Now I'm lost ? don't get me wrong, I didn't started yet to develop, but if Umidigi has an "open source" kernel, could it be decompiled somehow from the stock firmware?
Click to expand...
Click to collapse
Linux being open-source doesn't mean any modification to it is easily reverse-engineerable. There is no such thing as "decompilation", only reverse-engineering, which is exactly what I referred to as "not totally impossible". However, if you hope someone to devote an enormous amount of effort just to "decompile" a kernel, you'd better off just sue the manufacturer for kernel source code (they are legally bound to do so by using the Linux kernel). It's far more plausible.

PeterCxy said:
Linux being open-source doesn't mean any modification to it is easily reverse-engineerable. There is no such thing as "decompilation", only reverse-engineering, which is exactly what I referred to as "not totally impossible". However, if you hope someone to devote an enormous amount of effort just to "decompile" a kernel, you'd better off just sue the manufacturer for kernel source code (they are legally bound to do so by using the Linux kernel). It's far more plausible.
Click to expand...
Click to collapse
Anyway
I tried the exact same steps but ended up in a splash screen loop. Any idea how to fix this (or how to grab a log of this, if needed)?

No service on two of the sim card. Phone shows carrier, but no network.
Edited: Never mind. Start from fresh umidigi system, and all good.

SnapTheRipper said:
Anyway
I tried the exact same steps but ended up in a splash screen loop. Any idea how to fix this (or how to grab a log of this, if needed)?
Click to expand...
Click to collapse
TWRP keep system read only, no more boot loop.

test on Umidigi F1 Play
I make Kernel Changes to make your rom work on umidigi f1 play and it booted but a lot of issues :
- sim card doesnt recognize in second reboot
- A lot of NFC Force closes
- Sound is deteriorated (i Think it because the besloudness in the stock rom)
- Rom has a lot of features that not working (example percentage of battery is not showed after i enable it)
this just a report of 15 minutes testing roms

It's possible to revert to stock? How?

sinergine said:
It's possible to revert to stock? How?
Click to expand...
Click to collapse
That would be easiest if you use twrp and make a backup , before flashing this. Same as with any rom, you should make backup first.
If you didn't do that, or the restore fails. Then use sp-flash tool and flash factory firmware.
Umidigi posts the firmware on there community web forum.

SnapTheRipper said:
Anyway
I tried the exact same steps but ended up in a splash screen loop. Any idea how to fix this (or how to grab a log of this, if needed)?
Click to expand...
Click to collapse
Same for me
hyibin said:
TWRP keep system read only, no more boot loop.
Click to expand...
Click to collapse
How to resolve?

sinergine said:
Same for me
How to resolve?
Click to expand...
Click to collapse
Resolved with reflash
hyibin said:
No service on two of the sim card. Phone shows carrier, but no network.
Edited: Never mind. Start from fresh umidigi system, and all good.
Click to expand...
Click to collapse
Now i've this problem.
Tried to restart all step from fresh system but no network

sinergine said:
Tried to restart all step from fresh system but no network
Click to expand...
Click to collapse
You have to put sim cards in before the initial boot. I gave up because too many bugs.

[Treble][GSI] Ubuntu touch for Oneplus 3/3T

{
"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:
/*
* Your warranty is now void.
*
* 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.
*/
What is Ubuntu Touch?
Ubuntu Touch is the touch-friendly mobile version of Ubuntu.
This operating system is developed and maintained by UBports: An international community of passionate volunteers.
This means Ubuntu Touch is 100% community driven and independent.
What is Halium?
Halium is the collaborative project to unify the Hardware Abstraction Layer for projects which run GNU/Linux on mobile devices with pre-installed Android.
How it is a GSI?
First of all, I should mention ubports GSI definition is different from android, but both are generic.
ubports root file system was always generic and works for most cases, but devs were porting halium system image to add device-specific (HALs and configs) support to ubports Android container.
But after project treble which introduced in android 8, all device-specific parts of android system image moved to vendor partition and we can use "Generic system images" over one vendor partition.
In halium version 9, we use this adventure and have a totally generic system image + root file system.
Requirements:
The only Requirement of booting this GSI is having Halium patched kernel.
Keep in mind having android 9 firmware installed on the device as GSI base is mandatory
What's needed ?
Phone needs to be treblized - thanks to the project : https://forum.xda-developers.com/on...eble-lineageos-15-1-treble-oneplus-3-t3830455
Then custom kernel & lineage image dedicated to Ubports - OP3 https://drive.google.com/drive/folders/1vnJEKkhO3xqH-fWWG55-yxwx5K1EeKq7?usp=sharing
Ubports GSI image are required
Installation steps:
- Download:
Recovery : twrp-op3treble-3.3.1-1.img : there
LineageOS 16 Ubuntu touch custom : there
Firmware 9.0.6 : oxygenos-9.0.6 be careful the firmwares are device specific : there
Download the latest GSI zip from there
Download the Halium-ramdisk there
Download the halium-boot.img there
Download the OP3_GSI_Fix_V1.1.zip there
- Reboot into fastboot and install the TWRP recovery => Check the official link for installation TWRP link
- Treblelize your OP3(t), by following the information there : https://forum.xda-developers.com/on...eble-lineageos-15-1-treble-oneplus-3-t3830455
- Reboot into the TWRP Recovery
- Update the firmware
- Install LineageOS 16 Ubuntu touch custom
- Reboot into Lineage, confirm everything works fine.
- Ensure your /vendor (after mounting) is populated with content from an Android 9 ROM (LineageOS)
- Flash the GSI zip file
- Flash the halium-boot.img from before to your boot partition (if you didn't yet):
Code:
adb push ~/Halium/out/target/product/oneplus3/halium-boot.img /tmp/
adb shell "dd if=/tmp/halium-boot.img of=/dev/block/bootdevice/by-name/boot"
Or
Code:
fastboot flash boot out/target/product/oneplus3/halium-boot.img
- Flash the halium-ramdisk.zip
- Flash the fix for OP3 : OP3_GSI_Fix_V1.1.zip
- Reboot
- Enjoy
What's work:
Audio
Calling
SMS
4G - Yes but no icons - need to activated once after GSI is flashed
Wifi - Need a fix to restart it see the github repo
GPS
Vibration
Orientation sensor
Bluetooth
camera - zooming is sluggish
Video recording/decoding
Fingerprint + home button calling the dash <= Sweet !
What's Missing:
GSM tends to crash time to time on low signal.
Flash light
ADB/MTP - replaced by SSH
Libertine - didn't try yet
Anbox - Not tried yet
others ?
Thanks to :
https://forum.xda-developers.com/on...eble-lineageos-15-1-treble-oneplus-3-t3830455
https://forum.xda-developers.com/pr...development/gsi-ubuntu-touch-ubports-t4110581
And Ubports team : https://ubports.com/

Hi, thanks for this port.
What's the differences between this gsi build and the official build that flash with ubports-installer?

Sbodezzi said:
Hi, thanks for this port.
What's the differences between this gsi build and the official build that flash with ubports-installer?
Click to expand...
Click to collapse
Hello Sorry, I didn't see your reply.
It's a good question, I'm trying to maintain both port, as a quick glance :
- Official Ubports is based on halium 7.1 based on lineage 14.1.
- Ubports GSI is based on halium 9 based on lineage 16.0.
The first one doesn't need partition modification while the second requires the dedicated vendor partition.
On the other side installing via the ubports installer is annoying sometime due to the partition management of oneplus3. (The same to format to install lineage)
Experience wise, the GSI tends to be smoother than the official Ubports on the other side the update (edge = unstable) on the GSI are currently coming randomly depending on Erfan works. I don't know in the future how this will be handle. GSI doesn't have OTA while Official ubports yes.
Hardware wise the GSI has the advantage to have : Video recording, fingerprint reading, incall volume working, on the other side there are some bugs graphic/touch glitch, no data icon etc...
Some bug listed in the github repository, I found a fix and now I need to create a script post GSI install.
I personally prefer to use daily the GSI due to the feeling to be smoother.
A good video describing this port : https://www.youtube.com/watch?v=UyOcQtNDZwM

Thanks for the thread!!
Are you the Kevin I talked to on the Halium TG? Seems you fixed RIL, that's cool!
Thanks

slash.tux said:
Hello Sorry, I didn't see your reply.
It's a good question, I'm trying to maintain both port, as a quick glance :
- Official Ubports is based on halium 7.1 based on lineage 14.1.
- Ubports GSI is based on halium 9 based on lineage 16.0.
The first one doesn't need partition modification while the second requires the dedicated vendor partition.
On the other side installing via the ubports installer is annoying sometime due to the partition management of oneplus3. (The same to format to install lineage)
Experience wise, the GSI tends to be smoother than the official Ubports on the other side the update (edge = unstable) on the GSI are currently coming randomly depending on Erfan works. I don't know in the future how this will be handle. GSI doesn't have OTA while Official ubports yes.
Hardware wise the GSI has the advantage to have : Video recording, fingerprint reading, incall volume working, on the other side there are some bugs graphic/touch glitch, no data icon etc...
Some bug listed in the github repository, I found a fix and now I need to create a script post GSI install.
I personally prefer to use daily the GSI due to the feeling to be smoother.
A good video describing this port : https://www.youtube.com/watch?v=UyOcQtNDZwM
Click to expand...
Click to collapse
Thank you for your exhausting answer.
It seems worth taking a ride ?

thanks very much for your hardwork

what is the default password?i tried 0000 but cant access my files

The default password is phablet, by ssh [email protected]

how to making system be rw?
this [guide](https://ubports.com/blog/ubports-blogs-news-1/post/terminal-chapter-3-3073) need adb but adb doent work,anyother idea?

weigeloveu said:
how to making system be rw?
this [guide](https://ubports.com/blog/ubports-blogs-news-1/post/terminal-chapter-3-3073) need adb but adb doent work,anyother idea?
Click to expand...
Click to collapse
Use the application UT tweak tool (from Open Store) and go to the system menu.

stuck at oneplus logo
EDIT:
Now it works!!!!!!!!!!!!!!!! I made the Format Data with TWRP and then flashed the boot image by fastboot. It seems like the path is wrong, I think the right path for the dd would be /dev/block/by-name/boot. But now it works!
Hello all,
I am not totally new to the whole flashing thing but also not an expert so please excuse some lack of knowledge.
But I tried now several times this instrucions and got some issues fixed by myself, but always I end up with a stucked boot logo.
Flash TWRP treble -> treblized -> flash LOS 16.0 treble - > Updated Firmware with op3.zip (more to that later) -> flash LOS 16.0 Ubuntu -> check if LOS works -> Flash halium-boot.img with adb -> Flash GSI -> flash halium-ramdisk.img -> flash GSI Fix -> Reboot
So my first question, and sorry for my dumbness, but what is meant by " - Update Firmware " ? Are there maybe some more detailed instructions for that ?
Because what I did was downloaded the linked git repository, and then I zipped the files wich were inside the op3 folder only. And this zip I "installed" with TWRP. But that felt always kida wrong so maybe thats my issue. But what else I have to do?
The second thing I noticed is that the command for flashing the boot.img with adb points to "/dev/block/bootdevice/by-name/boot" but "bootdevice" seems to be a file if I got to FileManager within TWRP. The only place where a "boot" file is located at my device is "/dev/block/by-name/boot" so should I use this path instead then?
Besides that I didn´t do "Format Data" before flashing the boot.img like it mentioned in the linked description. But not this thread here so I was not sure if I will destroy something by formatting....
I hope you can help me
And pls apologize my bad language

Hy guys, I followed instructions to install UT on my OP3T but mobile data doesn't work. Any suggestion?

Hello, thanks a lot for this, I ran it and it did run better than the official UT mostly. I was wondering if you could make a GSI_fix for the phone for droidian. Or if you could perhaps guide me/send any tips because I really don't know how to go about making an adaptation package for the droidian_gsi. Thanks in advance!

Afaik you do not need any fix for it. But we are OT. It should work with droidian-rootfs-api28gsi-arm64 and optional the -devtools package. Do not use any fixes!

[ROM][H830|H850|RS988] UNOFFICIAL LineageOS 18.1 for LG G5

{
"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"
}
Disclaimer
Your warranty is now void.
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.
Introduction
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device. More info.
Install
Update recovery to the latest TWRP or Lineage Recovery build
Format data if coming from an UNOFFICIAL or non-Lineage build.
Flash the ROM
Flash any addons
Reboot
Bugs
If you encounter issues/bugs that are not known, please report. If I can replicate your issue then I can track it down.
If I cannot, please provide as much detail as possible. Logcats are a must.
Please indicate what g5 variant you have (h830, h850, rs988), the dated version, and any third party mods.
I am aware people run mods or change things. If needed I may ask you to data wipe or remove a mod that might be interfering.
Please avoid bringing up issues with your favourite gapps package. If a bug only exists with gapps, it's not my problem.
Changelog
Code:
[03/03/2021]
March security patch (android-11.0.0_r32)
[20/12/2021]
January security patch (android-11.0.0_r27)
Fixed camera crashes
[04/12/2021]
Updated LineageOS apps and frameworks
[13/12/2020]
LineageOS 18.1 - Android 11 QPR1
[30/11/2020]
Fixed boot after encrypting with a lockscreen set
Updated LineageOS apps and frameworks
[B]16/11/2020[/B]
First release
Downloads
Official builds
Archived unofficial builds: sourceforge
Sources
Gerrit
https://github.com/LineageOS
https://github.com/LineageOS/android_kernel_lge_msm8996
https://github.com/LineageOS/android_device_lge_msm8996-common
https://github.com/LineageOS/android_device_lge_g5-common
h830
h850
rs988

Will los 18.0 be coming to g6

hi will this work on h845 as well? if not, is it okay to flash h850 or h830 on my h845?

lgg5.845lol said:
hi will this work on h845 as well? if not, is it okay to flash h850 or h830 on my h845?
Click to expand...
Click to collapse
No, it won't work, don't try flashing an h830/h850 ROM as flashing a ROM not meant for the variant of your device will most likely land you in an unfixable hard brick. Ask me how I know.

Great to see you with new topics! I will try soon as possible :good:

ROMSG said:
No, it won't work, don't try flashing an h830/h850 ROM as flashing a ROM not meant for the variant of your device will most likely land you in an unfixable hard brick. Ask me how I know.
Click to expand...
Click to collapse
damn...sorry for that... its weird there's no new custom rom for h845, at least. on android 8 or 9 :laugh:

lgg5.845lol said:
damn...sorry for that... its weird there's no new custom rom for h845, at least. on android 8 or 9 :laugh:
Click to expand...
Click to collapse
The h845 is very different from the G5 h850/h830/rs988 instead of the sdm 820 it uses the sdm 652. A much cheaper and slower soc. So you see the sources listed in the op.
Sources
Gerrit
https://github.com/LineageOS
https://github.com/LineageOS/android_kernel_lge_msm8996
https://github.com/LineageOS/android...msm8996-common
https://github.com/LineageOS/android..._lge_g5-common
h830
h850
rs988
Even though @synescu has made a twrp pot almost all of these would have to be heavily modified to work with the g5 se. I tried to build android 7 for the se but the only device tree available is horribly out of date and even android 7 wouldn't build successfully ( @synescu who wrote this tree and made twrp for the g5 se has been inactive for a year). It also doesn't help that the g5 SE is very rare in the united states as it was a Europe exclusive and even using sites that will import from Europe the g5 se is super overpriced (sometimes even more than $300!) on the used market. So unless someone can find a g5 se for cheap a rom for the se won't be happening anytime soon, unfortunately.

When I try to build 18.0, all goes well. Then there is an error when it comes to signing the build. (I'm using the same scripts I use for 17.1, except s/17.1/18.0/g.)
Code:
ERROR: Failed to run signapk.jar: return code 1:
Error: Unable to access jarfile /home/rfrazier/android/lineage/lineage-18.0/build/make/tools/framework/signapk.jar
And here's the command.
Code:
## Signing
echo "Signing the APK."
time ./build/tools/releasetools/sign_target_files_apks -o -d ~/.android-certs \
$OUT/obj/PACKAGING/target_files_intermediates/*-target_files-*.zip \
signed-target_files.zip &>>${LOGFILE}
I suspect that it is operator error, but any suggestions would be welcome.
Best wishes,
Bob
PS signapk.jar exists in the directory in which I think i should be looked for: out/host/linux-x86/framework
So, I suspect that an environmental variable is being incorrectly set. Something to look into when I get some more time.
RLF

Great to see more development for the G5, thanks!
How is the stability of this compared to Lineage 17.1?

H820?
How about H820?

ajasei said:
How about H820?
Click to expand...
Click to collapse
As far as I know the H820 is not bootloader unlockable. There aren't any lineage builds for h820 anyway.

I think that the signing problem is related to a change in /build/tools/releasetools/common.py, and more particularly in changes to the following.
class Options(object):
def __init__(self):
Now if I could only read it (not being a programmer). I guess I'll give it a go later.
Best wishes,
Bob

Yes, something is definitely going on there. I hardwired in the path in /build/tools/releasetools/common.py , and it was built and signed just fine.
Code:
class Options(object):
def __init__(self):
# Set up search path, in order to find framework/ and lib64/. At the time of
# running this function, user-supplied search path (`--path`) hasn't been
# available. So the value set here is the default, which might be overridden
# by commandline flag later.
exec_path = sys.argv[0]
if exec_path.endswith('.py'):
script_name = os.path.basename(exec_path)
# logger hasn't been initialized yet at this point. Use print to output
# warnings.
print(
'Warning: releasetools script should be invoked as hermetic Python '
'executable -- build and run `{}` directly.'.format(script_name[:-3]),
file=sys.stderr)
# self.search_path = os.path.realpath(os.path.join(os.path.dirname(exec_path), '..'))
self.search_path = "out/host/linux-x86"
The last commented out line
self.search_path = os.path.realpath ...."
was replaced with
self.search_path = "out/host/linux-x86"
I haven't figured out the logic of the rest of the stuff, so don't know what's wrong with it.
Best wishes,
Bob
PS I tried a dirty update (on my spare phone), but it didn't work. I had to format data. It might have been because I had Magisk installed and that messed up the recovery partition, but I'm not sure. In any case, after formatting data it came up just fine. I haven't checked much yet, but WIFI works.
RLF
PPS It looks like a mistaken assumption about the location of the .jar file related to the file which calls it, i.e., that the files should be in the same subdirectory as common.py(c), which calls it, i.e., build/make/tools/<framework ...>. While, actually, the files are in out/host/linux-x86*/<framework ...>.
*Or, whatever platform is being used.
Unless, of course, one is supposed to do something to get those files (.jar lib) into the correct directories.
In any case. hardwiring isn't ideal, but at least it works.
RLF

Since it was working okay on my spare phone, I decided to give it a go on the phone I used. It installed okay, I set it up okay, got all the apps installed okay, etc. NFC works (yubico), BT works (keyboard). Unfortunately, I decided to encrypt. Wouldn't work. Said my data may be corrupted, I would have to format data and start again. Bummer.
And, of course, it was harder than ever to back up settings, including app settings, so, mostly, they aren't. There's an area ripe for improvement.
Note to self. Try encryption on the spare phone before even contemplating putting it on the main phone.
Best wishes,
Bob
PS I have /tmp/recovery.log, if anyone wants to see it. Although it may not be as useful as it could have been, as I reinstalled system on a whim before the last time of giving it a shot.
RLF
PPS I reinstalled, and everything seems to be working smoothly. Although I haven't tried much beyond basic call, NFC, BT, wifi, and the like. I'll try encrypting again, on my spare phone, in a couple of weeks, perhaps when the December security update comes out.
RLF

Thank you for the time you spent trying to check what's working and what's not. There was an annoying bug in the previous LineageOS versions: IR blaster doesn't work, or works once and then you need to reboot the phone to use it again. Can you please test if it works in 18.0? It's an underestimated feature that I use on a daily basis. This bug was the main reason, together with the lack of camera apps better than the G5's default (and G7's camera port, also based on LG framework), why I never used Lineage for more than a couple of days before reverting to stock based roms.

I didn't see IR blaster in the pull-down from the status bar, and didn't see it in the connected devices section. Also, I don't think that I have anything amenable to being blased by IR.
Best wishes,
Bob

wifi - works
bluetooth - works, and so does AudioFX, listening to music works great
ir blaster - not working |Confirmed working (with bug, can only blast one command before losing functionality, restarting device restores functionality for one blast) in latest 17.1 build|
encryption - not working, hangs after reboot on animation boot |Confirmed working in latest 17.1 build|
nfc - unknown, couldn't test since my G3's seem to have issues also
auto rotate - works
camera - works, front and back
torch - works
testing done on h830
quite the shame about how bugged the ir blaster is, my G3 running latest lineageos build blasts great.

NFC works - G5 (h850) Yubico Authenticator, with YubiKey 5 NFC.

whoops, reflashed between 17.1 and 18 a lot, during one of the quick setups of 18 I forgot to uncheck the box for lineageos custom recovery, but went back to uncheck it before finishing the rest.
TWRP still got erased and now with LineageOS recovery, whats the easiest way back to getting TWRP?
(I know I could reflash 20A and dirtycow, but i'm hoping for a cleaner way)

DrowningInFreedom said:
whoops, reflashed between 17.1 and 18 a lot, during one of the quick setups of 18 I forgot to uncheck the box for lineageos custom recovery, but went back to uncheck it before finishing the rest.
TWRP still got erased and now with LineageOS recovery, whats the easiest way back to getting TWRP?
(I know I could reflash 20A and dirtycow, but i'm hoping for a cleaner way)
Click to expand...
Click to collapse
Just flash it using fastboot. Look at the lineage wiki entry for your device.
Best wishes,
Bob

[ROM][Official][Nightly] LineageOS 18.1 for OnePlus 3/3T

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.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
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.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Important information:
This thread is for LineageOS 18.1 builds for OnePlus 3/3T. The following will not be supported here:
Custom kernels
Mods
Xposed
We don't support Xposed and any logcat which includes an Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
Tips:
You need at least OxygenOS 9.0.2 firmware, otherwise you'll get error 7 when installing the zip. Latest firmware is recommended.
Installation:
First time flashing LineageOS 18.1 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery (Official TWRP 3.4+ is highly recommended: https://dl.twrp.me/oneplus3/)
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash LineageOS
Optional: Install the Google Apps addon package
Reboot
Source code:
https://github.com/lineageos
Credits:
LineageOS Team & Contributors
Code Aurora Forum
......
Changelog and Download:
2021/2/8 (Initial release): https://androidfilehost.com/?fid=17248734326145731516​Known issues:​
This build is HIGHLY EXPERIMENTAL and NOT WELL TESTED.
Wifi display not work, don't ever attempt to use it or the system will crash.
VoLTE is not tested and I don't know if it ever works, please give feedback if you're able to verify.
2021/4/2: https://download.lineageos.org/oneplus3​
Fixed the sensor_SMD wakelock
Fixed ringtone when bluetooth headset connected

Wow !!! , i'm on LOS 17.1 Official now but waiting for LOS 18.1 Official
OP3 is my daily driver..
Thank you @dianlujitao

Thanks for this great Rom.
One issue.
It displays a popup with the following message: "This build was signed with public keys".
Should i ignore it?

Keyvannn said:
Thanks for this great Rom.
One issue.
It displays a popup with the following message: "This build was signed with public keys".
Should i ignore it?
Click to expand...
Click to collapse
Yes, you should

josepmaria said:
Yes, you should
Click to expand...
Click to collapse
Would updating to official builds be possible later on, based on the fact public keys are used?
Other question; is a locked bootloader possible with these builds?
I don't know enough about used keys to be sure...

Jan_L said:
Would updating to official builds be possible later on, based on the fact public keys are used?
Other question; is a locked bootloader possible with these builds?
I don't know enough about used keys to be sure...
Click to expand...
Click to collapse
Yes, the key for signing the build doesn't matter.

My initial testing of this rom is that everything is working (based on my usage): WiFi, phone calls, SMS, NFC (Google Pay) all work.
I had a bit of problem setting the wallpaper initially (FCed), but the problem went away on its own after waiting a bit of time.
I'm missing the settings option to specify the duration of the capacitive key backlight, but that's no big deal.
I'm using Opens Gapps pico 210130 and Magisk 21047.
I've seen evidence of the sensor_SMD kernel wake lock issue that I've seen on all Android 11 roms I've tested previously. I'll post more details on this once I've captured a logcat of the problem.

BillGoss said:
sensor_SMD kernel wake lock issue
Click to expand...
Click to collapse
Nap time by Franco mostly solved this for me.

Sideload TWRP 3.5.0, wipe dalvik & cache, flash 18.1. All good

Jan_L said:
Would updating to official builds be possible later on, based on the fact public keys are used?
Other question; is a locked bootloader possible with these builds?
I don't know enough about used keys to be sure...
Click to expand...
Click to collapse
Update to official build requires a clean install and an unlocked bootloader

raz123 said:
Nap time by Franco mostly solved this for me.
Click to expand...
Click to collapse
Last time I used NapTime, it drains more battery than it should and my phone was almost all the time in idle untouched with WIFI and everything else off

Regarding the sensor_SMD wake lock:
Generally, the rom can go for long periods without this wake lock showing up:
{
"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"
}
But the wake lock can start at random times:
And when it starts, it will stop the device from going into deep sleep (look at the "Awake (Screen off)" figures). This will drain the battery a lot faster than normal. See 210209-174541-log.zip for logs.
However, I find that the wake lock will always start when the phone is fully recharged (I usually do this just before I go to bed). See 210209-174541-log.zip for logs.
Fortunately, a reboot gets rid of the wake lock.

josepmaria said:
Update to official build requires a clean install and an unlocked bootloader
Click to expand...
Click to collapse
If the plattform key is changed a clean flash is highly recommended (though not required if you use a migration script or zip - NOT!!! recommended). Since los recovery (as well as current twrp for that matter) and los boot image are signed with aosp verity key, you don't need to unlock bl if you run any version of los with a locked bl.
I've explained the three different keys and signatures used in a single build in depth in the llos 17 thread: https://forum.xda-developers.com/t/...or-oneplus-3-3t.3990061/page-60#post-82568467

BillGoss said:
Regarding the sensor_SMD wake lock:
Generally, the rom can go for long periods without this wake lock showing up:
View attachment 5215977View attachment 5215981
But the wake lock can start at random times:
View attachment 5215983View attachment 5215985
And when it starts, it will stop the device from going into deep sleep (look at the "Awake (Screen off)" figures). This will drain the battery a lot faster than normal. See 210209-174541-log.zip for logs.
However, I find that the wake lock will always start when the phone is fully recharged (I usually do this just before I go to bed). See 210209-174541-log.zip for logs.
View attachment 5215983View attachment 5216001
Fortunately, a reboot gets rid of the wake lock.
Click to expand...
Click to collapse
Nice finding. Just check the source and that should be the Significant Motion Detector if I'm not wrong. Dunno if there are any drawbacks but you should be able to disable it by adding " ro.vendor.sensors.smd=false" to /vendor/build.prop, please try if it helps.

dianlujitao said:
Nice finding. Just check the source and that should be the Significant Motion Detector if I'm not wrong. Dunno if there are any drawbacks but you should be able to disable it by adding " ro.vendor.sensors.smd=false" to /vendor/build.prop, please try if it helps.
Click to expand...
Click to collapse
I set the property as you suggested. After more than 12 hours, including a full recharge, there's no sign of the wake lock. It's looking good.
Thank you!

May be a stupid question and definitely not belonging here, but can not find the answer anywhere else....
When is /vendor/build.prop used and when /system/build.prop?
It seems settings of /vendor/build.prop are used earlier in the boot process and are vendor specific, where afterwards /system/build.prop settings are added later in the boot process and are OS specific.
A lot of people are messing with build.prop settings but have no idea what they are doing and if settings are even working or not. As I see it, some settings put in /system/build.prop are in fact settings which belong in /vendor/build.prop, but I do not know if everything put in /system/build.prop will overrule /vendor/build.prop or the other way around....
In some Android 10 code I found the order default.prop, build.prop, vendor.prop, where /vendor/build.prop is loaded after /system/build.prop, though not sure if this is the default then....
You see, no idea what I am talking about; I hope someone can clear things up...

Jan_L said:
May be a stupid question and definitely not belonging here, but can not find the answer anywhere else....
When is /vendor/build.prop used and when /system/build.prop?
It seems settings of /vendor/build.prop are used earlier in the boot process and are vendor specific, where afterwards /system/build.prop settings are added later in the boot process and are OS specific.
A lot of people are messing with build.prop settings but have no idea what they are doing and if settings are even working or not. As I see it, some settings put in /system/build.prop are in fact settings which belong in /vendor/build.prop, but I do not know if everything put in /system/build.prop will overrule /vendor/build.prop or the other way around....
In some Android 10 code I found the order default.prop, build.prop, vendor.prop, where /vendor/build.prop is loaded after /system/build.prop, though not sure if this is the default then....
You see, no idea what I am talking about; I hope someone can clear things up...
Click to expand...
Click to collapse
First of all: since op3/t has no dedicated vendor partition /vendor is a symlink to /system/vendor.
/default.prop is read first and contains settings necessary for basic boot (historically this file has been part of the root partition which has been ramfs contained in the boot image as cpio archive prior to system as root, which allows to set these props before system was mounted - obviously that's not longer the case with system as root.
/system/vendor/build.prop is read as second source containing vendor specific props. Systematically this should contain settings specific to the vendor(s) of the device and the actual os (which are the same, as long as you use stock roms, but obviously differ if you use an custom source build rom like los).
/system/build.prop is reaf as third source and should contain general android settings.
If the same prop is set in more then one file the last one wins as long as it's no read only prop (ro.*). For ro.* prop the first one wins, because it can't be changed after setting. Exeption: if you use magisk, you can alter ro.* props (by command from the commamdline or a script).
Additionally to these three sources some props are set by init (first os process started by the kernel and controlling the boot process). See:
android_device_oneplus_oneplus3/init_oneplus3.cpp at lineage-18.1 · LineageOS/android_device_oneplus_oneplus3
Contribute to LineageOS/android_device_oneplus_oneplus3 development by creating an account on GitHub.
github.com

nvertigo67 said:
First of all: since op3/t has no dedicated vendor partition /vendor is a symlink to /system/vendor.
Click to expand...
Click to collapse
Thanks for the clear explanation nvertigo!

Does this rom support encryption?

Thank you for your hard work and look forward to the arrival of offical los18.1.