Database Users

Camera Failure

Phone is taking pics only when the wifi is on.
If wifi is not on, the pic is not saved, camera app closes and it says camera failure.
i am on froyo jpf
any suggestions?

sahilrana said:
Phone is taking pics only when the wifi is on.
If wifi is not on, the pic is not saved, camera app closes and it says camera failure.
i am on froyo jpf
any suggestions?
Click to expand...
Click to collapse
Go to Settings> Location and Security and Uncheck Use Wireless Connection. It will work fine then

jaskiratsingh said:
Go to Settings> Location and Security and Uncheck Use Wireless Connection. It will work fine then
Click to expand...
Click to collapse
Same issue on JPM, if wifi is on, all pictures are correctly taken. If wifi is off mostly the first picture succeeds but second cause the camera failure.
Does somebody know of another type of fix, patched Camera.apk or something? Wireless location is extremely handy for google maps etc.

I have been having this problem since JPF and I was hoping JPM fixed it..but no. And these were the updates the KIES gave me. Now I can't even connect to KIES anymore. Samsung has really messed up this whole thing... man...

JPM fixed this problem for me (flashed with Odin), you guys should try a factory reset.

Factory Reset did not fix that problem for me...

Going to reflash JPM with factory reset and wipe cache (both from recovery), will report back....

Ok, somehow the following steps at first seemed to fix my problem with the camera:
1. Before reflashing JPM firmware I did the following from recovery:
1a. wipe data/factory reset (scroll down to Yes -- delete all user)
1b. wipe cache
1c. reboot system now
2. Turn off phone
3. Turn on phone in download mode (volume down+home+power)
4. Flash JPM with odin
5. After flash and reboot again back into recovery (thru adb reboot recovery or volume up+volume down+home+power)
6. Again wiped data/factory reset & wipe cache & reboot (exact same steps as 1a-1c)
After these steps no camera failures...but after manually setting the apn of my provider ..... camera failures even with 3g turned off
Deleted the apn and no camera failures anymore :S So I think my choice is: mobile 3g internet OR fully functioning camera.
3g settings: mmc 204, mnc 16, verification pap, apn type internet (T-Mobile NL)

I too cant connect with Kies with JPM rom and the same camera problem...
-Techass.wordpress.com

I don't know exactly what I did but after a few hours of playing around with settings and APN widgets the camera is now working correctly, no camera failures to date.
First I downloaded an apns-conf.xml from cyanogen firmware where the APN settings for my provider were available (since I had to manually enter them and that was the moment the camer failure started to occur). I copied the apns-conf.xml from my phone (/etc) to my computer and added the lines for my provider and pushed them back to my phone. Onfortunately this did not fix the problem.
Then I tried numerous APN widgets to disable the apn (with prefix) or switch to an empty APN, both also unsuccesfull. Uninstalled these apps and widgets again.
After all these tries, I dove into the application settings and for some reason I thought it was a good idea to clean the data of the, in dutch "Netwerklocatie" app (in english i guess "Networklocation"). After that no more problems.....could be some corrupted data in this application...
Hopefully this works for all of you!

Trying this fix now... (cleaning the networklocation data).

Nope..did not help at all. Still the same old camera failure. This sucks.

my camera fails too but this is not related to wifi...
usually an app using camera causes this..!!!
i hav camscanner and taking one or two pics from camscanner fails the camera...
i usually wait for sometime and then camera works as normal....
hope the problem doesn't gets worse for me.!!!!!

Damn,problem keeps reocurring:-( cleaning networklocation application data only helps for a small amount of time...
Only option now is disabeling networklocation service or using different camera application,does anybody recommend a good basic camera app?(stocklike and fast startup)
Sent from my GT-I5800 using XDA App

Try Sleek camera or lg camera just like the stock one..
Sent from my GT-I5800 using XDA App

Beasy30 said:
I had this problem...I think is JPF FW that can't allow you to take pictures...
When I used JPF...the first time i tried to take a photo,Camera didn't work and crashed...Second time it was ok
Try to flash JPM or an other FW
Click to expand...
Click to collapse
I have JPM and the problem is still there...

Beasy30 said:
Mmmmmm it's inusual...With JPM (and Kyrillo's ROM and Indroid ROM) I haven't had this problem
Try to make a wipe
Click to expand...
Click to collapse
Im running the stock JPM I got via KIES. I've done several wipes/hard resets lately cuz Im currenly having problems with installing a theme. Or at the moment, installing the Contacts.apk correctly... Yet the camera fails. I just tried.
Maybe it is the ROM, I don't know. Am not yet brave enough to flash... Want to fix this theme issue first.

I'm on JPM too, flashed twice thru Odin and wiped everything. It has something to do with APN/Networklocation but I don't know how to fix it permanently
@devilgod18: thanks for the suggestion, now using Sleek Camera!

Download SGSTools and install Hacked Camera.apk.
After I install this, my camera working good.
Sent from my Kyrillos v3.3 Galaxy 3

Blame Geo-Tagging
The reason why our phone can't (normally) take phtos is because of geo-tagging.
Note that when you use the camera.apk, there's a live notification at the top, a sattelite getting sinal. The camera is trying to associate your photo (it happens with any app that uses camera) with the place where you took it.
When I flashed the Apollo 1.0 rom (deodexed custom rom), this problem was solved. The camera.apk don't even show this notification, and I was able to take as many photos as I wanted to with no crashes. I tryed to use his apk in others roms... but no success. I don't know if are some dependencies, libraries... But I know that it worked!
What I do is to turn off networks (fligth mode), and take photos. Works perfect!

