The problem of eradicating contacts designated as “read-only” on an Android machine stems from their supply. These contacts are sometimes synchronized from exterior accounts similar to Google, Microsoft Change, or social media platforms. The Android working system typically prevents direct modification or deletion of contacts managed by these accounts instantly by the native contacts software. Understanding the supply of those contacts is step one in direction of managing them. As an illustration, a contact synced from a company Change account would possibly seem read-only inside the private contacts app on the machine.
Successfully managing these entries is essential for sustaining information privateness, decluttering contact lists, and making certain environment friendly communication. Traditionally, customers encountering this challenge had restricted choices and sometimes resorted to disabling contact synchronization altogether, which was not at all times a fascinating answer. Fashionable approaches supply extra granular management, permitting customers to selectively take away or modify particular contacts with out affecting the complete synchronization course of. Streamlining the contact checklist improves search performance and reduces the potential for by accident contacting the mistaken particular person.
The following sections will discover varied strategies for addressing the read-only contact dilemma on Android gadgets. This can embody accessing account settings, using third-party purposes, and using particular strategies for managing contacts originating from completely different sources, providing an in depth information to regaining management over one’s contact checklist.
1. Account Synchronization
Account synchronization is the foundational course of figuring out the presence and immutability of contacts on an Android machine. Contacts designated as read-only are sometimes synchronized from exterior accounts, similar to Google, Microsoft Change, or social media platforms. The Android working system, by design, restricts direct modification or deletion of those contacts by the native contacts software as a result of the authoritative supply resides with the exterior account. As an illustration, if a contact originates from a Google Workspace account linked to the machine, any try and delete it instantly inside the Android contacts app will seemingly fail, because the working system acknowledges Google’s server as the first repository for that data. Understanding this hierarchical relationship is paramount in addressing the right way to successfully take away such contacts.
The significance of account synchronization lies in its function in sustaining information consistency throughout a number of gadgets and platforms. When a change is made on the supply account, similar to deleting a contact from the Google Contacts net interface, that change propagates to all synchronized gadgets, together with the Android telephone. Conversely, the Android system prevents native modifications from overriding the information held by the supply account to stop inconsistencies. This mechanism is important for enterprise environments, the place contact data should stay uniform throughout all workers’ gadgets. Nonetheless, it additionally presents a problem for particular person customers who want to customise their native contact checklist with out affecting the grasp copy held by the exterior account.
In conclusion, account synchronization is the principal determinant of whether or not a contact might be instantly deleted from an Android machine. The read-only designation serves as a protecting measure to stop information corruption and preserve consistency throughout platforms. To successfully take away these contacts, one should sometimes entry the supply account from which the contact is being synchronized and provoke the deletion course of there. Whereas various strategies, similar to disabling contact synchronization or utilizing third-party purposes, exist, they typically symbolize workarounds relatively than direct options. Subsequently, understanding the synchronization mechanism is the primary and most important step in mastering contact administration on Android.
2. Contact Supply Identification
Contact supply identification represents a crucial prerequisite to deleting read-only contacts on Android gadgets. The lack to instantly take away such entries from the native contacts software underscores the significance of figuring out the origin of the contact information. Learn-only contacts sometimes originate from synchronized accounts, together with Google, Change, or varied social media platforms. The Android working system restricts direct modification of those contacts as a result of the authoritative supply is maintained by the exterior account. With out precisely figuring out the contact’s supply, any try at deletion will seemingly show futile. For instance, trying to delete a contact synchronized from a company Change server by the Android contact software will fail as a result of the Change server retains management over the contact’s information. Conversely, accurately figuring out the supply permits focused intervention, similar to deleting the contact instantly from the Change server, which subsequently synchronizes the deletion to the Android machine.
The sensible significance of figuring out the contact supply extends past easy deletion. Understanding the origin informs the consumer about account permissions and potential restrictions. Company Change accounts, for example, typically impose stricter controls than private Google accounts. This understanding permits the consumer to anticipate potential challenges and choose the suitable methodology for elimination. Moreover, correct identification prevents unintended information loss. Deleting a contact instantly from the supply account will take away it from all synchronized gadgets. Subsequently, confirming the supply ensures the consumer is deleting the contact from the supposed location and avoids inadvertently dropping entry to crucial data throughout a number of platforms.
In abstract, contact supply identification is key to efficiently deleting read-only contacts on Android gadgets. The flexibility to pinpoint the origin of the contact information permits focused motion, knowledgeable decision-making, and the prevention of unintended information loss. Whereas Android gives varied strategies for managing contacts, together with disabling synchronization and using third-party purposes, these approaches are contingent upon precisely figuring out the contact’s supply. With out this understanding, the consumer is prone to encounter continued frustration and ineffective makes an attempt at contact elimination.
3. Account Permissions
Account permissions are central to the power to delete read-only contacts on Android gadgets. The working system’s contact administration protocols adhere strictly to the permissions granted to numerous accounts synchronized with the machine. These permissions dictate whether or not modifications, together with deletion, are allowed instantly from the Android interface or require intervention on the supply account stage. Understanding these permissions is paramount for efficient contact administration.
-
Write Entry Restrictions
Sure accounts, significantly these managed by company entities or older methods, might grant solely learn entry to contact information. This restriction prevents modifications to the contact checklist from the Android machine. The underlying rationale is to take care of information integrity and implement uniformity throughout the group. For instance, a company Change account would possibly synchronize contact data to an worker’s telephone however disallow native adjustments. Consequently, deleting a contact would necessitate accessing and modifying the contact checklist instantly inside the Change setting.
-
Synchronization Protocols and Override Capabilities
The synchronization protocol employed by an account influences the diploma to which native actions can override server-side information. Fashionable protocols typically prioritize server-side information, which means that any adjustments made on the Android machine are momentary till the following synchronization. If the account lacks the suitable write permissions, these adjustments will probably be reverted. Social media accounts, for example, sometimes synchronize contacts to the machine however stop native deletions from completely eradicating the contact from the consumer’s social community.
-
Person-Granted Permissions
In the course of the preliminary setup of an account on an Android machine, the consumer is usually prompted to grant varied permissions, together with contact entry. Whereas sometimes permitting learn entry, write entry shouldn’t be at all times explicitly requested or granted. If the consumer has not granted the account write entry to contacts, the Android system will deal with the contacts as read-only, stopping deletion. Revisiting the account settings and verifying the granted permissions is essential in troubleshooting deletion points. This course of can contain navigating to the machine’s settings menu, deciding on the account, and inspecting the particular permissions related to contact entry.
-
Account Kind and Administration Insurance policies
The kind of account, whether or not it’s a private Google account or a company Change account, considerably impacts the obtainable permissions and administration insurance policies. Company accounts typically have administrator-defined insurance policies that prohibit consumer actions on synchronized information. These insurance policies are designed to make sure compliance and information safety. Consequently, deleting a read-only contact from a company account might require contacting the IT division for help or modifying the contact checklist inside the designated company setting.
In conclusion, the power to delete read-only contacts on an Android machine is inextricably linked to the account permissions governing contact information. Understanding the write entry restrictions, synchronization protocols, user-granted permissions, and account-specific administration insurance policies is important for successfully managing and eradicating contacts. With out acceptable permissions, makes an attempt to delete contacts instantly from the Android interface will probably be unsuccessful, necessitating intervention on the supply account stage or various administration methods.
4. Disabling Contact Sync
Disabling contact synchronization represents a blunt, but efficient, methodology of addressing the persistent presence of read-only contacts on Android gadgets. Whereas not a selective deletion instrument, it severs the connection between the machine and the exterior account, successfully eradicating the synchronized contacts from view. The implications of this motion lengthen past mere contact elimination, affecting the consumer’s entry to up to date contact data and doubtlessly disrupting different synchronized companies.
-
Full Contact Elimination
Disabling contact synchronization instantly removes all contacts related to the required account from the machine’s contact checklist. This motion ensures that the read-only contacts, which resist particular person deletion, are not seen or accessible. The elimination is full, affecting all contacts linked to the disabled account, no matter whether or not they’re read-only or modifiable. For instance, disabling Google contact sync would get rid of all Google contacts from the Android telephone’s contact software.
-
Lack of Contact Updates
The first downside of disabling synchronization is the cessation of contact updates from the supply account. Any adjustments made to contacts on the exterior account, similar to new numbers, deal with updates, or profile image modifications, is not going to be mirrored on the Android machine. This creates a divergence between the machine’s contact checklist and the authoritative supply, doubtlessly resulting in outdated or inaccurate data. Contemplate a situation the place a contact adjustments their telephone quantity on a linked Change account; this variation is not going to propagate to the Android machine if synchronization is disabled.
-
Affect on Different Synchronized Providers
Disabling contact synchronization might inadvertently have an effect on different companies that depend on contact information. Some purposes use the Android contact checklist to establish customers or facilitate communication. For instance, disabling synchronization with a social media platform might stop the consumer from figuring out contacts inside that platform primarily based on their telephone numbers saved within the Android contact checklist. This interconnectedness necessitates cautious consideration earlier than disabling synchronization, as the implications can lengthen past the fast elimination of read-only contacts.
-
Re-enabling Synchronization and Potential Penalties
Re-enabling contact synchronization after a interval of disablement will restore the contacts to the Android machine. Nonetheless, any adjustments made to the contact checklist whereas synchronization was disabled will probably be overwritten by the information from the supply account. This habits can result in the lack of domestically added or modified contacts in the event that they battle with entries on the exterior account. The consumer ought to pay attention to this potential consequence and take acceptable measures, similar to backing up native contacts, earlier than re-enabling synchronization.
Disabling contact synchronization gives a definitive methodology for eradicating read-only contacts from an Android machine. Nonetheless, the motion carries important implications, together with the lack of contact updates and potential disruptions to different synchronized companies. The consumer should weigh these penalties towards the frustration of managing undeletable contacts earlier than continuing with this strategy. The choice needs to be knowledgeable by a transparent understanding of the trade-offs concerned and a cautious evaluation of the consumer’s particular wants and priorities.
5. Third-Get together Functions
Third-party purposes supply an alternate pathway for managing and doubtlessly deleting read-only contacts on Android gadgets, a job typically restricted by the working system’s native contact administration instruments. These purposes function by circumventing the usual Android contact protocols or offering superior options not obtainable within the default contacts software. The efficacy of those purposes is dependent upon their design, entry permissions, and compatibility with the machine’s working system. As an illustration, some purposes concentrate on figuring out and merging duplicate contacts, which can not directly deal with the problem of read-only entries by consolidating information from a number of sources right into a single, modifiable contact. Nonetheless, it’s essential to acknowledge that these purposes don’t inherently bypass the basic restrictions imposed by synchronized accounts; relatively, they provide supplementary instruments which will assist in streamlining contact lists.
The utility of third-party contact administration purposes is demonstrated in situations the place customers have quite a few contacts synchronized from varied sources, leading to a cluttered and difficult-to-manage contact checklist. These purposes might present options similar to batch enhancing, superior filtering, and the power to establish incomplete or outdated contact data. Whereas they can’t instantly delete read-only contacts originating from, say, a company Change account with out correct permissions, they will help in decluttering the contact checklist by hiding or archiving these entries, thereby bettering the consumer expertise. Moreover, sure purposes supply options that counsel various contact strategies, similar to initiating a name or message by a unique software, which might be helpful when coping with contacts whose data is incomplete or outdated. The sensible software of those instruments lies in augmenting the consumer’s management over their contact information, even when direct deletion shouldn’t be attainable.
In conclusion, whereas third-party purposes current an alternate strategy to managing contacts, together with these designated as read-only, their effectiveness is proscribed by the underlying restrictions imposed by synchronized accounts and account permissions. These purposes function supplementary instruments that may improve contact administration by providing superior options and improved group. Nonetheless, they shouldn’t be seen as a direct answer for deleting read-only contacts with out correct authorization or entry to the supply account. The challenges related to read-only contacts stay, and third-party purposes present a method to mitigate these challenges by enhanced group and administration capabilities, in the end contributing to a extra streamlined contact expertise on Android gadgets.
6. Internet Interface Administration
Internet interface administration gives a direct answer to the problem of deleting read-only contacts on Android gadgets. These contacts, sometimes synchronized from exterior accounts like Google or Microsoft Change, resist deletion by way of the telephone’s native contact software because of permission restrictions. The basis of the information, and consequently the locus of management, resides inside the supply account accessible by an online browser. Subsequently, accessing and modifying the contact checklist by the net interface of the originating service is usually the one methodology to completely take away such entries. For instance, a contact synced from a Google account and designated as read-only on an Android machine might be deleted by logging into Google Contacts by way of an online browser and eradicating the contact from there. This motion synchronizes the change again to the Android machine, successfully deleting the contact.
The sensible significance of understanding this lies in circumventing the constraints imposed by the Android working system on synchronized information. Direct manipulation of read-only contacts by way of the telephone’s interface is often prohibited to take care of information integrity throughout platforms. Internet interface administration permits the consumer to train management on the supply, making certain adjustments are mirrored on all gadgets linked to the account. The consequence of ignoring this strategy is sustained frustration in managing contact lists, leading to cluttered and inaccurate contact data on the Android machine. Company environments typically mandate this methodology for modifying worker contact particulars, as native adjustments on the machine could be overridden by the centrally managed contact checklist on the Change server. Failing to handle contacts by the net interface, in such a situation, ends in persistent inaccuracies and inefficiencies in communication.
In abstract, net interface administration is a crucial element of deleting read-only contacts on Android. It represents the authoritative methodology for modifying contact information synchronized from exterior accounts, bypassing the restrictions imposed by the native Android contact software. The effectiveness of this strategy hinges on the consumer’s understanding of the supply account and their capacity to navigate the corresponding net interface. Whereas various strategies exist, they typically supply momentary options or restricted management. Finally, for everlasting deletion, accessing and managing contacts by the net interface of the originating service stays probably the most dependable plan of action.
7. Root Entry (Superior)
Root entry, within the context of Android working methods, represents a complicated approach that grants customers privileged management over the machine’s software program. Whereas sometimes pointless for routine duties, it turns into related when addressing deeply embedded system limitations, similar to the lack to delete read-only contacts. Rooting a tool circumvents normal Android safety protocols, providing the potential to change system recordsdata and override restrictions imposed by the producer or account synchronization.
-
System Partition Modification
Root entry permits modification of the system partition, the place core working system recordsdata reside. Learn-only contacts typically persist because of synchronization protocols that stop adjustments to system-level contact databases. With root entry, it turns into attainable to instantly edit these databases, bypassing the supposed restrictions and facilitating the deletion of in any other case undeletable contact entries. This course of, nonetheless, carries important threat, as incorrect modifications can render the machine inoperable.
-
Third-Get together Software Utilization
Rooted gadgets can leverage specialised third-party purposes designed to handle system-level settings and recordsdata. These purposes might supply superior contact administration options not obtainable on non-rooted gadgets, together with the power to force-delete read-only contacts. These purposes work together instantly with the system recordsdata, bypassing the usual Android API restrictions. The consumer assumes duty for vetting the security and reliability of those purposes, as they function with elevated privileges.
-
Bypassing Account Synchronization
Root entry permits the consumer to successfully bypass account synchronization restrictions that sometimes stop the deletion of read-only contacts. By instantly modifying the contact database, the consumer can override the synchronization protocols, deleting the contact domestically even when the supply account makes an attempt to revive it. This strategy severs the connection between the native contact checklist and the exterior account, doubtlessly disrupting the supposed performance of the synchronization course of.
-
Safety Implications and Dangers
Acquiring root entry inherently weakens the machine’s safety posture. Rooting voids the producer’s guarantee in lots of instances and exposes the machine to elevated threat of malware and unauthorized entry. The elevated privileges granted by root entry might be exploited by malicious purposes, doubtlessly compromising delicate information or rendering the machine unusable. Subsequently, the choice to root a tool needs to be made with cautious consideration of the related dangers and advantages.
In abstract, whereas root entry gives a technical pathway to deleting read-only contacts on Android gadgets, it’s a complicated approach with important dangers. It grants privileged management over the system, permitting modification of contact databases and circumvention of synchronization restrictions. Nonetheless, the potential safety implications and the danger of rendering the machine inoperable necessitate warning and an intensive understanding of the method earlier than continuing. The consumer should weigh the advantages of deleting read-only contacts towards the inherent dangers of modifying the core working system.
8. Contact App Settings
The configuration choices inside the Android contact software instantly affect the administration, visibility, and modifiability of contact entries. Whereas not at all times a direct answer to deleting read-only contacts, these settings present avenues for filtering, displaying, and sometimes manipulating synchronized contact information. Understanding these settings is essential for navigating the complexities of contact administration, significantly when coping with entries resistant to straightforward deletion strategies.
-
Contact Filtering and Account Visibility
Contact purposes sometimes permit filtering contacts primarily based on the account from which they originate. Settings might embody choices to show contacts from all accounts, particular accounts, or native storage solely. Whereas filtering doesn’t delete read-only contacts, it supplies a method to briefly exclude them from view, decluttering the contact checklist. As an illustration, one would possibly select to show solely contacts saved domestically, successfully hiding contacts synchronized from a company Change account. This strategy doesn’t take away the contacts however relatively manages their visibility inside the software.
-
Show Choices and Sorting Preferences
Contact software settings typically embody customization choices for the way contacts are displayed, similar to title format (first title first or final title first), contact sorting preferences (alphabetical by first title or final title), and show order. Though these settings don’t have an effect on the modifiability of contacts, they contribute to the general consumer expertise by organizing the contact checklist in a logical and accessible method. In conditions the place read-only contacts are intermixed with modifiable entries, these show choices grow to be particularly helpful for navigating the contact checklist effectively.
-
Storage Location Administration
Some contact purposes supply choices for managing the default storage location for brand new contacts. This setting determines whether or not new contacts are saved domestically on the machine or related to a synchronized account. Whereas it doesn’t instantly impression current read-only contacts, setting the default storage location to native storage ensures that newly created contacts aren’t topic to synchronization restrictions, permitting for simpler modification and deletion sooner or later. It is a preventative measure to keep away from the creation of extra read-only entries.
-
Contact Becoming a member of and Duplicate Administration
Android contact purposes typically try and mechanically be a part of duplicate contacts from varied sources right into a single entry. Settings might embody choices for manually becoming a member of contacts or resolving conflicts. In instances the place a read-only contact is a replica of a modifiable contact, becoming a member of the 2 entries would possibly present a workaround for managing the knowledge. Nonetheless, it’s important to notice that the read-only attributes of the unique contact will seemingly persist, doubtlessly limiting the extent to which the joined contact might be modified.
In abstract, whereas contact software settings don’t present a direct answer for deleting read-only contacts, they provide beneficial instruments for managing contact visibility, group, and storage. By leveraging filtering, show choices, storage location administration, and duplicate decision options, customers can mitigate the challenges related to read-only entries and optimize their total contact administration expertise. These settings, at the side of different strategies similar to net interface administration and account synchronization changes, contribute to a complete strategy to dealing with read-only contacts on Android gadgets.
9. Short-term Contact Deletion
Short-term contact deletion, within the context of managing read-only contacts on Android gadgets, addresses the fast have to take away a contact from view with out affecting the underlying synchronization protocols. This system sometimes entails clearing the contact software’s cache and information or using software settings to filter contact visibility. The motion doesn’t completely delete the read-only contact from the synchronized account, however as an alternative, it removes the native copy saved on the machine. Because of this, the contact disappears from the consumer’s contact checklist till the following synchronization cycle, at which level the contact reappears, negating the momentary deletion.
This strategy is helpful in situations the place a consumer requires fast decluttering of their contact checklist with out the authority or need to completely delete the contact from the supply account. For instance, a consumer might need a contact from a earlier job synchronized by a company account. The contact is not related, however the consumer lacks the permissions to delete it from the corporate’s Change server. Clearing the contact software’s information will briefly take away the entry, offering a cleaner contact checklist. Nonetheless, upon the following synchronization with the Change server, the contact will reappear. The sensible significance of this methodology lies in its reversibility and non-destructive nature, making it a low-risk possibility for managing contact muddle.
In conclusion, momentary contact deletion serves as a palliative measure relatively than a definitive answer for managing read-only contacts on Android. It gives a short-term repair for decluttering contact lists however doesn’t deal with the underlying challenge of synchronization with exterior accounts. The important thing problem lies in understanding the momentary nature of the deletion and the necessity for various long-term options, similar to net interface administration or account permission changes, to completely take away undesirable read-only contacts.
Continuously Requested Questions
This part addresses frequent queries relating to the elimination of read-only contacts from Android gadgets, offering concise and informative solutions.
Query 1: Why are some contacts on an Android machine designated as read-only?
Contacts designated as read-only sometimes originate from synchronized exterior accounts, similar to Google, Microsoft Change, or social media platforms. The Android working system prevents direct modification to take care of information consistency with the supply account.
Query 2: Is it attainable to completely delete a read-only contact instantly from the Android contact software?
Direct deletion of read-only contacts from the Android contact software is mostly not attainable because of the aforementioned synchronization protocols. The first methodology entails accessing and modifying the contact checklist by the net interface of the originating service.
Query 3: What various strategies exist for managing read-only contacts if direct deletion shouldn’t be possible?
Different strategies embody disabling contact synchronization for the related account, using third-party contact administration purposes to filter or conceal contacts, or clearing the contact software’s cache and information for momentary elimination.
Query 4: How does disabling contact synchronization have an effect on different companies on the Android machine?
Disabling contact synchronization removes all contacts related to the required account and prevents future updates. This motion would possibly have an effect on different purposes that depend on the Android contact checklist for identification or communication.
Query 5: What dangers are related to gaining root entry to change system recordsdata for contact deletion?
Root entry voids the machine’s guarantee and exposes it to elevated safety dangers, together with malware and unauthorized entry. Incorrect modification of system recordsdata can render the machine inoperable.
Query 6: Is there a strategy to stop contacts from being designated as read-only sooner or later?
Stopping the read-only designation entails rigorously managing account synchronization settings and permissions. Storing new contacts domestically on the machine relatively than associating them with a synchronized account permits for larger management over their modification.
Understanding the supply of read-only contacts and the constraints imposed by account synchronization is essential for efficient contact administration on Android gadgets. Whereas direct deletion is usually not attainable, various strategies and preventive measures can mitigate the challenges related to these entries.
The following part will deal with superior troubleshooting strategies for significantly persistent read-only contact points.
Ideas for Managing Learn-Solely Contacts on Android
This part supplies sensible ideas for navigating the complexities of managing read-only contacts on Android gadgets. The following tips deal with optimizing contact administration methods inside the limitations imposed by synchronization protocols and account permissions.
Tip 1: Prioritize Internet Interface Administration: Entry the supply account (e.g., Google Contacts, Change Server) by an online browser to change or delete contacts. Adjustments made on the supply are synchronized to the Android machine, making certain a everlasting elimination.
Tip 2: Confirm Account Permissions: Look at the permissions granted to every synchronized account inside the Android machine settings. Be sure that contact entry is appropriately configured to stop unintended read-only designations.
Tip 3: Strategically Disable Contact Synchronization: If sure accounts contribute primarily undesirable read-only contacts, take into account disabling contact synchronization for these accounts. This removes the contacts from the machine however requires consciousness of the potential impression on different companies reliant on that account’s contact information.
Tip 4: Make the most of Contact Filtering: Make use of the contact software’s filtering choices to cover read-only contacts from particular accounts. This declutters the contact checklist with out completely deleting the entries.
Tip 5: Frequently Clear Contact Software Information: Periodically clear the contact software’s cache and information to take away domestically saved copies of read-only contacts. Word that this can be a momentary answer, because the contacts will reappear upon the following synchronization.
Tip 6: Export and Evaluation Contact Lists: Export contact lists from synchronized accounts to a pc for evaluation. This facilitates figuring out and deleting out of date or undesirable contacts instantly on the supply.
Tip 7: Consolidate Contact Info: The place attainable, consolidate contact data from a number of sources right into a single, modifiable entry. This reduces redundancy and simplifies contact administration.
The following tips supply a sensible framework for managing read-only contacts on Android gadgets. By understanding the constraints of direct deletion and leveraging various methods, customers can optimize their contact lists for improved effectivity and accuracy.
The next part will conclude this text with a abstract of key takeaways and proposals for continued contact administration.
Conclusion
The strategies by which to delete learn solely contacts on Android gadgets have been completely explored. The constraints inherent in synchronized accounts stop direct deletion by standard means. Administration methods, encompassing net interface modification, managed synchronization, and strategic filtering, supply viable paths to addressing this problem. Superior strategies, whereas presenting elevated dangers, supply various options for skilled customers.
The continuing evolution of Android working methods and make contact with synchronization protocols necessitates continued vigilance involved administration. Customers are inspired to undertake proactive methods for sustaining correct and streamlined contact lists. Considerate consideration of account permissions and information synchronization practices will contribute to a extra environment friendly and safe cell communication expertise. Continued consciousness of accessible instruments and strategies is paramount for managing contact data successfully.
