[Galaxy Note 3 Android Development] Eleo:
Well, for future references, your report should include more informations. For example see mine:

THESE ARE NOT DEFAULT SETTINGS/CHOICES AND SHOULD NOT BE USED AS DEFAULT FOR ANYBODY ELSE!! THESE ARE ONLY MY CHOICES AND I CAN CHANGE THEM WHENEVER I SEE A NECESSITY!

- N9005

- BL: QA3 CP: PD1 (doesnt matter country, you should mention the last three characters, because it tells whether your BL and CP are latest or old)

- Materialized TWRP 2.8.7.0

- Using dualboot patcher

- Flashed MagMa NX UX8.5 ROM to a new data slot (i.e. clean flash)

- Before ROM, flashed phantom kernel 1.2i for n9005 variant

- Aroma choices:

A. N9005

B. Kernel pre-installed

C. CSC - TUR

D. S-Cloud + Floating messages + Accessibility

E. Selected Separated noti (flashed modded S8 System UI afterwards)

F. N7 SM + No UDS + White Battery

G. S8 Launcher (but using latest beta Nova Launcher)

H. 4G + Multiuser + Dual Stereo

I. N7 camera

J. Soundalive

K. TUR GPS

L. No supersu (flashed system supersu zip after ROM)

M. No busybox

N. System xposed 87.1

O. No wipe

- After flashing ROM, flashed these zips:

A. System SuperSu

B. S7 photostudio

C. Headset fix type 1

D. Debloater ver.3

E. Modded S8 SystemUI

F. SM MOD -> C5 SM

Upon any app FC, I would visit data/system/dropbox folder, and share the crash log (system apps are marked as system app crash, other app FCs are marked as data app crash).

System free space is also important mostly for users who have missing apps (like spen apps) or dont see statusbar (system space is so full that systemUI cannot start). Note 3 has fixed system space of 2.3GB. Upon latest updates of s8 apps, framework and s8 systemUI, this space can be filled fastly. If you select to install all or most of debloatables (the page with selectabke s voice, samsung cloud, edge apps and etc), your system space will be filled fastly, which will lead to issues stated above. We are working on optimizing that space.

Also, mentioning active xposed modules are important. If possible, a screenshot of xposed modules page should be provided. That is needed, because xposed is fully working on vanilla android (AOSP), but it is not fully supported by modded UI like TouchWiz, MIUI or etc. Thus this also can help to find issue.

Standard recovery wipes before flashing a ROM are wiping a) cache b) dalvik cache c) data and d) system. This is called clean flashing. If you are wiping only a) cache and b) dalvik cache, this is called dirty flashing. These are standards of zip flashing.

A special case is dualboot (or also called mutliboot). When flashing a ROM to a new slot you are automatically clean flashing. But if you are flashing to an existing slot, then same principle above is applicable (for dualboot/multiboot you can search the thread I provided enough info).

I already mentioned FC logs above. But if there is no FC but a malfunction or dysfunction, a logging app (like matlog, syslog or alogcat) should be used. For this case, all you need to do is to find a repetative pattern (for ex. when opening an X app your phone freezes for 30 seconds but does not FC). Then you need to start logging from that logging app, repeat the steps to reproduce issue, then stop logging. Afterwards, you can try removing any personal details (if somebody called or sent an email it may show up in logs) and share the logs in post. This will help devs to find the core of the issue and provide a feedback to you (like disable this menu or uncheck this settings and etc).

After performing these steps you make devs work easier by providing them with the required data.