yashsingh1/xdaforums huggingface dataset:
[Treble-Enabled Device Development A/AB ROMS] Technical:
Hmmm... They're repositories seem to be buried. It's not easy to find them in GitHub. These are not good news.

I'll try PixelDust again, but probably will move into Beast. I do not like Bootleggers... :p
[Treble-Enabled Device Development A/AB ROMS] $@NTO$:
Hi! Which vendor to use for Havoc 2.3?
[Treble-Enabled Device Development A/AB ROMS] peppet:
Oreo vendor

Inviato dal mio Moto Z2 Play utilizzando Tapatalk
[Treble-Enabled Device Development A/AB ROMS] Technical:
The one your phone/manufacturer released. I use Pie version of Lineage16 vendor.
[Treble-Enabled Device Development A/AB ROMS] sebx_g1:
Moto Z play, Oreo vendor - havoc is good. Interface whistles are amazing but heavy for my Moto a bit. Waiting still for Pie working vendor with more modern kernel. Any why good job!!

Wysłane z mojego XT1635-02 przy użyciu Tapatalka
[Treble-Enabled Device Development A/AB ROMS] Technical:
Just to let you know that PixelDust and Beast have compilations issues in my system.

Havoc has unique customizations like Slim Recents, the glassy UI (besides dark and amoled black), battery life is amazing... So, why move? :D
[Treble-Enabled Device Development A/AB ROMS] Tarlafic:
On my Z17S the bluetooth app keep stopping, but was normal on 2.0
[Treble-Enabled Device Development A/AB ROMS] unix2208:
hi Guys,

I can install the rom super well and Magisk too, but with Gapps I get the error code: 64. Does anyone have an idea?
[Treble-Enabled Device Development A/AB ROMS] F1nes:
I can't finish set fingerprint lock. On Havoc 2.3 and 2.4. Mi A2 Lite device. What to do? Help
[Treble-Enabled Device Development A/AB ROMS] Technical:
See #3 on post #2. Maybe it helps.
[Treble-Enabled Device Development A/AB ROMS] mrram:
Download MagicGapps and Gapps. Put in internal storage. Flash using TWRP...
[Treble-Enabled Device Development A/AB ROMS] sebx_g1:
No problems with newest build with gapps micro . This rom is complete solution for me , waiting just for fixed pie vendor ( now I am on Oreo - moto z play) .
[Treble-Enabled Device Development A/AB ROMS] modest.young:
I'm so sad because I have to say that Havoc 2.3 didn't boot on Honor 9.

Thank you for your work!

Have a nice weekend.
[Treble-Enabled Device Development A/AB ROMS] Technical:
What a pity!

Indeed, it's Havoc v2.4 and the latest security updates from April are already there.

Are you starting from scratch? I mean, without Magisk, dirty flashes, etc.?

I need to check the logs, but I know that some patches are not being applied to some brands and then, they could fail.

Did you boot any other Pie GSI ROM in your phone?
[Treble-Enabled Device Development A/AB ROMS] unix2208:
Thanks for your help, but I've already tried everything, like system-partion magicApps. I have a mimix 3 and it just does not work. Maybe there will be another version with Gapps!

it just does not work for me and i love Havoc, unfortunately there is no version of HAVOC for the mix3
[Treble-Enabled Device Development A/AB ROMS] Xyam:
I got the error 64 too, even I cannot install magisk. Which version of Magisk do you use?

---------- Post added at 03:31 PM ---------- Previous post was at 03:31 PM ----------

Same here, using mix 3, no luck.
[Treble-Enabled Device Development A/AB ROMS] F1nes:
I can't set fingerprint pattern. Xiaomi Mi A2 Lite, please help
[Treble-Enabled Device Development A/AB ROMS] Txatxiquesi:
Do you install the gapps?.
[Treble-Enabled Device Development A/AB ROMS] F1nes:
Yes, I do. Pico arm64 Android 9. When I'm touching fingerprint scanner last time while setting up it says that it cannot be done :/
[Treble-Enabled Device Development A/AB ROMS] Technical:
As far I know, fingerprint is a matter of vendor. I did not have on Lineage15 (at least earlier versions), but I have on Lineage16 for my phone.

