Database Info

WiFi/Bluetooth - ICS -Lets share version numbers that appear to be fine.....

In this thread i am only referring to the WiFi/Bluetooth clash that seems to affect some of us but not all of us.
ie; The problem appears to be with the WiFi, WiFi fails to disconnect when leaving the ssid area. Wont reconnect when returning to the area, the WiFi connection just cycles, hunting and hunting, never connecting..... until i turn the Bluetooth off, then it connects within seconds. Switching off the Bluetooth appears to eliminate a 2.4ghz clash between the wifi and Bluetooth, allowing the WiFi to operate freely.
Other phone manufacturers have had to deal with this, its not uncommon.
I've been evolved in a bit of discussion about wifi this week, And i have found I have the WiFi/Bluetooth clash on my twin-core. but not the quad-core.
so i thought we should distribute the version numbers that are trouble free, that seems to me to be a better place to start than with just random testing like i have had to do to get my result... .. so a bunch of test roms later, here are the rom versions i use, and have turned out to be trouble free.
Twincore - Now runs "CleanROM 3", based on build version 1.88.707.2, now runs problem free. I had previously tryed Asian roms 1.77.708.3 & 1.77.708.2, the Modaco IR1(1.29.401.11), all had the W/BT problem.... there were some others that didnt work either but i lost track.
I also tried the wifi fix provided by JSLenterprises but got no relief from that, not on any of the versions i tested.
(To be fair to JSLenterprises, i dont even know if his fix was for this issue, i just tryed it because i was testing anything WiFi for my solution!)
Quadcore - Still running factory 1.29.728.12, always ran problem free!
Anyone else got some build numbers that you know are trouble free? we might be able to narrow down weeks of research for others trying to resolve this bluetooth/wifi clash.... or else wait for the proposed offical update of course.
And anyone having familiar problems might want to flash these versions i suggest, just to make sure i didnt just get lucky.
lets solve this sh..!

You had bluetooth issues, and flashing cleanrom 3.0 fixed them?
what issued did you have? my bluetooth is terrible.

Was person calling me hearing their echo when im on bluetooth one of these problems?? Just bought bloototh for car and receiver hears their own voice, big echo they say

I had no issue with the bluetooth itself...
explanation in opening post........

Blaze Signal Keeps Going Out Problem(On Any ROM!)

