apophis9283 said:

Updated to .276 as well as some other updates. This is probably the biggest update in quite awhile.

I was on Nameless Rom(0902 Build) running singularity 1.04 on OP8p (firmware F62) when i updated to the latest one. One thing i noticed is that the phone was not going into deep sleep mode and as such the ambient temps were hot to the touch. Reverted back to 1.04 and no issues.

MrEvilPanda said:

I was on Nameless Rom(0902 Build) running singularity 1.04 on OP8p (firmware F62) when i updated to the latest one. One thing i noticed is that the phone was not going into deep sleep mode and as such the ambient temps were hot to the touch. Reverted back to 1.04 and no issues.

I haven't had any said issues. If you can grab logs that would be greatif you can grab logs that would be great.

MrEvilPanda said:

I was on Nameless Rom(0902 Build) running singularity 1.04 on OP8p (firmware F62) when i updated to the latest one. One thing i noticed is that the phone was not going into deep sleep mode and as such the ambient temps were hot to the touch. Reverted back to 1.04 and no issues.

Hello! This is not a kernel-side issue. I have a Oneplus 8T and I am also on the Nameless ROM. I was pretty active in the telegram group channel of Nameless since last October. The heating issue is actually caused by Google Pixel Launcher. It was a bug that google already fixed on their Pixel devices. What happens is the Pixel launcher consumes around 22% of the CPU.

I have tested two solutions that work for this problem (this was also approved by the admins in the Nameless group chat):

1. Disable Android system intelligence app
2. Switch to the built-in Nameless launcher

Bumbae said:

Hello! This is not a kernel-side issue. I have a Oneplus 8T and I am also on the Nameless ROM. I was pretty active in the telegram group channel of Nameless since last October. The heating issue is actually caused by Google Pixel Launcher. It was a bug that google already fixed on their Pixel devices. What happens is the Pixel launcher consumes around 22% of the CPU.

I have tested two solutions that work for this problem (this was also approved by the admins in the Nameless group chat):

1. Disable Android system intelligence app
2. Switch to the built-in Nameless launcher

Click to expand...

Hi, i had already disabled both "android system intelligence" and "pixel launcher" before itself(after checking in the telegram group), so i dont think that was the reason it was not going into deep sleep. Thanks for the input.

apophis9283 said:

I haven't had any said issues. If you can grab logs that would be greatif you can grab logs that would be great.

MrEvilPanda said:

Hi, i had already disabled both "android system intelligence" and "pixel launcher" before itself(after checking in the telegram group), so i dont think that was the reason it was not going into deep sleep. Thanks for the input.

Since I have reverted back, i'll install it over the weekend and try to get you the log file.

Yeah mine's sleeping fine.

apophis9283 said:

Yeah mine's sleeping fine.

Hope these log swill suffice. In betterbattery stats i found the following causing wakelocks "job*/com.google.android.apps.messaging/androidx.work.impl.background.systemjob.SystemJobService#2604" (screenshot attached).