I don't understand why are we not able to produce the same post processing capabilities as oneplus? Are we missing something? If anyone can explain, I'll be really thankful!
Edit:
Ok! So, I did some digging and (anyone correct me If I'm wrong) here's the general flow of camera workings. Camera Application --> HAL(Hardware Application Layer) API --> Kernel --> Drivers --> Hardware Module. Now, "only Interface" for HAL is provided by Android, but each manufacturer has to implement this interface. So, Doesn't Oneplus provide us with the hal implementation? if, so, doesn't it include the post processing algorithms and methods already? I still am very confused. @siankatabg Can you please explain?
Sources: Android Source
0xelectron said:
I don't understand why are we not able to produce the same post processing capabilities as oneplus? Are we missing something? If anyone can explain, I'll be really thankful!
Click to expand...
Click to collapse
Yes... This is the case on every device and every custom rom.. We are missing the after processing that OOS does.. So that is why we do not get the same quality..
Puddi_Puddin said:
Yes... This is the case on every device and every custom rom.. We are missing the after processing that OOS does.. So that is why we do not get the same quality..
Click to expand...
Click to collapse
Yes, that's what I'm asking. Why are we not able to produce same post processing that oos does?
0xelectron said:
Yes, that's what I'm asking. Why are we not able to produce same post processing that oos does?
Click to expand...
Click to collapse
Maybe because it is a **** ton off work? Or noone has the knowledge?
Puddi_Puddin said:
Maybe because it is a **** ton off work? Or noone has the knowledge?
Click to expand...
Click to collapse
Isn't developing custom roms ton of work too?
P. S. Not trying to argue, just curious.
0xelectron said:
Isn't developing custom roms ton of work too?
P. S. Not trying to argue, just curious.
Click to expand...
Click to collapse
Yes.. Maybe a proper after processing is more work? I have no clue how you need to do those things.. But if it was easy I'm pretty sure someone would've done it already.
0xelectron said:
I don't understand why are we not able to produce the same post processing capabilities as oneplus? Are we missing something? If anyone can explain, I'll be really thankful!
Click to expand...
Click to collapse
This is the case for every custom rom and for every phone.
Maybe because the camera code is not open source and companies do not provide them to the dev community.
Iqbal Ansari said:
This is the case for every custom rom and for every phone.
Maybe because the camera code is not open source and companies do not provide them to the dev community.
Click to expand...
Click to collapse
Was not the case for the OnePlus One, all Nexus devices and the Pixel.
Even though they all use closedsource-postprocessing, all it takes is to install the correct camera app and your are good to go on custom-roms.
It only depends on how the OEM implements it. OnePlus, as a so called "community friendly" company, decided to link their postprocessing not only to their camera app, but also to their own OxygenOS framework,
which is completely against the community.
This makes it harder to use it on custom-roms, as the framework needs to be modified specifically for each rom.
Why? They say the camera+postprocessing is supposed to be quicker this way.
Maybe they are right (for their own implementation), maybe they don't know better (probably, seeing other shenanigans they pull on OOS).
Iqbal Ansari said:
This is the case for every custom rom and for every phone.
Maybe because the camera code is not open source and companies do not provide them to the dev community.
Click to expand...
Click to collapse
I get that they want protect their camera code to stay ahead in the game. But, I still don't understand why, we(community) are missing that, we are not able to produce the same quality as theirs. I think either its too hard, or, maybe we don't have required information about the camera module or something like that.
AcmE85 said:
Was not the case for the OnePlus One, all Nexus devices and the Pixel.
Even though they all use closedsource-postprocessing, all it takes is to install the correct camera app and your are good to go on custom-roms.
It only depends on how the OEM implements it. OnePlus, as a so called "community friendly" company, decided to link their postprocessing not only to their camera app, but also to their own OxygenOS framework,
which is completely against the community.
This makes it harder to use it on custom-roms, as the framework needs to be modified specifically for each rom.
Why? They say the camera+postprocessing is supposed to be quicker this way.
Maybe they are right (for their own implementation), maybe they don't know better (probably, seeing other shenanigans they pull on OOS).
Click to expand...
Click to collapse
Ok, it's difficult to port or implement their camera app in custom rom. But, why are we (community) not able to utilize the camera module as them? I mean they have great post processing, fast capture times, 60fps videos, etc. Why we are not able to implement those features? Are we missing something?
0xelectron said:
Ok, it's difficult to port or implement their camera app in custom rom. But, why are we (community) not able to utilize the camera module as them? I mean they have great post processing, fast capture times, 60fps videos, etc. Why we are not able to implement those features? Are we missing something?
Click to expand...
Click to collapse
You quoted the reason, what more do you need?
LineageOS uses the exact same drivers and system files for the camera which can be found in OxygenOS.
It is missing the links to the postprocessing which have to be integrated into the framework.
There is no documentation for this by OnePlus, so this is a painful job.
We have a port for the camera app which somehow provides similar or at least nearly the same quality:
https://forum.xda-developers.com/oneplus-3/themes/port-oxygenos-stock-camera-cm-t3451721
If someone can give you a more detailed explanation it is most definitely @siankatabg
0xelectron said:
I don't understand why are we not able to produce the same post processing capabilities as oneplus? Are we missing something? If anyone can explain, I'll be really thankful!
Click to expand...
Click to collapse
Do you have an example of aosp vs stock processing. I think it maybe possible if you could show me the difference I'd know where to start
Sent from my NX503A using XDA Free mobile app
Ok! So, I did some digging and (anyone correct me If I'm wrong) here's the general flow of camera workings. Camera Application --> HAL(Hardware Application Layer) API --> Kernel --> Drivers --> Hardware Module. Now, "only Interface" for HAL is provided by Android, but each manufacturer has to implement this interface. So, Doesn't Oneplus provide us with the hal implementation? if, so, doesn't it include the post processing algorithms and methods already? I still am very confused. @siankatabg Can you please explain?
defcomg said:
Do you have an example of aosp vs stock processing. I think it maybe possible if you could show me the difference I'd know where to start
Sent from my NX503A using XDA Free mobile app
Click to expand...
Click to collapse
I don't have examples currently, but, I've noticed that the post processing of aosp is generally inferior compared to stock. Also, it doesn't have features such as 60fps video recording and proper EIS/OIS.
AcmE85 said:
You quoted the reason, what more do you need?
LineageOS uses the exact same drivers and system files for the camera which can be found in OxygenOS.
It is missing the links to the postprocessing which have to be integrated into the framework.
There is no documentation for this by OnePlus, so this is a painful job.
We have a port for the camera app which somehow provides similar or at least nearly the same quality:
https://forum.xda-developers.com/oneplus-3/themes/port-oxygenos-stock-camera-cm-t3451721
If someone can give you a more detailed explanation it is most definitely @siankatabg
Click to expand...
Click to collapse
I think I'm not explaining myself properly. What I'm trying to ask is that why the the quality/features of the the camera in custom roms a little inferior compared to stock OOS? I did some digging and found out that most of the capabilities are included in the hal api, and it's implementation, I think is provided by Oneplus. I can be totally wrong (correct me, if I'm).
0xelectron said:
Ok! So, I did some digging and (anyone correct me If I'm wrong) here's the general flow of camera workings. Camera Application --> HAL(Hardware Application Layer) API --> Kernel --> Drivers --> Hardware Module. Now, "only Interface" for HAL is provided by Android, but each manufacturer has to implement this interface. So, Doesn't Oneplus provide us with the hal implementation? if, so, doesn't it include the post processing algorithms and methods already? I still am very confused. @siankatabg Can you please explain?
Click to expand...
Click to collapse
Yes The flow is Camera App > Android Java Framework > Android Framework Native (libcamera_client/service) | libhardware loads the hal > hal camera.msm8***.so that uses libmmcamera_interface to hook up with the vendor libs via MCT liboemcamera/libmmcamera_mct.so > libmmcamera2_sensor_modules.so > libmmcamera_imx298.so > loads calibration via chromatix as well as eeprom
what weird about one plus they seem to have multiple chromatix blobs for diff camera modes my theory the problem with calibration lies here because it shouldn't matter weather the rom is aosp or stock, the camera calibration should be same unless the behavior is changed on purpose its the way its worked with qualcomm devices
thats why i asked for a comparison between aosp and stock so i could see if say the noise reduction was heavy in aosp then we would know to look at the chromatix cpp files ive mapped the chromatix cpp hex offsets on hex workshop so you can copy entire calibation blocks from for example clear shot cpp chromatix libs. hell you could copy noise calibration from any device with same chromatix version ie lg v20 / mi5.
if its overexposure/underexposure dropped fps etc the the chromatix 3a lib is what you need to be looking at
defcomg said:
Yes The flow is Camera App > Android Java Framework > Android Framework Native (libcamera_client/service) | libhardware loads the hal > hal camera.msm8***.so that uses libmmcamera_interface to hook up with the vendor libs via MCT liboemcamera/libmmcamera_mct.so > libmmcamera2_sensor_modules.so > libmmcamera_imx298.so > loads calibration via chromatix as well as eeprom
what weird about one plus they seem to have multiple chromatix blobs for diff camera modes my theory the problem with calibration lies here because it shouldn't matter weather the rom is aosp or stock, the camera calibration should be same unless the behavior is changed on purpose its the way its worked with qualcomm devices
thats why i asked for a comparison between aosp and stock so i could see if say the noise reduction was heavy in aosp then we would know to look at the chromatix cpp files ive mapped the chromatix cpp hex offsets on hex workshop so you can copy entire calibation blocks from for example clear shot cpp chromatix libs. hell you could copy noise calibration from any device with same chromatix version ie lg v20 / mi5.
if its overexposure/underexposure dropped fps etc the the chromatix 3a lib is what you need to be looking at
Click to expand...
Click to collapse
Whoa! That's a lot of information. I've to study more. I'll definitely look into it. Thanks!
0xelectron said:
Whoa! That's a lot of information. I've to study more. I'll definitely look into it. Thanks!
Click to expand...
Click to collapse
Hex Workshop CPP Bookmark
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
attached the offset bookmark as well as the chromatix source if youd like to check it out
0xelectron said:
Whoa! That's a lot of information. I've to study more. I'll definitely look into it. Thanks!
Click to expand...
Click to collapse
You asked a question to which someone kindly gave you a simple answer and you weren't satisfied.... Then someone gave you a complex answer and you didn't understand...Smh and Lmfao!!
Sent from my ONEPLUS A3000 using Tapatalk
fcisco13 said:
You asked a question to which someone kindly gave you a simple answer and you weren't satisfied.... Then someone gave you a complex answer and you didn't understand...Smh and Lmfao!!
Click to expand...
Click to collapse
You're right. I didn't understand. But, that's a good thing. I'm learning. I'm digging. I'm doing something I would've not done, normally. For example, the first simple answer didn't satisfy me, so, I started learning the inner workings of the android camera. Second complex answer gave me more in-depth knowledge then I leaned, and it is making me study more to understand. So, say what you want, but, I'm thankful for both the answers. Thank you everyone!
Related
GALAXY NEXUS PHONE MODS
This is all part of the Galaxy Nexus ToolKit but I have made a new Thread for people who may not have noticed it, people who didnt need the ToolKit but may find some of the Mods useful or just people who want to talk about the Phone Mods specifically.
FUNCTIONS OF THE PHONE MODS SECTION V1.4 [GSM + LTE][13TH MARCH 2012]
Change the Screen Density (DPI)
CWM Recovery, Only 1 No in the Confirmation Screen
Camera Sounds (Disable/Enable Camera Shutter, Video Camera Shutter, Focus)
Camera Enhancements (Increase Video Bitrate, Sound Bitrate, Photo Quality)
Change WiFi Scan Interval (Time between scanning for new Wifi Access Points)
Startup Boot Animation Screen (Disable/Enable which affects Boot Time)
Screen Colour Control (Change Gamma Offset and Colour Multiplier)
--------------------------------------------------------------
DOWNLOAD
The Phone Mods are part of the Galaxy Nexus ToolKit. You can download the latest version *HERE* (no need to install drivers if you already have adb/fastboot drivers installed) and select option 18 in the Main Menu to enter the Phone Mods Section.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
--------------------------------------------------------------
USAGE
STOCK ROM users will need to enter the Mods Section via the Galaxy Nexus ToolKit as most functions need an insecure boot image which is set up from the Model Selection Screen of the ToolKit. If you are running a CUSTOM ROM (with insecure boot image) then you can run the ModsSection.exe directly if you wish.
ALL Mods Section functions require you to be booted into Android and connected to the PC via usb with adb/fastboot drivers installed. If you havent done this already then refer to the Galaxy Nexus ToolKit Thread for setup instructions.
The Galaxy Nexus ToolKit and Mods Section are very tightly integrated and so is impossible to seperate the 2 parts unless I want to cut out Stock Rom users (which I dont) so please dont ask if I can split them up. I could but its just not worth it.
Lastly if you have any ideas for functions that can be added to the Mods Section or just want to discuss a particular function then feel free.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.
*reserved for future use*
Already used your tool kit to root, unlock, and flash recovery!!! Awesome work you've done, it's too easy Glad to see you made a separate thread for this, I agree it got kind of lost in the original thread.
Sent from my Galaxy Nexus using Tapatalk
Hmm, I like the idea of being able to disable the boot animation, and I'll give the camera improvements a go and report back.
I've always tried to beat something into my geeks when I'm teaching IT classes, and that's the idea of "Do it right, make it easy". You sir, have done a great job at putting together this toolkit in a way that makes things simple, and with great documentation. Nice work!
graymulligan said:
Hmm, I like the idea of being able to disable the boot animation, and I'll give the camera improvements a go and report back.
I've always tried to beat something into my geeks when I'm teaching IT classes, and that's the idea of "Do it right, make it easy". You sir, have done a great job at putting together this toolkit in a way that makes things simple, and with great documentation. Nice work!
Click to expand...
Click to collapse
Thank you im sure your geeks learn alot from you lol
Disabling the boot animation knocks about 5 seconds off the bootup time and there are a few Roms with not very desirable graphics lol.
Please do report back I always welcome any feedback and ideas for additions.
I get an error when trying to backup the xml file...Any ideas?
Looks great . You don't happen to have a unix version?
If anybody is having problems... Or if your using francos kernel you need to disable fast usb charge.... Hey thanks for your great work
---------- Post added at 02:58 PM ---------- Previous post was at 02:56 PM ----------
MysticDeth said:
I get an error when trying to backup the xml file...Any ideas?
Click to expand...
Click to collapse
Are you using Franco kernel? Disable the fast usb charge.... Your good to go
MysticDeth said:
I get an error when trying to backup the xml file...Any ideas?
Click to expand...
Click to collapse
What Rom and kernel are you using?
Are you booted into Android and connected via usb cable before starting?
I dont know where the fast usb charge option is but as the previous user posted you can try to disable that and try again.
Also if you go back into the main ToolKit are you seeing the serial number under adb at the top?
Mark.
yyz71 said:
If anybody is having problems... Or if your using francos kernel you need to disable fast usb charge.... Hey thanks for your great work
---------- Post added at 02:58 PM ---------- Previous post was at 02:56 PM ----------
Are you using Franco kernel? Disable the fast usb charge.... Your good to go
Click to expand...
Click to collapse
I didn't disable fast usb charge but I did reboot and everything worked fine after the reboot
MysticDeth said:
I didn't disable fast usb charge but I did reboot and everything worked fine after the reboot
Click to expand...
Click to collapse
Glad it went well after the reboot
Mark.
io53 said:
Looks great . You don't happen to have a unix version?
Click to expand...
Click to collapse
I do want to have versions of the ToolKit for Mac and Linux if I can get some testers and/or people who can help me convert the scripts. Im guessing most of the scripts should work fine as they are just adb/fastboot commands but there may be differences with pauses and some search replace routines.
Do linux bash scripts work on unix?
Mark.
Wow.. that's more handy..
Thanks for the nee options being included in your tool..
What exactly does the camera enhancements option do?
Any news on the camera enhancement and weather it works?
bemymonkey said:
What exactly does the camera enhancements option do?
Click to expand...
Click to collapse
I also would like to know this. Very intriguing. Also, what are the chances of it screwing up the camera app? (Considering custom roms have modified versions)
frenccw said:
I also would like to know this. Very intriguing. Also, what are the chances of it screwing up the camera app? (Considering custom roms have modified versions)
Click to expand...
Click to collapse
I second this question, but on the other hand, we all have seen mskips dev work before this. A Nand backup/restore would solve everything, so don't fear a try..
bemymonkey said:
What exactly does the camera enhancements option do?
Click to expand...
Click to collapse
The enhancement does exactly what it states on the screen when you select option 4 in the phone mods section:
This mod focuses on the media_profiles.xml file in the /etc/ folder on your phone.
The x2 Quality Settings doubles the standard camcorder bitrate for 480P, 720P and 1080P [8M, 16M, 24M] as well as change the quality settings for the camera to 100, 85, 75 [from 95, 80, 70] and the memcap setting to 25000000.
The Medium Quality Settings push the camcorder bitrate up even more for 480P, 720P and 1080P [10M, 20M, 35M] as well as change the quality settings for the camera to 100, 85, 75 [from 95, 80, 70] and the memcap setting to 30000000.
The High Quality Settings push the camcorder bitrate up to the max for 480P, 720P and 1080P [14M, 30M, 50M] as well increase the Audio bitrate up to 128k and increase the Audio channels to 2. The duration setting has also been changed to 60 from 30 for the above formats. All the quality settings for the camera have been forced to 100 and the memcap setting has been pushed up to 40000000.
These 3 profiles are for testing and I hope you get improvements using them but if you want to you can customize either of them from the mods folder and push them back to your phone.
Click to expand...
Click to collapse
As for proof that the mod works I havent taken tests shots/videos with each mod but the stock bitrates for the camcorder are a bit low so increasing it can only benefit the quality of the captured image. Whether the highest setting is neccessary or not doesnt really matter as it is upto the end user to decide if they prefer it but I would definitely recommend applying at least the 2x setting .
frenccw said:
I also would like to know this. Very intriguing. Also, what are the chances of it screwing up the camera app? (Considering custom roms have modified versions)
Click to expand...
Click to collapse
I put a compulsory backup step in every mod section so that even on custom roms the original file can be saved to your computer before it is altered and pushed back if you dont like the changes. There is absolutely no chance of screwing up the camera app as only bitrates and quality settings are altered.
MuayThaiFighter8 said:
I second this question, but on the other hand, we all have seen mskips dev work before this. A Nand backup/restore would solve everything, so don't fear a try..
Click to expand...
Click to collapse
A NAND backup isnt needed as the file to be altered has to be backed up by the ToolKit in order to proceed so it can be easily and safely restored if the user wants to.
Mark.
Ah okay, so stills aren't affected at all?
bemymonkey said:
Ah okay, so stills aren't affected at all?
Click to expand...
Click to collapse
Does noone bother reading my posts properly lol
If you read my above post the camera quality (stills) is pushed up by pushing the modded settings.
The 2x and medium profiles pushes the 3 quality values of stills upto 100, 85 and 75 (instead of 95, 80, 70). The high quality profile pushes all 3 values upto 100 (meaning there is no compression in the images taken).
Mark.
Has the New camera API for Android 5.0 become available now that we are getting 5.0 roms?
Really looking forward to using the new features.
If not, what aspect of these new things are we waiting for to get support? Is it something in AOSP that we have to wait for, or something with the apps or roms themselves?
WACOMalt said:
Has the New camera API for Android 5.0 become available now that we are getting 5.0 roms?
Really looking forward to using the new features.
If not, what aspect of these new things are we waiting for to get support? Is it something in AOSP that we have to wait for, or something with the apps or roms themselves?
Click to expand...
Click to collapse
Do you mean for AOSP 5.0 or LG's own 5.0 rom?
I know that AOSP and all the roms using it's base, can't really handle the camera of the G3.
Could you specify?
Derduden said:
Do you mean for AOSP 5.0 or LG's own 5.0 rom?
I know that AOSP and all the roms using it's base, can't really handle the camera of the G3.
Could you specify?
Click to expand...
Click to collapse
I suppose the question applies to both, but in this case I'm just asking about CM12.
WACOMalt said:
I suppose the question applies to both, but in this case I'm just asking about CM12.
Click to expand...
Click to collapse
Well you're gonna get the new API, but it's going to be drastically limited since the LG camera needs an LG driver.
So you might have a feature more or two, but it's really no use when the camera is degraded to 2011 quality and video is only 15 fps.
There is a lot more to this than the API of the operating system. The driver is where the magic is at.
Derduden said:
Well you're gonna get the new API, but it's going to be drastically limited since the LG camera needs an LG driver.
So you might have a feature more or two, but it's really no use when the camera is degraded to 2011 quality and video is only 15 fps.
There is a lot more to this than the API of the operating system. The driver is where the magic is at.
Click to expand...
Click to collapse
isn't there a way to port that driver to AOSP? i find it hard to believe we are going to get stuck with this quality
sooti said:
isn't there a way to port that driver to AOSP? i find it hard to believe we are going to get stuck with this quality
Click to expand...
Click to collapse
I actually put up a post some time ago asking the same question, but the answer remains the same, it's probably not going to happen any time soon. Not to mention other problems that relates to G3 + AOSP. Example could be the IR remote controller.
I know that some developers had luck with AOSP + LG G2 with the camera, where they ported it, but AFAIK it was more or less crashing all the time and missing features and functions, so at the end of the day it wasn't really worth the effort.
Now what I have done is simply use LG's Lollipop and then tweak it all the way to AOSP, retaining all the good stuff
LG's rom can actually be made very nice including in performance and that comes from a guy whose old phone was a Nexus 5 with Lollipop
The ports of LGs camera always worked great for me on AOSP. And given how ridiculously simple the camera app is for the G3 I'd expect it to be even easier to get working.
I'm OK with sticking on stock Lolipop Roms if that means having access to the 5.0 Camera API. I just have to wait to get there since I'm on VZW.
Are you able to use the API on your Lollipop stock rom?
WACOMalt said:
Has the New camera API for Android 5.0 become available now that we are getting 5.0 roms?
Really looking forward to using the new features.
If not, what aspect of these new things are we waiting for to get support? Is it something in AOSP that we have to wait for, or something with the apps or roms themselves?
Click to expand...
Click to collapse
The lollipop roms from LG do not feature a camera driver for the new camera2 api. That is a shame for two reasons. First of all the new api gives you a lot of new options (manual mode, raw export among others) which in turn enable developers to implement neat tricks like the super sensor from A Better Camera. Overall a huge opportunity! Secondly the LG Flex2 with the exact same camera module (AFAIK) has the new api.
So please everyone ask LG about that. They might eventually listen. Or maybe some rom developer could port the driver over from the Flex2.
matthias.matthias said:
The lollipop roms from LG do not feature a camera driver for the new camera2 api. That is a shame for two reasons. First of all the new api gives you a lot of new options (manual mode, raw export among others) which in turn enable developers to implement neat tricks like the super sensor from A Better Camera. Overall a huge opportunity! Secondly the LG Flex2 with the exact same camera module (AFAIK) has the new api.
So please everyone ask LG about that. They might eventually listen. Or maybe some rom developer could port the driver over from the Flex2.
Click to expand...
Click to collapse
That's really sad. If the gflex 2 Roms have it and it is indeed the same module, is there any way to get it from there and add it to our stock based Roms?
WACOMalt said:
That's really sad. If the gflex 2 Roms have it and it is indeed the same module, is there any way to get it from there and add it to our stock based Roms?
Click to expand...
Click to collapse
That's what I'm hoping for. . . Anyone?
is there any luck of us getting this functionality on our phone ? does it require a firmware update from lg for the camera ?
because cyanogemod/aosp has the api already included. so it makes me think its the firmware which is lacking
lixxus said:
is there any luck of us getting this functionality on our phone ? does it require a firmware update from lg for the camera ?
because cyanogemod/aosp has the api already included. so it makes me think its the firmware which is lacking
Click to expand...
Click to collapse
Indeed it is the firmware. However XCam LG by xdabbeb acheives much if what I'd hoped for from the camera API. Bitrate/compression control, RAW (DNG format) support, ISO control and some shutter speed settings.
WACOMalt said:
Indeed it is the firmware. However XCam LG by xdabbeb acheives much if what I'd hoped for from the camera API. Bitrate/compression control, RAW (DNG format) support, ISO control and some shutter speed settings.
Click to expand...
Click to collapse
yeah thought so. thanks for the info. its a shame really. i hope LG come with a firmware update ,
I cant use the xcam as i use cyanogemod. I guess i will be patient
https://developers.google.com/glass/tools-downloads/system#factory_images said:
Warning: Rooting, unlocking, or flashing your Glass voids your warranty and can leave your device in an irrecoverable state. Proceed at your own risk.
Click to expand...
Click to collapse
This is the Android Open Source Project for Google Glass. The current version is 5.1.1 Lollipop. Thanks to the OMAP4-AOSP project, development for Glass has been rapid and stable. The blobs that are not provided by OMAP4-AOSP are pulled from XE22, and the XRX13B kernel is compiled from source.
This is not the OS you would expect to run on Glass. This is stock Android, and it is difficult to use. If you enjoy using your Glass on a day-to-day basis, please do not flash this ROM.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Why did you do this?
I wanted to create a base platform for developers, like myself, who like to experiment. We shouldn't be bound to the GDK.
I wanted to revive community interest in Google Glass. It is an incredibly interesting device that seemed to disappear before its peak.
Above all else, I just wanted to see if I could.
Installation Instructions
Your Glass will be wiped if you follow these instructions.
1) Download and extract the zip containing the boot.img and system.img files:
aosp_glass-1_5.1.1_042016.zip
MD5: 595c4e0b50fa191f42eb5609cfbf92fd
2) Boot Glass into fastboot mode:
From Glass, enter the Settings menu.
Scroll to the Device Info card and select it.
Scroll to the "Turn on debug" card and select it.
Once debugging is enabled, connect Glass to your computer and enter:
Code:
$ adb reboot-bootloader
https://developers.google.com/glass/tools-downloads/system#factory_images said:
You can also enter fastboot mode by holding down the camera button, pressing the power button (Glass must be off before doing this), and waiting about 10-15 seconds. Glass does not indicate that it is in fastboot mode (display is off), but you can run fastboot devices to check.
Click to expand...
Click to collapse
3) If you have not already, unlock your Glass:
Code:
$ fastboot oem unlock
4)
Code:
$ fastboot flash system system.img
$ fastboot flash boot boot.img
$ fastboot erase cache
$ fastboot erase userdata
$ fastboot reboot
The first boot may take some time as partitions are created and firmware versions are checked. You may also experience a reboot during the initial boot. To revert back to the stock Glass ROM, simply follow the instructions at https://developers.google.com/glass/tools-downloads/system#factory_images.
Working:
WiFi
Bluetooth pairing
GPS
Touchpad
Audio (kind of)
Camera (see below)
Known Issues:
Audio currently outputs either the left or right signal
Bluetooth connections cannot be made to various devices
Backlight control does not work
Powered off charging indicator is flakey
Camera gamma is sketchy in low light
Screenshots are glitchy
You tell me
Tips and Tricks:
Enable "Show touches" in the Developer options to navigate easier
Use ADB input commands for text or DPAD input: see http://stackoverflow.com/questions/7789826/adb-shell-input-events#answer-8483797
XDA:DevDB Information
AOSP for Google Glass, ROM for the Google Glass
Contributors
jtxdriggers, http://omap4-aosp.github.io/
Source Code: https://github.com/justindriggers/android_device_glass_glass-1
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Testing
Created 2016-04-11
Last Updated 2016-04-20
Awesome!
Thank you! That's awesome! I'll Flash it later this day
[edit]
installed it and its working I have also installed the pulled XE7 APKs from zhuowei . So far it is working. A real custom rom for Glass, with an easy to use launcher and glass-friendly apps would be fantastic. I think your Work is a perfect base for it. I am really looking forward on upcoming developments. Thank you again!
fuekiin said:
A real custom rom for Glass, with an easy to use launcher and glass-friendly apps would be fantastic. I think your Work is a perfect base for it. I am really looking forward on upcoming developments. Thank you again!
Click to expand...
Click to collapse
That's the long-term goal. Hopefully we can focus on getting Marshmallow working first, then we can start work on a new application layer. I am glad to hear that it's working for you. If you don't mind me asking, which version of Glass do you have (1GB or 2GB)? I personally have the 1GB model but I'd like to make sure the 2GB model works as well.
jtxdriggers said:
That's the long-term goal. Hopefully we can focus on getting Marshmallow working first, then we can start work on a new application layer. I am glad to hear that it's working for you. If you don't mind me asking, which version of Glass do you have (1GB or 2GB)? I personally have the 1GB model but I'd like to make sure the 2GB model works as well.
Click to expand...
Click to collapse
It's the newer Version with 2GB of RAM :good:
Where are you tracking bugs? Github?
fuekiin said:
It's the newer Version with 2GB of RAM :good:
Click to expand...
Click to collapse
Excellent!
fuekiin said:
Where are you tracking bugs? Github?
Click to expand...
Click to collapse
Report them in this thread for now. If this actually gains any popularity then perhaps I'll open an issue tracker.
Glad to see you've picked your glass up again. Does this rom support mouse functionality? If so it might be just what I am looking for. I will test this out later and let you know what I find.
exseus said:
Glad to see you've picked your glass up again. Does this rom support mouse functionality? If so it might be just what I am looking for. I will test this out later and let you know what I find.
Click to expand...
Click to collapse
Honestly not sure, let me know if it works!
jtxdriggers said:
Honestly not sure, let me know if it works!
Click to expand...
Click to collapse
For me it isn't working with my BT mouse.
Sent from my Nexus 6 using XDA-Developers mobile app
fuekiin said:
For me it isn't working with my BT mouse.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Do you still get a cursor and all that? That is a shame.
fuekiin said:
For me it isn't working with my BT mouse.
Click to expand...
Click to collapse
That's disappointing. I'll have to go grab one and see what I can do. It may be a limitation of the bluetooth controller on the device.
jtxdriggers said:
That's disappointing. I'll have to go grab one and see what I can do. It may be a limitation of the bluetooth controller on the device.
Click to expand...
Click to collapse
Tomorrow i will maybe do some more testing. Also with an wired Mouse.
Beside this Problem, have you thought about mirroring the touch pad? For me it's very confusing right now [emoji1]
Sent from my Nexus 6 using XDA-Developers mobile app
fuekiin said:
Tomorrow i will maybe do some more testing. Also with an wired Mouse.
Beside this Problem, have you thought about mirroring the touch pad? For me it's very confusing right now [emoji1]
Click to expand...
Click to collapse
It makes sense as it is to me. Have you tried enabling "Show touches" in the Input section of the Developer options?
jtxdriggers said:
It makes sense as it is to me. Have you tried enabling "Show touches" in the Input section of the Developer options?
Click to expand...
Click to collapse
Yeah, it's enabled [emoji106]
Do you see any possibility to get Android Wear working, like biktor_gj did it for the gear 2?
fuekiin said:
Do you see any possibility to get Android Wear working, like biktor_gj did it for the gear 2?
Click to expand...
Click to collapse
Unfortunately it's still too early to tell. I got 5.1.1 "booting" last night (I use that term loosely, as all that really works is ADB), so I'd say there's a chance. But honestly, I don't know enough about Android Wear (yet) to say anything confidently. We'll see!
Forgive my ignorance, but will this rom allow for installing regular android apps on the glass? What are the advantages of having this custom rom? Also where can I donate?
kevkid said:
Forgive my ignorance, but will this rom allow for installing regular android apps on the glass? What are the advantages of having this custom rom? Also where can I donate?
Click to expand...
Click to collapse
That is correct, I've had reports of people installing GApps successfully and everything - just be aware that using the device is pretty difficult. Not really the "at a glance" mentality that Google was going for.
Long term, I'm looking to get Lollipop and Marshmallow working, and eventually develop a Glass-friendly UI on top of those based off of what the community thinks Glass should have been. Only a handful of people seem to be interested, but it's a really great side project for me.
That said, I'm not currently accepting donations. If the cost of my build box gets too high then I may reconsider, but I honestly don't want people investing in something that I actually have very little time to work on.
jtxdriggers said:
That is correct, I've had reports of people installing GApps successfully and everything - just be aware that using the device is pretty difficult. Not really the "at a glance" mentality that Google was going for.
Long term, I'm looking to get Lollipop and Marshmallow working, and eventually develop a Glass-friendly UI on top of those based off of what the community thinks Glass should have been. Only a handful of people seem to be interested, but it's a really great side project for me.
That said, I'm not currently accepting donations. If the cost of my build box gets too high then I may reconsider, but I honestly don't want people investing in something that I actually have very little time to work on.
Click to expand...
Click to collapse
I believe you have opened the flood gates. It may reinvigorate the community and get some great stuff out there. Thanks!
kevkid said:
I believe you have opened the flood gates. It may reinvigorate the community and get some great stuff out there. Thanks!
Click to expand...
Click to collapse
I certainly hope so! Show me something cool!
The first Lollipop build has been uploaded and the OP has been updated to reflect the changes. During development, I stumbled upon a project whose focus is to maintain AOSP for OMAP4 CPUs (which Glass happens to use). Coincidentally, their development started only a few months ago, and is ready for us to use! I commend the developers of OMAP4-AOSP - without them, our progress would take much longer.
The newly uploaded image is based on their project. Don't worry, it's still very much AOSP. Up next - Marshmallow.
So camera doesn't work on 8.1 custom ROMs? Tried RR, it was very dark and I received a can't connect to the camera error, and on dotOS the image's normal, but I also received that error. I assume there are no workarounds for the lag before turning flashlight on?
EDIT: Nevermind, it started working after I disabled HDR. Sucks that I can't use it now.
EDIT 2: Only problem I noticed is WhatsApp Web's camera's laggy, so I'm currently unable to use it.
Hyoretsu said:
So camera doesn't work on 8.1 custom ROMs? Tried RR, it was very dark and I received a can't connect to the camera error, and on dotOS the image's normal, but I also received that error. I assume there are no workarounds for the lag before turning flashlight on?
EDIT: Nevermind, it started working after I disabled HDR. Sucks that I can't use it now.
EDIT 2: Only problem I noticed is WhatsApp Web's camera's laggy, so I'm currently unable to use it.
Click to expand...
Click to collapse
Hey what's up,
A. I don't recommended using dot (Its a blind build , which means a dev without the device is could be causing damage to your device not his)
B. Download Footej Camera
C. You could use this video
It enables hal3 latest cam api.
D.We are devs we have our lives we will fix as soon as we can.
Good luck let me know.
infixremix said:
Hey what's up,
A. I don't recommended using dot (Its a blind build , which means a dev without the device is could be causing damage to your device not his)
B. Download Footej Camera
C. You could use this video
It enables hal3 latest cam api.
D.We are devs we have our lives we will fix as soon as we can.
Good luck let me know.
Click to expand...
Click to collapse
Also dotos is discontinued so go for fedray AOSP Extended ROM I'm using right now and works great!
infixremix said:
Hey what's up,
A. I don't recommended using dot (Its a blind build , which means a dev without the device is could be causing damage to your device not his)
B. Download Footej Camera
C. You could use this video
It enables hal3 latest cam api.
D.We are devs we have our lives we will fix as soon as we can.
Good luck let me know.
Click to expand...
Click to collapse
Flashing hal3 solved the camera on WhatsApp but also made normal camera app stop working, although Footej Camera works, as does HDR now. Flashlight also has no lag now, so it's all a matter of workarounds. Thanks for the help!
Hyoretsu said:
Flashing hal3 solved the camera on WhatsApp but also made normal camera app stop working, although Footej Camera works, as does HDR now. Flashlight also has no lag now, so it's all a matter of workarounds. Thanks for the help!
Click to expand...
Click to collapse
Use gcam for the better pics
Why do you reccomend not to use DotOS?
infixremix said:
Hey what's up,
A. I don't recommended using dot (Its a blind build , which means a dev without the device is could be causing damage to your device not his)
B. Download Footej Camera
C. You could use this video
It enables hal3 latest cam api.
D.We are devs we have our lives we will fix as soon as we can.
Good luck let me know.
Click to expand...
Click to collapse
hi, when you say that "it could be causing damage to your device not his", can DotOs contain virus or only because the developer hasn´t the device?. Now I´m using DotOS and it works perfect for me, good battery, no major camera problems (sometimes a bit buggy on instagram with front camera) and stability.
DotOS is now being maintained again. Gotta figure out why I can't receive calls but am able to make them now.
EDIT: Had to stop using LTE and go back to using 3G for network. Also if anyone's having problems with TitaniumBackup, just select your microSD with DocumentProvider storage and it should work.
Hyoretsu said:
DotOS is now being maintained again. Gotta figure out why I can't receive calls but am able to make them now.
EDIT: Had to stop using LTE and go back to using 3G for network. Also if anyone's having problems with TitaniumBackup, just select your microSD with DocumentProvider storage and it should work.
Click to expand...
Click to collapse
Dotos isn't now I've moved on....
durc12 said:
hi, when you say that "it could be causing damage to your device not his", can DotOs contain virus or only because the developer hasn´t the device?. Now I´m using DotOS and it works perfect for me, good battery, no major camera problems (sometimes a bit buggy on instagram with front camera) and stability.
Click to expand...
Click to collapse
Dot OS is a kang they steal paid work . Yes there probably is a virus in there
infixremix said:
Dot OS is a kang they steal paid work . Yes there probably is a virus in there
Click to expand...
Click to collapse
If this were true it wouldn't be allowed on xda
Anything that requires payment eg premium apps or anything that circumvents/hacks apps to allow free use is banned from xda
Some roms may take freely open source code from other roms and collate it into a single rom
Examples of this in the past have been paranoid android & open kang project
This is totally acceptable as it's open source
If you feel DotOs is breaking licensing rules or including paid for apps you should report it to the moderators for investigation
TheFixItMan said:
If this were true it wouldn't be allowed on xda
Anything that requires payment eg premium apps or anything that circumvents/hacks apps to allow free use is banned from xda
Some roms may take freely open source code from other roms and collate it into a single rom
Examples of this in the past have been paranoid android & open kang project
This is totally acceptable as it's open source
If you feel DotOs is breaking licensing rules or including paid for apps you should report it to the moderators for investigation
Click to expand...
Click to collapse
I have proof , Ive shown proof. Even if its open source theherefore they kanged. There settings icons are taken from a payed sub theme .
infixremix said:
I have proof , Ive shown proof. Even if its open source theherefore they kanged. There settings icons are taken from a payed sub theme .
Click to expand...
Click to collapse
True :/
infixremix said:
I have proof , Ive shown proof. Even if its open source theherefore they kanged. There settings icons are taken from a payed sub theme .
Click to expand...
Click to collapse
Bar0ns600 said:
True :/
Click to expand...
Click to collapse
Open source is meant to be used in other projects - that's the whole point of being open sourced - Anyone can freely use & modify the code
There is nothing wrong with this
With regards to the images - These images maybe licenced - The paid app may have got these images from a licensed source to which DotOs may have also obtained them from
You would need to know who has the rights to these images
As long as the code of the theme is not used (if the code is not open sourced) or the apk of the theme has not been integrated, unless you can prove these images were designed & created by the theme makers & they own the copyright to these images you would have a hard job convincing me if I was a moderator
Report it & see what the response from xda is if you have concerns
Now the phone restarts whenever I take a photo. It may take some time for the app to crash and the interface restart, but soon after it restarts.
TheFixItMan said:
Open source is meant to be used in other projects - that's the whole point of being open sourced - Anyone can freely use & modify the code
There is nothing wrong with this
With regards to the images - These images maybe licenced - The paid app may have got these images from a licensed source to which DotOs may have also obtained them from
You would need to know who has the rights to these images
As long as the code of the theme is not used (if the code is not open sourced) or the apk of the theme has not been integrated, unless you can prove these images were designed & created by the theme makers & they own the copyright to these images you would have a hard job convincing me if I was a moderator
Report it & see what the response from xda is if you have concerns
Click to expand...
Click to collapse
You Clearly dont understand open source
infixremix said:
You Clearly dont understand open source
Click to expand...
Click to collapse
Haha its you that doesn't understand - let me give you the dictionary definition
open-source
denoting software for which the original source code is made freely available and may be redistributed and modified.
So by that definition it is perfectly acceptable to use open source coding, modify it & redistribute it under the same open source guidelines so by using other roms freely available open source code in your rom is perfectly acceptable
For example alot of roms use coding from lineageOS or omnirom
Please Google open source definition & terms of use for more details
TheFixItMan said:
Haha its you that doesn't understand - let me give you the dictionary definition
open-source
denoting software for which the original source code is made freely available and may be redistributed and modified.
So by that definition it is perfectly acceptable to use open source coding, modify it & redistribute it under the same open source guidelines so by using other roms freely available open source code in your rom is perfectly acceptable
For example alot of roms use coding from lineageOS or omnirom
Please Google open source definition & terms of use for more details
Click to expand...
Click to collapse
You are so fixed into your view its unreal . Basically your saying people are aloud to copy and paste code from someone else and it fits under fair use of open source. It doesnt and its highly doomed on. Lineage OS and Omni both get credited and commits are kept within authorship. Even if its open source . Else you are stealing someone elses work.
infixremix said:
You are so fixed into your view its unreal . Basically your saying people are aloud to copy and paste code from someone else and it fits under fair use of open source. It doesnt and its highly doomed on. Lineage OS and Omni both get credited and commits are kept within authorship. Even if its open source . Else you are stealing someone elses work.
Click to expand...
Click to collapse
Like I said - it needs to be distributed under the same terms as the original source
In your example you are talking about apache open source license
More details can be found
https://en.m.wikipedia.org/wiki/Open-source_software
Apache licence guide is here
https://en.m.wikipedia.org/wiki/Apache_License
Like other free software licenses, the license allows the user of the software the freedom to use the software for any purpose, to distribute it, to modify it, and to distribute modified versions of the software, under the terms of the license, without concern for royalties.
Click to expand...
Click to collapse
The difference being in this licence any copyrighted trademark & names must be maintained
So you have the right to freely use distribute & modify any of the code as long as you provide the source for your changes & have shown the changes from the original source & you haven't changed or modified copyrighted or trademark parts without the original owners consent
This fits with your example of authorship
TheFixItMan said:
Like I said - it needs to be distributed under the same terms as the original source
In your example you are talking about apache open source license
More details can be found
https://en.m.wikipedia.org/wiki/Open-source_software
Apache licence guide is here
https://en.m.wikipedia.org/wiki/Apache_License
The difference being in this licence any copyrighted trademark & names must be maintained
So you have the right to freely use distribute & modify any of the code as long as you provide the source for your changes & have shown the changes from the original source & you haven't changed or modified copyrighted or trademark parts without the original owners consent
This fits with your example of authorship
Click to expand...
Click to collapse
Dot is doesn't fit within this authorship they have admitted them selves
A working Gcam for our phone, because we deserve it:
BSG GCam APKs - Google Camera Port
Modified Google Camera app by BSG.
www.celsoazevedo.com
(always use this version: org.codeaurora.snapcam)
Compared to the stock camera, the shutter is faster and the colours are somewhat more vibrant. Haven't had a chance to compare night modes yet.
If you have an XML setup to recommend, please do share.
stazz83 said:
A working Gcam for our phone, because we deserve it:
BSG: MGC_8.1.101_A9_PV0h
Download MGC_8.1.101_A9_PV0h by BSG.
www.celsoazevedo.com
(always use this version: org.codeaurora.snapcam)
Compared to the stock camera, the shutter is faster and the colours are somewhat more vibrant. Haven't had a chance to compare night modes yet.
If you have an XML setup to recommend, please do share.
Click to expand...
Click to collapse
Nice thanks! Do you know how to set it as the default camera app? I tried disabling the op camera app, but now I cannot open my camera from my lock screen.
jprattnu said:
Nice thanks! Do you know how to set it as the default camera app? I tried disabling the op camera app, but now I cannot open my camera from my lock screen.
Click to expand...
Click to collapse
The option should be under app info > advanced settings.
Update: I have tested the latest BSG's version of 8 April and it works as well.
Just make sure you download the org.codeaurora.snapcam version from this page:
BSG: MGC_8.1.101_A9_GV1zfix
Download MGC_8.1.101_A9_GV1zfix by BSG.
www.celsoazevedo.com
Weird how 4K 60fps only works on the ultrawide camera and not the main camera.
Is there any gcam mod that allows to record 8k and 4k/120fps? BTW I tried many mods and I did not find any with all functionalities available: all cameras, motion photos, night sight etc. If motion photos available, only single camera can be used, etc.
I also don't understand why they decided to remove all languages other than English from all mods. Original Gcam supports many languages.
giaur said:
Is there any gcam mod that allows to record 8k and 4k/120fps? BTW I tried many mods and I did not find any with all functionalities available: all cameras, motion photos, night sight etc. If motion photos available, only single camera can be used, etc.
Click to expand...
Click to collapse
Not at the moment, as far as I know but our device's release happend less than a month ago so the development is still in early stages. BSG is quite fast at updates so hopefully it'll eventually happen.
giaur said:
I also don't understand why they decided to remove all languages other than English from all mods. Original Gcam supports many languages.
Click to expand...
Click to collapse
I guess that way is much more simple and if that's the trade-off for faster updates than I'm very happy with it.
stazz83 said:
I guess that way is much more simple
Click to expand...
Click to collapse
What is much more simple? Additional languages strings are original from Google, no need to touch them. Of course, additional custom settings will appear in English only, because they won't be translated.
Additional effort required to remove all translations. So it's opposite to what you are saying
What's the difference between the org.codeaurora.snapcam and the com.google.android.GoogleCameraEng apks?
Was wondering the same... Thank you.
JCDentonMale said:
What's the difference between the org.codeaurora.snapcam and the com.google.android.GoogleCameraEng apks?
Click to expand...
Click to collapse
JCDentonMale said:
What's the difference between the org.codeaurora.snapcam and the com.google.android.GoogleCameraEng apks?
Click to expand...
Click to collapse
That's the package signature. On some phones, using the Snapcam one allows access to the auxiliary cameras (ultrawide, telephoto).
jericho246 said:
That's the package signature. On some phones, using the Snapcam one allows access to the auxiliary cameras (ultrawide, telephoto).
Click to expand...
Click to collapse
So IOTW, the snapcam is preferred for the 9 Pro then? Also, can anybody find a way to track that specific release somehow incase it updates? Thank you!
Edit - what is an XML setup btw?
jprattnu said:
So IOTW, the snapcam is preferred for the 9 Pro then?
Click to expand...
Click to collapse
I think so, yes. I read Snapcam is recommended for phones from BBK-owned smartphone brands. However keep in mind a brand could "block" the access to auxiliary cameras at any moment. For example Samsung blocked access to the selfie camera, so in GCam ports, the selfie camera just does not work on Samsungs... Not sure if they have fixed it, but I know it's been a problem for Samsung users.
jprattnu said:
Also, can anybody find a way to track that specific release somehow incase it updates? Thank you!
Click to expand...
Click to collapse
I don't think there's a way to track it, just gotta visit the celsoazevedo page from time to time. Although most updates are minor, so don't worry about that.
jprattnu said:
Edit - what is an XML setup btw?
Click to expand...
Click to collapse
You can download a XML file, and import it to the GCam app. It will import settings from the file, so if you find a XML file for the 9 Pro BSG Gcam port, just download it and import it via the app. Also you can create XML files yourself, and share them if you want as well.
jericho246 said:
I think so, yes. I read Snapcam is recommended for phones from BBK-owned smartphone brands. However keep in mind a brand could "block" the access to auxiliary cameras at any moment. For example Samsung blocked access to the selfie camera, so in GCam ports, the selfie camera just does not work on Samsungs... Not sure if they have fixed it, but I know it's been a problem for Samsung users.
Click to expand...
Click to collapse
Some manufacturers have even coded things to prevent third-party cameras from using the phone's full camera resolution capabilities. On OnePlus devices they could be locked to 12 MP, even the main camera.
jprattnu said:
So IOTW, the snapcam is preferred for the 9 Pro then? Also, can anybody find a way to track that specific release somehow incase it updates? Thank you!
Edit - what is an XML setup btw?
Click to expand...
Click to collapse
Here is the updated files from the site that does all the gcam mods https://www.celsoazevedo.com/files/android/google-camera/dev-bsg/
There is no configs anyone has done yet here is my saved one with my settings if you wish to try it, only changed lens device settings and interface settings, nothing modified for actual photo adjustments.
To apply go into setting and look for load xml then pick it from the file picker
JCDentonMale said:
What's the difference between the org.codeaurora.snapcam and the com.google.android.GoogleCameraEng apks?
Click to expand...
Click to collapse
me too ...
jeudecon said:
me too ...
Click to expand...
Click to collapse
JCDentonMale said:
What's the difference between the org.codeaurora.snapcam and the com.google.android.GoogleCameraEng apks?
Click to expand...
Click to collapse
jprattnu said:
Was wondering the same... Thank you.
Click to expand...
Click to collapse
Nothing, really. They just have different signatures. If you find that certain additional modules (Magisk flashables that add or enhance a device's camera functions) don't work, try the other. Some devices have a camera version signed specifically for them (ie, Samsung phones) because of this. It just happens that the snapcam signature seems to work best on our device.
I'm having some nasty issues with a strong lilac purple pink RAW files from Gcam recently. It makes it unusable. It worked fine before but suddenly this problem started happening, perhaps it came after a system update. :/
/ Magnus
stazz83 said:
A working Gcam for our phone, because we deserve it:
BSG: MGC_8.1.101_A9_PV0h
Download MGC_8.1.101_A9_PV0h by BSG.
www.celsoazevedo.com
(always use this version: org.codeaurora.snapcam)
Compared to the stock camera, the shutter is faster and the colours are somewhat more vibrant. Haven't had a chance to compare night modes yet.
If you have an XML setup to recommend, please do share.
Click to expand...
Click to collapse
I tried this and the colors were way to bright and inaccurate
Rebelwolf4622 said:
I tried this and the colors were way to bright and inaccurate
Click to expand...
Click to collapse
We'll, it's not a secret that Google's image processing slightly saturates the colours and beautifies photos. Not a bad thing imho.
Anyhow, BSG keeps releasing new builds, the latest one dated today:
BSG: MGC_8.1.101_A9_GV1zfix
Download MGC_8.1.101_A9_GV1zfix by BSG.
www.celsoazevedo.com