Why are all ROMs discontinued ? - Samsung Galaxy M51 Questions & Answers

Hello,
Why are all ROMs discontinued for this device ?
Thanks

Was about to ask a similar question - or, more "constructive": Is there any ROM remaining for this device that still will receive sort of maintenance and updates?
Thanks!

kr428 said:
Was about to ask a similar question - or, more "constructive": Is there any ROM remaining for this device that still will receive sort of maintenance and updates?
Thanks!
Click to expand...
Click to collapse
Well, the answer to that question is no, that's why I asked why are all ROMs discontinued.

I wasn't sure if the answer's "no" because I'm unsure whether there might be any other ROMs than those listed in here. Hmmm, probably the usual issue of a developer giving up on the device.

because stock is fine once you debloat the phone

Related

Possible to install custom ROMs on K425 (AT&T K10)?

I've had a lot of trouble finding information on this specific model, so I'm wondering if it's possible to install a custom ROM like Cyanogenmod, for instance? I'm willing to answer questions and help out if more info is needed.
Possible maybe, available right now - no.
I don't see any development (at least here) on that model so bad news for you.
Professor Woland said:
Possible maybe, available right now - no.
I don't see any development (at least here) on that model so bad news for you.
Click to expand...
Click to collapse
I am in the process of device bring up for MS428. No ETA for Custom ROM though.

Any OFFICIAL LineageOS 14.1 users?

Long story short, I'm looking for the most stable and refined custom ROM for the MZP. I'm currently using Alberto97's AOSP 8.1 and while everything is working fine, it isn't really that refined. As it is ported from what I guess is the Google Pixel, the OS thinks that the device is a Google Pixel. For example, when I set up the device, it shows the banner "Finish setting up your Pixel". Also, when I register my fingerprint to unlock the device, the setup shows to use the index finger and touch the sensor located on the rear of the device (like the Pixel's). Charging with the phone powered off is also bugged, as it shows nothing but "Charging ??/100". I know these may seem like small things, but I'm a person with extreme attention to detail (almost borderline OCD) and things like these just bug the hell out of me, even though it isn't the devs fault at all (mad respect to Alberto).
Basically, I want a custom ROM that is MADE for the device, not ported. If you guys get what I mean. Polished is the word, I guess.
Seeing as LineageOS 14.1 is officially supported, do these cosmetic flaws exist? Can any LOS users confirm this? I apologize for bugging this sub with my stupid questions, I just want to settle with my phone once and for all.
Thank you to all for your help!
djdelarosa25 said:
Long story short, I'm looking for the most stable and refined custom ROM for the MZP. I'm currently using Alberto97's AOSP 8.1 and while everything is working fine, it isn't really that refined. As it is ported from what I guess is the Google Pixel, the OS thinks that the device is a Google Pixel. For example, when I set up the device, it shows the banner "Finish setting up your Pixel". Also, when I register my fingerprint to unlock the device, the setup shows to use the index finger and touch the sensor located on the rear of the device (like the Pixel's). Charging with the phone powered off is also bugged, as it shows nothing but "Charging ??/100". I know these may seem like small things, but I'm a person with extreme attention to detail (almost borderline OCD) and things like these just bug the hell out of me, even though it isn't the devs fault at all (mad respect to Alberto).
Basically, I want a custom ROM that is MADE for the device, not ported. If you guys get what I mean. Polished is the word, I guess.
Seeing as LineageOS 14.1 is officially supported, do these cosmetic flaws exist? Can any LOS users confirm this? I apologize for bugging this sub with my stupid questions, I just want to settle with my phone once and for all.
Thank you to all for your help!
Click to expand...
Click to collapse
Hi there,
None of the cosmetic flaws you said exist on the official LineageOS 14.1 ROM. I'm using it for several months now and it is certainly the most polished ROM created for this device.
By the way, I've tested weeks ago Alberto97's AOSP 8.1 and it was a weak experience. It wasn't optimized as I expected, some of the animations were jerky and I noticed multiple bugs.
I definitely recommend using LineageOS 14.1 ROM if you want a good experience. Also, I recommend using 7.1 ROMs instead of 8.0's/8.1's. They are way more stable and optimized.
If you have any question, feel free to ask.
Systemlessly said:
Hi there,
None of the cosmetic flaws you said exist on the official LineageOS 14.1 ROM. I'm using it for several months now and it is certainly the most polished ROM created for this device.
By the way, I've tested weeks ago Alberto97's AOSP 8.1 and it was a weak experience. It wasn't optimized as I expected, some of the animations were jerky and I noticed multiple bugs.
I definitely recommend using LineageOS 14.1 ROM if you want a good experience. Also, I recommend using 7.1 ROMs instead of 8.0's/8.1's. They are way more stable and optimized.
If you have any question, feel free to ask.
Click to expand...
Click to collapse
Sweet, thanks a lot man! I'm going to flash it right now.
Sadly, the flash failed It appears that it doesn't support the Oreo bootloader
djdelarosa25 said:
Sadly, the flash failed It appears that it doesn't the Oreo bootloader
Click to expand...
Click to collapse
What is the error?
Did you flash the official or soak test 8.0 rom before?
Systemlessly said:
What is the error?
Did you flash the official or soak test 8.0 rom before?
Click to expand...
Click to collapse
ERROR 7, my bootloader is not supported
I updated to official 8.0.0 Oreo by sideloading the OTA
djdelarosa25 said:
ERROR 7, my bootloader is not supported
I updated to official 8.0.0 Oreo by sideloading the OTA
Click to expand...
Click to collapse
Oh yeah, that's bad.
You should post a message regarding this issue on the Official Lineage 14.1 topic to make the developper aware. I think that's not hard to make the bootloader compatible, it should be some parameters to change
Systemlessly said:
Oh yeah, that's bad.
You should post a message regarding this issue on the Official Lineage 14.1 topic to make the developper aware. I think that's not hard to make the bootloader compatible, it should be some parameters to change
Click to expand...
Click to collapse
I've been trying to Google ways on how to contact the maintainer but I can't seem to find out how. Can you help me by sending a link on how to message the dev?
djdelarosa25 said:
I've been trying to Google ways on how to contact the maintainer but I can't seem to find out how. Can you help me by sending a link on how to message the dev?
Click to expand...
Click to collapse
According to this link: https://wiki.lineageos.org/devices/addison
It is said that it is mccreary the maintainer.
Here is his mail:
Sean McCreary: [email protected]
https://review.lineageos.org/#/q/owner:mccreary%40mcwest.org+status:merged
Systemlessly said:
According to this link: https://wiki.lineageos.org/devices/addison
It is said that it is mccreary the maintainer.
Here is his mail:
Sean McCreary: [email protected]
https://review.lineageos.org/#/q/owner:mccreary%40mcwest.org+status:merged
Click to expand...
Click to collapse
Holy cr*p, thanks so much, man! :laugh:
am also looking like dis , how smooth los 14.1? what is the present bug? in bootloader case, we can edit build prop instead zip folder
talktosam said:
am also looking like dis , how smooth los 14.1? what is the present bug? in bootloader case, we can edit build prop instead zip folder
Click to expand...
Click to collapse
I contacted the maintainer and he said it's not as simple as that, as there may be incompatibilities with a bootloader from a different Android version. We're messaging each other for the past few days and he sent me a test build. The flash succeeded, though we are unable to make it boot up.
djdelarosa25 said:
I contacted the maintainer and he said it's not as simple as that, as there may be incompatibilities with a bootloader from a different Android version. We're messaging each other for the past few days and he sent me a test build. The flash succeeded, though we are unable to make it boot up.
Click to expand...
Click to collapse
u ask any way to get LOS 15.1? any hope? how can i contact him?
talktosam said:
u ask any way to get LOS 15.1? any hope? how can i contact him?
Click to expand...
Click to collapse
I asked him yesterday but he said that it's against rules to ask for ETAs (even when I only asked him if it would come out, I didn't ask when :/)
Read the thread, one user already posted his email address here, though don't even try to ask him stuff like that again as surely he will link that to me.
djdelarosa25 said:
I asked him yesterday but he said that it's against rules to ask for ETAs (even when I only asked him if it would come out, I didn't ask when :/)
Read the thread, one user already posted his email address here, though don't even try to ask him stuff like that again as surely he will link that to me.
Click to expand...
Click to collapse
The dev (mccreary) just fixed the issue and official LineageOS 14.1 will now be compatible for Oreo bootloaders on the next build (May 2).
I have sideloaded the Oreo OTA on stock firmware.
Now i want to go back using LineageOS 14.1, anyway to do it?
vbdss said:
I have sideloaded the Oreo OTA on stock firmware.
Now i want to go back using LineageOS 14.1, anyway to do it?
Click to expand...
Click to collapse
Please see the post above you.
https://forum.xda-developers.com/showpost.php?p=76379057&postcount=16
---------- Post added at 07:06 PM ---------- Previous post was at 07:04 PM ----------
Happy to know that the developer fixed the issue @djdelarosa25. Well, it was a great idea to send him an e-mail.
vbdss said:
I have sideloaded the Oreo OTA on stock firmware.
Now i want to go back using LineageOS 14.1, anyway to do it?
Click to expand...
Click to collapse
Lineage 14.1 is Nougat based and it will not flash as it will display bootloader error while flashing in twrp. Wait for Lineage 15 or as djdelarosa25 said [/COLOR]
djdelarosa25 said:
The dev (mccreary) just fixed the issue and official LineageOS 14.1 will now be compatible for Oreo bootloaders on the next build (May 2).
Click to expand...
Click to collapse
wait till 2nd may
---------- Post added at 05:47 PM ---------- Previous post was at 05:32 PM ----------
djdelarosa25 said:
The dev (mccreary) just fixed the issue and official LineageOS 14.1 will now be compatible for Oreo bootloaders on the next build (May 2).
Click to expand...
Click to collapse
Is there any news for Lineage 15? I am kinda use to Oreo so I am looking for an Oreo ROM. I like AOSP no doubt but I'd also like to try a ROM that is build from scratch for MZP only.
Systemlessly said:
Happy to know that the developer fixed the issue @djdelarosa25. Well, it was a great idea to send him an e-mail.
Click to expand...
Click to collapse
Yeah, thanks for helping me, man! The dev was really cool - replies, debugs, and compiles really quickly as well. Talk about pro.
Manish355 said:
Is there any news for Lineage 15? I am kinda use to Oreo so I am looking for an Oreo ROM. I like AOSP no doubt but I'd also like to try a ROM that is build from scratch for MZP only.
Click to expand...
Click to collapse
I already asked him if it was in the works and he said don't ask for ETAs. I asked him again today and told him I wasn't asking for a date, just a confirmation if LOS 15 is in the works. We'll see what he says.
EDIT: So it counts as an ETA then. He said we'll just see it come out (so I guess it is in the works). But I wouldn't worry that much, the dev works really fast.
and yeah, I like a ROM that was made for the MZP as well. As much as I like Alberto's ROM, a ROM built from scratch > a port (though LOS 14.1 is Alberto's work as well). It's a pity he quit development of it.

