Database Info

[DEV] Fixing Wifi-Sleep issues

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

[Q] Wireless-N not work

Have faced a problem that my HTC One S don't connect to wi-fi N access point. It stucks at authentication. If I disable N-mode at AP - the phone connects normally. Does anybody have such problem? In both cases WPA2 is used.

bump.... so no one have such problems? or no one is using wifi-n?

have you try the advanced option of wi-fi?
option ---> wi-fi ----> advanced ----> better wi-fi performance?

igooor87 said:
have you try the advanced option of wi-fi?
option ---> wi-fi ----> advanced ----> better wi-fi performance?
Click to expand...
Click to collapse
Yes, I have tried but no luck. Here is logcat:
I/wpa_supplicant( 4356): wlan0: Trying to associate with yy:yy:yy:yy:yy:yy (SSID='MY-WLAN' freq=2472 MHz)
I/wpa_supplicant( 4356): Cancelling scan request -
I/wpa_supplicant( 4356): wpa_supplicant_set_state -
I/wpa_supplicant( 4356): WEXT: Custom wireless event: 'BEACONIEs='
I/wpa_supplicant( 4356): wpa_supplicant_set_state -
I/wpa_supplicant( 4356): wlan0: Associated with yy:yy:yy:yy:yy:yy
I/wpa_supplicant( 4356): Cancelling scan request -
I/wpa_supplicant( 4356): wpa_supplicant_set_state -
I/wpa_supplicant( 4356): [SeamLess] We are roaming state is drv->flag_roam_state is 0drv->flag_roaming is 0
I/wpa_supplicant( 4356): [SeamLess] We are roaming state is drv->flag_roam_state is 0drv->flag_disconnect_state is 0
I/wpa_supplicant( 4356): [SeamLess] Flag roam state is mlme_event_disconnect:1514
I/wpa_supplicant( 4356): [SeamLess] We are in roaming_scan_handler to register to timeout handlers
I/wpa_supplicant( 4356): [SeamLess] We requested scan to connect
I/wpa_supplicant( 4356): Setting scan request: 0 sec 0 usec
I/wpa_supplicant( 4356): wpa_supplicant_trigger_scan +
W/wpa_supplicant( 4356): [EAP-MSG] EAP [email protected]: eap_methods not available
I/wpa_supplicant( 4356): [SeamLess] This is already connected so rejected to yy:yy:yy:yy:yy:yy
I/wpa_supplicant( 4356): [SeamLess] flag_disconnect is set i.e., Seamless is give it up
I/wpa_supplicant( 4356): [SeamLess] Event DISASSOC is Generated seamless_roaming_disconnect:438
I/wpa_supplicant( 4356): wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
I/wpa_supplicant( 4356): WPA: Auto connect enabled: try to reconnect (wps=0)
I/wpa_supplicant( 4356): Setting scan request: 0 sec 500000 usec
I/wpa_supplicant( 4356): Setting scan request: 0 sec 100000 usec
I/wpa_supplicant( 4356): wlan0: CTRL-EVENT-DISCONNECTED bssid=yy:yy:yy:yy:yy:yy reason=0
I/wpa_supplicant( 4356): wpa_supplicant_set_state -
BUT, the passphase is correct. If I just turn off N-mode in access point it connects normally.

Does your router have the option for WPA+WPA2 not just one or the other? If so try enabling the setting to use both.
Sent from my HTC One S using xda premium

doktortaru said:
Does your router have the option for WPA+WPA2 not just one or the other? If so try enabling the setting to use both.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Currently I configure it to use only WPA2 (CCMP/AES cipher) but also tryed with WPA (TKIP cipher) and already tryed to use both WPA+WPA2 - no luck.
P.S.
I'm also have HTC Incredible S and it connects to AP normally in all possible modes while One S won't.

WLAN
Working fine on my Phone.. Problems with your Rom?

Andy2502 said:
Working fine on my Phone.. Problems with your Rom?
Click to expand...
Click to collapse
Have checked with 3 different roms including official. What AP do you have and which speed it suppors (150/300mbps)?

i had a similar issue but my phone would reboot after failed attempts to connect.
what is your baseband? i was on 0.15 and the phone finally connected when i used the TMOUS RUU to update to 0.16.

suhailtheboss said:
i had a similar issue but my phone would reboot after failed attempts to connect.
what is your baseband? i was on 0.15 and the phone finally connected when i used the TMOUS RUU to update to 0.16.
Click to expand...
Click to collapse
radio is 0.16.31501S.17_2_10.23.31501S.10L and the rom is 1.78.401.2, previously was on official T-Mobile DE rom, but currently on LeeDroid. With both roms wifi won't auth with AP in N-mode

Solved by compiling latest compat-wireless for AP.

darkside_ua said:
Solved by compiling latest compat-wireless for AP.
Click to expand...
Click to collapse
Hi, i have the same issue with the original ROM 1.78.401.2.
Could you please explain me how to solve this? My HTC is already rooted...
Thanks

