[Q] Which ROMs are safe for Bell I9000M (850mhz) users? - Galaxy S I9000 Q&A, Help & Troubleshooting

I'm just wondering if someone can list any ROMs or flashing methods/guides that work on Bell I9000M phones without losing the 850mhz band.
I'd really like to give Tayutama's SuperLite version a go (for example), but I need the 850mhz band; is it safe? If not is there something we can do to re-enable it without going back to a stock ROM?
I've looked around the forum and not seen any clear answer to this.
Input is appreciated!

I second this.. But im thinking ill be disappointed as ive read a few places that the bell galaxy s cant be flashed with the i9000 roms out there without minor to major issues

i believe if you flash only the pda and leave jh2 modem and jh2 csc. you can flash any of the newer roms 2.1 eclair.. but havent tried it myself.. my one exerience with jm7 when i didnt do this and only kept the csc i lost my 850 mhz.

lgkahn said:
i believe if you flash only the pda and leave jh2 modem and jh2 csc. you can flash any of the newer roms 2.1 eclair.. but havent tried it myself.. my one exerience with jm7 when i didnt do this and only kept the csc i lost my 850 mhz.
Click to expand...
Click to collapse
Does it have to be Eclair ROMs only?

I just spent the night trying various ones and got squat. I did find this post here (forum.xda-developers.com/showpost.php?p=8299301&postcount=18) but it seems to be older and references the JH2 files, and not necessarily a specific ROM.
If I find one that works, I'll post it here.
For now, I'm heading back down to 2.1 stock version (ugh).

http://lmgtfy.com/?q=site:+xda-developers.com+"i9000m"+froyo

I would also like to know as well... I am quite interested in trying Darky's Froyo rom
(Apparently it is safe, will probably give it a shot today at some point)

if you flash only the pda of a rom, and the jh2 modem/csc files, know that you may experience battery drain issues because they do not match. i flashed jpk with jh2 modem/csc for few days and the battery drain was insane. only fix was to flash the full jpk, then re-enable all the bands.

Would love to get an answer for this as well.
Phone crashed on first day from the store. Touchwiz issue had to wipe. So i dont see the down side to flashing when the stock can crash too.
And no gps which is such a letdown. Cant lock location ever.
Sent from my GT-I9000M using XDA App

Okay here are some straight facts - you can flash any of the new roms on a Bell SGS. You need the Bell version of the modem to maintain 850 - it works with 2.2 - it may or may not not be fully optimized for 2.2 but it works just as well as it does on 2.1. It just doesn't matter that much in the grans scheme of things.
All other so-called issues with battery drain, SD card, bricking, weird behavour, etc. are not caused by the ROMs either but rather the execution of underlying apps - usually optimization and timing related issues - if you have a problem it is most likely software related - i.e the app has not been optimized under FROYO.
Seriously, this is not rocket science. You cannot permanently brick your phone from FROYO - it is impossible.
If you want to successfully implement Froyo but are skeptical, pick a ROM, flash the Bell modem and then try it out for a week or two BEFORE dumping a bunch of new apps on it. Then decide if you want to keep it - which you will. Then start finding apps that are Froyo optimized and you will have no issues. Seriously.

rdenis said:
Okay here are someme straight facts - you can flash any of the new roms on a Bell SGS. You need the Bell version of the modem to maintain 850 - it works with 2.2 - it may or may not not be fully optimized for 2.2 but it works just as well as it does on 2.1. It just doesn't matter that much in the grans scheme of things.
All other so-called issues with battery drain, SD card, bricking, weird behavour, etc. are not caused by the ROMs either but rather the execution of underlying apps - usually optimization and timing related issues - if you have a problem it is most likely software related - i.e the app has not been optimized under FROYO.
Seriously, this is not rocket science. You cannot permanently brick your phone from FROYO - it is impossible.
If you want to successfully implement Froyo but are skeptical, pick a ROM, flash the Bell modem and then try it out for a week or two BEFORE dumping a bunch of new apps on it. Then decide if you want to keep it - which you will. Then start finding apps that are Froyo optimized and you will have no issues. Seriously.
Click to expand...
Click to collapse
I didn't flash a bell specific modem. I used the one that came packaged in Docs JPM froyo. Works perfect with no loss of any 850mhz 3G band.

