hi, the box goes to my avr not TV, but avr is not changing something. so I don’t have to set it up?
or will the setting change the dv tunneling protocol shown here via avr overlay?
currently all works perfect in tv led with my old lg oled b7 - colours look great!! 
but maybe slightly wrong who knows…
many thanks for your help!!
It shouldn’t change anything. Everything on your setup looks correct.
it’s just to good what you guys are doing here!!
many many thanks!!
I’ve ordered a second amb6+,
question
can I
→ and then use my backup I’ve made from the current box (3.5 gig all boxes checked) to ‘restore’ ( or better customize) the new box?
just like that? or all add ons and skin manual install before?
thanks!!
I did a restore successfully like that so you should be OK.
thanks!! sounds very good! I thought maybe I have to install all add ins before and that wound mean adding repositories… if they are included that saves hours
thanks!
I have CoreELEC running on MMC now, I was able to SSH into the box and access /usr/share/kodi/addons/skin.estuary/xml directory, there is a DialogueButtonMenu.xml. I opened it in nano but it tells me that this file is not writeable and Ctrl+O confirms that I cannot edit. CoreELEC is root by design, so sudo command doesn’t help. Any advise?
What are you trying to do? The CE OS is read-only and therefore cannot be edited.
Hi Have the C7, years ago a pro calibrator on AVS forum shared his DOLBY info file that he had calibrated into his set, it did make a noticeable difference on the black floor and colour balance, I also have a C9 which I autocal Dolby Vision myself, calibration can make a lot of difference, don’t worry about the flag in TV led mode on the LG’s they know, the only media player I had a problem with on the LG’s is the Shield and the Red push but that is well documented.
Hi how do you autocalibrate? I have an lg c6.
sounds good! but I’m just enjoying the good equipment. I don’t think I will ever calibrate… not so a techie. I anyway have colours set on 22 from 100 and not warm on my b7, I don’t like funky colours… and it’s looks def absolutely great now. it looks warm while it isn’t
I was only asking because I still don’t understand the autostart sh file consequences in dv Pic transmission.
its more an interest than an actual issue here…
ive now learned it’s not changing the displayed tunnel data 8bit 444 rgb, but I thought tv led dv is always transmitted like this… so why is this auto start file a topic for someone…
My TV has 4K modes of 25 fps and 60 fps, but there is no 50 fps mode. every time I play DV video of 25 fps and 50 fps under this version of CE, it will automatically change to Player Led Dolby Vision mode at 60 fps,even if I set “Settings->System->Display->Refresh Rate” to 25Hz, CE will still switch to Player Led Dolby Vision mode at 25 fps when playing these videos. Similarly, when playing HDR10 and HLG 4K videos of 25 fps and 50 fps, the CE will automatically become 60 fps output too, maybe is this a tiny bug ?
ps. When playing videos of 24 fps, this CE is absolutely correct . my CE is set to switch fps automatically and “Settings->System->Display->Refresh Rate” is always 60Hz.
I am trying to edit DialogueButtonMenu to remove MMC reboot option. I am afraid that my spouse will use it. I do have CE installed on MMC. Not sure if this option will mess things up if she clicks on it.
There no any issue when it boot to android. Just need simple reboot, and CoreElec will boot again.
You dont need Edit anything…
Your only solution would be to copy the Estuary to /storage/.kodi/addons | rename it | make your changes | Select this new skin via the GUI.
Another option is to install another skin, like Estuary Mod V2, that allows editing of the boot menu.
However, there’s no big deal if you boot into Android anyhow.
It shouldn’t be a big deal at all. The bug was fixed a long time ago and now it doesn’t matter if you boot into android. Reddit has outdated information.
FYI Still had issues last time I did this.
If you use Bluetooth - for example had paired in Bluetooth the provided remote, then booting into Android will mess with the permissions and basically breaks the pairing in CE which then needs to be corrected and the remote paired again.
Would be happy to hear that is fixed and I have out dated info?
@cpm Looks like it was pushed 3 weeks ago:
Thanks, looks cool - I guess may still need to pair again as I recall Android deletes the config - but no need to reset the permissions.
It’s been fine for me since the fix. I just rebooted to android some days ago and my Bluetooth kb is still working.
About | FAQ | Terms of Service | Privacy Policy | Legal Notice
