Database Info

[Q] Weird issue

Hi everyone,
I searched before I posted, but couldn't find a similar issue.
I'm running Cognition 3.04, and touch input seems to freeze up. If I let the screen go to 'sleep' and unlock the phone it will work for a few seconds, then start freezing again. Sometimes I can just wait a couple seconds and it will accept input. Even after a reboot, it will start this behavior after a few minutes.
The issue goes away when I go back to stock 2.1, though.
I realize the obvious solution is to stay with stock, but I was just curious if anyone else had experienced this and knew of a better solution (who wants to be on stock).
Thanks in advance.

That has happened to me before. Went away with a fresh flash and wipe of cache.

canadaboy37 said:
Hi everyone,
I searched before I posted, but couldn't find a similar issue.
I'm running Cognition 3.04, and touch input seems to freeze up. If I let the screen go to 'sleep' and unlock the phone it will work for a few seconds, then start freezing again. Sometimes I can just wait a couple seconds and it will accept input. Even after a reboot, it will start this behavior after a few minutes.
The issue goes away when I go back to stock 2.1, though.
I realize the obvious solution is to stay with stock, but I was just curious if anyone else had experienced this and knew of a better solution (who wants to be on stock).
Thanks in advance.
Click to expand...
Click to collapse
You didn't restore system data when you flashed this, did you?

canadaboy37 said:
Hi everyone,
I searched before I posted, but couldn't find a similar issue.
I'm running Cognition 3.04, and touch input seems to freeze up. If I let the screen go to 'sleep' and unlock the phone it will work for a few seconds, then start freezing again. Sometimes I can just wait a couple seconds and it will accept input. Even after a reboot, it will start this behavior after a few minutes.
The issue goes away when I go back to stock 2.1, though.
Thanks in advance.
Click to expand...
Click to collapse
Do you have any over/underclock settings applied? Are there are any voltage settings that you find?

cappysw10 said:
You didn't restore system data when you flashed this, did you?
Click to expand...
Click to collapse
The first time I flashed, I did that which I later realized to be a huge mistake. When this issue started, I flashed back to stock did a master clear and reflashed Cog, but the issue remains. Is there some step I missed in clearing out the old stuff?

This happens to me in swype occasionally. Super annoying bc it thinks I am taking my finger off the screen when I am not causing swype to be worthless. after a reboot it goes away
Sent from my SAMSUNG-SGH-I897 using XDA App

trekie86 said:
Do you have any over/underclock settings applied? Are there are any voltage settings that you find?
Click to expand...
Click to collapse
I haven't played with anything other than flashing Cognition onto the phone.
I'm going to try going through the whole thing again, but this time not reinstalling any old apps/data through Titanium Backup. I'll set everything from scratch and see if that makes a difference.

[Q] Deactivate the Search-button?

My search button is flickering, firing itself off in bursts, and I want to completely deactivate it. The flickering was/is apparent in Clockwork recovery --> Key test as well.
It first happened using a 2.3.4 deodexed rom (been using it for a month or so, but all of a sudden it started firing off), then I flashed a CM7 based rom which completely killed the button. I figured it was a hardware issue, but to be sure I flashed an ASOP rom (ZuluZulu) and after a couple of hours of use the search button button started firing off again. Between the periods of bursts, the button is as dead as ever, meaning it's lit, but does not respond (haptic feedback, opening the search app) at all.
Since I don't use the button at all, deactivating it completely would not only resolve the issue but save me the trouble of accidentally hitting it once in a while as well
I've searched a bit and found this answered thread over at Google: http://www.google.com/support/forum/p/Google+Mobile/thread?tid=49e8ca84071d51a4&hl=en
TS 4/21 said:
I have a nexus s running 2.3.3 and I will be using it normally and all of a sudden it will start a voice search without reason but, it opens and closes it really fast for as long as it wants. It only stops when I lock the phone and it does it in all my apps. I don't want to have wasted my money on a p.o.s phone just cause i can't stop it from wanting to search. Help it happens all day and more than ten times a day.
Click to expand...
Click to collapse
Google 6/3 said:
Hello again everyone,
Good news -- we've identified the source of this problem which is entirely software based. We're developing a fix which we can deploy with an over-the-air update. I don't have a timeline for when that'll happen yet, but when it's ready I'll let you know.
Click to expand...
Click to collapse
I don't know if it has anything to do with anything as not even wipe + re/flash different roms changes it though.

