yashsingh1/xdaforums huggingface dataset:
[Pixel C Original Android Development] muerte33:
I think I finally figured out what was wrong with fastboot on my Pixel C.

I saw some old 2018 threads about others having my "Unsupported Command" issues with fastboot.

I went into TWRP 3.7.0_9-1 and clicked on Advanced, then went into Terminal.

Luckily fwtool comes with TWRP in the sbin folder.

I issued the command:

fwtool vbnv read dev_boot_fastboot_full_cap

This gave a 0, so I knew it needed to be fixed (set to 1 from 0).

I then issued this command:

fwtool vbnv write dev_boot_fastboot_full_cap 1

I rebooted the tablet and double checked that it held that "1" too.

I'll try to see if I can run fastboot commands now.

Hopefully this can help anyone else that got this flag reversed.
[Pixel C Original Android Development] npjohnson:
the question I pose is, how the hell did you put TWRP on there to begin with lol.

also, how did that flag get set at all?
[Pixel C Original Android Development] muerte33:
I remember putting TWRP on a LONG time ago.

The version I ran for years was 3.4.0-0 (which was released around June 2020).

I only recently updated TWRP to 3.7.0.9-1 from TWRP 3.4.0-0 because I could not fastboot it either.

I remember using various versions of Magisk over the years, but ended up removing them every time.

This may have been how that flag got reversed. The device always shows bootloader unlocked.

You could run the command "Fastboot Flashing Unlock", and it would say "Device Already Unlocked".

I always used 3.4.0-0 TWRP to load ROMs from FollowMSI and Michie, so I never ran into the fastboot issue.

I am hoping to have some time to load the Lineage recovery and the new ROM later this week.

Thanks for all the help with this, I would love to squeeze an extra year out of this tablet!

Once google releases the next tablet (after this one with the Tensor G2), I may jump on a new one.

Update:

I was able to reflash the newest TWRP, so I am VERY confident the flash of the lineageOS recovery should work now!

I always got the Failed (Remote: "Unsupported command") after Writing 'recovery'.
[Pixel C Original Android Development] muerte33:
I got the LineageOS recovery.img installed with NO PROBLEMS!

When I went to do the Format Data/Factory Reset, it displayed these messages/errors:

Wiping Data

Formatting /data

Formatting /cache

Formatting /metadata

error: recovery: format_volume: FS_Type "EMMC" unsupported.

Resetting Memtag Message

Data Wipe Failed.

I went ahead and sideloaded the newest April ROM, and rebooted the system anyway.

I saw the normal messages upon boot:

Android System "There's an internal problem with your device contact your manufacturer for details".

"Serial Console Enabled, performance is impacted"

Speech services app closed when starting up.

I was able to connect to my network and finish setting up the Pixel "C".

There were 15 apps that needed updating.

All I can say is WOW, great job !

Thanks very much for all this effort!!
[Pixel C Original Android Development] npjohnson:
internal problem is expected, we are working on it.

Serial is for my debugging purposes, it will be disable when I'm done with bringup.

Speech services I will look into.
[Pixel C Original Android Development] muerte33:
Some good news:

I installed a fitness app that connects to a watch via BT that is working.

I installed a health app that communicates via the microphone to an external device that does EKGs.

Both installs did run into a little problem when trying to set permissions.

The installs hung, but a forced power down got me up/running again, then both apps worked fine after that.

That EKG app was always a pain to run on my phone because NFC gets in the way. I would have to remember to turn NFC back ON after I got done running the EKG. This is not a problem with the Pixel "C"!

The Google Playstore successfully updated from 40.4.31-31 to 40.6.31-31 too.

If I close the EKG app and then disable the Microphone from the pull down menu, then launch the EKG app again, it tries to tell me that the Microphone is OFF, but it hangs the Pixel "C" hard.

On my phone it detects NFC being on first with a warning, then gives a warning about the microphone being OFF.

