I am using the TomTom map API. But when I'm using the map there are so many black dots and boxes(as seen on the image below). When I zoom in the dots and boxes disappear, but then the new dots and boxes disappear. PS: I have not done anything special, I just added the map to my Android studio project as TomTom wanted.
Example Image of bug
This is a TomTom issue whilst running in the android emulator, this does not appear running on android devices. Same issue is shown in TomTom documentation.
Related
I'm using the emulator with Android Studio, and I'm experiencing the phenomenon shown in the image below.
The problem occurs only when the screen is turned sideways.
It does not happen in the default screen.
I don't know how to solve this problem, and I was wondering if you could tell me something that would help me.
Thank you very much!
You can solve this in three ways:
disable screen rotation - add this to the manifest XML under the relevant activity
android:screenOrientation="portrait"
If you want to go the long and better route it seems to me that you are using a layout that is not constraint layout, the latter supports rotation better, and when constraint correctly what is shown here should not happen.
If all else fails you can use special layout when the screen is in landscape mode, you can read more here:
Android Studio: Creating landscape layouts
For some reason all images I import to my android studio project are gray scale. Previously I found a solution here:
The colored image turned to have no color and just a grey vector in drawable?
But apparently the batch drawable importer stopped working in Android Studio 3.6. Is there another solution I am unaware of?
Edit: Do I need to give more information or am I just the only one with this problem?
I did a lot more looking and if you click on "resource monitor" on the left (for me) there is a "plus" sign that you can select to add drawables. Depending on the file type, it will correctly import the drawable as a full color image
I am new to android development. The mouse pointer on the design page is as shown in the screenshot. I am not able to edit anything like increasing the height and width of the widget on this page. I might be able to do it in XML but I want it done here.
I want a normal mouse pointer where I can edit the widgets.
I tried looking at some of the blogs but it didn't help.
activity.xml - design
It worked after removing the cache files and restarting the android studio
I'm currently working on an app in Android Studio where I need to capture an image using the camera on the phone. The image must be very specific and not contain any background noise.
The way I want to solve this problem is by adding a box to the camera preview indicating the region of interest (ROI). After that the image can be cropped in a way that only the content of the ROI is present.
How do I add this box to define ROI?
In my mind it would be perfect if it was a thin white line.
Can I do it if I use the Image Capture Intent or do I have to create my own camera app?
Check this out - is that what you're after?
http://code.tutsplus.com/tutorials/capture-and-crop-an-image-with-the-device-camera--mobile-11458
I've been experiencing some very strange behavours in an app I'm developing. The app is not very advanced, it stores a couple of places in a sqlite database and is displayed in listviews, on a mapview etc. So, when browsing through my app after deploying it to my phone everything works great, but after a while one listview doesn't get inflated. A scrollbar appears as if the items were there but I can't see them. I push the back button to close the app. When revisiting the app my first view, which has two buttons, gets all messed up. The buttons fill the viewport and the background disappears etc. I can't figure out what's wrong.
Anyone else facing these problems? My phone is a HTC Desire HD with Android 2.3.5
The app is pretty "layout heavy", if you know what I mean. The listview items has custom background images, I'm using custom fonts etc. But the app is running smoothly up to the point when it freaks out and displays/don't display everything wrong.
My first thought is there is some kind of memory issue, ideas?
EDIT:
I believe this might have something to do with defining and using #00000000 as transparent color. Use #android:color/transparent instead.
SOLUTION:
So after doing some testing I found that what I previously mentioned in the edit really is the cause of this problem. I had defined the transparent color in my colors.xml as #00000000. This seems to work, sometimes... And other times it grabs a drawable instead, but not a drawable that is named "transparent", it grabs ANY drawable. Weird but true.
After some testing I finally found the cause of this problem. I had defined the transparent color in my colors.xml as #00000000. This seems to work, sometimes... And other times it grabs a drawable instead, but not a drawable that is named "transparent", it grabs ANY drawable. Weird but true.
So to fix this problem you should use #android:color/transparent instead when you want transparency on, for example, a view background.
If there are memory errors you should be able to catch them in logcat. You'll get "VM failed on xxxx byte allocation" messages (or the like).
Silly/stupid answer: often when I run into layout issues within my app, it's because I needed to do a clean build after having changed my layouts. You might want to start there.
Edit: You might also try the emulator, and if you suspect memory issues you could start the emulator with a small heap to force the issue to occur sooner. You can also check your heap usage in DDMS or with the Eclipse MAT to see if it's leaking.
I was experiencing the same problem on Galaxy tab even with #android:color/transparent. Was able to fix it only by replacing android:background="#color/transparent" with android:background="#null".