Database Develop

(discussion) Rom development for Galaxy

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 !

Crappy firmware rant

I'm not sure if I can blame this on the race-to-market state that the industry is in but there are a lot of
poorly performing phones being released. Manufacturers rush to release new products without doing
the necessary development tests. Product testing has been moved form the lab to the customer base.
Take the case of the Nexus 4.
I read an article where an HTC Droid DNA user was complaining how HTC is slow to release the latest
Android OS and he decided it was time to make the switch to Nexus because he can't wait for updates.
But do Nexus users really get the best experience?
Nexus devices often use inferior hardware to cut the cost and I have no complaints here - I love the fact
that the Nexus4 costs almost half as much as the Droid DNA. But what about software?
I will give it to Google and LG for releasing a phone where at least everything works, some companies
don't go that far. But the Nexus4 currently works below it's potential. The firmware is buggy and not
optimized for best performance.
- The camera uses the same sensor as the LG Optimus 2X but produces much noisier pictures.
- The autofocus doesn't work that great.
- The screen colors are dialed in to a yellowish hue
- The microphone gain is way too high a distorts easy
There are a lot more annoyances but note that I only listed items that can easily be adjusted. With the
proper equipment it should take just a few hours to calibrate the phone so it works to it's highest
potential. Which makes me wonder whether calibration was done poorly or not at all.
Some argue that Google releases source code and unlocks their devices for independent developers to
adjust to their liking. But developers don't have the type of testing equipment that the manufacturer has
and even with the source code available it could be impossible to figure out how to control hardware modules
without the corresponding documentation. Developers tend to work in the dark most of the time.
Not sure what point I'm driving to here, I'm just frustrated. I'm realizing that I want a device where everything
works great at release time so I don't have to wait for kernel fixes. I wonder when (or if) LG and Google will
address these and how that reflects on the entire phone industry.

4.2 was obviously rushed, as was illustrated by the lack of December in the calendar. That can be fixed in time.
As regards hardware, I totally get where you're coming from. In order to make a decent profit on the handhelds, it's pretty clear that LG cut some corners in everything from components (some) to quality control. Is there a blasted thing that can be done about it from our end? No. But, we have a pretty freakin' awesome phone for $300-$350 with the latest Android. It's a tradeoff. Take it or leave it.

-Mindroid- said:
I'm not sure if I can blame this on the race-to-market state that the industry is in but there are a lot of
poorly performing phones being released. Manufacturers rush to release new products without doing
the necessary development tests. Product testing has been moved form the lab to the customer base.
Take the case of the Nexus 4.
I read an article where an HTC Droid DNA user was complaining how HTC is slow to release the latest
Android OS and he decided it was time to make the switch to Nexus because he can't wait for updates.
But do Nexus users really get the best experience?
Nexus devices often use inferior hardware to cut the cost and I have no complaints here - I love the fact
that the Nexus4 costs almost half as much as the Droid DNA. But what about software?
I will give it to Google and LG for releasing a phone where at least everything works, some companies
don't go that far. But the Nexus4 currently works below it's potential. The firmware is buggy and not
optimized for best performance.
- The camera uses the same sensor as the LG Optimus 2X but produces much noisier pictures.
- The autofocus doesn't work that great.
- The screen colors are dialed in to a yellowish hue
- The microphone gain is way too high a distorts easy
There are a lot more annoyances but note that I only listed items that can easily be adjusted. With the
proper equipment it should take just a few hours to calibrate the phone so it works to it's highest
potential. Which makes me wonder whether calibration was done poorly or not at all.
Some argue that Google releases source code and unlocks their devices for independent developers to
adjust to their liking. But developers don't have the type of testing equipment that the manufacturer has
and even with the source code available it could be impossible to figure out how to control hardware modules
without the corresponding documentation. Developers tend to work in the dark most of the time.
Not sure what point I'm driving to here, I'm just frustrated. I'm realizing that I want a device where everything
works great at release time so I don't have to wait for kernel fixes. I wonder when (or if) LG and Google will
address these and how that reflects on the entire phone industry.
Click to expand...
Click to collapse
Anddddddd, another whiner..... N4 is a great phone that came out just 2 months ago!!!! It will only get better!!! If you don`t like yours just sell it and head over to the FRUIT store

I don't understand .... You saying that phones like Samsung or apple are bugles?
1. ICS update for gs2. OMG battery drain was stupendous , even though Samsung released update after a month or son it took even longer on carrier based devices
2. IPhone there was an issue with WiFi or so
Fixed within few weeks
3. Nexus 4 - December bug fixed before December (I cant imagine update coming through on devices modified by network operators
It might seem that OEM devices are flawless bout you couldn't be more wrong . they have bugs but not ones that you see at first glance and trust me they take much longer to fix as less people notice them
Sent from my Nexus 4 using xda premium

MattSkeet said:
I don't understand .... You saying that phones like Samsung or apple are bugles?
1. ICS update for gs2. OMG battery drain was stupendous , even though Samsung released update after a month or son it took even longer on carrier based devices
2. IPhone there was an issue with WiFi or so
Fixed within few weeks
3. Nexus 4 - December bug fixed before December (I cant imagine update coming through on devices modified by network operators
It might seem that OEM devices are flawless bout you couldn't be more wrong . they have bugs but not ones that you see at first glance and trust me they take much longer to fix as less people notice them
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
This is a great point, and one of the main reasons to have a Nexus device.

Nothings perfect bro look at apple maps
Sent from my Nexus 4 using xda app-developers app

Problems like battery drain and Maps take a long time to debug and fix. It's still
unacceptable but understandable.
Offset colors on a screen should take minutes to adjust with the proper equipment.
Seriously! It should be done right the first time. I'm reading on here that small problems
with the Galaxy Nexus were never fixed.

BigDig said:
Anddddddd, another whiner..... N4 is a great phone that came out just 2 months ago!!!! It will only get better!!! If you don`t like yours just sell it and head over to the FRUIT store
Click to expand...
Click to collapse
So because he has legitimate complaints about a device he purchased, he must not voice them and go buy an iPhone? Do you realize how dumb that sounds? Just wanted to point that out.
Sent from my HTC VLE_U using xda premium

