Database Develop

ROM: Sony AOSP 8.1 (H3113) (unofficial)

{
"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"
}
Sony AOSP project​
Disclaimer
I'm not liable for anything YOU do to YOUR device, YOU are doing it and it's YOUR device.
What is it?
It's a project developed and maintained by Sony Xperia Developers team.
You can get more informations here: https://developer.sony.com/develop/open-devices/
Can I build it by myself?
Sure, just follow these instructions and have patience!
What works and what doesn't?
According to this official page, almost everything seems to be fine.
How can I flash it?
Follow these steps:
Unlock the bootloader (this will erase your data and will void warranty): https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
Setup fastboot on your PC (there are many guides for this step)
Download and unpack the zip archive
Open a shell into the folder containing unpacked files
Run these commands:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash userdata userdata.img (it’s not necessary to flash userdata every time)
Download and unpack the corresponding vendor image from here: https://developer.sony.com/develop/open-devices/downloads/software-binaries
Open a shell into the folder containing unpacked image
Run this command:
fastboot flash oem SW_binaries_for_Xperia_xxxxx.img (where "xxxxx" varies depending on the file)
(optional) In case you want to flash GApps, Magisk or other mods, you can use TWRP: https://forum.xda-developers.com/xa2-ultra/development/recovery-twrp-3-2-1-0-touch-recovery-t3774193
Reboot the device and enjoy!
Download link
You can get the builds from my AFH folder: https://androidfilehost.com/?w=files&flid=269497.
I haven't done any change to Sony's source code, these are vanilla builds.
Credits
All credits go to Sony and Google.
XDA:DevDB Information
Sony AOSP, ROM for the Sony XA2 Ultra
Contributors
axxx007xxxz
Source Code: https://github.com/sonyxperiadev
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Testing
Created 2018-05-08
Last Updated 2018-05-08

Reserved
NOTE: I'm in no way associated with Sony, these are unofficial builds and are made for pesonal usage.
Also, these builds are untested so I can't assure they're going to work!

Reserved 2
Post reserved for future usage.

Reserved 3
Post reserved for future usage.

Reserved 4
Post reserved for future usage.

New build
Build informations:
Build type: userdebug
Android revision: android-8.1.0_r20
CAF revision: LA.UM.6.4.r1
Last commit of sonyxperiadev/local_manifests: 81032020581dd636ab9d7f8414609bad07332288
Last commit of sonyxperiadev/kernel: 1df958f2943c6c5cae31018e42d2f42e8a55c4b3
Last commit of sonyxperiadev/device-sony-nile: c775da101d57377979cdcb79b1ba1b5bbd3739a4
Last commit of sonyxperiadev/device-sony-pioneer: 5b804c4aa86ca13653d2d692120437fa76f61ae9.
Download link: https://androidfilehost.com/?fid=818222786056029296.

It always says "There's an internal problem with your device" after booting up. It's kinda annoying.
And it also does not accept my Samsung microSD card formatted on stock ROM and wants me to format it. I'm backing it up, and will try to format it later.
Fingerprint aslo does not work, but I'm fine with that at the moment.
If someone needs to know, I have H4113 (dual-sim variant of regular XA2).

Casserole said:
It always says "There's an internal problem with your device" after booting up. It's kinda annoying. And it also does not accept my Samsung microSD card formatted on stock ROM and wants me to format it.
Click to expand...
Click to collapse
Just information: I have the H3223 not H3213, and haven't tried to flash this, but on the Google Pixel (8.1) with at least some custom kernels and some versions of Magisk, the same "There's an internal problem with your device" when you boot up, but other than possibly having your phone screen on longer than it should, there are no actual problems on the Pixel. Could be for the same reason(s), whatever those reasons are. I'm not positive but I think that more recent versions of Magisk might not cause that message anymore. I use an old version of Magisk, but in my case the Pixel custom kernel I use causes that, too.

roirraW "edor" ehT said:
I'm not positive but I think that more recent versions of Magisk might not cause that message anymore. I use an old version of Magisk, but in my case the Pixel custom kernel I use causes that, too.
Click to expand...
Click to collapse
I haven't flashed any magisks at the moment, so I don't think the problem are caused by it. But thanks anyway for the reply.

Casserole said:
I haven't flashed any magisks at the moment, so I don't think the problem are caused by it. But thanks anyway for the reply.
Click to expand...
Click to collapse
You're welcome! I'm not suggesting that you flashing Magisk or anything is the cause of this on this ROM, it's just related to changes in Android 8.1 and that it doesn't really necessarily mean there's something wrong. I'm sure there are ways around it, but since I'm not a developer and I don't know what triggers it, I don't know.

Is fingerprint scanner not working for everyone or it is not working only for those with a fingerprint scanner made by a a different hardware maker?