If I launch that app with microphone ON, from the Pixel "C" with LineageOS21, it works perfectly (which I will leave on from now on).

I normally DISABLE the microphone and camera on my phone during the day, but leave NFC on.

I wish Google would add NFC to the quick pull-down screen like they do for several other functions.

When security updates ended on the Pixel "C" for LineageOS20, I bought a Teclast Android 14 tablet from Walmart. The Pixel "C" ROM you have provided is noticeably faster than the brand new Teclast.

The EKG app I use updated about 3 months ago while on the April 2023 LineageOS20, and refused to run because it sensed it was running on an unlocked bootloader or a machine that did not pass safetynet, but it runs on your LineageOS21 ROM!

Great job NPJohnson !!
[Pixel C Original Android Development] wsxjh:
It still flashes back a lot when using the Bluetooth headset, which is very disruptive to normal use. Thank you very much for your work though, it would be great to have this bug fixed.
[Pixel C Original Android Development] A$h!$h:
Recovery support OTG?
[Pixel C Original Android Development] npjohnson:
Should? Idk why you would want that.
[Pixel C Original Android Development] A$h!$h:
Adb not working to flash rom
[Pixel C Original Android Development] npjohnson:
It works fine - that is not an error - it works, just reports it doesn't.

Continue and flash the ROM - it works fine.
[Pixel C Original Android Development] npjohnson:
Buy a different USB port, cable, or check your drivers, I literally only sideload.
[Pixel C Original Android Development] A$h!$h:
Camera issue only pending.... hope sir u will solve it
[Pixel C Original Android Development] npjohnson:
I literally have stated multiple times what is broken, and why it's not feasible to fix at this time.
[Pixel C Original Android Development] thorepck:
Hi Nolen. I'm trying to build my own zip without gapps, but it fails with 'ERROR: Duplicate module nvgpu.ko' - probably due to change 385973? Any hints on how to remedy this?
[Pixel C Original Android Development] npjohnson:
Are you building 20 or 21?

21 should be fine.
[Pixel C Original Android Development] thorepck:
I'm building 21
[Pixel C Original Android Development] npjohnson:
I just built it last week, really not sure what would be up
[Pixel C Original Android Development] EnginEAR:
This is amazing!

Thank you!!

Can't wait for the June 2024 build...
[Pixel C Original Android Development] npjohnson:
Unofficial build users:

For the next build you will need to update by hand in recovery and select "Yes" when prompted about signature mismatch.

I have started signing my builds again, and set it up so that you can migrate without wiping data, but you must select "Yes" to ignore signatures once to swap to a signed build.

Enjoy!
[Pixel C Original Android Development] muerte33:
Thanks very much for all your efforts! I saw that the initial warning message on boot is gone now too!
[Pixel C Original Android Development] npjohnson:
yup! Fixing stuff very very slowly
[Pixel C Original Android Development] muerte33:
Should we update the recovery too before we apply the new July ROM?

Thanks!
[Pixel C Original Android Development] npjohnson:
nope it does it all automagically
[Pixel C Original Android Development] acepool08:
Sorry for asking, but is this build already available? I canot find it and I don't know if I have to do something to be able to try it.

Thanks for the great work!
[Pixel C Original Android Development] npjohnson:
They start publishing for all my devices today.
[Pixel C Original Android Development] muerte33:
I downloaded the 1.81gb zip file using Firefox onto the Pixel itself, then booted to recovery, and installed the ROM from there. I replied "YES" to the prompt, and it updated and rebooted successfully. I almost started the update before checking my battery level, so everyone needs to do that before updating!

When I go to: Settings, System, System Updates, Preferences:

I did notice that the switch under the update preferences on my Pixel "C" has "Update Recovery" set to "OFF".

Should this be turned on?

