I have to admit that I love this rom. It's very smooth and has the smart stay function that I had wanted. There are some minor things that I want to know if they are only my problems.
1. Whenever a call ends, the call-end screen stays for a good 5 seconds instead of returning to either my phone screen or home screen immediately and then the screen turns dark. Is that a bug or just about this rom? I don't mind the 5 seconds delay but why would the screen go dark afterwards?
2. When I use my number pad during a phone call to enter numbers (say when calling using a prepaid card with pins), the numbers won't auto shrink to fit the screen. So I end up losing track of what I have actually entered. Is there a fix for that?
3. The JB radios are bad compared to the ICS ones, is there any way to flash any of the ICS radio in a JB rom?
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.
Hi,
my Nexus S is suffering from random touching the screen. This happens on only one spot - it's on the "m" location on the keyboard. It's very annoying when you try to type longer message - you get a lot of extra "m"s. I uploaded a video of the problem:
http://www.youtube.com/watch?v=XH_DUzuEszI
I tried different kernels and roms (even the stock ones), but the problem didn't go away. Internessting thing is, when the touching occurs, it is enough to turn the display off and then back on. Then it's ok for a while (5 minutes or logner...).
Does anyone know what might be wrong and how to fix it? I don't have warranty on the phone anymore, so i want to try to fix it before I have to buy a new phone.
Thanks
How come sometimes the screen goes black for about a second and comes back on... it's annoying when I'm playing games .. Im using the Cleamrom 2.5 but was also doing it on verizons stock rom
What is your screen timeout set to? I had this issue on my phone in 2 situations... On JellyWiz Rom it would do that right after I changed the volume while watching any video, and also randomly on the stock rooted ROM... I changed my screen timeout from 30 seconds to 1 minute and on the stock ROM it seems to have solved my issues.... Hopefully this helps....
My phone gets locked when I'm in a call, and no matter what it wont get unlocked.., as a result, I'm not able to access the keypad and worse I cant even disconnect the call., I have to wait until the person on other end disconnects..
One thing I have noticed is, this problem doesn't happens on sense-based roms., Other roms like CM, Miui all have this problem. Pls help.., i really like to use the latest CM10 based rom as my daily rom..
Do you have any software installed that could do that ? Are you using bluetooth headphones ?
Locking is standard behaviour. But I can easily unlock my phone, just like I normally do.
Can't you unlock your phone by sliding the button/ring to the right?
Sent from my Nexus 7
No,it happens on just flashed rom also... without any bluetooth headphones...
@BillGoss, by lock i mean, phone's display turns off when i pickup a call.., i tried pressing power/volume buttons, but no use.., i have to wait untill other person disconnects,on which, display turns on..
This is my first time installing custom ROM's on my otherwise stock Sprint Motorola photon 4G LTE. After successfully flashing CM13 (2016_08_20 snapshot release), I tried to make a call, and upon hitting "call" from the dialer, the screen goes black and stays that way. The only recourse is to hold down power button long enough to reboot. While the screen is black, there is no sound from the ear piece (i.e. it does not appear that the call is connected). Finally, while the screen is black, the phone does exhibit some reactions: it vibrates sometimes if I hit the power button, in other words, the device is still 'on" until I have to reboot it.
After this happened, I gave up on CM13 and flashed CM-12 (the latest snapshot release, from 2015) , and experienced the same behavior.
The call apparently was completed, because the other party received a missed call. However, there was no sound on my end (although there was side-tone, when I breathed on it)
I googled for about an hour, and saw examples of the same behavior on other devices claiming to be related to the proximity sensor (though in those cases, there apparently was audio in the ear piece-- ie. the call completed, and was in progress while the screen was black). This behavior was not observed a few minutes before under stock ROM in the same device (so doubt it's a strictly hardware issue, so doubt I need to open the device and clean the sensor, per some of the suggestions out there).
I suspect the answer is very basic, because I found no similar threads searching XDA.
Please let me know any ideas. I did not do anything about updating my baseband version from stock before flashing the CM ROMs., but don't know if I have to I'm a noob at custom Rom's and just remembered that you had to worry about the baseband / radio version back on the HTC Evo 8 years ago, which was my last time flashing. Again, the ROM itself worked fine-- wifi and 3G/LTE connectivity was a success.
Let me know any ideas.
thanks
After restoring to stock, dialing worked again on the phone, but the behavior on the device was different from two other photons I tested next to it.
In the stock ROM, the call connected, but the screen turned off immediately upon hitting "call" (even when the phone was on the desk). You could get the screen back (in stock only) by hitting the power button.
In my other two photons, the black screen does not kick-in immediately. So it does appear it could be something having to do with the proximity sensor (i.e. it's always engaged). I don't have the skills to confirm. I am writing-off this phone for now, and have a different device (so not a high-priority thread at this point), but let me know if anyone has any ideas. Thx.
There's a way to validate if the prox sensor is working - zDeviceTest in the Play Store will test all of the hardware, and it will also show the metrics each piece of hardware is receiving - the prox sensor being fairly simple, it just identifies if an object is "near" or "far".
I always recommend making sure everything works in the stock ROM before flashing anything custom - as you need to validate everything works before making tweaks.
My advice is the same as arrrghhhs. (This name really looks like it was typed with a Photon Q with some characters repeated by the device >.>)
I noticed that my proximity sensor sometimes "stuck" to near (I use some different app [SatStat] so it shows 3 cm or 100 cm instead of near/far). Winking a little above the sensor helps sometimes. But your problem sounds like a defect.