Wifi not starting - solution yet? (Maybe WMWifirouter related?) - Touch HD General

My wifi won't start. Whether it's through TouchFLO's comm manager or Window's own Wifi connection, it will give me the "Busy" rotary and then nothing happens.
I know exactly when the problem first appeared, though. I was using WMWifirouter (an ancient version, .8 or .9 something) while it was tethered to a Macbook for power (I think on ActiveSync, but I don't remember). From what I gather, that might not have been a good idea, or, rather, that theoretically should not have worked. But, it did. I disconnected the phone, and since then I've had the aforementioned wifi issue.
I've searched XDA and Google, and it seems the best answer I can find is to hard reset and see if it works. However, it seems that for a large majority of people who tried this method, the problem doesn't go away.
I'm hesitant to try a hard reset, as my HD's been working fine for the past 5 months and I've got a lot of time and work put into it, when it might not get me anywhere.
Hence, I'm asking if anyone's come across a solution to this problem that might work. I'm hoping it might be as easy as a registry tweak (I have seen some "solutions" that involve the registry, but they don't appear to apply in this case).
Since I'm in the US, and the HD is not officially provided by any carriers, I might have a lot of trouble getting any kind of warranty work done on it, and that also entails losing the phone for 2+ months, as best I can tell.
I might try flashing a newer HTC ROM, although I would be pretty mystified that my old ROM suddenly wasn't good enough. Maybe it's just that a new factory ROM would place the correct registry settings back in order?
Sorry for the long post, I'm just frustrated that I am unable to use wifi and that I'm starting to think the only solution will be to get a new phone or live without it.
Does anyone have any thoughts?
(I've looked at several threads on XDA already, none of them were at all resolved or even directly discussing the HD, so I think it's okay to post this thread.)
EDIT: I could tell I was going to get no response here, so I just went ahead and hard reset the device. That seems to have fixed it, for now. Wifi's working how it should. I'm adding this edit here for anyone else has this problem.

Just a bump, and also to add that when I run WMWifirouter with logging, it shows that it fails to Rebind the WLAN and also the CM-Set fails, if that is any clue.

Another detail, I notice that under Settings > Connections > Wi-Fi > Advanced > Advanced, there is nothing under Status, MAC, IP...I'm guessing that will always be empty if it's not connected? If not, are there values I should fill in?

Related

New Sprint Rom Is Here ???

