When I first start the camera app after a reboot I get the message "Cannot connect to camera". If I try to start the app again it works fine every time until the next reboot.
I've tried a factory reset which worked for a few reboots until the message started happening again.
I'm running the latest stock rom and can't figure out what's changing to cause this.
Any ideas?
Had you got that problem on earlier versions of stock ROM?
Sent from my R800i using xda premium
Sorry, I haven't had the phone long enough to have an older version of the stock rom.
Even I had this error once, I had to reboot the device to get that fixed.
This was the 1st time it happened.
One thing is it happened while shooting a 720p Video.
I don't think it's software problem, probably camera is damaged, or its flex cable. I had the same problem for a moment after disassembling my Play but I forgot to completely connect flex to the connector.
I think the only way to fix your problem is to bring Your Play to authorized service or (if your phone has warranty) send it to SE.
Sent from my R800i using xda premium
It could be but it just seems odd that its only the first time using the camera after a reboot. Try the app a second time and every other time its fine.
I would have though if it was the flex cable it would be all the time or happen randomly.
Well.
shadow wave said:
It could be but it just seems odd that its only the first time using the camera after a reboot. Try the app a second time and every other time its fine.
I would have though if it was the flex cable it would be all the time or happen randomly.
Click to expand...
Click to collapse
I'm having an issue like that right now. However, I started getting it after I messed with a ton of system files and the framework-res.apk
Did you do the same? I'm working on figuring out what went wrong, it's definitely a software issue for me.
Possible Problem and Solution
Hey guys,
I noticed something really curious after having an extensive conversation about a few r800's and a Moto Cliq XT about camera issues and I've isolated what might be the problem that people are unknowingly creating.
Status Bar Widgets
Having the LED/Flash/whateveryouwanttocallit light as a widget toggle in Android 2.3.x seems to use the same line of code as the camera. Or something techy like that. IDK. I was about to fix it after a ton of annoying work. But the easiest way (and fastest really) that I came across was just turning the widget off. Removing it completely. In fact, just get rid of that entire feature in 2.3.x and save it for like, IDK, 3.0+
Really hope this helps that random person out there who needs it.
-Fox
Fox Bailey said:
Hey guys,
I noticed something really curious after having an extensive conversation about a few r800's and a Moto Cliq XT about camera issues and I've isolated what might be the problem that people are unknowingly creating.
Status Bar Widgets
Having the LED/Flash/whateveryouwanttocallit light as a widget toggle in Android 2.3.x seems to use the same line of code as the camera. Or something techy like that. IDK. I was about to fix it after a ton of annoying work. But the easiest way (and fastest really) that I came across was just turning the widget off. Removing it completely. In fact, just get rid of that entire feature in 2.3.x and save it for like, IDK, 3.0+
Really hope this helps that random person out there who needs it.
-Fox
Click to expand...
Click to collapse
YES, i agree, should make a fix btw, =)
Related
I started using adw launcher ex and widgetlocker last night (good thing I couldn't sleep ) and am loving them to bits and pieces. one thing, though...
the home screen redraw thing is starting to get on my nerves. it's not so bad when using the home key to jump to the home screen, since I back out using the back key (close the app, save the ram), but even if I let it sleep long enough, it'll lag on redraw when I unlock it -_-
I've seen a fix on the internet that looks tempting but it requires that i root my phone; call me a coward, but my ill-experiences with this sort of thing have left me with no intention of doing so in the near future. any other solutions?
hellloooooo?
PondaRox said:
hellloooooo?
Click to expand...
Click to collapse
Well, I have this problem too sometimes. A reboot could help, and it just disappears for me after a while...
Then again, if it doesn't work and you want to root your phone, you could always post here. I'm sure you'll be helped quickly.
One last thing: Do you have a link to the video? Might be helpful later on
for now, disabling and uninstalling widget locker () has solved the problem. but then, the problem practically wasn't there when i first installed, so i wouldn't consider this case closed just yet
and i know i'll find help with rooting at xda, it's just that if i can brick my phone simply updating the firmware, who knows what i'll do while rooting? plus, there's still 2 months in my warranty, so if i ever decide to root, i'll let the warranty run out first
as for the fix, it wasn't really a video. search the forum (not the samsung galaxy s one) and you'll find it. but in any case, i have the link right here:
http://forum.xda-developers.com/showthread.php?t=932820
if you've rooted your phone, this fix is apparently guaranteed to fix (lol) the problem, which is why it's so tempting
PondaRox said:
for now, disabling and uninstalling widget locker () has solved the problem. but then, the problem practically wasn't there when i first installed, so i wouldn't consider this case closed just yet
and i know i'll find help with rooting at xda, it's just that if i can brick my phone simply updating the firmware, who knows what i'll do while rooting? plus, there's still 2 months in my warranty, so if i ever decide to root, i'll let the warranty run out first
as for the fix, it wasn't really a video. search the forum (not the samsung galaxy s one) and you'll find it. but in any case, i have the link right here:
http://forum.xda-developers.com/showthread.php?t=932820
if you've rooted your phone, this fix is apparently guaranteed to fix (lol) the problem, which is why it's so tempting
Click to expand...
Click to collapse
How did you try to upgrade your phone? Because, when I tried to do it with KIES, I bricked it too. Now, with ODIN, I don't worry about that anymore, once you know, it's easy.
Anyhow, thanks for the link.
flashing; relax, the mistakes were mine
and you're welcome
\m/
Tapatalking from my GT-i9003
i'm happy to report no problems in the hours since i deleted widget locker
but who knows when redraw lag will rear it's ugly head again? i'll wake this thread back up if that happens
by the way, i have another question, might as well ask it right here
have you had your phone just randomly restart while using adw launcher? because this morning, when i woke up, i heard that sound that plays when you plug your phone into the charger (i left it on there in the middle of the night). i figure it might have been a random reboot, but will take any other theory (heck, i'd LOVE to. i thought i was through with my phone randomly rebooting -_-)
PondaRox said:
by the way, i have another question, might as well ask it right here
have you had your phone just randomly restart while using adw launcher? because this morning, when i woke up, i heard that sound that plays when you plug your phone into the charger (i left it on there in the middle of the night). i figure it might have been a random reboot, but will take any other theory (heck, i'd LOVE to. i thought i was through with my phone randomly rebooting -_-)
Click to expand...
Click to collapse
Ummm... I never had that with ADW.
However, some ROMs do have problems with random reboots.
mine is stock JPKE1
\m/
Tapatalking from my GT-i9003
Hello xda members! I have been experiencing a strange problem with my "T-Mobile G2"'s microphone and would like to share it with you in case you had any insight on it:
My phone's microphone is not working - I cannot use voice input, music recognition services, etc. all it picks up is silence. What makes it a "strange" problem? Well, the microphone will work during calls, but ONLY IF I first snap out the keyboard and then snap it back in! Sometimes the microphone will fade out and then go silent again, at which point I'll open/close the keyboard again so that the other party can hear me again.
I thought it was software at first, but then I flashed it to stock and still had the same issue. Now I'm worried it might be a problem with the ribbon cable that connects the two halves. Have any of you ever heard of a similar problem? Any suggestions as to how I might fix it?
If it is intermittent and you reflashed then my guess would be hardware like you suggested.
Most likely you mic is loose. Does it behave the same as opening and closing if you just hit it or shake it?
Sent from my ghdudsjihfr using dhhcdfhuf.
Thanks for the replies, I honestly didn't expect any! Interesting thing.. I flashed MIUI yesterday and now it feels like the problem is fixed. I've noticed a slight lag before the mic responds the first few times but now it's spot on. I don't see why flashing to stock didn't fix it while flashing to MIUI did so I think it's just a coincidence and that this is still a hardware issue.
I'll try and poke around explore this more when I get more time.
jervill said:
Thanks for the replies, I honestly didn't expect any! Interesting thing.. I flashed MIUI yesterday and now it feels like the problem is fixed. I've noticed a slight lag before the mic responds the first few times but now it's spot on. I don't see why flashing to stock didn't fix it while flashing to MIUI did so I think it's just a coincidence and that this is still a hardware issue.
I'll try and poke around explore this more when I get more time.
Click to expand...
Click to collapse
Do you superwipe?
killj0y said:
Do you superwipe?
Click to expand...
Click to collapse
Yup I did use superwipe.
Incidentally, the issue returned after 2 days of working perfectly. Doing a wipe and then installing that same ROM fresh (not a backup) did not fix it so that new most likely ROM had nothing to do with it. I'm giving up then and calling this a hardware issue, period. I guess it's a good thing that the HTC One phones are are coming out soon!
So I got the Galaxy Nexus GSM today and it's one hell of a sexy device.
It obviously came with Ice Cream Sandwich out of the box. And errors out of the box. Right when I start the phone, Talk FCs. When I try to start the Camera, it FCs.
I though "What the heck, Jellybean probably fixes that", so I unlocked it and flashed Paranoid Android. Everything is a lot faster now, but I still have the same problems, except now Gallery just crashes, which renders the Camera unusable, because they're apparently linked together in Jellybean.
I tried 3rd party apps (Zoom Camera, Paper Camera and a few others) and none of them work.
So it seems that everything that has something to do with the Camera doesn't work.
I tried everything that I could think of;
Reflashing
returning to stock
force stop Camera
Disable and enable all network related functions in G+ and Gallery
Clearing cache - both for individual apps and the option from the recovery
Trying 3rd party apps
Googling everything I could think of
Installing G+ (that made me able to open Gallery, but Gallery still force closes when I open Camera)
Changing battery
Of course I can't see it being anything but a hardware issue, but some people who have compiled CM10 by themselves have the same errors. I don't know if that helps me.
So before I return it some time this week, does any one have any suggestions to what I could try?
I'll give this thread two days before I return it.
Thanks in advance.
You rooted? If not and you know how to root, root it, replace the app (gallery, camera, whatever is not working) with stock JB version. Hopefully it's just corrupted apps... That's easy to fix
Thanks for the reply. I've already tried the Jellybean version of Paranoid Android and it made no difference.
I though "What the heck, Jellybean probably fixes that", so I unlocked it and flashed Paranoid Android. Everything is a lot faster now, but I still have the same problems, except now Gallery just crashes, which renders the Camera unusable, because they're apparently linked together in Jellybean.
Click to expand...
Click to collapse
mrhaxx1 said:
Thanks for the reply. I've already tried the Jellybean version of Paranoid Android and it made no difference.
Click to expand...
Click to collapse
Might be a long shot, but have you tried fixing permissions in recovery?
Sent from my Galaxy Nexus using xda premium
I have, but I just tried again and it made no difference.
Also, I forgot to mention that it's not a storage issue, as I can save screenshots just fine.
mrhaxx1 said:
I have, but I just tried again and it made no difference.
Also, I forgot to mention that it's not a storage issue, as I can save screenshots just fine.
Click to expand...
Click to collapse
Any solutions for this yet? having the same problem.
Nope, nothing yet.
And to make the bad things worse, I've lost the receipt. So I can't even return it.
Bumpity bump!
mrhaxx1 said:
Bumpity bump!
Click to expand...
Click to collapse
I just went ahead and called verizon.. and they're shipping me a new phone today. I see a lot of posts about this, with no solution. It'll be quicker to do it this way. Except you call whatever your carrier is. Or samsung, if nothing else.
Well, you see, I bought the phone refurbished. There was a guarantee on it, but I lost the receipt, so I can't return it or get a new phone.
I ordered a rear- and front-facing replacement camera. It should arrive in 7-15 days because I'm ordering from the USA.
I looked into it, and disassambling and assembling it should be fairly simple. Nearly the same process as the Nexus S, which I've disassembled before.
If it doesn't work, I've only lost $22 and it's not like I have a valid guarantee on it anyway.
Oh well, replacing the cameras didn't work.
And I even managed to break the volume buttons.
Even if I got hold of the receipt, there would be no way they would repair it now.
I can as well just go buy a new phone. Next month. Maybe. At least everything else still works.
When you flash ROM, do you ensure you completely wipe previous ROM and data? Also, if you use something like Titanium Backup to restore your apps after flashing a new ROM, make sure you don't restore system apps or data. That will definitely screw things up in every ROM as incompatible files are mixed.
Try doing a full wipe of your device it could help
Sent from my Galaxy Nexus using xda app-developers app
It was like that on the stock rom.
And yes, I always ensure to wipe everything. As said in the OP, I even tried returning back to stock.
I got the same problem, I GOT IT FIXED NO HARDWARE FAILLURE!!
Hi,
this is what i did, got it fresh from the box, didn't even bother to set-up, I instantly updated to Jelly Bean..
everything worked perfectly, besides the camera, it crashed instantly.. (gallery did not respond)..
i rebooted it 2 times, then pressed the Power button + volume down.. it went to an system boot thingy.. the i connected it to my pc with an usb (usb debugging enabled).
my win7 pc said the drivers were installed, then i pressed the power button. after loading. the camera worked perfect.. thats REALY everything i DID.. i'll keep you posted if it fails again.
it also worked after unplugging the usb.. Hope I helped you a bit.
I can second this fix!
IvanGrozni87 said:
Hi,
this is what i did, got it fresh from the box, didn't even bother to set-up, I instantly updated to Jelly Bean..
everything worked perfectly, besides the camera, it crashed instantly.. (gallery did not respond)..
i rebooted it 2 times, then pressed the Power button + volume down.. it went to an system boot thingy.. the i connected it to my pc with an usb (usb debugging enabled).
my win7 pc said the drivers were installed, then i pressed the power button. after loading. the camera worked perfect.. thats REALY everything i DID.. i'll keep you posted if it fails again.
it also worked after unplugging the usb.. Hope I helped you a bit.
Click to expand...
Click to collapse
So, I was having this exact same issue and was ready to call Verizon for a replacement, when I tried this as a last resort and VOILA!! IT WORKED! I am still unsure of how this all came about, but for the purpose of hopefully helping someone with the same issue, I will second this quick fix as IT DID WORK FOR ME.
I had this same problem (camera/talk fc'ed on start, whenever opening either app), tried all the fixes I could and nothing worked. I eventually disassembled the phone and used a toothbrush and isopropyl alcohol to clean the main board and the connections for each of the camera modules. After a couple rounds of cleaning, everything started working again.
navjas73 said:
I had this same problem (camera/talk fc'ed on start, whenever opening either app), tried all the fixes I could and nothing worked. I eventually disassembled the phone and used a toothbrush and isopropyl alcohol to clean the main board and the connections for each of the camera modules. After a couple rounds of cleaning, everything started working again.
Click to expand...
Click to collapse
Thanks for this information, I'll try to do it with mine too. Any results I will post here.
I have tried searching for this problem but I must be using the wrong terms... so sorry in advance if I missed a post that addressed this issue.
My sprint S3 does this twitchy/glitching thing on every touchwhiz based jellybean rom (does not do it on TW ICS ROMS) I have tried. It basically makes it nearly impossible to do sliding animations, IE it can actually get stuck and start flashing halfway between screens, or when pulling down the top menu, however you can open new programs just fine if you are already on the right screen for them. Luckily it does not do this all the time, but when it happens it keeps doing for 10 minutes or so and its annoying as hell.
I figured this must be a rare issue even though it effects both my wifes phone and mine, since I have never read anything about it, however I just got a new replacement phone and it does the exact same thing, even on dead stock TW JB ROM.
Oddly enough I discovered last night that if I turn on my screen filter app it stops completely, but it starts right back up when I turn off screen filter..... any ideas how to fix this?
Try grabbing cache clear from the play store and set it to run every 12 hours. It helped my phone a good bit.
Sent from my SPH-L710 using xda premium
No one else ever has this issue?
joelespinoza said:
No one else ever has this issue?
Click to expand...
Click to collapse
I had it dude, but it was just on the CleanBean ROM, it was annoying as hell!
So I changed the ROM, Its weird that its happening on a Stock ROM, any suspicious app?
I've been able to replicate this issue on my G4 (815T Australian model) on a daily basis, just on the instagram app though.
I recorded a video of it. Slowmo part shows the issue
https://goo.gl/photos/F823e125PQckCPLp6
The screen seems confused and it just scrolls the other way even if my thumb wasn't touching the screen.
Factory data reset did not fix anything.
Are you able to replicate this LG G4 owners?
I don't use Instagram, so can't help with that app, sorry.
But if you go into Developer Options, and turn on "Show touch data", it might help add some more info to the discussion. It will show a trace on the screen of what the phone's touchscreen interpreted from your last tap/swipe.
It would presumably show a swipe up, and then back down, when you're getting these ghost touches that change the scroll direction. But perhaps it could also help show if swipes are interpreted the same way in other apps. It might help you learn a little more about what the phone is seeing, at least.
Thanks for the video and everything but why a new thread? Plenty of videos on the main thread.
Is another thread really necessary?
Sent from my LG-H811 using Tapatalk
Might be, because this only happens with IG. I've got the exact same problem, only with IG and its very annoying.
shook187 said:
Thanks for the video and everything but why a new thread? Plenty of videos on the main thread.
Is another thread really necessary?
Click to expand...
Click to collapse
Apologies, first time I posted it I was thinking it was just Instagram-specific.
KL643 said:
Might be, because this only happens with IG. I've got the exact same problem, only with IG and its very annoying.
Click to expand...
Click to collapse
Ahh good to know I'm not alone on this!
chobie said:
Apologies, first time I posted it I was thinking it was just Instagram-specific.
Click to expand...
Click to collapse
To me it looks like it is IG specific because I don't have this problem with any other app
You can try to change the touch feedback time from short to medium under settings/accessibility/motor & cogination. This will reduce the touch feedback time. Give it a try, and see if it gets better.
Sent from my iPad using Tapatalk
alanchai said:
You can try to change the touch feedback time from short to medium under settings/accessibility/motor & cogination. This will reduce the touch feedback time. Give it a try, and see if it gets better.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Done that but it doesn't solve this problem.
chobie said:
I've been able to replicate this issue on my G4 (815T Australian model) on a daily basis, just on the instagram app though.
I recorded a video of it. Slowmo part shows the issue
https://goo.gl/photos/F823e125PQckCPLp6
The screen seems confused and it just scrolls the other way even if my thumb wasn't touching the screen.
Factory data reset did not fix anything.
Are you able to replicate this LG G4 owners?
Click to expand...
Click to collapse
Question, do you have Google keyboard installed? Because I just removed Google keyboard and installed SwiftKey and it looks like the problem is gone....
KL643 said:
Question, do you have Google keyboard installed? Because I just removed Google keyboard and installed SwiftKey and it looks like the problem is gone....
Click to expand...
Click to collapse
Nope, I use Swiftkey from the beginning. Only LG stock keyboard is installed.
Mm, I've got LG keyboard freezed with TB and after changing from Google keyboard to SK, the problem is gone
KL643 said:
Mm, I've got LG keyboard freezed with TB and after changing from Google keyboard to SK, the problem is gone
Click to expand...
Click to collapse
Interesting. Not keen on rooting though. =\
So you reckon it's just a software issue?
chobie said:
Interesting. Not keen on rooting though. =\
So you reckon it's just a software issue?
Click to expand...
Click to collapse
Well this problem is only related to the LG G4 and IG for me...I don't have any other touchscreen problems with this phone. So for me I guess this is not hardware related. During the day I just had 2 small "ghost touches", way better than before. Will see how it goes the next few days...
Edit :
after a view days, it looks like it didn't solve this issue. Today I notice the ghost touches were there again in IG
Force GPU rendening under Developer options somewhat helped.
The new v10f on my Australian G4 didn't fix the issue as well.
Any updates on this? I had same issue. N this is a replacement unit after 2.5 weeks of waiting
Just day one and this ghost touch come up.
I also have this problem
Did you solve the problem?
I am facing similar issue.between...i am not using ig.
I've had this issue as well (not just IG) and sent the phone back for servicing. It was sent back to me with a report showing that they'd done a few things but the problem is still there. I'd been thinking I'd send it back in once more and ask them to have another look. I'm getting ghost touches everywhere and quite a bit, it's very annoying.
Someone mentioned there was another, large thread about this issue but I can't seem to find it, can anyone point me to it?
Hi, I posted this in a new thread yesterday as I couldn't find anything. Never thought to search for 'ghost taps' duh.
Every now and then when just doing normal things on the my phone it totally freaks out and all by it self it suddenly starts to tap random parts of the desktop, slides the pages, opens apps, closes apps, goes into calculator and a bunch of buttons are pressed randomly. It's almost like someone has hacked my phone and is trolling me by just tapping randomly on the phone.
Just today when looking at Facebook it closed the app, scrolled down notifications, data was turned off and wifi turned on.
I thought it might have been my screeen protector, bit of moisture in it or something. Took that off and still does it. Took out the battery for a minute and still does it.
It happened a few months ago then nothing for ages and now it's started again this weekend.
Thought it might have been only when connected to data but has now done it when offline.
Any one got a solution? Does a custom rom fix?