Marshmallow problems with spontaneous launching of Google Now, taking over device.

My phone has been misbehaving since it upgraded the OS to Marshmallow. It was primarily occurring with the Google Now app and it would take over the phone and flash up and off the screen and whilst this was going on, the phone is busy vibrating, the screen became unresponsive and generally I couldn't do anything with it during these episodes. I stopped it sending to the screen and then it was the Google app that kept flashing up, starting with a round circle coming from the app drawer icon. It has got worse over the last few days to the point that it might take me ten minutes before I could get access to the caller to make a call and even trying to shut down the device was near impossible because the confirmation box never stayed on the screen long enough to answer the question and then it didn't come back. Yesterday, after many tries to restart, it finally restarted in safe mode. If it was related to an app that I downloaded, it should have stopped then but it didn't. When I was able to get into settings, I then went to apps and then disabled google app as this was the one starting up and flashing the screen non stop. I was then asked if I wanted to replace it with a factory version which I did but I also left it disabled. The problem has continued but not as ferociously with the screen becoming unresponsive at times while the buzzing from the vibrate still occurring. I have looked up various forums but haven't found any that have similar problems described. I checked the screen overlay settings and they are enabled and that seems to be the main problem with marshmallow. I'm looking for some advice but realise that this might be too basic for this forum? Vodafone Smart ultra 6, Android version 6.0.1 Kernel version 3.10.49

Stoksie said:
My phone has been misbehaving since it upgraded the OS to Marshmallow. It was primarily occurring with the Google Now app and it would take over the phone and flash up and off the screen and whilst this was going on, the phone is busy vibrating, the screen became unresponsive and generally I couldn't do anything with it during these episodes. I stopped it sending to the screen and then it was the Google app that kept flashing up, starting with a round circle coming from the app drawer icon. It has got worse over the last few days to the point that it might take me ten minutes before I could get access to the caller to make a call and even trying to shut down the device was near impossible because the confirmation box never stayed on the screen long enough to answer the question and then it didn't come back. Yesterday, after many tries to restart, it finally restarted in safe mode. If it was related to an app that I downloaded, it should have stopped then but it didn't. When I was able to get into settings, I then went to apps and then disabled google app as this was the one starting up and flashing the screen non stop. I was then asked if I wanted to replace it with a factory version which I did but I also left it disabled. The problem has continued but not as ferociously with the screen becoming unresponsive at times while the buzzing from the vibrate still occurring. I have looked up various forums but haven't found any that have similar problems described. I checked the screen overlay settings and they are enabled and that seems to be the main problem with marshmallow. I'm looking for some advice but realise that this might be to basic for this forum? Vodafone Smart ultra 6, Android version 6.0.1 Kernel version 3.10.49
Click to expand...
Click to collapse
When you updated to Nougat, what method did you use to update? Did you update via OTA? We're you rooted when you did it?
Have you tried booting to recovery and factory resetting and wiping cache then rebooting?
Sent from my SM-S903VL using Tapatalk

Droidriven said:
When you updated to Nougat, what method did you use to update? Did you update via OTA? We're you rooted when you did it?
Have you tried booting to recovery and factory resetting and wiping cache then rebooting?
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
It was an update that appeared on my notifications and I thought it was a small bug fix update and didn't realize that it would replace the entire OS. I just allowed the update and then realized what had happened. I think it is Marshmallow that it updated to but originally the app drawer was paginated and accessed by side swipes whereas the system now is a long page of apps moved up and down. I don't know if it was rooted and I assume that that means it wasn't.
I was trying to avoid a factory reset but I did wipe the cache and rebooting. When google apps is disabled, the interruptions are less often and not for as long but it still went into a complete meltdown of a screen appearing and disappearing at such a rate that nothing can be done with it. It won't show a video because of the interruptions.

Stoksie said:
It was an update that appeared on my notifications and I thought it was a small bug fix update and didn't realize that it would replace the entire OS. I just allowed the update and then realized what had happened. I think it is Marshmallow that it updated to but originally the app drawer was paginated and accessed by side swipes whereas the system now is a long page of apps moved up and down. I don't know if it was rooted and I assume that that means it wasn't.
I was trying to avoid a factory reset but I did wipe the cache and rebooting. When google apps is disabled, the interruptions are less often and not for as long but it still went into a complete meltdown of a screen appearing and disappearing at such a rate that nothing can be done with it. It won't show a video because of the interruptions.
Click to expand...
Click to collapse
Unfortunately, I think you're gonna have to factory reset in stock recovery because there's obviously a conflict with something you already had on the device and it isn't playing nice with something that was in the update.
Sent from my SM-S903VL using Tapatalk

