Develop Bugs

[Q] cyanogen mod on S4. Camera photo quality downgraded?

Well I'm gonna get straight to the point. Cyanogenmod has downgraded the camera on my Galaxy S4. Photos are significantly noisier and overall lacking in the photo department. I went to Best buy to compare a stock S4 to my CyanogenMod S4 and right there and then my worries were confirmed. Is there any way to keep cyanogen mod and get back the awesome camera quality of the stock S4? The camera downgrade is really getting on my last nerve.
It was the CyanogenMod installed through the play store BTW..

You got a few options
1) ditch CM all together, and use a GPE rom. This is AOSP built by samsung and google. It does not have any of the issues CM has.
now.. some "RDs" on this site insist that the GPE edition roms are TW based, simply because they use the same kernels - this is not true. An adroid 4.3 kernel will work on a 4.3 rom, be it touchwiz, or aosp, and same with Android 4.4
I personally run VirginROM 2.5.4 with a custom kernel that is not allowed on XDA, and my stability is 100%, battery life lasts about 2 or so day with moderate use, and audio/video (what there kernels are known for) rock. These kernels do not overclock, but excel over others that do overclock when it comes to performance.
2) compile the focal camera app yourself and deal with all the CM issues, flaws, and "hybrid" merges...
3) purchased/download a 3rd party app from the google play store

shadowcandy said:
Well I'm gonna get straight to the point. Cyanogenmod has downgraded the camera on my Galaxy S4. Photos are significantly noisier and overall lacking in the photo department. I went to Best buy to compare a stock S4 to my CyanogenMod S4 and right there and then my worries were confirmed. Is there any way to keep cyanogen mod and get back the awesome camera quality of the stock S4? The camera downgrade is really getting on my last nerve.
It was the CyanogenMod installed through the play store BTW..
Click to expand...
Click to collapse
First off, no kidding. This did not need a new thread to be discussed. There are literally a thousand posts abotu camera quality with CM ROMS on the various S4 variant forums. Any search at all would have shown you the answer. Here's an example with posts from less than a week ago that explains this throughly.
Second, if this gets on your last nerve, get rid of CM and return to stock. This is the price of using CM. The camera isn't as good. Complaining about it and acting like CM owes you a better camera is downright rude to the CM team who gives you their ROM for free out of a desire to give a gift to the world. They don't owe you a thing.
The short version to your question abotu getting the CM camera back is simply no.
The long version is...
The issue with the camera in AOSP ROMS is that the stock TouchWiz camera has all kinds of proprietary software driving it. That software is built into different parts of the rom and absolutely requires the TouchWiz framework to run. (Which is also proprietary). You can't just pull the APK out of TouchWiz and install it on AOSP.
So there is no way to get the stock TW camera to run on any AOSP rom.
This means that any other app that is using the camera is using generic software to run the camera hardware. This leaves out the ability to do things that the TW software was specifically written to do like crisp auto focus and color depth and all those goodies that make the TW camera better. All that software was written specificly for the S4 hardware.
The Cyanogen camera or the Google stock camera is just an app using generic software not written specificly for this phone's camera hardware. That's no different than ANY other camera you can find on Google Play. They are ALL using generic software.
As a result, none of them are every going to be as crisp as the TouchWiz camera software. They almost all still take a really good picture with this phone, and many give various effects you might enjoy, but if you are looking the actual stock camera app that takes a higher resolution, better focused picture than the CM camera, you're not going to be able to do it.
Even with all that, the S4 camera hardware with CM camera software It's still better than most other phones on the market.
At the end of the day, it's not a camera that makes phone calls. It's a phone that has a camera in it. If photography is that big of a deal to you, you're never going to be happy with anything other than a true SLR. There's nothing wrong with that, mind you. But please stop complaining about the quality of the free ROM that har dworking developers put together in their spare time and gave to you as a gift with no questions or strings atatched.