what's with the lack of custom roms?

The Moto z play had plenty of developers dedicated to it but this has practically nothing. Is there a reason for that or did no developers buy this phone?
AndroidNazi said:
The Moto z play had plenty of developers dedicated to it but this has practically nothing. Is there a reason for that or did no developers buy this phone?
Click to expand...
Click to collapse
They're out there, google 'nash' roms and you should be able to find them. Some don't get posted here per XDA's request, the developer's, and/or both? Not sure what which is the case, but they're out there. I think they might be gearing more for treble and pie which isn't official on either side for us at the moment. With an official pie update in the future I'm sure some are hoping that'll fix some annoyances that have not been completely ironed out on the stock and custom side.
41rw4lk said:
They're out there, google 'nash' roms and you should be able to find them. Some don't get posted here per XDA's request, the developer's, and/or both? Not sure what which is the case, but they're out there. I think they might be gearing more for treble and pie which isn't official on either side for us at the moment. With an official pie update in the future I'm sure some are hoping that'll fix some annoyances that have not been completely ironed out on the stock and custom side.
Click to expand...
Click to collapse
If you do a google search, there is not that many for this device.. The roms that are available can be found here on XDA, (not many). Only other one I know of is Dirty Unicorn, which I have ran already for a while..
doubledragon5 said:
If you do a google search, there is not that many for this device.. The roms that are available can be found here on XDA, (not many). Only other one I know of is Dirty Unicorn, which I have ran already for a while..
Click to expand...
Click to collapse
Mokee is the only other one I could find. LOS 16 on Android file host runs really nice but it stopped getting updated around the end of September.
41rw4lk said:
They're out there, google 'nash' roms and you should be able to find them. Some don't get posted here per XDA's request, the developer's, and/or both? Not sure what which is the case, but they're out there. I think they might be gearing more for treble and pie which isn't official on either side for us at the moment. With an official pie update in the future I'm sure some are hoping that'll fix some annoyances that have not been completely ironed out on the stock and custom side.
Click to expand...
Click to collapse
Could you point me to the latest files to do trevle on Nash? I did treble on Addison so I know relatively what I need to do.
AndroidNazi said:
Could you point me to the latest files to do trevle on Nash? I did treble on Addison so I know relatively what I need to do.
Click to expand...
Click to collapse
Official LineageOS is treble enabled. Flash it, let it boot once, wipe data and flash the GSI of your choice.
Uzephi said:
Official LineageOS is treble enabled. Flash it, let it boot once, wipe data and flash the GSI of your choice.
Click to expand...
Click to collapse
Good to know, thanks.

