[Q] Camera Error - Cannot connect to camera. - Nexus S Q&A, Help & Troubleshooting

Just bought a new Nexus S [ GT-I9020T ] Factory Unlocked Sealed Phone. Got home, Did a full charge and started up the phone and followed the Initial Setup. First notification came up for a OTA upgrade to 2.34. Upgraded it. Everything was ok for couple of days.
Now! When i received a video call through Google talk the app was keep on crashing. Was not able to see any video or send any. Went into the camera app and it says Camera Error - Cannot connect to camera.
Read few threads and Googled the issue and tried the video chat with Qik, Fring etc and still had no luck.
Tried to restore/ wipe and it helped. The camera app worked and didn't see an error message. Until i tries to switch to front camera in the settings. Same Problem and the only thing solved it was a wipe/restore.
Tried to download a fresh 2.3.4 update and applied as an update instead of restore. Same issue, nothing changed.
I don't think it is a hardware issue. Has anyone else faced the same problem ? Is there a solution ? or is there a way to downgrade to the 2.3.3 firmware ?
Details in the Phone as of now
Model NO: Nexus S
Baseband Version: I9020XXKD1
Build Number: GRJ22
Please Help!

No one faced this problem?

techvin said:
No one faced this problem?
Click to expand...
Click to collapse
go the main phone settings, applications, manage applications, all, camera, clear data, then reboot. did that fix it?

simms22 said:
go the main phone settings, applications, manage applications, all, camera, clear data, then reboot. did that fix it?
Click to expand...
Click to collapse
Worked, thank you so much!

bighill89 said:
Worked, thank you so much!
Click to expand...
Click to collapse
sweet! works every time

Argh, problem is happening again. I don't want to have to Clear Data and Reboot every time I need to take a photo. Is there a long term solution? What's the cause of this anyway?

bighill89 said:
Argh, problem is happening again. I don't want to have to Clear Data and Reboot every time I need to take a photo. Is there a long term solution? What's the cause of this anyway?
Click to expand...
Click to collapse
corrupt data.

bighill89 said:
Argh, problem is happening again. I don't want to have to Clear Data and Reboot every time I need to take a photo. Is there a long term solution? What's the cause of this anyway?
Click to expand...
Click to collapse
you dont have to reboot.

simms22 said:
you dont have to reboot.
Click to expand...
Click to collapse
I tried force stopping the camera then clearing the data without a reboot, but it doesn't work. When I open the Camera app, the screen just goes black. I can press the Home button to exit.

Just did a factory reset. Back camera worked, but as soon as I switched to front camera, the app went black. I pressed the Home button. Then when I went back into the Camera app, it just said "Cannot connect to camera."
On the phone with Fido now to discuss repairs. I have a stock Nexus S with Fido, unrooted.

Wowzers, this is getting serious.
I rooted my phone, installed CM7 to see if it was a software problem, and still the same problem.
Now I unrooted my phone, locked the bootloader, and tomorrow I'll be giving it to Fido to send it to Samsung for warranty repair.

Help ?
I am having same problem with the frontal camera, after using video chat on messenger 1.4, I am running CM7. please help

meblacq said:
I am having same problem with the frontal camera, after using video chat on messenger 1.4, I am running CM7. please help
Click to expand...
Click to collapse
You might be **** out of luck dude. I just gave my phone to Fido to send to Samsung for warranty repair.

Related

Massive app crashes, phone unusable

