[ROM] DivestOS 20.0 for mata

[SkewedZeppelin]

I see references to "firmware is included" (your comment) and "firmware-empty" and "A/B devices only without firmware enabled".

mata has firmware included, it is installed when you update or sideload
firmware empty is called that because that repo doesn't actually contain the proprietary firmware

What is this "firmware" in relation to the boot, system, vendor and other images? Is the firmware related to AVB?

this is modem and bootloader and trustzone: https://gitlab.com/divested-mobile/firmware-empty/-/blob/master/mata/AndroidBoardVendor.mk

Is the PH-1 an AVB device? (does it require working with `avb_custom_key` in fastboot)

mata is not an avb/vb2.0 device, only vb1.0 as per the line on the downloads page.
only avb devices get avb keys

Aside: There is mention of "full" and "yes, ue" in the firmware-empty status. What do "ue" and "full" mean?

full means all firmware partitions and ue means update engine.

 

[chaseadam]

This is a known issue with the DivestOS recovery for mata. I have no idea why it happens, spent hours trying to figure it out.

So, looks like cannot perform the following steps without a working recovery.:

* A/B devices only without firmware enabled: $ adb sideload copy-partitions-device.zip
* Choose apply update, then via sideload and $ adb sideload divested-version-date-dos-device.zip

I am able to boot into DivestOS because fastboot included a boot, system and vendor, but I noticed there are references to "keys" in the care_map.pb file in divested-version-date-dos-device.zip.

Is it safe to lock bootloader without performing the recovery steps?
Is it safe to lock the bootloader without a "working" recovery?

 

[SkewedZeppelin]

* A/B devices only without firmware enabled: $ adb sideload copy-partitions-device.zip

A/B is not AVB, you don't need this step because firmware is included.

* Choose apply update, then via sideload and $ adb sideload divested-version-date-dos-device.zip

I am able to boot into DivestOS because fastboot included a boot, system and vendor, but I noticed there are references to "keys" in the care_map.pb file in divested-version-date-dos-device.zip.

because the recovery is broken you can install the OTA via the Updater app, this will ensure both slots have a copy.

Is it safe to lock bootloader without performing the recovery steps?

After you install via updater yes.

Is it safe to lock the bootloader without a "working" recovery?

As long as you keep allow oem unlocking checked in developer options, yes.
Note you can disable developer options after you verify it is checked.

 

[chaseadam]

Reporting back success with locking the bootloader with read out of the cryptographic ID of of the image after performing the OTA update. Thanks for the guidance @SkewedZeppelin!

 

[SkewedZeppelin]

Reporting back success with locking the bootloader with read out of the cryptographic ID of of the image after performing the OTA update. Thanks for the guidance @SkewedZeppelin!

You can compare it against: https://divestos.org/index.php?page=verified_boot_hashes
Device: mata SHA-256: 9C5FA345C738AD03 5922827FC60422C0 89C2C0AAEA7AF8B6 5B8E3124D614C10E

 

[hedgecore44]

Is there a way to upgrade in place to v19 without losing data?

 

[SkewedZeppelin]

Is there a way to upgrade in place to v19 without losing data?

Of course!
DivestOS supports in-place upgrades whenever possible.

Due to the recovery issue mata has, a coming 18.1 update will allow major version updates within the Updater app straight to 19.1:

DivestOS-Build/Scripts/LineageOS-18.1/Patch.sh at master · Divested-Mobile/DivestOS-Build

Everything needed to build DivestOS, a more private and more secure aftermarket mobile operating system. - Divested-Mobile/DivestOS-Build

github.com

A backup is as always recommeded, but I've already tested it working nicely.

 

[hedgecore44]

Of course!
DivestOS supports in-place upgrades whenever possible.

Due to the recovery issue mata has, a coming 18.1 update will allow major version updates within the Updater app straight to 19.1:

DivestOS-Build/Scripts/LineageOS-18.1/Patch.sh at master · Divested-Mobile/DivestOS-Build

Everything needed to build DivestOS, a more private and more secure aftermarket mobile operating system. - Divested-Mobile/DivestOS-Build

github.com

A backup is as always recommeded, but I've already tested it working nicely.

Woah awesome! Thank ya

 

[foueddyf]

I just installed 19.1 (19-20220515) (fresh install).

Using Gesture Navigation, swiping up from bottom of the screen doesn't do anything.
Same thing in 2-button navigation.
And in 3-button navigation, there's only 1 button, the back button. No home button or recent button.

The only navigation gesture that works is the Back gesture.

I can't swipe down from the status bar either, so impossible to access notifications.

Not sure if I'm doing something wrong here

