I am developing an android app so I am still in "debug mode" in terms of signing my app. The MapView that I am using used to work so far but since today (maybe yesterday) the map shows greyed out areas. (Compare the following image.)
Does anybody know the reason for this?
[EDIT]
I have installed my app on two other devices (Samsung Galaxy Ace and Galaxy S2). On the Ace it shows the exact same behavior with the greyed out "chessboard" tiles. On the Galaxy S2 however it does not.
I have also thrown away the debug certificate and generated a new fingerprint and API key. But that did not help.
Trying to narrow down the problem I found that it seems to be related to the streetview feature. When I started to code the mapview into my app I set the streetview feature to true:
mapView.setStreetView(true);
When I turn it off (set to false) the greyed out areas disappear.
I have not further investigated this but for now my problem is solved (so I wrote this as an answer).
Related
So I am one of several developers developing a GPS-app with the help of HERE SDK for Android.
This is a project that has been in the making for some time and it has been a somewhat smooth ride, until yesterday.
We have a couple of tablets to test our app with, and yesterday when building on the Samsung Galaxy Tab A(2016) the routing always gave us "GRAPH_DISCONNECTED" as an answer.
It doesn't matter what route I try. From current location. From a set location. The destination doesn't matter either.
So we have a CoreRouter.Listener that overrides the onCalculateRouteFinished-method and no matter what I do routingError seems to beceome GRAPH_DISCONNECTED.
I have tried to uninstall the app and install it again. Same result.
I have tried deleting the cache for the app. Same result.
The weird part? It has been working on the tablet for well over a year.
And if we use any other tablet, like the Xperia z4 tablet there is no problem with the routing.
Okay, so problem found!
Apparently, we had the wrong settings for the vehicle. It was too big to go from the positions we tried with, and that's why HERE couldn't make a valid route.
The strange part is that this route has worked with those vehicle settings before. So some construction must have come up all of a sudden that stopped me from making the same route.
I am using Google map API v2 in my android app. The map is working probably on all devices _ that I tested the app on it _ but Samsung S Duos with android version 4.1.2 though it works on Galaxy S3 mini with android version 4.1.2
When I run the app on Samsung s duos nothing looks wrong in the log Cat.. no errors no warnings.. it runs exactly as it runs on other devices but doesn't show the map.. only showing the zoom buttons and Google word at the bottom of the screen..
I figured out the problem.. it was a strange problem really! the date of the device was incorrect and that lead to an error in network connection.. the WiFi was connected but there was no really connection.. I fixed the date and the map was loaded :)
I wrote this to help anyone having the same problem! :)
I am developing an app in Android that I hope to release. I've got most of my GUI done, but it does not look even close to correct on the device when installed and opened. I have a screenshot of how it looks, and a screengrab of how it should look (taken from the Emulator in Eclipse) at the links at the bottom of this post. It's best to take a look at the two images rather than me try to describe how screwed up the app becomes on my device.
I had a friend with the exact same device, including hardware and Android version, and his loads up just fine. Does anyone have any idea what's going on here? Both devices are Galaxy Nexuses, running Android 4.0.2, GSM on AT&T (unlocked).
Installed on my device: http://i.stack.imgur.com/x66Jo.png
In the emulator: http://i.stack.imgur.com/qE0J6.png
I've seen this occur in some Galaxy Nexus' and I put it down to a bug/glitch in the OS on that Galaxy Nexus. Try a Factory Reset of your Galaxy Nexus, if that fails, try reinstalling the current OS version you have (if you can get your hands on it), if that fails, get it fixed under warranty.
Does your app use multiple activities?
Can you compare on your two devices if this setting is the same?
Settings > Developer Options > Don't keep activities checkbox.
I realise this is an old question now but I was having the same problem as you and stumbled across a solution. I didn't particularly want to factory reset my phone as per straya's instructions, so I started playing around options in the Settings > Developer Options menu.
As it turns out, this problem occurs for some applications if you have the Force GPU rendering option checked. Disable this (I'm not sure why it was enabled anyway) and everything displays as it should.
Complete beginner here so forgive me.
Porting an iOS App over to Android. We have custom image tiles laid over google maps. On iOS the streetmap displays as usual outside of our custom image tiles however on the Android version it is only showing a blank grid and we can't figure it out. The location works however it's just not showing the map.
We've tried a couple of different devices and the issue is the same across the board.
Any suggestions? If there is more info that I can provide that might help narrow the issue down, just ask.
EDIT: The device we are testing it on is a HTC. Apparently it works on a Nexus. Known compatibility issue?
If your MapView is not loading standard map tiles, either:
you do not have the INTERNET permission, or
you do not have an Internet connection, or
you are not using the right Maps API key for the signing key
When we create google map in our application and load in motorola milestone, left side a square portion is being cut off. Can anyone what may be the reason? The same code wont show any issues in other sets..
I think this will help you google maps glitch on motorola phones
And its a known bug in some of motorola phones