热门标签 | HotTags
当前位置:  开发笔记 > 编程语言 > 正文

了解开发手机的各项参数之SystemProperties

SystemProperties这个涉及的东西比较多,我这里只讲点简单的概念和常用的属性.Android的系统属性,主要分为两种:1.用文件保存的持久属性mydroid

SystemProperties这个涉及的东西比较多,我这里只讲点简单的概念和常用的属性.


Android的系统属性,主要分为两种:

1. 用文件保存的持久属性

mydroid\bionic\libc\include\sys\_system_properties.h 这个文件中有定义:

/*
** Rules:
**
** - there is only one writer, but many readers
** - prop_area.count will never decrease in value
** - once allocated, a prop_info's name will not change
** - once allocated, a prop_info's offset will not change
** - reading a value requires the following steps
**   1. serial = pi->serial
**   2. if SERIAL_DIRTY(serial), wait*, then goto 1
**   3. memcpy(local, pi->value, SERIAL_VALUE_LEN(serial) + 1)
**   4. if pi->serial != serial, goto 2
**
** - writing a value requires the following steps
**   1. pi->serial = pi->serial | 1
**   2. memcpy(pi->value, local_value, value_len)
**   3. pi->serial = (value_len <<24) | ((pi->serial + 1) & 0xffffff)
*/

#define PROP_PATH_RAMDISK_DEFAULT  "/default.prop"
#define PROP_PATH_SYSTEM_BUILD     "/system/build.prop"
#define PROP_PATH_SYSTEM_DEFAULT   "/system/default.prop"
#define PROP_PATH_LOCAL_OVERRIDE   "/data/local.prop"
#define PROP_PATH_FACTORY          "/factory/factory.prop"

2.每次开机都会导入的Cache属性,Framework层通过:

frameworks\base\core\java\android\os\SystemProperties.java 这个类来操作.

Cache的存储方式为:

/*
 * Properties are stored in a hybrid trie/binary tree structure.
 * Each property's name is delimited at '.' characters, and the tokens are put
 * into a trie structure.  Siblings at each level of the trie are stored in a
 * binary tree.  For instance, "ro.secure"="1" could be stored as follows:
 *
 * +-----+   children    +----+   children    +--------+
 * |     |-------------->| ro |-------------->| secure |
 * +-----+               +----+               +--------+
 *                       /    \                /   |
 *                 left /      \ right   left /    |  prop   +===========+
 *                     v        v            v     +-------->| ro.secure |
 *                  +-----+   +-----+     +-----+            +-----------+
 *                  | net |   | sys |     | com |            |     1     |
 *                  +-----+   +-----+     +-----+            +===========+
 */


如何获取Android的系统属性

1.通过android.os.Build这个类,我们可以得到一些基本信息:

以下是Build类的源码:

/*
 * Copyright (C) 2007 The Android Open Source Project
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *      http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */

package android.os;

import com.android.internal.telephony.TelephonyProperties;

/**
 * Information about the current build, extracted from system properties.
 */
public class Build {
    /** Value used for when a build property is unknown. */
    public static final String UNKNOWN = "unknown";

    /** Either a changelist number, or a label like "M4-rc20". */
    public static final String ID = getString("ro.build.id");

    /** A build ID string meant for displaying to the user */
    public static final String DISPLAY = getString("ro.build.display.id");

    /** The name of the overall product. */
    public static final String PRODUCT = getString("ro.product.name");

    /** The name of the industrial design. */
    public static final String DEVICE = getString("ro.product.device");

    /** The name of the underlying board, like "goldfish". */
    public static final String BOARD = getString("ro.product.board");

    /** The name of the instruction set (CPU type + ABI convention) of native code. */
    public static final String CPU_ABI = getString("ro.product.cpu.abi");

    /** The name of the second instruction set (CPU type + ABI convention) of native code. */
    public static final String CPU_ABI2 = getString("ro.product.cpu.abi2");

    /** The manufacturer of the product/hardware. */
    public static final String MANUFACTURER = getString("ro.product.manufacturer");

    /** The brand (e.g., carrier) the software is customized for, if any. */
    public static final String BRAND = getString("ro.product.brand");

    /** The end-user-visible name for the end product. */
    public static final String MODEL = getString("ro.product.model");

    /** The system bootloader version number. */
    public static final String BOOTLOADER = getString("ro.bootloader");

