After I have updated to Jelly bean 4.1 on my nexus s GT-I9023 phone I am facing problem which is given below
1) When I press call button for calling some person there is black out on the screen and all my buttons on the phone become nonfunctional .
3) When I receive the call from some person some time the call button doesn't function.
2) Third problem is my proximity sensor on the device which has stopped functioning after the update.
Please provide solution for this if any body has .I have already tried to reset my phone but still the problem exist .
Regards
Akhil
Same problem...... any fix out there?
Are others experiencing this problem?
Sent from my HTC One S using Tapatalk 2
Related
Is there anyone else having the same issue as I have? My Nexus S screen would turn off during/after a call, sometimes it would turn on when i press the power button and sometimes it would not. I am on stock Android 2.3.4 baseband I9020AUCKD1 Kerne version 2.6.36.7-ge382d80 android-build2apa28 #1 Build number GRJ22. I just got the OTA update the other day. Is this some kind of bug that comes with the update? I hope someone could shed a light on this matter. BTW I am on At&t if that helps. Thanks in advance!
Have den same problem in my phone to
Android 2.3.4
i9023
The screen turn's off when i answer a phone call.
I think it turns off when your in a call so that you don't touch the screen, it can detect you proximity , try on the middle of a call take the phone from your ear the screen should turn on.
Sent from my Nexus S using XDA App
I have the same problem... sometimes the display stays black after the call is finished. Then I have to press the power-button.
Rom: MIUI-1.8.19
Kernel: Netachy-1.3.7
I don't have a solution for this problem, but it certainly annoys me too.
It seems that the screen lock timer is still running while the call is in progress. You can verify this by trying to hit the home screen in the middle of the call and seeing the lock screen come up.
I also have this problem and can be very annoying.
This also happens sometimes when I am watching flash video content. As soon as the video finishes the display turns off. The person who said something about the idle timer continuing to count idle time sounds plausible. As soon as the app that was preventing the sleep/lock ends it sleeps immediately.
Sent from my Nexus S using Tapatalk
I think its the in pocket detection... does anyone how to update my kernel from 2.6.35.7 to 2.6.36.7?im not sure how to do?
I think you should just wait, as its going to be March real soon and we should start to see updates for the Nexus S and 4g coming up. If you really can't wait, go ahead .
mclee235 said:
I think its the in pocket detection... does anyone how to update my kernel from 2.6.35.7 to 2.6.36.7?im not sure how to do?
Click to expand...
Click to collapse
Are you rooted? Are you on a customer ROM?
If I'm not wrong, you can only update your unrooted stock ROM when you get an official update. (Somebody more experienced please confirm this)
However, once rooted and with a custom ICS ROM there is a whole list of Kernels that can be flashed and each one has the instructions on their respective pages.
dino993 said:
I think it turns off when your in a call so that you don't touch the screen, it can detect you proximity , try on the middle of a call take the phone from your ear the screen should turn on.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
you are correct
is that possible:
1. proximity sensor during the call in order to avoid your face accidentally touched the screen
2. over time to lockscreen , like 1 minute , but you spoke 2 minutes ... and then phone automatically screen off ?
I exprienced that sometime in stock GB ROM and custom GB ROM. I have yet to experience it in ICS so far. It could be that when you try to wake the screen up, the phone may actually try to wake up but at that time your phone call may take higher priority -- cpu wise, so it is busy processing your phone call instead. I'm thinking Windows processing priority and I'm a noob.. Or the proximity sensor processing got stuck.
This does actually happen sometimes on my 2.3.6 stock ROM (i9023). Never had problems with turning the screen back on afterwards, though.
Hello,
Anyone else experienced this?
When receiving a call, my phone only vibrates once. Ringtone is still there. I'm using LG's QuickCover for Nexus 5.
Is there a way to solve this?
Same here. It's horrible because the phone only vibrates one...
NEXUS % - ANDROID L
I have quick cover too. I was trying call without this cover and vibrate was working. When I closed the phone, vibrate worked as you described...
So it's a bug with the OFFICIAL cover?! I have receiver OTA yesterday and i discover that bug, the battery drains quickly and the lockscreen created by user preferences just disappeared as the silent mode... Common Google what is this?! Please fix that!
Yes, official cover.. Its a pity.. I really do miss a lot of calls because of that bug..
Nexoez said:
Yes, official cover.. Its a pity.. I really do miss a lot of calls because of that bug..
Click to expand...
Click to collapse
I hope Google fix that mess...
Same thing here, but for me it only occurs sometimes.
Noticed it the first time today after flashing the factory image from release day.
Also with the quick cover...
Same problem for me
I'm having the same problem with my Nexus 5 w/quick cover. With the cover on, my phone will only vibrate once for incoming calls when set to vibrate. If I remove the cover the phone will continue to vibrate when receiving an incoming call. GOOGLE, PLEASE FIX THIS BUG.!
Nexoez said:
Hello,
Anyone else experienced this?
When receiving a call, my phone only vibrates once. Ringtone is still there. I'm using LG's QuickCover for Nexus 5.
Is there a way to solve this?
Click to expand...
Click to collapse
Same here!
I tried even with Cyanogenmod 12 unofficial rom (based on 5.0.1) and still the same bug.
Come on Google!
Bug still present in 5.0.1 ?
DennizzNL said:
Bug still present in 5.0.1 ?
Click to expand...
Click to collapse
Bug still present after flashing the 5.0.1 Factory Image
Any workaround with stock?
Yes bug still appearing on Android 5.0.1
Hi guys. Could this be your problem? I was having same issue too.
Search on YouTube: My Google Nexus 5 is Not Vibrating - HOW TO FIX IT
Problem still not fixed after 5.1 update
Issue still in 5.1.1
Installed smart vibtrator and that seems to work..
Short vibrate with LG Quick Cover
I've created this tool to fix the issue on my nexus 5:
play.google.com/store/apps/details?id=org.koradesktop.mylongvibrator&hl=en
Hey Everyone,
I have installed factory image of 5.0 on my Nexus & since then I am facing the issue. My screen doesn't go off during calls & light sensor is also not working; Auto Brightness is also not working. I tried pulling back to 4.4 through which I made sure my hardware is working fine. It wasn't working in 5.0 Lollipop.
Has anybody else faced the same issue & does anyone know how to fix it?
Have attached the screenshot from CPU-Z.
Nyk
NykBradley said:
Hey Everyone,
I have installed factory image of 5.0 on my Nexus & since then I am facing the issue. My screen doesn't go off during calls & light sensor is also not working; Auto Brightness is also not working. I tried pulling back to 4.4 through which I made sure my hardware is working fine. It wasn't working in 5.0 Lollipop.
Has anybody else faced the same issue & does anyone know how to fix it?
Have attached the screenshot from CPU-Z.
Nyk
Click to expand...
Click to collapse
A few other people are also experiencing the same problem. You can follow another thread here .
There are multiple threads for this already. Please posthttp://forum.xda-developers.com/showthread.php?t=2941045 in them.
Also there is a bughttps://code.google.com/p/android/i...s Owner Summary Stars&groupby=&sort=&id=80149 report in Google. Please provide your input and vote for the bug for resolution.
Sent from my Nexus 5 using XDA Free mobile app
I have the same problem...
Any fix?
My GF's M2 Aqua has a bug with the accelerometer. If she makes a longish phone call the accelerometer stops working (i.e. no auto-rotate) without a reboot. Looks like I'm not the only one:
https://talk.sonymobile.com/t5/Xperia-M2-M2-dual-M2-Aqua/accelerometer-bug/td-p/918650/page/16
Anyone else facing this?
Apparently Sony are finally looking into it and hopefully will issue a fix in another firmware release.
Usually I'd just flash a custom ROM but there doesn't seem to be any reliable builds with a fully working camera...
I confirm that this happens to me too, I just hate it because it worked if I had NFC activated in the update before 18.3.1.c.1.13.
temporary solution
it seems that the proximity sensor has something to do with it.
somehow after a long call it stucks and blocks even the accelerometer and the compass sensors.
it happens even to me and you have to restart your device to work again, but if you talk using the headset or if you press the power button while you are talking at the phone you can avoid the bug.
for me is working all the time and i can wait patiently until the official fix
Looking at the other thread I posted, one of the users said a new firmware update has been pushed with the same version number. Let's hope it fixes it...
Accelelometer bug tread
maxray said:
it seems that the proximity sensor has something to do with it.
somehow after a long call it stucks and blocks even the accelerometer and the compass sensors.
it happens even to me and you have to restart your device to work again, but if you talk using the headset or if you press the power button while you are talking at the phone you can avoid the bug.
for me is working all the time and i can wait patiently until the official fix
Click to expand...
Click to collapse
Thanks for the tip, but :confused for how long should i press the power button...just one click or during the conversation?
Just enough to wake up the screen, can't say as my M2 has it as never had a problem of on my own one
D2303 stock 4.4.4 KK rooted philz touch recovery xposed Bravia engine 2 x-reality
I think it only affects the Aqua (2403) model. Anyway, I installed a kernel for the standard M2 model following the instructuions here: http://forum.xda-developers.com/xpe...a-2403-root-philz-touch-t3072833/post60152564 and it seems to have fixed the issue.
Apparently Sony are about to issue another software update, but I'll hold off on that until I know the status of this bug...
I have the latest update 1.15 and it seems that it doesn't have the bug anymore. I am quite happy now with phone. Hope it works for everybody
hy guys
>so when i take/get a phone call my display stays black when i remove it from my ear for at least 5 seconds even pressing the power button doesnt wake it up
im on stock 6.0 but i also got that problem on cm12,1
just wanna know if someone of you got the same problem :silly:
I read in various other topics that this seems to be a 6.0 bug that google has to fix in a future update.
I have been experiencing this also. Hopefully Google fixes it soon (by soon I mean soon, not Google soon).
I also have this problem, but for long calls. Haven't noticed it before 6.0