Good job and clarification - as long as the modem supports 850 it does not need to be Bell.

First off for those that think you have WCDMA 850 working after a rom flash designed for another region, make sure you actually try and run only the WCDMA 850 band to see if you actually have it. If your not running on Bell and your network doesn't have WCDMA 850 available to you then you can't check and it won't matter. Any rom designed for a region that doesn't use WCDMA 850 will not give you WCDMA 850 and why should it.
Install whatever rom you want and simply flash your JH2 modem to get your WCDMA 850 back. After the modem flash make sure you put your phone into automatic mode and select all to refresh the modem band availability.
If your able to flash your modem AND your csc you might even get your product code back.... maybe.
For Bell users it would be nice to have a Froyo modem that will support WCDMA 1900 and 850. The 2.1 JH2 works fine though with Froyo.

MKVFTW said:
I didn't flash a bell specific modem. I used the one that came packaged in Docs JPM froyo. Works perfect with no loss of any 850mhz 3G band.
Click to expand...
Click to collapse
Are you sure that you have the WCDMA 850 band functional with the JPM modem? Didn't work for me. Are you on Bell's network?

So is there a way to get the gps working? I can wait on Froyo but the GPS issue is terrible. Also any way to do a true backup of the phone. like an image.

stnd said:
So is there a way to get the gps working? I can wait on Froyo but the GPS issue is terrible. Also any way to do a true backup of the phone. like an image.
Click to expand...
Click to collapse
Can someone confirm whether there is or is not a GPS fix for I9000M for Bell?

opensourcefan said:
Are you sure that you have the WCDMA 850 band functional with the JPM modem? Didn't work for me. Are you on Bell's network?
Click to expand...
Click to collapse
No, im not on bells network. I am on rogers network. Rogers in my area only has 850mhz 3G in this area. I have 3G service and in service mode it says WCDMA 850 Band 5. It works. Its also working on the girlfriends.
Version info:
PDA: i9000XWJP6
PHONE: I9000XXJPM
CSC: I9000XEEJP4
Build: 2010.10
As for the GPS its a bit better but still sucks.

I've never had a GPS problem so I can't tell you if its an issue with the hardware/software/location/interference, etc. Since day 1 (three months ago) I have had no issues locking satellites to 10m accuracy, regardless of firmware. Actually the only time I had an issue was on Osoyoos lake but I suspect that may have had more to do with the proximity to the border crossing.

rdenis said:
I've never had a GPS problem so I can't tell you if its an issue with the hardware/software/location/interference, etc. Since day 1 (three months ago) I have had no issues locking satellites to 10m accuracy, regardless of firmware. Actually the only time I had an issue was on Osoyoos lake but I suspect that may have had more to do with the proximity to the border crossing.
Click to expand...
Click to collapse
Getting a fix isn't the issue. Its active tracking.

Active tracking has been a-o-k the whole time as well which I thought was implied by using the "locking to 10m accuracy" terminology.

Related

JK3 modem, loss of all reception, drains battery, requires a reboot