New sprint rom?? http://forum.ppcgeeks.com/showthread.php?t=10293&page=3
http://download.america.htc.com/RUU_...PL106_Ship.exe
It's been confirmed. That is the new official ROM for Sprint. It fixes the Bluetooth issues among others. No Rev. A or GPS of course, but that was expected.
question is, is this really "better" than the alltel rom that has been available for a long time already over at PPCgeeks...
The alltel rom fixed the BT and alarm problem as well. I'm excited to see that Sprint finally caught up, but I'm wondering if this is better than the setup I currently have.
Well I for one am happy and upset.. I would like to see REV A , as I need the faster upload speeds for sending big files from my 4gb micro sd.
I havent tried the Alltel rom, but the new sprint rom fixes the keyboard lag + wm6 responsiveness problems.
After reading all of the threads over at PPCGeeks, it seems like there are some mixed results on the ROM (to be expected I guess, you can't appease everyone.)
-Most are reporting the BT fix worked correctly.
-I didn't see anyone say that the Alarm fix didn't work
-People are reporting that the OS seems a little faster and better at managing memory, such as reclaiming more when you close an app, etc.
-The radio version on the Sprint ROM is 1.47, compared to 1.40 of the Alltel, some were reporting better reception between this one and the stock rom (1.32 I believe)
-the most widely spread issue I saw was that some users were having issues with their dpad not working. At first, someone pinned it down to sprinttv, as it worked after they removed it, but then others said that the problem returned.
-YMMV, but some reported that when they skipped the sprint customization of the rom (when it starts initially, after the 3 second delay where you can soft reset) it caused issues on their phone. One person said that a workaround for this was to let it install EVERYTHING initially, and then do a hard reset and skip the customization process. It makes sense that if it were something with the EXTRom that it might put something in there that you needed, but again, not sure on this one.
-I can't believe how many people were stuck on the idea that they would be able to use Sprite Backup or SPB Backup to restore all of their stuff. Let me say this again, because I don't think it can be said enough. Unless you are just restoring folders such as your documents or something non-system related, you CANNOT use these programs. You WILL overwrite the new files with the old ones, causing a boatload of issues, if it even works at all. So don't do it, or you will cause yourself some headaches. Activesync remembers the apps you have installed, so just sync afterwards and click the boxes. For your other stuff such as contacts, back those up with a contact backup app or sync with outlook if you've got it.
just my two cents.
kmartburrito said:
After reading all of the threads over at PPCGeeks, it seems like there are some mixed results on the ROM (to be expected I guess, you can't appease everyone.)
-Most are reporting the BT fix worked correctly.
-I didn't see anyone say that the Alarm fix didn't work
-People are reporting that the OS seems a little faster and better at managing memory, such as reclaiming more when you close an app, etc.
-The radio version on the Sprint ROM is 1.47, compared to 1.40 of the Alltel, some were reporting better reception between this one and the stock rom (1.32 I believe)
-the most widely spread issue I saw was that some users were having issues with their dpad not working. At first, someone pinned it down to sprinttv, as it worked after they removed it, but then others said that the problem returned.
-YMMV, but some reported that when they skipped the sprint customization of the rom (when it starts initially, after the 3 second delay where you can soft reset) it caused issues on their phone. One person said that a workaround for this was to let it install EVERYTHING initially, and then do a hard reset and skip the customization process. It makes sense that if it were something with the EXTRom that it might put something in there that you needed, but again, not sure on this one.
-I can't believe how many people were stuck on the idea that they would be able to use Sprite Backup or SPB Backup to restore all of their stuff. Let me say this again, because I don't think it can be said enough. Unless you are just restoring folders such as your documents or something non-system related, you CANNOT use these programs. You WILL overwrite the new files with the old ones, causing a boatload of issues, if it even works at all. So don't do it, or you will cause yourself some headaches. Activesync remembers the apps you have installed, so just sync afterwards and click the boxes. For your other stuff such as contacts, back those up with a contact backup app or sync with outlook if you've got it.
just my two cents.
Click to expand...
Click to collapse
i took the plunge yesterday, i skipped out on all the sprint customization and everything turned out ok....haven't tested bluetooth yet but everything you said seems to be on point...
kmartburrito said:
-YMMV, but some reported that when they skipped the sprint customization of the rom (when it starts initially, after the 3 second delay where you can soft reset) it caused issues on their phone. One person said that a workaround for this was to let it install EVERYTHING initially, and then do a hard reset and skip the customization process. It makes sense that if it were something with the EXTRom that it might put something in there that you needed, but again, not sure on this one.
Click to expand...
Click to collapse
Just to clarify this is part. A hard reset will completely erase any carrier customizations there is absolutely no reason for installing extrom, hard resetting then skipping. Just start out with the hard reset, skip customizations and you'll be good to go.
Although there are still the other bugs with the update =)
Just installed it a while ago, skipped the sprint customizations, everything seems to be running good and actually noticeably quicker than before. New startup screen is cool too, no problems thus far =)
do yourself a favor and wait for the next rom. If you didn't already experiance it, your device will lock up and go to sleep requiring a soft reset...very unusable. and BT will turn off after a few minutes randomly.
load the colonel's rom on, it's much better imho
Seems to only happen to some people though. I have had my phone on pretty much straight since the rom update.
there seems to be a major bluetooth issue where the BT just shuts off periodically.. Not sure how,but they found a way to make bluetooth even worse!
I can't carry on a conversation without BT shutting off on me.. (or use the gps without it shutting off/etc..)
-mark
I haven't updated yet, plan to over the weekend, but I would suggest anyone having problems to stop and consider their setup first...
1. What programs are installed that could cause problems?
2. What registry hacks have been done that may cause problems?
3. What configuration settings might need reset that may cause problems?
For example, after a hard reset, Enhanced Network over USB is enabled by default, and this often causes Active Sync to have issues. Likewise, power management tweaks will have reverted to defaults and you may like a more finely tuned setup.
As for memory leaks being better/worse, you may have programs installed that are out of date/buggy.
I realize it's easier to jump on the "this sucks" bandwagon, but it doesn't help you or other users with legitimate problems when no consideration is given to what is causing a given problem.
These situations are precisely why the instructions tell you that EVERYTHING will be erased. This is a good thing since it forces you to clean house, but it also means you have to pay attention to those things you often neglect or may have changed ages ago and forgotten.
Finally, if all else fails, try the ROM update again. Sometimes things go wrong.
Sorry if this seems like a rant, I just want people having issues to place blame where it truly belongs. After considering these matters, if you still have problems, definitely let HTC and the rest of us know.
Best Regards,
Aaron
GoodThings2Life said:
I haven't updated yet, plan to over the weekend, but I would suggest anyone having problems to stop and consider their setup first...
1. What programs are installed that could cause problems?
2. What registry hacks have been done that may cause problems?
3. What configuration settings might need reset that may cause problems?
For example, after a hard reset, Enhanced Network over USB is enabled by default, and this often causes Active Sync to have issues. Likewise, power management tweaks will have reverted to defaults and you may like a more finely tuned setup.
As for memory leaks being better/worse, you may have programs installed that are out of date/buggy.
I realize it's easier to jump on the "this sucks" bandwagon, but it doesn't help you or other users with legitimate problems when no consideration is given to what is causing a given problem.
These situations are precisely why the instructions tell you that EVERYTHING will be erased. This is a good thing since it forces you to clean house, but it also means you have to pay attention to those things you often neglect or may have changed ages ago and forgotten.
Finally, if all else fails, try the ROM update again. Sometimes things go wrong.
Sorry if this seems like a rant, I just want people having issues to place blame where it truly belongs. After considering these matters, if you still have problems, definitely let HTC and the rest of us know.
Best Regards,
Aaron
Click to expand...
Click to collapse
My experience is as simple and "vanilla" as it gets:
-Loaded new ROM
-Hard reset
-Stopped customizations
-Installed NO apps, did not turn on BT, made no calls, did nothing else
-3 DSODs in 4 hours
-Did a second flash (from a second computer with a freshly downloaded ROM)
-Hard reset
-Allowed customizations to run
-Again no apps, BT or calls
-DSOD within an hour
wsparvis said:
My experience is as simple and "vanilla" as it gets:
-Loaded new ROM
-Hard reset
-Stopped customizations
-Installed NO apps, did not turn on BT, made no calls, did nothing else
-3 DSODs in 4 hours
-Did a second flash (from a second computer with a freshly downloaded ROM)
-Hard reset
-Allowed customizations to run
-Again no apps, BT or calls
-DSOD within an hour
Click to expand...
Click to collapse
Sounds atypical to me, given that most users are updating without issue and experiencing better results. I have no reason to doubt your experience though... it sounds like you have faulty hardware, but here's a download link to the previous firmware if you're interested in trying it out first:
http://www.htcamerica.net/support/mogul/software-downloads.html
No, "most" users are not experiencing better results. I've been using this ROM with poor results, as have many others. Read this thread for many sad tales of woe:
http://forum.ppcgeeks.com/showthread.php?t=10302
Basically, the new ROM does fix a bunch of things, but breaks others, so I would not recommend installing this ROM.
1) Locks up when changing from Sprint to roaming. You can test this by manually switching from Sprint to roaming and back a few times, you WILL get a phone lockup.
2) BT turns off randomly for many users.
3) Turn on BT, let unit sit for a few minutes until it goes to sleep, turn unit back on, dpad no longer works. I have seen this myself many times.
Don't install this update --- use the Alltel ROM or wait for another update.
GoodThings2Life said:
Sounds atypical to me, given that most users are updating without issue and experiencing better results. I have no reason to doubt your experience though... it sounds like you have faulty hardware, but here's a download link to the previous firmware if you're interested in trying it out first:
http://www.htcamerica.net/support/mogul/software-downloads.html
Click to expand...
Click to collapse
1) You're incorrect in stating that most users have no problems, etc. Some do, some don't. Read the posts at ppcgeeks, pdaphonehome, BAW, hofo. I am not at all alone in having problems.
2) I downgraded 2 days ago, and my Mogul runs fine again - just exactly like it did for the 1st 3 months I had it. It's not my hardware! It's a bad ROM release.
Not everyone uses the phone in the same way at all. So of course some people will not see the same problems that others do.
If you never use Bluetooth and never roam, then this ROM will work for you. Otherwise, it will cause problems. For me, Bluetooth works much better in 2.09, and I rarely if ever see lockups as I have with 2.16. So, I'm going with 2.09 for now. The alarm problem IS fixed in 2.16 but I never use alarms on my phone so it's not an issue for me. Freezes when roaming ARE a problem.
cbunting said:
do yourself a favor and wait for the next rom. If you didn't already experiance it, your device will lock up and go to sleep requiring a soft reset...very unusable. and BT will turn off after a few minutes randomly.
load the colonel's rom on, it's much better imho
Click to expand...
Click to collapse
is colonels rom built on the alltel core rom? if so it may be our best bet as of now.

