Database Users

JasJar only works in WCDMA mode

I have my JJ since October 2005. It worked 100% on the original ROM. Early Dec. 2005 I upgraded to the then latest Radio and ROM's. No issues.
Then suddenly From January I cannot get the Phone to work or connect to a data connection. I was told to upgrade to a 64Bit SIM which I did but still no result. I have installed every release of the Radio ROM and every ROM version compatible on the Uni up to date.
When the BAND is set to Auto it will not give me a data connection nor will the phone work. When in GSM same result. When I put the BAND in WCDMA it works 100%. Data connections work, Phone works, SMS etc. Problem is it only works in 3G areas now!
HELP, after 2 months I'm pulling out my hear and carrying my SP3i as backup.

Bump

@postman
what other applications are you using? Have you tried to start a fresh system with no third part apps (ie after a hard reset)? Have you tried to use the .cab files from i-mate for your network?
When I had a JJ I had frequent connections/disconnectiond between GPRS and UMTS. With the latest Radio on my XDA Exec I don't suffer from such frequent switching and it seems to have improved the batetry life as well. I used radio rom version 1.06.00.

J,
At the moment with the new ROM no apps installed appart from the ExtROM. Local network .cab also installed.
Problem is not as such that swtiching is taking place, problem is in BAND = Auto or GSM the Uni does not work for neither phone service nor data. When in WCDMA it works 100% without any issues. Like I said the prob. with this is that 3G is not covered like GSM, so if I leave work the phone feature is basically null and void as only GPRS/GSM/EDGE in area where I live.
Maybe the 3G and GSM/GPRS works off diff stacks / protocols or even hardware?
Yours desperate,
postmanpat

@postman, if you have tried to reflash your JJ and still the problem persists and the original problem did not occur because you added any third-party s/w then my conclusion is that you may have a hardware problem. Contact i-mate they usually reply within 2/3 days.

I would say you probably have a hardware problem !!, the GSM and UMTS aspects of the phone are very separate !!!

1.20 Radio Rom takes long time to reregister on network after dropped off?

Hi all,
I'm currently experiencing a problem where my Softbank X01ht drops off the cellular network because I live in a low strength area, and takes forever, if at all, to automatically connect back to the network, even if I move into an area where I know the cellular strength is high.
If I manually turn off the phone portion of the hermes, and reconnect, then it happily detects the cellular network and connects. In other words, after disconnecting, it acts as though there is no network in range at all, even though I know there is.
This seems to have started after I upgraded my radio rom to version 1.20 from 1.07. Prior to the upgrade, I know it connected back to the network quite quickly after it dropped out. Has anyone else experienced this with the 1.20 Radio Rom? I currently have the Imate jasjam rom installed on my phone with the 1.04 bootloader.
Unsure if this is related, but the area that I live in has a weak UMTS network, but a relatively decent GPRS network. I'm thinking the phone is getting confused over which network to connect too.
It also seems that if I'm in an area with a pretty strong cellular strength, it doesn't drop out? Would I benefit from downgrading to the 1.16 Radio Rom?
Thanks in advance all.
Gene

I can also confirm that things added with that after a soft reset sometime it cant detect network..i have to manualy turn off/on the radio part....generelly it occures if i reset the set just after making a call or just getting disconnected from edge...
the previous 2 radio that i used 1.16 and 1.08 didnt suffer from those probs...
but the main benifit of 1.20 radio that i get is EDGE speed i can pump upto 220Kb (22-24 KB) download speed in flat when connected to pc as wireless modem but with the previous radios i can barely go 160Kb and the speed did uped/down regularly...
and somewhat strange with this 1.20 radio i cant search for network list manually when even i go to manual in network after sometime i get cant read error...but previous radios where ok in that par too...
and the last benifeat that i get with 1.20 is now the SIM STK menu is working.....