So, right now I am using the Axura RC1 CE (I will update later), but I have had the problem described in the topic on various other ROMs using the JK3 modem.
It works fine for a few days (time is random, I have not been able to manually reproduce the issue), then randomly I lose all reception. Switching to flight mode fails, it gives no error, it just does nothing, in the notification bar it just says (searching). I have to reboot the phone to get the phone functioning again.
Anyone else experiencing this on ATTs network, or if there is a fix, I spent the last hour searching and going through the various threads to no avail (or I just suck at searching)..
Did you try the Axura thread?
Sent from my liberated Captivate via XDA App.
I'm having the same issue but I've tried Assonance as well and still get the random no service. Tried different i9000 modems as well--anyone know if its safe to use a captivate modem??? I'm guessing no but just want to know if anyone has tried it without borking the phone.
derek_h77 said:
I'm having the same issue but I've tried Assonance as well and still get the random no service. Tried different i9000 modems as well--anyone know if its safe to use a captivate modem??? I'm guessing no but just want to know if anyone has tried it without borking the phone.
Click to expand...
Click to collapse
I'm having this same issue as well, that's why I've tried to stay away from the UGJK3 modem, however, it's seems every custom ROM is starting to use it
As far as using a captivate modem with an i9000 ROM, I've tried that also, while it didn't totally brick my phone, I did get random FCs. I've read that is a dangerous path to go down.
I feel the same way. I might try the CogKernel and see if that helps...
Please, please, PLEASE do not post these types of things in Development.
Sent from my Captivate.
+1 Lets keep this forum area clean .. its just for development stuff guys.
I have had the same issue with all I9000 modems, the only fix that has worked for me is to enter the service menu and force WCDMA 850 Band only. Also, questions should be posted in the question forum.
[this thread is pretty relevant to development - considering the rom chefs are using this modem in their releases and it has a potential major flaw. if the mods find it better to be in Q&A, then please move it - otherwise, i think the right eyes will see it here]
yes, yes and yes!
ive been posting about it in the perception thread, but no one (save for 1 user) chimed in with the same issue.
we both noticed that we both have an issue where we will bounce from 3G to H and back fairly often. this leads me to believe that it could be part of the problem.
i just odin'ed back to stock because my phone isnt receiving incoming calls now.
what i had planned to do was flash the latest perception but use a different modem... but it seems like the only sensible modem is the JK3 (although there is word on the street a new one just leaked?). so that idea is kind of out.
someone here said they were going to try cogkernel2, but i was on setirons and cogkernel2 and it happened with both. it seems to be a modem issue.
i wanted to lock the phone to use 3G only to see if that would help, but no one shared a way how... but reading this post it seems i can do it from the service menu - though i dont know exactly what to set/change to keep it only on 3G. (any help would be great).
so i believe im going to flash perception 8 and see if i can lock it into 3g mode and go from there. this is getting pretty tiring. im hoping if a new modem releases that will help, but i honestly am not sure i can wait since it is making the phone unusable.
below are my posts from the perception thread on the issue.
--
keener31 said:
i searched but did not find...
i see others have had issues with APN force closing. i do as well, but assuming that isnt a problem, i dont mind.
my issue is that after a certain period of time left asleep, my phone will completely fall off the network. changing flight and data mode dont work, nor help. a restart works. this has started a day or two ago, but was not an issue for the first week (give or take). if it is relevant, my network constantly swaps between H and 3G where i live.
i have not found a setting to force 3g (and disable hsdpa) as i figured it was the network hopping that was doing it. am i just missing that setting? anyone else with this issue? (again, i saw people with the apn force close but not complete loss of network unrelated to initial flash)
also, i think that each build should get its own thread. it is VERY difficult to find accurate information on the current build once a thread has 4 builds and 250 pages in it. even with search, it would still be a good idea.
thanks and thanks.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
keener31 said:
anyone having this issue or have any ideas?
of note: going into wifi settings is also borked. it will eventually time out and FC. i also think that the times my phone has completely lost network and not reconnected have happened more often when charging. but that could be coincidence.
(mobile)
sghi897-perception b.5
Click to expand...
Click to collapse
this continued the same way on perception7 with cogkernel2. no real difference.
Ryukeima said:
I have had the same issue with all I9000 modems, the only fix that has worked for me is to enter the service menu and force WCDMA 850 Band only. Also, questions should be posted in the question forum.
Click to expand...
Click to collapse
in relation to my post below yours, does locking the 850 band only force the phone to use only 3G, or is HSDPA/HSUPA still enabled but you found the 850 band to be more stable.
this is what my next attempt will be to get a solid platform going.
I've tried different modems other than jk3 and it doesn't fix the problem. Stinks that you've used Cogkernel2 and it doesn't help. I also tried the different band selection in service mode and it also hasn't help me (apparently this worked for some people). If you want to give it a shot do the following:
1. Dial *#0011#
2. menu button then soft back key
3. then phone control -> network control -> band selection
4. good luck!
derek_h77 said:
I've tried different modems other than jk3 and it doesn't fix the problem. Stinks that you've used Cogkernel2 and it doesn't help. I also tried the different band selection in service mode and it also hasn't help me (apparently this worked for some people). If you want to give it a shot do the following:
1. Dial *#0011#
2. menu button then soft back key
3. then phone control -> network control -> band selection
4. good luck!
Click to expand...
Click to collapse
ugh. that is disheartening. i will try the band lock, thanks.
can you confirm or deny that when you notice your phone goes completely out of service that it has been hopping between 3G and H? it would be interesting to see if we all have that issue as part of it.
also, fingers crossed for that supposed new modem.
/sigh
Yeah this really sucks because these roms are great with this one very big exception. I haven't noticed the hoping before I need to reboot. I have noticed that if I switch into airplane mode once I drop service I can't turn it off.
I had the same issues with Axura and Percetion. I found that switching my network control to WCDMA 1900 only pretty much fixed it. The only problem I had after was that any time I lost service naturally, ie, bad area, or shielded rooms, whenever I came back into a good service area I could never get a signal again. So I would have to reboot.
In the end, I'm back on Cog, 2.3b7 and no issues for about 14 hours now.
bobbylx said:
I had the same issues with Axura and Percetion. I found that switching my network control to WCDMA 1900 only pretty much fixed it. The only problem I had after was that any time I lost service naturally, ie, bad area, or shielded rooms, whenever I came back into a good service area I could never get a signal again. So I would have to reboot.
In the end, I'm back on Cog, 2.3b7 and no issues for about 14 hours now.
Click to expand...
Click to collapse
gotcha. keep us posted on how that turns out!
glad to hear that that version of cog seems to fix the issue. which version did you get--oc or non-oc?
derek_h77 said:
glad to hear that that version of cog seems to fix the issue. which version did you get--oc or non-oc?
Click to expand...
Click to collapse
I'm using the non oc. I'm not gaming or doing anything too wild with my phone so non is just fine for me.
hmmm, makes me think that's the issue then. most of these roms have kernels that have the oc feature.
hey keener, did you have the oc version of cog?
derek_h77 said:
hey keener, did you have the oc version of cog?
Click to expand...
Click to collapse
sadly ive been running non-OC this whole time, so that doesnt appear to be it :/

