Earlier quoted context omitted.
What do you mean by "permanent"?
My specific definition: 20 years later when a retired me boots up the device, it will be able to run the calculator app without shutting down.
Furilabs Linux Phone
151–160 of 259 posts
Re: Furilabs Linux Phone
#152Earlier quoted context omitted.
I think adults should read 'majority' when someone says everyone. I will keep saying it when talking with adults as it is just easier than put all the exceptions; if some people get annoyed by it, that's not really my problem.
Alternatively you could use 'most people', or any one of several equivalent expressions, and preserve the meaning of everyone as every one. There is an aroma of manipulation around using language that gives the impression of absolute consensus even if all parties involved understand its vernacular meaning. It's embellishment in service of influencing people and rightly denounced in any context where accurate communic…
Re: Furilabs Linux Phone
#153I'm so desperately looking for a DIY portable device that does not suck to build my portable audio player, best case supporting android with any of the following custom roms: LineageOS CalyxOS GrapheneOS /e/OS I even considered making a player myself using the T113-S3 SoC, unfortunately not having the required skills. There are so many people trying to build prototypes, but this seems to be a space that is not easy t…
Not Android, but it's an open-source music player: https://www.crowdsupply.com/cool-tech-zone/tangara
In Android, headphone remote works out of the box... that's why I would like to use one. There is the HiBy M300, which in my opinion would be worth having a custom rom :-) Indeed there seems to be efforts.
https://github.com/reindex-ot/hiby_digital_m300
https://www.head-fi.org/threads/hiby-digital-m300-android-di...
Re: Furilabs Linux Phone
#154Apparently it is based on Halium, so it's probably not going to run mainline Linux any time soon. On the other hand, I'm less happy with Android than I pretty much ever have been, so having some more options outside of relatively unusable Linux phones and being stuck with modified Android firmware certainly does not hurt. I am definitely interested, especially if the team working on it is as active as it seems they a…
I work on this device. We are currently QAing the latest update with our community, which contains a lot of goodies and improvements shaped directly from community feedback. You can see previous changelogs at https://furilabs.com/changelog I am obviously a little biased, but this is probably the first Linux phone that people can actually use. Someone in our community switched from iPhone to this without much of an is…
Re: Furilabs Linux Phone
#155Earlier quoted context omitted.
Afraid not. These things usually require hardware attestation to ensure you're running the exact software Google wants you to run. Now, if someone figured out a way to bypass it, that would probably work for a bit. But it's a cat and mouse game.
It's not just what Google wants you to run, it's what Google promises to some of its customers through a face it has on one of numerous facets(facing banks in this case) as what they let users do with phones, and a humanware chain of trust that allows the server and the phone to be viewed as sort-of secure computing environment. From an idealist standpoint, it shouldn't be done that way by taking away rights from use…
Re: Furilabs Linux Phone
#156Earlier quoted context omitted.
LTE set that back by a lot. For years there were no VoLTE implementations in common use other than stuffs on Android. Even those had compatibility issues and lots of carriers still block unapproved clients trying to register on VoLTE. For 3G, you could always do that. You only needed the right modem module with voice call support and audio I/O, like bare PCM pins, and a host micro to handle AT commands.
> there were no VoLTE implementations in common use other than stuffs on Android What's wrong with the Android one - is it not permissively licensed? I think the biggest problem of Linux phones is the community's obsession with trying (and failing) to reimplement (multiple times, in parallel) things that Android does really well and can be used as-is. That's why the PinePhone or Librem 5 still can't even match the us…
There were pointless debates around ITU-T and 3GPP as to whether the LTE is 3.5G or 3.9G or 4G next to the pink fact elephant that _it_ is going to be _the_ next cell standard anyway. That hot debate delayed voice call discussions to post-launch matter that eventually coagulated as the VoLTE.
The Voice-over-LTE was a total kludge together that were(ARE) carrier specific implementations. In Japan at least, it seemed to have had push from KDDI, esp. with hindsight that NTT docomo and Fujitsu, both formerly influential in 3G, both seemed on fire majority of that timeframe, while Nokia being a supernova beyond fire. It would be very natural if Samsung would have made vital contributions, but I don't have much informational pressure from that direction. VoLTE is phone company mannerisms, remnants of retro-futuristic media features of 3G, weird spaghetti codes from carrier labs, and international call exchange system, all homogenized in a blender; the artefacts were co-developed pair of server and client implementations that are standardized in the way there aren't many implementations but not something carefully spec-worked before construction for interoperability. That all happened ~a decade ago. Some point between Android 4 to 10.
I suppose it was all retconned into 3GPP standards after action, but the whole stack is still like a lobotomized Android call app and private fork of Asterisk embedded into the cellular core monstrosity. I guess embedded modem people(like Quectel) had finally got to port functions into modem chip firmwares so they can make calls, after someone done it for non-smartphones(KaiOS, Smarterphone...), I think around 2019 +/- 1 year.
What I'm trying to say is, VoLTE is complicated. It's something like SIM-authenticated SIP/RTP over IP under IP, not even regular 3G data session let alone SIP-VoIP on Layer 3 UDP/IP.
Osmocom project Wiki summarizes it better than I[1]: "Voice over LTE is an adaptation by 3GPP to use IMS over an LTE cellular network. The LTE EPS (Evolved Packet System) provides the functionality of the underlying IP-CAN. ... IMS is much more than normal SIP/RTP. And in addition to that, there is a tight integration between the LTE system and the IMS on top of it."
And it's supposed to be the core feature of a phone, "not".toupper() a party trick... There are better things to do in life for most people.
Re: Furilabs Linux Phone
#157If in any doubt about whether to buy this, look at Planet Computers offerings and the quality of their Linux build. They have been offering Mediatek-based Linux phones for several years. Spoiler: garbage with ancient proprietary kernel, thanks to Mediatek
Re: Furilabs Linux Phone
#158Earlier quoted context omitted.
Microsoft at one point was running full NT on ARM on phones. I think they could've done it within such price range, but didn't.
Didn't they? The Lumia 950 launched at about $500ish and supported Continuum. Continuum wasn't exactly full convergence, but it was kind of close. As I recall, they had a desktop dock and a laptop like dock, that you could pair your phone to (wireless or wired). Microsoft was big on their 'universal windows app' concept at the time, where universal meant actually only ran on a small fraction of windows devices. sigh
Re: Furilabs Linux Phone
#159It's on HN here:
Re: Furilabs Linux Phone
#160Earlier quoted context omitted.
> that can actually, imagine this, make and, to complicate matters even further, even take calls Showing how different different people are. I've probably made... 20? ish? phone calls in the last decade. (I'm 46.)
Holy moly, you must have very different life than most people I guess. I am from the younger generation which supposedly avoids making old-style phone calls as much as possible and I don't think I know anyone who has made less than 100 calls in the last decade.