So here's my issue, my Galaxy S Blaze has been switched from ROM to ROM constantly, I have seen ROMS with modified build.props, other added features, and a bunch of other tweaks, you name it! I don't know what all those tweaks mean, I have no idea if it could affect the way my phone receives the signal but it got me so frustrated that I kept switching roms until finally then I went back to stock and am no longer am switching to another ROM.
Here's a history of the ROM switching I've made in the past couple of months:
1st - MIUI
2nd- Cyanogenmod
3rd- Gummy ROM
4th- Liquidsmooth ROM
5th- Cyanogenmod
6th- Dirty Unicorns (problems with signal started occurring right about here, and onwards)
7th- Stock ROM (hmm... nope nothing fixed.)
8th- Validus (still no, I didn't like the constant force-closing of many apps)
9th- Gummy ROM (nope, what's worse is my screen kept freezing if I had atleast 2 apps open and I slid down the notification drawer)
10th- Cyanogenmod (well, maybe switching to cyanogenmod will fix it)
11th- Gummy ROM (*sigh* switching back? Nope, still didn't help my signal)
12th- Stock ROM (you would expect it to be fixed right about here, but nope)
So what's up what is the exact problem with my signal? Here's the thing: My signal works! That's a start atleast. However, if I turn on my Wi-Fi while I'm home, I can still call/text people, all of that works. But after maybe 2 hours or so, the signal bar is still there, it's telling me it has signal and it's connected, SOMETIMES it will be empty meaning I have no signal(when I really do). But in reality, I can't receive texts, nor calls, none of that. So how do I fix it? By restarting my phone sadly, that has been the only solution for me for these past 2 months. People have complained to me because I don't answer my phone anymore, well I'm sorry my phone can't receive those calls due to this messed up signal. There are 3 other T-Mobile phones in the house that have no problem! The problem here is with my Blaze phone.
So what if I turn the Wi-Fi off for the whole day and see if it's the main thing causing the issue? Well, I did this. Turns out that the signal stays on longer than when I'm on Wi-Fi but it still goes out. I have switched SIM Cards, I have tried switching my APN: from "epc.tmobile.com" to "fast.t-mobile.com" but the problem appears to happen more quickly on the "epc" one than the "fast" one. Please help me with this, this has been frustrating me a lot lately. I'm not sure if anyone has even had the same exact problem that I'm having, I've searched online but haven't seen a similar problem.
Some of you might say, wow that is a lot of ROMS you've switched to, I'm sure there were more that I missed but that's as of recent. I can install ROMS correctly, I know how to use CWM when installing a .zip and using Odin when it's a .tar(or other supported file extensions). I've factory reset, wiped the cache, the dalvik cache, all before installing a new rom. After installing each rom, I've also factory reset and wiped the cache to make sure no other problems could affect the way the rom would work. Hopefully I did the procedure right, thanks for anyone who's willing to help me!
Right now I am running:
Baseband Version:
T769UVLH5
Kernel Version:
3.0.8-perf-T769UVLH5-CL990184
[email protected] #1
SMP PREEMPT Fri Aug 17 15:12:14 KST 2012
Android Version:
4.0.4
Another Issue is that I can't even transfer files to and from my phone when connected to my computer! This is another big issue, here are some images:
http :// i.imgur.com/xx699ss.png
http :// i.imgur.com/1wRzJpX.png
Here's what happens when I turn Wi-Fi Calling on but maybe it's just a built-in function that I forgot it had and it's probably normal:
http :// i.imgur.com/cTSqRci.png
By the way, sorry for the links just copy and paste them in a browser to and remove the spaces between the http :// and i.imgur, thanks! Unfortunately, I can't post links until I reach 10 posts. If the links don't work for you, I've also provided attachments.
Many thanks!!!

That last picture does show the proper function of Wi-Fi calling however I don't know what to say about the rest of your problems.
Sent from my SAMSUNG-SGH-T769 using XDA Free mobile app

There are two things I would recommend trying...
1. Use Blackhole System Wipe
I know you've been following all the proper steps in CWM (and I would say to keep doing so), but I've added using Blackhole, in addition to the first steps, and I always get great system performance on my phone, and my parent's phones (I put them on ProvisionMod after stock was being stupid). It works well for pre installation for ANY ROM and helps prevent pesky issues. However, chances are, your issue is baseband related and this probably won't solve it... But still! You never know! It's worth a shot!
2. Reroot your phone
I know this will be annoying and pesky... but sometimes the process goes wrong from the beginning and starts giving issues later on... When I first rooted my mom's blaze, something went wrong, despite my following all the directions, and one of her partitions was completely disabled, no matter the ROM. I redid the process of rooting her phone (not from GB though... From the ICS stock) and fixed the issue instantly! I would try these two steps first and see if they do anything! Good luck!
Sent from The Doctor's Blaze

[Q&A] [ROM][4.4.4] OmniROM - Stingray/Stingray_CDMA - bigPart

Q&A for [ROM][4.4.4] OmniROM - Stingray/Stingray_CDMA - bigPart
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][4.4.4] OmniROM - Stingray/Stingray_CDMA - bigPart. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

no sound, no auto-rotate
I am fairly new to Rooting and updating my Xoom to the newest Kitkat system. I am having 2 issues as of right now. The sound has never worked no matter what the settings say, and initially the auto-rotate was functioning and suddenly it stopped.
I have checked all options/setting and see nothing that should explain either of these 2 issues. I also didnt add any new apps in the time from initial update to the auto-rotate not working so if anyone has any suggestions or ideas, it would be greatly appreciated.
Again I am fairly new to all this, so the simpler or more detailed the potential solution the more likely I will understand it.
Thanks.

No sound on Omni 4.4 cmda version
I love the rom, only problem is I have no sound on the cmda version. I read the comments and saw people suggest install the top rom version over the bottom and then reflashing gapps. Should have sound. When I do this tablet boots but keeps giving me error "Unfortunately, the process com.android.phone has stopped" I say ok but it keeps coming up and wont let me get any further. Any suggestions?

volume issue
Anyone know how to fix the no sound issue in omni rom 4.4.4 stingray cdma? I cant get any sound at all. Help would be appreciated.

Took a couple go's but now up and running 4.4.2!
Thank you!
First time I've moved from the standard stock implementation, never even rooted the device before, but a couple attempts and following your instructions I managed to install BigPart, Flash omni-4.4.2-201XXXXX-everest-HOMEMADE_XXXX.zip, gapps-xxxx.zip & UPDATE-SuperSU-v1.86.zip.
I was about to give up on the Xoom and buy something newer, Tab S or something, but this appears to have put new life back into the old Xoom!
Followed the instructions above, but could not get it to clear Dalvik, failed every time. In the end I bit the bullet and formatted the internal drive, then flashed again - worked like a charm - figured since I was going to pass it over for a new one or this was going to work I had little to lose. As it happens I now seem to have it back & working well.
Now have bunch of apps back installed and trying them all out, so far most appear to be fine; though Google maps crashes whenever I zoom in too far.... less than a country level, I don't mean excessively far - thoughts?

Blackdogn3 said:
Now have bunch of apps back installed and trying them all out, so far most appear to be fine; though Google maps crashes whenever I zoom in too far.... less than a country level, I don't mean excessively far - thoughts?
Click to expand...
Click to collapse
Google Maps v9+ has problems on the Xoom with all the different custom ROMS (Omni, CWM, EOS, etc). You need to downgrade to Maps v8.4.1 to get it to work.

slow1234 said:
Google Maps v9+ has problems on the Xoom with all the different custom ROMS (Omni, CWM, EOS, etc). You need to downgrade to Maps v8.4.1 to get it to work.
Click to expand...
Click to collapse
Thanks as said a newbie! Downgraded and working fine - thanks for quick reply

Blackdogn3 said:
Thanks as said a newbie! Downgraded and working fine - thanks for quick reply
Click to expand...
Click to collapse
It has also been noted that 9.2.0 is rolling out and that it works on the Xoom. I updated yesterday and did a quick check - it does appear to work fine!

No Sound
After I flashed "[ROM][4.4.4] OmniROM - Stingray/Stingray_CDMA - bigPart." onto my Verizon Motorola Xoom 4G Tablet,
I have no sound at all and also the auto-rotate feature does not work (stays locked in portrait mode until reboot).
A number of other forum members have posted the same problem. Can we get a solution from someone on the forum?

have all but twrp v 2.6.3 big part
I have every thing I need except big part v2.6.3, none of the links I've found work? Does it have to be v2.6..3. ? There seem to be updated versions?

No 3g or 1x fallback
Install this today, everything went ok, execpt i could not get verizon 3g or 1x service. 4g works fine, when i have coverage. SBF back to stock again i guess.

e:unable to mount '/cache
The process for flashing the xoom (stingray model) seems somewhat straightforward. Yet I can't seem to get a working flash from the effort. Two problems:
1) during the "wipe this and that" stage while running in recovery, I get "FAILED" for each of the requisite areas to wipe, along with other messages such as that in the title. while i find a handful of other posts within this forum from folks experiencing the same problem, i find nothing in response with useful suggestions to fix what's apparently broken;
2) the tablet boots up to the OMNI splash-screen, and that's it.
I've repeated the steps at the head of this thread umpteen-zillion times. But the result is the same after each attempt. Either some critical step (or two) is/are missing from the initial (and horribly written) description, or I have the most stubborn tablet built.
i haven't bricked the thing... i can access it via adb, and i can get into recovery with no issues. what i can't seem to do is:
1) find a TWRP download using the links provided that doesn't trip quarantine due to virus detection; or,
2) find a coherent set of instructions that correctly describe the logical flow of the process of flashing a ROM on a Xoom.
Suggestions?

