JP7708621B2 - Mobile terminal, information processing method, and information processing program - Google Patents

Description

The present invention relates to a mobile terminal, an information processing method, and an information processing program.

In recent years, mobile terminals have been proposed that diagnose the causes of problems such as an inability to communicate or an application program not operating as desired, and suggest solutions or provide guidance on operations to resolve the problem (see Patent Documents 1 and 2).

Patent No. 6492149 Patent No. 6405024

Many mobile device users are unfamiliar with information technology. Even if suggested solutions or instructions on how to resolve a problem are given, these users may find it difficult to carry them out. In addition, in order to resolve a problem, users must approve the proposed solutions or perform the necessary operations to resolve the problem, which is a hassle for users.

One aspect of the disclosed technology aims to provide a mobile terminal, an information processing method, and an information processing program that can reduce the burden on users in resolving malfunctions.

One aspect of the disclosed technology is exemplified by a mobile terminal as follows. The mobile terminal includes a storage unit that stores a correspondence between installed application programs and default settings set in the application programs, and a control unit. The control unit displays a list of application programs selected based on the usage history of the application programs, accepts designation of a first application program from the list, and, if the setting value set in the first application program differs from the first default value associated with the first application program in the storage unit, changes the setting value of the first application program to the first default value.

The disclosed technology can reduce the burden on users in resolving problems.

FIG. 1 is a diagram illustrating an example of a hardware configuration of a smartphone according to an embodiment. FIG. 2 is a diagram illustrating an example of a processing block of the smartphone according to the embodiment. FIG. 3 is a diagram illustrating an example of an application usage history management table stored in the management database in the embodiment. FIG. 4 is a diagram illustrating an example of a default value management table stored in the management database in the embodiment. FIG. 5 is a diagram illustrating an example of a Web information management table stored in the management database in the embodiment. FIG. 6 is a diagram showing an example of a display item candidate list stored in the management database in the embodiment. FIG. 7 is a diagram illustrating an example of an application usage history confirmation screen according to the embodiment. FIG. 8 is a diagram illustrating an example of an application usage history checking screen according to the embodiment. FIG. 9 is a diagram illustrating an example of an application selection screen according to the embodiment. FIG. 10 is a diagram illustrating an example of an application selection screen on which "medium items" are displayed in the embodiment. FIG. 11 is a diagram showing an example of a diagnosis screen in the embodiment. FIG. 12 is a diagram showing an example of a result display screen in the embodiment. FIG. 13 is a diagram illustrating an example of a processing flow of the smartphone according to the embodiment. FIG. 14 is a diagram showing an example of a process flow of T1 in FIG. FIG. 15 is a diagram showing an example of the process flow of T15 in FIG. FIG. 16 is a diagram showing an example of a diagnosis screen in the first modified example. FIG. 17 is a first diagram showing an example of a result display screen in the second modified example. FIG. 18 is a second diagram showing an example of the result display screen in the second modified example.

<Embodiment>
The configurations of the embodiments described below are merely examples, and the disclosed technology is not limited to the configurations of the embodiments. A mobile terminal according to the embodiment includes, for example, a storage unit that stores a correspondence relationship between an installed application program and a default value of a setting value set in the application program, and a control unit.

The control unit displays a list of application programs selected based on the usage history of the application programs, accepts designation of a first application program from the list, and, if a setting value set in the first application program differs from a first default value associated with the first application program in the storage unit, changes the setting value of the first application program to the first default value.

The mobile terminal is, for example, a smartphone, a tablet terminal, or a wearable terminal. In the mobile terminal, application programs selected based on usage history are displayed in a list. In such a list, for example, application programs most recently used by the user or application programs that the user uses frequently are displayed. When a user notices the occurrence of a malfunction and attempts to resolve the malfunction, it is considered highly likely that the application program that the user wishes to resolve the malfunction is an application program that was most recently used or an application program that is frequently used. Therefore, the mobile terminal can present application programs that the user is highly likely to wish to resolve.

