Database Develop

(discussion) Rom development for Galaxy

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 !

Rom developers please listen!!

So this is a post for just making people realise some of the things going on in the Samsung Galaxy Tab A development forum (specifically the custom Rom development). So let's get right into the thing. I believe custom Rom should be focusing on bringing newness to old devices. Of course and some features are not available in New devices, and custom Rom and debloated roms help fill the gap ( we all know how heavily modded Samsung firmware is).
However recently there is a trend for DEVELOPERS to make custom roms for recently released devices ( SM-T580, SM-T280) . While the old 2015 models and others have no roms yet. I did hear that someone was making a unified Rom for some of these models months ago. I'm not saying that there shouldn't be any roms for new models . But there is an overcrowding in the market with custom roms for these devices and also with very little difference between these roms. Imagine this like there are a lot of products for one group of people and the rest get no products at all!
So this is my petition. Can just some of you show a bit love for these devices? If enough of you respond to this maybe there will be a positive change! That's all I want . I want everyone to pass this message around. Thanks for the help. And thank you Developers who make custom roms for any device because I know it's a hard job and you are doing this for free. :good:
Peace
P.S: This is my first post. I know I did some things wrong. So PLEASE don't be too critical about this.

Hint, Hint!! Devs make mods for devices they OWN. They aren't in it to support Samsung. They aren't in it to be charitable. They are in it because they enjoy doing what they do and want the "latest and greatest" for themselves. But they ARE NOT going to support old devices they no longer have.
edit: There is also the fact that "custom" ROMs, like RR, Extremely and Ultra, are all just modifications of the STOCK ROM from Samsung. So, if Samsung hasn't produced a new ROM for an older device, then there is nothing to modify. The exception to that are the ROMs based on the LineageOS. But, again, these are based on adaptions from other devices that use the same SoC. So, if the LineageOS devs haven't produced one for the SoCs in older devices, you won't see one for your older Tab A.

Then why do they provide support for their releases. I get the thing you said about how roms a modified. But I dont think they make it just for themselves. If that were the case the would not be any "community" and XDA IS a well-knit community. Developers like @ashyx and @JazzPresso provide and support people with their mods and stuff. So the "want the "latest and greatest" for themselves. But they ARE NOT going to support old devices they no longer have. " part I don't get.
Sent from my Samsung SM-T355 using XDA Labs

How are they supposed to debug problems when they no longer have a device to use for testing? What's not to get?

But once you have device tree (more or less in stone) it's easy to just keep up to date. (To a degree) but only the latest popular devices get anything. Look at the smt280 ... Absolutely f***ING nothing past root for it. One decent time (decent being used loosely) while the exact same one other than modems are activated (t285) gets quite a bit of love. They are the exact same device! I'm fairly sure the 280 even has the modems! Just deactivated. We have to work with the devs more flexibility do they can do build and have GOOD feedback, timely reports and sure knowledge of how to log. (I stuck at it all) that's how but there are thread after thread of similar devices that none ever gives these devs the info. Dumps, etc that is needed to help us. We inquire on root or rom then they ask for stuff and we disappear. Never to be heard from again. Lots of these devs are so selfless in their endeavor with goose eggs for return

remarkablecow913 said:
But once you have device tree (more or less in stone) it's easy to just keep up to date. (To a degree) but only the latest popular devices get anything. Look at the smt280 ... Absolutely f***ING nothing past root for it. One decent time (decent being used loosely) while the exact same one other than modems are activated (t285) gets quite a bit of love. They are the exact same device! I'm fairly sure the 280 even has the modems! Just deactivated. We have to work with the devs more flexibility do they can do build and have GOOD feedback, timely reports and sure knowledge of how to log. (I stuck at it all) that's how but there are thread after thread of similar devices that none ever gives these devs the info. Dumps, etc that is needed to help us. We inquire on root or rom then they ask for stuff and we disappear. Never to be heard from again. Lots of these devs are so selfless in their endeavor with goose eggs for return
Click to expand...
Click to collapse
The last Samsung stock ROM for the 280 was 5.1. and there is no Linage version later than that to work from. But if you are so sure there is no difference between the 280 and 285, other than the modem, why don't you try flashing the 285 ROM on the 280? There is an Omni 6.0 ROM for the 285. I've successfully flashed 585 ROMs on a 580.
Anyway, complaining isn't going to change anything. No dev is going to put any effort into an outdated tablet.

