Ndroid 1.9 Updating EPG Download Failed

[MP3746]

I have tried NDroid 1.9 on Samsung Galaxy Note 2 and works well. On an LG Optimus 4x, trying to connect to the service fails and I just see the NDroid Robot and spinning circle that goes on forever. In fact, entering any IP address or URL gives the same result so there is no indication as to whether the connection is still trying to be made or the program has hung and is just repeatedly showing the spinning circle wait icon.

Now, when I restart the LG Optimus Phone, NDroid attempts to update the EPG but I see a "Download Failed" message. I have cleared app data and also uninstalled and reinstalled but still same problem.

I am not sure what the problem is and if I am required to upload logs, please advise where I can access the log files.

Thanks in advance.

[bgowland]

Reproduce the problem and zip / attach the nDroid Service logs and let me know the time you tried it. The logs location will vary depending on Windows version.

On XP... C:\Documents and Settings\All Users\Application Data\Beetec Services\nDroid Service\logs
For later Windows versions (Vista, W7 etc)... C:\Users\Public\Beetec Services\nDroid Service\logs (I think)

Easiest thing is to do a search for a file called nDroidService.log, find the folder it's in and zip / attach everything there.

Cheers,
Brian

[MP3746]

Reproduce the problem and zip / attach the nDroid Service logs and let me know the time you tried it. The logs location will vary depending on Windows version.

On XP... C:\Documents and Settings\All Users\Application Data\Beetec Services\nDroid Service\logs
For later Windows versions (Vista, W7 etc)... C:\Users\Public\Beetec Services\nDroid Service\logs (I think)

Easiest thing is to do a search for a file called nDroidService.log, find the folder it's in and zip / attach everything there.

Cheers,
Brian

Thanks Brian but I should have made it clear. The issue is at the client side. It doesn't even attempt to make connection with the server and all I see is the android robot and the spinning circle on my LG phone. In fact, if I uninstall and reinstall and change the wifi and data plan url to random IP addresses, I still receive the same issues in that the Android robot is shown with the spinning circle. So, what I was asking originally is "Are there any logs on the Android phone that I could submit so that the developers can establish what the issue is at client side?".

Thanks in advance.

[bgowland]

Thanks Brian but I should have made it clear. The issue is at the client side. It doesn't even attempt to make connection with the server and all I see is the android robot and the spinning circle on my LG phone.

Yes, I got that but the reason I need the service logs is to see if anything at all is happening. Even if it looks like the client isn't attempting to connect, there are a few things that happen before the download occurs and it could be a server-side issue.

In fact, if I uninstall and reinstall and change the wifi and data plan url to random IP addresses, I still receive the same issues in that the Android robot is shown with the spinning circle.

Yep, that would do it. It should report that the server address is invalid but on some devices it doesn't seem to do it - part of the reason I retired the v1.x version of nDroid and moved on to developing nDroid TE where I've re-written a load of the networking code.

So, what I was asking originally is "Are there any logs on the Android phone that I could submit so that the developers can establish what the issue is at client side?".

If the Optimus is running ICS then you can download an app such as catlog and email me with the data (the beetecservices email address which should show on Google Play). If it has been updated to JB then the answer is no - JB locked things down so unless a device is rooted, it's near impossible to monitor the local logging.

[MP3746]

Hi Brian,

I have attached the log from the server. I can see nothing has been logged for past 3 days while trying to connect using the Optimus phone. I can see logs for 11/08/2013 and I assume these were for successful connection on the Samsung Galaxy Note.

Unfortunately, my Optimus phone is using Jelly Bean. I had successfully managed to get nDroid to work in the past but not sure if this was before the upgrade to Jelly Bean.

I have also tried the nDroid TE and experiencing the same problems.

EDIT : Not sure where the attachment is??? I clicked Go Advanced to add an attachment. Am I doing it correctly? Since the log isn't big, I will just copy and paste it here as I can't see how to add attachment here:


