Database Info

Help with Evo setup/issues with cm7 (evervolv atm)

Hey Everyone,
This is probably my first or second post here ever. I have just recently really gotten into trying different roms and flashing my phone. I can generally find my answer in posts already around but am having issues that I cannot find answers to.
1. I have a voice mail icon that will not go away. I have flashed Evio sense based Rom and Evervolv cm7 based rom and it will show up with both. I called Sprint and had them try to clear some stuff out (it was fun trying to keep them from figuring out I wasn't in sense anymore ) which has actually lead me to not have any data connection except for 4g. I am doing a recovery of an old sense rom that I have a nandroid of to check and see if a profile update will fix this issue though. My main concern is the voice mail icon. I do not use google voice and have my inbox completely empty. I also have called myself and left a message and gone in and dialed in and checked it and it still is there. Am I going to need to do a full reinstall from scratch to avoid having this? My guess is it could somehow be saved in my TI backup that I have and showing up after I restore the data. Is this possible?
2. I really do not like the interface for the phone in cm7. I know I can get Go Contacts or Dialer One to replace the contact search and the initial plug in of the number but once I call it switches to the same in phone interface and this is the interface that I really want to change. It seems like every thread that I have found just suggest changing to Dialer One or another app like this but does not change the actual in phone look. It also seems really unresponsive sometimes taking up to 5 or 10 seconds to end a call and leaving me standing there poking the end call button over and over until it responds. Does anyone else have this issue?
3. The final issue I am having is with MMS and from what I have read it seems to be an issue with cm7 in general. Is there any workaround for this? The other parts I feel like there is probably something that I am just missing and can deal with but if I cannot get MMS working then its probably going to be a deal breaker for cm7 until it is fixed.
In closing I would like to thank the community here. There is a lot of hard work and dedication to helping others that goes on and I really appreciated any help that you can give me! I know my questions are wordy and long but I wanted to explain what I have done to try to fix these issues on my own before coming here to you all. Thanks again!

I have the voicemail icon issue as well. I have had it with other roms. When I loaded up this time, the first thing I did was set up Google Voice and I didn't have the issue. All of the sudden, a couple of hours later, the ROM forgot I was using Google Voice and then what do you know...the beloved voicemail icon shows up. I have seen several "solutions" for this, but none of them work. Why isn't there a setting to clear the icon or an app that will do it?...or is there?...or maybe a command in Terminal Emulator.
I am using TAKEphONE as my dialer as I have had success with it. As far as I know you can't change the actual phone app. Sense is just a skin on top of the phone app as far as I can tell because when you have Google Voice ask you if you want to use Voice or Sprint, you can see the stock Android phone app for a few seconds.
I do not have any experience today with MMS so I am not sure about that.

The issue with the VM icon is still seeming to haunt me however I flashed Ginger-Ale and if you go settings>call>voice mail icon reset you can get rid of it. I am however unsure if this will be a permanent fix or if it will work after another flash but I will know in about 15 min once I flash the new one by Deck.
I also found that if I went into titanium backup and froze phone.apk (I did this to see if by chance I could get Dialer One to not use the regular CM7 in call phone interface that it removed the Voice Main icon but also caused the phone to repeatedly FC. I ended up having to flash to a nandroid backup which of course brought back the VM icon but it at least let me know where the issue was coming from.

Completely not an answer, but just so you know...
Any time you call Sprint and they do any communication with your phone, they pull the phone's info - rom version, radio, kernel, etc. This information helps them troubleshoot the problems you're having. Usually this will tell them which official release you have on your phone - if you've updated via OTA, etc. So they may not have known that what you're running isn't Sense, but they do know it's a custom rom and that you're rooted. Whether or not the person you were talking to pulled this information, took note of it on your account, or even cares, is something no one can answer. But it is a possibility.
So if you're ever having software issues and you take it in to Sprint (even if you've unrooted) and they refuse to fix it - you'll know why. Of course, you'd have to get a combination of asshole Sprint employees to have issues, but it is a possibility.
I've heard of the tech mentioning the custom rom to some people, so you know that even if they don't say anything, they know.
(from... Evo/MIUI/Tapatalk)

dialer app voicemail storage

i never used the visual voicemail feature before i got my pixel, so it's new to me and i hope this isn't a dumb question that's been answered a million times, but i did searching both on xda-developers and on google and couldn't find an answer.
basically, i switched from verizon to fi the other day and was surprised to see that my all of verizon voicemails stuck around in the dialer app. this seems to me to suggest that they're stored somewhere on the phone itself. before that happened, i figured it was reaching out to verizon every time i played one. problem with this is, since they're on the device now, i figure i'll also probably lose them if i do factory data reset or flash PN on there (which i'd like to do).
so my questions are, where on the device are the recordings stored, and is there a way i can back them up and restore them? may seem silly, but i actually have some voicemails going as far back as february of 2007 (it told me they'd be saved for 21 days but they're still there a full 10 years later!), including some from a friend who passed away a few years ago. of course, i figured they'd vanish when i switched services so this is really all a bonus, but since it seems like there should be a way to preserve them...

