Database Users

Can't send/receive while device is in standby...!

Among a large and growing number of frustrations I have with my 9100 after only a day of use is that POP3 e-mail sending & receiving does not work correctly when the device is in standby.
It all works ok while the device is on (via either of WLAN or GPRS), but when in standby, nothing sends or receives.
I had a vaguely similar problem with my XDA II before, which was that in standby it operated so slowly that it would take 5 minutes just to connect, log in and lot out (i.e., even if there were no messages to collect).
Other pressing problems with the 9100 include:
- extremely poor Skype performance (even with the v1.2 Beta)
- device frequently crashes (esp. coming out of stand-by)
- no back-up support with ActiveSync 4.1
I've done any number of hard resets to no avail.
Perhaps there is a less buggy ROM than the one I have (1.1.9.3 / 16 Sep 05)? If so, where would I get that and how would I go about installing it (in simple steps, please!)?
Any help would be greatly appreciated! I'm nearing the point where I just send the unit back...

Even if nobody can help ...b
Even if nobody can help, I'd love to know if others have had the same issues?
I'm also having problems with the device regularly crashing when I bring it out of standby. Not sure, but this may be related to the Wireless LAN attempting to connect (it works fine while the unit's on).
A --> have others found the Wizard with 1.1.9.3 to be stable?
B --> have others had problems with GPRS send/receive in stand-by mode?

No phonecall when Bluetooth + network

