• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Boost Mobile] Official CyanogenMod 11 Nightlies!

I'm having camera issues. It freezes after I take a picture. Any body else have this problem? Is there a fix

This issue just started popping up on XDA as well for 12/12 and 12/13 builds. Just tried mine with same result of freeze after one picture. Going to test out some third party cameras and see what happens.
 
OK do this: download Cymera from Play Store. Go to Settings/Apps/All, choose Camera (default app) clear data, accept warning, then reboot. Cymera won't be able to connect if you don't do this. Just took multiple pix, no freezing, and seems like a pretty sweet app in general!
 
Yea I am. I figured out something else...it says Invalid path... But if I use the cm11 my files app I can access it

Have you enabled the Root Explorer option in ES and allowed it to have Superuser/root access? This could be the issue as well. I use ES and have this option enabled, and have no problem accessing external storage.
 
Ended up having to go back to stock yet again as there were too many issues with it. From the pains of trying to get everything working as far as data,WiFi,mms, ext and in top of that the camera deciding it wanted to act up. I'll still keep trying builds and uploading nightlies along with yours struckn to keep this thread going.
 
Ended up having to go back to stock yet again as there were too many issues with it. From the pains of trying to get everything working as far as data,WiFi,mms, ext and in top of that the camera deciding it wanted to act up. I'll still keep trying builds and uploading nightlies along with yours struckn to keep this thread going.

Thanks for the input my friend! Sorry it's giving you grief, my phone is doing well with it. These are the early days of official CM11 for sure, should be real solid and consistent hopefully sooner rather than later. Appreciate all your helpfulness with this thread too.
 
That is such a good point, I hadn't thought about it from that angle. They may claim it is invincible once tripped all they want as well, but since it was made by man it can be defeated by man as well. There is no such thing as 100% irreversible, short of taking a baseball bat to the phone.

This is definitely going to be interesting to follow and see where and how far it actually goes. Well, to see how far Samsung allows the public to see how far it goes anyways. :rolleyes:

Shhhh...... can u hear that??? Shhhh..... there it is again!! WTH?? AH HAH!! it's the bed calling my name is all. lmao! :p Looks like it's time to fire up the S3 and crawl in a nice warm bed. :D

Speaking of the S3, I'm sure curious about this new CyanogenMod. I have yet to try it but I'm a die hard CM guy. If a fully stable build is available it's what I'll end up running. I always do. I've got it on my TF300T and love it. CM7 hooked me back in my Prevail days. Thanks to Hroark and his hard work, I ran CM7 for the majority of the time I had the Prevail activated. That and Bloodawn's CTMod. Can't forget Kouma either. That cat has got some serious kernel skills for sure! I think back on my early days learning about Android and realize just how very lucky the Prevail section was to have so many awesome developers. LMAO!!!! I was one of the 1st to run ShabbyMod by ShabbyPenguin. Those were some good days man. :D

Shhhh.... there it is again! LMAO!!!! To bed I say! ;):p
 
Sleep tight my friend! Newest CM (official CM 11) has been running on my phone the last week straight, it's AWESOME! Unbelievable for a nightly. I know some people have had a lot of issues, like APOPHiS420 here on the forums, but for me it has been like an early Christmas gift.
 
Sleep tight my friend! Newest CM (official CM 11) has been running on my phone the last week straight, it's AWESOME! Unbelievable for a nightly. I know some people have had a lot of issues, like APOPHiS420 here on the forums, but for me it has been like an early Christmas gift.

I'm back up. I swear man.... that chemo ruined my internal clock. Just burnt it right up I guess.

Thanks for the info about CM. Usually I would say that I have a feeling I'll be trying it before long but I know me and I know better. It'll be flashed within the next few days. Hell bro, maybe even this afternoon! Lmao. :eek::D
 
OK. Which is the best build to flash? Your modded version or one of the new nightlies?

Is everything functional with your modded version?

Hope to get an answer soon. Gonna flash this or Beanstalk very ASAP. Just trying to get some 4 11 1st . :D
 
OK. Which is the best build to flash? Your molded version or one of the new nightlies?

Is everything functional with your modded version?

Hope to get an answer soon. Gonna flash this or Beanstalk very soon. :D