Wireless Display Adapters (Miracast)

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

Beanstalk and WiFi?

I am having an issue where my WiFi keeps disconnecting. Its only on my home router that I've noticed. Its a fritzbox. I have reinstalled the ROM. Plus wiped everything. No restore with titainium this time just in case. (I only restore user apps anyway.) This has been happening on the last two builds. Which strikes me as odd because I have been running Scotts cm10 with out issue from almost the beginning. And switched to beanstalk on day one. Its just been the last two builds of beanstalk giving me a hard time. Let me know your ideas. I've searched through the menus, but with all these added features I could have missed something.
Sent from my SGH-I997 using xda app-developers app

Same here...
Having the same basic issue, though it's more of a minor annoyance than anything else. Get kicked off wifi. Turn wifi off and then back on. Then reconnect and usually it works.
And I should say that this is just a minor, minor glitch in what is otherwise an awesome ROM. Thanks for all your work on it, Scott!
Any thoughts on wifi fixes?

I am happy with CM10 11/15 release. Everything is working and I recommend others to go to that release.
New releases, codename, etc. is just a toy for developers to experiment. There will always be something not working or working incorrectly.
I have been fed by "ultra smooth", "buttery smooth", etc. BS, basically no changes from earlier CM10. It is smooth until you have some app taking more cpu or available memory is close to 0. Then all smoothness disappears.
Just find a version which works for you and stop making troubles to yourself with newer and newer versions.
0.02c

Newest working for me fine
Sent from my SGH-I997 using Tapatalk 2

Scott's Beanstalk build does the same thing to me (haven't tried the 2/3 release), it seems to only happen when I turn WiFi sleep on. If I leave it set to never sleep, it doesn't disconnect.

I've been having this issue too, I think it has been happening for me since switching to any ICS or JB rom but it seems worse lately. I've been tempted to switch back to the latest official GB release to see if I still have the issue but haven't tried that yet
I've checked the wifi sleep settings and tried all possible options. If seems to go to sleep and never wakeup. If I am hooked to power it doesn't seem to happen or if there is something active it doesn't happen.
In the logcat it happens about here:
I/EventLogService( 1047): Aggregate from 1358904794591 (log), 1358904794591 (data)
W/wpa_supplicant(19752): wlan0: Failed to initiate AP scan
W/ThrottleService( 443): unable to find stats for iface pdp0
W/wpa_supplicant(19752): wlan0: Failed to initiate AP scan
I/wpa_supplicant(19752): wlan0: CTRL-EVENT-DISCONNECTED bssid=c0:c1:c0:dc:f5:cc reason=1
E/wpa_supplicant(19752): wpa_driver_nl80211_driver_cmd: failed to issue private commands
D/CommandListener( 142): Clearing all IP addresses on wlan0
D/ConnectivityService( 443): ConnectivityChange for WIFI: DISCONNECTED/DISCONNECTED
D/ConnectivityService( 443): Attempting to switch to mobile
D/ConnectivityService( 443): Attempting to switch to BLUETOOTH_TETHER
D/NetUtils( 443): android_net_utils_resetConnections in env=0x2a292630 clazz=0xef500001 iface=wlan0 mask=0x3
D/ConnectivityService( 443): resetConnections(wlan0, 3)
W/wpa_supplicant(19752): wlan0: Failed to initiate AP scan
D/NetUtils( 443): android_net_utils_resetConnections in env=0x2a292630 clazz=0xf1b00001 iface=wlan0 mask=0x3
D/ConnectivityService( 443): ConnectivityChange for WIFI: DISCONNECTED/DISCONNECTED
D/ConnectivityService( 443): Attempting to switch to mobile
D/ConnectivityService( 443): Attempting to switch to BLUETOOTH_TETHER
D/ConnectivityService( 443): resetConnections(wlan0, 3)
D/dalvikvm( 806): GC_CONCURRENT freed 625K, 22% free 4256K/5408K, paused 7ms+2ms, total 129ms
D/dalvikvm( 443): GC_CONCURRENT freed 1861K, 40% free 16643K/27640K, paused 10ms+9ms, total 102ms
D/dalvikvm( 443): WAIT_FOR_CONCURRENT_GC blocked 52ms
W/wpa_supplicant(19752): wlan0: Failed to initiate AP scan
W/wpa_supplicant(19752): wlan0: Failed to initiate AP scan
W/wpa_supplicant(19752): wlan0: Failed to initiate AP scan
W/wpa_supplicant(19752): wlan0: Failed to initiate AP scan
W/wpa_supplicant(19752): wlan0: Failed to initiate AP scan
W/wpa_supplicant(19752): wlan0: Failed to initiate AP scan
W/wpa_supplicant(19752): wlan0: Failed to initiate AP scan
W/wpa_supplicant(19752): wlan0: Failed to initiate AP scan
The "Failed to initiate AP scan" repeats until wifi is disabled and restarted.

