[Samsung Gear S] biktor_gj:
It's the same issue as [MENTION=3700808]deadlocked007[/MENTION] 's, there's a file with the wrong permissions in the framework directory that makes the Package Manager fail, look at my previous post and you'll fix it in no time ;)

Now about the modem, here's what I got so far:

1. Android boots

2. If the modem firmware isn't found, it doesn't attempt to boot it --> the watchdog timer that keeps it in sync doesn't start --> the watch stays up

2b. If the modem firmware is found -> boots the baseband --> watchdog timer starts --> QMI interface isn't bringed up --> modem watchdog eventually calls a reset and the watch reboots

There are a few device nodes in sysfs that don't exist in this kernel. I don't know if it's because this modem doesn't have them, or if it was some deliberate work by Samsung because they didn't use them in Tizen. Either way, the logs:

D/RIL-QMI ( 220): switch user for CTS
E/RIL-QMI ( 220): qmuxd: linux_qmi_read_sysfs_config: couldn't open file /sys/module/f_rmnet/parameters/rmnet_ctl_ch
E/RIL-QMI ( 220): qmuxd: linux_qmi_read_sysfs_config: couldn't open /sys/module/rmnet/parameters/rmnet_ctl_ch
D/RIL-QMI ( 220): linux_qmi_qmux_if_configure_port_timeout: mode=0, smd_timeout=20, hsic_timeout=60
E/RIL-QMI ( 220): linux_qmi_qmux_if_configure_port_timeout: failed to open HSIC timeout config=/sys/devices/virtual/hsicctl/hsicctl0/modem_wait errno [2:No such file or directory]
E/RILD ( 213): First Ril
E/RILD ( 213): LoadLogLevel: Log level is 3.
E/RILD ( 213): RIL_Init: version(7)
E/RILC ( 213): RIL_register: RIL version 7
E/RILD ( 213): LazyRilInit
E/RILD ( 213): SecRil(): ModelType: 1
E/RILD ( 213): Modem config #0: index[0], iftype[10], ifname[rmnet0], mtype[4], proto[10], protover[10], dbg-ifname[]
E/RILD ( 213): Force-exit is required for this thread
E/RILD ( 213): Modem config #1: index[1], iftype[10], ifname[rmnet0], mtype[32], proto[1], protover[1], dbg-ifname[]
E/RILD ( 213): Debug channel is not opened for ship build.
E/RILD ( 213): Force-exit is required for this thread
E/RILD ( 213): Trying qmi_init(): retryCount(0)
E/RIL-QMI ( 213): qmi_client [213]: unable to connect to server, errno=[2:No such file or directory], attempt=1
E/RIL-QMI ( 226): qmi_client [226]: unable to bind to client socket, rc = -1 errno[13:Permission denied]
E/RIL-QMI ( 226): qmi_qmux_if_pwr_up_init_ex: Initialization failed, rc = -1
E/RIL-QMI ( 221): qmi_client [221]: unable to connect to server, errno=[2:No such file or directory], attempt=1
E/RIL-QMI ( 226): qmi_client [226]: unable to bind to client socket, rc = -1 errno[13:Permission denied]
E/RIL-QMI ( 226): qmi_qmux_if_pwr_up_init_ex: Initialization failed, rc = -1
E/RIL-QMI ( 226): qmi_client [226]: unable to bind to client socket, rc = -1 errno[13:Permission denied]
E/RIL-QMI ( 226): qmi_qmux_if_pwr_up_init_ex: Initialization failed, rc = -1
E/RIL-QMI ( 226): qmi_client [226]: unable to bind to client socket, rc = -1 errno[13:Permission denied]
E/RIL-QMI ( 226): qmi_qmux_if_pwr_up_init_ex: Initialization failed, rc = -1
E/RIL-QMI ( 226): qmi_client [226]: unable to bind to client socket, rc = -1 errno[13:Permission denied]
E/RIL-QMI ( 226): qmi_qmux_if_pwr_up_init_ex: Initialization failed, rc = -1
E/RIL-QMI ( 226): qmi_client [226]: unable to bind to client socket, rc = -1 errno[13:Permission denied]
E/RIL-QMI ( 226): qmi_qmux_if_pwr_up_init_ex: Initialization failed, rc = -1
E/RIL-QMI ( 213): qmi_client [213]: unable to connect to server, errno=[2:No such file or directory], attempt=2
E/RIL-QMI ( 221): qmi_client [221]: unable to connect to server, errno=[2:No such file or directory], attempt=2
E/RIL-QMI ( 213): qmi_client [213]: unable to connect to server, errno=[2:No such file or directory], attempt=3

