yashsingh1/xdaforums huggingface dataset:
[Magisk] martyfender:
I would suggest that you provide device info and Magisk_debug.log, Magisk_log, install logs and maybe logcats as per the OP, so someone else can try to help you.

Upon looking back at your recovery log, I see you have the f2fs file system for data. Have You tried the f2fs loopback fix Magisk Module?

Flashing a custom kernel can help with this, instead of using the module.

UPDATE: I see you have a custom kernel, I presume since your recovery log states you are flashing OxygenOS, so the f2fs loopback fix is probably not needed, sorry. I am at a handicap since I don't own such devices.

https://xdaforums.com/apps/magisk/guide-magisk-official-version-including-t3577875

If you try the module, you must flash it through TWRP, not in the Magisk Manager.

Maybe your device forums will have better info on this and if it is compatible with Oreo.

In the OxygenOS forums I see they are providing the stable, Magisk 16.0.
[Magisk] dcop7:
For me it is strange as I never had this problem before v14.3 I think. After this version I saw that was a commit related to fstab. Maybe broke something? I provided the flash log. My device is a oneplus 3t with stock oreo 5.0.1 (android 8.0.0).

But for now, I have a workaround. Thanks
[Magisk] martyfender:
Your recovery log states that you were flashing the OxygenOS. Forgive me, but I thought that was a custom rom, not stock.

---------- Post added at 09:55 PM ---------- Previous post was at 09:50 PM ----------

In your recovery log, it states that you flashed OxygenOS. Forgive me, but I thought that was a custom rom, not stock. What is your workaround, flashing the noforce.zip?
[Magisk] NLBeev:
I got the idea you flashed stock. In case of patching error you'll lose decryption.
[Magisk] edwardmlyte:
16.3 beta worked fine. I installed 16.4 with the automatic method and after restarting the device magisk manager app will no longer stay onscreen on my Honor 9. Root continues to work in every way, however I cannot load the app for future upgrades, or adding extra apps to magisk hide.

--------- beginning of crash
[ 05-07 09:27:09.273 32171:32254 E/AndroidRuntime ]
FATAL EXCEPTION: AsyncTask #4
Process: com.topjohnwu.magisk, PID: 32171
java.lang.RuntimeException: An error occurred while executing doInBackground()
at android.os.AsyncTask$3.done(AsyncTask.java:365)
at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
at java.util.concurrent.FutureTask.run(FutureTask.java:271)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
at java.lang.Thread.run(Thread.java:784)
Caused by: java.lang.NullPointerException: Attempt to read from field 'java.util.LinkedList$Node java.util.LinkedList$Node.next' on a null object reference
at java.util.LinkedList$ListItr.next(LinkedList.java:893)
at com.topjohnwu.magisk.database.RepoDatabaseHelper.removeRepo(Unknown Source:10)
at com.topjohnwu.magisk.asyncs.UpdateRepos.doInBackground(Unknown Source:92)
at com.topjohnwu.magisk.asyncs.UpdateRepos.doInBackground(Unknown Source:2)
at android.os.AsyncTask$2.call(AsyncTask.java:345)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
... 3 more

Full logcat available at https://pastebin.com/k6DkkmjB
[Magisk] dcop7:
Yes, after flashing magisk, flashing force disable encryption
[Magisk] USA-RedDragon:
Latest Magisk Manager Beta and Stable both crash on startup:

Logcat is here:

https://pastebin.com/L0HKCwMd

Version before latest stable works fine
[Magisk] johnholley123:
I'm having a problem on Magisk beta 16.4 on my OP3T running DU where installing modules in TWRP takes a lot longer than usual. I haven't had this issue with previous versions of Magisk. Recovery log attached.
[Magisk] jellybean13:
Magisk has stopped.

OS: MediaTek AOSP

Android version: 6.0 (MRA58K)

Kernel version: 3.18.22+

Logcat:

05-10 19:57:59.551 31825 31941 E AndroidRuntime: FATAL EXCEPTION: AsyncTask #6

05-10 19:57:59.551 31825 31941 E AndroidRuntime: Process: com.topjohnwu.magisk, PID: 31825

