[Solved] Blue tint on RAW photos - Huawei P10 Lite Questions & Answers

I edited the build.prop to unlock RAW format but i cant explain this. Anyone can help me to find out what's wrong?
EDIT: Just swapped Red and Blue channel on Photoshop and it simply worked.
Here below my comparison of raw/stock camera details.

Raw vs JPEG

Ra2rd said:
I edited the build.prop to unlock RAW format but i cant explain this. Anyone can help me to find out what's wrong?
EDIT: Just swapped Red and Blue channel on Photoshop and it simply worked.
Here below my comparison of raw/stock camera details.
Click to expand...
Click to collapse
How you enable RAW format? Thanks

Ra2rd said:
I edited the build.prop to unlock RAW format but i cant explain this. Anyone can help me to find out what's wrong?
EDIT: Just swapped Red and Blue channel on Photoshop and it simply worked.
Here below my comparison of raw/stock camera details.
Click to expand...
Click to collapse
How did you swap the channels?

Related

Help creating booting.pgm

I have a rooted nst that I would like to customize the booting.pgm on. I thought I could do it by myself by just pasting a black and white image over the original booting.pgm but when i do that I just get a white screen on boot and no boot image at all. Any help would be greatly appreciated.
All the PGM files in the boot partition are 800 x 600 monochrome 8 bit bitmaps in the PGM format.
See: http://en.wikipedia.org/wiki/Portable_graymap
http://www.gimp.org/ can save images in this format.
They are actually upside-down landscape. The left side is near the "n" button.
awesome thanks for the tips. Can photoshop also save files in that format?
So i went ahead and tried to create one with photoshop and it didnt work and then I followed your instructions and used gimp and it worked perfect. Once again thanks for the help

Qualcomm assertive display plugin for lg g3

Flash the zip file from twrp....it will add few lines in build.prop and also add a file to etc folder.
I found it at nexus6 forum...so share it with you...one lg g3 user confirm it works.
use adaptive brightness to get maximum potential battery save!
Lot of people tried this mod and told that adaptive brightness works better and faster with assertive display, also in direct sunlight display is more visible.
****Don't forget to hit thanks if it's work for you..****
Um can you type the lines here and also add the file, got only temporary root, don't have twrp. Also this affects everything ? Games, pictures etc etc ?
massivebanana said:
Um can you type the lines here and also add the file, got only temporary root, don't have twrp. Also this affects everything ? Games, pictures etc etc ?
Click to expand...
Click to collapse
Here are the lines
# Assertive Display
ro.qcom.ad=1
ro.qcom.ad.calib.data=/system/etc/ad_calib.cfg
debug.sf.hw=1
And add the file from zip...to etc folder
massivebanana said:
Um can you type the lines here and also add the file, got only temporary root, don't have twrp. Also this affects everything ? Games, pictures etc etc ?
Click to expand...
Click to collapse
It will good for use adaptive brightness to get maximum potential battery save! Also adaptive brightness works better
Hello.. the ad_calib file. After moving it to etc folder any need to change permissions?
Hello. Please after flashing the file. The number 2 file. After movingit to etc folder should i change permissions?
princedede said:
Hello. Please after flashing the file. The number 2 file. After movingit to etc folder should i change permissions?
Click to expand...
Click to collapse
Yes you have to give proper permission....
anyone tried? and pls axplain installation, do we need to just flash both?
imamalemdar said:
anyone tried? and pls axplain installation, do we need to just flash both?
Click to expand...
Click to collapse
Just flash it
Anik49 said:
Just flash it
Click to expand...
Click to collapse
both and without any order right?
and do you really notice any big differences?
sorry for silly questions...
imamalemdar said:
both and without any order right?
and do you really notice any big differences?
sorry for silly questions...
Click to expand...
Click to collapse
Actually when i used it i found more vibrant screen....currently i am using fulmics 5.3 which also use assertive display plugin find both same...
Does this work at all without using auto brightness? I don't use that at all. I like to control where the brightness is set.
gonk24 said:
Does this work at all without using auto brightness? I don't use that at all. I like to control where the brightness is set.
Click to expand...
Click to collapse
Try it .....give us your result
Hey look do we just flash both files above ? Needs more explanation and what permissions do we have to give to it ? Only asking cause im not sure of permissions
kevinkehoe18 said:
Hey look do we just flash both files above ? Needs more explanation and what permissions do we have to give to it ? Only asking cause im not sure of permissions
Click to expand...
Click to collapse
I always thought it was rw-r-r
Anik49 said:
Try it .....give us your result
Click to expand...
Click to collapse
It's all flashed for now so we'll see. I'm already reminded of how I find auto brightness to be annoying. It's too dark when inside. I'm outside a lot during the day and keep brightness set at 70%. Inside at night I'll drop it to around 45%. Using auto set to 70% and being inside, the screen dims to what would be around 25% brightness. Too low, and I shouldn't have to set it above what's bright enough at the high end on manual.
So flash file no 1, wipe dalvik and cache, extract and place file no 2 in /etc?
And which permissions do I need to set?
Anik49 said:
Here are the lines
# Assertive Display
ro.qcom.ad=1
ro.qcom.ad.calib.data=/system/etc/ad_calib.cfg
debug.sf.hw=1
And add the file from zip...to etc folder
Click to expand...
Click to collapse
Bro....can u plz tell me how to add these lines in build.prop?? As i never did it before.....and on g3 d856 m still not able to get working twrp...so plz help me adding this lines in build.prop....n kindly some info about the permissions for ad_calib.cfg? Screenshots or video will be more efficient...
Panther.zr14 said:
Bro....can u plz tell me how to add these lines in build.prop?? As i never did it before.....and on g3 d856 m still not able to get working twrp...so plz help me adding this lines in build.prop....n kindly some info about the permissions for ad_calib.cfg? Screenshots or video will be more efficient...
Click to expand...
Click to collapse
you need root to add this line in your build.prop. have you rooted your phone?
Anik49 said:
you need root to add this line in your build.prop. have you rooted your phone?
Click to expand...
Click to collapse
Yes..but temporary with kingroot...

