Related
About CyanogenMod
CyanogenMod is a free, community built, aftermarket firmware distribution of Android which is designed to increase security, performance, reliability and customization over stock Android.
About nightly builds
Nightly builds are automatically compiled builds of the latest CyanogenMod source from github. These builds are not officially supported. If you find bugs or issues please discuss here. Do not submit bug reports for nightly builds on the CyanogenMod issue tracker.
How to install
Preparation
Ensure you have a working copy of ADB for your PC. A simple search should find versions for all major operating systems.
If you are running "stock" (ColorOS), the first thing you will need is a recovery. There are many recoveries available. The most popular ones are CWM and TWRP. Please consult other threads to find and install a suitable recovery.
Once you have a suitable recovery, download from download.cyanogenmod.org to your PC.
If you wish to have Google applications available such as the Play Store, download a current copy of gapps. CM recommended gapps are shown at wiki.cyanogenmod.org.
Reboot your phone into recovery.
Installation
If you wish to save any of your current data, back it up. Details vary by recovery. The app "Titanium Backup" is also popular to backup and restore your installed apps.
Wipe your internal data. Again, details vary by recovery. The option is usually called "wipe data / factory reset" or something similar. This is absolutely critical and required if you are coming from a stock ROM or a different third party ROM. Note! If you are coming from a previous nightly build of CM11, you can often get away with keeping your data. But if you encounter any issues, please wipe data and retry.
Find an option in your recovery that looks like "Install from sideload" or Install from ADB" and select it. On your PC, run "adb sideload cm-11-yyyymmdd-NIGHTLY-find7.zip". ADB should show a progress indicator. When the file has completed uploading, it should install. Repeat with your gapps package if desired.
Reboot your phone. The first boot after install can take a few minutes (usually no more than 5 minutes) so be patient.
Enjoy!
tdm
Systems Engineer
Cyanogen, Inc.
Known Issues
* Find7s: Screen may not wake when phone is hot.
This is apparently an interaction between the thermal throttling code and the video/gpu driver. It has been reproduced and we are working on a fix.
* Find7s: Notification light sometimes misbehaves.
We are working on a fix.
* Find7a: Battery sometimes drains too quickly.
This issue is under investigation. We do not have a repro or a fix at this point.
* Find7a: Mic doesn't work while on speakerphone.
This issue is under investigation. We do not have a repro or a fix at this point.
@tdm,
thanks for this, could you please let me know what the bugs for this are?
About time we hade a thread for CM in here!
Thanx and good work @tdm.
Would like to know what Recovery we must use. CWM or can we also use TWRP? What GAPPS - BANKS or PA GAPPS. Also when u use the package with google camera it breaks the camera functionality!
Answered my own question:
TWRP and CWM both work good.
Use PA GAPPS with NO! Google Camera
Cm works pretty well for me. When the Android OS is not draining my battery I can easily hold it out for over 24h, hope it gets fixed soon.
Is there something I can do to help in helping fixing this problem?
Besides I've had it a few times now that when I unlock my screen that my flashlight turns on, very weird, but only had it since today/latest nightly.
Willthor said:
I've had it a few times now that when I unlock my screen that my flashlight turns on, very weird, but only had it since today/latest nightly.
Click to expand...
Click to collapse
That has happened to me many times. The screen gestures are very sensitive. This is a firmware/hardware issue. I believe we plan to use the proximity sensor to mitigate the issue, not sure if that has been committed already or not.
Will CM include this following?
*50 MP Camera Snapper like on ColorOS
*Breathing Notifications (not Blinking Notifications like implemented now on CM).
Also there is a problem when you charge via VOOC Rapid Charger when the device is turned off, the output process on the screen will be an endless loop of Oppo logo->then Charging Indicator->Oppo Logo-> Charging Indicator again and just repeatedly same process.
hulicow said:
Will CM include this following?
*50 MP Camera Snapper like on ColorOS
*Breathing Notifications (not Blinking Notifications like implemented now on CM).
Also there is a problem when you charge via VOOC Rapid Charger when the device is turned off, the output process on the screen will be an endless loop of Oppo logo->then Charging Indicator->Oppo Logo-> Charging Indicator again and just repeatedly same process.
Click to expand...
Click to collapse
I believe Oppo is reserving 50mp for their own ROM.
Don't know about breathing notifications.
I'll try to look into off mode charging.
I'm on 07/15 nightly and the only bug I have is mic on speaker calls.
This is my daily driver now.
Anyone knows of a camera app that can take slow shutter photos like on colorOS camera?(about the only feature I miss from colorOS)
I don't need the 50mp camera thing. But proper hdr and more reliable auto focus would be nice. Up get a lot of out of focus pics on CM compared to ColorOS.
And a fix for the busted HLS streaming in kitKat would be sweet.
One more thing...a solid newb proof fix for the stupid partition layout would be awesome.
Finally...Auto brightness is borked. It's an issue on every ROM I've tried. Really frustrating.
Sent from my X9006 using XDA Premium 4 mobile app
tdm said:
Known Issues
* Find7s: Screen may not wake when phone is hot.
This is apparently an interaction between the thermal throttling code and the video/gpu driver. It has been reproduced and we are working on a fix.
* Find7s: Notification light sometimes misbehaves.
We are working on a fix.
* Find7a: Battery sometimes drains too quickly.
This issue is under investigation. We do not have a repro or a fix at this point.
* Find7a: Mic doesn't work while on speakerphone.
This issue is under investigation. We do not have a repro or a fix at this point.
Click to expand...
Click to collapse
Is the battery draining issue still there?
Juiceboy125 said:
Is the battery draining issue still there?
Click to expand...
Click to collapse
No battery drain for me at least.
But I can't seem to take a proper panorama photo, not even with OnePlus camera.
Other than those few annoying bugs it's the smoothest experience I 've ever had.
gamotom said:
No battery drain for me at least.
But I can't seem to take a proper panorama photo, not even with OnePlus camera.
Other than those few annoying bugs it's the smoothest experience I 've ever had.
Click to expand...
Click to collapse
Well, that's good to hear. I've had this rom for awhile and I just wanted to make sure. But, if you mind me asking, how much screen time do you usually get? I get about 5 and a half average.
Juiceboy125 said:
Well, that's good to hear. I've had this rom for awhile and I just wanted to make sure. But, if you mind me asking, how much screen time do you usually get? I get about 5 and a half average.
Click to expand...
Click to collapse
I get about 1,5 days of use with 4 and a half SOT. But keep in mind that I like my display bright so I've tweaked up autobrightness values.
Has anyone here experienced screen going unresponsive after a bit of browsing on chrome. No issues using Mozilla Firefox though!
Re battery drain: the battery drain happens in standby. Then the battery looses ~1.5-2% per hour, meaning almost 15-20% overnight. It should be only a few instead.
To investigate this, can you guys with no battery drain let us know which modem/firmware you guys are using?
Thanks!
Using the last few nightlies, I've noticed that the gestures no longer work with the screen off. Specifically, double tap to wake and drawing a circle to start the camera.
Not sure if it's something I did on my end or a more common issue
nihir said:
Using the last few nightlies, I've noticed that the gestures no longer work with the screen off. Specifically, double tap to wake and drawing a circle to start the camera.
Not sure if it's something I did on my end or a more common issue
Click to expand...
Click to collapse
double tap 2 wake works with flashing last 3 nightlys!
silasje1 said:
double tap 2 wake works with flashing last 3 nightlys!
Click to expand...
Click to collapse
Hmm. Must be something I've done. Thanks!
Hello guys!
So I have been trying out the Android P and I can say its gonna be a "monster" good change imo.
However, I have some issues and just want to see if it just me or everybody else. Basically what the issue is that I usually have no sound on meaning - There is 3 sounds -
1 turned on sound,
2. only vibration
3. No sound & vibration
so I usually do have the number 3 on usually but then I tried to use 1 and 2 and I figured out that Snapchat notification either does any sound or vibration while I tried facebook, whatsapp and everything else and there is no issue with it, Comes sounds and vibration.
The issue seems only to be on Snapchat, I tried to use the Beta snapchat and the original, I also reinstalled it aswell but nothing to go.
How is it going for you?
Bump!
I've been having the same issue since ever using Android P. Assumed it was just simply that Snapchat hasn't updated their stuff on their end to work with Android P properly in that area, but I don't know.
Ozzy0708 said:
I've been having the same issue since ever using Android P. Assumed it was just simply that Snapchat hasn't updated their stuff on their end to work with Android P properly in that area, but I don't know.
Click to expand...
Click to collapse
Oh there we go! Then im not the only one I believe
Hey guys ,
I've noticed that my auto brightness it's not working at all. I need to swipe it to change it.. either I'm in a dark room or outdoors.
Anyone experiencing the same problem ? I triple checked , auto brightness is on but just not working .
Anyone knows any fix for it ?
If it was working in the previous betas, it is probably not a hardware failure (Unless you unleashed havoc on the device during this beta). While it may be that the latest beta has brightness issues, in which case try re-flashing the firmware, Android P has introduced some weird Ai-Controlled Auto-Brightness, which could be the cause. I'm not sure if the new auto-brightness is working yet, so that could also be that cause. Take all of this with a pinch of salt though, I'm new to Pixel, but not new to android development
Jucacarvalho1987 said:
Hey guys ,
I've noticed that my auto brightness it's not working at all. I need to swipe it to change it.. either I'm in a dark room or outdoors.
Anyone experiencing the same problem ? I triple checked , auto brightness is on but just not working .
Anyone knows any fix for it ?
Click to expand...
Click to collapse
I just checked with mine and it's working. Try (re)flashing the factory image.
it's also work on my phone without a problem
Having slight issues with mine as well. I noticed it randomly will turn itself off at some point during the day. I seem to always have to re-enable it everyday.
-The story -
So I bought my mi mix 2 off swappa used and it was pretty much mint condition. When I received it it was on latest miui 11 global locked bootloader no root.. All worked fine for about three weeks. I ended up buying windows 10, again, which made me throw up a lil in my mouth. I did this so that I could use the mi unlock tool to unlock my bootloader. The java Linux tool no longer works to unlock if you use Linux so rn kinda forced to buy Windows. So I unlocked bootloader and then installed twrp and made a backup like I do with every phone since Android began. I then flashed HAVOC 3.1 using latest twrp recovery. I quickly realized my speaker decided to stop working in the earpiece soon after that. I ran some tests using apps and the earpiece speaker works, but NOT in a call. :crying:
-The problem I'm having in detail-
When I make a call to anyone they can hear me but I can hear NOTHING at all. Not low volume, but no sound whatsoever. If I switch to speaker phone however I can hear them and they can hear me fine. The top speaker that doesn't work during calls works when I tested it but refuses to work while on any call.
So naturally I Google searched the world for a few days hoping to find a fix. Then I thought maybe it was my recovery, maybe it was firmware I used, maybe it's a rom bug...etc...etc... I never proved it to be any of the things I thought it could be. I've installed other roms and I get the same thing with them. I've tried other firmware and same deal. I've disabled encryption, used magisk and not used magisk... Anyway, you get the picture.
Would anyone happen to know something I can do to fix this? I read some people touch up where top speaker is during a call ..That didn't work. ? I did 29 reboots and that did nothing. I checked the ear piece and cleaned what I could and that did nothing. I've wiped several different ways and used orange fox recovery and twrp different versions of both and that did nothing.
Please someone who's smart chime in and tell me I'm dumb and all I have to do is xyz and I can hear again from the earpiece on calls. Can it be a defective speaker? If so why does the speaker work fine on anything but NOT when making a call? Can it still be a defective speaker?
I did read TONS of reports of sound issues on Xiaomi devices across the board. That didn't make me smile much.. Anyway any advice or thoughts or anything would sure be extremely helpful and I'd forever be grateful. I hope you all have a good day and your speaker never acts stupid like mine is on my phone.
flash713 said:
-The story -
So I bought my mi mix 2 off swappa used and it was pretty much mint condition. When I received it it was on latest miui 11 global locked bootloader no root.. All worked fine for about three weeks. I ended up buying windows 10, again, which made me throw up a lil in my mouth. I did this so that I could use the mi unlock tool to unlock my bootloader. The java Linux tool no longer works to unlock if you use Linux so rn kinda forced to buy Windows. So I unlocked bootloader and then installed twrp and made a backup like I do with every phone since Android began. I then flashed HAVOC 3.1 using latest twrp recovery. I quickly realized my speaker decided to stop working in the earpiece soon after that. I ran some tests using apps and the earpiece speaker works, but NOT in a call. :crying:
-The problem I'm having in detail-
When I make a call to anyone they can hear me but I can hear NOTHING at all. Not low volume, but no sound whatsoever. If I switch to speaker phone however I can hear them and they can hear me fine. The top speaker that doesn't work during calls works when I tested it but refuses to work while on any call.
So naturally I Google searched the world for a few days hoping to find a fix. Then I thought maybe it was my recovery, maybe it was firmware I used, maybe it's a rom bug...etc...etc... I never proved it to be any of the things I thought it could be. I've installed other roms and I get the same thing with them. I've tried other firmware and same deal. I've disabled encryption, used magisk and not used magisk... Anyway, you get the picture.
Would anyone happen to know something I can do to fix this? I read some people touch up where top speaker is during a call ..That didn't work. I did 29 reboots and that did nothing. I checked the ear piece and cleaned what I could and that did nothing. I've wiped several different ways and used orange fox recovery and twrp different versions of both and that did nothing.
Please someone who's smart chime in and tell me I'm dumb and all I have to do is xyz and I can hear again from the earpiece on calls. Can it be a defective speaker? If so why does the speaker work fine on anything but NOT when making a call? Can it still be a defective speaker?
I did read TONS of reports of sound issues on Xiaomi devices across the board. That didn't make me smile much.. Anyway any advice or thoughts or anything would sure be extremely helpful and I'd forever be grateful. I hope you all have a good day and your speaker never acts stupid like mine is on my phone.
Click to expand...
Click to collapse
Try the latest version of Havoc 3.0, not 3.1. my device also has an unspeakable error on the call of messenger with most of the android 10 rom, i can hear the voice of the other side, but they can't hear me, after trying a lot of android 10 rom, i found only havoc os 3.0 is not making that error. Though it's not your fault, I think you should try it.
quan2032 said:
Try the latest version of Havoc 3.0, not 3.1. my device also has an unspeakable error on the call of messenger with most of the android 10 rom, i can hear the voice of the other side, but they can't hear me, after trying a lot of android 10 rom, i found only havoc os 3.0 is not making that error. Though it's not your fault, I think you should try it.
Click to expand...
Click to collapse
Mine is I can't hear them but they can bear me. What the hell is going on. Hahaha! If all else fails I'm going to get a new top receiver speaker put in at a shop close by. It does appear that many Xiaomi devices have had sound issues and have had speakers replaced. If you search on YouTube Xiaomi no sound on call or speaker replacement you'll see MANY videos on "how to." Quite a few videos specifically for mi mix 2. They should let us upgrade at least to the mix 2s for free.
I'll try 3.0 havoc but I've flashed around on Android 10 and 9 and problem hasn't gone away. Still zero sound on my end on calls but all speakers work doing anything else. Appreciate the recommendation. Thanks for commenting. Later today's ill flash 3.0 and see what's up. Then I may pull a few kernels from other roms and switch em out with whatever I'm on and see if I can't get something going that way.
I will also post a log of me on the phone talking and maybe someone can see something that's wrong... Hope so anyway..
flash713 said:
-The story -
So I bought my mi mix 2 off swappa used and it was pretty much mint condition. When I received it it was on latest miui 11 global locked bootloader no root.. All worked fine for about three weeks. I ended up buying windows 10, again, which made me throw up a lil in my mouth. I did this so that I could use the mi unlock tool to unlock my bootloader. The java Linux tool no longer works to unlock if you use Linux so rn kinda forced to buy Windows. So I unlocked bootloader and then installed twrp and made a backup like I do with every phone since Android began. I then flashed HAVOC 3.1 using latest twrp recovery. I quickly realized my speaker decided to stop working in the earpiece soon after that. I ran some tests using apps and the earpiece speaker works, but NOT in a call. :crying:
-The problem I'm having in detail-
When I make a call to anyone they can hear me but I can hear NOTHING at all. Not low volume, but no sound whatsoever. If I switch to speaker phone however I can hear them and they can hear me fine. The top speaker that doesn't work during calls works when I tested it but refuses to work while on any call.
So naturally I Google searched the world for a few days hoping to find a fix. Then I thought maybe it was my recovery, maybe it was firmware I used, maybe it's a rom bug...etc...etc... I never proved it to be any of the things I thought it could be. I've installed other roms and I get the same thing with them. I've tried other firmware and same deal. I've disabled encryption, used magisk and not used magisk... Anyway, you get the picture.
Would anyone happen to know something I can do to fix this? I read some people touch up where top speaker is during a call ..That didn't work. I did 29 reboots and that did nothing. I checked the ear piece and cleaned what I could and that did nothing. I've wiped several different ways and used orange fox recovery and twrp different versions of both and that did nothing.
Please someone who's smart chime in and tell me I'm dumb and all I have to do is xyz and I can hear again from the earpiece on calls. Can it be a defective speaker? If so why does the speaker work fine on anything but NOT when making a call? Can it still be a defective speaker?
I did read TONS of reports of sound issues on Xiaomi devices across the board. That didn't make me smile much.. Anyway any advice or thoughts or anything would sure be extremely helpful and I'd forever be grateful. I hope you all have a good day and your speaker never acts stupid like mine is on my phone.
Click to expand...
Click to collapse
Clearing the phone app cache data help me to overcome this but this problem in 3.1 occurs more often..
Sinchanwa said:
Clearing the phone app cache data help me to overcome this but this problem in 3.1 occurs more often..
Click to expand...
Click to collapse
Appreciate you commenting and man do I wish it was the phone app cache. I have to get a speaker replacement. Going to look into it tomorrow and get an estimates. I love my phone! Hope they don't try and tell me some insane cost for it and I sure hope that it gets fixed right. I'm going to a top rated place to get it fixed so fingers crossed. [emoji51]
Sent from my Ocean using XDA-Developers Legacy app
flash713 said:
Appreciate you commenting and man do I wish it was the phone app cache. I have to get a speaker replacement. Going to look into it tomorrow and get an estimates. I love my phone! Hope they don't try and tell me some insane cost for it and I sure hope that it gets fixed right. I'm going to a top rated place to get it fixed so fingers crossed. [emoji51]
Sent from my Ocean using XDA-Developers Legacy app
Click to expand...
Click to collapse
Hey there just want to know is your problem solved?
Sinchanwa said:
Hey there just want to know is your problem solved?
Click to expand...
Click to collapse
Not yet. What's up?
I flashed Bootleggers 5.0 about 12 hours ago and setup NanoDroid for the first time on this device. Super cool!!
Sent from my chiron using XDA-Developers Legacy app
flash713 said:
Not yet. What's up?
I flashed Bootleggers 5.0 about 12 hours ago and setup NanoDroid for the first time on this device. Super cool!!
Sent from my chiron using XDA-Developers Legacy app
Click to expand...
Click to collapse
Fine buddy..
So just for info i clean flashed havoc 3.1 and every thing is rocking if want to return on havoc plz clean flash it..:good::victory:
Sinchanwa said:
Fine buddy..
So just for info i clean flashed havoc 3.1 and every thing is rocking if want to return on havoc plz clean flash it..:good::victory:
Click to expand...
Click to collapse
I never thought that my sound issue was related to havoc in any way I am almost positive its a broken speaker. Looks as though that type of thing happens often on this device and other xiaomi devices. Google search receiver speaker replacement really fast and watch how many things show up about it. Its all over. I'm going to get a replacement. Using my moto g7 power rn as my main phone so I can have conversations and hear on my end. I always clean flash everything I flash. I never fail to wipe data, system, cache, delik cache on any install.
I have the same problem after installing Havoc 3.1. I tried updating the firmware...and rolling back the firmware to 9.5.16 to no avail
flash713 said:
-The story -
So I bought my mi mix 2 off swappa used and it was pretty much mint condition. When I received it it was on latest miui 11 global locked bootloader no root.. All worked fine for about three weeks. I ended up buying windows 10, again, which made me throw up a lil in my mouth. I did this so that I could use the mi unlock tool to unlock my bootloader. The java Linux tool no longer works to unlock if you use Linux so rn kinda forced to buy Windows. So I unlocked bootloader and then installed twrp and made a backup like I do with every phone since Android began. I then flashed HAVOC 3.1 using latest twrp recovery. I quickly realized my speaker decided to stop working in the earpiece soon after that. I ran some tests using apps and the earpiece speaker works, but NOT in a call. :crying:
-The problem I'm having in detail-
When I make a call to anyone they can hear me but I can hear NOTHING at all. Not low volume, but no sound whatsoever. If I switch to speaker phone however I can hear them and they can hear me fine. The top speaker that doesn't work during calls works when I tested it but refuses to work while on any call.
So naturally I Google searched the world for a few days hoping to find a fix. Then I thought maybe it was my recovery, maybe it was firmware I used, maybe it's a rom bug...etc...etc... I never proved it to be any of the things I thought it could be. I've installed other roms and I get the same thing with them. I've tried other firmware and same deal. I've disabled encryption, used magisk and not used magisk... Anyway, you get the picture.
Would anyone happen to know something I can do to fix this? I read some people touch up where top speaker is during a call ..That didn't work. I did 29 reboots and that did nothing. I checked the ear piece and cleaned what I could and that did nothing. I've wiped several different ways and used orange fox recovery and twrp different versions of both and that did nothing.
Please someone who's smart chime in and tell me I'm dumb and all I have to do is xyz and I can hear again from the earpiece on calls. Can it be a defective speaker? If so why does the speaker work fine on anything but NOT when making a call? Can it still be a defective speaker?
I did read TONS of reports of sound issues on Xiaomi devices across the board. That didn't make me smile much.. Anyway any advice or thoughts or anything would sure be extremely helpful and I'd forever be grateful. I hope you all have a good day and your speaker never acts stupid like mine is on my phone.
Click to expand...
Click to collapse
r_nally said:
I have the same problem after installing Havoc 3.1. I tried updating the firmware...and rolling back the firmware to 9.5.16 to no avail
Click to expand...
Click to collapse
This is just too strange. So maybe my issue does have something to do with installing Havoc 3.1. That was the first rom I flashed after I unlocked my bootloader and speaker worked fine on latest MIUI Global rom before... I wonder if it's possible to break a speaker due to a rom installation? I've never heard of that before. I thought surely it was just the rom and was a bug or a firmware problem. I flashed all kinda firmwares afterwards in latest twrp and also sideloaded a few to see if maybe something wasn't right with recovery and like you say it did not change anything at all. I still get zero sound on my receiver speaker while on a call.
I'm going to try a few more things and see if it does anything. If I find a fix or something that allows me to hear anything at all out of my end on receiver speaker I'll most definitely add it here in a post and to the op. Seems like there would be more people than us if it had something to do with Havoc... Idk. Appreciate your information. I hope we can get this fixed soon. I never even hardly used my phone when the speaker worked. ? I bought it used off swappa and about two weeks later unlocked and flashed Havoc and no sound during calls on my end.
Did you flash magisk also? Maybe that caused the problem...
I'm using Google phone but have also tried the stock Android phone as well as a couple of different versions of firmware. If no solution emerges I'm going to disassemble the phone and see if the earpiece has lost connection
r_nally said:
Did you flash magisk also? Maybe that caused the problem...
I'm using Google phone but have also tried the stock Android phone as well as a couple of different versions of firmware. If no solution emerges I'm going to disassemble the phone and see if the earpiece has lost connection
Click to expand...
Click to collapse
I used an app off Google play store to test speakers and my receiver speaker works but refuses to work during a call on my end. It did have sound come through loud and clear when I ran the tests I did when it first happened. I've flashed using magisk stable, canary, formatted data, used different firmwares, everything know to mankind and searched around and tried several things online and nothing. I've been trying to boot the Android 10 GSIs to see if that makes any difference but have had no luck using the same vendor and boot everyone used on pie GSIs so I snatched some from different roms and still no luck on GSIs that are Android 10. Lemme find link to test all i used and I'll return and post a link. Brb
Sent from my OnePlus5 using XDA Labs
You should add your findings to the havoc thread...if there are 2 people with the exact same problem maybe the developers will take notice and investigate
r_nally said:
You should add your findings to the havoc thread...if there are 2 people with the exact same problem maybe the developers will take notice and investigate
Click to expand...
Click to collapse
I doubt it and I did make a post there a while back about it. There are many others there ok that thread who reported sound issues and I wanted to confirm what for sure caused it before I put the blame all on a rom... The speakers on this device have had issues MANY times based on all the reports i read all over the internet. But if I can confirm exactly what it is I'll dang sure be very open about it online and let the world know in hopes that if it was something I did maybe someone else won't and I can somehow prevent it. But I did make a post there when it occurred. Search my username on the thread and you'll see it.
When you set a ringtone does sound come from your top speaker? On my device it does. Just curious. See if you can hear any sound selecting different ringtones. ?
Sent from my Mi MIX 2 using XDA Labs
I did find some info about pixel users who had this problem, in that case the problem was caused by file association issues with the phone app and Google play services. Some people were able to fix by removing the permissions of Google play services. I tried this approach but many of the permissions cannot be disabled
r_nally said:
I did find some info about pixel users who had this problem, in that case the problem was caused by file association issues with the phone app and Google play services. Some people were able to fix by removing the permissions of Google play services. I tried this approach but many of the permissions cannot be disabled
Click to expand...
Click to collapse
I'm going to clean flash now after I do a backup and I'll install havoc and NanoDroid which eliminates Googles hold on all our devices. Once I get all setup I'll run some tests and see if maybe this solves it.
NanoDroid: https://forum.xda-developers.com/showthread.php?t=3584928
[MODULE/SYSTEM] NanoDroid 22.5.1.20200102 (microG, pseudo-debloat, F-Droid + apps)
No difference
r_nally said:
I did find some info about pixel users who had this problem, in that case the problem was caused by file association issues with the phone app and Google play services. Some people were able to fix by removing the permissions of Google play services. I tried this approach but many of the permissions cannot be disabled
Click to expand...
Click to collapse
On my other device , Moto G7 Power see the 8th post here: https://forum.xda-developers.com/g7-power/development/rom-havoc-os-3-2-t4058987
This time I haven't had it occur on G7 Power but when I saw that guys post I had a flash back. :/
I suspect FW issue. Started not using top speaker after SW update. 10.0.6 When I receive a call and press the volume button, the 'earpiece' icon bar appear. I suspect the phone switch the sound to the 'earpiece' even if there is no earpiece. I even switched Bluetooth off, and still happens. The phone thinks there is a earpiece/headset connected even if there is none. I think Xiaomi Mi devs should post a solution or update. The issue is wide spread.
[edit 17Jul20]
OK, it happened again today. No sound from top speaker when making or receiving calls. Had to switch to speaker phone. Then I cleared the 'Contact and dialer' app cache memory. (And for good measure the other caller and dailer apps also. TOP SPEAKER CAME ALIVE AGAIN!! So I am pretty sure its a bug/memory issue.
What I did: Long press the dailer icon - tap on App info - press 'Clear data' icon and select to clear chache memory.
ToBadX2 said:
I suspect FW issue. Started not using top speaker after SW update. 10.0.6 When I receive a call and press the volume button, the 'earpiece' icon bar appear. I suspect the phone switch the sound to the 'earpiece' even if there is no earpiece. I even switched Bluetooth off, and still happens. The phone thinks there is a earpiece/headset connected even if there is none. I think Xiaomi Mi devs should post a solution or update. The issue is wide spread. - Christo
Click to expand...
Click to collapse
What's crazy is this happened on my device just after I wiped data, system cache and flashed HAVOC which was the first rom that I flashed when I got this device. And I flashed my firmware and it did nothing at all. I'm getting a another speaker from eBay this week. They're only like $3 US. Gonna replace it and see what happens. ?
Hello, I just received MIUI 11.0.2.0 based on Android 10 Stable, so I'm wondering if it is safe to update, I'm afraid that after updating the battery will drain faster as it usually happens, do you have any info about this?
HELLO!! I update my RN8P to android 10.0.2.0 QGGEUXM and the battery is very good as the android 9 :good: don't be Afraid ?
jimkan said:
HELLO!! I update my RN8P to android 10.0.2.0 QGGEUXM and the battery is very good as the android 9 :good: don't be Afraid
Click to expand...
Click to collapse
Update just showed up, is it worth? any audio improvement?
Update and don't be afraid ...?
jimkan said:
HELLO!! I update my RN8P to android 10.0.2.0 QGGEUXM and the battery is very good as the android 9 :good: don't be Afraid
Click to expand...
Click to collapse
After the upgrade the phone cannot connect anymore with the Bluetooth of my Ford C-Max (2011, it cannot be updated and I cannot update the car yet).
Is it happening to anyone else?
jimkan said:
HELLO!! I update my RN8P to android 10.0.2.0 QGGEUXM and the battery is very good as the android 9 :good: don't be Afraid ?
Click to expand...
Click to collapse
Well I have worse battery live on Android 10.
Something keeps phone awake and drain battery.
I have about 1 or 2 hours less SOT.
Looking for solution. ?
I ended up upgrading, at first, my phone was lagging when scrolling in any app, and the battery was somehow draining a bit faster but I managed to fix it.
Try this if you have a related problem.
-Go into developer settings
-Scroll almost to the button
-Disable MIUI optimization
-Reboot
-Enable MIUI optimization
-Reboot
Also, the permission of most of my apps got lost, like access to the microphone, storage, phone... so I had to re-enable them manually because they were "blocked".
For those experiencing problems, it's probably worth doing a full wipe. I tend to find its needed after as version update of Android.
I did a wipe and haven't encountered problems as of yet. Bluetooth, apps and battery all fine for me.
Kev23 said:
For those experiencing problems, it's probably worth doing a full wipe. I tend to find its needed after as version update of Android.
I did a wipe and haven't encountered problems as of yet. Bluetooth, apps and battery all fine for me.
Click to expand...
Click to collapse
Did a full wipe after the android 10 update and for now batterylife shortened for me. Hopefully after a few charges it will be better again.
gee2012 said:
Did a full wipe after the android 10 update and for now batterylife shortened for me. Hopefully after a few charges it will be better again.
Click to expand...
Click to collapse
You can do that also for fix battery drain...
[MIUI with Tom #8] FIX battery Drain in MIUI - after OTA or after reset to factory settings! https://c.mi.com/thread-2834067-1-0.html?t=1583590560499
littleleaf said:
After the upgrade the phone cannot connect anymore with the Bluetooth of my Ford C-Max (2011, it cannot be updated and I cannot update the car yet).
Is it happening to anyone else?
Click to expand...
Click to collapse
I didn't get much feedback so I suppose it isn't a very popular issue. However, I've a solution to share for the annoying problem.
After doing a full wipe of the phone the issue was still present and I was still facing connection problems.
So I enabled the developers options menu and started to play with Bluetooth hidden settings.
At first I downgraded the AVRCP version from the default 1.4 version to 1.3 but it was not working, so I tried 1.5 (same issue) and 1.6. This version was slightly better... The car was authenticating and showing the Bluetooth audio codec in a small icon beneath the device name (Ford Audio -> SBC) but the connection was not stable and dropping. So I changed the default audio codec and I set SBC.
Everything started to work well and I was able to make several hands free call without issues anymore.
I hope it helps whoever could have similar issues.
Angelo
littleleaf said:
I didn't get much feedback so I suppose it isn't a very popular issue. However, I've a solution to share for the annoying problem.
After doing a full wipe of the phone the issue was still present and I was still facing connection problems.
So I enabled the developers options menu and started to play with Bluetooth hidden settings.
At first I downgraded the AVRCP version from the default 1.4 version to 1.3 but it was not working, so I tried 1.5 (same issue) and 1.6. This version was slightly better... The car was authenticating and showing the Bluetooth audio codec in a small icon beneath the device name (Ford Audio -> SBC) but the connection was not stable and dropping. So I changed the default audio codec and I set SBC.
Everything started to work well and I was able to make several hands free call without issues anymore.
I hope it helps whoever could have similar issues.
Angelo
Click to expand...
Click to collapse
Today I discovered that settings changed in the developer menu are not persistent and don't survive to a phone reboot. So every time I get in the car I've to repeat settings.
This is quite annoying, any solutions other than waiting for another software update?
Another alternative would be changing the car, but it's more expensive than buying another mobile phone.
Danchibald said:
You can do that also for fix battery drain...
[MIUI with Tom #8] FIX battery Drain in MIUI - after OTA or after reset to factory settings! https://c.mi.com/thread-2834067-1-0.html?t=1583590560499
Click to expand...
Click to collapse
Tried this, still seeing high Android OS drain
gee2012 said:
Did a full wipe after the android 10 update and for now batterylife shortened for me. Hopefully after a few charges it will be better again.
Click to expand...
Click to collapse
Think you are right on the battery. Mine has settled down and not as good as before
I think after few cycles of charging it will be better...
littleleaf said:
After the upgrade the phone cannot connect anymore with the Bluetooth of my Ford C-Max (2011, it cannot be updated and I cannot update the car yet).
Is it happening to anyone else?
Click to expand...
Click to collapse
Me too...
I've got a Ford Focus with Sync 1.1, and have got issues with bluetooth. First of all, my car can't recognize signal level and i've got problem making calls and closing calls...
ScanaX said:
Me too...
I've got a Ford Focus with Sync 1.1, and have got issues with bluetooth. First of all, my car can't recognize signal level and i've got problem making calls and closing calls...
Click to expand...
Click to collapse
Changing profiles in the developer menu is not helping... I was able to make a couple of calls, no more. Connection is continuously dropping.
Full wipe was not a solution. Before the upgrade I never had a disconnection.
I also tested a couple of Bluetooth profiles apps, including Android Auto, but no luck.
I think we need a fix ASAP.
Is there an official support site where to make complaints regarding this update?
Ever since I updated to 11.0.3.0PGGEUXM I've been unable to use one of my wallet apps (bbva wallet), and am afraid something else breaks if I update; has anyone from Mexico updated and been able to use it again, along with citibanamex pay?
littleleaf said:
Changing profiles in the developer menu is not helping... I was able to make a couple of calls, no more. Connection is continuously dropping.
Full wipe was not a solution. Before the upgrade I never had a disconnection.
I also tested a couple of Bluetooth profiles apps, including Android Auto, but no luck.
I think we need a fix ASAP.
Is there an official support site where to make complaints regarding this update?
Click to expand...
Click to collapse
I'm opening a ticket reporting this issue with my phone...
I hope It will work
After 20 days I decided to downgrade back to MIUI V11.0.3.0PGGEUXM based on android 9, the only thing I liked about android 10 was the dynamic MAC address but it didn't compensate the high battery drain from the Android System, with up to 9-10 hours of CPU usage and about 6-6:30 hours of Screen-on time. I will test how many hours of SOT I have now.