Develop Bugs

[Q] Anything other than a TW and my camera just wont work, Help?

Hi there!
I have had an s3 for a few days now and love it!.
Any TW rom and my camera works just fantastic.
Any cm10/aokp/miui/etc rom and I just cant use the camera no matter what app I use to try it, whether it be the built in app or camera360/etc.
Driving me nuts and would love someone to help me. Anyway research I have done hasnt told me what I'm doing wrong.
I wipe cache/dalvik/factory reset/system before each rom. I have tried different kernels but nothing has helped.
Any gurus out there have any ideas on what I can do to fix this?

Your install process would be and please link the files you are flashing... I'll try and help you. I've seen a few people mention this the past couple days.

The most recent I tried to flash was Illusion v1.1.18 - (d2tmo, d2att & d2vzw) - 1|18|13 from this thread:
http://forum.xda-developers.com/showthread.php?t=2037028
I downloaded Illusion-v1.1.18-d2tmo.zip and gapps-jb-20121212-signed.zip.
I went into recovery which is twrp and the most recent version. I installed it with the goo.im app.
When in recovery I did:
1) Factory Wipe
2) Wipe Cache
3) Wipe Dalvik
4) Wipe System
I would then click Install and select the rom file, and after it succesfully flashed I would then flash the gapps file. All were successful.
I would then reboot and the rom would boot up fine. I setup my google account and all that then for the heck of it I would reboot.
I then would try the camera app and it would complain that it couldnt connect to the camera basically. I went into the play store and tried a free version of camera 360, puddle camera, etc and all would not work.
I went back into recovery, wiped cache and dalvik again, hopped on one foot, faced east, and clicked my heels together. Upon reboot the camera does not work.
I have wiped all that and tried to install [Kernel][JB] Leankernel: Minimalistic Kernel for D2TMO/D2ATT (AOSP) v2.3 [1/17/13] which flashed fine. Upon reboot I could change voltages to undervolt, mess with governors but cameras still do not work.
I have a backup of two TW roms (one stock) and both of the those roms work beautifully with whatever camera I try, including the built in/stock camera.
I hoped I didn't leave out something. If there is something I missed than I'm an idiot because it seems like I am really missing something.
Thanks for your help.

I don't see any reason your steps lead to that, the exact steps I take every time to flash. I'm researching but in the mean time, go to app manager and wipe cache and data from gallery... Are you using the same Gapps over and over on each try? Might wanna try a different set.

