Mod edit: TG link removed as per XDA's TG Chat Rules.
(TG link and home page was removed I can only see in their rules the TG link all good so adding back the home page to the home page)
I started project rooted to provide pre rooted roms to people. I'm looking for someone to help with pixel 6 pro. If anyone is interested please let me know. All it really is is patching operating systems, recompiling then, and sharing them.
I think that there is no value at all in this project. All anyone needs to do is run the original boot.img through magisk before they write it to the boot partition and the job is done.
In addition, if anyone was inclined to use 3rd party hosted pre-rooted (or not) boot images, I would VERY STRONGLY recommend that they DO NOT. This is simply because it opens them up to whatever other undisclosed changes happen to have been added to it.
Thanks for the feedback!!! I can assure you that there is absolutely no malicious intent or anything out of the ordinary in these roms. I've had mixed responses with some liking and disliking the project. If it's not your preference no problem I'm not going to stop you from doing it manually or not using my project either way. I'm doing this for fun and am providing a convenient place for roms in one place(without having to search through chats) and with the bonus of being rooted from the start.
Edit: typo
Jacobh1245 said:
Thanks for the feedback!!! I can assure you that there is absolutely no malicious intent or anything out of the ordinary in these roms. I've had mixed responses with some liking and disliking the project. If it's not your preference no problem I'm not going to stop you from doing it manually or not using my project either way. I'm doing this for fun and am providing a convenient place for roms in one place(without having to search through chats) and with the bonus of being rooted from the start.
Edit: typo
Click to expand...
Click to collapse
And I can absolutely assure you that I am a Nigerian Prince, and if you direct deposit $500 into my bank acount, I will turn it into $5,000,000.
Gytole said:
And I can absolutely assure you that I am a Nigerian Prince, and if you direct deposit $500 into my bank acount, I will turn it into $5,000,000.
Click to expand...
Click to collapse
Lol, I get it. I'm not well known or trusted yet as this is not my first project but first I've tried to get out there as much as I am. Again I'll reiterate that you don't have to use it if you don't trust it all my work is posted even the as basic as it is website is open source on GitHub. If you have any genuine feedback for me I'd love to hear it. Constructive feedback on how to get started and trusted wouldn't be so bad. Thanks for your opinion though, it's good to hear what a community thinks of new projects/ideas
Jacobh1245 said:
Lol, I get it. I'm not well known or trusted yet as this is not my first project but first I've tried to get out there as much as I am. Again I'll reiterate that you don't have to use it if you don't trust it all my work is posted even the as basic as it is website is open source on GitHub. If you have any genuine feedback for me I'd love to hear it. Constructive feedback on how to get started and trusted wouldn't be so bad. Thanks for your opinion though, it's good to hear what a community thinks of new projects/ideas
Click to expand...
Click to collapse
Thanks for being a great sport
Is there benefit in having it pre rooted? Perhaps easier to pass the safety checks for banking apps?
TrustAugustus said:
Is there benefit in having it pre rooted? Perhaps easier to pass the safety checks for banking apps?
Click to expand...
Click to collapse
Yes I have had better success with safetynet since doing this they don't always work out like that but for the most part it's been better. As far as pre-rooted with pixel devices it's not too hard to do, just time consuming. I'm going to build a set of instructions tonight for my website as to how to do so yourself for those who would rather do it manually
That sounds great. I'm looking forward to the project.
Back... like 10 years ago roms came pre rooted as well
TrustAugustus said:
That sounds great. I'm looking forward to the project.
Back... like 10 years ago roms came pre rooted as well
Click to expand...
Click to collapse
I remember that was one of the best things ever. That's just one of my reasons I wanted to do this. THANKS for the support!!!
Jacobh1245 said:
I remember that was one of the best things ever. That's just one of my reasons I wanted to do this. THANKS for the support!!!
Click to expand...
Click to collapse
We understand, just with the new safeties built into to hardware anymore it can comicate things for some people. I am not saying prerooted is WRONG, it can just cause problems. It's not you. Lol
Yeah, some devices can, some won't. I am alware of these but also understand the risk is minimal and unlikely to be president. Reality with anything like this even down to the roms themselves have so many variables that could cause problems. Which I why I have taken the extra steps to test that I have a solidly rooted Rom
Jacobh1245 said:
I started project rooted to provide pre rooted roms to people. I'm looking for someone to help with pixel 6 pro. If anyone is interested please let me know. All it really is is patching operating systems, recompiling then, and sharing them.
Click to expand...
Click to collapse
For anyone who might want to know this. I have a very poor excuse for a guide on making pre rooted roms on my page now if you have a pixel device it does work. It was quickly put together and I WILL update it SOON and will add screenshots to help as well as fine tuning the wording.
What would be nice is to have the installation routinely root the boot.img if the system is pre-rooted, like Lineage 18 does on my 1+7pro.
Jacobh1245 said:
Thanks for the feedback!!! I can assure you that there is absolutely no malicious intent or anything out of the ordinary in these roms. I've had mixed responses with some liking and disliking the project. If it's not your preference no problem I'm not going to stop you from doing it manually or not using my project either way. I'm doing this for fun and am providing a convenient place for roms in one place(without having to search through chats) and with the bonus of being rooted from the start.
Edit: typo
Click to expand...
Click to collapse
Its not a question of you having malicious intent. Its a question of best practices for security. Other people who may be more or less trustworthy than you may have similar projects (and in fact, I remember another thread with this exact purpose), and trusting those may be quite dangerous.
But more to the point, and WITHOUT putting your trustworthiness or honor in question, how can anybody know whether you are *actually* trustworthy or just someone claiming (falsely) to be?
And since the process of running it through Magisk is so absurdly trivial, what advantage does this provide to users to compensate them for the risk?
Advantages: nil
Risks: elevated
Rational choice: avoid.
96carboard said:
Its not a question of you having malicious intent. Its a question of best practices for security. Other people who may be more or less trustworthy than you may have similar projects (and in fact, I remember another thread with this exact purpose), and trusting those may be quite dangerous.
But more to the point, and WITHOUT putting your trustworthiness or honor in question, how can anybody know whether you are *actually* trustworthy or just someone claiming (falsely) to be?
And since the process of running it through Magisk is so absurdly trivial, what advantage does this provide to users to compensate them for the risk?
Advantages: nil
Risks: elevated
Rational choice: avoid.
Click to expand...
Click to collapse
It does a few things, it in many cases seems to help with safetynet being easier to pass( not always some roms are more stubborn). It provides a convinent place where everything is at. All my stuff is open source and downloadable so you may check whatever you want. Though I don't have the source code to the roms since I'm not building them. And I put links to the roms group chat and instructions as to how(for pixel devices) to make a pre-rooted rom yourself. So if you don't trust it but want it I give how to and where to get the files to do so some also fear that things may not work as mentioned above can happen but is very minimal especially since I test before releasing.
Jacobh1245 said:
It does a few things, it in many cases seems to help with safetynet being easier to pass( not always some roms are more stubborn). It provides a convinent place where everything is at. All my stuff is open source and downloadable so you may check whatever you want. Though I don't have the source code to the roms since I'm not building them. And I put links to the roms group chat and instructions as to how(for pixel devices) to make a pre-rooted rom yourself. So if you don't trust it but want it I give how to and where to get the files to do so some also fear that things may not work as mentioned above can happen but is very minimal especially since I test before releasing.
Click to expand...
Click to collapse
What version of Magisk do you intend to use? Because on at least 2 or 3 occasions due to Google changing things, Canary has been needed. On the other hand, there have also been occasions where Canary broke some things and Stable was needed.
Because the Pixel 6 series seems to be "often" affected by changes made by Google in their monthly updates, as well as Magisk itself, it seems that pre-rooting a rom on the Pixel 6 series "may" cause some unintended problems.
It's been quite the cat and mouse game when it comes to the Pixel 6 series and rooting in terms of these changes, and not in terms of just rooting itself, but other things like custom kernels, etc..
Lughnasadh said:
What version of Magisk do you intend to use? Because on at least 2 or 3 occasions due to Google changing things, Canary has been needed. On the other hand, there have also been occasions where Canary broke some things and Stable was needed.
Because the Pixel 6 series seems to be "often" affected by changes made by Google in their monthly updates, as well as Magisk itself, it seems that pre-rooting a rom on the Pixel 6 series "may" cause some unintended problems.
It's been quite the cat and mouse game when it comes to the Pixel 6 series and rooting in terms of these changes, and not in terms of just rooting itself, but other things like custom kernels, etc..
Click to expand...
Click to collapse
Currently I've been using v25.0 that is one thing I test too and check with others about. So far 25.0 is working great with the minor detail of having to download the magisk apk and install rather then the greyed out icon to "update" but it still works exactly the same and I have not experienced anything broken so far
Jacobh1245 said:
Currently I've been using v25.0 that is one thing I test too and check with others about. So far 25.0 is working great with the minor detail of having to download the magisk apk and install rather then the greyed out icon to "update" but it still works exactly the same and I have not experienced anything broken so far
Click to expand...
Click to collapse
Yes, but there have been occasions where after a monthly update a Canary version was needed (e.g. December update when Google moved its fstab to /system/etc.) and John had to update Magisk and push a Canary version before people could actually boot a rooted boot image.
And I'm curious if you closely follow the issues, PRs and commits in the Magisk Github? For example, Beta 25.0 has changed (actually changed with Canary 24303 I believe) so that custom kernels will no longer boot unless verity and verification are disabled or if the kernel uses the latest AK3 which patches vendor_dlkm.img and vbmeta.img, or if the kernel patches them itself.
My point is there could be some unintended consequences for people who may not be aware of any current issues unless they are made aware of them before flashing a pre-rooted rom.
Anyway, if people find this useful then good for them and good for you.
Lughnasadh said:
Yes, but there have been occasions where after a monthly update a Canary version was needed (e.g. December update when Google moved its fstab to /system/etc.) and John had to update Magisk and push a Canary version before people could actually boot a rooted boot image.
And I'm curious if you closely follow the issues, PRs and commits in the Magisk Github? For example, Beta 25.0 has changed (actually changed with Canary 24303 I believe) so that custom kernels will no longer boot unless verity and verification are disabled or if the kernel uses the latest AK3 which patches vendor_dlkm.img and vbmeta.img, or if the kernel patches them itself.
My point is there could be some unintended consequences for people who may not be aware of any current issues unless they are made aware of them before flashing a pre-rooted rom.
Anyway, if people find this useful then good for them and good for you.
Click to expand...
Click to collapse
I which case testing would show that plus I'm usually pretty good at keeping up with that kind of thing. It is a valid concern but since the versions I release are going to have the correct version for them I will do the same for each rom indevidually as need to make sure they will work properly. Whenever a new version is released. That too means if you are on the same rom and dirty flash to the next one magisk will prompt you to update the app(has been tested too)
Related
Okay so there are two multi-boot modifications flowing around XDA for a ton of various devices.. Has anyone ever considered porting one to the robin? lately with all these rock solid Roms it doesn't seem like too bad of an idea and I truly wish I had the experience to do it myself.
https://github.com/chenxiaolong/DualBootPatcher/
and
https://github.com/Tasssadar/multirom
and
https://github.com/efidroid/
Oh hell yes! I'd like to see this!
Desperately waiting for it!
Sounds cool, I can have Omni and XOSP at the same time ;P
https://github.com/efidroid/projectmanagement/wiki/[EFIDroid]-Porting-a-new-device
If you ask me, the lack of the need of the kexec-hardboot patch makes this project superior to multirom
Alexandroid99 said:
https://github.com/efidroid/projectmanagement/wiki/[EFIDroid]-Porting-a-new-device
If you ask me, the lack of the need of the kexec-hardboot patch makes this project superior to multirom
Click to expand...
Click to collapse
I'm taking a look at it and i'm gonna mess around with it and hopefully make an attempt to port it.. Hope all goes well
AnierinB said:
I'm taking a look at it and i'm gonna mess around with it and hopefully make an attempt to port it.. Hope all goes well
Click to expand...
Click to collapse
If you're lucky it's seriously easy, but it can become a very involved process fairly quickly when something doesn't work...
Alexandroid99 said:
If you're lucky it's seriously easy, but it can become a very involved process fairly quickly when something doesn't work...
Click to expand...
Click to collapse
Yeah but unfortunately for me repo is giving me a ton of problems and i've got to get to work. if someone else wants to try this, be my guest.
AnierinB said:
Yeah but unfortunately for me repo is giving me a ton of problems and i've got to get to work. if someone else wants to try this, be my guest.
Click to expand...
Click to collapse
I'm already syncing it. Someone got it to work partially on the Nexus 5X, which is the same arch. So fingers crossed...
Alexandroid99 said:
I'm already syncing it. Someone got it to work partially on the Nexus 5X, which is the same arch. So fingers crossed...
Click to expand...
Click to collapse
Let me know how it goes man :highfive:
Alexandroid99 said:
If you're lucky it's seriously easy, but it can become a very involved process fairly quickly when something doesn't work...
Click to expand...
Click to collapse
No dice. Tried to compile lk using msm8994 (SD810- same workaround as 5x) and was able to fastboot boot a nouefi lk.img but but once booted there was no device showing up in fastboot devices which unfortunately is key to the next step
A lot of Devs are getting into issues assuming that this device is similar to the 5X. No. It isn't. This device's implementation is completely different. Take a look at the two sources and you'll see it. NextBit's calls to device and storage are also different. Boot patches won't work the same way. The OmniROM Dev was the first to learn this which is why it took a lot of time. Also Robin doesn't seem to respond to slot switching though it has it. I may be wrong.
valhallen.282 said:
A lot of Devs are getting into issues assuming that this device is similar to the 5X. No. It isn't. This device's implementation is completely different. Take a look at the two sources and you'll see it. NextBit's calls to device and storage are also different. Boot patches won't work the same way. The OmniROM Dev was the first to learn this which is why it took a lot of time. Also Robin doesn't seem to respond to slot switching though it has it. I may be wrong.
Click to expand...
Click to collapse
I got lk to boot using the same lk_base as the 5x so there are a few thing in common because the aboot dump showed the same value. anyways I made some progress: Display to show, finalize_device to execute and was able to build uefi.img and boot it. upon booting uefi the kernel panics and reboots so I have to to figure that out before proceeding to the checklist.
valhallen.282 said:
A lot of Devs are getting into issues assuming that this device is similar to the 5X. No. It isn't. This device's implementation is completely different. Take a look at the two sources and you'll see it. NextBit's calls to device and storage are also different. Boot patches won't work the same way. The OmniROM Dev was the first to learn this which is why it took a lot of time. Also Robin doesn't seem to respond to slot switching though it has it. I may be wrong.
Click to expand...
Click to collapse
Alexandroid99 said:
If you're lucky it's seriously easy, but it can become a very involved process fairly quickly when something doesn't work...
Click to expand...
Click to collapse
I've got it to boot and run for the most part but I'm not the most experienced at porting and there are a few things left to do like configuring the fstab.multiboot correctly which is key to multi booting roms and installing the ota through efidroid app via github sever
AnierinB said:
So I've got efi-droid ported and working for the most part. I'm not the most experienced at porting and there are a few things left to do like testing multiboot roms and configuring a local ota sever to do so..
I'm making this post so that I can hand off my findings, config.ini, and my lk_inc.make to someone who has more experience/ someone who can get this done and wants to test multiboot and see if it's a go. Think you can do so and become the maintainer for this project?
Click to expand...
Click to collapse
I wish I was smart enough to do that. I can read code. I can test. Cannot write to save my life. Sorry. That's my truth.
valhallen.282 said:
I wish I was smart enough to do that. I can read code. I can test. Cannot write to save my life. Sorry. That's my truth.
Click to expand...
Click to collapse
As soon as I get these local ota server problems figured out and are able to actually test dual booting a rom I'll pm you with some goodies:good:
It's pretty easy to build yourself after you figure out what variables the lk.mk and config.ini need. Although I have been doing this for 3 days now with many trial and error. Pretty shocked it's even working as good as it is right now because there's been a lot of known issues with 64bit socs
delete
I'm gonna have to put this project behind me... I lack some knowledge on a few areas of the porting process and to configure it correctly is possible but I, myself can not do it. If a developer has the device, and wants to try porting/configuring it then go for it. The main thing is that we are able to get lk, uefi to boot and display screen (properly) so fixing the other issues like fstab.multiboot table should be easy for someone more experienced. At least theres hope with this modification. Sorry folks, I'll stick to my boot logos for now haha.
AnierinB said:
@ValHallen can you download the efi manager application off the play store and tell me what device it gives you an error for? then after doing so can you edit your build prop and add this line: efidroid.server_url=https://raw.githubusercontent.com/anierinbliss/efidroid_ota/master
then delete the app, reboot your phone and reinstall it.. Does it still fail?
Click to expand...
Click to collapse
I think you tagged the wrong person. But I'll try. In a short while.
It's probably best to put all thaz work out in the open including github repos and a separate thread so someone who's capable might stumble upon it and pick up qhere you left off.
So I have been in this modding android game for quite some time since I had an LG G3 and then I moved over to the Nexus 6 for about 2 years and some of these custom roms are just awesome but one thing I cannot get rid of properly are the inbuilt AOSP apps..
on the Nexus 6 a few years back somebody made a flashable zip that got rid of all of them and the boot animation but then fixed the boot animation being deleted and unfortunately time to change technology has changed and that doesn't work on this phone obviously.
I have tried using the magisk debloater and it just a little too complicated for me because I don't like having two of the same apps one being Google the other being AOSP and any other gaps package I flash besides the razorlove gapps fail when flashing a custom ROM..
I've tried using opengapps and I thought when flashing that package the AOSP apps get replaced with the Google version of them.
Would anybody mind listing what AOSP apps I can remove completely and I apologize if it's already on the thread but I didn't really see anything or maybe I just wasn't looking in the right place but can you guys help me out? I really like the RR ROM but the AOSP apps just bothered the hell out of me. I've tried using titanium to completely remove some of them like the AOSP Keyboard but it doesn't fully remove them and I don't want to go into the files that I don't know about and screw up my phone..
So right now I'm on stock and the limitations kind of suck so if anybody could you know help me out listing a method that they use to get rid of them that actually works or listing the ones that I can remove and what program I can use to remove them I do not want to disable them I want to remove them... Or because I know how to use Linux and what not you know maybe somebody could show me how to make a flashable zip that will remove them and I will gladly share it to the community but I'm looking for anything that helps.
It would be greatly appreciated!
soateufel said:
So I have been in this modding android game for quite some time since I had an LG G3 and then I moved over to the Nexus 6 for about 2 years and some of these custom roms are just awesome but one thing I cannot get rid of properly are the inbuilt AOSP apps..
on the Nexus 6 a few years back somebody made a flashable zip that got rid of all of them and the boot animation but then fixed the boot animation being deleted and unfortunately time to change technology has changed and that doesn't work on this phone obviously.
I have tried using the magisk debloater and it just a little too complicated for me because I don't like having two of the same apps one being Google the other being AOSP and any other gaps package I flash besides the razorlove gapps fail when flashing a custom ROM..
I've tried using opengapps and I thought when flashing that package the AOSP apps get replaced with the Google version of them.
Would anybody mind listing what AOSP apps I can remove completely and I apologize if it's already on the thread but I didn't really see anything or maybe I just wasn't looking in the right place but can you guys help me out? I really like the RR ROM but the AOSP apps just bothered the hell out of me. I've tried using titanium to completely remove some of them like the AOSP Keyboard but it doesn't fully remove them and I don't want to go into the files that I don't know about and screw up my phone..
So right now I'm on stock and the limitations kind of suck so if anybody could you know help me out listing a method that they use to get rid of them that actually works or listing the ones that I can remove and what program I can use to remove them I do not want to disable them I want to remove them... Or because I know how to use Linux and what not you know maybe somebody could show me how to make a flashable zip that will remove them and I will gladly share it to the community but I'm looking for anything that helps.
It would be greatly appreciated!
Click to expand...
Click to collapse
You do realize that AOSP is not a single project like some rom developers, right? If someone publishes an "AOSP" rom, that doesn't mean that they are following some kind of standards or rules.
nabbed said:
You do realize that AOSP is not a single project like some rom developers, right? If someone publishes an "AOSP" rom, that doesn't mean that they are following some kind of standards or rules.
Click to expand...
Click to collapse
Well obviously but what I'm saying is pretty much every ROM that I flash seems to have the built-in apps that are AOSP based or maybe I'm not saying it right but basically every ROM that I've tried (dirty unicorns, Resurrection Remix, carbon, dotOS, sudomod,) all have built-in AOSP Keyboard AOSP phone AOSP calendar AOSP email **** like that and that's what I want to remove
soateufel said:
Well obviously but what I'm saying is pretty much every ROM that I flash seems to have the built-in apps that are AOSP based or maybe I'm not saying it right but basically every ROM that I've tried (dirty unicorns, Resurrection Remix, carbon, dotOS, sudomod,) all have built-in AOSP Keyboard AOSP phone AOSP calendar AOSP email **** like that and that's what I want to remove
Click to expand...
Click to collapse
But I am doing some research on a flashable zip creator from XDA and hopefully I can make some progress with it
soateufel said:
Well obviously but what I'm saying is pretty much every ROM that I flash seems to have the built-in apps that are AOSP based or maybe I'm not saying it right but basically every ROM that I've tried (dirty unicorns, Resurrection Remix, carbon, dotOS, sudomod,) all have built-in AOSP Keyboard AOSP phone AOSP calendar AOSP email **** like that and that's what I want to remove
Click to expand...
Click to collapse
A piece of advice. Get rid of your Pixel as soon as you can. It's a bug testing platform for Google. Samsung, HTC, LG, Oneplus take buggy Google code and refine it. Google doesn't bother.
I only keep this $960 piece of **** (which is now worth less that $300) because I have no other alternative at the moment. As soon as I can dump it for a real a phone, I will.
I'm good thanks I do my research before I buy my phones and I will never buy another Samsung again and dumping my phone is not an option right now if it was I get me the Rog phone from Asus that thing is a beast
soateufel said:
I'm good thanks I do my research before I buy my phones and I will never buy another Samsung again and dumping my phone is not an option right now if it was I get me the Rog phone from Asus that thing is a beast
Click to expand...
Click to collapse
I used an S9 for a little while when I was setting it up for a friend. It's a marvelous phone. I have owned multiple HTC flagships in the past, and they were stellar. I have heard that LG and Oneplus were excellent. My last phone before Pixel XL was Note 7, which was absolutely amazing, one of a kind. This pos Pixel XL has been nothing but bug ridden nightmare. The only reason why I keep it around is because of Project FI. It's because it's cheap. Goddamn $960 nightmare on top of that.
Also, please use punctuation next time. Not using it seems like an insult, but maybe that's just me.
I like my pixel XL. No bugs here.
nabbed said:
I used an S9 for a little while when I was setting it up for a friend. It's a marvelous phone. I have owned multiple HTC flagships in the past, and they were stellar. I have heard that LG and Oneplus were excellent. My last phone before Pixel XL was Note 7, which was absolutely amazing, one of a kind. This pos Pixel XL has been nothing but bug ridden nightmare. The only reason why I keep it around is because of Project FI. It's because it's cheap. Goddamn $960 nightmare on top of that.
Also, please use punctuation next time. Not using it seems like an insult, but maybe that's just me.
Click to expand...
Click to collapse
lafester said:
I like my pixel XL. No bugs here.
Click to expand...
Click to collapse
Ignorance is bliss.
nabbed said:
Ignorance is bliss.
Click to expand...
Click to collapse
Maybe you can fill us in on all these bugs you speak of. Would hate to continue to be ignorant.
nabbed said:
Ignorance is bliss.
Click to expand...
Click to collapse
lafester said:
Maybe you can fill us in on all these bugs you speak of. Would hate to continue to be ignorant.
Click to expand...
Click to collapse
I'd like to know too, cause I must be missing something. I have absolutely no issues with my device...
lafester said:
Maybe you can fill us in on all these bugs you speak of. Would hate to continue to be ignorant.
Click to expand...
Click to collapse
Click on my profile and find new threads started by me in this subforum.
I believe every single new thread was me complaining about one bug or another.
The biggest one that is always on my mind though, and which is almost a deal breaker, was introduced by Google in the 7.0.2 update. And they still haven't fixed it, but all other manufacturers have - I know for a fact that this bug was fixed in Oreo by Samsung and Oneplus.
It's where you wear a smartwatch which can make and receive phone calls, such as my beautiful Huawei Watch with a gorgeous custom band, and then you get inside your car with a bluetooth hands-free car kit, or just a bluetooth headset, which then improperly connects to the phone as "Connected (no phone)." So you cannot use it. If you don't wear a watch, then everything works fine with a kit or bt headset. This is the reason why I don't wear my beautiful watch anymore. Google needs to fire their bluetooth stack programmer.
nabbed said:
I used an S9 for a little while when I was setting it up for a friend. It's a marvelous phone. I have owned multiple HTC flagships in the past, and they were stellar. I have heard that LG and Oneplus were excellent. My last phone before Pixel XL was Note 7, which was absolutely amazing, one of a kind. This pos Pixel XL has been nothing but bug ridden nightmare. The only reason why I keep it around is because of Project FI. It's because it's cheap. Goddamn $960 nightmare on top of that.
Also, please use punctuation next time. Not using it seems like an insult, but maybe that's just me.
Click to expand...
Click to collapse
My bad. I use speech to text a lot and I don't like using punctuation when speaking. It causes some bad habits.
Update though, upon doing further research making a flashable zip is complicated but I should have it all figured out by the end of the week and I'm not really having any bugs with the AOSP apps I just don't like looking in my app drawer and seeing there's duplicates and I really don't want to manually hide all of them each time I flash a ROM or something and do a backup.
On a side note I just found a Chrome extension that allows speech to text and is very good with no ads. If you're like me and you use your voice more than you use your keyboard, look up voice in voice typing under Chrome extensions pretty damn simple.
soateufel said:
My bad. I use speech to text a lot and I don't like using punctuation when speaking. It causes some bad habits.
Update though, upon doing further research making a flashable zip is complicated but I should have it all figured out by the end of the week and I'm not really having any bugs with the AOSP apps I just don't like looking in my app drawer and seeing there's duplicates and I really don't want to manually hide all of them each time I flash a ROM or something and do a backup.
On a side note I just found a Chrome extension that allows speech to text and is very good with no ads. If you're like me and you use your voice more than you use your keyboard, look up voice in voice typing under Chrome extensions pretty damn simple.
Click to expand...
Click to collapse
Sorry for hijacking your thread -was not my intention.
Making a flashable zip is easy with the tool I link in this thread. https://forum.xda-developers.com/pixel-xl/how-to/noob-friendly-tips-tricks-information-t3798529
soateufel said:
Update though, upon doing further research making a flashable zip is complicated but I should have it all figured out by the end of the week and I'm not really having any bugs with the AOSP apps I just don't like looking in my app drawer and seeing there's duplicates and I really don't want to manually hide all of them each time I flash a ROM or something and do a backup.
Click to expand...
Click to collapse
A friend of mine made a script specifically for what you are trying to do, granted, it's for a different device and older version of Android. Some small modification should be all it needs to suit your purpose, if nothing else, it may contain some useful information.
The thread is located here (Keep in mind, he's from Brazil, so his English is a little rough =)
nabbed said:
Sorry for hijacking your thread -was not my intention.
Click to expand...
Click to collapse
You are completely fine. I'm shocked how nice people are on here LOL usually people are just mean and think they have the right answer and I have to accept it no matter what and I just don't like people who are so full of themselves so thank you.
I've been trying to research this but I was supposed to have surgery today and I was getting ready for that and unfortunately it was cancelled without my knowledge so that was pretty stressful and now I have to start the whole process over again because the doctors I was going to go to no longer accept my insurance and nobody told me so I'm still going to work on this it's just going to be a little bit of a process.
soateufel said:
You are completely fine. I'm shocked how nice people are on here LOL usually people are just mean and think they have the right answer and I have to accept it no matter what and I just don't like people who are so full of themselves so thank you.
I've been trying to research this but I was supposed to have surgery today and I was getting ready for that and unfortunately it was cancelled without my knowledge so that was pretty stressful and now I have to start the whole process over again because the doctors I was going to go to no longer accept my insurance and nobody told me so I'm still going to work on this it's just going to be a little bit of a process.
Click to expand...
Click to collapse
As a side note, I am now in the same boat as you. I have a Oneplus 6 now, silk white, which is gorgeous. But it has double apps like yours - 2 calendars, 2 calculators, 2 message apps, 2 clock apps etc. I don't even really know which ones are Google and which ones are Oneplus - I think the round icons are Google, but rectangular icons are Oneplus. Plus I don't know which apps are better. I think that I will use some of them for a while and disable the least appealing ones.
There are only a handful, and maybe that's what you can do? Just disable? If you cannot disable from the main Android interface, you can do it from adb. There are commands that can disable and enable app packages from adb.
Hey guys I'm sorry it's been awhile since I've kept up with you guys. So a little side note
I have started this project it is my very first project on my GitHub.
But my problem is I have no idea how to even start this I mean I tried using the flashable zip creator and it pulled the system apps but I'm at a loss here any help would be greatly appreciated..
You can view the project at this link by the way
https://github.com/arkhamsaiyan/Marlin-AOSP-app-remover
Ok, so the thread i'm referencing is from the MIUI forum, but having tried it on my Pixel 3 XL, I am happy to report that it works FANTASTICALLY so far.
https://forum.xda-developers.com/Mi...en-to-84hz-t3942063/post79776396#post79776396
The OP is about a dbto.img replacement hack, using an apk called Lanthanum System Toolbox. The hack in question works great (I used the app to flash to dbto_a and dbto_b)
but the app itself is amazing. Forget init.d tweaks, magisk tweaks, searching for ever-better kernels, kernel aduitor, and all the rest.
There's a profile section which allows downloaded presets, the one for 845 SOC works great.
Only other things I should mention are that I had trouble dling the apk from xda, so i got it from their github (google Lanthanum System Toolbox) , and I'm running Colt OS - Enigma ROM (https://forum.xda-developers.com/pi...unofficial-colt-os-enigma-crosshatch-t3953043)
, boot.img extracted using https://forum.xda-developers.com/nokia-7-plus/how-to/guide-how-to-extract-payload-bin-ota-t3830962
, magisk canary patched and reflashed.
oh, and it's mostly localized in chinese,
but there's enough english that i was able to use it with very little trouble
perhaps i got the wrong apk, cause the screenshots on the OP are english
I really am surprised that there isn't a reference thread in the crosshatch forum already . you may consider my tone hyperbolic, but try it and you'll see i'm being understated if anything. enjoy!
not sure how increasing the refresh rate helps battery?
ha7msterx said:
Ok, so the thread i'm referencing is from the MIUI forum, but having tried it on my Pixel 3 XL, I am happy to report that it works FANTASTICALLY so far.
https://forum.xda-developers.com/Mi...en-to-84hz-t3942063/post79776396#post79776396
The OP is about a dbto.img replacement hack, using an apk called Lanthanum System Toolbox. The hack in question works great (I used the app to flash to dbto_a and dbto_b)
but the app itself is amazing. Forget init.d tweaks, magisk tweaks, searching for ever-better kernels, kernel aduitor, and all the rest.
There's a profile section which allows downloaded presets, the one for 845 SOC works great.
Only other things I should mention are that I had trouble dling the apk from xda, so i got it from their github (google Lanthanum System Toolbox) , and I'm running Colt OS - Enigma ROM (https://forum.xda-developers.com/pi...unofficial-colt-os-enigma-crosshatch-t3953043)
, boot.img extracted using https://forum.xda-developers.com/nokia-7-plus/how-to/guide-how-to-extract-payload-bin-ota-t3830962
, magisk canary patched and reflashed.
oh, and it's mostly localized in chinese,
but there's enough english that i was able to use it with very little trouble
perhaps i got the wrong apk, cause the screenshots on the OP are english
I really am surprised that there isn't a reference thread in the crosshatch forum already . you may consider my tone hyperbolic, but try it and you'll see i'm being understated if anything. enjoy!
Click to expand...
Click to collapse
Im getting bootloop when i tried itt on P
ha7msterx said:
Ok, so the thread i'm referencing is from the MIUI forum, but having tried it on my Pixel 3 XL, I am happy to report that it works FANTASTICALLY so far.
https://forum.xda-developers.com/Mi...en-to-84hz-t3942063/post79776396#post79776396
The OP is about a dbto.img replacement hack, using an apk called Lanthanum System Toolbox. The hack in question works great (I used the app to flash to dbto_a and dbto_b)
but the app itself is amazing. Forget init.d tweaks, magisk tweaks, searching for ever-better kernels, kernel aduitor, and all the rest.
There's a profile section which allows downloaded presets, the one for 845 SOC works great.
Only other things I should mention are that I had trouble dling the apk from xda, so i got it from their github (google Lanthanum System Toolbox) , and I'm running Colt OS - Enigma ROM (https://forum.xda-developers.com/pi...unofficial-colt-os-enigma-crosshatch-t3953043)
, boot.img extracted using https://forum.xda-developers.com/nokia-7-plus/how-to/guide-how-to-extract-payload-bin-ota-t3830962
, magisk canary patched and reflashed.
oh, and it's mostly localized in chinese,
but there's enough english that i was able to use it with very little trouble
perhaps i got the wrong apk, cause the screenshots on the OP are english
I really am surprised that there isn't a reference thread in the crosshatch forum already . you may consider my tone hyperbolic, but try it and you'll see i'm being understated if anything. enjoy!
Click to expand...
Click to collapse
Which dtbo.img did you use as well?
Don't try it on Android 10, it should work only on Pie
So does he mean that we can also get 84hz screen on pixel phone...?
DvLAx3l said:
Don't try it on Android 10, it should work only on Pie
Click to expand...
Click to collapse
I can't even get it to work on pie tho lol
ha7msterx said:
Ok, so the thread i'm referencing is from the MIUI forum, but having tried it on my Pixel 3 XL, I am happy to report that it works FANTASTICALLY so far.
https://forum.xda-developers.com/Mi...en-to-84hz-t3942063/post79776396#post79776396
The OP is about a dbto.img replacement hack, using an apk called Lanthanum System Toolbox. The hack in question works great (I used the app to flash to dbto_a and dbto_b)
but the app itself is amazing. Forget init.d tweaks, magisk tweaks, searching for ever-better kernels, kernel aduitor, and all the rest.
There's a profile section which allows downloaded presets, the one for 845 SOC works great.
Only other things I should mention are that I had trouble dling the apk from xda, so i got it from their github (google Lanthanum System Toolbox) , and I'm running Colt OS - Enigma ROM (https://forum.xda-developers.com/pi...unofficial-colt-os-enigma-crosshatch-t3953043)
, boot.img extracted using https://forum.xda-developers.com/nokia-7-plus/how-to/guide-how-to-extract-payload-bin-ota-t3830962
, magisk canary patched and reflashed.
oh, and it's mostly localized in chinese,
but there's enough english that i was able to use it with very little trouble
perhaps i got the wrong apk, cause the screenshots on the OP are english
I really am surprised that there isn't a reference thread in the crosshatch forum already . you may consider my tone hyperbolic, but try it and you'll see i'm being understated if anything. enjoy!
Click to expand...
Click to collapse
You used the dtbo.img from the mi9 thread that you linked? For me when I flash the dtbo.img the app just closes and nothing appears to happen. You were extract the boot.img for magisk or is it required for the mod as well? Thanks.
Well if some are interested, I can prepare kernel revisions with 64, 69, 70, 75, 80 and 84Hz screen refresh to test. I probably won't be able to test it before uploading each revision, so it would be up to each end user to check it's functionality. Of course I can get zero/natha/ responsibility if some devices are totally broken after.
melodystyle2003 said:
Well if some are interested, I can prepare kernel revisions with 64, 69, 70, 75, 80 and 84Hz screen refresh to test. I probably won't be able to test it before uploading each revision, so it would be up to each end user to check it's functionality. Of course I can get zero/natha/ responsibility if some devices are totally broken after.
Click to expand...
Click to collapse
That would be dope man, definitely willing to test it to tide me over until the pixel 4 comes out ?
eminem5055 said:
That would be dope man, definitely willing to test it to tide me over until the pixel 4 comes out
Click to expand...
Click to collapse
That would be awesome
OK, I ll try to get some permissions before building / posting the revisions.
melodystyle2003 said:
OK, I ll try to get some permissions before building / posting the revisions.
Click to expand...
Click to collapse
Sounds good man! ?
eminem5055 said:
Which dtbo.img did you use as well?
Click to expand...
Click to collapse
I used the one which is served directly from the OP I linked to..
I feel badly for all of the people who are having trouble with this.. bootloops and so forth. All I can say is I'm being truthful about the hardware and software I'm using, and it seems pretty straightforward to me. Using this device as my daily driver, still going strong.
ha7msterx said:
I used the one which is served directly from the OP I linked to..
I feel badly for all of the people who are having trouble with this.. bootloops and so forth. All I can say is I'm being truthful about the hardware and software I'm using, and it seems pretty straightforward to me. Using this device as my daily driver, still going strong.
Click to expand...
Click to collapse
ALSO, if the screen refresh part is a placebo, requiring a kernel modification to actually change, then ok.
Embarrassing to state, but I didn't actually test the resultant screen refresh rate, or really anything other than the subjective snappiness of my device.
So now I feel like I rushed to post, but I won't kill the thread because apparently melodystyle2003 is compiling a kernel. Thanks for that.
A small update, almost done with the first revision. I am dealing with some weird errors during the compiling procedure, that's why the 'almost' above, but hopefully tomorrow or day after tomorrow might have them tracked down and solved. After that, any upcoming revisions can be built much faster. My limited time can't guarantee any ETAs though. The guys that responded (with a like, quote or reply) to my previous relevant post, shall receive a download link of the kernel.
melodystyle2003 said:
A small update, almost done with the first revision. I am dealing with some weird errors during the compiling procedure, that's why the 'almost' above, but hopefully tomorrow or day after tomorrow might have them tracked down and solved. After that, any upcoming revisions can be built much faster. My limited time can't guarantee any ETAs though. The guys that responded (with a like, quote or reply) to my previous relevant post, shall receive a download link of the kernel.
Click to expand...
Click to collapse
Really looking forward to this
melodystyle2003 said:
A small update, almost done with the first revision. I am dealing with some weird errors during the compiling procedure, that's why the 'almost' above, but hopefully tomorrow or day after tomorrow might have them tracked down and solved. After that, any upcoming revisions can be built much faster. My limited time can't guarantee any ETAs though. The guys that responded (with a like, quote or reply) to my previous relevant post, shall receive a download link of the kernel.
Click to expand...
Click to collapse
Why don’t you just publish your code somewhere on github, so maybe somebody can help you to compile a kernel with your intended changes or can review the changes?
I’m pretty sure you can’t overclock the display of the pixel 3 devices as we’re using command mode panels and not video mode panels like some other devices where it’s possible to overclock the display refresh rate.
If you’re trying to modify this line for the pixel 3 xl:
https://github.com/freak07/Kirisaku...oogle/dsi-panel-s6e3ha8-dsc-wqhd-cmd.dtsi#L17
It will do nothing.
It’s similar to what happened in this thread and was described in this post
https://forum.xda-developers.com/showpost.php?p=79970079&postcount=35
Freak07 said:
Why don’t you just publish your code somewhere on github, so maybe somebody can help you to compile a kernel with your intended changes or can review the changes?
I’m pretty sure you can’t overclock the display of the pixel 3 devices as we’re using command mode panels and not video mode panels like some other devices where it’s possible to overclock the display refresh rate.
If you’re trying to modify this line for the pixel 3 xl:
https://github.com/freak07/Kirisaku...oogle/dsi-panel-s6e3ha8-dsc-wqhd-cmd.dtsi#L17
It will do nothing.
It’s similar to what happened in this thread and was described in this post
https://forum.xda-developers.com/showpost.php?p=79970079&postcount=35
Click to expand...
Click to collapse
Thanks for the information. On pocophone, changing the
"qcom,mdss-dsi-panel-framerate = <60>;" to the desired refresh rate i.e. 65 or more, was actually doing what was intended to. Have you tried something similar already that actually led only to the placebo effect described on the post you linked? If no, would you kindly do the corresponding changes in your kernel so someone can try it?
Regards
melodystyle2003 said:
Thanks for the information. On pocophone, changing the
"qcom,mdss-dsi-panel-framerate = <60>;" to the desired refresh rate i.e. 65 or more, was actually doing what was intended to. Have you tried something similar already that actually led only to the placebo effect described on the post you linked? If no, would you kindly do the corresponding changes in your kernel so someone can try it?
Regards
Click to expand...
Click to collapse
It´s not possible to overclock the displays of the pixel 3 or the pixel 3 xl that way. I don´t need to compile a test kernel to be able to tell you.
Displays running in command mode can´t be overclocked that way, unless you have access to internal files or you are able to flash display firmware to your device.
Both panels from Pixel 3 or Pixel 3 XL run in command mode:
https://github.com/freak07/Kirisaku...oogle/dsi-panel-s6e3ha8-dsc-wqhd-cmd.dtsi#L20
https://github.com/freak07/Kirisaku...google/dsi-panel-sw43408-dsc-fhd-cmd.dtsi#L20
Whereas the pocophone runs (as it seems more than one type of display across different units) all used panels in video mode.
https://github.com/d1stru3t0r/testz...qcom/dsi-panel-ebbg-fhd-ft8719-video.dtsi#L24
https://github.com/d1stru3t0r/testz.../dsi-panel-tianma-fhd-nt36672a-video.dtsi#L24
Panels in video mode can be overclocked this way, if it´s desirable is another question.
Sorry to be the bearer of bad news, but it´s simply not possible on Pixel 3 devices.
You can even unpack the dtbo.img, change the line you intend to change and any fps app might show you more than 60fps, but you just fooled the app into thinking our displays refresh at a higher rate than 60fps.
Hi ! im looking forward to change my rom and i wanted to know if specificly the xt2051-1 had one (cuz thats the one i have) i cant find any anywhere for it and i dont want to go for another versions rom cause i dont want my phone to f up i got my phone rooted and installed twrp on it ,my manager is magisk i am confortable with command lines even tho im learning + is there any programs i should use on my pc in case my phone decides to fudge?
thanks for the help
thanks for helping newbies like me
Considering you just got yours,we can assume that it has the new touch screen,so afaik the only rom that will work with touch is this one
https://build.lolinet.com/file/lineage/ginna/lineage-18.1-20210612-HOMEMADE-ginna.zip
This is electimons modded here on xda,and as far as i know nobody else has updated for the new touchscreen
timjames474 said:
This is electimons modded here on xda,and as far as i know nobody else has updated for the new touchscreen
Click to expand...
Click to collapse
A dev uploaded an unofficial 17.1 to AFH(1) w/ the new display driver a couple weeks back. It works great, except no audio besides during phone calls or when using headphones(or BT?, IDK).
I recently stumbled upon AlaskaLinuxUsers tutorial+videos(2) on how to setup & compile custom ROMs. Am in the process of setting up an Ubuntu workstation with 4th gen i5, 8GB DDR3, 2TB SSD & slow internet. It will take some time, apparently. My goal is to get this 17.1 working w/ new display &/or the working 18.1 w/ new display sans gapps. IDK if I will achieve a bootable ROM, but it looks like it's my only path, as outside of Electimon(3), not a lot of development is going on w/ Ginna anymore. Will post progress/results, if any is gained.
1
lineage-17.1-20210608-UNOFFICIAL-ginna.zip | ROM by elisam98 for Moto e 2020
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
2
[Guide][Video Tutorial] How to build Custom ROMs and Kernels![10,P,O,N,M,L]
Hey everyone! There is also a telegram channel where you can drop in for some help: https://t.me/joinchat/HR_8JgyDBdw_DvmndPl0kg I really hope that you have enjoyed the series, and that it was helpful to you in your Android career! Praise...
forum.xda-developers.com
3
Nothing but respect & gratitude for E's work. Am a long-time fan. However, his build contains Gapps & I don't want them.
Understandable if you get one going let me know because I'm currently on stock due to camera issues and I would love a ROM sans g apps especially if you would put sig spoof in for micro g
Just before i do something i just want to know if AOSP has a rom for that phone already cause its my fav rom of all time but if i have to port it myself is there any guidelines i could find on how to port/create custom roms ?
Imaunicorn666 said:
Just before i do something i just want to know if AOSP has a rom for that phone already cause its my fav rom of all time but if i have to port it myself is there any guidelines i could find on how to port/create custom roms ?
Click to expand...
Click to collapse
Two posts before yours, link #2.
I have been delayed... unidentified bug bite put me out of service for a bit. Wild f'n ride. Got Ubu w/s setup, will start provisioning/downloading tonight.
After ~14 hours downloading(multiple nights @ < 1MB/s... aggregating > 50 GB) on my wireless plan, I am yet to achieve a 100% sync of the LOS repo. After hitting the MU Throttle Threshold on last month's plan, I must concede defeat at this point as I cannot afford to jeopardize my only home inet option available for another 30 days(extreme rural living, no landlines or line-of-sight options). Sigh.
my schedule is full of other things but i will take a look at the links posted and attempt to to builds as it. LOS sans GAPPS sounds like a dream. currently I use 18.1 modded and manually degoogle it. its not so fun everytime i reset :/
Any update on a XT2051-1 with the new screen and no GAPPs
roycrt said:
Any update on a XT2051-1 with the new screen and no GAPPs
Click to expand...
Click to collapse
FWIW, I should have an internet connection capable of down/uploading in the next 2 weeks, at which time I will begin failing to compile until I succeed. Hopefully, on all points.
It seems like rolling the old 17.1 w/ the new display driver would be pretty straightforward, but a lot of ignorance is wrapped in that statement.
googleverifysux said:
FWIW, I should have an internet connection capable of down/uploading in the next 2 weeks, at which time I will begin failing to compile until I succeed. Hopefully, on all points.
It seems like rolling the old 17.1 w/ the new display driver would be pretty straightforward, but a lot of ignorance is wrapped in that statement.
Click to expand...
Click to collapse
Thank You googleverifysux! Just got the phone and would really like to degoogle it, then not worry for awhile
Hi all!
I have not been on here for several months but am starting to look at what's out there as of now. I am still on 12 and the June build with Kirisakura kernel. I would like to know what others are running so I can consider what to do next as it's time to start tinkering. Go to 13? Custom AOSP? What are most running now? And yes, I know the experience is unique to our devices so no need to point that out.
Thanks!
i use ricedroid v8 with kirisakura and it works perfectly
w_tapper said:
i use ricedroid v8 with kirisakura and it works perfectly
Click to expand...
Click to collapse
I second this.
Rice is one of the best custom roms here with loads of customisations and compatible with Kiri kernel.
I'm on stock for now but waiting for Rice 9
MidnightDevil said:
I second this.
Rice is one of the best custom roms here with loads of customisations and compatible with Kiri kernel.
I'm on stock for now but waiting for Rice 9
Click to expand...
Click to collapse
Awesome - this one did look great. I will check it out!
Thank you!!
I'm running paranoid android topaz. I like the fact the rom has an ota function. I think I gotta go thru the hassle of fastboot flashing root every update though
w_tapper said:
i use ricedroid v8 with kirisakura and it works perfectly
Click to expand...
Click to collapse
Agreed 100%.
fil3s said:
I'm running paranoid android topaz. I like the fact the rom has an ota function. I think I gotta go thru the hassle of fastboot flashing root every update though
Click to expand...
Click to collapse
I used to run PA on my past devices. Is this pretty stable in your experience?
darbylonia said:
I used to run PA on my past devices. Is this pretty stable in your experience?
Click to expand...
Click to collapse
Yes it's pretty stable. Some system apps show the 'app not responding' popup.
I experienced very severe slowdown and lag on stock. I think it had to do with cloud syncing. Although, on PA I don't experience any slowdown. Stable enough for daily use imo. Use the latest version
darbylonia said:
Hi all!
I have not been on here for several months but am starting to look at what's out there as of now. I am still on 12 and the June build with Kirisakura kernel. I would like to know what others are running so I can consider what to do next as it's time to start tinkering. Go to 13? Custom AOSP? What are most running now? And yes, I know the experience is unique to our devices so no need to point that out.
Thanks!
Click to expand...
Click to collapse
Depends on your objectives. If you have any interest in actual security, you should look at GrapheneOS. Pretty much everything else is made by kids who have no idea what they're doing, so don't trust it too far.
96carboard said:
Depends on your objectives. If you have any interest in actual security, you should look at GrapheneOS. Pretty much everything else is made by kids who have no idea what they're doing, so don't trust it too far.
Click to expand...
Click to collapse
Thanks! I will check out Graphene. Never tried it before. I am interested in security.
sjgoel said:
Agreed 100%.
Click to expand...
Click to collapse
Can you get rooted after it?
spinoza23 said:
Can you get rooted after it?
Click to expand...
Click to collapse
Yes.
Sandboxed gapps isn't flzwless. You can't sync contacts through google. If you consider graphene please research and don't just dive in like i did stupidly one day. It isn't customization focused so if you want to tweak stuff look into ricedroid or even crdroid. But if you want a secure os and don't use too much google graphene is the gold standard. Calling everything else garbage is a very terrible mindset. I try to encourage developers, not insult them like a certain someone in this thread
darbylonia said:
Thanks! I will check out Graphene. Never tried it before. I am interested in security.
Click to expand...
Click to collapse
if you want any extra features grapheneos is not what you want, unless you are being targetted by somebody or are super paranoid its overkill imo
MidnightDevil said:
I second this.
Rice is one of the best custom roms here with loads of customisations and compatible with Kiri kernel.
I'm on stock for now but waiting for Rice 9
Click to expand...
Click to collapse
Is rice like stock pixel ROM with all the same features like Now Playing etc? Obviously I know it has loads more customisations. Thanks.
Twilightsparklez said:
Sandboxed gapps isn't flzwless. You can't sync contacts through google. If you consider graphene please research and don't just dive in like i did stupidly one day. It isn't customization focused so if you want to tweak stuff look into ricedroid or even crdroid. But if you want a secure os and don't use too much google graphene is the gold standard. Calling everything else garbage is a very terrible mindset. I try to encourage developers, not insult them like a certain someone in this thread
Click to expand...
Click to collapse
Of course you can sync google contacts. Use DAVx5 as the interface software.
Twilightsparklez said:
Sandboxed gapps isn't flzwless. You can't sync contacts through google. If you consider graphene please research and don't just dive in like i did stupidly one day. It isn't customization focused so if you want to tweak stuff look into ricedroid or even crdroid. But if you want a secure os and don't use too much google graphene is the gold standard. Calling everything else garbage is a very terrible mindset. I try to encourage developers, not insult them like a certain someone in this thread
Click to expand...
Click to collapse
I am using GrapheneOS (my own Magisk Patched build) and you are able to sync google contacts with the included contacts app, it took a minute for them to appear after installing the play services and stuff then logging in, as well as granting the appropriate permissions, google play services needs the contacts permission, it's very secure by default and because of this you will need to grant google some permissions for everything to work as it does on google stock, like the notifications permission
w_tapper said:
if you want any extra features grapheneos is not what you want, unless you are being targetted by somebody or are super paranoid its overkill imo
Click to expand...
Click to collapse
Graphenes extra features are more security features, it does have far less customizability than some other roms but is still a great rom for every day use, I don't believe you need to be paranoid to want the security it offers
one of the main things for me is being able to lock the bootloader and have full AVB2 protections
this makes my data much more secure if the phone were to fall into the hands of someone else
You are also still able to root the phone with magisk and have a locked boot loader with Graphene if you build the rom yourself or use the builds I provide, this allows you to use Magisk and LSPosed to make further modifications as necessary
FireRattus said:
Graphenes extra features are more security features, it does have far less customizability than some other roms but is still a great rom for every day use, I don't believe you need to be paranoid to want the security it offers
one of the main things for me is being able to lock the bootloader and have full AVB2 protections
this makes my data much more secure if the phone were to fall into the hands of someone else
You are also still able to root the phone with magisk and have a locked boot loader with Graphene if you build the rom yourself or use the builds I provide, this allows you to use Magisk and LSPosed to make further modifications as necessary
Click to expand...
Click to collapse
yeah it does depend on your threat model ig, i find that i dont really need a locked bootloader so i dont mind