Ok, I'm hoping someone may have some idea why this error is plaguing me.
After a hard-reset, the following behavior is observed on the T-mobile 3.14 rom.
1. Set Ringer (or leave at default) to anything.
2. Hit Ok.
3. Change volume to either Off or Vibrate.
4. Go back to phone options - ringer is now set to "BellDitty".
Odd thing is that when volume is restored, the phone doesn't play anything when an incomming call is received - not even the listed "BellDitty".
Anyone know what the problem is? How to work around it? Is the ringer just set in the registry? If it is, then it could just be a case of writing a program to restore the ringer ever 2 sec. or so.
Hope you guys can help - a phone that fails to ring is a misbehaving in my book.
Thanks.
Fixed!!!
After doing some hunting, here is what I found. If you guys have some spare time, try doing this to your phones and see if you have the same oddball results. From what I found:
When the Pocket PC is put into Mute, a key in the registry (HKCU\ControlPanel\Sounds\RingTone0) named Sound is set to *none* or *vibrate* depending on what you mute to. There is another key in that branch named “SavedSound”, which has the ringer you setup in Phone options. Now, as long as you don’t go into Phone options and hit “Ok” while the phone is muted, the registry keys work just fine – as soon as you unmute, the value of “Sound” gets set to whatever “SavedSound” is. HOWEVER – if you do go into phone options and hit OK, it confuses PPC 2002. It writes the new sound to the “Sound” key, however it never cleans up after itself in the same way it would if you unmated. Now when you unmute, it looks to the Sound key to see if it says *none* or *vibrate* so it knows to re-enable the ringtone. When it finds the saved value from the phone applet (that you hit “OK” to) it assumes that the phone was unmuted, even though it wasn’t.
Re: Fixed!!!
dadarkmcse said:
After doing some hunting, here is what I found. [...]
Click to expand...
Click to collapse
Well researched !
[ I've had this thought more often: do we have a Microsoft representative in the room here? If not, I guess we need to have some protocol for reporting issues from our collective brain back to the developers. (But ofcourse MS really needs to be here and read the forum if they're serious about making this a real phone.) ]
Related
Is there a registry tweak to allow the speakerphone to stay enabled when you close the flip? Currently it ends the call.
I believe the same thing happened with the old MPx220 and the MPx200 but nothing was ever figured out for these phones.
I would like to know this as well.
Bump - Speakerphone while lid closed...
Any news on this?
My Googling is telling me thus far - NO! NO! and NO!
Any Russian Gurus care to negate this?
speakerphone
Ok, I am trying to figure this out, here is what I have so far,
I have two 3125's, one was running an old dopod rom and the other the most recent Cingular release. (will get numbers later)
On the old phone, if I hit the "lock keys setting" (press and hold home button), while on a call with the speaker phone on, I can close the phone, the call continues and the outer display shows the call info (ie, who the call is to and connection time)
One the newer phone, with the same setting, the phone just hangs up when you close it.
I backed up the old phone with sprite backup, then ran sprite on the newer phone thinking maybe the registry setting would carry over (in case I was missing something), but the newer phone still just hung up when closed during a call.
After several rom changes I remembered why I quit using the old phone, the charging port came loose and does not work, so my guess would be that the old phone stays on due to the broken charging port, what leads me to this is of course if you have the headset in, the phone can be closed while on a call.
Where does that leave us? It would seem that the issue is not a registry value change (although I won't give up on trying to find one) but a software issue and until someone figures out how to change it were are stuck with no closed speaker phone.
Morning guys and girls
Does anyone know of a way to make a registry key read only on WM6?
The reason I ask is that I get my direct push email via my work exchange server, but the lovely admin has decided to set a 5 min lock out policy that HAS to be implemented on the phone to accept the emails.
Basically that means every 5 mins the phone locks up and requires a PIN to unlock it, very annoying to say the least (I know its a security feature, but when you quickly want to check your emails/calender, its just annoying )
So, after many hours of searching through the registry I've found the key that decides how long the "lockout" interval is:
HKLM\Comm\Security\Policy\AE\{loadsofrandomnumbers}\AEFrequencyValue
Now this key is set to 5 as default (as its a 5min lockout rule) but when set to 999, I get 16.7 hours where I'm not bugged by lock outs. But back to my original question, the policy must "re-apply" its self every day as the offending reg key gets set back to 5 quite often. If I could make that reg key read only, then it wouldn't be able to change it back.
Thanks in advance guys!
Unlikely there is a way to make it read-only. Much realistic way to solve it is to
[1] hack the policy
[2] change the key just after is has been applied.
There is a home made software, RunEveryday (available in this forum) that runs your specific program everyday. If you were able to make a program or possibly CAB to change this, probably you can change it everyday.
Sorry to sound like a complete noob, but I'm attempting to write my first cab and have got this far...
[Version]
Signature="$Windows NT$"
CESignature="$Windows CE$"
Provider="mixmasterollie"
[CEStrings]
AppName="PIN Hack"
[SourceDisksNames]
1 = ,"Files",,.
[SourceDisksFiles]
"SAMPLE FILE.TXT"=1
[CopyFiles1]
"SAMPLE FILE.TXT",,,0x00000000
[DestinationDirs]
CopyFiles1=0,"\Storage"
[AddRegistry]
HKLM,"Comm\Security\Policy\LASSD\AE\{50C13377-C66D-400C-889E-C316FC4AB374}","AEFrequencyValue=0x0003E7"
[DefaultInstall]
CopyFiles=CopyFiles1
AddReg=AddRegistry
I've got cabwizsp.exe, makecab.exe and cabwiz.ddf, dragging my above inf on to cabwizsp.exe creates me a cab, but the cab doesn't "successfully" install
I'm not too sure I've written my "AddRegistry" bit correctly if anyone would be so kind as to correct it?
Thanks
I would use SKschema and write a little script which just overwrites the reg key every couple of minutes. Or use the (free) MORTscript.
Wasn't there already a hack to disable this policy? I'm sure I've seen it, about 6 months ago.
Since the lock is activated immediately, rewriting the registry ever minute or so won't really help I guess. However, in other cases, I would suggest using the state and notification broker to monitor the registry keys, get notification of a change of state, and immediately overwrite it.
V
hello.
i have a 32 gb hp touchpad overclocked.
when i turn it on i have sound working good.
but after very quicly, it have no more sound at all (even when i push the sound + or soung - button, i see the sound logo going up and down but no sound)
and if i turn it off and on the sound come back.
do you know what can be the problem ?
Thank you
Happens to me ALL THE TIME. I just chalk it up to WebOS being completely unfinished. But then again it could be some of the patches I have installed, since I spent all of about 3 minutes without them.
Me too, I read that Making a call in skype will bring sound back.
Apparently it helps to disable system sound, keyboard and vibrate.
Happened to me twice more today. So annoying.
Happens to mine pretty much daily. I don't see a whole lot of *****ing in general about it though, mostly here and Precentral, which leads me to believe it's mostly "modified" touchpads with this problem. I'm thinking it's a patch or kernal problem.
It's most likely a problem with a kernel or patch. I have 3 16GB's, two stock, one modded, and none of them exhibit this behavior. Since all of you have modded yours, I suggest removing patches/kernels and see if the problem persists.
parisien99 said:
hello.
i have a 32 gb hp touchpad overclocked.
when i turn it on i have sound working good.
but after very quicly, it have no more sound at all (even when i push the sound + or soung - button, i see the sound logo going up and down but no sound)
and if i turn it off and on the sound come back.
do you know what can be the problem ?
Thank you
Click to expand...
Click to collapse
te)
Install the Preware Linux App > Increase TouchPad Volume ( Lite)............
See if it makes a difference
I haven't figured out what causes it for me, but a simple solution to fix it without having to restart is to run a couple commands in xterm..
stop pulseaudio
start pulseaudio
Sound goes off (ANNOYING)
Why does the sound go off all of a sudden, I hate it, I can't even hear youtube videos, it requires a restart
Sent from my SCH-I510 using XDA App
Finally , I had to disable the email audible notification (left the vibrate only). Now it has been OK for more than 1 week, before it will lose sound in a few hours.
Hope HP get's this resolved.
Thanks
trialdoer said:
I haven't figured out what causes it for me, but a simple solution to fix it without having to restart is to run a couple commands in xterm..
stop pulseaudio
start pulseaudio
Click to expand...
Click to collapse
If you install the "Advanced Reset Options" patch, you can use it to restore your sound...
Just hold the power switch until the buttons show up, then tap "Cancel".
Hi,
Advanced Reset option does not fix the issue for me (unless I select Reset).
Sound fails even if the only App I have opened since a full reboot is the email App.
Maybe one of the installed Logging patches is causing the sound to drop out? Maybe we should enable logging to see if the logs give any indication around what is causing the sound issue?
this issue was happening to me everything my touchpad would go idle for longer than an hour (super annoying) however I gave all the suggestions here a try and finally had luck with robrob777's suggestion! Turning my email notification sounds to vibrate has seemed to fix my issue hasn't happened in 2 days. Just wanted to say thanks robrob777!
gburt said:
Advanced Reset option does not fix the issue for me (unless I select Reset).
Sound fails even if the only App I have opened since a full reboot is the email App.
Click to expand...
Click to collapse
There's an article over on precentral about fixing the problem, though it really isn't a fix, but rather a way of getting your sound back without a reboot. See it at:
www
precentral.net
/
fix-your-touchpad-s-lost-audio
Sorry about the format of the link, but forum rules for newbies prvented me from posting it properly. Since it obviously isn't spam, I am hoping I won't be in trouble for it.
It's complicated, and you might find a reboot easier, but perhaps some developer who's into patches will spot it and come up with a more permanent fix, either to fix the problem itself, or at the very least, to have the stop/start fix applied when the volume control button reaches max and is pressed again once or twice.
Update: It just became a little easier to apply the start/stop "fix". XServer, Xterm, and Xecutah just became available on webos-internals (.org). Just use Preware, select Applications, All, and the new stuff will show at the top of the page. Just download Xecutah and the other two packages will download with it if you allow it.
Update 2: Even easier...
After installing the X stuff, start Xecutah and create a shell script in the default directory you land in with Xecutah. I just used cat and typed it in.
cat >fixaudio
Here's what I put in it...
#!/bin/sh
stop pulseaudio
start pulseaudio
Then, fix up permissions...
chmod 070 fixaudio
(It's been a while since I used Unix/Linx, but I'm sure someone will correct my permissions choice if it's not right).
Then, when your sound goes away, start Xecutah and type fixaudio.
Even better... Use Preware to find an app called PulseAudio Restarter. Works well.
Hello guys,
I am having this issue with my device - sometimes when I press the home button the Voice talk / command powered by Vlingo starts. I always press the button just once (I understand that it should happen when one double-presses the home button) and it is very annoying :-(
Note, that I have Settings/Motion/Double tap turned off as well. Is there any way to fix this or do you have any idea what may be wrong??
Thanks in advance!
Sent from my GT-I9100 using XDA App
while in the motion settings, you can see the tutorial clip and that double tap has nothing to do with the home button, but with double tapping the top side of the device to start voice control instead of saying "hi galaxy". so even with that switched off, your device will react to hitting the home button twice and does not really help diagnose the initial problem.
either you have a slight hardware defect in the home button, a software issue (or maybe user error). since hardware would be more severe, let's see the software side first. what exact rom do you have? device rooted or not? anything that could mess with voice input (connected bluetooth hands free, market vlingo or other tts or stt software installed...)?
also, just to exclude user error, let another person try.
P.S. are there special circumstances when this happens? like only from deep sleep, only when charging, with a connected headset, running certain apps or whatever?
Chef_Tony said:
while in the motion settings, you can see the tutorial clip and that double tap has nothing to do with the home button, but with double tapping the top side of the device to start voice control instead of saying "hi galaxy". so even with that switched off, your device will react to hitting the home button twice and does not really help diagnose the initial problem.
either you have a slight hardware defect in the home button, a software issue (or maybe user error). since hardware would be more severe, let's see the software side first. what exact rom do you have? device rooted or not? anything that could mess with voice input (connected bluetooth hands free, market vlingo or other tts or stt software installed...)?
also, just to exclude user error, let another person try.
P.S. are there special circumstances when this happens? like only from deep sleep, only when charging, with a connected headset, running certain apps or whatever?
Click to expand...
Click to collapse
Hello, thanks for your reply. I am running the device with an unmodified SW i.e. stock rom (having a branded phone from orange slovakia), no rooted just some apps installed from the android market. It is XXKE4/XWKE7, running android 2.3.3. I dont use bluetooth or handset nor dock or anything like that.
The issue seems to be completely random to me, while I usually notice it during browsing web with opera, but it happens with more apps. I don't know what is tts or stt sw, nor market vlingo. If you would like to know some more details please let me know what would be relevant for you.
I already thought about the hw issue, but I am not sure if they would accept the warranty claim as it is quite random. I thought there would be some way to completely disable voice talk as I dont expect to use it anytime in the future anyway...
As of the user error, it happens both to me as well as to my gf while using the phone for common internet use.
Sent from my GT-I9100 using XDA App
ok, that gave us something to work with. for future reference, when asking a question like this, it might speed up the process by giving as much information in the initial post as possible and let me explain why:
the fact that you use your unrooted stock rom tells me, that it is not a common and maybe reported bug that comes with a custom rom, and with an unrooted device, it is rather unlikely, that you screwed up a system component like this.
bluetooth, docks and handfrees could influence the voice input and its triggering by having their own triggers, but that is not the case.
if it happens to other people with your phone as well, it excludes your personal behaviour, tremors or whatever (no offense, you never know, just to cover everything, some people are shaky).
if it happened only in a special state, like only while sleeping for a minute or while charging, it would ensure, that it has something to do with deep sleep.
about the other things: with tts i was referring to text to speech, the engine that reads out display content, like incoming calls, text messages or navigation instructions, stt refers to speech to text, like voice input, saying hi galaxy, telling where to navigate or dictating notes...
vlingo is the engine that is used for voice talk and voice command and there is also a 3rd version, that can be downloaded on the android market, coming with yet other features and having them all present and maybe screwed up settings might have influenced anything there, however, this doesn't seem to be the case either.
so this leaves few options for how to proceed. in your place i would start off with reading this thread: http://forum.xda-developers.com/showthread.php?t=1097153
it deals with home button issues and a theory on how the home button sometimes might react as much as 15-30 minutes later than initially pressed, which might coincide with an actual press and being registered as a double press (although that's a stretch at best).
and when it comes to a next step, if you made sure, that does not apply to you, i would be uncertain, which way to go. a factory reset might help, but if, after hours of setting the device up again, you realize there has not been any change, it was nothing but work. then there are 2 things left:
either flash a newer rom using odin and any rom from here: http://forum.xda-developers.com/showthread.php?t=1075278 (full guide and download links included)
OR decide to send it in for warranty first and see what's what.
flashing a rom might solve your problems but influence your warranty state, if not done correctly and cautiously, which would make sending it in risky.
sending it in first and not getting that bug recognized or repaired for free would mean you might end up with weeks without your phone and/or a huge bill and the same issue as before.
i guess i would get a usb jig, read up on flashing, try several stock roms, not root the device and see if the bug is gone, if not, flash back to stock, make sure the flashing is not traceable and then try a local store or your carrier for a hardware replacement or repair.
When i got this device i thought how stupid this was and hoped after flashing a custom rom maybe it would eliminate this stupid feature of this device. It seems HTC thinks it's a good idea to turn the screen ON after ending a phone call, WTF?
At work i use my bluetooth headset all day with my phone in my pocket. I will take my phone out, dial the number i want to speak to, press power to turn screen off, put device in pocket and have my conversation. I end the phone conversation with my bluetooth headset and guess what? The dang phone's screen turns on while it is in my pocket. I guess the light sensor has zero effect here! So now since this happens and my device has a timeout of 2min i set before screen turns off my phone accidentally "butt dials" people and without me knowing i'm now calling people randomly while i'm working!
Another case. I have my phone in my car's cupholder, i use bluetooth to make a call with my car, it initiates the call to my phone and again it turns the screen ON to make the call. WHY? I never pressed power on my device to turn the screen on to make a call. So again i press the power button to turn screen off while in call. I hang up the call when i'm done via the bluetooth in my car and again the device turns the screen back ON once i disconnect the call via bluetooth.
I just don't understand the logic behind this? Is this some HTC thing or all android? Coming from iPhone 4 never had this issue so was a first for me with this device. Just don't see the reason or logic for this?
Anyway to prevent this or stop this from happening? I mean isn't that the point of bluetooth to not need to touch your device thus no need for the screen to be turned on????
+1
It seems that this is not a HTC thing because I have the same behavior on my Samsung device. Same problem as well with pocket dialing during/after a call. Really annoying. I had the same thing on my old HTC Nexus One running Froyo, so this is not a new bug. Back then I tried a lot of different apps, and none helped. I even flashed CyanogenMod on it and it didn't change anything.
I really hope someone has run across a fix whether it's an app, a patch or a whole new ROM, because pulling my phone out of my pocket to turn the screen back off TWICE for every call I make or receive is getting to be a pain.
I can't believe this behavior is voluntary on the part of the designers. If it is, please someone explain why.
You can use TASKER(automation app at Play Store ) to Get you screen off after a call or while connected to the bluetooth ..
ethanon said:
You can use TASKER(automation app at Play Store ) to Get you screen off after a call or while connected to the bluetooth ..
Click to expand...
Click to collapse
Just downloaded but no idea how to use this thing. Not very saavy with this type of stuff. How can I use tasker to turn the screen off when ending a call ONLY while connected to a Bluetooth headset? This is my biggie since it's in my pocket.
Got it to work
Ok, I downloaded Tasker and I'm impressed.
Here's how I got this to work:
1: Create new profile using STATE, then go to NET, then hit BLUETOOTH CONNECTED. Here you can specify if you want only a specific device or any Bluetooth.
2: Set new task: SET plsLock to ON
3: Set exit task: SET plsLock to OFF
4: Create new profile using EVENT, then go to PHONE, and hit PHONE OFFHOOK.
5: Set new task as: SCREEN, SYSTEM LOCK
6: Hit IF, and specify if plsLock is ON
7: Create new profile using EVENT, then go to PHONE, and hit PHONE IDLE.
8: Set new task as: SCREEN, SYSTEM LOCK
9: Hit IF, and specify if plsLock is ON.
You're done.
Since I had the same problem with the wired headset, I also created a profile with HARDWARE, HEADSET that sets the variable plsLock to ON and exit task sets it back to OFF. You can name the variable anything you want and it will still work.
If anyone has a better/simpler way of programming this, please share. I just started using this program and am still trying to wrap my head around the way this is structured.
As this stands, it works... But it's still a patch on something that should be an option in Android.
Let me know what you think.
Ok thank you I'll give it a try. Yeah could never understand why my device thinks it's a good idea to turn screen back on after ending a call via Bluetooth or not? I receive call, I then press power button to turn screen off bit continue my call, the caller hangs up, boom my screen turns on displaying the phone dialer until my time out settings turn screen off. Dumbest feature I swear. Hello phone I pressed power offbutton to turn screen off, get the hint and keep screen off until I press power button and want it back on again. No sense...
Deeznuts, did you manage to get it working with tasker ? I guess it is the only possible way to get to your objective. Learning Tasker will give a new dimension to your phone. More over I will try to make a profile for your and get working .
For some reading
http://www.pocketables.com/2013/06/...rt-0-tips-and-tricks-for-learning-tasker.html
ethanon said:
Deeznuts, did you manage to get it working with tasker ? I guess it is the only possible way to get to your objective. Learning Tasker will give a new dimension to your phone. More over I will try to make a profile for your and get working .
For some reading
http://www.pocketables.com/2013/06/...rt-0-tips-and-tricks-for-learning-tasker.html
Click to expand...
Click to collapse
No unfortunately not. I would greatly appreciate that! I would think it's a simple task but honestly I'm very handicapped when it's comes to stuff like this.
Basically a string for tasker that would simply just do this:
When my device is connected to a Bluetooth device whether it be my car kit, headset, stereo headset, etc. and a phone call ends where by me pressing the End Call on screen button, by ending call with car kit, headset, etc, doesn't matter but will make the screen turn off. That's it.
When connected via Bluetooth, a phone call ends, screen turns off.
Now here's a kicker and not sure if this part would be harder. I'm connected via Bluetooth headset or device, I have screen on to manually make a phone call, then while on the call I press the power button to turn screen off while on call and put device in my pocket. Now when the call eventually ends I would want the screen to stay off.
I will read into the link you provided and mess with it somewhere. Thank you for your time and help.
Correct me if I am wrong , you mean to say that no matter what you want your screen to stay off after a call ...
ethanon said:
Correct me if I am wrong , you mean to say that no matter what you want your screen to stay off after a call ...
Click to expand...
Click to collapse
Correct BUT only when connected to a Bluetooth device. My gripe is on a Bluetooth call, place a call manually then talk on headset, car kit, etc. I press power button to turn screen off then put phone back in pocket, when call ends the phone turns screen back on for some reason. Never understood this?