[android-porting] Re: Android Bluetooth Stack/Profile Certification

['Glenn Kasten' via android-porting]

> Is there any QDID for profiles and stack for Android 10/11? 

As I interpret bullet 1 
of https://www.bluetooth.com/develop-with-bluetooth/qualification-listing/ 
which reads:
"Product qualifications cannot be inherited from your supplier, you must 
complete the qualification of your product for yourself"
this would mean that such a QDID would not be usable.

> If not, is there any opensource tools/any mechanism available to certify 
fluoride stack/profiles?

Sorry I don't know, perhaps someone else will be able to help.

On Monday, January 4, 2021 at 8:59:36 AM UTC-8 sbajaj wrote:

> hi,
>
> Is there any QDID for profiles and stack for Android 10/11? If not, is 
> there any opensource tools/any mechanism available to certify fluoride 
> stack/profiles?
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-porting/9d99d2ee-ad3d-4a2a-94ca-f8d210fcb1a4n%40googlegroups.com.

[android-porting] Re: Back porting SystemUI

['Glenn Kasten' via android-porting]

I have not tried this myself.  But I think it is likely to be difficult due 
to possibility of
the Q SystemUI assuming the existence of Q APIs throughout.
You could try back-porting yourself, but it might be a lot of work.

On Monday, May 4, 2020 at 8:53:29 AM UTC-7, 6020peaks /\/\/\ wrote:
>
> Hi,
>
> I am currently running an experiment and I would like to know if back 
> porting the SystemUI is possible at all. Let's say I want to use the 
> Android Q SystemUI in Android P. Did anyone try this before?
>
> If it is not possible what is the reason when it comes to the existing 
> dependencies?
>
> Thanks a lot for any hint!
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-porting/dc308b5c-5141-42ad-aa13-f25b02e24aa8%40googlegroups.com.

[android-porting] Re: How to get current working directory from Android Linux to help debug a file not found issue?

['Glenn Kasten' via android-porting]

Did you try   ?  Note the "h" not "g" at end, and no leading 
"linux/"


On Wednesday, April 1, 2020 at 9:58:45 AM UTC-7, Dave McLaughlin wrote:
>
> I am trying to track down a file not found error in a Realtek WiFi driver 
> and I am trying to get the current working directory and print this to the 
> debug output.
>
> I can't find which header file getcwd() is located in. Most website 
> searches indicate to use  but this doesn't work and I get a 
> compiler error when I try to use getcwd()
>
> A search of the Linux source finds many references to this function.
>
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-porting/1dec0b6b-e9a9-4f6e-8221-0514b339e534%40googlegroups.com.

[android-porting] Re: Adding support for 4 mic streams

['Glenn Kasten' via android-porting]

Perhaps this could be prototyped with an Android phone using a USB I/O 
device (e.g. Focusrite)  and channel index masks for recording.
I have not tested this recently, but I did in the past, and hopefully it 
should still work.

On Tuesday, February 26, 2019 at 10:11:59 AM UTC-8, Kushtrim Pacaj wrote:
>
> Adding support for 4 mic streams
> Hi
>
> I'm looking to add support for 4 mic streams in AudioRecording for a
> custom embedded device, so instead of getting strem like
> LLRRLLRRLLRRLLRR, i'd get AABBCCDDAABBCCDD.
> As far as I can tell, I need to modify AudioRecord (java+cpp) ,
> AudioFlinger , AudioPolicyConfig  , tinyAlsa HAL in order to change
> channel count , masks, and appropriate buffer sizes. Also obviously
> the kernel driver should fill the buffer as requested by the
> configuration.
>
> To do this I think is going to take me a long time, so I'm first looking to
> see if there is something already written in which to base my work
> into.
>
> Is there any custom ROM / AOSP fork /  developer board BSP that has
> implemented a similar feature ?
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: i want to build audioserver (/frameworks/av/media/audioserver) to 64-bit in android ,and it can't startup

[Glenn Kasten]

As of now, the AOSP release of Android does not yet officially support 
64-bit audioserver.
We are considering adding 64-bit option for audioserver in a future release,
but I can't give you a schedule of when that might happen.
Even then, it may be limited to platforms that are capable of supporting it
(for example due to dependencies on various libraries etc.).

On Wednesday, January 23, 2019 at 6:14:25 PM UTC-8, Andrew Chen wrote:
>
> I want to build audioserver(/frameworks/av/media/audioserver) to 64-bit, 
> and refer to the instructions in Android.mk 
> (/frameworks/av/media/audioserver/Android.mk)
>
>
> I add AUDIOSERVER_MULTILIB :=64 in device.mk, but it can't startup,  
> check the log and find the following error. 
>
> 01-20 09:44:31.637 2581 2581 F linker : CANNOT LINK EXECUTABLE 
> "/system/bin/audioserver": unsupported ELF TLS DT entry in 
> "/system/lib64/libaudioflinger.so"
>
>
> Also, use FILE command to check if it's 64 bit:
>
>
> #audioserver
>
> console:/system/bin # file audioserver audioserver: ELF shared object, 
> 64-bit LSB arm64, dynamic (/system/bin/linker64), for Android 28, 
> BuildID=01599, stripped
>
>
> #.so
>
> console:/system/lib64 # file libaudioflinger.so libaudioflinger.so: ELF 
> shared object, 64-bit LSB arm64, for Android 28, BuildID=fd41f, stripped
>
>
> in /frameworks/av/media/audioserver/Android.mk
>
> # If AUDIOSERVER_MULTILIB in device.mk is non-empty then it is used to 
> control# the LOCAL_MULTILIB for all audioserver exclusive libraries.# This is 
> relevant for 64 bit architectures where either or both# 32 and 64 bit 
> libraries may be built.## AUDIOSERVER_MULTILIB may be set as follows:#   32   
>to build 32 bit audioserver libraries and 32 bit audioserver.#   64  
> to build 64 bit audioserver libraries and 64 bit audioserver.#   bothto 
> build both 32 bit and 64 bit libraries,#   and use primary target 
> architecture (32 or 64) for audioserver.#   first   to build libraries and 
> audioserver for the primary target architecture only.#to build 
> both 32 and 64 bit libraries and 32 bit audioserver.
>
>
> it should be work normally when specifying AUDIOSERVER_MULTILIB := 64
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: Enabling I2S on Snapdragon 820 dev kit

[Glenn Kasten]

Sorry, I should have mentioned that path is relative to the root of your 
kernel tree.
So after you git clone Linux kernel, it is in subdirectory sound/soc .
If you want to browse a kernel tree online, one popular one is Linus:
https://github.com/torvalds/linux/tree/master/sound/soc

On Friday, November 30, 2018 at 8:00:15 AM UTC-8, Paul Kalebu wrote:
>
> Thanks Glenn. Do you also have a link to the source code?
>
> On Wednesday, November 28, 2018 at 7:11:15 AM UTC-8, Glenn Kasten wrote:
>>
>> This answer is not specific to 820.
>> Usually this is done via ALSA SoC.
>> Documentation is here:
>> ASoC Digital Audio Interface (DAI) 
>> <https://www.kernel.org/doc/html/v4.19/sound/soc/dai.html#asoc-digital-audio-interface-dai>
>> https://www.kernel.org/doc/html/v4.19/sound/soc/dai.html
>> Source code is at sound/soc
>>
>> On Tuesday, November 27, 2018 at 1:51:34 PM UTC-8, Paul Kalebu wrote:
>>>
>>> I'd like to interface with an audio device over I2S with my 820 dev kit 
>>> as the I2S slave. How can I go about making changes in the kernel to allow 
>>> for audio communication over the I2S interface?
>>>
>>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: Enabling I2S on Snapdragon 820 dev kit

[Glenn Kasten]

This answer is not specific to 820.
Usually this is done via ALSA SoC.
Documentation is here:
ASoC Digital Audio Interface (DAI) 

https://www.kernel.org/doc/html/v4.19/sound/soc/dai.html
Source code is at sound/soc

On Tuesday, November 27, 2018 at 1:51:34 PM UTC-8, Paul Kalebu wrote:
>
> I'd like to interface with an audio device over I2S with my 820 dev kit as 
> the I2S slave. How can I go about making changes in the kernel to allow for 
> audio communication over the I2S interface?
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: Android P porting on x86 platform

[Glenn Kasten]

> I just want to know if AndroidP is completely available for development 
or not.

Yes, please see this announcement:

Android 9 "Pie" source code is now available.
https://groups.google.com/forum/#!topic/android-building/PeF_PdaeB0U

> For porting AndroidN I have used kernel 4.16. Can I use same for AndroidP 
or any kernel version requirement for AndroidP or any specific kernel 
configurations required to be enabled for AndroidP?

Please see all of the pages under
https://source.android.com/devices/architecture/kernel

and especially see this page:
https://source.android.com/devices/architecture/kernel/android-common

(but all of the other pages are important too).

On Wednesday, September 19, 2018 at 8:53:39 AM UTC-7, shahul hameed wrote:
>
> HI All.
>
>
> I ported AndroidN on x86 based platform It is working fine.
>
> Now i am planning to port Android-P, I just want to know if AndroidP is 
> completely available for development or not.
>
> For porting AndroidN I have used kernel 4.16. Can I use same for AndroidP 
> or any kernel version requirement for AndroidP or any specific kernel 
> configurations required to be enabled for AndroidP?
>
> Thanks in advance.
>
> Regards,
> SK shahul.
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: How can I build submodules of android source tree but do not download full android source code?

[Glenn Kasten]

In general, the Android build dependencies are fairly complex
and difficult to document accurately because they change frequently.
You might be able to get the information you want by taking an existing 
working
build with full source code, and analyzing the internal generated files 
that describe
the dependencies. Then you could reverse-engineer the dependencies from 
that working build
and look for only the ones needed for bionic and then re-download just 
those modules.
However, even if that approach worked, you would need to have full sources 
to begin with. :-(
There may be other approaches that don't require full source, but I'm not 
familiar with them. 

On Sunday, August 12, 2018 at 1:05:50 PM UTC-7, ZhiHao Zhu wrote:
>
> Hi!
> I just desire. 
> If I just want rebuild bionic, *but I do not want down full android 
> source code**, I tend to just clone Bionic alone.*
> Could I possible use android build system (platfrom/build 
> ) use lunch or other 
> tool(maybe) to build submodules like Binoic or system_core?
> if we could, what is the approximate process,and what kind of work needs 
> to be prepared ?
>
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: porting 32 services to 64 bit

[Glenn Kasten]

Some of the services you mention depend on other code that is currently 
32-bit only,
such as various plug-ins, drivers, codecs, etc.  It is on the roadmap to 
eventually
convert all of that dependent code to run in 64-bit also, but I can't give 
a schedule for it.
If you would like to contribute towards the effort, please see 
https://source.android.com/setup/contribute/#contribute-to-the-code

On Sunday, August 12, 2018 at 1:05:30 PM UTC-7, Shy Shalom wrote:
>
> The company I work for is looking to port all of the services and 
> libraries that are still 32 bit to 64 bit.
> The ones that are 32 bit that I'm aware of are
> - audioserver, and other camera, media and drm related libraries and 
> services
> - bluetooth services and executables (bluedroid)
>
> I'm looking for some general advice for this project and if anyone has 
> specific knowledge of why this has not been done yet
> or possible things that would make the difficult.
> Thanks in advance
>
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: [AUTOMOTIVE] Tips on how to build Android Automotive ROM

[Glenn Kasten]

This suggestion is not specifically for automotive.
You can start here: https://source.android.com/
especially the sections Setup and Porting.

On Tuesday, July 24, 2018 at 7:28:39 AM UTC-7, miguelarc wrote:
>
> Hi everyone. I'm an android developer, but complete newbie in Android 
> AOSP/OS. 
>
> I'm trying to start compiling and building a Android custom ROM, 
> automotive to be exact, in a Raspberry Pi or even a NXP board. 
>
> Could you guys share some hints/tips on how to do it? Is it the same as 
> compiling/building a ROM for smartphones?
>
> Thanks in advance :)
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: com.android.phone has stoped

[Glenn Kasten]

Can you please include a very short excerpt of logcat and dmesg around the 
time of pop-up?

On Monday, July 23, 2018 at 6:37:55 AM UTC-7, Akshay Mhaske wrote:
>
> Hi,
>
> I am porting AOSP android N to x86 based system. I am 
> getting com.android.phone has stoped pop-up continously with live USB.
> But If I install in pendrive or hard-disk I am not geting this pop-up.
>
> Can any one please help with this issue.
>
> Regards,
> Akshay
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: Port single module from AOSP to Samsung tablet

[Glenn Kasten]

Unfortunately, that approach rarely works. You almost always need to 
re-build
from the original source code tree, modified with specific changes to your 
particular
library.  Sorry!

On Monday, July 16, 2018 at 7:51:28 AM UTC-7, jake.s...@gmail.com wrote:
>
> Hey, 
> How can I port single module (assume libnfc-nci) to a spesific device?
>
> I don't want to compile and port the whole AOSP for my device and there 
> isn't unofficial ROM for my device that i can compile and take from him 
> the .so's that I need.
>
> can someone please refer me to how it can be done? (what do I need for 
> this? do i need to link the compile process to a pre-built kernel of my ROM 
> ? what are the necessary steps for this porting)
>
> thank you
> jack
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: tinymix configuration for DMIC on Snapdragon 820 with Android 8.0

[Glenn Kasten]

As far as I know, the full information may be proprietary.  But you might 
be able to find what you need
by doing a web search to locate an Android device based on that chipset, 
and if it's an open source project then
the information you need might be in the audio portion of the port. So you 
could see how the
Android port configures the routing.  That could get you pointed in the 
right direction.

On Wednesday, July 11, 2018 at 7:02:54 AM UTC-7, Paul Kalebu wrote:
>
> Is there a manual/reference out there for how to configure tinymix to 
> route audio for interfacing with a digital microphone on Snapdragon 820?
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: user build not working

[Glenn Kasten]

There is not much information here to work with.  Can you share more about
how far the boot-up reached, from logcat or kernel console log?
If it is long, please post a link to the log (e.g. pastebin URL) rather 
than the whole thing.

On Tuesday, July 10, 2018 at 7:31:54 AM UTC-7, shahul hameed wrote:
>
> Hi All,
>
> I am porting AOSP source to X86 based platform, I complied  "eng" build  
> it working fine.
> But i complied "user" build it is not working,  It is restarting after 
> detecting Android at /dev/sda1.can anyone help me to resolve this issue.
>
> Thanks in Advance,
> Sk shahul.
>
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: Disable USB Audio Routing Programmaticaly

[Glenn Kasten]

At one time there was a setting for this, and there may still be but I seem 
to recall it has suffered from bit rot and does not work as well as it used 
to.
Search source code in frameworks/base and packages/apps/Settings for all 
references to the symbol
USB_AUDIO_AUTOMATIC_ROUTING_DISABLED and then follow the bread crumbs from 
there.
Please update here with anything you find, as I am curious too.

On Monday, December 18, 2017 at 12:48:42 PM UTC-8, PW wrote:
>
> Hi, I'm wondering if there is a way to disable USB AUDIO ROUTING on 
> nougat. I did it in lower api via reflection and 
> setwireddeviceconnectionstate. This however doesn't seem to want to work on 
> nougat and i'm not sure if the reflection has changed at all.
>
> I want exclusive access on USB output and do not want system notifications 
> to go via USB as they interrupt the signal.
>
> Thanks
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: Android porting as headless image

[Glenn Kasten]

Have you considered Android Things 
 ?  Display is optional 
for Android Things.
You might also want to see Section 2. Device Types of Android Compatibility 
Definition (CDD) 

and Section 7.1. Display and Graphics 
 
for 
screen options, if compatibility matters to you.

On Thursday, November 9, 2017 at 11:40:31 PM UTC-8, Harish Hanumanthappa 
wrote:
>
> We have a requirement to port android  AOSP  for headless application. 
> Going through the emails and previous posts, I am not able to find 
> information on whether it is possible to customise the latest releases of 
> Android for the headless application. Any pointers on how to proceed or 
> alternative solutions to considered will be of help and highly appreciated.
>
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] service announcement for android-porting

[Glenn Kasten]

android-porting is a moderated discussion group.
Too often posts are rejected because they are off-topic.
Please take a moment to review the posting guidelines in the welcome 
message at top of group 
.
This will save grief for both you and the volunteer moderators.
Thank you!

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: Source code for RaspBerry PI-2

[Glenn Kasten]

Not what you're looking for, but related: Things for Raspberry Pi 3 


On Tuesday, September 12, 2017 at 4:12:04 PM UTC-7, Vishwanath Hegde wrote:
>
> Hi,
>
> I have a Raspberry Pi-2 board. Can some one point me to the android source 
> and images which can run on this board?
>
> Regards,
> Vishwanath
>
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: Information regarding Android Auto and Android Automotive

[Glenn Kasten]

This may cover what you need, but I was unable to locate a specific 
partnership contact for Auto
https://source.android.com/compatibility/contact-us#for-business-inquiries

