developer.android.com breaks on G1 ?

by Sen » Wed, 04 Mar 2009 11:19:53 GMT


Sponsored Links
 Has anyone noticed that if you try to browse the Reference section of
developer.android.com, it doesn't let you scroll down to the bottom of
the page for a majority of the documentation?

I'd like to site in bed and browse some docs... this makes it
impossible...

Then again I don't have the RC33 update (because I have a developer
phone) so maybe it's fixed.

I just think it's kinda sad...  But then again maybe its strange
behavior with my phone...
--~--~---------~--~----~------------~-------~--~----~



developer.android.com breaks on G1 ?

by Jean-Baptiste Queru » Wed, 04 Mar 2009 22:06:52 GMT


 Yes, it's a known issue. From what I know the browser in android has
issues with CSS overflow on divs.

JBQ






-- 
Jean-Baptiste M. "JBQ" Queru
Android Engineer, Google.

Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.

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


Sponsored Links


developer.android.com breaks on G1 ?

by CKinniburgh » Wed, 04 Mar 2009 23:50:16 GMT


 I believe I have noticed this, or a similar issue on an iPhone today.
The Dev guides were cut off at the bottom of the page.




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



developer.android.com breaks on G1 ?

by meaglith » Sun, 15 Mar 2009 13:13:03 GMT


 You maybe access developer.android.com by Opera Mini.






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



Other Threads

1. Application forces close when launched from the market

Hi!

I have uploaded application to market and met weird problem which I
never received before - when I click "Open" button when the
application is installed I receive error dialog and the application is
forced to close. I do not have this problem when start application
from desktop launcher panel. I have already receive 2 stars for that
though the exception even comes not from my cod - very unpleasant
surprize from market app.

Application uses vibration and declares corresponding uses-permission
"android.permission.VIBRATE" - this is what the exception tells me
about, but I can't see such problem with other apps that use vibration
on market.


Here the exception:

