[ROM][11][OFFICIAL] LineageOS 18.1 for Razer Phone 2

[npjohnson]

heya, is there any official ETA in when the next nightly patch will be released?

Once a week, on Sunday. Won't vary from that.

First, I want to thank you for the work done - it's great!
Now I want to ask my questions. I installed the system exactly as described here:

Install LineageOS on aura | LineageOS Wiki

wiki.lineageos.org

Today I noticed that an update has come. In the android settings, I selected the update item and downloaded it. An error occurred while trying to install the update. The battery charge was about 70%. I ended up just reinstalling the system cleanly because I thought I had done something wrong.
I have a few questions:
1) When unlocking the bootloader, do I need to "unlock_critical"? The instructions do not indicate this, but I want to completely dispel my doubts.
2) After installing LineageOS-recovery, it logs in in a rather strange way. If I just turn on the phone with the vol+ button holding, then it boots up normally into recovery. If I boot into the recovery from the bootloader through the menu, then when I reboot, half of the screen fills with black, and the second is white. After a few seconds, the phone reboots again and boots into recovery. Is this the expected behavior or did I do something wrong?
3) Can the bootloader be locked after installing Lineage OS?

Updater - What was the error?

1) No you don't need to. It's only if you wanted to flash partitions like the factory image from Razer via fastboot - I would do it in case of emergency.
2) Yeah, some people see this, some don't - if you want to file a bug ticket like the wiki details, we can try to look into it (I hit this too), but it seems to me to be a bootloader bug or something - might not be something we can fix :/
3) Yes, but don't do it - if you mess up recovery and you locked the bootloader there's potentially no way to recover.

I think I managed to capture the freeze during video playback that others are experiencing. I can reproduce it pretty easily by using video playback in Google Photos.

Thanks for a the work so far! Hope this can help.

Please file this as a bug ticket on our Gitlab tracker like the wiki details, I'll take a look at it there and try to help

on slot a or b, sorry im too noob, can you give me command code step by step

No, sorry - just follow the wiki guide - it's very detailed.

 

[64-core CPU]

Updater - What was the error?

No details. When i try to update in the update menu, the update itself does not start, and an update error message appears in the shutter (the reason for the error is not indicated).

At the expense of locking the bootloader. Excuse me for my persistence, but I want to understand to the end and assess all the risks, I wish that the ability to lock the bootloader and keep the data safe is of some value to me. If the recovery is damaged, I will not be able to boot into the bootloader and unlock it via adb (provided that I did not enable OEM unlock in the android developer menu)? With the bootloader locked, will it be possible to update LineageOS or will you have to unlock it every time for updates?

 

[payypalmm]

GPS Location can open work, But low quality

 

[npjohnson]

No details. When i try to update in the update menu, the update itself does not start, and an update error message appears in the shutter (the reason for the error is not indicated).

At the expense of locking the bootloader. Excuse me for my persistence, but I want to understand to the end and assess all the risks, I wish that the ability to lock the bootloader and keep the data safe is of some value to me. If the recovery is damaged, I will not be able to boot into the bootloader and unlock it via adb (provided that I did not enable OEM unlock in the android developer menu)? With the bootloader locked, will it be possible to update LineageOS or will you have to unlock it every time for updates?

Really - please don't do this. Especially considered we flash a disabled vbmeta image, and you destroy any chance at verity working by flashing gapps.

And the OEM unlock toggle resets on every boot when you're locked - so you'd never have it checked when you need it to.

 

[jal3223]

Should Verizon owners open up a bug request for Volte, or is it being looked into? @npjohnson

 

[sikampang]

Once a week, on Sunday. Won't vary from that.

Updater - What was the error?

1) No you don't need to. It's only if you wanted to flash partitions like the factory image from Razer via fastboot - I would do it in case of emergency.
2) Yeah, some people see this, some don't - if you want to file a bug ticket like the wiki details, we can try to look into it (I hit this too), but it seems to me to be a bootloader bug or something - might not be something we can fix :/
3) Yes, but don't do it - if you mess up recovery and you locked the bootloader there's potentially no way to recover.

Please file this as a bug ticket on our Gitlab tracker like the wiki details, I'll take a look at it there and try to help