05-10 19:57:59.551 31825 31941 E AndroidRuntime: java.util.ConcurrentModificationException

05-10 19:57:59.551 31825 31941 E AndroidRuntime: at java.util.LinkedList$LinkIterator.next(LinkedList.java:124)

05-10 19:57:59.551 31825 31941 E AndroidRuntime: at java.util.LinkedList.removeOneOccurrence(LinkedList.java:835)05-10 19:57:59.551 31825 31941 E AndroidRuntime: at java.util.LinkedList.removeFirstOccurrenceImpl(LinkedList.java:830)

05-10 19:57:59.551 31825 31941 E AndroidRuntime: at java.util.LinkedList.remove(LinkedList.java:665)

05-10 19:57:59.551 31825 31941 E AndroidRuntime: at com.topjohnwu.magisk.asyncs.UpdateRepos.lambda$loadJSON$1$UpdateRepos(Unknown Source)

05-10 19:57:59.551 31825 31941 E AndroidRuntime: at com.topjohnwu.magisk.asyncs.UpdateRepos$$Lambda$1.run(Unknown Source)

05-10 19:57:59.551 31825 31941 E AndroidRuntime: at com.topjohnwu.magisk.asyncs.UpdateRepos.lambda$queueTask$0$UpdateRepos(Unknown Source)

05-10 19:57:59.551 31825 31941 E AndroidRuntime: at com.topjohnwu.magisk.asyncs.UpdateRepos$$Lambda$0.run(Unknown Source)

05-10 19:57:59.551 31825 31941 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)

05-10 19:57:59.551 31825 31941 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)

05-10 19:57:59.551 31825 31941 E AndroidRuntime: at java.lang.Thread.run(Thread.java:818)
[Magisk] dcop7:
Hello,

Not long ago I posted a problem with my oneplus 3t. I've reset everything. When to stock and started again.

Now, I'm having another problem. I boot, the phone is OK. After a while in suspended mode (screen off), I turn on the screen and I can't turn on wifi. I saw that are a few others with this problem. But I notice a few differences.

Where are a few notes:

- I can't switch wifi on, the switch turns off

- I opened an app to get logs and when it asked for root permission, the wifi worked! It turn on automatically

- after a while in suspended mode (without any reboot), I couldn't turn on wifi again. Then, I've opened magisk manager and it was a bit strange, I've posted a screen shot. The only thing that was in the main page was the thing circle in blue. I've used another app to ask root permission, the wifi turns on again and the main page of magisk goes to normal.

- I couldn't find logs in /data/adb, or /data/adb/magisk

- I'm on v16.0 stable and magisk manager 5.7

The only logs I could find are these:

05-13 02:16:35.808 478 975 I Magisk : ** late_start service mode running 05-13 02:16:35.823 478 975 I Magisk : * Running service.d scripts 05-13 02:16:35.823 478 975 I Magisk : * Running module service scripts 05-13 02:16:36.528 478 504 I Magisk : proc_monitor: zygote ns=mnt:[4026533652] zygote64 ns=mnt:[4026533736] 05-13 02:17:12.333 478 504 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=4869 ns=mnt:[4026534401]) 05-13 06:47:49.585 478 11828 E Magisk : sqlite3 open failure: unable to open database file 05-13 06:47:50.083 478 11862 E Magisk : sqlite3 open failure: unable to open database file

Can anyone help?
[Magisk] jenslody:
If you have no internet connection, your Manager looks like you described, so that part is normal.

You should update to Magisk beta (if you are on 32-bit device) or try my unoffical build, that includes 64-bit binaries. Or wait for a new beta, I guess it comes soon, as John is currently doing some work on Magisk.
[Magisk] dcop7:
I already tried v16.4 without luck. But is strange that the wifi only turns on when an app asks for root
[Magisk] ZUUUNN:
Im using v16 it didn't work same as v16.4 and I don't know how to upload it lol sorry

- Device platform: armeabi-v7a

- Extracting files

- Patch boot/ramdisk image: /dev/block/mmcblk0p20