Unlock Hidden Features in MIUI 8 Camera [Kenzo][MM]

Prerequisites
1. Rooted Device
2. TWRP Recovery
3. APK Editor
4. Any File Explorer with root access
5. Camera2 API
Procedure
1. Open file explorer and go to "/system/app/miuisystem" and copy the "miuisystem.apk" to phone memory
(Also make a backup of this file elsewhere)
2. Copy the downloaded "kenzo.xml" to phone memory
3. Install and open APK Editor then touch "Select an APK file" option
4. Select the "miuisystem.apk" from phone memory (From step 1) and choose "Simple Edit"
5. Navigate to "assets/device_features/" and locate "kenzo.xml", then touch the edit button on its right
6. Now select the "kenzo.xml" (From step 2) and touch the "Save" button on the right, then save the apk using "Save" button on the bottom
You will see a message, saying that the new apk was saved to "/storage/emulated/0/ApkEditor/tmp/gen.apk"​7. Open file explorer and go to "/storage/emulated/0/ApkEditor/tmp/" and rename "gen.apk" to "miuisystem.apk"
8. Move this "miuisystem.apk" to phone memory (For easy access from TWRP)(Optional)
9. Now reboot your device to TWRP recovery
10. Mount "system" partition
11. Open TWRP file explorer and navigate to "/system/app/miuisystem" and delete "miuisystem.apk"
12. Copy edited "miuisystem.apk" to "/system/app/miuisystem" and set CHMOD 755
13. Reboot your device and you'll see new options unlocked in camera
If it's taking too long to reboot it means that something went wrong (Good thing we have backed up the original miuisystem.apk). Boot into TWRP and restore the miuisystem.apk and repeat the steps carefully.​
Note
This method works for other devices running MIUI8 but you'll have to extract "youdevicename.xml" from "miuisystem.apk" and edit it yourself.
As always, I'm not responsible for damaged devices, do it at your own risk.
Have fun!
Bugs
1. Somehow the system timer (inside system clock) breaks. It doesn't sound the notification when timer runs out.
2. Exposure time setting in camera has no effect.
If anyone here can help me fix this, PM me.
Nice one bro
Sent from my Redmi Note 3 using Tapatalk
Hi, I can see this in your xml file:
<!--whether the device supports phone call noise suppression-->
<bool name="support_phone_call_noise_suppression">false</bool>
was it by default on false or did you change it?
This may help solving issue there is on Redmi phones, the noise cancellation get activated when recording video and this is causing awful result in the video file.
There are several bug report on miui forum about this, actually what we need is to disable "noise cancellation" for everything else but phone calls.
(you can see video that explain the issue on redmi 4, but redmi 2 and 3/3s... have this issue too...)
Do you have an idea?
ben770 said:
Hi, I can see this in your xml file:
<!--whether the device supports phone call noise suppression-->
<bool name="support_phone_call_noise_suppression">false</bool>
was it by default on false or did you change it?
This may help solving issue there is on Redmi phones, the noise cancellation get activated when recording video and this is causing awful result in the video file.
There are several bug report on miui forum about this, actually what we need is to disable "noise cancellation" for everything else but phone calls.
(you can see video that explain the issue on redmi 4, but redmi 2 and 3/3s... have this issue too...)
Do you have an idea?
Click to expand...
Click to collapse
It was "false" by default. Try making it true and check if the issue gets fixed.
it has any better options than snapdragon camera?
Oscilator said:
it has any better options than snapdragon camera?
Click to expand...
Click to collapse
Is SnapDragon Camera available for MIUI 8 Marshmallow?
oops I tried on miui now and it doesnt work
had in mind that ive used it on miu
thanks OP for doing this!
justinjoyn said:
Original XML
Click to expand...
Click to collapse
Hi Mate,
Vishal here.
Please attch the original XML please.
vdbhb59 said:
Hi Mate,
Vishal here.
Please attch the original XML please.
Click to expand...
Click to collapse
Here's the original XML for Kenzo
justinjoyn said:
Here's the original XML for Kenzo
Click to expand...
Click to collapse
<bool name="support_power_mode">false</bool> > change to true
<bool name="support_media_feedback">false</bool> > change to true
I searched. 4K support disconnects the notification outbursts somehow. BUG.
Try these values, but not too sure of its working.
vdbhb59 said:
<bool name="support_power_mode">false</bool> > change to true
<bool name="support_media_feedback">false</bool> > change to true
I searched. 4K support disconnects the notification outbursts somehow. BUG.
Try these values, but not too sure of its working.
Click to expand...
Click to collapse
This didn't change anything
justinjoyn said:
This didn't change anything
Click to expand...
Click to collapse
I too tried. Yes, did not change. I looked into the Boolean as well. Still nothing. I couldn't see it doing any astack calling. Does it call onto?
ben770 said:
Hi, I can see this in your xml file:
<!--whether the device supports phone call noise suppression-->
<bool name="support_phone_call_noise_suppression">false</bool>
was it by default on false or did you change it?
This may help solving issue there is on Redmi phones, the noise cancellation get activated when recording video and this is causing awful result in the video file.
There are several bug report on miui forum about this, actually what we need is to disable "noise cancellation" for everything else but phone calls.
(you can see video that explain the issue on redmi 4, but redmi 2 and 3/3s... have this issue too...)
Do you have an idea?
Click to expand...
Click to collapse
So did you try noise cancellation by editing miuisystem.apk file?