The 12/12 modded I posted has been great for me. There's no Apollo or email or live wallpapers. GApps I used are slightly debloated as well but nothing that can't be downloaded from Play Store if needed. Using latest dkp 4.4 kernel as well.
 
Bump. Edited previous post with needed info. Thanks.

Duh... Please disregard the modem question. I read the earlier post and see the it's not needed. Still, the comment about enforcing to permissive threw me for a loop. Is there something extra I need to do or just flash this baby?
 
Bump. Edited previous post with needed info. Thanks.

Duh... Please disregard the modem question. I read the earlier post and see the it's not needed. Still, the comment about enforcing to permissive threw me for a loop. Is there something extra I need to do or just flash this baby?

Your question is still useful for anyone else reading this.

1. Modem is personal choice. Also remember modem does not equal bootloader, it is just a way to access phone service and data. I am currently using MK5, MG2 was solid as well, and I have used the MK3 from Sprint no problem.

2. SELinux was introduced in 4.3, and was set to "Permissive" by default. In 4.4, the default is "Enforcing," which can mess with some root apps and their functionality unless it is manually set back to "Permissive." Think of it as Google's very light version of Knox, I can't think of any other comparison right now. My attempt to modify build.prop didn't stick, and I think this is an intentional design issue to prevent direct modification, as I have read about others having the same issue. To manually change: Open Terminal Emulator, and give it root access with the command "su" (don't use quotes), followed by the enter key. On the next line you will see it starts with # instead of $, this means root has been granted. On that next line, type "setenforce 0" (again, no quotes, and that is a zero not the letter O; this is just basic 0 or 1 meaning true or false in computer-land) and then hit enter key again. Make sure to close the program entirely after that or it will run in the background and consume battery. This has to be done after every reboot due to "Enforcing" being part of the build.prop.

SELinux has only given me problems a couple of times, so this is just more of a nerd thing than anything else, but I always feel there is no such thing as too much knowledge.
 
So long story short, flash away my friend! Hopefully APOPHiS420's experience was the exception and not the norm for the Boost side, I think Rally517 got good results with this, but not sure.
 
Your question is still useful for anyone else reading this.

1. Modem is personal choice. Also remember modem does not equal bootloader, it is just a way to access phone service and data. I am currently using MK5, MG2 was solid as well, and I have used the MK3 from Sprint no problem.

2. SELinux was introduced in 4.3, and was set to "Permissive" by default. In 4.4, the default is "Enforcing," which can mess with some root apps and their functionality unless it is manually set back to "Permissive." Think of it as Google's very light version of Knox, I can't think of any other comparison right now. My attempt to modify build.prop didn't stick, and I think this is an intentional design issue to prevent direct modification, as I have read about others having the same issue. To manually change: Open Terminal Emulator, and give it root access with the command "su" (don't use quotes), followed by the enter key. On the next line you will see it starts with # instead of $, this means root has been granted. On that next line, type "setenforce 0" (again, no quotes, and that is a zero not the letter O; this is just basic 0 or 1 meaning true or false in computer-land) and then hit enter key again. Make sure to close the program entirely after that or it will run in the background and consume battery. This has to be done after every reboot due to "Enforcing" being part of the build.prop.

SELinux has only given me problems a couple of times, so this is just more of a nerd thing than anything else, but I always feel there is no such thing as too much knowledge.


So long story short, flash away my friend! Hopefully APOPHiS420's experience was the exception and not the norm for the Boost side, I think Rally517 got good results with this, but not sure.

Excellent explanation bro. Thank you for breaking it down specifically for me. I have a good grasp on what's taking place now.

Yup just as I thought, I'm behind with the newer builds and what's been added, removed, added again, and then modified. LOL. Thanks for the specific Terminal Emulator instructions. I've used TE many time but it's worthless w/o the proper cmds. Very easy fix, just a minor inconvenience is all. Well worth the 15 second fix to be running the new CyanogenMod imo.
Hopefully it will not be an issue as you mentioned. If it is, I am now well equipped, thanks to you, with the information needed to disabled it.

Time to make a backup and give this baby a try.
Thanks again bro. :) I'll report back in a little while if the wife doesn't catch me 1st. LOL. :eek:
 
Back
Top Bottom