Question Dialer problem with Pixel Experience - Redmi Note 10

Hi
I have flashed Pixel Experience on the RN10 and it works almost flawlessly except for an big issue that didn't happened with MIUI
Whenever someone calls me, even if it's on contacts, the dialer (Google Dialer) shows this
<phone number of caller><my phone number>
In the notification, calling screen it appears as
<phone number of caller>&<my phone number>
This makes it to not display the contact name.
The dialer works fine otherwise, I can call or receive calls and evreything
Again this didn't happened before so I rule out carrier or SIM.
I tried flashing again update (March update) and updating the dialer, clearing dialer data, but the issue remains. I tried searching on the web but I can't find anything similar.
Thanks for any help.

Meh I installed the Unofficial LineageOS build from here and everything seem to be fine, waiting to evaluate battery life and some apps, but at least the DIALER (either the AOSP or Google's) show the caller ID fine
The major issue is that I cannot restore from old Pixel backup

Related

[Q] "No number available" when calling from vehicle bluetooth

I have a 2012 Volkswagen GTI with the RNS-315 nav system. I noticed the other day when trying to call my wife via the nav that somehow the directory the phone sends doesn't have her number - only her name. I tried via both voice commands, and from the navigation display. I tried unpairing/repairing the phone, power cycling the phone, editing the contacts, etc...I have a vague feeling it might have something to do with having the contacts linked (Google to Facebook and Skype, etc) but I don't know for sure. I know it isn't the nav system because it's worked before, and I can dial her number manually via voice or from the nav screen. Bluetooth works fine otherwise; I can place a call from either the phone or the car.
I haven't tried clearing out my contacts yet; I want to avoid that. I also haven't tried (but will) calling a non-linked contact vs linked.
I'm running CleanROM 4.5, stock kernel, nothing special.
Anyone else had issues with their phones sending names without numbers in contact lists?

[Q] SMS Error Code 98

EDIT: 11:15pm 9/25/2012 - ISSUE RESOLVED, SEE BOTTOM OF POST FOR SOLUTION
Okay, relevant information first:
Evo 4G LTE on Sprint
HBOOT 1.15 S-ON HTC DevUnlock
Current ROM CM10 Nightlies
Sprint-Google Voice integrated number
Now for the issue:
Texts can not be sent through the messaging app. When attempting to send a text, it will say "sending..." for a few seconds, then I get a notification saying "message not sent". Clicking on this notification takes me to the messaging app where the failed message has a red triangle next to it. When I long press the failed message, it comes up with a menu, and when I click "view details" it says "Error Code 98".
This happens both when connected to WiFi and when not connected to WiFi. It also happens both in my home town, and another town 45 minutes away (meaning the issue doesn't seem to be with the particular tower).
The last successful text sent or received was on Sept 13th.
Calls still operate as normal.
No changes were made by me between when my SMS was working properly, and when it stopped working. (Same ROM, Recovery, Kernel, etc). I haven't downloaded any SMS apps (handscent, gosms, etc) that could be interfering with the messaging app. I DO have the Google Voice app, but I had that when SMS was working properly as well, and the GV app hasn't been updated since March (meaning it shouldn't have changed how it was behaving).
Other peculiar behavior:
In addition to not being able to send texts via the messaging app, it seems that my number is also unable to receive texts. When texts are sent to my number, my phone does not receive them and they also do not show up in my Google Voice inbox. The sender is given no notice that the text has not been received. I am able to send texts from the Google Voice app, and others successfully receive them. When I send a text to myself from the Google Voice app, I receive it in my Google Voice app, but not in the stock messaging app (even though my Google Voice app settings say that texts will be received via the messaging app).
Things I've Tried (Updated: 3pm EST, 9/25/2012 ):
* Turning it off and on again
* Updating CM10
* Changing Google Voice settings (though it's possible I overlooked a setting)
* Factory Reset, Reflash ROM
* Flash Sense ROM, Update Profile/PRL
* Flash different AOSP ROM (Paranoid Android)
Things I've Not Tried (in order of how willing I am to do the things):
* Using an alternate SMS app (GoSMS, Handscent, etc)
* Un-integrating (and Re-integrating) Google Voice
* Giving the EvoLTE a relaxing bubble bath, to calm it down
* Flash Stock, Unroot, Update Radio
So, does anyone know what might cause this problem, and/or how to resolve it?
EDIT: Solution below
STORY:
I called Sprint Support, and had them reactivate my old phone (Evo4G running a CM9 alpha), by giving them the MEID for that phone. At this point I powered the phone back on, and called an activation number that they had given me (888-546-0314). On a Sense ROM, I would have simply updated my profile, instead of calling the number. We then tried SMS on the reactivated phone, and it worked (also, texts began showing up in Google Voice again at this time). I turned off my Evo 4G LTE, then I gave him the MEID for it and had him switch my number back to that phone. After he said he had switched it, I powered the Evo 4G LTE back up, and updated the profile, which I was able to do since I was still on Viper4G (note: I had to update the profile via WiFi, it might have worked over data, but it was taking longer than expected so we cancelled and just use WiFi for the update). Once the profile had updated, I called the test number again to confirm that the phone was activated. When I tried SMS, it worked as it should, including sending a copy to Google Voice.
TL;DR:
1. Find an old phone
2. Write down the MEID of both phones
3. Find a third phone to use to call Sprint (since you'll be activating/deactivating the other phones throughout the call)
4. Call Sprint Customer Support (888-211-4727), and punch the appropriate numbers until you are talking to someone
5. Have them switch your number to the old phone's MEID. Make sure the old phone is activated.
6. Have them switch your number back to the new phone's MEID. Make sure the new phone is activated.
7. Texting should be working on your new phone again.
Notes: The old phone may not be necessary. It may be enough for the Sprint Service Rep to deactivate your phone and then reactivate it. But I figured I would write out the EXACT method that solved the problem for me, since I am positive that this method has worked at least once. I have neither the means nor the desire to recreate the problem, so I will have to leave testing of other methods to the next person that experiences this problem.
Update: Clean flash of Paranoid Android did NOT resolve the issue. Still getting "Error Code 98".
So, this tells me/us this is not an issue with CM10 (which is not surprising, since I have no idea how what ROM I have flashed would keep Google Voice from receiving the texts as well).
This may sound odd but try moving the time up an hour or back an hour, error 98 is a problem with home agent, it's a sprint network error. I don't know of anything else that's helped
Try calling sprint and ask them if they can do anything. When I went s-off I had to call them bc my calls and text had errors. Data worked though.
They pushed something that fixed it in less than 10 seconds. Just wanted me to verify my account.
I tried changing the time 1 hour forward, and 1 hour backward, neither of those resolved the issue.
On hold with the Sprint tech department (it's taking longer than 10 seconds, but hopefully they figure out how to fix it.)
EDIT:
Mini-Update: Flashed Viper4G (a sense ROM), problem persists.
Updated profile and PRL while in Viper4G, problem persists.
Was told by Sprint technical support to press ##6-digit-MSL-here# and edit something, then reboot. Did that. Problem persists.
SOLUTION
The problem has been resolved, and the OP has been edited to include the method used to solve the problem.
If this was a game, Anthonicia would win for being closest (though it took closer to 2 hours on the phone with Sprint to fix the issue, if we include all four calls I made, 20-30 minutes if we only include that final one).

CM11 Dialer: Dialer/Browser automatically add "+1" prefix which blocks outgoing calls

CM11 Dialer: Dialer/Browser automatically add "+1" prefix which blocks outgoing calls
Great experiences so far with CM11. Persistent issue with native dialer (as well as Google Dialer) and unnecessary plus-code dialing for domestic calls.
However, I've noticed a persistent bug: the dialer will not complete any call that begins with a plus code extension (for example, “+1 555 6946). The dialer produces a busy signal instead of completing the call. However, if I edit it before calling to remove the “+1” prefix, the call completes normally. This problem occurs even though I am only making domestic calls within the US, and occurs in every tested version of Cyanogenmod (although it is absent in the rooted stock rom).
I can replicate the problem for any number that I look up on a web browser through Google. For example, if I look up “Chipotle New York” and hit “call” it automatically sends the dialer a number with a “+1” extension. Again, this results in a busy signal unless I edit the number to remove the “+1” prefix. This means that I cannot simply edit all of my contacts to remove the prefix since the problem will occur anytime I send a contact to my dialer through a browser.
Thanks in advance for any insights.
Device Information:
- CyanogenMod 11-20141112-SNAPSHOT-M12-jewel
- Android version 4.4.4
- Baseband version 1.13.11.1105
- Sprint (USA)
- on HTC Jewel (Evo 4g LTE)
Saw you hadn't gotten an answer to this in threads across a few sites, so hopefully this finds you. I've not found a proper fix for this bug either, but have been able to work around it by using an app called Prefixer from the store https://play.google.com/store/apps/details?id=com.tftbelow.prefixer&hl=en. A single outgoing rule is free. Just create one to remove all instances of +. The + will be put into the dialer still from google or calling back a number that came in with it, but when you hit send, the app intercepts the number, removes the + and the call connects.
Its a hack, but it works for now. Happy dialing!

Probably IMEI problem with Nougat

(sorry for My English)
I have two Vernee Apollo Lite with a custom rom MM based and works fine.
After i've installed Nougat i have this problems, i think it's IMEI problems, but i'm not sure:
- I have an "X" on SIM signal, look this screen: https://ibb.co/hKdvfk
- I can't read contact saved on My SIM card
- in lock screen i see "22210" (code of Vodafone Italia) instead "Vodafone IT"
- if i don't active the data connection or WiFi the date and hour do not set correctly.
I can call and surf on web with data connection without problems.
I can read My imei with *#06* in dialer.
This problem disappear when i return to MM.
Addendum:
I can't access at engeneering mode with code in dialer or app.
Thanks a lot to all.
It's normal on pure android that the signal has an "X" there if mobile data is deactivated. You can write SMS'ses with it and so on. It's no problem.
Thanks a lot, but why i can't real 'Vodafone it' on lock screen and i can't read the contact on SIM?
Up.
Contact's import and "Vodafone it" in lock screen works in AOSP 7.1.1 rom. How can i export this on Resurrection Remix or Lineage?

No incoming calls after CM 12.1 custom ROM on Galaxy Avant (G386W)

If I revert back to CM 11 (4.4.4) incoming calls work again, no issues. But if I install the CM 12.1 (5.1.1) rom, I no longer receive incoming calls. I can make outgoing calls just fine, and can receive texts fine. Also, another weird thing is that if I call my cell from my home phone (voIP), or my mom calls my cell from her cell, my cell doesn't ring. But if I call my cell from the Google Hangouts dialer (to my cell number) on either the same cell phone or a different cell phone, or dialing out using Google Voice service from my home phone, it rings my phone just fine. So it's like the only thing it will accept is Google Voice. NOTHING else.
I managed to fix the security settings crash (keymaster files), and am reading various bugfix suggestions on how to fix the camera, but I can't find any bugfix list suggestions for fixing the network. Any ideas on where to start?
Oops... wrong thread...

Categories

Resources