boot_patch.sh: ./util_functions.sh: boot_patch.sh: ./util_functions.sh: line 15: grep: Permission denied

line 15: ps: Permission denied

boot_patch.sh: ./util_functions.sh: line 15: grep: Permission denied

boot_patch.sh: boot_patch.sh: ./util_functions.sh: line 16: grep: Permission denied

./util_functions.sh: line 16: grep: Permission denied

boot_patch.sh: ./util_functions.sh: line 17: id: Permission denied

boot_patch.sh: ./util_functions.sh: line 17: grep: Permission denied

boot_patch.sh: line 75: chmod: Permission denied

boot_patch.sh: line 78: ./magiskinit: Permission denied

- Unpacking boot image

boot_patch.sh: line 87: ./magiskboot: Permission denied

boot_patch.sh: line 117: ./magiskboot: Permission denied

boot_patch.sh: line 148: ./magiskboot: Permission denied

boot_patch.sh: line 150: rm: Permission denied

boot_patch.sh: line 177: ./magiskboot: Permission denied

- Checking ramdisk status

- Patching ramdisk

- Repacking boot image

! Unable to repack boot image!

Failed!

! Installation failed
[Magisk] zr_hazem:
Phone: HTC10 Resurrection Remix 5.8.4 Nougat

Kernel:Tabp0le EAS AOSP 3.04

Magisk: Latest v16.4

Issue: Magisk module apps disappeared after reboot. I've provided the magisk log. I've read that this is a common issue and rebooting helps but it didnt in my case. In magisk manag3r it shows that magisk is installed and modules are installed but the modules apps dont appear in my app drawer. It's not the first time this happens to me and I'll probably reinstall magisk from scratch but its really annoying because i feel that it risks the stability of the rom and i generally want a stable rom. Ig u cant have that with beta xD
[Magisk] Didgeridoohan:
[MENTION=8324577]zr_hazem[/MENTION] Have you enabled Core Only Mode? If so, disable it...

Edit: Or, if you don't have Core Only Mode enabled, disable the module that's running the Soilwork_uni_V10_battery_Final.sh script. It might be causing issues. Actually, depending on how careful the creator has been, you might have to go into /sbin/.core/img/.core/post-fs-data.d and remove it yourself...
[Magisk] zr_hazem:
Thats odd that module didn't install when I flashed it. Anyway i uninstalled magisk and reinstalled vut when I go into modules the old ones are still there but their apps arent showing. Tried uninstalling one by one but still modules wont show..
[Magisk] Snuuuuupy:
Huawei P10 VTR-L09C432 running Magisk 16.0: Passes SN

Huawei P10 VTR-L09C432 running Magisk 16.4: Doesn't pass SN

Will upload logs on request - just let me know.
[Magisk] Didgeridoohan:
Always

assume you need to provide logs!

From the OP:
[Magisk] yhzhou2015@163.com:
anyone has this question？after device boot a few hours, the root permission will lost, typically after uninstall an app which ever request the root permission.

eg: after i uninstall one app which ever request root permission,the naptime app got a crash with the following logs:

Caused by: com.topjohnwu.superuser.NoShellException: Impossible to create a shell!

at com.topjohnwu.superuser.b.c(Shell.java:333)

at com.topjohnwu.superuser.b.b(Shell.java:246)

at com.topjohnwu.superuser.b.b(Shell.java:803)

at com.topjohnwu.superuser.b.a(Shell.java:104)

at com.topjohnwu.superuser.b$c.b(Shell.java:433)

at com.topjohnwu.superuser.b$c.b(Shell.java:426)

at com.topjohnwu.superuser.b$c.b(Shell.java:418)

at com.franco.doze.utils.e$1.a(RootUtils.java:15)
[Magisk] Evengard:
I've got a weird problem. Scripts in /sbin/.core/img/.core/post-fs-data.d and /sbin/.core/img/.core/service.d are just not being picked up! Like if they don't exist at all. The module scripts (for example /sbin/.core/img/<some-module-id>/service.sh) works fine.

I've attached the log, but it seems like it just skips the file. In this log it is supposed to run a /sbin/.core/img/.core/service.d/test.sh script which does

