MediaRecorder - No value other than 0 returned from getMaxAmplitude

by Dave Sparks » Sun, 01 Feb 2009 03:04:00 GMT


Sponsored Links
 Are you running on a G1 or on the emulator? If on the emulator, maybe
audio input isn't working correctly and it's failing to open the audio
input device.



--~--~---------~--~----~------------~-------~--~----~



MediaRecorder - No value other than 0 returned from getMaxAmplitude

by nicolas cosson » Sun, 01 Feb 2009 08:09:46 GMT


 are you testing it on the emulator or on the G1 device?

I'm not sure about it but I've read around some forums that you need a
virtual sd card to record audio on the emulator. (with the
mksdcard.exe in the tools provided with the sdk)
Some other sources also say it isn't possible to record audio on the
emulator yet.

Check if you can read/hear what you have recorded since you are using
a sdcard, maybe the sdcard is too small.

Why would you use a thread to return the max amplitude?

I am myself looking forward to record audio on the emulator and
constantly find contradictory informations about whether it's possible
or not.
the manual says it's not.

Any insight about that is appreciated in addition to the upper
problem.

thanks



On 31 jan, 15:12, "ph...@grantmidwinter.com"



--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


MediaRecorder - No value other than 0 returned from getMaxAmplitude

by Dave Sparks » Sun, 01 Feb 2009 12:18:21 GMT


 You shouldn't have to reboot the device. The release() call just
forces the release of the hardware resources instead of waiting for
the garbage collector to come along.

You should always call release() in your onPause() if you are using a
singleton hardware resource like a media player, media recorder,
camera, etc.




--~--~---------~--~----~------------~-------~--~----~



Other Threads

1. Android 2.0 vs 1.6 not running

I Have an app that is running fine in 1.6,

I have now updated my sdk to 2.0 and the app never starts properly

I was wondering if anyone had an idea of what would stop an app
running on the newer version that runs fine usually.


Once it is started, it runs threads correctly, but nothing gets
displayed then i get the error

WARN/ActivityManager(69): Activity idle timeout for HistoryRecord
{43b57a38 com.vlm.DojoSquabble/.Mid}

I have another application that is very similar that works correctly.
Its manifest defines its Activity class
as android:name=".Mid" , whereas the app that is failing has it as
android:name="Mid" . Does not seem to make a difference when i change
it but it is the only thing i can see that is different

Any help would be appreciated but if I figure it out ill post my
findings here anyway.

-- 

2. Can one Activity open another activities' options menu?

Just a simple question.  Can Activity "A" open the options menu of a
view in Activity "B"?

In this case I am building Activity A but Activity B can be any other
running activity.  I think this is an impossible security violation
but I really want someone to prove me wrong.

-- 

3. motorola cliq sdk 2.0

4. protocol buffer implementations

5. How to remove sms notifications in status bar

6. Android Market: Convert an app from Free to PAID

7. How to use startActivityForResult() & onActivityResult() ??