Database Users

Camera force close

I am having some trouble getting the camera working on a mytouch3g I have been working on. I have Engineering SPL 1.33.2004 installed with CM-recovery 1.4 installed. Have tried several 32B roms but always get a force close. Have wiped, restored nandroid backup, used clean sd, and even tried pushing the stock camera and 3rd party camera apps. Is there something I'm missing? I have rooted a few Dreams, but this is the first Sapphire I have dealt with. Any suggestions?

try flashing the stock mytouch rom. its on here some where. if that works then just try a cyanogen rom. i refer the 4.0.4 rom. if this works then you had corrupt files on dl. if this is the case then try using a dif os. if continues then your sd and or file reader is trying to filter content. so use something else. let me know. rockin...

Thanks for the reply. I have tried cm 4.0.4 as well as several of the 32B roms from the Sapphire board. In fact 4.0.4 is what I flashed it to as soon as I finished the rooting process the first time. The camera worked fine that night, but has since crapped out. None combo of roms/spl/radio seem to do any good. Even wiped, and unrooted w/ sappimg.nbh and started over a time or two. Then I read earlier someone on the Dream board had a similar problem, and fixed it by re-formatting SD. So I gave that a shot (even used a different SD that is known to work fine) but still no luck.
So now I have put the phone back to stock. I figured since every partition we change by rooting has been wiped and rewirtten to it's original state, it's best to just call it a hardware issue & have t-mo swap it out. I don't see anyone else having these kind of issues on here. So I'm thinking this phone must have met the floor somewhere between the time I flashed it and the time camera issues started. Nothing else can seem to explain it. Hopefully I'll have better luck with the next one.

gurnted said:
Thanks for the reply. I have tried cm 4.0.4 as well as several of the 32B roms from the Sapphire board. In fact 4.0.4 is what I flashed it to as soon as I finished the rooting process the first time. The camera worked fine that night, but has since crapped out. None combo of roms/spl/radio seem to do any good. Even wiped, and unrooted w/ sappimg.nbh and started over a time or two. Then I read earlier someone on the Dream board had a similar problem, and fixed it by re-formatting SD. So I gave that a shot (even used a different SD that is known to work fine) but still no luck.
So now I have put the phone back to stock. I figured since every partition we change by rooting has been wiped and rewirtten to it's original state, it's best to just call it a hardware issue & have t-mo swap it out. I don't see anyone else having these kind of issues on here. So I'm thinking this phone must have met the floor somewhere between the time I flashed it and the time camera issues started. Nothing else can seem to explain it. Hopefully I'll have better luck with the next one.
Click to expand...
Click to collapse
Hate to say bro, but ya has to be hardware. Everyone has messed with cam software and had success. So you have done right and reverted to stock. Send that bad boy back and get a newer exchange. Sadly to say my orig. spl was broke and had to send back. I tried talkin tmobile service techs thru the steps but they only were like "ahhhh ummm" lol. do the dew and get a newer hardware softer g2. fosho. . . . .

Yeah that's what I figured. At least the folks at t-mobile didn't give much hassle. It was within the 14 days so they were pretty quick to agree to the swap out. New one will be here next week, and I'll give it another go. Thanks for the help.

camera force close
hey great guys
i have x18i (china clone) mtk 6573 mobile. recently camera is force closing
and its flash is also not working. i tried factory reset also .... fone is rooted

Rogers HTC Dream issues

