Sure it does. I can have T's & C' for my own services and so can they. They are not legally obliged to let him scrape them. Then they'd need to pay for the load. Makes no sense.
Not really the point, it costs, people need to buy it, not doing it is easier.
My wired headphones (Sony MH410c) cost me three euros. But those were often included when buying a Sony phone. A decade ago you automatically had headphones when buying a phone.
Still doesn't make it alright, but it's let's accessible now and I can see that leading to a societal change.
The issue is not the free headphones that aren't there, it's that people think having no headphones is an excuse to create an acousting hellscape for everyone around them.
We can only solve that issue by telling people all the time until they stop doing it. It seems the reason it's happening more and more is just because many others wear headphones and stare at their phones and no longer observe their surroundings. Strange times.
I've ported Mobian to the Pixel 3a and use it as a daily driver.
two annoyances:
I've not yet figured out calls via Bluetooth, but other audio works fine, including XMPP calls via Dino [if anyone knows how to get calls working via Bluetooth, drop a comment and I'll see if I can get it working]
camera is buggy and does not work well yet (there are people working on that)
Oh and I'm currently working on mainlining the Xperia 10 III with the intention of porting Mobian. I got display, GPU, flashlight working, but am stuck at figuring out whether that phone has a bug that breaks it if I enable UFS support, like some Xperias has in the past. If anyone knows a way of veriying whether it is safe to turn on flash, that'd help a lot. I could then enable UFS, Wifi, Modem, GPS, and probably Bluetooth... all at once.
Just don't want to find out whether it'll break the hard way.
Could you please link to where you found that? Maybe that's outdated info? Without the context I'm not sure what exactly is unreliable.
Phone calls work, but only if the phone is not suspended. Some people are working on letting the phone wake up when called. Haven't followed the progress for a while. If you disable suspend, is works well, at least for me. Not sure whether others have noticed issues in different situations.
Not much, the battery will just deplete quicker. Otherwise you only notice that phone calls make the phone ring. If it is suspended, it won't ring. (for now)
...but I might have made the score of the century. £30 the lot. They all boot up happily with 5v power supplied with a couple of Dupont wires and hold at least a little bit of charge. Replacement USB cables and straps ordered, so full testing will need to wait until then.
Five original Pebble watches on a desktop. Two of them have original straps, the other three have no straps.
RFC 6350 has a “Security Properties” section which only has a “KEY” field. Public keys tend to be huge; likely too big for a Vcard that will then be encoded as a QR code that needs to fit on a business card. Also too big for a Vcard that would be SMS-transmitted. And it does not take much to throw LaTeX’s QR code ...
I already have an invite flow that users will arrive at and go through when signing up, now I want to let users create invites for other users. That page does not mention anything about that. It seems to be about adding a flow that asks user for details such as an email address and then they get their account.
In my case users have already gone through that and want to invite someone else.
With invitations, you can either email an enrollment invitation URL to one or more specific recipients with pre-defined credentials, or you can email a URL to users, who can then log in and define their own credentials.
I already have enrollment invitation URLs. Just not automatically. I wrote a script that uses the API for that purpose.
The docs even mention this about the flow:
Enrollment (2 Stage)
Flow: right-click here and save the file.
Sign-up flow for new users, which prompts them for their username, email, password and name. No verification is done. Users are also immediately logged on after this flow.
I have an unused Windows tablet from 2021 running some Core M processor or other that I want to put Linux on and start using again. It doesn't have a keyboard so I would have to actually use it as a tablet and not a laptop. Is there a distro built around one of the mobile desktop environments that also runs well on x86? (Last ...
be sure to not use greeter logins and disk encryption as the on-screen keyboards (OSK) don’t work outside the DE. also, issues with non-US keyboard layouts.
Just set up unl0kr and keep safe, no need to use an installation without encryption. It's not even difficult, mainly just requires installing the package and adding the unlock script path to crypttab.
It's nice to have a device with FDE and Secure Boot, gives peace of mind in case that thing ends up in the wrong hands.
Hey everyone, I'm going insane due to a lack of creative project. I've written an app already but I haven't gotten around to publishing it yet. I'd like to know what kind of apps you'd like to see created for mobile Linux. I prefer easier, bite-sized projects over particularly large ones, but I'd love to hear your ideas ...
I've been recently porting Mobian to the Pixel 3a and posting about it here*. Now, Mobian is close to being ready, but is not yet. I've been using it as a daily driver for a few months now, but it is not what most people looking for a well-working phone would want, currently. If you want to try a well supported device now, I suggest trying postmarketOS on the Pixel 3a perhaps, they're a bit quicker than I am, mostly because more people are working on it.
The Pixel 3a has recently been called one of the best supported Linux phones with a mainline kernel. Only issue right now is the camera not producing sharp photos, but they're people working on the drivers in the kernel to improve on that.
Other than that, I don't really know what's well supported, as I focus on what I have available here.
Curious how well existing Android devices with Linux support fare currently.
Better than the Pinephone. See my other post on this thread where I talk about my Mobian port to the Pixel 3a and click the link for some more detailed info on how well it works.
Oh and the Pinephone is just way too slow and the thermal design is not really good and it also does have issues in other parts of the hardware. It's not a good phone, it's a passable development device that easily allows to turn off things such as Bluetooth.
And... an old Android phone such as the Pixel 3a is just a lot cheaper and runs way faster with a far better battery life.
No idea, but you could of course install Waydroid on Mobian. I hope Android Translation Layer (https://gitlab.com/android_translation_layer) will at some point get to a state where it is usable as the superior Waydroid alternative for many people.
No idea, but you could of course install Waydroid on Mobian. I hope Android Translation Layer (https://gitlab.com/android_translation_layer) will at some point get to a state where it is usable as the superior Waydroid alternative for many people.
Definitely do! It's a lot of fun and it feels great to have Mobian on the phone instead of having old Android on it or even a phone in the trash and no phone.
Yup. It definitely is now ready for everyday use, though there are still a few smaller issues I've got to fix. But nothing that stops me from using it now.
The only thing special about the Pixel 3a is that I had it already. Maybe it is special in that it is now the smallest Linux phone that is supported by a mainline kernel AND which is actually usable as a phone (for some other phones audio does not work, for example). Some might call a headphone jack something special... or an eSIM, as there are not many Linux phones with an eSIM.
To get involved, I recommend joining the Moban Development Matrix room: #mobian-dev:matrix.debian.social
Pretty sure we can find something where skills in C would be helpful.
It is to Android apps what WINE is to Windows programs, while Waydroid is to Android apps what something between Docker and a VM would be to server software.
Actually, Waydroid is not too dissimilar from running, for example, an Ubuntu Desktop system in a Docker container on a Debian desktop system, just so you can use snap packages... Instead of installing snapd on Debian. (Not that I want snapd.)
Waydroid is more like an Android container appliance that runs a full Android system, while ATL, as the name Android Translation Layer suggests, translates functions and API calls, used by Android apps, into the appropriate methods of doing things on a regular GNU/Linux system (in contrast to an Android Runtime/Linux system), thereby being much more efficient, more comfortable to use and having the potential of integrating into the system really well.
That one uses an SDM845, while the Pixel 3a uses an SDM670. But there's a Mobian port to that one anyway. Not sure in what state, anyway. You could flash it and find out.
Camera is probably dead because not all the code has been written yet.
My background is just playing with Linux since before I was a teen, but I did not know anything about porting to phones until early this year.
I have some experience with postmarketOS, but more with Mobian as I am more of a Mobian person. I have more exprience with their docs and community than with postmarketOS itself. Many mobile Linux projects depend on the postmarketOS wiki, as they have the best source of information.
Mobian installation is easy, just flash the images.
Mobian documentation is somewhat lacking, but I want to improve on that once I'm less busy porting. Can't do everything at once, of course.
It's okay. I like that I can do whatever I want. There are some smaller issues still, but I'm fine with those, considering all the freedom I get.
I mean, I have to set the right SIM card slot and run a command to make Bluetooth work, after every boot, until that is solved. It's not too bad. Takes me ~25 seconds.
Only annoying issue that is next on my to do list: Have the phone wake up when using an alarm clock. For now I just leave an Android phone next to my bed for that. Soon that will be solved as well. Apparently I just have to get some Systemd configuration right, but have not yet had a closer look.
Overall I am pretty happy with it. Yet I would not give it to my parents and expect them to use it like any other phone.
If you are a nerd who does need an alarm clock or a camera in their phone, or can at least work around that for now, it's already a usable phone and messaging device.
No idea how that compares to postmarketOS. I have not tried daily driving it, as instead I intend to find issues on Mobian and solve those.
Headphones work for me and should as well on Mobian. Calls via Bluetooth do not work yet, not sure how to route the audio to the headsets. But I know there's some stuff going on and people are working on improving the audio configs, should all be much better very soon.
I'm on Debian, that's the reason I asked whether anyone knows the right Debian packge. :)
For now I use the Flatpak version, but that one has other issues, it does not keep the phone awake and once it suspends Bluetooth gets disconnected as well, which is fiddly.
Pebble, Rebble, and a Path Forward ( ericmigi.com )
https://www.reddit.com/r/pebble/comments/1p0huk5/pebble_rebble_and_a_path_forward/ ...
On not wearing headphones in public places
You're given $20,000 USD (or the equivalent in your local currency) to spend, but anything still left by the end of the day you lose for good. What are you spending it on?
What actively maintained main daily driver options do we even have nowadays?
cross-posted from: ...
So, I'm not saying I made the score of the century...
...but I might have made the score of the century. £30 the lot. They all boot up happily with 5v power supplied with a couple of Dupont wires and hold at least a little bit of charge. Replacement USB cables and straps ordered, so full testing will need to wait until then.
Vcard 4-- Unable to include the /fingerprint/ of an OMEMO encryption key
RFC 6350 has a “Security Properties” section which only has a “KEY” field. Public keys tend to be huge; likely too big for a Vcard that will then be encoded as a QR code that needs to fit on a business card. Also too big for a Vcard that would be SMS-transmitted. And it does not take much to throw LaTeX’s QR code ...
Authentik: Allowing users to create invites?
Hey there, ...
gammu/gnokii: a smarter way to do SMS msging than smartphones. Esp. for TUI users.
If you sit in front of a PC with a big screen all day, smartphones are not a good way to do SMS. Rationale: ...
Migration paths from both Synapse and Prosody to ejabberd?
Hey there, ...
Recommendations for mobile Linux desktop environments that run well on an x86 tablet?
I have an unused Windows tablet from 2021 running some Core M processor or other that I want to put Linux on and start using again. It doesn't have a keyboard so I would have to actually use it as a tablet and not a laptop. Is there a distro built around one of the mobile desktop environments that also runs well on x86? (Last ...
What Apps Are Missing on Mobile Linux?
Hey everyone, I'm going insane due to a lack of creative project. I've written an app already but I haven't gotten around to publishing it yet. I'd like to know what kind of apps you'd like to see created for mobile Linux. I prefer easier, bite-sized projects over particularly large ones, but I'd love to hear your ideas ...
Follow-up Two: Mobian on the Pixel 3a / 3a XL ( lemmy.sdf.org )
This is a follow-up to my earlier posts: ...
KDE Kasts on Phosh: Icons missing, what's the fix?
Hey there, ...
Follow-up: Mobian on the Pixel 3a / 3a XL (getting close) ( lemmy.sdf.org )
This is a follow-up to my earlier post: ...