Android
DROID DOES
Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
We are Android girls*,
In our Lemmy.world.
The back is plastic,
It's fantastic.
*Well, not just girls: people of all gender identities are welcomed here.
Our Partner Communities:
view the rest of the comments
Magisk needs to patch the boot.img file somehow.
Here's how I did it:
Magisk.apktoMagisk.zipMagisk.zipand let it installI will try this, thank you!! I appreciate the fast response, too!
Question: sideload how? Sorry, I am not completely familiar... should I just adb push it onto the internal disk? Also, should I leave the existing installation on there?
One last question: why is the latest shown on github as 27 yet the app downloads 28 to update?
Sideloading should be the same way you installed Lineage, assuming you used the official instructions and Lineage recovery.
I'm doing this from memory, so the steps may vary a bit.
Boot to recovery, click "Install", then choose "ADB Sideload".
From your PC, run
adb sideload Magisk.zip(assuming Magisk.zip is in your working directory).Then the phone should show progress; ignore anything pertaining to inability to verify. That's normal since the app you're installing isn't signed by Lineage.
Hey, dude or dudette, This worked perfectly! Thank you so much. On XDA forums these people write instructions like their abbreviating stuff on a grocery list. All it said for root was "get the latest magisk.zip from GitHub and install." Um - first of all, there's no zip from there, you need to rename the apk to zip - which he made no mention of. Second, saying to install an app is normally just running the apk in a file manager. Piss poor instructions from those guys. And that's consistent with pretty much almost all instructions I've seen over the past like year... YOU should be writing instructions on those pages FFS. And this you provided to me from memory! Dude/Dudette, you're AWESOME. Thank you.
And it's crazy also because I do not understand what the aging fuck I just did, and yet I've run my own IT company for nearly two decades. I think it's because mobile devices are so much in their own little pocket tech world. I dealt mostly with hardware and OS such as Windows and Linux, and software and network engineering and support. Mobile phones are such a separate cosmos.
Anyway, thank you again, a million times! I appreciate your help so much. I would gladly return the favor if you ever need something that I can provide. Peace out.
P.S. the only difference was in TWRP now you don't go to install, they have a separate ADB Sideload button. Other than that, literally step by step it was perfect instructions and took all of like 3 minutes in total. Most of that was the reboots lol.
Glad I could help!
TBH, my instructions were just my own phrasing of what I earlier read on XDA. I love XDA forums, and I've learned so much from there, but yeah, they do gatekeep pretty hard.
Ah, yeah. I haven't used TWRP for a while since my last couple devices weren't supported and I had to use Lineage's own recovery.
Yeah, what the hell is up with that?? It seems like they go out of their way to provide the content, but be ambiguous as they can about getting it to use. Who are they trying to impress? Some people have speculated it's just plain laziness, which I would not discount, but it seems like uniform laziness which would be weird. The instructions to install Lineage on this device were only the second set of instructions I've found that were coherent and comprehensive. I have tried to understand many others but they were really just plain incomplete!
Hey do you think you can recommend a good utility to move apps to the SD card? I understand that performance is a major issue and I've even seen apps not work properly when run off there, which is why I only ever move things like Icon Packs or other referential apps, not stuff that needs to function in realtime and stay loaded. But Lineage does not allow this, even if you turn it on in developer options. Pretty sure that even being there is only an oversight. But the device I'm toying with only has 16GB internal, and icon packs are huge and absolutely don't need to be on internal.
Not really, unfortunately for a couple of reasons.
My devices running Lineage have sufficient internal storage that I haven't really needed to mess with it on those or look for / familiarize myself with a solution.
My daily-driver device running do-googled stock Android only has 16 GB, but it does allow moving apps to SD. Sadly, I've had lots of issues with using the SD card in "extended storage" mode. Like, consistently, after each reboot, all my app launcher icons were gone from the home screen for anything that was on SD. Another time (and this is what made me say hell with it lol), I rebooted and the SD card was just wiped.
I've side-stepped the issue by using app-level options to store data on SD (with the apps still being on internal storage). e.g. I've got Organic Maps set to store the map files on SD, Nextcloud uses the SD card for its app data, camera defaults to the SD card, etc. It also helps that I don't run a lot of apps in general; pretty much most of my "apps" are just pinned web apps.
Oh, yeah the extended storage mode is iffy. They're all iffy to be sure, and I've seen icons be faded upon boot also but immediately they catch up and show solid.
Ironically, at least in my experience it is better to leave the SD as external, and use developer options to allow moving app to external even if not in the manifest. It's all about what apps you choose to move, less about the performance. Like I said, I don't move apps that need to run realtime and read and write data regularly, but stuff like icon packs, books, stuff like that, really anything that loads data only occasionally.
Right now, my real phone is still iPhone, but I'm thinking I'll change to android eventually. But I use several android devices as additional pocket computers.
I can't fathom why lineage devs made it like, not feasible. That should be up to the user. I did try to integrate some SD cards as extended internal storage but it fails every time with some java error and reports the SD corrupted. Lol three brand new chips are not corrupted dumbass Lineage lol. Good ones, too! So yeah, they effectively wrote it off as not an option. That's the one problem I have at the moment that I strongly disapprove. Other than that, the performance is insane! Similar with Cyanogen.
I still want to try out stuff like ResurrectionRemix, Havoc, /e/ and maybe Rising. For now I'm content mostly with Lineage on this Galaxy S5 but I really want to get something working that will let me move apps to the SD.
Thank you for all the replies and your insights. Greatly appreciated!