I was thinking that maybe such idea could be applied on a Linux phone that could run all your banking apps without Waydroid's "you-must-be-a-hacker" issues, literally by having a half-asleep Android running on another chip, which you can wake up whenever to do your "non-hacker" things, while at the same time you can run the rest of your system (calls, messaging, calculator, calendar, browser...) on your lightweight, private and personalized Linux mobile OS.
I think I would pay big bucks for something like this, and it could serve as a transition device for ditching Android in the future when Tux finally governs over the world.
That already exists with waydroid. It's what people use on the Librem 5 and PinePhone to run linux apps. It would save much more battery if it were at OS level, but I assume that would be akin to merging Android and mobile linux distros and a lot more work.
Why do you have the impression that waydroid has a "you must be a hacker" issue?
Safetynet worked at some point, but it's proprietary tech that changes on a whim. Any other emulator or container will probably run into the same problem. Starting an entire new emulator with the purpose of circumventing safetynet or other proprietary attestation is an effort that could've gone into making it work on waydroid instead.
If I am not mistaken, not all apps run on Waydroid, specially banking stuff will freak out because they have systems to know that you are running on true, verified hardware or not.
Alternative utopia: do online banking in a desktop web browser while seated comfortably at home, rather than on a street corner in the sun squinting at a tiny screen.
Indeed, this is the case with Revolut, a bank which literally requires iOS or Android spyware to sign up and use. But it's rare. And a reason to NEVER USE that bank.
I agree, but if you're like me, situations arise where I'm not at home, and unexpectedly spending money. Being able to look at my bank on my phone in the moment helps me judge if what I'm about to do is worth it.
I use Bitwarden, so I just have a shortcut in my launcher to my bank's web browser page, Bitwarden autofills, and I'm in my account in a few seconds. Honestly, it might just be my bank that's the issue, but their old mobile app took longer to load than it takes me to log into their webpage anyway (and it would log me out half the time). Years ago I thought this would be an issue for me when I planned to de-google, but it turns out it's a complete non-issue (for me) and in fact I actually like the web page better. I'm able to do a lot of things in the browser that the app didn't have the ability to access (at least at the time; it's likely been updated).
Just throwing it out there that it's not necessarily an issue, and often the difference between the app and the webpage is blown out of proportion.
Anyway, full and very easy android app support would be enough. Imaging installing an android apk app via your fdroid software store without thinking about it. Just like a flatpak. That's the future I want to live in.
Pretty sure it just had an emulation layer for Android. I had a Passport when it was new, and I remember the phone was emulating a version of Android a few years old, so a few apps didn't work properly
This should work on Jolla's Sailfish OS phones as they're running a legit Android in a sandbox. Unfortunately their hardware support is pretty abysmal if you want all features working - and since it's legit Android it's also not free (monetary) and Sailfish OS's UI toolkit is also not free (freedom).
edit: also, last time I checked, Bluetooth support for Android apps is terrible, basically only audio work(s|ed).
Some Android phones can already be dual booted with (in theory) any other UEFI compatible OS. There's a whole guide on the PostmarketOS about setting up a dual boot environment.
I briefly tested PostmarketOS on a OnePlus 6T. The core functions seemed fine but overall it lacked functionality, so my plan was to dual boot with LineageOS (a degoogled android project) for the bits that really just want a true android environment to function properly, and PmOS for everything else I could manage. In the end I just wasn't up for the process of setting up a dual boot, and went with just LineageOS. Been really happy with it so far, and will probably revisit dual booting when PmOS is more feature complete.
Edit, I suppose this doesn't touch on the idea of running two separate OS's on separate chips, and it does require a reboot to get the functionality of one OS or another, but besides that hiccup you'd get mostly the same functionality out of less complex hardware.
This is not dual booting in the classical way. Imagine your laptop had 2 processors, and you could be running Linux on one, while the other processor is dormant with Windows, and wakes up when you launch League Of Legends or something. But then, you minimize LoL and you are back on Linux.