Hey guys, I got a problem with my Camera freezing after I take a picture. I'm currently using Carbon, and noticed this with nightly 9-1-2014+Arrrrgh's Aug 2. 2014 overlocked kernel. So I updated to Carbon's nightly 9-22-2014 build hoping it would go away, but it's still happening after I take a picture. This time around I didn't install the overlocked kernel, so i'm using straight Carbon nightly. Also, i've tried using the Camera 360 app from the market and it still happens. The camera straight freezes and crashes after I take a picture. Anyone have any ideas?
Odd I don't have that issue with Carbon... but it's been a while since I've installed an official version.
You clean flashed I assume?
Well, I started using Carbon again once the JBBL builds started. I clean flashed the first JBBL nightly from Carbon, then dirty flashed 9-1-2014 version, and now on 9-22-2014 nightly.
Related
After flashing latest CM 10.1 nightly (20130311) my tablet booted up but I got the message " Unfortunately System UI has stopped working". Rebooted into twrp recovery and flashed CM 10.1 20130310 nightly. Everything worked fine as usual. Tried flashing CyanDelta 20130311 update file and got the same message. Flashed back to CM 10.1 20130310 nightly again and everything was fine. Has anyone experienced this problem with the CM 10.1 20130311 nightly on Xoom wifi? I have flashed CM 10.1 20130311 nightly on both my GNex and my Nex 7 and have had no problems. Has anyone heard of any bugs with the Xoom CM 10.1 nightly (wingray)? Thanks.
Sent from my Xoom using Tapatalk HD
I had the exact same issue last night. I chalked it up to user error since I had not upgraded CM from within the settings before. I am new to CM and didn't have this option on the competing ROM I used.
kevk60 said:
After flashing latest CM 10.1 nightly (20130311) my tablet booted up but I got the message " Unfortunately System UI has stopped working". Rebooted into twrp recovery and flashed CM 10.1 20130310 nightly. Everything worked fine as usual. Tried flashing CyanDelta 20130311 update file and got the same message. Flashed back to CM 10.1 20130310 nightly again and everything was fine. Has anyone experienced this problem with the CM 10.1 20130311 nightly on Xoom wifi? I have flashed CM 10.1 20130311 nightly on both my GNex and my Nex 7 and have had no problems. Has anyone heard of any bugs with the Xoom CM 10.1 nightly (wingray)? Thanks.
Sent from my Xoom using Tapatalk HD
Click to expand...
Click to collapse
Just wanted to report the same. Yesterday build did not work so I had installed 20130310 build and it is ok although I did not check all the apps.
RoryPG said:
I had the exact same issue last night. I chalked it up to user error since I had not upgraded CM from within the settings before. I am new to CM and didn't have this option on the competing ROM I used.
Click to expand...
Click to collapse
sashykanth said:
Just wanted to report the same. Yesterday build did not work so I had installed 20130310 build and it is ok although I did not check all the apps.
Click to expand...
Click to collapse
So far all my apps seem to be working with cm10.1 20130310 nightly.
Sent from my Xoom using Tapatalk HD
gapps won't flash after reflashing older nightly
kevk60 said:
After flashing latest CM 10.1 nightly (20130311) my tablet booted up but I got the message " Unfortunately System UI has stopped working". Rebooted into twrp recovery and flashed CM 10.1 20130310 nightly. Everything worked fine as usual. Tried flashing CyanDelta 20130311 update file and got the same message. Flashed back to CM 10.1 20130310 nightly again and everything was fine. Has anyone experienced this problem with the CM 10.1 20130311 nightly on Xoom wifi? I have flashed CM 10.1 20130311 nightly on both my GNex and my Nex 7 and have had no problems. Has anyone heard of any bugs with the Xoom CM 10.1 nightly (wingray)? Thanks.
Sent from my Xoom using Tapatalk HD
Click to expand...
Click to collapse
I had the same exact issue with my Xoom. I reflashed an older nightly and it's working again but now I can't get Gapps to flash properly. Every time it loads no gapps....????
I have tried reflashing the latest gapps 3 times now.
Anyone else have this issue or have Any suggestions? Running twrp if it matters but thinking of switching to CWM to try flashing gapps to see if it will take.
I use the team eos gapp pack for Xoom only. When I tried using other gapp packs my system ROM would be full and I could not update supersu. When I use the team eos for Xoom only gapps I found that I have about 30 mb left on my system ROM. My supersu was able to update then. I am using twrp 2.4.3.0 on my Xoom. Am running cm 10.1 20130310 and will stay there until a fix has been made. Do not know if this will help you, just wanted to let you know what has helped me. Are you wiping cache and dalvik before flashing gapps? I'm taking it you are flashing a previous build over the newest nightly.
Sent from my Nexus 7 using Tapatalk HD
kevk60 said:
I use the team eos gapp pack for Xoom only. When I tried using other gapp packs my system ROM would be full and I could not update supersu. When I use the team eos for Xoom only gapps I found that I have about 30 mb left on my system ROM. My supersu was able to update then. I am using twrp 2.4.3.0 on my Xoom. Am running cm 10.1 20130310 and will stay there until a fix has been made. Do not know if this will help you, just wanted to let you know what has helped me. Are you wiping cache and dalvik before flashing gapps? I'm taking it you are flashing a previous build over the newest nightly.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I did wipe both dalvik and cache before flashing gapps. I was using the gapps 20130301 so it could be that or maybe it's an older version of twrp that's causing the issue because I think I'm on 2.4.1.0.
I saw in another thread that I just read someone else was using a different gapps the gapps unified 20130220. I was thinking of giving that a try but I will try the one you recommended first as we both had the same issue above. I will also try flashing the new twrp to see if that's it as well.
Thanks I'll post back up later whether it worked or not.
If you have goo manager you could just update twrp from there.
Sent from my Xoom using Tapatalk HD
Looks like system ui bug issue has been fixed in the newest cm 10.1 nightly (20130314). Thanks to the devs.
Sent from my Xoom using Tapatalk HD
All,
I have an S3, i-535 that I have been trying out some different roms on. So far I've tried Paranoid Android 3.68, pacman 22.2.0 along with a pacman milestone build and aokp mr1_build 6 and in every rom the camera throws a "failed to connect" error. With PA i as able to use the camera with an app (mx or instagram, i can't remember), but the other roms it was completely non-functional.
I see other threads here about camera issues, but there aren't many that I can see that actually resolve the issue other than "install the latest cm". I'd really like to use PA, so is there any way to have a functioning camera with PA? Or pacman for that matter.
I should also note that I'm already on VRBMF1, the phone came from verizon on that version, so I'm assuming I don't have to do anything to the baseband... ?
Thanks
Try the latest AOKP nightly. I'm having no camera issues.
Sent from my SCH-I535 using Tapatalk 4 Beta
If I've helped, please hit the thanks button
success!! thank you!
Does anyone know why there is no Photosphere function on the CM12 nightlies?
I flashed the Lollipop firmware, followed by the latest CM12 nightlie. Photosphere force closes when using the Google camera app (and doesn't appear in any other camera app at all).
When I flash to the CM12s official release, Photosphere again works perfectly.
It cannot be firmware related as I updated firmware. This was done via clean wipes as well. From what I'm gathering, there's some difference in the CM12 Nightlies vs CM12s Official Release as related to Photosphere's functionality. I reflashed between the nightlie and official release twice to verify, and it was the same result each time - works fine in CM12s Official, Force Closes on CM12 Nightlie.
Anyone????
Hi guys,
some of you might know that there was a bug in the camera when using official CM12.1 nightly.
When you took a picture while using the flash the image was split into two parts. one brither part, one darker part. This was supposed to be a kernel / FW related issue with CM 12.1
Therefor I switched to CM12.1 nightly from SultanXDA, everything was fine there.
But since I am more the nightly type of person (he just continues the stable branch 12.1), I was wondering if someone could confirm me that in current official CM12.1 nightly the flash-camera bug is gone.
thnx a bunch
stefan
Still there on 31/08 nightly.
Hi.
I am new to this.
I am running RR for a while.
Every Time there's a new build up, dev instructs to flash latest CM NIGHTLY.
I was thinking - why not just run the Nightly build as a daily rom?
Am I missing something? Is it strictly for development purposes?
I am looking for rock solid stability mainly.
Thanks!
benyben123 said:
Hi.
I am new to this.
I am running RR for a while.
Every Time there's a new build up, dev instructs to flash latest CM NIGHTLY.
I was thinking - why not just run the Nightly build as a daily rom?
Am I missing something? Is it strictly for development purposes?
I am looking for rock solid stability mainly.
Thanks!
Click to expand...
Click to collapse
That's usually only recommended if there's a change in firmware in CM. It's not necessary to flash CM13 every time before flashing RR. I've never even used RR but I'm sure that's the only reason he would advise to flash CM.
Latest CM13 works great, rock stable at the moment so if you wanna switch go ahead
Sent from my A0001 using Tapatalk
CM nightlies contain firmware files in it. So what the dev wants is for you to update to the latest working firmware from CM nightly, and when you flash RR after, the firmware stays.