Review Acer Iconia Tab

by Gregorius Bimantoro » Sat, 14 May 2011 14:06:22 GMT

Sponsored Links
 Ada di 

Mau sedikit review,

Setelah memakai 1 harian, batt memang benar tahan 6-7 jam, enak bener
mindah-mindah file tinggal colok USB, dan hmmm...pengalaman pake honeycomb
beda yah. Unik aja kayak komputer yang dulu cuma di-angan-angan, maksudnya
dari style UI-nya. Banyak apps yang masih belum bisa muncul full screen?
Gampang kok, ikuti saja yang dipakai Galaxy Tab dengan SpareParts di Android
Market, youtube
disini< ;source=web&cd=3&ved=0CCsQtwIwAg&>.
Rooting sudah bisa pakai Gingerbreak
1.20<> ;.
Caranya mudah, pastikan ada microSD terpasang ya..lihat
disini<> ;

Selanjutnya untuk keperluan bisnis Docs2Go (pakai key dari applanet)
asik...Games sih lancar, ndak pernah nge-lag dengan 1GB RAM yah..should be
much better dari pesaing yang ada. Baca pake feedly mobile enak,
hmm..aplikasi2 lain semua berjalan lancar. Yang belum berhasil adalah
read/write, hehe berniat merubah sedikit di /system.

Kebetulan saya khusus testing untuk medical, bener2...dreams come true ini.
Google Body itu buat menjelaskan seluruh bagian tubuh jadi mudah, aplikasi2
medis semuanya jalan dengan tampilan yang tidak aneh (jujur saja galaxy Tab
jadi aneh tampilannya untuk banyak apps), tentu dengan sedikit hack.

Untuk beratnya sih sedikit terasa lebih enteng dari iPad1, dipegang nyaman,
tapi kalau lama-lama pegel juga tuh. Dibandingkan iPad2? IMHO cheaper
alternative. Oia protective case bahannya mirip iPad, lebih banyak lipetan
[image: Protective case for A500 now
available!-acer-a500-cover.jpg]<> ;

Berikut spec Acer Iconia Tab A500 :
[image: WiFi-only Acer Iconia Tab A500 hitting Best Buy with a $450 price
Acer Iconia Tab A500 Specification:

   - Android 3.0 Honeycomb
   - 10.1-inch 1280800 TFT WXGA display
   - NVIDIA Tegra 250 Cortex A9 1GHz processor (dual-core)
   - 1 GB RAM
   - 32 GB Internal Memory / microSD supporting up to 32 GB cards
   - 5 MP rear-facing camera / 2 MP front-facing camera
   - Two 3260 mAh Li-polymer batteries
   - WiFi 802.11 a/b/g/n, bluetooth, and GPS

G. Bimantoro
[y!] thebratasena


Re: Review Acer Iconia Tab

by Iqbal Z » Sat, 14 May 2011 14:58:15 GMT

*pura pura ngga baca review dahsyat ini*

On May 14, 2011 1:06 PM, "Gregorius Bimantoro" <> 
Android ;source=web&cd=3&ved=0CCsQtwIwAg&> ;


Sponsored Links

Other Threads

1. Background Task Result Reporting Hypothetical


I've been doing background tasks and they work, but I'm interested in 
best practice. I think this has been talked about on the list before, 
but I haven't seen a clear discussion, and one of Streets of Boston's 
posts yesterday got me thinking.

Say you have a background chore that needs to return results to the 
UI. You use AsyncTask or cook-up something on your own and the work 
gets done.

Now you need to notify the UI. So you post a Runnable or Message. Fine.

But let's say the user moved away from the invoking activity while 
the background thread was running, or changed orientation, so the 
result receiving activity is either no longer foreground or different.

If the user moved away from the initiating activity, the results 
arrive in the handler of a "zombie" activity no longer being 
displayed (but which can, I guess, now be garbage collected since the 
reference to the activity in the result message has been released). 
Is there anything to worry about here, or is it OK to mindlessly 
update a non-displayed view tree....?

If orientation has changed, the results are delivered to the "wrong" 
handler in the old activity. This is more of a problem. I've hacked 
around this in various ways, but they are all kind of clunky -- 
involving having activities "register" in some way with the 
background task so results go to the correct handler. Is there a more 
elegant approach?

I may be totally over thinking this, since my previous approaches 
work, but this morning I'm off to write more background code and I'd 
like to handle result delivery in a way that is "pretty." I also want 
to be sure I'm not making some obvious conceptual mistake in my 
mental model of all this.

Thanks smart people,

-- Ward


2. Executing code after installation

Hi I would like to be able to do some installation routines when APK
is installed and some clean up when APK is removed. I know there is
some broadcast intent to know when an application is installed or
removed , but the application in question does not receive those
intents. Is there any way to an an APK to execute some initialization
code after have just been installed e cleanup code when is about to be

My application uses other APKs as plugins. At every startup  it has to
check for new plugins what  is a cumbersome task . I would like to
make them smarter by implement a self registration mechanism during

Andr Oriani
SW Engineer


3. Are Binder objects leaked ?

4. Do i need to release the static variable and remove the listener when the app is closed?

5. Do i need to release the static variable and remove the listener when the app is closed?

6. stopService slow to act

7. why this code can't work