Hey everyone,

I wanted to share another update on the Lumia 1520 project because we finally crossed a milestone that honestly felt impossible a couple of weeks ago.

For anyone that hasn't seen my previous posts, the goal isn't just to "install Android." I'm trying to bring modern Linux/postmarketOS support to the Lumia 1520 so the phone can have a second life.

Over the last couple of weeks I've had to build a lot of things that simply didn't exist for this device:

• Wrote a new device tree for the Lumia 1520 (RM-940)
• Added Lumia 1520 support to lk2nd
• Built and tested custom bootloaders
• Fixed memory relocation issues that were preventing Linux from even starting
• Built a custom postmarketOS device package
• Got the Linux kernel loading and executing on real hardware

The exciting part is that today we finally reached the postmarketOS debug shell on the actual device. There is still a lot left to do before I'd call this usable, but seeing a Linux shell running on a Lumia 1520 is something I wasn't sure I was gonna be able to do.

https://preview.redd.it/2904oq6zd7bh1.jpg?width=1152&format=pjpg&auto=webp&s=eca3e67b29a6b8eb5fba18d9d0ebe795da15b987

This has turned into a much bigger project than I originally expected, but it's been incredibly rewarding.

Hey everyone,

First, I wanted to thank everyone who commented on my last post about the AI music generator I've been building. The feedback was honestly far more helpful than I expected.

The project officially has a name now: Callio.

The name comes from Calliope, the Greek muse of epic poetry. Since the goal is helping people create music and lyrics, it felt fitting.

A lot of people asked when they could try it, and over the last couple of weeks I've been pushing hard toward a working demo. The good news is that I now have a Windows installer, generation pipeline, stem editing, performance routing (spoken, sung, whisper, etc.), exports, and a local studio workflow all working.

The bad news, and something I learned the hard way, is that AI music quality is almost entirely a compute problem.

I can make Callio run locally, but the quality varies dramatically depending on the hardware it's running on. That's not the experience I want people judging the project by.

I don't want someone on an older laptop thinking, "This sounds terrible," when the bottleneck is their hardware, not the platform.

So I've decided to change direction.

Instead of trying to make every user's PC generate songs locally, I'm going to move the high-quality generation to a hosted GPU backend while keeping the editing, stem management, and studio workflow in the desktop app.

That way everyone gets the same quality output, regardless of whether they're using a gaming PC or a five-year-old laptop.

I'm still a one-person team, so this isn't going to happen overnight, but I'd rather delay the demo than release something that doesn't represent the vision.

Thanks again to everyone who's taken the time to comment, challenge ideas, and offer feedback. It's genuinely helped shape the direction of Callio. If you absolutely don't care, or have a PC beefy enough to run it, I am more than willing to share it still.

Hey everyone,

I've been working on a project to get postmakertOS onto my Lumia 1520 and it's coming with its headaches lol but also...i know what I got into lol When I started, there really wasn't a complete path forward for this device anymore, so I ended up building quite a bit from scratch.

So far I've:

• Built a new device tree for the Lumia 1520.
• Compiled a custom lk2nd bootloader using that device tree.
• Successfully built the bootloader and DTB into a working image.
• Got everything integrated into the postmarketOS build process.

At this point the software stack builds cleanly, which is crazy by itself (for me), considering how little active development there is for these old Lumias now.

The problem I'm fighting now is getting the kernel to actually continue booting. Right now I'm chasing what appears to be an early boot issue. I've been experimenting with things like framebuffer relocation, passing ramoops through lk2nd, kernel command line changes, and validating the memory layout. My current suspicion is that something in the MSM8974 memory map or reserved memory regions isn't lining up correctly, but I'm still narrowing it down.

My next steps are to start instrumenting the early boot path more aggressively and verify exactly where things are failing before Linux fully takes over.

Has anyone here worked on the Lumia 1520, Lumia 930/Icon, or other MSM8974 Windows Phones and run into something similar? Even if you worked on Mainline4Lumia years ago, I'd love to hear if there are any gotchas I'm overlooking.

It's been a fun project so far, and regardless of where it ends up, it's been pretty satisfying breathing some new life into a phone that's over a decade old.

So this is my latest song. I'm posting this here cuz while it's not fully AI, there is AI in it. But as for emotional music, What do you think?

I've been building an AI music platform and I'd love some feedback from people in this community. Being that most, if not all, AI music tools focus on generating songs that sound like existing artists.

I went in a different direction.

The platform generates original songs using a music theory knowledge graph (scales, chord progressions, voice leading, song structure, harmonic function, etc.) rather than trying to imitate copyrighted recordings. But the part I'm most excited and worried about in is the vocal system.

Instead of choosing a celebrity voice or cloning another artist, users train the system on their own voice. The onboarding process walks users through a series of vocal exercises and calibration recordings. The AI analyzes things like pitch range, vocal characteristics, vibrato, tone, and singing style, then builds a personal voice model that can be used in future songs.

The result is that every generated song is unique to that user because the vocals are literally based on their own voice.

The goal isn't:

"Make me sound like Artist X."

The goal is:

"Help me create music as myself."

What do you all think about this approach? Do you see more value in AI helping people become artists themselves?

Note: This is still an active development project and not a finished commercial product.

The core theory engine, knowledge graph, composition pipeline, and vocal calibration systems are built, but several AI components are still being upgraded and refined. Right now I'm focused on improving generation quality, expanding training data, and validating the user-owned vocal model workflow.

I'm sharing this early because I'd rather get feedback from musicians, producers, and AI music enthusiasts while the architecture is still flexible enough to change.

I run a small software company called Korelis Labs, and one of the bigger projects I'm working on is a privacy-focused Android operating system.

While building it, I ended up creating a number of privacy and security features that I thought would be useful outside of the OS itself, so I pulled some of those ideas into a standalone Android app called DeadKey.

DeadKey is what I'd call a privacy-first vault.

The goal was simple: keep your files under your control without requiring an account, a subscription, or a cloud service.

Features include:

• AES-256-GCM encryption
• Argon2id password protection
• Biometric unlock
• Decoy vault
• Duress/wipe PIN
• App Personas (Calculator, Notes, Files, or Weather)
• Offline-first design
• No analytics or tracking
• No account required
• No subscriptions
• Export encrypted backups wherever you want

One thing I intentionally didn't do was build a cloud service around it. Most vault apps seem to push users toward creating accounts and storing data on company-controlled infrastructure. I went the opposite direction. Your files stay on your device, and if you want backups, you can use whatever storage provider you already trust.

It's my first public Android app and it's been a fun project to build. Thought I'd share it here and see what people think.

https://preview.redd.it/cvg9g0slri7h1.png?width=941&format=png&auto=webp&s=e3d41b6dc624d3f2790c440d00f41782dc9a64f5