Hi,
My girlfriend has the moto g and since this morning it's unusable: every second comes a crash message that a app fc. All apps belonging to Google (YouTube, calendar...) are crashing and especially the launcher. It's just possible to go to settings via quick toggles. But I can't delete any data etc from apps. And it won't accept any changes to any settings. I can't open any app because the launcher doesn't work...
The problem: it's an unrooted, totally stock phone with just a few apps (whatsapp, chronus...) . Now I wanted to ask if anyone can help and maybe knows this problem and how to fix it. And: I can't connect it to the PC (win7). Anyone has a link and a description to install the USB drivers? I tried all the "normal" ways with Motorola device manager and manually install USB drivers. I want to backup the messages and pictures before I try a factory reset. I rebooted it in secure mode, but all the problems still exist...
I hope anyone can help... Thanks in advance!
I want the moderator to ban me.
alikpronoy said:
If it always crashes how would you be able to back up SMS and picture? Try to go to the store you bought your phone or call your tech support. But if nothing happens you just need to factory reset your phone.
Click to expand...
Click to collapse
If it connects to the pc, you can easily make a backup of these things. The Problem is that it doesn't connect because i have problems finding the correct usb driver.
alikpronoy said:
As much as we want to, but I think, there's no way to back it up. You just need to factory reset it.
Click to expand...
Click to collapse
Already tried a factory reset - doesn't work. Can't even boot into recovery... Now it's sent back to Motorola I would love to know what happened there on a complete stock phone with just a very few apps and just used for messaging, calls and photos. I hope Motorola says what went wrong when the phone is repaired.
Try to uninstal apps and try instal again.Maybe not completed installed before.
My girlfriends phone started doing the exact same thing this morning, what was the outcome? Did they replace the phone?

[Q] android.process.acore has stopped, on ALL lollipop roms, after complete wipe!

