【问题标题】:Google play connect failed谷歌播放连接失败
【发布时间】:2017-02-13 22:22:55
【问题描述】:

最近,我在使用 Google Play 时遇到问题,您可以在下面找到日志:

06-15 13:12:08.827  2942  6113 E CheckinTask: Checkin failed: https://android.clients.google.com/checkin (request #0): java.io.IOException: Rejected response from server: invalid hardware identifier: "DP7C Pro-SGA1" is not a valid device
06-15 13:12:08.827  4590  5984 D FotaUpdate: SdcardUtil:getExternalStorageStateExt: Environment.getExternalStorageState = mounted
06-15 13:12:08.829  2942  6113 V CheckinService: No Subscriptions found on the device
06-15 13:12:08.830  4590  5984 D Environment: getStorageVolume,  volume:StorageVolume:
06-15 13:12:08.830  4590  5984 D Environment:     mStorageId=65537 mPath=/storage/sdcard0 mDescriptionId=17040808 
06-15 13:12:08.830  4590  5984 D Environment:     mPrimary=true mRemovable=false mEmulated=true mMtpReserveSpace=10 
06-15 13:12:08.830  4590  5984 D Environment:     mAllowMassStorage=false mMaxFileSize=0 mOwner=UserHandle{0} mUuid=null 
06-15 13:12:08.830  4590  5984 D Environment:     mUserLabel=null mState=mounted 
06-15 13:12:08.830  4590  5984 D Environment: getStorageVolume,  volume:StorageVolume:
06-15 13:12:08.830  4590  5984 D Environment:     mStorageId=131073 mPath=/storage/sdcard1 mDescriptionId=17040806 
06-15 13:12:08.830  4590  5984 D Environment:     mPrimary=false mRemovable=true mEmulated=false mMtpReserveSpace=0 
06-15 13:12:08.830  4590  5984 D Environment:     mAllowMassStorage=true mMaxFileSize=0 mOwner=null mUuid=null 
06-15 13:12:08.830  4590  5984 D Environment:     mUserLabel=null mState=removed 
06-15 13:12:08.831  2942  6113 I CheckinService: Checking schedule, now: 1465992728830 next: 1465992763827
06-15 13:12:08.831  2942  6113 I CheckinService: active receiver: disabled

我有 3 个问题:

  1. Google Play checkinservice 是否在连接时验证序列号和 ro.product.device?
  2. 它的命名规则是什么?是否会检查任何其他参数?
  3. 设备是否可以使用默认序列号“0123456789ABCDEF”连接到 Google Play?

【问题讨论】:

    标签: android google-play-services


    【解决方案1】:

    好的,Google Play 的访问权限是由批准的设备授予的。如果您将 build.prop 文件中的设备名称更改为它无法识别的名称,它将不允许您进入。如果您没有更改设备名称,您可能需要恢复出厂设置以解决问题.

    【讨论】:

      【解决方案2】:

      属性“ro.product.device”不应包含任何空格。 这是“人工验证”的问题。

      【讨论】:

        猜你喜欢
        • 1970-01-01
        • 2019-07-05
        • 2012-12-15
        • 1970-01-01
        • 1970-01-01
        • 2012-01-24
        • 1970-01-01
        • 2016-08-25
        • 1970-01-01
        相关资源
        最近更新 更多