Notices

Originally Posted by Scorpius

I could try FCam API. I'll read the documentation to see if it's feasible.

In the mean time I need you all guys to vote for 1.1.40. Even if it still has that little bug of [voice note] instead of [image] when you send one (and should happen with video and audio too), let's vote so 1.1.40 can reach extras and people that are struggling to register can register easily and enjoy Yappari.

Vote here

Originally Posted by mrbee

The new version of Yappari came and it was nice, but when I restart my phone yappari seized to work. I have clicked on Yappari Icon severally without response. Please I need help

Originally Posted by Scorpius

And where is the log?

Try first: rm -v /home/user/.yappari/chats.db

If it doesn't work then I need to see the log.

Originally Posted by mrbee

i typed in the string in xterm and this is what I got:



BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso31+0cssu0) built-in shell (ash)
Enter 'help' for a list of built-in commands.

~ $ rm -v /home/user/.yappari/chats.db
rm: invalid option -- v
BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso31+0cssu0) multi-call binary

Usage: rm [OPTION]... FILE...

~ $
Yappari does not start at all so where can I get the log please?

Originally Posted by Scorpius

You didn't read the first post entirely. You always have to read the first post entirely on every thread you're gonna post a comment.

Anyway that's weird, but try:

rm /home/user/.yappari/chats.db

Without the -v option (I thought BusyBox supported but Maemo SUCKS SO MUCH that it doesn't really surprise me)

Originally Posted by NerdKnight

Several times I found Yappari eating the CPU, this happens when my n900 connects to a wifi router I have in bridge mode, that sometimes looses it's connection. In the log file I found the following lines repeating many times:

Code:

Connecting to c.whatsapp.net:443...
There was an IO error: Can't resolve server address (DNS problem?).
Connection closed.
Stopping timers.
Freeing up the connection.
Freeing up the socket.
Yappari will retry the connection in 10 seconds.

Originally Posted by Scorpius

Normal. If Yappari detects a connection it will try to connect, but if your connection doesn't really work it'll retry forever eating your CPU. You should address your router problem, which may not support the N900 power saving mode, disconnecting it (this is a common problem, try leaving the N900 without the power saving setting to see if it loses the connection, if it doesn't then it's time to buy another router).

Originally Posted by NerdKnight

Yeah It's an old router, this happens sometimes not regularly, but I think that yappari could use a bit less processor in this case, I notice this problem when the battery gets suddenly drained. Thanks for the quick reply, if I get more info about this I'll post it.