Sign in with
Sign up | Sign in
Your question
Closed

Problems galaxy s 4g in Opensuse 12.1

Last response: in Linux/Free BSD
Share
December 15, 2011 8:41:09 PM

First off loving the new opensuse, I see why people keep going on about kde. I've managed to figure out how to solve every other issue i was having from unresponsive volume control to the gfx driver installation. But I have a problem remaining with getting my phone detected in usb mode. Every other device I normally use with linux os have no problems being detected. Could there be some type of driver needed?
December 16, 2011 4:11:34 AM

Looking at the situation more it seems like there's a problem with viewing the actual folder. It immediately disconnects when trying to do so.
Score
0
December 16, 2011 10:58:03 AM

Dec 16 06:53:37 FabulaNovaCrystallis udevd[7591]: timeout: killing '/sbin/blkid -o udev -p /dev/sde' [7655]
Dec 16 06:53:38 FabulaNovaCrystallis udevd[7591]: timeout: killing '/sbin/blkid -o udev -p /dev/sde' [7655]
Dec 16 06:53:39 FabulaNovaCrystallis udevd[7591]: timeout: killing '/sbin/blkid -o udev -p /dev/sde' [7655]
Dec 16 06:53:40 FabulaNovaCrystallis udevd[7591]: timeout: killing '/sbin/blkid -o udev -p /dev/sde' [7655]
Dec 16 06:53:41 FabulaNovaCrystallis udevd[7591]: timeout: killing '/sbin/blkid -o udev -p /dev/sde' [7655]
Dec 16 06:53:42 FabulaNovaCrystallis udevd[7591]: timeout: killing '/sbin/blkid -o udev -p /dev/sde' [7655]
Dec 16 06:53:43 FabulaNovaCrystallis udevd[7591]: timeout: killing '/sbin/blkid -o udev -p /dev/sde' [7655]
Dec 16 06:53:44 FabulaNovaCrystallis udevd[7591]: timeout: killing '/sbin/blkid -o udev -p /dev/sde' [7655]
Dec 16 06:53:45 FabulaNovaCrystallis udevd[7591]: timeout: killing '/sbin/blkid -o udev -p /dev/sde' [7655]
Dec 16 06:53:46 FabulaNovaCrystallis udevd[7591]: timeout: killing '/sbin/blkid -o udev -p /dev/sde' [7655]

guess this confirms my thoughts.
Score
0
Related resources
December 16, 2011 2:15:41 PM

I went ahead and changed back to fedora 15... For some odd reason when looking into it further my phone is owned by root... Currently looking into to how to permanently change that back.
Score
0
December 16, 2011 2:58:34 PM

Ok this is just weird now. I change the permissions and plugged it back in. Now it says that the media is unreadable. The device still acts normally though.
Score
0

Best solution

December 27, 2011 1:53:55 PM

All of the Android devices that I've played with will have applications running as root (and therefore, if the underlying FS supports it, the files are owned by root as well). POSIX systems will honor user designations from other remote systems (in this case, the phone's designations from Android itself). All POSIX systems that have the idea of a "root" user designate the UID 0 to root, hence there is some level of security that travels with the file no matter where it goes.

I have a feeling, however, that is a fun aside from the issue you're seeing (since these devices are meant to plug into any machine and be accessible, methinks what's being mounted is FAT32), in which case it's some issue with the automounting support that's built into the version of Fedora you're using. I'd start by barking up that tree and see if someone else has run into a similar problem (FAT32 partition of an Android auto-mounted by Fedora in a way that's preventing access by Joe Linuxuser) and, more importantly, what solution they've come across. I mean I could offer a solution that'll work on any Linux out there, but it's neither pretty nor permanent.
Share
December 28, 2011 1:40:21 AM

bmouring said:
All of the Android devices that I've played with will have applications running as root (and therefore, if the underlying FS supports it, the files are owned by root as well). POSIX systems will honor user designations from other remote systems (in this case, the phone's designations from Android itself). All POSIX systems that have the idea of a "root" user designate the UID 0 to root, hence there is some level of security that travels with the file no matter where it goes.

I have a feeling, however, that is a fun aside from the issue you're seeing (since these devices are meant to plug into any machine and be accessible, methinks what's being mounted is FAT32), in which case it's some issue with the automounting support that's built into the version of Fedora you're using. I'd start by barking up that tree and see if someone else has run into a similar problem (FAT32 partition of an Android auto-mounted by Fedora in a way that's preventing access by Joe Linuxuser) and, more importantly, what solution they've come across. I mean I could offer a solution that'll work on any Linux out there, but it's neither pretty nor permanent.


As always a helpful response. The card in the phone(expanded memory card) is fat32. I'm too much of a coward to actually mess with my phone like that since there's so much important stuff on it(which doesn't make sense since I'm making a backup). What I did do however was install first reinstall fedora 15, everything worked perfectly. Couldn't get use to gnome 3 and fedora 15's kde was overly buggy so I installed fedora 14 back on, everything worked flawlessly. Realizing I need something that is still getting support I installed opensuse 11.x, no problems whatsoever from the device. Under opensuse 12.1 and the first fedora 15 install I did notice that when trying to mount the device whenever suse force quit the mounting then later re-mounted the device, I found that older version of the device were still mounted. I don't know, maybe it was a problem with that version of suse. Thanks for the suggestion bmouring, if I get a new phone(which I probably will later on) I'll reformat the disk. Of course I'll back it up first :D 
Score
0
February 10, 2012 12:06:12 PM

Best answer selected by Fenrir190.
Score
0
February 10, 2012 6:46:58 PM

This topic has been closed by Amdfangirl
Score
0
!