Related
Or rather lack of it.
I start of by saying, i am not a dev.
But i see that the way rom's is made for Galaxy lack's most of the things that makes custom rom's good, SGS's rom's seem more themes than proper custom rom's.
I have used Nexus and some of the great rom's to that device.
The SGS way to update FW seems to stop all real development?
What do you think?
samsung's drivers are encrypted and this makes developing roms pretty difficult. there can only be roms based on samsung releases. at least this is what i understood .
i am sure that the growing user base of this great phone will bring more attention from great developers ( hi paul ! , who will be able to overcome most of the problems and give us great roms.
The final non-beta firmware from Samsung hasn't even arrived yet! Give it some time!
Custom roms now would be obsolete within one week because of a newer official beta Firmware.
I was aware that a few days ago paul obrien was having a conversation to cyanogen about creating a vendor tree for the sgs which would enable us to use cyanogen mod. If someone can confirm this with paul this would be very good news for us sgs owners.
Sent from my GT-I9000 using XDA App
Right now I'd settle for a vanilla Froyo (my last phone was the N1).
The SGS has potential, but the stock ROM is so infested with Samsung customisations (eg non- AOSP dialer, contacts, music, etc etc), why have they re-invented the wheel?? Before this phone I didn't think fragmentation existed, only "legacy". Now I know exactly what fragmentation is, and it's ugly, annoying.
The only reason I ditched the N1 is because Google have said there would be no N2 so I figured I find another phone.
Now I realise how bad fragmentation is, the iPhone really doesn't look so bad again ... (previous to the N1, I was on a iPhone 3G)
It's a pity vendors can't be mandated to supply optional vanilla ROMs - I know Samsung have released a bunch of source code, maybe that's a start.
I guess I'll give it six months. I'm an end-user who wants an easy life, but appreciates the potential and integration with google services that Android provides - moreso in its vanilla form.
Did anybody try compiling the sourcecode that was released by samsung to create a flashable working version of the manufacturer Android version that is currently running in our phones?
If that is possible, and we do have the source code from samsung, I don't see why it would be impossible to get at least a vanilla AOSP 2.1-update1 running on our galaxies.
The encrypted (or closed source drivers) can be linked as binaries to the new AOSP build running on top of Samsung's kernel (which we do have the source code to).
Side question, anybody knows how to flash the phone once you got all source code by samsung compiled ? I know we end up with a zImage, possibly a system.img.. can you create Odin files with these easily ? any thoughts?
miker71 said:
Right now I'd settle for a vanilla Froyo (my last phone was the N1).
The SGS has potential, but the stock ROM is so infested with Samsung customisations (eg non- AOSP dialer, contacts, music, etc etc), why have they re-invented the wheel?? Before this phone I didn't think fragmentation existed, only "legacy". Now I know exactly what fragmentation is, and it's ugly, annoying.
The only reason I ditched the N1 is because Google have said there would be no N2 so I figured I find another phone.
Now I realise how bad fragmentation is, the iPhone really doesn't look so bad again ... (previous to the N1, I was on a iPhone 3G)
It's a pity vendors can't be mandated to supply optional vanilla ROMs - I know Samsung have released a bunch of source code, maybe that's a start.
I guess I'll give it six months. I'm an end-user who wants an easy life, but appreciates the potential and integration with google services that Android provides - moreso in its vanilla form.
Click to expand...
Click to collapse
same here. previous n1 user, got sgs just after google announced no n2 wil be available.
just took some actions to make things smoother for me :
1. launcher pro
2. dialer one
3. handcent sms
i used them all on n1 and now i do on sgs. its all good again . still, untill froyo hits us i think i will still miss n1's speed. also, i think after froyo hits us, we will get some more roms and goodies for our phones.
what exactly is a vendor tree? and how would it be able to get around the driver issue which is apparant to the SGS?
Some info on the .rfs files that samsung uses:
http://movitool.ntd.homelinux.org/trac/movitool/wiki/RFS
Merging into AOSP
It seems like good idea to have the scripts merged into AOSP tree that support building stock ROMS for samsung galaxy s, with binary-only files being downloaded directly from the device (if I'm not mistaken, this is how one can build froyo for N1 from source now).
From someone else experience: would the patches that add vendor-specific support for SGS be accepted into AOSP tree? Are there known blockers for this?
Hmm.. rom development is quite sluggish due to the firmwares that are being released!
But i really don't care! the original rom is fine with WJG5!
I just use Launcher Pro and widgets to make it better! Speed is ok!
bratfink said:
I was aware that a few days ago paul obrien was having a conversation to cyanogen about creating a vendor tree for the sgs which would enable us to use cyanogen mod. If someone can confirm this with paul this would be very good news for us sgs owners.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
This still doesn't get around the fact that the drivers are locked down and are near impossible to implement into outside roms that aren't Samsung based. Talking isn't doing anything.
miker71 said:
Right now I'd settle for a vanilla Froyo (my last phone was the N1).
The SGS has potential, but the stock ROM is so infested with Samsung customisations (eg non- AOSP dialer, contacts, music, etc etc), why have they re-invented the wheel?? Before this phone I didn't think fragmentation existed, only "legacy". Now I know exactly what fragmentation is, and it's ugly, annoying.
Click to expand...
Click to collapse
This isn't fragmentation though, this is exactly what Google wanted Android to be - a base for phone manufacturers to lay their own tweaks on top of. HTC, Motorola, Samsung etc don't just want to be differentiated by how their handset looks, they want to put their own stuff on there too. Previously each had their own OS (Symbian, UIQ etc.) that took years of development time and was very slow moving. Google provided Android as a quick route to market for a phone, the manufacturers didn't really have to worry too much about the OS and then get lots of apps for free.
The thing is, the vanilla apps are a bit.. basic. The standard music player is fine, it works and does what it says on the tin. The standard contacts is fine again etc. Makers can ship a ROM based on vanilla Android and it would be good to go, but if they can improve upon the apps and brand it slightly more then all well and good.
But it's not fragmentation. Android is a base. A starting point. It's not meant to look exactly the same on every device, but it's meant to work exactly the same as much as possible. These manufacturers get a stable, standard, capable phone OS for free, which to them is awesome. It saves them so much time and is ultimately why eventually there will be nothing but Android on devices. It's the Mac vs PC all over again - cool but closed and restricted vs ubiquitous free-for-all.
psychoace said:
This still doesn't get around the fact that the drivers are locked down and are near impossible to implement into outside roms that aren't Samsung based. Talking isn't doing anything.
Click to expand...
Click to collapse
If the right people get onto it it's only a matter of time. The G1 camera drivers were reverse engineered for Eclair CM ROMs after HTC gave the community sod-all.
dirk1978 said:
If the right people get onto it it's only a matter of time. The G1 camera drivers were reverse engineered for Eclair CM ROMs after HTC gave the community sod-all.
Click to expand...
Click to collapse
Didn't they have the source for 1.6's camera drivers? At least then they had a base to start from. That is not true with Samsungs drivers.
A little bit OT but due to the fact that in this thread are some EX-Nexus users: Would you recommend switching to the SGS ?
dirk1978 said:
it's meant to work exactly the same as much as possible.
Click to expand...
Click to collapse
It's when it doesn't work, it's very very annoying. How long do we have to wait for the Samsung music player to enable scrobbling? Sure I can use a different app from the Market - meaning Samsung wasted effort on their own Music app, why didn't they build on the AOSP version which does support scrobbling and iSyncr, etc because they use standard API or whatever so these other programs can read the state or whatever they need to do.
Same with dialer and contacts - on Launcher Pro, pressing the default Contacts icon - won't get you anything except maybe a FC :-(
The AOSP Desk Clock - where is that? If I install a clock from Market then I have two different Alarm daemons which is a waste of everyone's time when the default Clock in AOSP Eclair is fine and - more importantly - compatible with stuff and API calls.
Then all the other stuff that may or may not be Samsung stuff - the DRM, the Device Management, the Samsung Account - given the option I just don't want that stuff.
I'm intending to flash JG5 (from factory shipped JF3) which may increase performance but presume won't make these other problems go away.
I'm really happy with the hardware - but currently I am dissatisfied with the software and "Samsung knows best". For me, personally, Google knows best (and I bet they have data on me to prove it!), so I really want to see Froyo AOSP version for the Galaxy. That day may come, or it may not ...
I know I know, "can't please all of the people all of the time"
PAO1908 said:
A little bit OT but due to the fact that in this thread are some EX-Nexus users: Would you recommend switching to the SGS ?
Click to expand...
Click to collapse
Right now the question for me would be "do I recommend switching from Samsung OS from Froyo" - my answer would be no, unless:
1. better multitouch is important to you (better for gaming, no axis mess-up)
2. 4" screen is important (I do really like the Samsung screen)
3. Better built-in audio quality is important (the Galaxy is noticeably louder than the N1 and I think it may have a better A/D sampler too)
So fully recommend switching for hardware, UNLESS you can't live without Froyo.
I can live with the SGS shortcomings. Well, for a few months anyway ... and even if AOSP never comes there are alternatives in the Market but does mean you have to ignore the Samsung stock apps depending what you want to do (which means added complexity to your life, which I don't always have time to deal with!)
psychoace said:
This still doesn't get around the fact that the drivers are locked down and are near impossible to implement into outside roms that aren't Samsung based. Talking isn't doing anything.
Click to expand...
Click to collapse
Do you have any proof that the drivers are actually locked down in any way?
I can see the source of all the modules provided by samsung, just 3 of them (pvrsrvkm, s3cbc and s3clcd) are just precompiled, and if you check the info they are GPL.
Am I missing something?
@miker71
Thanks a lot !
Ok. First I would like to say I personally do not own a Samsung galaxy s6/edge. However, I have played around with one at length at the T-Mobile store, and I can definitely say touchwiz still isn't for me. While I was there at T-Mobile I saw a nexus 6 on display and decided to take a look at it. I absolutely fell in love with it for 2 reasons. One, for the size. Two, stock android. The first one is not a deal breaker when it comes to the s6. However, I find stock android MUCH better than touchwiz. Now I understand that making an AOSP ROM for the s6 is hard because of the exynos processor and all, but I really love the physical design, camera, fingerprint sensor, and heart rate monitor. All of this being said WHEN an AOSP ROM starts to be made please contact me so I can put my input in the development for features and stuff.
Stuff that would be ABSOLUTELY necessary.
1. Fingerprint capabilities. (on lockscreen, google play account, and to open certain apps maybe??)
2. Basically stock touchwiz camera. (with double press Home button to get camera feature)
3. Integration of the heart rate sensor. (Just allow apps to use it)
4. Super Stock animations (like on the nexus)
5. A close all button for the multitasking window
Stuff that is optional
1. Certain features not present in AOSP (like keep awake while you are looking at the phone P.S. I forgot what Samsung called it)
2. Xposed Framework module "swipeback" integration (I love that feature in ios)
3. Rest is open to community suggestions. Go wild! just remember this is AOSP based and hopefully won't be too crazy. Performance
and "butter smoothness" are of the utmost importance.
Will get the s6/edge in either March or April (2015)
reyjkl said:
Ok. First I would like to say I personally do not own a Samsung galaxy s6/edge. However, I have played around with one at length at the T-Mobile store, and I can definitely say touchwiz still isn't for me. While I was there at T-Mobile I saw a nexus 6 on display and decided to take a look at it. I absolutely fell in love with it for 2 reasons. One, for the size. Two, stock android. The first one is not a deal breaker when it comes to the s6. However, I find stock android MUCH better than touchwiz. Now I understand that making an AOSP ROM for the s6 is hard because of the exynos processor and all, but I really love the physical design, camera, fingerprint sensor, and heart rate monitor. All of this being said WHEN an AOSP ROM starts to be made please contact me so I can put my input in the development for features and stuff.
Stuff that would be ABSOLUTELY necessary.
1. Fingerprint capabilities. (on lockscreen, google play account, and to open certain apps maybe??) - Not going to happen. Stock Android does not support biometric security yet and this is a secured element of the device.
2. Basically stock touchwiz camera. (with double press Home button to get camera feature) - Again, not going to happen. The TouchWiz camera is built heavily ontop of the Touchwiz framework and is almost impossible to port. An application for Xposed can enable any hardware key combo to access the cam.
3. Integration of the heart rate sensor. (Just allow apps to use it) - Unless Google Fit builds it in and the framework support is through there I dont expect this to happen.
4. Super Stock animations (like on the nexus) - ROM's can change this
5. A close all button for the multitasking window - CM and most AOSP built roms have this
Stuff that is optional
1. Certain features not present in AOSP (like keep awake while you are looking at the phone P.S. I forgot what Samsung called it) - There are apps that can enable this
2. Xposed Framework module "swipeback" integration (I love that feature in ios) - There are modules for this and apps that can help here
3. Rest is open to community suggestions. Go wild! just remember this is AOSP based and hopefully won't be too crazy. Performance and "butter smoothness" are of the utmost importance. - With the Exynos processor this may take some time since a lot of it is closed source
Will get the s6/edge in either March or April (2015)
Click to expand...
Click to collapse
I dont want to burst your bubble since you are new, but that really isnt the way to go about asking for features in ROM's and no one is going to "contact you" when something is in development.
That being said I replied to your stuff in bold in the quote. That being said I highly doubt you will be satisfied with this device based on your demands and recommend looking for a device like the One Plus One or a Nexus that has a lot of what you want.
altimax98 said:
I dont want to burst your bubble since you are new, but that really isnt the way to go about asking for features in ROM's and no one is going to "contact you" when something is in development.
That being said I replied to your stuff in bold in the quote. That being said I highly doubt you will be satisfied with this device based on your demands and recommend looking for a device like the One Plus One or a Nexus that has a lot of what you want.
Click to expand...
Click to collapse
+1
you'll have a LONG wait if you think a developer is going to contact you for input on a list of things that cant readily be included in a rom anyways..
plus, what makes you think a developer would want your input??????
The fingerprint scanner, heartrate monitor, etc.,. (samsung specific features/capabilities) can't be supported with AOSP ROMs.
Sorry.
altimax98 said:
I dont want to burst your bubble since you are new, but that really isnt the way to go about asking for features in ROM's and no one is going to "contact you" when something is in development.
That being said I replied to your stuff in bold in the quote. That being said I highly doubt you will be satisfied with this device based on your demands and recommend looking for a device like the One Plus One or a Nexus that has a lot of what you want.
Click to expand...
Click to collapse
1. I do realize a lot of this stuff is not possible and might take a LONG time to develop.
2. You don't have to burst my bubble, I know it's unlikely. However, I was just feeling creative and wanted to put out my wishlist if all of this were possible
3. When I say AOSP, I really mean AOSP based. I thought incorporating the fingerprint sensor would be fairly easy? just create a few API's with Kernel??
4. I have no idea why I said "contact me" I must've been on something lol.
Thanks for the reply btw. Also too, I love the nexus 6 and I would take it over the one plus one any day. However, I will still give into the s6 cuz of da fingerprint and better processor.
Considering most of the things you are asking for will never happen, it is not matter of the "lenght'. i.e: the camera...this request been in demand since the gs3 (my first android device) I doubt it is going to change anytime soon.
Finger print for touchwiz is the same as camera for touchwiz...
Great way to provide inputs to by giving a "how" on how to do things for what you are requesting. Can always start a "how" in the development section for group projects when it become available for the s6.
reyjkl said:
just create a few API's with Kernel??
Click to expand...
Click to collapse
Dude you gotta get these ideas out there... PM all the recognized devs on xda fast. This is way bigger than just the S6
incuvolta said:
Dude you gotta get these ideas out there... PM all the recognized devs on xda fast. This is way bigger than just the S6
Click to expand...
Click to collapse
I'm guessing this is sarcasm but I usually can't get the sarcasm straight from context. Is it?
Yes Sheldon. It is sarcasm.
Hello Guys, Good Day
i have been using samsung mobiles from past 6 years, this time i switched to oneplus 3T but i didnt like the user interface it comes with. For Eg: while making a call In samsung could just swipe right on a contact to place a call and swipe left to compose msg....even creating contacts were easy. Likewise there are lot many other functionalities that i liked in samsung compared to 3T.....the only reason i opted for 3T was its hardware...... My question is, Is it possible to have the same functionality or user interface on 3T as well.
would really appreciate your views and replies
Kind Regards
The interface and functionality in OP3T is almost the same as stock Android with a few little tweaks here and there. So, if you like Samsung's iteration on Android, just get the Galaxy S series.
I didn't think I'd ever see someone saying they like Samsungs TouchWiz over Stock Android. Welp, to each their own. I respect your preference.
But unfortunately, It's not possible to get the Samsung UI i.e. TouchWiz without porting it to the 3T and i dont think anyone has attempted porting the same just yet, and i highly doubt someone ever will.
Wait and hope someone does port it and if that doesn't happen, you'll get used to OxygenOS soon enough!
Don't feel bad. Many long time Samsung users get used to features that many Android "puriest" never heard about. The one you mention is one I also liked when I had the s1.
To answer you. No. Touch wiz is not something you can get. But. You maybe able to use some separate apps to come close.
Stock Android is kinda bland compared to some of the other UI out there. Just need to find things that will work for you the way you want.
You can consider using third party apps to get some of the similar functionalities. For a swipe to call feature I use ExDialer and it's a fantastic dialer app. On OP3T having 6GB helps helps the cause of using 3rd party apps without feeling the pinch. Gluck with tweaking the phone to your liking.
(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.
Hello,
Without any doubt I can say that XZ Premium was my favorite phone, many mods, ports and ROMS. Changed it to OP 7Pro and Im also satisfied with XDA support but it wasnt enough so...
I bought XZ3 Dual 4/64 with A10 and 52.1.A.3.137 firmware. Read all possible topics here and Im totally confused what to do, could you help me out?
I dont really know should I unlock bootloader because I would like to have Sony Camera functions like 4K HDR etc.... but
I cant stand button navigation on stock, I would love to have gestures.
I dont need Sony audio enhancement because I mostly use V4A, what forces me to unlock BL and keep root.
I thought about SailfishOS but I need few android apps like messaging or banking app, cant live without it.
Thought about LineageOS but there are problems with crackling speaker, camera app, gcam not working, and I like sony stock apps but I dont mind using google apps instead, not a fan of lineage apps. Present magisk/hide is apprecatied.
Not a fan of A12- read that camera app is not working with a12, never flashed nor used A12.
No matter what I choose- there are downsides, so what will be the best choice?
Totally sad that XZ3 is not as supported as XZP, I would love to support XZ3 development but Im so underdeveloped that I only use whats given on xda ((
Have a great day!
Hello,
I'm at the same point as you. I'm a previous user of LineageOS on a Galaxy S7. That one had a lot of flaws but was still much, much better than anything that forces gapps on me, even though maybe the S7 version was the worst LineageOS ever. I also used it on S5 and S3. No LineageOS was perfect, but superior over all other ROMs I tried.
The thing that bothers me about the camera is: I can't find information about where the issue is after unlocking. People say it performs worse. But is it a driver thing you can't fix or is it just the Sony camera app? I get no answer here. If it's just the Sony camera app that is decapitated after unlocking, you should just get rid of this peace of crap and replace it with Open Camera. You can then switch to Camera 2 API and disable this awful edge enhancement and actually make good photos. The only downside is that Open Camera doesn't apply proper shutter time for very dark conditions automatically. 4k HDR also seems to work. But remember: I'm still on the original ROM and I don't know if anything will be different after unlocking. I would be thankful if someone could give any information about it.
You should be able to use almost any app on LineageOS. I use FDroid and Aurora as app managers. Some apps check for root or custom ROMs and refuse to work if they find it. I don't use any banking apps on Android. Maybe they do a root check. I can't tell you. You may use the web page of your bank instead. Telegram and Signal both work on LineageOS, I've never tried WhatsApp though.
What's the best option isn't an easy decision for the XZ3. There are always downsides on custom ROMs. The problem is that we can find almost no information on what exactly doesn't work as usual after unlocking, so we can't make our decision. I don't expect to find much help, if I encounter problems after unlocking.
I also spend hours and days trying to get information about all of this and didn't find what I need to know. The crackling speakers problem on LineageOS for example is new to me. Can you give me further information about it or provide a link? Have made any progress since your post here?