Originally posted by L_A_G
View Post
Announcement
Collapse
No announcement yet.
Sailfish OS 4.0.1 No Longer Support The Jolla Phone But Has Many Other Improvements
Collapse
X
-
- Likes 1
-
Originally posted by Almindor View PostDoes the XA2 run the latest android now? Is it stable-ish?
But please understand, you buy this phone with Sailfish OS because of the native system, Android apps are only an extra. Just like you don't switch to desktop Linux thinking about all the apps you want to run under Wine.
- Likes 3
Comment
-
Originally posted by Jedibeeftrix View Postis one better than the other?
speaking as an xa2 plus user...
If you are looking for a new device, you might wait out if Xperia 10 II gets support with this final release, and how good it is. It has newer hardware and an OLED screen. I just don't like the formfactor.
- Likes 1
Comment
-
Originally posted by bug77 View Post
I meant what's the added value? What does it do that others don't? What does it do better than others?
And Sailfish OS is a cool alternative because it is very functional OS that isn't Android, which you might or might not prefer for your privacy. I personally adore Sailfish UI and that all native apps are so consistent with it. I love that I can use my phone with just one hand, because most is accomplished through gestures and not buttons in furthest corners of the screen. Also I managed to configure MicroG well enough that all Android apps work for me. Although they work much slower than on Android, when I just need bank app, messaging apps and Firefox as a backup browser this is good enough. High battery drain (with Android support enabled) and very small device support are the biggest downsides of Sailfish OS to me, once I got used to it.
- Likes 3
Comment
-
Originally posted by Thaodan View PostBecause every Sailfish X is a new hardware adaption, possibly a new android version.
Comment
-
Originally posted by curfew View PostThis applies to all Android apps as well. Supporting a new display form factor equals to a "new adaptation". Supporting radically different resolutions equal to "new adaptations".
- Likes 3
Comment
-
Originally posted by bug77 View Post
I meant what's the added value? What does it do that others don't? What does it do better than others?
I don't need pay a thousand bucks for a phone every 1-2 years.
There Is no crap preinstalled.
It can use my Nextcloud(WebDAV) to sync calendars, contacts and files without the need to pay for extra apps.
If I activate developer mode I get a Linux terminal, a ssh-server and root access. This alone is a killer feature as it proves that I'm owning the device. I can compile and run what ever I want. I guess I could connect a screen, mouse and keyboard and use it as a full desktop after installing xwayland.
I can send SMS from my PC over SSH:
Code:$ ssh [email protected] $ devel-su # not needed if you are in the sailfish-radio group # dbus-send --system --print-reply --dest=org.ofono /ril_0 org.ofono.MessageManager.SendMessage string:"+00000000000" string:"Your SMS Text"
Code:$ rsync -avP [email protected]:/media/sdcard/0f094ac9-a065-40dc-aa42-4402c1ea424e/Videos/ Videos/
- Likes 2
Comment
-
Originally posted by sandy8925 View PostThis is the problem with trying to support ARM devices. Lack of proper closed source drivers unless you pay exorbitant amounts of money. Atleast on tablets they could've used Intel Atom SoCs with their nice open source drivers. But no, everyone's busy jerking off to their ARM fetish.
It's also more of a Qualcomm issue than an ARM issue as other SoC vendors are much more relaxed about it, but nobody else can offer the same range and particularly not the higher end of it. Apple spun their own ARM silicon to avoid being stuck with Qualcomm, their only other option after Samsung stopped selling their better SoCs to third parties."Why should I want to make anything up? Life's bad enough as it is without wanting to invent any more of it."
Comment
-
Originally posted by L_A_G View Post
I'd hardly call it a "fetish" considering there isn't much that's widely supported and fits in the smartphone/tablet power-performance envelope. Intel's low-power x86 just barely fit into it and it's Intel, a company known for highly anti-competitive business practices.
It's also more of a Qualcomm issue than an ARM issue as other SoC vendors are much more relaxed about it, but nobody else can offer the same range and particularly not the higher end of it. Apple spun their own ARM silicon to avoid being stuck with Qualcomm, their only other option after Samsung stopped selling their better SoCs to third parties.
Plus, those efforts are more recent. Intel's provided great open source drivers for atleast a decade, so they were definitely the better choice for an open tablet device in the past 10 years. But, people kept running after ARM in a crazed manner, ignoring the one hardware company that provided amazing open source support. I mean, open source GPU drivers, video decoding and encoding, OpenCL, WiFi, Bluetooth etc. All of the fundamental shit is supported and supported well. We could've had amazing, functional devices instead of having to struggle with closed source drivers written for Android. They could've gotten useful work done, but all of these projects wanted to hit their heads against concrete slabs instead.
Comment
-
Originally posted by sandy8925 View PostNobody else is offering better open source drivers, nor documentation and datasheets. Atleast in the case of Qualcomm, they're now officially contributing to and supporting Freedreno (along with Google). Broadcom is funding the development of open source GPU drivers for the Raspberry Pi. Other than those two, we have squat.
No, what's more relevant to hardware vendors are things like the task-suitability of available silicon as Intel didn't really make the low-power high-performance silicon that hardware vendors wanted due to the inefficient nature of x86 once you move into low power applications. In these applications Intel's Atom chips were either slow compared to ARM silicon in the same power envelope or then they were well beyond the power envelope of ARM chips with the same performance. Them being unsuitable for smartphone use also posed it's own problem as most tablet makers also make smartphones and making x86 tablets would mean that you'd have to make devices using two vastly different ISAs and thus have to duplicate a significant amount of effort for these two ISAs.
Let's also not even get into the fact that x86 was totally single-vendor here versus a myriad companies making ARM silicon. If Intel pulls out or decides to start abusing it's power as the sole x86 vendor in this space, a hardware vendor caught in this trap has zero good options. On ARM they can just switch to another vendor and all their code will run without as much as a recompile, which obviously isn't the case when the only escape is to a totally different ISA.
We're also talking about a space where Android, not desktop Linux, ruled the roost. While existing, Android on x86 always lagged behind ARM as Google couldn't be bothered due to a lack of vendor interest and Intel couldn't be bothered to make up the shortfall. Then at the end they just dumped a load of silicon at the market at cutthroat prices and when that didn't produce any real progress they just pulled out, vindicating vendors' decisions to not get tied to Intel's whims."Why should I want to make anything up? Life's bad enough as it is without wanting to invent any more of it."
- Likes 1
Comment
Comment