In addition, in this mobile terminal, the correspondence between the installed application programs and the default values of the setting values set in the application programs is stored in the storage unit, so the default value to be set in the specified application program can be determined univocally. Therefore, this mobile terminal can change the setting value of the application program to the default value without inquiring of the user as to whether or not the setting can be changed.

The list displays application programs that the user has used. In other words, application programs that the user is unfamiliar with are prevented from being displayed in the list. It is believed that even a user unfamiliar with information technology can easily specify an application program for which a malfunction is to be resolved from a list of familiar application programs. Furthermore, a user unfamiliar with information technology may have difficulty in deciding whether or not to change the settings when asked whether or not to change the settings. In contrast, as described above, with this mobile terminal, the setting values of the application program are changed to default values without inquiring of the user as to whether or not to change the settings, so the user does not have to worry about whether or not to change the settings. Therefore, with this mobile terminal, the burden on the user in resolving malfunctions can be reduced.

The mobile terminal described above can also be understood from the perspective of an information processing method and an information processing program.

The following further describes an embodiment in which the above-mentioned mobile terminal is applied to a smartphone, with reference to the drawings. FIG. 1 is a diagram showing an example of the hardware configuration of a smartphone 100 according to an embodiment. FIG. 1 also illustrates an example of the hardware configuration of a server 300 that communicates with the smartphone 100. The smartphone 100 and the server 300 communicate with each other via a network N1.

The smartphone 100 is a portable information processing device. The smartphone 100 includes a Central Processing Unit (CPU) 101, a Random Access Memory (RAM) 102, a Read Only Memory (ROM) 103, a communication unit 104, a speaker 111, a microphone 112, a display 113, and a touch panel 114. The CPU 101, the RAM 102, the ROM 103, the communication unit 104, the speaker 111, the microphone 112, the display 113, and the touch panel 114 are interconnected by a connection bus B1.

The CPU 101 is also called a microprocessor unit (MPU) or a processor. The CPU 101 is not limited to a single processor, and may have a multi-processor configuration. A single CPU 101 connected to a single socket may have a multi-core configuration. At least a part of the processing performed by the CPU 101 may be performed by a processor other than the CPU 101, for example, a dedicated processor such as a digital signal processor (DSP), a graphics processing unit (GPU), a numerical calculation processor, a vector processor, or an image processing processor. At least a part of the processing performed by the CPU 101 may be performed by an integrated circuit (IC) or other digital circuit. At least a part of the CPU 101 may include an analog circuit. The integrated circuit includes a large scale integrated circuit (LSI), an application specific integrated circuit (ASIC), and a programmable logic device (PLD). The PLD includes, for example, a field-programmable gate array (FPGA). The CPU 101 may be a combination of a processor and an integrated circuit. The combination is called, for example, a microcontroller unit (MCU), a system-on-a-chip (SoC), a system LSI, a chipset, etc. In the smartphone 100, the CPU 101 expands a program stored in the ROM 103 into a working area of the RAM 102, and controls peripheral devices through the execution of the program. This allows the smartphone 100 to execute processing that matches a predetermined purpose. RAM 102 and ROM 103 are recording media that can be read by smartphone 100.

RAM 102 is exemplified as a storage unit that is directly accessed by CPU 101. RAM 102 is used, for example, as a working area for CPU 101.

The ROM 103 stores various programs and various data on a recording medium. The ROM 103 stores an operating system (OS), various programs, various tables, and the like. The OS includes a communication interface program that transfers data to and from an external device connected via the communication unit 104. The ROM 103 may be, for example, an erasable programmable ROM (EPROM) or an electrically erasable programmable read-only memory (EEPROM). The RO
M103 may include a flash memory or a solid state drive (SSD).

The communication unit 104 is an interface with the network N1. The communication unit 104 communicates with external devices via the network N1.

