|
2012-03-06
, 17:51
|
Posts: 90 |
Thanked: 35 times |
Joined on Jan 2012
|
#102
|
The Following User Says Thank You to WhitP For This Useful Post: | ||
|
2012-03-07
, 03:15
|
Posts: 86 |
Thanked: 42 times |
Joined on Oct 2011
|
#103
|
Not done for Cell Ids, but similar "timeout" has been done to WLAN. I'll look into including it to CellID location for 1.5.0 or 1.6.0.
|
2012-03-07
, 08:14
|
Posts: 111 |
Thanked: 230 times |
Joined on Jul 2010
|
#104
|
|
2012-03-07
, 14:23
|
Posts: 4 |
Thanked: 2 times |
Joined on Mar 2012
|
#105
|
Did you see any calls in the call log, what I mean was the phone just silent? Just a word of warning about the rules as you described up there: setting cell id and WLAN to the same rule rarely makes sense. That kind of rule means both conditions must much, that you're in one of the specified Cell Ids AND you're connected to the specified WLAN. It's not that either of the conditions being true will make the rule active.
Anyway there's no way ProfileMatic can make your phone not receive calls (except by turning on flight mode, but uninstalling ProfileMatic would not resolve the issue in that case), so whatever it was I doubt it was caused by ProfileMatic. But if you can reproduce it and let me know the exact situation and what rules you had, I can try and reproduce it myself.
Anyway I will also be testing the power saving mode etc. more on my phone, but so far I have seen no problems.
|
2012-03-07
, 15:03
|
Posts: 9 |
Thanked: 7 times |
Joined on Jan 2012
|
#106
|
|
2012-03-07
, 16:03
|
Posts: 1,313 |
Thanked: 2,977 times |
Joined on Jun 2011
@ Finland
|
#107
|
The phone just went silent while on the caller side it kept ringing. Maybe this was caused by the conflict in my rules or possibly ProfileMatic conflict with other program, I'm not quite certain. But I can confirm that such silent behavior toward the incoming call was gone once I remove all rules and uninstall ProfileMatic.
Here are the 3 rules I added.
1. Home: All days 7:00-22:00, with cell id & WLAN SET (I also tried with only WLAN, it behaves the same), FB-Gtalk-Skype all OFF, power safe is OFF.
2. Outside: All days, 7:00-22:00, cell id NOT SET, WLAN NOT SET, only FB ON, power safe is OFF.
3. Night: All days, 22:00-7:00, cell id NOT SET, WLAN NOT SET, FB-GTalk-Skype all OFF, power safe is ON.
To my understanding, I also think that ProfileMatic rules should not block the incoming calls. But it happens and I really have no clue what is the cause of such behavior.
|
2012-03-07
, 16:07
|
Posts: 1,313 |
Thanked: 2,977 times |
Joined on Jun 2011
@ Finland
|
#108
|
I had similar issues. Sometimes I don't know which rule is active.
Is it possible to show the current active profile in the UI?
Furthermore, I second to have WLAN conditions based on visibility and not based on connection. Only with this it makes sense to set the availability e.g. SIP.
Missing feature 1.3 to 1.4:
I miss the switch to restore the BT setting like in other actions provided.
The Following User Says Thank You to ajalkane For This Useful Post: | ||
|
2012-03-07
, 17:51
|
Posts: 9 |
Thanked: 7 times |
Joined on Jan 2012
|
#110
|
Can you clarify a bit? I would imagine setting availability of SIP would make sense only when you're actually connected to the WLAN? Having it near-by but not connected would be no help with SIP connection.
I'm wary of adding support for near-by visible WLANs because that drains battery more due to polling.
The Following User Says Thank You to JLo For This Useful Post: | ||
My N9/N950 projects: