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.) ]
Hello,
I've got my HD2 for 7 months. Since I bought it I'm experiencing a small difficulty concerning voice calls and light sensor.
When calling, the light sensor detects proximity of my head (ear) and when the phone is close enough, display darkens and locks to avoid pushing buttons by cheeks and such stuff. That's quite handy sometimes.
My issue is, that when I put my HD2 next to my head (enough to darken the display) while dialing someone, the second when the dialed number accepts the call, my HD2 automatically hangs up.
If I dial the same person again without putting HD2 next to my head, the call connects and everything is OK.
So my question is, what is the reason for my HD2 to automatically hang up when the display is dark and how to avoid this situation? Is there some registry fault and fix or something similar?
It's driving me pretty crazy Please help.
Thanks in advance, Pete.
I think its a registry thing. I never experienced this, although i hear a lot of people complaining about it.
Solution to the issue
So finally after consulting few people over the internet, I've come to satisfying solution.
The basic idea is to backup, wipe everything out using hardreset and then restore everything back to its original state.
As backup&restore software I used SPB Backup 2.1.
I've done 3 tests: before reset, after reset&before restore, after restore.
First one went bad, as expected, second and third ones went good....
So everything solved, thanks for your attention
Hi guys. I'm totally new to the android/smart phone world btw. Anyways, I recently got my Samsung Galaxy S2... first thing I noticed, my touch screen wasn't working. I popped the battery in and out and then it started working as it should.
My phone was working fine this morning, then all of a sudden out of no where, the touch screen stopped working again. I've tried turning on/off the phone multiple times. I've taken out the battery and even my SIM card nothing... i'm worried.
Has this happened to anyone else? Is there a fix? Do i have to go through Samsung? I hope not. Incase anyone asks, I did not root my phone.
Any help/feedback would be appreciated.
When the touchscreen stops working... were you charging the phone at that time?
The first time i turned on my phone, was actually by accident and it was charging.
However, just earlier now, it was not. it was just sitting on my computer desk. The home button, lock button and touch capacitive buttons work.... but i can't get past the lock screen
you could try a factory reset to see if its software related, but it sounds like hardware. I would definitely Return the phone .
I guess I can't do a factory reset, since I can't get into any of the menus... man this sucks. I spent $900 *gulp*
To do a factory reset,
1. Turn the POWER OFF, pull the battery out and put it back again.
2. Simultaneously press and hold the Volume Up, Home and Power button
3. If the Samsung Symbol appears, release the Power button
4. A Boot Menu will then show, Use the volume up/down to choose wipe data/factory reset.
touch screen not needed this way.
oo that's interesting... I tried it. and it didn't get to a boot menu. maybe I was doing it wrong. I tried a few different ways, but no success. It turns out I have warranty with the store. They're going to replace it for me Thanks for the feedback guys. Awesome forums.
Something similar happened to me yesterday. When I had the in-box USB cable attached to a BoxWave VersaCharger (combined AC/DC charger), and the VersaCharger was plugged into 120V AC, the touchscreen would stop working. As soon as I unplugged the USB cable from the SGS2, or plugged the VersaCharger into a 12V DC lighter socket, the touchscreen would work fine.
I've got the same problem as the OP... I had my phone charging overnight and this morning when I first went to use the phone I could not unlock the screen. I could wake the screen via the home button, and see I had a missed call etc but it just wasn't responding to touch. BTW I can't remember if when I first tried to unlock the phone if it was charging or not but really this shouldn't matter.... oh and btw, I'm not rooted or anything either! Naturally I rebooted the phone but still the same problem....so I tried a battery pull and still the same problem. Just now I did a factory reset but the touch screen still isn't working! I guess this is a hardware problem so I'm going to get it fixed under warranty by Samsung! Gutted that I will likely be without my phone for a week or 2!
EDIT, UPDATE...
Well, I was just on my way to the repair shop Samsung warranty had told me to take it too, and I took my sim card out to put in my old Hero (the only thing I hadn't tried!) and I couldn't believe it but the touch screen started working fine again! Weird, but that is now my advice if anyone else has a problem with their touch screen not working - oh and I took the sim out whilst the phone was still turned on. Crisis averted!
UPDATE 2
Sadly this has happened about 4 times to me now and I'm just waiting for the inevitable next time. Each time doing a factory reset then taking the sim card out seems to bring the screen back to life (though last time not immediately) but I shouldn't have to put up with this. Problem is, I don't want to send off a seemingly perfectly working phone to get repaired as I fear they will struggle to notice the problem, never mind fix it! I'm hoping a new firmware comes out soon, in the hope that it may resolve my issues...
Me as well ...
I have had this happen to me twice now (Touchscreen not responding).
The first time I had just installed a game and thought it must have been related to that. Pulled the battery and no joy, left it for a while and it came back to life...
Second time I was surfing the web and it stopped responding, pulled the battery and left it for maybe a minute but no joy .... pulled the battery again and left it for probably 20min and it came back to life. When it came back up I noticed the livewallpaper had been turned off and my widgets were gone from the homescreen.
What I did notice when it wasn't working was it had "safe mode" displayed at the bottom left of the screen
Have the Same Problem
Have the same problem i Mine and was super exicedat first it worked fine and after charging the touchscreen stopped working i pulled the battery out and put it back in but no luckso im gonna return mine to the shop hope they replace it
Moral:AT FIRST SUPER EXICTED BUT NOW SUPER ANGRY
Same issue - Is there ANY way to save my data before I send it in for repair/replace?
Hi all,
As of this morning, I have exactly the same issue as the OP. Screen doesn't react to touch, with the exception of the capacitive buttons. I found a dude on YouTube that had the same issue: youtu.be/0oIdllWiV4I
The last thing I did with the phone before it started misbehaving was to answer a call. The phone was on the charger when the call came in - I can't recall whether I unplugged it before answering, or after, or at all during the call. Not sure it has any relevance anyway, only mention it because I've seen reports of people's screens no longer reacting to touch when the phone is plugged in to a charger (apparently it even states in the manual that this may happen).
Anyway, whilst all my contacts, SMS, photos etc are backed up to the cloud, the same can't be said for my app data. Before I lose hours and hours of progress in various games, or all my settings in numerous other apps, etc, can anyone think of any way to get access to the memory of the phone, bearing in mind the following:
I can't connect to Kies to pull a back-up because bluetooth is currently enabled on the phone and when one connects the USB cable, it says "Activating USB mode will deactivate Bluetooth. Continue?" but I can't click the Yes button
I can't connect in USB mass storage mode because I can't navigate to the settings menu entry to enable it
I can't turn Bluetooth off in order to get Kies working, becuase I can't get to the settings menu or pull down the notification bar to reach the power control.
I can't use Voice input to control the device (on the off chance there was a "bluetooth off" voice command) because (presumably with the most recent firmware I flashed via Kies a few weeks back) for some reason Vlingo is no longer the app on the double-home button action. Instead it calls Samsung Voice and wants to walk me through a first use tutorial, but I can't click the next/skip buttons
I installed via Android Market push the app belonging to www_remoteaccessphone_com as it promises to be able to remotely switch bluetooth off, but the website says I haven't installed the app yet, presumably because alrhough I was able to install it without touching the phone, it probably needs to be run at least once to set it up, and I obviously can't do that
I can't start Kies Air to try and get my data that way (starting it would require using the touch screen)
Kies via bluetooth isn't supported on Android
Needless to say, the data I'm trying to retrieve is on the internal memory, not the SD card. As you can see I've been trying all sorts of creative things, but I'm fairly sure I'm screwed. Any bright ideas I haven't thought of?
blaubeer said:
Hi all,
As of this morning, I have exactly the same issue as the OP. Screen doesn't react to touch, with the exception of the capacitive buttons. I found a dude on YouTube that had the same issue: youtu.be/0oIdllWiV4I
The last thing I did with the phone before it started misbehaving was to answer a call. The phone was on the charger when the call came in - I can't recall whether I unplugged it before answering, or after, or at all during the call. Not sure it has any relevance anyway, only mention it because I've seen reports of people's screens no longer reacting to touch when the phone is plugged in to a charger (apparently it even states in the manual that this may happen).
Anyway, whilst all my contacts, SMS, photos etc are backed up to the cloud, the same can't be said for my app data. Before I lose hours and hours of progress in various games, or all my settings in numerous other apps, etc, can anyone think of any way to get access to the memory of the phone, bearing in mind the following:
I can't connect to Kies to pull a back-up because bluetooth is currently enabled on the phone and when one connects the USB cable, it says "Activating USB mode will deactivate Bluetooth. Continue?" but I can't click the Yes button
I can't connect in USB mass storage mode because I can't navigate to the settings menu entry to enable it
I can't turn Bluetooth off in order to get Kies working, becuase I can't get to the settings menu or pull down the notification bar to reach the power control.
I can't use Voice input to control the device (on the off chance there was a "bluetooth off" voice command) because (presumably with the most recent firmware I flashed via Kies a few weeks back) for some reason Vlingo is no longer the app on the double-home button action. Instead it calls Samsung Voice and wants to walk me through a first use tutorial, but I can't click the next/skip buttons
I installed via Android Market push the app belonging to www_remoteaccessphone_com as it promises to be able to remotely switch bluetooth off, but the website says I haven't installed the app yet, presumably because alrhough I was able to install it without touching the phone, it probably needs to be run at least once to set it up, and I obviously can't do that
I can't start Kies Air to try and get my data that way (starting it would require using the touch screen)
Kies via bluetooth isn't supported on Android
Needless to say, the data I'm trying to retrieve is on the internal memory, not the SD card. As you can see I've been trying all sorts of creative things, but I'm fairly sure I'm screwed. Any bright ideas I haven't thought of?
Click to expand...
Click to collapse
flash it with CF-root, boot into CWM recovery, do a nandroid backup after that, use CWM recovery again to mount USB storage, connect to your PC and pull everything off.
Nitrile said:
flash it with CF-root, boot into CWM recovery, do a nandroid backup after that, use CWM recovery again to mount USB storage, connect to your PC and pull everything off.
Click to expand...
Click to collapse
Thanks for the quick advice. I guess I'll need to use my girlfriend's phone to download CF-root and then transfer the SD card to my device. Quick question before I proceed though - is it possible to remove all traces of such tampering, since I've already made out with Samsung that I'm sending it in for repair, and I'm not sure they will honour the warranty if they see it has been rooted etc.
blaubeer said:
Thanks for the quick advice. I guess I'll need to use my girlfriend's phone to download CF-root and then transfer the SD card to my device. Quick question before I proceed though - is it possible to remove all traces of such tampering, since I've already made out with Samsung that I'm sending it in for repair, and I'm not sure they will honour the warranty if they see it has been rooted etc.
Click to expand...
Click to collapse
get a USB jig off ebay or amazon to reset the flash counter. should not cost more than 5 or 6 euros, shipped.
anyways you need to flash CF-root through ODIN if you are coming from stock. instructions are all in chainfire's cf-root thread.
Nandroid Restore
So I successfully rooted, used CWM to do a Nandroid backup, mounted the sd_card and saved the contents (including the nandroid backup) to my PC, reflashed the stock rom & kernel, usb-jigged it to get the counter back to zero/original and sent the phone in for repair. My efforts paid off as they repaired it without question under warranty. I just received the phone back and today set about restoring my backup:
Copied the sd_card contents I'd saved to my HDD back onto the phone
Re-roooted it with Cf-mod.
Used CWM to restore the backup I took before sending it in
It restored boot/system/data/cache successfully
selected reboot now in CWM
The result is that it is still missing all my apps. It only seems to have the "data" like my camera shots and SMS messages, system settings like whether bluetooth is on or off, the volume level, Wifi networks etc. So something was restored. But there is no Google Account configured, the lock screen picture is the default not the one I had beforehand, and as I said, all the apps - the main reason I did this whole thing as my personal data is all backed up to the cloud on a regular basis anyway - have not been restored. Am I confused? I thought a nandroid backup took a complete snapshot of everything, apps included.
Finding out the list of Apps I had in order to reinstall them is not an issue - I have a list of everything I had installed saved on AppBrain. But if I reinstall the apps, all the settings (or progress in the games) within those freshly installed apps will be back to square one, not where I left them, right? Or should I reinstall the apps and then restore the data partition over the top again?
Are you guys using any type of screen protectors, cause if you are, that may be the issue s their have been reports that the screen becomes unresponsive with certain screen protectors when connected to a charger.
However, if you are not using a screen protector, then I would suggest getting the unit replaced as you should not have to do anything, root or otherwise, to get the touchscreen working on a touchscreen phone
achillies400 said:
Are you guys using any type of screen protectors, cause if you are, that may be the issue s their have been reports that the screen becomes unresponsive with certain screen protectors when connected to a charger.
However, if you are not using a screen protector, then I would suggest getting the unit replaced as you should not have to do anything, root or otherwise, to get the touchscreen working on a touchscreen phone
Click to expand...
Click to collapse
Nope, no screen protector or any kind of case for that matter. Anyway, that isn't my issue anymore. The touch-sensitive unit was defective, the phone was repaired under warranty. My issue now is getting my apps & settings back. I have meanwhile read elsewhere that Nandroid doesn't back up the apps - pretty deceptive "backs up everything!" "it is like time travel" etc comments around here then.
Anyway, I reinstalled all the apps I had previously, and thought by reapplying the data partition from the nandroid backup it might then bring back the settings for the reinstalled apps. Instead all it did was remove all those apps again - now I am really confused. How come the restore DOESN'T bring back the apps I used to have, but DOES remove the ones I subsequently install. Does Nandroid touch the apps or doesn't it?
Touch screen not working
So i am having a very peculiar problem related to the GT-I9100 Touch Screen.
I bought the phone from Saudi Arabia and I live in Bangladesh at the moment. So for now I don't have warranty.
I bought it on 4th of this month. It had 2.3.3. So I updated it to 2.3.5. I did not use the phone much before that so I don't know if this problem was there before.
So here is the problem.
First time I noticed it when i pulled the phone from my pocket and could not unlock the pattern. First I thought I forgot the pattern. After sometime I noticed that i could not touch the buttons. I was dragging my finger over the points but there was no connecting line. I restarted the set. But it still did not work. After sometime I took the battery out. And after that it started normally and unlocked. And the touchscreen is totally fine.
I tested it using *#0*#. And every single point in the screen registers touch.
After that this happened couple of times. First couple of days I thought it was a pattern unlock problem. But i tried PIN and Password even using no unlock. It happened in every case.
So after couple of days it totally stopped happening.
But from yesterday it is happening again. And today it happened 3 times.
So today as I had no unlock protocol i tried tapping Home twice. As this brings on the voice command menu. And for the first time i was in the phone without touching the screen.And first i noticed the Menu and Back Soft keys works.And the touchscreen still does not work. And i noticed some thing weird. Always some thing in the screen is Selected. In Menu the + Icon is selected. In first screen the Map icon is selected. Also in Recent Apps the first App is selected. So after a lot of reboots it is back to normal again. Now i see something interesting. In the Battery Usage Graph i can see some really sharp drops. 3 times. Looks like when this happens phones charge takes a nose dive.
So here is the Gist.
Info related the Problem:
1. Usually happens when the phone is my pant pocket for sometime. It does not happen if it is sitting on the table.
2. Touchscreen gets totally disabled.
3. I have no idea why this happens.The exact reason behind it.
4. Battery Charge takes a nose dive when this happens. See the attached images.
5. I still don't know how to bring it back. Sometimes a simple reboot works. Sometimes I have to pull the battery. And sometimes it works on its own.
6. Every other function of the phone works. Like music playback using my UE 200vi music keys using PowerAMP, Siri(Android version), Call can be received using headset.
Battery nose Dive:
dl.dropbox.com/u/30943431/SC20111115-203017.png
dl.dropbox.com/u/30943431/SC20111116-202913.png
Also the selection
dl.dropbox.com/u/30943431/SC20111116-202146.png
So this is the thing. My biggest problem right now is, I don't know why it happens and I don't know how to bring it back from this situation. If I knew I could make sure I don't get it again or I would just fix it every-time. As when this happens I cant make calls or anything which requires the touchscreen.
So guys help me if you can by giving ideas. As i will not go back to KSA in 6 months. So buying a $550 phone unlocked was a total waste. As i cant use it here.
Thanks a million in advance.
---------- Post added at 09:29 PM ---------- Previous post was at 09:13 PM ----------
Sorry for this. But looks like i cant post outside links before i have 8 posts. So i removed the "ht tp : //" part of the links. Copy paste in browser address bar and it will open fine.
And also the next time it happens i will do a video to shou you guys.
Having the same problem while charging touch screen doesn't work
Stock charger and usb cable
i was on CM7 but that happend so i flashed stock but no luck
I will write more observations
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.
Hi
I've recently got one of the EU 1/8 Omate Truesmart watches. To start with it was fine, but after realizing I had missed some calls yesterday I realized that the watch made no sounds and the mic wasn't working either when I made some test phone calls. The vibrate does still work. I've changed the Modes in the Audio Profile but that doesn't seem to have made a difference.
Has anyone else had these problems?
I suspect the mic and speaker are in different parts of the watch, so I'm guessing its a software issue rather than something has shaken loose. I tried to work out how to reset the watch, but so far I haven't worked out how to do that (I haven't patched it yet, so it still has the original version of the firmware etc).
Thanks for any assistance
Somehow I managed to get the sound and mic working again . The last thing I was trying was to turn the watch off and on repeatedly, pressing or holding the two buttons down while it booted. One of the other posts suggested that I could get to a menu to reset the watch this way. Whilst I never saw a menu, on one occasion it did take longer to boot than normal (a few extra seconds) so I may have selected an option with out realising.
I've been reading here for months waiting for my TS to arrive and today it has!
I quickly found that all sound and mic was not working and my heart sank. But reading this question and the poster's own reply, and a hint from elsewhere, I turned off "fast boot" in the accessibility menu, shut down and restarted, and hey presto, sound input and output works fine. The "fast boot off" setting seems to be required in order to make the device really reboot.
Many, many thanks to all here who have been contributing to the knowledge base on this device. Hopefully I can now contribute, if only from the point of view of a non-expert man-in-the-street end user, from time to time.