API 17 onCellInfoChange not updated and only called once with null list. [36964819]

Obsolete

Bug

Status Update

No update yet.

Description

da...@gmail.com

created issue #1

Jan 29, 2013 02:16PM

The PhoneStateListener onCellInfoChanged never returns cell info values. (The onCellLocationChanged returns values that differ when airplane mode is toggled, but not onCellInfoChanged is only called once at registration and returns a null List of CellInfo's)

Tested on Android 4.2.1 on Galaxy Nexus and Android 4.2.1 on Nexus 4.

Sample application attached, output from the Nexus 4:

01-25 19:04:31.516 D/CellInfoTest( 7999): Starting service
01-25 19:04:31.526 D/CellInfoTest( 7999): Service onCreate
01-25 19:04:31.526 D/CellInfoTest( 7999): Service onStartCommand
01-25 19:04:31.536 D/CellInfoTest( 7999): onCellLocationChanged called
01-25 19:04:31.536 D/CellInfoTest( 7999): dumpCellLocation:[10989,194036662,418]
01-25 19:04:31.536 D/CellInfoTest( 7999): onCellInfoChanged called
01-25 19:04:31.536 D/CellInfoTest( 7999): Null pointer for CellInfo
01-25 19:04:58.935 D/CellInfoTest( 7999): onCellLocationChanged called
01-25 19:04:58.935 D/CellInfoTest( 7999): dumpCellLocation:[10989,-1,418]
01-25 19:04:59.826 D/CellInfoTest( 7999): onCellLocationChanged called
01-25 19:04:59.826 D/CellInfoTest( 7999): dumpCellLocation:[-1,-1,-1]
01-25 19:04:59.956 D/CellInfoTest( 7999): onCellLocationChanged called
01-25 19:04:59.966 D/CellInfoTest( 7999): dumpCellLocation:[-1,-1,0]
01-25 19:05:00.857 D/CellInfoTest( 7999): onCellLocationChanged called
01-25 19:05:00.857 D/CellInfoTest( 7999): dumpCellLocation:[10989,194036662,418]

and from the Galaxy Nexus:

01-25 19:04:31.516 D/CellInfoTest( 7999): Starting service
01-25 19:04:31.526 D/CellInfoTest( 7999): Service onCreate
01-25 19:04:31.526 D/CellInfoTest( 7999): Service onStartCommand
01-25 19:04:31.536 D/CellInfoTest( 7999): onCellLocationChanged called
01-25 19:04:31.536 D/CellInfoTest( 7999): dumpCellLocation:[10989,194036662,418]
01-25 19:04:31.536 D/CellInfoTest( 7999): onCellInfoChanged called
01-25 19:04:31.536 D/CellInfoTest( 7999): Null pointer for CellInfo
01-25 19:04:58.935 D/CellInfoTest( 7999): onCellLocationChanged called
01-25 19:04:58.935 D/CellInfoTest( 7999): dumpCellLocation:[10989,-1,418]
01-25 19:04:59.826 D/CellInfoTest( 7999): onCellLocationChanged called
01-25 19:04:59.826 D/CellInfoTest( 7999): dumpCellLocation:[-1,-1,-1]
01-25 19:04:59.956 D/CellInfoTest( 7999): onCellLocationChanged called
01-25 19:04:59.966 D/CellInfoTest( 7999): dumpCellLocation:[-1,-1,0]
01-25 19:05:00.857 D/CellInfoTest( 7999): onCellLocationChanged called
01-25 19:05:00.857 D/CellInfoTest( 7999): dumpCellLocation:[10989,194036662,418]

The expectation is that if the device has enough information that onCellLocationChanged is called, a List containing at the very least the CellInfo for the connected tower should be returned.

deleted

Restricted

0 B

Comments

to...@gmail.com <to...@gmail.com> #2Sep 20, 2013 09:29AM

This was reported eight months ago. Is this going to be fixed anytime soon?

LTE cell measurements seem to be officially supported only via this interface (i.e. the old TelephonyManager.getCellLocation() can not be used for LTE since it is specified to return null when in LTE network). Thus it is important that this new interface works!

ju...@gmail.com <ju...@gmail.com> #3Sep 20, 2013 12:54PM

Just tested this on Nexus 4 with Android 4.3. onCellInfoChanged is called with null parameter.

bk...@gmail.com <bk...@gmail.com> #4Oct 12, 2013 03:18PM

How can we raise the priority of this issue? This should be fixed as soon as possible to give android a usable telephony API!

/ Kenneth

sa...@gmail.com <sa...@gmail.com> #5Oct 25, 2013 06:05AM

Hi, same thing in Nexus 7 (ME571-LTE). Tell ASUS to fix the problem. Galaxy S4 works just fine.

da...@gmail.com <da...@gmail.com> #6Oct 25, 2013 01:48PM

The reason the bug is here (and not on some ASUS forum) is that (in theory) Google has a compatibility test suite that tests the public API, and won't provide the Google apps (like Google Play) if the device fails that test (and you'd hope that their flagship device, the Nexus 4 would implement their documented public API.)

