I have buyed my Mi A2 Lite, he have oreo version of android, worth update to 9.0 ?
Luis2k17 said:
I have buyed my Mi A2 Lite, he have oreo version of android, worth update to 9.0 ?
Click to expand...
Click to collapse
Hello Luis2k17,
Hope You Are Doing Good.
Yes, People Are Facing Lots Of Problem After Updating To Android PIE 9.0.
Known Issues Are Given Below:-
Bluetooth Issue
Wifi Speed Issue
Voice Call Quality Issue
Call Recording Issue
Signal Drop Issue ETC ETC...
If You Are Satisfy With Mentioned Above Problem Then Go Ahead And Update To Android PIE 9.0
Greetings.
Thanks,
MUHAMMAD Asif Qasim
If you like using Gcam then no it is not worth it.
If you choose to stay on oreo, dont forget to disable in developer option, "automaticly install updates when reboot".
My phone upgraded to the March update, I have had none of the issues listed above, poor speech quality was fixed with this update. I don't use Gcam but believe that is an issue. If you upgrade, you can always revert to Oreo using Miflash tool.
I haven't had any problem when I updated to 9. I here there is a gcam for 9 now.but I'm custom ROM.but it seemednlike on 9 my data was faster
Luis2k17 said:
I have buyed my Mi A2 Lite, he have oreo version of android, worth update to 9.0 ?
Click to expand...
Click to collapse
The experience per users are different. Here's mine though.
Have this phone shipped with Oreo too, when I launch phone app everytime I'll make a call, I felt like it's slow AF, even I have the phone app updated. Then I haven't that much of the experience of Oreo version because of that.
And when I updated it to Pie version immediately after we (my family) bought this phone, for above reason, with February patch, the launch of the phone app (and almost all apps installed in this phone) seems faster than what was in Oreo. However, as other users said, there are issues: one of which is the WiFi/Bluetooth bug which the WiFi speed tend to go slow when connected to Bluetooth, and if it is connected to BT Audio, the audio/music/sound tend to stutters within 4 meters away from BT Audio equipment; GCam ports tend to have problems on focus (though it's partially fixed when you set GCam to 16:9 resolution). But so far, I'm still fine with it (and all good despite having these issues, at least it's not bricked, unlike its big brother, the Mi A2).
Here's the pick: If you're contented to what's on Oreo (plus better GCam handling and better WiFi) then stay with it. Otherwise, you can update it to Pie but with said issues.
Background: looking to "upgrade" my aging dual-sim global travel Huawei Honor 5X (BL unlocked running custom "Pie" ... ha ha) and ended up with A2 Lite (3G/32GB model - decided against the 4G/64GB) - tossed in a 64GB mSD for plenty of video storage & photos, using this as a backup & should be mostly on WiFi (5Ghz whenever possible, less congested ...) << would've gone for the A2 with bigger 6" + screen but a 4,000 mAh battery of the A2 Lite flipped the coin toss >>
Out of the box is Oreo - updated to mid 2018 and gone thru the updates, stopping just short of Pie, after installing my Apps & ran it, everything stable & smooth. Camera isn't a big deal, everything as expected & much faster & responsive compared to the Honor 5X, as good as my primary ... Motorola Moto X4 with 4G/64GB on Google "Fi" software channel, ran Oreo on it & updated since to Pie. Passed along my Moto G6 (3G/32GB) Fi variant (no NFC) to spouse with an integrated battery case (3,600 mAh + 4,000 mAh external ... "yes")
In short, I had plenty of competitive comparison - over AT&T, T-Mobile, Fi and also Ting & FreedomPop (both MNVO) networks, also while roaming abroad in Mexico & the Caribbeans recently ... just not with the new A2 Lite. I make good use of VoIP and WiFi calling, Duo/G.Voice/Hangouts but not much over WhatsApp or WeChat or FB Messenger. Whether it's on Oreo or Pie, pretty much not expecting to ever get WiFi calling enabled on AT&T or T-Mobile, but, not having Android Auto to work in our new Hyundai Sonata (2019) is not "happy" - and, AA is a problem with G6 and X4, tried all the "solutions" without rooting, as I wanted Google Pay to work on the X4 for mobile payment, sometimes.
Earlier this week, I decided - after taking precautions & making backups - upgraded A2 Lite to Pie, let it rebooted & settled down, check for more Apps updating, etc. Well, I am satisfied and happy, no problems with WiFi or LTE signals, as fast as it should be & benchmarked it with the other devices above - it's all good. My "happy dance" is with Android Auto, it worked the first time I tried and was in a hurry, it connected & Google Map is now projected onto the car's 7" touch-screen ... just couldn't get it to work on the G6 or X4 stock roms. Of course, Apple's CarPlay worked easily in the Hyundai with an iPhone SE running iOS 12.1.x
Being Android One, minimal to few bloatware (Xiaomi's bundle) is great - just switched to LawnChair v2.x launcher, so I can tweak the homescreen & lockscreen a little more. Battery life, especially on standby on WiFi is great - those are my thoughts ... I will update/amend this as necessary with any findings.
Hope this help to those using this in the Americas ...
Related
Hello guys,
Was wondering if people running the new official CM builds could give the rest of the community some overall impressions about the ROM. Specifically, what's working and what isn't, the issues they've faced so far and suitability as a daily driver. In the dev thread the only thing specified as not working is making calls.
The Dev thread is obviously not appropriate for this discussion and I'm eager to migrate from stock to AOSP since the device has long been abandoned by Samsung.
Well having an ATT Note 8.0 myself... as a 2nd unit to my 2 Note 8.0 devices running 4.4.2 amd 4.2.2. I chose to keep 4.2.1 on the ATT Note 8.0, due to it being locked and somewhat the step child here. Hopefully you have the Rogers (Canadian) version of my ATT Note 8.0. There are threads on Rogers Note 8.0 to assist you in recovering your device. If you have an ATT Note 8.0, your only hope is to have ATT send it in for exchange repair.
I am surprised you paid for a used item that did not work from a pawn shop. You may not get your money back, as some shops do not have a return policy.
gooberdude said:
Well having an ATT Note 8.0 myself... as a 2nd unit to my 2 Note 8.0 devices running 4.4.2 amd 4.2.2. I chose to keep 4.2.1 on the ATT Note 8.0, due to it being locked and somewhat the step child here. Hopefully you have the Rogers (Canadian) version of my ATT Note 8.0. There are threads on Rogers Note 8.0 to assist you in recovering your device. If you have an ATT Note 8.0, your only hope is to have ATT send it in for exchange repair.
I am surprised you paid for a used item that did not work from a pawn shop. You may not get your money back, as some shops do not have a return policy.
Click to expand...
Click to collapse
I'm not sure you're responding to the correct thread.
Anyone? Is there a chance the voice calls will work in the future or is it a dead end? Also how well do the cameras work (front and rear)?
Random video issues exist. Colored diagonal lines when using Netflix, Google video, etc. Also glitches sometimes when using various OS functions.
There are two of us with N5110s that have no gps output. Since I use mine for marine charts and the other is used for aviation charts it is more than an inconvenience. Sad to say that the other person (very competent, and specifically something of an expert on GPS) tried to file a bug report about it and was refused!?! Very strange.
What makes this particularly annoying is that the CM12.1 nightlies, very stable for a very long time, were converted to CM13 nightlies without any warning. Imagine my surprise when my occasional update resulted in CM13 booting (with problems) and required a wiping of /data to make it stable. Either a huge warning or a separate line of nightlies would seem appropriate.
Edit: I am also experiencing the occasional video flashing, but it doesn't get in the way of usability.
I am a big fan of CM but it does look like CM13 is still having teething problems.
Greg
The screen flicker issue is still there. Until they do not solve that issue, I cannot comfortably use CM13 on my N5100. I have to stay with CM12.1, and periodically test the nightly releases of CM13, until that bug is completely solved.
Everything else, seems to work fine.
sorry an unrelated question.
is there any cm 12.1 that works fine on n5100 which has fix calling bug.thanks
The flashing issue is supposed to be fixed in today's (4 May 16) nightly. Trying it now...
GPS still does not function.
Greg
CarinaPDX said:
The flashing issue is supposed to be fixed in today's (4 May 16) nightly. Trying it now...
GPS still does not function.
Greg
Click to expand...
Click to collapse
Yes, you are right. The flicker issue is solved in nightly release from May 4, 2016.
I have installed it, and make a backup of both, CM 12.1 and CM 13, to be protected if,
for some reason, something wrong will happen.
A workaround to easily change the USB mode from default, that is charging, to MTP data transfer,
will be usefull when connecting the phone to PC. It is very annoying to go every time to
Settings => Developer Options => Select USB Configuration, and choose the desired mode,
or select mode from drop down menu when you are notified for new USB connection presence.
There are third party applications on Google Play, like "USB for Marshmallow",
but it will be better if a solution to problem will be implemented directly in CM13,
that will set default mode to MTP data transfer.
I've tried Unofficial CM13 on my GT-N5100 3G/WIFI developed by RGIB.
SIM card not detected. Screen flicking. Camera failed.
parsa.io said:
I've tried Unofficial CM13 on my GT-N5100 3G/WIFI developed by RGIB.
SIM card not detected. Screen flicking. Camera failed.
Click to expand...
Click to collapse
have you followed Rgib's instructions on the first post of cm13?
Volte
Add volte support for oneplus one for the next official update
Got a 2017 VW and my old Xiaomi Mi Mix worked great with android auto being displayed on the dash.
I'm currently sitting on the 8.8.9 chinese miui 10 beta rom on the Mi Max 3 and I can't seem to get android auto to sync to the car.
Anyone else run into this?
omniphil said:
Got a 2017 VW and my old Xiaomi Mi Mix worked great with android auto being displayed on the dash.
I'm currently sitting on the 8.8.9 chinese miui 10 beta rom on the Mi Max 3 and I can't seem to get android auto to sync to the car.
Anyone else run into this?
Click to expand...
Click to collapse
I'm on miui.eu 10 global 8.8.3 and Android auto works fine.
Andy4Shurr said:
I'm on miui.eu 10 global 8.8.3 and Android auto works fine.
Click to expand...
Click to collapse
Is that the Xiaomi EU rom in the rom section?
And just to double check, Does android auto actually display on your car's screen ok? (I can launch Android auto on the phone fine)
omniphil said:
Is that the Xiaomi EU rom in the rom section?
Click to expand...
Click to collapse
It's an older version as I haven't updated yet... Don't know whether to do so as I'm happy with it as it is and my current version doesn't have anti rollback!
Andy4Shurr said:
It's an older version as I haven't updated yet... Don't know whether to do so as I'm happy with it as it is and my current version doesn't have anti rollback!
Click to expand...
Click to collapse
Does it actually connect to the screen in your car ok, Or are you just running the android auto app on your phone?
omniphil said:
Does it actually connect to the screen in your car ok, Or are you just running the android auto app on your phone?
Click to expand...
Click to collapse
Connects to my head unit display. It's in a 17 plate VW golf.
I always remove Android auto, Google, music apps, Google Maps etc from any battery saving restrictions in the settings and set them to have auto start permissions too.
Andy4Shurr said:
Connects to my head unit display. It's in a 17 plate VW golf.
I always remove Android auto, Google, music apps, Google Maps etc from any battery saving restrictions in the settings and set them to have auto start permissions too.
Click to expand...
Click to collapse
Ok thank you for confirmation, I'll see about moving over to the EU rom and see how that works for me. (Also 2017 Golf)
omniphil said:
Ok thank you for confirmation, I'll see about moving over to the EU rom and see how that works for me. (Also 2017 Golf)
Click to expand...
Click to collapse
No problem! It's one of the main reasons I got this phone over the Honor Note 10 as Huawei phones are notoriously bad for working with Android Auto.
MIUI PRO, No Dice
Andy4Shurr said:
No problem! It's one of the main reasons I got this phone over the Honor Note 10 as Huawei phones are notoriously bad for working with Android Auto.
Click to expand...
Click to collapse
My Android Auto would not work either on my phone. I am running MiUi Pro 8.9.6. It recognizes in the car and when I accept to run, it just doesn't show up. I have given it all the permissions required with no luck.
Damionix said:
My Android Auto would not work either on my phone. I am running MiUi Pro 8.9.6. It recognizes in the car and when I accept to run, it just doesn't show up. I have given it all the permissions required with no luck.
Click to expand...
Click to collapse
I'm guessing Xiaomi.eu must do something different with gapps then as Android pay also works with EU ROMs when it's based on Chinese miui which normally doesn't support that.
All I can tell you is that on this ROM Android Auto is working perfectly. It also did on my old mi mix 2 also running the EU ROM.
Andy4Shurr said:
I'm guessing Xiaomi.eu must do something different with gapps then as Android pay also works with EU ROMs when it's based on Chinese miui which normally doesn't support that.
All I can tell you is that on this ROM Android Auto is working perfectly. It also did on my old mi mix 2 also running the EU ROM.
Click to expand...
Click to collapse
Same here... Android Auto was not working on the Chinese roms, works great on the EU rom tho...
omniphil said:
Same here... Android Auto was not working on the Chinese roms, works great on the EU rom tho...
Click to expand...
Click to collapse
Glad you got it working mate, I couldn't live without Android Auto now I'm used to it!
Xiaomi.eu No Go
I tried the latest Xiaomi.eu ROM yesterday and got the dreaded Error -16 on it.
I just have no luck, and I need Android Auto work . Anyone have any suggestions?
I've got the same issue, really want AA to work again...
//Miui 10 CN stable
Ioniq electric
I can't get it working consistently on any of the EU roms newer than 8.8.9. I have filed a bug report for it in the standard MIUI forum, if it gets fixed there it should then get fixed in EU.
What you guys can do is register for the MIUI bug forum and then you can Confirm my bug report. The more people that Confirm it the more attention it is going to get so it gets fixed..
Here's a link to my bug report. Please Confirm it.
http://en.miui.com/thread-4255414-1-2.html
Done
omniphil said:
I can't get it working consistently on any of the EU roms newer than 8.8.9. I have filed a bug report for it in the standard MIUI forum, if it gets fixed there it should then get fixed in EU.
What you guys can do is register for the MIUI bug forum and then you can Confirm my bug report. The more people that Confirm it the more attention it is going to get so it gets fixed..
Here's a link to my bug report. Please Confirm it.
http://en.miui.com/thread-4255414-1-2.html
Click to expand...
Click to collapse
I have done joined your bug reporting. I hope more people voice their concerns on this topic.
Just to add some info to this... I am on MIUI 9 Global rom 9.6.8.0. I can get Android Auto to work by toggling the USB debugging in Developer settings. It doesn't seem to matter if its on or off, I just have to toggle it and android auto fires right up and connects to the car.
Very weird indeed, there is still some work needed to be done with these roms and Android Auto it seems.
Potential AA solution for Mi Max 3
Hi all - I've just signed up to post this reply, which I hope is helpful to someone at least.
Similar to a number of you, I have struggled to get AA working on the Max 3 (I received my Max 3 last week and it is updated to MIUI 10 Global Stable).
I profess to having no coding/coder/engineering background, but I have solved - with consistency - the lack of compatibility on my Skoda Superb (VAG unit). Where other phones are fine, this wasn't playing nicely.
Essentially, the car would see the phone, but when pressing one of the options on the touch-screen in the car (you choose Android Auto or Mirror Link), it would say that there is an error and to check the device was Mirror Link compatible.
After rebooting/fiddling, I managed to get it to link up once or twice from maybe a dozen tries. What I hadn't done is recorded my process of getting it to work.
Turns out it is pretty simple.
Clearing all apps from the system RAM via the menu button (three lines in MIUI 10, or, swipe up and hold for gestures) makes my Max 3 connect first time to the car without fail. I have read something about apps in the background conflicting with the messages/instructions sent and received, but hey - my layman's solution seems to be doing the trick.
If it works for you, excellent. If not, I apologise and hope a permanent solution comes along! MIUI is a strange beast with some options - some superb (individual data access via 4G and WiFI for example), some really backward (no merging of external SD to internal is criminal!).
jageanke said:
Hi all - I've just signed up to post this reply, which I hope is helpful to someone at least.
Similar to a number of you, I have struggled to get AA working on the Max 3 (I received my Max 3 last week and it is updated to MIUI 10 Global Stable).
I profess to having no coding/coder/engineering background, but I have solved - with consistency - the lack of compatibility on my Skoda Superb (VAG unit). Where other phones are fine, this wasn't playing nicely.
Essentially, the car would see the phone, but when pressing one of the options on the touch-screen in the car (you choose Android Auto or Mirror Link), it would say that there is an error and to check the device was Mirror Link compatible.
After rebooting/fiddling, I managed to get it to link up once or twice from maybe a dozen tries. What I hadn't done is recorded my process of getting it to work.
Turns out it is pretty simple.
Clearing all apps from the system RAM via the menu button (three lines in MIUI 10, or, swipe up and hold for gestures) makes my Max 3 connect first time to the car without fail. I have read something about apps in the background conflicting with the messages/instructions sent and received, but hey - my layman's solution seems to be doing the trick.
If it works for you, excellent. If not, I apologise and hope a permanent solution comes along! MIUI is a strange beast with some options - some superb (individual data access via 4G and WiFI for example), some really backward (no merging of external SD to internal is criminal!).
Click to expand...
Click to collapse
I am glad this thread is getting some attention, hopefully Xiaomi sees it....
I just went out and tried your method and unfortunately it didn't work for me, but I certainly appreciate you adding your workaround to this thread.
The workaround for me is to plug in the USB cable to the phone and then toggle the USB debugging and it connects as soon as I either turn on or off USB debugging. So as usual with these Chinese phones something is running in the background that is looking for Android Auto connections and the task managers on these phones are killing it. (toggling USB debugging must start whatever service is needed and it instantly connects) At least that's my theory anyways
Xiaomi.... Android does not need task killers! Please stop trying to "Optimize Memory", Free ram is totally wasted ram! The ram should be full of cached stuff for optimal performance, LOL
omniphil said:
I am glad this thread is getting some attention, hopefully Xiaomi sees it....
I just went out and tried your method and unfortunately it didn't work for me, but I certainly appreciate you adding your workaround to this thread.
The workaround for me is to plug in the USB cable to the phone and then toggle the USB debugging and it connects as soon as I either turn on or off USB debugging. So as usual with these Chinese phones something is running in the background that is looking for Android Auto connections and the task managers on these phones are killing it. (toggling USB debugging must start whatever service is needed and it instantly connects) At least that's my theory anyways
Xiaomi.... Android does not need task killers! Please stop trying to "Optimize Memory", Free ram is totally wasted ram! The ram should be full of cached stuff for optimal performance, LOL
Click to expand...
Click to collapse
Ah sorry to hear this.
Mine won't stay in USB debug mode anyway, but shame it hasn't sorted for you.
If it's an issue with other applications though, it would be good to figure out which one upsets it being detected right away.
Hi there, this is a cry for help post, since I am going insane trying to solve the Bluetooth connectivity issues between my Mi 5s and my car Bluetooth.
Info:
My phone is a Xiaomi Mi 5s, with unlocked bootloader and a Lineage 15.1 ROM with Gapps and the latest baseband firmware. (8.11.8)
The car system is a Renault Media Nav
The problem:
About 2 months ago my phone started having Bluetooth connection problems to my car without any apparent reason. To be more precise the phone pairs and connects to the multimedia system normally, (even displaying the phone battery and signal status), but there is no sound when playing music or when making calls. Moreover the car's interface fails to synchronize the contacts list, the call log and cannot initiate calls when dialing a number.
To save you the trouble I will numerate the actions I have taken to unsuccessfully solve or at least pinpoint what is causing the problem:
-I have deleted and re-paired both devices on both ends, countless times.
-Tried tweaking Bluetooth developer settings regarding AVCRP versions and sbc/aac codecs.
-I have paired the car with various other phones (Galaxy S4, Huawei P9, LG..) without any issues EXCEPT Xiaomi phones! (Mi 5s, Mi 8, Mi A2 lite)
-My Mi 5s (and Mi 8 and Mi A2 lite) connect to my Sony Bluetooth headset without any problem.
-I deleted WiFi/Bluetooth settings and Bluetooth Midi service Data
-Booted intro safe mode to rule out third party apps
-performed countless factory resets and Full wipes
-Tried different ROMs such as AEX, Pixel experience and MIUI latest Global Developer Rom
-The only circumstances under which the phone-car connection worked flawlessly was AFTER a fresh installation of Lineage os but BEFORE the "Last setup steps" was completed where I think that it updates to the latest Google play services. (Specifically from Play store version 12.1 to 12.7)
-It also worked fine when installing Lineage os WITHOUT Gapps!
Conclusion:
So it looks like the Google Play services update is causing the problem, which explains why the problem appeared our of the blue.
It also seems to affect all the Xiaomi phones I have tried!
Any thoughts? Anyone please?
Update: I managed to narrow down to the fact that everything is working fine until Google play services version 11.7. After the update is completed with the latest 14.7.99 the problem reappears imediately.
If it's Google play services it can only be some sort of security issue. Look in the changelog and see if they say anything about BT permissions etc.
pr0x2 said:
If it's Google play services it can only be some sort of security issue. Look in the changelog and see if they say anything about BT permissions etc.
Click to expand...
Click to collapse
Hi there, thank you for your reply!
I can't be sure it's Google Services, it just seems to be the only logical explanation I came up with, by ruling out everything else I could think of, with the actions I described.
It also seems to affect at least 2 more xiaomi models (Mi 8, and Mi A2 lite) which is quite weird isn't it? Is it possible that a Google Services bug affects various Xiaomi models of different hardware, and ROM? (Linage, MIUI, Android One)
Sorry if this a noob question, but do you mean the Google play services changelog? Because I wasn't able to find one online.
I am currently using an IQOO 9 pro (China version-OriginOS) in Greece. I came across a problem that I can't solve, no matter how hard I've tried: The "personal hotspot" does not work when I have my mobile data on (no wifi). When I have my device on wifi, other devices will recognise, connect and share internet but when ONLY my mobie data are on, other devices can see and connect to the "iqoo 9 pro network" but without internet. Factroy reset and Network Settings reset were in vain. I contacted IQOO support in India but they were not very helpful. I had the same problem with my IQOO 8 pro some time ago but did not bother to try and fix it. (I strongly believe it s a "setting" problem rather than me being SO unlucky to buy two similar phones with the very same (and only) problem.
Any suggestion/input would be most appreciated.
thx.
EDIT:
1) Problem solved Had to do with some Vodafone APN parameters so with a little experimentation and luck I got it right .
2) When I initially got the phone, had a lot of troubles with messages not coming (push notifications also, especially from my bank app, not allowing me to approve a transaction on time etc). With a little search and a lot of help from the topics in this section, I get notifications (messenger for example) faster than my PC, got rid of some Chinese bloatwear, solved the "hotspot" problem and by now, I have an excellent device, very fast, very customisable, working perfectly with other devices (my smartwatch for example), with a great camera, a really good battery (better than Samsung S21 Ultra that I was using 1 month ago). The only tiny problem now is this "Vivo security keyboard" that sometimes comes up (does not allow Google autofill- Google keyboard works fine btw) but is a minor problem, plus the lack of Android Auto witch (for me) is less than minor.
All in all If you give it a little time and effort you might end up with an excellent overall phone, a very premium-feeling-and-performing phone. No more overpriced Sammy Exynos garbage for me.
Apparently, weirdly this phone comes with no always on display OOTB.
Some Xiaomi phones are like that.
This is a serious con for me. I ordered it before knowing this, but it's not big enough an issue to cancel or pay 100€ more for Pro.
Is there a way to somehow enable this?
Does Xiaomi EU have this usually on phones that don't have it in stock MIUI?
I don't have this device but according to this link, there is.
Xiaomi Eu rom adds 'always' option.
https://www.reddit.com/r/PocoPhones/comments/13fo0ix
At Redmi Note 10 pro there was the same problem. But it was fixable by downgrading the com.miui.aod App. I have already tried over 10 different versions, but without success.
You mean you have tried 10 different versions of that app on this phone?
Have you tried disabling miui optimizations in the developer settings?
Apparently this also worked on some xiaomi devices.
People say doing that causes bugs but I had it disabled for the last 4 years and have not noticed anything except slow (but still working) Gmail attachments (yes, it's weird but those are connected, somehow).