Database Info

Sensor lag

Hey guys, I'm experiencing this strange issue. I'm not sure if it's hardware. When somebody's calling me and I answer the call and put my phone to my ear, there's about 3 sec lag until person on the other side can hear me. This used to work fine, it first occured when I started using Sense 3 ROM (not immediatelly), so I thought I should try Saga4D, but problem still persists. I haven't really tried any "nonsense" rom since I need Usb tethering. Is there any way to check or recalibrate this sensor?
Thanks for help!

Ok, it's most likely this issue: http://code.google.com/p/android/issues/detail?id=16230
I think it's time to switch to Windows Phone...

Good to know I am not alone...
Sent from my HTC Desire S using xda premium

I think this fixed it: https://market.android.com/details?id=cz.byteworks.cdp

Numline1 said:
Hey guys, I'm experiencing this strange issue. I'm not sure if it's hardware. When somebody's calling me and I answer the call and put my phone to my ear, there's about 3 sec lag until person on the other side can hear me. This used to work fine, it first occured when I started using Sense 3 ROM (not immediatelly), so I thought I should try Saga4D, but problem still persists. I haven't really tried any "nonsense" rom since I need Usb tethering. Is there any way to check or recalibrate this sensor?
Thanks for help!
Click to expand...
Click to collapse
not sure if this will help but have you tried including
ro.telephony.call_ring.delay=0
Click to expand...
Click to collapse
in /system/build.prop ?

Yep, common 2.3.3 problem.
What ROM are you on?
Did they fix this is 2.3.5?
-------------------------------
Sent from my HTC Desire S

Hey, thx for all answers. Fix I posted works only every few times. I use Saga4D, It's 2.3.5 Sense 3 ROM. Is there any Sense 3 ROM w/out this issue?
Sent from my HTC Desire S using Tapatalk

I don't really intend to bother anybody, but I had this problem with two Sense 3 ROMs. Is there any Sense 3 ROM you guys use without call answer delay? Besides official from HTC, I rather wouldn't S-ON my device just to check if I have update available. Thank you!

[Q] Proximity sensor not working