The speaker 111 is a device that outputs sound. For example, the speaker 111 outputs sound such as the voice of the other party during a call using the smartphone 100. The microphone 112 accepts input of the user's voice during a call using the smartphone 100.

Display 113 displays data processed by CPU 101 and data stored in RAM 102 and ROM 103. Display 113 is, for example, a Cathode Ray Tube (CRT) display, a Liquid Crystal Display (LCD), a Plasma Display Panel (PDP), an Electroluminescence (EL) panel, or an organic EL panel.

The touch panel 114 detects the touch position when the user touches the smartphone 100 with a finger or the like. By including the touch panel 114, the smartphone 100 can provide the user with an intuitive operating environment. It is preferable that the touch panel 114 be provided on the entire surface of the display 113.

The server 300 is an information processing device. The server 300 includes a CPU 101, a RAM 102, a ROM 103, and a communication unit 104. In the server 300, the CPU 101, the RAM 102, the ROM 103, and the communication unit 104 are also interconnected by a connection bus B1.

The network N1 is a computer network that connects information processing devices so that they can communicate with each other. The network N1 is, for example, a Local Area Network (LAN), a mobile phone communication line, or the Internet. The network N1 may be wired or wireless.

<Processing blocks of the smartphone 100>
2 is a diagram showing an example of a processing block of the smartphone 100 according to the embodiment. The smartphone 100 includes a control unit 20 and a management database 24. The control unit 20 includes a Web information acquisition unit 21, a usage history acquisition unit 22, and a terminal information acquisition unit 23. The smartphone 100 executes processing as each unit of the smartphone 100, such as the control unit 20 and the management database 24, by the CPU 101 executing a computer program executablely deployed in the RAM 102.

The management database 24 is a database that manages the usage status of application programs (hereinafter also referred to as apps) installed in the smartphone 100 and default values of setting values set in the setting items of the smartphone 100. The management database 24 is constructed, for example, on the ROM 103. FIG. 3 is a diagram showing an example of an app usage history management table 241 stored in the management database 24 in the embodiment. The app usage history management table 241 includes items of "app name" and "start time." The name of the started app is stored in "app name." The time when the app is started is stored in "start time." The app usage history management table 241 stores the app name and start time of the started app each time the app is started. The app usage history management table 241 stores, for example, the app name and start time of the apps started during the last 24 hours.

FIG. 4 is a diagram showing an example of the default value management table 242 stored in the management database 24 in the embodiment. The default value management table 242 includes the following items: "major item," "fixed item," "medium item," "diagnosis item," "default value," "executable," and "message." The "major item" stores the name of the app for which the setting value is to be checked and information indicating a malfunction occurring in the smartphone 100. Malfunctions occurring in the smartphone 100 include, for example, battery and charging problems, screen display and character problems, and terminal operation problems. The "fixed item" stores the priority of displaying items to be displayed on the app selection screen 223 (see FIG. 9) to make up for the shortage when the number of items displayed on the app selection screen 223 described later is insufficient compared to the preset number of items to be displayed.

In "medium items", symptoms (faults) that differ from the desired situation are stored. In "diagnosis items", diagnosis items corresponding to major and medium items are stored. In "default values", for example, setting values set at initial settings or setting values recommended for standard usage are stored. That is, in "default values", a setting value determined in advance is stored. In "executable", information (for example, a flag) indicating whether the setting can be changed by the smartphone 100 without the need for user operation is stored. In "message", a message that guides the user on the operation is stored for an item in which information indicating that the setting cannot be changed is stored in "executable". Each piece of information in the default value management table 242 is stored, for example, at the time of shipment of the smartphone 100.

FIG. 5 is a diagram showing an example of a Web information management table 244 stored in the management database 24 in the embodiment. The Web information management table 244 includes, for example, the same items as the default value management table 242. The Web information management table 244 stores information acquired from the server 300 by the Web information acquisition unit 21. The Web information management table 244 is an empty table until information is stored in it by the Web information acquisition unit 21. The example of FIG. 5 illustrates a case in which the Web information acquisition unit 21 acquires from the server 300 defect information such as "video viewing app" as a "major item", "empty (no data)" as a "fixed item", "no sound" as a "medium item", "media volume" as a "diagnosis item", "5 or more" as a "default value", "1" as an "executable" and "empty (no data)" as a "message".