Okay, guys, here's the problem. I have been pulling my hair out for days over this. On any Lollipop ROM I install, no matter what combination of gapps and AOSP ROM I install on my OPO, after completely and totally formatting caches, system, data, and /data/media, the problem persists:
Always after logging into an account, but not always the same one, I start to get an error "android.process.acore has stopped." It happens every few seconds and renders the device unusable. I have tried every fix I could find online, including wiping contacts storage data, contacts data, etc. I have formatted my phone several times, and each time the problem comes back. It only stops when I disable Contacts Storage in settings, which then in turn disables all contacts functionality.
This is getting totally ridiculous, and the only thing I can think of is that the AOSP version of contactsprovider.apk is totally corrupt. Any ideas?
I have the same problem... Did you succeed in resolving it?
flolep said:
I have the same problem... Did you succeed in resolving it?
Click to expand...
Click to collapse
Somewhat. The issue manifests itself when Facebook is synced with your contacts, and you use Facebook OAuth to sign into another app. For whatever reason, this causes the contacts app to go nuts, and the only way to fix it once it happens is to get rid of the Facebook app. It's a bug that is quite beyond me to fix. There is a modded Facebook apk floating around somewhere, that has had permissions modded so it's not allowed to use your contacts or register as an account in your phone. That works. It also works if when you install a new ROM, you sign into any apps that use your Facebook login before you install the Facebook app, that way you log into them with the browser and they never talk to the contacts app. Once you have installed the Facebook app, DO NOT EVER click "Sign in with Facebook" in any app on your phone, or you're screwed again.
That's pretty much what I've come up with thus far. Hope that helps.
EDIT: Here's the link to the thread with the modded Facebook apk: http://forum.xda-developers.com/showthread.php?t=2333637
I have the same issue on all CM12 based roms. It seems to happen for users with many contacts (hundreds). Uninstalling facebook seems to fix the problem for me. I have no such problems on my Nexus 5 with the same setup and facebook installed, so I wonder if it's not something specific to the bacon CM12 code.
prometheus1010 said:
I have the same issue on all CM12 based roms. It seems to happen for users with many contacts (hundreds). Uninstalling facebook seems to fix the problem for me. I have no such problems on my Nexus 5 with the same setup and facebook installed, so I wonder if it's not something specific to the bacon CM12 code.
Click to expand...
Click to collapse
It happens for other phones users... See here : https://productforums.google.com/forum/m/#!msg/nexus/Ip-hdFEQccY/OSFCz4Qj59oJ
Thanks for your partial solution @jkotzker... For me it's a no go because I am a big facebook user and I can install app with Facebook account linked at anytime... It's really really annoying to not log with Facebook account if the Facebook app is installed I don't know what to do... I tried everything like you.
I've recently been getting the same issue but mine says "unfortunately the process com.android.phone has stopped" everything was fine had this phone for about a month was on a lollipop ROM and that just randomly popped up. At first I thought it was the ROM so I switch to another lollipop ROM and got the same issue. So I went back to the latest ota kk ROM and til now I'm still getting the pop up. What's going on here? Please help
marcviado said:
I've recently been getting the same issue but mine says "unfortunately the process com.android.phone has stopped" everything was fine had this phone for about a month was on a lollipop ROM and that just randomly popped up. At first I thought it was the ROM so I switch to another lollipop ROM and got the same issue. So I went back to the latest ota kk ROM and til now I'm still getting the pop up. What's going on here? Please help
Click to expand...
Click to collapse
Oh yeah I've been trying to figure this out since cm12 unofficially came out for the note 4. Like all of you said it's fine for a while or sometimes it's messed up right away. I've had it work for two or three days then out of nowhere just have the error pop-up and never go away. Disabling google contacts storage also got rid of the error for me but of course I can't have the phone without google contacts and sync. This last time it happened just by downloading and signing into Dropbox, which isn't related to Facebook at all. This is belong frustrating because nobody seems to have a fix and it's the only thing stopping me from using cm 12. Is there any Dev that can help or work on this with a logcat?
Sent from my SM-N910T using XDA Free mobile app
pablo1215 said:
Oh yeah I've been trying to figure this out since cm12 unofficially came out for the note 4. Like all of you said it's fine for a while or sometimes it's messed up right away. I've had it work for two or three days then out of nowhere just have the error pop-up and never go away. Disabling google contacts storage also got rid of the error for me but of course I can't have the phone without google contacts and sync. This last time it happened just by downloading and signing into Dropbox, which isn't related to Facebook at all. This is belong frustrating because nobody seems to have a fix and it's the only thing stopping me from using cm 12. Is there any Dev that can help or work on this with a logcat?
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
I didn't find one...
I talked about this problem in xda temasek rom thread and ak kernel thread without success. I even sent a message on official cyanogenmod website, with last crash and logcat attached. No success. The problem happened in 2012 too... And since then, Google didn't have a solution for it.
It seems that Google is finally aware about this problem and the correction could arrive in "a future version"... Well. I want it now... Indeed, there seems to be only to increase the buffer transaction between applications and contact storage from 1MB to 2MB for example, to have it corrected. But no dev wants to do it because the problem cannot be reproduced! And it's rare! But we have it! It's incredible to have it back after a full wipe... And happening randomly, just after a random sync between application and Android system...
Any more updates on this issue/ anything else we can do to get this resolved? Even my partial, temporary solutions have stopped working, and I am getting really frustrated.
Glad to see I'm not the only one here with this issue. Took different search terms to eventually land me here since this such an old and somewhat common issue. Nonetheless... Same problem. OnePlus One running Temasek CM12. Disabling contacts storage.... Blah blah blah. Its rather disappointing there's no actual solution instead of a workaround. But, I'm finally happy to know its Facebook. An app I rarely use but do need unfortunately.
Edit: wondering if anyone has had any luck fastboot flashing the factory image? I know it's a pain in the ass to have to back up all your files, etc off the device so I'd like to know if anyone has had success or even tried this. Cuz, I really won't feel satisfied until I've resorted to this last measure if there's the possibility of eradicating the problem.
t3chn0s1s said:
Glad to see I'm not the only one here with this issue. Took different search terms to eventually land me here since this such an old and somewhat common issue. Nonetheless... Same problem. OnePlus One running Temasek CM12. Disabling contacts storage.... Blah blah blah. Its rather disappointing there's no actual solution instead of a workaround. But, I'm finally happy to know its Facebook. An app I rarely use but do need unfortunately.
Edit: wondering if anyone has had any luck fastboot flashing the factory image? I know it's a pain in the ass to have to back up all your files, etc off the device so I'd like to know if anyone has had success or even tried this. Cuz, I really won't feel satisfied until I've resorted to this last measure if there's the possibility of eradicating the problem.
Click to expand...
Click to collapse
I initially had this problem when I switched to lollipop, not sure how it fixed itself but I'm guessing it's the contacts sync like you posted here; only the first time I accidentally synced Fb contacts, and due to the massive number of friends on it, it crashed. But you can disable any sort of sync services on Fb and continue using the app for everything else, I've had no issues since.
Do you mean luck with fixing this issue after flashing the factory image or only returning to stock? Because I've had no issues returning to stock from lollipop by flashing the factory images through fastboot.
Aditya Srinidhi said:
I initially had this problem when I switched to lollipop, not sure how it fixed itself but I'm guessing it's the contacts sync like you posted here; only the first time I accidentally synced Fb contacts, and due to the massive number of friends on it, it crashed. But you can disable any sort of sync services on Fb and continue using the app for everything else, I've had no issues since.
Do you mean luck with fixing this issue after flashing the factory image or only returning to stock? Because I've had no issues returning to stock from lollipop by flashing the factory images through fastboot.
Click to expand...
Click to collapse
I meant with flashing the factory image via fastboot to stop the frustratingly obnoxious pop ups of the process stopping (w/o uninstalling FB). You answered my question.
So, get this... Resolved the error by uninstalling Facebook. Today I picked up a Moto 360 and you HAVE to install Motorola Connect to really personalize the device... Once I allowed it to see my Google+ account info the android.process.acore started again. I'm SO annoyed. Gonna try a factory reset again and see if that helps. The only way to stop it is to uninstall Motorola Connect and that really sucks cuz I want to (of course) mess with my watch. I know nothing of Android Wear yet or how to root, etc the 360 so.... Here I go. Boldly. Lol
I'm just curious why I haven't seen more people having this issue. It's been plaguing me now for almost 2 weeks. I'm ready to throw my Bamboo OPO out the effing window. WTF.
t3chn0s1s said:
I meant with flashing the factory image via fastboot to stop the frustratingly obnoxious pop ups of the process stopping (w/o uninstalling FB). You answered my question.
So, get this... Resolved the error by uninstalling Facebook. Today I picked up a Moto 360 and you HAVE to install Motorola Connect to really personalize the device... Once I allowed it to see my Google+ account info the android.process.acore started again. I'm SO annoyed. Gonna try a factory reset again and see if that helps. The only way to stop it is to uninstall Motorola Connect and that really sucks cuz I want to (of course) mess with my watch. I know nothing of Android Wear yet or how to root, etc the 360 so.... Here I go. Boldly. Lol
I'm just curious why I haven't seen more people having this issue. It's been plaguing me now for almost 2 weeks. I'm ready to throw my Bamboo OPO out the effing window. WTF.
Click to expand...
Click to collapse
It's mostly not because of lollipop, but might be the app itself, I read a few others having this problem on other forums with HTC, the solution they found was to clear data on contacts storage. Give that a try and see if it works, if not I'd suggest going back to Stock or probably the new OxygenOS which is supposed to be out by now. Check out @timmaaa index thread in the general section, it has all the necessary stock images you need. Report back and let us know if it fixed the issue for you
Aditya Srinidhi said:
It's mostly not because of lollipop, but might be the app itself, I read a few others having this problem on other forums with HTC, the solution they found was to clear data on contacts storage. Give that a try and see if it works, if not I'd suggest going back to Stock or probably the new OxygenOS which is supposed to be out by now. Check out @timmaaa index thread in the general section, it has all the necessary stock images you need. Report back and let us know if it fixed the issue for you
Click to expand...
Click to collapse
Yea, I tried clearing contacts storage numerous times to no avail. I can live without the app... At first I thought it was a requirement to change watch faces... But, I do have a backup of stock, rooted but I can't go back to KK after being so used to LP. I'm def going to jump on Oxygen just to try it out but I'm guessing I'll end up running stock CM12s. I can't wait. I'd much rather have a stock (w/root of course) or mostly stock device that actually works completely.
t3chn0s1s said:
Yea, I tried clearing contacts storage numerous times to no avail. I can live without the app... At first I thought it was a requirement to change watch faces... But, I do have a backup of stock, rooted but I can't go back to KK after being so used to LP. I'm def going to jump on Oxygen just to try it out but I'm guessing I'll end up running stock CM12s. I can't wait. I'd much rather have a stock (w/root of course) or mostly stock device that actually works completely.
Click to expand...
Click to collapse
The bug has been corrected by Google themselves with Android 5.1. Finally!.. So, like me, just try omni 5.1 or last cm12.1 unofficial and the error has gone! So good to use my phone.... Hmmm... How to say... Normally... Lol.
flolep said:
The bug has been corrected by Google themselves with Android 5.1. Finally!.. So, like me, just try omni 5.1 or last cm12.1 unofficial and the error has gone! So good to use my phone.... Hmmm... How to say... Normally... Lol.
Click to expand...
Click to collapse
Very nice. Glad to hear this... Xposed isn't compatible with 5.1 yet, right?
Two things to try…
Go into settings/apps , press the menu button and select "reset app preferences". Reboot
You Can also try entering the following in your commands:
Su (enter)
Killall rild (enter)
reboot
Should have read the entire post, glad that has been fixed by google, I experienced the same thing and it's a huge pain in the butt.
t3chn0s1s said:
Very nice. Glad to hear this... Xposed isn't compatible with 5.1 yet, right?
Click to expand...
Click to collapse
No. Not yet. But. Well. CM12 is already good functionality wise. And with this bug disappeared it's really a happiness.
---------- Post added at 12:42 AM ---------- Previous post was at 12:39 AM ----------
tmjm28 said:
Two things to try…
Go into settings/apps , press the menu button and select "reset app preferences". Reboot
You Can also try entering the following in your commands:
Su (enter)
Killall rild (enter)
reboot
Should have read the entire post, glad that has been fixed by google, I experienced the same thing and it's a huge pain in the butt.
Click to expand...
Click to collapse
Yeah, yeah. Already tried... Lol. I think I tried every single advice given in all the Android forums of the world on this bug lol. Well. Google finally heard us. +++
tmjm28 said:
Two things to try…
Go into settings/apps , press the menu button and select "reset app preferences". Reboot
You Can also try entering the following in your commands:
Su (enter)
Killall rild (enter)
reboot
Should have read the entire post, glad that has been fixed by google, I experienced the same thing and it's a huge pain in the butt.
Click to expand...
Click to collapse
Neither worked but thanks for the suggestion. I did find a Facebook work around. Found the Lite Version via a Google search (since its technically not available in the US) , installed it and it works fine. No android.process.acore FC's or repeated pop ups.
Update: This problem reared its ugly head again on CM12 and I ended up having to uninstall Twitter this time. So, now I'm on CM12s and as soon as I logged into my other Google account user Boxers email app I got the android.process.acore crash again. Uninstalling that app immediately stopped it. God I can't wait for 12.1 for our OPOs. This problem is absolutely ridiculous. I can't take this anymore. I really can't use ANY social media apps unless its like Tinfoil for FB or Twitter. I don't have any connected accounts except Google & Cyanogen.. Which I truly can live without but... Just for the hell of it.... Knowing I have a backup and I'm about to clean flash the latest stock build I tried to add Waze and it caused the crash all over again. Uninstalling Waze didn't help. I shouldn't have to deal with this. Only way to stop it is to disable contacts storage. Once it begins it doesn't stop. Effing Google with their half baked crap.