[Q] KB1 Compatible Modems

Has anyone tried the other modems to work with the stock froyo to see if they work better?
Not tried any myself since flashing KB1, but when on JJ4, trying any non AT&T Froyo modem.bin would result in a loss of sound during voice calls. HSUPA however would work under such a condition. Too bad I need this device to work as a phone first. To get a non AT&T modem, you needed to go with a non AT&T kernel, and then bluetooth voice would be static, so you also need a non AT&T framework. With a native ROM, you are pretty much HSDPA only, unless someone figures out how to patch in necessary code to enable the required handshaking.
I tried some other modems, but none had working sound in phone calls. You might be able to get vibrant modems to work, but then you'd lose 3g
When I was first working on HSUPA for the Captivate, I found that no alternate modem worked properly on the Captivate software. I believe this is due to the code being "wired up" a little differently. Every alternate modem lacked sound in phone calls and the only way around this was to use an I9000 (or Vibrant, etc) ROM with a matching modem. I think everyone stopped trying to find out exactly why the other modems don't work with Captivate ROMs once it reoriented kernels solved any issues we had with running I9000 ROMs on the Captivate. It was just a lot easier to use an I9000 ROM with an I9000 modem.
What we need is some kind of spreadsheet with ROMs down the side and modems across the top, and 3 different symbols representing Data, Voice, and GPS. You would colour each one RED, YELLOW or GREEN depending on how well it performed at that task on a given ROM.

[Q] Sprint Tab; want Gingerbread; don't care about phone service