Only issue I have with the latest 2/3 build is that when I connect BT to car for talk... the sound comes across like I'm listening to a Walkie Talkie from the person I'm talking to.
They here me fine though. Also. The BT to Streaming music sounds good.
I ended up just wiping and restoring the PREVIOUS build which was working perfect.

I'm at a loss on this one. I reverted to stock and then tried Aeon for a while and had the same issue, although Aeon would sometimes bring the Wifi back on its own without me having to disable wifi and re-enable it. With Aeon I had a problem with the screen not coming back on after a deep sleep that I had with some other GB releases so I decided to go back up to Bean Stalk.
Did a complete format, wipe, and install and I'm having the same wifi issue. It acts like "Keep Wi-Fi on during sleep" is set to "Only when plugged in" even though I have it set to Always. When it wakes back up the only way to bring wifi back is to disable/enable it. I'm tempted to start timing how long it takes
Some more logcat info:
I/PowerManagerService( 428): Going to sleep due to screen timeout...
I/wpa_supplicant( 595): wlan0: CTRL-EVENT-DISCONNECTED bssid=c0:c1:c0:dc:f5:cc reason=1
E/wpa_supplicant( 595): wpa_driver_nl80211_driver_cmd: failed to issue private commands
D/CommandListener( 142): Clearing all IP addresses on wlan0
D/ConnectivityService( 428): ConnectivityChange for WIFI: DISCONNECTED/DISCONNECTED
D/ConnectivityService( 428): Attempting to switch to mobile
D/ConnectivityService( 428): Attempting to switch to BLUETOOTH_TETHER
D/NetUtils( 428): android_net_utils_resetConnections in env=0x2a170ed0 clazz=0x6ac00001 iface=wlan0 mask=0x3
D/ConnectivityService( 428): resetConnections(wlan0, 3)
W/wpa_supplicant( 595): wlan0: Failed to initiate AP scan
D/dalvikvm( 587): GC_CONCURRENT freed 503K, 24% free 3101K/4080K, paused 7ms+53ms, total 152ms
D/SurfaceFlinger( 145): Screen released, type=0 flinger=0x2a007318
E/wpa_supplicant( 595): wpa_driver_nl80211_driver_cmd: failed to issue private commands
V/TransportControlView( 428): Create TCV com.android.internal.policy.impl.keyguard.KeyguardTransportControlView{41677960 V.E..... ......I. 0,0-0,0 #102030a android:id/keyguard_transport_control}
D/dalvikvm( 428): JIT code cache reset in 4 ms (1048448 bytes 1/0)
D/dalvikvm( 428): GC_CONCURRENT freed 1669K, 37% free 9285K/14728K, paused 3ms+9ms, total 103ms
V/KeyguardViewManager( 428): State lockbackground:null
W/wpa_supplicant( 595): wlan0: Failed to initiate AP scan
D/dalvikvm( 428): GC_FOR_ALLOC freed 664K, 37% free 9354K/14728K, paused 59ms, total 61ms
W/wpa_supplicant( 595): wlan0: Failed to initiate AP scan
W/wpa_supplicant( 595): wlan0: Failed to initiate AP scan
D/Tethering( 428): MasterInitialState.processMessage what=3
D/ConnectivityService( 428): handleInetConditionChange: no active default network - ignore
D/PicasaUploaderSyncManager( 1602): active network: null

I fixed mine by shutting off WiFi optimization in the WiFi advanced settings. All is back to normal now.
Sent from my SGH-I997 using xda app-developers app

I might have figured out my problem, hopefully I'm not jinxing myself by posting this.
I installed Wifi Fixer and that didn't really help, but it would make the network reconnect after it dropped. What really helped was turning on the logging and seeing what was happening.
I have a Linksys router that is 802.11A/N and 802.11B/G compatible. Well I had the same ssid for for sets of bands so I think there is either weird power saving on the A/N or something weird where it would switch back and forth and get into some weird state. I changed the ssid on my A/N to something different and it hasn't dropped in a while now
After I'm sure it is fixed I might add the A/N ssid to my phone to see if that works.
Hopefully this helps someone else out there.

Well I still had issues with Beanstalk (the latest 4.2.1 version). Last night I flashed back to stock GB and I'm going to see if the wifi problem persists for me.
I'd really like to be on a ICS/JB rom but with the wifi constantly freaking out and the crazy battery life I might end up sticking with GB.

What is the best GB for Infuse?
I am done playing QA. 8 months testing and I can't stay with : GPS is not turning up if not used for some time ( Maps or other GPS can't turn it on. Have to reboot ), 720p not working, 480p produces video which gallery sometimes have problems creating/viewing thumbnails (really slow response from phone and eating battery; if this happens screen stays black for minutes until it starts re-drawing), WiFi issues (I stopped using WiFi tethering, which was the main reason to try 4+), very frequent DEBUG logs (OS Monitor) eat CPU for no reason, bluetooth issues only on my phone.

[Q] VPN Connection Problem - KatKiss .029

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.