With all of the confusion regarding Miracast adapters (especially the Netgear PTV3000) I thought I'd try to point people in the right direction.
First thing's first, the Netgear PTV3000 does NOT work. It is not certified and has absolutely no connectivity out of the box. It can be flashed
with an experimental firmware to gain crappy functionality but will not work properly until an official update is released.
Edit: The Netgear PTV3000 IS now certified and works great! It's also cheaper than most and is the only stand alone Miracast adapter that can be purchased at Best Buy (or any other offline store for that matter).
So rather than waste your money on a Netgear adapter (like I did) you could buy yourself an Actiontec ScreenBeam which I have confirmed
not only works with the N4 but works great! And if you're not a big fan of Actiontec devices, here is a direct link to the Wi-Fi Alliances list of
Official Miracast Certified Recievers
which are certified (imagine that) to work with the Nexus 4.
Happy screen beaming :laugh:
Not that I don't believe you, but who/how did you confirm the ActionTec works?
I'm looking for some anecdotal reviews and opinions of it. Thanks.
narcopolypse said:
With all of the confusion regarding Miracast adapters (especially the Netgear PTV3000) I thought I'd try to point people in the right direction.
First thing's first, the Netgear PTV3000 does NOT work. It is not certified and has absolutely no connectivity out of the box. It can be flashed
with an experimental firmware to gain crappy functionality but will not work properly until an official update is released.
So rather than waste your money on a Netgear adapter (like I did) you could buy yourself an Actiontec ScreenBeam which I have confirmed
not only works with the N4 but works great! And if you're not a big fan of Actiontec devices, here is a direct link to the Wi-Fi Alliances list of
Official Miracast Certified Recievers
which are certified (imagine that) to work with the Nexus 4.
Happy screen beaming :laugh:
Click to expand...
Click to collapse
Where did you buy it?
Sent from my Galaxy Nexus using Tapatalk 2
plasticdarlow said:
Where did you buy it?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
First link on Google:
http://www.amazon.com/ACTIONTEC-SBWD100KIT01-ScreenBeam-Universal-Wireless/dp/B009Z8T3K6
Looks like it's not out yet. So the OP is either 1. speculating based on the certification (from just 9 days ago). Or 2. Has some sort of inside connection to get one before they have even gone up for sale.
Guessing it's 1.
Please post a YouTube video!
---------- Post added at 04:32 AM ---------- Previous post was at 04:30 AM ----------
Never mind I found one and it looks like the same adapter from far away....
https://www.youtube.com/watch?v=qjtSzfNVq5E&feature=youtube_gdata_player
---------- Post added at 04:52 AM ---------- Previous post was at 04:32 AM ----------
Aaaand furthermore if you can wait they are sitting in best buy stores according to their website...
http://m.bestbuy.com/m/e/product/detail.jsp?skuId=3179075&pid=1218382979736
I bought ACTIONTEC SBWD100KIT01 ScreenBeam, it should be shipped next week, i will post the results with Nexus 4.
rican408 said:
Aaaand furthermore if you can wait they are sitting in best buy stores according to their website...
http://m.bestbuy.com/m/e/product/detail.jsp?skuId=3179075&pid=1218382979736
Click to expand...
Click to collapse
This isn't the same product that's Miracast certified... Looks the same, but different model numbers.
Sent from my Nexus 4 using xda premium
freesoul27 said:
I bought ACTIONTEC SBWD100KIT01 ScreenBeam, it should be shipped next week, i will post the results with Nexus 4.
Click to expand...
Click to collapse
Where did you order from?
ericshmerick said:
First link on Google:
http://www.amazon.com/ACTIONTEC-SBWD100KIT01-ScreenBeam-Universal-Wireless/dp/B009Z8T3K6
Looks like it's not out yet. So the OP is either 1. speculating based on the certification (from just 9 days ago). Or 2. Has some sort of inside connection to get one before they have even gone up for sale.
Guessing it's 1.
Click to expand...
Click to collapse
Or 3, they have been up for sale on Amazon for a week now but are currently sold out. (seems par for the course with anything related to the N4) Fortunately a friend of mine got one before they sold out. Tested and confirmed working with his Nexus 4.
And FYI this also comes with a little USB dongle that you can plug into any computer to make it Miracast enabled. We tried it with an AMD computer running a Nvidia GPU and it works great!
plasticdarlow said:
Where did you buy it?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Amazon
rican408 said:
Where did you order from?
Click to expand...
Click to collapse
Amazon
Sent from my Nexus 4 using Tapatalk 2
narcopolypse said:
We tried it with an AMD computer running a Nvidia GPU and it works great!
Amazon
Click to expand...
Click to collapse
2 things (doubt you can help with the 2nd, but who knows).
1. when you use the USB dongle on the PC, does it mirror the laptop display, or can you configure it as a second screen?
2. Have you tested it with a Galaxy S3 (miracast certified)?
Nothing in the UK though
Sent from my Nexus 4 using xda app-developers app
I received my Actiontec adapter yesterday (bought through Amazon) and it does NOT work with both my nexus 4 devices.
It will try to pair and will fail after 20sec.
One N4 is unlocked and rooted running stock. The other N4 is not rooted and not unlocked fully stock with nothing installed on it.
Both will NOT connect with this adapter.
If anyone was able to get this to work please specify how you did it.
Both my N4's can connect to the Netgear PTV3000 with the beta firmware that was floating around.
Also, the Actiontec comes with a USB dongle that you can use on any PC to mirror its screen. Even that will only connect to the adapter two times in 20 tries...the rest will simply time out.
c4v3man said:
2 things (doubt you can help with the 2nd, but who knows).
1. when you use the USB dongle on the PC, does it mirror the laptop display, or can you configure it as a second screen?
2. Have you tested it with a Galaxy S3 (miracast certified)?
Click to expand...
Click to collapse
1. Didn't try but it did show up as an additional video card in device manager so I assume you could use it as a second screen.
Also, the Miracast standard (and pre release demos) say it should.
2. I couldn't get it to work but that doesn't surprise me.
clubtech said:
I received my Actiontec adapter yesterday (bought through Amazon) and it does NOT work with both my nexus 4 devices.
It will try to pair and will fail after 20sec.
One N4 is unlocked and rooted running stock. The other N4 is not rooted and not unlocked fully stock with nothing installed on it.
Both will NOT connect with this adapter.
If anyone was able to get this to work please specify how you did it.
Both my N4's can connect to the Netgear PTV3000 with the beta firmware that was floating around.
Also, the Actiontec comes with a USB dongle that you can use on any PC to mirror its screen. Even that will only connect to the adapter two times in 20 tries...the rest will simply time out.
Click to expand...
Click to collapse
It will not work on the Nexus 4 if it is rooted. As for not working with on your unrooted one, I don't know what to tell you. We got it to work. (after we figured out it has to be unrooted)
Also, it will only work if you've updated to JOP40D.
screenbeam
narcopolypse said:
Or 3, they have been up for sale on Amazon for a week now but are currently sold out. (seems par for the course with anything related to the N4) Fortunately a friend of mine got one before they sold out. Tested and confirmed working with his Nexus 4.
And FYI this also comes with a little USB dongle that you can plug into any computer to make it Miracast enabled. We tried it with an AMD computer running a Nvidia GPU and it works great!
Amazon
Click to expand...
Click to collapse
Could you do a video for me please? I'm really interested as to how miracast is implemented with the Nexus 4... does it just mirror everything on your screen no matter what app youre using, does it continue working when you turn the screen on the phone off, whats the latency like?
Really interested,
Thanks
narcopolypse said:
1. Didn't try but it did show up as an additional video card in device manager so I assume you could use it as a second screen.
Also, the Miracast standard (and pre release demos) say it should.
2. I couldn't get it to work but that doesn't surprise me.
It will not work on the Nexus 4 if it is rooted. As for not working with on your unrooted one, I don't know what to tell you. We got it to work. (after we figured out it has to be unrooted)
Click to expand...
Click to collapse
That is not accurate. I don't think it has anyhting to do with being rooted or not.
I contacted Actiontec and they responded saying that the shipping firmware will not work with the N4 and that they are working on a beta firmware that will fix the problem.
Since you got it to work, what firmware version is your adapter running?
I got mine today (Actiontec ScreenBeem SBWD100A v1.0.21). It does not work out of the box. (for me anyway)
Logcat is saying something about hdcp failing. apparently qseecom is looking in the wrong directory so i copied the discretix files from /vendor/firmware/discretix to /system/etc/firmware/ but it still wouldnt connect. Interestingly i can connect to it as a wifi-direct device it then disconnects saying the app wasnt found (on the tv). so after that i tried reconnecting the wfd, it connects but looks like hdcp still has issues and actually locks up the device every time. Anyway thats my story.
log snipped
Code:
I/ActivityManager( 544): Displayed com.android.settings/.Settings$WifiDisplaySettingsActivity: +527ms
W/System.err( 1987): Removed 2131231194
W/System.err( 1987): Removed 2131231203
D/overlay ( 163): FROM_STATE = OV_BYPASS_3_LAYER TO_STATE = OV_CLOSED
I/wpa_supplicant( 699): p2p0: P2P-DEVICE-FOUND 10:9f:a9:dc:a1:62 p2p_dev_addr=10:9f:a9:dc:a1:62 pri_dev_type=8-0050F204-5 name='SBWD-DCA162' config_methods=0x88 dev_capab=0x25 group_capab=0xa wfd_dev_info=0x0000060051022a012c
D/overlay ( 163): FROM_STATE = OV_CLOSED TO_STATE = OV_BYPASS_3_LAYER
I/wpa_supplicant( 699): p2p0: P2P-FIND-STOPPED
I/WifiDisplayController( 544): Connecting to Wifi display: SBWD-DCA162
I/wpa_supplicant( 699): p2p0: P2P-INVITATION-RESULT status=0
I/WifiDisplayController( 544): Initiated connection to Wifi display: SBWD-DCA162
E/wpa_supplicant( 699): Using interface p2p0 with hwaddr ea:92:a4:93:6a:82 and ssid "DIRECT-Am-Android_5132"
W/wpa_supplicant( 699): Device is trying to offload WPS Probe Response while not supporting this
W/wpa_supplicant( 699): Device is trying to offload P2P Probe Response while not supporting this
I/wpa_supplicant( 699): p2p0: CTRL-EVENT-CONNECTED - Connection to ea:92:a4:93:6a:82 completed (auth) [id=1 id_str=]
I/wpa_supplicant( 699): p2p0: P2P-GROUP-STARTED p2p0 GO ssid="DIRECT-Am-Android_5132" freq=2462 passphrase="GM1GC0rd" go_dev_addr=ea:92:a4:93:6a:82 [PERSISTENT]
D/CommandListener( 160): Setting iface cfg
D/CommandListener( 160): Trying to bring up p2p0
D/TetherController( 160): Starting tethering services
D/TetherController( 160): Tethering services running
D/WifiP2pService( 544): Started Dhcp server on p2p0
I/dnsmasq ( 2012): started, version 2.51 cachesize 150
I/dnsmasq ( 2012): compile time options: no-IPv6 GNU-getopt no-DBus no-I18N DHCP no-scripts no-TFTP
W/dnsmasq ( 2012): warning: no upstream servers configured
I/dnsmasq ( 2012): DHCP, IP range 192.168.49.2 -- 192.168.49.254, lease time 1h
I/dnsmasq ( 2012): read /etc/hosts - 1 addresses
D/overlay ( 163): FROM_STATE = OV_BYPASS_3_LAYER TO_STATE = OV_CLOSED
W/ThrottleService( 544): unable to find stats for iface rmnet_usb0
D/alsa_ucm( 166): snd_use_case_set(): uc_mgr 0x40bf82a0 identifier _verb value Inactive
D/alsa_ucm( 166): Set mixer controls for HiFi Lowlatency enable 0
D/alsa_ucm( 166): snd_use_case_set(): uc_mgr 0x40bf82a0 identifier _disdev value Speaker
D/alsa_ucm( 166): Set mixer controls for Speaker enable 0
W/wpa_supplicant( 699): Device is trying to offload WPS Probe Response while not supporting this
W/wpa_supplicant( 699): Device is trying to offload P2P Probe Response while not supporting this
I/wpa_supplicant( 699): p2p0: AP-STA-CONNECTED 10:9f:a9:dc:a1:62 p2p_dev_addr=10:9f:a9:dc:a1:62
I/wpa_supplicant( 698): Could not set station 10:9f:a9:dc:a1:62 flags for kernel driver (errno=11).
I/WifiDisplayController( 544): Connected to Wifi display: SBWD-DCA162
E/MonoPipe( 166): Failed to fetch local time frequency when constructing a MonoPipe (res = -32). getNextWriteTimestamp calls will be non-functional
I/AudioFlinger( 166): HAL output buffer size 1024 frames, normal mix buffer size 1024 frames
I/AudioMixer( 166): found effect "Multichannel Downmix To Stereo" from The Android Open Source Project
I/AudioFlinger( 166): HAL output buffer size 1024 frames, normal mix buffer size 1024 frames
I/AudioMixer( 166): found effect "Multichannel Downmix To Stereo" from The Android Open Source Project
I/WifiDisplayController( 544): Listening for RTSP connection on 192.168.49.1:7236 from Wifi display: SBWD-DCA162
D/ALSAStreamOps( 166): setParameters(): keyRouting with device 0x0
D/ALSAStreamOps( 166): setParameters(): keyRouting with device 0x0
I/AudioFlinger( 166): AudioFlinger's thread 0x40daf008 ready to run
I/AudioFlinger( 166): AudioFlinger's thread 0x41125008 ready to run
I/r_submix( 166): out_standby()
D/ALSAStreamOps( 166): setParameters(): keyRouting with device 0x0
I/dnsmasq ( 2012): DHCPDISCOVER(p2p0) 10:9f:a9:dc:a1:62
I/dnsmasq ( 2012): DHCPOFFER(p2p0) 192.168.49.75 10:9f:a9:dc:a1:62
I/dnsmasq ( 2012): DHCPREQUEST(p2p0) 192.168.49.75 10:9f:a9:dc:a1:62
I/dnsmasq ( 2012): DHCPACK(p2p0) 192.168.49.75 10:9f:a9:dc:a1:62
I/NetworkSession( 166): incoming connection from 192.168.49.75:44435 (socket 35)
I/NetworkSession( 166): added clientSession 2
I/WifiDisplaySource( 166): We now have a client (2) connected.
I/WifiDisplaySource( 166): Using AAC audio.
I/WifiDisplaySource( 166): Initiating HDCP negotiation w/ host 192.168.49.75:25030
D/QSEECOMAPI: ( 166): QSEECom_start_app sb_length = 0x480
D/QSEECOMAPI: ( 166): App is not loaded in QSEE
W/WifiDisplaySource( 166): Response handler for session 2, cseq 3 returned err -1010 (Unknown error 1010)
I/WifiDisplayController( 544): Lost RTSP connection with Wifi display due to error 1: SBWD-DCA162
I/WifiDisplayController( 544): Wifi display connection failed!
D/QSEECOMAPI: ( 166): Loaded image: APP id = 1
D/DxHDCP ( 166): AKE_SEND_CERT received
D/DxHDCP ( 166): AKE_RECEIVER_INFO received
D/DxHDCP ( 166): AKE_SEND_RRX received
D/DxHDCP ( 166): AKE_SEND_H_PRIME received
D/DxHDCP ( 166): AKE_PAIRING_INFO received
D/DxHDCP ( 166): LC_L_PRIME received
D/DxHDCP ( 166): REPEATERAUTH_SEND_RECEIVERID_LIST received
I/DxHDCPModule( 166): Got callback from DX: 7, 0x43b24874, 0x0
I/DxHDCPModule( 166): Got callback from DX: 9, 0x43b24ea8, 0x0
I/WifiDisplaySource( 166): Saw HDCP notification code 8, ext1 1135759016, ext2 0
E/WifiDisplaySource( 166): HDCP failure, shutting down.
I/WifiDisplayController( 544): Lost RTSP connection with Wifi display due to error 1: SBWD-DCA162
I/WifiDisplayController( 544): Wifi display connection failed!
D/overlay ( 163): FROM_STATE = OV_CLOSED TO_STATE = OV_BYPASS_3_LAYER
I/WifiDisplaySource( 166): Initiating HDCP shutdown.
I/WifiDisplayController( 544): Retrying Wifi display connection. Retries left: 2
I/WifiDisplayController( 544): Stopped listening for RTSP connection on 192.168.49.1:7236 from Wifi display: SBWD-DCA162
D/overlay ( 163): FROM_STATE = OV_BYPASS_3_LAYER TO_STATE = OV_CLOSED
I/wpa_supplicant( 699): p2p0: AP-STA-DISCONNECTED 10:9f:a9:dc:a1:62 p2p_dev_addr=10:9f:a9:dc:a1:62
W/wpa_supplicant( 699): Device is trying to offload WPS Probe Response while not supporting this
W/wpa_supplicant( 699): Device is trying to offload P2P Probe Response while not supporting this
I/wpa_supplicant( 699): p2p0: P2P-GROUP-REMOVED p2p0 GO reason=REQUESTED
D/WifiP2pService( 544): Client list empty, remove non-persistent p2p group
D/TetherController( 160): Stopping tethering services
I/dnsmasq ( 2012): exiting on receipt of SIGTERM
D/TetherController( 160): Tethering services stopped
D/WifiP2pService( 544): Stopped Dhcp server
D/CommandListener( 160): Clearing all IP addresses on p2p0
D/NetUtils( 544): android_net_utils_resetConnections in env=0x72438730 clazz=0x33d00001 iface=p2p0 mask=0x3
I/wpa_supplicant( 699): wpa_s->ifname p2p0 cmd SET p2p_group_idle 0
I/wpa_supplicant( 699): p2p0: P2P-DEVICE-LOST p2p_dev_addr=10:9f:a9:dc:a1:62
D/overlay ( 163): FROM_STATE = OV_CLOSED TO_STATE = OV_BYPASS_3_LAYER
D/overlay ( 163): FROM_STATE = OV_BYPASS_3_LAYER TO_STATE = OV_CLOSED
D/overlay ( 163): FROM_STATE = OV_CLOSED TO_STATE = OV_BYPASS_3_LAYER
D/overlay ( 163): FROM_STATE = OV_BYPASS_3_LAYER TO_STATE = OV_CLOSED
D/overlay ( 163): FROM_STATE = OV_CLOSED TO_STATE = OV_BYPASS_3_LAYER
I/EventLogService( 984): Aggregate from 1355272073669 (log), 1355271525913 (data)
D/dalvikvm( 984): GC_CONCURRENT freed 232K, 3% free 9401K/9660K, paused 3ms+3ms, total 22ms
I/ServiceDumpSys( 984): dumping service [account]
D/overlay ( 163): FROM_STATE = OV_BYPASS_3_LAYER TO_STATE = OV_CLOSED
D/overlay ( 163): FROM_STATE = OV_CLOSED TO_STATE = OV_BYPASS_3_LAYER
D/overlay ( 163): FROM_STATE = OV_BYPASS_3_LAYER TO_STATE = OV_CLOSED
D/overlay ( 163): FROM_STATE = OV_CLOSED TO_STATE = OV_BYPASS_3_LAYER
D/dalvikvm( 1987): GC_CONCURRENT freed 131K, 2% free 9378K/9536K, paused 3ms+3ms, total 20ms
D/overlay ( 163): FROM_STATE = OV_BYPASS_3_LAYER TO_STATE = OV_CLOSED
W/AudioTrack( 544): obtainBuffer timed out (is the CPU pegged?) 0x731d2b48 name=0x2user=00002000, server=00000000
D/overlay ( 163): FROM_STATE = OV_CLOSED TO_STATE = OV_BYPASS_3_LAYER
W/AudioTrack( 544): obtainBuffer timed out (is the CPU pegged?) 0x731d2b48 name=0x2user=00002000, server=00000000
D/overlay ( 163): FROM_STATE = OV_BYPASS_3_LAYER TO_STATE = OV_CLOSED
W/AudioTrack( 544): obtainBuffer timed out (is the CPU pegged?) 0x731d2b48 name=0x2user=00002000, server=00000000
EDIT:
so after reflashing the factory image and relocking the bootloader it is still failing on hdcp
Code:
I/WifiDisplaySource( 164): Initiating HDCP negotiation w/ host 192.168.49.75:25030
W/WifiDisplaySource( 164): Response handler for session 2, cseq 3 returned err -1010 (Unknown error 1010)
I/WifiDisplayController( 595): Lost RTSP connection with Wifi display due to error 1: SBWD-DCA162
D/QSEECOMAPI: ( 164): QSEECom_start_app sb_length = 0x480
D/QSEECOMAPI: ( 164): App is not loaded in QSEE
E/QSEECOMAPI: ( 164): Error::Cannot open the file /system/etc/firmware/dxhdcp2.mdt
E/QSEECOMAPI: ( 164): Error::Loading image failed with ret = -1
D/QSEECOMAPI: ( 164): QSEECom_start_app sb_length = 0x480
I/WifiDisplayController( 595): Wifi display connection failed!
D/QSEECOMAPI: ( 164): App is not loaded in QSEE
D/QSEECOMAPI: ( 164): Loaded image: APP id = 1
D/DxHDCP ( 164): AKE_SEND_CERT received
D/DxHDCP ( 164): AKE_RECEIVER_INFO received
D/DxHDCP ( 164): AKE_SEND_RRX received
D/DxHDCP ( 164): AKE_SEND_H_PRIME received
D/DxHDCP ( 164): AKE_PAIRING_INFO received
D/DxHDCP ( 164): LC_L_PRIME received
D/DxHDCP ( 164): REPEATERAUTH_SEND_RECEIVERID_LIST received
I/DxHDCPModule( 164): Got callback from DX: 7, 0x43316874, 0x0
I/DxHDCPModule( 164): Got callback from DX: 9, 0x43316ea8, 0x0
I/WifiDisplaySource( 164): Saw HDCP notification code 8, ext1 1127313064, ext2 0
E/WifiDisplaySource( 164): HDCP failure, shutting down.
I/WifiDisplayController( 595): Lost RTSP connection with Wifi display due to error 1: SBWD-DCA162
I/WifiDisplayController( 595): Wifi display connection failed!
@texasice, it is interesting to see that you are running V1.0.24 while mine is running 1.0.21. Did you get yours from Amazon?
clubtech said:
@texasice, it is interesting to see that you are running V1.0.24 while mine is running 1.0.21. Did you get yours from Amazon?
Click to expand...
Click to collapse
oops sorry typo its v1.0.21 from amazon
Related
Thought I may aswell get this up... I'm just writing up what I've found out myself since looking into it from last night. It may be of no use, it may help a basis of discussion for sorting this, or it may just disappear into the depths of XDA never to be seen again
Ok, as everyone pretty much knows, any FroYo (Ported or AOSP-built) ROM has an issue, where the WiFi suffers from extremely high latency and/or dropped packets when the phone is asleep, regardless if the power options are set or not (Settings -> Wireless and Blah -> WiFi -> Advanced)
Now... I've done some looking about on google, and found this thread
http://code.google.com/p/android/issues/detail?id=9781
This pretty much explains things bang on... I do also suffer from these problems (the streaming and such dropping out), but others have absolutely no throughput, this seems dependant on MAC address...
Those whose MAC starts with 00:23 seem to only suffer from high pings and the odd dropped packet.
Those whose MAX starts with 38:E7 seem to suffer 100% dropped packets.
(I'm not sure if there are any other MAC addresses)
So... According to the Google link above, it relates to a problem with how PSP (PowerSave Mode) is handled, aswell as possibly incompatibilities with certain makes of routers.
So what do we need to do?
Ideally, we need to make sure that any-and-all Wake-Locks are registered and managed correctly, or a quick dirty method, disable and-and-all mentions to any powersaving methods in either the Kernel Driver for the WiFi, FroYo itself for any sort of WiFi lock, or both... I've looked at the Kernel source (specifically /drivers/net/wireless/bcm4329/dhd_cdc.c) as mentioned on Lines 678 and 679 is:
Code:
/* Set PowerSave mode */
dhdcdc_set_ioctl(dhd, 0, WLC_SET_PM, (char *)&power_mode, sizeof(power_mode));
I did first try just disabling that completely, but it prevented the WiFi from even starting... Maybe a hook, or check on the power_mode variable needs to be looked into, see whats passed when PowerSave is sent (screen off) and override it with what the default setting for ON is? This line does also exist on 532 and 551, but 678 is the only area where it implicitly says PowerSave. (I need to read through the whole source file and work a flowchart out of how it works)
Then again, I could be barking up the wrong tree, but out of all the files in that folder, this is the *only* mention I could find at 3am last night...
The only other problem I can see is that the firmware for the WiFi is actually closed-source, and is ripped directly from existing HTC-based ROMS. So modifying this would be extremely difficult.
Now, people have said this issue doesn't show on ROMs released from HTC directly, but when I was still using WWE 1.15 and WWE 1.21-based ROMs, I had the same amount of hight latency pings and the odd packet drop as I do now with FroYo. (my MAC is 00:23) I've not tested the leaked 2.2 ROMs from HTC, so have no knowledge if this problem is fixed in there.
I also came across this (this is an email I was sent) this relates to a program called WiFi Fixer which appears to be working on most N1 devices... (this was found in a discussion originally I think from one of the linked threads from the google bug report above... I'll check and re-link when I can find the original source)
The release has new code. Should be out tomorrow. There are 2
options for Nexus One fixes which have been helping people with the
sleep policy bug.
The trick is it make take 15-30 seconds to kick in once the screen goes off.
http://dl.dropbox.com/u/6727098/listrc/wififixer.apk
You can try the RC4 build if you like, it's basically the same as
release will be.
Click to expand...
Click to collapse
However, using said app on the Desire causes the WiFi to completely stop working all together, and I experienced no joy with any other options it gives to try resolve this issue. Feel free to try it yourself, the hacks it does are non-permanent (it runs as a service) and as soon as its uninstalled, everything will go back to normal.
So yeah...
Modify the Kernel Source
Modify FroYo AOSP methods for sleeping
Modify both (possibly)
or something else...
One note, I've a Desire with Mac 38:E7 and I can confirm that with the HTC Leaked the wifi is always on (as I set it in the Wifi Policy) but with the screen off, yes I've higher pings.
But, with the AOSP (AOSPDesire/OpenDesire) even setting the Wifi Policy to Never, it falls at the time that the screen goes off.
for me it's perfect :00:23
check too this file: WifiService.java
/home/meliantq/aospdesire/system/frameworks/base/services/java/com/android/server/WifiService.java
already try to force stay on = ko
maybe change the wake lock
Differences between how the MAC addresses react, could be related to a possibly firmware bug for the driver too... Who knows...
I have also tried building an AOSP build around the new firmware files from the leaked HTC 2.2 ROMs, but these failed to connect at all too.
I thank you for your great work..I hope you can fix it.. and I hope i can use AOSP rom
meliantq - je te remercie pour ton travail formidable...
paul for me too is not really perfect ...
D/WifiWatchdogService( 163): (android.server.ServerThread) NEUF_68B8 (00:25:xx:xx:xx:xx) does not require the watchdog
V/WifiStateTracker( 163):IP configuration: ipaddr 192.168.1.50 gateway 192.168.1.1 netmask 255.255.255.0 dns1 192.168.1.1 dns2 0.0.0.0 DHCP server 0.0.0.0 lease 0 seconds
D/DataConnectionTracker( 333): disableApnType(default)
D/DataConnectionTracker( 333): setEnabled(0, false) with old state = true and enabledCount = 1
D/DataConnectionTracker( 333): EVENT_APN_ENABLE_REQUEST 0, 0
D/DataConnectionTracker( 333): dataEnabled = true, enabledCount = 1, isApnTypeActive = true
D/ConnectivityService( 163): ConnectivityChange for WIFI: CONNECTED/CONNECTED
V/ConnectivityService( 163): Policy requires mobile teardown
V/NetworkStateTracker( 163): Setting TCP values: [4095,87380,110208,4096,16384,110208] which comes from [net.tcp.buffersize.wifi]
D/Tethering( 163): Tethering got CONNECTIVITY_ACTION
D/Tethering( 163): MasterInitialState.processMessage what=3
E/HierarchicalStateMachine( 163): TetherMaster - unhandledMessage: msg.what=3
D/ConnectivityService( 163): adding dns 192.168.1.1 for WIFI
D/ConnectivityService( 163): adding dns 192.168.1.1 for WIFI
D/Smack ( 383): [XMPPConn] close connection, notifyClosed=false
E/ConnectivityService( 163): connected default network is not mActiveDefaultNetwork!
W/Smack/Packet( 383): notify conn break (IOEx), close connection
I/GTalkService( 383): [ServiceAutoStarter] --- connectivity changed
I/GTalkService( 383): [ServiceAutoStarter] --- start GTalk service ---
E/ConnectivityService( 163): connected default network is not mActiveDefaultNetwork!
D/dalvikvm( 383): GC_FOR_MALLOC freed 5110 objects / 447112 bytes in 46ms
D/NativeCrypto( 383): Freeing OpenSSL session
D/NativeCrypto( 383): Freeing OpenSSL session
D/MobileDataStateTracker( 163): default Received state= DISCONNECTED, old= CONNECTED, reason= dataDisabled, apnTypeList= default,supl
D/NetworkStateTracker( 163): setDetailed state, old =CONNECTED and new state=DISCONNECTED
D/ConnectivityService( 163): ConnectivityChange for mobile: DISCONNECTED/DISCONNECTED
D/ConnectivityService( 163): getMobileDataEnabled returning true
V/ConnectivityService( 163): Switching to already connected WIFI
D/ConnectivityService( 163): adding dns 192.168.1.1 for WIFI
D/Tethering( 163): Tethering got CONNECTIVITY_ACTION
D/Tethering( 163): MasterInitialState.processMessage what=3
E/HierarchicalStateMachine( 163): TetherMaster - unhandledMessage: msg.what=3
D/Tethering( 163): Tethering got CONNECTIVITY_ACTION
D/Tethering( 163): MasterInitialState.processMessage what=3
E/HierarchicalStateMachine( 163): TetherMaster - unhandledMessage: msg.what=3
I/GTalkService( 383): [ServiceAutoStarter] --- connectivity changed
I/GTalkService( 383): [ServiceAutoStarter] --- start GTalk service ---
I/GTalkService( 383): [ServiceAutoStarter] --- connectivity changed
I/GTalkService( 383): [ServiceAutoStarter] --- start GTalk service ---
W/GTalkService( 383): [GTalkConnection.14] doConnect: caught XMPPError connecting to mtalk.google.com:5228.: (502)
W/GTalkService( 383): -- caused by: java.net.SocketException: The operation timed out
D/NetworkLocationProvider( 163): onDataConnectionStateChanged 1
D/WifiService( 163): releaseWifiLockLocked: WifiLock{NetworkLocationProvider type=2 [email protected]}
W/GTalkService( 383): [GTalkConnection.14] doConnect: caught XMPPError connecting to mtalk.google.com:5228.: (502)
W/GTalkService( 383): -- caused by: java.net.SocketException: No route to host
W/GTalkService( 383): [GTalkConnection.14] doConnect: caught XMPPError connecting to mtalk.google.com:5228.: (502)
W/GTalkService( 383): -- caused by: java.net.SocketException: No route to host
D/NativeCrypto( 383): Freeing OpenSSL session
I/power ( 163): *** set_screen_state 0
D/WifiService( 163): ACTION_SCREEN_OFF
D/WifiService( 163): setting ACTION_DEVICE_IDLE timer for 900000ms
D/SurfaceFlinger( 163): About to give-up screen, flinger = 0x1269f0
D/AK8973 ( 143): Compass CLOSE
D/StatusBar( 163): DISABLE_EXPAND: yes
D/GoogleLoginService( 383): onBind: Intent { act=android.accounts.AccountAuthenticator cmp=com.google.android.gsf/.loginservice.GoogleLoginService }
W/InputManagerService( 163): Starting input on non-focused client a[email protected] (uid=1000 pid=163)
W/GTalkService( 383): [GTalkConnection.14] doConnect: caught XMPPError connecting to mtalk.google.com:5228.: (502)
W/GTalkService( 383): -- caused by: java.net.SocketException: No route to host
Click to expand...
Click to collapse
when screen off ping don't work
here is good:
/NetworkStateTracker( 163): setDetailed state, old =AUTHENTICATING and new state=CONNECTED
D/WifiWatchdogService( 163): (android.server.ServerThread) NEUF_68B8 (00:25:xx:xx:xx:xx) does not require the watchdog
V/WifiStateTracker( 163): IP configuration: ipaddr 192.168.1.20 gateway 192.168.1.1 netmask 255.255.255.0 dns1 192.168.1.1 dns2 0.0.0.0 DHCP server 0.0.0.0 lease 0 seconds
D/DataConnectionTracker( 333): disableApnType(default)
D/DataConnectionTracker( 333): setEnabled(0, false) with old state = true and enabledCount = 1
D/DataConnectionTracker( 333): EVENT_APN_ENABLE_REQUEST 0, 0
D/DataConnectionTracker( 333): dataEnabled = true, enabledCount = 1, isApnTypeActive = true
V/NetworkStateTracker( 163): Setting TCP values: [4095,87380,110208,4096,16384,110208] which comes from [net.tcp.buffersize.wifi]
D/ConnectivityService( 163): ConnectivityChange for WIFI: CONNECTED/CONNECTED
V/ConnectivityService( 163): Policy requires mobile teardown
D/ConnectivityService( 163): adding dns 192.168.1.1 for WIFI
D/Tethering( 163): Tethering got CONNECTIVITY_ACTION
D/Tethering( 163): MasterInitialState.processMessage what=3
E/HierarchicalStateMachine( 163): TetherMaster - unhandledMessage: msg.what=3
D/ConnectivityService( 163): adding dns 192.168.1.1 for WIFI
I/GTalkService( 383): [ServiceAutoStarter] --- connectivity changed
I/GTalkService( 383): [ServiceAutoStarter] --- start GTalk service ---
E/ConnectivityService( 163): connected default network is not mActiveDefaultNetwork!
E/ConnectivityService( 163): connected default network is not mActiveDefaultNetwork!
D/MobileDataStateTracker( 163): default Received state= DISCONNECTED, old= CONNECTED, reason= dataDisabled, apnTypeList= default,supl
D/NetworkStateTracker( 163): setDetailed state, old =CONNECTED and new state=DISCONNECTED
D/ConnectivityService( 163): ConnectivityChange for mobile: DISCONNECTED/DISCONNECTED
D/ConnectivityService( 163): getMobileDataEnabled returning true
V/ConnectivityService( 163): Switching to already connected WIFI
D/ConnectivityService( 163): adding dns 192.168.1.1 for WIFI
D/Tethering( 163): Tethering got CONNECTIVITY_ACTION
D/Tethering( 163): MasterInitialState.processMessage what=3
E/HierarchicalStateMachine( 163): TetherMaster - unhandledMessage: msg.what=3
D/Tethering( 163): Tethering got CONNECTIVITY_ACTION
D/Tethering( 163): MasterInitialState.processMessage what=3
E/HierarchicalStateMachine( 163): TetherMaster - unhandledMessage: msg.what=3
D/NetworkLocationProvider( 163): onDataConnectionStateChanged 1
I/GTalkService( 383): [ServiceAutoStarter] --- connectivity changed
I/GTalkService( 383): [ServiceAutoStarter] --- start GTalk service ---
I/GTalkService( 383): [ServiceAutoStarter] --- connectivity changed
I/GTalkService( 383): [ServiceAutoStarter] --- start GTalk service ---
D/WifiService( 163): releaseWifiLockLocked: WifiLock{NetworkLocationProvider type=2 [email protected]}
D/dalvikvm( 345): GC_EXPLICIT freed 3807 objects / 212656 bytes in 93ms
D/dalvikvm( 430): GC_FOR_MALLOC freed 9262 objects / 470528 bytes in 48ms
D/dalvikvm( 471): GC_EXPLICIT freed 3024 objects / 154712 bytes in 106ms
D/dalvikvm( 430): GC_EXPLICIT freed 4281 objects / 157808 bytes in 96ms
D/dalvikvm( 383): GC_EXPLICIT freed 4233 objects / 341024 bytes in 103ms
D/dalvikvm( 381): GC_EXPLICIT freed 93 objects / 4232 bytes in 52ms
D/WindowManager( 163): I'm tired mEndcallBehavior=0x2
I/power ( 163): *** set_screen_state 0
D/WifiService( 163): ACTION_SCREEN_OFF
D/WifiService( 163): setting ACTION_DEVICE_IDLE timer for 900000ms
D/StatusBar( 163): DISABLE_EXPAND: yes
D/GoogleLoginService( 383): onBind: Intent { act=android.accounts.AccountAuthenticator cmp=com.google.android.gsf/.loginservice.GoogleLoginService }
W/InputManagerService( 163): Starting input on non-focused client [email protected] (uid=1000 pid=163)
D/SurfaceFlinger( 163): About to give-up screen, flinger = 0x1269f0
Click to expand...
Click to collapse
Ping when screen off ok
I have MAC who starts with 38:E7
I also have network who became to state "disabled" after a long sleep time
I ave to re connect to the network.
It seems it happens only to secured networks
with richardtrip roms versions 2.0a b c and d It seems this problem disapeared.
edit: probably also because the rom had sleep problems as the battery consumption was high... so maybe it was as simple as no sleep measn also no wifi disconnection....
but why? why doesn't it work for me? Ok i changed my mobile package and i buyed origami jet package (internet mail&wifi, calls, tv, sms&mms etc unlimited).. I want to use AOSP rom and downloaded froyo-desire 0.1b...ooo la la
@Paul:
check the framework/base/wifi
/**
* Set power mode
* @param mode
* DRIVER_POWER_MODE_AUTO
* DRIVER_POWER_MODE_ACTIVE
* @return {@code true} if the operation succeeds, {@code false} otherwise
*/
public synchronized boolean setPowerMode(int mode) {
if (mWifiState.get() != WIFI_STATE_ENABLED && !isDriverStopped()) {
return false;
}
return WifiNative.setPowerModeCommand(mode);
}
Click to expand...
Click to collapse
meLIanTQ said:
@Paul:
check the framework/base/wifi
Click to expand...
Click to collapse
Looking
Also, in the same folder, check out lines 922 onwards for file WifiManager.java
Infact, the whole function (843 to makes some interesting reading...
/**
* Allows an application to keep the Wi-Fi radio awake.
* Normally the Wi-Fi radio may turn off when the user has not used the device in a while.
* Acquiring a WifiLock will keep the radio on until the lock is released. Multiple
* applications may hold WifiLocks, and the radio will only be allowed to turn off when no
* WifiLocks are held in any application.
*
* Before using a WifiLock, consider carefully if your application requires Wi-Fi access, or
* could function over a mobile network, if available. A program that needs to download large
* files should hold a WifiLock to ensure that the download will complete, but a program whose
* network usage is occasional or low-bandwidth should not hold a WifiLock to avoid adversely
* affecting battery life.
*
* Note that WifiLocks cannot override the user-level "Wi-Fi Enabled" setting, nor Airplane
* Mode. They simply keep the radio from turning off when Wi-Fi is already on but the device
* is idle.
*/
Click to expand...
Click to collapse
Also, 1094 on references to Multicast locks, could be related...
May be worth looking into this also...
I'll have a proper look over the weekend when I get time (joint birthday bash tomorrow with me and a friend), and been to the pub tonight so not the best time to start sifting though code & make changes lol!
Rawr
Also... References in WifiNative.java
Code:
/**
* Start filtering out multicast packets, to reduce battery consumption
* that would result from processing them, only to discard them.
* @return {@code true} if the operation succeeded, {@code false} otherwise
*/
public native static boolean startPacketFiltering();
/**
* Stop filtering out multicast packets.
* @return {@code true} if the operation succeeded, {@code false} otherwise
*/
public native static boolean stopPacketFiltering();
public native static boolean setPowerModeCommand(int mode);
Possibly disable the Start & Stop Packet Filtering routines, and override the setPowerModeCommand function too (which you already pointed out)
Further down WifiStateTracker.java too... line 2256... It's admitted in there it causes issues!! WTH?!?!
Code:
/*
* There are problems setting the Wi-Fi driver's power
* mode to active when bluetooth coexistence mode is
* enabled or sense.
* <p>
* We set Wi-Fi to active mode when
* obtaining an IP address because we've found
* compatibility issues with some routers with low power
* mode.
* <p>
* In order for this active power mode to properly be set,
* we disable coexistence mode until we're done with
* obtaining an IP address. One exception is if we
* are currently connected to a headset, since disabling
* coexistence would interrupt that connection.
*/
hazaa
yes i see the bluetooth coexist ... i don't know the issue :/
yes i see multicast but need to be enabled in kernel ? (i don't enable for me)
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
Click to expand...
Click to collapse
& is fine to read ^^
Code:
/**
* Allows an application to keep the Wi-Fi radio awake.
* Normally the Wi-Fi radio may turn off when the user has not used the device in a while.
* Acquiring a WifiLock will keep the radio on until the lock is released. Multiple
* applications may hold WifiLocks, and the radio will only be allowed to turn off when no
* WifiLocks are held in any application.
*
* Before using a WifiLock, consider carefully if your application requires Wi-Fi access, or
* could function over a mobile network, if available. A program that needs to download large
* files should hold a WifiLock to ensure that the download will complete, but a program whose
* network usage is occasional or low-bandwidth should not hold a WifiLock to avoid adversely
* affecting battery life.
*
* Note that WifiLocks cannot override the user-level "Wi-Fi Enabled" setting, nor Airplane
* Mode. They simply keep the radio from turning off when Wi-Fi is already on but the device
* is idle.
*/
but the bug is here when the screen is off
I/power ( 163): *** set_screen_state 0
D/WifiService( 163): ACTION_SCREEN_OFF
Click to expand...
Click to collapse
I/power enable the power mode => need to tweak the wifi power state
if tweak the power state of wifi don't work maybe he possible create a "fake screen off"
it's the WifiService.java , need to tweak
Code:
/**
* Return the DHCP-assigned addresses from the last successful DHCP request,
* if any.
* @return the DHCP information
*/
public DhcpInfo getDhcpInfo() {
enforceAccessPermission();
return mWifiStateTracker.getDhcpInfo();
}
private final BroadcastReceiver mReceiver = new BroadcastReceiver() {
@Override
public void onReceive(Context context, Intent intent) {
String action = intent.getAction();
long idleMillis =
Settings.Secure.getLong(mContext.getContentResolver(),
Settings.Secure.WIFI_IDLE_MS, DEFAULT_IDLE_MILLIS);
int stayAwakeConditions =
Settings.System.getInt(mContext.getContentResolver(),
Settings.System.STAY_ON_WHILE_PLUGGED_IN, 0);
if (action.equals(Intent.ACTION_SCREEN_ON)) {
Slog.d(TAG, "ACTION_SCREEN_ON");
mAlarmManager.cancel(mIdleIntent);
mDeviceIdle = false;
mScreenOff = false;
mWifiStateTracker.enableRssiPolling(true);
} else if (action.equals(Intent.ACTION_SCREEN_OFF)) {
Slog.d(TAG, "ACTION_SCREEN_OFF");
mScreenOff = true;
mWifiStateTracker.enableRssiPolling(false);
/*
* Set a timer to put Wi-Fi to sleep, but only if the screen is off
* AND the "stay on while plugged in" setting doesn't match the
* current power conditions (i.e, not plugged in, plugged in to USB,
* or plugged in to AC).
*/
if (!shouldWifiStayAwake(stayAwakeConditions, mPluggedType)) {
WifiInfo info = mWifiStateTracker.requestConnectionInfo();
if (info.getSupplicantState() != SupplicantState.COMPLETED) {
// we used to go to sleep immediately, but this caused some race conditions
// we don't have time to track down for this release. Delay instead, but not
// as long as we would if connected (below)
// TODO - fix the race conditions and switch back to the immediate turn-off
long triggerTime = System.currentTimeMillis() + (2*60*1000); // 2 min
Slog.d(TAG, "setting ACTION_DEVICE_IDLE timer for 120,000 ms");
mAlarmManager.set(AlarmManager.RTC_WAKEUP, triggerTime, mIdleIntent);
// // do not keep Wifi awake when screen is off if Wifi is not associated
// mDeviceIdle = true;
// updateWifiState();
} else {
long triggerTime = System.currentTimeMillis() + idleMillis;
Slog.d(TAG, "setting ACTION_DEVICE_IDLE timer for " + idleMillis + "ms");
mAlarmManager.set(AlarmManager.RTC_WAKEUP, triggerTime, mIdleIntent);
}
}
/* we can return now -- there's nothing to do until we get the idle intent back */
return;
} else if (action.equals(ACTION_DEVICE_IDLE)) {
Slog.d(TAG, "got ACTION_DEVICE_IDLE");
mDeviceIdle = true;
} else if (action.equals(Intent.ACTION_BATTERY_CHANGED)) {
/*
* Set a timer to put Wi-Fi to sleep, but only if the screen is off
* AND we are transitioning from a state in which the device was supposed
* to stay awake to a state in which it is not supposed to stay awake.
* If "stay awake" state is not changing, we do nothing, to avoid resetting
* the already-set timer.
*/
int pluggedType = intent.getIntExtra("plugged", 0);
Slog.d(TAG, "ACTION_BATTERY_CHANGED pluggedType: " + pluggedType);
if (mScreenOff && shouldWifiStayAwake(stayAwakeConditions, mPluggedType) &&
!shouldWifiStayAwake(stayAwakeConditions, pluggedType)) {
long triggerTime = System.currentTimeMillis() + idleMillis;
Slog.d(TAG, "setting ACTION_DEVICE_IDLE timer for " + idleMillis + "ms");
mAlarmManager.set(AlarmManager.RTC_WAKEUP, triggerTime, mIdleIntent);
mPluggedType = pluggedType;
return;
}
mPluggedType = pluggedType;
} else if (action.equals(BluetoothA2dp.ACTION_SINK_STATE_CHANGED)) {
BluetoothA2dp a2dp = new BluetoothA2dp(mContext);
Set<BluetoothDevice> sinks = a2dp.getConnectedSinks();
boolean isBluetoothPlaying = false;
for (BluetoothDevice sink : sinks) {
if (a2dp.getSinkState(sink) == BluetoothA2dp.STATE_PLAYING) {
isBluetoothPlaying = true;
}
}
mWifiStateTracker.setBluetoothScanMode(isBluetoothPlaying);
} else {
return;
}
updateWifiState();
}
/**
* Determines whether the Wi-Fi chipset should stay awake or be put to
* sleep. Looks at the setting for the sleep policy and the current
* conditions.
*
* @see #shouldDeviceStayAwake(int, int)
*/
private boolean shouldWifiStayAwake(int stayAwakeConditions, int pluggedType) {
int wifiSleepPolicy = Settings.System.getInt(mContext.getContentResolver(),
Settings.System.WIFI_SLEEP_POLICY, Settings.System.WIFI_SLEEP_POLICY_DEFAULT);
if (wifiSleepPolicy == Settings.System.WIFI_SLEEP_POLICY_NEVER) {
// Never sleep
return true;
} else if ((wifiSleepPolicy == Settings.System.WIFI_SLEEP_POLICY_NEVER_WHILE_PLUGGED) &&
(pluggedType != 0)) {
// Never sleep while plugged, and we're plugged
return true;
} else {
// Default
return shouldDeviceStayAwake(stayAwakeConditions, pluggedType);
}
}
/**
* Determine whether the bit value corresponding to {@code pluggedType} is set in
* the bit string {@code stayAwakeConditions}. Because a {@code pluggedType} value
* of {@code 0} isn't really a plugged type, but rather an indication that the
* device isn't plugged in at all, there is no bit value corresponding to a
* {@code pluggedType} value of {@code 0}. That is why we shift by
* {@code pluggedType — 1} instead of by {@code pluggedType}.
* @param stayAwakeConditions a bit string specifying which "plugged types" should
* keep the device (and hence Wi-Fi) awake.
* @param pluggedType the type of plug (USB, AC, or none) for which the check is
* being made
* @return {@code true} if {@code pluggedType} indicates that the device is
* supposed to stay awake, {@code false} otherwise.
*/
private boolean shouldDeviceStayAwake(int stayAwakeConditions, int pluggedType) {
return (stayAwakeConditions & pluggedType) != 0;
}
};
tested with this rom for 1/2h and the problem seem not happening.
Now I'm back to defrost 2.1 and still the problem
Hey guys signed up to the forum just to say thanks for looking into this .
Biggest problem with the current ROMs for me is losing WiFi when sleeping, so keep up the good work.
I have 38:e7 network too but I haven't had that issue on dj droid
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
sjauquet said:
tested with this rom for 1/2h and the problem seem not happening.
Now I'm back to defrost 2.1 and still the problem
Click to expand...
Click to collapse
joshjzx said:
I have 38:e7 network too but I haven't had that issue on dj droid
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
Wifi issue is valid for froyo non-sense roms.. Djdroid and Official Froyo are froyo sense roms..
joshjzx said:
I have 38:e7 network too but I haven't had that issue on dj droid
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
I can confirm this. Same Mac-Address an no problems with leaked Sense-Froyo. With defrost I have still the problems. So the bug seems to be fixed on sense-based roms.
Sent from my HTC Desire using Tapatalk
People, all the NON-Sense Froyo (OpenDesire/Defrost/OASPDesire...) Rom have this problem and All the Froyo Sense Roms (HTC Leaked/HTC Official HK) don't have this problem, that is a Fact so please stop say it over and over.
meLIanTQ - I'll work through that code tomorrow, see what I can pull off...
Just for the record, I've tested a N1 running FRF91 (official google build + kernel) completely unmolested... MAC is 38:E7... And it suffers from the EXACT same issue, so it's not just the Desire that this affects... So I will also be building a passion ROM to test on my friends N1 aswell if we manage to sort something for the Desire...
PaulW21781 said:
meLIanTQ - I'll work through that code tomorrow, see what I can pull off...
Just for the record, I've tested a N1 running FRF91 (official google build + kernel) completely unmolested... MAC is 38:E7... And it suffers from the EXACT same issue, so it's not just the Desire that this affects... So I will also be building a passion ROM to test on my friends N1 aswell if we manage to sort something for the Desire...
Click to expand...
Click to collapse
Drivers bug or froyo bug? if its a offcial bug maybe google work on ... and get a patch in futur update
How can help with this problem?
Code:
Sending a DHCP renewal
D/WifiStateTracker( 2717): Disable Bluetooth co-ex mode
V/WifiStateTracker( 2717): AutoIP is disabled
D/WifiStateTracker( 2717): DhcpHandler: DHCP request started
E/wpa_supplicant(11431): ERROR - wpa_driver_tista_private_send - error sending Wext private IOCTL to STA driver (ioctl_cmd = 8000305, drv->errors = 1, errno = 95 - Operation not supported on transport endpoint)
E/wpa_supplicant(11431): ERROR - Failed to handle rx data filter command!
D/WifiStateTracker( 2717): DHCP renewal started
- wifi disconnect on some router every 5-8 min.
- no problem with the same router on Android 2.3.4
- kernel problem?
Solution for this problem
- it is a problem with android >2.3.6
- there is no fix from google
- Change lease time for IP adress at your router from unlimited to 2 weeks or 2 year or 2 month ....
Code:
--------- beginning of /dev/log/main
D/alogcat (12049): stopped
D/alogcat (12049): starting ...
--------- beginning of /dev/log/system
W/InputManagerService( 2717): Window already focused, ignoring focus gain of: [email protected]
D/RadioSignalLevel( 3382): Gsm Radio Signal level: 4
D/RadioSignalLevel( 3382): Gsm Radio Signal level: 4
W/InputManagerService( 2717): Window already focused, ignoring focus gain of: [email protected]
D/WifiStateTracker( 2717): Sending a DHCP renewal
D/WifiStateTracker( 2717): Disable Bluetooth co-ex mode
V/WifiStateTracker( 2717): AutoIP is disabled
D/WifiStateTracker( 2717): DhcpHandler: DHCP request started
E/wpa_supplicant(11431): ERROR - wpa_driver_tista_private_send - error sending Wext private IOCTL to STA driver (ioctl_cmd = 8000305, drv->errors = 1, errno = 95 - Operation not supported on transport endpoint)
E/wpa_supplicant(11431): ERROR - Failed to handle rx data filter command!
D/WifiStateTracker( 2717): DHCP renewal started
I/ActivityManager( 2717): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.motorola.blur.home/.HomeActivity } from pid 2717
V/alogcat (12049): save instance
V/alogcat (12049): paused
I/ActivityManager( 2717): No longer want com.android.settings (pid 10969): hidden #21
D/battery_widget_monitor(10800): onReceive:Intent { act=android.appwidget.action.APPWIDGET_UPDATE cmp=ccc71.bmw/.lib.bmw_widget (has extras) }
W/battery_widget_monitor(10800): total active Widgets:4
I/ActivityManager( 2717): Resumed Activity: org.jtb.alogcat/.LogActivity totalTime: 182 ms
D/alogcat (12049): stopping ...
W/InputManagerService( 2717): Starting input on non-focused client [email protected] (uid=10099 pid=12049)
D/alogcat (12049): stopped
I/EventLogService( 3514): Aggregate from 1329512002062 (log), 1329512002062 (data)
I/ActivityManager( 2717): Starting: Intent { act=com.motorola.blur.apps.ACTION_APPS flg=0x10200000 cmp=com.motorola.blur.home/com.motorola.blur.apps.AppsActivity (has extras) } from pid 3414
I/ActivityManager( 2717): Displayed com.motorola.blur.home/com.motorola.blur.apps.AppsActivity: +621ms
D/dalvikvm(12049): GC_EXPLICIT freed 902K, 64% free 3238K/8967K, external 2939K/3671K, paused 70ms
I/ActivityManager( 2717): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=org.jtb.alogcat/.LogActivity } from pid 3414
V/alogcat (12049): started
I/alogcat (12049): new intent: android.intent.action.MAIN
D/alogcat (12049): stopping ...
D/alogcat (12049): canceling periodic saves
V/alogcat (12049): resumed
D/alogcat (12049): starting ...
I/ActivityManager( 2717): Resumed Activity: org.jtb.alogcat/.LogActivity totalTime: 217 ms
W/InputManagerService( 2717): Starting input on non-focused client [email protected] (uid=10141 pid=3414)
W/KeyCharacterMap(12049): Can't open keycharmap file
W/KeyCharacterMap(12049): Error loading keycharmap file '/data/usr/keychars/qtouch-touchscreen.kcm.bin'. hw.keyboards.65537.devname='qtouch-touchscreen'
W/KeyCharacterMap(12049): Can't open keycharmap file
W/KeyCharacterMap(12049): Error loading keycharmap file '/system/usr/keychars/qtouch-touchscreen.kcm.bin'. hw.keyboards.65537.devname='qtouch-touchscreen'
W/KeyCharacterMap(12049): Can't open keycharmap file
W/KeyCharacterMap(12049): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
Hi,
I found this with TPLINK routers (firewalls, etc.). I think the problem is about TPLINK's DHCP server implementation. I have a TPLINK firewall since 6 month ago, and I have this bug too.
TPLINK's DHCP server deamon (and sometimes their client) has some known incompatbility with ISP's DHCP solutions.
Of course, something is changed in 2.3.6 compared to 2.3.4, because same router is perfectly work with older version.
My workaround about this is disabling DHCP: I use manual IP, or use a "wifi profiler", which turns on/off predefined Fix IP on specified WIFI SSID.
I know it is not a perfect solution in foreign places.
I tried to replace dhcp deamon, wifi drivers, wifi configuration files from 2.3.4, but no success. (I am not a linux expert, so maybe I didn't change every dependent modules, etc.)
DHCP bug is allways present, whenever I'am using open, wep and wpa/wpa2 wireless link - if same DHCP server used.
(OFF: However I have another Wifi bug on CM7/MIUI ROMs with WPA2: after some minutes or transferring a few megabytes, the connection will "stuck" - no more dataflow, I have to reconnect.)
walter79 said:
How can help with this problem?
- wifi disconnect on some router every 5-8 min.
- no problem with the same router on Android 2.3.4
- kernel problem?
Click to expand...
Click to collapse
As a Defy+ user, I'd like to report this bug to official Motorola forum. I've already reported the search bug FC in app drawer. Please tell me how to report.
LeopardSurd said:
As a Defy+ user, I'd like to report this bug to official Motorola forum. I've already reported the search bug FC in app drawer. Please tell me how to report.
Click to expand...
Click to collapse
Copy the Logfile. For me the problem can find on router from Vodafon. (Vodafon Easybox 803 and 903) This router can only buy with a DSL-contract from Vodafon in germany. Maybe it is a kernel problem. I can`t test v3 kernel from motorola. I use a Android 2.3.4 kernel. I tried all v2 gingerbread kernels.
walter79 said:
Copy the Logfile. For me the problem can find on router from Vodafon. (Vodafon Easybox 803 and 903) This router can only buy with a DSL-contract from Vodafon in germany. Maybe it is a kernel problem. I can`t test v3 kernel from motorola. I use a Android 2.3.4 kernel. I tried all v2 gingerbread kernels.
Click to expand...
Click to collapse
ok, thanks!
There is a bug report on Motorola forum:
https://forums.motorola.com/posts/6c79bca040
Any way of using CM's WiFi driver on stock ROM?
Cm7 wifi is way faster than stock!
Can someone test to change ip adress lease time from unlimited to 2 weeks. You have to change this in your router
I found this in the Motorola forums, might help.
https://forums.motorola.com/posts/6808fc89ae
cdlq456 said:
I found this in the Motorola forums, might help.
https://forums.motorola.com/posts/6808fc89ae
Click to expand...
Click to collapse
This a different problem. I think only changing router DHCP settings will work.
I have no problems w Netgear WNR1000 ( this is my router model I think) , my rom is GGL ROM - Defy Green Lens [Android 2.3.6] . WIFI is working as a charm ,it is fast (faster than on CM72 roms) and energy efficient . I used to have problems with roms 2.1 , 2.2 - never with gingerbread roms . But those problems was connected with security settings .
This wifi bug is present in all Android 2.3.6 or 3.2 builds. Samsung has this bug too.
http://code.google.com/p/android/issues/detail?id=20461
There is no fix. You can only change the ip lease time of your router from unlimited to anything else.
I will check that in my router setup .
Solution for this problem
- it is a problem with android >2.3.6
- there is no fix from google
- Change lease time for IP adress at your router from unlimited to 2 weeks or 2 year or 2 month ....
http://review.cyanogenmod.com/#change,6098
Wifi problem is a framework problem. It is fixable by edit framework.jar on each >= android 2.3.6 rom.
I will test the fix on my MS2Ginger rom.
Thanks to quarx he found the fix on cm7 review page.
I know this is an oold thread, but I think that it's importannt that there's a fix that doesn't include changing settings in any rooter:
http://chromloop.com/2011/09/how-to...roblem-wifi-connected-but-no-internet-access/
My friend just bought the Defy+ from a store, new and quite expensive and was REALLY dissapointed to find out that it crashes most(all?) wireless N routers, cause he travels a lot and connects from a lot of random rooters. Applied this easy mod(after Framaroot-ing) and all seems ok after being connected for about 30 minutes now . Hurray!!:victory:
there's a wifi issue on my device when i flash the cm9(9.0-9.1stable or RC or newest nigthly) or cm10 .:crying:
when turn on the wifi ,always show "turning wi-fi on..." .or auto turn off turn on in loop... can't search or add.
but there isn't problem in ruu rom or miui that they both use the android 4.03.
my device is:
htc sensation xe.
cid HTC__622(writed 1111111).
flashed the newlest euorpe 3.33 firmware with the ruu.
1.29 hboot.
unlock.
ship s-off.
before flash new rom i had wipe all cache.
pelase help me...
Well which kernel dud you flash on top?
Sent from my Sensation using Tapatalk 2
blahbl4hblah said:
Well which kernel dud you flash on top?
Sent from my Sensation using Tapatalk 2
Click to expand...
Click to collapse
i hadn't changed the kernel, all are the rom or ruu default
i tried a lot of kernel, and had the same problem on ICS, but it's working on CM10 (bruce's nightly)
mrc90 said:
i tried a lot of kernel, and had the same problem on ICS, but it's working on CM10 (bruce's nightly)
Click to expand...
Click to collapse
please tell me~~~which kernel can work in cm10?
this is logcat:
D/libloc ( 241): loc_eng_ioctl result: client = 0, ioctl_type = RPC_LOC_IOCTL_
INJECT_PREDICTED_ORBITS_DATA, RPC_LOC_API_SUCCESS
D/libloc ( 241): loc_eng_deferred_action_thread. waiting for events
D/RPC ( 241): 3100008c:327681 sending RPC reply (XID 16)
D/ThermalDaemon( 756): CPU[0] frequency limited to 1512000
D/ThermalDaemon( 756): Sensor 'tsens_tz_sensor0' - temperature 53248, threshold
level 0
D/Tethering( 241): sendTetherStateChangedBroadcast 1, 0, 0
D/Tethering( 241): InitialState.processMessage what=4
D/Tethering( 241): sendTetherStateChangedBroadcast 0, 0, 0
D/SoftapController( 120): Softap fwReload - Ok
D/CommandListener( 120): Setting iface cfg
D/NetworkManagementService( 241): rsp <213 00:90:4c:11:22:33 0.0.0.0 0 [down br
oadcast multicast]>
D/NetworkManagementService( 241): flags <[down broadcast multicast]>
D/CommandListener( 120): Trying to bring down wlan0
D/CommandListener( 120): broadcast flag ignored
D/CommandListener( 120): multicast flag ignored
I/BATT_ALG( 130): batt_alg_overtemp_check:temp:377, isOver_temp:0
I/BATT_ALG( 130): vol=3960;curr=63;dis_curr=0;temp=377;id=2;level=82;chg_src=1;
chg_en=1;ov_chg=0;isOver_temp=0;timer=60;safety_count=120
D/dalvikvm( 595): GC_CONCURRENT freed 1556K, 79% free 2616K/12288K, paused 1ms+
2ms
W/BackupManagerService( 241): dataChanged but no participant pkg='com.android.p
roviders.settings' uid=1001
D/dalvikvm( 595): GC_CONCURRENT freed 1635K, 79% free 2700K/12288K, paused 2ms+
3ms
E/wpa_supplicant( 1352): Could not set interface wlan0 flags: Operation not perm
itted
E/wpa_supplicant( 1352): nl80211: Could not set interface 'wlan0' UP
E/wpa_supplicant( 1352): wlan0: Failed to initialize driver interface
D/Tethering( 241): sendTetherStateChangedBroadcast 1, 0, 0
D/dalvikvm( 595): GC_CONCURRENT freed 1682K, 78% free 2733K/12288K, paused 2ms+
2ms
E/WifiHW ( 241): Supplicant not running, cannot connect
E/WifiHW ( 241): Supplicant not running, cannot connect
E/WifiHW ( 241): Supplicant not running, cannot connect
E/WifiStateMachine( 241): Failed to setup control channel, restart supplicant
D/SoftapController( 120): Softap fwReload - Ok
D/NetworkManagementService( 241): rsp <213 a8:26:d9:16:7b:9e 0.0.0.0 0 [down br
oadcast multicast]>
D/NetworkManagementService( 241): flags <[down broadcast multicast]>
D/CommandListener( 120): Setting iface cfg
D/CommandListener( 120): Trying to bring down wlan0
D/CommandListener( 120): broadcast flag ignored
D/CommandListener( 120): multicast flag ignored
E/WifiHW ( 241): Unable to open connection to supplicant on "wlan0": No such f
ile or directory
D/dalvikvm( 241): GC_CONCURRENT freed 1691K, 60% free 4994K/12288K, paused 2ms+
4ms
D/dalvikvm( 595): GC_CONCURRENT freed 1636K, 78% free 2812K/12288K, paused 1ms+
3ms
E/WifiConfigStore( 241): Error parsing configurationjava.io.FileNotFoundExcepti
on: /data/misc/wifi/ipconfig.txt: open failed: ENOENT (No such file or directory
)
E/wpa_supplicant( 1508): wpa_driver_nl80211_driver_cmd: failed to issue private
commands
E/wpa_supplicant( 1508): wpa_driver_nl80211_driver_cmd: failed to issue private
commands
E/wpa_supplicant( 1508): wpa_driver_nl80211_driver_cmd: failed to issue private
commands
E/wpa_supplicant( 1508): wpa_driver_nl80211_driver_cmd: failed to issue private
commands
E/WifiStateMachine( 241): Failed to set country code cn
E/wpa_supplicant( 1508): wpa_driver_nl80211_driver_cmd: failed to issue private
commands
I/wpa_supplicant( 1508): wlan0: CTRL-EVENT-DRIVER-STATE HANGED
E/WifiStateMachine( 241): Failed to set frequency band 0
D/CommandListener( 120): Clearing all IP addresses on wlan0
D/ConnectivityService( 241): ConnectivityChange for WIFI: DISCONNECTED/DISCONNE
CTED
D/ConnectivityService( 241): Attempting to switch to mobile
D/ConnectivityService( 241): Attempting to switch to BLUETOOTH_TETHER
I/Jni WCMLinkStatus ( 512): ssid: Tmobile MAC: 00:00:00:00:00:00 bssid: 00:00
:00:00:00:00 ipaddr: 000.000.000.000 connected: 0
I/Jni WCMLinkStatus ( 512): addr: Ox0
E/Jni WCM_Init( 512): Not initialized
W/NetworkStats( 241): dropping UID delta from unknown iface: iface=wlan0 uid=0
set=DEFAULT tag=0x0 rxBytes=0 rxPackets=0 txBytes=140 txPackets=2 operations=0
D/ConnectivityService( 241): ConnectivityChange for WIFI: DISCONNECTED/DISCONNE
CTED
D/ConnectivityService( 241): Attempting to switch to mobile
D/ConnectivityService( 241): Attempting to switch to BLUETOOTH_TETHER
I/Jni WCMLinkStatus ( 512): ssid: Tmobile MAC: 00:00:00:00:00:00 bssid: 00:00
:00:00:00:00 ipaddr: 000.000.000.000 connected: 0
I/Jni WCMLinkStatus ( 512): addr: Ox0
E/Jni WCM_Init( 512): Not initialized
D/NetworkPolicy( 241): applying policy NetworkPolicy[NetworkTemplate: matchRule
=MOBILE_ALL, subscriberId=valid]: cycleDay=18, warningBytes=2147483648, limitByt
es=-1, lastSnooze=-1 to ifaces [rmnet0]
D/NetworkPolicy( 241): applying policy NetworkPolicy[NetworkTemplate: matchRule
=MOBILE_ALL, subscriberId=valid]: cycleDay=18, warningBytes=2147483648, limitByt
es=-1, lastSnooze=-1 to ifaces [rmnet0]
D/NetworkPolicy( 241): applying policy NetworkPolicy[NetworkTemplate: matchRule
=MOBILE_ALL, subscriberId=valid]: cycleDay=18, warningBytes=2147483648, limitByt
es=-1, lastSnooze=-1 to ifaces [rmnet0]
D/NetworkPolicy( 241): applying policy NetworkPolicy[NetworkTemplate: matchRule
=MOBILE_ALL, subscriberId=valid]: cycleDay=18, warningBytes=2147483648, limitByt
es=-1, lastSnooze=-1 to ifaces [rmnet0]
D/MP-Decision( 747): UP Nw:2.700000 Tw:180 rq:4.900000 seq:195
D/ThermalDaemon( 756): CPU[1] frequency limited to 1512000
D/Tethering( 241): InitialState.processMessage what=4
D/Tethering( 241): sendTetherStateChangedBroadcast 0, 0, 0
I/wpa_supplicant( 1508): wlan0: CTRL-EVENT-TERMINATING
D/MP-Decision( 747): DOWN Ns:2.100000 Ts:270 rq:0.000000 seq:297 (Up time:350)
W/Netd ( 120): No subsystem found in netlink event
D/NetlinkEvent( 120): Unexpected netlink message. type=0x11
I/Jni WCMLinkStatus ( 512): ssid: Tmobile MAC: 00:00:00:00:00:00 bssid: 00:00
:00:00:00:00 ipaddr: 000.000.000.000 connected: 0
I/Jni WCMLinkStatus ( 512): addr: Ox0
E/Jni WCM_Init( 512): Not initialized
I/Jni WCMLinkStatus ( 512): ssid: Tmobile MAC: 00:00:00:00:00:00 bssid: 00:00
:00:00:00:00 ipaddr: 000.000.000.000 connected: 0
I/Jni WCMLinkStatus ( 512): addr: Ox0
E/Jni WCM_Init( 512): Not initialized
D/MP-Decision( 747): UP Nw:2.700000 Tw:180 rq:3.200000 seq:199
D/Tethering( 241): sendTetherStateChangedBroadcast 1, 0, 0
D/Tethering( 241): InitialState.processMessage what=4
D/Tethering( 241): sendTetherStateChangedBroadcast 0, 0, 0
D/SoftapController( 120): Softap fwReload - Ok
D/CommandListener( 120): Setting iface cfg
D/CommandListener( 120): Trying to bring down wlan0
D/CommandListener( 120): broadcast flag ignored
D/CommandListener( 120): multicast flag ignored
E/WifiHW ( 241): Unable to open connection to supplicant on "wlan0": No such f
ile or directory
D/NetworkManagementService( 241): rsp <213 00:90:4c:11:22:33 0.0.0.0 0 [down br
oadcast multicast]>
D/NetworkManagementService( 241): flags <[down broadcast multicast]>
D/MP-Decision( 747): DOWN Ns:2.100000 Ts:270 rq:0.700000 seq:327 (Up time:495)
D/Tethering( 241): MasterInitialState.processMessage what=3
D/Tethering( 241): MasterInitialState.processMessage what=3
D/Tethering( 241): MasterInitialState.processMessage what=3
D/Tethering( 241): MasterInitialState.processMessage what=3
D/CMStats ( 523): Prompting user for opt-in.
D/CMStats ( 523): Prompting user for opt-in.
D/CMStats ( 523): Prompting user for opt-in.
D/CMStats ( 523): Prompting user for opt-in.
D/MP-Decision( 747): UP Nw:2.700000 Tw:180 rq:4.700000 seq:198
D/MP-Decision( 747): DOWN Ns:2.100000 Ts:270 rq:0.000000 seq:274 (Up time:274)
D/dalvikvm( 595): GC_CONCURRENT freed 1611K, 77% free 2916K/12288K, paused 1ms+
3ms
V/MediaScanner( 595): pruneDeadThumbnailFiles... android.database.sqlite.SQLite
[email protected]
V/MediaScanner( 595): /pruneDeadThumbnailFiles... android.database.sqlite.SQLit
[email protected]
I/power ( 241): *** set_screen_state 0
D/Sensors ( 241): handle : 4 en: 0, v010.0 - Try to resolve lock issue
D/Sensors ( 241): lock_status = 4
D/Sensors ( 241): Andy: MPLSensor::enable: lock1
W/MPL-sup ( 241): MLGetAKMComassStatus, gAKMCompassStatus = 0
D/Sensors ( 241): mEnabled = 0x0
D/Sensors ( 241): set_power_states++: enabled_sensors: 0 dmp_started: 1
D/Sensors ( 241): Before if statment: cs:0 rs:0 en_ped:0 da_ped:0 en_g:0 da_g:0
D/Sensors ( 241): Stopping DMP
I/ ( 241): mpu3050_suspend: suspending sensors to 0000
I/ ( 241): mpu3050_suspend: Will resume next to 0070
D/Sensors ( 241): inside if(s_use_timerirq)
D/Sensors ( 241): set_power_states--
D/Sensors ( 241): Andy: MPLSensor::enable: unlock1
D/Sensors ( 241): calling MLStoreCalibration()
D/Sensors ( 241): MPLSensor::enable--1
D/SurfaceFlinger( 123): About to give-up screen, flinger = 0xd81918
E/msm8660.gralloc( 123): In fb_enableHDMIOutput: externaltype = 0
I/SamplingRateChangeProcessor( 241): Increased sampling rate.
V/AudioHardwareMSM8660( 126): setParameters() screen_state=off
D/OpenGLRenderer( 435): Flushing caches (mode 0)
D/AccelerometerListener( 498): enable(false)
I/BATT_ALG( 130): batt_alg_overtemp_check:temp:377, isOver_temp:0
I/BATT_ALG( 130): vol=4017;curr=317;dis_curr=0;temp=377;id=2;level=82;chg_src=1
;chg_en=1;ov_chg=0;isOver_temp=0;timer=60;safety_count=180
I/power ( 241): *** set_screen_state 1
D/Sensors ( 241): handle : 4 en: 1, v010.0 - Try to resolve lock issue
D/Sensors ( 241): lock_status = 2
D/Sensors ( 241): Andy: MPLSensor::enable: lock1
D/Sensors ( 241): mEnabled = 0x10
D/Sensors ( 241): set_power_states++: enabled_sensors: 16 dmp_started: 0
D/Sensors ( 241): Before if statment: cs:0 rs:1 en_ped:0 da_ped:0 en_g:0 da_g:0
D/Sensors ( 241): STOP timerirq_1
I/WindowManager( 241): No lock screen!
D/Sensors ( 241): Starting DMP
I/ ( 241): mpu3050_resume: Resuming to 0070
D/Sensors ( 241): Exit: Starting DMP
D/Sensors ( 241): set_power_states--
D/Sensors ( 241): Andy: MPLSensor::enable: unlock1
D/Sensors ( 241): MPLSensor::enable--1
D/Sensors ( 241): (llu)G_Delay = 200
I/ ( 241): mpu3050_resume: Resuming to 0070
I/ ( 241): mpu3050_suspend: suspending sensors to 0070
I/ ( 241): mpu3050_suspend: Will resume next to 0070
I/MPL-ml ( 241): Actual ODR: 25 Hz
D/Sensors ( 241): (llu)G_Delay = 66
I/ ( 241): mpu3050_resume: Resuming to 0070
I/ ( 241): mpu3050_suspend: suspending sensors to 0070
I/ ( 241): mpu3050_suspend: Will resume next to 0070
I/MPL-ml ( 241): Actual ODR: 25 Hz
I/SamplingRateChangeProcessor( 241): Decreased sampling rate.
D/SurfaceFlinger( 123): Screen about to return, flinger = 0xd81918
E/msm8660.gralloc( 123): In fb_enableHDMIOutput: externaltype = 0
V/AudioHardwareMSM8660( 126): setParameters() screen_state=on
D/MP-Decision( 747): UP Nw:2.700000 Tw:180 rq:4.400000 seq:197
D/AccelerometerListener( 498): enable(false)
D/MP-Decision( 747): DOWN Ns:2.100000 Ts:270 rq:0.000000 seq:327 (Up time:441)
D/Tethering( 241): sendTetherStateChangedBroadcast 1, 0, 0
E/wpa_supplicant( 1526): Could not set interface wlan0 flags: Operation not perm
itted
E/wpa_supplicant( 1526): nl80211: Could not set interface 'wlan0' UP
E/wpa_supplicant( 1526): wlan0: Failed to initialize driver interface
E/WifiHW ( 241): Supplicant not running, cannot connect
E/WifiHW ( 241): Supplicant not running, cannot connect
E/WifiStateMachine( 241): Failed to setup control channel, restart supplicant
D/SoftapController( 120): Softap fwReload - Ok
D/NetworkManagementService( 241): rsp <213 a8:26:d9:16:7b:9e 0.0.0.0 0 [down br
oadcast multicast]>
D/CommandListener( 120): Setting iface cfg
D/NetworkManagementService( 241): flags <[down broadcast multicast]>
D/CommandListener( 120): Trying to bring down wlan0
D/CommandListener( 120): broadcast flag ignored
D/CommandListener( 120): multicast flag ignored
E/WifiConfigStore( 241): Error parsing configurationjava.io.FileNotFoundExcepti
on: /data/misc/wifi/ipconfig.txt: open failed: ENOENT (No such file or directory
)
E/wpa_supplicant( 1677): wpa_driver_nl80211_driver_cmd: failed to issue private
commands
E/wpa_supplicant( 1677): wpa_driver_nl80211_driver_cmd: failed to issue private
commands
E/wpa_supplicant( 1677): wpa_driver_nl80211_driver_cmd: failed to issue private
commands
E/wpa_supplicant( 1677): wpa_driver_nl80211_driver_cmd: failed to issue private
commands
E/WifiStateMachine( 241): set suspend optimizations failed!
E/wpa_supplicant( 1677): wpa_driver_nl80211_driver_cmd: failed to issue private
commands
E/WifiStateMachine( 241): Failed to set country code cn
E/wpa_supplicant( 1677): wpa_driver_nl80211_driver_cmd: failed to issue private
commands
E/WifiStateMachine( 241): Failed to set frequency band 0
E/wpa_supplicant( 1677): wpa_driver_nl80211_driver_cmd: failed to issue private
commands
W/wpa_supplicant( 1677): wlan0: Failed to initiate AP scan
E/wpa_supplicant( 1677): wpa_driver_nl80211_driver_cmd: failed to issue private
commands
E/wpa_supplicant( 1677): wpa_driver_nl80211_driver_cmd: failed to issue private
commands
I/wpa_supplicant( 1677): wlan0: CTRL-EVENT-DRIVER-STATE HANGED
W/wpa_supplicant( 1677): wlan0: Failed to initiate AP scan
E/wpa_supplicant( 1677): wpa_driver_nl80211_driver_cmd: failed to issue private
commands
D/CommandListener( 120): Clearing all IP addresses on wlan0
I/Jni WCMLinkStatus ( 512): ssid: Tmobile MAC: 00:00:00:00:00:00 bssid: 00:00
:00:00:00:00 ipaddr: 000.000.000.000 connected: 0
I/Jni WCMLinkStatus ( 512): addr: Ox0
E/Jni WCM_Init( 512): Not initialized
I/Jni WCMLinkStatus ( 512): ssid: Tmobile MAC: 00:00:00:00:00:00 bssid: 00:00
:00:00:00:00 ipaddr: 000.000.000.000 connected: 0
I/Jni WCMLinkStatus ( 512): addr: Ox0
E/Jni WCM_Init( 512): Not initialized
D/Tethering( 241): InitialState.processMessage what=4
D/Tethering( 241): sendTetherStateChangedBroadcast 0, 0, 0
W/NetworkStats( 241): dropping UID delta from unknown iface: iface=wlan0 uid=0
set=DEFAULT tag=0x0 rxBytes=0 rxPackets=0 txBytes=384 txPackets=6 operations=0
I/wpa_supplicant( 1677): wlan0: CTRL-EVENT-TERMINATING
W/Netd ( 120): No subsystem found in netlink event
D/NetlinkEvent( 120): Unexpected netlink message. type=0x11
I/Jni WCMLinkStatus ( 512): ssid: Tmobile MAC: 00:00:00:00:00:00 bssid: 00:00
:00:00:00:00 ipaddr: 000.000.000.000 connected: 0
I/Jni WCMLinkStatus ( 512): addr: Ox0
E/Jni WCM_Init( 512): Not initialized
I/Jni WCMLinkStatus ( 512): ssid: Tmobile MAC: 00:00:00:00:00:00 bssid: 00:00
:00:00:00:00 ipaddr: 000.000.000.000 connected: 0
I/Jni WCMLinkStatus ( 512): addr: Ox0
E/Jni WCM_Init( 512): Not initialized
D/Tethering( 241): sendTetherStateChangedBroadcast 1, 0, 0
D/Tethering( 241): InitialState.processMessage what=4
D/Tethering( 241): sendTetherStateChangedBroadcast 0, 0, 0
D/SoftapController( 120): Softap fwReload - Ok
D/CommandListener( 120): Setting iface cfg
D/CommandListener( 120): Trying to bring down wlan0
D/CommandListener( 120): broadcast flag ignored
D/CommandListener( 120): multicast flag ignored
D/NetworkManagementService( 241): rsp <213 00:90:4c:11:22:33 0.0.0.0 0 [down br
oadcast multicast]>
D/NetworkManagementService( 241): flags <[down broadcast multicast]>
First off, I just started using this rom last month, but my old TF101 is like a new tablet. Outstanding work!
I am having an issue connecting to a VPN using the built-in android VPN settings. The VPN server is a simple PPTP VPN running on a Win 7 system, setup through the "Incoming Connections" dialog. Earlier today, the tablet was able to connect to the VPN server no problem; however, it randomly stopped connecting this evening.
When connecting to the VPN, the built-in app starts sitting at "Connecting..." until it changes to "Disconnected". The server is setup correctly and still running as a Win 7 laptop is still able to connect without a hitch using the same wifi connection as the tablet. I also tried clearing cache/Dalvik and fixing permissions to no avail.
The problem might not be specific to this device/rom/android version since a gingerbread phone is also having a similar issue using 3g or wifi. The phone was able to connect earlier in the week but stopped connecting a few days ago. I have pasted the relevant section of the aLogcat log of the tablet below to shed some light on the subject. Can anyone give any input on why this issue might have just started cropping up?
I/mtpd ( 4222): Using protocol pptp
I/mtpd ( 4222): Connecting to ***.***.***.*** port 1723 via wlan0
I/mtpd ( 4222): Connection established (socket = 11)
D/mtpd ( 4222): Sending SCCRQ
D/mtpd ( 4222): Received SCCRP -> Sending OCRQ (local = 20020)
I/mtpd ( 4222): Tunnel established
D/mtpd ( 4222): Received OCRQ (remote = 63187)
I/h mtpd ( 4222): Session established
I/mtpd ( 4222): Creating PPPoX socket
I/mtpd ( 4222): Starting pppd (pppox = 12)
I/mtpd ( 4222): Pppd started (pid = 4223)
I/pppd ( 4223): Using PPPoX (socket = 12)
D/pppd ( 4223): using channel 2
I/pppd ( 4223): Using interface ppp0
I/pppd ( 4223): Connect: ppp0 <-->
D/EthernetService( 752): interfaceAdded: ppp0
D/EthernetService( 752): addInterface: ppp0
D/EthernetService( 752): addInterface: I cannot manage ppp0
D/EthernetService( 752): interfaceLinkStateChanged for ppp0, up = false
l3py said:
First off, I just started using this rom last month, but my old TF101 is like a new tablet. Outstanding work!
I am having an issue connecting to a VPN using the built-in android VPN settings. The VPN server is a simple PPTP VPN running on a Win 7 system, setup through the "Incoming Connections" dialog. Earlier today, the tablet was able to connect to the VPN server no problem; however, it randomly stopped connecting this evening.
When connecting to the VPN, the built-in app starts sitting at "Connecting..." until it changes to "Disconnected". The server is setup correctly and still running as a Win 7 laptop is still able to connect without a hitch using the same wifi connection as the tablet. I also tried clearing cache/Dalvik and fixing permissions to no avail.
The problem might not be specific to this device/rom/android version since a gingerbread phone is also having a similar issue using 3g or wifi. The phone was able to connect earlier in the week but stopped connecting a few days ago. I have pasted the relevant section of the aLogcat log of the tablet below to shed some light on the subject. Can anyone give any input on why this issue might have just started cropping up?
I/mtpd ( 4222): Using protocol pptp
I/mtpd ( 4222): Connecting to ***.***.***.*** port 1723 via wlan0
I/mtpd ( 4222): Connection established (socket = 11)
D/mtpd ( 4222): Sending SCCRQ
D/mtpd ( 4222): Received SCCRP -> Sending OCRQ (local = 20020)
I/mtpd ( 4222): Tunnel established
D/mtpd ( 4222): Received OCRQ (remote = 63187)
I/h mtpd ( 4222): Session established
I/mtpd ( 4222): Creating PPPoX socket
I/mtpd ( 4222): Starting pppd (pppox = 12)
I/mtpd ( 4222): Pppd started (pid = 4223)
I/pppd ( 4223): Using PPPoX (socket = 12)
D/pppd ( 4223): using channel 2
I/pppd ( 4223): Using interface ppp0
I/pppd ( 4223): Connect: ppp0 <-->
D/EthernetService( 752): interfaceAdded: ppp0
D/EthernetService( 752): addInterface: ppp0
D/EthernetService( 752): addInterface: I cannot manage ppp0
D/EthernetService( 752): interfaceLinkStateChanged for ppp0, up = false
Click to expand...
Click to collapse
I can confirm I have the same issue. 4.3 rom was fine, 4.4 is not connecting. Definitely not a issue with the vpn or details as I have tested on my phone and pc.
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!