I have a Sprint tab. I wan't to upgrade to gingerbread, and I don't care about CDMA service, but I have to have wifi. GPS would be preferred but I can live without it. It would also be nice if it wasn't a brick afterwards.
What are my options? Can I just flash Overcome without a modem file? Is there some sort of null modem file I can flash? Is there a different ROM or kernel I should use?
http://forum.xda-developers.com/showthread.php?t=1020167
jiminitaur said:
I have a Sprint tab. I wan't to upgrade to gingerbread, and I don't care about CDMA service, but I have to have wifi. GPS would be preferred but I can live without it. It would also be nice if it wasn't a brick afterwards.
What are my options? Can I just flash Overcome without a modem file? Is there some sort of null modem file I can flash? Is there a different ROM or kernel I should use?
Click to expand...
Click to collapse
Also very interested in this.
I recently put quite a bit of effort into getting GB to run on my Sprint tab. I use WIFI only so I was not concerned with a working CDMA radio. I attempted to flash the European GSM firmware to my device. I tried flashing the kernel and system only, leaving the CDMA radio file intact. I also tried flashing several GSM radio files to the device. In the end I was unsuccessful, and it took several hours to recover the device to an operational state.
If you WERE to get GSM GB working, there is a good chance that GPS and BT wouldn't function. That's kind of a deal breaker for me.
tldr; Sprint users are screwed until the official release of GB because the Overcome team doesn't care about us and the only guy who seems to know how to work the CDMA is making a crappy honeycomb build instead.
IMHO other devs should make a version of the ROM with all data taken out because it'll work for Sprint users and GSM users who tether instead of paying out the rear for a data plan on their tab.
----------------------------
tonman23: Thanks, but i was looking for gingerbread, not honeycomb. It's great that spacemoose can prove it in concept, but I don't like the honeycomb interface, and I'm not interested in flashing a half broken version of it to my phone. I want a stable gingerbread build for the improved performance and minor UI features.
etvaugha: BT & GPS are handled by chips completely independent of the modem. I can't post a link because I'm still new here but the ifixit galaxy tab teardown shows clearly that GSM tabs have distinct BT/WLAN & GPS chips. That's pretty standard fair for android devices, so I doubt they changed it simply for the CDMA models.
It also clearly shows that the modem is a GSM only chip, so the bin files are completely incompatible. The only solution is ROMs that will boot even if the modem isn't working right.
----------------------------
According the the Overcome 2.0 FAQ, the problem is that the phone won't finish booting if a valid modem.bin is not installed. Apparently the phone waits indefinitely (one user, PFOI, mentioned something about it working after 30 min or so) or crashes during the boot because it doesn't get a proper response from the modem chip.
This could easily be overcome if the devs would compile a WIFI only version of the rom/kernel, that doesn't require or support either modem (CDMA nor GSM). It seems to me that the this would be good for both sides, as the data plans for tabs are a rip off and smart users are going to tether their tabs in a mobile situation anyway. It would also probably be better for battery life considering there'd be one less chip running and less bus activity.
I'd imagine all that would be required is removing the modem initialization during the boot sequence. There might be a need to replace the functions that query the modem's status with static value return statements, but when the tab first boots it reports no service, so it's got an inherent ability to deal with not having network access. All that's needed is a couple little snippets to tell the device it doesn't, and to keep it from trying to get it.

[Bell i9000M] Problems after updating

