Android 2.1 WebKit and applicationCache

by hansamann » Thu, 13 May 2010 11:40:23 GMT


Sponsored Links
 Hi all,

I am trying to use the Android 2.1 WebKit applicationCache but I
notice several differences to the iPhone 3/4(beta) implementation. Can
anyone tell me what the current status is and if it is in a usable
state?

Here are  my observations that I can share:

- initial caching works, but instead of sending a checking event first
as on the iPhone, it will just send out the progress events and then
the final cache event
- once you reload the page, it just shows the noupdate event. no
checking before that
- even if you update the manifest, it will not notice that. It seems
webkit on android does not check the manifest after the initial
caching.
- forcing an update with applicationCache.update() also does not work.

That leaves the current implementation in a pretty unusable state,
your users would presumably never get an updated cache once the inital
caching has run.

Has anyone else experience with this or knows when applicationCache is
supposed to be fixed/working?

Thanx a lot!
Sven

--



Android 2.1 WebKit and applicationCache

by hansamann » Fri, 14 May 2010 01:53:53 GMT


 Hi, is there anyone who could answer this question or tell me where to
best post this? It's an important issue for me right now...

Thanx,
Sven



>


Sponsored Links


Re: Re: Android 2.1 WebKit and applicationCache

by Christopher Dale » Wed, 20 Apr 2011 21:27:57 GMT


 I would also be interested to know the current state of the applicationCache 
implementation. I am running into issues in the Android browser with going 
offline where I have no issues on Chrome. I think it would also be helpful 
if there was a central place where the statuses of implemented standards 
were layed out by android version so developers knew what they had to work 
with.

Thanks,

Christopher

-- 



Other Threads

1. Updated .apk wants uninstall first

I have been developing an app I want to share with friends and family for 
beta testing before I publish it to the android market. Problem is, since 
I've already had them install a previous version of the app, that when I 
send them the new .apk to install the installer wants the already installed 
app to be uninstalled first before the new version can be installed or 
updated.

Is this something I'm doing wrong in my program? I want the SQLite DB to 
always be intact and never loose data which is what happens when someone has 
to reinstall/update the app.

Please help! Thanks so much.

Derek

-- 

2. What I found using big images on an activity

How big is drawable/domo2048?
Is it 4MPixel. This means that, in the best scenario, it occupies 8Mbytes. 
Then, depending on how you show it, you have a scaled (down) version of the 
image as well.

Note that the memory held by the raw data of the image (the 8Mbytes if 
RGB_565 is used) is not 'seen' by the DalvikVM. This causes the DalvikVM not 
to call the garbage collector when it actually should (DalvikVM thinks the 
memory limit has not yet been reached to warrant a call to the garbage 
collector, because it doesn't 'see' the 8MByte of your image).

This means that even if there is 8Mbyte available but not in one contiguous 
chunk of memory, you may get an out-of-memory error.

Try this: in onDestroy, set the background-drawable of the ImageView with 
id=R.id.domo2048 to null and call System.gc(). See if your memory issues get 
any less.

As a side note:
Don't assign 4MPixel images to small screens. You'll be waisting a LOT of 
memory. :)
Pre-scale the image to one that would fit on the phone with the largest 
screen that you support, not any bigger than that.


-- 

3. SOOT : Kapan Ya Background Gmail Bisa Ganti Warna

4. Help required in application structuring

5. Live Report Promo Optimus 2X at Pasific Place

6. [WTS] Sticker Android - Waterproof & Rare Design - Satu"nya di Indonesia

7. How does the ActivityStack behave when it contains thousands of Activities?