UK[UE40F5500]freezes trying to change server IP or port.

[martint123]

R1a patches were installed - to be safe I copied them again, but date/time stamps were the same. Still stuck at loading....
Tomorrow I will empty the EPG and just reload a few hours to see if there is any iffy data in there. Meantime I'll swap IP address over on my servers so I can get back to teh working system.....
thanks again

[martint123]

Right - it appears to be something in the EPG. What I have just tried.

Copy database file from working test machine to problem machine...... Samsung app works fine.
Copy old problem database back....... app freezes at "loading current programmes".
Empty EPG using npvr setting option....... App goes to the main menu without problem.

to-do. reload problem database and think of a way to partially empty the EPG to try to find the troublesome entry.

[reven]

if you could send it to me, i could test against it to find the problem entry. or if you look at the web.log file for the last request before it freezes and then recreate that entry in chrome/ie/firefox and save that as a xml file.

[martint123]

I couldn't spot any specific point in the weblog to pin down an entry when I looked yesterday and now the logs have rolled over ;(

On the plus side, after the overnight EPG update it is working, so my slow chopping of the database to pin it down got it to the 13th.

I attach a copy of the db from yesterday if you want to try to identify the problem - nothing odd was noticed on a PC or NMT whereas on the samsung app it was a show stopper right from the off. You will have to crank your date back to the 13th.

p.s. for future ref, is there any way to force the app into setup mode like when first installed with no IP previously set??

thanks for your time.

hmmm, no attachment, maybe too big. dropbox link in a few minutes,

https://www.dropbox.com/s/cgvg99av1nltiq...pvrdb3.zip

[martint123]

attached in dropbox link https://www.dropbox.com/s/cgvg99av1nltiq...pvrdb3.zip

[reven]

you could try stopping nextpvr on the server to get a connection timeout, which should just take you to the main menu with "Settings" and "Exit" available. from there change the server ip (i havent test this).

ill try and look at the db in the next few days, busy making a web portal atm which will allow logs to be uploaded from the app

[martint123]

Excellent, stopping the service gets back to the settings/exit menu so that is very helpful.

Sadly It froze again this morning.

Copied good database from test machine to proposed new, freezing, machine and starts ok.
I copied the database from the freezing machine to the good test machine and it stopped in the same place. So it is something in teh database upsetting things.

The two machines have different tuners and different epg sources (the good one, dvb-t and the freezing xmltv.exe grabbing from the UK atlas source - needed for STB channels.).

[reven]

ok, heres the problem

Code:

<description>The life and career of the Croydon-born supermodel, who was famously spotted as a 14-year-old by an agent at JFK airport and has become one of the world&ppos;s most photographed women, as well as the subject of a gold statue by sculptor Marc Quinn.</description>

the "&ppos;" is invalid.

also

Code:

<channel id='7429' name='Discovery Home & Health' number='240'>

and

Code:

<channel id='7430' name='Discovery Home & Health +1' number='241'>

and

Code:

<channel id='7451' name='Crime & Investigation Network' number='553'>

and

Code:

<channel id='7452' name='Crime &amp; Investigation Network +1' number='554'>

the "&" aren't encoded to "&"

I thought sub fixed the "&" to amp; issue in one of the updates. which i thought were included with those packaged updates....

the "&ppos;" might be ok, some xml validators i ran it through complained, however chrome only complained about the "&" not encoded to "&".

sub if you read this can you let us know if this has been fixed in a patch?

[sub]

I definitely fixed the ampersand in the channel name in one of the patches that was posted (and current code still has that fix).

[reven]

martin try applying the patch here

looks like johnsonx42 might not have included it, since it was built on different build machine but appears to be fine.