Status bar area not covered when activity is resumed

by groob » Wed, 11 May 2011 04:42:35 GMT


Sponsored Links
 Hello!

I'm experiencing very nasty bug trying to implement Admob in my
application.
I thought the problem is in my code, but after some investigation I
found it present also in Android-Banner-Essentials example (available
for download here: 
 http://code.google.com/mobile/ads/docs/android/fundamentals.html )
I wonder if anyone ever met this problem or maybe knows how to deal
with it.

Basically, when application has both status and title bar disabled, it
should use full screen.
Banner Essentials example displays nothing but Admob banner on the
very top of area available.
I downloaded the example, changed only two things:
- added my publisher ID to compile properly and receive any ads ;)
- added one param to activity's manifest to disable title and status
bar:
android:theme="@android:style/Theme.NoTitleBar.Fullscreen"

Compiled binary, no matter what device is it launched on (tried Nexus
One, G1, Desire, different Android versions), is affected with the
same issue:
- when ad banner is displayed press Home,
- once taken back to home screen press and hold Home to see recently
launched apps,
- select back Banner Essentials app.
My tests reveal that with 50% reproduction chance Admob banner doesn't
go back to its position -the very top of the screen.
To show better what I mean I prepared three screenshots:
 http://goo.gl/u9DTl 

Important notices:
- when app is resumed normally, banner is displayed just below status
bar, and slides up until is aligned to the top screen border,
- when error appears the banner doesn't move at all,
- I couldn't reproduce the issue with any other interrupt (pressing
Back, Power Button),
- I think it may be somehow connected to gaining/losing foucs (see
screenshots).

My app is bit more complex than Banner Essentials so I started with
searching the issue in my code, with no luck, thus tried to simplify
the situation as much as possible and here are the results.

Does anyone know what may be causing the problem? Maybe some
additional flags or properties has to be set to handle this behaviour?

Any advice will be appreciated.

Regards.

-- 



Other Threads

1. bind to a remore service

Hallo,

i have made an application that is consisted of an activity and a
service.The service has an interface (created by an aidl file)
including methods implemented in the service.My activity binds to the
service and calls some methods of the service.All good till now.My
problem is when i want to bind to a service that belongs to a
different package from my activity.My activity doesn't have visibility
of the remote interface and i cannot import it :

public class Client extends Activity {
    /** Called when the activity is first created. */
        IGps mservice=null;
    @Override
    public void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        setContentView(R.layout.main);
        Intent i=new Intent();
        i.setComponent(new ComponentName("aexp.share.sharedapp3",
"aexp.share.sharedapp3.Service_impl"));
        bindService(i, conn, Context.BIND_AUTO_CREATE);

    }

    ServiceConnection conn=new ServiceConnection() {

                @Override
                public void onServiceDisconnected(ComponentName name) {
                        Log.e("TAG","DISCONNECTED");

                }

                @Override
                public void onServiceConnected(ComponentName name, IBinder 
service)
{

                        mservice=IGps.Stub.asInterface(service);
                        try
                        {
                                double a=mservice.getLat();
                                String a_str=Double.toString(a);
                                Log.e("TAG",a_str);
                        }
                        catch(RemoteException e)
                        {

                        }

                }
        };
}

Here i cannot see the IGps interface,Am i doing something wrong?

-- 

2. Eclair build bootup issue on Beagle board.

Hi,

We are facing a bootup issue on Beagle board, I could see the logs as shown
below.


I/SystemServer( 829): System Content Providers

I/ActivityThread( 829): Publishing provider settings:
com.android.providers.settings.SettingsProvider

I/SystemServer( 829): Battery Service

W/dalvikvm( 829): No implementation found for native
Lcom/android/server/BatteryService;.native_update ()V

W/dalvikvm( 829): threadid=15: thread exiting with uncaught exception
(group=0x4001b170)

E/AndroidRuntime( 829): Uncaught handler: thread android.server.ServerThread
exiting due to uncaught exception

E/AndroidRuntime( 829): *** EXCEPTION IN SYSTEM PROCESS. System will crash.

E/AndroidRuntime( 829): java.lang.UnsatisfiedLinkError: native_update

E/AndroidRuntime( 829): at
com.android.server.BatteryService.native_update(Native Method)

E/AndroidRuntime( 829): at
com.android.server.BatteryService.update(BatteryService.java:200)

E/AndroidRuntime( 829): at
com.android.server.BatteryService.<init>(BatteryService.java:138)

E/AndroidRuntime( 829): at
com.android.server.ServerThread.run(SystemServer.java:140)

E/AndroidRuntime( 829): Crash logging skipped, no checkin service

I/Process ( 829): Sending signal. PID: 829 SIG: 9

Any pointers to skip this to bring up the board quickly will be of great
help.

Karthik

-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: 

3. Suspicious TCP RST packets while device is sleeping.

4. concept of "user name"

5. Coloring Default Buttons - color filter only on unfocused state

6. Porting Android SDK For large screen devices.

7. Educational Resources