My phone is acting up a lot lately, I can't figure out what exactly is the cause to it.
I've just factory reseted the phone, still the same issue persists. Whenever I turn my wifi on, from anywhere, it turns itself back off in a minute or two. Never actually connects to any network. If I restart it, it might work fine for few hours.
On top of that, it's doing a random restarts on it own. Right before I did a factory reset it restarted on its own continuesly atleast 5 times.
Very frustrating. I can't pin point which app/system/file is doing that. I even wiped off my sdcard to pinpoint the issue.
Anyone else have the same issue? Any solution to this?
It's not a wifi sleep policy issue, I've checked.
Sounds like you have tried some really great steps to discover what is the root cause of these issues. If the wifi issue indeed happens everywhere then we know it is not the router you are connecting to. I would look at the steps in this article and see if there are any steps you may not have tried yet. http://support.t-mobile.com/docs/DOC-2726
My TMobile G2 turns WIFI back off in a few seconds, and never connect even after factory reset. I have flashed the radio to the 22.214.171.124 version, still no help.
If you are flashing radios and so forth, I wonder if you have rooted your phone. If so, then you need to stick to xda.com.
I think there needs to be a way to determine if some people who come on this site with weird problems are the result of them rooting their phone or trying to root their phone and messing the up phone. Because some of the problems that some people are having, I have never had with the G2.
You have to be rooted to be able get the superuser access required to flash new components.
Rooting itself is simply the acquisition of superuser rights and doesn't physically transform the device at all.
It's what you do having obtained those rights that can make the difference for good or ill.
The first thing I learned, and advise others, abiut modifying phones is how to revert to a stock configuration. Essential reading.
No, I was on stock Froyo before rooting, and the stock Froyo had this problem too.
I rooted because of this problem.
I'm not sure what you are saying "no" to. I was replying to another poster in the thread.
Everyone is on stock something or other before rooting for the first time. Rooting is just the means to an end.
My point is, if your device is screwed up after modifications have been applied, you have an option to flash back to stock and start over with a different custom configuration that is is perhaps more solid. I don't mean that you give up on trying to find an optimized custom configuration.
My device is screwed before modification was applied. Flashing back to Froyo or installing the oct OTA update on stock Froyo does not help.
Hey, it's your choice. Im simply saying that if you have been flashing sub-sets of the system, it might be wise to get back to a stock confuguration and then apply an optimized custom package from one of the dev community which contains a balanced mix of ROM/kernel/radio.
If you want to get the device replaced, you'll need to be able to get it back to stock as well.
Yes the radio firmware released by Tmobile may have issues if I run a customized ROM, but I am talking about issue occored on TMobile's stock ROM before doing any customization. I flashed the radio because of the problem. It is not like I want to flash if the stock ROM was working.
I think we are completely at crossed purposes here. I'm not saying you didn't have problems before rooting, and I'm not saying you should permanently revert to stock. All I'm saying is that the best platform to start over from might be the stock build, then select a complete custom ROM package and install that.
Thanks. But switching a ROM does not replace the radio. Already tried a few customized ROMs, did not help. The behavior is the same. I think the problem is in the radio firmware and/or the arena
That's why I said install a ROM PACKAGE which will include a matched kernel and RADIO.
It may well be that the issue is in the hardware. But isn't that all the more reason to get back to stock so you can get a warranty replacement?
ROM packages virtually never include the radio. When I flashed CM7, I went out to XDA and got the latest T-Mobile Radio, along with the Radio Interface Libraries (RILs) to match it.
Back to the OP, my guess is you have a bad phone. Un-root, and see if you can get it replaced.
Different experiences, I guess, several that I have used for the Samsung Vibrant did include the radio.
Even if the radio isn't directly included in the installation, there are recomended modems to match the ROM which can be easily accessed from within the source area for the ROM itself.
This whole strand of the discussion has been about reverting back to a point where the OP can either try a another route with a cutomization or get the device replaced.
Since he has a non-standard configuration, he won't be guaranteed to get a warranty replacement simply by un-rooting his device. He needs to re-apply the stock build to be sure of passing the warranty inspection. If it fails, he will be billed for the replacement device.
Retrieving data ...