since installing froyo and new radio,ive encountered something out of the ordinary.im now picking up on the att signal quite often.of course i cant use it since tmobile and att severed agreement.i didnt encounter this on eclair on my nexus or cupcake and donut on my mt3g.anyone else noticed this?
Related
I had read somewhere that the unofficial updates fixed the 3g issue for someone....
Any truth to this?
I never had any problems with my G1 phone with cyanogen mod and my 3g/edge connection
however, this damn nexus one cant hold a signal for ****.
If you have root then I say try one of the different radios to see which one works best for you.
I've tried all the radios and several ROMs and do not have near as good a connection like I did with my G1. Probably doesn't help I am usually on the edge of 3G coverage when I am at work and notice this. But the G1 was way better than any combination I have tried
with the ERE36B radio my Nexus gets WAY better reception than my G1 ever did.. and data speeds as well even with the garbage ERE27 radio, my buddy's (my old) G1 cant touch it in terms of actual data speed
hi guys, ive flashed a couple of different froyo roms and decided to stick to FroyoRedux 1.5
reason for all this reflashing.......when using 3G networks i randomly get no signal for about 2 minutes and then its back again. im not too sure why this is happening and wondering if anyone else encountered the same problem?
there seems to be no problem with 2G networks but being on 2G is lame and makes mobile internet kinda pointless.
BTW problem still persists in FroyoRedux 1.5
phone specs are in the sig (if you wanna know what im using)
cheers!
Had this issue on my kaiser running froyo also, went to an older radio which fixed it, and amazingly enough, the same happened on my G1, and the same step fixed it.
Using radio 2.22.23.02 I had regular 'no signal' issues, going back to 2.22.19.26I solved it for me, I still get signal loss on occasion, but only in known very low signal areas,
hmmm interesting, im gunna give this a try and see what the outcome is.
did u just flash the old radio file over your current one or did you use a specific procedure?
I'm not sure if this is the same as the well known "Nexus One 3G problem". I'm running CyanogenMod 6. I have been having occasional trouble on my home carrier (WIND Mobile Canada) where every once in a while, even though the 3G or H icon appears, I can't access anything and when I try the ping test under Testing/Phone information it fails.
The only way I'm able to get the Internet back is to disable mobile data (via widget) and re-enable. Then it lasts again for a while.
I'm currently on vacation in the US and using a T-Mobile SIM. It seems this problem is even worse on their network. Sometimes I only get maybe 2-5 minutes of a 3G connection before it freezes out like this. I've been leaving it on EDGE just to keep it stable, but this is obviously not an ideal solution.
About two weeks ago I started trying nightly builds of CM6 as I was interested in the FM Radio, and I have noticed this issue much more since then. It might be related, but it could also be a coincidence, and I don't want to start messing around with multiple ROM flashes while on vacation if that's not the problem in the first place. Any ideas on what to do?
Thanks
Charles
its a bug with 2.2.1,my nexus does this too. it will get stuck with the data up arrow lit up when the data stops working,turning data off and back on fixes it. there is even a post in the google bug tracker about it. I know for sure it happens in both FRG83 and FRF91,but I'm not sure exactly when it started. 2.1 roms for the N1 don't do it,and my g1 doesnt on 1.0-2.1,but on froyo roms it does exactly the same thing as the nexus.
I hope someone (google or a dev) can fix this,because its really annoying. my g1 is back to donut because its faster,and I'm considering going back to a 2.1 rom on the N1. I've confirmed the issue on ChromaticDream (g1),CM Nightlies (I've tried 198,200,201,202,203,220),CM6.0.0,Enomther's TheOfficialNexus (10/11/10),and a few others.
I thought I was the only one who noticed this bug. Does it occur in the stock (non-rooted) versions of 2.2.1 as well?
Just an update, although I do periodically experience this on my home provider (WIND Mobile Canada), it turns out that T-Mobile is having 3G issues in Portland this exact week and everyone's experiencing it. So the fact that 3G is nearly unusable on my trip is TMo's fault and not Android's.
UPDATE: I downgraded my radio to the official froyo radio (4.0-something lol) and my timeout problems are no more so far....
I have the same problem but with since I'm using nightlies 215 the problem is gone (i'm using 508 radio)
but lately I'm using nightlies 221 and 223 and the problem is back
I settled on 204 for vacation because I didn't want to fiddle with the ROM 10 hours away from my desktop comp! Now that I'm home, keep this thread updated with which builds seem to have a stable 3G connection.
I just flashed 225 with 512 radio and I can say this build is stable, no more intermittent connection lost. 225 nightlies is fast as well
Good to know. I'm on the 5.08 radio; is there a significant difference with 5.12?
Need help hoping someone can point me the right direction or has had this problem before.
On random occasions my connections to the T-Mobile network will stop. The way that I know it's stopped is I'll look at the 3G or H icons in the drop bar and the up arrow will be blinking as if it's try to connect but nothing will happen. During this time, no calls will come in or out, and data will not work. To get out of this, I either have to reboot or switch from 3G to EDGE (also happens while on EDGE too) or just wait it out, EVENTUALLY, the connections will be restored and the up and down arrows will light up showing traffic is flowing again. I know it's not coverage since more often than not I have full bars or at least 2 bars.
I'm thinking it's not the radio firmware, since I'm running modded ROMs (currently running CM6.1 RC1) and I've upgraded the radio successfully each time. The radio I'm currently running is 32.41.00.32U_5.08.00.04
Let me know if anyone has any ideas on how to troubleshoot this or has a clue on what I should do.
thanks
5.08 and 5.12 radio versions came from Korean updates, so would you like to give 4.06 a try to see if it solves the problem? if still doesn't, try 5.12 see if it works.
Radio image is not really tied with Rom, Froyo requires 4.06 or later radios. Since radio software handles all data communication.. so it is still possible that radio software caused the problem (i think )
Ive had this problem since I first got the N1, was happening even while running stock 2.1 so I dont think it has to do with the OS. I had written it off thinking it was an issue with TMO and their network. But at this point doesnt seem like that.
I've ran 4.06 radio in the past and still the problem presented itself so Im pretty confident that rolling back to 4.06 isnt going to fix it. I've just recently upgraded to the 5.12 radio so we'll see if that ends up working.
Other than that any other ideas?
I'm currently waiting for my replacement that Bell is sending me for my SGS phone. I am wondering 2 questions,
1-Is it safe to upgrade to Froyo if my cell phone comes with Eclair?
2-Do the new phones have the same GPS issues that the original one had?
Not sure if this makes any difference on what i will receive as a replacement but i live in Toronto.
I ended up buying the phone on launch day, never managed to get the gps to work and froyo blew out my internal sd a day after upgrade.
Thanks.
1-Is it safe to upgrade to Froyo if my cell phone comes with Eclair?
Safer its an official upgrade via Kies .
2-Do the new phones have the same GPS issues that the original one had
Original did not have a GPS problem its more like a few batches had a problem possibly still have a problem .
jje
Had the same issue myself. They sent back a reflashed (and replaced PCB) device. The GPS still sucks. This is after following all recommendations (except opening the case and adjusting the contacts). I have a replacement phone coming from Bell in a week or so.
I'll let you know what I get. The problem may be the contacts and if you search around you may find notes on this. I think AllGamer and others had some ideas on this.
Cheers,
Samsung I9000M Froyo Bell ROM