I just installed the 4.2 apps zip from http://phandroid.com/2012/11/06/android-4-2-gapps-package-download/
and the camera keeps FCing on me. It will take 1 picture then freeze on that picture, and close and cant open it again, nor did the picture actually save. Ive tried to reinstalled other signed gapps zips and even upgraded on my CM10 nightly to the latest one but still nothing.
is there specific instructions to remove camera?
First, this is the development section, not the Q&A section. You'll probably get more help if you posted this in the right sub-forum.
Second, why didn't you make a nandroid before you flashed the apps zip?
You need to tap on the screen before you take the picture because auto focus is wacky. If you do that you can take multiple pictures without the camera app locking up.
It has been proven this is the work around for now.
Sent from my SCH-I535 using Tapatalk 2
imp3r10 said:
I just installed the 4.2 apps zip from http://phandroid.com/2012/11/06/android-4-2-gapps-package-download/
and the camera keeps FCing on me. It will take 1 picture then freeze on that picture, and close and cant open it again, nor did the picture actually save. Ive tried to reinstalled other signed gapps zips and even upgraded on my CM10 nightly to the latest one but still nothing.
is there specific instructions to remove camera?
Click to expand...
Click to collapse
You need to use a root explorer and go into your system folder and delete it that way then you will have only your original camera
Sent from my SCH-I535 using xda premium
I have my bone stock VZ GS3 that got the official OTA for JB 4.1.1.
Since the update whenever I launch Navigation it will open, location lock, get desired directions, and usually crash within a few minutes.
I think it has something to do with Maps because when I check the Play Store, a lot of other GS3 users have been complaining of similar issues since the update.
Now is there anything that can be done on my end to possibly help? Or am I just stuck waiting for an update to the app?
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
sorry about that.
Anyone have any ideas?
bump?
No one else with this problem stock?
Talked to a couple friends today who are on other ROMS and Nav/Maps works fine for them
Have you tried going into application manager, force stop, and clear data? If that doesn't work, I would reboot into recovery, wipe caches, and fix permissions,
I had a similar problem and this worked for me,
HHF2 said:
Have you tried going into application manager, force stop, and clear data? If that doesn't work, I would reboot into recovery, wipe caches, and fix permissions,
I had a similar problem and this worked for me,
Click to expand...
Click to collapse
I have not tried that. Ill give it a shot, thanks!
I cant say ive experienced that exact problem, but since the OTA i have had a bunch of other bugs that werent present prior to the update. Many threads online about them also. Factory reset has helped some, but not all.
So I think the issue is still related to the JB update.
I did what HHF2 suggested and it didnt help. I have a couple friends running the latest milestone ROM from AOKP and their Maps/Nav works just fine.
So I rooted, unlocked, and ROM'd to the same one....only to continue to get force closes, to the point where within 2 blocks today, it closed 6 times..
Talking to one of the friends tonight, I found out that they never installed the official JB OTA, they went from ICS to the AOKP JB ROM. So that is bringing me back to think that something in the update screwed things up
Ok sooooooo
I flashed back using Odin to bone stock 4.0.4 Then rooted/unlocked BL/CWM. Then flashed the AOKP ROM and Gaaps, Nav/Maps STILL crashes
idk wtf is up
Try all of the following
Clear data for Maps
Clear data for Google Services Framework
Uninstall and Reinstall Maps and Naviation
Fix Permissions (custom recovery > advanced)
You could download an .apk for an older version of maps/nav to confirm if it's the latest release.
If all of that doesn't work and you still get Force Closes, then something deeper is going on. Download a logcat script capture (I use aLogCat) and post your results after replicating the FC. Hope this guidance helps you in some way. GL.
sweeds said:
Try all of the following
Clear data for Maps
Clear data for Google Services Framework
Uninstall and Reinstall Maps and Naviation
Fix Permissions (custom recovery > advanced)
You could download an .apk for an older version of maps/nav to confirm if it's the latest release.
If all of that doesn't work and you still get Force Closes, then something deeper is going on. Download a logcat script capture (I use aLogCat) and post your results after replicating the FC. Hope this guidance helps you in some way. GL.
Click to expand...
Click to collapse
Did the 4 bullet points in that order. So far, things seem to be a bit better, but it still says "searching for GPS" but at the same time I dont get great service inside my house. So tonight when I head out ill see if I can get a GPS lock on.
Even before when it was "searching for GPS" I could move the map around zoom in/out and it would force close after just a few seconds. Its better because I can scroll around and it hasnt closed yet.
Thanks
Glad to hear there is some improvement!
Download an app called GPS Status. It will tell you how many Satellites you're locked onto, and you can download the aGPS patch fix.
Sent via SGS3 using Tapatalk
Well now that I'm out of the house it has FC on my twice within 3mins
Think I'll try an older version APK. Any idea where to start my search for that?
I went back and read the GS3 reviews on Maps in the play store and a lot of ppl have the same issues
Sounds like it may be a bug in the latest version of GMaps.
Previous Google Maps apk:
http://www.eapktop.com/tag/google-maps-apk
Sent via SGS3 using Tapatalk
I went to that site and downloaded a .zip file of a previous version. Do I just load the whole .zip file from CWM? I didnt see (may have missed it) any APKs, they all seemed to be market links or .zip
I also just installed aLogCat. Booted Navigation and after it crashed I opened LogCat and it said "reading logs, please wait" and nothing ever happened.
stupidchicken03 said:
I went to that site and downloaded a .zip file of a previous version. Do I just load the whole .zip file from CWM? I didnt see (may have missed it) any APKs, they all seemed to be market links or .zip
I also just installed aLogCat. Booted Navigation and after it crashed I opened LogCat and it said "reading logs, please wait" and nothing ever happened.
Click to expand...
Click to collapse
I assume you just need to unzip the file and there's an apk in there.
For aLogCat, make sure you hit the play button first off. Also, go into settings and make sure the level is set to "verbose"
Sent via SGS3 using Tapatalk
Already tried unzipping it but there are no APKs in there.
For aLogCat, it was already set to verbose and when I open the program it says its running and only has the "pause" button. If I hit pause, I can then hit play, but it doesnt do anything again.
Google Maps APK Links:
http://www.androiddrawer.com/6632/download-maps-6-12-0-app-apk/#.USKzelqY5b0
Current version is 6.14.2, if you look on the right-hand side you can see different versions. This link is for the last major release, 6.12.0.
I recommend clearing Google Maps data, uninstall, then install using the prev version release apk. If the FC's stop, then we can confirm that the problem is a bug in the latest update to the app. Good luck :good:
sweeds said:
Google Maps APK Links:
http://www.androiddrawer.com/6632/download-maps-6-12-0-app-apk/#.USKzelqY5b0
Current version is 6.14.2, if you look on the right-hand side you can see different versions. This link is for the last major release, 6.12.0.
I recommend clearing Google Maps data, uninstall, then install using the prev version release apk. If the FC's stop, then we can confirm that the problem is a bug in the latest update to the app. Good luck :good:
Click to expand...
Click to collapse
Did all that and installed both 6.12 and 6.10 versions with no luck
I honestly think its something with the JB update and not just Maps.. but then again idk why mine didnt work after using Odin to go back to 4.0.4
The screenshot below is just 5 of the most recent ratings for Maps on the GS3
Both have been fixed but I remain very curious as to WTF, I don't know enough about Android to make any guesses??
Bug 1, running CM 10.1 and somewhere along the line of updating to the latest daily (Maybe March 20, not sure?) my browser began to not work right, I could go to any webpage w/o a problem but if I clicked on a link in the page I was on I would wind up with a blank page. This was not intermittent, it failed every time. I could open a page but could not open any link from the first page.
Bug 2, couldn't fix bug one other than wipe and re-install from scratch (which I did later) so I restored my backup of CleanRom and all seemed well until I tried to install a new app and couldn't get Google Playstore to open. It would say "Loading" and sit there forever. I used the Goo manager to download the latest Google apps and that fixed the problem but.... Playstore worked at the time the backup was made and was set to automatically update. After the restore it didn't try to update, it just hung trying to open.
Again, both are fixed, bug 1 by a fresh install of CM 10.1 and bug 2 by a new download of GAPPS but I'd sure like to know what caused the hiccups....
All your files were moved to a 0 folder and that's why you can't get anything loaded up on cleanrom and you don't need to flash gapps and touch wiz roms. And also aosp rooms aren't always gna be 100% perfect since there will be bugs so don't be complaining about having problems.
Sent from my SCH-I535 using xda app-developers app
If you have no idea what you're talking about and you (obviously) didn't read my post, please don't reply, OK? Thanks.
It happens when I open pages with flash. Dolphin browser too. On another Nexus s same problem. Can somebody explain?
ezantera said:
It happens when I open pages with flash. Dolphin browser too. On another Nexus s same problem. Can somebody explain?
Click to expand...
Click to collapse
The crashed should cased by flash plugin, as no one will update stock browser for you, you can send a request to dolphin team, using the email left on the google play store: [email protected]. Add "Comes from XDA" mark may help.
Update? Hm, I am on CM10.1 RC5. Somehow I cannot believe I need to install nightly to get a stable browser. I tried stable CM10.0, same thing... I am thinking I need to wipe sdcard, because that is only thing I did not do. I changed kernels, CM versions, even Miui.. on all of then browser is crashing..
Aaeon said:
The crashed should cased by flash plugin, as no one will update stock browser for you, you can send a request to dolphin team, using the email left on the google play store: [email protected]. Add "Comes from XDA" mark may help.
Click to expand...
Click to collapse
ps. I forgot to mention that I wiped all. cache, data, dalvik, system between trying new rom.
ezantera said:
Update? Hm, I am on CM10.1 RC5. Somehow I cannot believe I need to install nightly to get a stable browser. I tried stable CM10.0, same thing... I am thinking I need to wipe sdcard, because that is only thing I did not do. I changed kernels, CM versions, even Miui.. on all of then browser is crashing..
ps. I forgot to mention that I wiped all. cache, data, dalvik, system between trying new rom.
Click to expand...
Click to collapse
I have found some kernel/rom combos just can't deal with flash. I am very picky and spend an immence amount of time looking around at the most reliable combinations. My best luck (so far) with getting flash playing perfect, no fc and no graphical artifacts is SmoothROM 5.2 (motley kernel at standard settings) if you want to make sure everything has been done right the author also built a great little java applet that will clear all the proper caches and pushes your rom to the "sdcard" partition. I did a full backup and restored the last time and this thing runs so well.
I posted this in the wrong forum, whoops, well I guess I still have advice. Nightly ROMs are not as stable as cooked ROMs, and there will most likely be a really good one for your device that has cm as a base, paranoid/AOKP if you so desire. They tend to get a lot of bugs worked out that the big devs don't have time for.
Sent from my Nexus7
Smoothrom 5.2
Motley [email protected]
I start with a fresh wipe of my phone and then install BeanStalk with gapps (I'm currently using BS version 4.4.275 with gapps 20140105. Everything is fine for months. Then a couple of apps will start to crash a few times (the camera, dialer, browser and google apps). I've stopped using titanium backup and clockwork mod to restore my data because they were causing issues. Then the force closes become more and more frequent. I ran fix permissions and i have know clue if it helped or not. Then finally all hell breaks loose and everything begins to force close and give errors of no space left on phone. No launcher will stay open everything just bugs out. This seems to be an on going matter. It doesn't seem to resolve no matter what rom I run. I've gone through every folder sizing it and my phone is not out of space. I am getting very frustrated with my Infuse. I don't understand what some of the stuff means in my catlog file. If someone could help I'd greatly appreciate it.
i found out that Google+ and Google Drive might be the cause (such as when you upload or backup your photos to those clouds)
if you have time, go read those last 10 pages of BeanStalks, you will see what others have offered to resolve this issues
as for me, I'd do full wipe, specially format the sdcard0 (keep the Rom and Gapps to your SDcard1), and stop using the two Google services mentioned above. and use another Gapps (I am using the minimal one) Good luck!
Same problem with Unofficial CM 11.2 also
Exactly the same issue I am having with Unofficial CM 11.2 from scott.
I have been using Scott Harts Unofficial CM from 10.1 to 11.2 on my Samsung infuse and each time i notice a pattern.
Each of the above ROMs start out pretty smooth, and the phone works without any issues for 6 months or so. Then occasionally and app or two start crashing. Then in a weeks time all hell breaks loose and almost all apps start crashing such that the phone becomes unusable. Especially trebuchet starts crashing and that is the end of story.
In the past i have noticed this happens a month or so after an updated rom has been released and I used to upgrade to the new one and the cycle continues.
I am currently on the latest Unoffical CM 11_2 (Kitkat) and the appropriate Gapps installed and the same issue has happened twice.
I have tried the following to fix the issue and nothing helps
1. Clear data for trebuchet and a bunch of other apps.
2. Reinstall Gapps
3. Wipe Cache >> Wipe Dalvik Cache
4. Wipe Cache >> Wipe Dalvik Cache > install Gapps
5. Wipe Cache >> Wipe Dalvik Cache > install custom Rom >> install gapps >> wipe cache and dalvik again
The only way I have been able to get it working in the past is
1. Wipe data/factory reset > Clear Cache > clear Dalvik cache and possibly reinstall ROM and gapps (not sure, but I guess factory reset also does the trick)
So my phone is stuck in this mode and I would like to help debug the situation. Can someone help with the next steps? So that I can capture all required information before I do a factory reset .
Unable to get RSA prompt
Well I went ahead with a factory reset, installed Unofficial CM11_2 from Scott. Got the latest gapps from goo.im and phone seems normal again. But that is the expected behavior untill it starts acting up again.
I tried a lot to connect the phone through ADB and each time it remains unauthorized.
I tried on 2 different laptops, Windows 7, Windows Vista as well as Ubuntu - it always remained unauthorized and no matter what i tried ... changing USB ports , OS machines...nothing helped.
I never got the RSA signature prompt on my phone so could not do anything with ADB.
Any body has any ideas ?
hemen_kap said:
Well I went ahead with a factory reset, installed Unofficial CM11_2 from Scott. Got the latest gapps from goo.im and phone seems normal again. But that is the expected behavior untill it starts acting up again.
I tried a lot to connect the phone through ADB and each time it remains unauthorized.
I tried on 2 different laptops, Windows 7, Windows Vista as well as Ubuntu - it always remained unauthorized and no matter what i tried ... changing USB ports , OS machines...nothing helped.
I never got the RSA signature prompt on my phone so could not do anything with ADB.
Any body has any ideas ?
Click to expand...
Click to collapse
This has been an issue for a while, if the problem is showing up like this:
http://forum.xda-developers.com/showthread.php?t=2175261
Honestly haven't tried ADB with the newer stuff (namely Beanstalk), I just know that ADB as been a problem in the past for Scott's ROM's.
joel.maxuel said:
This has been an issue for a while, if the problem is showing up like this:
http://forum.xda-developers.com/showthread.php?t=2175261
Honestly haven't tried ADB with the newer stuff (namely Beanstalk), I just know that ADB as been a problem in the past for Scott's ROM's.
Click to expand...
Click to collapse
Yes, it is the same problem. Any suggestions ? How is the AOSP based Carbon ROM, any idea if it has the same issue too ?
hemen_kap said:
Yes, it is the same problem. Any suggestions ? How is the AOSP based Carbon ROM, any idea if it has the same issue too ?
Click to expand...
Click to collapse
Not sure about the other ROM's. I could go on a flashing journey, but I have two new devices I'm getting adjusted to right now. If you are not tied down to CM (don't know if it's your DD), I would suggest trying Carbon or CyanFox.
Me, I didn't need ADB that much at the time so I stuck with what I have. Not a solution, but I hope you find a ROM that works (partnered with a minimal gapps).
joel.maxuel said:
Not sure about the other ROM's. I could go on a flashing journey, but I have two new devices I'm getting adjusted to right now. If you are not tied down to CM (don't know if it's your DD), I would suggest trying Carbon or CyanFox.
Me, I didn't need ADB that much at the time so I stuck with what I have. Not a solution, but I hope you find a ROM that works (partnered with a minimal gapps).
Click to expand...
Click to collapse
Unfortunately the infuse is the only phone I have (so my DD)...but the lure to test the ADB on carbon is also compelling for me. Let me try moving to a non smart phone and try this out.
OK. So i installed the Carbon KK nightly, and encountered the same issue. adb devices always lists the phone as
0123456789ABCDEF unauthorized.
Also i never received the rsa prompt...
Moreover the device key seems to suggest it is some default value as compared to an actual device key.
Got it Working !!!
Ok so finally got it working.
I moved away from Scott's Unofficial CM11_2 on my daily driver and moved to Carbon ROM. Loving the new rom so far.
Once i moved to this ROM, I started adb on my desktop (adb kill-server, adb start-server) and was waiting
then on phone enabled Developer options and Android debugging over USB and connected the phone to desktop, and zingggg I get the RSA prompt.
One important thing it read is that you phone should be unlocked when you connect it to your desktop, so in case you have things like PIN or gestures that lock your screen....ensure that your screen is not locked when the phone is being connected.
Not sure if this was the issue or if it was the CM rom,,,but issue is resolved, I am loving Carbon...so not going back to CM to check the lockscreen theory....but worth a try for someone who is pulling his/her hair out like i was.
Ciao !!!
---------- Post added at 05:00 PM ---------- Previous post was at 04:41 PM ----------
missed mentioning that do not worry about the device id of 0123456789ABCDEF....i noticed it does not change for me even when adb connects properly.
It is the unauthorised state that needs to change to device.
What's the default launcher on Carbon, or does it give you a choice like Beanstalk?
Will be retiring the Infuse soon, so am thinking on what ROM to put on when I go to sell it (or give away). The requirement is that is not overwhelming to a new user. Cyanogenmod has a lot of customization, but it doesn't necessarily get in the way. I'd call it borderline overwhelming. Beanstalk is quite overwhelming, because you are forced to pick a launcher right from the beginning (even though I like it for the Jellybean qualities).
Because of these, I just may return it to stock, but have it rooted and with CWM.
joel.maxuel said:
What's the default launcher on Carbon, or does it give you a choice like Beanstalk?
Will be retiring the Infuse soon, so am thinking on what ROM to put on when I go to sell it (or give away). The requirement is that is not overwhelming to a new user. Cyanogenmod has a lot of customization, but it doesn't necessarily get in the way. I'd call it borderline overwhelming. Beanstalk is quite overwhelming, because you are forced to pick a launcher right from the beginning (even though I like it for the Jellybean qualities).
Because of these, I just may return it to stock, but have it rooted and with CWM.
Click to expand...
Click to collapse
I do not see any option to select a launcher like Scotts CM had. So i guess there is no direct option to select it.
Quick search in the running apps shows Launcher 3 running, and apk also available in the priv-app folder in rom, so can conclude launcher is Launcher3.
I did not find it overwhelming in any way.
-Hemen
hemen_kap said:
I do not see any option to select a launcher like Scotts CM had. So i guess there is no direct option to select it.
Quick search in the running apps shows Launcher 3 running, and apk also available in the priv-app folder in rom, so can conclude launcher is Launcher3.
I did not find it overwhelming in any way.
-Hemen
Click to expand...
Click to collapse
I flashed it last night (latest nightly), and it gave me the option of either Launcher3 or Google Now Launcher. I think if someone who was new to the device would be stumped a little by this, but would probably select the Google Now one (the question would be would they press once or always) and be done with it.
Having something recognizable runs at an advantage here compared to Beanstalk, where, unless you know CyanogenMod (or have played with a lot of launchers) you wouldn't know what to select. That would be overwhelming.
Anyway, I wiped the data again, breezed through setup (skipped everything but language and time zone), so it's all ready to go. If need be I can get them set up with a network and Google account before I throw them to the wind.
EDIT:
I see why I got the prompt ... I used the Paranoid Android micro apps package, which includes ... the Google Now Launcher.
hemen_kap said:
Exactly the same issue I am having with Unofficial CM 11.2 from scott.
I have been using Scott Harts Unofficial CM from 10.1 to 11.2 on my Samsung infuse and each time i notice a pattern.
Each of the above ROMs start out pretty smooth, and the phone works without any issues for 6 months or so. Then occasionally and app or two start crashing. Then in a weeks time all hell breaks loose and almost all apps start crashing such that the phone becomes unusable. Especially trebuchet starts crashing and that is the end of story.
In the past i have noticed this happens a month or so after an updated rom has been released and I used to upgrade to the new one and the cycle continues.
I am currently on the latest Unoffical CM 11_2 (Kitkat) and the appropriate Gapps installed and the same issue has happened twice.
I have tried the following to fix the issue and nothing helps
1. Clear data for trebuchet and a bunch of other apps.
2. Reinstall Gapps
3. Wipe Cache >> Wipe Dalvik Cache
4. Wipe Cache >> Wipe Dalvik Cache > install Gapps
5. Wipe Cache >> Wipe Dalvik Cache > install custom Rom >> install gapps >> wipe cache and dalvik again
The only way I have been able to get it working in the past is
1. Wipe data/factory reset > Clear Cache > clear Dalvik cache and possibly reinstall ROM and gapps (not sure, but I guess factory reset also does the trick)
So my phone is stuck in this mode and I would like to help debug the situation. Can someone help with the next steps? So that I can capture all required information before I do a factory reset .
Click to expand...
Click to collapse
Hi,
I was using CM 10.1 from Scott for like a year and didn't have any trouble at all, really the best ROM. Only had two small problems: wouldn't film on 720p without bugging, and MHL to HDMI was not working.
Now I installed CM 11, with latest gapps ( didn't know there was a CM11.2 ), and camera issue on filming is the same. But now it's worse, battery life is lasting half the time it was before, and gallery is crap, bugging every time. Did you have the same issues? Tell me the post of CM11.2 please..
Sent from my SGH-I997 using XDA Free mobile app
jloibman said:
Now I installed CM 11, with latest gapps ( didn't know there was a CM11.2 ), and camera issue on filming is the same. But now it's worse, battery life is lasting half the time it was before, and gallery is crap, bugging every time. Did you have the same issues? Tell me the post of CM11.2 please..
Click to expand...
Click to collapse
Not sure about this, but I think CM 11.2 is referred to as KitKat 4.4.4, which would be latest in the CM thread. So you are probably already running it.
Sent from my Asus MeMO Pad 8"
jloibman said:
Hi,
I was using CM 10.1 from Scott for like a year and didn't have any trouble at all, really the best ROM. Only had two small problems: wouldn't film on 720p without bugging, and MHL to HDMI was not working.
Now I installed CM 11, with latest gapps ( didn't know there was a CM11.2 ), and camera issue on filming is the same. But now it's worse, battery life is lasting half the time it was before, and gallery is crap, bugging every time. Did you have the same issues? Tell me the post of CM11.2 please..
Sent from my SGH-I997 using XDA Free mobile app
Click to expand...
Click to collapse
apart from the issues that i mentioned - my experience with CM 11.2 has been great. There are some obvious things like MHL etc that do not work, but those are known issues.
joel.maxuel said:
I flashed it last night (latest nightly), and it gave me the option of either Launcher3 or Google Now Launcher. I think if someone who was new to the device would be stumped a little by this, but would probably select the Google Now one (the question would be would they press once or always) and be done with it.
Having something recognizable runs at an advantage here compared to Beanstalk, where, unless you know CyanogenMod (or have played with a lot of launchers) you wouldn't know what to select. That would be overwhelming.
Anyway, I wiped the data again, breezed through setup (skipped everything but language and time zone), so it's all ready to go. If need be I can get them set up with a network and Google account before I throw them to the wind.
EDIT:
I see why I got the prompt ... I used the Paranoid Android micro apps package, which includes ... the Google Now Launcher.
Click to expand...
Click to collapse
You can download the Nova Launcher from the google play store if you want to have the same experience as with Scotts Beanstalk. I love the carbon ROM but I am so accustomed to the Nova launcher that I cant live without it.
hemen_kap said:
Exactly the same issue I am having with Unofficial CM 11.2 from scott.
I have been using Scott Harts Unofficial CM from 10.1 to 11.2 on my Samsung infuse and each time i notice a pattern.
Each of the above ROMs start out pretty smooth, and the phone works without any issues for 6 months or so. Then occasionally and app or two start crashing. Then in a weeks time all hell breaks loose and almost all apps start crashing such that the phone becomes unusable. Especially trebuchet starts crashing and that is the end of story.
In the past i have noticed this happens a month or so after an updated rom has been released and I used to upgrade to the new one and the cycle continues.
I am currently on the latest Unoffical CM 11_2 (Kitkat) and the appropriate Gapps installed and the same issue has happened twice.
I have tried the following to fix the issue and nothing helps
1. Clear data for trebuchet and a bunch of other apps.
2. Reinstall Gapps
3. Wipe Cache >> Wipe Dalvik Cache
4. Wipe Cache >> Wipe Dalvik Cache > install Gapps
5. Wipe Cache >> Wipe Dalvik Cache > install custom Rom >> install gapps >> wipe cache and dalvik again
The only way I have been able to get it working in the past is
1. Wipe data/factory reset > Clear Cache > clear Dalvik cache and possibly reinstall ROM and gapps (not sure, but I guess factory reset also does the trick)
So my phone is stuck in this mode and I would like to help debug the situation. Can someone help with the next steps? So that I can capture all required information before I do a factory reset .
Click to expand...
Click to collapse
OK the exact same problem has started again today on Carbon ROM. Wonder if this is a Cyanogen thing, as that seems to be common between the two.
Anyone else facing this ?
-Hemen
hemen_kap said:
OK the exact same problem has started again today on Carbon ROM. Wonder if this is a Cyanogen thing, as that seems to be common between the two.
Anyone else facing this ?
Click to expand...
Click to collapse
Hmm, don't think I kept a ROM on my Infuse long enough to encounter this problem (except for my several months with CM 10.1, no issues). As for other phones, I use Jellybean on my semi-retired HTC and did not have this problem (closest I came was when I tried out Fly-On mod - lag closures often). But I don't think It's a Jellybean problem.
I think (and this may have been covered already) this has to do with the piddly datadata partition filling up. One way to check is open a terminal emulator (app on the phone of adb shell) and type:
Code:
df
Look for datadata in that listing. If it is in the 90% range, that spells trouble. If that is the case, you could try one of two solutions.
I don't know what possessed the developers to separate the data partitions in KitKat (I know, for "performance reasons") but leave 1/2 a GB for it. Lower end phones these days give you twice that.
Over the past few years or so I've installed ROMs going back to ICS. 99% of the time there was absolutely no issue. I habitually do a (1) factory wipe, (2) dalvik wipe, (3) system format, (4) sdcard0 format, (5) install ROM zip, (6) install gapps, (7) wipe cache and (8) wipe dalvik.
In the hundreds of ROMs I've installed and tested, 1 or 2 were bad compiles, and everyone soon knew it. They were immediately removed from any host site. So, if you're having issues, (1) install you ROM as above, (2) perhaps install a smaller gapps, and/or (3) check that you're not overloading your phone from the PlayStore.
The last and rarest issue could be your phone, but rule of thumb that works 99% of the time is: (1) assume it's always your fault first, and (2) read, read, read, read, read.