Database Users

I still have the August update

Hi,
My phone doesn't detect new security updates. I'm stucked at the August one and the Support says that it's normal.
What can I do?
Thanks!

antonio8909 said:
Hi,
My phone doesn't detect new security updates. I'm stucked at the August one and the Support says that it's normal.
What can I do?
Thanks!
Click to expand...
Click to collapse
Be happy that you have fully working software. Major problems have been introduced in the October Security update, and even more problems are in the Oreo beta. I'd recommend staying on 7.1.1 August.

antonio8909 said:
Hi,
My phone doesn't detect new security updates. I'm stucked at the August one and the Support says that it's normal.
What can I do?
Thanks!
Click to expand...
Click to collapse
It might be that in your region updates aren't available. If you're willing to take the risk, you can try registering for the oreo beta update. Personally I haven't had any issues with my phone, but that's me. You might not be so lucky

redweaver said:
It might be that in your region updates aren't available. If you're willing to take the risk, you can try registering for the oreo beta update. Personally I haven't had any issues with my phone, but that's me. You might not be so lucky
Click to expand...
Click to collapse
I live in Spain and I didn't saw any problems here with updates :/ It's a very strange issue

chancooluk said:
Be happy that you have fully working software. Major problems have been introduced in the October Security update, and even more problems are in the Oreo beta. I'd recommend staying on 7.1.1 August.
Click to expand...
Click to collapse
Problems? I understand that in Oreo beta you can get more bugs but what are the problems with 7.1.2?
Thanks

antonio8909 said:
Problems? I understand that in Oreo beta you can get more bugs but what are the problems with 7.1.2?
Thanks
Click to expand...
Click to collapse
I'm talking specifically about the background tasks bug. Search the forums, it absolutely cripples the phone and requires a reboot twice daily to keep the phone running normally.

chancooluk said:
I'm talking specifically about the background tasks bug. Search the forums, it absolutely cripples the phone and requires a reboot twice daily to keep the phone running normally.
Click to expand...
Click to collapse
But it was going to be fixed in Oreo, right?

antonio8909 said:
But it was going to be fixed in Oreo, right?
Click to expand...
Click to collapse
Unfortunately it isn't fixed in the Oreo beta, neither is the SMS receiving bug (although that can be resolved by installing a third party SMS app). The Oreo beta has also introduced a load of Bluetooth problems (connection issues, poor quality audio, remote buttons not working).
It is currently not known if HMD will actual fix the issues in the final Oreo build.