Regarding omnistyle theming

Hello I created custom header image to use with omnistyle. But I realised I need a full apk to get it work. There is no option in pure nexus ROM to use custom header image (my own image). So how do I create an app (like this https://play.google.com/store/apps/details?id=com.dirtyunicorns.headers&hl=en )for omnistyle? I tried googling but could not find an answer. I am not a developer but some guidance or template would help.
Hello, i don't know if you still need this? I can make a template for Android Studio with a little guide if this is still relevant.
PONYMODZ said:
Hello, i don't know if you still need this? I can make a template for Android Studio with a little guide if this is still relevant.
Click to expand...
Click to collapse
Do you happen to know where to go to change the OmniStyle QS image collection names? For example, I've replace all of the "Nature" images with pictures of sharks. That was easy enough and the new images show up and work, but the image collection in the list still says "Nature." I would like to change it to say "Sharks." I've dug through the OminStyle.apk up and down, but I can't find where those names are set. I see them in the AndroidManifest.xml, but changing the android:label in the androidmanifest.xml has no effect.
sharkie405 said:
Do you happen to know where to go to change the OmniStyle QS image collection names? For example, I've replace all of the "Nature" images with pictures of sharks. That was easy enough and the new images show up and work, but the image collection in the list still says "Nature." I would like to change it to say "Sharks." I've dug through the OminStyle.apk up and down, but I can't find where those names are set. I see them in the AndroidManifest.xml, but changing the android:label in the androidmanifest.xml has no effect.
Click to expand...
Click to collapse
The names are set in the androidmanifest.xml i have no clue why it does not work for you. But it would be easier if you just add your images with an apk or add them directly to the Omnistyle.apk if you need help with that just contact me.
PONYMODZ said:
The names are set in the androidmanifest.xml i have no clue why it does not work for you. But it would be easier if you just add your images with an apk or add them directly to the Omnistyle.apk if you need help with that just contact me.
Click to expand...
Click to collapse
I've already added my images to the OmniStyle.apk, and that works. I just want the image group text to say what the actual images are rather than whatever the text is by default.
I'd rather work it out in the thread, if that's alright. This way others can find it should they need it.
I'm about to go to bed now, but tomorrow I can upload the AndroidManifest.xml, or the APK I'm working with, if you want to have a look. Let me know how to proceed.
Thank you so much for being willing to help me out with this!
Sent from my moto g(6) using XDA Labs
So here's what I have so far:
- You can see in the attached screenshot (AndroidManifext-xml_Changes.png) that I've changed the text in the "android:lable" section of each activity.
- You can see in the attached screenshot (Screenshot_MiXplorer_20190612-122940.png) taken from the OmniStyle.apk on my phone that the AndroidManifest.xml is there on my phone with my new text changes.
- However, you can see in the attached screenshot (HeaderImageCollectionTitle-NoChange.png) that the changed labels did not actually change anything.
More Information:
- This is the OmniStyle.apk from the 6-4-19 release of the Havoc ROM for the Pixel 2 XL. I've also check this ROM's Setting.apk and SystemUI.apk in case the text was set there, but I don't see any reference to those words anywhere in Settings or SystemUI. The link to that ROM is: https://forum.xda-developers.com/pixel-2-xl/development/pie-havoc-os-t3851780
- Here's a link where you can download my already modded apk as well in case you wanted to have a look at it (It's too big to upload directly): https://drive.google.com/open?id=1N-ivQSa3In1LbD8LZ4QrVrzo1HAB0giT
Let me know what else you need, if anything.
@sharkie405
So i have checked the apk and the Androidmanifest.xml is correct but when i tested the apk, for me it wasn't working at all. I use the same ROM as you on my S7(herolte) and when i replace my apk with yours there it cant be loaded at all i just see my custom Headers, maybe it's an issue with your ROM or the apk itself. Try to update your ROM and edit the new apk again, but best would be to restore your Omnistyle.apk and make custom headers with the Android Studio Template from me, if you need help with it just ask

