Related
I used to be able to simply turn off my Trinity to engage a PIN lock.
I want to be able to have the phone locked, once the screen is turned on again as oppose to a timely interval of x minutes (very annoying).
I cant seem to remember how I enabled this feature on my Trinity.
Any help?
Hi MrTW,
If I understood you correctly this should work?
1. Go to Start>Settings>Lock
2. Tick "Prompt if device is unused for"
3. Set the time option to 0 Minutes
That should do it - let me know how you get on.
Zippyioa
Hi zippyioa,
this is how it used to work on my Trinity. On the Tilt however it locks every 30 seconds or so and requires for me to enter the PIN (pretty annoying).
zippyioa said:
Hi MrTW,
If I understood you correctly this should work?
1. Go to Start>Settings>Lock
2. Tick "Prompt if device is unused for"
3. Set the time option to 0 Minutes
That should do it - let me know how you get on.
Zippyioa
Click to expand...
Click to collapse
Hi MrTW,
The instructions I gave you should set the phone to ask for a pin when you switch it on - isn't that what you wanted?
Zippyioa
yep, that is what it does essential. But on top of it the phone PIN locks each 30 seconds of none use.
I would like to have the phone PIN locked only when the screen is switched off; once the screen is on it shouldnt look.
I hope that makes sense.
Thanks for helping out!
zippyioa said:
Hi MrTW,
The instructions I gave you should set the phone to ask for a pin when you switch it on - isn't that what you wanted?
Zippyioa
Click to expand...
Click to collapse
MrTW said:
yep, that is what it does essential. But on top of it the phone PIN locks each 30 seconds of none use.
I would like to have the phone PIN locked only when the screen is switched off; once the screen is on it shouldnt look.
I hope that makes sense.
Thanks for helping out!
Click to expand...
Click to collapse
I get what you mean. You want the phone to ask for a PIN code when you switch it on, but you dont want it to ask you for a PIN code after x seconds of not using it.
I have searched for an answer but cant find one
You said you could do this on your Trinity - maybe it was available in WM5 but has been removed in WM6?
Any ideas anyone??
The other option you could try is to look at 3rd party software like this?
Let me know how you get on - this problem is bugging me now!!
Zippyioa
I had this too on my trin running WM6. I want it on the Kaiser ! I tried the 0 second thing, doesn't work right =(
My phone is policy locked by my corporate IT so I can't try this, but try setting the lock time and the auto-off time to the same value. Sounds like you already know where to find the lock time...the auto-off time is at Start->Settings->System Tab->Power->Advanced Tab.
Seems to me that if you set both to say 5 minutes, you're phone would stay on if you're using it and turn off after 5 minutes of inactivity. Since that is the same value as your lock time, it would be locked when you turned it back on.
Of course, the obvious trade-off here is battery life.
well, this solution also does not work.
The phone locks after 5 minutes (which makes sense, since I tell the phone to lock) but the phone does not ask for a PIN entry if i turn the screen back on again.
Its funny that this pretty important feature has been forgotten - time for someone to write a little program and earn a few bucks (I am the first to buy).
Thanks for all the help so far!
Fitipaldi1 said:
My phone is policy locked by my corporate IT so I can't try this, but try setting the lock time and the auto-off time to the same value. Sounds like you already know where to find the lock time...the auto-off time is at Start->Settings->System Tab->Power->Advanced Tab.
Seems to me that if you set both to say 5 minutes, you're phone would stay on if you're using it and turn off after 5 minutes of inactivity. Since that is the same value as your lock time, it would be locked when you turned it back on.
Of course, the obvious trade-off here is battery life.
Click to expand...
Click to collapse
Workaround
Hey, I've been looking for a solution to this for some time and I have finally figured out a way, to enable this feature. It's pretty ugly and I'm sure one of the gifted programmers out there could write a little program to do this all-in-one in no time, as mentioned above...! But anyway, here goes:
First of all, you need a program, that will allow you to call up the PIN lock functionality via a shortcut (alternatively, if you figure out where in the PPC file structure this command is hidden, this would work as well and possibly quicker). I use the freeware PocketToolman for this. Download here http://pockettoolman.blogspot.com/ and install. Then either: a) launch the program (which initially will only activate the tray icon), tap on the tray icon, go to settings - options and click through to the last page where you can find "Create PT Function shortcuts", tick the box saying PIN Lock and press OK or b) if you prefer creating shortcuts yourself, you can call the Toolman exe file using "/Lock" after the filepath (no inverted commas) and place this shortcut in a convenient place.
The second part of the solution, is to get a program, that allows you to manipulate notification queues. I personally use MemMaid (http://www.dinarsoft.com/memmaid/) which unfortunately is not freeware, but a lovely tool, worth paying for. The interesting thing is, that for the purpose of this exercise, you may be able to get away with using only the trial version. (There is the possibility, that there may be freeware out there, that can emulate this particular functionality, but frankly I couldn't be bothered to look, as it took me ages to figure this out as it is! ;-) ) Anyway, assuming you use MemMaid (and I would recommend you try it out using that, to see if it will work on your device as well...) you open it up and go to the 2nd tab at the bottom (at least for me, I'm using v2.0). That should take you into the notification queue. If not, then try the drop down menu at the top, to give you more options for that tab. Now you click on the "add" button and on the following screen click on the three dots next to program and choose either the automatically created shortcut from Toolman (should be in the Windows/Start Menu/Programs folder, may differ if you have a different native language) option a) or choose the shortcut you created yourself using option b) above. Now the final step is to change the event type from "Run at time" to "The device woke up". A click on add and then on OK and Voilà! You have a PPC that will no longer autolock when on, only when the device is woken up from suspension and on reboot or cold boot! Well, technically that's not quite true, a little thing I forgot and should've mentioned earlier: You need to turn the WM Lock on via settings-personal-lock for this all to work, as this method builds on WM resources and the setting to use for the time is of course 24h, as that is the longest available. So tecnically the other time you will be prompted for a password, is if you leave your device on (not suspended) and don't use it for 24h! For me at least, this is a relatively unrealistic scenario, as I really cannot see myself going 24h without my Uni! ;-) Hope this has helped you guys, btw if the need arises, I could translate all this into German if that would help anybody, I'm just too lazy to do so right now!
Ok known bug: It seems not to work the first time you suspend and reawaken the device after a reboot, but after that it works just fine.
i was sitting here on XDA and i saw that a user here had his phone stolen from him, and people posted several solutions like GPSTracker and latitude but the user did not have either installed. would anyone be interested in a remote brick? basically it would be like SMS commander, but you send a text that holds a password and the correct brick phrase and the phone will brick. the best(and worst) way i can see to do this would be to have an old radio on the sdcard and have the haykuro SPL on there as well. then when the phone receives the text it flashes the old radio and then the haykuro SPL which we all know would brick the phone. i am still working on possible implementation or another way of doing this(maybe run "wipe all" in terminal), but i was just wondering if anyone would be interested before i really try it out.
maybe in future if app works well our ROM devs could include in their build and then it couldn't be removed(easily). the main reason i would want something like this is so if my phone was stolen i could make it useless to the idiot that stole it.
few minor details that would need to be worked out:
won't work if SIM is changed as number would be different
if i use the terminal command "wipe all" then theif would only need to have a new ROM to install and it would be all better
on the of chance you get the phone back you would want to be able to easily fix the phone
let me know what you think, keep in mind this is a very early stage idea and i haven't put more than 20 minutes thought into it
cant lie the idea is brilliant but execution would be the make or break point, and i have a feelin this will take alot of test g1's to get working lol...and multiple devs as a team to get up off the ground. But im all for it, i have had bad luck in the past especially with sidekicks and etc and this would be a perfect idea to have.
Great idea but don't forget when restoring it (if you manage to retrieve your phone), it should only 'unlock' to a certain pass phrase pre-set by the user. If not anyone could just run the 'unlock' command to start using it again.
On the whole, a great idea.
However, I think flashing an incompatible theme with your current build would be sufficient, seeing as 99% of the people who go around stealing phones would have no idea how to fix a G1 stuck on the T-Mo/Not-Flashing-Android Screen.
Although the Old Radio+New SPL combo ensures that there will be minimal data retrieval, it also seems like overkill for the majority of circumstances, seeing as your phone would become a paperweight.
The terminal command "wipe all" will wipe the data and system partitions and crash the phone, when the person who stole it tries to reboot it it won't boot
Even if you wipe (or remove the SD card) most builds would still boot regardless. A remote kill switch has been around on many platforms for some time, hell even Microsoft have been threatening to use it on Vista for pirated builds but it has never happened.
In this case, perhaps the app would need root access, so it could remotely reboot the G1 and run a script to force a boot loop, if you wanted to go as far as rendering the mobile temp unusable.
However the G1 as it is has plenty of security flaws... I mean many of us managed to get root without issue and I'm sure any google searches will point them to this forum. There is no security for fastboot, nor accessing the recovery image so people can pretty much do as they please - If they know how.
Yeah, I don't know about bricking the phone because it would suck if eventually you did get it back. Then you're stuck with a brick phone maybe theres away around it though which could work not sure how you'd implement this though. I mean the idea is there just going to be abit hard to execute because the problem is with all these theft problems, if they have the phone off when the sms is sent then it doesn't work.
I wouldn't mind having this. If someone snatched my G1 out of my hands and got away, I would just use my friend's cell 1 minute later to make my phone a paper weight, then have peace of mind. lol
Dladu said:
Yeah, I don't know about bricking the phone because it would suck if eventually you did get it back. Then you're stuck with a brick phone maybe theres away around it though which could work not sure how you'd implement this though. I mean the idea is there just going to be abit hard to execute because the problem is with all these theft problems, if they have the phone off when the sms is sent then it doesn't work.
Click to expand...
Click to collapse
i am noting the issues, what i am planning is something similar to SMS commander, when the phone gets a text that says a certain thing it does something. if the phone is off then the text will still arrive when the phone is powered on, hell i could probably even remove the recovery screen and then the person would need to fastboot the phone.
sms commander just "listens" for the text of an incoming message and if it matches a certain phrase it runs a command. obviously i would need root, but at this point if you haven't rooted your phone this(if it works) woulud do it.
with that said, i am researching the APIs to see what would need to be done, i used to have something like this on my old 8525 and i never had to use it, but i'm paranoid about stuff like this
i love this idea, there was this time when i had sold my touch pro on craigslist but the buyer had ripped me off! so that just pissed me off!
(good name ideas)
Cold-Droid
Lock Me
Ban-Droid
Dream Lock
Use me...Not!
Where's My owner
or just a plain app called
"Brick"
This app would be cool if it detected the owners sim card so if it were ever replaced it would say wrong sim card enter passkey (which they will not know)
and if they were to ever put the sim card back in then still it will tell you(sim card has been removed please eneter passkey)
or something like that! just an idea!
kind of like sim lock but instead of sim being locked, the device will be locked!
Why you would want to destroy a phone?
Just remote wipe your data, thats enough. Write that as an app!
Not bricking!
Have you guys used/considered Mobile Defense?
So here is my idea for this application.
Instead of completely bricking the phone, make it so that if the SIM card is removed, or the secret SMS message is sent that it does a complete phone lock and displays a message on-screen stating "This phone is suspected to have been lost/stolen. Please call XXX number to return the property.". All the while sending precise GPS locations updated every x minutes to a preset Email address and/or send a SMS to a preset phone number. This way the real owner may be able to easily recover the phone and none of the information is exposed. The only way to unlock it is to put in a code to unlock it. After x amount of days without being recovered, the program will issue a recoverable brick all the while showing the same message. After x more days after the soft brick, the phone will format all ROM and be unrecoverable. By that time, the real owner would have already gotten his/her replacement G1 if they had insurance, and the thief will have a fancy paperweight.
Great idea
Is this going to get anywhere?
that'd be funny if you could lock the phone at a screen that has a customized text.
Like F**K YOU B*TICH
or maybe
If Found Contact -
ETC. and it just stays at that screen. wonder if thats possible
edit- i shoulda read page 2 haha. same idea as Setnev lol.
I was playing around with the pattern lock and eventually got the 'Too many pattern attempts!' message, with it asking for my Google username and password to log in.
No matter what, it doesn't accept my username/password. I am 100% sure I've typed it in correctly.
This bug has been around for over a year with many people reporting 'bricked' phones without even doing anything particularly naughty with their phones.
This is the Google bug that has been posted on it: http://code.google.com/p/android/issues/detail?id=3006#makechanges
As you can see this has been around for over a year. The 'null'-in-password trick doesn't work, nor does the spamming-home-button trick.
My phone is rooted and with the Voodoo Lagfix-only custom kernel. Any suggestions?
Do a hard reset / wipe. That's my suggestion.
Try booting into recovery (Home Button, Vol Up + Power), and resetting your cache and wiping it. Then try logging in with your Google account. If all else fails, try changing your Google password on the PC then logging in on the phone. And then if it still fails, looks like you need to flash the phone again. Next time, don't enter the thing wrong! Stop rushing haha .
I wasn't rushing, I was playing with the lock. It takes about 30 times before it's permanently requiring the username/password. But really...you can't blame me for not expecting this. :/
I'm currently trying to flash a new ROM but I've run into another problem - I can't get it to boot into downloader/recovery. It's not the lack of the 3 button combo - I've managed to reach Recovery and Downloader ONCE each in the past, but never again since.
And now with all my efforts to boot into recovery/downloader, it now cannot boot into normal usability mode (or in my case, locked mode). Instead, the Galaxy S logo loops endlessly.
Sigh.
Have you read the thread for the fix for Galaxy S variants that are lacking the 3 Button Combos? It's in Android Development. Maybe try that? Or, can you still connect the phone and connect with Kies?
I can't turn on the phone anymore, meaning no changing to USB debugging etc. And I'm having problem accessing recovery/download, even though I definitely HAVE done each of them once before and therefore do not have the 3 button problem.
Without turning on my phone, Kies can't detect it
So what happens when you power on?
Now, it shows the first Galaxy S splash screen, then shows the boot logo, then nothing. The boot logo continues to glow endlessly.
Be patient, i waited up to five minutes. If you see the s logo glowing/shining youare ok
Sent from my GT-I9000 using XDA App
okpc said:
Be patient, i waited up to five minutes. If you see the s logo glowing/shining youare ok
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Yeah it's continuously shining. Haven't left it for up to five minutes though... And even then it probably won't help since I'm still locked out of the phone, and unable to access download/recovery mode to reflash it.
After waiting for a long time, the logo disappears, screen goes black. Menu and back buttons light up. Nothing else.
Looks like your going to have to reflash your phone again. Download the desired firmware, open up Odin and put your phone into download mode and start the flashing procedure. Be more careful next time.
PaulForde said:
Looks like your going to have to reflash your phone again. Download the desired firmware, open up Odin and put your phone into download mode and start the flashing procedure. Be more careful next time.
Click to expand...
Click to collapse
Good advice considering he said his 3 button combo stopped working =))
All I did when I got that black screen was adb reboot recovery and wiped and phone bootedup fine. But only if you have debuging enable and and sumsung drivers. Hopes this help.
Sent from my SGH-T959 using XDA App
Can't enable USB debugging when phone can't be turned on at all.
danamoult said:
I was playing around with the pattern lock and eventually got the 'Too many pattern attempts!' message, with it asking for my Google username and password to log in.
No matter what, it doesn't accept my username/password. I am 100% sure I've typed it in correctly.
This bug has been around for over a year with many people reporting 'bricked' phones without even doing anything particularly naughty with their phones.
As you can see this has been around for over a year. The 'null'-in-password trick doesn't work, nor does the spamming-home-button trick.
My phone is rooted and with the Voodoo Lagfix-only custom kernel. Any suggestions?
Click to expand...
Click to collapse
Ok i did the same thing, and spent hours googling.
Tried the key combinations to restore, but never worked.
Heres what worked for me, but, be warned all your contacts will be lost if stored on the phone.
From another phone, call your locked number.
Answer it on the locked phone, then hit the "back" button.
This gives you full access to the phones menus etc.
Hang up on the phone you called from.
Now, go into Applications / Settings / Privacy / Factory Data Reset.
This worked for me whereas all other methods did not.
Once your phone is up and running again, be sure to create your google account on your phone.
That way your protected again. If you didnt previously have the account set up from your phone, like i didnt, then you cannot log in of course.
This works...give it a try. Hope it helps.
danamoult said:
Can't enable USB debugging when phone can't be turned on at all.
Click to expand...
Click to collapse
you need to be able to enter recovery mode for you to solve this problem
danamoult said:
I was playing around with the pattern lock and eventually got the 'Too many pattern attempts!' message, with it asking for my Google username and password to log in.
No matter what, it doesn't accept my username/password. I am 100% sure I've typed it in correctly.
This bug has been around for over a year with many people reporting 'bricked' phones without even doing anything particularly naughty with their phones.
This is the Google bug that has been posted on it: http://code.google.com/p/android/issues/detail?id=3006#makechanges
As you can see this has been around for over a year. The 'null'-in-password trick doesn't work, nor does the spamming-home-button trick.
My phone is rooted and with the Voodoo Lagfix-only custom kernel. Any suggestions?
Click to expand...
Click to collapse
dear friend dont worry or panic... i'll tell you a trick , go to the samsung customer care and tell them that your phone gets heated up very often and today it just refuses to boot up normally...
since your device cannot get into recovery mode or download mode the company will never know that you had played with the system files in the device or not... (rooted )..
since the samsung people will also try to get your device in recovery mode.. but when it will not go to the recovery mode you will get a mother board replacement under warranty.....
this heating up of the device is a common problem in the galaxy here in india.. so use this excuse and i know it works 100% ... (just dont tell them that you had rooted and lagfixed your device )
What you describe sounds like a very large security hole if I am reading it correctly.
Are you saying that even if your phone has been locked out from too many lock screen failures, that just answering an incoming phone call gives you full access to the phone? Really?
I just checked on my phone and while I can answer an incoming call while the screen is locked, if I hit the back button or menu button, I just get the lock screen.
I'm missing something here...
OzzYGuY said:
Ok i did the same thing, and spent hours googling.
Tried the key combinations to restore, but never worked.
Heres what worked for me, but, be warned all your contacts will be lost if stored on the phone.
From another phone, call your locked number.
Answer it on the locked phone, then hit the "back" button.
This gives you full access to the phones menus etc.
Hang up on the phone you called from.
Now, go into Applications / Settings / Privacy / Factory Data Reset.
This worked for me whereas all other methods did not.
Once your phone is up and running again, be sure to create your google account on your phone.
That way your protected again. If you didnt previously have the account set up from your phone, like i didnt, then you cannot log in of course.
This works...give it a try. Hope it helps.
Click to expand...
Click to collapse
distortedloop said:
What you describe sounds like a very large security hole if I am reading it correctly.
Are you saying that even if your phone has been locked out from too many lock screen failures, that just answering an incoming phone call gives you full access to the phone? Really?
I just checked on my phone and while I can answer an incoming call while the screen is locked, if I hit the back button or menu button, I just get the lock screen.
I'm missing something here...
Click to expand...
Click to collapse
chill my dear friend.... it cant be true.... its just his 1st post.. and samsung cannot be so dumb to leave a password protected keypad that can be cracked so easily.. even i tried the back key on a call with a password lock.. i cannot get passed the lock screen....
DISCLAIMER*** I DO NOT OWN A NEXUS 5, AND DO NOT FOLLOW IT HEAVILY THIS IS PURELY BASED ON MY EXPERIENCE TODAY AND MY YEARS OF USING ANDROID OS. I DO NOT USE IT DAILY AND ONLY USE IT EVERY NOW AND THEN FOR CALLS. MY INFORMATION MAY NOT BE ACCURATE AND PURELY BASED ON PREVIOUS USES OF DIFFERENT DEVICES FROM DIFFERENT BRANDS.
THIS MAY BE DISREGARDED OR/AND DELETED
Today my sister nexus 5 (aosp 5.1 "newest") was "stolen".
We spent the day looking all over the place for it and went back to a few stores we visited that day and asked the staff. But it was of no hope. No one has seen or heard of it, so we regarded it as stolen. So after awhile we went home we went to ADM (https://www.google.co.uk/android/devicemanager) and set up a lock and number to call as you would.
After a few hours my dad found it in his car :/ so yeah...
But that's just the bread of it. HERE is the butter:
1)The lock we set up was 100% not in place even tho ADM said it was "sent". AND the mobile data is ON, but this is just how ADM works and it doesn't check if the device receives it or not. Maybe google should add this feature.
BUT even after we got it back and connect to WIFI, the lock did NOT get put in place. Proving the phone does not check for any lock requests at screen unlock. But maybe because she already has a normal pincode in place and it couldn't over ride that :/
after that I took a interest in the security.
2)So i took a deeper look into the security and it flaw, and first off. EVEN locked I could access the status bar and turn on AIRPLANE MODE. This was without the password and I could turn on torch, wifi, mobile data ext off as well. The only thing I couldn't access was the "settings". But I had a great deal of control of the device's connectivity and from there a thief could make his way out without any calls or ANYTHING affecting him.
3)THIS was truly shocking. I'm not sure if this is by default or by accident. But by using the status bar "exploit" i was able to get into the users page and switch to guest mode. From there i was able to grant adb access and access the market. If this phone was rooted I guess you could install some apps to get rid of the lock screen or even install a custom recovery. But them i guess it's up to you to take the action.
As i said before. I do not use it. My sister does. But she does not root or mod, and only follows the AOSP path.
Some exploits may only work because of a few careless button presses. And may not even affect anyone at all if you don't spam the settings with random presses.
Thanks for listening to me and feel free to point out any mistakes i made and share if you could post if these "exploits" work for you. If someone already made a thread please delete this one. Thanks for listening
Actually the only serious thing is the guest mode option.. About the airplane mode, for a thief it would be much easier to simply turn the phone off.. Anyway I completely agree with you.. Google should take more seriously the security part.. It should even be impossible to turn off the phone without a code..
And make the back impossible to open so a thief can't pop out the battery.
Once a phone is out of your physical control, consider everything on it to be compromised, regardless of whatever security you have.
Please delete this. None of this is news or exploits. People have known and been disappointed by it from day 1 of Lollipop going live.
Well removing the battery of the n5 is not immediate.. If a thief want to resell it probably he won't do that until he's at home or wherever and if he couldn't turn it off you could track the position or at least erase your data..
91franz said:
Well removing the battery of the n5 is not immediate.. If a thief want to resell it probably he won't do that until he's at home or wherever and if he couldn't turn it off you could track the position or at least erase your data..
Click to expand...
Click to collapse
You say Google should take security more seriously. Take that advice. Never assume a thief would act in a manner that accommodates you.
That's right.. Anyway I should try to make his life as complicated as possible ?
It should even be impossible to turn off the phone without a code..
sseuorosal said:
It should even be impossible to turn off the phone without a code..
Click to expand...
Click to collapse
with some aluminium fold will easily to block any signal, the phone will eventually turn off.
p.s. If I am the thief which stole a useless phone, I will just break it and throw away. I don't think any thief will say "hey, I can't unlock it, let's return to the owner"
I was minding my own business grilling hamburgers for family and friends this afternoon when I thought, "my phone seems awfully hot in my pocket, what's up?" I took it out to see the dreaded green Android and the word "Erasing". It was already too late to do anything... it took another 20 minutes or so and sure enough it rebooted into the setup screen as though I had just done a factory reset.
Anybody have a similar experience? At this point it's clearly been erased, there's nothing to do but set it up again and back up more regularly, but what happened? No way did I press the boot loader button combo this afternoon. My boot loader is unlocked and I dirty flashed LMY47Z about two weeks ago but no other notable changes recently.
stevexyz0 said:
I was minding my own business grilling hamburgers for family and friends this afternoon when I thought, "my phone seems awfully hot in my pocket, what's up?" I took it out to see the dreaded green Android and the word "Erasing". It was already too late to do anything... it took another 20 minutes or so and sure enough it rebooted into the setup screen as though I had just done a factory reset.
Anybody have a similar experience? At this point it's clearly been erased, there's nothing to do but set it up again and back up more regularly, but what happened? No way did I press the boot loader button combo this afternoon. My boot loader is unlocked and I dirty flashed LMY47Z about two weeks ago but no other notable changes recently.
Click to expand...
Click to collapse
Rise of the machines
Al kidding aside, never heard or read of a `premature` wipe. You must have a wild and active life to be abe to do that
I'm sure you have heard the expression "butt dial" when you mistakenly dial a number while the phone is in your pocket? Well, you just did a "butt wipe"!
kevinga said:
I'm sure you have heard the expression "butt dial" when you mistakenly dial a number while the phone is in your pocket? Well, you just did a "butt wipe"!
Click to expand...
Click to collapse
That just gave me a good laugh, thanks!
But seriously, to the OP does anyone have your gmail password? Because you can remote wipe a device using Android Device Manager.
I setup my friends phone for him. We both pull pranks on each other so to get him back for letting all the air out of my tires while my car sat in my garage I remote wiped his phone on his way home.
bp328i said:
That just gave me a good laugh, thanks!
But seriously, to the OP does anyone have your gmail password? Because you can remote wipe a device using Android Device Manager.
I setup my friends phone for him. We both pull pranks on each other so to get him back for letting all the air out of my tires while my car sat in my garage I remote wiped his phone on his way home.
Click to expand...
Click to collapse
Nobody has my password and I use two factor Auth for my Google account so I really don't think so. I logged in to the device manager site to see if anything looked suspicious but there's no history of activity or anything like that.
It must have been a "butt wipe" as the other post said! [emoji23] wish I could figure out how it happened though.
Sent from my Nexus 6 using Tapatalk
Very unsettling. Now you're always going to be paranoid with that phone.
Sent from my Nexus 6 using XDA Forums Pro.
Well, our phones can locally wipe back to default state if a security code is incorrectly input 10 times in a row, I believe.
It's possible that you *did* butt wipe, I'm thinking.
- ooofest
Similar Case
This is one of the cases when you have a big string which gets inputted by the emergency call keypad. That screen matches with the butt wipe code of Android making the device in erase mode. I got the reason.
I travel a lot and always have the phone in my pocket so can someone tell how to switch off the emergency keypad.
Turn off ambient display and the phone won't wake in your pocket
I thought I did this once bit it was actually that I had switched user profiles by clicking on the blue figure circle in the notification panel. Check to see if you are signed into your account or more than likely your guest account.
You better hope you mistakenly did it or it could be remote code execution that might have caused the wipe by a third party.
Are you running a custom ROM. If no and you're running some variation they have security features in it now like most other devices that too many incorrect password attempts will wipe the phone more than likely what it happen
I just realized someone revived a dead thread lol. All of us saw the action and tried to help him.