[android-porting] Re: opencore test cases issue
just Compiled the opencore outside Android, how do i test it? On Feb 25, 2:13 pm, RaviY wrote: > That is correct. > > On Feb 24, 1:44 am, arindam das wrote: > > > Hi Uander , > > I guess ur doing it correctly.While running the test > > cases already provided by the PVcore,one can only see the logs and not the > > output on the screen or the speaker. > > > This is what my experience says.Other people who worked on this can confirm. > > > Regards > > Arindam > > > On Wed, Feb 24, 2010 at 1:09 PM, Umang Gupta wrote: > > > Hi Guys , > > > > I am facing problems while runningopencoretest cases using : > > > > command : pvplayer_engine_test -test L > > > > Android branch : Eclair > > > Omap Zoom2 board > > > > test cases are running fine as per log : > > > > pvplayer_engine_test -test L > > > SDK Labeled: PVDEV_CORE_RELEASE_6.506.4.1 built on 20090312 > > > > Starting Test 0: New-Delete > > > Results for Test Case 0: > > > Successes 2, Failures 0 > > > > Starting Test 1: Open-Play-Stop-Reset > > > Starting Test 0: New-Delete > > > Results for Test Case 0: > > > Successes 2, Failures 0 > > > > Starting Test 1: Open-Play-Stop-Reset > > > Results for Test Case 1: > > > Successes 2, Failures 0 > > > > Starting Test 2: CPM Open-Play-Stop-Reset > > > Results for Test Case 2: > > > Successes 2, Failures 0 > > > > Starting Test 3: Metadata > > > Results for Test Case 3: > > > Successes 1, Failures 1 > > > > Starting Test 4: Timing > > > Results for Test Case 4: > > > Successes 2, Failures 0 > > > > Starting Test 5: Invalid State > > > Results for Test Case 5: > > > Successes 2, Failures 0 > > > > Starting Test 6: Stop When Prepared > > > Results for Test Case 6: > > > Successes 2, Failures 0 > > > > The issue is that I am not getting sound while song is being played ? Is > > > taht the correct command . plz guide me whats the issue there as Music and > > > All videos are working with sound on my zoom2 . > > > > Thanks : > > > Uander > > > > -- > > > unsubscribe: > > > android-porting+unsubscr...@googlegroups.com > > > website:http://groups.google.com/group/android-porting -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
Re: [android-porting] Power button functionality (sleep/resume/wakeup)
Girish, I do have the power management code within the Kernel enabled since my screen timeout causes the system to go into the suspend state. I can then hit the Power button to wake up the system nicely. When I do press the Power button while the system is active, I don't see any messages related to early_suspend, any ideas on what exactly I should be looking for?? Regards -- Ashwin On Sat, Feb 27, 2010 at 2:53 AM, girish wrote: > Ok, I get your point. Mapping the power key is the first thing to do. Rest > android should take care... > > Can you attach your defconfig file, need to check if all the proper power > flags are enabled..which is > important for android power frmwork to work. > > Also, when you press the power key do you see any early_suspend dumps on the > terminal? if it > does and doesn't go any further to suspend to RAM that means someone is > holding a wake_lock. > > -Girish >> >> >> >> >> -- Forwarded message -- >> From: Ashwin Bihari >> Date: Fri, Feb 26, 2010 at 8:41 AM >> Subject: Re: [android-porting] Power button functionality >> (sleep/resume/wakeup) >> To: girish >> >> >> Girish, >> >> No, I don't want the power button to turn the device off, I've already >> implemented that at the Kernel level through a different scheme. I >> want to invoke the Linux Power Manage suspend and resume functionality >> with the power button through Android. If you take any Android phone >> right now, there's usually a single button (the top button on the >> Motorola Droid for example) that when pressed will put the device to >> sleep if it was awake or wake it up if it was asleep. In the sleep >> mode the LCD is turned off and the touchscreen doesn't respond to >> anything. >> >> It's basically what happens when you let the screen timeout and the >> device goes to sleep. The power button allows you to put the device to >> sleep faster, and that's the functionality I'm trying to implement. >> >> I have the power button mapped to KeyEvent.KEYCODE_POWER in my Android >> build, but that doesn't do anything.. >> >> Regards >> -- Ashwin >> >> >> >> On Fri, Feb 26, 2010 at 12:05 AM, girish wrote: >> > I guess you intend to power off the device when you hit the power button >> > right? >> > >> > First, the keycode as you mentioned should map Android power key. >> > Secondly, >> > you should >> > have proper hook in baseport level for pm_power_off() for DEVICE OFF. >> > >> > >> > -Girish >> > >> > On Wed, Feb 24, 2010 at 9:16 AM, Ashwin Bihari >> > wrote: >> >> >> >> I've got a custom board designed around the OMAP3530 and we have a >> >> power button the device that we want to use to cause Android to go to >> >> sleep or wakeup based on it's current state. >> >> >> >> I've done a few searches and have figured out the the function >> >> goToSleep within the PowerManager handles this functionality. For the >> >> power button handler, I'm sending the KEY_POWER eventcode into >> >> Android..this is mapped appropriately into Andriod as >> >> KeyEvent.KEYCODE_POWER. However, pressing the button doesn't cause >> >> anything to happen with Android..what am I missing in making my >> >> connections? >> >> >> >> Regards >> >> -- Ashwin >> >> >> >> -- >> >> unsubscribe: android-porting+unsubscr...@googlegroups.com >> >> website: http://groups.google.com/group/android-porting >> > >> > >> >> -- >> unsubscribe: android-porting+unsubscr...@googlegroups.com >> website: http://groups.google.com/group/android-porting > > -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
Re: [android-porting] Power button functionality (sleep/resume/wakeup)
did you check if hitting the power button locks the screen? You might need to look into that first... -Girish On Mon, Mar 8, 2010 at 9:20 AM, Ashwin Bihari wrote: > Girish, > > I do have the power management code within the Kernel enabled since my > screen timeout causes the system to go into the suspend state. I can > then hit the Power button to wake up the system nicely. > > When I do press the Power button while the system is active, I don't > see any messages related to early_suspend, any ideas on what exactly I > should be looking for?? > > Regards > -- Ashwin > > > > On Sat, Feb 27, 2010 at 2:53 AM, girish wrote: > > Ok, I get your point. Mapping the power key is the first thing to do. > Rest > > android should take care... > > > > Can you attach your defconfig file, need to check if all the proper power > > flags are enabled..which is > > important for android power frmwork to work. > > > > Also, when you press the power key do you see any early_suspend dumps on > the > > terminal? if it > > does and doesn't go any further to suspend to RAM that means someone is > > holding a wake_lock. > > > > -Girish > >> > >> > >> > >> > >> -- Forwarded message -- > >> From: Ashwin Bihari > >> Date: Fri, Feb 26, 2010 at 8:41 AM > >> Subject: Re: [android-porting] Power button functionality > >> (sleep/resume/wakeup) > >> To: girish > >> > >> > >> Girish, > >> > >> No, I don't want the power button to turn the device off, I've already > >> implemented that at the Kernel level through a different scheme. I > >> want to invoke the Linux Power Manage suspend and resume functionality > >> with the power button through Android. If you take any Android phone > >> right now, there's usually a single button (the top button on the > >> Motorola Droid for example) that when pressed will put the device to > >> sleep if it was awake or wake it up if it was asleep. In the sleep > >> mode the LCD is turned off and the touchscreen doesn't respond to > >> anything. > >> > >> It's basically what happens when you let the screen timeout and the > >> device goes to sleep. The power button allows you to put the device to > >> sleep faster, and that's the functionality I'm trying to implement. > >> > >> I have the power button mapped to KeyEvent.KEYCODE_POWER in my Android > >> build, but that doesn't do anything.. > >> > >> Regards > >> -- Ashwin > >> > >> > >> > >> On Fri, Feb 26, 2010 at 12:05 AM, girish wrote: > >> > I guess you intend to power off the device when you hit the power > button > >> > right? > >> > > >> > First, the keycode as you mentioned should map Android power key. > >> > Secondly, > >> > you should > >> > have proper hook in baseport level for pm_power_off() for DEVICE OFF. > >> > > >> > > >> > -Girish > >> > > >> > On Wed, Feb 24, 2010 at 9:16 AM, Ashwin Bihari > >> > wrote: > >> >> > >> >> I've got a custom board designed around the OMAP3530 and we have a > >> >> power button the device that we want to use to cause Android to go to > >> >> sleep or wakeup based on it's current state. > >> >> > >> >> I've done a few searches and have figured out the the function > >> >> goToSleep within the PowerManager handles this functionality. For the > >> >> power button handler, I'm sending the KEY_POWER eventcode into > >> >> Android..this is mapped appropriately into Andriod as > >> >> KeyEvent.KEYCODE_POWER. However, pressing the button doesn't cause > >> >> anything to happen with Android..what am I missing in making my > >> >> connections? > >> >> > >> >> Regards > >> >> -- Ashwin > >> >> > >> >> -- > >> >> unsubscribe: > >> >> android-porting+unsubscr...@googlegroups.com > >> >> website: http://groups.google.com/group/android-porting > >> > > >> > > >> > >> -- > >> unsubscribe: > >> android-porting+unsubscr...@googlegroups.com > >> website: http://groups.google.com/group/android-porting > > > > > -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
[android-porting] Re: porting android to OMAP 3530 with Torpedo SOM
Hi Deva, posting again, can i use the bootloader and the kernel available with Rowboat/beagle board. As my board is same based on 3530 referance platform. Thanks ruby On Mar 5, 7:40 pm, Deva wrote: > Hi Eric, > did u get my post below?? or do u have any sepcific question? > > [re-posting from previous thread] > First you can get bootloader and kernel working. then you can start > working > on android FS. > > >> Can i use the existing Rowboat or beagleboard android port as starting > > point. > kernel patches for torpedo board were not available in any > Logic PD teams were working on it. > Instead of you starting afresh, you can get help from them > > You can get contact details here > -http://article.gmane.org/gmane.linux.ports.arm.omap/23190 > > >>Then try to apply the Torpedo android pathes. > > ya, Once you have kernel booted up, then u can start poritng android > FS. > > On Mar 5, 9:40 am, eric wrote: > > > > > can anybody help me, if i am doing it the right way > > > On Mar 4, 7:22 pm, winsmart7 winsmart wrote: > > > > Hi, > > > > I am newbee to Android porting, can anyone please help me. > > > > I have to develop BSP for OMAP 3530 referance board with Torpedo SOM. > > > What i have > > > 1) Torpedo pathes required for Android 2.6.29.rc3 > > > 2) Beagle board BSP > > > > I have few basic questions > > > > 1) Can i use the existing Rowboat or beagleboard android port as starting > > > point. > > > 2) Then try to apply the Torpedo android pathes. > > > > As i am doing it for the first time it wold be of great help if any body > > > giudes me. > > > > Are my aproaches proper, if not what is best approach > > > > Thanks > > > ruby- Hide quoted text - > > - Show quoted text - -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
[android-porting] Re: Regarding BT-OPP (file tranfer using OPUSH application) throughput
YES I ever measured and improved the sharing performance during development. What you has pointed out match our current design: 1. There is concurrent thread, if UI activity is launched as visible. One is writing to database about the sharing progress, and the other querying to update the UI. So during sharing, performance is better if just keep OPP session in background. Even if user doesn't launch UI, there is still frequent DB updating, which is time consuming too. I'm sure there could be improvements for the concurrent cases in app, but we can't just delete the DB operations. 2. I believe the 16k you mentioned is the read buffer size for file in BluetoothOppObexClientSession.java BufferedInputStream a = new BufferedInputStream(fileInfo.mInputStream, 0x4000); This 16k buffer size is a balance of local buffer size and remote buffer size, although 16k might not be a perfect number. Remote may use different OBEX MTU, like 4k, 8k, 16, 32k, 64k, etc. New devices(mostly smart phones) may use 64K because of its high performance, while most legacy phones may use 4k. I think your data is collected when use a device with 64k OBEX MTU. In this case, we have to transfer 4 times to fill remote buffer, which match your result. But if we are transferring to a 4k buffer device, larger buffer size will be split into more packets, and actually slow down the transfer. Thanks for your data. Let's improve it continuously. On Mar 5, 4:01 am, Bheemsen wrote: > Hi All, > > I am using Eclair 2.1 on OMAP platform. > Eclair 2.1 has BT-OPP support (file transfer from Gallery application) > > With OPP application throughput numbers around 600 Kb/s (tested with 15M > file). > > We found that the UI updation is taking around 40-50ms for every 16k data > transfer. > > 1) If i comment the UI updation the throughput comes around 950kbps. > > 2) In BluetoothOppObexServer.java the read size is 16 Kb/s ,if i increase > the read size from 16Kb to 64 Kb the throughput will be 820 Kb/s. > > Is anybody measured the throughput with OPP? > > Is there any way to improve the throughput? > > -- > Regards > Bheemsen -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
[android-porting] apply theme over setting application wide
Hi all. I want to apply theme over setting application wide. So I implemented below code but there was no effect. Please give me help. 1. AndroidMenifest.xml -> added Widget.ListView style provided in android system and I changed style.xml file like below 2. FrameWork/base/core/res/res/values/styles.xml before change : @android:drawable/ list_selector_background After change:
Re: [android-porting] Re: porting android to OMAP 3530 with Torpedo SOM
I have support for the LogicPD Torpedo and SOM LV DevKits based on the Rowboat release and will be publishing my changes shortly..will send an email to this and the Rowboat mailing list for interested parties.. Regards -- Ashwin On Mon, Mar 8, 2010 at 6:02 AM, eric wrote: > Hi Deva, > posting again, > > can i use the bootloader and the kernel available with Rowboat/beagle > board. > As my board is same based on 3530 referance platform. > > Thanks > ruby > > On Mar 5, 7:40 pm, Deva wrote: >> Hi Eric, >> did u get my post below?? or do u have any sepcific question? >> >> [re-posting from previous thread] >> First you can get bootloader and kernel working. then you can start >> working >> on android FS. >> >> >> Can i use the existing Rowboat or beagleboard android port as starting >> >> point. >> kernel patches for torpedo board were not available in any >> Logic PD teams were working on it. >> Instead of you starting afresh, you can get help from them >> >> You can get contact details here >> -http://article.gmane.org/gmane.linux.ports.arm.omap/23190 >> >> >>Then try to apply the Torpedo android pathes. >> >> ya, Once you have kernel booted up, then u can start poritng android >> FS. >> >> On Mar 5, 9:40 am, eric wrote: >> >> >> >> > can anybody help me, if i am doing it the right way >> >> > On Mar 4, 7:22 pm, winsmart7 winsmart wrote: >> >> > > Hi, >> >> > > I am newbee to Android porting, can anyone please help me. >> >> > > I have to develop BSP for OMAP 3530 referance board with Torpedo SOM. >> > > What i have >> > > 1) Torpedo pathes required for Android 2.6.29.rc3 >> > > 2) Beagle board BSP >> >> > > I have few basic questions >> >> > > 1) Can i use the existing Rowboat or beagleboard android port as starting >> > > point. >> > > 2) Then try to apply the Torpedo android pathes. >> >> > > As i am doing it for the first time it wold be of great help if any body >> > > giudes me. >> >> > > Are my aproaches proper, if not what is best approach >> >> > > Thanks >> > > ruby- Hide quoted text - >> >> - Show quoted text - > > -- > unsubscribe: android-porting+unsubscr...@googlegroups.com > website: http://groups.google.com/group/android-porting > -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
Re: [android-porting] apply theme over setting application wide
On Mon, Mar 8, 2010 at 6:51 AM, Mycall wrote: > 1. AndroidMenifest.xml > > >android:icon="@drawable/ic_launcher_settings" >android:theme="@android:style/Widget.ListView" > That is not a theme, that is the style of a list view. Please see the various API demos for defining actual themes. -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
[android-porting] Re: Regarding BT-OPP (file tranfer using OPUSH application) throughput
YES we ever measured the sharing performance. What you has pointed out match our current design: 1. If UI activity launched as visible, then database query will frequently conducted to refresh the progress bar; - So during sharing, performance is better if just keep OPP session in background; root cause is that only OPP service to update the DB while UI activity will not be triggered to compete DB access. Suppose user opens the notification and keeps watching the bar moving, speed will be impacted by UI. 2. I believe the 16k you mentioned is the file read buffer size in BluetoothOppObexClientSession.java BufferedInputStream a = new BufferedInputStream(fileInfo.mInputStream, 0x4000); The 16k buffer is a balance between local buffer size and remote buffer size. OBEX MUT could vary with different devices, like 4k, 8k, 16, 32k, 64k, etc. New device(like smart phones) may use 64k because of its high performance, while legacy phones may use 4k. I believe your data is collected with a device of 64k MTU. It's true that use a 64k buffer will have better performance, because we have to transfer 4 times to fill remote buffer. If we transfer to a 4k buffer device, larger buffer size make be split into more packets, actually slow down the transfer. Thanks for your data, let's improve it continuously. On Mar 5, 4:01 am, Bheemsen wrote: > Hi All, > > I am using Eclair 2.1 on OMAP platform. > Eclair 2.1 has BT-OPP support (file transfer from Gallery application) > > With OPP application throughput numbers around 600 Kb/s (tested with 15M > file). > > We found that the UI updation is taking around 40-50ms for every 16k data > transfer. > > 1) If i comment the UI updation the throughput comes around 950kbps. > > 2) In BluetoothOppObexServer.java the read size is 16 Kb/s ,if i increase > the read size from 16Kb to 64 Kb the throughput will be 820 Kb/s. > > Is anybody measured the throughput with OPP? > > Is there any way to improve the throughput? > > -- > Regards > Bheemsen -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
[android-porting] FAT32 file size limited to 2GB
I am trying to play back 3GB videos from an SDHC card in OpenCORE v2.05 in Cupcake. The player crashes every time. ADB shell reports the file size to be a negative number (overflow). I believe the maximum file size on FAT32 is 4GB (2^32 - 1). The maximum size I can access on Android is actually 2GB (2^31 - 1), which makes me think the addressing is performed with a signed integer instead of unsigned. Does anyone know how to access files that are larger than 2GB? Was this fixed in a later version of Android? Can I change the type of some kernel variable to an unsigned int to unlock the extra addressing space? -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
[android-porting] ALSA Mixer commands and Hooks in alsa.conf
Hi guys I have a problem with ALSA. In principle it works fine, but not automated... I can set some controls on my mixer driver with alsa_amixer sset "AUX out" on perfectly and Android can play sound then. My question is, how do I get ALSA to do this automaticaly when it tries to open a playback device? I tried to make a hook in alsa.conf. Is this the right place for it? but all I get is: external/alsa-lib/src/control/setup.c:555:(add_elem) Cannot obtain info for CTL elem (MIXER,'AUX out',0,0,0): No such file or directory I don't think that what I try to do is something special... Any help would be appreciated Sven -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
[android-porting] Re: opencore test cases issue
http://android.git.kernel.org/?p=platform/external/opencore.git;a=blob;f=quick_start.txt;h=19eb9b6e282577a6fb1274746b5c566a277e4efe;hb=f1867b231dc4393a20790f645a5c115dc0259846 On Mar 8, 9:16 am, genxsol wrote: > just Compiled the opencore outside Android, > how do i test it? > > On Feb 25, 2:13 pm, RaviY wrote: > > > That is correct. > > > On Feb 24, 1:44 am, arindam das wrote: > > > > Hi Uander , > > > I guess ur doing it correctly.While running the > > > test > > > cases already provided by the PVcore,one can only see the logs and not the > > > output on the screen or the speaker. > > > > This is what my experience says.Other people who worked on this can > > > confirm. > > > > Regards > > > Arindam > > > > On Wed, Feb 24, 2010 at 1:09 PM, Umang Gupta wrote: > > > > Hi Guys , > > > > > I am facing problems while runningopencoretest cases using : > > > > > command : pvplayer_engine_test -test L > > > > > Android branch : Eclair > > > > Omap Zoom2 board > > > > > test cases are running fine as per log : > > > > > pvplayer_engine_test -test L > > > > SDK Labeled: PVDEV_CORE_RELEASE_6.506.4.1 built on 20090312 > > > > > Starting Test 0: New-Delete > > > > Results for Test Case 0: > > > > Successes 2, Failures 0 > > > > > Starting Test 1: Open-Play-Stop-Reset > > > > Starting Test 0: New-Delete > > > > Results for Test Case 0: > > > > Successes 2, Failures 0 > > > > > Starting Test 1: Open-Play-Stop-Reset > > > > Results for Test Case 1: > > > > Successes 2, Failures 0 > > > > > Starting Test 2: CPM Open-Play-Stop-Reset > > > > Results for Test Case 2: > > > > Successes 2, Failures 0 > > > > > Starting Test 3: Metadata > > > > Results for Test Case 3: > > > > Successes 1, Failures 1 > > > > > Starting Test 4: Timing > > > > Results for Test Case 4: > > > > Successes 2, Failures 0 > > > > > Starting Test 5: Invalid State > > > > Results for Test Case 5: > > > > Successes 2, Failures 0 > > > > > Starting Test 6: Stop When Prepared > > > > Results for Test Case 6: > > > > Successes 2, Failures 0 > > > > > The issue is that I am not getting sound while song is being played ? > > > > Is > > > > taht the correct command . plz guide me whats the issue there as Music > > > > and > > > > All videos are working with sound on my zoom2 . > > > > > Thanks : > > > > Uander > > > > > -- > > > > unsubscribe: > > > > android-porting+unsubscr...@googlegroups.com > > > > website:http://groups.google.com/group/android-porting > > -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
[android-porting] Re: Eclair's opencore does not compile
As long as one of the recognizers is able to recognize the file, it should play. -Ravi On Mar 5, 11:22 am, genxsol wrote: > Yes, it successfully compiled the opencore with passthru. > > i need to test if passthru is really working but i dont see any DRM > file in /engines/player/test/data/ for testing. > can i test .dcf file with pvplayer ? > > On Mar 5, 2:07 am, RaviY wrote: > > > > cc1plus: warnings being treated as errors > > > It looks like there is some warning and it is being treated as an > > error. > > > Comment the following line and try > > again.http://android.git.kernel.org/?p=platform/external/opencore.git;a=blo... > > > -Ravi > > > On Mar 4, 12:02 pm, genxsol wrote: > > > > i am getting this error when i compile opencore > > > > cc1plus: warnings being treated as errors > > > /home/zeeshan/opencore/engines/player/test/src/ > > > test_pv_player_engine.cpp: In function ‘int _local_main(FILE*, > > > cmd_line*, bool&)’: > > > /home/zeeshan/opencore/engines/player/test/src/ > > > test_pv_player_engine.cpp:2345: error: format not a string literal and > > > no format arguments > > > make: *** [/home/zeeshan/opencore/build_config/opencore_dynamic/build/ > > > engines/player/test/build/android/linux/dbg/test_pv_player_engine.o] > > > Error 1 > > > > could anybody help? > > > > On Mar 4, 1:38 am, Deva R wrote: > > > > > >The following files are there but their path does not show up as a "- > > > > >I" option: > > > > >== > > > > > > > > > >build_config/opencore_dynamic/build/installed_include/ > > > > >pvmf_omx_basedec_node.h:85:22: error: OMX_Core.h: No such file or > > > > >directory > > > > > Make sure that LOCAL_C_INCLUDES in your Android.mk includes the relative > > > > path correctly. > > > > > -Deva > > > > > On Thu, Mar 4, 2010 at 4:08 AM, iod wrote: > > > > > Hi > > > > > With ECLAIR's source code, trying to compile opencore module > > > > > separatley I get some missing included files as well as some missing > > > > > "-I" options in the build system. > > > > > Can anybody point me at the right/quickest fixes for this? > > > > > > Here's the list of really missing files during the build: > > > > > === > > > > > tools_v2/build/make/entry_point.mk:142: build_config/opencore_dynamic/ > > > > > build/installed_include/ALL_HDRS_INSTALLED: No such file or directory > > > > > tools_v2/build/make/entry_point.mk:143: build_config/opencore_dynamic/ > > > > > build/installed_lib/linux/ALL_LIBS_INSTALLED: No such file or > > > > > directory > > > > > nodes/pvomxencnode/src/pvmf_omx_enc_node.cpp:55:23: error: utils/ > > > > > Log.h: No such file or directory > > > > > nodes/pvomxvideodecnode/src/pvmf_omx_videodec_node.cpp:36:23: error: > > > > > utils/Log.h: No such file or directory > > > > > nodes/pvomxaudiodecnode/src/pvmf_omx_audiodec_node.cpp:37:23: error: > > > > > utils/Log.h: No such file or directory > > > > > codecs_v2/omx/omx_m4v/src/mpeg4_dec.cpp:31:23: error: utils/Log.h: No > > > > > such file or directory > > > > > > The following files are there but their path does not show up as a "- > > > > > I" option: > > > > > > == > > > > > build_config/opencore_dynamic/build/installed_include/ > > > > > pvmf_omx_basedec_node.h:85:22: error: OMX_Core.h: No such file or > > > > > directory > > > > > build_config/opencore_dynamic/build/installed_include/ > > > > > pvmf_omx_basedec_node.h:89:27: error: OMX_Component.h: No such file or > > > > > directory > > > > > build_config/opencore_dynamic/build/installed_include/ > > > > > pvmf_omx_basedec_callbacks.h:30:23: error: OMX_Types.h: No such file > > > > > or directory > > > > > > As a consequence of the above here are the symbols the compiler fails > > > > > to recognise: > > > > > > == > > > > > 'ANDROID_PRIORITY_AUDIO' was not declared in this scope > > > > > 'LOGE' was not declared in this scope > > > > > 'LOGW' was not declared in this scope > > > > > 'OMX_BOOL' does not name a type > > > > > 'OMX_CALLBACKTYPE' does not name a type > > > > > 'OMX_ERRORTYPE' does not name a type > > > > > 'OMX_EVENTTYPE' does not name a type > > > > > 'OMX_EXTRADATATYPE' has not been declared > > > > > 'OMX_HANDLETYPE' does not name a type > > > > > 'OMX_PARAM_PORTDEFINITIONTYPE' does not name a type > > > > > 'OMX_PTR' does not name a type > > > > > 'OMX_PTR' has not been declared > > > > > 'OMX_STATETYPE' does not name a type > > > > > 'OMX_TICKS' does not name a type > > > > > 'OMX_U32' does not name a type > > > > > 'OMX_U32' has not been declared > > > > > 'PRIO_PROCESS' was not declared in this scope > > > > > 'PVLOGMSG_STACK_ERR' was not declared in this scope > > > > > 'gettimeofday' was not declared in this scope > > > > > 'setpriority' was not declared in this scop
Re: [android-porting] ALSA Mixer commands and Hooks in alsa.conf
> I tried to make a hook in alsa.conf. Is this the right place for it? It should be 'asound.conf', you can check below link for reference: http://git.omapzoom.org/?p=platform/vendor/ti/zoom2.git;a=blob;f=asound.conf;h=6b3d6c1742559e3af1bac47e59b4d0bde6f9f839;hb=4ab009e3790922961d4bf3f8b4fd90f0e3ad8a64 -Misa On Mon, Mar 8, 2010 at 3:17 PM, mesv wrote: > Hi guys > > I have a problem with ALSA. In principle it works fine, but not > automated... > > I can set some controls on my mixer driver with > > alsa_amixer sset "AUX out" on > > perfectly and Android can play sound then. > > My question is, how do I get ALSA to do this automaticaly when it > tries to open a playback device? > > I tried to make a hook in alsa.conf. Is this the right place for it? > > but all I get is: > > external/alsa-lib/src/control/setup.c:555:(add_elem) Cannot obtain > info for CTL elem (MIXER,'AUX out',0,0,0): No such file or directory > > > I don't think that what I try to do is something special... > > Any help would be appreciated > > Sven > > -- > unsubscribe: android-porting+unsubscr...@googlegroups.com > website: http://groups.google.com/group/android-porting > -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
[android-porting] Re: FAT32 file size limited to 2GB
The underlying file i/o c library calls are likely to be the common 32 bit signed versions unless someone specifically chose the 64 bit versions. On Mar 8, 1:13 pm, Hedge wrote: > I am trying to play back 3GB videos from an SDHC card in OpenCORE > v2.05 in Cupcake. The player crashes every time. ADB shell reports the > file size to be a negative number (overflow). > > I believe the maximum file size on FAT32 is 4GB (2^32 - 1). The > maximum size I can access on Android is actually 2GB (2^31 - 1), which > makes me think the addressing is performed with a signed integer > instead of unsigned. > > Does anyone know how to access files that are larger than 2GB? Was > this fixed in a later version of Android? Can I change the type of > some kernel variable to an unsigned int to unlock the extra addressing > space? -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
[android-porting] Re: video play on android-2.1_r1
Hi Andy,
On android-2.1_r1 tag, external/opencore/android/
android_surface_output.cpp (Line 938)
-processWriteResponseQueue(2);
+processWriteResponseQueue(1);
Now it works on my target board.
Thanks.
On Mar 4, 11:36 am, Andy Quan wrote:
> The problem is probably caused by the patch
> below:http://android.git.kernel.org/?p=platform/external/opencore.git;a=com...
>
> Emulator uses base class MIO which locks 2 output buffers by default now
> instead of 1 buffer previously. PV OMX by default allocates 2 buffers only,
> and that's why only 2 frames are rendered.
>
> On real board we can use libopencorehw to customize the lock number or
> number of output buffers to avoid this problem. But it seems a big surprise
> that video playback can not work naturally in formal release.
>
> Is this a correct understanding?
>
> BTW, there are some voices of opencore replacement in next Android release.
> Is this true?
>
>
>
>
>
> On Thu, Feb 4, 2010 at 8:38 AM, abukustfan wrote:
> > Hi all,
>
> > I play a video file from Gallery but it did not play properly on my
> > android-2.1_r1.
> > Player's progress bar increase normally but it only show the first
> > frame on screen.
> > The kernel should be fine as android-1.6_r1 work.
>
> > Does anyone else have the same problem as me?
>
> > --
> > # I/ActivityManager( 639): Starting activity: Intent
> > { act=android.intent.actio
> > n.VIEW dat=content://media/external/video/media/3
> > cmp=com.android.gallery/com.an
> > droid.camera.MovieView (has
> > extras) }
> > V/MovieView( 861):
> > hasFocus
> > W/PlayerDriver( 625): Using generic video
> > MIO
> > I/ActivityManager( 639): Displayed activity com.android.gallery/
> > com.android.cam
> > era.MovieView: 970 ms (total 970
> > ms)
> > E/SW_DEC ( 625): PV SW DECODER is used for
> > MPEG4
> > W/MediaPlayer( 861): info/warning (1,
> > 44)
> > I/MediaPlayer( 861): Info
> > (1,44)
> > D/MediaPlayer( 861):
> > getMetadata
> > V/MovieView( 861):
> > hasFocus
> > W/InputManagerService( 639): Window already focused, ignoring focus
> > gain of: co
> > m.android.internal.view.IInputMethodClient$Stub
> > $pr...@2d27f070
> > D/dalvikvm( 772): GC freed 2118 objects / 95520 bytes in 89ms
>
> > --
> > unsubscribe:
> > android-porting+unsubscr...@googlegroups.com > googlegroups.com>
> > website:http://groups.google.com/group/android-porting
>
> --
> Thanks,
> Andy
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
[android-porting] Re: ALSA Mixer commands and Hooks in alsa.conf
> > I tried to make a hook in alsa.conf. Is this the right place for it? > > It should be 'asound.conf', you can check below link for > reference:http://git.omapzoom.org/?p=platform/vendor/ti/zoom2.git;a=blob;f=asou... > alsa.conf loads asound.conf if I understood that right. But does it mather if I put the definitions in the alsa.conf files? I asume you have a running zoom board. Don't you get those "Cannot obtain info for CTL elem ..." messages? Are those hooks in this config file the mixer commands? Sven -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