CDMA Voice and data programming
Hi,
Thanks for your effort and excellent work but I need some help, The main thing i want to try, is to get back my CDMA signal because since i tried the stock rom 4.1.2 i was not able to get any Data working there, my xoom is a just CDMA with no sim or LTE upgrade and i already tried 2 basebands on it the one with the last version of the stock room and the one that gets installed with the IMML update but no luck, if by any chance you have the first baseband it would be great i guess its something like 2.00.
Another question that I have is related to BP tools or programming the Cdma xoom, every time I try to start in bp tools I was not able to see the utility, just today i tried to connect to my PC and its not able to connect to CDMA Workshop or QPST, is there a way to do that? i need to activate something? any idea would be great!
And would be great if you have any MZ600 SBF where has included the first baseband 2.00 'cause probably it will help me to recover my 3g data (it's the only thing i didn't find and try).
Thanks!!!

is this have a default calling future like any mobile?

Thank You to OmniRom for xoom devolopers (all of you)
I just wanted to post a thank you to all of the developers of the omnirom for xoom. I was able to install it tonight, with a couple soft brick scares, but it is up and ruining. I love my xoom and am very appreciative.
Thanks....Steve

Xoom OnmiROM freezes
I've got a similar problem to the problem outlined in this post. My son also has seen it on his Xoom.
When it becomes unresponsive (either on the dock or not), the only way I can recover is to hold the volume up and the power button until the tablet reboots. To me, it appears it goes into a deep sleep that the power button alone can't wake it up from.
There seems to be no set time period that the tablet has to be up before it hangs. Sometimes I can set it down for an hour and other times it's still responsive the next day.