mt3g said:
I don't see any reason your steps lead to that, the exact steps I take every time to flash. I'm researching but in the mean time, go to app manager and wipe cache and data from gallery.
Click to expand...
Click to collapse
I did that earlier with no luck.
I just force stopped on gallery, wiped cache/data, rebooted, and I tried the camera only to get the same message.
Thank you for that tip but I will continue my research also.
Just because I looked at about phone.
Model of phone is SGH-T999 (just in case someone thinks I'm in the wrong forum"
Baseband version is T999UVDLJA
Kernel is of course 3.0.59-leanKernel
AOKP Version is Illusion v1.1.18 d2tmo
Build number is aokp-d2tmo-userdebug 4.2.1 (I truncated the rest)

mt3g said:
Are you using the same Gapps over and over on each try? Might wanna try a different set.
Click to expand...
Click to collapse
I have downloaded this gapps twice for the last rom http://goo.im/devs/itsmikeramsay/gapps-jb-20121212-signed.zip.
For the miui rom there was a gapps that was specific to miui and had miui in the name. The miui rom's camera didnt work.
I'll look for a different gapps if that might be the problem but since I have tried a couple roms and a few different gapps I feel that might not be the issue.
I still will give it another try though. Just have to find another gapps to try.

try these just in case they're corrupted. http://d-h.st/dtk these are the ones I use

mt3g said:
try these just in case they're corrupted. http://d-h.st/dtk these are the ones I use
Click to expand...
Click to collapse
I redid the entire install process from scratch using that gapps and the camera is still not working.
Ugh. Thanks for the link.
WIll keep trying :/

run a log cat and post it. Other then that maybe bad firmware...
did you update your phone to stock JellyBean via Over the Air or Odin? it updates the partitions which could be the issue, mmayyybbeee???!?!? Shots in the dark right now, just trying to help as I've never seen this issue before solved.

mt3g said:
run a log cat and post it. Other then that maybe bad firmware...
did you update your phone to stock JellyBean via Over the Air or Odin? it updates the partitions which could be the issue, mmayyybbeee???!?!?
Click to expand...
Click to collapse
It had JB on it when I got it almost 2 days ago. I tried to do an OTA when I got it but it said I was up to date.
Let me do a restore to stock and see what version it is.
Edit: Restored stock. Says android version 4.1.1, Kernel 3.0.31-370274se.infra, Build number JR003L.T999UVDLJA

Was it already rooted?
Sent from my SGH-T999 using xda premium

mt3g said:
Was it already rooted?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
It was new, out of the box. I watched the guy unrap it. It is one of the newer grey metal color looking ones. It was not rooted. I did that. Should I do an Odin to bring the device back to complete stock and start from scratch?
Will take a while since I have no idea where to start with all that

Thats the best suggestion I have. Maybe someone else will step in with an idea.
Sent from my SGH-T999 using xda premium

mt3g said:
Thats the best suggestion I have. Maybe someone else will step in with an idea.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
You have been helpful. In a bit ill reflash a cm/aokp rom and logcat it.

This is happening a couple of threads above you haha http://forum.xda-developers.com/showthread.php?p=36899130
Sent from my SGH-T999 using xda premium

mt3g said:
This is happening a couple of threads above you haha http://forum.xda-developers.com/showthread.php?p=36899130
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Hey thanks again for your help. I ended up falling asleep but installed Wicked V6 (tw based rom) and liking it enough that I will wait on a aokp/cm10.x rom until I get up the motivation to try again.
I'm sure I'll get an itch for a different rom in about a week though

dccoh said:
Hey thanks again for your help. I ended up falling asleep but installed Wicked V6 (tw based rom) and liking it enough that I will wait on a aokp/cm10.x rom until I get up the motivation to try again.
I'm sure I'll get an itch for a different rom in about a week though
Click to expand...
Click to collapse
All good, just hope the thread I pointed to will work out once you do want to give it another go.
Sent from my SGH-T999 using xda premium

mt3g said:
All good, just hope the thread I pointed to will work out once you do want to give it another go.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I backed up Wicked and loaded up my original rom that I wanted to try.
The fix in the said thread fixed me right up, camera works fine.
All this trouble because of one 350ish kb file
Thanks for checking on my issue.

dccoh said:
I backed up Wicked and loaded up my original rom that I wanted to try.
The fix in the said thread fixed me right up, camera works fine.
All this trouble because of one 350ish kb file
Thanks for checking on my issue.
Click to expand...
Click to collapse
Most definitely sir. I don't understand why that file was getting screwed over. Glad it all got worked out for you.
Sent from my SGH-T999 using xda premium

JellyBAM v7.0.0 boot not working for galaxy s3? FIX HERE!!

Hello everyone,
After trying to install JellyBAM v7.0.0, my phone would not boot. This was extremely frustrating, as jellybam is one of my favorite ROMS. The issue was with the kernel that came in the zip with the ROM.
This issue can be fixed one of two ways:
1. Dirty flash from v6.7.0
Have v6.7.0 already installed
-Wipe Cache
-Wipe Dalvik
Install from zip v7.0.0
2. Clean flash with different kernel
-Wipe Data
-Wipe Cache
-Wipe Dalvik
-Format System
-Install from zip v7.0.0
-Install your favorite kernel
I am currently running BMS kernel and it is working fine, but any kernel for 4.2.2 will do
Enjoy!

bump

Pretty sure jellybam ROMs are banned...
Sent From My Rooted, S-OFF'd Blackberry Curve using the iOS XDA Application for Android.

This didn't work for me. What worked was restoring just the BOOT from my previous 6.7.0. install (via advanced restore from CWM). Thanks though,

asaa said:
This didn't work for me. What worked was restoring just the BOOT from my previous 6.7.0. install (via advanced restore from CWM). Thanks though,
Click to expand...
Click to collapse
No reason this shouldn't work for you..

just tried flashing 7.0 and it failed might try downloading again later
Sent from my SCH-R530U using Tapatalk 2

trvbone said:
just tried flashing 7.0 and it failed might try downloading again later
Sent from my SCH-R530U using Tapatalk 2
Click to expand...
Click to collapse
Did you try one of the methods in the OP?

asaa said:
This didn't work for me. What worked was restoring just the BOOT from my previous 6.7.0. install (via advanced restore from CWM). Thanks though,
Click to expand...
Click to collapse
The only thing that wouldve changed it from the previous boot.img is the kernel
Maybe they changed the kernel between versions and it got messed up on v7

CNexus said:
The only thing that wouldve changed it from the previous boot.img is the kernel
Maybe they changed the kernel between versions and it got messed up on v7
Click to expand...
Click to collapse
You are correct. Its not that people are needing to redownload or something, the kernel that comes with the ROM is just broken. The dirty flash will keep the kernel from 6.7 and the clean flash with a seperate kernel will both solve this issue.

I'm on us cellular S3 I can't find 6.70 for my phone, I couldn't get it to even start flashing the zip. So option number 2 is not an option Lol
Sent from my SCH-R530U using Tapatalk 2

Amizzly said:
You are correct. Its not that people are needing to redownload or something, the kernel that comes with the ROM is just broken. The dirty flash will keep the kernel from 6.7 and the clean flash with a seperate kernel will both solve this issue.
Click to expand...
Click to collapse
I know, I was just posting that for his/her benefit because he/she seemed to have misunderstood it

I used the dirty flash version and it worked perfectly. Only one problem. It started out with my WiFi working. Then it stopped. I am in a place with free WiFi and i can not even turn WiFi on. Am i doing something wrong or is there an easy fix? I do appreciate everything that is shared here. Also thanks for the fix to get JellyBam 7.0 to work.
I am on a Galaxy S3 i747 AT&T phone.
Thanks in advance,
Jason

ja50nd4vi5 said:
I used the dirty flash version and it worked perfectly. Only one problem. It started out with my WiFi working. Then it stopped. I am in a place with free WiFi and i can not even turn WiFi on. Am i doing something wrong or is there an easy fix? I do appreciate everything that is shared here. Also thanks for the fix to get JellyBam 7.0 to work.
I am on a Galaxy S3 i747 AT&T phone.
Thanks in advance,
Jason
Click to expand...
Click to collapse
A clean flash always causes the least issues, see if that fixes your problem
Sent from my PG06100 using xda premium

I tried the clean flash and didn't have any luck. I'm not quite sure about the whole "kernel" thing. I don't know where to go for kernels or how to pick one.

OK, and again thank you for your time and info on this thread. I did the clean flash and used the kernel that the person starting the thread spoke about. The 3252013 kernel 3.0 worked and WiFi is on and working. So far this seems to be the winner. I didn't have success with 3.4, just so others reading know.
Thanks again.

The 3.4 kernels are still being debugged and tested IIRC

I'm using TWRP and can't seem to flash the .zip.
Anyone using TWRP with success?

Update: Was able to flash latest 7.1.
An issue I've been noticing with ROMs including PA, is that animations are very choppy.
Anyone else notice this?

Jellybam roms are banned from XDA for using other people's work without giving credit or getting permission from other developers. Also the reason the v7 flash doesn't work is because the developer forgot to include a kernel in the zip you need to pull one from another thread and place it in the zip. Also might need the meta folder from a cm Rom, can't really remember
Sent from my Nexus 7

BigMan0nCampus said:
Jellybam roms are banned from XDA for using other people's work without giving credit or getting permission from other developers. Also the reason the v7 flash doesn't work is because the developer forgot to include a kernel in the zip you need to pull one from another thread and place it in the zip. Also might need the meta folder from a cm Rom, can't really remember
Sent from my Nexus 7
Click to expand...
Click to collapse
There's a new release that works.

CM10

Best build yet. Wondering if anyone else is experiencing GPS issues?

I was having issues with GPS and streaming music thru Bluetooth.
Sent from my XT907 using Tapatalk 2

stupid question but...
Where are you getting this build?

straylight said:
Where are you getting this build?
Click to expand...
Click to collapse
Here's the original thread, use the GAPPs from the OP:
http://forum.xda-developers.com/showthread.php?t=2012093&page=26
Here's the post with the revised ROM, thanks to mic213:
http://forum.xda-developers.com/showpost.php?p=40364244&postcount=257

Hyro864 said:
I was having issues with GPS and streaming music thru Bluetooth.
Sent from my XT907 using Tapatalk 2
Click to expand...
Click to collapse
Bluetooth problem is with ASOP 4.2.1 builds its fixed in 4.2.2 I think.

edit: sorry for grammatical errors, im still upset it took four hours to get this phone back working again after doing a clean wipe
Interesting, I tried to install it, and was successful...but the keyboard doesnt work, every five seconds, i got a FC with the aosp keyboard. tried looking for another keyboard, but i cant type it in, so i guess i may have to put the apk on my sd card...also wifi doesnt want to turn on...is there no launcher in this rom? the home button doesnt work
to add, i have unlocked the bootloader, so im thinking this is a cosunmer-turned-into-a-dev phone...but i read that the rom was hybird...i really dont like safestrap, as it takes long to build a slot, so i figured unlocking the bootloader would be easy enough...but no...im using cwm 6.0.x

Herc08 said:
edit: sorry for grammatical errors, im still upset it took four hours to get this phone back working again after doing a clean wipe
Interesting, I tried to install it, and was successful...but the keyboard doesnt work, every five seconds, i got a FC with the aosp keyboard. tried looking for another keyboard, but i cant type it in, so i guess i may have to put the apk on my sd card...also wifi doesnt want to turn on...is there no launcher in this rom? the home button doesnt work
to add, i have unlocked the bootloader, so im thinking this is a cosunmer-turned-into-a-dev phone...but i read that the rom was hybird...i really dont like safestrap, as it takes long to build a slot, so i figured unlocking the bootloader would be easy enough...but no...im using cwm 6.0.x
Click to expand...
Click to collapse
Which build are you using?
Sent from my XT907 using xda premium

Leraeniesh said:
Which build are you using?
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
the beta i think, it was on hashofcodes' goo account...it is 4.1.2, i cant remember the date it is
however, i figure out how to install stock roms with an unlocked bootloader

Herc08 said:
the beta i think, it was on hashofcodes' goo account...it is 4.1.2, i cant remember the date it is
however, i figure out how to install stock roms with an unlocked bootloader
Click to expand...
Click to collapse
Try mic213's latest builds (last few pages of CM10 thread)
Sent from my XT907 using xda premium

Leraeniesh said:
Try mic213's latest builds (last few pages of CM10 thread)
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
Yeah the one on Hash's account is buggy ATM
Sent from my XT907 using Tapatalk 2

Hmm thanks. That's the one many threads recommend
Sent from my Carbon-ize Evita using xda-developers app

RikRong said:
Here's the original thread, use the GAPPs from the OP:
http://forum.xda-developers.com/showthread.php?t=2012093&page=26
Here's the post with the revised ROM, thanks to mic213:
http://forum.xda-developers.com/showpost.php?p=40364244&postcount=257
Click to expand...
Click to collapse
^^^Just a few posts above yours. Try it out. It seems to be the most stable build.
Herc08 said:
edit: sorry for grammatical errors, im still upset it took four hours to get this phone back working again after doing a clean wipe
Interesting, I tried to install it, and was successful...but the keyboard doesnt work, every five seconds, i got a FC with the aosp keyboard. tried looking for another keyboard, but i cant type it in, so i guess i may have to put the apk on my sd card...also wifi doesnt want to turn on...is there no launcher in this rom? the home button doesnt work
to add, i have unlocked the bootloader, so im thinking this is a cosunmer-turned-into-a-dev phone...but i read that the rom was hybird...i really dont like safestrap, as it takes long to build a slot, so i figured unlocking the bootloader would be easy enough...but no...im using cwm 6.0.x
Click to expand...
Click to collapse

Hyro864 said:
I was having issues with GPS and streaming music thru Bluetooth.
Sent from my XT907 using Tapatalk 2
Click to expand...
Click to collapse
Yes， streaming music thru Bluetooth won't work in cm10
GPS hasn't been tried yet , I don't use this.

so any fixes on CM10 gps? Someone said to flash to a stock based rom, get a gps lock then flash CM10.
which roms are stocked based?
once you get a gps lock, when installing CM10, do you do a clean wipe in CMW?

mightmuki said:
so any fixes on CM10 gps? Someone said to flash to a stock based rom, get a gps lock then flash CM10.
which roms are stocked based?
once you get a gps lock, when installing CM10, do you do a clean wipe in CMW?
Click to expand...
Click to collapse
Stock ROMs you can get here , or you can use this
I have succes after next:
1. Install AU mod
2. Lock GPS
3. Reboot to TWRP
4. Wipe cache / dalvik and factory reset (DO NOT WIPE SYSTEM)
5. install CM10 % GAPPS
6. Just enjoi! ):laugh:

