@Firelord if the downvote on this answer was yours: please consider removing it (maybe after Azza updated the post). Don't be fooled by the URL in the answer; it doesn't refer to a web service, but to an application – so the answer is fully valid, but massively lacking details (as I've pointed out in my comment).

@Izzy Yes, it is my downvote and I already acknowledged it on that post. But because a vote once locked cannot be changed unless the post is edited, I asked OP for an edit. :)

@Firelord Yupp, saw it meanwhile. So I'd say: the next turn is the OP's :)

Yuck! Ran out of votes... All hands: join me fighting down the review queue! I'm out of close-votes, but there are plenty questions left in the queue. Hurry, before the queue turns 4-digit #D

Is it justified to use tag connection-issues on questions like this?

I just rejected an edit made on that post which corrected no critical issues but only added that tag. The tag excerpt says that, use it if you have issue connecting device via Wifi, bluetooth, USB, or to mobile network. However, OP can load the pages in browser so network connectivity is fine, the problem is with Play Store only. // I posted this issue here because a high-rep user also used that tag on similar question here. So, am I wrong?

@Firelord Checking its tag-wiki, I'd say no. This is rather one of the "very special playstore issues", and thus tagged correctly.

@Firelord Well, according to Roman and Greek mythology, even gods can err :)

Ouch. Does that mean I could be wrong as well?

#D

@Firelord su beep, huh? LOL "Unknown id: beep" #D

Translating the command: "Switch to User 'beep'". Never heard of that user.

(my device neither)

And there he comes.

See his avatar landing :)

@Izzy The return of the Lord :D

@Firelord Oh my. Yeah, I've earned that... #D

And he punished me with fire, the Lord...

@Izzy I missed that technical inaccuracy because I was surprised how he wrote that answer with such confidence when OP and I had exact error, in fact, he didn't even consider my comment. You literally blew that answer. #D

@Firelord Thanks – I very much hope so (unless he can name a device where that works). I'm pretty confident he wasn't even trying that, but only "guessed" so from his Linux console.

(disclosure: that happened to me once as well, so I've (hopefully) learned my lesson)

But we could be both wrong: Have you tried it via adb shell, or via ssh? It might behave different.

I have no sshd running on any Android device, so I cannot test.

@Izzy Tried SSH and still same.

@Izzy But it makes me wonder, the shell is same, privileges differs, but gaining root privileges shouldn't make things different be it from SSH or ADB. Right?

@Firelord Ah, good – thanks. So we cannot blamed for that later :D

@Firelord Yes and no. The difference might be whether your "session" has a "tty" assigned.

(i.e. whether it counts as "local session")

Why would there be a beep command if it wouldn't work? If you try it locally (e.g. via a terminal app), I bet it would make an ugly noise.

So what's the difference from "being root via adb" and "being root locally"? Permission-wise I'd say nothing.

Yuck. Strike that. Just tried using the console built-in to JuiceSSH. No beep, neither as user nor as root: "beep: can't open console". So wut the heck is beep for then?

@Izzy Nope, at least in my devices, I see the same error even locally.

^^

Roger, confirmed that.

One day I'll setup my device to "electrocute" the user whenever beep was run. Definitely makes a noise then – though it will rather be an "eek" then #D

… and not come out of the speakers, but of the "speaker" (ahem, user's mouth)

@Izzy Sure about eek! :D

I'll call that feature "remote control" :)

Btw, in case you're using Linux on (one of) your computer(s): I've released Adebar 1.2 yesterday. Moah features and some little fixes. And already plans for the next version :)

OK, good night then: 1:30am here already, and I've gotta go to work tomorrow…

@Izzy Would see it for sure, but a few hours later since I would be going for sleep in few minutes.

@Firelord Heh! Yeah, full ack :)

Me too :)

Ok then. :) No su beep now for some hours. :D

Btw: Wiki (also on Github) was updated along, so everything should be up-to-date. Feel free to ping me if you've got questions.