My girlfriend has the Rogers HTC Dream, while I have the T-Mobile G1.
I was able to properly root both phones (although I had mine longer) and I have tried several different roms on both. When we were both running TheOfficial Rogers 1.8.4 and I think 1.9.1, everything was ok. TheOfficial AOSP 1.6 came out, so I took the plunge and tested it on my phone. It was fine.
She kept complaining that her phone was slow and non responsive at times, and indeed it was. I tried flashing the same TheOfficial AOSP 1.6 on her phone and did a wipe. I believe her phone was still non responsive at times, although I can't seem to remember exactly what it was this time.
I then proceeded to install the latest Cyanogen because I was curious and hoping that it could resolve the problems. -My amnesia kicking in again.. wtf?-
I decided to go back to TheOfficial AOSP 1.6. I do the wipe, flash the base rom, then the expansion, then reboot. On first boot, it connects to the GPRS fine. Connecting to the internet will cause the phone to hang. Only way to use the phone is keep it from connecting to 3G/Edge. If I reboot the phone, sometimes it gets stuck on the Rogers screen. When it does boot, it won't connect to GPRS. The only way to use her phone is to wipe and do a fresh flash. Then I won't be able to reboot or else I have to flash again. I have reflashed and rewiped this rom several times already and it's the same.
Anyone know the reason why? I have the correct radio and spl flashed. I have no idea why this is happening. I have flashed my T-Mobile G1 many, many times and, well.. she's using it now. I'm going to try Dwang's rom to see if the same thing happens.
So far it worked. I'm not getting any force closes. I can't figure out why I can't install TheOfficial Donut AOSP on this phone. Dwang's rom doesn't come with terminal or maps. I'm not sure if it's supposed to be like that. I tried the Google Navigation update mod and for some reason that just restored the normal Google Maps on her phone. I'll try it on my own phone later. I'll just leave it at that and won't update anymore unless someone can figure out for me how to install TheOfficial Donut AOSP.
Bye.

Hate to ask you something you might have answered, but are you sure that you have used the EBI1 radio image on the Rogers Dream?

Camera reboots phone with Android 1.6 or higher

