A OnePlus User Found A Bug When He Took A Screenshot While Watching Porn With Headsets On

It seldom happens that you come across certain instances which somehow are capable of making your day. We came across one such incident today. This will definitely lighten you up and at the same time rejenuvate your face with a smile.

OnePlus had announced it's beta program back in October. Through the means of the program, the company intends to take in help and feedback from the user community for solving bugs. As the beta builds are not stable, they are susceptible to bugs and users who volunteer to take part in the beta program are willing to try out some extra features at the cost of being exposed to some bugs. As it turns out, one of the OnePlus users apparently did not have a great experience when he came across a bug.

If you are one of those Android enthusiasts who love to try out custom ROMs, then you might be familiar with the way in which one should report bugs. You have to attach a logcat, which will allow the developer to make out where the software code is going wrong and at the same time, you must also mention how the bug can be replicated. In simpler terms, if the developer wants to come across the same bug you did, what all should he do. It might be opening an application and then doing certain stuff. Oh boy, I'm seriously laughing now. So give this paragraph another read after you have read the bug report which the user raised to OnePlus. This is what he had to say:

HI GUYS,
So today, I was in the living room watching porn with earphones on. I then decided to take a screenshot. 
GUESS WHAT HAPPENED? THE SOUND SWITCHED FROM EARPHONES TO LOUDSPEAKER for 5 secondsMy mom who was in the other room immediately came out and stared at me. I didn't know what to do. I just left. WTF ONEPLUS? HOW THE HELL DID THIS BUG POP UP ON NOUGAT?

After testing it later again, I see that it works for both wynk music and YouTube app. 

FIX THIS RN. THIS IS WORTHY OF A HOTFIX.

DO Y'ALL HAVE THIS ISSUE?

The forum thread was then bombarded by some salt rubbing into the wounds and some hearty laughs. As expected though, the thread was shortly closed for further replies by a moderator. Moderators might be people associated with OnePlus after all, so does that mean that OnePlus did notice the bug after all? I have my own doubts over that.

We can definitely make certain conclusions from the bug report. Although I don't prefer to analyse stuff like this, I really couldn't help myself here. The post made by the user dates back to December 26 and the user mentions that he came across the bug on Nougat. So this surely has to be one of the Nougat based OxygenOS beta builds for the OnePlus 3, since only OnePlus 3 and 3T have beta Nougat builds. The stable Nougat rollout for both the devices had begun on December 31, following which OnePlus 3T got it's first Nougat based beta build.

Although we can't surely confirm whether this bug still exists or not, but one of our readers indeed tested this out on his OnePlus 3 and claims that the bug still exists. However we can't assure you the authenticity of this claim.

They say that walls have ears, so, do blog walls have ears too? In case something like that does exist, knock-knock, OnePlus are you listening?

Source: OnePlus forums

Krittin Kalra

Krittin Kalra is a 20 year old Android freak. Striving for passions, chasing down his dreams and living a life without regrets is his sole mantra. A bit moody, he also does custom ROM reviews for AndroGuider. Currently pursuing his B.Tech, he aspires to follow his heart.