[Samsung Galaxy Ace 3] ChipKng:
Test results

I tried this new rom ( 20160929 ) and noticed the followings:

- Alarm sound cannot be changed. As you select the new item, it goes back to the 'buzz' sound.

- No random reboot on the first 2 days \o/

But after that, the random reboots are back:

[ 8657.841658] PM: Device wcnss_wlan.0 failed to suspend: error -1
[ 8657.841750] PM: Some devices failed to suspend
[ 8657.848159] tsu6721 15-0025: dev1: 0x0, dev2: 0x0, dev3: 0x0, ADC: 0x1f Jig:eek:FF
[ 8660.985470] init: avc: granted { set } for property=net.rmnet1.dns1 pid=238 uid=1001 gid=1001 scontext=u:r:rild:s0 tcontext=u:object_r:net_radio_prop:s0 tclass=property_service
[ 8661.010039] init: avc: granted { set } for property=net.rmnet1.dns2 pid=238 uid=1001 gid=1001 scontext=u:r:rild:s0 tcontext=u:object_r:net_radio_prop:s0 tclass=property_service
[ 8661.030122] init: avc: granted { set } for property=net.rmnet1.dns3 pid=238 uid=1001 gid=1001 scontext=u:r:rild:s0 tcontext=u:object_r:net_radio_prop:s0 tclass=property_service
[ 8661.047518] init: avc: granted { set } for property=net.rmnet1.dns4 pid=238 uid=1001 gid=1001 scontext=u:r:rild:s0 tcontext=u:object_r:net_radio_prop:s0 tclass=property_service
[ 8664.810467] tsu6721 15-0025: dev1: 0x0, dev2: 0x0, dev3: 0x0, ADC: 0x1f Jig:eek:FF
[ 8665.240895] tsu6721 15-0025: dev1: 0x0, dev2: 0x0, dev3: 0x0, ADC: 0x1f Jig:eek:FF
[ 8665.701143] tsu6721 15-0025: dev1: 0x0, dev2: 0x0, dev3: 0x0, ADC: 0x1f Jig:eek:FF
[ 8666.141552] tsu6721 15-0025: dev1: 0x0, dev2: 0x0, dev3: 0x0, ADC: 0x1f Jig:eek:FF
[ 8666.413183] dpm_run_callback(): power_suspend_late+0x0/0x64 returns -11
[ 8666.413213] PM: Device power.0 failed to suspend noirq: error -11
[ 8666.415258] PM: Some devices failed to power down
[ 8666.571706] tsu6721 15-0025: dev1: 0x0, dev2: 0x0, dev3: 0x0, ADC: 0x1f Jig:eek:FF
[ 8666.651791] Unable to handle kernel paging request at virtual address 00008303
[ 8666.658689] pgd = d801c000
[ 8666.661069] [00008303] *pgd=00000000
[ 8666.665190] Internal error: Oops: 5 [#1] PREEMPT SMP ARM
[ 8666.669859] Modules linked in: adsprpc
[ 8666.673735] CPU: 0 Tainted: G W (3.4.0-cyanogenmod-g69dae2a #1)
[ 8666.680938] PC is at kill_fasync+0x30/0xa8
[ 8666.684784] LR is at kill_fasync+0x20/0xa8
[ 8666.689087] pc : [<c0159bdc>] lr : [<c0159bcc>] psr: 20000193
[ 8666.689087] sp : d72abbf0 ip : 00000000 fp : d72abd90
[ 8666.700563] r10: 00000000 r9 : c09a6d00 r8 : 000cc405
[ 8666.705507] r7 : 00004601 r6 : 00020001 r5 : 0000001d r4 : 000082ff
[ 8666.712313] r3 : 00000001 r2 : d7207740 r1 : 0000001d r0 : c0fac940
[ 8666.718539] Flags: nzCv IRQs off FIQs on Mode SVC_32 ISA ARM Segment user
[ 8666.726017] Control: 10c5787d Table: 9e01c06a DAC: 00000015

And other one:

[ 1721.790324] dpm_run_callback(): power_suspend_late+0x0/0x64 returns -11
[ 1721.790324] PM: Device power.0 failed to suspend noirq: error -11
[ 1721.792674] PM: Some devices failed to power down
[ 1721.914390] tsu6721 15-0025: dev1: 0x0, dev2: 0x0, dev3: 0x0, ADC: 0x1f Jig:eek:FF
[ 1722.175430] dpm_run_callback(): power_suspend_late+0x0/0x64 returns -11
[ 1722.175461] PM: Device power.0 failed to suspend noirq: error -11
[ 1722.178757] PM: Some devices failed to power down
[ 1722.304684] tsu6721 15-0025: dev1: 0x0, dev2: 0x0, dev3: 0x0, ADC: 0x1f Jig:eek:FF
[ 1722.714939] tsu6721 15-0025: dev1: 0x0, dev2: 0x0, dev3: 0x0, ADC: 0x1f Jig:eek:FF
[ 1723.075171] tsu6721 15-0025: dev1: 0x0, dev2: 0x0, dev3: 0x0, ADC: 0x1f Jig:eek:FF
[ 1723.322081] dpm_run_callback(): power_suspend_late+0x0/0x64 returns -11
[ 1723.322111] PM: Device power.0 failed to suspend noirq: error -11
[ 1723.325346] PM: Some devices failed to power down
[ 1723.455363] tsu6721 15-0025: dev1: 0x0, dev2: 0x0, dev3: 0x0, ADC: 0x1f Jig:eek:FF
[ 1723.491225] Unable to handle kernel paging request at virtual address f8f02042
[ 1723.497634] pgd = d7298000
[ 1723.500533] [f8f02042] *pgd=00000000
[ 1723.503982] Internal error: Oops: 5 [#1] PREEMPT SMP ARM
[ 1723.508224] done.
[ 1723.509049] PM: suspend exit 2016-10-06 13:41:10.581557878 UTC
[ 1723.509079] suspend: exit suspend, ret = -11 (2016-10-06 13:41:10.581618864 UTC)
[ 1723.509110] active wake lock mmc1_detect
[ 1723.509140] active wake lock ipc00000017_Loc_hal_worker
[ 1723.509171] active wake lock sec-charger-monitor
[ 1723.509171] suspend: abort suspend
[ 1723.541400] Modules linked in: adsprpc
[ 1723.545185] CPU: 0 Tainted: G W (3.4.0-cyanogenmod-g69dae2a #1)
[ 1723.552265] PC is at kill_fasync+0x30/0xa8
[ 1723.556325] LR is at kill_fasync+0x20/0xa8
[ 1723.560414] pc : [<c0159bdc>] lr : [<c0159bcc>] psr: a0000193
[ 1723.560414] sp : c69b7d18 ip : 00000000 fp : c69b7e30
[ 1723.572104] r10: 00000000 r9 : c09a6d00 r8 : 00022c03
[ 1723.577078] r7 : 00004601 r6 : 00020001 r5 : 0000001d r4 : f8f0203e
[ 1723.583854] r3 : 00000001 r2 : c6a8aec0 r1 : 0000001d r0 : c0fac940
[ 1723.590111] Flags: NzCv IRQs off FIQs on Mode SVC_32 ISA ARM Segment user
[ 1723.597527] Control: 10c5787d Table: 9d29806a DAC: 00000015

So it seems the suspend still has some issues in the kernel. What I see before these the following:

[ 1331.884968] dpm_run_callback(): platform_pm_suspend+0x0/0x50 returns -16
[ 1331.884968] PM: Device alarm failed to suspend: error -16

When my girlfriend turned off the "alarms" permanently - because of the annoying buzz sound -, the phone seems stable. No reboots yet. I'll test further and will let you know the result. Fingers crossed. If the phone remains stable with alarm disabled, then I take a deeper look into the alarm device.