yashsingh1/xdaforums huggingface dataset:
[About XDA developers] Badger50:
Your assessment is spot on in some cases. We get called every name in the book at times just trying to make certain members aware of the rules. Which of course few read.

So when we close or move threads whether reported or not, we get the verbal hammer dropped on us at times, which is fine by me so long as they understand the consequences of their actions in return.

Personally, if I see a thread in the wrong section, I will move it as a courtesy to the correct section if there is one. We often move threads out of the "General Q & A" section to the proper device forum and so on.

The best thing an RC can do, is report a thread to be moved if you can, or just leave it to the powers that be if you so choose.

Please also understand that all Mods have their own style of moderating. Those of us that have been doing this for while, get fed up at times after countless translations, and thread moving, which could have easily been avoided if members would take just a little time to read the rules, or the "stickies" at the top of virtually every forum with instructions on where to post.

But alas, that never seems to happen.
[About XDA developers] TheMystic:
The above sums it up well. I wish I had seen everything from the other perspective better.

I looked up what happened to our OpenAL Moderator and was sad to note this update:

XDA Forums introduce OpenAL, the world's first AI-powered forum moderator

AI is here to stay, and XDA is one step ahead of the curve.

www.xda-developers.com

That mod was doing an excellent job at birth, but don't know what challenges led XDA to pull the plug on him (or her).
[About XDA developers] Oswald Boelcke:
Please don't forget @OpenAL was an April's fool created by one of my friends but also actually used by him. This means every action or post of OpenAL you saw was actually a "manual" post and action by my friend.

Revolutionizing Forum Moderation: Meet OpenAL, world's first AI Moderator

Update April 2nd: This was of course our April Fools' joke for 2023. Thank you all and be sure to check out our update here. Introducing AI Moderators: The Future of Online Content Moderation Tired of dealing with spam, hate speech, and other...

xdaforums.com

Regards

Oswald Bolecke

From my point of view, my friend @Badger50 already said everything that I intended to contribute.

Regards

Oswald Boelcke
[About XDA developers] TheMystic:
I will have to say that was very well thought out AND executed! It was too good to be true, and I made that known in comment #28, but the idea actually worked. :D
[About XDA developers] Renate:
I realize that even a move can be a rude hiccup for an OP, but I was mostly speaking of closing threads.

I've even considered having a forum for "purgatory", a one button solution for mods to shift a thread.

From there it could be allowed to sit or another mod might want to make the effort to move it to a more approriate place.

If someone posts a thread for an "Omnicron 12" in the wrong place, it gets closed, they open a new one, now we have two threads.

This just adds confusion to searches and leaves us with a one post, closed thread.

As far as stickies go, there is a large amount of sticky bloat which tends to dillute its importance.

As currently there are no specific forums that I follow (but a bunch of threads) I'm mostly on "Help Answer".

So I rarely notice what forum a thread is in when I answer a question.

One of the impetuses for this thread was an incident that occured last week.

A (presumably young) newby posted a thread. It was closed by a mod.

They opened a new thread with very unseemly language at the top.

