[Galaxy S 4 Active Q&A, Help & Troubleshooting] Edubaires:
I'll try again though From what I've seen on the Internet'm not the only one with this problem.

possible solutions?:

1 "that the issue is with the core, which control communication HW / OS, That it is some kind of HW Error, Given That neither stock or custom ROMs make any difference "

2 "If it gets stuck on" turning on "then ITS most likely to a system error .this is common in the community rooting the wifi if the file system Incorrectly was written) I have no idea how yours Became corrupt. "

3 "apparently some Kernel eliminates the problem"

4 "Instead Cyanogen ROM based Helps in every aspect."

question:

1. I saw a video on youtube "How to Fix Problems Android Wifi - Samsung Galaxy S4 - All Samsung phones [HD]" ( https: //www. youtube .com /watchv=26kFIPQ_WMY ) to s4 i9500) to flash zip:

"Modem wifi fix - Custom Kernel (Faux for S4) - Source for kernel and modem file"

by cwm this problem was solved, there is something similar for the gt-i9295?

2. I remembered that before you can successfully root (withmythi_cwm_swipe_3050.tar), use F-Auto-Root-jflte-jfltexx- gti9505.zip and Towel Root, root checker installed, checked "this device does not have any adequate root access", can it be that this is one of the reasons why not to start wifi bluetooth and corrupt data?

you know anything about this?

also come to think that could be installed applications eh: duu battery mod, greenify, FPSE, whatsapp uninstall but no difference. I have a theory that it is a software issue (although I have my doubts), sometimes the bluetooth symbol appears repeatedly seconds Qusiera turn blinking like that but something prevents you from starting,

I found this I found interesting and copy a fragment

Quote:

"3. Provide a proper wpa_supplicant.conf for your device

Providing a wpa_supplicant.conf it's important because the control

socket for android is specified in this file (ctrl_interface= ). This file

should be copied by your AndroidBoard.mk to

$(TARGET_OUT_ETC)/wifi (usually

/system/etc/wifi/wpa_supplicant.conf ). This location will be used

on wpa_supplicant service from init.rc.

There are two different ways in which wpa_supplicant can be

configured, one is to use a "private" socket in android namespace,

created by socket_local_client_connect() function in wpa_ctrl.c

and another is by using a standard unix socket.

Minimum required config options in wpa_supplicant.conf :

- Android private socket

ctrl_interface=wlan0

update_config=1

- Unix standard socket

5ctrl_interface=DIR=/data/system/wpa_supplicant GROUP=wifi

update_config=1

Depending on your driver you might also want to add:

ap_scan=1

If you have AP association problems with should change to

ap_scan=0 to let the driver do the association instead of

wpa_supplicant.

Seems that you can add ap_scan=1 to your wpa_supplicant.conf

depending on the drivers you have.

After some more research on the subject of ap_scan i found that:

# AP scanning/selection

# By default, wpa_supplicant requests driver to perform AP

scanning and then

# uses the scan results to select a suitable AP. Another alternative

is to

# allow the driver to take care of AP scanning and selection and

use

# wpa_supplicant just to process EAPOL frames based on IEEE

802.11 association

# information from the driver.

# 1: wpa_supplicant initiates scanning and AP selection

# 0: driver takes care of scanning, AP selection, and IEEE 802.11

association

# parameters (e.g., WPA IE generation); this mode can also be

used with

# non-WPA drivers when using IEEE 802.1X mode; do not try to

associate with

# APs (i.e., external program needs to control association). This

mode must

# also be used when using wired Ethernet drivers.

# 2: like 0, but associate with APs using security policy and SSID

(but not

# BSSID); this can be used, e.g., with ndiswrapper and NDIS

driver to

# enable operation with hidden SSIDs and optimized roaming; in

this mode,

# only the first network block in the configuration file is used and

this

# configuration should have explicit security policy (i.e., only one

option

# in the lists) for key_mgmt, pairwise, group, proto variables

It seems that addind ap_scan=1 imposes that

wpa_supplicant.conf handles the scanning and AP selection. IF

there's something wrong with the driver, and not with

wpa_supplicant as i originaly thought, this could bypass the

problem.

So I added ap_scan=1 just before the device identification lines in

wpa_supplicant.conf, reeboted, and now the wifi and bluetooth

toggle normaly. I've tried ap_scan=0 (the driver handles the

scanning) and the problem returns, so ap_scan=1 does allow you

to toggle the wifi and BT on."