Treble project depends a lot on patches and it can fail miserably on some phones (especially with semi-Treble support).
[Treble-Enabled Device Development A/AB ROMS] F1nes:
So, what shoud I do? Fingerprint was working on Havoc 2.0
[Treble-Enabled Device Development A/AB ROMS] Txatxiquesi:
What full rom you flash before havoc?.

Also i think you need to flash forze desencrypt & selinux.
[Treble-Enabled Device Development A/AB ROMS] F1nes:
Before Havoc i had stock rom 10.0.3.0. I coudn't boot in havoc after flashing stock oreo
[Treble-Enabled Device Development A/AB ROMS] Txatxiquesi:
But now, you start from the begining, a clean stock rom flash?

---------- Post added at 10:52 PM ---------- Previous post was at 10:51 PM ----------

But now, you start from the begining, a clean stock rom flash?
[Treble-Enabled Device Development A/AB ROMS] unix2208:
Hello,

is not it possible to create a gsi incl. Gapps?

Unfortunately I can not get the Gapps installed. As I have already described here, I always get Error 64 and at least it is not possible to install Gapps on the mix3
[Treble-Enabled Device Development A/AB ROMS] Txatxiquesi:
I think Nfound build have Gapps included. https://androidfilehost.com/?w=files&flid=282119
[Treble-Enabled Device Development A/AB ROMS] Technical:
Technically it's possible. It depends on hard disk space and time for compiling.

Any clue of what error 64 means on Gapps installation?
[Treble-Enabled Device Development A/AB ROMS] ChonDoit:
What about with ADB sideload?

If I don't bad remember if due missed unzip binary on

system/bin or xbin

Or didn't inlcuded on TWRP over sbin
[Treble-Enabled Device Development A/AB ROMS] Technical:
I had this error today in a friend's phone. It's an old a-only phone, but I forgot to download the correct gapps, arm and not arm64. Is it your case?
[Treble-Enabled Device Development A/AB ROMS] Xyam:
hey i figured out how to install GAPPS in our MIX3

1. Firstly download and install the unofficial TWRP from Xiaomi Forum China:

http://www.miui.com/thread-19749636-1-1.html

It is in Chinese, in case you cannot read Chinese just grab it from:

https://pan.baidu.com/s/1WyxLnpG3kMye9ss_nJRH3g

password: 16sq

2. Flash Xiaomi EU / Global

3. Factory reset and format data

4. Reboot to TWRP, make sure SYSTEM and VENDOR are mounted

5. Install HAVOC GSI

6. Check again if SYSTEM and VENDOR are mounted

7. Resize SYSTEM partition size

8. Root the device under ADVANCED -> Install Root

9. Reboot to TWRP again

10. Check again if SYSTEM and VENDOR are mounted

11. Finally install GAPPS and reboot to system

Your device is now rooted with Magisk v19.0 although you cannot see the Magisk Manager in the app drawer, just install the manager apk and you will get full root control.
[Treble-Enabled Device Development A/AB ROMS] Xyam:
By the way is auto brightness working in this ROM? I cannot find the setting.
[Treble-Enabled Device Development A/AB ROMS] wenjie1234:
Cannot boot on Galaxy Note 9 N960F/DS exynos version. I tried everything, flashing vendor, boot, etc non of it work. i tried another GSI rom (BlissRoms) and manage to boot.... Am I missing something? Here is what I do : I flash img to system, reboot, and resize system. Then flash OpenGapps (nano). Then reboot. It stuck at the booting screen which is an animated "android".
[Treble-Enabled Device Development A/AB ROMS] unix2208:
thanks Xyam,

a really good job, could you also see how it behaves with the newer versions and explain it shortly afterwards?
[Treble-Enabled Device Development A/AB ROMS] Xyam:
I cannot compare with old version as the latest version is the only one that I tried. However I can say that HAVOC is the best compared with other gsi Roms that I tried so far. Everything is smooth and the battery life is good. Still evaluating the RAM performance (some people said there was memory leak).

