I flashed the latest official nightly for CM10 and sure it's pretty buggy, but the biggest thing to me that's really bothering me is the closing of the app or rebooting of my phone when I try to use the camera or video camera as well as apps related to them. Is there any current fix or should I just wait for an upcoming nightly?
Sent from my SCH-I535 using xda app-developers app
Fallen224 said:
I flashed the latest official nightly for CM10 and sure it's pretty buggy, but the biggest thing to me that's really bothering me is the closing of the app or rebooting of my phone when I try to use the camera or video camera as well as apps related to them. Is there any current fix or should I just wait for an upcoming nightly?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I have had no problems with the camera, or anything for that matter! did you do a clean install?
jfhanny said:
I have had no problems with the camera, or anything for that matter! did you do a clean install?
Click to expand...
Click to collapse
I came from stock! The only thing I didn't do is flash back to completely stock-right out of factory. But I had no other ROM's or anything!
Fallen224 said:
I came from stock! The only thing I didn't do is flash back to completely stock-right out of factory. But I had no other ROM's or anything!
Click to expand...
Click to collapse
Clean install means wiping data/cache/dalvik.
Well then I did that!
Sent from my SCH-I535 using xda app-developers app
I would try reflashing, or getting a slightly older nightly just to check. I haven't had any problem with the camera on CM10 for quite a few builds now.
Yeah, sorry dude, mine works fine too . Had it happen one time on the last build but its worked fine since then.
Rumor has it.....some people got a bad batch of gapps with gallery issues. Make sure you're on 7/26 gapps. Also some have said that wiping cache/data for gallery actually cleared the problem up too. Its pretty random the people with camera issues, but its definately a common thing still. See the cm10 official thread and there are a LOT of ideas about it floating around.
Did you restore anything strange with TiBackup or anything? It's a long shot, but I noticed after accidentally restoring a "system app" from GB to JB, it caused me some problems (wasn't a GSIII phone though). I wiped & reflashed ROM to fix my issues, but it sounds like you've done that well enough.
Does your camera not work immediately after flashing CM10?
Fallen224 said:
I flashed the latest official nightly for CM10 and sure it's pretty buggy, but the biggest thing to me that's really bothering me is the closing of the app or rebooting of my phone when I try to use the camera or video camera as well as apps related to them. Is there any current fix or should I just wait for an upcoming nightly?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
First thing I would do is a permissions repair. fixing permissions can iron out all kinds of little issues.
You can do it through rom manager but I've never trusted it to do much properly so I always do permissions repair through recovery.
So, I already had the latest version of Gapps, I fixed the permissions, cleared the data/cache of the gallery, and flashed the latest nightly "8/22" yet it still isn't working. It's a pity having such a great ROM with such a potentially large drawback. I'm very much still open to more suggestions! I have nowhere near the Linux literacy of a developer, but push me to try something out of the ordinary and I can figure it out with not too much help!
Related
I haven't posted enough in order to put this thread where it should be so I'll have to post this here.
This ROM was great until a day ago, when I tried to download a photo the download froze at loading andstarted jumping wierdly in my notif bar. I entered the Downloads app , and saw that it was changing from In Progress to Failed. Also, the camera does not work and it did not work since I flashed the ROM. Should I reflash the ROM or wipe the davlik cache ?
pzabet said:
I haven't posted enough in order to put this thread where it should be so I'll have to post this here.
This ROM was great until a day ago, when I tried to download a photo the download froze at loading andstarted jumping wierdly in my notif bar. I entered the Downloads app , and saw that it was changing from In Progress to Failed. Also, the camera does not work and it did not work since I flashed the ROM. Should I reflash the ROM or wipe the davlik cache ?
Click to expand...
Click to collapse
This ROM is not even at beta status. The camera does work really buggy, and at the moment they seem to wait for an official leak. nexx and nk111 are working on cm9 and already had some good success with camera, at least face unlock does work too. But since there is no official source code, the hardware acceleration for the camera is very buggy at all
Sent from my HTC Desire S using XDA App
eyahl said:
This ROM is not even at beta status. The camera does work really buggy, and at the moment they seem to wait for an official leak. nexx and nk111 are working on cm9 and already had some good success with camera, at least face unlock does work too. But since there is no official source code, the hardware acceleration for the camera is very buggy at all
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
Thank you for your answer, I just reflashed the ROM and now the camera and downloads work.
Thanks again
i got problem with 3G too, i can't turn on my 3G even i chose "on" Data, anybody help me
kUkHoi said:
i got problem with 3G too, i can't turn on my 3G even i chose "on" Data, anybody help me
Click to expand...
Click to collapse
I don't know about 3G, it always worked for me ( first flash and the second time 'round)
I sugest that you back up your apps and app data ( Titanium Backup) , wipe cache and data, and reflash the ROM
kUkHoi said:
i got problem with 3G too, i can't turn on my 3G even i chose "on" Data, anybody help me
Click to expand...
Click to collapse
Also if you get it right please reply 'cause I'm dying to know
pzabet said:
I don't know about 3G, it always worked for me ( first flash and the second time 'round)
I sugest that you back up your apps and app data ( Titanium Backup) , wipe cache and data, and reflash the ROM
Click to expand...
Click to collapse
And please reply to me if you manage to get 3G working and tell me how you did it
pzabet said:
I don't know about 3G, it always worked for me ( first flash and the second time 'round)
I sugest that you back up your apps and app data ( Titanium Backup) , wipe cache and data, and reflash the ROM
Click to expand...
Click to collapse
normally 3g works on rc3.
I'd suggest same, full wipe and reflash
Sent from my HTC Desire S using XDA App
I posted yesterday regarding some issues I was having with moving the Miui Camera APK to my system/app folder....
I got it all sorted in the end, I reflashed the RC3 rom and now everything works exactly as it should except for the fact that the camera will not work at all now, I always get the message Unfortunately Camera has Stopped.....
Any ideas?
Andy3105 said:
I posted yesterday regarding some issues I was having with moving the Miui Camera APK to my system/app folder....
I got it all sorted in the end, I reflashed the RC3 rom and now everything works exactly as it should except for the fact that the camera will not work at all now, I always get the message Unfortunately Camera has Stopped.....
Any ideas?
Click to expand...
Click to collapse
go to settings>applications
choose the camera and clear data
should solve your problem
btw try cm9 alpha, its one step ahead
Hey Guys! Had this problem too... but cleaning data in settings->applications won't helped me. I used to clean cache & dalvik cache in Recovery... try to do this
mizerok said:
Hey Guys! Had this problem too... but cleaning data in settings->applications won't helped me. I used to clean cache & dalvik cache in Recovery... try to do this
Click to expand...
Click to collapse
same here and it dident work for me anymore, others methodes
eyahl said:
This ROM is not even at beta status. The camera does work really buggy, and at the moment they seem to wait for an official leak. nexx and nk111 are working on cm9 and already had some good success with camera, at least face unlock does work too. But since there is no official source code, the hardware acceleration for the camera is very buggy at all
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
am i supposed to say anything more??
Thanks, I got it all sorted and also giving CM9 a spin.
Camera seems good but no flash?
Sent from my Desire S using XDA App
Andy3105 said:
Thanks, I got it all sorted and also giving CM9 a spin.
Camera seems good but no flash?
Sent from my Desire S using XDA App
Click to expand...
Click to collapse
yep
But the most torch apps from market do work
Sent from my HTC Desire S
My phone was running Virtuous quattro and the apn worked fine for me except the front cam but now i use MIUI and the front cam works too
Sorry if this has been posted somewhere else, but after flashing AOKP Build 3 my camera keeps giving me the error "cannot connect to camera." I have tried clearing data on the gallery app, rebooting the phone, and nothing works.
I researched some and tried some fixes I found but none had any effect.
I then reflashed to stock to see if stock Touchwiz would work and it works with no issues. Wiped all data, reformatted my SD card, removed my SD card and cannot seem to find the culprit. I also flashed CM nightly to see if it was an AOKP issue with my phone, but had same issue
For whatever reason I cannot flash any AOSP rom without having FC on my camera. Any help would be appreciated. Again, sorry if it has been posted somewhere I haven't found, but I've looked for a few days and didn't locate anything that worked.
Did you try fixing permissions?
Zalithian said:
Did you try fixing permissions?
Click to expand...
Click to collapse
Do that and also format cache and dalvik.
shinjielric said:
Do that and also format cache and dalvik.
Click to expand...
Click to collapse
Did all of those and still no change in outcome.
MistarJones said:
Did all of those and still no change in outcome.
Click to expand...
Click to collapse
What version of CWM are you using? I've heard some versions don't play nice with AOSP.
EDIT: I'm assuming you're using CWM.
You happen to try a different camera from the play store? My quess is it wouldnt work either as its probaly a kernel issue?
Sent from my SCH-I535 using xda app-developers app
shinjielric said:
What version of CWM are you using? I've heard some versions don't play nice with AOSP.
EDIT: I'm assuming you're using CWM.
Click to expand...
Click to collapse
I am using las test, CWM touch. Could try with non touch after work.
x714x said:
You happen to try a different camera from the play store? My quess is it wouldnt work either as its probaly a kernel issue?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Yeah I tried with several camera alternatives and all said couldn't connect to camera as well. :/
this happened to me randomly yesterday on CM10 M1, I'm on leankernal and using twrp. I had just flashed the aosp camera mod earlier so I thought it was that. I just restored a backup I made the other day and it was all good since. I guess its a good reason to make routine backups on aosp
DertyDOH said:
this happened to me randomly yesterday on CM10 M1, I'm on leankernal and using twrp. I had just flashed the aosp camera mod earlier so I thought it was that. I just restored a backup I made the other day and it was all good since. I guess its a good reason to make routine backups on aosp
Click to expand...
Click to collapse
I tried that and any backup still having camera FC issues.
Originally Posted by shinjielric
What version of CWM are you using? I've heard some versions don't play nice with AOSP.
EDIT: I'm assuming you're using CWM.
Click to expand...
Click to collapse
I am using las test, CWM touch. Could try with non touch after work.
Click to expand...
Click to collapse
I'm using cwm touch v6.0.1.2 and its working good for me.
Sent from my SCH-I535 using xda premium
I've had the same issue and reflashed multiple times and tried all the above.
My Galaxy III SCH-I535 operates on Android 4.1.2 aokp_d2vzw_jb_milestone_1
Kernel is 3.0.48-cynagenmod-faux123-vzw...
I love this ROM. I'm not sure how it randomly a day or two into operation just quit the camera operation completely. This would be a real miracle solved
MistarJones said:
Sorry if this has been posted somewhere else, but after flashing AOKP Build 3 my camera keeps giving me the error "cannot connect to camera." I have tried clearing data on the gallery app, rebooting the phone, and nothing works.
I researched some and tried some fixes I found but none had any effect.
I then reflashed to stock to see if stock Touchwiz would work and it works with no issues. Wiped all data, reformatted my SD card, removed my SD card and cannot seem to find the culprit. I also flashed CM nightly to see if it was an AOKP issue with my phone, but had same issue
For whatever reason I cannot flash any AOSP rom without having FC on my camera. Any help would be appreciated. Again, sorry if it has been posted somewhere I haven't found, but I've looked for a few days and didn't locate anything that worked.
Click to expand...
Click to collapse
Did you ever get this resolved? I'm having the exact same issue and would love to get it fixed.
re fix
bandit2443 said:
Did you ever get this resolved? I'm having the exact same issue and would love to get it fixed.
Click to expand...
Click to collapse
I wasn't able to get it to fix. I came to the conclusion that it was a hardware issue. For whatever reason it works on touchwiz but wouldn't work on aosp ROMs. I got a warranty replacement and it solved the issue. Wasn't able to find a software fix.
MistarJones said:
I wasn't able to get it to fix. I came to the conclusion that it was a hardware issue. For whatever reason it works on touchwiz but wouldn't work on aosp ROMs. I got a warranty replacement and it solved the issue. Wasn't able to find a software fix.
Click to expand...
Click to collapse
Oh wow... that's an idea i hadn't thought of. Samsung replaced it under warranty? What did you tell them was wrong with it?
Camera Can't Connect & Firmware
shinjielric said:
I'm using cwm touch v6.0.1.2 and its working good for me.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I am having the "cannot connect" issue on CM10. I posted about it here: http://forum.xda-developers.com/showthread.php?t=2152348
The camera works fine in stock, but on CM10 no-go. According to this post its a firmware issue: http://forum.xda-developers.com/showthread.php?t=2006128
only problem is to fix I need to figure out what camera firmware I have so I can flash a new one - but I cannot determine what firmware i535 has? Anyone?
Based on another thread, seems like I might be able to copy the bins from the cameradata folder on stock where the camera works. No need to flash or anything.
http://forum.cyanogenmod.org/index.php?/topic/66022-Can't-Connect-To-Camera
Sent from my SCH-I535 using xda app-developers app
Ok...I had the CM9 Rom from erickmm and it was acting up so I decided to restore my Rom that I backed up which was the detoxed stock GB Rom from thazz and the same auto rotation problem that was on the cm9 Rom is now on the stock Rom. What should I do?
Sent from my SGH-T769 using xda app-developers app
Mr.Wellington said:
Ok...I had the CM9 Rom from erickmm and it was acting up so I decided to restore my Rom that I backed up which was the detoxed stock GB Rom from thazz and the same auto rotation problem that was on the cm9 Rom is now on the stock Rom. What should I do?
Sent from my SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
Did you do complete factory reset, wipe cache, wipe dalvik?
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
jparnell8839 said:
Did you do complete factory reset, wipe cache, wipe dalvik?
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
I'm kinda curious about this too. I ran an I577 build of CM10 for those folks, and they're experiencing this bug too.
Yep. Full clean before I restored. Was I suppose to do it again afterwards too?
Sent from my SGH-T769 using xda app-developers app
Mr.Wellington said:
Yep. Full clean before I restored. Was I suppose to do it again afterwards too?
Sent from my SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
I always over wipe, coming from HTC to Samsung. I always do those 3 steps before flashing and after flashing. A fix permissions street flash might help to
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
jparnell8839 said:
I always over wipe, coming from HTC to Samsung. I always do those 3 steps before flashing and after flashing. A fix permissions street flash might help to
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
Appreciate the advice. I've tried theses steps multiple times now to no avail. At first, I thought this was a hardware issue but now it seems many others are experiencing this. I've also tried the ROM from thazz and the CM9, as the OP. Now, my auto rotate is jacked up no matter what ROM I try. I've tried restoring the stock from t-mobile and the auto rotate is still broke. Ugghh. Looking forward to a fix...
Mr.Wellington said:
Ok...I had the CM9 Rom from erickmm and it was acting up so I decided to restore my Rom that I backed up which was the detoxed stock GB Rom from thazz and the same auto rotation problem that was on the cm9 Rom is now on the stock Rom. What should I do?
Sent from my SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
What exactly is your auto rotation problem? Mine is that once the screen goes to landscape, it won't go back to portrait. Along with that, rotation lags seriously, depending on the ROM. Right now, Blazr works the best for the rotation lag. The screen still won't go vertical once its in landscape, but rotation response is quick to landscape.
Idk if it'll help but maybe try flashing cm10 and calibrating g sensor or whatever it is when u lay it flat and calibrate its in settings somewhere maybe that will help
Just my 2 cents
Sent from my SAMSUNG-SGH-T769 using Tapatalk 2
dr4stic said:
I'm kinda curious about this too. I ran an I577 build of CM10 for those folks, and they're experiencing this bug too.
Click to expand...
Click to collapse
I haven't had any rotation problems out of your cm10 builds. The only problems I had were the random reboots but since you released the most recent build I have had no problema
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
glock12 said:
Appreciate the advice. I've tried theses steps multiple times now to no avail. At first, I thought this was a hardware issue but now it seems many others are experiencing this. I've also tried the ROM from thazz and the CM9, as the OP. Now, my auto rotate is jacked up no matter what ROM I try. I've tried restoring the stock from t-mobile and the auto rotate is still broke. Ugghh. Looking forward to a fix...
Click to expand...
Click to collapse
have u fixed it yet
having the same issue for 2months n aw
phedes1 said:
have u fixed it yet
having the same issue for 2months n aw
Click to expand...
Click to collapse
There is a flashable zip... somewhere in the t989 forums that is a fix to this. Sorry, Don't have the link. :/ It actually says rotation fix. It has worked for me in those times.
theprogram1 said:
There is a flashable zip... somewhere in the t989 forums that is a fix to this. Sorry, Don't have the link. :/ It actually says rotation fix. It has worked for me in those times.
Click to expand...
Click to collapse
fanks man, will search it out and see
is about the yamaha thin g
be careful though.. about what you install D: Don't brick your device. Just format system and data (after backing up) and install a rom.. see if that works first
Before I flash a new ROM ,I always format system in recovery (mounts and storage) then I wipe data ,cache,etc. Haven't had any issues with rotation or anything else to speak of. Good luck and as the other user said,be careful with what you flash or install.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
flyers00 said:
Before I flash a new ROM ,I always format system in recovery (mounts and storage) then I wipe data ,cache,etc. Haven't had any issues with rotation or anything else to speak of. Good luck and as the other user said,be careful with what you flash or install.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
i do appreciate ur efforts tryin g to help
am a noob and don t ave much ideas about this
but i got dis won derful phone from ma dad which was already on 2.3.6
and was alreadi aving the acceleromter isses
but i managed to get it to cyanogens stable 4.1.2 hoping to fix it but null
a detailed instruction wil reali help me
thanks in advance
flyers00 said:
Before I flash a new ROM ,I always format system in recovery (mounts and storage) then I wipe data ,cache,etc. Haven't had any issues with rotation or anything else to speak of. Good luck and as the other user said,be careful with what you flash or install.
Click to expand...
Click to collapse
I also lost auto-rotation functionality after installing CyanogenMod version 10.0.0 on my Galaxy S Blaze, even though "Auto-rotate screen" is checked under Settings --> Display. I'd be happy to try flyers00's suggestion about formatting before re-flashing, but I want to be sure I'm selecting the correct options in ClockworkMod. CWM's format options are: data, system, cache, emmc, sdcard and sd-ext. Which of these should I format?
Thanks.
tweaksall said:
I also lost auto-rotation functionality after installing CyanogenMod version 10.0.0 on my Galaxy S Blaze, even though "Auto-rotate screen" is checked under Settings --> Display. I'd be happy to try flyers00's suggestion about formatting before re-flashing, but I want to be sure I'm selecting the correct options in ClockworkMod. CWM's format options are: data, system, cache, emmc, sdcard and sd-ext. Which of these should I format?
Thanks.
Click to expand...
Click to collapse
Flash a Cyanogenmod Nightly. There more stable than 10.0.0
xWolf13 said:
Flash a Cyanogenmod Nightly. There more stable than 10.0.0
Click to expand...
Click to collapse
Thanks for your quick reply, xWolf13. I've been hesitant to go this route because, according to the folks at CyanogenMod, Nightlies "are as volatile as a firmware can get," and are "not meant for use for an average user."
(But I might eventually try it if I become frustrated enough with this issue.)
tweaksall said:
Thanks for your quick reply, xWolf13. I've been hesitant to go this route because, according to the folks at CyanogenMod, Nightlies "are as volatile as a firmware can get," and are "not meant for use for an average user."
(But I might eventually try it if I become frustrated enough with this issue.)
Click to expand...
Click to collapse
Nightlies are not necessarily volatile, there just maybe some things broken and some things fixed between updates. Most of the time there are no issues. On the blaze the old stable is not something any one will recommend, the latest nightly is the way to go.
Also, just a note, that most of the time there is an auto rotate setting on the launcher that is separate than the system wide auto rotate, same with other apps.
tweaksall said:
I also lost auto-rotation functionality after installing CyanogenMod version 10.0.0 on my Galaxy S Blaze, even though "Auto-rotate screen" is checked under Settings --> Display. I'd be happy to try flyers00's suggestion about formatting before re-flashing, but I want to be sure I'm selecting the correct options in ClockworkMod. CWM's format options are: data, system, cache, emmc, sdcard and sd-ext. Which of these should I format?
Thanks.
Click to expand...
Click to collapse
You can select format system. Sorry I didn't get back to you sooner, work has been nuts
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
I was hoping anyone here could relate to the problem my brother and I are having with pretty much all AOSP ROMs. Every time we install an AOSP ROM after even completely wiping everything except ext SD, after about an hour of run time to smoothness of the ROM goes away. The pull down is all choppy as well as scrolling the home screens. A reboot fixes it temporarily for around a minute or so and it goes back. We did find one AOSP nightly from the 15th that remained smooth but that was it.
If anyone has any ideas what could be causing this I would be eternally thankful. We have searched up and down and can't believe no one else is complaining of this. This is happening on both of our devices where pretty much the only similarity is that we use TWRP and update it regularly.
Thanks again for any advice you can provide.
Sent from my SCH-I535 using xda premium
I've had this same exact problem. I believe you meant the AOKP build from the 15th as that was the one that has remained smooth (but had some other bugs) for me. Seems like nobody else is having this problem.
Sent from my SCH-I535 using xda premium
Gordon Ramsay said:
I was hoping anyone here could relate to the problem my brother and I are having with pretty much all AOSP ROMs. Every time we install an AOSP ROM after even completely wiping everything except ext SD, after about an hour of run time to smoothness of the ROM goes away. The pull down is all choppy as well as scrolling the home screens. A reboot fixes it temporarily for around a minute or so and it goes back. We did find one AOSP nightly from the 15th that remained smooth but that was it.
If anyone has any ideas what could be causing this I would be eternally thankful. We have searched up and down and can't believe no one else is complaining of this. This is happening on both of our devices where pretty much the only similarity is that we use TWRP and update it regularly.
Thanks again for any advice you can provide.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
The reason people aren't complaining is because they haven't had that problem yet. The only thing I can tell you is when flashing ROMs make sure you completely wipe 2-3 times as for some reason with TWRP you have to do that to get some ROMs to work.
jmxc23 said:
The reason people aren't complaining is because they haven't had that problem yet.
Click to expand...
Click to collapse
Thank you for the wonderful insight. But in all seriousness I wonder what is causing it for us.
Sent from my SCH-I535 using xda premium
voltage526 said:
Thank you for the wonderful insight. But in all seriousness I wonder what is causing it for us.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
please read my edited post. I will also add that when flashing ROMs the results are very random even with the most stable of ROMs.
jmxc23 said:
please read my edited post.
Click to expand...
Click to collapse
Thank you. I wipe everything 2-3 times by habit though.
Sent from my SCH-I535 using xda premium
voltage526 said:
Thank you. I wipe everything 2-3 times by habit though.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Yes I wipe 3x and then use zips that wipe again.
then you guys might have to switch CWM recovery as I flashed most of the AOSP ROMs with no problems.
jmxc23 said:
then you guys might have to switch CWM recovery as I flashed most of the AOSP ROMs with no problems.
Click to expand...
Click to collapse
You really don't have any stuttering whatsoever with AOSP roms? Hmm.
I would think though if it was TWRP wouldn't a lot more people be having this problem? I will try CWM though.
Just wanted to update the thread. We have tried switching recoveries to CWM, also tried running the rom with absolutely nothing but Gapps. Same result after a few hours. This is on two completely separate devices, we can't be the only ones. Any additional advice would be really appreciated. This is driving us crazy!
I get pretty bad lag on carbon rom, flashing with CWM. Any other aosp rom runs fine but carbon seems to not like my phone
Sent from my SCH-I535 using xda premium
Carbon was the worst so far for me as well.
That goes with the fact not everyone will have the same results when flashing ROMs.
I flashed over to CarbonRom yesterday and everything was working properly except for the camera. When I tired to go into the camera I'd get a message "Can't connect to camera" and then the application would close out. I'm back to running CM 10.1.2-d2vzw and the camera works fine there.
Anyone else run into this issue or have a fix? I searched quite a bit and found a lot of threads related to the camera firmware but CM works fine.
Thanks
ffeingol said:
I flashed over to CarbonRom yesterday and everything was working properly except for the camera. When I tired to go into the camera I'd get a message "Can't connect to camera" and then the application would close out. I'm back to running CM 10.1.2-d2vzw and the camera works fine there.
Anyone else run into this issue or have a fix? I searched quite a bit and found a lot of threads related to the camera firmware but CM works fine.
Thanks
Click to expand...
Click to collapse
1.7 is pretty old. Try flashing a nightly. It will work 100%!
Sent from my SCH-I535 using xda app-developers app
Any particular nightly know to be good? I've always stayedaway from the nightly as you seem to always get the disclaimer that 'something could be broken' since new code is rolling in.
Thanks
ffeingol said:
Any particular nightly know to be good? I've always stayedaway from the nightly as you seem to always get the disclaimer that 'something could be broken' since new code is rolling in.
Thanks
Click to expand...
Click to collapse
The latest should be fine. I'm personally on July 4th with no issues.
Sent from my SCH-I535 using xda app-developers app
I flashed to nightly last night and everything seems to be working fine now. Time to customize and play.
ffeingol said:
I flashed to nightly last night and everything seems to be working fine now. Time to customize and play.
Click to expand...
Click to collapse
Sweet!
Sent from my SCH-I535 using xda app-developers app