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
Related
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.
I've developed an Android app for remote controlling some special hardware devices. The communication is done via udp and wifi. The app already runs on ~60k devices without any problems but since the rollout of Android 6 I'm getting more and more reports from users who get some strange errors:
Usually the app searches for the hardware with a broadcast package. The app then requests all data from the hardware to stay in sync (~4000 packages in both directions). This sync process is heavily tested with all wifi conditions possible and does work as intended (also on Android 6).
User with a Samsung device and Android 6 are now having the issue, that the sync is unable to complete (no reply from the hardware within 20 seconds). The odd thing is that the broadcast search does work just fine, as well as the beginning of the sync. Usually the timeout happens when 5-15% of the sync was completed.
As I have no idea what could cause this issue I wanted to ask if there is any known problems with Samsung / Android 6 and udp communication via wifi?
Also were there any other changes on the network stack in Android 6 that could cause this issue? On my test devices (HTC mostly) everything runs fine so I'm currently out of ideas.
Edit:
I narrowed the issue down to the following devices:
Samsung Galaxy 6
Samsung Galaxy 6 Edge
Samsung Galaxy Note 5
Edit 2:
I got a Samsung Galaxy 6 device for testing purposes and of course it does work for me. I also tried all sorts of network setup, power saving, anti virus and general settings combination but it's just working all the time.
Edit 3:
After getting some Galaxy S5 and S6 test devices I was not able to reproduce the problem. Comparing the ROM version I found out that these devices all have a newer rom than the devices which got the issues.
Turns out that Samsung simply broke something in their wifi stack which causes the wifi to stop working properly after some udp packages. So only fix for this issue is to wait and hope they fix it in all countries soon.
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 a developer and recently published my new application My VIT on Play Store. Everything is working fine except a small bug in Android Lollipop devices. Whenever my users are trying to install app from play store in their devices, they get a 505 during the time of installation.
The app is running well on Kitkat and many other Lollipop devices. Some devices like nexus 6, nexus 7 2013, htc one m8, yu yuphoria are facing problems. I contacted Google Support, but they provided me with solutions I already performed.
I have cleared my Play Store data, Play Services data, download manager data, reset my date/time and re-added my Google account. Still no luck. I think it's a development issue because my other app is running fine on those devices.
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.