By the way , some apps used to work well in MIUI and OOS do not work well in HAVOC (lagging), not sure about the root cause.
[Treble-Enabled Device Development A/AB ROMS] Technical:
Display > Adaptive brightness is working.
[Treble-Enabled Device Development A/AB ROMS] Xyam:
I don't have this option ... Also screenshot edit is not working either.
[Treble-Enabled Device Development A/AB ROMS] Technical:
Strange, I have it. I'm on version 20190403 and I will upload a new one soon.

Screenshot edit is not working for me either. I can workaround it with an app.
[Treble-Enabled Device Development A/AB ROMS] Xyam:
Thanks. I am on the same version too, that's why I asked.

Just heard that vendor overlay is required for auto brightness, is that true? by the way what's your device?
[Treble-Enabled Device Development A/AB ROMS] Technical:
I'm not sure about this answer, but I've said some threads here in xda on developing overlays for GSIs.

Moto Z2 Force (nash)
[Treble-Enabled Device Development A/AB ROMS] sebx_g1:
On some phones like mine you need to put manually your overlay file in to vendor/overlay folder... framework-res__auto_generated_rro.apk

You can take it from xda or your vendor rom. File operations make from twrp file editor.

Wysłane z mojego XT1635-02 przy użyciu Tapatalka
[Treble-Enabled Device Development A/AB ROMS] Xyam:
Thanks it works. I took the file from xda.

Just for my reference, how can I get it from my vendor rom?
[Treble-Enabled Device Development A/AB ROMS] sebx_g1:
Just copy that file from : system/overlay to another folder when you have installed your vendor rom alone .
[Treble-Enabled Device Development A/AB ROMS] Xyam:
Ah you're right. I was thinking to decompose vendor.img
[Treble-Enabled Device Development A/AB ROMS] sebx_g1:
Simple solutions are best ;) But I wonder if [MENTION=1011179]Technical[/MENTION] can puf this file into gsi to save users time -- specific overlays for Moto Z Play i have them all taken from vendor . ?
[Treble-Enabled Device Development A/AB ROMS] Technical:
Do you know how to generate a vendor.img from the phone itself? Thanks.

By the way, as Liquid is being supported by king1490, I'll release some other ROM in next days. As usual, only the customization rich ones :p
[Treble-Enabled Device Development A/AB ROMS] mohammadj26:
Can i just ignore "Android System: There's an internal problem with your device. Contact your manufacturer for details"

and Is that fix in v2.4?
[Treble-Enabled Device Development A/AB ROMS] modest.young:
How should I catch logs from phone that got bootlooped right after booting up. It bootlooped right after booting up, I even didn't see bootlogo of Havoc.

Yes I was starting from scratch (now I also tried it with the latest version - 20190407, with same result)

Thanks
[Treble-Enabled Device Development A/AB ROMS] Technical:
Yes. It's just a mismatch into 2 system files. I'm still trying to find a solution. But it has no impact at all on the phone, just an annoyance.
[Treble-Enabled Device Development A/AB ROMS] Technical:
https://www.xda-developers.com/how-to-take-logs-in-android/

https://xdaforums.com/showthread.php?t=2274119&page=87

Which is your phone?

I'm not sure I'll be able to help you, generally, this is a work for the Havoc devs and also the Treble patches.
[Treble-Enabled Device Development A/AB ROMS] Technical:
New compilations today. Maybe we have issues on Xiaomi phones, some patches are bringing issues... If anybody is brave enough to test, I'll be glad to understand what I've done correctly or wrong :o
[Treble-Enabled Device Development A/AB ROMS] Txatxiquesi:
I am about to say it:) , I successfully bot de 04/04 build on mi a2 lite on January stock rom, with encryption disabled & permissive selinux.

I have also the warning of vendor on boot just before entering the ping, for some reason if I install the camara2api magisk module, cámaras does not work, with out it works well.

Also the corner icons on the Notch does not fill very well, I trying to figure out...:confused:
[Treble-Enabled Device Development A/AB ROMS] mohammadj26:
my device is Xiaomi redmi 3 pro

lately i've commented that i'm facing so much issue(such as wifi ,fingerprint, screen pass out by showing mismath vendor error while using phone)

