[Q] Should Camera button switch to camera mode? - Motorola Photon Q 4G LTE

I'm new to this phone, Android, and CM11, so I'm not sure which of those three things are to blame...
I expected that when I push the camera button, the phone would switch to camera mode as it did on my previous phone (not a smartphone) but it doesn't appear to do anything at all. I can use the camera by opening the camera app, then the camera button does work to take photos so I know the button itself isn't broken.
Is this expected behavior, or does it work as I expected when the phone was stock? Is this possibly a bug in CM11 (I'm using 21OCT2014 nightly)? Is there a setting I can change to make the camera button switch to camera mode?

Nobody knows? I can try flashing my phone back to stock to see, but that means I'll have to learn how to backup first so it's not as easy as someone just answering...

I'm pretty sure on stock it launches the camera app properly.
I think the issue with CM is we share the device tree with many other devices (hence the moto_msm8960_jbbl name - it covers all the Moto's with that SoC and bootloader).
Someone was asking about that in the CM thread. I'll try to find the post - I meant to when I originally saw your thread and got distracted.

Thanks! I'll just cross my fingers a future CM will make it work, not a huge problem in the mean time.

enigma9o7 said:
Thanks! I'll just cross my fingers a future CM will make it work, not a huge problem in the mean time.
Click to expand...
Click to collapse
Ah, finally found the post.
(I kept forgetting to search for it, lol).
http://forum.xda-developers.com/showpost.php?p=55752030&postcount=34
Edit - looks like http://review.cyanogenmod.org/#/c/74257/ was just merged recently too. Try the Nov1 (or later) nightly of CM.

arrrghhh said:
looks like http://review.cyanogenmod.org/#/c/74257/ was just merged recently too. Try the Nov1 (or later) nightly of CM.
Click to expand...
Click to collapse
Thanks again! I tried 4 November, and sure enough, it works. I have to hold in the camera button a second, (not just push it once), but it did indeed open camera app.

enigma9o7 said:
Thanks again! I tried 4 November, and sure enough, it works. I have to hold in the camera button a second, (not just push it once), but it did indeed open camera app.
Click to expand...
Click to collapse
I believe this is by-design. You don't want to short press the camera button and have it always open the camera - as the press could have been a mistake. Long press ensures that is indeed the action you wanted.
Enjoy.

Related

CM7 Bugs and To DO list

Current version: CyanogenMod 7 Beta 6
Bugs:
[1].Microphone is not working when speaker is active
[2].Movie playback: playback is jumping frames backward
[3].Camera recording is skipping frames
[4].Igo and Motonav navigation very buggy/resets phone
Click to expand...
Click to collapse
To Do list:
[1].Recording: 720p (red lens) & WVGA (green lens)
[2].Power Menu:
-Reboot Recovery should go to Custom Recovery instead of Stock
-Reboot Bootloader should go to Bootloader or Android Bootmenu
Click to expand...
Click to collapse
Please report bugs here. Do it only if you have Current Release, specified at the top. A bug will be added only if a 2nd user will confirm/reproduce the problem!
I wonder when does the next version come?
thanks for your list
Not everyone has the volume up button bug I certainly do not. Also not sure how the reboot to recovery option would work as we have a non standard custom recovery.
Sent from my Defy on EphuNord rom.
I just tried the leaked version of Google music 3 and it works perfectly with 5.1 so may be we can have this as default music player in the next release.
Edit: how about requests, thanks.
Sent from my MB525 using XDA App
I'm hoping the final version or the next version can incorporate built-in codec like the Korean official froyo. If you have used Jboogie's Blur version that is based on Korean official froyo, it can play almost any type of video formats on the fly without using an app like v-player that relies on software codecs.
[2].DO NOT press Volume up when you are recording, because then your camera will freeze and force close and then you have to reboot
Click to expand...
Click to collapse
Just tried this out, but no freeze for me.
Another ToDo would be optimizing the battery management.
Stock Roms due its integration of motorola battery manager have a much better battery performance.
binodnepal said:
I just tried the leaked version of Google music 3 and it works perfectly with 5.1 so may be we can have this as default music player in the next release.
Edit: how about requests, thanks.
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Do you have a link (apk, update.zip) ?
ephumuris said:
Not everyone has the volume up button bug I certainly do not. Also not sure how the reboot to recovery option would work as we have a non standard custom recovery.
Sent from my Defy on EphuNord rom.
Click to expand...
Click to collapse
before the bootmenu we had a custom recovery that was called by an app, couldn't this call be made from the reboot menu?
so the bugs that i found
a.camera sound when boot (I got red lens)
b.720p playback don't work on portrait but landscape it's ok
c.I used VLC stream&convert to play my video from pc via defy. It took 12 seconds before the video appear. Normally,It takes 2-3 seconds on 3.4.2-177 or 3.4.3-11
The bugs on above i haven't found any except the microphone when speaker on.
---------------------------------------
Thank You
There is official bug tracker https://github.com/Quarx2k/android_device_motorola_umts_jordan/issues
je198ß said:
Do you have a link (apk, update.zip) ?
Click to expand...
Click to collapse
Try Google search, I got it from search
Sent from my MB525 using XDA App
in and out call have bug for me.
Everytime answer a phone and when the proximity sensor go to black screen my phone just go to mute mode.
I don't know why this happen to me, anyone??
my notification power widget disappear from notification bar and to bring them back i have to restart the phone. Does anyone know how to bring them back without having to reboot the phone????
stapuv said:
my notification power widget disappear from notification bar and to bring them back i have to restart the phone. Does anyone know how to bring them back without having to reboot the phone????
Click to expand...
Click to collapse
go to CM setting
h9s said:
go to CM setting
Click to expand...
Click to collapse
and what to do there?
In CM settings -> Interface->Notification power widget->disable hide on change
adyrafy said:
In CM settings -> Interface->Notification power widget->disable hide on change
Click to expand...
Click to collapse
ok 10x I will try it
When taking pictures with high contrast, for example outside with sun shining, the camera-app freezes sometimes and the preview looks weird. lock and unlock, and camera works again, but the previous taken picture is not beeing saved.
I can't tell if it's only for the green lense, but it is reproducable and in quarx' thread I saw a few guys having the same issues. I will search and quote them when I'm back home again.
edit: From Quarx' CyanogenMod 7 thread:
spryte said:
Could anyone else confirm problems taking photos outside with stock camera app? It does not take any photos at all when the sun is shining brightly, because when i take a photo the preview freezes and no Image ist bring safed. (I got a green lense)
Sent from my Defy running on CM7 Beta 5.1
Click to expand...
Click to collapse
marhensa said:
okay, it's true...
i can reproduce your error when capturing something with high contrast (like a lamp, lcd monitor, or outdoor capturing)
@Quarx, i think stock /system/etc/mot_ise_imager_cfg.bin is just fine.. it's more stable.
less compressed image is not neccesary enough,
we need reliable camera for a nice moment to capture...
imagine you suddenly saw ufo / superman / weird moment in the sky,
you take a picture but your camera freeze..
sorry for the dumb imagination
Click to expand...
Click to collapse
marhensa said:
cannot reproduce your error,
it just fine here, with/without flash.
green lens.
-----edit:
i can reproduce your error on high contrast object or condition
http://forum.xda-developers.com/showpost.php?p=13662285&postcount=3130
Click to expand...
Click to collapse
labsin said:
Made a photo outside and i just got the upper lines with rest greyed or green. Doesn't save picture. Now inside house, i don't have this.
It seems to be on 5Mpix only. Change focus or auto-flash don't change anything.
Also afterwards options on the screen don't work and have to switch video and back.
ps.: made donation!! ^^
moneybookers was easier for me.
Click to expand...
Click to collapse
so i've updated cm7 from 5.1 to 6, and now the wifi can't find any networks, not even if i manually set it up. tried to go back to 5.1 but that version wouldn't work anymore either. tried fxr wifi fixer from market, no success. tried wiping cache partition, no luck.

help! my camera does not work at all!

not only does it say "cannont connect to camera" but, the "Torch" flashlight does not work as well, i've flashed the camera libs over. and full wipe/flash but still can't get it to work i'm on CM9. :/ please do help!
boygee said:
not only does it say "cannont connect to camera" but, the "Torch" flashlight does not work as well, i've flashed the camera libs over. and full wipe/flash but still can't get it to work i'm on CM9. :/ please do help!
Click to expand...
Click to collapse
What version of CM9 are your on? Anythiny lower than Alpha 6 will have camera issues. There are two types of cameras for the DS. So there needs to be two kinds of drivers. The fix was implemented in A6. A simple reboot will work. If not just power off and do a battery pull. Count to 10, and power on.
Sent from my myTouch_4G_Slide using Tapatalk 2
i'm on alpha6, but i've changed to stock rom for a bit. i want to mess with all the camera functions it does. by any chance do you know how to disable the auto-cap function? there isn't a box to check or uncheck it.

[Q] Known bug list with CM11 XT897/Photon Q 4G

Hello,
is there a list of known bugs for the photon q somewhere? I cant find anything related to CM11 for it.
Using the latest CM11 nightly's i am getting some bugs, most important (for me) are:
- Once the phone is booted you get the SIM code screen. I can enter the SIM pin there via touch fine. After that screen is passed
it gets to the phone lock screen. There you can not enter the code via the touch screen, only via physical keyboard.
- Camera button doesnt work (doesnt launch camera app). Inside the camera app the button works (takes pictures).
- Sometimes the data connection "hangs up". It displays 3G/Edge/HSPA+ connected but no data is passed. Only way to get it back to work is to
reset the data connection by turning mobile data off and then back on. I havent been able to find any special situation when this happens, its just random.
Which nightly are you on? Are you using the moto_msm8960 builds?
You are describing some GSM issues, which I cannot recreate but the CM maintainers should be able to.
As for the camera button issue, I think you can map it to anything - although mine seemingly does nothing as well (outside of the cam app itself).
Sent from my PHOTON Q using XDA Free mobile app
The camera button is working in the M5 build. You have to hold it for about a second for it to work, probably a protection against accidental presses.
Solust said:
The camera button is working in the M5 build. You have to hold it for about a second for it to work, probably a protection against accidental presses.
Click to expand...
Click to collapse
I'm on a nightly from June 5th. Holding the button vibes the phone, but nothing actually happens.
The camera button works as expected for me on CM11 M7 from the 9th
Right now i am on today's nightly (15.06.2014).
I've checked the changelog but couldnt see any important changes that could have resolved this issue...will test the next days tho.
Any idea how to map it correctly?
I am not going to use M-builds, they are simply too old and include security bugs (like the openSSL issue).
arrrghhh said:
Which nightly are you on? Are you using the moto_msm8960 builds?
You are describing some GSM issues, which I cannot recreate but the CM maintainers should be able to.
As for the camera button issue, I think you can map it to anything - although mine seemingly does nothing as well (outside of the cam app itself).
Sent from my PHOTON Q using XDA Free mobile app
Click to expand...
Click to collapse
The one bug for the msm8960 builds is the incall volume bug, it goes away after restart, but usually shows up after each phone call for me

[Q] trying to use camera from lock screen results in crashreboot

I flashed 5.0 onto my Nexus 5 a while back and have been loving it. But there is a MAJOR issue I have encountered.
If, from the lock screen, i swipe to open the camera (I use Google's camera app) then swipe on the charms and select video and press record... i can almost always reproduce an immediate forced reboot it makes me very sad.
I have tried wiping the system cache... i'm not sure what else to do...
any advice?
bumping... been playing around with my N5 more and more and still getting the issue.
I notice that it happens in other camera apps that can take videos as well. Not just google's official camera app.
Also, it does not have to be launched from the lock screen for it to occur. sigh.
there have been a few times where i can get it to successfully record a video... but i can't reproduce it all the time. MOST of the time it crashes my entire phone
Same here. Noticed they pushing 5.01 out... Maybe a fix. I've had every Nexus and early software is allways buggy, IMO
thanks so much for replying. just glad it's not only my phone, you know?
I think I found a workaround until google fixes it. and they better.
if you open the camera and switch it to video mode but BEFORE pressing record, if you toggle the thunderbolt (light) on and off at least once (doesn't matter if you leave it on or on afterwards), then start recording it SHOULD work without rebooting... at least it has so far.
Dont have the issue on mine, i have the ElemantalX kernel though but i dont think that makes a difference
Zulith said:
I flashed 5.0 onto my Nexus 5 a while back and have been loving it. But there is a MAJOR issue I have encountered.
If, from the lock screen, i swipe to open the camera (I use Google's camera app) then swipe on the charms and select video and press record... i can almost always reproduce an immediate forced reboot it makes me very sad.
I have tried wiping the system cache... i'm not sure what else to do...
any advice?
Click to expand...
Click to collapse
I'm certainly not suggesting the issue doesn't exist, but I cannot reproduce this on my stock 5.0 installation.
That being said, there are seemingly lots of Lollipop bugs that some people get and others simply do not... in my experience that'll probably make them a little more time-consuming to fix.
Well, a little good news... I hope?
I did a flash to 5.0.1 stock and i can't reproduce it anymore. videos record perfectly fine.
now let's give it a week or so of me dicking around with various apps and settings and see how that goes
Zulith said:
Well, a little good news... I hope?
I did a flash to 5.0.1 stock and i can't reproduce it anymore. videos record perfectly fine.
now let's give it a week or so of me dicking around with various apps and settings and see how that goes
Click to expand...
Click to collapse
That's interesting - they must have changed something about the camera then.
I wasn't having the issue you described but I did occasionally get "cannot connect to camera".. fingers crossed it's sorted :good:

[HELP] Camera won't work after Android 11 Update + Possible Cause?

I was previously on android 10 i believe just a few days ago and my camera was working just fine. The other day I got a notification telling me to update to android 11...so i did and didn't think anything of it.
I use my camera alot for photography so this is very important to me, google camera or any app that uses your camera no longer works.
Example 1: As soon as I launch google camera it just crashes.
Example 2: Snapchat, instagram, or any other apps just give me the error like "snapchat was unable to open the camera".
I know a lot of people are getting this same issue because if you go to the play store and go to google camera app and sort reviews by recent tons of users are experiencing this.
I have two theories on what's causing this.
Theory 1: I've been using an app called "lens cap - disable camera" for over a year now just for peace of mind, I guess it used some sort of device administrator priveledges to block all apps from accessing the camera.
I believe I had the lens cap on (camera disabled) before and when I started updating to android 11 and I think that may have caused a weird break in permissions that somehow has me permanently unable to use the camera anymore.
The reason why this is something I suspect is because according to the developer of that app "android 11 removed most of the functionality of device administrator in favor of enterprise work profiles" (not sure what this means) but I think for some reason this caused it to get permanently blocked.
I have the github page for the apps source code if anyone can possibly look at it and see what exactly the app was changing in the first place because then maybe that way someone can possibly come up with a way to fix mine and many others cameras.
Edit: Apparently I'm not allowed to post links on a new account but the program can be found on github called LensCap by a user named percula
Theory 2: Android 11 just broke the camera by itself and the lens cap app maybe has nothing to do with it.
Ive already done all the obvious troubleshooting like resetting permission/preferences, restarting in safe mode, uninstalling and reinstalling camera apps + clearing cache and storage etc
Sorry of my formatting or grammar is sloppy at all I've had a long day and I just really want to get this working again
If none of your troubleshooting fixed the issue, I think the next option is to do a full reset (using recovery - not the selection in the settings menu). Another alternative is to flash the full factory image and allow it to factory reset the phone as well.
This will mean loosing all your app data and pictures, etc, so back up before you do it. But I am confident it will fix your issue, regardless of the actual cause.
sic0048 said:
If none of your troubleshooting fixed the issue, I think the next option is to do a full reset (using recovery - not the selection in the settings menu). Another alternative is to flash the full factory image and allow it to factory reset the phone as well.
This will mean loosing all your app data and pictures, etc, so back up before you do it. But I am confident it will fix your issue, regardless of the actual cause.
Click to expand...
Click to collapse
So would you recommend doing "recovery" or "flashing"? Also how do I get to this "recovery" thing,
originally I was thinking about trying to downgrade back to android 10 but from what I remember the steps looked really confusing ;w;
Apparently a lot of people are getting this issue but in the end they said they had to try and RMA it, so I hope recovering or flashing fixes it, kinda worried this update actually permabricked something in my phone.
sorry if its a dumb question I don't know much about phone stuffs
thank you for your response.
There's definitely an issue with android 11 and the camera.
I didnt have any issues on the beta 2, 2.5, or 3. But upon installing the public, official version.. the camera fails. I've tried 2 factory resets. I've installed the ota.zip via adb sideload. And then did a complete format and install of the full image.
Here's what issue I'm having, personally:
When I open the gcam app, it freezes for about 15 seconds. Then I get the "not responding" screen. If I hit wait, about 15 second later, I get the camera on and it's images are on the screen. But it's so laggy that it's not even functional. For instance, If I try to zoom in, it's about 20 seconds until it actually does. Same for taking a picture. I have sent bug reports to them.
I'm gonna downgrade to a better/smoother version. Probably a custom android 10.
Like others, I use it24/7. The pixel 3a is an incredible camera. I hope it's fixed soon.
I don't even know where to post, I came here looking for a solution, but looks like there may be none, other than going back to Android 10 and never ever installing any kind of update on this phone.
I bought the 3a because of the camera, and because I was taking crappy quality pix of my toddler with my previous phone. A9 worked great, A10 worked great. Camera almost instant, switching from Camera, to Video to Portrait, no problem. Message that A11 is available, so hey why not, it's not IOS. Wrong. It totally screwed me, the camera takes from 1-8 seconds to start, to switch between modes. If I double click power when locked camera start (with delays), I then turn it off using power button, when I unlock the phone the camera app is open.
Sometimes when I open it a second time it stays on the setting I chose before (i.e. portrait, or video - not camera default - this would be a nice toggle in the options though - say if you always shoot portrait).
Portrait mode has reversed the picture order (left/right - blur/no blur).
I have missed many shots of my little one since I've upgraded because of this garbage update.
I have a lot of apps that aren't the "latest" version, that work as I need them to; can someone suggest an app that will let me back up my exact versions, then reinstall them after? I have no idea if such a backup/restore app could also save the app data; I don't have root
Also, if someone could point me to a post which shows the way to switch back to Android 10, step by step, I would appreciate it. If I need to reload all the apps and info, I might as well go back to a known working version.
I have also noticed that some other apps are acting funky now. A once rock stable and reliable phone, these days I just want to throw it straight down at the pavement with all my strength... often...
I have the same issue. Have you resolved it yet. My camera app is working but other app using camera gives error.i had also lenscap and problem arised after update to android 11

Categories

Resources