I don't know what else is looking for, but the devices:

/sys/module/f_rmnet/parameters/rmnet_ctl_ch

/sys/module/rmnet/parameters/rmnet_ctl_ch

/sys/devices/virtual/hsicctl/hsicctl0/modem_wait

Are definitely not there. The first two seem like the USB bridge drivers by their names, but the third one, from what I could find, belong to Qualcomm's HSIC driver (internal USB controller for directly attached peripherals from the CPU).

The rest of the devices seem to be there (/dev/smd*, /dev/smdcntl*) but those sysfs devices and /dev/hsicctl* aren't.

Then, after 20 seconds from the bootup, the watch resets due to the modem timeout and we begin again.

In case you're seeing something I don't, netcfg does show up the rmnet devices that should be there for interface level communication (!=driver level)

rmnet1 DOWN 0.0.0.0/0 0x00001002 0a:39:c8:30:27:eb

rmnet0 DOWN 0.0.0.0/0 0x00001002 7a:5c:74:22:95:83

rmnet4 DOWN 0.0.0.0/0 0x00001002 ca:d5:88:cf:6c:10

rmnet3 DOWN 0.0.0.0/0 0x00001002 be:34:35:33:47:3c

rmnet2 DOWN 0.0.0.0/0 0x00001002 5a:54:06:11:f2:9d

rmnet7 DOWN 0.0.0.0/0 0x00001002 52:79:2e:03:de:3d

rmnet6 DOWN 0.0.0.0/0 0x00001002 3e:20:90:de:75:4e

rmnet5 DOWN 0.0.0.0/0 0x00001002 a6:0e:c7:d0:a4:7a

rev_rmnet4 DOWN 0.0.0.0/0 0x00001002 82:b6:53:bf:7c:a5

rev_rmnet3 DOWN 0.0.0.0/0 0x00001002 7e:1e:fa:a4:80:67

rev_rmnet2 DOWN 0.0.0.0/0 0x00001002 3a:d4:95:a9:a4:c5

rev_rmnet7 DOWN 0.0.0.0/0 0x00001002 fa:fb:47:72:85:63

rev_rmnet6 DOWN 0.0.0.0/0 0x00001002 e6:56:49:47:20:da

rev_rmnet5 DOWN 0.0.0.0/0 0x00001002 a2:6f:5b:83:b4:24

rev_rmnet8 DOWN 0.0.0.0/0 0x00001002 82:ef:50:9b:8f:e0

rev_rmnet1 DOWN 0.0.0.0/0 0x00001002 fe:44:ad:4c:b2:82

rev_rmnet0 DOWN 0.0.0.0/0 0x00001002 9e:2a:ec:77:99:c4

wlan0 DOWN 0.0.0.0/0 0x00001002 00:90:4c:94:fa:7f

rmnet_usb0 DOWN 0.0.0.0/0 0x00001002 aa:37:74:8f:da:98

lo UP 127.0.0.1/8 0x00000049 00:00:00:00:00:00

sit0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00

p2p0 DOWN 0.0.0.0/0 0x00001002 00:90:4c:33:22:11

dummy0 DOWN 0.0.0.0/0 0x00000082 f6:ac:10:a4:b4:dd