[Nexus 4 Original Android Development] show-p1984:
If you are a dev you have no time to pry the information out of somebody. You filter out messages that are incomplete or just plain stupid, ruthlessly. You are blunt, because you just have no frakking time to say please and maybe and could you every time you explain something, which happens 50 times a day though the frakking information is already in the first post or on google!

eg: Person X asks: "How do I get a kmsg?"

What you think about that person: "Ok, a newbie, np I will tell him."

What mods think about that person: "Why the frak do we have a search function?"

What hackers (aka devs) think about that person: *throws the post into the imaginary trash can*

eg: Person X says: "Crashed x times because y didn't function properly and it overall sucked! I reverted back to stock!"

What you think about that person: "Valid feedback."

What mods think about that person: "Somewhat lacking information but valid."

What hackers (aka devs) think about that person:

a) That person just assumes that feature y is broken while he has no clue what he is doing or about anything he just assumes would be broken. Strange dude #ignore or be blunt. (depending on time available)

b) That person has done some digging and found out that feature y is broken but didn't include the frakking log. #ignore or assume a) because if he had done some digging he surely would have included the log.

c) What the... #imaginary-trash-can

If I would be polite and pry out the necessary information out of everybody this wouldn't be a full time job, this would be impossible to accomplish on a 24 hour day.

I highly suggest that you read the link in my signature, which explains this situation and the misconception that someone is angry just because he is blunt quite good.

For example this would be a hole-in-one issue report which never, ever occurred (this issue is just a dummy):

##############################################

Let's start with the place: The ISSUE TRACKER, not the thread!

Device: mako

Android version: 4.2.1

Kernel version: Bricked 0.75

Settings: STOCK

Title: Kernel panic and hard reboot. Null pointer oops in do_sweep2wake()

Content:

Hi,

I recently experienced hard reboots due to kernel panics when using s2w on my mako with Bricked 0.75. It usually happens after resume from deep sleep and seems to be late_resume related. I have attached a log in which you can see a null pointer oops in do_sweep2wake().

[OPTIONAL, IF YOU HAVE PROGRAMMING KNOWLEDGE:]

My research showed that the power device pointer is not checked if it is valid and therefore is NULL sometimes.

I do not know why that pointer is not set on rare occasions, but I have added this patch:

#simplified

+ if (bad_device_ptr->bla)
bad_device_ptr->bla();

This seems to fix the issue and keeps the function intact.

[IF YOU HAVE NO PROGRAMMING KNOWLEDGE:]

I googled this issues and it seems that there are source code changes required which I have no knowledge of.

I would be happy to provide any more information needed.

##############################################

I can deal with someone who has no experience, but I can't/won't deal with someone who made ignorance his/her life philosophy.