Re: [android-developers] ICS/Galaxy Nexus Can't Loop Audio without GAP

2011-12-23 Thread YuviDroid
I just did a quick test with your apk and:

Galaxy Nexus - Android 4.0.1 - Kernel 3.0.1-ga052f63 - FAIL
Galaxy S 2 - Android 2.3.4 - Kernel 2.6.35.11-ninphetamine-2.1.3 - PASS
(pls note that this is a custom ROM, I couldn't test right now with a stock
ROM)

Tomorrow I will test on a Nexus S, Xoom, and Archos G9.

Cheers,
Yuvi
http://www.droidahead.com

On Fri, Dec 23, 2011 at 1:39 AM, csyperski csyper...@gmail.com wrote:

 ICS can't loop audio seamlessly with more than one core, when using
 MediaPlayer-setLooping(true).  This is a major bug that is causing
 problems for my applications.  I have a sample project below
 demonstrating the issue.

 I have included a link to a very simple eclipse project that you can
 use to test for the setLooping bug.  This bug doesn’t seamlessly loop
 an audio file.  It plays a simple sine wave that can be used to easily
 detect if your device is displaying the bug.  I have also provided the
 direct like to the apk file as well.

 I feel this bug is an important bug to get fixed.  Although this is a
 simple example, it has real world problems including:

 *Looped music playback
 *Sound machine type applications
 *Game sample loops


 I feel this bug hurts the Android platform and encourages the
 ‘fragmentation’ fault argument.  Some devices/firmware don’t present
 the bug while others do.  For example, almost every recent Motorola
 device has the bug, but most HTC devices don’t.  The Xoom shipped
 without the bug, but a firmware update introduced the bug (I don’t
 know which version introduced it).

 I have an application, SleepyTime, which used to be available on all
 devices but now isn’t available on many devices on the Android Market
 because the bug is present on those devices.  This creates a bad user
 experience for the user because:

 *A user on phone A can get the app, but a user on phone B may not be
 able to.
 *A user with phone X paid for the app, then upgrades to phone Z, which
 can’t get the app because this device has the bug, and now doesn’t
 understand why they can’t download the application they paid for.

 To anyone experiencing this bug, please run this application on any
 device you have access to and report the Android version, kernel,
 device name, and weather the bug is present.  We need to give the
 engineers as much information as possible if we want this to get
 resolved.  Please get as many people as possible to start this bug to
 give it more visibility.

 Eclipse Project:
 http://cwssoft.com/downloads/LoopBug.zip

 APK:
 http://cwssoft.com/downloads/LoopBug.apk



 Here are my test results:


 
 HTC G2
 Android Version:
 2.3.4

 Kernel:
 2.6.35.10-g96de068

 Status:
 Pass

 
 Motorla Xoom
 Android Version:
 3.2.1

 Kernel:
 2.6.36.3-g111d827

 Status:
 FAIL

 

 HTC Nexus One
 Android Version:
 2.3.6

 Kernel:
 2.6.35.7-59465-g42bad32

 Status:
 Pass

 

 Kindle Fire

 Android Version:
 N/A

 Kernel:
 N/A

 Status:
 Pass

 

 Logitech Revue

 Android Version:
 3.1

 Kernel:
 N/A

 Status:
 Fail!!!


 http://code.google.com/p/android/issues/detail?id=18756

 Chuck Syperski
 CWS Software LLC

 --
 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 unsubscribe from this group, send email to
 android-developers+unsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/android-developers?hl=en

-- 
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 unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] ICS/Galaxy Nexus Can't Loop Audio without GAP

2011-12-22 Thread csyperski
ICS can't loop audio seamlessly with more than one core, when using
MediaPlayer-setLooping(true).  This is a major bug that is causing
problems for my applications.  I have a sample project below
demonstrating the issue.

I have included a link to a very simple eclipse project that you can
use to test for the setLooping bug.  This bug doesn’t seamlessly loop
an audio file.  It plays a simple sine wave that can be used to easily
detect if your device is displaying the bug.  I have also provided the
direct like to the apk file as well.

I feel this bug is an important bug to get fixed.  Although this is a
simple example, it has real world problems including:

*Looped music playback
*Sound machine type applications
*Game sample loops


I feel this bug hurts the Android platform and encourages the
‘fragmentation’ fault argument.  Some devices/firmware don’t present
the bug while others do.  For example, almost every recent Motorola
device has the bug, but most HTC devices don’t.  The Xoom shipped
without the bug, but a firmware update introduced the bug (I don’t
know which version introduced it).

I have an application, SleepyTime, which used to be available on all
devices but now isn’t available on many devices on the Android Market
because the bug is present on those devices.  This creates a bad user
experience for the user because:

*A user on phone A can get the app, but a user on phone B may not be
able to.
*A user with phone X paid for the app, then upgrades to phone Z, which
can’t get the app because this device has the bug, and now doesn’t
understand why they can’t download the application they paid for.

To anyone experiencing this bug, please run this application on any
device you have access to and report the Android version, kernel,
device name, and weather the bug is present.  We need to give the
engineers as much information as possible if we want this to get
resolved.  Please get as many people as possible to start this bug to
give it more visibility.

Eclipse Project:
http://cwssoft.com/downloads/LoopBug.zip

APK:
http://cwssoft.com/downloads/LoopBug.apk



Here are my test results:



HTC G2
Android Version:
2.3.4

Kernel:
2.6.35.10-g96de068

Status:
Pass


Motorla Xoom
Android Version:
3.2.1

Kernel:
2.6.36.3-g111d827

Status:
FAIL



HTC Nexus One
Android Version:
2.3.6

Kernel:
2.6.35.7-59465-g42bad32

Status:
Pass



Kindle Fire

Android Version:
N/A

Kernel:
N/A

Status:
Pass



Logitech Revue

Android Version:
3.1

Kernel:
N/A

Status:
Fail!!!


http://code.google.com/p/android/issues/detail?id=18756

Chuck Syperski
CWS Software LLC

-- 
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 unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


Re: [android-developers] ICS/Galaxy Nexus Can't Loop Audio without GAP

2011-12-22 Thread Christopher Van Kirk
With respect, this is not the only example of fragmentation in the 
Android ecosystem.


On 12/23/2011 8:39 AM, csyperski wrote:

ICS can't loop audio seamlessly with more than one core, when using
MediaPlayer-setLooping(true).  This is a major bug that is causing
problems for my applications.  I have a sample project below
demonstrating the issue.

I have included a link to a very simple eclipse project that you can
use to test for the setLooping bug.  This bug doesn’t seamlessly loop
an audio file.  It plays a simple sine wave that can be used to easily
detect if your device is displaying the bug.  I have also provided the
direct like to the apk file as well.

I feel this bug is an important bug to get fixed.  Although this is a
simple example, it has real world problems including:

*Looped music playback
*Sound machine type applications
*Game sample loops


I feel this bug hurts the Android platform and encourages the
‘fragmentation’ fault argument.  Some devices/firmware don’t present
the bug while others do.  For example, almost every recent Motorola
device has the bug, but most HTC devices don’t.  The Xoom shipped
without the bug, but a firmware update introduced the bug (I don’t
know which version introduced it).

I have an application, SleepyTime, which used to be available on all
devices but now isn’t available on many devices on the Android Market
because the bug is present on those devices.  This creates a bad user
experience for the user because:

*A user on phone A can get the app, but a user on phone B may not be
able to.
*A user with phone X paid for the app, then upgrades to phone Z, which
can’t get the app because this device has the bug, and now doesn’t
understand why they can’t download the application they paid for.

To anyone experiencing this bug, please run this application on any
device you have access to and report the Android version, kernel,
device name, and weather the bug is present.  We need to give the
engineers as much information as possible if we want this to get
resolved.  Please get as many people as possible to start this bug to
give it more visibility.

Eclipse Project:
http://cwssoft.com/downloads/LoopBug.zip

APK:
http://cwssoft.com/downloads/LoopBug.apk



Here are my test results:



HTC G2
Android Version:
2.3.4

Kernel:
2.6.35.10-g96de068

Status:
Pass


Motorla Xoom
Android Version:
3.2.1

Kernel:
2.6.36.3-g111d827

Status:
FAIL



HTC Nexus One
Android Version:
2.3.6

Kernel:
2.6.35.7-59465-g42bad32

Status:
Pass



Kindle Fire

Android Version:
N/A

Kernel:
N/A

Status:
Pass



Logitech Revue

Android Version:
3.1

Kernel:
N/A

Status:
Fail!!!


http://code.google.com/p/android/issues/detail?id=18756

Chuck Syperski
CWS Software LLC



--
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 unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en