Development [ROM][OOS CAM][OFFICIAL][OnePlus 9 Pro][13.0.0_r41]Nameless AOSP[2023/05/09]

[pineappleraptor]

Hi everyone! I'm having a problem with Google messaging RCS (Chat features) in the stock Google Messages App. I think it could be related to this ROM because on Oxygen OS I never had this issue.

What happens is when I talk to a known Chat user in Google Messages it keeps forcing me to SMS mode several times throughout the day. When the Chat user sends me a message it shows that it was sent via "Chat" but when I then reply, it puts my reply to "SMS". Resetting network settings (,including pulling the SIM) and clearing the app cache does not solve the issue.

I've done lots of App troubleshooting but to no avail.

On OxygenOS13, I could use RCS features with anyone who used them on their end and it would never force me to SMS. Thanks to anyone who could advise!

 

[kodayoda713]

i'm thinking of flashing another rom because the real problems (camera crashing/blurry/black screen, gifs/videos not loading in apps like reddit or twitter, bad bluetooth audio call quality...) don't seem to get fixed. Has anyone had that same experience with other roms? Is it a base problem ?

In regards to the gif/video issue, on the lineage posts describing this, someone suggested changing this setting in developer options to Disabled. Seems to have worked for me.

 

[yamanetoshiro]

Hi everyone! I'm having a problem with Google messaging RCS (Chat features) in the stock Google Messages App. I think it could be related to this ROM because on Oxygen OS I never had this issue.

What happens is when I talk to a known Chat user in Google Messages it keeps forcing me to SMS mode several times throughout the day. When the Chat user sends me a message it shows that it was sent via "Chat" but when I then reply, it puts my reply to "SMS". Resetting network settings (,including pulling the SIM) and clearing the app cache does not solve the issue.

I've done lots of App troubleshooting but to no avail.

On OxygenOS13, I could use RCS features with anyone who used them on their end and it would never force me to SMS. Thanks to anyone who could advise!

I had this problem as well!! Even after taking logs and searching multiple threads, I could not figure out what was causing it so I switched roms. I have flashed numerous roms since (Stag OS, CrDroid, Lineage OS, Watchdogs, Xtended, etc).
Nameless seems to be the only one with this issue...

 

[lev.sagal]

Does anyone have an issue with charging on the latest version from 18th February? I mean when connecting the cable to charge the charging indication (sound, animation and screen powers on) repeats every 10-15 seconds for about two minutes and at the same time quick charging doesn`t work. Need to disconnect the cable a few times but again charging indication repeats after each connect.

 

[LeonTLR]

Just updated to latest version. My flashlight in the pulldown menu says "camera in use" and doesn't work. Any fixes for that?

Edit, figured it out. It was a setting in aosp mods.

 

[ArtemKomrad]

Does anyone have an issue with charging on the latest version from 18th February? I mean when connecting the cable to charge the charging indication (sound, animation and screen powers on) repeats every 10-15 seconds for about two minutes and at the same time quick charging doesn`t work. Need to disconnect the cable a few times but again charging indication repeats after each connect.

I am having the same problem. Appeared after the last update. Hope it gets fixed soon

 

[f2bacon]

@chandu dyavanapelli i think you've been a part of every rom i've used over the last 6 years! small world.
im coming from the oneplus 8t with havoc rom. it looks like you've stopped working on havoc, and switched to nameless? if i can expect a similar experience i'll order the 9 pro right now instead of the pixel 6 pro

 

[Zesty59]

Currently on rooted f.73, do i need to downgrade?

 

[Rtxda]

Maybe someone can give me/semi noob a tip what I can do best now?
In short:
I get the orange state notification while booting and I don't have root anymore.