I sent them a friendly PM (mentioning that I wasn't a mod or had any standing) asking them in their own interest to consider editting it.

They ended up (correctly) being banned. Still, this all wasn't inevitable from the start.
[About XDA developers] TheMystic:
I suggest that instead of closing/ locking the thread, the post must be hidden from public (except for the member who created it) and a notification be sent to the member to change the sub-forum to make it visible again, AFTER reading the rules of posting.

Hidden posts would be auto-deleted after a period of time, say a month. If the member doesn't bother to make the required change, the post would be gone forever.

Now the member is more likely to read the rules and post it in the correct sub-forum.

This will take care of this:
[About XDA developers] woodman:
Yes being a moderator is thankless but it is very rewarding though.

It can be interpreted as rude when people say the mod team is just a "hammer" when we do our best to maintain order and peace around the site, for free and on our free time when we have real life and family to take care of.

The first rule being a mod is to be more a mediator than a moderator. It's in their mind.

Some mods make mistake, we're human... I did a bunch myself when I was one...

But some mods can abuse their power at times (it's very rare but it happens, we had this in the past), so if it happens you can raise a report to the moderator committee if it's really worth a report. I mean If they are rude or something. The mods are not above the rules and are not untouchable.

Closing a thread or moving a thread when it's done a good way with explanations is not a problem and is not rude.

I'm no longer a mod but I still support this view.
[About XDA developers] Badger50:
While you are correct, if we don't post the "stickies," then we have no guidance for new users, or documentation to support our actions when they occur.

Ah yes! I was the one that banned that member after what he publicly called my colleague and friend after being given 2 chances to post in the correct section.

Just a small sample of what we get at times via PM's which include death threats and the ever frightening: "I'm casting a voodoo spell on your family." Good fun right there, but easily rectified 🔨🪓😉

With all due respect, I'd happily wager a bet with you on that one.😉

After being a Mod for 4+ years, I have PM'd and PSA'd members until I'm blue in the face to repeated offenders who think the rules don't apply to them.

I am always polite and calm when I do. And while most are understanding and compliant, others have called me:

Fascist

Hitler

Nazi

Communist

Zionist

Kim Jong Un

Mother*****r. Etc..etc. You get the picture.

Personally, I could care less what a virtual person thinks of me, I am simply here to do a job I happily volunteered for, and accepted.

It still amazes me after 13 years on XDA, how seriously some members take this device hacking stuff which has no bearing or meaning in the real world. It's a hobby and passion for Pete's sake, nothing more IMHO, but still.

And finally, this quote from one of my friends and mentors says it all:

To which I say: Absolutely and Hell Yeah!

So why make a big deal about it?? 😉

Badger out.😁
[About XDA developers] TheMystic:
No bets, but you can give it a try if there is nothing to lose.
[About XDA developers] simplepinoi177:
This kinda depends on where you "lurk". As it shows in the Admins and Moderators Google Doc at the bottom of every (this) page, many moderators are Forum Specific where those Forum Specific Moderators are assigned a specific section/manufacturer of the site to "patrol". The Senior Moderators pick up the slack as they are not Forum Specific and handle all sections. So if you, or any member, tend to only frequent certain sections or devices or manufacturers, you're likely to see only a smaller portion of moderators taking action in the "area".

Like stated before, all mods have their own "style". Mine is, as much as I can, will move rather than close -- but there are so many factors; depends on how much time I can give to moderating, how many other "moves" and "reports" and "translations" that I might be inundated with that needs to be addressed (where simply closing will just be quicker), Senior Members or non-new-members really should know better, stuff like that. And, like it was mentioned before, "Mediators before Moderators", but technically we can (or arguably are expected to) close & delete any post that breaks the Forum Rules -- which wrongly placed threads break the FIRST Rule #1 and #5

XDA Developers Forum Rules said​

5.​

Duplicate threads and posts will be removed

Always post in an existing thread if a topic already exists, before creating a new thread.

Use our search function to find the best forum for your device.

1. Search before posting.​

​

Use one of our search functions before posting or creating a new thread. Whether you have a question or just something new to share, it's very likely that someone has already asked that question or shared that news.​

So closing threads may be "unconstructive" (arguably) in terms of flow of the site, but it is certainly constructive in the sense that the members (especially new ones) would now understand the rules and to pay/heed attention to them -- leading to better considerations (of the rules) when creating a post; which I consider a very constructive thing/concept when it can be said that anything was added to what members knowledge through learning here (whatever it may be; in this case the rules and how to follow them)...
[About XDA developers] TheMystic:
In some of the forums, when creating a new post, there is a pop-up that shows some of the rules in a summary form, such as Search first, be mindful of using the correct sub-forum, language, etc. XDA should consider implementing a similar pop-up, especially for new members, and those who repeatedly post in the wrong sub-forum.
[About XDA developers] simplepinoi177:
But then what would us mods kill/fill our spare time with...?!?! j/k

In these forums...are they Xenforo based (which XDA is, of course)? If they are, you could probably research it and then bring it up to the site admin(s) displaying what and how it can be done. Might convince him/them to implement it...!
[About XDA developers] TheMystic:
😬

I'm not sure if they are using Xenforo, but that is what I think they do.

Here is an example when posting to Windows 11 Forum:

As you can see, there is a 'Post Thread' button on all screens. This is definitely better than how it is implemented here at XDA. I have myself struggled several times to find this button which is hidden inside each sub-forum.

When creating a new post, it first prompts you to choose the sub-forum. Again, a user is unlikely to choose the wrong sub-forum in this case. Whether he chooses the most appropriate one or not can be a matter of subjectivity.

And then this screen show up:

Not exactly a pop-up in this case, but for sure I have seen it in some forum that I don't remember now.
[About XDA developers] Renate:
Well, to add to my heap of disdain for "Questions and Answers":

I was (trying) to help someone on a thread when I noticed that it said [Solved].

I said, "Hmm, it doesn't seem solved. The last person was still crying in their beer over a bricked device."

Of course the OP had solved their problem and gone on to greener pastures (or their just desserts).

But someone else tagged on to it.

So maybe on Q&A when a solution has been found we should declare it found and close the thread to avoid a better solution being found? :p
[About XDA developers] simplepinoi177:
I'm a mod (probably the only one) that marks titles as [SOLVED] and/or changing the tag.

For me, I only do it when the OP says it's been fixed and an explanation of what was wrong/how it was fixed (however minimal it may be). But I found that many times I end up doing it and they come back a day or two later saying that either the fix didn't hold or they were mistaken initially and the problem still remained.

The thing is that they are always free to edit out the [SOLVED] and change the tag at any time, if this is the case.

Also, as you mentioned, if someone else comes on to get help on the same thing, it often looks like it isn't actually solved or resolved, but it was for the OP and not the new one -- and I should only go off of the OP who originally created the topic than anyone/everyone else.

But yes, this is why we're taught as moderators to not delete/remove threads -- so it can still be discussed in there (if not locked & closed), have as a reference, gain what had worked and didn't. I've been using XDA since '09, member since '12, and a mod not that long, and have only recently witnessed how very old threads with the same issues/topics/inquiries still come up 3-5+ years later! A lot of our members love to try to revive old devices and such....

So even though I know you were joking, this is why we wouldn't close these threads after the initial inquiry had been answered and left for other members to start a whole new one....also Rule 5.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] LuK1337:
LineageOS is a free, community built, aftermarket firmware distribution of Android 14, which is designed to increase performance and reliability over stock Android for your device.

LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.

Instructions :

https://wiki.lineageos.org/devices/guacamole

Downloads :

https://download.lineageos.org/guacamole

GPL compliance :

https://github.com/LineageOS/android_kernel_oneplus_sm8150

Reporting Bugs

DO NOT Report bugs if you're running a custom kernel or you installed Xposed

Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)

If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)

