Samsung Galaxy S, PDA:JPA/PHONE:JPP/CSC:JP7 (VDI)
Windows 7 Ultimate (32bit)
Fedora 14 (32bit) [no Kies]
I tried to raise the same issue with both Vodafone (Ireland) and Samsung. Haha... Those people who replied have not clue what I was talking about. Both companies asked me to send the mobile to them
Basically lammers. I asked them to pass this to their developers, but they also does not understand the word "escalation"
I do not believe Samsung developers do not read those posts. That would prove their lack of interest.
I tried to troubleshoot the issue a little bit myself, but not great results. I believe the issue is somewhere in between the Kies drivers and contacts database.
Phone after a fresh restart.
Settings > Wireless and Network > USB settings > Ask on connection
After few connections with PC:
1. Phone switches to and displays Car mode in Notifications area.
2. Screen turns to landscape.
3. Kies does not connect and Windows does not see the phone storage.
Settings > Wireless and Network > USB settings > Mass storage
After few connections with PC eventually you can get "USB mass storage" prompt on the phone and phone storage will apear and can be mounted.
Changed back to Settings > Wireless and Network > USB settings > Ask on connection
After connecting a USB cable got "Select USB mode".
Selected Samsung Kies. Kies lanuched and got MTP Application Connected on the phone.
Phone appeared eventually and connected in Kies.
Clicked contacts and got nothing, but noticed Windows Auto-run window. Changed all the options for GT-I9000 to "No action" and closed the promped.
Now in contacts I get "No response from the device..." error message. Clicked OK. Contacts in Kies stay blank.
From Kies also:
Tried to export Contacts and got "Device not responding" error.
Tried to export Schedule and got "Device not responding" error.
Tried to export Memo and got "There is not Memo available to transfer" message.
Tried to backup Contacts and got the error and blank Contacts page again.
"An unexpected error prevented the data from backijng up" when tried to backup with Kies.
When trying to connect in Fedora 14 as a USB mass storage I got this:
[ 383.229028] usb 4-1: new low speed USB device using uhci_hcd and address 2
[ 383.292075] hub 4-0:1.0: unable to enumerate USB device on port 1
[ 385.357029] usb 4-1: new low speed USB device using uhci_hcd and address 3
[ 385.419086] hub 4-0:1.0: unable to enumerate USB device on port 1
[ 386.456029] usb 4-1: new low speed USB device using uhci_hcd and address 4
[ 386.518064] hub 4-0:1.0: unable to enumerate USB device on port 1
[ 388.371034] usb 1-5: new high speed USB device using ehci_hcd and address 8
[ 388.485939] usb 1-5: New USB device found, idVendor=04e8, idProduct=681d
[ 388.485945] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 388.485950] usb 1-5: Product: SAMSUNG_Android
[ 388.485953] usb 1-5: Manufacturer: SAMSUNG
[ 388.485957] usb 1-5: SerialNumber: 1000ccb884cd
[ 388.598562] Initializing USB Mass Storage driver...
[ 388.600599] scsi4 : usb-storage 1-5:2.0
[ 388.600827] usbcore: registered new interface driver usb-storage
[ 388.600833] USB Mass Storage support registered.
[ 389.606354] scsi 4:0:0:0: CD-ROM Android UMS CD-ROM 00 PQ: 0 ANSI: 2
[ 389.607215] scsi 4:0:0:1: Direct-Access SAMSUNG GT-I9000 0000 PQ: 0 ANSI: 2
[ 389.608119] scsi 4:0:0:2: Direct-Access SAMSUNG GT-I9000 Card PQ: 0 ANSI: 2
[ 389.614956] sr1: scsi3-mmc drive: 0x/0x caddy
[ 389.617124] sr 4:0:0:0: Attached scsi CD-ROM sr1
[ 389.623734] sr 4:0:0:0: Attached scsi generic sg4 type 5
[ 389.629801] sd 4:0:0:1: Attached scsi generic sg5 type 0
[ 389.631604] sd 4:0:0:2: Attached scsi generic sg6 type 0
[ 389.647330] sd 4:0:0:1: [sdd] Attached SCSI removable disk
[ 389.656040] sd 4:0:0:2: [sde] Attached SCSI removable disk
[ 395.382511] TCP lp registered
[gescape@grendel media]$ sudo mount /dev/sdd/ /media
mount: no medium found on /dev/sdd
[gescape@grendel media]$ ls
[gescape@grendel media]$ cd ..
[gescape@grendel /]$ sudo mount /dev/sdd/ /media
mount: no medium found on /dev/sdd
[gescape@grendel /]$ sudo mount /dev/sde /media
mount: no medium found on /dev/sde
What I found online:
Froyo Update for Galaxy S Fries Internal Storage
by FABSH on DECEMBER 19, 2010 ¬∑ in ANDROID
There are reports that Samsung pulled the update to Android 2.2 ‚€œFroyo‚€Ě for the Canadian version of their Galaxy S phone (the Bell Vibrant) after reports of inaccessible internal storage after the firmware update with their official tool. Apparently Samsung is investigating the issue and has halted all distribution of Froyo updates to the Galaxy S.
Samsung pulls Froyo update for Bell's Vibrant after reports of fried internal storage -- Engadget
Samsung pulls Froyo update for Bell's Vibrant after reports of fried internal storage
By Chris Ziegler posted Dec 18th 2010 7:47PM
We have no idea why Samsung's having such a hard time delivering its overdue promised Froyo upgrades worldwide for the Galaxy S series, but it's not looking any easier for them this weekend: the only Canadian Galaxy S to get upgraded so far, Bell's Vibrant, has just had its update pulled. Seems a healthy number of users attempting the upgrade using Sammy's Kies desktop software ended up with inaccessible internal storage, which sucks for a variety of obvious reasons -- and that would be the apparent reason for the removal of the update. Here's the official statement:
"There have been intermittent issues reported during the firmware upgrade process with Kies for the Samsung Galaxy S i9000M series of phones. Samsung's development team is currently aware of this issue and working towards a solution. Accordingly, The firmware update feature, which affects the ability to upgrade to Android 2.2, is temporarily disabled until a solution is released. We apologize for the inconvenience."
Lads, sorry for a very long post, but I think people must know about the problems with Galaxy S and Android.
I am absolutely disappointed, to be honest with you. Adverts were promising the best smart on the market. After few months I truly believe it is the best crap on the market!!!
It looks to me that Samsung decided to push all the testing down to customers. Not the best way to decrease costs of design&development.
I am sure now, this is my last smart from Samsung.