All about Meridian's data collection

Since version 0.7.1 of Meridian Noble, free version of Meridian starts to collect anonymous user data for developing.
The mechanism  is using Flurry and Google Analytics, which will collect data for:

• Meridian Errors. This is most important, as with this we can get information for debugging without requesting users to install Log Collections or so on.
• The actions of Meridian, like one video play, browsing using which tab, headset button pressed, etc. This is used for counting what mechanism is more used, so we'll do more effort on those features.
  
• Your device model, carrier, and firmware version. This is used for device-dependant features priority, for example, if there's still a lot of people using Android 1.5 devices, Meridian will keep supporting 1.5, instead of going to a minimum 1.6 release.

And Meridian will NOT collect the informations like:

• Meridian does NOT collect what's in your phone or SD card. We will be reported you played a music or video, from artist or album, but we don't know what it actually is.
• Meridian does NOT collect anything related to your Google account, like your account name, mail, calendar, everything.
  
• Meridian does NOT collect your location information, other than which country you live (using IP information). At the very first 0.7.0 it did, but now removed.
  
• Meridian does NOT collect your call information. It only knows the phone is hooked or not.
• Meridian does NOT collect your phone number, messages, or contacts.
  

This data collection can be disabled in Pro version. For Pro version info please check here.

Auto Starting Bug

This is a confirmed major bug, but I still can't find the reason.
I have gotten several different reports of auto starting (Disconnecting headset, disconnecting bluetooth, end of a call, etc.), but all of them do not appear when I do it in my office :(
In fact myself sometimes meet the auto-start, but I have totally no idea since I'm not taking log yet. Hope the logged version now will produce more hint.
...First of all, I can only wait it occurs. Grrr.

Why some BlueTooth headset butons does not work in Meridian ** Modified **

09/12/17

I'm responded from HTC that this is because some devices, like HTC Magic or Hero in Android 1.6 or older, uses HTC's own bluetooth driver.
As a result, it's not intercepting signals, but it just can't be used by thrid-party apps.
This will be fixed after Android 2.0 (As we know Android fully supports bluetooth from 2.0), so let's wait.

Guys, I know you really want an Equalizer

But an equalizer can't be done in the Java layer and Android does not support that feature yet.
So until Android does it, I can't do anything for it.

0.1.4 release

I'm now going to do another work so I only shortly say it's a fixing update.
Oh ya, you can buy pre-release Pro version here: http://sites.google.com/site/eternalsandbox/update-to-professional-version

About 0.1.0

Okay I never know Device ID is a HEX sequence rather than DEC one.
I'll fix it tomorrow, Meridian will keep unpublished for about half a day.

About the Pro version

I'm working on it, but as I'm not a U.S. nor U.K. citizen, I can't sell it on Market.
By now the plan is to sell on SlideME and AndAppStore, they offers Paypal payment.
Also, I'm not going to move many current features to Pro version only, but it also means Pro version won't have many extra features by now.
It does not make sense, maybe I'll think more about the Pro version's value.