I have tested some other Qt applications and they seem to have the same problem as yappari regarding the arabic letters, so i guess it is Maemo Qt related. So ..
Just out of curiosity because I don't have problems with 2/2.5G and have a flatrate data plan, did you customize TCP_KEEPIDLE, TCP_KEEPCNT and TCP_KEEPINTVL? If yes, I'm curious about which values are you using, if not you probably should if you want to detect a disconnection before waiting more than 2 hours. Also you probably want to change the CNT to something like 3 or 5 and INTVL to 1 second to detect the disconnection in 3/5 seconds instead of the default 11 minutes (CNT=9 AND INTVL=75, maybe on crappy connections it would be good to keep the high CNT to avoid "false" disconnections). Also keep in mind that TCP keeps alive will send very small packets regularly (each TCP_KEEPINTVL seconds) and this, even when small, will probably consume bytes from your data plan.
I don't have that level of control using a QTcpSocket.
add an option to run on startup but delayed like after 2 minutes of boot.
Is their a way to lower the CPU and RAM consumption of Yappari Like having a process for background (just to capture messages) and another for the GUI. N900 is an aging device we should try to save every 1mb!
You should measure CPU and memory utilization of Yappari and you'd realize CPU consumption is always at 0% (since Yappari is event based, if nothing's happening, then nothing's done) and memory consumption is even lower than modest, Calendar and other programs you have running 24/7 in your N900.
I have tested some other Qt applications and they seem to have the same problem as yappari regarding the arabic letters, so i guess it is Maemo Qt related. So ..
What is wrong with arabic while using yappari ? I don't have any problem with typing Arabic in yappari using virtual keyboard
first of all thanks a lot for your time with this great app. IŽd like to ask if you could upload to other server as the 0.0.16 link is dead. Thanks for help.
@Scorpius
it works well thanks for the status thing
but sometimes it keeps telling DNS error i think (on the wireless only) 3g works well
here is my log