I'm not sure if I am the only one but searching hasn't really helped me find any answers. Basically, since updating (rather, doing a clean install of 4.2 tajku) to 4.2 Jellybean, I often have an issue where despite the fact that the proximity sensor blacks out the screen, the dial pad when pulled up still detects key hits. Hence, my cheek is randomly pressing buttons. Happens during voicemail since the dial pad is needed to get through menus and/or during calls which have a menu system.
Any else have this problem or have any ideas how I can resolve it?
Same here
Glad I'm not going crazy. Seems to also be happening without the dial pad, per say. I say that because it appears during a call, I was pressing something so I removed from proximity to be greeted by the lock screen (number pad). So I wonder if it has something to do with that. I am going to disable pin lock for awhile to see if that alleviates the problem.
Do you have something similar with SKype?
Do you have Skype installed?
I've something similar to this. When I am making a Skype call the screen does not go off during the call. It stays on and the only way I can make the call is to manually lock the screen before putting the phone over my ear.
You are the 5th person I meet complaining of this issue.
MenaMAKS said:
Do you have Skype installed?
I've something similar to this. When I am making a Skype call the screen does not go off during the call. It stays on and the only way I can make the call is to manually lock the screen before putting the phone over my ear.
You are the 5th person I meet complaining of this issue.
Click to expand...
Click to collapse
No Skype. And the screen goes off due to the proximity sensor - but the buttons and/or dial pad are still active. I'll try changing my power button back from "end call" to just screen off and see if that helps.
Anyway, a quick update. Seems like a couple of factory resets did the job. So something with Titanium Backup did not translate over well to 4.2 (from 4.1.2). On top of that, I can no longer seem to do a full restore, causes my device to go into boot loop. Don't know why it worked the first time. At any rate, just re-downloaded all my apps and so far so good. Just have to try and restore individual app data one by one and see if I can get it to stick without fudging up the dial pad again.
EDIT: Scratch that, it's going it again. What the hell... 4.2 is such a @#@#@ in the ass.
Still having same issue. Glad you came back with an update, bc I was about to re-flash and re-download all of my apps. I know you say that you experience it even without the keypad pulled up, but I have not. Usually happens when I call an automated system, and my call gets sent to every extension possible!
Sent from my Galaxy Nexus using xda app-developers app
Alright, I think I have it working. I did factory reset... made sure any phantom directories (i.e. storage(sdcard)/0/0/0/0 etc) were deleted.
1) By default, I tested by calling voice mail then rolling my cheek against the screen. So far so good.
2) I downloaded StickMount, Titanium Backup Pro, NTFS mounter (for ntfs driver) and ES File Explorer. Tested again as per above. OK.
3) Used Titanium Backup to restore missing apps + data. Did a test, still good.
4) Used Titanium Backup to restore only select system data (i.e. call logs, SMS log, alarm, etc). Still tests fine.
5) Enabled PGM free. Did test and BOOM, problem.
So it seems like with 4.2 there is something screwy with PGM which is essentially keeping the screen "awake" even though it's off due to sensor. Don't know why I didn't think of it earlier.
EDIT: Checked the PGM thread and it appears the author has already fixed it though only the paid version is updated atm. Says will update the free version soon if the paid version doesn't have any new bugs.
Awesome, nice work! Will see of it works for me too and report back.
Sent from my Galaxy Nexus using xda app-developers app
Edit Uninstalled PGM, reboot and its solved! Thanks for your hard work!
I was going crazy with this issue too .. it's good that it's not only me .. i will disable PGM and try
My brother's nexus has this issue without pgm installed on full stock 4.2.1 rom.
I have watched the serial code and production date is c9,or rather september 2012.
What I have to do to fix this very annoying issue?
edit: no one has this issue?It's a common problem of latest batch sold in Italy.
Related
Hello everybody,
Everything is fine with my Arc, except for the huge problem that sometimes I simply can't answer an incoming call! It happens like this: When a call is incoming, the phone starts ringing and vibrating as it usually does. However, the screen that is supposed to come up which shows you who is calling and where you can select to accept or reject the call is simply not showing up.
Has anybody experienced this before?
All I can do is slide to unlock the screen and then I'm looking at my home screen with the phone still ringing but no chance to get the call. There is nothing in the notification area or anywhere else where I could answer the call. All I can do is to wait until the ringing stops!! Really really bad behavior.
Furthermore, once the ringing has stopped, there is no information about the missed call in the call log. So I can't even call back the person who called me!
First time this happened I had "Plants vs Zombies" running so I figured the phone wasn't fast enough to switch to the incoming call. But it also happens when the phone is idling.
There seems to be no scheme behind all of this. Sometimes it happens twice in a row, sometimes only once a week.
I got my unbranded simlock free Arc in mid April with 2.3.2 and .181 firmware and applied Gingerbreak for root access. Later I upgraded via PC Companion to 2.3.3. and .145 firmware. But I lost root which I didn't like. So I downloaded the Generic World Firmware .181 and flashed it on the phone. Then used Gingerbreak again and made an OTA update to 2.3.3. and .145 firmware. Now I have root and the latest firmware.
All the while I used Titanium Backup to restore all my data, settings and apps as I don't want to reinstall all from scratch because it would take forever.
With this latest firmware, everything is fine, except for the call problem!
Please help me, what can I do?? I don't want to reflash and upgrade or whatever or lose all my data. I just want my phone to be able to handle calls as it should be!!
P.S.: I used Antek App Manager and frooze (not deleted!) some apps which where uncessesary and running in the background or at startup which speed up my startup time and free ram quite a bit. But I didn't frooze any crucial apps, at least I hope. Only stuff like Chinese keyboard and Let's Golf etc.
Also, if I would have frozen the call handling app or something, I wouldn't be able to accept calls in most cases, wouldn't I?
P.S.: I used Antek App Manager and frooze (not deleted!) some apps which where uncessesary and running in the background or at startup
Click to expand...
Click to collapse
Think you may have answered your own question here...
could be, but on the other hand I only frooze really stupid apps which should not affect any important functions of the phone. Also, if I frooze something important related to calls, why is it working most of the time? This is what I don't get.
Here is what I frooze (most of them just took up space in the app drawer and I don't use them), maybe it helps:
- stock browser (I use Opera)
- chinese keyboard (I'm german and don't need it)
- "Downloads"
- retaildemo
- live ware manager
- fb mediadiscovery
- dlna server
- news and weather
- postcard
- SE setup wizard
- sim toolkit
- sony ericsson sync service
- playnow
- sony ericsson support
- track id
- twitter
- let's golf
- google talk
- sony ericsson sync client wizard
so is your problem solved?
Anything related to google should be left alone news and weather should be fine to freeze or delete but would leave Talk alone, and depending what data from which FW was backed up, might also be an issue.
so I defrosted Google Talk. Anything else I should defrost?
Under "Settings" and then "Running services" I sometimes stop "Timescape Legacy Plugin" or whatever it's called because it takes up RAM. Could this also be a cause but I believe it's only for the Timescape app which I seldom use.
drsoran2 said:
Hello everybody,
Everything is fine with my Arc, except for the huge problem that sometimes I simply can't answer an incoming call! It happens like this: When a call is incoming, the phone starts ringing and vibrating as it usually does. However, the screen that is supposed to come up which shows you who is calling and where you can select to accept or reject the call is simply not showing up.
Has anybody experienced this before?
Click to expand...
Click to collapse
I have the exact same problem.
It doesn't happen often but it's really annoying either way.
I barely installed anything off the market and I don't use any sort of app killers/managers.
that's strange because I thought it could be my own fault because I played around and frooze same apps. But it's "good" to know that I'm not the only one.
Do you have any hints about when it happens or when not? Can you exclude anything?
Today, I re-enabled all the froozen apps and then frooze some of them again, according to the thread here on xda. But only apps about which I was really sure.
Don't know how I could test if the error is gone. I mean, have people calling me 100 times and hope it occurs or not doesn't really sound great.
may be there is some problem in your firmware,try some other firmware of other region.................
drsoran2 said:
that's strange because I thought it could be my own fault because I played around and frooze same apps. But it's "good" to know that I'm not the only one.
Do you have any hints about when it happens or when not? Can you exclude anything?
Click to expand...
Click to collapse
That's the weirdest part, the only thing I used that day was Whatsapp.
The incident happened about 5 hours later, I was in a car when my phone started ringing.
I tried picking it up but.. I guess you know the rest..
I was about to buy this phone but now I'm having second thoughts.
@flamez
yesterday it happened to me again. The weird thing is, that my girlfriend said she called me three times but I heard it ringing four times! She claims she didn't call me between her second and her third call! But it definetly rang but I couldn't answer it. Also my other friends say that they didn't call me at this time. Could be someone calling who I don't know at the exact time but the chance is slim I guess.
Also whenever there is such a phantom call, there's not even a hint of it inside the missing calls log. And when this happens, nobody ever leaves a message on my mailbox. Is this the same for you? Could be the person is just lazy but I don't know.
Furthermore, it happened several times to me already and never once a person asked me later why I didn't get their call. Strange, isn't it. It almost seems like that there was no one calling at all!
Now, could it be for some unknown reason that our phones just start ringing as if there is a call but in fact there isn't one at all?! You know, the phone just running crazy and triggering the ringtone? That could be the reason why the "accept call screen" doesn't show up and there's no call log because there is now call!
I know, sounds very weird. But think about it. They could be really "ghost calls".
briggs007 said:
I was about to buy this phone but now I'm having second thoughts.
Click to expand...
Click to collapse
Well, I can tell you that this a great phone and it seems me and drsoran2 are the only ones with this problem..
Guess we just had some bad luck..
drsoran2 said:
@flamez
yesterday it happened to me again. The weird thing is, that my girlfriend said she called me three times but I heard it ringing four times! She claims she didn't call me between her second and her third call! But it definetly rang but I couldn't answer it. Also my other friends say that they didn't call me at this time. Could be someone calling who I don't know at the exact time but the chance is slim I guess.
Also whenever there is such a phantom call, there's not even a hint of it inside the missing calls log. And when this happens, nobody ever leaves a message on my mailbox. Is this the same for you? Could be the person is just lazy but I don't know.
Furthermore, it happened several times to me already and never once a person asked me later why I didn't get their call. Strange, isn't it. It almost seems like that there was no one calling at all!
Now, could it be for some unknown reason that our phones just start ringing as if there is a call but in fact there isn't one at all?! You know, the phone just running crazy and triggering the ringtone? That could be the reason why the "accept call screen" doesn't show up and there's no call log because there is now call!
I know, sounds very weird. But think about it. They could be really "ghost calls".
Click to expand...
Click to collapse
No, I don't think that's it..
It's happened only twice to me over a 2-3 month period and my friends have always called me back asking why I never pick up the phone.
It really just happens about once a month to me, and I can answer the second time they call me right away without any problem.
Are you guys running task killers?
{EDIT - I remember OP saying that he'd frozen a load of stuff.. Suggest that if you're getting this a lot that you un freeze all of it and see how it goes, maybe just freeze the end user apps - like Lets Golf HD at first then build up the frozen apps slowly until you get the problem..}
im_iceman said:
Are you guys running task killers?
{EDIT - I remember OP saying that he'd frozen a load of stuff.. Suggest that if you're getting this a lot that you un freeze all of it and see how it goes, maybe just freeze the end user apps - like Lets Golf HD at first then build up the frozen apps slowly until you get the problem..}
Click to expand...
Click to collapse
No, as I said before, I'm not using any sort of task killers/app managers.
Today first time i encountered same problem. I have WhatsApp running in background. No task killer, nothing else.
Though i donno how to solve this problem. But i can surely tell how to pick up call in this case.
Just press the power key, this will take phone in locked state, but the call wont be rejected.
now click the home key and you will see the answer key, now slide it, it will slide without problem
it's good news that you found a workaround! I'll try to remember it the next time it happens.
Today, I had the problem again but this time it was different. The slider or the contact picture of the person calling didn't appear, but I could see the number of the person who is calling in the notification bar (not the name, just the number although this number and contact is stored in my contacts).
This happened the first time, all the other times the phone just rang without any hint of who is calling.
It would be nice if we were able to pinpoint a certain event which causes this odd behavior but so far I had no luck. What I'm doing differently since the last time it happened is, that I don't use task killers anymore. But still, it happened again today.
It's difficult to find out what it is when you don't know what causes it and when it will happen. For example, it happened to me today once for the first time in about a week.
in recent days, "it" happened very often to me!
Sometimes, the phone manages to at least show the number of the person calling so that I can call back. But usually it doesn't! The call just disappears into nirvana.
Do you guys remember if the error is associated with a certain amount of RAM left available? In other words, if the available RAM at the time of the incoming call is below a certain limit (which I don't know) the phone can't display the call. When it happened to me today, I had only 90MB RAM left. Maybe the phone can't free up enough RAM fast enough?!
Also the trick, which somebody mentioned a few posts above me, that when it happens you press the power button and then home and then you can slide and accept the call very rarely works!
I'm desperate and don't know what to do about it. I have just finished adjusting my phone to my needs. I linked apps with Link2SD and now have over 100 apps installed and still 215MB left on the internal memory, I have root and the .145 firmware. Everything is fine, except for this error!! It would take ages to restore it to the point where it is now, if it is complety possible at all.
I mean, if a phone can't handle calls, what good is it for?
I had a NEC e616 years ago which frooze while sending SMS or crashed after connecting a call or during a call and other "funny" things, but this was well known for this model.
But we don't have 2004 anymore and I except the Arc to work.
I could send it in on warranty, possibly. But then everything would be erased and it would take forever to get it repaired.
And I'm afraid they are going to tell me that they couldn't reproduce the error (because it happens so randomly)!
Such a nice and beautiful phone if not for this stupid error!
I'm already tempted to get rid of the phone and look for something else. But who's going to buy a phone with a bug which can't display phone calls?!!
I mean, I could reset it and flash the fimware and stuff and then hope. Maybe the error is gone. Maybe it persists and then all my data is gone and I have to start from scratch.
Or it is gone and then I have to start from scratch also!
If I should be forced to do it all over again and have all the work, then I could do it on another phone as well.
The Samsung Galaxy SII is quite ugly, to wide and big but I hope it can at least handle a call?!
Thank you for any help!!
Hmm..
If it happens rarely.. Why don't you sell it off on ebay
If asked about other mobile. I prefer sensation to sgs2. Much better phone function. In fact IMO htc is better than all other androids when it comes to phone functions.
Sent from my LT15i using XDA Premium App
I have a problem where, I am in a conversation in Whatsapp, and i am done writing a message, and then i lock the screen, and when i unlock it maybe 15 seconds later, i type, but nothing is showing up, its just records what i press but doesn't type. I have to go the the main screen, and reopen Whatsapp to get it working again...
Anyone else notice this?
Its really annoying if you are in an intense conversation and have to act fast
ROM: Codename Android 1.5.5
Kernel: FrancoKernel Milestone 2
I have wiped everything 1000x times and reinstalled everything. Found some people who had the same issue, but no one found a solution.
Thanks XDA,
David
Dubadai said:
I have a problem where, I am in a conversation in Whatsapp, and i am done writing a message, and then i lock the screen, and when i unlock it maybe 15 seconds later, i type, but nothing is showing up, its just records what i press but doesn't type. I have to go the the main screen, and reopen Whatsapp to get it working again...
Anyone else notice this?
Its really annoying if you are in an intense conversation and have to act fast
ROM: Codename Android 1.5.5
Kernel: FrancoKernel Milestone 2
I have wiped everything 1000x times and reinstalled everything. Found some people who had the same issue, but no one found a solution.
Thanks XDA,
David
Click to expand...
Click to collapse
Happens sometimes to me too and I am rooted on stock. Pretty sure it has nothing to do with us and everything to do with whatsapp having an ICS bug.
Sent from my Galaxy Nexus using Tapatalk
Whatsapp used to have exact same problem on my Nokia 5800XM too, I think it happens because of Whatsapp.
confirmed this happening occasionally on LG optimus one.
therefore, it is definitely because of the whatsapp app itself
usually i just press back button for once, back to conversation list and go back to my conversation. typing works back so you dont need to go homescreen thats two steps back
Confirmed bug for me too
Galaxy Nexus GSM
AOKP M4
Franco M2
To everyone who replied, thank you! Makes my life easier knowing its not ROM/Kernel etc...
Filed a complain to Whatsapp, such a great app apart from this bug!
Miasmic said:
confirmed this happening occasionally on LG optimus one.
therefore, it is definitely because of the whatsapp app itself
usually i just press back button for once, back to conversation list and go back to my conversation. typing works back so you dont need to go homescreen thats two steps back
Click to expand...
Click to collapse
I usually press home button and then my Whatsapp icon on my main screen, usually goes fast, but still... rather annoying
How deep would this 'error' lie? Could devs fix it?
I get this exact same problem with Handcent! Currently using Swype, and like 30% of the time I will have to go back to the conversation list and re-select my conversation to start typing again.
Sent from my Galaxy Nexus using Tapatalk
Quick question, is everyone using NovaLauncher too? It sometimes happen with normal SMS as well. But 95% of the time it is Whatsapp
ohh3nry said:
Quick question, is everyone using NovaLauncher too? It sometimes happen with normal SMS as well. But 95% of the time it is Whatsapp
Click to expand...
Click to collapse
I am also using Nova, but I'm not sure why that would affect other apps like this.
Any solution to this problem?
Got the very same at my galaxy s6, too. Android 5.1.1
I'd also like to know if there's any workarounds for this. My wife's having the issue and she's blaming me. :silly:
I may have a workaround. I have the galaxy note 3 and i use a custom rom thats pretty much close to stock and I notice that if I lock the device and unlock shortly after, I can't type anywhere, on kik, what'sapp, gosms pro, even google search. So I've just decided to test things out and see what's going on and here is what I found....
Eventually I can type again if I simply wait, but no one likes to wait but this is the longest solution.
Clearing the RAM using built in cleaner or 3rd party memory cleaner seems to allow me to type again.
I didnt like playing the guessing game in knowing how long to wait before I can type again so in kik or go sms pro, I would type one of the native apps' emoticon and then hold the backspace button down until it erases it...then I knew it was ready to let me type again (I have haptic feedback on for keyboard presses so I can look away as I hold down the backspace button - this would let me know when it eventually erased due to the haptic feedback of the smiley getting deleted).
Since the issue occurred only after unlocking, I tried turning off the lock screen completely and turning off phone and back on again....keyboard types right away with no issues!
Its more secure to have a lock screen on the phone so turning off lock screen isn't the best option unless you're like me and are the only person at home with no worries of someone else taking your phone so I decided to try something else that seemed to solve the issue, and that is..............turning off "Multiple Widgets" in lock screen.....tested and worked! I can totally type again right away after unlocking the lockscreen shortly after locking it.
This is what worked for me and for you developers out there....if you can use this to pinpoint why this happens on android, perhaps you can use this information to rectify it.
Hope I helped!!!
I searched the AT&T Galaxy S III General forum and saw no other posts similar. Essentially, I was wondering if anyone had experienced other bugs in the stock firmware. I am not rooted and have not modified my phone's software from stock.
There are two bugs I currently have seen. One I can and will provide screenshots of. This is where during the lockscreen the formatting will be incorrect, such that the last number on the time will be small and the charging text appears on the same line. Also note that the lockscreen shortcuts at the bottom are spaced oddly. I always have five icons, yet sometimes only 3 or 4 show spaced unevenly. I can reproduce this by watching Netflix and while a video is playing, I lock the screen. When I first unlock it, this will happen. This will fix itself if I relock the screen and wake the device again.
The second bug is in the messaging app. Sometimes when my device falls asleep by itself while I have the keyboard up and active on a thread, and I wake it, the keyboard is unusable. I can click on the message block to bring up the keyboard, but all of my keystrokes are not entered into the message block. I have to back out of the keyboard and thread, to the thread list, then go back to the thread. My previous keystrokes are still not showing, but the keyboard will then work.
Anyone else noticed any bugs?
I'm fine on my phone
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I've had the second bug happen with the keyboard maybe a handful of times since I got the phone but definitely not a regular occurrence.
I wouldnt worry too much about it but if it bothers you that bad just try a factory reset.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
No problems here
Sent from my SAMSUNG-SGH-I747 using xda premium
MercilessLTD said:
The second bug is in the messaging app. Sometimes when my device falls asleep by itself while I have the keyboard up and active on a thread, and I wake it, the keyboard is unusable. I can click on the message block to bring up the keyboard, but all of my keystrokes are not entered into the message block. I have to back out of the keyboard and thread, to the thread list, then go back to the thread. My previous keystrokes are still not showing, but the keyboard will then work.
Click to expand...
Click to collapse
I've only experienced this issue that you describe. I've gotten used to it, so I'm now indifferent towards it.
I've had issues with the battery life however and how the actual "percentage" is being reported, but I think that it's just Jelly Bean that is causing the issue when my device is restored to stock setup as opposed to running ICS. Sometimes, my phone gets really warm overnight (and I can assure you that nothing is running in the background). Looking at the battery graph, I see a sharp drop within the space of about 20 minutes. This causes the back cover of my phone to be discolored. My i747 is only 5 weeks old and I'm the original owner.
phone minimizes
I have an issue where my phone screen turns off when I'm it for a while (typically at work I use a wired headset). When I wake the phone up and swipe on the lock screen, the phone shows the phone "app" for a second then it jumps to the home screen (as if I hit the home button). Typically I'm unlocking the phone so I can either hit a number on the phone (like, press 1 for English) or I'm wanting to hang up. So I have to go back into the phone application to do either task.
ICS didn't do that to me.
Me and a few others have experienced a bug where the external sd unmounts itself at random. Mostly when the screen goes to sleep. For one freezing the MTP application with tibu solved his sd problem but by doing that you cant mount your phone to a pc. As far me nothing has helped yet. My external sd just unmounts at random and I have to remove it and put it back several times to get it to work again and sometimes and I have to format it in the pc to get it to work again. This has happened to a a lot of tmobile users. I never noticed this problem on ics so im assuming its a jb problem. Its not a micro sd card being bad because it does it with my other cards to and one is a very expensive Samsung card..
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
get2brad said:
I have an issue where my phone screen turns off when I'm it for a while (typically at work I use a wired headset). When I wake the phone up and swipe on the lock screen, the phone shows the phone "app" for a second then it jumps to the home screen (as if I hit the home button). Typically I'm unlocking the phone so I can either hit a number on the phone (like, press 1 for English) or I'm wanting to hang up. So I have to go back into the phone application to do either task.
ICS didn't do that to me.
Click to expand...
Click to collapse
I think this has happened to me once or twice. But I guess with the scarcity it's happened I thought I was bumping the back button or home button with my face, i.e. a failure of the proximity sensor to correctly detect my face.
I just started noticing the Keyboard Messaging bug myself. Wasn't sure why it was happening.
I just remembered (or refreshed my memory since my phone just started doing it) that whether or not TalkBack is off or on, my phone needs to tell me which number screen I am whenever I slide my finger across the dots at the bottom of the home screen or the app drawer. Is this a different setting I am missing or is this another bug?
I have had the messaging bug occur a couple of times. No biggee to me considering it has only happened twice in a month's time. I have seen other phones with much more persistent and annoying bugs and by comparison, this is nothing.
no problems here... i like it a lot now
Problem on Stock/root
Hey, not sure if this is the right place for this post, but my GS3 is on stock jelly bean and rooted. For some reason I am not receiving incoming calls. I tried calling my phone from gmail and the phone rings, but nothing happens on my phone. Any ideas as to why this is
Luker161 said:
Hey, not sure if this is the right place for this post, but my GS3 is on stock jelly bean and rooted. For some reason I am not receiving incoming calls. I tried calling my phone from gmail and the phone rings, but nothing happens on my phone. Any ideas as to why this is
Click to expand...
Click to collapse
I'm not sure if this is the right place either, since this is generally non-rooted, although the topic doesn't specify that I suppose.
However, I would venture a guess that you may need to wipe your data and cache. Sounds like a default app issue to me.
If I use bluetooth headphones on my walk to work, then plug in wired headphones at work, the audio plays out of the speaker.
It's really annoying because it happens every morning (as it's too early for me to remember things like that) and blasts my podcasts to my coworkers. Removing the wired headphones and reinserting fixes the issue.
No issues here.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I have never had any of these issues
Sent from my SAMSUNG-SGH-I747 using xda premium
miketigerwoods said:
If I use bluetooth headphones on my walk to work, then plug in wired headphones at work, the audio plays out of the speaker.
It's really annoying because it happens every morning (as it's too early for me to remember things like that) and blasts my podcasts to my coworkers. Removing the wired headphones and reinserting fixes the issue.
Click to expand...
Click to collapse
Actually, I've had a similar issue. I use Google Play Music (as a carry-over from my Nexus S). When the first song of the playlist would finish (using the headphone jack to play through my car stereo), the second song would start on the phone speaker.
It doesn't seem to happen anymore, but it did directly after the JellyBean update.
PIN Lock Instantly with power button
I am upset that the "Lock Instantly with Power Key" option missing from 4.1.1. I have been searching for a fix, but I must be the only one annoyed by this, or I'm bad at searching.
...
I have a pin lock but am used to a 15 min delay before I need to enter the pin, and being able to push power to shut the screen off at will. That is no longer an option as it always will lock to the PIN screen if the power button is pushed. It is very annoying to me.
Another bug is the Keyboard defaulting Samsung Keyboard on reboot. Every time I restart, I have to go back into settings to select Swiftkey.
Okay this has bugged the heck out of me for ages, maybe someone knows the answer to it.
The top notification bar (and sometimes the row underneath in certain apps) sometimes is completely unpressable, as if it's being blocked. I should note this happens on my Note 7, but has also occurred on my Note 3, my old S2 and even the S7. Which makes me think it must be a setting I choose, or an app I install.
Sometimes, I'll turn on my phone, go past the lock screen and I won't be able to drag the notification bar down. I found a workaround (which has worked on all my old phones).
- Turn the phone off
- Turn it back on
- On the lock screen try to drag the notification bar down (which doesn't do anything)
- Unlock the phone
- Then it works again!!
My mrs had this too, and my workaround fixed it.
This issue has spanned over multiple versions of Android and is now doing my head in.
Any ideas?
Some app overlay is on top of it such as: Flux, blue light filter, and things like that. Once disable the issue is gone. That might be your issue.
jonboyuk said:
Okay this has bugged the heck out of me for ages, maybe someone knows the answer to it.
The top notification bar (and sometimes the row underneath in certain apps) sometimes is completely unpressable, as if it's being blocked. I should note this happens on my Note 7, but has also occurred on my Note 3, my old S2 and even the S7. Which makes me think it must be a setting I choose, or an app I install.
Sometimes, I'll turn on my phone, go past the lock screen and I won't be able to drag the notification bar down. I found a workaround (which has worked on all my old phones).
- Turn the phone off
- Turn it back on
- On the lock screen try to drag the notification bar down (which doesn't do anything)
- Unlock the phone
- Then it works again!!
My mrs had this too, and my workaround fixed it.
This issue has spanned over multiple versions of Android and is now doing my head in.
Any ideas?
Click to expand...
Click to collapse
I would place a 90% bet on this being a carried over app problem. Have you tried a fresh reset and reproduced the problem?
Have you also tried the service test for Touch ans S Pen? *#0*#
Kansatsusha said:
Some app overlay is on top of it such as: Flux, blue light filter, and things like that. Once disable the issue is gone. That might be your issue.
Click to expand...
Click to collapse
I thought as much. I used to have Twilight installed but I deleted it and it hasn't solved my issue!
alltaken123 said:
I would place a 90% bet on this being a carried over app problem. Have you tried a fresh reset and reproduced the problem?
Have you also tried the service test for Touch ans S Pen? *#0*#
Click to expand...
Click to collapse
I think so too. One example I have an issue with is the offscreen memo function. I pull the stylus out and can write on the screen off, but the row of buttons along the top NEVER work! But, I should say on a hard reset it was fine until all the apps were installed and logged into, or a setting was put in place. The service test for S Pen and Touch works perfectly. All I can think is trying to install 1 app at a time, and seeing what happens as a result. Will be painful with 100+ apps though. I'm about to replace my N7 on the recall too so I want to hold off on a hard reset too.
I feel your pain, if it were me I would rather discover the erroneous app now than later. Perhaps a backup via smartswitch on PC (very fast over USB 3) and when you know which app restore the backup and delete the app accordingly?
alltaken123 said:
I feel your pain, if it were me I would rather discover the erroneous app now than later. Perhaps a backup via smartswitch on PC (very fast over USB 3) and when you know which app restore the backup and delete the app accordingly?
Click to expand...
Click to collapse
By pure luck. I found it. 3 years of pain and I nailed the bugger! Something you said triggered a thought process.
It was....
Cerberus security! An app that automatically hides itself from the draw once it's installed so usually never crossed my mind.
Disabling the "Block Status bar" feature in Cerberus fixed it.
PHEW!!!!!!!!!!! Thanks for this (both of you).
good for you!
This has been annoying since I got the phone 7 months ago.
It doesn't turn off the screen when I take/make a call. I'm constantly putting my caller on hold or even hanging up with my ear or cheek. I've Googled the crap out of this and I've found MANY different settings to check/change - NONE of which exist on this phone.
So does anyone know? Is this simply not a feature of this phone?
Thank you.
bcsteeve said:
This has been annoying since I got the phone 7 months ago.
It doesn't turn off the screen when I take/make a call. I'm constantly putting my caller on hold or even hanging up with my ear or cheek. I've Googled the crap out of this and I've found MANY different settings to check/change - NONE of which exist on this phone.
Click to expand...
Click to collapse
I thought it was just me! I haven't looked for a solution as yet, but if you find one please post back here and share.
Actually I did resolve it finally! I installed a different dialer app and it worked with it. I hated the app though, so I uninstalled it. Before I had a chance to find a different app, a call came in (using the default app again) and it worked as it should. I can't explain why, but for me... installing a different app and then removing it got the default dialer to behave correctly.
Now that it works "correctly", I have noticed a quirk with it. I have to wait for an outgoing call to actually be ringing (which can take some time with some calls) before I put it up to my ear or the screen won't shut off until I bring the phone down and then back up. Now, it is *possible* that this was always the issue and I just never figured it out. So maybe the whole app install/uninstall thing is unnecessary. Not sure.
bcsteeve said:
Actually I did resolve it finally! I installed a different dialer app and it worked with it. I hated the app though, so I uninstalled it. Before I had a chance to find a different app, a call came in (using the default app again) and it worked as it should. I can't explain why, but for me... installing a different app and then removing it got the default dialer to behave correctly.
Now that it works "correctly", I have noticed a quirk with it. I have to wait for an outgoing call to actually be ringing (which can take some time with some calls) before I put it up to my ear or the screen won't shut off until I bring the phone down and then back up. Now, it is *possible* that this was always the issue and I just never figured it out. So maybe the whole app install/uninstall thing is unnecessary. Not sure.
Click to expand...
Click to collapse
I had a same problem too, but did resolved after factory reset. But I don't know where is the problem located, maybe the proximity sensor is very sensitive even with dust.
Sorry, bad English.
Your English is fine
I think you might be right, because my problem now seems to come and go. The screen definitely shuts off, but there's some times when my face will put the call on mute or other strangeness. I've even accidentally sent an email to my Mom, all with my cheek while on the phone with someone else! I had to click the back button 6 or 7 times to get back to the phone screen.
This phone was good value, but I do regret the purchase.
The proximity sensor is very sensitive, even with a very small string. I just test this when I call my second phone. And moving around my finger, and boom! My screen is turned off, but did turned on again after I moving away my finger. This is surprising me when I call my mom, and I force to turn off my device, and it's rebooted. After my device is successfully booted, I tried to call my Dad, and surprisingly the screen is not turned off. So I'll try to find the problem, and I founded them:
The proximity sensor is very sensitive, so be sure to wipe the proximity sensor until it gets clean completely.
That's it, so no matter if you use a different dialer or default dialer for your device, just keep in mind that I mentioned there.
Thank you. As always, sorry for my bad English.?