On Monday, July 17, 2017 at 7:41:12 AM UTC-7, Renjith Rajagopal wrote:
>
> Hey Oscar,
>
> Have you got any additional information regarding Automotive.
> I was trying to integrate those feature .But couldnt able to find proper 
> documentation.
>
> Regards,
> RR
> On Friday, May 19, 2017 at 5:03:57 PM UTC+2, Oscar Dávila wrote:
>>
>> Hello, 
>>
>> I would like to get so information regarding Android Auto and Android 
>> Automotive, as today, I've only found information about how to develop 
>> applications for android auto (
>> https://developer.android.com/auto/index.html), however, I have not 
>> found information regarding how to add android auto support to an embedded 
>> system, let's say, add android auto in my embedded platform so I can 
>> connect my phone to it.  
>>
>> Also I would want to know more about Android Automotive (
>> https://source.android.com/devices/automotive) I understand that this is 
>> totally different to Android Auto, as this is the full android OS but with 
>> and automotive porting, is more information about this available out there?
>>
>> Regards!
>>
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: Question on fastboot oem unlock

[Glenn Kasten]

> 1. Is it possible to rename the unlock command to say 'fastboot oem 
secret_word'?

The host side of fastboot is open source, so you can do whatever you want 
to it, including adding an alias called "secret_word" or any other change. 
See
https://android.googlesource.com/platform/system/core/+/master/fastboot

However the device side of fastboot is often closed source, so you would 
need to work with the device OEM if you want to change that.

> 2. Is is possible if some one unlocks the device that it also formats the 
/system partition?

Standard implementations wipe the data partition.  If you want to modify 
the code to wipe more partitions, see #1 above.

On Wednesday, July 12, 2017 at 11:35:34 AM UTC-7, Joey Troy wrote:
>
> I have two questions and was wondering if anyone could assist
>
> 1. Is it possible to rename the unlock command to say 'fastboot oem 
> secret_word'?
>
> 2. Is is possible if some one unlocks the device that it also formats the 
> /system partition?
>
> Thanks,
>
> Joey
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: Assertion fail in AudioTrackShared

[Glenn Kasten]

Please file a bug report by following the instructions here:
  https://source.android.com/source/report-bugs
Be sure to include the device manufacturer and model, full build ID, 
reproduction instructions, and any other information that you think would 
be helpful.
Thank you


On Monday, May 29, 2017 at 10:05:37 AM UTC-7, srinidhi kandi wrote:
>
> Hi,
>
> I Randomly encountered assertion fail in Android-N because the 
> buffer/frames being null.
>
>
> Line 3392: 02-13 23:45:45.468  1145 19335 I AudioFlinger: BUFFER TIMEOUT: 
> remove(4097) from active list on thread 0xa8283780
> Line 3513: 02-13 23:45:45.567  1145 19337 W AudioFlinger: 
> PatchTrack::releaseBuffer() disabled due to previous underrun, restarting
> Line 3514: 02-13 23:45:45.567  1145 19337 F AudioTrackShared: Assertion 
> failed: buffer == NULL || buffer->mFrameCount == 0
>
> Could you indicate what scenario can cause this situation to occur.
>
> Thanks
>
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: Implementation of HAL for one of the feature in Android O

[Glenn Kasten]

The current HAL documentation is here:
https://source.android.com/devices/#Hardware-Abstraction-Layer
It has not yet been updated for O, because O is not open-source yet.
That URL will probably be updated sometime after O is open-source.


On Monday, May 22, 2017 at 7:34:52 AM UTC-7, Kirti Badkundri wrote:
>
> Hi All, 
>  Need help to create my own HAL for one of the feature in Android 
> O. As, In Android O, there are new concepts like HIDL. 
> Need inputs from experts.
> If possible share the contact number, so that I can discuss. It will be 
> great help from the Experts.
>
> Regards
> KKB
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: ninja: build stopped: subcommand failed. - HELP PLEASE !

[Glenn Kasten]

FYI for the future, please use android-building instead of android-porting
for this kind of topic.  More of the right people are on that discussion 
group.  Thank you

On Thursday, May 11, 2017 at 8:14:23 PM UTC-7, huang_qi...@hotmail.com 
wrote:
>
> I guess you are sharing the compiling server with others? Try the 
> following procedures:
>
> 1) Modify *SERVER_PORT_SERVICE *and *SERVER_PORT_ADMIN *value in file 
> *.jack_settings* to another number greater than 8000, for example 8040 
> and 8041.
> 2) Then modify *jack.server.service.port* and *jack.server.admin.port *
> value in file *config.properties *as same as step 1. (means 8040 and 8041 
> as example shows in step 1)
> 3) Recompile
>
> This works for me.
>
>
> 在 2017年5月11日星期四 UTC+8上午1:46:28，Aditya Parmar写道：
>>
>> *[  0% 16/20913] Ensure Jack server is installed and started*
>> *Jack server already installed in "/home/aditya/.jack-server"*
>> *Server is already running*
>> *ninja: build stopped: subcommand failed.*
>> *build/core/ninja.mk:148 : recipe for target 
>> 'ninja_wrapper' failed*
>> *make: *** [ninja_wrapper] Error 1*
>>
>>
>> *i'm getting this error everytime i do make*
>>
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: Building Chromium system webview apk

[Glenn Kasten]

This discussion group android-porting is focused on technical issues 
related to porting
the AOSP upstream distribution to non-AOSP-supported build targets.
Other distributions, proprietary services, and non-technical discussions, 
are all off-topic.
Please limit any follow-ups to the technical issues raised here.
Thank you

(I'm one of the volunteer moderators of this discussion group,
but I am not an expert in the technical area of this thread)

