I've seen numerous posts from people reporting in that the cell signal which I believe is %CELLSIG is not being reported correctly when on LTE. And this is not just CDMA phone but GSM as well.
--
You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/uDnxVh8Bqgo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tasker+un...@googlegroups.com.
Visit this group at http://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.
I would imagine that since I'm on a Nexus 5 KK 4.4.2 that I would have API-17 support.
--
That's great, thanks. How do I import that? I've tried as a tsk.xml and as a prf.xml but no joy...
Seems annoying that it has to be a battery-intensive looped task to monitor signal strength. I hope this will be fixed as there are a very large number of potential use-cases here...
Cheers for the task!
I can't get it to work unfortunately, it just flashes the name of the variable rather than any content (ie. "%dbm(1)" flashes up)
Mark
Clipboard :
%cell_list
Ah, thanks!
CellInfoWcdma:{mRegistered=YES mTimeStampType=oem_ril mTimeStamp=118521798243836ns CellIdentityWcdma:{ mMcc=234 mMnc=20 mLac=104 mCid=10451524 mPsc=415} CellSignalStrengthWcdma: ss=3 ber=99},CellInfoWcdma:{mRegistered=NO mTimeStampType=oem_ril mTimeStamp=118521798243836ns CellIdentityWcdma:{ mMcc=2147483647 mMnc=2147483647 mLac=2147483647 mCid=2147483647 mPsc=470} CellSignalStrengthWcdma: ss=0 ber=99}
Network is 3(uk), lte mostly.
I imported the task rather than typing it in. It appears to have parsed correctly...
Mark
You need to set the clipboard to %cell_list(). The parentheses have to be included.
What about the other questions?
On April 24, 2015 9:50:50 AM
Vick Lee <confu...@gmail.com> wrote:
> Since you have to use a context that checks every 2 minutes, how bad
is the
> battery drain?
"Efficient" was probably a poor choice of words. What I meant was that I couldn't find any way to keep cell signal strength updated except with a repeating time loop. Two minutes seems a long time between updates.
This is in contrast to wifi signal strength which can be updated, via an intent, as soon as it changes.
Sent with AquaMail for Android
http://www.aqua-mail.com
I abandoned it, as battery drain was worse than just allowing the phone to hunt for a signal in a no-signal workplace.
I ran it every 2 mins. If there was consistently bad signal (a signal strength derived from this thread of less than 15) for 10 mins a profile was activated that enables airplane mode-without wifi changes. Every 10 mins it checked a spot signal strength, with a reset - to-baseline if the signal had normalised, and a continuance in 10 mins checking if not.
On April 26, 2015 11:51:34 PM Vick Lee <confu...@gmail.com> wrote:
> Just curious why
Signal_Strength.tsk.xml used
> TelephoneManger.getAllCellInfo() then parsed text signal? Instead
couldn't
> CellSignalStrength.getDbm() be used?
That's what I originally
thought, but that method always returns -1 for LTE signals. Some
explanation for this can be found here: http://goo.gl/oXfXqA
The new update has broken the script posted above for me- is it working for anyone else? Cell_list is now empty and the task throws up errors...
Does anyone know if this is ever going to get fixed?