{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DivestOS is a more private and more secure aftermarket system.
Nexus 5 Notes:
- 16.0 is quite buggy, 15.1 should be stable
- Bluetooth may or may not work on 16.0
Features:
- strong focus on FOSS
- various system hardening
- various privacy enhancements
- automated removal of unnecessary proprietary blobs
- automated kernel hardening and CVE patching
- ability to relock bootloader on supported devices
- verified boot on supported devices
- no root support
- SELinux always enforcing
- encrypted by default
- monthly updates
- OTA delta updates
- OTA updates over Tor (optional)
- F-Droid included
- hardened system WebView with rapid updates: https://divestos.org/misc/ch-dates.txt
Extra Features (not installed by default & also compatible with all systems):
- Mull, our hardened fork of Fenix with rapid updates: https://divestos.org/misc/ffa-dates.txt
- Hypatia, our real-time malware scanner
- Extirpater, our free space eraser
Links:
- Website: https://divestos.org
- Onion: http://divestoseb5nncsydt7zzf5hrfg44md4bxqjs5ifcv4t7gt7u6ohjyyd.onion
- Downloads: https://divestos.org/index.php?page=devices&base=LineageOS#device-hammerhead
- Changelogs: https://divestos.org/index.php?page=news
- Project History: https://divestos.org/index.php?page=history
- Known Issues: https://divestos.org/index.php?page=broken#hammerhead
- Screenshots: https://divestos.org/index.php?page=screenshots
- Security Patching Overview: https://divestos.org/index.php?page=patch_levels
- About + Credits + Notices: https://divestos.org/index.php?page=about
- Donate: https://divested.dev/donate
- Source Code: https://github.com/divested-mobile or https://gitlab.com/divested-mobile
- XMPP Chat Room: xmpp:[email protected]
Device Specific Links:
- Device Tree: https://github.com/LineageOS/android_device_lge_hammerhead
- Kernel: https://github.com/LineageOS/android_kernel_lge_hammerhead
- Kernel CVE Patches Applied: https://github.com/Divested-Mobile/...CVE_Patchers/android_kernel_lge_hammerhead.sh
Other Bits:
- Good and bad feedback is welcomed. Else how can we improve?
- If you find a bug, please report it below or via GitHub/GitLab.
- Testing/Translations/Code contributions are gratefully appreciated.
Important Notes for New Users:
- Please make a backup of your device and copy it to another computer.
- You must wipe before installing this OS.
- This OS has userdata encrypted by default
- You are intended to relock your bootloader with this OS (if your device is marked supported for that).
DivestOS does *not* support the following:
- Google Apps (OpenGAPPS)
- DRM (Widevine)
- alternative recoveries (TWRP)
- root (Magisk)
- runtime modification frameworks (Xposed or theme engines)
All downloads are GPG signed with the following key:
Code:
#B874 4D67 F9F1 E14E 145D FD8E 7F62 7E92 0F31 6994
-----BEGIN PGP PUBLIC KEY BLOCK-----
mDMEXupIxBYJKwYBBAHaRw8BAQdAC1RiTvrqJaAQ4FIHsxX+gzEgdT4mspISS+p0
y847Nge0SERpdmVzdE9TIFJlbGVhc2UgU2lnbmluZyAoMjAyMCAjMSkgPHN1cHBv
cnQrcmVsZWFzZXNpZ25pbmdAZGl2ZXN0b3Mub3JnPoiQBBMWCAA4FiEEuHRNZ/nx
4U4UXf2Of2J+kg8xaZQFAl7qSMQCGwMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AA
CgkQf2J+kg8xaZR1BgEAwwLVVsG7kbp8M3GTV987XpVl5cZeTtDc/g+66briCHUB
APiuH/dk8eRnhFnq4Up2/j7uD/8FtSvxPbHiz6t1MdgB
=VzP2
-----END PGP PUBLIC KEY BLOCK-----
I'm trying to use this but both camera and wifi hotspot do not seem to work. Can I help somehow?
Hammerhead: camera and hotspot do not work. · Issue #140 · Divested-Mobile/DivestOS-Build
Phone boots fine, tho. Bootloader relocking works as well. I haven't tried calling, incoming SMS do work. I'd like to use this phone again, but I can't without camera and hotspot. I did run a logca...
github.com
Hi
@SkewedZeppelin Just did a clean install. I can't remove apps the regular way (tap, hold, swipe to the uninstall field at the top). I have to go into apps section in the settings and there click uninstall.
fw190 said:
Hi
@SkewedZeppelin Just did a celan install. I can't remove apps the regular way (tap, hold, swipe to the uninstall field at the top). I have to go into apps section in the settings and there click uninstall.
Click to expand...
Click to collapse
This is an old bug in the launcher, it happens at random sometimes. Just force stop Trebuchet.
Hi guys.
I have device LG Nexus 5x bullhead and tried to install Divest on it.
(I installed custom ROMs several times, I am not new to this process)
All went smooth, but when I was setting up the phone, on the step to set the screen lock pin/pattern - it just crashed.
After this I had difficulties to boot it even into fastboot menu and when I did - I tried to flash the genuine (Google) ROM on it (I did it several times and it is working ROM), but during the flashing, in the terminal it showed a list of archives missing.
Now the phones goes to Google logo and then to black screen.
Well, I do not know if there is any workaround or not.
Please advice.
Thanks
balakarpo said:
Hi guys.
I have device LG Nexus 5x bullhead and tried to install Divest on it.
(I installed custom ROMs several times, I am not new to this process)
All went smooth, but when I was setting up the phone, on the step to set the screen lock pin/pattern - it just crashed.
After this I had difficulties to boot it even into fastboot menu and when I did - I tried to flash the genuine (Google) ROM on it (I did it several times and it is working ROM), but during the flashing, in the terminal it showed a list of archives missing.
Now the phones goes to Google logo and then to black screen.
Well, I do not know if there is any workaround or not.
Please advice.
Thanks
Click to expand...
Click to collapse
That sounds less like a DivestOS issue and more like user-error or the dreaded Nexus 5X bootloop issue: https://en.wikipedia.org/wiki/LG_smartphone_bootloop_issues#Nexus_5X
I test DivestOS on bullhead each monthly update before release (without issue).
SkewedZeppelin said:
That sounds less like a DivestOS issue and more like user-error or the dreaded Nexus 5X bootloop issue: https://en.wikipedia.org/wiki/LG_smartphone_bootloop_issues#Nexus_5X
I test DivestOS on bullhead each monthly update before release (without issue).
Click to expand...
Click to collapse
Thanks for replying so soon.
I installed two ROMs before (LineagOS 17.1 and 19.1 Unofficial version) on this device without problem. The unique problem was that I was unable to encrypt the phone on those and that was the main reason to try DivestOS.
I understand it can be the hardware problem (maybe mine), but is there any workaround? Thanks
Hello, first of all thank you for creating this awesome rom. Im using it for some extended period of time on my backup devices which is Nexus 5 and it works great, it feels so secure and also having latest security patch is awesome. Keep doing the great job! Rom is awesome, recommended for everyone!
I managed to install DivestOS 18.1 even on my Nexus 4, works as it should for now. (Been a nexus fan before so i got these 2 nexuses :-D) Is there a chance that you make it for my main phone which is Xiaomi Mi 10t pro, please? At least one build and thats it
scorpion994 said:
I managed to install DivestOS 18.1 even on my Nexus 4, works as it should for now. (Been a nexus fan before so i got these 2 nexuses :-D) Is there a chance that you make it for my main phone which is Xiaomi Mi 10t pro, please? At least one build and thats it
Click to expand...
Click to collapse
Any device I add I have to perpetually maintain.
apollon is already in the queue to be eventually added maybe someday: https://github.com/Divested-Mobile/DivestOS-Build/issues/68
Thank you so much for this
Hello, good day! I was trying to fix my nexus 5 Wi-Fi problem, so I was flashing a few ROMs to see if it get fixed. I tried this one then... No success. Now I'm trying to go back to a stock image, but I'm having trouble to get my phone recognized by the computer. Do I get this problem because the phone is encrypted? Can I decrypt my phone? Can't use trwp eider, because of the encryption.
arnoldwu said:
Hello, good day! I was trying to fix my nexus 5 Wi-Fi problem, so I was flashing a few ROMs to see if it get fixed. I tried this one then... No success. Now I'm trying to go back to a stock image, but I'm having trouble to get my phone recognized by the computer. Do I get this problem because the phone is encrypted? Can I decrypt my phone? Can't use trwp eider, because of the encryption.
Click to expand...
Click to collapse
TWRP should work fine?
DivestOS makes no changes that would lock you to DivestOS or prevent you from switching.
Maybe try a different cable, and a USB 2.0 port.
Also Wi-Fi works fine on my hammerhead, if it doesn't work on multiple systems maybe you have a hardware issue or corrupted persist partition.
SkewedZeppelin said:
This is an old bug in the launcher, it happens at random sometimes. Just force stop Trebuchet.
Click to expand...
Click to collapse
Big fan of your OS, i know you do not support SU or Magisk or microG, but could you atleast let us multiboot with your awesome OS? please kindly add the Kexec-Hardboot patch to your kernel so we could be able to boot into a googled OS, or Ubuntu Touch.
thanks in advanced and looking forward to this patch added.
Kexec-hardboot patch
[email protected] said:
please kindly add the Kexec-Hardboot patch to your kernel so we could be able to boot into a googled OS, or Ubuntu Touch.
Click to expand...
Click to collapse
No, kexec is explicitly disabled for security reasons: https://github.com/Divested-Mobile/DivestOS-Build/blob/master/Scripts/Common/Functions.sh#L1048
If you want such changes the way to get them is by compiling your own builds: https://divestos.org/pages/build
Ubuntu Touch for this device is also blatantly insecure missing years of basic security patches: https://github.com/ubports/android_kernel_lge_hammerhead/commits/ubp-5.1
SkewedZeppelin said:
No, kexec is explicitly disabled for security reasons: https://github.com/Divested-Mobile/DivestOS-Build/blob/master/Scripts/Common/Functions.sh#L1048
If you want such changes the way to get them is by compiling your own builds: https://divestos.org/pages/build
Ubuntu Touch for this device is also blatantly insecure missing years of basic security patches: https://github.com/ubports/android_kernel_lge_hammerhead/commits/ubp-5.1
Click to expand...
Click to collapse
please do elaborate on the security reasons, all kali nethunter kernels have Kexec-hardboot enabled, i run the latest version and would love to see the exploits for it. Please enlighten me.
[email protected] said:
please do elaborate on the security reasons, all kali nethunter kernels have Kexec-hardboot enabled, i run the latest version and would love to see the exploits for it. Please enlighten me.
Click to expand...
Click to collapse
There are no direct exploits for it, it is just attack surface reduction.
SkewedZeppelin said:
There are no direct exploits for it, it is just attack surface reduction.
Click to expand...
Click to collapse
maybe possibly supply an optional flashable zip for this minor reduction. giving the user the option to enable this to run nethunter kernel, currently i run it systemless, but i have to use an external wifi adapter, honestly is not very stealthy. I believe there are various benefits to having hardboot, that is just one. (having internal wifi support for nethunter)
P.S. maybe it could be added as a developer option in your OS?
[email protected] said:
maybe possibly supply an optional flashable zip for this minor reduction. giving the user the option to enable this to run nethunter kernel, currently i run it systemless, but i have to use an external wifi adapter, honestly is not very stealthy. I believe there are various benefits to having hardboot, that is just one. (having internal wifi support for nethunter)
Click to expand...
Click to collapse
no.
That would require compiling every kernel twice.
SkewedZeppelin said:
no.
That would require compiling every kernel twice.
Click to expand...
Click to collapse
to recompile your kernel do i simply remove "optionsNo+=("KEXEC" "KEXEC_FILE");" and add it to the "optionsYes+=(" section ?
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DivestOS is a more private and more secure aftermarket system.
Nexus 6 Notes:
- 15.1 builds are also available for those who need IMS/VoLTE
- in-place upgrade to 18.1 is not possible unlike previous DivestOS releases due to keystore change
Features:
- strong focus on FOSS
- various system hardening
- various privacy enhancements
- automated removal of unnecessary proprietary blobs
- automated kernel hardening and CVE patching
- ability to relock bootloader on supported devices
- verified boot on supported devices
- no root support
- SELinux always enforcing
- encrypted by default
- monthly updates
- OTA delta updates
- OTA updates over Tor (optional)
- F-Droid included
- hardened system WebView with rapid updates: https://divestos.org/misc/ch-dates.txt
Extra Features (not installed by default & also compatible with all systems):
- Mull, our hardened fork of Fenix with rapid updates: https://divestos.org/misc/ffa-dates.txt
- Hypatia, our real-time malware scanner
- Extirpater, our free space eraser
Links:
- Website: https://divestos.org
- Onion: http://divestoseb5nncsydt7zzf5hrfg44md4bxqjs5ifcv4t7gt7u6ohjyyd.onion
- Downloads: https://divestos.org/index.php?page=devices&base=LineageOS#device-shamu
- Changelogs: https://divestos.org/index.php?page=news
- Project History: https://divestos.org/index.php?page=history
- Known Issues: https://divestos.org/index.php?page=broken#shamu
- Screenshots: https://divestos.org/index.php?page=screenshots
- Security Patching Overview: https://divestos.org/index.php?page=patch_levels
- About + Credits + Notices: https://divestos.org/index.php?page=about
- Donate: https://divested.dev/donate
- Source Code: https://github.com/divested-mobile or https://gitlab.com/divested-mobile
- XMPP Chat Room: xmpp:[email protected]
Device Specific Links
- Device Tree: https://github.com/LineageOS/android_device_moto_shamu
- Kernel: https://github.com/LineageOS/android_kernel_moto_shamu
- Kernel CVE Patches Applied: https://github.com/Divested-Mobile/...8.1/CVE_Patchers/android_kernel_moto_shamu.sh, https://github.com/Divested-Mobile/...5.1/CVE_Patchers/android_kernel_moto_shamu.sh
Other Bits:
- Good and bad feedback is welcomed. Else how can we improve?
- If you find a bug, please report it below or via GitHub/GitLab.
- Testing/Translations/Code contributions are gratefully appreciated.
Important Notes for New Users:
- Please make a backup of your device and copy it to another computer.
- You must wipe before installing this OS.
- This OS has userdata encrypted by default
- You are intended to relock your bootloader with this OS (if your device is marked supported for that).
DivestOS does *not* support the following:
- Google Apps (OpenGAPPS)
- DRM (Widevine)
- alternative recoveries (TWRP)
- root (Magisk)
- runtime modification frameworks (Xposed or theme engines)
All downloads are GPG signed with the following key:
Code:
#B874 4D67 F9F1 E14E 145D FD8E 7F62 7E92 0F31 6994
-----BEGIN PGP PUBLIC KEY BLOCK-----
mDMEXupIxBYJKwYBBAHaRw8BAQdAC1RiTvrqJaAQ4FIHsxX+gzEgdT4mspISS+p0
y847Nge0SERpdmVzdE9TIFJlbGVhc2UgU2lnbmluZyAoMjAyMCAjMSkgPHN1cHBv
cnQrcmVsZWFzZXNpZ25pbmdAZGl2ZXN0b3Mub3JnPoiQBBMWCAA4FiEEuHRNZ/nx
4U4UXf2Of2J+kg8xaZQFAl7qSMQCGwMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AA
CgkQf2J+kg8xaZR1BgEAwwLVVsG7kbp8M3GTV987XpVl5cZeTtDc/g+66briCHUB
APiuH/dk8eRnhFnq4Up2/j7uD/8FtSvxPbHiz6t1MdgB
=VzP2
-----END PGP PUBLIC KEY BLOCK-----
Hi, this is really great! I'm on e OS now so I'm accustomed to (almost) no google. Although I want to ask:
1. if microG is possible to install and use? Say like in a work profile. I have a banking app which is dependent on google and I figure if bootloader is locked it won't detect root no more.
2. Updates are OTA?
3. Reverse process is possible? Going back to e OS in examlpe
Regards
Kjivar said:
Hi, this is really great! I'm on e OS now so I'm accustomed to (almost) no google. Although I want to ask:
1. if microG is possible to install and use? Say like in a work profile. I have a banking app which is dependent on google and I figure if bootloader is locked it won't detect root no more.
2. Updates are OTA?
3. Reverse process is possible? Going back to e OS in examlpe
Regards
Click to expand...
Click to collapse
1. microG is not supported by DivestOS. If you want to compile DivestOS yourself you just need to change one line to build in microG. However simply having a locked bootloader with microG is not enough to pass SafetyNet. At a minimum you'd likely need 'DroidGuard Helper'.
2. Yes, of course.
3. Most definitely. Just unlock and flash whatever.
Ok, thanks
It actually isn*t depending on SafetyNet, just detects root (unlocked bootloader I think) with Rootbeer. Using Magisk hide is only solution now. Dunno if Droid Guard helper has been updated yet. I'll check into it tho.
Going stock with locked bootloader is out of the question. Guess I'll just go ahead with this, and use a second device for that app.
Keep up the good work
@Kjivar
Anyway, locking the bootloader is perhaps a bad idea while running a custom rom - if the phone becomes unbootable for some reason, you may not be able to fix it.
Edit: see reply below - locking is safe on this rom (but I still wouldn't try it on any other rom)
runekock said:
@Kjivar
Anyway, locking the bootloader is perhaps a bad idea while running a custom rom - if the phone becomes unbootable for some reason, you may not be able to fix it.
Click to expand...
Click to collapse
Bootloader locking on supported devices is one of the primary benefits of running DivestOS.
Older devices let you unlock no matter and newer ones will do so as long as OEM unlocking is checked.
Even if /system is corrupted the OEM unlock flag is stored in the checksummed persistent data block and you'd still be able to unlock to fix.
Especially on older devices bootloader locking can be bypassed using manufacturer tools.
My daily driver for the past five years has always had its bootloader locked.
And my stack of test devices all have their bootloader locked.
It is not my fault other ROMs aren't signed correctly to support such a basic feature.
This ROM looks shady
Rootmaster906 said:
This ROM looks shady
Click to expand...
Click to collapse
Please elaborate.
SkewedZeppelin said:
Please elaborate.
Click to expand...
Click to collapse
You can't do anything with this thing. You can't flash gaps and you can't flash magisk. What good is this ROM if you can't do any of that?
Rootmaster906 said:
You can't do anything with this thing. You can't flash gaps and you can't flash magisk. What good is this ROM if you can't do any of that?
Click to expand...
Click to collapse
Those are valid concerns for some users like yourself, but that simply makes you not the target audience.
It does not make it shady.
SkewedZeppelin said:
Those are valid concerns for some users like yourself, but that simply makes you not the target audience.
It does not make it shady.
Click to expand...
Click to collapse
My apologies. I wasn't trying to diss your rom. What happens when I flash this? Is this actually a good ROM or no?
Rootmaster906 said:
My apologies. I wasn't trying to diss your rom. What happens when I flash this? Is this actually a good ROM or no?
Click to expand...
Click to collapse
If you feel the features offered are in your interest, I welcome you to try it.
Just sure to backup first and ensure that backup is somewhere other then your phone.
As forceencrypt is set by default.
And TWRP will be replaced with DivestOS recovery on first boot.
SkewedZeppelin said:
If you feel the features offered are in your interest, I welcome you to try it.
Just sure to backup first and ensure that backup is somewhere other then your phone.
As forceencrypt is set by default.
And TWRP will be replaced with DivestOS recovery on first boot.
Click to expand...
Click to collapse
How do I decrypt? Same as formatting data? Also, can I flash twrp back in divest recovery?
Rootmaster906 said:
How do I decrypt? Same as formatting data? Also, can I flash twrp back in divest recovery?
Click to expand...
Click to collapse
You can format /data in TWRP.
You can flash TWRP back using fastboot.
SkewedZeppelin said:
You can format /data in TWRP.
You can flash TWRP back using fastboot.
Click to expand...
Click to collapse
This ROM is pretty dope! I guess only 8.1 is available. Why can't gapps and magisk be used? Thanks
Rootmaster906 said:
This ROM is pretty dope! I guess only 8.1 is available. Why can't gapps and magisk be used? Thanks
Click to expand...
Click to collapse
Hmm?
8.1 is only if you require VoLTE, otherwise 11.0 is reported stable and more secure.
SkewedZeppelin said:
Hmm?
8.1 is only if you require VoLTE, otherwise 11.0 is reported stable and more secure.
Click to expand...
Click to collapse
Page doesn't have a link for a11. Edit..had to refresh page. Sorry.
Rootmaster906 said:
Page doesn't have a link for a11
Click to expand...
Click to collapse
I assure you, it is there, use Find In Page/Ctrl-F:
https://divestos.org/mirror.php?base=LineageOS&f=shamu/divested-18.1-20210807-dos-shamu.zip
SkewedZeppelin said:
I assure you, it is there, use Find In Page/Ctrl-F:
https://divestos.org/mirror.php?base=LineageOS&f=shamu/divested-18.1-20210807-dos-shamu.zip
Click to expand...
Click to collapse
Found it. So....why isn't magisk and Gapps supported?
Rootmaster906 said:
Found it. So....why isn't magisk and Gapps supported?
Click to expand...
Click to collapse
I don't believe most users need root access, and it also reduces security and prevents easily using features such as verified boot.
GAPPS goes strongly against the privacy and freedom that DivestOS strives to offer, as it is proprietary code from Google.
Warning: bugs and outdated SP ahead...
Spoiler
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Stellar OS is an optimized LineageOS-based Android aftermarket firmware with extra features, developed by people all over the world.
Quoting the LineageOS description:
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Click to expand...
Click to collapse
We offer vanilla and gapps variants. If you install a vanilla variant, the only supported Gapps package is MindTheGapps (gapps builds are not available for a few devices due to space issues).
Download & instructions:
Build 23th September 2021
• 1.1 source update (September SP + new features)
• Fixed fast charging display
Vanilla | Gapps
Old releases:
Spoiler
Build 12th August 2021
Initial release
If you are coming from an older build (beta testers), clean flash is required
Vanilla | Gapps
IMPORTANT: If you are coming from another ROM, you need to format data (there where you type yes in twrp).
IMPORTANT: OTA updates require enabling recovery update in Setup Wizard (or, if you already set your device up developer options) - they do not support TWRP.
About:
Features:
All Mint 2.1 features
September security patch
SafetyNet passing WITHOUT Magisk Hide
Many optimizations
New wallpapers & bootanimation
QS customization (tint, rows customizer, data usage)
Status bar customization (4G/LTE toggle, new NFC & VoLTE icons)
Kill app from notification
Notification pulse
KitKat-style notification ticker
Screenshot sound toggle
Per-app volume
WiFi & Bluetooth timeout
Stellar Tweaks customization section
Navbar Tuner
Improved Trebuchet+
OmniJaws weather service
Many lockscreen clocks
Statusbar ticker
Signed official builds
Smart Charging & Cutoff
Sensor, Wakelock and Alarm blocker
Battery info on lockscreen
Improved microG support (signature spoofing, location support)
...and more (we accept suggestions)
The focus for the inital release was an neccessary set of tweaks and optimizing android.
What's working:
WiFi
Camera and Camcorder
Bluetooth
Fingerprint - Oreo firmware required
GPS
OTG
Video Playback
Audio
RIL
VoLTE
USB tethering/audio
SELinux: Enforcing
Bugs:
You tell me
Sources are available at https://github.com/Stellar-OS and https://github.com/Stellar-Devices
Screenshots from ocean are attached
ROM OS Version: 1.0
ROM Kernel: Linux 3.18.140
ROM Firmware Required: Must be on latest Oreo Stock firmware
Based On: LineageOS 18.1
Version Information
Status: Stable
Current Stable Version: 1.0
SELinux Status: Enforced
Release Date: 15th August 2021
Thanks for letting us know- I'll have to try this! Will Mint 2.1 Seed vault backups be compatible with this new ROM?
doug888 said:
Thanks for letting us know- I'll have to try this! Will Mint 2.1 Seed vault backups be compatible with this new ROM?
Click to expand...
Click to collapse
I'm not sure, as this is a android version jump, but it's worth to try.
In instaled it, its working perfectly. No issues at all until now. Thank you so much for keeping my moto g5 alive
I have one minor issue. It seems TWRP has been replaced by lineageOS recovery. I would like to keep it that way in orer to receive updates. I would like to flash and install magisk though in order to hide root so I can work with MS Oulook and such. I do not see the option in lineageOS recovery. Can I boot into TWRP recovery from adb/fastboot, and then fash it? or are there other options?
listm said:
In instaled it, its working perfectly. No issues at all until now. Thank you so much for keeping my moto g5 alive
I have one minor issue. It seems TWRP has been replaced by lineageOS recovery. I would like to keep it that way in orer to receive updates. I would like to flash and install magisk though in order to hide root so I can work with MS Oulook and such. I do not see the option in lineageOS recovery. Can I boot into TWRP recovery from adb/fastboot, and then fash it? or are there other options?
Click to expand...
Click to collapse
It got replaced because you enabled the checkbox in setup wizard. Disable it in developer settings and install TWRP as normally.
nift4 said:
It got replaced because you enabled the checkbox in setup wizard. Disable it in developer settings and install TWRP as normally.
Click to expand...
Click to collapse
I missed that one. Thanks for the quick reply.
Issue solved. Sadly the microsoft company portal is aware of my device being rooted, this was also the case in android 10, but Ill work around it.
listm said:
I missed that one. Thanks for the quick reply.
Issue solved. Sadly the microsoft company portal is aware of my device being rooted, this was also the case in android 10, but Ill work around it.
Click to expand...
Click to collapse
Have you hidden magisk with a random package name in its settings?
Does your device pass ctsprofile?
If not install magisk hide props module and terminal emulator. Once installed type props in terminal emulator and change the fingerprint to a pixel 4 android 11
Also hide the app that detects root with magisk hide
TheFixItMan said:
Have you hidden magisk with a random package name in its settings?
Does your device pass ctsprofile?
If not install magisk hide props module and terminal emulator. Once installed type props in terminal emulator and change the fingerprint to a pixel 4 android 11
Also hide the app that detects root with magisk hide
Click to expand...
Click to collapse
Yeah, I did all that, I think
- Hidden Magisk, named it Settings
- It passes SafetyNet, and ctsProfile (evalType Basic)
- I did install hide props, ran the emulator and changed the fingerprint. That was new to me.
I have hidden everything of outlook, company portal, etc, but it still I get the error doing my device check in the business portal. As I said, I can work around it. I really appreciate you helping me out but don't bother if you're too busy ;-)
listm said:
Yeah, I did all that, I think
- Hidden Magisk, named it Settings
- It passes SafetyNet, and ctsProfile (evalType Basic)
- I did install hide props, ran the emulator and changed the fingerprint. That was new to me.
I have hidden everything of outlook, company portal, etc, but it still I get the error doing my device check in the business portal. As I said, I can work around it. I really appreciate you helping me out but don't bother if you're too busy ;-)
Click to expand...
Click to collapse
Unfortunately I don't use it else I would test it out and try get it to work
Hi nift4,
awesome work!
My Moto G5 works fine - I've noticed a very long boot time (5 minutes), though.
I did a cleanup with formatting system, data and vendor, before I flashed this image. Maybe to much?
regards, Andy
AndyFx12 said:
Hi nift4,
awesome work!
My Moto G5 works fine - I've noticed a very long boot time (5 minutes), though.
I did a cleanup with formatting system, data and vendor, before I flashed this image. Maybe to much?
regards, Andy
Click to expand...
Click to collapse
This is due to a slow driver, an issue that is known and present in all Android 11 builds for Moto G5, even official Lineage OS.
Idk if kernel 4.9 will get usuable any time soon, but that will hopefully resolve that issue.
listm said:
Yeah, I did all that, I think
- Hidden Magisk, named it Settings
- It passes SafetyNet, and ctsProfile (evalType Basic)
- I did install hide props, ran the emulator and changed the fingerprint. That was new to me.
I have hidden everything of outlook, company portal, etc, but it still I get the error doing my device check in the business portal. As I said, I can work around it. I really appreciate you helping me out but don't bother if you're too busy ;-)
Click to expand...
Click to collapse
Hide props is not needed on this rom, for general information. I built it into the source.
AndyFx12 said:
Hi nift4,
awesome work!
My Moto G5 works fine - I've noticed a very long boot time (5 minutes), though.
I did a cleanup with formatting system, data and vendor, before I flashed this image. Maybe to much?
regards, Andy
Click to expand...
Click to collapse
Formatting system and data is an good idea actually. It prevents leftovers (on system, some things like Gapps packages store restore scripts). Formatting vendor is useless. No harm done, just time wasted.
Thanks for your replies and explanation!
It's amazing to see Android 11 on such an "old" device!
regards, Andy
@nift4 Are you still working on kernel 4.9?
xenondroid said:
@nift4 Are you still working on kernel 4.9?
Click to expand...
Click to collapse
Yes. Jarl & wiktorek140 made it work near to perfect on montana and I am trying my best to replicate that on cedric. Jarl said he will only bringup 4.9 ports to LineageOS 19...
Flashed this to replace Mint 2.1 no problems. Even the Seedvault backup worked. Battery seems to last longer too. One strange thing I'm experiencing since I flashed Stellar is that whenever I reboot my phone I get 5 text messages within a couple of minutes from O2 (my mobile network operator) saying my number doesn't support Visual Voicemail. I've never used Visual Voicemail it in the past, wonder why I'm getting these messages?
Thanks
doug888 said:
I've never used Visual Voicemail it in the past, wonder why I'm getting these messages?
Click to expand...
Click to collapse
Probably because it's enabled by default in Android 11. You can disable it in Dialer settings, I think.
Thanks! That worked
Hi,
Thank you for your work !
My questions may be slightly off-topic... and from a newbie but I am wondering why SafetyNet is OK on this ROM (checked with an application, without Magisk installed) BUT some applications still refuse to work or complain :
- WhatsApp just warns my device is not supported
- HID Approve (an MFA auth. app) refuses to run
- My banking app refuses to enable basic features at launch
What kind of checks have been implemented within these applications (are they well-known ?) and is there a way to workaround these issues ?
Otherwise, I could relock my bootloader and reinstall Oreo Stock but I tried many times a few months ago and never managed to do it without losing my IMEIs (I have not done EFS backups before installing MintOS...). Any suggestion to make this work without buying another phone ?
Thank you !
LineageOS 20.0 for Sony Xperia XZ1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
RELEASE
This is an alternative ROM for the Sony Xperia XZ1, offering several privacy features.
Please report any issues you observe apart from the ones listed below. Logs are needed for me to fix anything (preferably dmesg and logcat).
DOWNLOAD
You can download the latest releases here:
poplar (G8341):
https://sourceforge.net/projects/yoshino/files/poplar/twrp/
https://sourceforge.net/projects/yoshino/files/poplar/lineage-20.0/
poplar_dsds (G8342):
https://sourceforge.net/projects/yoshino/files/poplar/twrp/
https://sourceforge.net/projects/yoshino/files/poplar/lineage-20.0/
poplar_canada (G8343):
https://sourceforge.net/projects/yoshino/files/poplar/twrp/
https://sourceforge.net/projects/yoshino/files/poplar/lineage-20.0/
poplar KDDI (SOV36)
https://sourceforge.net/projects/yoshino/files/poplar/twrp/
https://sourceforge.net/projects/yoshino/files/poplar/lineage-20.0/
RECOMMENDED GAPPS (others works too)
https://androidfilehost.com/?w=files&flid=322935
INSTALLATION
Before first install: flash and boot into the TWRP provided in this thread, format data, reboot to recovery and wipe all internal partitions, then flash the ROM, GApps and root (if needed).
Note: There is not going to be a LOS su addon anymore. If you need root, flash a root manager of your choice. No guaranteed support from LOS for this.
When updating from previous builds, simply dirty flash the ROM is enough, decryption in new TWRP works now
Recommended GApps: MindTheGapps provided in this thread.
KNOWN ISSUES
Stock camera is not working anymore due to incompatibility of stock library (libimageprocessorjni.so) with new libgui
Currently, LOS isn't feature complete yet, so some things, buttonn, advanced menù etc. may be still missing
You tell me...
Contributors
derf elot, modpunk, Rooted_Ansh
Source Code
poplar: https://github.com/whatawurst/android_device_sony_poplar
poplar_dsds: https://github.com/whatawurst/android_device_sony_poplar_dsds
poplar_canada: https://github.com/whatawurst/android_device_sony_poplar_canada
poplar_KDDI: https://github.com/whatawurst/android_device_sony_poplar_kddi
kernel: https://github.com/whatawurst/android_kernel_sony_msm8998
Rom Information
ROM OS Version: Android 13
ROM Kernel: Linux 4.4
Version Information
Status: Stable
Current Stable Version: 1.2
Stable Release Date: 2023-05-06
ALL CREDITS TO DERF ELOT AND THE OTHER DEVS BEHIND THE ROM, I'M ONLY POSTING IT.
---------------------------------------
Changelogs:
v1.2 (2023-05-10):
- Updated to T QPR2 release (LineageOS upstream)
- Updated to May 2023 Security updates (both ROM and kernel)
- Our kernel now includes updates by CIP and is up-to-date with tag st40 - thanks also to Flamefire for help with some of these (1)
- Reduced zram size to 25% (1gb) of out total RAM to have more to use freely
- Updated BT stuff for QPR2 (maybe offloading is working again? needs confirmation)
- Added the option to reflash the mbn via OpenCS (see Xperia Parts) - thanks also to shank03 & Flamefire (2)
- Fully enabled IMS on Congstar Germany via overlay on lilac
- Possibly some battery/performance optimizations here and there
- Fixed Android Auto support
- Added new LineageOS "Charging control hal" for battery charging care (3)
- Maybe more I forgot...
(1) The CIP kernel includes fixes for issues and security vulnerabilities from 4.14 kernel (see https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git)
(2) A somehwat lengthy explanation: This option is off by default on fresh installs. When upgrading, this should be enabled because we enforced this for everybody previously. However, this option is only required for certain carrier mbns that enable IMS. Personally, I know that the O2/Telefonica Germany mbn needs this, otherwise you get a crashing modem at every boot (unless you switch to 3g before rebooting and back to LTE after boot). I generally recommend playing with this option, and if you don't need it (e.g. modem doesn't crash on boot), just keep it off - like mentioned before, this is now the default behavior of OpenCS on fresh installs anyway.
(3) This is not finalized or merged upstream is LineageOS yet, but seems like a nice feature to have and test drive already. Some bugs may be possible.
v1.1 (2023-01-08):
Updated to T QPR1 release (LineageOS upstream)
New default camera app (LineageOS upstream) - yes, we cannot change video fps currently (thanks Sony!)
Any other updates by LineageOS upstream
Kernel security updates (also thanks to Flamefire)
Dropped keyprovd service - it is useless on unlocked BL anyway
Show 4G instead of LTE icon - saves some space too
Enable IMS by default - this still only works if carrier is supported
Fix some selinux denials (also thanks to Flamefire)
Fixup ViLTE dependencies - this might in theory work again, but it's not enabled yet
v1.0 (2022-10-02):
Initial release
Can’t wait to try it !!! Thanks tux
Can i flash this using old twrp version like 3.6.2 - 9?
The rom is great but every time the device reboots and finishes the boot animation it repeats one more time boot animation.
According to the picture, I can't scroll down as usual, can only use those 4 buttons @@ until rebooting (I had landscape rotation to watch youtube then rotate the screen again when the video ends and it's like that
).
rarely but the sound doesn't play even if i keep the volume high or switch to listening to music or watching youtube until the device is restarted
(sorry if I said wrong or wrong grammar, I'm not very good at English. )
raffyei8ht said:
Can i flash this using old twrp version like 3.6.2 - 9?
Click to expand...
Click to collapse
No idea, but for internal memory decription the new one is needed.
Tux111 said:
No idea, but for internal memory decription the new one is needed.
Click to expand...
Click to collapse
What is the use of internal decription if you don't mind me asking
raffyei8ht said:
What is the use of internal decription if you don't mind me asking
Click to expand...
Click to collapse
By default android protect (encrypt) your internal memory. TWRP lacked decryption for a long time, now its supported. This means, with new recovery, you can see and manage your internal memory via TWRP using your lockscreen password. Before, you simply can't.
The fingerprint sensor doesn't work, auto brightness is also not working, does anyone know how to fix it
Each time I reinstalled a rom, some function which worked just fine on that rom stopped functioning, do you guys know how to prevent this
This is a very good ROM. Good for daily use. Didn't encounter any problem. Can't wait for the Pixel Experience Android 13.
ecrissor said:
The fingerprint sensor doesn't work, auto brightness is also not working, does anyone know how to fix it
Click to expand...
Click to collapse
FP perfectly working.
ecrissor said:
Each time I reinstalled a rom, some function which worked just fine on that rom stopped functioning, do you guys know how to prevent this
Click to expand...
Click to collapse
I guess you have some missing files or something like that. Try reflashing stock rom and persist.img, something wrong with your files.
Maybe this is a dumb question, but what is the difference between the twrp provided here and the 'stock' twrp from twrp.me? Will both work?
Nice room
great work
poplar_dsds said:
Maybe this is a dumb question, but what is the difference between the twrp provided here and the 'stock' twrp from twrp.me? Will both work?
Click to expand...
Click to collapse
Both works but this one should be able to decrypt internal memory. No idea if the one from twrp.me does the same or if its the same file.
Tux111 said:
Both works but this one should be able to decrypt internal memory. No idea if the one from twrp.me does the same or if its the same file.
Click to expand...
Click to collapse
Okay i see, thank you! I updated to your version of twrp and dirty flashed the rom from 19.x to this version, worked great, even with apps and so on!
Also thanks for the ROM!
Hi there,
I'm a complete noob on XDA, but I just flashed this TWRP (twrp-3.6.2_12-0-20221002-poplar) over another TWRP (twrp-3.7.0_9-0-poplar) and now, when entering recovery mode I get stuck in loading screen of teamwin Recovery Project 3.6..2_12-0
I can get out of loading screen by pressing all buttons, and device turns off.
I rebooted into fastboot and flashed back the 3..7 TWRP and now things are back to normal.
Any sugestions on what I can do to install this TWRP?
xdatomsgmail said:
Hi there,
I'm a complete noob on XDA, but I just flashed this TWRP (twrp-3.6.2_12-0-20221002-poplar) over another TWRP (twrp-3.7.0_9-0-poplar) and now, when entering recovery mode I get stuck in loading screen of teamwin Recovery Project 3.6..2_12-0
I can get out of loading screen by pressing all buttons, and device turns off.
I rebooted into fastboot and flashed back the 3..7 TWRP and now things are back to normal.
Any sugestions on what I can do to install this TWRP?
Click to expand...
Click to collapse
So, I was able to install lineage-20.0-20221002-UNOFFICIAL-1.0-poplar.zip from this post using TWRP 3.6..2_12-0, without problems.
Did not try to flash twrp-3.7.0_9-0-poplar again.
Is there a thread with future requests? I would like the default browser not to default to google, as the whole point for me is to de-google my phone.
Hi, so I've been absent from Custom Roms for the last couple years - since I got my XZ1 and the DRM key extraction was too much of a hassle for me as I didn't miss much from the stock rom.
Since I got some spare time over the years I was thinking to finally tackle that topic, but I have two questions:
1) The opening post says this
Tux111 said:
Stock camera is not working anymore due to incompatibility of stock library (libimageprocessorjni.so) with new libgui
Click to expand...
Click to collapse
is it even still relevant for me to back up my DRM keys / back up the TA partition if I don't want to go back to stock? what camera are you using then? is the quality comparable? is slow motion still possible?
2)
i know that in the past, safety net checks were just looking for bootloader / root, but they changed to checking if the ROM is signed with a proper signingkey, right? is this rom signed with a non-test-key?
I've got a couple of banking apps on my phone and it would obviously prevent it from being a daily driver if they were not supported anymore :/
Thanks in advance!
New LOS Update 1.1 is here! Enjoy!
xdatomsgmail said:
So, I was able to install lineage-20.0-20221002-UNOFFICIAL-1.0-poplar.zip from this post using TWRP 3.6..2_12-0, without problems.
Did not try to flash twrp-3.7.0_9-0-poplar again.
Is there a thread with future requests? I would like the default browser not to default to google, as the whole point for me is to de-google my phone.
Click to expand...
Click to collapse
By default the browser isn't Google Chrome afaik, so i don't see the problem. Also, tbh, this makes no sense considering Android=Google. Chromium is builded inside the ROM,is part of the ROM,so once you install Android, you are installing something from Google. So i don't get it.
If you don't install gapps, then you don't have Chrome as default browser. Otherwise, flash gapps and remove Chrome.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS GitHub repo. And if you would like to contribute to LineageOS, please visit Gerrit Code Review.
Click to expand...
Click to collapse
MUST-READ BACKGROUND - Android 13 and the two approaches:
As some of you already know, due to various reasons, @phhusson , who kickstarted the GSI trend and committed to it over the years, is backing out from future development - there won't be any AOSP 13+ builds or patches directly from him. He did most of the heavylifting for fixing bugs and implementing features, and selflessly supported more than his AOSP GSIs and more than devices he own. For the situation of GSIs today, we owe him a big thank-you.
Since PHH made up his mind, a number of existing builders incl. myself have formed the TrebleDroid organization, with PHH himself helping us in technical issues. TD will forward-port PHH's final patches (v415) onto Android 13 and attempt to fix new issues. This is still a new and ongoing process, but if done right, will have compatibility and feature-completion on par with past PHH-based GSIs.
Meanwhile, I'm aware that at least I myself am not as capable as PHH, and won't be able to look after the myriad of patches and devices, esp. legacy ones (pre-A10). Therefore, inspired by @PeterCxy , I'm taking a different approach - start over from AOSP's generic gsi_* target, add in the minimum amount of fixes needed for my own devices, shaking off much of the legacy burden in the process and making it easier for myself to follow/maintain. This is a radical, selfish approach that by definition won't work for legacy devices anymore, and won't work as well as PHH-based GSIs that you've come to love either. However, I've fixed it up to my own daily-driver standards, and I figured it should still be of use to many. For now, I call this the "light" approach.
Disclaimer:
No flashing instructions will be offered. If you're here in this forum, you should know what you're doing.
No guarantees that everything would work. This is a GSI, bugs are bound to happen.
The selfish nature of this approach means I can and will ignore certain bugs as I see fit. Deal with it or kindly go try something else.
Download:
https://sourceforge.net/projects/andyyan-gsi/files/
Scroll down for the naming rules of variants.
Compressed as .xz archives - extract first.
Stuff on GitHub (builders-only):
Most things should be self-explanatory. Not the cleanest code, but should help if you need some clues.
lineage_build_unified - my unified script for building
lineage_patches_unified - my unified patches for building
device_lineage_gsi - my device tree that extends native generic targets
Thanks to:
The LineageOS team - helping me out even when they don't offer GSIs themselves
@phhusson - shaped the treble community, and even the "light" approach uses his fixes/infra extensively
@PeterCxy - inspired me with his personal-use GSI, and coded critical fixes such as sysbta
...and more
Donate?
https://paypal.me/AndyCGYan
This post documents my progress on top of the native generic targets.
Already implemented/fixed:
Built-in root (PHH-SU)
Device overlays
Screen resolution & refresh rate - improved upon PHH's implementation
Alternative audio policy (Qualcomm)
Disable soundvolume effect (Qualcomm)
Alternative backlight scale (MediaTek)
resetprop/copyprop tool
In-call audio
BT audio
VoLTE on Qualcomm/MediaTek pre-S vendors
VoLTE on Qualcomm/MediaTek S vendors - new, backported to PHH-based
GAPPS - using MindTheGapps for now
Securized - "on-demand" reversible toggle
Disable A2DP offload
Alternative audio jack detection
Signature spoofing - limited to priv-app for the same security reason as in PHH/TD-based
Optional FP lockout (set persist.sys.fp.lockouts.disable to true to disable timeout on failed FP attempts)
Built-in PHH-SU app for *S variant
Override minimum brightness
Override navbar availability
Exfat
In-call audio on Snapdragon 8 Gen 2 (SM8550) and newer Qualcomm devices
To be implemented/fixed at a later time:
VoLTE on Motorola Qualcomm S vendors - situation did not improve with stock T, lowering priority
Known but will not implement/fix:
Compatibility with legacy (pre-A10) devices, A-only, VNDKLite
FOD/UDFPS (commonly known as in-display fingerprint) - not skilled enough for it and not interested either
MediaTek kernel BPF bug (#9)
VoLTE on non-Qualcomm/MediaTek vendors
Samsung/Huawei oddities
Notes:
I now have a rather taxing day job, and can't devote nearly as much time/effort into this as I did as a student, or even a year ago.
No A-only or VNDKLite builds. These are concepts that don't exist natively.
GAPPS builds are offered as-is without guarantees. As a Chinese I can't/won't help with GAPPS/SN issues - please help each other out.
ADB is intentionally insecure, even on first boot (turned on by default and no authentication needed). GSIs are more fragile compared to device-specific custom ROMs, both on first boot (no-boot issues) and on subsequent boots (after tuning certain Treble settings), and I insist that no-auth ADB is a must-have for debugging and general fail-safe.
Signature spoofing (MicroG) is supported, but only for priv-apps. This is a security consideration from PHH.
Refer to #9 for explanation/workaround of an MediaTek-specific kernel bug that causes no internet.
TD-based LOS20 will be offered as well, but at a later date - I've only made a first test build of it today. At its current state though, it doesn't work as well as PHH-based A12 either, so don't get your hopes up too high.
Good job!
Yay!!!
yay!!!! thank you!!!!
Thank you very much for your great work. I've been waiting for this for a long time.
I ran into a very, very strange bug.
I have a Qin F21PRO (MT6761).
This model has two sub-models:
4GB RAM + 64GB storage
3GB RAM + 32GB storage.
My device is
4GB RAM + 64GB storage
But after flashing this GSI, it is shown that there is only 32GB storage.
edit: after factory reset via twrp, i getting 64GB storage
There's a known kernel bug in some recent MTK devices that breaks BPF badly, resulting in broken networking features since Android 13, and no-boot since r11 (Google decided to tighten the check). I've reverted the no-boot, but the actual bug can't be fixed from platform-side.
This affects LOS in that it has Restricted Networking Mode turned on by default, and with the bug in place, apps cannot be added to the allow list, resulting in no internet in even system apps.
If you own an MTK device and notice such a thing, as a temporary workaround, you can turn the feature off manually with:
Code:
adb shell settings put global restricted_networking_mode 0
If you're on the gN variant, SetupWizard would also have no internet, so just skip the setup entirely, turn on USB Debugging once you're in the OS, run the above, then re-initiate the setup from the status bar.
As for a more persistent fix - thanks to @Rortiz2 , there's now a way to manually patch the kernel binary, however I no longer have an affected device for testing this. Feel free to try out the patcher here.
There might be other broken networking features that I'm unaware of. In the long term, the one true solution is to upgrade to a newer vendor base, hoping that the OEM has merged the kernel-side fix.
AndyYan said:
TD-based LOS20 will be offered as well, but at a later date - I've only made a first test build of it today. At its current state though, it doesn't work as well as PHH-based A12 either, so don't get your hopes up too high.
Click to expand...
Click to collapse
There is no Navigation key or gesture options, How to do it?, I can install it on my Samsung device but without navigation, no home/back key
redymedan said:
There is no Navigation key or gesture options, How to do it?, I can install it on my Samsung device but without navigation, no home/back key
Click to expand...
Click to collapse
Ugh, a Samsung oddity. I didn't implement the force overide switch - if a non-Samsung hits this as well, I might.
If you know how to, try adding "qemu.hw.mainkeys=0" to /system/build.prop. These images are EXT4 unshared blocks, so as long you have verity disabled and root, you should be able to edit/save it.
redymedan said:
There is no Navigation key or gesture options, How to do it?, I can install it on my Samsung device but without navigation, no home/back key
Click to expand...
Click to collapse
AndyYan said:
Ugh, a Samsung oddity. I didn't implement the force overide switch - if a non-Samsung hits this as well, I might.
If you know how to, try adding "qemu.hw.mainkeys=0" to /system/build.prop. These images are EXT4 unshared blocks, so as long you have verity disabled and root, you should be able to edit/save it.
Click to expand...
Click to collapse
Same problem with Redmi Note 10 (mojito)
@redymedan @spider1163 Can you give me the full result of "getprop" from shell? Paste it to e.g. Pastebin.
D
AndyYan said:
Ugh, a Samsung oddity. I didn't implement the force overide switch - if a non-Samsung hits this as well, I might.
If you know how to, try adding "qemu.hw.mainkeys=0" to /system/build.prop. These images are EXT4 unshared blocks, so as long you have verity disabled and root, you should be able to edit/save it.
Click to expand...
Click to collapse
Done! I just added "qemu.hw.mainkeys=0" to /system/build.prop and the navigation keys enabled. also in Gesture menu "System navigation" option appeared. It works now on my Galaxy A50, Thanks
Other problem: Google Play Protect certified "This device isn't Play Protect certified"
amazing! waiting for gapps variant now.
redymedan said:
Done! I just added "qemu.hw.mainkeys=0" to /system/build.prop and the navigation keys enabled.
Click to expand...
Click to collapse
Thanks for confirming it's that simple! Given that "light" won't look back on legacy devices, I think I'll just enable this prop globally in the next releases.
This is exactly what I was waiting for, it will be fun to test on my old Huawei P smart 2019 with Android 9 vendor so let's see what happens. Any result of this experiment will be shared here.
THX for your great work.
But how can I install gapps?
I've tried to install BitGApps with Magisk as a Magisk module, but it says 'insufficient partition size'.
There's no working TWRP for my device
michael_hamada said:
THX for your great work.
But how can I install gapps?
I've tried to install BitGApps with Magisk as a Magisk module, but it says 'insufficient partition size'.
There's no working TWRP for my device
Click to expand...
Click to collapse
you wait... ..
THX for your great work. but auto brightness not working Is this expected behavior?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DivestOS is a more private and more secure aftermarket system.
(normally I only make threads for devices known fully working, however making this thread to replace an unofficial and improper thread)
Poco F1 Notes:
- camera does not work on these builds due to a longstanding incompatibility with the kernel changes made
a workaround is to flash an official LineageOS boot.img, however that negates all of the kernel security patches and hardening
if anyone technical can help bisect the changes that would be much appreciated
help to compile and what to change can be provided as needed
Features:
- strong focus on FOSS
- various system hardening
- various privacy enhancements
- automated removal of unnecessary proprietary blobs
- automated kernel hardening and CVE patching
- ability to relock bootloader on supported devices
- verified boot on supported devices
- no root support
- SELinux always enforcing
- encrypted by default
- monthly updates
- OTA delta updates
- OTA updates over Tor (optional)
- F-Droid included
- hardened system WebView with rapid updates: https://divestos.org/misc/ch-dates.txt
Extra Features (not installed by default & also compatible with all systems):
- Mull, our hardened fork of Fenix with rapid updates: https://divestos.org/misc/ffa-dates.txt
- Hypatia, our real-time malware scanner
- Extirpater, our free space eraser
Links:
- Website: https://divestos.org
- Onion: http://divestoseb5nncsydt7zzf5hrfg44md4bxqjs5ifcv4t7gt7u6ohjyyd.onion
- Downloads: https://divestos.org/index.php?page=devices&base=LineageOS#device-beryllium
- Changelogs: https://divestos.org/index.php?page=news
- Project History: https://divestos.org/index.php?page=history
- Known Issues: https://divestos.org/index.php?page=broken#beryllium
- Screenshots: https://divestos.org/index.php?page=screenshots
- Security Patching Overview: https://divestos.org/index.php?page=patch_levels
- About + Credits + Notices: https://divestos.org/index.php?page=about
- Donate: https://divested.dev/donate
- Source Code: https://github.com/divested-mobile or https://gitlab.com/divested-mobile
- XMPP Chat Room: xmpp:[email protected]
Device Specific Links:
- Device Tree: https://github.com/LineageOS/android_device_xiaomi_beryllium, https://github.com/LineageOS/android_device_xiaomi_sdm845-common
- Kernel: https://github.com/LineageOS/android_kernel_xiaomi_sdm845
- Kernel CVE Patches Applied: https://gitlab.com/divested-mobile/.../CVE_Patchers/android_kernel_xiaomi_sdm845.sh, https://gitlab.com/divested-mobile/.../CVE_Patchers/android_kernel_xiaomi_sdm845.sh
Other Bits:
- Good and bad feedback is welcomed. Else how can we improve?
- If you find a bug, please report it below or via GitHub/GitLab.
- Testing/Translations/Code contributions are gratefully appreciated.
Important Notes for New Users:
- Please make a backup of your device and copy it to another computer.
- You must wipe before installing this OS.
- This OS has userdata encrypted by default
- You are intended to relock your bootloader with this OS (if your device is marked supported for that).
DivestOS does *not* support the following:
- Google Apps (OpenGAPPS)
- DRM (Widevine)
- alternative recoveries (TWRP)
- root (Magisk)
- runtime modification frameworks (Xposed or theme engines)
All downloads are GPG signed with the following key:
Code:
#B874 4D67 F9F1 E14E 145D FD8E 7F62 7E92 0F31 6994
-----BEGIN PGP PUBLIC KEY BLOCK-----
mDMEXupIxBYJKwYBBAHaRw8BAQdAC1RiTvrqJaAQ4FIHsxX+gzEgdT4mspISS+p0
y847Nge0SERpdmVzdE9TIFJlbGVhc2UgU2lnbmluZyAoMjAyMCAjMSkgPHN1cHBv
cnQrcmVsZWFzZXNpZ25pbmdAZGl2ZXN0b3Mub3JnPoiQBBMWCAA4FiEEuHRNZ/nx
4U4UXf2Of2J+kg8xaZQFAl7qSMQCGwMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AA
CgkQf2J+kg8xaZR1BgEAwwLVVsG7kbp8M3GTV987XpVl5cZeTtDc/g+66briCHUB
APiuH/dk8eRnhFnq4Up2/j7uD/8FtSvxPbHiz6t1MdgB
=VzP2
-----END PGP PUBLIC KEY BLOCK-----
SkewedZeppelin said:
Poco F1 Notes:
- camera does not work on these builds due to a longstanding incompatibility with the kernel changes made
a workaround is to flash an official LineageOS boot.img, however that negates all of the kernel security patches and hardening
if anyone technical can help bisect the changes that would be much appreciated
help to compile and what to change can be provided as needed
Click to expand...
Click to collapse
Probably something with hardening broke it?
I tag @Pierre2324 and @REIGNZ3 which maintain their own kernels, if they have some spare free time beside their own projects, to take a look and help with info if possible.
Retrial said:
Probably something with hardening broke it?
Click to expand...
Click to collapse
perhaps, the camera isn't broken on any other device with the same changes and I spent many hours sanity check the changes that are applied to it
even overhauled a lot of the CVE patcher in hopes it'd fix it: https://divestos.org/index.php?page=news#2022-03.2
it is a weird outlier
SkewedZeppelin said:
perhaps, the camera isn't broken on any other device with the same changes and I spent many hours sanity check the changes that are applied to it
even overhauled a lot of the CVE patcher in hopes it'd fix it: https://divestos.org/index.php?page=news#2022-03.2
it is a weird outlier
Click to expand...
Click to collapse
camera: fix new version · LineageOS/[email protected]
Opensource base V11.0.0.1 , but not anyone update More people get V11.0.5.0 stable,and Dev version Change-Id: I6903fe7026c16e47c8cd7c9af1169404f50bca59
github.com
Ever tried reverting this?
REIGNZ3 said:
camera: fix new version · LineageOS/[email protected]
Opensource base V11.0.0.1 , but not anyone update More people get V11.0.5.0 stable,and Dev version Change-Id: I6903fe7026c16e47c8cd7c9af1169404f50bca59
github.com
Ever tried reverting this?
Click to expand...
Click to collapse
Thanks I'll pull it into next update and see if it goes, but given the LineageOS kernel is known working I'm confident it is something I broke.
SkewedZeppelin said:
Thanks I'll pull it into next update and see if it goes, but given the LineageOS kernel is known working I'm confident it is something I broke.
Click to expand...
Click to collapse
I know this is time consuming but If you have time, add your sauce to kernel one by one, give for testing each time and see what change result to break the camera
Retrial said:
I know this is time consuming but If you have time, add your sauce to kernel one by one, give for testing each time and see what change result to break the camera
Click to expand...
Click to collapse
@SkewedZeppelin or you can try something like "binary search": apply 50% of patches. In case of no luck, apply other part. For else, divide problematic part again (to apply 50% from this patches). And so on... Anyway, thanks for great ROM!
Hi) Today you have updates on the conventions but I don't see our beryllium (it is no longer supported?
Morillio said:
Hi) Today you have updates on the conventions but I don't see our beryllium (it is no longer supported?
Click to expand...
Click to collapse
The January update is currently uploading. I do not drop devices without announcement.
You can either wait a few hours for the upload to finish or download the last build from here: https://divestos.org/builds/old/old.txt
next day edit: they've been up for a while: https://divestos.org/index.php?page=news#2023-01
Thanks for the reply)) I'll wait!
Anyone currently using this custom rom?
ushilives said:
Anyone currently using this custom rom?
Click to expand...
Click to collapse
> Updater checks past 4 days: 93
Hello there! In your rom there is no support wifi 5.0 frequency? in the settings only 2.4( Tell me I don't see it or it is not there?
Morillio said:
Hello there! In your rom there is no support wifi 5.0 frequency? in the settings only 2.4( Tell me I don't see it or it is not there?
Click to expand...
Click to collapse
you don't see any 5GHz networks at all? or just some? they may have country code mismatched?
SkewedZeppelin said:
you don't see any 5GHz networks at all? or just some? they may have country code mismatched?
Click to expand...
Click to collapse
I'm Talking about hotspot band 5.0 gHz support
Morillio said:
I'm Talking about hotspot band 5.0 gHz support
Click to expand...
Click to collapse
Oh. The Wi-Fi hotspot will default to 5GHz. To use 2.4GHz check the "Extend compatibility" option.
SkewedZeppelin said:
Oh. The Wi-Fi hotspot will default to 5GHz. To use 2.4GHz check the "Extend compatibility" option.
Click to expand...
Click to collapse
I have in the hotspot no switch band 5.0 / 2.4
The option is right there in your first screenshot.
5GHz is the default.
The "Extend compatibility" toggle is used to switch from 5GHz to 2.4GHz.
SkewedZeppelin said:
The option is right there in your first screenshot.
5GHz is the default.
The "Extend compatibility" toggle is used to switch from 5GHz to 2.4GHz.
Click to expand...
Click to collapse
I'm sorry, but no. On the connected device shows that the network 2.4 band