On Thursday, March 9, 2017 at 7:33:23 AM UTC-8, Michael Robbeloth wrote:
>
> I hate to bump an old thread like this, but I would like to know if there 
> are any guides, blog posts, or whitepapers on doing this especially in the 
> context of Android devices that do not have Google Play Services on them. 
> Google is really is stubborn about granting the licensing rights to Google 
> Play Services on hardware anything older than the current release. 
> Unfortunately, it is very difficult for small embedded shops to turn out 
> new Android firmware with the same speed that large-scale OEMs are able to 
> do -- it feels as though we'll always be behind the major players. It also 
> limits the use of Android on novel devices in niche markets where it would 
> be helpful to have Google Play Service (not necessarily for the Store) 
> where components like webview can get update on a more regular basis and 
> apps that have Google services dependencies can run more reliability (it's 
> amazing how few Android developers test for use on devices w/o Google 
> Services).
>
> Michael
>
> On Tuesday, January 19, 2016 at 12:35:20 PM UTC-5, Kyle wrote:
>>
>> I know Google has moved Android System WebView updates to the Play Store, 
>> but it looks like updates are not being pushed to 
>> android.googlesource.com.  For example, vanilla AOSP Lollipop (5.1.1) 
>> looks like it builds version 39 of Chromium, while my Nexus 5 (6.0.1) runs 
>> 47.0.2526.100.  (There is no AOSP marshmallow branch in 
>> external/chromium_org.)  For non-Play Store builds, is it possible to pull 
>> in a newer Chromium version directly from chromium.org (particularly in 
>> the interest of security updates)?  It looks like there are directions on 
>> building system_webview_apk from chromium.org (
>> https://www.chromium.org/developers/how-tos/build-instructions-android-webview),
>>  
>> but how can I tell which Chromium release versions are compatible with my 
>> AOSP version?
>>
>> Can anyone provide any insight on whether or not this is feasible?  Or do 
>> the Android System WebView updates from the Play Store contain additional 
>> changes that aren't available from chromium.org?
>>
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Porting from 5.1 to 6.0/7.0

[Glenn Kasten]

This is a re-post from one that accidentally slipped through moderation 
into the wrong group.
 cut here 

Hi,

looking for some starting point on checklists/change-logs etc for me to 
port an AOSP code base from Lollipop to 6.0 or 7.0

Any links and support are appreciated.

Regards,
Abhayadev S.

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: How to disable synchronization between audio and video when using openmax al api

[Glenn Kasten]

You may want to consider using the MediaCodec APIs.
Then you can control playback of each elementary stream more precisely 
yourself.

On Tuesday, December 13, 2016 at 11:42:56 AM UTC-8, Ashutosh Pandey wrote:
>
> Hi, 
>
> I am playing Mpeg2ts data streaming over udp network in android. I am 
> using openmax al apis exposed in NDK.
> I am facing high latency around 800-900 ms. I am suspecting because of 
> audio and video synchronization overhead latency is very high.
> I searched for api to disable audio and video synchronization but didn't 
> find one. 
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: Android 6.0.1: The player doesn't support this type of audio file

[Glenn Kasten]

Does the wav file play OK on other Android devices with open-source ports 
(such as Nexus and Pixel)?

If "yes", then it is probably a problem in your porting configuration so 
compare the media-related files of your port vs the other device.

If "no", then it may be that the particular file is of a kind of wav that 
is not supported,
so can you please supply a link to the file?

On Monday, November 21, 2016 at 7:49:03 AM UTC-8, Jagan Teki wrote:
>
> Hi,
>
> I've pored android 6.0.1 on my device and trying to play .wav file., but 
> when I am trying to play on Music app it's showing
> " The player doesn't support this type of audio file"
>
> Android audio HAL look fine, but it's not playing any help?
> [   80.461337] [c0] lpass_set_sched: [AudioOut_2] pid = 5677, prio = 49
> [   80.482909] [c1] lpass_set_sched: [AudioOut_2] pid = 5677, prio = 49
>
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: Where are security patches for older AOSP versions published?

[Glenn Kasten]

You might want to ask on android-security-discuss, since they focus on this 
kind of topic.
https://groups.google.com/forum/#!forum/android-security-discuss

But they don't seem to be active recently :-(


On Wednesday, November 9, 2016 at 9:33:15 AM UTC-8, Arne-Christian Blystad 
wrote:
>
> Hello,
>
> With the latest security bulletin ( 
> https://source.android.com/security/bulletin/2016-11-01.html ) it's 
> really difficult to update all components to the latest security patch 
> without getting access to the patches.
>
> E.g.
>
>- A-30916186
>- A-30259087
>- A-30765246
>- A-28672558
>- A-31217937
>
>
> We care about security on our products, and would love to provide our 
> customers with a secure system.
>
> Best regards,
> Arne-Christian Blystad
>
> On Friday, 12 August 2016 18:40:44 UTC+2, avk wrote:
>>
>> Hi,
>>
>> I'd like to [try to] make a custom build of AOSP for my device, which does 
>> not receive security updates from vendor anymore. For this reason I'm 
>> looking for sources of Android 4.4 along with all the relevant security 
>> patches.
>>
>> source.android.com  mentions 
>> that KitKat still receives security updates:
>>
>> The Android security team currently provides patches for Android versions 
>>> 4.4 (KitKat), 5.0 (Lollipop), 5.1 (Lollipop MR1), and 6.0 (Marshmallow).
>>
>>
>> Also latest security bulletin 
>>  alongside 
>> many CVE's mentions 4.4.4 among "Updated AOSP versions". Yet when I go 
>> to appropriate reference
>> (for example, this commit 
>> 
>>  
>> for first CVE in the list), the appropriate commit seems to appear only 
>> in master branch. I'm not familiar with AOSP version control yet, but I 
>> checked list of branches for this particular framework here 
>> .
>>
>> So, my question is: where do backported security patches go? If current 
>> googlegroup is not appropriate place for this question, please point me 
>> in the right direction.
>>
>> Cheers,
>>
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: Why drmserver is 32bit only?

[Glenn Kasten]

It's 32 bits due to various OEM and DRM provider dependencies, and since it 
is legacy code in maintenance mode we didn't think it was worth pushing for 
new 64 bit libraries.

On Sunday, October 23, 2016 at 9:06:06 PM UTC-7, Ted Jiang wrote:
>
> I am an android system developer, and recently I was assigned to make our 
> system pure 64bit.
> I found that drmserver’s makefile includes “LOCAL_32_BIT_ONLY”, which 
> makes 32bit is mandatory,  I don't understand why.
>
> I’ve also noticed this commit in 2014: 
>
> https://android-review.googlesource.com/#/c/88154/
>
>
> Any help would be appreciated.
>
>  
>
>
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: Porting Android Wear to New Smartwatch

[Glenn Kasten]

Note from one of the volunteer moderators ...

Please note that this thread is starting to veer off-topic.
The android-porting group is for discussion of porting the AOSP source code 
distribution to non-AOSP-supported build targets.



On Tuesday, April 5, 2016 at 11:20:04 AM UTC-7, Nikola Veljkovic wrote:
>
> I do not think you will find a link to the code. You should probably 
> contact Android Partnership. 
>  
>
> Please send inquiries about licensing Google Mobile Services through the GMS 
> contact  form. Other non-GMS 
> partnership inquiries can be sent to android-partnersh...@google.com
>
>
>  
> Hopefully somebody with more info will reply here.
>
> On Tuesday, April 5, 2016 at 7:49:54 PM UTC+2, Andrew Wang wrote:
>>
>> Does the AOSP site have a link to the code? I found this website: 
>> https://android.googlesource.com/platform/build/+refs, from the Google 
>> Git. Or do I have to contact Android Partnership to get the code?
>>
>> On Tuesday, April 5, 2016 at 9:59:02 AM UTC-4, Nikola Veljkovic wrote:
>>>
>>> Android Wear is (in part) proprietary code, not open source. If you have 
>>> access to it, look for Emerald release, which is based on Marshmallow.
>>>
>>> On Sunday, April 3, 2016 at 11:49:01 PM UTC+2, Andrew Wang wrote:

 Hi,

 How would I port Android Wear onto a smartwatch? Where can I find 
 specifically the Android Wear Marshmallow code? Also, how do I combine the 
 hardware drivers with the source code? 

 Your help is greatly appreciated.

>>>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: How to enable off_load audio on x86_64 emulator build and using goldfish kernel(3.10-m-dev),finally want to write compressed audio data to file at kernel level

[Glenn Kasten]

NY, I am curious how you ended up simulating a DSP in the emulator, and 
whether it was effective?
As far as I know the main purpose of the compress/offload feature is to 
reduce power consumption,
and I'm wondering whether that is as beneficial in the emulator environment.

On Wednesday, March 9, 2016 at 5:58:59 PM UTC-8, NY wrote:
>
> added below code to audio_policy.conf and push same file to /system/etc 
> and ran "adb shell stop media and start" media.
> Now I could see in dumpsys of media.audio_policy with COMPRESS_offload 
> flag got enabled.
> However I could not see receiving compressed data  to audio_hw.c file 
> ,please help me to understand more on this with emulator build.
> compress_offload {
> sampling_rates 8000|11025|16000|22050|32000|44100|48000
> channel_masks AUDIO_CHANNEL_OUT_MONO|AUDIO_CHANNEL_OUT_STEREO
> formats AUDIO_FORMAT_MP3
> devices AUDIO_DEVICE_OUT_SPEAKER|AUDIO_DEVICE_OUT_WIRED_HEADSET|
> AUDIO_DEVICE_OUT_WIRED_HEADPHONE
> flags AUDIO_OUTPUT_FLAG_DIRECT|AUDIO_OUTPUT_FLAG_COMPRESS_OFFLOAD|
> AUDIO_OUTPUT_FLAG_NON_BLOCKING
> }
> On Tuesday, September 29, 2015 at 12:02:42 PM UTC-7, NY wrote:
>>
>> Thanks ,Finally I found to enable offload audio on emulator.
>>
>> On Tuesday, September 29, 2015 at 9:20:39 AM UTC-7, NY wrote:
>>>
>>> Thanks for your reply,Please provide me pointer if you know someone in 
>>> Android Team at Google, who can help me on this?
>>>
>>> On Monday, September 28, 2015 at 2:42:58 PM UTC-7, Glenn Kasten wrote:
>>>>
>>>> Sorry, I don't know how to simulate a DSP on emulator.
>>>>
>>>> On Monday, September 28, 2015 at 12:49:15 PM UTC-7, NY wrote:
>>>>>
>>>>> I actually gone through your post before I post my Question and my 
>>>>> question is more about how can we do this in emulator?if so where can we 
>>>>> do 
>>>>> and collect the compressed data at kernel level.this will halp to 
>>>>> simulate 
>>>>> the audio dsp on emulator.
>>>>>
>>>>>
>>>>> On Monday, September 28, 2015 at 11:48:19 AM UTC-7, Glenn Kasten wrote:
>>>>>>
>>>>>> See post #4 of 
>>>>>> https://groups.google.com/forum/#!topic/android-porting/SBVinW-RHzU
>>>>>> in particular the paragraph that begins "Offloaded tracks are new for 
>>>>>> Android 4.4 (KitKat)"
>>>>>> and the next paragraph "To read more "
>>>>>>
>>>>>>
>>>>>> On Monday, September 28, 2015 at 11:41:48 AM UTC-7, YADLA NIRANJAN 
>>>>>> wrote:
>>>>>>>
>>>>>>> Hello,
>>>>>>>
>>>>>>> I have built x86_64 emulator from Google latest source code and as 
>>>>>>> well compiled goldfish kernel(3.10-m-dev) to generate 
>>>>>>> "./arch/x86_64/boot/bzImage"
>>>>>>>
>>>>>>> How to enable audio_offload?, want to enable 
>>>>>>> "AUDIO_OUTPUT_FLAG_COMPRESS_OFFLOAD" flag in audio_policy.conf, however 
>>>>>>> I 
>>>>>>> could not find this file in /system/etc/
>>>>>>> Assume somehow If we enable audio_offload on emulator build then I 
>>>>>>> want to know how to collect compressed audio data at kernel level(may 
>>>>>>> be at 
>>>>>>> compress_offload.c file ).
>>>>>>>
>>>>>>>
>>>>>>> Build instructions:
>>>>>>> Step1:Got the latest source code from 
>>>>>>> http://source.android.com/source/downloading.html
>>>>>>> Built the emulator using below configuration on latest Android 
>>>>>>> source code
>>>>>>>
>>>>>>> 
>>>>>>> PLATFORM_VERSION_CODENAME=REL
>>>>>>> PLATFORM_VERSION=5.1.51
>>>>>>> TARGET_PRODUCT=aosp_x86_64
>>>>>>> TARGET_BUILD_VARIANT=eng
>>>>>>> TARGET_BUILD_TYPE=release
>>>>>>> TARGET_BUILD_APPS=
>>>>>>> TARGET_ARCH=x86_64
>>>>>>> TARGET_ARCH_VARIANT=x86_64
>>>>>>> TARGET_CPU_VARIANT=
>>>>>>> TARGET_2ND_ARCH=x86
>>>>>>> TARGET_2ND_ARCH_VARIANT=x86
>>>>>>> TARGET_2ND_CPU_VARIANT=
>>>>>>> HOST_ARCH=x86_64
>>>>>>> HOST_OS=linux
>>>>>>> HOST_OS_EXTRA=Linux-3.13.0-63-generic-x86_64-with-Ubuntu-14.04-trusty
>>>>>>> HOST_CROSS_OS=windows
>>>>>>> HOST_BUILD_TYPE=release
>>>>>>> BUILD_ID=AOSP
>>>>>>> OUT_DIR=out
>>>>>>> 
>>>>>>> ran below command
>>>>>>> $make -j8
>>>>>>>
>>>>>>>
>>>>>>> Step2:Got kernel code using  below command
>>>>>>> git clone https://android.googlesource.com/kernel/goldfish.git
>>>>>>> ran below cmds
>>>>>>> $ make x86_64_emu_defconfig
>>>>>>> $ make -j8
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Note:If we successfully be able to write compressed data to a file 
>>>>>>> at kernel level, this will allow us to achieve in simulating audio DSP 
>>>>>>> on 
>>>>>>> emulator build.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> NY
>>>>>>>
>>>>>>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: HAL spec and implementation

[Glenn Kasten]

HAL implementations are usually in one of a few places:

open source: device/vendor/codename/area/...
for example Nexus 9 audio HAL is under device/htc/flounder/audio/

open source: hardware/vendor/area/...
for example Nexus 6P audio HAL is under hardware/qcom/audio/

closed source: could be anywhere else

On Wednesday, February 17, 2016 at 8:16:13 AM UTC-8, Jagee wrote:
>
> I'm looking for Android HAL specification document.
> Also, looking for HAL implementation in the OS.
> Not just example how to use it from application layer, but the HAL
> infrastructure itself in the OS.
> If this info is open, i'll be happy to get some link.
> Meanwhile, I found just headers structures, but not the implementation 
> itself.
> http://source.android.com/devices/halref/index.html
>
> Thanks.
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: Vendor binaries for Nexus 5X and 6P?

[Glenn Kasten]

Evan - thanks for catching this!

As Evan noted, this group android-porting,  is for discussion
of building AOSP distribution for non-AOSP-supported build targets.

The focus of group android-building is for building AOSP distribution for 
AOSP-supported build targets.

On Tuesday, November 3, 2015 at 7:42:22 AM UTC-8, Evan Anderson wrote:
>
> This should be in android-building since it's an AOSP target related 
> question.
>
> The 5X/6P operate like the Nexus 9.  The proprietary binaries reside on a 
> separate vendor partition (which is what vendor.img is), and as such the 
> binaries don't need to be built in to AOSP builds.
>
> On Monday, November 2, 2015 at 2:15:50 PM UTC-5, Hamilton Turner wrote:
>>
>> Hi all, 
>>
>> I don't see any vendor binaries for the 5X or 6P located at 
>> https://developers.google.com/android/nexus/drivers . I do, however, see 
>> a vendor.img in the nexus factory images here - 
>> https://developers.google.com/android/nexus/images?hl=en#bullhead
>>
>> Are the 5X/6P binaries not released yet, or is there some new mechanism 
>> being used to distributed vendor binaries? 
>>
>> Thanks,
>> Hamilton
>>
>>
>>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: How to enable off_load audio on x86_64 emulator build and using goldfish kernel(3.10-m-dev),finally want to write compressed audio data to file at kernel level

[Glenn Kasten]

Sorry, I don't know how to simulate a DSP on emulator.

On Monday, September 28, 2015 at 12:49:15 PM UTC-7, NY wrote:
>
> I actually gone through your post before I post my Question and my 
> question is more about how can we do this in emulator?if so where can we do 
> and collect the compressed data at kernel level.this will halp to simulate 
> the audio dsp on emulator.
>
>
> On Monday, September 28, 2015 at 11:48:19 AM UTC-7, Glenn Kasten wrote:
>>
>> See post #4 of 
>> https://groups.google.com/forum/#!topic/android-porting/SBVinW-RHzU
>> in particular the paragraph that begins "Offloaded tracks are new for 
>> Android 4.4 (KitKat)"
>> and the next paragraph "To read more "
>>
>>
>> On Monday, September 28, 2015 at 11:41:48 AM UTC-7, YADLA NIRANJAN wrote:
>>>
>>> Hello,
>>>
>>> I have built x86_64 emulator from Google latest source code and as well 
>>> compiled goldfish kernel(3.10-m-dev) to generate 
>>> "./arch/x86_64/boot/bzImage"
>>>
>>> How to enable audio_offload?, want to enable 
>>> "AUDIO_OUTPUT_FLAG_COMPRESS_OFFLOAD" flag in audio_policy.conf, however I 
>>> could not find this file in /system/etc/
>>> Assume somehow If we enable audio_offload on emulator build then I want 
>>> to know how to collect compressed audio data at kernel level(may be at 
>>> compress_offload.c file ).
>>>
>>>
>>> Build instructions:
>>> Step1:Got the latest source code from 
>>> http://source.android.com/source/downloading.html
>>> Built the emulator using below configuration on latest Android source 
>>> code
>>>
>>> 
>>> PLATFORM_VERSION_CODENAME=REL
>>> PLATFORM_VERSION=5.1.51
>>> TARGET_PRODUCT=aosp_x86_64
>>> TARGET_BUILD_VARIANT=eng
>>> TARGET_BUILD_TYPE=release
>>> TARGET_BUILD_APPS=
>>> TARGET_ARCH=x86_64
>>> TARGET_ARCH_VARIANT=x86_64
>>> TARGET_CPU_VARIANT=
>>> TARGET_2ND_ARCH=x86
>>> TARGET_2ND_ARCH_VARIANT=x86
>>> TARGET_2ND_CPU_VARIANT=
>>> HOST_ARCH=x86_64
>>> HOST_OS=linux
>>> HOST_OS_EXTRA=Linux-3.13.0-63-generic-x86_64-with-Ubuntu-14.04-trusty
>>> HOST_CROSS_OS=windows
>>> HOST_BUILD_TYPE=release
>>> BUILD_ID=AOSP
>>> OUT_DIR=out
>>> 
>>> ran below command
>>> $make -j8
>>>
>>>
>>> Step2:Got kernel code using  below command
>>> git clone https://android.googlesource.com/kernel/goldfish.git
>>> ran below cmds
>>> $ make x86_64_emu_defconfig
>>> $ make -j8
>>>
>>>
>>>
>>> Note:If we successfully be able to write compressed data to a file at 
>>> kernel level, this will allow us to achieve in simulating audio DSP on 
>>> emulator build.
>>>
>>> Thanks,
>>> NY
>>>
>>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: How to enable off_load audio on x86_64 emulator build and using goldfish kernel(3.10-m-dev),finally want to write compressed audio data to file at kernel level

[Glenn Kasten]

See post #4 of 
https://groups.google.com/forum/#!topic/android-porting/SBVinW-RHzU
in particular the paragraph that begins "Offloaded tracks are new for 
Android 4.4 (KitKat)"
and the next paragraph "To read more "


On Monday, September 28, 2015 at 11:41:48 AM UTC-7, YADLA NIRANJAN wrote:
>
> Hello,
>
> I have built x86_64 emulator from Google latest source code and as well 
> compiled goldfish kernel(3.10-m-dev) to generate 
> "./arch/x86_64/boot/bzImage"
>
> How to enable audio_offload?, want to enable 
> "AUDIO_OUTPUT_FLAG_COMPRESS_OFFLOAD" flag in audio_policy.conf, however I 
> could not find this file in /system/etc/
> Assume somehow If we enable audio_offload on emulator build then I want to 
> know how to collect compressed audio data at kernel level(may be at 
> compress_offload.c file ).
>
>
> Build instructions:
> Step1:Got the latest source code from 
> http://source.android.com/source/downloading.html
> Built the emulator using below configuration on latest Android source code
>
> 
> PLATFORM_VERSION_CODENAME=REL
> PLATFORM_VERSION=5.1.51
> TARGET_PRODUCT=aosp_x86_64
> TARGET_BUILD_VARIANT=eng
> TARGET_BUILD_TYPE=release
> TARGET_BUILD_APPS=
> TARGET_ARCH=x86_64
> TARGET_ARCH_VARIANT=x86_64
> TARGET_CPU_VARIANT=
> TARGET_2ND_ARCH=x86
> TARGET_2ND_ARCH_VARIANT=x86
> TARGET_2ND_CPU_VARIANT=
> HOST_ARCH=x86_64
> HOST_OS=linux
> HOST_OS_EXTRA=Linux-3.13.0-63-generic-x86_64-with-Ubuntu-14.04-trusty
> HOST_CROSS_OS=windows
> HOST_BUILD_TYPE=release
> BUILD_ID=AOSP
> OUT_DIR=out
> 
> ran below command
> $make -j8
>
>
> Step2:Got kernel code using  below command
> git clone https://android.googlesource.com/kernel/goldfish.git
> ran below cmds
> $ make x86_64_emu_defconfig
> $ make -j8
>
>
>
> Note:If we successfully be able to write compressed data to a file at 
> kernel level, this will allow us to achieve in simulating audio DSP on 
> emulator build.
>
> Thanks,
> NY
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: SoC requirement for Android

[Glenn Kasten]

See https://source.android.com/source/faqs.html#compatibility
and https://source.android.com/compatibility/index.html
and https://source.android.com/compatibility/android-cdd.pdf
Parts of compatibility are impacted by SoC choice.

On Tuesday, September 8, 2015 at 7:25:40 AM UTC-7, Raul Piper wrote:
>
> Hi, 
> We are developing a new SoC based hardware board,IS there any Official 
> Android Document for the SoC requirement for Android L ( and higher) 
> installation  - e.g Frequency,RAM,GPU,etc(what factor to be looked for?
> Is this the correct mailing list I have asked this Qs.
> Please let me know
> Thanks and Rgds,
> Rp
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [android-porting] Steps for begginer (Porting Tutorial)

[Glenn Kasten]

I recommend this site also:
  https://source.android.com/devices/index.html
The "interfaces" section describe the major Hardware Abstraction Layer (HAL)
interfaces that you will need to implement when you port to a new device.

On Thursday, September 3, 2015 at 5:33:29 PM UTC-7, Brian Yee wrote:
>
> Hi Raul,
>
> So if I wanted to build for the Samsung Galaxy Tab S2 9.7, which has 
> the Exynos 5433 CPU I could use the 'kernel/exynos' option listed in the 
> table?  Thus I can build the vanilla AOSP and put it on the tablet?  How 
> would I get things like the drivers for the video card, camera and other 
> hardware in the build?
>
> I believe  cyanogenmod has a build, but I want to learn how to do it 
> myself so I can play around with the AOSP, make changes and put it on the 
> tablet.
>
> If not how would I go about doing this with the Samsung tablet i have 
> referenced?  Buying a Nexus 9 is out of the questions right now.
>
> Thanks for any help!
> -Brian
>
>
>
>
> On Wednesday, July 22, 2015 at 10:35:19 AM UTC-4, Raul Piper wrote:
>>
>> Hi Jaimin,
>> Is your allwinner a20 processor listed under the list of Processors(Soc) 
>> mentioned in the list of AOSP(android Open Source kernel) kernels here : 
>> (under Figuring out which kernel to build : ) 
>>
>> -> 
>> http://source.android.com/source/building-kernels.html#figuring-out-which-kernel-to-build
>>
>>
>> DeviceBinary locationSource locationBuild configurationshamu
>> device/moto/shamu-kernelkernel/msmshamu_defconfigfugu
>> device/asus/fugu-kernelkernel/x86_64fugu_defconfigvolantis
>> device/htc/flounder-kernelkernel/tegraflounder_defconfighammerhead
>> device/lge/hammerhead-kernelkernel/msmhammerhead_defconfigflo
>> device/asus/flo-kernel/kernelkernel/msmflo_defconfigdeb
>> device/asus/flo-kernel/kernelkernel/msmflo_defconfigmanta
>> device/samsung/manta/kernelkernel/exynosmanta_defconfigmako
>> device/lge/mako-kernel/kernelkernel/msmmako_defconfiggrouper
>> device/asus/grouper/kernelkernel/tegrategra3_android_defconfigtilapia
>> device/asus/grouper/kernelkernel/tegrategra3_android_defconfigmaguro
>> device/samsung/tuna/kernelkernel/omaptuna_defconfigtoro
>> device/samsung/tuna/kernelkernel/omaptuna_defconfigpanda
>> device/ti/panda/kernelkernel/omappanda_defconfigstingray
>> device/moto/wingray/kernelkernel/tegrastingray_defconfigwingray
>> device/moto/wingray/kernelkernel/tegrastingray_defconfigcrespo
>> device/samsung/crespo/kernelkernel/samsungherring_defconfigcrespo4g
>> device/samsung/crespo/kernelkernel/samsungherring_defconfig
>>
>> If it is there it is fairly easy to start the porting process : 
>> As a summary these will be the steps : 
>>
>> 1.Download the Android source (start with Kitkat : 4.4.4 ) and build it , 
>> follow : http://source.android.com/source/building-running.html
>> 2.Download the kernel source for your board and build it. follow : 
>> http://source.android.com/source/building-kernels.html
>> 3.Link the zImage of the kernel built in #2 at 
>> arch//boot/zImage (use ln -s  kernel)
>> 4.Build the Android as whole or build the bootimage - make bootimage 
>> 5.Now in the device/// there must be a README 
>> to flash the board you have using fastboot.
>> 6.Using #5 Use the images formed in the  out/target/product/> name> - system.img ,boot.img and userdata.img as  formed after #4 (for all 
>> images ) to flash your board.
>> 7.Connect your Board with the HDMI cable to a Display screen and connect 
>> it using USB cable for USB adb debugging.
>>
>>
>> You can connect the minicom to get the output while your board 
>> boots(kernel) up by connecting RS232-to-USB cable with your board .
>> If you find any issue post the logs here .
>>
>> This link has all the information you need : 
>> http://source.android.com/source/building-kernels.html#figuring-out-which-kernel-to-build
>> and follow below points sequentially : 
>>
>>- Overview 
>>- Downloading and Building 
>>
>>- Initializing the Build Environment 
>>   
>>   - Downloading the Source 
>>   
>>   - Building and Running 
>>   
>>   - Building for Devices 
>>   
>>   - Building Kernels 
>>   
>>
>>
>>
>> Have a good luck exploring your board with the Android.
>> Rgds,
>> Rp
>>
>>
>>
>>
>>
>>
>>
>> On Wed, Jul 22, 2015 at 10:35 AM, Jaimin Ajmeri  
>> wrote:
>>
>>> Hi People,
>>>
>>> I would like to learn porting android os to allwinner a20 processor. I 
>>> want to learn the process involved in porting android os to a new board. 
>>> Please guide through the process.
>>>
>>> Thanks,
>>> Jaimin
>>>
>>> -- 
>>> -- 
>>> unsubscribe: android-porti...@googlegroups.com
>

[android-porting] improvements to source.android.com

[Glenn Kasten]

(apologies for the cross-post with android-building)

https://source.android.com/ is your "go to" site for technical information 
on
downloading, building, porting, and testing the Android Open Source Project.

We've just updated the site with several major additions,
in particular Google Feedback integration. This feature allows you to 
comment
on particular pages and make suggestions for improvements to the site.

Please check out the "What's New" section of
https://source.android.com/ and let us know what you think
(using Feedback of course!)

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: YouTube not adapting quality on new device

[Glenn Kasten]

I spoke with someone from our device compatibility team.
They are aware of this issue, especially on earlier versions of the OS.
The best way to get adaptive YouTube playbacks is to use the latest OS 
(currently 5.1.1 on some devices; or whatever is the latest available 
version on other devices).

As you are working with a device OEM,
I want to suggest a few other resources for OEMs:

AOSP
https://source.android.com/

compatibility discussion group
https://groups.google.com/forum/#!forum/android-compatibility
(registration required)

proprietary Google services including Youtube and others
https://source.android.com/compatibility/index.html#licensing-gms
https://source.android.com/compatibility/contact-us.html

On Friday, July 17, 2015 at 5:52:29 PM UTC-7, Bill wrote:
>
> Thanks for that. While your device compatibility team can address the 
> testing coverage issue, will they also be able to investigate the root 
> cause? If not, who/where do we need to forward this inquiry to, to help 
> determine what is needed for us to get YouTube working on our new device?
>
> On Friday, July 17, 2015 at 2:32:31 PM UTC-7, Glenn Kasten wrote:
>>
>> Thanks for the update.  
>>
>> By the way, the latest build for N6 is 5.1.1 according to
>>
>> https://source.android.com/source/build-numbers.html#source-code-tags-and-builds
>> so you will probably be offered an update for that.  It would be 
>> interesting to know how
>> well N6 running 5.1.1 works.  Also any other Nexus devices if you have 
>> access to them.
>>
>> You may have found a weakness in our compatibility testing,
>> so I will forward your note to the device compatibility team for them to 
>> investigate.
>>
>> On Friday, July 17, 2015 at 2:25:14 PM UTC-7, William Chow wrote:
>>>
>>> OK, we just got a Nexus 6 and confirmed that it doesn't have this 
>>> problem, i.e. it adapts up/down based on the network speed. This N6 is 
>>> running 5.0.1.
>>>
>>> On Thursday, July 16, 2015 at 8:41:54 AM UTC-7, Glenn Kasten wrote:
>>>>
>>>> Do you have test results for any Nexus family devices (e.g. 5, 6, 7, 
>>>> 10, etc.)?
>>>> Those are the reference devices used during release testing, so it will 
>>>> be helpful to know how they behave.
>>>> Please also include the exact OS version for each Nexus device.
>>>>
>>>> On Thursday, July 16, 2015 at 6:54:29 AM UTC-7, William Chow wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> Not sure if this is the right forum but came here first since it is 
>>>>> affecting development of a new device. Please let me know if there is a 
>>>>> better forum for this.
>>>>>
>>>>> I'm looking into a problem for an OEM regarding a new device in 
>>>>> development, where YouTube does not adaptively adjust the video quality 
>>>>> based upon the actual network speed. Instead, it always picks a specific 
>>>>> resolution to play based on the network type:
>>>>>
>>>>>1. 3G: 360p
>>>>>2. 4G: max device resolution
>>>>>3. WiFi: max device resolution
>>>>>
>>>>> The problem is that on WiFi or LTE, it does not adjust the quality 
>>>>> down when the network is too slow for the device's max resolution 
>>>>> (typically 720p or higher), and winds up stalling/buffering because it's 
>>>>> forcing 720p. Conversely, if I have a fast 3G connection, it won't adjust 
>>>>> the quality up above 360p even when the network can deliver 480p or 
>>>>> higher. 
>>>>> YouTube will stick to that quality even when I set quality to "Auto".
>>>>>
>>>>> I analyzed a variety of other devices and found some devices have this 
>>>>> problem, while most do not:
>>>>>
>>>>>- Devices that also have this problem (quality is fixed, selected 
>>>>>based on network type)
>>>>>   - Samsung Tab 4 (SM-T237P)
>>>>>   - Xolo Omega 5
>>>>>   - Star Up Vision
>>>>>- Devices that don't have this problem (quality is adaptive, 
>>>>>adjusts based on actual network speed)
>>>>>   - Samsung: S4, S5, S6, Note4
>>>>>   - LG: G2, G3, G4
>>>>>   - Panasonic P55
>>>>>   - Cherry: Flare, Topaz
>>>>>   - Sony: Xperia Z3
>>>>>
>>>>> One o

[android-porting] Re: YouTube not adapting quality on new device

[Glenn Kasten]

Thanks for the update.  

By the way, the latest build for N6 is 5.1.1 according to
https://source.android.com/source/build-numbers.html#source-code-tags-and-builds
so you will probably be offered an update for that.  It would be 
interesting to know how
well N6 running 5.1.1 works.  Also any other Nexus devices if you have 
access to them.

You may have found a weakness in our compatibility testing,
so I will forward your note to the device compatibility team for them to 
investigate.

On Friday, July 17, 2015 at 2:25:14 PM UTC-7, William Chow wrote:
>
> OK, we just got a Nexus 6 and confirmed that it doesn't have this problem, 
> i.e. it adapts up/down based on the network speed. This N6 is running 5.0.1.
>
> On Thursday, July 16, 2015 at 8:41:54 AM UTC-7, Glenn Kasten wrote:
>>
>> Do you have test results for any Nexus family devices (e.g. 5, 6, 7, 10, 
>> etc.)?
>> Those are the reference devices used during release testing, so it will 
>> be helpful to know how they behave.
>> Please also include the exact OS version for each Nexus device.
>>
>> On Thursday, July 16, 2015 at 6:54:29 AM UTC-7, William Chow wrote:
>>>
>>> Hi,
>>>
>>> Not sure if this is the right forum but came here first since it is 
>>> affecting development of a new device. Please let me know if there is a 
>>> better forum for this.
>>>
>>> I'm looking into a problem for an OEM regarding a new device in 
>>> development, where YouTube does not adaptively adjust the video quality 
>>> based upon the actual network speed. Instead, it always picks a specific 
>>> resolution to play based on the network type:
>>>
>>>1. 3G: 360p
>>>2. 4G: max device resolution
>>>3. WiFi: max device resolution
>>>
>>> The problem is that on WiFi or LTE, it does not adjust the quality down 
>>> when the network is too slow for the device's max resolution (typically 
>>> 720p or higher), and winds up stalling/buffering because it's forcing 720p. 
>>> Conversely, if I have a fast 3G connection, it won't adjust the quality up 
>>> above 360p even when the network can deliver 480p or higher. YouTube will 
>>> stick to that quality even when I set quality to "Auto".
>>>
>>> I analyzed a variety of other devices and found some devices have this 
>>> problem, while most do not:
>>>
>>>- Devices that also have this problem (quality is fixed, selected 
>>>based on network type)
>>>   - Samsung Tab 4 (SM-T237P)
>>>   - Xolo Omega 5
>>>   - Star Up Vision
>>>- Devices that don't have this problem (quality is adaptive, adjusts 
>>>based on actual network speed)
>>>   - Samsung: S4, S5, S6, Note4
>>>   - LG: G2, G3, G4
>>>   - Panasonic P55
>>>   - Cherry: Flare, Topaz
>>>   - Sony: Xperia Z3
>>>
>>> One other thing we noticed on some devices with this problem is that in 
>>> the YouTube "stats for nerds", the "Bandwidth" value is stuck on 0 KiB/s 
>>> (mini graph is empty). This was true for the Star and Xolo devices 
>>> mentioned above, although the Tab 4 was showing a valid bandwidth value, so 
>>> not sure if this is relevant/related to the issue.
>>>
>>> Is there a system property or other setting that needs to be set/cleared 
>>> to allow YouTube to automatically adjust quality based on actual network 
>>> speed?
>>>
>>> --Bill
>>>
>>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: YouTube not adapting quality on new device

