Related
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
cappiez said:
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
I had the same issue today between 2 and 3, but it wasn't letting me send texts even though I could receive them. Maybe a network hiccup?
I am on stock radios, didn't know new ones came out. It is working for me now.
in the same boat
looks like we're in the same situation. I looked through the threads and this is another case of call errors. I found this thread and one other, not sure if it was droid dna related.
cappiez said:
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
sjhanson Today, 12:20 AM #1035
Junior Member
Thanks Meter 1
Posts: 11
Join Date: Jan 2011
I am running 3.0.3 now. I was running Viper until the big man published 3.0.3, then i switched back. But even on Viper I was getting the same COM.PHONE.ANDROID has stopped error.
Cheers!
http://forum.xda-developers.com/showthread.php?t=2126386&page=2
borkborkbork! said:
looks like we're in the same situation. I looked through the threads and this is another case of call errors. I found this thread and one other, not sure if it was droid dna related.
Click to expand...
Click to collapse
Link to any of the other threads?
http://forum.xda-developers.com/showthread.php?t=2157855
xDexter said:
Link to any of the other threads?
Click to expand...
Click to collapse
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
TheJ0hnman said:
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
Click to expand...
Click to collapse
You went back to S-ON or just a different kernel?
TheJ0hnman said:
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
Click to expand...
Click to collapse
I also tried going back to stock ruu , nothing worked for me
borkborkbork! said:
I also tried going back to stock ruu , nothing worked for me
Click to expand...
Click to collapse
I am having 0 issues anymore with S-OFF and .torrented's rom and suggested R/W kernel: http://forum.xda-developers.com/showthread.php?t=2150262
xDexter said:
I am having 0 issues anymore with S-OFF and .torrented's rom and suggested R/W kernel: http://forum.xda-developers.com/showthread.php?t=2150262
Click to expand...
Click to collapse
com.android.phone .. but I still get my txt messages, go figure. I think my partitions may be in rare shape from rom's, kernals, and all the other numerous changes. Never been the same after I got error 7 on schatka 3.0.2, I switched back and forth from viper/hatka and twrp/cwmr
I took my phone into Verizon yesterday, explained the situation. Told them it started after ota, and I had done a factory reset already. They tried a new SIM card to no avail, overnighting a new phone.
Sent from my HTC6435LVW using xda premium
xDexter said:
You went back to S-ON or just a different kernel?
Click to expand...
Click to collapse
Forgot about this post, sorry. Did not go back to s-on, just flashed stock kernel from here: http://d-h.st/Ma1, boot.img via fastboot and then the modules zip contained within in recovery, and everything was good.
This didnt work for me . Any other suggestions?
cappiez said:
I took my phone into Verizon yesterday, explained the situation. Told them it started after ota, and I had done a factory reset already. They tried a new SIM card to no avail, overnighting a new phone.
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
Basically I hd the same situation happen to myself, no calls or data but wifi was good. Mine started to fail slowly , firs \t it was showing a 1X connection but dl were about 3G speeds. Next I lost signals in areas I never had signal issues with. Then total loss. New sim card and spent hours on the support line and a replacement unit.
Got a PM request for assistance, and thought I don't have a lot of tips to offer other than what I provided before, I'm going to post a more detailed overview (as I remember it, it's been awhile...) in case it's helpful for any other who may come across it later. The bottom line for me was that once things broke, it didn't work again until I flashed stock kernel via fastboot +modules in recovery and did a clean install of Hatka 3.03 w/ Sense launcher. That said, because of my flashing compulsion and failure to fully test things once installed, I can't pinpoint the exact step at which things broke.
Initially, I: Bought phone and factory reset, did not take Verizon OTA. Fiddled around, hated Sense, unlocked, flashed recovery, flashed Viper 1.1.0 (?, whatever the base was), booted and setup, fiddled around, hated Sense, wiped data, flashed 3 subsequent Viper updates (1.1.1,2,3 maybe?), booted and setup, fiddled around, hated Sense. Wiped and reinstalled de-Sensed Viper a few times in an attempt to get rid of Sense as much as possible.
Then things get murky. I did s-off, and at some point flashed (recovery) a kernel, Cubed I think. Wifi or something was borked (as I understand is the case with Cubed/Viper), and I flashed stock kernel back via recovery (no modules, I didn't catch that part at the time) and restored my backup for good measure, leaving me on fully functional Viper 1.1.3. Everything worked for a few days, but I continued to hate Sense, and began searching for something more sensible. At some point I flashed Hatka 3.03 w/ de-Sensed options, went to 320 DPI, and thought everything was fine for about 18 hours until I realized my phone was warm, and figured out it was rebooting every time I received (or placed) an incoming call (boss was pissed and kept trying to call me, already gives me a hard time about being an Android fanboy so I'm never going to hear the end of that). After a few hours of fiddling and various recovery attempts including restores and full wipe/clean installs of Viper, I finally managed to get things up and running with A. flashing stock kernel via fastboot + modules in recovery and a full wipe/clean install of Hatka 3.03 w/ Sense + Xperia launchers and eventually a 380 DPI.
One of or some combination of the s-off/custom kernel/failure to reinstall stock kernel modules/de-Sensed/low DPI/pin lock/Widget Locker/Viper combo I had going fouled something up, which I know is not entirely helpful. If I found myself in this situation again, I would flash stock boot.img via fastboot + modules in recovery, and probably flash a stock ROM to rule out anything else, then wipe and flash things from there until I got where I wanted or it broke.
For the record, I'm now back on my Galaxy Nexus until stable-ish CM 10.1 is within sight or I get tired of waiting and sell the thing, I just can't tolerate Sense.
same issue
I've been reading wherever I see this topic and haven't found the answer that I'm looking for. Have tried everything said but nothing has fixed my problem can't make or receive calls. This problem happened after I turned s-off have relocked boot loader, flashed RUU, reset factory, re-unlocked bootloader, re-flashed different roms, and flashed radios still not working. No doubt it is a software issue. Does anyone know how to format internal storage on this phone. My thinking is if that can be done problem should go away and then can re-flash to stock. Any help would be most appreciated.
jimmydee62 said:
I've been reading wherever I see this topic and haven't found the answer that I'm looking for. Have tried everything said but nothing has fixed my problem can't make or receive calls. This problem happened after I turned s-off have relocked boot loader, flashed RUU, reset factory, re-unlocked bootloader, re-flashed different roms, and flashed radios still not working. No doubt it is a software issue. Does anyone know how to format internal storage on this phone. My thinking is if that can be done problem should go away and then can re-flash to stock. Any help would be most appreciated.
Click to expand...
Click to collapse
Have you tried fixing permissions? In some other post I read phone process force closing was just a matter of wrong permissions.
In other hand I think if you format system, data and cache the phone storage would just keep hboot and recovery; at that point you could only run RUU to stock or adb sideload from recovery if your CWM version has the feature.
Sent from my HTC6435LVW using xda app-developers app
still problem
Yes have fixed permissions. Also have formatted everything I could in CWM still have problem. Is there a way to format with ADB commands?
I recently updated my phone's ROM to the Angry Bean ROM (Virgin Mobile version of Wild for the Night). Everything worked great (SMS, MMS, 4G, etc.), but then I received the "Low Storage Space" message. I hopped on the forums and found the WiMax fix zip and flashed it. It took care of my issue with the low storage space, but now I cannot receive text messages.
No matter what I do, I cannot get them working. I can send, I can send / receive phone calls, and I can flash back to a non-JB ROM and they start working again.
Any help would be appreciated
seabiscuit68 said:
I recently updated my phone's ROM to the Angry Bean ROM (Virgin Mobile version of Wild for the Night). Everything worked great (SMS, MMS, 4G, etc.), but then I received the "Low Storage Space" message. I hopped on the forums and found the WiMax fix zip and flashed it. It took care of my issue with the low storage space, but now I cannot receive text messages.
No matter what I do, I cannot get them working. I can send, I can send / receive phone calls, and I can flash back to a non-JB ROM and they start working again.
Any help would be appreciated
Click to expand...
Click to collapse
I have confirmed that this is only due to flashing the WiMax Zip (which has to be done). It works fine up until that moment. Then I have to flash back to a stock ROM to get it functioning again (then back to a JB ROM, where it works until I have to Flash the WiMax Log Fix).
seabiscuit68 said:
I have confirmed that this is only due to flashing the WiMax Zip (which has to be done). It works fine up until that moment. Then I have to flash back to a stock ROM to get it functioning again (then back to a JB ROM, where it works until I have to Flash the WiMax Log Fix).
Click to expand...
Click to collapse
did you flash the MMS fix? i know its built in but sometimes you need to just like the Wimax one.
I achieved s-off using moonshine a couple of days ago.
I then proceeded to flash CyanFox CM10.2 and found it a bit more beta than what I wanted and only used it for about a day.
I then switched to NOS google play edition which I loved but came across an odd error when installing certain apps. Something along the lines of "Cannot access SD or Storage".
I then tonight decided to switch to ViperDNA as I was now looking for a desensed version of a ROM. After installation I noticed that I couldn't get a connection to Verizon and the APN info was not right. So I decided to flash the rom 2 more times with no eval.
Next I installed Carbon and found that I had the same issue but this time the AOSP (I think) setup that says "Welcome" would come back with "Could Not Activate Your Phone".
I then researched a number of things and could not get the cell service to connect.
I read that deactivating my service was the issue and that I would have to back to a stock rom. I am not to sure of this but I then flashed the Stock Rooted 2.06 ROM and then started receiving 'SIM Card Not Found' issues. My SIM card was removed and then reinserted and the device rebooted still nothing.
I then read elsewhere that flashing different radios might help but the only thing that I can across was the 1.01.04.0308 firmware which is the same that I have. I decided to fastboot and try that anyway.
So hopefully I have done enough research where you folks won't call me a noob. But help?
Thanks
So I used http://forum.xda-developers.com/showthread.php?t=2293919 to go s-on and back to stock and still nothing.
I then decided to set a APN and go the data working but the voice and sms doesn't. Any thoughts?
Thanks Again
Fixed
Well after I flashed RUU, I did a factory reset from the settings menu.
I think that flashed the old radios for me. I would like someone to confirm that this is what fixed it.
Thanks to the incoming call issue due to VoLTE, I've decided to return my phone to stock. I read a post that said all I'll have to do is lock my bootloader and use an RUU. Well the RUU freezes. I've tried it three times, waiting for about 30 minutes each time, but never could get pass the ROM loading stage. I don't quite know what the issue is. I've tried on 2 different laptops, both running Windows 7 Pro. I'm currently running Venom 4.6.0 with TWRP recovery and S-ON. I downloaded 4.28.502.1 RUU as that was the stock ROM I was running before going to Venom. Any thoughts or suggestions?
Sometimes apps like HTC sync will cause issues with ruu exes. Be sure nothing else that can talk to the phone is installed.
Thanks, I'll try with sync manager not running.
jfalgout2003 said:
Thanks, I'll try with sync manager not running.
Click to expand...
Click to collapse
Be sure it is uninstalled. I tried with it "not running" and still had the issue. I had to completely uninstall HTC Sync.
Thanks for the advice. Finally have my phone back to stock. It's quite unfortunate, but I'll have to live with the bloat until there's a fix for the VoLTE issue on custom ROMs.
Sent from my HTC One_M8 using Tapatalk
Any ideas? Other apps I installed to try (eg Signal) fail too. Stock ROM.
This is my fist post, have visited many times. Here we go.
As a LG V20 owner, I recommended the V30+ to two people at work. In a matter of 24 hours, both units stopped sending and receiving emails. I have taken the sims out and tested these in other phones, not a sim issue. I then moved my sim (Telstra Aus) into the V30 and only in the Messaging app, it came up with the message No SIM. This I thought might be a sim slot issue, moved it into the other slot closest to the outside. This worked for about an hour. Then the same issue occurred again. It has to be software, an update or a network change that has caused this. I did a network setting reset, have cleared cache for messaging app. SAFE MODE etc. Very strange.
yanni_pap said:
Any ideas? Other apps I installed to try (eg Signal) fail too. Stock ROM.
Click to expand...
Click to collapse
Yes I used Messenger app for SMS and this failed. It sounds network setting related but still testing.
I had the same problem on my V30, suddenly SMS has stopped working. (I'm using Textra app)
I checked the sim card on the other phone and it was ok.
I found on the internet that other V30 are also affected.
The solution was to install the Message app from Google and run it.
Now SMS is working on Textra and also on the stock app.
Whoa, didn't see this before I posted in another thread. Same problem here, but I already had Messages installed! Wonder if it's just this phone for some reason?? My partner is also on VZ (S7) and can send SMS
edit: apparently it's something Google broke. Temp fix is to disable Carrier Services!
I just recently started having text messages not sending. I am on Verizon LG V30 using the vs996 30c debloated rom. Everything has worked fine until last week when I installed the latest Resurrection Remix rom. Since these roms’ tethering and WiFi do not work, I tried installing the us998 modem zip. I don’t know if that is the problem or not, but, I could not get it to work. I have since reinstalled my 99630c debloated rom and have now lost the ability to send text messages, although I can receive texts just fine. I have done clean installs and dirty installs of the rom. I, just yesterday, did a restore of a previous 99630c backup, changed messaging apps, etc. I even reinstalled Verizon’s messaging app.The messaging problem still persists.
i just got off the phone with a very nice Verizon tech, who spent about 40 minutes trying to help me. No success. She said everything appears to be working fine on their end. She ran out of things to try. She thinks my rooting the phone might possibly have something to do with it, which I agree with.
Does anyone have a working link to John Fawkes vs99630c zip? The one one his zip thread does not download for me. I thought I would try starting again with that zip. Maybe I need to try a different modem download?
Any suggestions much appreciated. Thx
gimpy1 said:
I just recently started having text messages not sending. I am on Verizon LG V30 using the vs996 30c debloated rom. Everything has worked fine until last week when I installed the latest Resurrection Remix rom. Since these roms’ tethering and WiFi do not work, I tried installing the us998 modem zip. I don’t know if that is the problem or not, but, I could not get it to work. I have since reinstalled my 99630c debloated rom and have now lost the ability to send text messages, although I can receive texts just fine. I have done clean installs and dirty installs of the rom. I, just yesterday, did a restore of a previous 99630c backup, changed messaging apps, etc. I even reinstalled Verizon’s messaging app.The messaging problem still persists.
i just got off the phone with a very nice Verizon tech, who spent about 40 minutes trying to help me. No success. She said everything appears to be working fine on their end. She ran out of things to try. She thinks my rooting the phone might possibly have something to do with it, which I agree with.
Does anyone have a working link to John Fawkes vs99630c zip? The one one his zip thread does not download for me. I thought I would try starting again with that zip. Maybe I need to try a different modem download?
Any suggestions much appreciated. Thx
Click to expand...
Click to collapse
See my solution directly above your question. It's not "rooting" that caused it, it's "Google" that caused it. Uninstalling or freezing Carrier Services will fix it. Did for me.
Check the litany of * reviews from today alone:
https://play.google.com/store/apps/details?id=com.google.android.ims&showAllReviews=true
Also, both the standard and debloat ROMs for VS99630c from their respective threads and androidilehost are downloading fine for me.
Thx, but did not work for me. I went into TiBu and found carrier services sitting in the non installed portion of the apps. So, I installed it (first with app, then with data) and tried both messaging apps with it installed. That did not work, so I went back into TiBu again and froze it. It still does not work.
I have tried downloading the standard zip from Fawkes zip thread 8 or 10 times or so. It gets to about 8 or 9% , then gives the message unsuccessful.
I will keep trying. Thx for your suggestions.
As an edit. My phone has also started giving me problems with my fingerprint recognition and my phone dialed has suddenly changed looks forcing me to constantly press and swipe an unlock button to keep the dial pad open if I hesitate too long in punching in numbers or trying to change to speakerphone from there.
I don’t know if it is something I have done/installed (wrong modem perhaps?).
And having the new XDA transition at the same time certainly didn’t help .
gimpy1 said:
Thx, but did not work for me. I went into TiBu and found carrier services sitting in the non installed portion of the apps. So, I installed it (first with app, then with data) and tried both messaging apps with it installed. That did not work, so I went back into TiBu again and froze it. It still does not work.
I have tried downloading the standard zip from Fawkes zip thread 8 or 10 times or so. It gets to about 8 or 9% , then gives the message unsuccessful.
I will keep trying. Thx for your suggestions.
Click to expand...
Click to collapse
I don't know what to tell you about the downloads, confirmed they work.
You don't need to freeze CS, you can literally just uninstall it from the Play store. It's just an enhancement for the Google MEssages app they broke. if you don't use Messages, you surely don't need it. I don't know what you meant about CS showing up in the "non installed portion of the apps". It's either installed and frozen or thawed, or it's not. Maybe you had a backup there for reasons? Regardless, you certainly need to reboot after changing CS, not sure if you did that.
You have alot of other issues coming from RR, then flashing a modem, then trying to dirty flash VS996. Since you have TB already, you should definitely backup your apps, then Maybe clean flash VS99630c once you've followed the WTF thread. You should probably wipe your system after the other ROMs and just start over.
That certainly was a quick answer. In TiBu, under “backup/restore”, I have all the apps that are currently on my phone—a very long list. This list can be frozen, etc., and is bolded and colored fonts. Scrolling down that list, it ends and a list starts that is not bolded and has lines thru it. I guess these are apps, etc. that I have, at one time, had on the phone and can be re installed via TiBu.
I was trying to “start over” by downloading the vs99630c rom and try it. Where were you thinking I need to start over at? I wish to work only on “zips” via twrp, as I don't have much luck/knowledge with kdz and computers.
Thx, again.
Again, I'm the furthest thing from the expert here, but he's on travel! Check the WTF thread, because I'm not sure what happens when you wipe with the flashes you've made. But you'd probably start from 6.7. MORE TWRP ACTIONS here:
https://forum.xda-developers.com/t/...ar-instructions.3790500/page-10#post-76584629
I would reboot to TWRP and do a complete system backup in case this goes tits up you can restore that from TWRP. Then I would boot to OS and back up everything in TB, then delete all uninstalled backups through the batch actions. Then reboot to TWRP again, wipe, install the VS99630c ROM, install MAgisk, reboot. Make sure your install works then restore your apps through TB.
Ok, thx. I wish to install the vs99630c rom zip now (not the debloated) and am unable to download it from JohnFawkes LG V30 vs 996-30c thread from here on xda. I have tried via my phone about a dozen times now and it stops now generally after the 10 to 20% zip has downloaded. I even tried it a couple of times downloading onto a laptop. Can you possibly point me to a different link that I can try? I need to be on Verizon’s vs 996 and not on the 998 rom, I think? Sorry for the big bother.
Well, I did finally find a download mirror on here from chazzmatts thread using his mirror. It is downloaded now. I will try this installation before going thru the wtf steps you referred me to. If this doesn’t work, then i will try it.
thx, again for your help.
As an update, I did a clean wipe and installed this zip. So far, it seems to have settled things down for. I was able to text (2) and make a phone call. Both worked. I did agree to everything they asked (I normally refuse things such as location, etc.). I’m happy for now. Later, I may try to reinstall the debloated zip.
Ideveraux, thx for all your help on here. I really appreciate it.
Make sure you backup TWRP and TB. Just saying!
And to the OP, I’m sorry I hijacked your thread. I hope you got yours solved, too.
I had this problem after owning the phone for several days.
I'm not sure why, but when i installed Google's "Messages" app, the problem was fixed.
I didn't have to run the messages app, just install it. The stock app suddenly started working again.
I then uninstalled google messages (without ever running it), and the next day I had the same problem.
Once again; I installed google messages, and the problem solved itself without ever running google messages.
This time; I haven't uninstalled google messages.
I'm guessing that something about SMS settings got messed up (i checked them when the problem first happened and couldn't find a problem), and installing a new message app restored the settings to normal.
TLDR: if SMS stops working, Install Google Messages. Problem solved.
Lozv said:
I had this problem after owning the phone for several days.
I'm not sure why, but when i installed Google's "Messages" app, the problem was fixed.
I didn't have to run the messages app, just install it. The stock app suddenly started working again.
I then uninstalled google messages (without ever running it), and the next day I had the same problem.
Once again; I installed google messages, and the problem solved itself without ever running google messages.
This time; I haven't uninstalled google messages.
I'm guessing that something about SMS settings got messed up (i checked them when the problem first happened and couldn't find a problem), and installing a new message app restored the settings to normal.
TLDR: if SMS stops working, Install Google Messages. Problem solved.
Click to expand...
Click to collapse
I tried that initially and that's not the accepted fix at all. Read above.