[wrxtasy]

Tip of the Day for TvHeadend users:

Kodi > Settings > Addons > MyAddons > PVR Clients > TvHeadend HTSP Client > Configure > Streaming Settings >
Use Predictive Tuning to speedup channels switches > OK

For those with Dual Tuner setups this works nicely indeed for almost instant channel switching on ARM devices.

[Vlaves]

If you want a Simple Max CPU Performance Overlock just copy this script to a plain text file named autostart.sh

Code:

#!/bin/bash
# available Freq: 96000 192000 312000 408000 504000 600000 696000 816000 912000 1008000 1104000 1200000 1296000 1416000 1488000 1536000 1632000 1728000

echo 1728000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo performance > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

This autostart.sh file should be copied to the folder Configfiles when you SMB connect to the C1+

I have done that, but where can I check if it is successfully set?

Thanks again for all your support here

Regards
Vlaves

[wrxtasy]

SSH into the C1+ using Putty or Terminal (OSX) - copy and paste Line by Line

http://wiki.openelec.tv/index.php/Ssh_commands

user = root
password = openelec

Code:

cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

if 1728000 and performance as not spat out then Execute permissions need to be set properly...

Code:

chmod +x .config/autostart.sh
reboot

[wrxtasy]

Sadly still not working with my August T210v1/Geniatech T220. Only get FAILs when I try to scan DVB-T2 muxes in TV Headend.

Is w_scan compiled as an add-on for the ODroid C1?

w_scan is available if you install the OE Unofficial Repo. Its in one of the Sub-Folders.

As detailed in the C2 thread, T220 specific patch plugged into the v3.10.100 C1 Kernel combined along with the T230 patch as well.
Released as OE 6.95.9 / Kodi Jarvis 16.0 RC3 with updated TvHeadend Client + more.

OpenELEC-Odroid-C1-6.95.9.tar file HERE

W.

[DEcosse]

Code:

cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

if 1728000 and performance as not spat out then Execute permissions need to be set properly...

Code:

chmod +x .config/autostart.sh
reboot

I checked as above and the freq comes out at 1536000; (scaling_governer does come out as 'performance')
So I then entered the command as per above and reboot;
it still comes out as 1536000

I went into the autostart.sh file and confirmed it is as per your suggestion:

Code:

#!/bin/bash
# available Freq: 96000 192000 312000 408000 504000 600000 696000 816000 912000 1008000 1104000 1200000 1296000 1416000 1488000 1536000 1632000 1728000

echo 1728000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo performance > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

Suggestions as to why it will not pick the 1728000 frequency?

[Vlaves]

As detailed in the C2 thread, T220 specific patch plugged into the v3.10.100 C1 Kernel combined along with the T230 patch as well.
Released as OE 6.95.9 / Kodi Jarvis 16.0 RC3 with updated TvHeadend Client + more.

OpenELEC-Odroid-C1-6.95.9.tar file HERE

W.

Is this OpenELEC-Odroid-C1-6.95.9 the update for OpenELEC-Odroid-C1-6.95.7 (mean like a stable version)?
So should I update?

Btw. does the ODROID still have problems with ethernet? I saw in other posts ppl. having buffering issues in Kodi, which were solved by setting that port, where the ODROID ist connected to, to 100Mbit.
I used your advanced settings file, but since I changed my port to 100Mbit I don't need it any more. No buffering issues at all even without the advancedsettings file and much faster start in playback.

Thanks again

regards
Vlaves

[wrxtasy]

I'm not sure what Ethernet problems you are talking about ?
I've never had an issue, like ever.

Unfamiliar with this Port changing to 100Mbit either......please explain.

That OE 6.95.9 is stable as far as I'm concerned.
It's using the older Kernel with minimal patches with these numerical releases.

@noggin - Are you able to test your T220 if possible with OE 6.95.9 pls ?

[Vlaves]

I'm not sure what Ethernet problems you are talking about ?
I've never had an issue, like ever.

For example here and here

Unfamiliar with this Port changing to 100Mbit either......please explain.