sajib said:
I can also confirm that things added with that after a soft reset sometime it cant detect network..i have to manualy turn off/on the radio part....generelly it occures if i reset the set just after making a call or just getting disconnected from edge...
the previous 2 radio that i used 1.16 and 1.08 didnt suffer from those probs...
but the main benifit of 1.20 radio that i get is EDGE speed i can pump upto 220Kb (22-24 KB) download speed in flat when connected to pc as wireless modem but with the previous radios i can barely go 160Kb and the speed did uped/down regularly...
and somewhat strange with this 1.20 radio i cant search for network list manually when even i go to manual in network after sometime i get cant read error...but previous radios where ok in that par too...
and the last benifeat that i get with 1.20 is now the SIM STK menu is working.....
Click to expand...
Click to collapse
Thanks sajib,
Glad I'm not the only one experiencing it. For me, however, it only occurs when it looses connection to the cellular network. After every soft reset so far, it has connected to the cellular network automatically. To me it doesn't seem to even search for the network. That is, after loosing connection, it is resigned to the fact that it can't connect to a network, so doesn't even try, unless I force it too. I think I have seen it connect automatically once or twice, but either way, it takes at least 10-20 minutes, sometimes it never connects, and I force a manual reconnect by turning off the phone and turning it back on. So is this a known problem with the 1.20 Radio Rom?

Try this...
I had the same problem on my TyTn. Took forever to WiFi connect. Then I found this registry setting:
[HKLM\Comm\TIACXWLN1\Params]
"dot11ShortPreambleInvoked"=dword:00000001
Now my WiFi time-to-connect seems much faster.

software_samurai said:
I had the same problem on my TyTn. Took forever to WiFi connect. Then I found this registry setting:
[HKLM\Comm\TIACXWLN1\Params]
"dot11ShortPreambleInvoked"=dword:00000001
Now my WiFi time-to-connect seems much faster.
Click to expand...
Click to collapse
Hi!
Thanks for the advice, but mine isn't a Wifi problem, but a problem with connecting to the cellular network.
Or do you think that your connecting to the WiFi network and the cellular network are one in the same?

i am using the 1.20 radio as well, but cant say that i have had any of the said problems... i have the cingular 8525 and have used the 2 latest cingular roms, the aku2.3 and 2.6.. but i did have some of the same problems with i used cingulars 1.16 radio

shogunmark said:
i am using the 1.20 radio as well, but cant say that i have had any of the said problems... i have the cingular 8525 and have used the 2 latest cingular roms, the aku2.3 and 2.6.. but i did have some of the same problems with i used cingulars 1.16 radio
Click to expand...
Click to collapse
Do you commonly get cellular network disconnects? I find that if I'm moving around the city or driving around in the car, the network connection is maintained, and sometimes will automatically find the network if it does get disconnected. However, it is only when I am home that the phone disconnects and doesn't try to reconnect once it has been disconnected.
Any idea of what might have caused this issue with you with the 1.16 Radio Rom? Possibly something to do with the AKU version? I'm using AKU 2.3.
Thanks,
Gene

GeneNZ said:
Do you commonly get cellular network disconnects? I find that if I'm moving around the city or driving around in the car, the network connection is maintained, and sometimes will automatically find the network if it does get disconnected. However, it is only when I am home that the phone disconnects and doesn't try to reconnect once it has been disconnected.
Any idea of what might have caused this issue with you with the 1.16 Radio Rom? Possibly something to do with the AKU version? I'm using AKU 2.3.
Thanks,
Gene
Click to expand...
Click to collapse
I too have the original problem but have not upgraded the radio ROM. I have the T-Mobile Vario II (sorry not sure what ROM that is) but often when I move from an area of either very weak or no signal to an area with a signal (coming out of a shielded building) I too get the same problem. Initially the phone shows weak (or even strong) signal strength but when I try to make a call I get the box up on the phone screen telling me it cannot connect. I have found that eventually it will, when left to it's own devices, get itself sorted out and allow a connection. But it is invariably quicker turing off the phone (via comm manager) then back on - this always results in a valid connection.
Perhaps the problem that you describe is not related just to the 1.20 Radio ROM upgrade?

