I have the latst CM10 that was posted on the forums but the camera app is not showing for me. Anybody know why? I installed gapps.
Nobody ha this issue before? I know the camera works because I can use it in google hangouts, I just don't have a camera app. Is there somewhere I can get it or does anyone understand why the stock isn't showing up?
It's odd that you don't have a camera app since it's a system app. Could you have accidently disabled it? If you didn't, you can find the Android 4.2 camera and flash it. Works fine except for photosphere.
Had the same problem; I was following one of the tutorials that advised to desactivate Gallery, but the photo app dissapeared when doing so. Reactivating Gallery brings back the photo app. Hope this helps...
the gallery apk does contain the camera runtimes, they aren't seperate.
Related
I flashed cyanogenmod 7.1 a few days back and really love this ROM.
The camera though seems to be really bad. Everything appears dark once the picture is taken.
Is there any way to flash the stock camera to cyanogenmod ? Or any other solution ?
I can confirm this. Using Euroskank 12-26 kang, the camera seems to take an acceptable picture, but when first reviewed and later viewed in the gallery, the picture becomes very dark. Once viewed online or on another device, the picture seems to be fine.
So.. not really sure if it's a problem with the camera or the gallery.
Nothing to do with the hardware camera...Try flashing a stock camera apk or just revert back to your previous rom backup and do a clean wipe and try again
I seemed to have fixed the issue by moving all the pictures out of the DCIM folder and clearing the Gallery app data.
returnzer0 said:
I seemed to have fixed the issue by moving all the pictures out of the DCIM folder and clearing the Gallery app data.
Click to expand...
Click to collapse
The problem has been discussed before and this is the solution.
is there a way to flash only the camera app from stock rom to cyanogenmod ? Tried restoring camera app from titanium backup but that didnt work
OK, so I'm building a AOSP rom from source for the Xoom. When I compile the rom it will make gallery2.apk just fine. But the camera app does not show up in the app drawer although gallery will.
I have copied gallery2.apk to my galaxy nexus and both camera and gallery works fine.
I have googled and come up short of solutions for this issue other than "camera & gallery merged". I know this already, it just seems like something is missing allowing the xoom to start the camera hardware.
Also, camera works fine on other builds like CM or EOS....just not my build...grrrrr
Does anyone have any ideas to throw my way to get this resolved? Any help is appreciated.
Oh...when trying a 3rd party camera app I get "Error: Cannot start camera"
SOLVED - WAS MISSING A DRIVER
Hi All,
Long time reader of the forum, finally registered an account.
I'm having an issue wherein the camera freezes and crashes while taking video in apps. Video works fine while recording using the camera app. I've noticed this while using the messaging app and vine. In vine the video starts recording for about .5 seconds before crashing.
I am rooted and using AOKP JB rom (latest). I would have posted in that forum but I'm not allowed since it's a new account (you guys are serious here). I've searched that forum, found a few related posts but no resolution. I have fully wiped, I have cleared app data. I think its a problem with a ROM or Kernel itself. Actually seems like a buffer issue since the video records briefly before crashing but who knows.
If anyone has had a similar issue maybe with another ROM let me know. thanks.
No one else has had this problem??
If there was another topic let me know, I've searched heavily but maybe I've missed it.
I'm just trying to determine if this is hardware or software (or kernel/ROM).
Can anyone confirm that they are NOT having this issue and let me know what software you're running?
Thanks.
The most reliable test of whether your problem is hardware or firmware related is to flash back to stock and try the video in the stock camera. You can make a nandroid backup and restore it afterwards to get back to where you are now.
On the stock GB ROM the camera works in SMS but malfunctions in some apps.
I just flashed the official JB ROM from samsung and everything works perfectly, so definitely software.
same issue here, for vine, snapchat, instagram.
Similar issue here, with a Samsung Galaxy 2 (SGH-T989D) running JB 4.1.2 with the official JB update, rooted.
Camera will work for 20-30 seconds and then the in-app video preview will freeze and the only way to get the camera to work again is to reboot. There is no zombie Camera process to kill. Fixing permissions doesn't help. Doesn't matter which app tries to access the camera, they all fail.
I've tried the diagnostics test (*#0*#) and have been able to determine that it's only the rear facing camera that fails, the front facing camera always works fine.
I tried various camera firmware versions (using the "Camera Firmware Standard" screen, *#34971539#), currently running version SEEH05. Other versions either didn't work at all or would perform equally poorly.
I thought it might be an SD card problem,
But after removing the external SD card, the camera performed even worse (crashed even faster).
On the other hand the phone is still under warranty from Telus, so I'm considering flashing back the unrooted ROM and returning it for repairs, unless someone can suggest something else to try.
Running PAC ROM (22.0 i think) from the ported development section and have the same issue with the rear camera but the front camera seems to work OK most of the time for Snapchat and such. A while back I tried one of the separate 4.2.2 camera APK's that's floating on this site and had the same issue still.
Has anyone tried the new leaked 4.3 camera to see if that works better/worse?
Not sure if this would work or not, but you could probably try.
Clear out all current videos and pictures on internal sd card(of course after taking backup), wipe/reset and then do a fresh rom install.
Article from DroidLife with link to download the new stock camera app from the Google GS4 and HTC One.
http://www.droid-life.com/2013/06/27/download-new-stock-camera-app-from-google-play-edition-phones/
Hope it plays well with our phone...
Digil said:
Article from DroidLife with link to download the new stock camera app from the Google GS4 and HTC One.
http://www.droid-life.com/2013/06/27/download-new-stock-camera-app-from-google-play-edition-phones/
Hope it plays well with our phone...
Click to expand...
Click to collapse
I already tried it... and it works well on LG stock 4.1.2 also. including Photosphere.
Edit: We don't have HDR mode. (on 4.1.2)
Failed to install for me on 6/23 Rootbox.
Works perfectly on slick jb. Photosphere worked pretty well too.
Sent from my LG-E970 using xda premium
Digil said:
Failed to install for me on 6/23 Rootbox.
Click to expand...
Click to collapse
Workaround to get to install on Rootbox:
-browse to /system/app with a file browser
-find Gallery2.apk. Rename Gallery2.apk to Gallery2.apk.bak
-exit file browser
-install new camera app as you normally would (sideload)
Optional if you want your old camera and the new one (I did, cause there's more options in the RootBox camera, and it can save to external - the new one can't)
-go back in your file browser, and rename the Gallery2.apk.bak to Gallery2.apk. (it will be at the bottom of the list now due to the .bak extension)
you will now have 2 cameras in your app drawer.
This worked for me (i already had 2 cameras installed by using ponyexpress' sphere fix) and the new camera overwrote pony's sphere camera.
Edit: getting gallery fc when trying to save pics with new cam. Clearing app data didn't seem to solve this. Still messing around trying to get it to work right.
Edit 2: At work, so can't spend too much time with it. If I already have GalleryGoogle.apk installed (from ponyexpress' prior sphere fix) it will install itself as a system app, overwriting pony's fixed sphere camera. If I rename GalleryGoogle.apk to GalleryGoogle.apk.bak before I install, it will install as a user app (presumably because there is no GalleryGoogle.apk in /system/app to overwrite??).
In both cases, the gallery will force close immediately after taking the first photo with the camera. I can re-open the camera app, and take one more shot, then get another gallery force close. The photos I'm taking are being saved, and are viewable in the gallery. Clearing app data for GalleryGoogle.apk in either case does not fix the force close. Also, once I clear app data the UI in the new camera gets mangled - it appears that all the functions still work and are in their proper places, but the icons representing many of them are either wrong or absent. Not sure what to make of this. If installed as a system app, uninstalling updates then reinstalling results in screwed up UI from the get-go.
I've pretty much reached the extent of my troubleshooting knowledge on this - if anyone has any other suggestions, I'll give them a shot. A full wipe may be helpful, but I'm not in a position to do that until after the weekend at the earliest - and I'm not convinced it will change anything. FWIW, I'm on houstonn's RootBox 6/28a build using his included kernel, Banks 4.2.2. multi-dpi gapps, houstonn's ATT NFC fix and as previously stated, pony's sphere camera flashable fix.
How is the quality on root box? Any better or worse?
danial.aw said:
How is the quality on root box? Any better or worse?
Click to expand...
Click to collapse
I'm certainly not the best person to be comparing quality of camera apps to each other - but it looks about the same, or maybe slightly poorer than the included RootBox camera. This is with minimal testing and a very un-critical eye.
Hello everyone. I just got this phone the other day after returning the galaxy s5. I am loving it but I have one issue and maybe I'm just doing something wrong.
Everytime I take a picture in the camera app after tapping the check button, the camera closes and I return to the home screen. Does anyone else have this problem or is there something obvious I'm doing wrong?
Not normal. If the phone is stock (unrooted, etc.) I would try a factory reset (backup any personal data first) and see if the problem persists.
Only time I see a check in camera app is when sending picture via mms and it asks where I want to send [email protected],camera etc... if this is case of attaching picture directly from camera to an mms then this is a normal function, if taking a picture and it just closes then this is not normal reaction
Well it seems that the problem has resolved itself. I was just about to post a screen shot of the check mark so you guys could see it and then it just starting working as normal. Thanks for the responses and I'll post here if it comes up again.
Ok the problem returned... I showed the issue to a buddy who has the same phone and it also turned out that I was missing several options on the camera. I did a factory reset and the problem persisted.
I think I found the issue... I was using Google Now Launcher. Apparently that launcher doesn't play well with the camera. I uninstalled the launcher and voila, all the features (video, zoe, dual camera,etc) are back and the camera no longer closes after taking a pic.
Anyone else want to test this theory and see if happens?
confirmed issue and workaround
Hi there,
I can confirm that the Now launcher uses the native Google camera instead of the Zoe camera. I have also found that from the lock screen with the now launcher installed, unlocking by pulling the camera icon opens the full HTC zoe-enabled camera again. I find this super annoying as I'd like to have Google launcher and have the camera work properly. Anyone know a fix for this other than my workaround?
Ditto for T-Mobile HTC One (M7)
There's a lot I really like about the Google Launcher, but this just drives me nuts. I didn't really understand the workaround suggested here ( though I have no doubt it works). But the suggestion sounded on target. So, I went into my app list and shared it from there. It didn't do the funky stuff any more. I wonder if there's a setting to change that behavior: like someone thought, Hey, take a picture and go back to our regular programming? It's a shame because I really feel that the Google camera takes better picture.
In any case, just to let folks know that this is a real problem. The OP was on target.
To anyone else having this problem that does not use Google Now Launcher, another app that causes this is Omni Swipe. The default camera button in the tools section isn't the right camera (not sure what it's trying to access but still). If you add the correct camera app to the app section, it'll be fine.
Yes, this solved my problem as well. I went back to the default launcher and now the camera is working fine