summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2013-12-13Revert "Grant D-bus access to user "app""submit/tizen/20131220.013930submit/tizen/20131219.030145submit/tizen/20131217.004543accepted/tizen/mobile/20131223.191815accepted/tizen/mobile/20131218.175308accepted/tizen/ivi/20131220.020918accepted/tizen/ivi/20131219.030127accepted/tizen/ivi/20131217.185017accepted/tizen/mobileaccepted/tizen/iviZhang zhengguang1-8/+1
This reverts commit 03f4145af2d97a35de8ac5bed0688fb1000a12ea. Change-Id: I33ae7bdd71bec8bed90bb2c16a3f4a566ee8177e
2013-12-12Grant D-bus access to user "app"submit/tizen/20131212.062347accepted/tizen/mobile/20131216.220249Zhang zhengguang1-1/+8
Bug Fixing: TIVI-2270 Change-Id: I0307fce1268b7c57b6f84d6d1c5e2efe1424c2f3 Signed-off-by: Zhang zhengguang <zhengguang.zhang@intel.com>
2013-11-29Bug fixing TIVI-2106: wifi/bluetooth enable/disable issuesubmit/tizen/20131129.083938accepted/tizen/20131205.214625accepted/tizen/20131202.210836Zhang zhengguang2-5/+5
Root cause: When rfkill is disabled, it didn't handle correctly in old code, which leads to rfkill logic error. Change-Id: I176888f0c00eb4968d0d27aea06853970230119c Signed-off-by: Zhang zhengguang <zhengguang.zhang@intel.com>
2013-11-21Fix bluetooth enable fail issue for bluez 5.xsubmit/tizen/20131122.011455accepted/tizen/20131122.203502Zhang zhengguang1-7/+2
Root cause: When ConnMan tries to enable bluetooth technology, firstly it will send RFkill unblock event to kernel, then call dbus method to enable bluetooth device. When bluez receives the RFkill event, it will power on the device immediately, and sends PropertyChanged message to ConnMan. In ConnMan, the device powered state is updated in device enable dbus reply callback function, but ConnMan receives PropertyChanged message before device enable dbus reply, and in current ConnMan bluetooth plugin for Bluez 5.x, when handling PropertyChanged message, it finds the adapter state(enabled) is different with the device state ConnMan stores(disabled), it will disable the bluetooth device. Solution: In ConnMan bluetooth plugin for Bluez 5.x, When ConnMan finds the adapter state is different with the device state ConnMan stores, update device state in ConnMan to the adapter state. Change-Id: Iaba867daf228ce785d71b6e5358ec3f26ccac425 Signed-off-by: Zhang zhengguang <zhengguang.zhang@intel.com>
2013-11-01Upstream/rtnl: Do not remember interface namesubmit/tizen/20131101.022911accepted/tizen/20131112.015054accepted/tizen/20131105.192326accepted/tizen/20131101.181611Jukka Rissanen1-12/+12
Use always the interface index and only when interface name is needed, then fetch the name. This minimizes races when interface name changes because of udev rules. Upstream commit Id: bcb7f23f1e9afb2cf8f27368f9da418b49db9adc Change-Id: I5f128f2d7c118ec90381388dc313b91ff4e4c8f9 Signed-off-by: Chengyi Zhao <chengyi1.zhao@archermind.com>
2013-11-01Upstream/technology: Do not use interface name when adding interfaceJukka Rissanen3-4/+9
Use always the interface index and only when interface name is needed, then fetch the name. This minimizes races when interface name changes because of udev rules. Upstream commit Id: 8c7e5d046ff2dbc7d969b097d74b9897b725e08d Change-Id: Ie32e6e8d8896167caa7caaeb784c8f974c455a6e Signed-off-by: Chengyi Zhao <chengyi1.zhao@archermind.com>
2013-11-01Upstream/technology: Do not use interface name when removing interfaceJukka Rissanen3-3/+6
Use always the interface index and only when interface name is needed, then fetch the name. This minimizes races when interface name changes because of udev rules. Upstream commit Id: 168b6d8db09d348e82399a68ec4a94b62fd2f54f Change-Id: Ia5059189372260196751f879156175db9f28c4c7 Signed-off-by: Chengyi Zhao <chengyi1.zhao@archermind.com>
2013-10-31Upstream/rtnl: Set service type to unknown if interface can not be foundChengyi Zhao1-1/+4
If the system can't find the related network interface in /sys/class/net/, ConnMan will set the interface type to "unknown". Upstream commit Id: d06050d3ad668b0ba67b33869d7a4a281c300e0f Change-Id: I417c7eafd0b000fd6d42f9be07fd78ed34aeac86 Signed-off-by: Chengyi Zhao <chengyi1.zhao@archermind.com>
2013-10-28Tethering: Remove USB interface from NetworkInterfaceBlacklistguoqiang.liu1-1/+1
Change-Id: If731fad9c7caa27d8d71ca042cb9c0de1f4a77b4
2013-10-28Tethering: Get the client mac info of Gadget tetherguoqiang.liu1-0/+83
Change-Id: Icfa6cd683c659e6728060d6201b90109c63fe56d
2013-10-28Tethering: Add gadget device rtnl handlerguoqiang.liu1-0/+43
The technology will not power on despite gadget interface is up, add rtnl handler to fix it. Change-Id: I25409db8793fd79c1e6b1248a7d919701890ed4d
2013-10-28Tethering: Watch the connection and disconnection signal of BluetoothChengyi Zhao1-3/+72
Signed-off-by: Chengyi Zhao <chengyix.zhao@intel.com> Change-Id: I38bb9b799c3e4c4c25acd9d264a4225bf59401dc
2013-10-28Tethering/Upstream: readme: USB gadget tethering kernel options addedJukka Rissanen1-0/+6
Upstream commit Id: 3cf33b786c1302b2aced9ac7a768a5c6136871f0 Change-Id: I98751dc2e4b049791787fac3b92bcafdf3840653
2013-10-28Tethering/Upstream: ethernet: Create USB gadget device driverJukka Rissanen1-0/+39
We need to create the device driver for USB gadget device, otherwise the Gadget technology will not be created correctly. Upstream commit Id: be294f9dd48b896d0e404a4a203252f088ff452b Change-Id: Ifa21d2bc9641e6eb24f2417a78d35f8b68d26bcb
2013-10-28Tethering/Upstream: technology: Return error if no devices can be found for ↵Jukka Rissanen1-1/+1
a technology Instead of returning 0 (Success) when there are no devices for a given technology, return ENXIO so that caller can inform user about the issue. Upstream commit Id: ad79c1acbd86cf64fbc0b864aefcd537bbebabf8 Change-Id: I5b6e869cf543a7be06411b90069de759a2386ad8
2013-10-28Tethering/Upstream: technology: Technology must have a name when saving its dataJukka Rissanen1-2/+6
It is no use saving the technology if the name is missing as the group name in settings file would be NULL in that case. Upstream commit Id: 339f05f38f2dd769fe04912ea157323298a0d091 Change-Id: I9abc95441fd5069e70b548888f6deceb5ab269c6
2013-10-28Tethering/Upstream: technology: USB gadget technology type had no nameJukka Rissanen1-1/+2
Having no name meant that the entries in settings file had NULL group name which is bad. Upstream commit Id: 9d1fbfe3c079d81a6068df60682ecd6d04d8511d Change-Id: I27dce5ac46c9ea5ce2faa2c7a034f486f9961cc4
2013-10-22packaging: Disable rfkill build configsubmit/tizen/20131023.012643accepted/tizen/20131023.170941Arron Wang1-0/+1
Change-Id: I5e5c699bd5d0e919c04ce7940d0d9c9c07364a13
2013-10-22Tizen: Add option to disable rfkill operationArron Wang2-0/+11
In Tizen, bluetooth enable/disable operation is handled by bluetooth framework, if the device is rfkilled, bt frwk may failed to work Change-Id: Ifcd06f322c7064125ea0840f3d01a653e7f32194
2013-08-15technology: Do not send any rfkill to kernel after receiving onesubmit/tizen_ivi_release/20131120.032027submit/tizen_ivi_genivi/20140131.015912submit/tizen/20130912.075641submit/tizen/20130815.011956ivi_oct_m2accepted/tizen_ivi_release/20131120.050253accepted/tizen/ivi/genivi/20140131.020206accepted/tizen/20130912.093500accepted/tizen/20130912.085336accepted/tizen/20130912.082351tizen_ivi_releasetizen_ivi_geniviJukka Rissanen1-37/+6
If we receive rfkill event from kernel, we must not send it back blindly. This could cause a ping-pong effect where the technology is switched on/off constantly. Upstream commit id:7a2d00e0bfe99cc327f78b9841bd8aca9efa2877
2013-08-15technology: Check hardblock when returning from offline modeJukka Rissanen1-0/+3
If we are hardblocked, then we must not enable the technology when we are returning from offline mode. Upstream commit id:10ce0a87d558b77bed2961c2933918f46c1a0dee
2013-08-15gsupplicant: Only add interface when wpa_supplicant is in ready stateJukka Rissanen1-1/+3
I noticed following scenario: - hardblock the device - turn on offline mode - turn off hardblock, as offline mode is still on connman will set softblock on - wpa_supplicant generated these state signals in this order: 1. INACTIVE 2. DISABLED - wifi.c cannot handle these events because the wifi pointer is NULL at this point - gsupplicant will then call wifi.c:interface_added(), this will cause the scanning to start but that will fail because we are still in softblocked state (wpa_supplicant returns error) - wifi.c goes now to forever loop i.e., it tries to start scan constantly. Only way to recover is to unblock wifi by turning offline mode off. The fix to this issue is simple, if the interface is not yet ready then gsupplicant will not call wifi.c:interface_added() callback as that is useless anyway. Upstream commit id:70445458847721186622677e2810febbf2f2f454
2013-08-14technology: Offlinemode could not be disabled if no technology was poweredJukka Rissanen1-5/+9
If all the technologies were powered off, then offline mode could not be disabled. Fixes BMC#26018 Upstream commit id:b4f0e902a111e29451ff604bb00795363d0093aa
2013-08-13Fix the issue TIVI-1426:submit/tizen/20130813.015237Chengyi Zhao1-1/+1
[3.0] connman-test/simple-agent needs pygobject
2013-08-09Start ntp service after connmansubmit/tizen/20130812.012612Jean-Benoit MARTIN1-1/+2
Change-Id: I1dd9521e358c2b85da0cb1fb104265aa0b14184c Bug-Tizen: TZPC-4242
2013-08-09Fix TIVI-1449:[3.0] Fail to surf internetsubmit/tizen/20130809.033909Chengyi Zhao1-0/+1
through wifi tethering connection Add iptables dependency
2013-08-09Upstream/technology: Follow external rfkill events and act accordinglyJukka Rissanen1-6/+27
Fix bug: CM-645 Fix bug: TIVI-1044 Upstream commit id: 48dbff35d34257dc7055a35aae2a19ed0a06825b
2013-08-09Upstream/technology: Check offline mode separately when rfkill device is addedJukka Rissanen1-3/+4
Upstream commit id: c3c35b8842b24546b0424ca1d83ca919ffd2427c
2013-08-09Upstream/technology: Do not activate technology if returning fromJukka Rissanen1-0/+3
hardblock while in offline mode Upstream commit id: f2a958c7ed02d5ea5b83422ae12e8edd7f7481d1
2013-08-09Upstream/technology: Print information when technogy is switched onJukka Rissanen1-1/+3
Upstream commit id: 5378ab988795358855e76f5dfce71907e0346110
2013-08-07TNCD-3: Remove the global ConnMan settings filePatrick McCarty2-19/+0
The ConnMan settings file should reflect requirements for each vertical, and it would be better to ship a custom settings file per vertical. Also, some verticals may want the ConnMan default settings, which is not possible if the connman package installs a settings file overriding the ConnMan defaults. Change-Id: I111da3c223dac23f35d53a16da55391b34d05bfc
2013-08-07Revert manifest to default floorPatrick McCarty1-9/+3
In commit 6f8eff092409c87722f8447f5157a42c6b750b08, the packaging manifest was modified to define the "connman" domain, etc. This was fixed in the previous commit, but it should be using the default floor manifest instead. Change-Id: I90859240509b3dcfbd2a7607b0ded613cca8e618
2013-08-06Bug fixing IVI-1526: Fail to zypper install connman-testsubmit/tizen/20130806.052151Zhang zhengguang1-7/+1
Signed-off-by: Zhang zhengguang <zhengguang.zhang@intel.com>
2013-08-06Update connman standard groupsubmit/tizen/20130806.030102Zhang zhengguang1-1/+1
2013-08-05Add build and configure filesubmit/tizen/20130805.055949Zhang zhengguang5-5/+61
2013-08-05Tethering: Add tethering interfaces description to technology-api.txtsubmit/tizen/20130805.054220Chengyi Zhao1-0/+12
2013-07-26Tethering: Optimize the interface between connman and mobileap-agentChengyi Zhao2-28/+19
2013-07-18Tethering: Add tethering feature support in config fileChengyi Zhao1-1/+1
2013-07-18Tethering: Add test script of open and hidden APChengyi Zhao1-7/+27
2013-07-18Tethering: Add hidden access point support in technologyChengyi Zhao9-9/+60
2013-07-18Tethering: Add open access point support in technologyChengyi Zhao1-15/+18
2013-07-18Tethering: Notify listeners when station connection changesChengyi Zhao2-1/+103
2013-07-12Tethering: Add interface that save lease in DHCP informationChengyi Zhao5-66/+104
2013-07-12Tethering: Add station information management featureChengyi Zhao3-0/+105
2013-07-12Tethering: Add handling for wpa_supplicant authorized/deauthorized signalsChengyi Zhao2-0/+57
2013-07-08resetting manifest requested domain to floorsubmit/tizen/20130710.165621accepted/tizen/20130710.213944Alexandru Cornea1-0/+4
2013-07-04Make ntp, openconnect configurableAnas Nashif2-15/+24
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2013-07-04Merge changes Iea93a2e9,Ic5591d5a into tizenMartin Xu2-0/+71
* changes: Tizen: Add always on feature Tizen: Fix wifi enterprise to support SIM and AKA
2013-07-04Merge "Tizen: Integrate telephony plugin" into tizenMartin Xu4-0/+1796
2013-07-04Tizen: Add always on featureArron Wang1-0/+40
run auto connection when default service is NULL will not auto connect MMS cellular service