tony.wheeler said:
I too have the original problem but have not upgraded the radio ROM. I have the T-Mobile Vario II (sorry not sure what ROM that is) but often when I move from an area of either very weak or no signal to an area with a signal (coming out of a shielded building) I too get the same problem. Initially the phone shows weak (or even strong) signal strength but when I try to make a call I get the box up on the phone screen telling me it cannot connect. I have found that eventually it will, when left to it's own devices, get itself sorted out and allow a connection. But it is invariably quicker turing off the phone (via comm manager) then back on - this always results in a valid connection.
Perhaps the problem that you describe is not related just to the 1.20 Radio ROM upgrade?
Click to expand...
Click to collapse
Hi Tony,
It could possibly be an application or the ROM itself causing the problem, however, I think its the radio rom in my case, simply because this problem only started occuring after I upgraded to the 1.20 Radio Rom. Previously on the 1.07 Radio rom, the phone would connect automatically and immediately. Also I just performed a hard reset after I discovered this problem, and it still seems to be occurring...
I also am sure that after a long while the phone reconnects, I have seen it try reconnect a couple of times. But then again, a couple of times I've left it for 10-30 minutes, and it hasn't reconnected. Unsure of exactly how it chooses to reconnect and when it tries to reconnect. You would think it would try reconnect constantly after a specified period, but in my case it seems very random.

GeneNZ said:
Do you commonly get cellular network disconnects? I find that if I'm moving around the city or driving around in the car, the network connection is maintained, and sometimes will automatically find the network if it does get disconnected. However, it is only when I am home that the phone disconnects and doesn't try to reconnect once it has been disconnected.
Any idea of what might have caused this issue with you with the 1.16 Radio Rom? Possibly something to do with the AKU version? I'm using AKU 2.3.
Thanks,
Gene
Click to expand...
Click to collapse
i actually get pretty solid coverage whether moving or stationary. especially at home since i live not a quarter mile from a cingular tower and i dont think its necessarily related to the aku version since i have gotten the same result with either 2.3 or 2.6. But i can say for sure that the cingular 1.16 radio is junk my biggest complaint was gsm calls cutting out and on my calls on 3G had a very weird digitized background noise, kinda sounded like a bad digital echo... 1.20 fixed all of that for me

shogunmark said:
i actually get pretty solid coverage whether moving or stationary. especially at home since i live not a quarter mile from a cingular tower and i dont think its necessarily related to the aku version since i have gotten the same result with either 2.3 or 2.6. But i can say for sure that the cingular 1.16 radio is junk my biggest complaint was gsm calls cutting out and on my calls on 3G had a very weird digitized background noise, kinda sounded like a bad digital echo... 1.20 fixed all of that for me
Click to expand...
Click to collapse
When I'm roaming around my connection always seems to be sustained. e.g, I've been checking my phone ever 1hour for about 24 hours, and have yet to see my signal lost. Is it possible that the phone is getting confused over which band to connect to? As I said in my first post, I have a relatively weak 3G/UMTS signal from my home (1-2 bars), and a relatively strong GPRS signal (3-4 bars). Presumably the phone is UMTS-preferred, and uses GPRS as a secondary.
I saying this, even if I go to another area which usually has 5 bars UMTS signal, I haven't seen the phone immediately connect. This was after about 10-15minutes waiting in that area.
Gene

