I have to post here because I'm a massive lurker and haven't got the post count for the development forum!
Firstly, excellent to see Task back in action for ICS! I was considering going back to stock for the OTA following today's ICS release but figured seeing as I was already rooted I might as well stick with custom roms.
I installed Infamous 2 (1st Aug) no problem at all, smooth as silk for a day 1 release! I used it for a bit before seeing Task was back with his first ICS so thought I'd stick with what I know best and completed the process again for his rom.
Install went fine, factory reset/wipe everything, install from .zip and booted first time no problems. I didn't go through the Google setup, or wifi, in order to let the rom settle, then I rebooted after 10 mins and the problem started. I got the following error on screen every 10 seconds:
android the process com.android.phone has stopped working
It would hang every time (unsurprisingly) and I couldn't access files via PC either, despite MTP connection showing. I've now restored back to Task14 from recovery backup and I'll wait for some more mods to be done before trying again, but thought I'd share my experience here in the hope it might help others/Task sort things out if it happens to them.
/refreshes the forum over and over again impatiently waiting for the real goodies to start flowing
mooter said:
I have to post here because I'm a massive lurker and haven't got the post count for the development forum!
Firstly, excellent to see Task back in action for ICS! I was considering going back to stock for the OTA following today's ICS release but figured seeing as I was already rooted I might as well stick with custom roms.
I installed Infamous 2 (1st Aug) no problem at all, smooth as silk for a day 1 release! I used it for a bit before seeing Task was back with his first ICS so thought I'd stick with what I know best and completed the process again for his rom.
Install went fine, factory reset/wipe everything, install from .zip and booted first time no problems. I didn't go through the Google setup, or wifi, in order to let the rom settle, then I rebooted after 10 mins and the problem started. I got the following error on screen every 10 seconds:
android the process com.android.phone has stopped working
It would hang every time (unsurprisingly) and I couldn't access files via PC either, despite MTP connection showing. I've now restored back to Task14 from recovery backup and I'll wait for some more mods to be done before trying again, but thought I'd share my experience here in the hope it might help others/Task sort things out if it happens to them.
/refreshes the forum over and over again impatiently waiting for the real goodies to start flowing
Click to expand...
Click to collapse
logcat or it didnt happen.
task650 said:
logcat or it didnt happen.
Click to expand...
Click to collapse
I see some logs in the root folder, is that what you're referring to? I'll happily help you investigate if I can but it'll help if you point me in the right direction. Actually, maybe I'll try again and see how I get on? Restoring from backup was pain-free so not much to lose but 20 mins
Regardless, I very much look forward to seeing your work progress on this one over time! I know you're busy but superstars have obligations dude haha ;D
edit - trying again now with logcat reader installed - I'll report back!
do you have Ti backup installed? I would first try to see if there is some kind of phone apk in there. If there is try to clear the phone apk data and cache. If that doesnt work maybe try freezing it. Its strange that you have this error since tasks rom is a stock galaxy tab 10.1 ics build. Maybe try to wipe everything again and follow tasks instructions one more time step by step. sometimes weird things happen and a reflash might fix that. And just a stupid question but you have the wifi p7510 tab right
Related
I get this message when I boot up.
I cannot access settings so I cannot perform a factory reset.
Is there any way to factory reset when you cannot access "Settings" because of constant force closes.
I am running stock but with lots of side-loaded apps.
I can access the file explorer. That is the only thing I can open that will remain open even though I get constant force close popups like "android.process.acore has stopped... android.process.media has stopped unexpectedly...
Is my gtab toast? Can it be saved or should I return it?
I get this all the time, with all the mods I do. Don't worry, your system is fixable.
For me, I use clockworkmod recovery .08. There's a "fix permissions" option and this always fixes the problem for me. It also allows a data wipe within recovery.
If you are 100% stock, you could try one of the stock ROM's here as well - that might get you working. You have a few options, here. Check out the FAQ in my signature. I'm actually posting up the new stock update that I pulled from TnT, today.
EDIT: Direct link the the stock ROM updates -- http://forum.xda-developers.com/showthread.php?t=842000. You'd need to understand how to actually run these, which I mention in the FAQ section.
thx Roebeet, I was able to update to the new stock rom.
But I still have the same problem. Is there any other way to wipe my data. Can it be done while connected by usb or do i have to root it?
Is there any hardware button method to do a factory reset?
I still cannot open settings... it gets canceled by the force closes.
I am ready to give upon my G-Tab which I was enjoying so much.
Does anyone know how to wipe the date if you cannot open settings???
Try clockworkmod - it really is a great tool. You can find it in the Tnt Lite dev section as I have a link for .08.
For UID issues, "fix permissions" will correct it. And you can wipe data via clockworkmod as well. You can even remove it by flashing back to stock -- the latest stock firmware works as I've done it myself, the other day.
Btw, there are so many threads here that I sometimes miss replying. I dont ignore, I just might miss a post. Always feel free to PM me if you have a question.
I had a similar issue where something got corrupted in my user data and I was completely unable to start the settings or open the keyboard. I had to flash back to the full vanilla ROM because it contained clockworkmod, which was the only option available to accomplish a factory reset. That wasn't a fun day.
Think I figured out a key reason for sudden UID issues
People including me are getting UID errors even after having a stable rom and several reboots with no issues. Based on guinea piggin' my G, I can confirm the issues happen on apparently stable installs anytime you update a Google app.
Case in point, I updated Google Voice and Gmail and soon after I rebooted the G- UID city. I have started with a clean rom and installed many different apps to test. The only apps that hose the device at reboot are the GAPPS and it is not just if you update with the package. Simply updating from market will work fine, until you reboot and then it is a few minutes for trying to shut the device down and then perhaps two reboot attempts using fixed permissions.
TnT 2.20 (at least) does NOT like GAPP updates. How could VS bork this up so bad that fundamental apps for Android bork the device?
Again, the Tap UI team and who hired them and approved it on the Gtablet should be fired, rehired for a minute and then fired for good. Word.
This sounds kind of "preachy," but don't give up.
There is a learning curve to the G-Tablet, and it takes a good bit of reading on this site and assimilating the info.
I will testify that I had a hugely bad malfunction and and even worse fix on my tablet.
Using suggestions from helpful folk -- and carefully researching what I needed to do -- I was able to get my tablet back working just fine. To be sure, it's not stock any more!!! But I actually believe that with all I learned about flashing, mods, etc., I now could go back and make it stock again if I wanted to.
Don't give up. Just keep reading and researching the learning.
Rev
rushless said:
People including me are getting UID errors even after having a stable rom and several reboots with no issues. Based on guinea piggin' my G, I can confirm the issues happen on apparently stable installs anytime you update a Google app.
Case in point, I updated Google Voice and Gmail and soon after I rebooted the G- UID city. I have started with a clean rom and installed many different apps to test. The only apps that hose the device at reboot are the GAPPS and it is not just if you update with the package. Simply updating from market will work fine, until you reboot and then it is a few minutes for trying to shut the device down and then perhaps two reboot attempts using fixed permissions.
TnT 2.20 (at least) does NOT like GAPP updates. How could VS bork this up so bad that fundamental apps for Android bork the device?
Click to expand...
Click to collapse
Not true for me, I installed the new Gmail from the Market with no problems. I am on TNTLite 2.2.1.
Google Voice has always been a hack for a tablet, since it is not actually phone. You might want to pull it out and see if your issues are solved.
I am back up and running thanks to clockwordmod. Thanks again!
ninjaprofessor said:
I am back up and running thanks to clockwordmod. Thanks again!
Click to expand...
Click to collapse
Good to hear and thanks for the update!
I am currently having this problem. I am hoping to sell my 10" Android 2.2 Tablet PC on Craigslist... I need to fix this Error... I've only used it 10 times to play Angry Birds. The forum with the links I am confused as to what one to use... I am younger I must say. I am not a 21 year old "computer whiz"/.NET/OS maker... I do make websites. Besides that... I do not know how to "Wipe my system partition" as my Error message says to. Especially due to the fact I cannot open Settings. PLEASE HELP. I may have repeated things said above in his problems but I would like a "NOOB" walk through... (Because I am one). Please help. Thanks in advance. -Sophomoric
Hey, I had a same after my phone battery was empty and it turned off. I kept it off and recharged it, then I had the feeling "I'm feeling Lucky" -.-' so nice from google. xD
Had to wipe everything then full reinstall... such a pain.
Probably the cleanest solution HERE
I had used the amaze 4g all in one tool kit to unlock my bootloader, install a custom recovery, and then installed a custom rom (bullet proof 2.5) along with the provided kernel to go with it.
The phone worked great for a few days, then I noticed that it was acting like the wireless network radios were turned off in the software. They were still enabled so I rebooted and it fixed the problem for a little while.
Now my phone will only give me the com.android.phone has stopped working error and will not let me turn on the wireless network radios.
I have tried complete wipe of the phone and re-installation of the custom rom. I have tried different, yet still recommend, custom kernels, as well as different recoveries all with the same issue.
Any help would be greatly appreciated. I tried searching with out any good results.
Thanks.
Are you a Tmobile user?
Double0EK said:
Are you a Tmobile user?
Click to expand...
Click to collapse
Yeah. Even tried a new simcard even though I didnt think it would do any good.
toyoter91 said:
I had used the amaze 4g all in one tool kit to unlock my bootloader, install a custom recovery, and then installed a custom rom (bullet proof 2.5) along with the provided kernel to go with it.
The phone worked great for a few days, then I noticed that it was acting like the wireless network radios were turned off in the software. They were still enabled so I rebooted and it fixed the problem for a little while.
Now my phone will only give me the com.android.phone has stopped working error and will not let me turn on the wireless network radios.
I have tried complete wipe of the phone and re-installation of the custom rom. I have tried different, yet still recommend, custom kernels, as well as different recoveries all with the same issue.
Any help would be greatly appreciated. I tried searching with out any good results.
Thanks.
Click to expand...
Click to collapse
are you running joes "one good rom"? dude it says right in the op
Attention 2: on the first start "com.android.phone" process will FC, it is normal.
It's because of Toggle2G app. Just open that app and give it permission to run.
mrmako777 said:
are you running joes "one good rom"? dude it says right in the op
Attention 2: on the first start "com.android.phone" process will FC, it is normal.
It's because of Toggle2G app. Just open that app and give it permission to run.
Click to expand...
Click to collapse
I actually stated in my first post what rom I was running when all this happened.
I have tried Joes "one good rom" and followed all his kernel and set up instructions with no luck. On his rom I don't get the error message, but all of the wireless network options are grayed out. I am starting to think it might be something hardware.
toyoter91 said:
I actually stated in my first post what rom I was running when all this happened.
I have tried Joes "one good rom" and followed all his kernel and set up instructions with no luck. On his rom I don't get the error message, but all of the wireless network options are grayed out. I am starting to think it might be something hardware.
Click to expand...
Click to collapse
doh! shame on me for not seeing that i would say if worse comes to worse, reflash the stock rom and see if youre up and running. if its still not working, then id say maybe send it in for warranty
mrmako777 said:
doh! shame on me for not seeing that i would say if worse comes to worse, reflash the stock rom and see if youre up and running. if its still not working, then id say maybe send it in for warranty
Click to expand...
Click to collapse
No worries. I am actually in the process of finding and flashing the stock rom back onto it, going to try and put everything back to stock and see what happens.
Having a similar problem
toyoter91 said:
No worries. I am actually in the process of finding and flashing the stock rom back onto it, going to try and put everything back to stock and see what happens.
Click to expand...
Click to collapse
Hi. I decided to add to this thread instead of starting a new one since i am having a similar problem. The originator never said if he was able to solve the problem. I was using the Energy ROM (http://forum.xda-developers.com/showthread.php?t=1362759) (ICS, S-ON) and everything was fine. I decided to try the Speed ROM (project "butter" http://forum.xda-developers.com/showthread.php?t=1623184) which is Jellybean based. I did a full wipe, and after installing it I got the same com.android.phone error. I got it to stop, but then started having other issues like Superuser, BusyBox, and Titanium Backup unable to get root access. Unable to find any other solutions, I decided to restore to stock, which went fine (well I had to try a few times as I haven't done it before). After that, and having the phone working fine back at stock ICS I reflashed the Speed ROM. I ended up with the same issue. I wiped again and returned to the Energy ROM and it seems to be working fine. My quesiton is, why is the Speed ROM not working on my phone? When it flashed there were no issues, and I followed the instrucitons exactly.
I would post in the Speed ROM forum but I don't have enough posts yet since I am usually able to find answers by searching.
BillyD325 said:
Hi. I decided to add to this thread instead of starting a new one since i am having a similar problem. The originator never said if he was able to solve the problem. I was using the Energy ROM (http://forum.xda-developers.com/showthread.php?t=1362759) (ICS, S-ON) and everything was fine. I decided to try the Speed ROM (project "butter" http://forum.xda-developers.com/showthread.php?t=1623184) which is Jellybean based. I did a full wipe, and after installing it I got the same com.android.phone error. I got it to stop, but then started having other issues like Superuser, BusyBox, and Titanium Backup unable to get root access. Unable to find any other solutions, I decided to restore to stock, which went fine (well I had to try a few times as I haven't done it before). After that, and having the phone working fine back at stock ICS I reflashed the Speed ROM. I ended up with the same issue. I wiped again and returned to the Energy ROM and it seems to be working fine. My quesiton is, why is the Speed ROM not working on my phone? When it flashed there were no issues, and I followed the instrucitons exactly.
I would post in the Speed ROM forum but I don't have enough posts yet since I am usually able to find answers by searching.
Click to expand...
Click to collapse
That's a common problem with SpeedRom and some other as well. Re-flash the SpeedRom, after it boot-up, go to Google Play store and download SuperSU -not Superuser -, open SuperSU and update binary. After that you can install busy box and run Titanium ....
antiquezip said:
That's a common problem with SpeedRom and some other as well. Re-flash the SpeedRom, after it boot-up, go to Google Play store and download SuperSU -not Superuser -, open SuperSU and update binary. After that you can install busy box and run Titanium ....
Click to expand...
Click to collapse
Thank you! After I posted I ran across somehting in the speed rom thread that made me go back to the original post. Sure enough, there is a download link for SuperSU which it says you need to flash to gain root after installng the ROM. I guess I read the instructions above, scrolled down to the rom download link, and then stopped. I will try this again with what you suggested when I have time in the next day or two.
BillyD325 said:
Thank you! After I posted I ran across somehting in the speed rom thread that made me go back to the original post. Sure enough, there is a download link for SuperSU which it says you need to flash to gain root after installng the ROM. I guess I read the instructions above, scrolled down to the rom download link, and then stopped. I will try this again with what you suggested when I have time in the next day or two.
Click to expand...
Click to collapse
I had this error factory reset stop the error.
This belongs in Q&A.
Thread Moved.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice"
Sent from my Galaxy Note (i717), using XDA Premium.
I've read the majority the Diet ICS thread and haven't found much of a solution. I was hoping somebody with this ROM could help me. The ROM has worked great, I've been using it for the past week and have re-flashed the subsequent updates every few days. Currently DIET is on 7.11.12 and it hasn't fix a couple issue I'm having. Not sure if its just my device but there is a bug after you hang up a call. It doesn't show the shortcuts on my device between the image and call/text buttons. Also my GPS hasn't been able to get a lock the past few updates. Its odd since I havent read about anyone else having these issues. I've owned and iPhone the past 4 years so im extremely new to rooting, this is my first ROM. So far this phone has been incredible... I don't know why it took me so long to make the switch.
Any help would be appreciated.
** Sorry for posting in this section, I'm new to the forum and wasn't able to post in ATT Android Development
Shampuu said:
I've read the majority the Diet ICS thread and haven't found much of a solution. I was hoping somebody with this ROM could help me. The ROM has worked great, I've been using it for the past week and have re-flashed the subsequent updates every few days. Currently DIET is on 7.11.12 and it hasn't fix a couple issue I'm having. Not sure if its just my device but there is a bug after you hang up a call. It doesn't show the shortcuts on my device between the image and call/text buttons. Also my GPS hasn't been able to get a lock the past few updates. Its odd since I havent read about anyone else having these issues. I've owned and iPhone the past 4 years so im extremely new to rooting, this is my first ROM. So far this phone has been incredible... I don't know why it took me so long to make the switch.
Any help would be appreciated.
** Sorry for posting in this section, I'm new to the forum and wasn't able to post in ATT Android Development
Click to expand...
Click to collapse
I know this reply comes a little late. I was having a few of the same issues until i began to re-flash the kernel i use after updating the version of Diet ICS that i use. This process has flawlessly worked for me with every update:
Reboot in to recovery
Wipe cache partition
Wipe Dalvik Cache
Fix Permissions
Backup to an external SD card
Install your update from Zip
reboot in to recovery
Flash Kernel
Fix permissions again
Reboot in to ICS
I hope this helps!
Hi, I just recently came back to this forum, pleased to find that we now have CM10 working on Amaze ! (Thank you sportsstar!)
However I did have a couple issues when installing, and seeing as how a lot of people in the CM10 thread asked to redirect questions here, I figured I make a thread.
My problem is that it seems as though no matter what I install, there is always a problem. As far as I know, I am using the basic ICS-Ruby kernel that was dumped 6+ months ago. I installed the CM10 rom using 4EXT, with no issues.
However when I installed the Gapps (gapps-jb-20130301-signed) I constantly had the Android keyboard force close on me. So instead I tried to install the JB-4.2-Gapps-signed. With these, the Android keyboard would not force close but the Google Now search app would force close everytime.
I've also tried installing the DARK GLASS 0.6 ROM by jose, but then the wifi would not turn on. (When I would try to turn it on, it would just hang saying "Turning on Wifi").
It is probably worth mentioning that I did do a full wipe everytime I installed the CM10 rom. I was sure to be very thorough. When I installed DARK GLASS 0.6 ROM, again, I did a full format of partiitions, and a wipe. Still the issues above arise.
Can someone maybe help me out as to what I'm doing wrong? Thanks!
------------------------------------------------------------------------------------------------------------------------------------------------------
EDIT: I just looked at my phone info, and apparently the kernel I'm using is 3.0.53-gd28c6eb. Is this okay or do I need to flash a new kernel ?
I am currently running the nightly builds of the carbon ROM, and it has worked great until the last week or so. Lately when ever I try to update to the new nightly build after the update and the android is optimising sequence, when the phone arrives at the home screen I get the following message.
unfortunately com.android.phone has stopped working.
I can't get passed this error making the rom un usable I then have to roll back to a previous backup.
I really want to if I can fix this so I can start moving forward again.
So my question is is the something to do with the way my phone is setup, or is it something wrong it the current builds that the Carbon ROM team are currently pushing out?
Many thanks.
fastfibre said:
I am currently running the nightly builds of the carbon ROM, and it has worked great until the last week or so. Lately when ever I try to update to the new nightly build after the update and the android is optimising sequence, when the phone arrives at the home screen I get the following message.
unfortunately com.android.phone has stopped working.
I can't get passed this error making the rom un usable I then have to roll back to a previous backup.
I really want to if I can fix this so I can start moving forward again.
So my question is is the something to do with the way my phone is setup, or is it something wrong it the current builds that the Carbon ROM team are currently pushing out?
Many thanks.
Click to expand...
Click to collapse
Wipe cache and Dalvik Cache
Sorry it took me so long to respond, I have only just now had a chance to try what you suggested but unfortunately it did not resolve the issue. So I want to reinstall the rom completely, but am not sure where to find the latest gapps for my device.
Many thanks.