Bernie's Blog - Latest Comments

Re: Validation with Android Saripaar

Ragunath Jawahar — Sat, 01 Aug 2015 22:32:57 -0000

You're welcome :)

Re: Validation with Android Saripaar

PRiya Bharath — Sat, 01 Aug 2015 22:23:54 -0000

wow! tks for replying but figured that out. :)

Re: Validation with Android Saripaar

Ragunath Jawahar — Sat, 01 Aug 2015 22:01:57 -0000

If you are using Gradle, use this one liner in your dependencies block,

compile 'com.mobsandgeeks:android-saripaar:2.0.0'

Re: Validation with Android Saripaar

PRiya Bharath — Sun, 05 Apr 2015 08:03:19 -0000

Hi, how do you go about actually adding this library in Android Studio?

Re: A crazy property market

Nick — Tue, 17 Dec 2013 03:30:27 -0000

That's me in the photo...light green shirt guy... ya I still remember it was crazy queuing for hours and went in picked the unit within 1 min. Luckily managed to get the right unit although I would prefer klcc view unit.

Re: Android Kiosk Application

Nikos — Wed, 04 Dec 2013 05:26:21 -0000

Hi,
Thanks for this. Could you please tell me what I need to do in order to show the System UI Bar again.. I haven't tried to hide it yet, but Id'like to know how I can switch back
thanks

Re: Private: Retaining Fragments in ViewPagers

Kashban — Fri, 09 Aug 2013 02:14:02 -0000

Use a GUI-less fragment with setRetainInstance(true) to store any data to big to go into Bundles during configuration changes.

More about it here:

http://www.vogella.com/arti...

Re: Private: Retaining Fragments in ViewPagers

Kashban — Fri, 09 Aug 2013 02:11:33 -0000

You mistake setRetainInstance(true) with configChanges=orientation in the manifest.

With setRetainInstance(true) the fragment is detached from the activity when it's destroyed during configuration changes and reattached as soon as the activity has been recreated. Other than with configChanges=orientation the GUI actually IS recreated using the resource identifiers. Since I do not hold any references to Context-based entities, there is no risk of leaking the old context.

But, and that is the main point to get a fluid and performant orientation change, the data cached in the fragment instance is still there and that's where all the stuff goes which is too expensive to recreate or reload. All I do is to store the bitmaps of the thumbnails in an array in the fragment and when rebuilding the GUI after the orientation change grab those instead of reload them from disk and do all the bitmap operations again (sizing, rotating). This is the memory caching you mentioned.

Yes, I could use a seperate worker fragment to cache data between orientation changes and I probably will in future versions of my app, but so far everything works smoothly even with retaining the instance of a fragment with GUi. I'm using ViewPager to switch fragments, not backstack.

As you say setRetainInstance does not work with fragments on the backstack so here a worker fragment is required.

For a complete explanation and tutorial see

http://www.vogella.com/arti...

Re: Private: Retaining Fragments in ViewPagers

Josh Brown — Thu, 08 Aug 2013 23:49:45 -0000

Also setRetainInstance() doesn't work on Fragments in the back stack

Re: Private: Retaining Fragments in ViewPagers

Josh Brown — Thu, 08 Aug 2013 23:45:14 -0000

You WANT the GUI to be recreated on orientation change. Otherwise changes due to resource qualifiers and other things can be missed. You also risk leaking the old Context (Views hold references to the Context that created them). This sounds to me like you need to be memory-caching your thumbnails, but that's a totally separate issue. Another possible approach is creating another Fragment whose only job is to hold your cached images. This way your Views still get recreated appropriately and your non-UI fragment can retain its instance.

Re: Private: Retaining Fragments in ViewPagers

Kashban — Thu, 08 Aug 2013 02:37:50 -0000

See my answer to Josh.

Re: Private: Retaining Fragments in ViewPagers

Kashban — Thu, 08 Aug 2013 02:36:46 -0000

setRetainInstance(true) is the only way I found to make orientation changes in my ViewPager performant. In my App I initially load some thumbnails from pictures on SD card lazily, so GUI takes some time to complete. I then cache the bitmaps of those thumbnails in an array in the fragment, because reloading them takes some time.

With setRetainInstance(false) and only relying to the ViewPager on every orientation change the GUI is completely recreated, loading thumbnails included.

With setRetainInstance(true) the ViewPager grabs hold of the "old" fragment instance and the orientation change is smooth and fast.

So far I didn't came across any issues by using a fragment with setRetainInstance(true) in the ViewPager.

Re: Private: Install CyanogenMod 10.1 on the Nexus Q

Mihai — Thu, 11 Jul 2013 14:31:20 -0000

I had the same experience: no image in recovery mode on monitor, worked fine on TV.
Dell monitor, Sony TV.
I did adb shell while in recovery mode and saw some messages about display not being HDCP compliant. That may explain why monitors don't work.

Re: Java Development Kit v7 on MacOS X 10.8.3

Ashton — Sun, 19 May 2013 13:34:23 -0000

Thanks for the write up. I follow this exactly and saw the "you need java SE6.." and then I did the link but when I run eclipse is see: "Alert: Failed to create the Java Virtual Machine."

Any chance you could point me in the right direction? I am actually not even sure how to go back to Oracle or Apple version of java 6 if needed.. so I have myself in a hole

Thanks!

Re: Java Development Kit v7 on MacOS X 10.8.3

Guest — Wed, 24 Apr 2013 21:02:30 -0000

Re: Java Development Kit v7 on MacOS X 10.8.3

Guest — Wed, 24 Apr 2013 21:02:20 -0000

Test

Re: Setting Up OpenVPN on an EC2 Instance

Darragh O'Reilly — Tue, 23 Apr 2013 06:59:33 -0000

nice one. Thanks.

Re: Cheap data plans for existing DiGi users

Bernie Eng — Mon, 18 Feb 2013 01:24:29 -0000

How did you get the free SIM? And why not DiGi? I take it you're not happy with the service? :)

Re: Cheap data plans for existing DiGi users

Palmdoc — Sat, 16 Feb 2013 17:39:57 -0000

I got a free SIM and one month use free. RM19 for 1 Gb. Not likely to take the bait.

Re: Private: Install CyanogenMod 10.1 on the Nexus Q

ebernie — Wed, 23 Jan 2013 05:09:10 -0000

Nice :)

I would've thought connecting to monitor would've fared better vs a TV.

Re: Private: Install CyanogenMod 10.1 on the Nexus Q

Declan Shanaghy — Wed, 23 Jan 2013 05:05:07 -0000

Hmm, strange. I disconnected from my PC monitor and hooked it up to my TV and display worked fine.

TV is a Sharp Aquos 37" (LC-37GP1U)
Monitor is a Gateway LP2417 24"

Re: Private: Install CyanogenMod 10.1 on the Nexus Q

ebernie — Wed, 23 Jan 2013 04:46:06 -0000

Have you tried booting into CWM from bootloader?

If you've got the Q booted up, boot into booloader (adb reboot bootloader), and your Q should be glowing red. Verify you're in bootloader (fastboot devices should show your device connected) and then finally (fastboot boot [your downloaded recovery]).

Re: Private: Install CyanogenMod 10.1 on the Nexus Q

Declan Shanaghy — Wed, 23 Jan 2013 04:40:15 -0000

I have the same problem. No display in recovery mode. I have CM 10.1 pushed to /sdcard, how can I install it without using the display?

Re: Private: Retaining Fragments in ViewPagers

Bernie Eng — Tue, 22 Jan 2013 19:14:14 -0000

Hi Josh,

- setRetainInstance(boolean) is no longer called.
- the problem I faced was the inability of the adapter to retrieve its previous Fragments. Any idea how one can go about retrieving existing fragments in an Adapter's getItem() method?
- onSaveInstanceState(Bundle): what about objects that can't fit into bundles?

Re: Private: Retaining Fragments in ViewPagers

Josh Brown — Tue, 22 Jan 2013 15:14:36 -0000

This is a VERY dangerous approach!. setRetainInstance(true) should only be called on Fragments that don't have a UI. Fragments already have a mechanism for persisting their state: onSaveInstanceState(). Then in your onCreate() and/or your onCreateView() you read the values from the bundle passed in (it will be null on the first run). FragmentManager ensures everything gets linked back up properly, even if you're using ViewPagers. All you should have to do is set the adapter.