touch /data/media/0/logs/test.txt

but after rebooting there is no result - the file test.txt doesn't get created. If instead I create a /sbin/.core/img/test/service.sh file with the EXACT same content (not present in the log) it actually works correctly. Seems like the core/*.d folders are somewhat ignored?
[Magisk] Iocere:
Magisk manager latest beta is crashing after a few hours uptime. After phone restart its working for a while. I'm using a 8.1 gsi.
[Magisk] siealex:
Try to disable all automatic update checks in Manager.
[Magisk] jcmm11:
Are you using the dark theme? If so try turning it off. Seems to make a difference for me. I've had no crashes with it off, do get some with it on.

Still evaluating this, but so far seems to work.
[Magisk] SacredDeviL666:
Thread cleaned.

References :-

https://xdaforums.com/showpost.php?p=72588015&postcount=1

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382

https://xdaforums.com/apps/magisk/guide-magisk-troubleshooting-t3641417

https://xdaforums.com/showpost.php?p=76379922&postcount=5618

Thanks.
[Magisk] Moozotti:
This happening with me and i did the same solution. Works fine but some times i have some freezes
[Magisk] ipdev:
Will give it a shot.

I use the dark theme but, primarily only have this issue on one device.

Never thought it may be theme related.

Also not sure the best way to word this but, calling for root before opening Manager seems to fix / avoid the FC's. Just opening a root app like AdAway for example.

I just switched the dark theme off, let's see what happens. :)
[Magisk] patster98:
On latest magisk 16.4.2 magisk "uninstalls" itself after some hours of pphone usage... Fixed after rebooting.

Oneplus 3

Nitrogen Os 8.1 18/5 build

Latest open gapps

Open beta 36 firmware

Magisk 16.4.2 beta

mods;

Cloudflare dns 4 magisk

Google sans mod font

iOS 11.1 emoji

Ram management fixes by crock

Sysconfig patcher

Viper 4 magisk
[Magisk] Downunder35m:
I use Magisk on a TCL TV and together with Whiteak in the Australian Whirlpool forum I try to "fix" the root for these smart TV's.

After a lot of problems with modules, their impossible installation and some other minor issues Whiteak created a modified Magisk.zip to fix the issues.

So it means using a patched bootloader, installing Magisk Manager and then using the Manager to flash the Magisk.zip t get full funtionality.

For example the boot partition by deafult is "found" by using standard means of locating it, same for system, recovery, vendor and so on.

However, on most TV systems the entire Android system is pretty well secured and partition infos that give more than just the block number are hard to find.

Same as far as I know for many chinese smartphones.

This causes Magisk to fail when it comes to install or use those partitions properly.

For example the Magisk folder inside the ADB folder won't be created at all.

I think I pointed in the right direction, but

here

is the Zip file Whiteak created that we use to flash to make Magisk work properly.

It would be nice if one of the developers could look into int, compare it to the default Magisk and implement some changes for one of the next releases.

I am quite certain there are other users who struggle with module installations based on the same problem.
[Magisk] kgursu:
Self-removal

Multiple times I did encounter self-removal of Magisk, where Magisk is not installed anymore, but Magisk Manager is there.

What could be the reason for this and how to prevent it?

Thanks.
[Magisk] Pater Draco:
ITs most likely the device you are using. Many will revert all system apps back to what was there on factory every few hours.
[Magisk] jenslody:
It's most likely an issue with MagiskHide being unable to remount files/folders. [MENTION=4470081]topjohnwu[/MENTION] knows about it and it's under investigation.

It would be good if people with this issue can try what happens if MagikHide is disabled (if possible).
[Magisk] Aleksanderbjorn:
Having problems with bootloop after installing modules. Tried 3 different modules and bootloop after all. Had to remove and fix mm in TWRP. Any suggestions?

---------- Post added at 12:37 AM ---------- Previous post was at 12:33 AM ----------

10-14 18:17:58.685 489 489 I Magisk : Magisk v16.0(1600) daemon started

10-14 18:17:58.693 489 493 I Magisk : ** post-fs mode running