[Glenn Kasten]

Do you have test results for any Nexus family devices (e.g. 5, 6, 7, 10, 
etc.)?
Those are the reference devices used during release testing, so it will be 
helpful to know how they behave.
Please also include the exact OS version for each Nexus device.

On Thursday, July 16, 2015 at 6:54:29 AM UTC-7, William Chow wrote:
>
> Hi,
>
> Not sure if this is the right forum but came here first since it is 
> affecting development of a new device. Please let me know if there is a 
> better forum for this.
>
> I'm looking into a problem for an OEM regarding a new device in 
> development, where YouTube does not adaptively adjust the video quality 
> based upon the actual network speed. Instead, it always picks a specific 
> resolution to play based on the network type:
>
>1. 3G: 360p
>2. 4G: max device resolution
>3. WiFi: max device resolution
>
> The problem is that on WiFi or LTE, it does not adjust the quality down 
> when the network is too slow for the device's max resolution (typically 
> 720p or higher), and winds up stalling/buffering because it's forcing 720p. 
> Conversely, if I have a fast 3G connection, it won't adjust the quality up 
> above 360p even when the network can deliver 480p or higher. YouTube will 
> stick to that quality even when I set quality to "Auto".
>
> I analyzed a variety of other devices and found some devices have this 
> problem, while most do not:
>
>- Devices that also have this problem (quality is fixed, selected 
>based on network type)
>   - Samsung Tab 4 (SM-T237P)
>   - Xolo Omega 5
>   - Star Up Vision
>- Devices that don't have this problem (quality is adaptive, adjusts 
>based on actual network speed)
>   - Samsung: S4, S5, S6, Note4
>   - LG: G2, G3, G4
>   - Panasonic P55
>   - Cherry: Flare, Topaz
>   - Sony: Xperia Z3
>
> One other thing we noticed on some devices with this problem is that in 
> the YouTube "stats for nerds", the "Bandwidth" value is stuck on 0 KiB/s 
> (mini graph is empty). This was true for the Star and Xolo devices 
> mentioned above, although the Tab 4 was showing a valid bandwidth value, so 
> not sure if this is relevant/related to the issue.
>
> Is there a system property or other setting that needs to be set/cleared 
> to allow YouTube to automatically adjust quality based on actual network 
> speed?
>
> --Bill
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: Does LP5.1 Support Multi-client Recording?

[Glenn Kasten]

Sorry, I can't share any future plans or schedules.

On Thursday, June 4, 2015 at 8:50:29 PM UTC-7, liu.yana...@gmail.com wrote:
>
> Thanks for your quick response.
> For multi-client recording, is there any plan to support in future android 
> release? Will it be ready in android M? 
>
> Best Regards
> Yanan
>
> 在 2015年6月5日星期五 UTC+8上午8:50:47，Glenn Kasten写道：
>>
>> No, there are bits of code, but it is incomplete and doesn't work.
>>
>> On Thursday, June 4, 2015 at 5:44:26 PM UTC-7, liu.y...@gmail.com wrote:
>>>
>>> I have a question about multi-client recording.
>>>
>>> In my opinion, multi-client recording means one input stream (eg. from 
>>> microphone), one record thread, with multiple record track for different 
>>> client. Please correct me if my understanding is wrong. :)
>>>
>>> I've noticed that there is related code in audioflinger/recordthread to 
>>> support multi-client recording, but it seems that when client new a 
>>> AudioRecord, AudioPolicyManger will always open a new input stream. Please 
>>> guide me how to use it.
>>>
>>> Thanks very much and looking forward to your reply.
>>>
>>> Best Regards
>>> Yanan
>>>
>>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: Does LP5.1 Support Multi-client Recording?

[Glenn Kasten]

No, there are bits of code, but it is incomplete and doesn't work.

On Thursday, June 4, 2015 at 5:44:26 PM UTC-7, liu.yana...@gmail.com wrote:
>
> I have a question about multi-client recording.
>
> In my opinion, multi-client recording means one input stream (eg. from 
> microphone), one record thread, with multiple record track for different 
> client. Please correct me if my understanding is wrong. :)
>
> I've noticed that there is related code in audioflinger/recordthread to 
> support multi-client recording, but it seems that when client new a 
> AudioRecord, AudioPolicyManger will always open a new input stream. Please 
> guide me how to use it.
>
> Thanks very much and looking forward to your reply.
>
> Best Regards
> Yanan
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: Question about AudioMixer

[Glenn Kasten]

You are correct, it is possible to overflow / clip if there are too many 
active tracks at a high volume.

On Monday, June 1, 2015 at 5:44:55 PM UTC-7, jcboo5...@gmail.com wrote:
>
> Hi.
>  
> I'm Android Developer.
>  
> I have some questions about AudioMixer of Android AudioFramework.
>
>  
>
> When Mixing audio frames sample by sample,
>
>  
>
> In theory, Overflow can be occurred. 
>
>  
>
> Because size of sample is 16bit size , so 32bit outTemp buffer is used in 
> AudioMixer.cpp
>
>  
>
> But, Tracks can be max 32 tracks, so It can be the range of
>
>  
>
> -32*4096*32767 ~ 32(max number of tracks)*4096(volume max 
> value)*32767(sample max valume).
>
>  
>
> But 32bit signed pcm can be ranged of -16*4096*32767 ~ 16*4096*32767.
>
>  
>
> So 16*4096*32767 ~ 32(max number of tracks)*4096(volume max 
> value)*32767(sample max valume) or -32*4096*32767~ -16*4096*32767 range 
> occur overflow.
>
>  
>
> I want know the reason that how come the outTemp buffer size is 32bit, and 
>
>  
>
> When the integer volume range is 0~ 2048 ,or outTemp buffer size is 64bit, 
> the overflow does not occur.
>
>  
>
> Please reply the question.
>
>  
>
> Thanks,
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: Question2 about AudioMixer(limiting)

[Glenn Kasten]

Yes, it is possible to overflow if there are too many tracks at high volume 
all playing at once.

On Monday, June 1, 2015 at 7:12:31 PM UTC-7, jcboo5...@gmail.com wrote:
>
> I have one more question of AudioMixer.
>
> I think Android Mixing technique is that, just add the pcm sample of 
> tracks.
>
> One sample size is 16 bit, so when the 8 tracks (having max volume) is 
> added, 
>
> 32367~ 8*32767 range valume is mapping to 32767.   -8*32767 ~ -32767 range 
> value is mappling to -32767.
>
> I want know I understand correctly.
>
> plz reply my question.
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: What does "deep buffer" mean in the audio system/driver?

[Glenn Kasten]

normal tracks - PCM, typical buffer size is ~20 ms, higher latency
fast tracks - PCM, typical buffer size is 5 ms or less, lower latency
deep buffer - PCM, typical buffer size is >= 100 ms, very high latency, 
intended to save power
codec offload - MP3/AAC/etc., very high latency, intended to save even more 
power than deep buffer

