We have an HTML5 app that uses web sql, offline functionalitiy and the geolocation API with the enableHighAccuracy option set true.
Since iOS6 position.coords.accuracy often reports high values (100m+) even after a couple minutes warm up outdoors whereas iOS5 went to and stayed at 5m accuracy fairly quickly the same on iPhone 4S, iPad 3.
One workaround is to kill all apps then run the Apple map app, press the current location button and then start the HTML5 web app in which case things work as expected.
Thanks to SO12503815 we are not running mobile-web-app-capable.
Any workarounds, aside from coding a native app ?
Related
What versions of chrome are compatible with loadrunner 11.52 on windows?
I saw a post that said version 26 was supported, but Im looking to record using chrome version 13 on windows 7
NB: Browser version is mandated by the project.
NNB: Assume playback is browser agnostic - as the commands generated will send the raw HTTP(S) requests to the target server, without any UI
All versions when using the proxy recording model.
I just recorded again , and quit before I got the site up (so recorded for about 4 minutes with an empty chrome screen and a spinning timer) to see what Loadrunner recorded - I got web_url, web_add_cookie & web_custom_request for google safebrowsing & related api - ...
Unless you work for Google or have their expressed written permission then you do not use automated tools against their site. This is why the sample applications exist. Or, you may download and install onto a server you own, control, manage, ... any of the thousands of open source applications which are available on the market.
Pointing an automated tool at a site you don't own, manage or control is no different than driving down the street and shooting at parked cars, homes and signs just because they are there and you can. Pointing a performance testing tool at the same is akin to pointing a piece of field artillery at someone's home. This is something you do not engage in as a performance test professional.
I am developing a game using PhoneGap iOS. I integrated Ads in it using Mobclix as well as iAds. Also I integrated Flurry in the game for analytics.
But after integrating Ads in the game I am facing some performance issues in the game on some devices. They are as follows :-
Ipod touch :- Slow response to touch events, Animations are too slow, Rendering has become slow.
Iphone :- Animations are slow but better than Ipod touch.
It works fine on Ipad.
I have used PhoneGap to port our HTML5 code on the devices.
I checked Removing the Ads and Flurry Code then game runs Fine. I also searched extensively for this problem, but couldn't find a suitable answer. Looking forward to getting some help, here.
I've noticed (from first hand experience) that the Flurry HTML5 SDK can slow your app down, massively. It communicates with the server by inserting SCRIPT tags into the HEAD section of the DOM, which has three drawbacks that I can see:
Some browsers (e.g. mobile Safari on iOS it seems) will wait for HEAD scripts to resolve before running any other scripts
If you make multiple Flurry calls, you'll soon reach the browser's concurrency limit for multiple downloads from the same server, since each call creates a new SCRIPT tag.
The script tags are never removed, so the DOM keeps growing.
One solution is to try the native Flurry SDK for the phone(s) you are targeting, but that's not an option if you are supporting browser WebApps, and increases your development time & download size for native apps.
I find it pretty shocking that the Flurry HTML5 SDK is so inefficient. Back to Google Analytics I guess.
Any ideas on how to get memory usage, Javascript errors, etc. from Chrome running on Google TV?
I have a page that is getting the "Aw, snap!" error when viewed in the Chrome browser on Google TV (Logitech). The page is fairly simple, but it does load a bunch of photos, though only up to 7 at a time (the photos are loaded using JavaScript). The photos are 640x480 and ~500KB each. They are stacked and the top one fades out (using jQuery) until all are gone then a new batch is loaded.
It only crashes on Google TV (it runs fine on Windows 7) and it takes a while before it crashes (I can get it down to about 10-20 minutes before it crashes by turning on a "fast mode" on our page).
Unfortunately I can't figure out how to get any information that might help me debug it. It would be cool to be able to get Chrome's developer tools on the Google TV device.
Currently there is no way to pull debug information from Chrome on Google TV. The Logitech Review is rather limited in it's RAM and you may be encountering an issue there (I don't know how big these images are). It is also possible that you have a memory leak in your javascript code. This might be hidden on other systems running a browser as there would be more memory to buffer you from seeing the error.
My advice would be to create a virtual machine (VirtualBox is free and runs on Windows) - create a VM with limited memory (256Mb Ram for instance) and install Ubuntu or some other flavor of linux that can run Chrome. Then run your app in the VM and see what happens.
Failing that you could always try loading the imaged with static image tags and see if it is the images that are causing the crash. If it's not the images then I would say look at your JS code closely and perhaps run it through JSLint (http://www.jslint.com/)
We have used HTML5s navigator.geolocation and found it to be very good on iOS and Android smartphones. Now the users want the same HTML5 web app to run on a laptop with external GPS. Using Windows 7 on the laptop I just can't figure a way to share the location to a HTML5 browser (tried Safari, FF, IE, Chrome). For testing I am using a GlobalStat BU-353 USB GPS which works standalone and I have found GPSDirect (cool freeware) to feed that signal to Win7 Sensor Location Services but still the HTML5 browsers do not see the GPS.
Anyone had any luck with this please ?
I was looking for similar solution and found this: GpsGate.
It is standalone application which connects to almost any GPS device and publishes it's data in several forms including browsers (through Javascript API which in turn makes jsonp call to http://localhost:12175/gps/[getVersion|getGpsInfo]?jsonp=padding). It's not compatible with Geolocation API, but I think writing simple adapter shouldn't take much time. Another good thing is that it's Express edition is free for both private and commercial use (link).
EDIT: After some digging I found this patch which adds geolocation compatible adapter for GpsGate to some other geolocation library.
Issue 45535 is beginning to address this in the Chromium feature requests. As of Jan 5 2012, the feature has been marked as "started".
Feature request: http://code.google.com/p/chromium/issues/detail?id=45535
As long as you only need a single browser for your client solution (and not a universal solution) this will solve your problem.
A great method to start testing and keeping an eye out for this issue is to download Chrome Canary, which is usually 2 versions ahead of the Chrome release. I'm right now using v18 on Canary and it's great since I've been keeping an eye on the websocket schema changes.
You can find Canary here: http://tools.google.com/dlpage/chromesxs
I'm using gears.js and geo.js in an attempt to cover all grounds, in terms of finding the user's geolocation. So if the user is using something less than IE9, I would possibly prompt install for Google Gears, so I know for desktop, IE7 + is covered.
For the mobile devices I'm looking at geo
which covers quite a few mobile devices.
I'm wondering if there is anything which accounts for WP7 geolocation as well using JavaScript, and if there is better ways of handling GeoLocation for all devices.
Not entirely sure how Google Gears work for IE7/8 also, so any elaboration on that would be great. (I'm not assuming Gears is the only/best way forward though for non geolocation supported browsers, so any correction on that is fine!)
I ran into this today: http://geosenseforwindows.com/ it basically gives Wifi based geolocation to the Windows 7 Sensor API:
Geosense is a Windows Sensor that
provides the Location and Sensors
platform in Windows 7 with accurate
and reasonably ubiquitous positioning
information without requiring or the
assistance of GPS hardware, enabling
more practical location-based
applications and scenarios on Windows
7.
Unfortunately I don't think IE can access that Sensor API without resorting to COM calls in your javascript.
We also use the free/commercial GpsGate, which lets any browser on a Windows machine directly access a real hardware GPS device on the computer.
In answer to the WP7 part of your question.
There is CURRENTLY no way to get geolocation from in the browser in IE on Windows Phone 7. This should change when the next version of the browser is released.