Updates
August 31, 2026 - DresSecureComms 1.9.0: The Offline Scanner Lands, Plus vCard, Languages, and a Run of Fixes
This is the update that finishes the file scanner and brings DresSecureComms up to the level of the rest of the system. Since the last post I have shipped a run of releases, working through bug reports as they came in and adding the features people asked for, and the app is now sitting on around sixteen thousand downloads across everywhere it is published. Here is everything that landed.
The offline scanner, the last piece. The file scanner can now check a file or an installed app against a signature database held on your own device, with nothing sent anywhere and no key or connection needed. This is the part Hypatia was known for, done my own way inside the app. It ships with a starter database of over three thousand real Android stalkerware and spyware signatures, credited in the app to the Stalkerware Indicators Collective, so it detects genuine threats the moment you install it. You manage the database yourself: on the file scan menu there is now an offline signature database option that shows how many signatures are loaded and lets you import a signature file straight from your device, using the system file picker so no permission is needed, either replacing the database or adding to it. Import a fresh file whenever you want to keep it current. VirusTotal stays exactly where it was, a separate option that still runs its online check for anything the offline scan does not flag. The scanner now works with no VirusTotal key at all, which it did not before.
Import and export your contacts as a file. A supporter asked for a way to move contacts in and out without granting the full contacts permission, and it is in. You can import contacts from a .vcf file and export your encrypted contacts to one, both through the system file picker, so no contacts permission is ever needed. It is useful for moving in from a backup or another app, keeping a local copy, or working fully offline. Thank you to the person who suggested and supported it.
Choose your language. A user wrote in asking to use the app in their own language, so there is now a language setting, with Spanish as the first full translation and the framework in place for more. It uses Android's own per-app language system, so it works from Android 7 all the way up and appears in the system language screen on newer versions too. To request a language that is not listed, email me and I will look at adding it.
The fixes. Contact names with emoji or accents imported from a .vcf file were showing garbled, a decoding fault in the importer, now corrected. Some conversations showed a blank message screen until you placed a call to that person, a thread lookup that could quietly fail, now given a fallback so the messages load either way. And when the app is your default phone app, tapping a missed call notification did nothing, because Android builds that notification itself and the app was not advertising a call log for it to open, now fixed so it opens your call history as expected. Thank you to the people who traced these, one of them right down to the logcat line.
What is left. There is one more known issue I am working through carefully, a crash during background MMS handling on Android 16 that comes from the ageing MMS library the app relies on, and because it sits on the part of the app that sends and receives MMS it needs proper testing on a real device across a carrier before it ships, so it is getting its own focused release rather than being rushed in. Beyond that, DresSecureComms joins the rest of the system at the stage of simply being kept maintained, and my attention turns to the Linux distribution and the bonus app, one that works alongside Magisk, for Google's install restriction.
Get the app from GitHub releases or IzzyOnDroid. It is now also listed on several third party stores, gathered together in the Projects tab. If something breaks on your device, tell me with the device and ROM, that is how these get found.
August 9, 2026 - DresSecureComms Nearly Finished, a Fresh Demo, and a Batch of Hardening
The push on DresSecureComms is nearly at the finish line. Since the modules were signed off I have been heads down on the app, working through bug reports as they come in and tightening the parts that needed it, and it is close now to sitting at the same level as the rest of the system.
The geo spoofer. A user on a OnePlus Nord 4 running Android 16 reported that the mock location feature failed with a message every time they tried it. It turned out to be mine, not their phone. When the app registers itself as a location source it has to tell Android how accurate that source is, and it was handing over a value that newer Android no longer accepts, so the whole thing was refused and the refusal was being swallowed without anyone being told. It is fixed, it now gives Android the values it expects and registers through the newer interface on Android 12 and later, the spoofed position is also handed to the combined location source that most apps actually read today, and there is a new button to stop mocking without restarting the phone. A real thank you to the person who reported it and tested another app on the same handset to prove the fault was mine.
Hardening. Alongside the visible fixes I closed a couple of quieter things. One of the app's internal receivers was reachable by other apps on the device when it never needed to be, so it has been shut to the app itself, and one of the screens that other apps can hand information to is now guarded against being handed something malformed. Neither was known to be exploited, both are the sort of thing you fix before it ever becomes a problem rather than after.
A new demo. The demo video on the site was showing an older build, so I recorded a fresh one on a Moto g32 running the current system, and this time I host it here myself rather than on a third party. You can watch it in the DresOS Android tab above. It runs through the whole system on a real device, the file scanner and the spam shield included.
What is left. One more major update finishes DresSecureComms, the big piece being the offline signature side of the file scanner, the part that brings in what Hypatia was known for so a file can be checked with nothing leaving the phone at all. After that the app joins the rest of the system at the stage of simply being kept maintained. I am also lining up the last of the housekeeping, and there is groundwork going on behind the scenes toward the Linux distribution and toward the bonus module for Google's September install restriction.
Get the app from GitHub releases or IzzyOnDroid. If something breaks on your device, tell me with the device and ROM, that is how these get found.
August 4, 2026 - The Modules Are Complete: microG v3.1.7, WebView v2.3.2, and Both Now Self-Maintaining
Over the past couple of days I pushed the last manual patches to both Magisk modules, and from my end they are now complete. From here they keep themselves current. A GitHub Action runs every week, pulls the newest version of everything the modules carry straight from its original source, including my own DresOS WebView engine from its own repository, checks each one against its pinned signing key, then rebuilds the module, bumps the version and publishes the new release by itself. Nobody has to rebuild them by hand anymore, and the new releases come through the same way they always have. This is something I planned for a long time, to switch on once the modules were finished, so that keeping them current stops being a weekly job and that time can go into the rest of the organisation instead.
Where that leaves the system. With the build guide refined, both modules patched and now maintaining themselves, and the WebView engine tracking Cromite's latest, three of the four parts of the DresOS Android system are solid and only need keeping current from everything I can see. The last part is DresSecureComms, and the next couple of weeks are tunnel vision on bringing it up to the same level as the other three. Alongside that I will keep pushing engine updates to bring the WebView to completion and keep refining the parts that are already done. This is me holding to my word: every part of the system stays updated and maintained, not shipped and forgotten.
The WebView engine, honestly. The newer engine I put out caused pages to crash inside some apps, so I have reverted to the previous engine and there should be no more browser problems. I tried to take a shortcut to build the new one and it did not work out, which is simply how you learn what works and what does not. A proper updated engine is coming, but not this week. The current workload is full with finishing DresSecureComms and getting some bug bounty work going to bring in funding for the organisation's future.
After that. Once DresSecureComms is where it needs to be, the whole system is at the stage of simply being kept maintained, and from then on I only push an update when something major genuinely needs changing in one of the four parts. Over the next couple of months it is looking promising that my Linux distribution project run begins, with a roadmap and a full plan released right here on the website, so keep an eye out for it. There may also be one last module before then, one that gets around the app installation restriction Google brings in this September. That one is not part of the Android system, just a bonus for the community.
To everyone who has used my projects, tested them on their devices, sent in bug reports, or helped in any other way, thank you. This began as one person's dream and you are the reason it keeps becoming real. Let's keep building, and keep fighting to keep Android open.
August 1, 2026 - microG v3.1.5, WebView v2.2.1, and the Modules Now Update Themselves
Both Magisk modules have been audited end to end and both have a release out of it. The short version: the bundled apps inside the microG module now keep themselves current without me.
The automation is live. A pipeline runs every week against GmsCore, the microG Companion, GsfProxy, Aurora Store and Aurora Services. If any one of them has moved, the module is rebuilt, the version bumped and the release published on its own. Until now only a GmsCore change could set that off, so an Aurora update could sit there unnoticed for as long as it took someone to spot it. Every bundled app is also checked against a pinned signing key before it is staged as a system app, which previously only applied to the microG core. If a download ever comes back signed by someone else, the build stops rather than shipping it.
The rest is smaller. The WebView module's update check still pointed at my old GitHub account, so in-app update checks were not resolving properly; that is fixed. And a permission entry added to the microG module in v3.1.4 for Aurora Services turned out to do nothing at all, because the app never asked for those permissions in the first place, so it has been taken back out and the generator that writes that file now handles an app with no entry yet.
What I am doing next. The WebView module gets the same treatment microG just had: an automatic build and release workflow, so when I push a new engine the module rebuilds, versions and publishes itself rather than waiting on me to remember. That is the whole point of this stretch. The Android system is finished, so the work now is making sure it stays current on its own, because a privacy system that quietly falls behind upstream is worse than useless. Between the two modules and the app, that is nearly everything I ship maintaining itself.
Grab them from the module releases. As always, if you flash something and it breaks, tell me with your device, ROM and Android version, and it gets fixed.
July 30, 2026 - DresSecureComms 1.8.1, the Scan Engine, and What Comes Next
Three bug reports came in from people running 1.8.0 and all three turned out to be real, so 1.8.1 is out and it is worth updating to straight away. Thank you to everyone who sent them in. This is exactly why I ask.
Messages that only showed up in the notification. If someone's number reached you in one format and you had saved it in another, with the country code against without it for instance, Android could file the same person under two separate conversations. Your replies went into one and their messages went into the other, so what you received was nowhere to be found inside the app even though the notification showed it fine. Conversations are now matched on the number itself, so everything with that person sits in one thread whichever way it arrived, and threads that were already split show up joined back together.
Calls. The message notification sound no longer plays just before the ringtone on an incoming call. The screen now always comes back on after you move the phone away from your ear too. That one only bit phones using virtual proximity sensing rather than a real sensor, where the screen simply stayed dark and you had to wake it before you could hang up. There is a switch under Settings, Calls if you would rather it never blanked at all.
Sending. A message that fails to send now says so and is marked as failed, instead of sitting there looking like it went. Replies sent straight from a notification now appear in the conversation, and long ones are split properly rather than being dropped.
The scan engine is nearly complete. Until now, if VirusTotal had never seen a file, File Scan told you exactly that and left you there, which is the most common result for anything built outside the Play Store. You can now send that file to VirusTotal yourself and have its engines analyse it. It asks every single time, it is one file at a time, and the prompt says plainly that the file leaves your phone and that VirusTotal keeps what it is sent and shares it with the antivirus companies it works with. Nothing is ever uploaded on its own, and a sweep of your installed apps still never uploads anything. You can also scan one app on its own now instead of sweeping all of them. What is left for version two is offline signature scanning, the part Hypatia is known for, and then the engine is finished.
Automation on the module repos. The microG module already pulls the latest officially signed microG core on a schedule and bumps itself when upstream moves. I am extending that to everything else the modules carry, so every app bundled inside them stays current on its own instead of waiting on me to rebuild by hand. That work starts shortly.
The Linux distro. Work on my defensive security distribution starts soon. I am taking a short break first. Seven months on the Android system is a long run, and the right thing to do before I point my attention somewhere else is to make sure that system is properly robust, so the next stretch goes on bug reports, fixes and keeping everything current. Then the distro build begins in earnest.
Get the app from GitHub releases or IzzyOnDroid, and the modules from the module releases. If you find something broken, tell me. It gets fixed.
July 23, 2026 - DresSecureComms 1.8.0, Hypatia Dropped, and microG v3.1.3
This is the update that finishes what I set out to do with DresSecureComms. It now handles the malware scanning and the spam calls too, which means another two apps come out of the build and more than half of the system's core functions run on components I build and sign myself.
File Scan. DresSecureComms can now check a single file, or every app installed on your device, for malware. It does it by fingerprint, so the file never leaves your phone: only a SHA-256 goes out, and it comes back checked against seventy or more antivirus engines at once. This is version one, and it is what replaces Hypatia inside DresOS. Hypatia set the bar for on device scanning and it served the system well, and offline signature scanning, the thing Hypatia is known for, is what version two adds.
Spam Shield. Incoming calls are now screened before your phone rings. Premium rate numbers are rejected, short codes are silenced, and callers faking the first digits of your own number get flagged. You can go stricter and silence anyone not in your contacts, or reject withheld numbers outright. Saved contacts always ring through. The important part is that all of it runs on the device: no number is ever sent anywhere to be looked up, which is the whole problem with every mainstream spam blocker.
Encryption keys are now per contact. This was the real weakness people kept pointing at, and they were right. One code shared with everybody meant anyone with the code could read everything. Now each contact gets their own code, set from the conversation menu, used only for that thread. The old shared key still covers anyone you have not set a code for, and every message you have already sent still opens.
Fixes people asked for. The screen now turns off when you hold the phone to your ear on a call. Starting a new message suggests your contacts as you type, so you no longer have to go and look a number up first. The option to save a number is hidden once that number is already saved. And you can block or unblock any number straight from the call log.
microG v3.1.3. The module's update and issues links now point at the current organisation, so update checks resolve properly again, and the leftover build plumbing from the retired Google signed flavour is gone. Nothing changed in what lands on your device.
The guide has been cut down again to match. Hypatia is out of it entirely, its section, its firewall rule and its weekly scan step, with the scanning folded into the DresSecureComms section where it now belongs.
Get the app from GitHub releases or IzzyOnDroid, and the module from the module releases.
July 18, 2026 - The DresOS Android Defensive Security System Project Run Is Now Finished
This has been my first ever proper project run, and it lasted 7 months altogether. Within these 7 months I gained many loyal users who now put their trust into DresOS, and I could not thank each and every one of you enough, especially everyone who sent in bug reports. Without you my job would have been 100x harder.
Over the past few days I put out some of my last big updates to everything to do with parts of my system, that being the build guide, the Magisk modules, and DresSecureComms. I only have one more module left to release that is part of my system, but it is not a main component. It will be released in September, when Google brings the next restriction into place around app installation, as my system solely focuses on battling Google and its data mining monopoly by bypassing each and every restriction they bring into place.
The reason the project run has come to an end is that I have done everything I set out to do. Continuing with the Magisk module roadmap is not a viable option, as both my microG suite and my system WebView module with my own WebView engine are enough, and the guide as a whole has been refined, debloated, and rewritten to be less convoluted. The rest of the roadmap was just covering things in the guide that can be done manually, whereas the microG suite and the WebView module were genuinely needed.
DresSecureComms was a recent addition I brought in over the rest of the Magisk modules, as it covers and secures core components needed for your day to day life on Android. Soon I will add my file scan engine, and after that it will be complete in full, along with one final massive change within the system: dropping Hypatia for DresSecureComms for the malware scanning.
Of course this does not mean I am dropping the projects. No, no, no. Each and every single one of them will be maintained and updated constantly to bring you the latest device security, and at some point in the future, when Google has calmed down, I will release a full custom ROM, starting off with the Moto G32.
But for now, as an organisation, I must change gears and move on to the build and release of my Linux distribution, which should elevate me to whole new heights by bringing secure solutions to both mobile phones and computers.
One last thing: if you enjoyed using any of my projects and love what I am doing, then please help me out by telling a friend about DresOS, shouting me out in your social media stories, posting links to my website dresos.org, and/or putting a tip in the jar to go towards test devices, servers, and coffee for the late night build sessions.
ko-fi.com/dresos
Thank you guys for showing me so much love 💚
- DresOS / The DresOS Foundation
July 3, 2026 - The DresOS Foundation, dresos.org, and DresSecureComms 1.6.0
I am now The DresOS Foundation. DresOS has grown out of a personal GitHub account and into its own organisation at github.com/The-DresOS-Foundation. The full DresOS Android guide has already made the move, and DresSecureComms and the Magisk modules follow it over shortly. Links to repositories that have moved redirect automatically, so nothing breaks while the migration finishes.
The website has its own domain. This site is now at dresos.org, and I finally have a proper contact address to match: security@dresos.org. Same site, real home.
DresSecureComms 1.6.0 is out, and it is on IzzyOnDroid. The app is now listed on IzzyOnDroid and scans completely clean on VirusTotal, zero detections across every engine. 1.6.0 makes picture messaging work end to end: the crash when sending a photo or group message is fixed, and incoming photos now download automatically, appear inside the conversation, and raise a notification, with picture only conversations showing up in the message list. Your own sent messages appear in the chat instantly and stay in your history whether or not the app is the default SMS app. The in call keypad and call controls are much larger, message notifications carry a Copy action, and tapping a notification opens that conversation. Coming next: importing your own PGP, age, or SSH ED25519 keys to sign your messages. Thanks to the Fossify team, whose Messages, Phone, and Contacts apps I used as references for the MMS work. A huge thank you must also go to Fake Traveler; my mock location components are built on references from their application. And to URL Check, just for the scan part that connects to VirusTotal; I built my scan engine from that.
DresOS microG v3.1.1. The microG module dropped the experimental Google signed build path entirely; grafting Google's certificate onto microG's bytes is not possible without Google's private key, so the module no longer pretends otherwise. Stock ROM guidance was replaced with honest, version aware signature spoofing instructions: LSPosed (JingMatrix fork) plus FakeGApps on Android 15 and below, and on Android 16 or newer a ROM with built in microG signature spoofing is required. Everything else about the bootloop safe pure file overlay design is unchanged.
Get DresSecureComms from IzzyOnDroid or GitHub Releases.
June 23, 2026 - DresSecureComms, the DresOS Secure Communications App
DresOS now has its own secure communications app. DresSecureComms is a single, FOSS, fully de Googled app that brings private messaging, calling, contacts, link threat scanning, photo metadata wiping, and location spoofing together in one place, built and signed by DresOS with no Google services and no trackers.
It can be set as your default SMS and phone app. Messaging is a private offline SMS client with optional per message AES-256-GCM encryption, readable only by another DresSecureComms user who shares the key. The dialer is a full default phone app with its own in call screen - mute, speaker, keypad, hold, add call - plus a deletable call history and caller ID and spam screening. Contacts live in an encrypted on device vault with add, edit, and import. Threat Scan checks any link against VirusTotal and returns a clear safe, suspicious, or dangerous verdict. There is also a photo metadata wiper, a geo spoofer for mock locations, an app lock, and an app wide block screenshots mode.
In the DresOS Android system it consolidates several separate tools into one app, taking over URL Check, the Fossify Phone, Messages, and Contacts apps, and Fake Traveler.
Source and releases: github.com/DresOperatingSystems/DresSecureComms.
June 19, 2026 - The Biggest DresOS Update Yet
This is one of the largest coordinated updates DresOS has shipped. The whole system WebView path is now DresOS's own from source to signature, microG gained an automatic update pipeline, and the entire DresOS Android guide and security architecture were rewritten to match. Here is everything in one place.
DresOS WebView - my own system WebView engine. DresOS now ships its own system WebView. DresOS WebView is a Chromium engine built from Cromite (Chromium 145.0.7632.120), with Google services and telemetry stripped and Cromite's privacy and security hardening throughout. It replaces the previous third party WebView engine entirely. Where that engine was someone else's build, DresOS WebView is my own, signed with the DresOS release key, so the whole WebView path is under DresOS end to end.
It installs the same proven way as before: the signed APK is placed in the systemless tree at system/product/app/ via Magisk magic mount, a static RRO adds the package plus the DresOS certificate to config_webview_packages, and service.sh promotes it to the active provider with cmd webviewupdate set-webview-implementation after boot complete, verified via dumpsys. The post-fs-data bootloop sentinel and the inert mode fallback carry over, so a failed activation can never bootloop the device, and removing the module restores the stock WebView. Flashing it over the previous WebView module updates in place, with nothing to uninstall first.
The engine is also published on its own as a standalone signed APK, DresOS WebView v1.0.0, so it can be installed independently of the module. It is distributed through its own GitHub releases only.
DresOS microG v3.0.1 - now self updating. The DresOS microG module has been bumped to v3.0.1. A weekly GitHub Actions pipeline now pulls the latest officially signed microG core (GmsCore, Companion, GsfProxy) straight from the official microG F-Droid repo and auto-bumps the module whenever upstream changes, so microG stays current without a manual rebuild. The bundled APKs and the install logic are unchanged, and it remains the same bootloop safe pure file overlay with ROM provided signature spoofing.
The guide and security architecture, rewritten end to end. The full DresOS Android Defensive Security guide, the SECURITY_ARCHITECTURE diagram, and the system changelog were all updated to the new WebView engine and microG v3.0.1. Step 7, the Part 3 app suite, the What You Will Need table, the Replacement Overview, and the Layer 5 WebView diagram now describe DresOS WebView and org.dresos.webview throughout.
Requirements (WebView module): Magisk 29.0 or newer, Android 10 through 16, arm64. After flashing, verify with adb shell dumpsys webviewupdate; the active provider should be org.dresos.webview.
I rely on community testing. If you flash any of this and something breaks, please open a bug report at github.com/The-DresOS-Foundation/DresOS-Magisk-Modules/issues with device model, Android version, ROM, root provider, and the logs at /data/adb/modules/dresoswv/logs/.
June 5, 2026 - DresOS microG v3.0.0 Released
The DresOS microG Magisk module has been rebuilt from the ground up and released as v3.0.0, replacing the v2.0.0 design entirely. v3.0.0 is a pure file overlay: no Zygisk payload, no Xposed or LSPosed dependency, and no boot time PackageManager work, which means it physically cannot bootloop the device and it coexists cleanly with the DresOS WebView module.
It ships the officially signed microG suite as privileged system apps under product: GmsCore 0.3.15, Companion (FakeStore at com.android.vending), GsfProxy, DroidGuard Helper, Aurora Store, and Aurora Services, with a privapp permissions allowlist generated from the bundled manifests.
Signature spoofing is now provided by the ROM rather than by the module. Because the bundled microG APKs carry the official microG key, any ROM with microG signature spoofing support spoofs them automatically once they are placed in priv-app. There is no bundled hook and no Xposed framework on any ABI.
Aurora Services now lands as a priv-app with its own permissions allowlist, so silent prompt free installs through Aurora Store work without the standard Android installer prompt for every app. This resolves the v2.0.0 Aurora Privileged Extension issue. ROMs that already ship an upstream signed microG (CalyxOS, LineageOS for microG, iodeOS, /e/OS) are autodetected by cert match and their copy is preserved. GrapheneOS is hard refused.
The DresOS Android guide has been updated end to end: Step 5, Step 6, the What You Will Need table, and the SECURITY_ARCHITECTURE.md Layer 8 entry all reflect v3.0.0. The guide also gained an Aves Libre gallery, the Stratum offline 2FA app, the Tuta Calendar encrypted calendar, and a one tap DresOS HeliBoard design, and every download link was audited to a stable form.
Watch the full system running on a Motorola Moto g32 in the demo video further down this page, recorded on the current build and hosted here on my own site.
I rely on community testing. If you flash v3.0.0 and something breaks, please open a bug report at github.com/The-DresOS-Foundation/DresOS-Magisk-Modules/issues with device model, Android version, ROM, root provider, the output of the Action button on the module, and the logs at /data/adb/modules/dresosmicrog/logs/.
May 25, 2026 - DresOS microG v2.0.0 Released
The DresOS microG Magisk module has been released as v2.0.0. It replaced the older manual microG plus signature spoofing framework setup in the DresOS Android guide with a single flash.
The module stages the full microG suite as systemless privileged apps: microG GmsCore 0.3.7.250932, microG Companion (FakeStore at com.android.vending), microG GsfProxy, microG DroidGuard Helper, plus Aurora Store as a user app. APKs and matching privapp permissions XML land in the same partition (system/product/priv-app on API 28 plus, system/priv-app on API 26 and 27), satisfying Android 11 plus same partition enforcement.
Signature spoofing is bundled as a Zygisk hook scoped to the microG process only. On arm64 and x86_64 LSPosed is no longer required. On armeabi-v7a, armeabi, x86, or riscv64 the bundled hook does not ship a prebuilt and LSPosed plus FakeGApps remains the fallback.
Cert identity is verified post boot by reading the X.509 SHA-256 that PackageManager itself computes via cmd package dump, not by hashing META-INF/*.RSA blobs which legitimately vary between build environments. ROMs that already ship a working upstream signed microG (CalyxOS, LineageOS for microG, iodeOS, /e/OS) are autodetected by cert match and their copy is preserved; only the Aurora components are staged on those ROMs. GrapheneOS is hard refused because GrapheneOS deliberately blocks signature spoofing and ships its own Sandboxed Google Play.
Debloat moved off systemless overlay markers onto runtime pm disable-user, persisted in /data/system/users/0/package-restrictions.xml. This ends the Android 14 plus boot loop class where overlaying a priv-app directory hid the ART OAT cache. Uninstalling the module re enables every package the module disabled.
The bootloop sentinel is per component: a strike for the Zygisk hook only disables Zygisk on the next boot, a strike for the priv-app overlay only disables the overlay, a strike for the debloat pass only disables debloat. The rest of the module keeps running.
Known issue in v2.0.0: the Aurora Privileged Extension (com.aurora.services) does not always land as a system priv app on every device. Aurora Store itself works fine. The silent install path through Aurora Services is the affected piece, which means you will see the standard Android installer prompt for each Aurora Store install. This was resolved in the v3.0.0 rebuild.
The DresOS Android guide has been updated end to end. Step 5 (Install Magisk Modules), Step 6 (Set Up microG), the SECURITY_ARCHITECTURE.md Layer 8 entry, the What You Will Need table, and the Magisk Modules Roadmap all reflect the new module.
I rely on community testing. If you flash v2.0.0 and something breaks, please open a bug report at github.com/The-DresOS-Foundation/DresOS-Magisk-Modules/issues with device model, Android version, ROM, root provider, the output of the Action button on the module, and the three logs at /data/adb/modules/dresosmicrog/logs/.
May 12, 2026 - First Official Website Update: DresEcoVerse Archived
The DresEcoVerse has been officially closed down. I now maintain this actively updated website where all my resources, guides, and announcements can be found in one place. This is easier for everyone to navigate and keeps everything centralized.
With my focus now on the already released DresOS Magisk Modules for my Android Defensive Security System build, and with the full app list included directly in the DresOS Android guide, there is no longer a need for the EcoVerse as a separate hub.
Important: DresOS has no active Telegram presence. This website is the only place to verify link authenticity and official announcements.
April 30, 2026 - Keep Android Open
Hello and I have a massive favour for you guys all open source organisations like mine need your help to keep the android world open, the world of android is starting to Look bleak but with your help I can keep the fight against google going, to find out how you can help and do your part please check the links below and lets keep the struggle going
https://keepandroidopen.org/open-letter/
https://keepandroidopen.org/
