Hi,i have the latest cm10 nightly build installed on my galaxy pad 2 10.1 p5113 and when i open the default camera app it always says 'insert an sd card before using the camera' and i cant record anything except in the panorama mode,my 32gb patriot micro sd card is recognized by everything else on the tablet including es file explorer,cool reader etc.
On the stock 4.04 the default camera works,was wondering if anyone else had this issue,i searched the forums and read the known issues but nothing was said about the camera app.
May be try to delete cash of app or try to install ics camera app from market or i think their is setting in app to change storage permanently try it
Sent from my GT-P5100 using xda app-developers app
Already have done those suggestions.
1- I think their is build 27/8 try it make sure it is for 5113
2- Or try delete cash and dalvik cash noooooo factory reset in cwm also try fix permissions in cwm then reboot and see
3- If problem persists try alternative cam app temporarily write cam in google play search
Sent from my GT-P5100 using xda app-developers app
I have installed all the nightly builds since the stable version and all of them have the same problem,i did install zoom camera and it works ok.I'll just wait and see if any newer builds will have the camera working for my p5113,i have tried everything that can be done such as installing the stock rom and then installing the nightly builds with wipe data /factory reset and wipe cache partition and also wipe dalvik cache.
Related
Alright so I did the whole CM7 R11 trick to have twrp. Now after all that I went back to flash gapps, Google works but the market isn't there. I've done everything but go back to one click and redo everything. Also when I was on cm7 (I'm on mokee now testing to see if it wasn't cm7 only) after clearing cache and dalvik, fixing permissions, a lot of things started to force close. Any advice/help will be appreciated
I would suggest you reformat your SD Card from blue CWM with 2048 partition and 0 swap and reflash. Make sure to backup your SD Card before doing this. I had the same problem and that fixed it for me.
When I went from bml to cm711twrp I skipped the beginning part where it said to sign in or create and it wasn't there. So I did a factory reset/system wipe and installed cm711 and flashed gapps again. I signed in and it was the "market". I then got a fc b/c it updated to the play store.
Sent from my SGH-T959V using XDA
I'll give both advices a try and see which one works. Thanks guys
Sent from my cm_tenderloin using XDA
goddi2010 said:
When I went from bml to cm711twrp I skipped the beginning part where it said to sign in or create and it wasn't there. So I did a factory reset/system wipe and installed cm711 and flashed gapps again. I signed in and it was the "market". I then got a fc b/c it updated to the play store.
Sent from my SGH-T959V using XDA
Click to expand...
Click to collapse
It worked!! Thanks again goddi
Sent from my cm_tenderloin using XDA
I've already flashed a custom recovery image of ClockworkMod Recovery 5.8.3.1 and have rebooted into recovery, which works fine.
I have Downloaded the latest version of CyanogenMod and gapps-ics and placed on the root of the sd card in my xoom. I have also tried this by placing this in the root on the internal storage but I am having the same issue here.
I can wipe data/factory reset fine, as well as wipe cache no issues, but then when I go into install zip from SD card, then choose zip from sd card I get the line E:Can't mount /sd/card/ so can't install the zips cm-9.0.0-rc1-wingray or gapps-ics
Any thoughts on what might be the issue here, and why I cant get to the zips. As I said I have tried this both ways, having the zips on the internal storage and on the actual SD card.
HELP! So so fed up with v3.2 I need CM9 on this!
I don't know if the message is caused by the launcher. I would disable the signature check and try again.
Sent from my SGH-I897 using xda app-developers app
nliu0704 said:
I don't know if the message is caused by the launcher. I would disable the signature check and try again.
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
I had the same problem, did a few google searches which indicated there was a problem with that version of ClockworkModRecovery, i ended up reflashing with ClockworkMod 3.2.0.0 (R4c) and all was fine after that.
Hope that helps,
K
Thanks will give that a go and post back later for if it helps others.
Sent from my LT26i using xda app-developers app
Hi everyone,
I have TF101 with the Team EOS JellyBean ROM,
When I try to open the Play Store or download files in the browser, I get force close of "Android.Process.Media" and then the store/browser force closes too.
Any help would be much appreciated as I can't install apps on my tablet currently.
corydor13 said:
Hi everyone,
I have TF101 with the Team EOS JellyBean ROM,
When I try to open the Play Store or download files in the browser, I get force close of "Android.Process.Media" and then the store/browser force closes too.
Any help would be much appreciated as I can't install apps on my tablet currently.
Click to expand...
Click to collapse
Go to settings ->applications->all
scroll down to "Google services framework" and clear cache and data, now scroll down to play store and wipe cache and data again... just for good measures wipe data from all Google related apps...
Now restart and go to recovery->advanced->fix permissions-> wipe dalvik cache and cache and restart your tablet... this should work....
If doesn't then wipe everything and reinstall the from from scratch....
Sent from my Transformer TF101 using xda app-developers app
udupa82 said:
Go to settings ->applications->all
scroll down to "Google services framework" and clear cache and data, now scroll down to play store and wipe cache and data again... just for good measures wipe data from all Google related apps...
Now restart and go to recovery->advanced->fix permissions-> wipe dalvik cache and cache and restart your tablet... this should work....
If doesn't then wipe everything and reinstall the from from scratch....
Sent from my Transformer TF101 using xda app-developers app
Click to expand...
Click to collapse
I just tried this and after the reboot I was still getting the force close, so I reinstalled the ROM and the problem was still there. Don't know what to do.
I am also confused as when I install a different jellybean ROM, my home screen layouts are all still the same, even if I wipe the system.
corydor13 said:
I just tried this and after the reboot I was still getting the force close, so I reinstalled the ROM and the problem was still there. Don't know what to do.
I am also confused as when I install a different jellybean ROM, my home screen layouts are all still the same, even if I wipe the system.
Click to expand...
Click to collapse
What recovery r u using ? Try TWRP... download TWRP AND INSTALL IT by flashing it through recovery.....
1) wipe your external SD CARD CLEAN
2) copy say AOSP JB and TWRP to your now clean SD card
3) go to recovery and flash TWRP first and reboot again into recovery.
4) now wipe system, cache, dalvik, system and internal memory using wipe option
5) now flash ASOP JB and once done just wipe dalvik and restart...
Hopefully this should work....
Sent from my Transformer TF101 using xda app-developers app
I'm already using TWRP, I had to install it because I was stuck on CWM. I'm using a SD that's brand new too! .. so confused. The card was clean when I first installed JB on my tablet. I had just downloaded the ROM and flashed. But from the start I was getting Force Closes...
corydor13 said:
I'm already using TWRP, I had to install it because I was stuck on CWM. I'm using a SD that's brand new too! .. so confused. The card was clean when I first installed JB on my tablet. I had just downloaded the ROM and flashed. But from the start I was getting Force Closes...
Click to expand...
Click to collapse
Go to twrp-> wipe-> system wipe, dalvik wipe, cache wipe, internal memory wipe and format system... these will clean your tablet of any old android files and its totally clean.. now go under storage and mounts and mount storage and format storage after these steps reinstall.. I'm running on AOSP without any issues...
Sent from my Transformer TF101 using xda app-developers app
udupa82 said:
Go to twrp-> wipe-> system wipe, dalvik wipe, cache wipe, internal memory wipe and format system... these will clean your tablet of any old android files and its totally clean.. now go under storage and mounts and mount storage and format storage after these steps reinstall.. I'm running on AOSP without any issues...
Sent from my Transformer TF101 using xda app-developers app
Click to expand...
Click to collapse
Should I try a different JB ROM instead of the Team EOS one? Could you link to the thread with the one you use possibly?
corydor13 said:
Should I try a different JB ROM instead of the Team EOS one? Could you link to the thread with the one you use possibly?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=28915296
Download superuser, latest AOSP ROM, harmony kernel for JB, and Google apps from above link.. and flash kernel 1st through recovery, restart wipe everything present on internal memory (refer previous post), then flash the AOSP JB ROM (release 3).... all are in above link read and do properly and you should not see any issues...
Sent from my Trnsformer TF101 using xda app-developers app
udupa82 said:
http://forum.xda-developers.com/showthread.php?p=28915296
Download superuser, latest AOSP ROM, harmony kernel for JB, and Google apps from above link.. and flash kernel 1st through recovery, restart wipe everything present on internal memory (refer previous post), then flash the AOSP JB ROM (release 3).... all are in above link read and do properly and you should not see any issues...
Sent from my Trnsformer TF101 using xda app-developers app
Click to expand...
Click to collapse
I did all the wipes you said, pressed on format and it failed. I proceeded to flash the AOSP JB ROM anyway, and when it booted, I had the same force closes again. I'm so confused. It had completely wiped the data from my tablet, but the home screen was still how it was before and the wallpaper the same...
corydor13 said:
I did all the wipes you said, pressed on format and it failed. I proceeded to flash the AOSP JB ROM anyway, and when it booted, I had the same force closes again. I'm so confused. It had completely wiped the data from my tablet, but the home screen was still how it was before and the wallpaper the same...
Click to expand...
Click to collapse
X
Did you flash harmony kernel... ? Do exactly what I say, when you go to twrp recovery flash harmony kernel and restart and get back into recovery... now go to wipe and wipe everything expect external memory ( cache, dalvik, system, internal memory) after all these now flash the AOSP JB ROM and wipe dalvik/cache after installation.. now flash superuser which you downloaded from the link within AOSP... important is try AOSP ROM WITH HARMONY KERNEL... leave team EOS JB for now...
Sent from my Transformer F101 using xda app-developers app
If you talking about just the wallpaper (green leaf wallpaper ) p, then green wallpaper is same for both ROMs as its the default wallpaper of JB... go to settings and find out what ROM you running on... also try clearing data of applications which are FCing....
Sent from my Transformer TF101 using xda app-developers app
udupa82 said:
If you talking about just the wallpaper (green leaf wallpaper ) p, then green wallpaper is same for both ROMs as its the default wallpaper of JB... go to settings and find out what ROM you running on... also try clearing data of applications which are FCing....
Sent from my Transformer TF101 using xda app-developers app
Click to expand...
Click to collapse
I did all of the wipes in the order you said, I flashed the harmony kernel and the AOSP JB ROM, and still get all the force closing of android.process.media.
I selected the orange canyon kind of wallpaper when I was in Team EOS and when the AOSP ROM booted, it was that wallpaper. Even though I know it should be the leaf one. All my widgets were still there too. Even though in the settings menu it said it was running on the AOSP ROM.
I have the Samsung Galaxy S3 (verizon), and I am having quite a few problems that no one else seems to be having. Have have searched the forums, googled the problems, and done every kind of troubleshooting that I can think of (will list).
Problems:
Rom: ParanoidAndroid (jellybean
Issue: Wifi does not work in tablet, phablet, or hybrid mode. Camera does not save pictures.
Troubleshooting: Data wipe/restored to backup. Data wipe reinstalled rom, gapps, wiped cache, wiped Dalvik. Clear data in framework, media, and gallery.
Rom: LiquidSmooth (jellybean)
Issue: Camera not saving images.
Troubleshooting: Same as above.
Rom: MiUi (jellybean)
Issue: Camera not saving pictures, No ext sd card support. (not going to list known issues since that would be redundant)
Troubleshooting: Same as above.
Again, I have googled all of the issues. Tried as many fixes as I could find. If I am being a noob then please just tell me. If there are step by step instructions that I have missed please point me in the right direction. Would love to get one of these roms working today before I have to go to work
Still need help with this. Going through the QandA forum for the 100th time now searching for a fix....
The ext. sd card issue seems to be a common thing happening in some of these roms mainly CM based. The fact its happening on MiUi is new to me (haven't read that, nor have I researched it). As far as the camera saving pictures goes, I assume you have tried changing the default storage location from internal to external? The fact that you have the same issue on multiple roms leads me to a hardware malfunction issue, in which case a factory reset would be in order as first on the list of things to do to fix it. Did the camera save when you were in any form of stock rooted/unrooted?
No, I didn't change the storage from external to internal. I have searched up and down for the setting and cannot find it. Yes, everything is functioning correctly on the stock rom. Just getting frustrated considering I love miui and still cannot get sd or cam support. Don't mean to be stupid, just trying to get this all straight.
The setting will be in the camera app itself.
Sent from my SCH-I535 using xda premium
Went into the camera app again, no settings for storage location. Tried restarting also, no luck just tries to "activate" my service over and over. Tried the menu button in the camera app and nothing. Really didn't want to factory reset... Guess I'll try that. Gotta ask is that gonna make my root go away? Also do I need to restore to a stock rom before I reset it?
Flash on synergy or clean rom and see if it happens then, jb may not be responding well to your device for some reason.
Sent from my SCH-I535 using xda premium
Hi, hoping for some help. I am running PAC-rom (latest nightly) and am encountering the following situation.
My phone and internal memory (sdcard0) works fine without a microsd plugged in.
As soon as I plug in any Microsd (tried a 32gb and 4gb and 8gb) the phone loads the contents of the microsd (external and sdcard1 I believe), but then sdcard0 does not get mounted.
Seems it only wants to run one or the other. I have tried searching and came across ideas of formatting etc, but nothing seems to get them to work together. Has anyone else encountered this? Any ideas?
Let me know if any additional information is required to troubleshoot.
Thanks!
Sounds like a software fluke ... Try falling back to the latest stock ROM ucmc1 via Odin and perform cleanup ... Wipe and factory reset. Then do a clean install if your favorite custom ROM following their installation directions from their xda page.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
I'm also having the same issue. Have took it it re-inserted, wiped it, nothing fixes it. I'm running CM10 with twrp
Sent from my SAMSUNG-SGH-I727 using XDA Premium 4 mobile app
I haven't gone to stock but have the issue on the latest CM as well as PACman.
I guess a better question would be whether anyone running these roms DOES NOT have the issue?