[FIX][GUIDE] S3 can't connect to WIFI

I've noticed lately that there are some unlucky victims of this weird tragedy, the infamous Authenication Error. I have experienced this and it is downright annoying :silly:
I have searched high and low on how to get this sorted out and found some methods and tricks to do the job.
you may have tried:
-restart the router
-entered router details manually on s3
-flashed another custom rom
-flashed another modem, kernel
-flashed a stock firmware
-reset the router
-restore factory settings
-wipe cache/fix permissions
i suggest you try the methods out to see which does the job for you. i followed some steps from this Q&A thread
ONE FIX FOR ONE DUDE MIGHT NOT BE A FIX FOR ANOTHER DUDE
Click to expand...
Click to collapse
METHOD A: WIFI POWERSAVING MODE OFF
1. Go to dialer
2. dial *#0011#
3. press menu button
4. select wifi
5. turn off wifi powersaving mode
METHOD B: FACTORY RESET
METHOD C: FLASH STOCK ROM/FIRMWARE
go to sammobile.com, look for a susceptible ROM there and flash via odin.. don't forget to wipe everything :fingers-crossed:
METHOD D: KILL wpa_supplicant thanks d4fseeker!
1. Connect your phone to the computer and open adb shell
2. Kill any process named wpa_supplicant and type:
Code:
wpa_supplicant -dd -i wlan0 -f /sdcard/wifi.log -c /etc/wifi/wpa_supplicant.conf
3.Then attach the generated logfile after having tried connecting to a wifi network.
**Alternatively you can run "wpa_cli" and show it's output.
METHOD E: SETUP STATIC IP
1. Go to Settings
2. Go to Wi-Fi
3. Choose Wi-Fi router
4. press Show advance options
5. change DHCP to static
6. input your ip the same thats appearing on your router
**TEMPORARY FIX only, you have to input the static ip everytime you connect
METHOD F: ADD A RESERVE IP ADDRESS
go to router and add a reserve IP address same one on your phone
METHOD G: EXTREME WIPE thanks slking1989!
1. back up via android. Copy backup to pc if u try this and it doesn't work u cant go back to before. Also backup and apps or pics music etc to pc
2. Download latest stock Rom with root
3. full Wipe, wipe cache partition, wipe dalvik cache. Flash latest wanam stock Rom. And repeat the wiping in recovery again. Full, cache and dalvik. Fix permissions.
4. Now reboot. And test if u still have the problem. As I did still. If not... yay you!
5. Do a hard reset. Yes a factory reset. NOT a full wipe via recovery. A reset via settings/backup and wipe/factory personal data reset. WARNING by doing this you will lose all app settings. All android backups and all data on internal storage. I believe this will also leave your ext sd contents unusable so ALWAYS backup to pc!
6. Repeat steps 3 and 4 again. This made my WiFi range and connectivity problems
Disappear! Although I still had authentication errors
7.Then repeat step 5 and see your outcome. It's seems for me atleast, that a double wipe was necessary.
**SIGNIFICANT OTHERS:
WiFi authentication error & ATT Uverse router
S2 YouTube Video How to fix Authentication Error, maybe this'll help
A discussion in androidforums.com about Authentication Error
step by step directions for a DIR-655 to setup WPS
How to fix network authentication error for your android phone YouTube Vid
you may also help lpallard, a member from androidforums.com in sending a bug report to Google: Issue #36993 - android - wifi no longer working in ics 4.0.4 - Android - An Open Handset Alliance Project - Google Project Hosting
Click to expand...
Click to collapse
FEEL FREE TO POST MORE SUGGESTIONS TO FIX THIS AND I'LL ADD IT IN THE OP
Click to expand...
Click to collapse

I've tried everything as per above and on the other thread and I'm still having the same issue. The other problem is it does at times randomly connect, at random speeds. Sometimes I'll get 1mbps. Really annoying. A few times I've had a steady connection, this has nothing to do with the password. I'm having the same issue even connecting to open networks with no authentication.
Could it be a hardware issue? I think the issue started with me when the phone severely overheated overnight.

au_stevo said:
I've tried everything as per above and on the other thread and I'm still having the same issue. The other problem is it does at times randomly connect, at random speeds. Sometimes I'll get 1mbps. Really annoying. A few times I've had a steady connection, this has nothing to do with the password. I'm having the same issue even connecting to open networks with no authentication.
Could it be a hardware issue? I think the issue started with me when the phone severely overheated overnight.
Click to expand...
Click to collapse
It is not a hardware issue. It is merely a software problem, no need to panic. I am still experiencing the problem when i connect to my old wifi router. I believe i have read it online that ever since the JB updates, the S3 wont connect to any insecure wifi routers for safety purposes..
Sent from my GT-I9300 using xda premium

saywhatt said:
It is not a hardware issue. It is merely a software problem, no need to panic. I am still experiencing the problem when i connect to my old wifi router. I believe i have read it online that ever since the JB updates, the S3 wont connect to any insecure wifi routers for safety purposes..
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I've given up hope. After trying AOSP and Standard roms, full wipes multiple times and flashing via odin nothing has helped. Mobile hot spot does not work either, this leads me to believe it's a hardware issue.
It wouldn't make sense that they'd deny access to open routers since public hotspot networks are open but require authentication via http.

