Related
Thanks to guest/Bad we have a solution :
* Call someone.
* turn back clock as many hours as the outgoing counter
* hang up
* Let someone call you
* turn back clock as many hours as incoming counter
* hang up
don't overturn, because it will cause the counter to be in the millions.
THis solution is so easy, nobody figured it out until now :lol:
M4io,
thanks but can you explain more how to do that, i'm little confused with steps!!
Thanks
I think somebody knows but they do not want to share us. M4io
I tested so many times, because I made overturn, million hours
And now it's so easy M4io?
reset for dummies (just an expression, nothing personal) :
tap on the Flag (left top corner)
tap settings
tap the tab System (in the botttom)
tap Device information
tap the tab Call duration (in the bottom)
write down incoming and outgoing
for example :
incoming = 48hr 27 min. 55 sec
outgoing = 14r 57 min 01 sec
Outgoing reset :
Call someone, (with the phone, not with your voice).
While the conversation is ongoing :
tap on the Flag (left top corner)
tap settings
tap the tab system
tap clock & alarms
tap the tab Time
change the Time
for example
if it is 15:37 18/01/2005
change it -14hr 57min 01 sec (outgoing)
to 00:41 18/01/2005
tap OK (right top corner)
end the conversation/ hang up the phone.
Set your clock back to reality
incoming reset :
let someone call you.
While the conversation is ongoing :
tap on the Flag (left top corner)
tap settings
tap the tab system
tap clock & alarms
tap the tab Time
change the Time
if it is 15:37 18/01/2005
change -48hr 27 min. 55 sec (incoming)
to 15:10 16/01/2005
tap OK (right top corner)
end the conversation/ hang up the phone.
Set your clock back to reality
you are the best man it really rocks man thanks a lot really looking for it from a long time. thanks man really a very very nice post simply i can say the best one till date.
thanks very much
jeet
What if the counter is on something like 165247hr15min30sec ???
elio said:
What if the counter is on something like 165247hr15min30sec ???
Click to expand...
Click to collapse
Just change the date/time back to what was before. It will revert back to your original counter value.
No u don't get me, I mean for some odd reason, without any manipulation from my part, the counter has jumped to such crazy figures. So I guess this elegant way to reset won't work in such a case?
elio said:
What if the counter is on something like 165247hr15min30sec ???
Click to expand...
Click to collapse
you could try to turn back 18 years
I don't know when it overflows , but you could try to turn forward.
short explanation : small negative display as large positive numbers if you handle it as unsigned field.
so it could be that
165247hr15min30sec is something like -1hr00min00sec
so you could solve it by turning the time forward 1 hour.
if anyone knows approxemately what -00hr00min01sec is you could calculate how much to turn forward.
ANYONE ?
The only time I have seen such high numbers for calls is on a brand new phone, once a call is made it resets.
maybe your counters were very close to zero point and by using it went from negative to positive?
oldest virtual xda phone user
In fact there's been quite a few reports on such odd counter behavior. Best solution in my opinion is to use a third party software and forget about the built in counter.
Meanwhile we could launch a contest for the "oldest virtual xda phone user" ) But screen captures are required!!
cool but have you tried reseting the "all calls" from the call timers?
(phone/call history/tools/call timers)
Thanks to Bonzo
I think the zero point is :
1193046 hr 28 min 16 sec
thus if your counter is closer to this, than to 0, It is easier to turn time forward going over 1193046 hr 28 min 16 sec. This should give you a very small calling time.
Wohoo! I got mentioned!
Sweet! :lol:
thanks to M4IO
problem with Magneto
For the those who are using WM5.0/Magneto, both INCOMING and OUTGOING call duration are set to "Unknown".
I guess this solution is not compatible with WM5.0 (as of May 20 2005 version 1. 50f.blWWE)
Re: problem with Magneto
steelorange said:
For the those who are using WM5.0/Magneto, both INCOMING and OUTGOING call duration are set to "Unknown".
I guess this solution is not compatible with WM5.0 (as of May 20 2005 version 1. 50f.blWWE)
Click to expand...
Click to collapse
My Call Duration still showing hour (not Unknown). I use WM2005 with the latest RAM upgrade.
Re: problem with Magneto
istana_pulau_es said:
My Call Duration still showing hour (not Unknown). I use WM2005 with the latest RAM upgrade.
Click to expand...
Click to collapse
May i know your ROM Version? (Settings>System Tab>Device Information)
Thanks
worked fine for me though my counter was 175???, had to devide this number by 24 then by 365 days to make how many years it was around 22 years of my total 27 years old on the phone gosh :shock: anyways went back to the 80's hanged went to real time vuala got it right
PS i have windows 2005 1.50h
"I CAN'T GET TO MY PHONE BEFORE IT GOES TO VOICEMAIL!" Sound familiar?
This thread is to discuss and discover/provide work-arounds (and potentally solutions) for the lag time between the initial ring from a caller and the incoming notifications on the android phone. Since there are other ways to make it possible to answer a call before it gets forwarded, other perspectives/ideas/questions/discussion are welcome here as well.
(Since I started the griping here I figure I better follow up.)
After a day or so of being opened, there are already several things we can do to help our phones ring faster posted in this thread. If something is confusing to you, please ask. If you click on the username of a post, you have the option to send a personal message. Unless you are darn sure other people have your question, please use this option. If it turns out your question would better suit this or any thread, you can paste your PM into the thread at any time.
I have to say this so I can rail on people: no matter how many Opening Posts say READ, READ, READ, the people who consistently don't read the thread haven't read the Opening Post, either. Don't be one of those people. The rest of us resent you for cluttering the thread, consequently creating even more clutter because there's too much crap for other people to read. We think you are being ignorant and selfish. This entire forum is public information; try to keep in mind your potential future boss might be checking this out to see how useful you might be in their workplace. So this, though probably not read by its intended audience, reserves for me the right to be even b****ier
In case anybody is inclined to test it, I already discovered that the phone doesn't ring when it's powered down....
The phone Prioritizer, combined with using ogg format, seems to do the best or me: I can't find it anywhere else. If I've posted this wrongly, please holler.
There was discussion going into the cupcake build about the latency increasing. I can't speculate on the cause of the latency, but it seems to have been going from the first OEM builds.
Delay in phone ring
Delayed phone ring (and even more delayed screen activation and caller ID) on incoming calls. Speaking for myself, callers hear a couple of rings before my ringtone starts to play. And there is another couple of seconds of delay beyond that before the screen lights up and the caller ID comes on.
I have been having this problem for the past, oh, ten or twenty updates. I have tried MANY things to fix it. If you hadn't already said that you always reinstall the radio when you flash, I was going to try that next in my quest for a solution. This ringtone delay problem is currently my number one irritation with my G1, and is at the TOP of my list of issues that I hope Cyanogen will address and conquer.
I have tried "renice -20" on the phone program, with no improvement. I have tried moving ringtones2SD from fat32, with no improvement. I have tried reformating all my custom ringtones as OGG, with no improvement. I have tried installing and uninstalling a variety of programs, with no improvement.
I am certain that Janis and I are not the only people with this problem. I have seen it mentioned by a lot of people in a variety of threads. I am glad to see a specific thread about this particular topicl If anyone has figured out a solution, please speak up. If no one has, perhaps reports from enough people will serve to convince developers to look into it more deeply. Anyone else have feedback?
I myself am curious to kno if there is any way to work on this. I have been a happy Rom switcher and each Rom has always given me 2 ring delays. The way I worked mine to get close to 1 ring is to constantly use a task killing APK, which I may add is tedious, and making sure I'm clocked 245min 584max
After I moved my ringtones from sdcard/audio/ringtones to sdcard/media/audio/ringtones a prescribed by Cyanogen when he originally took all the ringtones out, I had to re-pick my ringtone, as I would expect.
The odd thing is I also have to do it when I add (a) ringtone(s) to the folder or delete one or more. Can anyone shed any light for me on how the system/phone app references ringtones? Why would it lose a ringtone to reference just becuase I added one to the folder it's in?
How to test, or one way to do it
I use the home phone or skype, that way I can hear how many rings are actually happening for myself, count actual seconds (ear to the phone, eye on the clock), and I can see what order things happen. No one else,except you guys, has to bear with my hare-brained methods, either.
The last time I tested, the ring actually started before the caller ID popped up, but that was a first for me. Nothing happened until about the end of the second ring from the home phone.
Now I'm running Compcache 32mb, Linux partition swap 128mb, CPU 528/245.
Mines takes about a good 2 to 3 rings on the other side before my phones starts to even vibrate. Itfirst vibrates and then plays the ringtone.
Anyone remember before cupcake, when you got a call, even the call button wouldn't accept the call. Thankfully that's fixed but this still hasn't been fixed.
Mines takes about a good 2 to 3 rings on the other side before my phones starts to even vibrate. Itfirst vibrates and then plays the ringtone.
Anyone remember before cupcake, when you got a call, even the call button wouldn't accept the call. Thankfully that's fixed but this still hasn't been fixed.
I don't think you will get rid of the 2 rings on the other end before the phone rings. That is probably just the network finding your phone. However, I have had issues with my phone vibrating 2 or 3 times before the ringtone would start playing. I turned off vibrate and it helped. Then I turned it back on and disabled Missed Call. Now there is barely one vibrate before the ringtone starts playing. I'm turning off Missed call until they have an update for it.
I also found that the battery status widget causes a huge delay if you have it set to update as soon as it changes. It checks everytime the phone comes on and that slows things way down. I set it to update every 60 seconds and it still had some delay but not as much.
bout time
glad 2 see its not just me, i almost missed out on a job cause my phone will 'pause' so long it goes to voice mail b4 i can answer. seems like the issue comes and goes, but when its bad, its horrible, 1st it will vibrate for 2-5 sec b4 it rings , then its about 3 sec b4 the id info displays and when im lucky the call button wont react for like 4 or 5 pushes. sum times the phone app force closes, which means 15-30 sec wait while it reacquires the network and if it force closes the call doesnt show up in the call log.
iv had this issue with all the rom's and yes i reload the radio about 2 times a week, but even the stock 1.5 gives me the same issue
ok enough venting, any dev's that have might have an alpha or beta fix im willing to test!
SamCookD405 said:
glad 2 see its not just me, i almost missed out on a job cause my phone will 'pause' so long it goes to voice mail b4 i can answer. seems like the issue comes and goes, but when its bad, its horrible, 1st it will vibrate for 2-5 sec b4 it rings , then its about 3 sec b4 the id info displays and when im lucky the call button wont react for like 4 or 5 pushes. sum times the phone app force closes, which means 15-30 sec wait while it reacquires the network and if it force closes the call doesnt show up in the call log.
iv had this issue with all the rom's and yes i reload the radio about 2 times a week, but even the stock 1.5 gives me the same issue
ok enough venting, any dev's that have might have an alpha or beta fix im willing to test!
Click to expand...
Click to collapse
This isn't a ROM problem, it is a phone resources problem. There is something dragging your phone down. It might be different for each one of us having issues.
Ditching userinint.sh
I rm'ed user.conf and userinit.sh to use Cyanogen's default compcache and default CPU scaling. I re-downloaded Swapper and set up to use my 128mb (overkill) linux partition.
I got lights & vibrate at the end of the first ring, I got caller ID and ring just about halfway into the second ring.
Using the attached user.conf I didn't get ring or caller ID until the end of the second ring, sometimes after.
So I installed missed call (donation) and maxed it out. No change. Still getting first response at the end of the first ring, and ring and caller ID about 1/2 way into the second ring.
Maxed out my CPU at 528/528 with SetCPU. Got about .1 of a second advance. It starts to ring and gave me caller ID about 1/4-1/3 of the way into the second ring. Hard to tell, but a bit earlier than 1/2. The second and third time I tried it, it wasn't as fast. Caller ID came up just barely into the 2nd ring, but ring didn't start until the end.
I think the first ring is network time. For the duration of it, I'm guessing, the call isn't at my G1 yet. This sucks.
I think the phone app is set to vibrate and light the phone first, and leaves time for this to happen. It may be because it's the fastest way to alert the user, since looking for ringtone, handling it and sending it can (doesn't always) take some time, it just uses the reliable method and then triggers the less reliable, already slower ring process.
So maybe Cyanogen, or anyone who's familiar with it, can see if this ring vs. vibrate lag can be eliminated. I'd rather have the phone look for a ring first.
But, if you need to get to calls that quickly, set it to vibrate for now?
I downloaded the ogg ring package from the custom userinit thread. Trying that next.
This doesn't contribute anything to the thread at all (except maybe encouragement) but I'm glad someone is bringing this annoying "feature" up for public discussion.
I keep myself updated with CM and kspec oreo as a theme. As it is right now, I get one ring and the call goes to voicemail. The caller ID display actually lights up after the call has been forwarded. Hope the culprit (if there is just one) is found soon.
There has been a parameter on some of my previous phones called slot index. It was available through a keypad menu, it set how often the phone polled the tower. It sped up the ring responce dramatically.
Tried the ogg files, woohoo!
I've got my CPU set to 528/384 with SetCPU, Linux partition swap 128mb with Swapper (I can set them on the fly without rebooting), and used the ogg files in media/audio/ringtones, and I get ring and caller ID at or before the beginning of the second ring, a split second after the vibrate started. I tried messing with CPU speeds, and it does seem to make a difference as to when the ring actually sounds. I'd say about 1/2 a ring between 245 idle and 528 idle with 528 max for both.
I also have my frequency scaling at 16. So I think that means if 16% of my CPU power is being used, it hops it up from min to max. OK, maybe not 16%, I don't know how the numbers translate, but 16 is low, so I'm running at 528 when a squirrel farts outside.
I have BatteryLife and Missed Call enabled.
So there's the pause after the first ring to deal with, but I really don't think it's the phone after this. maybe we need to join forces and barrage T-mobile with complaints. I mean, why have the ringing on the calling end start if the network isn't connected?
Well, at least we won't ever have to worry about appearing too desperate.
2 or 3 bars, so my signal isn't that great. I'm in the suburbs (not that I love it, but it's where I am).
I'd be very curious to find out if others who have their CPUs running high and are using ogg files are getting a different response. I'm also going to try it in different locations.
I am going to suggest to Cyanogen to include the ogg fles as part of his add-on collection.
Face of Ring
I think I may uninstall this, even though I love it. It bumped the ring to after the caller ID. Caller ID still popped up during the pause after the first ring, but the ring and vibrate didn't happen until mid 2nd ring.
(I'm using rings to measure because 1. it's easier 2. the rings/pauses are shorter than a second 3. in large part it's the caller experience we're concerned about. I don't have a stellar chronometer handy, either.)
Well, thanks for starting this thread, Janis. It's a common complaint across all builds. I've grudgingly resorted to calling my phone after every reboot, just to try to keep the ringtone and I'm guessing Phone.apk?? in memory for as long as it will stay in there. That definitely helps for awhile. I know we're trying to make these phones more into computers, but they're still phones and as such calling and communications should be the main priority. I've converted to .ogg, however they are larger files than the .mp3's I converted from. Maybe I should have used a smaller bitrate. Anyhow, it doesn't seem to make much of a difference. I've tried placing them in /sdcard/media/audio/* and /system/sd/media/audio/*. Does not seem to make much of a difference.
I want a hardware hack to increase the RAM...I hate the trade off we're facing. Losing physical keyboard to obtain greater memory. Or make a "Dream plus" with more RAM. I'd even be happy with just a slight increase in internal storage or none at all and more RAM. The devs here have done wonders with the hardware provided, and the implementation of apps to sd has really made this seemingly poor thought out device (in areas), one of the best. I remember, before I was brave enough to attempt apps to sd, having to decide which app to uninstall, just to make room for one I might want more. Seems like ages ago. While I'm reminiscing, I'd like to give a retro shout-out to Lucid and MarcusMaximus who were pioneers in this area and others.
Sorry, about the tangent...but we've made great strides on the computer end of this device...let's regress, so to speak, and make the phone the primary function, hopefully without backsliding on progress we've made on our phones as a mobile computing device.
EDIT: I've also uninstalled "AutoLock" for this reason, because I'd read somewhere that this may be the culprit...I may have seen positive results, or possibly just placebo.
I have the app "Caller Lookup" installed and have noticed tha that app comes up before caller id and or the ringtone. Its there after 1 or 2 vibrate pulses.
make sure T-mobile, or whomever, has your time-before-forwarding maxed
My poor 74-year-old mom was having a heckuva time getting to her phone in time. As per the instructions from a Tmobile service rep, we punched a # and some digits and got a 65 second ring time. This was a year ago or so. I was told that same week that if my OS on my WinMo phone couldn't do it, there was no way they could (there's a way to set it in WinMo), which was BS.
I know it takes network time/space/bandwidth to let it ring, and it's not paid time. I wonder, not to be a rabble rouser (heh), if we kept calling them, maybe hundreds of us if we could get it going, and made them spend more money on customer service than that bandwidth, if they'd bump that.
Anyone?
PLEASE SUBSCRIBE TO THIS THREAD (in thread tools above) TO KEEP UP MOMENTUM! LET'S GET THIS DONE!
I had a PM from the user aelsharawi recently, who asked me to update the ‘locate my phone’ profile on the Tasker wiki. Never one to step away from a challenge, I started pondering and then pondered a little further and decided that this is something I really need community input on to plan and construct.
Losing your device feels like losing a limb or a close family member and instead of sitting by the home phone (if anyone still uses one!) waiting for the police to call to say they have recovered it, wouldn’t it be better to know that you can still control it remotely and in the mean time it’s working hard to return itself to you, like a little, lost, soft, cuddly puppy… Ok then…
Even if you don’t yet use Tasker, please do contribute and tell me what you would like your device to do! Grab your free trial from here
Continue to read for my initial ideas and the up-to-date community input!
------------------------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------
Whilst pondering, I realised that should you be separated from your device, you may not always want to take the same action.
For example, if you know you’ve just left it on your seat on the train that is chugging out of the station, requesting Tasker to wipe all of your data and massively overclock the CPU so much that it sets on fire, probably isn’t what you’re after. Alerting a nearby passenger that it’s been left and a small reward is on offer for its safe return, would perhaps increase your chances of seeing it again.
Alternatively, if you’re pretty sure your device has just been swiped, a polite message of pretty please return me, hoping to play on the conscience of a thief, may not do the trick. A sleuth mode would be more appropriate here, where the device starts to mimic being asleep/off whilst all the time updating you of its location amongst other things.
Different eventualities such as the above made me realise I would need more than one profile for this, perhaps even a precautionary profile, so if I knew I was going out to get completely wasted, I could set the device to check it was still in my possession at regular intervals!
Anyway, you get the general idea… on to my list of what Tasker could theoretically do to help:
1) Play very loud music
2) Display a message of death threats
3) Display a nice message
4) Display a reward message
5) Display a current location message
6) Speak instructed text
7) Email/text location
8) Lock
9) Wipe
10) Encrypt
11) Mimic being off/dead
12) Partially disable
13) Disable all buttons
14) Brick
15) Change splash Screen (I think?)
16) Change Boot animation
17) Shine torch
18) Take a picture
19) Text/email that picture
20) Display that picture (!)
21) Bluetooth the picture to nearby devices
22) Bluetooth a file/message to nearby devices
23) Send call logs
24) Block calls
25) Send text logs
26) Make it call the local police station and then speak!
27) Turn on a nearby TV
28) Show pornography
So, the above are a load of possible things that popped into my head (and you can see I was running out of ideas near the end). I’m sure you can help me think of plenty more…?
Sadly, the one thing that isn’t possible is to make the device boot if it is off… Yes I know everyone’s Nokia could do this back in 1982, but sadly not our dear Androids…
Over to you folks, let me know your thoughts!
Please respect the forum rules and belittle other people’s ideas and opinions as much as possible. It’s so much more fun that way…
Just kidding!
Your ideas
29) Send voice recording
30) Video Call
31) Activate Mic (sleuth make/answer call)
32) Disable USB/recovery/fastboot (unlikely) - Anyone know if these can be disabled by deleting certain system files?
33) Request thief's personal info! (see #39)
34) React to movement
35) Set to speaker phone and make call
36) Request to insert charger!
37) Auto-dial a fake contact of very HOT girl and then activate forward facing camera!
38) Notify of new number is SIM is changed!
39) Fake 'initial Set-up' mini program, that Tasker will send out the input from <-- Volunteer to write this?!
40) Gestures active to tell when phone is tilted to take picture with rear camera (not a problem for front facing)
41) Mute camera sound and disable flash for sleuth mode
42) Everyone start posting pictures of HOT girls that we can use as the fake contact! (don't pretend you have real ones)
Example profile added to post #3 for ideas!
Sherlock droid!
Thanks for all of your encouragement and feedback so far, please keep it coming, it's the only way to get this right. The best ideas are often the most simple, so please do not be afraid to post. If anyone flames you, they'll be struck off my 'Tasker help list'!
V1 BETA Set-up (Of course completely open to change by your input)
There will be four contexts for you to activate:
SherlockGreen
Situation Example: Device left moments ago on a train or in a restaurant. Drastic action is not required. Hopeful of good and honest Samaritan retrieving device.
SherlockAmber
Situation Example: Honestly, I'm not sure! You tell me....
SherlockRed
Situation Example: Device has definitely been stolen. Voluntary recovery unlikely. Ultra sleuth recovery mode and potential device wipe/brick.
DrWatson
Situation Example: You've woken up still drunk. Can't remember anything (apart from your 'Sherlock Codes'!). Can't find your phone. It could just be under the sofa. Perform single adhoc actions such as manual loud tones and vibrates etc etc.
Work in Progress
Preparation
* Make sure GPS and Wifi are checked in Menu/Settings/Location & Security (Google tells us that in Gingerbread no additional resource is used)
* Download SherlockGreen.zip from post #3
* Create a folder: /sdcard/Tasker/Sherlock
* Use the tone in the .zip and drag into the /Sherlock folder or use and rename your own SherlockGreen.ogg (if using .mp3 change action #13 & #16 in the task SherlockGreen
* Copy any picture into the /Sherlock folder and rename SG-ContactWallpaper.jpg (adjust in above task, action #9 if necessary)
* For testing, enter your own number in:
SherlockGreen - Action #1, #7
SG-FoundOk - Action #4, #7
SG-FoundNo - Action #3
* For full testing, set networks to 2g only and data connection and wireless off.
Don't forget to run (by pressing 'test') SherlockVarClear first and then after each test you run.
Either press 'test' in SherlockGreen , press done and apply and return to the home screen or text yourself sherlockgreen123
SherlockGreen V1 BETA Explained
SherlockGreen V1
SherlockGreen
* Kicked off by received text from any number with content 'sherlockgreen123'
* First priority to alert your Sherlock contact(s) that you've lost your device and they need to be ready to let you know what information they receive.
* Switches on 3g preferred and data connection (if they were off) and uses them and GPS to get a location.
* Sends location via text to Sherlock Contact. Time out set to three minutes in case of no fix.
* Wallpaper changed to show number 'Samaritan' is to dial.
* Screen time out increased.
* Display Brightness increased.
* Alert sound kicks off x 2
* Speech alerts Samaritan to pick up your phone x 2
SG-FoundMenu
* Activated during the above
* Screen prompt to 'PRESS HERE'
* If pressed, SG-FoundOk kicked off
* If not pressed, SG-FoundNo kicked off
SG-FoundOk
* Stops alert and speech to prevent being off-putting!
* Sends SMS to confirm manual interaction with screen at SG-FoundMenu (Battery level added in V2)
* Speech thanking Samaritan
* Another GPS location sent by SMS
* Screen alert asking them to enter their number if they'd prefer.
* Wait task ticks down...
* If no Samaritan contact perform task XXXXX <-- next stage
SG-FoundNo
* Instructs to restart SherlockGreen
* IF created loop variable %SHERG is less than 4 (to limit repeats)
* Another GPS location sent by SMS (SherlockGreen will have already sent 3)
* Perform task XXXXX <--- Next stage
SherlockVarClear
* To clear the created variables for testing purposes.
Testing thoughts and requests
* A low resolution SG-ContactWallpaper.jpg is needed that fits above and below the menu task and is easy for us all to edit in basic 'paintshop' and the menu background too VOLUNTEER NEEDED!
* Should SherlockGreen allow the device to be unlocked and load up the dialler if Samaritan screen interaction is made in SG-foundMenu??
* Need the most alerting alert of alert tones evar! Upload your suggested tone in a .zip!
Sherlock Green V2?
(* Battery level added in V2
* Should the SMS volume be muted and notification switched off to avoid alerting 'thief'?)
Dr Watson V1 BETA
Preparation
* Make sure GPS and Wifi are checked in Menu/Settings/Location & Security (Google tells us that in Gingerbread no additional resource is used)
* Download DrWatson.zip from post #3
* Create a folder: /sdcard/Tasker/Watson
* Use the tone in the .zip and drag into the /Watson folder or use and rename your own drwalert.ogg (if using .mp3 change action #4 in the task DrWAlert
* For testing, enter your own number in:
DrWLocation - Action #6
* For full testing, set networks to 2g only and data connection and wireless off.
DrWatson V1 BETA Explained
DrW-PopUp
* Purpose - display received text content as a pop-up on the screen
* Activated by the receipt of an SMS (from any sender) containing the text 'drwpop'.
* Note: In the context it states 'drwpop*'. The '*' is a wild card, so Tasker will allow further body text to be included in the same SMS.
* SMS body text (%SMSRB) is split at '###' until '###'
* Your SMS must therefore be 'drwpop ###THIS WILL DISPLAY ON THE SCREEN###'
DrW-Alert
* Purpose - Vibrate, torch and sound for localised searching.
* Activated by the receipt of an SMS (from any sender) containing the text 'drwalert'.
* If Tasker is handing your notification sounds, a 5 second wait is required in action #1 to prevent the alert sound being killed.
DrW-Location
* Purpose - Adhoc location request
* Activated by the receipt of an SMS (from any sender) containing the text 'drwlocation'.
* GPS & NET locations sent with accuracy [V2 Google maps link with pointer sent for both].
* Battery status included.
DrW-Tasker
* Purpose - Populate the created variable %DRWVAR
* Activated by the receipt of an SMS (from any sender) containing the text 'drwtasker'.
* SMS body text (%SMSRB) is split at '###' until '###'
* Your SMS must therefore be 'drwtasker ###1###'
DrW-Var
* Purpose - Triggered when %DRWVAR is set to '1' to perform actions.
* Note: Actions are up to you. Examples included are to set profile status 'XX' to off and set profile status 'XX' to on. These actions could be to turn on battery saving profiles you have or to turn off battery intensive profiles or profiles you consider may conflict with future actions such as notification control or to cease data connectivity under certain conditions. Turning off the sms preview in the notification bar and silencing the sms notification would be an obvious choice.
Testing thoughts and requests
As a reminder, 'Dr Watson' is supposed to be when you're not certain where your device is and are not overly concerned. That said, the ad hoc functions may well be useful under 'Sherlock circumstances'.
It is theoretically possible (a statement used when I haven't quite fathomed out how yet!) using a combination of DrW-Tasker & DrWVar that you can request Tasker to SMS/e-mail you any requested variable. For example, if you populate a created variable %DRWVAR-REQUEST with the body text of '###%UPS###' - you could then request that another created variable is set to %DRWVAR-REQUEST (= %UPS) and an SMS is sent containing %DRWVAR-REQUEST-POPULATED which is %UPS! You therefore receive a text with 'up time in seconds...' You with me....
I'm starting to forget my 'codes' already!
----------------------------------------------------------------------
----------------------------------------------------------------------
Over to you for a while now folks. Please test and provide your complete feedback. All I've done so far can be deleted if you think it's heading in the wrong direction and I won't be bothered - let's get this right...
To help by searching this thread PLEASE ADD A TITLE TO YOUR POSTS detailing the task or context you are referring to - otherwise 'general suggestion' etc etc.
Please clearly document/explain any changes you suggest to the tasks/contexts in your posts using the 'copy to clipboard' in Tasker and then pasting here, with a .zip for good measure!
----------------------------------------------------------------------
----------------------------------------------------------------------
I WANT TO GET INVOLVED!! BUT WHAT SHALL I DO??? >>CLICK HERE<<
SEE THE 'HOW DO I BRICK MY PHONE?' THREAD >>HERE<<
Please feel free to post your ideas below!
Yes, we all know Seek Droid is an absolute bargain at $0.99 in the mean time...
SherlockGreen Installation Instructions
In menu options/profile data 'Import One Task':
SG-FoundMenu.tsk.xml
SG-FoundOk.tsk.xml
SG-FoundNo.tsk.xml
SherlockVarClear.tsk.xml
In menu options/profile data 'Import One Profile':
Sherlock-Green.prf.xml
Dr Watson Installation Instructions
In menu options/profile data 'Import One Profile':
DrW-Alert.prf.xml
DrW-PopUp.prf.xml
DrW-Location.prf.xml
DrW-Tasker.prf.xml
DrW-Var.prf.xml
The thanks meter lets me know I'm appreciated
I would enjoy having something like this that works reliably, definitely the things that have to be perfected are the locate, encrypt, backup, wipe, alert, custom message and lock-out features.. Everything else is just a great added bonus.
Maybe see if you can somehow activate the microphone to listen to nearby conversation, or cameras to see anything thats going on (hopefully its not just a pocket shot lol)
Sent from my rooted G2X
DrowsyMalice said:
I would enjoy having something like this that works reliably, definitely the things that have to be perfected are the locate, encrypt, backup, wipe, alert, custom message and lock-out features.. Everything else is just a great added bonus.
Click to expand...
Click to collapse
The basics could definitely be perfected...
Maybe see if you can somehow activate the microphone to listen to nearby conversation, or cameras to see anything thats going on (hopefully its not just a pocket shot lol)
Click to expand...
Click to collapse
I like it - start voice recorder for ten seconds - zip it up and email it... or just dial-out of course...
A pocket shot would be a little disappointing!
Keep the ideas coming....
Those are some pretty good bonuses. I think it would be cool to have the phone fake being bricked. Fully functional for the owner with remote password. However, phone will run a program in background for "brick" mode.
Display will be nothing but static, all buttons are disabled whilst sending its location, video and voice recordings to your pc.
Pulling the battery, trying to reboot into recovery or fast boot, or connection with usb will not work. All settings are initiated upon boot. Phone is "bricked" until you send the password via your pc.
I don't know if this would be possible, just a thought.
Rooted G2
lncoln said:
Those are some pretty good bonuses. I think it would be cool to have the phone fake being bricked. Fully functional for the owner with remote password. However, phone will run a program in background for "brick" mode.
Display will be nothing but static, all buttons are disabled whilst sending its location, video and voice recordings to your pc.
Pulling the battery, trying to reboot into recovery or fast boot, or connection with usb will not work. All settings are initiated upon boot. Phone is "bricked" until you send the password via your pc.
I don't know if this would be possible, just a thought.
Rooted G2
Click to expand...
Click to collapse
I'm sure we could achieve most of it with pooled knowledge...
'Brick mode' is really essential to allow the phone to keep communicating. Would need a silent, black splash and boot animation so if the device was rebooted it would still appear off... or perhaps a fake one that appears to show errors and say's 'powering off'...?
Recovery and Fastboot are completely separate - to my knowledge they can't be tampered with from the OS - Although maybe there are some essential system files they use that Tasker could delete? I'm really not knowledgeable enough about that...
How about preventing itself from being uninstalled. Perhaps by needing a password (or some other means) to continue with the uninstall.
Would it be possible to take a picture when movement is detected? and send this picture by email?
How about it setting itself to speaker phone and calling a selected contact who can instruct them on how to get the phone back to you.
...insert witty signature here.
And if that fails within a # of tries, emails location to you periodically.
...insert witty signature here.
baboonsRus said:
And if that fails within a # of tries, emails location to you periodically.
...insert witty signature here.
Click to expand...
Click to collapse
A fake brick option would be the best, coupled with sensor awareness for recovery.
For the fake brick, it think it would be best if the screen gets stuck at a battery low/please plugin your charger, so that the perp will always charge your phone for you if they wanna use it.
For the sensor awareness, taking a recording, as well as taking occasional videos would be nice, as well as GPS location data.
Tasker and other apps can't enable/disable GPS since 2.3.3, Google change the security restrictions, also Radio on/off is not possible. And yes, this sucks.
Still works on CM7 though
Found this thread through a post I made on another forum.
That's an awesome list, will have a go at implementing some of these to my setup.
edit: maybe after reboot (if a security flag has been activated) the 'lockscreen' can ask the guy to input his info (name/email..password?? lol) in order to use the phone, then obviously send those out.
suggestion:
- enable Taskers PW-protection
feedback:
- don't like: 2-5 (maybe display a sms-provided msg instead?), 27, 28
- like: 1, 6, 7, 8, 9, 10, 23
BTW: any good alarm sounds you guys can recommend? Looking for a nice loud one that'll be easy to hear when nearby
rjg0691 said:
How about preventing itself from being uninstalled. Perhaps by needing a password (or some other means) to continue with the uninstall.
Click to expand...
Click to collapse
If you're talking about Tasker itself, then it can already be password protected.
AntAreS24 said:
Would it be possible to take a picture when movement is detected?
and send this picture by email?
Click to expand...
Click to collapse
I'm not sure how to tap into the sensor controls, but enabling a number of Tasker gesture alerts that basically activate for any movement would do it. Tasker would only react to these gestures if it knew it was in 'slueth mode'.
baboonsRus said:
How about it setting itself to speaker phone and calling a selected contact who can instruct them on how to get the phone back to you. And if that fails within a # of tries, emails location to you periodically.
...insert witty signature here.
Click to expand...
Click to collapse
Both could work. If you've left it on a train for example, it would first text your chosen emergency contact telling him/her it's about to call them and to get ready to shout loud to see if someone hears...
sakai4eva said:
A fake brick option would be the best, coupled with sensor awareness for recovery.
For the fake brick, it think it would be best if the screen gets stuck at a battery low/please plugin your charger, so that the perp will always charge your phone for you if they wanna use it.
For the sensor awareness, taking a recording, as well as taking occasional videos would be nice, as well as GPS location data.
Click to expand...
Click to collapse
The ultimate goal would be to make the perp leave the phone 'awake' for as long as possile whilst fooling them into doing something like looking for a charger (that would be great if they kept charging it up!!) or following long winded instructions that they think will give them full use of the device, all the time keeping them unaware that they are being hunted down!
Furzbirre said:
Tasker and other apps can't enable/disable GPS since 2.3.3, Google change the security restrictions, also Radio on/off is not possible. And yes, this sucks.
Click to expand...
Click to collapse
lifelikelife said:
Still works on CM7 though
Click to expand...
Click to collapse
CM have indeed hacked this.
For other custom ROMs, Google will tell you that under settings/location and secuirty wifi and GPS should always be ticked and will use no extra resource until required. Alternatively, most Gingerbread ROMs have the the status bar power widget. I'm pretty sure this is controlled by a simple system file that Tasker could overwrite - further investigation needed.
lifelikelife said:
Found this thread through a post I made on another forum.
That's an awesome list, will have a go at implementing some of these to my setup.
edit: maybe after reboot (if a security flag has been activated) the 'lockscreen' can ask the guy to input his info (name/email..password?? lol) in order to use the phone, then obviously send those out.
Click to expand...
Click to collapse
Ha! We know there are some very dumb criminals around. It could be worth a shot!
XlAfbk said:
suggestion:
- enable Taskers PW-protection
feedback:
- don't like: 2-5 (maybe display a sms-provided msg instead?), 27, 28
- like: 1, 6, 7, 8, 9, 10, 23
BTW: any good alarm sounds you guys can recommend? Looking for a nice loud one that'll be
easy to hear when nearby
Click to expand...
Click to collapse
We'll make sure that these profiles are fully configurable for individual tastes - so if one users likes one idea and not another, they can easily adjust. I'm sure we'll get some volunteers on XDA to make us the custom bootanimations, splash screens, black wallpaper, fake wallpaper (with instructions on), images we can show on the screen (with fake instructions on) and sounds etc etc etc.
i think a good option would be to initate a fake phone call (activate ringer, stock Call Screen with picture of a really attractive girl) and have the caller name be something like, "the best hookup ever" so as the Thief looks at it--the Front Facing Camera option is enabled & takes a picture of the Thief.
this picture then gets automatically sent to a designated email.
just a thought.
project.in.process said:
i think a good option would be to initate a fake phone call (activate ringer, stock Call Screen with picture of a really attractive girl) and have the caller name be something like, "the best hookup ever" so as the Thief looks at it--the Front Facing Camera option is enabled & takes a picture of the Thief.
this picture then gets automatically sent to a designated email.
just a thought.
Click to expand...
Click to collapse
Ha! Classic... Love it If only I already had such a 'contact' in my phone...
I could do with a device with a forward facing camera too...
Whew god, first suggestion, kill that signature. Wow.
Anywho. I wrote something like this myself a while back, but it's not quite in good shape to share I don't think, I'd have to evaluate it.
Anywho, it watches for SMS or Email with keywords and does some action based on those keywords. Primary keyword is to send information, such as location, last call in, last call out, last sms in, last sms out, phone number, battery info, some misc other stuff I think, had to keep it at 140 for sms.
Also if the phone number changes, it sends the same info every 5 minutes to a predesignated SMS.
For email I had to write my own http mail relay since I could not figure out a way to send mail without some intermediate steps showing on the screen or needing to hit the Send button.. kinda defeats the purpose. So it just does a POST to my web server and it sends the email.
If nothing is written here yet and anyone is interested, I can do some clean up and post it. Although I'm pretty bad about getting it done, I still need to post some GPS Tracking tasks I wrote a while back for "TrackMe".. ahem.
Can we get it to mimic the initial android phone setup, the welcome to android screen, make them touch the android, then they input their info?
Sent from my VM670 using XDA App
Hi,
First I want to tell you, that I'm from Poland, so You will propably find large numbers of errors in this.
Please, imagine this situation written below:
One day Jaccob was on city centre with their friend. There were no signs of such an accident. Suddenly one of his friends fell to the ground. He hit hardly head and not only lost unconscious, but he stopped to breath. Jacob was panicked. He was remembering sth from first aid course lessons from his school, but he have trouble to do anything. He decided to call emergency - and what? He took his phone and was trying to call, but when he touched the telephone app, the phone freezed, and few seconds later he saw the booting screen. And second was passing. In about a 3 minutes he was able to do call. For luck, someone else called emergency earlier and friend of Jacob was saved by paramedics.
Click to expand...
Click to collapse
It's only a story, not true at all, but some day it can happen.
It's my big petition for all developers of phones and systems: Together - let's create a special mode, to able turn on the phone and make emergency call in shortest time.
For example: a special key sequence that will trigger emergency call menu on any phone and a special menu item in Recovery.
Sorry for my bad English. I believe that You will understand me.
The problem is that special mode or not the phone software has to be operating properly for the phone to make any sort of call - if it fails and has to restart when you want to make a call then you have to wait until the restart is completed - end of story (especially for friend of Jacob)..
Many modern phones already allow an emergency call to a pre-progammed number even if the phone is locked just by holding down a single key.
Jaccob could also have a heart attack when he's trying to make the call - or get hit by lightening - or fall into a sink hole.
Even a "dumb" phone can potentially fail.
What if Jaccob had been playing Angry Birds all day and drained his battery and found out his phone had no charge when he went to place a call ?
What if he dropped the phone and it broke or fell in a puddle ?
My phone reboots in less than 1 minute, it can make an emergency call from the lock screen, and I have never had it freeze. I don't think this is an issue. It's possible, sure (I've had other Android devices freeze - so I'm sure a phone could, too).
I'm not sure how much faster it could really be, even with some kind of stripped-down OS. Android is such a light system already. And who would develop and make sure this emergency OS worked for all phones, and make them compatible with so many ? How would the phone know to trigger it ?
Lots of modern phones don't even have full key-pads any more. The fastest way for me to get to the dialer would be to just hit the wake button and tap the "emergency call" button on the screen. Even if I had to unlock it, I would just put in my pattern and tap once the "phone" app's button. I tried it and even with having to close out of an app I had open, it took me five seconds to do all of that.
Other people have different phones, but all Android phones are fairly similar in those functions from what I know. I think they've done all they can to make it fast and easy to make a phone call in an emergency.
Heck, what if Jaccob was born in the 1920s and he didn't have a cell phone at all ? When I was a kid, cell-phones weren't yet completely common - we had to run inside to make an emergency call, or to the nearest open business or even pay-phone. It's great that cell-phones can connect people in times of need, and I think it's good to see how much they already do even if they're not infallible.
Honestly, in the situation described the "solution" for any day and age would be better CPR and emergency aid classes (although Hollywood movies are doing a decent job with this - they're not always right in their techniques, but people have saved lives because they imitated what they knew from watching CPR performed in countless films). You can't always rely on technology or someone coming to save you. What if they were somewhere with no phone reception to even make an emergency call ? Yes, the technology should be as reliable as possible and make emergency functions accessible, but there is only so much you can do. Electronic devices can and do fail. Systems crash, batteries die.
it already exists, its called 999. but if your phone is switched off or out of battery well then your out of luck. It would be easier to convice everyone to carry a back-up phone than do this kind of mod
My phone is randomly logging battery status. Sometimes every few seconds.
The log is always the same. Battery level greater than zero, with date and time stamp.
Sometimes it's a few seconds apart, sometimes it's a minute or two. Overnight it was exactly every 30 minutes. It's writing the log to a text file. It appears to have been doing this ever since I got the phone. Only yesterday, it just decided to start notifying me of this. An Office notificaation pops up with "Batterylog.txt is ready to download"
Every.
Freakin'.
Time.
Haven't figured out why or how to stop the logging, but turning off notifications for office at least stopped the annoying notifications.
I have an S22 Ultra, all stock and up to date. Any way to stop it?
Where is it logging it to? Can you share the file? I wonder if there is something in the header of the file
gmm6797 said:
Where is it logging it to? Can you share the file? I wonder if there is something in the header of the file
Click to expand...
Click to collapse
It's saving in Documents. This is everything it shows. i see no header info.
That doesnt help me help you. I have seen apps that log what they are doing, and with new Android permission rules, everything has to go into downloads... so that makes it even harder. I am at a loss with that info, sorry
gmm6797 said:
That doesnt help me help you. I have seen apps that log what they are doing, and with new Android permission rules, everything has to go into downloads... so that makes it even harder. I am at a loss with that info, sorry
Click to expand...
Click to collapse
Yeah. There just isn't a lot of info there. I was mostly curious as to why whatever it is feels the need to log the battery status every 30 minutes, and why the only info given is "battery level greater than zero". That's pretty obvious by the fact that the phone is on. I'm even more curious as to why, all of a sudden, it started sending me notifications for it. I haven't changed any settings in forever.
I'd like to know what app it is, but there is absolutely nothing to go on. The file size is up to 1.4 kb since 11/03 04:37. I wonder how long it will take to get to 1 GB.
I'm sure there has to be an explanation. One of your apps is doing it, just not sure how to figure out which one it is.
I agree. I'm sure you've thought of this but it might be time to uninstall your apps one at a time until you figure out which one is responsible for it.
pauper66 said:
It's saving in Documents. This is everything it shows. i see no header info.
Click to expand...
Click to collapse
go to developer options and see if you have accidentally enabled "system activity" recording or some other setting there etc ..
daitalos said:
go to developer options and see if you have accidentally enabled "system activity" recording or some other setting there etc this has-been happening since the day the phone went into service. I didn't go into developer options until some time after, but I did check that. And asany settings as I could possibly find.
Click to expand...
Click to collapse
dj24 said:
I agree. I'm sure you've thought of this but it might be time to uninstall your apps one at a time until you figure out which one is responsible for it.
Click to expand...
Click to collapse
That thought occurred to me, but I opted for planB instead. I ordered a Pixel 7 Pro last nigjt.
Not purely for this reason tho. Phone tookansty fall a couple months ago. Nickel size chunk of screen gone, and it hasn't been fully right since screen replacement. Something loose inside, among other things.