erebion

@erebion@lemmy.sdf.org

This profile is from a federated server and may be incomplete. Browse more on the original instance.

erebion,

A bunch of marketing blah blah, I wonder what they’re up to.

erebion,

Sending all the voice messages I get to some server? Uhm, no.

Great idea in theory, though.

erebion,

Do you get fined if you are unlucky to have no harvest and cannot bring anything back?

erebion,

Matrix is not the right protocol for staying anonymous. There’s way too much unprotected metadata.

You might be able to mitigate that somewhat by using an instance that is accessible via TOR and being careful who you communicate with, depending on threat models and so on.

But if you want to communicate anonymously and not leak meta data… Probably not what you are looking for.

erebion,

I don’t know what would fit your needs, but Signal does not require Play Services. And even if those are present, it does not leak data to Google. Other than “Signal is installed” and “You get a push message”, Signal does not put your messages into the notifications. Instead Signal connects to the Signal servers and then gets the encrypted messages from there and only then decrypts.

Even if you have Play Services installed, you can force it to use a background connection inatead, if you disable Play Services before installing Signal, it wall automatically fall back to it.

If you want a version without Play Services libraries, you could use Molly, a hardened version of Signal, which is available in a version without those libraries.

Molly even allows linking phones as secondary devices, not just desktops.

erebion,

Not having systemd was always the only reason I did not seriously consider using it, now I will have to re-consider.

erebion,

Only if you have a different use-case or if you are a fundamentalist. Most software is not inherently bad, it just might not be what you want.

erebion,

Pretty much the only one.

Though there’s also Neochat fron the KDE F-Droid Repo.

erebion,

Oof, hopefully you have photos at least.

erebion,

Did you try Flare yet?

erebion,

Not yet. You can link it to a phone or register with signal-cli and link it to that.

erebion,

Oh, I don’t mind questions. :)

Help: A lot via the Mobian Ports ( -ports:matrix.org ) Matrix room and the postmarketOS offtopic ( :postmarketos.org ) Matrix room.

Sources: Not much there yet. As soon as there are official builds for the Pixel 3a, I will start writing docs. I already have a lot of notes on what I had to do. But first I need to have someone merge the Kernel patches, as I don’t know C, which makes resolving merge conflicts really hard, it turns out. Once that is done, there are just a few smaller merge requests left and builds will appear magically.

The whole process is not that difficult if there are already Kernel patches available. In the case of the Pixel 3a, I only had to clone the sdm670-mainline repo ( gitlab.com/sdm670-mainline/linux-patches ) , compile the kernel (two commands) and get a .deb, which I used with mobian-recipes ( salsa.debian.org/Mobian-team/mobian-recipes/ ) to build an image. I then wrote a config file for droid-juicer ( gitlab.com/mobian1/droid-juicer/-/…/4 ) which tells it what files on the vendor and modem partitions it should get, then those are copied to /usr/lib/firmware/updates/.

That was easy as dmesg will just tell you what files it cannot load because they are missing. Just find those, write the config, run droid-juicer, reboot… boom. Display, Wifi, LTE and so on working.

Then smaller stuff like udev rules for vibration and an initramfs hook ( salsa.debian.org/…/qcom-firmware?ref_type=heads ) so that firmware files get integrated into initramfs and components start to work early during boot.

The most difficult part would be merging the Kernel patches with other patches and resoving the merge conflicts… At least to me, as I don’t know C.

If there are no mainlining efforts for a phone yet, then I don’t know what to do, as that requires a Kernel dev.

For the Pixel 4a you mentioned, there is a postmarketOS port. So this should be doable. ( wiki.postmarketos.org/…/Google_Pixel_4a_(google-s… )

That’s all not that hard, my main difficulty was finding out what to do. Everything I did so far would be an afternoon of work, if I had just found the necessary information much quicker. Instead I spent two weeks, of which 95 % was finding info, lol.

Just join the Mobian Matrix room, we should be able to help you, even though I know far less than the others there…so far. :p

I do hope that’s helpful and I’ll happily try to answer more questions. :)

Kernel mainlining effort for the SoC in thr Pixel 4a: github.com/sm7150-mainline/linux

erebion,

Nope. They look differently and have different functions. PostmarketOS wiki has screenshots: wiki.postmarketos.org/wiki/Category:Interface

erebion,

Not exactly. But while UBPorts has a good looking user interface, they don’t have many UBPorts apps yet. A regular distribution can often be more useful, but as always it depends on the use-case.

erebion,

Same, my Pinephone does that within an hour maybe xD

erebion,

Those are impossible to hard brick in my experience, you would need to break both bootloaders and recoveries. See if this helps:

flash.android.com/welcome

