Ok this might be in here already but I can't find it. I have a rooted G1 with cyan 4.2.14.1 and I recently did a data wipe. After, everything worked except my browser. It's Loccy's I have tried deleting all remnants of it and reinstalling it using the apk. I have tried to reinstall cyan. I have even gone into the davlik folder and tried deleting it that way. Nothing has worked so far. I downloaded Dolphin Browser and that works fine so I know it's nothing with the phone itself. I am lost for an answer if someone could help me I would appreciate it. Thanks.
Related
It's crashed through several rom updates and after a wipe at some point. I removed the com.android.browser.apk and reinstalled it and it still crashes.
What else can I do to try and fix it?
Pinesal said:
It's crashed through several rom updates and after a wipe at some point. I removed the com.android.browser.apk and reinstalled it and it still crashes.
What else can I do to try and fix it?
Click to expand...
Click to collapse
Load a new rom on your card, wipe, and update and see if that fixes your problem.
Well, that's a last resort right now.
I'm sure the problem comes from me restoring the browser setting from the app Backup for Root Users.
If someone could tell me where the browser settings are stored, I could try deleting them and seeing if that helps.
Check out the lasts posts from the soulife rogers remix thread... there is a few people with that same issue... link is in my sig.
I have been having this issue ever since my phone booted up and all my apps sequentally had force close dialogs happen. I am running my apps from the SD and figured something went wrong with the boot up sequence. I tried doing a nandroid backup, reinstall fresh 1.1, but no luck.
I then used my backups to reinstall over all my apps, then went into Market to install them via that. Everything seemed to be just fine, but the phone app would still not dial anything and when I recieved a call, it gives the error "The process com.android.phone has stopped unexpectedly" and then proceeds to try to reset the phone connection. Most times I lose all data connection and need to reboot.
Recently, I tried installing the latest Modoco CDMA rom. No luck. I then did a Titanium backup and force reinstalled everything again. Still no luck.
Anyone have this issue and get it resolved? My Hero can do everything but make and accept calls. I really don't want to do a wipe as this problem can just happen again, so I would rather understand the process.
Thanks in advance.
Ceger
Simplest way to fix this should be clearing the dalvik/boot cache from fresh's kitchen. I really should write up a guide on how to do these simple tasks manually.
obelisk79 said:
Simplest way to fix this should be clearing the dalvik/boot cache from fresh's kitchen. I really should write up a guide on how to do these simple tasks manually.
Click to expand...
Click to collapse
Will that work on MCR 2.2 as well? I'll look into that. Is it something I can do from recovery?
Ceger
yes should work on mcr 2.2 and can be done manually from recovery, I know recovery does dalvik cache, not sure if it also kils the boot cache as well though. The older version only did dalvik.
obelisk79 said:
yes should work on mcr 2.2 and can be done manually from recovery, I know recovery does dalvik cache, not sure if it also kils the boot cache as well though. The older version only did dalvik.
Click to expand...
Click to collapse
Do you need to do both? Wiping the dalvik cache created lots of app fc issues, which would be fine if the phone actually worked. Still won't make or receieve calls.
And thank you for the assistance.
Ceger
Edit. Clearing the boot cashe got rid of the FC issues. However, still have same issue with the phone app. This is so annoying.
honestly the best bet to clear up the issues would be to do a full wipe from recovery. Wipe the phone clean then run the stock RUU and re-root and install your custom rom. Do a nandroid backup first just to prevent losing any of your info.
Unfortunately despite the many well written guides here on XDA there are always a few issues most likely a result of slight hardware quirks or unfortunate circumstances at the time of flashing.
Just for '****s and giggles' have you tried pulling your battery for 30 seconds, reinstalling it and booting the phone up?
Heck sometimes just a reflash of the rom right over top of itself. I've been tinkering with this phone since the day root came out and I still don't fully understand all of it's quirks.
Ceger said:
I have been having this issue ever since my phone booted up and all my apps sequentally had force close dialogs happen. I am running my apps from the SD and figured something went wrong with the boot up sequence. I tried doing a nandroid backup, reinstall fresh 1.1, but no luck.
I then used my backups to reinstall over all my apps, then went into Market to install them via that. Everything seemed to be just fine, but the phone app would still not dial anything and when I recieved a call, it gives the error "The process com.android.phone has stopped unexpectedly" and then proceeds to try to reset the phone connection. Most times I lose all data connection and need to reboot.
Recently, I tried installing the latest Modoco CDMA rom. No luck. I then did a Titanium backup and force reinstalled everything again. Still no luck.
Anyone have this issue and get it resolved? My Hero can do everything but make and accept calls. I really don't want to do a wipe as this problem can just happen again, so I would rather understand the process.
Thanks in advance.
Ceger
Click to expand...
Click to collapse
use these commands to clear cache
rm -r /data/boot-cache/
rm /data/dalvik-cache/
once you finish then reboot.everything should go away...
he's done that already.
then i suggest to extract the rom zip file, and get into command on your device and go under the system/lib or app and see what is listed in the folders. and compare it to the rom folder.
That's how i was able to fix the voice search on my device, one of the lib file was missing and got it to work after that.
obelisk79 said:
honestly the best bet to clear up the issues would be to do a full wipe from recovery. Wipe the phone clean then run the stock RUU and re-root and install your custom rom. Do a nandroid backup first just to prevent losing any of your info.
Unfortunately despite the many well written guides here on XDA there are always a few issues most likely a result of slight hardware quirks or unfortunate circumstances at the time of flashing.
Just for '****s and giggles' have you tried pulling your battery for 30 seconds, reinstalling it and booting the phone up?
Heck sometimes just a reflash of the rom right over top of itself. I've been tinkering with this phone since the day root came out and I still don't fully understand all of it's quirks.
Click to expand...
Click to collapse
Done and done and no difference.
reddick said:
then i suggest to extract the rom zip file, and get into command on your device and go under the system/lib or app and see what is listed in the folders. and compare it to the rom folder.
That's how i was able to fix the voice search on my device, one of the lib file was missing and got it to work after that.
Click to expand...
Click to collapse
Done, even manually moved some files in case they were corrupted at one point. Very bad move, nandroid backup was my friend there.
Guess a wipe will be the only option then. How annoying.
Thanks for all of your inputs.
Ceger
Another thought... would updating my phone with latest kernal compile possibly do the trick? Or how about a replacement process for google.com.phone?
Ceger
Interesting theory.... worth a try.
i had this issue once and it was because of somehow the uids for the apps got messed up. a wipe should fix this in most cases. but for me it went like ur issue. i almost event went back stock. then i looked into it and found that in my packages.xml file the the uids were all messed up. i had multiple uids and certs for the apps i was having issues with. so what i did was pulled the packages.xml from the device and erased the apps i was having issues with. then pushed it back and rebooted. that cleared the issue. so if i were u i would research that. do a google search on it. then if it doesnt work do the ruu and reroot. good luck man. i know how u must be feeling. i was there
toastcfh said:
i had this issue once and it was because of somehow the uids for the apps got messed up. a wipe should fix this in most cases. but for me it went like ur issue. i almost event went back stock. then i looked into it and found that in my packages.xml file the the uids were all messed up. i had multiple uids and certs for the apps i was having issues with. so what i did was pulled the packages.xml from the device and erased the apps i was having issues with. then pushed it back and rebooted. that cleared the issue. so if i were u i would research that. do a google search on it. then if it doesnt work do the ruu and reroot. good luck man. i know how u must be feeling. i was there
Click to expand...
Click to collapse
Actually, the fix was much simpler. I wiped the SD ext partition and just did a Recovery Wipe. It went back to stock modded rom that remained rooted. I then used Titanium to reinstall my apps with data and then MyBackup to get back some settings such as my scenes, etc. and all was good. Took all of 30 minutes to get my Hero back up and running in better condition than before.
Thanks all for the assists.
Ceger
com.android.phone
com.android.phone
i am facing this prob on cyanogen mod10....when ever i reboot my optimus 2x....i face this damn problem
help plzzzzzzzzzz.....!!!!!
i have the android 2.3.1 version on my phone, i flashed the NAND and everything for it, i have had it working fine for a while now, but since two nights ago, i was trying to go on my browser, and for some reason when i click it, it opens up and then just immediately minimizes itself and closes and just leaves me at the homescreen, and i cant seem to figure out why its doing that..ive been trying to search all over for it, does anyone know how i can fix this ?
Try clearing the cache for the browser in manage applications. Also, have you tried rebooting the phone?
yeahh i rebooted it, and cleared the cache and date from the browser, but it still acts up, i dont know how to fix it, or should i just get a different rom ?
As some of you may know, Flash Player 10.3 is released and when you try to install it on the new build of GladiAtrix, it will say insufficient space or whatever. I'm assuming this has to do with the Hulu hack? Well just thought I'd warn you guys
i didn't get that problem, make sure that all your cache is wiped in the cwm menu, sometimes adding a rom will do that, sometimes a simple reset fixes it. - hopefully that helps.
I personally tried it and it worked fine, but i had an issue with my speeds for about 5 minutes. It would acts extremely sluggish and then would cut out. After it acted all fine, if any of u guys get that problem, let it pass and you should be fine.
I had the flash player issue. Installed gladiatrix and flash would not work. Then I was not able to uninstall flash without manually doing it which I really dont know how to do. I had to find the old 10.2 leaked apk and then updated it to get it working again.
Clearing my cache didn't do anything :/
I made a new modded libflashplayer.so for 10.3. It's working fine for me. Remember to change the permissions.
I was having the same error. I just uninstalled 10.2 and installed 10.3. Hulu still works.
Sent from my MB860 using XDA App
can someone post flash 10.3.
it is unavailible in my country
Rooted running cm7. I tried downloading my September magazine issues and it said there was error. I tried fixing permissions and rebooting and also reinstalled but still just gives me an error. Any thoughts?
Have you tried to clear data and relogin?
I know, Nook app is shytty
i had this problem and didnt find a fix either
I had the same problem about a month and a half ago. I wish I could give you a good answer on how to fix it. I uninstalled and reinstalled several times with no effect. Log out and login was similarly ineffective. One morning I opened the app at random and voila, everything worked as it was supposed to. Very strange. Good luck.