[ROM][11] Havoc-OS 4.xx [Vanilla] [a3y17lte] [UNOFFICIAL] [arm64] | [UNOFFICIAL] [GSI] [Exynos7870] [A/B]

[Firngrod]

I am hesitant for two reasons:
1) Copyright/licensing. I've modified the script provided by @TheObcd I think, from the July 2022 release of https://github.com/debie-A320FL/OTA/releases. I haven't checked his licensing terms.
2) Risk of bricking anybody elses device. I just modified parts of an existing larger script. I don't know how it was originally generated. There are parts of the package that I don't understand and therefore haven't touched and cannot vouch for. I don't know if what I did may cause damage on other devices.

Here's what I did: I unpacked the zip, modified the line fetching the Vendor partition number adding a head -1 command between the grep and awk. Then I changed the if on vendor to a while and re-fetched the vendor partition within that loop after delete to clear out any duplicate vendor partitions. Finally, I also modified the sizes declared in the global variables at the top of the script. I can get you a diff later.
I also updated the META-INF script to report my changed target partition sizes. There's also a binary file in there. I don't know what that does.
Then I zipped it up again and ran it on the phone. Seemed to work.

 

[Firngrod]

I guess if we could get him to implement those changes and release them, that would be a boon for his stuff, and then you can reference that.

EDIT: I guess he wouldn't have the sizes your ROM requires.

 

[Firngrod]

Here's the diff of his repartition script (extracted zip file) and mine:

diff -r old/META-INF/com/google/android/updater-script new/META-INF/com/google/android/updater-script
34,35c34,35
<     ui_print("       SYSTEM: 2500MB");
<     ui_print("       VENDOR: 160MB");
---
>     ui_print("       SYSTEM: 2900MB");
>     ui_print("       VENDOR: 440MB");
diff -r old/repartition.sh new/repartition.sh
20,21c20,21
< SYSTEMSIZE=2500
< VENDORSIZE=160
---
> SYSTEMSIZE=2900
> VENDORSIZE=440
36c36
< VENDOR=`$SGDISK --print $DISK | grep VENDOR | awk '{printf $1}'`
---
> VENDOR=`$SGDISK --print $DISK | grep VENDOR | head -1 | awk '{printf $1}'`
53,54c55,56
<     if [ ! -z $VENDOR ]; then  
<         VENDORPART=`$SGDISK --print $DISK | grep VENDOR | awk '{printf $1}'`
---
>     while [ ! -z $VENDOR ]; do  
>         VENDORPART=`$SGDISK --print $DISK | grep VENDOR | head -1 | awk '{printf $1}'`
56c58,59
<     fi
---
>     VENDOR=`$SGDISK --print $DISK | grep VENDOR | head -1 | awk '{printf $1}'`
>     done

I left the vendor partition cleanup in there. I could definitely see other people having flashed repartition scripts repeatedly trying to install something and ending up with a bunch of vendor partitions like I did.

 

[TheObcd]

I am hesitant for two reasons:
1) Copyright/licensing. I've modified the script provided by @TheObcd I think, from the July 2022 release of https://github.com/debie-A320FL/OTA/releases. I haven't checked his licensing terms.

The script has been made by @Astrako and shared intially in his post.

 

[Firngrod]

The script has been made by @Astrako and shared intially in his post.

Thanks! Well that indicates that the changes I have made are safe. He only recommends changing the partition target sizes, so it is apparently safe to do nothing else. The multi-vendor cleanup is safe as well, as far as I can tell. Maybe I should mention the option of updating the official script with that in that thread.

 

[Flominator]

Thread is updated with some more details about instructions, that hopefully pervent people, from falling in the pit messing up their patitions

 

[Firngrod]

I think the best instructions would be to get on the latest treble-capable recovery, then point them towards the thread pointed at by TheObcd with the sizes necessary. That script is safe to use unless the partitions are already messed up.

Now that I have (tried to) set up my phone as I would have it if it were my daily driver, I have noticed two features not working:
1) Adaptive charging - It happily charges beyond the stated max charge.
2) LiveDisplay cannot be turned on. The mode picker will reflect my choice, but settings will remain grayed out, and when I leave and come back, the picker is back to "Off".

 

