qqwen10 | 1 Mar 17:12 2014
Picon

audio effect getting disabled automatically

Hi everyone. 


I am having a problem regarding audio effects. The auxillary effect is getting disabled automatically. 


There is an auxiliary effect declared in the system which enhances the volume of output (be it a music played or ring tone). These effects where ported from jellybean (4.1.2) to ics (4.0.4). 


Now when it is the only effect declared it works like a charm enhancing the volume ,but when a  INSERT effect is created (like equalizer) the auxiliary effect changes  state to 0,

when the equalizer effect is turned off ( by using music player interface) the auxiliary effect gets enabled again.


I have seen this behavior with other music players also.So the chance of one particular music player causing this problem alone is null


My system: ICS 4.0.4

sound effects ported from jelly bean (4.1.2)


expecting your expertise to solve this




--
--
unsubscribe: android-porting+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
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+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit https://groups.google.com/groups/opt_out.
Tung Nguyen Thanh | 1 Mar 08:16 2014
Picon

Building for a new device

I have a new device. It doesn't have a camera. so what i can't do to
disable camera. Because I want to reduce code size. Please help me
solve this problem.

--
--
unsubscribe: android-porting+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
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+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit https://groups.google.com/groups/opt_out.
Stephen Proffitt | 27 Feb 19:17 2014
Picon

3.1 Kernel for Tegra 2

I know that there isn't an official 3.1 kernel for a Tegra 2 however, I've started working on getting one ported, but I'm running into a snag with drivers.

After working out GPIO issues, I'm having a problem with the light sensor (isl29018 specifically). Every time I've tried to build, I get this error:

drivers/staging/iio/light/isl29018.c: In function 'isl29018_write_raw':
drivers/staging/iio/light/isl29018.c:356: error: 'IIO_CHAN_INFO_CALIBSCALE_SEPARATE' undeclared (first use in this function)
drivers/staging/iio/light/isl29018.c:356: error: (Each undeclared identifier is reported only once
drivers/staging/iio/light/isl29018.c:356: error: for each function it appears in.)
drivers/staging/iio/light/isl29018.c: In function 'isl29018_read_raw':
drivers/staging/iio/light/isl29018.c:396: error: 'IIO_CHAN_INFO_CALIBSCALE_SEPARATE' undeclared (first use in this function)
drivers/staging/iio/light/isl29018.c: At top level:
drivers/staging/iio/light/isl29018.c:415: error: 'IIO_CHAN_INFO_CALIBSCALE_SEPARATE' undeclared here (not in a function)
drivers/staging/iio/light/isl29018.c:426: error: expected ')' before '(' token
drivers/staging/iio/light/isl29018.c:427: error: expected ')' before string constant
drivers/staging/iio/light/isl29018.c:428: error: expected ')' before string constant
drivers/staging/iio/light/isl29018.c:429: error: expected ')' before '(' token
drivers/staging/iio/light/isl29018.c:432: error: expected ')' before '(' token
drivers/staging/iio/light/isl29018.c:439: error: 'iio_dev_attr_range' undeclared here (not in a function)
drivers/staging/iio/light/isl29018.c:439: error: request for member 'dev_attr' in something not a structure or union
drivers/staging/iio/light/isl29018.c:439: error: request for member 'attr' in something not a structure or union
drivers/staging/iio/light/isl29018.c:439: error: initializer element is not constant
drivers/staging/iio/light/isl29018.c:439: error: (near initialization for 'isl29018_attributes[0]')
drivers/staging/iio/light/isl29018.c:440: error: 'iio_const_attr_range_available' undeclared here (not in a function)
drivers/staging/iio/light/isl29018.c:440: error: request for member 'dev_attr' in something not a structure or union
drivers/staging/iio/light/isl29018.c:440: error: request for member 'attr' in something not a structure or union
drivers/staging/iio/light/isl29018.c:440: error: initializer element is not constant
drivers/staging/iio/light/isl29018.c:440: error: (near initialization for 'isl29018_attributes[1]')
drivers/staging/iio/light/isl29018.c:441: error: 'iio_dev_attr_adc_resolution' undeclared here (not in a function)
drivers/staging/iio/light/isl29018.c:441: error: request for member 'dev_attr' in something not a structure or union
drivers/staging/iio/light/isl29018.c:441: error: request for member 'attr' in something not a structure or union
drivers/staging/iio/light/isl29018.c:441: error: initializer element is not constant
drivers/staging/iio/light/isl29018.c:441: error: (near initialization for 'isl29018_attributes[2]')
drivers/staging/iio/light/isl29018.c:442: error: 'iio_const_attr_adc_resolution_available' undeclared here (not in a function)
drivers/staging/iio/light/isl29018.c:442: error: request for member 'dev_attr' in something not a structure or union
drivers/staging/iio/light/isl29018.c:442: error: request for member 'attr' in something not a structure or union
drivers/staging/iio/light/isl29018.c:442: error: initializer element is not constant
drivers/staging/iio/light/isl29018.c:442: error: (near initialization for 'isl29018_attributes[3]')
drivers/staging/iio/light/isl29018.c:443: error: 'iio_dev_attr_proximity_on_chip_ambient_infrared_supression' undeclared here (not in a function)
drivers/staging/iio/light/isl29018.c:443: error: request for member 'dev_attr' in something not a structure or union
drivers/staging/iio/light/isl29018.c:443: error: request for member 'attr' in something not a structure or union
drivers/staging/iio/light/isl29018.c:443: error: initializer element is not constant
drivers/staging/iio/light/isl29018.c:443: error: (near initialization for 'isl29018_attributes[4]')
make[4]: *** [drivers/staging/iio/light/isl29018.o] Error 1
make[3]: *** [drivers/staging/iio/light] Error 2
make[2]: *** [drivers/staging/iio] Error 2
make[1]: *** [drivers/staging] Error 2
make: *** [drivers] Error 2


I've looked over the file and all previous code blocks and there is nothing missing. I've been looking over the board files and it seems to my untrained eyes that the functions are being called properly, but obviously something is wrong. Any ideas?

--
--
unsubscribe: android-porting+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
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+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit https://groups.google.com/groups/opt_out.
Dave McLaughlin | 27 Feb 14:42 2014
Picon

Notification LED not working..

I've written code to toggle an LED based on notification but so far the function never gets called.

I've implemented this in lights.c and the backlight is driven from here too and that is working.

I can toggle the LED from the debug port so I know the GPIO direction setting is correct.

Is there a setting somewhere in the build that I need to do to get notification lights working?

--
--
unsubscribe: android-porting+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
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+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit https://groups.google.com/groups/opt_out.
Naaman Sittsamer | 25 Feb 22:06 2014
Picon

Possible audio resampling issue in 4.3

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+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
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+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit https://groups.google.com/groups/opt_out.
Android Newbie | 25 Feb 19:33 2014
Picon

display message from system service

I am adding additional battery properties that require a shutdown under certain conditions. I have a requirement that the user be notified of the shutdown reason

Basically I am adding additional checks like shutdownIfOverTemp() in BatteryService, so I can use that function as an example of where I would like to add a reason notification to the end user.

The standard behavior simply shuts down the phone (at least in 4.1.2 that I am based on):

    private final void shutdownIfOverTemp() {
        // shut down gracefully if temperature is too high (> 68.0C)
        // wait until the system has booted before attempting to display the shutdown dialog.
        if (mBatteryTemperature > 680 && ActivityManagerNative.isSystemReady()) {
            Intent intent = new Intent(Intent.ACTION_REQUEST_SHUTDOWN);
            intent.putExtra(Intent.EXTRA_KEY_CONFIRM, false);
            intent.setFlags(Intent.FLAG_ACTIVITY_NEW_TASK);
            mContext.startActivity(intent);
        }
    }

I'm not sure what my options are to notify the user.
I can't display a toast from the service right?

It might be OK to set EXTRA_KEY_CONFIRM to true (iffy in the case of being over temp), but I don't think this provides me a way to show a message anyway (I'll try it next)

The only way I can think of is to send a new intent SHUTDOWN_REQUEST_BATTERY_OVERTEMP then define an activity that would catch it, display something ("system shutting down due to battery temperature") and that activity would then send ACTION_REQUEST_SHUTDOWN? and I would have to do this for every separate shutdown reason or can I add an additional extra to ACTION_REQUEST_SHUTDOWN that would indicate the shutdown reason?


--
--
unsubscribe: android-porting+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
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+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit https://groups.google.com/groups/opt_out.
SSI | 25 Feb 09:54 2014
Picon

JB4.3 compilation error

Hello,

   I have checked in android jelly bean 4.3 source code into my server with below command,

    svn import -m "commit message here" /source_code_path/jb4.3/ URL_LINK/JB4.3/ --no-ignores

 before commit I checked that source code is compiling or not . It was working fine. After compiling the source code and I checked out to local machine and kept it for compilation using make -j4 command.

  It is giving below error

   build/core/base_rules.mk:130: *** libcore: MODULE.TARGET.ETC.target-cacert-74c26bd0.0.svn-base already defined by libcore.  Stop.

 If I commented out in above file line number 130, it is started build and it is created boot.img and other binaries but not system.img. I got below error before it complete the build.

Target ram disk: out/target/product/sabresd_6dq/ramdisk.img
Target boot image: out/target/product/sabresd_6dq/boot.img
----- Making recovery image ------
Copying baseline ramdisk...
Modifying ramdisk contents...
cp: cannot stat `out/target/product/sabresd_6dq/root/init.recovery.*.rc': No such file or directory
make: [out/target/product/sabresd_6dq/recovery.img] Error 1 (ignored)
----- Made recovery image: out/target/product/sabresd_6dq/recovery.img --------

zip error: Invalid command arguments (cannot repeat names in zip file)
make: *** [out/target/product/sabresd_6dq/system/etc/recovery-resource.dat] Error 16

Can anybody tell me that why I am getting above errors? Is am doing anything wrong in importing source code to server using svn ?

Kindly help me to resolve the problem

Thanks

--
--
unsubscribe: android-porting+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
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+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit https://groups.google.com/groups/opt_out.
SzuHung | 23 Feb 14:04 2014
Picon

Android 4.4 low power sensor support sensor types?

In android 4.4 can support low power sensor.
Is only support Step detector, Step counter, Significant motion and Geomagnetic rotation vector sensor type?
Whether to support Proximity/Light sensor type? 

--
--
unsubscribe: android-porting+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
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+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit https://groups.google.com/groups/opt_out.
Richard Phillips | 22 Feb 10:27 2014
Picon

Porting to new board - advice on first steps

Hello all,

I'm currently running an Android build on the beagleboard-xM, and now need to migrate this build to our
custom board. This board uses the AM3715 (TI ARM Sitara) SoC, the xM uses the DM3715, but it's basically the
same. I expect the main differences are likely to be at board level, rather than SoC... (crosses fingers)

So, what should my first steps be? My guess is I need to set up a "board config (file?)" of some kind, and "make
config" the kernel accordingly?

I'm reading books and websites and plan to attend a course on this soon, but would appreciate a nudge in the
right direction!

Regards,
Richard.

-- 
--

-- 
unsubscribe: android-porting+unsubscribe@...
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+unsubscribe@...
For more options, visit https://groups.google.com/groups/opt_out.

Satish Aradhya | 23 Feb 13:19 2014
Picon

Kitkat porting on custom hardware

Hi, all,

 I have ported kitkat to our new hardware.
     But still im seeing Jelly Bean  home screen and icon tiles also looks JB layout.

      by ADB shell, if we query of android version it gives 4.4.2 

          
     What should I do? Do I missed any other while porting..

--
--
unsubscribe: android-porting+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
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+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit https://groups.google.com/groups/opt_out.
petr.vorel | 19 Feb 21:49 2014
Picon

In which part of Android ajust code to calibrate screen

Hi there,

I need to calibrate screen (move coordinates to right, basically add some
margin to left). Where is the best place to adjust the code? In kernel driver?
Or would it be possible and easier in user space libraries? Or is there a some 
boot parameter? (something like disp.screen0_output_mode from
http://linux-sunxi.org/Kernel_arguments)?

I'm using Allwinner A31.

Thanks for any advice.

Regards,
Petr

--
--
unsubscribe: android-porting+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
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+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit https://groups.google.com/groups/opt_out.

Gmane