can i get GPSServer Uninstall CAB

thats works please
thank you
I have never gotten it to work. Why do you need it?
Im gonna go out on a limb here but I think he wants it so he can uninstall it...Maybe.. I might be wrong though. LOL J/K of course.
No really, I think I need it too. My Touch for some reason just wont pick up satellites anymore. Kinda just happened out of the blue. I was using it just fine a few days ago and now I cant acquire any satellites using either Google Maps Garmin XT or Live Search. Only thing I recently did was install G-Alarm... I'm not sure If that would cause it to stop working though.
There are other posts about this problem..Verizon must have blocked the GPS function....again
^^ Yup... Now the trick is to figure out what they did and how to undo it.
I don't understand why someone would want to uninstall the gpsserver cab. Reversing will involve changing qpst and registry settings.
Same thing here, out of the blue it stopped working. Never could figure out why a company wants to PO its customers so bad. Would be curious if this just localized or system wide. I am the Minneapolis area.
My XV6900 was working fine with GoogleMaps and Livesearch. That is, until this past Tuesday. Nothing changed on the phone. Now just searches for sats and never finds any. I'm in RI, but I first noticed it when in MD.
Somehow, Verizon must have modified my phone.
I also tried to re-install GPSServer, but since the un-installer doesn't work, re-installing didn't work either.
I might try re-installing MR1 and going for it again, but that's not the right solution if Verizon can find me again and re-modify...
Same problem in Jacksonville, Florida area using XV6800 and GoogleMaps.
Assuming this is some action that came from Verizon, I'm very dissappointed in what they have done. What it is costing them to find ways to block the GPS hardware that we all paid for and the loss of customer loyalty has to be more than what they earn on the GPS "service" they offer. Once again, a greedy company that does not see the big picture.
Same experience in Southern California. Everything had been working fine for months, but I lost GPS functionality on Wed 3/18. It's truly hard to understand why Verizon would be so shortsighted. Can't wait to see if someone posts a solution to this problem.
GPS is Now Working with GoogleMaps
OK, it is now working, but I must admit I'm not exactly sure why or how.
I changed the registry settings for PDEAddress and PDEPort to 5C8BC6D8 and 8889, respectively (as posted on another site) using PHM RegEdit and soft reset, but the GPS still did not work. So, I set the settings back to their original values and soft reset again and now the GPS is working fine.
I'd like to see if someone else can replicate this and get the same result. If so, we may have the solution.
So, I would suggest the following steps:
Record the current values of these two registry keys.
Change the settings of these two keys per serfboreds post.
Soft reset.
Change key values back to original settings.
Soft reset.
Test result.
I look forward to hearing if someone else can get this to work.
Lost GPS Again
After a wonderful day of enjoying the unfettered use of the GPS hardware that I PURCHASED WHEN I BOUGHT MY XV6800, I have again lost GPS functionality.
I sure hope that someone can come up with a remedy for this.
booberthecat said:
OK, it is now working, but I must admit I'm not exactly sure why or how.
I changed the registry settings for PDEAddress and PDEPort to 5C8BC6D8 and 8889, respectively (as posted on another site) using PHM RegEdit and soft reset, but the GPS still did not work. So, I set the settings back to their original values and soft reset again and now the GPS is working fine.
I'd like to see if someone else can replicate this and get the same result. If so, we may have the solution.
So, I would suggest the following steps:
Record the current values of these two registry keys.
Change the settings of these two keys per serfboreds post.
Soft reset.
Change key values back to original settings.
Soft reset.
Test result.
I look forward to hearing if someone else can get this to work.
Click to expand...
Click to collapse
Didn't try your steps, but did do PDEAddress and PDEPort to 5C8BC6D8 and 8889, respectively (as posted on another site) using PHM RegEdit and waited awhile so new settings could take and be written to registry. Had to reset a couple of times and make sure phone had clear view of sky. It took awhile to see the satellites and lock on, so be patient. Did this yesterday and accuracy seemed off some, but today locks in faster and seems to be more accurate. So, for now, it is working again.
Reply to bparent
I tried those settings again and GPS is back!
Thanks for your post and getting me to explore that option again!
I'm the Washington DC metro area. Boy am I glad I found THIS thread. My GPS is mysteriously not working now either. I want to try Booberthecat's suggestion but you didn't provide explicit instructions. Are these reg keys under HKLM?
fluidj said:
I'm the Washington DC metro area. Boy am I glad I found THIS thread. My GPS is mysteriously not working now either. I want to try Booberthecat's suggestion but you didn't provide explicit instructions. Are these reg keys under HKLM?
Click to expand...
Click to collapse
Look in last 5 or so pages here. http://forum.xda-developers.com/showthread.php?t=424387
drewcam888 said:
Look in last 5 or so pages here. http://forum.xda-developers.com/showthread.php?t=424387
Click to expand...
Click to collapse
Thanks Drew!
The fix posted by Zaneymonster worked!
I'll paste here too:
Zaneymonster said:
Originally Posted by zanymonster View Post
Here's is the tested and proven solution for us.
1) if you haven't already, you need to flash your phone to MR1 or MR2 official release. You can find the MR1 for 6900 herehttp://www.pcdphones.com/phone_downl...zon%20Wireless
2) install Valhalla .cab file for gpsserver (attached)
3) edit the registry and change the following 3 entries:
* \KHLM\Software\Valhalla Legends\GPSServer\PDEAddress = C3CF657E (REG_DWORD Hex)
* \HKLM\Software\Valhalla Legends\GPSServer\PDEPort = 7788 (REG_DWORD Decimal)
* \HKLM\Software\Valhalla Legends\GPSServer\Mode = 0
Reboot. You must do a soft reset before this will work. Get ready for slower locks and less accuracy, but it does work, and it is good enough for turn by turn in Live Search.
I understand most of you have a 6800, and that that is in fact what this thread is supposedly all about, but the 6900 has the same GPSOne chipset and works with the same gpsserver.exe when using the stock MR1 or MR2 roms.
I have done 3 phones today, and it fixed them all! (Noting of course that they no longer work with aGPS, which is a serious drag)
Please also note that I DID NOT install any of the other "fixes" or utilities posted here, just the valhalla .cab file and that's it.
There are some tweaks that may make for faster fixes, but I am still researching those.
I am still hoping that rldleblanc will tell us how he discovered the address and port that worked. I suspect he subscribed to VZNav and did some packet analysis. Either way, thanks man!
Click to expand...
Click to collapse
booberthecats solution worked like a champ for me. Thanks.
I've been trying to get this to work for 3 weeks, Zaneymonster reg edit values was the final piece to the puzzle, THANKS!
same in philadelphia pa
however it would work if i let it search for awhile. by the time i made it to where i'd be going about an hour or maybe a little less, it would have locked in a signal. a couple months of this...
today 5/16 is the first i've tried it since. and it locked in within seconds. i reset and on/off, trying to see if it would do it cold. and it sure locked in quick.
i didn't do anything it just happened.
but im happy, since im heading on a trip tomorrow!
vern