If only someone could port treble then the tablet would be sorted. But I doubt that's ever going to happen.

lewmur said:
The last Samsung stock ROM for the 280 was 5.1. and there is no Linage version later than that to work from. But if you are so sure there is no difference between the 280 and 285, other than the modem, why don't you try flashing the 285 ROM on the 280? There is an Omni 6.0 ROM for the 285. I've successfully flashed 585 ROMs on a 580.
Anyway, complaining isn't going to change anything. No dev is going to put any effort into an outdated tablet.
Click to expand...
Click to collapse
Anytime I tried twrp error was just because of device name or something of that sort. Is there a way of kinda forcing the flash? I've never tried it through other way. Thanks for advice

Support of RR remix

Somebody tried reguest support of some custom rom ? I try it right now.

najjannajS650 said:
Somebody tried reguest support of some custom rom ? I try it right now.
Click to expand...
Click to collapse
Nothing will do it, first you need a working TWRP, secondly you need a dev that would do active support. Forget about it, Moto G6 (ALI) has no developers interest in this phone model.

kemoti said:
Nothing will do it, first you need a working TWRP, secondly you need a dev that would do active support. Forget about it, Moto G6 (ALI) has no developers interest in this phone model.
Click to expand...
Click to collapse
The G6 has been out since just May, what are you talking about? Most people in the Moto G series had G5S+'s where there's a **** load of development for and decided that the G6 wasn't enough of an upgrade for them to make the change, but there will always be a potential for new Devs to come to a device. I'll take this over to Android Forums for all I care and crowd source over there, there's always been a desire from up and coming Devs to work on low end phones over there, I bet anything someone will be willing to Dev on a donate device, especially a mid range.

Causical said:
The G6 has been out since just May, what are you talking about? Most people in the Moto G series had G5S+'s where there's a **** load of development for and decided that the G6 wasn't enough of an upgrade for them to make the change, but there will always be a potential for new Devs to come to a device. I'll take this over to Android Forums for all I care and crowd source over there, there's always been a desire from up and coming Devs to work on low end phones over there, I bet anything someone will be willing to Dev on a donate device, especially a mid range.
Click to expand...
Click to collapse
Treble GSI's are the future for our phone. i already had RR booting and working with the official GSI available on the project treble forums. TWRP works, it just needs some kinks worked out before the broad public uses (have to wipe data to put files on internal memory, and some people have had success with forceencrypt/dm verity disabling)

Dadud said:
Treble GSI's are the future for our phone. i already had RR booting and working with the official GSI available on the project treble forums. TWRP works, it just needs some kinks worked out before the broad public uses (have to wipe data to put files on internal memory, and some people have had success with forceencrypt/dm verity disabling)
Click to expand...
Click to collapse
Just for sake of discussion, doesn't Treble offer less feature implementation when it comes to actual device hardware to software "connectivity" [for lack of a better word] in other words little hardware side things that could be tweaked by the user with CyanogenMod builds per say?