tombassi said:
cool down dude !! XDA is not the correct please for these bad words. if you don't know what you are doing that is not the Developer fault and if you need no bugs stay with the stock ROM.
Click to expand...
Click to collapse
Thanks! With "almost everything seems to be fine", I meant that most of the main parts (should) work.
Camera is a known problem on Sony devices due to DRM keys getting erased on bootloader unlock.
Casserole said:
It always says "There's an internal problem with your device" after booting up. It's kinda annoying.
And it also does not accept my Samsung microSD card formatted on stock ROM and wants me to format it. I'm backing it up, and will try to format it later.
Fingerprint aslo does not work, but I'm fine with that at the moment.
If someone needs to know, I have H4113 (dual-sim variant of regular XA2).
Click to expand...
Click to collapse
The SD card problem could be related to your phone being dual SIM: as the title says, these builds are for H3113 (single SIM variant).
You can try to set dual SIM properties in build.prop (you can do it with an app like this or a text editor if you have root access, otherwise I think it's doable through TWRP too):
Code:
persist.multisim.config=dsds
persist.radio.multisim.config=dsds
ro.telephony.default_network=9,1
then reboot the phone and test.
These come directly from H4113 makefile, I can't assure you everything will be fine after this, but you can give it a try.
As per the fingerprint, it's currently broken on all variants, I'm sorry.
mirco_pa said:
Is fingerprint scanner not working for everyone or it is not working only for those with a fingerprint scanner made by a a different hardware maker?
Click to expand...
Click to collapse
Sony website reports it as currently not working on AOSP, I'm sorry.

axxx007xxxz said:
The SD card problem could be related to your phone being dual SIM: as the title says, these builds are for H3113 (single SIM variant).
You can try to set dual SIM properties in build.prop (you can do it with an app like this or a text editor if you have root access, otherwise I think it's doable through TWRP too):
Click to expand...
Click to collapse
I think SD card problem was related to something else, because it started working after reformatting.
But there were also problems with SIM card, it worked on first boot, but after removing and inserting it again device shown that there were no signal, so your solution may be helpful in this situation. I can't test it due to limited amount of time, though.

New build
Build informations:
Build type: userdebug
Android revision: android-8.1.0_r26
CAF revision: LA.UM.6.4.r1
Last commit of sonyxperiadev/local_manifests: 1c992d7f3f2ef8d0b53397e23227e10489e40bec
Last commit of sonyxperiadev/kernel: ab6fd5b1a4126cfdd4391eefe8eba17eb6626781
Last commit of sonyxperiadev/device-sony-nile: 7d57c76da9ce47849429347e77e013781e63db2f
Last commit of sonyxperiadev/device-sony-pioneer: 5b804c4aa86ca13653d2d692120437fa76f61ae9.
Download link: https://androidfilehost.com/?fid=890278863836285554.

Can you build one for H4113? You shood have files for it too

Thanks axxx007xxxz for sharing these builds! They helped me recover Android on my completely wiped h3113 pioneer. Both the 8.0 and 8.1 build work for me. Downloading them to my PC was the hardest part, for some reason the download often fails.
I still have a couple of questions about these Sony AOSP builds that maybe you can answer:
1. Do you know what the Sony software binaries* do? I have flashed them on my device a couple of times, but I don't see anything added.
2. What is the difference between build type "userdebug" and "eng"?
3. If I use this build, how would you recommed I update it? Is the only way to flash in fastboot? (Like step 6 in Sony's guide**?)
Thank you!
roirraW "edor" ehT said:
Just information: I have the H3223 not H3213, and haven't tried to flash this, but on the Google Pixel (8.1) with at least some custom kernels and some versions of Magisk, the same "There's an internal problem with your device" when you boot up, but other than possibly having your phone screen on longer than it should, there are no actual problems on the Pixel. Could be for the same reason(s), whatever those reasons are. I'm not positive but I think that more recent versions of Magisk might not cause that message anymore. I use an old version of Magisk, but in my case the Pixel custom kernel I use causes that, too.
Click to expand...
Click to collapse
I get the same error message right after booting, also without root. It's annoying, but I guess I can live with it.
P.S. As I'm a new user, I cannot use links yet. Please use these footnotes instead:
*: https[colon]//developer[dot]sony[dot]com/develop/open-devices/downloads/software-binaries
**: https[colon]//developer[dot]sony[dot]com/develop/open-devices/guides/aosp-build-instructions/build-aosp-nougat-8-1-oreo-4-4/#tutorial-step-6

1. parts of android which are closed source, graphics driver for example. you won't see them.
2. eng should give you more debugging options, like working adb logcat without enabling developer options which is sometimes needed while you're porting android to new device and there's just black screen on the phone for example. correct me if i'm wrong.
3. flashing worked through twrp for me but i had to build unsingned zip.
regarding the internal problem message, just ignore it.

davidhozic said:
Can you build one for H4113? You shood have files for it too
Click to expand...
Click to collapse
Checking H4113 makefile, I don't see big differences except for a few properties: https://github.com/sonyxperiadev/device-sony-pioneer/blob/master/aosp_h4113.mk#L18-L22; you can try to set them (you can use an app like this) and check if you can get dual SIM to work.
I can make a H4113 build if you want to test it though.
Nonstop decay said:
Downloading them to my PC was the hardest part, for some reason the download often fails.
Click to expand...
Click to collapse
Unfortunately, Android File Host is problematic sometime.
Nonstop decay said:
I still have a couple of questions about these Sony AOSP builds that maybe you can answer:
1. Do you know what the Sony software binaries* do? I have flashed them on my device a couple of times, but I don't see anything added.
2. What is the difference between build type "userdebug" and "eng"?
3. If I use this build, how would you recommed I update it? Is the only way to flash in fastboot? (Like step 6 in Sony's guide**?)
Click to expand...
Click to collapse
Basically, what @frantisheq said.
I think you can flash IMG files through TWRP too if you extract the ZIP into your phone's memory.

axxx007xxxz said:
I can make a H4113 build if you want to test it though.
Click to expand...
Click to collapse
Just wondering aside from not being supported in Sony's open device program what exactly is needed to get the H3223 from getting AOSP 8.1 built for it? I can't imagine the kernel being much different on the H3223 from any of the other XA2 Ultra single sim models, right?

axxx007xxxz said:
Checking H4113 makefile, I don't see big differences except for a few properties: https://github.com/sonyxperiadev/device-sony-pioneer/blob/master/aosp_h4113.mk#L18-L22; you can try to set them (you can use an app like this) and check if you can get dual SIM to work.
I can make a H4113 build if you want to test it though.
Unfortunately, Android File Host is problematic sometime.
Basically, what @frantisheq said.
I think you can flash IMG files through TWRP too if you extract the ZIP into your phone's memory.
Click to expand...
Click to collapse
Yes plese make a build for H4413, i get so many random errors and every time i fix an error there appears another. And is the build for this model supposed to work with h4113? Aren't the boot images incompatible?

[OFFICIAL] [NIGHTLIES] LineageOS 16.0

{
"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"
}
Moto Z2 Force
Code:
- Your warrenty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 16.0 thread for the Motorola Moto Z2 Force, codename nash.
Join our Moto Z2 Force Development Discord server!
How to Install:
Please follow the instructions on our Official LineageOS Wiki page here.
If you don't follow these instructions, please don't expect support here. We also don't support 3rd party addons (Magisk/XPosed/Dolby/Viper/etc.), so please don't seek support if you use these.
Known Bugs:
Camera Mods don't work
Official Lineage OS builds will not ever allow Moto's Battery Mod "Efficiency Mode" to work.
The EQ Apps for Audio Mods (eg. JBL2 App) won't work, and will crash.
Ultrasonic Proximity Sensor doesn't work -- No support present in the OSS Audio HAL. If it was written in, it wouldn't be used by anything in Lineage, as the normal proximity sensor works fine.
Notes:
Official Lineage OS builds for nash ship with full Project Treble compatibility! Flash GSI's to your heart's content after flashing Lineage. Please don't report GSI bugs here, report them instead to the GSI's maker.
Technical details on our Treble implementation:
Treble is enabled with VNDK runtime enforcement. VNDK runtime enforcement means that unlike most "ported treble" you'll see, ours is just as it would be from the OEM, and can run GSIs. without need for hacks or additional flashable zips. We relabeled /oem to /vendor (as /oem isn't wasn't used in custom ROMs anyway). To use a GSI, flash official Lineage, then flash your GSI, it's that simple! Flashing a factory image will likely write over /oem and remove the mock vendor image.
Download:
LineageOS Updater
npjohnson's Personal Updater -- These are experimental, likely to break/eat your cat/destroy your data, and include GApps -- you'll only find support for these in the Discord linked above.
XDA:DevDB Information
[OFFICIAL] [NIGHTLIES] LineageOS 16.0, ROM for the Moto Z2 Force
Contributors
npjohnson, erfanoabdi, invisiblek
Source Code: https://github.com/LineageOS/
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Oreo Firmware
Based On: LineageOS
Version Information
Status: Nightly
Created 2019-03-03
Last Updated 2020-01-12

Reserved

Reserved

Thank you， ota ：）

How to get root on LOS 16?
There's no official root binary for LOS 16: https://download.lineageos.org/extras

7bob said:
How to get root on LOS 16?
There's no official root binary for LOS 16: https://download.lineageos.org/extras
Click to expand...
Click to collapse
Check again.

Just finished installing Lineage 16 on my moto z2 force, I cannot find the option for locking the screen by using the fingerprint that came originally with the phone. Is this feature available on lineage 16?

zidemizar said:
Just finished installing Lineage 16 on my moto z2 force, I cannot find the option for locking the screen by using the fingerprint that came originally with the phone. Is this feature available on lineage 16?
Click to expand...
Click to collapse
Yes. If you aren't seeing it, I'd suspect you're using an unsupported addon, or your hardware is failing.
It shows up/works fine here.

npjohnson said:
Check again.
Click to expand...
Click to collapse
Thanks, now I see it.
Is there something I have to consider when updating a Z2 Force from 15.1 to 16? Or can I just follow the general update guidelines?

7bob said:
Thanks, now I see it.
Is there something I have to consider when updating a Z2 Force from 15.1 to 16? Or can I just follow the general update guidelines?
Click to expand...
Click to collapse
Just follow general guidelines. We already had testers and upgrading from 15.1 to 16.0 didn't cause any issues. Obviously, if you do run into an issue, it is suggested to clean flash first to see if it was a borked update

npjohnson said:
Yes. If you aren't seeing it, I'd suspect you're using an unsupported addon, or your hardware is failing.
It shows up/works fine here.
Click to expand...
Click to collapse
Do you have a screenshot showing that it shows under screenlock settings?
Also what gaaps did you use when installing, I used the reccomended mindthegaaps and it kept giving me errors related to pixel apks.

link if image does not work
https://imgur.com/a/1eoVcgk
This is what shows under my screenlock setting, I do not have the setting that allows me to lock the phone using the fingerprint reader, this is from a fresh Lineage 15.1 installation with mindthegaaps, nothing else is installed on it. Had the same issue with lineage 16

Am I able to install Lineage 16 on Sprint Moto Z2 Force? I will get the phone next week, so I don't know if it's nash or what? Thanks.

Now I have installed los 16 and it was instructive for me. Learning by doing. After I have get working TWPR on both slots, data area of los 16 was suddenly encoded and requires a passwort for it on TWRP start to use it. So backup of intern data fails. Ok so far, we have two slots and that's anyway the backup. But how will work the update process? Just over the updater-function in settings/system or over TWRP? I'm on slot b now and on system_a is nothing. If I want update later, I have to do just flash the zip over TWRP and then reboot it and then maybe flash gapps again, because it's the first update on slot_a? Hope that's works because the encoding problem. Don't have the key.

AmazerG said:
Am I able to install Lineage 16 on Sprint Moto Z2 Force? I will get the phone next week, so I don't know if it's nash or what? Thanks.
Click to expand...
Click to collapse
Sure. It works on TMO and SPR, just no VZ and ATT for obvious reasons. Nash is the internal name for the Z2.
allrightlite said:
After I have get working TWPR on both slots, data area of los 16 was suddenly encoded and requires a passwort for it on TWRP start to use it. So backup of intern data fails. Ok so far, we have two slots and that's anyway the backup. But how will work the update process? Just over the updater-function in settings/system or over TWRP?.
Click to expand...
Click to collapse
Remove your fingerprint and screen lock method prior to entering TWRP. If you came from a stock ROM you must format data before flashing LOS. Updates can be done automatically with the updater, or manually thru recovery. The latter requires more time with no added benefits. Also encryption is enabled with custom ROMs.

So I was able to successfully update from 15.1 to 16.0. Here's what I did:
Backup my data
Boot into bootloader
Code:
fastboot boot twrp-3.2.3-2-nash.img
In TWRP, wipe System partition, then start sideload
Code:
adb sideload lineage-16.0-20190305-nightly-nash-signed.zip
reboot into bootloader
Code:
fastboot boot twrp-3.2.3-2-nash.img
In TWRP, start sideload
Code:
adb sideload MindTheGapps-9.0.0-arm64-20190216_211116.zip
Code:
adb sideload addonsu-16.0-arm64-signed.zip
reboot
done

I have tries at this moment to update over the lineage updater in settings and it's stopping with installation error. After try to reboot to TWRP it's endet up in reboots. But LOS16 stats normally again after press power button a little bit. Now I try again to update. Presumably it isn't working again. I think I will reflash twrp first and try then over this to update. Good idea or what's going wrong on my phone?
I must do new install. All broken. Holy crap. Hope this time I get it working.

7bob said:
So I was able to successfully update from 15.1 to 16.0. Here's what I did:
Backup my data
Boot into bootloader
Code:
fastboot boot twrp-3.2.3-2-nash.img
In TWRP, wipe System partition, then start sideload
Code:
adb sideload lineage-16.0-20190305-nightly-nash-signed.zip
reboot into bootloader
Code:
fastboot boot twrp-3.2.3-2-nash.img
In TWRP, start sideload
Code:
adb sideload MindTheGapps-9.0.0-arm64-20190216_211116.zip
Code:
adb sideload addonsu-16.0-arm64-signed.zip
reboot
done
Click to expand...
Click to collapse
what are the steps to update from firmware 8.0 to LineageOS 15.1 or 16, please
unlock bootloader, twrp, magisk (no problem),
My phone locks the boot loader again when I try to install a custom ROM
my firmware (TWRP, magisk)
RETAIL/NASH_RETAIL_8.0.0_OPXS27.109-34-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
in any way I thank you :good:

Ok, I have found out how get it working. Updater app not working here, always installation error after end of update process. Don't know why. So now I have a way found out, which seems to be working every update. Go to TWRP, flash los16 new zip and, this is very important (understand it very late xD) don't forget to flash twrp installer zip directly after los 16, because otherwise on the other slot is the stock recovery again. So, after this boot to the other slot with twrp directly from your phone and flash gapps every time, every update. Here I forgot it and nothing of the play store and co. was working anymore. Android Framework ID was away, too. Is there an easier way to update over TWRP or do I have to do so? And what happend to, backup wasn't possible to restore, maybe cause thought encoding?
The new update process with A/B is not easy to understand directly But the rom is a beast, very very good. Why I update and switch to los16? That's easy, because the bluetooth bugs on stock oreo was terrible (and no 8.1-batterie icon ) and lags on few drm videos and here and there. Speed of the UFS-flash going slower and slower, no its 3 times faster again. This phone works really great with LOS16. Very good work! It's not easy to understand all, but I will get it in my brain
Edit: There is another point, which could be interesting. Netflix shows error on start up (15001) and this even though safety net is passed. Hm.. Have downloaded from play store. Maybe older version does do this job, don't know.

Ace42 said:
Sure. It works on TMO and SPR, just no VZ and ATT for obvious reasons. Nash is the internal name for the Z2.
Click to expand...
Click to collapse
Is there anything different between Sprint Z2 force and Tmo ones in terms of hardware such as lack some band or what?

[ROM][EOL] Magma Moonshine - Android Q for Nexus 4 [mako]

{
"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"
}
HTML:
#include "std_disclaimer.h"
/*
* Your warranty is now void.
*
* 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.
*/
IMPORTANT: You need to have a /system partition at least 1272 MB size to flash this ROM.
voron00 said:
A few options to repartition the device:
https://forum.xda-developers.com/nexus-4/general/guide-increase-nexus-4s-partition-space-t3800264
https://forum.xda-developers.com/nexus-4/orig-development/repartition-nexus-4-repartition-t3844383
Also quick and easy repartitioning script for flashing on stock partition table only: https://drive.google.com/file/d/1GNbxlqG78WYOeXBxgmfGgMmsf02KMVOX/view?usp=sharing
Use at your own risk.
Click to expand...
Click to collapse
Any repartitioning is done at your own risk.
Descritpion:
One of the first releases of Magma for any device. It's meant to be clean and stable that's why it's pretty bare for now. I'm using Nexus 4 for testing this so probably more updates will come.
Official release with OTA will be available soon :fingers-crossed:
Working/not working:
- everything should work like on LOS 16 by voron
Flashing Instruction:
1. Backup all your data (Important)
2. Wipe system, data and cache.
3. Flash the ROM.
4. Reboot.
Downloads:
ROM: https://mirror.codebucket.de/magma/mako/
Credits:
- LineageOS team.
- @voron00 for his work on LOS for mako
Sources:
Device: https://github.com/MagmaDevices/device_lge_mako
Kernel: https://github.com/voron00/android_kernel_lge_mako
Vendor: https://github.com/voron00/proprietary_vendor_lge
Source Code: https://github.com/MagmaProject

edi194 said:
Working/not working:
- everything should work like on LOS 16 by voron
Click to expand...
Click to collapse
Does this mean that the ROM is Android 9 that looks like Android 10?

ze7zez said:
Does this mean that the ROM is Android 9 that looks like Android 10?
Click to expand...
Click to collapse
This rom is Android 10 based

Looking pretty good. I had already repartitioned for PIE and Magma installed without any problem. I couldn't change my home wallpaper to the pure black I prefer, and I discovered that the smallest OpenGapps containing Wallpapers is Mini, which was too big for my system partition. I installed Pico (Micro also works) and got the Wallpapers apk from Apkpure. All working fine.
The only thing not working is Magisk 20.1, which refuses to stick. I get an "installed ok" message in TWRP, but Magisk Manager isn't installed when I boot, and when I install the apk Manager says that Manager is up to date but Magisk itself isn't installed. I'll keep trying and report if I get any more info.
Great job, @edi194. Amazing to have Android 10 running on such a very old device. Thank you.
Edit: I've installed Magma on my second N4, which is a good one (screen works fine), and Magisk doesn't stick on this one either.
This is absolutely not any sort of criticism, just reporting. As I said, I'm blown away by having Android 10 on my ancient N4s - a remarkable achievement for which I'm very grateful.

Why does it want gapps for 7.1.2 and not 10?
nvm silly me downloaded arm64 gapps
Rom is running super smooth!

Thanks for the ROM. Tried it out.
It's not smooth, stutters more than Pie ROMs. However, given that it's still early stage for 10 ROMs, it's very impressive. No huge bugs. Totally usable performance. Pie ROMs in early stages were way more slower than this.
Keep up the good work! It will be great to see some updates!

Hi, body, good job for this, it's very smooth on my nexus4. And I want to know which gapps I can flashed on it? I can't find it. Thanks~

https://www.cyanogenmods.org/downloads/pico-opengapps-for-android-10-arm32/
Pico works fine.

Testing, testing, testing...
New build is up!
Changelog:
- updated device tree
- updated source
- changed bootanimation
Nothing pretty big ¯\_(ツ)_/¯
December patch not added... yet.
Known bugs:
- inbuilt screen recording will crash your systemui constantly, don't use it
- too big advanced reboot icon
Download link: https://mirror.codebucket.de/cosp/test/Magma-Moonshine-OFFICIAL-mako-20191213.zip

Thanks for the new version. I like the new Marshmallow(?) boot animation.
A couple of things to report. Each time I've flashed after a total wipe (all partitions) & format.
1) Magisk still doesn't stick. Manual installation of Magisk Manager shows "Magisk not installed" although TWRP shows a successful installation. I mention this only because I don't think it's a Magisk problem, as Magisk works on my Nexus 5 with Android Q.
On my first two attempts I got a bootloop - it showed the SIM PIN screen for a second, and then the boot animation showed. This repeated for about 10 minutes.
On the third attempt I installed only the ROM & OpenGapps Pico (no Magisk), and the bootloop is still happening as I write this.
2) I set a security PIN, which was accepted, but then the security showed the unlock method as "Swipe", and no PIN is required to open the phone. When I try to change it again, it says "Wrong PIN".
I have two Nexus 4s. The other one still has the original Magma on it and it doesn't have the PIN or bootloop problems, though Magisk doesn't work on that device either.
It may be only this specific device. Can anyone confirm that these problems don't happen on their device?

dahawthorne said:
Thanks for the new version. I like the new Marshmallow(?) boot animation.
A couple of things to report. Each time I've flashed after a total wipe (all partitions) & format.
1) Magisk still doesn't stick. Manual installation of Magisk Manager shows "Magisk not installed" although TWRP shows a successful installation. I mention this only because I don't think it's a Magisk problem, as Magisk works on my Nexus 5 with Android Q.
On my first two attempts I got a bootloop - it showed the SIM PIN screen for a second, and then the boot animation showed. This repeated for about 10 minutes.
On the third attempt I installed only the ROM & OpenGapps Pico (no Magisk), and the bootloop is still happening as I write this.
2) I set a security PIN, which was accepted, but then the security showed the unlock method as "Swipe", and no PIN is required to open the phone. When I try to change it again, it says "Wrong PIN".
I have two Nexus 4s. The other one still has the original Magma on it and it doesn't have the PIN or bootloop problems, though Magisk doesn't work on that device either.
It may be only this specific device. Can anyone confirm that these problems don't happen on their device?
Click to expand...
Click to collapse
Flashing opengapps will break multiple things in android 10 on 32 bit arm devices at the moment, including security PIN settings.