Long story:
About 3 months ago I bought my new phone and straight away installed the Nameless ROM and Magisk. This went quite well (needed to install the ROM twice. After the first the touch function wasn't available, after wiping and installing again it worked).
For some days I got a notification that there is an update avalable. So I installed the updated Nameless ROM three days ago.
- As instructed in the Magisk-thread, I first disabled all modules in Magisk.
- Then I selected the downloaded update file in the system update menu. I didn't restart the phone right away.
- I selected "install to inactive slot" in Magisk and then restarted.
- While this restart the orange state notification came up. Though everything seemed to be normal, still rooted.
- Then I probably made my slightly frustrated error. I selected "install to inactive slot" in Magisk again.
- Afterwards the error "Qualcomm crashdump mode" came up.
- Then I just tried to dirty flash the updated ROM-version again (Instruction "Install LineageOS on lemonadep").
- After that the phone started again with the orange state message, but without root.
- Then I tried to boot temporarily with root, but after "fastboot reboot" the "Qualcomm crashdump mode" came up again.
- Then I dirty flashed the updated ROM again.
And this is now my current status. - The phone starts with the orange state message and has no root.
What is the best thing I can do now? Would it work to wipe (I would of course prefer a solution without wipe) and flash the updated ROM? (Would this also require flashing the additional partition-files?)
I would be grateful for any help.
(I hope everything is understandable - used an online translater)

 

[kodayoda713]

Maybe someone can give me/semi noob a tip what I can do best now?
In short:
I get the orange state notification while booting and I don't have root anymore.

Long story:
About 3 months ago I bought my new phone and straight away installed the Nameless ROM and Magisk. This went quite well (needed to install the ROM twice. After the first the touch function wasn't available, after wiping and installing again it worked).
For some days I got a notification that there is an update avalable. So I installed the updated Nameless ROM three days ago.
- As instructed in the Magisk-thread, I first disabled all modules in Magisk.
- Then I selected the downloaded update file in the system update menu. I didn't restart the phone right away.
- I selected "install to inactive slot" in Magisk and then restarted.
- While this restart the orange state notification came up. Though everything seemed to be normal, still rooted.
- Then I probably made my slightly frustrated error. I selected "install to inactive slot" in Magisk again.
- Afterwards the error "Qualcomm crashdump mode" came up.
- Then I just tried to dirty flash the updated ROM-version again (Instruction "Install LineageOS on lemonadep").
- After that the phone started again with the orange state message, but without root.
- Then I tried to boot temporarily with root, but after "fastboot reboot" the "Qualcomm crashdump mode" came up again.
- Then I dirty flashed the updated ROM again.
And this is now my current status. - The phone starts with the orange state message and has no root.
What is the best thing I can do now? Would it work to wipe (I would of course prefer a solution without wipe) and flash the updated ROM? (Would this also require flashing the additional partition-files?)
I would be grateful for any help.
(I hope everything is understandable - used an online translater)

To my knowledge, root is not what causes orange state message. It's the unlocked bootloader, which is pretty much required if you're flashing custom roms. If you search in the nameless telegram group, you can find the abl.img. to flash in flashbootd. That will fix your orange state message

 

[Rtxda]

To my knowledge, root is not what causes orange state message. It's the unlocked bootloader, which is pretty much required if you're flashing custom roms. If you search in the nameless telegram group, you can find the abl.img. to flash in flashbootd. That will fix your orange state message

That helped. Thanks. No orange state notification.
Maybe I should post this in the Magisk thread, but since it was part of my previous post:
I can't root the device. When I try to temporarily boot with root (tried twice: with a self patched file and one from the Magisk thread), Windows CMD says okay/okay, and then the device reboots by itself (before I can enter fastboot reboot). And then I end up in Qualcomm crashdump mode again. But then I can just reboot the device and end up in the system. But without root. Without being able to select anything under Magisk other than patching a file.
Does anyone else have an idea for this?

 

[kodayoda713]

That helped. Thanks. No orange state notification.
Maybe I should post this in the Magisk thread, but since it was part of my previous post:
I can't root the device. When I try to temporarily boot with root (tried twice: with a self patched file and one from the Magisk thread), Windows CMD says okay/okay, and then the device reboots by itself (before I can enter fastboot reboot). And then I end up in Qualcomm crashdump mode again. But then I can just reboot the device and end up in the system. But without root. Without being able to select anything under Magisk other than patching a file.
Does anyone else have an idea for this?

That's the most correct way to do it, but you can also try sideloading magisk in recovery. Download the magisk APK, rename to zip file, then sideload.

 

[Rtxda]

That's the most correct way to do it, but you can also try sideloading magisk in recovery. Download the magisk APK, rename to zip file, then sideload.

Thank you very much! It worked. - No orange state notification anymore and back with root.
And I recognized that I already had Magisk as zip on my PC. I must have sideloaded Magisk while the first installation of the ROM too.

 

[cavid3232]

sound problem with incoming call. Does anyone know how to solve the problem?

 

[cavid3232]

sound problem with incoming call. Does anyone know how to solve the problem?

?

 

[kodayoda713]

?

Maybe try uninstalling updates and clear cache of phone app, then update app through play store

 

[El Brillantinas]

Testing this awesome ROM. No problems so far.

Question: OTA updates come in time? If so, Is it safe to update via OTA?

 

[bbortel93]

Back on Nameless after a while, fluid as always. However, I was unable to join a zoom meeting just now. I had to use my girlfriend's iphone ‍.
Any idea why that was the case? I was able to join last week using WatchDogs just fine. Solution?
Thank you dev

 

[chandu dyavanapelli]

New build up!

Source changelog
- Added lockscreen shortcuts customization
- Added vertical QS layout
- Added support for showing battery level for AirPods series
- Added more fonts, signal and Wi-Fi icons
- Allow to set lockscreen clock font
- Allow to adjust display's RGB color balance
- Allow to change volume dialog position in landscape mode
- Allow to mute media volumes via alert slider for bluetooth devices
- Allow to disable heads up notification in landscape mode

Device changelog
- Merged LA.UM.9.14.r1-21200-LAHAINA.QSSI13.0 CLO / android11-5.4 lts / ASB-2023-03-05_11-5.4 tags in the kernel
- Updated blobs and firmware from OOS 11.F.21
- Fixed NFC not working properly for some users
- Fixed overheating issue
- Fixed heavy active/inactive drains
- Fixed wired charging randomly gets disconnected
- Fixed wired/wireless warp charging randomly gets slow down
- Fixed random media playback issue in social media apps

Note
- Security patch merge is skipped this month due to huge changes in QPR2. It will come in next month release with April security patch


Gdrive mirror:

Nameless-AOSP_lemonadep-13.0-20230320-0338-Official.zip

Nameless-AOSP_lemonadep-13.0-20230320-0338-Official.zip

drive.google.com

 

[usmandiaye]

New build up!

Source changelog
- Added lockscreen shortcuts customization
- Added vertical QS layout
- Added support for showing battery level for AirPods series
- Added more fonts, signal and Wi-Fi icons
- Allow to set lockscreen clock font
- Allow to adjust display's RGB color balance
- Allow to change volume dialog position in landscape mode
- Allow to mute media volumes via alert slider for bluetooth devices
- Allow to disable heads up notification in landscape mode

Device changelog
- Merged LA.UM.9.14.r1-21200-LAHAINA.QSSI13.0 CLO / android11-5.4 lts / ASB-2023-03-05_11-5.4 tags in the kernel
- Updated blobs and firmware from OOS 11.F.21
- Fixed NFC not working properly for some users
- Fixed overheating issue
- Fixed heavy active/inactive drains
- Fixed wired charging randomly gets disconnected
- Fixed wired/wireless warp charging randomly gets slow down
- Fixed random media playback issue in social media apps

Note
- Security patch merge is skipped this month due to huge changes in QPR2. It will come in next month release with April security patch


Gdrive mirror:

Nameless-AOSP_lemonadep-13.0-20230320-0338-Official.zip

Nameless-AOSP_lemonadep-13.0-20230320-0338-Official.zip

drive.google.com

Thank you very much Sir. Just Great !