semi-anonymous said:
I've got a similar problem to the problem outlined in this post. My son also has seen it on his Xoom.
When it becomes unresponsive (either on the dock or not), the only way I can recover is to hold the volume up and the power button until the tablet reboots. To me, it appears it goes into a deep sleep that the power button alone can't wake it up from.
There seems to be no set time period that the tablet has to be up before it hangs. Sometimes I can set it down for an hour and other times it's still responsive the next day.
Click to expand...
Click to collapse
It's not real common for this to happen, but this same issue does occasionally happen on the CyanogenMod 11 Rom also. Other than this, and the workarounds to do a few other things in Android 4.4.4, the Xoom has been a real God send that is just amazing.

Non-Functioning Sensors post-flash w/Omni Stingray
Finished flashing XOOM 4G with (in order listed):
Xoom-Universal-Root
R.A.H._TWRPv2.6.3
omni-4.4.4-20141130-1816+0100-stingray_cdma-HOMEMADE
pa_gapps-modular-pico-4.4.4-20150215-signed
UPDATE-SuperSU-v2.45
After I noticed that the auto-rotate didn't work, I downloaded "My Android Sensors" from the Play Store. It shows the NO sensor is working. What gives..?

Looking for file EOS-Stingray-imm76l-radios-update.zip
Hi all,
Can someone help with the file ?
EOS-Stingray-imm76l-radios-update.zip
Thank you

The Rom works great.
I installed it month ago and it is working fine.
Batterylife is perfect and all things are working.
Thanks

[Q] Does anybody else have a problem with the screen waking up?

Hi there, I bought an S Relay when it was first released here in the US. I just have a tiny issue with it that still hasn't been resolved in however many times I've updated the damn thing.
I currently have a cyanogenmod based rom on the phone, but this happens with almost any cyanogenmod rom. (Including the official ones) The screen, even though I unlock the phone, will sometimes decide to stay dark or give me this weird broken-crt pattern with bits of what I'm supposed to be looking at jumbled in. Does anybody else have this issue? Or am I just crazy?
In this respect, the offical samsung rom works great with the phone. I would use it if it didn't suck so bad, which is why I want to figure this out. The specific rom is FatToad[Android 5.0.2] by TeamApexQ, but this has happened ever since they started development on the cyanogenmod rom way back when.

Are you using bluetooth when this happens? As of FatToad 5.0.2, currently the only verified reason for this to happen is memory exhaustion (and resultant spike in CPU as it attempts to swap and fails) The only thing I've seen to cause this and not fall prey to Android's low memory killer is the bluetooth stack which seems a bit buggy. If you are not using bluetooth, please send me a logcat of the issue. Also, when this happens, can you still get to adb?

Magamo said:
Are you using bluetooth when this happens? As of FatToad 5.0.2, currently the only verified reason for this to happen is memory exhaustion (and resultant spike in CPU as it attempts to swap and fails) The only thing I've seen to cause this and not fall prey to Android's low memory killer is the bluetooth stack which seems a bit buggy. If you are not using bluetooth, please send me a logcat of the issue. Also, when this happens, can you still get to adb?
Click to expand...
Click to collapse
I'm going to install android studio now and see if I can get the log info. But no, without bluetooth enabled, this still happens.

