Openelec Build for OPI PC and 2 now with HW decoding

xonex

I have tried with fresh image and waiting for 10mins.. After 2-3 minutes the OpenElec logo was displayed and then it went to Input Not Supported again.

As my monitor has two states - No signal when unplaged and Input Not Supported when there is some signal but it looks like as it can not be displayed I believe there is something running on my board but it just can not be displayed on the screen.

How can I debug it?

jernej

xonex replied at 2016-5-12 23:36
I have tried with fresh image and waiting for 10mins.. After 2-3 minutes the OpenElec logo was displ ...

Connect serial adapter to RX,TX and GND pins and provide the output.

chaszim

Dima replied at 2016-5-12 13:45
I also have Orangepi PC.I have tried the main functions of user settings: configured some addons li ...

Most people hate to admit when their wrong, fortunantly, I'm not one who suffers that. I think I found my error, in the sequencing, of how to change &save settings.So, I suppose, all my objections, to the other changes, are now rendered mute. And, sorry for the delay, I was at the hospital in Tampa, most of the day for tests.

This is how it works,

>Customer Setting "Task Bar" Main

System > (Confluence)Appearance > Skin > -Settings > Home window options > --- /show video information ("on" to add) /show weather information ("on" to add) ---- /Hide-Music ("on" to exclude) /Hide Pictures ("on" to exclude)
-exit -back
-exit -back
-exit -back  or the "Home" tab works too (to home screen / task bar)
choose power tab /reboot  ---> retains changes
                          /shutdown ---> retains changes

choose power button pc <2x> shutdown - restart---> retains changes
choose power button pc <1 long>  reboot---> retains changes
                          /power plug ---> looses changes

>Customer Setting "Task Bar" Subs
System > (Confluence)Appearance > Skin > -Settings > Add-on Shortcuts Add-on  <add> 1 /(Israel Live) 2/ (cCloud TV) 3/(channel PEAR)
(same for "Programs")
Home tab
choose power tab /reboot  ---> retains changes
                          /shutdown ---> retains changes

choose power button pc <2x> shutdown - restart---> retains changes
choose power button pc <1 long>  reboot---> retains changes
                          /power plug ---> looses changes


Results same as above, working.


Once the unit shuts down by any of the above shutdowns, except pulling the plug, It should have saved the settings. But, after normal shutdown is where I pull the plug, to conserve power, and other security issues. And that's where the mistake occoured. Even after shutting down normally the settings aren't saved unless you've reboot without power loss at least once.
Now, let me wager a guess here. You fixed the PC power button, about 1 or 2 images back, from 4/28. So, to restart the computer before a working power button, after normal Tab Shutdown, you had to pull the power for restart? And the settings did hold without issue before then.



My error was not rebooting to save the change.


You can't pull the power plug, until you've fully rebooted, at least once, restarting with the power button, and then shutdown again, using the shutdown tab. Once done, you can pull the plug and the settings will still hold.
So it boot>, settings>, Home>, reboot>, shutdown>, pull the plug. This works & the settings then hold.
Once everything is saved, you can pull the plug anytime after, even while watching something, that as long as there's nothing being saved, which you need if an app locks up the system.
I'm still waiting to see if the power button work on a system lockup


  
But, I still don't understand, what's going on with the time/date, dropping to 1969, &, why clock set fails for me on openELEC. I've got a thought on that. I've seen no descussion, on what time server Open/Kodi uses. The time server I add in Open's Network setting, says, keep the "pings" to a minimum, else your black listed.
So, my thoughts are, the unit looses signal from the server, it continues, until interupted, & requires to re-sync. When it can't, it runs back to the bios, which was likely written in 1969 in unix or c/pm, and takes that as the correct time stamp. It's either a problem to be solved by whoever wrote the original versions of OpenELEC. But it could just as easily be a hardware problem with OrangePi clock or bios. So, the first thing is to figure out which. It effects the ability to display accurate Time, Weather and other information, so it needs to be addressed.
Edit: BTW SD card is a 16gb. FAT is 5.12mb Free, about 128mb used EXT4 14.33GB Free / 1.72gb used

jernej

chaszim replied at 2016-5-13 00:37
Most people hate to admit when their wrong, fortunantly, I'm not one who suffers that. I think I f ...

The reason why it falls back to 1. 1. 1970 (give or take timezone) is format which is internally used for time representation. That is something called unix time stamp and 0 means, you guess it, 1. 1. 1970. This is something which was invented in old unix days (70's obviously) and it remained standard to this day. So unless you syncronize with time server, it will stay that way, because there is no RTC on board.

I will add syncronization command to sleep, so it hopefully preserve the data.

chaszim

jernej replied at 2016-5-12 23:43
I will upload new build soon (few days) to fix some things and one of them will be wifi driver cra ...

how do you do dmesg without a cable? And, please tell me more about how to load a new image from withing openelec. I get you use a tar file but how/where, is it downloaded etc. And location of tar file.

chaszim

jernej replied at 2016-5-13 07:46
The reason why it falls back to 1. 1. 1970 (give or take timezone) is format which is internally u ...

Yea, now it apparently save after re-boot. Ideally it should be save on exit from page. But, you know we'll take what we get, and like it. Thanks And, right again I remember now too, that there was no real time clock module onboard. Which I looked at one, for the RPI, (pretty cheep) wondering if it would be too nasty to interface. I still haven't got around to loading the new image, it's been a rough couple of days. should I hold now till the new new image comes out?

lymon

jernej replied at 2016-5-13 07:46
The reason why it falls back to 1. 1. 1970 (give or take timezone) is format which is internally u ...

Maybe include the "fake-hwclock" package ?
I use it on other devices that don't have a RTC and  it will reset the time/date to that of the last reboot..even if you don't have a network/ntp connection (yet)

jernej

chaszim replied at 2016-5-13 01:19
Yea, now it apparently save after re-boot. Ideally it should be save on exit from page. But, you kn ...

Adding RTC should not be too hard nor expensive. Usually, it's not included beacause it needs some kind of another type of power supply likw button cell battery.

It's on you if you want to update. Some bugs are fixed, some introduced... I thought I make clear where to update file in latest prebuild images thread. Check FAQ point 12 for update instructions. But if you do update, you can enable automatic updates from now on.

jernej

lymon replied at 2016-5-13 05:53
Maybe include the "fake-hwclock" package ?
I use it on other devices that don't have a RTC and  it  ...

I'm not a fan of adding things which are not by default in other official images.

Dima

chaszim replied at 2016-5-13 08:02
how do you do dmesg without a cable? And, please tell me more about how to load a new image from w ...

You an dmseg through putty and SSH (first enable SSH in openelec settings).
Updating image: just upload tar file in "updates" folder with Samba (in Windows just go to network, find your openelec orangepi there). However, since last update you will be able to go to settings -> Openelec settings and there choose update