Related
The similar threads weren't of any help on this issue from what I could tell, and I'm sure it's something that's a straight forward answer, but I really just wanted to know if there's any way to fix my camera on my G2. The issue I'm having is that while using the Un-Official CM9-RC2 build I'm having serious issues with the camera taking a bit low quality images from time to time, as well as being unable to scan in bar codes due to the fact that it's unable to auto-focus, or even focus on anything for that matter.
If more information needs to be provided, I'll be glad to. I don't consider myself an expert on Android development, so excuse me for this question. Thanks!
Wolfy9247 said:
The similar threads weren't of any help on this issue from what I could tell, and I'm sure it's something that's a straight forward answer, but I really just wanted to know if there's any way to fix my camera on my G2. The issue I'm having is that while using the Un-Official CM9-RC2 build I'm having serious issues with the camera taking a bit low quality images from time to time, as well as being unable to scan in bar codes due to the fact that it's unable to auto-focus, or even focus on anything for that matter.
If more information needs to be provided, I'll be glad to. I don't consider myself an expert on Android development, so excuse me for this question. Thanks!
Click to expand...
Click to collapse
First of all you are on an unofficial cm build so you should no get every thing working perfect, try clearing camera data in settings if it does not help
then its certainly your rom but also try clearing cache if it still does not go then maybe you have to change the rom, there are many roms that have camera working in good shape check the developer section an un-official CM will not help always read the details of rom before downloading them every rom has its good and bad so its your choice looking at the kind of roms here i dont think CM is gonna help some dev use them as a base to build stable roms try those
you can try andromadus audacity or mimicry ics and for sense try gen y visionx there are sooo many good roms out there why stick to un -official ones HOPE I HELPED
strip419 said:
First of all, you're on an un-official CM build so you shouldn't get everything working perfectly, however I'd recommend clearing the camera data in your settings if it doesn't help. If that doesn't work, try clearing the cache. If those don't work, it's most certainly your ROM, and you should maybe considering switching to a ROM that has the camera working in good shape. Check the developer section, an un-official CM will not always work, so read the details of the ROM before downloading them to determine whether it's good or bad.
You can always try Andromadus, Audacity, or Mimicry ICS and for Sense you might try gen y visionx. There are so many good ROMS out there, why stick to the un-official ones? Hope I helped!
Click to expand...
Click to collapse
(The quoted post was edited for more clarity and understanding while I was trying to read over it.)
The camera app doesn't have any cache, I did clear the data but the problem still persists. I'll consider using another ROM, however I do believe it's mainly the camera drivers for ICS for G2 that are just rubbish at the moment though. I was mainly seeing if anyone had any fixes or recommendations besides just switching.
Wolfy9247 said:
(The quoted post was edited for more clarity and understanding while I was trying to read over it.)
The camera app doesn't have any cache, I did clear the data but the problem still persists. I'll consider using another ROM, however I do believe it's mainly the camera drivers for ICS for G2 that are just rubbish at the moment though. I was mainly seeing if anyone had any fixes or recommendations besides just switching.
Click to expand...
Click to collapse
You're right, the quality won't be as good in ICS as it was in GB. I can't say the same for JB, but for ICS we need(ed) major changes/rewrites to the camera drivers in general.
Developers tried tirelessly to get the camera codes from Qualcomm, not sure they gave them out so the dev had to work around it. But some sense ics roms have very good camera quality and HD video . I am on gen y vision X you can try that
Sent from my HTC Desire Z using xda premium
Hi! This is my first mod for Android; a partially working attempt at getting the Samsung camera (from the leaked 4.2.2 ROM; XUFME7) to work on AOSP ROMs. Not a skin, this is the full camera along with most of the features!
Want to see it in action? No screenshot - it looks exactly the same as on TW ROMs - but here's a video. http://www.youtube.com/watch?v=mYX4PSVDiIU Apologies for the terrible quality, but it's hard to film a phone with the Nexus 7's front camera, and I couldn't find a decent screen capture app :<
--
Port for Android 4.3
Beta version NOW AVAILABLE, click here for details + download: http://forum.xda-developers.com/showpost.php?p=46566446&postcount=135
It doesn't work as well as the 4.2.2 version - in particular, video recording is 100% broken, even in the AOSP camera - but you can still try it out if you don't mind this!
--
Port for Android 4.2.2
Working/Non-Working Features List:
What Works:
Front and back cameras
"Wand" Filters
Flash
Auto & Macro focus modes
Tap-to-focus
White Balance options
GPS tagging
Gallery shortcut (uses AOSP Gallery)
Shooting modes:
Single Shot
Best Photo
Face Detection
HDR
Beauty
Smile Shot
Low light
Possibly Working, depending on kernel:
(These features require that the mediaserver process can write to /sdcard (for burst shot/best face) and /data (for panorama). The only way to change this is using a modified kernel with an init.rc which gives it that access. In my experience, with Googy-Max kernel, Panorama works but the other two don't. Your mileage may vary.)
Burst shot
Best Face
Panorama
Not Working, may be fixed later:
Shutter sounds
Automatic mDNIe / screen brightness adjustment
Not Working, unlikely to be fixed:
Camcorder
Share Shot
Voice recognition
Weather/city photo tagging in the media database (what's this used for exactly?)
Untested:
Buddy Photo Share
External SD card
Download:
Download:
This patch is ONLY compatible with AOSP-based 4.2.2 ROMs running on the GT-I9300 and GT-I9300T; the international models of the Galaxy S3 (Exynos chip, no LTE)
CWM zip: http://d-h.st/sg8 (5.26 MB / MD5: f53d603f49de1bb0aba90546b9bbc1ce)
Notes:
This patch has only been tested on RootBox 4.1. Please let me know if you have trouble using it on any other ROM!
Disclaimer:
This is an experimental patch, and you install it at your own risk! I am not responsible for anything that occurs as a result of this. Always make backups.
Installation:
You need a recovery that allows you to install .zip files; most likely CWM or TWRP. But you probably already have one of these if you're running AOSP on this phone
1. Boot into recovery mode: turn the phone off, hold down VolumeUp+Home and then press the power button
2. Make a Nandroid backup (not obligatory, but recommended in case something goes wrong!)
3. Flash the camera mod zip
4. Wipe the Cache and Dalvik Cache - just in case
Hope you enjoy it! Now go out and take some awesome photos
Changelog:
20th July 2013: Released first version. Camera (+ most features) is functional. Camcorder appears but does not record successfully.
22nd July 2013: Released new version which should work on any AOSP ROM, instead of needing a custom built ROM.
17th October 2013: 4.3 beta release is out.
Hm, I'm guessing that the picture quality isn't different from the AOSP camera app and this tho there still is missing sources from Samsung that we'll never get.
Otherwise. Nice mod!
Eleve11 said:
Hm, I'm guessing that the picture quality isn't different from the AOSP camera app and this tho there still is missing sources from Samsung that we'll never get.
Otherwise. Nice mod!
Click to expand...
Click to collapse
Thank you
I've seen people talk about how the camera on AOSP is worse because of missing sources, but I'm not sure what sources these are. The Samsung kernel module is open source, and this mod replaces all the user space code related to the camera - as far as I know, anyway - with the TW versions. (Please correct me if I'm wrong on this )
This is purely anecdotal and rather hard to test accurately, but I never noticed much of a difference in picture quality between AOSP and TW, I just wanted the camera app because of the extra modes and options that are really useful.
I was not Using AOSP based ROMs only for the sake of camera.
But now, i can use any ROM i want..
Thannks man.. This is super cool.. will test this ASAP..
Well, the full version method didn't work for me on todays' CM nightly build. I installed it following the procedures, and then opened the camera app. The screen went black, and then froze. I restarted the phone, and it kept looping on the boot animation
Luckily I don't delete the CM updater temporary files, so I was able to boot into recovery and re-install the 'stock' CM build. Also, despite the fact that I mostly understood the instructions, they were quite confusing!
does hdr work? is it like the tw cam?
Sent from my GT-I9300 using xda app-developers app
kuci06 said:
Okay, so I just flashed the modified Rootbox rom, and the burst shot feature does not work properly. The little counter bar comes up, but doesn't shoot photos at all. Also breaks functionality after that, not even the close button works.
Click to expand...
Click to collapse
Just as I expected I'll have to figure out a fix for this somehow...
Writing to /data does seem to work, so maybe I can patch the Samsung lib to store burst shots there, and move them to the SD card from the camera apk :x
iSasha said:
Well, the full version method didn't work for me on todays' CM nightly build. I installed it following the procedures, and then opened the camera app. The screen went black, and then froze. I restarted the phone, and it kept looping on the boot animation
Luckily I don't delete the CM updater temporary files, so I was able to boot into recovery and re-install the 'stock' CM build. Also, despite the fact that I mostly understood the instructions, they were quite confusing!
Click to expand...
Click to collapse
Apologies for the confusing instructions :< I think I got carried away a bit with the technical details!
You cannot use this mod with an existing build of another ROM (like the CM nightlies) unless it has been compiled with the source code patches I provided. Samsung's camera libs are not compatible with normal AOSP builds, but my patches change the interface in AOSP to fix that.
It's a bit of a lofty goal but I hope that other ROMs will some day include these patches, because it doesn't affect normal camera operation, and it allows you to use the Samsung camera if you flash the appropriate libs...
I would like to provide builds of other ROMs in the future, but this is difficult to do because it takes me 2-3 days to download the source code of each ROM and 8 hours to compile it from scratch - this is why I only have RootBox right now. So it would be extremely helpful if other developers would integrate this.
Notor1ouS- said:
does hdr work? is it like the tw cam?
Click to expand...
Click to collapse
HDR works perfectly Exactly like in the TW 4.2 camera, you get an Options menu with Normal/Strong HDR effect and with the option to save original/HDR photo or just HDR.
Treeki said:
Apologies for the confusing instructions :< I think I got carried away a bit with the technical details!
You cannot use this mod with an existing build of another ROM (like the CM nightlies) unless it has been compiled with the source code patches I provided. Samsung's camera libs are not compatible with normal AOSP builds, but my patches change the interface in AOSP to fix that.
It's a bit of a lofty goal but I hope that other ROMs will some day include these patches, because it doesn't affect normal camera operation, and it allows you to use the Samsung camera if you flash the appropriate libs...
I would like to provide builds of other ROMs in the future, but this is difficult to do because it takes me 2-3 days to download the source code of each ROM and 8 hours to compile it from scratch - this is why I only have RootBox right now. So it would be extremely helpful if other developers would integrate this.
Click to expand...
Click to collapse
Oups... I just copied over the lib and camera files over using a root explorer app. I doubt that I'll have the patience to wait days to build it form source myself, but I'll be looking forward to see these libs integrated in future versions of CM!
"Not Working, unlikely to be fixed:
Camcorder"
is that a typo for "cam recorder" ? or cam recording is working just fine?
AvivEliyahu said:
"Not Working, unlikely to be fixed:
Camcorder"
is that a typo for "cam recorder" ? or cam recording is working just fine?
Click to expand...
Click to collapse
Camcorder is a term for video recorder.
Also op thanks this mod hope it gets implemented in the rom I'm using!
Sent from my GT-I9300 using xda app-developers app
@Treeki would you continue to publish updated Rootbox Nightlies with this camera every time Rootbox is updated?
EDIT: I also think you should move this to Android Development forum instead of apps and games because you are working on a ROM based of Rootbox sources... Not just the app itself..
Sent from my GT-I9300 using Tapatalk 2
sorry for quick quesrion...
if i merge this to rom, will it just replace the original cm camera or cm camera is still there and it make new icon for the sammy camera?
Sent from S3, power By Temasek'Rom and Kernel!
I'm quoting the answer provided on the Original Thread...
Treeki said:
.
It's a bit of a lofty goal but I hope that other ROMs will some day include these patches, because it doesn't affect normal camera operation, and it allows you to use the Samsung camera if you flash the appropriate libs...
.
Click to expand...
Click to collapse
If I'm not wrong it doesn't break CM Camera, it just helps Sammy camera to Partially work...
Sent from my GT-I9300 using Tapatalk 2
thanks~
Sent from S3, power By Temasek'Rom and Kernel!
jimbo77 said:
@Treeki would you continue to publish updated Rootbox Nightlies with this camera every time Rootbox is updated?
Click to expand...
Click to collapse
Hm.. that's something I hadn't thought about yet :x
I will try and publish a new one every few days but I don't have the resources to make daily builds, unfortunately...
Now that I have some more experience with the Android build system and I know exactly what needs to be changed, I'm going to look again at modifying the Samsung binaries to work with any AOSP ROM instead of doing this the other way round. That was my intention when I first started the project, but I changed tactics because I wasn't sure exactly how much I would need to modify.
I don't know if I'll succeed at this but I'll give it a shot ... If I could get it to work, it would be a much better solution because it should work on practically any ROM with just a flashable zip. Can't promise anything yet though :<
Treeki said:
Hm.. that's something I hadn't thought about yet :x
I will try and publish a new one every few days but I don't have the resources to make daily builds, unfortunately...
Click to expand...
Click to collapse
Well, the Rootbox Nightlies doesn't come out every day as well so I think it will be nicely timed with you, btw if you ever want a beta tester of some sort.. Shoot a PM and I'll be more than glad to help...
I'm a Rootbox user since long time so it will not affect me to try your builds...
Sent from my GT-I9300 using Tapatalk 2
Welp.
I was going to post a picture of myself facepalming... taken with the TW camera app, of course... but I figured XDA is just a bit too public for that.
It turned out that one single byte in mediaserver was all I needed to change for my original attempt from several days ago to work. I wish I had known that before I started all this stuff about compiling ROMs... I suppose it was a good learning experience, though. I really didn't expect the fix to be that simple.
So my final mod turns out to be much, much simpler:
- Use Samsung files, with one modified to add a version of Camera::connect that only takes one param
- Modify mediaserver to allocate a CameraService that is 12 bytes bigger than the AOSP version
I feel kinda dumb now. Oh well! Hindsight is 20/20. And... sometimes the simplest solutions turn out to be the right ones
I'll put together a CWM zip that should [hopefully] work on all ROMs and add it to the OP shortly! Now available. Please try it out and let me know how it goes, and what ROM you're using! Off to sleep now, at the very appropriate time of 9am...
It is working correctly on the temasek rom. Thanks a lot.
Treeki said:
Not Working, unlikely to be fixed:
Camcorder
Click to expand...
Click to collapse
first. really cool mod !!!! exactly what im waiting fot
Q
is it possible to change the shortcut to googlecam recorder , when we click on video?
and a shortcut to photosphere from sammys cam "scenes" would be cool
Gesendet von meinem GT-I9300 mit Tapatalk 2
Wow if this could be optimised with AOSP it will be perfect! Flashing it now.
Sent from my GT-I9300 using xda premium
I am sure this topic has been beaten to death already but I still wanted to share my experience with custom ROMs and finally going back to the STOCK ROM. If beginners want to try out Custom ROMs, may be they can read this beginner's post.
First the ritual - Android community is great. ROM developers are great minds at work! Thanks for doing all the hard work and showing me whats in the Custom ROM world.
I started out with simple rooting of my phone to get tethering (cheap on my part but I think I pay more than what my carrier offers). After rooting, custom ROM was just so tempting. So I tried a few - CM, AOKP, Carbon. Honestly, out of all, CM10.0 was the most stable for me. Things I loved:
1. Battery Life - Can't say enough. There is so much junk that runs in background on STOCK ROMs.
2. 4.2.2 JB - Better than 4.1.2 but then, not by miles.
3. Ability to flash ROMs over the weekends You know it.
4. Utilities like Titanium backup and others that needed Root access.
5. Tether - super like.
Things I hated:
1. Force closures - OMG I couldn't understand how the STOCK ROMs are so robust or Is it that the Apps are tested on Stock ROMs very well that they don't crash. Countless failures for Instagram, Email, Camera, BT etc.
2. Camera functionality - I give 10 out of 10 to Samsung in creating great camera app. I am a heavy smartphone camera user. The 4.2.2 camera app was so laggy on my GS3. The user interface sucked (circle). No meter mode. Bad panorama mode, HDR mode and worst low light photos.
3. On one of the custom ROMs, I had horrible issues with making and receiving phone calls (Yes it can go that bad).
4. Bluetooth pairing with devices. BT crashed a lot while music was interrupted with incoming calls.
All in all, I am now happy that I am back to the STOCK ROM with This Link Many thanks to the Member.
There is a lot of excitement and good things about the Custom ROMs but if you are like me who is not a super power user, there is a lot to consider before jumping.
Happy Monday!
In CM 10.1, the FC issues were fixed for me. This applies for most current AOSP roms. I have not had any issues with camera lag either. I will admit that the stock camera is more robust with options but there are third party apps that help minimize the feeling of loss.
Regarding testing, this is what goes on here. The difference is you see the testing phases while you do not with the manufacturer. In addition, many of the drivers and hardware info is proprietary so developing drivers that are stable can be a hit and miss affair.
On the same note, not every phone and user is the same and the experience will be different for each. ROMs will possibly work differently across the same models of phone due to minor variations in quality which are nearly impossible to catch during the manufacturing process due to nearly microscopic differences.
Sent from my SAMSUNG-SGH-I747
aybarrap1 said:
In CM 10.1, the FC issues were fixed for me. This applies for most current AOSP roms. I have not had any issues with camera lag either. I will admit that the stock camera is more robust with options but there are third party apps that help minimize the feeling of loss.
Regarding testing, this is what goes on here. The difference is you see the testing phases while you do not with the manufacturer. In addition, many of the drivers and hardware info is proprietary so developing drivers that are stable can be a hit and miss affair.
On the same note, not every phone and user is the same and the experience will be different for each. ROMs will possibly work differently across the same models of phone due to minor variations in quality which are nearly impossible to catch during the manufacturing process due to nearly microscopic differences.
Sent from my SAMSUNG-SGH-I747
Click to expand...
Click to collapse
Totally agree with the slight variations in experiences with Custom ROMs. But for some reason, my jump to 10.1 was not smooth with FCs and I quickly made a u-turn to 10.0 and then ultimately to the STOCK ROM. Camera Apps like Camera Zoom are very good and they do provide more options like Metering and time lapse (missing in STOCK), they are still not complete (simple example - I can't enable Panorama from CamerZoom). Nevertheless, the experience can be really amazing when things work out but really frustrating when they don't. STOCK has its problems like I am missing my Solid Battery life today :crying:
I think I'm about to go back to stock as well. While I love all the extra features that custom roms offer, all the tinkering and occasional bugginess can take away from the overall experience. At least for me, anyways.
I also had been doing it long enough that I felt really comfortable with all the flashing that I was doing, but would still make the occasional mistake (look at the hilarity I posted in the stupid questions thread today). I'm thinking I'll play it safe, at least for now, before I do something I regret.
Sent from my SGH-I747M using xda app-developers app
newmind02 said:
I think I'm about to go back to stock as well. While I love all the extra features that custom roms offer, all the tinkering and occasional bugginess can take away from the overall experience. At least for me, anyways.
I also had been doing it long enough that I felt really comfortable with all the flashing that I was doing, but would still make the occasional mistake (look at the hilarity I posted in the stupid questions thread today). I'm thinking I'll play it safe, at least for now, before I do something I regret.
Click to expand...
Click to collapse
It is in my opinion that even the stock roms have bugs. At seemingly random times, my alarm clocks on my AT&T S3 just didn't work when running stock. I was almost late for work 3 days in a row because of it (my alarm is set to repeat 5 times a week every week at the exact same time. I never turn it off). In addition, I get the occasional random battery drop that seems to have something to do with the switch between H+ and LTE when on a phone call.
I stuck with the stock rom for a while but now that AOSP roms are stable, I have switched. Whatever bugs are present do not affect me or they are so minor I work around it. It really comes down to what you find to be acceptable for you.
As far as being comfortable and making mistakes, I have done it as well. Being a flashing fiend has made me overconfident a few times and I botched several installs. Luckily I have been so busy of late, that my flashing desire has been on hold.
Never had any force closes.
Never had any lag
Never had any problems on custom Roms.
If you're experiencing and lag, force closes, you're MORE than likely doing something wrong on your end.
This phone doesn't lag. It should lag whatsoever. 1.5Ghz and 2Gs of ram does not create lag.
Touchwiz runs a LOT more stuff in the background.
Just follow instructions on how to flash, what to flash, and what to tweak. And I can guarantee you an awesome experience.
The camera as well. Just took some amazing lightning shots with 4.2.2 camera, on burst mode with 20 pictures taken in less then 3 seconds. No lag what's so ever.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
jayRokk said:
Never had any force closes.
Never had any lag
Never had any problems on custom Roms.
If you're experiencing and lag, force closes, you're MORE than likely doing something wrong on your end.
This phone doesn't lag. It should lag whatsoever. 1.5Ghz and 2Gs of ram does not create lag.
Touchwiz runs a LOT more stuff in the background.
Just follow instructions on how to flash, what to flash, and what to tweak. And I can guarantee you an awesome experience.
The camera as well. Just took some amazing lightning shots with 4.2.2 camera, on burst mode with 20 pictures taken in less then 3 seconds. No lag what's so ever.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I concur
Sent from my SAMSUNG-SGH-I747
techmine said:
I am sure this topic has been beaten to death already but I still wanted to share my experience with custom ROMs and finally going back to the STOCK ROM. If beginners want to try out Custom ROMs, may be they can read this beginner's post.
First the ritual - Android community is great. ROM developers are great minds at work! Thanks for doing all the hard work and showing me whats in the Custom ROM world.
I started out with simple rooting of my phone to get tethering (cheap on my part but I think I pay more than what my carrier offers). After rooting, custom ROM was just so tempting. So I tried a few - CM, AOKP, Carbon. Honestly, out of all, CM10.0 was the most stable for me. Things I loved:
1. Battery Life - Can't say enough. There is so much junk that runs in background on STOCK ROMs.
2. 4.2.2 JB - Better than 4.1.2 but then, not by miles.
3. Ability to flash ROMs over the weekends You know it.
4. Utilities like Titanium backup and others that needed Root access.
5. Tether - super like.
Things I hated:
1. Force closures - OMG I couldn't understand how the STOCK ROMs are so robust or Is it that the Apps are tested on Stock ROMs very well that they don't crash. Countless failures for Instagram, Email, Camera, BT etc.
2. Camera functionality - I give 10 out of 10 to Samsung in creating great camera app. I am a heavy smartphone camera user. The 4.2.2 camera app was so laggy on my GS3. The user interface sucked (circle). No meter mode. Bad panorama mode, HDR mode and worst low light photos.
3. On one of the custom ROMs, I had horrible issues with making and receiving phone calls (Yes it can go that bad).
4. Bluetooth pairing with devices. BT crashed a lot while music was interrupted with incoming calls.
All in all, I am now happy that I am back to the STOCK ROM with This Link Many thanks to the Member.
There is a lot of excitement and good things about the Custom ROMs but if you are like me who is not a super power user, there is a lot to consider before jumping.
Happy Monday!
Click to expand...
Click to collapse
I tend to go back and forth between CM10.1 and Stock.
The biggest thing CM misses for me is the camera. Call me a fanboy but I really like what Samsung did to their camera optimizations in TW.
That being said, I don't like TW very much but a custom launcher and a few minor tweaks can make TW tolerable.
For apps running in the background I highly recommend Greenify for keeping apps dormant when you're not using them.
Titanium Backup also has a feature called Freeze that basically does the same thing as Greenify except it takes the app and prevents it from being used at all.
This is good for apps that you never use that come preloaded on the GS3 (AT&T and Samsung bloatware).
Hey guys I'm a little sad :/
As many of you would know G3 camera support on AOSP is in a really poor condition.
The driver made by LG isn't present on AOSP, making it an utter disappointment after you get over the thrilling speed compared to LG's own rom.
I know the G2 camera has been ported, I also found a post requesting a port for G3 (last response in october), but that didn't happen.
I don't know in detail how hard the problem is, but I imagine that it should be doable unless of course this is completely proprietary code by LG.
I am imagining that you could simply move the right apk's to the phone and try out if something will work, unless of course it is in the LG kernel itself, but then maybe an LG kernel could be used with AOSP, who knows.
The guy who is working on LG XCam for both the G2 and G3 already said he will focus on LG's own roms, so that a no go as well. I have really been looking, but nothing seems to be up.
So is anyone working on this and does anyone know in detail how hard it is to solve?
Coming from Nexus 5 with SlimKat on it, LG G3 seems like the slowest thing known to man, haha, so AOSP is a must, preferably with a good camera as well.
1 moving some files wil not work start by understanding how a total framework works.
2 ya you can do kernel but do you know how it works with driver and app .
3 if you love the cam so mutch why not build a rom with lg framework ?
Jhinta said:
1 moving some files wil not work start by understanding how a total framework works.
2 ya you can do kernel but do you know how it works with driver and app .
3 if you love the cam so mutch why not build a rom with lg framework ?
Click to expand...
Click to collapse
1. I don't think the whole framework needs to be understood to port the functionality of the camera
2. No I don't, but I think the kernel is actually containing the driver, if I understand how a Linux Kernel works, but I could be wrong, since I don't know for sure on Android. Furthermore I was thinking both (parts of) the kernel and camera app could be applied to AOSP.
3. It's not the camera app or LG framework, it's the fact that the camera does not work properly on AOSP. I don't care about settings, GUI or functionality, but it simply performs like a phone from 5 years ago with 15 fps video and poor colors and constrast in images.
Hi, I am looking for the best camera app for my D855 with Dirty Unicorn 7.1.2. Can you help me? there is an original camera's porting for aosp?
gianm.93 said:
Hi, I am looking for the best camera app for my D855 with Dirty Unicorn 7.1.2. Can you help me? there is an original camera's porting for aosp?
Click to expand...
Click to collapse
what should i do?
Impossible.
I have tried htc 10 camera port, snap camera hdr, google camera. They are all the same. The best alternative is lg g2 camera port. You can see the difference in low light conditions.
This one:
https://www.androidfilehost.com/?w=files&flid=146615
You have to downgrade your display resolution to 1920x1080 @ 420 dpi.
Coolgoly said:
This one:
https://www.androidfilehost.com/?w=files&flid=146615
You have to downgrade your display resolution to 1920x1080 @ 420 dpi.
Click to expand...
Click to collapse
Why I have to downscale the screen resolution?
tylerberk said:
Impossible.
Click to expand...
Click to collapse
Why the porting is impossible?
gianm.93 said:
Why the porting is impossible?
Click to expand...
Click to collapse
LG didn't release the sources.
Why there is LG G2 camera ported (without certain features, but it is), and there aren't any g3 camera port :/
TheBerebian said:
Why there is LG G2 camera ported (without certain features, but it is), and there aren't any g3 camera port :/
Click to expand...
Click to collapse
Because no one did it. You can try.
gianm.93 said:
Why I have to downscale the screen resolution?
Click to expand...
Click to collapse
Because G2 has a full hd display and this app comes from it.
If you run it on a qhd display like the G3 one you wiil encounter an incorrect visualization.
It's easy to change the resolution and dpi
using terminal emulator,if the phone is rooted
Coolgoly said:
Because G2 has a full hd display and this app comes from it.
If you run it on a qhd display like the G3 one you wiil encounter an incorrect visualization.
It's easy to change the resolution and dpi
using terminal emulator,if the phone is rooted
Click to expand...
Click to collapse
Easy DPI Changer works as well, and it is best to use lg g3 on 1080p res makes the phone much more fast and stable.
Hi, I also miss the superior quality of camera from stock ROM. I was trying to follow some tutorials on porting vendor apps to AOSP (getting the camera apk file, some libraries, framework files and permission files and compiling them all together), but it never worked with the camera. Sadly, I'm pretty sure that if it was possible, somebody smarter would have already done it. With LG being jerks and not releasing the sources, we most likely won't get the stock camera on AOSP, ever. That being said, I can think of four possible ways of dealing with the situation.
First, use stock ROM only. Yes, I know, that sucks. Or stock based ROM such as Fulmics, if you really think there is a difference between these two.
Second option is multirom. I was using it for last few months with LineageOS as primary and stock as secondary ROM, and everytime when I knew I would be taking some photos (when I went to concerts/holidays/celebrations/some unusual stuff), I booted to stock ROM and was good to go.
Third option is to have a TWRP backup of your current system and of stock ROM and restoring the backup of the ROM you want to use (AOSP for daily usage, stock for the days you know you'll be using your camera a lot). The previous (multirom) option is faster and easier to manage, and you can always add new ROMs and experiment as you wish. However, it requieres a custom recovery and I wasn't able to pass SafetyNet test with multirom and LineageOS with Magisk. Also, multirom makes a little bit of a mess at your /system partition. This third option (backing up/restoring system in TWRP) takes longer, the backups are large, but I'm liking that a bit more for some reason - it feels "cleaner" and more transparent to me.
The last option is to be on AOSP and use a camera app of your choice which you find has the best quality. I was experimenting with this a lot and tried dozens of camera apps (including the LG G2 camera port). Honestly, most of the photos were about the same quality. Even the G2 camera wasn't better than the rest I tested. I also compared the test pictures to stock camera (yes, I took the time to reboot to my secondary ROM for every test I was making at that time) and I was very sad that nothing was close to the stock camera quality. LG really does some magical post processing which works like a charm and looks really good. Anyways, after the tests I decided to stick with Snap Camera HDR. It has a trial and a paid version on the Play Store, in case you want to give it a shot. At good light conditions, the photos are actually comparable to stock camera. There is tons of settings to play with. It has a special "LG mode", which actually works even on AOSP ROMs and enables some LG specific features. It can also record 4K videos with stabilization. If you give it a try and really look into the settings (I recommend going also to the developer's website, where every option in the settings is described), you might end up with decent stock camera replacement. It took me about an hour to go through all the settings, but I'm fairly satisfied with the photos now. Although it has been last updated almost a year ago on the Play Store, there is a much more recent beta version here on the xda forums.
tl;dr I believe that porting stock camera app to AOSP is impossible. If you want stock camera quality, you really have to use stock ROM one way or another (either be on stock, or have a stock ROM TWRP backup and restore it whenever you want to take a good photo, or use multirom to switch your current ROM more quickly). If you want to use AOSP exclusively, I recommend Snap Camera HDR.
felmaster said:
Second option is multirom. I was using it for last few months with LineageOS as primary and stock as secondary ROM, and everytime when I knew I would be taking some photos (when I went to concerts/holidays/celebrations/some unusual stuff), I booted to stock ROM and was good to go.
Click to expand...
Click to collapse
There's another option similar (or not) to multirom:
For installing multiple ROMs I use DualBootPatcher, a great method devised originally for the SGS4, but available for a number of devices now, including our G3. I highly recommend it, it seems cleaner than multirom to me and more user friendly. It is possible to flash ROMs from within the app (they have to be patched first, this also happens inside the app, hence the name), backup, restore and more. There may be some hiccups now and then, but all in all it works smoothly.
Just search the LG G3 forums for DualBootPatcher, there's a thread with download links, description and how-to.
LG G3 AOSP Camera Comparison
felmaster said:
Hi, I also miss the superior quality of camera from stock ROM. I was trying to follow some tutorials on porting vendor apps to AOSP (getting the camera apk file, some libraries, framework files and permission files and compiling them all together), but it never worked with the camera. Sadly, I'm pretty sure that if it was possible, somebody smarter would have already done it. With LG being jerks and not releasing the sources, we most likely won't get the stock camera on AOSP, ever. That being said, I can think of four possible ways of dealing with the situation.
First, use stock ROM only. Yes, I know, that sucks. Or stock based ROM such as Fulmics, if you really think there is a difference between these two.
Second option is multirom. I was using it for last few months with LineageOS as primary and stock as secondary ROM, and everytime when I knew I would be taking some photos (when I went to concerts/holidays/celebrations/some unusual stuff), I booted to stock ROM and was good to go.
Third option is to have a TWRP backup of your current system and of stock ROM and restoring the backup of the ROM you want to use (AOSP for daily usage, stock for the days you know you'll be using your camera a lot). The previous (multirom) option is faster and easier to manage, and you can always add new ROMs and experiment as you wish. However, it requieres a custom recovery and I wasn't able to pass SafetyNet test with multirom and LineageOS with Magisk. Also, multirom makes a little bit of a mess at your /system partition. This third option (backing up/restoring system in TWRP) takes longer, the backups are large, but I'm liking that a bit more for some reason - it feels "cleaner" and more transparent to me.
The last option is to be on AOSP and use a camera app of your choice which you find has the best quality. I was experimenting with this a lot and tried dozens of camera apps (including the LG G2 camera port). Honestly, most of the photos were about the same quality. Even the G2 camera wasn't better than the rest I tested. I also compared the test pictures to stock camera (yes, I took the time to reboot to my secondary ROM for every test I was making at that time) and I was very sad that nothing was close to the stock camera quality. LG really does some magical post processing which works like a charm and looks really good. Anyways, after the tests I decided to stick with Snap Camera HDR. It has a trial and a paid version on the Play Store, in case you want to give it a shot. At good light conditions, the photos are actually comparable to stock camera. There is tons of settings to play with. It has a special "LG mode", which actually works even on AOSP ROMs and enables some LG specific features. It can also record 4K videos with stabilization. If you give it a try and really look into the settings (I recommend going also to the developer's website, where every option in the settings is described), you might end up with decent stock camera replacement. It took me about an hour to go through all the settings, but I'm fairly satisfied with the photos now. Although it has been last updated almost a year ago on the Play Store, there is a much more recent beta version here on the xda forums.
tl;dr I believe that porting stock camera app to AOSP is impossible. If you want stock camera quality, you really have to use stock ROM one way or another (either be on stock, or have a stock ROM TWRP backup and restore it whenever you want to take a good photo, or use multirom to switch your current ROM more quickly). If you want to use AOSP exclusively, I recommend Snap Camera HDR.
Click to expand...
Click to collapse
Snap Camera would look good on good light conditions but the actual problem starts with low light, Snap camera adds too much noise on photos compared to LG Camera Port, LG camera port is also great on good light conditions. Any camera app can seem close to stock on good light but real comparison should be made on low light. None of them is comparable to stock LG G3 camera of course, i think laser autofocus and object tracking don't work in any of them.
Check my comparison below(On Snap Camera, LG mode and noise reduction enabled):
https://yadi.sk/d/wEn4oOTw3JxEik
felmaster said:
Hi, I also miss the superior quality of camera from stock ROM. I was trying to follow some tutorials on porting vendor apps to AOSP (getting the camera apk file, some libraries, framework files and permission files and compiling them all together), but it never worked with the camera. Sadly, I'm pretty sure that if it was possible, somebody smarter would have already done it. With LG being jerks and not releasing the sources, we most likely won't get the stock camera on AOSP, ever. That being said, I can think of four possible ways of dealing with the situation.
Click to expand...
Click to collapse
You know how to port the Stock Music player of Fulmics 7.5 to AOSP?
I am on Resurrection Remix 7.1.2
I was looking for best camera without any problems
Finally i installed Google Camera. Works fine
Not the best quality but is ok
vampirakos said:
I am on Resurrection Remix 7.1.2
I was looking for best camera without any problems
Finally i installed Google Camera. Works fine
Not the best quality but is ok
Click to expand...
Click to collapse
Try Snap Camera, or Open Camera.
What about Snapdragon Camera? There is a versione for Nougat that we could use?
Try Footej Camera