Let me explain my issue.
My proximity sensor stopped working (it would work occasionly) when running HyperNonSense ICS. I tried installing the DHD proximity sensor app, but that doesn't support the kernel. I have recently flashed virtious inqusition, and the sensor now will not work at all. I have tried the DHD app again, with the same issue, and I have tried pointing a camera at it whist calling voicemail, however there was no responce. I have also tried a proximity sensor app (http://goo.gl/TlTa8 and http://goo.gl/9gf4V) however both show no reading.
I guess I am going to have to send it in (I don't want to be without it!!!) Unless anyone has any suggestions.
EDIT: Sorry mod - didn't realise I was posting in general!

Bump
Sent from my GT-P1000 using XDA

I also bump this!!!
Proximity / light sensor also recently stopped working and the and I'm currently stock with s-on. I am probably just gonna send it in for repair.
Sent from my HTC Sensation 4G using XDA

Ok, restored back to stock (1.50) with ruu and the problem is still there.

brilldoctor said:
Ok, restored back to stock (1.50) with ruu and the problem is still there.
Click to expand...
Click to collapse
I believe this is a hardware issue as it is probably with mine.
Sent from my HTC Sensation 4G using XDA

According to the user manual, the proximity sensor is in the top left corner, under the glass of the screen, do you have a full size screen protector on, it could be blocking it.
John.

Tinderbox (UK) said:
According to the user manual, the proximity sensor is in the top left corner, under the glass of the screen, do you have a full size screen protector on, it could be blocking it.
John.
Click to expand...
Click to collapse
I always thought that the proximity sensor and the light sensor were in the same area, but regardless both of mine seems to be messed up. The led lights at the bottom of my phone don't even come on anymore. :-\
Sent from my HTC Sensation 4G using XDA

Same problem here.Any solutions so far?
If sending it back for a repair will fix it,that means there is actually a way to fix it,so why no one knows how to do it?
It`s a HTC secret or something?!

Mine just died today fully. Phone would turn on over the last couple of days then when it goes into stand by the screen would freeze. A pull of the battery and reboot would not get it to come back on. I then treid a couple of adb reboot commands and it got it back again.
Then today it just died. Not getting battery light or anything. All it will do is power on and vibrate then nothing. As I am custom rom I cant send it back or they will charge a fortune, so just bit the bullet and ordered a new one arriving on Saturday

Let me just clarify - I have no screen protector on - Just this case http://www.amazon.co.uk/gp/product/B005B3OEV2/ref=oh_o01_s00_i00_details - I have sent the phone in to carphone and will report when I get it back

GhostXSeries said:
Mine just died today fully. Phone would turn on over the last couple of days then when it goes into stand by the screen would freeze. A pull of the battery and reboot would not get it to come back on. I then treid a couple of adb reboot commands and it got it back again.
Then today it just died. Not getting battery light or anything. All it will do is power on and vibrate then nothing. As I am custom rom I cant send it back or they will charge a fortune, so just bit the bullet and ordered a new one arriving on Saturday
Click to expand...
Click to collapse
When you plug it in to your PC, is it coming up with QLOAD USB or something like that?
Also, try http://forum.xda-developers.com/showthread.php?t=1198585 (AT YOUR OWN RISK!!!)

Ok, just got it back from repair and its working fine (but they updated it so now I can't s off it)
Sent from my HTC Sensation Z710e using XDA

brilldoctor said:
Ok, just got it back from repair and its working fine (but they updated it so now I can't s off it)
Sent from my HTC Sensation Z710e using XDA
Click to expand...
Click to collapse
@brilldoctor: I have been struggling with this for WEEKS! It is NOT a hardware problem. It's an upgrade to ICS and get stuck with this **** problem! I tried other threads and nothing successful. My capacitive backlights for the touchpad under the LCD's dont work either WITHIN a ROM. In recovery they work fine. Another run-around was to Fix Permissions in Recovery also and then boot into the ROM and sometimes they all worked, sometimes they didn't. Another one was to SuperWipe and start from scratch down to the Radio flashing level.....same ****, lights, sensors don't work.
I'm still going crazy trying to figure it out as it is NOT a hardware problem!!!!!!

Hi guys! I'm having the same problem here, my proximity sensor is not working at all, I'm on Virtuous inquisition 4.0.2 and tried different kernels but nothing! I just wanna know if it is a hardware problem or something else??

Do you guys found a solution or an explanation to the problem? Or still using your sensation without the proximity sensor?
Sent from my Sensation using xda premium

Same thing with prox sensor here
Weird thing is that, when I take the flashlight and point it to the prox sensor (with light) andro sensor Anrdoid Sensor Box reports that proximity sensor is working (0.0 cm -> 3,5 cm).
That would definitely mean that it's a software, not a hardware problem.
Maybe some kind of calibration for proximity sensor would fix it, but I can't find one (there are for rezound and zte, but no for sensation (pyramid)).
How can I just disable it?

Arachnosoft said:
Do you guys found a solution or an explanation to the problem? Or still using your sensation without the proximity sensor?
Sent from my Sensation using xda premium
Click to expand...
Click to collapse
I ended up sending it in for repair, which fixed it

Arachnosoft said:
Do you guys found a solution or an explanation to the problem? Or still using your sensation without the proximity sensor?
Sent from my Sensation using xda premium
Click to expand...
Click to collapse
Its the update that brought these problems. I've helped many with this same problem.
When you boot your phone, cover the sensor with your thumb. That is all.
Sent from my Sensation using xda app-developers app

got same problem with elegancia .... no proximity and light sensor... sad , i tryed to serch every post in google... without luck.
Some1 got some ideas , exept send to warranty. So long i cant go without phone.
and wagedroid cover dont help :S huh , so unhappy :S

I have the same problem as all of you guys. I tried everything I found as a possible solution on the web, but none of them worked for me. The funny thing is, that they work sometimes, and sometimes don't work. But what I found out, is that they are not working when the battery charge is 30%-100%, and when gets less than 30%, they start working perfectly. I tested it for about a week, and it was the same everytime the charge was getting less that 30%. So may be some of the developers might know where this problem could be coming from, since on a low charge the sensors work just fine.
If it matters, I am using my stock battery, but it is the same with my other battery.
My current ROM is ViperS 1.6.3, Sense 4.1 from this thread: http://forum.xda-developers.com/showthread.php?t=1671547&highlight=vipers

oneplus one touch screen problem?

touch screen sensitivity is so low, sometime it gets stuck when typing or just miss a few keys and very very annoying. is there a way to fix this ATM ? i'm not sure its software problem or my phone is defected. i flashed like 5 6 roms already but the problem still there, change to another keyboard and samething . any help ?

Software. Have to wait for an official fix
Sent from my A0001 using Tapatalk

sjhotwings said:
touch screen sensitivity is so low, sometime it gets stuck when typing or just miss a few keys and very very annoying. is there a way to fix this ATM ? i'm not sure its software problem or my phone is defected. i flashed like 5 6 roms already but the problem still there, change to another keyboard and samething . any help ?
Click to expand...
Click to collapse
I feel your pain. My situation is absolutely the same. I beleive it could have started after I used the chinese car charger and power bank on vacation. Did you use something like that?

sjhotwings said:
touch screen sensitivity is so low, sometime it gets stuck when typing or just miss a few keys and very very annoying. is there a way to fix this ATM ? i'm not sure its software problem or my phone is defected. i flashed like 5 6 roms already but the problem still there, change to another keyboard and samething . any help ?
Click to expand...
Click to collapse
The problem is in the touchscreen firmware and the fix have to be released from synaptics and not frome Oneplus.
The fact is that it may take a few or a long time based on the issue and it may be enven never be fixed, who knows.
As now i am really disappointed. They should have never release da device knowing of such a major bug.

ky3bmu4 said:
I feel your pain. My situation is absolutely the same. I beleive it could have started after I used the chinese car charger and power bank on vacation. Did you use something like that?
Click to expand...
Click to collapse
No, nothing related to the charger tho haha. the problem started as soon as i turn on the phone for the first time and it went crazy like that since then. i flashed almost every rom on here still no good. i flashed fusionjack slimsaber rom earlier and it really improved alot . you might want to check that rom out.i'm gonna stick w/ slimsaber for a while now i guess

sjhotwings said:
No, nothing related to the charger tho haha. the problem started as soon as i turn on the phone for the first time and it went crazy like that since then. i flashed almost every rom on here still no good. i flashed fusionjack slimsaber rom earlier and it really improved alot . you might want to check that rom out.i'm gonna stick w/ slimsaber for a while now i guess
Click to expand...
Click to collapse
Thx for the advice. For me the issue seems to be solved randomly when I restored the 33R in Twrp. However some other problems remain: like not getting back to the mobile Internet after leaving the wifi area or loseing the network at all ( curable by switching on and off the airplane mode or rebooting respectively).
My phone is cursed really xD

ky3bmu4 said:
Thx for the advice. For me the issue seems to be solved randomly when I restored the 33R in Twrp. However some other problems remain: like not getting back to the mobile Internet after leaving the wifi area or loseing the network at all ( curable by switching on and off the airplane mode or rebooting respectively).
My phone is cursed really xD
Click to expand...
Click to collapse
try slimsaber , it worked very good for me . and hope it work for you too

sjhotwings said:
try slimsaber , it worked very good for me . and hope it work for you too
Click to expand...
Click to collapse
I'm not sure if this is the same issue, but when you run a touch screen test, does it work with more than one touch? IE is multitouch working? I had an issue the other day and I resolved it by turning off the phone, attaching it to the charger and then turning it back on (read it on the oneplus forum). It is a known issue and they are working on bringing us the fix.
Hope this is helpful.

I have this issue too, although it's been mitigated somewhat by the most recent software patches they pushed in 30O and 33R. I'm on a CM nightly at the moment and it's certainly usable. I made the issue a lot better by disabling haptic feedback in the SwiftKey settings - it almost feels like that extra effort to run the vibrating motor causes the screen to respond badly or something.

Is it doing this?
http://youtu.be/XsGPsDP4V0U
If so this is what mine is doing and it's soooo annoying trying to type.

http://www.androidheadlines.com/201...ti-touch-issues-oneplus-one-fix-incoming.html

Some-not me, have been able to mitigate the problem by running a code through terminal emulator.
This has been brought up in CM bug log as Bacon 55.
You don't have to be rooted to do this.
Type: su (if you're rooted)
Type: cat /sys/class/input/input0/baseline_test
Press enter.
Note that you will need to do this every time you reboot your phone.
Credits to a member on jira cm. Forgot to name! Hope it works for you

I've tried everything and everything failed.
Let's hope synaptics pushes out a fix soon. I can't stand this issue. Basically two different touches near each other are recognized as a swype -_-'

i did a test using multitouch test app. i use 1 finger touch on the phone and got a red dot, finger #2 gave me a blue dot . as soon as my 2 fingers get close together 1 of the dot disappear, also test w/ 4 5 fingers same result .thats why if you text really fast , you get alot of missing words and sometime it lag and get stuck.

I think that until this gets fixed the phone will be not ready to be sold,too...
Sent from my Oneplus One

Here is a fix I have tried and it has helped me a lotttt.
https://play.google.com/store/apps/details?id=br.shop4apps.touchscreenbooster.com

DuckMcQUack said:
I think that until this gets fixed the phone will be not ready to be sold,too...
Sent from my Oneplus One
Click to expand...
Click to collapse
Is this phone worth purchasing since customer service is not readily available. I'm not sure if I want to spend my money and not be able to get quality customer service. What are your thoughts?

alhadee12 said:
Is this phone worth purchasing since customer service is not readily available. I'm not sure if I want to spend my money and not be able to get quality customer service. What are your thoughts?
Click to expand...
Click to collapse
As long as the touchscreen issue is not fixed the phone has to be considered to be bugged and faulty. I would not spend my money on a defective phone at a very few weeks from N6 release that will be a superior terminal by far.
Even if it gets fixed it will be not worthy the same as N& is near to come anyways.
I wish i didn't buy mine.

DuckMcQUack said:
As long as the touchscreen issue is not fixed the phone has to be considered to be bugged and faulty. I would not spend my money on a defective phone at a very few weeks from N6 release that will be a superior terminal by far.
Even if it gets fixed it will be not worthy the same as N& is near to come anyways.
I wish i didn't buy mine.
Click to expand...
Click to collapse
Thanks, I started becoming more concerned because users have been paying long wait times for service and possibly having to ship back to China at the customers cost. That's a bad deal.

alhadee12 said:
Thanks, I started becoming more concerned because users have been paying long wait times for service and possibly having to ship back to China at the customers cost. That's a bad deal.
Click to expand...
Click to collapse
Definitely. I would stay away from this thing.
And by the way who knows if the ghost touches/swypes problem is not even a software issue just as the multitouch not working when placing the phone on a non-conductive surface...

[Q] My in call mic broke only speaker phone working after running L for a few days.

I'm really not sure what happened at first I thought it was a software problem but after checking all the roms on my Multirom including my OG stock ROM and it seems to me my mic is broken. I noticed it because I use voice to text and voice search allot and it was working fine on Preview LPX13D and the white Preview LPX13D for the N5 and then it just seemed to stop working at some point. I was going to post this in the Preview LPX13D thread but after testing it in all rom and doing a factory reset to stock unrooted and the problem is still there. so i'm guessing I'am just burnt and have to send my phone back to Google. My step dad gave it to me for xmas last year tho so I don't have the order # and or was not bought by me. I guess I will contact him and see if he will send it back for me. I was posting this to see if there was a solution i was unaware of because I did see a few people posting about the same problem when L first dropped but I didn't see any solutions and i'm guessing most people just sent there's in. If I'am not able to send it back to Google What part should I order to fix it. Is it the Speaker phone part that has both mics on it or the flex cable? Thanks to everyone for their help and advance and to all of the Devs for all their hard work.

NUGZZ420 said:
I'm really not sure what happened at first I thought it was a software problem but after checking all the roms on my Multirom including my OG stock ROM and it seems to me my mic is broken. I noticed it because I use voice to text and voice search allot and it was working fine on Preview LPX13D and the white Preview LPX13D for the N5 and then it just seemed to stop working at some point. I was going to post this in the Preview LPX13D thread but after testing it in all rom and doing a factory reset to stock unrooted and the problem is still there. so i'm guessing I'am just burnt and have to send my phone back to Google. My step dad gave it to me for xmas last year tho so I don't have the order # and or was not bought by me. I guess I will contact him and see if he will send it back for me. I was posting this to see if there was a solution i was unaware of because I did see a few people posting about the same problem when L first dropped but I didn't see any solutions and i'm guessing most people just sent there's in. If I'am not able to send it back to Google What part should I order to fix it. Is it the Speaker phone part that has both mics on it or the flex cable? Thanks to everyone for their help and advance and to all of the Devs for all their hard work.
Click to expand...
Click to collapse
I got that too, definitely same problem. I can't send it to Google too. What to do guys?

maarcnylmz said:
I got that too, definitely same problem. I can't send it to Google too. What to do guys?
Click to expand...
Click to collapse
I ended up sending my phone back I tried everything to fix it.

I am having the same issue. I can't make out what the fault is. I have googled extensively and it could be one of these:
1. Noise cancellation microphone
2. Earphone jack that doesn't recognise when the earphones are removed
3. A hardware malfunction.
The thing is that I have tested all of these.
1. Covering the noise cancellation mic or fiddling with the build.prop makes no difference
2. I have tried to turn off the headphones while they were in using an app from the play store. Didn't solve the problem
3. Installed a noise meter app and when I blow /tap straight on the grill were the mic is house, there is recognition. Also tested using Google voice search. Also recognised some words. Finally, if i make a call and put the phone in speaker mode the person on the other side hears me loud and clear. So not the hardware (I don't think)
I google some more and noticed that a number of phones have this issue not just the Nexus 5. For example the OnePlus One (https://forums.oneplus.net/threads/microphone-problem.91832/page-3), the Moto G (http://www.androidpure.com/how-to-fix-the-no-sound-during-calls-issue-on-the-moto-g/) the HTC One X (http://forum.xda-developers.com/showthread.php?t=2283990), the LG Optimus (http://forum.xda-developers.com/showthread.php?t=2461432) and probably more.
So, could this be a broader problem with Android itself? I have too many questions.
Hopefully somebody brilliant from this forum will see this and apply their genius minds.

i have the same issue, need help

Lucas1 said:
i have the same issue, need help
Click to expand...
Click to collapse
I was unable to find a solution for it. I sent my phone back to Google and got a New one. If you got yours from the play store less than a year ago you maybe able to get them to replace it.

Touch Isn't working *Screen NOT cracked*

Hello, so i had my OnePlus one for a while and just recently i dropped it lucky the screen didn't crack and opens up just fine but the touch stopped working is there a fix for this? And how do i go about it.. I'm currently in Egypt so there isn't really any replacements and anyone who knows much about this device to be able to repair it at a decent price. I would like to fix it on my own, and i honestly hope its just a wire unplugged or something..
Thanks.

Rexee said:
Hello, so i had my OnePlus one for a while and just recently i dropped it lucky the screen didn't crack and opens up just fine but the touch stopped working is there a fix for this? And how do i go about it.. I'm currently in Egypt so there isn't really any replacements and anyone who knows much about this device to be able to repair it at a decent price. I would like to fix it on my own, and i honestly hope its just a wire unplugged or something..
Thanks.
Click to expand...
Click to collapse
hi firstly tell me what trouble shooting have you done and secondly what rom are you on is it stock or custom

kallum7 said:
hi firstly tell me what trouble shooting have you done and secondly what rom are you on is it stock or custom
Click to expand...
Click to collapse
I was on a Custom rom i forgot the name but i think it was Tuga its been a while since i last used the phone due to the issue. But the touch screen didn't work in recovery either.

Rexee said:
I was on a Custom rom i forgot the name but i think it was Tuga its been a while since i last used the phone due to the issue. But the touch screen didn't work in recovery either.
Click to expand...
Click to collapse
please follow this https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 and when it says it is only for hard bricks a=only still use it

Rexee said:
Hello, so i had my OnePlus one for a while and just recently i dropped it lucky the screen didn't crack and opens up just fine but the touch stopped working is there a fix for this? And how do i go about it.. I'm currently in Egypt so there isn't really any replacements and anyone who knows much about this device to be able to repair it at a decent price. I would like to fix it on my own, and i honestly hope its just a wire unplugged or something..
Thanks.
Click to expand...
Click to collapse
If you're screen stopped working after dropping it, it is most likely damaged. Dropping it will not cause any rom to malfunction and stop touch from working. It may be a loose connection, or if you got the device used from somewhere, the screen may have once been replaced and the replacement may not be as good as the original (which by no means was perfect either).

It happened to me. Open your opo, disconnect and then reconnect the screen.