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.
Related
I am facing very weird issue. Working on mobile application using Ionic and Angularjs. Things are pretty good but all of a sudden side menu scrollbar become sluggish. It will be easy to pin point things but issue is only coming with Samsung S6 (Android 5.x). S4 it is good. Any other mobile with Android 5.X version it is good. iOS working great. Just specific mobile it is not good.
I am creating dynamic menu based on response, I tried to do it hard code way but nothing helps. Also cross check digest timing that is also in ms. So, I doubt that can be issue.
I can't even pin point the issue to solve it. As things are very much specific to this mobile.
Any idea to debug it or way I can get and/or provide more info.
Let me know if any further information is required.
PS: I tried fresh ionic application with side menu, there it is working good on S6.
I've got a problem with my phone.
I am developing for Android and trying out transitions between activities, but my phone won't show them. So I downloaded the final source code of a transition tutorial:
http://chrisrisner.com/31-Days-of-Android--Day-17%E2%80%93Animating-between-Activities
I installed it directly onto my phone, but the transitions are still not showing. I think it has to do something with the settings on my phone.
I already activated Settings > Display > Show Animations.
My Phone is a new HTC Desire X running Android 4.2.
I didn't find anything on stackoverflow or google. I hope you guys have a solution for this!
Thanks in advance!
Okay, 4 months later I got a new phone (Nexus 5) and it shows all transitions, so i guess transitions are just deactivated on the Desire X, probably because it's too slow anyways.
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.
I have hooked up the Facebook application. I have a couple different devices to test on, and I'm getting different results. So far, everything is working great with my Motorola Droid phone, but I get a different experience when it comes to running the same code on an HTC Flyer. Basically, it leaves me stuck at the "Loading" screen with a black "Facebook" screen in the background. My application never completes authentication.
I have been digging around on the web, and I found a post about proceeding through SSL errors,
but this solution that doesn't work for me.
I am officially frustrated and I am not sure how to explain the problem better. I know my SSO keys are correct, because I have one device that is fully working with the Login Experience and one that doesn't. I have searched the web and there hasn't been any working solutions that I could find.
stringa
I am trying to wrap my head around Android Widgets, using the sample provided here: http://code.google.com/p/wiktionary-android/
I have corrected the strings.xml but the plugin will not work properly, neither on the emulator nor on the actual phone. It installs fine, but it never updates.
But at least on the simulator i get some DDMS output, telling me, that the API-response could not be parsed, so I assume, that the Wiktionary API has probably changed.
However, on my phone, the public void onUpdate(...) method doesn't even seem to get called at all when I install the Widget. I have inserted Log.i(...) lines for debugging and while they all show up when I use the Widget on the emulator, none of them seem to come up when it actually runs on the phone.
The phone is a Samsung Galaxy S II running android 2.3 but that hardly matters I think.
has anybody encountered this before and knows anything that might help?
EDIT I was told it might be a permissions issue, but could not verify this.
OK. Just in case anybody else ever comes across this. There is a strange thing with android widgets when the throw an exception... just uninstalling isn't always enough one hast to restart the phone.
Can not explain why that is but it always did the trick.