MediaRecorder buffering

by RFuente » Thu, 21 Oct 2010 19:22:34 GMT

Sponsored Links
 Hi everyone!

I've been working with MediaRecorder for a while and still keep up
discovering funny things about this class. I have two instances: one
of them records video and the other one records audio (why I don't
implement this with just one instance will be long to explain xD).

At the same time I am sending stored data via UDP to a remote machine
(running Java). The thing is that audio data is being received in
bursts and I've managed to find this is due to the way MediaRecorder
stores data. Do you know if it always behaves in the same way? At the
moment, data is being stored into the SD card, has any of you tried
writing into internal storage or maybe directly into a socket file

I know mine is not the best approach but it's still under development
(Android 1.6).

If anyone could give a hand it would be very much appreciated. Thanks.


Other Threads

1. neighbor cell information yields odd results with 3G

I have an app that collects neighbor cell information (CID and RSSI).
It works fine in 2G.  When switching to 3G, the getCid() and getRssi()
throw a NumberFormatException

List<NeighboringCellInfo>  neighCell = null;
neighCell = telManager.getNeighboringCellInfo();
for (i = 0; i < numNeigh; i++) {
        try {
                NeighboringCellInfo thisCell = neighCell.get(i);
                int thisNeighCID = thisCell.getCid();
                int thisNeighRSSI = thisCell.getRssi();

        } catch (NumberFormatException e) {
                NeighboringCellInfo thisCell = neighCell.get(i);
                cellIdOutput = String.format("%s", neighCell.toString

Using toString() (as above in last line of the catch) generates the
following string...

[[6c at 0], [74 at 0]]

This NeighboringCellInfo list identifies it's size as 2, which looks
right from the string output.

Does this string contain 3G cell ID such as scrambling code (in hex)?
Anyone know how to decode it?

Thanks in advance for the help.


2. Verizon attacks iPhone with ne w 鈥楧roid鈥?campaign

It's about fricken time.  T-Mobile, if you are reading, WTF?  You
should have done this a year ago instead of leave it up to your

Now let's hope app sales go up or at least increase a bit.


3. TabHost crash (was: hardcoded borders)

4. Android 1.6 deployement status

5. Android Music Player noy indexing mp3 files

6. ADC2 entries so far...

7. Basic game structuring with two threads?