Android Dev

Open Source Foursquare client for Android.

惠普旗下的Palm公司已确认，公司副总裁、webOS UI设计负责人、著名移动用户体验设计大师Matias Duarte将离职。而来自Google方面的消息，Duarte将加入Google，出任Android用户体验总监一 职。由于历史上Matias Duarte在跳槽时，总是带着自己的团队同行，所以很可能Palm原设计团队的其他人也会随之而去。这其实并不奇怪，Duarte本来就是 Android之父Andy Rubin 2000年创办的公司Danger的设计总监。 2005年Danger被微软收购后（最近推出的Kin手机来自Danger），Duarte加盟 Helio公司（由EarthLink与SK合资创办，现在是Springt-Nextel的一部分）任副总裁，负责体验设计。2007年加盟Palm， 主导webOS的UI设计。无论是Danger、Helio还是Palm webOS，其界面设计都广受好评，可惜产品本身生不逢时。尤其是webOS， 曾被许多开发者称为在创新性上唯一能与iPhone相提并论的操作系统。

Matias Duarte，在产品管理、信息架构、交互设计、视觉设计、用户研究等领域均有很深造诣的设计大 师。1996年毕业于马里兰大学。拥有计算机科学学位，并辅修了艺术和艺术史。大学期间曾经开发了一款免费游戏软件，并连续三年获得Linux Journal的读者选择奖。1996年为Atari公司（乔布斯曾经在此打工）的游戏担任过主设计师。1997年在创业公司 MagicArts任合伙人兼设计副总裁。2000年加入Danger，任设计总监，领导了SideKick产品的设计。2005年加盟Helio。 2007年加盟Palm。 曾荣获2002年Wired Rave大奖，美国国家设计奖提名，拥有9个美国实用专利和2个设计专利。 他的自我介绍上这样描述自己的目标：To create great products that make people smile.（创造使人微笑的优秀产品。）

Sunil回信了。 Hi Luke, Rest assured the apps are fine. We are migrating people over the new system and will let you know when it's complete. Showing false does not impact your earnings or account. 他只字未提Superdroid的事件。

http://groups.google.co.nz/group/android-developers/browse_thread/thr... 这个有个账号做adsense网页的，账号被封 又打开的，半年前的事情。 在android developer人多些

google最后给的判决书： Hi, After further review from our abuse team we have confirmed that your account that was closed was modifying the ad behavior which is strictly prohibited as stated in the AdSense policies. These types of violations pose a significant risk to advertisers and for this reason we can no longer work with you through any partnering AdSense account or product offering. This will be the final communication about this issue. Please do not reply to this email as you will not receive a response. Thank you for your understanding. Google AdSense 我们自始至终都不知道原因。