and you said that issues cause of vendor not rom

that time i've installed hacov v2.3 from a backup from another ido device

after that i've installed latest official version with the same vendor and i have no issue(just android system internal issue pop-up in every boot-up)

so i though that's because of restoring a backup

and i go for this 2.4 version

now i'm receiving mismatch vendor pop-up and fingerprint not work most of the time(actually just work in every boot-up)

but no more problem (still)

i hope you guys go for fix these issue cause this rom is awesome

and sorry for not being able to share better things to help, cause i'm a noob user

overall thanks
[Treble-Enabled Device Development A/AB ROMS] Txatxiquesi:
Is there any way to avoid the apps don't ignore the notch?, They just expand and hide the notch.:confused:
[Treble-Enabled Device Development A/AB ROMS] Jeff88malaquias:
:confused: bootloop now
[Treble-Enabled Device Development A/AB ROMS] Technical:
:crying: Which is your phone?
[Treble-Enabled Device Development A/AB ROMS] Xyam:
Thanks for the new compilation. Everything works fine in Mi Mix3 on 0409 build.
[Treble-Enabled Device Development A/AB ROMS] modest.young:
My phone is Honor 9 (STF-L09).

I'll try to catch logs.

Regards.
[Treble-Enabled Device Development A/AB ROMS] gaban05:
Is bluetooth call working on this ROM ?
[Treble-Enabled Device Development A/AB ROMS] vince31fr:
[MENTION=1011179]Technical[/MENTION]: Many thanks for your builds! Your last one (20190409) really works like a charm. The only problem that I still had with previous builds (fingerprint reader randomly deactivated for apps authentication) seems to have vanished. This remains to be confirmed in the long term. I hope you will keep us updated, havoc is really a great rom.

About more specific vendor related problems, I made an overlay for mi8se users with the latest values extracted from latest miui dev (9.3.28), in attachment. The settings for automatic brightness is a bit different, in particular minimum brigthness which is a bit less low.

I also made a magisk module which:

- puts the mi8se overlay in /vendor/overlay

- puts havoc bootanimation in /system/media

- solves the boot warning (This device...) and a problem in phh's rw-system.sh due to incorrect ro.build.fingerprint and ro.vendor.build.fingerprint values

- solves the bluetooth audio incall problem, by umounting the empty directory of /vendor/etc/audio performed in phh's rw-system.sh script

- puts the two libs camera.qcom.so and com.qti.chi.override.so in /system/vendor/lib/hw so that GCam works perfectly (for me, MGC_6.1.021.MI8_V2e.zip), see related topic https://xdaforums.com/mi-8-se/themes/fullyworking-google-camera-xiaomi-mi-8-t3877714

Thanks again for your hard work and long life to havoc!
[Treble-Enabled Device Development A/AB ROMS] Technical:
Really a community work! Thanks for your participation.

How does your Magisk module work? Can it be used in non Xiaomi phones?

Do you know how to correct the phh's script error on fingerprint mismatch while we're compiling the ROM?
[Treble-Enabled Device Development A/AB ROMS] vince31fr:
You're welcome!

The magisk module could be installed on any device I suppose: the mi8se overlay would be activated only for that device. However I only put the havoc bootanimation corresponding to mi8se, with a witdh screen of 1080, so it may be crappy for other screen sizes.

Just look inside the zip: it's very simple. Some things are put in the magisk mirror filesystem (like the overlay, the gcam libs, the bootanimation), some other in the system.prop file to add some extra properties, and some in the service.sh script which is executed at each boot. The magisk xda page is well-documented if you're not familiar with it. For that last one, service.sh, it does 2 things:

- it umounts the empty directory /vendor/etc/audio which is mounted in rw-system.sh at line 315 and prevents incall bluetooth audio to work properly on sirius (this may not be the case for all devices, and does not work in some other GSIs like Bliss).

- it sets ro.build.fingerprint and ro.vendor.build.fingerprint to ro.vendor.build.fingerprint_real which, in the sirius device, is the correct fingerprint. In fact, ro.vendor.build.fingerprint is set in miui to dipper (mi8), and I suspect the system partition of mi8 and mi8se to be the same, so things in /vendor use ro.vendor.build.fingerprint_real (sirius) and things in /system use ro.vendor.build.fingerprint (dipper). That's why rw-system.sh sees dipper instead of sirius, which causes some problems for the mi8se.

The boot warning comes from the fact that ro.build.fingerprint and ro.vendor.build.fingerprint mismatch, and apparently using everywhere the vendor fingerprint (the correct one, with sirius and not dipper) solves the problem.

I think you won't find a global solution to this problem by playing with properties: even if you set ro.build.fingerprint to ro.vendor.build.fingerprint in your havoc build, which can solve the problem for some devices, some other devices like sirius use things like ro.vendor.build.fingerprint_real which are not generic to the best of my knowledge...

Btw, finally the app fingerprint authorization is deactivated at each reboot... but once set again by adding or removing a fingerprint, it does not randomly vanished (still have to be confirmed, I reboot my device too often ;) ).
[Treble-Enabled Device Development A/AB ROMS] Technical:
1. Bootanimation worked for me.

2. Vendor message was not solved (it's there). Probably you'll need to mount A/B system partitions differently from A-only system.

3. Google Camera opens and closes immediately.

4. Can't test Bluetooth but hope it did not mess it :D
[Treble-Enabled Device Development A/AB ROMS] vince31fr:
1. great ;)

2. Vendor message not solved: I think my hack works only for sirius (which is an aonly device) because of the two properties (ro.vendor.build.fingerprint and ro.vendor.build.fingerprint_real) which is a miui feature I think. A more generic implementation would be to set ro.build.fingerprint to ro.vendor.build.fingerprint, and not ro.vendor.build.fingerprint_real as I did. However, I could change my implentation to test first if ***_real exists or not, and setting ro.build.fingerprint to the right value...

3. the libs for gcam are specific to mi8se

4. bluetooth: it may work, or not. I don't know why /system/etc/audio is set to an empty dir in rw-system.sh, hiding the file audio_policy_configuration.xml, but this was the problem for mi8se.

---------- Post added at 02:55 PM ---------- Previous post was at 02:32 PM ----------

I have uploaded a new version of the magisk module, which now:

- sets ro.build.fingerprint and ro.vendor.build.fingerprint to ro.vendor.build.fingerprint_real if it exists as in sirius device

- or sets ro.build.fingerprint to ro.vendor.build.fingerprint if ro.vendor.build.fingerprint_real does not exist.
[Treble-Enabled Device Development A/AB ROMS] Txatxiquesi:
Any ideas why I cant use camara2api with this rom on a mi a2 lite? Camera apps don't open because a fatal error, and gcams crash.
[Treble-Enabled Device Development A/AB ROMS] eremitein:
on daisy with pie vendor gcam not working in any GSIs

solution still not found
[Treble-Enabled Device Development A/AB ROMS] Txatxiquesi:
I was using gcam on official havoc GSI.:confused:
[Treble-Enabled Device Development A/AB ROMS] eremitein:
with pie vendor (10.x.x.x stock)? you sure?
[Treble-Enabled Device Development A/AB ROMS] unix2208:
with my mi mix 3 the system sounds are tinny, music is ok
[Treble-Enabled Device Development A/AB ROMS] Technical:
Open Camera is what is working on GSIs.

You can install ViPER4Android and enhance the sound 10x. It works like a charm in Havoc.
[Treble-Enabled Device Development A/AB ROMS] modest.young:
I'm unable to catch logs, because phone didn't boot successfuly so adb didn't recognizes it.

Regards.
[Treble-Enabled Device Development A/AB ROMS] Txatxiquesi:
I am wondering what i need to do for fix the overlay on mi phone a Mi a2 lite.
[Treble-Enabled Device Development A/AB ROMS] vince31fr:
The first thing to know is wether the existing overlay is really used, or not. If you look at the overlay sources available from phh's github, you can see that the tested property is "ro.vendor.build.fingerprint" with the value "+*iaomi/platina*", which is the codename of mi8 Lite.