-Mindroid- said:
I'm not sure if I can blame this on the race-to-market state that the industry is in but there are a lot of
poorly performing phones being released. Manufacturers rush to release new products without doing
the necessary development tests. Product testing has been moved form the lab to the customer base.
Take the case of the Nexus 4.
I read an article where an HTC Droid DNA user was complaining how HTC is slow to release the latest
Android OS and he decided it was time to make the switch to Nexus because he can't wait for updates.
But do Nexus users really get the best experience?
Nexus devices often use inferior hardware to cut the cost and I have no complaints here - I love the fact
that the Nexus4 costs almost half as much as the Droid DNA. But what about software?
I will give it to Google and LG for releasing a phone where at least everything works, some companies
don't go that far. But the Nexus4 currently works below it's potential. The firmware is buggy and not
optimized for best performance.
- The camera uses the same sensor as the LG Optimus 2X but produces much noisier pictures.
- The autofocus doesn't work that great.
- The screen colors are dialed in to a yellowish hue
- The microphone gain is way too high a distorts easy
There are a lot more annoyances but note that I only listed items that can easily be adjusted. With the
proper equipment it should take just a few hours to calibrate the phone so it works to it's highest
potential. Which makes me wonder whether calibration was done poorly or not at all.
Some argue that Google releases source code and unlocks their devices for independent developers to
adjust to their liking. But developers don't have the type of testing equipment that the manufacturer has
and even with the source code available it could be impossible to figure out how to control hardware modules
without the corresponding documentation. Developers tend to work in the dark most of the time.
Not sure what point I'm driving to here, I'm just frustrated. I'm realizing that I want a device where everything
works great at release time so I don't have to wait for kernel fixes. I wonder when (or if) LG and Google will
address these and how that reflects on the entire phone industry.
Click to expand...
Click to collapse
WAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA.....
frustrated with what?
I turn my phone on it comes on. I dial a number it calls it. I go to a web page it loads it. I stream music is streams it.
Your issue is you seem to think your little bubble of the world applies to everyone. My Phone does not have a yellowish tint. I don't use the microphone. So I don't care about distortion with it. The camera looks fine to me. But then again I aint a photo junkie. Altho if I was I'd use my Nikkon camera, not my phone....
You see, I get a nexus, and android, so that I can tinker. I can create. I can remove, I can improve. I can have the newest and latest.
You seem to get one because? I don't know what you got on for. Cause these things seem lost on you....
Do as others say, Sell it, make an extra hundy, and go get something else.....

