• 2 Posts
  • 19 Comments
Joined 8M ago
cake
Cake day: Apr 26, 2025

help-circle
rss

never once succeeded in any meaningful way that I’m confident I can lose the thing and restore it on another device.

I do a full backup. transfer the backup file to the other phone. initiate restore - errors, incomplete data, apps are never to rarely transferred, a total mess. phones aren’t the same but are similar (SDM845) and the same LOS 22.2 with microG and magisk.


can you expand on the backup and possibly restore that worked for you? no solution I tried on a rooted lineageos worked, tried phone to similar phone and restore to same phone after wipe. tried adb, seedvault, neobackup, a couple others (anything with backup on fdroid) none worked remotely acceptable.


thanks for the linked writeup, always new stuff to learn.

I’m on 6T and mobian, how’s your luck with taming cameras?


them dudes should allow us paupers to get at the “furyos” with our shitty $50 phones. or at least put the evidently complete product it in the hands of someone who ran linux phones (i.e. experience with mobian, pmOS, phosh, etc) instead of confused youtubers swiping the same two screens left/right not undestanding dick about the issues.

I am not spending a multiple of the total of all my hardware combined in order to find out it has the same performance and issues my oneplus 6t with mobian has.

y’all with the graphenes and co., respectfully, you don’t understand what you’re talking about.


the wall of shame is an awesome resource for us looking to get at cheap, discarded phones. thanks!


can you share some of the things regarding MTK unlocks? when looking for cheap used devices I’ve routinely skipped over MTK devices thinking that unlock is impossible and, more importantly, there aren’t ROMs for 'em.

also, look at mobian. UT (at least in my case, SDM845) requests that the phone should be at the stock android image (9.0) which I find virtually impossible to downgrade to.


no such thing exists. there’s a buncha stuff claiming to do it but I’ve tried everything there is and everything fails differently, but consistently.

source: tried for close to two weeks to create a perfect clone to a similar phone (Poco F1 to Oneplus 6T - both have the same SoC, LineageOS, rooted) so that all apps and settings and storage and whathaveyous are copied and I failed. even the supposedly standard backup - wipe - restore, on the same phone, doesn’t work.


tried it on three different models, no perceptible change. all BS does is turn on dark mode (already on) and limits background syncing (already minimal).


dormancy in stand-by
any ideas on making an android phone (LOS 22.2, root) more dormant in standby? I got a couple older ex-flagships with beefier SoC that aren't super-energy efficient and chew through the battery without doing anything. they got no SIM cards and broadband is disabled by way of Airplane mode, they're on wifi with very few background apps (syncthing, KDE Connect - tried without them, same) and still they barely last 24 hours doing nothing, just sitting there with SoT of like 5 mins. tried just LOS (with unifiedpush) and LOS + microG + replace FOSS apps with Gplay apps, thinking that background sync could be the issue, no significant difference. I've tried some tools like 3c CPU Manager that let you underclock CPU and GPU, but them things are for people trying to maximize their SoT, like use less power while they're being used. what I'm looking for is something to bring the consumption way, *way* down when it's not being used.
fedilink

why would swiping away an app not kill it? why would you do that? leave it be until it’s done wtf

how much RAM you got? on my two A15 phones with 6 and 8 GB RAM nothing extraordinary happens in that regard, whereas my A15 4 GB RAM tablet can’t handle a lot of open apps and OOM kills some in the background.

edit: you seem to be trying to run android apps like desktop apps. that doesn’t work here. how things work is most apps are dormant when they don’t have focus and when they receive a push message e.g. “you have a new message”, their handler wakes up, fetches stuff from the server and updates local state (and then optionally displays the notification).

so you either need to install unified push and get apps that support it or have e.g. microG implement a subset of Play services so that GCM/FCM works with “normal” apps. the third option, what you may be doing, is having every app excluded from sleep and doing their own updates checking.

the example where you close an app and then go “why app closed” is unrelated.


gOS threat model is “everything everywhere all at once” - nation state actors et al - and from that standpoint, yeah, eOS and lOS and whoever else is lacking.

but the vast majority of users have a threat model that can be boiled down to two things:

  1. a lost/stolen device doesn’t compromise me - the fucker can’t get at my stuff and/or impersonate me, and
  2. free from apple’s/google’s reign - I control what stuff runs on my phone

both easily accomplished with lineageOS and derivatives running on a $50 phone. if you truly want to spend four digits annually on Newest & Best, you do you, I’m good.



disable network comms for Gcam and install the magisk module that fakes the necessary services are installed (play store, photos) and you’re good. the opensource variants are lacking, to say the least.


I have no alternative but used phone + lineageOS; the stuff you’re mentioning (new phone with whatever crap they installed on there) isn’t even on my radar as an option.

as to longevity, it’s a stop-gap to hold us over until postmarketOS or any of its brethren are ready. banking on the benevolence of evilcorp to give us this thing for free for ever isn’t a viable strategy.


your phone isn’t booting a linux desktop. it’s booting a java virtual machine and within it a whole stack and within it the stuff that behaves like a desktop environment and all that from shit-slow, unreliable storage.

honestly, with the whole chain it’s amazing that everything boots and runs so well.


you should aim at $100ish (used obv) and make it as fungible as possible. a lost or stolen or exploded phone is then a no biggie. it’s encrypted by default so nobody can get at your shit, it’s easily replaced with another one, restore data, roll on. so it doesn’t matter which one you get, as long it has official lineageOS support. go to https://wiki.lineageos.org/devices click on “filter” and choose the latest LOS version (22.2 as of now) and then pick and choose whatever’s in that budget.

edit: replacing the battery on the 6a is also possible, youtube for details; not the easiest thing out there but not that hard either, especially when it’s doomed anyhow.


buncha clowns ITT laughing at a dude trying to swim for the first time. OMG how does he not know how to X and Y lolz why don’t you flatpak bust a cap in they ass…

this was an exceptionally excellent writeup especially with the “day 7: can’t do thing. day 10: here’s how to do thing” from the perspective of someone who used windows for ever and invariably looks at the thing from that point of view. dude pulled of transitioning a laptop with a buncha esoteric peripherals and an nvidia desktop and made almost everything work!

also, major ups for using the single most excellent solution for beginners, Ubuntu, and not getting lost in “no true scotsman” garudas and arches and atomic thisandthats.


what’s way more angering is the deliberate constant raising of prices. tech is supposed to get better and cheaper at the same time. what was thousands in '06 should be like $100 now. no, a desktop is still supposed to cost north of $1000 without a monitor.

mentioned it a coupla times, RX 570, a midrange GPU, was introed in 2017 at $170. nowadays, midrange starts at like $700?

that same year I bought a Redmi Note, a feature rich budget phone from a budget line for $140. nowadays, a comparable Snapdragon model with an insignificant performance and feature jump is $300+.


possible. I tried it at one point with the -Z option, which should disable compression but no change, same result.


works. still would like to know what the issue is with adb.


trying to transfer a large (13 GB) folder via USB to my phone with `adb push`. if I try singular, smaller files they go through, pushing the whole folder hangs adb and then gets OOM killed. `adb pull` from phone #1 worked without issues, pushing it to phone #2 starts eating up all RAM (16 GB) and then gets killed. so I created a 16 GB swap file, `swapon`, push - same thing, eats up all RAM, then all swap, then OOM manager kills konsole. no files are created on the phone. transferring via MTP isn't viable, it's like 700 bytes/sec. tried everything suggested [here](https://lemmy.ml/post/25303953). edit: tried adb over wifi, different terminal, same deal.
fedilink