Also, Pixel 3 has different hardware, but is supported by pmOS and I’ve spotted some commits in Mobian, so there might be people working on it there.

erebion,

Exactly my thought, but isn’t that breadboarding then?

erebion,

You could join the Mobian Matrix room or the PostmarketOS room I have mentioned in another post on this thread (or whatever the right term is… Comment on a post? Sub-post?). I did not know anything about porting two weeks ago, but asking dumb questions helps learning.

erebion,

Phosh, Gnome Shell for Mobile is still in develoment and not packaged for Debian yet. As far as I know, it is only packaged in postmarketOS.

erebion,

Cool! Well, it’s just a merge conflict. I don’t knoe how to combine the patches. Should be pretty easy for someone that does not need to google for every line of C.

I can give you notes* later on what to do to get to the conflict, then maybe you can resolve it and push the result to some repo? :)

*Just 3 or 4 commands, I think, including the Debian gbp command

erebion, (edited )

So, a lot of commands, but not very complicated:


<span style="color:#323232;">git clone https://gitlab.com/sdm670-mainline/linux
</span><span style="color:#323232;">cd linux
</span><span style="color:#323232;">git remote add mobian https://salsa.debian.org/Mobian-team/devices/kernels/qcom-linux
</span><span style="color:#323232;">git remote add kernelorg https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
</span><span style="color:#323232;">git fetch mobian
</span><span style="color:#323232;">git fetch kernelorg
</span><span style="color:#323232;">git checkout mobian-6.7
</span><span style="color:#323232;">git checkout -b mobian-6.7.2
</span><span style="color:#323232;">gbp pq import             # so you end up on the `patch-queue/mobian-6.7.2` branch with all the patches in debian/patches applied
</span><span style="color:#323232;">gbp pq switch             # switch to patch-queue/mobian-6.7.2
</span><span style="color:#323232;">git rebase v6.7.2
</span><span style="color:#323232;">gbp pq rebase             # (rebases the patch-queue branch on the now-rebased `mobian-6.7.2` branch)
</span><span style="color:#323232;">
</span><span style="color:#323232;">git checkout origin/on-stable
</span><span style="color:#323232;">git checkout -b temp-sdm670
</span><span style="color:#323232;">git rebase patch-queue/mobian-6.7.2
</span><span style="color:#323232;"># this is where I got and get the conflict, the rest *should* be correct
</span><span style="color:#323232;">git checkout patch-queue/mobian-6.7.2
</span><span style="color:#323232;">git merge temp-sdm670
</span><span style="color:#323232;">gbp pq export # switches to mobian-6.7.2
</span><span style="color:#323232;">#all new patches should be straight under `debian/patches`, create `debian/patches/sdm670` and move them all there
</span><span style="color:#323232;">mkdir -p debian/patches/sdm670
</span><span style="color:#323232;">mv debian/patches/*.patch debian/patches/sdm670
</span><span style="color:#323232;">#edit `debian/patches/series` to:
</span><span style="color:#323232;">#1. reflect that files have been moved to `sdm670/`
</span><span style="color:#323232;">#2. ensure patches from the `ath10k`, `debian` and `mobian` folders come last in the list 
</span><span style="color:#323232;"># commit changes (this commit will be amended afterwards)
</span><span style="color:#323232;">vim debian/patches/series
</span><span style="color:#323232;">git add -A
</span><span style="color:#323232;">git commit -m "added patches from the sdm670-mainline repo"
</span><span style="color:#323232;">gbp pq drop
</span><span style="color:#323232;">gbp pq import
</span><span style="color:#323232;">gbp pq export --drop --renumber
</span><span style="color:#323232;">
</span><span style="color:#323232;"># push the branch somewhere
</span>

I’ve added some comments to hopefully make it easier to figure it out

erebion,

Depaving the way to a bright future, love it.

erebion,
  • user names cannot be changed
  • never delete your database, have backups, all the state is in there, if you lose your DB, you essentially have to set up a new server: Your server will say you are not in a room while others say you are, so you cannot join. Always keep your DB backed up.
erebion, (edited )

Could be both that and burn out and/or depression. Talk to a professional, not the internet, about this.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • megavids
  • kavyap
  • DreamBathrooms
  • thenastyranch
  • ngwrru68w68
  • tacticalgear
  • magazineikmin
  • Youngstown
  • khanakhh
  • rosin
  • slotface
  • InstantRegret
  • everett
  • mdbf
  • JUstTest
  • cubers
  • GTA5RPClips
  • cisconetworking
  • modclub
  • ethstaker
  • osvaldo12
  • Durango
  • normalnudes
  • tester
  • provamag3
  • Leos
  • anitta
  • lostlight
  • All magazines