I read that thread:
http://forum.xda-developers.com/showthread.php?t=1243699
and wondering if is possible to use our phone as fully (or close to that) terminal /computer.
I want to learn linux to work with some commands, but sometimes it just dont work.
Ofcourse there is many solutions but all of them work fine for software keyboard.
I want to use hardware keyboard in full.
Any ideas?
Related
I have been playing with Pocket PC for years and yet there is one issue that I really don't understand.
With WM5, Why would the custom installed SIP input methods such as T9 Phone pad would not load sometimes? Only the standard keyboard would load when I select the phone pad. I have to reset a couple of times and sometimes it loads.
WHY?
Anyone please give me an idea... Thanks...
Any news on this?
I encountered the same problem. The custom keyboard I use (which is signed and worked fine on WM 2003) some times stops working. It can be fine for a day or two, but then I can't select it (or any other custom keyboard) only the default English keyboard comes up until I reset the device. A few other people I know have observed the same problem on different WM5 devices.
P.S. I used no other 3rd party software, the apps that ran were mainly Excel, Messaging and Internet Explorer so I can only guess it is an OS related bug.
Try this
http://forum.xda-developers.com/viewtopic.php?t=56053
some reading here
http://forum.xda-developers.com/viewtopic.php?t=26586
Thanks hanmin, but both of these threads just deal with another way of changing the SIP provided the one you want can load.
The problem I am facing is that at some point the keyboard will stop loading completely until I reset the device.
Unfortunately, because it usually takes quite a bit of use before this happens, and it seems to be somewhat random occurrence I haven't been able to trace the exact circumstances of the failure.
Oh.
I have the similar problem too. Some customized input just do not load correctly. I had a few input methods installed, and I've noticed that, upon a soft reset, if I were to use SIP-A first, it will be 'dead' unless I do another soft reset. However, if I were to use SIP-B first, then load SIP-A, it will be fine throughout the session. See if you are having the same problem.
Hmm, that's a bit different from my problem, where all custom SIPs first works then don't but here is a question:
Are SIP-A and SIP-B from the same company? Perhaps they are using some shared component which one fails to load but other succeeds?
Just a thought...
Hi folks,
As I have locked out my SPV-M2000 and can't figure out the keys for the keyboard (see here), I need to try and track down some of the SMS/MMS messages stored on the device.
I can still browse via my PC, but I don't know where they will be stored or if I can retrieve them.
Any ideas?
Well, changes are, if you were to copy everything off your phone, and copy them all over back to them, chances are the stuff will remain.
However, I think it ought to be best if you can solve your keyboard problem.
For your keyboard, I'm not sure how a BA works, but default a Wizard keyboard starts without Cap, and a CAP will be on until you off it. And Shift and Fn will only function while you are holding it (kinda like the Shift key on your PC keyboard). I'm not sure, probably you've got your number wrong? As I guess, you will need to use the Fn key for typing a number (not sure how your keyboard goes).
ANYWAY, I guess you aren't getting much of a respond because you've not got your info out as much as you should. First of all, it may be not as "generally" as you think. And, not all people know what a M2000 is and they don't borther to look for it. Although I hate people with multiple posts, I guess it would be good if you could repost this on the BlueAngel forum and try your luck there, eps the keyboard issue seems very easy to solve.
I'm trying to get AndroidControl working, because my screen and digitalizer is broken on my XT907. The issue I'm running into, is that AndroidControl never recognizes the device.
Running through the cmd, adb devices doesn't list it, so it's not picking it up. I understand that adb must be enabled on the phone, but can't find a way to do this, since the screen is broken. Every fix or workaround involves some other program or action that requires seeing the screen or having touchscreen capabilities, which I obviously don't have.
Is there anything I can do to get this taken care of ? Neither my roommate nor I can find anything that works. Please help!
Hi all.
Basically, my display and touchscreen aren't working. For why, you can see here: http://forum.xda-developers.com/goo...eakerphone-t3043151/post67360800#post67360800
So I managed to get access to files (pictures mainly) on my phone by, without access to the screen/touch, installing TWRP and entering into recovery mode and using ADB (pull). Installing TWRP was all from computer, and I didn't have much interactivity with the phone itself during this process. Luckily my phone already had unlocked bootloader (which I believe during that process you have to confirm something on the phone itself?).
So now, I want to go a bit further and get more access to my phone. Best way to do that, for me, seems to use VNC server on the phone. Unfortunately I don't already have one installed. And it looks like most of them need root access?
So (as the subject implies), I'm wondering if its possible to root my phone from my PC without needing to do anything on my phone -- well, if I need to push volume up/down and power button to select stuff, that could work, just can't press anything on screen of course.
Assuming that is possible, I'd have to find a nice VNC server apk and install it via ADB install, correct (sorry I'm not very experienced in all this).
Assuming that works, I'd need to ensure that the VNC server starts on boot.
Assuming that works, if I remember correctly from when I was rooted before, when the VNC server (or any root-needing app) starts, SuperSU pops up and asks if I want to grant that app access. So somehow I'd have to have SuperSU (or whatever alternative) automatically grant it...
So, anyone think this is possible? If so, any hints?
I'm also open to any other way to gain more access to my phone (ie, not using VNC etc), if anyone has any feasible suggestions.
Thanks
snoopac19 said:
I'm also open to any other way to gain more access to my phone (ie, not using VNC etc), if anyone has any feasible suggestions.
Thanks
Click to expand...
Click to collapse
What exactly do you want to access on your phone?
Hah. Good question. I don't really know. Wanna poke around and see if I'm missing anything.
I know I missed a bunch of WhatsApp messages that came in while phone was on and I couldn't see anything. Of course that's not super important.
Basically would like to poke around to see if I missed grabbing anything.
Now that I say it out loud (or type it on the forum), I begin to think it's not worth the hassle.
Maybe the real reason is the challenge, and seeing if it can be done?
Like I said. Good question!
I had an issue when Android 12 (it might have been Android 11, can't remember) first came out where my physical Keyboard connected through USB wouldn't type. I searched for hours on end and FINALLY found something in the official Android docs where you can change either a global setting or a flag to allow keyboard input under certain conditions. I can't remember for sure what it was, but I think it's either while a screen overlay is detected or while an accessibility service is running. Well, here I am years later with that same problem again. Only this time, I can't for the life of me find the answer. If I remember right, I had to put in an ADB command to set a certain flag to allow it. I've searched XDA and Android docs for hours but cannot find it. Please, someone help before I go insane. I really need my keyboard to work.
Edit: nevermind I found it! For anyone looking for the answer, go to the docs here: https://developer.android.com/about/versions/12/behavior-changes-all#untrusted-touch-events
You can fix it for a specific app by doing `adb shell am compat disable BLOCK_UNTRUSTED_TOUCHES com.example.app` or for all apps (doesn't always work) by doing `adb shell settings put global block_untrusted_touches 0`