Unbelievably aggravating browser issue...

Im at my wit's end. Im about to give up on my beloved Android, this makes no sense. Surely Im not the only person experiencing this hair pulling issue. It happened with my g1, my MT3G and now my nexus one:
yahoo.com
capitalone.com
and god knows what other sites
I can sign in to these sites a few times and then i get an error saying im entering invalid info. I am NOT entering invalid info, ive tried signing in 30 times each time i sit down to try to deal with this
This issue happens without me changing any settings or downloading any apps
When i wiped the g1 or the MT3G the sites would again work a few times
I feel like I should try the iphone or a windows phone.
Does anyone know how to wipe this phone (yes i googled the s*** out of this question)? And more importantly does anyone know whats making my Android phones reject these popular websites? I love google, but these are legit sites that this phone ought to be able to handle. thanks for any help
Browser>Menu>More>Settings...
Clear Cookies, Form Data, & Cache one at a time to see if one helps.
what browser are you on? if you havnt switched to the dolphin browser (multitouch yay!) or opera mini (fastest prolly), id highly recommend you try them if you havnt already and both are faster than stock
im losing my ****
thanks for the replies though. I have deleted cache, etc. in the browser many times and i have tried dolphin, but it hasnt helped. It seems so strange that I cant find any existing issue discussion here or in the g1 or mt3g forum, capitalone.com might be overlooked but surely many others have had the yahoo.com issue, i mean i first turned on the phone, signed in fine then could never sign in again, i havent done anything to set me apart from the other users and yet ive had this issue on all 3 android phones. ive now reset my nexus phone without saving my settings or apps and still i can sign in once and never again.
any other ideas? thank you
1 more browser, try opera lol... after that idk... sorry bud
DMaverick50 said:
im losing my ****
thanks for the replies though. I have deleted cache, etc. in the browser many times and i have tried dolphin, but it hasnt helped. It seems so strange that I cant find any existing issue discussion here or in the g1 or mt3g forum, capitalone.com might be overlooked but surely many others have had the yahoo.com issue, i mean i first turned on the phone, signed in fine then could never sign in again, i havent done anything to set me apart from the other users and yet ive had this issue on all 3 android phones. ive now reset my nexus phone without saving my settings or apps and still i can sign in once and never again.
any other ideas? thank you
Click to expand...
Click to collapse
Did you delete Cookies and saved form data?? or was that part of "etc"?
Opera Mini 4 sucks on Android. Hopefully Opera Mini 5 and Opera Mobile will be better and have multi-touch.
Hi there I'm keen to help you replicate this problem. Is it anythng to do with the number of unsuccessful attempts per session. Most sites lock you out after a certian number of incorrect entries. I know some SIPs can be a ***** to get first time.
Have you unlocked your phone flashed a custom rom? Are you signing in over wifi? might it be an isp issue?
neucleotide said:
Hi there I'm keen to help you replicate this problem. Is it anythng to do with the number of unsuccessful attempts per session. Most sites lock you out after a certian number of incorrect entries. I know some SIPs can be a ***** to get first time.
Have you unlocked your phone flashed a custom rom? Are you signing in over wifi? might it be an isp issue?
Click to expand...
Click to collapse
thanks for the help.
It happens on 3g, e, g and wifi
I havent rooted
i dont know about the isp thing
The issue occurs after the first or second successful login, without any extra attempts in the session
When the issue happens i can wipe the phone and am able to sign in again, i think if i dont sign out it will stay signed in and i can go with it like that for a bit longer but eventually signs me out and back to square one
When it happened on my MT3G i had a couple of refurbished replacements and the issue persisted
TMO told me that it was an app screwing it up because when i restarted in safe mode i could sign in. But i started with a clean wipe and could only sign in once or twice. Surely im doing something wrong but damned if i can figure it out
I use capital1 and yahoo but I've never had any issues with them on my G1, MyTouch or N1, weird.
Tried it on my G1 and it's working just fine!
Maybe you could provide a log of what is happening the moment you try to login? I think you should be able to do a logcat on a non-rooted phone.
Using ADB just run:
Code:
adb logcat > log.txt
i really, really appreciate everyones help, ive been dealing with this for a long time and its been quite frustrating.
I just reset the phone, signed in to two of the issue sites and ive been changing settings and downloading apps but i havent signed out of either site nor have i reset the phone or deleted the browser cache or data. Im guessing itll go bunk in the next day or two as usual and if it does im going to try to get a log. I havent been doing any rooting/development stuff since my g1 about 5 months ago so im a bit rusty but i should be able to manage a log...
I have problems with certain sites and authentication while tethered. If I had to pull a unicorn out of my ass I would assume it's what proxy you're connected to. Someone smarter than I would probably be able to give you a way to test. I've been able to duplicate the problems on my various Android devices. So I don't think it's android as much as it my provider in my area. I don't have an intimate knowledge of their topology so someone shed some light on this.
When you log into the sites, do they run in a mobile version or desktop version?
I use dolphin, much better browser
How complex is your userid/password?
if it contains some symbols or similar, perhaps try a less complex one??
Simple Id and password. Problem w/ mobile as well as desktop version and I've tried dolphin...
I've logged in a couple of times after latest wipe, there's a slight chance the disruption coincides with me setting up yahoo in the email app. I don't know if that would explain anything but it wouldn't explain capitalone though both are currently working and the only thing I've done differently is not set up yahoo email..problem solved? I'm afraid to sign in and sign out too much to test it, I suppose ill find out sooner than later
I keep getting a uportal error on another site I've had no problems with on g1 or mytouch. From googling it I believe uportal error indicates a proxy issue can anyone elaborate or otherwise explain? The last time I messed with proxies was with g1. This seems to be set up a bit differently, or else I've forgotten where to find them...
same issue
experiencing the same issue. cleared all existing data on the phone, wiped/installed.
CM-5.0.4.1 w bits. Can't figure it out.