grep -r DEEP_BUFFER in frameworks/av/* is a starting point for details


On Thursday, May 21, 2015 at 12:32:39 PM UTC-7, 尹豪雲 wrote:
>
> Hello Experts,
>
> I am studying the Audio Framework recently.
> And I found the "deep buffer" playback which is used when playing MUSIC 
> stream. Right?
>
> I wonder to know what is the difference by comparing with other playback.
>
> 1. Deep Buffer
> 2. Codec Offload
> 3. Normal Tracks
>
> I think I know what are Codec Offload & Normal Tracks for.
> But I don't understand "deep buffer"
>
> 1. How does "deep buffer" work?
> 2. Why music stream plays as "deep buffer" way?
> 3. What is the benefit of the "deep buffer"
> 5. Where can I find any reference data about "deep buffer"
>
> Thanks & Best Regards.
>
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: what is the lunch option to use for Sprint Note 3 image

[Glenn Kasten]

For lunch combinations supported by the AOSP upstream distribution, see
https://source.android.com/source/building-devices.html#picking-and-building-the-configuration-that-matches-a-device

For lunch combinations supported by other distributions, you will need to 
contact wherever you got the distribution from.

This discussion group android-porting is about the process of porting to
non-AOSP-supported target devices, not about to build for a specific device.

On Thursday, May 14, 2015 at 12:21:35 PM UTC-7, Shahin Ansari wrote:
>
> I have a copy of Samsung Source, and AOSP. I have a zImage as a result of 
> following the instructions in the README files of the source. But I do not 
> know much about the build environment, and since I do not have a system.img 
> or ramdisk, I think I may have missed a step. I looked in 
> /out/target/product/generic directory. Do I still need to run lunch script 
> and the rest of the steps in the android.source.com? And if so what 
> should I put in the menu of lunch? 
>
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: question about audio latency

[Glenn Kasten]

Question 1:

The pipe from normal mixer's submix to fast mixer track 0 is needed for 
devices that can only handle a single output stream in the kernel.
This was a problem initially.  Nowadays, more devices support mixing in the 
kernel, so we could remove the pipe.
I am filing an internal issue to track this.  Please feel free to file an 
external issue here also, if you want to:
https://code.google.com/p/android/issues/entry

You are correct that mixing track 0 from the submix does add computational 
delay, but it does not add algorithmic delay
or significant latency.  So removing or disabling the pipe when possible 
should be more efficient for CPU usage / power consumption,
but I don't expect it will decrease latency significantly.

Question 2:

I am not sure what you mean, by delay caused by SRAM zero data.  Do you 
mean the computational delay
caused by writing zeroes into SRAM?  If so, that is not a significant 
contributor to total latency.
Or do you mean something else?

On Monday, May 11, 2015 at 5:11:53 AM UTC-7, weiwei Zhang wrote:
>
> I am an android platform developer, recently I am doing some investigation 
> about audio latency,and i have two question about it , could you help me on 
> that?
>
> 1st question:
>
> I just read the FastMixer code of LP5.0, when play a sound pool stream, a 
> fast track such as fast track1 will be created and audio flinger will also 
> write zero data to fast track0 , finally both of them will be mixed in fast 
> mixer thread.
>
> My question is why we need audio flinger audio_Out thread write zero data 
> to fast track0 and then mixed with fast track1,as i known, it will add more 
> latency for sound pool playback. Whether we can mix fast track 1-7 directly 
> by fast mixer thread and write them to HAL?
>
>  2nd question is:
>
> The definition of warm latency in CDD* is:*
>
> *"warm output latency*" is defined to be the interval between when an 
> application requests audio playback and when sound begins playing, when the 
> audio system has been recently used but is currently idle (that is, silent).
>
> As I known, when the audio system has been recently used but is currently 
> idle, audio_out thread in audio flinger will write zero data to SRAM(at 
> most 3 seconds), when application requests audio playback, should the warm 
> latency include the delay caused by SRAM zero data? 
>
>
> Thank you firstly.
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: PreProcessor Effects integration in AudioFlinger

[Glenn Kasten]

The audio input HAL normally runs on the same thread as RecordThread (it is 
called by RecordThread),
so I think this is OK.  But I will ask others to confirm.

On Tuesday, April 28, 2015 at 8:29:48 PM UTC-7, Hongyan wrote:
>
> I have a question about the preprocessing effects integration model in 
>
> current audio framework, could anyone help on?
>
>  
>
>  
>
>  
>
>  Currently Android provided 3 kinds of preprocessing effects: 
>
>  AEC/NS/AGC and they’re wrapped into libaudiopreprocessing.so
>
>  
>
>  When App(Eg: Hangout) created such kind effects (type == what defined 
>
>  in libaudiopreprocessing.so), effects will  be created and then handle 
>
>  will passed to HAL for further processing.
>
>  
>
>  
>
>  
>
>  SO maybe audio flinger should not call process_l function anymore for 
>
>  PRE or PROC effects, right? because they’re suppose to be handled in HAL.
>
>  
>
>  
>
>  
>
>  But in bool AudioFlinger::RecordThread::threadLoop()
>
>  
>
>  
>
>  
>
>  size_t size = effectChains.size();
>
>  
>
>  for (size_t i = 0; i < size; i++) {
>
>  
>
>  // thread mutex is not locked, but effect chain is locked
>
>  
>
>  effectChains[i]->process_l();
>
>  
>
>  }
>
>  
>
>  
>
>  
>
>  All of effects will be processed no matter if it’s PRE or PROC, so 
>
>  it’s possible both HAL and Audioflinger called the process function. 
>
>  It’s not expected. Is't a bug? 
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: audio output latency measurement suggestion

[Glenn Kasten]

Very creative suggestion!  It sounds like you have already done this test;
would you be willing to share some graphical data showing the relationship 
between the two pulses?
(e.g. a graph with time on X axis, and both accelerometer data and audio 
data on Y axis in different colors)

On Friday, April 3, 2015 at 4:47:40 PM UTC-7, George Tsiros wrote:
>
> use the accelerometer. as far as i can tell, the accelerometer sensor data 
> is not buffered thus latency is minimal
>
> rest device on something soft (i used cigarette rolling filters)
>
> set accelerometer to maximum refresh rate, on my xperia z ultra it is 200 
> Hz
>
> output pulses (say 1% duty cycle at 1 Hz) at maximum possible amplitude
>
> measure difference in time between request for sound playback and movement 
> detected via the accelerometer
>
> some tweaking will be necessary to filter out the noise from the signal
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: AOSP image with Developer Options enabled by default

[Glenn Kasten]

The source code for Settings is at 
packages/apps/Settings/src/com/android/settings/DevelopmentSettings.java
Search around in there. Best case, you can find a property name that you 
can set in your device.mk properties,
or worst case you can modify the code to do what you want.

On Thursday, March 12, 2015 at 5:50:40 AM UTC-7, Daniel Doron wrote:
>
> Hi,
>
> I would like to create an AOSP image where "Developer options" is enabled 
> by default, usb debugging also enabled by default and always allowed. 
> Is this possible? How can I do that? 
>
> Thanks,
> Daniel. 
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: custom rom on emuator gives EGL_NOT_INITIALIZED

[Glenn Kasten]

You can't combine components from different build targets.
For the emulator, you need to build with lunch for goldfish, and use only 
images from that build.

On Tuesday, February 3, 2015 at 8:24:00 AM UTC-8, suat...@gmail.com wrote:
>
> Hi everyone just im newbie of google groups and android systems. Sorry for 
> my english
>
> Im just try to run a custom rom on emulator and i take samsung galaxy s3 
> rom contains
>
> -boot.img
> -recovery.img 
> -system.img.ext4
>
> and i built a goldfish_armv7(3.4 version from git) kernel successfully 
> named zImage. this image working perfect with sdk images (4.4.2 , 4.2.2)
>
> when i give this command;
>
>  emulator -avd killer442 -system /home/sfk/Downloads/system.img.ext4 
> -kernel /home/sfk/goldfish/arch/arm/boot/zImage 
>or
>  emulator -avd killer442 -system /home/sfk/Downloads/system.img.ext4 
> -kernel /home/sfk/goldfish/arch/arm/boot/zImage -gpu off
>
> logcat gives me the log in file. How can i solve this problem. If i 
> compile this rom from source with editing build.prop for emulator can i run 
> it on emulator ? or any idea or theory ?
>
> thank you.
>
> 02-03 13:16:47.960: I/DEBUG(42): !@dumpstate -k -t -z -d -o 
> /data/log/dumpstate_app_native -m 44
> 02-03 13:16:48.110: E/dumpstate(92): Cannot get free space size. So, skip 
> dumpstate.
> 02-03 13:16:50.280: E/installd(99): Could not create directories; exiting.
> 02-03 13:16:50.320: E/keystore(100): chdir: /data/misc/keystore: No such 
> file or directory
> 02-03 13:16:51.200: E/SurfaceFlinger(96): ro.sf.lcd_density must be 
> defined as a build property
> 02-03 13:16:51.260: E/dalvikvm(97): /system/framework/android.policy.jar 
> odex has stale dependencies
> 02-03 13:16:51.260: E/dalvikvm(97): /system/framework/services.jar odex 
> has stale dependencies
> 02-03 13:16:51.260: E/dalvikvm(97): /system/framework/apache-xml.jar odex 
> has stale dependencies
> 02-03 13:16:51.280: I/Adreno(96): open(/dev/kgsl-3d0) failed: errno 2. No 
> such file or directory
> 02-03 13:16:51.320: W/libEGL(96): eglInitialize(0x1) failed (EGL_SUCCESS)
> 02-03 13:16:51.320: E/Adreno200-EGL(96): : 
> EGL_NOT_INITIALIZED
> 02-03 13:16:51.320: E/Adreno200-EGL(96): : 
> EGL_NOT_INITIALIZED
> 02-03 13:16:51.320: E/Adreno200-EGL(96): : 
> EGL_NOT_INITIALIZED
> 02-03 13:16:51.320: E/SurfaceFlinger(96): couldn't find an EGLConfig 
> matching the screen format
> 02-03 13:16:51.320: E/Adreno200-EGL(96): 
> : EGL_NOT_INITIALIZED
> 02-03 13:16:51.320: E/Adreno200-EGL(96): 
> : EGL_NOT_INITIALIZED
> 02-03 13:16:51.320: E/Adreno200-EGL(96): 
> : EGL_NOT_INITIALIZED
> 02-03 13:16:51.320: E/Adreno200-EGL(96): 
> : EGL_NOT_INITIALIZED
> 02-03 13:16:51.320: E/Adreno200-EGL(96): 
> : EGL_NOT_INITIALIZED
> 02-03 13:16:51.320: E/Adreno200-EGL(96): 
> : EGL_NOT_INITIALIZED
> 02-03 13:16:51.320: E/Adreno200-EGL(96): 
> : EGL_NOT_INITIALIZED
> 02-03 13:16:51.320: E/libEGL(96): eglQuerySurface:350 error 300d 
> (EGL_BAD_SURFACE)
> 02-03 13:16:51.320: E/libEGL(96): eglQuerySurface:350 error 300d 
> (EGL_BAD_SURFACE)
> 02-03 13:16:51.320: E/Adreno200-EGL(96): 
> : EGL_NOT_INITIALIZED
> 02-03 13:16:51.320: E/libEGL(96): call to OpenGL ES API with no current 
> context (logged once per thread)
> 02-03 13:16:51.320: A/libc(96): Fatal signal 11 (SIGSEGV) at 0x 
> (code=1), thread 111 (SurfaceFlinger)
> 02-03 13:16:51.420: I/DEBUG(42): failed to open tombstone file 
> '/data/tombstones/tombstone_00': No such file or directory
>
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: source.android.com site has been updated with new docs

[Glenn Kasten]

We now have a detailed list of all the new and improved documentation here:
https://groups.google.com/forum/#!topic/android-building/En61B4_KkAQ

On Monday, November 3, 2014 12:48:59 PM UTC-8, Glenn Kasten wrote:
>
> The Android Open Source Project (AOSP) site at 
> http://source.android.com/index.html
> has just been updated with new and re-organized documentation.
> See section "WHAT'S NEW" on the home page for a few of the highlights
> (and there many other improvements not listed).
> As always, please let us know if you find any errors, broken links, 
> or missing information that you would like to see added. 
> Please feel free to reply here with your comments and suggestions.
> Thanks for your feedback!
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] source.android.com site has been updated with new docs

[Glenn Kasten]

The Android Open Source Project (AOSP) site at 
http://source.android.com/index.html
has just been updated with new and re-organized documentation.
See section "WHAT'S NEW" on the home page for a few of the highlights
(and there many other improvements not listed).
As always, please let us know if you find any errors, broken links, 
or missing information that you would like to see added. 
Please feel free to reply here with your comments and suggestions.
Thanks for your feedback!

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: [Android][K44 Audio] AudioTrackShared mFutex deadlock

[Glenn Kasten]

Eleven - Thank you for your post.
I could not figure out from your post what your exact code change is.
Can you please upload your CL to AOSP?
See https://source.android.com/source/submit-patches.html
It will be easier to review there.
Thanks

On Monday, October 13, 2014 10:35:01 PM UTC-7, eleven xiang wrote:
>
> Dear All,
>
> firstly, I am sorry to trouble you for a Andriod Audio issue.
>
> in AudioTrackShared.cpp, for a recording case, we met below issue:
>
> recording case met overrun, so the inputThread will sleep a while, but 
> AudioRecrodThread will continue to run and block at mCblk->mFutex.
> if right now, user stop the recording, and the inputThread has no chance 
> to release mFutext, then to standby.
>
> And the client's interrupt was just called right before 
> AudioRecordThread's obtainBbuffer try to wait mCblk->mFutex.
> @@ -209,13 +209,18 @@ status_t ClientProxy::obtainBuffer(Buffer* buffer, 
> const struct timespec *reques
>  }
>  int32_t old = android_atomic_and(~CBLK_FUTEX_WAKE, &cblk->mFutex);
>  if (!(old & CBLK_FUTEX_WAKE)) {
> int rc;
>  if (measure && !beforeIsValid) {
>  clock_gettime(CLOCK_MONOTONIC, &before);
>  beforeIsValid = true;
>  }
> int ret = __futex_syscall4(&cblk->mFutex,
> mClientInServer ? FUTEX_WAIT_PRIVATE : FUTEX_WAIT, old 
> & ~CBLK_FUTEX_WAKE, ts);
>
> Then we will find that AudioRecrodThread will always be blocked, because 
> RecordTrack's destory will also miss the wake mCblk->mFutex, for it was 
> already Interrupted before.
>
> So I wonder why has below CBLC_INTERRUPT condition judgement before wake, 
> Could we just remove it ?
>
> void ClientProxy::interrupt()
> {
> audio_track_cblk_t* cblk = mCblk;
> if (!(android_atomic_or(CBLK_INTERRUPT, &cblk->mFlags) & 
> CBLK_INTERRUPT)) {
> (void) __futex_syscall3(&cblk->mFutex, mClientInServer ? 
> FUTEX_WAKE_PRIVATE : FUTEX_WAKE,
> 1);
> }
> }
>
>
> Thanks
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: how to build Android for Galaxy S2?

[Glenn Kasten]

Note from one of the moderators ...

The OP asked about a non-AOSP-supported device, 
which is exactly on-topic for this group android-porting.
So I allowed both the OP and the reply above.
However, detailed discussion of non-AOSP distributions
would be off-topic for this group. 
Please use appropriate forums that are specific to those non-AOSP 
distributions
if you need to go deeper into any of those.
Thanks! 

On Tuesday, September 9, 2014 1:07:33 AM UTC-7, extrapedestrian wrote:
>
> I would check these sites 
> http://www.xda-developers.com/
> http://www.cyanogenmod.org/
>
>
> http://xda-university.com/as-a-developer/getting-started-building-android-from-source
> http://forum.xda-developers.com/galaxy-s2/development-derivatives
>
> sorry no precise answer, i never built for this device.
>
> On Sunday, September 7, 2014 9:31:17 PM UTC+2, plevintampabay wrote:
>>
>> Hello,
>>
>>I've been writing apps for Android for a few
>> years, and I now have a need to get into the OS.
>>
>>
>>   I have looked at the docs at source.android.com, and for phones, they only 
>> discuss the Galaxy Nexus.  I would like to make some mods to the current OS 
>> code base and put it on a Galaxy S2.  Is this possible?  Can you suggest web 
>> sites or other docs, of where to begin?
>>
>> Thanks,
>> Paul
>>
>>
>>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: Deadlock in libOpenSLES when end skype call

[Glenn Kasten]

https://android-review.googlesource.com/#/c/105606/

On Thursday, May 29, 2014 1:45:23 AM UTC-7, Katy Ma wrote:
>
> Have you tried the opensles test case 
> under /frameworks/wilhelm/tests/examples/slesTestRecBuffQueue.cpp on kk4.4?
> Becasue I tried this case "slesTest_recBuffQueue" for several times and 
> similar deadlock issue will be reproduced easily. The case will be clocked 
> and cannot be finished.
>
> On Thursday, May 15, 2014 10:47:06 PM UTC+8, Glenn Kasten wrote:
>>
>> Thank you for your report.   We have a similar report here:
>>  https://groups.google.com/forum/#!topic/android-ndk/G7dLKAGGL28
>> I think I might have a fix, but I am looking for a test case.
>> Do you have a test case you can share, that is simpler than Skype?
>>
>> On Tuesday, May 13, 2014 9:58:34 PM UTC-7, Katy Ma wrote:
>>>
>>> When using skype call, sometimes skype call cannot be end if press end 
>>> call button, and such log will appear,
>>>
>>> "W/libOpenSLES( 2355): 
>>> frameworks/wilhelm/src/android/AudioRecorder_to_android.cpp:217: pthread 
>>> 0x62471b80 (tid 2810) sees object 0x66a0d518 was locked by pthread 
>>> 0x5fb4cc90 (tid 2377) at frameworks/wilhelm/src/itf/IObject.c:411"
>>>
>>> I think when end skype call, 
>>>
>>> 1. libOpenSLES to destroy CAudioRecorder(object locked, later will unlock 
>>> only in IObject_deinit after finish destroyed in 3.)
>>> 2. EVENT_MORE_DATA/EVENT_OVERRUN(etc.) happens and skype callback function 
>>> will handle the event with a lock(requires lock in 1.).
>>> 3. After  1.,  ~AudioRecord  will  be  called  during  destroy,it will wait 
>>> for a lock only when mThreadExitedCondition.broadcast() after 
>>> AudioRecordThread returns, however AudioRecordThread is blocked in 
>>> processAudioBuffer when handle EVENT_MORE_DATA/EVENT_OVERRUN(etc.)(requires 
>>> lock in 2.) However 1. cannot be finished if 3. is blocked. 
>>>
>>>
>>> So dead lock happened.
>>>
>>>
>>> It seems that when destroy CAudioRecoder, there's no need to handle the 
>>> event, however it's hard to sync. And handling event with lock may cause 
>>> deadlock when destroy CAudioRecorder.
>>>
>>>
>>> So can we just remove the lock when handling event? Why we need lock here? 
>>>
>>>
>>>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: How to route audio to different sound cards in android

[Glenn Kasten]

Please see one of the example AOSP-supported audio HALs and audio 
configuration files.
For example, device/samsung/manta/audio/* and similar directories for other 
devices.
You should also look at audio_policy.conf in one directory level above.

On Monday, August 25, 2014 6:19:30 AM UTC-7, Puneet B wrote:
>
> HI ALL,
>
> We have custom ALLWINNER A20 board with android. We compiled android 
> source code and booted successfully.
> We have 2 sound card 1.HDMI 2.ANALOG codec both are working fine.
>
> In ubuntu there is an aption to pass sound card number in mplayer and 
> aplay like.
> mplayer -ao alsa:device=hw=0.0 filename
> mplayer -ao alsa:device=hw=1.0 filename
>
>
> Now we want to develop and android apk which will play songs only in HDMI 
> sound card and another apk only 
> through Analog sound card or Is there anyway to pass sound card number as 
> an argument in android.
>
> Kindly give me any hints or link to achieve this.
>
> Regards
> Punith
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: How to add custom player with registerExtensions()@frameworks/av/media/mediaserver/register.cpp

[Glenn Kasten]

Please upload your proposed fix to AOSP, see
https://source.android.com/source/submit-patches.html

On Wednesday, June 25, 2014 10:47:48 PM UTC-7, xia...@marvell.com wrote:
>
> Hi,  
>
> I am from Marvell Semiconductor.
>
> I meet a problem about 
> registerExtensions()@frameworks/av/media/mediaserver/register.cpp, hope 
> that I can get some advice here J
>
>
> In frameworks/av/media/mediaserver/Android.mk
>
>+ifneq ($(BOARD_USE_CUSTOM_MEDIASERVEREXTENSIONS),true)
>
> +include $(CLEAR_VARS)
>
> +LOCAL_SRC_FILES := register.cpp
>
> +LOCAL_MODULE := libregistermsext
>
> +LOCAL_MODULE_TAGS := optional
>
> +include $(BUILD_STATIC_LIBRARY)
>
> +endif
>
> So if we define BOARD_USE_CUSTOM_MEDIASERVEREXTENSIONS := true, we can 
> implement registerExtensions()@frameworks/av/media/mediaserver/register.cpp 
> and load some extensions.
>
>  
>
> Now I have a player called MRVLMediaPlayer(Similar with StageFright 
> player), so I plan to register it into MediaPlayerFactory.
>
> I implement MRVLMediaPlayer as shared library - libmrvl_media_player.so, 
> and it links other shared libraries like libOmxCore.so, ……
>
>  
>
> But here comes the problem: libregistermsext.a is a static library, it 
> can’t load libmrvl_media_player.so without change 
> frameworks/av/media/mediaserver/Android.mk
>
> If mediaserver links libdl.so, we can easily load libmrvl_media_player.so 
> without change frameworks/av/media/mediaserver/Android.mk in this way:
>
> // Add custom players.
>
> void registerExtensions() {
>
>   android::registerCustomPlayers();
>
> }
>
> à
>
> static bool registerCustomPlayers() {
>
> dlopen(“player_mmp.so”, RTLD_NOW);
>
> createFactoryFunc createFactory = (createFactoryFunc) dlsym(handle, 
> "createFactory");
>
> MediaPlayerFactory::IFactory* factory = 
> createFactory((player_type)kLoadablePlayerStart);
>
> MediaPlayerFactory::registerFactory(factory, 
> (player_type)kLoadablePlayerStart);
>
> }
>
> And comes the implementation of player_mmp.so:
>
>   MmpPlayer.cpp:
>
> extern MediaPlayerBase* createMRVLMediaPlayer();
>
> class MmpPlayerFactory : public MediaPlayerFactory::IFactory {
>
> virtual sp createPlayer() {
>
> ALOGD("create MRVLMediaPlayer");
>
> return createMRVLMediaPlayer();
>
> }
>
> }
>
> extern "C" MediaPlayerFactory::IFactory* 
> createFactory(android::player_type playerType) {
>
> return new MmpPlayerFactory(playerType);
>
> }
>
> Android.mk:
>
> LOCAL_SRC_FILES := MmpPlayer.cpp
>
> LOCAL_SHARED_LIBRARIES  := \
>
> libcutils\
>
> libutils \
>
> libmrvl_media_player
>
> LOCAL_MODULE := player_mmp
>
> include $(BUILD_SHARED_LIBRARY)
>
>
> If frameworks/av/media/mediaserver/Android.mk mediaserver already linked 
> libdl.so, the above can be easily done
>
> @@ -25,7 +27,8 @@ LOCAL_SHARED_LIBRARIES := \
>
> libmediaplayerservice \
>
> libutils \
>
> liblog \
>
> -libbinder
>
> +   libbinder \
>
> +   libdl
>
>  
>
>  LOCAL_STATIC_LIBRARIES := \
>
> Libregistermsext
>
>  
>
> Is it possible that Google add libdl.so into mediaserver 
> LOCAL_SHARED_LIBRARIES so that vendors can add their players without modify 
> Android code?
>
> Or do you have any ideas for add customer players which are implemented as 
> shared libraries?
>
>
> Thanks
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: hat is acdb loader and csd client in audio in android

[Glenn Kasten]

It's a proprietary Qualcomm technology,
only used on Android devices that use a Qualcomm SoC.

On Sunday, June 22, 2014 10:40:29 PM UTC-7, Rajkumar Thavti wrote:
>
> Hi ,
>  can any one fully give info on acbd(audio calibration data
> base) in android. i am studying the audio playback and capture flow
> from application to hardware.
>
>   i have digged on it but got to know very less info on that.
>
>   and also about the csd client (circuit switched database) in 
> android.
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: What scenarios lead to creation of a new PlaybackThread?

[Glenn Kasten]

You are welcome!  There are threads in mediaserver, and threads in each 
client app.
I'll start with mediaserver.
This adb shell command will show the pid of mediaserver:
ps mediaserver
Then to see the threads, do 
ps -t pid
The primary output thread is usually named AudioOut_2 or similar.
This should always be present.
The primary output thread may have a companion FastMixer thread, which 
works under its supervision.
The primary output thread may go into idle (standby) when there is no audio 
to be output,
but it usually never exits.
Then there are direct output, offloaded output, and duplicating threads.
These are created and destroyed as needed.
Direct output is used when no mixing is needed, for example for HDMI output.
Offloaded output is for MP3/AAC playback in low-power mode to a DSP, 
without requiring decode to PCM on app processor.
Duplicating output is a kind of fake output, used as a sub-mix for 
Bluetooth A2DP notifications + music.
The number of output threads is mainly limited by the number of available 
output sinks (devices or virtual devices).
Input is similar to output, but there is no concept of a primary input 
thread that is always active.
There are also many other threads in mediaserver, but I'm not experienced 
in that area.

On the client app side, there is one AudioTrack thread per AudioTrack 
object.
It services callback handlers.

I can't answer the processing power question; there is no easy formula that 
I know of.

On Thursday, June 12, 2014 12:05:01 PM UTC-7, Andrei wrote:
>
> I'm trying to find out how the number of playback threads grows under 
> different usage conditions.
>
> I've been following AudioFlinger code, but some things are less apparent 
> than others. So far, Glenn Kasten has been very helpful with his responses, 
> so thanks a ton!
>
> From some debugging messages I've inserted into AudioFlinger, I see that 
> one thread gets created when I play audio using a browser or a media 
> player. This one persists, and I believe never gets destroyed even if I 
> don't play any audio for a while. Then there are other threads that get 
> created and destroyed pretty frequently. Those threads are responsible for 
> system sounds, e.g. button clicks. I believe I've also seen another thread 
> created when I turn on navigation (is this true?). Navigation audio lives 
> alongside media playback and uses "ducking" whenever it needs to play 
> something back. So far, I haven't seen more than three PlaybackThread 
> instances actively processing audio at a given time.
>
> Is there a theoretical or practical limit to how many playback threads can 
> be actively processing audio at once? I'm inserting some audio processing 
> into playback before audio goes out to hardware, and I'd like to know how 
> much processing power my algorithms may need in reality.
>
>
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: Understanding seemingly circular calls in IAudioPolicyService

[Glenn Kasten]

This answer applies to similar binder calls also, with appropriate 
modifications:

The getOutput in IAudioPolicyService.cpp that calls 
remote()->transact(GET_OUTPUT, ...
is the client side stub / marshalling code.

In the same source file IAudioPolicyService.cpp the "case GET_OUTPUT:"
is the server side stub / marshalling code. It pulls out the input 
parameters,
and then invokes the real server getOutput. Upon return, it packages up
the output parameters.

And where is the real server getOutput? It's in AudioPolicy*.cpp


On Monday, June 9, 2014 8:44:55 PM UTC-7, Andrei wrote:
>
> I'm trying to untangle the getOutput call 
> 
>  
> in IAudioPolicyService. When this method is called, data parcels are sent 
> using remote 
> ()->
> transact 
> (
> GET_OUTPUT 
> ,
>  
> data , &
> reply ). 
> The way this works (as I understand it) is as follows. The remote() call 
> returns 
> 
>  
> a reference to an IBinder object. When its transact method 
> 
>  
> is called, it again ends up calling BnAudioPolicyService 
> 
> ::onTransact 
>  
> which 
> called remote()->transact in the first place. So it looks like they just 
> keep calling each other.
>
> I must be missing something. What's the right way to resolve this?
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: Need clarification in interaction between audio tracks, audio mixers and audio playback threads

[Glenn Kasten]

> 1. Each playback thread in AudioFlinger has a mixer buffer, from which 
these threads write to the appropriate sink.
Except for "direct" or "offloaded" threads, where there is no mixing.

> 2. Each mixer thread is a particular kind of playback thread with extra 
capabilities of acting as a "fast mixer" and sending audio directly to 
hardware.
A "fast mixer" is an optional assistant thread that works under the 
supervision of it's parent "normal mixer" thread.

> 3. Each audio track is attached to a playback thread. Several tracks can 
run simultaneously on the same playback thread.
Correct

> 4. There exists an AudioMixer class which also keeps a list of tracks, 
and is responsible for things like downmixing, resampling, etc.
Correct

> 5. It doesn't look like AudioMixer and MixerThread are related things, 
they just both happen to have "mixer" in their names.
They are only distantly related ... MixerThread and FastMixer _use_ an 
AudioMixer object.

> 1. MixerThread derives from PlaybackThread. Is my assessment of their 
differences correct, and if not, why do both exist?
Because there are also PlaybackThreads that aren't MixerThreads ... namely 
direct and offloaded.

> 2. What is the connection between AudioMixer, MixerThread, PlaybackThread 
and AudioTrack?
> (also 3. and 4.)
That's too big for me to answer here right now, sorry.

Sorry I didn't have time to answer all your questions, but I hope that the 
above was at least enough to help you get started.
I encourage adding logs and observing the logs.
Or if you can ask some very precise focused question(s), I might be able to 
help better.
Good luck!


On Monday, June 9, 2014 5:34:50 PM UTC-7, Andrei wrote:
>
> For purposes of this discussion, let's leave audio capture alone, 
> and focus solely on audio playback.
>
> From reading AudioFlinger source and experimenting with OpenSL ES code, 
> here's what I believe happens under the hood:
> 1. Each playback thread in AudioFlinger has a mixer buffer, from which 
> these threads write to the appropriate sink.
> 2. Each mixer thread is a particular kind of playback thread 
> with extra capabilities of acting as a "fast mixer" and sending 
> audio directly to hardware.
> 3. Each audio track is attached to a playback thread. Several tracks 
> can run simultaneously on the same playback thread.
> 4. There exists an AudioMixer class which also keeps a list of tracks, 
> and is responsible for things like downmixing, resampling, etc.
> 5. It doesn't look like AudioMixer and MixerThread are related things, 
> they just both happen to have "mixer" in their names.
>
> Here are four questions I have, all closely related, hopefully it's okay 
> to ask all of them in a single post.
> 1. MixerThread derives from PlaybackThread. Is my assessment of their 
> differences correct, and if not, why do both exist?
> 2. What is the connection between AudioMixer, 
> MixerThread, PlaybackThread and AudioTrack? In particular, when an audio 
> track is playing audio (let's forget about preparation and 
> initialization), when chain of function calls is induced in all of them? 
> Some graphical representation would be very helpful, if it's available.
> 3. How do all of the above keep track of each other? In other words, 
> do playback threads keep track of audio mixers that in turn keep track of 
> audio tracks, etc.? What's the structure of object "ownership"?
> 4. Finally, I see there two interesting variables in the 
> source. PlaybackThread has a variable named mMixBuffer, from which audio 
> is read into the sink. PlaybackThread also has a vector 
> called mActiveTracks, which contains a list of all track objects from 
> which audio should be played. I read through entire Threads.c, and 
> unless I've missed something important, I don't see how audio from 
> active tracks eventually ends up in mix buffer. In fact, I don't see a 
> single method of PlaybackThread which would read data from active tracks 
> or which data to mix buffer. Where does this magic happen?
>
> Hopefully, I'm not asking for an entire book chapter worth of info. If you 
> know of an article that contains some of this information, please share a 
> link.
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: Using init.rc to start and restart a Linux daemon

[Glenn Kasten]

Quality improvements to the documentation would be welcome;
please see http://source.android.com/source/submit-patches.html


On Friday, June 6, 2014 6:38:41 PM UTC-7, trevd wrote:
>
> Hi Bob
>
> Ay there's definitely plenty of room for error. For reference the init 
> "language" is "documented" here 
> https://android.googlesource.com/platform/system/core/+/master/init/readme.txt.
>  
> However it's a mixture of fact and fiction as some of the functionality was 
> never implemented. the "on device-" triggers only ever existed in the mind 
> of author ( although I believe intel eventually implemented it 4 years down 
> the line :\ ). It was this functionality which the hotplug service was 
> developed to implement. 
>
> I can only apologise for "contrived" nature of my code. I was just picking 
> up C and Linux at the time after spending a decade on .Net, so I can 
> definitely say it's not the finest piece of code I've ever hacked together 
> but it did the job. :)
>  
> trevd
>
>
> On Friday, 6 June 2014 18:29:24 UTC+1, rsg wrote:
>
>> Hi trevd,
>>
>> Yeah, you are right.  What I discovered is that I had a faulty Android.mk 
>> file that was driving the build of my daemon, such that it sometimes 
>> worked, but usually didn't.  So many of my changes weren't actually taking 
>> effect!  Then, the hang, which was simply a mistake on my part when 
>> creating the bootable SD Card (don't ask, too embarrassing!), really had me 
>> confused.
>>
>> I sorted those issues out last night, and my code (with DAEMONIZE not 
>> defined) works correctly.
>>
>> Thanks for confirming my understanding, and for the example daemon - 
>> seems the right balance between contrived (for ease in understanding) and 
>> the usual "real-world" (too complicated to understand); it's likely to 
>> serve as a useful reference going forward!
>>
>> Regards,
>> Bob
>>
>>
>> On Friday, June 6, 2014 11:16:03 AM UTC-4, trevd wrote:
>>>
>>> Hi there
>>>
>>> I don't think you need to "daemonize" the process manually as the native 
>>> service infrastructure handles that for you. IIRC you can sit in the loop 
>>> on the Main thread.
>>> Here's an example of a USB Device hotplug listener I wrote a while back 
>>> which ran as a system service.
>>>
>>> https://github.com/trevd/android_external_hotplugd/blob/ics/hotplug.c
>>>
>>> However if you actually do want to daemonize the process you can add 
>>> oneshot to the service declaration which will tell init to only start the 
>>> service once, e.g
>>>
>>>  service rsgd /system/bin/rsgd
>>> oneshot
>>> class main
>>> user system
>>>
>>>
>>> Hope that helps!
>>> trevd
>>>
>>>
>>>
>>> On Wednesday, 4 June 2014 05:11:30 UTC+1, rsg wrote:

 I need to write a Linuxland daemon that talks to our custom hardware. 
  I would like to use the /init process to start, and if necessary, restart 
 it.  I have made this entry into the init..rc file that looks 
 like this:

   service rsgd /system/bin/rsgd
 class main
 user system

 Here is my daemon (just a skeleton now, but it runs):

 #include 
 #include 
 #include 
 #include 
 #include 
 #include 
 #include 
 #include 
 #include 

   #define DAEMONIZE
  

 int main(void)
 {

 #ifdef DAEMONIZE 

   pid_t pid, sid;
   
   /* Fork off the parent process */
   pid = fork();
   if (pid < 0) {
 exit(EXIT_FAILURE);
   }
   /* Exit the parent process. */
   if (pid > 0) {
 exit(EXIT_SUCCESS);
   }
 #endif

  

   /* Change the file mode mask */
   umask(0);
   
 #ifdef DAEMONIZE 

   /* Create a new SID for the child process */
   sid = setsid();
   if (sid < 0) {
 /* Log the failure */
 exit(EXIT_FAILURE);
   }
 #endif

  

  
   /* Change the current working directory */
   if ((chdir("/")) < 0) {
 /* Log the failure */
 exit(EXIT_FAILURE);
   }
   
   /* Close out the standard file descriptors */
   close(STDIN_FILENO);
   close(STDOUT_FILENO);
   close(STDERR_FILENO);
   
   /* Daemon-specific initialization goes here */
   
   /* The Big Loop */
   while (1) {
 /* Do some task here ... */

 usleep(10); /* wait 100 milliseconds */
   }
   exit(EXIT_SUCCESS);
 }


 Nothing fancy.  When I build the system, the daemon gets created 
 properly, and lives in /system/bin, as expected.  When I boot the system, 
 however, /init continually starts my daemon, many times, until the system 
 eventually runs out of memory!

 Is there something my daemon needs to do so /init doesn't think it has 
 died and needs to restart? 

 Well, as I wrote this originally, I had an "Aha!" moment - /init must 
 be acting on the exit of the parent process

