Related
If you are using the EVO based build, you can ignore this thread.
This fix is ONLY for Desire based build with EVO's Camera application.
PLEASE DO NOT USE THIS FIX IF YOU ARE USING THE EVO BASED BUILD.
First!!
After i fix the real 5MP capture in HTCCamera, i have also fix the Thunder Cloud Review window in HTCCamera today.
The fix APK is including the real 5MP fix and correct review window after you capture.
There is no more thunder & cloud strange picture again. You can also do some actions, like Share,Delete,Goto Media Gallery or Capture again.
What's the fix
1.fix the Thunder Cloud Review Window
2.fix the real 5MP
3.fix the Shutter Sound , if you use my old file, please download it again(Update @2010/11/07)
I have only test in Desire base, OTA 2.29
How to install it?
The APK CAN NOT INSTALL into your HD2 Android.
You have two way to install this fix.
Make sure your /system is Rear/Write not Read Only.
1. Putting the HTCCamera.apk into your HD2 SD Card using File Explorer with root access, copy the fixed HTCCamera.apk to /system/app and overwrite the original one, if you can find HTCCamera.odex in the /system/app, please delete it. In order to prevent the default shutter sound, you have delete(or rename) the camera_click.ogg in system. Go to /system/media/audio/ui and find out the camera_click.ogg, delete it or rename it.
I suggest you can use a Free root File Explorer called "Super Manager". The software you can search it on Market by "Super Manager" or "gpc". It is my design. It can help you move the fixed APK file into /system/app.
2. Using shell command
Code:
adb push HTCCamera.apk /system/app
adb shell rm /system/app/HTCCamera.odex
adb shell rm /system/media/audio/ui/camera_click.ogg
If you use it in your release build, CREDITS, thanks
How to use it?
First, you have using the last EVO-bases kernel and the attachment APK file.
After installing it, you just have to launch the Camera.
If you are lucky, you can enjoy the new real 5 Mega pixel camera without Thunder Cloud right now. You don't have to reset you HD2-Android.
Enjoy it!!
If the fix is helpful, you can donate to me. thanks
Awesome!
Thanks a lot. I've been looking for something like this for quite a while.
Oh yes !
Thanks a lot !
Thanks for your work. now fix HD recording
(i know its codec related)
i have tried this but it just disable review after photo taking, is it something wrong?
Worked like a charm for me. thanks.
I used Android Commander to copy the file, I tried using super manager like you said but it would copy the file incorrectly to 0.00k, weird.
Anyway works now.
Thanks man. Works great.
Great Job
Tested Work 100%
Thanks
Does this fix the widescreen picture at 5mpx resolution. I don't think so
Sent from my HTC HD2 using XDA App
Any one having this resolution with this?
2592*1944 (Real 5 Mega Pixel)
How is it possible?
I did as mentioned in the first post, cloud at preview has been successfully fixed, but I didn't get the real 5 mega pixel. I desire it!
Can some one please help me?
After replacing my Camera app I now have no camera app at all! I tried 3 or 4 times, downloaded the file twice and used 2 different root explorers, including the one suggested.
Anyone know what could be causing this?
I am using a Desire-based build for Tmo-US, and I upgraded the kernel to Hastarin r8 before attempting this.
EDIT: Nevermind, switched builds now fix is already applied
works for me!
Hiya, first a big thanks for this one, seems to work perfectly, getting full 5mp (2592 x 1944) res photo's without the cloud stuff, review window works well, seems to keep to the 5 second timeout i put in settings for it too.. replaced original file with android commander btw, just make sure u got usb debugging mode on for that to work
one more request though: could you also fix the setting for shutter sound? i've tried setting it off/on, but the sound remains on no matter what the setting says.. i don't know if that's kernel related (though i don't think so), so that would be really nice if u could fix that as well
working with darkstone froyostone 3.2 with hastarin r8 + letama's pppd wrapper v0.3 here
edit: been trying some more settings, and it seems that setting the camera to widescreen just stretches the photo to widescreen, the picture looks squashed compared to what u see in the viewfinder(screen) before u take the photo. doesn't seem to be the case for the 4:3 mode though, taking pictures there just gives nice unsquashed photos
Perfect !
Thank for your hard work !
But how to ZOOM ?!
djbarney said:
one more request though: could you also fix the setting for shutter sound? i've tried setting it off/on, but the sound remains on no matter what the setting says.. i don't know if that's kernel related (though i don't think so), so that would be really nice if u could fix that as well
Click to expand...
Click to collapse
Thanks for the work and I second the shutter sound request too.
noobshite said:
Thanks for the work and I second the shutter sound request too.
Click to expand...
Click to collapse
fix it now.
You can referrer to the first post
Can you help me? How can I have the real 5mpx camera with widescreen resolution as in the screenshots
Will next fix for Face detection?
shree.cse said:
Can you help me? How can I have the real 5mpx camera with widescreen resolution as in the screenshots
Click to expand...
Click to collapse
We don't have HTC customize camera library.
The camera library in your HD2 is based on Nexus One with some modify. It is impossible to fix the widescreen and face detection in HD2 HTC [email protected] without the HTC customize camera library for HD2.
I think it is very hard for us to get the camera library.
If we can get the HTC customize camera library source (NOT the current library with the open source,Nexus One), we can modify it to work in HD2.
However, how can we get the source code?
Maybe somebody can be a thief and steal the source code from HTC office
I remember 1 of the version from darkstone ROM, the camera face detection is working fine. But i can't recall which version is that.
iamgpc said:
We don't have HTC customize camera library.
The camera library in your HD2 is based on Nexus One with some modify. It is impossible to fix the widescreen and face detection in HD2 HTC [email protected] without the HTC customize camera library for HD2.
I think it is very hard for us to get the camera library.
If we can get the HTC customize camera library source (NOT the current library with the open source,Nexus One), we can modify it to work in HD2.
However, how can we get the source code?
Maybe somebody can be a thief and steal the source code from HTC office
Click to expand...
Click to collapse
Then what does this mean?
Fix: Real 5mpx
Sent from my HTC HD2 using XDA App
Hey guys,
recently I see many Wildfire Roms presenting itself with the "new" bravia engine. I sounded great - and I went straight for some research here on XDA. There are several threads about porting it to any device u want...
So I took the 2 files and modified the build.prop and went for happy testing - sadly my screenshots form before after didn't show ANY difference...
So I searched on...
Checked out several screenshots in all those treads and notice that most screenshots also don't show any difference... reading on....
Many people notcied the same so most time a great discussion in each thread started.
Some peeople mentioned I can't be screenshotted casue its postprocessing,...
Others tell it only works with sony screens,.. and some complain it slightly doesn't work.
So what is the truth about that?
1. Cant' be screenshotted imho is bull**** since the flow should be: data -> processing -> buffer -> screen and a screenshot is taking data out of the buffer normaly (even there are different techiques - but root screenshot programs should do that as far as I know)
2. Only with sony screens? Nope don't think so as its JUST postprocessing - nothig else...
3. Doesn't work - a hoax? Maybe
So I asked myself how all this is working a great review i found was this
He is mentioning that there are several things needed for getting be engine to work.
1. be_* files
2. build.prop editing
3. the SWIQI service
4. an edited Galery app (since the one he found was complaining about the missing files if he deleted em)
Wich sounded quite propper to me. As postprocessing noramly is done by an app or has to be included into the rendering engine of android totaly... but his research showed it seems to be the galery app. Even he also has some wallpaper stuff meanwhile but to me this seems more like the galery app rerenderes the photo and then sets this rerendered photo as wallpaper. Sadly he doesnt describe it...
Sadly I can't find ANY thread here on XDA wich also ports the swiqi service propper (and doesn't just edit the build.prop + the be_* files). The only source I found wich also included some swiqi*.jar was owain94 (wich is credited in last rempuzzle btw) but he also closed his thread for hoax reasons... So even this doesn't wokr as it seems.
EDIT: the SGS version also seems to be here
No offense guys - I appreciate all the work u do for us - but since I couldn't figure out any wokring veriosn of BE Engine Ports and I see more and more Roms including it - I just asked myself if we got a popper port now - or still just those file copy actions?
Maby the SGS port is really working but I didn't have time to figure it out yet - it seems to be dependent on the galery app wich makes it quite useless if u dont use the android galery but quickpic,...
Anyway as the credits in Wildpuzzle (to owain94) and High-Voltage (didn't find any) don't go to the SGS guy i asked myself if those are even wokring?
And if u got those old (hoaxed) version (wich even jamal is presenting here in buzz forum) u should consider testing the above mentioned
thx, and welcome. u r the lastest one who realized the flooding of fake bravia engines in many roms and you have found the working one now on the sgs2, sgs, etc
yes, after i found it's was a placebo, i looked into it and came out with the solution to make it happen, as well as wallpaper rendering with the bravia engine. but initially my mod was treated as another placebo by others who believe "it wont work on non sony devices". and sadly, this was the reason why my threads were all deleted....
anyway, in these mths, i kept telling ppl in many threads under different models about the bravia engine works on non sony devices, and probably all devices, provided that it is correctly implemented. luckly, i can see some positive results and feedbacks. but still, many are still talking about the file permission thing
on the other hand, however, i'm quite worry about the trends in xda now. ppl are going crazy to produce different roms by putting hittest mods to attract ppl to download them and perhaps to make some money. and in fact they do earn money
rather, only limited ppls are willing to continue to create new things or mods and this makes me sad. i've asked ppl to come and join the bravia engine mod as to port it to other devices but no one is interested in it. ppls prefer instant solutions now, unlike the days before where there were lots of developers contributing their works. and i started to realized that being a developer or modders does not get anything. ppl wont remeber u but they will say it very proudly which rom they r using, and they even dont know who made the mods, which is not important at all.
i can tell u frankly, the balance of my paypal donation account is still zero after producing some good and useful mods for more than a year. that's why i said money wont goes to edison but phillips
lastly, thx for ur interests in my bravia mod. and u can find some screenshots below
http://ykkfive.blogspot.com/2012/02/more-bravia-engine-screenshots-marked.html
http://ykkfive.blogspot.com/2012/01/sgs2-ics-403-sony-bravia-engine-demo.html
http://ykkfive.blogspot.com/2012/01/sgs2-wallpaper-sony-bravia-engine-demo.html
http://ykkfive.blogspot.com/2011/12/sgs2-gallery3d-with-sony-bravia-engine.html
FrEcP said:
Hey guys,
recently I see many Wildfire Roms presenting itself with the "new" bravia engine. I sounded great - and I went straight for some research here on XDA. There are several threads about porting it to any device u want...
So I took the 2 files and modified the build.prop and went for happy testing - sadly my screenshots form before after didn't show ANY difference...
So I searched on...
Checked out several screenshots in all those treads and notice that most screenshots also don't show any difference... reading on....
Many people notcied the same so most time a great discussion in each thread started.
Some peeople mentioned I can't be screenshotted casue its postprocessing,...
Others tell it only works with sony screens,.. and some complain it slightly doesn't work.
So what is the truth about that?
1. Cant' be screenshotted imho is bull**** since the flow should be: data -> processing -> buffer -> screen and a screenshot is taking data out of the buffer normaly (even there are different techiques - but root screenshot programs should do that as far as I know)
2. Only with sony screens? Nope don't think so as its JUST postprocessing - nothig else...
3. Doesn't work - a hoax? Maybe
So I asked myself how all this is working a great review i found was this
He is mentioning that there are several things needed for getting be engine to work.
1. be_* files
2. build.prop editing
3. the SWIQI service
4. an edited Galery app (since the one he found was complaining about the missing files if he deleted em)
Wich sounded quite propper to me. As postprocessing noramly is done by an app or has to be included into the rendering engine of android totaly... but his research showed it seems to be the galery app. Even he also has some wallpaper stuff meanwhile but to me this seems more like the galery app rerenderes the photo and then sets this rerendered photo as wallpaper. Sadly he doesnt describe it...
Sadly I can't find ANY thread here on XDA wich also ports the swiqi service propper (and doesn't just edit the build.prop + the be_* files). The only source I found wich also included some swiqi*.jar was owain94 (wich is credited in last rempuzzle btw) but he also closed his thread for hoax reasons... So even this doesn't wokr as it seems.
EDIT: the SGS version also seems to be here
No offense guys - I appreciate all the work u do for us - but since I couldn't figure out any wokring veriosn of BE Engine Ports and I see more and more Roms including it - I just asked myself if we got a popper port now - or still just those file copy actions?
Maby the SGS port is really working but I didn't have time to figure it out yet - it seems to be dependent on the galery app wich makes it quite useless if u dont use the android galery but quickpic,...
Anyway as the credits in Wildpuzzle (to owain94) and High-Voltage (didn't find any) don't go to the SGS guy i asked myself if those are even wokring?
And if u got those old (hoaxed) version (wich even jamal is presenting here in buzz forum) u should consider testing the above mentioned
Click to expand...
Click to collapse
Ok,maybe you are right.
But i m not a dev,and people says that it works on all phones.
There is no way to see if it is really working.
Anyway this should process all images in every app,so quick pic should work.
Anyway,sony phones don t have any option to activate this engine,like xloud
Sent from my HTC Desire S using XDA Premium App
kylon said:
Ok,maybe you are right.
But i m not a dev,and people says that it works on all phones.
There is no way to see if it is really working.
Anyway this should process all images in every app,so quick pic should work.
Anyway,sony phones don t have any option to activate this engine,like xloud
Sent from my HTC Desire S using XDA Premium App
Click to expand...
Click to collapse
There is no way to see if it is really working. <-- u can compare the outputs by screen capture before and after installing the mod u mentioned
this should process all images in every app,so quick pic should work. <-- not really. it depends where the bravia engine resides. if it is embedded in the browser for instance, then other apps are supposed not affected unless they r modified to do so
Intro:
As many of us, (myself included), we already knew that @Sultanxda said that his ROM and Camera HAL he developed on it, doesn't support RAW picturing. Months ago, I discovered a way to get ride into it, and manage to taking RAW photos. I'm not claiming I've developed by myself, I just found it as curious I'm. As I didn't see any post or thread informing about this, I decided to start this one to discuss about it. So, let start.
Requisites:
Obvious thing, you have to root, unlock, blah blah and install the pertinent ROM from the Sultanxda's thread. It works on all CM 12.1 builds. I haven't tested it on OxygenOS 1.0.0, OxygenOS 2.1.4, or Sultan's CM 13. Try and let me know.
***ANY SUGGESTIONS OR INFO ARE VERY WELCOME, AS I SAID, I'M NOT A DEVELOPER - I'M JUST SHARING IN SOMEONE DON'T KNOW ABOUT THIS***
Update! March 28th, 2016
Now you can test and use the CM12.1 Sultanxda's Snapdragon Camera, merged with the features I will detail below in the post. The user @gwindlord, sent me this incredible app. You can try it out flashing this zip.
Also, I've just realized that, this is a DNG photo tutorial! Because, the .raw file generated is pretty obsolete in the SnapCam. And the newer Bacon Camera app, doens't generate a .raw file. It is just a .dng with a .jpeg preview file. FreeDCam, doens't generate any .jpeg or .raw, that's why you can't edit these files on Snapseed.
Steps:
1.- You have to install these two apps.
SnapCam 0.6 by @fgnm - http://forum.xda-developers.com/oneplus-one/themes-apps/app-snapdragon-camera-mod-t3210978
Snapseed by Google- https://play.google.com/store/apps/details?id=com.niksoftware.snapseed
2.- Before you open the SnapCam, make sure that the Snapdragon Camera that comes with the ROM, is already closed. When you open it, change the picture resolution to 13 MP (I guess theres a bug that makes appear a 21.5 MP resolution, maybe due the app was build to work entirely with the original CM Camera HAL).
3.- Then, go to Settings > More Settings
4.- Uncheck the Zero Shutter Lag option, and swipe down to find "Select Picture Format" option. Tap on it.
5.- Now, I'll try to explain the options that appears there, as far as I know due the results I got before;
JPEG - Normal .jpeg picture, as any camera does. Duh.
YUV422SP - This seems to be a Generic RAW codec, the camera app will crash after taking a picture, and just a .dng file will be dumped.
BayerQ10RGGB - Qualcomm codec. - A pure RAW file will be dumped, with a minor warm color temperature. *RECOMMENDED*
BayerM10RGGB - Qualcomm codec. - A pure RAW file will be dumped, with a minor warm color temperature, BUT, with a few last pixels on the right side, corrupted.
BayerIQ10RGGB - Qualcomm codec. - A pure RAW file will be dumped, with a highly green tint quality.
Select the one as you desire.
6.- Make sure that the "Save DNG raw" option is checked. If not, it will not work. (Dunno why).
7.- Take any photo. The picture will take around 5 secs to process, have a still hand!
8.- Go to the gallery app (stock one recommended), and there will be a new "raw" folder on it. All RAW photos taken will appear there. No one will have a preview, but you can read a few metadata info on the details.
9.- Now, go to the Snapseed app and open a pic normally. Select any of these pictures with no preview on it. You will have to guide using the date was taken.
10.- If everything goes right, the RAW editing welcome splash screen should appears. Pass over it, and you'll see the taken photo.
11.- Make the adjustments that you desire (you can manipulate it a lot, the quality is incredible). And then, save the picture. A progress bar should appear on the notification panel.
12.- When if finished, voilá! A processed .jpeg file will appear on you gallery. It's done!
Alternative Workarounds:
- Using the FreeDCam app by @troopii - https://play.google.com/store/apps/details?id=troop.com.freedcam
With this app, beside it can get all parameters directly from the camera driver, there's a way to take pictures in .dng format. No RAW will be generated, so you will not be able to edit it on Snapseed. The colors on this one will be totally natural and untouched, as well as exposure, contrast and sharpness.
- Using the Bacon Camera app by @fgnm (Paid app!) - https://play.google.com/store/apps/details?id=com.fgnm.baconcamera
As it is based on his deprecated SnapCam app, this app have the same method to work. But, the behaviour seems to be diferent. In case you use the BayerM10RGGB, a weird corruped picture will be dumped. I recommend the BayerQ10RGGB codec again, the result will be different; the white balance will appears 'cold' in this case, and the photo will have the normal resolution of 4208x3120. The main problem is, all pictures will be in potrait mode, no matters how you rotate the device.
Bugs - Curiosities:
I've noticed a few weird thing that I can't find an explanation, but well;
Pictures dumped will have a weird resolution; 4212x3082.
There are a few manual modes you can't use on this, like as; sharpness, contrast, saturation, and white balance.
Using the FreeDCam you can take .dng pictures using the front camera.
The .raw file is undecodable, but the .dng one is not. If you use RawTherapee for Windows, you may get able to edit your files even more.
The RAW file need the .dng one to work and viceversa on Snapseed.
Thanks to:
I want to give a lot of thanks to Sultanxda for his incredible ROM and Camera HAL, to fgnm; to develop an exclusive camera app designed for the OnePlus. And now also to gwindlord, to merge these functions into the original CM12.1's Snapdragon Camera.
Conclusion:
I remember I saw a post of Sultan saying that he got a kinda RAW picturing while he was developing his HAL, but it was undecodable. I really love this partial funtion, because I found the camera of the OPO a very good tool. And I hope that this tutotial work for all of you, or at least find it useful. I'm not have a technical knowledge of how this works, but it works. So, let's give it a try.
Good luck for everyone, and regards!
Interesting! Since Sultanxda's camera HAL was developed from the Oxygen OS's one, I wonder if this method also works on Oxygen OS? Maybe more people can try and report
FreeDCam has issues focusing on Sultanxda latest stable 6.0 and SnapCam 0.6 force closes when I tried to use it though
firenxe said:
FreeDCam has issues focusing on Sultanxda latest stable 6.0 and SnapCam 0.6 force closes when I tried to use it though
Click to expand...
Click to collapse
I had not any focus problems con FreeDCam. SnapCam 0.6 might not work on MM roms.
I'm using the latest sultan MM rom from 18/04 and can confirm that it is possible to save dng files with FreeDCam!
I didn't flashed any of the zip files or anything else.
The exposure of the photos is not correct. Everything is too bright, but I can correct that by "underexposing" in RAW postproduction.
firenxe said:
Interesting! Since Sultanxda's camera HAL was developed from the Oxygen OS's one, I wonder if this method also works on Oxygen OS? Maybe more people can try and report
Click to expand...
Click to collapse
Sultans hal was picked from caf and not oxygen os. He is using camera libraries from oxygen os. This is sth different.
Sent from my A0001 using XDA-Developers mobile app
With sultans MM rom snapseed can't see the dngs from the FreeDcam folder but you can share them into the app. A bit awkward.
While Adobe's Lightroom app does view and edit them nicely!
Sent from my A0001 using XDA-Developers mobile app
Hello every one! Hope you're having a great day
I'm here because I need your help To make a long story short, until I can save enough to buy a new proper camera, I'm stuck with my P9 Lite, which cannot save pictures as RAW/DNG files. This feature is provided by Google's Camera2 API, which my phone doesn't have/support. Four questions:
1. Is it possible to install Camera2 API on my phone, through a custom ROM?
2. Is it possible to install a custom ROM without losing on the initial image quality provided by my phone's camera?
3. In theory, could this API be enabled by a future software update? Or does it only have to do with how the phone was originally conceived?
4. Even if I managed to get the API on my phone, would it be possible to make it fully supported, and would I be able to save RAW/DNG files even if my phone originally doesn't offer this option?
Thank you very much!
P.S: I've never thought of "flashing" a custom ROM on my phone, this issue is the only reason why I'm considering it. As you may have noticed by my way of explaining things, I'm a five year old when it comes to informatics, and I'd probably be the first in line to buy Smartphone Software For Dummies. As much as I admire how technical and specialised you can get about a science that goes way beyond my understanding abilities, if you can keep things slow and simple, as if you were talking to an actual five year old, I'd be very grateful
themadbuddha said:
Hello every one! Hope you're having a great day
I'm here because I need your help To make a long story short, until I can save enough to buy a new proper camera, I'm stuck with my P9 Lite, which cannot save pictures as RAW/DNG files. This feature is provided by Google's Camera2 API, which my phone doesn't have/support. Four questions:
1. Is it possible to install Camera2 API on my phone, through a custom ROM?
2. Is it possible to install a custom ROM without losing on the initial image quality provided by my phone's camera?
3. In theory, could this API be enabled by a future software update? Or does it only have to do with how the phone was originally conceived?
4. Even if I managed to get the API on my phone, would it be possible to make it fully supported, and would I be able to save RAW/DNG files even if my phone originally doesn't offer this option?
Thank you very much!
P.S: I've never thought of "flashing" a custom ROM on my phone, this issue is the only reason why I'm considering it. As you may have noticed by my way of explaining things, I'm a five year old when it comes to informatics, and I'd probably be the first in line to buy Smartphone Software For Dummies. As much as I admire how technical and specialised you can get about a science that goes way beyond my understanding abilities, if you can keep things slow and simple, as if you were talking to an actual five year old, I'd be very grateful
Click to expand...
Click to collapse
Can't you just install https://play.google.com/store/apps/details?id=net.sourceforge.opencamera on stock ROM? I think the camera2 api should be available.
Thank you for replying! The application supports Camera2 API, but if the API is not available on my phone in the first place, I don't think the application will work...According to my researches, the API is like, let's say, a camera: if your phone doesn't have a camera, you could install as many camera apps as you want, your phone still won't take any pictures...What I need is a way to add a camera to my phone - in our case, the API - so that I can start taking pictures - in our case, saving RAW/DNG files. Also, I might be wrong.
themadbuddha said:
Thank you for replying! The application supports Camera2 API, but if the API is not available on my phone in the first place, I don't think the application will work...According to my researches, the API is like, let's say, a camera: if your phone doesn't have a camera, you could install as many camera apps as you want, your phone still won't take any pictures...What I need is a way to add a camera to my phone - in our case, the API - so that I can start taking pictures - in our case, saving RAW/DNG files. Also, I might be wrong.
Click to expand...
Click to collapse
So the app doesn't work? I can't test it cause I am not on stock.
Just tried open cam on stock rom and I can capture RAW dng files, so it seems like camera2 is supported try it out!
UPDATE: Enable "Use alternative flash method" in photo settings if it won't take pictures when camera2 is enabled.
Open camera is pretty buggy on this phone when shooting RAW. Try "Footej camera", seems to work better
yaa but for footej need to pay to have fully featured. I payed for this but for m there is no diference to open camera.
I didn't say that Footej is better than open camera. Just that open camera often bugs for me when using camera2 - eg nothing happens when pressing camera button.
Sry for reviving the thread, is there any way to increase max shutter speed in camera2 api? I'm really interested in shooting some raw stuff but apps like Opencamera or Adobe Lightroom won't allow me to set over 1 second shutter speed (apart from the built-in camera app that allows up to 8 secs, but without raw support...) so it's a pain in the butt if I want to take raw pictures at night.
Using the stock Marshmallow Emui
The Lightroom app has a built in camera which can shoot RAW, I tried it and it works flawlessly.
Camera API2 *IS* present on p9 lite and *DOES* work.
zgomot said:
The Lightroom app has a built in camera which can shoot RAW, I tried it and it works flawlessly.
Camera API2 *IS* present on p9 lite and *DOES* work.
Click to expand...
Click to collapse
Yup it does, but shutter speed cannot be set over 1 second (see the screenshot), that means night photos end up being very noisy since I need to drastically increase iso. The default camera app allows much longer shutter time, that's why I'm wondering what's wrong
If it was possible to set it to like 10 secs in the Lightroom app, the camera would be damn great
Krastinov said:
Yup it does, but shutter speed cannot be set over 1 second (see the screenshot), that means night photos end up being very noisy since I need to drastically increase iso. The default camera app allows much longer shutter time, that's why I'm wondering what's wrong
If it was possible to set it to like 10 secs in the Lightroom app, the camera would be damn great
Click to expand...
Click to collapse
Have you tried Camera FV5?
zgomot said:
Have you tried Camera FV5?
Click to expand...
Click to collapse
Yea, but it says that this device doesn't support raw :|
Krastinov said:
Yea, but it says that this device doesn't support raw :|
Click to expand...
Click to collapse
Is it the trial version?
zgomot said:
Is it the trial version?
Click to expand...
Click to collapse
Full. Does it work for you?
Also I heard that official Nougat brings raw support to the built-in camera, can anyone verify that? I might wanna update in that case
Krastinov said:
Full. Does it work for you?
Also I heard that official Nougat brings raw support to the built-in camera, can anyone verify that? I might wanna update in that case
Click to expand...
Click to collapse
I Know This Is Quite Old But In Case Someone Is Still Wondering;
I'm Using Stock Nougat Firmware On My P9 Lite And It Does Support Raw Format, But You Have To Root The Phone And Enable Raw/DNG Format In Some System Files
Know issues:
1. Bluetooth toggle will not turn on
2. video codec makes first 10-15 seconds of video only green screen--(not noticed so much after install gapps and using chrome browser)
3. Camera not working
Resolved*
*testing phone had stock camera app disabled and was using open camera. With stock camera multiple crashes and unable to connect issue with camera. V3.5 has removed stock camera and added open camera to priv-app (preinstalled)
4. Microphone is also not working
V3.5 has fixed microphone.
5. video recording not working
V3.7 fixed video record for back camera only--also seems to have stabilized photo camera--(but still has crashed)
V-x-4.1 minor edits. Removed old renamed files. Removed apps and libs for fingerprint scanner. Swapped apns-config.xml from V21 to try get connection for more carriers. But it seems some devices are not able to even see imei from board V4.1 removed. Audio broken
x-v-4.6 has audio streaming partly functioning. Audio/ video plays some amount of time then stops. but will continues if playing through bluetooth. Further testing on speaker needed. Audio issue notIS present in FMRadio and unknown in phone. So far only in streamingMOST SOUND situations, like music apps and YouTube.
Also list of added apps primarily added for testing reasons
1. GPS test
2. AudioRecorder
3. File_Manager _es_file V3 (fewer ads)
4. OpenCamera
V5.0
removed extra fingerprint program, added MDDB folder (base band) trying to resolve 2 reports of lost IMEI on this rom. I have not had issue, so cannot confirm if adding these files has fixed problem.
V6.7-current beta
/system changes tracked on github
v6.7-or current /system
boot.img changes on github
https://github.com/mrmazakblu/Slim-port-boot-img
..
..
Install:
must have unlocked boot loader.
put rom file on sdcard and install with twrp =>Latest TWRP 3.1.1-0
you needs to install gapps.
http://opengapps.org/http://opengapps.org/
You need to enable navigation bar to get onscreen buttons.
settings >Navigation >Navigation bar >Enable navigation bar.
thanks to : @vampirefo this rom is ported from his build for the BLU Life Max
XDA:DevDB Information
Slim6 port for R1-HD, ROM for the BLU R1 HD
Contributors
mrmazak
ROM OS Version: 6.0.x Marshmallow
Based On: @vampirefo 's Blu Life Max SlimRom
Version Information
Status: Beta
Stable Release Date: 2017-06-16
Current Beta Version: x-5.0
Created 2017-06-09
Last Updated 2017-11-02
Thanks Great work I would like a RR.5.7.4
Enviado desde mi R1 HD mediante Tapatalk
can you take photos from this rom how looks like and thanks for working on this device i hope issue with camera will be fixed thanks @mrmazak
meroher said:
can you take photos from this rom how looks like and thanks for working on this device i hope issue with camera will be fixed thanks @mrmazak
Click to expand...
Click to collapse
there are 4 screen shots on the screenshot tab. But the look of any rom can be changes how you like with different launchers if desired.
Fixed the bugs except for the camera one.
New zip file in download tab.
Moved status from testing to beta.
camer.sh is my porting script, I made it, to make porting libs easier.
Sent from my Life Max using Tapatalk
vampirefo said:
camer.sh is my porting script, I made it, to make porting libs easier.
Sent from my Life Max using Tapatalk
Click to expand...
Click to collapse
Yes, the original locations listed in the script are to your /home dir.
I imported all but a few of the libs listed. The ones left out were *nvram*, related and one for "fs_mgr". one of them caused the rom to freeze at boot with the pop up message "starting apps". Left it there for 20 minutes first time. then started removing libs untill it booted again.
I was hoping to find what you did to make the camera work in zenUI. and that camera.sh was big help, but did not get the camera going. By itself.
I have been using diff to compare the lib folder in zenrom to 6.6 (because 6.6 was used to port zen, i think) and then compare Slim lib folder. I compiled lists of different files, identical files, missing files. All this has not gotten me any closer yet.
so far I have (as long as I didn't miss any) swapped in all the libs that were identical between zen and 6.6 to this slimrom using V21 as donor, only seemingly to have no effect.
After I run out of libs to swap in I am out of ideas.
I know it has been said fixing camera on cm/ lineageOS 14 (android 7) is not possible yet. But I thought is was possible on android 6
Camera Is Fixed*
I now have camera working on this slim port...
uploading built/port number 33 (X-3.3)
still needs small bug fixed, that will not screen cast to chromecast.
and first time I opened camera I did not have any on-screen navigation buttons(no way to exit camera). after some time buttons were available and next time it opened normal.
mrmazak said:
Yes, the original locations listed in the script are to your /home dir.
I imported all but a few of the libs listed. The ones left out were *nvram*, related and one for "fs_mgr". one of them caused the rom to freeze at boot with the pop up message "starting apps". Left it there for 20 minutes first time. then started removing libs untill it booted again.
I was hoping to find what you did to make the camera work in zenUI. and that camera.sh was big help, but did not get the camera going. By itself.
I have been using diff to compare the lib folder in zenrom to 6.6 (because 6.6 was used to port zen, i think) and then compare Slim lib folder. I compiled lists of different files, identical files, missing files. All this has not gotten me any closer yet.
so far I have (as long as I didn't miss any) swapped in all the libs that were identical between zen and 6.6 to this slimrom using V21 as donor, only seemingly to have no effect.
After I run out of libs to swap in I am out of ideas.
I know it has been said fixing camera on cm/ lineageOS 14 (android 7) is not possible yet. But I thought is was possible on android 6
Click to expand...
Click to collapse
I believed the newer libs might fix the camera, that was the reason, I bought a cheap R1HD from eBay, but the phone didn't work so couldn't test.
Anyway it seems they did, so that's good.
Sent from my Life Max using Tapatalk
vampirefo said:
I believed the newer libs might fix the camera, that was the reason, I bought a cheap R1HD from eBay, but the phone didn't work so couldn't test.
Anyway it seems they did, so that's good.
Sent from my Life Max using Tapatalk
Click to expand...
Click to collapse
the final step was to use the stock "system\lib\hw\camera.mt6735.so" but rename it to "system\lib\hw\camera.mt6737m.so"
i found that when I was trying to change the build.prop to show "6735" on platform but phone would not boot like that. So i got thinking any file needed that had 6735 in the name would also not work,
mrmazak said:
the final step was to use the stock "system\lib\hw\camera.mt6735.so" but rename it to "system\lib\hw\camera.mt6737m.so"
i found that when I was trying to change the build.prop to show "6735" on platform but phone would not boot like that. So i got thinking any file needed that had 6735 in the name would also not work,
Click to expand...
Click to collapse
Yes, ROM is built for 6737, R1HD and Life Max are almost the same phone, difference size, camera and 6737 instead of 6735.
Anyway good job.
Sent from my Life Max using Tapatalk
how is the performance vs stock with all bloatware removed?
deathblade200 said:
how is the performance vs stock with all bloatware removed?
Click to expand...
Click to collapse
Seems a little quicker on slim6
Great job, I like it
So is this a usable daily driver?
roboman2444 said:
So is this a usable daily driver?
Click to expand...
Click to collapse
It's been stable and smooth for me, I have not had any force closes, reboots, or any odd behavior. I would call it a good daily.
mrmazak said:
It's been stable and smooth for me, I have not had any force closes, reboots, or any odd behavior. I would call it a good daily.
Click to expand...
Click to collapse
Nice, ill think about installing it then.
Will the camera fix potentially help with android 7 roms?
roboman2444 said:
Nice, ill think about installing it then.
Will the camera fix potentially help with android 7 roms?
Click to expand...
Click to collapse
I do not think the camera fix here will help 7.
These lib files, "so" files, "blobs", call them as you will. Are still for Android 6 so , as I believe will not work on 7
mrmazak said:
Seems a little quicker on slim6
Click to expand...
Click to collapse
I know benchmarks don't mean a whole lot but they can give an idea of performance so could you provide some benchmarks for comparison? just trying to decide if I should switch to the rom or not
deathblade200 said:
I know benchmarks don't mean a whole lot but they can give an idea of performance so could you provide some benchmarks for comparison? just trying to decide if I should switch to the rom or not
Click to expand...
Click to collapse
They would be the same or about the same, a rom doesn't increase benchmarks, a custom kernel might, benchmarks have their place this isn't one of them.
To each their own I guess.
Sent from my Life_Max using Tapatalk