Thanks, @voron00, but both problems persist.
Full wipe & format, install Magma only, no Gapps or Magisk, boot was fine. I chose Security/PIN, entered the PIN, which was accepted, and pressed the back button. It showed "Swipe". I locked the screen and unlocked it with a simple swipe, no PIN required. I tried changing it again and got "Wrong PIN".
And I'm afraid it's bootlooping again - a second of the SIM PIN screen and then the boot animation.

Looking into this, if I'll fix it I'll push new build today

Thanks, @edi194 - much appreciated.
I thought that reporting this without a log might not be too helpful, so I tried it on my second Nexus 4, which is in perfect condition. I'm afraid that both the PIN & bootlooping are happening on that device as well - just Magma, no Gapps or Magisk.
Thanks for your work on Nexus 4 Android 10.

Update... again
Changelog:
- hopefully fix keyguard (pin/password/pattern is now working, after reboot it takes some time to unlock)
- added (useless for now) MagmaSettings
- removed screenrecorder (not working on mako anyway)
- really small source updates
About Magisk...
To be honest, I don't know what's the problem. Tested several Q/10 roms and it wasn't working on any of them. Probably it's an kernel thing but i'm not experienced about these at all. We need to wait for proper fix by someone else.
Download link on first post

Wow, you're good...
PIN and reboot now work correctly.
Magisk still doesn't work despite claiming to be installed in TWRP. No problem - my Nexus 4s are my emergency phones.
I don't know if it's of any help (or interest ) but the Android 10 on my Nexus 5, on which Magisk does work, is the work of @z3DD3r - an experimental Hammerhead LineageOS 17 on the green banner at the top of this link:
https://sourceforge.net/projects/hammerhead-lineageos/files/16.0/