needletothebar said:
i never used the visual voicemail feature before i got my pixel, so it's new to me and i hope this isn't a dumb question that's been answered a million times, but i did searching both on xda-developers and on google and couldn't find an answer.
basically, i switched from verizon to fi the other day and was surprised to see that my all of verizon voicemails stuck around in the dialer app. this seems to me to suggest that they're stored somewhere on the phone itself. before that happened, i figured it was reaching out to verizon every time i played one. problem with this is, since they're on the device now, i figure i'll also probably lose them if i do factory data reset or flash PN on there (which i'd like to do).
so my questions are, where on the device are the recordings stored, and is there a way i can back them up and restore them? may seem silly, but i actually have some voicemails going as far back as february of 2007 (it told me they'd be saved for 21 days but they're still there a full 10 years later!), including some from a friend who passed away a few years ago. of course, i figured they'd vanish when i switched services so this is really all a bonus, but since it seems like there should be a way to preserve them...
Click to expand...
Click to collapse
I have a Verizon Pixel and voicemails are stored at Verizon. I still have a voicemail from a friend from 2015 that comes back after every factory reset, new ROM, even going from a Nexus 6 to the Pixel.

strange! so how am i accessing them after switching to a Project Fi SIM card? are you using the visual voicemail feature where they show up in the dialer app?

could it be that the google cloud backup stuff has them stored and that's what's bringing them back for you?

I know I am a little late but I have the answer. I am presuming you mean a hard copy file of the actual voicemail ? As long as you see it there. its really simple
Open the voicemail menu in the dialer app. Expand the voicemail in question , and simply use the send to feature at the bottom and it will export an .amr file to the place of your choice!
PROFIT!

Pixel calls silent on both ends

My Pixel suddenly stopped being able to make and receive phone calls a few days ago. The Phone app is extremely sluggish trying to make a call, will usually finally "connect" and look like the call is open, but I hear nothing but silence on the other side, and the other person can't hear me. It's slow to try and hang up, too. I see calls coming in, and can try and answer, but with the same result. Missed calls are registered. Voicemail also does not work. I can see there is a message, but can't play it.
Running 8.1 with February 5 security patch. Carrier is Verizon. I've gone in the store, and they switched out the SIM card. I've also tried a hard factory reset, all with no difference to the problem. The phone is over a year old, so I think a replacement is not possible...
If anyone can help me or has any ideas, I would greatly appreciate it! Thanks!

It's a hardware problem, Google is aware of the problem, they should replace your device. Contact Google, even if you are out of warranty they will replace the device for you!

OK WORKAROUND FOR ANSWERING CALLS UPDATE:
Found this floating on some other forum, not sure where after this mad dash of a search I did this morning, but original credit to them...
When you receive a call and the phone is active and unlocked, press the power button to lock the phone and bring up the blue call management screen. Now you can swipe to answer.
This seems to work for more than one test call as I've tried this multiple times in a row.
NO REAL WORKAROUND FOR MAKING CALLS YET (outside of airplane mode toggle, or using Google voice/hangouts to place calls).
GOOGLE SUPPOPRT - THIS IS CLEARLY A SOFTWARE ISSUE, not a 3rd party app issue either since the problem goes away for answering calls when you press the lock screen or toggle airplane mode for placing calls. Please STOP ASKING CUSTOMERS TO invest hours of time (or money) FACTORY RESETTING PHONES, or REPLACING/BUYING NEW PHONES.
MY HUNCH, is there is some core google service that isn't being used in SAFE MODE, but starts being used on NORMAL BOOT that is causing all these issue. I really DOUBT its a 3rd party app.

