[ROM][11.0][4.9][AOSP][KUGO] Explosive Lobster

[betacrypt]

I have a treble ready 10 boot.img for kugo, but am hesitant to bork my current setup to test the vendor.img from Xperia X. I figured it was the boot.img causing Magisk to not run fully.

I've got a backup XC I can test your A10 boot image on both with treble pie and treble 11 vendor. Not sure how that would go but if we can get A10 gsis working that might be ideal for now. There are many solid A10 roms to choose from.

 

[norabitox]

Hello
Thanks to everyone's efforts

Please tell me the solution for this error
Best regards.

 

[Spaceoid]

Hello
Thanks to everyone's efforts

Please tell me the solution for this error
Best regards.

As far as I understood, in the present build you just have to ignore it (it only appears on boot), and it is already fixed in the next build that is to come.

 

[norabitox]

As far as I understood, in the present build you just have to ignore it (it only appears on boot), and it is already fixed in the next build that is to come.

I see
Thank you very much

 

[MichaBit]

Best regards.

How did you manage the clock like that?
I want this too!

 

[norabitox]

How did you manage the clock like that?
I want this too!

Hello
This is a SimpleDigiClockWidget app

 

[MichaBit]

This is a SimpleDigiClockWidget app

Looks very good, considerably better than the simple org watch.
I had installed Omniclock, that looked similar nice and snooze was working, but the time was always wrong.

 

[norabitox]

[QUOTE = "MichaBit、投稿：84395851、メンバー：6657302"]
Looks very good, considerably better than the simple org watch.
I had installed Omniclock, that looked similar nice and snooze was working, but the time was always wrong.
[/見積もり]

 

[Vx.34]

EDIT: Moved to right thread.

 

[Spaceoid]

Just to give this ROM some remedy - I guess the GPS problems were my own fault. I experienced them on LOS16, AOSP10 and this AOSP11 Treble ROM. I now went back completely to stock 118 and then installed the AOSP10 ROM by vKnecht again, and now my GPS works just fine. So I assume it would work well on THIS ROM here now as well.

 

[maluus]

How often do random reboots occur on daily use?

 

[Spaceoid]

How often do random reboots occur on daily use?

When I used the ROM in its current state, reboots would happen between 0 and 2 times per day.

 

[maluus]

When I used the ROM in its current state, reboots would happen between 0 and 2 times per day.

So there isn't any improvement

 

[Spaceoid]

So there isn't any improvement

I guess the next build is coming soon

 

[maluus]

I guess the next build is coming soon

Well, since the problem is to do with the kernel, unless it's solved on kernel level, I m afraid we won't see any significant improvement by rom updates. Let's hope the opposite.

 

[&(*)]

I've got a backup XC I can test your A10 boot image on both with treble pie and treble 11 vendor. Not sure how that would go but if we can get A10 gsis working that might be ideal for now. There are many solid A10 roms to choose from.

Sorry been busy with another project and haven't had much time; here you go (attached below) . For the vendor.img go here: ( https://androidfilehost.com/?fid=10763459528675571027 )
Make sure you don't mix up the boot supplied here and the boot supplied in the .zip from the link, just use the vendor from it. Remember to use an A/B system.img with whatever 10 variation you choose and you might also need to set SELinux to permissive with: ( https://zackptg5.com/downloads/Kernel-Sepolicy-Patcher.zip )&( https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip ) disable encryption of data as it can cause issues with any type of locking method and verity so it will boot. Test everything and post your results when you get a chance.

 

[betacrypt]

Sorry been busy with another project and haven't had much time; here you go (attached below) . For the vendor.img go here: ( https://androidfilehost.com/?fid=10763459528675571027 )
Make sure you don't mix up the boot supplied here and the boot supplied in the .zip from the link, just use the vendor from it. Remember to use an A/B system.img with whatever 10 variation you choose and you might also need to set SELinux to permissive with: ( https://zackptg5.com/downloads/Kernel-Sepolicy-Patcher.zip )&( https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip ) disable encryption of data as it can cause issues with any type of locking method and verity so it will boot. Test everything and post your results when you get a chance.

Thanks for this - wasn't able to get it going with any treble 10 a/b gsi though.

I used the boot image you provided and the vendor image from the zip, set selinux to permissive by flashing the zip, and it still wouldn't boot to system. Got stuck in a boot loop that just loaded TWRP after each restart. Will try flashing some other combinations to see if anything else might work.

 

[&(*)]

Thanks for this - wasn't able to get it going with any treble 10 a/b gsi though.

I used the boot image you provided and the vendor image from the zip, set selinux to permissive by flashing the zip, and it still wouldn't boot to system. Got stuck in a boot loop that just loaded TWRP after each restart. Will try flashing some other combinations to see if anything else might work.

It could be just an A system - try that first, then if it doesn't boot try it with the 11 vendor from here. It's all I can offer thanks to the build system wanting to inflate libraries at quite the expense. Did you try AndyYan's GSI vndklite (try both a/b & a)?

 

[betacrypt]

It could be just an A system - try that first, then if it doesn't boot try it with the 11 vendor from here. It's all I can offer thanks to the build system wanting to inflate libraries at quite the expense. Did you try AndyYan's GSI vndklite (try both a/b & a)?

Alright no luck so far. I've used the following combinations to no avail:

• Your boot + your vendor + Andy Yan's LineageOS 17.1 A/B
• Your boot + your vendor + Andy Yan's LineageOS 17.1 A only
• Your boot + A11 treble vendor + Andy Yan's LineageOS 17.1 A/B
• Your boot + A11 treble vendor + Andy Yan's LineageOS 17.1 A only
• Your boot + A11 treble vendor + Andy Yan's LineageOS 18.1 vndklite A/B

All of these scenarios result in bootloops. The only combination that got me the furthest is:

• Treble 9 boot + your vendor + Andy Yan's LineageOS 17.1 A only

This one gets me to the OS boot screen but hangs and never loads system successfully.

 

[&(*)]

Alright no luck so far. I've used the following combinations to no avail:

• Your boot + your vendor + Andy Yan's LineageOS 17.1 A/B
• Your boot + your vendor + Andy Yan's LineageOS 17.1 A only
• Your boot + A11 treble vendor + Andy Yan's LineageOS 17.1 A/B
• Your boot + A11 treble vendor + Andy Yan's LineageOS 17.1 A only
• Your boot + A11 treble vendor + Andy Yan's LineageOS 18.1 vndklite A/B

All of these scenarios result in bootloops. The only combination that got me the furthest is:

• Treble 9 boot + your vendor + Andy Yan's LineageOS 17.1 A only

This one gets me to the OS boot screen but hangs and never loads system successfully.

Try without the SELinux patch to permissive; disabling verity wouldn't hurt for the testing either, did you do that as well after disabling SELinux? Do you have the correct OEM libraries installed: ( https://androidfilehost.com/?fid=6006931924117907560 ) ? I will go over the boot again and see if somehow I wrote in the line for treble to be enabled incorrectly (don't believe I did, but will look). If @Sjll would reply to someone we might be able to get an updated tutorial for 10 and 11 treble.