If there were an alternate public API that provided the LTE info, or the Google developer devices implemented the public API as documented and some OEM blew it, it wouldn't matter so much.

While fixing this on individual devices is good, what really needs to happen in addition to that, is an update to the CTS to test CellInfo and actually require that devices pass that part of the CTS and implement the API before getting the Google apps.

sa...@gmail.com <sa...@gmail.com> #7Nov 13, 2013 07:56PM

I tried below work around and it looks working
1. list to LISTEN_SIGNAL_STRENGTHS event telephonyManager.listen(phoneCallsListener,PhoneStateListener.LISTEN_SIGNAL_STRENGTHS)
2. onSignalStrengthsChanged call telephonyManager.getAllCellInfo(). Returns values are not null. But I am not sure that returned values are correct or not yet.

iv...@gmail.com <iv...@gmail.com> #8Dec 1, 2013 09:23PM

I've noticed something quite strange on the Nexus 5 (4.4). On Sprint LTE, it will return data for this. However, for a 3G provider (haven't tried LTE), it will return null.

ls...@gmail.com <ls...@gmail.com> #9Mar 1, 2014 02:47PM

[Comment deleted]

da...@gmail.com <da...@gmail.com> #10Dec 11, 2014 07:05PM

http://stackoverflow.com/questions/21251943/phonestatelistener-what-can-i-expect-from-oncellinfochanged

Suggests doing a hack with TelephonyManager.getAllCellInfo and onSignalStrengthsChanged.

en...@google.com <en...@google.com> Dec 13, 2014 06:56AM

Status: Won't Fix (Obsolete)

ol...@rosello.eu <ol...@rosello.eu> #11Dec 15, 2014 10:02AM

Why is this obsolete ? Is this method obsolete in the API ?

mt...@gmail.com <mt...@gmail.com> #12Apr 30, 2015 08:59AM

Nexus 5 LMY47D still same problem... onCellInfoChange gets called only once with null values even thus network cell that I'm connected to changes.

Workaround with using onSignalStrengthsChanged instead works fine but it is too frequent for my needs - battery drain for user.

gk...@android.com <gk...@android.com> #13Apr 30, 2015 03:30PM

Please file a new issue, thanks

da...@gmail.com <da...@gmail.com> #14Apr 30, 2015 04:03PM

As per previous comment by project member:

https://code.google.com/p/android/issues/detail?id=170806&thanks=170806&ts=1430409684

I invite all 41 folks that starred this issue to go star the new issue as well.

I have a number of other issues closed as "Obsolete" that are still failing, should I be just duplicating them as well?

da...@gmail.com <da...@gmail.com> #15Apr 30, 2015 05:59PM

Since they are just closing anything that references old version numbers as Obsolete and not actually testing if the failure persists, I've reopened the ticket with sample code at:

https://code.google.com/p/android/issues/detail?id=170816&thanks=170816&ts=1430416733

sh...@gmail.com <sh...@gmail.com> #16Oct 13, 2015 10:15AM

Me also getting null values for all kitkat versions,please let me know the possible cause for this