Thanks for your replies. I've contacted Google, and they didn't seem to think it was justification for replacing the phone out of warranty. They said I could either take it to a repair place to fix it or trade it in for the new Pixel 2 and get some money for it.
The workaround for answering calls works to connect the call and start the timer, but I still can't hear the caller and they can't hear me...
I still after much troubleshooting have found no way in which calls are functional. In addition to the attempts made above, I've since tried to uninstall and reinstall the phone app, and also to install a different phone app. No change to the problem. Even more curious, the problem still persists in Safe Mode.
If anyone has any more ideas, I'm all ears! Thanks!

Can't Answer or Make Calls

So far, I can't seem to find anyone else having this exact issue. Starting yesterday, I was not able to answer or make a phone call. The dropdown "incoming call" notification came, but I couldn't tap answer or reject. The button would light up like it was registering my touch, but nothing would happen. I went to my contacts to return the call and nothing happened when I tapped call. I tried manually dialing the number, same thing. I tried other contacts, all the same thing. I restarted the phone and the problem went away, for a little while, then came back ( should note that if I am in my car and on bluetooth, I can answer a call using the car's answer function, but I can't make calls). A few times, the phone would make the call, but maybe a minute to two minutes later, like the Android phone app was moving in super slow motion. Things I have tried: clearing cache/data from phone app, uninstalling all updates from phone app. Nothing seemed to help other than rebooting, but that only works for a little while. I have not yet done a factory reset.
I am on Android 8.1 on T-Mobile.
I run a business and can't be without my phone! This is very frustrating. Google support wasn't much help.
Thanks!
Lou

It's a defective phone by manufacture, it's a crack in the audio codec on the motherboard. Contact Google or the retailer you bought your phone from if you are still under warranty or even if it's finished you should get a replacement from Google anyway.

Thank you. The Google support person I spoke with yesterday didn't mention anything about this. I'll have to reach out to them to see if they will issue a replacement as it's out of warranty. Is this the same issue that the class action suit is about?

louballs said:
Thank you. The Google support person I spoke with yesterday didn't mention anything about this. I'll have to reach out to them to see if they will issue a replacement as it's out of warranty. Is this the same issue that the class action suit is about?
Click to expand...
Click to collapse
Exactly that is the same issue, mine was under warranty but as I am out of Canada, they told me they will replace it only if I bring it back to Canada, unfortunately I am still outside and the warranty finished, I tried to fix the phone at a local shop and they damaged the phone totally trying to fix it, I just bought another one after, but this time I made sure the device was manufactured after 2016, mine is March 2017 and it doesn't have the mic issue.

Alaadragonfire said:
Exactly that is the same issue, mine was under warranty but as I am out of Canada, they told me they will replace it only if I bring it back to Canada, unfortunately I am still outside and the warranty finished, I tried to fix the phone at a local shop and they damaged the phone totally trying to fix it, I just bought another one after, but this time I made sure the device was manufactured after 2016, mine is March 2017 and it doesn't have the mic issue.
Click to expand...
Click to collapse
Looking at the online info for the cracked audio are you sure it's the same issue I'm experiencing. It's not that I can't hear anyone or people can't hear me it's that my phone will not even attempt to make a call or answer a call. It just won't respond to me pushing the "answer" or "dial" button. Also, I haven't been able to replicate this issue in safe mode. Maybe something else at work??

louballs said:
Looking at the online info for the cracked audio are you sure it's the same issue I'm experiencing. It's not that I can't hear anyone or people can't hear me it's that my phone will not even attempt to make a call or answer a call. It just won't respond to me pushing the "answer" or "dial" button. Also, I haven't been able to replicate this issue in safe mode. Maybe something else at work??
Click to expand...
Click to collapse
It's the same thing my phone used to do, I even reinstalled the factory image and setup a new phone and still acted the same.. I hope yours is not but unfortunately if you had the same experience in safe mode then it is what it is my friend

Alaadragonfire said:
It's the same thing my phone used to do, I even reinstalled the factory image and setup a new phone and still acted the same.. I hope yours is not but unfortunately if you had the same experience in safe mode then it is what it is my friend
Click to expand...
Click to collapse
Ok, though I have NOT been able to replicate it in safe mode, so that's why I was wondering if maybe something else. I'll try to get them to replace my phone and hopefully that fixes it.

