Hi all.
I recently upgraded my Prime to Jelly Bean, I had to do a manual SD card update, as OTA failed for me.
Everything seems to be good... except I JUST noticed that my stock camera app is gone.
I realized that the homescreen app shortcut for the camera no longer worked, so deleted that (it was pointing to a non-existing app), and I find that the app does not exist in my app-drawer (at least not that I can see... I honestly don't recall what the app was called >_<)
I had done a full backup using the stock app backup/restore app, and I can't see the stock photo app in that backup file either.
So now I'm stuck having to find/install a 3rd party app to use the camera.
Any advice is appreciated.
Hi there,
Have you desactivated Gallery? Had the same problem and re-activating the Gallery fixed it.
Well, I CAN access it through a button in the Gallery app, which I didn't realize before... thanks.
Still odd that I don't have the app any more that launches directly into the camera.
Related
Does anybody notice the same issue?
My phone is not rooted. After the official update to 2.2 (ED01) I found this problem with all apps on my Fascinate that have the scan function: google goggle, shopsavvy, amazon, etc. Sometimes they crash at starting (goggle will force the phone to reboot), but most of the time you can open the app and scan properly once or twice, then the scanner fails to auto-focus or adjust brightness or white balance, getting no response. Hitting any keys on screen or the back key will only end up with vibrating and screen-blackout. I can only exit the situation by hit home and kill the app in task manager.
I found a similar post around xda:
http://forum.xda-developers.com/showthread.php?t=894544
The problem is said to be associated with the stock Email.apk and will be gone once you run the email app. But this solution doesn't work for me.
Anyone has more idea?
I just tested out Google Shopper and Barcode Scanner with two barcodes each, and neither had any issue. Have you opened up the camera app since updating? Froyo brought about new camera firmware, so if you haven't opened Camera since updating, that could be what's causing the FCs.
The stock camera app and third-party apps like retro camera both have no issue. The picture-taking function goes well, problems only come when the app need to scan back and forth and auto adjust.
HKReeves said:
The stock camera app and third-party apps like retro camera both have no issue. The picture-taking function goes well, problems only come when the app need to scan back and forth and auto adjust.
Click to expand...
Click to collapse
I just tried google shopper and it's working for me.
Sent from my SCH-I500 using XDA Premium App
Thank you for testing that for me. Can more people try out? Am I the only one that have this issue?
If so I assume this is an individual problem that can be fixed by factory reset, although I am reeeeaaaally unwilling to do that.
My phone is all tricked out and everything works great.
I tried on my wife's phone which is stock and it has numerous issues with camera, google goggles, market, barcode scanner, etc... surprised she's not noticed. :/
Rebooted and everything worked.
Google Goggle's might have crashed and caused the initial issue.
So, maybe just a reboot will help you?
Thanks, but I have no luck with that. Roboot doesn't help at all in my case. I even uninstalled the Goggles and the other scanner apps still suffered the same issue.
Google goggles works for me
Sent from my SCH-I500 using XDA App
I removed a bunch of bloat apps with Titanium and wanted to restore S Memo to try out S Voice a little more and discovered that the restore doesn't work. It opens but immediately FCs. All the other bloat apps install back just fine. I even pasted in SMemo.apk,SMemo.odex,SMemoProvider.apk,SMemoProvider.odex from an S3 rom dump and no go. Any ideas? It isn't incredibly important but still driving me a bit nuts.
To clarify, I'm trying to see if anyone knows the full dependencies for this app. I have searched high and low on xda and others and this app is specifically problematic but it SHOULD work when on stock with TW.
I was also trying to work this out the other day. There are some guides on de-odexing the S memo app which, thinking about it, might hint at it's dependencies.
see here:
http://forum.xda-developers.com/showthread.php?t=1724567
Have you had any luck?
Hi All,
I have 2x Galaxy S3's, a work one and my own one, my personal one is rooted (to allow titanium backup to do it's thing), it also has ClockworkMod running on it. It's got the stock rom still.
I'm an android developer day to do, and now when developing my app, if I'm using my work phone and it crashes on the phone it says Your App has crashed, click okay to force close.
However, on my rooted phone it doesn't do that, it just crashes and I have to restart the phone just stays with the notification top bar still there and working (clock changes and can see wifi sending/receiving) . But i can't close the app, can't use the home button etc
Does anyone know the solution to this? It's quite infuriating at times.
youtube link + ?v=3mawem-refw here's a video of it happening
Ignore this... App is still there, just not displaying in launcher. If Icon in their launcher is deleted, you can still access it through the gallery by swiping right for the camera.
I accidently deleted the Omate Camera app last night, but can't track it down. (Mea culpa:my ROM backup MIA as well)
Tried looking through Dees Troy's Bluetooth ROM for the apk, but didn't recognize it by name. App isn't in the Omate store, yet seemed to be proprietary Omate when I was using it.
Any help locating a copy to re-install would be appreciated (or even the name of the APK). Rather fond of my setup now and would rather not mess with it by reflashing.
If you think you got app and only icon is gone just go to setting in app manegmer find the luncher and tap on clear data bottom. This will rest your luncher and bring your all app again.
But if you have uninstalled the app by root access the easiest way is flashing new ROM.I hope this help you.
Sent from my HUAWEI MT1-U06 using Tapatalk
Hi there. Please, could you guys help me with my camera app trouble? I've got Huawei Mate 9 Pro with latest updated Android 9 (EMUI 9.1, details below) and I use original Huawei camera app. I like this phone and everything worked just fine, till now... Two weeks ago I tried tu use my camera app and I couldn't. I didn't install any new 3rd party app lately. When I press the camera app button camera starts with black screen and error message "Camera Error - camera was disabled because of safety reasons" and then it shutdowns. I also get error messages in all other apps that use camera - Whatsapp says "Unable to start camera, restart your phone", Messenger says "We're sorry, camera doesn't work. It may be necessary to close other apps that are using camera", and so on... Like I said - I didn't install any other app lately, so everything is like it was.
What's interesting - I tried to run my phone in Repair mode and there camera app works fine, everything is ok. But when I switch to my account and phone profile it doesn't work.
I tried to stop camera app, clear the cache and data. Tried to wipe phone cache and reset apps permissions. I checked all camera app permissions - everything is ok. I called the Huawei consumer help center and they didn't know how to help me, just said I need to run factory reset. So, frustrated, I made a factory reset with backup. After reset and restoring backup of all apps and data, and security update of phone - the camera app worked again! I could make pictures and movies... for one day. After night I tried to run camera app again, and there's the error again. Now I'm helpless... Please, help me. What could be the reason of this error?
My guess is that some other app uses camera app or it was disabled (locked / banned) by Google Account or something? Why? Could it be blocked for "safety reasons" because of some specific photo?
Huawei Mate 9 Pro
Android 9
EMUI 9.1
Compilation 9.1.0.254(C432E7R1P6patch03)
Camera app version 9.1.0.333
Up. Anyone could help me? Problem still exists...
Did you manage to find a solution ?
edit : found out what was causing mine, sensors were set to off in an app, forgot to turn back on. works agein