I have never experienced any of these issues.
One thing I wonder is what if you rolled back to 7.1.1 then upgraded straight to oreo beta (if that's possible)? I'm just wondering if the issue doesn't have something to do with 7.1.2

December images up

I just noticed December's images are up for og pixel xl and pixel

Zehlek said:
I just noticed December's images are up for og pixel xl and pixel
Click to expand...
Click to collapse
Eh Zehlek, I am trying to update from the August Pie build. Do you think just flashing the system.img and vendor.img would work (like it was in the Nexus days)? I can't really be bothered going through the re-rooting .
Thanks.

Anyone who has updated,,,have you noticed anything with the Dec update? Or just another security patch?

Archangel said:
Anyone who has updated,,,have you noticed anything with the Dec update? Or just another security patch?
Click to expand...
Click to collapse
Just the new search bar with the Google Assistant link and drawing program hidden in the Easter Egg.

jaytv said:
Just the new search bar with the Google Assistant link and drawing program hidden in the Easter Egg.
Click to expand...
Click to collapse
I heard for other devices (Pixel 2) the UI (At least on the home screen) has been much more fluid with the updated Pixel launcher. I would agree with this on the Pixel XL too now...I have far less stutters using navigation gestures and swiping right to go to the Discover feed. Good update!

This is really random, but after updating anyone else having an issue with the screen turning off when a right to far left of the screen is performed? Noticed it when I was swiping a word from far right of the screen to far left, and it turns the screen off. Does the same thing outside of the app. Checked the Gestures settings and couldn't find anything relevant. (Wiped data on upgrade) Any suggestions are appreciated!

chinesecooler said:
Eh Zehlek, I am trying to update from the August Pie build. Do you think just flashing the system.img and vendor.img would work (like it was in the Nexus days)? I can't really be bothered going through the re-rooting .
Thanks.
Click to expand...
Click to collapse
I'm not 100% sure I would ask @razorloves he is the expert on this one

chinesecooler said:
Eh Zehlek, I am trying to update from the August Pie build. Do you think just flashing the system.img and vendor.img would work (like it was in the Nexus days)? I can't really be bothered going through the re-rooting .
Thanks.
Click to expand...
Click to collapse
doubt it. you need the kernel too (boot.img). then you'd need to reflash twrp and magisk.
you also need new radio & bootloader img's.
what's so hard about re-rooting? you just have to flash twrp and magisk, right?

razorloves said:
doubt it. you need the kernel too (boot.img). then you'd need to reflash twrp and magisk.
you also need new radio & bootloader img's.
what's so hard about re-rooting? you just have to flash twrp and magisk, right?
Click to expand...
Click to collapse
Yeah figured that out. Initially I just flashed the two and it boot looped. Had to do the lot and reroot. :/

Archangel said:
Anyone who has updated,,,have you noticed anything with the Dec update? Or just another security patch?
Click to expand...
Click to collapse
Before the update, I had to manually enter my apn, but After December update, all my apn automatically work. I noticed better signal reception too. I don't know if it's the update related.

I liked it,
Rebooted after initial setup and fastbooted into twrp...
Installed king kernel 3.16
Installed magisk.
Perfection, battery lasts forever now. 5.5h sot is an daily thing, 3.5-4h if streaming pandora

Magisk & Swiftkey after PIE update

Since updating to PIE ( both 10.0.1.0 and 2.0 versions) SwiftKey keyboard has become abnormally big ( even on Smallest size, it takes more than half the screen)
I noticed that it only happens when the boot.img is patched ( either patched through magisk - or simple boot from fastboot ).
This didn't happen while on Oreo, and doesn't happen on other devices like OP6 with Magisk installed.
Can someone confirm that this problem indeed exists ?
(Below i have attached what the keyboard looks like on default size)

SwiftKey is working fine here on Android 9 (10.0.1.0) and even after december update (10.0.2.0).
ps: Stock version.

Same problem here, sometimes when i reboot the device it becomes normal until the next reboot when it gets big again.
Can you provide me the patched boot.img from 10.0.2.0?

I faced this problem on oreo. Uninstaller it after couple of days installed it again and it stated to work just fine

Ed1ne1 said:
SwiftKey is working fine here on Android 9 (10.0.1.0) and even after december update (10.0.2.0).
ps: Stock version.
Click to expand...
Click to collapse
It works fine when i boot with stock boot.img
Rafaelboxer said:
Same problem here, sometimes when i reboot the device it becomes normal until the next reboot when it gets big again.
Can you provide me the patched boot.img from 10.0.2.0?
Click to expand...
Click to collapse
https://androidfilehost.com/?w=file...0jdbNOp6HOGGVkLrdw077xj2gCGsIEx0vNTgBym_XrmSc
I used this one, but also patched the stock one with magisk. Both same results.
It has never happened to me, it always stays like this
anshmiester78900 said:
I faced this problem on oreo. Uninstaller it after couple of days installed it again and it stated to work just fine
Click to expand...
Click to collapse
Maybe SwiftKey fixed it alongside? I never had this problem on Oreo, atleast since i bought this phone( late September)

Confirmed, same here.

Confirmed this when using patched boot image.. Don't know why but it's ok.. I don't need root anymore

I stopped using swiftkey for the same problem, now I use google keyboard and with the days I feel comfortable.

syncstar32 said:
I stopped using swiftkey for the same problem, now I use google keyboard and with the days I feel comfortable.
Click to expand...
Click to collapse
GBoard is the best alternative indeed, but it still can't come close to SwiftKey after 4 years of learning your patterns

Looks normal to me

Working fine for me.

clarkcant said:
Working fine for me.
Click to expand...
Click to collapse
Which ROM are you using?

I had exactly same problem
Pie (december/2018) + Magisk 18 = Swiftkey is huge
I din't found any solution and uninstalled magisk

On stock ROM with Magisk, I also have it. In CRDroid, there was no problem...

champagne66601 said:
Which ROM are you using?
Click to expand...
Click to collapse
Stock OOS.

Anyone find a solution for this?

bbcastro said:
Anyone find a solution for this?
Click to expand...
Click to collapse
Only using stock boot.img fixes that
Yesterday i happened to reboot my phone while charging ( very rare occasion)
On reboot, SwiftKey bugged itself out again.
Reboots/Clear storage wouldnt help
Finally , i flashed again stock boot.img and it was the only thing that fixed that

Pie update available as of today (18 Jan 2019)

Got the Pie update notice today along with January security patch. My question is for those who, like me, waited until the official notification to update.
With so many here experiencing problems with the previous update(s), it's hard to distinguish which threads are for it, custom, or for the latest Xiaomi update. Did you update to Pie in January? Are there any issues you've noticed with the update? Should I pull the trigger on the update or wait?
Any info is appreciated, as always.
Regards,
KB

I just directly installed January update, migrated from Oreo. Didn't face any issues as of yet.
By the way how do you guys turn on FM Radio?

No data since update.
I did the update earlier today and haven't been able to get mobile data since. Can anybody help me?

Barneyjp18 said:
I did the update earlier today and haven't been able to get mobile data since. Can anybody help me?
Click to expand...
Click to collapse
I downloaded my update with the mobile data and used it since right after. No problem. Wifi seems ok too.

Barneyjp18 said:
I did the update earlier today and haven't been able to get mobile data since. Can anybody help me?
Click to expand...
Click to collapse
That sounds like a serious issue, and one that makes me think I might just wait a bit on this update. Thanks for the feedback, and I hope you get the issue resolved. Where are you located?

KB_Thailand said:
That sounds like a serious issue, and one that makes me think I might just wait a bit on this update. Thanks for the feedback, and I hope you get the issue resolved. Where are you located?
Click to expand...
Click to collapse
I'm am located in Japan. Did the update while connected to wifi on WiFi. I never even questioned it as never had a problem in the 14months I have owned the phone.

Barneyjp18 said:
I'm am located in Japan. Did the update while connected to wifi on WiFi. I never even questioned it as never had a problem in the 14months I have owned the phone.
Click to expand...
Click to collapse
I understand. I've not experienced many of the issues some have with the updates, though the battery issues a few updates ago were driving me crazy. Those seem to be resolved now and I can easily get 2 to 3 days out of a charge. The only reason I hesitated was I read some of the threads from the initial update Xiaomi put out, and was trying to be sure this one was less troublesome before allowing it. I saw a couple of folks complain about the loss of WiFi and Data on the first update, so perhaps all of the initial bugs haven't been squashed. I'm in Thailand, so need it to be as clean as possible.
Again, hope you get the issue resolved. Let us know if you do.

I am from Czech Republic and I can say I don't have any LTE issues, battery is great. No issues with Pie at all.

@KB_Thailand
If you are a big fan of gcam.. Then dont update, else do it.
For me everything is working fine, except gcam focus issue.
Stock camera works though.

ShaikhSiddiky said:
I just directly installed January update, migrated from Oreo. Didn't face any issues as of yet.
By the way how do you guys turn on FM Radio?
Click to expand...
Click to collapse
You need to connect a wired headphone in the 3.5 mm jack, then you will get FM.
Regards

Eshwar123 said:
@KB_Thailand
If you are a big fan of gcam.. Then dont update, else do it.
For me everything is working fine, except gcam focus issue.
Stock camera works though.
Click to expand...
Click to collapse
It's not working even flashing the magisk patch module?

ccalixtro said:
It's not working even flashing the magisk patch module?
Click to expand...
Click to collapse
I don't know about this, coz I'm a non rooted user.
If it works, please share,

Eshwar123 said:
I don't know about this, coz I'm a non rooted user.
If it works, please share,
Click to expand...
Click to collapse
Well it works for me. Just unlock the bootloader, put the phone in fastboot mode, boot twrp cosmicdans from adb, flash magisk and when it boots open magisk and download camera patch for pie. It's really easy but i think when you unlock the bootloader you lose your data so think about it.

KB_Thailand said:
Got the Pie update notice today along with January security patch. My question is for those who, like me, waited until the official notification to update.
Click to expand...
Click to collapse
If you are stock 100% do it, if not hang out a while, no big issues now for stock, very few people on stock have had an issue with the latest Pie, those that do have very simple easily fixed things.
Barneyjp18 said:
I did the update earlier today and haven't been able to get mobile data since. Can anybody help me?
Click to expand...
Click to collapse
Try the last page here, changing the IPv4/IPv6 setting, it fixed it for others who had a problem.
https://forum.xda-developers.com/mi-a1/help

I have also lost my data connection since the update.
Does anyone have any idea on how to fix this problem?
EDIT : It seems that the update deleted the apn configuration. Re-entering it solved the issue.

Based on the positive responses I went ahead and did the update since my A1 is stock. So far so good with no issues I've noticed. Both data and wifi seem to be working properly.
Thanks for the responses!

After updating to pie many of the users including myself face an issue where the mic volume has reduced a lot. Other people can't hear me properly on normal voice calls

ccalixtro said:
Well it works for me. Just unlock the bootloader, put the phone in fastboot mode, boot twrp cosmicdans from adb, flash magisk and when it boots open magisk and download camera patch for pie. It's really easy but i think when you unlock the bootloader you lose your data so think about it.
Click to expand...
Click to collapse
Thank you for confirming that,
After rooting, and installing the magisk patch, can I completely unroot and lock the bootloader, and will the patch still work?
Will unlocking the bootloader also wipe data?
(i thought only locking bootloader will wipe, we can use the vol button trick)
Thanks in advance.

Eshwar123 said:
Thank you for confirming that,
After rooting, and installing the magisk patch, can I completely unroot and lock the bootloader, and will the patch still work?
Will unlocking the bootloader also wipe data?
(i thought only locking bootloader will wipe, we can use the vol button trick)
Thanks in advance.
Click to expand...
Click to collapse
1. Unlocking bootloader wipes data
2. Does your phone contain nuclear weapon key? If no, then i don't see any reason you dont want a unlocked bootloader. (Manufacturer denying warranty for unlocked bootloader is thing of past, MI has no problem with it. Also you can lock phone just before giving it to MI store in any case)
3. As long as you install apps from playstore, i also dont see any problem with a rooted phone either.

.:Addicted:. said:
1. Unlocking bootloader wipes data
2. Does your phone contain nuclear weapon key? If no, then i don't see any reason you dont want a unlocked bootloader. (Manufacturer denying warranty for unlocked bootloader is thing of past, MI has no problem with it. Also you can lock phone just before giving it to MI store in any case)
3. As long as you install apps from playstore, i also dont see any problem with a rooted phone either.
Click to expand...
Click to collapse
I just want to stay stock and receive official updates and with gcam working as like on oreo. That's it Bro.,
That's why i wanted to unroot and keep the BL locked.
Will the vol down key avoid wipe for unlocking BL as well?
And will the patch work after unroot?
Thanks

Beta 5/RC1 of Q on deck!

Beta 5/RC1 of Q is officially in the on-deck circle for registered devices; I'm downloading it now for my 3a. (OTA). The big attraction for me - dark mode changes (I enabled dark mode with the previous beta).

PGHammer said:
Beta 5/RC1 of Q is officially in the on-deck circle for registered devices; I'm downloading it now for my 3a. (OTA). The big attraction for me - dark mode changes (I enabled dark mode with the previous beta).
Click to expand...
Click to collapse
Let us know if it boots without fuss

SketchyStunts said:
Let us know if it boots without fuss
Click to expand...
Click to collapse
Working fine here. My 3a restarted once after first boot but it's working fine now

What Issues?
baddesthad said:
Working fine here. My 3a restarted once after first boot but it's working fine now
Click to expand...
Click to collapse
No issues at all; just one quibble - no dark-mode launch animation (even though systemwide dark mode is still active, as I set it with beta 4). And I'm admitting it's a quibble. (It should be present if you have systemwide dark mode set.)

anyone know how to root on beta5??

jayxiao171735 said:
anyone know how to root on beta5??
Click to expand...
Click to collapse
With the latest Magisk Canary, I guess. Haven't tried it myself because latest Pie security patch works like a charm for my needs.

baddesthad said:
Working fine here. My 3a restarted once after first boot but it's working fine now
Click to expand...
Click to collapse
I would double check you didn't fall back to DP4. A reboot means it might have failed to boot to DP5 and falled back to DP4 slot.

Uzephi said:
I would double check you didn't fall back to DP4. A reboot means it might have failed to boot to DP5 and falled back to DP4 slot.
Click to expand...
Click to collapse
I was on the stock July update (phone is a week old) and this is the first developer preview update I received. The build number I have is below

Where is everyone getting beta 5? I only have beta 4 available.

stevew84 said:
Where is everyone getting beta 5? I only have beta 4 available.
Click to expand...
Click to collapse
OTA here

Uzephi said:
OTA here
Click to expand...
Click to collapse
Are you already on Q4? That update is small.
I'm flashing the June stock image since the July one has an issue with the Q OTA.

stevew84 said:
Are you already on Q4? That update is small.
I'm flashing the June stock image since the July one has an issue with the Q OTA.
Click to expand...
Click to collapse
That's where I screwed up initially. Pie with July security patch... Took OTA beta 4 which had June's patch. This was withing a hour of buying it lol.

SketchyStunts said:
That's where I screwed up initially. Pie with July security patch... Took OTA beta 4 which had June's patch. This was withing a hour of buying it lol.
Click to expand...
Click to collapse
I went to the June image and now there is no Q beta available...even though I'm enrolled in the beta program. Weird. I've had the beta previously.
EDIT: got it. thanks.

stevew84 said:
Are you already on Q4? That update is small.
I'm flashing the June stock image since the July one has an issue with the Q OTA.
Click to expand...
Click to collapse
Yes, I went from Q4 to Q5. Needed a reboot as update was stuck at optimizing apps for over 30 minutes.

OTA in Both Caases
Uzephi said:
Yes, I went from Q4 to Q5. Needed a reboot as update was stuck at optimizing apps for over 30 minutes.
Click to expand...
Click to collapse
Beta 4 (via OTA) from default Pie two days ago, and beta 5/RC1 (from beta 4) today (also via OTA). I don't have the proper cables to connect to my PC (all my cables with the proper end at the PC end, can't connect to my 3a - because they are - at the phone end - USB-B - not USB-C; if I had even a USB-to-USB cable, I would not be in this pickle).