    /**
     * The radio firmware version number.
     *
     * @deprecated The radio firmware version is frequently not
     * available when this class is initialized, leading to a blank or
     * "unknown" value for this string.  Use
     * {@link #getRadioVersion} instead.
     */
    @Deprecated
    public static final String RADIO = getString(TelephonyProperties.PROPERTY_BASEBAND_VERSION);

    /** The name of the hardware (from the kernel command line or /proc). */
    public static final String HARDWARE = getString("ro.hardware");

    /** A hardware serial number, if available.  Alphanumeric only, case-insensitive. */ 
    public static final String SERIAL = getString("ro.serialno");
  
    /** Various version strings. */
    public static class VERSION {
        /**
         * The internal value used by the underlying source control to
         * represent this build.  E.g., a perforce changelist number
         * or a git hash.
         */
        public static final String INCREMENTAL = getString("ro.build.version.incremental");

        /**
         * The user-visible version string.  E.g., "1.0" or "3.4b5".
         */
        public static final String RELEASE = getString("ro.build.version.release");

        /**
         * The user-visible SDK version of the framework in its raw String
         * representation; use {@link #SDK_INT} instead.
         * 
         * @deprecated Use {@link #SDK_INT} to easily get this as an integer.
         */
        @Deprecated
        public static final String SDK = getString("ro.build.version.sdk");

        /**
         * The user-visible SDK version of the framework; its possible
         * values are defined in {@link Build.VERSION_CODES}.
         */
        public static final int SDK_INT = SystemProperties.getInt(
                "ro.build.version.sdk", 0);

        /**
         * The current development codename, or the string "REL" if this is
         * a release build.
         */
        public static final String CODENAME = getString("ro.build.version.codename");

        /**
         * The SDK version to use when accessing resources.
         * Use the current SDK version code.  If we are a development build,
         * also allow the previous SDK version + 1.
         * @hide
         */
        public static final int RESOURCES_SDK_INT = SDK_INT
                + ("REL".equals(CODENAME) ? 0 : 1);
    }

    /**
     * Enumeration of the currently known SDK version codes.  These are the
     * values that can be found in {@link VERSION#SDK}.  Version numbers
     * increment monotonically with each official platform release.
     */
    public static class VERSION_CODES {
        /**
         * Magic version number for a current development build, which has
         * not yet turned into an official release.
         */
        public static final int CUR_DEVELOPMENT = 10000;
        
        /**
         * October 2008: The original, first, version of Android.  Yay!
         */
        public static final int BASE = 1;
        
        /**
         * February 2009: First Android update, officially called 1.1.
         */
        public static final int BASE_1_1 = 2;
        
        /**
         * May 2009: Android 1.5.
         */
        public static final int CUPCAKE = 3;
        