As I explained, for mi8se (codename sirius), ro.vendor.build.fingerprint is set to dipper (mi8) instead of sirius, and ro.vendor.build.fingerprint_real is set to sirius. This leads to a big problem: the mi8se overlay is not loaded, as it expects sirius and not dipper.

So take a look in the file /vendor/build.prop and search all lines with the string "fingerprint". If the values differ as it is the case for mi8se, you can try to use my magisk module which solves this issue.

If you really want to modify the mi8 lite overlay, you can download the sources in phh's husson github, and build the overlay with apktool or aapt for instance (not a trivial task). You can also submit some modifications to phh's github so that they will benefit to all mi8 lite users.
[Treble-Enabled Device Development A/AB ROMS] F1nes:
Does the ROM works well on Mi A2 Lite (daisy)? What base could I use to install Havoc?
[Treble-Enabled Device Development A/AB ROMS] Txatxiquesi:
yes ,works well , i use 10.0.0.3.
[Treble-Enabled Device Development A/AB ROMS] F1nes:
I have problem with fingerprint... I can't set my finger in settings? What to do?
[Treble-Enabled Device Development A/AB ROMS] Txatxiquesi:
Do you install permisive selinux & forze decryption?
[Treble-Enabled Device Development A/AB ROMS] F1nes:
Where I can download forze decryption?
[Treble-Enabled Device Development A/AB ROMS] Txatxiquesi:
https://xdaforums.com/mi-a2-lite/how-to/gsi-tweaks-fix-t3899630
[Treble-Enabled Device Development A/AB ROMS] F1nes:
It isn't working... I can' set my fingerprint at all.....
[Treble-Enabled Device Development A/AB ROMS] Txatxiquesi:
What havoc build you are using?, Mine April 03.
[Treble-Enabled Device Development A/AB ROMS] F1nes:
Me too
[Treble-Enabled Device Development A/AB ROMS] Txatxiquesi:
What was the steps you did to flash the rom from the begining?.

I follow this https://xdaforums.com/mi-a2-lite/how-to/guide-functional-twrp-magisk-pie-gsi-t3900119/page3
[Treble-Enabled Device Development A/AB ROMS] F1nes:
1. I flashed stock 10.0.3.0 Pie stock rom

2. Reboot to bootloader

3.Open commander in PC and type "fastboot flash system system.img"

4.I open twrp and flash opengapps

5. I reboot to Havoc without problems

6. Than I flashed permissive v2 and disforsenc_daisy__zero and Magisk of course

I think that's all
[Treble-Enabled Device Development A/AB ROMS] Txatxiquesi:
Follow the guide.
[Treble-Enabled Device Development A/AB ROMS] F1nes:
The same think man... Again I can't set my finger in settings
[Treble-Enabled Device Development A/AB ROMS] eremitein:
on our phone if you have goodix scaner and using pie vendor fp don't be saved by default
[Treble-Enabled Device Development A/AB ROMS] Technical:
New builds are out and apply all the available patches until yesterday.
[Treble-Enabled Device Development A/AB ROMS] Txatxiquesi:
How to know what module i have?, because mine is working.
[Treble-Enabled Device Development A/AB ROMS] eremitein:
if your working then you have "fpc" :laugh:

install any hardware info app or just look in console with commands:

su

getevent
[Treble-Enabled Device Development A/AB ROMS] Mikfyr69:
Can anyone help me ?

I used now havoc v.2.1 build date 13-01-2019 Official.

why every time I upgrade to version 2.2 the official banking application can't be used, to be able to use it I have to go down to the current version again. it seems that the developer of the banking application has detected a device change. Can anyone know the cause of the problem?
[Treble-Enabled Device Development A/AB ROMS] Txatxiquesi:
To do a update , can i just flash the new image via twrp and wipe cache & dalvik?.

Any problem with the magisk modules?.
[Treble-Enabled Device Development A/AB ROMS] Botandroid:
Don't work for me. I have Umidigi one pro version 64arm a. I install and don't boot. Thanks
[Treble-Enabled Device Development A/AB ROMS] conanedogawa1011:
ARM32-A

Is there any build for arm32? We really need it please