Droidriven said:
Unfortunately, I think you're gonna have to factory reset in stock recovery because there's obviously a conflict with something you already had on the device and it isn't playing nice with something that was in the update.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Thanks for taking the time to respond. I have resigned myself to that although it does not seem to be anything that I downloaded to the phone as it occurred in safe mode too. I was just hoping that there was a fix out there but obviously it is not a widespread occurrence.

Stoksie said:
Thanks for taking the time to respond. I have resigned myself to that although it does not seem to be anything that I downloaded to the phone as it occurred in safe mode too. I was just hoping that there was a fix out there but obviously it is not a widespread occurrence.
Click to expand...
Click to collapse
It could have been something in system that got changed during the update but the data from before the change is still there and conflicting with whatever changes were made. Some kind of saved system data that can only be wiped by factory reset or reflashing.
Sent from my SM-S903VL using Tapatalk

I did a factory reset, lost a lot of photos that had started being saved on the phone and not the sdcard after the upgrade to Marshmallow. Have had to accept that but unfortunately the bizarre behavior did not stop and it continues on and off, sometimes so bad that I cannot dial a number on it and other times it happens but I can get in between the action and dial or send a text etc. I have gradually been stopping things like notifications from google apps and traffic reports from google maps (this may have had a good effect) and anything that might be doing constant checks. It seems to have quietened down over the last day or so and I even got to play a game on it but the next option is to send it away to an engineer. I just thought that I would let you know the outcome of the factory reset.

Laggy Pixel - almost impossible to make/receive phone calls

Hi all,
Pixel 1 after one of the latest updates turned into almost unusable piece of junk ;/
I do not know if this is OTA update issue or hardware fault, but phone must be restarted frequently, otherwise is almost impossible to make phone call - phone is laggy, screen doesn't respond properly, sometimes must hold power button for several seconds to force reboot, as it is not possible to reboot using the screen.
After reboot seems to work fine until someone is calling - when I answer, the caller cannot hear me and I must restart the phone again to make another try. Sometimes it work and I can talk over the phone, but mostly don't.
Phone never been rooted or anything, always updated with the latest OTA software.
I did factory reset - no change ;/
Is there anything I could try? I was thinking to try to go back to older software, but I'm not sure if this is software issue, as didn't found any other posts on this forum describing similar problems.
It is unusable anyway, so I will try anyhing.

pawel.mrk said:
Hi all,
Pixel 1 after one of the latest updates turned into almost unusable piece of junk ;/
I do not know if this is OTA update issue or hardware fault, but phone must be restarted frequently, otherwise is almost impossible to make phone call - phone is laggy, screen doesn't respond properly, sometimes must hold power button for several seconds to force reboot, as it is not possible to reboot using the screen.
After reboot seems to work fine until someone is calling - when I answer, the caller cannot hear me and I must restart the phone again to make another try. Sometimes it work and I can talk over the phone, but mostly don't.
Phone never been rooted or anything, always updated with the latest OTA software.
I did factory reset - no change ;/
Is there anything I could try? I was thinking to try to go back to older software, but I'm not sure if this is software issue, as didn't found any other posts on this forum describing similar problems.
It is unusable anyway, so I will try anyhing.
Click to expand...
Click to collapse
Ive updated to latest ota on pixel 1 and had no problems so far. You could check the dialer app is set as default dialer and all permissions are granted and maybe clear the apps storage/cache, force stop it and re open it and see if that solves anything? Could also check background apps and running services in developing options to see if an app is banging out the memory causing it to lag?
Sent from my Pixel using XDA Labs

pawel.mrk said:
Hi all,
Pixel 1 after one of the latest updates turned into almost unusable piece of junk ;/
I do not know if this is OTA update issue or hardware fault, but phone must be restarted frequently, otherwise is almost impossible to make phone call - phone is laggy, screen doesn't respond properly, sometimes must hold power button for several seconds to force reboot, as it is not possible to reboot using the screen.
After reboot seems to work fine until someone is calling - when I answer, the caller cannot hear me and I must restart the phone again to make another try. Sometimes it work and I can talk over the phone, but mostly don't.
Phone never been rooted or anything, always updated with the latest OTA software.
I did factory reset - no change ;/
Is there anything I could try? I was thinking to try to go back to older software, but I'm not sure if this is software issue, as didn't found any other posts on this forum describing similar problems.
It is unusable anyway, so I will try anyhing.
Click to expand...
Click to collapse
if you already did factory reset then it must be a sign of motherboard is dying soon or bad nand chip. motherboard failing on pixel is very common but it happens to less than 1% of people. there are plent of threads on reddit/xda on this.

