Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
SD Card corrupt error - Moto G5, Android 7
795 views
Skip to first unread message
Biggles
Jun 12, 2017, 12:55:43 PM6/12/17
to
We have two Moto G5 phones, both with 64GB micro SD cards for additional
storage, formatted to store files (i.e. so that the cards can be read in
a PC or another device. Several times now, on both phones, on starting
the phone from OFF, Android reports the SD card as corrupt and says "tap
to fix". Well the "fix" is to reformat the card, so hardly a fix.
Anyhow, the "corrupt" cards read OK in Windows 10 on laptop, and copying
the data in Windows then reformatting the card in Android seems to fix
the problem, then a couple of restarts later the card is reported again
as "corrupt". In frustration I have tried switching the phone off and on
again, and this usually clears the error, not always on the first power
cycle, but usually by the third.
We don't tend to switch our phones off very often, but it is very
irritating to have to power cycle the phone several times to get the
card recognised. Has anyone else had this problem - I'm trying to figure
out whether it is Moto hardware, Android software, SD card or a
combination which is causing the problem. We are using two SD cards from
the same manufacturer, and I have tried one from a different
manufacturer which "seems" to not suffer from the same issue, but as it
is intermittent it's difficult to be sure.
Never had a problem with my previous phone which was Android 5 but only
16GB SD card.
Has anyone else had this problem with SD cards in phones?
Cheers
Biggles
storage, formatted to store files (i.e. so that the cards can be read in
a PC or another device. Several times now, on both phones, on starting
the phone from OFF, Android reports the SD card as corrupt and says "tap
to fix". Well the "fix" is to reformat the card, so hardly a fix.
Anyhow, the "corrupt" cards read OK in Windows 10 on laptop, and copying
the data in Windows then reformatting the card in Android seems to fix
the problem, then a couple of restarts later the card is reported again
as "corrupt". In frustration I have tried switching the phone off and on
again, and this usually clears the error, not always on the first power
cycle, but usually by the third.
We don't tend to switch our phones off very often, but it is very
irritating to have to power cycle the phone several times to get the
card recognised. Has anyone else had this problem - I'm trying to figure
out whether it is Moto hardware, Android software, SD card or a
combination which is causing the problem. We are using two SD cards from
the same manufacturer, and I have tried one from a different
manufacturer which "seems" to not suffer from the same issue, but as it
is intermittent it's difficult to be sure.
Never had a problem with my previous phone which was Android 5 but only
16GB SD card.
Has anyone else had this problem with SD cards in phones?
Cheers
Biggles
nospam
Jun 12, 2017, 2:15:53 PM6/12/17
to
In article <ohmgrm$u7f$1...@dont-email.me>, Biggles
shit about errors (no surprise there) or isn't hitting the spots that
do have errors, while android is.
replace the card.
> We don't tend to switch our phones off very often, but it is very
> irritating to have to power cycle the phone several times to get the
> card recognised. Has anyone else had this problem - I'm trying to figure
> out whether it is Moto hardware, Android software, SD card or a
> combination which is causing the problem. We are using two SD cards from
> the same manufacturer, and I have tried one from a different
> manufacturer which "seems" to not suffer from the same issue, but as it
> is intermittent it's difficult to be sure.
further evidence it's the card.
> Never had a problem with my previous phone which was Android 5 but only
> 16GB SD card.
that's different card and a different phone.
<ne...@packaging.the-shillings.net> wrote:
> We have two Moto G5 phones, both with 64GB micro SD cards for additional
> storage, formatted to store files (i.e. so that the cards can be read in
> a PC or another device. Several times now, on both phones, on starting
> the phone from OFF, Android reports the SD card as corrupt and says "tap
> to fix". Well the "fix" is to reformat the card, so hardly a fix.
> Anyhow, the "corrupt" cards read OK in Windows 10 on laptop, and copying
> the data in Windows then reformatting the card in Android seems to fix
> the problem, then a couple of restarts later the card is reported again
> as "corrupt". In frustration I have tried switching the phone off and on
> again, and this usually clears the error, not always on the first power
> cycle, but usually by the third.
that sounds like a marginally defective card. windows doesn't give a
> We have two Moto G5 phones, both with 64GB micro SD cards for additional
> storage, formatted to store files (i.e. so that the cards can be read in
> a PC or another device. Several times now, on both phones, on starting
> the phone from OFF, Android reports the SD card as corrupt and says "tap
> to fix". Well the "fix" is to reformat the card, so hardly a fix.
> Anyhow, the "corrupt" cards read OK in Windows 10 on laptop, and copying
> the data in Windows then reformatting the card in Android seems to fix
> the problem, then a couple of restarts later the card is reported again
> as "corrupt". In frustration I have tried switching the phone off and on
> again, and this usually clears the error, not always on the first power
> cycle, but usually by the third.
shit about errors (no surprise there) or isn't hitting the spots that
do have errors, while android is.
replace the card.
> We don't tend to switch our phones off very often, but it is very
> irritating to have to power cycle the phone several times to get the
> card recognised. Has anyone else had this problem - I'm trying to figure
> out whether it is Moto hardware, Android software, SD card or a
> combination which is causing the problem. We are using two SD cards from
> the same manufacturer, and I have tried one from a different
> manufacturer which "seems" to not suffer from the same issue, but as it
> is intermittent it's difficult to be sure.
> Never had a problem with my previous phone which was Android 5 but only
> 16GB SD card.
Robert Marshall
Jun 12, 2017, 4:20:04 PM6/12/17
to
On Mon, Jun 12 2017, Biggles <ne...@packaging.the-shillings.net> wrote:
> We have two Moto G5 phones, both with 64GB micro SD cards for
> additional storage, formatted to store files (i.e. so that the cards
> can be read in a PC or another device. Several times now, on both
> phones, on starting the phone from OFF, Android reports the SD card as
> corrupt and says "tap to fix". Well the "fix" is to reformat the card,
> so hardly a fix. Anyhow, the "corrupt" cards read OK in Windows 10 on
> laptop, and copying the data in Windows then reformatting the card in
> Android seems to fix the problem, then a couple of restarts later the
> card is reported again as "corrupt". In frustration I have tried
> switching the phone off and on again, and this usually clears the
> error, not always on the first power cycle, but usually by the third.
>
>
> We have two Moto G5 phones, both with 64GB micro SD cards for
> additional storage, formatted to store files (i.e. so that the cards
> can be read in a PC or another device. Several times now, on both
> phones, on starting the phone from OFF, Android reports the SD card as
> corrupt and says "tap to fix". Well the "fix" is to reformat the card,
> so hardly a fix. Anyhow, the "corrupt" cards read OK in Windows 10 on
> laptop, and copying the data in Windows then reformatting the card in
> Android seems to fix the problem, then a couple of restarts later the
> card is reported again as "corrupt". In frustration I have tried
> switching the phone off and on again, and this usually clears the
> error, not always on the first power cycle, but usually by the third.
>
>
> Has anyone else had this problem with SD cards in phones?
>
I've seen this problem with a moto g5 and 32GB card, my suspicions are
>
about the card, though I've already done one replacement - there's
sometimes also errors on music tracks on the card - when it's been
successfully recognised. Yes and a second reboot clears it for me -
never had to go to a third.
Robert
--
La grenouille songe..dans son château d'eau
Frank Slootweg
Jun 13, 2017, 9:47:18 AM6/13/17
to
Biggles <ne...@packaging.the-shillings.net> wrote:
> We have two Moto G5 phones, both with 64GB micro SD cards for additional
> storage, formatted to store files (i.e. so that the cards can be read in
> a PC or another device. Several times now, on both phones, on starting
> the phone from OFF, Android reports the SD card as corrupt and says "tap
> to fix". Well the "fix" is to reformat the card, so hardly a fix.
> Anyhow, the "corrupt" cards read OK in Windows 10 on laptop, and copying
> the data in Windows then reformatting the card in Android seems to fix
> the problem, then a couple of restarts later the card is reported again
> as "corrupt". In frustration I have tried switching the phone off and on
> again, and this usually clears the error, not always on the first power
> cycle, but usually by the third.
Are you sure that the phones support 64GB MicroSD cards?
> We have two Moto G5 phones, both with 64GB micro SD cards for additional
> storage, formatted to store files (i.e. so that the cards can be read in
> a PC or another device. Several times now, on both phones, on starting
> the phone from OFF, Android reports the SD card as corrupt and says "tap
> to fix". Well the "fix" is to reformat the card, so hardly a fix.
> Anyhow, the "corrupt" cards read OK in Windows 10 on laptop, and copying
> the data in Windows then reformatting the card in Android seems to fix
> the problem, then a couple of restarts later the card is reported again
> as "corrupt". In frustration I have tried switching the phone off and on
> again, and this usually clears the error, not always on the first power
> cycle, but usually by the third.
Your 16GB cards are SDHC cards. SDHC cards go upto 32GB.
A 64GB card is a SDXC card and hence your devices must be compatible
with that standard.
If your phones are incompatible with 64GB SDXC cards, I would expect
them to not accept the cards are all, but stranger things have happened.
If your phones are incompatible, but do accept the cards, then the
problem might occur when the phones try to write to an area above 32GB.
If you're not sure, then lookup the specs for your device. IME, the
manufacturers manuals are totally useless for this and the manufacturers
website is mostly useless for this.
IME, <http://www.gsmarena.com> is a good source for these kind of
technical specifications.
If "Moto G5" is a sufficiently exact product indentification, then
gsmarena says it supports upto 256GB cards, so 64GB *should* not be a
problem.
Anyway, I recently posted here about a similar problem with a camera
which also could only be 'solved' by using a different type of card.
[...]
daar...@gmail.com
Jan 20, 2018, 8:58:47 AM1/20/18
to
Hopefully, the Android developer community will acknowledge the issue soon and fix it - after all, it shouldn't be too hard to find by tracking back through the code commits and finding any that relate to power-down procedures. It will be a change that was made between the final Android 6 and Android 7.0.
Regards, David
daar...@gmail.com
Jan 20, 2018, 8:58:57 AM1/20/18
to
On Monday, 12 June 2017 17:55:43 UTC+1, Biggles wrote:
Roger Mills
Jan 20, 2018, 5:17:18 PM1/20/18
to
Android 6. I use a 16GB micro-SD card, configured as system memory. I've
had no less than THREE of these go bad!
Typically, this is what happens. You need to re-start Android for some
reason; either it's run out of juice and shut down, or you decide that a
reset would be a good idea. You input the password when requested, and
it says "Checking". [When everything is normal, after a few seconds it
says "Starting Android"]. Under fault conditions, it displays "checking"
for *ages* and then eventually says that there is an error. Although the
password is correct, it has been unable to decrypt the memory, and it is
necessary to reset it to factory conditions. DOOM!
If you ignore that, and shut it down and start it again, it *may* be ok
next time - but most likely it will say that it cannot access the SD
card. The phone will work, but any apps on the card won't run, of
course. A card configured as system memory can't be read by a computer,
so has to be replaced.
I was hoping that if I replaced the G2 with a later model, I wouldn't
get this problem any more - but it seems like I'm wrong!
--
Cheers,
Roger
____________
Please reply to Newsgroup. Whilst email address is valid, it is seldom
checked.
VanguardLH
Jan 21, 2018, 2:10:38 AM1/21/18
to
daargles wrote:
> Biggles wrote:
>
>> We have two Moto G5 phones, both with 64GB micro SD cards for additional
>> storage, formatted to store files (i.e. so that the cards can be read in
>> a PC or another device. Several times now, on both phones, on starting
>> the phone from OFF, Android reports the SD card as corrupt and says "tap
>> to fix". Well the "fix" is to reformat the card, so hardly a fix.
>> Anyhow, the "corrupt" cards read OK in Windows 10 on laptop, and copying
>> the data in Windows then reformatting the card in Android seems to fix
>> the problem, then a couple of restarts later the card is reported again
>> as "corrupt". In frustration I have tried switching the phone off and on
>> again, and this usually clears the error, not always on the first power
>> cycle, but usually by the third.
>>
>> We don't tend to switch our phones off very often, but it is very
>> irritating to have to power cycle the phone several times to get the
>> card recognised. Has anyone else had this problem - I'm trying to figure
>> out whether it is Moto hardware, Android software, SD card or a
>> combination which is causing the problem. We are using two SD cards from
>> the same manufacturer, and I have tried one from a different
>> manufacturer which "seems" to not suffer from the same issue, but as it
>> is intermittent it's difficult to be sure.
>>
>> Never had a problem with my previous phone which was Android 5 but only
>> 16GB SD card.
>>
>> Has anyone else had this problem with SD cards in phones?
>
> Biggles wrote:
>
>> We have two Moto G5 phones, both with 64GB micro SD cards for additional
>> storage, formatted to store files (i.e. so that the cards can be read in
>> a PC or another device. Several times now, on both phones, on starting
>> the phone from OFF, Android reports the SD card as corrupt and says "tap
>> to fix". Well the "fix" is to reformat the card, so hardly a fix.
>> Anyhow, the "corrupt" cards read OK in Windows 10 on laptop, and copying
>> the data in Windows then reformatting the card in Android seems to fix
>> the problem, then a couple of restarts later the card is reported again
>> as "corrupt". In frustration I have tried switching the phone off and on
>> again, and this usually clears the error, not always on the first power
>> cycle, but usually by the third.
>>
>> We don't tend to switch our phones off very often, but it is very
>> irritating to have to power cycle the phone several times to get the
>> card recognised. Has anyone else had this problem - I'm trying to figure
>> out whether it is Moto hardware, Android software, SD card or a
>> combination which is causing the problem. We are using two SD cards from
>> the same manufacturer, and I have tried one from a different
>> manufacturer which "seems" to not suffer from the same issue, but as it
>> is intermittent it's difficult to be sure.
>>
>> Never had a problem with my previous phone which was Android 5 but only
>> 16GB SD card.
>>
>> Has anyone else had this problem with SD cards in phones?
>
> It's an Android 7.0 problem. The issue is being widely reported in
> the Lenovo and Samsung communities, and it's always after a
> power-down restart that the issue occurs. With the Moto G5 series of
> phones, it's not so obvious that it's an Android 7.0 fault, but it's
> clear in the Samsung community - phone/SD card combinations work fine
> until they upgrade from the starting Android 6 to Android 7.
>
> Hopefully, the Android developer community will acknowledge the issue
> soon and fix it - after all, it shouldn't be too hard to find by
> tracking back through the code commits and finding any that relate to
> power-down procedures. It will be a change that was made between the
> final Android 6 and Android 7.0.
When you meld or adopt the SD card with internal storage, the SD card
> the Lenovo and Samsung communities, and it's always after a
> power-down restart that the issue occurs. With the Moto G5 series of
> phones, it's not so obvious that it's an Android 7.0 fault, but it's
> clear in the Samsung community - phone/SD card combinations work fine
> until they upgrade from the starting Android 6 to Android 7.
>
> Hopefully, the Android developer community will acknowledge the issue
> soon and fix it - after all, it shouldn't be too hard to find by
> tracking back through the code commits and finding any that relate to
> power-down procedures. It will be a change that was made between the
> final Android 6 and Android 7.0.
gets encrypted. If you configure the SD card as secondary storage, you
don't have to encrypt it (which keeps it portable). Also, adopting the
SD card doesn't give you oldstorage+newstorage for capacity. You lose
the internal storage which got supplanted when you made the SD card all
of your internal storage capacity. Adoptable Storage is a bad idea.
Do NOT elect formatting the SD card as internal (primary) storage. This
adoption option became available back in Android 6.
https://liliputing.com/2015/10/android-6-0-can-treat-sd-cards-as-internal-storage-at-a-cost.html
https://www.androidcentral.com/adoptable-storage
There is no guarantee the certificate used in one version of Android
will the same one used in another version of Android. I'm not sure that
even different instances of the same Android version will use the same
encryption certificate. The encryption is performed on the SD card
under the instance of the Android version that did the encrypting. When
you choose to adopt the SD card to supplant internal storage, the SD
card *will* get encrypted. You don't get a choice. Once you elect
adoptable storage for the SD card, the SD is *never* to get removed;
else, it become unreadable (that's the point of the encryption). The SD
card gets locked to *that* Android instance.
According the 2nd article above (which Moto G5), Samsung removed
Adoptable Storage in their modified version of Android. Guess Moto
decided to let it slide through.
When I first saw Adoptable Storage, yeah, it looked like a keen way to
increase the interal storage. However, then I read further and realized
I was tossing my onboard internal storage for the far slower SD card's
storage. Instead of buying a cheaper smartphone with less internal
storage, and because Adoptable Storage wasn't anything I wanted to use,
I got a smartphone with more internal storage to start with. The SD
card - removed from my old smartphone and transferred to the new one -
remained secondary (normal) storage.
Users forget or don't know that flash memory cards are disposable memory
devices. They degrade with every write. Storing videos, audio, photos,
or other static data files incurs sufficiently low write volume that a
flash card will last a long time, like 10 years, or more. However, when
flash gets used in a scenario that generates a huge volume of writes
then its lifespan gets shortened at a much faster pace. Using flash as
internal storage used by the OS and apps means a lot of contant writing.
If you use the SD card for adoptable storage, make sure to get a fast
one, not the cheapies found in sales to lure you to a site.
The Real Bev
Jan 21, 2018, 2:21:34 AM1/21/18
to
and a lot of apps still wrote themselves to actual internal space rather
than the sdcard, so I still ran out of memory pretty quickly.
Android 7 (different phone) didn't seem to offer than option, which I
would have rejected anyway -- I don't see how I can use all 64GB of
internal space PLUS the 64GB sdcard :-)
--
Cheers, Bev
"I believe that forgiving [terrorists] is God's function.
Our job is to arrange the meeting."
- Norman Schwartzkopf
Carlos E.R.
Jan 21, 2018, 3:44:08 PM1/21/18
to
the same route. The card would show no problem at all on the computer,
yet I backed it up, then formatted with sector testing: no issues found,
but it failed on the phone. I replaced the card with a new one, smaller
and different brand - same issue. I told the phone to go ahead and
format the card, but it failed. Currently it doesn't even recognize that
there is a card in it.
I suspect the connections.
I found an official support thread where possibly hundreds of users of
that same model related the same problem. The official solution to the
thread is pure garbage. Some of them are using big, new, and very
expensive cards.
Spanish:
<https://forums.lenovo.com/t5/forums/v3_1/forumtopicpage/board-id/Moto-X-Play_es/page/8/thread-id/2>
That page is in Spanish, but may be of use to you to find a similar
support forum thread in English.
My problem started with Android 6 (months after having V6), and in the
middle of testing the thing got an update to Android 7, which I accepted
thinking it might solve the issue. It did not.
I have given up.
--
Cheers, Carlos.
The Real Bev
Jan 21, 2018, 5:05:01 PM1/21/18
to
The rest seemed like the usual stuff that never solves the actual
problem. Sometimes factory resets don't either if the hardware is crap
-- like the GPS chip in my BLU phone, which invented points all by itself!
> Spanish:
> <https://forums.lenovo.com/t5/forums/v3_1/forumtopicpage/board-id/Moto-X-Play_es/page/8/thread-id/2>
>
> That page is in Spanish, but may be of use to you to find a similar
> support forum thread in English.
https://forums.lenovo.com/t5/Moto-X-Play/Problemas-con-la-tarjeta-SD-desde-la-actualización-a-Android-6/m-p/3579909#M133
> My problem started with Android 6 (months after having V6), and in the
> middle of testing the thing got an update to Android 7, which I accepted
> thinking it might solve the issue. It did not.
recommended and it still didn't work. It should still be under
warranty, right?
> I have given up.
NOOOOOO!
--
Cheers, Bev
You know how dumb the average person is?
Well, by definition, half are *even dumber*!
Carlos E.R.
Jan 21, 2018, 5:44:08 PM1/21/18
to
On 2018-01-21 23:04, The Real Bev wrote:
> On 01/21/2018 12:41 PM, Carlos E.R. wrote:
>> On 2017-06-12 18:55, Biggles wrote:
...
> On 01/21/2018 12:41 PM, Carlos E.R. wrote:
>> On 2017-06-12 18:55, Biggles wrote:
>>> Has anyone else had this problem with SD cards in phones?
>>
>> Yes, I have that problem or very similar with my Motorola X Play. I went
>> the same route. The card would show no problem at all on the computer,
>> yet I backed it up, then formatted with sector testing: no issues found,
>> but it failed on the phone. I replaced the card with a new one, smaller
>> and different brand - same issue. I told the phone to go ahead and
>> format the card, but it failed. Currently it doesn't even recognize that
>> there is a card in it.
>>
>> I suspect the connections.
>>
>> I found an official support thread where possibly hundreds of users of
>> that same model related the same problem. The official solution to the
>> thread is pure garbage. Some of them are using big, new, and very
>> expensive cards.
>
> I assume that "restablécelo de fábrica" is "factory reset" in English.
> The rest seemed like the usual stuff that never solves the actual
> problem.
> Sometimes factory resets don't either if the hardware is crap
> -- like the GPS chip in my BLU phone, which invented points all by itself!
recipe worked for someone, and although I didn't read the 24 pages, I
didn't find any.
>
>> Spanish:
>> <https://forums.lenovo.com/t5/forums/v3_1/forumtopicpage/board-id/Moto-X-Play_es/page/8/thread-id/2>
>>
>>
>> That page is in Spanish, but may be of use to you to find a similar
>> support forum thread in English.
>
> Google translate does an OK job.
It is getting better and better.
>
> https://forums.lenovo.com/t5/Moto-X-Play/Problemas-con-la-tarjeta-SD-desde-la-actualización-a-Android-6/m-p/3579909#M133
>
>
>> My problem started with Android 6 (months after having V6), and in the
>> middle of testing the thing got an update to Android 7, which I accepted
>> thinking it might solve the issue. It did not.
>
> I think the G5 and XPlays are both bad. You did everything they
> recommended and it still didn't work. It should still be under
> warranty, right?
April 2016. Hum! I should check whether the warranty was two years or
one. Hum. More things to do.
>> I have given up.
>
> NOOOOOO!
is a memory hog.
That the G5 maybe bad is bad news to me, because I was about to
recommend the G5S+ to a friend. The price is right, the features are
right, and I prefer a phone that is as pure Android as possible: I
bought mine with Android 5, it got updated to 6, and about a month ago
to 7. She has a Samsung Galaxy trend plus, which shuts off when se tried
to do somethings like viewing a video. Its memory its too short, the
Android version too old. Similar to my Galaxy Mini II. Samsung appears
to never upgrade their versions. Good hardware typically but obsolete
software.
--
Cheers, Carlos.
The Real Bev
Jan 21, 2018, 7:08:10 PM1/21/18
to
suspect that a factory reset RARELY actually solves the problem itself,
it just kills everything. You're probably too young to remember TRS-80
computers. Their contacts were NOT gold-plated and eventually corrosion
made something stop working. No matter what went wrong, the solution
was to take the machine apart, clean all the contacts, and put it back
together again.
The equivalent of a factory reset, except that it didn't wipe the floppy
disks!
>>> Spanish:
>>> <https://forums.lenovo.com/t5/forums/v3_1/forumtopicpage/board-id/Moto-X-Play_es/page/8/thread-id/2>
>>>
>>>
>>> That page is in Spanish, but may be of use to you to find a similar
>>> support forum thread in English.
>>
>> Google translate does an OK job.
>
> Good :-)
>
> It is getting better and better.
>>
>> https://forums.lenovo.com/t5/Moto-X-Play/Problemas-con-la-tarjeta-SD-desde-la-actualización-a-Android-6/m-p/3579909#M133
>>
>>> My problem started with Android 6 (months after having V6), and in the
>>> middle of testing the thing got an update to Android 7, which I accepted
>>> thinking it might solve the issue. It did not.
>>
>> I think the G5 and XPlays are both bad. You did everything they
>> recommended and it still didn't work. It should still be under
>> warranty, right?
>
> No, I don't think so. I don't remember the date of purchase, but perhaps
> April 2016. Hum! I should check whether the warranty was two years or
> one. Hum. More things to do.
>>> I have given up.
>>
>> NOOOOOO!
>
> I can live without a memory card, but I have to empty it often: whatsap
> is a memory hog.
>
> That the G5 maybe bad is bad news to me, because I was about to
> recommend the G5S+ to a friend. The price is right, the features are
> right, and I prefer a phone that is as pure Android as possible: I
> bought mine with Android 5, it got updated to 6, and about a month ago
> to 7. She has a Samsung Galaxy trend plus, which shuts off when se tried
> to do somethings like viewing a video. Its memory its too short, the
> Android version too old. Similar to my Galaxy Mini II. Samsung appears
> to never upgrade their versions. Good hardware typically but obsolete
> software.
2-year guarantee. I should know, but I don't. I think everybody was
selling them off for roughly the same price in anticipation of the G5S
with a bigger screen and "better" camera. So far the only problem I've
had is the inability to use the phone after I installed the cheap
hotspot, and that had nothing to do with either the hotspot or the
phone, but with a setting on the keyboard I'd chosen :-( The only thing
Lenovo/Motorola could suggest was a factory reset.
--
Cheers, Bev
I've had a Lucas pacemaker for years and have
never experienced any prob
Carlos E.R.
Jan 21, 2018, 7:48:09 PM1/21/18
to
instead, I remember the Sinclair ZX80 ;-)
>
> The equivalent of a factory reset, except that it didn't wipe the floppy
> disks!
Rather similar to the actual bugs problems in the primitive tube or
relais computers.
I suspect the contacts in the card socket because each time I removed
the card and reinserted it the problem was worse. It may well be that
they are not gold plated! But the socket is so tiny that it seems
impossible to reach it and clean or bend them without breaking something
else. But it would be the first time I would see a card fail because of
such a thing.
I would certainly try a factory reset if 1) somebody said that it
worked, and everybody I read said no, and 2), if it wasn't a recipe the
flower pots repeat every time for every problem they have no idea what
else to say.
>>> I think the G5 and XPlays are both bad. You did everything they
>>> recommended and it still didn't work. It should still be under
>>> warranty, right?
>>
>> No, I don't think so. I don't remember the date of purchase, but perhaps
>> April 2016. Hum! I should check whether the warranty was two years or
>> one. Hum. More things to do.
>
> Most credit cards extend the warranty by some amount of time.
>>>> I have given up.
>>>
>>> NOOOOOO!
>>
>> I can live without a memory card, but I have to empty it often: whatsap
>> is a memory hog.
>>
>> That the G5 maybe bad is bad news to me, because I was about to
>> recommend the G5S+ to a friend. The price is right, the features are
>> right, and I prefer a phone that is as pure Android as possible: I
>> bought mine with Android 5, it got updated to 6, and about a month ago
>> to 7. She has a Samsung Galaxy trend plus, which shuts off when se tried
>> to do somethings like viewing a video. Its memory its too short, the
>> Android version too old. Similar to my Galaxy Mini II. Samsung appears
>> to never upgrade their versions. Good hardware typically but obsolete
>> software.
>
> I bought my G5 in November from Best Buy -- I think that gives me a
> 2-year guarantee. I should know, but I don't. I think everybody was
> selling them off for roughly the same price in anticipation of the G5S
> with a bigger screen and "better" camera. So far the only problem I've
> had is the inability to use the phone after I installed the cheap
> hotspot, and that had nothing to do with either the hotspot or the
> phone, but with a setting on the keyboard I'd chosen :-( The only thing
> Lenovo/Motorola could suggest was a factory reset.
--
Cheers, Carlos.
Frank Slootweg
Jan 22, 2018, 9:57:30 AM1/22/18
to
[I do not have the original post, so I'm using the copy which Carlos
quoted:]
Carlos E.R. <robin_...@es.invalid> wrote:
> On 2017-06-12 18:55, Biggles wrote:
> > We have two Moto G5 phones, both with 64GB micro SD cards for additional
> > storage, formatted to store files (i.e. so that the cards can be read in
> > a PC or another device. Several times now, on both phones, on starting
> > the phone from OFF, Android reports the SD card as corrupt and says "tap
> > to fix". Well the "fix" is to reformat the card, so hardly a fix.
> > Anyhow, the "corrupt" cards read OK in Windows 10 on laptop, and copying
> > the data in Windows then reformatting the card in Android seems to fix
> > the problem, then a couple of restarts later the card is reported again
> > as "corrupt". In frustration I have tried switching the phone off and on
> > again, and this usually clears the error, not always on the first power
> > cycle, but usually by the third.
> >
> > We don't tend to switch our phones off very often, but it is very
> > irritating to have to power cycle the phone several times to get the
> > card recognised. Has anyone else had this problem - I'm trying to figure
> > out whether it is Moto hardware, Android software, SD card or a
> > combination which is causing the problem. We are using two SD cards from
> > the same manufacturer, and I have tried one from a different
> > manufacturer which "seems" to not suffer from the same issue, but as it
> > is intermittent it's difficult to be sure.
> >
> > Never had a problem with my previous phone which was Android 5 but only
> > 16GB SD card.
> >
> > Has anyone else had this problem with SD cards in phones?
Biggles,
Are you sure that the Moto G5 phones *do* support *64GB* MicroSD-cards?
64GB cards are SDXC cards, which is a different electronic standard
than the (16GB) SDHC card you used before. (SDHC supports upto 32GB.)
Please check specifically that the Moto G5 phone actually does support
64GB SDXC cards.
If it does not support SDXC, then all kind of problems can and do
occur.
> Yes, I have that problem or very similar with my Motorola X Play. I went
> the same route. The card would show no problem at all on the computer,
> yet I backed it up, then formatted with sector testing: no issues found,
> but it failed on the phone. I replaced the card with a new one, smaller
> and different brand - same issue. I told the phone to go ahead and
> format the card, but it failed. Currently it doesn't even recognize that
> there is a card in it.
>
> I suspect the connections.
>
> I found an official support thread where possibly hundreds of users of
> that same model related the same problem. The official solution to the
> thread is pure garbage. Some of them are using big, new, and very
> expensive cards.
Carlos,
Same comment for you: Are you sure your phone supports the capacity
(in GB) cards you're using?
quoted:]
Carlos E.R. <robin_...@es.invalid> wrote:
> On 2017-06-12 18:55, Biggles wrote:
> > We have two Moto G5 phones, both with 64GB micro SD cards for additional
> > storage, formatted to store files (i.e. so that the cards can be read in
> > a PC or another device. Several times now, on both phones, on starting
> > the phone from OFF, Android reports the SD card as corrupt and says "tap
> > to fix". Well the "fix" is to reformat the card, so hardly a fix.
> > Anyhow, the "corrupt" cards read OK in Windows 10 on laptop, and copying
> > the data in Windows then reformatting the card in Android seems to fix
> > the problem, then a couple of restarts later the card is reported again
> > as "corrupt". In frustration I have tried switching the phone off and on
> > again, and this usually clears the error, not always on the first power
> > cycle, but usually by the third.
> >
> > We don't tend to switch our phones off very often, but it is very
> > irritating to have to power cycle the phone several times to get the
> > card recognised. Has anyone else had this problem - I'm trying to figure
> > out whether it is Moto hardware, Android software, SD card or a
> > combination which is causing the problem. We are using two SD cards from
> > the same manufacturer, and I have tried one from a different
> > manufacturer which "seems" to not suffer from the same issue, but as it
> > is intermittent it's difficult to be sure.
> >
> > Never had a problem with my previous phone which was Android 5 but only
> > 16GB SD card.
> >
> > Has anyone else had this problem with SD cards in phones?
Are you sure that the Moto G5 phones *do* support *64GB* MicroSD-cards?
64GB cards are SDXC cards, which is a different electronic standard
than the (16GB) SDHC card you used before. (SDHC supports upto 32GB.)
Please check specifically that the Moto G5 phone actually does support
64GB SDXC cards.
If it does not support SDXC, then all kind of problems can and do
occur.
> Yes, I have that problem or very similar with my Motorola X Play. I went
> the same route. The card would show no problem at all on the computer,
> yet I backed it up, then formatted with sector testing: no issues found,
> but it failed on the phone. I replaced the card with a new one, smaller
> and different brand - same issue. I told the phone to go ahead and
> format the card, but it failed. Currently it doesn't even recognize that
> there is a card in it.
>
> I suspect the connections.
>
> I found an official support thread where possibly hundreds of users of
> that same model related the same problem. The official solution to the
> thread is pure garbage. Some of them are using big, new, and very
> expensive cards.
Same comment for you: Are you sure your phone supports the capacity
(in GB) cards you're using?
The Real Bev
Jan 22, 2018, 11:32:41 AM1/22/18
to
brand card I bought, but it was one of the big-name cards from Best Buy
(~$25 on sale).
> 64GB cards are SDXC cards, which is a different electronic standard
> than the (16GB) SDHC card you used before. (SDHC supports upto 32GB.)
>
> Please check specifically that the Moto G5 phone actually does support
> 64GB SDXC cards.
>
> If it does not support SDXC, then all kind of problems can and do
> occur.
spec lists offered by non-manufacturers are simply wrong.
Manufacturers' lists less so, of course, but still...
--
Cheers, Bev
"A friend is someone who puts the needs of others above their own.
Find one of those people and take advantage of him." --Rat
Frank Slootweg
Jan 22, 2018, 12:00:01 PM1/22/18
to
*phone* says that it supports/works_with that capacity (in GB) cards,
i.e. *not* that - in your experience - it happens to work (FSVO 'work').
Note that the *quality* ("big-name card"), is only secondary! If the
capacity (in GB) is not officialy supported by the manufacturer, then
the quality doesn't matter.
> > 64GB cards are SDXC cards, which is a different electronic standard
> > than the (16GB) SDHC card you used before. (SDHC supports upto 32GB.)
> >
> > Please check specifically that the Moto G5 phone actually does support
> > 64GB SDXC cards.
> >
> > If it does not support SDXC, then all kind of problems can and do
> > occur.
>
> I'm pretty sure it says so in the specs. Incidentally, sometimes the
> spec lists offered by non-manufacturers are simply wrong.
> Manufacturers' lists less so, of course, but still...
Yes, I know that manufacturers often omit these (non) 'details' from
the skimpy - if any - 'manual' which they supply, but it's *essential*
information.
What I do is keep the 'datasheet' which I had before I bought the
bloody thing.
The Real Bev
Jan 22, 2018, 12:25:43 PM1/22/18
to
On 01/22/2018 09:00 AM, Frank Slootweg wrote:
> The Real Bev <bashl...@gmail.com> wrote:
>> On 01/22/2018 06:57 AM, Frank Slootweg wrote:
>> >
>> > Biggles,
>> >
>> > Are you sure that the Moto G5 phones *do* support *64GB* MicroSD-cards?
>>
>> Mine does! 64GB internal plus 64GB external. I can't remember which
>> brand card I bought, but it was one of the big-name cards from Best Buy
>> (~$25 on sale).
>
> Note that with 'support', I mean that the *manufacturer* of the
> *phone* says that it supports/works_with that capacity (in GB) cards,
> i.e. *not* that - in your experience - it happens to work (FSVO 'work').
>
> Note that the *quality* ("big-name card"), is only secondary! If the
> capacity (in GB) is not officialy supported by the manufacturer, then
> the quality doesn't matter.
Indeed. Before I bought the phone I checked out the capacities at the
> The Real Bev <bashl...@gmail.com> wrote:
>> On 01/22/2018 06:57 AM, Frank Slootweg wrote:
>> >
>> > Biggles,
>> >
>> > Are you sure that the Moto G5 phones *do* support *64GB* MicroSD-cards?
>>
>> Mine does! 64GB internal plus 64GB external. I can't remember which
>> brand card I bought, but it was one of the big-name cards from Best Buy
>> (~$25 on sale).
>
> Note that with 'support', I mean that the *manufacturer* of the
> *phone* says that it supports/works_with that capacity (in GB) cards,
> i.e. *not* that - in your experience - it happens to work (FSVO 'work').
>
> Note that the *quality* ("big-name card"), is only secondary! If the
> capacity (in GB) is not officialy supported by the manufacturer, then
> the quality doesn't matter.
Motorola website. (8GB internal memory, even with a 32GB external card,
is woefully inadequate in Android6!) I only mention 'brand name' from a
reputable store (right across the street) because we had serious trouble
buying what turned out to be counterfeit (or factory rejected) 128GB
cards from Amazon and ebay; we got our money back, but it was a nuisance.
>> > 64GB cards are SDXC cards, which is a different electronic standard
>> > than the (16GB) SDHC card you used before. (SDHC supports upto 32GB.)
>> >
>> > Please check specifically that the Moto G5 phone actually does support
>> > 64GB SDXC cards.
>> >
>> > If it does not support SDXC, then all kind of problems can and do
>> > occur.
>>
>> I'm pretty sure it says so in the specs. Incidentally, sometimes the
>> spec lists offered by non-manufacturers are simply wrong.
>> Manufacturers' lists less so, of course, but still...
>
> Don't be 'pretty sure', be *really* sure!
manufacturers' websites) is a real pain to navigate. Those for whom
this is of interest may do the research themselves.
> Yes, I know that manufacturers often omit these (non) 'details' from
> the skimpy - if any - 'manual' which they supply, but it's *essential*
> information.
>
> What I do is keep the 'datasheet' which I had before I bought the
> bloody thing.
Cheers, Bev
"Sure, everyone's in favor of saving Hitler's brain, but when
you put it into the body of a great white shark, suddenly
you're a madman." --Futurama
VanguardLH
Jan 22, 2018, 3:21:16 PM1/22/18
to
Frank Slootweg wrote:
> Are you sure that the Moto G5 phones *do* support *64GB* MicroSD-
> cards? 64GB cards are SDXC cards, which is a different electronic
> standard than the (16GB) SDHC card you used before. (SDHC supports
> upto 32GB.) Please check specifically that the Moto G5 phone actually
> does support 64GB SDXC cards. If it does not support SDXC, then all
> kind of problems can and do occur.
https://www3.lenovo.com/gb/en/smartphones-and-watches/moto/smartphones/Moto-G-5th-gen/p/PMIPMIK12MF
> Are you sure that the Moto G5 phones *do* support *64GB* MicroSD-
> cards? 64GB cards are SDXC cards, which is a different electronic
> standard than the (16GB) SDHC card you used before. (SDHC supports
> upto 32GB.) Please check specifically that the Moto G5 phone actually
> does support 64GB SDXC cards. If it does not support SDXC, then all
> kind of problems can and do occur.
Click on the Tech Specs tab.
"Storage (ROM): 16GB, up to 128GB microSD Card support"
https://motorola-mobility-en-in.custhelp.com/app/answers/prod_answer_detail/a_id/118108
Page 52
"Note: Your phone support microSD cards up to 128 GB."
The original thread was about the Moto G5 as per the Subject header so
that's whose specifications I looked up.
Carlos E.R.
Jan 23, 2018, 9:16:07 AM1/23/18
to
It is 32 GB, SandisDisk Ultra. The new replacement is 16 GB Toshiba, and
is not even recognized. None is recognized.
--
Cheers, Carlos.
VanguardLH
Jan 23, 2018, 3:01:05 PM1/23/18
to
A couple solutions mentions there. The 2nd is easier because it
involves just clearing cache and clearing data using the functions
available in the phone. The 1st solution (which seems to eradicate some
corrupted USB enumeration data in the OS) requires a USB-attached card
reader which would be at extra expense.
Carlos E.R.
Jan 23, 2018, 9:12:08 PM1/23/18
to
On 2018-01-23 21:00, VanguardLH wrote:
> https://forums.lenovo.com/t5/MOTO-G-3rd-Gen/SD-Card-Missing-Please-Reinsert/td-p/3283758/page/13
>
> A couple solutions mentions there. The 2nd is easier because it
> involves just clearing cache and clearing data using the functions
> available in the phone.
I think I did, but...
> https://forums.lenovo.com/t5/MOTO-G-3rd-Gen/SD-Card-Missing-Please-Reinsert/td-p/3283758/page/13
>
> A couple solutions mentions there. The 2nd is easier because it
> involves just clearing cache and clearing data using the functions
> available in the phone.
Delete all caches from all apps? How? I don't remember. Ok, I see it.
Doing... no dice.
> The 1st solution (which seems to eradicate some
> corrupted USB enumeration data in the OS) requires a USB-attached card
> reader which would be at extra expense.
This one looks interesting:
+++------------
09-20-2017 07:40 AM
I have found this probable solution: Gopi Kumar 7說：
This is a well discussed and easy to fix bug... Disconnect USB cable, go
to Settings, Apps, and Show System Apps and find External Storage and
Media Storage and clear data and cache on each one and reboot, then give
it 5 min after full boot up to rebuild media databases and connect to
USB and select MTP. Should be good to go.
https://productforums.google.com/forum/#!topic/nexus/11d21gbWyQo
------------++-
The apps name here seem to be "Almacenamiento de medios" and
"Almacenamiento externo". Did so, restarted the phone. Doesn't seem to
find any external storage.
Remove the card, delete that cache data, reinsert card... No dice, no
card seen at all.
I have to eat something, later I'll try the external hardware.
[...]
Ok, first I tried a new OTG I had bought (triple sockets), and it had
problems even with and USB stick. Then I noticed that what had problems
was the ES File explorer app. I also tried the old OTG cable.
The phone has no problems accessing an external USB stick, or the memory
cards. I tried two, the old and the new. The phone wanted to format the
old one, I did. I created directories, accessed files, no problem. But
it will not even detect the presence of any of those cards connected
"internally".
--
Cheers, Carlos.
VanguardLH
Jan 23, 2018, 10:01:57 PM1/23/18
to
screwup on managing "internal" memory (part of the mass subsystem of the
hardware although the OS likes to call it external storage).
Carlos E.R.
Jan 24, 2018, 6:12:08 AM1/24/18
to
On 2018-01-24 04:01, VanguardLH wrote:
--
Cheers, Carlos.
> Carlos E.R. wrote:
>> [...]
>>
>> Ok, first I tried a new OTG I had bought (triple sockets), and it had
>> problems even with and USB stick. Then I noticed that what had problems
>> was the ES File explorer app. I also tried the old OTG cable.
>>
>> The phone has no problems accessing an external USB stick, or the memory
>> cards. I tried two, the old and the new. The phone wanted to format the
>> old one, I did. I created directories, accessed files, no problem. But
>> it will not even detect the presence of any of those cards connected
>> "internally".
>
> Sounding more like a physical defect in the SIM/SDcard socket or an OS
> screwup on managing "internal" memory (part of the mass subsystem of the
> hardware although the OS likes to call it external storage).
I know :-(
>> [...]
>>
>> Ok, first I tried a new OTG I had bought (triple sockets), and it had
>> problems even with and USB stick. Then I noticed that what had problems
>> was the ES File explorer app. I also tried the old OTG cable.
>>
>> The phone has no problems accessing an external USB stick, or the memory
>> cards. I tried two, the old and the new. The phone wanted to format the
>> old one, I did. I created directories, accessed files, no problem. But
>> it will not even detect the presence of any of those cards connected
>> "internally".
>
> Sounding more like a physical defect in the SIM/SDcard socket or an OS
> screwup on managing "internal" memory (part of the mass subsystem of the
> hardware although the OS likes to call it external storage).
--
Cheers, Carlos.
Biggles
Feb 27, 2018, 2:03:59 PM2/27/18
to
daar...@gmail.com Wrote in message:
Looks like you are right. Just had an Android update (version
number didn't change, still 7.0) on both phones and they both
now restart without the SD card error. No recognition that I
could see from Motorola of the problem, or that the update should
fix it.
--
Biggles
----Android NewsGroup Reader----
http://usenet.sinaapp.com/
number didn't change, still 7.0) on both phones and they both
now restart without the SD card error. No recognition that I
could see from Motorola of the problem, or that the update should
fix it.
--
Biggles
----Android NewsGroup Reader----
http://usenet.sinaapp.com/
Carlos E.R.
Feb 28, 2018, 8:36:08 AM2/28/18
to
On 2018-02-27 20:03, Biggles wrote:
> daar...@gmail.com Wrote in message:
>> On Monday, 12 June 2017 17:55:43 UTC+1, Biggles wrote:
>> It's an Android 7.0 problem. The issue is being widely reported in the Lenovo and Samsung communities, and it's always after a power-down restart that the issue occurs. With the Moto G5 series of phones, it's not so obvious that it's an Android 7.0 fault, but it's clear in the Samsung community - phone/SD card combinations work fine until they upgrade from the starting Android 6 to Android 7.
>>
>> Hopefully, the Android developer community will acknowledge the issue soon and fix it - after all, it shouldn't be too hard to find by tracking back through the code commits and finding any that relate to power-down procedures. It will be a change that was made between the final Android 6 and Android 7.0.
>
> daar...@gmail.com Wrote in message:
>> On Monday, 12 June 2017 17:55:43 UTC+1, Biggles wrote:
>> It's an Android 7.0 problem. The issue is being widely reported in the Lenovo and Samsung communities, and it's always after a power-down restart that the issue occurs. With the Moto G5 series of phones, it's not so obvious that it's an Android 7.0 fault, but it's clear in the Samsung community - phone/SD card combinations work fine until they upgrade from the starting Android 6 to Android 7.
>>
>> Hopefully, the Android developer community will acknowledge the issue soon and fix it - after all, it shouldn't be too hard to find by tracking back through the code commits and finding any that relate to power-down procedures. It will be a change that was made between the final Android 6 and Android 7.0.
>
> Looks like you are right. Just had an Android update (version
> number didn't change, still 7.0) on both phones and they both
> now restart without the SD card error. No recognition that I
> could see from Motorola of the problem, or that the update should
> fix it.
I hope to get that update soon!
> number didn't change, still 7.0) on both phones and they both
> now restart without the SD card error. No recognition that I
> could see from Motorola of the problem, or that the update should
> fix it.
--
Cheers, Carlos.
Steve Hayes
Mar 3, 2018, 6:45:44 AM3/3/18
to
On Tue, 27 Feb 2018 19:03:57 +0000 (GMT+00:00), Biggles
<ne...@packaging.the-shillings.net> wrote:
>> It's an Android 7.0 problem. The issue is being widely reported in the Lenovo and Samsung communities, and it's always after a power
I have a Moto G Play with Android 6.
<ne...@packaging.the-shillings.net> wrote:
>> It's an Android 7.0 problem. The issue is being widely reported in the Lenovo and Samsung communities, and it's always after a power
I haven't had any problems with the SD card.
It keeps offering to download Android 7 -- should I therefore avoid
it?
--
Steve Hayes
http://www.khanya.org.za/stevesig.htm
http://khanya.wordpress.com
The Real Bev
Mar 3, 2018, 11:44:14 AM3/3/18
to
On 03/03/2018 03:48 AM, Steve Hayes wrote:
> On Tue, 27 Feb 2018 19:03:57 +0000 (GMT+00:00), Biggles
> <ne...@packaging.the-shillings.net> wrote:
>
>>> It's an Android 7.0 problem. The issue is being widely reported in the Lenovo and Samsung communities, and it's always after a power
>
> I have a Moto G Play with Android 6.
>
> I haven't had any problems with the SD card.
>
> It keeps offering to download Android 7 -- should I therefore avoid
> it?
Depends :-)
> On Tue, 27 Feb 2018 19:03:57 +0000 (GMT+00:00), Biggles
> <ne...@packaging.the-shillings.net> wrote:
>
>>> It's an Android 7.0 problem. The issue is being widely reported in the Lenovo and Samsung communities, and it's always after a power
>
> I have a Moto G Play with Android 6.
>
> I haven't had any problems with the SD card.
>
> It keeps offering to download Android 7 -- should I therefore avoid
> it?
The thing I find annoying about A7 is that for some reason you can't
move apps to the sdcard. I've got 64GB internal memory as well as a
64GB sdcard, but sooner or later I'm going to bump up against a wall.
OTOH, I haven't seriously investigated new apps that might do that --
the ones I already have won't.
--
Cheers, Bev
You are more likely to catch swine flu from a
police officer than from an actual pig.
Carlos E.R.
Mar 3, 2018, 1:56:09 PM3/3/18
to
On 2018-03-03 12:48, Steve Hayes wrote:
> On Tue, 27 Feb 2018 19:03:57 +0000 (GMT+00:00), Biggles
> <ne...@packaging.the-shillings.net> wrote:
>
>>> It's an Android 7.0 problem. The issue is being widely reported in the Lenovo and Samsung communities, and it's always after a power
>
> I have a Moto G Play with Android 6.
>
> I haven't had any problems with the SD card.
>
> It keeps offering to download Android 7 -- should I therefore avoid
> it?
I would hesitate.
> On Tue, 27 Feb 2018 19:03:57 +0000 (GMT+00:00), Biggles
> <ne...@packaging.the-shillings.net> wrote:
>
>>> It's an Android 7.0 problem. The issue is being widely reported in the Lenovo and Samsung communities, and it's always after a power
>
> I have a Moto G Play with Android 6.
>
> I haven't had any problems with the SD card.
>
> It keeps offering to download Android 7 -- should I therefore avoid
> it?
--
Cheers, Carlos.
0 new messages