09-03-2012 07:14 PM
Just testing my Gingerbread 2.3.6 Samsung Galaxy device and I find that Norton
Mobile Security installation corrupts my Micro SD memory card. I am using a
Windows 7 PC.
Connecting device to PC by USB with data transfer mode I now get this message
every time where I never use to get it before NMS 3.0. The Windows error message
I get is below-
Removing the memory card from the device and using an adaptor to connect
the Micro SD to a PC I still get the message.
Now I have noticed I can download NMS 3.0 without activation or opening the app
and test USB transfer mode and all is fine, at this stage the only Norton file on the
Micro SD is the .symantec_persisted file.
Then if I open the NMS 3.0 app for the first time and tap agree and start the app
that is when the issue starts. I skip sign in and go straight to the Lite version.
I close NMS 3.0 and connect the device to the PC via USB and the message comes up
straight away in data transfer mode.
Now looking at the memory card with an Explorer app I see I now have 2 more
Norton files being- (symantec_update_temp) and (.norton) .
So this issue is happening without even signing into NMS 3.0.
So I uninstall NMS 3.0 and connect again to PC via USB and I still get the message.
I remove the memory card and using the adaptor connect to the PC , still getting
the message. So I deleted all Norton files from the memory card. Still the same
message comes up when re connecting the memory card. Same thing when connecting
to PC via USB.
The only way to fix the issue and stop getting the Windows error message when
connecting to the PC is to format the memory card . This is very annoying. As I now
have to format and reload a 16 GB memory card and uninstall and stop using
Norton Mobile Security 3.0. :-(
This sounds like a serious issue that the Norton Team needs to look into.
09-04-2012 10:40 AM
Thanks for reporting this!
We would need more information on this. I am sending you a PM. Please send us the requested information to investigate this issue further.
09-04-2012 05:23 PM - edited 09-04-2012 05:25 PM
Thanks for the reply and PM.
I have been doing some more testing and i think i have found where the
issue is coming from.
The problem with the error message seems to be because of Software
related to storage devices. So this is like Andmike pointed that it might be
related to the issue that dph15 has in the thread here.
My Software that does not seem to like Norton Mobile Security 3.0 is Sony
PMB ( Sony Picture Motion Browser) it is a old version maybe a couple of
years old that i do not use anymore . So i have uninstalled Sony PMB ( And
it is very hard to fully uninstall) and NMS at the moment and will carry out a
few more tests and post back with the results soon.
09-04-2012 07:40 PM - edited 09-04-2012 07:41 PM
Certainly seems NMS 3.0 has some compatibility issues with external media storage
devices and thier software for computers.In this case it is a Sony Bloggie video camera
and it's PC software program Sony Picture Motion Browser.
And in the case of dph15 it is a compatibility issue with Sony PC Companion software
and the Sony Xperia Arc mobile phone.
With Sony PMB uninstalled from all PC's now i have no more error messages when
connecting Gingerbread Galaxy Y to the PC via USB for media transfer.
Have had no issues with ICS devices all is ok and compatible with Sony PMB it appears.
But i do not have the software program anymore, one less headache. :-)
So it appears there is a compatibility issue with Sony media device computer software
and Norton Mobile Security 3.0.
09-04-2012 08:39 PM
I haven't experienced any data corruption. On my Xperia Arc, if NS has been granted device admin privileges, and I connect the usb cable to my PC, I hear the USB connection chimes but the phone never shows up in windows explorer and the Sony software cannot find the phone.
If I revoke device admin privileges, then the phone & PC connect without difficulty. After this connection is established, I can re-enable admin status for NS and the connection does not disappear unil the usb cable is disconnected from either the phone or the PC. To reconnect the devices, I need to toggle admin off again.
With admin mode enabled, if I attempt to connect the phone to a usb port that has not been used before, windows attempts to install the appropriate drivers (as usual) but the driver installation fails. If admin mode is off, then the drivers are installed just fine.
Some way some how, NS with device admin rights is preventing the connection between the two devices. This is the only difficulty I have observed so far with NS v188.8.131.523
09-04-2012 08:54 PM - edited 09-04-2012 08:54 PM
Do you have a second PC that does not have the Sony Companion
software program installed.?
Can you try connecting your Sony device to a different computer.?
If not can you safley remove the Sony program to see if this is the issue
when your device admin with NMS 3.0 is active when connecting to your PC.?
Keep us posted. ;-)
09-04-2012 09:14 PM - edited 09-04-2012 09:14 PM
When I was experiencing the problems, PC Companion was not running. It was installed, but was and is configured not to run at system startup.
After connecting the phone and it not showing up in the list of connected devices I started PCC to see if the software could detect the phone and obviously it did not.
As I just posted in my thread, all this testing has some how fixed my particular problem. The phone is now connecting to the PC in either data transfer mode, with and without PCC running. Since I can no longer duplicate the problem (at least for now, Murphy way well return tomorrow) I am left thinking that it was a windows problem all along.
09-04-2012 09:38 PM
That is good news. :-)
Unfortunately i do not have any settings on my device to toggle between
media transfer mode and mass storage mode, USB Mass Storage only. :-(
Still my issue that i thought was linked to yours which does not seem to be,
is fixed with no Sony software installed.
One possibility for the problem i had could be a compatibility issue with a old
version of Sony PMB as i have not used or updated it for a long, long time.
Any how i will leave this one with the Norton Team to see what they come up with. :-)