I have an Android ICS 4.0.3 installed in my phone. I have created one Mobile Web Application (test url http://drupal.langoor.mobi), for which I serve the HTML page from the MySQL database in the backend dynamically.
Problem:
The html page is not rendered by the default stock browser of Android and Dolphin browser.
This problem does NOT occure in chrome, firefox, safari mobile browsers.
To figure out the problem, I followed these approaches:
Used Adobe Shadow to do remote inspect of the HTML Page, which did NOT help much becuase I was NOT able to see any error in content loading.
Assuming Javascript/jQuery conflicts to be a problem, I tried removing all the linked js files which are served dynamically from server (not Static), then the HTML page was rendering but with no style applied.
I tried searching and found this link but it's not helpful:
Android - html from android_assets in WebView, CSS not loading in ICS
Please help me out with this.
After digging more around Problem, I found that main cause for problem was, content being sent in Uncompressed format from Server and because of which Android ICS's default and Dolphin Browser are not able to render it properly.
Here is the link where i have mentioned exact cause of problem.
Enabling data compression for Apache2 + FastCGI setup
Thanks
Related
it's been a week since i'm looking for a solution to bypass the block on the android webview to simple pick up a file (client side) from a device to upload on a server.
I've read all the posts on StackOverflow but can't find a working solution. Many solutions are on android program language, not HTML!
Can someone suggest a working example?? i'm going crazy about that (a simple form that works on iOs and on mobile Chrome browser but not on webview based on Chromium!!).
I have got a fully working phonegap 1.6.1 application, built in HTML5. I'd like to make this page refresh itself from the internet (replace the in-app html file with the online one, and save it for later), but when it is not possible, just do nothing.
It is on Android (2.3.7 & 4.1.2)
Is it possible?
I would really appreciate if you could send me a code (script) that helps.
P. S. I'm doing the job in DreamWeaver without any databases, etc.
Thanks in advance!
You need to whitelist your website in order for it to be allowed to take over the WebView provided by PhoneGap.
http://docs.phonegap.com/en/1.9.0/guide_whitelist_index.md.html
https://build.phonegap.com/blog/access-tags
Are you wanting to replace the actual html with what is found on the corresponding web site or are you trying to update content on the page? One is possible the other is not as your html index is compiled into the adk and not really editable on the fly, per se. You may update content dymanically from the web, but I'm pretty sure it is impossible to re-compile your apk on the android device itself.
However, if your html file is nothing more than a web view or iframe of your web site, then it will work, provided the app may reach the internet. The problem is that your app will not work if not connected to the internet. However, you could write a js routine to pull a default html view when internet access cannot be had.
I have a web application that works perfectly well on Desktop Chrome browser, on IPhone and IPad browsers and android build in browser.
However when I tried to run it on the new Chrome for Android it does not works. I found out that the manifest file is not even queried (downloaded). The request for the file is never fired. At least it never arrives to the web server.
Does anybody know, is this feature (offline cache) supported for Chrome on Android? Or is there some other possibility why it would not work?
EDIT: First three lines from main index HTML which is the only HTML in the app.
<!DOCTYPE HTML>
<html manifest="resources/advanced/common/cache/application.appcache">
<head>
EDIT2:
The weirdest thing, it just started working. Today I sat down and tried to further test the issue. Out of the blue with no changes at all my web server started receiving requests for the manifest file. And all of a sudden the app just works. Now talk about strange.
According to here Chrome for Android does support the App Cache: http://html5test.com/compare/browser/chromemobile.html
Are you sure the HTML syntax is correct and that you have the right MIME type set up for the manifest file on your server? Reporting any errors that occur might help indicate the problem.
I have a full Jquery Mobile app the currently builds and looks fine in multiple browsers. I am currently working on getting the version ported using phonegap for android. As it loads up on the phone, it has several images that are loaded depending on localStorage (I originally used cookies but found some android devices aren't too friendly with that). Now, almost all of these triggers load images fine, except the last page. A certain set of images won't load, and I get the error (when running in an emulator Unknown chromium error: -6. Others on the page use the same process and have no problem, and all the images are referred to locally.
Why would this be happening and what can I do to fix this?
Turns out in the android browser, under phonegap, file names are case-sensitive. So it wasn't able to load things with capital letters and such.
I want to show wml page on android. I have designed small wml page. I am using Apache server to deploy the pages. But the page is not displaying. It is displaying just like xml page. I have added some line to mime.types which is given in following site
http://e-articles.info/e/a/title/How-To-Configure-Apache-or-IIS-Web-Server-to-Work-with-WML-~-Openwave-SDK/
Still it is not working on android emulator... any idea??
AFAIK, Android's edition of WebKit does not support WML. It is possible you can find some third-party WML app.
Im having a similar issue. I just finished our new website using WordPress. The site comes up but in XML format. The WordPress theme didn't load nor did any pictures. I used WordPress and a similar template to create another site and that is coming up fine. The only thing I can think of I did 301 redirects and maybe that is effecting the new site's display on Android devices.