[ROM] DivestOS 20.0 for cheeseburger/dumpling

[SkewedZeppelin]

Does this ROM supports work profile ?

Yes.

Can we use work related apps. Here ?

Apps like Shelter will work fine.
Actual enterprise MDM apps may or may not work.

 

[altromass]

Hi.
I'd like to install Divestos on my OP5 where I already have Lineageos 19.1.
As I'm not starting with the latest stock rom on my phone, as suggested, should I take extra steps before flashing Divestos?
Thankyou.

 

[SkewedZeppelin]

Hi.
I'd like to install Divestos on my OP5 where I already have Lineageos 19.1.
As I'm not starting with the latest stock rom on my phone, as suggested, should I take extra steps before flashing Divestos?
Thankyou.

Since you are already on Lineage, just follow steps 7, 9, 10, and 12: https://divestos.org/index.php?page=bootloader#fastbootUnlocking

 

[altromass]

Great, thankyou

Since you are already on Lineage, just follow steps 7, 9, 10, and 12: https://divestos.org/index.php?page=bootloader#fastbootUnlocking

 

[bonswouar]

Great from the privacy prespective.
Jailed situation from 'people-who-want-to-do-what-they-want' prespective.

Please read this:

Faq - DivestOS Mobile

divestos.org

I really love the idea behind DivestOS, but I can't switch because of those limitations.
Basically the ONE root feature I don't want to loose is being able to manage my charging cycles, with https://github.com/VR-25/acc
IMO that should be pretty much mandatory on any custom OS, specially older phones, batteries don't last forever!

But I totally understand the reasons of not wanting root, and 100% agree on the other principles!
That's unfortunate, I guess I'll stick with LineageOS + microG..

 

[loparaan]

Hello, I just discovered this rom, and sorry, some issues are not clear to me:

1.- When it says that it does not support Google Apps (OpenGAPPS), does it mean that there is no way to install google services, for example to make use of apps from the Google store? I have purchased quite a few applications that I would like to continue using. If not, I don't understand doing so much emphasis on security, when it doesn't let you use the Google app store.

2.- Backup system, what system are you using? If you don't have the possibility to use google services, I understand that I won't be able to restore my phone, or use the contacts I have stored, or use the calendar for events, tasks or birthdays, right?

 

[SkewedZeppelin]

some issues are not clear to me:

1. Apps that have a hard dependency on Play Services will not work. eg. mandatory Safetynet, in-app purchases, Play License checks, or mandatory GCM

Apps that have a fallback or work without those will usually work, and you can install them from Aurora Store.


2. Seedvault is included and lets you backup system/apps/contacts/messages to a folder, to a flash drive, or to select cloud providers

You can use EteSync or DavDroid or DecSyncCC as contact/calender/tasks provider

 

[cmonty14]

Hi,
I have migrated successfully from LIneageOS to DivestOS 20.
Everything is working fine.
However I cannot start banking app ING after installing it from Aurora store.
Are there known issues with banking apps not running on DivestOS?

THX

 

[cmonty14]

After installing DivestOS 20.0 on my device and installing all previously used apps I have identified this issue:
I cannot pair my Garmin watch with app "Garmin connect".

The issue is that "Garmin connect" crashed when it starts pairing after watch has been identified. Here's the relevant crash information:

type: crash
osVersion: OnePlus/OnePlus5T/OnePlus5T:13/TQ2A.230305.008.C1/eng.emy.20230321.233403:user/release-keys
package: com.garmin.android.apps.connectmobile:7558
process: com.garmin.android.apps.connectmobile

android.content.ActivityNotFoundException: No Activity found to handle null
at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:2200)
at android.app.Activity.startIntentSenderForResultInner(Activity.java:5895)
at android.app.Activity.startIntentSenderForResult(Activity.java:5858)
at androidx.activity.ComponentActivity.startIntentSenderForResult(SourceFile:2)
at android.app.Activity.startIntentSenderForResult(Activity.java:5813)
at androidx.activity.ComponentActivity.startIntentSenderForResult(SourceFile:1)
at com.garmin.android.apps.connectmobile.bic.SetupWizardActivity$q.onDeviceFound(SourceFile:41)
at android.companion.CompanionDeviceManager$Callback.onAssociationPending(CompanionDeviceManager.java:252)
at android.companion.CompanionDeviceManager$AssociationRequestCallbackProxy$$ExternalSyntheticLambda0.accept(Unknown Source:4)
at android.companion.CompanionDeviceManager$AssociationRequestCallbackProxy.lambda$execute$1(CompanionDeviceManager.java:924)
at android.companion.CompanionDeviceManager$AssociationRequestCallbackProxy$$ExternalSyntheticLambda4.run(Unknown Source:4)
at android.os.Handler.handleCallback(Handler.java:942)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:201)
at android.os.Looper.loop(Looper.java:288)
at android.app.ActivityThread.main(ActivityThread.java:7884)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
at com.android.internal.os.ExecInit.main(ExecInit.java:48)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:355)

I could pair the watch in > Settings > Bluetooth, but then the watch is not identified by "Garmin connect" either.

Could you please advise how to fix this issue?

 

[SkewedZeppelin]

at android.companion.CompanionDeviceManager$Callback.onAssociationPending(CompanionDeviceManager.java:252)

Could you please advise how to fix this issue?

Interesting!

That is CompanionDeviceManager which DivestOS removes.
I originally removed it years ago because it was only used by Android Wear (which depends on Google Play Services which isn't included).
But it seems to be commonly used these days as you demonstrate.

I'll add it back in the next update.

 

[cmonty14]

Interesting!

That is CompanionDeviceManager which DivestOS removes.
I originally removed it years ago because it was only used by Android Wear (which depends on Google Play Services which isn't included).
But it seems to be commonly used these days as you demonstrate.

I'll add it back in the next update.

Could you please share this fix with me so I can test it?

And should I report this issue in Git to make this official?

 

[androidtel]

Thank you for making this ROM available!
Up to date and with the possibility to lock the bootloader.
Thank you!

 

[androidtel]

Update to April 16 2023 DOS version with Android security update of April 5 did work perfectly.
Thank you for your work.