Board replaced for wifi error
I too had the wifi problem that it would simply not connect to my network . My phone was in warranty . I had tried the above steps . Except *#0011# none worked for me , and that too after reboot I had to press *#0011# again . Not to mention the wifi power saving off would eat my battery like mad . I went to the samsung service centre (Mumbai/India) . They checked my phone , said the board needed to be replaced and kept it for two days . Voila ! two days later board replaced and that to the non SDS one . I checked it on playstore . Sadly they did not give me the 32gb Board . But its ok . Im happy .

can anyone please help me i am on firmware 4.1.2 but when i turn the wifi on it says turning on and it is stuck there forever??

Try Triangle away
Another method that works to me was trying the trinagle away app, try it if you intent everything else before

The problem disappeared when my router was modified to B mode only.
Try confirming it by changing your router to G-Only mode (no connection)
and then B-Only mode (connects each time)
Using stock unrooted new gt-i9300 Android 4.1.2 I9300XXEMG4

Samsung Galaxy S3 ( GT-I9300 ) Philippines 4.1.2 * Rooted *
Is this topic still active? You see I have the same problem too. I've done the method/s mentioned above and nothing happens. Wifi still not working if it's away from the router for like 1 meter. But it does work when I put my phone on the top of the router

Help
wayneshotss said:
Is this topic still active? You see I have the same problem too. I've done the method/s mentioned above and nothing happens. Wifi still not working if it's away from the router for like 1 meter. But it does work when I put my phone on the top of the router
Click to expand...
Click to collapse
S3 details :
i9300
I have same problem , wifi range 2 or 3 meters... someone was able resolve that problem ?? :crying:
I have already made:
Wipes / factory reset
Change modem
Reinstall Firmware
Change Firmware
Change Rom
Change kernel
Static IP config ---> s3 wifi config
code *#0011# power save disable
reset router
dhcp static config ---> in router config
how I can resolve this proble ?? if i am near to my router i have contection ... what is the problem? could be issue hardware???
the passsword is correct, my s3 connects a few meters!!!!

I cant connect to the WiFi network... In poor signals..
But i can connect normally when the signal is rich...
I can't find solutions...
When i try to connect poor wifi signals (might be signal is average)
The router shows """connecting""" and """saved"""
I had changed my modem.....
Changed my rom
Nothing cure my wifi issue... Pls help me....

THANKS IT WORKS! LIKE CHARM! METHOD A: works for me =)

Exactly the same problem as mine. How can I resolve this?
---------- Post added at 09:23 AM ---------- Previous post was at 09:18 AM ----------
Wasabyto:) said:
S3 details :
i9300
I have same problem , wifi range 2 or 3 meters... someone was able resolve that problem ?? :crying:
I have already made:
Wipes / factory reset
Change modem
Reinstall Firmware
Change Firmware
Change Rom
Change kernel
Static IP config ---> s3 wifi config
code *#0011# power save disable
reset router
dhcp static config ---> in router config
how I can resolve this proble ?? if i am near to my router i have contection ... what is the problem? could be issue hardware???
the passsword is correct, my s3 connects a few meters!!!!
Click to expand...
Click to collapse
Exactly the same problem. What to do?

saywhatt said:
I've noticed lately that there are some unlucky victims of this weird tragedy, the infamous Authenication Error. I have experienced this and it is downright annoying :silly:
I have searched high and low on how to get this sorted out and found some methods and tricks to do the job.
you may have tried:
-restart the router
-entered router details manually on s3
-flashed another custom rom
-flashed another modem, kernel
-flashed a stock firmware
-reset the router
-restore factory settings
-wipe cache/fix permissions
i suggest you try the methods out to see which does the job for you. i followed some steps from this Q&A thread
METHOD A: WIFI POWERSAVING MODE OFF
1. Go to dialer
2. dial *#0011#
3. press menu button
4. select wifi
5. turn off wifi powersaving mode
METHOD B: FACTORY RESET
METHOD C: FLASH STOCK ROM/FIRMWARE
go to sammobile.com, look for a susceptible ROM there and flash via odin.. don't forget to wipe everything :fingers-crossed:
METHOD D: KILL wpa_supplicant thanks d4fseeker!
1. Connect your phone to the computer and open adb shell
2. Kill any process named wpa_supplicant and type:
Code:
wpa_supplicant -dd -i wlan0 -f /sdcard/wifi.log -c /etc/wifi/wpa_supplicant.conf
3.Then attach the generated logfile after having tried connecting to a wifi network.
**Alternatively you can run "wpa_cli" and show it's output.
METHOD E: SETUP STATIC IP
1. Go to Settings
2. Go to Wi-Fi
3. Choose Wi-Fi router
4. press Show advance options
5. change DHCP to static
6. input your ip the same thats appearing on your router
**TEMPORARY FIX only, you have to input the static ip everytime you connect
METHOD F: ADD A RESERVE IP ADDRESS
go to router and add a reserve IP address same one on your phone
METHOD G: EXTREME WIPE thanks slking1989!
1. back up via android. Copy backup to pc if u try this and it doesn't work u cant go back to before. Also backup and apps or pics music etc to pc
2. Download latest stock Rom with root
3. full Wipe, wipe cache partition, wipe dalvik cache. Flash latest wanam stock Rom. And repeat the wiping in recovery again. Full, cache and dalvik. Fix permissions.
4. Now reboot. And test if u still have the problem. As I did still. If not... yay you!
5. Do a hard reset. Yes a factory reset. NOT a full wipe via recovery. A reset via settings/backup and wipe/factory personal data reset. WARNING by doing this you will lose all app settings. All android backups and all data on internal storage. I believe this will also leave your ext sd contents unusable so ALWAYS backup to pc!
6. Repeat steps 3 and 4 again. This made my WiFi range and connectivity problems
Disappear! Although I still had authentication errors
7.Then repeat step 5 and see your outcome. It's seems for me atleast, that a double wipe was necessary.
**SIGNIFICANT OTHERS:
WiFi authentication error & ATT Uverse router
S2 YouTube Video How to fix Authentication Error, maybe this'll help
A discussion in androidforums.com about Authentication Error
step by step directions for a DIR-655 to setup WPS
How to fix network authentication error for your android phone YouTube Vid
Click to expand...
Click to collapse
Hello there. I tried all the guide above. And also from most of the other solution from other website. Believe me. Nonoe of it working. So here i found a solution. I go to repair shop. And say want to repair my wifi. They change wifi ic, next day i try the phone, and now its workinģ! They say wifi ic can èxpire