I just dumped the log from my phone around when this happens. It took a few tries to get it to happen, but it eventually did. I stopped logcat right after I got the screen to wake and unlock successfully. I'll attach it here.
Also, adb does work even when the screen doesn't wake up.
(I had to zip it since the size nazis caught me 36 kb over the 512 kb limit.)

jjsullivan5196 said:
I currently have a cyanogenmod based rom on the phone, but this happens with almost any cyanogenmod rom. (Including the official ones) The screen, even though I unlock the phone, will sometimes decide to stay dark or give me this weird broken-crt pattern with bits of what I'm supposed to be looking at jumbled in. Does anybody else have this
Click to expand...
Click to collapse
Same problem here, and I have yet to find a solution (CM11)

I tried to change the governor, and it seemed to work, but then I*updated to Valdius 5.0.2, and no wakelocks.

wifi problem, CM12 fresh install

So I wiped the phone completely, installed the latest CM12 nightly, franco kernel, gapps. The usual. Everything went buttery smooth, connected to wifi, got all my apps installed, settings set, and set my phone down.
Come back to it a few hours later and there was an exclamation mark over the wifi icon, which took several seconds to go away. Now the wifi is INCREDIBLY slow and/or won't work. Facebook won't load, webpages won't, the play store will let me search around it I can download an app but it takes maybe a minute of just sitting there before it starts to download (and then it will download at a slow speed but not this excruciatingly slow speed).
I've used this same setup for a long time and never had this problem, nor have I ever had this problem with any combination of phone/rom/kernel/settings. It wasn't even happening earlier, it just started within the past hour. Has this happened to you guys? What's going on, and how do I fix it?

There's no problem with lag as far as I can tell. Everything works great except the wifi, and everything WAS working perfectly until the wifi started acting up an hour ago.
LTE works fine. Things that didn't help the problem:
Rebooting
Wiping cache, dalvik, and internal storage then rebooting
Forgetting network and reconnecting
I'm sure I could reset the entire phone and things would work again because this must be some bug, but I'd rather not have to do that.

.Psd
I have this issue and having more time than brains I hammer at it until my desire is met!
I first thought it was from dirty flashing but it isn't.
I found that opening my wifi connection and getting to advanced settings and the setting DHCP to static and giving it any IP address in your range. Mine said it was 192.168.1.192 so I went with 192.168.1.19(4) and bam it worked!
I have done this with iphones by giving them the DNS of google 8.8.8.8
Good luck
Rick

