Make your own badges, or select some of the ready made ones – like this one:
Trying out /e/
So starting this morning, I’m trying out /e/ on my Google Nexus 5 phone. Haven’t tried much so far, but set up a few contacts, email – the provided mail program is a fork of k9 which is nice, and I took some screenshots:
Of course the battery of my older phone isn’t as good as a new one, still have to see how long that will last between recharges. And the geolocation – see weather widget – is also not very precise, but that isn’t the phone’s fault, every other machine here which uses IP based geolocation based on the router’s address would show the same. The weather by the way is drawn from OpenWeatherMap, same as the weather widget in Gnome on Linux – very nice.
And yes, it looks like an iPhone, doesn’t it? But it’s an ePhone instead, with only free and open source software. So far I like it, even if it hasn’t (yet) all the bells & whistles of a modern Android, but let me explore more about it first…
As always, thanks for reading.
Update, from 13:49:
Not missing much so far… I’ve downloaded my own albums into the /Music folder on the phone, and the app shows them nicely:
So far, this all looks like a fully functional mobile phone. Have to interrupt for now, so more later…
Update2, from 16:11:
Just sent Mitchie to work, taking only the Nexus instead of my Pixel phone. And I had installed OsmAnd for offline navigation:
And what shall I say? That older phone with /e/OS connected to our Yaris Hybrid with Bluetooth, it played my music over the car stereo system and told me the route via OsmAnd, warning me about every pedestrian crossing (you can silence that if they’re too many). Perfect, and all of that without even inserting a SIM card into the device! Wonderful.
Again, thanks for reading – and more later.
An experiment in de-Googling
A week ago, we swapped some phones. Mitchie got a new one, Zuleikha got her Pixel 4a 5G, and Zuleikha’s 3a went to my brother Willi in Cologne after packing it like this:
Which means that by now, I have the oldest phone in the household. Mine will still be supported until August next year, and by then I’d have to decide what other system to put on it. I wanted to test some, but not on my working phone – instead I grabbed for the much older Nexus 5 which we still have:
This isn’t supported even by LineageOS anymore, except if you’d install some unofficial custom ROM or even build one yourself. But that is currently a bit too much even for me, so I checked and found a supported environment in the e.foundation which looks like this:
So this afternoon I first charged that device, and when turning it on I first got a bist nostalgic, seeing that cute animated robot during the boot process, but anyway, it had to go. And now I have /e/OS on it:
What you can also see in case that you know /e/OS is that I already installed two more apps, namely F-Droid and Zapp (and by now, also Firefox Focus).
So – it will be interesting to see how this goes with no Google services on board. The installed MicroG fakes some of them, so that you can still get notifications, or run Google Maps if you’d need that – but I’ll try to keep it safe and simple. Will be interesting… and who knows, maybe I’ll even prefer this newly found privacy? And there’s no reason to dump a perfectly fine phone which isn’t even 10 years old… and it has a screen of under 5 inches which is FullHD and beats the current iPhone SE, go figure…
Anyway, like always, thanks for reading.
Cookie from my phone’s camera
Yesterday I’ve been watching a video on my phone when Cookie decided that he wanted some closer proximity, so he came and laid down with/beside me:
This is straight from my phone’s camera, no editing whatsoever:
As always, thanks for viewing.
It all adds up
Or: your low latency is not my low latency
With makers of mobile phones and even notebook computers ditching the headphone sockets, more and more people have come to accept in-ears and headphones without cables, most of them using Bluetooth technology to transmit the audio to and from your phones, notebooks, computers, and so on.
And some people – like those playing games – noticed that it takes some time to get audio “streamed” to your wireless cans or in-ears, and that there can be lags between the picture they see, and the sound they hear.
But that’s not the worst. Even with “low latency” Bluetooth codecs – aptX speaks of 40ms – they still forget that there are people for whom this is much too much.
Musicians for example – some people claim that they can hear latencies of around 10ms (I can’t), and so we all set our audio interfaces to the lowest possible settings to achieve latencies of possibly 5ms or better – otherwise it would be hard to play in time with what you hear from others’ tracks coming from your DAW (digital audio workstation). We spend quite a lot of money to get interfaces like from RME or other professional vendors which can give you these low latencies – and then we should add 40ms for the Bluetooth cans only? No way.
Which is why musicians like Zuleikha or myself will always stay with cables, and only buy devices which offer a proper headphone jack. There’s no way around it. KISS principle anyone?
You probably don’t mind the lag if you’re listening to your phone while jogging. But we do – we simply have to. And we’re the ones you’re listening to (or so we hope, but I speak for all musicians here).
So please stop these claims of having ‘low latencies’ if you don’t even consider musicians.
Thanks.
Sustainability & privacy
The problems that we all have with our “smart” mobile phones are two-fold – first, their vendors decide on how long you can use them with their support, second, they spy on you, me, and us all.
I wrote about the first problem lately, with Zuleikha’s Google Pixel 3a being supported until recently. It still runs Android 12 which is newer than what the vast majority of people have on their phones (according to Google’s stats), but it won’t get the next version 13 or any further security updates, thus it will be increasingly insecure.
There are mostly two alternative operating systems to remedy that, namely LineageOS and /e/ which is also based on LineageOS (and both are based upon the Android Open Source Project, or short AOSP). The differences between these are mostly that LineageOS by itself doesn’t use Google services (if you don’t install them), and is a bit harder to install especially for beginners, while /e/ comes with microG services which mostly replace Google’s services (which spy on you). There’s also a fork of LineageOS with microG, keep that in mind as well.
About that ‘spying’ and privacy part: here are two videos in German which concentrate a bit more on that part, and less on the sustainability aspect, so the first one also mentions GrapheneOS and CalyxOS, two alternatives in regard of security rather than longevity:
So yes, both GrapheneOS and CalyxOS run fine – on Pixel devices as long as these are supported by Google. But if the sustainability *and* the security aspects are equally important to you (as they should be to us all), then have a look at /e/ and/or at LineageOS, with or without microG.
/e/ by the way has its ‘Bliss’ launcher which looks much more like iOS rather than Android, but that could be changed with a few (non-mouse- but finger-) clicks. The look of it really reminds me of the iPhone SE (2020) I had for a while from my former employer, while LineageOS has the same ‘MaterialU’ (or whatever the name is) design language that the AOSP and also Google’s own Pixel devices are using. So choose your poison here, can’t discuss about aesthetics…
And /e/ also supports a number of devices still older than the ones supported by LineageOS, like for instance Google’s Nexus 5 (made by LG which was wonderful). It will still run a fork of Android ‘Nougat’, but hopefully by now a bit more secure than the original one…
There are many more videos, also in English, which explain all the differences between these operating systems, just wanted to push some of my own relatives into the general directions with the two from above.
And as always, thanks for reading, and for viewing.
Now that sounds like progress on the ARM front
The Linux kernel 5.19 is out. And it seems that Linus wrote his announcement on a Mac (with the newer M1 architecture) running Asahi Linux…
See also on lwn, The Register, or Phoronix – and probably soon all over the media… but don’t run and buy Macs for that right now, Apple does still not support Linux. And buying the latest and greatest hardware is – as we say in Germany – like “stitching with a hot needle”.
As always, thanks for reading.
Bits from DebConf ’22 in Prizren, Kosovo
The Debian developer team have been uploading videos from their latest conference, and so far I’ve seen two of them which I found very interesting, these were
The current state of Debian on smartphones by Guido Günther, and
Lenovo Linux 2022 by Mark Pearson.
See the whole list of talks in case you are interested, which I’ve found via Planet Debian and Bits from Debian. Always interesting to see some faces I know, even if I haven’t seen them in years (hello Steve!) 🙂 And thanks to all of you Debianistas for all of the great work you’re doing!
Edit, from July 31st, 2022: Phoronix also reported about Mark’s talk from above.
ネコ
ネコ means ‘Neko’, which is Japanese for ‘Cat’. And I think that’s the title of this song with some incredible bass playing in it:
I don’t know who played that bass, but it seems that the song is track number 7 from this album from composer Yuki Hayashi. Found via TalkBass.
Deep Dark Blue is album of the day again on Wikiloops
My friend and fellow musician OliVBee from Wikiloops made an exceptional album in 2017, that was before I even had joined the ‘loops. He called that album after one of the songs’ titles, Deep Dark Blue, and I had written about and reviewed it some 3 years ago already. It’s one of the best albums I’ve ever heard *anywhere*, and this one is available only at the ‘loops:
You can listen to it on Wikiloops in its entirety. If you’re a member in Wikiloops you can also download it including a cover, so you could burn this onto a CD if you like. You can do the same as a non-member of the ‘loops if you get what we call a download ticket, starting at 2,40€ like here (you’ll get this when pressing the download button on the album’s page):
I *am* a (paying) member, and I’ve still also paid for some of these albums, because they’re worth it, and because that way, we support ourselves with keeping that platform alive and running. This is especially important since these days of Corona, and because not everyone can go out and meet other musicians (and not from around the globe as here). So if you can, go and pay for an album or two of your choice, that would help us all – thanks.
Being at it, I’ve cleaned up the home screen of my phone yesterday, and this is how it looks now:
And I don’t know if you can see it in that image, but I’ve replaced the standard Chrome browser button with one of Firefox, which leads directly to the Wikiloops start page:
Even if not that many people see my phone’s home screen, I’m still putting an ad for Wikiloops proudly in the middle of its screen. This is to say thanks to my friends and to Richard, the founder of the ‘loops.
And before I forget it: thanks also to Anne, and to all of the other wonderful musicians on Oliv’s great album! Last not least, this album is also a master class for us bass players… *and* with top pro drummers to boot! 🙂 Did I mention that I love that fretless guitar which Oliv is playing?
As always, thanks for reading (and probably for listening or even supporting us).