Question When will the CUSTOM ROMS arrive?

Is there any estimate, when will the custom roms arrive?
On Monday, 4:12 AM
Real time is like 3 months ig for first stable ones.
Is this even a question? Sir, you'll need to wait for the devs to release here or go to their respective website as you probably know it and ask there on their telegram channel about your question. From there, you'll get your answer not here
Soon
i can compile TWRP for poco f3 but i don't want to use my device as guinea pig also i'm scared of bootloop also not confident enough on my skill compiling TWRP <: i guess ill wait for official twrp release for it
Jinzuken said:
Is this even a question? Sir, you'll need to wait for the devs to release here or go to their respective website as you probably know it and ask there on their telegram channel about your question. From there, you'll get your answer not here
Click to expand...
Click to collapse
This is a question because I am not asking about a particular ROM or anything. I am just asking generally that how much time is taken after the device is released to the public for the CUSTOM ROMs to come out.
Hussainbukhari said:
This is a question because I am not asking about a particular ROM or anything. I am just asking generally that how much time is taken after the device is released to the public for the CUSTOM ROMs to come out.
Click to expand...
Click to collapse
I get it your question is general, but you must ask your question to the proper ones like directly to the ROM Developer or ROM Telegram Channels, from there you'll get your answer not here. Try to look back for the devices which already available now in the market then try to research when each roms was published or announced, what is the date or months margin between the device was released/announced versus the when the specific rom was announced/released to the public. From there, you'll get your answer, I'm trying to help you dude. Sometimes, to get some answers to your question, you'll need to research it or google it. Google is available, google is waiting for you.
Sooon :
Rom: hentaiOS Dev: Dyne, camera fixed, everything else work
Jokes aside, this phone feels like a flagship killer what Oneplus should be. I'm hoping for big aftermarket community
dirtytwo said:
On Monday, 4:12 AM
Click to expand...
Click to collapse
Do you mean that hentaiOS will come two days later?
No joke, hentaiOS is coming real soon.
dirtytwo said:
No joke, hentaiOS is coming real soon.
Click to expand...
Click to collapse
Is there a device tree and vendor tree available from the Hentai OS ?
Not yet. They are right now test first custom rom with open source vendor and kernel.
most of the devices worldwide are still on lock bootloader because of the 7day xiomie restriction bleat,
I saw hentaiOS on telegram waiting for my poco f3 to unlock bootloader and flash custom roms
dirtytwo said:
Not yet. They are right now test first custom rom with open source vendor and kernel.
Click to expand...
Click to collapse
Hi do you know where I can follow the ROM development?
Ultraschorsch said:
Soon
Click to expand...
Click to collapse
RemindsMeOfCarlPei™
hentaiOS Rika Tatacaw Furry Open Pre-Release is out.
dirtytwo said:
hentaiOS Rika Tatacaw Furry Open Pre-Release is out.
Click to expand...
Click to collapse
Where can I find it?

Question [RESOLVED] Not receiving MMS on crDroid 8.2 and my LE2125 is identified as LE2123?