St.Noigel said:
Stock ROMs you can get here , or you can use this
I have succes after next:
1. Install AU mod
2. Lock GPS
3. Reboot to TWRP
4. Wipe cache / dalvik and factory reset (DO NOT WIPE SYSTEM)
5. install CM10 % GAPPS
6. Just enjoi! ):laugh:
Click to expand...
Click to collapse
Its okay to flash an AU rom in for USA ?

mightmuki said:
Its okay to flash an AU rom in for USA ?
Click to expand...
Click to collapse
Do you mean in Verizon XT907?
I flash AU on my XT907 Verizon. It`s OK. But i have 2G.. I don`t know what about LTE or 3G operators..

mightmuki said:
so any fixes on CM10 gps? Someone said to flash to a stock based rom, get a gps lock then flash CM10.
which roms are stocked based?
once you get a gps lock, when installing CM10, do you do a clean wipe in CMW?
Click to expand...
Click to collapse
Every ROM listed for the RazrM (so far) is stock based, except CM10 and CM 10.1 . All the ones posted in this forum and DroidRzr were designed to be used with Safestrap and they are based on stock. Yes, you need to do a clean wipe for any ROM you install. However, I flashed Rage two nights ago and wiped cache/dalvik, factory data reset, but I DID NOT wipe system. It flashed perfectly. After you wipe, reboot recovery and mount system. After you wipe, TWRP says the system is mounted, but it is not. If you flash CM, you will need to flash a stock boot.img before you can go back to stock ROM.

