[Moto Z ROMs, Kernels, Recoveries, & Other Developm] Conkerts:
Hi everyone.

So I did a "short" photo test. Video test comes later. This post is prone to changes, because I'll probably extend it. If it becomes too much, I'll move it somewhere else.

Because this post grows, I'll put the conclusion at the front. This is also for the TL;DR people ;)

* Current conclusion (14.08.17):

- Atm, I prefer moto cam for photos and open camera if (4K) video is needed.

- Modded Google cam is also worth a try and has good quality.

- I will iterate more on my testing methodology (better & objective image quality criteria, maximum resosultion, outside motives, macro, HDR modes, panorama, video).

**************************************************

* 1. Evening scene in room with (enough) halogen light (11.08.17):

- These scenes are usually the worst case scenario for smartphone cams.

- I had to use 1080p (2MP) everywhere, because of camera fv-5 lite constraints

**************************************************

*************************

** stock cam (org.cyanogenmod.snap)

- has no RAW export, not that many settings, but clean UI

- the only app which used in auto settings flash in this scene, so white balance is different

- focus is sometimes slow or photos are not sharp

- sharpness: not that good, considering it used flash

- quality: is ok, relative low image noise

- personally I dont like the app

-> will test the modded Google cam instead

*************************

** camera fv-5

- lite version, so only 1080p (2MP) capture is allowed

- paid version has RAW export & lots of settings, good and clean UI

- nice intro tutorial

- no video recording included, separate app cinema fv-5 needed

- sharpness: ok

- quality: seemed to use some sort of sharpener, slightly too much for my taste & lowest image noise in the test

- personal opinion:

will maybe test it more in depth, but wont buy atm

*************************

** moto cam (with internal cam)

- has no RAW export, not that many settings but clean UI

- really fast focus

- crash on video recording

- sharpness: ok

- quality: some image noise, but overall ok and I liked it the most (maybe it cheated a bit, because resolution was higher)

- personal opinion:

best quality so far, will use it atm for taking photos, my sister prefers the photo as well ;)

*************************

** open camera

- open source

- has RAW export & lots of settings,

- UI is ok (some settings are a bit hidden), nice descriptions

- did cause a crash (while switching modes), but can't reproduce it again ...

- a bit on the slow side with the focus, but makes sure the photos are sharp

- has working 4K 60 fps video recording

- Warning: in DRO mode (called "dynamic range optimisation", sort of 1 pic HDR) it has a weird contrast and extreme sharpener, looks ugly (and image noise gets amplified, would not recommend it)

- in STD mode contrast & quality similar to fv-5, so it's ok

- personal opinion:

I would prefer this one, because it's open source & has RAW export,

but (!) in the current state, I *advise* to test the image quality for yourself, before using it in "production mode".

Will test it more in depth ...

**************************************************

2. Outdoor test (14.08.17)

- this time with full 13MP resolution

**************************************************

****************************

** stock cam (org.cyanogenmod.snap)

- the picture is in general a bit too bright, and contrast is quite bad, so details are lost

- I still dont like the app, and I don't see a reason to use it

-> will test the modded Google cam instead

****************************

** camera fv-5

- difficult to compare due to lite version with only fhd

- the picture is again a bit too bright, and contrast is quite bad, so details are lost

****************************

** moto cam (with internal cam)

- contrast ok most of the time, more saturated colors

- in general: can't complain and would prefer this app

****************************

** open camera

- contrast a bit stronger than in moto cam

- colors a bit less saturated

- be careful with HDR modes, they produce strange results

**************************************************

3. Video test (14.08.17)

**************************************************

*************************

** stock cam (org.cyanogenmod.snap)

- the picture is slightly too bright, otherwise ok

- image stabilisation not that good, open cam is better

*************************

** camera fv-5 (-> cinema fv-5)

- only 720p resolution due to lite version

- quality, colors & contrast seem ok for this resolution

- Atm, I don't see a reason to buy this app

*************************