[android-porting] Re: Camera on Nexus 5 (Hammerhead)

[Glenn Kasten]

AOSP master is under active development right now, so it is very likely to
have occasional build breaks or regressions.  If you do find the root cause,
please update here. Or even better if you find a fix, please upload a patch 
using the procedure at
http://source.android.com/source/submit-patches.html
AOSP can't accept patches here, either inline or as attachments.

On Friday, June 6, 2014 10:58:17 AM UTC-7, Owain Davies wrote:
>
> Hello porters,
>
> This about an issue I have found with the on the latest master branch aosp 
> built for the Nexus 5 with the camera.
>
> I have today downloaded the latest aosp master branch. I applied the 
> latest proprietary drivers for hammerhead and and built the 
> full_hammerhead_userdebug build.
> It builds and flashes fine. It starts but when I try to use the camera It 
> fails with "Unfortunately, Camera has stopped.". See attachment 
> LaunchCamera-logcat.log.
>
> In summary:
>
> At around line 149, bad things start to happen,
>
> E/mm-camera(  199): mct_stream_metadata_bus_msg:Failed to do buf_done
> F/libc( 3110): system/media/camera/src/camera_metadata.c:497: 
> clone_camera_metadata: assertion "validate_camera_metadata_structure(clone, 
> NULL) == OK" failed
> F/libc( 3110): Fatal signal 6 (SIGABRT), code -6 in tid 3273 
> (cam_stream_proc)
> I/DEBUG   ( 2095): *** *** *** *** *** *** *** *** *** *** *** *** *** *** 
> *** ***
> There then follows a crash report that idicates that the media server 
> crashed and fingers the "/system/bin/mediaserver" as the victim and 
> consequentially all the related services died.
> With the media server dead the Camera application throws a fatal exception 
> and dies.
> There then appear to be many problem in mm_camera running in t PID199,
>
> PID199 in this case is /system/bin/mm-qcamera-daemon and is started as a 
> service by init.
>
> So, I ran the following command to get adb logcat from boot.
> adb reboot ; adb logcat > boot-logcat.log
>
> Output attached, slightly abbreviated. I have noted the following problems:
>
> around line 34:
> E/mm-camera-img(  199): cac_comp_load:679] Error opening CAC library 
> E/mm-camera(  199): module_cac_init:1027] Error rc -6
>
> But I can track down what the CAC library is or what a reutnr code of -6 
> means.
>
> @46:
> D/mm-camera-intf(  186): mm_camera_open: dev name = /dev/video1, cam_idx = 
> 1 
> D/mm-camera-intf(  186): mm_camera_open:failed with I/O error retrying 
> after 20 milli-seconds
>  
> @435: it fails to open the camera with errors in libsensor and mm-camera
>
> Eventually the camera opens @449 but can not get a data stream from the 
> camera @452
>
> It then tries again with the second camera and fails similarly.
>
> I have checkd the camera was working on the stock factory image, and if I 
> build clean from the release tag android-4.4.3-r1.1. So something has 
> happened between then and now. I though it might be the tightening up of 
> the sepolicy, but I changed the kernel command line to start with selinux 
> in permissive mode, also I am not seeing any particularly relevant denials.
>
> Thanks,
>
> Owain
>
> P.S. I don't know if this is the right group for this as the Nexus 5 is 
> already supported, and the problems appear to manifest in a proprietary 
> binary, but these are the same drivers that work fine in 
> android-4.4.3-r1.1, so I think it is some thing that changed in the the 
> open source. I hope somebody can point me in the right direction.
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: AOSP on x86_64

[Glenn Kasten]

see https://groups.google.com/forum/#!topic/android-building/vfWe_VCt4sE

On Wednesday, June 4, 2014 3:34:14 AM UTC-7, Stéphane Konstantaropoulos 
wrote:
>
> Hello,
>
> I noticed there is a target aops-x86_64
>
> What does this support?
>
> Thanks
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: Deadlock in libOpenSLES when end skype call

[Glenn Kasten]

Thank you for your report.   We have a similar report here:
 https://groups.google.com/forum/#!topic/android-ndk/G7dLKAGGL28
I think I might have a fix, but I am looking for a test case.
Do you have a test case you can share, that is simpler than Skype?

On Tuesday, May 13, 2014 9:58:34 PM UTC-7, Katy Ma wrote:
>
> When using skype call, sometimes skype call cannot be end if press end 
> call button, and such log will appear,
>
> "W/libOpenSLES( 2355): 
> frameworks/wilhelm/src/android/AudioRecorder_to_android.cpp:217: pthread 
> 0x62471b80 (tid 2810) sees object 0x66a0d518 was locked by pthread 
> 0x5fb4cc90 (tid 2377) at frameworks/wilhelm/src/itf/IObject.c:411"
>
> I think when end skype call, 
>
> 1. libOpenSLES to destroy CAudioRecorder(object locked, later will unlock 
> only in IObject_deinit after finish destroyed in 3.)
> 2. EVENT_MORE_DATA/EVENT_OVERRUN(etc.) happens and skype callback function 
> will handle the event with a lock(requires lock in 1.).
> 3. After  1.,  ~AudioRecord  will  be  called  during  destroy,it will wait 
> for a lock only when mThreadExitedCondition.broadcast() after 
> AudioRecordThread returns, however AudioRecordThread is blocked in 
> processAudioBuffer when handle EVENT_MORE_DATA/EVENT_OVERRUN(etc.)(requires 
> lock in 2.) However 1. cannot be finished if 3. is blocked. 
>
>
> So dead lock happened.
>
>
> It seems that when destroy CAudioRecoder, there's no need to handle the 
> event, however it's hard to sync. And handling event with lock may cause 
> deadlock when destroy CAudioRecorder.
>
>
> So can we just remove the lock when handling event? Why we need lock here? 
>
>
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: Kitkat: A2DP playback no sound

[Glenn Kasten]

This seems like an uninitialized value, not a valid value.

I suggest that you find a known working reference device
(e.g. Nexus family) running the same OS version, and then
start comparing logs, volumes at various places etc., to
see where the difference first appears in the pipeline.

On Monday, April 14, 2014 4:10:24 PM UTC-7, Uday Gupta wrote:
>
> Hi,
>
> On our development platform on KK, A2DP playback has no sound. Data dump 
> in the A2DP HAL shows all zeros.
>
> Enabling and adding some logs in AudioFlinger.cpp and threads.cpp shows 
> the master volume as -0.02.
>
> Has sometime changed in KK compared to JB and some configuration 
> parameters need to be set to set the master volume to 1.0f.
>
> Thanks
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: OpenCore and stagefright.

[Glenn Kasten]

My memory is that Stagefright framework started coming in around Froyo +/- 
1.
ICS probably still contained bits of the old framework.
You could search through the code as of that release and look for 
references.
I'm not sure what you mean by "supports".

On Thursday, April 10, 2014 10:39:49 PM UTC-7, sithruk sana wrote:
>
>
>
> Hello all,
>
> I would like to know if JellyBean supports Opencore ?,  Does it ?
>
> I think ICS supports both stagefright and opencore right ?
>
> Kindly correct me if i am wrong?
>
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: Getting Sensor information from Audio HAL

[Glenn Kasten]

I'm not sure what kind of sensors you need to  get information from, but
there's an example of monitoring device orientation and rotation in  

frameworks/base/media/java/android/media/AudioService.java.
Search for mMonitorOrientation and mMonitorRotation.
On Wednesday, March 26, 2014 8:07:09 PM UTC-7, Uday Gupta wrote:
>
> Hi,
>
> I am working on some audio algorithm in audio HAL. This audio algorithm 
> needs to get the information from the sensors. What would be the best way 
> to get this information?
>
> 1. Directly call the kernel sensor interface.
> 2. Use the sensor service.
>
> Thanks
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: Issue playing .mxmf file

[Glenn Kasten]

Does this file play correctly on other Android-based devices,
especially Nexus family devices?  If so, please say which device(s)
it plays correctly on, and which device(s) it fails on.

If it does not play correctly on any Android device,
then this is off-topic for android-porting. In that case,
please file a bug here:
   https://code.google.com/p/android/issues/list

Thanks

On Thursday, March 13, 2014 4:05:58 PM UTC-7, Uday Gupta wrote:
>
> hi,
>
> I have issue playing the attached .mxmf file.
>
> Sonivox EAS XMF parser returns EAS_ERROR_FILE_FORMAT.
>
> The file seems to be correct in the beginning. Looks like some issue with 
> meta data information.
>
> Does somebody know about how to fix this?
>
> Thanks
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: Issue with FastMixer while playing short tones

[Glenn Kasten]

Please say which SoC, OEM device name/model, Android release version,
and the audio output HAL configuration: number of HAL buffers, frames per 
buffer,
sample rate in Hz, and frame format (e.g. stereo 16-bit PCM). Also
please include the output of dumpsys media.audio_flinger while you are 
hearing glitches.

On Friday, March 14, 2014 1:31:42 AM UTC-7, Mohan Kumar wrote:
>
> I seeing issues when I use fastmixer for output while I play short Tones 
> by pressing volume button, The output is having extra zeroes inserted 
> between the actual output which makes glitches in the output.
>
> How can we solve this issue?
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[android-porting] Re: Where in the Android OS is the single sink into which audio gets mixed?

[Glenn Kasten]

I was afraid you would mention offloading! :-)
OK, so offloading is yet another way for audio to be played.

So here's the distinction between deep buffer and offloaded tracks:

 - Deep buffer tracks are decoded from MP3, AAC, etc. to PCM on app 
processor
   and then written as PCM to HAL [driver].
   The buffer size is larger than normal mixer's typical 20 milliseconds,
   perhaps on the order 100 to 200 milliseconds or so.
   The key thing is that app processor still needs to wake up several times 
a second,
and must run the software decoder on app processor.
   This does save wakeup & context switch time relative to normal tracks,
but the decode time is the same.  Implementation is mostly portable,
   although it does require device to support multiple concurrent output 
streams
   (recall that FastMixer is also using a stream), so not all devices can 
do it.

 - Offloaded tracks are new for Android 4.4 (KitKat),
and implementation is even more device-specific.  It is enabled on 
Nexus 5.
Offloaded track data is transferred from app processor to HAL/driver
in encoded format (MP3, AAC, etc.).   Decode is then (partially) 
implemented
in hardware, typically by a DSP attached to app processor.
This has the advantage of even fewer app processor wakeups,
and no decode on app processor.  Presumably the DSP is optimized
for decode and so can do it more efficiently than app processor.
Also as the data sent to DSP is in encoded format which is much smaller,
a given buffer size can translate to longer elapsed time per buffer,
on the order of seconds.
The principle downside to offloading is that it requires a DSP,
and the greater complexity of implementation.

