PINE64

I found a weird problem that occurs when starting my Pine.

When I plug in the power i don't get any input on my TV.
To get the image showing I need to disconnect the HDMI cable and reinsert it (hotswap).
I have red in another thread here that hot swapping is NOT recommended with the Pine.

I have tried choosing another input on the TV and than back to the Pine, but this doesn't help. 

Anyone else having this issue?

My setup is Pine A64+ 2Gb running Android 5.1.1 (Rooted) build 20160505


If anyone have a fix for this that would be nice. Or maybe I'll just have to wait for the next build to see if its fixed then.

(05-22-2016, 11:43 AM)Tarjei85 Wrote: [ -> ]I found a weird problem that occurs when starting my Pine.

When I plug in the power i don't get any input on my TV.
To get the image showing I need to disconnect the HDMI cable and reinsert it (hotswap).
I have red in another thread here that hot swapping is NOT recommended with the Pine.

I have tried choosing another input on the TV and than back to the Pine, but this doesn't help. 

Anyone else having this issue?

My setup is Pine A64+ 2Gb running Android 5.1.1 (Rooted) build 20160505


If anyone have a fix for this that would be nice. Or maybe I'll just have to wait for the next build to see if its fixed then.

Weird bug - have you reported it here ? I cannot help you unfortunately, but you are correct hdmi does carry a low DC charge and therefore could potentially damage equipment.

No I havent reported the bug there yet. Will do later today.
Thanks for the reminder.

One more question, does this happen with all images or just android?

I have only tried android, and it is only on the ××0505 image.

Not an expert (at all!) but could this be a HDMI handshake issue ?

I have no idea. I'm a noob when it comes to this. Will check it out and troubleshoot some more later. Thank you.

After some more testing. I got really surprised. The problem went away. Just suddenly. No idea what caused it.

Was changing HDMI-cables, power cables and psu with no luck, so when I gave up for the night and reconnected the settings I had when the problem surfaced, it was gone. I have not been able to provoke the problem to reaccur after that.

Good to know mate that said ... very strange...

(05-27-2016, 04:33 AM)Luke Wrote: [ -> ]Good to know mate that said ... very strange...

Yes in deed... now I just have to provoke the error so I can try to figure out what did it... *AndTheNextProjectIsBorne