Related
I've been trying for quite a long time to make my LG KS20 show me the CellID of the tower it is currently connected to. There are so many applications around the net that claim to do that, but unfortunately all of them just return 0 as current CID. I tried making my own application using the RIL's RIL_GetCellTowerInfo but I also always get 0. I tried signing my app with a temporary certificate, and adding that certificate to the phone but I still get 0. I tried different mobile operators and the result is always the same... And yet, Google Maps can identify my location without a problem so it is doable! Does anybody have any idea how to do that? Please, help, I'm getting very desperate here
I tried to get the cellId for a long time, but I think that's there's something blocking it in the RIL, that's why we always get 0 from RIL_GetCellTowerInfo.
As for GMaps, it never found my position automatically using celltowerid. Are you sure your position detection is not based on ip address ?
If I remember well, there are multiple ways to get celltowerid : 2 of these ways are rilnotifycallback and rilresultcallback.
I found a software( can't remember its name sorry, but if you're trying to get cellid I bet you know it) that could test each mode (perhaps 5/6 different methods) to try to get cellId. I remember that the 2nd one (was it result or the notify callback?) kind of worked. You have to :
- launch the (notify or callback) test mode -> return value is 0 .
- Then disable phone driver (easiest way is to go to airplane mode), -> the cellId, displays erratic values (000000 or fffff or whatever there is in memory at this place)
- Then enable phone driver (by going back to normal mode) -> the cellId display is right for a few seconds (it matched the values returned by another phone I had) but isn't updated after that.
Don't know if it helps you, but that's as far as I went concerning cellid.
Thanks for the info. Well, I tried manually writing C# code for RIL. Of course GetCellTowerInfo didn't work so I tried with DevSpecific. I bruteforced all the possible commands of the type {i, 0, 0, 0} but none of them seemed to work. Almost all of them gave an error "not implemented" or a basic error. Only {16, 0, 0, 0} returns an array of 20 bytes, but no combination of those gives the LAC (which I have via MiCard) so there's no CellID as well (as far as I know it would usually return the LAC combined with CellID). So it's a dead-end. The only thing I could not get up and running was querying the GSM modem directly through a COM port. I found that the RIL COM port should be 1, but no matter which command I send it remains silent. I disabled all the security in my device (it was in tier one mode before that) and signed all my applications with a personal certificate, which I added to the trusted certificates on my KS20. That didn't help as well. I think it's simply not implemented in the firmware of the radio.
And about Google Maps, well I found out that I actually used it via WiFi when I tried. Firstly I thoght it got the CellID because my laptop was running on the same WiFi, but "My Location" via maps.google.com just showed an error, while it was correct on my cell phone, but when I tried it elswhere and via 3G today, it showed me an error "Your location is not available now".
To wrap it up, as Google haven't come up with idea how to get CellID, probably I won't be able as well. But the topic still remains open (and if I come across new ideas, I'll definately try them). So if somebody has any other idea, I would really appreciate if he would share it.
i develop a geo location application my windows mobile phone is htc fuze with windows mobile 6.5
I want only to show me, Longitude and Latitude but i can't
I build this kowor.com/version/Kataskopos.apk
this link contain tha source but maybe it's not correct
Does anyone have any idea ?
I coulndn't succeed in getting the Cell ID to LG KS20 so I migrated to Android.
Anyway, to show the longitude and latitude you need GPS. If you don't have one, you could use Cell ID but it will give you a big error (typically around 1.5 km) and you still need to send the Cell ID to a database online which will convert it to geo coordinates (databases like Open Cell ID).
Good luck!
I'm using aLogcat2.4 free from market. While I'm on DLXA2 stock rom.
I'm getting constant error showing these :
Code:
E/DataRouter( 128): smd_file_fd = 16 and external_file_fd = 27
E/DataRouter( 128): ==KDW(3)== smd_new_status = (356)
E/DataRouter( 128): ==KDW(4)== smd_new_status = (320)
E/DataRouter( 128): DCD pinstatus is ON
E/DataRouter( 128): +
E/DataRouter( 128): -
E/DataRouter( 128): fd is 23 Content read is USB Switch : PDA_AP
E/DataRouter( 128): length is 20
E/DataRouter( 128): Content of Buf
E/DataRouter( 128): DrReadUsbStatus File Open success
E/DataRouter( 128): DrReadUsbStatus 21 characters Buffer from USB file USB_STATE_NOTCONFIGUR
E/DataRouter( 128): DrReadUsbStatus returns false USB is offline
E/DataRouter( 128): DrReadUsbStatus returns false USB is offline
E/DataRouter( 128): Turn OFF the SMD DTR bit
These errors show almost every second. Is this normal?
Apart from reading the Logcat....have you noticed any problems on your device.....
such as Force Close by Apps, or random reboots, stuff like that??
Why are you running Logcat....what problem were you tracking down??
Sent from my GT-I8150 on Lanzarote Canary Vacation using Tapatalk
It's rather about battery life. I found out when nighttime standby, data disabled, no wifi, no bluetooth, no gps. battery drops 1% less then 1 hour, while I expect it would hold at least 2 hour. While browsing, I see some say they last 3-4 hour every 1%. Maybe there is something wrong with rom or maybe hardware (?)
Can you share if you are getting the same error in logcat?
I'm running DXLA2, even if I do factory reset, then install alogcat, the error is there.
I just now install cwm recovery, and ready to test other rom. if you are not getting the same error, can you share what rom you use?
Thanks.
Really friend....
I am getting constant DataRouter 129 errors
slightly different, but similar....
AFAIK.....
this is Android System checking the Status of USB connection status......
Just try connect your phone to PC/Laptop....
mount USB storage.....
then check do those errors still occur.....
I don't got no PC or Laptop in Vacation
I don't think this will affect Battery Stats!!!
Let us know results of log at with phone connected to PC...OK
Sent from my GT-I8150 on Lanzarote Canary Vacation using Tapatalk
irishpancake said:
Really friend....
I am getting constant DataRouter 129 errors
slightly different, but similar....
AFAIK.....
this is Android System checking the Status of USB connection status......
Just try connect your phone to PC/Laptop....
mount USB storage.....
then check do those errors still occur.....
I don't got no PC or Laptop in Vacation
I don't think this will affect Battery Stats!!!
Let us know results of log at with phone connected to PC...OK
Sent from my GT-I8150 on Lanzarote Canary Vacation using Tapatalk
Click to expand...
Click to collapse
Out of curiousity, I tried flash OKVFinal4 by kezra, same DataRouter error..
Tried kernel from cowithgun, same error.
Connecting to PC still show as error in logcat both with MTP or USB storage.
Maybe I just got a bad batch of battery..
I guess this is normal on galaxy W, then this assume solved. Thanks for the information..
Any news on this. I know it's and old thread, but it's the only one on internet.
I lost 10% in sleep mode in 6 hours because of this:
15:23:29.695 DataRouter( 1792)
DrReadUsbStatus returns false USB is offline
I have galaxy w, 2 sg2 and one s3, all have this error.
Our app reads Type 2 tags (NfcA, Ndef). During the testing we have been able to consistently reproduce a condition where the NFC stack becomes unresponsive to subsequent reads. To restore it, we go to Settings, cycle the NFC box (off->on).
Ways to reproduce: We are moving the tag along the reading area in constant slow motion. Most of the time the tag is not read at all and the familiar "bleh" sound is emitted, as expected. Within a minute or about 10 tries, we hear the "bleh" sound too but no more reading is possible.
We reproduced this problem with the stock 4.2.1 as well as cm nightly based on 4.2.1 with kernel version 3.4.5-g73335a3
Below is logcat snippet from the crash:
D/NativeNfcTag( 620): Connect to a tech with a different handle
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
E/NfcNciHal( 620): GKI_getbuf() unable to allocate buffer!!!!!
E/NfcNciHal( 620): Failed to allocate GKI buffer
E/USERIAL_LINUX( 620): userial_read_thread(): unable to get buffer from GKI p_buf = 0x0 poolid = 1
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
Any clues much appreciated.
debriter said:
Our app reads Type 2 tags (NfcA, Ndef). During the testing we have been able to consistently reproduce a condition where the NFC stack becomes unresponsive to subsequent reads. To restore it, we go to Settings, cycle the NFC box (off->on).
Ways to reproduce: We are moving the tag along the reading area in constant slow motion. Most of the time the tag is not read at all and the familiar "bleh" sound is emitted, as expected. Within a minute or about 10 tries, we hear the "bleh" sound too but no more reading is possible.
We reproduced this problem with the stock 4.2.1 as well as cm nightly based on 4.2.1 with kernel version 3.4.5-g73335a3
Below is logcat snippet from the crash:
D/NativeNfcTag( 620): Connect to a tech with a different handle
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
E/NfcNciHal( 620): GKI_getbuf() unable to allocate buffer!!!!!
E/NfcNciHal( 620): Failed to allocate GKI buffer
E/USERIAL_LINUX( 620): userial_read_thread(): unable to get buffer from GKI p_buf = 0x0 poolid = 1
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
Any clues much appreciated.
Click to expand...
Click to collapse
Do you know the specific IC used in the tag? I can't recreate this so far.
Additional info:
We run tests on two different ICs: NTAG203 (NXP) and Vera M1HW (Verayo) -- both crash Nexus 10 NFC fairly easily. Up to 10 attempts max. The key is not to expose the tag for long, but swing it instead "teasing" the reader.
We cannot reproduce this problem on Nexus 7 (4.2.1 OS, kernel 3.1.10-g72e6ca1). Despite hundreds of similar tests, we didn't hang the N7's NFC.
We reproduced this problem on two Nexus 10's (to make sure it wasn't a defective unit perhaps).
debriter said:
Additional info:
We run tests on two different ICs: NTAG203 (NXP) and Vera M1HW (Verayo) -- both crash Nexus 10 NFC fairly easily. Up to 10 attempts max. The key is not to expose the tag for long, but swing it instead "teasing" the reader.
We cannot reproduce this problem on Nexus 7 (4.2.1 OS, kernel 3.1.10-g72e6ca1). Despite hundreds of similar tests, we didn't hang the N7's NFC.
We reproduced this problem on two Nexus 10's (to make sure it wasn't a defective unit perhaps).
Click to expand...
Click to collapse
Yep, I think I could reproduce (sort of) the behavior, I tried it with a (NfcA, Ndef, Mifare classic) tag ... as mifare classic is not recognized by the nexus 10, it should be quite similar ....but i needed round about 20 taps...and it´s reproducible .
One strange thing, I also recognized, is that if no 3rd party App with the right tech filter is installed (or background filters disabled)... the nexus 10 will only give you the standard NFC FAILURE sound.
And finally, I think i found the solution .... at least in my case it crashes the receiving app / launcher ... I tried it with only NFC Retag installed as receiver and a new tag... so every scan showed up a "New Tag detected " dialog .... and after ~20 dialogs the app/ launcher hangs ....
after finding that, tried some other tags (with other tech) ... with the same result .... and i can confirm that the nexus 7 has no problems ... so I think (without a deep analysis), it´s some buffer overflow / memory leak within the nfcdispatcher / launcher....after that, the fix was easy 1 line of code within the app....and now everything works fine, no more crashes ... so if you use an dialog to start your app, it´s probably the same problem.
ascsa said:
1 line of code within the app....and now everything works fine, no more crashes ... so if you use an dialog to start your app, it´s probably the same problem.
Click to expand...
Click to collapse
Our activitity is fine -- the UI remains fully operational. The underlaying NFC stack is hosed and doesn't respond to any further contacts with tags. The only way to bring NFC back is to cycle the (system) NFC Settings. After that, the activity reads tags again, until another NFC crash and so on.
We aren't lunched through a dialog. The activity is started manually (not via AAR or blank tag).
AW: [Nexus 10] NFC stack dies after partial NFC-Tag read
debriter said:
Our activitity is fine -- the UI remains fully operational. The underlaying NFC stack is hosed and doesn't respond to any further contacts with tags. The only way to bring NFC back is to cycle the (system) NFC Settings. After that, the activity reads tags again, until another NFC crash and so on.
We aren't lunched through a dialog. The activity is started manually (not via AAR or blank tag).
Click to expand...
Click to collapse
Hmm then, I can't reproduce your error.... After changing the code, I could tap the tag a hundred times and every thing is fine....
Edit: Though about it, this sounds a little bit like the Nexus 10 NfcV issue (NFC stack relies on an optional command, and if this command is not implemented on the chip, the stack crashes immediately)... However seems that in your case something overflows... But as mentioned I could not reproduce it with my test tags...
Sent from my GT-I9300 using xda premium
same issue faced on samsung galaxy 4 for type b tags
ascsa said:
Yep, I think I could reproduce (sort of) the behavior, I tried it with a (NfcA, Ndef, Mifare classic) tag ... as mifare classic is not recognized by the nexus 10, it should be quite similar ....but i needed round about 20 taps...and it´s reproducible .
One strange thing, I also recognized, is that if no 3rd party App with the right tech filter is installed (or background filters disabled)... the nexus 10 will only give you the standard NFC FAILURE sound.
And finally, I think i found the solution .... at least in my case it crashes the receiving app / launcher ... I tried it with only NFC Retag installed as receiver and a new tag... so every scan showed up a "New Tag detected " dialog .... and after ~20 dialogs the app/ launcher hangs ....
after finding that, tried some other tags (with other tech) ... with the same result .... and i can confirm that the nexus 7 has no problems ... so I think (without a deep analysis), it´s some buffer overflow / memory leak within the nfcdispatcher / launcher....after that, the fix was easy 1 line of code within the app....and now everything works fine, no more crashes ... so if you use an dialog to start your app, it´s probably the same problem.
Click to expand...
Click to collapse
Dear Senior Member,
Can you suggest me that 1 line change.
Hi
From the description this looks like an RF stuck, If possible try to use a Field detector to check
Normally The NFC chip switch between poll phase and Listen phase, In the poll phase the chip is looking for a tag to activate and RF field is ON
in The listen phase the chip waits to be activated by something else(like a reader or another phone) and the RF field is OFF, so if you have a field detector the led should be bliking if everything is Okay. If the led is continuously on or off this mean that something is wrong at RF level.
This could be a firmware level issue, in that case you need to alert the chip maker so they can fix
jhonpaul2020 said:
Dear Senior Member,
Can you suggest me that 1 line change.
Click to expand...
Click to collapse
katongo said:
Hi
From the description this looks like an RF stuck, If possible try to use a Field detector to check
Normally The NFC chip switch between poll phase and Listen phase, In the poll phase the chip is looking for a tag to activate and RF field is ON
in The listen phase the chip waits to be activated by something else(like a reader or another phone) and the RF field is OFF, so if you have a field detector the led should be bliking if everything is Okay. If the led is continuously on or off this mean that something is wrong at RF level.
This could be a firmware level issue, in that case you need to alert the chip maker so they can fix
Click to expand...
Click to collapse
Hi guys, this thread and the issues described are 10+ month old ....the , at this time, new broadcom nfc stack had some issues, but most of the issues were resolved ....so I wouldn´t refer to this anymore.
NFC Issue with Note 3
ascsa said:
Hi guys, this thread and the issues described are 10+ month old ....the , at this time, new broadcom nfc stack had some issues, but most of the issues were resolved ....so I wouldn´t refer to this anymore.
Click to expand...
Click to collapse
Dear Senior Member,
The same issue is still there on Note 3 also with Android version 4.3
FIXED: Welp, nevermind, I think I figured out the problem. I went ahead and reflashed, everything was fine for the trouble apps until I went through and installed everything else and it went right back to breaking things. Started going through apps that have any sort of root or admin privileges, and it looks like Kasperky's Mobile Security app is the problem. Removed it on both Nexus 7 and SGS3 and they're both acting normal with WiFi.
This is a bit of a strange problem, and I'm hoping someone here can at least help point me in the right direction to figure out the cause.
Basically, when I pulled my Nexus 7 out of the box, everything was fine. Then I rooted it, and in the process it factory resets, so reinstalled all my apps. When setting everything back up, I noticed certain apps just cannot do anything through WiFi. Tumblr cannot log in, TorrentFu cannot connect to my linux box's transmission, WD 2Go can't log in to my WD Live NAS but eventually gets on for whatever reason, among other small problems.
Now, here's the strange bit. I have an identical problem with my Samsung GS3 running CyanogenMod 10.1.2, and I had this problem when using CM10.1 Milestones as well, but didn't with CM10. On the phone, if I disable WiFi and use the phone data everything logs in and acts like there's no problem. Turn wifi back on, and everything gets crappy.
Now, when I had this problem with just my SGS3 I thought little of it, just dealt with it. However, with the Nexus 7 2013 Wifi only, I can't really do that. On both devices, most things work just fine, like Plume, browser, etc. On the phone, sometimes it won't auto connect to Wifi, or Wifi gets ridiculously slow for the things that do normally work, but it's also easily avoided by just switching wifi off. I'm noticing it's doing the same things with the Wifi on the Nexus, and since it's my only outbound connection on the device, is making it useless while rooted in some cases.
I've been running adb logcat on it, trying to catch the specific calls or failure points. Here are some of few places I see network errors (had to edit to cut out a URL since I haven't posted here enough).
Code:
[ 07-28 12:41:13.035 22839:22855 W/GoogleAnalyticsTracker ]
Problem with socket or streams.
java.net.ConnectException: failed to connect to www[dot]google-analytics[dot]com/127.0.0.1 (port 80): connect failed: ECONNREFUSED (Connection refused)
at libcore.io.IoBridge.connect(IoBridge.java:114)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:192)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:459)
at java.net.Socket.connect(Socket.java:842)
at org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:119)
at com.google.android.apps.analytics.PipelinedRequester.maybeOpenConnection(Unknown Source)
at com.google.android.apps.analytics.PipelinedRequester.addRequest(Unknown Source)
at com.google.android.apps.analytics.NetworkDispatcher$DispatcherThread$AsyncDispatchTask.dispatchSomePendingHits(Unknown Source)
at com.google.android.apps.analytics.NetworkDispatcher$DispatcherThread$AsyncDispatchTask.run(Unknown Source)
at android.os.Handler.handleCallback(Handler.java:730)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:137)
at android.os.HandlerThread.run(HandlerThread.java:61)
Caused by: libcore.io.ErrnoException: connect failed: ECONNREFUSED (Connection refused)
at libcore.io.Posix.connect(Native Method)
at libcore.io.BlockGuardOs.connect(BlockGuardOs.java:85)
at libcore.io.IoBridge.connectErrno(IoBridge.java:127)
at libcore.io.IoBridge.connect(IoBridge.java:112)
... 12 more
[ 07-28 13:05:58.048 25336:26131 E/TumblrHTTPService ]
Error in sending post!
java.lang.IllegalArgumentException: The passed parameters were insufficient for the API call 'notifications'.
at com.tumblr.network.TumblrHTTPService.processIntent(TumblrHTTPService.java:453)
at com.tumblr.network.TumblrHTTPService.onHandleIntent(TumblrHTTPService.java:748)
at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:65)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.os.HandlerThread.run(HandlerThread.java:61)
[ 07-28 12:53:13.462 22334:24804 E/HttpTransaction ]
Unexpected exception
java.io.IOException: NetworkError
at com.google.android.gms.auth.GoogleAuthUtil.getToken(Unknown Source)
at com.google.android.gms.auth.GoogleAuthUtil.a(Unknown Source)
at com.google.android.gms.auth.GoogleAuthUtil.getTokenWithNotification(Unknown Source)
at om.google.android.apps.plus.api.ApiaryAuthDataFactory$ApiaryAuthDataImpl.getAuthToken$22670df9(ApiaryAuthDataFactory.java:142)
at com.google.android.apps.plus.api.ApiaryAuthDataFactory$ApiaryAuthDataImpl.getAuthToken(ApiaryAuthDataFactory.java:93)
at com.google.android.apps.plus.network.ApiaryHttpRequestConfiguration.getHeaders(ApiaryHttpRequestConfiguration.java:60)
at com.google.android.apps.plus.network.HttpOperationRequest.getHeaders(HttpOperationRequest.java:54)
at com.android.volley.toolbox.HttpClientStack.performRequest(HttpClientStack.java:80)
at com.android.volley.toolbox.BasicNetwork.performRequest(BasicNetwork.java:93)
at com.android.volley.NetworkDispatcher.run(NetworkDispatcher.java:95)
I've googled around for parts of this but of course found nothing.
Ultimately, what I KNOW is the common factor between the two devices is the list of apps I'm using (for the most part) and having been rooted. Different hardware, different AOSP ROMs (CM10.1 on the SGS3, Stock on the N7-2), different root methods, different recoveries (CWM on SGS3, TWRP on N7-2), pretty much anything I can think of except the apps I'm using and the fact that it's rooted. I've used rooted/ROM'd androids since my first (HTC Evo) but I've never really dived in much deeper than this in terms of finding actual problems.
Any help just pointing me in the direction for how to pinpoint what's going on would be greatly appreciated. I only know how to adb logcat, but I'm sure there's some other tricks to try. Considering the number of apps I use, it'll be pretty hard to just pull them off one by one, but I'm half way considering reflashing, rooting again, and just installing the problem apps first to eliminate outside apps...
Click to expand...
Click to collapse
Hey guys
Seeking for some help please. The following error started from nowhere
"AsyncSocketException: connect failed, type = Socket not open, errno = 103 (Software caused connection abort)"
1. I can't remember if it started after latest samsung software update or not
2. I don't even know which app causes this as I have SmartLife app due to my smart plugs (bakibo)
3. I have searched this and some people suggested clearing google services cache but it didn't work for me
4. It pops up everytime I unlock the screen as well as when I am using my phone. It's so often that it's driving me nuts lol
Any ideas at all?
Many thanks
same here ...
Hey
I found a solution in the end. Sockets only work on 2.4GHz and most of the WiFi are now 5GHz.
If you split your network thru your network app the error pop up will stop however once you use your phone data instead of WiFi the pop up will start again.
Luckily, my smart socket app had several updates and at the moment all good regardless.
ALWA7SH6 said:
same here ...
Click to expand...
Click to collapse
Hey
I found a solution in the end. Sockets only work on 2.4GHz and most of the WiFi are now 5GHz.
If you split your network thru your network app the error pop up will stop however once you use your phone data instead of WiFi the pop up will start again.
Luckily, my smart socket app had several updates and at the moment all good regardless.
Same here. Any solution?