RikRong said:
Every ROM listed for the RazrM (so far) is stock based, except CM10 and CM 10.1 . All the ones posted in this forum and DroidRzr were designed to be used with Safestrap and they are based on stock. Yes, you need to do a clean wipe for any ROM you install. However, I flashed Rage two nights ago and wiped cache/dalvik, factory data reset, but I DID NOT wipe system. It flashed perfectly. After you wipe, reboot recovery and mount system. After you wipe, TWRP says the system is mounted, but it is not. If you flash CM, you will need to flash a stock boot.img before you can go back to stock ROM.
Click to expand...
Click to collapse
AOKP is AOSP based too... We just got a port of it
Sent from my XT907 on CM10.1 using Tapatalk 2

sloosecannon said:
AOKP is AOSP based too... We just got a port of it
Sent from my XT907 on CM10.1 using Tapatalk 2
Click to expand...
Click to collapse
Thanks, I forgot about that one.

Any 4.2.2 ROM makes my camera crash

Hello,
I'm sorry if this is a repost of any sort . I am currently running a 4.1.2 rom and as it turns out any 4.1.2 rom that I run will have a functioning camera for my phone. However whenever I try to flash any 4.2 .2 rom on my phone the camera ceases to run correctly. I'm flashing the rom with clockworkmod touch and I have also tried flashing a camera fix I found on xda. I have even tried using third party camera apps, but those don't work either. Can anyone try to point me in the right direction or even try to help me troubleshoot this thing??
Thanks in advance
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

