Related
Or rather lack of it.
I start of by saying, i am not a dev.
But i see that the way rom's is made for Galaxy lack's most of the things that makes custom rom's good, SGS's rom's seem more themes than proper custom rom's.
I have used Nexus and some of the great rom's to that device.
The SGS way to update FW seems to stop all real development?
What do you think?
samsung's drivers are encrypted and this makes developing roms pretty difficult. there can only be roms based on samsung releases. at least this is what i understood .
i am sure that the growing user base of this great phone will bring more attention from great developers ( hi paul ! , who will be able to overcome most of the problems and give us great roms.
The final non-beta firmware from Samsung hasn't even arrived yet! Give it some time!
Custom roms now would be obsolete within one week because of a newer official beta Firmware.
I was aware that a few days ago paul obrien was having a conversation to cyanogen about creating a vendor tree for the sgs which would enable us to use cyanogen mod. If someone can confirm this with paul this would be very good news for us sgs owners.
Sent from my GT-I9000 using XDA App
Right now I'd settle for a vanilla Froyo (my last phone was the N1).
The SGS has potential, but the stock ROM is so infested with Samsung customisations (eg non- AOSP dialer, contacts, music, etc etc), why have they re-invented the wheel?? Before this phone I didn't think fragmentation existed, only "legacy". Now I know exactly what fragmentation is, and it's ugly, annoying.
The only reason I ditched the N1 is because Google have said there would be no N2 so I figured I find another phone.
Now I realise how bad fragmentation is, the iPhone really doesn't look so bad again ... (previous to the N1, I was on a iPhone 3G)
It's a pity vendors can't be mandated to supply optional vanilla ROMs - I know Samsung have released a bunch of source code, maybe that's a start.
I guess I'll give it six months. I'm an end-user who wants an easy life, but appreciates the potential and integration with google services that Android provides - moreso in its vanilla form.
Did anybody try compiling the sourcecode that was released by samsung to create a flashable working version of the manufacturer Android version that is currently running in our phones?
If that is possible, and we do have the source code from samsung, I don't see why it would be impossible to get at least a vanilla AOSP 2.1-update1 running on our galaxies.
The encrypted (or closed source drivers) can be linked as binaries to the new AOSP build running on top of Samsung's kernel (which we do have the source code to).
Side question, anybody knows how to flash the phone once you got all source code by samsung compiled ? I know we end up with a zImage, possibly a system.img.. can you create Odin files with these easily ? any thoughts?
miker71 said:
Right now I'd settle for a vanilla Froyo (my last phone was the N1).
The SGS has potential, but the stock ROM is so infested with Samsung customisations (eg non- AOSP dialer, contacts, music, etc etc), why have they re-invented the wheel?? Before this phone I didn't think fragmentation existed, only "legacy". Now I know exactly what fragmentation is, and it's ugly, annoying.
The only reason I ditched the N1 is because Google have said there would be no N2 so I figured I find another phone.
Now I realise how bad fragmentation is, the iPhone really doesn't look so bad again ... (previous to the N1, I was on a iPhone 3G)
It's a pity vendors can't be mandated to supply optional vanilla ROMs - I know Samsung have released a bunch of source code, maybe that's a start.
I guess I'll give it six months. I'm an end-user who wants an easy life, but appreciates the potential and integration with google services that Android provides - moreso in its vanilla form.
Click to expand...
Click to collapse
same here. previous n1 user, got sgs just after google announced no n2 wil be available.
just took some actions to make things smoother for me :
1. launcher pro
2. dialer one
3. handcent sms
i used them all on n1 and now i do on sgs. its all good again . still, untill froyo hits us i think i will still miss n1's speed. also, i think after froyo hits us, we will get some more roms and goodies for our phones.
what exactly is a vendor tree? and how would it be able to get around the driver issue which is apparant to the SGS?
Some info on the .rfs files that samsung uses:
http://movitool.ntd.homelinux.org/trac/movitool/wiki/RFS
Merging into AOSP
It seems like good idea to have the scripts merged into AOSP tree that support building stock ROMS for samsung galaxy s, with binary-only files being downloaded directly from the device (if I'm not mistaken, this is how one can build froyo for N1 from source now).
From someone else experience: would the patches that add vendor-specific support for SGS be accepted into AOSP tree? Are there known blockers for this?
Hmm.. rom development is quite sluggish due to the firmwares that are being released!
But i really don't care! the original rom is fine with WJG5!
I just use Launcher Pro and widgets to make it better! Speed is ok!
bratfink said:
I was aware that a few days ago paul obrien was having a conversation to cyanogen about creating a vendor tree for the sgs which would enable us to use cyanogen mod. If someone can confirm this with paul this would be very good news for us sgs owners.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
This still doesn't get around the fact that the drivers are locked down and are near impossible to implement into outside roms that aren't Samsung based. Talking isn't doing anything.
miker71 said:
Right now I'd settle for a vanilla Froyo (my last phone was the N1).
The SGS has potential, but the stock ROM is so infested with Samsung customisations (eg non- AOSP dialer, contacts, music, etc etc), why have they re-invented the wheel?? Before this phone I didn't think fragmentation existed, only "legacy". Now I know exactly what fragmentation is, and it's ugly, annoying.
Click to expand...
Click to collapse
This isn't fragmentation though, this is exactly what Google wanted Android to be - a base for phone manufacturers to lay their own tweaks on top of. HTC, Motorola, Samsung etc don't just want to be differentiated by how their handset looks, they want to put their own stuff on there too. Previously each had their own OS (Symbian, UIQ etc.) that took years of development time and was very slow moving. Google provided Android as a quick route to market for a phone, the manufacturers didn't really have to worry too much about the OS and then get lots of apps for free.
The thing is, the vanilla apps are a bit.. basic. The standard music player is fine, it works and does what it says on the tin. The standard contacts is fine again etc. Makers can ship a ROM based on vanilla Android and it would be good to go, but if they can improve upon the apps and brand it slightly more then all well and good.
But it's not fragmentation. Android is a base. A starting point. It's not meant to look exactly the same on every device, but it's meant to work exactly the same as much as possible. These manufacturers get a stable, standard, capable phone OS for free, which to them is awesome. It saves them so much time and is ultimately why eventually there will be nothing but Android on devices. It's the Mac vs PC all over again - cool but closed and restricted vs ubiquitous free-for-all.
psychoace said:
This still doesn't get around the fact that the drivers are locked down and are near impossible to implement into outside roms that aren't Samsung based. Talking isn't doing anything.
Click to expand...
Click to collapse
If the right people get onto it it's only a matter of time. The G1 camera drivers were reverse engineered for Eclair CM ROMs after HTC gave the community sod-all.
dirk1978 said:
If the right people get onto it it's only a matter of time. The G1 camera drivers were reverse engineered for Eclair CM ROMs after HTC gave the community sod-all.
Click to expand...
Click to collapse
Didn't they have the source for 1.6's camera drivers? At least then they had a base to start from. That is not true with Samsungs drivers.
A little bit OT but due to the fact that in this thread are some EX-Nexus users: Would you recommend switching to the SGS ?
dirk1978 said:
it's meant to work exactly the same as much as possible.
Click to expand...
Click to collapse
It's when it doesn't work, it's very very annoying. How long do we have to wait for the Samsung music player to enable scrobbling? Sure I can use a different app from the Market - meaning Samsung wasted effort on their own Music app, why didn't they build on the AOSP version which does support scrobbling and iSyncr, etc because they use standard API or whatever so these other programs can read the state or whatever they need to do.
Same with dialer and contacts - on Launcher Pro, pressing the default Contacts icon - won't get you anything except maybe a FC :-(
The AOSP Desk Clock - where is that? If I install a clock from Market then I have two different Alarm daemons which is a waste of everyone's time when the default Clock in AOSP Eclair is fine and - more importantly - compatible with stuff and API calls.
Then all the other stuff that may or may not be Samsung stuff - the DRM, the Device Management, the Samsung Account - given the option I just don't want that stuff.
I'm intending to flash JG5 (from factory shipped JF3) which may increase performance but presume won't make these other problems go away.
I'm really happy with the hardware - but currently I am dissatisfied with the software and "Samsung knows best". For me, personally, Google knows best (and I bet they have data on me to prove it!), so I really want to see Froyo AOSP version for the Galaxy. That day may come, or it may not ...
I know I know, "can't please all of the people all of the time"
PAO1908 said:
A little bit OT but due to the fact that in this thread are some EX-Nexus users: Would you recommend switching to the SGS ?
Click to expand...
Click to collapse
Right now the question for me would be "do I recommend switching from Samsung OS from Froyo" - my answer would be no, unless:
1. better multitouch is important to you (better for gaming, no axis mess-up)
2. 4" screen is important (I do really like the Samsung screen)
3. Better built-in audio quality is important (the Galaxy is noticeably louder than the N1 and I think it may have a better A/D sampler too)
So fully recommend switching for hardware, UNLESS you can't live without Froyo.
I can live with the SGS shortcomings. Well, for a few months anyway ... and even if AOSP never comes there are alternatives in the Market but does mean you have to ignore the Samsung stock apps depending what you want to do (which means added complexity to your life, which I don't always have time to deal with!)
psychoace said:
This still doesn't get around the fact that the drivers are locked down and are near impossible to implement into outside roms that aren't Samsung based. Talking isn't doing anything.
Click to expand...
Click to collapse
Do you have any proof that the drivers are actually locked down in any way?
I can see the source of all the modules provided by samsung, just 3 of them (pvrsrvkm, s3cbc and s3clcd) are just precompiled, and if you check the info they are GPL.
Am I missing something?
@miker71
Thanks a lot !
Hey guys,
what do you think, is it possible to port the Android 2.3 Gingerbread from Nexus S to our Samsung Galaxy S. Because it has a similar hardware!
/Discuss
You're fast , just wanted to ask this. Hope some legend dude will do this.
Theoretically it should be very simple to port the software. The only difference I can see from a hardware perspective is the NFC chip which simply needs to be disabled in software, and the missing search button which will need to be mapped to a menu long-press.
I did some work on the NITDroid project back when I had an N900, and neither of these is particularly difficult to do.
For nexus S info:
http://googleblog.blogspot.com/2010/12/introducing-nexus-s-with-gingerbread.html
http://www.google.com/nexus/#!/tech-specs
http://www.google.com/phone/compare/?phone=nexus-s&phone=samsung-galaxy-s
will the iNAND be a problem?
Supercurio says the devices use different types of memory.
Might be a bit of a problem
i can't see any reason we will have issues bringing it to the galaxy s line, especially if its the same SoC... and hardware, gps might be different, but thats a huge bonus anyways
Arkanius said:
Supercurio says the devices use different types of memory.
Might be a bit of a problem
Click to expand...
Click to collapse
yea the Nexus use the 16gb iNAND...
Since Samsung closely helped Google at making the hardware, hopefully we might have a quick 2.3 Samsung version for our devices
Which will then be easier to bring down to stock with the Cyanogen team progress
It must be far easier than a sense port or even cyanogen port.
Sent from my GT-I9000 using XDA App
One thing that also caught my eye was, that the video recording isn't HD... probably to not throw away boatloads of RAM for the camera...
Arkanius said:
Since Samsung closely helped Google at making the hardware, hopefully we might have a quick 2.3 Samsung version for our devices
Which will then be easier to bring down to stock with the Cyanogen team progress
Click to expand...
Click to collapse
I wouldn't bet on that. If Sammy released 2.3 in short order for the SGS it would cannibalize Nexus S sales. The aftermarket community is still the best bet.
binary110 said:
i can't see any reason we will have issues bringing it to the galaxy s line, especially if its the same SoC... and hardware, gps might be different, but thats a huge bonus anyways
Click to expand...
Click to collapse
GPS is the same! Both using A-GPS Chips. The NFC Software must be Disabled, Bluethooth Updated to 3.0, Nexus S has only 2.1 and Video Recording Updated to 1280x720, Nexus S had 720x480
Arkanius said:
Supercurio says the devices use different types of memory.
Might be a bit of a problem
Click to expand...
Click to collapse
Thats the biggest problem, I think. SuperCurios Tweet to iNand Tweet
Leandros
This a premature thread. Once a dump or aosp is released only then can we begin to do something about it. Till then this is a discussion thread and not related to development. IMHO
What about rfs? Im sure google is not using it. We will have to work that out as well.
2.3 SDK is out so I see no problem in getting gingerbread.
Whether as a port from the NS or a homebrew I don't really care.
All I want is the integrated SIP client. Been missing this since switching from my Nokia e90 Communicator to Android 1 year ago.
I am interested how the nexus S fares against a hacked Galaxy S, don't think it will be any faster!
Mycorrhiza said:
2.3 SDK is out so I see no problem in getting gingerbread.
Whether as a port from the NS or a homebrew I don't really care.
All I want is the integrated SIP client. Been missing this since switching from my Nokia e90 Communicator to Android 1 year ago.
I am interested how the nexus S fares against a hacked Galaxy S, don't think it will be any faster!
Click to expand...
Click to collapse
Everything is virtually the same.
I call up one the powers of the all powerful XDA to port the N:S for all the SGS's that are out there, so we can forget about samsung roms and use a normal google one
The Nexus S doesn't seem to support an external sd card. Likely another problem?
bigriot said:
The Nexus S doesn't seem to support an external sd card. Likely another problem?
Click to expand...
Click to collapse
Maybe... but I can live without an external SDCARD for now...
Just read the news about these two getting the update that fixes the SMS bug but no mention of any other 2.2.x O/S'd phones getting it. Can't be far off surely?
http://phandroid.com/
I just want that SMS fix, I've seen two I9000Ms do it. I pinged Samsung Canada on Twitter, we'll see what their response is.
v.2.3 2012
v2.4 2022
v3.0 2050
maybe
My20 said:
v.2.3 2012
v2.4 2022
v3.0 2050
maybe
Click to expand...
Click to collapse
maybe ayes maybe naws
My20 said:
v.2.3 2012
v2.4 2022
v3.0 2050
(American variant releases not guaranteed)
Click to expand...
Click to collapse
Fixed that for you.
i somewhere read that we can expect 2.3 for SGS for the end for the first quarter of the year...but are you people using stock ROMS ? i think Darky's ROM is working on a multi-device able to detect and flash devices accordingly, shouldn't that fix your sms problems ?
ps: i have the i9000, but what is "the sms problem", i don't think i have it..
Everybody bug samsung to skip 2.3 and prep for 3.0.
With carriers charging 15-20¢/SMS and having a free replacement (google voice, google talk, emails)
I really couldn't care less about SMS. I should even remove the SMS app from my phone.
Why do y'all want honeycomb (3.0), it's for tablet, not SmartPhones :|
t1mman said:
Why do y'all want honeycomb (3.0), it's for tablet, not SmartPhones :|
Click to expand...
Click to collapse
It's for both.
t1mman said:
Why do y'all want honeycomb (3.0), it's for tablet, not SmartPhones :|
Click to expand...
Click to collapse
So wrong, it hurts.
rumor
the rumor is here :
i like the way they say
"site called SamFirmwares – one we’ve never heard of before."
Click to expand...
Click to collapse
they better all listen to these site ! i wonder how these big companies would react to
all the amazing roms out there !
JCopernicus said:
So wrong, it hurts.
Click to expand...
Click to collapse
Is it? Then prove me wrong...
From google:
Honeycomb is the next version of the Android platform, designed from the ground up for devices with larger screen sizes, particularly tablets.
Click to expand...
Click to collapse
http://googlemobile.blogspot.com/2011/01/sneak-peak-of-android-30-honeycomb.html
That's the reason Google is naming "honeycomb" 3.0, and later Tablet optimisez releases will be 3.x where smartphone will stay on 2.x
Before saying crap at one another, do some research...
t1mman said:
Is it? Then prove me wrong...
From google:
http://googlemobile.blogspot.com/2011/01/sneak-peak-of-android-30-honeycomb.html
That's the reason Google is naming "honeycomb" 3.0, and later Tablet optimisez releases will be 3.x where smartphone will stay on 2.x
Before saying crap at one another, do some research...
Click to expand...
Click to collapse
It's literally hurting my brain that you think that. Check back after 3.0 line is cut and put up on AOSP, you'll see all the honeycomb roms(for phones) floating around.
JCopernicus said:
It's literally hurting my brain that you think that. Check back after 3.0 line is cut and put up on AOSP, you'll see all the honeycomb roms(for phones) floating around.
Click to expand...
Click to collapse
You can get rom floating around of about anything, doesn't mean it's made for it... You can even get a whole Linux distrubution working on SGS, still it's not "official" or optimised...
Still, nothing will be official and Honeycomb is still optimised for Tablet. I don't know why your "brain hurts", but when google sais their thing is optimised for something, since they made the thing, you'd better beleive them!
hell, you can put a Corvette engine in a Civic, still it's not meant or optimised for.
t1mman said:
You can get rom floating around of about anything, doesn't mean it's made for it... You can even get a whole Linux distrubution working on SGS, still it's not "official" or optimised...
Still, nothing will be official and Honeycomb is still optimised for Tablet. I don't know why your "brain hurts", but when google sais their thing is optimised for something, since they made the thing, you'd better beleive them!
hell, you can put a Corvette engine in a Civic, still it's not meant or optimised for.
Click to expand...
Click to collapse
http://developer.android.com/sdk/android-3.0-highlights.html
Honeycomb adds "tablet" (ie big screen) specific support. It's not an independent branch, feature sets will trickle down accordingly to phones, they will both be 3.0.
P.S. A rom built from AOSP is as official as you can get in regards to Android.
JCopernicus said:
http://developer.android.com/sdk/android-3.0-highlights.html
Honeycomb adds "tablet" (ie big screen) specific support. It's not an independent branch, feature sets will trickle down accordingly to phones, they will both be 3.0.
P.S. A rom built from AOSP is as official as you can get in regards to Android.
Click to expand...
Click to collapse
You can't read title can't you?
"New UI designed from the ground up for tablets"
The reason it's (honeycomb) taking another number (3.0) instead of following the same (2.x) is because it's for tablets...
as far as AOSP vs. Official, their's a huge difference between official source code (from google) vs official rom (from samsung).
I can't tell the future, but I can most certainly say that Kies would offer 2.4 hell before 3.0 for our devices (which are smartphones, not tablet).
t1mman said:
You can't read title can't you?
"New UI designed from the ground up for tablets"
The reason it's (honeycomb) taking another number (3.0) instead of following the same (2.x) is because it's for tablets...
as far as AOSP vs. Official, their's a huge difference between official source code (from google) vs official rom (from samsung).
I can't tell the future, but I can most certainly say that Kies would offer 2.4 hell before 3.0 for our devices (which are smartphones, not tablet).
Click to expand...
Click to collapse
The large screen views (which never existed) are built from the "ground up" because, guess what? They never existed in the first place.
The reason it's taking 3.0 is because it's a huge jump in feature set, and qualifies as a version realease and not just a point release.
If a device has a certain feature it can access certain API from the android OS. If a device doesn't, then it can't. It's that simple.
"tablets" have the big screen feature and they can access the nested view API's. You don't know how android works. there is ONE line, which sits at 2.3.2, and it's device independent.
Just like the Nexus S can access the NFC api's because it has an NFC chip.
AOSP is the code that google/samsung/moto/acer/etc pull from, and build more on top.
Cyanogen roms are on par and equivalent(better actually) as google's roms, you can't get more "official" than AOSP. MFG roms are actually less true to AOSP as they are modified. You probably won't see 3.0 on the current galaxy line at all, but that has nothing to do whether it works on there or not.
Chill out dude! Take a deep breath....
This is getting nowhere, running in circle...
I'm pretty sure we won't see Honeycomb as a release by the makers (Samsungs, Motorola, LG, HTC, name em) on any smartphone. Don't know why this is such a big deal for you and what you don't get on the whole deal but if you want,
You can bookmark this thread and if you see an official honecomb as an official release by samsung or LG or HTC or google on a Smartphone, revive it from the archives and rub it on my face, I'll gladly take the fall...
Chill out? I think I'm just typing normally on a keyboard? Maybe I'm smashing keys, and don't recognize it?
You don't understand how android works if you think it won't appear on phones, we're not going around in circles. You're just wrong.
Hey, i was just wondering why hasnt there been any stock android roms for the note 8 yet? I saw the s9 getting a resurrection remix. Is there any technical limitations thats holding back the development or do people just not care?
Because this phone has a pen ana that pen won't work without source code from Samfail
silveraero said:
Because this phone has a pen ana that pen won't work without source code from Samfail
Click to expand...
Click to collapse
Stock Android - and especically things like RR actually have pretty solid stylus support. And there's plenty of apps that add features like pen-gestures and replicate the proprietary Samsung stuff.
The problem is likely more to do with the lack of treble support that the S9 has - which drastically simplifies the issue of dealing with proprietary firmware and API's.
And the fact that a large portion of Note 8 users have models with locked bootloaders, which prevent the usage of non-Samsung ROMS. There have been several threads detailing attempts at making AOSP or similar ROM's, but all have fallen silent without much to show in the way of progress:
https://forum.xda-developers.com/galaxy-note-8/how-to/unofficial-lineageos-t3686026
https://forum.xda-developers.com/galaxy-note-8/how-to/bounty-aosp-roms-note8-t3686083
https://forum.xda-developers.com/galaxy-note-8/how-to/resurrection-remix-official-note-8-t3756351
Decoding and dealing with proprietary API's and firmware takes a lot of time and luck without sources which Samsung refuse to provide. And the pool of developers that seem interested in such a huge effort for the Note 8 seems to be shrinking.
Aaren11 said:
Stock Android - and especically things like RR actually have pretty solid stylus support. And there's plenty of apps that add features like pen-gestures and replicate the proprietary Samsung stuff.
The problem is likely more to do with the lack of treble support that the S9 has - which drastically simplifies the issue of dealing with proprietary firmware and API's.
And the fact that a large portion of Note 8 users have models with locked bootloaders, which prevent the usage of non-Samsung ROMS. There have been several threads detailing attempts at making AOSP or similar ROM's, but all have fallen silent without much to show in the way of progress:
https://forum.xda-developers.com/galaxy-note-8/how-to/unofficial-lineageos-t3686026
https://forum.xda-developers.com/galaxy-note-8/how-to/bounty-aosp-roms-note8-t3686083
https://forum.xda-developers.com/galaxy-note-8/how-to/resurrection-remix-official-note-8-t3756351
Decoding and dealing with proprietary API's and firmware takes a lot of time and luck without sources which Samsung refuse to provide. And the pool of developers that seem interested in such a huge effort for the Note 8 seems to be shrinking.
Click to expand...
Click to collapse
SO basically no hope for the future? this thing wouldve been a beast with an aosp rom. Thats really dissapointing i was looking forward to android p (
2000ftt said:
SO basically no hope for the future? this thing wouldve been a beast with an aosp rom. Thats really dissapointing i was looking forward to android p (
Click to expand...
Click to collapse
I wouldn't say the situation is hopeless. Just pretty silent at the moment. Some of the groundwork seems to have been done particularly by @SaschaNes and the teams they're a part of. But they've been silent on actual progress of bootable builds for several months now. No clue if they're still working at it or not.
I would say AOSP or Lineage for the Note 8 is achievable it would just take reasons for developers to dedicate their time and effort. And currently, there aren't many for most. Few dev's actually have the device, and even fewer are interested in AOSP for it. Perhaps a bounty might lure one or two - but it would have to be sizeable, and considering the amount of people that seem to have bought this device for the Samsung features - that's going to be hard to organize.
considering the amount of people that seem to have bought this device for the Samsung features - that's going to be hard to organize.
Click to expand...
Click to collapse
This, is the reason the note line, for a while now, has not had the development other Samsung phones have. Add to that , snapdragon and its lockdown , makes it difficult to see the note series as a custom powerhouse.
Sent from my Galaxy Note8 using XDA Labs
Which is a shame, considering the legacy of the Note 3,4 and 5 which continue to have AOSP roms built for them to this day - which has drastically extended the lifespan beyond Samsungs woeful EOL. Sadly devs simply don't seem to have the motivation or time to deal with jumping through the increasingly convoluted hoops constantly being errected by google and OEMs.
Because the note 8 is so locked down
i prefer one ui on this note device as a daily OS since it has S-pen features and LED View cover support. also the stock camera app just works better than anything else i have tried
The only oneui port we have is a broken ish rom right now since i have been experiencing alot of lag while charging and apps randomly crashing when in that laggy state but the camera app on that rom is missing features but the werdest thing is that the phone can apparently record at 4K 60FPS so thats nice i guess.
requirements for a port like this is ofcourse S-pen features, support for the LEW view case. the oneui camera app that can record at 4k 60fps whould be nice but is not a requirement at all
hopefully some one decides to do a port of oneui 3 or 4
If someone were to make a port of the newer OneUI versions, I'd say they might as well take the bit of extra effort and include the Galaxy S8, S9, Note9...
But I think the reality is, it's probably difficult and very time-consuming, because of drivers, but also in part due to OneUI itself.
Biggest hurdle are the drivers I'm sure. Likely requires lots of reverse engineering. Lots of time.
The few people that have the required skills may not want to waste their sanity and time for this, especially not without payback.
cyanGalaxy said:
If someone were to make a port of the newer OneUI versions, I'd say they might as well take the bit of extra effort and include the Galaxy S8, S9, Note9...
But I think the reality is, it's probably difficult and very time-consuming, because of drivers, but also in part due to OneUI itself.
Biggest hurdle are the drivers I'm sure. Likely requires lots of reverse engineering. Lots of time.
The few people that have the required skills may not want to waste their sanity and time for this, especially not without payback.
Click to expand...
Click to collapse
You can use noble rom v 2.5(one ui 4) for note 9 if you looking for a port rom