Related
Greeings, I wish to buy XZ Premium and the model will be g8142 in my country. Before buying I would like to ask some questions.
1. I need to root my device, and it seems that the rooting method only support Android 8.0. So sould I flash stock 8.0 ROM before rooting?
2. I heard that rooting will damage the camera function and make it green screen or something. Camera is a very important part to me and I wish to retain the original quality as the unroot stock ROM. Is there any way to fix it?
3. LG's app will crash if I change the resolution in terminal. Will Sony's apps crash or cannot be used if I change the resolution to 1080p and also lower the DPI?
4. Anything else that need to be noticed after rooting and need to be fixed?
Thanks a lot in advance.
Vulturon said:
Greeings, I wish to buy XZ Premium and the model will be g8142 in my country. Before buying I would like to ask some questions.
1. I need to root my device, and it seems that the rooting method only support Android 8.0. So sould I flash stock 8.0 ROM before rooting?
2. I heard that rooting will damage the camera function and make it green screen or something. Camera is a very important part to me and I wish to retain the original quality as the unroot stock ROM. Is there any way to fix it?
3. LG's app will crash if I change the resolution in terminal. Will Sony's apps crash or cannot be used if I change the resolution to 1080p and also lower the DPI?
4. Anything else that need to be noticed after rooting and need to be fixed?
Thanks a lot in advance.
Click to expand...
Click to collapse
Hello to can root your device and if you unlock the bootloader some fonctions will stop working but we have a fix for that and for the resolution it's normal they are many app who doesn't even support 1440p
1. You can root any ROM, just flash magisk in twrp.
2. There are drm fixes available, e.g. Janjan's kernel, xperifix.
3. You can change the screen resolution to 4k in adb but not every app is working. No need to change, default 1080p is all right.
4. Every time you have to update the software manually and apply drm fix if you unlock the bootloader. Android Pie is probably going to be the last major update for the phone. There are not many custom roms out there.
You are welcome.
xueyaotianxia said:
1. You can root any ROM, just flash magisk in twrp.
2. There are drm fixes available, e.g. Janjan's kernel, xperifix.
3. You can change the screen resolution to 4k in adb but not every app is working. No need to change, default 1080p is all right.
4. Every time you have to update the software manually and apply drm fix if you unlock the bootloader. Android Pie is probably going to be the last major update for the phone. There are not many custom roms out there.
You are welcome.
Click to expand...
Click to collapse
Thanks a lot for the reply! Helps a kot, please allow me to ask a little more
1. https://forum.xda-developers.com/xz-premium/development/kernel-sony-xz-premium-5-2018-t3784669
Does that mean most of you guys are following this guide to root and no issues occur in rooting g8142?
2. Drm fix really can solve the issue of camera of rooting? e.g. green photos or easily overheat, because I am buying this phone for the camera quality, if this is uncertain then I will consider another phone.
3. About resolution, from what I saw in the demo phone in my local store, the screenshot of XZ Premium is 2160 x 3840, doesn't that mean it is always on 2160x3840? I don't want such high res and I like to make it always 1080x1920.
Hope it wont make Sony stock app crashes... Will it?
Thanks in advance again!
Vulturon said:
Thanks a lot for the reply! Helps a kot, please allow me to ask a little more
1. https://forum.xda-developers.com/xz-premium/development/kernel-sony-xz-premium-5-2018-t3784669
Does that mean most of you guys are following this guide to root and no issues occur in rooting g8142?
2. Drm fix really can solve the issue of camera of rooting? e.g. green photos or easily overheat, because I am buying this phone for the camera quality, if this is uncertain then I will consider another phone.
3. About resolution, from what I saw in the demo phone in my local store, the screenshot of XZ Premium is 2160 x 3840, doesn't that mean it is always on 2160x3840? I don't want such high res and I like to make it always 1080x1920.
Hope it wont make Sony stock app crashes... Will it?
Thanks in advance again!
Click to expand...
Click to collapse
1. Yes that's the drm fix. After you've flashed the official firmware and then apply drm fix.
2. What drm fix does is that it tricks the phone to think that the bootloader is not unlocked. You can check *#*#7378423#*#* and then service info, configuration, it will say bootloader unlocked allowed: no. But you are still running the phone with an unlocked bootloader.
3. The phone will stay at 1080p unless there is 4k content, or 1440p content...if you change it in adb, when you press the app switcher button, it will show every app as black colour, no content. I have manually changed it to 1440p before no app crashes, 4k is not good because there might be some issues. So I switched back to default which is 1080p.
To be honest even it is on 1080p the screen looks fantastic. I bought it only because of the screen. Proudly G8142 owner here...
xueyaotianxia said:
1. Yes that's the drm fix. After you've flashed the official firmware and then apply drm fix.
2. What drm fix does is that it tricks the phone to think that the bootloader is not unlocked. You can check *#*#7378423#*#* and then service info, configuration, it will say bootloader unlocked allowed: no. But you are still running the phone with an unlocked bootloader.
3. The phone will stay at 1080p unless there is 4k content, or 1440p content...if you change it in adb, when you press the app switcher button, it will show every app as black colour, no content. I have manually changed it to 1440p before no app crashes, 4k is not good because there might be some issues. So I switched back to default which is 1080p.
To be honest even it is on 1080p the screen looks fantastic. I bought it only because of the screen. Proudly G8142 owner here...
Click to expand...
Click to collapse
Thanks a ton. Can you show me which one is the app switcher icon you mentioned? Is that mean the app drawer icon? That turn to black? Thanks
Vulturon said:
Thanks a ton. Can you show me which one is the app switcher icon you mentioned? Is that mean the app drawer icon? That turn to black? Thanks
Click to expand...
Click to collapse
It is the square button on the right hand side of your home button(app switcher). When you press this, all apps become black, you won't see the preview.
Vulturon said:
Thanks a ton. Can you show me which one is the app switcher icon you mentioned? Is that mean the app drawer icon? That turn to black? Thanks
Click to expand...
Click to collapse
This.
xueyaotianxia said:
It is the square button on the right hand side of your home button(app switcher). When you press this, all apps become black, you won't see the preview.
Click to expand...
Click to collapse
Alright. In adb, Is it possible to transfer a .ogg file into system/media/ui without rooting the device and replace the orogonal one? I want to replace a ui sound file with a .ogg file. Thanks a lot
Some of you may not notice, but I'm sure there are a few that do. Touch screen responsiveness on custom ROMs or GSI's for Mata is working, but is definitely not as fluid as stock.
Easiest way to tell is just typing on the keyboard and taking note of the shot delay in between touches. For me, I type fast, and this causes spelling mistakes often, because the touch screen (on a ROM or GSI.) doesn't register as it does on stock.
Next is mobile gaming. Touch seems to be a total hit and miss here, and sometimes won't work at all unless one finger is already on the screen. That's not a big deal, because a simple reboot fixes this temporarily. This was fixed a while ago here, if I recall correctly:
https://review.lineageos.org/c/LineageOS/android_frameworks_native/+/198809
Overall I am hoping to find a fix for this touch responsiveness issue. It effects a ton of aspects of this phone and prevents me from staying on ROMs, and resorting to restoring backups to use my phone properly again.
I've tried messing with the build.prop, switching kernels, checked out various forums and attempted things I probably shouldn't have tweaked with, but still have had no luck figuring this out on ROMs or GSI's. Yet on Stock everything functions properly, and touch is no issue.
Can anyone shed any light on this at all? (To clarify there are 2 issues here: general delay in touch, and touch screen not working after a while on games.)
Hi, I just flashed gsi rom yesterday and also found it more laggy than stock. I tried to search for a way to improve it but failed. Please let me know if you find a way to solve this problem.
Actually I flashed it just to make the stasus bar shorter and make it possible to disable navigation bar. I may change back to stock if I find any method to do so on it.
lovelock8353 said:
Hi, I just flashed gsi rom yesterday and also found it more laggy than stock. I tried to search for a way to improve it but failed. Please let me know if you find a way to solve this problem.
Actually I flashed it just to make the stasus bar shorter and make it possible to disable navigation bar. I may change back to stock if I find any method to do so on it.
Click to expand...
Click to collapse
Still trying different things, but so far no luck, touch remains a bit laggy. Gonna try something later though, are you currently on a GSI with Root?
In: system / usr / idc there should be some .idc files, I wonder if there are some entries on stock that aren't in GSI's or ROMs?
I dunno, just shooting in the dark here.
MoistPicklez said:
Still trying different things, but so far no luck, touch remains a bit laggy. Gonna try something later though, are you currently on a GSI with Root?
In: system / usr / idc there should be some .idc files, I wonder if there are some entries on stock that aren't in GSI's or ROMs?
I dunno, just shooting in the dark here.
Click to expand...
Click to collapse
Yes,I rooted it. I just checked idc folder of my stock room restore, there are no more but 1 less idc file in the stock rom. I copied the entire idc folder to main storage, restored the gsi room and replaced it. I don't think it makes obvious change,at least did not make the touch screen as good as the stock.
But I did flash elemental-x kernel after flashing gsi. It might have make it better? Maybe I just got used to the sensitivity of gsi but you may try to flash the kernel and replace the folder, see if any changes are noticed.
I'm running the latest HavocOS GSI build with the neutrino gemini kernel. Also using Ex Kernel Manger so the settings will stick or can be changed. No touch lag or the like on my end. Very smooth.
hx3 said:
I'm running the latest HavocOS GSI build with the neutrino gemini kernel. Also using Ex Kernel Manger so the settings will stick or can be changed. No touch lag or the like on my end. Very smooth.
Click to expand...
Click to collapse
Is the status of Havoc OS as high and wide as the stock room? Or is it just normal size as on other Android devices? Considering transfer to it.
lovelock8353 said:
Is the status of Havoc OS as high and wide as the stock room? Or is it just normal size as on other Android devices? Considering transfer to it.
Click to expand...
Click to collapse
Unfortunately, the latest build of HavocOS is from October 27th. However, you can still use the latest December firmware/security update from Essential.
There is one bug with it, at least for me and others, and it's the fingerprint sensor doesn't work for us. It doesn't show up in Settings either. It worked on previous builds, though. Not to knock the developer at all, as I appreciate the work that has been put in.
As far as the "normal size" you brought up... Are you referring to file size? If so, it's in the same ballpark as any other stock/stock-ish ROM that doesn't include gapps. I used Pico gapps, as I don't use many Google apps. Hopefully that answered your questions.
hx3 said:
Unfortunately, the latest build of HavocOS is from October 27th. However, you can still use the latest December firmware/security update from Essential.
There is one bug with it, at least for me and others, and it's the fingerprint sensor doesn't work for us. It doesn't show up in Settings either. It worked on previous builds, though. Not to knock the developer at all, as I appreciate the work that has been put in.
As far as the "normal size" you brought up... Are you referring to file size? If so, it's in the same ballpark as any other stock/stock-ish ROM that doesn't include gapps. I used Pico gapps, as I don't use many Google apps. Hopefully that answered your questions.
Click to expand...
Click to collapse
Thank you for your information!
I'm sorry I mistyped the question. Actually what I wanted to ask was the status bar, which bothered me a lot on the stock rom. I flashed to pixelexperience specially for changing the status bar height to normal (and being able to disable navigation bar completely). I don't know why it was so hard that I didn't find any way to do so on stock rom.
lovelock8353 said:
Thank you for your information!
I'm sorry I mistyped the question. Actually what I wanted to ask was the status bar, which bothered me a lot on the stock rom. I flashed to pixelexperience specially for changing the status bar height to normal (and being able to disable navigation bar completely). I don't know why it was so hard that I didn't find any way to do so on stock rom.
Click to expand...
Click to collapse
Oh, yeah, that's the other "issue" people have had with HavocOS on the PH-1. The status bar is very thin...About 50% too thin, and I don't know of any way to change it. It doesn't really bother me after getting used to it. I'll have to try out Pixel Experience, though. I do miss the fingerprint sensor working properly.
hx3 said:
I'm running the latest HavocOS GSI build with the neutrino gemini kernel. Also using Ex Kernel Manger so the settings will stick or can be changed. No touch lag or the like on my end. Very smooth.
Click to expand...
Click to collapse
Thanks for the input, pretty sure I have already tried the Oct 27th Havoc OS with Neutrino and still had those touch issues with games, but I will give it another shot in case, did you by chance modify a few things with EX Kernel Manager?
hx3 said:
Oh, yeah, that's the other "issue" people have had with HavocOS on the PH-1. The status bar is very thin...About 50% too thin, and I don't know of any way to change it. It doesn't really bother me after getting used to it. I'll have to try out Pixel Experience, though. I do miss the fingerprint sensor working properly.
Click to expand...
Click to collapse
The status bar is also thin pixelexperience if you care. Aside from the touch screen latency, I haven't noticed any other issue on this rom, so I recommend you give it a try.
Tried Havoc OS paired with Neutrino, and tweaked around with EX Kernel Manager last night for a while, but still had issues with touch on games and keyboard. Literally everything I have tried on custom installations has not helped improve touch responsiveness.
Come on, surely some random dev still lurks these forums who also notices these delays in touch. Would love to help solve this if I knew exactly where to start, and am willing to test or tweak to get this resolved.
No idea if this will help, but it's easy to try. In developer settings, find grip rejection and try toggling it on. Else, in the same place, try adjusting touch sensitivity.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
ktmom said:
No idea if this will help, but it's easy to try. In developer settings, find grip rejection and try toggling it on. Else, in the same place, try adjusting touch sensitivity.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
Grip rejection and touch sensitivity aren't available in GSI's unfortunately, but even some ROMs that do include those settings still have delayed touches, and games eventually lose touch until you reboot on occasion.
Compared to stock, the only ROM that had touch working perfectly (like stock) was Kuran's AICP O. I suspect this has something to do with his kernel, but I am just speculating, I can't be sure on that one.
Then even on a GSI with a stock kernel I still get touch issues, so I have a feeling it has something to do either something in /system but then again, I'm still guessing.
But I appreciate the reply thank you for chiming in on this. ?
The only reason I suggested that "fix" was when I was running AOSiP Pie, that was the only way to get rid of the lag. Simply toggling the grip rejection solved the problem immediately.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
ktmom said:
The only reason I suggested that "fix" was when I was running AOSiP Pie, that was the only way to get rid of the lag. Simply toggling the grip rejection solved the problem immediately.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
Huh, last time I was on AOSiP Pie (maybe a week ago) I still had touch issues, but hell, for some awesome customization, maybe it's time for another try on that. Thank you, by the way, I really dig that signature of yours.
MoistPicklez said:
Huh, last time I was on AOSiP Pie (maybe a week ago) I still had touch issues, but hell, for some awesome customization, maybe it's time for another try on that. Thank you, by the way, I really dig that signature of yours.
Click to expand...
Click to collapse
Throw a setprop in front of these... And reboom... See if it helps
persist.vendor.qti.inputopts.enable=true
persist.vendor.qti.inputopts.movetouchslop=0.5
rignfool said:
Throw a setprop in front of these... And reboom... See if it helps
persist.vendor.qti.inputopts.enable=true
persist.vendor.qti.inputopts.movetouchslop=0.5
Click to expand...
Click to collapse
Thanks will try this tonight.
So I'd just use:
adb shell
Then
setprop (entry here)
?
MoistPicklez said:
Thanks will try this tonight.
So I'd just use:
adb shell
Then
setprop (entry here)
?
Click to expand...
Click to collapse
Sure...
But why for you no have magisk?
rignfool said:
Sure...
But why for you no have magisk?
Click to expand...
Click to collapse
Edit: I think I may have gotten it figured, and at least narrowed down the issue. I Installed Havoc OS 10-27 again with Dec-patched-boot.img, then Neutrino Hercules over that, on both slots, changed CPU to performance and enabled touchboost, then added these lines to my build.prop and rebooted:
persist.vendor.qti.inputopts.enable=true
persist.vendor.qti.inputopts.movetouchslop=0.6
So far so good, touchscreen jank is gone, scrolling isn't bad at all, and best of all games seem way more fluid. Will continue to test it out.
Edit 2: So far so good games haven't lost touch, not even once, games are still fluid and there are literally no touch delays when gaming or typing. So either the kernel (with performance mode and touch boost on) or the entries I added to the build.prop have fixed this finally. Or both. So freakin' happy.
WARNING: I'VE TESTED THIS GUIDE ON STOCK FIRMWARE (OREO AND PIE) ONLY
Hey, just a moment before reading: did I help you? Then consider paying me a coffee or anything for my effort of course this isn't mandatory!
UPDATE: the reddit thread is dead! It will now only link to this guide since updating the same guide two times is pretty useless!
This is an expanded guide for all those people which want to reach the maximum camera quality on their X4.
Please note that this post is not intended to give advices on how to get the best shots on GCAM (but you can do it in comment or ask me, no prob!), but on how to get the best working GCAM possible setup! In other words I won't suggest parameters for HDR+ or Saturation, or custom libs etc...
FOA why you should choose Google Camera instead of the Motorola one? Well I think the following shots speak for themselves:
Cropped detail of an HDR shot:
Moto Camera HDR (taken with wide lens)
Google Camera HDR+ (taken with wide lens)
If you'd like to see more examples just look at this HQ album, you'll be amazed by the details.
Another field in which you can really apprecciate the potential of this camera is the selfie and portrait one. I will spare you from looking at my selfies (you can find one in the previous gallery), so just trust me, or do some googling!
What you need to do in order to use the GCAM on your X4 really depends on what you want to achieve:
1) GCAM 6.2.0.30 for normal lens
- Root needed: NO
- Unlocked Bootloader needed: NO
GCAM 6.2.0.30 adds Time-Lapse feature, and you can simply install it and it will run. There's a lot of ports avaiable, my suggestion goes to this one. Please remember that all the rights belong to Arnova, the original developer.
A couple of things must be tuned in order to get the best experience, so head up to the app settings and:
- on "About" check "advanced options"
- on HDR+ Options:
1) Disabled AWBGains Mod -> ON
2) RAW Format -> RAW10
3) Image Format -> YUV_420_888
4) GCAM wb Mode -> ON
Also, I suggest you to check the "Saturation adjustements" section, because this version really oversaturates photos. Try what levels are the best for you, in my case they were 1.0 - 1.0 for back camera and 1.1 - 1.3 for front camera.
2) GCAM 6.2.0.30 for wide lens
- Root needed: NOT NECESSARILY
- Unlocked Bootloader needed: YES
This is the 6.2.0.30 GCamera with Wide Lens support.
The apk is the same one
After the installation you must enter the package name (org.codeaurora.snapcam)inside the followind /system/build.prop lines:
1) vendor.camera.aux.packagelist
2) vendor.camera.aux.packagelist2
3) ro.camera.cfa.packagelist
You can do this either with a privileged file manager (i.e.: Solid) or with adb pull.
Then activate "Enable aux button" in Settings, and a little tree icon will pop up, allowing you to switch lens.
----------------------
FAQ:
Q: What works in these ports?
A: The following features are fully working:
- HDR +
- Portrait
- PhotoSphere
- Night Sight- Panoramic
- Video
- Slow Motion
- Pixel 2/3 AWB
- TimeLapse
- Motion
Q: What about AR?
A: I'm not interested in it and haven't checked, so I can't assure you that it will work
Q: 60fps videos aren't in 60fps?
A: You can shoot in 60fps by disabling video stabilization in Settings, otherwise 60fps videos will drops to nearly 28-30fps.
Q: Why does my selfie looks purple/green/any other ****ty color?
A: In that case just head over Input model in your port settings and change the front camera model (in my case to Nexus 6P with 6.1 and Pixel 3 for 6.2, but just try). This port also have specific fixes for certain titn problems
Q: I can't even start the camera!
A: this can happen on some devices. To fix try the following: long press on the app icon and use the "take a selfie" shortcut. Wait a moment and the camera should work, allowing you to use it in future just by opening it normally. If it is black even via the selfie shortcut long press the switch camera button, it should work. This procedure must he done only one time!
Q: The 6.2 ports gives me some weird greenish/yellowish balance in photos.
A: This is a problem with Pixel AWB. It reduces chromatic shifts to give you more natural photos, but it can ruin other ones. It usually happens when you are pointing an object which has an intense illumination behind it. If your port allows it just disable it, otherwise select from the viewfinder another White Balancement mode (Cloudy works best for my tastes). Pixel 2 AWB should be the best anyway, and I almost never encounter problems.
Q: Can't install the apk
A: Delete the old version before re-installing.
Best night site for me has been
https://www.celsoazevedo.com/files/a...09_MI8_V1a.apk
Thanks for posting this. As soon as I get Pie, I will be implementing option 3.
flipguyfromthepi said:
Best night site for me has been
https://www.celsoazevedo.com/files/a...09_MI8_V1a.apk
Click to expand...
Click to collapse
Could you fix the link? It seems to be broke. TIA
is it possible to port a gcam pointing wide lens to the secondary camera of the Moto X4?
CypherPotato said:
is it possible to port a gcam pointing wide lens to the secondary camera of the Moto X4?
Click to expand...
Click to collapse
Need root for it, just download any version compatible with wide lens and put the package name on this line inside build.prop:
vendor.camera.aux.packagelist2
Hi there!
Anybody has any idea why gcam (MGC_6.1.021_MI8_V1a_xcam_0.apk) does not want to take any shots without HDR?? I remember gcam 5.1 working fine without HDR and the shutter speed was obvs way faster. So sometimes I want to take a fast shot and gcam 6.1 won't let me. I already tried changing the input model.
Thanks!
UPDATE: for those who want GCAM 6.1 with Night Sight I updated the suggested apk, with one that looks more stable (the old one used to crash rarely on my phone).
uccollab said:
UPDATE: for those who want GCAM 6.1 with Night Sight I updated the suggested apk, with one that looks more stable (the old one used to crash rarely on my phone).
Click to expand...
Click to collapse
In case anyone had any trouble editing the build.prop remove the following space:
vendor.camera.aux.packagelist2=com.motorola.ccc,co(THIS SPACE)m.dual.GCam,com.motorola.camera2
I realized it while typing, but if you only copy and paste you might not.
With all these camera mods, is there anyway to verify the security of them? I don't think I have ever had problems with an XDA app but these are all hosted offsite.
sleze said:
With all these camera mods, is there anyway to verify the security of them? I don't think I have ever had problems with an XDA app but these are all hosted offsite.
Click to expand...
Click to collapse
I don't really check it, cause that's the official repo for the gcam ports, and all the developers (like Arnova etc..) are well known here.
uccollab said:
I don't really check it, cause that's the official repo for the gcam ports, and all the developers (like Arnova etc..) are well known here.
Click to expand...
Click to collapse
I am on Moto Pie and using the gcam port from 2nd option. once I take a picture in night sight, I cannot take another picture till I force close the camera. Do you have the same issue as well?
munchy_cool said:
I am on Moto Pie and using the gcam port from 2nd option. once I take a picture in night sight, I cannot take another picture till I force close the camera. Do you have the same issue as well?
Click to expand...
Click to collapse
Hi, I'm on stock Pie and not getting this issue, do you have other ports installed?
uccollab said:
Hi, I'm on stock Pie and not getting this issue, do you have other ports installed?
Click to expand...
Click to collapse
nopes ..
i tried bsg's port and that works fine
Can anyone post a video of this? Trying to have my friend install this and it would help him to have a visual.
uccollab said:
2) Open up the buid.prop file (located in /system/system/). You can either do this by an adb pull command (after booting a custom recovery like TWRP) or with a privileged file manager if you're rooted. In the build.prop you must add the following line (or edit it, if already present): vendor.camera.aux.packagelist2=com.motorola.ccc,com.dual.GCam,com.motorola.camera2
Click to expand...
Click to collapse
johnjingle said:
In case anyone had any trouble editing the build.prop remove the following space:
vendor.camera.aux.packagelist2=com.motorola.ccc,co(THIS SPACE)m.dual.GCam,com.motorola.camera2
I realized it while typing, but if you only copy and paste you might not.
Click to expand...
Click to collapse
Had to remove the space as well, Night Sight works wonders!
I installed option 2 and the rear cam has a yellowish tint. Is there a fix?
Hi, just tried this out on my new moto x4 (The second one with night sight) and it works pretty smoothly. I was just wondering if there was a way to enable the actual front facing flash for selfies and not just brighten the screen up like it does on default (in the recommended app at least)
ALL i want to do is have the stock camera default to manual mode... Or at least REMAIN in manual mode after I set it to that so I don't have to switch to manual every single time I start the camera app. The Auto settings on the stock camera are GARBAGE compared to my Moto X2 (2nd Gen).
Thanks a ton
Has anyone tried google camera on moto one vision?
m2l4489 said:
Has anyone tried google camera on moto one vision?
Click to expand...
Click to collapse
Do you have Motorola one vision phone?
Bump. ?Im also curious about Gcam on M.O.V, anybody tried already?
The Play store says it's not compatible.
Maybe there's a way around that.
Not sure what it would add compared to the Motorola one or OpenCamera to be honest (I used it on my Nexus 5 until last week).
I've tried a few modded ones but none of them worked fine so far.
Yeah, i'v tried 3-4 versions for exynos, and no luck. App's starts properly, I see the user interface, but no view from camera, just black screen. May it need some app settings changes?
NiceMrMustard said:
The Play store says it's not compatible.
Maybe there's a way around that.
Not sure what it would add compared to the Motorola one or OpenCamera to be honest (I used it on my Nexus 5 until last week).
Click to expand...
Click to collapse
You don't go to Play Store if you want Gcam on your non-Pixel device.
You use apk files to install them
ozzmozz said:
Yeah, i'v tried 3-4 versions for exynos, and no luck. App's starts properly, I see the user interface, but no view from camera, just black screen. May it need some app settings changes?
Click to expand...
Click to collapse
Have you tried the gcam for snapdragon? As incredible as it seems it takes some functions, nothing else in night mode or portrait mode, which I tested was one normal if I'm not mistaken
The latest beta version by @Arnova8G2, at the following link, has many features working on Motorola One Vision (not all, though: Night Vision and a few others are not working and device is seen as 12Mpx instead of 48Mpx): https://www.celsoazevedo.com/files/android/google-camera/dev-arnova8G2-beta/
marco.ciccaglia said:
The latest beta version by @Arnova8G2, at the following link, has many features working on Motorola One Vision (not all, though: Night Vision and a few others are not working and device is seen as 12Mpx instead of 48Mpx): https://www.celsoazevedo.com/files/android/google-camera/dev-arnova8G2-beta/
Click to expand...
Click to collapse
Did you compare this mod whit stock camera app, is quality better than motocam?
I don't think the two can be compared at this stage. The porting shoots at only 12Mpx and not at full 48Mpx as the stock camera.
Maybe in future releases...
marco.ciccaglia said:
I don't think the two can be compared at this stage. The porting shoots at only 12Mpx and not at full 48Mpx as the stock camera.
Maybe in future releases...
Click to expand...
Click to collapse
It may be that the gcam doesn't take use of the quad pixel technology like stock cam do, and therefore won't see it as 48mp.
Stock can doesn't actually save the pictures in 48mp but at 12mp (12x4=48) when it's sampled down, but ofc with better details and light.
Sent from my motorola one vision
Tried many mods, none of them worked well, in arnova's I get black pictures, other ones get super overexposed pics
Does the Moto One Vision has camera2api enabled or do we have to manually enable?
magnaroader said:
Does the Moto One Vision has camera2api enabled or do we have to manually enable?
Click to expand...
Click to collapse
It has full camera2 API support by default.
Sent from my motorola one vision
I had this one out around 15 days back - https://f.celsoazevedo.com/file/cfiles/gcm1/Gcam_6.2.030_Advanced_V2.1.190614.0200.apk
Couldn't take a portrait. Couldn't capture 1/8 slow motion vids. Couldn't attempt night sight and photobooth (whatever that is).
But serious question - Do we really need Google camera? By 'we', I mean casual users. Not hardcore shutterbugs.
PS - I didn't try changing settings.
baunthiyal said:
I had this one out around 15 days back - https://f.celsoazevedo.com/file/cfiles/gcm1/Gcam_6.2.030_Advanced_V2.1.190614.0200.apk
Couldn't take a portrait. Couldn't capture 1/8 slow motion vids. Couldn't attempt night sight and photobooth (whatever that is).
But serious question - Do we really need Google camera? By 'we', I mean casual users. Not hardcore shutterbugs.
PS - I didn't try changing settings.
Click to expand...
Click to collapse
YES we really do need GCam. Try using any other Portrait mode shots with any other camera (flagship or not) and tell me if the processing comes anywhere near as good.
I've tried Gcam on many phones and the quality is consistent enough to justify the need on this device.
Hopefully someone can find a working gcam, or ask the appropriate modders if they can port one for us.
try this : MGC_6.1.021_BSG_Arnova-TlnNeun_Urnyx05-v4.3.apk
and use this configs : mackytravel-nightsight.xml
(search from google)
and you can try and find the best correct setting (Exposure compensation,Libs,Adjust saturation,.............)for good quality picture by yourself
(How to use config : Create a folder name Gcam inside that folder create a new folder name Configs and download below’s config and paste it, then open gcam and tap the black area in viewfinder and select this config then restore.)
I had just installed @Arnova8G2 's Gcam_6.2.030_Advanced_V2.1.190614.0200.apk earlier today.
As of this post, it is the most up to date of Arnova8G2's Google Camera apks. The detail looks amazing as expected of the Google Camera, but when I check the pictures, they have a noticeable grey filter effect going on. A second issue I ran into is when I switch to Portrait mode, the mode freezes. The final issue I've found so far is the app also sometimes freezes when switching to selfie mode.
I'm wondering if anyone's also run into some of these issues and if I should use an earlier build instead?
NOTE: This is my first time using a third party apk, so I apologize if I sound ignorant. Do apps like these automatically update or do I need to install a newer apk manually for each iteration?
Apologies
I apologize, I'm new to this forum so I'm not sure how to delete this post. I realized that I forgot to install a config file, and once I did it fixed my issues.
tdnguyen0 said:
I apologize, I'm new to this forum so I'm not sure how to delete this post. I realized that I forgot to install a config file, and once I did it fixed my issues.
Click to expand...
Click to collapse
Which config
Primal instinct said:
Which config
Click to expand...
Click to collapse
I reverted to the stable Arnova's Advanced 1.6 apk along with the OP7_Arnova_Beta_Fizwiz_2.0.xml config file and it works (minus some of the more advanced functionality in the settings).
@tdnguyen0 , https://www.celsoazevedo.com/files/android/google-camera/f/changelog566/
Ok so for front cam freezing in portrait change to nexus 6p in "advanced" then " base" and after that go to "fixs" and go to viewfinder change to YUV_420_888
For color none of the auto exposure fixes worked or white balance... The only thing that seemed to work okay for me was going to "libs" and changing to "Eszdman" its sets color gamut
Hello , i am using the application for oneplus 7 pro but i have a very big problem that i can't solve , when i take any picture with HDR+ it replays me always (processing HDR+) and still very much time to process and maybe not ! ? I don't know what i can do ??
Please replay me as soon as possible .