GeneNZ said:
When I'm roaming around my connection always seems to be sustained. e.g, I've been checking my phone ever 1hour for about 24 hours, and have yet to see my signal lost. Is it possible that the phone is getting confused over which band to connect to? As I said in my first post, I have a relatively weak 3G/UMTS signal from my home (1-2 bars), and a relatively strong GPRS signal (3-4 bars). Presumably the phone is UMTS-preferred, and uses GPRS as a secondary.
I saying this, even if I go to another area which usually has 5 bars UMTS signal, I haven't seen the phone immediately connect. This was after about 10-15minutes waiting in that area.
Gene
Click to expand...
Click to collapse
yes, the phone is set to prefer the UMTS bands.. have you tried setting the band manually instead of it letting it autosearch? you can do it in the phone settings menu or use the app listed here: http://forum.xda-developers.com/showthread.php?t=286844

HSDPA/3G automatic switching

Hello,
I have just upgraded to the official GPS ROM and I am on the Swedish 3 operator. I have noticed since the upgrade that the network connection is switching from 3G to HSDPA when there is a demand of bandwidth or simply when there is data in either direction.
I can see that the purpose of this was to make it possible and more reliable to place and receive calls during data sessions. I have figured out though, that with the old ROM, there was no such switching (but there was no distinction with the icon, so you really had no idea) and the connection speed was always constantly 1Mbits/s when using Internet Sharing for example. Now with the HSDPA/3G switching/throttling, the connection often drops down to 3G speeds and Skype-calls are lacking quality from this a bit when using Skype in the car which i do quite regularly nowadays using my Jabra JX-10 headset.
I also realize that there is still a problem with outgoing and incoming calls during these automaticly switched-on HSDPA-sessions. That is probably why HTC has decided to keep the HSDPA sessions as short as possible, that's fine, but what boggles me is the algorithm used for the switching. It seems to always kick in HSDPA in the beginning of a new data session, and after a short time of inactivity (while pondering what favourite page to open this time) the connection drops down to 3G and it won't kick back to HSDPA even when you start browsing again, until a certain period of "non-HSDPA-ratio" has been reached and the phone thinks it would be OK to kick in the highspeed again for a little while.
I also noticed that using Skype would keep HSDPA alive once you place a call from a fresh started data session and keep talking ;-)
This is not a particular problem to me, I was just wondering of anyone else here has noticed and had an idea of what the programmers had in mind?
BTW: I am running TomTom 6.010 and Franson GpsGate on the machine now and it works absolutely like a dream. I used to have a Blue-I Bluetooth GPS in the car (Trimble based chipset, only 8 channels but quite OK piece of hardware) but this is far superior when it comes to HOLDING a persistent fix also when moving indoors. The TTFF is quite fast as long as you are outdoors, most of the time i have a fix before i leave the parking space. I noticed there being a dynamic number of satellites of the receiver, sometimes i see 7 out of 8 satellites, and then sometimes i see 10 out of 12! Anyone noticed?
Thanks in advance! Cheers...

It’s not your phone that decide to change from HSDPA mode to normal R99 (384kbits) mode and vice versa. Everything are always controlled by the network. The behaviors that you describe are normal. Besides the HSDPA is quit new for the operators and new parameters needs to be tuned for best performance for every users.
BTW, the degradation that you notice. You are not alone that use HSDPA.... Its finally the big success for 3G

I use Phone Alarm profiles and BandSwitch to control my connection based on business hours. I get a poor singal unless on 3G where my office is located. I force it to GPRS otherwise to save battery.

I have similar problems, cannot receive or start calls when HSDPA connected. Shouldn't that be possible anyway, calling and transferring data at the same time? Or is this a network provider problem?