Causical said:
Just for sake of discussion, doesn't Treble offer less feature implementation when it comes to actual device hardware to software "connectivity" [for lack of a better word] in other words little hardware side things that could be tweaked by the user with CyanogenMod builds per say?
Click to expand...
Click to collapse
im not exactly sure what you mean by that but i assume any hardware issues (i've really only noticed some bugginess with bluetooth audio) can be fixed with a custom system image based on an official GSI.

Dadud said:
im not exactly sure what you mean by that but i assume any hardware issues (i've really only noticed some bugginess with bluetooth audio) can be fixed with a custom system image based on an official GSI.
Click to expand...
Click to collapse
Yeah, right...I meant like more system side like deeply modified frameworks and stuff and things that have been modded in the system like tweaks to things like active or "live display" or whatever. Other things like how notification LED functions and tweaks to the make camera actions snappier...I know there's more...I guess a better way to describe it is things that Xposed would do, but built into a ROM. Treble isn't enabling those things is it? Since it's just a software update that's entirely parallel to a phones hardware?

Thanks, that is what I want to hear ?

Good to know some of you were able to boot GSI's already. I maintain RR for another Moto device. Once I get the bootloader unlocked, I'll work towards getting us up and running with RR

Non EMUI Rom for Mate 20 PRO

(I have no permissions for ROMs sections so posting this here)
So it looks things are slowly moving , and we are able to unlock bootloader and root our devices.
User @auras76 was kind enough to bring as the first ROM available, but I guess I am not the only one looking forward to get rid of EMUI and its poor customisation layer
I hope once firm .173 hits general release we start getting more dev interest, but the goal of this thread is to find out if any dev could be potentially interested (or already planning) to work on a non-EMUI ROM
I can imagine a bounty could be organised for users to support financially this action.
What are everyone's thoughts on this?

Doubt you will see much development of any major Rom's if there is not a free way to unlock your bootloader as there just won't be that many unlocked devices

I am fully aware of that, however let´s hope that changes if/when .171 FW is generally available and allows bootloader unlock.
I just wanted to check if there would be a way to attract some devs here, even by supporting their work (purchasing a device? 10$ per person???)

If you like custom ROMs so much buy a One Plus phone. Lots of custom ROMs and every custom ROM has bugs. There is no build of any custom ROM that doesn't have bugs and sometimes the bugs on "stable" versions of custom ROMs are so serious they impact the basic functionality of the phone.
If you think I'm exaggerating pick a custom ROM for the OP5, 5T, OP6 or 6T and look at the last several pages of user posts.
They will be users reporting bugs-often very serious ones.
If you pick an OP5 or 5T ROM many will no longer be in development. The last several pages before the ROM was abandoned will be users still reporting bugs that will never get fixed.
And that is on phones that are supposedly very development friendly.
The days of custom ROMs that improve a phone's functionality, speed and stability over the stock ROM died with Nexus phones but if you want to run a custom ROM anyway buying this phone makes pretty much no sense because Huawei is not developer friendly. They don't want owners of Huawei phones to unlock their bootloaders or run custom ROMs on Huawei devices. The same is true for Xiaomi and Samsung phones.
For that matter Google, the company behind Nexus phones which were the most developed friendly phones anyone could buy no longer wants people to use custom ROMs which is why they came up with the ROM certification program and safety net.
Apps that help phone owners bypass safety net are automatically banned from the Play Store. Whatever method Magisk uses to bypass Safety Net gets plugged by Google forcing the developer to come up with a new method that will stop working when it also gets plugged by Google.
The developer behind SuperSu said the writing was on the wall for original Android development several years ago and he knew what he was talking about.

Well, I thought XDA was exactly the place where people "like custom ROMS" and tinker with their phones.
I am coming exactly from OP phone so I know how scene works there.
OP phones are dev-friendly but not many people try different ROMs as Oxygen is probably the smoothest implementation layer of all manufacturers, so there is no need other to change other than fun.
But we are not talking about OP but Huawei here, which is the opposite case. Lousy software implementation, from battery management (see the Powergenie issues threads), to Huawei bloatware, notification handling, little customisation allowed.... So Huawei is not like OP but more like Xiaomi, heavily (not for good) customised Android version. And there might be not many OP ROMS, but check in Xiaomi land... many super stable versions that improve almost any Xiaomi device with AOSP or LOS versions.
As I said, maybe all it takes is to support a dev with a device for ROM release... I know I wouldn't be the only one looking forward to this.

Alright let's clear up what XDA is about.
It's a hub for developers. It's not a hub for people coming in with no knowledge demanding/posting hundreds of threads asking for ROMs for a device which is bootloader locked in most cases. Attitude like this steers developers away from devices because of noob communities. Look at the Samsung community on XDA.
Huwaei is still an infant when it comes to Android so they are learning the ins and outs of what works and what doesn't. Give em a break. They produce amazing devices with amazing technology. Just because it's locked doesn't mean you have to get your nickers in a twist because no one wants to develop for a new company on the Android scene. Give it some time. Maybe someone will come along and get the ball rolling for everyone and find a nice little backdoor in the bootloader and make it possible for everyone. Till then don't hold your breath and stamp your feet. Do your research before you flog out a grand on a device that might not have unofficial development for.

I really hope we can open this device up for more development, what could we do with unbridled access to the NPU, 3 rear cameras and the front 3d point cloud camera array

jhs39 said:
If you like custom ROMs so much buy a One Plus phone. Lots of custom ROMs and every custom ROM has bugs. There is no build of any custom ROM that doesn't have bugs and sometimes the bugs on "stable" versions of custom ROMs are so serious they impact the basic functionality of the phone. .
Click to expand...
Click to collapse
Had to pop in here to tell you you're completely wrong on that one.
Off the top of my head. No limits xXx for the OnePlus 5, not a single bug.
From Oreo 8.1 anyway.
A lot for devices have ROMs which surpass stock in more ways than one and have zero bugs
Further to my point and @ the OP.
The p20 pro has only seen ROMs because of the last few users / developers who have committed to Huawei/Honor devices and the fact that Honor view 10 ROMs work on the pro, in light of the changes made by Huawei IE: bootloader lock down, you will not see a lot of ROMs at all for your device in fact anyone who wants to root / flash / unlock their phones should not touch Huawei or Honor ever again, maybe (and that's a big maybe) the greedy pair of OEMs will see sense. But I doubt it.
Advice in short, dont buy their phones, I certainly won't ever again. They don't deserve it after what they've done.

Question Why no custom ROMs yet?

Hello,
I've been missing for quite a long time from XDA, but I'm about to get a new phone soon (maybe another OnePlus?) and I came here to check for new custom ROMs updates.
But it seems I cannot find any custom ROM for the OnePlus 10 Pro (yet?), why is that?
Thanks for the info.

No msm unbrick tool, no sources and so on.
Oneplus sucks every phone a little bit more! 10 pro is definitely my last OP phone

You can try GSI roms, but they're buggy (e.g. fingerprint sensor is not working)
Also you cannot unbrick your phone unless you send it to 1+ which makes development hard

Source tree is different default compilable sources.i hope someone could port it.

All of the above! Everything is different now a days with "all" OEM's, Google, Carrier's, etc.
But if some motivated Developers get the device, then who knows what mods will come our way....
Also, Magisk Modules are the modding wave !
Cheers

galaxys said:
All of the above! Everything is different now a days with "all" OEM's, Google, Carrier's, etc.
But if some motivated Developers get the device, then who knows what mods will come our way....
Also, Magisk Modules are the modding wave !
Cheers
Click to expand...
Click to collapse
What mods are you using mate?

There are already custom ROM for Xiaomi 12/Pro which also use Snapdragon 8 gen 1 so maybe there's luck but OnePlus sources are lacking and I asked Luke1337 and he is not interested in blind building since he ain't got the device.

See a my reply to other post on oneplus 10 pro

ectoplasma22 said:
There are already custom ROM for Xiaomi 12/Pro which also use Snapdragon 8 gen 1 so maybe there's luck but OnePlus sources are lacking and I asked Luke1337 and he is not interested in blind building since he ain't got the device.
Click to expand...
Click to collapse
İ can't found it .could u share for me .it has same tree our devices i could work it.

metrixx02 said:
İ can't found it .could u share for me .it has same tree our devices i could work it.
Click to expand...
Click to collapse
There's a telegram group, check the pinned posts
Xiaomi 12 | OFFICIAL
Xiaomi 12 Official Group • English only chat • Read Rules ( /rules ) • Channel : @Xiaomi12GlobalUpdates • Photography group : @Xiaomi12GlobalPhotography • Off-Topic Group : @PocoOffTopic • Customization Group : @PocophoneCustomization
t.me

I've found this: https://github.com/OnePlusOSS/android_kernel_msm-5.10_oneplus_sm8450
And this: https://github.com/OnePlusOSS/android_kernel_modules_and_devicetree_oneplus_sm8450
But, sadly, I've also read this post: https://forum.xda-developers.com/t/how-not-to-guide.4458091/post-87108519

It's truly a sad time to be an android user....
But i've got a little thought in the back of my head that i can't shake, i think things will change.
No idea how it'll happen, may take a while, maybe after the release of the T / R 10 devices.
Time will tell, but yep it's certainly a crap time for Android; when a google flagship and oneplus devices don't have a single official ROM (pixel has AOSP unofficial afaik) it's time to re-evaluate your purchases a lot more carefully.

dladz said:
It's truly a sad time to be an android user....
But i've got a little thought in the back of my head that i can't shake, i think things will change.
No idea how it'll happen, may take a while, maybe after the release of the T / R 10 devices.
Time will tell, but yep it's certainly a crap time for Android; when a google flagship and oneplus devices don't have a single official ROM (pixel has AOSP unofficial afaik) it's time to re-evaluate your purchases a lot more carefully.
Click to expand...
Click to collapse
Yeah, I remember the old times here on XDA, there was so many threads proposing many different flavors.
I used to flash and try new ROMs almost everyday...
Now I have to get a new phone, I came here to check and I've realized it all changed.
It's even hard to find ROMs for Google Pixels and OnePlus phones, I don't know what happened but it's kinda frustrating...

Guys just relax and give some time for developers.good news for sm8450 chipset is someone ported device and vendor tree for Xiaomi phones.i hope not far our phones .just relax.

metrixx02 said:
Guys just relax and give some time for developers.good news for sm8450 chipset is someone ported device and vendor tree for Xiaomi phones.i hope not far our phones .just relax.
Click to expand...
Click to collapse
Honestly mate, I've had enough phones to know that it should have happened by now.
I'm very patient, no problem in waiting, but every single OnePlus device has had several ROMs by this point bar none

metrixx02 said:
Guys just relax and give some time for developers.good news for sm8450 chipset is someone ported device and vendor tree for Xiaomi phones.i hope not far our phones .just relax.
Click to expand...
Click to collapse
Don't worry, we are just talking and comforting each other...
But well, I remember ROMs used to be posted here (almost) even before phones were available to be bought.
And since it seems that Google Pixels too lack of ROMs, I have a feelings things has changed lately somehow... but we all hope you are right man!

Why do you need google roms? are they better?
Otherwise it finds 2-3 threads about to change to global or EU version.
But that is not you want?

lorenx said:
Don't worry, we are just talking and comforting each other...
But well, I remember ROMs used to be posted here (almost) even before phones were available to be bought.
And since it seems that Google Pixels too lack of ROMs, I have a feelings things has changed lately somehow... but we all hope you are right man!
Click to expand...
Click to collapse
Google has made a lot of changes to the OS that just make everything a headache for custom ROM devs so that's not helping. The writing is on the wall for the Android ROM community and once Google finally forces hardware attestation the inability to easily hide root or unlocked bootloaders at all will kill off a lot more interest. The future of mobile phones is one of two separate walled gardens.

EtherealRemnant said:
Google has made a lot of changes to the OS that just make everything a headache for custom ROM devs so that's not helping. The writing is on the wall for the Android ROM community and once Google finally forces hardware attestation the inability to easily hide root or unlocked bootloaders at all will kill off a lot more interest. The future of mobile phones is one of two separate walled gardens.
Click to expand...
Click to collapse
The only issue is erofs partitions. Everything else can be edited to change values. Maybe devs will have to find a way to make the rw. That's the issue I see for the future. But pa said they made a build with erofs for op7 so maybe they are looking into it.

toolhas4degrees said:
The only issue is erofs partitions. Everything else can be edited to change values. Maybe devs will have to find a way to make the rw. That's the issue I see for the future. But pa said they made a build with erofs for op7 so maybe they are looking into it.
Click to expand...
Click to collapse
There's also the fact that A/B partitions lead to plenty of bricks and the devs get blamed for it plus the issues that come with AVB 2.0, manufacturers not releasing full kernel sources... It's all a circus.