Well Said !!
I appreciate the way you explained. :good:
Skipjacks said:
First off, no kidding. This did not need a new thread to be discussed. There are literally a thousand posts abotu camera quality with CM ROMS on the various S4 variant forums. Any search at all would have shown you the answer. Here's an example with posts from less than a week ago that explains this throughly.
Second, if this gets on your last nerve, get rid of CM and return to stock. This is the price of using CM. The camera isn't as good. Complaining about it and acting like CM owes you a better camera is downright rude to the CM team who gives you their ROM for free out of a desire to give a gift to the world. They don't owe you a thing.
The short version to your question abotu getting the CM camera back is simply no.
The long version is...
The issue with the camera in AOSP ROMS is that the stock TouchWiz camera has all kinds of proprietary software driving it. That software is built into different parts of the rom and absolutely requires the TouchWiz framework to run. (Which is also proprietary). You can't just pull the APK out of TouchWiz and install it on AOSP.
So there is no way to get the stock TW camera to run on any AOSP rom.
This means that any other app that is using the camera is using generic software to run the camera hardware. This leaves out the ability to do things that the TW software was specifically written to do like crisp auto focus and color depth and all those goodies that make the TW camera better. All that software was written specificly for the S4 hardware.
The Cyanogen camera or the Google stock camera is just an app using generic software not written specificly for this phone's camera hardware. That's no different than ANY other camera you can find on Google Play. They are ALL using generic software.
As a result, none of them are every going to be as crisp as the TouchWiz camera software. They almost all still take a really good picture with this phone, and many give various effects you might enjoy, but if you are looking the actual stock camera app that takes a higher resolution, better focused picture than the CM camera, you're not going to be able to do it.
Even with all that, the S4 camera hardware with CM camera software It's still better than most other phones on the market.
At the end of the day, it's not a camera that makes phone calls. It's a phone that has a camera in it. If photography is that big of a deal to you, you're never going to be happy with anything other than a true SLR. There's nothing wrong with that, mind you. But please stop complaining about the quality of the free ROM that har dworking developers put together in their spare time and gave to you as a gift with no questions or strings atatched.
Click to expand...
Click to collapse

AOSP roms for G3 - how stable will they be?

I have asked this question elsewhere but didn't get an answer so I'm trying here.
I've had 3 generations of Samsungs and I really want to switch to something different, possibly the LG G3. What would really convince me is if I could reasonably anticipate a rock solid AOSP ROM for it at some point in the future. I'm sick of Samsungs bulky and laggy Touchwiz, and I've fallen in love with the pure Google experience that AOSP roms offer; but while they work OK on the Samsung, they suffer from a drop in quality and performance because I am told Samsung drivers are not open source and they have to use open source alternatives.
I've noticed that LG have an open source code distribution page with software for phones on it. Now I'm no developer, so the question I am asking is - do LG release their code open source? And does this mean that original developers are able to drive the LG hardware properly? What were AOSP roms like for the G2?

astralbee said:
I have asked this question elsewhere but didn't get an answer so I'm trying here.
I've had 3 generations of Samsungs and I really want to switch to something different, possibly the LG G3. What would really convince me is if I could reasonably anticipate a rock solid AOSP ROM for it at some point in the future. I'm sick of Samsungs bulky and laggy Touchwiz, and I've fallen in love with the pure Google experience that AOSP roms offer; but while they work OK on the Samsung, they suffer from a drop in quality and performance because I am told Samsung drivers are not open source and they have to use open source alternatives.
I've noticed that LG have an open source code distribution page with software for phones on it. Now I'm no developer, so the question I am asking is - do LG release their code open source? And does this mean that original developers are able to drive the LG hardware properly? What were AOSP roms like for the G2?
Click to expand...
Click to collapse
the aosp builds for the g2 are pretty stable..it only took them a few weeks to sort them out but i just wish they offered a google edition like many companies are doing with their devices like the m8..s5..etc

hello00 said:
the aosp builds for the g2 are pretty stable..it only took them a few weeks to sort them out but i just wish they offered a google edition like many companies are doing with their devices like the m8..s5..etc
Click to expand...
Click to collapse
Thanks for the reply. I found one or two aosp builds for my Galaxy S3 that I would describe as 'stable' in that they don't crash or lock up - but the audio quality using an open source driver is noticeably poorer, and that affects using the phone, audio messages, music playback, and video recording/playback - to the point that it just wasn't acceptable to me. My camera would always crash on aosp roms too.
So I'm still interested to know if original developers have access to the source code for for the G3 hardware - because if I'm paying for a 13mp laser guided camera, I want it to still function as it should under any rom I put on it!

astralbee said:
Thanks for the reply. I found one or two aosp builds for my Galaxy S3 that I would describe as 'stable' in that they don't crash or lock up - but the audio quality using an open source driver is noticeably poorer, and that affects using the phone, audio messages, music playback, and video recording/playback - to the point that it just wasn't acceptable to me. My camera would always crash on aosp roms too.
So I'm still interested to know if original developers have access to the source code for for the G3 hardware - because if I'm paying for a 13mp laser guided camera, I want it to still function as it should under any rom I put on it!
Click to expand...
Click to collapse
I was also wondering about this. On the Htc one xl the aosp camera was significantly worse than the sense one.
Is there any way to know if when the g3 gets aosp there will be any driver issues? The g3 on paper seems absolutely fantastic but the possibility of no aosp or aosp with less functionality is terrifying to me.

I wish there was a GPE version of the G3.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

astralbee said:
Thanks for the reply. I found one or two aosp builds for my Galaxy S3 that I would describe as 'stable' in that they don't crash or lock up - but the audio quality using an open source driver is noticeably poorer, and that affects using the phone, audio messages, music playback, and video recording/playback - to the point that it just wasn't acceptable to me. My camera would always crash on aosp roms too.
So I'm still interested to know if original developers have access to the source code for for the G3 hardware - because if I'm paying for a 13mp laser guided camera, I want it to still function as it should under any rom I put on it!
Click to expand...
Click to collapse
I THINK a lot of code is shared from these manufacturers but camera stuff may not be on that list . Just got the LG G3 yesterday and i don't like it at all besides the camera , finding it kinda laggy in comparison to N5 ( if u use the resents button a lot u'll notice ) and its not the same build quality as my G2 , feels cheaper to me . I'm a fan of AOSP, all my devices have some form of it, this G3 may be going back to the store for a new M8 its pretty easy convert to full GPE . and i love my M7

hello00 said:
the aosp builds for the g2 are pretty stable..it only took them a few weeks to sort them out but i just wish they offered a google edition like many companies are doing with their devices like the m8..s5..etc
Click to expand...
Click to collapse
Where can I download the AOSP builds for g3? If they don't exist, where will I go to find them when they do exist?
Thanks!

distancesprinter said:
Where can I download the AOSP builds for g3? If they don't exist, where will I go to find them when they do exist?
Thanks!
Click to expand...
Click to collapse
They don't exist yet. From what I understand the boot loader hasn't even been unlocked yet. I guess there are people working on it tho. As far as where you can find the builds, they'll be here on XDA, either in the Android Development section of this G3 forum, or in the carrier specific G3 sections (which have yet to be created).
Never mind, I guess they just created the carrier threads.....

CM 13 vs. Marshmallow

Like in the topic, which is better? CM have better performance but marshmallow is better cuz it have dual window, qslide etc.
I dont know :/ write advantages and defects of both, PLEASE!
Sent from my LG-H815 using Tapatalk

CM13 IS Marshmallow you i... also, CM13 has multiwindow too. None of them has "defects". They both work great. They work so great infact that it's no longer a question of functionality but rather a question of preference.

patryk.kecik said:
Like in the topic, which is better? CM have better performance but marshmallow is better cuz it have dual window, qslide etc.
I dont know :/ write advantages and defects of both, PLEASE!
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
You mean CM vs LG Stock? Currently stock. CM13 still has a lot of bugs + way worse camera (in terms of functions)