Bell Atrix , lost wifi, bluetooth and rebooting lots

Hey,
My phone started acting up after 1 month of upgrading to gb 2.3.6. My wifi and bluetooth wont turn on and my phone constantly reboots. I used CWM and did a full wipe. and flasehd the darkside ROM. Still i have the same issue.
Does anyone know what do I need to do to get my phone working?
Thanks
A friend of mine has the same problem, Im pretty sure thats a hardware issue already. !
running gb 2.3.6 #4 - still no wifi/bluetooth
Having the same issues. Does anyone know if wifi and BT share an antennae?
try flashing a differnt radio? for your phone specs
look in ihop thread or fruit cake thread for your radios
r0nz3y said:
Hey,
My phone started acting up after 1 month of upgrading to gb 2.3.6. My wifi and bluetooth wont turn on and my phone constantly reboots. I used CWM and did a full wipe. and flasehd the darkside ROM. Still i have the same issue.
Does anyone know what do I need to do to get my phone working?
Thanks
Click to expand...
Click to collapse
schufly73 said:
Having the same issues. Does anyone know if wifi and BT share an antennae?
Click to expand...
Click to collapse
I'm pretty sure this is a hardware issue... I have been having this problem myself, and have tried flashing many of ROM and Radio's since it has reared it's ugly head - all to no avail. The WiFi an Bluetooth do share the same Broadcom chip... maybe there's enough of us experiencing the problem that we can collaboratively order a dozen of these things (they only seem to sell in bulk).
Had the same issue, ATT had to replace the phone.
Any more news on this issue?
Same thing happened to my Atrix last week (Bell, 2.3.6, locked bootloader, unrooted).
Same here
Same problem on my original Atrix, which was replaced under warranty by AT&T six months ago. Recently my replacement Atrix has been having the same problem. Wifi won't enable and frequent reboots.
Although the phone should still be under the 1-year warranty, AT&T refuses to honor it because the screen is cracked (so much for Gorilla glass).
After getting two phones with the same problem, and hearing about countless others having the same problem, and getting screwed out of the warranty, this is definitely my last Motorola phone.
EDIT:
The "fix" that was originally posted here doesn't actually work. I'm almost certain that this is a hardware problem. As of now there is no software fix, if one even exists.
Check this thread for more info:
https://forums.motorola.com/posts/0c2f1387d6
I recommend that you post to acknowledge you have the same problem.
i tried the script and it tells me "oops... did NOT find wpa_supplicant.conf! any help?
cafe. said:
I found a permanent solution to the problem. It was probably more obvious than I originally thought it would be. This is probably what will fix it if you recently ran some sort of 3G tweak as it probably damaged/corrupted /data/misc/wifi/wpa_supplicant.conf. Before I get started with what what problems my phone was having:
-'Wifi Error' message when enabled
-Random reboots when trying to enable wifi
-Bluetooth worked fine (and if you are having issues with bluetooth it may be due to a similar bluetooth related file having problems)
-Impossible to fix by flashing new roms, wiping/factory reset, and virtually every other possible thing I tried
So, just before giving up, I found something called 3Gturbocharger--which can be downloaded from here: http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021 REMEMBER: IT'S 3GTURBOCHARGER, NOT ANY OF THE OTHER SIMILARLY NAMED FILES.
Now, the value of the script isn't really in the "tweaks" it provides, but rather the easy way it provides to reset the file of interest (/data/misc/wifi/wpa_supplicant.conf). Run the script using "script manager" as root, once you've done this you'll be able to run a feature within the script called Wi-fixer. Run it and reboot. The problems should all be corrected. You could also try to manually navigate to 'data/misc/wifi/wpa_supplicant.conf' and simply rename it to whatever you want (as the script does), at which point the old file will be replaced by a newly generated one.
I'm assuming that in your case the bluetooth equivalent of "wpa_supplicant.conf" was corrupted. Possibly /data/misc/bluetooth/dynamic_auto_pairing.conf or /data/misc/bluetooth/incoming_connection.conf. Worth a shot trying the method I described on those files as well. Try it out, you've got nothing to lose.
Click to expand...
Click to collapse
im getting that to
My Atrix wifi stopped working in the past, but started working again. It currently stopped working once more, giving me an Error if I turn it on. The Bluetooth has never had issues and still works, I am a month past warranty but with unlocked BL it doesn't matter anyway. This seems to be a slight issue with these phones unfortunately.
I could live with the phone without wifi, but the constant reboots are unavoidable. I notice that when I originally boot the phone, if I use it and keep the screen on it works, but as soon as I turn the screen off, it reboots. Odd to me.
Ya I have the Bell Atrix myself and I'm still on Froyo because of complaints of GB. (especially battery life) Maybe I'll do ICS, but I'll wait for some reviews since its not that easy to go backwards as say my OG SGS...
Sent from my MB860 using xda premium
Now, the value of the script isn't really in the "tweaks" it provides, but rather the easy way it provides to reset the file of interest (/data/misc/wifi/wpa_supplicant.conf). Run the script using "script manager" as root, once you've done this you'll be able to run a feature within the script called Wi-fixer. Run it and reboot. The problems should all be corrected. You could also try to manually navigate to 'data/misc/wifi/wpa_supplicant.conf' and simply rename it to whatever you want (as the script does), at which point the old file will be replaced by a newly generated one.
Click to expand...
Click to collapse
Anyone try doing this manually? I can't locate the file.
wpa_supplicant file
hi, the file is in etc/wifi and the bluetooth file is in etc/bluetooth/ i renamed the .conf files but this don't solved the problem.

