yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] Miustone:
I don't wanted to ask, but I'm sure many will appreciate that including Me! I switched some days ago from a Pixel 2 XL to a Mi Mix 2 which is just A-Only and has a lack of community Vendor Support. I created a Vendor Installer myself using the Omni Kernel for Chiron with EAS and Vendor which works flawless with the most GSIs. I just had strange issues after playing with the Bliss UI Options which caused a bricked OS for Me. The Devices shuts down after a Black unresponsive Screen and if it boots up again does it directly power off after the Vendor Missmatch Message. I don't had this Issue with other GSIs so is this maybe a Bliss GSI Bug which does also affect other Devices!?

Thanks for Your Support btw! :highfive:
[Treble-Enabled Device Development A/AB ROMS] rafik25:
Bah.....without gapps its not a good idea......i have issues with gsi roms without gapps impossible to install it with perseus device
[Treble-Enabled Device Development A/AB ROMS] Shobit Joura:
Plz fix or remove the awful animation of getting qs tiles white and again accent color upon sliding statub bar down
[Treble-Enabled Device Development A/AB ROMS] CarloBello:
Mi Mix 3, rom AB+gapps (last 11.8), last Magisk Canary updated yesterday causes random reboot, and no wake up display on incoming call
[Treble-Enabled Device Development A/AB ROMS] GOONER13:
Anyone else having difficulty with substratum or have I missed something important? Having a lot of brainfarts these days.
[Treble-Enabled Device Development A/AB ROMS] KevMetal:
everyone with magisk stop using beta and new builds ... in my experience ..magisk 17.2 works without any bugs in all pie treble gsi's ..while newer builds have different bugs ..like 18+ on more than one of my devices loses root or other bugs ..
[Treble-Enabled Device Development A/AB ROMS] royalcrown01:
Bootloop on my honor 7a AUM-L29
[Treble-Enabled Device Development A/AB ROMS] pacman00700:
when i try to flash through the boot loader i get this message FAILED (remote: 'No such partition.').

i have an essential ph-1 which has a/b partitions.

what am i doing wrong?
[Treble-Enabled Device Development A/AB ROMS] sixohtew:
i lent my brother my ph-1 so im not 100% positive but i think you may need a patched boot.img

but for the error youre getting is fixed with this code

fastboot flash system_a system.img

fastboot flash system_b system.img
[Treble-Enabled Device Development A/AB ROMS] pacman00700:
Thank you so much!

The commands below worked

fastboot flash system_a system.img

fastboot flash system_b system.img

I guess i still need a patched boot image. So what month of patched boot image? How do i get that?
[Treble-Enabled Device Development A/AB ROMS] hamzasr:
Are you using the latest platform tools for adb and fastboot execution. Because latest platform tool doesn't require a slot suffix to flash any image.
[Treble-Enabled Device Development A/AB ROMS] CarloBello:
How can i install by twrp pico gapps on bliss last build stock? I receive always error code: 64 (i try all possibilities to mount system, etc...)
[Treble-Enabled Device Development A/AB ROMS] Technical:
I got this error in the past because I've downloaded a different (wrong) version of Gapps architecture: arm x arm64.
[Treble-Enabled Device Development A/AB ROMS] CarloBello:
I'm sure that is the right version, it is also the same file that i have downloaded and works in other GSI on my phone.... :(
[Treble-Enabled Device Development A/AB ROMS] sixohtew:
Can you pull a logcat? Just start up fresh and recreate the issue while logcat is running. Paste log to pastebin so the thread doesn't get pushed down like 40 inches lol
[Treble-Enabled Device Development A/AB ROMS] sixohtew:
The full substratum commits are still open in our Gerrit sever, once those are merged, I'll post a new build
[Treble-Enabled Device Development A/AB ROMS] sixohtew:
Um...not sure what you mean..when you flash this GSI, you have the option to change the qs tiles to different animations, however these are not enabled by default, so you must've gone into the settings and changed it..and I definitely don't know what you mean when you say "qs tiles white and again accent color upon sliding status bar down"

