I did a search and found relayed posts for related issues but no resolution.
If I try to use the flash with the camera on my phone it reboots almost every time. Sometimes I get to take one but then the second will cause a reboot.
This happened with the stock camera on rooted debloated deknoxed stock KitKat and jellybean. I can't remember ICS... Also happens in the couple third party cameras I've tried.
One possible cause I read was a crappy aftermarket battery. I've tried 3 different stock batteries. One is from my girlfriends s3 that does not have this issue. I had it with all of them.
Flash works just fine as a flashlight. Camera works just fine without flash. Picture quality with the KitKat camera doesn't seem as good though.
Not sure what is left to check.
thedumbass said:
I did a search and found relayed posts for related issues but no resolution.
If I try to use the flash with the camera on my phone it reboots almost every time. Sometimes I get to take one but then the second will cause a reboot.
This happened with the stock camera on rooted debloated deknoxed stock KitKat and jellybean. I can't remember ICS... Also happens in the couple third party cameras I've tried.
One possible cause I read was a crappy aftermarket battery. I've tried 3 different stock batteries. One is from my girlfriends s3 that does not have this issue. I had it with all of them.
Flash works just fine as a flashlight. Camera works just fine without flash. Picture quality with the KitKat camera doesn't seem as good though.
Not sure what is left to check.
Click to expand...
Click to collapse
you could always Odin Stock again and see if the problem is still there or you can make a backup of your current rom then clean flash a new custom rom and see if that fixes the issue but i've got no other idea then that sorry
Could be kernel related.. The fact flashlight works fine but flash doesn't is very interesting. If you're under volted you should set it back to standard just to see if it was that. It can be weird. If not, try wiping the data for the camera by going into app manager. Always worth a try.
The issue has been around as long as I can remember with this phone. It has survived multiple clean and dirty flashes of stock and stockish jelly bean and KitKat.
I've used stock and now cnexus' modified kernels. With and without xposed. Stock and 3rd party cameras.
Not that I record many videos but I tried video plus flash since posting this. It worked just fine. Far from extensive testing though.
I've been thinking that it could be hardware for awhile. But figured I'd see if someone else had seen this and if anyone had a real resolution.
Related
The camera has stopped working randomly. The only thing I could think of that might of caused it would be the phone some how shut down when it was in my pocket. When I start up the camera app it immediately closes. When I attempt to use Google goggles, it says cannot connect to camera. What can I do?
First off you can give us some more details as to what software you are running. Are you on a stock Sprint ROM? A custom ROM? Did you install any software and then notice this change? Does this happen 100% of the time?
I'm running the stock 2.2 rooted odexed rom. Stock kernel. And haven't installed any new software to cause this...
I've cleared cache, dalvik cache, camera app's cache and it still doesn't work...
No one has any idea? Has this ever happened to anyone else?
It happens to me on both ava stock 2.2 and now netarchys 2.2... I have to wipe everything to get it back for a few hours... it just did it to me again do you have netarchys fps fix?
Sent from my PC36100 using XDA App
This is the craziest thing ever. The camera has returned to working after 10 hours of not working. I didn't do anything to get it to return. I will be continuing to monitor the camera to see if it happens again... This is the first time it has ever happen and the first time I've been on a 2.2 Rom for a significant amount of time.
This just barely happened to my phone too! Grrrr!!!
I'm running Fresh.02 + I tried flashing several kernels to see if it would fix it but none of them helped.
kernels I tried, latest versions of: kingX, snap, netarchy
Will try to do a full wipe and flash the stock 2.2 rooted w/o any fancy mods. <--- ok this fixed it!
Does installing the 3D Gallery app cause the Sense camera app to randomly stop working?
I'm getting the same problem again on a different ROM.
UPDATE: I've uninstalled 3D Gallery & cleared data on the Camera app and it still doesn't work.
i am having this same problem. have flashed several roms with no fix. cannot pin point when this happened either. really frustrating. ive done reboots, wipe, you name it.
happened to me
blix1337 said:
No one has any idea? Has this ever happened to anyone else?
Click to expand...
Click to collapse
Yes it happened to me, but i have HTC EVO 3D i used leedriod rom and it happend exactly i changed rom to ics and still didnt work know i will call htc and ask them how to get the official ics rom after that if camera wont work i will tell them that the camera was working before i made this update and they must fix it for free
Hi guys
Any luck with this problem? I'm using a rooted xperia neo running [email protected] #2 with an unlocked boot loader - I've used Google goggles many times before and then today its coming up with "Cannot connect to camera. You may need to restart your device" and yet the camera is working because behind this pop up I can see the image that the camera is seeing. I've tried to take a screen shot of this but the screen shot uses the camera and therefore I blanks out the image through the back lens.
I've also uninstalled the app and reinstalled it - cleared all Dalvik cache - as well as moved it to SD and made it a system app - none of these trials have made any difference.
hilfordjames said:
Hi guys
Any luck with this problem? I'm using a rooted xperia neo running [email protected] #2 with an unlocked boot loader - I've used Google goggles many times before and then today its coming up with "Cannot connect to camera. You may need to restart your device" and yet the camera is working because behind this pop up I can see the image that the camera is seeing. I've tried to take a screen shot of this but the screen shot uses the camera and therefore I blanks out the image through the back lens.
I've also uninstalled the app and reinstalled it - cleared all Dalvik cache - as well as moved it to SD and made it a system app - none of these trials have made any difference.
Click to expand...
Click to collapse
Are you sure there are no problems or known bugs with the rom you are using? Have you tried reflashing your rom? (it might be a pain to do, but something in the rom might have broke and it can help to start fresh).
I never post here but I have had a problem with my phone's camera that I fix by some random thread I found a while ago so I thought I would share what helped me. The thread stated it is something to do with the camera's connection to the phone and sometimes with drops or bumps of the phone it becomes loose. All I had to do was turn the phone face down, put my thumb over the camera and press down with some force. Not enough to break it but just to reseat the connection. After that, restart the phone. I have done this a few times and it has been successful ever time. I hope you guys have the same success.
Sent from my GT-P3110 using Tapatalk 2
hippy70 said:
I never post here but I have had a problem with my phone's camera that I fix by some random thread I found a while ago so I thought I would share what helped me. The thread stated it is something to do with the camera's connection to the phone and sometimes with drops or bumps of the phone it becomes loose. All I had to do was turn the phone face down, put my thumb over the camera and press down with some force. Not enough to break it but just to reseat the connection. After that, restart the phone. I have done this a few times and it has been successful ever time. I hope you guys have the same success.
Sent from my GT-P3110 using Tapatalk 2
Click to expand...
Click to collapse
That is correct, in some cases i have found the camera has come unseated. but it could also be the board.
When activating the camera on stock rom, rooter stock rom or custom rom the camera will lock up the phone, screen will turn off and a battery pull must be done to get the phone rebooted. Doesn't seem to matter the rom. Still the same effect.
Back story:
So my sister in law came to visit with her nice new shiny sgsII (t989). She got it from her friend who happens to be a tmobile salesmen in Seattle. She was told that the camera didn't work cause he downloaded something. But took it anyways (since he is her friend and she got it for free).
I thought I'd take a crack at it. Tried a factory reset. Same issue. Found that it was stock 2.3.5 and NOT rooted. Thought maybe a new camera app would fix it thinking the app would hook into the os/hardware and not the default camera.apk.... Same deal.
Last step I tried before coming here was to install a custom 2.3.6 ROM. It got to the standard camera screen but with nothing coming from the camera (black screen) and locked up before needing a battery pull.
I've come to the conclusion that her friend either tried to flash a different cameras firmware on the t989 or dropped it in the toilet OR BOTH!
What do you guys think the issue is?
Why would he want to flash different camera firmware?
I'm stumped. She is here on vacation and that phone is her camera.
da_dragon2k3 said:
When activating the camera on stock rom, rooter stock rom or custom rom the camera will lock up the phone, screen will turn off and a battery pull must be done to get the phone rebooted. Doesn't seem to matter the rom. Still the same effect.
Back story:
So my sister in law came to visit with her nice new shiny sgsII (t989). She got it from her friend who happens to be a tmobile salesmen in Seattle. She was told that the camera didn't work cause he downloaded something. But took it anyways (since he is her friend and she got it for free).
I thought I'd take a crack at it. Tried a factory reset. Same issue. Found that it was stock 2.3.5 and NOT rooted. Thought maybe a new camera app would fix it thinking the app would hook into the os/hardware and not the default camera.apk.... Same deal.
Last step I tried before coming here was to install a custom 2.3.6 ROM. It got to the standard camera screen but with nothing coming from the camera (black screen) and locked up before needing a battery pull.
I've come to the conclusion that her friend either tried to flash a different cameras firmware on the t989 or dropped it in the toilet OR BOTH!
What do you guys think the issue is?
Why would he want to flash different camera firmware?
I'm stumped. She is here on vacation and that phone is her camera.
Click to expand...
Click to collapse
how does one flash a camera firmware?
So this happens on every camera app?
Don't know how one would flash the camera firmware. It was an educated guess. From the info I was told "he downloaded something and now the camera doesn't work" is the only thing I could conclude from that.
On the Samsung Vibrant people would use alternative modified camera.apk or use custom kernels to get the front facing camera working but never seen of anyone changing firmware before.
I have tried technically 4 different apps. one from the stock rom, 2 from the market. PUdding camera and the other I don't recall off the top of my head. They both did the same thing. Which brings me to believe it is either the driver (which could be fixed by a different kernel) or the hardware. Come to think of it, it wasn't rooted when she got it. So I doubt he flashed anything. Unless he odin'd something....
Just got done talking the the previous owner. Turns out all he did was installed some official Google apps from the market place when this happened. Doesnt seem like he did anything wrong. He told me of two other issues that started at the same time as this one. Video playback will reboot the phone and web video reboot as well.
Got a workaround for the video playback: installed mx player and set it to render A/V in software mode. Not the best solution, but it works.
Online videos crash. IE any site with heavy flash. Updating flash didnt solve it nor an uninstall/reboot/reinstall.
That's where I'm at. 1 step forward 2 steps back...
Hate to do this, but..
Bump
So I've been having a bit of trouble with my t989 lately, when I try unlocking the phone I will either get a black screen (the lock screen will appear for a split second before going blank if I hit the lock button again) or it won't track my finger movements on the screen. If I manage to unlock the device I end up seeing numerous graphic glitches ranging from the bar at the top w/ the clock/battery meter just gone and the keyboard not working.
I'm runing CM9.0.0 because I had issues with 10.2 (battery wouldn't charge) and 10.1.3 (similar to my lock screen issues but not as severe, still agitating) and also 9.1 which had the same exact issues as I'm having now. I've tried installing with different gapps but the same thing happens. The phone will work for a day or two, then the glitches come. After resetting, everything is normal for a day or so, then it's normal a few hours, etc. The time is getting narrower between reboots and it's a bit frustrating.
Does anyone know what I could be doing wrong, if anything? I flash via twrp and wipe, then install the rom, then install gapps, then reboot, wait 20min, reboot, and go about my business w/ the setup and such. I would be fine going back to 10.1.3 but jellybean roms and snapchat don't really like to work together on this phone for some reason. It's really the only app I use because it seems like the only way my friends want to communicate nowadays, so I'd prefer to stay on ics if possible...
If anyone can give any insight I'd really appreciate it
greenghoul said:
If anyone can give any insight I'd really appreciate it
Click to expand...
Click to collapse
Have you tried using Odin to flash back to stock? That is usually the recommended step if you are having problems with custom ROMs.
And the newest stock is 4.1.2, so at least you wouldn't have to be on ICS.
meekrawb said:
Have you tried using Odin to flash back to stock? That is usually the recommended step if you are having problems with custom ROMs.
And the newest stock is 4.1.2, so at least you wouldn't have to be on ICS.
Click to expand...
Click to collapse
I'll give that a try. Odin is just the program used to root originally, correct? Also, I want to stay on ICS if possible. So after doing that I'm going to try CM9 again and see how that works.
Anyway, the past few days I've been using AOKP mr2 milestone 1 and it's been okay. For some reason the battery life is bad even with juice defender and a task killer taking care of things. In a matter of minutes after clearing tasks I'm down from ~350mb of ram free to 60. Is that normal with that rom?
I'm not sure what to do at this point. I'm not the best with technology but i figured i was smart enough to figure this out...
bump.
I still haven't tried flashing w/ odin yet. Does anyone know where I can find a gingerbread stock rom? I've been looking for a while and can only find the jellybean one. Since I want to stay on ICS what I want to do is go from gingerbread and up to that rather than downgrading from the jellybean stock rom if that makes sense.
I've been getting these glitches/artifacts/tearing on any 4.4+ rom on my T-mobile S3.
It's like the status bar will glitch down to the bottom of the screen.
I'm currently on a 4.3 stock rom (ENC2), It's been rooted with the samsung toolkit and has knox disabled (at least according to the app).
I've tried most current d2lte roms, PA, spirit, ACIP...ect.) and they all have it.
I know for a fact I'm missing something. I just can't remember what it is for the life of me. I know it has something to do with the bootloader/binary. I seem to remember when 4.4.1 came out there was something with the bootloader we had to do and no matter what I search nothing is coming up with the correct solution.
I'm hoping someone could tell me what i'm missing because it seems painfully obvious and I'm missing it, . I really don't enjoy using TW.
We don't ever mess with the bootloader or other parts of the base firmware, so maybe you're thinking of a different device?
When did it start? What was the last thing you did (flash)? Tbh, to me it sounds like a hardware problem. Maybe a connector got loosened, or some moisture/water damage, or even heat damage could cause what you are describing. Especially if its happening on every ROM.
Flash the stock NC2 firmware via Odin and factory reset. If it still happens after that its almost certainly hardware related.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Does it also happen with touchwiz?
So. I ran the knox removal thing from the samsung toolkit and now I don't see them on the latest CM nightly.
I have to test a few other roms but I don't know, it's somehow fixed, thank you for the responses.
Glad to hear it. Be careful with the toolkit though. It is not supported and has bricked devices.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
After giving it a few days the issue came back.
I've tested this on a stock nc2 touchwiz as well as your (doc) latest likewise release with no issues with the screen or anything.
For the non touchwiz I tried aicp latest 4.4.4, the latest cm11, the latest aospa weekly and a 4.3 AOKP release (milestone2).
The glitch issue wasnt in the cm release for a day or so then showed up, all others showed up instantly.
I also emergency recovered via kies. Then rerooted. I'm also using the latest twrp
Here is a logcat of the ROM I'm currently on, the 4.3 AOKP. I wish I had more of an understanding of logcats so i knew if I posted the right section.
http://pastebin.com/UyZFHriB
I was curious so I booted up a nandroid of aicp and then restored a backup of the boot from likewise. Results were minimal glitching but no connectivity at all. APNs didn't load and WiFi is broken. I'll post a video shortly of the screen.
The only thing that jumps out on that logcat is where you have this kind repeated several times in a row:
09-18 13:35:38.752 W/ActivityManager( *761): Permission denied: checkComponentPermission() owningUid=10060
But I honestly don't know what its referring to. But I will say that since it appears to be happening on every rom, even stock, it sounds more like a hardware issue. Display problems usually are to begin with, but almost any problem that persists across multiple ROMs and wipes can usually be blamed on a hardware malfunction.
Watch a disassembly video on youtube, then open it up and reseat all connectors. (Don't mess with the antenna. Its fragile and not related to the issue at hand.)
Sent from my SAMSUNG-SGH-T999 using Tapatalk
DocHoliday77 said:
But I will say that since it appears to be happening on every rom, even stock, it sounds more like a hardware issue.
Click to expand...
Click to collapse
That's the odd thing, On both 4.3 and 4.4.2 versions of touchwiz I don't get the glitching. Only on AOSP based roms. I could just go stick with a touchwiz based rom and be done with it but my personal preference is not using touchwiz. I'm just confused as to what is actually causing this.
I'm guessing it has to have something to do with the bootloader and baseband.
I think i did forget to mention this is a "refurbished" warranty replacement, i regret that I don't recall which specific version it had as stock, I'd guess it has to be enc2?
Here is a poor quality video to show whats happening, on the home screen you see the glitching where the status bar glitches down to the bottom. I tried to get it to do what it sometimes does in both the MLB app as well as the reddit app but it decided not to be as noticeable this time.
http://youtu.be/ZsZL1Okio-A (sorry about the added music )
Just a side question, I couldn't seem to find a definitive answer, but was it ok to downgrade within the 4.3 bootloaders? I thought I remember reading that as long as you don't go from 4.3 to 4.1.2 it was fine.
Soryy I misunderstood before about it happening on stock. Have you tried any different kernels? I'd suspect that before bootloader. But since it's a refurb, there's just no telling for sure.
Once on 4.3 you cannot downgrade your firmware at all. You can flash older roms, but that's it.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
I have started with the stock ROM, and used cm13, and even updated to the newest fully stock ROM 3.2.4 and to no avail.
The camera app either force closes or nothing shows up on screen. Every once in awhile the front camera will work, but I'll click the icon to switch to the rear camera and no effect, it just stays on fron t camera.
I've tried many third-party apps, I've tried cm camera fix, everything I can think. Clearing data and coach for the app the whole shabang.
Now I'm ordering a brand new camera module and I will see what happens. But any help and any information will be much appreciated thanks
Was it working when you bought it...what did you do to it before it broke?
it definitely seems like a hardware issue, had it been a software issue a custom rom or 3rd party camera might have resolved it and since you have tried many roms and reverted back to stock too so it doesnt look like a software issue.
GeneralDisaray2 said:
Was it working when you bought it...what did you do to it before it broke?
Click to expand...
Click to collapse
Funny you should ask, because I honestly don't know when it actually started but I do remember wiping userdata so I could unencrypt my phone and thereafter was when I noticed it no longer worked. Don't know if those 2 things correlate because I flashed back to stock (which is encrypted) and still no luck
Did you solve the camera problem ???