[Q] Ongoing issue with "Chrome is not responding"

Firstly I want to apologize if there's a thread on this. I tried searching and didn't find anything. Google fails me as well.
For a few months now, Chrome has been driving me insane on my stock nordic Z3 (5.0.2 with the .690 firmware). I also have the most recent version of Chrome installed.
Every single time I open the app, it works for about 2 seconds, then completely freezes for around 15 seconds after which a message pops up stating "Chrome is not responding. Would you like to close it?" If I press "OK", it obviously closes the app and the problem appears again when I restart it. If I choose "wait", Chrome works just fine until the next time I open it. EDIT: The freezing problem started happening three times in a row a few days ago.
This happens every single time I open the app, whether launching it or opening it from the recent apps menu.
I'm pretty certain the problem has been around since the v39 build of Chrome, as 38 worked just fine. I have tried everything I can think of to fix it. Uninstalled updates and re-updated it, updating to lollipo didn't help, I also did a completely fresh install today (repairing via Sony Bridge for Mac) and it didn't help either. And apparently I can't go back to v38 anymore since lollipop doesn't seem to support it.
I would really want to use Chrome, as I've gotten used to it and enjoyed it quite a lot. I'd really appreciate the help.
Try clearing the data in settings - apps - chrome
gregbradley said:
Try clearing the data in settings - apps - chrome
Click to expand...
Click to collapse
I have done this too. Also, the problem persists even with completely fresh installs of Chrome.
Remove your google account, restart the phone and restore your google account
gregbradley said:
Remove your google account, restart the phone and restore your google account
Click to expand...
Click to collapse
Tried it, sad to say it didn't work either. Interestingly it now does the same 15 second freeze, but without the error message in the end. Curious indeed.
EDIT: Got the error message again.
Does this happen on Wifi or on data?
If on wifi is always the same router?
gregbradley said:
Does this happen on Wifi or on data?
If on wifi is always the same router?
Click to expand...
Click to collapse
I Use data 90% of the time, and various routers when on wifi. The problem occurs in all circumstances.
Are you rooted? Unlocked bootloader?
You say you are on the Nordic version of .690, is that the original region for the device you bought and the area you reside in?
Can you revert back to KK by flashing a FTF for your device and region and try V38 again to see if that works still.
gregbradley said:
Are you rooted? Unlocked bootloader?
You say you are on the Nordic version of .690, is that the original region for the device you bought and the area you reside in?
Can you revert back to KK by flashing a FTF for your device and region and try V38 again to see if that works still.
Click to expand...
Click to collapse
I have a completely untouched device. So no root, locked bootloader and it's always been that way. Thus Nordic is the original region of my device.
I'd rather not flash back to kitkat, but I can tell you that I tried reverting back to v38 before updating to lollipop and it worked normally without the freezing issue.
This is my version of chrome on Lollipop. Can you update to this? I am also not rooted so you should be able to update to this
gregbradley said:
This is my version of chrome on Lollipop. Can you update to this? I am also not rooted so you should be able to update to this
Click to expand...
Click to collapse
I have the same version of chrome as you. The problem has persisted during every single update after v38.
ok without logs I can go no further with this. Is there any chance you can pull some logs off your device?
gregbradley said:
ok without logs I can go no further with this. Is there any chance you can pull some logs off your device?
Click to expand...
Click to collapse
How do I do that?
install a logCat app from the playstore
gregbradley said:
install a logCat app from the playstore
Click to expand...
Click to collapse
Does this require root? One of the apps I tried is requiring it and the other one isn't doing much either. Should I be doing something to make it work?
isshoni said:
I would really want to use Chrome, as I've gotten used to it and enjoyed it quite a lot. I'd really appreciate the help.
Click to expand...
Click to collapse
Maybe try the beta version of chrome in case it's a bug which has been fixed but not yet rolled out to chrome. Perhaps try this first as it'll be quicker!
Perhaps it's some data associated with chrome that's getting pulled down after each restore. Perhaps you can try, on a desktop pc, backing up your bookmarks and then deleting them, and clearing chrome's data on your phone, then trying again? And if that doesn't work try getting rid of extensions (not that I think they should be pulling them down as chrome for android doesn't yet support them, although I'm sure I read years ago that one day they would). And anything else associated with your chrome account.
Another one, perhaps quicker (not sure) would be to see if you can associate your phone with a new google account with no previous chrome use and see if it goes wrong with that one. It would help to rule out account-related problems.
Another possibility is that it's not chrome causing the problem but something it relies on; google play services, for example. Perhaps clear data on any apps chrome could conceivably use.
I'm happy to report that my problem is now solved, though still a giant mystery.
My upper speaker broke and I had to get it replace under warranty. I got insanely lucky as they replaced both front and backside glass pieces, the frame, the screen module itself and of course the speakers. So I've now got a brand-new looking phone So happy.
Anyway, I complained about the software being a mess so they also did a complete reinstall and after that Chrome works absolutely perfectly. As magically does everything else too. Not yet a sign of lollipop's previous lagging and rebooting.
It still bugs me, however, that why would Chrome suddenly start having this unreasonable issue. I had tried everything suggested in this thread and nothing worked. My own clean install didn't work. I'm really quite bothered by this.

