I have an issue where MediaRouteButton is not detecting chromecast on some devices.
It's being detected on the older phone Samsung Galaxy Nexus, but not on my Google Pixel.
The funny thing is it used to work on my Google Pixel, but now it's not working anymore. On my pixel, I checked wifi multiple times and YouTube chromecast works, just not my app.
I checked the sample MediaRouterButton demo and it's not working either. https://github.com/googlecast/MediaRouter-Cast-Button-android
The callback doesn't seem to be triggered.
mMediaRouter.addCallback(mChromecastDeviceSelector,
mMediaRouterCallback,
MediaRouter.CALLBACK_FLAG_REQUEST_DISCOVERY);
EDIT:
I tested on N and O and it didn't work. However the N and O device and the same Google Play Services version (11.7.46). The Samsung Galaxy Nexus has Jellybean but an older Google Play Services version (10.2.98)
EDIT2: Looks like it's working again after the weekend, dunno what happened. :/
EDIT3: It's NOT working again.
Related
Geofencing is worked well in other android devices like Nokia, Motorola, Lg. But not in give Exit and Enter Callback in the latest Samsung devices. It will Register and unregister well.
S9 is Oreo and S10 is Pie. It requires notification running for background services and externally handle the permissions. Since oreo, you will not be able to keep bg services running continuously without notification. Use androidX library from Pie to lower support. Hope it helps.
Check the issue reported at google issue tracker here
It seems to be have been fixed now.
I was looking at newest phones at the store today and found out that my app cant be seen in google play on S10, S10+, S10e, S9, S9+ and NOTE9. Other Motorola, Huawei, Honor... works fine. And its strange because on my emulator Pixel2 with Android Pie and with google play store it works fine too. In google play console/release management/device catalog it says that all newer galaxy phones are supported but in reality they are not. Target API in my app is 27 but that shouldn't matter, wright!?
Anyways, how do I fix that?
How do I replicate Nexus 5 images rotation issue when I don't have a Nexus 5?
I have a bug reported that images taken within my app are turned upside down when using Nexus 5. I have 6 devices at hand but not this one, and all 6 work just fine.
How can I replicate this issue, using a good, reliable online service that provides developers with real devices to test on?
Google has the Cloud Test Lab which allows you to test different orientations on real devices, including the Nexus 5.
An emulator like Genymotion has the device you require and many others too.
I am using Activity Recognition API available in Google Play Services.
I've tried using Google Play Services 5+ and Google Play Services 6+ (using the new API with GoogleApiClient) on Android 4+ and Android 5+. Everything works great on different kinds of devices, except Samsung Galaxy Note 4
(Announced 2014, September)(Can not test on other Samsung devices.)
The problem is that:
Samsung Galaxy Note 4 has Google Play Services 5.0.89 (currently the
last version is 6.5.99) (and it's not possible to update it)
Activity Recognition API doesn't work (it's available, just
doesn't trigger needed recognition events)
Does anyone faced the similar problems on any Samsung devices?
How to resolve it?
Thanks.
the sample code from http://developer.android.com/training/location/activity-recognition.html
doesn't work in Nexus S and Motorola droid devices (and probably on other devices also),
confirm working on Nexus 7 2013 and Samsung Galaxy Young,
this occurs after update to latest play services 5.0.89, in my recall two months ago, it works fine on all devices,
try to switch using GoogleApiClient, no luck
confirm working after enable network Provider on location access, I think this is a bug on play service