WARNING to Motorola phone owners....

My Motorola Z6m slidephone had pictures on it of an aquaintenance's kids
and he wanted me to send him the pictures so he could have a copy of
them.

I don't text or SMS or MMS or any other letter combinations on my
Pageplus cellular account, so I suggested, as he had a brand new Samsung
Galaxy S in Sprint's clothes we just bluetooth the pictures to him, as we
were standing a few feet apart.

I set up my picture viewer on the Motorola to one of the pictures he
wanted and went through the menus to send it to him on Bluetooth. They
phones DID connect up on BT, but suddenly the Motorola reported an error
it had gotten from the BRAND NEW SPRINT Samsung Galaxy S Android-based
phone that the pictures couldn't be displayed as they were "NOT
COMPATIBLE" with the Samsung! ***?!...NOT COMPATIBLE?? THEY'RE JPEGS!
I sensed Sprintshit afoot. We tried it 3 times with 3 pictures....NO
TRANSFERRING ALLOWED ON BLUETOOTH, EVEN THOUGH THE PHONES WOULD CONNECT
AND HE HAD TO APPROVE THE TRANSFER. What ********! Ive sent pictures to
the simplest of BT-equipped phones, PDAs, Nokia Linux tablets, laptops
and Netbooks running WinXP or Vista or 7 or even Win98SE!