06/04/2013 14:56:38.267 serviceHelper.GetConnStrings() returned : True
06/04/2013 14:56:38.268 nDroidService v1.8.7 build: 1.8.4839.41231 started.
06/04/2013 14:56:38.269 Creating new nDroidServiceListener object...
06/04/2013 14:56:38.270 Creating new nDroidServiceStreamer object...
06/04/2013 14:56:38.271 Creating new nDroidServiceListener thread...
06/04/2013 14:56:38.271 Creating new nDroidServiceStreamer thread...
06/04/2013 14:56:38.274 Starting nDroidServiceListener thread...
06/04/2013 14:56:38.274 Starting nDroidServiceStreamer thread...
06/04/2013 14:56:38.275 OnStart() - Creating FileGenerator object...
06/04/2013 14:56:38.275 OnStart() - Creating FileGenerator thread...
06/04/2013 14:56:38.275 OnStart() - Starting FileGenerator thread...
06/04/2013 14:56:38.389 ResolveAssemblyEventHandler() called.
06/04/2013 14:56:38.389 args.Name: System.Data.SQLite, Version=1.0.65.0, Culture=neutral, PublicKeyToken=db937bc2d44ff139
06/04/2013 14:56:38.389 Attempting to find assembly: System.Data.SQLite.dll
06/04/2013 14:56:38.393 Assembly C:\Program Files (x86)\NPVR\System.Data.SQLite.dll loaded...

06/04/2013 15:08:04.263 serviceHelper.GetConnStrings() returned : True
06/04/2013 15:08:04.283 nDroidService v1.8.7 build: 1.8.4839.41231 started.
06/04/2013 15:08:04.362 Creating new nDroidServiceListener object...
06/04/2013 15:08:04.377 Creating new nDroidServiceStreamer object...
06/04/2013 15:08:04.409 Creating new nDroidServiceListener thread...
06/04/2013 15:08:04.409 Creating new nDroidServiceStreamer thread...
06/04/2013 15:08:04.471 Starting nDroidServiceListener thread...
06/04/2013 15:08:04.471 Starting nDroidServiceStreamer thread...
06/04/2013 15:08:04.471 OnStart() - Creating FileGenerator object...
06/04/2013 15:08:04.471 OnStart() - Creating FileGenerator thread...
06/04/2013 15:08:04.471 OnStart() - Starting FileGenerator thread...
06/04/2013 15:08:06.034 ResolveAssemblyEventHandler() called.
06/04/2013 15:08:06.034 args.Name: System.Data.SQLite, Version=1.0.65.0, Culture=neutral, PublicKeyToken=db937bc2d44ff139
06/04/2013 15:08:06.034 Attempting to find assembly: System.Data.SQLite.dll
06/04/2013 15:08:06.065 Assembly C:\Program Files (x86)\NPVR\System.Data.SQLite.dll loaded...
07/04/2013 11:20:31.413 Aborting nDroidServiceListener thread...
07/04/2013 11:20:31.418 Aborting nDroidServiceStreamer thread...

11/08/2013 13:11:33.677 serviceHelper.GetConnStrings() returned : True
11/08/2013 13:11:33.678 nDroidService v2.0.2 build: 2.0.4938.31086 started.
11/08/2013 13:11:33.707 Creating new nDroidServiceListener object...
11/08/2013 13:11:33.707 Creating new nDroidServiceStreamer object...
11/08/2013 13:11:33.724 Creating new nDroidServiceListener thread...
11/08/2013 13:11:33.736 Creating new nDroidServiceStreamer thread...
11/08/2013 13:11:33.794 Starting nDroidServiceListener thread...
11/08/2013 13:11:33.794 Starting nDroidServiceStreamer thread...
11/08/2013 13:11:33.794 OnStart() - Creating FileGenerator object...
11/08/2013 13:11:33.795 OnStart() - Creating FileGenerator thread...
11/08/2013 13:11:33.795 OnStart() - Starting FileGenerator thread...
11/08/2013 13:12:34.097 CustomCommand received: 130
11/08/2013 13:12:34.097 Restarting listener threads...
11/08/2013 13:22:46.081 Aborting nDroidServiceListener thread...
11/08/2013 13:22:46.092 Aborting nDroidServiceStreamer thread...

11/08/2013 13:41:50.315 serviceHelper.GetConnStrings() returned : True
11/08/2013 13:41:50.315 nDroidService v2.0.2 build: 2.0.4938.31086 started.
11/08/2013 13:41:50.316 Creating new nDroidServiceListener object...
11/08/2013 13:41:50.317 Creating new nDroidServiceStreamer object...
11/08/2013 13:41:50.317 Creating new nDroidServiceListener thread...
11/08/2013 13:41:50.317 Creating new nDroidServiceStreamer thread...
11/08/2013 13:41:50.319 Starting nDroidServiceListener thread...
11/08/2013 13:41:50.319 Starting nDroidServiceStreamer thread...
11/08/2013 13:41:50.319 OnStart() - Creating FileGenerator object...
11/08/2013 13:41:50.320 OnStart() - Creating FileGenerator thread...
11/08/2013 13:41:50.320 OnStart() - Starting FileGenerator thread...
11/08/2013 13:42:04.457 CustomCommand received: 130
11/08/2013 13:42:04.457 Restarting listener threads...
11/08/2013 13:42:05.947 Aborting nDroidServiceListener thread...
11/08/2013 13:42:05.947 Aborting nDroidServiceStreamer thread...

