My phone is my sole PC and has been for about 7 months now. I use it for everything. I’m using nreal AR glasses for a massive virtual 80" screen via Dex. I use a Bluetooth mouse and mechanical keyboard. I use libre office for real work, I do development work right on the phone. I also use andronix on the phone for when I need a more full blown Linux desktop for gimp, IDEs, GIS, etc.

I buy cocaine with my phone

My phone is setup to pretty much do my IT job from it if I have to. I can remote into my work computer/servers and accomplish pretty much any task I need to. Its extremely handy having a foldable for the extra screen space when I need it.

This is pretty niche, but damn do I use my phone a lot to manage my Homelab server. In fact, I don’t actually currently have access to a computer, so I can ONLY manage my server via my phone.

I use JuiceSSH to SSH into my server.

I use OpenVPN Connect to connect to my server via VPN.

There’s also plenty of apps that I use to connect to the *arr suite of software that I have running for media.

Sometimes I use termux and yt-dlp or ocrmypdf because its easy and much safer than those sketchy websites. Thats it.

I don’t do much on my phone anymore.

But, I’d like to pitch in with a story from the time when I was involved with the Android-x86 project, and was testing out a bunch of things on their Android distro.

I had a Vaio laptop from 2010 that had the first gen Core i3 in it. Was pretty okay for the time specs wise, and it came with Windows 7. I used that for a while, and eventually replaced it with Ubuntu 10.10 Maverick Meerkat - probably my most favourite version of Ubuntu to date. It had all the right things - Unity, good support for most things - and it was just a joy to use.

Back then, towards late 2011, the Android-x86 team (mainly Chih-Wei Huang, but also a bunch of other folks) were hard at work making Android 4.0 Ice Cream Sandwich stable on x86 architecture. ICS had a lot of things going for it - Google were gearing up for Project Butter (I think that’s what it was called anyway), and ICS was built on the strong foundations of both Honeycomb and Gingerbread, which meant that of course it was pretty decent to use on large screen devices.

In the late 2000s and early 2010s in my country, we were just seeing the rise of Internet in the form of 3G and CDMA dongles - they weren’t fast, but they were good enough. This was also the start of the 3G revolution - smartphones were just coming out with support for 3G bands, and by smartphones, I mean Nokia S40 and S60 (v3 and v5) phones, with a couple of Samsung Galaxy SIIs thrown in here and there. Data plans were usually at a premium - 1 Gigbyte of data cost about 15 USD, which meant I needed to make a wise choice in deciding which operating system I wanted to download.

I happened to choose Android-x86, and it so happened that I would not have access to another PC or that much data for the next couple of years.

So what did I use on that Vaio that ran Android-x86 ICS? In no particular order:

• I did taxes, and paid bills
• I booked movie tickets, and ordered food
• I did a bunch of reading on the Kindle app, and on Aldiko
• I browsed a bunch of forums I frequented back then and made posts, replied to them and so on. This was mostly done on the Tapatalk app, but also on the ICS browser (yes, we had a separate browser from AOSP prior to the switch to the ARMv7 and v8 platforms and Google’s release of Chrome)
• I tagged a bunch of my MP3 files using an audio signature app that mostly got it right

For more hardcore stuff, I was also involved with a few projects in the Samsung Galaxy Y ROM scene, and I helped by testing out the ROMs on my Galaxy Y. I would download the ROM on the Vaio through the browser, use a file manager I was familiar with from my days in Symbian called Xplore to move it over from the Vaio to the Galaxy Y, then flash the ROM on the phone through Creeds version of the Samsung recovery. Oftentimes, I would need to make quick edits to the ROMs themselves by editing manifest files or oftentimes the install script for the ROM itself.

I used to use Picsay Pro editor for editing and touching up a bunch of images. All of them would get backed up on Google+ and this carried on into the Google Photos era, and eventually ended up living in Drive when Google axed the Photos free forever plan.

I used Tasker quite heavily to automate a bunch of things TBH. Back when root was a very easy thing to acquire, I would periodically backup chats from WhatsApp on my Galaxy Y, and upload it to an FTP server on the Vaio. I had a Tasker script firing on both devices at around the same time, and it used to work like a charm much before WhatsApp eventually got around to rolling out chat backups. I used Tasker to run a task to export my contacts and SMS to the phone storage.

