I know, although the probability of that is low, as I said, no time at the moment to fiddle with it.You possibly are risking corrupted data with that.
I know, although the probability of that is low, as I said, no time at the moment to fiddle with it.You possibly are risking corrupted data with that.
should work.Will this work on c6602 ?? And any bugs so far?
Looking into that, we've recently added newly introduced 'sdcardfs'.Indeed there was random reboot
Here is the last kmsg
I will further look into this, if no solution is brought up, we will revert the full sdcardfs./* XXX
* Original sdcardfs code calls inode_permission(lower_inode,.. )
* for checking inode permission. But doing such things here seems
* duplicated work, because the functions called after this func,
* such as vfs_create, vfs_unlink, vfs_rename, and etc,
* does exactly same thing, i.e., they calls inode_permission().
* So we just let they do the things.
... */
That's old kernel and not from Chippa_a build (since the kernel version is 3.4.112).On stock kernel (build from cm repo) F2FS seems instable. Dmesg:
Code:[ 1446.561279] init: Untracked pid 13676 exited with status 0 [ 1525.714660] binder: 12456: binder_alloc_buf, no vma [ 1525.719085] binder: 1097:5326 transaction failed 29201, size 76-0 [ 1525.733001] binder: 1097:5326 transaction failed 29189, size 1068-4 [ 1670.148345] ------------[ cut here ]------------ [ 1670.152130] kernel BUG at ../../../../../../kernel/sony/apq8064/fs/f2fs/node.c:2205! [ 1670.152130] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM [ 1670.152130] Modules linked in: [ 1670.152130] CPU: 1 Not tainted (3.4.112-odin-g18938610f78 #1) [ 1670.152160] PC is at flush_nat_entries+0x3cc/0x53c [ 1670.152160] LR is at flush_nat_entries+0x394/0x53c [ 1670.152160] pc : [<c039954c>] lr : [<c0399514>] psr: 20000013 [ 1670.152160] sp : e8405d20 ip : 00000000 fp : c25ed000 [ 1670.152160] r10: 000013b6 r9 : ee4597e0 r8 : e6a5f4d0 [ 1670.152160] r7 : 00000001 r6 : 00000000 r5 : e6a5f4c8 r4 : e6a5f4d0 [ 1670.152191] r3 : 00000001 r2 : 00000000 r1 : 20000013 r0 : c204ba1c [ 1670.152191] Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user [ 1670.152191] Control: 10c5787d Table: a99a406a DAC: 00000015 [ 1670.152191] [ 1670.152191] PC: 0xc03994cc: […] [ 1670.153411] [<c039954c>] (flush_nat_entries+0x3cc/0x53c) from [<c038da18>] (write_checkpoint+0x2e8/0xba8) [ 1670.153411] [<c038da18>] (write_checkpoint+0x2e8/0xba8) from [<c03855cc>] (f2fs_sync_fs+0x90/0xf4) [ 1670.153411] [<c03855cc>] (f2fs_sync_fs+0x90/0xf4) from [<c0379a0c>] (f2fs_do_sync_file+0x33c/0x670) [ 1670.153442] [<c0379a0c>] (f2fs_do_sync_file+0x33c/0x670) from [<c0379d64>] (f2fs_sync_file+0x24/0x2c) [ 1670.153442] [<c0379d64>] (f2fs_sync_file+0x24/0x2c) from [<c029306c>] (vfs_fsync+0x20/0x28) [ 1670.153472] [<c029306c>] (vfs_fsync+0x20/0x28) from [<c02933d0>] (sys_fdatasync+0x1c/0x30) [ 1670.153472] [<c02933d0>] (sys_fdatasync+0x1c/0x30) from [<c01062a0>] (ret_fast_syscall+0x0/0x30) [ 1670.153472] Code: ebfa8c94 e5953014 e3530000 0a000000 (e7f001f2) [ 1670.153503] ---[ end trace faa72f49d02715fe ]--- [ 1670.153503] Kernel panic - not syncing: Fatal exception [ 1670.160186] CPU0: stopping [ 1670.160186] [<c010ce04>] (unwind_backtrace+0x0/0x138) from [<c010bd28>] (handle_IPI+0x138/0x240) [ 1670.160217] [<c010bd28>] (handle_IPI+0x138/0x240) from [<c0100590>] (gic_handle_irq+0x138/0x164) [ 1670.160247] [<c0100590>] (gic_handle_irq+0x138/0x164) from [<c0b019c0>] (__irq_svc+0x40/0x74) [ 1670.160247] Exception stack(0xec305e00 to 0xec305e48) [ 1670.160247] 5e00: 00000058 00000010 c8c34000 60000013 c132f550 c132f550 00000058 00000002 [ 1670.160247] 5e20: 00000006 c132fe70 c132f550 c132f550 00000000 ec305e48 00a000df c019cda4 [ 1670.160278] 5e40: 60000013 ffffffff [ 1670.160278] [<c0b019c0>] (__irq_svc+0x40/0x74) from [<c019cda4>] (console_unlock+0x318/0x3d8) [ 1670.160308] [<c019cda4>] (console_unlock+0x318/0x3d8) from [<c0af20c0>] (console_cpu_notify+0x54/0x60) [ 1670.160308] [<c0af20c0>] (console_cpu_notify+0x54/0x60) from [<c0b03414>] (notifier_call_chain+0x40/0x68) [ 1670.160339] [<c0b03414>] (notifier_call_chain+0x40/0x68) from [<c019e4f0>] (__cpu_notify+0x2c/0x48) [ 1670.160339] [<c019e4f0>] (__cpu_notify+0x2c/0x48) from [<c019e568>] (cpu_notify_nofail+0x10/0x1c) [ 1670.160369] [<c019e568>] (cpu_notify_nofail+0x10/0x1c) from [<c0ac6584>] (_cpu_down+0x150/0x2f0) [ 1670.160400] [<c0ac6584>] (_cpu_down+0x150/0x2f0) from [<c0ac6750>] (cpu_down+0x2c/0x40) [ 1670.160400] [<c0ac6750>] (cpu_down+0x2c/0x40) from [<c0ac80f0>] (store_online+0x2c/0x78) [ 1670.160430] [<c0ac80f0>] (store_online+0x2c/0x78) from [<c02bed54>] (sysfs_write_file+0x108/0x13c) [ 1670.160430] [<c02bed54>] (sysfs_write_file+0x108/0x13c) from [<c026c284>] (vfs_write+0xac/0x160) [ 1670.160461] [<c026c284>] (vfs_write+0xac/0x160) from [<c026c5d0>] (sys_write+0x38/0x64) [ 1670.160461] [<c026c5d0>] (sys_write+0x38/0x64) from [<c01062a0>] (ret_fast_syscall+0x0/0x30) [ 1670.160491] &@[email protected]:*mpdecision* [ 1670.160491] wcnss_8960: crash shutdown : 0 [ 1670.661132] &@[email protected]:*libraries-threa* [ 1675.662994] Rebooting in 5 seconds.. [ 1675.662994] Restarting Linux version 3.4.112-odin-g18938610f78 ([email protected]) (gcc version 4.9 20150123 (prerelease) (GCC) ) #1 SMP PREEMPT Sat Apr 1 03:06:25 CEST 2017 [ 1675.662994] [ 1675.713012] arm_restart: Console was locked! Busting [ 1676.877990] [ 1676.879394] Restarting Linux version 3.4.112-odin-g18938610f78 ([email protected]) (gcc version 4.9 20150123 (prerelease) (GCC) ) #1 SMP PREEMPT Sat Apr 1 03:06:25 CEST 2017 [ 1676.879394] [ 1676.897155] Going down for restart now
I am currently using the kernel from the lineage repo with f2fs updates manually pulled and haven't had a reboot since then (2 days). But as far as I see Chippa_as kernel has the buggy f2fs kernel: https://github.com/Chippa-a/android_kernel_sony_apq8064/commits/cm-14.1/fs/f2fs and your kernel seems to be the same: https://github.com/daedroza/kernel_sony_apq8064/commits/cm-14.1/fs/f2fsThat's old kernel and not from Chippa_a build (since the kernel version is 3.4.112).
You can build with my kernel (see repo kernel_sony_apq8064) or go with Chippa_a kernel.
I've updated to .113 and lots of thing including CVE. Chippa_a is using a older rebase (no changes in functionality, just few changes in commit history)I am currently using the kernel from the lineage repo with f2fs updates manually pulled and haven't had a reboot since then (2 days). But as far as I see Chippa_as kernel has the buggy f2fs kernel: https://github.com/Chippa-a/android_kernel_sony_apq8064/commits/cm-14.1/fs/f2fs and your kernel seems to be the same: https://github.com/daedroza/kernel_sony_apq8064/commits/cm-14.1/fs/f2fs
jonpas reported to have reboots daily with f2fs, I suspect him to use this kernel.
Use Google drive scannerDoes any one having trouble with camscanner?
It FC all the time, tried to uninstall and install again but the problem persists...any one?
Have you tried downloading the rom again? Maybe first time you got a bad filehii i flash rom in recovery mod but it stuck at this msg ((patching system image unconditionally))
i used tWRP 3.0
i try many rom and i get the same msgHave you tried downloading the rom again? Maybe first time you got a bad file