To read more (either documents or source) about deep buffers,
   grep -r AUDIO_OUTPUT_FLAG_DEEP_BUFFER frameworks/av/*
   grep -r AUDIO_OUTPUT_FLAG_COMPRESS_OFFLOAD frameworks/av/*
These grep results will give you the starting points for your code reading.
Then continue following the code from there. Adding logs is always helpful! 
:-)

On Thursday, March 6, 2014 12:08:53 PM UTC-8, AudioLinger wrote:
>
> Hi Glenn,
>
> Thanks for your reply, it's very helpful and confirms most of the things 
> I've discovered in my investigation.
>
> As a short followup question, where can I read more (either documents or 
> source) about deep buffers? I enabled logging and added some custom log 
> messages in AudioFlinger::PlaybackThread::threadLoop_write(), and I see 
> that it writes to two different sinks depending on the application. One of 
> them (the "normal sink") writes frames of audio depending on how I 
> configure AudioFlinger, and the other one writes to an AudioStreamOut (HAL 
> object) directly. Whenever the latter happens, I also see messages about 
> offloading printed. Is this in any way related to deep buffers or 
> fast/normal mixer selection?
>
> On Thursday, March 6, 2014 7:10:13 AM UTC-8, Glenn Kasten wrote:
>>
>> See attached diagram "Audio playback architecture.pdf".
>> This shows 3 major paths that audio can be played out, 
>> however these are not the only paths.
>>
>> 1. Low latency tracks are mixed directly by fast mixer.
>> They have attenuation applied, but no resampling or app processor effects.
>>
>> 2. Normal latency tracks are mixed by normal mixer,
>> and in addition to attenuation can have optional resampling
>> or app processor effects applied. Both of the latter can use
>> significant CPU time, and may be bursty in CPU consumption,
>> thus this is why they are limited to normal tracks.
>> The output of normal mixer is a single fast track (via a memory pipe),
>> which then is treated as (1) above by fast mixer.
>>
>> 3. Deep buffer tracks, used for music playback with screen off,
>> go through a similar path as #2 but without the fast mixer part.
>> After the mix is done, it is written directly to HAL.
>>
>> There are other paths but they are less relevant to your question.
>>
>> So to answer your question: no there is no single point.
>> If you're applying CPU-intensive processing, I would recommed
>> adding them to the normal mixer path used for #2 and #3.
>> Avoid adding them to fast mixer as this will likely cause
>> performance problems for lower latency tracks.
>>
>>
>> On Wednesday, March 5, 2014 6:20:02 PM UTC-8, AudioLinger wrote:
>>>
>>> Hi all,
>>>
>>> I've been reading through AudioFlinger and audio hardware code looking 
>>> for the place where all audio from all tracks and sessions comes together. 
>>> My initial guess was the audio mixer, but there are now two audio mixers 
>>> (the normal one and the FastMixer). When lo

[android-porting] Re: Where in the Android OS is the single sink into which audio gets mixed?

[Glenn Kasten]

See attached diagram "Audio playback architecture.pdf".
This shows 3 major paths that audio can be played out, 
however these are not the only paths.

1. Low latency tracks are mixed directly by fast mixer.
They have attenuation applied, but no resampling or app processor effects.

2. Normal latency tracks are mixed by normal mixer,
and in addition to attenuation can have optional resampling
or app processor effects applied. Both of the latter can use
significant CPU time, and may be bursty in CPU consumption,
thus this is why they are limited to normal tracks.
The output of normal mixer is a single fast track (via a memory pipe),
which then is treated as (1) above by fast mixer.

3. Deep buffer tracks, used for music playback with screen off,
go through a similar path as #2 but without the fast mixer part.
After the mix is done, it is written directly to HAL.

There are other paths but they are less relevant to your question.

So to answer your question: no there is no single point.
If you're applying CPU-intensive processing, I would recommed
adding them to the normal mixer path used for #2 and #3.
Avoid adding them to fast mixer as this will likely cause
performance problems for lower latency tracks.


On Wednesday, March 5, 2014 6:20:02 PM UTC-8, AudioLinger wrote:
>
> Hi all,
>
> I've been reading through AudioFlinger and audio hardware code looking for 
> the place where all audio from all tracks and sessions comes together. My 
> initial guess was the audio mixer, but there are now two audio mixers (the 
> normal one and the FastMixer). When looking at the ssize_t AudioFlinger::
> PlaybackThread::threadLoop_write() method inside 
> frameworks/av/services/audioflinger/Threads.cpp, depending on existence of 
> a "normal sink" we either process audio through a mixer or, if I understand 
> it correctly, send it directly to the hardware to take care of. My goal is 
> to be able to process all audio (except phone call and other such special 
> things) that the device outputs. The above mentioned method was my best 
> guess, but even at that point it splits into different mixing strategies.
>
> Any pointers?
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Audio playback architecture.pdf
Description: Adobe PDF document

[android-porting] Re: Possible audio resampling issue in 4.3

[Glenn Kasten]

Sorry I won't be able to answer all of your questions, but I'll try to 
respond to some of them:

> How do I set it?

See this article http://source.android.com/devices/audio_src.html
section "Resampler implementations", last paragraph.

> What's the performance impact for choosing a high-quality resampler?

It will use more CPU cycles and thus more power, but the exact amount 
depends
on a lot of factors such the exact device, SoC set, etc.  You could measure
with clock_gettime or a battery meter, but I suspect that the difference 
would
not be easily noticeable for a single conversion stream ...  it would 
probably take multiple streams to see a difference.  But that's just a 
guess.

> is it affecting the playback latency?

Resampling is not supported for fast tracks, so in that sense
all tracks with resampling are by definition on the higher latency path.
Between resampler implementations, there is a very slight
difference in algorithmic delay due to the filters, but I think
that's minor on the order of 10s of samples.

On Tuesday, February 25, 2014 8:48:26 PM UTC-8, Naaman Sittsamer wrote:
>
> Thanks Glenn.
> So for my needs do you see this fix fine (removing the "else" section) ?
> What resampler do you recommend to use in such cases (AudioResamplerOrder1 
> / AudioResamplerCubic / AudioResamplerSinc)? How do I set it? What's the 
> performance impact for choosing a high-quality resampler? is it affecting 
> the playback latency?
>
> Thanks,
> Naaman
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-porting] Re: Possible audio resampling issue in 4.3

[Glenn Kasten]

Thanks for reporting this issue.
Android supports a variety of resampler implementations.
At least one of the implementations is suitable for higher-quality music 
playback,
and is used in special common use cases such as 44.1 -> 48 and vice-versa.
But the default fall-back implementation, used for non-special cases, is 
"linear interpolation".
Linear resampling is quite fast but also low quality.
The implementation of linear resampling used here has a further limitation 
that it does not support resampling by arbitrary ratios.
I'm surprised that you were previously able to resample by larger ratios.
Perhaps a different implementation was being used, or maybe the ratio check
was too aggressive.  In any case, I'm glad to hear that you were able to 
workaround this.

Looking forward, we recognize that the default fallback resampler choice of 
"linear"
was perhaps a reasonable tradeoff in the days of slow processors,
but is unnecessarily optimized for speed on current processors.
We are reviewing our suite of resamplers, and hope to improve the
quality and power consumption tradeoffs.
We also want to allow a wider range of ratios.
I can't commit to a date or version for these improvements.

On Tuesday, February 25, 2014 1:06:44 PM UTC-8, Naaman Sittsamer wrote:
>
> Hi,
> I have a system where the audio hardware supports 16KHz.
> I've moved from Android 4.2.2 to 4.3 and now it seems there's no 
> resampling. If I play 44.1KHz media (e.g. music, ringtones) it results with 
> slow audio.
> If I play 16KHz file it sounds good. On the previous release the 
> resampling was fine (done by audioflinger).
>
> After code inspection, I found a fix for this issue, 
> in frameworks/av/services/audioflinger/Threads.cpp - 
> MixerThread::prepareTracks_l() :
> // limit track sample rate to 2 x output sample rate, which changes at 
> re-configuration
> uint32_t maxSampleRate = mSampleRate * 2;
> uint32_t reqSampleRate = track->mServerProxy->getSampleRate();
> if (reqSampleRate == 0) {
>reqSampleRate = mSampleRate;
> } else if (reqSampleRate > maxSampleRate) {
>reqSampleRate = maxSampleRate;
> } 
> mAudioMixer->setParameter(
>   name,
>   AudioMixer::RESAMPLE,
>   AudioMixer::SAMPLE_RATE,
>   (void *)reqSampleRate);
>
> Since my HW works with 16KHz then all the 44.1KHz media is handled as 
> 32KHz, hence it sounds slowly. 
> Is there a reason for this logic? audio quality limitation?
> By removing the "else" part resampling works fine.
> Is it a bug?
> In 4.2.2 this logic is missing and there're no resampling issues.
>
> Thanks,
> Naaman
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-porting] updated audio porting documentation

[Glenn Kasten]

The audio section of the device porting documentation 
at http://source.android.com/devices/audio.html
was updated recently.  New topics include sample rate conversion, and audio 
debugging tips and tricks.
In addition, if you would like to contribute to the porting docs for audio 
or any other area, please see today's post at android-contrib:
  https://groups.google.com/forum/#!topic/android-contrib/U98QmzoRlCw

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-porting] announcing android-64 group (cross-post)

[Glenn Kasten]

There is a new discussion group for those actively porting the Android 
platform and/or tools to 64-bit architectures:
  https://groups.google.com/forum/#!forum/android-64
It is a non-domain group, and there should be no posting of confidential 
information.
However, it is members-only, with the membership criteria being 
approximately
   "Are you actively porting Android platform and/or tools to 64-bit 
architectures?"
It is not for discussion of 64-bit apps at this time.

This is a good time to review the scope of android-porting: 
  porting vanilla AOSP distribution to a non-AOSP-supported platform
It's not for discussion of downstream distributions,
modifications to the platform other than porting, or app development.

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-porting] Re: Inheriting MediaPlayer.cpp class to implement own methods

[Glenn Kasten]

MediaPlayer.cpp is part of the platform, and not intended for direct usage
from application via NDK.   I suggest you first learn how to build the 
platform "as is"
from source for some appropriate reference device, then start making
small changes as you get more familiar with the code.

On Wednesday, February 5, 2014 6:32:11 PM UTC-8, Mayank Agarwal wrote:
>
> Hi,
>
> How can i inherit Android MediaPlayer.cpp class to implement my own 
> methods.
> Also i want to use hardware decoder omx il component instead of 
> omx.google.h264.decoder.
>
> How do i go about changing the code in .cpp files using android ndk.
> Do i have to load all media_lib.so and other dependabe iso's in java file
> before i can make any changes in cpp code.
> Also should i have to include header files.
> Is there any framework or method which allows us to inherit android .cpp 
> file
> and implement our own methods anactions.
>
> Regards
> Mayank
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-porting] Re: build alsa libraries - android 4.0.3 for msm8660_surf

[Glenn Kasten]

I don't know the answer to your specific question,
but I want to share a tip that will help answer questions like this ...
I use the "mgrep" shell function, which is defined by ". build/envsetup".
Go to the top of your tree, then type "mgrep string" and it will
find anywhere that string appears in the makefiles.
In this case, the ".default" and ".so" parts might be constructed at 
build-time,
so I would do an "mgrep alsa" instead.

On Monday, January 20, 2014 5:51:50 AM UTC-8, fasal rahman wrote:
>
> Hi,
>   I was trying to build alsa library  (alsa.default.so ) for the device 
> msm8660_surf, but the module is not  getting built. I tried building the 
> whole system by executing "Make" command from the project root directory, 
> but i couldn't find the library (alsa.default.so) in the new system 
> image. I also tried with "mm" command from "hardware/qcom/alsa_sound/" and 
> it  shows "nothing to be done for all_modules". 
>
>
> I  followed the followin steps to buidl msm8660_surf.
>
> 1)source build/envsetup.sh 
> 2) choosecombo 1 msm8660_surf eng
> 3) Make 
>
> Can  any one help me ?
>
> Thanks a lot.
> Fasal
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-porting] Re: Android based on linux 3.10 kernel

[Glenn Kasten]

android-porting is a technical forum for porting the generic AOSP 
distribution to non-AOSP-supported targets.
This thread is starting to veer into an area where further discussion would 
be off-topic.
Please move follow-up discussion to another forum, perhaps android-kernel.
Thanks!


On Wednesday, January 15, 2014 10:25:06 AM UTC-8, Subodh Nijsure wrote:
>
>
> Google is in powerful position to nudge the SOC vendors to push their code 
> changes to linux-arm, rather than allowing push to  android.googlesource 
> that gives SOC vendors way to circumvent going the linux-arm way?
>
> -Subodh
>
> On Tuesday, January 14, 2014 7:29:51 AM UTC-8, Glenn Kasten wrote:
>>
>> Generally speaking, Android user mode is not tied to a particular version 
>> of Linux kernel.
>>
>> Each device project picks a kernel that is well-suited to the device and 
>> has been validated.
>> Usually these kernels come from an SoC vendor that has ported generic 
>> upstream kernel to their SoC.
>>
>> For example, if you go to https://android.googlesource.com/ and scroll 
>> down to
>> kernel/ section, you'll see a number of separate kernel git projects for 
>> several SoCs.
>> You'll see that the upstream kernel versions from which these are derived 
>> vary: 3.4, 3.1, 3.0, etc.
>>
>> So far it has not been feasible to merge all these kernel git projects 
>> from various SoCs into
>> a single git project, for various technical and administrative reasons.
>>
>> Regarding your question about 3.10, the presence of a particular branch
>> does not indicate any commitment to support that version on any specific 
>> device.
>>
>> On Monday, January 13, 2014 5:41:23 PM UTC-8, cchh wrote:
>>>
>>> I saw the Google have 3.10 kernel branch in 
>>> https://android.googlesource.com/kernel/common/. But I dont notice 
>>> there are any gits been updated to make them work with 3.10 kernel. At 
>>> least, the bionic.git need to be updated to include those 3.10 kernel 
>>> header. Does anyone porting the android into 3.10 kernel or even higher 
>>> version? Or what is the plan for Google on 3.10 kernel?
>>>
>>> BRs
>>> Guoyin Chen
>>>
>>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-porting] Re: Android based on linux 3.10 kernel

[Glenn Kasten]

Generally speaking, Android user mode is not tied to a particular version 
of Linux kernel.

Each device project picks a kernel that is well-suited to the device and 
has been validated.
Usually these kernels come from an SoC vendor that has ported generic 
upstream kernel to their SoC.

For example, if you go to https://android.googlesource.com/ and scroll down 
to
kernel/ section, you'll see a number of separate kernel git projects for 
several SoCs.
You'll see that the upstream kernel versions from which these are derived 
vary: 3.4, 3.1, 3.0, etc.

So far it has not been feasible to merge all these kernel git projects from 
various SoCs into
a single git project, for various technical and administrative reasons.

Regarding your question about 3.10, the presence of a particular branch
does not indicate any commitment to support that version on any specific 
device.

On Monday, January 13, 2014 5:41:23 PM UTC-8, cchh wrote:
>
> I saw the Google have 3.10 kernel branch in 
> https://android.googlesource.com/kernel/common/. But I dont notice there 
> are any gits been updated to make them work with 3.10 kernel. At least, the 
> bionic.git need to be updated to include those 3.10 kernel header. Does 
> anyone porting the android into 3.10 kernel or even higher version? Or what 
> is the plan for Google on 3.10 kernel?
>
> BRs
> Guoyin Chen
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-porting] Re: FLAC decoder/Parser in Android Kitkat takes up too much CPU

[Glenn Kasten]

The clang -ftrapv option is not currently implemented efficiently for the 
type of integer computation-intensive code used in FLAC inner loops.
The code generated for -ftrapv option doesn't yet take advantage of the ARM 
architecture's "V" (overflow) condition code bit.

On Thursday, January 9, 2014 3:42:45 PM UTC-8, Uday Gupta wrote:
>
> Thanks.
>
> I actually made the same change after I posted the query and the stutters 
> went away. Looks like the clang compiler is was inefficient compared to gcc 
> or is it that compiler options are not getting passed to clang?
>
> On Thursday, January 9, 2014 3:06:08 PM UTC-8, Glenn Kasten wrote:
>>
>> See https://code.google.com/p/android/issues/detail?id=62562
>> comment #23 Nov 25, 2013
>> and the AOSP CL that it links to:
>> https://android-review.googlesource.com/#/c/70749/
>>
>> On Thursday, January 9, 2014 2:43:38 PM UTC-8, Uday Gupta wrote:
>>>
>>> Hi,
>>>
>>> Has anybody seen that FLAC decoder/Parser in Android Kitkat is taking up 
>>> too much CPU.
>>>
>>> For example to get 4096 frames it can take anywhere from 90 to 150 msec 
>>> on our platform.
>>>
>>> Only change between JB and KK seems to be in Android.mk. KK Android.mk 
>>> adds
>>>
>>> LOCAL_CLANG := true
>>> LOCAL_CFLAGS += -ftrapv
>>>
>>> If I remove the above changes, then the time taken is consistently less 
>>> than or equal to ~10 msec.
>>>
>>> Does anybody know what this new LOCAL_CLANG option is for.
>>>
>>> Thanks
>>>
>>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-porting] Re: FLAC decoder/Parser in Android Kitkat takes up too much CPU

[Glenn Kasten]

See https://code.google.com/p/android/issues/detail?id=62562
comment #23 Nov 25, 2013
and the AOSP CL that it links to:
https://android-review.googlesource.com/#/c/70749/

On Thursday, January 9, 2014 2:43:38 PM UTC-8, Uday Gupta wrote:
>
> Hi,
>
> Has anybody seen that FLAC decoder/Parser in Android Kitkat is taking up 
> too much CPU.
>
> For example to get 4096 frames it can take anywhere from 90 to 150 msec on 
> our platform.
>
> Only change between JB and KK seems to be in Android.mk. KK Android.mk adds
>
> LOCAL_CLANG := true
> LOCAL_CFLAGS += -ftrapv
>
> If I remove the above changes, then the time taken is consistently less 
> than or equal to ~10 msec.
>
> Does anybody know what this new LOCAL_CLANG option is for.
>
> Thanks
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-porting] Re: How are users and groups created

[Glenn Kasten]

see system/core/include/private/android_filesystem_config.h

On Wednesday, December 25, 2013 10:48:26 AM UTC-8, ramon...@tandemg.com 
wrote:
>
> I've written a daemon that I want to run on boot with init.rc
> As I see, for each process, init.rc defines a group and a user for 
> security reasons.
> How do I create a user and a group for my daemon. Is it created 
> automatically once I define a new service with new user/group in init.rc ?
>
> Thanks.
> Ramon
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-porting] Re: Full documentation for init process.

[Glenn Kasten]

As you have found, the internal documentation is sometimes out-of-date.
In cases like this, the authoritative reference is the source code
in system/core/init/

A general web search for this topic finds a number
of articles on this subject.  I can't vouch for the accuracy of them all,
but some of them might be helpful to you.

If you would like to help improve the documentation, please see
http://source.android.com/source/life-of-a-patch.html

On Thursday, December 12, 2013 11:41:10 PM UTC-8, jui...@gmail.com wrote:
>
> Hi,
> Because I was digging sources and Internet for long time with this topic 
> and didn't find some full documentation for this I dare to ask someone here.
> I'm having some troubles with porting Android to some new device so that's 
> why I choose this group.
>
> During the study of init.rc doc (
> https://android.googlesource.com/platform/system/core/+/master/init/readme.txt)
>  
> I had feeling that no one care about proper documentation.
> Let see some example:
> In readme.txt is written:
> "Actions and Services implicitly declare a new section. All commands
>
> or options belong to the section most recently declared.  Commands
> or options before the first section are ignored."
>
>
> Then I look into example file (from: 
> https://android.googlesource.com/platform/system/core/+/master/rootdir/init.rc)
>  and see, that firs command is the "include" but it is command (placed in 
> section commands in readme.txt) so it should be ignored. Why is not ignored? 
> Why is not proper described? What happen if I include file which is on 
> partition which isn't mounted at beginning?
>
>
> Then I started looking closer and deeper and here is another example of lack 
> of lack of consistency: Triggers.
>
> readme.txt:
>
> "Actions take the form of:
>
> on 
> 
>
>  ...
>
>
> Triggers
>
>...
>
> boot
>
>...
>
> =
>
>...
>
> device-added-
> device-removed-
>
>...
>
> service-exited-
>
>..."
>
>
> So what is that in example init.rc like:
>
> on early-init
>
> on init
>
> on fs
>
> on post-fs
>
>
> There is no documentation for this (even "do not touch this sections"), no 
> definition in keywords.h or init_parser.c after digging more finally I have 
> it! In file init.c function main there is section of parsing those "Triggers" 
> but when this is triggered? Which goes first? How init recognizing that now 
> is "init" part of process, or "fs".
>
>
> Then looking closer I see some another crucial label for init process called: 
> "charger". Where it is came from? Why some boot has "charger" option. When?
>
> Why this is not documented if this is important part of init process?
>
>
> So is there any real, I mean REAL documentation for whole Android init 
> process?
> Because this what is provided by AOSP is really poorly written. To not say 
> "slovenly".
>
> I will be really thankful for giving me some ideas and "breadcrumbs" for 
> understanding whole booting process in init part as well as what I should 
> care most with porting Android to new device.
>
> Thanks
> Kamil
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-porting] Re: Question about Android OpenMAX IL API upgrade

[Glenn Kasten]

There is still no change as of Android 4.4,
and the Android media team does not typically publicly pre-announce such 
changes.

On Thursday, December 12, 2013 8:36:04 PM UTC-8, yoon jeesoo wrote:
>
> Hi googles.
>
> this question has been not updated since 2012. 
> Do you still have no plan to upgrade OpenMAX IL API 1.2 version?
>
>
> Best Regards.
> Jeesoo
>
> 2012년 8월 14일 화요일 오전 1시 13분 34초 UTC+9, Glenn Kasten 님의 말:
>>
>> The Android media team does not usually pre-announce such things.
>>
>> On Thursday, August 9, 2012 11:11:39 PM UTC-7, Wen AnJun wrote:
>>>
>>> Hi, googles,
>>>  The latest version of OpenMAX IL is 1.2, but in Android 4.1.1 
>>> JellyBean,  the OpenMax IL is still 1.1.2.   Is there any plan to upgrade 
>>> the OpenMAX IL API in the coming Android AOSP.  ? 
>>>
>>> Best Regards.
>>> Anjun
>>>
>>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-porting] Re: Join android wilhelm project

[Glenn Kasten]

frameworks/wilhelm is the pathname of the git repository for 2 APIs:
 - Android native audio based on OpenSL ES
 - Android native media based on OpenMAX AL

OpenSL ES is recommended for lower-latency audio output.
For audio input and normal latency audio output, I recommend
android.media.AudioRecord and android.media.AudioTrack respectively.

Regarding OpenMAX AL, please see my 2013/11/20 post at
"OpenMAX AL Player"
https://groups.google.com/forum/#!topic/android-ndk/XzJ_vOGiGPo

You mentioned you want to join the project.
If you want to use the API as a developer, there is no need to join 
anything.

If you want to contribute patches (such as bug fixes etc.)
please see http://source.android.com/source/submit-patches.html

For very small bug fixes, you can simply confirm there is a bug at the
public issue tracker then upload your patch to AOSP.
For anything more significant, I recommend first discussing
your proposal on either android-contrib or android-ndk groups first,
make sure there is consensus on it, and then upload the patch.
A series of smaller patches is preferred over one large patch.

http://source.android.com/source/report-bugs.html
https://groups.google.com/forum/#!forum/android-contrib
https://groups.google.com/forum/#!forum/android-ndk



On Tuesday, December 10, 2013 6:11:20 PM UTC-8, Mayank Agarwal wrote:
>
>
> Hi,
>
> I would like to join android wilhelm project.Any pointers on that.
>  
> I would like to understand how OpenMax al processes audio/video data 
> before sending it down to hw/soc
>
> Regards,
> Mayank
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-porting] Re: Android makefiles(.mk) documentation.

[Glenn Kasten]

The high-level "how to" guide is 
at http://source.android.com/source/building.html
but this doesn't discuss the details of how it works inside, or how to 
write your own makefiles.

I personally prefer to learn by copy and paste from existing makefiles,
but if you want to really study it from the ground up, see build/core/*.mk
There's actually a lot of comments in most of the .mk files there.



On Wednesday, December 4, 2013 7:41:30 PM UTC-8, manty kuma wrote:
>
> Hi,
>
> I am porting libraries from one architecture to other architecture. I am 
> new to makefiles and am wasting a lot of time by referring to other 
> makefiles to understand how i should change them,
>
> I want to learn about android makefiles. How to write and modify them. 
> Could you please guide me to the official android documentation related to 
> this? Also Other helping resources would be of great help.
>
> Best Regards,
> Sandeep Kumar
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-porting] Re: TLV320AIC on Android 4.3

[Glenn Kasten]

This log means the client (app) was unable to find free space in the buffer 
shared with AudioFlinger,
in order to fill it with more output data.   It could mean that the 
AudioFlinger playback thread is stalled.
For example, a call to HAL write is blocking and not returning.  I would 
add logs inside of your audio HAL
write, and AudioFlinger playback thread.

On Tuesday, November 19, 2013 3:37:28 PM UTC-8, Adam Lee wrote:
>
> Good day everybody :) 
> I have been working on porting Android 4.3 to one of my boards - Gumstix 
> Pepper. This board is using TI's AM335x and TLV320AIC. This codec is the 
> same codec found in Beaglebone Black's audio cape. 
>
> A lot of things are working really well, including video acceleration, 
> wifi, usb and etc, except for audio. 
> Soon after boot, audio stops working entirely. It seems to work for a few 
> minutes, but definitely stops working after the first sound/audio event 
> (such as playing mp3 through the music player). 
>
> W/AudioTrack(  321): obtainBuffer timed out (is the CPU pegged?) 
>> 0x5910cba0 name=0x2 user=4000, server=
>> W/AudioTrack(  321): obtainBuffer timed out (is the CPU pegged?) 
>> 0x5910cba0 name=0x2 user=4000, server=
>
>
> The device directory is here . And i 
> am pretty confident the Kernel is good. The kernel works well with a custom 
> Linux distribution root file system. 
>
> Any insight into this problem will be much appreciated!
>
> Adam 
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-porting] Re: Tegra-2 - KitKat

[Glenn Kasten]

See http://source.android.com/source/building-devices.html
section "Picking and building the configuration that matches a device"
and search for your device's codename (in this case "wingray").
The column "Branch" shows the most recent branch with Android support for 
that device.

Also see http://source.android.com/source/building-kernels.html
table "Figuring out which kernel to build"
although that does not show a branch.

On Monday, November 11, 2013 6:46:28 AM UTC-8, Giveen wrote:
>
> Does AOSP still have support for Tegra2 SoC?
>
> I know that CM dropped support for it, and I need to know if I need to go 
> back to AOSP for development.
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-porting] Re: why volatile for mReachedEOS...

[Glenn Kasten]

Most 'volatile' in the code are historical, as volatile is no longer 
considered best coding practice since the semantics of volatile are unclear 
for SMP and don't deal with load/acquire.
Nowadays we usually use the atomic library routines or intrinsics, or 
mutexes.
My experience is that is relying on volatile for correct behavior is often 
suspect on SMP.
I'm not familiar with this module AMRWriter in particular, so I can't 
comment on whether it is correct or not.

On Friday, November 1, 2013 12:24:46 PM UTC-7, baskar_IEL wrote:
>
> Hi All,
>
> I was going through the AMRWriter.h file , the variable mReachedEOS is
>
> volatile bool mReachedEOS - from JB version.  and 
>
> bool mReachedEOS - in GingerBread Version.
>
> Please let me know what difference it will make by qualifying the variable 
> to "Volatile".
>
>
> Regards,
> BT.
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-porting] Re: Audio Codec Offload support in Kitkat

[Glenn Kasten]

After syncing AOSP branch android-4.4_r1, look at these projects and files:
  hardware/libhardware/include/hardware/audio*.h
  hardware/qcom/audio/
  device/lge/hammerhead/audio*.conf
Do a git log on these, and look especially at CLs with the words "offload" 
or "tunnel".
I think the new APIs are intended for the offload stream only.

On Saturday, November 2, 2013 1:29:49 PM UTC-7, Uday Gupta wrote:
>
> Hi,
>
> Is there an example of sample code and audio_policy.xml for 
> supporting Audio Codec Offload support in Kitkat.
>
> Also can the newly added API's for audio_stream_out like pause, resume 
> drain and flush be used by other HALS like primary or deep buffer.
>
> Thanks.
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-porting] re-designed source.android.com porting section

[Glenn Kasten]

The source.android.com site has just been updated:
   http://source.android.com/devices/index.html
This includes a newly redesigned organization of the porting section,
and new content in these areas:
low RAM, camera, security, storage, and audio terminology.
Please take a look and let us know what you think.
We're especially interested in missing information that you wanted added,
bad links, formatting problems, etc.  Feel free to reply here with your 
comments.

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-porting] Re: Android failing to finish booting (hang at spash screen). Potential problem adding shared library to AudioFlinger

[Glenn Kasten]

I don't see the logs from init when it tries to fork/exec mediaserver.
That step must be failing, probably because it doesn't find the .so,
but I don't see the log.  Maybe it's scrolled off, or is in another log?
(dmesg is usually for kernel, but it's worth taking a look there)

See system/core/rootdir/init.rc and search for "service media 
/system/bin/mediaserver".
That's what tells init to fork/exec mediaserver, which contains 
AudioFlinger.

Besides looking at more and earlier logs, you could instrument the .so 
dynamic loader
in bionic.   Another suggestion is to copy your .so to /system/lib/ as a 
test.

On Wednesday, October 30, 2013 12:52:30 PM UTC-7, Kieran Cox wrote:
>
> Hello,
>
> First, thanks in advance for taking a look and any help you can offer.
>
> I have made some modifications for AudioFlinger that have the dependency 
> of a prebuilt external library. Initially I linked the library in as a 
> static library. To facilitate this I added a new folder for my library at 
> "androidRoot/external/libaudiodsp". Inside that directory I dropped in the 
> *.so and *.a library files. The necessary include files are also added in a 
> sub-directory "androidRoot/external/libaudiodsp/include"
>
> I also added a brief Android.mk file:
> 
> LOCAL_PATH:= $(call my-dir)
> include $(CLEAR_VARS)
>
> LOCAL_PREBUILT_LIBS := libaudiodsp.a
> #LOCAL_PREBUILT_LIBS := libaudiodsp.so
>
> include $(BUILD_MULTI_PREBUILT)
> 
>
> Then I added the new external library to the "build/core/pathmap.mk" 
> file. (see attached)
>
> After making two small changes to the AudioFlinger Android.mk file, namely:
> LOCAL_C_INCLUDES := \
> $(call include-path-for, audio-effects) \
> $(call include-path-for, audio-utils) \
> $(call include-path-for, libaudiodsp)
>
> LOCAL_STATIC_LIBRARIES := \
> libscheduling_policy \
> libcpustats \
> libmedia_helper \
> libaudiodsp
>
> Viola, everything builds, and runs as expected.
>
> Now I went to try to use the shared library. Which requires me commenting 
> out the *.a file and commenting in the *.so in the 
> external/libaudiodsp/Android.mk file.  I  removed "libaudiodsp" from 
> the LOCAL_STATIC_LIBRARIES tag in the AudioFlinger Android.mk file.  I then 
> added it to the shared library tag, ie:
> LOCAL_SHARED_LIBRARIES := \
> libaudioutils \
> libcommon_time_client \
> libcutils \
> libutils \
> libbinder \
> libmedia \
> libmedia_native \
> libnbaio \
> libhardware \
> libhardware_legacy \
> libeffects \
> libdl \
> libpowermanager \
> libaudiodsp
>
> Everything then builds/compiles just fine. However, the system now will 
> not boot! It's stuck in the initial Android bootup screen. The logs show 
> issues with AudioPolicyService and Media player service (see attached 
> crashlog.txt):
>
> W/AudioSystem(  718): AudioPolicyService not published, waiting...
> I/ServiceManager(  718): Waiting for service media.player...
> I/ServiceManager(  718): Waiting for service media.audio_policy...
> I/ServiceManager(  718): Waiting for service media.player...
> I/ServiceManager(  718): Waiting for service media.audio_policy...
> W/IMediaDeathNotifier(  718): Media player service not published, 
> waiting...
> I/ServiceManager(  718): Waiting for service media.audio_policy...
> I/ServiceManager(  718): Waiting for service media.player...
> I/ServiceManager(  718): Waiting for service media.audio_policy...
> I/ServiceManager(  718): Waiting for service media.player...
> I/ServiceManager(  718): Waiting for service media.audio_policy...
>
>
> I've read quite a few posts about adding shared libraries, even rebuilt 
> the *.so with the Android toolkit and nothing seems to help thus far. 
>
> I tried changing the external/libaudiodsp/Android.mk file to the 
> following, but it made no difference:
> LOCAL_PATH:= $(call my-dir)
> include $(CLEAR_VARS)
> LOCAL_MODULE := libaudiodsp
> LOCAL_SRC_FILES := libaudiodsp.so
> LOCAL_MODULE_TAGS := optional
> LOCAL_MODULE_CLASS := SHARED_LIBRARIES
> LOCAL_MODULE_SUFFIX := .so
> include $(BUILD_PREBUILT)
>
> An attempt was made to add "LOCAL_REQUIRED_MODULES := libaudiodsp" to the 
> AudioFlinger Android.mk file. Again this had no effect, system hangs in the 
> same manner.
>
> I tried making a "shared static" library. In which the library itself was 
> shared, but all of it's dependencies were linked into the *.so statically. 
> This change again had no effect on the crash.
> Example:
> $CPP -shared -static -o libaudiodsp.so \
> -Wl,--whole-archive libaudiodsp.a \
> -Wl,--no-whole-archive
>
> Unfortunately only solution that works is retreating back to the static 
> library configuration. :-(
>
> Since the only thing that changed was converting the static library to a 
> shared library, it would seem that the new dependency on the shared library 
> is not being properly propagated through the build system (also not  being 
> checked/verified as a dependency) and is thus causing a c

[android-porting] Re: how to port wpa_cli

[Glenn Kasten]

I don't know anything about wpa, so my answer is not specific to wpa or the 
problem in first paragraph.  This is only about the second paragraph.

When I need to run something as non-root from adb shell, I usually just do:
  su uid#
For example:
adb shell
root@manta:/ # id
uid=0(root) gid=0(root) context=u:r:shell:s0
root@manta:/ # su 1010
root@manta:/ $ id
uid=1010(wifi) gid=1010(wifi) context=u:r:su:s0
root@manta:/ $ id

I think chown only does what you want if you also set the setuid bit.

On Wednesday, October 30, 2013 9:41:51 AM UTC-7, Bruno Correia wrote:
>
> Hi all,
>
> I'm trying to cross-compile the wpa_cli, so that in the future i can 
> change some of it's methods.
> At the moment, I can cross-compile the wpa_cli using the 
> arm-linux-gnueabi-gcc, but when I push the wpa_cli into my Android and try 
> to run it, it remains in loop trying to connect to the wpa_supplicant.
>
> According to what i could ascertain, the wpa_supplicant and wpa_cli of the 
> system, run as wifi group. However, when i run my wpa_cli with adb, the 
> proccess always run as root. Even if i use "chown wifi.wifi wpa_cli". Could 
> the problem be here?
>
> Any guess why this is happening?
>
> Best Regards,
> Bruno Correia
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-porting] Re: ASF files

[Glenn Kasten]

Please don't re-use an existing thread for a new topic.
Instead please start a new thread.

On Sunday, September 1, 2013 9:33:41 PM UTC-7, Er. Pragati Singh wrote:
>
> Dear all 
>
>
> kindly let me know the process of android porting witch one ubuntu ver is 
> required for that kindly guide me with step by step and kindly send links 
> for same.
>
>
>  
> Thanks in advance! 
>
>
>
> On Tuesday, August 27, 2013 5:27:57 PM UTC+5:30, gowtham rangarajan wrote:
>>
>> Hi.,
>> Im working with android BSP.
>> Im not able to get my wma files to be displayed in the songs list in .
>> I've registered my ASF parser and it is extracting .I've also added the 
>> .asf extension in stagefright media scanner .
>> As an experiment 
>> I renamed file to a ".aac" extension to see if its a problem with the 
>> extension . I did not get it up still .
>>
>> Please suggest a method .
>> Thanks a lot  :),
>> Gowtham Rangarajan 
>>
>>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-porting] Re: integration of audio components in android

[Glenn Kasten]

see http://source.android.com/devices/audio.html
and the subsection links at left below section Audio

On Monday, September 2, 2013 10:20:24 PM UTC-7, gowtham rangarajan wrote:
>
> Hi,
> I would like to know how to integrate post processing components like 
> resampler, equalizer etc., into the android multimedia framework. 
> Links to tutorials ., etc., would be helpful .
>
> I have experience in integrating audio codecs into the framework.
>
> Thanks a lot :)
> Gowtham  
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[android-porting] Re: ASF files

[Glenn Kasten]

See Custom media file format ( codec integration)
https://groups.google.com/forum/#!topic/android-porting/8icy0bpCh14

On Tuesday, August 27, 2013 4:57:57 AM UTC-7, gowtham rangarajan wrote:
>
> Hi.,
> Im working with android BSP.
> Im not able to get my wma files to be displayed in the songs list in .
> I've registered my ASF parser and it is extracting .I've also added the 
> .asf extension in stagefright media scanner .
> As an experiment 
> I renamed file to a ".aac" extension to see if its a problem with the 
> extension . I did not get it up still .
>
> Please suggest a method .
> Thanks a lot  :),
> Gowtham Rangarajan 
>
>

-- 
-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

--- 
You received this message because you are subscribed to the Google Groups 
"android-porting" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to android-porting+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.