OK you're not happy but these threads go nowhere and you can see that already so will stop it now.
Thread closed.

Is software to blame for unreliable camera and speaker? Possibly...

So we already have a thread on how software may be to blame for the hit-and-miss autofocus of the camera on this phone. That came from The Verge review of the phone which stated that:
There is a glimmer of hope, however. Representatives from the Android team say that software is to blame for the weak performance, not hardware, and reps tell me that a fix is coming to deal with the issues in the upcoming weeks. I've even seen an early build of the new software, and while it's only a minor improvement — autofocus is a hair faster, but still inconsistent, and picture quality hasn't changed — it's nice to see Google already at work.
Of course, there's no set date for a fix at this point, and I don't know how much the camera can actually be improved through software, but if the Moto X is any kind of example, there might just be a solution to this very disheartening problem.
Click to expand...
Click to collapse
Now I have seen another article from Pocketnow about the iffy quality of the speakers suggesting that software, again, might be to blame:
But as it turns out, this lousy audio quality isn’t system-wide, and some apps seem immune, playing music without issue. That’s led to speculation that the Nexus 5′s software could be behind these quality problems, attempting to filter or otherwise shape its audio output, and ending up with the mess we see here.
We can’t help but wonder if this might be tied to Google’s rush to get together sufficient stock for the phone’s launch, resulting in a situation like we saw exemplified with the mandatory update needed to even set up the phone. Hopefully, Google will be speaking up soon to clarify just what’s going on here, and let us know if any fix might be forthcoming.
Click to expand...
Click to collapse
Finally there are rumours of 4.4.1 already beginning to surface.
What do make of all this? Do you think we might possibly see improvements to camera and speaker in software updates?

I hope so. I have been a nexus fan since the beginning but honestly the speaker and camera quality frankly sucks on this phone after using it for a few days. I know for the price point what do you expect but if other company's like Xiaomi can create a great phone for low $300's than Google/LG should be able to do the same. I really think a software update can fix these 2 issues so here's for hoping.
Sent from my Nexus 5 using xda app-developers app

[PROJECT][WIP]Touchwiz camera for AOSP

It might sound ridiculous, but let me and my development team (my close relatives which do have their down work) begin our biggest project yet - porting Touchwiz Camera for AOSP ROMS (or at least every feature which are available on stock Touchwiz). Our goal is simple - bring glorious Touchwiz camera and it's bells and whistles to AOSP ROMs, let it be Lineage or Resurrection Remix, it doesn't matter. We began our development and we will consider using Magisk as an option of getting this to work.
Be aware, that this project might never come to life (trust me, if developers couldn't bring all of our camera features to AOSP, then it's obvious how difficult it is to accomplish this). It might even require to edit the entire AOSP for this to work.
As everyone know, Touchwiz camera is closely related to Touchwiz framework, so as a consequence it closely relies on that code written. AOSP has a completely different CameraHAL for making camera even to work. So, yeah. OnePlus One has something similar already accomplished, so our goal is exactly the same.
All of the development progress will be posted here.
And please note, that this is our hobby job, not a full-time job, so when there is free time to spare, we'll spend it doing this crazy project to work and move forward.
XDA:DevDB Information
Touchwiz Camera porting project to AOSP, Device Specific App for the Samsung Galaxy S5
Contributors
airidosas252
Version Information
Status: Testing
Current Stable Version: TBA
Current Beta Version: TBA
Created 2017-06-30
Last Updated 2017-06-30

Reserved

Reserved1

go for it! good luck

Wait for it. Good luck!

Glad to hear this. Hope you can get it figured out.

I'm so glad to know that! :victory: PATIENCE and HOPE! :good:

Best of luck to ya!

Good luck guys!

Amazing!

Good luck! Hoping you can make it

Good luck guys!!! I have been waiting for such great developers!!! If you'll do it you'll sign a mile Stone, it will be part of the developing history!
I wish you all the best

Thanks for all your great words!
On the flip side, we had many difficulties, starting from bootloop issues to camera stop working even with stock ROM. We are still doing some progress. Logcats and tons of trials and errors helped us out. Moving slowly forward.
Sorry for being off quite recently. Busy working and doing personal stuff.

