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 !
Related
Hello Guys,
I know many people here are wondering that how to fix the GPS issue after upgrading to Jelly Bean 4.1.2 I have been searching for a long time now and last week I found a proper fix for this problem at last
The GPS problems people are facing after upgrading to 4.1.2 JB are :
1. GPS taking a long long time to show my location
2. Maximum time it shows that unable to find my location
3. Even if I use Gps Fix or GPS Fix Delux application, I have to do the fix everytime I turn on my GPS, reboot my phone, if I'm not using GPS more that 1.5 - 2 hours
It's Really Annoying . . . Thats Why I came up with a brilliant solution of this which whill need fix for 1 time only. You will never have to fix your GPS again.
The Steps for One Time fixing the GPS issue:
1. Download this Application from play store : GPS Status - Test & Fix
2. Go under open sky
3. Open the application.
4. If you see that your Latitude and Longitude are not Showing, then your GPS is not working.
5. For that case, 1st tap on the "Reset GPS"
6. Then Tap on the "Get Xtra Data"
7. This will take 5-10 mins of time to completing the fix. But make sure you are under open sky and You are Connected to Internet. To get the Xtra Data, the application will need Internet connection.
8. After a while when you will see that the application is showing your Latitude and Longitude, you will understand that your GPS has been fixed. You will never have to run this app ever again. From now on your GPS will get auto locked to your position.
Enjoy
*** NO ROOT REQUIRED ***
Screenshots:
{
"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"
}
If this thread helped you, dont forget to hit the thanks button :good:
This 'Xtra data' thing is in "GPS Aids' as well. But it does not stick forever. Are you saying now after using the tool you mentioned, anytime you are outdoors just opening say for example Navigation or Maps you get a direct gps lock within a minute or so without making use of additional gpsfix apps ever?
Can you post your gpsconf file here after you have used this app?
RAD7 said:
This 'Xtra data' thing is in "GPS Aids' as well. But it does not stick forever. Are you saying now after using the tool you mentioned, anytime you are outdoors just opening say for example Navigation or Maps you get a direct gps lock within a minute or so without making use of additional gpsfix apps ever?
Can you post your gpsconf file here after you have used this app?
Click to expand...
Click to collapse
Yes brother it worked for me even if I do reboot my phone or turn on my gps after long time keeping it in off state, it just auto lock my position. Yes sometime tough it takes a little time, but I never have to do gps fix again. Also as you requested I'm attaching my gps.conf file here.
You can get it from here: https://www.sugarsync.com/pf/D1732447_087_30755727
P.S.: It took almost 1 minute and 29 seconds to lock my position.
Sent from my ME865 using Tapatalk 2
isaumya said:
Yes brother it worked for me even if I do reboot my phone or turn on my gps after long time keeping it in off state, it just auto lock my position. Yes sometime tough it takes a little time, but I never have to do gps fix again. Also as you requested I'm attaching my gps.conf file here.
You can get it from here: https://www.sugarsync.com/pf/D1732447_087_30755727
P.S.: It took almost 1 minute and 29 seconds to lock my position.
Sent from my ME865 using Tapatalk 2
Click to expand...
Click to collapse
I used root tweaker and m getting it fixed
Sent from my ME865 using xda premium
Ok I used this tool today and I tested it randomly through the day before I came to commenting and I second your post that indeed this thing has been the best so far of all tools I used for the gps fix. The reason I had asked for your gpsconf file was to see values this tool wrote & yours is the global ntp pool, I have mine manually edited as the India ntp server. On second use it did refuse to lock but thereon the results have been nearly instantaneous :good:
RAD7 said:
Ok I used this tool today and I tested it randomly through the day before I came to commenting and I second your post that indeed this thing has been the best so far of all tools I used for the gps fix. The reason I had asked for your gpsconf file was to see values this tool wrote & yours is the global ntp pool, I have mine manually edited as the India ntp server. On second use it did refuse to lock but thereon the results have been nearly instantaneous :good:
Click to expand...
Click to collapse
Really happy to know that it worked for you brother, sometimes it take 2 minutes to lock the gps. Don't worry just wait it will be automatically locked
Sent from my ME865 using Tapatalk 2
Worked perfectly, bro. Thanks for the solution. I must say JB 4.1.2 absolutely rocks!
Thank you worked for me too! I recently purchased GT-H9500 (S4 clone) I'm pretty sure I checked the gps when I got it a week ago and it worked. I rooted a few days ago and it did not work.
The app took about 15-20 minutes. it was interesting watching it, first it was 0/0 then 0/1 then 0/2 etc, finaly the screen populated with similar data above.
the magnetic field is "not available" for some reason
ozzman77 said:
Worked perfectly, bro. Thanks for the solution. I must say JB 4.1.2 absolutely rocks!
Click to expand...
Click to collapse
I'm really glad to know that it works for you. Please don't forget to give a thanks a reputation.
Sent from my ME865 using Tapatalk 4 Beta
mgh0621 said:
Thank you worked for me too! I recently purchased GT-H9500 (S4 clone) I'm pretty sure I checked the gps when I got it a week ago and it worked. I rooted a few days ago and it did not work.
The app took about 15-20 minutes. it was interesting watching it, first it was 0/0 then 0/1 then 0/2 etc, finaly the screen populated with similar data above.
the magnetic field is "not available" for some reason
Click to expand...
Click to collapse
I'm really glad to know that it works for you. Please don't forget to give a thanks a reputation.
Sent from my ME865 using Tapatalk 4 Beta
Hi,
I have tried "GPS Status - Test & Fix" in my LG Optimus L5 II Dual E455 phone and it didnt fix the issue. I got the phone 2 weeks back and only first time the navigation worked. I think i did an update software for LG the first time and I think it stopped working after that. I had tried the "GPS Status - Test & Fix" several times,also restarted and reset the phone couple of times. it hasnt fixed yet.
Any other suggestions would really help.
Thanks in advance.
An Update:
Now my GPS is working. What i had tried is i went to LG Customer Support and they swaped my Sim 1 and Sim 2 as my Sim 1 was earlier in roaming. Then they enabled my Data Connectivity instead of wifi and were able to get the position in the google maps. But my GPS application "navfree" and "GPS Status-Test & Fix" were still not able to fix the Satellites.
So, i came out disappointed. Then i travelled with my Data Connectivity enabled and used "Google Apps" for navigation for one whole day. Then i tried the "GPS Status - Test & Fix" and few other GPS fix apps and they all started getting the satellite fixed. Now, i disabled and tried the GPS app "navfree" for past few days without Data Connectivity and its working.
So in Summary to have it work :
1. Swapped the Sim's
2. Enabled Data Connectivity in the non-roaming SIM
3. Use Google Navigation for a day with it
4. Run "GPS Status -Test & Fix" in open sky and reset old data and get new GPS Data.
5. GPS satellite got fixed
6. Turned off Data Connectivity
7. Tried NavFree app.
8. working for past few days without issue and without data connectivity.
Hope that helps for other users.Also, thanks to "isaumya" for providing the initial solution.
din_jig said:
Hi,
I have tried "GPS Status - Test & Fix" in my LG Optimus L5 II Dual E455 phone and it didnt fix the issue. I got the phone 2 weeks back and only first time the navigation worked. I think i did an update software for LG the first time and I think it stopped working after that. I had tried the "GPS Status - Test & Fix" several times,also restarted and reset the phone couple of times. it hasnt fixed yet.
Any other suggestions would really help.
Thanks in advance.
Click to expand...
Click to collapse
Interesting I find this post today as I am in roughly the same boat, except I have owned the phone for a couple of months now and was beginning to think it was related to a software update. I may try restoring an earlier version and seeing if that fixes it.
spunkylm said:
Interesting I find this post today as I am in roughly the same boat, except I have owned the phone for a couple of months now and was beginning to think it was related to a software update. I may try restoring an earlier version and seeing if that fixes it.
Click to expand...
Click to collapse
Can only speak for Motorola Atrix 2 & the one & only final fix for the damned gps lock issue is by a user called 'ghittone', that is the only one that works & nothing else, period!!
thanks
Thanks dude.. I works...!!
Hey, the "Get Xtra Data" for me works really fast, not even close to 5-10min you said. How do I know it's working?
:good::good::good:
I didnt work for me
Hi,
I did what you said. after sometime it shows the screen you have shared, however whenever I start that app again or even try to navigate using google map problem remains as it is
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
Hi there,
I need some help or advice. I have upgrade to A13 some days ago and apart from the crazy battery drain with "Phone Idle" and "Mobile Networks" I am facing a weird Viber drain which never occured before :
Shows and 20-30% battery consumation with 15-25 hours "alive" and only 2-3 minutes in background.
Ofcourse this is nonsense the real usage is the 2-3 minutes and not the 15-25 hours
I have wiped cache , and done a uninstall re-install but nothing happens.
Viber is the no.1 battery consumer in the app list.
Any advice,guys?
I am already very disappointed with the A13 drain with "Phone Idle" and now this Viber issue comes up Heeeeelp !
Why are you reporting a viber bug here?
ibanezman192 said:
Why are you reporting a viber bug here?
Click to expand...
Click to collapse
He's reporting it here because its a13 problem on our device not vibers.i have p6p and i have the same bug. does anybody have a solution?
This does not have anything to do with the P6.
It is an app issue and needs to be reported to the developer of the app.
Exactly. It's a well known problem with the latest version of Viber across many devices. So stop spamming irrelevant stuff to Pixel 6, or else.
ibanezman192 said:
Exactly. It's a well known problem with the latest version of Viber across many devices. So stop spamming irrelevant stuff to Pixel 6, or else.
Click to expand...
Click to collapse
How come it only showed up after A13 uprade? On A12 Viber was normal, with A13 its a mess with massive drain
You cant be serious this is not A13 related.....
blaze73 said:
How come it only showed up after A13 uprade? On A12 Viber was normal, with A13 its a mess with massive drain
You cant be serious this is not A13 related.....
Click to expand...
Click to collapse
Because Viber app is maybe not updated to support A13.
Several apps need an update to work under A13.
In my case, DJI Mimo needed an update to v1.7.26, after that it started correctly.
Cheers
Tom
tom1807 said:
Because Viber app is maybe not updated to support A13.
Several apps need an update to work under A13.
In my case, DJI Mimo needed an update to v1.7.26, after that it started correctly.
Cheers
Tom
Click to expand...
Click to collapse
I see this is a bummer. However I feel that this is more like a Google issue not Viber's fault but we will see. My battery life
is tragic, worst ever in my 10+ years smart phone usage...
Looks like your feeling is not shared with the moderators, it was moved to general.
Beside that, maybe check Google whether others reported the same problem and maybe offer workarounds.
Cheers
tom1807 said:
Looks like your feeling is not shared with the moderators, it was moved to general.
Beside that, maybe check Google whether others reported the same problem and maybe offer workarounds.
Cheers
Click to expand...
Click to collapse
I tried to check but could not find any workaround so far and this is very annoying that it is the main consumer. (APP)
Top drainer it is, next to "Phone Idle" I have been trying to find a workaround but none so far or I have been bad with searching...
blaze73 said:
I tried to check but could not find any workaround so far and this is very annoying that it is the main consumer. (APP)
Top drainer it is, next to "Phone Idle" I have been trying to find a workaround but none so far or I have been bad with searching...
Click to expand...
Click to collapse
Look into this topic, the section "RECOMMENDED AFTER UPDATE". The first 3 items could help, but you should be familiar with "platform-sdk-tools" and ADB commands (also how to open a command prompt in Windows).
Cheers
Tom
tom1807 said:
Look into this topic, the section "RECOMMENDED AFTER UPDATE". The first 3 items could help, but you should be familiar with "platform-sdk-tools" and ADB commands (also how to open a command prompt in Windows).
Cheers
Tom
Click to expand...
Click to collapse
I did some of the settings and no, I am not familar with "platform-sdk-tools" and ADB commands.
I am a regular user not a tweaker. Unfortunately nothing has changed. Phone ide is 35% in 8 hours in flight mode
and Viber is still top consumer APP Insane ! I am really fed up with this A13. Battery cant even last 24 hours
using flight mode for the night. : (
{
"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"
}
Maybe you should explain what you did?
Cheers
tom1807 said:
Maybe you should explain what you did?
Cheers
Click to expand...
Click to collapse
The recommended "DISABLE" bits and parts. Did not really help. Still heavy battery drain and Viber is no.1 consumer APP-wise otherwise its "Phone Idle" 30-35%
No, I specifically said the 3 commands written in "RECOMMENDED AFTER UPDATE". The others may help, but not for ur problem.
One command specifically deals wit re-compiling all the apps which could help with overheating and battery drain.
The other one deals with battery drain.
"Disable" bit and parts could cripple your phone if you don't know what they exactly do.
And don't focus on how much 30-35% for Phone idle writes.
If your phone used for example 10% battery, the 30% of these 10% were drained, but not 30% of the battery.
Cheers
tom1807 said:
No, I specifically said the 3 commands written in "RECOMMENDED AFTER UPDATE". The others may help, but not for ur problem.
One command specifically deals wit re-compiling all the apps which could help with overheating and battery drain.
The other one deals with battery drain.
"Disable" bit and parts could cripple your phone if you don't know what they exactly do.
And don't focus on how much 30-35% for Phone idle writes.
If your phone used for example 10% battery, the 30% of these 10% were drained, but not 30% of the battery.
Cheers
Click to expand...
Click to collapse
Alright. Can you tell me what to do and how to do with these 3 commands? I will perform but I would need some step-by-step help if possible
Enable USB debugging on your mobile. Download the platform-sdk-tools and unzip to a directory.
Connect your mobile to a PC, and open a command prompt.
Type adb devices, authorize the connection on the mobile and then type the commands.
All this can be easily found, here on XDA and internet.
Cheers
tom1807 said:
Enable USB debugging on your mobile. Download the platform-sdk-tools and unzip to a directory.
Connect your mobile to a PC, and open a command prompt.
Type adb devices, authorize the connection on the mobile and then type the commands.
All this can be easily found, here on XDA and internet.
Cheers
Click to expand...
Click to collapse
Great. Many thanks, man. I will wait for the september patch if nothing happens I will do these steps.
Viber is still no.1. consumer staying on top with 25% consumation with bogus data
Phone Idle is 35% with 18-20hours standby which is insane. This A13 update was a catastrophe in terms of battery life
Google won't fix Viber. That's a Viber problem.
So far Viber is developed up to API 30, Android 13 is API 33.
Cheers
tom1807 said:
Google won't fix Viber. That's a Viber problem.
So far Viber is developed up to API 30, Android 13 is API 33.
Cheers
Click to expand...
Click to collapse
Good to know that. (API 33) I have sent a report , trouble ticket to Viber support.
Hope it will be dealt with.
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
Anyone else experiencing the problem? I hooked up to head unit and phone asking me to charge or transfer file lol.
I'm on global rom with mi 13 cn
{
"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"
}
no problems with Android Auto on Xiaomi EU rom.
i have the CN version s well...
Gankadin said:
no problems with Android Auto on Xiaomi EU rom.
i have the CN version s well...
Click to expand...
Click to collapse
I did some searches and apparently miui14 has this issue. Not sure how yours worked fine though
rockmaster said:
I did some searches and apparently miui14 has this issue. Not sure how yours worked fine though
Click to expand...
Click to collapse
i tested it on 2 cars: mg zs ev- at first it crashed but after restarting the issue gone, on BYD atto 3 it worked perfectly from the first try. it even works wireless...
Gankadin said:
i tested it on 2 cars: mg zs ev- at first it crashed but after restarting the issue gone, on BYD atto 3 it worked perfectly from the first try. it even works wireless...
Click to expand...
Click to collapse
Thanks. Just flashed EU .21 rom. Let's see....
rockmaster said:
Thanks. Just flashed EU .21 rom. Let's see....
Click to expand...
Click to collapse
Good luck
Gankadin said:
i tested it on 2 cars: mg zs ev- at first it crashed but after restarting the issue gone, on BYD atto 3 it worked perfectly from the first try. it even works wireless...
Click to expand...
Click to collapse
Hi, do you have any disconnection with Wireless Android Auto as described here ? : https://new.c.mi.com/global/post/88433 .
Android Auto Wireless disconnects temporarily when phone switches between 3G/4G/5G.
butchy93 said:
Hi, do you have any disconnection with Wireless Android Auto as described here ? : https://new.c.mi.com/global/post/88433 .
Android Auto Wireless disconnects temporarily when phone switches between 3G/4G/5G.
Click to expand...
Click to collapse
i hadn't got disconnection when going from 4g or 5g to 3g, but if there is area without any data connection then i got disconnection and as soon as data connection is back the AA is back as well. usually it takes less than a minute.
BTW bros on my MG i have a wired AA, and i noticed that with my old cable i would get errors and crashes, as soon as I switched to the original cable that came in the box all errors gone and vanished.
So if you experience problems consider to switch to original cable.
Gankadin said:
i hadn't got disconnection when going from 4g or 5g to 3g, but if there is area without any data connection then i got disconnection and as soon as data connection is back the AA is back as well. usually it takes less than a minute.
Click to expand...
Click to collapse
Thx for your quick answer.
So Xiaomi didn't manage to fix this bug with Miui14.
butchy93 said:
Thx for your quick answer.
So Xiaomi didn't manage to fix this bug with Miui14.
Click to expand...
Click to collapse
Yeah
Gankadin said:
i tested it on 2 cars: mg zs ev- at first it crashed but after restarting the issue gone, on BYD atto 3 it worked perfectly from the first try. it even works wireless...
Click to expand...
Click to collapse
You already test Android auto in Atto 3? Which version are you running on Atto 3 ? mine is 1.3.x
if we are running at the same version can you tell me how to make it work, please? Thank you
Bigbearxl said:
You already test Android auto in Atto 3? Which version are you running on Atto 3 ? mine is 1.3.x
if we are running at the same version can you tell me how to make it work, please? Thank you
Click to expand...
Click to collapse
I don't have Android Auto native yet, only apple car play right now.
I am using Carlink dongle that is connected to the car and allow me to use the Android Auto.
Something like this:
https://a.aliexpress.com/_mqEq6e6
Gankadin said:
I don't have Android Auto native yet, only apple car play right now.
I am using Carlink dongle that is connected to the car and allow me to use the Android Auto.
Something like this:
https://a.aliexpress.com/_mqEq6e6
Click to expand...
Click to collapse
Thank you for the replies Gankadin, I thought we have native Android Auto already, I'll wait till 1.4 maybe XD.
Xiaomi mi 13 with miui 14.07.
Android auto works but wireless android auto IF it works, disconnects. But mostly can't connect to AA Wireless dongle on Toyota Rav 4. My "old" LGV60 worked perfectly. My wife's Xiaomi mi 10 with miui 13 worked well to. But with miui 14 the story is the same.
digitalw said:
Xiaomi mi 13 with miui 14.07.
Android auto works but wireless android auto IF it works, disconnects. But mostly can't connect to AA Wireless dongle on Toyota Rav 4. My "old" LGV60 worked perfectly. My wife's Xiaomi mi 10 with miui 13 worked well to. But with miui 14 the story is the same.
Click to expand...
Click to collapse
Which version of the Xiaomi 13 is it? Chinese Mainland version or global version?
Are you on their official build or custom build like EU? Did you unlock your bootloader, please?
It is the official rom, global version 14.07
The problem is basically in management of the mobile data, wifi and bluetooth by MiUi
first i got instructions from Xiaomi:
1. Check if Android Auto is the latest version and if there is a new version in the Google Play Store 2. Find Android Auto in Settings-App Settings-App Management and clear Android Auto data. Then, turn on the self-start permission, try to grant the required permission, open Android Auto once, and grant the permission 3. Turn on Android Auto. Go into """"Settings"""", find """"Previously connected cars"""", tap the """"three dots"""" at the top Forget all cars, and make sure """"Add new car to Android Auto"""" is activated 4. Use another USB cable, the length should not exceed 6 feet, do not use a USB extender, there is a """"trident"""" symbol on the USB cable. Select the second """"Android Auto"""" in the pop-up box after the USB connection 5. Try to connect wirelessly, enter """"Connect a car"""", select wireless connection
After all this, android auto was still not working until i did :
Apps/manage apps/Android Auto> restrict mobile data - ON (?!)
In android auto, enter developer mode and make Wireless android auto ON
Now, 3 days of driving and all works great.