        /**
         * September 2009: Android 1.6.
         * 
         * 

Applications targeting this or a later release will get these * new changes in behavior:

*
    *
  • They must explicitly request the * {@link android.Manifest.permission#WRITE_EXTERNAL_STORAGE} permission to be * able to modify the contents of the SD card. (Apps targeting * earlier versions will always request the permission.) *
  • They must explicitly request the * {@link android.Manifest.permission#READ_PHONE_STATE} permission to be * able to be able to retrieve phone state info. (Apps targeting * earlier versions will always request the permission.) *
  • They are assumed to support different screen densities and * sizes. (Apps targeting earlier versions are assumed to only support * medium density normal size screens unless otherwise indicated). * They can still explicitly specify screen support either way with the * supports-screens manifest tag. *
  • {@link android.widget.TabHost} will use the new dark tab * background design. *
*/ public static final int DOnUT= 4; /** * November 2009: Android 2.0 * *

Applications targeting this or a later release will get these * new changes in behavior:

*
    *
  • The {@link android.app.Service#onStartCommand * Service.onStartCommand} function will return the new * {@link android.app.Service#START_STICKY} behavior instead of the * old compatibility {@link android.app.Service#START_STICKY_COMPATIBILITY}. *
  • The {@link android.app.Activity} class will now execute back * key presses on the key up instead of key down, to be able to detect * canceled presses from virtual keys. *
  • The {@link android.widget.TabWidget} class will use a new color scheme * for tabs. In the new scheme, the foreground tab has a medium gray background * the background tabs have a dark gray background. *
*/ public static final int ECLAIR = 5; /** * December 2009: Android 2.0.1 */ public static final int ECLAIR_0_1 = 6; /** * January 2010: Android 2.1 */ public static final int ECLAIR_MR1 = 7; /** * June 2010: Android 2.2 */ public static final int FROYO = 8; /** * November 2010: Android 2.3 * *

Applications targeting this or a later release will get these * new changes in behavior:

*
    *
  • The application's notification icons will be shown on the new * dark status bar background, so must be visible in this situation. *
*/ public static final int GINGERBREAD = 9; /** * February 2011: Android 2.3.3. */ public static final int GINGERBREAD_MR1 = 10; /** * February 2011: Android 3.0. * *

Applications targeting this or a later release will get these * new changes in behavior:

*
    *
  • The default theme for applications is now dark holographic: * {@link android.R.style#Theme_Holo}. *
  • On large screen devices that do not have a physical menu * button, the soft (compatibility) menu is disabled. *
  • The activity lifecycle has changed slightly as per * {@link android.app.Activity}. *
  • An application will crash if it does not call through * to the super implementation of its * {@link android.app.Activity#onPause Activity.onPause()} method. *
  • When an application requires a permission to access one of * its components (activity, receiver, service, provider), this * permission is no longer enforced when the application wants to * access its own component. This means it can require a permission * on a component that it does not itself hold and still access that * component. *
  • {@link android.content.Context#getSharedPreferences * Context.getSharedPreferences()} will not automatically reload * the preferences if they have changed on storage, unless * {@link android.content.Context#MODE_MULTI_PROCESS} is used. *
  • {@link android.view.ViewGroup#setMotionEventSplittingEnabled} * will default to true. *
  • {@link android.view.WindowManager.LayoutParams#FLAG_SPLIT_TOUCH} * is enabled by default on windows. *
  • {@link android.widget.PopupWindow#isSplitTouchEnabled() * PopupWindow.isSplitTouchEnabled()} will return true by default. *
  • {@link android.widget.GridView} and {@link android.widget.ListView} * will use {@link android.view.View#setActivated View.setActivated} * for selected items if they do not implement {@link android.widget.Checkable}. *
  • {@link android.widget.Scroller} will be constructed with * "flywheel" behavior enabled by default. *
*/ public static final int HOnEYCOMB= 11; /** * May 2011: Android 3.1. */ public static final int HONEYCOMB_MR1 = 12; /** * June 2011: Android 3.2. * *

Update to Honeycomb MR1 to support 7 inch tablets, improve * screen compatibility mode, etc.

* *

As of this version, applications that don't say whether they * support XLARGE screens will be assumed to do so only if they target * {@link #HONEYCOMB} or later; it had been {@link #GINGERBREAD} or * later. Applications that don't support a screen size at least as * large as the current screen will provide the user with a UI to * switch them in to screen size compatibility mode.

* *

This version introduces new screen size resource qualifiers * based on the screen size in dp: see * {@link android.content.res.Configuration#screenWidthDp}, * {@link android.content.res.Configuration#screenHeightDp}, and * {@link android.content.res.Configuration#smallestScreenWidthDp}. * Supplying these in as per * {@link android.content.pm.ApplicationInfo#requiresSmallestWidthDp}, * {@link android.content.pm.ApplicationInfo#compatibleWidthLimitDp}, and * {@link android.content.pm.ApplicationInfo#largestWidthLimitDp} is * preferred over the older screen size buckets and for older devices * the appropriate buckets will be inferred from them.

* *

Applications targeting this or a later release will get these * new changes in behavior:

*
    *
  • New {@link android.content.pm.PackageManager#FEATURE_SCREEN_PORTRAIT} * and {@link android.content.pm.PackageManager#FEATURE_SCREEN_LANDSCAPE} * features were introduced in this release. Applications that target * previous platform versions are assumed to require both portrait and * landscape support in the device; when targeting Honeycomb MR1 or * greater the application is responsible for specifying any specific * orientation it requires.

    *
  • {@link android.os.AsyncTask} will use the serial executor * by default when calling {@link android.os.AsyncTask#execute}.

    *
  • {@link android.content.pm.ActivityInfo#configChanges * ActivityInfo.configChanges} will have the * {@link android.content.pm.ActivityInfo#CONFIG_SCREEN_SIZE} and * {@link android.content.pm.ActivityInfo#CONFIG_SMALLEST_SCREEN_SIZE} * bits set; these need to be cleared for older applications because * some developers have done absolute comparisons against this value * instead of correctly masking the bits they are interested in. *

*/ public static final int HONEYCOMB_MR2 = 13; /** * October 2011: Android 4.0. * *

Applications targeting this or a later release will get these * new changes in behavior:

*
    *
  • For devices without a dedicated menu key, the software compatibility * menu key will not be shown even on phones. By targeting Ice Cream Sandwich * or later, your UI must always have its own menu UI affordance if needed, * on both tablets and phones. The ActionBar will take care of this for you. *
  • 2d drawing hardware acceleration is now turned on by default. * You can use * {@link android.R.attr#hardwareAccelerated android:hardwareAccelerated} * to turn it off if needed, although this is strongly discouraged since * it will result in poor performance on larger screen devices. *
  • The default theme for applications is now the "device default" theme: * {@link android.R.style#Theme_DeviceDefault}. This may be the * holo dark theme or a different dark theme defined by the specific device. * The {@link android.R.style#Theme_Holo} family must not be modified * for a device to be considered compatible. Applications that explicitly * request a theme from the Holo family will be guaranteed that these themes * will not change character within the same platform version. Applications * that wish to blend in with the device should use a theme from the * {@link android.R.style#Theme_DeviceDefault} family. *
  • Managed cursors can now throw an exception if you directly close * the cursor yourself without stopping the management of it; previously failures * would be silently ignored. *
  • The fadingEdge attribute on views will be ignored (fading edges is no * longer a standard part of the UI). A new requiresFadingEdge attribute allows * applications to still force fading edges on for special cases. *
  • {@link android.content.Context#bindService Context.bindService()} * will not automatically add in {@link android.content.Context#BIND_WAIVE_PRIORITY}. *
  • App Widgets will have standard padding automatically added around * them, rather than relying on the padding being baked into the widget itself. *
  • An exception will be thrown if you try to change the type of a * window after it has been added to the window manager. Previously this * would result in random incorrect behavior. *
  • {@link android.view.animation.AnimationSet} will parse out * the duration, fillBefore, fillAfter, repeatMode, and startOffset * XML attributes that are defined. *
  • {@link android.app.ActionBar#setHomeButtonEnabled * ActionBar.setHomeButtonEnabled()} is false by default. *
*/ public static final int ICE_CREAM_SANDWICH = 14; /** * December 2011: Android 4.0.3. */ public static final int ICE_CREAM_SANDWICH_MR1 = 15; /** * June 2012: Android 4.1. * *

Applications targeting this or a later release will get these * new changes in behavior:

*
    *
  • You must explicitly request the {@link android.Manifest.permission#READ_CALL_LOG} * and/or {@link android.Manifest.permission#WRITE_CALL_LOG} permissions; * access to the call log is no longer implicitly provided through * {@link android.Manifest.permission#READ_CONTACTS} and * {@link android.Manifest.permission#WRITE_CONTACTS}. *
  • {@link android.widget.RemoteViews} will throw an exception if * setting an onClick handler for views being generated by a * {@link android.widget.RemoteViewsService} for a collection container; * previously this just resulted in a warning log message. *
  • New {@link android.app.ActionBar} policy for embedded tabs: * embedded tabs are now always stacked in the action bar when in portrait * mode, regardless of the size of the screen. *
  • {@link android.webkit.WebSettings#setAllowFileAccessFromFileURLs(boolean) * WebSettings.setAllowFileAccessFromFileURLs} and * {@link android.webkit.WebSettings#setAllowUniversalAccessFromFileURLs(boolean) * WebSettings.setAllowUniversalAccessFromFileURLs} default to false. *
  • Calls to {@link android.content.pm.PackageManager#setComponentEnabledSetting * PackageManager.setComponentEnabledSetting} will now throw an * IllegalArgumentException if the given component class name does not * exist in the application's manifest. *
  • {@link android.nfc.NfcAdapter#setNdefPushMessage * NfcAdapter.setNdefPushMessage}, * {@link android.nfc.NfcAdapter#setNdefPushMessageCallback * NfcAdapter.setNdefPushMessageCallback} and * {@link android.nfc.NfcAdapter#setOnNdefPushCompleteCallback * NfcAdapter.setOnNdefPushCompleteCallback} will throw * IllegalStateException if called after the Activity has been destroyed. *
  • Accessibility services must require the new * {@link android.Manifest.permission#BIND_ACCESSIBILITY_SERVICE} permission or * they will not be available for use. *
  • {@link android.accessibilityservice.AccessibilityServiceInfo#FLAG_INCLUDE_NOT_IMPORTANT_VIEWS * AccessibilityServiceInfo.FLAG_INCLUDE_NOT_IMPORTANT_VIEWS} must be set * for unimportant views to be included in queries. *
*/ public static final int JELLY_BEAN = 16; /** * Android 4.2: Moar jelly beans! * *

Applications targeting this or a later release will get these * new changes in behavior:

*
    *
  • Content Providers: The default value of {@code android:exported} is now * {@code false}. See * * the android:exported section in the provider documentation for more details.
  • *
  • {@link android.view.View#getLayoutDirection() View.getLayoutDirection()} * can return different values than {@link android.view.View#LAYOUT_DIRECTION_LTR} * based on the locale etc. *
  • {@link android.webkit.WebView#addJavascriptInterface(Object, String) * WebView.addJavascriptInterface} requires explicit annotations on methods * for them to be accessible from Javascript. *
*/ public static final int JELLY_BEAN_MR1 = 17; } /** The type of build, like "user" or "eng". */ public static final String TYPE = getString("ro.build.type"); /** Comma-separated tags describing the build, like "unsigned,debug". */ public static final String TAGS = getString("ro.build.tags"); /** A string that uniquely identifies this build. Do not attempt to parse this value. */ public static final String FINGERPRINT = getString("ro.build.fingerprint"); // The following properties only make sense for internal engineering builds. public static final long TIME = getLong("ro.build.date.utc") * 1000; public static final String USER = getString("ro.build.user"); public static final String HOST = getString("ro.build.host"); /** * Returns true if we are running a debug build such as "user-debug" or "eng". * @hide */ public static final boolean IS_DEBUGGABLE = SystemProperties.getInt("ro.debuggable", 0) == 1; /** * Returns the version string for the radio firmware. May return * null (if, for instance, the radio is not currently on). */ public static String getRadioVersion() { return SystemProperties.get(TelephonyProperties.PROPERTY_BASEBAND_VERSION, null); } private static String getString(String property) { return SystemProperties.get(property, UNKNOWN); } private static long getLong(String property) { try { return Long.parseLong(SystemProperties.get(property)); } catch (NumberFormatException e) { return -1; } } }

那么就写一个例子,把Build中能查到的所有属性都打印出来吧,当然手机用的是我的花屏MX3.

public class MainActivity extends Activity {