Thanks very much Mr Johnson for version 21-20240704-UNOFFICIAL-sphynx!!
[Pixel C Original Android Development] npjohnson:
Yeah go ahead and turn it on.
[Pixel C Original Android Development] acepool08:
Is there anything one can do to help with the constant System UI and launcher crashes?

That and the BT/headphone jack are probably the only issues I would consider big enough...

Thanks!
[Pixel C Original Android Development] npjohnson:
BT issue?
[Pixel C Original Android Development] acepool08:
I tried connecting two devices at the same time (headphones and a controller) and it was disconnecting from one of them constantly, which was not convenient.
[Pixel C Original Android Development] Punze:
In the 20240722 version, the sound picture is out of sync when the video is played.
[Pixel C Original Android Development] Punze:
After restarting the device, the sound and picture are synchronized
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] npjohnson:
Razer Phone 2

- Your warranty is now void.
- You have been warned.
- Use at your own risk.

Introduction:

This is the Official Lineage OS 21 thread for the Razer Phone 2.

Downloads:

Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.

aura - Official builds​

aura - My unofficial with Google Apps/Pixel goodies included. OTA's roll roughly once a month. Support not guaranteed or implied.​

If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.

Known Bugs:

Known bugs:

- Chroma RGB LEDs are not implemented yet

Known bugs (won't fix):

- Can't switch screen resolution (defaults to 2560x1440)

Find any more? Report them according to this guide.​

Notes:

The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.

Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!​

Kernel Source: https://github.com/LineageOS/android_kernel_razer_sdm845
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] TechX1991:
error on the download page, can't download it
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] npjohnson:
Yeah, GitHub asked me to clear old builds, they're uploading but it may take a day or so.
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] lohgab:
hi, thanks for the continues upgrade to android14.

my phone cts profile match fail, I think it was from android13/os20 around Nov/Dec last year when my wallet app doesn't work.

I was hoping the upgrade can fix this but still CTS profile match fail. Appreciate the help on this.

Thank you again, as with lineageos21 upgrade this phone feels faster.
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] npjohnson:
Nope, my workaround was patched.
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] TechX1991:
Can we get a rom without gapps?
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] npjohnson:
Not until the official comes out (no ETA).
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] lohgab:
Thanks for the response.
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] unsponsoredgeek:
It works!

Hopefully the RGB bits can be ported from PixelExperience before it sunsets.
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] XxRaVenxX21:
Works great! Love the updates! I contributed!
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] Jitteryheart87:
any chance that one of you would be willing to make a video tutorial on how to do this lineageOS 20 to 21 upgrade on the razer phone 2??
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] npjohnson:
No, the wiki really covers it all accurately and install instructions change.

So a video would be outdated within some short time.
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] Jitteryheart87:
oh ok. yeah that makes sense
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] Jitteryheart87:
which wiki page? you mean this one... https://wiki.lineageos.org/gapps/ or are you referring to a different one?
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] npjohnson:
Why would you need the Google apps page? Aura is your device, so go to it's page and grab the upgrade guide.
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] Jitteryheart87:
when i go to your unof

when i go to your "unofficial with Google Apps/Pixel goodies included..." page https://wiki.oddsolutions.us/devices/aura/ & click on downloads, it says "your device does not exist" and there is just nothing to download
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] npjohnson:
Yeah, I'm redoing my infrastructure, builds should be up by Tuesday or Wednesday
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] Jitteryheart87:
oh ok.

thank you : )
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] npjohnson:
Sadly, this device utilizes android.hardware.radio@1.3 (or below).

This means that the March security bulletin - known as QPR2 - fully killed this device.

We (LineageOS) are trying to write a wrapper to make older radio HAL versions compatible with newer radio HAL versions.

With that said, we may or may not be successful and we're entirely unsure how long it would take.

So, sadly, for now, this device has 21 builds disabled - I have deployed one final February ASB unofficial build people can use in the intermediary (or you can use the final official build).

I will announce here if/when the device is re-added to the roster.
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] Hammerfest:
That truly sucks.

