Development [ROM][OOS CAM][OFFICIAL][OnePlus 9 Pro][13.0.0_r30]Nameless AOSP[2023/03/20]

[Gerrrbil]

Does someone know if the following issues are still present in latest build or they've been fixed:
1. Corrupted "metallic" sound when hearing me in calls from the other side
2. Quiet wireless charging mode in AirVOOC charger not working

 

[usmandiaye]

Hey I seem to have issues with flashing this, I've tried using the nameless wiki guide which worked before I goofed it with a kernel flash and then couldn't flash it since, I used MSM to unbrick, updated to oos13 tried flashing and adb sideload threw error 9 at me, then it bricked once more, had to unbrick it and I'm not sure how to continue from here.
Do I need to flash both slots? Do I need to do it with firmware 12 or 13? Is there anything I'm missing?
Any help would really be appreciated as battery life sucks on oos and I really do like this rom

On which ROM are you? Can you get into recovery mode?

 

[bonfire9211]

On which ROM are you? Can you get into recovery mode?

Right now I'm on stock OOS12 I can get into recovery, thinking if I should update to OOS13 before flashing nameless

 

[usmandiaye]

Right now I'm on stock OOS12 I can get into recovery, thinking if I should update to OOS13 before flashing nameless

No, you shouldn't update. Follow the instructions from this link to install nameless : https://wiki.lineageos.org/devices/lemonadep/install.

 

[chandu dyavanapelli]

New build up!

Gdrive mirror:

Google Drive: Sign-in

Access Google Drive with a Google account (for personal use) or Google Workspace account (for business use).

drive.google.com

Source changelog
- Merged February security patch (android-13.0.0_r30)
- Allow to hide the battery icon
- Fixed volume dialog bg tint for inactive rows
- Minor cleanup and improvements

Device changelog
- Update proprietary blobs and Carrierconfig from OOS 11.F.20
- Report "Discharging" status instead of "Connected, not charging" in battery setting, when there is no charger connected
- Fixed offline charging (power off charging)
- Fixed pixel ringtones playback issues
- Fixed dolby atmos crash
- Minor audio and performance improvements


FAQ
1. Dirty flash is fine? if I'm coming from a previous oos 13 firmware based build?

A: Yes, dirty flash works and you can manually sideload or update from ota or local update from ota.

2. How can I flash this build if I'm coming from oos 12 firmware based custom rom or stock oxygen os 12/13?

A. Same as before, all these builds included OOS 13 F.18 firmware.

3. Is OOS 13 F.20 firmware required for the new build? because the new build proprietary blobs are based on F.20.

A. Nope.

4. I'm using Oxygen OS F.20 build, so is the F.18 firmware required for this build?

A. Nope, but all my builds included F.18 firmware for now, so if you're coming from higher/lower version firmware it doesn't matter, when you are flashing the nameless build it's override the firmware which we included in builds.

 

[salihcei]

New build up!

Gdrive mirror:

Google Drive: Sign-in

Access Google Drive with a Google account (for personal use) or Google Workspace account (for business use).

drive.google.com

Source changelog
- Merged February security patch (android-13.0.0_r30)
- Allow to hide the battery icon
- Fixed volume dialog bg tint for inactive rows
- Minor cleanup and improvements

Device changelog
- Update proprietary blobs and Carrierconfig from OOS 11.F.20
- Report "Discharging" status instead of "Connected, not charging" in battery setting, when there is no charger connected
- Fixed offline charging (power off charging)
- Fixed pixel ringtones playback issues
- Fixed dolby atmos crash
- Minor audio and performance improvements


FAQ
1. Dirty flash is fine? if I'm coming from a previous oos 13 firmware based build?

A: Yes, dirty flash works and you can manually sideload or update from ota or local update from ota.

2. How can I flash this build if I'm coming from oos 12 firmware based custom rom or stock oxygen os 12/13?

A. Same as before, all these builds included OOS 13 F.18 firmware.

3. Is OOS 13 F.20 firmware required for the new build? because the new build proprietary blobs are based on F.20.