Unfortunately, recovery from backup twrp 3.3.1-1 UA does not work for me. The system does not stand up and hangs on flying balls. Adb works. I can do logcat if needed.
Has anyone obtained a working system from recovery?

When I read your post my first thought was that "hangs on flying balls" must be a traditional Polish way of saying "Not very stable". But then I got what you meant...
I can confirm that recovering an image doesn't seem to work, which rather defeats the purpose of a recovery. I've never seen a TWRP recovery failure before. I did a backup with 3.3.1-1 UA, wiped everything except Internal Storage, and recovered the image, but it "hung on flying balls" .
I flashed standard TWRP 3.3.1 Mako, but that's the same - although it did complain about vendor & EFS partitions not being found. When I get more time I'll reinstall Magma and try the same backup, wipe & recovery with standard TWRP.
Update: No, standard TWRP doesn't work either. Full wipe & format, flash Magma & OpenGapps only, took TWRP backup, system rebooted ok, back to TWRP, recovered this new backup apparently ok, but it's been on the flying dots boot screen for 10 minutes now.

edi194 said:
About Magisk...
To be honest, I don't know what's the problem. Tested several Q/10 roms and it wasn't working on any of them. Probably it's an kernel thing but i'm not experienced about these at all. We need to wait for proper fix by someone else.
Click to expand...
Click to collapse
Try the commits on Nov 19, 2019 here: https://github.com/Colt-Enigma/platform_system_extras/commits/c10
Nitin

