Related
Or rather lack of it.
I start of by saying, i am not a dev.
But i see that the way rom's is made for Galaxy lack's most of the things that makes custom rom's good, SGS's rom's seem more themes than proper custom rom's.
I have used Nexus and some of the great rom's to that device.
The SGS way to update FW seems to stop all real development?
What do you think?
samsung's drivers are encrypted and this makes developing roms pretty difficult. there can only be roms based on samsung releases. at least this is what i understood .
i am sure that the growing user base of this great phone will bring more attention from great developers ( hi paul ! , who will be able to overcome most of the problems and give us great roms.
The final non-beta firmware from Samsung hasn't even arrived yet! Give it some time!
Custom roms now would be obsolete within one week because of a newer official beta Firmware.
I was aware that a few days ago paul obrien was having a conversation to cyanogen about creating a vendor tree for the sgs which would enable us to use cyanogen mod. If someone can confirm this with paul this would be very good news for us sgs owners.
Sent from my GT-I9000 using XDA App
Right now I'd settle for a vanilla Froyo (my last phone was the N1).
The SGS has potential, but the stock ROM is so infested with Samsung customisations (eg non- AOSP dialer, contacts, music, etc etc), why have they re-invented the wheel?? Before this phone I didn't think fragmentation existed, only "legacy". Now I know exactly what fragmentation is, and it's ugly, annoying.
The only reason I ditched the N1 is because Google have said there would be no N2 so I figured I find another phone.
Now I realise how bad fragmentation is, the iPhone really doesn't look so bad again ... (previous to the N1, I was on a iPhone 3G)
It's a pity vendors can't be mandated to supply optional vanilla ROMs - I know Samsung have released a bunch of source code, maybe that's a start.
I guess I'll give it six months. I'm an end-user who wants an easy life, but appreciates the potential and integration with google services that Android provides - moreso in its vanilla form.
Did anybody try compiling the sourcecode that was released by samsung to create a flashable working version of the manufacturer Android version that is currently running in our phones?
If that is possible, and we do have the source code from samsung, I don't see why it would be impossible to get at least a vanilla AOSP 2.1-update1 running on our galaxies.
The encrypted (or closed source drivers) can be linked as binaries to the new AOSP build running on top of Samsung's kernel (which we do have the source code to).
Side question, anybody knows how to flash the phone once you got all source code by samsung compiled ? I know we end up with a zImage, possibly a system.img.. can you create Odin files with these easily ? any thoughts?
miker71 said:
Right now I'd settle for a vanilla Froyo (my last phone was the N1).
The SGS has potential, but the stock ROM is so infested with Samsung customisations (eg non- AOSP dialer, contacts, music, etc etc), why have they re-invented the wheel?? Before this phone I didn't think fragmentation existed, only "legacy". Now I know exactly what fragmentation is, and it's ugly, annoying.
The only reason I ditched the N1 is because Google have said there would be no N2 so I figured I find another phone.
Now I realise how bad fragmentation is, the iPhone really doesn't look so bad again ... (previous to the N1, I was on a iPhone 3G)
It's a pity vendors can't be mandated to supply optional vanilla ROMs - I know Samsung have released a bunch of source code, maybe that's a start.
I guess I'll give it six months. I'm an end-user who wants an easy life, but appreciates the potential and integration with google services that Android provides - moreso in its vanilla form.
Click to expand...
Click to collapse
same here. previous n1 user, got sgs just after google announced no n2 wil be available.
just took some actions to make things smoother for me :
1. launcher pro
2. dialer one
3. handcent sms
i used them all on n1 and now i do on sgs. its all good again . still, untill froyo hits us i think i will still miss n1's speed. also, i think after froyo hits us, we will get some more roms and goodies for our phones.
what exactly is a vendor tree? and how would it be able to get around the driver issue which is apparant to the SGS?
Some info on the .rfs files that samsung uses:
http://movitool.ntd.homelinux.org/trac/movitool/wiki/RFS
Merging into AOSP
It seems like good idea to have the scripts merged into AOSP tree that support building stock ROMS for samsung galaxy s, with binary-only files being downloaded directly from the device (if I'm not mistaken, this is how one can build froyo for N1 from source now).
From someone else experience: would the patches that add vendor-specific support for SGS be accepted into AOSP tree? Are there known blockers for this?
Hmm.. rom development is quite sluggish due to the firmwares that are being released!
But i really don't care! the original rom is fine with WJG5!
I just use Launcher Pro and widgets to make it better! Speed is ok!
bratfink said:
I was aware that a few days ago paul obrien was having a conversation to cyanogen about creating a vendor tree for the sgs which would enable us to use cyanogen mod. If someone can confirm this with paul this would be very good news for us sgs owners.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
This still doesn't get around the fact that the drivers are locked down and are near impossible to implement into outside roms that aren't Samsung based. Talking isn't doing anything.
miker71 said:
Right now I'd settle for a vanilla Froyo (my last phone was the N1).
The SGS has potential, but the stock ROM is so infested with Samsung customisations (eg non- AOSP dialer, contacts, music, etc etc), why have they re-invented the wheel?? Before this phone I didn't think fragmentation existed, only "legacy". Now I know exactly what fragmentation is, and it's ugly, annoying.
Click to expand...
Click to collapse
This isn't fragmentation though, this is exactly what Google wanted Android to be - a base for phone manufacturers to lay their own tweaks on top of. HTC, Motorola, Samsung etc don't just want to be differentiated by how their handset looks, they want to put their own stuff on there too. Previously each had their own OS (Symbian, UIQ etc.) that took years of development time and was very slow moving. Google provided Android as a quick route to market for a phone, the manufacturers didn't really have to worry too much about the OS and then get lots of apps for free.
The thing is, the vanilla apps are a bit.. basic. The standard music player is fine, it works and does what it says on the tin. The standard contacts is fine again etc. Makers can ship a ROM based on vanilla Android and it would be good to go, but if they can improve upon the apps and brand it slightly more then all well and good.
But it's not fragmentation. Android is a base. A starting point. It's not meant to look exactly the same on every device, but it's meant to work exactly the same as much as possible. These manufacturers get a stable, standard, capable phone OS for free, which to them is awesome. It saves them so much time and is ultimately why eventually there will be nothing but Android on devices. It's the Mac vs PC all over again - cool but closed and restricted vs ubiquitous free-for-all.
psychoace said:
This still doesn't get around the fact that the drivers are locked down and are near impossible to implement into outside roms that aren't Samsung based. Talking isn't doing anything.
Click to expand...
Click to collapse
If the right people get onto it it's only a matter of time. The G1 camera drivers were reverse engineered for Eclair CM ROMs after HTC gave the community sod-all.
dirk1978 said:
If the right people get onto it it's only a matter of time. The G1 camera drivers were reverse engineered for Eclair CM ROMs after HTC gave the community sod-all.
Click to expand...
Click to collapse
Didn't they have the source for 1.6's camera drivers? At least then they had a base to start from. That is not true with Samsungs drivers.
A little bit OT but due to the fact that in this thread are some EX-Nexus users: Would you recommend switching to the SGS ?
dirk1978 said:
it's meant to work exactly the same as much as possible.
Click to expand...
Click to collapse
It's when it doesn't work, it's very very annoying. How long do we have to wait for the Samsung music player to enable scrobbling? Sure I can use a different app from the Market - meaning Samsung wasted effort on their own Music app, why didn't they build on the AOSP version which does support scrobbling and iSyncr, etc because they use standard API or whatever so these other programs can read the state or whatever they need to do.
Same with dialer and contacts - on Launcher Pro, pressing the default Contacts icon - won't get you anything except maybe a FC :-(
The AOSP Desk Clock - where is that? If I install a clock from Market then I have two different Alarm daemons which is a waste of everyone's time when the default Clock in AOSP Eclair is fine and - more importantly - compatible with stuff and API calls.
Then all the other stuff that may or may not be Samsung stuff - the DRM, the Device Management, the Samsung Account - given the option I just don't want that stuff.
I'm intending to flash JG5 (from factory shipped JF3) which may increase performance but presume won't make these other problems go away.
I'm really happy with the hardware - but currently I am dissatisfied with the software and "Samsung knows best". For me, personally, Google knows best (and I bet they have data on me to prove it!), so I really want to see Froyo AOSP version for the Galaxy. That day may come, or it may not ...
I know I know, "can't please all of the people all of the time"
PAO1908 said:
A little bit OT but due to the fact that in this thread are some EX-Nexus users: Would you recommend switching to the SGS ?
Click to expand...
Click to collapse
Right now the question for me would be "do I recommend switching from Samsung OS from Froyo" - my answer would be no, unless:
1. better multitouch is important to you (better for gaming, no axis mess-up)
2. 4" screen is important (I do really like the Samsung screen)
3. Better built-in audio quality is important (the Galaxy is noticeably louder than the N1 and I think it may have a better A/D sampler too)
So fully recommend switching for hardware, UNLESS you can't live without Froyo.
I can live with the SGS shortcomings. Well, for a few months anyway ... and even if AOSP never comes there are alternatives in the Market but does mean you have to ignore the Samsung stock apps depending what you want to do (which means added complexity to your life, which I don't always have time to deal with!)
psychoace said:
This still doesn't get around the fact that the drivers are locked down and are near impossible to implement into outside roms that aren't Samsung based. Talking isn't doing anything.
Click to expand...
Click to collapse
Do you have any proof that the drivers are actually locked down in any way?
I can see the source of all the modules provided by samsung, just 3 of them (pvrsrvkm, s3cbc and s3clcd) are just precompiled, and if you check the info they are GPL.
Am I missing something?
@miker71
Thanks a lot !
Hey guys, just a quick question, is Cataclysm rom built off of a genuine stock system.img like the ones hosted on the google dev site? Or is some of it AOSP based? And if it is from stock genuine Android, isn't there some kind of legal issue with that? Just wondering this, I use Cataclysm and I LOVE IT! It's my daily driver! Thanks all!
H4X0R46 said:
Hey guys, just a quick question, is Cataclysm rom built off of a genuine stock system.img like the ones hosted on the google dev site? Or is some of it AOSP based? And if it is from stock genuine Android, isn't there some kind of legal issue with that? Just wondering this, I use Cataclysm and I LOVE IT! It's my daily driver! Thanks all!
Click to expand...
Click to collapse
The dev had an explanation of how it worked on the original thread. Android is open source and google releases sources for all the nexus devices and they also conveniently package them into flashable images to fix things. There was at least 1 release where the dev had to wait for the source to come out even though the factory images were out in order to do anything. So in short no there's no legal issue. The dev used open source files and modified them for non-profit. The reason no one else really does that type of mod is due to the fact that AOSP mods are widespread and people can just use others' code to incorporate them into the rom (or just use CM). Or if the dev is particularly dedicated then they might use an AOSP base because they want to keep up with all the bleeding edge enhancements to android which may or may not have any real benefit. When you target just 1 device by using its stock rom source then the mods have to be made for specifically that device (and why would anyone create code for 1 device when they could just use what works on virtually all devices) though the Nexuses are evidently similar enough to port between them hence the N5, 6, 5x, and 6p versions. The use of the stock source however meant that you kept the "rock solid stability" that Google's team of software engineers created so the dev could focus on adding features because the base he was working on was solid.
StykerB said:
The dev had an explanation of how it worked on the original thread. Android is open source and google releases sources for all the nexus devices and they also conveniently package them into flashable images to fix things. There was at least 1 release where the dev had to wait for the source to come out even though the factory images were out in order to do anything. So in short no there's no legal issue. The dev used open source files and modified them for non-profit. The reason no one else really does that type of mod is due to the fact that AOSP mods are widespread and people can just use others' code to incorporate them into the rom (or just use CM). When you target just 1 device by using its stock rom source then the mods have to be made for specifically that device (and why would anyone create code for 1 device when they could just use what works on virtually all devices) though the Nexuses are evidently similar enough to port between them hence the N5, 6, 5x, and 6p versions. The use of the stock source however meant that you kept the "rock solid stability" that Google's team of software engineers created so the dev could focus on adding features because the base he was working on was solid.
Click to expand...
Click to collapse
So all in all, Cataclysm is using stock Android and not AOSP, but done in a way that there are no legal issues? So in essence, flashing the system.img file from the dev site and adding Cataclysm mod to it is the the exact same difference as using the full Cataclysm installer? No AOSP added?
StykerB said:
.... "rock solid stability" that Google's team of software engineers created
Click to expand...
Click to collapse
That has a price:
- white ui, grey text on white bad readable; especially with sunlight;
- white background causes battery drain on amoled displays;
- pesky search bar; not removable or change to transparent;
- no option to change to a dark theme;
- N6 full resolution 2560 x 1440 not used;
- N6 native resolution = 493. G. sets it to 560 dpi;
- no option to kill running apps;
- code to use layers can't be used without rooting;
- G-apps not predestinated for layers.....etc.
NLBeev said:
That has a price:
- white ui, grey text on white bad readable; especially with sunlight;
- white background causes battery drain on amoled displays;
- pesky search bar; not removable or change to transparent;
- no option to change to a dark theme;
- N6 full resolution 2560 x 1440 not used;
- N6 native resolution = 493. G. sets it to 560 dpi;
- no option to kill running apps;
- code to use layers can't be used without rooting;
- G-apps not predestinated for layers.....etc.
Click to expand...
Click to collapse
Yes but would you rather not have something solid for people to build on? some of those things aren't even about stability... like the full resolution thing? assuming you're referring to onscreen buttons, and DPI is always on every device set in multiples of 80 for app standardization reasons. The overlay code for layers wasn't intended to be used for theming. Hence why google only used it for stuff like the ATT boot animation. and Google's apps and OS are separate and shouldn't be expected to adhere to a modding community's theme engine that they don't support. And dark themes were probably a design decision rather than actual stability issue.
StykerB said:
.....some of those things aren't even about stability... like the full resolution thing?....
Click to expand...
Click to collapse
You're right my list is not about stability only.
Using the N6 now for more than a year. I've seen a beta version with a dark theme, but it was removed. Why? Stability issues ?
To make the N6 acceptable for my daily use, especially battery life and readability, I had to change a lot of things. That has consequences for the stability. The N6 is still stable but I wouldn't say rock stable.
So all in all cataclysm is built using real Android? The main question in this thread lol But yea, AOSP does have it pros and cons as well as stock, I have to play devils advocate here and say that all roms do have their differences.
H4X0R46 said:
So all in all cataclysm is built using real Android? The main question in this thread lol But yea, AOSP does have it pros and cons as well as stock, I have to play devils advocate here and say that all roms do have their differences.
Click to expand...
Click to collapse
Yes what he did was use the stock android package. But make no mistake. AOSP is the real android. There are very few diff between what google releases and AOSP. The main diff is thie closed sourced stuff Google adds.
zelendel said:
Yes what he did was use the stock android package. But make no mistake. AOSP is the real android. There are very few diff between what google releases and AOSP. The main diff is thie closed sourced stuff Google adds.
Click to expand...
Click to collapse
Thanks! I was never sure just how much stuff is taken out of AOSP, but it's just small differences then. Glad I know that now! And hey, since we're on the subject, how are gapps legal? Aren't gapps those closed source bits that google DOES omit from AOSP? Play store and background things? Like, I know there's some legal thing where gapps shouldn't be preinstalled in an AOSP rom, but what's the grey area with gapps? Thanks again for the detailed description! Learning these things is good lol
If you have a look around, legal means very little here.
Google has only issued a C&D order to CM to not enclude it in their roms. This is why no aosp has them built in by default.
zelendel said:
If you have a look around, legal means very little here.
Google has only issued a C&D order to CM to not enclude it in their roms. This is why no aosp has them built in by default.
Click to expand...
Click to collapse
LOL I had a feeling that was the case here on XDA haha but I love Android and the development is HUGE! No other mobile OS can match Google's Android! Thanks for answering my questions man! Appreciate the help! Have a good rest of the night! Or day depending on where you're from, I'm from USA lol
H4X0R46 said:
LOL I had a feeling that was the case here on XDA haha but I love Android and the development is HUGE! No other mobile OS can match Google's Android! Thanks for answering my questions man! Appreciate the help! Have a good rest of the night! Or day depending on where you're from, I'm from USA lol
Click to expand...
Click to collapse
Im in the US as well. Well kinda lol I live in Alaska.
Yes it is but that might becoming to an end soon. With more and more people closing off their source. This is a good and bad thing. We will see what happens. Also more and more OEM are gonna lock down their devices so people will have to pic. Things like mobile pay or modding their device.
zelendel said:
Im in the US as well. Well kinda lol I live in Alaska.
Yes it is but that might becoming to an end soon. With more and more people closing off their source. This is a good and bad thing. We will see what happens. Also more and more OEM are gonna lock down their devices so people will have to pic. Things like mobile pay or modding their device.
Click to expand...
Click to collapse
Yea it's awful that people are making everything closed source! I'm a person who loves to tinker with my things, modded game consoles and phones and all, my hobby haha I just hope Android always stays open source! AOSP anyways. And are they starting to make Android devices more secure and non moddable? I hope the Nexus line always stays developer friendly, because I bought a Nexus for the sake of tinkering with it lol
H4X0R46 said:
Yea it's awful that people are making everything closed source! I'm a person who loves to tinker with my things, modded game consoles and phones and all, my hobby haha I just hope Android always stays open source! AOSP anyways. And are they starting to make Android devices more secure and non moddable? I hope the Nexus line always stays developer friendly, because I bought a Nexus for the sake of tinkering with it lol
Click to expand...
Click to collapse
Honestly. It because of script kiddies. The ones that just build from others source and post roms. Doing nothing but changing some text. To be honest all it would take is Google to stop pushing code to aosp. Android development would die off at that point.
Yeah if you look at things like Samsung, some devices are not even rootable, Sony, if you unlock the bootloader you lose the camera functions, even China based companies are locking bootloaders. Xiaomi just started doing this and have refused to give some the unlock because it goes against their business plan.
As for the nexus. We should be OK but then you have things like the Mm kernel that was a pain to get root on. And you lose mobile payments. Also more and more apps are looking for things like root and xposed and then refusing to work if they are installed.
zelendel said:
Honestly. It because of script kiddies. The ones that just build from others source and post roms. Doing nothing but changing some text. To be honest all it would take is Google to stop pushing code to aosp. Android development would die off at that point.
Yeah if you look at things like Samsung, some devices are not even rootable, Sony, if you unlock the bootloader you lose the camera functions, even China based companies are locking bootloaders. Xiaomi just started doing this and have refused to give some the unlock because it goes against their business plan.
As for the nexus. We should be OK but then you have things like the Mm kernel that was a pain to get root on. And you lose mobile payments. Also more and more apps are looking for things like root and xposed and then refusing to work if they are installed.
Click to expand...
Click to collapse
I've definitely heard of apps looking for root and for xposed framework (both of which I can't live without and use), and a lot of phones from certain companies are completely out of my interest because of no moddability. I wonder if it's even possible to root newer Samsung phones because of Knox security, and I won't even touch an Xperia, I've heard that they merge a lot of partitions, like boot and recovery and things like that, too confusing and not worth it to me. I just hope Android development stays strong in the Nexus scene at least, I love my Nexus!
Also, why do almost all AOSP ROMs have the "KitKat" sounds? Is that just what's released in AOSP? The "knocking" sounds I mean.
H4X0R46 said:
Also, why do almost all AOSP ROMs have the "KitKat" sounds? Is that just what's released in AOSP? The "knocking" sounds I mean.
Click to expand...
Click to collapse
To be honest I never noticed. I don't use any of the stock sounds.
H4X0R46 said:
I've definitely heard of apps looking for root and for xposed framework (both of which I can't live without and use), and a lot of phones from certain companies are completely out of my interest because of no moddability. I wonder if it's even possible to root newer Samsung phones because of Knox security, and I won't even touch an Xperia, I've heard that they merge a lot of partitions, like boot and recovery and things like that, too confusing and not worth it to me. I just hope Android development stays strong in the Nexus scene at least, I love my Nexus!
Click to expand...
Click to collapse
I dont think the Nexus line will see many issues other then root becoming harder to get.
Some Samsung devices cant be rooted. Like my buddy that is a samsung fan has a note 4, note 5 and a few Galaxy s5 in his house and all of them are locked down.
More and more people are too worried about things like warranty to even bother really. I even waited on updating the n6 until root was gotten for it.
Pretty sure those can be rooted but you trip Knox which voids warranty. I haven't looked at Sammy phones since I had my S4 but I know the Note 4 and S5 had ROMs.
HipKat said:
Pretty sure those can be rooted but you trip Knox which voids warranty. I haven't looked at Sammy phones since I had my S4 but I know the Note 4 and S5 had ROMs.
Click to expand...
Click to collapse
Nope no root for the note 5. Only some can be. The tmobile version doesn't lock the bootloader but the rest do.
As tripping Knox is not an option for many as it voids their warranty but flashing roms does that anyway.
This post is not demand a build for our phone, this post is not to get anybody upset it is just a question that I've had for many years.
I've owned every single Nexus device up until the Nexus 6P, and have owned every single pixel device... I remember that with each Nexus phone the support scene was so robust that you look forward to a new phone to come out and see development on it...
For some reason pixel phones are one of the only phones that don't get love from any custom ROM development out there.. you see that lineage OS does not support our phone and has not supported our phone since the Pixel 1 officially. Paranoid Android has not supported our phone at all since the Pixel 1 , And the last official update from them was in 2017.. why is it that our phone being one of the latest phones does not get love?
The main thing that I've heard is that our phone is too expensive to build for, but I have seen the OnePlus 7 pro have vast support in the community and it is almost up there as far as pricing goes as the pixel.
I have always been one to contribute to donations or to work that's worth donating to, dirty unicorns has been a great ROM, but if you think about it our selection of ROMs can be counted with one hand .
Make Google phones great again!
I also believe the pixels don't attract the custom rom enthusiasts like us they are made & sold & marketed to people to be a iPhone competitor also I feel a lot of developers are getting older & many devs just support a few phones that's it & there are not as many devs on the scene like there were years ago unfortunately I remember have my OG Droid from Verizon the support was crazy unfortunately I feel we have to look at it this way its a end of a era for google phones sad to say
Those custom roms are made to make our experience feel like Pixel. They take here and there from pixel feature. Since we are using pixel software, so what the point of having the custom rom? Kernel is more important. Thanks god we have artemis and kiri. Soon we will have Proton or maybe Sultan.
Btw we dont have TWRP support while there is for OP7Pro. Install a custom rom or make one is pain in the ass.
Because they consistently don't live up to expectations. Everybody keeps waiting for them to live up to hype and at least attempt to challenge others with hardware or respond to feedback and they continue to ignore that feedback. it's still in all right device, I like it it's overpriced as hell and I'm glad I waited a few months to get it, still tempted by the OnePlus 8 pro after leaving my 7 pro for this.
kickenwing13 said:
Because they consistently don't live up to expectations. Everybody keeps waiting for them to live up to hype and at least attempt to challenge others with hardware or respond to feedback and they continue to ignore that feedback. it's still in all right device, I like it it's overpriced as hell and I'm glad I waited a few months to get it, still tempted by the OnePlus 8 pro after leaving my 7 pro for this.
Click to expand...
Click to collapse
Better off going back to the 7 pro.It jus got Dual boot twrp. I'm running Oos and lineage as of this writing tomorrow might be different :laugh: . I got a 3xl and it lost twrp after Android 9 you can fastboot boot it with half the functions not working the 7t the same way an id imagine 8 pro be the same. Only way to have fun with Magisk on the 3xl Android 10 is to be running a user-debug build. Without the debug build magisk will let you overlay the system an look at your data but that's bout it. The way things look nowadays looking alot more locked down then they used to wait til Android 11 hits even more so is the case. Now Google going to build their own chipset like Samsung with help from Samsung Which will bring us one more step closer to Google Fuschia instead of Android
ROMs in general have gone down hill.
The need for them isn't really there. Early on, Android phones had tons of issues, shortcoming and limitations... ROMs were a way around that, to get the phones to work the way we wanted and the way they should have come out of the box.
Now? Most phones are really good, and there's not much to improve. ROM's don't really have much to offer any more, other than to a shrinking pool of users who want to tweak their phones more than they actually USE their phones...
Adding upon all comments above one of the reason is people are stuck with IOS. They don't know the actual power of Android. Who ever tries the Android are forced to go back to ios again because lack of facetime and other apps that are only available only ios
alwynjoshy said:
Adding upon all comments above one of the reason is people are stuck with IOS. They don't know the actual power of Android. Who ever tries the Android are forced to go back to ios again because lack of facetime and other apps that are only available only ios
Click to expand...
Click to collapse
Realistically, what's the power of android these days? Yes, you can tweak icons and the status bar and stuff, which 99.99% of phone owners don't care about...
The differences between the platforms isn't as great as it once was... I am on an iPhone 11 Pro at the moment and its a great phone... I want to come back to Android at some point but the watch situation on Android is a joke. And for the Pixels... they just never live up to the hype. I love Samsung, but updates still suck. There is OnePlus but some of the features like Wifi calling don't work on ATT half the time...
I prefer Android overall, but if you want the complete package with a good watch, Apple has the better package.
I had high hopes for Essential but we saw where that went...
I wish that Google would put out a pixel without giant bezels, that didn't have a last generation processor, etc... They will put out a phone in November that's using the same specs as phones that came out last month...
SquireSCA said:
Realistically, what's the power of android these days? Yes, you can tweak icons and the status bar and stuff, which 99.99% of phone owners don't care about...
The differences between the platforms isn't as great as it once was... I am on an iPhone 11 Pro at the moment and its a great phone... I want to come back to Android at some point but the watch situation on Android is a joke. And for the Pixels... they just never live up to the hype. I love Samsung, but updates still suck. There is OnePlus but some of the features like Wifi calling don't work on ATT half the time...
I prefer Android overall, but if you want the complete package with a good watch, Apple has the better package.
I had high hopes for Essential but we saw where that went...
I wish that Google would put out a pixel without giant bezels, that didn't have a last generation processor, etc... They will put out a phone in November that's using the same specs as phones that came out last month...
Click to expand...
Click to collapse
There are few functions which apple cant replace using of Clone applications, Root functions apps, custom fonts and many
alwynjoshy said:
There are few functions which apple cant replace using of Clone applications, Root functions apps, custom fonts and many
Click to expand...
Click to collapse
Realistically, today, what does the average person need root access on their phone for? I haven't rooted or ROM'd in several years... The tinkerer in me wants to, but I never find any compelling reason to...
I just don't care enough about what font my Instagram icon uses...
SquireSCA said:
Realistically, today, what does the average person need root access on their phone for? I haven't rooted or ROM'd in several years... The tinkerer in me wants to, but I never find any compelling reason to...
I just don't care enough about what font my Instagram icon uses...
Click to expand...
Click to collapse
my root need are viperfx, swift theme installer, fingerface , Sd maid ( save 2GB in every week when cleanup), etc
I have a Galaxy Note 10+. One of the heavy flagship phones from last year. There's about 3 ROMS and the communication in the threads is just about non-existent.
It's kinda sad because I remember my Note 4 having a ****load of AOSP ROM options and this phone has 1 that hasn't been updated in months. I would love to root/flash a ROM on my phone but I think the main thing is a lack of developers. Most have probably moved on and don't see a point in developing custom ROMs when most phones nowadays are capable of doing almost anything. The main reason I rooted/flashed ROMs was for the ability to customize my phone to my liking.
PieceofSlice said:
I have a Galaxy Note 10+. One of the heavy flagship phones from last year. There's about 3 ROMS and the communication in the threads is just about non-existent.
It's kinda sad because I remember my Note 4 having a ****load of AOSP ROM options and this phone has 1 that hasn't been updated in months. I would love to root/flash a ROM on my phone but I think the main thing is a lack of developers. Most have probably moved on and don't see a point in developing custom ROMs when most phones nowadays are capable of doing almost anything. The main reason I rooted/flashed ROMs was for the ability to customize my phone to my liking.
Click to expand...
Click to collapse
Exactly, and today, so many stock phones allow most of the customization that ROMs used to have to provide... And if not, install a different launcher and there are your themes...
i42o said:
This post is not demand a build for our phone, this post is not to get anybody upset it is just a question that I've had for many years.
I've owned every single Nexus device up until the Nexus 6P, and have owned every single pixel device... I remember that with each Nexus phone the support scene was so robust that you look forward to a new phone to come out and see development on it...
For some reason pixel phones are one of the only phones that don't get love from any custom ROM development out there.. you see that lineage OS does not support our phone and has not supported our phone since the Pixel 1 officially. Paranoid Android has not supported our phone at all since the Pixel 1 , And the last official update from them was in 2017.. why is it that our phone being one of the latest phones does not get love?
The main thing that I've heard is that our phone is too expensive to build for, but I have seen the OnePlus 7 pro have vast support in the community and it is almost up there as far as pricing goes as the pixel.
I have always been one to contribute to donations or to work that's worth donating to, dirty unicorns has been a great ROM, but if you think about it our selection of ROMs can be counted with one hand .
Make Google phones great again!
Click to expand...
Click to collapse
IMO Pixels don’t have the fan base of the type of enthusiast that install custom ROMs and such. Higher spec phones like OnePlus and stuff like they are more heavily modded i feel like because those types of people are attracted to the specs. Pixels don’t have specs that are anything to write home about. Where as a OnePlus with 12GB of RAM is pretty impressive.
TechOut said:
IMO Pixels don’t have the fan base of the type of enthusiast that install custom ROMs and such. Higher spec phones like OnePlus and stuff like they are more heavily modded i feel like because those types of people are attracted to the specs. Pixels don’t have specs that are anything to write home about. Where as a OnePlus with 12GB of RAM is pretty impressive.
Click to expand...
Click to collapse
That's probably it right there. The latest and greatest Pixel, uses specs that are already obsolete... Every year, they bring half year old specs and release their new phones with comparable specs to everyone else's specs that are already on the way out.
My thoughts below are mine, and mine only..
The reason you don't see as many custom roms here on xda imho is because it's no longer a hub that's a viable place for most roms to gain any value. the passion for development hasn't died. There are many great new features, and things users would love. Sure, the pixels are great out of the box, but you can say that for any flagship that has come out recently.
Don't get me wrong, xda is great, I'm just saying you shouldn't think devs and users have lost interest because their content isn't on xda.
I mean you're right,. It's different than the days of installing a ROM on a Droid x or something and actually seeing a notable difference between Moto blur and not. Or my note two with some of the different runs I could get on it. I don't know, I think I would like the freedom to make different apps different notifications so that I could customize notifications by app or by person a little easier for text messages. Little things like that that I feel like I used to get in some of those older arms but maybe not maybe I'm just misremembering or something.
Surge1223 said:
My thoughts below are mine, and mine only..
The reason you don't see as many custom roms here on xda imho is because it's no longer a hub that's a viable place for most roms to gain any value. the passion for development hasn't died. There are many great new features, and things users would love. Sure, the pixels are great out of the box, but you can say that for any flagship that has come out recently.
Don't get me wrong, xda is great, I'm just saying you shouldn't think devs and users have lost interest because their content isn't on xda.
Click to expand...
Click to collapse
Where should one go to get ROM's for this device?
jmartin72 said:
Where should one go to get ROM's for this device?
Click to expand...
Click to collapse
After hours of research I think I have found some in the ROM section of this forum
Mackay53 said:
After hours of research I think I have found some in the ROM section of this forum
Click to expand...
Click to collapse
Why not try reading before you post, and make yourself look foolish.
As far as I can remember OnePlus has had ROMs / mods / kernels and god knows what very early on.
This turd? it's at the back of a very long smelly queue, the level of interest is non existent.
If you're planning to jump ship to this!
Don't.
Get a pixel or wait.
For me if this phone fails then it's bye bye OnePlus.
WTH happened??
They became successful and don't need the community anymore. It wouldn't surprise me to find out the 11 series ships with entirely disabled fastboot like Oppo devices apparently have.
Those mods depends on developers... Those guys get old and do not care about development anymore.
We now have only the manufacturers and google mainly.
Including Android 13 beta, it's available for us.
EtherealRemnant said:
They became successful and don't need the community anymore. It wouldn't surprise me to find out the 11 series ships with entirely disabled fastboot like Oppo devices apparently have.
Click to expand...
Click to collapse
I've got no words for that..
Just an emoji.
To you OnePlus
zopostyle said:
Those mods depends on developers... Those guys get old and do not care about development anymore.
We now have only the manufacturers and google mainly.
Including Android 13 beta, it's available for us.
Click to expand...
Click to collapse
I've made a mod for this device mate. I've made guides.
Something is different with this device.
I just wish I'd seen it before.
Game over for me pal... Sitting with this crap OOS for another year?? No chance I'm getting the pixel 7 this turd it's getting sold
dladz said:
I've made a mod for this device mate. I've made guides.
Something is different with this device.
I just wish I'd seen it before.
Game over for me pal... Sitting with this crap OOS for another year?? No chance I'm getting the pixel 7 this turd it's getting sold
Click to expand...
Click to collapse
Honestly the holdup is probably on Qualcomm. Sahara is updated v3.x, so all firehose tools we've had stopped working. If MSM was leaked successfully, people would be able to reverse the new protocol, so QCom probably put more restrictions on OEMs to prevent that. Additionally, sources still doesn't seem to be released so nothing really can be built against. Check out any SD8G1 devices and the dev support currently:
Moto Edge X30: https://forum.xda-developers.com/f/moto-edge-x30.12479/?prefix_id=33 (nothing)
Applies to other Motos: https://forum.xda-developers.com/f/motorola-edge-2022.12581/?prefix_id=33, https://forum.xda-developers.com/f/moto-edge-30-pro.12543/
Xiaomi 12 Pro: https://forum.xda-developers.com/f/xiaomi-12-pro.12493/?prefix_id=33 (sad)
Same with other Xiaomi SD8G1s, https://forum.xda-developers.com/f/xiaomi-12.12491/?prefix_id=33
Honor: https://forum.xda-developers.com/f/honor-magic-4-ultimate.12577/?prefix_id=33 (nothing)
Nubia: https://forum.xda-developers.com/f/nubia-red-magic-7.12563/?prefix_id=33 (nothing)
Realme: https://forum.xda-developers.com/f/realme-gt-2-pro.12549/?prefix_id=33 (nothing)
The pickings are gonna be slim if you wanna be on SD8G1 and want a custom ROM.
craznazn said:
Honestly the holdup is probably on Qualcomm. Sahara is updated v3.x, so all firehose tools we've had stopped working. If MSM was leaked successfully, people would be able to reverse the new protocol, so QCom probably put more restrictions on OEMs to prevent that. Additionally, sources still doesn't seem to be released so nothing really can be built against. Check out any SD8G1 devices and the dev support currently:
Moto Edge X30: https://forum.xda-developers.com/f/moto-edge-x30.12479/?prefix_id=33 (nothing)
Applies to other Motos: https://forum.xda-developers.com/f/motorola-edge-2022.12581/?prefix_id=33, https://forum.xda-developers.com/f/moto-edge-30-pro.12543/
Xiaomi 12 Pro: https://forum.xda-developers.com/f/xiaomi-12-pro.12493/?prefix_id=33 (sad)
Same with other Xiaomi SD8G1s, https://forum.xda-developers.com/f/xiaomi-12.12491/?prefix_id=33
Honor: https://forum.xda-developers.com/f/honor-magic-4-ultimate.12577/?prefix_id=33 (nothing)
Nubia: https://forum.xda-developers.com/f/nubia-red-magic-7.12563/?prefix_id=33 (nothing)
Realme: https://forum.xda-developers.com/f/realme-gt-2-pro.12549/?prefix_id=33 (nothing)
The pickings are gonna be slim if you wanna be on SD8G1 and want a custom ROM.
Click to expand...
Click to collapse
There are MSM Tools out for ColorOS on the 10 Pro though. Three of them, in fact, are publicly available, they're just encrypted.
一加10 Pro/9008线刷救砖包ColorOS 12.1 A.04 - 一加手机官方ROM - 一加手机官方ROM下载
本站提供一加全机型ROM下载，包括一加Ace 2V、ACE2、Ace/10R、一加10 Pro、9Pro、9RT、9R、8T、8 Pro、一加8、7T Pro、7T、7Pro等全系一加机型的升级全量包、降级包、9008线刷救砖包等各种官方和原厂ROM，全部资源完全免费，不限速，无需登录
yun.daxiaamu.com
一加10 Pro/9008线刷救砖包ColorOS 12.1 A.07 - 一加手机官方ROM - 一加手机官方ROM下载
本站提供一加全机型ROM下载，包括一加Ace/10R、一加10 Pro、一加9Pro、一加9RT、一加9R、一加8T、一加8 Pro、一加8、一加7T Pro、一加7T、一加7Pro等全系一加机型的升级全量包、降级包、9008线刷救砖包等各种官方和原厂ROM，全部资源完全免费，不限速，无需登录
yun.daxiaamu.com
NE2210domestic_11_A.12_2022030701060000.zip - 一加手机官方ROM - 一加手机官方ROM下载
本站提供一加全机型ROM下载，包括一加Ace/10R、一加10 Pro、一加9Pro、一加9RT、一加9R、一加8T、一加8 Pro、一加8、一加7T Pro、一加7T、一加7Pro等全系一加机型的升级全量包、降级包、9008线刷救砖包等各种官方和原厂ROM，全部资源完全免费，不限速，无需登录
yun.daxiaamu.com
If Qualcomm is going to start being anti-developer, I guess it's a good thing that Pixel doesn't use their processors anymore.
EtherealRemnant said:
There are MSM Tools out for ColorOS on the 10 Pro though. Three of them, in fact, are publicly available, they're just encrypted.
Click to expand...
Click to collapse
Exactly, it got leaked but OnePlus put more protections around it. The thing itself is packed as well, I was able to start reversing it, and the protocol commands are COMPLETELY different. A lot of lower level things are much easier to reverse from dynamic analysis rather than static with vmprotect and other packers on. I don't really have time to do a full deep dive analysis on the protocol while not being able to even see it in action, just complete guesses. See https://github.com/bkerler/edl/issues/274 for a brief description in the 3rd post. Even if the loader is sent, the magic to start communication in firehose is now different as well, so after getting past sahara, now you have to deal with firehose.
craznazn said:
Exactly, it got leaked but OnePlus put more protections around it. The thing itself is packed as well, I was able to start reversing it, and the protocol commands are COMPLETELY different. A lot of lower level things are much easier to reverse from dynamic analysis rather than static with vmprotect and other packers on. I don't really have time to do a full deep dive analysis on the protocol while not being able to even see it in action, just complete guesses. See https://github.com/bkerler/edl/issues/274 for a brief description in the 3rd post. Even if the loader is sent, the magic to start communication in firehose is now different as well, so after getting past sahara, now you have to deal with firehose.
Click to expand...
Click to collapse
Sounds like it is time to move away from Qualcomm then. I guess my next phone is going to be a Pixel after all. At least there I know that I'll get rapid updates that actually fix bugs rather than this nonsense with OnePlus that forces people to go to custom ROMs just to get basic functionality and a stable device in the first place.
EtherealRemnant said:
Sounds like it is time to move away from Qualcomm then. I guess my next phone is going to be a Pixel after all. At least there I know that I'll get rapid updates that actually fix bugs rather than this nonsense with OnePlus that forces people to go to custom ROMs just to get basic functionality and a stable device in the first place.
Click to expand...
Click to collapse
Honestly I would just stick with OP9 on a supported stable rom of some kind and use it into the ground. Not sure what's going on but look at the dev section for Pixel 6 Pro, you got kernels, and that's about it, and it's been over 6 months since release already. The few roms that did come out are dying or dead.
If you don't care for custom roms to begin with, then samsung is always an option with an arguably better support promise than google
craznazn said:
Honestly I would just stick with OP9 on a supported stable rom of some kind and use it into the ground. Not sure what's going on but look at the dev section for Pixel 6 Pro, you got kernels, and that's about it, and it's been over 6 months since release already. The few roms that did come out are dying or dead.
If you don't care for custom roms to begin with, then samsung is always an option with an arguably better support promise than google
Click to expand...
Click to collapse
Oh no, I definitely do care for custom ROMs, I am *never* happy being locked down to what the manufacturer wants me to have which is why my last Samsung was the Note 5. If I got a Pixel, I would probably install ProtonAOSP (which is available on Pixel 6/Pro), use the Pixelify Magisk module to get back anything I lost, and be happy as can be. The only reasons I didn't go with the Pixel 6 originally were the reports of the crappy screen, the crappy Samsung modem (that's still giving people problems), and the crappy battery life. The 6 Pro was out because of the curved screen, the crappy modem, and the crappy battery life. My OP9 has none of those issues, just janky stock software complete with a massive and unacceptable SoC throttle and a buggy boot/fastboot implementation that makes it easy to brick.
I am happy with my OnePlus 9 now that I have StagOS paired with OOS12 C.48 firmware, there are only very minor issues and one major one that I have to remember to work around every time I restart the phone, but I am never happy for long and I get grass is always greener syndrome pretty frequently lol. I have been keeping tabs on the OP10P forum because it was originally going to be my next device (I only just got my 9 in February and I'm already wanting something new) but obviously the situation right now with OOS12 being a dumpster fire and how many people have bricked their OP10P trying to root it or change the firmware between regions... it's not a great sales pitch for sure when there isn't an MSM available and it sounds like there won't be for quite awhile, if ever.
There are so many issues with this phone and I started to hate the OnePlus. I'm definitely going to change my OP10 Pro to Google Pixel 7!
Yeah, I've been a oneplus fan for a long time. AT&T forced me to upgrade from my OP7Pro due to them discontinuing the older bands and I got the 10 pro without much research.
It works great, I've been loving it and it hasn't had nearly as much bugs as others have said with the hangs and what not. Everything feels super crisp, but I definitely agree with the overtuning optimization. Can't even background a game to send a text without it closing. Terrible.
So I'm already thinking I should have gotten the 9 Pro. More 5G bands, why the hell they got RID of a feature is beyond me, and actual custom ROM support, albeit very new. I'm sure given enough time the 10 pro will have custom roms, but the drought sure is making me feel like trading it in for the 9 Pro.
TL;DR Definitely considering trading in my OP10Pro for OP9Pro.
Prant said:
Yeah, I've been a oneplus fan for a long time. AT&T forced me to upgrade from my OP7Pro due to them discontinuing the older bands and I got the 10 pro without much research.
It works great, I've been loving it and it hasn't had nearly as much bugs as others have said with the hangs and what not. Everything feels super crisp, but I definitely agree with the overtuning optimization. Can't even background a game to send a text without it closing. Terrible.
So I'm already thinking I should have gotten the 9 Pro. More 5G bands, why the hell they got RID of a feature is beyond me, and actual custom ROM support, albeit very new. I'm sure given enough time the 10 pro will have custom roms, but the drought sure is making me feel like trading it in for the 9 Pro.
TL;DR Definitely considering trading in my OP10Pro for OP9Pro.
Click to expand...
Click to collapse
The phone is on point mate, the stamina and performance...even the camera is good (beside the lack of macro) video zooming is amazing and so smooth and stable, battery will last 3 days with little use or 10+ hours SOT otherwise, definitely 8+
Performance as I said is nuts. PS2 games? No problem, full 60 FPS which is a vast improvement over my 8pro, the 8 gen1 is superb, my phone's never got over 32-34c
I've read it's Qualcomm being bumholes, I've heard Devs just won't get it (waiting for the 11)
I've read all kinds of madness.
This would be the first time OnePlus has really dished out a dodo... Honestly the last time I felt like this it was with HTC, only we had ROMs to flash, I know things have changed and Google wants to go the way of Apple, probably to get a nod from corporate tools who couldn't care less and will still buy an iPhone anyway.
I know we only account for a small percentage of people who buy Android devices and mod them I think it was 5-10% maybe less. But it doesn't end with those numbers, every person on XDA (well a large number) are usually the designated IT as nominated by their mum/dad/sisters etc and we fix things for everybody, but we also influence what they buy so no that percentage is a load of old twaddle, if you couple the rooters with the people we influence and the people the talk to, then that number is a much higher percentage.
Just reminds me of the HTC one X when Nvidia got hold of it and locked it down, HTC never recovered from that, Samsung saw an opening and the Galaxy's S took over, I think the pixel or something else will do the same to OnePlus, have been looking at the nothing phone, it looks ridiculous but it there's a custom ROM scene for it then I'm heading that way after one year with this.
dladz said:
The phone is on point mate, the stamina and performance...even the camera is good (beside the lack of macro) video zooming is amazing and so smooth and stable, battery will last 3 days with little use or 10+ hours SOT otherwise, definitely 8+
Performance as I said is nuts. PS2 games? No problem, full 60 FPS which is a vast improvement over my 8pro, the 8 gen1 is superb, my phone's never got over 32-34c
I've read it's Qualcomm being bumholes, I've heard Devs just won't get it (waiting for the 11)
I've read all kinds of madness.
This would be the first time OnePlus has really dished out a dodo... Honestly the last time I felt like this it was with HTC, only we had ROMs to flash, I know things have changed and Google wants to go the way of Apple, probably to get a nod from corporate tools who couldn't care less and will still buy an iPhone anyway.
I know we only account for a small percentage of people who buy Android devices and mod them I think it was 5-10% maybe less. But it doesn't end with those numbers, every person on XDA (well a large number) are usually the designated IT as nominated by their mum/dad/sisters etc and we fix things for everybody, but we also influence what they buy so no that percentage is a load of old twaddle, if you couple the rooters with the people we influence and the people the talk to, then that number is a much higher percentage.
Just reminds me of the HTC one X when Nvidia got hold of it and locked it down, HTC never recovered from that, Samsung saw an opening and the Galaxy's S took over, I think the pixel or something else will do the same to OnePlus, have been looking at the nothing phone, it looks ridiculous but it there's a custom ROM scene for it then I'm heading that way after one year with this.
Click to expand...
Click to collapse
On point brother,
This is happening atm, and my last op phone unfortunately. This brand was the pc of the smartphone world, modding and general feel wise but not anymore...
dladz said:
Just reminds me of the HTC one X when Nvidia got hold of it and locked it down, HTC never recovered from that, Samsung saw an opening and the Galaxy's S took over, I think the pixel or something else will do the same to OnePlus, have been looking at the nothing phone, it looks ridiculous but it there's a custom ROM scene for it then I'm heading that way after one year with this.
Click to expand...
Click to collapse
Nah, something else might come along but not Google. You can always leave it up to Google to **** something good up.
Though I wouldn't communicate it in the same way (please keep it civil folks), I do very much agree that OnePlus has become exactly what they were up against back in 2014. They've become massive hypocrites by shutting out the community that made them. There was so much amazing development on the OnePlus One, which I have proudly owned as a daily driver for over 3 years, that a lot of community invented/inspired goodies ended up in all Android iterations by all brands active in the market today. It was truly revolutionary. And this is how OnePlus thanks us today: with a knife in our collective backs. Under the disguise of "improving security" – which is an easy excuse for a lot of things – companies like OnePlus and of course also Google have been striking development communities hard. Why? Not willing to deal with any liability or unpredictable situations (shareholders like keeping things predictable) I guess. The cool thing, though, is that we're still here and we're still developing!
I currently have high hopes for Nothing. If it'll be anything like Bacon, another community revolution is just around the corner...
Aldonski said:
On point brother,
This is happening atm, and my last op phone unfortunately. This brand was the pc of the smartphone world, modding and general feel wise but not anymore...
Click to expand...
Click to collapse
Cheers ace, I was slightly inebriated last night
Timmmmaaahh! said:
Though I wouldn't communicate it in the same way (please keep it civil folks), I do very much agree that OnePlus has become exactly what they were up against back in 2014. They've become massive hypocrites by shutting out the community that made them. There was so much amazing development on the OnePlus One, which I have proudly owned as a daily driver for over 3 years, that a lot of community invented/inspired goodies ended up in all Android iterations by all brands active in the market today. It was truly revolutionary. And this is how OnePlus thanks us today: with a knife in our collective backs. Under the disguise of "improving security" – which is an easy excuse for a lot of things – companies like OnePlus and of course also Google have been striking development communities hard. Why? Not willing to deal with any liability or unpredictable situations (shareholders like keeping things predictable) I guess. The cool thing, though, is that we're still here and we're still developing!
I currently have high hopes for Nothing. If it'll be anything like Bacon, another community revolution is just around the corner...
Click to expand...
Click to collapse
Huawei!! Seems they all sing from the same song sheet.
Bring back HTC, c'mon Taiwan. You got this bro..
dladz said:
Huawei!!
Click to expand...
Click to collapse
I'm new to the world of root and I want to try different ROMS, custom kernels, debloat, etc. I'm fully aware of the risks that come with rooting my phone, and I'm ready to go. I have a Pixel 5a. When I check out the 5a forums, there's not much there. The P5 has all the action! I want to know if I substitute the Barbet images for the Redfin images, can I use the Pixel 5 methods on my 5a?
keylimepienapples3000 said:
I'm new to the world of root and I want to try different ROMS, custom kernels, debloat, etc. I'm fully aware of the risks that come with rooting my phone, and I'm ready to go. I have a Pixel 5a. When I check out the 5a forums, there's not much there. The P5 has all the action! I want to know if I substitute the Barbet images for the Redfin images, can I use the Pixel 5 methods on my 5a?
Click to expand...
Click to collapse
You can use the same methods to root, but you can't use the custom firmware built for the 5
xunholyx said:
You can use the same methods to root, but you can't use the custom firmware built for the 5
Click to expand...
Click to collapse
Right on. Thanks for the reply.. Why does the 5 seem so much more popular?
Because the 5 was the "flagship" device that year
The Pixel 5 and 5a share the same SoC, so the firmware is effectively the same between them. Still, for the sake of being safe, I wouldn't mix and match.
The only difference between the two is the 5 has 8GB RAM, while the 5a has a bigger screen and a bigger battery. Other than that, they're identical.
Thanks for the info.. How risky is it-- If the biggest difference is in the RAM? About 10 or 12 years ago I read an article about Android and it's capabilities through open source code, so I've wanted to root and mess around with ROMS and different firmware for a long time. Unfortunately, at that time I was in prison so naturally I didn't have access to a phone. I got home in 2020 looking to change my life so I've tried to at least make this a hobby. So far I'm somehow not very lucky in getting the right phones. I thought I finally did last year when I bought a Moto Stylus 5g from cricket. I paid the phone off, cricket unlocked it, but Motorola won't give up the unlock code. Then I got a Pixel 3 but it turned out to be from Verizon and they're haters off the jump, so that was a huge disappointment too. Finally, I have this Pixel 5a. Factory unlocked, incredibly easy as far as unlocking the bootloader and rooting go and I can't seem to find a custom ROM for it. I was able to flash to graphene OS, but there were some issues with my esim so I went back to stock. A couple nights ago I tried Bliss ROMs but I don't know what I'm doing wrong there but I can't get it to work. I got kind of excited about the pixel experience plus, but that guy doesn't seem to be messing around with it anymore, he says there doesn't seem to be enough interest in it. When I look at the Pixel 5 forum, they have all the bells and whistles! I don't have an education nor do I have the money to buy phone after phone. Especially some of the more popular brands. Unless I'm looking at a ROM that requires more of it, how does 2gb if RAM make such a difference? Also you replied to another question I posted. About locking the bootloader.. what happens if I lock it without having the stock and bone firmware?
keylimepienapples3000 said:
Thanks for the info.. How risky is it-- If the biggest difference is in the RAM? About 10 or 12 years ago I read an article about Android and it's capabilities through open source code, so I've wanted to root and mess around with ROMS and different firmware for a long time. Unfortunately, at that time I was in prison so naturally I didn't have access to a phone. I got home in 2020 looking to change my life so I've tried to at least make this a hobby. So far I'm somehow not very lucky in getting the right phones. I thought I finally did last year when I bought a Moto Stylus 5g from cricket. I paid the phone off, cricket unlocked it, but Motorola won't give up the unlock code. Then I got a Pixel 3 but it turned out to be from Verizon and they're haters off the jump, so that was a huge disappointment too. Finally, I have this Pixel 5a. Factory unlocked, incredibly easy as far as unlocking the bootloader and rooting go and I can't seem to find a custom ROM for it. I was able to flash to graphene OS, but there were some issues with my esim so I went back to stock. A couple nights ago I tried Bliss ROMs but I don't know what I'm doing wrong there but I can't get it to work. I got kind of excited about the pixel experience plus, but that guy doesn't seem to be messing around with it anymore, he says there doesn't seem to be enough interest in it. When I look at the Pixel 5 forum, they have all the bells and whistles! I don't have an education nor do I have the money to buy phone after phone. Especially some of the more popular brands. Unless I'm looking at a ROM that requires more of it, how does 2gb if RAM make such a difference? Also you replied to another question I posted. About locking the bootloader.. what happens if I lock it without having the stock and bone firmware?
Click to expand...
Click to collapse
Stay on stock ROM. Root, and use this Magisk/Xposed MOD..
[MOD][Xposed+Magisk][13 Compatible] AOSP Mods - System modifications for AOSP-based Android 12+
This is a mixed Xposed+Magisk module, which is made to allow customizations that are not originally designed in AOSP (Android Open Source Project). Features: Currently, AOSP Mods offers customizations on different aspects of system framework and...
forum.xda-developers.com
As for RAM, see if this helps, it "Expands RAM memory by converting a part (Internal) storage to swap RAM."
Thank you. I'm going to check it out now.
Ok. My phone didn't like swapper very much. After rebooting, my screen was flickering out of control and I couldn't do anything but power down. After a couple of reboots it started up normally but now I can't use mobile data and I'm not able to access any Magisk Modules. The button is greyed out. Any idea how to reverse this?
keylimepienapples3000 said:
Ok. My phone didn't like swapper very much. After rebooting, my screen was flickering out of control and I couldn't do anything but power down. After a couple of reboots it started up normally but now I can't use mobile data and I'm not able to access any Magisk Modules. The button is greyed out. Any idea how to reverse this?
Click to expand...
Click to collapse
oh wow that's very odd how many GB did you do? I suggest 2 but if it's doing that then yea lets rid it.
when it's grey it mean it'sdisabled. you can click the remove button and reboot and it will be gone.