A. Nope.

4. I'm using Oxygen OS F.20 build, so is the F.18 firmware required for this build?

A. Nope, but all my builds included F.18 firmware for now, so if you're coming from higher/lower version firmware it doesn't matter, when you are flashing the nameless build it's override the firmware which we included in builds.

Thanks a lot for update!

 

[Mar-cel]

QR-code Icon not working latest build

 

[mavi_ay]

QR-code Icon not working latest build

Works great for me. No problem with qr code.

 

[DirtryElectroOP3]

New build up!

Gdrive mirror:

Google Drive: Sign-in

Access Google Drive with a Google account (for personal use) or Google Workspace account (for business use).

drive.google.com

Source changelog
- Merged February security patch (android-13.0.0_r30)
- Allow to hide the battery icon
- Fixed volume dialog bg tint for inactive rows
- Minor cleanup and improvements

Device changelog
- Update proprietary blobs and Carrierconfig from OOS 11.F.20
- Report "Discharging" status instead of "Connected, not charging" in battery setting, when there is no charger connected
- Fixed offline charging (power off charging)
- Fixed pixel ringtones playback issues
- Fixed dolby atmos crash
- Minor audio and performance improvements


FAQ
1. Dirty flash is fine? if I'm coming from a previous oos 13 firmware based build?

A: Yes, dirty flash works and you can manually sideload or update from ota or local update from ota.

2. How can I flash this build if I'm coming from oos 12 firmware based custom rom or stock oxygen os 12/13?

A. Same as before, all these builds included OOS 13 F.18 firmware.

3. Is OOS 13 F.20 firmware required for the new build? because the new build proprietary blobs are based on F.20.

A. Nope.

4. I'm using Oxygen OS F.20 build, so is the F.18 firmware required for this build?

A. Nope, but all my builds included F.18 firmware for now, so if you're coming from higher/lower version firmware it doesn't matter, when you are flashing the nameless build it's override the firmware which we included in builds.

installed via local upgrade. no problems so far

 

[usmandiaye]

I am having this issues on call app " This device is not supported and calls may not function correctly"
Also Twitter videos do not play automatically, the app says " the audio is used by another app".

 

[mavi_ay]

I am having this issues on call app " This device is not supported and calls may not function correctly"
Also Twitter videos do not play automatically, the app says " the audio is used by another app".

1- Uninstall call app or uninstall update on call app.
2- Update call app again.
3- Problem fixed.

I had the same problem.

 

[khanboy619]

1- Uninstall call app or uninstall update on call app.
2- Update call app again.
3- Problem fixed.

I had the same problem.

Thank you for the quick fix, appreciate it!

 

[tkrpprime]

Hi! Thank you for maintaining this rom, it's a really great experience. But I'm having an issue with my bluetooth earphones. When I'm using them on the AAC codec, the audio starts to stutter for no reason. They're only working fine on the SBC codec. The earphones are alright, cuz they work flawlessly on my second phone. I think it's a bug, but is there any fix for that?

 

[netboost]

QR-code Icon not working latest build

Try to uninstall and reinstall Google Play Services.

 

[skywalker_fakih]

Is the White theme mode fixed in the latest rom? or still black icons and background?

 

[bonfire9211]

Hey I'm having a green tint in low brightness, specifically below 19% the screen starts having a green tint, didn't happen in OOS.
Wonder if it's happening to anyone else

 

[bonfire9211]

Hi! Thank you for maintaining this rom, it's a really great experience. But I'm having an issue with my bluetooth earphones. When I'm using them on the AAC codec, the audio starts to stutter for no reason. They're only working fine on the SBC codec. The earphones are alright, cuz they work flawlessly on my second phone. I think it's a bug, but is there any fix for that?

I have the same issue with LDAC on the xm4

 

[LoKoO]

Back to crdroid, crashing oos cam its the only reason.

 

[cavid3232]

.

 

[cavid3232]

hi! I flashed only one slot, and forgot the second. Installed nameless. Should I start over now? With msmtool?