PGHammer said:
Beta 4 (via OTA) from default Pie two days ago, and beta 5/RC1 (from beta 4) today (also via OTA). I don't have the proper cables to connect to my PC (all my cables with the proper end at the PC end, can't connect to my 3a - because they are - at the phone end - USB-B - not USB-C; if I had even a USB-to-USB cable, I would not be in this pickle).
Click to expand...
Click to collapse
So basically you like to live dangerously....I can respect that :good:

Actually.....
SketchyStunts said:
So basically you like to live dangerously....I can respect that :good:
Click to expand...
Click to collapse
I live more dangerously testing Windows (which I have been doing since Windows 95 - the original one). Rather amusingly, I've been more conservative (if not downright chicken) when it comes to the phone side of operations - mostly because I've had to. Remember - until Q, Android beta testing was a lot more closed than the same for Windows. Heck - even with Q, where is the most OPEN portion of the testing program? Easily explained - the Pixels. Every Pixel ever built - from the first one to the current one - can- and could - opt-in to it. Problem - until now, Pixels were chained to a limited set of providers. (In the United States, a grand total of two - Verizon and Google itself (via Fi).) The 3a and 3aXL changed that - as long as you had a nano-SIM, and $479USD (at worst), you could get a Pixel and activate it. I'm not on Verizon - I'm not on a Big Four carrier, either. What carrier am I on? Tracfone - an MVNO. (Tracfone uses the towers of all of the Big Four carriers; with the S7 - the phone my SIM came out of, I used the towers of T-Mobile AKA the Uncarrier.) Since I've had the opportunities, I've paid it back, and paid it forward (when and where possible). The Pixel 3a makes it possible - so why not? However, I don't recommend it due TO that it lets me pay it forward - quite aside from that, the Pixel 3a - merely as a mainstream/midrange user - is the best-used and best-supported such new phone. THAT is why I recommend it.
#teampixel #whatcamera?