6 is a diagram showing an example of a display item candidate list 243 stored in the management database 24 in the embodiment. The display item candidate list 243 includes an item of "display item candidate". In the "display item candidate", display items determined by the control unit 20 as display item candidates to be displayed on the application selection screen 223 (see FIG. 9) are stored. Examples of information stored as display items include information stored in the "major items" of the default value management table 242 and information stored in the "major items" of the Web information management table 244. In the display item candidate list 243, the display item candidates are arranged in the order in which they were added. The ROM 103 is an example of a "storage unit".

Returning to FIG. 2, the web information acquisition unit 21 acquires information from the server 300. The server 300 registers defect information from the smartphone 100, app vendors, users, and the like. The defect information registered in the server 300 includes the items of "major item", "fixed item", "medium item", "diagnosis item", "default value", "executable", and "message", as exemplified in the default value management table 242, for example. Note that the "fixed item" item may be omitted from the information registered in the server 300. The web information acquisition unit 21 accesses the server 300 and determines whether there is new defect information that is not registered in the default value management table 242. If the web information acquisition unit 21 determines that there is new defect information, it acquires the new defect information from the server 300 and adds the acquired defect information to the web information management table 244. Furthermore, the web information acquisition unit 21 adds information corresponding to the "major item" among the defect information acquired from the server 300 to the display item candidate list 243. The server 300 is an example of an "external server".

The usage history acquisition unit 22 acquires the usage history of apps used by the user. For example, the usage history acquisition unit 22 refers to the app usage history management table 241 to acquire the app that was last (most recently) launched by the user. Next, the usage history acquisition unit 22 refers to the app usage history management table 241 to acquire the launch time of the app and the number of times the app has been launched in the last hour. Next, the usage history acquisition unit 22 refers to the app usage history management table 241 to acquire the launch time of the app and the number of times the app has been launched in the last 24 hours. The usage history acquisition unit 22 adds the app name to the display item candidate list 243 according to the priority order based on the app usage history acquired from the app usage history management table 241.

The terminal information acquisition unit 23 acquires terminal information of the smartphone 100. The terminal information may include the free space of the RAM 102 and the ROM 103. If the free space of the RAM 102 and the ROM 103 is less than a threshold, the terminal information acquisition unit 23 adds this to the display item candidate list 243.

The control unit 20 guides the user to check the usage status of apps on the smartphone 100 and diagnose any malfunctions. In this embodiment, after checking the app usage history, the control unit 20 accepts the user's designation of an app from among the checked apps for which the user wishes to resolve a malfunction, and executes a malfunction diagnosis for the specified app.

FIG. 7 is a diagram showing an example of an app usage history confirmation screen 221 in an embodiment. The app usage history confirmation screen 221 is displayed on the display 113 by the control unit 20. The app usage history confirmation screen 221 includes a confirmation start button 2211 and a progress display 2212. When the confirmation start button 2211 is selected by a touch operation on the touch panel 114, for example, the control unit 20 executes a check of the app usage history.

FIG. 8 is a diagram showing an example of an app usage history checking screen 222 in an embodiment. The app usage history checking screen 222 is displayed on the display 113 by the control unit 20. The control unit 20 causes the app usage history checking screen 222 to be displayed on the display 113 while the app usage history is being checked. While the app usage history checking screen 222 is displayed, the web information acquisition unit 21 acquires defect information, the usage history acquisition unit 22 acquires the app usage history, and the terminal information acquisition unit 23 acquires terminal information. By displaying the app usage history checking screen 222 on the display 113, the control unit 20 can inform the user of the progress of the app usage history check.

