My app displays MPVolumeView button. When no earphone or bluetooth headset is not connected, clicking on this button shows two options. iPhone and iPhone speaker (for speaker and ear piece). This was perfectly fine till iOS 10. But on iOS 11, this button is disabled. It shows available routes only when connected to wireless headset.
I do not see any change or deprecated APIs in MPVolumeView. Anyone else seeing this issue?
Also a thing to note here is I still see old volume control indicator while I read about volume control indicator designed differently on iOS 11.
Figured out that I need to use AVRoutePickerView on iOS 11. This offers audio route options and also volume slider.
Related
I'm trying implementing a action.devices.types.GARAGE device but when I get the SYNC the garage device show up with an gear icon and when I press it it only show the device settings.
I implement another devices with action.devices.types.LIGHT, action.devices.types.SWITCH and action.devices.types.OUTLET and all works fine.
Any idea what I'm doing wrong?
The device type GARAGE does not have touch control support, whileOUTLET, SWITCH, and LIGHT do. You can see the full list of devices with touch control support in the docs.
If you can still use voice control to control the GARAGE through your integration, then everything is working as expected.
I tried to install a Codename One app on a tv box that runs Android 7. It works, except the fact that I cannot use the tv remote control to switch from a Button to another (I need to enable the mouse pointer simulation to tap the Buttons, that is not user friendly).
Any idea to manage this use case? Or the problem is that I'm using a BrowserComponent?
I’ve just published in the Play Store my first Codename One app for Android TV (I hope that it will be approved). I confirm that it can be used with the tv remote control if I do a simple navigabile UI, that can be tested in the Simulator using the arrows. I’ve done tests with an Android TV Box. My problem was that I used a BrowserComponent, that then I replaced with a simple standard UI composed of Buttons.
i am working on opentok with nodejs.
i use tokbox for one-to-one videochats between users. It works properly in chrome, but not working in firefox.
it give me error
OT.Publisher.onStreamAvailableError OT_MEDIA_ERR_ABORTED: The selected
voice or video devices are unavailable. Verify that the chosen devices
are not in use by another application. (getUserMedia error:
NotReadableError)
Firefox can not open the same camera in different tabs. You'll need a second camera or set media.navigator.streams.fake to true in about:config which enables fake devices.
I can't figure out what is causing this issue on the BlackBerry Z10 where the mobile menu that I created for disinherited.com won't properly function as links.
The menu items won't click through to their href's or show their dropdown menus(javascript).
It works well on a number of other browsers and devices. This is just one that won't work.
Anybody have any suggestions as to what browser compatibility issues I might be missing?
The "About Us" link doesn't do anything for me (even on Desktop browsers).
I would guess that there might be some CSS (a layer maybe) that is interfering with the click/action event. I would suggest connecting remote web inspector to see what exactly is going on.
Did you know that BlackBerry 10 has some of the best remote web debugging capabilities?
Plug your device in via USB
Enable Settings -> Developer Mode
Open http://disinherited.com in the BlackBerry browser
from your desktop browser, open http://169.254.0.1:1337
You are connected to the live content, running on the BlackBerry, from your desktop browser. From there, you can inspect, debug, profile what your website is doing.
With respect to webpages and webapps using Facebook's Javascript and Server side integration...
Facebook documentation notes that the send dialog is not supported on mobile devices, but they don't indicate how they make the determination that the dialog will not be shown or how we can find out.
This makes it difficult to display some alternate functionality in the right cases. For example the iphone is out, but the ipad will display the iframe version. The Nexus 7 with Chrome won't do the popup, but it doesn't have "mobile" in the user agent.
Does anybody know the criteria? ie. Regex on the user agent, or some certain feature detection?
Right now I am using browser sniffing :-(
function isMobile(string) {
return /mobile|android/i.test(string || navigator.userAgent);
}
Which, for instance, doesn't account for the fact that iPad Safari will display this dialog as an iFrame (but not the popup).
Thanks.