i'll begin with the question of what did you wipe before you flashed 4.2.2 and what ROM/release have you tried flashing?

Flash to factory stock and if ur camera still doesn't work it must logically be a hardware issue. Please guys correct me if I'm wrong
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

xBeerdroiDx said:
i'll begin with the question of what did you wipe before you flashed 4.2.2 and what ROM/release have you tried flashing?
Click to expand...
Click to collapse
I had just updated cwm to the latest touch version about a month ago. After that I was still on stock TW 4.1.1. Then, I tried flashing a 4.2.2 jellybam v7.6 and the camera stopped working so I flashed back to stock and the camera worked fine. I then tried flashing to the latest realease of CM 10.1 nightly
about 3 weeks ago but the camera didnt work so I flashed to 4.1.2 CSROM v1.4 then 1.5 and the camera worked fine. So I then tried CM10.0 4.1.2 and the camera still worked so last night I flashed to the latest CM nightly and the camera stopped working. Any thoughts?
Cprager said:
Flash to factory stock and if ur camera still doesn't work it must logically be a hardware issue. Please guys correct me if I'm wrong
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I did and it still works. So it can't be a hardware issue. It has to do with how my phone flashes the software because I haven't seen anyone else having the same issues with the ROMS that I have been flashing.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

AaronYoLungz said:
so last night I flashed to the latest CM nightly and the camera stopped working. Any thoughts?
Click to expand...
Click to collapse
if the camera stopped working simply from updating your current ROM to the latest release than a wipe and reflash could possibly have ironed out this issue. this is assuming you dirty flashed the update. we all do that, but in the event things dont funtion properly afterwards, a wipe is required.