If you're talking about theming the qs tiles, again that's not enabled by default. My recommendation is you start over, wipe data, and begin fresh. That way you won't mess with things you don't like...many people what to theme their devices, so that's not going anywhere. And same goes for qs tile animation..you don't have to use these features if you don't like them, but don't come to the thread (with nothing proving you have an error, which usually means it's user error) and say "Plz fix or remove the awful animation of getting qs and so on and so on"

Number 1. That's incredibly rude to us who work hard every day to give you something different but still normailzed in AOSP form. And how can I "fix" something when the only thing I have to go off of is your rude statement, which didn't even make sense..in the OP there is all the info you need to file a logcat. But again this seems like you were messing around with the blissify settings and just touched every button you could without realizing what you were doing. If you do have a bug or error, I need a logcat. If you can't get me a logcat and still tell me it's a rom/gsi issue, I will be forced to disregard your posts as user error. Anything after that that is disrespectful to me or my teammates, you will be blocked from this thread. Now please tell me what your problem is, grab a logcat, take a screenshot or use another phone to take a screenshot, and if I see I can help you out, I will. But honestly I think you should start over, that way when you change something, you can change it back if you don't like it.

I'm going to have to make a post about being rude in my threads. This has got to stop
[Treble-Enabled Device Development A/AB ROMS] sixohtew:
What's the error? I used opengapps arm64 Pico and it works just fine. The reason I took the gapps out is well number 1. Any custom ROM that has Gapps built in got/or will get a cease and desist letter from Google. So it's always good to make sure we don't have to pay a grip of money like CyanogenMod did. I will continue, however, to make builds with and without Gapps, you just must be patient because each build takes roughly 1 hour..so thats 4 hours total, as long as my testing shows no noticable bugs
[Treble-Enabled Device Development A/AB ROMS] GOONER13:
I'm going to have to make a post about being rude in my threads. This has got to stop[/QUOTE]

The vast majority of us are very grateful of the hard work that you guys put in for us.

For us I say 'Thank you'.
[Treble-Enabled Device Development A/AB ROMS] Germano1980:
[MENTION=4745578]sixohtew[/MENTION], I tried installing your rom by fastboot and it did not work (bootloop). Then I tried to install directly through TWRP, clearing the system, cache, dalvik and internal memory and also went into bootloop. Then I tried to install over another GSI (DotOs, from Nfound) and started, but then the screen turned black and nothing happened. My device is a Xiaomi Mi Max 3 (Aonly). Can you help me?
[Treble-Enabled Device Development A/AB ROMS] sixohtew:
First, I would say get the factory images, or go back to the latest stock ROM for your device. Once it's setup, go back into twrp and wipe everything but internal storage. NOW here's what you gotta remember, once you wipe system (necessary to start fresh with the GSI) reboot to recovery from within twrp. It will say there is no OS installed, ignore this and just reboot to recovery. Once that boots back into twrp, flash GSI a-only.img to the system partition. Once done, AGAIN reboot to recovery. Once again you will be told there is no OS installed. This is normal because twrp thinks that since you wiped system partition, nothing but a full fledged ROM can fix, this is wrong because GSIs are only the system partition. Once twrp loads back up, go ahead and reboot system. You shouldn't have the no OS error this time and you should be able to boot into the ROM. If not and you still have issues, try flashing the stock ROM that came with your device, and then wipe cache and dalvik cache, BUT DONT WIPE SYSTEM..that's what caused your first error when it bootlooped. follow these instructions and let me know how it works. If you're still having troubles, I'll send you to our telegram channel so either Jon aren or Jack can maybe give you a fix. Hope this helps
[Treble-Enabled Device Development A/AB ROMS] Shobit Joura:
I understand , that i posted with less information , but in telegram grp i even posted the animation video hich is really annoying (i am not trying to offend or disrespect anyones work ,

So i am sorry about that , but still the animation control is about the qs tiles behaviour on tapping on that, but i am discussing about the qs tiles turning white and back to accent color upon drawing status bar ,

For reference i even shared video in telegram group

Link is. https://t.me/Team_Bliss_Community/22404

And i can confidm that this isnt user error .
[Treble-Enabled Device Development A/AB ROMS] Germano1980:
Got it, I'll try it later and let you know.,
[Treble-Enabled Device Development A/AB ROMS] sixohtew:
I haven't seen the telegram post you did...maybe it's in a room I'm not in..I'll look at the video when I get home..but for future reference, please grab a logcat, as it tells us exactly what is going on with the error. I appreciate your apology, but you have to give more info than just a video and explaining what went wrong. Logcats are devs best friends as we can pin point the error and how to fix it moving forward
[Treble-Enabled Device Development A/AB ROMS] Shobit Joura:
As i said it isnt an error , its a type of animation or maybe loading qs tiles i proper dont know but i think the video i shared will explain all what is happening even if i can record logcat and give if u still need that..

But have a look at video as i suppose it will be capable of explaining the situation i am facing
[Treble-Enabled Device Development A/AB ROMS] GGelmi:
11.8 stock no gapps, downloaded file Is *.IMG.xz and when i install pico opengapps TWRP tells me GSI Is Android 7.2.1 not 9

GGelmi

PS: mi 5 3/64
[Treble-Enabled Device Development A/AB ROMS] KevMetal:
I'm no dev but i think what is happening here is that an overlay is literally something lain over something else ..so when your phone is laying your chosen layer over the base layer it does it a little too slowly so you see it happening

this might be cos your phone is too old and slow maybe or perhaps there might be a way to speed up this process to avoid it being seen

im sucking my thumb here but makes sense to me ...like any device loading slowly results in missing icons or incomplete themes

if you wait it corrects itself cos it has time to fully load .....

how good is your device's graphics and processor ?
[Treble-Enabled Device Development A/AB ROMS] conanedogawa1011:
ARM32-A

Can we have arm32 builds please?
[Treble-Enabled Device Development A/AB ROMS] Shobit Joura:
I am having , mi a1 with 625 cpu ,and that's nowhere slow , everything is smooth and that animation happens on clean install too with no theme overlays etc.
[Treble-Enabled Device Development A/AB ROMS] teeterteeter:
I'm running the 11.7 A/B with GAPPS built in on an Umidigi F1. Everything seems to be running well and smooth, with the exception of VoLTE and VoWifi. I'm on T-mobile in the USA and out of the box the phone works for both on the stock software. I dialed *#*#4636#*#* and both appear to be provisioned in the dialer settings. In addition, if I go to Network & Internet > Mobile Network > Advanced the wifi calling option is available and turned on. Even so, if I make a call in airplane mode with wifi turned back on and connected, it fails... and whenever I place a call on LTE, it drops back to H+. Any help or ideas on how to get it working would be greatly appreciated. Thanks.
[Treble-Enabled Device Development A/AB ROMS] CYB3R0ID694:
Hey bro, Any Update?

Is it booted or not?
[Treble-Enabled Device Development A/AB ROMS] ashokmor007:
No did not boot so i got the normal zip of bliss ...

Flazhed tht n enjoyed the rom
[Treble-Enabled Device Development A/AB ROMS] dracinn:
Unable to flash vbmeta on my Pixel XL says partition doesn't exist.
[Treble-Enabled Device Development A/AB ROMS] CYB3R0ID694:
If possible, Ca you share link.. I would like to try it..

It's like i haven't tried any custom ROM from last 1 year after i sold my LeEco Le 2
[Treble-Enabled Device Development A/AB ROMS] sixohtew:
fastboot flash vbmeta_a vbmeta.img
[Treble-Enabled Device Development A/AB ROMS] dracinn:
Still says partition doesn't exist.
[Treble-Enabled Device Development A/AB ROMS] KevMetal:
1. adb reboot bootloader

2. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

3. fastboot flash boot_a boot.img

4. fastboot flash boot_b boot.img

5. fastboot -w flash system_a *NAME OF.img

6. fastboot -w flash system_b *NAME OF.img

if ab partition phone

if a-only you only have one boot and system file to flash ...maybe boot isn't required ..
[Treble-Enabled Device Development A/AB ROMS] vosathanh:
Again, can anyone install gcam on this Rom for Lenovo Z5? This rom run perfectly. But i don't like the open camera. Thanks in advance.
[Treble-Enabled Device Development A/AB ROMS] dracinn:
No matter what I do I can't flash vbmeta because of this error. I'm on the latest Pie firmware for Pixel XL so I should have full Treble support so I don't understand what's going on.

"chronos@localhost ~/Downloads/XDA/Descendant $ fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

Sending 'vbmeta' (4 KB) OKAY [ 0.091s]

Writing 'vbmeta' (bootloader) Flashing active slot "_a"

FAILED (remote: 'partition [vbmeta] doesn't exist')

fastboot: error: Command failed"
[Treble-Enabled Device Development A/AB ROMS] KevMetal:
what about backing up your existing vbmeta ...then try to format or wipe it before flashing it ...

is your bootloader unlocked ?
[Treble-Enabled Device Development A/AB ROMS] dracinn:
How do I do that?
[Treble-Enabled Device Development A/AB ROMS] KevMetal:
i dont have the same phone as you ...

if there is a twrp for your phone just BOOT not flash twrp via fastboot

then on your phone make full backup using twrp

reboot to system & copy full backup to pc

then using

fastboot -w

you can wipe stuff but be careful

fastboot -w vbmeta

*to wipe only the vbmeta

fastboot -w

will wipe data ...in which case will lose stuff if you have no backup

BEFORE trying above try just factory resetting your phone inside system and disabking all security features and removing google account and passord for your screen ...then try flashing the gsi and or vbmeta ...
[Treble-Enabled Device Development A/AB ROMS] dracinn:
For whatever reason it seems as though I don't have a vbmeta partition so I'm going to check out some Pie factory images for Pixel XL.
[Treble-Enabled Device Development A/AB ROMS] KevMetal:
ok but just humor me ...sounds crazy but try to update your adb ...others fixed .." no such partition " on certain phones by doing that ..

here is a reference

https://android.stackexchange.com/questions/164529/unable-to-flash-factory-rom-on-pixel

* and last possibility is to try switching from usb 3 to usb 2 port ...trying different cables etc ..
[Treble-Enabled Device Development A/AB ROMS] buckofive:
First off let me start by saying thanks for being one of the few custom GSI ROMS that has variants with Gapps in the system image. I have a strange Chinese tablet (Alldocube X U1005) and while the most of the hardware is great, it has a crappy Mediatek MT8173 SoC so it is not nearly as developer friendly as any Snapdragon chipset as we will never likely see the hardware sources. There is some kernel source posted, but I'm putting all efforts into working with Treble GSIs. So far Blissroms has the most potential for unlocking the potential of the device.

I've been flashing lots of GSIs in a experimental attempts to get a working daily driver on Pie - when the current vendor firmware & images are based on Oreo. The good news is that the Blissrom GSI Bliss-2019-04-05-arm64-a-gapps.img works surprisingly well. Working from the stock Chinese firmware I was able to flash an unofficial TWRP recovery, full wipe, change format of system from EXT4 to F2FS and then flash the Blissrom GSI. I was a bit skeptical when there were many boot/reboots and no Blissroms boot animation. But it did eventually boot and the very first message I saw was from the Android System:

"There's and internal problem with your device. Contact your manufacturer for details"

Nevertheless I carried on and was super happy to see that wifi works and having the Gapps built in worked perfectly as I was able to walk through the Android Setup wizard and everything worked flawlessly. I was even able to sync my apps/content from a cloud backup and 52 apps & data all installed. #winning

The internal problem appears to be with the camera - as there is no camera app and the QR code scanning app crashes when attempting to access the camera.

As this error message occurs so early in the boot stage, I'm not quite sure how to capture a catlog trace. I suspect that the problem is that the camera has some legacy HAL and that in order for it to work with the new Pie based GSIs that it would take some sort of shim to use the HIDL.

If you anyone is interested in investigating further, I'm happy to help out. I would also point to the xda post (our device is so niche, the entire forum is basically a single thread!)

https://xdaforums.com/general/device-reviews-and-information/10-5-inch-super-amoled-2560-x-1600-t3821327

At the bottom of the OP there are some GitHub repository links for:

android_device_cube_u1005

android_vendor_cube_U1005

These were ported to the LinaroOS 15.1 and might be handy for reference.

Anyways, thanks for making such a kick ass GSI and giving mid-range devices the chance to get a taste of Pie Bliss!
[Treble-Enabled Device Development A/AB ROMS] Poor Grammar:
:confused:...!!!!STOP what your doing right now before you brick your device..If you truly don't know how to backups data, reboot recovery,,etc you are about to screw something up really bad and no one will help you because it will be your own fault for not Reading and understanding what your doing and how it works... YouTube it, Google it read it... It's how I learned to get better... This is a awesome community..:good:
[Treble-Enabled Device Development A/AB ROMS] dracinn:
I know how to use TWRP I already do this regularly I thought he was talking about backing vbmeta.
[Treble-Enabled Device Development A/AB ROMS] FrenchSparda:
Hi guys, i tried to install your ROM on the Chuwi Hi9 Air...but with no luck.after flashing image in TWRP, when i'm rebooting tablet, it enters fastboot mode...

Here's what i did :

1- back to stock (8.0 latest build)

2- flashing TWRP

3- Format data

4-reboot recovery

5- Flashing DisablingEncryption zip file (because encryption, i wasnt able to access nor copying files on internal storage, so i disabled encryption)

6- wiping system, data, cache

7- flashing Blissrom .img file (A partition only, and i choose to install it on System "slot")

8- reboot

9- rebooted in fastboot mode

I tried to flash pico gapps after flashing ROM image at some time, but i got a message error..saying the gapps package is made for 9.0....so it seems flashing image didnt worked ?

Any help would be great. And many many thanks for your work.
[Treble-Enabled Device Development A/AB ROMS] vosathanh:
I think it should be like this to get it booted:

- Flash stock rom

- Falsh twrp

- Wipe dalvik/cache and system (do not format data)

- flash bliss

- reboot

I did successfully on Lenovo Z5
[Treble-Enabled Device Development A/AB ROMS] FrenchSparda:
Still no luck with your method :(

Always rebooting in fastboot mode

Would it be possible to flash system img file with SPF Tools ?
[Treble-Enabled Device Development A/AB ROMS] KevMetal:
i would say put 100% stock rom ..factory reset rom inside OS ..go to fastboot

using fastboot flash phhussan OREO VAnilla with gapps no su ...reboot system

if boots do factory reset inside rom

using fastboot flash phhussan vanilla PIE gsi with gapps no su ..reboot system

factory reset inside phhussan pie ..reboot fastboot

in fastboot flash gsi

DON'T DISABLE ANY ENCRYPTION OR FLASH TWRP OR GAPPS NOTHING

boot system

if successfully boots go in fastboot

flash twrp

boot recovery

flash gapps and su if needed

reboot system

*some phones have problems with custom recoveries and treble gsi

*some phones have problems with custom recovery-gsi-encryption ..which sometimes prevents booting

*some phones only boot if first flashed phhussan vanilla gsi's and later flashed other treble gsi's on top

*lastly my one phone fails to boot first time but if I just do a factory reset ( normal wipe ) ..AFTER installing new gsi in recovery on first failed boot it boots up ...have you tried ?
[Treble-Enabled Device Development A/AB ROMS] FrenchSparda:
i tried, many thanks, but no matter which gsi img i want to flash, i get error message

Invalid sparse file format at header magic

error: write_sparse_skip_chunk: don't care size 311968600 is not a multiple of the block size 4096

error: write_sparse_skip_chunk: don't care size 177754968 is not a multiple of the block size 4096

error: write_sparse_skip_chunk: don't care size 43541336 is not a multiple of the block size 4096

Sending sparse 'system' 1/4 (131068 KB) error: write_sparse_skip_chunk: don't care size 311968600 is not a multiple of the block size 4096

error: write_sparse_skip_chunk: don't care size 311968600 is not a multiple of the block size 4096

OKAY [ 5.410s]

Writing sparse 'system' 1/4 FAILED (remote: sparse chunk size is too big.)

Finished. Total time: 172.440s

then, i'm reflashing stock rom...and tried the previous steps
[Treble-Enabled Device Development A/AB ROMS] KevMetal:
try to download the VERY NEWEST ( LATEST) adb ...my adb/ fastboot had that error and was fixed by updating
[Treble-Enabled Device Development A/AB ROMS] FrenchSparda:
I'm using the latest minimal adb & fastboot package. I'll try to figure it out next week ;)
[Treble-Enabled Device Development A/AB ROMS] teeterteeter:
Update:

I was able to write to system using Root Explorer. I moved both files to system and rebooted with no success, attempting both system>priv-app and then system>app.

I then pulled the entire folder from the stock rom which (in the case of IMS) looks like this:

ImsService > Included ImsService.apk and an oat folder. Oat folder > arm64 folder > ImsService.odex & ImsService.vdex

When I copy the entire ImsService folder with Root Explorer to system>app and set permissions to rwxr-xr-x (and change included apk to rwxr-xr-x) it still doesn't have any effect. When I do the same in the system>priv-app folder, I lose all cell service on reboot.

At this point I've definitely exhausted my knowledge. Any ideas would be greatly appreciated. Thanks

Original Message:

Quick follow up to my Volte issues...

I tried installing the Ims.apk floating around and it doesn't change anything, I'm assuming it may be because it's a Mediatek phone. I downloaded the stock rom and extracted two apks from the system img:

ImsService.apk

WfoService.apk

I attempted to install them through adb to both /system and to /system/priv-app, however it doesn't work as I can't actually get "adb root" to work, so it is still a read only file system. I also enabled terminal in the developer options in an attempt to do it straight from the phone and it also returns that I can't write to system despite successfully granting permissions through Magisk after typing su in terminal.

I'm not terribly knowledgeable in this area, but I would gladly try any suggestions in an attempt to get it working, as volte (and to a lesser extent vowifi) is fairly important for decent service in my area. Thanks for any help.
[Treble-Enabled Device Development A/AB ROMS] Khan ubaid:
Any support for huawei phones???
[Treble-Enabled Device Development A/AB ROMS] Sutan99:
other than double tap to wake is this the top to unlock sweep support (ZenMotion feature)?