11/08/2013 13:42:07.301 serviceHelper.GetConnStrings() returned : True
11/08/2013 13:42:07.302 nDroidService v2.0.2 build: 2.0.4938.31086 started.
11/08/2013 13:42:07.303 Creating new nDroidServiceListener object...
11/08/2013 13:42:07.303 Creating new nDroidServiceStreamer object...
11/08/2013 13:42:07.304 Creating new nDroidServiceListener thread...
11/08/2013 13:42:07.304 Creating new nDroidServiceStreamer thread...
11/08/2013 13:42:07.306 Starting nDroidServiceListener thread...
11/08/2013 13:42:07.306 Starting nDroidServiceStreamer thread...
11/08/2013 13:42:07.306 OnStart() - Creating FileGenerator object...
11/08/2013 13:42:07.306 OnStart() - Creating FileGenerator thread...
11/08/2013 13:42:07.307 OnStart() - Starting FileGenerator thread...

[bgowland]

Unfortunately, my Optimus phone is using Jelly Bean. I had successfully managed to get nDroid to work in the past but not sure if this was before the upgrade to Jelly Bean.

In which case getting at the real-time logs on the phone isn't going to be possible. I actually agree with what they did in JB as it improves security and privacy but I didn't know they were going to do it. I'll try and add something to nDroid for a future release to allow it to read its own logs and send them to me for debugging purposes.

EDIT : Not sure where the attachment is??? I clicked Go Advanced to add an attachment. Am I doing it correctly? Since the log isn't big, I will just copy and paste it here as I can't see how to add attachment here:

That is only the nDroidService.log which doesn't llog connection attempts and activity. I really need nDroidServiceListener.log and nDroidServiceHelper.log. Ideally zip all the files in the\logs folder.

When you reply on the forums, "Go Advanced" then scroll to Additional Options, click on Manage Attachments then at top left Choose File. This gives a standard WIndows file chooser. WHen you've selected the file click Upload in the Manage Attachments window then Close Window.

[MP3746]

Hi Brian,

I have uploaded the logs directory in a zip file. As far as I can see, nothing is being logged by the server, so the client isn't sending anything to the server. This could be a Jelly Bean issue.

[bgowland]

Hi Brian,

I have uploaded the logs directory in a zip file. As far as I can see, nothing is being logged by the server, so the client isn't sending anything to the server.

Yeah, definitely no indication of connection attempts. Clutching at straws...have you tried restarting the nDroid Service or a reboot of the computer? It's possible the nDroid Service has hung (but fairly rare in my experience). If that doesn't fix it then it's definitely client-side.

This could be a Jelly Bean issue.

No, my Google Play statistics show just over 60% of installations of nDroid v1.x are on devices running JB v4.1 or higher. But then again it seems odd that it might be specific to the LG Optimus 4x in general. I have seen Android devs post code problems on Q&A sites saying that certain devices don't work with their apps though - perhaps this is one of those cases.

I'll do some digging.

Cheers,
Brian

[MP3746]

I am trying to connect using nDroid TE and I see the log file sizes and dates not changing. The server machine has been rebooted and the service is running fine. I have also rebooted my Optimus phone. As I mentioned earlier, there are no problems using a Galaxy Note 2. So this suggests firewall, port forwarding, ndroid Services, etc are all set up correctly.

Thank you for your help. I am a software developer myself, by the way, but unfortunately, I don't know Android software development to be able to track this problem down. I am going to try nDroid on the BlueStacks Android emulator and see if the problem is there.

EDIT: Oh by the way, in nDroid TE after failure to connect, I receive the message CONN_CONNECT_FAIL_UNKNOWN

[bgowland]

I can only find one LGE Optimus 4 in the full nDroid v1.x statistics file but what is odd is there aren't any for nDroid TE. Was the update to JB an official one or have you installed a custom ROM?