CN103428333B - Mobile terminal, server and errors repair method - Google Patents
Mobile terminal, server and errors repair method Download PDFInfo
- Publication number
- CN103428333B CN103428333B CN201210149220.1A CN201210149220A CN103428333B CN 103428333 B CN103428333 B CN 103428333B CN 201210149220 A CN201210149220 A CN 201210149220A CN 103428333 B CN103428333 B CN 103428333B
- Authority
- CN
- China
- Prior art keywords
- mistake
- server
- communication unit
- mobile terminal
- sent
- 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
Abstract
The invention provides a kind of mobile terminal, comprising: detecting unit, detect the ruuning situation of mobile terminal, when mistake appears in mobile terminal, record described mistake; Communication unit, is connected to described detecting unit, the reparation patch corresponding with described mistake described mistake being sent to server and receiving from described server; Repair unit, be connected to described communication unit, repair described mistake according to described corresponding reparation patch.According to technical scheme of the present invention, can monitor the mistake of mobile terminal and report ruuning situation, initiatively the mistake occurred be repaired, improve the stability of system.Present invention also offers a kind of server and a kind of errors repair method.
Description
Technical field
The present invention relates to communication technical field, in particular to mobile terminal, server and errors repair method.
Background technology
Along with the development of intelligent terminal; various application software is also arisen at the historic moment; in use; often there will be system mistake or software error; if application software is collapsed, user can only close this application software by force or reinstall application software, if collapse in system operation or go out to misrepresent deliberately extremely; user also cannot solve, can only restarting systems.
Secondly, if certain File lose or document lending in terminal system, or in system, the startup of certain module makes mistakes, then terminal can remain on black state always, cannot continue to start, and has had a strong impact on the normal use of user.
Summary of the invention
Consider above-mentioned background technology, an object of the present invention is to provide a kind of mobile terminal, can the mistake that operationally occurs of repair system or software, improve the stability of a system.
In view of this, according to an aspect of the present invention, provide a kind of mobile terminal, comprising: detecting unit, detect the ruuning situation of mobile terminal, when mistake appears in mobile terminal, record described mistake; Communication unit, is connected to described detecting unit, the reparation patch corresponding with described mistake described mistake being sent to server and receiving from described server; Repair unit, be connected to described communication unit, repair described mistake according to described corresponding reparation patch.
When there is mistake in mobile terminal, the situation of this mistake can be recorded in daily record, and mistake is sent to server, the solution of this mistake is issued by server, and repair this mistake, and then improve the stability of mobile terminal, avoid user to run into this mistake just needs positive closing software or system at every turn, affects the normal use of user.
In technique scheme, preferably, described detecting unit, also for adding up the record number of times of described mistake, when described record number of times is more than or equal to threshold value, orders described communication unit that described mistake is sent to described server.
When errors are encountered, occurred mistake can be recorded in daily record, and statistics often kind of wrong number of times, if number of times exceeds threshold value, illustrate that this mistake more seriously and often occur, then can report server by this mistake, repair corresponding mistake.If number of times is one time twice, the chance made a mistake after illustrating is less, then can repair, and avoids frequent reparation to affect the normal use of user.
In above-mentioned arbitrary technical scheme, preferably, whether described detecting unit also for when described mobile terminal cannot normally start, detects described communication unit and starts, if described communication unit starts, then by described communication unit, the mistake of described appearance is sent to described server.
In the process that mobile terminal starts, normally unit is started by sequence one by one, namely a unit cannot start the startup that can not affect other unit, but terminal can be caused to rest on the blank screen stage always, and then cause terminal cannot continue to start, have a strong impact on the use of user, if communication unit normally starts, then the mistake that other unit occur can be reported server by information unit, receive the reparation patch from server, thus repair the mistake of other unit appearance, avoid terminal to rest on the blank screen stage always.
In technique scheme, preferably, can also comprise: Tip element, be connected to described detecting unit, when described detecting unit detects that described communication unit is not activated, prompting user will close described mobile terminal.
If detect, communication unit does not normally start, then point out the information that described in user, communication unit does not normally start.
According to a further aspect in the invention, additionally provide a kind of server, comprising: communication unit, receive the mistake from the such as mobile terminal described in above-mentioned arbitrary technical scheme, and be sent to described mobile terminal by searching the reparation patch that unit finds out; Memory cell, carries out corresponding stored by mistake and reparation patch; Describedly search unit, be connected to described communication unit and described memory cell, according to the mistake that described communication unit receives, in described memory cell, find out the reparation patch corresponding with the mistake of described reception.
According to another aspect of the invention, additionally provide a kind of errors repair method, comprise the following steps: the ruuning situation of sense terminals, when mistake appears in terminal, record described mistake and described mistake is sent to server; According to mistake preset in described server and the corresponding relation repairing patch, find out the reparation patch corresponding with the mistake that described terminal sends; Described corresponding reparation patch is sent to described terminal to repair described mistake.
When there is mistake in mobile terminal, the situation of this mistake can be recorded in daily record, and mistake is sent to server, the solution of this mistake is issued by server, and repair this mistake, and then improve the stability of mobile terminal, avoid user to run into this mistake just needs positive closing software or system at every turn, affects the normal use of user.
In technique scheme, preferably, describedly record described mistake and the step described mistake being sent to server can also comprise: the record number of times adding up described mistake, when described record number of times is more than or equal to threshold value, is sent to described server by described mistake.
When errors are encountered, occurred mistake can be recorded in daily record, and statistics often kind of wrong number of times, if number of times exceeds threshold value, illustrate that this mistake more seriously and often occur, then can report server by this mistake, repair corresponding mistake.If number of times is one time twice, the chance made a mistake after illustrating is less, then can repair, and avoids frequent reparation to affect the normal use of user.
In above-mentioned arbitrary technical scheme, preferably, can also comprise: if described server does not find out described corresponding reparation patch, then the mistake that described terminal sends is sent to designated contact, the reparation patch corresponding with the mistake of described transmission is sent to described server and preserves by described designated contact, to upgrade described preset mistake and the corresponding relation repairing patch.
In the process that mobile terminal starts, normally unit is started by sequence one by one, namely a unit cannot start the startup that can not affect other unit, but terminal can be caused to rest on the blank screen stage always, and then cause terminal cannot continue to start, have a strong impact on the use of user, if communication unit normally starts, then the mistake that other unit occur can be reported server by information unit, receive the reparation patch from server, thus repair the mistake of other unit appearance, avoid terminal to rest on the blank screen stage always.
In above-mentioned arbitrary technical scheme, preferably, can also comprise: when described terminal cannot normally start, whether the communication unit detecting described terminal starts, if described communication unit starts, then by described communication unit, the mistake of described appearance is sent to described server.
In technique scheme, preferably, if described communication unit is not activated, then points out described in user and believe the information that module is not activated.
Accompanying drawing explanation
Fig. 1 shows the block diagram of mobile terminal according to an embodiment of the invention;
Fig. 2 shows the block diagram of server according to an embodiment of the invention;
Fig. 3 shows mobile terminal and server according to an embodiment of the invention and carries out the schematic diagram of data interaction;
Fig. 4 shows the flow chart of errors repair method according to an embodiment of the invention;
Fig. 5 shows the flow chart of errors repair method according to still another embodiment of the invention;
Fig. 6 shows the flow chart of the errors repair method according to one more embodiment of the present invention.
Embodiment
In order to more clearly understand above-mentioned purpose of the present invention, feature and advantage, below in conjunction with the drawings and specific embodiments, the present invention is further described in detail.
Set forth a lot of detail in the following description so that fully understand the present invention; but; the present invention can also adopt other to be different from other modes described here and implement, and therefore, protection scope of the present invention is not by the restriction of following public specific embodiment.
Below in conjunction with drawings and Examples, the present invention will be further described.It should be noted that, when not conflicting, the feature in the embodiment of the application and embodiment can combine mutually.
First describe in detail according to embodiments of the invention referring to figs. 1 to Fig. 3.
Fig. 1 shows the block diagram of mobile terminal according to an embodiment of the invention.
As shown in Figure 1, mobile terminal 100 comprises according to an embodiment of the invention: detecting unit 102, detects the ruuning situation of mobile terminal, when mistake appears in mobile terminal, records described mistake; Communication unit 104, is connected to described detecting unit 102, the reparation patch corresponding with described mistake described mistake being sent to server 200 and receiving from described server 200; Repair unit 106, be connected to described communication unit 104, repair described mistake according to described corresponding reparation patch.
When there is mistake in mobile terminal, the situation of this mistake can be recorded in daily record, and mistake is sent to server, the solution of this mistake is issued by server, and repair this mistake, and then improve the stability of mobile terminal, avoid user to run into this mistake just needs positive closing software or system at every turn, can not affect the normal use of user.
In technique scheme, preferably, described detecting unit 102, also for adding up the record number of times of described mistake, when described record number of times is more than or equal to threshold value, orders described communication unit 104 that described mistake is sent to described server 200.
When errors are encountered, occurred mistake can be recorded in daily record, and statistics often kind of wrong number of times, if number of times exceeds threshold value, illustrate that this mistake more seriously and often occur, then can report server by this mistake, repair corresponding mistake.If number of times is one time twice, the chance made a mistake after illustrating is less, then can repair, and avoids frequent reparation to affect the normal use of user.
In above-mentioned arbitrary technical scheme, preferably, whether described detecting unit 102 also for when described mobile terminal cannot normally start, detects described communication unit and starts, if described communication unit starts, then by described communication unit, the mistake of described appearance is sent to described server.
In the process that mobile terminal starts, normally unit is started by sequence one by one, namely a unit cannot start the startup that can not affect other unit, but terminal can be caused to rest on the blank screen stage always, and then cause terminal cannot continue to start, have a strong impact on the use of user, if communication unit normally starts, then the mistake that other unit occur can be reported server by information unit, receive the reparation patch from server, thus repair the mistake of other unit appearance, avoid terminal to rest on the blank screen stage always.
In technique scheme, preferably, can also comprise: Tip element 108, be connected to described detecting unit, when described detecting unit detects that described communication unit is not activated, prompting user will close described mobile terminal.
If detect, communication unit does not normally start, then point out the information that described in user, communication unit does not normally start.
Fig. 2 shows the block diagram of server according to an embodiment of the invention.
As shown in Figure 2, server 200 comprises according to an embodiment of the invention: communication unit 202, receive the mistake from the such as mobile terminal 100 described in above-mentioned arbitrary technical scheme, and be sent to described mobile terminal by searching the reparation patch that unit 206 finds out; Memory cell 204, carries out corresponding stored by mistake and reparation patch; Describedly search unit 206, be connected to described communication unit 202 and described memory cell 204, according to the mistake that described communication unit 202 receives, in described memory cell, find out the reparation patch corresponding with the mistake of described reception.
Fig. 3 shows mobile terminal and server according to an embodiment of the invention and carries out the schematic diagram of data interaction.As shown in Figure 3, when terminal system starts by mobile terminal 100, during system cloud gray model or running software time the mistake that occurs carry out adding up and mistake statistics number being exceeded threshold value is sent to server 200, to prestore the corresponding solution of multiple mistake at server 200, after finding out the solution (reparation patch) corresponding with this mistake according to the mistake of mobile terminal 100 transmission, corresponding solution is back to mobile terminal 100, repairs the mistake occurred.If server 200 does not find out the solution corresponding with the mistake that mobile terminal 100 sends, then this mistake is sent to engineer, in figure 3, can be sent in the notebook computer 300 of engineer by mail box fashion, engineer finds out solution after receiving this mistake, then by notebook computer 300, this mistake is sent to server 200 to preserve, when again there is same error in mobile terminal 100, the solution that engineering is uploaded just can be fed back to mobile terminal 100 by server 200, add the self-regeneration function of mobile terminal, improve the stability of a system.
Fig. 4 shows the flow chart of errors repair method according to an embodiment of the invention.
As shown in Figure 4, errors repair method, comprises the following steps: step 402 according to an embodiment of the invention, the ruuning situation of sense terminals, and when mistake appears in terminal, mistake is also sent to server by misregistration; Step 404, according to mistake preset in server and the corresponding relation repairing patch, finds out the reparation patch corresponding with the mistake that terminal sends; Step 406, is sent to terminal with mis repair by corresponding reparation patch.
When there is system or software error in mobile terminal, the situation of this mistake can be recorded in daily record, and mistake is sent to server, the solution of this mistake is issued by server, and repair this mistake, and then improve the stability of system, avoid user to run into this mistake just needs positive closing software or system at every turn, can not affect the normal use of user.
In technique scheme, preferably, misregistration step mistake being sent to server can also comprise: the record number of times of mistake of statistics, when recording number of times and being more than or equal to threshold value, is sent to server by mistake.
When errors are encountered, occurred mistake can be recorded in daily record, and statistics often kind of wrong number of times, if number of times exceeds threshold value, illustrate that this mistake more seriously and often occur, then can report server by this mistake, repair corresponding mistake.If number of times is one time twice, the chance made a mistake after illustrating is less, then can repair, and avoids frequent reparation to affect the normal use of user.
In above-mentioned arbitrary technical scheme, preferably, can also comprise: if server does not find out corresponding reparation patch, then the mistake that terminal sends is sent to designated contact, the reparation patch corresponding with the mistake sent is sent to server and preserves by designated contact, to upgrade preset mistake and the corresponding relation repairing patch.
In the process that terminal starts, normally unit is started by sequence one by one, namely a unit cannot start the startup that can not affect other unit, but terminal can be caused to rest on the blank screen stage always, and then cause terminal cannot continue to start, have a strong impact on the use of user, if communication unit normally starts, then the mistake that other unit occur can be reported server by information unit, receive the reparation patch from server, thus repair the mistake of other unit appearance, avoid terminal to rest on the blank screen stage always.
In above-mentioned arbitrary technical scheme, preferably, the system of terminal can also comprise the following steps: when cannot normally start, whether the communication unit of sense terminals starts, if communication unit starts, then detect the mistake that other modules occur, by communication unit, the mistake of appearance is sent to server.
In technique scheme, preferably, if communication unit is not activated, then point out the information that described in user, communication unit is not activated.The signal lamp flicker etc. that described prompting can be voice message, specify, when terminal can normally show, also can pass through display screen display reminding information.
Errors repair method is according to still another embodiment of the invention further illustrated below in conjunction with Fig. 5.
As shown in Figure 5, in step 502, when system cannot normally start, detect lattice module and whether normally start, profiling error reason.It should be noted that, android mobile phone is when starting, first start linux virtual machine, then on linux virtual machine, start Android system, when starting Android system, normally each module starts successively, that is, a module cannot start the normal startup that can not have influence on other modules in system, but cell phone system but can be caused to rest on the blank screen stage always, and then causes cell phone system cannot continue to start.
In step 504, judge whether communication unit normally starts, if normally start, then enter step 506, if normally do not start, then enter step 510.If the communication unit rested in the mobile phone of black state normally starts, that just utilizes communication unit to come to carry out alternately with server by network, so the communication unit started can be utilized to server to report the problem of handset starting blank screen, and download corresponding reparation file or system upgrade bag by communication unit, system blank screen problem is repaired.
Step is in step 510, and prompting user is about to shut down and shut down.
In step 506, automatic detected error (such as display module goes wrong) is sent to server.
In step 508, after server receives reason of makeing mistakes, if some system file is lost, then issued the file of loss by system communication locations; If system problem is serious, does not just lack certain file, then automatically issue AKU in terminal by communication unit.After the complete AKU of terminal downloads, Auto-mounting also restarts terminal.
When cell phone system startup makes mistakes and rests on the blank screen stage, data interaction is carried out by the communication unit that started and server, failure cause is sent to server, automatically download loss or the file of makeing mistakes or download AKU from server automatically to repair to carry out system, download successfully and restart mobile phone, enter upgrade mode, and loading upgrading bag, upgrade file is installed in systems in which, and then the self-regeneration of completion system blank screen.
Below in conjunction with Fig. 6, the errors repair method according to one more embodiment of the present invention is described
As shown in Figure 6, in step 602, when system starts, start detection system or running software situation, if system or application software are run make mistakes, automatically record in daily record.
In step 604, timing daily record is analyzed, to same problem make mistakes number of times statistics, whether misjudgment number of times exceedes the threshold value of engineer or user's setting, if the determination result is YES, then enter step 606, upload onto the server after log file analysis is arranged; If judged result is no, then terminate this flow process.
In step 608, server carries out analyzing and processing after receiving the journal file uploaded again, whether the mistake analyzed in journal file pre-sets solution or patch in the server, if had the solution pre-set or patch in server, then progressively deal with problems according to solution or automatically issue patch, if server cannot be dealt with problems, then the problem log put in order is preserved, and (by mail or note form) notifies correlation engineering teacher, after engineer receives problem, analyze and propose solution or develop corresponding patch, then reparation patch is uploaded onto the server, the terminal of makeing mistakes is issued to by server, and preservation is automatically solved by server in the server after running into same problem next time.
Can the ruuning situation of real-time detecting system or software according to technical scheme of the present invention, when after system or software report exception, automatic misregistration in daily record, engineer or user can set a threshold value, after the number of times that report is abnormal reaches this value, error situation will be reported from trend server, server can carry out report analysis after receiving and reporting mistake, if set solution or patch in the server, server automatically issues patch file and repairs system or software, if there is no solution in server, special engineer then can be transferred to carry out analyze and solve, after engineer has solved problem, corresponding solution or patch is uploaded on server, with make server next time run into same problem after automatically solve process.
In the present invention, unless otherwise clearly defined and limited, the term such as term " installation ", " being connected ", " connection ", " fixing " should be interpreted broadly, and such as, can be fixedly connected with, also can be removably connect, or connect integratedly; Can be mechanical connection, also can be electrical connection; Can be directly be connected, also indirectly can be connected by intermediary, can be the connection of two element internals.For the ordinary skill in the art, above-mentioned term concrete meaning in the present invention can be understood as the case may be.
The foregoing is only the preferred embodiments of the present invention, be not limited to the present invention, for a person skilled in the art, the present invention can have various modifications and variations.Within the spirit and principles in the present invention all, any amendment done, equivalent replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (6)
1. a mobile terminal, is characterized in that, comprising:
Detecting unit, detects the ruuning situation of mobile terminal, when mistake appears in mobile terminal, records described mistake;
Communication unit, is connected to described detecting unit, the reparation patch corresponding with described mistake described mistake being sent to server and receiving from described server;
Repair unit, be connected to described communication unit, repair described mistake according to described corresponding reparation patch;
Whether described detecting unit also for when described mobile terminal cannot normally start, detects described communication unit and starts, if described communication unit starts, then by described communication unit, the mistake of described appearance is sent to described server;
Described detecting unit, also for adding up the record number of times of described mistake, when described record number of times is more than or equal to threshold value, orders described communication unit that described mistake is sent to described server.
2. mobile terminal according to claim 1, is characterized in that, also comprises: Tip element, is connected to described detecting unit, and when described detecting unit detects that described communication unit is not activated, prompting user will close described mobile terminal.
3. a server, is characterized in that, comprising:
Communication unit, receives the mistake from mobile terminal as claimed in claim 1 or 2, and is sent to described mobile terminal by searching the reparation patch that unit finds out;
Memory cell, carries out corresponding stored by mistake and reparation patch;
Describedly search unit, be connected to described communication unit and described memory cell, according to the mistake that described communication unit receives, in described memory cell, find out the reparation patch corresponding with the mistake of described reception.
4. an errors repair method, is characterized in that, comprises the following steps:
The ruuning situation of sense terminals, when mistake appears in terminal, records described mistake and described mistake is sent to server;
According to mistake preset in described server and the corresponding relation repairing patch, find out the reparation patch corresponding with the mistake that described terminal sends;
Described corresponding reparation patch is sent to described terminal to repair described mistake;
When described terminal cannot normally start, whether the communication unit detecting described terminal starts, if described communication unit starts, then by described communication unit, the mistake of described appearance is sent to described server;
Describedly record described mistake and the step described mistake being sent to server also comprises: the record number of times adding up described mistake, when described record number of times is more than or equal to threshold value, is sent to described server by described mistake.
5. errors repair method according to claim 4, it is characterized in that, also comprise: if described server does not find out described corresponding reparation patch, then the mistake that described terminal sends is sent to designated contact, the reparation patch corresponding with the mistake of described transmission is sent to described server and preserves by described designated contact, to upgrade described preset mistake and the corresponding relation repairing patch.
6. errors repair method according to claim 4, is characterized in that, if described communication unit is not activated, then points out user and closes described terminal.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210149220.1A CN103428333B (en) | 2012-05-15 | 2012-05-15 | Mobile terminal, server and errors repair method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210149220.1A CN103428333B (en) | 2012-05-15 | 2012-05-15 | Mobile terminal, server and errors repair method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103428333A CN103428333A (en) | 2013-12-04 |
| CN103428333B true CN103428333B (en) | 2015-12-16 |
Family
ID=49652491
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210149220.1A Active CN103428333B (en) | 2012-05-15 | 2012-05-15 | Mobile terminal, server and errors repair method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103428333B (en) |
Families Citing this family (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104794054A (en) * | 2015-04-22 | 2015-07-22 | 惠州Tcl移动通信有限公司 | Log information real-time obtaining and uploading method and system and mobile terminal |
| CN105812477A (en) * | 2016-04-15 | 2016-07-27 | 广州杰赛科技股份有限公司 | Cloud disk deployment method and system |
| CN107817984A (en) * | 2016-09-13 | 2018-03-20 | 高德信息技术有限公司 | A kind of hot patch loading method and device |
| CN108008972A (en) * | 2016-10-27 | 2018-05-08 | 北京京东尚科信息技术有限公司 | Restorative procedure, the apparatus and system of the application program of client |
| CN106791976A (en) * | 2016-12-07 | 2017-05-31 | 康佳集团股份有限公司 | The method and system of application have been installed in a kind of Android television monitoring and treatment |
| CN106776243B (en) * | 2016-12-30 | 2021-03-16 | 中国银联股份有限公司 | Monitoring method and device for monitoring software |
| CN109933478B (en) * | 2017-12-19 | 2021-02-26 | 华为技术有限公司 | Storage system and fault processing method thereof |
| CN112822065B (en) * | 2020-12-30 | 2022-07-15 | 上海数果科技有限公司 | Linux-based talkback service monitoring system and monitoring method |
| CN113641386A (en) * | 2021-08-17 | 2021-11-12 | 西安酷赛科技有限公司 | Method and system for upgrading based on error reporting frequency |
| CN115277747B (en) * | 2022-06-24 | 2023-06-23 | 共青科技职业学院 | Vehicle network repair method, system, computer device and readable storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6389288B1 (en) * | 1997-06-27 | 2002-05-14 | Fujitsu Limited | Mobile communication terminal capable of executing location-related services |
| CN1470985A (en) * | 2002-07-24 | 2004-01-28 | 力捷电脑股份有限公司 | Error back-report and correction method for peripheral unit |
| CN101175109A (en) * | 2006-10-31 | 2008-05-07 | 中兴通讯股份有限公司 | System abnormal information processing method and device |
| CN101631324A (en) * | 2009-08-11 | 2010-01-20 | 酷派软件技术（深圳）有限公司 | Mobile terminal fault diagnosis and repair method and mobile terminal thereof |
| CN101714105A (en) * | 2008-10-07 | 2010-05-26 | 英业达股份有限公司 | Error reporting and error solving replying system of application program and method thereof |
| CN102056202A (en) * | 2009-10-29 | 2011-05-11 | 中兴通讯股份有限公司 | Mobile terminal error processing method and system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP4309198B2 (en) * | 2003-07-30 | 2009-08-05 | Ｎｅｃインフロンティア株式会社 | Voice data wireless communication system and voice data wireless communication program |
-
2012
- 2012-05-15 CN CN201210149220.1A patent/CN103428333B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6389288B1 (en) * | 1997-06-27 | 2002-05-14 | Fujitsu Limited | Mobile communication terminal capable of executing location-related services |
| CN1470985A (en) * | 2002-07-24 | 2004-01-28 | 力捷电脑股份有限公司 | Error back-report and correction method for peripheral unit |
| CN101175109A (en) * | 2006-10-31 | 2008-05-07 | 中兴通讯股份有限公司 | System abnormal information processing method and device |
| CN101714105A (en) * | 2008-10-07 | 2010-05-26 | 英业达股份有限公司 | Error reporting and error solving replying system of application program and method thereof |
| CN101631324A (en) * | 2009-08-11 | 2010-01-20 | 酷派软件技术（深圳）有限公司 | Mobile terminal fault diagnosis and repair method and mobile terminal thereof |
| CN102056202A (en) * | 2009-10-29 | 2011-05-11 | 中兴通讯股份有限公司 | Mobile terminal error processing method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103428333A (en) | 2013-12-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103428333B (en) | Mobile terminal, server and errors repair method | |
| CN103377094B (en) | Method for monitoring abnormality and device | |
| CN105611330B (en) | Smart television maintenance method and system, server and mobile terminal | |
| CN103458086B (en) | A kind of smart mobile phone and fault detection method thereof | |
| CN102591745B (en) | Method and device for system recovery based on android system and intelligent equipment | |
| CN103530199A (en) | Software running error repairing method, device and system | |
| CN102508734B (en) | Operating system recovery method and intelligent equipment | |
| CN101466115A (en) | Failure detection method, system and mobile terminal | |
| CN102681871A (en) | Firmware upgrading system based on communication interfaces | |
| CN102736978A (en) | Method and device for detecting installation status of application program | |
| JP2014130585A (en) | Firmware upgrade error detection and automatic rollback | |
| CN107678875B (en) | Fault detection and automatic repair method, device, terminal and storage medium | |
| CN111143150A (en) | Method and system for testing PCBA (printed circuit board assembly), testing equipment and micro-control unit | |
| CN103249027B (en) | The method and apparatus that a kind of terminal traffic processes | |
| CN104049999A (en) | Automatic storage device repair system based on network and method thereof | |
| CN106897166B (en) | Mobile terminal and repairing method thereof | |
| CN103309712A (en) | Mobile phone software upgrade method and system | |
| CN103019751A (en) | Plug-in equipment matching and maintaining method | |
| WO2015120687A1 (en) | Method and apparatus for diagnosing and solving mobile terminal fault | |
| CN103970564A (en) | Automatic repairing and upgrading method of embedded operating system and embedded operating system with automatic repairing and upgrading functions | |
| CN108121612A (en) | A kind of collapse processing method and system based on linux kernel router | |
| CN106604138A (en) | Remote restoration method and system for intelligent television | |
| CN105824649A (en) | Method and device for determining whether installation of driver application program is successful and electronic equipment | |
| CN108111343B (en) | Method and equipment for realizing terminal monitoring based on cloud platform and computer storage medium | |
| CN110198222B (en) | Plug-and-play test method and test master station for power distribution automation terminal |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |