On GCam Pink/Purple Distorted Photos Problem - Redmi Note 8 Guides, News, & Discussion

Many people complain about this and seems like few know about the issue. I should say that I'm not a dev, I just figured it out and tired of writing it after each complaint, which is why I write it as a new thread.
So, in short, there are ways in which gcam speaks with the camera. With RN8(t), we need the app use raw10 rather than raw_sensor for us to be able to have photos. This means that you need a version which either shoots with raw10 by default, or lets you switch from raw_sensor to raw10.
Sadly(?) there are not many that allows this, and almost all are version 6.x ones except Nikita's. The modders I found that allow switch or use raw10 are Nikita, overwhelmer, fu24, wyroczen, and trCam of tigr. There can be others, these are just those that I found. and I did not try each and every one of them. So if you are suffering from this problem, go for these modders' versions.
I may add that I like to use Parrot043's mod, as its output is practically what I want, yet unfortunately it is not usable without raw_sensor. Like his/hers, Arnova8G2's, BSG's, and many others' mods don't (didnt?) work. Yet as they are making new builds every now and then, maybe they will include a switch later on.
I should note that neither of those that I tried can do (good) astrophoto - or it was the case for me. Also none of these managed to produce good shadows (shadows in both Photoshop sense, shadows as shadows, and the transitive area between blacks and whites). On the other hand, it can be a problem with my device as I have seen people shooting pretty fine photos with these - including, interestingly, astrophotos. I just try and wrote my experience. Do NOT rely solely on my experience. Go and try for yourselves. This is just a starting point for those of you that have the problem, not an ultimate guide.
About auxiliary cameras, I cannot say much as I had them working at some point (with a fix from PA devs, I forgot the name of the dev and the patch sadly, and with fu24's version), yet now again they are broken. Funny part is that Paranoid Android claims to have them all working from the start, and other than me, I saw no one complaining that wide and macro don't work. Probably something is broken with my mobile, which is why I cannot say much on the issue.
Of the custom ROMs, I have found only Paranoid Android allowing shooting with raw_sensor. It might be the case with some other ROMs, so you better go check it out for yourselves as well. I can confirm that Pixel Experience and LineageOS did not allow shooting with raw_sensor, but it can change as well. Everything, as we know, comes down to the devs. This is just my experience, and I do not test each and every ROM every other day.
I hope that this will be useful for you, and there won't be complaints about pink/purple lines. This is because of GCam, not ROM builders as such. You can, surely, "force" the ROM builders to include raw_sensor shooting, yet it's up/down to them to do it or not.
So, I hope that this will help you to have a better idea about the problem, and you can solve it easily/easier.

Related

Build camera/camcorder/video for eclair/froyo.

I need a straight answer as it's possibly the one thing I can't figure out.
For eclair, NCommander fixed camera, but camcorder and video were broken from a straight build from AOSP.
CM later fixed these, but I never quite figured out how. Then everybody else started getting the camera fixed on their roms (by pulling a couple libs, I assume), but I myself couldn't figure out how the heck it was done, where an alternate source was available, or even an explanation of exactly what was broken/how it was fixed, etc. Same went for video playback/hw acceleration.
Now, on froyo, camera is broken again and NCommander's camera won't work either. It's been fixed by other people, but when I ask around, there seems to get a reluctance and I never really get an answer (and don't give me the "you're not asking the right question" line, I'm being pretty straightforward).
I need somebody here who has some knowledge as to why/how camera/hw is not working and how to fix it. I don't need libs. I need to know how to get the thing built from AOSP, why it breaks, and what I should look out for in the future, should it break again.
As far as I can tell, the problem is that the qcomm proprietary parts are outdated (for dream, last were 1.6 and eclair/froyo break compatibility with those libraries). Those libraries have to be linked-to at compile time of other hardware-libs and without the correct library, it won't build right.
What I don't get is: 1. which parts are missing, 2. where are people getting them from, 3. how do you add them to AOSP (other than PRODUCT_COPY_FILES) to get camera and all hw working right (including 3d acceleration).
Or maybe the project aurora community is better able/willing to help...
Bump. Totally interested. If OP already got an answer, please share.
Jubeh sorry I can't help you out I'm not a dev or a chef so I can't really give you any help. But I am interested in how your progress is going with this rom?
I found two sources for hardware files for the msm7k on our phones, including the camera and hw3d driver for dream. Also, building camera for AOSP seems to be fixed now. I'm just waiting from my battery to get here so that I can test. ebay parts from hong kong take forever.

Haw can I use Chroma Dialer on Stock 5.1.1?

I have used Chroma in the past with minimal issues, but prefer the pure stock over a rom - so my question is; is there any way to use the Chroma Rom Dialer on the stock 5.1.1? (since I know there's several telephony, dialer, phonesky apps/files) I am not sure how I would go about doing that, or what all I would need to change in order to pull it off - if this is even possible at all?
Reason for my question, I like that it has BUILT IN native call blocking ability that the stock dialer doesn't, other than THAT feature it's identical to the stock dialer. I don't care if it's the Chroma dialer, or another rom dialer, I just want the STOCK dialer (or stock-like) to have this ability.
I know there's 3rd party apps for this type of thing, and I've used many of them, but I very much so prefer NOT to have to use a 3rd party app for something that (IMO) should have been built in to begin with.
If you wish to know why this is important to me, read the spoiler:
So, I get ~3-6 calls every day that's just the same BS; Scam calls saying I can lower my CC interest rates and to press 1 to speak to a representative. They always call from a different number, so blocking them individually doesn't work since it's never the same twice (typically - you'll understand after reading below). If you DO press 1 you get a rude person who will cuss at you, call you names, or laugh at you if you ask to be removed from their calling list. Doing that will only make it worse. I've recorded dozens of calls where they say really effed up things to me. Beyond harassment, it's straight up abuse.
I have been getting them for years, I DO NOT own a credit card, never have owned one, and have never even applied for one - plus there's THOUSANDS of pages on Google about these type of calls being a major problem. Even the FCC has a $50,000 bounty for anyone who can legally or illegally stop them - no questions asked (how badass is that!?) - THAT should tell you how hard they are to catch, find, or stop.
After more than 2 years of filing formal complaints/reports with the FCC, Local PD, FBI (as told to by the FCC), USCC, and have seeked legal advice from my lawyer as to getting this stopped via getting a subpoena so uscc has to release the real call origin trace, I'm on the Do Not Call list... - I've been met with ONE solution that has been common on all counts; change my number. That's not really an option, I've had this number since 1997, I'm not about to change it for obvious reasons.
Now, I've tried many apps to get this stopped, ranging from free to paid, and have not found one that ACTUALLY works toward getting it stopped, many are difficult to use or require WAY too much effort and personal information in order to do anything but ask you to donate.
So far I have logged (through Google Voice VM) a growing total of 566 *different* numbers they have called me from - from all over the US and some that are unused anywhere on earth.
In conclusion, Ive logged 566 different numbers that have called me a total of 11,925 times since 2008.
If that isn't justification for this request, then IDK what is. Shy of ditching my phone altogether, I'm out of ideas.
Bumping - I'd really appreciate any help, gents.
iRub1Out said:
Bumping - I'd really appreciate any help, gents.
Click to expand...
Click to collapse
Have no idea. If dialer would work would need boh contacts and dialer apk. Have no idea where the code for that mod is and if ASOP dialer will even work on stock. Then you have odex vs deodex to work through.
If it CANT work on stock (which, honestly, I didn't expect it to) given, as you said, the differences are small on the surface but in the actual build they're very different. I understand that, and those are things I considered leading me to wonder.
Can anyone MAKE the stock dialer with that mod added in, or a otherwise stock rom with that?
It seems like a lot to request, I know, but I've been looking for this for months, I've even set up a bounty in a thread on TUSCC, its something that I've really hoped would become a mod thru xposed or "Pure Shamu" rom with it. However, it seems that others don't experience this ridiculous problem, leading to it not being as popular as I wish it was.
Trying to stop an ex from calling is one thing, but trying to stop every call that isn't a contact, I realize that's quite another. Thus is my case, its crazy how many spoofed numbers they use. I'm more amazed that the carrier hasn't done something than I am that it's not a mod. There's tens of thousands of people with this problem and the one solution that requires no effort on the end user isn't available to cell phone users.
I don't know - I'm just at my wits end with these calls. I'd be happy to do it myself if a dev is willing to give me some direction, or ideas to try out.
As a side note, I've recorded several where I just screw with them for as long as I can - then put it on YT after they realize they've been trolled and blow up. It's a small, yet, satisfying "middle finger" I can do.
iRub1Out said:
If it CANT work on stock (which, honestly, I didn't expect it to) given, as you said, the differences are small on the surface but in the actual build they're very different. I understand that, and those are things I considered leading me to wonder.
Can anyone MAKE the stock dialer with that mod added in, or a otherwise stock rom with that?
It seems like a lot to request, I know, but I've been looking for this for months, I've even set up a bounty in a thread on TUSCC, its something that I've really hoped would become a mod thru xposed or "Pure Shamu" rom with it. However, it seems that others don't experience this ridiculous problem, leading to it not being as popular as I wish it was.
Trying to stop an ex from calling is one thing, but trying to stop every call that isn't a contact, I realize that's quite another. Thus is my case, its crazy how many spoofed numbers they use. I'm more amazed that the carrier hasn't done something than I am that it's not a mod. There's tens of thousands of people with this problem and the one solution that requires no effort on the end user isn't available to cell phone users.
I don't know - I'm just at my wits end with these calls. I'd be happy to do it myself if a dev is willing to give me some direction, or ideas to try out.
Click to expand...
Click to collapse
If I knew what the mod is it would be possible to port to stock. My guess it is in smali which cannot access on stock odex. Stock Would have to be deodexed to access smali which is also possible in rom form. Nobody I know of is deodexing stock 5.1.1 We have done it and got it working but don't post as we still don't know if everything works. Lollipop is still hard to make fully working rom from stock image. M is even going to be harder. Would still need the code required to enable the mod.
prdog1 said:
If I knew what the mod is it would be possible to port to stock. My guess it is in smali which cannot access on stock odex. Stock Would have to be deodexed to access smali which is also possible in rom form. Nobody I know of is deodexing stock 5.1.1 We have done it and got it working but don't post as we still don't know if everything works. Lollipop is still hard to make fully working rom from stock image. M is even going to be harder. Would still need the code required to enable the mod.
Click to expand...
Click to collapse
I concurr, your talking about taking apk's not meant for a certain rom and adding them in to pray it works. Did you look in the market t.o see if there was a KB you liked there? You can't just switch around apk's like that because you could easily get force closes. If you want to try just copy and paste it into a rom. you wont brick doing that, it may work
I know it isn't as easy as swapping apks - I had *hoped* it would be similarly easy, but figured there was no way.
Idk what the mod is, or how Chroma did it - but the dialer looks stock other than the addition of that option under the advanced menu in the dialer settings.
I've looked in the market, used many of them, Mr. Number was my go to for a long time but it is iffy on 5.1 as *sometimes* a call will get through for a couple rings then gets blocked. It would also block known contacts on a rare occasion, I would go a couple days without knowing I had missed a call from a family member because it didn't show up in Mr. Number or the stock dialer - somehow it blocked it and had no record of the call even coming in.
That's why I was hoping to find a way to get this option in the stock dialer - without porting anything or swapping apks, that way it's a native feature to the dialer and I wouldn't have to depend on 3rd party apps to do it.
I've asked Google, but their solution was to add them to one contact and send the calls to VM - while that essentially works, that means I'd have to add all 500+ numbers to a single contact, and they OFTEN call from spoofed numbers I've never seen before - so that really doesn't solve anything.

[sultanxda]camera port to cm13 - please

WHOEVER AGREES TO THE POST BELLOW PLEASE LEAVE A COMMENT TO SHOW SUPPORT FOR THE CAMERA PORT
Hello, there Sultanxda
I'm posting this post?with the hope that you'll see what I have to say.
First of all, congrats on the work you done on CM*13 and Lineage *14. Congrats on the touches you added to both.
I love the stability, the battery life on your CM*13, BUT, your camera, or CM'S camera user interface, I just dont think its that much USER FRIENDLY as OOS camera is. I have tried so many ways to get that camera ported onto this ROM and withkut success and I'm sure others have tried it too.
Through this post I am requesting a port file or an update which provides both cameras and let us choose which one we use, or use both in diff situations.
Look, man I get it, you've put work in the camera, BUT the user interface. Please allow us to use OOS camera with no issues.
I'm sure other people would appreciate it too if you would do that. That way your ROM would be the best ROK there is for OnePlus3T. The reason I left your rom ia because of the camera. The camera is one of the most important things in my phone since i capture moments, and I there are moments that I want to capture on the spot, quick and easy, moments when I want to take a quick video and by the time I bring up the video feature its too late, the moment is gone. I hope that you can underatand me of why I want the OOS camera on your rom.
WHOEVER AGREES TO THE POST BELLOW PLEASE LEAVE A COMMENT TO SHOW SUPPORT FOR THE CAMERA PORT

[HELP] What about RAW shooting?

Hello there everybody,
I recently purchased a brand new Huawei P8 Lite 2017 (also known as P9 lite 2017, Honor 8 lite etc. in some countries) and I was really happy to get one at almost 140$. I also bought it since everyone on the net was praising the excellent camera for this phone range. I was super-happy when I also stated that it was supporting camera2api; which means I can take RAW/DNG photos with the stock camera app or other proper applications.
Unfortunately, something was wrong: even if the phone can actually take RAW photos with apps such like OpenCamera and stuff, the result is not what I (and probably everybody else) was expecting. The files are kind of missing a color channel (red one, I think), which makes the photos almost useless, since the saturation is messed up and I can't even fix it with heavy Lightroom editing. I just don't understand why it behaves like that. Am I missing anything?
Or does a hidden RAW enable feature exist like in the P9 lite and must it be unlocked by file editing ?(https://www.xda-developers.com/guide-enables-raw-capture-in-the-stock-huawei-p9-lite-camera).
Is there a custom ROM that can actually implement this feature or will it ever be one?
Thanks for the answers.
Did you solve this? I have the same problem probably. From what I could gather the red and blue channels come out swapped. So I just made a preset in photoshop using the channel mixer. Even so the images still have to be heavily adjusted, retouched around the center and they're softer around the edges.
I didn't see many people complaining online and your thread has no answers, so I though to maybe leave this information here. It's weird that the stock camera app works well, but I'm still in warranty so lets see what huawei can do about this.

Telelens camera/4k60fps - AOSP ROM

Hi guys,
I just bought this phone and tried some custom rom, and it works perfectly!
I have just a couple of questions about the camera,
How can I know if, for example, the google camera port is using the telelens instead the main camera?
I just love to have the pixel experience on my mi8 but, I want also to be able to use all the cameras in my phone. I also searched the 4k60fps option in google camera or im ANXCamera but the maximum setting is 4k30fps.
I tried to learn something more in some thread and i found that many people talks about the impossible to access the second camera through the api2.
I'm honest, I don't have the knowledge to understand all that, so I'm asking you, did you know some guide that can help me out?
I just want to know if with an aosp rom is possibile to access the full potential of mi8 camera, nothing else. I wish I could use some google experience instead the miui but with a complete camera app.
Thank you
Thomas

Categories

Resources