If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log

Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.

What is your--
LineageOS version:
LineageOS Download url:
Gapps version:

Did you--
wipe:
restore with titanium backup:
reboot after having the issue:

Are you using--
a task killer:
a non-stock kernel:
other modifications:

Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] darksx:
Hello folks,well we can start a new journey,build is downloaded and ready to be flashed.i can't wait to try it out.Big big thanks to Luk

PS: oh man i love new boot animation,everything is so so smooth,i'm in love with this Rom.cheers
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] aidansdead:
Just upgraded from v20. Running smoothly here! Well done! 🎉
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] kpmohamedhussain:
Upgrading from 20 to 21 with below steps, pls fonfirm??

boot to recovery

Adb sideload rom.zip

Reboot to recovery

Adb sideload gapps.zip

Adb sideload magisk.zip

Reboot
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] LuK1337:
Upgrade LineageOS on guacamole | LineageOS Wiki

wiki.lineageos.org
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] SLAlmeida:
Version 21 installed, for now all apps are working, just a little flickering on the screen
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] darksx:
I made a clean flash and didn't noticed any kind of flickering
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] kool018:
Awesome work!

I've forgotten which GApps I ended up installing with LineageOS. Is there any way to check that? I'd imagine it probably doesn't matter as long as the new GApps have the same system apps, but that's the trick!
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] almahix:
So pleased. At long last my archaic oneplus 7 pro is running state of the art software. I was so tempted to switch ROMs but I stuck with my favorite, Lineage, and now it is up to date. Thank you LuK, and the other developers who brought this to us.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] zyguo:
Hey Google is not supported on this device.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] NavHussain:
Upgraded from 20 to 21, OS is smooth but none of the apps are working... Any firmware to be installed...
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] darksx:
Did you follow upgrade instructions to the letter
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] NavHussain:
Yes, followed steps as per the wiki link. No errors during installation. But when I open any app, it just get stuck with app logo
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] wolfofthenightt:
For some reason I was unable to get the phone to be discovered by ADB on my computer with it booted to the last version of LOS20. I was able to put the phone into recovery mode to get ADB working and then complete the upgrade steps in the wiki.

If anyone can't get their phone to be recognized by their computer, try putting the phone in recovery mode.