Progress update:
Nougat is an utter a**. Not only it would be next to impossible to make video recording work (photo capturing is a much easier job), it would take years to make it work. We are searching for some counter measures now. Looks like horrible roadmap is coming up next to our door. We are prepared.
Reserve engineering is as prominent as my need to eat. I know it does not make much sense, but I think you get the idea. Thanks for the support you all.

airidosas252 said:
Thanks for all your great words!
On the flip side, we had many difficulties, starting from bootloop issues to camera stop working even with stock ROM. We are still doing some progress. Logcats and tons of trials and errors helped us out. Moving slowly forward.
Sorry for being off quite recently. Busy working and doing personal stuff.
Click to expand...
Click to collapse
airidosas252 said:
Progress update:
Nougat is an utter a**. Not only it would be next to impossible to make video recording work (photo capturing is a much easier job), it would take years to make it work. We are searching for some counter measures now. Looks like horrible roadmap is coming up next to our door. We are prepared.
Reserve engineering is as prominent as my need to eat. I know it does not make much sense, but I think you get the idea. Thanks for the support you all.
Click to expand...
Click to collapse
Don't give up! "Hope is the last to die"! :good:
Sent from my SM-G900F that scored 73.844 in AnTuTu with No Limits 6.1 ROM. . .

Are you reverse engineering with IDA? there was a developer working on the s6 I think it was who reverse engineered and found many factory variables that were called on during certain camera processes and managed to implement them into the camera wrapper in a "dirty" fashion that wouldn't get approved to be official. It did seem though he improved the camera a lot by using factory light sensing and focusing calls he found from the reverse engineering. Id bet our s5 uses many of those same functions and names, i'll see if I can dig that thread it. It was shared in the lineage 14.1 thread.

Wow this is a amazing info
The bad camera in resurrectionremix is the only part, why I don't use this awesome rom on my S7.
Take your time and hopefully you rock it

omgbossis21 said:
Are you reverse engineering with IDA? there was a developer working on the s6 I think it was who reverse engineered and found many factory variables that were called on during certain camera processes and managed to implement them into the camera wrapper in a "dirty" fashion that wouldn't get approved to be official. It did seem though he improved the camera a lot by using factory light sensing and focusing calls he found from the reverse engineering. Id bet our s5 uses many of those same functions and names, i'll see if I can dig that thread it. It was shared in the lineage 14.1 thread.
Click to expand...
Click to collapse
Yeah, reserve engineering is our only way out. It's not possible to achieve anything in a simple fashion. I would definitely call this project a win if we at least succeed making 1080p60 to work properly, other things like fast focusing and other things might come as well, since the dynamic range on LOS completely sucks. Pictures look dead.
BTW, if what you are saying about S6 is correct, our job might become a lot easier. I believe S6 has a different camera sensor calibration from the get-go, even if the sensor is identical (minus the OIS). If those variables are accessible to us, we might get some incredible results. Of course, with a lot of patience.

And for your own convenience, I won't ask for any donations. Why? My words speak for themselves. I don't want to rob your money. And as plus, I would lose my confidence.

Wishing u and ur team the best of luck with this project fingers crossed

LineageOS on OP3T, everything works?

Hi
I'm new here. I recently got a Oneplus 3T (Midnight Black Edition). I am a huge fan of lineageOs. I was wondering if I flash los in Oneplus 3T, will everything work? I mean is there any known bug present?
Thanks for replying.

There was some bugs a year ago, but those have all been ironed out under the past year.
And the camera API problems can only be fixed by OnePlus, if only they would.

pitrus- said:
There was some bugs a year ago, but those have all been ironed out under the past year.
And the camera API problems can only be fixed by OnePlus, if only they would.
Click to expand...
Click to collapse
Sorry if this is a lame question, but the "camera API" problem as you mentioned means anything related to end user/ day-to-day camera usages? or this is more of a developer's headache? Simply asking if the camera will not work?

tushxda said:
Sorry if this is a lame question, but the "camera API" problem as you mentioned means anything related to end user/ day-to-day camera usages? or this is more of a developer's headache? Simply asking if the camera will not work?
Click to expand...
Click to collapse
Camera will work. I think stock LOS has alright camera. Sultan's camera work makes the quality match OP's camera software but it lacks features such as 1080p60 or 720p120. Not sure if you can get those features if you use 3rd party cameras or not. Paranoid Android uses a custom camera driver that they create that makes the quality really good, but I never used the ROM myself.