louballs said:
Ok, though I have NOT been able to replicate it in safe mode, so that's why I was wondering if maybe something else. I'll try to get them to replace my phone and hopefully that fixes it.
Click to expand...
Click to collapse
Try to factory reset it from the settings, maybe it will work and it turns out to be some issue/app that is making your phone to act like that, just back up everything on your phone as the factory reset deletes everything on the phone. If it didn't work out then you should replace your phone.

Alaadragonfire said:
Try to factory reset it from the settings, maybe it will work and it turns out to be some issue/app that is making your phone to act like that, just back up everything on your phone as the factory reset deletes everything on the phone. If it didn't work out then you should replace your phone.
Click to expand...
Click to collapse
Thanks! I was hoping to avoid as it's super annoying, but that's my last option.

I'm glad I've found this thread - I have the exact same issue. Tmobile and a pixel (1) that this just started happening with.
If i reboot the phone I can dial out, but after that it won't dial anymore. If I do attempt to dial, it seems to dial like the OP says, a few minutes later.
I'm able to answer the phone from the lock screen (by swiping up) but the drop down with answer and decline don't work when the screen is unlocked.
I've tried removing updates, clearing cache and defaults on the phone app, no luck. A reboot is the only fix, but it seems to last only for 1 call.
I havent dropped the phone or anything. @louballs, please report your findings after a reset, I'll keep playing with my phone too, maybe we can figure this out.

Alaadragonfire said:
Try to factory reset it from the settings, maybe it will work and it turns out to be some issue/app that is making your phone to act like that, just back up everything on your phone as the factory reset deletes everything on the phone. If it didn't work out then you should replace your phone.
Click to expand...
Click to collapse
nichos said:
I'm glad I've found this thread - I have the exact same issue. Tmobile and a pixel (1) that this just started happening with.
If i reboot the phone I can dial out, but after that it won't dial anymore. If I do attempt to dial, it seems to dial like the OP says, a few minutes later.
I'm able to answer the phone from the lock screen (by swiping up) but the drop down with answer and decline don't work when the screen is unlocked.
I've tried removing updates, clearing cache and defaults on the phone app, no luck. A reboot is the only fix, but it seems to last only for 1 call.
I havent dropped the phone or anything. @louballs, please report your findings after a reset, I'll keep playing with my phone too, maybe we can figure this out.
Click to expand...
Click to collapse
Well, I'm glad I'm not alone. Is it possible it's a network thing with Tmobile? I'm not saavy enough to say it's possible or not, but maybe the other members can tell or help troubleshoot. It can't be coincidence we both have the exact same problem.

Same problem with a Pixel 1 and Verizon
Having the same problem. When I get a call I get a drop down with the caller and answer or decline button. Neither one works and I have to just let it ring out. I get a missed call notification but no voicemail notification. I have deleted truecaller app and rebooted but no change.

Switchkey said:
Having the same problem. When I get a call I get a drop down with the caller and answer or decline button. Neither one works and I have to just let it ring out. I get a missed call notification but no voicemail notification. I have deleted truecaller app and rebooted but no change.
Click to expand...
Click to collapse
I've found that if it's ringing, you can press the power button and it will take you to the "swipe up to answer" blue screen. That works for me.
Doesn't solve the problem any of us are having, but at least you can answer calls when they come in.
@Switchkey are you on Tmobile too?

nichos said:
I've found that if it's ringing, you can press the power button and it will take you to the "swipe up to answer" blue screen. That works for me.
Doesn't solve the problem any of us are having, but at least you can answer calls when they come in.
@Switchkey are you on Tmobile too?
Click to expand...
Click to collapse
Verizon

I have a Pixel XL 1st edition and I just started having this problem yesterday. The drop down menu won't work to answer calls and if I try to call back it won't go through until a minute after I try to connect the call. I'm on the Verizon network so I doubt it is a carrier issue. My best guess is that it has something to do with the most recent update. I really hope this gets resolved. It's the first real issue I've had with this phone.

