WO2018090719A1 - 一种自动切换默认Launcher的方法、装置及终端 - Google Patents

一种自动切换默认Launcher的方法、装置及终端 Download PDF

Info

Publication number
WO2018090719A1
WO2018090719A1 PCT/CN2017/103294 CN2017103294W WO2018090719A1 WO 2018090719 A1 WO2018090719 A1 WO 2018090719A1 CN 2017103294 W CN2017103294 W CN 2017103294W WO 2018090719 A1 WO2018090719 A1 WO 2018090719A1
Authority
WO
WIPO (PCT)
Prior art keywords
launcher
default
log information
information
sample
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2017/103294
Other languages
English (en)
French (fr)
Inventor
辛奇
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangzhou Shiyuan Electronics Thecnology Co Ltd
Original Assignee
Guangzhou Shiyuan Electronics Thecnology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Guangzhou Shiyuan Electronics Thecnology Co Ltd filed Critical Guangzhou Shiyuan Electronics Thecnology Co Ltd
Publication of WO2018090719A1 publication Critical patent/WO2018090719A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/451—Execution arrangements for user interfaces

Definitions

  • Embodiments of the present invention relate to an application technology of an electronic device, and in particular, to a method, an apparatus, and a terminal for automatically switching a default Launcher.
  • Android is an open source operating system based on Linux. It is mainly used in smart terminals such as mobile phones, tablets, TVs or watches. In Android, it mainly includes operating system, middleware, user interface and application.
  • the Launcher application is the first application launched after the Android system is loaded. It is responsible for processing and responding to all operations except the application itself, including providing the operation interface (ie desktop) and response. Launch applications and set wallpapers, etc. by clicking on the app icon on the desktop. After the system runs the Android installation package (AndroidPackage, APK) of the Launcher application, the system is booted. In practical applications, the developer or user will customize the Launcher according to their own needs, and set the customized Launcher application as the default Launcher to automatically launch the customized Launcher after booting.
  • AndroidPackage Android Installation package
  • the user will repeatedly see the Launcher application crash prompt, such as the prompt "Process com.android.launcher unexpected stop” prompt window, and the user can not continue to use the smart terminal, lowering user experience.
  • the Launcher application crash prompt such as the prompt "Process com.android.launcher unexpected stop” prompt window
  • the invention provides a method, a device and a terminal for automatically switching a default Launcher, so as to solve the problem that the user cannot continue to use the smart terminal after the default Launcher crashes continuously, thereby improving the user experience.
  • an embodiment of the present invention provides a method for automatically switching a default Launcher, where the method includes:
  • At least two desktop launcher Launchers are built in the smart terminal, and one Launcher is set as the default Launcher for booting the smart terminal;
  • the Launcher corresponding to the default Launcher is switched.
  • an embodiment of the present invention further provides an apparatus for automatically switching a default Launcher, where the apparatus includes:
  • the launcher has a built-in module for embedding at least two desktop launcher Launchers in the smart terminal, wherein one Launcher is set as the default Launcher for booting the smart terminal;
  • a number determining module configured to determine an abnormal number of times during the running of the default Launcher
  • the launcher switching module is configured to switch the Launcher corresponding to the default Launcher if the abnormal number exceeds a preset threshold.
  • an embodiment of the present invention further provides a terminal, including the apparatus for automatically switching a default Launcher shown in the second aspect.
  • the invention integrates at least two desktop launcher Launchers in the smart terminal, wherein one Launcher is set as the default Launcher for the smart terminal to start up; the abnormal number of times during the default Launcher operation is determined; if the abnormal number exceeds the preset threshold, the default is switched.
  • the Launcher corresponds to the Launcher.
  • the default Launcher sends When the user continues to crash, the default Launcher corresponding to the Launcher is automatically switched to ensure that the smart terminal can continue to be used after the default Launcher crashes, improving the user experience.
  • FIG. 1 is a flowchart of a method for automatically switching a default Launcher according to Embodiment 1 of the present invention
  • FIG. 2 is a flowchart of a method for automatically switching a default Launcher according to Embodiment 2 of the present invention
  • FIG. 3 is a flowchart of a method for automatically switching a default Launcher according to Embodiment 3 of the present invention
  • FIG. 4 is a schematic structural diagram of an apparatus for automatically switching a default Launcher according to Embodiment 4 of the present invention.
  • FIG. 1 is a flowchart of a method for automatically switching a default Launcher according to Embodiment 1 of the present invention.
  • the present embodiment is applicable to solving a persistent crash of a default Launcher in a smart terminal, and the method may be performed by automatically switching a device of a default Launcher.
  • the device can be implemented in software and/or hardware, and can be integrated into a smart terminal such as a mobile phone or a tablet computer. Referring to FIG. 1, the method provided in this embodiment specifically includes the following steps:
  • Step 101 Built in the smart terminal at least two desktop launcher Launchers, one of which The Launcher is set to the default Launcher for the smart terminal to boot.
  • the developer or operator will develop a custom Launcher, and install the customized Launcher and the system's own Launcher in the smart terminal before the smart terminal leaves the factory.
  • the user can also install the Launcher in the smart terminal according to his own needs.
  • the default Launcher that is started by the smart terminal is set to start the default Launcher after the system is powered on, so that the user operates the smart terminal in the default Launcher.
  • the custom Launcher is set as the default Launcher for the smart terminal to boot, so that after the system is booted, the system runs the customized Launcher to display the customized Launcher for the user.
  • the user can also set the default Launcher of the smart terminal to start up after the system is powered on. If the user enters the setting interface, a list of built-in Launchers pops up, and the Launcher selected by the user in the list is set as the smart terminal. Start the default Launcher.
  • Step 102 Determine an abnormal number of times during the default Launcher operation.
  • the smart terminal interface When an exception occurs during the running of the default Launcher, the smart terminal interface will pop up a prompt window for running the crash and restart the default Launcher. However, when the default Launcher runs continuously, the default Launcher is restarted and the persistent crash cannot be resolved. The user will repeatedly see the pop-up prompt window for running crash. Since the Launcher is the first program to run after the system is powered on, it is the entry point of other applications. Therefore, after the default Launcher continues to crash, the user will not be able to continue to operate the smart terminal.
  • the invention detects whether the default Launcher has a continuous collapse by counting the number of abnormalities in the default Launcher running after the system is powered on.
  • Step 103 If the number of abnormal times exceeds a preset threshold, switch the Launcher corresponding to the default Launcher.
  • the user can correspond to the default Launcher after the switchover.
  • the Launcher operates on other applications in the smart terminal to ensure that the smart terminal can continue to use after the default Launcher crashes.
  • the number of abnormalities is cleared to prevent the default Launcher from being accumulated after the system is turned on, resulting in false detection of the default Launcher. collapse.
  • At least two desktop launcher Launchers are built in the smart terminal, and one Launcher is set as the default Launcher for starting the smart terminal; determining the number of abnormal times during the default Launcher operation; if the abnormal number exceeds the preset Threshold, then switch the Launcher corresponding to the default Launcher.
  • the Launcher corresponding to the default Launcher is automatically switched to ensure that the smart terminal can continue to be used after the default Launcher crashes, thereby improving the user experience.
  • FIG. 2 is a flowchart of a method for automatically switching a default launcher according to Embodiment 2 of the present invention. This embodiment is further optimized for the foregoing embodiment. Referring to FIG. 2, the method provided by this implementation specifically includes:
  • Step 201 Built in the smart terminal at least two desktop launcher Launchers, wherein one Launcher is set as the default Launcher for starting the smart terminal;
  • Step 202 Obtain log information of a first preset length in the log file, and obtain a sample sample of the log information.
  • the invention automatically obtains the log information of the first preset length in the log file, and obtains a sample sample of the log information.
  • the log information of the first preset length in the log file is sequentially obtained according to the preset time interval, and the sample log sample is obtained.
  • the first preset length is 50 lines
  • the preset time interval is 1000 milliseconds.
  • After the system is started first obtain the log information of 1-50 lines in the log file, obtain the sample sample of the log information, and record the number of rows in the log file of the last line of the log information in the sample of the log information, that is, 50.
  • the preset time interval is 1000 milliseconds
  • the log information of 51-100 lines in the log file is obtained from the next line of the record, and the log information sample is obtained again.
  • Step 203 Determine whether the abnormal information of the current default Launcher is included in the sample sample of the log information. If yes, go to Step 204. Otherwise, go to Step 202.
  • the log information in the sample sample of the log information includes the abnormal information of the current default Launcher, thereby determining whether the default Launcher is abnormal. If the default information of the default Launcher is included in the sample of the log information, the default Launcher operation is abnormal. Otherwise, the log information of the first preset length in the log file is obtained periodically according to the preset time interval, and the sampled sample of the log information is obtained. The default number of exceptions during the Launcher run, continuously detecting whether the default Launcher has a continuous crash.
  • Step 204 Accumulate the number of abnormalities in the default Launcher operation according to the default information of the default Launcher.
  • the default is determined.
  • the launcher runs abnormally, and accumulates the default number of exceptions of the default Launcher according to the obtained exception information of the default Launcher, and counts the number of abnormalities during the default Launcher operation.
  • step 205 Determine whether the abnormal number exceeds a preset threshold. If yes, go to step 206. Otherwise, go to step 202.
  • the number of abnormal times exceeds the preset threshold, it is determined that the default Launcher is in a persistent crash state, and the Launcher corresponding to the default Launcher is switched; if the abnormal number of times does not exceed the preset threshold, the first preset length in the log file is obtained periodically according to the preset time interval. Log information, get the log information sample, and continuously check whether the default Launcher has a continuous crash.
  • Step 206 Switch the Launcher corresponding to the default Launcher.
  • the technical solution of the embodiment obtains the log information of the first preset length in the log file, and obtains the sample information of the log information, and determines whether the abnormal information of the default Launcher is included in the sample sample of the log information, and if the abnormal information of the default Launcher is included, according to the default
  • the launcher's exception information accumulates the number of exceptions during the default Launcher run.
  • the real-time statistics of the number of abnormalities in the default Launcher running according to the log information in the log file continuously detect whether the default Launcher is in a continuous crash state.
  • FIG. 3 is a flowchart of a method for automatically switching a default launcher according to Embodiment 3 of the present invention. This embodiment is a further optimization of the foregoing embodiment. Referring to FIG. 3, the method provided by this implementation specifically includes:
  • Step 301 Built in the smart terminal at least two desktop launcher Launchers, wherein one Launcher is set as the default Launcher for the smart terminal to boot.
  • Step 302 Obtain log information of a first preset length in the log file, and obtain log information sampling. specimen.
  • Step 303 Determine whether the Exception field is included in the sample record of the log information. If yes, go to step 304. Otherwise, go to step 302.
  • the printed exception information will include the Exception field. Therefore, it is possible to determine whether the log information in the sample of the log information includes the abnormal information by detecting whether the Exception field is included in the sample of the log information.
  • the comparison interface public Boolean contains (String input) of the String class in the Android Software Development Kit (Android SDK) can be called, and the parameter Exception is input, if the return value is true. , the log information in the sample log sample is determined to include abnormal information.
  • Step 304 Determine whether the log information of the second preset length of the Exception field in the log information sampling sample includes the current default device name of the Launcher. If yes, go to step 305. Otherwise, go to step 302.
  • the log information in the sample file of the detected log information includes an Exception field, and after determining that the log information in the sample file of the log information includes the abnormal information, the log information of the second preset length including the Exception field in the sample sample may be detected by detecting the log information.
  • the current default Launcher package name is included to determine whether the exception information included in the log information sample is the default Launcher exception information. If two Exception fields are included in the sampled log file, the log information of the two Exception fields in the log sample and the upper 10 rows and the lower 10 rows of the row are obtained, and the obtained Exception field is detected. Whether the log information of the last 10 rows and the bottom 10 rows of the row and the row includes the package name of the current default Launcher.
  • the Exception is the exception thrown by the default Launcher. If not included The current default Launcher package name indicates that the Exception is not the exception thrown by the default Launcher. Then, the log information of the first preset length in the log file is continuously obtained, and the log information sample is obtained, and the default Launcher is continuously detected to continuously crash.
  • Step 305 Cache the log information of the third preset length of the Exception field of the package name of the default Launcher in the log information sample.
  • the third pre-prefix of the Exception field Set the length of the log information cache to save the default information of the default Launcher. If you confirm that the Exception line and the log information of the last 10 lines and the bottom 10 lines of the line include the current default Launcher package name, the log information of the line of the Exception and the last 20 lines and the bottom 20 lines of the line are cached. .
  • Step 306 Accumulate the number of exceptions in the default Launcher running process by the default Launcher package name.
  • the number of the current default Launcher package names included in the log sample sample is counted. If the log information of the second preset length including the Exception field in the log information sampling sample includes the package name of the current default Launcher, the number of the default Launcher package name in the sample of the log information is 2, and The number of exceptions in the default Launcher running process increases the number of default Launcher package names, and counts the number of exceptions during the default Launcher run.
  • Step 307 Determine whether the abnormal number exceeds a preset threshold. If yes, go to step 308. Otherwise, go to step 302.
  • Step 308 Obtain a Launcher list including the package name information of the built-in Launcher
  • the information of all the Launchers in the smart terminal is obtained by the PackageMessager class, and is saved in a list, thereby obtaining a Launcher list of the built-in Launcher package name information.
  • Intent mainIntent new Intent(Intent.ACTION_MAIN,null);
  • Step 309 Remove the Launcher in the Launcher list that is the same as the current default Launcher package name, and obtain the first Launcher list.
  • the Launcher corresponding to the current default Launcher is removed from the Launcher list to prevent the Launcher corresponding to the current default Launcher from being switched to the Launcher corresponding to the default Launcher.
  • Step 310 Confirm any Launcher in the first Launcher list as the target Launcher, and switch the Launcher corresponding to the default Launcher to the target Launcher.
  • any Launcher is automatically selected from the first Launcher list as the target Launcher, and the first Launcher in the selectable list is the target Launcher.
  • the switch corresponding to the default Launcher is switched to the target Launcher, and the target Launcher is started.
  • the user operates the other applications in the target Launcher to ensure that the smart terminal can continue to be used after the default Launcher crashes.
  • Step 311 Obtain log information that is not obtained in the log file.
  • Step 312 The log information of the third preset length of the Exception field of the package name of the default Launcher before the switch is obtained and cached.
  • detecting whether the Exception field is included and detecting whether the second predetermined length of the log information including the Exception field includes the package name of the Launcher corresponding to the default Launcher before switching.
  • the third preset length of the log information of the Exception field is cached, so as to save the abnormality information of the Launcher corresponding to the default Launcher before the switch.
  • Step 313 Output all cached log information to the target directory.
  • the cached log information is saved in the same file according to the chronological order of the cache, and then the file is output to the specified target directory, so that the development and maintenance personnel can view and analyze the Launcher in the target directory.
  • the abnormal information is convenient for development and maintenance personnel to carry out maintenance.
  • the technical solution of the embodiment determines whether the log information of the second preset length including the Exception field in the sample file of the log information includes the package name of the current default Launcher. If the package name of the default Launcher is included, the default Launcher is running. The number of exceptions accumulates the number of default Launcher package names. Therefore, it is convenient and quick to count the number of abnormalities in the default Launcher running process, and detect whether the default Launcher has a continuous crash.
  • the Launcher list By obtaining the Launcher list including the built-in Launcher package name information, the Launcher list has the same Launcher name as the current default Launcher package, and the first Launcher list is obtained, and any Launcher in the first Launcher list is confirmed as the target Launcher, and Switch the Launcher corresponding to the default Launcher to the target Launcher. Thereby obtaining information of all Launchers built in the smart terminal, and will continue to collapse The collapsed Launcher is removed, and any Launcher other than the continuously crashing Launcher is automatically confirmed as the target Launcher, and the Launcher corresponding to the Launcher is switched to the target Launcher, and the target Launcher is started, so that the user is in the target Launcher in the smart terminal. Other applications operate to ensure that the smart terminal can continue to use after the default Launcher crashes. By caching the exception information of the continuously crashing Launcher and outputting it to the target directory, it is convenient for the development and maintenance personnel to view and analyze the abnormal information of the Launcher that has been continuously crashing in the target directory, which is convenient for the development
  • FIG. 4 is a schematic structural diagram of an apparatus for automatically switching a default Launcher according to Embodiment 4 of the present invention.
  • the apparatus is used to implement the method for automatically switching a default Launcher provided by the foregoing embodiment, where the apparatus includes:
  • a launcher built-in module 401 configured to build at least two desktop launcher Launchers in the smart terminal, wherein one Launcher is set as the default Launcher for starting the smart terminal;
  • the number determining module 402 is configured to determine an abnormal number of times during the default Launcher operation
  • the launcher switching module 403 is configured to switch the Launcher corresponding to the default Launcher if the abnormal number exceeds a preset threshold.
  • the number determining module includes:
  • the sample sampling unit is configured to obtain log information of a first preset length in the log file, and obtain a sample sample of the log information;
  • the abnormality information determining unit is configured to determine whether the abnormal information of the current default launcher is included in the sample of the log information sample;
  • An abnormal number accumulation unit configured to include an exception information of the default Launcher, according to the The default information of the Launcher is added to the number of exceptions during the default Launcher run.
  • the abnormality information determining unit is specifically configured to:
  • abnormal number accumulation unit is specifically used for:
  • the number of exceptions in the default Launcher running process is added to the number of the default Launcher's package name.
  • the Launcher switching module is specifically configured to:
  • the exception number accumulating unit is further configured to: if the current default browser package name is included, sampling the log information includes an Exception field of the default Launcher package name The third preset length of the log information cache.
  • the foregoing solution further includes an information cache module, specifically configured to:
  • sample sampling unit is specifically used for:
  • the log information of the first preset length in the log file is obtained in sequence, and the log information sample is obtained.
  • the Launcher corresponding to the default Launcher is initially set as a custom Launcher.
  • the fifth embodiment of the present invention provides a terminal, which integrates the device for automatically switching the default Launcher shown in Embodiment 4 of the present invention, and can automatically switch the default Launcher by performing a method of automatically switching the default Launcher.
  • the terminal in this embodiment may specifically be an intelligent terminal such as a mobile phone, a tablet computer, or a television.
  • the smart terminal can continue to use and improve the user experience.
  • the above device may perform the method provided by any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of performing the above method.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Telephone Function (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明公开了一种自动切换默认Launcher的方法、装置及终端。该方法包括：在智能终端中内置至少两个桌面启动器Launcher，其中一个Launcher设置为所述智能终端开机启动的默认Launcher；确定所述默认Launcher运行过程中的异常次数；若所述异常次数超过预设阈值，则切换所述默认Launcher对应的Launcher。本发明的技术方案可在默认Launcher发生持续崩溃时，自动切换默认Launcher对应的Launcher，保证默认Launcher崩溃之后智能终端能够继续使用，提高用户体验。

Description

一种自动切换默认Launcher的方法、装置及终端 技术领域
本发明实施例涉及电子设备应用技术，尤其涉及一种自动切换默认Launcher的方法、装置及终端。
背景技术
安卓是一种基于Linux的开放源代码的操作系统，主要用于手机、平板电脑、电视或手表等智能终端。在安卓系统中，主要包括操作系统、中间件、用户界面和应用程序。
其中，Launcher(桌面启动器)应用程序，是安卓系统加载完毕后第一个启动的应用程序，其负责处理和响应除应用本身操作外的所有操作，例如包括提供操作界面(即桌面)、响应于点击桌面上的应用程序图标而启动应用程序和设置壁纸等等。在系统运行Launcher应用程序的安卓安装包(AndroidPackage，APK)之后，完成系统开机。在实际应用中，开发者或用户会根据自身需求定制Launcher，并将定制的Launcher应用程序设置为默认Launcher，从而在开机后自动启动定制的Launcher。
然而，当定制Launcher应用程序出现持续崩溃后，用户将反复看到Launcher应用崩溃的提示，如持续出现“进程com.android.launcher意外停止”的提示窗口，且用户无法继续使用该智能终端，降低用户体验。
发明内容
本发明提供一种自动切换默认Launcher的方法、装置及终端，以解决在默认Launcher出现持续崩溃后，用户无法继续使用该智能终端的问题，提高用户体验。
第一方面，本发明实施例提供了一种自动切换默认Launcher的方法，该方法包括：
在智能终端中内置至少两个桌面启动器Launcher，其中一个Launcher设置为所述智能终端开机启动的默认Launcher；
确定所述默认Launcher运行过程中的异常次数；
若所述异常次数超过预设阈值，则切换所述默认Launcher对应的Launcher。
第二方面，本发明实施例还提供了一种自动切换默认Launcher的装置，该装置包括：
Launcher内置模块，用于在智能终端中内置至少两个桌面启动器Launcher，其中一个Launcher设置为所述智能终端开机启动的默认Launcher；
次数确定模块，用于确定所述默认Launcher运行过程中的异常次数；
Launcher切换模块，用于若所述异常次数超过预设阈值，则切换所述默认Launcher对应的Launcher。
第三方面，本发明实施例还提供了一种终端，包括第二方面所示的自动切换默认Launcher的装置。
本发明通过在智能终端中内置至少两个桌面启动器Launcher，其中一个Launcher设置为智能终端开机启动的默认Launcher；确定默认Launcher运行过程中的异常次数；若异常次数超过预设阈值，则切换默认Launcher对应的Launcher。实现在智能终端中存在多个Launcher的情况下，当默认Launcher发 生持续崩溃时，自动切换默认Launcher对应的Launcher，保证默认Launcher崩溃之后智能终端能够继续使用，提高用户体验。
附图说明
图1为本发明实施例一中的一种自动切换默认Launcher的方法的流程图；
图2是本发明实施例二中的一种自动切换默认Launcher的方法的流程图；
图3是本发明实施例三中的一种自动切换默认Launcher的方法的流程图；
图4是本发明实施例四中的一种自动切换默认Launcher的装置的结构示意图。
具体实施方式
下面结合附图和实施例对本发明作进一步的详细说明。可以理解的是，此处所描述的具体实施例仅仅用于解释本发明，而非对本发明的限定。另外还需要说明的是，为了便于描述，附图中仅示出了与本发明相关的部分而非全部结构。
实施例一
图1为本发明实施例一提供的一种自动切换默认Launcher的方法的流程图，本实施例可适用于解决智能终端中默认Launcher发生持续崩溃情况，该方法可以由自动切换默认Launcher的装置来执行，该装置可以采用软件和/或硬件的方式实现，并一般可集成在手机或平板电脑等智能终端中。参见图1，本实施例提供的方法具体包括如下步骤：
步骤101、在智能终端中内置至少两个桌面启动器Launcher，其中一个 Launcher设置为智能终端开机启动的默认Launcher。
其中，在智能终端中内置至少两个桌面启动器Launcher的方式有很多，本发明对此不作限定。如为了满足自身的需求，开发者或运营商会研发定制Launcher，并在智能终端出厂前将定制Launcher以及系统自带Launcher安装于智能终端内。又如，用户还可根据自身需求，自行在智能终端中安装Launcher。
在智能终端出厂前，会设置智能终端开机启动的默认Launcher以在系统开机后启动默认Launcher，使得用户在默认Launcher中对智能终端进行操作。优选将定制Launcher设置为智能终端开机启动的默认Launcher，从而在系统开机启动后，系统自行运行定制Launcher，为用户展示定制Launcher。用户还可在系统开机后，在设置界面自行设置智能终端开机启动的默认Launcher，如用户进入设置界面后，弹出列有内置的Launcher的列表，将用户在列表中选择的Launcher设置为智能终端开机启动的默认Launcher。
步骤102、确定默认Launcher运行过程中的异常次数。
当默认Launcher运行过程中出现异常后，智能终端界面会弹出运行崩溃的提示窗口，并需重新启动默认Launcher。然而当默认Launcher运行过程中出现持续崩溃时，重新启动默认Launcher，无法解决持续崩溃问题，用户将反复看到弹出的运行崩溃的提示窗口。由于Launcher为系统开机后运行的第一个程序，是其它应用程序的入口，因此在默认Launcher出现持续崩溃后，用户将无法继续对该智能终端进行操作。
本发明在系统开机后，通过统计系统开机后默认Launcher运行过程中的异常次数以检测默认Launcher是否出现持续崩溃。
步骤103、若异常次数超过预设阈值，则切换默认Launcher对应的Launcher。
如果确定默认Launcher运行过程中的异常次数超过预设阈值，则确定默认Launcher出现持续崩溃，切换默认Launcher对应的Launcher，启动切换后的默认Launcher对应的Launcher，则用户可在切换后的默认Launcher对应的Launcher中对智能终端中的其它应用程序进行操作，保证默认Launcher崩溃之后智能终端能够继续使用。
示例性的，可在每隔一定时间间隔后，若异常次数未超过预设阈值则将异常次数清零，以防在系统开机后，对默认Launcher的异常次数持续累加导致误检测默认Launcher出现持续崩溃。
本实施例的技术方案，通过在智能终端中内置至少两个桌面启动器Launcher，其中一个Launcher设置为智能终端开机启动的默认Launcher；确定默认Launcher运行过程中的异常次数；若异常次数超过预设阈值，则切换默认Launcher对应的Launcher。实现在智能终端中存在多个Launcher的情况下，当默认Launcher发生持续崩溃时，自动切换默认Launcher对应的Launcher，保证默认Launcher崩溃之后智能终端能够继续使用，提高用户体验。
实施例二
图2为本发明实施例二提供的一种自动切换默认Launcher的方法的流程图，本实施例为对上述实施例的进一步优化。参见图2，本实施提供的方法具体包括：
步骤201、在智能终端中内置至少两个桌面启动器Launcher，其中一个Launcher设置为所述智能终端开机启动的默认Launcher；
步骤202、获取日志文件中第一预设长度的日志信息，得到日志信息取样标本；
在安卓系统中，每个应用程序运行异常时，都会抛出异常，并可打印异常信息到日志文件中，从而可通过查看日志文件中保存的日志信息，确定异常出现的位置和异常的问题。
本发明在系统启动后，自动获取日志文件中第一预设长度的日志信息，得到日志信息取样标本。
优选的，按照预设时间间隔，依次获取日志文件中第一预设长度的日志信息，得到日志信息取样标本。示例性的，第一预设长度为50行，预设时间间隔为1000毫秒。则在系统启动后，首先获取日志文件中1-50行的日志信息，得到日志信息取样标本，并记录此次日志信息取样标本中日志信息的最后一行在日志文件中的行数，即50，在相隔预设时间间隔1000毫秒后，从记录的下一行开始，获取日志文件中51-100行的日志信息，再次得到日志信息取样标本。
步骤203、判断日志信息取样标本中是否包括当前的默认Launcher的异常信息，若是，执行步骤204，否则，执行步骤202。
在获得日志信息取样标本后，检测日志信息取样标本中的日志信息是否包括当前的默认Launcher的异常信息，从而确定默认Launcher是否运行异常。如果日志信息取样标本中包括当前的默认Launcher的异常信息，则确定默认Launcher运行异常，否则，按照预设时间间隔定时获取日志文件中第一预设长度的日志信息，得到日志信息取样标本，统计默认Launcher运行过程中的异常次数，持续检测默认Launcher是否发生持续崩溃。
步骤204、根据默认Launcher的异常信息对默认Launcher运行过程中的异常次数累加。
如果日志信息取样标本中包括默认Launcher的异常信息，则确定默认 Launcher运行异常，根据得到的默认Launcher的异常信息对默认Launcher的异常次数累加，统计默认Launcher运行过程中的异常次数。
205、判断异常次数是否超过预设阈值，若是，执行步骤206，否则，执行步骤202。
如果异常次数超过预设阈值，则确定默认Launcher处于持续崩溃状态，切换默认Launcher对应的Launcher；如果异常次数未超过预设阈值，则按照预设时间间隔定时获取日志文件中第一预设长度的日志信息，得到日志信息取样标本，持续检测默认Launcher是否发生持续崩溃。
步骤206、切换默认Launcher对应的Launcher。
本实施例的技术方案通过获取日志文件中第一预设长度的日志信息，得到日志信息取样标本，判断日志信息取样标本中是否包括默认Launcher的异常信息，若包括默认Launcher的异常信息，根据默认Launcher的异常信息对默认Launcher运行过程中的异常次数累加。实现根据日志文件中的日志信息实时统计默认Launcher运行过程中的异常次数，从而持续检测默认Launcher是否处于持续崩溃状态。
实施例三
图3为本发明实施例三提供的一种自动切换默认Launcher的方法的流程图，本实施例为对上述实施例的进一步优化。参见图3，本实施提供的方法具体包括：
步骤301、在智能终端中内置至少两个桌面启动器Launcher，其中一个Launcher设置为所述智能终端开机启动的默认Launcher。
步骤302、获取日志文件中第一预设长度的日志信息，得到日志信息取样 标本。
步骤303、判断日志信息取样标本中是否包括Exception字段，若是，执行步骤304，否则，执行步骤302。
若应用程序运行异常，打印的异常信息均会包括Exception字段，因此，可通过检测日志信息取样标本中是否包括Exception字段，确定日志信息取样标本中的日志信息是否包括异常信息。
如由于日志信息为String类型数据，因此可调用安卓软件开发工具包(Android Software Development Kit，Android SDK)中的String类的对比接口public Boolean contains(String input)，输入参数Exception，若返回值为true，则确定日志信息取样标本中的日志信息包括异常信息。
步骤304、判断日志信息取样标本中包括Exception字段的第二预设长度的日志信息是否包括当前的默认Launcher的包名，若是，执行步骤305，否则，执行步骤302。
在检测到日志信息取样标本中的日志信息包括Exception字段，确定日志信息取样标本中的日志信息包括异常信息后，可通过检测日志信息取样标本中包括Exception字段的第二预设长度的日志信息是否包括当前的默认Launcher的包名来确定日志信息取样标本中包括的异常信息是否为默认Launcher的异常信息。如检测到日志信息取样标本中包括2个Exception字段，则分别获取日志信息取样标本中2个Exception字段所在行及所在行的上10行和下10行的日志信息，并检测获取的Exception字段所在行及所在行的上10行和下10行的日志信息是否包括当前的默认Launcher的包名(Package Name)，若包括当前默认Launcher的包名，则说明该Exception为默认Launcher抛出的异常，若不包括 当前默认Launcher的包名，则说明该Exception不是默认Launcher抛出的异常，则继续获取日志文件中第一预设长度的日志信息，得到日志信息取样标本，持续检测默认Launcher是否发生持续崩溃。
步骤305、将日志信息取样标本中包括默认Launcher的包名的Exception字段的第三预设长度的日志信息缓存。
优选的，若日志信息取样标本中包括Exception字段的第二预设长度的日志信息中包括当前默认Launcher的包名，说明该Exception为默认Launcher抛出的异常，则将该Exception字段的第三预设长度的日志信息缓存，从而保存默认Launcher的异常信息。如若确认获取的Exception所在行及所在行的上10行和下10行的日志信息包括当前默认Launcher的包名，则将该Exception所在行及所在行的上20行和下20行的日志信息缓存。
步骤306、将默认Launcher运行过程中的异常次数累加默认Launcher的包名的个数。
优选的，在确认包括当前默认Launcher的包名后，统计该日志信息取样标本中包括的当前默认Launcher的包名的个数。如若日志信息取样标本中有2个包括Exception字段的第二预设长度的日志信息中包括当前默认Launcher的包名，则该日志信息取样标本中默认Launcher的包名的个数为2，并将默认Launcher运行过程中的异常次数累加默认Launcher的包名的个数，统计默认Launcher运行过程中的异常次数。
步骤307、判断异常次数是否超过预设阈值，若是，执行步骤308，否则，执行步骤302。
步骤308、获取包括内置的Launcher的包名信息的Launcher列表；
示例性的，可通过PackageMessager类获取智能终端中的所有Launcher的信息，并保存在一个列表中，从而获取内置的Launcher的包名信息的Launcher列表。如通过下列程序实现：
PackageManager pm＝this.getPackageManager()；
Intent mainIntent＝new Intent(Intent.ACTION_MAIN，null)；
mainIntent.addCategory(Intent.CATEGORY_LAUNCHER)；
//通过查询，获得所有ResolveInfo对象.
List<ResolveInfo>resolveInfos＝pm.queryIntentActivities(mainIntent，Packag eManager.MATCH_DEFAULT_ONLY)；
步骤309、去除Launcher列表中与当前的默认Launcher包名相同的Launcher，得到第一Launcher列表。
通过去除Launcher列表中与当前的默认Launcher包名相同的Launcher，将当前默认Launcher对应的Launcher从Launcher列表中去除以防止再次将当前默认Launcher对应的Launcher切换为默认Launcher对应的Launcher。
步骤310、将第一Launcher列表中任一Launcher确认为目标Launcher，并将默认Launcher对应的Launcher切换为目标Launcher。
在得到第一Launcher列表后，从第一Launcher列表自动选取任一Launcher为目标Launcher，如可选取列表中的第一个Launcher为目标Launcher。并将默认Launcher对应的Launcher切换为目标Launcher，从而启动目标Launcher，用户在目标Launcher中，对其它应用程序进行操作，保证默认Launcher崩溃之后智能终端能够继续使用。
步骤311、获取日志文件中未被获取的日志信息。
将默认Launcher对应的Launcher切换为目标Launcher后，获取日志文件中未被获取的所有日志信息，以获取日志文件中未被获取的异常信息。
步骤312、获取未被获取的日志信息中包括切换前默认Launcher的包名的Exception字段的第三预设长度的日志信息并缓存。
示例性的，在获取的未被获取的日志信息中，检测是否包括Exception字段，并检测包括Exception字段的第二预设长度的日志信息中是否包括切换前默认Launcher对应的Launcher的包名，若包括，则缓存包括该Exception字段的第三预设长度的日志信息，从而保存未被获取的切换前默认Launcher对应的Launcher的异常信息。
步骤313、将所有缓存的日志信息输出至目标目录中。
优选的，将各缓存的日志信息按照缓存的时间先后顺序保存在同一文件中，再将该文件输出到指定的目标目录中，从而开发维护人员可在目标目录中查看并分析发生持续崩溃的Launcher的异常信息，便于开发维护人员进行维护。
本实施例的技术方案，通过判断日志信息取样标本中包括Exception字段的第二预设长度的日志信息是否包括当前的默认Launcher的包名，若包括默认Launcher的包名，将默认Launcher运行过程中的异常次数累加默认Launcher的包名的个数。从而实现方便快捷地对默认Launcher运行过程中的异常次数进行统计，检测默认Launcher是否发生持续崩溃。通过获取包括内置的Launcher的包名信息的Launcher列表，去除Launcher列表中与当前的默认Launcher包名相同的Launcher，得到第一Launcher列表，将第一Launcher列表中任一Launcher确认为目标Launcher，并将默认Launcher对应的Launcher切换为目标Launcher。从而获取智能终端中内置的所有Launcher的信息，并将发生持续崩 溃的Launcher去除，自动将除持续崩溃的Launcher之外的任一Launcher确认为目标Launcher，并将默认Launcher对应的Launcher切换为目标Launcher，进而启动目标Launcher，使得用户在目标Launcher中对智能终端中的其它应用程序进行操作，保证默认Launcher崩溃之后智能终端能够继续使用。通过缓存出现持续崩溃的Launcher的异常信息并输出至目标目录，便于开发维护人员在目标目录中查看并分析发生持续崩溃的Launcher的异常信息，为开发维护人员提供便利。
实施例四
图4为本发明实施例四提供的一种自动切换默认Launcher的装置的结构示意图，上述装置用于实现上述实施例提供的自动切换默认Launcher的方法，该装置包括：
Launcher内置模块401，用于在智能终端中内置至少两个桌面启动器Launcher，其中一个Launcher设置为所述智能终端开机启动的默认Launcher；
次数确定模块402，用于确定所述默认Launcher运行过程中的异常次数；
Launcher切换模块403，用于若所述异常次数超过预设阈值，则切换所述默认Launcher对应的Launcher。
上述方案中，可选的是，所述次数确定模块包括：
标本取样单元，用于获取日志文件中第一预设长度的日志信息，得到日志信息取样标本；
异常信息判断单元，用于判断所述日志信息取样标本中是否包括当前的所述默认Launcher的异常信息；
异常次数累加单元，用于若包括所述默认Launcher的异常信息，根据所述 默认Launcher的异常信息对所述默认Launcher运行过程中的异常次数累加。
上述方案中，可选的是，所述异常信息判断单元具体用于：
判断所述日志信息取样标本中是否包括Exception字段；
若是，判断所述日志信息取样标本中包括所述Exception字段的第二预设长度的日志信息是否包括当前的所述默认Launcher的包名；
相应的，所述异常次数累加单元具体用于：
若包括所述默认Launcher的包名，将所述默认Launcher运行过程中的异常次数累加所述默认Launcher的包名的个数。
上述方案中，可选的是，Launcher切换模块具体用于：
获取包括内置的所述Launcher的包名信息的Launcher列表；
去除所述Launcher列表中与当前的所述默认Launcher包名相同的Launcher，得到第一Launcher列表；
将所述第一Launcher列表中任一Launcher确认为目标Launcher，并将所述默认Launcher对应的Launcher切换为所述目标Launcher。
上述方案中，可选的是，所述异常次数累加单元还用于：若包括当前的所述默认Launcher的包名，将所述日志信息取样标本中包括所述默认Launcher的包名的Exception字段的第三预设长度的日志信息缓存。
上述方案中，优选的是，还包括信息缓存模块，具体用于：
获取所述日志文件中未被获取的日志信息；
获取所述未被获取的日志信息中包括切换前默认Launcher的包名的Exception字段的第三预设长度的日志信息并缓存；
将所有缓存的日志信息输出至目标目录中。
上述方案中，优选的是，标本取样单元具体用于：
按照预设时间间隔，依次获取日志文件中第一预设长度的日志信息，得到日志信息取样标本。
上述方案中，优选的是，所述默认Launcher对应的Launcher初始设置为定制Launcher。
实施例五
本发明实施例五提供了一种终端，该终端集成了本发明实施例四所示的自动切换默认Launcher的装置，可通过执行自动切换默认Launcher的方法来进行自动切换默认Launcher。
示例性的，本实施例中的终端具体可为手机、平板电脑及电视等智能终端。
在用户使用本实施例中的终端过程中，在终端中存在多个Launcher的情况下，持续检测默认Launcher是否发生持续崩溃，当默认Launcher发生持续崩溃时，自动切换默认Launcher对应的Launcher，保证默认Launcher崩溃之后智能终端能够继续使用，提高用户体验。
上述装置可执行本发明任意实施例所提供的方法，具备执行上述方法相应的功能模块和有益效果。未在本实施例中详尽描述的技术细节，可参见本发明任意实施例所提供的方法。
注意，上述仅为本发明的较佳实施例及所运用技术原理。本领域技术人员会理解，本发明不限于这里所述的特定实施例，对本领域技术人员来说能够进行各种明显的变化、重新调整和替代而不会脱离本发明的保护范围。因此，虽 然通过以上实施例对本发明进行了较为详细的说明，但是本发明不仅仅限于以上实施例，在不脱离本发明构思的情况下，还可以包括更多其他等效实施例，而本发明的范围由所附的权利要求范围决定。

Claims (10)

  1. 一种自动切换默认Launcher的方法，其特征在于，包括：
    在智能终端中内置至少两个桌面启动器Launcher，其中一个Launcher设置为所述智能终端开机启动的默认Launcher；
    确定所述默认Launcher运行过程中的异常次数；
    若所述异常次数超过预设阈值，则切换所述默认Launcher对应的Launcher。
  2. 根据权利要求1所述的方法，其特征在于，所述确定所述默认Launcher运行过程中的异常次数，包括：
    获取日志文件中第一预设长度的日志信息，得到日志信息取样标本；
    判断所述日志信息取样标本中是否包括当前的所述默认Launcher的异常信息；
    若是，根据所述默认Launcher的异常信息对所述默认Launcher运行过程中的异常次数累加。
  3. 根据权利要求2所述的方法，其特征在于，所述判断所述日志信息取样标本中是否包括当前的所述默认Launcher的异常信息，包括：
    判断所述日志信息取样标本中是否包括Exception字段；
    若是，判断所述日志信息取样标本中包括所述Exception字段的第二预设长度的日志信息是否包括当前的所述默认Launcher的包名；
    相应的，若是，根据所述默认Launcher的异常信息对所述默认Launcher运行过程中的异常次数累加，包括：
    若是，将所述默认Launcher运行过程中的异常次数累加所述默认Launcher的包名的个数。
  4. 根据权利要求3所述的方法，其特征在于，所述切换所述默认Launcher 对应的Launcher，包括：
    获取包括内置的所述Launcher的包名信息的Launcher列表；
    去除所述Launcher列表中与当前的所述默认Launcher包名相同的Launcher，得到第一Launcher列表；
    将所述第一Launcher列表中任一Launcher确认为目标Launcher，并将所述默认Launcher对应的Launcher切换为所述目标Launcher。
  5. 根据权利要求3所述的方法，其特征在于，所述将所述默认Launcher的异常次数累加所述默认Launcher的包名的个数之前，还包括：
    将所述日志信息取样标本中包括所述默认Launcher的包名的Exception字段的第三预设长度的日志信息缓存。
  6. 根据权利要求5所述的方法，其特征在于，所述若所述异常次数超过预设阈值，则将默认Launcher切换为目标Launcher之后，还包括：
    获取所述日志文件中未被获取的日志信息；
    获取所述未被获取的日志信息中包括切换前默认Launcher的包名的Exception字段的第三预设长度的日志信息并缓存；
    将所有缓存的日志信息输出至目标目录中。
  7. 根据权利要求2所述的方法，其特征在于，所述获取日志文件中第一预设长度的日志信息，得到日志信息取样标本，具体为：
    按照预设时间间隔，依次获取日志文件中第一预设长度的日志信息，得到日志信息取样标本。
  8. 根据权利要求1所述的方法，其特征在于，所述默认Launcher对应的Launcher初始设置为定制Launcher。
  9. 一种自动切换默认Launcher的装置，其特征在于，包括：
    Launcher内置模块，用于在智能终端中内置至少两个桌面启动器Launcher，其中一个Launcher设置为所述智能终端开机启动的默认Launcher；
    次数确定模块，用于确定所述默认Launcher运行过程中的异常次数；
    Launcher切换模块，用于若所述异常次数超过预设阈值，则切换所述默认Launcher对应的Launcher。
  10. 一种终端，其特征在于，包括权利要求9所述的自动切换默认Launcher的装置。
PCT/CN2017/103294 2016-11-15 2017-09-25 一种自动切换默认Launcher的方法、装置及终端 Ceased WO2018090719A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201611029806.9A CN106775633A (zh) 2016-11-15 2016-11-15 一种自动切换默认Launcher的方法、装置及终端
CN201611029806.9 2016-11-15

Publications (1)

Publication Number Publication Date
WO2018090719A1 true WO2018090719A1 (zh) 2018-05-24

Family

ID=58970808

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/103294 Ceased WO2018090719A1 (zh) 2016-11-15 2017-09-25 一种自动切换默认Launcher的方法、装置及终端

Country Status (2)

Country Link
CN (1) CN106775633A (zh)
WO (1) WO2018090719A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116185440A (zh) * 2021-11-29 2023-05-30 广州迈聆信息科技有限公司 基于安卓系统的Launcher应用更新的方法、装置和显示设备

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106775633A (zh) * 2016-11-15 2017-05-31 广州视源电子科技股份有限公司 一种自动切换默认Launcher的方法、装置及终端
CN113849337B (zh) * 2021-11-30 2022-03-01 飞狐信息技术（天津）有限公司 一种系统异常的处理方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103677587A (zh) * 2013-12-11 2014-03-26 Tcl集团股份有限公司 一种Android系统中快速切换主界面的方法及系统
CN103713813A (zh) * 2014-01-03 2014-04-09 三星电子（中国）研发中心 对智能手持设备的功能进行控制的方法
CN104794014A (zh) * 2015-04-08 2015-07-22 华为技术有限公司 系统运行的方法及智能终端
CN105677421A (zh) * 2016-01-06 2016-06-15 惠州Tcl移动通信有限公司 一种移动终端的桌面启动器的定制方法及系统
CN106775633A (zh) * 2016-11-15 2017-05-31 广州视源电子科技股份有限公司 一种自动切换默认Launcher的方法、装置及终端

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103400081B (zh) * 2013-07-30 2016-09-21 东莞宇龙通信科技有限公司 终端和用户界面的显示控制方法
CN105487980B (zh) * 2015-12-04 2019-06-07 Tcl集团股份有限公司 修复应用程序运行异常的方法及装置
CN105607972B (zh) * 2015-12-28 2019-06-18 Tcl集团股份有限公司 一种异常修复的方法及装置
CN106095621B (zh) * 2016-06-12 2019-06-11 Tcl集团股份有限公司 一种安卓系统中Launcher运行异常的恢复方法及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103677587A (zh) * 2013-12-11 2014-03-26 Tcl集团股份有限公司 一种Android系统中快速切换主界面的方法及系统
CN103713813A (zh) * 2014-01-03 2014-04-09 三星电子（中国）研发中心 对智能手持设备的功能进行控制的方法
CN104794014A (zh) * 2015-04-08 2015-07-22 华为技术有限公司 系统运行的方法及智能终端
CN105677421A (zh) * 2016-01-06 2016-06-15 惠州Tcl移动通信有限公司 一种移动终端的桌面启动器的定制方法及系统
CN106775633A (zh) * 2016-11-15 2017-05-31 广州视源电子科技股份有限公司 一种自动切换默认Launcher的方法、装置及终端

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116185440A (zh) * 2021-11-29 2023-05-30 广州迈聆信息科技有限公司 基于安卓系统的Launcher应用更新的方法、装置和显示设备

Also Published As

Publication number Publication date
CN106775633A (zh) 2017-05-31

Similar Documents

Publication Publication Date Title
CN104598380B (zh) 一种基于控件的自动化测试方法及系统
US9471474B2 (en) Cloud deployment infrastructure validation engine
CN108804299B (zh) 应用程序异常处理方法及装置
CN103617057B (zh) 安装应用程序的方法及装置
US20160224207A1 (en) Method and system for freezing and unfreezing applications
CN106095621B (zh) 一种安卓系统中Launcher运行异常的恢复方法及系统
CN110018918B (zh) 终端异常的修复方法、装置、移动终端及存储介质
US10366226B2 (en) Malicious code analysis device and method based on external device connected via USB cable
CN105045708A (zh) 软件运行错误处理方法及系统
CN110232022A (zh) 网络环境测试方法、装置及终端设备
CN105867962A (zh) 系统升级的方法和装置
WO2018090719A1 (zh) 一种自动切换默认Launcher的方法、装置及终端
US8468388B2 (en) Restoring programs after operating system failure
CN1845077A (zh) 一种对计算机进行远程检测及控制的方法
CN112506693A (zh) 一种记录异常信息的方法、装置、存储介质和电子设备
CN103019706A (zh) 针对启动项目的处理方法和装置
CN116938711A (zh) 固件升级方法、装置、电子设备及存储介质
US20180144134A1 (en) Detection system and detection method
CN112182581B (zh) 应用测试方法、装置、应用测试设备和存储介质
CN105242981A (zh) 一种Kdump的配置方法及计算机设备
CN104298618B (zh) 一种智能终端的命令处理方法及装置
US9817730B1 (en) Storing request properties to block future requests
CN104077210A (zh) 一种客户端崩溃的定位方法及系统
CN111124627B (zh) 应用程序的调起者确定方法、装置、终端及存储介质
CN112988554B (zh) Sdk检测方法、装置、sdk、程序、设备和存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17872247

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17872247

Country of ref document: EP

Kind code of ref document: A1