Videos and sound stops working

I have a rooted S6 international version with magisk and with OdexLite ROM and sometimes I can't play videos,anywhere,youtube,facebook,instagram,stories from snapchat,etc.Oh,and another problem is the sound just cuts off,like I can't hear a notification or anything and I can't play songs,it's says "Failed to play track" .If I restart my phone it solves the problem,but just for some hours and i don't want to do this 4 times a day.It is the ROM problem or it's a root problem?
Daryuszs said:
I have a rooted S6 international version with magisk and with OdexLite ROM and sometimes I can't play videos,anywhere,youtube,facebook,instagram,stories from snapchat,etc.Oh,and another problem is the sound just cuts off,like I can't hear a notification or anything and I can't play songs,it's says "Failed to play track" .If I restart my phone it solves the problem,but just for some hours and i don't want to do this 4 times a day.It is the ROM problem or it's a root problem?
Click to expand...
Click to collapse
Have to tried clearing dalvik and cache in TWRP?
sofir786 said:
Have to tried clearing dalvik and cache in TWRP?
Click to expand...
Click to collapse
Yea,but no luck
Daryuszs said:
Yea,but no luck
Click to expand...
Click to collapse
Only thing else I can think of is to clean flash that Rom, I'm on it and have no issues
Oh wow, finally with the same problem as mine, but really didn't notice about the video problem, but I surely have it sometimes. See my thread here:
https://forum.xda-developers.com/galaxy-s6/help/problem-sound-output-t3617534
Try uninstalling Facebook Messenger for some time and check if the problems persist, that's my case and most probably yours too.
G920Fuser said:
Oh wow, finally with the same problem as mine, but really didn't notice about the video problem, but I surely have it sometimes. See my thread here:
https://forum.xda-developers.com/galaxy-s6/help/problem-sound-output-t3617534
Try uninstalling Facebook Messenger for some time and check if the problems persist, that's my case and most probably yours too.
Click to expand...
Click to collapse
I'll try,never thought about that.I'll come back with the results
How'd it go?
I'm trying to check if there's a setting forcing this bug, but I think it's something inside the app that's causing it, unfortunately.
G920Fuser said:
How'd it go?
I'm trying to check if there's a setting forcing this bug, but I think it's something inside the app that's causing it, unfortunately.
Click to expand...
Click to collapse
I'm surprised that solved the problem,I installed messenger lite and it's all good,but I don't want to keep it forever.I'll install the original messenger again and see what I can do.
You tried blocking all the notifications from messenger?
Daryuszs said:
I'm surprised that solved the problem,I installed messenger lite and it's all good,but I don't want to keep it forever.I'll install the original messenger again and see what I can do.
You tried blocking all the notifications from messenger?
Click to expand...
Click to collapse
I too am using Messenger Lite. I have not turned off notifications because that will disable a very important feature of the app , but other than that, I have tried everything and there isn't a single setting that is causing the problem and only the Messenger team can fix it since it's inside the app.
If we send more emails to them, they'll maybe consider fixing it.