xBeerdroiDx said:
if the camera stopped working simply from updating your current ROM to the latest release than a wipe and reflash could possibly have ironed out this issue. this is assuming you dirty flashed the update. we all do that, but in the event things dont funtion properly afterwards, a wipe is required.
Click to expand...
Click to collapse
Well before I flashed any rom I always wiped all user data, I wiped the cache and dalvik cache and in some cases I even formatted the system in advanced settings. In every case the camera never worked.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

If it could help, I can get a report of the crash... The only thing is I would need guidance on going about getting it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

i would back everything up. you have a working nandroid to fall back on?
then i would fully wipe the device and start over. you seem to be having problems with 4.2.2, not specifically aosp. it appears aosp and touchwiz 4.1.1 and 4.1.2 are working for you. correct? when transitioning android versions, its basically required to wipe everything in order to avoid issues. make sure you have the latest gapps for 4.2.2. that may be your problem right there.
in the event you choose to wipe and reflash a 4.2.2 rom,
- backup your files
- have a nandroid, the rom you want and gapps on a micro sd card.
- boot into recovery
- wipe data/factory reset
- wipe cache
- wipe dalvik
- format /system
- format /data + media
- flash rom from external sd card
- flash gapps from external sd card
- reboot and let your phone sit a few minutes then reboot again. check it out.
you wont get any ROM support from devs on your issues until you come from a complete wipe. a hassle to set everything up again but it will likely be your fix. if not, we can go a different direction.

Alright I'll try this now. I will keep you updated
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

AaronYoLungz said:
Alright I'll try this now. I will keep you updated
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
did you make sure you were flashing the correct gapps for your version of android? i'd hate to see you do all this for an incorrect gapps issue. yes, keep me posted

xBeerdroiDx said:
did you make sure you were flashing the correct gapps for your version of android? i'd hate to see you do all this for an incorrect gapps issue. yes, keep me posted
Click to expand...
Click to collapse
Alright I followed all of the above steps and my phone camera still isnt working. For clarification, gallery app works but when I actually try to use the camera I get a "Camera Error - Cannot connect to camera " popup window with an okay button below it.

