07-03-2016, 11:47 AM
(This post was last modified: 07-03-2016, 11:58 AM by Raslin777@gmail.com.)
For me the workaround of just going to
Settings=>accounts=>add account=>google account
It will verify your account setting before adding the new Google account. Just cancel or exit the screen and goto Google play. Should be working fine for a while before it happens again or you reboot.
Total time for workaround is about 30secs.
I originally thought that this was a certificate/token issue due to it seemed it happened after rebooting. The build.prop listed the timezone as Los Angeles which is incorrect because I'm in New York. I figured maybe while it verified the account at boot up it had the incorrect time but it seems that this is not the case. I modified the build.prop to New York, re-authenticated and rebooted. Same auth issue. I'm still looking at logcats for anything during the playstore issue. Next I will look at the live boot logcats to see if it logs anything during boot up.
I don't think this is the issue. I could be wrong but I think the authentication fails before the extsd error hits. Also when adding a new account shouldn't fix anything with mounted volumes which is a workaround. Unless it's looking to write to that location account information but caches it memory. Which would enable it to work till the memory is dropped for it. Maybe I should log all reads and writes. I'll post back with the results.
Settings=>accounts=>add account=>google account
It will verify your account setting before adding the new Google account. Just cancel or exit the screen and goto Google play. Should be working fine for a while before it happens again or you reboot.
Total time for workaround is about 30secs.
I originally thought that this was a certificate/token issue due to it seemed it happened after rebooting. The build.prop listed the timezone as Los Angeles which is incorrect because I'm in New York. I figured maybe while it verified the account at boot up it had the incorrect time but it seems that this is not the case. I modified the build.prop to New York, re-authenticated and rebooted. Same auth issue. I'm still looking at logcats for anything during the playstore issue. Next I will look at the live boot logcats to see if it logs anything during boot up.
(06-21-2016, 11:04 AM)xtcrefugee Wrote: Same issue, using the 32GB Remix image. It would be nice if there was a quicker fix than removing and re-adding the Google account.
Googling DF-DLA-15 shows unmounting external storage as a possible solution. I noticed that the Remix file manager sees several additional volumes that cannot be read or written to and I've not seen that on an Android device before, is there any chance these (whatever they are) are causing the problem?
I don't think this is the issue. I could be wrong but I think the authentication fails before the extsd error hits. Also when adding a new account shouldn't fix anything with mounted volumes which is a workaround. Unless it's looking to write to that location account information but caches it memory. Which would enable it to work till the memory is dropped for it. Maybe I should log all reads and writes. I'll post back with the results.
