Why Google chooses odd versions of Kernel tree ?

by gulshan . karmani » Tue, 06 Jan 2009 06:26:30 GMT


Sponsored Links
 Hi All,

      Can anyone explain why Google chooses odd versions of Kernel
tree ?

       It is valid not to use the latest version for developments but
why always odd ones like 25 and 27.


rgds,
Gulshan
--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



Why Google chooses odd versions of Kernel tree ?

by Brian Swetland » Tue, 06 Jan 2009 07:37:13 GMT


 [gulshan.karm...@gmail.com]

2.6.25 was the most recent released kernel when we were finalizing
things for 1.0.  2.6.27 was the most recent released kernel when we
moved forward from 2.6.25. 

We need a stable tree for development, and we currently base that tree
on a released kernel (not a -rc).  We will periodically shift
development forward to the newest released kernel as baseline.

There's nothing special about odd-numbered kernel versions.

Brian

--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---


Sponsored Links


Why Google chooses odd versions of Kernel tree ?

by gulshan karmani » Tue, 06 Jan 2009 11:51:30 GMT


 Thanks to clarify Brian.

Right now any possibilty to move from 2.6.27 to 2.6.28 ? Is there any
roadmap or plan  ?








--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



Other Threads

1. How can I change the color of the "Search" button on Searchable Activity?

Hi all,
Firstly, we can see here:
{sdk-path}/docs/reference/android/app/
SearchManager.html#SearchabilityMetadata

In particular, we can change the text in the "Search" button through
below:
android:searchButtonText ----If provided, this text will replace the
default text in the "Search" button.

Then, I need to change the color of the "Search" button. Maybe I need
to change the android framework, is it? what can I do?

Any suggests will be helpful. Thank you very much.

-- 

2. RemoteService and RemoteServiceBinding - Different package (apk) - Problem

Hi!!

I have made two different packages for API Demo sample -
RemoteService in Service app package (Service.apk)
RemoteServiceBinding in Client app package(Client.apk)
(two different apk and two different projects in eclipse)

The Service app offer services which Client app binds to and utilizes.
The Service app gets started during BOOT COMPLETE.

This model works great when I do a full source build(without eclipse).

But when I make them under Eclipse, and my Client app invokes
registerCallback method on Service app interface, the
IRemoteServiceCallback instance(interface implemented in Client app)
is received null in Service app.

I have confirmed that mCallback (object passed) is not null.

I couldn't observe any error in logs. What could be the problem?

Thanks in advance
Ash

#####################
Client app - code
#####################
private IRemoteServiceCallback mCallback = new
IRemoteServiceCallback.Stub() {
        /**
         * This is called by the remote service regularly to tell us
about
         * new values.  Note that IPC calls are dispatched through a
thread
         * pool running in each process, so the code executing here
will
         * NOT be running in our main thread like most other things --
so,
         * to update the UI, we need to use a Handler to hop over
there.
         */
        public void valueChanged(int value) {
            mHandler.sendMessage(mHandler.obtainMessage(BUMP_MSG,
value, 0));
        }
    };

 private ServiceConnection mConnection = new ServiceConnection() {
        public void onServiceConnected(ComponentName className,
                IBinder service) {
            // This is called when the connection with the service has
been
            // established, giving us the service object we can use to
            // interact with the service.  We are communicating with
our
            // service through an IDL interface, so get a client-side
            // representation of that from the raw service object.
            mService = IRemoteService.Stub.asInterface(service);
            mKillButton.setEnabled(true);
            mCallbackText.setText("Attached.");

            // We want to monitor the service for as long as we are
            // connected to it.
            try {
                mService.registerCallback(mCallback);
            } catch (RemoteException e) {
                // In this case the service has crashed before we
could even
                // do anything with it; we can count on soon being
                // disconnected (and then reconnected if it can be
restarted)
                // so there is no need to do anything here.
            }

######################
Service app code
######################
private final IRemoteService.Stub mBinder = new IRemoteService.Stub()
{
        public void registerCallback(IRemoteServiceCallback cb) {
            if (cb != null) mCallbacks.register(cb);
        }
        public void unregisterCallback(IRemoteServiceCallback cb) {
            if (cb != null) mCallbacks.unregister(cb);
        }
    };

####################
PROBLEM---------
---------------------------------
The registerCallback gets invoked on Service app code but parameter
'cb' is null
#####################

-- 

3. Updating SDK through AVD

4. loop sound

5. R file not generating automatically

6. Tasks Running in Androi

7. How to exclude com.android.internal.R from my apk