LineageOS for dumpling, onyx and castor

November 18, 2022 / Development, Mobile

After software support for OnePlus 5T ran out 2 years ago, we spent a LOT of time getting OnePlus 5 and 5T up to speed on LineageOS. By now it is safe to say that LineageOS on these devices is superior to OxygenOS, especially in terms of performance and battery usage. We ported over EAS (energy aware scheduling), fixed tons of big and small errors so now everything is working smoothly. The latest official version is based on Android 12, but the version for Android 13 is in an even better state already, so it will be released rather soon!

Also, some legacy devices got some much needed love, such as Sony Xperia Tablet Z2 WiFi and LTE variants. Both of them are now running LineageOS 18.1 based on Android 11 just fine.

Go check it all out at the LineageOS Download Center.

I would like to take this opportunity to thank all the donors who donated money and in some cases even devices for me to help improve the situation. Your help is very much appreciated, and you guys are all in the Hall of Fame!

Android Storage Access Framework woes after reboot

November 5, 2020 / Development

There seems to be a lot of confusion amongst developers how to get persistible permissions when using the SAF. Wasted some hours on this, so it is worth a note here.

To get the average file open dialog using the SAF, one could do this:

Intent intent = new Intent(Intent.ACTION_OPEN_DOCUMENT);
intent.addCategory(Intent.CATEGORY_OPENABLE);
intent.setType("*/*");
startActivityForResult(i, 0);

That works perfectly fine, but after a reboot, the permissions are gone, and opening the same file (without opening the dialog again) will fail. There are lots of resources on the Internet that tell developers to add some arguments when calling the Intent. This is wrong! Passing these to the intent is completely useless:

intent.addFlags(Intent.FLAG_GRANT_READ_URI_PERMISSION); // Don't do this
intent.addFlags(Intent.FLAG_GRANT_WRITE_URI_PERMISSION); // Also no!
intent.addFlags(Intent.FLAG_GRANT_PERSISTABLE_URI_PERMISSION); // NO!

Instead, a single call to takePersistableUriPermission will retain permissions even after a reboot:

protected void onPropertyRequestResult(int propertyRequestCode, int resultCode, Intent data) {
    getContentResolver().takePersistableUriPermission(data.getData(), Intent.FLAG_GRANT_READ_URI_PERMISSION | Intent.FLAG_GRANT_WRITE_URI_PERMISSION);
}

The nightly is dark and full of terrors

May 25, 2016 / Development, Mobile

Today, I am happy to announce the start of CyanogenMod 13 nightlies for Xperia Tablet Z (pollux) and Xperia Tablet Z Wifi (pollux_windy). This means CM13 is considered stable enough for daily use on these devices, so the terrors should be rather limited. Anyone interested can find the official downloads at the usual location. Active development on the fusion3 platform is ongoing, I will attempt to shift focus to the phones now.

Marshmallow Is Alive

October 6, 2020 / Development, Mobile

Today, Xperia Tablet Z booted into CyanogenMod 13 for the first time. Many things still broken, but it is a start!

Marshmallow Screenshot

Lollipop Fusion Complete

September 24, 2015 / Development, Mobile

As of today, all Sony Xperia devices based on the Fusion3 board (Xperia Z, ZL, ZR, Tablet Z, Tablet Z WiFi) are getting official CyanogenMod 12.1! When I first started looking at these devices in December 2014, the CM12 source code would not even compile, let alone boot, and even the recovery was broken.

Well, here we are, hundreds of commits and quite a lot of annoyances later: F2FS is now supported, a plethora of kernel changes and the new BFQ scheduler made the user experience better than ever, the latest proprietary blobs are integrated, SELinux is properly set up, and a ton of reorganization and cleanup has been done – for all of Sony’s MSM8960 devices and beyond.

Still many things to do, but for today, I’m lighting a cigar! If you have one of these devices, check out GET.CM and give it a whirl. There is a truly fantastic team of developers at Cyanogen and CyanogenMod, and without them, none of us could enjoy mobile computing quite like we do.

Carpe Noctem #2

August 20, 2015 / Development, Mobile

After a long, arduous development road, I’ve enabled CyanogenMod nightly builds for the Sony Xperia Z. This brings nightlies directly from CM11 to CM12.1, which hopefully all users will enjoy. Thanks to everyone at my XDA thread, especially Andy van der Steen, who lent me his phone for development. Without that, I would never have come this far.

Xperience F2FS

August 19, 2015 / Development, Mobile

Starting with early March 2015, CyanogenMod for the whole original line of Sony’s Xperia Z devices support F2FS, a filesystem optimized for flash memory. Tests have shown it to outperform the default ext2/3/4 that we used previously, so definitely a nice thing to have.

However, if you want to benefit from F2FS, you need to manually convert your phone. Be aware that this needs some understanding of how to use ADB and the conversion process will DELETE all you user data/settings!

First, you need to have CyanogenMod 12 or higher installed on your phone, and be using the official recovery. Also, you need ADB installed and ready to use on your computer.

This is how you convert to F2FS:
– Connect your phone via USB and boot into recovery mode
– Open a command line and type “adb shell”
– Type “mkfs.f2fs /dev/block/platform/msm_sdcc.1/by-name/cache”
– Type “mkfs.f2fs /dev/block/platform/msm_sdcc.1/by-name/userdata”
– Reboot the device

Carpe Noctem

July 21, 2015 / Development, Mobile

After a long development phase, Xperia Tablet Z and Xperia Tablet Z Wifi are now on the official nightlies list of CyanogenMod 12.1, not least thanks to testers on XDA and generous donations.
The list of improvements since CM12 is immense, with a load of kernel updates that makes these devices as smooth and fast as they have never been on CyanogenMod.
Enjoy people!

CyanogenMod Fusion

July 21, 2015 / Development, Mobile

In January, I’ve been added as a device maintainer for Sony’s fusion3 platform on CyanogenMod. That platform includes the original Xperia Z line of devices (Z, ZL, ZR, Tablet Z, Tablet Z Wifi). Most of my work went into the platform and the 2 tablets, since I actually own one of these. By now, I greenlighted the tablets for CM12, and they are now official CyanogenMod nightlies. , they are my main target of development. The phones will trail a bit, since I need to rely on others to test fixes and features for me, mainly through a thread on XDA.

Smart phone RIL

January 7, 2015 / Development, Mobile

After tinkering with cameras and solar power systems, it was time to play around a bit with Android – in the form of CyanogenMod. After setting up a build environment for my i9100 (a Galaxy S2 in marketing terms), I decided to help figure out a problem with open-sourcifying one of the libraries for it, namely libril (part of the radio interface layer).

This device has a history of freaking out OSS people, and libril was no different, as can be seen in the code review for the library. While the same code would work perfectly fine on similar devices with similar radios, it kept crashing on the i9100 upon dialing out. After some debugging, I found out that the UUS (user-to-user signaling) handling was causing the crash – a MEMMAP SIGSEV error!

Namely, it was memset(&uusInfo, 0, sizeof(RIL_UUS_Info)); that caused the kernel to freak. Intermediate solution? Remove the UUS information, as it is not really mandatory. The question remains: why can’t the phone allocate the (little) memory required for this struct? Might have something to do with heap/stack allocation…

Scroll to Top