So I recently (past month) decided to test out the GB ROMs for the Desire. Everything went perfectly smooth except for the crazy lock screen.
For some reason, if I call someone and they hang up my phone will go to the lock screen. As long as the proximity sensor is activated and i'm not the one ending the phone call it automatically locks the screen.
This happens if the other party hangs up, network error, busy, etc... and its driving me nuts.
So far i've tried CM7 RC1/RC2, Oxygen, Gingervillain, Devnull (stockish GB) and every one of them gives me the same thing.
I've changed ever setting possible but I keep receiving the same problem.
Now I'm not sure if this is related or not, but if when I connect my Desire to the computer it will give me the phone off/on click maybe 5-6 times in succession and then everything is normal. Same problem with all ROMs.
Could someone please verify that I'm not the only one with this problem? And if anybody has a solution I would really appreciate it.
Thanks.
Forgot to mention that the Sense ROMs dont have this problem.
I get the auto screen lock, not sure about the phone off/on click tho :/
Ive tried the same roms too..
Do you have a Sense GB ROM for Desire?
Anyways, try "Return to dialer after call" in contacts preference.
markdomingo said:
Do you have a Sense GB ROM for Desire?
Anyways, try "Return to dialer after call" in contacts preference.
Click to expand...
Click to collapse
Nope normal GB ROM. And that doesnt work either :/
Well my friend got a brand new Nexus S with Gingerbread and I tried this thing out on it.
Turns out its something built into Gingerbread and it doesn't look like you can change it
Related
every other time my phone rings I cant answer it. The accept button just wont move?? is it just me or have anyone else had this error I have a dezire z
Do you have set CPU set to 245MHz @ screen off?
no i dont, why?
Well that could be one cause, maybe it's a bad app causing your phone to temporarily freeze? Can you slide it the other way and ignore the call?
Did you try flashing a different kernel?
Sent from my CyanogenMod powered G2.
Utorrent76 said:
Did you try flashing a different kernel?
Sent from my CyanogenMod powered G2.
Click to expand...
Click to collapse
why do you suggest this? how do you know hes using kernels? im just trying to see what your connection to the solution is -its quite a specific answer to a problem that hasnt really been examined. what rom is he on, etc before you can start talking about kernels -- so can you clarify?
accept button - do you mean the slider? if you have cmod - just activate settings to disable lock menu/trackball/ whatever --also you could try the no-lock unless you have security issues.
if no cmod -- theres apps to reduce the lockage -- that may help you get your phone calls but still doesnt fix the problem? you could try enomther's and his awesome extra ssettings app has all those options
Thanks for your help, well it is my wifes phone and it is fresh from the store, just a bunch of apps installed.
I will try some things and see if i can figure it out. And yes it is the slide button, can that be switched for a push button, Is it theme based or in the dialer?? hope you understand what i say.
jaypeg123 said:
Thanks for your help, well it is my wifes phone and it is fresh from the store, just a bunch of apps installed.
I will try some things and see if i can figure it out. And yes it is the slide button, can that be switched for a push button, Is it theme based or in the dialer?? hope you understand what i say.
Click to expand...
Click to collapse
If its a stock DESIRE Z and not a G2 then I think it's safe to assume its got sense on it and not AOSP. Did you try hard resetting it? (power down and pulling the battery for at least 30 sec) other than that id check for any OTA updates in the settings menu. OR if you're willing/know how, you can root it and run CM or virtuous. Both ROMs are excellent. If you do that and the problem persists, it could very well be a faulty unit. You have a lot of options!
I found I had problems answering calls when I had a specific make of screen protector on the phone. As soon as I took that off and went back to a previous one I'd used then it was fine again ! It's a long shot, but I thought I'd throw it in there.
Problem solved, An update did the trick, thanks for helping out my friends,
same problem , cannot answer with swipe keys
I have the same problem, which update did you use
same problem , cannot answer with swipe keys
I have the same problem, which update did you use
I am having a problem where all vibration/haptic feedback will just randomly stop working completely. Then a few hours (and sometimes days) later it will randomly start working again. It will keep working again for a few hours or maybe days, and then randomly stop again. There seems to be no pattern to it.
I have no idea what is causing this. Has anyone else experienced this, or does anyone have any idea how to fix it?
This is extremely frustrating as I am someone who never uses the ringer; I just always have my phone on vibrate.
I'm running the latest stable release of CM 7.1 for the Evo 4G, but I had this happen before on stock Sense as well.
mredmond2012 said:
I am having a problem where all vibration/haptic feedback will just randomly stop working completely. Then a few hours (and sometimes days) later it will randomly start working again. It will keep working again for a few hours or maybe days, and then randomly stop again. There seems to be no pattern to it.
I have no idea what is causing this. Has anyone else experienced this, or does anyone have any idea how to fix it?
This is extremely frustrating as I am someone who never uses the ringer; I just always have my phone on vibrate.
I'm running the latest stable release of CM 7.1 for the Evo 4G, but I had this happen before on stock Sense as well.
Click to expand...
Click to collapse
I am having this same issue as well. It must be software related because the vibrate function works just fine when the phone rings. I am running CM 7.1 stable on an Evo 4G. I noticed the issue as well on CM 7.0.3.1 or whatever the latest stable build was on CM.
Does the phone ever always (or never) vibrate under a certain circumstance? i.e. incoming text, email, incoming/outgoing call, typing, etc.? Also, do you have any toggle widgets that could affect vibrate/ringer status?
I ask this because, and this may sound silly, it may be that you are modifying settings unknowingly. I've had that happen where I have my hands in my pockets and next thing I know I've accidentally got my Facebook up and running and typed half a book in the status field.
Again, I know that sounds silly but I ask because it's happened to me before.
Concordium said:
Does the phone ever always (or never) vibrate under a certain circumstance? i.e. incoming text, email, incoming/outgoing call, typing, etc.? Also, do you have any toggle widgets that could affect vibrate/ringer status?
I ask this because, and this may sound silly, it may be that you are modifying settings unknowingly.
Click to expand...
Click to collapse
That's fine, its an important clarification to make. But no, I am absolutely sure I have not changed any of the options unknowingly. As I said in the OP, ALL vibration/haptic feedback will cease to function entirely. I've often had it happen that in the middle of typing something, the haptic feedback for the keyboard will just go away. Immediately after this if I check the soft key buttons or test the vibration for notifications, none of these will produce any sort of vibration response either. Then randomly a few minutes, hours, or days later, all haptic feedback will just return. Its been an extremely strange and frustrating issue.
4nth0ny said:
It must be software related because the vibrate function works just fine when the phone rings. I am running CM 7.1 stable on an Evo 4G. I noticed the issue as well on CM 7.0.3.1 or whatever the latest stable build was on CM.
Click to expand...
Click to collapse
For me, when the vibration stops working, it stops working for everything, even when the phone rings. But that's what I can't figure out: if it is a software or hardware related issue. I was having this problem on stock Sense, and I figured if it was software related, perhaps flashing a new ROM (in my case, CM7), would fix it. However it hasn't, so I'm beginning to think if it is indeed a software issue, it must be a bug somewhere very deep within the code, otherwise it has to be a hardware issue. But if its a hardware issue, I can't figure out why it would randomly stop/start working like it does, and the thing is, most (75%) of the time, it is working. Its just the other 25% that annoys the hell out of me. That's why I thought I'd ask and see if anyone else had experienced it or found any solutions.
Its a CM7 thing I've noticed it on Xplod, Decks, and CM7 I don't really mind it cuz my ringers are loud as hell but yeah its pretty weird :shrugs:
Usually AOSP ROMs for some reason have that problem cuz on sense ROMs it never happens
infamousteeboy said:
Its a CM7 thing...Usually AOSP ROMs for some reason have that problem cuz on sense ROMs it never happens
Click to expand...
Click to collapse
Well like I said before, I was having this problem on my stock Sense ROM.....
infamousteeboy said:
Its a CM7 thing I've noticed it on Xplod, Decks, and CM7 I don't really mind it cuz my ringers are loud as hell but yeah its pretty weird :shrugs:
Usually AOSP ROMs for some reason have that problem cuz on sense ROMs it never happens
Click to expand...
Click to collapse
I've never had that problem on CM and I've been using many different versions of it for a long time. I don't know if I am lucky or what but people complain about a lot of issues that are claimed to be CM issues....yet I've never had a single one of them.
Concordium said:
I've never had that problem on CM and I've been using many different versions of it for a long time. I don't know if I am lucky or what but people complain about a lot of issues that are claimed to be CM issues....yet I've never had a single one of them.
Click to expand...
Click to collapse
Well I kinda had the same problem that he's run into on CM but I figured it out but I figured since he's had the problem on a sense ROM also then maybe its not the ROM but I jus went into everything that had the option to vibrate and turned them all on cuz I've flashed a couple ROMs and the vibration would be off I try not complain about anything about any ROM its a person hard work they've done for free I try to figure things out on my own as much as possible before I create a thread not bad talkin the OP but jus sayin you know?
I don't think that it's rom related. I've been having issues with my haptic feedback since I got the phone, even before rooting it. I think it's just a crappy vibrator. (If there's a better name than "vibrator", please someone tell me.)
I had vibration problems on my first Evo as well, it was never rooted. My second Evo was a HW004 and the haptic feedback was perfect - it was softer instead of the shock-like haptic feedback I've experienced with my 003s. My current and third Evo is also a 003, so I assumed it had something to do with the motor used in 003s.
I've just turned haptic feedback off. I thought I'd miss it, but I've gotten used to it. I still use have my phone set to vibrate for notifications and calls and I've seen fewer issues.
If you think you can go without, I'd suggest turning haptic feedback off. Otherwise, unroot and take it into Sprint. You may have more luck calling, because if you can't replicate the issue in front of them then they can't do much.
Sent from my Evo + MIUI using Tapatalk!
plainjane said:
I don't think that it's rom related. I've been having issues with my haptic feedback since I got the phone, even before rooting it...
...Otherwise, unroot and take it into Sprint. You may have more luck calling, because if you can't replicate the issue in front of them then they can't do much.
Click to expand...
Click to collapse
Yeah, its definitely not ROM related...I don't know if people aren't reading the posts, but I've said several times that this occasionally happened on stock Sense, both before and after rooting.
Dang. I didn't want to have to bring it in to get it fixed, but I guess that's what I'm gonna have to do if its a hardware problem...I was really hoping it was software related or if someone would know of a way to fix it so that I could avoid dealing with warranty services...I got suckered into the Best Buy warranty, and it turns out that even though they either give you a new or refurbished model, they make you turn yours in and wait 5-7 days for the replacement to come in instead of ordering the replacement and then doing a trade with you when it comes in. I already experienced it once before when my USB port broke... :/
Not being able to replicate the issue is my main concern since sometimes it works and sometimes it doesn't. Trying to get it to stop working at a time when I can actually run out to the store is gonna be a pain...And I really don't want to waste a trip to the Best Buy store only to have it start working again with me trying to tell the GeekSquad Agent, "I promise, I promise! It was broken just 5 minutes ago!!" I can't imagine how many of those they have to deal with....
All of a sudden regions of my screen are not responding to touch and it seems like the calibration is off. For instance, when typing, the backspace is always typing the letter 'L' above and I'm unable to pull the notification bar down (it thinks I'm touching below it).
Is my phone toast, or is there a way to recalibrate the screen?
Did you try the touch calibration under language and keyboard? Are you stock, rooted sense, or AOSP?
Sent from my Droid.
I'm rooted, on Aerovan's CM7.2. About 5 minutes ago the notification bar was working fine, but then I locked the phone and it stopped working again. When I touch the notification bar, it thinks I'm touching below it.
I've tried formatting and loading default CM7.2 to no avail. Dipped phone in dry rice all last night to no avail.
Not sure what to try at this point. I can't find any calibration tools in the Settings, including the one in the keyboard/input area.
also happening for me
brymaster5000 said:
Did you try the touch calibration under language and keyboard? Are you stock, rooted sense, or AOSP?
Sent from my Droid.
Click to expand...
Click to collapse
Tkanks for the post I was having the same issue and saw ur post to calibrate the screen and that works so thanks
jheathco said:
I'm rooted, on Aerovan's CM7.2. About 5 minutes ago the notification bar was working fine, but then I locked the phone and it stopped working again. When I touch the notification bar, it thinks I'm touching below it.
I've tried formatting and loading default CM7.2 to no avail. Dipped phone in dry rice all last night to no avail.
Not sure what to try at this point. I can't find any calibration tools in the Settings, including the one in the keyboard/input area.
Click to expand...
Click to collapse
I haven't run CM7.2 for a while, so I can't remember if there is a keyboard calibration like in Sense (I'm on SkyRaider Zeus). Hopefully someone running it can chime in.
Unfortunately I can't even find Skyraider to download. But this screen issue is bugging me BIG TIME. I have a dialer in the launcher bar at the bottom left that responds when I touch it. If I'm in an app however and touch that area, it doesn't respond.
WTF is going on?!
I've tried reformatting on clean CM7.2 and CM9. Stock is my last hope...
brymaster5000 said:
I haven't run CM7.2 for a while, so I can't remember if there is a keyboard calibration like in Sense (I'm on SkyRaider Zeus). Hopefully someone running it can chime in.
Click to expand...
Click to collapse
I got skyraider 1.3 from their website but pull down goggles and set up just force closes. I am not the only one. Think they uploaded a bad zip I would love to try again if it worked. I downloaded twice and seen a post today I am not the only one with this issue.
Dude I have so many issues like that, even on pure stock. Idk...but on cm9 I had some serious issues
Sent from my HTC Incredible 2 using XDA
I have tried searching for this problem but I must be using the wrong terms... so sorry in advance if I missed a post that addressed this issue.
My sprint S3 does this twitchy/glitching thing on every touchwhiz based jellybean rom (does not do it on TW ICS ROMS) I have tried. It basically makes it nearly impossible to do sliding animations, IE it can actually get stuck and start flashing halfway between screens, or when pulling down the top menu, however you can open new programs just fine if you are already on the right screen for them. Luckily it does not do this all the time, but when it happens it keeps doing for 10 minutes or so and its annoying as hell.
I figured this must be a rare issue even though it effects both my wifes phone and mine, since I have never read anything about it, however I just got a new replacement phone and it does the exact same thing, even on dead stock TW JB ROM.
Oddly enough I discovered last night that if I turn on my screen filter app it stops completely, but it starts right back up when I turn off screen filter..... any ideas how to fix this?
Try grabbing cache clear from the play store and set it to run every 12 hours. It helped my phone a good bit.
Sent from my SPH-L710 using xda premium
No one else ever has this issue?
joelespinoza said:
No one else ever has this issue?
Click to expand...
Click to collapse
I had it dude, but it was just on the CleanBean ROM, it was annoying as hell!
So I changed the ROM, Its weird that its happening on a Stock ROM, any suspicious app?
Hello.
I have 2 years old Desire HD. I installed several custom roms over last years but lately I have major problem. My phone application is crashing. Situation is the same every time - I try to call somebody, i chose a name and hit a call button. Everything seems to be ok but i don't get any signal at all. After 1 minute application is closing in the same way it would after hitting "end call" button, or if i would not get connection. Basicly I cant call anybody, everything else is working grate. Also when that happens i tried to call my phone from other number, on my other phone I did get a signal and everything but my DHD was behaving like nobody was calling me. My girlfriend also told me that she was calling me on some ocassions, I wasnt picking up but ofcourse i did not get any info on missed calls or anything.
After reset all is working as normal, untill next problem.
I have tryed PAC-man AIO by CedArctic, JellyTime and Virtuous Quattro - the same problem.
What could be the reason for that? Any sollutions?
Larithiel said:
Hello.
I have 2 years old Desire HD. I installed several custom roms over last years but lately I have major problem. My phone application is crashing. Situation is the same every time - I try to call somebody, i chose a name and hit a call button. Everything seems to be ok but i don't get any signal at all. After 1 minute application is closing in the same way it would after hitting "end call" button, or if i would not get connection. Basicly I cant call anybody, everything else is working grate. Also when that happens i tried to call my phone from other number, on my other phone I did get a signal and everything but my DHD was behaving like nobody was calling me. My girlfriend also told me that she was calling me on some ocassions, I wasnt picking up but ofcourse i did not get any info on missed calls or anything.
After reset all is working as normal, untill next problem.
I have tryed PAC-man AIO by CedArctic, JellyTime and Virtuous Quattro - the same problem.
What could be the reason for that? Any sollutions?
Click to expand...
Click to collapse
Might be a Problem with your radio. try flashing different radios.. also the roms that you are using are still in beta stages. Its better to use Stable roms. i use jellytime r10. its near stable
Been there done that i used several diferent radios and jellytime r9, r10. Same problem. Im starting to think it's hardware...
Sent from my Desire HD using xda app-developers app