I've been around a while so I'm not new to Android or to tech in general but I am new to this Slot A/B stuff and also new to using Verizon 5G/LTE.
After soft-bricking my new phone by flashing TWRP and crDroid 8.2 based on Android 12, everything seems to be working well except I noticed that I'm not receiving MMS. I went to APN settings but I'm not able to edit the existing ones and if I add a new one, I can't change any settings there except the APN field. I also noticed that my build.prop identifies my phone as LE2123. I confirmed before I modified anything that I have LE2125. Any thoughts on this?
Resolution:
It looks like All LOS based roms as well as TWRP and crDroid recovery are going to show a model of LE2123. It also looks like my MMS issues were caused by YAATA. It's either not compatible with Android 12 or with 5g/VoLTE etc. I ended up restoring back to factory using MSM tools and then installed one thing at a time until I narrowed it down to YAATA. Uninstalled and problem resolved
If I'm not mistaken crDroid is
LOS based where Derpfest is AOSP based
Why would you post an issue with crDroid in a separate post instead of reporting it in the actual rom's thread?
ive had that happen on occasion. the latest bug i seem to have acquired is that during the phone connection where and when the person making the call (me) in said scenario wait's for the other party to answer does not hear anything until either some one answers or their voicemail does.
I've got the same issue with the no ringing during a call on Derpfest rom but doesn't really bother me much I've gotten used to it
Elrey567 said:
I've got the same issue with the no ringing during a call on Derpfest rom but doesn't really bother me much I've gotten used to it
Click to expand...
Click to collapse
i have noticed that whenit says LE2125, and not 2123, both issues do not exist.
oneszero said:
i have noticed that whenit says LE2125, and not 2123, both issues do not exist.
Click to expand...
Click to collapse
just now read your previous post. DERP!
djsubterrain said:
Why would you post an issue with crDroid in a separate post instead of reporting it in the actual rom's thread?
Click to expand...
Click to collapse
I actually did post in the crDroid thread and got no response so then I made a separate thread
0siribix said:
I actually did post in the crDroid thread and got no response so then I made a separate thread
Click to expand...
Click to collapse
upon further testing,it only happens after cRDroid is flashed. Think it might have to do with the boot..img? Under the Model tab, I'm curious, what Platform does your phone say your is?
oneszero said:
upon further testing,it only happens after cRDroid is flashed. Think it might have to do with the boot..img? Under the Model tab, I'm curious, what Platform does your phone say your is?
Click to expand...
Click to collapse
It says lahaina
0siribix said:
I actually did post in the crDroid thread and got no response so then I made a separate thread
Click to expand...
Click to collapse
Opening multiple threads like this won't help but make this place worse. Did you try contacting the Developer in the device group chat? The majority of the devs nowadays use Telegram groups for communication between users/devs. Also, without providing proper LOGS, don't expect any kind of support or reply from a developer. Friendly advice.
ekin_strops said:
Opening multiple threads like this won't help but make this place worse. Did you try contacting the Developer in the device group chat? The majority of the devs nowadays use Telegram groups for communication between users/devs. Also, without providing proper LOGS, don't expect any kind of support or reply from a developer. Friendly advice.
Click to expand...
Click to collapse
In my defense, I opened a single thread, not multiple. When I didn't get a response for two days in the crDroid thread, I assumed that if I was going to get any support that a dev would ask for the logs or other info they need. I mean, what's the point of going through the trouble of obtaining logcat and uploading it just to be ignored
Also, FWIW, I searched around this forum and google for a while before I started this thread precisely to avoid this situation.
Anyway from what I'm gathering, it sounds like maybe LOS 19 for this phone is not quite ready. I think I'll flash TWRP and go back to crDroid 7 for a bit. I might try one of the AOSP variants but I've always leaned toward the LOS flavors in the past
It looks like All LOS based roms as well as TWRP and crDroid recovery are going to show a model of LE2123. It also looks like my MMS issues were caused by YAATA. It's either not compatible with Android 12 or with 5g/VoLTE etc. I ended up restoring back to factory using MSM tools and then installed one thing at a time until I narrowed it down to YAATA. Uninstalled and problem resolved

Categories

Resources