AaronYoLungz said:
Alright I followed all of the above steps and my phone camera still isnt working. For clarification, gallery app works but when I actually try to use the camera I get a "Camera Error - Cannot connect to camera " popup window with an okay button below it.
Click to expand...
Click to collapse
what ROM and release did you end up flashing?

xBeerdroiDx said:
what ROM and release did you end up flashing?
Click to expand...
Click to collapse
ROM: cm-10.1-20130521-NIGHTLY-d2att
Gapps: gapps-jb-20130301-signed
EDIT: The problem described in the post#11 has always been the case

i would do 1 of 2 things: flash this 4.2 camera zip in recovery and see if that camera and gallery work or flash a different 4.2.2 ROM like tasks. this will help determine if its just cm10.1 thats giving you grief.
if you download and flash the 4.2 camera, just wipe cache, dalvik and flash the zip. in the event you get a freeze up when taking a picture with auto-focus, you have to set the scene to "Action" mode.
hit me back

xBeerdroiDx said:
i would do 1 of 2 things: flash this 4.2 camera zip in recovery and see if that camera and gallery work or flash a different 4.2.2 ROM like tasks. this will help determine if its just cm10.1 thats giving you grief.
if you download and flash the 4.2 camera, just wipe cache, dalvik and flash the zip. in the event you get a freeze up when taking a picture with auto-focus, you have to set the scene to "Action" mode.
hit me back
Click to expand...
Click to collapse
Should I remove Gallery4.apk and Gallery2.apk from /system/app?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

You can use a file Explorer to move those 2 to a different folder so that you can move them back if need be

xBeerdroiDx said:
You can use a file Explorer to move those 2 to a different folder so that you can move them back if need be
Click to expand...
Click to collapse
Alright so I ended moving the gallery, then flashing the new camera app in CWM then wiped the cache and dalvik. No luck, so I tried restarting my phone, fixing permissions, and nothing worked. I then full wiped my phone and flashed Vanilla Rootbox, tested camera and it didnt work. It still said "Camera Error- Can't connect to camera" . . I flashed the camera zip provided followed by a cache and dalvik wipe but I got the same message. Following the above steps I did the exact same thing with AOKP and the exact same thing happened.
Is it possible that my phone just can't support 4.2.2?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Is it possible that an outdated version of Odin could be the problem?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

[Q] Updating To Cm-10.2-20130907-Nightly From Cm-10.1.2

Hi,
I was trying to update to the nightly version of CyanogenMod, so I went to the update part in the settings and selected the latest nightly. I want to update for the Google Voice integration with any app. Upon downloading and restarting the phone to apply the update, it was at the screen with this (bit.ly/1a9E9NF) and 'Samsung Galaxy S III' written on the top but wouldn't move past that. I was able to boot into recovery mode and I installed CM-10.1.2 (Stable) on a microSD and applied that update so I was able to take control of the phone again, however; I was not able to get the nightlies. Can anyone help with that?
On a different note, when I updated back to CM-10.1.2 (Stable) the Google Play store would not work and many Google Apps would crash, I fixed this by going back into recovery mode and re installing GApps, is that related at all?
Right now, I have everything exactly as I had it before trying to go to nightlies, my issue is how do I update to nightlies now? Did I do something incorrect?
I have a Samsung Galaxy S III AT&T - I747. This is where I downloaded the update to my microSD card: bit.ly/14KMExv
Thank You,

