Today, Xperia Tablet Z booted into CyanogenMod 13 for the first time. Many things still broken, but it is a start!
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.
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.
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
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.
Well, Peter has been at it again, and incorporated changes for the latest WinUAE version. Also, the repository with all the help pages is now publicly hosted on Github! Better late than never, after more than a decade of secrecy :)
You can find the download at the usual location.
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.
Checkpoint switched the platform for their security products from SecurePlatform to Gaia. Sooner or later, a switch to Gaia will be necessary… Well, there are plenty of documents about this topic out there. Rejoice, people, one follows right here – valid for small installations (standalone boxes, really).
First of all, you want to get the current configuration from your box. You need to understand that this consists of 2 parts: the OS level configuration (interfaces, routing table) and the CP database (rulebase, CP settings). Checkpoint provides tools for the latter, but not for the latter.
On the OLD firewall
1) Download this script
2) Get the target migration tools from Checkpoint. Either from a box with the target software installed, or from their download center
3) Copy both over to the box, by any method that works for you (TFTP, FTP, USB, magic)
4) Extract the CP upgrade_tools
5) Spread some execute permissions if necessary! “chmod +x splat2gaia.sh” and “chmod +x migrate”
For the OS level configuration
1) Execute “splat2gaia.sh”
2) Copy the output somewhere safe
For the CP database
1) Execute “migrate export”
2) Copy the resulting TGZ file somewhere safe
On the NEW firewall
1) Install a fresh Gaia image, if not already installed
2) Follow CP’s guide and finish the first time configuration wizard
Restore the OS level config
1) Get console access to the box
2) Copy the output of splat2gaia.sh over line by line, or copy it into a bash script
Restore the rule database
1) Copy the TGZ over to $FWDIR/bin/upgrade_tools
2) Execute “migrate import”
Almost done! Now, connect to the box via your newly installed SmartDashboard, and install the rule database. Only after that step will the rules be enforced!
Note: depending on how you perform the switch over to the new platform, you might get a ton of “TCP packet out of state” errors. In that case, you might want to go to general options -> stateful inspection, and disable the “drop out of state packets” for the first couple of hours of operation.