FIG. 9 is a diagram showing an example of the application selection screen 223 in an embodiment. The application selection screen 223 is displayed on the display 113 by the control unit 20. When the acquisition of defect information by the web information acquisition unit 21, the acquisition of application usage history by the usage history acquisition unit 22, and the acquisition of terminal information by the terminal information acquisition unit 23 are completed, display items to be displayed on the application selection screen 223 are selected. The selection of display items will be described later with reference to the flowcharts of FIGS. 13 to 15. The application selection screen 223 also includes an Other button 2231. When the Other button 2231 is designated by a touch operation or the like, the control unit 20 may display a screen for selecting other applications not displayed on the application selection screen 223. The application selection screen 223 is an example of a "list".

The control unit 20, which has received the selection of a display item, displays the application selection screen 223 on the display 113. In the example of FIG. 9, "Top of the screen is glowing", "SNS application", "Phone application", "Email application", and "Internet" are displayed as display items. In the example of FIG. 9, "Top of the screen is glowing" is malfunction information acquired by the Web information acquisition unit 21, and "Phone application trouble", "Email application trouble", and "Internet trouble" are display items selected based on the application usage history acquired by the usage history acquisition unit 22. Each display item displayed on the application selection screen 223 illustrated in FIG. 9 is, for example, information stored in a "major item" of the default value management table 242.

The control unit 20 accepts the designation of any display item on the application selection screen 223. When any display item is designated, the control unit 20 causes the application selection screen 223 to display a "medium item" that is associated with the designated display item in the default value management table 242.

Fig. 10 is a diagram showing an example of an app selection screen 223 on which "middle items" are displayed in an embodiment. Fig. 10 shows an example in which "SNS app" is specified. When "SNS app" is specified on the app selection screen 223, the control unit 20 acquires a "middle item" corresponding to the "SNS app" in the default value management table 242. The control unit 20 displays the acquired "middle item" below the "SNS app" on the app selection screen 223 (between "SNS app" and "Phone app" displayed below "SNS app").

When any of the "medium items" is specified on the application selection screen 223 illustrated in FIG. 10, the control unit 20 executes a diagnosis of the "diagnosis item" corresponding to the specified "medium item" in the default value management table 242.

Figure 11 is a diagram showing an example of a diagnosis screen 224 in an embodiment. The diagnosis screen 224 is displayed on the display 113 by the control unit 20. In the diagnosis, it is determined whether the setting value set for the "diagnosis item" is the "default value" in the default value management table 242. Then, for any "diagnosis item" that is not set to the default value, the control unit 20 changes the setting value to the default value.

In the example of FIG. 11, the "diagnosis items" displayed are "Check and change airplane mode settings," "Check and change mobile data settings," "Check SIM insertion," and "Check whether the device is in or out of communication range." A completion mark 2241 is added to diagnosis items for which the settings have been checked and changed as necessary. A progress mark 2242 is added to diagnosis items that are currently being diagnosed. By displaying this type of diagnosis screen 224, the control unit 20 can notify the user of the progress of the diagnosis.

12 is a diagram showing an example of a result display screen 225 in an embodiment. After completing the diagnosis, the control unit 20 causes the display 113 to display the result display screen 225. The result display screen 225 displays the setting items whose settings have been changed by the diagnosis and the setting values of the setting items. Furthermore, for setting items that are set as not executable in the "executable" field of the default value management table 242, the result display screen 225 displays the message stored in the "message" field of the default value management table 242 in association with the setting item.

In the example of FIG. 12, for example, it can be seen that the setting item "Airplane mode settings" has been changed to "Off." In addition, it can be seen that the setting item "Mobile data settings" is set to "On," which is the default value (settings have not been changed). A completion mark 2252 is added to setting items whose settings have been changed, such as the setting item "Airplane mode settings," and setting items that have already been set to the default value, such as "Mobile data settings."