我Google了下 "modifying the ad behavior " 就是指你修改了 Google提供的 adsense js code 或者 sdk 唯一有可能的就是这里了 GoogleAdView adView = (GoogleAdView) activity.findViewById(R.id.ad<http://r.id.ad/> ); if (adView != null) { View vc = adView.getCurrentView(); if (vc instanceof WebView) { ((WebView) vc).destroy(); } View vn = adView.getNextView(); if (vn instanceof WebView) { ((WebView) vn).destroy(); } } 因为用了adsense之后 我们的程序老是crash 从stack trace看是因为Google adsense sdk 引起的. 资源没有释放. 然后去Adsense的那个mail list AFMA 问了 碰到2个都有同样问题的 然后有人给了个code 因为adsense sdk没有destroy ad view  所以要手动destroy下 我们就在每个有ads的activty的 onDestroy 加上这段 就好了 程序没有crash了 结果就被搞了 连负责我们android adsense sales都事先不知道 adsense team就直接把我们封了 还在beta 测试阶段的东西 还有bug  我们只是加了这个保证他资源正常释放不会影响到我们程序 结果就挂了 而且Google的态度巨NX无比 连个申述的途径都没有  只是给了个link类似事后调查

我刚刚给我的sale发了一封信： Hi Sunil, It has been long that I haven't talked to you. I have a question, when I went to the application register page, I found the page layout was changed and some of my apps were gone. For example UK TV Guide, Australia TV Guide, etc. Also, the published status are all "false". I am confused because I am still seeing my ads are clicked in the daily report. Is there anything wrong? I am nervous because I just knew that an AdSense developer's account was disabled without any warning,  and the developers themselves don't know the reason. I don't want that happened on me so I really appreciate your comment. below is the letter in AFMA group. Looking forward to your reply. Thanks. Cheers, Luke 接下来我引用了superdroid的信。看看他怎么说吧。

If you're managing the cursor yourself the cleanest way to go is probably this: Cursor cursor = getContentResolver().query(...); try {     // read from the cursor and do stuff } finally {     if (cursor != null) cursor.close(); }

Another option if you still want to use Activity.managedQuery() is to get your information and then: stopManaging(cursor); cursor.close(); Cheers, Justin Android Team @ Google

Adobe Reader for Android支持多指手势，包括双指缩放、双击缩放、拖动等等，还包括一个新的reflow模式，会将宽度又宽文字又多的页面在小屏幕上也能方便阅读。不过Adobe Reader for Android不支持搜索，不支持那些被密码保护的文档。 在菜市场里搜索Adobe Reader for Android就可以找到。

// Get display for detecting the phone orientation display = ((WindowManager) getSystemService(WINDOW_SERVICE)).getDefaultDisplay(); // Get the orientation int orientation = display.getOrientation();

android.view.Display class provide a simple way to determine the phone orientation.

Google Chrome to Phone Extension is a project consisting of a Chrome Extension, Android App, and supporting AppEngine server that enables users to send links from their Chrome desktop browser to their Android device using Android's Cloud to Device Messaging service.

The android:inputType attribute has three pieces: The class is the overall interpretation of characters. The currently supported classes are text (plain text), number (decimal number), phone (phone number), and datetime (a date or time). The variation is a further refinement on the class. In the attribute you will normally specify the class and variant together, with the class as a prefix. For example, textEmailAddress is a text field where the user will enter something that is an e-mail address (foo@bar.com) so the key layout will have an '@' character in easy access, and numberSigned is a numeric field with a sign. If only the class is specified, then you get the default/generic variant. Additional flags can be specified that supply further refinement. These flags are specific to a class. For example, some flags for the text class are textCapSentences, textAutoCorrect, and textMultiline.

    <EditText android:id="@+id/edtInput"        android:layout_width="0dip"        android:layout_height="wrap_content"        android:layout_weight="1"        android:inputType="textShortMessage|textAutoCorrect|textCapSentences|textMultiLine"        android:imeOptions="actionSend|flagNoEnterAction"        android:maxLines="4"        android:maxLength="2000"        android:hint="@string/compose_hint"/>

onSaveInstanceState() is called by Android if the Activity is being stopped and may be killed before it is resumed! This means it should store any state necessary to re-initialize to the same condition when the Activity is restarted. It is the counterpart to the onCreate() method, and in fact the savedInstanceState Bundle passed in to onCreate() is the same Bundle that you construct as outState in the onSaveInstanceState() method.

Note that saveState() must be called in both onSaveInstanceState() and onPause() to ensure that the data is saved. This is because there is no guarantee that onSaveInstanceState() will be called and because when it is called, it is called before onPause().

The density of a screen is important because, other things being equal, a UI element (such as a button) whose height and width are defined in terms of screen pixels will appear larger on the lower density screen and smaller on the higher density screen.

The density-independent pixel is equivalent to one physical pixel on a 160 dpi screen, the baseline density assumed by the platform (as described later in this document). At run time, the platform transparently handles any scaling of the dip units needed, based on the actual density of the screen in use. The conversion of dip units to screen pixels is simple: pixels = dips * (density / 160). For example, on 240 dpi screen, 1 dip would equal 1.5 physical pixels. Using dip units to define your application's UI is highly recommended, as a way of ensuring proper display of your UI on different screens.