Develop Bugs

Keyboard does not type after unlock - Whatsapp

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!!!

[BUG] Screen Sensitivity Issue-Lag (4.0.4-4.1.x)

Problem summary
Known cause (might be others): selecting an app from the Recents list (Task Switcher)
Temporary fix: turn the screen off, then back on
Workaround: avoid using Recents list (you can use a 3rd party task switcher instead)
How to test: open Messaging, hit Home, hit Recents, select Messaging from the list. Your screen will be less sensitive until you turn the screen off and back on. You can view the pressure by going to Settings -> Developer Options -> turn on Pointer Location. This will allow you to see the Prs of each tap in your status bar. Normally your lightest taps that register will show anywhere from 0.28 to 0.32. However, after this bug is activated, you will mostly get values over 0.40 for your light taps. This is actually a very noticeable increase, especially when trying to type quickly.
Please report any other known methods to "activate" this bug. After re-assigning my Recents button to a 3rd party app (I'm using Simple Task Switcher), I haven't seen this bug at all. It seems that a couple of people have seen it produced by something other than Recents, but they haven't narrowed it down (or reliably reproduced it on purpose).
Please star this issue officially so Google can fix:
Link is http://code.google.com/p/android/issues/detail?id=29734
Note: Downloading & using Screen filter application from play store, with brightness set to

Your hands are really dirty or really dry. Try moisturizer or something.

Been using my screen for almost hour straight now. No issues.
--------+++--------
iphone. helping computer illiteracy become popular since 2007.

Hehe yes this s gonna be a difficult one to confirm. But it is definitely not dirty hands. To clarify, a quick press of the power button to lock then unlock completely fixes the issue. Same fingers suddenly register perfectly. This is driving me nuts as the phone is not even usable right now. Literally.

@rbiter said:
Been using my screen for almost hour straight now. No issues.
--------+++--------
iphone. helping computer illiteracy become popular since 2007.
Click to expand...
Click to collapse
ios 6.2 doesnt get issues.

I don't know about your other experiences, but as far as the browser goes I have the same scrolling effects as you do. I think this is how it is meant to be. They tightened the scrolling a lot and I kinda like it. Before one small flick would send me across the whole page, which was kinda annoying. Just my preference.

I'm not having this problem. It would drive me crazy too. Been using my phone alot over the past two days and I didn't run into this problem even after almost 1h of continuous surfing. Also a few checkpoints of Shadowgun didn't trigger it.
But you can confirm your problem if you enable "cursor position" in the dev options (hope that's what it 's called in english). "Prs" and "Size" should need a lot more than around 0.30-0.40 to register your touch if you have the problem you describe.

I am sorry that you're experiencing this, but 4.0.4 has nothing to do with this. 4.0.4 is just software, Galaxy Nexus is not a pressure-sensitive device, it is merely touch-sensitive. Which means that software gets an analogue signal from the touchscreen, either 1 or 0. It has no 'range' of sensitivity, so it cannot decrease in sensitivity in software (if it did, then it would not work at all).
This is entirely hardware issue and I suggest either making sure your screen is clean, your screen protection thing (if you use one) isn't acting up or if your hardware has become faulty (have you dropped it recently?).
If problem persists then return under warranty.

My wife had this issue once.
It was the third party launcher she was using.
I don't think its a matter of touch sensitivity dropping, its a matter of the system just being too slow to really work right.
It was ADW EX, fwiw.

kristovaher said:
I am sorry that you're experiencing this, but 4.0.4 has nothing to do with this. 4.0.4 is just software, Galaxy Nexus is not a pressure-sensitive device, it is merely touch-sensitive. Which means that software gets an analogue signal from the touchscreen, either 1 or 0. It has no 'range' of sensitivity, so it cannot decrease in sensitivity in software (if it did, then it would not work at all).
This is entirely hardware issue and I suggest either making sure your screen is clean, your screen protection thing (if you use one) isn't acting up or if your hardware has become faulty (have you dropped it recently?).
If problem persists then return under warranty.
Click to expand...
Click to collapse
Lol that is hilarious. You forgot the step where its the OS that actually processes the input data, so in that process, a ton of problems can arise.
And personally, since 4.0.4 I have also been experiencing a "similar" issue. When scrolling down (and only down), I experience a kind of "lag" like if it only registers the swipe movement half an inch lower. Its not a big deal, but still an issue.
Edit : What he explains as "pressing very hard" is most likely the fact that when you press harder you actually cover more surface, so the amount of extra input data can definitely impact the behavior.

I had issues for a few hours after the 4.0.4 update, where my softkey buttons weren't responding. Thankfully, it seems to be fine now, but it was a cause for concern.
Sent from my Galaxy Nexus

gokpog said:
I'm not having this problem. It would drive me crazy too. Been using my phone alot over the past two days and I didn't run into this problem even after almost 1h of continuous surfing. Also a few checkpoints of Shadowgun didn't trigger it.
But you can confirm your problem if you enable "cursor position" in the dev options (hope that's what it 's called in english). "Prs" and "Size" should need a lot more than around 0.30-0.40 to register your touch if you have the problem you describe.
Click to expand...
Click to collapse
Thank you my friend, I should have thought of this; now I have numbers to confirm this. So with cursor option enabled I can get down to 0.30, managed 0.28 once. However when the bug starts, I can confirm that I cannot get below 0.60. It just refuses to register that input for some reason.
I lock the screen, 1 second is all it takes, and now it registers down to 0.30 again and all touch works properly. Its almost like some type of memory leak issue is the way it feels to me. It only starts happening after a few min of use.
Its definitely an issue now that I can see the pressure numbers. The question is what the hell can I do about it. I flashed aokp29 with the latest 4.0.4 ota merged in, problem still occurs. I'm gonna try stock 4.0.2 or 4.0.1 just to see. Thanks.

I have never had much luck upgrading Linux versions. That's why I start fresh every time with Android. Lol
Sent from my Galaxy Nexus using Tapatalk

Before I start digging, anyone know specifically which driver controls the touch input? I'll try looking thru github.
Also I was on stock 4.0.1 prior to this. So this could be normal behavior for everyone but everybody is used to it since nobody stayed on 4.0.1 like me. Cause I can easily say this is difficult to notice if you aren't paying attention. The question is, why does locking the screen temporarily change it back...

I can confirm some of what you are saying..sometimes when I'm browsing the scrolling tightens up..I lock the phone then unlock it and it is smooth again..doesn't happen all the time tho..doesn't bother me but I've noticed it
Sent from my Galaxy Nexus using XDA

I can also confirm. This morning I found the Swiftkey was lagging on Facebook. Something like the phone did not receive the touch. Then I rebooted and now it is ok.
I did not get this issue on 4.0.2 and I don't install anything new on 4.0.4.
The way I installed 4.0.4 was from the official factory image, so my phone is fresh! I reinstalled all apps manually as well. Nothing fancy apps.

I know this is my first post, but I can definitely confirm this issue.
I use my Galaxy Nexus for development, so the screen is always on. The sensitivity goes down very quickly.
My phone was an International GNEX that I loaded the US firmware on and then I flashed the OTA 4.0.4 update.

kristovaher said:
I am sorry that you're experiencing this, but 4.0.4 has nothing to do with this. 4.0.4 is just software, Galaxy Nexus is not a pressure-sensitive device, it is merely touch-sensitive. Which means that software gets an analogue signal from the touchscreen, either 1 or 0. It has no 'range' of sensitivity, so it cannot decrease in sensitivity in software (if it did, then it would not work at all).
This is entirely hardware issue and I suggest either making sure your screen is clean, your screen protection thing (if you use one) isn't acting up or if your hardware has become faulty (have you dropped it recently?).
If problem persists then return under warranty.
Click to expand...
Click to collapse
Just to point out, the phone is all digital. It does not get an analog signal from touching the screen. Also to that point you said analog but then described digital with the 1 and 0

Has anyone affected tried going between 4.0.2 and 4.0.4? To check the possibility of a driver or some related value changing.
Also, if not fixed by going back to 4.0.2, this could be due to current leakage from somewhere causing the touch to not work properly. I've seen it on other capacitive touch devices, though mainly when a non-compatible charger is connected. When you shut the screen off, the charge causing the problem/interference with the touch is temporarily dissapated, but then comes back after you use it again. Probably very unlikely in this case, unless Google changed something in the touch driver that makes it more sensitive to interference, which in turn messes with actual input from fingers.

TechNoir said:
Has anyone affected tried going between 4.0.2 and 4.0.4? To check the possibility of a driver or some related value changing.
Also, if not fixed by going back to 4.0.2, this could be due to current leakage from somewhere causing the touch to not work properly. I've seen it on other capacitive touch devices, though mainly when a non-compatible charger is connected. When you shut the screen off, the charge causing the problem/interference with the touch is temporarily dissapated, but then comes back after you use it again. Probably very unlikely in this case, unless Google changed something in the touch driver that makes it more sensitive to interference, which in turn messes with actual input from fingers.
Click to expand...
Click to collapse
Its possible. I was on 4.0.1 so perhaps this issue originated in 4.0.2 but I never noticed since I didn't update then. I can add that I did multiple wipes and clean flashes, and also tried both aokp 28 and 29 (new 4.0.4 ota merged), and happened on both.
I'll post what I just sent to arbiter which gives more insight.
From my extra testing under normal use my light touches register 0.28-0.33. Especially on swipes, the end of the swipe registers 0.28 as the finger travel breaks contact with the screen giving that swipe extra input which pushes the swipe motion further extra boost. When the bug starts the touch swipe won't even break 0.38-0.40, and that extra swipe data is lost resulting in the end of the swipe data points being excluded and swipes travel half the distance.
This gets exacerbated on the keyboard when fast typing light pressed. Its so bad it frustrates my face off cause typing just ceases to be possible. Such a difficult issue to diagnose.
Click to expand...
Click to collapse
Yes my face literally flew off!

[Q] 4.2 Issue with proximity sensor/dialpad?

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.

4.2.1 bugs on GNex

I hope there is no similar thread on this yet and I request to all to add bugs here
my device: GSM international yakju-rooted
bugs:
1. clear recent apps in landscape mode, then switch to portrait mode and the cleared recent apps are BACK!!....and vice versa!!
2. Did OTA update with Bluetooth on and cannot switch off Bluetooth now with devices paired. Bluetooth switches back on automatically as soon as I try to switch it off. Correct me if this is a change in 4.2.1 or if this is indeed a bug.
Other complaints
1. apps on lockscreen widgets starting up randomly
2. 3 sec lag to start daydream and camera app
3. butter gone
4. laggy
luckily no random reboots and broken Bluetooth as others have reported on my device yet. I am not happy Google.

1. doesn't happen with me
2. can't test that (no bluetooth accessories)
Others:
1. lockscreen needs improvement (like clock widget auto resizing itself to full screen when swiping through screens)
2. my camera app starts in less than 2 seconds
3. 4.2 is a little heavier than 4.1.2 but still buttery compared to other high end phones
4. not on my phone

Something which happens to me when creating events on calendar... If i manually type in the end time of the event and the minutes are 59 (e.g. setting the end time to 22:59) when i press okay the time goes back one hour (e.g. 22:59 becomes 21:59). Anyone else?

I have none of the issues any of you have specified.
Sent from my Galaxy Nexus

I got the same Recent App bug, which I didn't notice before!
But overall it is running smoothly. Did you try factory reset or flashing stock image?
jam_27 said:
I hope there is no similar thread on this yet and I request to all to add bugs here
my device: GSM international yakju
bugs:
1. clear recent apps in landscape mode, then switch to portrait mode and the cleared recent apps are BACK!!....and vice versa!!
2. Did OTA update with Bluetooth on and cannot switch off Bluetooth now with devices paired. Bluetooth switches back on automatically as soon as I try to switch it off. Correct me if this is a change in 4.2.1 or if this is indeed a bug.
Other complaints
1. apps on lockscreen widgets starting up randomly
2. 3 sec lag to start daydream and camera app
3. butter gone
4. laggy
luckily no random reboots and broken Bluetooth as others have reported on my device yet. I am not happy Google.
Click to expand...
Click to collapse

* I listen to podcasts via Bluetooth car audio during my drive to and from work. Ever since 4.2, I get frequent Bluetooth disconnects while I am listening to audio. This never happened before 4.2. Unfortunately, 4.2.1 did not fix it.
* When third party apps such as Locale or Tasker turn WiFi on, it will not connect to any access points in range. However if I turn WiFi on via the WiFi settings, it connects immediately.
* Car mode is broken in 4.2 and 4.2.1. A "car home" app used to be able to invoke a mode where the home button would return you to the car app instead of the desktop. Now, the home button drops you to the desktop and crashes the launcher (Android's desktop process).
* Overall, much more lag and delays. Looks like 4.2.x is optimized for the Nexus 4 and its 2GB of RAM. 4.1.2 seemed perfect -- too bad we only had it for less than a month.

Well, my screen shuts off at random.. I can still press stuff, but it's totally black!! I have to put the battery and restart

bugs
I cannot use my BT headset, it disconnects when screen is off.
Camera is very very laggy.

Wipe phone and flash complete stock image!
I have none of these bugs! Bluetooth works like a charm.

Stock browser omnibox issue. When I open bookmarks and links from 3rd party appss, it's all good.
But when I try to type a search or url, the adress bar freezes and stays frozen on the screen. Rotate the screen and it becomes a black empty wasted space.
Is it a bug in in 4.2/4.2.1 or is it my phone?
Sent from my Galaxy Nexus using xda app-developers app

i find it takes a couple of swipes of the security pattern at times, screen doesnt always respond as quick if ive not used my phone for a few hours.
didnt happen on 4.1.2 , not a massive issue but i do notice it

FrankNS said:
Wipe phone and flash complete stock image!
I have none of these bugs! Bluetooth works like a charm.
Click to expand...
Click to collapse
Firstly, It sounds bit too much to do a complete wipe and re-flash or a factory reset for just a dot.dot update.
Also, I have been reading that for some wipe and re-flash did not fix the Bluetooth issue. Also, a just a factory reset after OTA hasn't worked for all.
Can we please have confirmation here that a the factory reset thingy works so that all of us having issues can give it a shot?
In case we should wipe and re-flash, can it be done in the following way?
1. full backup system (in my case using titanium backup)
2. factory reset
3. copy the relevant image , yakju 4.2 in my case, into memory and flash zip using cwm recovery (6.0.1.5 in my case). then flash 4.2.1 similarly.
4. restore root.
5. system data/apps restore
please let us know.

International Yakju here and I've get the most annoying out of the problems. Random soft restarts. I've done a soft reset and it didn't help. I'm getting really pissed at this. Thinking of rolling back to 4.1.x

I havent tested bluetooth but I have random errors, sometimes when phone is locked It vibrates, I unlock it and it is asking with wich program I want to open, I choose gmail and it attaches a bug report, a .txt file with 4mb and a screenshot tottaly black.
weird. 4.2.1 yakju

jam_27 said:
I hope there is no similar thread on this yet and I request to all to add bugs here
my device: GSM international yakju-rooted
bugs:
1. clear recent apps in landscape mode, then switch to portrait mode and the cleared recent apps are BACK!!....and vice versa!!
2. Did OTA update with Bluetooth on and cannot switch off Bluetooth now with devices paired. Bluetooth switches back on automatically as soon as I try to switch it off. Correct me if this is a change in 4.2.1 or if this is indeed a bug.
Other complaints
1. apps on lockscreen widgets starting up randomly
2. 3 sec lag to start daydream and camera app
3. butter gone
4. laggy
luckily no random reboots and broken Bluetooth as others have reported on my device yet. I am not happy Google.
Click to expand...
Click to collapse
I agree with the 3rd and 4th points. Camera app is quite different from ISC 4.0 and Jelly Bean 4.1, both icons are rotating while the phone is rotated. However, Jelly Bean 4.2's icon, instead of rotating, they shift the position while the phone is put as horizontally. I hope these will be fixed in the near update.

jam_27 said:
I hope there is no similar thread on this yet and I request to all to add bugs here
my device: GSM international yakju-rooted
bugs:
1. clear recent apps in landscape mode, then switch to portrait mode and the cleared recent apps are BACK!!....and vice versa!!
Click to expand...
Click to collapse
I got the same bug on both my galaxy nexus and nexus 7. For those who said that they don't have this bug, did you leave at least one app on and rotate the screen while having the recent apps menu open? Try again.

NexusDro said:
I got the same bug on both my galaxy nexus and nexus 7. For those who said that they don't have this bug, did you leave at least one app on and rotate the screen while having the recent apps menu open? Try again.
Click to expand...
Click to collapse
Just tryed that, no bug.

Can I turn off updates
OTA update to 4.2, totally stuffed my setup, flashed 4.2.1, no difference, have now flashed stock 4.1.2. to make the phone work as it should do.
Problem 1: The signal strength meter vanished on my car screen, no indication that bluetooth had connected.
Problem 2: The speaker, as I am sure we are all aware, is rubbish. I am using the pucker car mount and have a small speaker system set up and hooked into this so that I can hear warnings from CamerAlert. The phone connects over bluetooth but the CamerAlert warnings are directed out of the device speaker and go via the car mount to the speaker system - works a treat. With 4.2 this totally disappears and I get half a warning from the device speaker itself.
Having gone to 4.2 and back I can vouch for the fact that it is the update that is wrong.It will take me another day to get the 'phone back as I want it and I will then do a full backup. Thanks a bunch Google for, really professional update.
All I want now is for the 'phone to stop nagging me to update, anyone know how to turn off updates ??

my phone freeze after taking a picture today, so weird it didn't happen before and i need to pull out the battery in order to restart the device because the power button not give a respond.. so sad.. in 4.1.x everything is good.. for the first time on my gnex i need to pull out the battery twice today.. huh!!

Wow. I was very pissed of with the overall lagginess of 4.2/4.2.1 update, but I thought I might wait and hopefully Google will fix that. But then I noticed just how ofter the stock launcher crashes (leaks from RAM anyways). 5-10 times in an hour after using heavy apps like Chrome, Pocket, Facebook etc I press home button and I get and empty wallpaper. WTF? How is this even possible for a stock app?. And then there are things I've mentioned in other similar 4.2-reated threads like camera animation that lags and music widget that stops responding and keeps playing after headphones are unplugged...Gosh, that's the worst update (for me at least) ever. And now I noticed that recent apps bug. It does exist. Awesome.

Note 4 Suddenly Having a Multitude of problems. Hardware Issue?

Hello, I have had my Note 4 for quite some time now and have not had any issues with it up until the last month or so.
At first it started out as just a hiccup every now and then, an example would be when I play music via bluetooth to my Jeep CD Player, I would sometimes have to turn bluetooth off then back on to get it to connect or reconnect.
Now things are getting out of hand. Here is a list of problems I have on a daily/hourly basis and seemingly at random times. I cannot reproduce any of these problems (except the NFC problem) on demand.
I have noticed that rebooting the phone will clear up these issues (except NFC) for a short time, SOMETIMES. Other times a reboot does nothing to help the situation.
Keyboard Lag
Sometimes when I press the keys the phone vibrates indicating a key press and magnifies the key that is being pressed, but fails to enter anything in the text box/input field. For the record I am using Swiftkey. I have noticed that this happens most often when I open an app via "popup notification." For example, if I were to receive an IM or SMS I would tap on the notification that pops up, which then switches to/opens the corresponding app. It is then I will more often than not have this issue. To remedy this I have to close and re-open the app, sometimes several times causing the keyboard to open and close, several times... Sometimes when I TAP a key, the phone will behave as though I have held the key down or performed a "long press." This issue is not exclusive to the keyboard, it often happens anywhere on the screen and with any app, usually indicating that I have been "long pressing" for about 1-2sec at a time.
NFC Does Not Work
One day while I was at work I attempted to add the office printer via NFC. To my surprise I was unable to turn on NFC via the "quick settings" drawer. In the quick settings panel the NFC icon would light up, as if it were turning on, and then just turn right back off again, this happens consistently. I went into setting to enable NFC that way and I am stuck with a slider that is actually in the "on" position but greyed out, I am unable to interact with it.
Bluetooth Connectivity
I have a JVC CD player in my Jeep, I often use YouTube or Google Play Music when I drive. Usually I do not have any problems connecting to the CD player at first, but after about 30-60sec of playback the audio goes blank. The app says that it is still playing however no audio can be heard. Then it will suddenly come back on after about 5-10sec, and here is where it gets strange. After the audio comes back on after this "hiccup" the playback is fast, as in it is playing at 2X's it's normal speed, makes the vocals sound like chipmunks. This will continue indefinitely until I turn on the screen, unlock the phone, then shut the screen off. Then the audio goes on playing fine. This happens with both YouTube and Play Music, while using YouTube the video gets sped up as well. I also experience issues with connectivity where sometimes at random the phone will just disconnect from the CD player, and refuse to reconnect until I have rebooted the phone, or if it does reconnect I get no audio until the phone is rebooted. I notice that this ONLY happens when connected via bluetooth. If I turn bluetooth off while this is happening music will play over the phone's speaker perfectly normal. My CD player has a hands free feature, and I do not seem to have any issues with phone calls, it's only with music playback do I have problems.
Originally I thought it was my CD player acting up, however in light of the other problems, and the fact that I tested it with my tablet and two of my friend's phones without issue, I don't think the CD player is the problem.
Sluggish/Glitchy UI
Sometimes when the phone really freaks out, the UI behaves very strangely. Sometimes notification Icons will hover above the running app, other times the whole screen will lock in place for a few seconds. Sometimes if the screen is locked up, I will shut it off, then turn it on, shut it off, turn it on. However as I press the power button to turn the screen on and off, nothing is happening, the screen just stays black while the "back" and "recent apps" buttons light up at the bottom. Then when the screen does finally come back in it will flash on and off quickly in accordance with how many times I pressed the power button. While all this is happening, if I hold the power button to turn the phone off, the power/reboot menu will appear without incident. Sometimes when I am swiping to unlock the phone, it does not register the full swipe. Basically it acts/appears as though I lightly touched the screen and moved my finger a half inch even though I have drug my finger all the way across the screen. To remedy that issue I have to SLOWLY drag my finger across the screen and then it unlocks without incident. I have also noticed that when I go to "swipe away" a notification, especially one that has "information" in it, it will swipe off the information but leave the notification there and display the app name the notification was from. An example would be, if I just installed an app (for example YouTube) from the Play Store, the notification will say "YouTube has been successfully installed." When I swipe either left or right to remove that notification, a "white ghost box" or "overlaying top layer" with the "successfully installed" text in it will slide away. However it leaves behind a green box/notification that says "Google Play Store" and that remains until I shut the screen off and turn it back on.
NFC Will Not Turn On
I simply cannot get NFC to turn on, the slider is in the ON position but is greyed out as I mentioned earlier. I would post a picture but I guess there is a 10post rule before I can do that. I have given up on NFC, mostly because I rarely use it, so it's really not that big of a deal.
Initializing the Camera
I use an app called "Telegram" instead of SMS messaging, thus I use Telegram to share pictures with friends. Sometimes, again I am not able to reproduce this problem on demand, the problem comes and goes seemingly at random. The camera will take more than 30-60sec to initialize, while I am waiting for it I am stuck with a black screen. If the camera doesn't initialize, shutting the screen on then off will take me back to the telegram app. I never get an error message or anything. Other times when I try to use the camera it pops on instantly and works flawlessly. Originally I thought this was a problem specific to telegram, however in the name of science I tested it with the default camera app and get the same results.
USB File Transfers
I'm not really sure this is specific to my phone, but whenever I transfer files from my PC to the phone or from the phone to PC, it is PAINFULLY slow. It's even painfully slow when the PC just displays what is in the folder. However I can't say for sure this is related because I never attempted to transfer files until I started having these issues, at which point I thought it would be a good idea to start backing things up.
Gets Stuck in 3G Mode
This happens rarely, not even sure that it's related but I felt that it was worth mention.
What have I done to try to remedy this problem you ask?
So far I have performed a non-root ADB nandroid backup, just in case factory resetting the phone didn't work.
I have factory reset the phone 2 times, I see no improvements.
I have cleared out my SD card/removed SD card
I removed and/or shut off bloatware apps (Yes I tested the phone without removing/disabling bloatware, still having the same issues)
Wiped cache via Recovery
I am not sure what else I can really do to fix the phone, I am starting to think that this is a hardware issue. I should mention that there was no significant event that I feel would cause these malfunctions. System update installed and worked perfectly up until this last month, I have not dropped the phone from significant height, the phone has an otterbox anyway. I have not gotten the phone wet, it has not been left outside, this phone has not seen any abuse what-so-ever. I just started having these problems out of the blue and they seem to be getting progressively more frequent and longer lasting. If I don't get any ideas from here I am going to try to get Verizon to replace the phone via insurance, however I don't have high hopes for that because I have grandfathered unlimited data and this is not the "original" phone that I had when I added the insurance option, so I am not sure it's covered.
Does anyone have any ideas on what could be causing this or anything I can do to correct it or try to troubleshoot it?
Any help is greatly appreciated!
Phone Information is as follows:
Samsung Galaxy Note4
Model: SM-N910V
Android Ver: 5.0.1
Baseband Ver: N910VVRU2BOG5
Build#: LRX22C.N910VVRU2BOG5
HW Ver: N910V.05
Verizon Wireless
Non-Root, Default Launcher, Not modified in any way.
I realize that this is a long post but whenever I ask for help I like to be detailed. If I left out any information that might be helpful please let me know.

Unfortunately, it looks very much like components on your logic board are going bad. Sometimes a few specific things will go bad that don't actually make the phone unusable, but make it act similar to what you are explaining. It wouldn't be worth the money you'd have to pay someone to track down the bad components and replace them. If you really like the note 4, I would just make a full backup with kies while you can, buy a new phone and restore your backup.

All of Kies backups do NOT restore to a new phone! Only contacts, messages and call logs will restore on a new phone. Use Samsung Smart Switch or Helium. Good luck
Sent from my SM-N910V using Tapatalk

outcasted2003 said:
All of Kies backups do NOT restore to a new phone! Only contacts, messages and call logs will restore on a new phone. Use Samsung Smart Switch or Helium. Good luck
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
I see. I didn't know that because I've always restored my backups to the same phone. Thanks for the info.