App drawer search takes forever to load and for the keyboard to show up. Frustrated!

Thankful to the person who posted it on Reddit (But no good responses yet). Hopefully through this platform we can get some help.
So I don't know if this is bothering anyone else, but the app drawer search takes forever to load and for the keyboard to show up - by that I mean 5 seconds or so, but it's still crazy when the nova search is instant. Is anyone else having the same problem?
PS: Even with the new TouchWiz update, issue still exists.
Please Help.
Singh Saluja said:
Thankful to the person who posted it on Reditt (But no good responses yet). Hopefully through this platform we can get some help.
So I don't know if this is bothering anyone else, but the app drawer search takes forever to load and for the keyboard to show up - by that I mean 5 seconds or so, but it's still crazy when the nova search is instant. Is anyone else having the same problem?
Please Help.
Click to expand...
Click to collapse
Haven't encountered that on my T-Mobile variant. Per chance did you restore any or all data from another phone.
ggrant3876 said:
Haven't encountered that on my T-Mobile variant. Per chance did you restore any or all data from another phone.
Click to expand...
Click to collapse
Hi I also have the T-Mobile variant no root absolutely stock but yes I did restored my pictures from last iOS(iPhone 6s) do you think that might be an issue.
Should I restore the device again to factory settings?
Singh Saluja said:
Hi I also have the T-Mobile variant no root absolutely stock but yes I did restored my pictures from last iOS(iPhone 6s) do you think that might be an issue.
Should I restore the device again to factory settings?
Click to expand...
Click to collapse
Not sure just pictures would cause this but you might try a factory data reset. I'd wait a bit and see if you get anymore suggestions first.

Categories

Resources