After using the updater for the first time, I thought there was an update, but it was actually the same build that was already installed.
Went and upgraded anyway, rebooted, all is fine now
EDIT: Looks like a simple reboot fixes the issue.

 

[SkewedZeppelin]

I just installed 19.1 (19-20220515) (fresh install).

Using Gesture Navigation, swiping up from bottom of the screen doesn't do anything.
Same thing in 2-button navigation.
And in 3-button navigation, there's only 1 button, the back button. No home button or recent button.

The only navigation gesture that works is the Back gesture.

I can't swipe down from the status bar either, so impossible to access notifications.

Not sure if I'm doing something wrong here

After using the updater for the first time, I thought there was an update, but it was actually the same build that was already installed.
Went and upgraded anyway, rebooted, all is fine now
EDIT: Looks like a simple reboot fixes the issue.

If you only installed it via fastboot it is possible your firmware was outdated. Firmware is only included in the OTA, which is why sidleoading again is recommended, but mata recovery is half broken and can't sideload, so installing via the Updater app does the same.

So either firmware related, or the reboot fixed it.

 

[chrisrg]

I've installed DivestOS again over the 032 stock OOS and upgraded ota to 19.1
Once again I'm curious to know whether I should expect wifi calling to work, or is it purposely not available?

 

[SkewedZeppelin]

I've installed DivestOS again over the 032 stock OOS and upgraded ota to 19.1
Once again I'm curious to know whether I should expect wifi calling to work, or is it purposely not available?

VoLTE is and I've personally tested it working.
VoWiFi is currently removed and not supported.

Scripts/Common/Deblob.sh · master · DivestOS Mobile / DivestOS-Build · GitLab

Everything needed to build DivestOS, a more private and more secure aftermarket mobile operating system. https://divestos.org/index.php?page=build

gitlab.com

I ask every few months if users want VoWiFi back and they say no: https://forum.f-droid.org/t/divesto...-with-enhanced-privacy-and-security/10105/565

 

[chrisrg]

VoLTE is and I've personally tested it working.
VoWiFi is currently removed and not supported.

Scripts/Common/Deblob.sh · master · DivestOS Mobile / DivestOS-Build · GitLab

Everything needed to build DivestOS, a more private and more secure aftermarket mobile operating system. https://divestos.org/index.php?page=build

gitlab.com

I ask every few months if users want VoWiFi back and they say no: https://forum.f-droid.org/t/divesto...-with-enhanced-privacy-and-security/10105/565

Ah, OK, thanks for the info and link to the forum. I'll go and have a look.

Thank you for keeping mata alive and kicking with a great OS and relock bootloader capability.

 

[foueddyf]

If you only installed it via fastboot it is possible your firmware was outdated. Firmware is only included in the OTA, which is why sidleoading again is recommended, but mata recovery is half broken and can't sideload, so installing via the Updater app does the same.

So either firmware related, or the reboot fixed it.

Yes I used your fastboot release flashed over 032.
I relocked the phone and all is great now

There's 1 bug I've noticed and I'm not sure if its Android 12 related or DivestOS related:
Certain apps have an "app switcher" privacy option where the preview of the app when switching apps is blank.
Somehow in this ROM, the app preview thumbnail is still fully displayed in the app switcher. It worked fine in Android 11, although I was on a different ROM.

 

[SkewedZeppelin]

There's 1 bug I've noticed and I'm not sure if its Android 12 related or DivestOS related:
Certain apps have an "app switcher" privacy option where the preview of the app when switching apps is blank.
Somehow in this ROM, the app preview thumbnail is still fully displayed in the app switcher. It worked fine in Android 11, although I was on a different ROM.

Screen security does work, but when you immediately open switcher it continutes to show a real time preview of apps now. You can observe this effect with the camera app.
Once you switch to another app or go home and open the switcher again you'll see no preview for such apps.

 

[foueddyf]

Screen security does work, but when you immediately open switcher it continutes to show a real time preview of apps now. You can observe this effect with the camera app.
Once you switch to another app or go home and open the switcher again you'll see no preview for such apps.

You're right. Didn't noticed the new behavior, thanks

 

[TempAccount10001]

@SkewedZeppelin

Hope you and your loved ones are safe and healthy.

I have a question regarding DRM on vayu, sorry for asking on a different device thread.

I'm have issues with video playback on Udemy (not working). I'm using the app to offline download courses.

Could you please add google DRM please.
If possible a option to enable it.
I would love to use a hardened device as a daily driver.

Regards,
I

 

[SkewedZeppelin]

Could you please add google DRM please.

Absolutely not.

 

[TempAccount10001]

Absolutely not.

Understandable. Thanks for the reply.

 

[TempAccount10001]

@SkewedZeppelin

Could you please update vayu to 19.1.

Official lineage 19.1 scheduled for next friday