I just want to ask if there is now a workaround to solve the file upload problem in Android when there's not enough RAM after file selection.
Look at these URLs:
Android browser refreshes page after selecting file via input element
http://code.google.com/p/android/issues/detail?id=53088
https://github.com/kostysh/File-uploading-component-for-Sencha-Touch/issues/5
My smart phone Samsung Galaxy xcover has 37,70 MB RAM.
When I click a standard HTML file upload control on a web page and select a file (from gallery, camera, camcorder etc.) Android kills the browser instance to get some free RAM, then Android starts the browser again and refreshes the web page.
I think there must be a technical solution some day ...
Has anybody new information about this problem?
Thomas
Related
Installed expo-image-picker, calling launchImageLibraryAsync. This works completely fine on Emulator.
On a real android device (Samsung A3, API 24), and picking images from the Library, I sometimes get an error Uri lacks 'file' scheme: content://com.android.provider.media.documents/documents/<imagename..>.
My understanding is that it's images which have been saved NOT by the device camera, e.g. whatsapp, other apps using the camera. Images which were taken on the device camera work OK and have a local path.
Is there a known way to deal with this? I can't seem to stop the user seeing/picking these images, and can't pass in any options to ignore this error (or fail gracefully if multiple images are selected and only 1 fails). Currently we just catch and give a generic error which is a bit mmm.
I've come across a specific issue that seems to have started happening in the very recent versions of Chrome, I can't specify the exact version when this started happening but I will try to fully explain the scenario.
I have a PWA application that is normally run in a chromeless window on an Android 7 tablet. When it is offline and all the applications files are cached (verified in devtools) it will not download cached PDFs. However, if I run the application in normal Chrome, still offline, the PDFs will download correctly.
The error (shown as a toast message) is simply "Cannot display PDF (xxx.pdf cannot be opened)" No errors show in the console. I added a console.log message to note when these PDF files are being served and it is only shown when not in chromeless mode.
if (requestUrl.pathname.startsWith('/Content/maps/') || requestUrl.pathname.startsWith('/Content/pictures/')) {
console.log("Serving pdf or image file");
event.respondWith(servePDF(event.request));
return;
}
To me, this indicates that something is different while running PWAs in chromeless mode and I cannot find a work around or fix for this issue.
As part of a study, I use a website (.NET) to administer an experiment via a tablet and 4G WiFi modem. The experiment involves downloading a total of 70MB of images from the website as it goes from page to page, with each page downloading around 5MB of images each.
I have written an application cache manifest file "dvams.appcache" in which I list all of the image files and other resources which I wish to have cached locally on my tablet. In the aspx page using the image files, I have included the manifest attribute (manifest="dvams.appcache") in the HTML element, as directed.
However, when I run my experiments out in the field, Chrome (version 43) does not seem to take any notice of the manifest file, and the files do not persist locally on my tablet for more than a short period of time, after which Chrome behaves as if they have been removed from the cache.
In every experimental run I do, the browser continues to retrieve a lot of files it has already downloaded from the website. The speed of my 4G connection varies markedly, and downloading these files time and time again is excruciatingly slow, with pages taking as long as 2 or 3 minutes to download the required image files.
My theory is that the file cache size needs to be increased to accommodate the 70MB of files I wish to be cached, or that an "offline mode" setting that used to exist in earlier versions of chrome (but did appear to work) needs to be set somewhere. I have seen how a cache size parameter "--disk-cache-size=104857600" can be added as a parameter to the chrome executable file when called from Windows, but cannot figure out how to accomplish this on Android 5.1.
Why are these cached files being deleted? How can I force Chrome/Android to ALWAYS go to the cache for images it has already downloaded, and make these offline files persist PERMANENTLY unless I manually tell Chrome to clear them?
I'm working with a special image format and was creating something to dynamically generate it. I went to try it in mobile Chrome (it isn't displayable in the browser but it could be downloaded) and suddenly it opened about fifty new tabs! I fought with my browser to close them all but it just kept creating more.
http://www.sudomemo.net/images/dynamic/profile/540417_0BC7C6632064B_047.ntft
There are no redirects, no scripts. It's an image.
Any clue as to why this is happening? Have I discovered a Chrome bug?
Google Chrome 39.0.2171.93 (Official Build)
Revision bec62c44cbc7da9f6a507873382ebc111d66e9d7-refs/branch-heads/2171#{#449}
OS Android 4.4.2; XT1031 Build/KXB20.9-1.10-2.27
Steps to reproduce: Tested on Android Kit Kat, with the only installed browser being Google Chrome.
Open Chrome and go to the above link.
I figured it out a while ago.
To make it short, mobile Chrome didn't know how to handle the file, as it had a text/HTML content type but wasn't parsable as text or HTML. It got passed to the Android Content Provider, (that bit which gives you options between which apps you can use to open something), which immediately returned it to Chrome, as it's the only browser on my phone, opening it in a new tab. This looped over and over, quickly causing my phone to slow down and crash.
I successfully managed to add on my android desktop a link to a web page.
I did that from Chrome, I added my url as a favourite, then from the favourite screen there is a link to add it on the desktop.
However, when I launch the url from the shortcut created on the android desktop, then the URL is started from the standard android brower, not from Chrome??
With my GALAXY S3 it works fine, Chrome is used.
But from the GALAXY S4, it does not!
it does not even ask which browser I want to use.
And I have no means to select "open with..."
Maybe I could from EsExplorer, but where can I find the shortcut?
in which folder are they stored?
thanks
Rod
I think you selected Always... at the first time when opening url, try this: http://www.howtogeek.com/howto/43135/how-to-change-the-default-application-for-android-tasks/
What i'm try to say is i don't think the problem is with chrome. It's your Android settings. And for the second part i don't think you can access your home screen elements from File Explorer.