Hi.
Today I ported all my things from P5 to P7Pro and I noticed a very annoying thing.
In every call, after a minute or two there beggins cracking/squealing, like it's a bad connection.
I updated the phone to the latest Android version (screen in att). I tried restarting, with another SIM but the same ...
No problem at all on my P5.
Anyone else facing that?
I'm really disappointed that this disables the basic use of the phone and I don't even know how to start reporting a bug considering I'm using the phone in an unsupported country. :/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks for your help.
Strange one, not something I have nor read anyone else having. I'd suggest you have a faulty handset if you have tried another sim from another sim in it (presumably from another provider).
Beefheart said:
Strange one, not something I have nor read anyone else having. I'd suggest you have a faulty handset if you have tried another sim from another sim in it (presumably from another provider).
Click to expand...
Click to collapse
Yes, another SIM from another provider.
Yes, strange one. I did not found anything similar anywhere ...
akulp said:
Yes, another SIM from another provider.
Yes, strange one. I did not found anything similar anywhere ...
Click to expand...
Click to collapse
Do you have clear calling enabled? Not sure if it would make a difference, but I did see one or two people report that their connection was worse with it, although for most I think it's better. Not sure they reported crackling/squealing though.
Lughnasadh said:
Do you have clear calling enabled? Not sure if it would make a difference, but I did see one or two people report that their connection was worse with it, although for most I think it's better. Not sure they reported crackling/squealing though.
Click to expand...
Click to collapse
I read about CC, but in my version there is no such option for now. Waiting for upgrade ...
Hello I have the same issue with Italian PosteMobile.
Where are you from?
It starts after 5 or 6 minutes in call.
Same phone but with other operator I have no problems.
Is your operator a virtual one? Full MNVO?
giobik said:
Hello I have the same issue with Italian PosteMobile.
Where are you from?
It starts after 5 or 6 minutes in call.
Same phone but with other operator I have no problems.
Is your operator a virtual one? Full MNVO?
Click to expand...
Click to collapse
Hi!
Not so great for you and me, but great that I'm not the only one.
I'm from Slovenia.
Hm, strange, so something with operators u think? I'm on Telekom Slovenia, so biggest national operator ...
Idk but I know someone that works for my operator and they will try to understand what's the problem, in theory...
I'm also thinking opting in Beta Android to check if a newer rom fixes the issue.
If I have news I'll post here!
giobik said:
Idk but I know someone that works for my operator and they will try to understand what's the problem, in theory...
I'm also thinking opting in Beta Android to check if a newer rom fixes the issue.
If I have news I'll post here!
Click to expand...
Click to collapse
Great, thank you!
giobik said:
Idk but I know someone that works for my operator and they will try to understand what's the problem, in theory...
I'm also thinking opting in Beta Android to check if a newer rom fixes the issue.
If I have news I'll post here!
Click to expand...
Click to collapse
Hm, today I had zero issues up to now.
Yesterday in the evening I took out my primary SIM card, cleaned SIM slot with air pressure ...
I keep fingers crossed!
Same issue here but I only get it after exactly 20 minutes of calling. I'm using kpn Netherlands with a esim . I migrated from pixel 5 also with esim on same provider. I must note that after I disabled 2g calling from the settings that not all calls have the issue anymore.
Same problem here in Portugal after 15m in a call.
I must say that now after testing a couple of days with the 2g slider turned off, 90+% of the calls go without big audio issues. Only sometimes 1-5 seconds long distortion of some kind is left
Hello, problem still present after many updates and now on last beta.
Probably most of you solved it by switching to another operator, but I can't.
I opened an issue in Android Bug Report and discovered through logcat that there are some duplicate received frames.
If you suffer from the same issue I kindly ask you to post in this official issue link to let Android developers know that I'm not the only one with this problem!
Google Issue Tracker
issuetracker.google.com
Take a look to my answer number 6 to see the logcat :
On a Windows PowerShell:
adb logcat | find "F1:ERR"
Google Issue Tracker
issuetracker.google.com
If the problem remains unsolved I will sell my Pixel 7Pro, I can't work with this issue (and cannot change operator as it is the professional on that gave me my employer).
Thank you!
Same problem here
Hello, as of today nothing changed, just updated on beta 13 (T2B2.221216.008)
Annoying...
Same problem here!
After about 8 minutes of calling with Postemobile operator (Italy), the call starts croaking! More and more often I receive text messages from people who have looked for me, despite the fact that the phone was always under excellent signal. Postemobile still has VoLTE not enabled on Pixel7.
sbellisario said:
Same problem here!
After about 8 minutes of calling with Postemobile operator (Italy), the call starts croaking! More and more often I receive text messages from people who have looked for me, despite the fact that the phone was always under excellent signal. Postemobile still has VoLTE not enabled on Pixel7.
Click to expand...
Click to collapse
Please, write a comment in this Bug Issue Tracker to let know Google we have this horrible problem.
Also click the +1 on top to increment the counter!
Google Issue Tracker
issuetracker.google.com
giobik said:
Please, write a comment in this Bug Issue Tracker to let know Google we have this horrible problem.
Also click the +1 on top to increment the counter!
Google Issue Tracker
issuetracker.google.com
Click to expand...
Click to collapse
done
Related
Does anybody else have a problem with their caller ID? I am on t-mobile in the US and sometimes the phone number shows up, sometimes it says unknown. This happens randomly even the same person. One time, their caller id would show up, the other time it'd say unknown.
I'm on Tmobile USA as well and don't have any of these problems.
Maybe try clearing the contacts and sync them again?
Sent from my HTC VLE_U using XDA
I never had caller ID... Though I remember it was one of the "bonus apps" the icon of which was shaped like a gift box.
Given my repulsion to bloatware, I deleted it. Finally, frustrated with the whole lack of caller ID, I finally dropped $6.99 on White Pages Pro (or something like that). Now my caller ID is great and it adds the info if I want to make a new contact. Very nice.
Sent from my HTC One-S (rooted), stock ROM
Got a new one at costco...Same problem..wtf. Can it be the sim card or something? Any ideas?
So this is what I mean about the unknown caller ID problem. Unknown callers with a phone number is not the problem. The problem is unknown callers calling me with no phone number. And these numbers are not blocked. I asked my friend to help me test it for me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This happens on and off WIFI calling and this is my second One S with the same problem. Kinda annoying because I don't know who to call back if I get a missed call.
I've been having the same problem. I took it back to the t-mobile store and they gave me a new one but after a few days the problem came back. I'm not sure if it's the phone or the sim card.
jmnz said:
I've been having the same problem. I took it back to the t-mobile store and they gave me a new one but after a few days the problem came back. I'm not sure if it's the phone or the sim card.
Click to expand...
Click to collapse
Yes! Thank you! I thought I was alone here. Where are you from? Do you by any chance use an app called screen filter?
Xdpker06 said:
Yes! Thank you! I thought I was alone here. Where are you from? Do you by any chance use an app called screen filter?
Click to expand...
Click to collapse
Yeah I thought I was the only one having this problem. I'm from around the LA area and no I don't have that app.
I also have the same problem. I am in Foxboro, MA. I called Tmobile and they are telling me it's a network issue. Supposed to be resolved in 72 hours. I'll post back with my results.
I seem to be running into the similar issue. I once resolved it by installing the Rooted nandroid available here, it had gone away so I re installed a custom rom but then after a couple weeks it came back? I read thru the forums that's it may have to do with facebook contacts? I'm trying out the new energy rom now, hopefully it clears the problem
mbotelho said:
I also have the same problem. I am in Foxboro, MA. I called Tmobile and they are telling me it's a network issue. Supposed to be resolved in 72 hours. I'll post back with my results.
Click to expand...
Click to collapse
Sweet. I factory reset my one s last night and haven't had this problem today. Don't know whether to attribute it to the reset or t mobile fixing their network. Either way everything's good so far.
Xdpker06 said:
Sweet. I factory reset my one s last night and haven't had this problem today. Don't know whether to attribute it to the reset or t mobile fixing their network. Either way everything's good so far.
Click to expand...
Click to collapse
I tried factory resetting my phone about a week ago but after a few days the problem came back. I'm hoping T-Mobile resolves this problem soon.
Try Factory Reset and also try clearing Cache/Data in the Phone Application Settings if applicable. Obviously, reboot afterwards.
I'm going to assume you are not rooted.
I did a factory reset as well, but still had the problem. I'll try to clear my Phone data/cache first and also try another factory reset today.
I spent an hour on the phone with Tmobile advanced tech support. They think it's a network issue, but haven't figured out exactly what it is yet.
Another thing, when I have Wifi calling on, my caller id works just fine. Really weird.
I did another factory reset today, didn't update any of the apps, basically didn't touch anything and caller id is still not working.
I am also on the latest OTA update. I wonder if that has anything to do with it?
I love this phone, just wish I could tell who is calling me.
So I've discovered a little more from testing this morning. Would be interested to hear if anyone else sees the same thing.
Reboot the phone with Wifi off -> Caller ID works -> Turn on Wifi and Wifi calling ->
Caller ID broken.
Reboot the phone with Wifi off -> Caller ID works -> Turn on Wifi with no Wifi calling -> Caller ID still works.
Looks like the issue might be related to Wifi calling somehow. I'll update Tmobile tech support and hopefully they have some kind of answer.
Ok so after hours of reseting the phone, the settings, wipping everything, re installing the Rom all this over and over, doing nandroid etc... I finally got it to show me the caller ID again.
It was weird because for a while I could get it to show it to me after a new install but then as soon as I'd reboot, It go back to the same thing.
Still confused as far as what is making it hide the caller info. I doubt it's Tmobile network because then I would imagine at least some other phones would have similar issues. then again I don't know because when it started again for me yesterday I was just driving on the road, no settings had been changed (although I had just left my house wifi)
its very confusing
well i am having the same issue. and i have Samsung Galaxy S2. my caller id shows as UNKNOWN
Xdpker06 said:
Yes! Thank you! I thought I was alone here. Where are you from? Do you by any chance use an app called screen filter?
Click to expand...
Click to collapse
Just want to share that I'm having the same issue on my One S. Seems random but have not done any testing to try to figure out a pattern. I'm in southern NH if that makes a difference.
Sent from my cm_tenderloin using xda premium
HeydavidV said:
Just want to share that I'm having the same issue on my One S. Seems random but have not done any testing to try to figure out a pattern. I'm in southern NH if that makes a difference.
Sent from my cm_tenderloin using xda premium
Click to expand...
Click to collapse
Thanks for sharing. I'm in the bay area in CA. I don't want to jinx it, but I haven't had this problem occur in 48 hours. But I have noticed that it occurs more when new numbers call you for the first time so I don't really know because I haven't had anybody new call me.
Since its now officially rolling out, I was wondering what other bugs people have spotted in B361 (and if known, any ways to fix/get around them).
For me so far I've notice
Android Pay -- Android Pay no longer works as its supposed to. It no longer works from any screen, and only works when the app is open. It also takes a very long time to respond even when it is open (I'm actually not certain that it's not working from the lock screen, but if it is, it takes far too long to respond)
Device security -- If you use a Google Apps account that requires device encryption, and that a password be required on restart, the system seems to report that these criteria are not met, even when they are. Device Policy will bombard you with notifications that they are not met, and prevent the account from syncing.
The first one is just extremely irritating, but really not that big a deal. Although I don't have huge issues not being able to sync the Google Apps account in question, I feel the second issue should be classed as critical, and should've been fixed before final release, because for some users this will be a dealbreaker.
Android Pay working fine for me.
oxfordmark said:
Android Pay working fine for me.
Click to expand...
Click to collapse
Well that's weird (but possibly good news). What cust version are you on? Did you get it on final release or from early update program? I even did a full wipe and the problem persists.
Android Pay is working fine for me aswell, C432 here, Updated from L09C432B182 to L09C432B361
esist said:
Well that's weird (but possibly good news). What cust version are you on? Did you get it on final release or from early update program? I even did a full wipe and the problem persists.
Click to expand...
Click to collapse
Hey
I'm C432 and went from B182 to the latest version on Saturday. I want part of the beta
Working great here too
166>>182>>>361
Used Huawei updater
Sent from my EVA-L09 using Tapatalk
Not sure if this is a bug or not but can any of you guys change the notification icon colours? For instance textra and whatsapp allow you to select the colour but it stays as white. Previous android versions worked fine.
i contacted huawei live support and they told me that if problems appear you should do a factory reset because of data migration issues, this helped me for example with lockscreen notifications
on 361 since last week and haven't found issues with Android Paid. I only unlock with fingerprint and place the phone over the nfc terminal.
theogkillzone said:
Android Pay is working fine for me aswell, C432 here, Updated from L09C432B182 to L09C432B361
Click to expand...
Click to collapse
That's really strange (that I'm having issues). It does seem to be entirely related to B361 cause it disappeared when I did a rollback to B182.... Have to tinker with it some more and find the cause.
OldDroid said:
i contacted huawei live support and they told me that if problems appear you should do a factory reset because of data migration issues, this helped me for example with lockscreen notifications
Click to expand...
Click to collapse
I did that. After I first experience issues, I rolled back, upgraded again, then did a factory reset.
dbesoli said:
on 361 since last week and haven't found issues with Android Paid. I only unlock with fingerprint and place the phone over the nfc terminal.
Click to expand...
Click to collapse
Is this what others have been doing?
This worked for me today. I remember it not working before but I'm really not certain.
But before I could pay for small transactions without unlocking at all, which definitely doesn't work since the update.
Maybe it's related to magazine unlock. I had it disabled before update but this doesn't seem to be possible anymore.
I find my whatsapp notifications are slow to come through , if they come through at all, anybody else have the same issue?
jpbroad1970 said:
I find my whatsapp notifications are slow to come through , if they come through at all, anybody else have the same issue?
Click to expand...
Click to collapse
Is it closing WhatsApp when the screen turns off? I did notice once that WhatsApp was open with WiFi on and messages weren't even going out until I went into Contacts and hit refresh (what I always do to force WhatsApp to retry to connect to the internet). But it was just a once off.
it seems to close , I will keep my eye on it. it only appears to be on the 1st one or two messages.......perhaps its just me lol
jpbroad1970 said:
it seems to close , I will keep my eye on it. it only appears to be on the 1st one or two messages.......perhaps its just me lol
Click to expand...
Click to collapse
Try disabling it closing it when the screen turns off.
Out of curiosity, do we know if there is any difference between the B361 that was released as early adopter, and the B361 that was released as final? There were two "full" packages, with different dates on them, both marked B361. As early adopter update, I got one with a kernel build date of 30 December.
Does anyone who got it as the "final" update know if theirs is actually the same? I know a different build date doesn't necessarily mean it had any changes beyond that, but just to know.
esist said:
Try disabling it closing it when the screen turns off.
Out of curiosity, do we know if there is any difference between the B361 that was released as early adopter, and the B361 that was released as final? There were two "full" packages, with different dates on them, both marked B361. As early adopter update, I got one with a kernel build date of 30 December.
Does anyone who got it as the "final" update know if theirs is actually the same? I know a different build date doesn't necessarily mean it had any changes beyond that, but just to know.
Click to expand...
Click to collapse
my build is 30th December, I was thinking about going back and then reloading the later firmware in case its any different
There are no NFC settings
Are you sure? You flashed rom for l19
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wysłane z mojego EVA-L09 przy użyciu Tapatalka
Debug USB keeps switching off whenever I go outside developer options..
esist said:
Is this what others have been doing?
This worked for me today. I remember it not working before but I'm really not certain.
But before I could pay for small transactions without unlocking at all, which definitely doesn't work since the update.
Maybe it's related to magazine unlock. I had it disabled before update but this doesn't seem to be possible anymore.
Click to expand...
Click to collapse
Yeah, before this update I just had to turn the phone on for Android Pay to work, now I have to unlock it (with my fingerprint). I guess it's enhanced security to stop people pocket swiping your money
DEPRECATED, PLEASE DOWNLOAD FORM OFFICIAL PIXEL EXPERIENCE WEBSITE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PixelExperience for Moto G6 Plus
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 10.0
Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
Fingerprint reader
NFC
Lights
Sound / vibration
Known issues
You tell me!
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download from Android File Host Folder
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog
Our device Telegram group
Our device Telegram channel
Android OS version: 10.0.0_r40
Security patch level: July 2020
Build author/Device Maintainer: @juampapo546
Special thanks to: @Jleeblanch
Device Source code: https://github.com/juampapo546
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
Changelog 16/07
Fixed bluetooth and wired headsets calls
Update kernel and some device stuff
5th July security patch
Thanks!!!
It's a very good and stable Rom
After two days of using I found no issue and the battery was at the second cycle 7 hours of screen on time and everything worksfine
You can use it as daily driver
hey there, just curious if this has the same issue with bluetooth headphone calling as some other roms for this phone?
Reece's Puffs said:
hey there, just curious if this has the same issue with bluetooth headphone calling as some other roms for this phone?
Click to expand...
Click to collapse
For the moment yes, we all use same dt so bugs are shared, we are working on it
juampapo546 said:
For the moment yes, we all use same dt so bugs are shared, we are working on it
Click to expand...
Click to collapse
dt?
but thank you for letting me know, thats very helpful
Reece's Puffs said:
dt?
but thank you for letting me know, thats very helpful
Click to expand...
Click to collapse
Device tree, it would be like the specific device Configuration, that's the difference between an evert and an ali rom (Plus vendor and kenel)
Am using this rom from a month ago, and honestly everything is so perfect. And I couldn't find any bugs in daily routine usage.
Untill I travelled from one city to other and when signals started gain/drop scene, my phone automatically was restarting after every few minutes.
And another thing it makes my game crash while playing ?
Okay am reediting to add another bug.
Whatsapp calls are perfectly working on speaker and wired handsfree. But cellular calls are only working on phone speaker but not on wired handsfree. And in case my handsfree is plugged in and I got a call, no audio will progress on both sides even if I unplug handsfree at that time.
Sometime "Settings" gets crash too.
haris.sdq said:
Am using this rom from a month ago, and honestly everything is so perfect. And I couldn't find any bugs in daily routine usage.
Untill I travelled from one city to other and when signals started gain/drop scene, my phone automatically was restarting after every few minutes.
And another thing it makes my game crash while playing
Okay am reediting to add another bug.
Whatsapp calls are perfectly working on speaker and wired handsfree. But cellular calls are only working on phone speaker but not on wired handsfree. And in case my handsfree is plugged in and I got a call, no audio will progress on both sides even if I unplug handsfree at that time.
Sometime "Settings" gets crash too.
Click to expand...
Click to collapse
I'm aware of the incoming call on headset/bt bug. However i never experienced the signal drop of this rom, maybe check on the guide i've made for a similar issue (It's on the Moto g6 plus guides section)
If you discover any other bug please share me a log
Thank you for responding.
Actually its not a signal problem with this ROM, but where i live in Pakistan so on highways we experience signal drops from cellular towers.
And problem with this ROM is when signals get up and down phone gets restart repeatedly.
Or in simple words when signals are auto switching between 2G, 3G and 4G it gets restart.
And also please guide me how to share logs ?
Microphone is working?
Jonathas S said:
Microphone is working?
Click to expand...
Click to collapse
Yes its working after you switch off Voice Match "Hey Google" in your Assistant setting.
A noob question! Since you don't have VoLTE line it may never be incuded in the ROM. Correct? That being the case, is it possible for you to take the module from other moto devices or say if i could send you my phone's image, could you add the module to rom? It would be really helpful. Eversince I uncloed my device, every update makes me reset the phone and gets stuck on bootloop. It's very time consuming and beats the hell out of me
Hi, sorry for cross posting. Just installed LineageOS and noticed the problem about the Bluetooth calling issue. Thought I'd install this one, but read that it has the same problems. Does anyone here have an update on that? Anything I can do to help?
CAST to SmartTV
Hello, very nice job! CAST work? Mirroring?
haris.sdq said:
Thank you for responding.
Actually its not a signal problem with this ROM, but where i live in Pakistan so on highways we experience signal drops from cellular towers.
And problem with this ROM is when signals get up and down phone gets restart repeatedly.
Or in simple words when signals are auto switching between 2G, 3G and 4G it gets restart.
And also please guide me how to share logs ?
Click to expand...
Click to collapse
Connect your phone yo pc, give adb acces to it and on the power shell (in adb folder) run
adb logcat -d > log.txt
and share me the log.txt file that will appear in your adb folder, it's important to take the log while the error is happening
sani23 said:
A noob question! Since you don't have VoLTE line it may never be incuded in the ROM. Correct? That being the case, is it possible for you to take the module from other moto devices or say if i could send you my phone's image, could you add the module to rom? It would be really helpful. Eversince I uncloed my device, every update makes me reset the phone and gets stuck on bootloop. It's very time consuming and beats the hell out of me
Click to expand...
Click to collapse
Atm we haven't found a workaround for volte, maybe I'll look into it once other bugs are solved
WhistlerNL said:
Hi, sorry for cross posting. Just installed LineageOS and noticed the problem about the Bluetooth calling issue. Thought I'd install this one, but read that it has the same problems. Does anyone here have an update on that? Anything I can do to help?
Click to expand...
Click to collapse
Most bugs are shared because we use the same device source (I base on joshua's work, lineage maintainer). As soon as this issue is solved I'll upload the build and add it to the changelog
Hello together,
I flashed the ROM yesterday and everything is working extremly good except one thing. Normal phone calls are not working. Everytime I do a call it says that the phone call is initializing but it hangs up at that point. If I try to close the call it just says that the call is closed but nothing happens. I have to restart the phone completely. I come from Lineage OS 17.1 and I the phone call issue was there too. Any idea how I can get it back to working? Things I tried:
- Other Dialer apps with setting them to standard with every right they need
- Deactivate auto search network and set the correct provider
- Setting LTE to default
I added two logfiles but i had to shorten it a little bit because of the size for free users. I hope it's enough.
Outgoing Call:
https:// pastebin.com / aGM9WV5S
Canceling Call:
https:// pastebin.com / wc54K0A7
Edit: Sry for insert spaces in the links but under 10 posts you can't post links.
ceroc said:
Hello together,
I flashed the ROM yesterday and everything is working extremly good except one thing. Normal phone calls are not working. Everytime I do a call it says that the phone call is initializing but it hangs up at that point. If I try to close the call it just says that the call is closed but nothing happens. I have to restart the phone completely. I come from Lineage OS 17.1 and I the phone call issue was there too. Any idea how I can get it back to working? Things I tried:
- Other Dialer apps with setting them to standard with every right they need
- Deactivate auto search network and set the correct provider
- Setting LTE to default
I added two logfiles but i had to shorten it a little bit because of the size for free users. I hope it's enough.
Outgoing Call:
https:// pastebin.com / aGM9WV5S
Canceling Call:
https:// pastebin.com / wc54K0A7
Edit: Sry for insert spaces in the links but under 10 posts you can't post links.
Click to expand...
Click to collapse
First of all, please install the official version found at pixelexperience.org/evert
Secondary, to make calls disable VoLTE for now
juampapo546 said:
First of all, please install the official version found at pixelexperience.org/evert
Secondary, to make calls disable VoLTE for now
Click to expand...
Click to collapse
Thanks for the quick answer! I used the official plus edition from your site for flashing. Disabling VoLTE worked. I totally forgot what VoLTE means pronounced... It makes now sense why everybody is asking about it. Sorry for bothering you and keep on the good work. Never had less problems with Pixel Experience than with other roms.
Hi,
I am using Freedom Mobile in Canada and bought the Sony XPERIA 5 III 5G XQ-BQ72. This is a taiwanese dual sim.
The basic services work but the enhanced services don't. I checked before hand and knew that to be the case but having read forums I thought I might be able to get it working.
First I tried @Gigio755 advice here https://forum.xda-developers.com/t/xq-at52-volte-or-wifi-calling-in-canada.4128611/
Where you dial dial *#*#4636#*#* and switch Vowifi on. But the thing is greyed out
Next I tried was @BSPI advice here
https://www.reddit.com/r/freedommobile/comments/bg5x3c
That's where you text *#243203855# then choose GLW, but I get MMI error.
I've also tried @f1v12 advice here
https://www.reddit.com/r/galaxys10/comments/dbf1lj
Where you text #272<your phone's imei number># but also get MMI error
To fix the MMI error I tried following https://www.technobezz.com/fix-connection-problem-invalid-mmi-code/
These didn't work, but specifically I couldn't try method 3, Turn on IMS over SMS because my IMS is not registered
Following @sooki99 here
https://www.reddit.com/r/freedommobile/comments/c331l5
I tried to register an apn type ims, but got an error saying Freedom does not allow adding apn type IMS.
I've contacted tech support with Freedom, they said they registered my IMEI. They also said they don't need to provision my IMEI so I'm not sure what registering they did.
So, I'm wondering what the next thing to try is. Is there a way to fix the MMI error so I can at least send dial codes?
I was thinking of flashing the US firmware next, does anyone know if that works? I know I'd loose the dual sim support (on a side note, why is that?), but does anyone know if that would help?
I have also the problem with wifi calling feature with Israeli operator. The feature on the network side activated, and they checked it with the phone number. They told me they don't need IMEI for wifi calling, and if the phone supports it, the option should appear on the phone''s menu, but it doesn't appear.
I got the phone from UK, it's dual sim model XQ-BQ52
Any ideas?
Hi @dima_vy
First thing to try would be the firmware flashing. You can do this without rooting or boot unlocking.
Get xperifirm and newflasher. There's a few customizations for XQ-BQ52 you can try without messing up your phone. I have the XQ-BQ72, and when I tried the 52 firmwares, the phone works but the modem connects and disconnects continuously so I doubt you'll find a working solution from the 72's.
But...
From a comment by @noldoli on:
Thank you ASUS for implementing VoLTE & VoWiFi for Telstra, Australia in Nov 2021 Firmware Update
Please tell us some basic information before asking for help: Model Name: Rog 5 Firmware Version: WW_18.0840.2109.188 Rooted or not: Not Frequency of Occurrence: Happily always! APP Name & APP Version (If your issue relates to the app): Phone calls In addition to information above, please also...
zentalk.asus.com
it really looks like you need:
The phone having the necessary MBN files for the mobile carrier in question
The SIM having VoLTE provisioned by the carrier in question
It really seems you need Sony to include these files on their updates, which they are unlikely to do in countries they did not release the phone. BTW, if you ask Sony they will blame the carrier.
So, I think the next thing to try is with a root, following @astracd guide for the onplus 5: https://forums.oneplus.com/threads/oneplus-5-5t-freedom-mobile-wind-wifi-calling-and-volte.880807/
You need to root, and try replacing the mbn files from the pixel 4 (assuming they have the israili customizatins). It's an older modem. but that doesn't seem to be a problem.
Rooting guide from @Miustone
[CLOSED] Deleted
Here was a Guide. Someone said people don't care about Me or My Work so...
forum.xda-developers.com
I couldn't get my superuser to work (so must not have been rooted properly), so I couldn't continue testing other mbn files. I'd love to hear if someone has success with this method though.
mavicanuck said:
You need to root, and try replacing the mbn files from the pixel 4 (assuming they have the israili customizatins). It's an older modem. but that doesn't seem to be a problem.
Click to expand...
Click to collapse
mbn file must be for the phone with same chipset.
Pixel 4 uses Qualcomm SM8150 Snapdragon 855 and Sony Xperia 5 III SM8350 Snapdragon 888. So pixel mbn file will not work with this phone.
OK, I see guys, thank you for advises. I don't see any Israeli versions on any other models... I will try to do more research.
PHHs AOSP GSI based ROMs will have a way to force VoLTE and WiFi Calls on any way. If You can live with AOSP, that will BE the easy way (possibly)
I read today about android 12 coming to Xperia 5 iii, may be it will fix the issue
I just checked again, and there is a global version for XQ-BQ52 with CID 23365115. Is there a way to check what firmware i have exactly installed?
Android 12 didn't fix VoWifi issue
Hi,
I've seen there's now a USA customization out. Does anyone know if that will work on Freedom in Canada?
mavicanuck said:
Hi,
I've seen there's now a USA customization out. Does anyone know if that will work on Freedom in Canada?
Click to expand...
Click to collapse
Unlikely. Sony does not have Wi-Fi Calling on AT&T, T-Mobile, or Verizon.
They only had Wi-Fi Calling on the XZ1 Compact on T-Mobile. Literally just one phone on one network in all their history.
There is a version for global market for XQ-BQ52. May be this one will work?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Problems like this make it harder to consider future Xperia phones. I would happily buy the Xperia 1 IV but no volte means it's not worth buying
Hazzay88 said:
Problems like this make it harder to consider future Xperia phones. I would happily buy the Xperia 1 IV but no volte means it's not worth buying
Click to expand...
Click to collapse
The main issue that in some time mobile operators will shut down the 3G networks, and phone without VoLte simply won't work...
Thats exactly
dima_vy said:
The main issue that in some time mobile operators will shut down the 3G networks, and phone without VoLte simply won't work...
Click to expand...
Click to collapse
That's exactly the issue we face. I have the Xperia 1 II and flashed SEA firmware to get volte working but I don't think I will have the same success with Xperia 1 IV.
I would definitely buy the Xperia 1 IV if I know volte will work. It's an expensive phone and having no volte will make the phone useless once 3G network is shut which is imminent now
Hazzay88 said:
Thats exactly
That's exactly the issue we face. I have the Xperia 1 II and flashed SEA firmware to get volte working but I don't think I will have the same success with Xperia 1 IV.
I would definitely buy the Xperia 1 IV if I know volte will work. It's an expensive phone and having no volte will make the phone useless once 3G network is shut which is imminent now
Click to expand...
Click to collapse
I have now Xperia 5 iii, and I'm not sure that there is any firmware that will allow me to use volte and vowifi in Israel. According to Sony, as they don't sell phones here, they won't provide firmware which will support these functions in Israel... Israeli ministry of communications allows operators to shut down 3g networks in 2025 I think. I expect this phone to work more. My previous Xperia x worked 4.5 years.
So I just hope that there will be a way to use Sony phones in the future
If the Xperia 1 IV doesn't have success I will get the Pixel 7 Pro as that is locally available which volte/ WiFi calling will work out of the box. However I prefer Xperia 1 IV but not going to pay for a phone with limited features. 3G network will start to shutdown this year for Australian network operators
Hello,
I have a Xiaomi 12 since September 2022. I have just received miui 14 in global version. When I use Android auto, the phone randomly disconnects and reconnects in a loop. No matter if I unplug or plug my phone back in or restart it or not, it cannot be reconnected.
I can reconnect it again the next day until it starts again, sometimes after ten minutes sometimes an hour.
I suspect the battery saver killing a process despite the fact that I changed the settings of many apps to prevent this.
My old Oneplus works perfectly on my car.
I am really very disappointed with this phone and miui 14 does not bring anything, I do not even have the novelties like the super icons...
Can you help me
MrBiker37 said:
Hello,
I have a Xiaomi 12 since September 2022. I have just received miui 14 in global version. When I use Android auto, the phone randomly disconnects and reconnects in a loop. No matter if I unplug or plug my phone back in or restart it or not, it cannot be reconnected.
I can reconnect it again the next day until it starts again, sometimes after ten minutes sometimes an hour.
I suspect the battery saver killing a process despite the fact that I changed the settings of many apps to prevent this.
My old Oneplus works perfectly on my car.
I am really very disappointed with this phone and miui 14 does not bring anything, I do not even have the novelties like the super icons...
Can you help me
Click to expand...
Click to collapse
Probably due to the rom version.
Either you wait for an update to a stable or you downgrade but it involves unlocking the bootloader.
I know your phone says Stable but it still says Stable.
Xiaomi 12 GlobalStable BetaRecoveryV14.0.2.0.TLCMIXM13.04.7 GB2023-01-14
Thank you for your reply.
Do you think this is a bug that will be fixed? From what I've read some users have had this bug since the phone was marketed...
I'm not against unlocking the bootloader and installing beta versions but that removes the warranty. Do you think there is a hardware problem?
MrBiker37 said:
Thank you for your reply.
Do you think this is a bug that will be fixed? From what I've read some users have had this bug since the phone was marketed...
I'm not against unlocking the bootloader and installing beta versions but that removes the warranty. Do you think there is a hardware problem?
Click to expand...
Click to collapse
Was it working before the update?
Unlocking the bootloader does not void the warranty.
it never worked even with miui 13
MrBiker37 said:
it never worked even with miui 13
Click to expand...
Click to collapse
Which model?
my phone/detailed info/model.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
just 2201123G would have been enough, whatever.
Go to installed apps/3 dots at top right/show all apps/search for auto/android auto/additional settings in the app.
And/ or
empty the cache and / or erase everything and / or uninstall the updates.
I've done this procedure several times before, the last time when I last updated Android auto with the new interface, about a week ago.
MrBiker37 said:
I've done this procedure several times before, the last time when I last updated Android auto with the new interface, about a week ago.
Click to expand...
Click to collapse
May be a hardware problem, do a factory reset to be sure, since you will have to do it anyway if you send it in warranty.
Hello what I remember is that the cellular network change during drive was suspected to disturb the AA connection for several mobile models.
NOSS8 said:
May be a hardware problem, do a factory reset to be sure, since you will have to do it anyway if you send it in warranty.
Click to expand...
Click to collapse
I didn't want to come to this but I resigned myself and I just did it, I'm going to test like this.
Loddel said:
Hello what I remember is that the cellular network change during drive was suspected to disturb the AA connection for several mobile models.
Click to expand...
Click to collapse
It may be an idea but what would be the solution if it exists?
Thank you so much for your help
hi,
in miui 13, i had the same problem
with a renault car with rlink
the problem is the usb cable.
try others
maybe
MrBiker37 said:
it never worked even with miui 13
Click to expand...
Click to collapse
There was already this problem on some devices with MIUI13.
https://xiaomi.eu/community/threads/android-auto-wireless-connection-aborts-network-change.67875/
MIUI : 14.0.23.1.30.DEV
Android13
Android Auto
Disruption is very severe.........
NOSS8 said:
There was already this problem on some devices with MIUI13.
https://xiaomi.eu/community/threads/android-auto-wireless-connection-aborts-network-change.67875/
Click to expand...
Click to collapse
Thanks a lot but my car is not compatible with wireless.
The factory reset seems to have been beneficial but I have not been able to test over long distances for the moment.
The problem appeared briefly during one of my routes.
I will also try with another cable. Thank you for your answers !
MrBiker37 said:
Thanks a lot but my car is not compatible with wireless.
The factory reset seems to have been beneficial but I have not been able to test over long distances for the moment.
The problem appeared briefly during one of my routes.
I will also try with another cable. Thank you for your answers !
Click to expand...
Click to collapse
Hi,
Did the factory reset solve the problem ? I have the disconnect/reconnect loop on my xiaomi 12 since i start using it (miui 13 and 14). I was never able to fix it.
Note that i am using it wireless, so usb cable cannot be the culprit, and my wife galaxy s21 works flawlessly wirelessly with the same car
I have the same problem with my Xiaomi 12 pro...
There's any solution?
MrBiker37 said:
Hello,
I have a Xiaomi 12 since September 2022. I have just received miui 14 in global version. When I use Android auto, the phone randomly disconnects and reconnects in a loop. No matter if I unplug or plug my phone back in or restart it or not, it cannot be reconnected.
I can reconnect it again the next day until it starts again, sometimes after ten minutes sometimes an hour.
I suspect the battery saver killing a process despite the fact that I changed the settings of many apps to prevent this.
My old Oneplus works perfectly on my car.
I am really very disappointed with this phone and miui 14 does not bring anything, I do not even have the novelties like the super icons...
Can you help me
Click to expand...
Click to collapse
Hi, exactly same problem on my Xiaomi Redmi note 10 Pro since MIUI 14 update, whatever AA release I try. Any solution found? Thx
tompie00 said:
Hi, exactly same problem on my Xiaomi Redmi note 10 Pro since MIUI 14 update, whatever AA release I try. Any solution found? Thx
Click to expand...
Click to collapse
Unfortunately I have not found a solution.
I got around the problem by buying an Android auto wireless adapter (my car is not compatible with AA Wireless).
I have take this https://aawireless.io/
Sometimes there are disconnections but it reconnects right away.
Moreover, it is very practical not to take out the phone for short trips.
Have a Good day !