Related
I am experiencing very erratic behavior with my call recording feature on my Touch Pro. I have tried many different roms, and even a few different radios. What happens is sometimes it records the other party very clearly for the entire call. Other times during the call the other party goes back and forth from sounding choppy to clear. For the life of me I cannot figure out what is going on. I've read others who use the GSM version of this phone who were plagued by this problem claim that it goes away with their new official rom upgrade, but of course, that won't work since I'm CDMA, on USCC. Another thing is I've not seen anyone report the recording being back and forth from choppy/stuttering/distorted to clear. So ... I wonder how many others have had this same experience I am having. I suspect this could be related to something very low level if since I tried different ROMs and that didn't solve it and others have reported this being fixed with an OFFICIAL ROM upgrade, which upgrades the radio, OS, ect., everything, then maybe there is no setting I can change to fix this? If anyone has any suggestions or direct solutions I would be very eager to try them. I know this is a very esoteric issue and probably won't get many responses however.
I have included a zip file of a recording I did which demonstrates the issue I've been experiencing. For anyone brave enough to really try to offer me a suggestion or solution, thank you!
Peter
Still no ideas? I've flashed MULTIPLE ROMS and nothing seems to fix this, yet others have seemed to fix this by ROM flashing.. what is the CAUSE of this issue????
Hi guys,
I'm new to this forum but I have read all rules before posting. I hope I got everything right. If not, please let me know and I'll make changes ASAP.
I have installed Paranoid Android 3.68 last week and have been experiencing this problem (couldn't post it in that thread because I am still a newbie).
My phone crashes into Safe Mode at least once daily without me doing anything. Every time I reboot to normal mode, I would have to restore my 3D Background, Swiftkey, and NiLS apps. So I'm guessing that the crash happened due to (one of) these apps. Could this be an incompatibility issue? Is there any way I can prevent this from happening because it gets quite troublesome to restore these apps so often...
Thanks a lot!
mycxmei said:
Hi guys,
I'm new to this forum but I have read all rules before posting. I hope I got everything right. If not, please let me know and I'll make changes ASAP.
I have installed Paranoid Android 3.68 last week and have been experiencing this problem (couldn't post it in that thread because I am still a newbie).
My phone crashes into Safe Mode at least once daily without me doing anything. Every time I reboot to normal mode, I would have to restore my 3D Background, Swiftkey, and NiLS apps. So I'm guessing that the crash happened due to (one of) these apps. Could this be an incompatibility issue? Is there any way I can prevent this from happening because it gets quite troublesome to restore these apps so often...
Thanks a lot!
Click to expand...
Click to collapse
Hi there;
Try removing one app at a time and observe and good luck
I have been having a persisting force close issue that I initially thought was linked to Greenify. "Unfortunately, Context Service has stopped" after every call I made or received, and upon booting the phone. Trial and error have caused me to find the only thing that allows me to run Xposed without any issue is having 7 or less modules enabled. I can switch between modules. For instance, I had Xposed Torch enabled and things were fine with 7 modules. I installed Xtoast, rebooted, and instant error/FC. Repeats no matter how many times I reboot. I uninstall Xposed Torch, which was just working perfectly fine, and leave XToast installed. Reboot and no error. Rebooted over and over to ensure, no error. Switched a few modules around to ensure, and it seems to not matter what modules I have installed. I have no issues whatsoever running Xposed as long as I only have seven modules installed, but if I go to install an 8th, no matter what it is, I immediately get Context Service force closes. I have not found anything on here about a definitive amount of modules you can install, so I can only hope someone has a clue what could be going on. Normally I'd look to the Logcat, but it doesn't seem to be a specific module causing this. I'd really appreciate any help any of you might have. Xposed has a lot more to offer for me than you can cram in seven modules.
Logcat? The Xposed log may not show you anything but an unfiltered logcat will.
GermainZ said:
Logcat? The Xposed log may not show you anything but an unfiltered logcat will.
Click to expand...
Click to collapse
You mean the full logcat I create through adb? If so, do i need to produce the issue while the phone is one and then take the logcat? Phone has been rebooted since the last time i got the FC, just don't want to waste time learning to upload and uploading a logcat now while phone is working if I need to re-create the problem first in order for it to be useful. Definitely will take the time to upload a logcat because I would really like to fix this issue, I just wanna make sure I do it correctly.
wrongway213 said:
You mean the full logcat I create through adb? If so, do i need to produce the issue while the phone is one and then take the logcat? Phone has been rebooted since the last time i got the FC, just don't want to waste time learning to upload and uploading a logcat now while phone is working if I need to re-create the problem first in order for it to be useful. Definitely will take the time to upload a logcat because I would really like to fix this issue, I just wanna make sure I do it correctly.
Click to expand...
Click to collapse
Enable 7+ modules so that the issue will be reproduced on next boot.
Reboot and start the logcat while the device is booting.
Wait till you see the FC and stop the logcat.
Upload the logcat.
Thanks for your reply. I just figured out the problem, thankfully.. I was preparing to do what you said, and I for some reason thought to reinstall Busybox before installing an eighth module and rebooting. My Busybox install must have been faulty. After reinstalling it said I had just reinstalled the same version as previously installed, but now I am back to nine modules and no problems.
scratch that, problem keeps getting weirder. Installed Wanam Xposed again and the issue came right back, uninstalled and the issue came back until I went back down to 7 modules and now no issue. I'm so confused..
wrongway213 said:
scratch that, problem keeps getting weirder. Installed Wanam Xposed again and the issue came right back, uninstalled and the issue came back until I went back down to 7 modules and now no issue. I'm so confused..
Click to expand...
Click to collapse
Honestly can't say anything without a logcat, please grab one.
You should also be able to use an app to do it (e.g. CatLog) since your device is booting. Just start the app as soon as your device boots.
GermainZ said:
Honestly can't say anything without a logcat, please grab one.
You should also be able to use an app to do it (e.g. CatLog) since your device is booting. Just start the app as soon as your device boots.
Click to expand...
Click to collapse
FC is not currently happening, but I just downloaded Catlog and I am still getting a lot of errors in my logcat.. makes me curious as to whether my issue can be pinpointed without messing things up yet again. I attached my logcat filtered for "error", if you are able to discern anything from it, please do let me know what you find. If not I'll be sure to load Catlog at boot and grab one if the error does occur again. Thank you for recommending Catlog, by the way, SO much easier for a new guy like me than terminal emulator/ADB.
Edit: I see you mentioned an unfiltered logcat earlier, but honestly I do not know what I am doing with logcats at all, and as the error is not occuring right now I thought it might be a little unnecessary to look through a million lines of text.. I figure this is short enough that if something sticks out I can fix it, if not I can run Catlog again if the problem persists.
F/C All devices
All of my androids device using Xpose are force closing, well apps that are associated with it. Only fix I could find is older download..it seems the update had issues..
wrongway213 said:
FC is not currently happening, but I just downloaded Catlog and I am still getting a lot of errors in my logcat.. makes me curious as to whether my issue can be pinpointed without messing things up yet again. I attached my logcat filtered for "error", if you are able to discern anything from it, please do let me know what you find. If not I'll be sure to load Catlog at boot and grab one if the error does occur again. Thank you for recommending Catlog, by the way, SO much easier for a new guy like me than terminal emulator/ADB.
Edit: I see you mentioned an unfiltered logcat earlier, but honestly I do not know what I am doing with logcats at all, and as the error is not occuring right now I thought it might be a little unnecessary to look through a million lines of text.. I figure this is short enough that if something sticks out I can fix it, if not I can run Catlog again if the problem persists.
Click to expand...
Click to collapse
I'm asking for an unfiltered logcat because not all useful lines will contain "error". Filtering for " AndroidRuntime" is usually enough, but it's safer to just upload the whole thing.
Anyway, please upload one when you can reproduce the issue. I see some errors related to secure storage in your log but I don't think that's related to anything.
jon3640 said:
All of my androids device using Xpose are force closing, well apps that are associated with it. Only fix I could find is older download..it seems the update had issues..
Click to expand...
Click to collapse
Well, if it is a problem with the framework, it won't be fixed unless you help out by posting a logcat.
GermainZ said:
I'm asking for an unfiltered logcat because not all useful lines will contain "error". Filtering for " AndroidRuntime" is usually enough, but it's safer to just upload the whole thing.
Anyway, please upload one when you can reproduce the issue. I see some errors related to secure storage in your log but I don't think that's related to anything.
Well, if it is a problem with the framework, it won't be fixed unless you help out by posting a logcat.
Click to expand...
Click to collapse
problem came back again for no reason, only 6 mods enabled and all have been stable for days... restart phone because i was getting a crazy mms wakelock in bbs. here's the logcat with the "unfortunately, context service has stopped" both from just automatically happening and i triggered it by having my girlfriend call me. i then disabled xposed, restarted and no problems, so i took a logcat of that to show how my phone runs normally in case you need it. let me know if you do and i will upload that as well.. if you can find anything in here i will greatly appreciate it. i can't even use xposed at this point, i'm worried i'm either damaging my phone or possibly missing calls/texts/notifications. thanks for your time in advance.
It's an ANR (Application Not Responding) error, so I'm guessing your phone kinda hangs for a bit before showing you the dialog?
It doesn't seem to be related to Xposed at all, though. It's Samsung's "Context service" (com.samsung.android.providers.context), so I'd personally try checking for a system update before anything else. You're likely to get more help in the S5 section (since the problem isn't related to Xposed), through it looks like no one else has this problem.
It hangs for a second, but those errors don't stop things I can see, just errors. I have to admit, I don't quite understand, if it's not related to Xposed, why would it only happen with certain modules enabled? That's why I assumed it was xpoaed related to begin with. Do I need to Odin back to stock? I don't want to damage my phone but I don't know anything about that error or if it could he damaging.. Sorry for the text wall. Thanks for being so helpful.
Sent from my SM-G900V using XDA Free mobile app
wrongway213 said:
It hangs for a second, but those errors don't stop things I can see, just errors. I have to admit, I don't quite understand, if it's not related to Xposed, why would it only happen with certain modules enabled?
Click to expand...
Click to collapse
Coincidence, I'd say. You'd probably get the same thing without Xposed, but as you've noticed it seems to happen semi-randomly, so chances are you weren't "lucky" enough.
wrongway213 said:
Do I need to Odin back to stock?
Click to expand...
Click to collapse
If you're using a custom ROM, you could also report this problem to the ROM dev with the logcat and ask him if his base is up to date or if there's anything he can do about it.
wrongway213 said:
I don't want to damage my phone but I don't know anything about that error or if it could he damaging..
Click to expand...
Click to collapse
It's mostly just annoying, there should be no permanent damage of any kind.
GermainZ said:
Coincidence, I'd say. You'd probably get the same thing without Xposed, but as you've noticed it seems to happen semi-randomly, so chances are you weren't "lucky" enough.
If you're using a custom ROM, you could also report this problem to the ROM dev with the logcat and ask him if his base is up to date or if there's anything he can do about it.
It's mostly just annoying, there should be no permanent damage of any kind.
Click to expand...
Click to collapse
could it be related to s health? i know this isn't the s5 forum, but i see under app info on s health there is a "com.samsung.android.providers.context.permission.WRITE_USE_APP_FEATURE_SURVEY".. i have heard people talk about having issues with s health and xposed. could that permission be the context service error i am getting, based on what you have seen in my logcat?
wrongway213 said:
could it be related to s health? i know this isn't the s5 forum, but i see under app info on s health there is a "com.samsung.android.providers.context.permission.WRITE_USE_APP_FEATURE_SURVEY".. i have heard people talk about having issues with s health and xposed. could that permission be the context service error i am getting, based on what you have seen in my logcat?
Click to expand...
Click to collapse
I didn't see anything related to S Health, but it might've related to the secure storage (though I'm not sure if that's a stock Samsung thing or if it's activated by the user).
I've tried browsing the forums, and even locating the post talking about the fix for the camera, and I simply can't find it. I really don't want to go without a phone seeing as my job requires my phone, but it really sucks not having a camera or a flashlight toggle.
I've seen some people that have indicated its a physical issue, however, it sporadically starts working again. Note: I would like to avoid doing the super data wipe as I'm also having computer issues at the same time. If someone needs me to post a catalog, I will need help Learning what to filter out in order to upload only the necessary info.
I've tried wiping the data through twrp advanced wipe, and of course the dalvik cache has been wiped many-a-time. Any help would be appreciated!
Um...I don't think you even explain you problem. Might want to elaborate a bit.
Sent from my Nexus 6 using XDA Free mobile app
No matter what ROM I use, no matter what camera I try to install, I cannot get it to consistently work. More often than not, cannot connect to camera. I feel like its a setting or file sticking on the "SD card" that is interfering. I also cannot use the flashlight toggle, and parts of Google+ and gallery crash at times. This has been intermittently occurring since my first flash. Blissful ROM v1.7 twrp 2.8.4.0
Tried every wipe except for the one that makes me type yes. I've already flashed boot.IMG to disable decryption, and I'm starting to think that may have something to do with it.
I was under the impression I had twrp 2.8.4.0, but after double checking, it looks like it was stuck on 2.8.2.1. I flashed the newer version from twrp manager, and now my camera is working. I didn't do anything other than install the new recovery. And yes I've tried rebooting my phone in the past. This may be a temporary fix, but I'll report back tomorrow on whether it is still working. This is very odd.
Andddddddd it stopped working again. Super legit.
Might be similar to my issue.
My camera started only showing front facing..even the option for back facing wasn't there. Did wipes in recovery and app settings. Would work, it seemed, but would revert right back to not working. At one point the camera app wasn't appearing in the app drawer at all even though it was shown in "all apps".
This occurred on stock and custom ROMs. I was advised to try flashing factory IMG but I'm well within the warranty period ( phone less than 2weeks) so I'm locking it back up and have a replacement on the way from ATT...
* I also noticed the issue starting while I was on bliss ROM 1.7
Sent from my Nexus 6 using XDA Free mobile app
My camera is really shaky and won't focus correctly in landscape mode. I returned the first phone I had for basically the same thing because it wasn't focusing in portrait mode but looked fine in landscape. I haven't seen anyone else have this issue. At first I thought the camera was inconsistent but if you zoom in you can see that it doesn't focus properly.
I'm starting to wonder why there are so many people experiencing the same or similar camera issues. The only reason I'm starting to think that it is software based and not entirely hardware based is because I was having this same issue (cannot connect to camera) on my sgs5 with cm based Roms.
I'm not saying any of this makes sense, its just strange. I wish we could help troubleshoot what the root of this problem is instead of just RMAing the device. I'm afraid to RMA with T-Mobile.
you better do it before its too late. id rma it.
cellularticulate said:
No matter what ROM I use, no matter what camera I try to install, I cannot get it to consistently work. More often than not, cannot connect to camera. I feel like its a setting or file sticking on the "SD card" that is interfering. I also cannot use the flashlight toggle, and parts of Google+ and gallery crash at times. This has been intermittently occurring since my first flash. Blissful ROM v1.7 twrp 2.8.4.0
Tried every wipe except for the one that makes me type yes. I've already flashed boot.IMG to disable decryption, and I'm starting to think that may have something to do with it.
I was under the impression I had twrp 2.8.4.0, but after double checking, it looks like it was stuck on 2.8.2.1. I flashed the newer version from twrp manager, and now my camera is working. I didn't do anything other than install the new recovery. And yes I've tried rebooting my phone in the past. This may be a temporary fix, but I'll report back tomorrow on whether it is still working. This is very odd.
Click to expand...
Click to collapse
There is no sdcard.
Try going back to factory sysimage, and data wipe.
Are you using any "added in" camera software? If so, what?
cellularticulate said:
I'm starting to wonder why there are so many people experiencing the same or similar camera issues. The only reason I'm starting to think that it is software based and not entirely hardware based is because I was having this same issue (cannot connect to camera) on my sgs5 with cm based Roms.
I'm not saying any of this makes sense, its just strange. I wish we could help troubleshoot what the root of this problem is instead of just RMAing the device. I'm afraid to RMA with T-Mobile.
Click to expand...
Click to collapse
Similar issue. Get errors "Unfortunately, camera has stopped" or "cannot connect to camera." I picked up the phone right before a 2 week vacation so unfortunately I can't bring back to AT&T. Hopefully Moto plays nice. Problems originally occurred on stock 5.0 before the 5.0.1 update. Since AT&T was lagging on OTA, I flashed to the official BlissPop rom but I have the same problems. Sometimes it'll work like it's supposed to for a couple days but always reverts back to the errors. Nothing like being at the top of a mountain in Hawaii and "cannot connect to camera" right????Since I've read about this happening on so many different firmware variations, I have to believe it's a hardware issue.
I have only had issues with the stock camera app. Ive been running Pure Shamu for 2.5 weeks now and only using the Google Camera app from the play store (the one with HDR+ and the icon has the lens filled with rainbow colors) with absolutely no issues and only getting excellent quality pictures.
Had the issue where the camera wouldn't focus and everything on the screen gets jiggly and wavy like there's some sort of interference. I had motion sickness looking at the screen. Called Moto for an advance replacement and after a week of delay due to stock issue...somehow they were kind enough to upgrade me to a CW 64gb model. I hope it's new and no more camera issues.
Has everyone who got the 'no-focuse OIS' issue gotten new phone on RMA?
I took mine to repair few days ago and they said that they won't give me a new phone instantly, rather they try to fix the OIS. Not sure how that is going to work..?
They also suggested that this issue might be "self inflicted" or just an "feature" of the camera itself. fml.
Giants2010 said:
Similar issue. Get errors "Unfortunately, camera has stopped" or "cannot connect to camera." I picked up the phone right before a 2 week vacation so unfortunately I can't bring back to AT&T. Hopefully Moto plays nice. Problems originally occurred on stock 5.0 before the 5.0.1 update. Since AT&T was lagging on OTA, I flashed to the official BlissPop rom but I have the same problems. Sometimes it'll work like it's supposed to for a couple days but always reverts back to the errors. Nothing like being at the top of a mountain in Hawaii and "cannot connect to camera" right????Since I've read about this happening on so many different firmware variations, I have to believe it's a hardware issue.
Click to expand...
Click to collapse
I returned mine to stock, unroot/locked boot loader, factory reset, before shipping it off and the camera issue was still there. Maybe hardware related I'm thinking.
Sent from my Nexus 6 using XDA Free mobile app
Something rather peculiar Ive noticed...
I didn't really pinpoint this until today, but the camera very consistently starts working when you go into fastboot, load the recovery, and then boot into system. I'm really, sincerely not quite sure why this would be happening, but I still feel like it has something to do with boot.IMG
If any devs can point me in the right direction to try and track down the possibility of this being an issue, I'd love to potentially fix a bunch of people's camera issues (albeit there is probably also a hardware defect direct from moto).
Is logcat going to pick up on issues that originate from boot?
cellularticulate said:
I've tried browsing the forums, and even locating the post talking about the fix for the camera, and I simply can't find it. I really don't want to go without a phone seeing as my job requires my phone, but it really sucks not having a camera or a flashlight toggle.
I've seen some people that have indicated its a physical issue, however, it sporadically starts working again. Note: I would like to avoid doing the super data wipe as I'm also having computer issues at the same time. If someone needs me to post a catalog, I will need help Learning what to filter out in order to upload only the necessary info.
I've tried wiping the data through twrp advanced wipe, and of course the dalvik cache has been wiped many-a-time. Any help would be appreciated!
Click to expand...
Click to collapse
This is a hardware issue. Check http://forum.xda-developers.com/nexus-6/help/camera-lens-movement-t2984298
rdizzle707 said:
This is a hardware issue. Check http://forum.xda-developers.com/nexus-6/help/camera-lens-movement-t2984298
Click to expand...
Click to collapse
Not the issue I'm explaining though. This is a bit more deeply seeded of an issue. When I boot directly into the ROM, my twrp installer says I'm back on 2.8.2.1, but when I boot into fastboot and then twrp, and then ROM, it says 2.8.4.0 and my camera works. This is legitimately weird as ****.
cellularticulate said:
Not the issue I'm explaining though. This is a bit more deeply seeded of an issue. When I boot directly into the ROM, my twrp installer says I'm back on 2.8.2.1, but when I boot into fastboot and then twrp, and then ROM, it says 2.8.4.0 and my camera works. This is legitimately weird as ****.
Click to expand...
Click to collapse
Ohhh man that is weird.
rdizzle707 said:
This is a hardware issue. Check http://forum.xda-developers.com/nexus-6/help/camera-lens-movement-t2984298
Click to expand...
Click to collapse
rdizzle707 said:
Ohhh man that is weird.
Click to expand...
Click to collapse
It appears a bit more stable now. I tried flashing twrp from my computer and it seems to be a bit more nice. That and normal reboot to twrp doesn't say 2.8.2.1 - let me check twrp manager now.
And my camera and flashlight have worked for almost three days now. Dafuq.
Same issue. "Unfortunately, Camera has stopped."
No flash light available, only front camera working, clicking on HDR exits the app with the aforementioned error message.
Has anyone solved this issue?
I was on 5.1 stock (with root) and now I've updated to 5.1.1, but with no change to the Camera behaviour.
Hey everyone,
I have had multiple updates for Lineage on my Mix and still the issue remains. As mentioned in the title, the camera does not record video. It takes pictures just fine and when attempting to record video it looks to be recording, but when played back it's just the first frame and audio. I have tried multiple camera applications and none of them have helped.
It almost feels like an issue not with lineage itself, but the kernel on my device perhaps? I should mention this too, when i'm recording video through facebook messenger it works just fine, but only then. I can watch videos people sent to me just fine as well, so i don't believe playback is the issue.
Is anyone else having this issue with lineageOS on their Mix?
If anyone knows a way to fix this please tell me, its been bothering me forever. Thanks!
xstewminator said:
Hey everyone,
I have had multiple updates for Lineage on my Mix and still the issue remains. As mentioned in the title, the camera does not record video. It takes pictures just fine and when attempting to record video it looks to be recording, but when played back it's just the first frame and audio. I have tried multiple camera applications and none of them have helped.
It almost feels like an issue not with lineage itself, but the kernel on my device perhaps? I should mention this too, when i'm recording video through facebook messenger it works just fine, but only then. I can watch videos people sent to me just fine as well, so i don't believe playback is the issue.
Is anyone else having this issue with lineageOS on their Mix?
If anyone knows a way to fix this please tell me, its been bothering me forever. Thanks!
Click to expand...
Click to collapse
Can only guess at flashing 7.7.20 firmware from TWRP
jazz452 said:
Can only guess at flashing 7.7.20 firmware from TWRP
Click to expand...
Click to collapse
I'm sorry to sound dumb, but where would I be able to see my current firmware? Im guessing in about phone, but I'm not seeing it.
Thanks for your help, and I will try to flash that if I can.
xstewminator said:
I'm sorry to sound dumb, but where would I be able to see my current firmware? Im guessing in about phone, but I'm not seeing it.
Thanks for your help, and I will try to flash that if I can.
Click to expand...
Click to collapse
Just flash it anyway no harm if using upto date ROM, it's worth a try.
jazz452 said:
Just flash it anyway no harm if using upto date ROM, it's worth a try.
Click to expand...
Click to collapse
I'm having trouble getting what you told me to find. I have an up to date rom, the latest lineage os release, and I'm confused as to what you mean by firmware? Is that included in the rom? Thanks, sorry to sound dumb, just never ran into this issue before.
xstewminator said:
I'm having trouble getting what you told me to find. I have an up to date rom, the latest lineage os release, and I'm confused as to what you mean by firmware? Is that included in the rom? Thanks, sorry to sound dumb, just never ran into this issue before.
Click to expand...
Click to collapse
If you go to RR thread it's on the first page