Anyone getting a strange clicking sound coming out of the speaker? It always happens when my screen goes to sleep (around 1-2 seconds after) as well as performing some actions on screen.
Yep, I get this on GBRemix 2.1 whenever I start some action that involves sounds. I think it's just the speaker turning on and off. A little annoying, but I can live with it.
Strange part is it also happens when my phone is on silent. I agree it is annoying but I can live with it as well. Just wanted to know if I'm alone in it and if anyone had a fix.
Also noticed this using GingerTh3ory 4.2. Maybe a kernel issue?
I'm using Dream kernel
Related
Hi!
Just wondering if anyone else has noticed haptic feedback (eg. during typing) randomly cutting out. I thought about it just now and haven't yet been able to check if it's actually turned off in the settings when it disappears. It is turned on now however. Haven't found any pattern to this whatsoever. Anyone else?
Animec said:
Hi!
Just wondering if anyone else has noticed haptic feedback (eg. during typing) randomly cutting out. I thought about it just now and haven't yet been able to check if it's actually turned off in the settings when it disappears. It is turned on now however. Haven't found any pattern to this whatsoever. Anyone else?
Click to expand...
Click to collapse
yep can confirm the same thing i have had that after awhile it just stops
I've had the same thing, where it randomly stops, but it also then after a few seconds, gives me a quick blurb, like it hit lag, then comes back all at once.
Same here also, it stops the sound also when I'm typing and after little silence it comes back with missed sounds nd feed backs.
Same here. Though not too worried
sent from my TouchPad
Maybe I'm the only one that loses it after I let the Touchpad "sleep". I also lose my keyboard when I reboot my tablet also. I have to go into settings and redo it. I use thumb keyboard though.
Not too worried about it though. I'm sure they'll get it going.
I've searched with several different search strings and haven't found an answer to this question, so here goes;
When I place a call and bring the phone to my ear the screen turns off (dims?). At the end of the call after I bring the phone away from my ear, it takes several seconds for the screen to turn back on, sometimes it doesn't turn back on unless I press the power button.
First, is this the normal behavior for the phone app on the I777?
Second, is there a setting somewhere to change the delay for the "screen on after a call" (I know there is a setting in settings-display for screen time-out).
I hate to make the comparison, but on my iPhone (No flaming please, I'm reformed) the screen turned off and on very quickly and I just wonder what I need to do to get that kind of response on the SG2, during the phone call.
BTW, I'm running UnNamed 2.2.1 (Gingerbread 2.3x) with Entropy's kernel.
Thanks for any help.
Clean your screen.
You using a case? Maybe it's partially blocking the proximity sensor.
mbamberg said:
I've searched with several different search strings and haven't found an answer to this question, so here goes;
When I place a call and bring the phone to my ear the screen turns off (dims?). At the end of the call after I bring the phone away from my ear, it takes several seconds for the screen to turn back on, sometimes it doesn't turn back on unless I press the power button.
First, is this the normal behavior for the phone app on the I777?
Second, is there a setting somewhere to change the delay for the "screen on after a call" (I know there is a setting in settings-display for screen time-out).
I hate to make the comparison, but on my iPhone (No flaming please, I'm reformed) the screen turned off and on very quickly and I just wonder what I need to do to get that kind of response on the SG2, during the phone call.
BTW, I'm running UnNamed 2.2.1 (Gingerbread 2.3x) with Entropy's kernel.
Thanks for any help.
Click to expand...
Click to collapse
Ironically I had the same experience in UnNamed to I assumed it was just the nature of GB. It may very well have been as I don't have that issue with ICS based ROMS. And I like the dialer better to boot.
audiophan said:
Ironically I had the same experience in UnNamed too I assumed it was just the nature of GB. It may very well have been as I don't have that issue with ICS based ROMS. And I like the dialer better to boot.
Click to expand...
Click to collapse
OK,
I'm in the throes of upgrading to an ICS ROM, so maybe I'll just go ahead and see if that fixes the problem.
Thanks for the answers
I think its a sensor issue having to due with how long it waits to scan again after light levels are changed. No idea what stock settings are but I can say I don't have a problem with it on AOKP.
I have Speed Rom 5.1 on my Amaze. When I am finished with a call, the screen stays black. I try to hit the power button, but nothing happens. I have to remove my battery in order to reboot. Can someone shed some light on why this happening? I am thinking that it may have something to do with my CPU Tuner settings, but I am not sure.
mrcash101 said:
I have Speed Rom 5.1 on my Amaze. When I am finished with a call, the screen stays black. I try to hit the power button, but nothing happens. I have to remove my battery in order to reboot. Can someone shed some light on why this happening? I am thinking that it may have something to do with my CPU Tuner settings, but I am not sure.
Click to expand...
Click to collapse
Probably that or a bad flash, just reflash, see if it solves the issue.
Most likely it's something simple, like an issue with your proximity sensor. I know there was an app that could calibrate that but I forgot what the app was.
Stock Rom - Black screen while phoning
There is a similar problem on my wife's phone with a stock rom (not rooted Amaze from T-Mobile). When making or accepting a call, the screen will instantly go off even without leaning the phone against anything and won't turn on unless the power button is pressed. Sometimes the screen would turn on by itself after a while after the other phone was hanged.
I've downloaded AndroSensor app: the proximity value does't change even when touching the area near the earpiece. It keeps showing ( 0.5mA ) 3.5 in.
I've found a thread which is there since april 2012 and describes quite a similar problem.
okay.. i just the original post date for this thread.. please don't bring back threads that are 6 month's old which issues might have been solved already since no ones been posting in it for 6 months...
(anyways) this is what i was gonna say
on my current s3 when my phone is placed to my ear it cuts off the display.. and if you pass your hand anywhere near the sensor's to the top near the camera it cuts off the display.. maybe there's a feature like that enabled on the stock rom also.. or you could possible check with the system settings to see "screen" on/off settings in display or power saving mode.. or something...
Thanks for the answer. I didn't notice that the thread was that old. I think I will keep up a newer one. But the current issue isn't likely to have been solved.
The problem doesn't seem to be triggered by wrong sensor measures (because the screen will go off even after disabling the sensor) nor does it depend on the rom version (same thing on the CM10).
Resolved:
It will sound stupid but I have found a simple solution:
I have just wiped the screen in the upper left corner where the proximity sensor is located and it started behaving normally. Though I don't use any protection tape on the screen it seem to have become less sensitive because of mud or sweat.
I've had this problem on my GSII (SGH-i777) since playing around with ICS roms, in both AOKP and CMD.
What happens is, after locking it, or a program is supposed to wake it from a blank screen, nothing happens when pressing the power button. The phone is still on and the buttons on the bottom still light up and I can feel vibrations and sounds, but I cannot get the screen to come back on without rebooting.
I'm not sure what causes this and it seems to feel semi random, but I suspect it may be connected to the locking animation in some way introduced in ICS (the emulation of turning off a CRT monitor).
I'm wondering if anyone else has run into this problem and knows a good fix to avoid it (other than going back to stock firmware).
What app are you using that is supposed to wake your phone? Just my opinion but it sounds like an issue with the app.
PS. Crt off animation was introduced well before ics.
ThomasBags said:
I've had this problem on my GSII (SGH-i777) since playing around with ICS roms, in both AOKP and CMD.
What happens is, after locking it, or a program is supposed to wake it from a blank screen, nothing happens when pressing the power button. The phone is still on and the buttons on the bottom still light up and I can feel vibrations and sounds, but I cannot get the screen to come back on without rebooting.
I'm not sure what causes this and it seems to feel semi random, but I suspect it may be connected to the locking animation in some way introduced in ICS (the emulation of turning off a CRT monitor).
I'm wondering if anyone else has run into this problem and knows a good fix to avoid it (other than going back to stock firmware).
Click to expand...
Click to collapse
Try turning off CRT in system setting / ROM Control / General UI / uncheck CRT off animation. I have it off and never have a problem in AOKP
This guy probably didn't wipe everything before posting. Yes this includes your data.
Sent from my MB860 using Tapatalk 2
Hi guys, I just got the N7.1 last week, with Android 10 already on it (December update). Both are new for me, so I have no idea if these are Nokia or Android issues, but hopefully you can help me:
1) Ring volume is very loud! Even the lowest setting is still way louder than I've ever had before. Is this normal?
2) On Mario Kart Tour the sound is awful. Even on low volumes the game produces a loud crackling sound. Might be very game specific, but it's the only one I play atm
3) On the lock screen the upperleft corner of the statusbar shows the carrier. When you go to home screen this changes to clock. Quite often the carrier 'sticks' and also shows on home screen. I then have to go back and forth a bit to get the clock back.
4) Not always, but like 80% of the time, when I unlock the phone directly with my fingerprint, the home screen will show. This sounds quite normal, but I mean that it minimizes any app I was working with / had open while the lock went on. I've never had this behaviour before: it used to just go back to the app I was using.
5) Sometimes I get some serious lag while typing, until now I only notice this in message boxes on forums, like the one I'm typing in right now. During typing the letters stop appearing and everything seems to freeze. Then when I hide/lower the keyboard on my phone, the typed letters appear instantly and I can continue.
Cheers!
There are many bugs in the Android 10 update Nokia released. There are multiple topics about them in the Nokia 7.1 subforums. I know audio issues with games and other apps is one of them. As far as I can tell, Nokia has not acknowledged these bugs (even on their own forums) and there is no ETA on fixes.
I now see some reports of crackling sound, but do you guys have the other issues as well? There are a lot of annoying bugs!!
Yes!
All the other issues you face are common. The loud ring volume you acknowledged is common too and i too, face it and get disturbed by it too
The crackling sound you get in games is common too.