Isnt APK the alpine package mangager? (which would mean they didnt made another package thingy)
As I use neither aas (cant as I use faifphone 4) nor waydroid (not sure if waydroid would work) I really can understand some of your issues especially the browser one, as angelfish is only a current workaround (which also lacks some basic things like copy/paste into other applications).
Also, not sure if I’m correct, I think piggz does not work for jolla so if he decides to stop working on angelfish nobody updates this browser anymore.
Regarding the firefox update, again not sure, but I think currently the goal is to update to esr101 (which is also outdated) to then maybe be able to easy update to a then also outdated firefox version?
Yes; you got it wrong. Don’t just assume the worst about people.
Firefox on Android uses special Android bindings and a special Android UI that isn’t helpful here.
Features are not actively removed - nobody just added GUIs for them yet.
What’s possibly on offer to share effort with is
It isn’t a perfect experience either, and it would take a lot of compositor work to get running.
Okey, didn’t knew about it. This changes everything in this case.
This would be nice - there would be no need to like do a lot of development, but to just somehow make it easier to provide it on SFOS would be cool.
If this would be available, then they can do their own browser as they want - as long as reliable and up do date solution is available.
As you would have immediately android app support with this option, wouldn’t it be best? Check all necessary apps from this forum if they work or not. I have done the same and only it seems that Snapchat isn’t currently working of those apps I use now. Edit: Also the possible TOH could bring something completely new to the table that others don’t have
Regarding apps, you might be able to even use the Thunderbird with AAS. Signal can be replaced with native Whisperfish, Newpipe can be replaced with native Sailpipe and Bitwarden with native Bitsailor. There is quite a big list of native clients, you just need to find them
OH, YES. I’m so wrong.
The whole PMOS is based on Alpine Linux, so it all makes sense. I thought that it was based on debian or something, but that makes sense now. Still it’s an unfortunate extension in this case, but not their fault. We need mobile Flatpak though.
I’m not so sure, although it is ‘convenient’ for developers. The effort that @rinigus and @piggz have undertaken, first with qt5.15 and now with qt6 is a better bet, I feel. But that’s kind of a personal feeling thing. I dislike flatpak because you wind up with 12 versions of the same no longer updated library on your device (ie. desktop). It’s the same with AppImage, and worse. It’s one of the reasons I dropped using the mac entirely since you couldn’t work on applications with shared libraries without a real headache. If you only care about ONE app, it’s great. Fire and forget. But, what if you maintain multiple applications using the same libraries? So you package those same libs 5 times? ummmm.
Well, I’m using GrapheneOS, so if something doesn’t work here, then it probably doesn’t work with AAS an vice versa - so it’s not an issue, because I’m probably avoiding it already.
I didn’t notice those. Didn’t knew about Sailpipe & somehow I cannot install this - it says I have wrong architecture - I have aarch64 & package is aarch64
Yeah, all of this is kinda dependent on the state of the whole OS when the phone will be released (also money situation plays the big role here). Fairphone is more repairable & Xperia 10 VII is smaller. If Jolla 2 would be 6.1” or 6.0” I would go with this immediately - 6.0” is perfect for me.
Also I hope Jolla will design the phone to have a 3,5 mm Jack.
The user-space is 32-bit, the kernel is still 64-bit. Not sure how to trivially check - here it is just a well-known fact. It is an ancient phone. Use a package manager (or store client as applicable) - don’t download and sideload apps. Not only will you get updates, you also won’t have to bother about what architecture you are running.
Okay. First - it’s not going to be solved because:
XA2+ is already old & it was underpowered when it was released (Sony has a habit of selling hardware with lower model of SOC for a higher price) & with AAS & web browser inside it I would expect it to be even worse. I would love to test it at least with Waydroid, but I doesn’t want to boot (I did a lot of tweaking to make it work, but it didn’t).
Also why would I even consider paying for something, that I can get with just a flash of LineageOS for free…?
Now you are also missing 1 angle in all of this - I’m also testing the OS to some extend, it takes time.
When you have mediocre or even bad experience with trial version would you want to pay for a full version??? It’s a fixable ,bad experience” but still not good enough for me to want, to pay for an OS as much, as the phone is now worth on second hand market.
Check with 
