nDroid v1.2.x (Beta) support thread

[bgowland]

I'm hoping this will work - my machine doesn't always play nice going into or coming out of standby so I've had a couple of odd results. I think it should be OK though.

I've only included the 4 main files - stopping the nDroidService and dropping these in place then start the service again should work.

EDIT: Attachment moved to post #1

[BrettB]

Living in a GMT time-zone working with a UTC (effectively GMT) data source and pretending it belongs to various people in different time-zones and adjusting accordingly and deciding if the Guide list looks the way they should see it. Sounds so easy. :eek:

OK, the attached (I hope) should fix the time-offset issues. If it does, I'll move it to post #1 as the current release.

Well, it's closer. Now the listings are only off by 1 hour. I'm guessing that yesterday they would have been correct, but today, since daylight savings time began today, they are showing up 1 hour earlier than they should. (i.e. a show which actually starts at 7pm is listed as starting at 6pm)

[agerdin]

bgowland,

Been trying the differernt releases for some days now and I just cannot get it to work. Since trying the last time I have rooted my phone and is now running Android version 2.3.3.

Installing according to instructions but I am getting "INVALID CREDENTIALS" in the logs.

Code:

13-03-2011 19:48:11.453 CreateHttpListener() listening...
13-03-2011 19:49:26.578 Url: http://192.168.0.100:8790/
13-03-2011 19:49:26.578 request: System.Net.HttpListenerRequest
13-03-2011 19:49:26.578 hrhkey.Key: x-ndroid-action hrhkey.Value: download
13-03-2011 19:49:26.578 hrhkey.Key: x-ndroid-file hrhkey.Value: channel.zip
13-03-2011 19:49:26.578 hrhkey.Key: x-ndroid-exdata1 hrhkey.Value: admin
13-03-2011 19:49:26.578 hrhkey.Key: x-ndroid-exdata2 hrhkey.Value: 5f4dcc3b5aa765d61d8327deb882cf99
13-03-2011 19:49:26.578 hrhkey.Key: Connection hrhkey.Value: Keep-Alive
13-03-2011 19:49:26.578 hrhkey.Key: Accept-Encoding hrhkey.Value: gzip
13-03-2011 19:49:26.578 hrhkey.Key: Host hrhkey.Value: 192.168.0.100:8790
13-03-2011 19:49:26.578 INVALID CREDENTIALS
13-03-2011 19:49:26.578 CreateHttpListener() listening...

I am sure I am using the same credentials as in my NEWA and they are also entered in the nDroidSettings.xml file.

Any ideas?

\\Agerdin
\\Agerdin

[bgowland]

I'm guessing that yesterday they would have been correct, but today, since daylight savings time began today, they are showing up 1 hour earlier than they should.

At least we got to that sooner rather than later. I wasn't sure if the offset function I'm using included DST or not - now we know. Relatively quick fix, I'll post an update ASAP.

I am sure I am using the same credentials as in my NEWA and they are also entered in the nDroidSettings.xml file.

All I can suggest is to reset everything to the defaults...

1. Reset npvr on the MVP & web settings page to use admin and password for username/password
   
2. Edit nDroidSettings.xml to be the same NOTE use something simple like Notepad as there's a possibility something like Wordpad might introduce Unicode characters which would cause problems
   
3. Restart the nDroidService after making the above changes as they are only read at startup
   
4. Reset the nDroid client on you phone to use the same (or leave it alone if you haven't changed them on your phone as these are the defaults).
   

NOTE: These are ALL case-sensitive.

Let me know if you still have problems.

[bgowland]

bump

[BrettB]

Installing according to instructions but I am getting "INVALID CREDENTIALS" in the logs.
\\Agerdin

I think that when I was first trying this out I was running into a similar problem. If I recall correctly, the nDroidServiceHelper.log showed the user and password correctly from the nDroidSettings.xml file, but the nDroidServiceListener.log file was always using the "admin" and encrypted "password" instead of what was specified in nDroidSettings.xml.

[bgowland]

I think that when I was first trying this out I was running into a similar problem. If I recall correctly, the nDroidServiceHelper.log showed the user and password correctly from the nDroidSettings.xml file, but the nDroidServiceListener.log file was always using the "admin" and encrypted "password" instead of what was specified in nDroidSettings.xml.

The username and password in the nDroidSettings.xml file must be in plain text - encryption is handle by the service helper to match the NEWA credentials.

[bgowland]

As the title says, I've updated the nDroid client to compensate for DST. I'll move this to post #1 when I get confirmation that things work how they should.

EDIT: Attachment moved, download from post #1

[marcuswar]

I think that when I was first trying this out I was running into a similar problem. If I recall correctly, the nDroidServiceHelper.log showed the user and password correctly from the nDroidSettings.xml file, but the nDroidServiceListener.log file was always using the "admin" and encrypted "password" instead of what was specified in nDroidSettings.xml.

Yes same here, what ever username and password I put in the nDroidSettings.xml gets ignored and it seems to be using the defaults of "admin" and "password". I've changed the NEWA password back to the default "password", rstarted the services and it now connects fine. Looking in the logs the hashed password string is always the same, so it looks like the nDrod client is not honouring the username and password settings.

[BrettB]

As the title says, I've updated the nDroid client to compensate for DST. I'll move this to post #1 when I get confirmation that things work how they should.

That did it. Thanks!