Hi, noob to xda forums and flashing ROMS in general.
Having trouble with Wifi disconnects with two identical phones, which were working well with stock 4.0.2 roms from t-mobile.
I have tried cm-10.1-20130402-UNOFFICIAL-ruby and cm-10.1-20130405-UNOFFICIAL-ruby.zip on my and my son's Amaze devices.
In both of them I have Wifi issues. It appears normal when it connects, for a few seconds, perhaps a minute or two, however, it then very often silently disconnects, but still shows it's connected, albeit often with a little grey mark that is barely noticeable.
I am not sure what that means. .. see the attached image in case it helps.
In any case, I do not see many people mentioning this problem with these ROMs.
I wonder if I did not flash properly. What I did was put: the zip in the external sd card, format everything and reset to factory settings with 4ext, and then install the zip and then gapps (the first time) and the rest of the times only just clear cache+davlik and install the zip from sdcard.
Seeking possible pointers to get this fixed up!
Thanks!
Something I had an issue with which was totally unrelated to the ROM was an issue with my WiFi router. For some reason when I switch from ICS > JB or vice versa, the router had an issue with the storage of the mac address. I had to clear the mac address from the router and restart wifi on the phone to get a new ip addy from the router.
Not saying this is your issue, but worth a look since other are not having issues with the ROM. Good luck.
I am having the exact same problem ihama and I also have two Amaze phones. At first I thought I messed something up with the first phone when I did the S-Off because that was when I noticed the problem. I flashed a ton of different roms to my phone to try and fix the problem and none of them helped. I also flashed the stock kernel many times and that didn't fix it either. I got my girlfriend's new phone a week later and I decided not to S-Off hers or change anything for the first few days. It never dropped WiFi. As soon as I unlocked the bootloader it started dropping it like crazy with the stock rom. I haven't tried vinniej's solution yet but I am definitely going to soon because nothing else worked. I spent hours looking for information on this problem and this is the first post I've seen that mentioned the problem I'm having.
One thing to mention, I flashed Viper Amaze on my phone yesterday and it has not dropped Wifi yet. I'm not sure if fixed it or not but I am going to wait and see with mine. I will try vinniej's way with my girlfriend's phone when I get a chance.
S_O_B said:
I am having the exact same problem ihama and I also have two Amaze phones. At first I thought I messed something up with the first phone when I did the S-Off because that was when I noticed the problem. I flashed a ton of different roms to my phone to try and fix the problem and none of them helped. I also flashed the stock kernel many times and that didn't fix it either. I got my girlfriend's new phone a week later and I decided not to S-Off hers or change anything for the first few days. It never dropped WiFi. As soon as I unlocked the bootloader it started dropping it like crazy with the stock rom. I haven't tried vinniej's solution yet but I am definitely going to soon because nothing else worked. I spent hours looking for information on this problem and this is the first post I've seen that mentioned the problem I'm having.
One thing to mention, I flashed Viper Amaze on my phone yesterday and it has not dropped Wifi yet. I'm not sure if fixed it or not but I am going to wait and see with mine. I will try vinniej's way with my girlfriend's phone when I get a chance.
Click to expand...
Click to collapse
This worked for me.
Have you checked the Mac address on each phone to verify that they are different?
Sent from my HTC Amaze 4G using Tapatalk 2
bunyan69 said:
Have you checked the Mac address on each phone to verify that they are different?
Click to expand...
Click to collapse
Yes, the MACs are different (as they should -- the MACs are probably on the hardware device, not on the driver or even the OS).
Also, the previous link,
Looks like your kernel isn't flashing properly if you are s-on then use 4ext recovery with smart flash enabled you will have a higher chance of having a working ROM using that method.
Click to expand...
Click to collapse
Did not do much for me, because I was already using smart flash (also, my two phones have s-on).
I may have to enable ssh and take a look at the logs to see if something comes up.
No luck with clearing the mac address. I got a new IP and it dropped wifi a few minutes later. I switched my router out with another one just to see if that was the problem.
The phone with Viper Amaze Rom still has not dropped wifi once.
Boy, is my face red.
@bunyan69, you were correct. In fact the two MACs are identical in the two phones. Somehow the MAC in the hardware is not picked up, or is being overridden.
I searched on how to reset the WiFi MAC permanently, however, I only find temporary solutions that vanish after a reboot (ifconfig) or some fastboot oem command that does not exist in the HTC Amaze devices I have (the emapiWlanMac command).
@S_O_B How did you change your MAC? From your message, it would seem you "cleared" you MAC ... which is ambiguous to me ...
EDIT: the MAC I get is apparently very common, so one may guess it's probably overridden somewhere in the system code: 00:d2:8b:43:9f:fd
This is the solution for permanently changing the MAC of the WiFi in the Amaze (ruby) phone:
su -
mount -o remount -o rw /system
cd /system/etc/firmware/ti-connectivity
calibrator set nvs_mac wl1271-nvs.bin 00:d2:8b:XX:YY:ZZ
cd /
mount -o remount -o ro /system
change the XX YY ZZ to any other (hex) numbers as you please.
(The assumption is that you are connected with adb shell)
Related
After having the phone nearly a week I'm still having problems with the WiFi.
Fine for day one, then noticed when I took it out of my pocket a day later or so that WiFi stated "Error" and couldn't initialize, This happens continously now and sporadically at random intervals (Reboot does not appear to fix it but keep trying does seem to)
Anyone know of this or how to fix it? Or is it just a dodgy handset? (I've still got a couple weeks to swap it over luckily)
I've searched the forums and found something about the same issue after a flashed kernel but I am COMPLETE STOCK, EXCEPT For Root and S-OFF and even restoring to a compeltely basic almost "Out of the box" image does not appear to fix it.
I flashed my Radio today to see if it helps but it doesn't look like it currently.
Any help appreciated (Hope this is in the right forum.
daniluvsuall said:
After having the phone nearly a week I'm still having problems with the WiFi.
Fine for day one, then noticed when I took it out of my pocket a day later or so that WiFi stated "Error" and couldn't initialize, This happens continously now and sporadically at random intervals (Reboot does not appear to fix it but keep trying does seem to)
Anyone know of this or how to fix it? Or is it just a dodgy handset? (I've still got a couple weeks to swap it over luckily)
I've searched the forums and found something about the same issue after a flashed kernel but I am COMPLETE STOCK, EXCEPT For Root and S-OFF and even restoring to a compeltely basic almost "Out of the box" image does not appear to fix it.
I flashed my Radio today to see if it helps but it doesn't look like it currently.
Any help appreciated (Hope this is in the right forum.
Click to expand...
Click to collapse
this error is generally caused by a mismatch between the loaded kernel and the loaded wifi module.
the loaded wifi module must be compiled with and match the loaded kernel. flashing a kernel and then loading a custom rom (which loads its own modules overwriting the modules from the kernel) is generally the way this error occurs.
how you rooted the device could lead to the above wifi error i.e. custom ROM with root, which could result in the above situation, or just flashing superuser.apk which wouldn't result in the above situation.
the part of your comments which stands out to me is that the issue appears to be intermittent. i think the best suggestion and approach, at this point, would be to load a completely stock system.
if the wifi issue still persists, even though it is intermittent, it should be hardware related as my device has never had this type of wifi issue and i'm on a stock ROM. if you're on stock and still have this issue, i would def take it back as it would appear to be hardware related. hopefully the wifi issue will occur while you're at the store making it easy to demonstrate the issue.
hope that helps, good luck!
Hi,
Sometime today I lost my phone signal on my SG2. I'm not sure exactly at what moment as I first noticed that I had a couple of bars but no 3G when I tried to browse the web. So I restarted the phone but to no avail. Since then I've lost all bars and can't make any calls either.
The only thing I have done today "out of the ordinary" was to connect to the phone using Wifi File Explorer to transfer a file, which I tried to connect to without being on a wifi network by first trying the "Wifi Direct settings" in Settings, which didn't work, and then by tethering by Wifi which worked. Maybe some setting got stuck in the process, but I'm not sure since never checked if it worked right before and after.
If anyone has any idea what could be wrong please let me know, as I am literally without a phone!
I recommend downloading http://www.androidzoom.com/android_applications/communication/no-signal-alert-pro_fyyo.html this will definitely be of benefit to you if your suffering from signal problems, it has been of good use to me.
Check your IMEI is the correct one for your phone .If not restore your backed up EFS folder .
Or try backup data and factory reset as a first step.
jje
Thanks for the quick replies!
The IMEI does not correspond to the one I have written down, though I'm not 100% I what have on my note is the latest IMEI; but how could that change though by itself, if my note is correct??
Also, I just saw something very strange: I turned on my phone and had full bars (no 3G though), and right in front of my eyes all bars dropped, one by one, during the course of 5-6 seconds. Something is VERY off...
Regarding factory reset: my phone is rooted (thanks to XDA!) and I have Tit.backup: can I will my phone still be rooted if I do a factory reset?
Something went probably wrong when rooting it (not neccesarily any errors) and effed up tge EFS folder.
Try to flash back to stock ROM, it might work to restore your.folder.
Sent from my GT-I9100 using xda premium
UPDATE
bruflot said:
Something went probably wrong when rooting it (not neccesarily any errors) and effed up tge EFS folder.
Try to flash back to stock ROM, it might work to restore your.folder.
Click to expand...
Click to collapse
I should have been more clear on that, but I rooted the phone about a month ago and it has worked flawlessly since then, so it couldn't be that.
Anyway, I looked around a little and found this post:
http://androidforums.com/samsung-ga...connectivity-but-no-idea-why.html#post2722784
He seemed to have had the exact same problem that happened to me, so I decided to wait, and sure enough the connection reestablished itself about an hour ago and while I was watching for it, with the signal slowly creeping back up during a couple of minutes, and several hours after I lost it. Very odd.
This surely has to be an Android bug but that only shows up under certain and rare conditions.
To be sure I made a speed test and got 4.84 Mbps/up, 1.19 down, which I guess is fine; I never did one prior to this so I have nothing to compare to.
Again, appreciate the advice!
EDIT: For posterity, I should add that during these hours, even when I briefly apparently had a (non-3G) signal, I had a notification during all this time saying that I could only make emergency call.
I'm having the same issue. No Bars at all most of the time and when I have some, it never connects to 3G, G at most, and can't load any thing at all.
Very frustrating. I have been using Lite'ning rom 6.1 for a few months and had no problems at all until about a week ago.
I flashed back to a stock rom and still having the same issue.
I've also seen the bars drop down one by one in a 5 second window, bizarre!
Anyone find a fix for this? Or could the phone be faulty?
malicedix said:
I'm having the same issue. No Bars at all most of the time and when I have some, it never connects to 3G, G at most, and can't load any thing at all.
Very frustrating. I have been using Lite'ning rom 6.1 for a few months and had no problems at all until about a week ago.
I flashed back to a stock rom and still having the same issue.
I've also seen the bars drop down one by one in a 5 second window, bizarre!
Anyone find a fix for this? Or could the phone be faulty?
Click to expand...
Click to collapse
I was on Lite'ning about 3 weeks ago and actually completely lost signal several times. Reboots and hard resets solved the problem temporarily. I then flashed Batista FH 2.4 with ICS and things were great. I'm now on GingerMod. No issues.
I don't know how it could be kernel related though, especially if you are 100% stock again.
I got my phone back on Wednesday from the repair people that my insurers use after dropping it last month and shattering the screen inside (fortunately the phone itself still worked properly)
At the time the phone had been dropped, I was having problems with it in that the phone couldn't get a phone signal at all and I was going to fix the problem myself. The repair people knew that it had been jailbroken and I explained that I would fix the problem with the lack of signal myself.
Now, I have a new problem in that every time I get a WiFi signal, it keeps getting disconnected within seconds and I've noticed that the repair people seem to have reactivated the infamous "Flight Mode" problem which seems to have somehow affected the inbuilt WiFi system in that every time the phone manages to detect a signal, whether it's at home or elsewhere, such as university, it loses the signal.
In any case, does anyone have any suggestions on how to fix the problem (I installed the latest VillainROM yesterday which is 3.0) including what modem to use and how to install it?
I would try some different modems and see if you find one that solves your problem. In the first few posts of the VillainRom thread is a link to the thread attachments. Included in there should be a few modems in zip format which you can flash through CWM. Also some of the posters (I think one is geko95gek??) have them in their signatures.
Hope this helps
borgmanjayce said:
I
Now, I have a new problem in that every time I get a WiFi signal, it keeps getting disconnected within seconds and I've noticed that the repair people set to have reactivated the infamous "Flight Mode" problem which seems to have somehow affected the inbuilt WiFi system in that every time the phone manages to detect a signal, whether it's at home or elsewhere, such as university, it loses the signal.
In any case, does anyone have any suggestions on how to fix the problem (I installed the latest VillainROM yesterday which is 3.0) including what modem to use and how to install it?
Click to expand...
Click to collapse
Hey there, not sure whether this is an ongoing issue, but the problem seems to be related to the embedded kernel from VR 3.0 (Nimphetamine 2.0.5) I was facing exactly the same problem. The only way to fix it was to flash a different kernel (siyah 2.2 in my case) .
I tried all available radios but nothing fixed it, maybe pulser has to take care of it in the next release, so flash another kernel and the problem will be solved, good luck!
Yep, as in above post. WiFi drivers are found in the kernel. Try Siyah, Speedmod etc.
Sent from my GT-I9100 using xda premium
This is a problems I'm having now with my GS2 and ICS(current is Bezke rom and Pure rom prior to that). Both of these ICS roms exhibit the same problem, it will see the wifi spot (its a Apple time machine and the connection uses WPA protection), it just won't connect to it.... EVER. The router is also just in the next room, so it has a perfect strong signal.
I did not have a problem before the ICS upgrade, it connected to the wifi spot just fine. As far as I'm concerned this is NOT a hardware problem but in software. I have had this issue with MANY MANY other high end android phones (I go through a lot), so much so that I got a 2nd router and run it open just for my android phones. I've tried utilities that "reset" the phone settings to help connect (not sure what that means, maybe like a DNS flush or ipconfig release/renew kind of deal...) but they never work.
Ive searched online for this issue and apparently thousands of others have had this same issue, but I don't remember seeing any talk of what exactly the problem is, or what to fix it (aside from flashing another rom). I would rather not be flashing every rom under the sun until I finally get it working, but I might just have to.
I really like this phone (I also have a 4S but don't use it because I like this Samsung so much) and plan on keeping this a while. Its a GT-I9100 BTW and not a carrier branded device, I have it on T-Mobile US.
I'm probably going to try the official Sammy rom next and see what happens. FWIW my last phone that had this problem was a Optimus 3D and it was running STOCK F/W and still would not connect. C'MON GOOGLE! WTF, This is a problem, can we PLEASE get it fixed
Can i take it that you have tried connecting with no security setup on the WiFi router first .
jje
Same problem here. Just upgraded two S2's at work. Went thru the process to 2.3.4 and 2.3.5 and once in 4.0.3 neither of them worked using our cisco wifi. Remember having the same problem on the old HTC Hero, but the Desire and the Sensation (both 2.3.5 and 4.0.3) works fine, as do iPhones and some tablets.
Problem must lie within the S2 since we have loads of computers and other phones connected. Have tried static settings instead of dhcp but the setup on the phone is quite limited.
Same here
9.5-9.7 Resurrection ICS based on XXLPH/XXLPJ won't connect to wpa2 secured University wifi. I've tried the official XXLPQ by Samsung and everything works like a charm.
It installed the XXLPQ so that is a no go. Tried connecting to a htc sensation hotspot and that worked. They just don't want to connect to the Cisco.
Encryption requres screen lock
I'm on campus Wi-Fi a lot. apparently "credential storage" used on these enterprise networks can only be used when you have a screen lock pin code set up
Does that help?
trying to find a way around it myself, I dont want to have to type a pin in every time I pick up my phone when I'm sitting in my apartment streaming pandora.
Sorry I forgot to reply back, but I ended up "cheating" and getting another router SPECIFICALLY for my android devices that dont like wifi security. I got a coupon in the mail for a free wifi router (N too!), its pretty low end but hey, it works.
Sure thats not really fixing the issue with the phone, but Ive gotten to the point of so much frustration, if I try any further to fix the phone and fail I'll either end up destroying the thing, turning to drugs or both.
Sadly, that last sentence was not hyperbole, Im serious. HOWEVER the phone is working, so all is well here
first i wanna thank you guys for this awesome forum
i have an AT&T aria phone that randomly reboots
LIBERTY PVT SHIP S-OFF
HBOOT-1.02.0000
MICROP-831b
TOUCH panel-stn21_03
radio-7.16.35.11
Nov 4 2010
the phone is rooted with CWM v2.5.0.1 istalled.
i flashed the original ATT rom 2.2 from HTC website and it didnt fix it
i flashed shipped att rom and it didnt fix.. also flashed rooted rom yet no luck
1-i tried to unlock the bootloader with HTCDEV.COM but it gives me error message
fastboot oem get_identifier_token
...INFO[err] command error
2-i tried to use the revolutianary website and no luck either
3-i tried to put the original img on the sd card LIBEIMG.zip and booted into bootloader but the phone didnt recognize the file at all.
i am a newbie in the android word but i can swear i did every thing by the book in these last 3 steps** at least as i could understand**
p.s: i dont know wut or who did this to this phone
This is sort of a long shot, but did you happen to install a 32GB SD card around the time the problem started happening?
If not, did you change ANYTHING else? new SIM card? new charger? etc.
nope i did not install 32 GB card..
i dont know exactly what happened to this phone.. i took it AS IS..
when i first got the phone it had the original at&t 2.2 stock S-off ... i was lucky to flash CWM using fastboot..
i think if i can install HBOOT again and turn S on this might solve the problem... or may be i need to do something to the partitions but as i told u im a newbie in here
i am sure it is a software problem due to the error message i get when i try to unlock the bootloader...
I tried everything: stock AT&T Froyo rom, returned to S-on, new sd card, new sim card. Also returned to HTC for "repair," but it still rebooted so I returned to HTC for another try.
BTW, I used the Unrevoked method to root/S-off the phone, and the S-on method listed in the development forum to take the phone back to stock. Both with no problem (several times). The S-on was a little trickie, had to load stock AT&T rom, then follow the S-on instructions, which includes loading the stock AT&T Froyo rom again.
I'll report the results of my 2nd HTC repair on the 2 Arias reboot problem thread.
Sent from my MB860 using XDA
i am trying to install HBOOT 1.03 but no luck.. i think if there is a way to reflash the hboot this would solve the problem
gdjy said:
i am trying to install HBOOT 1.03 but no luck.. i think if there is a way to reflash the hboot this would solve the problem
Click to expand...
Click to collapse
Don't try to do that. HBOOT 1.03 will not fix your problem, it'll only make it worse (not being able to easily S-OFF). You should avoid HTC's official bootloader unlocking method -- it's worse than Revolutionary.
thank u drumist...
i tried already but no luck.. it says device ID error..
i am so desperate in here.. is there anyway i can fix this aria??
To my surprise I had called HTC and found out that my phone was still under warranty. As I said above, the phone is now back at HTC for a 2nd try. I will let you know what they found as soon as I get the phone back -- it took about a week last time.
Drumist was very supportive in my effort to find the problem, and against his advice and out of desperation, I did restore the HBOOT, and, as he said above, it did not solve the problem. The phone was back to being completely stock -- ATT Froyo 2.2 and S-ON -- and it sill had random reboots --taking anywhere from 1 minute to almost an hour before rebooting. Which is really annoying when trying to troubleshoot. I even re-rooted and S-Off'd the phone using Revolutionary, and still had the problem. I then returned the phone to stock again prior to sending it to HTC for repair. Checked one more time... still random rebooting. As I am now using another phone -- Atrix 4G -- solving this has become more of a challenge.
The other thing that's amazing is that I have 2 ATT Arias with exactly the same problem!
I wonder if it is a location thing. You don't happen to reside in SE Pennsylvania do you?
the same thing has been happening to me. it just started happening recently.
about 10-20 times a day the phone just buzzes and goes straight to the white HTC turning on background.
it's very annoying.
charbo187 said:
the same thing has been happening to me. it just started happening recently.
about 10-20 times a day the phone just buzzes and goes straight to the white HTC turning on background.
it's very annoying.
Click to expand...
Click to collapse
I have to agree with you, it is really annoying. Luckily I dont use my phone very often. I dont think it is location based, as I'm in eastern Iowa.
Ok. Just got my Aria back from HTC after their 2nd attempt at at fixing the random reboot problem. It rebooted within 5 minutes of turning it on! And twice after that.
The only thing I did was put in the battery. No SD or SIM card, and I did not plug in a battery charger. I didn't even have a chance to connect to my wifi.
I will call HTC tomorrow and anticipate sending it back to HTC for a 3rd try.
I really thought they would send me a new phone after the 2nd attempt at fixing it. Although now I'm really curious about what could be causing this.
It's interesting that that there are more reports about this problem. I had rooted and installed multiple roms before restoring it to stock AT&T Froyo prior to returning it to HTC for repair. Has anyone had this random reboot problem on a phone that was never rooted?
Oh well. I will probably be sending it back to HTC tomorrow, and will keep you posted about the results.
Sent from my MB860 using XDA
I am having the same issues...luckily I now have the HTC One X, however I do still use the Aria as a dedicated GPS, which is frustrating having CONSTANT reboots.
This also only happened recently...I wonder what the issue could be...
Reboot saga
Just spoke to HTC about their failed 2nd attempt to repair my phone. They told me the repair records state that they replaced the "main board," which I assume is like the mother board.
If that is true, I would assume that would be like getting a new phone. If that doesn't fix it, I am truly baffled. The ONLY thing I did was put the old fully charged battery in the phone to test it -- without a SIM or SD card . Could the problem be related to the battery? Since I have another Aria (with its own battery) with the same problem, I doubt it.
Regardless, HTC is having me send it back for a 3rd try to fix it, and they sent me a prepaid shipping label this time.
They said if the 3rd repair attempt doesn't fix it, they would send it to a higher level repair facility for a 4th try! I can't complain about HTC's commitment to trying to repair my phone.
From the responses on this thread, this has become a recent problem. Mine started about a month ago. Any theories out there?
Thanks for sharing your experiences yar, however I'll be dealing with the reboots cause I cant go that long without my phone.
Another thought I had while driving yesterday, Do your guy's that reboots, happen usually after you press the lock button? I've noticed after I send a text message and I hit the lock button is mostly when it will restart. Anyone think it would be that button causing the problem or maybe the HTC Sense Lockscreen?
While I'm waiting for HTC to return my phone after their 3rd attempt to fix this problem I have been experimenting with my other Aria.
I booted into CWM and left it there for over an hour and the phone did not reboot. Does this helps isolate the problem?
Also, has anyone managed to stop a random reboot problem?
Sent from my MB860 using XDA
Just got my Aria back from HTC after their 3rd attempt, and it rebooted within 10 minutes. I even used a new battery, thinking that somehow that was causing the problem. No sim or sd card, and I did not even log onto wifi. They claim they replaced the "main board." Its hard to believe they actually tested it.
Probably beating a dead horse, but I will take HTC up on their offer to send it to the next level of service for a 4th try at fixing the problem. Can't believe it wouldn't be more cost effective to just send me a new phone at this point... but then there might not be any new Arias available.
Sent from my MB860 using XDA
try setting the Aria data comm to Edge only
I've been following this thread with interest since I have an Aria with AT&T "service" and have been experiencing the random reset problems described here. I have not rooted the phone and have the stock 2.2.2 release side loaded through HTC Sync. After several attempts to isolate the problem, I think I may have stumbled across something that works (so far, no reboots in the last 11 hours, but, that is not conclusive evidence yet). Try using the "hidden test feature" by entering *#*#4636#*#* on the dialer keypad. Then under the "Phone information" section select "GSM only". I understand that this forces the phone to use only the Edge data format.
I think there may be a problem with the Aria's firmware that communicates with the 3G network. I was able to use 3G successfully in the past year, but, something must have changed recently in the way AT&T configured this network or at least I suspect that a recent network change has caused these problems with our phones. You would think that AT&T and HTC would be aware of such a problem by now since I imagine many of us are affected. I'm leaving my phone on Edge until I see evidence that the problem has been resolved.
RWB Jr said:
I've been following this thread with interest since I have an Aria with AT&T "service" and have been experiencing the random reset problems described here. I have not rooted the phone and have the stock 2.2.2 release side loaded through HTC Sync. After several attempts to isolate the problem, I think I may have stumbled across something that works (so far, no reboots in the last 11 hours, but, that is not conclusive evidence yet). Try using the "hidden test feature" by entering *#*#4636#*#* on the dialer keypad. Then under the "Phone information" section select "GSM only". I understand that this forces the phone to use only the Edge data format.
I think there may be a problem with the Aria's firmware that communicates with the 3G network. I was able to use 3G successfully in the past year, but, something must have changed recently in the way AT&T configured this network or at least I suspect that a recent network change has caused these problems with our phones. You would think that AT&T and HTC would be aware of such a problem by now since I imagine many of us are affected. I'm leaving my phone on Edge until I see evidence that the problem has been resolved.
Click to expand...
Click to collapse
I will have to give this a try, as for HTC and ATT knowing, they probably don't care and I dont really blame them this is a 2 year old phone.