Fix for Nexus 7 2013 (flo) Touchscreen Glitches

For a long time now my Nexus 7 2013 (flo) 32gb has had this annoying touchscreen glitch where it will get false readings causing it to push buttons I didn't want to press, zoom when I wanted to scroll, and generally make it unusable unless I rebooted (which on some occasions didn't fix the problem). After doing some research, I found that it seems to be a common enough problem, but there was only one thread that claims to have fixed it. Now, to be honest I didn't try his method, as frankly it looked long, complicated, and I never found the time. Yesterday the thought occurred to me that the screen may actually be picking up real interference, and that it may just simply be to sensitive, so I set about to decrease the sensitivity on the device. To decrease the sensitivity ( THIS REQUIRES ROOT) I used root explorer (you may use any file explorer that can access root files) and went to the folder "/system/usr/idc" and opened the file "touch_dev.idc" in a text editor. In this file I found the line "touch.pressure.scale = 0.0125" and changed the value from 0.0125 to 2.5. I then saved the file and rebooted. Since doing this I have not had the touchscreen glitch, and I have been using the device for a little over 24 hours now. I used to get the glitch about 3 times a day. I will continue to test this config, to see if it actually does fix the problem, but due to the nature of the problem, the only way to know if this fix works, is to use it over a long period of time. I will remove this post if the issue ever returns and I am not able to fix it using a similar method.
Notes:
* the directory is "/system/usr/idc/touch_dev.idc"
* increase the value of "touch.pressure.scale" to decrease the screen sensitivity
* make sure you have write privileges (in root explorer, don't forget to hit the R/W button before opening the .idc file in a text editor)
* don't forget to save the file
* after saving the file, reopen it to make sure the change took place, if it didn't make sure you have write privileges and actually saved it
* don't forget to reboot for the changes to apply (I'm not sure if its necessary, but am willing to bet that it is)
* this should work with other versions of the nexus 7 flo, not just the 32gb
* I am not liable for any damages caused to your device (you should know this by now)
*I have only tested this on one device, as it is the only one I have access to with this problem
* If this fix works for you, please let me know below, feedback is appreciated
* I didn't return the device, simply because I lost the receipt, and don't know if the warranty is still in place
Edit:
This does not work, after more testing issues returned. But I will continue to try different values to see if this can fix the problem.

			
				
