05-18-2010 06:36 PM
I use a FAT+ EMEA v1.45.
Had trouble with accessing the Picasa app through the link on the homescreen.
The FAT+ restarts after the first attempt, and after doing another attempt the device hangs totally.
Unplugging power will restart the device but the problem remains.
Entering the Internet menu, and accessing Picasa app that way, the gui (the user interface) is scrambled up, menus not where they suppose to be, text ontop of other choices and so on. Pressing up and left key will atleast mark the choices on the menu, and thereby making search accessable.
The serach engine seemed to work fine after that.
I tried to talk to the Seagate chat support, but a total dissapointment!!!
First of all they totally dissagreed that Picasa app comes with the FAT+ device?? and that i only had picasa on the computer.. well yeah i have it on the computer but that aint the same thing as the picasa search engine thats on the FAT+ device...
then they wanted me to update to v1.55 US Only.
I asked if i should do it since it said US ONLY, and NOT FOR EMEA devices.
They said i should so i did.
The support wasnt even intrested in seeing photos of the bugs, i mean come on, if seagate doesnt belive the customers, how can you seriously belive that the customers will belive in seagate?
The device died and wouldnt restart.
After asking the chat support again, they refferd to FAT (not +) firmware, but i didnt even try that since the support guy wasnt even intrested in hearing me out on this bug issue.
I then found the EMEA v1.45 firmware update and were able to perform some kind of recovery firmware update.
And the device worked fine... i thought.
The Picasa service started working allright, and didnt seem to be any other gui errors visible.
But then after listening for a while to an internetradiostation, i could hear the sound in the background kind of dropping off like a pulse every second.
Somekind of internetlag i first thought, but then the same sounderror occured when playing mp3s from a usbdrive attached to the FAT+ unit.
I also did a fast test by looking at a moviefile, that had a lower volume overall. about half of the soundeffect as it should perform on max volume.
And now the latest bug that i havent seen before. While watching youtube clips, the screensaver aborts everything when it starts in the middle of a clip. Returning to the home screen, rather than continue to watch the clip that it should not interrupt in the first place.
Now i wonder, Could this be known bugs or is there a hardware failure on this device that makes these errors pop up here and there?
The unit itself is just about 3 days old for me but im not givving up on seagate yet
Could it be some kind of internal memory error making the firmware code go crazy and flip out from time to time and not use the resources as it should?
05-18-2010 11:09 PM
Sorry to hear about your support problems, that's what happens when you have someone on the other end that knows nothing about the device that they are giving support for and are just reading from a book.
Anyhow, I know that this may seem redundant, but you may want to try and re-flash the firmware again with a fresh firmware download. I have had similar problems, where the install of the firmware went wrong somewhere and things that were supposed to work, didn't. Re-flashing the firmware usually corrected the problem, although I have had to re-flash more than once, because even after re-flashing a new problem would show it's ugly face.
05-19-2010 05:13 AM
The support people needs to listen to the customers even though reading from the book. I know more about the product after a couple of hours use with a simple interface. I know they have support for all seagate devices but if they cant provide good support, that leaves the customer in a very negative situation.
Anyhow i think i have reflashed the device 5-6 times now, going from automatic update to doing cold-restart-updates via USB.
And actually new errors occur now, the 2 latest updates, the device hangs during indexing of the same usb drives that were in use before.
But what makes the device buggy? this has to be a case of hardware error since different errors occur after flashing it. Perhaps memoryhandling, or even the flash memory itself. Is the flashmemoryspeed to slow for the FAT+ device, making the flash fail every time so to say?
If the same kind of error would occur each and every time i would say that its a software bug, but now its not.
I had simular problems on the pc when trying to use some different CompactFlash cards as harddrives. Some worked, and some gave errors from time to time propably due to that they were to slow or had a cheap component setup.