Instagram gets force close.
I'm running cm7.2
I'm getting FC every time I take picture with my "Instagram camera". I'm also using CM7 7.2.0 RC1 version of Cyanogen Mod, and I do believe that this isn't problem with ROM, that is problem with Instagram itself.
Waiting for the patch might help, but no one knows that for sure. Maybe it's FC-ing because HTC Tattoo doesn't support Instagram.
It doesnt FC on Rallapag's CM9 builds!!!
jakonicki93 said:
I'm getting FC every time I take picture with my "Instagram camera". I'm also using CM7 7.2.0 RC1 version of Cyanogen Mod, and I do believe that this isn't problem with ROM, that is problem with Instagram itself.
Waiting for the patch might help, but no one knows that for sure. Maybe it's FC-ing because HTC Tattoo doesn't support Instagram.
Click to expand...
Click to collapse
I have the same exact problem.
Related
Hello guys, I recently bought a xperia x10 off my friend. It was running on 1.6 Donut. When I bought the phone the camera was ok (I didn't took any picture but I could go through settings and stuff). I've updated my phone to 2.3.3 today and now whenever I start the camera and start to go through settings or try to take picture it says: "Sorry! Activity Camera (in application Camera) is not responding"
The only options are Force Close and Wait. I've also used "Camera 360" it worked for a while, took a couple of picture and then the same thing happend to that too.
Could it be a hardware issue? cuz I can't return the phone now
Any idea
more info needed. how did you upgrade?
Sent from my X10 using XDA Premium App
Using SEUS....its offical 2.3.3
hmmm... what happens if you select wait?
if issues continue i would re-install the update...
wish i could be more help...
well, sometimes it becomes normal and sometimes it hangs...and I've re-installed the update like hundreds of times but no luck in that. Anyway i've just rooted my phone and installed xrecovery and i don't know how but the bugs seems to have fixed by that???
I have the same problem, did everything as you said, so now when you did all that camera works fine?
having the same problem...any solution??
Never have this problem with the ROMs developed from Erick, WB, TH or Blue Sparks.
If you have rooted your phone, you could try one of these ROMs.
the problem appear on stock 2.3.3.. no root.. all stock... clean memory card...
the camera only snap picture when i restart the phone, then after 1 or 2 picture taken the 3rd photo canot snap already. it cant focus and hang. ask me to fc or wait....
I have the same problema, with the stock rom. Im going to try with Wolf's rom, lets se how it goes.
I get the error with camera360 ultimate 2.4.1 and vignette.
any solution??? still having this problem...
nah its fixed now...for the first time rooting fixed that and now everytime i give it a uk update its completely fine from the start
I've been running CM7 on my Attic 4G AT&T for about a month now.. and just recently, whenever I try to take a picture or open the gallery, the app crashes. Anyone having the same issues or have any way to fix it?
Sent from my MB860 using XDA App
Just reflash it from CWM - it wont wipe anything. I'd also reinstall gapps. Should fix any issues. I've been running the Beta of CM7 since a day or two after its release. Never had any issues. Only thing I could consider an 'issue' was a bad kernel flash, which re-flashing the CM7 Beta.zip fixed.
I reflashed CM7 and the camera still doesn't work. I don't have the issue with the gallery crashing anymore, but whenever I press the button to take a picture, I get a popup saying the camera crashed.
TreyChristopher said:
I reflashed CM7 and the camera still doesn't work. I don't have the issue with the gallery crashing anymore, but whenever I press the button to take a picture, I get a popup saying the camera crashed.
Click to expand...
Click to collapse
Edit: nevermind forget what i said
i cant seem to get my vibrant with the latest cm7 to work properly anymore. my browser crashes, my messaging crashes and so does fb or any other app i try to go into. does anyone know why its doing this? i would love some help on this damn issue, thanks
EDIT: BTW my phone was working fine until one day it randomly started doing all the crashing in a CM7 Nightly, afterwords i decided to update to the latest CM7 Official and thought it was going to fix the problems. unfortunately it did not and the problems still persist.
EDIT 2: NVM fixed......
I tried using the latest gapps from goo.im/gapps on Munjeni's CM9 rom and was getting boot loops.
I used th gapps-ics-tiny.zip and was able to boot but calendar does not sync. Doesn't even give me the option for calendar under "Accounts and Sync."
Any else having this problem?
Use the Google apps in the Winsuk thread:
http://forum.xda-developers.com/showthread.php?t=1451906
They work perfectly.
Sent from my Liberty using XDA
Thanks for the help..will try that one
Sent from my Liberty using XDA
I got a boot loop on first boot, pulled battery then it booted.
Sent from my Liberty XDA
I decided to give it a shot last night. The ROM and gapps in munjeni's thread installed without any issue. I only played with it for about an hour or so, but it was really cool.
Here's hoping the camera and GPS can be worked out soon.
April 13 update
Latest version of menjuni's CM9 working great with a number of fixes:
- GPS working
- Wifi status working
Can't wait to give it a try.
Sent from my Liberty using XDA
Wallpaper size
I am posting this here because I am not eligible to post on the development site.
I have noticed that all versions of the CM9 ROM have built-in wallpapers that are not properly sized for the Aria. The wallpaper that loads first time it the right size, but once another is loaded, they all appear too big, and you can't go back to the stock ICS wallpaper without reloading the ROM.
Am I missing something?
And please note: I am not complaining. The Aria/CM9 team -- notably WinSuk and Munjeni -- have done a fantastic job and great service for the Aria network.
I decided to give this ICS ROM a try for fun today...after someone mentioned to me that the Captivate and Aria (as old devices) both have ICS.
It seems like it should work fine...for the most part...as an everyday device. As long as you can deal with having no working camera or GPS.
I didn't actually slip my sim card in...since it's not currently my main phone.
Battery?
Hey guys,
Im on winsuks latest cm9. it works great for me except my batter lasts about half the time it lasted with cm7. Does anyone know if munjeni's cm9 is any easier on the battery?
I didn't try WinSuk's ROM yet, I'm running munjeni's ROM as a daily driver. In the build from 27.4., camera and GPS are working; I'm trying now the deodexed built munjeni posted today and see if it works better.
chrome
does anyone know how to get google chrome beta working on this rom? I'd love to try it out
dylantep said:
does anyone know how to get google chrome beta working on this rom? I'd love to try it out
Click to expand...
Click to collapse
Supposedly it's for Armv7 only...we are Armv6
mikelebz said:
Supposedly it's for Armv7 only...we are Armv6
Click to expand...
Click to collapse
aww thats disappointing. I was really looking forward to trying it
s2e
Had s2e working fine but when I updated to the latest version (may 10th) I cant seem to use it anymore. it just keeps asking for root access and the app never actually opens. is anyone else having this problem?
dylantep said:
Had s2e working fine but when I updated to the latest version (may 10th) I cant seem to use it anymore. it just keeps asking for root access and the app never actually opens. is anyone else having this problem?
Click to expand...
Click to collapse
Yes i had the same issue, run "fix permissions" in rom manager, i tried that option in cwm and it did not work. I am back on cm7 because for some reason i wasnt able to receive calls, i was able to make calls, send and receive messages etc...
fix permissions did not help. however I was able to get s2e to work by using superSU from the play store.
Haven't tested out calling/messaging yet
call and messaging send/receiving also seems to work for me.
dylantep said:
Had s2e working fine but when I updated to the latest version (may 10th) I cant seem to use it anymore. it just keeps asking for root access and the app never actually opens. is anyone else having this problem?
Click to expand...
Click to collapse
I got the problem, too. For me the solution was to reinstall the su binary using the update option in the settings menu of superuser.
Sent from my Liberty using xda premium
MMS
is anyone else having problems recieving MMS messages. it shows up with a download button but it is unable to download. Works ok if I use go sms but I would prefer to just use stock
So I've been using CM since CM7. when I was flashing one of CM9 night versions, which has the problem of (unfortunately, Gallery has stopped), I thought it'll end up as soon as the next nightly will fix it.
I tried most of CM9 nightlies, the stable CM9, many CM10 nightlies and finally I'm on the stable CM10, still I have the camera problem. I've flashed it many times, odin it to stock and flash back to CM7/9/10, but it didn't work, the camera stopped working even in the stock version. I thought maybe the camera is broken but today the I reflashed CM10 and it worked, now it's back to same problem.
Any ideas folks?? Thanx and sorry for the long story
Sent from my SGH-T959 using xda app-developers app
Try going to settings> manage apps> all> gallery> clear cache and reboot.
What you don't know could fill a book.
Just tried it, didn't work
Gladiolur said:
Just tried it, didn't work
Click to expand...
Click to collapse
Get me a logcat.
Camera problem
Hope this is what you asked for,
Saif,
Gladiolur said:
Hope this is what you asked for,
Saif,
Click to expand...
Click to collapse
Almost. You need to run "su" before you run logcat when you do it with the terminal else it will only capture a crippled version of logcat because apps in Jelly Bean are restricted to only getting their own logcat unless they're root.
I've done it, the window keeps filling up with new sentences for two hours and didn't stop, I didn't actually know when to copy the logcat!!