[ROM + KERNEL][8.1.0][EAS+CLANG 5.0][OFFICIAL] AospExtended v5.8

[The Marionette]

That means the JBL audio mods won't work now, correct?

Nope, audio on mods should work, I didn't remove the commits for that.
I merely removed the commits which broke video codecs from the upstream.

Video playback now works and audio on mods still works ( again, mp3 tracks are buggy; you need to play/pause and lock/unlock the phone till it works every boot but flac files work from the get go ) .

 

[szybki_ben]

How can i enable deep sleep freqs?

 

[The Marionette]

How can i enable deep sleep freqs?

You don't have to.
If you actually let your phone stay on the desk untouched for a couple of minutes and after refreshing the cpu state data in Kernel Audiutor, you should see that Deep Sleep was used for that amount of time.

 

[szybki_ben]

You don't have to.
If you actually let your phone stay on the desk untouched for a couple of minutes and after refreshing the cpu state data in Kernel Audiutor, you should see that Deep Sleep was used for that amount of time.

Well I'm checking it on kernel auditor for about 2 days now. I regularly have to leave my phone about 2/3 times in my car for about an hour every day, and every time i check on cpu stats if it got into deep sleep and every time it's listed in unused frequencies :/

 

[tatomoreno]

for me it stays the same, for some reason when I restore my backup with titanium app, the phone returns without being able to receive calls.

PS sorry for the bad english

 

[yanniclord]

I had to completely wipe and reflash my Phone, and ever since I have set it up newly, I am totally unable to restore apps with TitaniumBackup, doesn't matter what I do. It worked with the previous version, but after Dirty Flashing that, multiple apps started constantly Force Closing on me, so I wiped my Phone and installed AEX 5.5 (latest), Magisk 16.4 and OpenGapps.arm64 . However, like I said, any attempt to restore apps with TitaniumBackup seem to fail no matter what, even tried Indirect Restoration in the Settings of TitaniumBackup, didn't help either, the restoration just get's stuck. Any idea?

Just as a side note, ctsProfile is still true even after a complete wipe, so that works solid.

 

[The Marionette]

Well I'm checking it on kernel auditor for about 2 days now. I regularly have to leave my phone about 2/3 times in my car for about an hour every day, and every time i check on cpu stats if it got into deep sleep and every time it's listed in unused frequencies :/

I released the working build yesterday and I stated that deep sleep is working on it.

 

[tatomoreno]

here the titanium works well for me, no problem, the big question is not restart after restore, the phone is unable to receive any voice calls, only sounds of notifications that do not appear. too strange.

 

[EvilDragon17]

Quick bug report:
On the latest version (May 22nd), the game Kingdom Hearts: Union Cross doesn't work anymore.
It shuts down immediately before showing any graphic (it rotates the screen though).

Flashing back to the version from May 17th makes the game work again.

I doubt that's the only game which is affected, which is why I mention it.
You mentioned you switched to a new kernel... is the GPU working properly? It could very well be the game doesn't start because 3D is not working properly.
And I know 3D drivers are often a pain in the ass - and they depend on the kernel version, etc.

 

[szybki_ben]

here the titanium works well for me, no problem, the big question is not restart after restore, the phone is unable to receive any voice calls, only sounds of notifications that do not appear. too strange.

How have to go into the phone app in settings and set it as "phone app". Had the same problem earlier and it solved it

 

[The Marionette]

Quick bug report:
On the latest version (May 22nd), the game Kingdom Hearts: Union Cross doesn't work anymore.
It shuts down immediately before showing any graphic (it rotates the screen though).

Flashing back to the version from May 17th makes the game work again.

I doubt that's the only game which is affected, which is why I mention it.
You mentioned you switched to a new kernel... is the GPU working properly? It could very well be the game doesn't start because 3D is not working properly.
And I know 3D drivers are often a pain in the ass - and they depend on the kernel version, etc.

Other games including 3d benchmarks work.
I will try to debug it but it will take time to go through 2000 commits to find out why that one game won't start.

 

[TheMellowOne]

Quick bug report:
On the latest version (May 22nd), the game Kingdom Hearts: Union Cross doesn't work anymore.
It shuts down immediately before showing any graphic (it rotates the screen though).

Flashing back to the version from May 17th makes the game work again.

I doubt that's the only game which is affected, which is why I mention it.
You mentioned you switched to a new kernel... is the GPU working properly? It could very well be the game doesn't start because 3D is not working properly.
And I know 3D drivers are often a pain in the ass - and they depend on the kernel version, etc.

Perhaps change gpu render to skia? in dev options.

 

[The Marionette]

Perhaps change gpu render to skia? in dev options.

It doesn't make a difference ( tested it myself ) .

 

[EvilDragon17]

Is there a way to see a log output so we know why it crashes?

 

[The Marionette]

Is there a way to see a log output so we know why it crashes?

You can easily take a log if you're that curious.

 

[yanniclord]

Anyone else experiencing issues with the ROM's Battery Counter? I have tried reflashing (not dirty, clean, even with /data/ partition wipe) it countless of times, but the issue still persists. The deepSleep issue was resolved, I now have much more Power left in my Phone throughout the day than before, however, there is a big catch. Let's say that my Phone drained from 100% down to 65% over the course of 6 hours. Not bad and about the usual what I had before on 7.1.1. However, if I now reboot my Phone and come back in, it suddenly says I only have like 30% Power left. What? If I now reboot into my Recovery, the Power indicator is correct and still shows about 60%~ is left. This makes the Phone kind of unreliable in terms of usage, because I have for about 3 hours now had my Phone on 0% Power Indicator in the ROM (yes, 0%, and it doesn't shut down), and then sometimes I have like 20% left (as the ROM tells me), but then the Phone suddenly shuts down because it actually has 0% Power left in reality. What could cause this?

EDIT: If you need any logcat files @The Marionette then just tell me

 

[The Marionette]

Anyone else experiencing issues with the ROM's Battery Counter?
.
.
.

EDIT: If you need any logcat files @The Marionette then just tell me

If the battery percentage is making leaps after a reboot, your battery might be dying.

The same happenned to me 2 months ago, 81% would suddenly drop to 24% after a reboot.

Try going to pure stock for a day or two to be sure.

 

[yanniclord]

Yeah like I said, this issue has been existing ever since the update to Android 8 and this ROM, 7.1.1 was totally fine and my Battery lasted for days in deepSleep, so I have a hard time believing that. And if it would only be jumping down then I'd maybe understand, but it also jumps up so that it says "20% left" or so, and then the Phone turns off the next second. However, when in TWRP, the Power Indicator is always correct, it's only in the ROM/Android OS itself, not in the Recovery or Bootloader Power Indicator (when charging the Phone).

 

[EvilDragon17]

Ahwell, since the upgrade today, Kingdom Hearts only shows a grey screen when I start it on the the 20180517 release.. They broke it completely. I'll update 20180523 now.

 

[The Marionette]

Yeah like I said, this issue has been existing ever since the update to Android 8 and this ROM, 7.1.1 was totally fine and my Battery lasted for days in deepSleep, so I have a hard time believing that. And if it would only be jumping down then I'd maybe understand, but it also jumps up so that it says "20% left" or so, and then the Phone turns off the next second. However, when in TWRP, the Power Indicator is always correct, it's only in the ROM/Android OS itself, not in the Recovery or Bootloader Power Indicator (when charging the Phone).

I honestly don't know. Battery stats are fine for me.
You can eventually try flashing a rom which works for you and then clean flash AEX.