[Firngrod]

Also, lock screen auto rotation cannot be toggled separately from auto rotation in general. I cannot get it to not auto rotate if auto rotate in general is on.

 

[Flominator]

I look at roms featuresets soon

Also, lock screen auto rotation cannot be toggled separately from auto rotation in general. I cannot get it to not auto rotate if auto rotate in general is on.

auto rotate shoud be fixed now
not loading livedisplay too (dont expect all modes to be working for now, enabled all avaiable ones for now)
about Adaptive charging I have to do some fruther debuggig

 

[Firngrod]

I am still getting auto rotation on lock screen if under "Settings" -> "Display" -> "Rotation" I enable "Auto-rotate screen" but disable "Auto-rotate lockscreen".

LiveDisplay seems halfway fixed. I can select "Color profile", and it seems to take effect, but the "Display mode" and accompanying "Color temperature" settings are still not taking effect. I cannot tell if it's one or the other, or both, which doesn't work.

Furthermore, I have found that enabling "Settings" -> "Configuration Center" -> "Gestures" -> "Power menu" -> "Advanced reboot" and then using advanced reboot to reboot to recovery doesn't work. It just turns off the phone.

Maps in Android Auto has the issue that it thinks I'm sitting solidly in Google's headquarters in California. I don't think that's related to the ROM, but to something in the apps. It's probably caused by running without a SIM card. I will try to verify that at some point.

Another note: The official latest version of TWRP doesn't handle the data partition for this ROM well. It can be used to install the ROM, but booting to recovery after that will cause Data to be inaccessible. Your version works fine, though. I haven't tested Orange Fox yet. Maybe the guide should explicitly recommend using your version.

Finally: Is there a bug tracker I can use rather than forum posts? Also, maybe a guide to how I might build it myself if at all possible, then maybe I can fiddle around with trying to fix some bugs myself?

Thanks again for all your work! It's much appreciated!

 

[Bernique]

I have just installed your ROM and it seems to work fine. Thanks for the job. I just have one issue, it does not recognize my SD card. I know it works fine, because my PC and TWRP can mount it, but not your ROM. Any solution?
Otherwise, do you intend to update it regularly?

 

[Flominator]

I have just installed your ROM and it seems to work fine. Thanks for the job. I just have one issue, it does not recognize my SD card. I know it works fine, because my PC and TWRP can mount it, but not your ROM. Any solution?
Otherwise, do you intend to update it regularly?

wich filesystem is it formatted ? (fat 32, ext4 work fine)

 

[Bernique]

wich filesystem is it formatted ? (fat 32, ext4 work fine)

ExFAT

 

[Firngrod]

ExFAT

I've got my external SD formatted as vFAT, that works.

 

[Bernique]

I've got my external SD formatted as vFAT, that works.

I have finally backed up my card and reformated it through the Samsung instructions, it is now fat32

 

[kwallet]

thank you for your work flominator.

do i understand right if i am running debie's linageos rom with orangefox (r11) right now then i dont have to do anything else just flash the rom normally?

how is this rom compare performance-wise to debie's dec18 lineageos?

is it compatible with a320FL too right?

 

[Flominator]

thank you for your work flominator.

do i understand right if i am running debie's linageos rom with orangefox (r11) right now then i dont have to do anything else just flash the rom normally?

how is this rom compare performance-wise to debie's dec18 lineageos?

is it compatible with a320FL too right?

1. yes with orangefox you can falsh it without issues
2. the performence about is equal
3. it is compatible with a320fl/a320f

 

[kwallet]

1. yes with orangefox you can falsh it without issues
2. the performence about is equal
3. it is compatible with a320fl/a320f

thanks
ill get another a3 and install on it.

 

[yourproblem]

Verry nice! Thank you.
Seems to work. Only the configuration of Power button is missing (for example pushing twice for lamp). Maybe there isn't one in Havoc, i don't know.
Crdroid would be also nice, since it has more option to configure...

 

[kwallet]

Verry nice! Thank you.
Seems to work. Only the configuration of Power button is missing (for example pushing twice for lamp). Maybe there isn't one in Havoc, i don't know.
Crdroid would be also nice, since it has more option to configure...

you can set it up in configuration center / gestures / quick torch