本文介绍了解锁屏幕的Galaxy Nexus ADB的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述



我有一个破碎的屏幕一场噩梦的一天,结果
我有'的Droid屏与终极触摸屏控制不过举手投足似乎不工作这个手机解锁通常需要但是,这种停止,我可以得到它的点击代替刷卡,任何想法与亚行解锁所以我可以得到我的消息将是一个生命的救星


I'm having a nightmare day with a broken screen ,
I've 'Droid Screen' with 'Ultimate Touchscreen Control' however the gestures dont seem to work for this Phones unlock it usually requires a swipe that stops however I can get it to 'click' in place , any ideas to unlock with the ADB so I can get to my messages would be a life saver

推荐答案

所以让我成为你生命的救星(也许)

so let me be your life saver (maybe)

我在的Nexus已经打破了屏幕4几个星期前,我也一直在寻找类似的回答。它是重要的,这是的的Nexus 4奇巧股票与4.4没有根,只有亚洲开发银行和默认模式锁(点)

I've broke screen in my Nexus 4 few weeks ago and I was also looking for similar answer. it's is important that it was Nexus 4 stock Kitkat 4.4 with no root, only ADB and default pattern lock (dots)

所以我一直在寻找ADB命令,发现简单的的SendEvent 方法。它alows做挥笔像你需要一些例如:

so I've been looking in adb command and found simple sendevent method. it alows to do swipes like you need, some example:

cd C:\sdk_patch\platform-tools
adb shell sendevent /dev/input/event2 3 57 58 
adb shell sendevent /dev/input/event2 3 58 17 
adb shell sendevent /dev/input/event2 3 53 470 
adb shell sendevent /dev/input/event2 3 54 1200
adb shell sendevent /dev/input/event2 0 0 0 
adb shell sendevent /dev/input/event2 3 53 670 
adb shell sendevent /dev/input/event2 3 54 1200
adb shell sendevent /dev/input/event2 0 0 0 
adb shell sendevent /dev/input/event2 3 58 88 
adb shell sendevent /dev/input/event2 3 54 1494 
adb shell sendevent /dev/input/event2 0 0 0 
adb shell sendevent /dev/input/event2 3 54 1820 
adb shell sendevent /dev/input/event2 0 0 0 
adb shell sendevent /dev/input/event2 3 58 96 
adb shell sendevent /dev/input/event2 3 53 612 
adb shell sendevent /dev/input/event2 0 0 0 
adb shell sendevent /dev/input/event2 3 58 98 
adb shell sendevent /dev/input/event2 3 53 617 
adb shell sendevent /dev/input/event2 0 0 0 
adb shell sendevent /dev/input/event2 3 57 4294967295 
adb shell sendevent /dev/input/event2 0 0 0

这code,我作为执行蝙蝠,它是我的绘画图案锁这是

this code I'm executing as bat and it is drawing my pattern lock which was

1 2 3
4 5 6
7 8 9

1 - > 2 - > 5 - > 8(点连接)

1 -> 2 -> 5 -> 8 (dots connected)

我真的不记得这些数字他们的意思,但你可以发现它在文档。我记得在触摸像素的 53 54 的位置(X / Y),点刷卡',那么 0 0 0 作为确认(?)。所以你需要知道你的屏幕分辨率(N4是HD)以及位置(近似,点允许点'检查')的点(注意这可能与物理按键屏幕可能有圆点比N4低一点软按钮缩小一点屏幕)。在上述code也有一些短的延迟( 58 和毫秒后?),所以你可以看到图案/滑动正在快速绘图(pretty我记不清了)

I don't really remember these numbers what they mean, but you can found it in documentation. what I remember that 53 and 54 are position (x/y?) in pixels of touch, point 'to swipe', then 0 0 0 as confirmation (?). so you need to know resolution of your screen (N4 is HD) and also position (approximate, point that allows to dot 'check') of your dots (note that probably screens with physical buttons might have dots a bit lower than N4 with soft buttons shrinking a bit screen). in above code there are also some short delays (58 and miliseconds after?) so you can see how pattern/swipe is drawing (pretty fast as I remember)

重要:不同的设备有不同的事件若干负责联系。就像上面我N4其 EVENT2 ,但我一直在测试使用的Nexus 7 2013(全高清,在不同的坐标点,也只有无根ADB)亚洲开发银行这样的方法和有 event7 是工作(如果我记得正确的...)。网上说比最常见的就是 EVENT0 ,它是一个猜测,这取决于制片人......在你的设备它可能我的另一个号码(事件从0开始上升continously数字,亚行将引发错误/当你调用不存在的事件警告,大概7-9之间水木清华是最后一个事件文件号码)

important: different devices have different event number responsible for touch. like above in my N4 its event2, but I've been testing this adb methods with Nexus 7 2013 (full HD, dots in different coordinates, also only adb without root) and there event7 was working (if I remember properly...). Internet said than most common is event0, its a guessing, depending on producer... In your device it might me another number (event numbers starting at 0 and rising continously, adb will throw an error/warn when you call non-existing event, probably smth between 7-9 is last event file number)

提示:解锁首先要做的后置长关屏等待时间(1小时),以及在开发选项选中选项充电时或水木清华不关闭屏幕这样,这些都会让你保持屏幕上长时间不自动锁定,也可以删除模式锁定,但在选择你需要写它,点的位置都有点不同,所以你onlock code坐标可能无法正常工作

tip: after unlock first thing to do is set a long screen-off wait time (1 hr) and also in dev options check option "don't turn off screen when charging' or smth like this. these will allow you to keep screen on for long time without auto-lock. you can also remove pattern lock, but in options you need to write it and positions of dots are a bit different, so your onlock code with coordinates may not work

我知道,现在还不清楚,挺直的答案,但我一直在寻找这种方法的很多的一些测试,坐标和事件号应该给你你想要的东西。还有:当你解锁手机,您可以使用它发射广告屏幕直奔电脑,该机还支持触摸这个屏幕(但只有单一的水龙头和刷卡挺直头也不回)。你可能会从安装谷歌播放,例如任何备份应用程序短信backuping。祝你好运。

I know that it's not clear, stright answer, but I was looking for this method a lot and some tests with coordinates and event number should give you what you want. also: when you unlock your phone you might use Android Control which transmitting your screen straight to computer, it also supports touching this screen (but only single tap and stright swipe without turning). you might install any backup app from Google Play, e.g. for sms backuping. Wish you luck

PS。亚行有望方法也是亚行外壳输入(检查文档),但它支持(我知道)只能直轻扫和单水龙头(和其他的不转动),我猜那Android的控制和类似桌面应用程序正在使用这些命令,这是因为没有图灵的能力,而刷卡)的原因。还听说最新AirDroid 3还可以流您的屏幕,也许这个程序将帮助

PS. hopeful method for adb is also adb shell input (check docs) but it supports (as I know) only straight swipe and single tap (and other ones without turning), I'm guessing that Android Control and similar desktop apps are using these commands and this is a reason for no ability of turing while swiping). also I've heard that newest AirDroid 3 can also stream your screen, maybe this app will help

这篇关于解锁屏幕的Galaxy Nexus ADB的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

09-18 08:29