[android-developers] Re: Samsung-Specific Media Player Errors
I have been seeing similar things to this as well. I get this odd III constructor output, and 100 errors every time I play an mp3. Samsung Vibrant Galaxy S log. I have no idea why. I get these when audio plays, as well as when it fails: 11-19 14:09:41.950 W/MyMediaPlayer( 6226): prepareAsync called (1) 11-19 14:09:41.955 E/( 2207): III Inside Constructor of PVMFMemoryBufferWriteDataStreamImpl 11-19 14:09:41.960 I/MyMediaPlayer.fireUserActivity( 6226): calling userActivity to wake up prepareAsync() 11-19 14:09:41.990 E/MediaPlayer( 6226): message received msg=3, ext1=0, ext2=0 11-19 14:09:41.990 E/MediaPlayer( 6226): callback application 11-19 14:09:41.990 E/MediaPlayer( 6226): back from callback 11-19 14:09:41.990 I/PlayerDriver( 2207): buffering (1) 11-19 14:09:41.990 E/MediaPlayer( 6226): message received msg=3, ext1=1, ext2=0 11-19 14:09:41.990 E/MediaPlayer( 6226): callback application 11-19 14:09:41.990 E/MediaPlayer( 6226): back from callback 11-19 14:09:41.995 E/( 2207): III Inside Constructor of PVMFMemoryBufferReadDataStreamImpl 11-19 14:09:41.995 E/( 2207): III Inside Constructor of PVMFMemoryBufferReadDataStreamImpl 11-19 14:09:41.995 E/( 2207): III Inside Constructor of PVMFMemoryBufferReadDataStreamImpl 11-19 14:09:41.995 E/( 2207): III Inside Constructor of PVMFMemoryBufferReadDataStreamImpl 11-19 14:09:41.995 E/( 2207): III Inside Constructor of PVMFMemoryBufferReadDataStreamImpl 11-19 14:09:41.995 E/( 2207): III Inside Constructor of PVMFMemoryBufferReadDataStreamImpl 11-19 14:09:41.995 E/( 2207): III Inside Constructor of PVMFMemoryBufferReadDataStreamImpl 11-19 14:09:41.995 E/( 2207): III Inside Constructor of PVMFMemoryBufferReadDataStreamImpl 11-19 14:09:41.995 E/( 2207): III Inside Constructor of PVMFMemoryBufferReadDataStreamImpl 11-19 14:09:41.995 E/( 2207): III Inside Constructor of PVMFMemoryBufferReadDataStreamImpl 11-19 14:09:41.995 E/( 2207): III Inside Constructor of PVMFMemoryBufferReadDataStreamImpl 11-19 14:09:41.995 E/( 2207): III Inside Constructor of PVMFMemoryBufferReadDataStreamImpl 11-19 14:09:42.000 E/MediaPlayer( 6226): message received msg=3, ext1=2, ext2=0 11-19 14:09:42.000 E/MediaPlayer( 6226): callback application 11-19 14:09:42.000 E/MediaPlayer( 6226): back from callback 11-19 14:09:42.000 E/MediaPlayer( 6226): message received msg=3, ext1=4, ext2=0 11-19 14:09:42.000 E/MediaPlayer( 6226): callback application 11-19 14:09:42.000 E/MediaPlayer( 6226): back from callback 11-19 14:09:42.000 E/MediaPlayer( 6226): message received msg=3, ext1=5, ext2=0 11-19 14:09:42.000 E/MediaPlayer( 6226): callback application 11-19 14:09:42.000 E/MediaPlayer( 6226): back from callback 11-19 14:09:42.000 E/( 2207): III Inside Constructor of PVMFMemoryBufferReadDataStreamImpl 11-19 14:09:42.005 E/( 2207): III Inside Constructor of PVMFMemoryBufferReadDataStreamImpl Any information out there on this would be great. Occasionally, songs just fail. But, even without failing I get 101 consecutive errors from the MediaPlayer, starting with ext1=0 thru ext1=100, as well as this III constructor business. This makes finding real errors in the log very very hard. Bad Samsung. On Dec 9, 8:41 am, Rich miser...@gmail.com wrote: Hello! I'm having some significant issues with MP3 streaming on large files on Samsung Devices with Android 2.1 (ie, the Samsung Galaxy S). This is using mfrederick's NPR-code for streaming mp3 support. Has anybody else encountered this? Does anybody have a Samsung phone which allows side-loading who would be willing to help debug this? Here is the dump trace. SISO apparently means Samsung India Software Operations 12-07 17:39:35.812 D/MediaPlayerService( 2209): getPlayerType : url =http://127.0.0.1:60943/http://mymp3.mp3, filePath =http://127.0.0.1:60943/http://mymp3.mp3 12-07 17:39:35.812 D/ ( 2209): SISO TEST registering PVMFRecognizerPluginFactory 12-07 17:39:35.812 D/ ( 2209): SISO TEST registering PVMFRecognizerPluginFactory success 12-07 17:39:35.822 E/ ( 2209): III Inside Constructor of PVMFMemoryBufferWriteDataStreamImpl 12-07 17:39:35.912 I/System.out( 2935): interface name: null 12-07 17:39:38.515 I/AudioHardwareALSA( 2209): Output standby called!!. Turn off PCM device. 12-07 17:39:41.147 D/dalvikvm( 2935): GC freed 890 objects / 108752 bytes in 93ms 12-07 17:39:45.377 E/MediaPlayer( 2935): message received msg=3, ext1=0, ext2=0 12-07 17:39:45.377 E/MediaPlayer( 2935): callback application 12-07 17:39:45.377 E/MediaPlayer( 2935): back from callback 12-07 17:39:45.392 E/ ( 2209): III Inside Constructor of PVMFMemoryBufferReadDataStreamImpl 12-07 17:39:45.392 D/ ( 2209): SISO TEST PVOMA1FFRecognizerFactory::CreateRecognizerPlugin() 12-07 17:39:45.392 D/ ( 2209): SISO TEST
[android-developers] Re: Streaming MP3 Playback Problems on Android 2.2
I'm seeing this issue as well, and only with 2.2. I've seen it with the emulator, droid x, nexus one and moto droid. It happens lot more to me (10x+) with high bitrate streams than low ones (320 vs 120 kbps mp3). It seems intermittent and I can find nothing on the web posted about it other than this thread. It is a real problem with media apps running in 2.2. The constant -2147483648 always appears with this MediaPlayer error, and could probably be tracked down in the source. The problem is not with eMusic or the stream. I have seen the same issue with streams hosted by other services. On Sep 18, 12:51 pm, jdeslip jdes...@gmail.com wrote: Yes, it works fine on 2.1 and below. This is almost certainly related to the problems the Pandora/Last.fm etc.. apps have on 2.2. I just want to find out what the recommended tactic for developers with this problem is. Is Google on verge of releasing an update 2.2? Or is there an official workaround? On Sep 17, 11:58 pm, Indicator Veritatis mej1...@yahoo.com wrote: If that were the problem, then why would it work under 1.5 and fail under 2.2? On Sep 17, 8:50 pm, Doug beafd...@gmail.com wrote: Have you considered that eMusic might be doing something on the server side to prevent the stream from working? Many sites that stream things will leave urls active for a limited time or require you to preserve an HTTP session. -- 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] Re: Settings.Secure.ANDROID_ID not unique on DROID2?
Assuming new devices are fixed moving forward, I'm curious about devices remaining in market with this problem. Will an OTA update to Gingerbread fix the ANDROID_ID for clients with the default one? I'm guessing ANDROID_ID persists across os updates and that only hard reset will spawn a new one, after a device has updated to a version of the os/firmware that will correctly set it? My assumption, correct me if I'm wrong: In order to cure this insecure android id, a client must both update and reset? -Ben On Aug 21, 6:28 am, OldSkoolMark m...@sublimeslime.com wrote: Perhaps this has already been answered in the originating thread, but I couldn't find it. The LVL docs suggest using additional features besides ANDROID_ID, and the question was which? Dianne Hackborne had issues with using the IMEI. Is using the MAC address a better option? On Aug 20, 12:04 pm, Trevor Johns trevorjo...@google.com wrote: Hi everyone, Just to follow up a bit here, the reason we believe this is happening is because ro.serialno isn't set on these devices. (Note that the ro.* properties currently aren't required by the CDD/CTS.) Unfortunately, it seems that we're using ro.serialno as the seed for the PRNG when generating ANDROID_ID. See: frameworks/base/packages/SettingsProvider/src/com/android/providers/setting s/SettingsProvider.java:416 http://www.google.com/codesearch/p?hl=en#uX1GffpyOZk/packages/Setting... I've gone ahead and opened up a bug here for tracking purposes: http://code.google.com/p/android/issues/detail?id=10639 (We suspect that the Droid 2 isn't the only phone affected by this, likely just the most noticeable instance.) We have a fix for this checked into our internal Git repo, so once that change propagates to vendors this shouldn't be an issue on future devices. For existing devices though, if you absolutely depend on the uniqueness of ANDROID_ID, you'll unfortunately need to rely on some other identifier (IMEI, WiFi MAC, etc.). -- Trevor Johns On Fri, Aug 20, 2010 at 10:46 AM, suzanne.alexandra suzanne.alexan...@motorola.com wrote: Andrew, I don't know that this is reported in any public bug system. I've reported it within a Motorola bug system. - Suzanne On Aug 20, 12:33 am, Maps.Huge.Info (Maps API Guru) cor...@gmail.com wrote: John, have you had any complaints yet about conflicts from duplicate unique ids? I handled it in code. -John Coryat -- 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.comandroid-developers%2Bunsubs cr...@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] Re: USB Issues: 2nd Droid not recognized by ADB
I had this issue. authorwjf suggested a fix that worked at the bottom of this post. Switched usb driver in device manager to USB Composite Device and it worked for me. Instructions: http://groups.google.com/group/android-developers/browse_thread/thread/3571170253b99d0/92c8a626e08e2574 On Aug 20, 11:46 am, Richard Schilling richard.rootwirel...@gmail.com wrote: I have two Droids. The first is recognized just fine by ADB and Eclipse. In hardware manager, it's identified as 'Android Phone/Android Composite ADB Interface'. The second is not recognized by ADB at all. In hardware manager, it's identified as 'Android Phone/Android Composite ADB Interface' The computer is a Windows 7 Professional machine. What's going on here? Richard -- 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] Re: connected Motorola Droid not recognized by adb
Thanks a-wjf. Switching device driver to USB Composite Device worked like a charm. Kostya, I've never seen that menu and on both 2.1 and 2.2 the Droid only allows for mounting and unmounting from that menu. But, your screenshots are sweet and I'd like your menu instead of mine. On Aug 19, 1:28 pm, authorwjf wfran...@softlayer.com wrote: Like you I had similar problems getting my Motroloa DROID to show up as a device in Android Device Chooser dialog under Eclipse. I am running the 32-bit version of Windows 7. I found a number of forums that tried to address this issue, but no one seemed exactly sure what was happening, and a number of the sites suggested re-installing Windows. It just so happens that prior to doing Android development I wrote device drivers for Windows. So I am at a bit of an advantage here. USB drivers can be touchy, but you shouldn't have to re-install your OS and the idea of a driver boost app from a third party makes me shudder. More than likely what is happening is the OS has associated your DROID with the generic driver that comes with the Windows Android SDK. You can verify this by bringing up the Windows Device Manager. If in your root node you see, ANDROID PHONE instead of ADB INTERFACE, this post should solve your problem. Obviously, if you have not already gone out to the Motorola website and downloaded the 32 or 64 bit drivers for the DROID, this needs to be your first step. After you run the MSI you downloaded from Motorola, reboot your machine, bring up your old friend the device manager again, and reconnect your DROID. As mentioned in other posts on this thread, you need to have the USB debugging turned on from the DROID's application menu. Expand the ANDROID PHONE node, right click, and choose UPDATE DRIVER SOFTWARE. You will be presented with two options, the one you want is BROWSE MY COMPUTER FOR DRIVER SOFTWARE. When the next dialog comes up, select LET ME PICK FROM A LIST OF DEVICE DRIVERS ON MY COMPUTER. As long as you have the SHOW COMPATIBLE HARDWARE box checked, you should see a couple options. Ideally, you are looking for MOT COMPOSITE ADB INTERFACE. However, in some cases only ANDROID COMPOSITE ADB INTERFACE shows up. This *should* work as well. The one thing you don't want is the generic ANDROID ADB INTERFACE, which seems to be the default (thus the problem to begin with). Click NEXT and the driver will install. Its possible at this point (in fact likely), Windows will force you to do a reboot. Once that is complete you should be good to go. Hope this was helpful! -- 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] Re: connected Motorola Droid not recognized by adb
I have been seeing the same issue as John for a few weeks now, but have not posted about it because I do have a working Droid, also. I think it's an issue with the device, but I cannot confirm that. Here is what I know: * I have two Droids. One is recognized by adb when connected, and the other is not. I have been through every setting on the device and have been fully unable to attach one of the two Droids, ever. * BOTH droids have the same software -- Firmware: 2.1-update1 Baseband version: C_01.3E.03P Kernel: 2.6.29-omap1-g7fa8788android- bu...@apa26 #1 Build number: ESE81 * USB debugging, Allow Mock Locations, and Unknown sources are all checked on both devices * None of my other 5 android phones have ever done this, including the third droid that belongs to my gal. Busted Droid connected: $ adb devices List of devices attached Working Droid connected: $ adb devices List of devices attached 040362610D009006device I have not found the Portal Tools menu Kostya is talking about... For the life of me I cannot find out why the busted droid never connects to ADB. I can't debug or sideload on the crappy one. It's only for release testing at this point. Anyone else seen this issue or know more about it? Ben On Aug 12, 3:55 am, Kostya Vasilyev kmans...@gmail.com wrote: John, I am developing on a Moto Milestone, which is essentially same phone. Pull down the status area. Select the item with the USB icon (USB connection management, or something like that), not the triangular one. Choose Portal Tools from the list that pops up. This will make the phone visible to adb and Eclipse - assuming the drivers really did install correctly. You might be prompted to install additional drivers at this point (actual adb driver). -- Kostya 12.08.2010 3:25, john brown пишет: Hello, I am trying to connect a Verizon Motorola Droid (Android 2.1) to my computer and Run my application on the device. I have followed the instructions on developer.android.com about how to install the USB driver and set up the device for development. Specifically, I installed the Usb driver from whithin Eclipse (galileo) using the Adnroid SDK and AVD Manager. (I checked adb at this time and no recognition.) Then I installed the driver in windows (XP) via Start Control Panel Add Hardware. The windows installation seemed to work because during or after the installation of the C:\android-sdk-windows\usb_driver some window came up and announced that the adb bla.. bla. was installed successfully. On the device I have enabled debugging via Settings Applications Development USB debugging is checked. I also bring down the tri fork thing and mount the sdcard. I can successfully copy files to and from the device sdcard. My application successfully runs on the ADV and I can access the ADV sdcard using adb push and adb shell. With the moto droid connected, mounted, etc, if I run the command prompt adb command adb devices the resulting list is empty. No devices recognized. With the ADV running and the moto droid connected, mounted, etc, if I run the command prompt adb command adb devices the resulting list shows only the emulator-5554 device. (this is the same thing it shows if the moto droid is not connected and only the ADV is running). If I Run from Ecipse with the device connected, debugging, and mounted, an instance of the ADV is launched and the program runs on the ADV, not the device. I cannot get anything to recognize that the device is connected. My conclusion is that the android debug bridge, adb, is not recognizing the device. I would appreciate any suggestions on how to get adb to recognize and work with my device. Thanks to all persons for previous favors and advice. John Brown P.S. Verizion website has a fix for device not recognized that is called DriverBoost and will update all your USB driver to the official version. I did not like the sound of Verizon fixing all my drivers when I am only having trouble with Verizon's Moto droid but I downloaded it anyway. this is the actual quote: DriverBoost scans your PC and uniquely identifies each and every device driver. Then using a sophisticated matching algorithm every device driver on your PC is matched with the latest version of that driver on our proprietary database. New drivers are then quickly downloaded onto your computer. I went to install DriverBoost and it quickly informs me that the first thing it will do is install the latest version of Microsoft.net. I DROPPED IT LIKE A HOT POTATO. -- Kostya Vasilev -- WiFi Manager + pretty widget --http://kmansoft.wordpress.com -- 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] Re: Bug with Android 2.2 Layout Gravity?
Other possibly useful links about negative margins and Froyo: http://code.google.com/p/android/issues/detail?id=9280 http://code.google.com/p/android/issues/detail?id=8754 On Aug 5, 11:48 am, TreKing treking...@gmail.com wrote: On Thu, Aug 5, 2010 at 12:53 PM, Stan stande...@gmail.com wrote: Has anyone else encountered this issue? Tip: always try searching the group for your problem first. A search for negative margin yields this: http://groups.google.com/group/android-developers/browse_thread/threa... http://groups.google.com/group/android-developers/browse_thread/threa... --- -- TreKing http://sites.google.com/site/rezmobileapps/treking - Chicago transit tracking app for Android-powered devices -- 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