No, sorry - just follow the wiki guide - it's very detailed.

ok thanks for your reply, i was installed this rom from wiki guide

 

[unsponsoredgeek]

It was easy to flash and booted up right out of the box. WiFi and Bluetooth worked as well.

I did find a bug: the flashlight does not work. The Flashlight icon is greyed out with the text "Camera in use". The camera is not in use and even rebooting the phone does not fix the error.

I can't delete and reinstall the Camera app, so there is no workaround for now.

Just updated to the new build via ADB. (The updater failed.) and the camera/flashlight bug persists....

 

[sikampang]

bug rom build 20 juny, sometime when charging from 2% to 50% this phone always connect and disconect every minute.. after 60% charging work normal
and when play game sometime speaker not working and working again

 

[64-core CPU]

Really - please don't do this. Especially considered we flash a disabled vbmeta image, and you destroy any chance at verity working by flashing gapps.

And the OEM unlock toggle resets on every boot when you're locked - so you'd never have it checked when you need it to.

OK, thanks.

 

[tzukiwy]

Just updated to the new build via ADB. (The updater failed.) and the camera/flashlight bug persists....

did you do it via flash or sideload?

 

[sako_1930]

I just extract the payload and flash system/vendor/boot/vbmeta images (after restoring to razer mr6) and the camera and flash problem fixed but now there is new issue appears there is no sound came out of the speakers.
any idea how to fix that or what image file i should flash next to make speakers work ?

p.s. I just did that because I flash factory vendor\boot\vbmeta\GSI rom and the camera still used the telephoto one so I decided to test that this way.

 

[npjohnson]

Should Verizon owners open up a bug request for Volte, or is it being looked into? @npjohnson

Ive said a few times, bug ticket with logs pls

 

[jal3223]

Ive said a few times, bug ticket with logs pls

Sorry man, I didn't see that you said that relating to this issue. I'll try to grab logs, but I'm not hopeful that they will help with Volte. Thanks for the reply though.

 

[unsponsoredgeek]

did you do it via flash or sideload?

The original build I flashed via the standard method (reformatting before loading the ROM).
For the update I used LineageOS recovery to update via ADB sideload (without reformatting).

 

[npjohnson]

Sorry man, I didn't see that you said that relating to this issue. I'll try to grab logs, but I'm not hopeful that they will help with Volte. Thanks for the reply though.

they will be better than nothing haha - we can compare working volte log to non-working.

 

[tzukiwy]

The original build I flashed via the standard method (reformatting before loading the ROM).
For the update I used LineageOS recovery to update via ADB sideload (without reformatting).

can the adb sideload be done on a windows machine? or does it need linux/mac. also did you lose all your data after sideloading?

 

[jal3223]

they will be better than nothing haha - we can compare working volte log to non-work

they will be better than nothing haha - we can compare working volte log to non-working.

Man, I feel like an idiot. lol. I flashed stock to get logs regarding signal, then flashed Lineage for logs and now signal is working on Verizon. I'm not sure if it just needs to be registered in stock first, but now IMS is registered in Lineage for me. I have verified everything by placing a phone call and receiving an SMS. Sorry for the false report.

 

[npjohnson]

Man, I feel like an idiot. lol. I flashed stock to get logs regarding signal, then flashed Lineage for logs and now signal is working on Verizon. I'm not sure if it just needs to be registered in stock first, but now IMS is registered in Lineage for me. I have verified everything by placing a phone call and receiving an SMS. Sorry for the false report.

Wait, so VZW IMS works for you?

That's awesome if so!

 

[jal3223]

Wait, so VZW IMS works for you?

That's awesome if so!

Yeah, it does. It started work after getting IMS registered on stock and then flashing Lineage. I used MR6 firmware specifically. I'm not sure if maybe the system got corrupt or something with the previous test builds. Anyways, it is working though. Thank you!

 

[N_otori0us_]

can the adb sideload be done on a windows machine? or does it need linux/mac. also did you lose all your data after sideloading?

it can be done on Windows, look up "minimal adb and fastboot", that's the thing I used. If you're installing the software for the first time then yeah you are supposed to wipe all your data before you flash it meaning you'll lose all your data.