Don't bother adjusting any further, it's a very well known problem and has nothing to do with this, put it back to it's default and then use the fix mentioned in this forum, (the software touchscreen driver fix). It's simple, takes about 5 mins, doesn't require root and actually works. TS10 solved 99% of my problems, which were pretty severe before.
Solaris81 said:
Don't bother adjusting any further, it's a very well known problem and has nothing to do with this, put it back to it's default and then use the fix mentioned in this forum, (the software touchscreen driver fix). It's simple, takes about 5 mins, doesn't require root and actually works. TS10 solved 99% of my problems, which were pretty severe before.
Click to expand...
Click to collapse
Ok, yeah I'll have to do that. I posted this a bit early, as I was seeing positive results at first and got excited. Thanks.
yes, there are 3 different fixes posted, ts10, ts20 and ts30.....and there are a couple of others in that thread too. I found the experiment ts18 worked best for me. ts10 was an improvement, ts20 better, and and ts30 too sensitive. after sticking with ts20 I decided to try the additional ones and so far 18 is best for me.
try the 3 main ones....and use the one that works best......if you still see little bugs in it, then try the experimental ones closest the 10 or 20 or 30 that worked best for you. I feel like I have a brand new device since running this fix on mine. You don't have to be rooted, but you do have to be unlocked.
I have a wifi 32 gb model manufactured Sept 2013
Question, I originally bought a n7 lte (deb) in November 2013. Don't know manufacture date. Had to return for hardware failure in the touchscreen and the replacement was manufactured in November 2013. So far I have not seen the same touchscreen issues I had with my original (ghost touches, touches not registering etc). Should I try to use the fix in that thread or leave well enough alone? Tia
pre4speed said:
Question, I originally bought a n7 lte (deb) in November 2013. Don't know manufacture date. Had to return for hardware failure in the touchscreen and the replacement was manufactured in November 2013. So far I have not seen the same touchscreen issues I had with my original (ghost touches, touches not registering etc). Should I try to use the fix in that thread or leave well enough alone? Tia
Click to expand...
Click to collapse
Well that's really up to you. If it works fine then you don't need a fix.... But if there are glitches.... Well you know where to get a fix.
Solaris81 said:
Don't bother adjusting any further, it's a very well known problem and has nothing to do with this, put it back to it's default and then use the fix mentioned in this forum, (the software touchscreen driver fix). It's simple, takes about 5 mins, doesn't require root and actually works. TS10 solved 99% of my problems, which were pretty severe before.
Click to expand...
Click to collapse
Okay, but you do know there are SEVERAL different issues with the touchscreen & that thread only will fix (partially fix as everyone I know that has tried it, still has occasional issues) one of three or more issues. There is also a grounding issue, that your reference WILL NOT FIX. There are also issues with the ribbon cable placement, which was my issue & several others, which requires opening the case & either reattaching the cable or reinforcing the connection at the terminal, which fixed mine & a few others. Just saying, I wouldn't blindly state that "this fix" will solve all your issues.
can anyone provide a flashable patch to try? Thanks
This problem is starting to annoy me really badly D:
I have seen different types of issues on my N7 2013 - 32gb. I tested using YAMTT app.
1. touch will not be registered at certain areas or ghost touches - this is worse with stock rom the tablet came with. the best solution for stock rom is to either try ts10, ts09 etc. or try different roms. I finally settled with AOSB rom with Glitch kernel, working fine.
2. touch will work fine if you hold the tablet in your hand or have it connected to usb or headphones. but wont register or see ghost touches if you keep it in a flat place and use it - (grounding issue) - there are various fixes i have seen. (a) remove the tablet and do fix (b) try different magnetic cases if you use one (c) some report that ts file fixes fix these too.
Mine still have this issue. I use it by holding it. Have to try the fixes above sometime.
3. Touch is too sensitive - I believe that is what OP suggests a fix. Sometime when i was scrolling through emails, suddenly a click registers and it goes inside an email. I will try this and report.
Even if one of the above fixes work, after some time if you see problems again, do a reboot and it will be back working normal again. I am still not convinced if it is just a software issue or a hardware issue or both.
This seems to have helped with the 'jumpy' touch issues I've been having. It could also be because I just rebooted for the first time in over a month.
I set mine to 3.0, for me its a lot better than 2.5
Can you (or someone) please post a direct link to the main thread (or others) - I am having a little trouble locating. Thanks. By that I mean main thread mentioned in 2nd post regarding T10 etc
This seems to be it:
http://forum.xda-developers.com/showthread.php?t=2428133
Nexus 7 unresponsive screen or reaction without touching
Started having trouble with my Nexus 7 2013 not responding to touches or sometimes just entering characters not touched when doing keyboard entry. Thought it might be sensitivity issue, but checked one of the posts on line here and found that mine was actually set more sensitive than the suggested amount. Thought it might be a software issue as it really started getting bad after update to Version 5.0.2. I found that it seemed to be worse after notices that some of the apps had updated. My solution albeit imperfect was to start deleting apps until I found the problem. Not sure which it is, but it appears to be some of the in built apps that come from Google. I forced stop on several of these like play movies and books and did the uninstall procedure. Like magic, my Nexus started responding like if was just out of the box. Unfortunately, Google has these set so that they evidently run automatically when the tablet is turned on and update by themselves (which seems to have the effect of turning them back on as well). In any case, when I start getting sensitivity issues like it not responding to areas of the screen or not swiping, I go to apps and go through the list forcing a stop on all I don't use (especially You Tube) then uninstalling (only option seems to be going back to factory versions). Nexus then works OK until the next "automatic" update, I actually use (i.e. enable) one of the apps or turn the Nexux completely off and reboot. At least it is less frustrating doing this every week or so than having a non-responsive tablet. If anyone knows how to "permanently" kill these Google apps or at least turn off the auto-start and auto-update functions, I would be pleased to hear it. By the way, the best I can tell, stopping these does not seem prevent You Tube videos playing or any of the other tablet functions from working, but maybe utilizing them from a browser or whatever is what triggers them coming to life again. I'm a novice so I don't know.

Categories

Resources