davebugyi said:
You mean CM vs LG Stock? Currently stock. CM13 still has a lot of bugs + way worse camera (in terms of functions)
Click to expand...
Click to collapse
Except, it doesn't have "a lot of bugs". It has "some" bugs, most of which you won't even notice, as any ROM out there has, even official OEM ones. The camera is a non-issue as you can easily find apps in the Play Store that have even more functionality than LG's stock camera app.

nitrous² said:
Except, it doesn't have "a lot of bugs". It has "some" bugs, most of which you won't even notice, as any ROM out there has, even official OEM ones. The camera is a non-issue as you can easily find apps in the Play Store that have even more functionality than LG's stock camera app.
Click to expand...
Click to collapse
Well I tried it a week ago exactly. That build had more than just "some bugs". App wise you are right, there is Proshot and Camera FV-5. But you mean CM13 now also has a working laser focus, spectrum sensor and long exposure for the camera?

What about qslide? Is it available on cm 13? And which camera app is better than lg stock camera or cm13 camera? And what about lg apps? I mean calendar, smart notice, quick remote. Its important for me.
Sent from my LG-H815 using Tapatalk

I you don't care about camera quality: CM13 all the way. But if you care, forget CM13. Camera it's just horrible. Photos with horrible quality, not so many options, strange ratio, etc.
I've tried CM13 one day after use stock MM for almost a month (the seven version) and returned to stock because camera.

I completely agree. CM 13 is an amazing project but I think that is a little bit unfair put a young project devolped by a guy or two VS the stock one that starts from completely different conditions.
At this stage of development there is no contest simply because CM 13 has a lot of bugs and no real optimizations focused on G4 only.
All that said what I hope is to have in the future someone that works on a custom kernel cause what I see in the past is that custom ROM works perfectly only on Nexus devices but custom kernel could really improve stock experience in terms of fluidity and battery life without losing features that comes only with stock ROM (e.g. camera or dual window).

I would have 5.1 or Android 6.0 over CM 13 any day. I use quick circle case so dont want to lose awesome feature to give up
Sent from my LG-H815 using Tapatalk

How does having the released mi5s kernel help in the camera department?

Hi.
I'm using EU MIUI 7.3.30 and it's not bad, but I would much prefer using a non-MIUI ROM such a LineageOS.
However, all the AOSP variants using the stock kernel (LOS,RR...) until now have had mediocre to faulty camera implementations and I've tested many camera apps at that - Piximod mark IV, stock LOS, stock RR, Google camera, a better camera, open camera, manual camera... None of them are able to hold a candle to the stock camera app under MIUI in terms of having everything (video,RAW,HDR,panorama...) working flawlessly under one app.
I'm not even sure if this will change now that we have the released kernel for the mi5s, so please help me understand the following:
1. Does having the released kernel potentially help in getting a better camera experience under LOS, RR or a similar ROM versus using the stock kernel from MIUI? How so?
2. Does having the released kernel potentially help in porting the stock MIUI camera app under LOS/RR?
3. Does having the released kernel potentially help in getting a *better* camera implementation than currently under stock camera app MIUI by better utilizing the camera2API (from my understanding the stock camera app in MIUI doesn't use V2 of the camera API)?
4. Does having the released kernel potentially allow one to port the Pixel camera app?
Thanks all

I think you should create this thread into the Question & Answer Section.
But for your question regarding the kernels and implementation for los / rr, yes indeed it'll help for dev to use new released kernel from xiaomi, since the kernel is made specifically for mi5s hardware optimization and function.
Yes and yes, the bottom line is the kernel will give us huge advantage rather than use stock kernel like we use right now if we use los / rr, for the camera of course there will be some improvements, not only the camera, fingerprint, ambient display, multi touch, etc will improve.

As far as I understand the source doesnt contain every information.
Open source sounds cool yeah. But take Amazons FireTV as an example. There is a source code available because of GPL, however they only share the source of the stuff they have to share and nothing else. So source doesnt mean, the source code of everything.
As a better example you can take the Google Pixel. You would expect that the VERY Android device itself should have source code of everything available. Like the Google Camera Software and algorithm that could be used for the Mi5S since both share the same Sony Sensor. Sounds awesome right? Sadly Google, doesn't share this particular piece of source code/drivers.
And when I talked with LuK about source, he was not very optimistic. It is because the Qualcomm Fingerprint reader is also closed. Which is why he said "Qfp will still be a mess"
So.. Long story short. It will still be a custom rom with its disadvantages. But I believe that it will contribute a lot in terms of stability. Phone calling , no force closes and sudden reboots.
I mean after all these years on xda , everyone should already got used to "everything works. Stable build. not working : camera etc"
This will not change I think. In fact it will get more complicated and the list of troublesome things will get longer as phones get more and more features with closed source. Fingerprint reader is such a thing for instance. and More advanced sensors in the future etc..
So there are two options:
1) Either you stick with your current phone and try to make it work and live with its downsides. Maybe after 3 to 5 years, almost everything will be supported or maybe not. Although by then the phone will most likely be obsolete and any 100$ phone will beat it.
Go back 5 years. Would you still bother with a Samsung Galaxy S2 or S3?
2) Just get a phone that has proper company support from the start and use the phone at its full potential right away. Like the Google Pixel. However it costs more. So you have to weigh the Pros and Cons. Do you want to spend more money or more time and headaches. Everyone has to make a decision there.
As for me: I know that I drop and break expensive stuff. So I buy cheap phones. xD

