Screen write stops - Galaxy Note 4 Q&A, Help & Troubleshooting

I have an issue with screen write. I am rooted btw. I can take screenshots and save them no problem. But if I write on the image and hit the checkmark I get an error saying sceen write has stopped. I have googled around, found some threads, tried the fixes. Thought maybe I froze something with titanium backup. I have un frozen everything, rebooted multiple times. Forced stop, clear cache for screen write and myscript resource manager. I have wiped the phone and flashed paulpizz rom again. I am using the emotion kernel. Anyone else having this issue? Should I try a different rom? Root is sticking and everything else seems to be working wonderfully.
Thanks for any help or insight.

Related

The process com.android.phone has stopped unexpectedly

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.....!!!!!

Root and Lag Fix Problem

Ok, so I rooted my phone yesterday via "one-click root" and worked like a charm. I deleted alot of bloatware and used info in a thread here in the forums as far as what to remove (Kindle, MobiTV, Amazon Mp3, etc But I also wanted to do a lag fix. I came across a guy that had a lag fix that I wouldn't have to use a pc for that was just a update.zip file that I would install. I followed his YouTube video step by step and had NO problem all the way up until I rebooted my phone. When I did so, my boot animation disappeared and my phone went BLACK! I contacted him and he had me clear user data and sd files and clear cache from the recovery screen. Now when I try and start my phone everything boots up but when I get to my homescreen I can't stop getting Force Closes and this is what the messages say:
----------
Sorry!
The process android.process.media has stopped unexpectedly. Please try again. dumpstate_app_201008310134_android_process_media.log has been saved. Use *#9900# to copy out log.
----------
AND when I try to open the Web it says:
----------
Sorry!
The application Web (processcom.android.browser) has stopped unexpectedly. Please try again. dumpstate_app_201008310147_com_android_browser.log has been saved. Use *#9900# to copy out log.
----------
And same for Gmail App when I try to open it.
And they won't stop popping up. Barely long enough for me to open ANY apps.
I don't know much about rooting yet but I know I probably need to re-install firmware or something that includes ALL the bloatware including the apps I removed with my Root Manager. I just need advice or a solution or something because its deffinatly making me mad!
Thanks for all your help!
Kyle
i had that exact same thing happen to me, but that was when i tried to revert back to non-lag fix. something errored out during the uninstall and i got exactly what you got, a ton of fc's. my solution was i flashed my phone back to factor stock using odin.
probably other solutions, but i chose the cleanest route, maybe not quickest.
Not sure if you would have enough time but you could try Fix Permissions on the Rom Manager app if you have it. If not you could try ADB pushing the APK and maybe you could open it before all the FC's. I have had that help before, but like said above quickest and easiest will just be to start over. Apply the lag fix first this time (you were probably already thinking this ) they seem to work better that way without any of these problems. For me at least
I have no idea where to start! I am brand new to this rooting stuff so I am LOST! REALLY lost! What is the first step for me? Do you know of anyone who can walk me through this?
It appears that more than one lag fix was applied. Start from a clean rom and start again.
[email protected]

[Q] Phone is ocassionally rendered useless after a reboot.

I have tried flashing a couple different roms, including Bonsai, TrulyEpic Rebirth. I get everything up and running, and a few reboots later, I turn my phone on, and I'm back at the setup screen, where you enter your gmail acct info, and it teaches you how to use the Swype keyboard and everything. I get through all that, and i just have a barrage of "this program force-closed" windows. Everytime I do that, I have to start all over. I've had to do this 5 or 6 times since I got the phone on Monday.
What I do is:
Flash DK28 with Odin.
One-click root/clockwork recovery 3.0.0.5
Let the system do the ext4 conversion
factory reset, clear cache partition, clear dalvik cache 3x
flash rom
restore all my apps
then, a few reboots later, I end up with the setup screen, and the barrage of FC notifications.
Am I missing something?
EDIT: WHOOPS. I'm half asleep and didn't read that right. When you say restore apps, are you restoring a cwm backup or are you talking about the app restoration build into the setup wizard?l
Built in setup app.
I used to have this problem too, it was very frustrating. For me, I finally narrowed it down to somehow corrupting the ROM by using the 3-button instant reboot method. Since I was using the no-journaling mod I figured that somehow I was forcing a re-boot while the system was writing something? I don't really know for sure though, but I can say now that I use QuickBoot and avoid the 3-button method, I haven't had any problems. Good luck!
Thanks. I have yet to try the no-journaling mod, nor do I know what the 3 button method is. I've been using a widget called "boot control", but I'll switch back to quick-boot (i've used it in the past) to see if that helps.

[Q] System UID Inconsistent Error after Titanium Backup

I searched and haven't found anything that's worked.
My phone was running fine after I flashed the crDroid rom. I then used Titanium Backup to only restore Bluetooth Connections, to see if it'd work. I had tried this same thing before with a full restore, and kept getting stuck in a Boot Loop, and had to restore and wipe constantly.
Now after I rebooted, it's giving me the "System UID Inconsistent - Please Wipe Data Partition .... I'm Feeling Lucky"
I press the I'm Feeling Lucky, and a lot of apps are gone. Is there a fix for this other than restoring and reformatting again? I've downloaded the Fix Permissions app from the App store, but no luck.
Thanks for any help!
sixout said:
I searched and haven't found anything that's worked.
My phone was running fine after I flashed the crDroid rom. I then used Titanium Backup to only restore Bluetooth Connections, to see if it'd work. I had tried this same thing before with a full restore, and kept getting stuck in a Boot Loop, and had to restore and wipe constantly.
Now after I rebooted, it's giving me the "System UID Inconsistent - Please Wipe Data Partition .... I'm Feeling Lucky"
I press the I'm Feeling Lucky, and a lot of apps are gone. Is there a fix for this other than restoring and reformatting again? I've downloaded the Fix Permissions app from the App store, but no luck.
Thanks for any help!
Click to expand...
Click to collapse
I think you have not changed the settings in TB to the "legacy" folder. Search the forum for solutions
Probably the cleanest solution HERE

[Q] Rom Manager - Fix Permissions problem

Has anyone else encountered problems running Fix Permissions from Rom Manager lately?
After Steven's warning here http://forum.xda-developers.com/showpost.php?p=49990427&postcount=62, I did a clean install and did not replace Browser or Gallery, all went well for a while, but then I began getting Trebuchet FC errors, rebooted to recovery to run Fix Permissions, but it is not avalible in the 6.0.4.7 CWM recovery, so I tried it through Rom Manager - noticed that it now has "toasts" rather than the old console type display, set it aside and let it run. Came back to my homescreen rather than the "reboot now" message that I was expecting. Re-booted and noticed a few user apps were missing, also got a few "android.process.media has stopped" errors as well as Trebuchet FC's. Convinced that I had a bad install, I formatted system, data and cache and flashed the latest nightly - 2/19 - oops, see http://forum.xda-developers.com/showpost.php?p=50470383&postcount=119 - getting stuck on the bootloader convinced me that I had something wrong with the EMMC, so I followed Leapinlar's (thanks again) Partition Repair guide at http://forum.xda-developers.com/showthread.php?p=28457126#post28457126 - of course, the same thing happened again because of the bad nightly. Finally re-flashed the 2/15 nightly and got everything working again, ran fix permissions just to make sure. Actually sat and watched about a half dozen "toasts" and then my display went black, with occaisional SU "toasts" popping up until my homescreen came back on after about 10 minutes - not back to Rom Manager, no reboot warning, just sitting at my homescreen. I let it sit for another 10-15 minutes and rebooted, after starting, a few user apps missing, "android.process.media has stopped" errors as well as Trebuchet FC's. I started a Logcat and ran Fix Permissions again, same thing. Logcat is at https://dl.dropboxusercontent.com/u/20993724/lc022014.txt if anyone is interested, I am going to report to ClockworkMod.
After re-formatting system, data and cache, 2/20 nightly installed fine, all has been well for the last few days, but have not run fix permissions.
I believe koush and cm decided that fix permissions is not needed anymore.

Categories

Resources