I'm able to switch the port on my routers switch to 100Mbit, on which the Odroid is connected to. Same you can do in linux on commandline, something like setting the ethernet card to 100Mbit manually and not let it autodetect speed.
After I changed it on my router, the speed is awsome, everything I start playing even with just standard cache settings start play immediatelly. If you want to test, simply remote advancedsettings.xml and start playing something. After that set the ethernet port to 100Mbit, it will start playing instantly everything.

That OE 6.95.9 is stable as far as I'm concerned.
It's using the older Kernel with minimal patches with these numerical releases.

Okay Thanks a lot for all your work and support here, will update then as soon as possible

Regards
Vlaves

[wrxtasy]

Ethernet RJ-45 jack
The standard RJ45 Ethernet port for LAN connection supports
10/100/1000 Mbps speed. The green LED Flashes when there is 100
Mbps connectivity, and the yellow LED Flashes when there is 1000
Mbps connectivity

I've always had a Yellow connector light = GigaBit Ethernet

Yes sounded like a Router issue.

[Vlaves]

Ethernet RJ-45 jack
The standard RJ45 Ethernet port for LAN connection supports
10/100/1000 Mbps speed. The green LED Flashes when there is 100
Mbps connectivity, and the yellow LED Flashes when there is 1000
Mbps connectivity

I've always had a Yellow connector light = GigaBit Ethernet

Yes sounded like a Router issue.

Exactly that is the problem, the lights are showing that one have 1000Mbit, but the speed is not there. With 1000Mbit Videos should start instantly without the need to adjust Kodi cache settings. I guess there is still some problem. If I set router port to 1000Mbit the yellow LED flashes, but I get buffering issues, without adjusting cache in Kodi. If set it to 100Mbit, no single buffering issue. And Kodi as far as I understood calulates how much it needs to cache based on the ethernet speed it gets reported. But if ethernet then is not delivering data fast enough, then there is buffering.

At least thats how I understood the Kodi caching, please correct me if I'm wrong.

Anyway it is working perfectly for me set to 100Mbit, so I wanted to share in case someone else is expiriencing the same issues.

Regards
Vlaves

[DEcosse]

Not sure if you missed my post above wrxtasy (I realize you can't catch everything!)

Suggestions as to why it will not pick the 1728000 frequency?

Any ideas/suggestions there?

[Vlaves]

Not sure if you missed my post above wrxtasy (I realize you can't catch everything!)

Suggestions as to why it will not pick the 1728000 frequency?

Any ideas/suggestions there?

For me the same. Just tested it. Execution rights are set prperly on the autostart.sh. Commands copied from here inside the file. "Performance" gets set, but the 1728000 doesn't get set.

Also don't know, why not. If I execute those commands in terminal and then check everything seems to be set correctly, but after reboot only the "Performance" part gets set or it was set once prior and also gets not set while start.

Regards
Vlaves

[wrxtasy]

I suspect its something to do with the copying and pasting of what I have written above into a plain text file and the script is failing, try this instead:

Code:

nano .config/autostart.sh

Copy and paste below:

Code:

#!/bin/bash

echo 1728000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo performance > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

CTRL-O to save, CTRL-X to exit.

Code:

chmod +x .config/autostart.sh
reboot

[Vlaves]

I suspect its something to do with the copying and pasting of what I have written above into a plain text file and the script is failing, try this instead
...

Thanks a lot, that worked perfectly I guess you were right, it was a copy and paste error...

Thanks again for all your support here

Regards
Vlaves

[DEcosse]

Thanks - it wasn't quite that smooth for me but got there:
I initially tried from a linux machine directly from Terminal;
When the file opened in the editor it had the code as per original suggested config;
I deleted the entire content and inserted the new code in whole,, saved to filename, and exit, followed by chmod & reboot
That still did not 'take'
Repeated once again and still same result.

I exited my linux machine and went to windows machine; used cyberduck and deleted the autostart.sh file;
then exited cyberduck and used putty to ssh in once again;
this time obviously it was creating a new autostart.sh which was initially blank
After executing as per your last instruction, it did in fact work and happy to report is now at the higher frequency