Having been thwarted by the Sprintshit installed on it, I pulled out the
microSD card (2G and he pulled out his 2GB microSD card. We simply
plugged my Motorola-formatted FAT32-based microSD card into his phone.
Bingo! He could see the pictures, nicely thumbnailed next to the file
names my MotoROKR had put on them. He found the pictures and we tried to
COPY them to his internal memory. OH OH....SPRINTSHIT AGAIN! THERE WAS
NO COPY COMMAND ON THE PICTURES! HE WASN'T ALLOWED TO COPY PICTURES FROM
THE MEMORY CARD TO THE INTERNAL MEMORY....no go, again! He was PISSED!
Pity the Sprint store tomorrow morning! He's a mean-looking trucker
type! They don't like to be told "NO" by anything or anybody!

Well, he could LOOK at the pictures and we tried to SEND them to his
wife's phone, a lesser sellphone than the Samsung beast. He clicked SEND
and we waited and we waited and we waited.....it never happened. He
could send her text messages, BUT NOT THE GD PICTURES ON MY MICROSD IN
HIS PHONE! NUTS! He HAS sent her pictures taken by his phone to her
phone, successfully, though.....

NOW THE WARNING PART FOR ALL MOTOROLA EQUIPPED PHONE OWNERS......

NEVER LET ANYONE WITH AN ANDROID PHONE PLUG YOUR MOTOROLA MEMORY CARD
INTO AN ANDROID PHONE!......

We gave up and he handed me my card back. I plugged it back into the
Motorola Z6m AND IT WOULDN'T FIND ANY OF THE PICTURES ON MY MEMORY CARD
ANY MORE! I tried everything, reboot phone, reload memory card,
everything. The Android phone didn't erase the pictures, as the Z6m
still reports most of the memory card's capacity is full of "something".
BUT, the phone will no longer display any of its own stored pictures on
my card.

Any ideas to restore them is greatly appreciated. I have copies of all
the pictures on my netbook hard drive, so they're not really lost, but
there must be some way to recover the connection between the Z6m and its
own stupid pictures in Motorola's OWN directory structure!

NUTS! GODDAMNED SELLPHONE ********!

Larry wrote:
> My Motorola Z6m slidephone had pictures on it of an aquaintenance's kids
> and he wanted me to send him the pictures so he could have a copy of
> them.
>
> I don't text or SMS or MMS or any other letter combinations on my
> Pageplus cellular account, so I suggested, as he had a brand new Samsung
> Galaxy S in Sprint's clothes we just bluetooth the pictures to him, as we
> were standing a few feet apart.
>
> I set up my picture viewer on the Motorola to one of the pictures he
> wanted and went through the menus to send it to him on Bluetooth. They
> phones DID connect up on BT, but suddenly the Motorola reported an error
> it had gotten from the BRAND NEW SPRINT Samsung Galaxy S Android-based
> phone that the pictures couldn't be displayed as they were "NOT
> COMPATIBLE" with the Samsung! ***?!...NOT COMPATIBLE?? THEY'RE JPEGS!
> I sensed Sprintshit afoot. We tried it 3 times with 3 pictures....NO
> TRANSFERRING ALLOWED ON BLUETOOTH, EVEN THOUGH THE PHONES WOULD CONNECT
> AND HE HAD TO APPROVE THE TRANSFER. What ********! Ive sent pictures to
> the simplest of BT-equipped phones, PDAs, Nokia Linux tablets, laptops
> and Netbooks running WinXP or Vista or 7 or even Win98SE!
>
> Having been thwarted by the Sprintshit installed on it, I pulled out the
> microSD card (2G and he pulled out his 2GB microSD card. We simply
> plugged my Motorola-formatted FAT32-based microSD card into his phone.
> Bingo! He could see the pictures, nicely thumbnailed next to the file
> names my MotoROKR had put on them. He found the pictures and we tried to
> COPY them to his internal memory. OH OH....SPRINTSHIT AGAIN! THERE WAS
> NO COPY COMMAND ON THE PICTURES! HE WASN'T ALLOWED TO COPY PICTURES FROM
> THE MEMORY CARD TO THE INTERNAL MEMORY....no go, again! He was PISSED!
> Pity the Sprint store tomorrow morning! He's a mean-looking trucker
> type! They don't like to be told "NO" by anything or anybody!
>
> Well, he could LOOK at the pictures and we tried to SEND them to his
> wife's phone, a lesser sellphone than the Samsung beast. He clicked SEND
> and we waited and we waited and we waited.....it never happened. He
> could send her text messages, BUT NOT THE GD PICTURES ON MY MICROSD IN
> HIS PHONE! NUTS! He HAS sent her pictures taken by his phone to her
> phone, successfully, though.....
>
> NOW THE WARNING PART FOR ALL MOTOROLA EQUIPPED PHONE OWNERS......
>
> NEVER LET ANYONE WITH AN ANDROID PHONE PLUG YOUR MOTOROLA MEMORY CARD
> INTO AN ANDROID PHONE!......
>
> We gave up and he handed me my card back. I plugged it back into the
> Motorola Z6m AND IT WOULDN'T FIND ANY OF THE PICTURES ON MY MEMORY CARD
> ANY MORE! I tried everything, reboot phone, reload memory card,
> everything. The Android phone didn't erase the pictures, as the Z6m
> still reports most of the memory card's capacity is full of "something".
> BUT, the phone will no longer display any of its own stored pictures on
> my card.
>
> Any ideas to restore them is greatly appreciated. I have copies of all
> the pictures on my netbook hard drive, so they're not really lost, but
> there must be some way to recover the connection between the Z6m and its
> own stupid pictures in Motorola's OWN directory structure!
>
> NUTS! GODDAMNED SELLPHONE ********!
>


I recommend CardRecovery.com

Free trial available.

In article <Xns9DEFCE0831F41noonehomecom@74.209.131.13>, noone@home.com
says...


> We gave up and he handed me my card back. I plugged it back into the
> Motorola Z6m AND IT WOULDN'T FIND ANY OF THE PICTURES ON MY MEMORY CARD
> ANY MORE! I tried everything, reboot phone, reload memory card,
> everything. The Android phone didn't erase the pictures, as the Z6m
> still reports most of the memory card's capacity is full of "something".

#1: Phonescoop will generally tell you which Bluetooth profiles a phone
supports.

#2: Try plugging the card into a media reader. Try reading it on a
computer instead of a phone. The phones usually have a specific
directory structure they are looking for, and which directories are
required depends on which phone you have.

--
Steve Sobol, Apple Valley, California, USA
sjsobol@JustThe.net

On Sat, 11 Sep 2010 00:02:26 -0700, in
<MPG.26f4c95f32c7bfa2989a2c@news.justthe.net>, Steve Sobol
<sjsobol@JustThe.net> wrote:

>In article <Xns9DEFCE0831F41noonehomecom@74.209.131.13>, noone@home.com
>says...
>
>> We gave up and he handed me my card back. I plugged it back into the
>> Motorola Z6m AND IT WOULDN'T FIND ANY OF THE PICTURES ON MY MEMORY CARD
>> ANY MORE! I tried everything, reboot phone, reload memory card,
>> everything. The Android phone didn't erase the pictures, as the Z6m
>> still reports most of the memory card's capacity is full of "something".
>
>#1: Phonescoop will generally tell you which Bluetooth profiles a phone
>supports.
>
>#2: Try plugging the card into a media reader. Try reading it on a
>computer instead of a phone. The phones usually have a specific
>directory structure they are looking for, and which directories are
>required depends on which phone you have.

Good advice on both counts.

--
John

"Assumption is the mother of all screw ups."
[Wethern’s Law of Suspended Judgement]

On Sat, 11 Sep 2010 00:11:55 +0000, in alt.cellular.attws Larry
<noone@home.com> wrote:

>My Motorola Z6m slidephone had pictures on it of an aquaintenance's kids
>and he wanted me to send him the pictures so he could have a copy of
>them.

Next time, Bluetooth the pictures to your laptop and then email them
to your acquaintance. MUCH safer that way.

Also, the phone crippling that you refer to as "Sprintshit" was
actually invented by Verizon Wireless. Please give proper credit.

Steve Sobol <sjsobol@JustThe.net> wrote in
news:MPG.26f4c95f32c7bfa2989a2c@news.justthe.net:

> In article <Xns9DEFCE0831F41noonehomecom@74.209.131.13>,
> noone@home.com says...
>
>
>> We gave up and he handed me my card back. I plugged it back into the
>> Motorola Z6m AND IT WOULDN'T FIND ANY OF THE PICTURES ON MY MEMORY
>> CARD ANY MORE! I tried everything, reboot phone, reload memory card,
>> everything. The Android phone didn't erase the pictures, as the Z6m
>> still reports most of the memory card's capacity is full of
>> "something".
>
> #1: Phonescoop will generally tell you which Bluetooth profiles a
> phone supports.
>
> #2: Try plugging the card into a media reader. Try reading it on a
> computer instead of a phone. The phones usually have a specific
> directory structure they are looking for, and which directories are
> required depends on which phone you have.
>

#2 is a charm. I found the Android had added another thumbnails directory
to the root and I supposed the Motorola balked at finding something it
didn't understand. I deleted the extra directory and all was restored.

If they can't get the pictures from my bluetooth functionality, they'll
have to do without in the future.....damn it.

Robert Higgins <robert@nospam.bogus> wrote in
news:gk8n869kur8jtkhhl68dqnlbnlhutua32k@4ax.com:

> Also, the phone crippling that you refer to as "Sprintshit" was
> actually invented by Verizon Wireless. Please give proper credit.
>
>

The only carrier I ever had that didn't cripple up the phones was
Alltel.....

At 12 Sep 2010 02:19:33 +0000 Larry wrote:
> Steve Sobol <sjsobol@JustThe.net> wrote in
> news:MPG.26f4c95f32c7bfa2989a2c@news.justthe.net:
>
> > In article <Xns9DEFCE0831F41noonehomecom@74.209.131.13>,
> > noone@home.com says...
> >
> >
> >> We gave up and he handed me my card back. I plugged it back into the
> >> Motorola Z6m AND IT WOULDN'T FIND ANY OF THE PICTURES ON MY MEMORY
> >> CARD ANY MORE! I tried everything, reboot phone, reload memory card,
> >> everything. The Android phone didn't erase the pictures, as the Z6m
> >> still reports most of the memory card's capacity is full of
> >> "something".
> >
> > #1: Phonescoop will generally tell you which Bluetooth profiles a
> > phone supports.
> >
> > #2: Try plugging the card into a media reader. Try reading it on a
> > computer instead of a phone. The phones usually have a specific
> > directory structure they are looking for, and which directories are
> > required depends on which phone you have.
> >
>
> #2 is a charm. I found the Android had added another thumbnails
directory
> to the root and I supposed the Motorola balked at finding something it
> didn't understand. I deleted the extra directory and all was restored.
>
> If they can't get the pictures from my bluetooth functionality, they'll
> have to do without in the future.....damn it.


In this case, however, you should blame your Motorola rather than the
Samsung or Android. There's no good reason the Moto should be confused
by additional folders added to the card, as long as its required/self-
created file/folder structure is left intact, which it seemingly was.

Todd Allcock <elecconnec@AnoOspamL.com> wrote in news:cHXio.44794$rC7.40478
@newsfe10.iad:

> In this case, however, you should blame your Motorola rather than the
> Samsung or Android. There's no good reason the Moto should be confused
> by additional folders added to the card, as long as its required/self-
> created file/folder structure is left intact, which it seemingly was.
>
>

Right. I'm to blame for trying to be nice to someone....

At 12 Sep 2010 22:25:34 +0000 Larry wrote:
> Todd Allcock <elecconnec@AnoOspamL.com> wrote in news:cHXio.44794
$rC7.40478
> @newsfe10.iad:
>
> > In this case, however, you should blame your Motorola rather than the
> > Samsung or Android. There's no good reason the Moto should be
confused
> > by additional folders added to the card, as long as its required/self-
> > created file/folder structure is left intact, which it seemingly was.
> >
> >
>
> Right. I'm to blame for trying to be nice to someone....


I'm not picking on you- there's nothing wrong with the warning- but your
posts clearly blamed "Sprintshit," Samsung or Android, while espousing
the virtues of Alltel who was the only provider you've used that doesn't
cripple phones, etc., but in this instance, your phone seems to be to the
culprit, since it seemed to be "confused" by the addition of any storage
card folders it doesn't create itself.

Your warning probably needs to be amended to not sticking a Z6's storage
card in ANY other phone- not just Androids!