Someone knows, if does exist something like a small standalone application for toogling wireless connection state (fligth mode on/off)?
Since Himalaya doesn't have a specific HW button to do so, and doing it with the stylus is not much convenient for frequent use, I'm looking for a tool I could assign to one of the existing butons.
My problem, is I have a twin GSM SIM card at the car, and at least some of you should know these twin SIM cards have functional problems, if you doesn't disconnect the primary SIM before.
Anyway you have to switch off/on the primary phone, after leaving the car, to have it able for doing/receiving calls again.
Thanks
Fernando Correia
Related
Hello everybody.
Just question, maybe someone have answer to it. I am trying to use my XDA-II as modem for GPRS... well, why? First - i have unlimited unique package on my SIM (unlimited country calls, unlimited GPRS, unlimited everything inside country). Sure, i am not bad guy, and to not use only GPRS and overload network ( ), i did installation of satellite dish. So, now i have 100 Kb/s downloads. But there is few problems, and main of them -
XDA gives connection by GPRS to other PC's in network, only by using wmodem, what can emulate modem on IrDA, USB, Serial, Bluetooth.
1)When i have attached USB cable, and XDA II charged not 100%, slowly it will go to zero, and turn off GSM part finally. If it is charged 100%, and when i am using GPRS - light is turned off, it will stay 100% always. Very strange situtation, isn't it?
2)wmodem occupating GSM device totally. Means i cannot receive calls at same moment. Why so expensive device is have so ugly features?
Yes, well, it is unique - PDA and GSM in one case, but it is working worst on this case, than regular mobile + PDA!!!
3)And main problem for me, it is when GPRS disconnected by GSM operator (well, sometimes network overload, sometimes signal problems), wmodem is not replying, and i need to go and press Stop/Start (and sometimes mobile need reboot, cause it is not finding network or just stuck), i feel Windows style. I tried ROM's 1.66 and even I-Mate ROM 1.72 - all the same.
As solution i can buy GPRS PCMCIA or USB device, but i need remove each time when i come to home SIM-card, but that means it will be destroyed after 1-2 month, and it is not nice way.
Seems a GSM part XDA is very weak, and looks like Internet in Windows 3.11, like fifth leg for rabbit. Anybody have ideas, or maybe already fix this things?
And sorry for my so bad english
I have the same problem but not for GPRS. I want to use WModem for data enabled GSM. All you said happend for me.
Me is getting exactly the same stuff here
For problem with battery discharging, should be a solution somewhere in this forum, U should change the pins in USB Cable (some soldering involved)
For other problems I do not known solutions yet. ;(
I know there are several apps available for profile switching but I'm looking for some specific functionality.
What I want is an automated profile switch when the mda is on external power.
I think I had a program for this a while ago but due to all the rom upgrades etcetera I seem to have lost it.
Does anybody know which of the known profile apps can do this?
Thanks
haven't come across one that changes the profile based on the charging status however I did have one last year that would react to the GSM cell ID that it was in e.g. if it recogonised the cell at your work it would go into vibrate mode or if it recognised the cell at your home it would switch to quiet or what ever you choose . It was quite neat but I'm damned if I can find it. i'll keep looking.
phoneAlarm will do this
Even Profilws for Windows Mobile does this........ Look at www.winmobileapps.com
Thanks guys, I'll check them out.
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.
Hi! Was just wondering if it's possible to cut off all the connections the phone makes as soon as it an battery is inserted - such as connect to network provider. Was reading a while ago that as soon as the phone got an battery inserted - even when it's turned off - it's possible to turn on the mic. To make this possible the phone got to be susceptible for the instruction to activate the mic or camera which got to come over radio. So is it possible in the open-source world of android? Would really appreciate it if you could enlighten me here!
greets
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...