edi194 said:
Changelog:
- hopefully fix keyguard (pin/password/pattern is now working, after reboot it takes some time to unlock)
- added (useless for now) MagmaSettings
- removed screenrecorder (not working on mako anyway)
- really small source updates
About Magisk...
To be honest, I don't know what's the problem. Tested several Q/10 roms and it wasn't working on any of them. Probably it's an kernel thing but i'm not experienced about these at all. We need to wait for proper fix by someone else.
Download link on first post
Click to expand...
Click to collapse
FYI recorder is also fixed in latest sources.

[ROM][UNOFFICIAL][jd2019][9 Pie] LineageOS 16.0 for the Lenovo Z5s L78071

{
"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 9 Pie, 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. 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.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Known issues: (as of May 19, 2020)
- FM Radio app doesn't work; It actually works, just once every two attempts: If it crashes the first time, select close app, clear apps from background and try again; I'll find a definite fix soon;
- Wi-Fi signal strength doesn't show on status bar, only in the wireless screen;
- Fingerprint reader doesn't work;
- SELinux is currently set to permissive;
Instructions:
- This is a FULL ROM build, meaning your BOOT, DTBO, SYSTEM and VENDOR partitions will be overwritten. Backup first!
- You need firmware version 11.x.y (preferably 11.3.169 - recovery encryption only tested with that version), any will do. 10.5 will not work
- Download TWRP from the files section, fastboot flash it (if you don't have custom recovery yet)
- Download patched vbmeta.img
- Download the latest build
- (Optional) Download Gapps (arm64 9.0, any flavor) and Magisk
- Boot to recovery (whichever you have), flash the new recovery
- Reboot to recovery, now your data is decrypted, flash vbmeta, latest build, magisk and gapps
- Format DATA completely to start from scratch since encryption is different
- Reboot
Downloads:
Builds: https://sourceforge.net/projects/lineageos-lenovo-z5s/files/
Source code:
LineageOS: https://github.com/LineageOS
Kernel and Device Tree: https://github.com/jacoghi
Reporting Bugs:
DO NOT Report bugs if you're not following the instructions!
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.

Changelog:
May 19, 2020:
- Initital release, everything working except for FM and fingerprint reader;
- Kernel is completely overhauled and updated to LA.UM.7.8.r1-08500-SDM710.0;
- Audio drivers are stock 11.3.169 (we don't have the sources);
- Wifi is open-source, with MAC randomization currently being tested;
- Call recording already works;
- BT Audio works for calls and everything else, HD codecs being optimized;
- Wifi Display works perfectly on my cheap chinese Android TV Box. Please test with a Chromecast / Google Cast / SmartTVs, since I don't have any of those;
- Camera2API is active, RAW pictures are also enabled;
- Build will automatically encrypt your device, I had to fool Lenovo's BS keymaster to make it work, so it has to be enabled;
- As of now, I don't care if your apps work or not, that's not my problem, just let me know about hardware issues;

jacoghi said:
Please test with a Chromecast / Google Cast / SmartTVs, since I don't have any of those;
Click to expand...
Click to collapse
I can confirm that this works.
It's great to have a ROM that works and doesn't have audio problems or auto brightness issues compared to GSIs. I've been using this for two days without any problems aside from the bugs already mentioned. I am holding off on using Magisk like I normally do so as not to introduce complications.
Overall, a great first effort. Thank you very much!

carlshark said:
I can confirm that this works.
It's great to have a ROM that works and doesn't have audio problems or auto brightness issues compared to GSIs. I've been using this for two days without any problems aside from the bugs already mentioned. I am holding off on using Magisk like I normally do so as not to introduce complications.
Overall, a great first effort. Thank you very much!
Click to expand...
Click to collapse
Thanks for confirming that to me, great to know. Would you happen to have any of those fancy hi Def Bluetooth headphones so we can test aptx and aptxhd? And you can use magisk without any issues, I'm using it here right now, no problems.

jacoghi said:
Would you happen to have any of those fancy hi Def Bluetooth headphones so we can test aptx and aptxhd?
Click to expand...
Click to collapse
No, sorry. If that changes, I will let you know
I can imagine most of the users that are here are currently using a GSI. The stock 11.3.169 from here can actually be installed via TWRP. Flashing it would revert to stock recovery so users need to reinstall the TWRP recovery image during the same session. That's how I ensured that I was running an 11.x firmware after using all those GSIs from 4PDA. Hopefully this helps others to revert to stock so they can use your LOS build.

Some more good news, we now have a TWRP that decrypts data even from this updated Lineage 16 build. It actually should work for any ROM flashed atop firmware 11.3.169. That's the one I'm using and probably the majority of people who wanna stick to "the latest and greatest" speech, so here we go, now we can enable OTAs without any issues and flash anything. This recovery can decrypt any data regardless of password type, so you can use PATTERN, PIN, or whatever, it will work, I tested them all.
https://sourceforge.net/projects/lineageos-lenovo-z5s/files/twrp-3310-jd2019-recovery.img/download

And what is apparently massive news for us, our phone will get an Android 10 official update, meaning we'll be able to boot lineage 17.1 with the updated audio drivers (in theory). Anybody in China or who knows how to trick their system and able to get ahold of these files?
https://club.lenovo.com.cn/thread-5849244-1-1.html

jacoghi said:
Some more good news, we now have a TWRP that decrypts data even from this updated Lineage 16 build. It actually should work for any ROM flashed atop firmware 11.3.169. That's the one I'm using and probably the majority of people who wanna stick to "the latest and greatest" speech, so here we go, now we can enable OTAs without any issues and flash anything. This recovery can decrypt any data regardless of password type, so you can use PATTERN, PIN, or whatever, it will work, I tested them all.
https://sourceforge.net/projects/lineageos-lenovo-z5s/files/twrp-3310-jd2019-recovery.img/download
Click to expand...
Click to collapse
Hi, I used your recovery to try and create a full backup of your ROM before I go back to stock. I encounter an error when it tries to backup the system partition - the backup fails. When I tried to install the Full OTA ROM from Lenovo, it also fails. I flashed the other TWRP and both the backup and install worked.
I'm going back to stock to get the 11.5 update available only if the phone has a locked bootloader.

carlshark said:
Hi, I used your recovery to try and create a full backup of your ROM before I go back to stock. I encounter an error when it tries to backup the system partition - the backup fails. When I tried to install the Full OTA ROM from Lenovo, it also fails. I flashed the other TWRP and both the backup and install worked.
I'm going back to stock to get the 11.5 update available only if the phone has a locked bootloader.
Click to expand...
Click to collapse
Hey man, thanks for the report. I just rebooted to recovery and backed up the system partition without a hitch, so no clue what happened with you. Regarding the Lenovo Ota it probably doesn't work since they use different manifests from the ones I'm using with lineage. Nevertheless I'll make it universal now that I know about it. Let me know if you can get 11.5 and we can make a dump of all partitions. Thanks man

jacoghi said:
Hey man, thanks for the report. I just rebooted to recovery and backed up the system partition without a hitch, so no clue what happened with you. Regarding the Lenovo Ota it probably doesn't work since they use different manifests from the ones I'm using with lineage. Nevertheless I'll make it universal now that I know about it. Let me know if you can get 11.5 and we can make a dump of all partitions. Thanks man
Click to expand...
Click to collapse
The only thing I can think about was that I was trying to save to a microSD instead of internal storage.
Anyhow, I'm back on LOS. I went back to stock, relocked the bootloader, got the update notification but the downloaded update fails on install. I "read" in the Chinese forums that access to 11.5 is some sort of closed beta; some users also encounter failed updates.
@wzsx150 published a new TWRP based on Android 10, probably with the partition file info of 11.5. It doesn't work for me when I flashed it on top of 11.3 (Android 9). Thought it might help you further.

carlshark said:
The only thing I can think about was that I was trying to save to a microSD instead of internal storage.
Anyhow, I'm back on LOS. I went back to stock, relocked the bootloader, got the update notification but the downloaded update fails on install. I "read" in the Chinese forums that access to 11.5 is some sort of closed beta; some users also encounter failed updates.
@wzsx150 published a new TWRP based on Android 10, probably with the partition file info of 11.5. It doesn't work for me when I flashed it on top of 11.3 (Android 9). Thought it might help you further.
Click to expand...
Click to collapse
hey man could you please help out, was trying to revert to the stock rom but getting a blank screen after i'm done and it shows lenovo

carlshark said:
The only thing I can think about was that I was trying to save to a microSD instead of internal storage.
Anyhow, I'm back on LOS. I went back to stock, relocked the bootloader, got the update notification but the downloaded update fails on install. I "read" in the Chinese forums that access to 11.5 is some sort of closed beta; some users also encounter failed updates.
@wzsx150 published a new TWRP based on Android 10, probably with the partition file info of 11.5. It doesn't work for me when I flashed it on top of 11.3 (Android 9). Thought it might help you further.
Click to expand...
Click to collapse
That's why it failed, system partition is 5.1 GB, your sdcard is probably formatted in FAT32 which DOESN'T ALLOW files over 4GB, that's a filesystem limitation.
I'll wait for somebody getting us 11.5 firmware files and release a new twrp for Android 10, (partitions won't change and AFAIK, wsx's twrp doesn't decrypt and is full of extra non open source stuff) and Lineage 17.1, until then makes little sense to me update this knowing it won't last long anyways.

jacoghi said:
That's why it failed, system partition is 5.1 GB, your sdcard is probably formatted in FAT32 which DOESN'T ALLOW files over 4GB, that's a filesystem limitation.
Click to expand...
Click to collapse
Oh, right, I totally forgot all about that. Should have tried enabling compression or saving to internal storage.
I'll wait for somebody getting us 11.5 firmware files and release a new twrp for Android 10, (partitions won't change and AFAIK, wsx's twrp doesn't decrypt and is full of extra non open source stuff) and Lineage 17.1, until then makes little sense to me update this knowing it won't last long anyways.
Click to expand...
Click to collapse
I've found a 4PDA post regarding updating to 11.5 and reposted the good stuff here. Hope it helps. Thanks for your good work!
---------- Post added at 06:38 AM ---------- Previous post was at 06:35 AM ----------
seisa said:
hey man could you please help out, was trying to revert to the stock rom but getting a blank screen after i'm done and it shows lenovo
Click to expand...
Click to collapse
I know this is the wrong thread to answer this, but we can't really help you out without some more details. Were you trying to install through recovery? Through QFIL?
From the looks of it, sounds like you have a bootloop. Try doing QFIL again and unlocking bootloader, or the other way around - sometimes it works for me that way.

I have Z5s 6GB/128GB model, sold as Global Version & Global ROM.
It does have EU LTE bands, so it probably is somewhat "global".
The downside: I am at 10.5 version with no updates available. Seller also told that there are no updates.
Two questions:
1. Is it absolutely necessary to have 11.3+ to install this LineageOS ROM? What is blocking installation if I have 10.5? Can I brick it?
-- EDIT: I will answer myself: Yes it is needed. LineageOS did not flash over 10.5 and gave an error. That was validation error before flashing, so no harm done.
2. Is it safe to install Chinese ROM on this device? Is it possible to loose something in the process? Like LTE bands or something else important?
-- EDIT: Seems to be ok.
I really want to install LineageOS or some other google free AOSP ROM. But I do not want to loose important features or brick it in the process.
Thanks.
EDIT: I installed Arrow OS GSI at the moment over 10.5 and it seems to work. But still looking forward to get pure LineageOS installed.

I have one problem that is hardware related:
Microphone level is quite low compared to my previous phone and people are complaining about low volume when I call.
Is there any way to add more gain? I tried to search but did not find easy and straightforward answer. Most solutions refer to methods/files that do not exist on this ROM.
What I found was complaint that there is still no way to easily manage audio stuff in android...
Mic Test (lauresprojects.com.mictest) app confirms that recording levels are considerably lower in both direct sound and communication mode when comparing to my other phone.
Otherwise seems to working quite nicely. Thanks for your good work.

I can't use face unlock with this ROM.

Is there still some active development at this project?
Is there some active development at this project?

[ROM] Dirty Unicorns 14.7 {Bonito} (09/13/20)

{
"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"
}
About Us:
Dirty Unicorns is an AOSP based project built to enhance the stock Android experience.
Our focus has been and is always to contribute back to the community. That is ultimately why we do what we do.
We DO NOT accept, nor ask, for donations. We do not believe in that. Everything that is necessary to keep this project going comes out of our own pocket. This includes, but is not limited to; Devices, Gerrit, our websites and services, etc.. The only thing that we ask in return is that you have patience, search the thread for answers prior to posting, read diligently, and try to enjoy the process with us!
Kernel Source:
https://github.com/DirtyUnicorns/android_kernel_google_bluecross
Flashing Instructions:
If you have a device that uses TWRP
Verify that you're using the latest version of TWRP
Perform a FULL WIPE: (A full wipe is when you wipe system/data/cache/dalvik)
Flash the latest version of this ROM
Reboot and ENJOY!
If you have a device that does not use TWRP
Download boot.img and ROM zip from DU server
Reboot into bootloader and flash the boot.img
Code:
fastboot flash --slot all boot boot.img
Reboot to recovery
Go to recovery select factory reset
Select Apply update from ADB to flash the zip
Code:
adb sideload nameofbuild.zip
Reboot and ENJOY!
If you're just updating DU on a device without TWRP
Download ROM zip from DU server
Reboot into recovery and select Apply update from ADB to flash the zip
Reboot system now and ENJOY!
**All bugs and feature requests must be reported to JIRA**
**If you use Xposed, please don't bother reporting any bugs**
**If you use another kernel, please don't bother reporting any bugs**
**If you fail to follow these instructions, please don't bother reporting any bugs**
Download Links:
Build(s) - Bonito
Other Links:
ROM Source - https://github.com/DirtyUnicorns
Gerrit - http://gerrit.dirtyunicorns.com
Crowdin (translations) - https://crowdin.net/project/dirtyunicorns
JIRA (Bug Reporting / Feature Requests) - http://jira.dirtyunicorns.com/
Telegram - https://t.me/dirtyunicorns / https://t.me/DirtyUnicornsSupport
XDA:DevDB Information
Dirty Unicorns, ROM for the Google Pixel 3a XL
Contributors
NYCHitman1, jbats
Source Code: https://github.com/DirtyUnicorns
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 14.7
Stable Release Date: 2020-09-13
Created 2020-08-08
Last Updated 2020-09-13

Thank you so much!
I've used nothing but DU since March and I'd like to thank you for your continued work on our device. Hopefully now more people will find and appreciate your efforts!

Sweet a new rom to try out

@jbats good to see you round these parts. Just installed DU for the 1st time on bonito; runs good, looks good, and I like the new boot logo and recovery. Any plans to build an in rom updater like lineage or aosip? I've become a fan of seamless updates. Anyways, nice work as usual and thanks for the rom.

41rw4lk said:
@jbats good to see you round these parts. Just installed DU for the 1st time on bonito; runs good, looks good, and I like the new boot logo and recovery. Any plans to build an in rom updater like lineage or aosip? I've become a fan of seamless updates. Anyways, nice work as usual and thanks for the rom.
Click to expand...
Click to collapse
Currently, no. However, we are planning to do this in the future.

Just flashed & loving it so far. Great to see the team still working. I'm trying to remember the first phone I flashed dirty on. Maybe htc m8. It was so long I don't recall

I've installed Bliss and Dirty Unicorns,
Dirty Unicorns is better IMO because of the minimal apps and quickness of multi-tasking.
Only complaint I would have is the lack of customization when it comes to status bar and colors.
Love the ROM and still using it, ty DU team. Please make variations of your boot animation

godpowerrr said:
I've installed Bliss and Dirty Unicorns,
Dirty Unicorns is better IMO because of the minimal apps and quickness of multi-tasking.
Only complaint I would have is the lack of customization when it comes to status bar and colors.
Love the ROM and still using it, ty DU team. Please make variations of your boot animation
Click to expand...
Click to collapse
We're not making anymore variations of the boot animation. We have a light version and a dark version. That's good enough for us.
As for the lack of customization, we include what we find useful. We're never going to be one of these cookie cutter kitchen sink ROM's you see littered across XDA. If you would like to make a particular feature request, check the OP for instructions on how to do so.

FYI
Tried flashing boot .img and rom.zip from perminent TWRP (stock Pie), and does not work. I'll update to Q and follow the directions now.
Ok? I have no adb device detected from DU recovery. I guess I'll truy TWRP. Nevermind, temporary TWRP doesn't work with June release of Q.
Back to initial Pie factory image, and now will not boot into DU recovery. Temporary TWRP will not flash du_bonito-v14.6-20200808-1220-OFFICIAL and gives an error.
Flashed bootloader-bonito-b4s4-0.2-6355063.img, radio-bonito-g670-00042-200421-b-6414611.img, and 20200808-OFFICIAL-boot.img from fastboot and DU recovery has adb and sideload is working, but get an error at 47%
Code:
C:\Users\Russell\Downloads\Android\ADB and Fastboot>adb sideload du_bonito-v14.6-20200808-1220-OFFICIAL.zip
serving: 'du_bonito-v14.6-20200808-1220-OFFICIAL.zip' (~47%) adb: failed to read command: No error
In recovery
Code:
Step 1/3
Error applying update: 7 (ErrorCode::kInstallDeviceOpenError)
E:Error in /sideload/package.zip (status 1)
Maybe a bad download, but I'll probably try v14.5 if I'm going to go through the trouble downloading again.
Honestly, I already pulled the trigger on an LG V20, and just playing with this a bit more before it goes on Swappa. No SD slot, no decent recovery partition, and USB 2.0? No thanks.

ssurell said:
Tried flashing boot .img and rom.zip from perminent TWRP (stock Pie), and does not work. I'll update to Q and follow the directions now.
Ok? I have no adb device detected from DU recovery. I guess I'll truy TWRP. Nevermind, temporary TWRP doesn't work with June release of Q.
Back to initial Pie factory image, and now will not boot into DU recovery. Temporary TWRP will not flash du_bonito-v14.6-20200808-1220-OFFICIAL and gives an error.
Flashed bootloader-bonito-b4s4-0.2-6355063.img, radio-bonito-g670-00042-200421-b-6414611.img, and 20200808-OFFICIAL-boot.img from fastboot and DU recovery has adb and sideload is working, but get an error at 47%
In recovery
Maybe a bad download, but I'll probably try v14.5 if I'm going to go through the trouble downloading again.
Honestly, I already pulled the trigger on an LG V20, and just playing with this a bit more before it goes on Swappa. No SD slot, no decent recovery partition, and USB 2.0? No thanks.
Click to expand...
Click to collapse
If you're coming from Pie, you need to flash stock to both slots to get your firmware up to date.
TWRP does not work on Q for Pixel 3 and 4.
Please do some research before messing with the device further.

NYCHitman1 said:
If you're coming from Pie, you need to flash stock to both slots to get your firmware up to date.
TWRP does not work on Q for Pixel 3 and 4.
Please do some research before messing with the device further.
Click to expand...
Click to collapse
I like to try every possible combination of flashing, maybe resize or dd some partitions at sleep deprived 4am, whatever. But I've been using the factory flash-all images, so I assume both slots, else what good are they. Some of the problem may have been with the myriad of adb versions I have littering my system. A photographic memory would be more effective than research redundancy (I forgot thinking temp. TWRP still worked).
Come to think of it, I think I flashed the June OTA going to Q. So that's likely why I didn't have ADB with DU Recovery

ssurell said:
I like to try every possible combination of flashing, maybe resize or dd some partitions at sleep deprived 4am, whatever. But I've been using the factory flash-all images, so I assume both slots, else what good are they. Some of the problem may have been with the myriad of adb versions I have littering my system. A photographic memory would be more effective than research redundancy (I forgot thinking temp. TWRP still worked).
Come to think of it, I think I flashed the June OTA going to Q. So that's likely why I didn't have ADB with DU Recovery
Click to expand...
Click to collapse
Unfortunately, it doesn't. The flash-all script only flashes to the active slot on the device, so you would have to manually change slots and run said flash-all script again to be completely up to date. As for the platform-tools versions, I believe 30.0.4 is the latest revision available at this time. Might be a good idea to download that and delete everything else you have.
Outside of this, our flashing instructions are very clearly labeled and should get you through the process of flashing DU as long as you follow the instructions that are applicable to you.

ROM is running great. Do we have to do a full wipe or can we just clear cache between uodates

sjpritch25 said:
ROM is running great. Do we have to do a full wipe or can we just clear cache between uodates
Click to expand...
Click to collapse
You don't have to wipe at all between updates. It's written in the OP. Please read the instructions.

Great ROM, only issue I have is that whenever I try to change the volume while using my Pixel Buds, the system UI crashes and restarts every time. I've also found that this isn't device specific and happened on other phones I've had with Bliss. Aside from that, great work!

champ784 said:
Great ROM, only issue I have is that whenever I try to change the volume while using my Pixel Buds, the system UI crashes and restarts every time. I've also found that this isn't device specific and happened on other phones I've had with Bliss. Aside from that, great work!
Click to expand...
Click to collapse
Could be a larger platform issue. You could provide logs to Google, but seeing as R is literally right around the corner -- they'll likely ignore it until the revision is out to the masses.

Download from DU site fails
I can't download any file greater than 1GB in size from https://download.dirtyunicorns.com/
It always stops at exactly 1 GB.
Unfortunately the latest DU release for bonito is 1.07 GB in size.
Can you confirm that? Maybe it's my Internet connection. I've tried different browsers and even wget.
Are there any mirrors?

NYCHitman1 said:
Could be a larger platform issue. You could provide logs to Google, but seeing as R is literally right around the corner -- they'll likely ignore it until the revision is out to the masses.
Click to expand...
Click to collapse
Yeah that's what I figured. The second Android R releases, I don't see anyone caring ??

socksi said:
I can't download any file greater than 1GB in size from https://download.dirtyunicorns.com/
It always stops at exactly 1 GB.
Unfortunately the latest DU release for bonito is 1.07 GB in size.
Can you confirm that? Maybe it's my Internet connection. I've tried different browsers and even wget.
Are there any mirrors?
Click to expand...
Click to collapse
Hi @socksi. I have downloaded the file in 12 secs from our server without issue. Unfortunately, we do not use mirrors.
I will reach out to our webmaster and have him look into it. Stay tuned.

NYCHitman1 said:
Hi @socksi. I have downloaded the file in 12 secs from our server without issue. Unfortunately, we do not use mirrors.
I will reach out to our webmaster and have him look into it. Stay tuned.
Click to expand...
Click to collapse
It fails even when using a VPN tunnel. Most probably it's not my Internet connection.
Maybe some kind of GEO blocking? I'm from Germany.