This is explained here:
https://divestos.org/pages/faq#deviceStatus
1 Like
Running the latest version on a OP7T for a while now and i noticed that when 90Hz is enabled, after some time of inactivity it drops to 60Hz (presumably for battery saving) but also there is a shift in brightness and color (with screen timeout disabled).
Also, Seedvault backup fails to complete. Goes up to 83% an then fails. Looking at its github and searching a bit online it seems it is very unreliable. I assume you can’t include the latest versions because they are targeted to A14 and A15. Are there any tips/recommendations for backing up before OS updates?
Finally is there a way to run apps that say that they “need” the latest version of Google play to run? It used to run fine, but after an app update it shows a notification and the only option is to close the app. I tried the MicroG compatibility layer but it does not seem to work.
P.S. I recommended Divested Computing for the 2024 Proton Fundraiser, maybe you can include it to the news page so more people can recommend it to Proton.
does it ever go back up?
like worse/darker or brighter?
you can maybe check logcat to see what app it fails on and then disable that one
https://divestos.org/pages/faq#backups
it should work just fine
are you sure you installed the latest version of microG from F-Droid? the default is one is very old
https://divestos.org/pages/faq#microgEnable
will do, thank you
About the screen, from 90 it drops to 60 after a few seconds of inactivity and when you interact with the screen it jumps back at 90. At 60 the screen is dimmer and has different color hue (seems a bit red-er to my eyes). I tried with adaptive brightness off, extra dim off and night light off, same behavior. Might be my actual screen without confirmation from other people.
The app issue is fixed for now, the issue probably was not using the latest version of microg.
As about the backup, i will read the logs and see if i can figure something out.
Edit: took the brute force approach and disabled “App backup” and excluded all apps except “Device settings” and it still failed. Probably will contact Seedvault devs.
Thanks Tavi for the help.
Please amend the app list under https://divestos.org/misc/app-backup.txt to include the Fossify apps or perhaps replace the Simple Mobile Tools with their Fossify versions.
Have you had your screen repaired/replaced or device refurbished?
I’ve heard numerous reports of (OnePlus 6/7) screens being replaced with regular LED panels not OLED ones. While it could be software, if it was replaced it may also be hardware.
You can force 90hz via the “Force peak refresh rate” option in “Developer options” to workaround the drop.
if it fails immediately, some times force stopping it and trying again is successful
will do!
I got it from a friend, i think its the original panel. I run it at 60Hz now for better battery life and to avoid the issue.
As for the backup, it gets to 80-90% either with everything enabled or everything disabled and fails.
Does anyone know why DivestOS 19.1 consumes so much battery on the Vayu? I did a test, and with the Stock MIUI 13 ROM on Android 12, the battery consumption is normal; the charge takes a long time to drain. However, on DivestOS 19.1, the battery drains very quickly. Does anyone have any idea what might be causing this and how to fix it? I searched through the DivestOS documentation but couldn’t find anything on the subject.
Warning: Never close the bootloader of the Pixel 4a (sunfish) after flashing with DivestOS!!!
According to the DivestOS instructions for the Pxcel 4a it says:
“Relockable: Reported Working”
In my experience, this information is wrong! I relied on this information and only closed the bootloader after setting up DivestOS. When I subsequently rebooted, I received the message: “Can’t find valid operating system, the device will not start. “ And so it was, everything was wiped out. The only possible solution was to reopen the bootloader via Fastboot, which then automatically reinstalled a ‘virgin’ DivestOS without the installations and changes I had made.
Had I perhaps done something wrong myself?
The second installation was also flattened when the bootloader was relocked.
It seems to me to be unpossible to run DivestOS with a closed bootloader on the Pixel 4a.
Translated with DeepL Translate: The world's most accurate translator (free version)
In der DivestOS-Anleitung zum Pixel 4a heißt es:
„Relockable: Reported Working“
Diese Angabe ist nach meiner Erfahrung falsch! Ich hatte mich auf die Angabe verlassen und erst nach der Einrichtung von DivestOS den Bootloader geschlossen. Beim darauf folgenden Neustart erhielt ich die Meldung: "Can’t find valid operating system, the device will not start. " Und so war das dann auch, alles platt gemacht. Die einzig mögliche Lösung war dann, den Bootloader über Fastboot wieder zu öffnen, womit dann automatisch die Reinstallation eines ‚jungfräulichen‘ DivestOS erfolgte, ohne die von mir vorgenommenen Installationen und Änderungen.
Hatte ich vielleicht doch selbst was falsch gemacht?
Auch die zweite Installation wurde beim Relock des Bootloaders platt gemacht.
You need to flash via fastboot once and via sideload twice per the instructions: https://divestos.org/builds/LineageOS/sunfish/install.html
Then you can safely relock.
@SkewedZeppelin I like your Project a lot and I check it from time to time about Updates. I’m excited to get a Build for my Device one Day in the Future and I appreciate your effort a lot. I did read about how you manage your Time for this great work and I have much respect for that! I recommend DivestOS where ever I can and I hope that this Project get bigger and more seen. And I did read too, that you eventually wanted to publish a GrapheneOS Store Fork for DivestOS Apps and I really loved this Idea! I hope this will happen and I can’t wait to switch to DivestOS, when my Device get’s a Build. I can’t imagine how time intensive it may all to manage it alone but I wanna say thank you for everything you do for us and we appreciate every little effort and Ideas, like for example the Idea above. I wish you patience and success. We stand with and behind you 
1 Like
@SkewedZeppelin, sorry to ask again but, well it’s been a few weeks and my post is getting buried in the thread. I have some questions about installing DivestOS on my Pixel 7 Pro and potentially contributing with testing and whatnot on some other devices I own. It seems like the preferred place to ask about this is the XMPP chat, but I still can’t post there. What needs to be done to be approved to post?
If you prefer, I can go ahead and post what I have to say here, just might be quite a bit of back and forth is all… Just let me know how I should proceed.
Hello.
First, thanks for DivestOS, I have been using it and it works really well in my old faithful Galaxy S4 Mini.
Second, any chance this device might get the next Android version (so as to keep being supported with security updates)? From what I see it is marked as EOL by end of the year.
Truth is, I have a couple of these devices running very well, and I know others who do as well! So… fingers crossed Thanks!
@GNUser
I won’t ship newer than Android 11/18.1 for that device since Android 12 has strict kernel requirements (bpf & cgroup support in 4.4+) which that device does not meet due to its ancient kernel (3.4).
The point of DivestOS however is to keep providing monthly updates regardless of it being EOL by Google or by the manufacturer, so they will keep coming anyway.
Oh, okay. Well, I always thought it was actually surprising to have newer versions of Android running on this anyway. Though I have seen Android 12 for the 9195l so I though it would be doable. Probably not worth the extra work anyway.
BUT, you did give a glimpse of hope! You mean that in 2025 I will still have the option of running the updater and get the device secure, just as I do today? That’s wonderful news!
Any idea at which point it will not be possible to do so anymore (as in, security updates might become incompatible with it?)
Thanks again!
they do it, but in a way that subtly breaks part of the network stack which I deem unacceptable to ship
yes
no, these are NOT secure, please read: Patch Levels - DivestOS Mobile
DivestOS is the most secure choice in most cases for end of life devices, but it is still insecure due to the limitations of what can/can’t be patched
@SkewedZeppelin What happens in the system when we enable the ‘Unprivileged microG Enablement’ option, even if microG is not installed?
@Zorosuro nothing
@SkewedZeppelin How can a user find out whether he can install ROM DivestOS or not on his phone model, which is indicated on the site?
Please write opposite each phrase you came up with: yes, it is possible to install Divest0S, it will work or no, it is impossible to install DivestOS, it will not work.
Status: Broken -?
Status: Very Likely Working -?
Status: Untested -?
Status: Tested Working -?
Status: Mostly Working -?
Status: Reported Working -?
Status: Mostly Working and Outdated -?
The logic is very simple, I do not want to guess or waste time on experiments, but to be sure that after installing ROM DivestOS for my device I will be able to use it.
I’ll use the hint, those with working in their name are the one you want
2 Likes