What's the status of your Pixel? Is the bootloader unlocked? Rooted? Did you have any such problems on the December udpate?

As mentioned - I did factory reset as I thought it may help cure the problems, but it didn't.
I have never unlocked bootloder and phone is not rooted. All standard here.
I have the latest update installed and same problems persist ;/
I'll try another factory reset today.

Screen goes black, buttons don't respond, can get calls from other phones to me

Hi all, I have been facing a really weird problem for the past few weeks. Sometimes all of a sudden, my phone screen completely turns black, and the buttons (as well as the alert slider) stop responding. There is no indication whatsoever that it is NOT switched off. However when I try calling it from another phone, ring can be heard as if my phone is working fine. I don't understand where the problem lies. Any suggestions are welcome.
I am rooted with Magisk 19.3, Riru-EdXposed 0.4.5.1 Sandhook, Riru-Core v19.5.
Edit: Android Pie. OOS 9.5.10.GM21AA

I had this problem recently when accessing certain apks. Reflashing the firmware sorted it for me.

no root same problem to me after I update from Android 9 to Android 10

hallo dare said:
I had this problem recently when accessing certain apks. Reflashing the firmware sorted it for me.
Click to expand...
Click to collapse
Thanks I will try doing that.

Same problem here when opening quite a few apps. Issue didn't start until I updated to Android 10 (and rooted), on a converted T-Mobile variant. Wonder if that is the source of our problem. I'm sorely tempted to use the MSM tool and go back on TMO's Android 9 (and pray for a official update to 10). Unless someone can find a solution to this, rebooting the phone every time I want to open certain apps is a real pain.

NighthawkXL said:
Same problem here when opening quite a few apps. Issue didn't start until I updated to Android 10 (and rooted), on a converted T-Mobile variant. Wonder if that is the source of our problem. I'm sorely tempted to use the MSM tool and go back on TMO's Android 9 (and pray for a official update to 10). Unless someone can find a solution to this, rebooting the phone every time I want to open certain apps is a real pain.
Click to expand...
Click to collapse
It definitely is a A10 issue as I too have started to have this issue when opening games and ram extensive apps. A workaround is to open the game or app in split screen mode and once the app has started you can switch back to fullscreen mode or start the app from recents. That has worked for me 100% of the time. The 10.0.1 update seemed to make it worse because you have to reboot the phone to escape the black screen were as at first you could use gestures to escape the app.

mookiexl said:
It definitely is a A10 issue as I too have started to have this issue when opening games and ram extensive apps. A workaround is to open the game or app in split screen mode and once the app has started you can switch back to fullscreen mode or start the app from recents. That has worked for me 100% of the time. The 10.0.1 update seemed to make it worse because you have to reboot the phone to escape the black screen were as at first you could use gestures to escape the app.
Click to expand...
Click to collapse
Good idea using split screen, I'll have to start doing that for the time being. I moved over to Open Beta 3 and the issue is still there and worst as with 10.0.1. Hopefully OnePlus can nail this bug soon. It's turning a otherwise amazing phone into a headache.

I have the same problem. Running 10.0 rooted. For me, this has only happened when opening Youtube Vanced. One clever solution is to enable "Quickly turn on camera" and doublepress power if this happens. This launches camera and returns the screen to normal.

hallo dare said:
I had this problem recently when accessing certain apks. Re-flashing the firmware sorted it for me.
Click to expand...
Click to collapse
Experiencing this too, it does seem to be related to certain .apks, how bizarre is that? Really don't want to re-flash as I am encrypted... Can you dirty-flash with an encrypted system and not loose any data?

cantenna said:
Experiencing this too, it does seem to be related to certain .apks, how bizarre is that? Really don't want to re-flash as I am encrypted... Can you dirty-flash with an encrypted system and not loose any data?
Click to expand...
Click to collapse
I reflashed through TWRP and all data was fine. I'm encrypted too.
But it goes without saying, make sure you do a backup before flashing anything