Related
I just installed Starburst on my phone and evertyhing works great with the exception of the default phone app. Whenever i try to launch it i just get a black screen then a popup saying the process android.process.acore has stopped unexpectedly and it tells me to force close.
Anyone else ever get this and find a solution?
Sometimes the installation can go wrong. Juat wipe ecerything, THREE TIMES EACH, cacha, data, n dalvik. also download starburst 1.7 again (just in case), and flash it. U shud not have any issues.
Sent from my SPH-D710 using xda premium
I just flashed to version 1.8 after formating usb under storage then wiping data/cache/dalvik each 5x and am still getting the same force close on the stock dialer. Everything else works fine so i'll probably stick with this rom for a little bit.
LordFan21 said:
I just flashed to version 1.8 after formating usb under storage then wiping data/cache/dalvik each 5x and am still getting the same force close on the stock dialer. Everything else works fine so i'll probably stick with this rom for a little bit.
Click to expand...
Click to collapse
Format system.
Sent from my SPH-D710 using XDA App
Formatting system fixed it thanks. I got storage and system confused when reading your directions.
LordFan21 said:
Formatting system fixed it thanks. I got storage and system confused when reading your directions.
Click to expand...
Click to collapse
No Worries.
Sent from my SPH-D710 using XDA App
This might not have something to do with JellyKing per se but the error occurred after flashing the 2.0 version.
Now when I start my phone I always get "System UIDs Inconsistent" I formatted data, system, ext and so on and nothing did work. I also tried the factory reset over and over also trying different versions of JellyKing and nothing did work so far, also tried the Fix Permissions with no result.
I really need help to fix this so my phone is actually usable again.
Oh and the gapps process is crashing all the time so that I can't finish the installation phase in the beginning. But when I flash the latest gapps lite I don't get the setup process with language selection and so on. But that may fix the initial issue though.
Okay ran into the problem with that, I seem to have no keyboard.
hinogi said:
This might not have something to do with JellyKing per se but the error occurred after flashing the 2.0 version.
Now when I start my phone I always get "System UIDs Inconsistent" I formatted data, system, ext and so on and nothing did work. I also tried the factory reset over and over also trying different versions of JellyKing and nothing did work so far, also tried the Fix Permissions with no result.
I really need help to fix this so my phone is actually usable again.
Oh and the gapps process is crashing all the time so that I can't finish the installation phase in the beginning. But when I flash the latest gapps lite I don't get the setup process with language selection and so on. But that may fix the initial issue though.
Okay ran into the problem with that, I seem to have no keyboard.
Click to expand...
Click to collapse
This is due to...improper mount of ext partition & flash ..so do a clean wipe...& reinstall Romok
Sent from my HTC Wildfire S A510e using Xparent Cyan Tapatalk 2
kantry123 said:
This is due to...improper mount of ext partition & flash ..so do a clean wipe...& reinstall Romok
Sent from my HTC Wildfire S A510e using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
I wiped everything except the sdcard and had that problem.
Hey guys,
I recently moved to the gs3 and jelly bean so this may be a known solution but for the life of me I can't find it. I've tried liquid 2.1 and 2.2 both with multiple gapps and still have the problem on clean wipes. Phone itself is only a day old.
When I start my camera it lags for a minute showing no picture then crashes, saying gallery has stopped. The funny thing is it actually WORKED before I updated my google apps through play? Worked fine on original rom also. This is driving me nuts as it is literally my only problem and I need my camera, but love this rom.
Thanks!
EDIT: BTW. Gallery starts fine on its own and I've tried the camera32_patched_v2.zip fix I found on another site and no luck(just have two camera icons and both do same thing)
thegrog said:
Hey guys,
I recently moved to the gs3 and jelly bean so this may be a known solution but for the life of me I can't find it. I've tried liquid 2.1 and 2.2 both with multiple gapps and still have the problem on clean wipes. Phone itself is only a day old.
When I start my camera it lags for a minute showing no picture then crashes, saying gallery has stopped. The funny thing is it actually WORKED before I updated my google apps through play? Worked fine on original rom also. This is driving me nuts as it is literally my only problem and I need my camera, but love this rom.
Thanks!
EDIT: BTW. Gallery starts fine on its own and I've tried the camera32_patched_v2.zip fix I found on another site and no luck(just have two camera icons and both do same thing)
Click to expand...
Click to collapse
Clear data on the gallery app (settings/ manage applications, or something along those lines) go to all apps and find gallery, clear data on it and try to use the camera again..
SPRINT GS3 FAQ
flastnoles11 said:
Clear data on the gallery app (settings/ manage applications, or something along those lines) go to all apps and find gallery, clear data on it and try to use the camera again..
SPRINT GS3 FAQ
Click to expand...
Click to collapse
I've tried that. Still no luck.
thegrog said:
I've tried that. Still no luck.
Click to expand...
Click to collapse
Are you downloading your GAPPS from goo.im? If so, are they the 4.2.2 version?
Android Attack said:
Are you downloading your GAPPS from goo.im? If so, are they the 4.2.2 version?
Click to expand...
Click to collapse
Yes and yes. I've tried gapps-jb20121011 and 20130301, both on liquid 2.1 and 2.2. Clean wiped each time. Same thing with camera always. Grey screen when it starts and then shortly after opening it crashes with gallery error.
thegrog said:
Yes and yes. I've tried gapps-jb20121011 and 20130301, both on liquid 2.1 and 2.2. Clean wiped each time. Same thing with camera always. Grey screen when it starts and then shortly after opening it crashes with gallery error.
Click to expand...
Click to collapse
Did factory reset first from settings(not sure if you should do this from inside a rom but oh well) and then rebooted into recovery. Tried rewiping and reinstalling again... Cleared cache, divak. used liquid 2.2 and jb2012011 which goo.im says is correct, fixed permissions. Got constant com.google errors and couldn't run initial setup had to put 20130301 just to get to setup and have phone back running again. Camera still broke(this time I tried before any updates again and it didn't even work then). What am I doing wrong?
thegrog said:
Did factory reset first from settings(not sure if you should do this from inside a rom but oh well) and then rebooted into recovery. Tried rewiping and reinstalling again... Cleared cache, divak. used jb2012011 which goo.im says is correct, fixed permissions. Got constant com.google errors and couldn't run initial setup had to put 20130301 just to get to setup and have phone back running again. Camera still broke(this time I tried before any updates again and it didn't even work then). What am I doing wrong?
Click to expand...
Click to collapse
Not sure if this will help, but I suggest: Do factory reset from custom recovery, wipe cache and dalvik. Then, install the latest M Snapshot of CyanogenMod found here. Then flash the latest 4.2.2 GAPPS from here. Reboot into system, try out the camera and check if it works. If it works on CM, do factory reset, wipe cache and dalvik then install Liquid Smooth. Good luck!
Android Attack said:
Not sure if this will help, but I suggest: Do factory reset from custom recovery, wipe cache and dalvik. Then, install the latest M Snapshot of CyanogenMod found here. Then flash the latest 4.2.2 GAPPS from here. Reboot into system, try out the camera and check if it works. If it works on CM, do factory reset, wipe cache and dalvik then install Liquid Smooth. Good luck!
Click to expand...
Click to collapse
Update... I've been busy and have not had time to redo the phone again today, and I'm already 4 /0 folders deep(wtf 4.2?).
Here is the thing.. the camera started working out of the blue. I had the phone up for about 4-5 hours and randomly opened camera(which i keep doing) and it finally worked! I was able to take pics. Then my battery died... and now the camera is borked again after restarting. This is driving me insane. Any idea what is going on?
thegrog said:
Update... I've been busy and have not had time to redo the phone again today, and I'm already 4 /0 folders deep(wtf 4.2?).
Here is the thing.. the camera started working out of the blue. I had the phone up for about 4-5 hours and randomly opened camera(which i keep doing) and it finally worked! I was able to take pics. Then my battery died... and now the camera is borked again after restarting. This is driving me insane. Any idea what is going on?
Click to expand...
Click to collapse
Charged for a bit and was able to start camera on second try then it would not reopen no matter what I did. Restated a few times and everything. This is going to make me crazy lol.
thegrog said:
Update... I've been busy and have not had time to redo the phone again today, and I'm already 4 /0 folders deep(wtf 4.2?).
Here is the thing.. the camera started working out of the blue. I had the phone up for about 4-5 hours and randomly opened camera(which i keep doing) and it finally worked! I was able to take pics. Then my battery died... and now the camera is borked again after restarting. This is driving me insane. Any idea what is going on?
Click to expand...
Click to collapse
What I recommend doing is having phone charged to at least 70%, using Titanium Backup to restore your apps, and follow these instructions to the dot. This is what I did while using TWRP 2.5.
1) redownload LS v2.2 and gapps 20130301
2) backup all apps to TB
3) boot into TWRP
4) select 'Wipe' then 'Advanced Wipe'
5) wipe dalvik cache, system, data, cache
6) flash ROM then gapps
7) go back to 'Advanced Wipe' and wipe cache and dalvik cache again ONLY
8) reboot and run through setup wizard
9) immediately go into Play Store and cancel all installing apps.
10) install TB and restore user apps from there
11) reboot
now test out the camera
Sent from my SGH-T999 using xda premium
LuigiBull23 said:
What I recommend doing is having phone charged to at least 70%, using Titanium Backup to restore your apps, and follow these instructions to the dot. This is what I did while using TWRP 2.5.
1) redownload LS v2.2 and gapps 20130301
2) backup all apps to TB
3) boot into TWRP
4) select 'Wipe' then 'Advanced Wipe'
5) wipe dalvik cache, system, data, cache
6) flash ROM then gapps
7) go back to 'Advanced Wipe' and wipe cache and dalvik cache again ONLY
8) reboot and run through setup wizard
9) immediately go into Play Store and cancel all installing apps.
10) install TB and restore user apps from there
11) reboot
now test out the camera
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Did exactly that.. except installed newest cm10.1 M instead of liquid just to test. Same issue. Camera seems to work randomly but most of the time get the gallery has stopped error. Wtf?
thegrog said:
Did exactly that.. except installed newest cm10.1 M instead of liquid just to test. Same issue. Camera seems to work randomly but most of the time get the gallery has stopped error. Wtf?
Click to expand...
Click to collapse
Is there a zip for the old camera to add it back? I just need a working camera don't care which it is.
Have you tried this one? The gallery seems to work. Maybe it will for you too
http://forum.xda-developers.com/showthread.php?t=1966426
Sent from my Nexus 4 using xda premium
---------- Post added at 08:29 PM ---------- Previous post was at 08:19 PM ----------
You can also try the Note 2 repacked camera
http://db.tt/i2BOv4Ax
Sent from my Nexus 4 using xda premium
Does it give you an error, or just close out, FC, any thing? Sounds like an issue that may need some other type of edits. Oh and update your recovery, that's why you have multiple /0 folders....
mt3g said:
Does it give you an error, or just close out, FC, any thing? Sounds like an issue that may need some other type of edits. Oh and update your recovery, that's why you have multiple /0 folders....
Click to expand...
Click to collapse
It force closes with gallery has stopped error
look through this and try it out http://forum.xda-developers.com/showthread.php?t=2102981&highlight=camera+connect
LuigiBull23 said:
Have you tried this one? The gallery seems to work. Maybe it will for you too
http://forum.xda-developers.com/showthread.php?t=1966426
Sent from my Nexus 4 using xda premium
---------- Post added at 08:29 PM ---------- Previous post was at 08:19 PM ----------
You can also try the Note 2 repacked camera
http://db.tt/i2BOv4Ax
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Didn't work same issue
Tried some of the fixes from that thread too and nothing...
My question now is, I've seen someone saying turning on geotagging fixed the issue. I always turned it off when camera starts the first time, is there some way to turn it back on without redoing rom? Installing that other cam didn't even give me the option again and can't find it in settings.
Still can't get this camera working. Have not even been able to get it to work at all for 2 days now. Someone has to have an idea?
Solution - switch roms. You aren't stuck with roms. Try the aokp port. It's good. So is cm.
Sent from my SPH-L710 using xda app-developers app
WindroidApps said:
Solution - switch roms. You aren't stuck with roms. Try the aokp port. It's good. So is cm.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I HAVE switched to cm, I'm running it right now. Same exact issue. Works once in a blue moon but usually gallery has stopped and force close of camera. Worked on stock, this is a brand new replacement I got last week.
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] Phone was fine, ran out of battery, now "System Ui Has stopped" every few seconds
Hey,
Note 2 running PACMAN rom, android 4.3.
I woke up and checked it at 8am, no problems at all. Went to use it at 1pm and it had run out of battery. I plugged it into my computer to charge it, turned it on and it said "System UI has stopped. Blame Tyler" - and continues to do this every time you press OK, with about a 3 second gap in between each one.
I restart my phone quite regularly and I don't think I've installed anything that could be causing this. I've disabled XPosed but same problem. Any other ideas? Otherwise I'll have to just wipe it and start again, perhaps with CM. I need a working phone for tomorrow though!
Cheers
Maybe a silly question, but have you wiped cache and dalvik cache from recovery? If not try it.
Sent from my GT-N7100 using Tapatalk
chandoliasnikos said:
Maybe a silly question, but have you wiped cache and dalvik cache from recovery? If not try it.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
This seems quite sinisiter - thanks for the suggestion but it hasn't worked, and it's unearthed something more concerning about the state of my phone (the TWRP messages, see below). Can't believe I didn't think to do that myself though! (I haven't messed around with ROMs for quite a while so am out of practice, I've had this one for a few months).
Delvik cache completed, then said something like "updating partition details. E: Error opening '/data/system/...." I/O Error" and various APKs - one of which was system UI. Wiping the cache again told me done, but loads of errors of similar APKs (This time in /data/data/ though). This sounds incredibly ominous though and I've never seen that error before in any of the wipes or anything I've done.
Restarted it but the system UI error messages persist. I want to wipe and install a fresh ROM but I'm worried I'm going to be left with a totally useless phone if things won't wipe or flash properly. Any ideas would be great.
If anything goes wrong u still have the option to flash a new rom through odin.
Sent from my GT-N7100 using Tapatalk
chandoliasnikos said:
If anything goes wrong u still have the option to flash a new rom through odin.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
I'm currently downloading a rom to flash with odin. I tried to do a nandroid backup but the same I/O errors appeared. I have no idea what could have caused this as the phone was running absolutely fine yesterday!
try to fix permissions in recovery. On HD2 it helped in 90% of the cases
yaro666 said:
try to fix permissions in recovery. On HD2 it helped in 90% of the cases
Click to expand...
Click to collapse
Yup. This might be the solution.
Helped me 90% of the times. Go to TWRP -> Advanced -> Fix Permissions
Sent from my GT-N7100 using Tapatalk