Memory question

by Phil Nickinson » Sun, 18 Apr 2010 20:40:00 GMT


Sponsored Links
 Curious why spec sheets would list ROM at 512MB, but on-device "phone
memory" is listed at 748MB. Is that just because of the usual app
storage limitation, or is it something else?

Can someone set me straight here? Thanks!

--



Memory question

by Matt Kanninen » Tue, 20 Apr 2010 09:09:27 GMT


 What device would you be talking about?



>


Sponsored Links


Memory question

by Phil Nickinson » Tue, 20 Apr 2010 13:16:10 GMT


 The Incredible. HTC's looking into it for me ...





> >



Memory question

by Matt Kanninen » Wed, 21 Apr 2010 02:42:27 GMT


 Got a link?





> > >



Memory question

by Phil Nickinson » Wed, 21 Apr 2010 02:45:43 GMT


 About halfway down in the "settings" section. All the written specs we've
received -- and there have been mistakes in there -- list it as 512. Just a
partition thing, probably?

 http://www.androidcentral.com/verizon-droid-incredible-screenshot-gallery 







> > > >



Memory question

by Al Sutton » Wed, 21 Apr 2010 03:03:17 GMT


 table width="100%">I'll bet it's 512ish MB *RAM*, and the 8GB Flash has a quarter gigabyte app partition (around 768 MB).


Al.

--

* Looking for Android Apps? - Try http://andappstore.com/ *

======
Funky Android Limited is registered in England & Wales with the company number  6741909. 

The views expressed in this email are those of the author and not necessarily those of Funky Android Limited, it's associates, or it's subsidiaries.



On 20 Apr 2010, at 19:45, Phil Nickinson wrote:

About halfway down in the "settings" section. All the written specs we've received -- and there have been mistakes in there -- list it as 512. Just a partition thing, probably?

http://www.androidcentral.com/verizon-droid-incredible-screenshot-gallery



On Tue, Apr 20, 2010 at 1:42 PM, Matt Kanninen


Memory question

by Phil Nickinson » Wed, 21 Apr 2010 03:07:11 GMT


 But the usual Android 512MB app limit still applies, right?









>> > > >



Memory question

by Al Sutton » Wed, 21 Apr 2010 03:15:59 GMT


 table width="100%">What 512MB app limit?


--

* Looking for Android Apps? - Try http://andappstore.com/ *

======
Funky Android Limited is registered in England & Wales with the company number  6741909. 

The views expressed in this email are those of the author and not necessarily those of Funky Android Limited, it's associates, or it's subsidiaries.



On 20 Apr 2010, at 20:06, Phil Nickinson wrote:

But the usual Android 512MB app limit still applies, right?

On Tue, Apr 20, 2010 at 2:00 PM, Al Sutton <a...@funkyandroid.com> wrote:


I'll bet it's 512ish MB *RAM*, and the 8GB Flash has a quarter gigabyte app partition (a



Other Threads

1. Questions about Activity.finish() and a couple of other things.

I'm following the tutorial found at
http://developer.android.com/resources/tutorials/testing/activity_test.html
to learn how to test on the Android. I'm noticing some weirdness and I
can't find any explanations yet online. So I'm hoping someone here can
help me understand this.

I wrote the method testStateDestroy(). Here's the code:

public void testStateDestroy()
    {
        mActivity.setSpinnerPosition(TEST_STATE_DESTROY_POSITION);
        mActivity.setSpinnerSelection(TEST_STATE_DESTROY_SELECTION);

        mActivity.finish();

        boolean flag = mActivity.isFinishing();
        mActivity = null;
        System.gc();

        mActivity = this.getActivity();

        int currentPosition = mActivity.getSpinnerPosition();
        String currentSelection = mActivity.getSpinnerSelection();

        assertEquals(TEST_STATE_DESTROY_POSITION, currentPosition);
        assertEquals(TEST_STATE_DESTROY_SELECTION, currentSelection);
    }

The setUp() method calls mActivity.getActivity() which starts the
Spinner app up. So far so good. In this method, after setting the
spinner selection, I call finish(). The app goes away. I capture the
isFinishing() flag and it is indeed true. I set mActivity to null and
ask the GC kindly to do a pass. It may or may not, but let's give it a
shot. Then I call getActivity() again. The application does NOT start
up...I'm still at the Android start screen. Yet I have a valid
activity object because the following lines of code that get the
position and selection of the spinner work and the asserts pass.

Okay, so in debug, after setUp calls getActivity, I use the emulator
to change the selection of the spinner to something else. I enter this
method and I can see the selection changes. The same behavior
ensues...no app shows up after calling getActivity(), but the values
retrieved are the right ones which were set before calling finish().

As a side note, the tutorial asks to include a testPreconditions()
method. This method never gets called even though the tutorial states
that it will be called once per test suite. So that's another issue
that I'm noticing.

All the code I've written comes straight from the tutorials except the
line to set mActivity to null and the call to System.gc, which have no
real effect here. If I remove these lines of code I see the same
behavior.

Does anyone have any insight into what's going on with the activities
and the testPreconditions() method? Thanks!

-- 

2. List view problem

Hi,
    I am using a list view and and the onListItemClick() method. The
problem I am having is that when I press the back button and tap on
another item on the list the position value stays the same. Has anyone
else encountered this problem?

thanks,

Clive

--

3. which is the fastest encryption scheme that i can use with android?

4. CONFIG_PM_SLEEP and CONFIG_USER_WAKELOCK (with Gingerbread)

5. Custom Menu entries for Kernel

6. how to load intro while setting up huge database

7. How to make an efficient rendering loop with cache-based scrolling/zooming