FreePrograms.me

Problems with the Google Play service: error when receiving data from the server [RPC:S-7:AEC-0]

Проблемы с сервисом Google Play: ошибка при получении данных с сервера [RPC:S-7:AEC-0]
Error RPC:S-7:AEC-0 is one of those problems that may not be solved quickly and easily. It occurs when, when trying to obtain information from Google Play, the service cannot identify the processor or RAM of the device being used, as a result of which updating the application may be impossible. Solving the problem: first steps
To fix this error, it is recommended to first do some basic steps one by one, which, although not a fact, can help fix the error:
  1. Completely reboot your device. In some situations this solves the problem.
  2. Check that the time on the device is correct. Make sure the assigned time zone matches reality.
  3. Clear cache and other minor accumulated data on your device. For this:
    1. Go to Setting - The dispatcher is private - All, then click on the icon Google Play Services.

      Проблемы с сервисом Google Play: ошибка при получении данных с сервера [RPC:S-7:AEC-0]


    2. In the menu that opens, click on the button Stop, then carry out removing installed updates.




  4. Try restarting synchronization with the service. To do this, go to Setting - Accounts - Googlewhere disable synchronization. Reboot your device and turn this feature back on.

Radical methods: deleting your Google account
If the above methods do not solve the problem with obtaining data from the server, then you need to resort to re-creating your account in the Google service. For this:
  1. Open Setting - Accounts - Google.
  2. Click on the button Delete account.



  3. After this, restart your device and create a new profile in the Google service.
If none of these methods still helped you, then we advise you to implement reset your Android device to factory settings.
December 14, 2016 1
Comment
Enter the code below:*
Click on the image to update the code if it is illegible
  1. Diz1k
    Diz1k
    6 December 2023 21: 00
    I had this error on two devices, thanks I solved it