05-21 01:20:30.110 489 2037 I Magisk : ** post-fs-data mode running

05-21 01:20:30.116 489 2037 I Magisk : * Creating /sbin overlay

05-21 01:20:30.117 489 2037 I Magisk : * Mounting mirrors

05-21 01:20:30.118 489 2037 I Magisk : mount: /sbin/.core/mirror/system

05-21 01:20:30.118 489 2037 I Magisk : link: /sbin/.core/mirror/vendor

05-21 01:20:30.118 489 2037 I Magisk : bind_mount: /sbin/.core/mirror/bin

05-21 01:20:30.118 489 2037 I Magisk : * Setting up internal busybox

05-21 01:20:30.135 489 2037 I Magisk : * Merging /data/magisk_merge.img -> /data/adb/magisk.img

05-21 01:20:30.234 489 2037 I Magisk : New module: camera2api

05-21 01:20:30.248 489 2037 I Magisk : * Mounting /data/adb/magisk.img

05-21 01:20:30.318 489 2037 I Magisk : * Running post-fs-data.d scripts

05-21 01:20:30.318 489 2037 I Magisk : * Running module post-fs-data scripts

05-21 01:20:30.318 489 2037 I Magisk : * Loading modules

05-21 01:20:30.318 489 2037 I Magisk : camera2api: loading [system.prop]

05-21 01:20:30.319 489 2059 I Magisk : * Starting MagiskHide

05-21 01:20:30.319 489 2059 I Magisk : hide_utils: Hiding sensitive props

05-21 01:20:30.319 489 2059 I Magisk : hide_list: [com.google.android.gms.unstable]

05-21 01:20:30.355 489 2059 I Magisk : hide_list: [com.snapchat.android]

05-21 01:20:30.385 489 2059 I Magisk : proc_monitor: init ns=mnt:[4026531840]

05-21 01:20:30.711 489 2185 I Magisk : ** late_start service mode running

05-21 01:20:30.711 489 2185 I Magisk : * Running service.d scripts

05-21 01:20:30.711 489 2185 I Magisk : * Running module service scripts

05-21 01:20:31.776 489 2059 I Magisk : proc_monitor: zygote ns=mnt:[4026533820] zygote64 ns=mnt:[4026533855]

05-21 01:20:51.332 489 2059 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=5144 ns=mnt:[4026533944])

05-21 01:21:04.733 489 2059 I Magisk : proc_monitor: com.snapchat.android (PID=6476 ns=mnt:[4026533973])
[Magisk] SacredDeviL666:
Hi,

Few posts have been moved to Magisk General thread.
[Magisk] infernix:
I frequently get magic manager to crash. It happens after an uptime of many hours or even days; a reboot fixes it. So unfortunately haven't found a way to reproduce. Logcat output:

05-25 05:50:07.780 16454 16454 E AndroidRuntime: FATAL EXCEPTION: main
05-25 05:50:07.780 16454 16454 E AndroidRuntime: Process: com.topjohnwu.magisk, PID: 16454
05-25 05:50:07.780 16454 16454 E AndroidRuntime: java.lang.ExceptionInInitializerError
05-25 05:50:07.780 16454 16454 E AndroidRuntime:	at com.topjohnwu.magisk.database.MagiskDatabaseHelper.openDatabase(Unknown Source:7)
05-25 05:50:07.780 16454 16454 E AndroidRuntime:	at com.topjohnwu.magisk.database.MagiskDatabaseHelper.<init>(Unknown Source:9)
05-25 05:50:07.780 16454 16454 E AndroidRuntime:	at com.topjohnwu.magisk.database.MagiskDatabaseHelper.getInstance(Unknown Source:2)
05-25 05:50:07.780 16454 16454 E AndroidRuntime:	at com.topjohnwu.magisk.MagiskManager.onCreate(Unknown Source:74)
05-25 05:50:07.780 16454 16454 E AndroidRuntime:	at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1119)
05-25 05:50:07.780 16454 16454 E AndroidRuntime:	at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5740)
05-25 05:50:07.780 16454 16454 E AndroidRuntime:	at android.app.ActivityThread.-wrap1(Unknown Source:0)
05-25 05:50:07.780 16454 16454 E AndroidRuntime:	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1656)
05-25 05:50:07.780 16454 16454 E AndroidRuntime:	at android.os.Handler.dispatchMessage(Handler.java:106)
05-25 05:50:07.780 16454 16454 E AndroidRuntime:	at android.os.Looper.loop(Looper.java:164)
05-25 05:50:07.780 16454 16454 E AndroidRuntime:	at android.app.ActivityThread.main(ActivityThread.java:6494)
05-25 05:50:07.780 16454 16454 E AndroidRuntime:	at java.lang.reflect.Method.invoke(Native Method)
05-25 05:50:07.780 16454 16454 E AndroidRuntime:	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
05-25 05:50:07.780 16454 16454 E AndroidRuntime:	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)
05-25 05:50:07.780 16454 16454 E AndroidRuntime: Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String[] java.lang.String.split(java.lang.String)' on a null object reference
05-25 05:50:07.780 16454 16454 E AndroidRuntime:	at com.topjohnwu.superuser.internal.ShellImpl.testCmd(Unknown Source:23)
05-25 05:50:07.780 16454 16454 E AndroidRuntime:	at com.topjohnwu.superuser.io.SuFile.testShell(Unknown Source:16)
05-25 05:50:07.780 16454 16454 E AndroidRuntime:	at com.topjohnwu.superuser.io.SuFile.<init>(Unknown Source:23)
05-25 05:50:07.780 16454 16454 E AndroidRuntime:	at com.topjohnwu.magisk.utils.Const.<clinit>(Unknown Source:5)
05-25 05:50:07.780 16454 16454 E AndroidRuntime:	... 14 more
[Magisk] Vishal P:
Hi,

Magisk Manager is crashing everytime, when I go to downloads section of magisk manager. Check attachment.

Device: Redmi note 3

OS: Nitrogen OS Oreo 8.1
[Magisk] guest4711:
Did you grant "storage" permissions to MagiskManager?
[Magisk] Vishal P:
Yes
[Magisk] Parzival_UY:
Hi topjohnwu,

I PM'd you before cause I couldn't make Magisk work on my Nexus 4. After several attempts during the weekend I gave it a try on my Nexus 6P. Following the same steps I was able to pass SafetyNet check using v16.0, so that's something I can't wrap my head on.

Anyway, I tried using v16.4 but now I'm not able to pass SafetyNet check. Tried reinstalling several times but still can't go through.

I uploaded magisk_debug.log like asked to Drive: https://drive.google.com/open?id=1eCVDtYGmk4GEXBY9nngIrllD3kznFwN4

If there's anything I could check for further information, please let me know.

Any insight would be appreciated.

Thanks
[Magisk] Tickle.:
Hi guys,

I have a problem occuring. My satynet check was not succesful until now so I flashed the "universal safetyfix patch"

result, after rebooting magisk manager told me Magisk is not anymore installed.

I go back to recovery and try to flash it => Error

I try to uninstalled magisk => Error.

So I'm completely in a deadend.

What can I do please ?

Thanks
[Magisk] gothicVI:
1. Logs!

2. If it's not specifically beta related post in the general thread.

Gesendet von meinem Moto G (5) Plus mit Tapatalk
[Magisk] Tickle.:
1. I tried to get one but didn't find it...

2. Main thread is closed

Edit: After some manipulation, I finally manage to flash v.16 but when I reboot, still nothing => magisk is not installed. anyway I'm going to upgrade my rom tonight. I think it will clean all this up.
[Magisk] Didgeridoohan:
It certainly is not... The release thread is closed, but the main support thread is wide open and tons of users are posting completely useless reports here in the beta thread that actually belong in the support thread instead.

Any kind of useful posts about the beta release are completely drowned in general support questions and useless posts about SafetyNet (that [MENTION=4470081]topjohnwu[/MENTION] specifically asks in the OP to keep out of this thread).

Yes, if it wasn't apparent, I'm a little annoyed about the state of this thread...