Related
Anyone else having a problem on Sprint with Wifi Teather connecting to PPTP VPNs? After I teather I cannot seem to get on a VPN I can connect to from my DSL modem fine. No clue how to even begin to start troubleshooting...
TrevE said:
Anyone else having a problem on Sprint with Wifi Teather connecting to PPTP VPNs? After I teather I cannot seem to get on a VPN I can connect to from my DSL modem fine. No clue how to even begin to start troubleshooting...
Click to expand...
Click to collapse
So meaning you are connecting to a vpn from your laptop. When you are at home and on your home wireless you can connect to the vpn just fine, but when you are using the wireless provided by wifi tether on your phone it won't connect?
I'm almost certain that is probably caused by your vpn software not allowing a connection to an ad-hoc network which is what wifi tether creates. It's considered insecure because it's a lot easier for someone to spoof/do a man-in-the-middle attack.
flipzmode said:
So meaning you are connecting to a vpn from your laptop. When you are at home and on your home wireless you can connect to the vpn just fine, but when you are using the wireless provided by wifi tether on your phone it won't connect?
I'm almost certain that is probably caused by your vpn software not allowing a connection to an ad-hoc network which is what wifi tether creates. It's considered insecure because it's a lot easier for someone to spoof/do a man-in-the-middle attack.
Click to expand...
Click to collapse
wow thanks for the quick response. Exactly, I am using a laptop on my home DSL using DD-WRT for wireless & it connects to VPN fine. When I switch over to wifi teather running on sprint & try connecting and it gets to verifying username and password and then throws error 619: A connection to the remote computer could not be established, so the port used for this connection was closed.
I am using the built-in MS PPTP client so I guess I could see about the adhoc network, ill google around and see if I can find another client to test.
this has to do with GRE (a protocol that is used in pptp) not being enabled in your dsl router. i have fios and had to enable the protocol in my fios router to get pptp to work. i also had to enable port 1723. forwarding the port is not enough, in most cases. im not sure what wifi tether enables in iptables on the phone but you may need to edit iptables. see this link http://poptop.sourceforge.net/dox/gre-protocol-unavailable.phtml
cteneyck said:
this has to do with GRE (a protocol that is used in pptp) not being enabled in your dsl router. i have fios and had to enable the protocol in my fios router to get pptp to work. i also had to enable port 1723. forwarding the port is not enough, in most cases.
Click to expand...
Click to collapse
It works on my DSL fine, its when i switch over to wifi teather on Sprint then i cannot connect.
TrevE said:
It works on my DSL fine, its when i switch over to wifi teather on Sprint then i cannot connect.
Click to expand...
Click to collapse
does it work ok when your on another network, or at a friends house
cteneyck said:
...im not sure what wifi tether enables in iptables on the phone but you may need to edit iptables. see this link http://poptop.sourceforge.net/dox/gre-protocol-unavailable.phtml
Click to expand...
Click to collapse
Only reference to IPtables i can see in wifiteather is in http://android-wifi-tether.googlecode.com/svn › trunk › res › raw › tether
http://www.google.com/codesearch/p?...tether\.googlecode\.com&sa=N&cd=2&ct=rc&l=123
startipt() {
## Setting up firewall rules
run : \
"Setting up firewall rules" \
'"$iptables" -F &&
"$iptables" -F -t nat &&
"$iptables" -I FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT &&
"$iptables" -I FORWARD -s 192.168.2.0/24 -j ACCEPT &&
"$iptables" -P FORWARD DROP &&
"$iptables" -t nat -I POSTROUTING -s 192.168.2.0/24 -j MASQUERADE'
Click to expand...
Click to collapse
Not really good with iptables, dunno if thiat means anything...
try this
$su
#iptables -A INPUT -p 47 -j ACCEPT
or add that to the script
cteneyck said:
try this
$su
#iptables -A INPUT -p 47 -j ACCEPT
Click to expand...
Click to collapse
I started tethering, then i ran SUFBS. Went to terminal, did the above, went back to my laptop connected to the wifitether network, tried to connect to VPN and it still failed. Its got to be related to firewall or something like an app blocking it though right? If sprint was blocking GRE I wouldnt think it would get as far as verifying username and password(?)
The VPN box I am connecting to is a m0n0wall box. There are 6 other connections to it so I know its working.
This is a log of the connection when I try to connect using wifi tether:
http://pastebin.com/mb796e7b
Here is the logs of the connection when it works (my DSL line):
http://pastebin.com/m2a9a8313
Logs are in reverse order. what sticks out to me is it looks like when connected with wifi tether, it looks like its fails trying to negotiate protocols. I see it doing the following over and over
#Dec 10 02:06:50 mpd: [pt1] LCP: SendConfigReq ###
#Dec 10 02:06:50 mpd: ENDPOINTDISC [802.1] 00 90 27 0f 3f 64
#Dec 10 02:06:50 mpd: MP SHORTSEQ
#Dec 10 02:06:50 mpd: MP MRRU 1600
#Dec 10 02:06:50 mpd: AUTHPROTO CHAP MSOFTv2
#Dec 10 02:06:50 mpd: MAGICNUM 91ae4210
#Dec 10 02:06:50 mpd: MRU 1500
#Dec 10 02:06:50 mpd: PROTOCOMP
#Dec 10 02:06:50 mpd: ACFCOMP
#Dec 10 02:06:50 mpd: [pt1] LCP: SendConfigReq ###
On my DSL line that works it does the above step only once and then goes on starting with:
#Dec 10 02:09:36 mpd: [pt1] LCP: rec'd Configure Request #1 link 0 (Req-Sent)
#Dec 10 02:09:36 mpd: CALLBACK
#Dec 10 02:09:36 mpd: [pt1] LCP: SendConfigRej #0
#Dec 10 02:09:36 mpd: Not supported
#Dec 10 02:09:36 mpd: CALLBACK
#Dec 10 02:09:36 mpd: ACFCOMP
#Dec 10 02:09:36 mpd: PROTOCOMP
#Dec 10 02:09:36 mpd: MAGICNUM 5f561cd6
#Dec 10 02:09:36 mpd: MRU 1400
#Dec 10 02:09:36 mpd: [pt1] LCP: rec'd Configure Request #0 link 0 (Req-Sent)
TrevE said:
The VPN box I am connecting to is a m0n0wall box. There are 6 other connections to it so I know its working.
This is a log of the connection when I try to connect using wifi tether:
http://pastebin.com/mb796e7b
Here is the logs of the connection when it works (my DSL line):
http://pastebin.com/m2a9a8313
Logs are in reverse order. what sticks out to me is it looks like when connected with wifi tether, it looks like its fails trying to negotiate protocols. I see it doing the following over and over
try this also
iptables -t nat -A PREROUTING -i tiwlan0 -p tcp --dport 1723 -j DNAT --to 192.168.1.0/24
iptables -t nat -A PREROUTING -i tiwlan0 -p 47 -j DNAT --to 192.168.1.0/24
#Dec 10 02:06:50 mpd: [pt1] LCP: SendConfigReq ###
#Dec 10 02:06:50 mpd: ENDPOINTDISC [802.1] 00 90 27 0f 3f 64
#Dec 10 02:06:50 mpd: MP SHORTSEQ
#Dec 10 02:06:50 mpd: MP MRRU 1600
#Dec 10 02:06:50 mpd: AUTHPROTO CHAP MSOFTv2
#Dec 10 02:06:50 mpd: MAGICNUM 91ae4210
#Dec 10 02:06:50 mpd: MRU 1500
#Dec 10 02:06:50 mpd: PROTOCOMP
#Dec 10 02:06:50 mpd: ACFCOMP
#Dec 10 02:06:50 mpd: [pt1] LCP: SendConfigReq ###
On my DSL line that works it does the above step only once and then goes on starting with:
#Dec 10 02:09:36 mpd: [pt1] LCP: rec'd Configure Request #1 link 0 (Req-Sent)
#Dec 10 02:09:36 mpd: CALLBACK
#Dec 10 02:09:36 mpd: [pt1] LCP: SendConfigRej #0
#Dec 10 02:09:36 mpd: Not supported
#Dec 10 02:09:36 mpd: CALLBACK
#Dec 10 02:09:36 mpd: ACFCOMP
#Dec 10 02:09:36 mpd: PROTOCOMP
#Dec 10 02:09:36 mpd: MAGICNUM 5f561cd6
#Dec 10 02:09:36 mpd: MRU 1400
#Dec 10 02:09:36 mpd: [pt1] LCP: rec'd Configure Request #0 link 0 (Req-Sent)
Click to expand...
Click to collapse
If you notice in your logs that your when your are not connected via wifi tether, it will call the authentication via mschapv2
the problem is definately in the wifi tether program. its not allowing the gre protocol. i will test this this weekend and try to come up with a fix if somebody doesn't beat me to it.
you should be able to adb into your phone and run the "iptables -A INPUT -p 47 -j ACCEPT " command. and get it to work without errors.
or you could just disable the firewall by stopping iptables all together
# iptables stop (not sure on the syntax but im sure somebody will correct me)
cteneyck said:
or you could just disable the firewall by stopping iptables all together
# iptables stop (not sure on the syntax but im sure somebody will correct me)
Click to expand...
Click to collapse
Correct me if im wrong, but isn't iptables what forwards packets from the phone to the PC when your tethered? If i disable this wouldnt that stop everything?
iptables is the "firewall" of android.
Ok its working for me with no mods
Here is my setup
Server
VPN Server: Ubuntu 9.04 running pptpd
Router: Verizon Fios Router with PPTP forwarded to my server
Remote
HTC Hero (rooted running fresh 1.0 and wifi tether)
Windows XP (client)
I didn't have to modify any configurations on the phone itself and it works perfectly.
I suspect that you have firewall issues on the server side of your network.
I have verified connections from multiple locations personally now, this a company's PPTP server - i cant imagine its the server. We have stuff coming everywhere from public wifi & airports/panera to the local cable & dsl. Nobody else is having this issue, id think itd have came up somewhere by now. Im using wifi tether in the rom from - http://forum.xda-developers.com/showthread.php?t=587674 is it possible its rom related?
Wifi Tether says its version 1.60-pre3 looks like build date was october 2. Ill try jumping up to latest and greatest 1.70-pre1 even though i dont see many changes. Anywhere else I can look? Any way to turn on logging to see if the packets are being dropped?
You connection is failing with authentication (i suspect radius). I am running the same version of wifi-tether as you and it works perfectly.
Why would one connection fail with radius but it works with every other connection? Radius is everything or nothing...
Hi!
Is the Q capable of doing wifi over 5GHz ?
Accoriding to:
http://www.qualcomm.com/snapdragon/smartphones/motorola-photon-q
and
http://en.wikipedia.org/wiki/Snapdragon_(system_on_chip)#Snapdragon_S4
it should be capable of doiung so.
Is there a way to determine the exact cpu type build in? ... did a cat /proc/cpuinfo
-> Hardware is : msm8960dt
So the hardware is capable of 5Ghz Wifi. Maybe there are some antennas missing.
As far as I can tell, it isn't. When I run the INSSIDer application, it does not detect any 5 ghz channels, despite having 5 ghz channels in range.
Sucks! I have to buy a dual band router because the 2.4GHz spectrum is crowded in this apartment. I literally get a better signal from my upstairs neighbors router than i do my own.
Sent from my XT897 using Tapatalk 2
jae18708 said:
Sucks! I have to buy a dual band router because the 2.4GHz spectrum is crowded in this apartment. I literally get a better signal from my upstairs neighbors router than i do my own.
Sent from my XT897 using Tapatalk 2
Click to expand...
Click to collapse
Try changing the channel on your router.
As a matter of fact, you can use that same inssider application I mentioned to find what channels nearby wifi networks are running, and change the channel yours is operating on to avoid the interference.
Have you tried poking around in the build.prop to see if 5 GHz can be enabled? You may have to find one from an Android device that does have 5 GHz to get the proper line.
Found this @ /system/etc/firmware/wlan/prima/WCNSS_qcom_cfg.ini
Something about gEnableApProt states about n.
Hopefully someone is wiser and braver than me to know more about this file and changes which may enable 5ghz.
Code:
# This file allows user to override the factory
# defaults for the WLAN Driver
# Enable IMPS or not
gEnableImps=1
# Enable/Disable Idle Scan
gEnableIdleScan=0
# Increase sleep duration (seconds) during IMPS
# 0 implies no periodic wake up from IMPS. Periodic wakeup is
# unnecessary if Idle Scan is disabled.
gImpsModSleepTime=0
# Enable BMPS or not
gEnableBmps=1
gBmpsMinListenInterval=1
gBmpsModListenInterval=2
gBmpsMaxListenInterval=3
gPowerUsage=Max
#Telescopic Beacon skipping
gTelescopicBeaconWakeupEn=1
telescopicBeaconTransListenInterval=3
telescopicBeaconTransListenIntervalNumIdleBcns=1
telescopicBeaconMaxListenInterval=3
telescopicBeaconMaxListenIntervalNumIdleBcns=1
# Performance parameters
gEnableCloseLoop=1
gDataInactivityTimeout=120
gChannelBondingMode5GHz=1
# Enable suspend or not
# 1: Enable standby, 2: Enable Deep sleep, 3: Enable Mcast/Bcast Filter
gEnableSuspend=3
# Phy Mode (auto, b, g, n, etc)
gDot11Mode=0
# Handoff Enable(1) Disable(0)
gEnableHandoff=0
# CSR Roaming Enable(1) Disable(0)
gRoamingTime=0
# Assigned MAC Addresses - This will be used until NV items are in place
# Each byte of MAC address is represented in Hex format as XX
Intf0MacAddress=000AF58989FF
Intf1MacAddress=000AF58989FE
Intf2MacAddress=000AF58989FD
Intf3MacAddress=000AF58989FC
# UAPSD service interval for VO,VI, BE, BK traffic
UapsdMask=0
InfraUapsdVoSrvIntv=0
InfraUapsdViSrvIntv=0
InfraUapsdBeSrvIntv=0
InfraUapsdBkSrvIntv=0
# Disable RSSI FW filtering
gEnableFWRssiMonitoring=0
# Make 1x1 the default antenna configuration
gNumRxAnt=1
# Beacon filtering frequency (unit in beacon intervals)
gNthBeaconFilter=50
# Enable WAPI or not
# WAPIIsEnabled=0
# Flags to filter Mcast abd Bcast RX packets.
# Value 0: No filtering, 1: Filter all Multicast.
# 2: Filter all Broadcast. 3: Filter all Mcast abd Bcast
McastBcastFilter=0
#Flag to enable HostARPOffload feature or not
hostArpOffload=1
#SoftAP Related Parameters
# AP MAc addr
gAPMacAddr=000AF58989EF
# 802.11n Protection flag
gEnableApProt=1
#Enable OBSS protection
gEnableApOBSSProt=0
#Enable/Disable UAPSD for SoftAP
gEnableApUapsd=1
# Fixed Rate
gFixedRate=0
# Maximum Tx power
# gTxPowerCap=30
# Fragmentation Threshold
# gFragmentationThreshold=2346
# RTS threshold
RTSThreshold=2347
# Intra-BSS forward
gDisableIntraBssFwd=0
# WMM Enable/Disable
WmmIsEnabled=0
# 802.11d support
g11dSupportEnabled=1
# SAP Country code
# Default Country Code is 2 bytes, 3rd byte is optional indoor or out door.
# Example
# US Indoor, USI
# Korea Outdoor, KRO
# Japan without optional byte, JP
# France without optional byte, FR
#gAPCntryCode=USI
#Short Guard Interval Enable/disable
gShortGI20Mhz=1
gShortGI40Mhz=1
#Auto Shutdown Value in seconds. A value of 0 means Auto shutoff is disabled
gAPAutoShutOff=0
# SAP auto channel selection configuration
# 0 = disable auto channel selection
# 1 = enable auto channel selection, channel provided by supplicant will be ignored
gApAutoChannelSelection=0
# Listen Energy Detect Mode Configuration
# Valid values 0-128
# 128 means disable Energy Detect feature
# 0-9 are threshold code and 7 is recommended value from system if feature is to be enabled.
# 10-128 are reserved.
# The EDET threshold mapping is as follows in 3dB step:
# 0 = -60 dBm
# 1 = -63 dBm
# 2 = -66 dBm
# ...
# 7 = -81 dBm
# 8 = -84 dBm
# 9 = -87 dBm
# Note: Any of these settings are valid. Setting 0 would yield the highest power saving (in a noisy environment) at the cost of more range. The range impact is approximately #calculated as:
#
# Range Loss (dB) = EDET threshold level (dBm) + 97 dBm.
#
gEnablePhyAgcListenMode=128
#Preferred channel to start BT AMP AP mode (0 means, any channel)
BtAmpPreferredChannel=0
#Preferred band (both or 2.4 only or 5 only)
BandCapability=1
#Beacon Early Termination (1 = enable the BET feature, 0 = disable)
enableBeaconEarlyTermination=1
beaconEarlyTerminationWakeInterval=3
#Bluetooth Alternate Mac Phy (1 = enable the BT AMP feature, 0 = disable)
gEnableBtAmp=0
#SOFTAP Channel Range selection
gAPChannelSelectStartChannel=1
gAPChannelSelectEndChannel=11
#SOFTAP Channel Range selection Operating band
# 0:2.4GHZ 1: LOW-5GHZ 2:MID-5GHZ 3:HIGH-5GHZ 4: 4.9HZ BAND
gAPChannelSelectOperatingBand=0
#Enable Keep alive with non-zero period value
gStaKeepAlivePeriod=55
#If set will start with active scan after driver load, otherwise will start with
#passive scan to find out the domain
gEnableBypass11d=1
#If set to 0, will not scan DFS channels
gEnableDFSChnlScan=1
# Enable logp/SSR
gEnableLogp=1
# Enable Automatic Tx Power control
gEnableAutomaticTxPowerControl=1
# Priority Setting:COUNTRY IOCTL > 11d > NV default
gCountryCodePriority=1
END
# Note: Configuration parser would not read anything past the END marker
Sent from my awesome XT897
Found this :
http://www.modaco.com/topic/361678-5ghz-wifi/
Try it when i am home and in range of a 5ghz rooter.
Sent from my awesome XT897
A quick look through iwlist looks good so far
Code:
sh-4.2$ iwlist wlan0 frequency
wlan0 32 channels in total; available frequencies :
Channel 01 : 2.412 GHz
Channel 02 : 2.417 GHz
Channel 03 : 2.422 GHz
Channel 04 : 2.427 GHz
Channel 05 : 2.432 GHz
Channel 06 : 2.437 GHz
Channel 07 : 2.442 GHz
Channel 08 : 2.447 GHz
Channel 09 : 2.452 GHz
Channel 10 : 2.457 GHz
Channel 11 : 2.462 GHz
Channel 12 : 2.467 GHz
Channel 13 : 2.472 GHz
Channel 36 : 5.18 GHz
Channel 40 : 5.2 GHz
Channel 44 : 5.22 GHz
Channel 48 : 5.24 GHz
Channel 52 : 5.26 GHz
Channel 56 : 5.28 GHz
Channel 60 : 5.3 GHz
Channel 64 : 5.32 GHz
Channel 100 : 5.5 GHz
Channel 104 : 5.52 GHz
Channel 108 : 5.54 GHz
Channel 112 : 5.56 GHz
Channel 116 : 5.58 GHz
Channel 120 : 5.6 GHz
Channel 124 : 5.62 GHz
Channel 128 : 5.64 GHz
Channel 132 : 5.66 GHz
Channel 136 : 5.68 GHz
Channel 140 : 5.7 GHz
Current Channel:6
Sent from my awesome XT897
So back home but unable to see 5ghz wifi ;( don't know if i miss something to edit, or if the gui is "forcing" 2.4 ghz.
Maybe a more experienced user can hop in.
Finally answering and closing this thread.
I am now on scrillax gsm cm10.1 nightlies and able to connect to 5ghz networks.
Somehow the signalstrength is not properly shown, so it may use a stronger 2.4 Ghz channel if applicable. Forcing 5Ghz works just fine.
Gesendet von meinem XT897 mit Tapatalk 2
I wonder what is different in skrillax's ROM that enables 5GHz, and if it's something that can be applied to stock JB.
BAMF said:
I wonder what is different in skrillax's ROM that enables 5GHz, and if it's something that can be applied to stock JB.
Click to expand...
Click to collapse
Is this thread really dead?
I can't imagine that nobody is interested in getting 5GHz WiFi working...
probably it's just some regulatory settings, as there seem to be ROMS that are capable of 5GHz wifi.
Just tried CM11 nightly and CarbonROM, no luck with both.
Can't somebody experienced have a look at the configuration?
Killler07 said:
Is this thread really dead?
I can't imagine that nobody is interested in getting 5GHz WiFi working...
probably it's just some regulatory settings, as there seem to be ROMS that are capable of 5GHz wifi.
Just tried CM11 nightly and CarbonROM, no luck with both.
Can't somebody experienced have a look at the configuration?
Click to expand...
Click to collapse
See this thread:
http://forum.xda-developers.com/showthread.php?t=2671559
Hello there,
I'm having troubles with the Ouya controller on my Nvidia Shield Tablet. I've tried to play games like Portal using it, but it just spins around by itself and it's simply unplayable due to that. I've tried applying the patch in the alternative gamepads thread, but still the issue appers and I'm not sure if it's related to Android L or not.
Any idea what to do? This is the logcat:
Code:
W/bt-btif ( 6096): btif_hh_upstreams_evt: BTA_HH_OPN_EVT: handle=0, status =6
D/HidService( 6096): Connection state B8:5A:F7:C4:6B:F0: 1->0
D/BluetoothAdapterService( 6096): getAdapterService() - returning com.android.bl
[email protected]
D/BluetoothAdapterProperties( 6096): CONNECTION_STATE_CHANGE: B8:5A:F7:C4:6B:F0:
1 -> 0
I/LocalBluetoothProfileManager( 4257): Failed to connect HID device
D/CachedBluetoothDevice( 4257): onProfileStateChanged: profile HID newProfileSta
te 0
W/ActivityManager( 657): getRecentTasks: caller 10036 does not hold GET_TASKS;
limiting output
E/bt-btif ( 6096): bte_scan_filt_param_cfg_evt, 1
V/BluetoothDiscoveryReceiver( 4257): Received: android.bluetooth.adapter.action.
DISCOVERY_FINISHED
W/bt-l2cap( 6096): L2CAP got conn_comp for unknown BD_ADDR
E/bt-btm ( 6096): tBTM_SEC_DEV:0x6fe92ebc rs_disc_pending=0
W/bt-btif ( 6096): info:x0
D/ ( 6096): remote version info [b8:5a:f7:c4:6b:f0]: 5, f, 2211
I/BTConnectionReceiver( 1378): onReceive(context, Intent { act=android.bluetooth
.device.action.ACL_CONNECTED flg=0x4000010 cmp=com.google.android.googlequicksea
rchbox/com.google.android.search.core.service.BluetoothConnectionReceiver (has e
xtras) }, [BluetoothDevice: address=B8:5A:F7:C4:6B:F0, alias=null, name=OUYA Gam
e Controller, majorDeviceClass=1280, deviceClass=1284]
I/BluetoothClassifier( 1378): Bluetooth Device Name: OUYA Game Controller
W/bt-btif ( 6096): new conn_srvc id:23, app_id:5
W/bt-btif ( 6096): btif_hh_upstreams_evt: BTA_HH_OPN_EVT: handle=0, status =0
W/bt-btif ( 6096): BTA_HH_OPEN_EVT: Found device...Getting dscp info for handle
... 0
E/bt-btif ( 6096): check_cod: remote_cod = 0x000504
E/bt-btif ( 6096): check_cod: remote_cod = 0x000504
D/BluetoothAdapterService( 6096): getAdapterService() - returning com.android.bl
[email protected]
D/HidService( 6096): Connection state B8:5A:F7:C4:6B:F0: 0->2
D/BluetoothAdapterService( 6096): getAdapterService() - returning com.android.bl
[email protected]
D/BluetoothAdapterService( 6096): getAdapterService() - returning com.android.bl
[email protected]
D/BluetoothAdapterState( 6096): CURRENT_STATE=ON, MESSAGE = USER_TURN_ON
I/BluetoothAdapterState( 6096): Bluetooth already ON, ignoring USER_TURN_ON
W/bt-btif ( 6096): btif_hh_upstreams_evt: name = OUYA Game Controller
W/bt-btif ( 6096): bta_hh_co_send_hid_info: fd = 61, name = [OUYA Game Controlle
r], dscp_len = 261
W/bt-btif ( 6096): bta_hh_co_send_hid_info: vendor_id = 0x2836, product_id = 0x0
001, version= 0x0003,ctry_code=0x00
D/BluetoothAdapterProperties( 6096): CONNECTION_STATE_CHANGE: B8:5A:F7:C4:6B:F0:
0 -> 2
E/EventHub( 657): could not get driver version for /dev/input/js0, Invalid argu
ment
W/bt-btif ( 6096): bta_hh_co_send_hid_info: fd = 61, dscp_len = 261, result = 0
W/bt-btif ( 6096): Device B8:5A:F7:C4:6B:F0 already added
W/bt-btif ( 6096): btif_hh_upstreams_evt: Device already added
D/CachedBluetoothDevice( 4257): onProfileStateChanged: profile HID newProfileSta
te 2
E/blakeinputnotify( 1303): locked_handle_input_inotify: /dev/input/event6 is not
blake
I/RSMouse ( 657): ============================================================
I/RSMouse ( 657): Controller "OUYA Game Controller" detected!
I/RSMouse ( 657): ============================================================
I/RSMouse ( 657): Controller Details:
I/RSMouse ( 657): Button 0 = 304 (130)
I/RSMouse ( 657): Button 1 = 305 (131)
I/RSMouse ( 657): Button 2 = 307 (133)
I/RSMouse ( 657): Button 3 = 308 (134)
I/RSMouse ( 657): Button 4 = 310 (136)
I/RSMouse ( 657): Button 5 = 311 (137)
I/RSMouse ( 657): Button 6 = 312 (138)
I/RSMouse ( 657): Button 7 = 313 (139)
I/RSMouse ( 657): Button 8 = 315 (13B)
I/RSMouse ( 657): Button 9 = 314 (13A)
I/RSMouse ( 657): Button 10 = 317 (13D)
I/RSMouse ( 657): Button 11 = 318 (13E)
I/RSMouse ( 657): Button 12 = 316 (13C)
I/RSMouse ( 657): Button 13 = -1 (FFFFFFFF)
I/RSMouse ( 657): Button 14 = -1 (FFFFFFFF)
I/RSMouse ( 657): Button 15 = -1 (FFFFFFFF)
I/RSMouse ( 657): Button 16 = -1 (FFFFFFFF)
I/RSMouse ( 657): Button 17 = -1 (FFFFFFFF)
I/RSMouse ( 657): Button 18 = -1 (FFFFFFFF)
I/RSMouse ( 657): Button 19 = -1 (FFFFFFFF)
I/RSMouse ( 657): Button 20 = -1 (FFFFFFFF)
I/RSMouse ( 657): Button 21 = 0 (000)
I/RSMouse ( 657): Button 22 = 0 (000)
I/RSMouse ( 657): Axis 0 = 0 (000) (0, 32768, 65535) Deadzone = 8190
I/RSMouse ( 657): Axis 1 = 1 (001) (0, 32768, 65535) Deadzone = 8190
I/RSMouse ( 657): Axis 2 = 3 (003) (0, 32768, 65535) Deadzone = 8190
I/RSMouse ( 657): Axis 3 = 4 (004) (0, 32768, 65535) Deadzone = 8190
I/RSMouse ( 657): Axis 4 = 2 (002) (0, 0, 65535) Deadzone = 8190
I/RSMouse ( 657): Axis 5 = 5 (005) (0, 0, 65535) Deadzone = 8190
I/RSMouse ( 657): Axis 6 = -1 (FFFFFFFF) (0, 0, 0) Deadzone = 0
I/RSMouse ( 657): Axis 7 = -1 (FFFFFFFF) (0, 0, 0) Deadzone = 0
I/RSMouse ( 657): ============================================================
I/RSMouse ( 657): Controller "OUYA Game Controller" loaded (id=12)
I/RSMouse ( 657): Vendor=2836 Product=0001
D/EventHub( 657): No input device configuration file found for device 'OUYA Gam
e Controller'.
E/KeyLayoutMap( 657): /system/usr/keylayout/Vendor_2836_Product_0001.kl:41: Exp
ected key flag label, got 'ALT'.
W/EventHub( 657): Unable to disable kernel key repeat for /dev/input/event6: Fu
nction not implemented
I/EventHub( 657): New device: id=12, fd=190, path='/dev/input/event6', name='OU
YA Game Controller', classes=0x80000149, configuration='', keyLayout='/system/us
r/keylayout/Generic.kl', keyCharacterMap='/system/usr/keychars/Generic.kcm', bui
ltinKeyboard=false, wakeMechanism=EPOLLWAKEUP, usingClockIoctl=true
D/InputReader( 657): Mouse Mode = Touch
I/RSMouse ( 657): setVirtualMouseState: enable
I/InputReader( 657): Device added: id=12, name='OUYA Game Controller', sources=
0x01001513
I/InputReader( 657): Setting mTouchBlackoutEnabled from property to 1
I/InputReader( 657): Setting mExtendBlackoutWhilePointersDown from property to
1
I/InputReader( 657): Setting mIIRLowPassFactor from property to 1.000000
I/InputReader( 657): Setting mPressureEBC from property to 0.900000
I/InputReader( 657): Setting mToolSwitchTime from property to 400 ms
I/InputReader( 657): Setting mToolSwitchRange from property to 200
I/InputReader( 657): Setting mEraserLatchRange from property to 10
I/InputReader( 657): Setting mEraserDelayTime from property to 250 ms
I/InputReader( 657): Setting mPinchToZoomTime from property to 1000 ms
I/InputReader( 657): Setting mPinchToZoomRange from property to 1100
I/InputReader( 657): Setting mPinchToZoomRectangleX from property to 800
I/InputReader( 657): Setting mPinchToZoomRectangleY from property to 1400
I/InputReader( 657): Setting mPinchToZoomRectangleCenterX from property to 600
I/InputReader( 657): Setting mPinchToZoomRectangleCenterY from property to 960
I/InputReader( 657): Setting mEdgeRemapMarginLeft from property to 10
I/InputReader( 657): Setting mEdgeRemapMarginTop from property to 5
I/InputReader( 657): Setting mEdgeRemapMarginRight from property to 15
I/InputReader( 657): Setting mEdgeRemapMarginBottom from property to 5
W/EventHub( 657): An input event from /dev/input/event6 has a timestamp that ap
pears to have been generated using the wrong clock source (expected CLOCK_MONOTO
NIC): event time 1420482646686335000, current time 1510801470576, call time 1510
801461159. Using current time instead.
W/EventHub( 657): An input event from /dev/input/event6 has a timestamp that ap
pears to have been generated using the wrong clock source (expected CLOCK_MONOTO
NIC): event time 1420482646686335000, current time 1510801530242, call time 1510
801461159. Using current time instead.
W/EventHub( 657): An input event from /dev/input/event6 has a timestamp that ap
pears to have been generated using the wrong clock source (expected CLOCK_MONOTO
NIC): event time 1420482646686335000, current time 1510801572826, call time 1510
801461159. Using current time instead.
D/Index ( 4257): Indexing locale 'en_GB' took 39 millis
D/blake_utils( 1303): Non Blake HIDRAW device: OUYA Game Controller
W/ActivityManager( 657): getRecentTasks: caller 10036 does not hold GET_TASKS;
limiting output
W/ActivityManager( 657): getRecentTasks: caller 10036 does not hold GET_TASKS;
limiting output
D/btif_config_util( 6096): btif_config_save_file(L188): in file name:/data/misc/
bluedroid/bt_config.new
W/ActivityManager( 657): getRecentTasks: caller 10036 does not hold GET_TASKS;
limiting output
D/HeadsetStateMachine( 6096): currentState is Disconnected
W/ActivityManager( 657): getRecentTasks: caller 10036 does not hold GET_TASKS;
limiting output
I've figured out the issue with the OUYA controller on Lollipop and it's all related to line 41 in the .kl file, specifically HOME ALT. I've removed the HOME ALT and replace it with BUTTON_START instead and it seem to work a lot better now, and gamepad is being detected properly:
https://drive.google.com/file/d/0B86...ew?usp=sharing
So if you're having issues with the OUYA gamepad on Nvidia SHield tablet, use that patch as it seem to fix the issues and it works really well (better than Dualshock 3 for an example).
Could you please reupload the patch? Having alot of trouble getting the OUYA keymapping
EDIT: Figured it out, took the Vendor_2836_Product_0001.kl changed Line 41 to BUTTON_START !
Thanks for pointing me in the right direction!
Hi,
I'm trying to use my Mi 4c as ftp server but isn't working.
Firstly I tried with the ftp option available in file explorer app without luck. Then, I installed primitive ftpd and it displays this info:
Code:
IP Address (Network Interface)
10.0.2.15 (usbnet0)
192.168.1.99 (wla0)
From my laptop, ping command can't connect with my phone:
Code:
ping 192.168.1.99
PING 192.168.1.99 (192.168.1.99) 56(84) bytes of data.
WARNING: kernel is not very fresh, upgrade is recommended.
From 192.168.1.67: icmp_seq=2 Destination Host Unreachable
From 192.168.1.67: icmp_seq=3 Destination Host Unreachable
From 192.168.1.67: icmp_seq=4 Destination Host Unreachable
--- 192.168.1.99 ping statistics ---
6 packets transmitted, 0 received, +3 errors, 100% packet loss, time 5000ms
pipe 4
As you can see, my local network is 192.168.1.0/24 but my phone is not available (I don't know what is usbnet0). I tried with other apps that use a local network such as LG TV Remote or Epson iPrint and they aren't working either, What can I do? I'm using the newest rom from xiaomi.eu
Thanks in advance and sorry if my english is not good.
Hey guys,
I have a Bluetooth pairing problem with my car. My car was in a workshop and they disconnected the battery. After I get it back, I tried to reconnect the phone with the car and got the message "wrong PIN". I deleted the device and tried again, but I get the same error message without a PIN/code query. The connection with my Lumia 930 -> car working fine.
Is it possible to pairing manually (e.g. in a file that include uuid, name, code,...) or reset bluetooth?
Thanks a lot for your help,
Daniel
EDIT: I have connected a PS4 controller over Bluetooth and the pairing works correct for this device
EDIT2: Today I connected another Bluetooth device (BT speaker) again and the connection working fine. After a couple of hours I found a config (/data/misc/bluedroid/bt_config.conf) file that include
Code:
[Info]
FileSource = Empty
TimeCreated = 2018-01-07 15:14:28
[Adapter]
Address = 4c:74:03:df:f0:3c
LE_LOCAL_KEY_IRK = f65d6a2e87ffeb328f2a82ddffd877c3
LE_LOCAL_KEY_IR = 84ec4a284353ec7dd4adeabedf63fee3
LE_LOCAL_KEY_DHK = 1fcc619373fa6d15cf0d04c035a0e28c
LE_LOCAL_KEY_ER = 0a6b8b36db5bf28de89980573927fb4c
ScanMode = 0
DiscoveryTimeout = 120
Name = bqAquarisM5
[fc:70:5a:19:95:4f]
Timestamp = 1516727821
DevClass = 2360324
DevType = 1
AddrType = 0
Manufacturer = 10
LmpVer = 4
LmpSubVer = 4192
Name = BX-100
LinkKeyType = 4
PinLength = 0
LinkKey = 51a24d2784b68bc6949eb4887a3fb177
Service = 0000111e-0000-1000-8000-00805f9b34fb 0000110b-0000-1000-8000-00805f9b34fb 0000110e-0000-1000-8000-00805f9b34fb 00000000-0000-1000-8000-00805f9b34fb
Is it possible to add the necessary information manually?
EDIT: Solved! I don't know what the problem was, but I cleared cache and dalvik-cache, restored the privacy guard settings and reboot. Now it works!