[Matt Devo]

after some days of tries/installations ive arrived to a stable OSes configuration with a dual boot, but I'm having a slight issue.
I'm used to watch movies in Kodi 14.1 under Lubuntu (latest Intel 1.07, Kodi is configured as supposed to) and *sometimes randomly* the CPU spikes/stucks up and starves Kodi decoding, which litterally stop for a second or two, and then resumes, with of course 2 seconds of dropped frames.

I've studied the taskmanager performances and found no evidence of a *random* task asking for high cpu cycles, and since i'm not running any background task nor server (just a little FTP server, which is mostly off), I'm wondering if Kodi itself could be the reason.
Should I maybe configure/disable something under Kodi (samba, upnp, etc.), which could be cause of this issue?

Is this a known issue or is particular of mine?

monitor using top via ssh to see what's causing the CPU spikes. It's not a known issue that I'm aware of.

I have some questions please.

In Dual boot mode, one has to keep Developer mode on otherwise CTRL-D to boot to Chrome won't work, correct? If developer mode is turned off what happens to the setup?
With 16GB SSD and allowing 8Gb to Openelec, why is it the free space for ChromeOS Data(documents,etc) ends up to be approx 2GB only?
I have setup the box sucessfully on a small 22" LED Monitor as when i turned developer mode, my old Samsung TV fails to bring up image but should it work after a full setup of OpenElec?

Thank you.

If you turn off developer mode, the system will go back to stock -- booting immediately to ChromeOS, with no access to the legacy boot function. Your OE partition/data shouldn't get erased, but won't be accessible.

The ChromeOS disk layout consists of 12 partitions (including the 2 used for OpenELEC), so whatever free space it's reporting is likely only the userdata partition.

There's no reason to think it won't work on your TV, but obviously you'll have to dual boot blindly