Everything appears to be working fine so far. My only complaint is I wish there was some way to turn off the back arrow that pops up when using gesture navigation.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] NavHussain:
Any suggestions pls....
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] almahix:
Same here. I had to flash gapps and all is well. I also had to flash the magisk patched boot img which I haven't had to do in so long.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] almahix:
Everything is working fine except I can't seem to get any FTP apps to connect to my "server" upstairs. My other phone is connecting fine but not this one with lineage 21
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] 百变小鹦:
The same problem, I've tried following the steps again to update, but it doesn't work. And every time I reboot, there are different very few apps that start properly
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] 百变小鹦:
May I ask if you are experiencing the problem like 'when open any app, it just get stuck with app logo' as well? How did you solve it?
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] kpmohamedhussain:
I am not the only one, may be some bug?
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] krishnasen:
Does it support pKVM @LuK1337
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] aidansdead:
Are you using Magisk v27.0 with Zygisk enabled? If so, it might be a Magisk bug. Try disabling Zygisk and see if that resolves it, and if it does, you might want to roll back to the previous version of Magisk if you need Zygisk.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] TheKillingJoke98:
I have this flickering issue too.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] darksx:
Is this a little bit higher,all background apps are closed
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Samppaz:
Any suggestions?

OS: upgraded to lineage-21.0-20240219-nightly-guacamole-signed.zip

Camera APK: AGC_v9.2.14_v4.0_snap_gcamapk.io

+ magisk module install: op7Pro-cam-enhance-avrbin-v6.zip

When i hit record Button, timer start running and after some time when i stop it, the result is: "Video won't be saved, record time too short"

No matter how many seconds it have recorded by timer, results are always record time too short.

! My broblem is now fixed. Maybe it was wrong apk for my phone or somethink that cannot tell.!

Sorry for unnessesary post, i try to avoid them.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] frogzhou:
same here.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] darksx:
I see that build from monday is removed,probably nothing to worry about
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] mostafasaeedix:
i recently changed my battery and installed lineage 21 , i don't know it's because of the new battery or rom itself but my battery life has improved a lot ! by the way everything is so far so good . thank you dude and keep up with the good work!
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] drmagesh7:
For me rom is super smooth but battery backup is discharging fast , I think I have to change battery 🔋
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] drmagesh7:
While charging mobile getting hot and , I think warp charge is missing because it's taking so much time to get full charge
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] jpennycook:
I upgraded yesterday from LineageOS 20->21. During the initial install, adb stopped reporting any progress after 47% (as mentioned in the installation instructions) - I gave up waiting after a while and rebooted to recovery to install NikGApps Core + Digital Wellbeing + Device Health. I've not noticed any new problems so far.

Before I upgraded, I tried to take a Seedvault backup but that failed repeatedly, so I'm glad the upgrade worked!

Now charging for the first time since the upgrade. I don't use the official fast charger. I am currently seeing a charging current of just under 1.9A which was also the same before the upgrade (as per AccuBattery Pro)
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] zyguo:
Serious random reboot after enable Hey Google. About less than 1 min, for sure, but it still should be called random reboot right?

I've been found this issue for a long time, from LOS perhaps 20, 19, 18, 17 maybe more, for this device.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] yaroslavalexashkin:
Is firmware bundled with this version of LineageOS flawed? (user-settable root of trust doesnt seem to work)
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] 1nker:
Hello, folks.

I've just upgraded from 20 to 21, however I forgot to clear the gapps in /data previously, causing the phone to bootloop now.

So I'd like to ask you if there's a way to decrypt /data or delete the gapps folder in the /data file by any other means?

Thanks for help.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] 1nker:
Is it possible to downgrade the system from level 21 to level 20 to make it easier to re-decrypt /data to remove the corresponding file?

Please help.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] yaroslavalexashkin:
If you have adb access and root its very easy

When device is in bootloop you can still connect to it and /data is mounted in this state

If not, then you probably can create some init.rc script and write it into /system from recovery (idk if this would work tho)

I think its not possible to mount /data from recovery (but i may be mistaken)
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] 1nker:
Thank you for your advice, it was very helpful.

Unfortunately, I lost adb access of my phone, but I have root.

As you say, creating some scripts might be a good way to delete these files, but when I mount /system in rec, it is unwritable.

I've encountered this before, the last time I upgraded another phone. Then I decrypted /data by OrangeFox recovery, successfully deleted the gapps file and completed the system upgrade.

For now, perhaps the easiest and most feasible way to access /data is by downgrading and re-entering the system.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] znbaboy:
My device cannot pass basic integrity after updating to LineageOS 21. Can anyone else confirm?

The exact same setup works fine on my Pixel 7 Pro using LineageOS 20. Will be using that until I can pass basic integrity
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] khusika:
LineageOS does not support that matter, and it is a known issue in all LineageOS

Quirks - Device integrity | LineageOS Wiki

wiki.lineageos.org