Hi! This is my first post on XDA.
As a user of CM for more than a year ago on my i9300, and after enduring a lot of bugs, I wonder: What happens to CM?
It's a known fact that the Exynos platform is a headache for developers because there is no documentation or open sources from Samsung. So, things like the camera, the sound system, the HDMI output and the GPU do not work as they should.
However, here are many good developers who have fixed these bugs, or at least improve them a bit. And most of these fixes are open source and accessible by everyone on Github.
So, what is waiting CM to implement them? Giving credit to their authors, obviously.
CyanogenMod announces itself as an alternative to the stock firmware that lets you take full advantage of your smartphone, making it better and more stable. Now they are also a company: Cyanogen Inc. As a reputable brand, it should offer a higher quality firmware. ROMs like Nameless (I'm using it right now) works better even being "not official".
This is just an opinion as a user. I'm not criticizing or forcing anyone to do anything. But if there are hundreds of people using a ROM with bugs that were fixed, why not implement them? I would be the first to help, but my skills are just about webdev.
Respect and thanks for i9300 developers on XDA, and sorry about my bad English. When I use my native language I express myself MUCH better. Trust me. lol
Thanks for reading.
There's no i9300 maintainer, and they accept pull requests (on gerrit) when somebody sends them.
Also, the fact that there's no i9300 maintainer is directly connected with what you already said - lack of proper documentation. Nobody wants to fix the mess that has been created since whole this time. The amount of hacks required to make AOSP work on i9300 is too damn high. I'm slowly fixing this mess, making i9300 a bit better supported, but it's still a long way until it's done. Take a look at ArchiKernel for example, why I had to create my own kernel? Because smdk4412 sources were so much outdated that they finished around update7, right after sudden death fix. XXELLA, 4.1.2 Android times, hello. So first thing was to cleanup the kernel mess, use up-to-date samsung sources (used for stocks) and make them work with AOSP. Now, if I commit my work to CM, they'll deny this instantly because new kernel supports only i9300 and this commit would break all other exynos4 variants from compiling. Yes, together we COULD fix it, make it work with other devices. But I have better things to do than trying to fix whole exynos4 family, I focus on i9300.
This is one of the reasons why we won't see any official cm12 nightly for i9300. Because nobody is going to maintain that. Even if we can fix something, nobody is going to commit that, unless we put serious effort for making it universal across all supported devices.
That's a real shame the device is in such a mess.
Actually, to be fair, using Omnirom 4.4.4, I'm finding that the only thing that doesn't work properly is the notification led (no one seems to know why it only works 3 times out of 4).
I'll probably end up buying a new phone next year, anyway, since buy this time next year the i9300 will be almost 4 years old. In smartphone terms, that means it's getting along a bit.
(oh, and thanks for all your work on it, JustArchi!)
JustArchi said:
There's no i9300 maintainer, and they accept pull requests (on gerrit) when somebody sends them.
Also, the fact that there's no i9300 maintainer is directly connected with what you already said - lack of proper documentation. Nobody wants to fix the mess that has been created since whole this time. The amount of hacks required to make AOSP work on i9300 is too damn high. I'm slowly fixing this mess, making i9300 a bit better supported, but it's still a long way until it's done. Take a look at ArchiKernel for example, why I had to create my own kernel? Because smdk4412 sources were so much outdated that they finished around update7, right after sudden death fix. XXELLA, 4.1.2 Android times, hello. So first thing was to cleanup the kernel mess, use up-to-date samsung sources (used for stocks) and make them work with AOSP. Now, if I commit my work to CM, they'll deny this instantly because new kernel supports only i9300 and this commit would break all other exynos4 variants from compiling. Yes, together we COULD fix it, make it work with other devices. But I have better things to do than trying to fix whole exynos4 family, I focus on i9300.
This is one of the reasons why we won't see any official cm12 nightly for i9300. Because nobody is going to maintain that. Even if we can fix something, nobody is going to commit that, unless we put serious effort for making it universal across all supported devices.
Click to expand...
Click to collapse
Thanks for answering my topic. The opinion of a developer like you is very appreciated.
This situation only seems to give more reasons for not buy a Samsung phone again. This lack of support from the manufacturer is a disrespect to the user's investment. And fragmentation strikes again. Sad but true.
Thanks again for your great work of keeping this device alive for all of us.
StephenJSweeney said:
That's a real shame the device is in such a mess.
Actually, to be fair, using Omnirom 4.4.4, I'm finding that the only thing that doesn't work properly is the notification led (no one seems to know why it only works 3 times out of 4).
I'll probably end up buying a new phone next year, anyway, since buy this time next year the i9300 will be almost 4 years old. In smartphone terms, that means it's getting along a bit.
(oh, and thanks for all your work on it, JustArchi!)
Click to expand...
Click to collapse
I tried OmniROM few months ago, but it had some annoying bugs (like camera crashes) and I missed some customizations of CyanogenMod. Anyway, I'll try it again. My next buy might be a Motorola phone. The AOSP support is priceless.
ouch01 said:
I tried OmniROM few months ago, but it had some annoying bugs (like camera crashes) and I missed some customizations of CyanogenMod. Anyway, I'll try it again. My next buy might be a Motorola phone. The AOSP support is priceless.
Click to expand...
Click to collapse
I had the camera crash on CM11 M11, and switched over to Omnirom shortly after that. I'm using Google Camera with an Omnirom nightly from November, and I've never had a camera crash.
Agree with you about getting a Motorola. I'd love it if the next Moto G refresh (if there is one) came with some more RAM, increased storage (16GB instead of 8), 4G, and a multicolour led. Being able to customize the colours to suit the category of app is something I love about custom ROMs. That should be baked into Android, to be honest (but at least there's LightFlow).
JustArchi said:
There's no i9300 maintainer, and they accept pull requests (on gerrit) when somebody sends them.
Also, the fact that there's no i9300 maintainer is directly connected with what you already said - lack of proper documentation. Nobody wants to fix the mess that has been created since whole this time. The amount of hacks required to make AOSP work on i9300 is too damn high. I'm slowly fixing this mess, making i9300 a bit better supported, but it's still a long way until it's done. Take a look at ArchiKernel for example, why I had to create my own kernel? Because smdk4412 sources were so much outdated that they finished around update7, right after sudden death fix. XXELLA, 4.1.2 Android times, hello. So first thing was to cleanup the kernel mess, use up-to-date samsung sources (used for stocks) and make them work with AOSP. Now, if I commit my work to CM, they'll deny this instantly because new kernel supports only i9300 and this commit would break all other exynos4 variants from compiling. Yes, together we COULD fix it, make it work with other devices. But I have better things to do than trying to fix whole exynos4 family, I focus on i9300.
This is one of the reasons why we won't see any official cm12 nightly for i9300. Because nobody is going to maintain that. Even if we can fix something, nobody is going to commit that, unless we put serious effort for making it universal across all supported devices.
Click to expand...
Click to collapse
i feel you
SlimRoms is the answer
unlike CM, Slim has a I9300 maintainer, has support, every weekly update works properly.
Devs should really take a look at Slim's Gerrit and Freenode/#SlimDev
StephenJSweeney said:
I had the camera crash on CM11 M11, and switched over to Omnirom shortly after that. I'm using Google Camera with an Omnirom nightly from November, and I've never had a camera crash.
Agree with you about getting a Motorola. I'd love it if the next Moto G refresh (if there is one) came with some more RAM, increased storage (16GB instead of 8), 4G, and a multicolour led. Being able to customize the colours to suit the category of app is something I love about custom ROMs. That should be baked into Android, to be honest (but at least there's LightFlow).
Click to expand...
Click to collapse
The thing with Motorola is that their stock roms are basically just stock android. No laggy touchwiz skins, just a google launcher. Bloatware is at a minimum. A low spec phone like the moto G still is great because of how vanilla its experience is.
Rumours have it that the galaxy S6 international variant will have an exynos processor. I found a thread comparing the leaked info of the snapdragon 810 vs the next exynos processor and it seems that the exynos is getting a lot of popularity from users on the thread and it ain't no slouch. As it is now, phone's are so fast, that it's very hard to find a way of improving them. Like who compares app opening times nowadays? That will be much the case for 2015's flagships as well. I doubt I'd be disappointed if I had the next Samsung release if I thought I'd be in for a laggy UI, it's just whether I can tolerate the touchwiz experience or if I wanna switch to a vanilla aosp rom. That's where the problem arises.
arashvenus said:
SlimRoms is the answer
unlike CM, Slim has a I9300 maintainer, has support, every weekly update works properly.
Devs should really take a look at Slim's Gerrit and Freenode/#SlimDev
Click to expand...
Click to collapse
But only in your imagination. There is noone at slimrom. Just check their gerrit.
whatsgood said:
Rumours have it that the galaxy S6 international variant will have an exynos processor .... I found a thread comparing the leaked info of the snapdragon 810 vs the next exynos processor and it seems that the exynos is getting a lot of popularity from users on the thread and it ain't no slouch.
Click to expand...
Click to collapse
Aren't the Exynos processors the cause of much grief in the open source community, though? Aren't Qualcomm processors, such as the Snapdragon, much more popular because they're easier to work with..?
StephenJSweeney said:
Aren't the Exynos processors the cause of much grief in the open source community, though? Aren't Qualcomm processors, such as the Snapdragon, much more popular because they're easier to work with..?
Click to expand...
Click to collapse
Correct.
Eleve11 said:
Correct.
Click to expand...
Click to collapse
Well then, no more Samsung phones for me, then. Not unless they use Qualcomm..!
StephenJSweeney said:
Aren't the Exynos processors the cause of much grief in the open source community, though? Aren't Qualcomm processors, such as the Snapdragon, much more popular because they're easier to work with..?
Click to expand...
Click to collapse
Yes, that's what i thought but people are showing interests due to how powerful the processor is. I think they're saying it's more powerful than the snapdragon 810. I'm not that techy but they were mentioning that the new exynos will be smaller in size or something, whilst the snapdragon will be bigger. Apparently smaller is better, but yes the problem is open sourcing. If you want to install a stock android custom rom, it will be difficult for developers to build a rom that can push your phone to it's full potential. Snapdragon doesn't have this problem.
Basically if you love flashing different roms that are fully functional a snapdragon 810 phone is for you. If you like what Samsung offers in it's next flagship and won't be tempted to flash other roms then the exynos is for you
whatsgood said:
Yes, that's what i thought but people are showing interests due to how powerful the processor is. I think they're saying it's more powerful than the snapdragon 810. I'm not that techy but they were mentioning that the new exynos will be smaller in size or something, whilst the snapdragon will be bigger. Apparently smaller is better, but yes the problem is open sourcing. If you want to install a stock android custom rom, it will be difficult for developers to build a rom that can push your phone to it's full potential. Snapdragon doesn't have this problem.
Basically if you love flashing different roms that are fully functional a snapdragon 810 phone is for you. If you like what Samsung offers in it's next flagship and won't be tempted to flash other roms then the exynos is for you
Click to expand...
Click to collapse
I prefer to have less powerful processor, with full documentation how it works, rather than exynos and big giant hackish black box, which noone understands.
The problem is not with the exynos, but with Samsung. Judging from Exynos4, their kernel sources and own experience, exynos may look like it works, but amount of hacks and dirty workarounds to make it work, is too damn high. This could all be solved if Samsung changed their policy from "respect GPL, f*ck the rest" to "respect developers, show them that our SoC can be developer-friendly, too".
The problem is that we're not even 0.01% of Samsung sales, so why should they care. I'm not going to buy Samsung phone again, regardless if it has Snapdragon inside or not. The problem is not with the Exynos, the problem is in Samsung's policy.
JustArchi said:
I prefer to have less powerful processor, with full documentation how it works, rather than exynos and big giant hackish black box, which noone understands.
The problem is not with the exynos, but with Samsung. Judging from Exynos4, their kernel sources and own experience, exynos may look like it works, but amount of hacks and dirty workarounds to make it work, is too damn high. This could all be solved if Samsung changed their policy from "respect GPL, f*ck the rest" to "respect developers, show them that our SoC can be developer-friendly, too".
The problem is that we're not even 0.01% of Samsung sales, so why should they care. I'm not going to buy Samsung phone again, regardless if it has Snapdragon inside or not. The problem is not with the Exynos, the problem is in Samsung's policy.
Click to expand...
Click to collapse
Yeah +1 for that. My next Phone will be definitly a Sony or a One plus. I think both are the developer friendliest in android ...
what for get android with huge ram but still lag? i won't go for android for sure. just stick with ios better. with android 8gb & asop, cm etc still can't fix the bugs. android received update so slow than ios.
khanmein said:
what for get android with huge ram but still lag? i won't go for android for sure. just stick with ios better. with android 8gb & asop, cm etc still can't fix the bugs. android received update so slow than ios.
Click to expand...
Click to collapse
Yeah you are right but i think the most decent phone is the htc one......i would buy a windows phone rather than an iPhone
http://www.reddit.com/r/Android/comments/2qn8s4/new_impressive_lollipop_touchwiz_gives_nexus_line/
This is an interesting article on the new touchwiz that appears in android lollipop on the galaxy note 3. Surprisingly I can see nothing but praise from this person, apparently it seems to be running very well in comparison to touchwiz on KitKat. Is Samsung finally doing something good?
whatsgood said:
http://www.reddit.com/r/Android/comments/2qn8s4/new_impressive_lollipop_touchwiz_gives_nexus_line/
This is an interesting article on the new touchwiz that appears in android lollipop on the galaxy note 3. Surprisingly I can see nothing but praise from this person, apparently it seems to be running very well in comparison to touchwiz on KitKat. Is Samsung finally doing something good?
Click to expand...
Click to collapse
its useless even if they port it to our i9300..1gb of ram..maybe its time to upgrade to more stronger phone..
Related
Good day all
I used to have a Captivate (Galaxy SI) then the Note I. Once I purchase a device, I instantly flash a CM rom. It's been a year of suffer with the not-fully-supported Note. Frequent reboots, Bluetooth and UI glitches, heat and charging problems. It's easier to live with theses issues instead of living with TouchWiz.
Long story short, I'm planning to purchase a new device. What do you think the best high-end device (other than f#$%ing Samsung) in terms of CM support.
I know, I know that the Nexuses are best bets ! But I wanna explorer other options (screen size, SD, resolution, camera, etc) :victory:
I've seen people give appraisals on Oppo Find 5.
You precious advices and suggestions brothers.
AhmadAlmousa said:
Good day all
I used to have a Captivate (Galaxy SI) then the Note I. Once I purchase a device, I instantly flash a CM rom. It's been a year of suffer with the not-fully-supported Note. Frequent reboots, Bluetooth and UI glitches, heat and charging problems. It's easier to live with theses issues instead of living with TouchWiz.
Long story short, I'm planning to purchase a new device. What do you think the best high-end device (other than f#$%ing Samsung) in terms of CM support.
I know, I know that the Nexuses are best bets ! But I wanna explorer other options (screen size, SD, resolution, camera, etc) :victory:
I've seen people give appraisals on Oppo Find 5.
You precious advices and suggestions brothers.
Click to expand...
Click to collapse
well you can buy a nexus, some devices in sony are open sourced..or better you can buy a google play edition phone :good:
Where do you think CM would perform better... on Google Edition phones or the Open Source Sony ones.
AhmadAlmousa said:
Where do you think CM would perform better... on Google Edition phones or the Open Source Sony ones.
Click to expand...
Click to collapse
that depends on the phones spec..:good:
AhmadAlmousa said:
Where do you think CM would perform better... on Google Edition phones or the Open Source Sony ones.
Click to expand...
Click to collapse
CM is developed as free and open source software based on the official releases of Android by Google, with added original and third-party code.
in conclusion phones like Nexus will always have a CM support.
Also visit HERE to see a list of supported devices.
Gens, I fully understand your inputs. For instance, my Note, which has been receiving its share of the nightlies and RCs. So far, I'm still getting heat problems, lags, bluetooth connectivity issues, battery drains.
I'm not looking for supported device. I'm trying to find almost(fully) supported high-end device. So far, I found that my best bet could be
1-Oppo Find 5
2-Xperia Z
3-Qualacomm-based Galaxy devices ?
What do you think the best of them could be ?
AhmadAlmousa said:
Gens, I fully understand your inputs. For instance, my Note, which has been receiving its share of the nightlies and RCs. So far, I'm still getting heat problems, lags, bluetooth connectivity issues, battery drains.
I'm not looking for supported device. I'm trying to find almost(fully) supported high-end device. So far, I found that my best bet could be
1-Oppo Find 5
2-Xperia Z
3-Qualacomm-based Galaxy devices ?
What do you think the best of them could be ?
Click to expand...
Click to collapse
Oppo FFInd 5 is the one.:good:
The S Pen is one of the main the reasons for the Note Range, and I think that CM is big enough now to not only build these generic ROMs but should take some time to develop specifics, I really LOVE CM but due to the fact that the S Pen functionality is so poorly integrated (it really is) I cant use CM, and I think that CM has enough people involved in developing to take the S Pen functionality and get it into CM for the Note Range, I know it won't be easy but really, I'm sure it can be done, and would love to see it, similarly the fact that the heartrate monitor etc. is just ignored by CM is another example of where generic ROMs miss out... I know its easy to sit here and chirp but I'm so peeved myself, Having tried so many CM based ROMs for the Note 4 and just not being able to use the things (not easily anyhow) specific to the Note 4.
EDIT: Sorry think this is in the wrong section... hopefully Mod will move it appropriately.
Jostian said:
The S Pen is one of the main the reasons for the Note Range, and I think that CM is big enough now to not only build these generic ROMs but should take some time to develop specifics, I really LOVE CM but due to the fact that the S Pen functionality is so poorly integrated (it really is) I cant use CM, and I think that CM has enough people involved in developing to take the S Pen functionality and get it into CM for the Note Range, I know it won't be easy but really, I'm sure it can be done, and would love to see it, similarly the fact that the heartrate monitor etc. is just ignored by CM is another example of where generic ROMs miss out... I know its easy to sit here and chirp but I'm so peeved myself, Having tried so many CM based ROMs for the Note 4 and just not being able to use the things (not easily anyhow) specific to the Note 4.
EDIT: Sorry think this is in the wrong section... hopefully Mod will move it appropriately.
Click to expand...
Click to collapse
+1
Sent from my SM-N910F using XDA Free mobile app
+1
i always wish there would be a stock android + samsung features (multi window, camera, apps, spen)
would be much cooler than touchwiz and there is many useless stuff in tw but much missing in stock android
Gesendet von meinem SM-N910F mit Tapatalk
http://forum.xda-developers.com/showthread.php?t=3000448
Careful, you might be ridiculed for saying a 'possible negative' comment about CM... Haha. Although I personally don't think it is. Seems like a bit of a touchy subject.
It would be awesome though I agree.
+1
+10000
tusvik said:
http://forum.xda-developers.com/showthread.php?t=3000448
Click to expand...
Click to collapse
@Jostian, I think this app goes a long way towards answering your call to action.
Unfortunately I have an Exynos device so at present I can't test CM 12.
I wouldn't mind just having CM available on my variant of the Note 4 at all. Or more than 1 ROM full stop.
kopkiwi said:
I wouldn't mind just having CM available on my variant of the Note 4 at all. Or more than 1 ROM full stop.
Click to expand...
Click to collapse
Its nice to have and works great but you have to give up a lot of features including any Samsung accessories you may use and fast charging. Also while battery life is more then enough to get you through the day it's not as great as stock TW battery life.
Still the same for me I have CM also on all my android devices, but not on my note4, because I love the spend features, and I will miss this on CM, if anyone has a 3partyApp that has the same functions like the samsung spen app, please let me know.
I am about to buy this phone because it is just so damn good for it's very low price tag, however one thing is bugging me about it. I came here to find that there are no Marshmallow ROMs for it yet and the main reason for me wanting to upgrade my phone in the first place is so that I will be able to run the latest Android ROM's without performance problems. I am currently on CyanogenMod 13 on my old Samsung Galaxy S3 and I like it, but it is slow. The Redmi Note 2 doesn't even have CyanogenMod support.
Is this because Xiaomi are going to release an official MIUI based on Marshmallow? I don't want to buy this phone if it means I am going to be stuck on MIUI or on an older version of Android. I am a bit perplexed because this phone sold a lot so why hasn't anyone made Marshmallow for it yet?
Do you think that development is going to pick up for this device or is this device a bad option if you want to run the latest Google Android (not MIUI)?
Certainly, the RN2 is a lot of hardware for the money, but without source code, things are limited to either repacked/tweaked roms, or roms that are built from source, but have significant hardware functionality imperfections because source is not available. It doesn't seem clear to me whether Xiaomi will release a Marshmallow-based MIUI for the RN2 or not. Some people say yes, some people say no, so until it actually happens (if it ever does), who knows. I also bought the RN2 because it was so much hardware for the price, but I am also disappointed with the lack of CM and similar. This is certainly not for a lack of people not trying, but it seems like certain parts of the hardware will never become functional with CM unless the necessary source code is released. If you don't happen to use these parts of the hardware, well, maybe it doesn't matter. Personally, I have stuck with sMIUI because all the hardware is completely working, but I sure wish a CM version with all working hardware will eventually emerge.
verbage said:
Certainly, the RN2 is a lot of hardware for the money, but without source code, things are limited to either repacked/tweaked roms, or roms that are built from source, but have significant hardware functionality imperfections because source is not available. It doesn't seem clear to me whether Xiaomi will release a Marshmallow-based MIUI for the RN2 or not. Some people say yes, some people say no, so until it actually happens (if it ever does), who knows. I also bought the RN2 because it was so much hardware for the price, but I am also disappointed with the lack of CM and similar. This is certainly not for a lack of people not trying, but it seems like certain parts of the hardware will never become functional with CM unless the necessary source code is released. If you don't happen to use these parts of the hardware, well, maybe it doesn't matter. Personally, I have stuck with sMIUI because all the hardware is completely working, but I sure wish a CM version with all working hardware will eventually emerge.
Click to expand...
Click to collapse
Thanks for the explanation. It seems really unfortunate that they haven't released the source. I guess I should either buy the more expensive Mi4 (which I believe the source is released for) or I can just wait it out and see if the source code get's released for the RN2. It seems strange to me that they wouldn't release Marshmallow-based MIUI for such a popular, fairly new phone. I think they will release it. If they release MM-MIUI then will that enable other developers to bring stock Android Marshmallow or CyanogenMod to the RN2?
M will deffo be released for RN2. Main reason we still dont have it is:
a) first "official" device with M is supposed to be mi5
b) MTK prolly didnt polish 6.0 yet
Major companies that use X10 (eg Sony & HTC) didnt realse M for their devices either, at least as far as i know, however they are planned. So yeah M will arrive eventually, which is great, but that doesnt mean custom roms will get any better. And knowing xiaomi, and their kernel release policies, this is pretty much 100%. Pretty sure they still havent released any kernel source for their older MTK powered devices.
I think I'm going to buy the Mi4 rather because its kernel is open. I want to know that I'll be able to get android roms of any new releases. It's a real shame because the Redmi Note 2 is cheaper and a more superior device, but I have read that Mediatek are scumbags when it comes to releasing kernels because they want to force you to buy a new device when your OS becomes outdated which goes against the open source licence of Linux. Oh well, I guess that's business.
rimpy said:
If they release MM-MIUI then will that enable other developers to bring stock Android Marshmallow or CyanogenMod to the RN2?
Click to expand...
Click to collapse
If they release MM-MIUI for the RN2, unless they release the source code, this will still mean that roms are cooked/repacked, or built from source, but probably imperfectly due to lack of source. Though MIUI is based on Android, I don't think there are free and open MIUI repositories where one could grab the necessary source code for the RN2.
At this point, like everyone said, it is very unlikely that Xiaomi will ever release the source code for the RN2. Without it, custom ROMs will never be proper, and it's the reason there are no MM builds yet.
However, even though MIUI is horrible and God knows that I hate it, it's quite usable. A version of the Xposed framework that works on the latest MIUI builds has been released a couple of days ago, and with it you can get most of the functionality a custom ROM provides. It's not perfect, and I'd prefer AOSP, but it is, IMO, the best this phone has to offer at the moment.
I only got mine about three months ago, and while there were many times I came to regret my purchase, every other phone in this price range and slightly above has inferior hardware. With that said, if you want a phone running AOSP or something very close to it, you'd be better off getting a Nexus or a device that is officially supported by CM.
Thanks all. I was just about to buy the RN2 but I am glad I posted here first. I've learnt a lot and I don't think I would be happy with a phone that has a closed source kernel. The Mi4 has a smaller screen, no SD slot, slower, and costs more, but its kernel source is released and it is supported by CM13. Still very good value for money so that's gonna be my next phone.
It actually isnt slower. Benchmarks only. If you run them side by side with either MIUI or CM youll see than Mi4 is actually much faster than RN2, so yeah, its a better option if you have the money
Oneplus x is a really nice phone , i especially like its form factor which is why i brought one just today , but i read a thread where oneplus did not release MM kernel sources and this phone's production stopped. Now i am thinking about giving it back as it would be nearly impossible for future development.
What would anyone who is a present owner suggest in such a situation ? I am only getting this phone because of its 5 inch form factor and good development team.
P.s i know onyx got some top class dev's and Nougat is already on its way, i do not doubt their potential but just this phones future development progress.
Thank you.
We don't need OnePlus for further development. We are perfectly capable of keeping it up to spec. You'll be fine. Enjoy your new toy
It's a phone. You aren't buying it for its future development, you buying it for its features and the fact that they satisfy you. Don't fall in such buyer loop.
Sent from my ONE E1001
sniper20 said:
It's a phone. You aren't buying it for its future development, you buying it for its features and the fact that they satisfy you. Don't fall in such buyer loop.
Sent from my ONE E1001
Click to expand...
Click to collapse
I am a person who is easily bored out using the same rom , i like aosp but i tend to move between different roms (once a week) just because of that . The fact that this phone has CM13 , MIUI (WIP) , SAILFISH OS excited me the most. This is the only reason i look for a phone with good dev community in it which partially require OEM & Chipset supplier support to release drivers.
Of course the phone excites me but I've looped through so many phones that the phone hardware alone does not excite me anymore.
Thank you for the advise tho.
RJDTWO said:
We don't need OnePlus for further development. We are perfectly capable of keeping it up to spec. You'll be fine. Enjoy your new toy
Click to expand...
Click to collapse
thank you for the reply , but might i ask why . I always thought OEM's have to release the kernel sources or the phone will have less chance to be supported by next android version because dev's have to depend on hacks to get things working which is never ideal.
tufli said:
thank you for the reply , but might i ask why . I always thought OEM's have to release the kernel sources or the phone will have less chance to be supported by next android version because dev's have to depend on hacks to get things working which is never ideal.
Click to expand...
Click to collapse
No. Theoretically the only thing we need kernel wise is the DTS and a few drivers. We can pull the source for the 801 from Qualcomm themselves. We don't need an OEM outside of that
Is there anything that predicts developers will take more interest in the Galaxy S23 range, so we can finally have a custom ROM scene for Galaxy?
Maybe because the S23 (all devices: S23, S23 Ultra, S23 Plus) ditch Exynos in favour of a Qualcomm SM8550-AC, an S23-exclusive version of the Snapdragon 8 Gen 2
Did we need a change of wind to make things turn out differently for this device versus earlier Galaxy S ranges? I really hope it's time for renewal, as if im not wrong, the last one that had a nice ROM scene & development going on was the Galaxy S5+ which is so many years ago..
I am talking about a sizable custom ROM scene (all recent devices were dealt a bad hand, or completely lacked it) and the least that would make me very happy: the entry of LineageOS, something that's not been there for years, surely for reasons.
Due to having been away from Galaxy as a result of the lack of ROM scenes in prior devices, I am out of the loop regarding Samsung Galaxy platforms for development support, can anyone state what the main things holding it back have been in recent years? Things being locked down too much, like with other major brands? For what the main blockers are, is there reason to believe that the S23, or the move from Exynos to Qualcomm chips on the other hand, will make a difference? Because as far i know, Qualcomm is the proficient & preferred platform for most devs.
Well as much as Samsung makes everything depend on Knox not being tripped, I doubt it.
I noticed that something may be ongoing when it comes to custom ROM (LineageOS, chipset) work for Galaxy S23+, see: https://forum.xda-developers.com/t/lineageos-progress.4582781/
Development there can benefit S23 Ultra vice versa, as it's similar and also sm8550-ac, who knows if that person succeeds they'll move on to S23 Ultra afterwards. I know it's speculation, but in my book these are hopeful signs.
Rom scene has been dull on this side due to Samsung Crippling devices when rooted (Knox being permanently tripped - hence killing resale value) and Dev's losing interest in Samung. We have 2 roms and 2 devs actively supporting the development here which is nothing like the Galaxy S5 or Note 4 Days.
Aside to the above, The stock devices are so good, that there's nothing more you can achieve by rooting which can outweigh the cons of rooting.
JazonX said:
... We have 2 roms and 2 devs actively supporting the development here...
Click to expand...
Click to collapse
There exist at least 2 other very good and stable Roms with lots of mods for the Ultra.
ATN Rom and VN Rom.
just noticed this thread about gsis on the s23 range : https://forum.xda-developers.com/t/how-to-gsi-on-s23-ultra.4564249/#post-88279455 (seems to be interesting)
(also noticed a discussion on installing other gsis on the xiaomi 13 : https://forum.xda-developers.com/t/xiaomi-13-gsi.4572035 )
seems to be interesting to me ... maybe I ll buy an S23 to try (I saw a used one that was not too expensive) but maybe I am not avanced enough to succeed
pierro78 said:
seems to be interesting to me ... maybe I ll buy an S23 to try (I saw a used one that was not too expensive) but maybe I am not avanced enough to succeed
Click to expand...
Click to collapse
Nice, i was mainly interested in LineageOS/for development to get going on something like the latest Snapdragon 8 Gen 2 (sm8550) chipsets, if only we can get a flagship from today in the best possible software package which is where i won't settle for anything less than LineageOS. Not in any case, no matter how good the stock ROM is - it's about freedom, control, privacy & security - where in LOS everything is opensource and auditable (as opposed to OEM.. you don't know what may be running and how secure it is). Not to speak of even faster security patch levels than from any vendor. I also believe you won't feel the true power of your high end hardware until you're running an OS that's practically as clean as AOSP, such as LOS. It's like people dont know any better, and that raw performance (flagships..) offsets your perception anyways.
Since this topic, i've set my gaze on a new device with the same chipset (sm8550) as the Galaxy S23 range - the Motorola Edge 40 Pro, a flagship.. even if chaptsand (as per https://forum.xda-developers.com/t/lineageos-progress.4582781/) can pull it off for Galaxy, i found a way to kickstart the effort for Moto Edge 40 Pro as well, by sponsoring it and bringing a few devs together. If you're interested in that effort, read some comments before and after this one: https://forum.xda-developers.com/t/...-motorola-edge-30-dubai.4536169/post-88509185, and it still has to be moved into its own topic. But if that gets accomplished and for Galaxy it doesn't turn out well, at least ill have something to recommend to anyone that wants LineageOS on a latest tech flagship. For those that think like me, and won't ever settle for less.
mxz55 said:
Since this topic, i've set my gaze on a new device with the same chipset (sm8550) as the Galaxy S23 range - the Motorola Edge 40 Pro, a flagship.. even if chaptsand (as per https://forum.xda-developers.com/t/lineageos-progress.4582781/) can pull it off for Galaxy, i found a way to kickstart the effort for Moto Edge 40 Pro as well, by sponsoring it and bringing a few devs together. If you're interested in that effort, read some comments before and after this one: https://forum.xda-developers.com/t/...-motorola-edge-30-dubai.4536169/post-88509185, and it still has to be moved into its own topic. But if that gets accomplished and for Galaxy it doesn't turn out well, at least ill have something to recommend to anyone that wants LineageOS on a latest tech flagship. For those that think like me, and won't ever settle for less.
Click to expand...
Click to collapse
thanks ! very interesting and generous from you !!
but I must say I am more interested in a hardware with a "flater" screen than the Edge 40 Pro.
an inconvenience with the S23 is that you are losing OTA with stock rom if you root it ( https://www.xda-developers.com/how-to-unlock-bootloader-root-magisk-samsung-galaxy-s23/ )
so, unless there is some AOSP rom with updates for the S23, it seems safer to me to go for the Xiaomi 13 (after I had a look at this guide : https://forum.xda-developers.com/t/...bootloader-root-flash-twrp-flash-rom.4538433/ ) ... or maybe I ll go for the Poco F5 pro 12/256 as it should start with an early bird price of 499E tomorrow, although it s an SD 8+ gen 1 instead of an SD 8 gen 2 (oh it will be 479E with the 20E coupon on https://ams.event.mi.com/fr/poco-f5-series-product-launch ) ...
good luck !