I have i9305 and I same problem after changing ROM still the same an I don't have any way to get service menu. WiFi only connect with full strength signal. Help

i9305 - WIFI ISSUE
It's a wifi antenna issue, replace or check connections ...
saywhatt said:
I've noticed lately that there are some unlucky victims of this weird tragedy, the infamous Authenication Error. I have experienced this and it is downright annoying :silly:
I have searched high and low on how to get this sorted out and found some methods and tricks to do the job.
you may have tried:
-restart the router
-entered router details manually on s3
-flashed another custom rom
-flashed another modem, kernel
-flashed a stock firmware
-reset the router
-restore factory settings
-wipe cache/fix permissions
i suggest you try the methods out to see which does the job for you. i followed some steps from this Q&A thread
METHOD A: WIFI POWERSAVING MODE OFF
1. Go to dialer
2. dial *#0011#
3. press menu button
4. select wifi
5. turn off wifi powersaving mode
METHOD B: FACTORY RESET
METHOD C: FLASH STOCK ROM/FIRMWARE
go to sammobile.com, look for a susceptible ROM there and flash via odin.. don't forget to wipe everything :fingers-crossed:
METHOD D: KILL wpa_supplicant thanks d4fseeker!
1. Connect your phone to the computer and open adb shell
2. Kill any process named wpa_supplicant and type:
Code:
wpa_supplicant -dd -i wlan0 -f /sdcard/wifi.log -c /etc/wifi/wpa_supplicant.conf
3.Then attach the generated logfile after having tried connecting to a wifi network.
**Alternatively you can run "wpa_cli" and show it's output.
METHOD E: SETUP STATIC IP
1. Go to Settings
2. Go to Wi-Fi
3. Choose Wi-Fi router
4. press Show advance options
5. change DHCP to static
6. input your ip the same thats appearing on your router
**TEMPORARY FIX only, you have to input the static ip everytime you connect
METHOD F: ADD A RESERVE IP ADDRESS
go to router and add a reserve IP address same one on your phone
METHOD G: EXTREME WIPE thanks slking1989!
1. back up via android. Copy backup to pc if u try this and it doesn't work u cant go back to before. Also backup and apps or pics music etc to pc
2. Download latest stock Rom with root
3. full Wipe, wipe cache partition, wipe dalvik cache. Flash latest wanam stock Rom. And repeat the wiping in recovery again. Full, cache and dalvik. Fix permissions.
4. Now reboot. And test if u still have the problem. As I did still. If not... yay you!
5. Do a hard reset. Yes a factory reset. NOT a full wipe via recovery. A reset via settings/backup and wipe/factory personal data reset. WARNING by doing this you will lose all app settings. All android backups and all data on internal storage. I believe this will also leave your ext sd contents unusable so ALWAYS backup to pc!
6. Repeat steps 3 and 4 again. This made my WiFi range and connectivity problems
Disappear! Although I still had authentication errors
7.Then repeat step 5 and see your outcome. It's seems for me atleast, that a double wipe was necessary.
**SIGNIFICANT OTHERS:
WiFi authentication error & ATT Uverse router
S2 YouTube Video How to fix Authentication Error, maybe this'll help
A discussion in androidforums.com about Authentication Error
step by step directions for a DIR-655 to setup WPS
How to fix network authentication error for your android phone YouTube Vid
Click to expand...
Click to collapse

Wifi Turning on Stuck

UPDATE - Problem sorted via philos64 thread at the top...
Should've tried that 1st, but posted here hoping someone would confirm that was the route to take, as it wasn't actually bricked... Never mind, all done..
Why??? Was out earlier so I turned my wi-fi off and my mobile on and everything was working fine..
When I got home, I turned the mobile off and tried to turn wifi back on, but it is hanging on 'Turning wifi On.'
Tried rebooted the tablet a few times and rebooting the router, (BT HomeHub 3), but still the same problem.
This N7 is rooted and running 4.2.2.
When I look at the Advanced Wifi the MAC and IP address are unavailable.
When I go into Wifi Analyzer it says the wifi needs to be turned on and tries but gets same hang and retries...
On the left of the analyzer it shows my Wifi ID with a mac address underneath with a yellow triangle and 'No Signal!' in red.
The wifi from the router is working as my phone is connected via wifi.
Any ideas please people ???
:crying:

going for the post with the most views and zero replies is not on my bucket list... So I'm going to reply to myself..
An Update....
The problem is still there, so I went into bootloader - recovery mode....Then I went into Android system Recovery.
I selected cache then wipe dta/factory reset.. Reboot then starts tablet as new with the unlocked symbol, then goes through the initial setup. Select language, then it does Select wifi and displays 'Turning on wifi'.. Hung...
Would flashing it via Nexus root toolkit sort out then problem... If so, any clues what flash and how...
If it wouldn't fix it... Is the tablet now bricked??
Please answer someone if you know..
Cheers

There have been several posts about wi-fi problems if the outer shell of the N7 is separated and not fully locked in. A loose or separated shell can cause a disconnect in the wi-fi antenna. Check for any separation and maybe squeeze the front and back together all the way around the outer edge.

I did read them and a lot of other threads but they were mainly to do with wi-fi looping and not connecting.... I couldn't find any other post regarding just 'turning it on'.... And seeing as it's sorted with just a flash of the stock rom, I can safely assume this problem had nothing to do with hardware...
Hence why I was surprised I was the only 1 with this 'type' of prob.... (but I didn't read every post so I may have missed one).

Same problem too
filking said:
I did read them and a lot of other threads but they were mainly to do with wi-fi looping and not connecting.... I couldn't find any other post regarding just 'turning it on'.... And seeing as it's sorted with just a flash of the stock rom, I can safely assume this problem had nothing to do with hardware...
Hence why I was surprised I was the only 1 with this 'type' of prob.... (but I didn't read every post so I may have missed one).
Click to expand...
Click to collapse
im experiencing the same thing. im using Samsung galaxy S4 i9505 LTE and on android 4.3/ rooted Baseband i9505XXUEMJ5. it happened when i was trying to erase all the bloatware on my phone using Trulyclean by schoolsux. after i flashed the script i started having this problem.so far ive tried to do a factory reset by using custom recovery, tried to download the modem fix and flashed it through odin and do the advanced settings on wifi and uncheck the auto network switch. The problem that i have is yes it say "connecting" for 2-3 minutes then it gives you a list of possible wifi connections and then you connect. another 2-3 minutes then it wont connect. repeat the steps and now i can connect, then if you turn off the wifi you will have to go through the whole process again. it doesnt save any wifi connections you have connected before. there are 2 other ways i havnt tried yet and that is to flash a different kernel. a custom kernel and reflashing my phone again with the android 4.3 then root:laugh: for the nth time already:fingers-crossed:

hammerthumbs said:
im experiencing the same thing. im using Samsung galaxy S4 i9505 LTE and on android 4.3/ rooted Baseband i9505XXUEMJ5. it happened when i was trying to erase all the bloatware on my phone using Trulyclean by schoolsux. after i flashed the script i started having this problem.so far ive tried to do a factory reset by using custom recovery, tried to download the modem fix and flashed it through odin and do the advanced settings on wifi and uncheck the auto network switch. The problem that i have is yes it say "connecting" for 2-3 minutes then it gives you a list of possible wifi connections and then you connect. another 2-3 minutes then it wont connect. repeat the steps and now i can connect, then if you turn off the wifi you will have to go through the whole process again. it doesnt save any wifi connections you have connected before. there are 2 other ways i havnt tried yet and that is to flash a different kernel. a custom kernel and reflashing my phone again with the android 4.3 then root:laugh: for the nth time already:fingers-crossed:
Click to expand...
Click to collapse
i have same issue with htc one x, my wifi doesn't wan't to turn on. it stuck on "turning on...", i tried to flash different roms, etc, now i think about flashing kernel, did you do that? did it help?

Same problem on N4
Have had the exact same problem not once but twice. One day it works perfectly fine. Next day, it just stops at turning on process.
On my N4 the 4.2 was working fine. Along comes the 4.3 OTA update and the wifi stops working. Does not startup or show the mac addr either.
Did factory reset, wipe cache and even reflash binary from google stock images. No relief.
One day, the wife using gmaps started the gps location service and pop the wifi started,
Now after the 4.4 OTA all seemed to work well till yesterday and pop the wifi breaks down. the earlier trick of gmaps does not seem to work. I think one of the google apps update is breaking this.
After rebooting also, the device seems to remember the wifi state and tries to read the previous history and restore for the startup. And that is killing.
Any idea how to debug this or to wipe the wifi logs or to manually start the wifi/bluetooth radio.. ya athe bluetooth is also stuck.
Thanks guys in advance

Where is the fix?
filking said:
UPDATE - Problem sorted via philos64 thread at the top...
Should've tried that 1st, but posted here hoping someone would confirm that was the route to take, as it wasn't actually bricked... Never mind, all done..
Why??? Was out earlier so I turned my wi-fi off and my mobile on and everything was working fine..
When I got home, I turned the mobile off and tried to turn wifi back on, but it is hanging on 'Turning wifi On.'
Tried rebooted the tablet a few times and rebooting the router, (BT HomeHub 3), but still the same problem.
This N7 is rooted and running 4.2.2.
When I look at the Advanced Wifi the MAC and IP address are unavailable.
When I go into Wifi Analyzer it says the wifi needs to be turned on and tries but gets same hang and retries...
On the left of the analyzer it shows my Wifi ID with a mac address underneath with a yellow triangle and 'No Signal!' in red.
The wifi from the router is working as my phone is connected via wifi.
Any ideas please people ???
:crying:
Click to expand...
Click to collapse
Hi Can you please send a link for the solution? i am still stuck with "wifi turning on" screen and cant seem to bypass it. No matter what Stock image i flash through Wug Toolkit.

i have got the same wifi errorrigictsi vanished
initially i had loaded my explorer with fly rom and everything waas working except the internal memory. i'm not even able to download at least an app and then i tried bulletsense rom for increasing the internal memory of my explorer. it's successful, and the memory increased. From there onwards, the problem started. the wifi first said error... but after reboot, it's all the time saying "turning on"..
by typing "ifconfing twlan0" it said no devices found... so i thought it might be some driver error. coueld any one port some other drivers to the below rom so that i can have both internal memory and wifi...
link to bulletsense rom ///d-h.st/xFr//// ( add https before /xxxx/)
here is a screenshot of it...///bit.ly/MMSeam///
any one please help me on this and give me a chance to raise your thanks meter...
sorry that i'm newbie and not allowed to post links.

Hey guys.. I faced similar issue in my AMOI 820 based Indian local device Micromax (rooted + custom kernal)
I fixed this stuck wifi problem by uninstalling Google apps in system by removing them using Titanium back up + and again installing them from playstore if needed.. Hangouts(in my case) if it's a system app after getting updated is the culprit .. Try removing it and reboot and test it yourself..

guess it working now!!
I was going crazy about this stuck wifi issue!!
I tried everything!! I found on the advance panel on the wifi
That the MAC address and the IP address is unavailble.
After many tries i think i fixed it!! Using:
Busybox and MacMan
MacMan changed my MAC address and now the wifi is no longer stuck!!!! Hope it will help you too. Peace

yurashi# said:
I was going crazy about this stuck wifi issue!!
I tried everything!! I found on the advance panel on the wifi
That the MAC address and the IP address is unavailble.
After many tries i think i fixed it!! Using:
Busybox and MacMan
MacMan changed my MAC address and now the wifi is no longer stuck!!!! Hope it will help you too. Peace
Click to expand...
Click to collapse
I have same problem on my nexus 5,
But macman is not working.
Any other solutions

wifi turning on problem
i have a xperia sola mobile ..
wifi is does not work ..please help
when touch the wifi option then it does not turning on ..

wifi on cm10 and cm 10.1 not working at all

Hi, maybe someone has a clue:
I seem to be the only one who can't use cm10 because wifi is just not working. On cm10 it's dropping out all the time as soon as data gets transfrerred (i.e. app download) and on cm10.1 its not even dropping. there is no data throughput whatsoever.
If you need more info, just tell me which one and I'll post it. I'm desperate.
Any ideas?

Assuming you have made a clean install, with system and data wiped as well, you should check your router configuration, try changing channel and/or security parameters
Sent from my MB526 using Tapatalk 2

thanks for the suggestion. I don't have access to all the routers settings but I tried to use one even without security and the drop outs still appeared. Working well on m7.
I just realise: At the beginning of a fresh build it sometimes happens that wifi works for a couple of MB and suddenly starts dropping.

Is the Wi-Fi network used by many persons at a time? More than a couple of devices connected may cause problems because the new Wi-Fi drivers starts jamming devices, and sometimes as a result the Wi-Fi network is unable to deliver data.
Sent from my MB526 using Tapatalk 2

I wouldn't say so. Not to many and it didn't work with the old wifi driver on cm10 either. The wifi keeps working for other parties in the network - so it is not jammed.
I might try again with a new build but I'm pretty hopeless...
Here is a long post about what I tried so far:
http://forum.xda-developers.com/showpost.php?p=38869441&postcount=915
measel said:
Hi I'm sorry to bother again.
I tried to figure out whats wrong with the wifi bug I'm having: constant drop outs while using any kind of wifi traffic.
Good news:
it worked well at home with my fritzbox router. (only tried 3-4 app downloads) > after a short while it stopped working
Bad news:
in my studio we got a different router and there I got the drop outs.
What I tried so far without luck (always a reboot in between):
disable Draft-N in wpa_supplicant
compared wpa_supplicant but it's the same as in cm7
delete rgnt from system/bin
change build.prop to use all 14 channels > ro.wifi.channels=14
tried changing PowerSavePowerLevel = 0 to 1
copied tiwlan.ini from cm7 backup because a few settings are different
tried 12-12-05 Quarx build
tried 12-10-18 build (but got a bootloop and stopped trying)
tried newest 13-03-07 build
ADDED tried 13-04-09 build
tried newest build and did another factory reset AFTER installing the ROM.
searched the web and found that maybe it might have something to do with wpa2, but the router at home uses wpa2/wpa (which means it's wpa2 as well or not?) and NO I cannot change the routers settings and I don't think it is a solution because i can use but not access like a dozen routers.
checked dmesg: in the TIWLAN section after the wifi connection it says: "iface_stat: stat_update() tiwlan0 not found
is it in any way possible that some settings change because I plugged usb "charge only" in while trying to download from Playstore? because it seems that dmesg spits somthing out regarding usb... (I'm can't really read/understand the output though)
oh and btw. first connection was fine in my last try: I could update Gmail, then I connected my usb and drop outs began. but I don't think it's related.
ADDED change to static IP
ADDED change regional code in wifi settings (w/o knowing what that actually does)
ADDED tried factory reset from stock, flash sbf and start from scratch.
Things I didn't try (and don't know if it would make any sense):
replace tiwlan_drv.ko
change vsel
[...]
Click to expand...
Click to collapse

It may be something elementary, but I presume Wi-Fi optimization is configured properly right?(IT MUST BE DISABLED)
I have had this issue but setting channel manually fixed it for me. This issue I had only on jb and with a specific router only. All others work properly on every channel.
Sent from my MB526 using Tapatalk 2

Damn I can't just change all the channels in all the wifi networks I'm allowed to use... but I will try that with my own one.

I did not try to change channels, yet but I tried once more to start from scratch: wipe from stock / flash sbf / install cm10 and so on..
Reason: Someone hinted the stock wipe could help. But here is the problem:
Everytime I try to wipe from stock (before or after flashing sbf) I get the old "E:can't mount cache:recovery/..." ERROR. Something seems to be wrong and I wonder if that could prevent my wifi from working (maybe data is still unwiped...)
Any more ideas?

Stock recovery can't handle ext4, hence the read errors.
Stock recovery wipe will not help if custom recovery data wipe does not help. You can also try manually deleting the Wi-Fi folder in the data partition.
You'll have to try changing channels eventually, I think.
Sent from my MB526 using Tapatalk 2

thats a misunderstanding:
I know that stock recovery can't handle ext4. My working system is cm7 so I stockwiped from cm7 and still couldn't get rid of the errors. I even checked the filesystem with e2fsck but everything seems to be ok. And I can install everything so... I don't know.

If your current rom is cm7 then you shouldn't get the error messages in stock recovery. I assume you've flashed a sbf and still gotten this error. You can try enabling the blank flash option from rsdlite.
You can verify whether data is wiped or not by wiping in custom recovery, and then cross checking with aroma file manager(flashable) to ensure data is wiped. If not then you have some kind of hardware eMMC problem which somehow triggers the Wi-Fi problem probably because of leftover Wi-Fi files and modules.
Also, couple of people have had luck flashing a newer sbf like dfp 231(with higher bl version), which seems to work in some cases for similar problems. Beware of the no downgrade issue in these recent sbfs.
And what misunderstanding are you talking about?
Sent from my MB526 using Tapatalk 2

thekguy said:
If your current rom is cm7 then you shouldn't get the error messages in stock recovery. I assume you've flashed a sbf and still gotten this error. You can try enabling the blank flash option from rsdlite.
Click to expand...
Click to collapse
That does sound pretty scary.
You can verify whether data is wiped or not by wiping in custom recovery, and then cross checking with aroma file manager(flashable) to ensure data is wiped. If not then you have some kind of hardware eMMC problem which somehow triggers the Wi-Fi problem probably because of leftover Wi-Fi files and modules.
Click to expand...
Click to collapse
I can't waste another day on hunting the /cache problem right now because of work, but as soon as I have more time I'll try a little more.
Here is some news from me: I had the chance to try it on another wifi router last night and behold: It worked nearly flawless.. a few hickups I think, but it worked. That means WIFI is not broken, but there must be some software-related problem/ or some network weirdness.
Also, couple of people have had luck flashing a newer sbf like dfp 231(with higher bl version), which seems to work in some cases for similar problems. Beware of the no downgrade issue in these recent sbfs.
Click to expand...
Click to collapse
This I will not do!
thekguy said:
And what misunderstanding are you talking about?
Click to expand...
Click to collapse
Just that stock over ext4 thing. Nevermind.
Thank you for helping. I wonder if there is a way to find the problem.

Did you check the channel that particular Wi-Fi router operated at? Same as or different than the problematic routers ? Because if so then we have narrowed the problem down
Sorry for the scary part
Sent from my MB526 using Tapatalk 2

[Q] Problem with WIFI, freeze and reboot after time of sleep (Also in secure mode)

Hi, I never root my phone or flash a custom ROM.
The problems was started when I flashed a new ROM from sammobile of another country, my phone comes with 4.2 and I flashed a 4.3.
I flashed newer ROM from only Vodafone-Spain (only those really are my official supplier), and then I update ever with Samsung KIES, (no Knox counter)
So, with Andorid 4.3 I had more problems than now with 4.4, now the only problem is with WIFI
I can use normally, with screen ON, the problem is when sleep for a long time (more than 1 hour) when I touch a button I see the unlock screen, but does not seem to work the touch screen, and screen go off after a seconds, if I touch other button the screen don't go on. And then, after aprox 30s it reboot itself, and show a window telling that the Process System is not responding, do you want to close?, and two buttons, close or wait.
I tried to start my phone in Secure Mode and I have the same problem, so it is not an app, it is the ROM.
I do at least 2 Factory Reset, but the problem is still there.
I think it is a software problem and not a hardware problem, because the problem start when I update to Android 4.3
I tried the trick WIFI Power save Mode OFF (on dialer, *#0011# -> WIFI -> Power save mode OFF) and never reboot automatically, so the problem I think it is with this power save mode. But if I turn off, when WIFI is ON, the battery drain fast.
In the samsung shop they tell me that first will format my phone to see if the problem solve and try for a time, if not solve, then I have to send by mail... and I will not send it because I know the time it will take to repair it is about 1-2 months and I need the phone for my work.
So is there another solution or something to try?

Napalm Candy said:
So is there another solution or something to try?
Click to expand...
Click to collapse
Try reflashing the Firmware once again mate and Here you can follow the tutorial from here

Repulsa said:
Try reflashing the Firmware once again mate and Here you can follow the tutorial from here
Click to expand...
Click to collapse
Since the first ROM (4.2) I flashed 3 or 4 ROMs from SamMobile, so I am not very optimistic. But I don't lost nothing, I will try it

I flash again the ROM, and after 2 days testing, the problem is still there.
Any other thing to try before send to samsung?

Please, give me another idea to try. I really have a problem with WIFI
This is how Wifi (some times) drain my battery when are not connected to a network. But the problem is worst when is connected, because it freeze and reboot.

Hello! You could fix the problem? I took suffering the same problem as your months, and I have not been solved, I'm for kicking the **** mobile! As may give so many problems with the wifi?
regards

manguila said:
Hello! You could fix the problem? I took suffering the same problem as your months, and I have not been solved, I'm for kicking the **** mobile! As may give so many problems with the wifi?
regards
Click to expand...
Click to collapse
Yes I solve. So.. I don't solve it, it solve it self. One day I saw that I don't had wifi connection, then I saw that I don't any WIFI names stored, all was erased automatically, I don't know how.
But the result it, I don't have anymore a freeze or a reboot because wifi. ALL, absolute ALL run fine now. I had a lot of WIFI names stored, about 30-50, maybe this was the problem, a conflict with some of these names, but I'm not sure
No one update, reflash, factory reset, or start in safe mode was solve any problem, the problem solve it self... very strange.
If you try a factory reset, then don't restore all your mobile config. Try to install all apps manually, one by one. I ever restored my backuped config, and I think this was the problem.
Hope you can solve it

Napalm Candy said:
Yes I solve. So.. I don't solve it, it solve it self. One day I saw that I don't had wifi connection, then I saw that I don't any WIFI names stored, all was erased automatically, I don't know how.
But the result it, I don't have anymore a freeze or a reboot because wifi. ALL, absolute ALL run fine now. I had a lot of WIFI names stored, about 30-50, maybe this was the problem, a conflict with some of these names, but I'm not sure
No one update, reflash, factory reset, or start in safe mode was solve any problem, the problem solve it self... very strange.
If you try a factory reset, then don't restore all your mobile config. Try to install all apps manually, one by one. I ever restored my backuped config, and I think this was the problem.
Hope you can solve it
Click to expand...
Click to collapse
Thank you very much for answering so quickly.
Happens to me exactly what you do, but seems to have no solution.
I have tried more than 8 roms, stock or mods, and always fails.
At first I thought it would issue the modem or kernel, but after many tests, I do not ****ing know what is causing the problem.
I'm running out of solutions, anyway thanks for telling your case...
I'm glad that in the end one way or another, you have it fixed.
:good:

manguila said:
Thank you very much for answering so quickly.
Happens to me exactly what you do, but seems to have no solution.
I have tried more than 8 roms, stock or mods, and always fails.
At first I thought it would issue the modem or kernel, but after many tests, I do not ****ing know what is causing the problem.
I'm running out of solutions, anyway thanks for telling your case...
I'm glad that in the end one way or another, you have it fixed.
:good:
Click to expand...
Click to collapse
What happens when you fully wipe, flash a 4.4.2 rom, don't restore anything, not even your google account and don't install any apps.

Lennyz1988 said:
What happens when you fully wipe, flash a 4.4.2 rom, don't restore anything, not even your google account and don't install any apps.
Click to expand...
Click to collapse
Thanks for your interest! The truth is that it is very strange ...
If I remember correctly, already try what you mention me, but I kept going ... It's like at some point something had happened which change roms not seem to solve..
I'm considering installing a rom with 4 files and pit file, but do not know if this will help in something
Let's see if I can come up with the bug because it is becoming a pain in the ass
:good:

I would try what say Lenny1988. So the only change before solution and after solution, was a big crash on WIFi drivers/app/modem (don't sure) it self, and was deleted all my stored wifi access points that I had. It was a problem related to Wifi power save, if I disabled it then I had no reboots/freezes.
So, I would try a factory wipe and DON'T restore anything, and try for a couple days. If work, then you know a way to solve it.
Tell us if it works.

Hello there! I will update with the latest news!
I tried the recommended advice, but no luck...Not seem to affect him leave without restoring.
The only thing that seems to work and keep it running, is to disable wifi power saving system
you know....
Code:
1. Go to your phone dialer
2. Dial *#0011#
3. When you see the "ServiceMode" screen, press the left menu button
4. Select "WiFi"
5. See that "Wifi Power Save Mode" button that is "ON" - well turn it "OFF"
But this way drain your battery much faster,so it does not seem a good solution to the problem.
Curiously, the same phone, some people suffer this problem and others do not....
It may be hardware? or software?
If I find something, I'll note here.
Regards