** moto cam (with internal cam)

- test not possible (due to crash)

*************************

** open camera

- even 4K 60fps video possible

- image stabilisation is mostly ok / seems to work better than in stock cam

- quality, colors & contrast are ok

- Atm, I would recommend using this one, as long as moto cam won't work

--------------------------------------- other stuff ---------------------------------------

While changing some modes on open cam, I got a "serious camera error" as well. So, next time I started a cam app, device rebooted. That's the part where "short" test wasn't that short anymore.

Also I had again lots of these extremely annoying boot freezes/loops afterwards.

It appears either as a freeze of the boot animation,

OR

after a while (1-2 min), the phone vibrates slightly every 7 seconds & the boot animation just loops and nothing happens,

This happens *always after* I enter the decryption pattern.

And again, I'm not able to get any logs, ARRGH.

It didn't even help to wipe system completely and flash it again.

Seems to be something wrong with the data partition. (Repairing doesn't help, only complete backup restore of data helps).

Anyway, that's currently the worst bug, imho -.-

-------

Ok, update:

Under TWRP -> Advanced I found a copy log option, and if I check "include kernel log",

it'll write a dmesg backup on sdcard (which is probably the last kmsg).

And there I found loooooots of filesystem errors (besides some segfault ...), like

5>[ 16.328418,3] F2FS-fs (dm-0): recover_inode: ino = ff8f, name = system@framework@boot.art
<5>[ 16.328967,3] F2FS-fs (dm-0): recover_dentry: ino = ff8f, name = system@framework@boot.art, dir = e9a4, err = 0
<5>[ 16.328991,3] F2FS-fs (dm-0): recover_data: ino = ff8f, recovered = 0 blocks, err = 0
<5>[ 16.329037,3] F2FS-fs (dm-0): recover_dentry: ino = fe63, name = system@framework@boot.oat, dir = e9a4, err = 0
<5>[ 16.329059,3] F2FS-fs (dm-0): recover_data: ino = fe63, recovered = 0 blocks, err = 0
<5>[ 16.331357,3] F2FS-fs (dm-0): recover_data: ino = fe63, recovered = 872 blocks, err = 0
<5>[ 16.331697,3] F2FS-fs (dm-0): recover_data: ino = fe63, recovered = 111 blocks, err = 0

Seems it continues to do something after the filesystem check, because msm_thermal kicks in, and "something" is running (for some time), because I've got entries like this at the end.

<6>[ 367.373783,0] msm_thermal:do_cluster_freq_ctrl Limiting CPU2 max frequency to 2150400. Temp:47
<6>[ 367.373790,0] msm_thermal:do_cluster_freq_ctrl Limiting CPU3 max frequency to 2150400. Temp:47
<4>[ 368.058105,1] smbchg_heartbeat_work: EB Input 0 mA, PMI Input 500 mA, USBC CL 500 mA, DC 900 mA
<4>[ 368.058118,1] smbchg_heartbeat_work: Step State = FIRST, BSW Mode OFF, EB State DISCONN
<12>[ 368.059266,0] healthd: usbc: Unknown power supply type
<5>[ 374.802552,2] audit: type=1400 audit(2816.970:43): avc: denied { write } for uid=0 pid=409 comm="recovery" name="recovery.log" dev="dm-0" ino=50438 scontext=u:r:recovery:s0 tcontext=u:object_r:media_rw_data_file:s0 tclass=file permissive=1
<5>[ 374.803352,2] audit: type=1400 audit(2816.974:44): avc: denied { setattr } for uid=0 pid=409 comm="recovery" name="recovery.log" dev="dm-0" ino=50438 scontext=u:r:recovery:s0 tcontext=u:object_r:media_rw_data_file:s0 tclass=file permissive=1

[MENTION=6298645]erfanoabdi[/MENTION]

I never had something like this before on my other devices.

Do you maybe know, whats causing the problems with the data partition ? (Maybe because of the encryption ?)

Have a nice weekend everyone ;)