The latest trick
Tried calling my wife from the car while driving using Google Assistant. Three times it said it understood I wanted to call my wife's mobile but it did nothing. 20 minutes later while I am driving I hear "Hello?" 20 minute delay on voice dialing a number. Luckily she said hello. If it had been someone else they might have just listened to me go about my day. This all started in the last few days. Prior to that the Pixel 1 phone has been great.

Same problem here. TMobile pixel 1. A reboot fixes temporarily. Started in the past week.

Update:
So from the beginning, I have NOT been able to replicate this problem in safe mode. I can make/answer calls with no issues whatsoever. So on Sunday night I spent some time uninstalling almost all of my apps and the issue seemed to go away. I went back in and reinstalled them and my phone was fine up until this morning. So because it was working for a couple days and works in safe mode. Is it possible that it is some sort of app conflict? I don't want to spend countless hours on this, but I really don't want to buy a new phone. Google will NOT exchange for me and I still owe $200 for this damn phone as I did the installment plan! This is very frustrating. Can anyone having this issue consistently try it in safe mode and report back to see if they can replicate it? In the mean time, I'm just going to run my phone in safe mode so I can answer calls at work.

Hey guys, my dad has been having the same issue on his Pixel. I quickly scrolled through the most recent posts on /r/GooglePixel and found this post. The comment mentioning disabling the phone permission for all other apps other than your default phone app seems to be working for my dad. So, I guess that's a workaround until Google fixes it (better than staying in Safe Mode, at least).

ApertureAndroid said:
Hey guys, my dad has been having the same issue on his Pixel. I quickly scrolled through the most recent posts on /r/GooglePixel and found this post. The comment mentioning disabling the phone permission for all other apps other than your default phone app seems to be working for my dad. So, I guess that's a workaround until Google fixes it (better than staying in Safe Mode, at least).
Click to expand...
Click to collapse
Interesting find! That might explain why after uninstalling a bunch of apps it started working again, for a while. Perhaps one of the apps is causing some conflict? I've just done a clean install again after uninstalling a bunch of apps I don't use anymore. If it comes back, I'll check the permissions and report back!

Keep re-receiving old texts, how do I make this stop?

Basically what happens is I get old texts from previous conversations as if they were new. They will come in randomly but tend to follow the sequence of the conversation, so it basically replays the conversation but slowly over the day. Seems to affect group chats more. It makes following conversations very hard since they are full of old texts that are not relevant but they show up as new. Also annoying to keep getting notifications when I'm actually waiting for a text only to see that it's an old text that I got days ago.
Current phone is Google Pixel 4A with CalyxOS, but I've also tried Graphene OS and had the same issue. I've tried the stock app as well as QKSMS. I did not get the issue with Signal (using as SMS client) but they dropped support for SMS, so this started back again as soon as I switched off Signal. I even tried putting the sim card in my old phone (stock android) and it's still doing it! This part is strange to me because when this problem first surfaced, doing this did fix the problem.
How do I make this stop or begin troubleshooting this? Nobody in my contacts is having this issue so trying to convince them to switch to another messaging system is kind of futile, this is my problem. I am starting to wonder if I should just get an iphone like everyone else because it just works, but I really hate the closed nature of apple ecosystem.

I was thinking of looking into how to do app development and modify an existing open source client so that it ignores texts that have a send date older than 24h, but before I do that, is there already a text client for Android available in the F droid store or as an APK that would have such a feature?

So this is not just group chats like I thought. Starting to get old texts I got from single conversations now. Even pictures get resent. These show up as new texts, though they still have the original send date. This will at least make it easier to filter these out.

Anyone have an ideas how to make this stop? Driving me insane. I really don't want to have to write my own app.

Anyone? This problem is driving me insane. It started happening with a vengeonce again. I am being bombarded by old texts that I already got days ago. It's just playing out the entire conversation over the course of a few days. Have to put the phone in airplane mode to make it stop otherwise the phone is just lit up non stop with old texts coming in.
At very least is there some kind of logging of sorts I can enable that would help me better troubleshoot this?

Inreally dont know but i Remember this happened to me sometime ,maybe Just try a factory reset or change rom , i dont know

I tried several roms, resets etc. While it was happening I even put the sim card in another phone and it started doing it on that phone too. It's also not a carrier issue since I'm the only person having this issue. I've also tried all sorts of text apps. The only one it didn't do it with was Signal but they dropped SMS support, which really sucks.