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
hi all, i really like modding my phone and changing roms but i like the oos camera; honestly it works better (at the momment) than the third party camera apps.
that said, i'm wanting to know if there is any way to port the oos camera app for aosp or caft roms in a easy way (I'm not a developer, just an android entuciast )
Yes there is a way as a guy on the OP3/T forums ported the OOS camera too LineageOS after a lot of time and effort so it can be done, I am waiting for AOSPA to come out as they managed to use the stock camera libs (I believe) which led to pretty much the same video/picture quality.
I'm also looking for an op5 camera port for rom aosp or caf .. hopefully in the future
Hello all. just looking for some wise advice.
1: I see a lot of talk about rooting the phone. Is the just for the installation of a custom ROM, or for better functionality? I don't need cool heavy metal ROM surfaces my desktop is all black with all buttons hidden.
2: I saw no mention of bloatware, but generally speaking, how pure of an android experience is this? Can I simply uninstall whatever programs I want?
3: Any comments on the voice activation and and ease of use?
I basically need a gutsy daily driver, with good photo capabilities, (I also take photos at night as a part of my security job at a factory, and sometimes the photos for california License plates which are white reflect a lot of light and blur out on my Motorola Moto X pure), that I can give commands to while I am driving to take pictures and make calls, and check messages.
Is this the phone ror me?
Thanks!
1)Stock Rom behave as good as any custom rom. Most of the time people root their phone to have extra permission they may need to run apps that need it
2)You can remove every single piece of bloatware using ADB, no root needed
3)Works fine and is quite fast
Photos on stock rom are not Flagship level but neither crap.
For good photo capabilities I suggest you to use google camera with camera2 api enabled. The best way to achieve this is with magisk I think since with it you can hide root from various apps too while be able to enable camera2 api. But beware you should be on a firmware that a patch is available to make gcam working with it (library things.. Xiaomi changes things there a lot).
Or maybe you'd prefer a china based miui rom since the stock cam quality is better on china firmware. But for that prefer roms like xiaomi eu (because the stock china miui is in chinese and apps are default chinese apps)
Hi there,
I am sick of tired using MIUI and its childish design, so decided to upgrade to AOSP based custom ROMs for my Ginkgo. I can say that i tried almost all custom Q ROM's, but in every one of them built in camera app was taking photos all in yellow accent. It's weird but i've faced this issue for almost all Q ROM's so far. Trying GCam/trCam and plenty of other camera apps didn't help. But when i use WhatsApp's built-in camera, there is no problem. Also there is no problem with MIUI based custom ROM's like MIUI EU, MIUIMIX and MiRoom. So i'm pretty sure it's not related with the hardware, it's software based.
Weird thing is no one except me is talking about this. It's like i am the only one who is facing this bug. Any idea to fix this ****ty issue?
Sample image URL: i.hizliresim.com/yjAzDn.jpg
You’re not alone! I’ve only used ( I’m using Pixel Experience Q) and the stock cam has a warm tint, but I used a GCam with and set it to an inbuilt IMX 586 white balance preset ( Ik, the RN8 has a GM2) and it looked normal He devs should be able to fix it once Xiaomi comes out with actual android 10 miui so they can get proper android 10 blobs!
You are not alone indeed. Also, as well as fixing this, I'd like to understand how one selects between the various cameras. For example, how does one select the 48mp camera ?
(only installed rom last night, so need to play some more but very keen to find an answer to the yellow tint problem)
An update - having tried the camera again today, it is fine. I have both the built-in and open camera apps. I will do more testing tonight but this tinting thing might be a misapplication of some night-mode setting (no, I didn't have night-mode enabled when I tested the camera last night and got tinted results).
that is the issue with device tree
wait for new tree by fabian
Hello, I did some more testing last night. It seems (and I am no photographic expert) that if the camera is used in ambient light then it appears to work fine. If there is any "warm" light (such as from a light bulb) in the area it can see then it over-tones yellow. I tried it in the evening and again this morning. I guess we just need to wait for the device tree?
I did wonder if installing the MIUI camera app would work better - I haven't tried it but I guess the device tree would make this an issue at a lower level than the apps...
im curious about this yellow tint as well, a friend has an iphone 11 pro with no yellow tint in the same room as me, note 8t same problem as op's
Hello everyone, I'll be getting my Poco F3 tomorrow and I have a few questions. Most of them were asked already but they're relatively old already and I'm unsure whether it got fixed or not. Anyways, here are my questions.
1) Was the proximity sensor issue patched/fixed? Is it any better than the release? I've seen quite a few commentaries regarding it's poor quality.
If it didn't get fixed, what are some workarounds?
2) In Samsung phones (at least a few years back) your camera quality used to be ABSOLUTELY TRASH if you used an AOSP ROM. Does the same happen with this phone? If so, GCam is the only workaround?
3) Is the real world performance (gaming, scrolling, app loading times) lower in AOSP ROMs?
Please reply to this one only if you have measured the performance on both ROMs yourself instead of repeating what somebody else said (we don't know the variables they had during testing).
4) Is it possible to flash an official recovery ROM with a locked bootloader? If so, would this tool be the safest way to do?
GitHub - Szaki/XiaomiADBFastbootTools: A simple tool for managing Xiaomi devices on desktop using ADB and Fastboot
A simple tool for managing Xiaomi devices on desktop using ADB and Fastboot - GitHub - Szaki/XiaomiADBFastbootTools: A simple tool for managing Xiaomi devices on desktop using ADB and Fastboot
github.com
5) Is it possible to downgrade a update through flashing a recovery ROM? (e.g. 12.5.7 to 12.5.6).
6) Is the screen dimming when gaming still an issue? If not, are there any workarounds?
7) Are there any other issues that I didn't mention or things you'd like to say?
Notes:
- When I say "AOSP ROMs" I'm mainly thinking about Lineage and MicroG for Lineage.
- Feel free to only reply to one or two of them, I'll be happy as long as the information is legitimate.
1. ROMs based on the ROM that was banned from here due to its name trees generally don't have much issue with it, as long as the hardware goes - it is as inaccurate on MIUI. With some lower quality ROMs it may be better or worse, as with anything else
There was one workaround with disabling the proximity sensor and turning off the screen when in-call, but that's rather a half measure.
2. There is MIUI camera port for Alioth somewhere, but as now most ROMs are based on A12 the compatibility may vary.
Gcam by BSG works well even with default settings and it supports all the hardware, so there's that. Needless to say, it doesn't support upscaling present in MIUI cam (so the front camera will take ~5 Mpix photos, compared to the fake 20 Mpix in MIUI).
3. I've used MIUI and some AOSP/Pixel ROM for some time and although benchmarking apps indeed show a little lower scores on AOSP (at least the few I've tried), AOSP ROMs generally feel more snappy - the difference may stem from the UX itself tho (i.e. janky MIUI gestures vs AOSP gestures).
4. I'd say it's always safer to go with official fasboot ROMs. Alioth is a bit messy when it comes to recovery in general; some ROMs work only with their own recovery images, some are recommended to use with the AOSP recovery, and both official and unofficial TWRPs aren't stable enough (or really worth it, IMO).
5. No idea; I believe Alioth has ARP, so you may need a workaround for it.
6. Never happened to me (MIUI or AOSP), it may be either vendor or screen panel specific.
7. Some people report slow charging speeds, which (as long it doesn't take over two hours) may be considered a feature as constant charging with full power is known to exhaust PMIC chips leading to hardware failures in the long run.
Apart from that, there is the green tint, which may happen in 120 Hz mode on some panels, but it is calibrated in some ROMs. It does occur on MIUI too.
EDIT: Also idle drain, but that's again ROM specific. Iirc LineageOS is generally stable when it comes to that.
Thank you very much for your reply, I have the device for a day and I have no issues with it.
My only qualm is the display panel on low brightness which looks rather bad (colors seem to shift only on certain areas, probably because it's not dimming it evenly) but that's fair considering the price point of the phone.
Also, the camera isn't even as bad as I thought, a happy surprise.