Infeasible
Status Update
Comments
ra...@google.com <ra...@google.com> #2
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!
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!
le...@google.com <le...@google.com>
le...@google.com <le...@google.com>
ds...@google.com <ds...@google.com> #3
Just tested this on Nexus 4 with Android 4.3. onCellInfoChanged is called with null parameter.
Description
First, please search through existing issues to ensure that the bug has not already been reported. You can start the search here:
If the issue has already been reported, you can click the star next to the issue number to subscribe and receive updates. We prioritize responding to the issues with the most stars. You can also comment on the issue to provide any details of your experience with it.
If your issue has not been reported, please provide all of the following:
-----------------------------------------------------------------------------------------------------------------------------
A short description of the issue:
A small code sample that reliably reproduces the issue. The sample should run as-is or with minimal setup, without external dependencies.
What steps will reproduce the problem?
1.
When I type a name in create topics api, if the last character is a spacing character (' ') , a topic is created that cannot be used in the classroom.
=> I think team Google needs to apply trim() to name of create topics api.
2.
3.
What is the expected output? What do you see instead? If you see error messages, please provide them.
Please provide any additional information below, such as number of users impacted, IDs, or whether you have been able to find a workaround.