I'm trying to implement In-App Billing. I'm signed into a test account
registered with the Market, and I've updated my public key in the
code. I can purchase one of the test product IDs.
However, it appears that a blank signature is sent in the
PURCHASE_STATE_CHANGED intent. The log appears as
More debugging on this issue...
I am using this method to generate keys from a passphrase:
KeyGenerator kgen = KeyGenerator.getInstance(AES, BC);
SecureRandom sr = SecureRandom.getInstance(SHA1PRNG,
Crypto);
sr.setSeed(seed);
In Gingerbread, I'm decoding some previously-encoded data with the
following:
SecretKeySpec skeySpec = new SecretKeySpec(raw, AES);
Cipher cipher = Cipher.getInstance(AES);
cipher.init(Cipher.DECRYPT_MODE, skeySpec);
byte[] decrypted = cipher.doFinal(encrypted);
I now get this
Dan, not sure since it's customer reported. We do know the model is
SPH-M900 and running 2.1-update1.
On Sep 6, 4:59 pm, dan raaka danra...@gmail.com wrote:
what is the build fingerprint on your device ?
$ adb shell getprop | grep finger
-Dan
--
You received this message because you are
More information.. here is the logcat when the issue occurs. We first
try 16000 Hz, and then 8000.
D/App ( 2618): Main activity starting
I/AudioPolicyManager( 1889): getInput() inputSource 1, samplingRate
16000, format 1, channels 10, acoustics 0
W/AudioHardwareALSA( 1889): openInputStream :
We have been getting reports of audio recording not working on Samsung
Moment phones on 2.1-update1.
int bufferSize = AudioRecord.getMinBufferSize(sampleRate,
AudioFormat.CHANNEL_IN_MONO,
AudioFormat.ENCODING_PCM_16BIT);
this.audioRecord = new
We have an app that plays and records audio using AudioRecord and
AudioTrack, and also uses the 2.2 requestAudioFocus() API for audio
ducking.
We also use the AudioManager.getStreamVolume() call to determine if
the user has their volume control all the way down (as sometimes
happens) and to issue
We have an app which requests and abandons audio focus several times
over the course of its lifetime. When the process exits, these
messages appear several (30+) times in the log:
W/AudioService( 1086): AudioFocus audio focus client died
W/AudioService( 1086): AudioFocus audio focus
Our app has a problem with AudioRecord where the recorded audio is
very slw (sound like it's 2x slower). We use
AudioRecord.getMinBufferSize to try 16000 Hz first and then back down
to 8000 Hz if that function returns an error. So my guess is that the
audio is reported as 8000 Hz even though
Our app has a problem with AudioRecord where the recorded audio is
very slw (sound like it's 2x slower). We use
AudioRecord.getMinBufferSize to try 16000 Hz first and then back down
to 8000 Hz if that function returns an error. So my guess is that the
audio is reported as 8000 Hz even though
The device in question is running 1.5, FWIW - therefore it would get
AudioFormat.CHANNEL_CONFIGURATION_MONO.
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To
I've got unit tests which are subclasses of AndroidTestCase, I thought
they were just taking awhile to run, but for some reason when I run
them via Eclipse, they actually run twice. I can verify this in
LogCat .. after the Console outputs Launching instrumentation
12 matches
Mail list logo
