CN106547667B - Fault prompting method and system for mobile terminal - Google Patents
Fault prompting method and system for mobile terminal Download PDFInfo
- Publication number
- CN106547667B CN106547667B CN201510589957.9A CN201510589957A CN106547667B CN 106547667 B CN106547667 B CN 106547667B CN 201510589957 A CN201510589957 A CN 201510589957A CN 106547667 B CN106547667 B CN 106547667B
- Authority
- CN
- China
- Prior art keywords
- fault
- bus
- bus equipment
- equipment
- fault event
- 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.)
- Active
Links
Images
Landscapes
- Debugging And Monitoring (AREA)
- Telephone Function (AREA)
Abstract
The fault prompting method of the mobile terminal can be used in mobile phone, computer and other equipment, firstly, judging whether the communication with the bus equipment is wrong, and receiving the fault event reported by the bus equipment driver when the communication with the bus equipment is wrong; judging the bus equipment corresponding to the fault event; and generating fault prompt information of the bus equipment. According to the scheme, when communication with the bus equipment is wrong, fault information reported by the bus equipment driver is received, and the fault information of the bus equipment is displayed, so that a user can conveniently know whether the fault caused by the error of the bus equipment or the fault caused by system problems exists, analysis is not needed in a Log mode and the like, the bus equipment with the fault can be well positioned, and valuable reference information is provided for developers or users.
Description
Technical Field
The invention relates to the field of intelligent mobile terminals, in particular to a fault prompting method and system of a mobile terminal.
Background
Along with the development of intelligent equipment, intelligent equipment is increasingly popularized, especially intelligent equipment that conveniently carries such as smart mobile phone, panel computer. At present, functions of smart phones are more and more, and bus devices (also called peripheral devices of the smart phones) of the smart phones are more and more abundant, where the bus devices generally refer to devices connected with a mobile phone controller through an I2C bus or an SPI bus, and therefore the bus devices are named according to types of used buses, such as I2C bus devices or SPI bus devices. I2C is an abbreviation for Inter-Integrated Circuit, a two-wire serial bus developed by PHILIPS corporation for connecting microcontrollers and their peripherals. At present, the touch screen of the mobile phone and various sensors are basically connected with a main controller through an I2C bus. The SPI bus (Serial Peripheral Interface) is a high-speed, full-duplex, synchronous communication bus, and is also a common bus for connecting the main controller of the mobile phone to the bus device. The bus device of the mobile phone, for example, the touch screen, is a device that must be provided to implement an input function, and the bus device of the mobile phone further includes various sensors such as a gravity sensor, a proximity sensor, a gyroscope, and the like to enhance user experience and implement additional functions.
As the types of the bus devices of the mobile phone are more and more, the functions of the operating system of the mobile phone are more and more, and the compatibility and the processing speed are challenged, the potential risk of the bus device failure is increased. However, when a mobile phone bus device fails, the most conventional method is to analyze the cause of the failure through a system Log, i.e., a Log. A Log is usually a record of some kind of processing that has been done by the system or some software so that for future reference, by analyzing the Log, exceptions that occur during program installation or running can be found. For example, when a phenomenon that a mobile phone screen does not react (also called freeze) occurs, it can be determined whether the mobile phone freeze is caused by a touch screen or a system crash by analyzing the Log. However, because the information in the program running process is more, the analysis of the Log itself is time-consuming and labor-consuming, and particularly when the mobile phone screen freezing phenomenon occurs, once the debugging function of the USB interface is not opened, almost no way is available to obtain the Log information.
Disclosure of Invention
Therefore, the technical problem to be solved by the present invention is to overcome the defect that it is impossible to determine whether a system is in a problem or a bus device is in a failure when a bus device of a mobile terminal in the prior art is in a problem, thereby providing a method and a system for prompting a failure of a mobile terminal.
Therefore, the invention provides a fault prompting method of a mobile terminal, wherein bus equipment refers to a component connected with a controller of the mobile terminal through a bus, a fault event reporting interface is arranged in an operating system kernel of the mobile terminal, and the method comprises the following steps:
judging whether communication with the bus equipment is in error;
when an error occurs, receiving a fault event reported by the bus equipment;
acquiring bus equipment corresponding to the fault event according to the reported fault event;
and generating fault prompt information of the bus equipment.
Preferably, after the generating the bus device fault notification information, the method further includes:
judging whether the bus equipment is recovered to be normal after being in error;
and if so, generating prompt information for the bus equipment to recover to normal.
Preferably, the bus device comprises a touch screen or a gravity sensor or a proximity sensor or other bus device.
Preferably, in the step of determining whether the communication with the bus device is faulty, the first bus device reads and writes the return value of the function to determine whether the communication with the bus device is faulty.
Preferably, in the step of determining whether the bus device is recovered to normal after an error occurs, the second bus device reads and writes the return value of the function to determine whether the communication with the bus device is recovered to normal after an error occurs.
In addition, the present invention also provides a fault prompting system of a mobile terminal, wherein a fault event reporting interface is arranged in an operating system kernel of the mobile terminal, and the fault prompting system comprises:
a communication judging unit for judging whether communication with the bus device is erroneous;
the fault reporting unit is used for receiving a fault event reported by the bus equipment driver when an error occurs;
a bus device judging unit, configured to judge a bus device corresponding to the fault event;
and the fault prompting unit is used for generating fault prompting information of the bus equipment.
Preferably, the method further comprises the following steps:
the recovery judging unit is used for judging whether the bus equipment is recovered to be normal after being in error;
and the recovery prompting unit is used for recovering to normal after the bus equipment goes wrong to generate the prompting information that the bus equipment recovers to normal.
Preferably, the bus device comprises a touch screen or a gravity sensor or a proximity sensor or other bus device.
In addition, the invention also provides a fault prompting method of the mobile terminal, which is applied to an input subsystem of an android operating system, wherein the input subsystem comprises a local framework layer and a Java layer, and the method comprises the following steps:
receiving a fault event reported by a driver of bus equipment through a local framework layer, wherein the fault event comprises fault occurrence or fault removal;
reporting the fault event to a Java framework layer by the local framework layer;
and the input system of the Java framework layer receives the fault event and sends the fault event to a notification manager of the Java framework layer, and the notification manager judges the bus equipment to which the fault belongs according to the received fault event and displays the prompt message of fault occurrence or the prompt message of fault removal in a bullet frame mode.
The technical scheme of the invention has the following advantages:
1. the fault prompting method and the fault prompting system of the mobile terminal can be used in equipment such as a mobile phone, a computer and the like, firstly, whether communication with bus equipment has an error is judged, and when the error occurs, a fault event reported by a bus equipment driver is received; and then judging the bus equipment corresponding to the fault event, and generating fault prompt information of the bus equipment. According to the scheme, when communication with the bus equipment is wrong, fault information reported by the bus equipment driver is received, and the fault information of the bus equipment is displayed, so that a user can conveniently know whether the fault caused by the error of the bus equipment or the fault caused by system problems exists, analysis is not needed in a Log mode and the like, the bus equipment with the fault can be well positioned, and valuable reference information is provided for developers or users.
2. The fault prompting method and the fault prompting system of the mobile terminal further judge whether the bus equipment is recovered to be normal after the fault occurs, and if so, generate the prompting information that the bus equipment is recovered to be normal. Because the fault prompt is carried out when the fault occurs, sometimes the fault of the bus equipment can be automatically repaired, at the moment, if the fault removing prompt is not carried out, a user cannot know that the normal actual state is recovered at the moment, and therefore the prompt is carried out under the condition that the bus equipment is recovered to be normal after the fault occurs, the user can know the current actual state, and the use of the user is facilitated.
3. The fault prompting method of the mobile terminal can be used in any operating system such as an Android system and an iOS system, is mainly used in an input subsystem when being used in the Android system, realizes the process of transmitting and displaying a fault event from a bottom layer to an upper layer through a local framework layer and a Java framework layer, and displays the fault of the bus equipment in a pop-up frame mode through a notification manager of the Java framework layer, so that a user can visually determine whether the bus equipment has the fault.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings can be obtained by those skilled in the art without creative efforts.
Fig. 1 is a schematic structural diagram of a mobile phone using the fault notification method of a mobile terminal according to an embodiment of the present invention;
fig. 2 is a flowchart of a fault notification method of a mobile terminal in an embodiment of the present invention;
FIG. 3 is a flowchart of a fault notification method in an input subsystem of the android system in an embodiment of the present invention;
fig. 4 is a block diagram of a fault notification system of a mobile terminal in an embodiment of the present invention.
Detailed Description
The technical solutions of the present invention will be described clearly and completely with reference to the accompanying drawings, and it should be understood that the described embodiments are some, but not all embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
In addition, the technical features involved in the different embodiments of the present invention described below may be combined with each other as long as they do not conflict with each other.
In this embodiment, a fault notification method for a mobile terminal is provided, where the mobile terminal may be a mobile terminal such as a mobile phone and a tablet computer, as shown in fig. 1, a bus device of the mobile terminal in this embodiment includes a touch screen 1, a gravity sensor 2, a proximity sensor 3, and the like, an operating system is run in a mobile terminal controller 4, the bus device of the mobile terminal includes types such as an I2C bus device and an SPI bus device, and the operating system and the bus device of the mobile terminal communicate with each other through an I2C bus or an SPI bus, and the fault notification method for the mobile terminal includes the following steps, and a flowchart is shown in fig. 2:
s11, judging whether the communication with the bus device is error, executing step S12 when the communication is error, and continuing to detect whether the communication with the bus device is error when no error occurs.
If the mobile phone controller judges whether the communication with the bus equipment is wrong or not, if the communication with the bus equipment is wrong, the bus equipment is judged to be in fault, and whether the communication fault of the bus equipment or the information fault of the bus equipment is judged to be in fault of the bus equipment.
Preferably, the main controller of the handset can judge whether the communication between the main controller of the handset and the bus device is in error through the return value of the read-write function of the main controller of the handset and the bus device. Taking the driving code of touch IC ft5336 of touch IC supplier tetai technology as an example, the device communicates with the host through I2C bus, and the host reads the touch coordinate data in the interrupt function static irqreturn _ t ft5x06_ ts _ interrupt (intirq, void dev _ id) by the following code:
rc＝ft5x06_i2c_read(data->client,®,1,buf,data->tch_data_len)；
whether the communication between the host and the ft5336 is successful or not can be judged by the return value of the function ft5x06_ i2c _ read (), wherein the communication is successful and more than or equal to 0 and is failed and less than 0, and if the communication is failed, the communication is considered to be in error.
And S12, receiving the fault event reported by the bus equipment.
The bus device of the mobile phone comprises hardware and a software program (i.e. driver) matched with the hardware, if the bus device fails, the driver of the bus device can obtain the failure, and the driver of the bus device can report the failure event. The mobile phone operating system can receive the fault event reported by the driver through the bus.
And S13, judging the bus equipment corresponding to the fault event.
Such as determining whether the fault event corresponds to a touch screen, a gravity sensor, a proximity sensor, or other bus device.
And S14, generating bus equipment fault prompting information.
Generating corresponding bus equipment fault prompt information according to the bus equipment with the fault judged in the previous step, and sending the prompt information to display equipment for displaying, for example, displaying on a display screen in a pop-up window mode, and if the bus equipment with the fault is the touch screen fault, displaying the touch screen fault information on the display screen; if the gravity sensor is in fault, displaying a message of the fault of the gravity sensor on a display screen; and if the fault is the proximity sensor, displaying a message of the fault of the proximity sensor on the display screen.
According to the fault prompting method of the mobile terminal in the embodiment, when communication with the bus equipment is in error, the fault information reported by the bus equipment driver can be received, and the fault information of the bus equipment is displayed, so that a user can conveniently know whether the fault is caused by the error of the bus equipment or caused by a system problem, analysis is not needed in a Log mode and the like, the bus equipment with the fault can be better positioned, and valuable reference information is provided for developers or users. The scheme can be applied to intelligent electronic equipment such as smart phones, ipads and tablet computers, and is applicable to operating systems of any mobile terminals such as an android system, iOS or Windows phone.
In a further embodiment, some handset bus device errors are temporary and can automatically recover to normal, at which point the user cannot know that the fault has been resolved and therefore needs to display this recovery message to the user. Therefore, on the basis of the above scheme, the fault prompting method of the mobile terminal further comprises the following steps:
and S15, judging whether the bus equipment is normal after error, if so, executing a step S16, otherwise, continuously detecting. If the communication between the mobile phone bus equipment and the mobile phone controller is recovered to be normal, the bus equipment is considered to be recovered to be normal after the error occurs. Consistent with the above-mentioned manner of determining whether the communication with the bus device is faulty, it can be determined whether the communication between the host and the ft5336 is successful, more than or equal to 0, and less than 0 fails, according to the return value of the function ft5x06_ i2c _ read ().
And S16, generating prompt information for the bus equipment to return to normal and sending the prompt information to the display equipment.
If the touch screen is recovered after the fault, displaying that the touch screen is recovered to be normal in a bullet frame mode according to the received event data; if the gravity sensor is recovered after the fault, displaying the removal of the gravity sensor fault in a bullet frame mode according to the received event data; if the proximity sensor is recovered after the failure, the release of the proximity sensor failure is displayed in a bullet box form according to the received event data. If the bus equipment is a fault event of other bus equipment, the judgment and the processing are continued.
The scheme can prompt the self-recovery fault of the mobile phone bus equipment to be removed, so that a developer or a user can know that the fault is removed, more valuable information is provided, and the situation that the mobile phone bus equipment can normally work and the user still thinks that the fault exists is avoided.
In addition, the present embodiment also provides a mobile terminal for performing fault notification by using the fault notification method, where the mobile terminal may be an electronic device such as a smart phone, a tablet computer, a handheld PDA (Personal Digital Assistant), and the like.
In addition, this embodiment further provides a fault prompting method for a mobile terminal in an input subsystem of an Android operating system, where the input subsystem includes a local framework layer and a Java layer, a fault event reporting function is added in a Linux kernel in the Android system in advance, an interface is set in the input subsystem, and a fault event reporting function is added. Specifically, an event type (type) EV _ ERR may be newly added in the Linux input subsystem and all code types of the EV _ ERR may be defined.
Implementing interfaces for reporting fault events, reference codes such as
The Code is used for judging which device has a fault event, and Value: 1, fault occurrence; the 0 fault is resolved.
The flow chart of the fault prompting method for the input subsystem of the android system is shown in fig. 3, and the process includes:
and S21, receiving a fault event reported by a driver of the bus equipment through the local framework layer, wherein the fault event comprises fault occurrence or fault release.
The bus equipment driver reports a fault event to a local framework layer in an Android input system, the fault event can be a fault or a fault relief, the types of the related local framework layer mainly include EventHub, InputReader and InputDispatch, and the acquisition and processing of the fault event are added in the types.
And S22, reporting the fault event to a Java framework layer by the local framework layer.
The related classes of the Java framework layer mainly comprise native InputManager, InputManagerservice and InputMonitor, and the acquisition and processing of the fault event are added in the classes.
And S23, the input system of the Java framework layer receives the fault event, and the fault event is transmitted to the notification manager of the Java framework layer by the input system of the android Java framework layer.
And S24, judging the bus equipment to which the fault belongs according to the received fault event by the notification manager of the Java framework layer, and displaying the prompt message of fault occurrence or the prompt message of fault release in a bullet frame mode.
When the bus equipment to which the fault belongs is judged, if the bus equipment is a touch screen fault event, the notification manager displays the occurrence or the release of the touch screen fault in a popup frame mode according to the received event data.
If the event is a gravity sensor fault event, the notification manager displays the occurrence or release of the gravity sensor fault in a bullet box mode according to the received event data.
If the event is a proximity sensor failure event, the notification manager displays the occurrence or release of the proximity sensor failure in a box-elastic form based on the received event data.
The above-described order of judgment is set as needed, and here is only one specific implementation of the present embodiment.
In other operating systems, the processing process is similar in the windows method, and the processing process is realized by using functions in the system, for example, a touch screen is taken as an example, and the reporting flow of the error event is touch driver- > HID class driver- > HIDtouch class driver- > input read- > Native UI, and Native UI displays a popup box.
According to the invention, the person skilled in the art can prompt the bus equipment fault for the mobile terminal of any operating system.
In addition, this embodiment further provides a fault notification system of a mobile terminal, where an operating system kernel of the mobile terminal is provided with a fault event reporting interface, and a structural block diagram of the system is shown in fig. 4 and includes
A communication judging unit 11 that judges whether communication with the bus device is erroneous;
a fault reporting unit 12, configured to receive a fault event reported by a bus device driver when an error occurs;
a bus device determining unit 13 configured to determine a bus device corresponding to the fault event;
the failure presentation unit 14 generates bus device failure presentation information.
In addition, as the optimized scheme, the method further comprises the following steps:
a recovery judging unit 15, which judges whether the bus equipment recovers to normal after making an error;
and the recovery prompting unit 16 generates prompting information for recovering the bus equipment to be normal if the bus equipment is recovered to be normal after an error occurs.
Wherein the bus device comprises a touch screen or a gravity sensor or a proximity sensor or other bus devices.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It should be understood that the above examples are only for clarity of illustration and are not intended to limit the embodiments. Other variations and modifications will be apparent to persons skilled in the art in light of the above description. And are neither required nor exhaustive of all embodiments. And obvious variations or modifications therefrom are within the scope of the invention.
Claims (7)
1. A fault prompting method of a mobile terminal is provided, the mobile terminal comprises a bus device connected with a controller of the mobile terminal through a bus, and a fault event reporting interface is arranged in an operating system kernel of the mobile terminal, and the fault prompting method is characterized by comprising the following steps:
judging whether communication with the bus equipment is in error;
when an error occurs, receiving a fault event reported by bus equipment, wherein the fault event is reported by a driver of the bus equipment; the bus equipment driver reports the fault event to a local framework layer in the Android input system through a fault event reporting interface;
acquiring bus equipment corresponding to the fault event according to the reported fault event;
generating bus device fault prompt information
Judging whether the bus equipment is recovered to be normal after being in error;
and if so, generating prompt information for the bus equipment to recover to normal.
2. The method for prompting fault of mobile terminal according to claim 1, wherein the bus device comprises a touch screen or a gravity sensor or a proximity sensor or other bus devices.
3. The method according to claim 1 or 2, wherein the step of determining whether the communication with the bus device is faulty determines whether the communication with the bus device is faulty by the first bus device reading and writing a return value of the function.
4. The method according to claim 1, wherein in the step of determining whether the bus device is recovered to normal after an error occurs, the method determines whether the communication with the bus device is recovered to normal after an error occurs by using a return value of the read/write function of the second bus device.
5. A fault prompt system of a mobile terminal is provided, a fault event reporting interface is arranged in an operation system kernel of the mobile terminal, and the fault prompt system is characterized by comprising:
a communication judging unit for judging whether communication with the bus device is erroneous;
the fault reporting unit is used for receiving a fault event reported by a bus equipment driver when an error occurs, wherein the fault event is reported by a driver of the bus equipment; the bus equipment driver reports the fault event to a local framework layer in the Android input system through a fault event reporting interface;
a bus device judging unit, configured to judge a bus device corresponding to the fault event;
the fault prompting unit is used for generating fault prompting information of the bus equipment;
the recovery judging unit is used for judging whether the bus equipment is recovered to be normal after being in error;
and the recovery prompting unit is used for recovering to normal after the bus equipment goes wrong to generate the prompting information that the bus equipment recovers to normal.
6. The system of claim 5, wherein the bus device comprises a touch screen or a gravity sensor or a proximity sensor or other bus devices.
7. A fault prompting method of a mobile terminal is applied to an input subsystem of an android operating system, wherein the input subsystem comprises a local framework layer and a Java layer, and the method is characterized by comprising the following steps:
receiving a fault event reported by a driver of the bus equipment through a local framework layer, wherein the fault event is reported by the driver of the bus equipment, and the fault event is reported to the local framework layer in the Android input system through a fault event reporting interface by the driver of the bus equipment; the failure event comprises failure occurrence or failure release;
reporting the fault event to a Java framework layer by the local framework layer;
the input system of the Java framework layer receives the fault event and sends the fault event to a notification manager of the Java framework layer, the notification manager judges the bus equipment to which the fault belongs according to the received fault event and displays the prompt message of fault occurrence or the prompt message of fault release in a bullet frame form, and the fault prompt message acquires the bus equipment corresponding to the fault event according to the reported fault event to generate; and the prompt information is generated according to the bus equipment which is recovered to be normal after the bus equipment is in error.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510589957.9A CN106547667B (en) | 2015-09-16 | 2015-09-16 | Fault prompting method and system for mobile terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510589957.9A CN106547667B (en) | 2015-09-16 | 2015-09-16 | Fault prompting method and system for mobile terminal |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106547667A CN106547667A (en) | 2017-03-29 |
| CN106547667B true CN106547667B (en) | 2020-05-22 |
Family
ID=58361738
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510589957.9A Active CN106547667B (en) | 2015-09-16 | 2015-09-16 | Fault prompting method and system for mobile terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106547667B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108724916B (en) * | 2018-04-18 | 2020-08-18 | 南通达成包装制品有限公司 | Be applied to corrugated board production line's reminding device that rectifies |
| CN109582506B (en) * | 2018-12-25 | 2022-01-07 | 深圳开立生物医疗科技股份有限公司 | Touch screen failure recovery method and device, host equipment and touch system |
| US10897318B2 (en) * | 2019-04-16 | 2021-01-19 | Qualcomm Incorporated | Method and apparatus for maximum permissible exposure proximity sensor fault detection |
| CN111654578B (en) * | 2020-06-02 | 2021-06-15 | Tcl通讯（宁波）有限公司 | Mobile terminal sensor restoration method |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1913693A (en) * | 2006-08-26 | 2007-02-14 | 华为技术有限公司 | Fault information collection system and method |
| CN103019913A (en) * | 2012-11-21 | 2013-04-03 | 广东欧珀移动通信有限公司 | Abnormal prompting method and system for mobile terminals and hardware thereof |
| CN103514030A (en) * | 2012-07-24 | 2014-01-15 | Tcl集团股份有限公司 | Event collecting and reporting system and method of Android system |
| CN103543344A (en) * | 2012-07-10 | 2014-01-29 | 上海斐讯数据通信技术有限公司 | Method for solving failure of capacitive screen and capacitive screen anomaly detection circuit |
| CN104199755A (en) * | 2014-08-25 | 2014-12-10 | 广东欧珀移动通信有限公司 | Method and system for diagnosing hardware module faults based on indicator lights |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101893959B (en) * | 2010-06-22 | 2012-03-28 | 中科方德软件有限公司 | Method for implementing touch direction identification in linux kernel |
| CN102662665B (en) * | 2012-03-29 | 2015-04-22 | 福州瑞芯微电子有限公司 | Input subsystem enabling Android to support various sensors |
| KR102140592B1 (en) * | 2013-10-18 | 2020-08-03 | 에스케이하이닉스 주식회사 | Data storage device |
| CN104184905A (en) * | 2014-09-11 | 2014-12-03 | 三星电子（中国）研发中心 | Electrostatic disturbance processing method of mobile terminal and mobile terminal |
-
2015
- 2015-09-16 CN CN201510589957.9A patent/CN106547667B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1913693A (en) * | 2006-08-26 | 2007-02-14 | 华为技术有限公司 | Fault information collection system and method |
| CN103543344A (en) * | 2012-07-10 | 2014-01-29 | 上海斐讯数据通信技术有限公司 | Method for solving failure of capacitive screen and capacitive screen anomaly detection circuit |
| CN103514030A (en) * | 2012-07-24 | 2014-01-15 | Tcl集团股份有限公司 | Event collecting and reporting system and method of Android system |
| CN103019913A (en) * | 2012-11-21 | 2013-04-03 | 广东欧珀移动通信有限公司 | Abnormal prompting method and system for mobile terminals and hardware thereof |
| CN104199755A (en) * | 2014-08-25 | 2014-12-10 | 广东欧珀移动通信有限公司 | Method and system for diagnosing hardware module faults based on indicator lights |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106547667A (en) | 2017-03-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106547667B (en) | Fault prompting method and system for mobile terminal | |
| US8468389B2 (en) | Firmware recovery system and method of baseboard management controller of computing device | |
| CN109670319B (en) | Server flash safety management method and system thereof | |
| CN111427803B (en) | Automated random test method, apparatus, computer device and medium | |
| CN104794014A (en) | System operation method and intelligent terminal | |
| CN104185836A (en) | Method and system for verifying proper operation of computing device after system change | |
| CN109032838B (en) | Automatic verification method for consistency of backup and recovery data of virtual machine | |
| US8375198B2 (en) | Boot system and method having a BIOS that reads an operating system from first storage device via an input/output chip based on detecting a temperature of a second storage device | |
| KR101714522B1 (en) | Method and apparatus for providing linking service between vehicle audio video nevigation and smartphone based on virtualization framework | |
| CN113672306B (en) | Server component self-checking abnormity recovery method, device, system and medium | |
| CN106168974B (en) | Method and system for processing multi-system screenshot file | |
| CN108520063B (en) | Event log processing method and device and terminal equipment | |
| CN110096882B (en) | Safety measurement method in equipment operation process | |
| CN104750537A (en) | Test case execution method and device | |
| CN106201787A (en) | Terminal control method and device | |
| CN111475356A (en) | System startup test information display method and related device | |
| CN115168119A (en) | PCIE (peripheral component interface express) link detection method, device and medium for server | |
| CN115373559A (en) | All-in-one machine touch operation method and device, storage medium and all-in-one machine | |
| CN114113855A (en) | Electrostatic discharge detection processing method and device and terminal equipment | |
| CN115185745A (en) | Data processing method, system, electronic device and computer readable storage medium | |
| CN104951325A (en) | Information display method and electronic equipment | |
| CN107766251B (en) | Detection method, system and device for loading image and readable storage medium | |
| CN114461479A (en) | Method and device for debugging multimedia processing chip, storage medium and electronic equipment | |
| CN110837433A (en) | Performance optimization method and device and electronic equipment | |
| CN114026539A (en) | Storing POST code in electronic tag |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |