What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

WiFi issues with ROOTED Froyo. Droid 1

You are leaving out some very key pieces of information to troubleshoot this problem.

1) 2.2 ROM being used include maker and version. (STOCK ROM, 2.2 with root made by Pete FRG01B by Pete)
2) 2.2 Kernel being used include maker, slots, min/max freq and voltage. (2.6.62.9-g103d848android-build@apa26 #1)
3) 2.1 ROM being used include maker and version. (STOCK ROM, 2.1 with root. 2.1-update1)
4) 2.1 Kernel being used include maker, slots, min/max freq and voltage (2.6.29-omap1-g7fa8788android-build@apa26 #1 Build ESE81) .


see above in RED

I will assume those are both standard voltage kernels for the sake of this discussion.

With this information, your testing clearly shows there is a fault in the hardware.

My recommendation is simple. Install the official 2.2 ROM and take the phone into Verizon for repair. Because if you were not rooted, the results would be the same and that would be your only recourse.

If you don't believe you phone is at fault, then find the nearest open WiFi and rerun the tests. If you continue to get these issues with other makes of Wireless routers, then you have eliminated all possible variables and you are back to your phone.

Yea I'm running Stock voltages and CPU speeds. I've tried NON rooted 2.1 also. I had the SAME issue with WiFi not reporting. I called VZW a while back and told them of this issue. They said I'd need to get a replacement. I plan on doing that. I wanted to rule the OS out first. See I OC'ed my CPU a while back and apps started to FC almost instantally. Then the screen went blank. I pulled the battery right away but it must have damaged the WiFi chip. WiFi seems to be working ok other than the reporting of signal. Which is strange.
 
You are leaving out some very key pieces of information to troubleshoot this problem.

1) 2.2 ROM being used include maker and version.
2) 2.2 Kernel being used include maker, slots, min/max freq and voltage.
3) 2.1 ROM being used include maker and version.
4) 2.1 Kernel being used include maker, slots, min/max freq and voltage.

For me, I've tested it with stock 2.1, stock 2.1 rooted (with and without kernel), Chevy's last 2.1 ROM, chevy's kernels. On 2.2, rooted 2.2 stock (with p3's kernel that came with the leaks and chevy's), Sapphire .8.4 and 1.0 (sapphire kernels and chevy's kernels), stock 2.2 OTA file, non-root, no kernel obviously (the latest one anyway).

I have to make the same recommendation for you. The fact that you listed 2.2 OTA and you have a problem also show you should go to Verizon and ask for a repair. Or you can also try trouble shooting with other WiFi routers if you don't feel the phone is at fault.
 
What could have caused this? I OC'ed my CPU but if the other guy on here didn't do that what screwed the WiFi chip up?

I just hate getting a FRU. I have one now. But it took 2 trys to get a good one that didn't have a lot of flaws.
 
see above in RED

I will assume those are both standard voltage kernels for the sake of this discussion.

With this information, your testing clearly shows there is a fault in the hardware.

My recommendation is simple. Install the official 2.2 ROM and take the phone into Verizon for repair. Because if you were not rooted, the results would be the same and that would be your only recourse.

If you don't believe you phone is at fault, then find the nearest open WiFi and rerun the tests. If you continue to get these issues with other makes of Wireless routers, then you have eliminated all possible variables and you are back to your phone.

Yea I'm running Stock voltages and CPU speeds. I've tried NON rooted 2.1 also. I had the SAME issue with WiFi not reporting. I called VZW a while back and told them of this issue. They said I'd need to get a replacement. I plan on doing that. I wanted to rule the OS out first. See I OC'ed my CPU a while back and apps started to FC almost instantally. Then the screen went blank. I pulled the battery right away but it must have damaged the WiFi chip. WiFi seems to be working ok other than the reporting of signal. Which is strange.

xmguy - i thought you said that 2.1 worked fine?
 
You are leaving out some very key pieces of information to troubleshoot this problem.

1) 2.2 ROM being used include maker and version.
2) 2.2 Kernel being used include maker, slots, min/max freq and voltage.
3) 2.1 ROM being used include maker and version.
4) 2.1 Kernel being used include maker, slots, min/max freq and voltage.

For me, I've tested it with stock 2.1, stock 2.1 rooted (with and without kernel), Chevy's last 2.1 ROM, chevy's kernels. On 2.2, rooted 2.2 stock (with p3's kernel that came with the leaks and chevy's), Sapphire .8.4 and 1.0 (sapphire kernels and chevy's kernels), stock 2.2 OTA file, non-root, no kernel obviously (the latest one anyway).

I have to make the same recommendation for you. The fact that you listed 2.2 OTA and you have a problem also show you should go to Verizon and ask for a repair. Or you can also try trouble shooting with other WiFi routers if you don't feel the phone is at fault.

I would think the same thing, but 2.1 works fine - stock/rom/anything 2.1.
 
What could have caused this? I OC'ed my CPU but if the other guy on here didn't do that what screwed the WiFi chip up?

I just hate getting a FRU. I have one now. But it took 2 trys to get a good one that didn't have a lot of flaws.

I have oc'd, but even still, if I go back to 2.1 anything, mine works fine.
 
I will assume those are both standard voltage kernels for the sake of this discussion.

With this information, your testing clearly shows there is a fault in the hardware.

My recommendation is simple. Install the official 2.2 ROM and take the phone into Verizon for repair. Because if you were not rooted, the results would be the same and that would be your only recourse.

If you don't believe you phone is at fault, then find the nearest open WiFi and rerun the tests. If you continue to get these issues with other makes of Wireless routers, then you have eliminated all possible variables and you are back to your phone.

Yea I'm running Stock voltages and CPU speeds. I've tried NON rooted 2.1 also. I had the SAME issue with WiFi not reporting. I called VZW a while back and told them of this issue. They said I'd need to get a replacement. I plan on doing that. I wanted to rule the OS out first. See I OC'ed my CPU a while back and apps started to FC almost instantally. Then the screen went blank. I pulled the battery right away but it must have damaged the WiFi chip. WiFi seems to be working ok other than the reporting of signal. Which is strange.

xmguy - i thought you said that 2.1 worked fine?

Both had issues. But 2.1 was MORE stable. See video 1 that shows what happens with my WiFI. Video 2 shows Froyo WiFi status.

I want to try and fully UNROOT the entire phone. I've done it before. Go to 2.0.1 upgrade to 2.1 then to 2.2 via OTA. That would rid the bootloader and the root/custom rom thingy.
 
What could have caused this? I OC'ed my CPU but if the other guy on here didn't do that what screwed the WiFi chip up?

I just hate getting a FRU. I have one now. But it took 2 trys to get a good one that didn't have a lot of flaws.

I have oc'd, but even still, if I go back to 2.1 anything, mine works fine.

@ jntdroid

If you watch my first video. Does your 2.1 do this? If I launch WiFi on the far end of my house and WiFi levels are at 1 bar. Then come to the spot where my router is it will stay at 1 bar until I either go to the WiFi settings page then it will update or use a WiFi scanning app it will then show full signal. It works fine then.
I even tried a WiFi meter widget on the home screen. It didn't help. I also noticed a flickering effect on the WiFi meter on the status bar. If I say had 3 of 4 bars the top 4th bar would flash every 5 seconds.
 
My plans as of now get another FRU Droid. I have 2 Nandroid backups. of 2.1 and 2.2 both set to run as they were backed up. If HW IS the issue. I will install SPRecovery and then restore the Nandroid backup of 2.2 or 2.1 and see what occurs.
 
I didn't realize you were having problems with 2.1 as well - I missed that in the videos! I'll be curious as to your results once you completely wipe/unroot back to stock 2.0.1/2.1, as I just did the same to test out some tonight.
 
I didn't realize you were having problems with 2.1 as well - I missed that in the videos! I'll be curious as to your results once you completely wipe/unroot back to stock 2.0.1/2.1, as I just did the same to test out some tonight.


It's definitely HW. I flashed to official 2.2 (non rooted) and WiFi indicator is still not working right.

My phone's flash has had enough. I flashed SPRecovery back on. but forgot to downgrade to 2.0.1 after installing 2.2 OTA first and my OS was FC'ing. I then flashed it back to 2.0.1. Then installed the SPRecovery and it bricked it. If it wasn't for my Nandroid backup. I'd have to restore to factory state. I'm now back running 2.1 rooted, as I have been.

I'm getting this exchanged ASAP.
 
What could have caused this? I OC'ed my CPU but if the other guy on here didn't do that what screwed the WiFi chip up?

I just hate getting a FRU. I have one now. But it took 2 trys to get a good one that didn't have a lot of flaws.

I have oc'd, but even still, if I go back to 2.1 anything, mine works fine.
It's possible something was changed in the 2.2 code that somehow has an incompatibility with your WiFi chip. That's far from the realm of impossibility, of course, so it's possible one of the more completely-tweaked ROMs would have something a little different? I think Cyanogen is working on a new driver for the WiFi so the WiFi tethering will be infrastructure format rather than ad-hoc, leastways I remember him tweeting someone that the hardware supported infrastructure but that it was a driver issue preventing it from working at that point.
 
I am having the same issue with the indicator.

I just manually updated to 2.2 (no root - Full version)

Never Rooted (hence never OC'd)

The Indicator has no bars. When I go into the WIFI Settings, the signal bar of the Network I'm connected to jumps up and down, but the Upper Indicator does not reflect this.

I have not done any packet tests, but I did think that when in my usual "sitting on my a$$ spot" it was choppy

I have tried to change the Radio frequency (channel) on the Router - No Good

EDIT**** My Router shows a constant STRONG Signal when the phone is right by the router (approx -47 DB)
 
I am having the same issue with the indicator.

I just manually updated to 2.2 (no root - Full version)

Never Rooted (hence never OC'd)

The Indicator has no bars. When I go into the WIFI Settings, the signal bar of the Network I'm connected to jumps up and down, but the Upper Indicator does not reflect this.

I have not done any packet tests, but I did think that when in my usual "sitting on my a$$ spot" it was choppy

I have tried to change the Radio frequency (channel) on the Router - No Good

EDIT**** My Router shows a constant STRONG Signal when the phone is right by the router (approx -47 DB)

Funny that you just posted this... I'm working on getting some screenshots right now to show what's going on with mine.
 
I am having the same issue with the indicator.

I just manually updated to 2.2 (no root - Full version)

Never Rooted (hence never OC'd)

The Indicator has no bars. When I go into the WIFI Settings, the signal bar of the Network I'm connected to jumps up and down, but the Upper Indicator does not reflect this.

I have not done any packet tests, but I did think that when in my usual "sitting on my a$$ spot" it was choppy

I have tried to change the Radio frequency (channel) on the Router - No Good

EDIT**** My Router shows a constant STRONG Signal when the phone is right by the router (approx -47 DB)
Are you having connection issues or just a buggy WiFi indicator bar? If it was the latter I'd deal with it, see if it was corrected in the next update rumored to hit in the next couple of weeks, and if it wasn't I'd ask Verizon about it.
 
Back
Top