Hi, i have a little bit trouble with my Honor7.
sometimes my Honor 7 lost the signal and has no automatic return into the "signal" received status.
I can see a "x" at the indicator and found some red parts in my akku-mobil-radio-stats.
in the german android-hilfe forum there are more users having this trouble like me.
We have two workarounds:
1.) monitoring the radiostatus with a Tasker task (playing an acoustic notification after loosing the signal)
2.) using a monitor app like: NoCoverageAlert
but this is no solution! To fix this problem temporary, it is helpfull to switch into the "airplane mode" and after than back to "online mode".
here are my questions:
1.) is there somebody else having this trouble?
2.) is there an other solution than my?
(i know, some solution could be to root the phone and switch the online mode automatically using a tasker script, but i do not want to root at this time!)
BTW: my phone is an unrooted phone with B121 (it is the same problem at B140 or B313!)
feel free to answer me!:laugh::good:
Yeah I also faced this problem some days ago. I lost the signal and the phone stayed in the state of no signal. I doesn't happen every time. Maybe only if you stay a longer period without signal.
to reach this situation it will be enough to use our elevator or to visit our basement.
i think it is the modem driver, which does not rescan gsm signal after timeout.
I face this problem frequently after updating to B313 marshmallow test
this problem is present at all versions of Honor 7 firmware!
This problem seems to be solved since update B170. :good::laugh:
if your phone is rooted, you can use Tasker to solve this problem too!
create a new profile "GSM Monitor" with "State" ->Variables->VariableValue/Conditions %CELLSRV eq noservice
create a task "GSM Alarm" with the following steps into it:
If %CELLSRV neq service & %AIR neq on
Run Shell (as root) command: "setting put global airplane_mode_on 1; am broadcast -a android.intent.action.AIRPLANE_MODE --ez state true"
Run Shell (as root) command: "setting put global airplane_mode_on 0; am broadcast -a android.intent.action.AIRPLANE_MODE --ez state false"
please enter command without ""!
finally bundle the Profile "GSM Monitor" with this task, and switch the profil to on.
Every time you lost the signal, tasker switch into airplane mode and back to online. This solved the problem with loosing the GSM Signal 100%!
Related
I've had this problem for some time now and I have no words to describe this symptom ... I know I'm not alone as I know a few other people have the same problem:
The signal bar on Xda II shows ok, green LED still flashes like normal, even my Phone Dashboard showed that I'm connected to my mobile operator with signal strength >90% ... Nothing is suspicious until you start making calls, everything stays at "Dialing ..." and there will be no dialing tone !!! Make another call, same ...
Then you'll use the landline to call yourself on the mobile, it goes to the voice message ... All those time, you were actually not connected to the mobile network! When you realise this, the only remedy is to turn on and off Wireless / Flight Mode.
Now, have you had similar experience ?
I think, somehow the mobile network lost you, and Xda II didn't even notice it therefore did not bother to reconnect as it thought it was still connected. Is this it ? Or anyone has any other theory or solution to this irritating problem ~ which I genuinely have no idea who to blame ?
i think i know what the problem is
:idea: try to download and install this software,
http://www.gb-soft.cz/xdaii/product_gprs_tweak_en.htm
and in "gprs settings", disable "gprs always online", and set it to "search gprs on start gprs connection".
that way, you will be connected to your operator as simple gsm phone, not a gprs one.
the mobility managment in this status (imsi attached, instead of combined attached) is more simple to the network, and you won't lose service.
Hope it will solve your problem,
please update...
Tomer
thanks i have downloaded it and installed, and set the "GPRS always on" to false, but the other one was default ticked ("Search GPRS on start GPRS conn").
i will start my observation today and see if the problem reproduce itself.
Chris
did this solve it for you?
Coming into the 8th day with this Tweak installed, with GPRS set to search on GPRS start (not radio start). So far, the network problem has not occured. I would like to give it another 2 to 3 weeks before announcing the problem solved.
However, just one little note, after installing the Tweak ... a day or two I noticed that the BT Icon no longer shows on the main screen task bar even after numerous soft reset. Not sure what causes it.
#WombatPhoneRoam.mscr
#
#Change Log:
# 0.8 Initial Beta Release
# 0.8.3 Improvements made to Dialup switching and Operator Logo Shown (Work still needs to be done)
# 0.8.4 Added routine to periodically try to scan for 3G operators when phone is in E and G network modes
# 0.8.5 Improved Switching of modes and scanning. Added removal of popup connection windows, Added Automatic repair of lockup of DUN
# 0.8.6 Rewrote parts of the script to streamline logic and improve speed. Improvements made to CPU usage
# 0.8.7 Added Debugging Option to turn off debugging and set variables to debugging settings
# IF YOU LIKE THIS SCRIPT PLEASE CONSIDER A SMALL DONATION with PAYPAL to
# https://www.paypal.com/cgi-bin/webs...=PP-DonationsBF:btn_donateCC_LG.gif:NonHosted
#
#Wombat's PhoneRoam Version 0.8.7
# This Mort Script Came about as I am with "3" Network in Australia and this has Rediculous Hefty Data Charges when it roams on the
# Telstra Network (THREE Uses the Telstra network when Roaming).
# To Combat this I wrote this script to keep the Phone connected to Data to the 3G and HSDPA Modes wherever possible
# When it drops back to Telstra Network on Edge or GPRS it Disables Data usage
# It Should work with any network where you only have one 3G or HSDPA Carrier Available:
# NOTE: It will try to connect to any HIGH SPEED NETWORK AVAILBLE
#
# The script will set the mode to WCDMA (High Speed Data Only) when it CAN reach a High Speed Network to keep it from flip flopping between networks.
# When the WCDMA network is not available (No 3G or H available) it will switch to AUTO mode and allow the phone to Roam onto NON High Speed Networks.
# This is so that you can still make/recieve calls when you are not in a 3G or HSDPA coverage area.
# When High Speed is available again it will switch back a short time after the WCDMA network is again available. (Radio will turn off for short time)
#
# NOTE IT WILL NOT CHANGE MODES OR DISCONNECT WHEN YOU ARE MAKING A PHONE CALL!!!.
# IF THE CALL IS MADE OR RECEIVED While WCDMA ONLY IS ENABLED you may experience phone dropouts if in a fringe High Speed data area.
#
# Whenever it is on a network that DOES NOT provide 3G or H data speeds it will automatically kill the Data connection whenever it is attempted.
# It should do a good job to eliminate Roaming charges but there may still be some small charges due to delays when speeds are switched.
# This script works quite well but still has a few bugs due to the Dialup Networking in WM6 being quite flakey and is prone to locking up.
# NO GUARANTEES that it will not keep you from being charged for DATA on the lower speed networks BEWARE!!!!
#
# Disclaimer: I WILL NOT BE HELD RESPONSIBLE FOR ANY DATA USAGE OR COSTS INCURRED BY THE USE OF THIS SCRIPT OR ANY DAMAGE CAUSED!!!
# BEWARE THIS SCRIPT ATTEMPTS TO KEEP YOU CONNECTED TO THE INTERNET WHENEVER POSSIBLE. YOU ARE RESPONSIBLE FOR ALL DATA COSTS INCURED!!!
# USE AT YOUR OWN RISK!!! YOU HAVE BEEN WARNED!!! SEVERAL TIMES!!!
#
#
# IF YOU LIKE THIS SCRIPT PLEASE CONSIDER A SMALL DONATION with PAYPAL to
https://www.paypal.com/cgi-bin/webs...=PP-DonationsBF:btn_donateCC_LG.gif:NonHosted
#
# Usage: YOU MUST INSTALL VJVolbilis first. You can get it from http://www.vijay555.com/?Releases:VJVolubilis
# It also requires Mortscript to be installed. You will need to set the variables below to point to the install folder
# Place this script in a directory on your WM6 device and create a shortcut in the Startup folder of your PDA
# or just place the script in your startup folder
#
# This will cause the phone to automatically connect to the internet whenever a 3G or H data service is available and stay disconnected
# whenever a G or E network is detected.
#
# The Operator Logo will change to the following
#
# e.g.When Connected to a highspeed network 3 I:HSDPA
# When Disconnected and Roaming Roaming D:Edge
#
# Operator Logo (Sometimes will show a Number which is the Signal Strength not sure why?) or U for Unknown at startup
# ?: = I=Connected, A=Available D=Disconnecting,F=Failure,S:Searching,
# The next shows the Data mode it is on or is available H=HSDPA, 3G=3G, E=Edge, G=GPRS (else it shows the Unknown mode value)
#
# You can create a Terminate Script like this below to kill the running script if you need to. (Included in Zip File)
# TerminateWombatPhoneRoam.mscr
Regards
Wombat
[Script] Wombat's PhoneRoam Script (Stay Connected to High Speed Networks Only)
This is BRILLIANT!! Thankyou so much, there should be some paypal dollars on the way for you mate. Kudos!
seems perfect for me, as I'm on three mobile. I have an HTC Touch HD running Windows Mobile 6.1
I installed VJVolbilis. Then I installed Mortscript. Next, I tried to run wombatphone script which I have on my sd card. Nothing happens. Do I need to do something first?
edit: just realised it is working on the today page. However, quite quickly I get a crash with VJVolbilis causing me to enter my pin again and essentially making my phone stuck
edit2: it appears to also cause scummvm and shell32 to crash (the former is strange as scummvm isn't running)
Just noticed that data still goes out even if roaming if I press 'update now'.
Thanks this is exactly what I needed - will install and see how it goes as I'm heading out to a Three non-service area next week.
Is it possible to get back the standard Operator Logo?
I am back from holidays today so I will look into some of the problems you have been getting.
There is some issues with VJVolbilis as it does sometimes locks up trying to kill the dialup session. Windows Dialup is rather unstable anyway.
Just noticed that data still goes out even if roaming if I press 'update now'.
Click to expand...
Click to collapse
It will still try to dial but it detects this and should kill the dialup session within a few seconds of it starting. I am looking at doing this a better way maybe with the NODATA program to disable the dialup session all together?
However, quite quickly I get a crash with VJVolbilis causing me to enter my pin again and essentially making my phone stuck
Click to expand...
Click to collapse
I too have seen this sometimes. I think it is caused if VJVolbilis runs twice and tries to dial at the same time another session is tring to dial. I have done some things to reduce this in this version but it is still there sometimes. I will look at what I can do to improve it.
Is it possible to get back the standard Operator Logo?
Click to expand...
Click to collapse
I will look at adding a menu system in the future that will allow you to set this Operator functions. I have enabled it in this version as it is a beta and I needed to get some feedback on how it is working so left it enabled. In the Meantime You can disable it by commenting out the following lines
Code:
# RegWriteString( "HKLM", "System\State\Phone", "Current Operator Name", WriterString )
Well I tested the script whilst in a non-roaming area (about 70km outside the CBD, I'm also on the Three network in South Australia) and it worked a treat. I was mainly concerned about Push Email which I use for work. I sent myself a test email and the phone did not receive it.
I did, however, get prompted to enter my username and password for Planet3 numerous times (assume this was whenever ActiveSync tried to access the Exchange server).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I was back with normal metro area, I knew was non-roaming as I had been checking the coverage to see when I went onto roaming, it did not reconnect to Three. I left it a while but still nothing. I had to eventually terminate the script.
I also am running across a problem with VJVolubilis - but this seems only to happen when I soft reset my phone.
I'm now at home which I know is within the Three HSPDA coverage area (as it was previously showing this). However, with the script running again, it's showing "T:OFF". When looking at my Network settings you can see in the top menu bar it's showing the standard HSPDA logo but I'm not sure what "T:OFF" refers to??
*edit*
On a side note I get no sound playing when I do receive an email with your script running.
squibly said:
I was mainly concerned about Push Email which I use for work. I sent myself a test email and the phone did not receive it.
Click to expand...
Click to collapse
I will try to work out how to turn on the push email when the data connection is up this should keep the data flowing. When you are in a Roaming State (i.e. in only an E or G area) you wont be able to recieve emails.
This is whole purpose of this script to stop you from getting charged heaps by Tel$tra when roaming. It should however reconnect once you are back in a Three Coverage area and allow you to receive your emails.
squibly said:
I did, however, get prompted to enter my username and password for Planet3 numerous times (assume this was whenever ActiveSync tried to access the Exchange server).
Click to expand...
Click to collapse
I too have seen this as well. Am working on a way to disable the connection altogether when roaming. This should stop the issue with the password prompt comming up.
I have found the registry keys I need to use I am just working on the logic.
I should have another version available in the next few days.
squibly said:
When I was back with normal metro area, I knew was non-roaming as I had been checking the coverage to see when I went onto roaming, it did not reconnect to Three. I left it a while but still nothing. I had to eventually terminate the script.
Click to expand...
Click to collapse
This I also know about. It is caused by the multple disconnections it needs to make to the connection whenever anything trys to connect to the internet. Hopefully the changes I have made to disable the connection altogether should rectify this.
squibly said:
I also am running across a problem with VJVolubilis - but this seems only to happen when I soft reset my phone.
Click to expand...
Click to collapse
Again this should be reduced in the next version.
squibly said:
it's showing "T:OFF". what does "T:OFF" refers to??
Click to expand...
Click to collapse
This refers to that it is connected but there is no data networks available. I think this may also be related to the crashing of Windows dialup. Hopefully I should have this reduced in the next version also.
squibly said:
*edit*
On a side note I get no sound playing when I do receive an email with your script running.
Click to expand...
Click to collapse
This one puzzles me. I am not using sound at all so there should not be any reason that the sound is effected by my script. I have not seen this as yet here and still get the email received sounds from my device. I will keep an eye out for it. let me know if you narrow down when if it occurs in the next version.
Hey just FYI: Three only uses the Telstra network when "Roaming". When you are in Three Mobile Broadband coverage, it's actually on Three's own infrastructure
WombatPhoneRoam Version 0.8.5 Beta
Released Version 0.8.5 Beta.
#WombatPhoneRoam.mscr
#
#Change Log:
# 0.8 Initial Beta Release
# 0.8.3 Improvements made to Dialup switching and Operator Logo Shown (Work still needs to be done)
# 0.8.4 Added routine to periodically try to scan for 3G operators when phone is in E and G network modes
# 0.8.5 Improved Switching of modes and scanning. Added removal of popup connection windows, Added Automatic repair of lockup of DUN
# IF YOU LIKE THIS SCRIPT PLEASE CONSIDER A SMALL DONATION with PAYPAL by going to following Address
#https://www.paypal.com/cgi-bin/webs...=PP-DonationsBF:btn_donateCC_LG.gif:NonHosted
#Wombat's PhoneRoam Version 0.8.5
# This Mort Script Came about as I am with "3" Network in Australia and this has Rediculous Hefty Data Charges when it roams on the
# Telstra Network (THREE Uses the Telstra network when Roaming).
# To Combat this I wrote this script to keep the Phone connected to Data to the 3G and HSDPA Modes wherever possible
# When it drops back to Telstra Network on Edge or GPRS it Disables Data usage
# It Should work with any network where you only have one 3G or HSDPA Carrier Available:
# NOTE: It will try to connect to any HIGH SPEED NETWORK AVAILBLE
#
# The script will set the mode to WCDMA (High Speed Data Only) when it CAN reach a High Speed Network to keep it from flip flopping between networks.
# When the WCDMA network is not available (No 3G or H available) it will switch to AUTO mode and allow the phone to Roam onto NON High Speed Networks.
# This is so that you can still make/recieve calls when you are not in a 3G or HSDPA coverage area.
# When High Speed is available again it will switch back a short time after the WCDMA network is again available. (Radio will turn off for short time)
#
# NOTE IT WILL NOT CHANGE MODES OR DISCONNECT WHEN YOU ARE MAKING A PHONE CALL!!!.
# IF THE CALL IS MADE OR RECEIVED While WCDMA ONLY IS ENABLED you may experience phone dropouts if in a fringe High Speed data area.
#
# Whenever it is on a network that DOES NOT provide 3G or H data speeds it will automatically kill the Data connection whenever it is attempted.
# It should do a good job to eliminate Roaming charges but there may still be some small charges due to delays when speeds are switched.
# This script works quite well but still has a few bugs due to the Dialup Networking in WM6 being quite flakey and is prone to locking up.
# NO GUARANTEES that it will not keep you from being charged for DATA on the lower speed networks BEWARE!!!!
#
# Disclaimer: I WILL NOT BE HELD RESPONSIBLE FOR ANY DATA USAGE OR COSTS INCURRED BY THE USE OF THIS SCRIPT OR ANY DAMAGE CAUSED!!!
# BEWARE THIS SCRIPT ATTEMPTS TO KEEP YOU CONNECTED TO THE INTERNET WHENEVER POSSIBLE. YOU ARE RESPONSIBLE FOR ALL DATA COSTS INCURED!!!
# USE AT YOUR OWN RISK!!! YOU HAVE BEEN WARNED!!! SEVERAL TIMES!!!
#
#
# IF YOU LIKE THIS SCRIPT PLEASE CONSIDER A SMALL DONATION with PAYPAL by going to following address:
#https://www.paypal.com/cgi-bin/webs...=PP-DonationsBF:btn_donateCC_LG.gif:NonHosted
#
# Usage: YOU MUST INSTALL VJVolbilis first. You can get it from http://www.vijay555.com/?Releases:VJVolubilis
# It also requires Mortscript to be installed. You will need to set the variables below to point to the install folder
# Place this script in a directory on your WM6 device and create a shortcut in the Startup folder of your PDA
# or just place the script in your startup folder
#
# This will cause the phone to automatically connect to the internet whenever a 3G or H data service is available and stay disconnected
# whenever a G or E network is detected.
#
# The Operator Logo will change to the following
#
# e.g.When Connected to a highspeed network 3 I:HSDPA
# When Disconnected and Roaming Roaming D:Edge
#
# Operator Logo (Sometimes will show a Number which is the Signal Strength not sure why?) or U for Unknown at startup
# ?: = I=Connected, A=Available D=Disconnecting,F=Failure,S:Searching,
# The next shows the Data mode it is on or is available H=HSDPA, 3G=3G, E=Edge, G=GPRS (else it shows the Unknown mode value)
#
Working great so far, also on Three in Oz. Thankyou! Will wait for my next bill and donate.
At risk of off-topic which radio do you use and what battery life do you get? I use the radio from the latest three rom update (but different rom) and my battery lasts the working day just about
cheers
Russ
bigruss said:
Working great so far, also on Three in Oz. Thankyou! Will wait for my next bill and donate.
At risk of off-topic which radio do you use and what battery life do you get? I use the radio from the latest three rom update (but different rom) and my battery lasts the working day just about
cheers
Russ
Click to expand...
Click to collapse
Hi Russ,
I use a Kaiser TYTN II on Three (Not originally a Three phone) running WM6.1
These phones chew power like no end and i'm lucky if it lasts the whole day. I have to charge it at home and at night. (and that's without using the GPS.) If I use the GPS or the wireless features it actually discharges faster than it charges especially with the GPS running.
As Mentioned in the read-me I cant guarantee that it wont have any roaming charges they just shouldn't be anywhere near what they would have been if you didn't run the script. Keep an eye on it because if the script stops running it may still connect to the lower speeds. I have limited testing abilities here to make it roam (pretty much the only place is the Restroom ) I have tried to think of as much as I can to prevent it but it is Windows so all bets are off!!!
Wombat
Hi All,
To alleviate some of your fears, I will give you my example of my roaning data usage.
The script has saved me heaps.
I will give you my example of my roaming data usage. I use roughly 100MB - 200MB of data most months on Three.
Last month it was $1.77 (around 1mb) of roaming charges last month (December) This was while I was writing the first version of the script and I had been trying to break the script and sometimes did
Many improvements have been made since then.
On the months that I did not have the script prior to this it usually cost me around $50 for the leakage data when it roamed. Then I learned that you can set the phone to stop lower speed data but the downside of this was that there was times that I did not have phone coverage (when out of three network there was no service). That's why I started to write this script.
I am still waiting for this months bill as I have been continuously testing my script (9th Feb) but I believe it still will be very low roaming data usage. Only time will tell and Im hoping for some good feedback from you all so that I can make this a success and save you some money $$$
Regards
Wombat
Sounds good, I got $100 of roaming data over the last few months. My work (UNSW Campus) has patchy reception so I am constantly in and out of 3's 3g network. So far your script is working beautifully when it roams onto Telstra, at least when I am watching or try to manually activesync for example when roaming.
btw I have a diamond, my previous phone was a kaiser and I think it had slightly better battery life than the diamond. Can't wait for the next leap forwards in battery technology, I too am tied to my charger!
Good stuff Russ.
Keep me posted on the performance you are getting.
I suspect that you may get some higher Battery usage by using the script. This is not so much from the script it will be due to the switching of bands/disconnecting etc and the fact that it is using 3G and HSDPA more often (uses more power for these data types). I have mine connected to Active Sync Exchange syncronisation across the net constantly and get quite a few emails over the day. So far i dont see too many issues with my battery life (other than usual this phone sucks the juice anyway)
I hope to hear from more of you on your experiences and improvements you would like to see in this script. Eventually I would like to make it into an APP.
Thanks to all of you for trying this script and hopefully It will save you money.
Regards
Wombat
Battery Usage
Hi Russ,
I am posting this PM here for all to see as it addresses some good points.
I really appreciate the feedback from you.
I have decided that it needs to be in the thread as you make some good points.
bigruss said:
Hey Wombat,
I sent this by PM because if this is a one off I don't want your script to be tarnished! Feel free to post this and reply into the thread if you would rather keep discussion there.
Click to expand...
Click to collapse
This is really helpful and something that I need from you all to make this a better application. whether it be good or bad. I hope that the people reading the comments wont be too put off by any criticism of the script and will keep in mind that it is still an early Beta version and is not yet finished by any means.
I need more of you to try it out and give me your feedback as this will help me to improve it and add the features that are most wanted and iron out any bugs that I am sure it will have some.
bigruss said:
It seems to be hammering my battery today, task manager (dotfred) shows mortscript processor use at 25-70% all the time! I am in a roaming zone with weak signal (basement).
Click to expand...
Click to collapse
I have not yet had the time to address battery usage properly. As my phone is a heavy usage device as it is I havent really noticed the extra usage of it. (or cared that much at this stage) I have been more concerned at the moment with getting it working properly than battery life. I will definitely look at it to see where I can improve on it in this next version I am writing at the moment. Are you able to try the suggestion below and let me know if the cause of the CPU usage is due to the network scan it does every 40 seconds when in roaming? if so this should be improved by setting it to 240 seconds or more.
I have installed this task manager on my phone now and I am looking at what is using the extra power. I suspect it may have allot to do with the new features that I added to keep the phone online whilst it was roaming.. I had changed quite a bit around in the latest version 0.8.5.
I am wondering if you are getting this same problem if you run the older version? 0.8? that may give me something to work off.
bigruss said:
Can I
1) run a script (don't know how to write) to run manually that will terminate your phoneroam script and deactivate the data connection. I could then use this when I am in the basement (no chance of 3g signal) and run your normal script when I am not? I could possibly automate this with phonealarm depending on cellid I guess.
Click to expand...
Click to collapse
Well hopefully you wont need to disable my script (thats my intention anyway) I just need to address the cpu usage for the next version.(see improvement below) Unfortunately with Windows Mobile it doesn't seem to be anyway to actually disable the auto dialing features easily. I am learning new things about it daily and have asked this same question on other forums on here but I have not gotten a answer on how to actually achieve it.
The NoData program seems to do this but I haven't yet worked out all of the things that need to be done to prevent it from connecting I am trying to avoid using third party programs if I can help it but had to succome to Vjvobilis as it was quite reliable at killing the connection. I am still working on this one I have added some things but still needs more work.
bigruss said:
2) adjust the frequency that this script runs at, maybe so it checks the connection status every 10 minutes, I would rather 'lose' ten minutes of possible 3g connection than have my battery go.
Click to expand...
Click to collapse
I have most of those variables built into the script already however I have them quite low at the moment so that I can test more thoroughly I will look at what I can do to improve this in the next version. This is possibly the reason you are getting such a high CPU usage.
I also will be adding a configuration menus into it later in order to allow tweaking of the settings but this may still be a little while off.
bigruss said:
The problem may be the weak signal, as I posted yesterday it seemed to be working great, then I was mostly in 3g reception and occasionally it would move to roaming. Or could be that I am roaming all day and it keeps searching every minute or so if there is a 3g connection available.
Click to expand...
Click to collapse
This definately appears to be where I may have not set the variables high enough. if you change the following variable in the script
Code:
;Number of seconds before it will check if WCDMA network is available
RescanTime=240
you can set the time it will wait to do a scan of the networks 240 will make it check every 4 minutes easy fixed.
As for putting the discussions in the main forum I probably prefer it as it keeps the thread near to top on the front page. This forum is very busy and threads get burried very quickly on here so the more comments we get in this thread the more people will see and use the script and comment on it and the better it will become.
So people give it a try and give me some feedback on what you like, Dislike or want improved. I will try to do what I can to help
hope This helped you Russ
cheers
Wombat
Will try you suggestion and let you know in the thread, though I may not be back into dodgy reception areas for a week or so. In the meantime I have been trying to use phonealarm, and it does deactivate the data connection quite nicely but it doesn't always switch to my 'roaming' profile when roaming and so I still get some data transfer. You could try phonealarm, backup the registry with the 'data connection active' (wincereg I think is the name of the registry software), change the data connection to inactive and backup the reg again then compare to see what the change did?
Just had a quick go. I am in good HSPDA reception area, the connection is staying active and there is no flipping to roaming at all. The 0.8 script gives me 8% mortscript CPU usage constantly, The 0.8.5 script gives me 40-50% mortscript CPU usage.
I usually disconnect the data connection after 1 minute inactive to save battery. Is there a way to allow this in the script? So the script is only called if an application attempts to make a data connection, then if there is 3g the connection is allowed but if there is only roaming then the connection is killed? Maybe then the script can just be called and doesn't have to run constantly?
btw I'm not daft but I am not a programmer either so forgive me for impossible/useless suggestions :-D
bigruss said:
Just had a quick go. I am in good HSPDA reception area, the connection is staying active and there is no flipping to roaming at all. The 0.8 script gives me 8% mortscript CPU usage constantly, The 0.8.5 script gives me 40-50% mortscript CPU usage.
I usually disconnect the data connection after 1 minute inactive to save battery. Is there a way to allow this in the script? So the script is only called if an application attempts to make a data connection, then if there is 3g the connection is allowed but if there is only roaming then the connection is killed? Maybe then the script can just be called and doesn't have to run constantly?
btw I'm not daft but I am not a programmer either so forgive me for impossible/useless suggestions :-D
Click to expand...
Click to collapse
I haven't looked at that as I need a nailed up connection most of the time I will look into this soon.
From your previous post I have determined where the issue is with the high CPU usage it seems that Mortscript has a tendency to hog cpu when doing checks for tasks and active window checking. I have improved it quite a bit by re-adding the sleep statement near the beginning of the script (under the first while statement) This brings it back to the 10% but it slows it down quite a lot and the timings are out. I will need to look further into this. I have my next version almost written and it will have a major rewrite of some of the routines. Once I have finished testing I will release it. If you want to improve the latest version uncomment the sleep statement under the while. That should reduce the CPU allot.
Code:
While (Initialized = 1)
Sleep (1000)
Hi wornbat,
Does this work only when we are in roaming..... can we make use of it when we are in home network.
On the latest M5 release, and every nightly before, the phone cannot get a GPS lock if it's on LTE. If I go to the network settings and switch off LTE and use 3G, it gets a location lock. Is there anything I can do to fix this?
Note: I'm using the Note 3 for Sprint. No custom Kernel.
Any ideas?
Tried doing a factory reset, but problem still persists. Does anyone know where I can report this?
I know this is an old thread, but maybe this will help someone in the future if they Google search (that's how I found this while looking for a solution). This advice worked for me:
Use root browser to edit the last line in
/etc/gps.conf
The last line will be
LPP_PROFILE=0
Change the 0 to 3. Save and exit.
In advance I will like to appologyse for my communications skills as my english is "NOT VERY GOOD LOOKING".
I can 100% comment on a FIX for the GPS signal lost, many of us have been having this issue for the past few releases of 12.1 - 5.1.1 cianogenmod and I believe I finally found the reason.
When the new system updates gets done the update changes automatically the type of connections that you phone will pick up signal from the towers and satellites. When there is not satellites available it does pick up signal from towers and then based on that compute a calculation and makes a faster FIX that takes 14 seconds at its worst.
So based on that principal idea I went inside the bands and type of connections in the test menu that is in (*#*#4636#*#* ) without brackets and noticed that my phone was set to pick up signals only for LTE/GSM.
This is because this two kind of signals are the most common now days but it is wrong especially for Canada that actually has so many towers with 2g, 3g and CDMA type of conections.
I did a test and inside my home was not getting a FIX picking up just 2-3 satellites and not getting a FIX IN LOCATION, but my new not 4 was so QUICK that I decided to give it a better range of connectivity for tower calculation and went ahead and changed the option to WCDMA and LTE wich are the ones I have notice work the best... I put the one that had the most that includes WCDMA/LTE/GSM etc and ever since it works better than my new note 4.
1 - #*#*4636*#*#
2- Phone information
3 - Set prefer network type.
3 - WCDMA/GSM/LTE
4 - get out and reboot.
This should fix it PLEASE REPORT BACK if this works for you let's keep helping everyone.
--------------------------------------------------
--------------------------------------------------
Okay I have a Verizon Galaxy Note 3 and I keep having WiFi notification pop-up saying connected it's been doing this for the past year and a half. I have done multiple Factory resets with no luck my phone is all stock not rooted and latest available update
If anybody has a solution to this problem could you please tell me that would be much appreciated thank you....
--------------------------------------------------
--------------------------------------------------
teckynerd6249 said:
--------------------------------------------------
--------------------------------------------------
Okay I have a Verizon Galaxy Note 3 and I keep having WiFi notification pop-up saying connected it's been doing this for the past year and a half. I have done multiple Factory resets with no luck my phone is all stock not rooted and latest available update
If anybody has a solution to this problem could you please tell me that would be much appreciated thank you....
--------------------------------------------------
--------------------------------------------------
Click to expand...
Click to collapse
It's supposed to do that, you can try turning it off by going into WiFi settings, use the bottom menu key to select Advanced, and unchecking the notification. On my Note 3, even though that setting is off, I still get a quick popup showing when it connects.
It should only do it once when it connects to an access point. However if you have it set (also under advanced settings) to turn off WiFi after your phone goes to sleep for a certain period of time, when it wakes it will reconnect, and renotify you.
Sent from my SM-N900V using Tapatalk
donc113 said:
It's supposed to do that, you can try turning it off by going into WiFi settings, use the bottom menu key to select Advanced, and unchecking the notification. On my Note 3, even though that setting is off, I still get a quick popup showing when it connects.
It should only do it once when it connects to an access point. However if you have it set (also under advanced settings) to turn off WiFi after your phone goes to sleep for a certain period of time, when it wakes it will reconnect, and renotify you.
Click to expand...
Click to collapse
I forgot to mention it repeats itself over and over after saying connected annoying already told notification I do know how to disable it but that's not the problem it's repetitive even after saying it's connected on all WiFi networks
One possibility is that your connection actually is bouncing. (Continuously disconnecting/reconnecting)
If that were the case then the frequent messages are appropriate, but symptomatic of some other problem such as hardware (flakey antenna connection?) or a strange software stack incompatibility between your handset and WiFi AP.
(The latter is more likely if you observe the problem only on certain WiFi networks; the former if it happens on all of them)
while [ 1 -eq 1 ] ; do
_res=`ifconfig wlan0 | grep -c 'inet addr'`
if [ $_res -gt 0 ] ; then
echo 'wlan0 UP'
else
echo 'wlan0 DOWN'
fi
done
bftb0 said:
One possibility is that your connection actually is bouncing. (Continuously disconnecting/reconnecting)
If that were the case then the frequent messages are appropriate, but symptomatic of some other problem such as hardware (flakey antenna connection?) or a strange software stack incompatibility between your handset and WiFi AP.
(The latter is more likely if you observe the problem only on certain WiFi networks; the former if it happens on all of them)
while [ 1 -eq 1 ] ; do
_res=`ifconfig wlan0 | grep -c 'inet addr'`
if [ $_res -gt 0 ] ; then
echo 'wlan0 UP'
else
echo 'wlan0 DOWN'
fi
done
Click to expand...
Click to collapse
Thank for the info. It happens on any wifi network im debating on removing the os completely and reinstall it. Any more info would be awesome thanks
Completely useless information but just figured I'd share my story. My father just gave back my old Note 3 and said he was having issues with it. WiFi, WiFi Tether, & GPS were all broke and network connection would drop randomly throughout the day. He was on PL1 or whatever the latest firmware update was. I then flashed back to OB6 firmware which corrected ALL the issues. I let the phone download the OF1 or whatever the next firmware update was and it succeeded with everything still working properly. Overnight the phone downloaded the PL1 or whatever the most recent firmware is, which I updated to that morning. PL1 re-broke EVERYTHING on the phone that I spent a day fixing. I then reflashed OB6 and then rooted and unlocked the bootloader and am downloading an Android 6.0 ROM to try right now. LONG STORY SHORT, the most recent Verizon update SUCKS and breaks the functionality of the phone (at least for me).
teckynerd6249 said:
Thank for the info. It happens on any wifi network im debating on removing the os completely and reinstall it. Any more info would be awesome thanks
Click to expand...
Click to collapse
Try running that script (say in a terminal emulator) I posted in my reply. If you see the wlan0 interface bouncing up and down it suggests a hardware problem (given that you said the symptom is on all WiFi networks).
I suppose it could be software... but until you start digging for more information (e.g. dmesg output or logcat output) or trying some experiments, it's all guesswork at this point.
AntwonJenkins said:
Completely useless information but just figured I'd share my story. My father just gave back my old Note 3 and said he was having issues with it. WiFi, WiFi Tether, & GPS were all broke and network connection would drop randomly throughout the day. He was on PL1 or whatever the latest firmware update was. I then flashed back to OB6 firmware which corrected ALL the issues. I let the phone download the OF1 or whatever the next firmware update was and it succeeded with everything still working properly. Overnight the phone downloaded the PL1 or whatever the most recent firmware is, which I updated to that morning. PL1 re-broke EVERYTHING on the phone that I spent a day fixing. I then reflashed OB6 and then rooted and unlocked the bootloader and am downloading an Android 6.0 ROM to try right now. LONG STORY SHORT, the most recent Verizon update SUCKS and breaks the functionality of the phone (at least for me).
Click to expand...
Click to collapse
The OP failed to report what ROM, modem, or bootloader he is using so it's impossible to determine if were talking apples vs. oranges here.
That said, I am using the PL1 modem (most recent), the AryaMod ROM, and the NC4 bootloader and do not experience the mentioned symptoms. Both WiFi & GPS seem to behave correctly. That would seem to exonerate at least the baseband/modem firmware, but who knows.
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...