	private TextView tv;

	@Override
	protected void onCreate(Bundle savedInstanceState) {
		super.onCreate(savedInstanceState);
		setContentView(R.layout.activity_main);
	
		StringBuffer sb = new StringBuffer();
		sb.append("ro.build.id"+" : "+Build.ID+"\n");
		sb.append("ro.build.display.id"+" : "+Build.DISPLAY+"\n");
		sb.append("ro.product.name"+" : "+Build.PRODUCT+"\n");
		sb.append("ro.product.device"+" : "+Build.DEVICE+"\n");
		sb.append("ro.product.board"+" : "+Build.BOARD+"\n");
		sb.append("ro.product.cpu.abi"+" : "+Build.CPU_ABI+"\n");
		sb.append("ro.product.cpu.abi2"+" : "+Build.CPU_ABI2+"\n");
		sb.append("ro.product.manufacturer"+" : "+Build.MANUFACTURER+"\n");
		sb.append("ro.product.brand"+" : "+Build.BRAND+"\n");
		sb.append("ro.product.model"+" : "+Build.MODEL+"\n");
		sb.append("ro.bootloader"+" : "+Build.BOOTLOADER+"\n");
		
		sb.append("ro.hardware"+" : "+Build.HARDWARE+"\n");
		sb.append("ro.serialno"+" : "+Build.SERIAL+"\n");
		sb.append("ro.build.type"+" : "+Build.TYPE+"\n");
		sb.append("ro.build.tags"+" : "+Build.TAGS+"\n");
		sb.append("ro.build.fingerprint"+" : "+Build.FINGERPRINT+"\n");
		sb.append("ro.build.date.utc"+" : "+Build.TIME+"\n");
		sb.append("ro.build.user"+" : "+Build.USER+"\n");
		sb.append("ro.build.host"+" : "+Build.HOST+"\n");
		sb.append("radioVersion"+" : "+Build.getRadioVersion()+"\n");
		
		sb.append("ro.build.version.incremental"+" : "+Build.VERSION.INCREMENTAL+"\n");
		sb.append("ro.build.version.release"+" : "+Build.VERSION.RELEASE+"\n");
		sb.append("ro.build.version.sdk"+" : "+Build.VERSION.SDK_INT+"\n");
		sb.append("ro.build.version.codename"+" : "+Build.VERSION.CODENAME+"\n");

		tv = (TextView) findViewById(R.id.show);
		tv.setText(sb.toString());

	}
}

运行截图:

2.通过反射,直接调用SystemProperties这个类的方法:

当手机通过adb连接电脑后,我们可以通过 adb shell getprop > d:\prop.txt 来获得系统的所有属性值.

而Build这个类获得的属性有限,所以通过反射,我们可以获得更多的信息.

我们发现,Build中有个用 hide标记的属性,让我们用反射把他们show出来