Is anyone else having this problem?
I've got a Rogers HTC Magic, and whenever I've tried a ROM with Android 1.6 or greater (I've tried 3 or 4) the accessing the camera will cause the phone to reboot itself.
It doesn't happen the first time I use the camera, but it does the second time and consistantly.
Does anyone else have this problem?
1.5 ROMs are fine. I'm currently using cursorsense and it's not an issue but at some point I will want to use a newer version of Android.

I have the same problem :x

Relash the rom. If you are using any of the legal roms (cyanogen/superd) flash the base before the rom. remember to wipe before starting.

I've tried cyanogen 2.1 test2 and Smoki both causes reboot when using camera apps (barcode scanner, google goggles, fxcamera, ...).
It doesn't reboot always tho like 1/3 times i use one of these apps i get a black screen and then a reboot.
Im using CursorSense now and all the camera apps work just fine :s.
Always did a wipe before flashing the roms.

Known issue. Been dealing wirh this for a long time on my Rogers Magic. I think the trouble is the devs dont have this model, and no one has submitted useful logs. http://code.google.com/p/cyanogenmod/issues/detail?id=792

Too many issues so few roms

3rd thread, about 4th rom flashed
constant issues with builds. have gone from stock to:
cm 6.1.3 -apps crashing, random crash notices i.e "phone book has crashed force close" - "the process com.android.phone has stopped unexpectedly"
cm 7 - random reboots, opening browser caused power cycle, wifi issues, lag (thread posted, no solutions at the forefront)
currently on tripnraver pre release. now another issue. no signal what so ever.
original baseband on this xperia x10a is .55. it is suggested to use with bands 52 or 49.
loading either of these basebands. which ive done. doesn't seem to fix the no signal problem. the description states should be backwards compatible even if appropriate bb is not installed on device. yet no luck.
attempting to flash either baseband fails to resolve this problem. currently trying to flash back to stock and try another full reinstall and baseband flash in flashtool.
any ideas would be a great help. having to flash x number of times between roms is getting quite time consuming
thanks everyone.

if you want to stay on the miui rom, you can flash the baseband patch located here and stay on whatever baseband works best for you (I'm on .55 and find it fantastic), then when you load the rom, go to dev tools>bad behaviour>crash the system server.
http://forum.xda-developers.com/showthread.php?t=1011608
Otherwise, I would recommend wolfbreaks cm 6.1.3, as it is the most stable. You must have done something wrong during installation as I never had an issue with his roms.

The only issue I have ever had with any rom is MiUi and thats because I used the wrong baseband. You must be doing something wrong for you to be having problems

if you want, try this flash, it's trips miui pre-final with the baseband patch implemented.
http://www.multiupload.com/KCKE9K2WKN
worked with my .54 baseband

thanks so much for the links to the baseband patches. i remember coming across a thread that posted it but unfortunately forgot to book mark. so im definitely going to go ahead and try with the patch installed. hopefully all works well
each rom ive flashed has been done properly according to instructions. cache wiped, dalvik, and full reset as per menu options in xrecovery.
one way or another i experienced lag for the most part, and as mentioned some random crashes. never had reset on wolfs rom just error messages at times. trips rom worked excellent, smooth and quick. hopefully with the patch implemented everything will work flawlessly
thanks you guys
*Updated
Flashed over rom with baseband patch. signal working. everything running smooth.
except for when using camera zoom. zoom default displays 0x. as soon as the option is selected it spawns an immediate force close
any patches? or similar outcome for anyone else?
i will outline my steps below so everyones up to speed on how i performed this flash.
- flashed back stock in SEUS
- root with one click (success)
- installed busy box (market)
- installed xrecovery apk
- booted into xrec
1. full factory reset
2. wipe cache
3. wipe dalvik cache
4. wipe battery stats
5. install custom zip from sd card
6. selected trips rom with bb patch implemented
5. reboot

Camera zoom doesn't work in most ROMs yet and the lag you were experiencing was likely just the FW "settling" it can take a little bit and a couple reboots sometimes for the phone to calibrate itself properly.
Sent from my X10i using XDA Premium App

thanks cmoney. maybe ill try my luck with cm7. give it a few reboots and hope for the best. great rom. im really loving trips iphonesque style
clean smooth and quick. everythings working great. hoping the zoom may get fixed soon enough. only other inquiry i have with regards to this rom is the apps2sd.
this feature is essential to myself personally. and it is not working as ive noticed on this rom. ive read a thread with regards to a fix for the last release. i checked the settings for an enable option in case the feature requires being manually set as active but nothing listed. within sd settings state reads as unavailable. if anyone has an answer as to whether this fix will function with the current pre release. ill be going ahead with completeling the flash and reporting what i find back on this thread.
thanks again everyone

Try Wolfbreaks rom. It's very very stable for me. It has cam and everything upto date.

im going to flash back to wolfbreaks updated 6.1.3 unless anyone can point me in the direction of a fix for trips rom.
the smooth and fluid feel of trips rom was brilliant. i am hopeful someone has directions for an apps2sd fix as i have flashed the build twice and the same issue has occured.

thesoundofsilence said:
im going to flash back to wolfbreaks updated 6.1.3 unless anyone can point me in the direction of a fix for trips rom.
the smooth and fluid feel of trips rom was brilliant. i am hopeful someone has directions for an apps2sd fix as i have flashed the build twice and the same issue has occured.
Click to expand...
Click to collapse
works for me on trips newest....

i just downloaded the new version 1.0
this is ridiculous. without the baseband patch. crash system server. no signal
now apps to sd is saying "apps2sd is not supported on this device"
this is an xperia x10, so obviously there must be something wrong here.
can anyone elaborate on exactly what to do about this because im going to attempt to flash back the rom, flash the bb patch right after, reboot. i assume this will only solve my signal issue. but this apps to sd is getting extremely frustrating and i can not figure out why it is not showing an enabled status.
- Flashed 1.0 with baseband patch - network signal resolved.
- apps to sd is STILL not working. and i really dont know what to do about this. everything else on this rom is perfect. is there something im missing? i came across a patch for apps2sd fix but this was for a previous version. would it be needed here? is there a setting that must be enabled first in order to start apps to sd as a service.
- as mentioned previously within the main menu, under sd card settings. message states "apps2sd is not supported on device" and on previous build would display "apps2sd unavailable". its simply impossible that the phone doesn't support it. as with every other rom the feature has worked. froyo would support it. the question is how do i go about enabling said feature?

thesoundofsilence said:
i just downloaded the new version 1.0
this is ridiculous. without the baseband patch. crash system server. no signal
now apps to sd is saying "apps2sd is not supported on this device"
this is an xperia x10, so obviously there must be something wrong here.
can anyone elaborate on exactly what to do about this because im going to attempt to flash back the rom, flash the bb patch right after, reboot. i assume this will only solve my signal issue. but this apps to sd is getting extremely frustrating and i can not figure out why it is not showing an enabled status.
- Flashed 1.0 with baseband patch - network signal resolved.
- apps to sd is STILL not working. and i really dont know what to do about this. everything else on this rom is perfect. is there something im missing? i came across a patch for apps2sd fix but this was for a previous version. would it be needed here? is there a setting that must be enabled first in order to start apps to sd as a service.
- as mentioned previously within the main menu, under sd card settings. message states "apps2sd is not supported on device" and on previous build would display "apps2sd unavailable". its simply impossible that the phone doesn't support it. as with every other rom the feature has worked. froyo would support it. the question is how do i go about enabling said feature?
Click to expand...
Click to collapse
I dunno man, it works fine for me, but I copied data from my 0.3.2 xrecovery image, so that might be why. try flashing that apps2sd fix for 0.3.2, should work fine

damn it. i just found that thread. found the links to the fixes. so far ive tried miui32_a2sd_fix.zip. and flashed that over with xrec prior to reboot. which did nothing.
there are two more links so im going to try those two flashes as well and hope that one of them will do the trick. if its working when utilizing .32 patches then ideally the bloody thing would have to work here. thanks for the input though dtox. much appreciated

I don't know what else to suggest man
From the feedback I see in the miui thread, everyone else is reporting it working!
Did you factory wipe, wipe cache partition, and wipe dalvik cache before install? then flash the miui 1.0.zip, and flash immediately the baseband patch then reboot into the rom.
Remember not all apps allow apps2sd so use something like android system info, go into the applications tab click on one, click manage and then see if the option "move to sd" is highlighted. Like I said check a few though, not all apps can be moved

i just replied in the dev section lol but yes i have gone ahead and checked the applications menu. specifically downloaded a file i have moved to sd on a previous occasion from the market.
nothing
the "apps to sd" selection is completely greyed out. no matter what application i click on or download. i did a full wipe, full install, and selected the apps2sd fix immediately after rom and bbpatch flash, prior to rebooting. issue still remains.
we'll see i guess. thanks again dtox

thesoundofsilence said:
i just replied in the dev section lol but yes i have gone ahead and checked the applications menu. specifically downloaded a file i have moved to sd on a previous occasion from the market.
nothing
the "apps to sd" selection is completely greyed out. no matter what application i click on or download. i did a full wipe, full install, and selected the apps2sd fix immediately after rom and bbpatch flash, prior to rebooting. issue still remains.
we'll see i guess. thanks again dtox
Click to expand...
Click to collapse
Try it again but without the fix...

i did that to it doesnt work i get the same message displayed
i tried with fix and without. another thing to note is that the rom itself says it should work with a different baseband as it has elements of unified. (which it doesn't) i had to flash the bb patch to get signal.
im not sure whats up with this but until i figure it out for a certainty ive flashed back over to wolf breaks rom. hopefully something will surface and i can give trips rom another go.

thesoundofsilence said:
i did that to it doesnt work i get the same message displayed
i tried with fix and without. another thing to note is that the rom itself says it should work with a different baseband as it has elements of unified. (which it doesn't) i had to flash the bb patch to get signal.
im not sure whats up with this but until i figure it out for a certainty ive flashed back over to wolf breaks rom. hopefully something will surface and i can give trips rom another go.
Click to expand...
Click to collapse
No idea man, like I said it is fine for everyone else so I'm so no big development will arise that will make it function with your phone....

maybe it has something to do with 10a. i dont know. but the point is it shouldn't even be doing this regardless. hypothetically if its froyo and it has apps2sd built in. it should work. its not the way ive flashed. the phone supports it. so my only conclusion the rom must not be as compatible as stated. and from reading different posts about the prev builds sometimes the patches worked at other times they didnt. and also the fact that the rom is claimed to work without the need for a bbpatch. yet without the patch instaled phone caught no single. i guess certain unexplainable glitches can be bound to happen at times but any how ill give it one last go.
if nothing comes out of that then im giving up on that build because it seems relatively hopeless.

lol I'm using an x10a...
Still man you're the only person reporting this. Don't you find that strange? What baseband are you using anyhow?

LG G2 Cannot connect to camera

Had this phone for about 1 week now. Everything been fine until today. I tried to take a few pictures, but I couldn't. Received an a pop up with "Cannot connect to camera" I'm not sure what's causing this issue, I cleared the data/cache on it and still occurs. Is there any solution to this issue?
Thank you.

I have exactly the same situation.. But it's weird - ported LGCamera works without errors, other apps (market or aosp based) throw error. Sometime clear app data help, but only sometimes..
It could be hardware problem?

I've had this happen when I was on an older CM11 nightly.I did have to preform a clean install to fix the problem.

xxxrichievxxx said:
I've had this happen when I was on an older CM11 nightly.I did have to preform a clean install to fix the problem.
Click to expand...
Click to collapse
18/03? It didn't helped.. I was testing old and newest ROMs - same situation I think it could be some hardware problem - currently I have version from Singapore build at 02/2014
EDIT#1
Weird.. I will go back to stock - test, then install custom ROM.. Something go wrong - when I'm using ported LGCamera.apk in CM/Slim/PA it's working, other camera apps - don't..

I guess I found out the issue of why it was being caused. I also have a Nexus 5 and both had the APP Flashlight by Go Launcher. Seems to me when I downloaded and used it couple of times it caused my camera not to work on both phone. Uninstalled it and now it's working fine with now issues. I'm not sure if you guys also have a flashlight app, but maybe you can give it a try.

I got a replacement g2 from my insuarance and from the box mine done the same thing i tried every app i could find one day i flashed a diffrent rom and was bored. Clicked on my cam and it worked went back to my stock backup for my updatez and it wouldnt connect found out its was a software isse broken software from the factory i put a new stock rooted rom on and good as new. Mine was down. For about a month whrn i notticex what was wrong i thouvht i had a hardware failure but it wasnt there is always a chance of a bad cam but also some app like certain flashlights do take over your hardware if uve rooted and the phone is new goback stock unroot and have swapped

I'm on stock KK right now = 0 problems, so I think it's not hardware. LG camera and other apps always working fine.
Now I will go back to AOSP and test apps again

zg85 said:
I'm on stock KK right now = 0 problems, so I think it's not hardware. LG camera and other apps always working fine.
Now I will go back to AOSP and test apps again
Click to expand...
Click to collapse
Hello,
Did you go back to aosp ? Is the camera ok now ?
Thanks

Here's a thought. After a new rom anybody feel there is a dial pad code to bridge the connection gap.

help, question
TheMadScientist420 said:
I got a replacement g2 from my insuarance and from the box mine done the same thing i tried every app i could find one day i flashed a diffrent rom and was bored. Clicked on my cam and it worked went back to my stock backup for my updatez and it wouldnt connect found out its was a software isse broken software from the factory i put a new stock rooted rom on and good as new. Mine was down. For about a month whrn i notticex what was wrong i thouvht i had a hardware failure but it wasnt there is always a chance of a bad cam but also some app like certain flashlights do take over your hardware if uve rooted and the phone is new goback stock unroot and have swapped
Click to expand...
Click to collapse
hardware if uve rooted and the phone is new goback stock unroot and have swapped[/QUOTE]
hey, i also got a replacement phone via assurant insurance. can u dumb it down, what exactly did you do to get the camera working back again?... ROM?... i dont really have any apps for the camera, only whatsapp...
ill be waiting for your answer, thanks

THANKS，I got the same problem and after I deleted the Go Flashlight the camera worked again!

Same issue. Go flashlight solved thanks to this thread.

Having similar issue. Flashed a new bootstack and camera stopped working. Factory reset, fresh install tot, then kdz, then cloudy g3. Camera still force closes and other camera apps can't connect. I can take one picture after a fresh install (which I did three times flashing from tot...).

Camera not working
reeper250 said:
Having similar issue. Flashed a new bootstack and camera stopped working. Factory reset, fresh install tot, then kdz, then cloudy g3. Camera still force closes and other camera apps can't connect. I can take one picture after a fresh install (which I did three times flashing from tot...).
Click to expand...
Click to collapse
hi i have also the same problem.. have you any solution ??

umair_hashmi said:
hi i have also the same problem.. have you any solution ??
Click to expand...
Click to collapse
Nothing worked. Just gave away the phone and bought an LG G3