For setting items that are set as "unexecutable" in the default value management table 242, a warning mark 2253 is added, such as "SIM insertion" and "In/Out of communication range". By adding the warning mark 2253 to the setting items on the result display screen 225, the control unit 20 can show the user the setting items that require user operation. The result display screen 225 also includes an end button 2251. When the end button 2251 is selected by the user's touch operation or the like, the control unit 20 ends the diagnosis.

<Processing flow of the smartphone 100>
Fig. 13 is a diagram showing an example of a processing flow of the smartphone 100 according to the embodiment. Hereinafter, an example of a processing flow of the smartphone 100 will be described with reference to Fig. 13 .

At T1, the usage status of the smartphone 100 is acquired. The control unit 20 causes the display 113 to display the application usage history confirmation screen 221. When the confirmation start button 2211 on the application usage history confirmation screen 221 is selected, the control unit 20 causes the display 113 to display the application usage history confirmation screen 222, and acquires the usage status. The control unit 20 causes the display 113 to display the application selection screen 223 including display items selected according to the acquired usage status. Details of the processing of T1 will be described later with reference to FIG. 14.

At T2, a major item is specified. The control unit 20 causes the display 113 to display the application selection screen 223. When one of the setting items displayed on the application selection screen 223 is specified, the control unit 20 causes the application selection screen 223 to display the medium items included in the specified major item.

At T3, a medium item is specified. The control unit 20 accepts the specification of one of the medium items displayed on the application selection screen 223.

At T4, the diagnosis is performed. The control unit 20 performing the diagnosis shows the user the diagnosis status for the medium items specified at T3 by displaying the diagnosis screen 224 on the display 113. During the diagnosis, for items that are "executable" in the default value management table 242 and can be changed by the smartphone 100 without requiring user operation, the setting value is changed to the default value without confirmation from the user. When the diagnosis is completed, the control unit 20 notifies the user of the diagnosis result by displaying the result display screen 225 on the display 113.

Figure 14 is a diagram showing an example of the processing flow of T1 in Figure 13. Below, an example of the processing flow of T1 in Figure 13 will be described with reference to Figure 14.

In T11, the Web information acquisition unit 21 determines whether or not defect information that is not stored in the default value management table 242 is registered in the server 300. If the defect information is registered (YES in T11), the process proceeds to T16. If the defect information is not registered (NO in T11), the process proceeds to T12.

At T12, the terminal information acquisition unit 23 acquires the free space of the RAM 102 of the smartphone 100. If the free space of the RAM 102 is equal to or greater than the threshold (YES at T12), the process proceeds to T17. If the free space of the RAM 102 is less than the threshold (NO at T12), the process proceeds to T13.

At T13, the terminal information acquisition unit 23 acquires the free space in the ROM 103 of the smartphone 100. If the free space in the ROM 103 is equal to or greater than the threshold (YES at T13), the process proceeds to T18. If the free space in the ROM 103 is less than the threshold (NO at T13), the process proceeds to T14.

At T14, the usage history acquisition unit 22 determines whether the usage period of the smartphone 100 (e.g., the time elapsed since the smartphone 100 was turned on) is equal to or greater than a threshold. If the usage period of the smartphone 100 is equal to or greater than the threshold (YES at T14), the process proceeds to T15. If the usage period of the smartphone 100 is less than the threshold (NO at T14), the process proceeds to T19.

At T15, the usage history acquisition unit 22 refers to the application usage history management table 241 to acquire the usage status of the application. The usage history acquisition unit 22 adds the application selected according to the usage status of the application to the display item candidate list 243. Details of the process of T15 will be described later with reference to FIG. 15.

At T16, the web information acquisition unit 21 acquires defect information that is not stored in the default value management table 242 from the server 300. The web information acquisition unit 21 stores the acquired defect information in the web information management table 244. In addition, the web information acquisition unit 21 adds information corresponding to the "major items" among the defect information acquired from the server 300 to the display item candidate list 243.

At T17, the control unit 20 adds the medium-sized item associated with the large-sized item "lack of free memory (RAM)" in the default value management table 242 to the display item candidate list 243. In this example, it is assumed that "Device is running slowly" is added to the display item candidate list 243.

