I've asked a number of questions about what the Alpha 2 is for this thread:
http://forum.xda-developers.com/showthread.php?t=1581065
I guess the question was answered (Thanks), but I'm very confused as to what an Alpha is and what an RC is. The latest title of this thread states "RC3 not Alpha." For those of us new to these ROMS, how are we supposed to make heads or tails of what is being presented. I asked a number of times, if RC2 was Alpha 2, and just got circular answers or "No." I finally found a link myself, which someone responded was the right one for Alpha 2, but I'm still confused as to what RC1, 2, 3, etc. has to do with Alpha 2, 3, 4. Can anyone explain this?
Finally found out the answer to my question by asking in Androidforums
Alpha: for developer testing only; many inherent bugs that require other people who understand coding and such to assist with working on. Not ready for mass consumption, period. There can be different stages of useability here, but suffice it to say, that unless you know how to work under the hood (so to speak), don't touch an Alpha release.
Beta: Still in testing stage, but generally fit for public consumption as most major immediate flaws have been ironed out and just some system bugs remain with UI tweeks to be made as well. Like with Alpha, there are different stages of beta release as well, but they are all varying degrees of "generally useable but not entirely ready to be a daily driver".
RC: This stands for Release Candidate. Imagine a mother bird choosing which of her chicks to kick out of the nest first. The RC is the one she's chosen, so while it's still not fully baked in the sense that it isn't a completely air-tight product from both system and UI perspectives, it's definitely capable of being a daily driver for the avg person, as well as for the person with moderately sophisticated needs. Varying degrees of this step as well (RC2, RC3, etc), but typically when you're looking at a release candidate version of software/firmware, it's close enough to "fully baked" to where you can rely on it to work for you with consistency.
Related
What is cynagenmod and what's so "great" about it?
Thanks!
Sent from my SGH-T959 using XDA App
At the time cyanogen brought a lot of features we now use everyday. Os optimizations apps to sd. Things lf that nature. It is fully opensource and open to anyone to use.
I am fascinated and captivated by the vibrant screen on my epic galaxy s.
Nabeel10 said:
What is cynagenmod and what's so "great" about it?
Thanks!
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
The ability to customize the phone, the stability, the speed, the battery life, and it gives phones the the g1/dream froyo which I guess was deemed impossible. It also gives users great support and updates quite frequently.
duboi97 said:
The ability to customize the phone, the stability, the speed, the battery life, and it gives phones the the g1/dream froyo which I guess was deemed impossible. It also gives users great support and updates quite frequently.
Click to expand...
Click to collapse
Plus it is a large group of people that work collectively together, they along with a few others are the ones that the leading "cutting edge" devs........ they blazed the trail and now all of us and the current devs benefit from their work.
Yea. Since its built from scratch it is faster than any roms here.
The g1 roms were same speed rooted or not
When cm came it was fast! And then a rom based on cm called super d was even faster and then a european rom was fastest!
So what I'm trying to say is, CM is and will be faster than the ROMs built here overclocked or not because the ROMs found here are based on the Official Froyo made by Samsung not a Vanilla Gingerbread rom built from scratch
So I think something built frrom scratch is better than something just modified and themed
Sent from my SGH-T959 using XDA App
It's built from scratch using the AOSP source, which a lot of ROMs are not (many ROMs are merely modified versions of existing stock ROMs).
It has an extensive amount of customization and flexibility beyond any other ROM I've ever used on an Android device.
I don't mind the ROM I'm running on my Vibrant, but I miss CyanogenMod. Since the CM7 release candidate for the MT4G just hit, I think it's time for me to change it up a bit. I'm tired of my short-range wifi (seriously, less than full bars when I'm only six feet away from my 802.11n router?), non-functional GPS and totally wonky compass, anyway.
I think one of its advantages is the sheer size of the community, if you've ever used various Linux distributions the same concept applies. When your user base expands to the point where you've got dozens if not hundred of loyal users posting guides, reporting bugs, requesting features, and answering new user's questions the community really feeds on itself and builds momentum. Cyanogen is largely responsible for a lot of the momentum in the rom community, and I know it's brought more people to the community than almost any other project.
A lot of things.
The cyanogenmod options alone are worth it - VM Heap, swap, JIT, compcache, et cetera. Granted these things are more relevant to lower end devices. Then there's the native ADW launcher integration. I've never been about to replace the stock launcher with ADW and get the same results.
It's really just its use in practice. Everything works, the interface is very instant/responsive (no jagged animations/scrolling, ever), no force closes, lots of mods/hacks for it from the community, which in general is very scrutinous about performance/stability hangups. Battery life twice what you're use to.
They're the only ROM team I've donated to. I flashed hundreds of roms when I had my Magic (one of the hardware-weakest android phones) but CM is what kept it up to par, giving me an extra generation's life out of it.
I personally love all the features built in, like pulldown menu modifications, as well as pretty much customizing every aspect, NO roms like that exist for our Vibrants..
It is Cyan in color, and mod like the british music scene duh!
hmm... I might have to give cm7 a try once they get it working on the vibrant. They are working on it right? If the manufactures were smart, they would give a pre-release phone to those guys before it's available to the public. Of course, the carriers may not like it. I just purchased my vibrant 3 weeks ago (former iphone 4 user). I tried a few darkyy's roms, then toxic, then finally I stuck with trigger. I'm very satisfied with it - mainly b/c everything works nice and smooth.
I see I'm a bit late but yes, Trigger is awesome. I tried flashing others and I always come back after 2days tops.... For some reason, Trigger runs so much smoother than the other ROMs on my phone... And I have tried 2.2.1(Honestly I dont get the difference) and I am not a fan of the 2.3.3 because most say the GPS doesn't work and I use my GPS at work, yes through my phone(I'm cheap). Plus that is one of my reasons for buying a "smart phone" It has everything at your finger tips, or supposed to at least right. Hope your having fun.,..... BTW, CM is freaking awesome on every device I have seen it on...... I'm actually curious to know why it's not on the Vibrant as an official build but eh..... It will come when it's ready I suppose
The GoogleNow ICS project is currently pretty stable with version "M6" and you can use it on even the stock ROM (root).
Does this negate from your anxiousness to update to Jellybean? Or are you looking more forward to performance features?
It's holding me over until Cm10 is finished
Sent from my EVO using Tapatalk 2
If you have Jellybean on another device (like myself), then I'd have to say the consensus would be 'no, it's not "enough"'. Not everyone will react this way to my upcoming point but being a PC gamer and being used to super smooth transitions/FPS is very eye sensitive and non-smooth animations hurt my eyes at times. Project Butter is everything they said it will be and more. The smoothness doesn't end within Google Apps/Android OS. It's universal. Everything is ... well... buttery smooth. It's awesome but it's something you have to experience first hand to appreciate.
Also, notifications (while not all apps are taking advantage of this atm) are awesome. Being able to read my emails without having to open Gmail for a quick summary is great. All around small updates that make a huge difference. Bottom line: if you're not yet using Jellybean, you'll be fine. If you have experienced the different smaller update flavors that the jelly beans offer, it will suck for a little bit.
For those not aware that we have a fully working version of Now, download it here (get the M6 version):
http://forum.xda-developers.com/showpost.php?p=29756226&postcount=2856
Or watch a video of myself sucking at impromptu talking while filming something late at night and showing off how fully Now is working next to a Jellybean device:
Yes. To me, GoogleNow is actually the least attractive part of jellybean, and my current plan is actually to fully disable it when we get the jb update.
I just want it for the newness & also because I don't have it yet.
I'm pretty satisfied though.
With my old tablet the custom roms always meant a performance increase too, but:
I've tried pretty much well every single custom rom available for this tablet by now and i still havent managed to find one that actually increases the performance of the tablet. When im running the stock firmware i get about 7500-7600 on quadrant and my browser is really responsive and stuff. There's not been a single custon rom out there that has even performed better then 5600 on quadrant. Is it just me, or are the custom roms not hat good performance wise?
EDIT: By better performance i mean how snappy the tablet feels, using benchmarks as a secondary frame of reference.
Not sure if quadrant is doing a good job. I also am getting same results as you with 7xxx for stock and 5xxx for all CM based ones. Although the CM roms feel smoother here.
Sent from my SGP311 using XDA Premium HD app
I abstained the vote cause the question does not bear a black and white / yes or no answer anymore these days.
In my humble opinion, and I picked up the smartphone / PDA / mobile device modding bug back about when this site catered to the the original HTC XDA almost exclusively, and Steve Jobs was merely having wet dreams about his iPhone (*1)... nodded RIMs have gotten to a state where they are overvalued. Saying a custom ROM is always way ahead of stock is like saying "one device with a fixed featureless fits everyone perfectly".
Custom ROMs had their deserved heyday when the industry loaded up near every carrier distributed smartphone with scrappy bloatware that made you weep. Depending on the mobile OS at any given time it was nigh impossible to get rid of that stuff, unless you flashed the whole shebang. From there on the custom ROM scene kinda exploded along with the market distribution of smartphones and later on tablets, certainly owed to the introduction of Android over older generation closed source systems, which enabled much more in-depth possibilities of adding novel features, fixing stuff that was basically broken out of the box and integrating all of this nicely.
(For a frame of reference: I tossed my PalmPilot and Nokia phone when the HTC Wallaby (Telekom MDA or so)hit the shelves... Early adopter by nature and I thought combining cellphones and PDAs, bother which I used avidly was the most revolutionary idea since the combustion engine. This was generation Windows Pocket PC, basically a PDA with cellphone feature thrown in as an afterthought (the antenna actually doubles a stylus compartment). Phone integration was a PITA on good days. On bad, long work days it might just happen that your moody battery would jump from 35% to flat out dead within a mere six minute phone call. Yet, no biggie right? Well, it was, the devices had no non volatile storage. Dead battery means go home, pray your last phone backup is recent enough and restore the entire thing. I spent a lot of time fixing this device (windows style - shoehorning in binary OS components from newer PocketPC versions and prodding the registry on the phone (!)...) to a point where it was almost usable as PDA only device, supplementing telephonly with a Nokia.
A while later better devices came out, PocketPc was scrapped for Windows Mobile and in high hopes I got a HTC Charmer. This looked like a more solid platform and indeed proper custom ROMa emerged, adding real functionality and allowing to get rid of carrier branded crap, later even RIMs emerged with Windows Mobile version updates never intended for that phone, some even taking the recent cutting edge HTC front-end, the first incarnation of Sense (I think it was called vanilla). I figured the really bad conceptual problems were fixed and merrily went along. But, as god hates my guts, I drained the battery accidentally, only to find that the phone would still go dead, deaf, dumb and wiped despite a good three or four years of technological progress. I was so confident that I neglected backups with that model and basically lost the majority of my stuff again. The Nokia dumbphone was back in the game, the HTC left a dent in the wall that required plaster and a patch of new wallpaper.
TL;DR: The first gen smartphones (PDA with cell module afterthought were such flawed concepts, badly integrated, that keeping recent backups and maintaining it operational took quite an effort on user side, on that sort of negated the higher productivity of using one altogether. But bear with me now, I am still circling around the point or two I want t. Make.
Because a few months after I abandoned smartphones for good (or so I thought) Apple coughed up their iPhone prototype and a few months later pumped it to market. I was amazed (not because of the technological feat, they were more or less throwing R&D money bricks at existing tech and concepts, however they exactly figured out what went wrong in the early generations, fixed that stuff, added fingerdriven multi-touch in favor of stylus driven displays and, this is the real kicker, in a time and age when the cool cell to have was a Nokia 8 Series or a decent, very small flipphone or clamshell they managed to brainwash their customers into what PDA and smartphone adopters at that time already knew - it's totally worth to dump the train of ever smaller telephony only cells for a much larger, more fragile device because of all the freedom and power those things offer you.
I kept my guard and obviously went for Android devices once I got back on the horse. HTC Desire, a backup Wildfire, Desire HD, Sensation, One S and a few tablets along the way. Now, here is the kicker. The Desire ran much better with a custom. The Wildfire could only be updated to a recent Android version with a custom ROM due to HTCs sometimes appalling quick update discontinuation. The Desire HD ran a basically stock custom ROM! But with lots of lovely icon eyecandy, so I stuck with that too. The Sensation benchmarked equally (give or take 5%) but the ROM added novel features, properly implemented, which I decided to stick with. But frankly, it was because I could. I would not have recommended a newbie to Android flashing to take the plunge. My current HTC One S has a recovery downloader and is rooted cause some essential apps I can't live without need it. Full custom ROM switch. I see no point. Android has come a long way. If today I have bloatware I can go to App Manager and disable them. Icon gone, runtime resource hogging gone. Many features that were the selling points for a custom ROM a while back are now natively incorporated.
This is just how I feel about my Sony SGP311 now. It runs 4.2.2 rooted, no recovery yet. This is planned, maybe at some point a stable, close to stock custom kernel to allow some overclocking on a per app basis for XBMC. But other than that it just Danny works. The Sony skin put over stock Androi. Is not that bad, and more to the point it never gave me the impression of hogging the system. Turn off what is useless to you, Office suite, walkway, etc and be on your merry way. It just comes down to what you do with the device, but as a custom ROM junkie who has just gotten off the habit, for me it makes no sense anymore.
Now, if you made it all the way here, I ran two benchmarks on my 4.2.2 root but stock. Maybe they aid you in your decision.
EDIT: the attachments are garbage. Here are proper links:
http://i.imgur.com/vMFEX1p.png
http://i.imgur.com/IEPVvMS.png
http://i.imgur.com/mB5MKSH.png
Also, none of the above is supposed to rain on the developers parade or something. I admire your skills and dedication over all those years, and there isn't a single custom ROM that went onto my devices withour a PayPal "crate of beer" donation ever. However, the fiddling, time spent reading up on custom ROM choice, issues and unlocking process etc is just not in relation for me anymore. Those thoughts are yours to reject, spindle, mutilate, adopt, oppose or plainly ignore... Just speaking for myself here.
Thanks for this! I was also trying to decide if I should be flashing a custom rom on my XTZ. I am itching to flash but couldn't come up with any strong reason to do so, probably for battery life and stock look?
Will be interesting to hear from another person who is a strong believer of flashing custom rom on XTZ.
Sent from my GT-N7105 using Tapatalk
i got slightly better score using a custom rom. Plus i get themes, expanded desktop and pie control which is a must for this tablet. I hope more xda developers develop for this tablet. Will reward with donations
By "better performance" do mean higher benchmark scores? Because any of the 4.3 ROMs I've tried are generally smoother than Sony's 4.2.2.
Spartoi said:
By "better performance" do mean higher benchmark scores? Because any of the 4.3 ROMs I've tried are generally smoother than Sony's 4.2.2.
Click to expand...
Click to collapse
4.3 too bugy for me
im using 4.2.2 cm rom FXP242-cm-10.1-20131021-UNOFFICIAL-pollux_windy.zip
i already sent team a donation hope to keep em motivated
Spartoi said:
By "better performance" do mean higher benchmark scores? Because any of the 4.3 ROMs I've tried are generally smoother than Sony's 4.2.2.
Click to expand...
Click to collapse
Sorry, the post was incomplete. Changed it.
r1ntse said:
Sorry, the post was incomplete. Changed it.
Click to expand...
Click to collapse
I prefer 4.2 ATM. I get close to 30 Mbps download speed on this ROM where on 4.3 roms only 2mbps download? Also video cam recording, screen is squashed on 4.3. Other than that they run great but I personally cant feel a performqnce boost from 4.3 to 4.2. I also installed crossbreader and Supercharger V6 script which addresses screen redraw lags, so if there is a slower issue with 4.2 i would have addressed it with these two mods and may not be able to tell.
Ivan, or more popularly known as 秋叶随风, is a super fan / guru that has help beloved MIUI fans around the world by developing customised ROMs.
When the MIUI news team first broke news about the upcoming interview
with Ivan, our ever enthusiastic fans responded with over 100+ burning
questions for dear Ivan in our fan poll!
Despite churning out amazing works that are used by MIUI fans all around
the globe, Ivan keeps a surprisingly low profile, and trying to befriend him
on QQ is no easy feat; His one and only friend request question requires
you to know his boss’s phone number before you can gain acceptance as his
friend!
Of course, the MIUI news team spares no efforts in reaching out to Ivan
for the ever curious MIUI fans, and here’s the much-awaited interview with
some of the interesting fan questions, complete with a real snapshot of
what Ivan looks like!
Question 1 : Tell us 4 interesting facts about
yourself!
I’m actually a staff of Xiaomi and a big loyal fan of MIUI!
Nobody calls me by my real name at work - Instead, everyone prefers to
call me by my nickname, “秋大”
I used to be a developer for iOS and webkit, the open source web browser
engine that's used by Safari, Dashboard, Mail, and many other OS X
applications
I’m a novice in swimming, having just picked up the skill last year; To be
honest, my swimming can’t even rival that of the kids that I see in the pool!
Question 2: What do you actually do in Xiaomi and
how long have you been working there?
I started working for Xiaomi last year and is currently involved in Linux
server and configuration management and technical support. My main duty
is to ensure that my fellow colleagues can work or laze happily! Occasionally,
I dabble in MIUI system upgrades, memory optimization, stable ROMs
upgrades as well as updating the Android version to allow my colleagues to
test out Google’s latest features.
Question 3: How did you learn to customise ROMs
and can you teach other aspiring fans how to go about
doing it too and what is required to get started?
When I first came into contact with Android phones, the phone
manufacturers integrated the phones with too much bloatware that made the
user experience abysmal. Hence i decided to try my hand at customising the
ROM by myself, purely out of interest! I am actually self-taught, and
personally i think this is one area that is very difficult to teach.
For aspiring fans that would like to go down this path to customise their own
ROM, my advice would be to first familiarise yourself with Java, C, C++
and Linux, as well as shell kernel script writing. A good way to get started is
to follow what others have done in customising the ROM, by basing it on
their git log to understand the logic behind the tweaking. Of course, the
prerequisites are that you have plenty of time, and a relatively good
computer with fast internet speed.
Question 4: What features are you planning to add
to your latest customised ROM?
It may surprise you, but i do not like adding new functionalities. If you want
to, you don’t have to do it yourself, but use the ready solutions out there
like CyanogenMod, Paranoid Android, AOKP, etc.
Question 5: What device are you using now and why?
I am currently using two phones; an iPhone 5, and Mi2. I love my Mi2
primarily because i find the size perfect, and the hardware is not outdated,
and best of all, i can customise it everyday!
Question 6: How long does it take for you to work
on each ROM?
From conceptualisation till its actual run takes around 1 week, but it could
take 1 to 2 months to correct for all the bugs and stabilise the system. If i
am lucky, I could update and release a more stable version in 1 - 2 weeks.
Question 7: Do you actually earn anything from
doing this?
I pursue and customise ROMs out of my pure personal interest and passion
to share what I love with fellow MIUI fans, and I do not earn a single cent
out of this. Of course, more money is always good, but personally my
opinion is that if one were to pursue this out of monetary interest, it would
defeat the purpose of doing this in the first place.
Question 8: What was the first ROM you made and
what was the motivation behind it?
I first customised the ROM for my Huawei C8500/U8150. Back then,
the phones is packed with more customised softwares. I had the idea of
customising it for my phone for a very simple reason; the touch points for
the phone weren’t many at the point in time, and i decided to tweak the
kernel source to add two more touch points and that’s how I got started!
After that, I got hooked on customising and the rest is history.
***** TOP FAN. QUESTION *****
(from @ej8989 -> We see you have great potential as paparazzi! Care to join the
MIUI News Team? )))
Question 9: Are you dating someone within the
MIUI community?
My interactions with fellow colleagues hardly extend beyond our professional
working relationship, and the majority of the fans are guys! No girl would
want to date a code geek anyway, so… to put it simply, no.
Source : MIUI forum
en.miui.com/thread-48984-1-1.html
Hope all of you enjoyed. (Nothing talked about sources makes me sad).
Lol. No mi-bunny for me though.
Dear Ivan
Have a great respect for you Bro...
SaiMadhav
sivabommakanti said:
Ivan, or more popularly known as 秋叶随风, is a super fan / guru that has help beloved MIUI fans around the world by developing customised ROMs.
When the MIUI news team first broke news about the upcoming interview
with Ivan, our ever enthusiastic fans responded with over 100+ burning
questions for dear Ivan in our fan poll!
Despite churning out amazing works that are used by MIUI fans all around
the globe, Ivan keeps a surprisingly low profile, and trying to befriend him
on QQ is no easy feat; His one and only friend request question requires
you to know his boss’s phone number before you can gain acceptance as his
friend!
Of course, the MIUI news team spares no efforts in reaching out to Ivan
for the ever curious MIUI fans, and here’s the much-awaited interview with
some of the interesting fan questions, complete with a real snapshot of
what Ivan looks like!
Question 1 : Tell us 4 interesting facts about
yourself!
I’m actually a staff of Xiaomi and a big loyal fan of MIUI!
Nobody calls me by my real name at work - Instead, everyone prefers to
call me by my nickname, “秋大”
I used to be a developer for iOS and webkit, the open source web browser
engine that's used by Safari, Dashboard, Mail, and many other OS X
applications
I’m a novice in swimming, having just picked up the skill last year; To be
honest, my swimming can’t even rival that of the kids that I see in the pool!
Question 2: What do you actually do in Xiaomi and
how long have you been working there?
I started working for Xiaomi last year and is currently involved in Linux
server and configuration management and technical support. My main duty
is to ensure that my fellow colleagues can work or laze happily! Occasionally,
I dabble in MIUI system upgrades, memory optimization, stable ROMs
upgrades as well as updating the Android version to allow my colleagues to
test out Google’s latest features.
Question 3: How did you learn to customise ROMs
and can you teach other aspiring fans how to go about
doing it too and what is required to get started?
When I first came into contact with Android phones, the phone
manufacturers integrated the phones with too much bloatware that made the
user experience abysmal. Hence i decided to try my hand at customising the
ROM by myself, purely out of interest! I am actually self-taught, and
personally i think this is one area that is very difficult to teach.
For aspiring fans that would like to go down this path to customise their own
ROM, my advice would be to first familiarise yourself with Java, C, C++
and Linux, as well as shell kernel script writing. A good way to get started is
to follow what others have done in customising the ROM, by basing it on
their git log to understand the logic behind the tweaking. Of course, the
prerequisites are that you have plenty of time, and a relatively good
computer with fast internet speed.
Question 4: What features are you planning to add
to your latest customised ROM?
It may surprise you, but i do not like adding new functionalities. If you want
to, you don’t have to do it yourself, but use the ready solutions out there
like CyanogenMod, Paranoid Android, AOKP, etc.
Question 5: What device are you using now and why?
I am currently using two phones; an iPhone 5, and Mi2. I love my Mi2
primarily because i find the size perfect, and the hardware is not outdated,
and best of all, i can customise it everyday!
Question 6: How long does it take for you to work
on each ROM?
From conceptualisation till its actual run takes around 1 week, but it could
take 1 to 2 months to correct for all the bugs and stabilise the system. If i
am lucky, I could update and release a more stable version in 1 - 2 weeks.
Question 7: Do you actually earn anything from
doing this?
I pursue and customise ROMs out of my pure personal interest and passion
to share what I love with fellow MIUI fans, and I do not earn a single cent
out of this. Of course, more money is always good, but personally my
opinion is that if one were to pursue this out of monetary interest, it would
defeat the purpose of doing this in the first place.
Question 8: What was the first ROM you made and
what was the motivation behind it?
I first customised the ROM for my Huawei C8500/U8150. Back then,
the phones is packed with more customised softwares. I had the idea of
customising it for my phone for a very simple reason; the touch points for
the phone weren’t many at the point in time, and i decided to tweak the
kernel source to add two more touch points and that’s how I got started!
After that, I got hooked on customising and the rest is history.
***** TOP FAN. QUESTION *****
(from @ej8989 -> We see you have great potential as paparazzi! Care to join the
MIUI News Team? )))
Question 9: Are you dating someone within the
MIUI community?
My interactions with fellow colleagues hardly extend beyond our professional
working relationship, and the majority of the fans are guys! No girl would
want to date a code geek anyway, so… to put it simply, no.
Source : MIUI forum
en.miui.com/thread-48984-1-1.html
Hope all of you enjoyed. (Nothing talked about sources makes me sad).
Click to expand...
Click to collapse
Greetings,
I'm posting this on the General as the forum associated with this mobile device is pretty much dead ATM. It falls very much more in the category of "I need help figuring out how to do this Android Global thing" rather then a very specific issue with a device.
The long and the short of it is the Samsung Galaxy On5 SM-G550T/1 was a fairly short lived phone in the US. It's a barebones phone that has a lot of features of design choices of the Galaxy S5 and S6 while having very minimal accessory hardware (which as an altimeter and advanced GPS systems).
This phone, however, has seen *A LOT* of popularity in Easter EU, Middle Eastern or Indian markets and thus there is a TON of Rom development still active for this phone.
The SM-G550FY has significant differences with the Sound Drivers, Camera Drivers, Bluetooth Drivers and Modem Drivers that makes the ROMs, in general, compatible enough to be installed, but not compatible enough to have the Sound or Camera work and has varying levels of Modem and Bluetooth viability; more often then not, they work though.
Someone finally dropped a hint that most these drivers are in the /system/lib folder requiring CHMOD of 740 to work; but no one to the best of my knowledge has actually gotten this "workaround" to work. This was something that was completely foreign (no pun intended) to many of us who have posted in that forum. I've had zero success with this, but it seems to have gotten me looking in new directions for fixes.
So my questions are a few fold that I hope the XDA greater community can help with:
#1.) Is there a way to import the correct drivers that are verified working in the same version of Android from another rom?
#2.) Are drivers for different versions of Android the same (IE 6.0 and 7.0 since those are the ROMs being regularly released) or are we reliant on Samsung to release a properly working set of 7.0 drivers to get Android 7.0 working on the US/CA variants of the phone?
#3.) I'm looking for good resources to learn how to build an installer for a ROM to try to build and release a patcher to make SM-G550FY roms compatible with SM-G550T/1 Roms. What resources could you suggest to get myself better up to speed to doing this.
#4.) I'm also looking for good resources to learn how to build ROMs perhaps based on Lineage for my model of the phone. Where would I go to learn more about that?
Thanks for any help you guys can provide.