Database Users

[APP] Samba Filesharing still FCs on S III

Note: I would've added this info to the appropriate thread but as a new user I cannot.
I've got the latest version of the Samba Filesharing app installed on a rooted but otherwise stock Verizon S III and for the record the reported FCs for this app are seen on this phone, even if I am not actually using the app. I suspect it's causing some other WiFi problems while contending for resources in the background (I'll know more once I freeze/uninstall it). It's also reported to cause unexpected traffic even when "disabled" (seen by firewall users), which could be a source of other issues.
The whitelist workaround doesn't help (e.g., enable whitelist with an empty whitelist and then check manual start).
Also, SU doesn't seem to be involved in any way with the app starting in the background... in this testing I'm not even enabling the filesharing function, yet I still get the lag followed by a FC whenever I disable WiFi. Thus the SU notification workaround appears to be irrelevant (it was originally supposed to address the relatively new lag seen when enabling the filesharing function though it doesn't appear to solve that problem either). **
** If you toggle Wifi off and back on in a relatively short time you may not see the FC issue, as it seems to take a few seconds for the app to come back to life in the background after a FC / force stop... it also seems to take longer (around a minute) to restart itself after the latter.
Reading the thread above, it seems that this useful app may unfortunately not be under active development anymore - if it is I hope the issue is resolved eventually, and if not then I hope this information saves others from further headaches. I do like this app, but it doesn't have a true on-demand mode such that when it's disabled it's truly disabled - staying hooked into WiFi whenever running in the background is not good (leading to FCs and other confirmed and unconfirmed side-effects). It's not clear to me why the app starts itself whenever WiFi is turned on but it indeed does that (neither the FC or force-stop leave it dead for long).

[BUG REPORT] LG L Bello D331 - official Lollipop D33120c_00 (CIS region) bug report

Hello to all D331 owners!
For the last couple of weeks, I've been testing the official Lollipop ROM, released for the CIS region (D33120c_00). Similar ROM was also released for TelCel (Mexico) and Avea (Turkey). My phone originally came with D33110f_00 unbranded KitKat ROM (V10f_EUR_XX). The Lollipop ROM was flashed using LG Flash Tool 2014, after which a factory reset was performed.
Here are the bugs I've found so far, and it seems we're dealing here with an unpolished, test ROM. Values in brackets (High, Medium, Low) represent the severity of the problem:
1. [High]: Magnetic field sensor lag. The sensor's polling rate won't go above 15 Hz, which causes reduced framerate in most of the compass apps. Since polling rate in KitKat was well above 50 Hz, this could indicate a major optimization flaw, rendering apps which require precise magnetic sensing useless.
2. [Medium]: Sensors report themselves incorrectly. In various diagnostic apps, sensors report themselves as "MTK [sensor name]". In KitKat, they were correctly reported as "LGE [sensor name]".
3. [Medium]: Apps take way more storage. Actually not a bug, since ART runtime in Lollipop works that way. Nevertheless, it's a good reminder since Smart Cleaning reports 30% storage in use on the first Lollipop boot (it was nearly half that much in KitKat).
4. [Medium]: Play Store lag. This problem is present in KitKat too, but in Lollipop it feels a bit worse. When you scroll up or down the list of paid / free apps (after you select a category), scrolling framerate drops on random spots throughout the list. In landscape orientation, the framerate drops even more.
5. [Low]: Blurry recent apps previews. In the new recent apps list, previews of currently opened apps are a bit blurry. They were perfectly sharp in KitKat. On a rare occasion, some previews would exhibit black horizontal lines.
6. [Low]: Non-standard font in Wi-Fi password field. When a popup window to enter your Wi-Fi credentials appears, the password entry field doesn't feature the standard Roboto font. It features some sort of fixed-length font (similar to Lucida Console on Windows). Bug not present in KitKat.
7. [Low]: Stock Jelly Bean wallpaper on first boot. When you flash the Lollipop ROM, you'll be presented with one of the stock Android wallpapers (which dates back to Jelly Bean). Once you select another wallpaper, you cannot select this one again, as it can't be found in the stock LG wallpaper gallery. In KitKat, you are presented with the default LG wallpaper.
8. [Low]: Phone app recent list leftover. After you finish a call or dial an USSD code, they will suddenly appear in the recent apps list - but not before all other recent apps are swiped away. If you use the "Clear all" button, they won't appear. The correct behavior would be to list them among all other recent apps immediately, not only after all other apps were swept away.
(Note: This list is not finalized, there could be more bugs that are yet to be found.)
To conclude this report, I have a question - is it possible to report these kind of bugs directly to LG technical teams, is there any official procedure? I mean, they have to get aware of bugs somehow - or do they find and correct them on their own, without any kind of user reports?

Sidenote:
The firmware which I'm testing can't be found on DevTester's website (or anywhere else for that matter). DevTester's firmware site is the only real alternative to LG Phone Firmware site. In other words, 99% firmwares from the LG Phone Firmware can also be found on DevTester's website, which is updated daily. This is not the case with the firmware I'm testing, and this could be one more proof I'm dealing with beta or pre-release stuff.
(Disregard this post, the firmware list on those websites are generated by IMEI check and only contain direct links to LG servers.)

6. [Low]: Non-standard font in Wi-Fi password field. When a popup window to enter your Wi-Fi credentials appears, the password entry field doesn't feature the standard Roboto font. It features some sort of fixed-length font (similar to Lucida Console on Windows). Bug not present in KitKat.
Click to expand...
Click to collapse
@TMHKR22 Hi there,
Just to mention that i'm D855 (G3) user here, and the fixed width font on wifi password is still present even in stock marshmallow (was present in lolipop too).

MIUI kills background processes and possible solution

Hi all
I discovered that MIUI very aggressively kills background processes, which are needed for Push functions. Affected apps on my device (now with Global 8.0.3.0, but also with Chinese developer 6.x.x. Haven't tested 7.x.x.) are Touchdown, KIK, Gmail, Threema and others.
Those apps don't seem to have Push correctly working, some apps get messages with several hours delay.
I allowed all those apps to Autostart in the Settings -> Permissions.
There is an option in the Android Developer Options (To enable Developer Options Settings App > About Phone > MIUI Version > Keep on tapping till it is enabled.) called MIUI Optimization, which seems to have an effect on the memory process killing, but maybe also on the Permission functions. After I disabled this option and rebooted, several apps were running, although they weren't in the autostart permitted list. It's possible though, that they were active before the reboot and MIUI restarted them after the reboot.
Source:
https://forum.xda-developers.com/re...de-redmi-note-3-sd-mtk-multi-tasking-t3358433
Turn On MIUI Optimization : This option enables a pleothora of MIUI based settings & optimizations as per the guidelines set by the MIUI developers. This setting can sometimes cause a variety of issues on non-MIUI based apps such as Google Apps & Apps from Google Playstore. Its better to disable if you rely on Google Playstore for apps & services.
With the MIUI Optimization Enabled, some users reported the following issues.
- Cannot set third-party launcher like Nova, Apex or Google Now Launcher.
- Wallpaper cannot be set using in-built options via custom launchers.
- Occasional lags, stutters or freezes while scrolling web-pages & long lists.
- Custom apps set as default restore to default MIUI apps on reboot.
- Cannot set accessibility services on reboot.
- Background apps cannot sync data.
- Music players stop playing after sometime.
- UI Animations are not synced properly.
Click to expand...
Click to collapse
I'm testing now if my mails are correctly delivered again, because that was buggering me the most. This worked fine on my old Sony Z1C and also Huawei Y6 II.
So far it doesn't seem to help though, but I'm testing a bit further.

Thanks!!!

patoberli said:
Hi all
I discovered that MIUI very aggressively kills background processes, which are needed for Push functions. Affected apps on my device (now with Global 8.0.3.0, but also with Chinese developer 6.x.x. Haven't tested 7.x.x.) are Touchdown, KIK, Gmail, Threema and others.
Those apps don't seem to have Push correctly working, some apps get messages with several hours delay.
I allowed all those apps to Autostart in the Settings -> Permissions.
There is an option in the Android Developer Options (To enable Developer Options Settings App > About Phone > MIUI Version > Keep on tapping till it is enabled.) called MIUI Optimization, which seems to have an effect on the memory process killing, but maybe also on the Permission functions. After I disabled this option and rebooted, several apps were running, although they weren't in the autostart permitted list. It's possible though, that they were active before the reboot and MIUI restarted them after the reboot.
Source:
https://forum.xda-developers.com/re...de-redmi-note-3-sd-mtk-multi-tasking-t3358433
I'm testing now if my mails are correctly delivered again, because that was buggering me the most. This worked fine on my old Sony Z1C and also Huawei Y6 II.
So far it doesn't seem to help though, but I'm testing a bit further.
Click to expand...
Click to collapse
You can also use, Push Notification Fixer from Google play. I only had the problem when using chinese rom. After switching to global, the notification a lot better

Go to the security app and inside saving battery settings and uncheck apps you don't want Miui to manage.

Done that now too, although I have already disabled the battery saver. I wonder if this will help a little, at the moment I don't get messages/notifications to my smartwatch, for example.

Hi,
This guide helped me (somehow): http://www.forbes.com/sites/bensin/...ions-on-xiaomis-miui-8-for-real/#1434cfd94e1b.
The 5 steps in short are:
Settings --> Battery & performance --> Manage apps battery usage --> choose apps --> select app that should receive push notifications and set "No restrictions"
Settings --> Permissions --> Autostart --> activate for all apps that should receive notifications
Settings --> Notifications & status bar --> App notifications --> select relevant app and activate "Priority"
In the overview of running apps/app manager lock the relevant apps (swiping down)
Settings --> Additional settings --> Developer options --> Memory optimisation --> set to "Off"
Push notifications now work perfectly on one phone (Redmi 3s with latest stock global rom stable), while i have still some troubles on another one (Mi 5s with latest xiaomi.eu stable). For the later the mail client (k9 mail) does not poll the mailboxes at the defined intervals (while k9 works fine on the redmi). Maybe also a configuration problem of k9, have no idea yet...
Regards,
gp

I have stopped using k9 because of those kind of problems. Now I use Sol Mail

EMJI79 said:
I have stopped using k9 because of those kind of problems. No I use Sol Mail
Click to expand...
Click to collapse
k9 is indeed cumbersome to the extent that you have a lot of settings and you have to apply many of them for each individual account separately. Sometimes less is more...
But once you managed that you can make use of the export/import settings function.
Most important feature for me is that all account settings are kept inside the app and can not be queried by other apps (which would be the case if the info is stored in the android account store).
Never tried Sol Mail so can't tell how this app manages the accounts...

I don't know either.
I choose Sol Mail after I had choose K9 because they offer unified view for received and sent message from every account into one single screen.

EMJI79 said:
Go to the security app and inside saving battery settings and uncheck apps you don't want Miui to manage.
Click to expand...
Click to collapse
patoberli said:
Done that now too, although I have already disabled the battery saver. I wonder if this will help a little, at the moment I don't get messages/notifications to my smartwatch, for example.
Click to expand...
Click to collapse
Ok, can now confirms that it indeed helped Not perfect, but much better.

Android Q Beta - All in details

All you want to know in one place about
Android Q
General info: https://android-developers.googleblog.com/2019/03/introducing-android-q-beta.html | https://www.google.com/android/beta
Opt In/ Opt Out your Pixel device(s): https://www.google.com/android/beta#devices Enable OTA Updates (You will get the beta updates like usual updates)
System images: https://developer.android.com/preview/download
Official Reddit forum from Google: https://www.reddit.com/r/android_beta/ for Bug reporting and solutions
If you manually flashed Android Q on your device by downloading the image from developer.android.com, you won’t receive updates automatically unless that device is also opted-in to the Android Beta Program for Pixel on the Opt In URL.
Using OPT out and returning to Pie the device will be facotry reseted:
You will not be able to unenroll and revert back to a lower public release version of Android without first wiping all locally saved data on your device. You may also encounter issues restoring a backup.
You will NOT receive separate monthly security updates while on a beta build.
Update working fine from Pie. Data and settings are remain.
Rooting: https://www.xda-developers.com/root-android-q-beta-google-pixel-pixel-2/
Magisk: https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Hide back Button: https://www.xda-developers.com/android-q-gestures-back-button/
System seems stable. Call, SMS, Network, Bluetooth, Audio working fine.
Problems / Bugs
- Laggy Camera on all Pixel devices. (I can confirm It is MUCH slower than Pie. First pic about 4-9 sec)
- Slow(er) HDR+ picture processing. New feature: Dynamic depth format for photos
- Google is deprecating the Android Beam API used to share files with NFC
- Now playing not working (For me)
- Edit button on screenshot notification NOT working
- No options to block numbers in dialer or anywhere else
- No info about the charging estimated time
- Built in Screen recording in broken: FIX: https://www.androidpolice.com/2019/...t-in-screen-recording-but-its-broken-for-now/
- Android Q's Dark Mode Breaks Google Photos
2019. March 15.: Live wallpapers with cloud updates are broken FC in every second reported by many users
- Not working apps: https://www.reddit.com/r/android_beta/wiki/index: Some banking apps will not work in this beta, but Google Pay will work!
General App Compatibility Issues
Google Apps
Android System Webview (Beta users should leave the program)
Files by Google
3rd Party
AirWatch Hub
Boxer
Chase
Citrix Secure Hub
Evernote
Fate Grand Order
Firefox (non-nightly builds)
Huntington Bank
LastPass (app loads, major functionality issues)
Lloyds Bank
LinkedIn
Plex
PokemonGo
Samsung Galaxy Wear App
Syncthong
TELLO
Trials Frontier
WeChat
ZMODO Security Cameras
Other Notable Issues with Apps
Android Messages - MMS photo quality degraded
Google Photos & Dark Mode (Cannot read any text, logos are hidden)
MapMyRun will not work in the background (Q Location Permission Changes)
Improvements:
- "Always on" redesigned: https://9to5google.com/2019/03/13/android-q-aod-music/ Lift to wake, and double tap now ignores Always on display and get you directly to lock screen (if any) (This is no improvement for me)
- Much faster finger print reading
- Much faster face recognition
- Play Music lock screen wallpaper redesigned (It is just broken for me)
- New guesture: https://9to5google.com/2019/03/13/android-q-improved-multitasking-gesture/
New Features:
○ System-wide Dark Mode:
Solution 1:
- Use the Battery Saver to Enable Dark Mode.
Solution 2:
- Use ADB to Enable Dark Mode in Android Q
Code:
adb shell settings put secure ui_night_mode 2
- Use ADB to Disable Dark Mode in Android Q
Code:
adb shell settings put secure ui_night_mode 1
- Use ADB to AUTO Dark Mode in Android Q
Code:
adb shell settings put secure ui_night_mode 0
Solution 3:
Before the update set the device theme to Dark in the developer options.
The option removed in Q so you will not be able to modify it after the update.
○ Device Theming:
In the end of the Developer Settings you can find the options:
- Color
- Font
- Icon Shape​
Only a few settings. You can play around​
○ Time to read
In Settings -> Accessibility You can set the notifications timeout​
○ Sharing Shortcuts
New sharing options and redisgned interface​
○ Wi-Fi sharing via QR Code
Android Q now allows you to share your current Wi-Fi connection simply via a QR code​
○ Feature Flags in developer options
https://www.reddit.com/r/android_beta/comments/b0xmio/feature_flags_hidden_options_and_what_they_do/
https://9to5google.com/2019/03/14/android-q-beta-1-feature-flags/
Desktop mode:
https://www.xda-developers.com/android-q-desktop-mode/
More from Google:
Foldables and innovative new screens
More privacy protections in Android Q
Giving users more control over location
Settings Panels
Improved peer-to-peer and internet connectivity
Wi-Fi performance mode
Camera, media, graphics
Dynamic depth format for photos
New audio and video codecs
Native MIDI API
ANGLE on Vulkan​Neural Networks API 1.2
ART performance
More to come...

eBENdre said:
All you want to know in one place about
Android Q
Problems / Bugs
- Laggy Camera on all Pixel devices. (I can confirm It is MUCH slower than Pie. First pic about 4-9 sec)
- Slow(er) HDR+ picture processing. New feature: Dynamic depth format for photos
- Google is deprecating the Android Beam API used to share files with NFC
- Now playing not working (For me)
- Edit button on screenshot notification NOT working
- No options to block numbers in dialer or anywhere else
- No info about the charging estimated time
- Built in Screen recording in broken: FIX: https://www.androidpolice.com/2019/...t-in-screen-recording-but-its-broken-for-now/
- Android Q's Dark Mode Breaks Google Photos
.
Click to expand...
Click to collapse
Just to help out a bit, if possible:
Camera seems to be fine on my P2XL - though I have not enabled any HDR+ or raw settings.
Now Playing is working for me, grabbed the theme song off the show I was watching last night.
Markup "edit" button can be fixed. Clear data in markup, open photos and use markup from within that; you should get a permission request. (simply going into permissions on the markup app and enabling any/all may work as well, but is untested)
In dialer/recents, tap the number, and choose block from the drop down menu. I am in the beta for the Google phone app - so that may be part of it. Dirty flash may also affect this.
Clarification only: Photos is broken in dark-mode, but only in that all options dialogs/drop-downs are white text on white background. Other than that, you can still browse photos/albums, etc.
For clarity: My device is the Pixel 2 XL and Q was installed via factory image with full wipe (no dirty flash), and I did not restore from any backups.

Camera is fine for me on 2xl. Nothing different. HDR+ works as normal so does raw DNG.

Mr Patchy Patch said:
Camera is fine for me on 2xl. Nothing different. HDR+ works as normal so does raw DNG.
Click to expand...
Click to collapse
Thank you. I'm on dirty upgrade. I will reset my phone soon. I will test it again.

eBENdre said:
Thank you. I'm on dirty upgrade. I will reset my phone soon. I will test it again.
Click to expand...
Click to collapse
You should check 9to5 Google they have some more adb commands for stuff like the different clocks for aod and how to use swipe left to go back

kevtrysmoddin said:
You should check 9to5 Google they have some more adb commands for stuff like the different clocks for aod and how to use swipe left to go back
Click to expand...
Click to collapse
thanks, I will add more later. Swipe left already on the list btw

Much faster fingerprint?
It already feels almost instant in Pie, what can they improve?

eBENdre said:
Problems / Bugs
- Now playing not working (For me)
- No info about the charging estimated time
- Built in Screen recording in broken: FIX: https://www.androidpolice.com/2019/...t-in-screen-recording-but-its-broken-for-now/
- Android Q's Dark Mode Breaks Google Photos
Click to expand...
Click to collapse
Now playing is working for me - just not displaying on the lock screen. I just got home form a birthday party, and every song the DJ played is in my NP history;
In addition to the charging time estimate, the estimate in the pull down notification area is completely off base compared to the estimated time left in Settings --> Battery;
My built in screen recording works for me, and has worked since I enabled it from the Features flags in Developer Options;
No issues with Google Photos with dark Mode. Caveat: I had dark mode enabled in Pie, and took the Q DP1 OTA over that Pie install;
I found that there is a microphone icon at the top left when selecting Panorama photo mode that I never saw before (was that introduced with Q DP1, or just a very recent Google Camera update?)
I've not noticed a discernible slowdown in the Camera app (and I always use HDR+ / Night sight for my photos), but I have noticed that when I try to view a picture / video, particularly like an MMS in Messages / Google Voice, the phone is extremely slow and laggy.

@eBENdre just got xl 2 ,prerooted,one question,if i install Q 1 will it owerwrite twrp magisk also,will there be problems maybe? Thanks
For years used htc,this is new for me.

Boskoel03 said:
@eBENdre just got xl 2 ,prerooted,one question,if i install Q 1 will it owerwrite twrp magisk also,will there be problems maybe? Thanks
For years used htc,this is new for me.
Click to expand...
Click to collapse
Yes, it will overwrite twrp and magisk.
There are always potential problems with any update to beta builds, however, many are running Q without issues. Best advice I can give is to familiarize yourself with fastboot commands, since you'll need to install twrp again, and read, read, and read again all of the information in the Q threads so you know what to do and expect :good:

Badger50 said:
Yes, it will overwrite twrp and magisk.
There are always potential problems with any update to beta builds, however, many are running Q without issues. Best advice I can give is to familiarize yourself with fastboot commands, since you'll need to install twrp again, and read, read, and read again all of the information in the Q threads so you know what to do and expect :good:
Click to expand...
Click to collapse
Huge thanks mate,and there is problem for me,as keybord not working on laptop...

You'll probably need access to a different computer - or else need to buy a cheap USB KB to use, because use of a separate computer / laptop is pretty much essential to get this working (root + Q, not to mention installing TWRP by using fastboot boot to boot TWRP, then installing TWRP from inside the booted TWRP).

Badger50 said:
Yes, it will overwrite twrp and magisk.
There are always potential problems with any update to beta builds, however, many are running Q without issues. Best advice I can give is to familiarize yourself with fastboot commands, since you'll need to install twrp again, and read, read, and read again all of the information in the Q threads so you know what to do and expect :good:
Click to expand...
Click to collapse
Did it,through twrp,lost it off course,now one more question,will i be able to recive next build,like regular OTA,altough my bootloader is unlocked? Thanks once again....

Boskoel03 said:
Did it,through twrp,lost it off course,now one more question,will i be able to recive next build,like regular OTA,altough my bootloader is unlocked? Thanks once again....
Click to expand...
Click to collapse
You should get the next update fine, provided your on stock recovery without root. I don't run betas personally, but my info comes from reading about others that do. As with anything android...YMMV :good::laugh:

Android Q Beta Experience
I've been on Android Q beta for almost 3 weeks now. It is used as a daily driver since I have only the one Pixel 2. I flashed the new image myself using TWRP rather than opt into the beta with Google. Other than a problem with now playing not always showing up on the screen and a slight delay when I go to the Favorites page in Phone app everything seems to work alright. I am getting roughly the same battery life as with Android Pie. Oh, and my banking app (ICICI Bank, India) is not working. It doesn't send an SMS to activate the app. I thought this might be as the phone number is shown as unknown. I understand that Vodafone in India does not show the phone number in the SIM information in Settings. I have activated dark mode and even photos and camera app work without a hitch. I have rooted with Magisk (Canary channel) and that is working without any problem.

OTOH, I've also been on Q since the day it came out (my birthday, coincidentally - love being an Ides of March baby lol).
I've had some issues crop up here and there, but nothing really serious. I was on Pie, rooted, and used the uninstall routine inside of Magisk to de-root my Taimen before taking Q, and then rooted it again with the (then latest) canary build.
What I'm hoping is that the Magisk procedure to de-root the device, take the OTA, and then before rebooting, applying the patched boot.img to the new partition will work, the same as if you're rooted on Pie and get an OTA.
Time will tell.

My notifications is coming like this only.. is this a bug?
or the clock is missing?
My device is not rooted. I'm not using any module or theme.

Clock missing - have you rebooted?

johnlgalt said:
Clock missing - have you rebooted?
Click to expand...
Click to collapse
Yes I have. Atleast 2-3 times.

Wonder if it is System UI Tuner related?
You could give this a shot and see if the System UI is set to hide the clock, though the last time I actually tried to hide the clock, it didn't leave that space there....
---------- Post added at 04:13 PM ---------- Previous post was at 03:48 PM ----------
New warning posted on the Android Beta page https://www.google.com/android/beta#devices
Caution: The current release contains significant behavior changes that affect apps in particular. The latest updates around isolated storage may cause issues with apps that access photos, videos, media, or other files stored on your device, such as when browsing or sharing in social media apps.
Click to expand...
Click to collapse
I'm installing the update now, let's see just how differently this works on my Taimen.

Android 10 for MI A2 has arrived :)

just checked update is there
1283.7mb to download . i didn't test it yet good luck

Portugal??

Arrived in Italy.
Camera Api 2 not supported

I haven't test it in full (obviously) but there are already some annoying glitches...

emmc bug is still present

n0b0dy666 said:
I haven't test it in full (obviously) but there are already some annoying glitches...
Click to expand...
Click to collapse
No problems for me so far. Loving it

n0b0dy666 said:
I haven't test it in full (obviously) but there are already some annoying glitches...
Click to expand...
Click to collapse
What kind of glitches?

on mine i can't remove the top most notification on settings (customize your a2 phone with wallpapers, blabla)
L.E. and the notification led was broken for a bit, fixed itself after a few restarts.

No boot loop (I was afraid)
It took about 5 minutes to restart, after password took about 3 minutes with the message your phone is starting, and it restarted again, then everything is fine.
*Camera API2 not enabled, (Though this would be it but...Xiaomi)
*the downloads issue from past update is gone
*camera seems fine,
*there's this app called "Device Personalization Services" which just crashes, it can be unistalled though
*persistance Custumize your Mi A2 message at the top of settings (can't dissmiss it?)
Everything else seems fine so far.

Gestures in third party launchers don't work

So I've installed it, here are some important points worth mentioning :
1- no camera 2 api
2- no ARCore
3- The device personalisation services which is the app responsible for app suggestions in app menu and smart replies etc. is now visible via app menu and it shouldn't
4- Google play music is now force installed, you could uninstall it in pie and Oreo
5- remember how we complained about xiaomi not adopting to new Google material design guide lines by making dialog corners edgy ? Well it became seriously worse, everything is pointy and I don't like it
6- Google Assistant gestures are not working
7- all new features are working pretty well including new gestures and system wide dark mode and new theming options in developer options, tho unlike pixels system wide dark mode doesn't apply at boot screen
8- I suspect there's again some noises coming from camera, better check that yourself
9- there's an annoying banner in settings about some suggestions which you can't get rid of , possibly because of Device Personalisation Services app being faulty
10- if you have 2 users set on your phone you can't see the user switcher until you turn it on and off in settings
11- The security patch is still from December so expect another OTA in near days before next month which possibly includes bug fixes and January patch
12- some quick step ( default launcher ) features aren't working, you wanna guess which ? You're damn right, the ones related to Device Personalisation Services.
13- a lot of lagging, well there's nothing really there to say about it, is it? Expect some annoying lags.
14- the trusted face option is removed from smart Lock so you can't unlock your device with face recognition at the moment.

What about disabling Device Personalisation app?

i'll add a few bits:
- no longer says charging quickly (i hope it's just a display thing and still fastcharges)
clear cache on the device personalization services and it should stop crashing on load (still doesnt open, but wont see the force close)

Bluetooth is not working to me
Anyone can confirm?

carlosm182 said:
Bluetooth is not working to me
Anyone can confirm?
Click to expand...
Click to collapse
nope, working here

iluvatrix said:
What about disabling Device Personalisation app?
Click to expand...
Click to collapse
Hi, I don't think you should disable it, well you can uninstall it but that would be pointless. Device Personalization Services is an app which was present in OS since Android pie and it has always been hidden as a part of system apps, now due to a bug it's not working and it's being shown in apps list like any other app

Audio
Multimedia audio doesn't seem to work yet the other audio channels seem fine, anyone else?

LonelyGlitch said:
So I've installed it, here are some important points worth mentioning :
1- no camera 2 api
2- no ARCore
3- The device personalisation services which is the app responsible for app suggestions in app menu and smart replies etc. is now visible via app menu and it shouldn't
4- Google play music is now force installed, you could uninstall it in pie and Oreo
5- remember how we complained about xiaomi not adopting to new Google material design guide lines by making dialog corners edgy ? Well it became seriously worse, everything is pointy and I don't like it
6- Google Assistant gestures are not working
7- all new features are working pretty well including new gestures and system wide dark mode and new theming options in developer options, tho unlike pixels system wide dark mode doesn't apply at boot screen
8- I suspect there's again some noises coming from camera, better check that yourself
9- there's an annoying banner in settings about some suggestions which you can't get rid of , possibly because of Device Personalisation Services app being faulty
10- if you have 2 users set on your phone you can't see the user switcher until you turn it on and off in settings
11- The security patch is still from December so expect another OTA in near days before next month which possibly includes bug fixes and January patch
12- some quick step ( default launcher ) features aren't working, you wanna guess which ? You're damn right, the ones related to Device Personalisation Services.
13- a lot of lagging, well there's nothing really there to say about it, is it? Expect some annoying lags.
14- the trusted face option is removed from smart Lock so you can't unlock your device with face recognition at the moment.
Click to expand...
Click to collapse
1- requires device with pie release(ours oreo)
2- arcore with sdm660 ? hell no
14- it is completely removed in ten. not xiaomi's fault

x_avier said:
No boot loop (I was afraid)
It took about 5 minutes to restart, after password took about 3 minutes with the message your phone is starting, and it restarted again, then everything is fine.
*Camera API2 not enabled, (Though this would be it but...Xiaomi)
*the downloads issue from past update is gone
*camera seems fine,
*there's this app called "Device Personalization Services" which just crashes, it can be unistalled though
*persistance Custumize your Mi A2 message at the top of settings (can't dissmiss it)
Everything else seems fine so far.
Click to expand...
Click to collapse
it is necessary to perform hard reset?

jordiop said:
Gestures in third party launchers don't work
Click to expand...
Click to collapse
That's an android thing, not Mi A2 thing. It's like that on every phone with android q