i have issue when using mobile to view app, when i go to map section it's not displayed well.
this is how it looks, and it's not the same on all devices (this is SS taken from ZTE Blade A6 lite which has version 7.1.1), on some newer androids it's fine.
I was wondering are there some limitations to implementation or it's known issue?
If the map is rendering fine on other android devices, then problem could be with device and not how the sdk works. you can refer to github for efficient map rendering practices followed in our sample code implementation(https://developer.here.com/documentation/android-sdk/4.2.0.0/dev_guide/content/topics/examples.html). Is there any specific error which is logging at the application level while map rendering. Do you mind sharing to know the issue better.
Related
Hi I'm new here and I want to make a WebAR application using A-Frame. I know the basics and all that but one major problem I'm having is being able to walk around in the scene using ARCore running in Chrome. Is this even possible? I found a WebVR application from 6 years ago that solved the problem of positional tracking but the code's so depreciated it doesn't work anymore. I would prefer using ARCore for tracking but if nothing else marker based tracking will work too.
Edit: here's the depreciated code on github https://github.com/AVGP/goggle-paper
Doesn't use ARCore but instead marker based tracking. Better than nothing I suppose.
As of today, support for ARCore via the web (and thus A-Frame) is only available on Chrome browser with some Android devices.
Here are some great examples of working projects that you can build from:
https://github.com/chenzlabs/aframe-ar
https://aframe-ar.glitch.me/
New features such as image tracking are only available on Chrome Canary (experimental). See this example for image marker tracking:
https://arimg.glitch.me/
And associated documentation:
https://github.com/immersive-web/marker-tracking/blob/main/explainer.md
I have been working on adding background music to a Glitch project. I followed the Aframe.io documents to create a sound component and set it to automatically play upon running, however, when I try to run the project, the sound does not play automatically on my laptop. I have to open the Aframe inspector and un-pause my project for the music to begin. For some reason, I have not encountered this issue when I tried the same project on my phone. The sound played as expected once the program is up and running. I am not sure what is causing the sound to malfunction but any help is greatly appreciated. Here is the project I am working on: https://glitch.com/edit/#!/animation-animate?path=index.html%3A15%3A23
when working with sounds natively with Aframe, I had the same problem and one of the recommendations that I can give you is to play sounds with the HowlerJS sound library, which is compatible with most frameworks and also compatible with A-Frame
I share their page and the documentation, this library is very easy to use and implement to the project
https://howlerjs.com/
https://github.com/goldfire/howler.js#documentation
Autoplay audio on most modern browsers requires user interaction before enabling audio. You can put a div in front of your scene that upon click starts playing your background audio.
Check out a related SO question / answer for video autoplay that should help:
Autoplaying videosphere from A-frame is not working on any browser(Safari/Chrome)
Another user on A-Frame discord provided this example demo:
https://aframe-autoplay-background-music.glitch.me/
framers!
My VR app brings up a 3d photo menu, where I can select what kind of stereographic view works for my app. Some a frame apps (like Mozillas a frame painting app) do show in 3d. How do I ensure that my aframe shows in 3d?
My code is here: vr-hangman.glitch.me .
I would post a snippet but no part of the code stands out as having a bug.
When I use Chrome DevTools to fake a phone, I'm getting the error shown in this bug report: https://github.com/aframevr/aframe/issues/2385
I've figured out part of the answer, and resolved the bug above. I forked a glitch project to start out with, and it had an old version. However, my app still appears to be incompatible with the Samsung Internet VR experience.
So I forked an old A-Frame VR snippet on Glitch, so it was outdated with that bug.
Samsung Internet doesn't support "async function* runGame()" as a snippet. Even though it still updates the display.
I'm a beginner and I'm trying to use photoswiper in a PhoneGap app. I'm trying to use this example :
[http://jsfiddle.net/Gajotres/PFqVs/][1]
that works great in any browser, but just don't work on any device.
When I open, it's like I have a css issue since I don't see any king of style and when I touch any image, I just see it full size but can't swipe to see the next one.
Any help will be appreciated!
May be you should mention all sites with external resources in the WhiteList?
I have developed a mobile site using Icefaces-mobile framework in that I want to search the things based on area zoomed in on the mobile screen, for this users can zoom in/out & navigates the area but the problem is after doing zoom in/out/navigations 4 to 6 times browser becomes unresponsive. I think it must be problem with browsers capability of handling/execute the javascript(correct me if I m wrong).
I have generated latest API key for map using some standers steps given by google on their forum.
Thanks in Advance.
The stock Android browser does suffer from serious limitations, and it could be device performance limitations, as the previous poster mentioned. But you should also be careful that you're not inadvertently causing a memory leak in your own JavaScript. Are there DOM updates from Ajax interactions being generated during this? Check the Android LogCat messages to see the ICEfaces/ICEmobile logging which will show the updates. Check to ensure that if you're custom function is being re-run that you're not causing a memory leak there. If not, I doubt there's an issue with the GMap code and it's likely just a device limitation. Perhaps also put your gmap code in a separate HTML page without ICEmobile and see if you still have the problem.