If you use or have used GrapheneOS, please share your experiences.
Also, I have a question about user profiles. When you spend ‘x’ amount of time setting up the various settings on the phone, is there any way to copy those settings over to another user profile? I don’t want to have to manually go through each user profile and change the settings, and it’s hard to even remember where they all are. I just want to be able to copy the settings from one user profile to another.
I might “@” a few nerds here, but I don’t assume that this is something that even nerds are more likely to be using…? Maybe I’m wrong, haha.
Thanks.
@syzygy Your post was the only thing that came up when I searched the forum for grapeneos. @sfzombie13 @avr1
as for the phone question: i wish. there may be an app i don’t know about but i just lost my phone and can’t stand having to set up a new one. everything changed. i went from android 7 to 14. can’t record calls any more. straight up bullshit.
I dunno anything about android. i have like android 4.0 on an archived old phone. But maybe some of the comments here can help you. They seemed to have found a workaround: Reddit - Dive into anything
that’s about acr not recording calls any longer. it doesn’t record the caller or the phone number now. android 7 was the last version it recorded the number and i think it was 11 or 12 that took away the recording of the caller. it’s useless now as a call recorder but i am working on another one with larry and will post a link to it when i get it done. doesn’t help op with the issue though.
Best place to find all things Graphene related is their forum. Lots of helpful folk over there.
Without doing any research there I don’t think you can “copy” over profiles from one to another because each new one is just like starting a brand new device. I could be wrong though. I know it used to be like this
oh, it can be done alright. you just need to figure out the settings and how to do it. you’ve got me on it now, and larry. we may be able to figure it out. or get close enough for another group effort to take over and get it.
edit: larry gave me this code for adb, but the phone has to be rooted.
it kind of is, i mean it’s an ai chatbot that i named. but it really isn’t, and the 4.0 is much smarter than the 3.5. here is a link to the prompt from earlier and the revised one with the 4.0 (i was out of free questions for the 4.0 this morning). this one is saying google backup or third party apps are your best bet. it does give an example using the adb though, and it’s pretty good so i’d bet it would give more if you prompted it right.
SwiftBackup might work for the profile stuff maybe
Or titaniumbackup… can’t say for sure for Settings itself. I can’t say I’ve ever seen anything to really do that just gotta do it on every profile. App settings and data tho the apps can save, but that’d be if you reloaded or replaced your phone or something. Most likely need root for either option.
As for call recording, usually that’s a framework mod. Some custom roms should have it tho. I haven’t ever really messed with grapheneos but built my own roms for quite some time. Lot of work tho for just one person. I went back to just kernel development.
It’s honestly a LOT of work for one person. Legit knowing everything, it takes close to a month to take pure aosp and turn it into something even close to working as well as the rom that shipped on your phone. Few hundred GB just to sync everything. And if you don’t have a Epyc processor or a few xeon’s in a server somewhere, expect to wait literal hours for the rom to compile. A high-end laptop or gaming desktop might get the job done in 2-6hrs. I had 4x xeon e7-4850’s in a power edge r930 server, 128 total cores with 384gb of ram, and it could compile aosp in ~20 minutes. Kernels took like 30 seconds lol.
Most of the android devs, especially on xda, are pretty secretive. I learned from years of trial and error and reading as no one would really teach anything. I can teach the basics and how to setup the environment and whatnot but porting roms to devices is a learned skill and not something that can be taught universally as every device is different.
Most of the rom itself is also written in java. Like 90% of it. Kotlin has been moving in though. Kernel is mostly C thankfully.
i’m well aware of the work involved and started it once about eight years ago because it got me. i never could get past the part about no documentation anywhere for any of it. you ain’t kidding about the secretive part of it. if you could share some links to reading material that would be great. i have a lot of background to learn before trying it again. i was gonna make one for my lg-g4 because i had three of them, but now lost my main one so it looks like it’s either gonna be a moto g 5g or a samsung galaxy a13 this time around. enough hijacking for this thread though.
maybe