About 2 weeks ago I upgraded my phone to gingerbread. I flashed it with darkys 10.1 (I9000XWJVH), after flashing it I CWM'd the bell modem (I9000UGKC1).
Now I seem to have problems, 3 out of 4 calls to my phone end up going directly to voice mail instead of to the phone, and on outgoing it takes me 2-3 tries to finally connect and make a call. Did I miss a step somewhere, or using something that I shouldn't be? before I flashed it I was on darkys 9.5 with JK2 modem and everything was working flawlessly.
I just flashed the JL2 modem onto it, and still same issue's :/ so i'm guessing either the phone is screwed, or something with darky's isn't right. Still looking for any feedback or suggestions tho.
Yeah I would reflash Darky's and try again. I am pretty sure I was on that combo for a while and it was fine. At any rate you've eliminated a bad download or file as the cause so I'd just reflash darkys maybe with a freshly downloaded copy.
G
Reflashed twice now.. including once doing a full format of the phone before install and still nothing.. in fact it's worse now, before 1 out of 4 worked... now it's none at all... it's really strange cuz data works fine, just phone calls don't. Now I need to figure out how to roll it all back to 9.5 :/
I assume that you have gone to the band selection and made sure 850/1900 on the bands that it shows? I think there is also a JV6 (can't exactly recall) for 850/1900 band in i9000t or b or something. Basically more 850 than 1900 (and I believe jl2/kc1 are the other way around) but its for GB so maybe it might make a difference. Doesn't sound like it could get worse!
Beyond that I can't think of anything else.
G

[Q] Mobile data connectivity issues, which radio?

Hi guys (and girls),
I'm going slightly mad trying to figure out a stable setup for my O2X. I have been switching between the latest CM7 nightlies, and MoDaCo FR19. In general, CM7 gives me quite frequent black screens, and FR19 seems quite stable. However, there is one issue that is present in both ROMs.
I am unable to get a stable mobile data connection when I switch from WiFi. Sometimes it works, and sometimes it doesn't. To get it to work again, it sometimes works to switch to 2G only (and possibly back again). I have tried several different radios recently: 218, 606, and 622, all with the appropriate RIL. The mobile data connection for 218 drops in and out at random without any clear pattern. For the other two radios switching on or off 2G only seems to achieve stable connection. However, it does not actually seem to affect whether I get a 3G or 2G signal. The display can say H or G, even when 2G only is checked. Bluetooth did not work correctly with 606.
To top everything off, the GPS does not seem to behave consistently for a all the different radio versions.
I guess that people have different experience with different radios, so which radio are the guys in Norway using? Do I really have to slog through every released radio and spend the day checking each one of them? Can I expect to find a radio/from combination that blacks to give me a stable GPS and mobile data connectivity, as well as good WiFi?
I know this has been discussed numerous times before, but people never seem to reach any conclusions. I'm just looking for advice on how to proceed to fix my problem.
I'm on cm7 .77 and i honestly havent had a blackscreen since i flashed it (yesterday morning) + battery is good now. For me this is the most stable nightly so ill stick with it for 2 weeks on my holiday )
Edit: bb .502 ril 218(i think) dont have any problems with network switching btw
Sent from my Optimus 2X using XDA App
kolaf said:
Hi guys (and girls),
Do I really have to slog through every released radio and spend the day checking each one of them?
Click to expand...
Click to collapse
You probably have to, yes. This sounds more like a problem with the specific coverage in your area and how the phone interacts with the cell-towers than an actual problem with the phone. You may be in an area with weak signals from several stations, you may be in an area suffering from sudden bursts of noise, there could be a lot of reasons for why this is happening.
First thing I'd try is to upgrade to the latest official firmware (10C - 0622 for Norway), just to have a baseline for comparison. In theory this firwmare (and baseband) has recently been validated by the norwegian carriers, and should have the best chance of success.
Then you should probably do a manual scan (in phone settings) for networks, and pick one manually.
Also try using the INFO menu (*#*#4636#*#*) and see if choosing a specific protocol helps.
If you're still unable to maintain a stable connection, I'd say that'd be grounds for returning the phone for a replacement.
Weak advice, I know, sometimes there just aren't any quick solutions.
::Trym
TrymHansen said:
First thing I'd try is to upgrade to the latest official firmware (10C - 0622 for Norway), just to have a baseline for comparison. In theory this firwmare (and baseband) has recently been validated by the norwegian carriers, and should have the best chance of success.
::Trym
Click to expand...
Click to collapse
Thanks for your reply. Do you by any chance have a link to the firmware?
kolaf said:
Thanks for your reply. Do you by any chance have a link to the firmware?
Click to expand...
Click to collapse
Sort of. In this thread http://forum.xda-developers.com/showthread.php?t=1035041 you'll find complete ROMs of the previous versions. Install one of those with SmartFlash, then run the LG Mobile Update tool to get the latest.
::Trym
Okay, I see, downloading now. So it is good enough to use one of the smartflash files, I don't have to use nvflash?
kolaf said:
Okay, I see, downloading now. So it is good enough to use one of the smartflash files, I don't have to use nvflash?
Click to expand...
Click to collapse
No, you don't have to use NVFlash. The advantage of using the smartflash method is that you get a completely "factory fresh" phone, with all the stock content present (movies, music, pre-installed apps) and you're sure to get a matching baseband and ROM.
Note that you have to flash both files, both the baseband and the ROM. The LG update tool won't update if you have a "new" baseband on an old ROM.
::Trym
So the firmwares from that post do not include the baseband? Anyway, I'm currently running baseband 405, so I guess this is sufficient to get the new update. And the new update will then overwrite everything to the latest official version, both ROM and baseband, correct?
kolaf said:
So the firmwares from that post do not include the baseband? Anyway, I'm currently running baseband 405, so I guess this is sufficient to get the new update. And the new update will then overwrite everything to the latest official version, both ROM and baseband, correct?
Click to expand...
Click to collapse
Yes, it does. Each firmware pack comes with TWO files, the baseband and the ROM. To make sure you avoid any trouble, just flash them both, though, as you say, you can probably stay on the one you have, as yes, the LG Mobile Update tool will overwrite both the baseband and the ROM with the new versions.
::Trym
Flashing of old firmware, with subsequent upgrade to latest release for Norway is complete.
I got version V10c, with baseband 1035.21_20110622, kernel 2.6.32.9. My mobile data seems to be enabled as soon as I get mobile coverage (which admittedly is poor right where I live). Even though it pains me, I guess I should leave it as stock for a day or so to see how it behaves.
I guess rooting it shouldn't affect performance in any way?
My initial experience is that it is much more snappy than the stock firmware that the phone came with, but time will show
kolaf said:
Flashing of old firmware, with subsequent upgrade to latest release for Norway is complete.
I got version V10c, with baseband 1035.21_20110622, kernel 2.6.32.9. My mobile data seems to be enabled as soon as I get mobile coverage (which admittedly is poor right where I live). Even though it pains me, I guess I should leave it as stock for a day or so to see how it behaves.
Click to expand...
Click to collapse
Yeah, you probably should, as your mission right now is to find out whether you can get a stable mobile data connection or not.
kolaf said:
I guess rooting it shouldn't affect performance in any way?
Click to expand...
Click to collapse
Not to my knowledge, but I'd still advise you to wait a few days while sorting out the connection issue. Not that I think rooting it would affect that one way or another, but if you can't get it work as it is, you can return the phone in the state it is now, factory fresh.
kolaf said:
My initial experience is that it is much more snappy than the stock firmware that the phone came with, but time will show
Click to expand...
Click to collapse
It certainly is. It also *stays* snappy over time, which can't be said for the 10a/b versions.
::Trym
The first test drive with the new firmware has been completed. On the way out it switched to mobile data flawlessly, but a longer drive it started falling out and reappearing for only short periods. When we stopped at the destination seemed to stabilise with a 3G connection again.
For the return trip I selected use only 2G network. The network connection remained stable for the entire journey.
I will have to test more, but the conclusion seems to be that it has trouble switching between the 2G and 3G networks when moving. I will try the same trip with a Telenor SIM card, and with different combinations of enabling 2G and 3G modes.
By the way, what is the difference between forcing 2G in the regular settings menu and in the special information menu?
kolaf said:
I will have to test more, but the conclusion seems to be that it has trouble switching between the 2G and 3G networks when moving. I will try the same trip with a Telenor SIM card, and with different combinations of enabling 2G and 3G modes.
By the way, what is the difference between forcing 2G in the regular settings menu and in the special information menu?
Click to expand...
Click to collapse
The 2G only setting in the phone menu equals the "GSM only" setting in the INFO-menu. I'm far from an expert in these matters, this thread has an overview: http://forum.xda-developers.com/showthread.php?t=675136& of what the different modes do.
::Trym
More testing seems to indicate that as long as i leave "use 2G only" check, my mobile data connection seems to be pretty stable. It even switches between 2G and 3G, although apparently a bit more conservatively.
I guess I get to keep my phone anyway
Now for some rooting...
Just an update on the results from my testing. The second time I went out my mobile connection never appeared. This was with only 2G checked in the settings menu. In the Info menu, this corresponded to GSM only.
I then changed it to GSM auto (PRL), and then I got my intermittent mobile data again. I then change it to WCDMA preferred, and my data connection seems to be stable for now. This apparently requires much more testing...
F another chapter in the connectivity saga. Having WCDMA preferred selected in the Info menu, things mostly work, although the data connection drops sometimes.
Another problem I'm noticing with the stock ROM is that it usually is unable to reconnect to my home WiFi network when it comes within range. I have the money was selected to reconnect. Sometimes I even find it disabled in the list.

Categories

Resources