Notices

Thnx for th latest update, and the status update option man... Kip up the gr8 work u r doing..

Scorpius, thanks for the update.

Can you explain the problem more detailed please. Was it because of the switching from portrait to landscape mode and vise versa?

Greetings

It's kinda hard to explain but it has to do something with available resources. If the Yappari window was open, no matter what you did, it'd never close (but I guess you never tried that out).

When you closed it and left it in background, when the phone needed more resources than it had available, like when you need to switch the whole desktop from landscape to portrait, or when you received a phone call, the phone assumed you weren't using Yappari anymore and just quit it. That's why it only happened sometimes, and not always. Sometimes the phone didn't need that kind of "garbage collection" because it already had enough resources available.

So I just needed to tell the OS that even if it needed more resources it couldn't quit Yappari unless the user wanted to.

Phones are different so when you quit an application resources are not immediately freed, because that's inefficient in a phone. They are just marked "useless". When you closed the main Yappari window, the phone was marking it as not needed anymore. I wasn't "pinning" the application properly.

<rant at other devs not related to you or your question>
Phones are not PCs and if you're a developer you really need to know that programming for a phone is not the same than programming for a PC and everybody just forgets that. I don't understand why people is using python or any interpreted language on a phone, when resources are so limited. Usually a perfect code for a PC works totally wrong in a phone, and sometimes you have to even break some "conventions" and "good practices" of coding for PCs on a phone to save resources.

There's even a whole movement out there to compile CSSU in Thumb-2 instead of standard ARM instruction set (ARM processors have 2 instructions sets: ARM and Thumb-2) that saves something like 22 MB of RAM. 22 MB in a phone is like $1 million dollars in your pocket. YES, it's THAT important.

BTW Yappari is 100% native code.
</rant>

It sounds quite easy, if you know the background. I guess programming for a phone like galaxy s3 isn't that restricted because of the better hardware especially 1GB RAM - our N900 really suffers from less memory.

Yeah but android is crazy when it comes to background/pause proccesses

Sorry for hijack, please forgive me.

So far 0.0.16 is working fine, no more whatsapp upgrade messages (to compensate my offtopic)

Thanks Scorpius!

I've send Scorpius a PM about 'Invalid list size in readListSize: token xx' with a logfile, so if other people have the same problem, I think he is/goes working on it.

Very nice release! (the first one I can use, thanks for integrating the new addressbook query method!).

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.

Because all of these reasons, it would be nice if in the future these feature is configurable by the user (enabling the keepalive and setting the parameters to adjust to each different type of crappy connection)

There are more TCP options in Linux to impreove latency which can be added in the future (by default linux tends to be more bandwidth-oriented than latency-oriented).

Anyway, thanks again for the new release!

It would be also be nice to have a copy and paste function, for situations like if, for instance, someone sends you a phone number.

Another improve, to see the contact info who is chating you.
I have received some chats from numbers I don't have in my adress book.
Thanks to Scorpius for this new release.

Would like to request a way of seeing what messages are being kept by Yappari. For example, the server message to update "whatsapp" which we got before. I am sure it is still cached by yappari, but we can't access it since it's not part of our contacts and we upgraded to newer version. How do we clear those message?

Hope you understand my request...