Hi!
I just noticed that when the screen is locked and you double tap the home butten, the voice control will start. Then you are able to just go to your homescreen. Is this happening on your sgs2's too?
Found it on Villain Rom 1.1
Sent from my GT-I9100 using XDA App
No
Sent from my GT-I9100 using XDA App
No
But you are using a modified non standard rom .
jje
However, i just wanted to share it. Here's a short video of it on youtube: http://goo.gl/F0Fuh
Sent from my GT-I9100 using XDA App
delet sorry
Yep same here using KE7 XEU (stock version) and default lock screen.
Double hit home button while in lockscreen and when voice control starts just tap cancle and viola youre on home screen.
But it doesnt happen when you active pattern or number lock.. so its not really a security issue =)
lugi93 said:
Yep same here using KE7 XEU (stock version) and default lock screen.
Double hit home button while in lockscreen and when voice control starts just tap cancle and viola youre on home screen.
But it doesnt happen when you active pattern or number lock.. so its not really a security issue =)
Click to expand...
Click to collapse
Why does everyone have to put FIVE ALARM FIRE!!! titles in their not so significant posts. If the phone doesn't have lock enabled this is a convenience feature not a security problem.
BarryH_GEG said:
Why does everyone have to put FIVE ALARM FIRE!!! titles in their not so significant posts. If the phone doesn't have lock enabled this is a convenience feature not a security problem.
Click to expand...
Click to collapse
Watch my video.. I have the passcode enabled and it happens.
Sent from my GT-I9100 using XDA App
Cannot reproduce on villainrom 1.1 using pattern lock
Cannot reproduce on villainrom 1.1 using alphanumeric password.
Not happening on mine..Gingerbread. Rooted. Stock ROM. Pattern lock
Sent from my GT-I9100 using XDA App
supermult said:
Watch my video.. I have the passcode enabled and it happens.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Then friggin turn off Voice Talk so its not running in the background and turn it back on when you need it. If you need more help, post in Villian's thread in the development forum. No offense, but this isn't front page news.
BarryH_GEG said:
Then friggin turn off Voice Talk so its not running in the background and turn it back on when you need it. If you need more help, post in Villian's thread in the development forum. No offense, but this isn't front page news.
Click to expand...
Click to collapse
I believe it is. I didn't know about this
supermult said:
Watch my video.. I have the passcode enabled and it happens.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
I think this IS a security issue
Stock or modified?
Rooted?
Not happneing for me
Im on a stock KE2 firmware and this doesnt happen for me, it stays on the lock screen (have the alphanummeric lockscreen set).
Mittaa said:
I think this IS a security issue
Stock or modified?
Rooted?
Click to expand...
Click to collapse
I mean seriously, do you even read any of the posts before replying?
1) OP said he's running a Villain ROM which means he's rooted and modded.
2) Another poster running Villain can't replicate the problem.
3) No one other than the OP (and I'm assuming even you) can replicate the problem.
4) Who knows what the OP might be running app wise that might be triggering the issue on his phone.
I know I'm not a mod but these little "crisis" posts that start out as embers end up being raging fires. Maybe its because of all the different languages spoken. By all means, if anyone running a stock ROM can replicate this report back. It would indeed then be an issue worthy of the front page and the title "Security Flaw in our phones."
Just to add - I'm using litening 1.1, and I have an enforced exchange PIN.
Double clicking the home button will not get past the password entry screen.
Believe me, I've tried all ROMs and various apps to get around the password, still haven't found one yet.
Related
I just noticed today accidentally that you can press and hold the search button on the lock screen and perform anything Google Voice Actions is capable of. I am using a Droid 2 unrooted. This may affect the Droid X as well.
This is a huge security flaw in Motorola's modified lock screen. Hopefully this thread garnishes enough attention so that this can be patched soon!
Steps to reproduce:
1. Lock your screen
2. Press and hold the search button "magnifying glass"
3. Speak any voice action and the phone will respond. Note: you will not get any visual or audible cues that it is working, but it is!
I use Widget Locker which allows me to disable this flaw, but this is a good find.
Thanks for making it public.
Oh wow!!
Sent from my DROID2 using XDA App
Wow is right.... good find... Moto please fix.
Must be fixed!..my D2 doesn't do that
Sent from my DROID2 using XDA App
yunghostage said:
Must be fixed!..my D2 doesn't do that
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Is your D2 rooted?
Is your D2 modified in anyway in regards to the lock screen?
Have you recently received an OTA update from VZW?
The issue is still affecting me and others. I do know if you Google Voice Actions can't recognize your phrase, it will obviously stop and not do anything.
Mine too, Droid 2 FRG22D rooted but no roms
Just checked, my D2 will do the same thing. It is rooted, but totally stock otherwise with no rom changes. FRG22D (2-week old phone).
Same Here with a Rooted D2!
Wow, that's a serious flaw... a custom rom will probably be able to remedy that though
Here's two articles showing good video demonstrations of the issue:
Edit: I tried to post the links, but I guess my newbie status doesn't allow it.
If you go to boygeniousreport and droid-life, you can find the articles there.
Hi. I use this app quite frequently and after updating last night it seems to have stoped working. When I start it the screen just goes white. Is it possible that the art update caused this?
Sent from my MB860 using XDA App
That "App" is just a link to the mobile site https://m.pnc.com try going there from your browser.
cla2000 said:
Is it possible that the art update caused this
Click to expand...
Click to collapse
Using reason and logic. Then Yes!
Thx for the reply. I seen the mobile site is identical. I just liked than when using the app and trying to close it it would actually ask if u want to do that and then it would close completly. The stupid phone browser allways stays on in the background.
Sent from my MB860 using XDA App
Gotcha, I use Dolphin HD, so when I hold down the "back" button on the phone it asks me if i want to exit and gives options to clear cache and recent history. 2c
It appears all the banking apps have the same problem after the update. The Bank of America app does exactly the same thing. Maybe it's a security thing.
Is there any way to disable the slide to unlock feature and just have the pattern unlock ?
Also in this boat, searching leads to several threads like this
Yes you need to uncheck the auto launch of the play app.
I don't recall where I seen it.
I'll post when I find it.
Open the play app, push the menu button and select settings.
Then uncheck auto start.
Forget what I said.
I thout you meant when you slid the screen and not the slide bar on the screen.
There is no way that I have found.
Settings / location and security / setup screenlock
Sent from my R800x using XDA Premium App
fenix4o9 said:
Settings / location and security / setup screenlock
Sent from my R800x using XDA Premium App
Click to expand...
Click to collapse
That's where we go to set the pattern unlock, what we want to know is how to remove the slide to unlock that comes up before the pattern unlock
This needs a bump, so here it is. I'm in this boat all of a sudden because my employer enforces an entry code for devices for a corporate account. I'm getting really unhappy having to slide, enter pin every time !
Try the app "antilock"
Its free on the market and does exactly what you want, I believe. I use it myself so I don't need to slide twice as I use widgetlocker
Hope this helps!
works like a charm!
Uninstalling, sometime after turning the app on my phone started to act "funny" or erratic... After uninstall everything seems to be normal again.
Sent from my R800a using XDA App
hexen2006 said:
Uninstalling, sometime after turning the app on my phone started to act "funny" or erratic... After uninstall everything seems to be normal again.
Sent from my R800a using XDA App
Click to expand...
Click to collapse
Mine too, It started flickering like mad and asked me for the code over and over.
So the proximity sensor completely stopped working sibce I upgraded to Gingerbread. Well the little red light still comes on but when I put the phone to my face while in a call I expect the screen to automatically turn off but I forget that it no longer works so I end up pressing buttons while talking. If anyone else is experiencing the same issue, or if there are any known fixes someone PLEASE help. Other than that I still really like Gingerbread.
Sent from my MB860 using XDA Premium App
Sadly I don't have any help for you as I am limited in my knowledge...However, I used Kenn's 2.3.4 beta ROM a couple weeks ago or whatever, and I ALSO have noticed that the sensor doesn't seem to work properly. It works right most of the time for me (dunno about you), but there have been times where it screws up. Kind of lame, but I'm sure this is fixable if other people experience the same issue and someone is willing to fix.
Try fix permissions
I am also experiencing this same issue, worked before but not now. I have already fixed permissions...
Sent from my MB860 using XDA Premium App
Well its rly good to kno that im not the only person experiencing this problem. Hopefully someone or Motorola will fix this issue soon. Its actually quite annoying..
Sent from my MB860 using XDA Premium App
My nexus one had a flaky proximity sensor
workaround: turn off the screen with the power button when answering call
annoying but works
wintermute000 said:
My nexus one had a flaky proximity sensor
workaround: turn off the screen with the power button when answering call
annoying but works
Click to expand...
Click to collapse
Lol yes of course. Guess ill just live without that minor luxury for the time being. Reminds me of my original HTC Touch. (KICKIN' IT OLD SCHOOL) lol.
Sent from my MB860 using XDA Premium App
wintermute000 said:
My nexus one had a flaky proximity sensor
workaround: turn off the screen with the power button when answering call
annoying but works
Click to expand...
Click to collapse
Yes but since the phone has the sensor I'd rather not have to hit the power button every time I start a phone call. Then I have to hit the power button again to get to the dialer or other apps. Hence inconvenient.
Sent from my MB860 using XDA Premium App
edit your build.prop and set proximity time to like 200 and distance to 20.
dLo GSR said:
edit your build.prop and set proximity time to like 200 and distance to 20.
Click to expand...
Click to collapse
Exactly how? Please? Not a noob but definitely not that advanced yet. Im quite tech savy so fire away.
Sent from my MB860 using XDA Premium App
Install Proximity Sensor Finder app to do some test.... my work like charm with the new GB 2.3.4/4.5.91
mramirezusa said:
Install Proximity Sensor Finder app to do some test.... my work like charm with the new GB 2.3.4/4.5.91
Click to expand...
Click to collapse
Did that nothing happened. Tried everything!! Need to know how to change build.prop as mentioned in a few posts above.
Sent from my MB860 using XDA Premium App
cwburns32 said:
Did that nothing happened. Tried everything!! Need to know how to change build.prop as mentioned in a few posts above.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
get root explorer, open up build.prop in system and change those values
Not sure......mine works perfect now since the update........before the update, it was spotty at best......
dLo GSR said:
get root explorer, open up build.prop in system and change those values
Click to expand...
Click to collapse
I have root explorer and know where build.prop is located but can't seem to edit the build.prop. how do I got about doing this??
I found the proximity sensor settings in the build.prop and both are disabled??
Sent from my MB860 using XDA Premium App
I had same problem and found another solution online: remove battery.
I was shocked it was that simple, but I did it yesterday and the proximity sensor worked great all day today. Crossing my fingers that it will stay that way.
tlphipps said:
I had same problem and found another solution online: remove battery.
I was shocked it was that simple, but I did it yesterday and the proximity sensor worked great all day today. Crossing my fingers that it will stay that way.
Click to expand...
Click to collapse
I pull my battery often, my sensor stopped working shortly after I flashed Gingerblur a few months back...hmmmm
Someone out there please tell me how to edit the info in the build.prop. I see where my proximity sensor is at and both sections are labeled as disabled. Need to know how to edit so I can get it working again!!
I use root explorer. open build prop. make it r/w at the top. Hold finger on screen to open menu. scroll down to open in text editor.
edit: my current settings are below. and my sensor does not turn of screen. I think mine stopped working on the 1.5.7 update. hasn't work since.
proximit sensor screen off delay
mot.proximity.delay=450
proximit sesor disable touch distance
mot.proximity.distance=60
mrphil101 said:
I use root explorer. open build prop. make it r/w at the top. Hold finger on screen to open menu. scroll down to open in text editor.
Click to expand...
Click to collapse
I figured out I could do this but also downloaded PropEditor which allows you to edit and .prop on your device.
After changing numbers, still nothing....
cwburns32 said:
I figured out I could do this but also downloaded PropEditor which allows you to edit and .prop on your device.
After changing numbers, still nothing....
Click to expand...
Click to collapse
what numbers did you change it to? for me 200 & 20 worked.
edit: also don't forget to reboot after
Hi All,
Who know what apps or anythings script for double tap to wake the screen (like Lumia) so.. we no need to push the button..
seven6ixers said:
Hi All,
Who know what apps or anythings script for double tap to wake the screen (like Lumia) so.. we no need to push the button..
Click to expand...
Click to collapse
As I remember it comes as a part of the kernel for those devices including LG G2, since there aren't any custom kernels out for these devices yet I highly doubt that's a possibility right now.
you can opt for proximity actions for locking and unlocking, although it would drain your battery a bit.
I'm using Wakeup Touch Nexus which is available in Google Play for free. Dint notice any battery drainage. Very nice app. If anyone got better app can suggest me too...
chris7524 said:
I'm using Wakeup Touch Nexus which is available in Google Play for free. Dint notice any battery drainage. Very nice app. If anyone got better app can suggest me too...
Click to expand...
Click to collapse
How is it going frenz? is it ok?:laugh:
seven6ixers said:
How is it going frenz? is it ok?:laugh:
Click to expand...
Click to collapse
Very good:good:
Tnx
Sent from my SM-N7505 using XDA Premium 4 mobile app
Hey, try this app- knockr
It can be downloaded free from playstore
:thumbup::thumbup::thumbup:
Sent from my SM-N750 using XDA Free mobile app
Sent from my SM-N750 using XDA Free mobile app
It's not really "double tap", I use "Gravity Screen" as an alternative to the on/off button
ryansmth76 said:
Hey, try this app- knockr
It can be downloaded free from playstore
:thumbup::thumbup::thumbup:
Sent from my SM-N750 using XDA Free mobile app
Click to expand...
Click to collapse
Doesnt work for me.. lags a bit..
Sent from my SM-N750 using XDA Free mobile app
Pretty much every major OEM like Sony, HTC, LG and even Chinese manufacturers like OPPO , Xiaomi etc have implemented double tap to wake on their large screen phones and I really don't know what's stopping Samsung to implement in spite of so many Note generations .
Only way to properly implement this is using a custom kernel for the device
Tap Tap App @ Play Store
Tap Tap App works for me. Galaxy Note 4.
Requires configuration.
Lost functionality, how to get it back?
rakeshishere said:
Pretty much every major OEM like Sony, HTC, LG and even Chinese manufacturers like OPPO , Xiaomi etc have implemented double tap to wake on their large screen phones and I really don't know what's stopping Samsung to implement in spite of so many Note generations .
Only way to properly implement this is using a custom kernel for the device
Click to expand...
Click to collapse
OK, I've got a VKWorld VK6050S (note the S). This will be a long story, but I feel I must post many details. Otherwise, there will be that smart-*** posting "but you can't do that!!!"
Had the phone for several weeks now. Took a LONG time to set it up and get it running EXACTLY the way I wanted it to. As part of that process, I installed Nova launcher, and an app called "DTSO". Anyway, when it was all set up.... I could double-tap the home screen to lock, and the display would go black. Then, *without using the proximity sensor*, I could double-tap the middle of the BLACK screen, which would cause the display to wake up and display the lock screen. I didn't set a lock on this screen, so I could just swipe up to clear it. Note I could double-tap the BLACK screen to wake it up.
So I was happy with the way everything was set up. Only problem was, it was not stable. Most of the time, if you tried to take a picture, the phone would freeze. (forever). Or sometimes a reboot would take HOURS (starting after the animated vkworld logo displayed) I tried several suggestions. It was not a bad memory card, and it was not corrupted files on a memory card. I tried clearing various caches, etc. Nothing worked. Finally, in desperation...I went to the factory boot menu (chinese, but I found a guide for it) and cleared hardware cache / emmc / whatever. That left me with *** CHINESE LOLLIPOP ***, and all my apps/settings/data were GONE...
(sigh)
So I had to start from figuring out how to switch back to English. And then starting all over again. I wasn't back to "zero". I went back to "minus one". (!!!!)
After many hours setting up the phone again with dozens of applications, getting my account settings input, getting it all configured...
The only thing I can NOT do now is to double-tap the black screen to wake it up. The phone is rock-solid STABLE now, so that is an improvement. But I want it to wake the screen with a double-tap, like it did before!!!
I'm now using "Go" launcher. But I (temporarily) tried "Nova" launcher, like I had it before. DTSO does not work like it used to. It won't wake up the screen while black. Again, this USED TO WORK, so it's not a hardware issue. What did I do wrong? What did I miss in setting this thing up again?