Related
So I've noticed this issue for a little while. I haven't heard others mention this issue but occassionally haptic feedback or vibration will stop occurring like the vibration driver or motor dies temporarily. I've tried to get logs showing the issue but I see nothing about this in the logs, either the kmsg or logcat, most likely making it a hardware issue as it comes back later on its own. It's not a ROM/kernel issue as it has happened regardless of the kernel or ROM.
It may be worth a try doing an RUU to stock froyo and re-rooting but I thought I'd just check if others have had this issue or have a suggestion. I didn't see this issue when I checked the auto-thread search feature when entering the title. I can check google to see if it's reported there. It's not too big of a deal except of the chance that the phone may not vibrate on an incoming call in vibrate only mode.
I mainly wanted to just see if I'm alone on this.
tiny4579 said:
So I've noticed this issue for a little while. I haven't heard others mention this issue but occassionally haptic feedback or vibration will stop occurring like the vibration driver or motor dies temporarily. I've tried to get logs showing the issue but I see nothing about this in the logs, either the kmsg or logcat, most likely making it a hardware issue as it comes back later on its own. It's not a ROM/kernel issue as it has happened regardless of the kernel or ROM.
It may be worth a try doing an RUU to stock froyo and re-rooting but I thought I'd just check if others have had this issue or have a suggestion. I didn't see this issue when I checked the auto-thread search feature when entering the title. I can check google to see if it's reported there. It's not too big of a deal except of the chance that the phone may not vibrate on an incoming call in vibrate only mode.
I mainly wanted to just see if I'm alone on this.
Click to expand...
Click to collapse
I can't really say for myself. I always turn all haptic feedback and vibrations off on mine but I'll turn it back on for a bit and see if I get similar results.
Sent from my ADR6300 using XDA App
my wife has the att nitro hd, when the screen goes off during a call sometimes nothing including power button will turn it back on. Anyone know of a fix? did the ATT small update fix this?
Actually it comes back on after a long minute or two. Not very helpful if you need the dialpad or keys, etc.
I have just rooted it for her and installed CWM.
I have added a few proximity tweaks to build.prop
gsm.proximity.enable=false (rebooted twice but screen still goes off)
also used the ro.lg.proximity and the mot.lge.proximity (dont recall exact wording) both were set to a value of 5.
I'll have to take alook into the lg hidden dialer menu to see if I can disable this.
I dont like this sensor on my device either, but I have an option in settings to disable it, which makes it bearable.
thanks for the help guys.
I have noticied LG throws together some junky builds, typos, bad english/grammar. Wonky sensors etc. Incorrect kernel build ReadMe's
I thought I recall someone with another device just placing a peice of tape over the sensor. hmmm..worth a try.
cheers.
chrisrotolo said:
gsm.proximity.enable=false (rebooted twice but screen still goes off)
also used the ro.lg.proximity and the mot.lge.proximity (dont recall exact wording) both were set to a value of 5.
Click to expand...
Click to collapse
Congrats. Today, you learned that most of the "tweaks" found at XDA are utter bull****
aremcee said:
Congrats. Today, you learned that most of the "tweaks" found at XDA are utter bull****
Click to expand...
Click to collapse
What about the tweaks that aren't BS? Are they already included in your CM9 builds?
From what I can tell, pretty much the main thing that build.prop is good for is providing information about the system and software (i.e. info about the build). It's not really used much for useful configurations as far as I know.
networks tweaks actually have doubled me download speed.
I still have faith.
but can anyone answer my questions I posted in ICS SLim thread and PM'ed Andasa , no responses yet.
does ICS slim or CM9 have option to keep lcd no during call? and does it work??
what's working not working? I found changelogs but not a working/not working list for CM9.
and has anyone successfully restored a nandroid from ICS to GB without real issues?
thanks guys.
i doubt the ota fixed your issue as the issue is not one that occurs for every nitro.
I can tell you that when I make a phone call they screen stays no.
what's working not working, well, many of us are running it daily with no probs.
as you prolly know, it is a nightly build so a public list of what's working or not isn't rly part of the deal.
i've succesfully restore a nandroid from both slim and cm9 back to the stock att rom and others many many times. dozens.
thanks good enough.
I will have to give it a go.
would you recommend one or the other?
CM9 or slim?
thank you.
well, I like them both a lot. slim is just a trimmed down version of cm9 and i _think_ it does run just a bit snappier........maybe..but it's not wildly different from cm9. I usually switch back&forth throughout the day.
There's no setting in CM9 to disable the proximity sensor, although there may be a way to do it.
We just got a Nitro HD for my wife and her phone also has this issue. I have not gotten to know the phone well enough to try rooting or anything else of that nature, it's pure stock.
When she makes a call the screen turns off immediately after hitting the call button and will not wake up. When she receives a call we get a glimpse of the in-call screen with the various buttons etc but then the screen turns off. If the other party hangs up her screen turns back on, but if she calls something automated, like voicemail, she can't do anything except pull the battery to disconnect.
I've tried putting my thumb over the proximity sensor, hitting all buttons including power, and nothing makes the screen wake up or turns the phone off other than a battery pull.
The phone was running a build from last November when we first got it (V10i?) and today prompted us to update, so I did that hoping it would solve the problem. The phone is currently on V10j, but the problem persists.
Any help?
no driver said:
We just got a Nitro HD for my wife and her phone also has this issue. I have not gotten to know the phone well enough to try rooting or anything else of that nature, it's pure stock.
When she makes a call the screen turns off immediately after hitting the call button and will not wake up. When she receives a call we get a glimpse of the in-call screen with the various buttons etc but then the screen turns off. If the other party hangs up her screen turns back on, but if she calls something automated, like voicemail, she can't do anything except pull the battery to disconnect.
I've tried putting my thumb over the proximity sensor, hitting all buttons including power, and nothing makes the screen wake up or turns the phone off other than a battery pull.
The phone was running a build from last November when we first got it (V10i?) and today prompted us to update, so I did that hoping it would solve the problem. The phone is currently on V10j, but the problem persists.
Any help?
Click to expand...
Click to collapse
If you bought it from a store, get it exchanged for a new one.
actually works much faster on cm9, but therr still should be an optin to keep lcd on during call. i found some free apps that will disable hardware drivers but cant find the name of the proximity sensor driver, only that is named LGE.
Unfortunately it was given to us by a friend after my wife lost her Captivate, so taking it to a store to exchange is probably not going to work too well. As far as I can tell it was never used before we got it--the battery was still in it's own sealed pouch, the texting and driving warning was on the phone, and the phone went through the whole initial setup routine--but they didn't send us the box, I guess to cut down on mailing costs. I was hoping there was a known solution.
Ok, I downloaded two proximity sensor test apps today, but neither showed any activity. On my Captivate I get different readings with Proximity Sensor Finder (market link), but on the Nitro it is stuck at 3cm and it doesn't register anything no matter where I put my hand over the phone.
Can someone whose phone works right try installing this app and make sure that it picks up different readings on this device? OP, if you are still having issues, can you also try this app and see if it is static for you?
Thanks.
Took off the screen protector that they installed at the AT&T store and now the proximity sensor works just fine. OP, do you have a screen protector on your device?
we had an awfully thick one from att. we have since changed it to a super thin one. screen off is not a real problem on cm9, however i feel all devices should have the option to disable proximity sensor/keep lcd on during calls.
It's worth trying to use the warranty on the phone. Even though you dont have the original sales reciept, the phone has been released for less than a year, so no matter when you bought it, it is still within it's year long guaranteed warranty window.
Finished reading the thread, I suppose this post is now irrelevent
I m facing an awkward problem with my WFS's touch.... It works pretty fine with everything for sometime but after some irregular time, it starts acting erratically and I simply loose the focus on the screen...... the touch buttons automatically start acting until I lock the phone using power button.... As soon as I do so, it works like a charm again after sometime....
Notes:-
1. It doesn't happen in any particular ROM.
2. It doesn't happen in any particular apps.
3. It doesn't happen in any particular time interval, it just happens, sometimes after 10 seconds only, and sometimes not even for half an hour continuously.... (I was watching a movie on phone on mxplayer.... It worked pretty fine for about 45 minutes, and all of sudden, the touch closed the movie....... I turnt the screen off and then again came back, then it happened again within 10 to 20 seconds continuously for about 10 times so I got pissed off and kept the mobile aside.......)
4. I have tried almost everything out there related to touch fixes for WFS, like unlock freeze problem solutions etc, but neither of them happens to work in my case.....
5. I just have a hunch that its moisture problem.... I guessed, that when I use my phone's screen continuously, it works like a charm like earlier, but when the screen gets heated up ,it starts reacting erratically......
If anyone has any solution of at least knows the accurate problem, I wold b really thankful to them...........
I have tried using different ROMs, Kernels etc...........
nikhilkaushik said:
I m facing an awkward problem with my WFS's touch.... It works pretty fine with everything for sometime but after some irregular time, it starts acting erratically and I simply loose the focus on the screen...... the touch buttons automatically start acting until I lock the phone using power button.... As soon as I do so, it works like a charm again after sometime....
Notes:-
1. It doesn't happen in any particular ROM.
2. It doesn't happen in any particular apps.
3. It doesn't happen in any particular time interval, it just happens, sometimes after 10 seconds only, and sometimes not even for half an hour continuously.... (I was watching a movie on phone on mxplayer.... It worked pretty fine for about 45 minutes, and all of sudden, the touch closed the movie....... I turnt the screen off and then again came back, then it happened again within 10 to 20 seconds continuously for about 10 times so I got pissed off and kept the mobile aside.......)
4. I have tried almost everything out there related to touch fixes for WFS, like unlock freeze problem solutions etc, but neither of them happens to work in my case.....
5. I just have a hunch that its moisture problem.... I guessed, that when I use my phone's screen continuously, it works like a charm like earlier, but when the screen gets heated up ,it starts reacting erratically......
If anyone has any solution of at least knows the accurate problem, I wold b really thankful to them...........
I have tried using different ROMs, Kernels etc...........
Click to expand...
Click to collapse
What if i told you there is a perfectly working forum for questions?
POST IN THE RIGHT FORUM PLEASE.
sukhjit321 said:
What if i told you there is a perfectly working forum for questions?
POST IN THE RIGHT FORUM PLEASE.
Click to expand...
Click to collapse
And what if I told u that I already did and when no one answered, to get this question raised to the right people I had to ask it here.........
No offense, but this problem of mine is making me mad cos sometimes my phone becomes unusable for sometime.... No disrespect to the forum rules.... Nor to you or anyone.... But I need at least a proper hint about the problem.... If you wanna delete this thread thinking that I have violated the rules, then sure, be my guest....
nikhilkaushik said:
And what if I told u that I already did and when no one answered, to get this question raised to the right people I had to ask it here.........
No offense, but this problem of mine is making me mad cos sometimes my phone becomes unusable for sometime.... No disrespect to the forum rules.... Nor to you or anyone.... But I need at least a proper hint about the problem.... If you wanna delete this thread thinking that I have violated the rules, then sure, be my guest....
Click to expand...
Click to collapse
So what? Just bump the topic. There is a proper place for posts.
YOU had a question. Hence the post should be in Q&A forum. As simple as that.
If noone replied that's because maybe no one knows any solution.
nikhilkaushik said:
I m facing an awkward problem with my WFS's touch.... It works pretty fine with everything for sometime but after some irregular time, it starts acting erratically and I simply loose the focus on the screen...... the touch buttons automatically start acting until I lock the phone using power button.... As soon as I do so, it works like a charm again after sometime....
Notes:-
1. It doesn't happen in any particular ROM.
2. It doesn't happen in any particular apps.
3. It doesn't happen in any particular time interval, it just happens, sometimes after 10 seconds only, and sometimes not even for half an hour continuously.... (I was watching a movie on phone on mxplayer.... It worked pretty fine for about 45 minutes, and all of sudden, the touch closed the movie....... I turnt the screen off and then again came back, then it happened again within 10 to 20 seconds continuously for about 10 times so I got pissed off and kept the mobile aside.......)
4. I have tried almost everything out there related to touch fixes for WFS, like unlock freeze problem solutions etc, but neither of them happens to work in my case.....
5. I just have a hunch that its moisture problem.... I guessed, that when I use my phone's screen continuously, it works like a charm like earlier, but when the screen gets heated up ,it starts reacting erratically......
If anyone has any solution of at least knows the accurate problem, I wold b really thankful to them...........
I have tried using different ROMs, Kernels etc...........
Click to expand...
Click to collapse
I'm having same problem...
Some guys from forum suggested that it may be caused by using non-HTC charger or damaged charger...But my problem has not resolved after changing charger...
Do you have any other suggestion?
Sorry everyone, my apologies for breaking the rules.....
Solution
I went to HTC customer service center and they just saw the problem and said they'd require to update the touchscreen firmware.... I asked them to do it, so they asked me for some time to get it from other service center.... They said it'd flash everything, but as of now I'm not sure whether they're right or wrong, but I'm waiting for them to get the card....
Apologies again to everyone for opening a wrong topic.... I request the mods to remove this thread....
Problem: Cannot turn on the screen by pressing the power button sometimes. The screen is black or very dim, I cannot tell. One can see nothing on the screen, and it doesn’t accept any touch input, either. The phone still rings if there’s an incoming call. If this happens, the following several presses (about 10 - 20) on the power button will probably lead to a reboot. The “screen auto-rotate” and the proximity sensor may fail after the reboot, but will recover after a manual reboot.
Frequency: Fewer with higher Rom version. About once per day for 4.3.
Other description:
The problem frequently happens when I just take the phone outside my house/office, and seldom happens when the phone just stays somewhere.
The problem seems to be irrelevant to the remaining battery capacity or the uptime, but it never happens when charging.
The problem seems to be irrelevant to the Apps installed.
The problem seldom happens in the first 3-4 days after flashing a Rom, but happens more and more frequently as time goes by. My guess is some cache is stuffed by some trash, which causes the problem. The phone may be fine as long as the trash can be cleaned up on a regular basis.
I manually reboot my phone at most every two days.
Solutions tried, but don’t work
Flashing official ROMs 4.0.4, 4.1.1, 4.1.2, 4.2.2 and 4.3 following the procedure “adb reboot bootloader; fastboot oem unlock; flash-all; fastboot oem lock”, without google wallet, not rooted.
Turning off the auto-brightness control, as suggested by some post on the Internet.
Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app
Thymo said:
Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.
Bobby_yan said:
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.
Click to expand...
Click to collapse
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.
Thymo said:
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.
Click to expand...
Click to collapse
No.
No, I just tried the official ROMs. Any suggestion?
Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...
eKeith said:
Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...
Click to expand...
Click to collapse
Thanks a lot. I'm trying it.
Bobby_yan said:
Thanks a lot. I'm trying it.
Click to expand...
Click to collapse
LagFix does NOT help in my case. Any other suggestions? Thanks.
I've also had this blank screen with calls still ring issue for as long as I can remember, nearly 2.5 yrs.
I've always suspected it's my ROM and so I'd try out another ROM'S, BUT no other ROM works like how I'd like, so I always come back to my ROM.
It doesn't happen every single day, but it does happen very often.
I've tried using apps that auto reboot daily, but eventually this blank screen issue will return.
Unfortunately I can't seem to find any solution, so I just put up with it, it's like the 1 only flaw with my ROM.
&
Not to be at all rude, but I'm really glad op has had this issue from testing other versions of Android, cause then at least I know I don't need to give up my great tablet mode ROM.
LOL
I think I've finally found a work around for this screen of death.
Using Exposed, download/install this module/extension:
Disable Proximity
http://repo.xposed.info/module/com.mrchandler.disableprox
It does exactly what it's name is and ever since then I've not once had to remove my GN battery to work again because the screen went completely dead.
NVM
Screen still goes dead.
Anyone find an actual fix to this?
isajoo,
I had pretty much the same problems with my Galaxy Nexus running CyanogenMod 11 M12.
It got better by doing the following :
Blowing dry air in the earpiece… though the proximity sensor is clearly beside it. Can't do any harm though, I guess.
Settings/Applications/All/menu/Reset applications preferences (or whatever that's called in english) : that seemed to do a lot of good to my phone ! However, it's a very unsatisfactory answer on a technical point of view, as I still don't know WHAT was precisely needed. It's a "magic wand" solution for which I can't give an explanation.
Not specifically related, but greatly helped my phone in the responsiveness area : Trimmer (fstrim) (https://play.google.com/store/apps/details?id=com.fifthelement.trimmer), an updated version of LagFix that you may already know
Hope that helped !
(I wanted to try http://www.androidlegend.com/how-to-perform-proximity-sensor-calibration-on-any-samsung-phone/ as well, but apparently, /sys/class/sensors/proximity_sensor/prox_cal does not exist on my phone…)
Hey everyone. I'm enjoying this phone but I do have a few small issues which I'm hoping I can forget about once custom ROMs start to come out
(Come on and release factory images already Razer!!!)
One of them is the proximity sensor which I find incorrectly thinks I've taken my head away from the earpiece during a call and then starts spamming commands with my cheeks.
I have this issue on like every second phone call and it's a bit irritating. Especially when I still haven't received (other than the first one when I first got the phone) any more updates.
The other main gripe is the lack of a pocket sensor/script. Probably related. As in, if you have double tap to wake enabled, good luck putting this in an awkward pocket (inside motorbike jacket pocket) without waking the screen and spamming commands again with your fingers.
Lastly. I wish they had just put the fingerprint sensor somewhere else. I have turned the screen off so many times while watching YouTube it's actually starting to really annoy me
Just wondering, even if you like this phone overall, and I do, if anyone else had these gripes?
I'm having the same issue with a Razer phone I picked up this week. It's a pain.
I've tried using this as advised on another thread and it seems to be working fine, so I'm totally lost.
https://play.google.com/store/apps/details?id=ru.andr7e.sensortest
Handaloo said:
I'm having the same issue with a Razer phone I picked up this week. It's a pain.
I've tried using this as advised on another thread and it seems to be working fine, so I'm totally lost.
https://play.google.com/store/apps/details?id=ru.andr7e.sensortest
Click to expand...
Click to collapse
I'm just glad to hear someone else is noticing this. Does nobody else make phone calls on their phones??
Had the issue with the proximity sensor on a phone call again last night. Realllly annoying.
At least factory images are out now, unfortunately, it took so long, developers etc don't look too bothered about this device - I may be wrong and would be delighted to start seeing some custom stuff out there. So long as they can keep the 120Hz functionality!
Yeah I would definitely be tempted if a good Rom was released. You're probably right about it though, not a HUGE demand for these.
I've had it several times with calls and it will be super annoying if it doesn't get fixed with an update soon. I'll give you a shout if I get anywhere with it outside of this thread.
EDIT:
And yet, I just took two calls this morning back to back with ZERO issues.
anyone any more luck on this?
nk33 said:
anyone any more luck on this?
Click to expand...
Click to collapse
Nope. I still get these issues from time to time.
I even switched to global ROM and they exist there too.
Hi all.
This issue was resolved on my phone with a hard reset (volume up + power button), then a factory reset (in settings -> system -> reset options ). The proximity sensor now works as it is supposed to.
Hope this helps.