Will be keeping an eye out on this thread, have yet to find a phone where the loss of front facing speakers isnt an absolute loss of interest.

EDIT: ya, just looked at current and some upcoming phones, zero interest, so anything that can be done to keep it alive would be appreciated.
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] npjohnson:
We had two issues with QPR2:

- The easier android.hardware.radio.config@1.0 was dropped - we were able to wrap that quickly

- The harder fact that android.hardware.radio@1.3/1.2/1.1/1.0 were all dropped.

We can't use newer versions natively because our modem firmware (we can't touch that) is far too old. We can only "wrap" it by handling and translating new responses to the old modem - not fun, not easy, and needs to cover x^n edge cases - going to take a while if we are even able to.
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] Jitteryheart87:
i second what Hammerfest said but i also do understand your response. i will be keeping an eye out as well for any updates to this (which i do hope will still come eventually) but either way, i do want to mention that i do truly appreciate all of your efforts and contributions that you've made for this device so far, it has made me able to use my razer phone 2 for longer than i had expected to and i thank you for that : )
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] ProjectPatatoe:
Thank you for your work! I'll be keeping an eye out on this.
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] KillerTheLord:
@npjohnson This might sounds like an extremely dumb question. I understand that the radio (and hence all of SIM functionality) will stop working. Will rest of the pieces WiFi, BT etc keep on working? If yes, would it be possible to get updates with that heading that SIM functions won't work? Or does LOS team think that it isnt worth it maintaining a device when its primary function of calling is lost?
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] npjohnson:
Yes anyone can go build broken images rn.

Lineage will not be doing that officially ever.
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] unsponsoredgeek:
Bummer. Thanks again for all your efforts.

I'll stick to your last official builds until they are pronounced dead even though e/OS is still alive (for now).

I have one RP2 and one RP1 running your last build(s) and the spare RP2 still on the last PixelExperience Plus build.
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] npjohnson:
The radio issue has been fixed and official builds begin again within the next week within the next week
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] unsponsoredgeek:
Yes...HaHaHa.YES!
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] Hammerfest:
thats friggin fantastic, i tried, i really tried, there's nothing coming I care for :(

Will dump some new phone money to ya when i can, very much love to you and the team!
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] droiddudeuk:
Hi, really good rom but I have been having some issues with audio clipping on a few emulators PSP PS2 from what I have tried. it doesn't seem to affect video playback, any suggestions?
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] BoppingMoose:
So awesome you are keeping this phone alive!

Is the camera handling the different lenses properly when zooming? Previous Lineage versions locked to just the standard rear camera and didn't shift to the 2nd camera on zoom.
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] npjohnson:
It treats it as an auxillary camera now. But yes it works.
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] nubiusss:
Can you update the gpu drivers? Its been an issue for awhile now since Razer used their own custom driver. Games nowadays requires 385 or higher drivers for their games.
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] npjohnson:
"An issue" - what exactly is the issue?

I really hate just kanging things for the reason of doing so.

What games require specific adreno versions?
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] nubiusss:
Wuthering Waves, they just released it but it requires a driver higher than V385. Sorry if i troubled you. Thanks!
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] Hammerfest:
I know its not helpful, but I had been sideloading an update to the gpu driver due to issues I had with games, cant bloody remember what they where as I dont game on my phone at all anymore -_-

Will try to check my history and load without drivers when your unofficial update drops with all the fix's
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] BoppingMoose:
So in a camera app can you cycle through the 3 cameras (front back and zoom) or does it still switch to the optical 2x when you zoom in?
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] npjohnson:
Cycle through.
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] nubiusss:
This is what I encounter when trying to play Wuthering Waves. Currently running PE13 as LineageOS 21 was freezing my whole phone, forcing me to restart the system everytime.
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] ltlwet20:
Hello and thank you for keeping the RP2 alive. I updated last week and yuzu and vita3k stopped working. I can get into the emulators but when I go to play a game the emulators crash. I've tried reinstalling the emulators but that doesn't work. I also updated to yesterday's lineage update. Any ideas?
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] simondyno:
Hi npjohnson -

I appreciate your dedication. Thank you for all the time and effort you've put into this project!

Installed your custom version last week and have discovered a couple things:

Audio tip

I resolved audio playback issues by disabling AudioFX.

HDMI Issue:

Trying to output video via HDMI over USB causes phone to restart.

This happens with the three different USB-C hubs I've tested.

Hub works until you plug in the HDMI cable to a monitor, and then the phone restarts.

If you use a USB-C monitor, the phone restarts as well.

This same issue also occurred in Lineage 18, but I didn't try on 19 or 20.

Found a similar report with the same behavior but different device: https://gitlab.com/LineageOS/issues/android/-/issues/6130

I'll post a bug report when I can get logcat over wireless ADB working.

Thanks!
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] npjohnson:
interesting, lmk when you have logs
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] simondyno:
It's AudioFX you need to turn off to workaround the audio issues, not Dolby. Corrected above.

And I'll flash the latest nightly official and get logs from that before posting to gitlab - in the meantime,

here are the logs when connecting to the Pinephone USB-C HDMI connected dock, and an Epson moverio bt-40, a usb-c HMD. Also logcat -d catching several restarts.
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] waffleboi9000:
1. I'm having issues with freezes when viewing videos, and certain kinds of media, one consistent way was viewing gifs in the discord app. These freezes completely lock up the device and require holding the power button until it reboots. I recall experiencing this same issue in earlier builds of the pixel experience rom, but they were eventually fixed. Here's a link to the relevant part of the Pixel Experience thread in case it helps: https://xdaforums.com/t/rom-12-1-official-pixelexperience-plus-discontinued.4374131/page-13. As part of this issue, I was also seeing flickering while watching youtube videos in fullscreen mode.

2. Also wanted to mention that I'm experiencing audio distortions and stuttering when playing games (I only tested Honkai Star Rail) at below 50% volume through the speakers, which was also seen in older pixel experience builds.

3. Would it be possible to port over the razer chroma controls and dolby atmos support from the PE builds?
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] waffleboi9000:
just wanted to say that i can confirm this behavior, with a RP2 connected to a lenovo usb-c dock and a monitor using hdmi.
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] npjohnson:
No we won't be importing razor chroma or Adobe Atmos.

If anything we'll do a proper light hal at some point.

Dolby we won't include for licensing reasons.
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] waffleboi9000:
Thanks for the quick response, makes sense.
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] npjohnson:
Unofficial build users:

For the next build you will need to update by hand in recovery and select "Yes" when prompted about signature mismatch.

I have started signing my builds again, and set it up so that you can migrate without wiping data, but you must select "Yes" to ignore signatures once to swap to a signed build.

Enjoy!
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] waffleboi9000:
7/4/24 update didn't fix the freezing from discord gifs, but it did fix the flickering youtube videos.

EDIT: The flickering is actually still there.
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] NeoEdo:
7/4: Thank you for the update! Updating the unofficial manually was simple.

The only recurring issue I have is that the videos on "X" still cause the screen to flash. (Started with the last update)

Other than that, thank you again for keeping these phones alive!
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] waffleboi9000:
Does anyone know what QPR the unofficial release is on? The reason being that I was looking to use my phone as webcam, a feature listed as part of Android 14 QPR1, but I don't seem to see it when connecting to my laptop via usb-c.
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] npjohnson:
QPR3, the latest.

That is a feature of the platform, but it requires heavy device specific stuff that hasn't been back ported to the 4.9 kernel.

Maybe someday.
[Razer Phone 2 ROMs, Kernels, Recoveries, & Other D] waffleboi9000:
Makes sense, thanks for the quick response.