I found out some strange bug:
When my TYTN is connected to the network (UMTS) and bluetooth is switched on too I can not make telephone calls. TYTN starts dialing but disconnects after 5 sec. (No errormessage, but plays a sound 3 times (something like: ding…ding…ding).
Incoming calls do not get trough too (Only busy tone).
When I switch off Bluetooth or network connection everything works fine again.
I searched this forum up and down, but found no answer.
Am I the only one or did somebody notice this bug too?

i found that i cannot use my phone at all if i restart my phone with BT and wifi on somtimes, removing the bt and wifi seems to fix it for me. strange eh?
i often get phone failed.

Its annoying. I am always afraid that I forget to switch off the Networkconnection after I have checked emails or was surfing in the internet.
Its the basic purpos of a phone to be reachable.
Am I the only one with this problem? Is something wrong with my phone?

Sorry to poll this.
But nobody else has noticed this?

Hey folks,
Am I the only one with this bug ?
Really need help for this problem

I forgot to post that my problem has gone.
It definitly was a network problem caused by my networkprovider "One Austria" (now Orange).
After a long call with the technical support they changed some of their serversettings
and wow this problem is gone.
Never happened again (since 6 month)
Hope this helps someone

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.

Bluetooth signal strength bug with my stereo's car

Hi, i write from italy and i have an annoying bug with the stereo of my car (ford fiesta) and my xiaomi mi a1.
from 2-3 months when i take my car and power on my radio the bluetooth appear works fine, the phone establishes the bluetooth connection and i see on the radio the real and correct signal strength; but after few seconds the signal strength disappears and if i try to start call with the command buttons on the radio i can't because the radio say me that i don't have signal! but if i take the phone i see that i have a good signal, and if i try to start the call with the phone works fine, i hear the voice and i can speak without problems with bluetooth system of my radio but anyway appears no signal on the display of the radio.
it's like if the phone after few seconds forgets to broadcast the correct signal strength.
someone have the same problem? how can i solve it? i tried al lot of solutions, but without good results
thank you

Hi I'm facing the same issue but on a BMW car...
I think with August security patch was the last time signal strength on Bluetooth did work properly.
Now I have to reconnect Bluetooth to get it to work for a few minutes or use the phone to start a call.
I am also looking for a solution but nothing so far :/

for me the problem started when i upgrade os from 7 to 8 (i think).
the problem is very "funny" because my wife has the same phone, same os, same patches (i bought both phones in the same moment and from the same shop) but her phone works great with the car without problem! damn!

hi, i update the post because i circumscribed the problem: if i take the car, power on the radio and power on the bluetooth of the phone, the phone connect correctly to the radio, and show me the real and correct signal strength (for example 3 of maximum of 6). but as soon as the signal downgrade or upgrade (from 3 to 2, or from 3 to 4) the signal strength on the radio disappears and reset all (zero) and i'm not able to start call with the command of the radio, i only can start call directly with the phone
i see bluetooth log, when phone connect bt to radio the phone send this info:
+CIND: 0,0,1,3,0,4,0
legend +CIND: ("call",(0,1)),("callsetup",(0-3)),("service",(0,1)),("signal",(0-5)),("roam",(0,1)),("battchg",(0-5)),("callheld",(0-2))
when the signal strength on the radio disappears and reset all (zero) the phone send this info:
+CIEV: 3,0
+CIEV: 4,0
3 = service, 0 = no service (previously was 1)
4 = signal, 0 = no signal (previously was 3)
but the phone in realty upgrade the signal strength from 3 to 4!!!!!

It's really fun and strange ... but I solved the problem: I put the SIM in slot 2 of the phone ... and now it does not make any more problems, it works perfectly! but I can not use micrsd now

The same happens to me. I have a Renault Kadjar with RLink 2
Any Solution?
Thanks

Someone says that with the november's update patch the problem disappears, not for me. i solved the problem with this method: put the sim on the second slot of the phone

Pollocedrone said:
Someone says that with the november's update patch the problem disappears, not for me. i solved the problem with this method: put the sim on the second slot of the phone
Click to expand...
Click to collapse
I've installed the November update but the problem still persists.
BYE

I solved the problem with this method: put the sim on the second slot of the phone

solved definitely with android 9 pie update!

TicWatch Pro 3 LTE Ultra and LTE connection problem

Hello,
I have a TicWatch Pro 3 LTE Ultra and I got an e-SIM from my operator (Orange France). It works ok with one minor detail : it seems that the LTE connection only gets established if I turn flight mode on and then off...
E.g. test situation : watch is connected via BT. I turn off BT and Wifi on the watch, and the LTE connection does not start.
I turn on and off flight mode and voilà, LTE connection is established.
Other test situation : I left home for a footing and after a while realized the watch had not connected to LTE. Turned flight mode on and off, and voilà, LTE connection is ok.
Is it normal behavior? Do I miss a config parameter somewhere? If it is normal, the least I can say is that it is not seamless...
Thanks for any help,

thefa said:
Hello,
I have a TicWatch Pro 3 LTE Ultra and I got an e-SIM from my operator (Orange France). It works ok with one minor detail : it seems that the LTE connection only gets established if I turn flight mode on and then off...
E.g. test situation : watch is connected via BT. I turn off BT and Wifi on the watch, and the LTE connection does not start.
I turn on and off flight mode and voilà, LTE connection is established.
Other test situation : I left home for a footing and after a while realized the watch had not connected to LTE. Turned flight mode on and off, and voilà, LTE connection is ok.
Is it normal behavior? Do I miss a config parameter somewhere? If it is normal, the least I can say is that it is not seamless...
Thanks for any help,
Click to expand...
Click to collapse
Hey, I faced the same situation as you and after some investigation, I figured out what was the cause in my case - maybe it will help you too. I use two SIMs in my phone - the main one is from T-Mobile, the second one is from Orange. It turned out that if my Orange SIM card isn't set as default FOR THE PHONE CALLS, the watch does not switch to LTE automatically (at the same time in the Wear OS app the option of the watch LTE connection disappears). Interestignly, the options of default SIM card for SMS and for mobile internet don't play the key role here. Let's check if this helps in your case, if not, maybe do a factory reset.
Also I found out that it may behave differently on a different ROMs - when I switched ROM to the other one, LTE on my watch enables automatically irrespective of which SIM card is set as default.

Thanks a lot for answering so fast ! I knew there should be someone out there with an opinion ;-)
I do have 2 SIMs on my phone. One is Orange (e-SIM on the phone as well, BTW) and the other is Bouygues.
I tried to configure Orange as default for calls, ran the same test but did not see an improvement.
I'll test more and see if after restarting everything, it gets better.
Thanks again for the answer, I'll report back right here after more tests.

Also, what ROMs are you talking about, please? ROM for the watch? Which ROM do you use? I have the standard one...

Update from the morning, I had a notification on my watch saying that the e-Sim was activated" (which it was already), and now it seems that the LTE connection establishes itself when and as it should !!
Thanks a lot @Lord Sithek !

thefa said:
Update from the morning, I had a notification on my watch saying that the e-Sim was activated" (which it was already), and now it seems that the LTE connection establishes itself when and as it should !!
Thanks a lot @Lord Sithek !
Click to expand...
Click to collapse
Oh wow, I was just writing an answer to you Im glad you got it working. By the way, I was talking about the custom ROM on my phone (Xiaomi Mi Note 10). It's strange, but since I switched to the other one (namely, OcatviOS) the issue is gone, even though I set T-Mobile SIM as the default for everything. I didn't find a key to this mystery yet, but good that it works now
One thing that I observed when I was facing your issue is that when the Orange SIM card wasn't set as default for phone calls, the option in the WearOS app that I marked in the screenshot attached disappeared. Whenever Orange was set as default, it was appearing again. Maybe that will be some kind of clue for you and other users in the future.
Cheers

Thanks! I have to say that the the various effects config parameters _on the phone_ have on the watch are less than clear to me... everything but intuitive...