[Galaxy Note 3 Android Development] renegade027:
High Incedence of Framework Reboots

Hi, I too have had issues with random framework reboots on both v8 and v9. This happens randomly during screen-on time, but also while the device is in my pocket or on the table. Every few minutes, in fact. Further, my phone too would freeze on the bootup screen at night.

Both times have installed the ROM with data wipes and all my apps have been downloaded from Playstore and not restored. I run no framework modifications other than the AOSP theme.

I've been on practically every version of X-ROM since about Noveber and I really really like it, so would not want to give it up. I'd rather work with people in the forum and especially the developers to see how I can resolve these issues.

Freezing Google Search and Google+ has improved the situation somewhat - now the framewrok reboots still happen spontaneously - but about once per hour. I will take a clue from people on the forum and uninstall them completely and re-instal from Play to see if that helps at all.

Both Chrome and the stock browser freeze practically on every attempt to use them.

proces.android.media is also stopping quite frequently.

Finally any app that needs to display the spinning circle for more than a second, including the system settings (i.e the settings search function) is likely to FC or cause a framework reboot.

I consider myself an experienced user, yet this time I am at a loss what to do.

I've tried running the bootloop fix mentioned here and elsewhere - no imporovement - what it actually does is erase the EFS partition and re-create it without wiping the contents. Might have helped others but not me.

I've tried the 4-piece leaked KK with a PIT file repartitioning, the Polish official firmwhare, etc. Re-flashed modems, etc. to rule out a radio issue - same - no improvement.

One thing that I've noticed in the installation log may be a clue:

Wiping + Deleting System ...
==========================
mount: failed to mount /dev/block/mmcblk0p24 at /cache: Device or resource busy
mount: failed to mount /dev/block/mmcblk0p26 at /data: Device or resource busy
Installing System please wait ...
==========================

and then, further down:

Permissions ...
==========================
set_perm: chown of /system/bin/.ext/.su to 0 0 failed: No such file or directory
set_perm: chmod of /system/bin/.ext/.su to 6755 failed: No such file or directory
set_perm: chown of /system/etc/bluetooth/auto_pairing.conf to 1000 1000 failed: No such file or directory
set_perm: chmod of /system/etc/bluetooth/auto_pairing.conf to 640 failed: No such file or directory
set_perm: chown of /system/etc/bluetooth/blacklist.conf to 3002 3002 failed: No such file or directory
set_perm: chmod of /system/etc/bluetooth/blacklist.conf to 444 failed: No such file or directory
set_perm: chown of /system/etc/init.goldfish.sh to 0 2000 failed: No such file or directory
set_perm: chmod of /system/etc/init.goldfish.sh to 550 failed: No such file or directory
set_perm: chown of /system/lib/libdummy.so to 0 0 failed: No such file or directory
set_perm: chmod of /system/lib/libdummy.so to 644 failed: No such file or directory
about to run program [/system/xbin/su] with 2 args
about to run program [/sbin/busybox] with 4 args
chmod: /data/data: No such file or directory
run_program: child exited with status 1
about to run program [/sbin/busybox] with 4 args
Installing Busybox
==========================
about to run program [/system/xbin/busybox] with 4 args
==========================
Kernel Installation
==========================
Flashing Kernel X-Note
mount: failed to mount /dev/block/mmcblk0p26 at /data: Device or resource busy
mount: failed to mount /dev/block/mmcblk0p24 at /cache: Device or resource busy
==========================
Done ...
==========================
script result was [/preload]

I don't know if this is supposed to happen this way during installation...

Anyway, any help in setting up logcat with the appropriate parameters (what app do you use guys, haven't done this in like 2 years; or a terminal command???) and then reading/interpreting it would be greatly appreciated.

Finally, I too think, that unappreciative comments are not appropriate and if anyone does not like the development direction of this ROM could try something elese.

Best regards,

Nick