I've just started developing engineering software for the TyTNII for the telecoms community which I will be posting here as "freeware".
Like every other developer here I wrote a "CellTrack" clone in c# using RIL. The problem is, once the phones "in call" the MCC/MNC/Cell ID stops updating. No matter how many times I query the RIL, it always reports the same Cell ID even though I've driven 30 miles from the originating cell.... end the call and it'll instantly flick over to the new correct cell.
The question is before I go insane ... is there anyway to get live updates whilst the phones "in call" .... I've tried loads of RIL clones and they all do the same.
It'd be a killer app if this could be done!!
It's Saturday night and i'm just off testing FieldtEST by frank!!!
Cheers
Phil
Right ... I've discovered that it's impossible in Windows Mobile to get the Cell ID whilst the phone is "In Call", either if you try to get it from the RIL or via AT commands (AT+GREG).
I think this is because "hand overs" are done by the phone only reporting the surrounding bcch numbers to the BSC but i'm probably wrong ... Only spent 4 years doing BTS data!!
Hopefully someone will read this and it'll save them a week of trying!!!
Cheers
Phil
Hi guys!
I am not a developer but maybe the following can be of help.
Are you speaking about UMTS right?
The MCC/MNC/Cell ID you access from the RIL is probably updated only when the mobile performs "Cell Reselections". The latters are performed only when the mobile is Idle or using the common channels.
When you are in a call, "Cell Reselections" are not anymore performed. "Hard, Soft, or Softer handovers" are used instead.
The mobile keeps a list of connected cells (they can be more than one). In the UMTS standards this list is called "active list set".
The phone just sends measurement reports to the RNC. The latter commands to the phone which cell to add, remove, or replace from the active list set.
Therefore the cellID you are getting with the RIL command remains obsolete.
If you have a RIL query or AT command to get the "active list set" than you are done!
Hope it helps...
btw, I didn't find clones of CellTrack for WM.. Can you please provide me with some links? Thank you very much!
Danilo
Thanks for your explanation ...
As for the Windows Mobile clones of Cell Track ... if you search for CELLID in the forum you can take your pick of which one you like the look of. they all work pretty much the same. You will need to be able to build the database yourself like you did with Cell Track.
Cell Track Clones clicky
Mines just like Cell Track, but the main plus points i've added is a "Bearing to site", and a "Distance to Site (In miles)" which updates live from the GPS.
If you want a pretty much finished beta version PM me your email and i'll send it over.
Cheers
Phil
net library for cell id and more
.net library for cell id and more
h tt p:// cellid.ru / celliddelta.zip
hi,
i'm having problems with google maps latitude not updating in the background. i'm supposed to be able to have my google maps location updated automatically in the background by cell id location detection.
apparently some phones are unable to do this :
"Windows Mobile phones that do not support cell ID (cell tower) location detection because of a manufacturer limitation in allowing the proper API will not be able to use Latitude to update location automatically in the background. This is a limitation of certain Windows Mobile phones that cannot be worked around currently."
does anyone know if the x1 supports cell ID location detection ?
thanks in advance
The google maps cell id location (not with latitude) works for me. It gives me my (general, about a radius of 300 yards) location even with the GPS turned off.
thanks for the reply !
do you use latitude and does it auto-update ?
cheers !
It does .. if you have GM on, it updates about once per minute, via GSM or GPS. If you turn them off with Latitude on, it will ask you if you want to detect the position even with GM off. If you say yes, GM will silently start-up every 20 minutes, detect to position via GSM, and then update the position in Latitude. It works even with phone in stand-by (screen turned off).
i have just re-downloaded the latest version of maps and it hasn't updated in over an hour despite the fact that i have latitude updates switched on.
any ideas ?
still no update in 12 hours !
Strange .. you can use FdcSoft TaskManager to display notifications queue. You should see GoogleMaps waiting there for next 20 minutes. It works for me but I used it only two days or so. I will test it some more.
It seems the refresh is only done when data connection is active. It does not initiate one. Also WIFI is by default off on X1 while standby (GPRS is not).
But it works rather reliably it seems.
hmmm, still no update for me in 18 hours. my data connection has been on for a couple of hours during that time.
any ideas ?
what should i be looking for in my notifications queue ?
cheers !
The process is GoogleMaps\googlemapsrunat.exe and it should be on top. Hard to miss, really.
Btw. you have latitude working when GM is on, right ?
hi,
yeah, latitude works just fine when i'm actually in google maps but as soon as i close the app, my location is no longer updated.
i don't have that process in my list - i assume it's there all the time and is run every 20 minutes or so ?
when i have google maps open, choose Latitude and the click the Privacy tab, i have "Detect your location" selected. is there anything else that i need to do ?
thanks again !
Not sure if we understand eachother .. it should not be in the process list .. it is in 'notifications' list. There is queue of all tasks scheduled for some time or event. Fdc Task manager can display the queue, just select it from the combo.
There you should see it waiting.
Are you asked if you want to detect location when exiting GM ?
ok, that makes more sense.
it's not there either and i'm not prompted when exit google maps ...
:-(
My version is 3.2.1 (#35).
Btw. I have just found .. you must exit the maps with 'exit' command in menu. Closing it with X won't ask the question.
genius !
ok, i now have the notification so hopefully my updates will work from now on ...
thanks for all your assistance.
have just checked and it auto-updates after an hour. not ideal but better than nothing !
thanks again.
Hello everyone,
A big thanks in advance (and after, no worries) if you can help.
I have a nexus 6, CM13 and all it's fine but few weeks ago my bluetooth started to act a little strange by itself : it's turn off, disconnect the headset and turn on and reconnect the headset.
I have made test this weekend and I don't see any pattern.
I desactivate all the authorization for all the apps and no succes. I deinstall lot of apps but nothing.
I have the habit of listenning audio book when running or fitness so to have to relaunch the play during activity is quite boring.
If you have any idea or if you need some log, please ask!
You're not alone. I and many others are having the same problem with no resolution yet. I even bought a new headset a couple months ago, thinking my headset was going bad, but that didn't help.
I saw that. I find a lot of thread on the net about this problem. Various rom, various phone and no solution.
Sometimes they tried to do factory reset but with no success.
And I have two headset (one for the sport and one for the rest) so I already exclude the headset.
BT issues are really nothing new with CM roms. They have had them for years and never fixed them. This is why more and more are no longer using their code. Many are completely dropping all their code with the 7.0 update.
Your best bet is to troubleshoot it yourself. The first thing you should have done is pull a logcat.
JimSmith94 said:
You're not alone. I and many others are having the same problem with no resolution yet. I even bought a new headset a couple months ago, thinking my headset was going bad, but that didn't help.
Click to expand...
Click to collapse
I should have mentioned that I'm not on CM, but am having the same problems on stock rooted 6.0.1 with the August security update.
JimSmith94 said:
I should have mentioned that I'm not on CM, but am having the same problems on stock rooted 6.0.1 with the August security update.
Click to expand...
Click to collapse
This normally turns out to be a kernel issue somewhere. As you are on stock then I would get a logcat. At worst case it maybe a hardware issue. A log will help you determine where the issue is.
Same problem here. For months having this annoying issue.
I'm also on stock rom, and this is getting worse everyday. I am now on Nougat beta participating in the preview with the stock rom and the problem is still there.
I tried several fixes and resets, wipes, etc. with no success. I am very close to throw it against the wall, believe me. It is specially annoying with my VW bluetooth and with a Jabra 510 speaker. With my other bluetooth headphones (Genius) it works very well and no cuts... I don't understand the pattern...
So, I read to do a logcat... how do I do it? And how do I deduct from the log what is happening and when?
Thanks in advance.
agustinsj said:
Same problem here. For months having this annoying issue.
I'm also on stock rom, and this is getting worse everyday. I am now on Nougat beta participating in the preview with the stock rom and the problem is still there.
I tried several fixes and resets, wipes, etc. with no success. I am very close to throw it against the wall, believe me. It is specially annoying with my VW bluetooth and with a Jabra 510 speaker. With my other bluetooth headphones (Genius) it works very well and no cuts... I don't understand the pattern...
So, I read to do a logcat... how do I do it? And how do I deduct from the log what is happening and when?
Thanks in advance.
Click to expand...
Click to collapse
XDA Developers, being a forum for developers, has many tutorials and help threads about logcat, since a logcat is the single best, and often the ONLY way to find OS level issues.
http://forum.xda-developers.com/showthread.php?t=2141817
http://forum.xda-developers.com/showthread.php?t=1726238
http://forum.xda-developers.com/showthread.php?t=1378491
Pkt_Lnt said:
XDA Developers, being a forum for developers, has many tutorials and help threads about logcat, since a logcat is the single best, and often the ONLY way to find OS level issues.
http://forum.xda-developers.com/showthread.php?t=2141817
http://forum.xda-developers.com/showthread.php?t=1726238
http://forum.xda-developers.com/showthread.php?t=1378491
Click to expand...
Click to collapse
I have a BT headset and an Android Wear watch connected.Here are (I think) the relevant parts of one of my logcats where it dies and restarts four minutes apart:
Code:
08-10 12:53:17.182 975 1681 I ActivityManager: Process com.android.bluetooth (pid 21994) has died
08-10 12:53:17.183 975 1681 W ActivityManager: Scheduling restart of crashed service
...
08-10 12:53:17.401 975 1073 I ActivityManager: Start proc 31623:com.android.bluetooth/1002 for service com.android.bluetooth/.btservice.AdapterService
...
08-10 12:53:20.312 975 3086 I ActivityManager: Process com.android.bluetooth (pid 31623) has died
08-10 12:53:20.313 975 3086 W ActivityManager: Scheduling restart of crashed service
...
08-10 12:53:21.362 975 2813 I ActivityManager: Start proc 31765:com.android.bluetooth/1002 for broadcast com.android.bluetooth/.pbap.BluetoothPbapReceiver
...
08-10 12:57:43.497 975 3092 I ActivityManager: Process com.android.bluetooth (pid 31765) has died
08-10 12:57:43.499 975 3092 W ActivityManager: Scheduling restart of crashed service
...
08-10 12:57:43.695 975 1073 I ActivityManager: Start proc 932:com.android.bluetooth/1002 for service com.android.bluetooth/.btservice.AdapterService
...
08-10 12:57:46.510 975 3098 I ActivityManager: Process com.android.bluetooth (pid 932) has died
08-10 12:57:46.511 975 3098 W ActivityManager: Scheduling restart of crashed service
...
08-10 12:57:49.453 975 1073 I ActivityManager: Start proc 1403:com.android.bluetooth/1002 for service com.android.bluetooth/.btservice.AdapterService
I see nothing before it dies, and it seems really weird that BT dies with only an informational message, but the restarts are warnings.
JimSmith94 said:
I have a BT headset and an Android Wear watch connected.Here are (I think) the relevant parts of one of my logcats where it dies and restarts four minutes apart:
Code:
08-10 12:53:17.182 975 1681 I ActivityManager: Process com.android.bluetooth (pid 21994) has died
08-10 12:53:17.183 975 1681 W ActivityManager: Scheduling restart of crashed service
...
08-10 12:53:17.401 975 1073 I ActivityManager: Start proc 31623:com.android.bluetooth/1002 for service com.android.bluetooth/.btservice.AdapterService
...
08-10 12:53:20.312 975 3086 I ActivityManager: Process com.android.bluetooth (pid 31623) has died
08-10 12:53:20.313 975 3086 W ActivityManager: Scheduling restart of crashed service
...
08-10 12:53:21.362 975 2813 I ActivityManager: Start proc 31765:com.android.bluetooth/1002 for broadcast com.android.bluetooth/.pbap.BluetoothPbapReceiver
...
08-10 12:57:43.497 975 3092 I ActivityManager: Process com.android.bluetooth (pid 31765) has died
08-10 12:57:43.499 975 3092 W ActivityManager: Scheduling restart of crashed service
...
08-10 12:57:43.695 975 1073 I ActivityManager: Start proc 932:com.android.bluetooth/1002 for service com.android.bluetooth/.btservice.AdapterService
...
08-10 12:57:46.510 975 3098 I ActivityManager: Process com.android.bluetooth (pid 932) has died
08-10 12:57:46.511 975 3098 W ActivityManager: Scheduling restart of crashed service
...
08-10 12:57:49.453 975 1073 I ActivityManager: Start proc 1403:com.android.bluetooth/1002 for service com.android.bluetooth/.btservice.AdapterService
I see nothing before it dies, and it seems really weird that BT dies with only an informational message, but the restarts are warnings.
Click to expand...
Click to collapse
Is this logcat from the watch or phone and is the headset connected to the watch or phone and is this BT crash from the watch or headset?
I'm trying to understand if this is a phone issue or watch issue and who to get this information to for some help?
As we've exchanged posts before, both my headset and watch drop connections from the phone, though I've minimized this with some hacks. This only happens when I am out and about, and can not duplicate it when I am near a computer to get a logcat. When I'm walking or on my bike I get it from the headset, even when the phone is on my belt only two feet away. When I look at the watch, it has dropped too.
Pkt_Lnt said:
Is this logcat from the watch or phone and is the headset connected to the watch or phone and is this BT crash from the watch or headset?
I'm trying to understand if this is a phone issue or watch issue and who to get this information to for some help?
As we've exchanged posts before, both my headset and watch drop connections from the phone, though I've minimized this with some hacks. This only happens when I am out and about, and can not duplicate it when I am near a computer to get a logcat. When I'm walking or on my bike I get it from the headset, even when the phone is on my belt only two feet away. When I look at the watch, it has dropped too.
Click to expand...
Click to collapse
Hi Pkt_Lnt! This is from my phone and I have saved the rest of the logcat if it will help you. My BT headset is only connected to my phone. This was at home while I was on a phone call and the BT connections to both the headset and watch were lost twice. The phone icon went from connected to just on both times. I don't recall this happening before I got an Android Wear watch, but I've had several over the past few years.
BTW, I'm only on the phone two or three times a day, but this happens almost every time I receive a call, but very rarely when I initiate a call.
I'd be interested in what hacks you have done to see if they might help me.
Thanks Pkt_Lnt! for your useful information.
As Jim I also have a watch connected (Huawei) and I see also continuous but random disc&connections.
Will try to get that catlog for the thread as soon as I can.
One thing that maybe a chance or not is that always always when I'm ridding and go through a bridge the BT disconnects from my car headset. Always. That is the only pattern I can verify. Can a LTE cell update break a BT connection? Maybe the radio chip is fooled by this change?
I remember in previous versions to marshmallow that this happened once in a blue moon... now dozens an hour.
Thanks.
JimSmith94 said:
Hi Pkt_Lnt! This is from my phone and I have saved the rest of the logcat if it will help you. My BT headset is only connected to my phone. This was at home while I was on a phone call and the BT connections to both the headset and watch were lost twice. The phone icon went from connected to just on both times. I don't recall this happening before I got an Android Wear watch, but I've had several over the past few years.
BTW, I'm only on the phone two or three times a day, but this happens almost every time I receive a call, but very rarely when I initiate a call.
I'd be interested in what hacks you have done to see if they might help me.
Click to expand...
Click to collapse
I've frozen Google Connectivity Services, switched to Legacy DHCP in developer settings, turned off wifi on the watch, and disabled cloud sync in the Android Wear app on the phone.
agustinsj said:
Thanks Pkt_Lnt! for your useful information.
As Jim I also have a watch connected (Huawei) and I see also continuous but random disc&connections.
Will try to get that catlog for the thread as soon as I can.
One thing that maybe a chance or not is that always always when I'm ridding and go through a bridge the BT disconnects from my car headset. Always. That is the only pattern I can verify. Can a LTE cell update break a BT connection? Maybe the radio chip is fooled by this change?
I remember in previous versions to marshmallow that this happened once in a blue moon... now dozens an hour.
Thanks.
Click to expand...
Click to collapse
Well, the bridge would block the cell signal, but I don't think it should drop the BT since they are handled by different software, but I'm not sure what hardware (antenna) handle cellular / wifi / bluetooth. This is hard to sort out. What I know is that cellular, voice and data, is controlled by the phone radio. Both wifi and bluetooth are controlled by the kernel. On bluetooth and wifi drops, they will occur simultaneously for me. When I see a bluetooth drop on mobile, there is not effect on my cellular data.
So, what would help is noting phone type, ROM used, kernel used, and I know we all have Huawei watches. I have a Nexus 6, Pure nexus ROM, ElementalX kernel. I've tested three kernels besides stock to see what is happening. It just occurred to me that I have not disconnected my watch when out using my headset to see if those headset dropouts happen.
edit - Even though I've tried differnet kernels to solve the BT / WiFi drops, I suspect they have the same stock kernel modules that control those functions since I've seen no difference in them. No kernel control apps have anything related to those two functions either. (le sigh)
There is no solution, but hope for the future.
Check posts 8 and 11 here. I have the HBS-730 and it works except for the "out of range" dropouts.
http://forum.xda-developers.com/nexus-6/help/nexus-6-marshmallow-bluetooth-operating-t3253708
Ideas from Reddit, none have worked for me.
https://www.reddit.com/r/nexus6/comments/4pk876/nexus_6_keeps_disconnecting_bluetooth_audio_at/
Google Product forums have many posts, but no solutions and it is a user to user forum like XDA.
I've found so many entries in Google Code, but none that seem to be this issue. I have not been able to search all that come up to narrow it down and report with a good logcat.
https://code.google.com/p/android/i...D+Type+Status+Owner+Summary+Stars&cells=tiles
Now my head hurts from all the searching, I need a time out.
Pkt_Lnt said:
I've frozen Google Connectivity Services, switched to Legacy DHCP in developer settings, turned off wifi on the watch, and disabled cloud sync in the Android Wear app on the phone.
Well, the bridge would block the cell signal, but I don't think it should drop the BT since they are handled by different software, but I'm not sure what hardware (antenna) handle cellular / wifi / bluetooth. This is hard to sort out. What I know is that cellular, voice and data, is controlled by the phone radio. Both wifi and bluetooth are controlled by the kernel. On bluetooth and wifi drops, they will occur simultaneously for me. When I see a bluetooth drop on mobile, there is not effect on my cellular data.
So, what would help is noting phone type, ROM used, kernel used, and I know we all have Huawei watches. I have a Nexus 6, Pure nexus ROM, ElementalX kernel. I've tested three kernels besides stock to see what is happening. It just occurred to me that I have not disconnected my watch when out using my headset to see if those headset dropouts happen.
edit - Even though I've tried differnet kernels to solve the BT / WiFi drops, I suspect they have the same stock kernel modules that control those functions since I've seen no difference in them. No kernel control apps have anything related to those two functions either. (le sigh)
Click to expand...
Click to collapse
I am on a stock rooted Nexus 6 running the latest MOB30W, my watch is the Huawei Watch running the latest M6E69B, and I'm on the latest Android Wear 1.5.0.3124679.gms.
I have tried your hacks as well, but they made no difference. However, I just tried your suggestion and disconnected my watch in the Android Wear app. I just made it through a 25 minute incoming call with no disconnect at all, so I think you're on to something! Maybe for now, somebody can come up with something in Tasker to disconnect the watch when the phone is answered and reconnect on hangup.
JimSmith94 said:
I am on a stock rooted Nexus 6 running the latest MOB30W, my watch is the Huawei Watch running the latest M6E69B, and I'm on the latest Android Wear 1.5.0.3124679.gms.
I have tried your hacks as well, but they made no difference. However, I just tried your suggestion and disconnected my watch in the Android Wear app. I just made it through a 25 minute incoming call with no disconnect at all, so I think you're on to something! Maybe for now, somebody can come up with something in Tasker to disconnect the watch when the phone is answered and reconnect on hangup.
Click to expand...
Click to collapse
Ah, I love Tasker ideas!
http://www.pocketables.com/2015/01/disconnecting-one-bluetooth-device-using-tasker.html
Try the attached, customize them for your device and contacts and let me know. I don't have a second phone here to test them at the moment.
You will need Secure Settings if you don't already have it. It has its own idiosyncrasies with systemless root if you have it.
Attachments removed because of errors in my logic.
Pkt_Lnt said:
Ah, I love Tasker ideas!
http://www.pocketables.com/2015/01/disconnecting-one-bluetooth-device-using-tasker.html
Try the attached, customize them for your device and contacts and let me know. I don't have a second phone here to test them at the moment.
You will need Secure Settings if you don't already have it. It has its own idiosyncrasies with systemless root if you have it.
Click to expand...
Click to collapse
Haha, I had created my own before I saw that you had attached yours! The watch ID is different of course, but yours disconnects when the phone is ringing and reconnects when it's off hook.
As I understand it, off hook means that the phone state is either dialing, active, or on hold, so I set mine to disconnect the watch when the phone is off hook and reconnect when it's idle. I'm a Tasker rookie, and I don't have a second phone to test with either, so I could be wrong.
JimSmith94 said:
Haha, I had created my own before I saw that you had attached yours! The watch ID is different of course, but yours disconnects when the phone is ringing and reconnects when it's off hook.
As I understand it, off hook means that the phone state is either dialing, active, or on hold, so I set mine to disconnect the watch when the phone is off hook and reconnect when it's idle. I'm a Tasker rookie, and I don't have a second phone to test with either, so I could be wrong.
Click to expand...
Click to collapse
Oh good. Yes I can see now I had phone off hook wrong. I have plenty of Tasker profiles, but none on phone calls. Let me know if this works when you test it.
Pkt_Lnt said:
Oh good. Yes I can see now I had phone off hook wrong. I have plenty of Tasker profiles, but none on phone calls. Let me know if this works when you test it.
Click to expand...
Click to collapse
I added flash messages to my connect and disconnect tasks, dialed my Google Voice number, and the messages popped up on the screen properly. I'll have to wait for an actual call to be sure it really works.
Dear all,
I just install catlog, launch it, bluetooth, the music app and after a few moment : disconneting like always.