ibrahim1996 said:
Hi,
I was trying to update to the nightly version of CyanogenMod, so I went to the update part in the settings and selected the latest nightly. I want to update for the Google Voice integration with any app. Upon downloading and restarting the phone to apply the update, it was at the screen with this (bit.ly/1a9E9NF) and 'Samsung Galaxy S III' written on the top but wouldn't move past that. I was able to boot into recovery mode and I installed CM-10.1.2 (Stable) on a microSD and applied that update so I was able to take control of the phone again, however; I was not able to get the nightlies. Can anyone help with that?
On a different note, when I updated back to CM-10.1.2 (Stable) the Google Play store would not work and many Google Apps would crash, I fixed this by going back into recovery mode and re installing GApps, is that related at all?
Right now, I have everything exactly as I had it before trying to go to nightlies, my issue is how do I update to nightlies now? Did I do something incorrect?
I have a Samsung Galaxy S III AT&T - I747. This is where I downloaded the update to my microSD card: bit.ly/14KMExv
Thank You,
Click to expand...
Click to collapse
How do you personally flash ROMS? Flashing them wrong can cause issues. Do you wipe everything first and then flash the software? Your supposed to wipe in recovery data, cache, and dalvik cache in that order or at least that's what I do each time. It always works for me.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

Bruce Lee said:
How do you personally flash ROMS? Flashing them wrong can cause issues. Do you wipe everything first and then flash the software? Your supposed to wipe in recovery data, cache, and dalvik cache in that order or at least that's what I do each time. It always works for me.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well, I am only updating my ROM, not flashing a new one. So wiping my phone would be unnecessary and inconvenient. I've updated before but only to stable versions, this is the first time I've tried a nightly.

ibrahim1996 said:
Well, I am only updating my ROM, not flashing a new one. So wiping my phone would be unnecessary and inconvenient. I've updated before but only to stable versions, this is the first time I've tried a nightly.
Click to expand...
Click to collapse
Nightlies are a totally different breed. Whenever I flash ROM. I wipe everything. Since the latest nightly is a different android version from the previous android version. I am highly recommending flashing clean not dirty. The GAPPs are different also. It might be inconvenient but flashing clean eliminates many issues.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

[Fix] 4.3 ROMs stuck on splash screen after first reboot

repruth there
spongdangly said:
[Fix] 4.3 ROMs stuck on splash screen after first reboot
Click to expand...
Click to collapse
Thanks for the response! I really don't want to do a factory reset so I guess I'll go to my second option. The only reason I really want the nightly is for the Google Voice to Stock SMS integration which was available in the July Nightlies, is there an archive to those nightlies. I've tried looking but have had no luck.
Thank You,

ibrahim1996 said:
Thanks for the response! I really don't want to do a factory reset so I guess I'll go to my second option. The only reason I really want the nightly is for the Google Voice to Stock SMS integration which was available in the July Nightlies, is there an archive to those nightlies. I've tried looking but have had no luck.
Thank You,
Click to expand...
Click to collapse
Current nightlies for cyanogenmod are Broken. Source!

ibrahim1996 said:
Thanks for the response! I really don't want to do a factory reset so I guess I'll go to my second option. The only reason I really want the nightly is for the Google Voice to Stock SMS integration which was available in the July Nightlies, is there an archive to those nightlies. I've tried looking but have had no luck.
Thank You,
Click to expand...
Click to collapse
Here's a link to MSgtSimon's CyanogenMod d2att archive. I believe 0813 was the last 10.1 nightly (I had been running it for over a week without any major hiccups). You could also try 10.1.3-RC2 (I'm not sure how stable this is since I haven't used it) if you wanted the ROM to have the most recent patches.
thepoetlives89 said:
Current nightlies for cyanogenmod are Broken. Source!
Click to expand...
Click to collapse
The 0906 and 0907 CyanogenMod Nightlies were broken but today's (0908) is supposed to be fine.

spongdangly said:
The 0906 and 0907 CyanogenMod Nightlies were broken but today's (0908) is supposed to be fine.
Click to expand...
Click to collapse
Hopefully it will work for most; but i would stay away from nightlies for a couple of days just to be sure.

thepoetlives89 said:
Hopefully it will work for most; but i would stay away from nightlies for a couple of days just to be sure.
Click to expand...
Click to collapse
I'm running the latest nightly (0908) without any problems. I believe there was a problem with the online builder before. You can see that the nightlies for 0906 and 0907 (the two that didn't work) were only 184mb in size compared to the rest of the 10.2 ROMs that are 193mb in size.