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)
So first things first, I was running Synergy r73 fine for a few days, beautifully even.
Then today out of the blue without changing anything, my phone had some brief freezing issues and then I could no longer send texts or outgoing calls. I am still receiving texts, and my data connections work perfectly, but when I try to send a message I just get a "failed" notification a few seconds later. When trying to call out I just get nothing and then the call ends after 20 seconds or so.
I tried a battery pull, sim reseating, data/cache reset, and I even used ODIN to go back to the stock VRALHD rom. Still having the same problem.
I can't call Verizon support until tomorrow and all the retail stores in the county close on Sundays, so I figured posting here in the meantime couldn't hurt.
I had the same exact issue and had to go all the way back to VRALF2, following the stickied guide, and once I did that I had to dial the reprovision code. I can't remember the code off of the top of my head but it is posted all over the place. I would try that first and if it doesn't work then go all the way back stock. Also get the Phone Info app, open it and go into Device information and on the little drop down box make sure LTE/CDMA/EvDO is selected. Do those two things and see if that doesn't solve the problem, and if not then you may have to go all the way back to the first stock ROM like I did, hopefully you won't though!
Sent by one of my many Anthromorphic Personifications
I checked the radio mode with the phone info app and it's what it should be. I guess I'll be doing another odin flash. Hope it works
EDIT: Going back to the older stock flash didn't work either, even after doing the reprovision code :-/
I guess I'll be making a trip to the store tomorrow
New phone is in and working perfectly. I do miss some of the aspects of the Synergy mod, but now I'm hesitant to re-rom it. Is it even remotely possible that rooting and installing a rom can cause this issue to happen several days after installing?
In phone info make sure it is set to LTE/CDMA/EVDO
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!
Hello, I'm a normal (not expert on rooting etc) android phone user and even after googling i couldn't solve or answer my question/issue. The past phone I had was an xperia z3 compact. This phone was able to send mms automatically (even with data off i could see the lte working for a few seconds and then the mms was sent it stopped). Now with my latest phone Lg Q6 i need to put the data on (and off) each time i want to send or recieve and mms. I checked on the Android messages app and my lg q6 has acces to my network. So i believe it should be able to also send mms automatically but it doesnt. So what is it? As i said i did some googling and i found nothing. Some people said it was the apn, and i checked, is the same info that i had before. I don't want to download any 3rd apps either. I know that i could just leave the data on but i don't want to risk it as i have a small data plan.
I contacted lg, google and Fido. Fido and google said that Lg is the one that should be able to help me with this (even if the app is from google) so i call Lg and they suggested a reboot, and factory reset. Still the same.
I have the idea is like some coding (ors something like that) on the app that doesn't allow it. After reading some forums i saw that HTC and some samsung phones also send mms automatically.
Any ideas on what else can i do?
Thanks!
Have you tries all the tips on this website: http://www.talkandroid.com/guides/beginner/how-to-automatically-receive-mms-picture-messages/
If you have and it's still not working, then I think it may be a factory problem.
mawalaka said:
Have you tries all the tips on this website: http://www.talkandroid.com/guides/beginner/how-to-automatically-receive-mms-picture-messages/
If you have and it's still not working, then I think it may be a factory problem.
Click to expand...
Click to collapse
I'll check it out and post the update after. Thanks!
Update: I tried what it said on that link and also some things from the comments and still the same. I'm looking now for more info in this forum so i'll see if there's something new to try.