This also being the golden era of ROMs, I used to use Titanium Backup on both my Vaio and the Galaxy Y to have a very identical setup of apps. This meant that for apps that didn’t have a cloud sync feature (which to be fair was most apps), I’d backup and transfer backups to and from the device to ensure I was working with the same set of data. I didn’t do this for all apps because the process is tedious, but yeah. Titanium Backup was also great for very quickly setting up a new custom ROM with the exact same settings as the old ROM.

I used ICS on that Vaio for almost 2 years. I used it until my first week of Uni, and I eventually switched to Linux on that laptop until I replaced it with a MacBook.

Using Android on a computer made me realize a lot of things: Android is a damn capable OS, and its vast majority of applications enrich the experience very very much. There’s almost nothing that you can’t do on Android that a computer can’t, especially when it comes to general computing needs. Android might have been built with phones in mind, but Google have put in a ton of work to make that transition over to bigger screens very smooth - I still firmly believe that Honeycomb was one of their best releases, right alongside KitKat. Both very polished Android offerings, and set the basis for a lot of things that we still use on modern Android today.

Since that time running Android on a computer, my Android based computing needs aren’t that great TBH. I rarely use my phone these days, and since I switched from my Mi A1, I haven’t really tinkered with Android much.

I still fondly recall a lot of things that made Android dear to me - like Xposed, Titanium Backup, Magisk, CyanogenMod, LineageOS, omniROM, the rise and fall of the Android modding scene on XDA Developers and the growth of some great devs like AChep (creator of AcDisplay), Paul Henschel (Paranoid Android), Francisco Franco (Franco Kernel dev), and many many more.

For me, Android will still remain one of the best computing experiences that most people can and will have. It will probably also be the first ever computing experience for the newer generations, and I think Android is poised beautifully to capture and enthrall generations of users to come.

I used my Pixel 5 as a mobile recording rig. Plugged in my audio interface via USB-C (which powered it as well), two wireless XLR receivers and used the app n-track to record an interview with an astronaut at an ESA event (lav mic on myself and the astronaut).

In that moment, I felt like a pro.

Unfortunately, the interview didn’t get a lot of views on my YouTube channel haha

Using a software defined radio (SDR). However you would need additional hardware. The most popular one, RTL-SDR works well with Android apps. There’s a lot you can do with SDRs. With my phone I mostly use it for receiving satellite imagery from the NOAA-15, 18 and 19 which transmit APT around 137MHz making it easy to receive with a simple V-Dipole antenna. Recently Meteor M N2-3 has launched which also transmits LRPT, which is digital at 4 times the resolution. Unfortunately, its LRPT antenna has not deployed properly so the signal is very poor. Ideally I’d use a Yagi-Uda antenna for that. For decoding LRPT, I use SatDump, for APT I record it as audio in SDR++, then use noaa-apt in Termux, but SatDump can decode it too.

I also use it for receiving DAB+ radio with welle.io. A separate DAB+ receiver would cost me just as much as the RTL-SDRv3 + Dipole kit.

ADS-B is also fun to look at.

Anyway, there’s a lot to do with it ranging from just listening to FM radio, up to (illegally) decrypting GSM phone calls and SMS texts. Crazy Danish Hacker has a series on the latter: https://youtube.com/playlist?list=PLRovDyowOn5F_TFotx0n8A79ToZYD2lOv but that you can’t do on a phone anymore.

Edit: I forgot to mention Android Proxy Server which is useful on school network to go through my data.

I’ve set up my old phone to forward me 2fa sms messages from my burner sim cards to my actual phone. Allows me to keep my phone number private. Pretty easy to set up with something like macrodroid.

I use the ACC (Advanced Charging Controller) Magisk module to limit how fast my phone can charge, how hot it’s allowed to get while charging and at what battery percentage it should stop/restart charging, to prevent excessive battery degradation.

I use Droidcam OBS to link my phone camera up to OBS to use as a webcam. Iriun does the same thing but without the OBS part.

revanced app for yt

If you’re using a phone with a designated desktop mode (Samsung Dex), try replacing your computer with your phone for a while. Depending on your needs, you may find you don’t often need a computer.

I’ve used mine as a bridge to my home network if I want to access it from work. Use my phone as a hotspot, wireguard VPN from my phone to home network, then connect my work laptop to my phone’s hotspot.

I already use cloudflared to expose a couple of hosted services that I commonly access remotely, but it’s nice to know I can use my phone/VPN as a quick way to get to my entire home network from any computer, without the network being publicly exposed 99.9% of the time

I occasionally use DriveDroid (root) to boot Linux ISOs.

My device also IR so Mi Remote comes in handy.