dentman said:
.Psd
I have this issue and having more time than brains I hammer at it until my desire is met!
I first thought it was from dirty flashing but it isn't.
I found that opening my wifi connection and getting to advanced settings and the setting DHCP to static and giving it any IP address in your range. Mine said it was 192.168.1.192 so I went with 192.168.1.19(4) and bam it worked!
I have done this with iphones by giving them the DNS of google 8.8.8.8
Good luck
Rick
Click to expand...
Click to collapse
I'll try it, but then how come it was working fine earlier and now it's being problematic? Also, I don't see any setting to change the DHCP...
(I've never had to do this before, even with this exact setup... :/)

dineshjumani said:
I did not face this issue till now but it seems opo have many issue I have issue with lag in games and did you try factory reset or try installing again and please also help me by telling do you have lag in games in opo in small games like subway surfers or dumb ways to die 2
Click to expand...
Click to collapse
You're already discussing this here:
http://forum.xda-developers.com/showthread.php?t=3066492
Transmitted via Bacon
---------- Post added at 15:56 ---------- Previous post was at 15:53 ----------
.psd said:
I'll try it, but then how come it was working fine earlier and now it's being problematic? Also, I don't see any setting to change the DHCP...
(I've never had to do this before, even with this exact setup... :/)
Click to expand...
Click to collapse
Are you running the same build of Franco as when it was working perfectly? Something could have changed within the kernel perhaps, try using the stock kernel with a ROM before creating bug reports.
Transmitted via Bacon

This isn't a bug report, and it's explicitly regarding a setup (perhaps the most popular setup) involving a custom rom and kernel.
The kernel version is the same. As I stated, everything worked fine, as it ALWAYS does with this very stable setup (OPO + CM12 + Franco kernel), then when I came back to my phone the wifi was having problems and has been since.
I just wiped the phone completely and reinstalled the rom and kernel, and it's still having the problem. The only difference is now I can't reinstall any apps because the Internet is effectively nonexistent...

.psd said:
This isn't a bug report, and it's explicitly regarding a setup (perhaps the most popular setup) involving a custom rom and kernel.
The kernel version is the same. As I stated, everything worked fine, as it ALWAYS does with this very stable setup (OPO + CM12 + Franco kernel), then when I came back to my phone the wifi was having problems and has been since.
I just wiped the phone completely and reinstalled the rom and kernel, and it's still having the problem. The only difference is now I can't reinstall any apps because the Internet is effectively nonexistent...
Click to expand...
Click to collapse
Ok, but you didn't mention which build of Franco you're on. Franco evolves, like any other kernel, to keep up with how the ROMs evolve. And vice versa.
I had assumed that seeing as it was after a flash, that the chances of either the ROM build version or the kernel build version changing were pretty high. Or don't you update your ROM or your kernel? If you're on the latest CM12 nightly but still using whatever build of Franco you're on then it isn't the same setup you've been using, because part of that config has changed (different ROM build).
Anyway, you came here looking for help. And one of the first things anyone who's even slightly capable in the world of ROM/kernel flashing will tell you is to test without the custom kernel. That's basic troubleshooting, it's a process of elimination. If the problem stops, there's a high chance the kernel was causing it (or there's a mismatch between the kernel build and the new ROM build), if the problem persists you've pretty much ruled out the kernel as the problem, move on to next possible cause. It'll take you less than a minute to dirty flash the ROM zip so you're on the stock kernel, not hard at all.
Transmitted via Bacon
---------- Post added at 16:25 ---------- Previous post was at 16:20 ----------
PS. The q&a and troubleshooting section is here:
http://forum.xda-developers.com/oneplus-one/help
Transmitted via Bacon

Perhaps we misunderstood rah other. What I meant was that earlier today I wiped my device and installed cm12 and Franco kernel. Everything was working fine, I downloaded all my apps (over wifi, which was working fine), set my settings, then left the device alone for several hours. When I picked it up later on, there was an exclamation mark on the wifi icon, which took awhile to go away. Even after it went away, the Wifi has remained dysfunctional.
A wipe and reflash doesn't restore proper wifi functionality. At worst, I would expect it to restore wifi and then give me trouble some hours later, but in fact the wifi is botched from the get go, suggesting that something in my phone has changed.
But my main point was to see if this is a problem others have experienced, because I never have before. And if people had experienced if, I'm curious what they did to resolve the issue.

.psd said:
Perhaps we misunderstood rah other. What I meant was that earlier today I wiped my device and installed cm12 and Franco kernel. Everything was working fine, I downloaded all my apps (over wifi, which was working fine), set my settings, then left the device alone for several hours. When I picked it up later on, there was an exclamation mark on the wifi icon, which took awhile to go away. Even after it went away, the Wifi has remained dysfunctional.
A wipe and reflash doesn't restore proper wifi functionality. At worst, I would expect it to restore wifi and then give me trouble some hours later, but in fact the wifi is botched from the get go, suggesting that something in my phone has changed.
But my main point was to see if this is a problem others have experienced, because I never have before. And if people had experienced if, I'm curious what they did to resolve the issue.
Click to expand...
Click to collapse
Ok, fair enough. But like I said, the first thing you need to do is get rid of the custom kernel in order to test properly. The fact that it was working fine earlier doesn't mean it can't be the kernel, at the same time I'm not saying that it is the kernel, what I'm saying is testing on stock is the first step in working this out, you need to remove any variables.
Transmitted via Bacon

I think it's my modem/router (net gear c3000). Will look more into the situation later.
EDIT: bingo. Factory reset the modem and problem fixed immediately.

Great, glad to see you got it worked out.
Transmitted via Bacon

Have the same problem connecting to wifi after I installed CM12 Nightly.
Doing a factory reset now and checking.
Hope this should solve the wifi issue
---------- Post added at 10:35 AM ---------- Previous post was at 10:24 AM ----------
Did factory reset but still the same issue.
The wifi status is still connecting from a long time........doesn't get connected

Did turn on and turn off the flight mode too (read in few posts that it solved the issue). But it did not solve the issue...
Any help or suggestion?