I have a strange issue. My quick settings are not accessible when using any apps. I can Swipe down from the home screen and access them easily, but when I open an app and try to swipe down it does not work. Attached is a short video (zipped mp4). I had the phone come from repairs due to charging port damage and had loaded stock software through Odin. I wiped the cache and reset twice after that. All touches are also being registered properly. I am on latest July 1 patch on A50. And here is a similar issue posted on One Plus forum: https://forums.oneplus.com/threads/...-settings-not-working-in-opened-apps.1093999/
Tried this as well, but issue still persists.
Any solutions?
Related
Hi guys, I never posted here but am trying to find some help. I've had my S4 for quite a while now, and I just factory reset everything because I kept getting a "Unfortunately, the process android.process.acore has stopped." message that wouldn't go away or let me use my phone without an interruption literally every 2 seconds. But before I even had that problem, there were worse problems as well. There are two things that occur frequently:
1. Sometimes, when I tap on an icon, the indicator light shows up (a glow around the icon), but the app itself does not open. Then, if i tap on it repeatedly, nothing happens. I can temporarily fix this problem by opening up the recent/opened apps list (holding home button) and clearing everything (or clicking on that app if it had been opened). Once cleared, I can tap it again and it would open. As you might see, this can get very annoying and troublesome after doing it so many times. Is there anyway I can permanently fix this so that I don't need to keep clearing the open apps list?
2. Sometimes, when I unlock my screen, exit an app, press the home button, or clear the opened app list (as mentioned above), my wallpaper changes to an app. The app is usually random and sometimes is not one that I had opened. For example, the background of my messaging app or Astro File Manager would show up even if I had not recently opened it at all. I can also temporarily fix this by clearing the recent/opened apps list (as mentioned in #1). After clearing this, the wallpaper resets. Is there any way I can fix this permanently as well?
3. Snapchat and VSCO Cam constantly "stop unexpectedly". I don't know if this is a firmware or incompatibility issue, but it usually works fine. This message pops up once in a while and isn't too burdensome, but is still quite annoying.
Thank you for all the help in advance. I am trying to get the most out of my phone and appreciate any help.
Are you running stock or custom and has anything changed since you factory reset?
Sent from my SGH-M919 using Tapatalk
serio22 said:
Are you running stock or custom and has anything changed since you factory reset?
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
It's stock right now. Not rooted or anything at all. I didn't really change much of the device internally, only downloaded a couple of apps, but those have been working fine since the beginning. It is running Kit Kat, 4.4.2. I am currently using Nova Launcher as my home screen replacement.
I've got the "cannot connect to camera" issue since last summer, but I can still use the camera if I reset my phone once or twice. It became seriously day by day until now, I cannot activate my camera completely. "Flashlight" shows gray in top menu (but flashlight hardware is fine), Google Camera will FC after few seconds I open it.
I saw many threads in XDA and Chinese forums, tried safe mode, factory reset, wipe all data and even flash factory images, relock bootloader by following those instructions but nothing helps. I don't know why because I didn't do anything to my phone and it just naturally became like this. Except for the camera, all the hardwares and softwares as well as functions are working properly, no signs of getting worse.
I'm not sure the camera module or the motherboard has broken or not, anyone still have any ideas to fix this?
Starting today, my camera opens to a blank black screen when I launch the app. If I reboot the phone, I can successfully launch the camera app and take photos. However, if I attempt to use the camera built into Android Messages, Facebook, and even the bar code scanner app I have installed, the issue starts again. I have tried uninstalling the updates to the camera app, clearing data, and I even did a factory restore. I booted up into safe mode, then duplicated the issue there as well (this eliminates 3rd party apps as the cause). Some other threads I have read say to toggle Bluetooth or turn on airplane mode. Nothing fixes the problem.
I hopped in chat with Google Support and they had me follow this guide (which didn't fix anything). They requested the factory reset. After the factory reset, they required me to gather a bug report to send to them. I requested a replacement device, but the support technician declined and said this issue isn't something that can get a replacement device. I am very irritated I spent so much money on this device and it is already (two and a half weeks later) starting to not work.
Has anyone else on the Pixel 3 XL had this issue? Any other recommendations to fix it?
try flash-all.bat from googles factory images. could be a corrupt persist partition
I don't have an unlocked bootloader. That's required for that, right? Would I need an unlocked bootloader to flash the image?
tallymatty said:
I don't have an unlocked bootloader. That's required for that, right? Would I need an unlocked bootloader to flash the image?
Click to expand...
Click to collapse
believe so
then you can relock
process takes 5 minutes to complete
Blank camera screen when camera opened from from another app
I have the same issue with my pixel 3 xl. Blank camera when it's opened with messages app, fb, WhatsApp, Instagram, fb messages. Called Google support and they had me clear cache, uninstall cam updates restart phone and in the end factory reset but it didn't fix it. They can't identify if it's a software issue. They even had me boot up in safe mode and had screen sharing session.
After multiple calls and hours of troubleshooting, Google will be replacing my phone. Hopefully the new phone don't have this problem.
No luck for me, unfortunately. I unlocked the bootloader and flashed the factory image. The issue persisted after the flash. I contact Google Support again and they continue to tell me the issue is going to be resolved by engineering and they will not replace the defective device. Total bummer for such an expensive brick.
On support contact #3, Google has decided to replace the device for me. Just FYI, in case anyone else has this problem with their phone. I asked for a manager during contact #2 and didn't hear anything back for 24 hours. The person I got on #3 was very nice and assisted in the replacement order.
Had the same issue with 2 of my pixel 2 xl phones. First one was sent away for 2 weeks and then replaced. replacement one lasted a couple months before it had the same issues, I demanded a RMA from google so i could get it swapped in store. The second phone that was replaced lasted a day, it had a weird bright screen flash when locking, unlocking, hanging up from a call etc. That was also RMA and returned and replaced in store.
Hope my 3 doesn't have these issues.
camera hardware is crashing when used by any app other than the "Camera" app
I have the same issues during one week. What I find is the playground and any app other than the "Camera" app attempts to access the camera hardware, the camera itself becomes unresponsive.* After that, the camera cannot be accessed by any application, including the "Camera" app. There Google support told me the engineers will fix that problem. But I'm not sure if that's a hardware issue or software issues.
I'm wondering if this is a November update issue - anyone try flashing back to first release?
Similar issue here, on November, will try to flash november again and test.
Edit:
and..... did not fix a thing. Looks like it is hardware related or if there is a hardware rev in a specific part that is not coded properly.
I can assure you that it is not an issue with November patch or any patch. I have this issue and I am still running with the stock September security patch that came with the phone. I was hoping that updating to the latest patch would fix the issue, but now I'm beginning to think that won't resolve the problem.
Sent from my Pixel 3 XL using Tapatalk
I'm the new one ?
Same problem here ?
Hello guys, a few months ago I ran into this problem with my samsung galaxy note 8 (SM-N950N) where my camera app keeps crashing each time I switched from the rear camera (which works fine) to the front camera.
I had checked so many posts in this forum and beyond in search of a solution, but I kept circling back to the same set of troubleshooting instructions, which ranged from doing a simple restart all the way to factory reset and even flashing stock firmware.
I tried all of it and none of them was able to solve the front camera issue and I was tempted to think it was a hardware issue, however if I access the hardware diagnostic menu (*#0*#) I discovered that my front camera works perfectly fine.
When it was all looking like all hope's were lost, I stepped on a solution - follow in these steps;
1. Ensure that your camera app is up to date (clear app cache and data)
2. Update gallery app (clear app cache and data)
3. Enable all permissions in both apps
4. Go to the gallery menu menu (the 3 dots on top right corner) and select "camera"
You should be able to access the camera app and check to see if both front and rear camera are now working.
This worked for me and I hope someone here finds it useful.
Hey there, you may want to post in the Samsung forum to find a solution to your answer.
2nd Samsung post in the 4a5g forum..hmm..
Well done... Androids wuv attention
A hard reset seldom fixes anything except a virus or an old load that needs a refresh.
Invariably if the root cause isn't found eventually many times it reoccurs after the reload... as many have witnessed to their dismay.
My phone is stuck in a boot loop!
I have found that the only "fix" is a factory reset... but that only delays the inevitable. The boot loop returns after about a week.
I've cleared cache multiple times, repaired apps multiple times, uninstalled many apps, put every app possible into deep sleep, made sure apps are all updated in both app stores, "repaired apps", and reflashed the firmware with Odin... only to be back where I started with the boot loops.
I have found some overheating and RAM errors in logs in Recovery, as well as the following error multiple times in groups of 3:
"unable to set property "ro.boottime.init.mount.cache" to "0": error code: 0xb, try count 1-3"
Is this the culprit?
Has anyone else experienced this phenomenon and fixed it?
pipd0ge said:
My phone is stuck in a boot loop!
I have found that the only "fix" is a factory reset... but that only delays the inevitable. The boot loop returns after about a week.
I've cleared cache multiple times, repaired apps multiple times, uninstalled many apps, put every app possible into deep sleep, made sure apps are all updated in both app stores, "repaired apps", and reflashed the firmware with Odin... only to be back where I started with the boot loops.
I have found some overheating and RAM errors in logs in Recovery, as well as the following error multiple times in groups of 3:
"unable to set property "ro.boottime.init.mount.cache" to "0": error code: 0xb, try count 1-3"
Is this the culprit?
Has anyone else experienced this phenomenon and fixed it?
Click to expand...
Click to collapse
Strange.
Is your phone rooted?
Did you try using it with minimal apps installed.
Check under battery what app uses the most battery (maybe an exotic app on top is heating your phone)?
bigchrizzieboy said:
Strange.
Is your phone rooted?
Did you try using it with minimal apps installed.
Check under battery what app uses the most battery (maybe an exotic app on top is heating your phone)?
Click to expand...
Click to collapse
Not rooted.
Also, the reboot sequence happens even when the phone is in Safe Mode as well.
Will remove a few more apps--VPN and a few others that don't seem rogue but may have sufficient permissions to break a device.
Few more errors were in the logs but I don't know javascript or similar to decode, just looking for keywords and the above mounting cache error seemed most problematic.
Z Fold 4 randomly crashing/resetting after Android 13 update
Z fold for randomly crashing/resetting after android 13 update Also my watch 5 pro just disappeared from my galaxy wear app yet it is still connected and receiving notifications Anyone else having these issues Opens in new window PDF Download Word Download Excel Download PowerPoint...
us.community.samsung.com
Maybe this steps can help you?
bigchrizzieboy said:
Z Fold 4 randomly crashing/resetting after Android 13 update
Z fold for randomly crashing/resetting after android 13 update Also my watch 5 pro just disappeared from my galaxy wear app yet it is still connected and receiving notifications Anyone else having these issues Opens in new window PDF Download Word Download Excel Download PowerPoint...
us.community.samsung.com
Maybe this steps can help you?
Click to expand...
Click to collapse
Tried those already. Thanks for linking though--glad to see it's more widespread so we might see an update soon.
Good news: I've isolated the issue to be caused by the One UI 5.1 update (security patch Feb 1). Funny enough, they claim that there is a south australian app causing the issue, but don't state the app name: link.
Bad news: Samsung is censoring me on their forum and not allowing posts--and deleting them when created.
Also, their factory warranty email, [email protected], is non-responsive for 2 weeks. I'm not able to call their support phone (833)690-0918 due to the reboot loops.
Losing all goodwill Samsung built with me through the years.