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
Related
I am experiencing random lock ups and freezes. It happens especially when I receive texts and incoming calls after about 30 minutes of no use. WiFi does not work either. It is very annoying and frustrating as I lose the text or miss the call. I have to reset the phone to get it working again. Sometimes it takes several resets.
EDIT: Other random tidbit...after playing with the phone a bit more, I have found that the phone functions perfectly when plugged into the power outlet-WiFi, texting, incoming calls...Maybe it has something to do with the power settings when not plugged in?
Is anyone else experiencing this?
Does anyone have a guess at what might be the problem?
I am running:
SPL 2.47
2.42.50 radio
DCD Custom 3.2.6
I have never had this problem until about a week ago. I am wondering if it is a hardware issue as I have tried re-flashing several times. It will work well for a few hours then act up again. I am thinking about relocking my phone and taking it in for service, but that is a last resort.
Thanks in advance for any help.
same thing happened to me. It started ever since i switch out for a new battery though. I seriously think it's my battery that causes these random freezes.
hmmm...it does seem to be a battery issue as it works while plugged in. Is there any way to reset the battery somehow?
Freezes here too
I've had my phone freeze twice in the last two days. Yesterday at work, connected via activesync, when I disconnected the screen wouldn't come on. Then today I was connected to the wall charger, disconnected and the screen wouldn't come on again. Had to remove the battery both times to get the phone working again.
My experiences
When the 6800 came out I liked it so much that I hooked my entire family up with one and I have seen more problems than a lot of people. I just thought I would share some of the freezing problems I've seen and what I've dont to replace them. And if the device is not freezing when it is plugged into the wall is the screen off like in idle, or is it real dim and still up? And one great thing you can do to reduce daytime freezes is to leave the device off at night when you charge it (if you can stand to do that), or at least soft reset when you grab it to start the day.
1) The most common reason for lock ups that I've seen is memory drain. It is caused from programs you've installed that continually run in the background. The biggest killer is recieving calls when the phone has been sitting at idle too long or trying to run activesync or an internet browser.
Fix: You can try to go back and remove the programs that you've recently installed till you lack this problem, but the ultimate fix is to hard reset.
2) Some registry edits have poor efects on the way the phone performs and this is when it seems everything is good, you are keeping the memory clear with a task manager, yet it still freezes in the middle of doing something.
Fix: Every titan seems to act a little differently than others. The only time I hack the registry is when one of my family members phone is having an issue, or when I get bored and I want to mess around with my own's performance. The remedy for this is installing the stock carrier rom and then moving to a rom of your choice. Read the posts too. Make sure the radio is compatible with the rom. Trust me in this forum you can find anything.
3) Memory boosting software like memaid or oxios close apps are great, however, with some programs they interfeer with each other and cause problems.
Fix: Forget this memory programs. Find a rom with good memory management.
Animez: That is how mine started...now it does it at least 6 times a day.
Sweeny: Thank you for your detailed response. I do not think it is memory drain as I use x-button and maintain my task manager quite frequently. I have not made any registry edits except for the DCD kitchen (3.2.6), arcsoft, and carrier cab I have installed...
Question: Does the registry get wiped on a reflash or do I need to hard reset to wipe the registry? I don't really trust myself all that much fiddling with the registry unless I know what all the strings do.
bdlane said:
Animez: That is how mine started...now it does it at least 6 times a day.
Sweeny: Thank you for your detailed response. I do not think it is memory drain as I use x-button and maintain my task manager quite frequently. I have not made any registry edits except for the DCD kitchen (3.2.6), arcsoft, and carrier cab I have installed...
Question: Does the registry get wiped on a reflash or do I need to hard reset to wipe the registry? I don't really trust myself all that much fiddling with the registry unless I know what all the strings do.
Click to expand...
Click to collapse
A hard reset or rom flash will wipe your registry since it's included in the new rom and also stored in the hard reset rom. So if you screw it up, worse case you hard reset, or reflash with a new rom/same rom, doesn't matter.
You can also back up your phone prior to making any changes, and if you screw up, hard reset and then restore the backup.
BTC
Sorry if this is the wrong place for this - or if this is discussed else where. The search terms for this are so generic, I was finding lots of unrelated topics.
I'm using stock Rom w/WM6.1. When in the Windows contact list (TouchFlo is off) and I start entering characters to find a name, when I get to the fourth or fifth character, all of a sudden the screen switches to the dialer mode, and a call is initiated to the person who was listed first in the search list. The problem is by no means consistent. I may go days without it happening, but when it does start doing it, I'll be repeatable until I set the phone down for a few minutes. After that, it works as it should again.
This same thing happens on my wife's Diamond, and my dad's Sprint Touch Pro as well. It's extremely frustrating.
Has anyone seen this problem? Know what's causing it? How can we fix it?
Thanks!
Over the past week or so I have noticed the backlight on my Atrix acting strange during calls. Sometimes it will not shut off when placed next to my head(I can see the screen out of the corner of my eye) or it will not light up when taken away from my head(to key in a selection on a menu). Sometimes it also shuts the backlight off as soon as the call is placed and I have to press the power button to "wake it up" so that I can make a selection.
The only other thing that I noticed just a little bit ago is - while in a call the LED next to the earpiece appears to be glowing red(dim - like the Terminator's eye right before it got crushed ).
I haven't added any apps in the last two weeks and there haven't been any major updates to speak of.
The phone is basically stock. I did root it so I could use titanium backup and barnacle.
Build: OLYFRU4 1.8.3
Kernel: 2.6.32.9-00007
baseband: n_01.77.15p
android version: 2.2.2
sys ver: 4.1.83.nb860.att.en.us
Has anyone else had a similar problem? More importantly, has anyone else resolved a similar problem?
Thank you in advance for any assistance provided.
Interesting.. I have similar problems, and I've heard this is a known problem with the Gingerbread update (which you haven't done it seems). I've personally noticed that this happens after I use bluetooth and making calls and stuff with BT devices. Do you do anything like that?
I do use a bluetooth headset but haven't noticed any problems when using it.
Shortly after making this thread I checked for any OTA updates and there was the gingerbread update available. I went ahead and performed the update and the problem still exists.
I also believe that my terminology was different and that is why I didn't have success when searching. I have found several threads describing the problem as dealing with the proximity sensor instead of the light sensor. I have not found a definite solution though yet - I'm contemplating a factory reset.
So I went ahead and did the big wipe and still have the same issue. I've read over the other "proximity issue" threads which all involve editing the value in build.prop.
The problem with this is, mine seems to have problems both ways. I've had it blank the screen right after pressing "dial" and then I've also had it not blank the screen at all(allowing it to cheek dial). The other weird thing I mentioned in my first post, is the sensor LED( to the right of the ear slot) is glowing red when there is an active call. I don't recall seeing it do that before.
I'm really tempted to have an insurance claim really soon.
71chevellejohn said:
So I went ahead and did the big wipe and still have the same issue. I've read over the other "proximity issue" threads which all involve editing the value in build.prop.
The problem with this is, mine seems to have problems both ways. I've had it blank the screen right after pressing "dial" and then I've also had it not blank the screen at all(allowing it to cheek dial). The other weird thing I mentioned in my first post, is the sensor LED( to the right of the ear slot) is glowing red when there is an active call. I don't recall seeing it do that before.
I'm really tempted to have an insurance claim really soon.
Click to expand...
Click to collapse
Unfortunately, it sounds like your proximity sensor (or logic board in general) may be going haywire - meaning a hardware problem not a software problem (I'm guessing that since, as you said, it's happening both ways)...
In my sig there is a app called Build.prop editor. You can use this to change the proximity timing and distance. the little red light you see is the infrared sensor that tells the screen to shut off.
In the build.prop edit mot.proximity.delay=200
and edit mot.proximity.distance=30
should fix screen not turning off issue.
Once again link in my sig for build.prop app( must be rooted)
You can try other values that fit you, doesnt have to be 200 and 30
Ok so I want to convey all the relevant information without this being a mile long.
I have a o2 UK SGS2 running on a 3 sim. I have flashed on Lite'ing 6.1 with ninphetmaine 2.0.5. Up until the following, everything has been 100%.
This morning I downloaded Destinia and played it for a while. Before quitting I took a quick look at in app purchases to see if they charge ridiculous prices (they do). I'm not interested so I quickly spam back to close everything. This is when **** ****s up. OS becomes unresponsive immediately and I have no choice but to pull the battery. (power menu disappears instantly, no registered actions from soft keys or menu button in OS). No change on reboot.
I try reflashing Lite'ning. Mostly no change but I got the chance to get into task manager and uninstall Destinia/Launcher Pro.
I reinstall launcher pro, and now it works most of the time except:
1. Quite frequently the voice action app will load itself, and the unlock notification will pop up.
2. MTP notification will appear occasionally and phone will act like it's plugged in
3. Random Launcher/OS crashes. Sometimes screen on but no response from apps or OS. Sometimes screen won't turn on at all, just softkeys and darkness.
4. at first unlock after boot, camera makes standard focusing sound.
5. on boot, little popup dialog will read "in app purchases not supported in this version of android".
Really I doubt there's going to be any solution other than "wipe and reflash" but I'm really interested if anyone knows what would cause all these problems.
Cheers
. I'm not interested so I quickly spam back to close everything
Whatever that means looks to be the source of your problem..
jje
JJEgan said:
. I'm not interested so I quickly spam back to close everything
Whatever that means looks to be the source of your problem..
jje
Click to expand...
Click to collapse
what this means is that pressed back from the game's in app purchases screen, back to the main menu and then back to the Launcher, I'm sure everyone has done basically this countless times.
Fine but my dictionary defines spam as a different meaning .
But as posted that's where it all went wrong for whatever reason .
jje
Right I wipe-flashed stock 2.3.5 and it's STILL doing this. Voice actions popping up at random, all sorts of apps crashing and hanging all the time.
This has to be a hardware problem now, right?
just a stab in the dark but run a virus check.
I've never had a virus in my life, but I checked anyway and nothing.
Right so I've been watching my phone today. It's still doing random voice action popups. If I leave the phone on standard standby it will be fine for a while. It will then randomly turn on the screen by itself. The screen will stay on, if i leave it long enough the whole thing become totally unresponsive. If I press power the phone will wait a few seconds, then restart. If I don't touch it, it will just restart on its own eventually.
Can anyone recommend at least, some logging software that will let me look at the underlying OS and see what's happening when this is going on.
Is there any possibility your phone also goes to car-mode by itself?
spare parts app??
Your phone is more or less doing the same thing as mine is. It's a hardware issue from the seems of it. The voice command thing is from a dirty pin in the USB connector part which apparently isn't that hard to clean, for users in the thread below it actually helped to solve the issue. But my persisting issue is the unresponsive screen and power button causing an active screen to dim out and making the screen unresponsive..
http://forum.xda-developers.com/showthread.php?t=1174291
Im getting random voice talk and mtp etc. phone is all ovr the place. flashed litening and nimphet last week and seemed fine. used mhl hdmi cable and problems seemed to start from there.
millia90 said:
Your phone is more or less doing the same thing as mine is. It's a hardware issue from the seems of it. The voice command thing is from a dirty pin in the USB connector part which apparently isn't that hard to clean, for users in the thread below it actually helped to solve the issue. But my persisting issue is the unresponsive screen and power button causing an active screen to dim out and making the screen unresponsive..
http://forum.xda-developers.com/showthread.php?t=1174291
Click to expand...
Click to collapse
Read your thread http://forum.xda-developers.com/showthread.php?t=1278790 and your problems are down to the letter the same. I've resigned myself to it being a hardware fault and put in a service request with samsung. Wish I had better news.
Yea me too. My issue is that my SGSII was manufactured in UK so I'm at odds seeing as how I'm in America. The people at the Samsung call center referred me to the UK number so I guess I will have to bits the bullet.
A rather annoying issue has started to plague my Z2 and I was wondering if anyone else has come across it?
For the past two or so weeks it I've been having a number of missed calls (important one as well), this is despite the fact the phone as been three foot away from me. I've not heard it ring. Which is defeat the whole point of the thing.
I've now found out that occasionally it seems to want to stop making any sound. No notifications, ringtones etc. During one of it's tantrums I tried to play a MP3 via Doubletwist and it simply skipped through all of the album in record time without a single sound being played.
The only way to rectify this PIA issue is to reboot the phone.
I've also noticed that the vibrate is also occassionaly turned off, which is equally annoying.
Does anyone have any idea what could be causing this?
My phone is on 402 and rooted.
Thanks for any advice.
Do you have any apps installed like "sd card fix" or something like that? An app that should bring back the Feature to write on sd card with other then system app? For me these apps are making similiar problems. After deinstalled, everything working as it should be.
Thank you for your reply!
I've gone through and checked, and I don't have anything like that on my phone.
My old Galaxy S3 used to play up at times by refusing to receive calls and I found out it was down to my ringtone which seemed to be 'corrupt'. A reboot and it was back up and running.
This though is odd, as I don't have ANY sound. It's as if the sound part of the phone has given up the ghost!!!
I'm not even sure what makes it happen, which is REALLY annoying. At least then I could rectify it. It just happens.