Related
Hi all. I've had an issue for a few weeks now. I have apps that are constanly locking up and force closing on my phone. I'm currently running Jelly Beans 11 with a rooted and unlocked GS3.
All different apps force close: gmail, play store, kik messenger, system processes. It seems it's not centralized to gapps for instance.
I've installed Beans 5, 6, 8, 9 once. 10 about 2 times, and version 11 i think 3 times. Each time I do a delvik cache wipe, a cache wipe, and a factory reset via CWM. Some times even the initial setup wizard will lock up after first boot.
I've tried flashing different modems as well, and i'm currently on the newest verizon one, the K3.
If anyone has any information on how to fix this it would be much appreciated. Even a full phone wipe or something... I'm going to try clean rom and CM 4.2 tonight.
In a seperate issue, that may or may not be related:
I'm currently in iraq and i'm using the world phone exploit to get cell service and data here in Baghdad. It used to work great, but now the data connection will be connected, but no data will upload or download for long periods of time. For example i could send a kik message while connected to EDGE network, but it might take an hour for it to actually send. It didn't used to do this...
All things considered i'm wondering if I actually physically damaged the phone somehow...
If I haven't provided enough information, please let me know and i'll be happy to reply.
Ok, i tried CM 4.2 and there weren't any lockups. But i couldn't keep the rom, doesn't seem to be any way to get cell service. it won't let me change the band to global.
Going to try clean rom now.
Clean rom works fine as well...
So why would Jelly Beans ROM, that's worked fine for quite a while for me, through various versions of ICS and JB, to suddenly cause apps to force close and general instability?
I've checked MD5's and they're correct...
I think i still need a few more posts before i can post in the dev section as well.
Any help is appreciated, thanks
Have you tried fixing permissions?
Here's how I flash a rom:
Wipe data/ factory reset
Wipe cache
Wipe dalvic
Format system
Flash rom
Boot the phone, wait 5 min and then wipe cache and dalvic again. I then fix permissions and then boot the phone and profit.
Sent from my SCH-I535 using xda app-developers app
bobAbooE said:
Have you tried fixing permissions?
Here's how I flash a rom:
Wipe data/ factory reset
Wipe cache
Wipe dalvic
Format system
Flash rom
Boot the phone, wait 5 min and then wipe cache and dalvic again. I then fix permissions and then boot the phone and profit.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
+1
fixing permissions is a must after a flash/restore.
ok i'll try installing beans again and using fix permissions afterwards.
Thanks
still not working
Ok, i've tried fixing permissions and i'm still having problems. Gapps has stopped working... System UI has stopped working... I followed the above posts exactly.
Any other suggestions?
Are you flashing gapps or just using that term to describe the apps from Google?
Sent from my SCH-I535 using xda app-developers app
bobAbooE said:
Are you flashing gapps or just using that term to describe the apps from Google?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
gapps was the term that the phone said when it crashed. But no i'm not flashing the gapps, they're included on most of the roms like Jelly Beans 11. I've had a few different gapps force close, like the store and gmail. but i've also had the system ui and kik force close.
Sorry man, it's beyond my knowledge. Never had a bunch of apps stop working that fixing permissions or a clean install didn't fix.
Sent from my SCH-I535 using xda app-developers app
How did Beans build 10 work for you, was that running fine? There are only two things I could suggest since you've tested normal suggestions already:
1) Beans removed a few files from System/Bin on Build 11, these are all included in Build 10. Maybe your phone needs those in order to work properly:
gsiff_daemon
mpdecision
qosmgr
smdexe
This is why I ask was Build 10 working fine for you? If so, maybe pulling these files from the Build 10 zip then putting them into System/Bin, setting permissions as rw r- r-, and rebooting could help. Or it could not.
2) Try flashing with TWRP recovery and see if the FC issue pops up.
SlimSnoopOS said:
How did Beans build 10 work for you, was that running fine? There are only two things I could suggest since you've tested normal suggestions already:
1) Beans removed a few files from System/Bin on Build 11, these are all included in Build 10. Maybe your phone needs those in order to work properly:
gsiff_daemon
mpdecision
qosmgr
smdexe
This is why I ask was Build 10 working fine for you? If so, maybe pulling these files from the Build 10 zip then putting them into System/Bin, setting permissions as rw r- r-, and rebooting could help. Or it could not.
2) Try flashing with TWRP recovery and see if the FC issue pops up.
Click to expand...
Click to collapse
Well I think 10 was when the issue started but i'm not sure anymore. I've flashed so many versions in the past week, from 5 to 11 that i've forgotten. I'll see if I can't do that though and see what happens.
should I do a factory reset? i mean is there an equivelant to formating a hard drive and reinstalling windows that i can do on an android?
Icewolf69 said:
Well I think 10 was when the issue started but i'm not sure anymore. I've flashed so many versions in the past week, from 5 to 11 that i've forgotten. I'll see if I can't do that though and see what happens.
should I do a factory reset? i mean is there an equivelant to formating a hard drive and reinstalling windows that i can do on an android?
Click to expand...
Click to collapse
To be consistent, its best to clean flash (factory reset/dalvik/cache) build 10 just to see if it works fine.
The equivalent to a Windows reinstall would be using Odin to flash a stock image. Using Odin, you would reset your phone back to fresh out of the box, bloated Verizon OTA. I feel that's unnecessary though cuz you flashed CleanRom and had no issues. If you flash another TW JB rom and have no issues, then it's more telling. As of now, something specific in Beans Build 11 (we'll verify b10 soon) is causing issues for you. Are you restoring any apps with Titanium Backup or restoring text messages using another app?
Edit: to detail a little more about the Odin route. After flashing the stock image, then you would need to root, unlock, install a custom recovery all over again and THEN flash Beans build 11. Idk if you want to do all that, esp if you haven't confirmed if this is something that's been happening with prior builds or with other roms.
SlimSnoopOS said:
To be consistent, its best to clean flash (factory reset/dalvik/cache) build 10 just to see if it works fine.
The equivalent to a Windows reinstall would be using Odin to flash a stock image. Using Odin, you would reset your phone back to fresh out of the box, bloated Verizon OTA. I feel that's unnecessary though cuz you flashed CleanRom and had no issues. If you flash another TW JB rom and have no issues, then it's more telling. As of now, something specific in Beans Build 11 (we'll verify b10 soon) is causing issues for you. Are you restoring any apps with Titanium Backup or restoring text messages using another app?
Edit: to detail a little more about the Odin route. After flashing the stock image, then you would need to root, unlock, install a custom recovery all over again and THEN flash Beans build 11. Idk if you want to do all that, esp if you haven't confirmed if this is something that's been happening with prior builds or with other roms.
Click to expand...
Click to collapse
I just did a fresh install of 10, including cache, delvik, factory reset, system partition, and after first boot i went back and fixed permissions. I'm still getting force closes. media service, google play, etc. I don't have many apps on it yet to see what else will force close since i'm not using titanium backup to restore anything. Everything is fresh and coming from the play store...
I should be hitting 10 posts soon so i'll be able to try and post in the beans thread, or the dev section. But any other ideas would be appreciated. Thanks.
I also seem to be getting a lot of "invalid file" and "file couldn't be downloaded" when i try to install apps from the store. Not sure what this means
Beans 12 came out today and I tried installing that and i'm getting the same issue.
Tomorrow i'm going to do a full wipe to stock verizon image. and go through the unlock and root motions unless someone has any more ideas.
Thank you for the help so far, i appreciate it.
I did a complete stock OTA flash last night to verizon's jelly bean, and went through the root and unlock process again. flashed beans 12, and i'm still getting the same error.
I'm on beans 6 right now and it's working great. Going to try changing a few settings in 12 to see if it works and then maybe see if 10 works.
I installed CarbonROM 1.6.1 on my S3 yesterday, and every time I reboot the phone, it goes to an activation screen that never finishes. Additionally, my phone number displays incorrectly. I can fix this by going in and out of Airplane mode and changing the CDMA subscription. But it just reverts back after a reboot (along with the activation screen).
This has been mentioned several times in the developer forum, but I have not found a solution to make it work. I performed a clean install (factory reset, wipe cache and dalvik cache, etc.) along with another install on top of the same ROM without wiping. Does anyone have any suggestions on how to fix this?
Thanks.
That's pretty much it
Unfortunately that's pretty much it. Your phone information should eventually stick (dunno why, but it does eventually) but if it doesn't then try another clean install. (btw have you made a backup of your imei, that might help a little as well.) I've had this problem many times and these work for me pretty much every time.
I discovered that this isn't an issue only with CarbonRom. I tried LiquidSmooth and ran into the exact same issue. I then proceeded to install CleanROM and no longer experienced the issue. So it seems to be an issue with AOSP ROMS.
I've done numerous clean installs and dirty installs, all with the same result. I've also backed up my IMEI. When you say that my phone info should eventually stick, are we talking about needing to let it run for days/weeks without rebooting?
Thanks.
IamMark70 said:
I discovered that this isn't an issue only with CarbonRom. I tried LiquidSmooth and ran into the exact same issue. I then proceeded to install CleanROM and no longer experienced the issue. So it seems to be an issue with AOSP ROMS.
I've done numerous clean installs and dirty installs, all with the same result. I've also backed up my IMEI. When you say that my phone info should eventually stick, are we talking about needing to let it run for days/weeks without rebooting?
Thanks.
Click to expand...
Click to collapse
ive been having this issue when i tired both roms so i ended up on cleanrom and then went over to beans for now due to it been base off of clean rom and having the asop look and feel of a aosp rom and the features of touchwiz and the stabilizability of it
I tried a couple more things and simply could not get around the activation issue after every reboot. Also always had to go in and change it from nv to rium/sim. I simply don't see how everyone using AOSP ROMS isn't running into this issue on the S3, and I have yet to see one definitive answer on how to resolve it.
I ended up taking your advice and installing Beans. Its a pretty nice ROM and close enough to AOSP.
IamMark70 said:
I tried a couple more things and simply could not get around the activation issue after every reboot. Also always had to go in and change it from nv to rium/sim. I simply don't see how everyone using AOSP ROMS isn't running into this issue on the S3, and I have yet to see one definitive answer on how to resolve it.
I ended up taking your advice and installing Beans. Its a pretty nice ROM and close enough to AOSP.
Click to expand...
Click to collapse
yep its pretty good rom i like it. im kinda having a issue with my picture messages though but probably had a dirty flash when i chose the aosp mms. if you like touchwiz also check out cleanrom its a great stock rom best stable rom and pretty great battery life as well and beans rom i think is based off clean well your welcome hope you enjoy the beans rom aslo i had issues with the sim card to so your not alone
IamMark70 said:
I installed CarbonROM 1.6.1 on my S3 yesterday, and every time I reboot the phone, it goes to an activation screen that never finishes. Additionally, my phone number displays incorrectly. I can fix this by going in and out of Airplane mode and changing the CDMA subscription. But it just reverts back after a reboot (along with the activation screen).
This has been mentioned several times in the developer forum, but I have not found a solution to make it work. I performed a clean install (factory reset, wipe cache and dalvik cache, etc.) along with another install on top of the same ROM without wiping. Does anyone have any suggestions on how to fix this?
Thanks.
Click to expand...
Click to collapse
I downloaded Liquid Smooth 2.4, and it finally addressed the issue of the activation screen popping up after every reboot. So I'm extremely happy and loving the ROM!
Hi all - This is my first post and I am sorry if I'm breaking a rule. I have tried searching for a resolution to this issue before joining up but could not find anything specific to my phone, rom, issue.
Background:
I rooted my phone a while back but for some reason never flashed to a custom rom, just wanted the root. Last week I flashed after some trial/error to AOKP. I cleared the data/cache and did a fresh install of AOKP 4.2.2 with the 2013-03 package of GAPPS. I installed my Titanium Backup'd apps overtop via the app, not an update.zip.
Situation:
My voicemail notification is not going away after I get a voicemail. I will get the notification (sometimes quicker than other times) but after I call my voicemail, listen to the message and delete it the notification does not go away. I have to go into the Phone app-info and force stop/clear data for the notification to go away.
Phone details:
Sprint Samsung Nexus S 4G
AOKP 4.2.2 (goo.im-devs-qnhoang81-crespo4g - aokp_crespo4g_unofficial_2013-05-25.zip)
GApps gapps-jb-20130301-signed.zip
No custom voicemail program - typical Sprint voicemail setup.
If no one is aware of a good resolution with my specific setup, I would also appreciate suggestions of ROMs w/ latest Android that fellow Sprint customers arent having this issue with on the Nexus S 4G.
Thank you very much and I appreciate your patience if I did something wrong with this thread.
I've had this happen with slimrom. I either did a funky flash or found some other way of mucking up my install.
I eventually just did a full wipe and have been fine ever since.
weedy2887 said:
I've had this happen with slimrom. I either did a funky flash or found some other way of mucking up my install.
I eventually just did a full wipe and have been fine ever since.
Click to expand...
Click to collapse
+1 to doing a full wipe (then adding) re-install...
If a full wipe and re-install doesn't fix your issue with the rom ( as I can't speak for app behavior ) flash back to stock and start over, remembering to always back up your data first..
Thanks guys, thinking back I went from stock 4.1.1 to AOKP 4.2.1 then to AOKP 4.2.2. I thought I did clean installs both times. Is it possible that something with my Backup apps is causing the issue? Like if I'm restoring phone settings from a previous version to the new version?
If that didn't fix it.... go into settings/ Apps scroll along the top until you see ALL apps and scroll down to phone...clear data...
I've got a bit of an issue here. Out of nowhere (I've had the latest OTAs for about 2 weeks now) I am unable to receive SMS. When one tries to come through I got a "com.android.phone has stopped". I was bone stock, no unlocked bootloader or anything. Since then, I have tried a couple different ROMs but still seem to be unable to get SMS. MMS come through fine and I can send outgoing messages, but SMS do not work. Data also seems to work fine.
Any ideas would be incredibly helpful.
Thank you!
ETA : On the first boot of a stock + root install, I was able ot send one before getting the error. I don't understand. After the error pops up once, I can not get any more SMS.
ETA 2 : I have flashed the factory CM11 image and still get the issue on CM11. I am at a loss and have no idea what else to do. It seems to be a hardware problem.
ETA 3 : Here is my exact crash report.
java.lang.NullPointerException: Attempt to invoke virtual method 'long com.android.internal.telephony.SmsMessageBase.getTimestampMillis()' on a null object reference
at android.telephony.SmsMessage.getTimestampMillis(SmsMessage.java:625)
at com.android.internal.telephony.InboundSmsHandler.notifyAndAcknowledgeLastIncomingSms(InboundSmsHandler.java:621)
at com.android.internal.telephony.InboundSmsHandler.handleNewSms(InboundSmsHandler.java:510)
at com.android.internal.telephony.InboundSmsHandler$DeliveringState.processMessage(InboundSmsHandler.java:397)
at com.android.internal.util.StateMachine$SmHandler.processMsg(StateMachine.java:966)
at com.android.internal.util.StateMachine$SmHandler.handleMessage(StateMachine.java:789)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.os.HandlerThread.run(HandlerThread.java:61)
I had the exact same problem on my wife's OPO, rooted, stock ROM, though it turned out slightly differently. The update gave the never-ending com.android.phone error. You can go into Airplane Mode to stop the crash. I read through the crash logs, and figured it was something to do with the APN. I deleted the APN, turned off Airplane Mode, and the crash stopped.
Phone and SMS work fine, as does wi-fi. However, I couldn't get any data at all. Not a great solution. I couldn't manually set the APN either, since I got a "APN Settings not allowed for this user" message, and removing the SIM, rebooting without it, then inserting it again, didn't help.
Also, root was removed. I installed TWRP and re-flashed the SuperSU zip file (make sure you go directly into recovery after the fastboot reboot or it'll flash Cyanogen Recover on top of TWRP and you have to start over!).
I did a full Titanium Backup as well as a Nandroid backup to a USB-OTG drive. Next step is to do a factory reset in TWRP and see if that fixes the APN issue.
Synyster06Gates said:
I've got a bit of an issue here. Out of nowhere (I've had the latest OTAs for about 2 weeks now) I am unable to receive SMS. When one tries to come through I got a "com.android.phone has stopped". I was bone stock, no unlocked bootloader or anything. Since then, I have tried a couple different ROMs but still seem to be unable to get SMS. MMS come through fine and I can send outgoing messages, but SMS do not work. Data also seems to work fine.
Any ideas would be incredibly helpful.
Thank you!
ETA : On the first boot of a stock + root install, I was able ot send one before getting the error. I don't understand. After the error pops up once, I can not get any more SMS.
ETA 2 : I have flashed the factory CM11 image and still get the issue on CM11. I am at a loss and have no idea what else to do. It seems to be a hardware problem.
ETA 3 : Here is my exact crash report.
java.lang.NullPointerException: Attempt to invoke virtual method 'long com.android.internal.telephony.SmsMessageBase.getTimestampMillis()' on a null object reference
at android.telephony.SmsMessage.getTimestampMillis(SmsMessage.java:625)
at com.android.internal.telephony.InboundSmsHandler.notifyAndAcknowledgeLastIncomingSms(InboundSmsHandler.java:621)
at com.android.internal.telephony.InboundSmsHandler.handleNewSms(InboundSmsHandler.java:510)
at com.android.internal.telephony.InboundSmsHandler$DeliveringState.processMessage(InboundSmsHandler.java:397)
at com.android.internal.util.StateMachine$SmHandler.processMsg(StateMachine.java:966)
at com.android.internal.util.StateMachine$SmHandler.handleMessage(StateMachine.java:789)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.os.HandlerThread.run(HandlerThread.java:61)
Click to expand...
Click to collapse
Raketemensch23 said:
I had the exact same problem on my wife's OPO, rooted, stock ROM, though it turned out slightly differently. The update gave the never-ending com.android.phone error. You can go into Airplane Mode to stop the crash. I read through the crash logs, and figured it was something to do with the APN. I deleted the APN, turned off Airplane Mode, and the crash stopped.
Phone and SMS work fine, as does wi-fi. However, I couldn't get any data at all. Not a great solution. I couldn't manually set the APN either, since I got a "APN Settings not allowed for this user" message, and removing the SIM, rebooting without it, then inserting it again, didn't help.
Also, root was removed. I installed TWRP and re-flashed the SuperSU zip file (make sure you go directly into recovery after the fastboot reboot or it'll flash Cyanogen Recover on top of TWRP and you have to start over!).
I did a full Titanium Backup as well as a Nandroid backup to a USB-OTG drive. Next step is to do a factory reset in TWRP and see if that fixes the APN issue.
Click to expand...
Click to collapse
Unfortunately nothing has worked. I have fully wiped the phone MANY times. I installed 4 different 5.0.2 ROMs, rolled back to factory 4.4.4 ROM via fastboot, and even tried a 5.1.1 ROM this morning. The only time it crashes is when I receive a text.
Synyster06Gates said:
Unfortunately nothing has worked. I have fully wiped the phone MANY times. I installed 4 different 5.0.2 ROMs, rolled back to factory 4.4.4 ROM via fastboot, and even tried a 5.1.1 ROM this morning. The only time it crashes is when I receive a text.
Click to expand...
Click to collapse
Have you tried flashing a new modem at all? It seems the only thing that would be the same still after flashing all of those various ROMs would be the modem. Seeing as you have issues with the communication, I'd say modem would be a good thing to try..
Try flashing your rom, then the appropriate modem, then boot.
You can get your modem from either here (for OxygenOS) which should work for CM12, 12.1, etc. or here (for CM11/CM11s)
The_Symbiote said:
Have you tried flashing a new modem at all? It seems the only thing that would be the same still after flashing all of those various ROMs would be the modem. Seeing as you have issues with the communication, I'd say modem would be a good thing to try..
Try flashing your rom, then the appropriate modem, then boot.
You can get your modem from either here (for OxygenOS) which should work for CM12, 12.1, etc. or here (for CM11/CM11s)
Click to expand...
Click to collapse
I'm beginning to think T-Mobile had an issue with the OPO devices or something. I was speaking with someone across the country (eliminating a tower problem) that was running Oxygen OS and I had restored to COS12 at the time. Both of our devices suddenly got all the texts that had previously not come in and they started working correctly at the same time. As of right now it seems I'm good to go.
I recently upgraded my phone from 4.4.4 to the latest OTA. It was working fine for a while but it crashed, rebooted and keeps (re)optimizing the apps. It'll get stuck on some of them for a long time and might make it through, or I hard reboot it and it does it all over. Whenever it does make it through, it says "starting apps" and then reboots and does it all over again.
I've cleared the cache multiple times and restored the stock recovery, but still not working. Does anyone else have any other suggestions that I could try??
Also I read somewhere that there was a zip I could possibly flash to use all the cores, as lollipop only uses one during this process? Does anyone know where that is?
Thanks.
natboy said:
I recently upgraded my phone from 4.4.4 to the latest OTA. It was working fine for a while but it crashed, rebooted and keeps (re)optimizing the apps. It'll get stuck on some of them for a long time and might make it through, or I hard reboot it and it does it all over. Whenever it does make it through, it says "starting apps" and then reboots and does it all over again.
I've cleared the cache multiple times and restored the stock recovery, but still not working. Does anyone else have any other suggestions that I could try??
Also I read somewhere that there was a zip I could possibly flash to use all the cores, as lollipop only uses one during this process? Does anyone know where that is?
Thanks.
Click to expand...
Click to collapse
To make things clearer. Previous what ROM were you on? After your proclaimed (OTA), what was the ROM suppose to be?
I went from the Oneplus One CM 4.4.4 to the CM 5.1 OTA. Not sure why you're don't believe me..
I think I might have bad memory or flash or something at this point..
So since yesterday I've tried using the tutorials here to flash stock Kitkat with the same errors happening. When it boots up, I get a done of crashes on things like gapps and process.acore. I also tried flashing the stock Lollipop; both using the non fastboot and fastboot way. Every time wiping everything with all the same results. The only rom I've had some slight uptime with has been slimrom without gapps as there's not much running there. Once I add the gapps package to it, processes start crashing again.
Does anyone know of a memory/cpu/flash test I could try, or any other suggestions? Thank you.