At T18, the control unit 20 adds the medium-sized item associated with the large-sized item "lack of free memory (ROM)" in the default value management table 242 to the display item candidate list 243. In this case, it is assumed that "lack of storage" is added to the display item candidate list 243.

At T19, the control unit 20 causes the display 113 to display the application selection screen 223 including the display items added to the display item candidate list 243 at T15, T16, T17, and T18. Note that, if the number of display item candidates added to the display item candidate list 243 is equal to or greater than a predetermined threshold (e.g., 4), the control unit 20 causes the application selection screen 223 to display the number of display item candidates added to the display item candidate list 243 from the top to the threshold.

Figure 15 is a diagram showing an example of the processing flow of T15 in Figure 14. Below, an example of the processing flow of T15 in Figure 14 is described with reference to Figure 15.

At T151, the usage history acquisition unit 22 refers to the application usage history management table 241 and identifies the application that was launched last among the applications stored in the “major items” of the default value management table 242. The usage history acquisition unit 22 adds the identified application to the display item candidate list 243.

At T152, the usage history acquisition unit 22 refers to the app usage history management table 241 and identifies apps that have been launched within the past hour from among the apps stored in the "major items" of the default value management table 242. The usage history acquisition unit 22 refers to the app usage history management table 241 and acquires the number of times the identified app has been launched within the past hour from the current time. The usage history acquisition unit 22 adds apps to the display item candidate list 243 in descending order of the number of times they have been launched within the past hour from the current time.

At T153, the usage history acquisition unit 22 refers to the app usage history management table 241 and identifies apps that have been launched within the past 24 hours from among the apps stored in the "major items" of the default value management table 242. The usage history acquisition unit 22 refers to the app usage history management table 241 and acquires the number of times the identified app has been launched within the past 24 hours from the current time. The usage history acquisition unit 22 adds apps to the display item candidate list 243 in descending order of the number of times they have been launched within the past 24 hours from the current time.

<Effects of the embodiment>
In this embodiment, the application to be diagnosed is presented to the user as in the application selection screen 223, and the application specified by the user is diagnosed. In the diagnosis, as described in T4 of Fig. 13, for items in the default value management table 242 that are set as "executable" without user operation and that can be changed by the smartphone 100, the default value management table 242 is referenced and the setting value is changed to the default value without confirmation from the user. Therefore, according to this embodiment, a defect can be corrected without user operation, and thus the user is not bothered.

In addition, in this embodiment, a list of apps that the user has used most recently is displayed on the app selection screen 223, and the user can select the app for which the malfunction is to be resolved from the apps displayed on the app selection screen 223, so that even a user who is unfamiliar with information technology can easily resolve the malfunction.

As described above, in this embodiment, a diagnosis is performed on an app specified by the user. Therefore, compared to a technique in which the user is asked to specify which malfunctions to resolve after first diagnosing malfunctions on the entire mobile device, the processing load on the smartphone 100 caused by malfunction resolution can be reduced and the desired malfunction can be resolved in a shorter time.

<First Modification>
The above-described embodiment can be modified in various ways. For example, in the embodiment, when a "medium item" such as "cannot connect to SNS" or "no notification sound" is selected on the application selection screen 223, a transition to a diagnosis screen 224 is made and diagnosis is started. However, as in the diagnosis screen 224a illustrated in FIG. 16, a diagnosis start button 2243 may be provided and diagnosis may be started after the diagnosis start button 2243 is specified. By adopting such a configuration, it is possible to present the items to be diagnosed to the user and start diagnosis after obtaining the user's consent.

