Hey Guys,
Can someone build a script or tell me if this has already been done? I have a verizon Omnia i910 running Win Mob 6.1. I am also using SPB Shell 2.1.4 Every time I soft reset the device the Voice Command gets disabled. I have to go into the settings>Personal>voice command and check the "Enabled" setting. The problem is that my SPB Backup resets my phone every night after backing up my phone. So every morning I have to go back in and enable the voice command. I would really appreciate the help or any suggestions in how to fix this.
Robb
No idea why this thread is here (please have a look at the stickies in this forum; this has nothing to contribute to Development or Hacking).
Anyhow, find the exe in in Windows folder, copy and paste the shortcut in windows>start up.
Moved to appropriate forum.
Sorry I put it there as I though it was pertaining to somone helping me develop a program to set the voice command to enabled upon soft reset. Sorry if that was wrong.
Robb
Related
Having installed Dutty's WM6.1.5.2.19209 I installed Resco keyboard.
I cant select the Resco keyboard - Transcriber and Symbol pad can be selected, but if Resco keyboard is selected it immediately goes back tp PCM.
I've tried all the suggestions I can find in these forums:
1.) Installed Default IM Selector (selected Resco, then soft reset)
2.) Installed SIP Change (selected Resco the soft reset)
3.) Start > Settings > Input (selected Resco...)
No effect. Any ideas?
yes I got any problem with Duttys_WM6.1_5.2.19400_1_64.08.21[Cube] rom
<Mean>
You obviously didn't read Dutty's thread before flashing this ROM.
</Mean>
If you browse to the appropriate Dutty thread, I guarantee you that within 6 posts from the top (hint: LOOK AT POST 5), you will find your solution. In the future, please check the thread for your ROM before creating a new thread. It is highly likely that someone has already run into your issue, and the solution is posted in there.
i have the same issue and have read the thread but it still doesn't work
Download the 3 files attached in Post #5, then follow the instructions in Post #1185.
I think your comments were a tiny bit mean, but understandable as a lot of people don't read the threads before asking the same question over and over again.
Sadly, I have been reading threads for days now, searching for every keyword I can think of, followed the instructions (including installing SIP Change. Select which keyboard you want. Then install Default IM Selector. The select the same keyboard. Then soft reset.) and I still can't get it to work. Maybe I'm doing something stupid, so here is what I've tried in full:
1) Initial preparation...
Start with a SIM unlocked TYTNii from Orange (Kaiser130)
PIM Backup
HARDSPL - didn't work (white screen) so tried JumpSPL1.56-kais.exe
JumpSPL1.56-kais.exe didn't work either so tried JumpSPL1.93-kais.exe
JumpSPL1.93-kais.exe worked fine.
Flash hard SPL using KaiserCustomRUU
2) Flashed Dutty's ROM
http://rapidshare.com/files/107917203/Ruu_Signed_Duttys_WM6.1_Official_5.2.19209_1_58_16 _27__FIX_.zip
As I type the following, I'll repeat each action so that I can document each message and behaviour accurately...
3) Hard Reset - everything looks great, but I don't like the size of the keys on PCM keyboard
4) I install Resco Keyboard using .exe from pc with usb connection.
There's an option to install as the default keyboard so that remained ticked. At the end of the install, there's a message "Unable to initialise the Resco Keyboard. Input method will be activated after the next soft-reset".
Soft Reset.
5) Test by opening Tasks application
6) Now that's really annoying, as it works straight away this time. Without having to run SIP Change or Default IM Selector. The only difference is that I haven't installed other software first.
So, thanks for your response which in a round about way fixed the problem!
Unfortunately Dutty's Apr 09 ROM saw many people running into your problem even after running the 3 CAB files posted by AllTheWay. Sometimes it took several times running thorough the steps until the change finally stuck.
I have the same annoying issue. I have tried many solutions to solve it, but all failed. who can give me the accurate answer? thx
It seems far too random to me. I wonder if anyone has a technical explanation of why trying it a few times seems to work.
[ Er, no I haven't searched the forums this time ;-) ]
You all know that this should have been in Dutty's thread in the first place. No need to continue posting in it.
Hi,
I am facing problem that, my HTC Touch HD freeze after show green window startup screen. I got to soft-reset 2-3 times in order to make it run fine.
I found the following in windows\startup folder. Does anyone know which program could make my gadget slow/freeze?
AutoStarter.lnk
ChangeScreen.lnk
DynaNIs.lnk
G4_SIP_SC.exe
iLock2.lnk
KAVMobile7.lnk
PKG.lnk
SecureService.lnk
Services.lnk
SuperStarter.exe
usemynls.exe
VPortBoot.exe
WKTASK.lnk
Please advice. Thank you
Which program last time you installed and the problem started? You remove that program and see whether it correct the problem. You can disable some windows start up programs by SKTOOLS if they are started from windows start up folder. You cannot disable any program if started from windows registry.
I've had my Touch Pro for a while now but I've always had one problem with it that is pretty darn annoying, & that is that the phone seems to auto-unlock when I'm receiving calls. And so, many times the phone has answered the call in my pocket & I've had no idea. Or worse yet, it's cancelled the phone call without me getting round to even take the phone out of my pocket. I wondered if there was any fix for this.
I'm pretty damn sure that I've seen this problem before when roaming around here & PPCgeeks but after spending the past half hour or so trying to look for a fix, I just can't seem to find one. And so, I knew that if I just posted a thread that someone would most likely be able to help me & it'd all be alot easier than me spending all day trying to find whatever it is I need.
Oh, & before you ask, I've not got any custom ROMs or anything on my phone. I've installed apps from here, & some other stuff, but it's all just on the standard XDA Serra ROM.
you could install the Tachi dialer which gives a sliding mechanism if answering the phone
or swtich on auto lock after backlight dim
Free program called slide to unlock "s2u2" will work, also, you can download the program Advanced Configuration, and there is an option to allow the default slide lock that is built into windows mobile. The screen will still light up, but, unless you unlock the screen, it won't answer the call.
S2U2 Thread on XDA>>>> http://forum.xda-developers.com/showthread.php?t=527523
Advanced Configuration Utility Thread on XDA>>>>> http://forum.xda-developers.com/showthread.php?t=317070
I tried the Advanced Configuration Utility program but whenever I try to load the program (obviously after installing it), I get an error message saying:
An unexpected error has occured in AdvancedConfig.exe.
Select Quit & then restart this program, or select Details for more information.
This application requires a newer version of the Microsoft .NET Compact Framework than the version installed on this device.
Click to expand...
Click to collapse
Clicking 'Details' doesn't seem to do anything, except give me the 2nd paragraph from above (about the .NET framework).
Where can download this ".NET Compact Framework", or does anybody know of any other programs/applications/utilities/whatever which can help me with this problem.
Oh, & yeah, thanks for the help guys.
Net Compact Framework v3.5
http://forum.xda-developers.com/showthread.php?t=432470
Alright well I installed that & I'm still getting error messages when trying to load the Advanced Configuration Utility program. However this time instead I just get:
An unexpected error has occured in AdvancedConfig.exe.
Select Quit & then restart this program, or select Details for more information.
Click to expand...
Click to collapse
And then if I click Details I get:
AdvancedConfig.exe
Exception
at
Microsoft.AGL.Common.MISC.HandleAr()
at
System.Windows.Forms.ImageList.ctor()
at AdvancedConfig.□.□()
at AdvancedConfig.□..ctor()
at AdvancedConfig.□.□()
Click to expand...
Click to collapse
So yeah, there's still some kind of problem. Though what it is exactly, I do not know.
try attached CAB and have a look at below thread.
http://forum.xda-developers.com/showthread.php?t=425650
Google Pocketshield. Great program.
Shield Tablet Bug Fix "missing home button, recent tabs, notification centre" Nougat
Hello Everybody. I have a Shield Tablet running Nougat. I have been experiencing the bug described in the Title a few times, and I finally found a way to solve such bug, at least in my specific scenario. It might not work for everybody but, as I have seen a lot of Users experiencing such bug and being forced to deal with it through a factory reset, I thought posting an easy guide might be helfpful to some. It is not rocket science, but for me it does the trick well. Should you feel there is an easier way to solve the same issue, please, do not hesitate to add it to this post.
I already posted this guide on the official Shield Tablet forum, but I cannot add the link because I am a new User (c'mon dudes, I am not spamming.. just trying to help ). Therefore, I am just gonna copy paste the guide. I apologise if the formatting is not ideal.
Hello Everybody, I know that there is an Android bug that has been creating issues for many years, also on shield tablets. When the bug starts, the home button disappears, it is impossible to open the "recent app" tab, the notification centre cannot be pulled down, and there are many other side effects. Since I started having this issue, I did quite a lot of research. Apparently, all I could find were information regarding how to solve the bug on Lollipop and Marshmallow, but nothing regarding Nougat. The way this bug is usually fixed is by starting the Setup Wizard on the device. Unfortunately though, I was not able to open it due to permission restrictions. Some guides mentioned installing Nova from the appstore, and setting up an action Widget in order to start the Setup Wizard. This did not work for me as well. What I was able to do, instead, was creating and setting up a new User profile, which then fixed the bug on my main User.
I am sure people more experienced and talented than me probably would have been able to find a neater way to make this happen. However, as I am quite a noob with these kind of things, I thought that writing a basic guide might be helpful for others as well.
Before going on, you should know that in my case, the only way to fix the problem is to have "debug settings" enabled on your device BEFORE the bug starts. When I first got the bug, I had not unlocked "debug settings" and I could not do it afterward, as tapping 7 times on the build number did nothing. You also need to have Android Debug Bridge (adb) installed on your computer and configured with the tablet.
Also, the process I will describing now creates a new User and switches to it by using terminal commands and Adb. I am aware that there would be an easier way to achieve the same result by going on "settings>Users" on the tablet. However, if you experience the same bug I was having, you will find out that clicking on the "Users" tab does nothing.
Here is a step by step guide of what I did:
1
Normally boot your tablet and connect it to the computer via usb cable
2
Run a command prompt windows on the computer and run Adb. Even if, due to the bug, you won’t be able to transfer files to the tablet via USB, adb should be able to interact with the shield anyway. To double check this, type the command: adb devices . You should be able to see your device listed.
3
It is now time to create a new User through the command prompt. You can do that by typing the command:
adb shell pm create-user User_Name
Once the new user has been created, the prompt will show you the respective User_ID. You will need to type such number in order to switch to that user, by typing the command:
adb shell am switch-user User_ID
eg. adb shell pm create-user Charlie
Success: created user id 11
adb shell am switch-user 11
4
Your shield should have now switched to the new user just created. At this stage, finish the new user configuration stage on the tablet. Skip all the google services related options, as you do not need them. When the configuration process is finished, the home button, the notification centre, the recent app, etc. should be back. Now that the bug is fixed, it should be possible to go back to your main User profile by simply switching User from the settings menu on the shield: settings>Users. At this stage, if everything went well, you should be logged with your main User, and the bug should have been fixed. It is now possible to go again on settings>Users and delete the new User created on step 3.
This is it. It works well for me and, even if I do not exclude that the bug will present itself again at some point, this is a 5 minutes solution to fix it. I apologise for any english mistake, as English is not by main language. Also, somebody might know of an easier way to solve the issue on Nougat, although I was not able to find any online, and that is why I wrote this short guide. I hope it will be able to help some of you!
Have a nice day!
Alberto
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`