Starting activity: Intent { action=android.intent.action.MAIN
flags=0x10000000 comp={org.sadko.boozemeter/
org.sadko.boozemeter.BoozeMeter} }
W/ActivityManager(   49): Permission Denial: starting Intent
{ action=android.intent.action.MAIN flags=0x10000000 comp=
{org.sadko.boozemeter/org.sadko.boozemeter.BoozeMeter} } from
ProcessRecord{432fba88 5964:com.android.vending/10004} (pid=5964,
uid=10004) requires
android.permission.VIBRATE
D/AndroidRuntime( 5964): Shutting down
VM
W/dalvikvm( 5964): threadid=3: thread exiting with uncaught exception
(group=0x4000fe68)
E/AndroidRuntime( 5964): Uncaught handler: thread main exiting due to
uncaught
exception
E/AndroidRuntime( 5964): java.lang.SecurityException: Permission
Denial: starting Intent { action=android.intent.action.MAIN
flags=0x10000000 comp={org.sadko.boozemeter/
org.sadko.boozemeter.BoozeMeter} } from ProcessRecord{432fba88
5964:com.android.vending/10004} (pid=5964, uid=10004) requires
android.permission.VIBRATE
E/AndroidRuntime( 5964):        at android.os.Parcel.readException
(Parcel.java:
1066)
E/AndroidRuntime( 5964):        at android.os.Parcel.readException
(Parcel.java:
1054)
E/AndroidRuntime( 5964):        at
android.app.ActivityManagerProxy.startActivity
(ActivityManagerNative.java:
998)
E/AndroidRuntime( 5964):        at
android.app.Instrumentation.execStartActivity(Instrumentation.java:
1436)
E/AndroidRuntime( 5964):        at
android.app.Activity.startActivityForResult(Activity.java:
2528)
E/AndroidRuntime( 5964):        at android.app.Activity.startActivity
(Activity.java:
2572)
E/AndroidRuntime( 5964):        at
com.android.vending.controller.AssetInfoActivityController.handleLaunch
(AssetInfoActivityController.java:510)
E/AndroidRuntime( 5964):        at
com.android.vending.controller.AssetInfoActivityController.handleRequest
(AssetInfoActivityController.java:136)
E/AndroidRuntime( 5964):        at
com.android.vending.AssetInfoActivity.onClick(AssetInfoActivity.java:
284)
E/AndroidRuntime( 5964):        at android.view.View.performClick
(View.java:
2110)
E/AndroidRuntime( 5964):        at android.view.View.onTouchEvent
(View.java:
3524)
E/AndroidRuntime( 5964):        at android.widget.TextView.onTouchEvent
(TextView.java:
4659)
E/AndroidRuntime( 5964):        at android.view.View.dispatchTouchEvent
(View.java:
3179)
E/AndroidRuntime( 5964):        at
android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:
857)
E/AndroidRuntime( 5964):        at
android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:
857)
E/AndroidRuntime( 5964):        at
android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:
857)
E/AndroidRuntime( 5964):        at
android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:
857)
E/AndroidRuntime( 5964):        at
android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:
857)
E/AndroidRuntime( 5964):        at
android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:
857)
E/AndroidRuntime( 5964):        at
android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:
857)
E/AndroidRuntime( 5964):        at
com.android.internal.policy.impl.PhoneWindow
$DecorView.superDispatchTouchEvent(PhoneWindow.java:
1593)
E/AndroidRuntime( 5964):        at
com.android.internal.policy.impl.PhoneWindow.superDispatchTouchEvent
(PhoneWindow.java:1089)
E/AndroidRuntime( 5964):        at
android.app.Activity.dispatchTouchEvent(Activity.java:
1873)
E/AndroidRuntime( 5964):        at
com.android.internal.policy.impl.PhoneWindow
$DecorView.dispatchTouchEvent(PhoneWindow.java:
1577)
E/AndroidRuntime( 5964):        at android.view.ViewRoot.handleMessage
(ViewRoot.java:
1140)
E/AndroidRuntime( 5964):        at android.os.Handler.dispatchMessage
(Handler.java:
88)
E/AndroidRuntime( 5964):        at android.os.Looper.loop(Looper.java:
123)
E/AndroidRuntime( 5964):        at android.app.ActivityThread.main
(ActivityThread.java:
3739)
E/AndroidRuntime( 5964):        at
java.lang.reflect.Method.invokeNative(Native
Method)
E/AndroidRuntime( 5964):        at java.lang.reflect.Method.invoke
(Method.java:
515)
E/AndroidRuntime( 5964):        at com.android.internal.os.ZygoteInit
$MethodAndArgsCaller.run(ZygoteInit.java:
739)
E/AndroidRuntime( 5964):        at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:
497)
E/AndroidRuntime( 5964):        at dalvik.system.NativeStart.main
(Native Method)




Here is application manifest:

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
      package="org.sadko.boozemeter" android:versionCode="3"
android:versionName="1.0.2">
    <application android:icon="@drawable/icon" android:label="@string/
app_name" android:permission="android.permission.VIBRATE"
android:enabled="true" android:debuggable="true">
        <activity android:label="@string/app_name"
android:name="BoozeMeter">
            <intent-filter>
                <action android:name="android.intent.action.MAIN" />
                <category
android:name="android.intent.category.LAUNCHER" />
            </intent-filter>
        </activity>
    <activity android:name="ResultShower"></activity>
<activity android:name="TremorSensor"></activity>


<activity android:name="AboutActivity" android:label="@string/
about_caption"></activity>
<activity android:name="com.sadko.bursaq.GotoBursaqActivity"
android:label="@string/get_bursaq_caption"></activity>
</application>

<uses-sdk android:minSdkVersion="2"></uses-sdk>
<uses-permission android:name="android.permission.VIBRATE"></uses-
permission>
</manifest>
--~--~---------~--~----~------------~-------~--~----~

2. redirect stdout

hi all,

i am running a benchmark on android which outputs the logs to the
screen.unfortunately i dont see the logs on 'adb logcat'.Is there a
way i can save the output logs on the screen ?      thanks

--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-kernel+unsubscr...@googlegroups.com
website: 

3. Activity / Screen rotation relationship

4. OpenGL .dae model loader

5. Documentation inconsistency in Service.onBind() intent extras availability

6. launch an app with widget

7. Percentage of loading in WebView