<Second Modification>
Even if the setting value is set to the default value, the user may not be able to resolve the problem. In such a case, a method for resolving the problem may be stored in advance in a "message" in the default value management table 242, and the user may be informed of the message. FIG. 17 is a diagram showing an example of a result display screen 225 informing the user that there is no problem with the settings in the second modified example. When the diagnosis result display field 2254 is specified in the result display screen 225 exemplified in FIG. 17, the control unit 20 may display a "message" associated with the item displayed in the diagnosis result display field 2254 in the default value management table 242 in the resolution method guidance field 2255, as exemplified in FIG. 18. In this case, if the message is a message prompting a restart, the control unit 20 may display a restart button 2256 together with the message for the user's convenience.

The embodiments and variations disclosed above can be combined with each other.

<Computer-readable recording medium>
An information processing program that causes a computer or other machine or device (hereinafter, referred to as a computer, etc.) to realize any of the above functions can be recorded on a recording medium that can be read by the computer, etc. Then, the computer, etc. can provide the function by reading and executing the program from the recording medium.

Here, a computer-readable recording medium refers to a recording medium that stores information such as data and programs electrically, magnetically, optically, mechanically, or chemically and can be read by a computer. Examples of such recording media that can be removed from a computer include flexible disks, magneto-optical disks, Compact Disc Read Only Memory (CD-ROM), Compact Disc-Recordable (CD-R), Compact Disc-ReWritable (CD-RW), Digital Versatile Disc (DVD), Blu-ray Disc (BD), Digital Audio Tape (DAT), 8mm tape, and memory cards such as flash memory. Additionally, examples of recording media that are fixed to a computer include hard disks and ROMs.

100: Smartphone 101: CPU
102...RAM
103...ROM
DESCRIPTION OF SYMBOLS 104: Communication unit 110: Housing 111: Speaker 112: Microphone 113: Display 114: Touch panel 20: Control unit 21: Web information acquisition unit 22: Usage history acquisition unit 23: Terminal information acquisition unit 24: Management database 221: Application usage history confirmation screen 222: Application usage history confirmation screen 223: Application selection screen 224: Diagnosis screen 224a: Diagnosis screen 225: Result display screen 241: Application usage history management table 242: Default value management table 243: Display item candidate list 244: Web information management table 300: Server 2211: Confirmation start button 2212: Progress display 2213: Cancel button 2231: Other buttons 2241: Completion mark 2242: Progress mark 2243: Diagnosis start button 2251: End button 2252: Completion mark 2253: Caution mark 2254: Diagnosis result display field 2255: Solution method guide field 2256: Restart button B1: Connection bus N1: Network

Claims (6)

a storage unit that stores a correspondence relationship between an installed application program and a default value of a setting value that is set in the application program;
A control unit,
The control unit is
displaying a list of application programs selected based on the usage history of the application programs;
Accepting a designation of a first application program from the list;
when a setting value set in the first application program is different from a first default value associated with the first application program in the storage unit, changing the setting value of the first application program to the first default value;
Mobile device. the control unit causes the application program that was last launched to be displayed on the list with priority.
The mobile terminal according to claim 1 . the control unit causes application programs which have been started up frequently to be displayed in the list with priority.
The mobile terminal according to claim 1 . when the control unit acquires, from an external server, a correspondence relationship that is not stored in the storage unit, the control unit causes the application program associated in the correspondence relationship acquired from the external server to be preferentially displayed in the list.
The mobile terminal according to claim 1 . An information processing device including a storage unit that stores a correspondence relationship between an installed application program and a default value of a setting value set in the application program,
displaying a list of application programs selected based on the usage history of the application programs;
accepting a designation of a first application program from the list;
and when a setting value set in the first application program is different from a first default value associated with the first application program in the storage unit, executing a process of changing the setting value of the first application program to the first default value.
Information processing methods. An information processing apparatus including a storage unit that stores a correspondence relationship between an installed application program and a default value of a setting value set in the application program,
displaying a list of application programs selected based on the usage history of the application programs;
accepting a designation of a first application program from the list;
and when a setting value set in the first application program is different from a first default value associated with the first application program in the storage unit, executing a process of changing the setting value of the first application program to the first default value.
Information processing methods.