Question Custom rom is same camera quality with stock?

Can someone tell me a rom with the same image quality as the stock rom? I'm using deepfest and the photos are really bad

I find google camera works well with lineage os, same as stock. Battery life isn't great for me though
Info about raven | LineageOS Wiki
wiki.lineageos.org

hoanganhltv98 said:
Can someone tell me a rom with the same image quality as the stock rom? I'm using deepfest and the photos are really bad
Click to expand...
Click to collapse
It's hard to understand your description... Do you mean camera app or rom ?

I think that the camera works worse on custom firmware. unless of course you are not a specialist in photo / video, then you most likely will not notice the differences, but they are present.
It is better to install the camera from BSG and customize it for yourself. however, you can ask for a config file with settings

idark11 said:
I think that the camera works worse on custom firmware.
Click to expand...
Click to collapse
They most certainly work *precisely* the same. What you are experiencing is that you probably at one point heard about some (different) phone that truly DID degrade image quality when unlocking (I think Sony did that?), and have therefore gone looking for imperfections, which you have convinced yourself are present.
The reality is that the camera HAL is absolutely IDENTICAL on the factory system image and on AOSP, and the output of both will be absolutely identical in every way.

96carboard said:
They most certainly work *precisely* the same. What you are experiencing is that you probably at one point heard about some (different) phone that truly DID degrade image quality when unlocking (I think Sony did that?), and have therefore gone looking for imperfections, which you have convinced yourself are present.
The reality is that the camera HAL is absolutely IDENTICAL on the factory system image and on AOSP, and the output of both will be absolutely identical in every way.
Click to expand...
Click to collapse
then explain to me why on a custom ROM ricedroid lens not working x4?

96carboard said:
They most certainly work *precisely* the same. What you are experiencing is that you probably at one point heard about some (different) phone that truly DID degrade image quality when unlocking (I think Sony did that?), and have therefore gone looking for imperfections, which you have convinced yourself are present.
The reality is that the camera HAL is absolutely IDENTICAL on the factory system image and on AOSP, and the output of both will be absolutely identical in every way.
Click to expand...
Click to collapse
tell me why on a bone pzu evolution X stuck when changing camera?

@idark11 ; because they ****ed something up. Its easy to break things.
If you build a pure aosp system, it will work perfectly.

camera works better on hentaiOS