21–30 of 169 posts
I personally would avoid anything Manjaro related due to recurring controversies around the project leadership: https://www.reddit.com/r/linux/comments/hxpj87/change_in_man... I wish PinePhone would partner with Arch or Debian instead.
I personally would avoid anything Manjaro related due to recurring controversies around the project leadership: https://www.reddit.com/r/linux/comments/hxpj87/change_in_man... I wish PinePhone would partner with Arch or Debian instead.
The Mobian[1] project (Debian for PinePhone) is doing very well.
A Mobian PinePhone edition is possible - but in the meantime people can install the OS on existing PinePhones.
Do these support Android apps? How would I develop a native app for one of these?
> Do these support Android apps? They do not, at least not yet. They may support anbox at some point, but that's not a given. > How would I develop a native app for one of these? The same as you would for any Linux distro. I would check out Plasma Mobile, as they have toolkit's and a workflow already in place is my understanding.
And hopefully never. Almost all Android apps rely on the closed-source GMS for essential functionality (eg: push notifications). There will need to be an open alternative to GMS if the goal is to support Android apps but a better idea would be to abandon Android as template basis going forward.
I personally would avoid anything Manjaro related due to recurring controversies around the project leadership: https://www.reddit.com/r/linux/comments/hxpj87/change_in_man... I wish PinePhone would partner with Arch or Debian instead.
The drama of Manjaro leadership notwithstanding, does the distro work on the phone?
I personally would avoid anything Manjaro related due to recurring controversies around the project leadership: https://www.reddit.com/r/linux/comments/hxpj87/change_in_man... I wish PinePhone would partner with Arch or Debian instead.
> I wish PinePhone would partner with Arch or Debian instead. The Mobian[1] project (Debian for PinePhone) is doing very well. A Mobian PinePhone edition is possible - but in the meantime people can install the OS on existing PinePhones. [1] https://mobian-project.org/
Earlier quoted context omitted.
> Do these support Android apps? They do not, at least not yet. They may support anbox at some point, but that's not a given. > How would I develop a native app for one of these? The same as you would for any Linux distro. I would check out Plasma Mobile, as they have toolkit's and a workflow already in place is my understanding.
> They do not, at least not yet. And hopefully never. Almost all Android apps rely on the closed-source GMS for essential functionality (eg: push notifications). There will need to be an open alternative to GMS if the goal is to support Android apps but a better idea would be to abandon Android as template basis going forward.
I think getting people onto devices that support open and flexible alternatives is the first step to actually converting users to these alternatives. I won't switch to a platform that doesn't let me communicate with people I know, and I wouldn't expect others to do so either. However, I could get people to switch from a less convenient option (e.g. Signal on Anbox) to a more convenient option (e.g. Matrix for messaging) in time.
Can someone help me understand the relationship between phone hardware and carriers in the US? I recently bought a new, unlocked Samsung phone on Amazon. When I put a Verizon SIM card into it, a Verizon-specific firmware module got added. I don't understand why that would be necessary. Asking because I'm attracted to the idea of a phone I truly control, but not sure what that means for carrier compatibility.
Sprint (which is now T-Mobile) has required an activation app for their CDMA devices called SprintDM. Without it, phone will not activate and work. Most alternative OS like LineageOS don't include it, but if you activate on stock OS and don't wipe modem partitions, it continues to work. Thankfully they are transitioning to T-Mobile network.
AT&T has no activation crap but may not let imported devices based on IMEI numbers they don't have.
(PS: I know supremacists will claim Android is linux but the thing about supremacists is they no real ideals so they will ignore how close Android is)
I personally would avoid anything Manjaro related due to recurring controversies around the project leadership: https://www.reddit.com/r/linux/comments/hxpj87/change_in_man... I wish PinePhone would partner with Arch or Debian instead.
Word. Debian is great! In the past when I see people using Ubuntu, I always wondered why? It is so interesting how people in tech just fall into the fashion trap.
Can someone help me understand the relationship between phone hardware and carriers in the US? I recently bought a new, unlocked Samsung phone on Amazon. When I put a Verizon SIM card into it, a Verizon-specific firmware module got added. I don't understand why that would be necessary. Asking because I'm attracted to the idea of a phone I truly control, but not sure what that means for carrier compatibility.
T-Mobile and Verizon should allow any modern device. Verizon used to need a activation conponent for the CDMA radio but modern devices just use LTE and voLTE. They did have a visual voicemail blob that used to be pulled in, but now they follow spec and don't require anything special. Sprint (which is now T-Mobile) has required an activation app for their CDMA devices called SprintDM. Without it, phone will not activa…