Monthly Archives: May 2011

Crash Reporting

It is too bad that DaTuner needs to request full internet access for crash reporting, but it does. I have seen a few complaints already about this, but here is my point of view.

If there were a better way (via the Android Market API, which has internet access, for instance) I would do it.

Here, though, is my reasoning as to why I feel I need to have network based crash reporting.
– Out of 110 000 downloads (and counting), only about 15 people have emailed me to report a crash and the circumstances surrounding it.
– It has been > one week on several occasions before I have received feedback on my bug fix for the reported bug from the person. I am very thankful that the person contacted me to begin with, but this just isn’t working.

Further Justifications.
1.) I don’t want DaTuner’s only advantage to be that it doesn’t request Internet access. Sure, it also doesn’t include ads but if it’s another tuner vs. DaTuner I want DaTuner to win based on its ease of use, precision, and responsiveness and not simply on the permissions it doesn’t request. If that was the case I would have just spent a few hours writing a simple FFT based tuner and published it without permissions and never updated it afterwards.

2.) I make no money on the free app, and nobody else does either. Let’s just assume, hypothetically, that DaTuner suddenly becomes really popular because of how accurate it is (I can always hope!) but if that just translates to more downloads of a free app and fewer downloads of every other paid tuner app on the market, who wins? I would rather that those downloads go to other paid apps or ad-supported apps since at least a developer somewhere will make money from them, especially if those other apps are better or more feature rich (many are more feature rich – at least so far.) Who’s thinking about the poor hardware tuner guys we’re stealing the business from? They need to survive too!

So, to users of DaTuner; I apologize for asking for full internet access, but this seems to be the only way for me to get nearly immediate feedback on whether or not new features I will be releasing have also unintentionally included new bugs. You have my word that the network access will ONLY be used to report crashes (unless I release another ad-supported app down the road but that would be another app.)

If you really don’t want any apps on the phone to have network access, I recommend you download a power control app so you can turn off data access for all apps with the click of a button. DaTuner will work great even with network access off, since it will only ever try to use it if it crashes. Crashes are not an intentional feature of DaTuner.

One Star

5 star ratings are fleeting. They turn to 1 star as soon as a release is made with a bug in it.

1 star ratings are permanent. They seem to never turn back into 5 stars when the bug is fixed.

Why is that?

DaTuner and DaTuner Donate are back up!

I have now streamlined communications between the audio input thread and the analysis thread, which resulted in better responsiveness, at least on my X10 Mini Pro.

I am currently limiting CPU usage in the analysis thread. Perhaps in the donate version I will provide an override so that 100% CPU can be used for analysis, since analysis only runs when the signal level is over a certain threshold, anyway.

Please try the latest updates and PLEASE email me if they don’t work.

DaTuner down for maintenance

I think I have recently released a version of DaTuner that doesn’t work as it should, as I have been getting a higher ratio of low ratings than usual, so both the donate and free versions have been unpublished until I resolve the issue.

Update: DaTuner is back up, both donate and free versions!