xFirefly93 said:
With the latest Magisk Canary, I guess. Haven't tried it myself because latest Pie security patch works like a charm for my needs.
Click to expand...
Click to collapse
sorry, this method seems doesn't work, when I use Magisk canary to create the patched boot img, it said that failed to build....any solutions for that?

jayxiao171735 said:
sorry, this method seems doesn't work, when I use Magisk canary to create the patched boot img, it said that failed to build....any solutions for that?
Click to expand...
Click to collapse
Ask John over at Twitter.

jayxiao171735 said:
sorry, this method seems doesn't work, when I use Magisk canary to create the patched boot img, it said that failed to build....any solutions for that?
Click to expand...
Click to collapse
I posted this in another thread you asked this question in, but I figured it would be good to post here to for the benefit of others.....
I found this on the latest Magisk Canary build thread.
tysj said:
Problem they're having is that it isn't outputting the patched boot.img as it says it is. I'm running to the same issue on my Pixel 3.
EDIT:
Somehow got it to work. Uninstalled Magisk Manager, re-downloaded again from the OP, decided to update Magisk Manager from the app, then tried patching the boot.img again which finally work. Flash the patched_boot in fastboot and all is well.
Click to expand...
Click to collapse
So it sounds like there is so issue with the Magisk Manager - either the user wasn't really on the latest build, or there is some sort of permission issue with writing files, etc. But it seems that reinstalling the manager fixes the issue and you should be able to get Magisk to modify the stock boot.img file as normal.