I've got a working ncidd with a few clients. However, the Android
client on my Sony Bravia Android TV is crashing my server by exhausting
available connections. The TV is a 2020 A8H model with up to date
firmware and Android OS.
So before I report a bug, I figured I'd throw the issue out there for
comment. I suspect what is happening is that the TV is putting the app
to sleep and then it tries to open a new connection when it wakes up.
I'm open to settings suggestions or anything else I ought to check.
Why do I want to run the Android client on my TV? Well the pop-up with
caller id and the voice announcement is a nice feature and well suited
for a TV screen while streaming or watching content.
Thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The ncidd server coming in the 1.12 version of NCID has a fix so it won't crash on too many client connections.
The current NCIDandroid 0.2.0.7 wasn't supposed to do this any more, but I wasn't able to reliably duplicate it while trying to fix it.
I'm going to release 0.2.0.8 this week, so let me know if it is still happening when you get it, and also tell me what it sends when it connects.
-- with verbose level 2, ncidd will log client HELLO messages in /var/log/ncidd.log
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
A preliminary observation is that when I select settings, it instead returns to the Android home screen.
Also noticed is that on internal calls, say from a 3 digit extension, the caller name is displayed but the number shows as a $AREA-$NPA-$NXX-literal string. The prior version correctly displayed the callinge extension, say 100.
We'll see if it crashes the server after it has been up for a little bit, and I will report back. Thank you.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I wasn't seeing any problem on the TV version, so I uninstalled the one I had put on with adb and loaded the one from the Play store. With no previous settings it shows no calls, and as you say crashes out to the android TV home screen for trying to look at Settings. Hopefully the Play store will give me crash logs.
I am seeing your problem for formatting short numbers and having them appear as $AREA-$NPA-$NXX. This should have worked properly without installing NCID 1.12, I will fix this.
I'm not quite sure what you mean by "NANP compliant numbers". Ones that are 10 or 11 digits? -- so that if one lives in North America and the number is 10/11 it formats with hyphens, otherwise gets the Google format?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So yes, by NANP compliant numbers I mean 10 (or 11) digits in the form of NPA-NNX-XXXX.
What would be ideal (for me) is if the number matches that mask it gets displayed based upon the nanp_format config parameter, otherwise it gets displayed as if option 0 is in effect.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ouch. I tried uninstalling and reinstalling on my tablet from the Play store and it has a similar problem with crashing out of the Settings, which is bad for a new install.
Anyway, the Play store version appears to be largely broken.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The Settings crash seems to come from the package build that tries to make the package smaller.
The bad formatting of short numbers came while adding support for $ALL
I'll put an 0.2.0.9 version out soon ...
Last edit: Ed Attfield 2021-08-21
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I will need to see the ncidd log at a high "verbose" level.
Send me what you have now, and then set verbose=7 in ncidd.conf, restart it and wait.
I'd like to see the first few lines from "Started:" to "Begin: Loading..." for the run that crashed, and I'd like to see a lot of the end as it gets in trouble and crashes.
Please remove personal information like phone numbers and names.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
SourceForge no longer allows us to use ncidsupport@users.sf.net or ncidsupport@users.sourceforge.net for forwarding attachments to NCID Developers. See today's updated post New email address for sending attachments to NCID support team for temporary work arounds.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It appears that the Sony Bravia TV is putting the NCIDandroid app to sleep in a way that does not close the connection to the server, much like putting the device into airplane mode.
The app's Keep Alive timer will make a new connection roughly every five minutes, eventually using up all of the allowed client connections in ncidd.
When the connection table is full, ncidd uses -1 as an array index, and may crash.
a) On some devices, Keep Alive should be set to 0 minutes to turn it off
b) There is a fix for ncidd that will be needed in some architectures, coming in 1.13
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Some followup...I was looking at my DHCP server and see that the Sony Bravia is constantly renewing its DHCP while turned off. That tells me that there is some power saving method which is putting the network to sleep and doing a DHCP req on resume (even while off), which it seems to do rather frequently (minutes rather than hours). That could explain a bit more about why it keeps opening new connections to the server.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've got a working ncidd with a few clients. However, the Android
client on my Sony Bravia Android TV is crashing my server by exhausting
available connections. The TV is a 2020 A8H model with up to date
firmware and Android OS.
So before I report a bug, I figured I'd throw the issue out there for
comment. I suspect what is happening is that the TV is putting the app
to sleep and then it tries to open a new connection when it wakes up.
I'm open to settings suggestions or anything else I ought to check.
Why do I want to run the Android client on my TV? Well the pop-up with
caller id and the voice announcement is a nice feature and well suited
for a TV screen while streaming or watching content.
Thanks.
The ncidd server coming in the 1.12 version of NCID has a fix so it won't crash on too many client connections.
The current NCIDandroid 0.2.0.7 wasn't supposed to do this any more, but I wasn't able to reliably duplicate it while trying to fix it.
I'm going to release 0.2.0.8 this week, so let me know if it is still happening when you get it, and also tell me what it sends when it connects.
-- with verbose level 2, ncidd will log client HELLO messages in /var/log/ncidd.log
Thanks for the quick response. I'll look for the updates and report back in this thread.
NCIDandroid 0.2.0.8 is in the Play store now,. I hope it helps.
NCID 1.12 is available on Sourceforge ff you want to be among the first to try it.
A preliminary observation is that when I select settings, it instead returns to the Android home screen.
Also noticed is that on internal calls, say from a 3 digit extension, the caller name is displayed but the number shows as a $AREA-$NPA-$NXX-literal string. The prior version correctly displayed the callinge extension, say 100.
We'll see if it crashes the server after it has been up for a little bit, and I will report back. Thank you.
I also installed ncidd 1.12. I now undertand the change made to number formatting and why my local extensions were not properly displaying.
Changing the nanp_format to 0 fixes that for the Android client, but then I don't get the nice formatting on NANP compliant numbers.
So...if I may make a suggestion, can we have another option for the NANP display formatting? Something like:
set nanp_format = 4 # All-hyphen format for compliant numbers, otherwise don't format
Or this could just be added to format 2.
Thanks for your work on the project. It is exceptionally helpful to me.
I wasn't seeing any problem on the TV version, so I uninstalled the one I had put on with adb and loaded the one from the Play store. With no previous settings it shows no calls, and as you say crashes out to the android TV home screen for trying to look at Settings. Hopefully the Play store will give me crash logs.
I am seeing your problem for formatting short numbers and having them appear as $AREA-$NPA-$NXX. This should have worked properly without installing NCID 1.12, I will fix this.
I'm not quite sure what you mean by "NANP compliant numbers". Ones that are 10 or 11 digits? -- so that if one lives in North America and the number is 10/11 it formats with hyphens, otherwise gets the Google format?
So yes, by NANP compliant numbers I mean 10 (or 11) digits in the form of NPA-NNX-XXXX.
What would be ideal (for me) is if the number matches that mask it gets displayed based upon the nanp_format config parameter, otherwise it gets displayed as if option 0 is in effect.
Ouch. I tried uninstalling and reinstalling on my tablet from the Play store and it has a similar problem with crashing out of the Settings, which is bad for a new install.
Anyway, the Play store version appears to be largely broken.
The Settings crash seems to come from the package build that tries to make the package smaller.
The bad formatting of short numbers came while adding support for $ALL
I'll put an 0.2.0.9 version out soon ...
Last edit: Ed Attfield 2021-08-21
Also, ncidd 1.12 is still crashing if I use the Android client. Is there any data I can provide for troubleshooting?
I will need to see the ncidd log at a high "verbose" level.
Send me what you have now, and then set verbose=7 in ncidd.conf, restart it and wait.
I'd like to see the first few lines from "Started:" to "Begin: Loading..." for the run that crashed, and I'd like to see a lot of the end as it gets in trouble and crashes.
Please remove personal information like phone numbers and names.
Log sent.
Hi All,
SourceForge no longer allows us to use ncidsupport@users.sf.net or ncidsupport@users.sourceforge.net for forwarding attachments to NCID Developers. See today's updated post New email address for sending attachments to NCID support team for temporary work arounds.
It appears that the Sony Bravia TV is putting the NCIDandroid app to sleep in a way that does not close the connection to the server, much like putting the device into airplane mode.
The app's Keep Alive timer will make a new connection roughly every five minutes, eventually using up all of the allowed client connections in ncidd.
When the connection table is full, ncidd uses -1 as an array index, and may crash.
a) On some devices, Keep Alive should be set to 0 minutes to turn it off
b) There is a fix for ncidd that will be needed in some architectures, coming in 1.13
Some followup...I was looking at my DHCP server and see that the Sony Bravia is constantly renewing its DHCP while turned off. That tells me that there is some power saving method which is putting the network to sleep and doing a DHCP req on resume (even while off), which it seems to do rather frequently (minutes rather than hours). That could explain a bit more about why it keeps opening new connections to the server.