kiu (author of CallLocation)

I won’t state that these Apps are buggy ..or defect, it just seems to be a fact that if there are too many apps acting in background and there action take place around the same event “incoming call” problems may raise quickly.

So the solution should be simply to deceide which apps need to be present. You can check how many apps are running at the same time with a little help of an app named “Taskiller” for example. It’s free for download in the market and will show you in a cute list which apps are running and grab memory and CPU time.

Beside this, the new NoStalk Version 1.2, compiled against the latest SDK Version (SDK 1.5_r3) is in the Market up from now. Update your NoStalk and enjoy the silence

Feel free to ask questions here. It’s not a good Idea to do this within the market comment function.

There seem to be two main issues out there in the field.
a) All calls claim to be unknown
b) It worked for a while and now there is no more call-blocking (Phone rings)

First of all i would like to point out that i wrote this app with the original SDK version 1.5_r2. The app is compiled against this SDK and and has been tested on Emulator and on a real world G1. Testing on “Real World G1″ comes in place again with every new release of the Android OS, published by Google OTA. I’m using a non rooted G1 and no other Software which do handle calls or handling contacts.

Right now i’m using the original firmware 1.5, kernel Version 2.6.27-00393-g6607076, CRC37.

I could not redraw any of the issues described in the comments on the market when testing on my phone.

Some information on the two main issues mentioned above. I do not touch the incoming number in any way except reading it and checking if the respective field is emtpy or not. If emtpy the phone switches to silent mode else not. After this, everything else belonging to this call will be handled by the phone itself respectivly another piece of software. (which may in some cases also come in place before my software catches the incomming call)
If the Phone state changes after call has not been taken, the app changes Ring Mode back to normal.
I did not touch contacts or another ringing behavior on the phone. You can see this on the regarding missing permissions.

So under normal circumstance there is no way that this app will change all callers to unknown. (Definition of unknown here is, that there is no caller ID with this call, so there is no Caller Number displayed)

Now there are two things which could begin to make troubles.
First of all, if you have many apps running on your phone or you have’nt restartet your phone for a long time, there may be a large amount of memory consumption by other apps. This could slow down the phone processor and may cause troubles detecting unkown caller ID, which is in fact a very timecritical process.
So please check if there are other apps running in background which maybe could cause this behavior.

Secondly it may be possible that you are running a rooted phone with a modified part of the android OS. This could seriously cause troubles detecting the caller ID or other things. Everything is possible and could not be checked by me.

So if you experience troubles, everyone has the ability to write his comments here with some information regarding Firmware release, CRC and Kernal Release and a description what kind of problem is ongoing. If possible for me i will check if there are known issues in the regarding area of OS-Source.

In the next few days i will publish a new release which will be compiled against the latest SDK 1.5_r3. Your GSM will tell you about it

One more word about uninstalling .. there are no hooks in the application which will disallow uninstalling it. That must be an issue with other software or ROM things.
The software isn’t even copyprotected.