Unable to increase the output volume - android

Tried endpoint.audDevManager().setOutputVolume(percentage), with values ranging between 100-1999. Unfortunately, it's not resulting in any increase in volume.
The documentation suggests that:
This method is only valid if the device has PJMEDIA_AUD_DEV_CAP_OUTPUT_VOLUME_SETTING capability in AudioDevInfo.caps flags.
And I've already ensured that this flag is set. Is there anything else that I need to take care of?

Sauw Ming suggested (over mail) to use AudioMedia::adjustRxLevel(float level) instead, and that fixed the issue for values of level over 3.0. At least that's when there was perceivable difference in volume.

I also worked with endpoint.audDevManager().setOutputVolume(percentage) and it works after the call start.I got the change of volume.Also i used the range 1-100.Please check it with this settings.

Related

Array in Between Condition

How do I implement this condition as shown in this image.
That's just in 2..4, i.e. in the integer range from 2 to 4, including the 4.
The ≤ is just some hint text provided by the IDE, similar to how you can see argument names in function calls - it's not part of the code, it's not really there. They added it to make it clearer what the .. operator does (vs until)
This might be because they're introducing a new operator, ..< which seems intended to replace until, or maybe they've been there a while! You can turn them on and off here in the settings:

AOSP: Disable default display

I'm trying to disable the default/built in display in AOSP. Is there a default flag i can enable/disable to achieve this?. Note: I am compiling Android 10.
I suspect his is possible because of a comment in /core/java/android/view/Display.java
I tried removing the builtin or internal flags in frameworks/base/services/core/java/com/android/server/display/LocalDisplayAdapter.java but that causes DisplayManagerService to throw an exception onBootPhase. Any pointer is appreciated.
Workaround only since i couldn't find the actual place to disable it but this worked.
In DisplayManager on the public Display[] getDisplays(String category) method i checked. If there's two displays, then ignore whatever display is not the default display. Terrible temporary workaround but this is my solution. Accepting until someone posts a better soltuion!

How to create NotificationManager Policy correctly?

I am facing a problem with the NotificationManager Policy.
Let's say I just want to be interrupted by alarms. Then I specify that as the Category (NotificationManager.Policy.PRIORITY_CATEGORY_ALARMS) but what values should I pass to create the Policy? I am talking about the priorityCallSenders, and the priorityMessageSenders. No calls and no messages are allowed, only alarms, so why should I have to specify a value for them?
The available values are:
PRIORITY_SENDERS_ANY
PRIORITY_SENDERS_CONTACTS
PRIORITY_SENDERS_STARRED
Which one should I use? The code results messy and confusing if I specify I want only alarms BUT then use the constant PRIORITY_SENDERS_ANY.
For you to remember, here I paste the call to create the Policy:
myPolicy = new NotificationManager.Policy(NotificationManager.Policy.PRIORITY_CATEGORY_ALARMS, iCallsPrioritySenders, iMessagesPrioritySenders);
myNotificationManager.setNotificationPolicy(myPolicy);
On the other had, and I suspect that the issue might come from here, I am not able to set this values correctly in Xiaomi.
I have tried in Huawei and Android Emulator setting a value like this (even when it is not allowed by Android documentation):
NotificationManager.Policy(NotificationManager.Policy.PRIORITY_CATEGORY_ALARMS, -1, -1);
and it works well with both. But the problem is with Xiaomi. For some reason, calls/messages are always accepted and I am not able to disable calls. It looks like must be Any, Contacts or Starred.
Any light in this issue and the right values to pass?

DJI WaypointActionType for CAMERA_FOCUS and CAMERA_ZOOM

The documentation online did not have these two actions (CAMERA_FOCUS and CAMERA_ZOOM). Could anyone tell me what parameters are acceptable for these actions? I'm assuming it would only work with the Inspire drones which is what I'm working with. Thank you.
Current documentation:
CAMERA_FOCUS and CAMERA_ZOOM available in SDK:
How the zoom function waypoint action basically works the same way as the setOpticalZoomFocalLength function in DJICamera.
You will need to calculate the focal length value to pass in base on the current lens you are using. The max and min focal length values you can find under getOpticalZoomSpec function.
More information on setOpticalZoomFocalLength in DJI android sdk api:
https://developer.dji.com/mobile-sdk/documentation/cn/faq/cn/api-reference/android-api/Components/Camera/DJICamera.html#djicamera_camerasettings_setopticalzoomfocallength_inline
Hope that helps.
Not really sure what is your meaning.
I guess you want to know how to control camera focus/zoom using DJI MSDK? refer to their class reference and call the corresponding function. EZ as ABC
https://developer.dji.com/cn/mobile-sdk/documentation/faq/cn/api-reference/android-api/Components/Camera/DJICamera.html
There are a few more missing. I see the following (including the ones you mention):
CAMERA_ZOOM(7),
CAMERA_FOCUS(8),
FINE_TUNE_GIMBAL_PITCH(16),
RESET_GIMBAL_YAW(17);
I'll see what I can find out and get back to you.
DJI got back to me the other day, apparently these values are inactive currently, they do nothing in the current release but it's possible that a future release will include the functionality.
No date, version or timeline was indicated on when they might work.
For now, ignore them, they will likely be removed in the next update.

How to find cause of 'Transform with key of "perspective" cannot be zero: {"perspective":0}'

I'm taking over care and feeding of an existing React-native app. There's a part of the app that takes a picture, which results in the message "Transform with key of "perspective" cannot be zero: {"perspective":0}". (This happens in the Android emulator.)
In the existing code, there's no place that designates a perspective. I'm curious what might be implicitly expecting this.
I figured out what was happening. The code was rendering a FlipCard (#see react-native-flip-card) FlipCard takes an attribute "perspective," whose default is zero. Setting it to something other than zero saved the day: ...<FlipCard perspective={0.5}...>
Hope this helps someone.

Categories

Resources