I too am on the Swedish operator 3. I have an unlocked, non-operator distributed HTC TyTN that I had updated the radio to 1.40xxx and the ROM to Black Dymond 3.5 and was having the exact same problem. I could reproduce the incoming call not getting through error every single time I got the phone to go into HSDPA mode.
After some initial searching I read somewhere it was network dependent (Nokia switches vs Ericsson) and the only way to solve it was to disable the HSDPA using e.g. HTweakC, which I did and it solved the problem, but then of course I couldn't take advantage of the high-speed data access, which was the major reason I got this phone.
I recently noticed that 3 released a new extended ROM with instructions to update the ROM to the latest (as is available on the ftp here) then install their ExtROM. I went to the trouble to try and breakdown what was in this extended ROM, but being a newbie to pocketpc it was all hyroglyphics to me, so I went ahead and installed it over my old HTC ext ROM (which I saved for later use just in case).
When I get around to it I may mount this extended ROM here (I have it, but don't have too much time to put it up right now, so someone may beat me to it).
Anyway, Black Dymond 3.5 didn't install the Extended ROM after a hard reset (assuming that was the intention), so I did it myself afterwards. One initial bug that showed up quickly was the Comm Manager not wanting to start saying it would only manage a max of 7 items (whatever that means). So I installed Schaps latest Comm Manager and it worked fine.
Well, guess what, now there's a daemond that starts on boot and the phone app is different (another bug is that the text on the phone app buttons remain in the 3 theme although I changed back to black, but that's minor), but now I cannot replicate the no incoming calls during HSDPA error.
Apparently they've added something that makes the phone connect properly to their 3G/HSDPA network for call handling. Now I've got full HSDPA speed and no problem on incoming calls (plus still have Black Dymond's great VOIP/SIP WM6 solution).

Ok, as a noob I of course missed the fact that the daemon starting at boot is Voice Commander. Still the actual phone app/dll is somehow different with this ExtROM and it's solved my problems.

No GSM Error Tried Wiki already

Guys here is my situation. I have a Cingular 8525 for some time now I noticed that it was dropping signal and then recovering it I thought it was a radio problem but I changed numerous radios and it didn't fix the issue. Last night I noticed that it wasn't picking up any signal, on turning it on I noticed that I had No GSM I tried the way in the Wiki but I am unable to flash using the radio 1.16 to it I unchecked Allow USB connections but for some reason I cannot flash the radio. I started the phone attempted to flash the phone with several other radios and it just hangs. On rebooting I see NO GSM but when my phone starts up I see it reads the network but I cannot do anything else no calls nothing. Is there another way to flash the radio to my device or is the radio just dead? If so I have another 8525 thats not working can the radio part of it be changed?
Regards

It seems your phone is toggling between 3G and the older GPRS. By default, the 8525 automatically selects 3G if it is available. If you move out of 3G range (considering 3G support nationwide isn't great yet), which will happen often, you will lose signal temporarily and either switch to GPRS or regain a 3G signal. Currently I default my phone to use GPRS just because i can't be bothered with having to deal with dropping signal/calls as often as i used to with the automatic setting. There is a free tool called BandSwitch which can accomplish this for you. The newer version (2.1) is not free but if you can get your hand on the older version which is, it'll work satisfactorily well. I hope this solves your problem.

I had the same problem and nothing worked for me.
Try different solutions posted my various users and see if anytihng works for you.
I think it is a hardware radio problem and probably the only solution is to change the motherboard.
If it is still under warranty - get it done. If not, you are out of luck.

Elf loses phone signal, doesn't reconnect

My wife's Elf keeps losing the phone network connection, each time she was in an area without reception, like elevators etc. and than refuses to register back to the network. Only way to get it to register again is to do a soft reset. (turning off and on the phone radio sometimes works, automatic and manual network selection don't). Tried another SIM card, same thing happened. The problem developed when she started to use GPRS/EDGE (previosly used her phone for calls and SMS).
Any ideas?

Have you tried flashing to a new radio in the elf upgrading forums?
Cheers

Changed radio still no go. Interesting enough it works when she doesn't use GPRS. I changed the RIL registry settings, and will be testing it next few days.

Oh, check it out and see how it goes.
Radio is usually affecting the issue.
You can hard reset, if it doesnt work!
Do backup!!

Seems like I tried everything possible and still nothing, it is probably hardware failure. My wife is going nokia after this, she said no more winmo.