Camera pictures allways complette Green!

Hello people, I have a big Problem. The Stock camera is just making a Green Image. Yesterday i did take pictures from my bike Tour and now ever Thing is Green. In video-picture-focus mode
Apps like cameringo are not effectet. Dont know where the Problem should be.
I cleanen the Cache and everything.
This is the link to one pic https://picload.org/view/dggcdprw/img_20170908_163208.jpg.html
Did you change your DPI or Font-Size? Or did you mess with any kind of build.prop editor?
Do you have night mode one?
I didnt change anything. Thats why i Was so confussed about it.
just flashed the full 4.5.10 zip. Camera is now working again.
Dan3ll1 said:
Hello people, I have a big Problem. The Stock camera is just making a Green Image. Yesterday i did take pictures from my bike Tour and now ever Thing is Green. In video-picture-focus mode
Apps like cameringo are not effectet. Dont know where the Problem should be.
I cleanen the Cache and everything.
This is the link to one pic https://picload.org/view/dggcdprw/img_20170908_163208.jpg.html
Click to expand...
Click to collapse
I have seen this before on the HTC 10 the problem was actually because users had flashed a new ROM from a different base but had not updated their firmware.
See if this the case for yourself.
If your firmware doesn't match the base you're on then update it.
I dig this thread out because I have the same error again but this time i know why. Allways when i edit the build.prop and Reboot i cant take pictures because they are green. This time i tried to set the soundcontroll to 50 clicks for better adjustment. No big deal and no big change. And last time i tried to Set the Screen Resolution to 4k for YouTube vidz.
Question is why is the cam allways broke
Are you taking a picture of a green sheet?
worldsoutro said:
Are you taking a picture of a green sheet?
Click to expand...
Click to collapse
Damn bruh, that joke. U are one of the funny few?
But no i just take a Green sheet of a green picture....
why is everyone so negative? I know the solution. @Dan3ll1
you must be rooted
Go to play store and download ES File explorer
Give ES Root permissions
go into local device -> system
find build.prop tap and hold the icon
now click more in the bottom right, click properties, find permissions and click change then choose the following
Owner: Read, write, execute
Group: Read
Other: Read
Camera shouldn't take green pictures anymore.
OcazPrime said:
why is everyone so negative? I know the solution. @Dan3ll1
you must be rooted
Go to play store and download ES File explorer
Give ES Root permissions
go into local device -> system
find build.prop tap and hold the icon
now click more in the bottom right, click properties, find permissions and click change then choose the following
Owner: Read, write, execute
Group: Read
Other: Read
Camera shouldn't take green pictures anymore.
Click to expand...
Click to collapse
I will try this out. Phone is rooted twrp and magisk running. I will give a Feedback if it works
OcazPrime said:
why is everyone so negative? I know the solution. @Dan3ll1
you must be rooted
Go to play store and download ES File explorer
Give ES Root permissions
go into local device -> system
find build.prop tap and hold the icon
now click more in the bottom right, click properties, find permissions and click change then choose the following
Owner: Read, write, execute
Group: Read
Other: Read
Camera shouldn't take green pictures anymore.
Click to expand...
Click to collapse
Nope, did not work. Still green when i edit the build.prop
Dan3ll1 said:
I will try this out. Phone is rooted twrp and magisk running. I will give a Feedback if it works
Click to expand...
Click to collapse
U edited it? If you did youre doing it wrong. Just change permissions
OcazPrime said:
U edited it? If you did youre doing it wrong. Just change permissions
Click to expand...
Click to collapse
Not much to do wrong. I did change the permission. Reboot - edit build.prop - Reboot - camera broke
Flashed full zip - magisk - twrp
Set permission - edit build.prop - Reboot - camera broke - green pic
Dan3ll1 said:
Not much to do wrong. I did change the permission. Reboot - edit build.prop - Reboot - camera broke
Flashed full zip - magisk - twrp
Set permission - edit build.prop - Reboot - camera broke - green pic
Click to expand...
Click to collapse
What room are you on?
OcazPrime said:
What room are you on?
Click to expand...
Click to collapse
I am on OOS 4.5.13 with Franco Kernel
Dan3ll1 said:
I am on OOS 4.5.13 with Franco Kernel
Click to expand...
Click to collapse
Maybe just use the google camera. Its pretty good.
OcazPrime said:
Maybe just use the google camera. Its pretty good.
Click to expand...
Click to collapse
I tried a few other camera Apps. All have the same green picture, even WhatsApp and other Apps that use the camera are just taking green pictures.
Then i have to life with those soundsteps
Dan3ll1 said:
I tried a few other camera Apps. All have the same green picture, even WhatsApp and other Apps that use the camera are just taking green pictures.
Then i have to life with those soundsteps
Click to expand...
Click to collapse
Yikes. Maybe try clean flashing. Or going into twrp and trying the option Fix contents under the advanced tab.
Had the same problem.
Setting the build.prop permissions to 644 saved me.

Categories

Resources