    /**
     * Returns true if we are running a debug build such as "user-debug" or "eng".
     * @hide
     */
    public static final boolean IS_DEBUGGABLE =
            SystemProperties.getInt("ro.debuggable", 0) == 1;

public class MainActivity extends Activity {

	private TextView tv;

	@Override
	protected void onCreate(Bundle savedInstanceState) {
		super.onCreate(savedInstanceState);
		setContentView(R.layout.activity_main);
	
		
		try {
			Class classT = Class.forName("android.os.SystemProperties");
			Method m = classT.getMethod("getInt", new Class[]{String.class,int.class});
			int isDebugable = (Integer) m.invoke(classT,new Object[]{"ro.debuggable",0});
			
			tv = (TextView) findViewById(R.id.show);
			tv.setText("       "+(isDebugable == 1));
		} catch (IllegalArgumentException e) {
			// TODO Auto-generated catch block
			e.printStackTrace();
		} catch (ClassNotFoundException e) {
			// TODO Auto-generated catch block
			e.printStackTrace();
		} catch (NoSuchMethodException e) {
			// TODO Auto-generated catch block
			e.printStackTrace();
		} catch (IllegalAccessException e) {
			// TODO Auto-generated catch block
			e.printStackTrace();
		} catch (InvocationTargetException e) {
			// TODO Auto-generated catch block
			e.printStackTrace();
		}

	}
}





推荐阅读
  • Google Play推出全新的应用内评价API,帮助开发者获取更多优质用户反馈。用户每天在Google Play上发表数百万条评论,这有助于开发者了解用户喜好和改进需求。开发者可以选择在适当的时间请求用户撰写评论,以获得全面而有用的反馈。全新应用内评价功能让用户无需返回应用详情页面即可发表评论,提升用户体验。 ... [详细]
  • VScode格式化文档换行或不换行的设置方法
    本文介绍了在VScode中设置格式化文档换行或不换行的方法,包括使用插件和修改settings.json文件的内容。详细步骤为:找到settings.json文件,将其中的代码替换为指定的代码。 ... [详细]
  • 本文讨论了一个关于cuowu类的问题,作者在使用cuowu类时遇到了错误提示和使用AdjustmentListener的问题。文章提供了16个解决方案,并给出了两个可能导致错误的原因。 ... [详细]
  • XML介绍与使用的概述及标签规则
    本文介绍了XML的基本概念和用途,包括XML的可扩展性和标签的自定义特性。同时还详细解释了XML标签的规则,包括标签的尖括号和合法标识符的组成,标签必须成对出现的原则以及特殊标签的使用方法。通过本文的阅读,读者可以对XML的基本知识有一个全面的了解。 ... [详细]
  • 自动轮播,反转播放的ViewPagerAdapter的使用方法和效果展示
    本文介绍了如何使用自动轮播、反转播放的ViewPagerAdapter,并展示了其效果。该ViewPagerAdapter支持无限循环、触摸暂停、切换缩放等功能。同时提供了使用GIF.gif的示例和github地址。通过LoopFragmentPagerAdapter类的getActualCount、getActualItem和getActualPagerTitle方法可以实现自定义的循环效果和标题展示。 ... [详细]
  • CF:3D City Model(小思维)问题解析和代码实现
    本文通过解析CF:3D City Model问题,介绍了问题的背景和要求,并给出了相应的代码实现。该问题涉及到在一个矩形的网格上建造城市的情景,每个网格单元可以作为建筑的基础,建筑由多个立方体叠加而成。文章详细讲解了问题的解决思路,并给出了相应的代码实现供读者参考。 ... [详细]
  • 本文介绍了Android 7的学习笔记总结,包括最新的移动架构视频、大厂安卓面试真题和项目实战源码讲义。同时还分享了开源的完整内容,并提醒读者在使用FileProvider适配时要注意不同模块的AndroidManfiest.xml中配置的xml文件名必须不同,否则会出现问题。 ... [详细]
  • Android源码深入理解JNI技术的概述和应用
    本文介绍了Android源码中的JNI技术,包括概述和应用。JNI是Java Native Interface的缩写,是一种技术,可以实现Java程序调用Native语言写的函数,以及Native程序调用Java层的函数。在Android平台上,JNI充当了连接Java世界和Native世界的桥梁。本文通过分析Android源码中的相关文件和位置,深入探讨了JNI技术在Android开发中的重要性和应用场景。 ... [详细]
  • Java学习笔记之面向对象编程(OOP)
    本文介绍了Java学习笔记中的面向对象编程(OOP)内容,包括OOP的三大特性(封装、继承、多态)和五大原则(单一职责原则、开放封闭原则、里式替换原则、依赖倒置原则)。通过学习OOP,可以提高代码复用性、拓展性和安全性。 ... [详细]
  • 本文介绍了如何使用C#制作Java+Mysql+Tomcat环境安装程序,实现一键式安装。通过将JDK、Mysql、Tomcat三者制作成一个安装包,解决了客户在安装软件时的复杂配置和繁琐问题,便于管理软件版本和系统集成。具体步骤包括配置JDK环境变量和安装Mysql服务,其中使用了MySQL Server 5.5社区版和my.ini文件。安装方法为通过命令行将目录转到mysql的bin目录下,执行mysqld --install MySQL5命令。 ... [详细]
  • 欢乐的票圈重构之旅——RecyclerView的头尾布局增加
    项目重构的Git地址:https:github.comrazerdpFriendCircletreemain-dev项目同步更新的文集:http:www.jianshu.comno ... [详细]
  • 本文整理了Java面试中常见的问题及相关概念的解析,包括HashMap中为什么重写equals还要重写hashcode、map的分类和常见情况、final关键字的用法、Synchronized和lock的区别、volatile的介绍、Syncronized锁的作用、构造函数和构造函数重载的概念、方法覆盖和方法重载的区别、反射获取和设置对象私有字段的值的方法、通过反射创建对象的方式以及内部类的详解。 ... [详细]
  • HDU 2372 El Dorado(DP)的最长上升子序列长度求解方法
    本文介绍了解决HDU 2372 El Dorado问题的一种动态规划方法,通过循环k的方式求解最长上升子序列的长度。具体实现过程包括初始化dp数组、读取数列、计算最长上升子序列长度等步骤。 ... [详细]
  • 高质量SQL书写的30条建议
    本文提供了30条关于优化SQL的建议,包括避免使用select *,使用具体字段,以及使用limit 1等。这些建议是基于实际开发经验总结出来的,旨在帮助读者优化SQL查询。 ... [详细]
  • Oracle10g备份导入的方法及注意事项
    本文介绍了使用Oracle10g进行备份导入的方法及相关注意事项,同时还介绍了2019年独角兽企业重金招聘Python工程师的标准。内容包括导出exp命令、删用户、创建数据库、授权等操作,以及导入imp命令的使用。详细介绍了导入时的参数设置,如full、ignore、buffer、commit、feedback等。转载来源于https://my.oschina.net/u/1767754/blog/377593。 ... [详细]
author-avatar
爱你真好958_358
这个家伙很懒,什么也没留下!
PHP1.CN | 中国最专业的PHP中文社区 | DevBox开发工具箱 | json解析格式化 |PHP资讯 | PHP教程 | 数据库技术 | 服务器技术 | 前端开发技术 | PHP框架 | 开发工具 | 在线工具
Copyright © 1998 - 2020 PHP1.CN. All Rights Reserved | 京公网安备 11010802041100号 | 京ICP备19059560号-4 | PHP1.CN 第一PHP社区 版权所有