I understood echo was corrected in cm14 10/11 official nightly.
I am still suffering that badly, or did I misunderstood the fix?
Sorry!
Maybe a clean flash is needed, not sure though...
But the fix was definitely merged in the 10/11 build, https://review.cyanogenmod.org/#/c/170189.
1337jay said:
Maybe a clean flash is needed, not sure though...
But the fix was definitely merged in the 10/11 build, https://review.cyanogenmod.org/#/c/170189.
Click to expand...
Click to collapse
I did a clean flash & test it, no luck
Also the same, when restore my data from backup with TWRP... As expected.
What I mean is people in the other end hearing bad echo.
mjkoira said:
I did a clean flash & test it, no luck
Also the same, when restore my data from backup with TWRP... As expected.
What I mean is people in the other end hearing bad echo.
Click to expand...
Click to collapse
I just tried in my car thru Bluetooh system.
It´s working fine there, no echo.
1337jay said:
Maybe a clean flash is needed, not sure though...
But the fix was definitely merged in the 10/11 build, https://review.cyanogenmod.org/#/c/170189.
Click to expand...
Click to collapse
I believe that fix corrected the problem of zero audio coming through in calls, which happened after the official build was out.
Sent from my ONEPLUS A3000 using Tapatalk
1337jay said:
Maybe a clean flash is needed, not sure though...
But the fix was definitely merged in the 10/11 build, https://review.cyanogenmod.org/#/c/170189.
Click to expand...
Click to collapse
I'm still getting echo in 11/11 build
The problem still persists in the 11/11 build, but it's only when using the speakerphone.
Sent from my ONEPLUS A3000 using Tapatalk
I just read about someone having no echo without flashing Gapps, then after flashing Gapps he had echo. Could be Gapps issue?
Sent from my OnePlus3 using XDA Labs
Doesn't appear to be. I'm on an unofficial 11/17 from https://nyyu.tk/cm/ (got impatient awhile back), with pico gapps but I also tried "Banks" when cm14/14.1 wasn't official yet. My location/service provider are T-Mobile USA close to Seattle, WA. My OP3 was purchased in mid-June, model A3000, current baseband on firmware 3.5.5 ".0.c1.9.2-00004-M8996FAAAANAZM-1".
Every couple days when I update I wipe the cache, dalvik, and system partitions, then reboot twrp prior to installing the updated CM and pico gapps. When I'm on firmware 3.2.7 it's less than when I'm on firmware 3.5.5. I have tried bringing my phone back to almost complete stock (thanks to the unbrick guide), then tested gapps/no gapps, 3.2.7/3.5.5 firmwares, different versions of twrp, clean/dirty flashes, official/unofficial builds.
When in Bluetooth it's fine, wired gaming headset it was reduced until a certain distance from caller (one room away), headset audio was low echo but speakerphone was so bad the caller had to hang up it was starting to cause a reverb.
Related
Latest update: 2016-10-27 To view a changelog, you can visit http://www.cmxlog.com/13/quark/ for a rough idea up to the build date.
Hi all. I was able to compile this stock build of CM 13.0 thanks to the efforts/hard works of Skrilax_CZ, baybutcher27, the folks who created Resurrection Rom Remix, and those over at CyanogenMod. It takes some minor features from Resurrection Rom apparently (i.e. notification light, some tiny performance/battery tweaks, and the ability to install Motorola apps). It is otherwise stock CM 13 and I use this daily. I and the other authors/devs assume no responsibility if you damage your device somehow.
Please don't feel pressured to update any more often than you wish .
Notes:
In order to make my calling work for Verizon, I had to go under Settings->Cellular networks->Preferred network type, and select LTE/CDMA (not LTE/GSM/UMTS). I assume GSM users should be fine with the defaults.
My recommendations to install:
Install TWRP 3.0.2 if you haven't already: http://forum.xda-developers.com/mot...recovery-twrp-2-8-7-0-touch-recovery-t3180308
Perform a backup of your current system/ROM (not really needed if just flashing a newer version).
Perform a factory reset/wipe (if coming from another ROM). If not coming from another ROM, still safest to do a dalvik/art cache reset.
Install the .zip
Install the appropriate google apps (http://opengapps.org/ , ARM, 6.0). I would think nano or micro is best.
(Optional) Install a custom kernel. The best at the time of this writing are at:
http://forum.xda-developers.com/moto-maxx/development/kernel-bhb27-kernel-t3207526 (CM-NX-RR-M builds for Marshmallow)
The latest is here: https://www.androidfilehost.com/?w=files&flid=50122
Wipe dalvik/art cache if you install another kernel.
Reboot and enjoy
Kernel Adiutor is very good for performance/power saving adjustments:
https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor
If you are using bhb27 kernels, then you should use his version of Kernel Adiutor:
https://www.androidfilehost.com/?w=files&flid=48767
Here is the link to the latest ROM on the hosting website:
[2016-10-27]https://www.androidfilehost.com/?fid=457095661767104611
Previous Builds:
https://www.androidfilehost.com/?w=files&flid=52716&sort_by=date&sort_dir=DESC
I'll be back to post updates fairly regularly (~every 1-2 weeks), but I also work full time in addition to being a Dad (those of you who are know how that is ) and won't really be able to response to PMs very well. The sources I used can be found under the post on XDA here at http://forum.xda-developers.com/moto-maxx/development/rom-resurrection-remix-t3316232 (device, vendor, and kernel trees). Thanks and God bless.
I just flash this version and its absolutely amazing.
Good job devs!
Bugs I noticed:
-Settings for LED doesn't work.
-Android Auto says is not a supported device.
-Quick Charge 2.0 doesn't seems to work.
-Phone gets really hot when charging.
-...
I have been tempted to flash this all day, but I love how smooth my phone has been on resurrection remix and I enjoy the extra customizations it has. I'm eagerly awaiting the next resurrection remix build for all the latest git changes
emi.guego said:
Bugs I noticed:
-Settings for LED doesn't work.
-Android Auto says is not a supported device.
-Quick Charge 2.0 doesn't seems to work.
-Phone gets really hot when charging.
-...
Click to expand...
Click to collapse
That's a bummer with some of those bugs. Hopefully those will be taken care of soon and I'll be able to sync and rebuild. Did all of these happen to be with the stock kernel, or did you happen to flash another (like baybutchers)? I've seen a few specific to the tiles, but I dont have an Android Auto system to check against. Also, if they are working (or some) in resurrection then I could possibly try to patch this.
calsurferpunk said:
That's a bummer with some of those bugs. Hopefully those will be taken care of soon and I'll be able to sync and rebuild. Did all of these happen to be with the stock kernel, or did you happen to flash another (like baybutchers)? I've seen a few specific to the tiles, but I dont have an Android Auto system to check against. Also, if they are working (or some) in resurrection then I could possibly try to patch this.
Click to expand...
Click to collapse
I don't know exactly, I installed it by downloading the zip and gapps to my PC and used the ADB sideload, before that I was using the last nightly of CM12.1. I did that and I didn't loose my info (either way I did a TWRP backup of everything, except cache previously), so I think it was the CM kernel. When I installed for the first time CM I flashed also the zip and gapps, if that way the stock kernel is changed with the CM kernel I think I'm using CM kernel.
emi.guego said:
I don't know exactly, I installed it by downloading the zip and gapps to my PC and used the ADB sideload, before that I was using the last nightly of CM12.1. I did that and I didn't loose my info (either way I did a TWRP backup of everything, except cache previously), so I think it was the CM kernel. When I installed for the first time CM I flashed also the zip and gapps, if that way the stock kernel is changed with the CM kernel I think I'm using CM kernel.
Click to expand...
Click to collapse
Yeah that sounds like the stock cm kernel then if you didn't flash anything like that separately. I don't know if it would help, but you could always try the other kernel I posted about and see if Android Auto works (would have to restore your backup if you didn't want to keep it). It just depends how much you care and if it's worth staying with the ROM to you. There's obviously bound to be some bugs, but I enjoy using a lean version of the latest and greatest system. Thanks for the feedback .
Installed it 2h ago, everything is running fine so far.
This is smoother than the old cm and than rr too. I'm impressed!
I'm using Bhb Kernel.
My phone is turbo charging, led is working...
No bugs for me.
Nice job, mate! I'm glad we got a new cyanogenmod that we can have updates. Keep strong!
Enviado de meu Moto MAXX usando Tapatalk
thanks,
hope bat drain @ standby will be best from rom's i tested.
somebody can advice what app use to get best standby time? im using Purify but i think it doesnt help much. also on mostly rom'z even when battery mode is set to eco that doesnt help much
Maro' said:
thanks,
hope bat drain @ standby will be best from rom's i tested.
somebody can advice what app use to get best standby time? im using Purify but i think it doesnt help much. also on mostly rom'z even when battery mode is set to eco that doesnt help much
Click to expand...
Click to collapse
I've just been going under the built in privacy guard and setting advanced permissions to where apps I don't need to start at boot are denied, in addition to also denying a lot of them from being allowed to keep the device awake. I get very little battery drain in standby this way. If the cell signal is too weak though, it's really hard to prevent extra drain as it over compensates to get a good signal.
Updated ROM to CyanogenMod 13 changes as of March 24.
calsurferpunk said:
Updated ROM to changes as of March 24.
Click to expand...
Click to collapse
Changelog?
Debuffer said:
Changelog?
Click to expand...
Click to collapse
It's a little hard to say since there is a lot and I am just syncing to the main CyanogenMod 13 repository. However, this is a good link if you go by the date and something similar (such as the Nexus 6 which shares a lot of hardware).
http://www.cmxlog.com/13/shamu/
This may be a dumb question but does this have VoLTE enabled and working(Verizon user)? Since it is CyanogenMod based I assume not but just waned to ask.
calsurferpunk, can you fix wifi on XT1254 with stock Brasil 1225's 6.0.1 ROM? CM12.1 and CM13 detect Moto Maxx and Droid Turbo radio very good!
*GPS*
working for U guys? For me not (BB kernel, location: Europe)
soccertolive said:
This may be a dumb question but does this have VoLTE enabled and working(Verizon user)? Since it is CyanogenMod based I assume not but just waned to ask.
Click to expand...
Click to collapse
Your assumption is correct. I don't believe this has ever worked with CyanogenMod. I'm on Verizon and haven't seen it.
Maro' said:
*GPS*
working for U guys? For me not (BB kernel, location: Europe)
Click to expand...
Click to collapse
I had this problem on other ROMs as well until I restored the original manufacturer ROM, set GPS to device only, verified it worked, then flashed the new ROM. You might have to do the same here. I believe it's been a long ongoing bug with CyanogenMod (and probably others).
pretty thx for the cm13,did it have ambient display?
I am downloading this at work right now. It is slow and will take me a couple to download.
While it is dl'g, I have a question about wiping. Do I still need to do a factory reset if I am coming from a marshmallow cm13 RR rom?Baybutchers?
Also, I have not been able to get my GPS to work properly. In your post #17, you referred to original manufacturer rom. Where can I get this rom to set the gps? I do have computerfreek's room saved as a backup if I could use it? I don't have easy access to a computer to do a fastboot.
Thx.
Sent from my DROID Turbo using Tapatalk
Wait, ROM was updated to day 24?
im having the worst time ever, i flash the latest nightly of cm13 and the gapps from the gapps.org site, open_gapps-arm-6.0-nano-20160327 and i get crashes when CM boots now and google services isnt working. ive tried the clearing data, cache, rebooting, etc and its still giving errors. im not exactly new a this (been using CM off and on since CM7 on htc evo) and have had most nexus devices. ive tried using different versions of twrp, 2.8.7, 2.8.6, 3.0.0.0, 3.0.0.1 nothing is working as it should. what am i doing wrong
I'm currently in the same predicament. I've tried using diffent gapps that i've seen some forums users suggest. I've had no resolution.
93zx7 said:
I'm currently in the same predicament. I've tried using diffent gapps that i've seen some forums users suggest. I've had no resolution.
Click to expand...
Click to collapse
This is partially a CM issue, which should be fixed and merged into nightlies by now, and partly related to opengapps. A few weeks ago, opengapps commited some code that dealt with cm setup wizard, to ill effects, then, they changed pre-odex, and broke their packages for CM...
http://forum.xda-developers.com/android/help/qa-gapps-android-5-1-5-0-4-4-t3124506/page33
Don't assume that nightlies are stable, or that all gapps packages function equally.
fixed with cm 13.1 4/4/2016 and nano gapps 4/5/2016
dwreck420 said:
fixed with cm 13.1 4/4/2016 and nano gapps 4/5/2016
Click to expand...
Click to collapse
Can you check your tablet and see what the last 3 numbers are for google play services that are installed?
same thing happened to me, CM13 + nano opengapp,= bootloop ...that opengapp is starting to be very annoying... I'll have to find another source for gapps.
zigonneux said:
same thing happened to me, CM13 + nano opengapp,= bootloop ...that opengapp is starting to be very annoying... I'll have to find another source for gapps.
Click to expand...
Click to collapse
deltadroid gapps
slim gapps
Seems that there are DU builds for the HTC 10 (pme). Here: https://download.dirtyunicorns.com/pme/
Has anyone tried them? If yes, what are your impressions? :laugh:
errikosd said:
Seems that there are DU builds for the HTC 10 (pme). Here: https://download.dirtyunicorns.com/pme/
Has anyone tried them? If yes, what are your impressions? :laugh:
Click to expand...
Click to collapse
It is AOSP based compared to LOS (CM) which the majority of the ROMs posted are.
DU is a great ROM. I found that it lacked some important features that I like, but a very solid ROM.
Yes i tried on Sprint but there was no data...even after entering the apn in
errikosd said:
Seems that there are DU builds for the HTC 10 (pme). Here: https://download.dirtyunicorns.com/pme/
Has anyone tried them? If yes, what are your impressions? :laugh:
Click to expand...
Click to collapse
Encryption was not working, even with a full data format prior to flashing.
Any other opinions?
I have been running the weekly and official builds with nebula eas kernel for about 5 weeks or so. I personally feel its the best non-sense based ROM for my usage. It does lack some customisations most others have but makes up for it by being super stable, fast, battery friendly and just works as its supposed to with bull. I use superSU, substratum and A.R.I.S.E audio mod with selinux permissive without dramas.
mrrflagg said:
I have been running the weekly and official builds with nebula eas kernel for about 5 weeks or so. I personally feel its the best non-sense based ROM for my usage. It does lack some customisations most others have but makes up for it by being super stable, fast, battery friendly and just works as its supposed to with bull. I use superSU, substratum and A.R.I.S.E audio mod with selinux permissive without dramas.
Click to expand...
Click to collapse
Does it come with root or Magisk out of the box?
To reverse the question, can I use it as clean Android without root, passing SafetyNet? Thanks!
errikosd said:
Does it come with root or Magisk out of the box?
To reverse the question, can I use it as clean Android without root, passing SafetyNet? Thanks!
Click to expand...
Click to collapse
It comes WITHOUT root. So you can choose your preffered method or no root at all.
I don't know about safetynet as I am not using android pay or anything that relies on it to pass.
Also I have not had any encryption issues as someone earlier replied
mrrflagg said:
I have been running the weekly and official builds with nebula eas kernel for about 5 weeks or so. I personally feel its the best non-sense based ROM for my usage. It does lack some customisations most others have but makes up for it by being super stable, fast, battery friendly and just works as its supposed to with bull. I use superSU, substratum and A.R.I.S.E audio mod with selinux permissive without dramas.
Click to expand...
Click to collapse
What firmware and TWRP Version are you using with it ? With the Nougat firmware and latest TWRP, I get the encryption issue..
Scutariu said:
What firmware and TWRP Version are you using with it ? With the Nougat firmware and latest TWRP, I get the encryption issue..
Click to expand...
Click to collapse
401.4 FW and 3.1.0 TWRP. What kind of encryption issue? I did have once only rebooted into recovery and it asked for the password but I just rebooted in recovery from TWRP and it never happened again.
mrrflagg said:
401.4 FW and 3.1.0 TWRP. What kind of encryption issue? I did have once only rebooted into recovery and it asked for the password but I just rebooted in recovery from TWRP and it never happened again.
Click to expand...
Click to collapse
I've tried several combinations, with older/latest firmware.
Every time, It would ask for the encryption password on bootup.
Even if I haven't set one up.. With data format prior to installing
Anyway, got sick of re-setting apps on my phone, just installed Maximus HD ROM, and that's that ?
Dirty Unicorns
errikosd said:
Seems that there are DU builds for the HTC 10 (pme). Here: https://download.dirtyunicorns.com/pme/
Has anyone tried them? If yes, what are your impressions? :laugh:
Click to expand...
Click to collapse
The 4-8-17 build is Android 7.1.2 and so far it is running really well. I am surprised that there is not a thread in the ROM section for DU.
morr22066 said:
The 4-8-17 build is Android 7.1.2 and so far it is running really well. I am surprised that there is not a thread in the ROM section for DU.
Click to expand...
Click to collapse
I think it was the DU team's decision to close all and not allow any XDA threads. Someone correct me if I am wrong.
No idea why though.
morr22066 said:
The 4-8-17 build is Android 7.1.2 and so far it is running really well. I am surprised that there is not a thread in the ROM section for DU.
Click to expand...
Click to collapse
A quick question.
What variant , firmware and TWRP are you using?
Everytime I try that rom..it encrypts itself with an unknown password, and upon restart I'm unable to access my phone
Encryption
Scutariu said:
A quick question.
What variant , firmware and TWRP are you using?
Everytime I try that rom..it encrypts itself with an unknown password, and upon restart I'm unable to access my phone
Click to expand...
Click to collapse
I have had that happen when switching from a sense based ROM to LOS or AOSP and it's a "pita"... Anything that I want to keep gets moved to my SD card before I reboot to recovery.
I read through several threads and tried several possible solutions so I can't remember exactly which one worked.
I am currently on Verizon, official Nougat with the flashed us unlocked "patch", TWRP 3.1.0-1. If you are on Verizon or Sprint you need to patch the image with a missing image that is found in the us unlocked model (there are threads discussing it where you can find the file).
LOS
Scutariu said:
A quick question.
What variant , firmware and TWRP are you using?
Everytime I try that rom..it encrypts itself with an unknown password, and upon restart I'm unable to access my phone
Click to expand...
Click to collapse
The Lineage is wiki spells things out pretty well.
https://wiki.lineageos.org/devices/pme/install
Here is another thread on twrp issues
https://forum.xda-developers.com/htc-10/how-to/guide-fix-pin-pattern-password-t3538438
morr22066 said:
The Lineage is wiki spells things out pretty well.
https://wiki.lineageos.org/devices/pme/install
Click to expand...
Click to collapse
It was not related to the data partition.
The format user data was done prior and after flashing it.
There is a DU Oreo-based build for the HTC 10: https://download.dirtyunicorns.com/?device=pme
For the time being it is under "RC". Downloading now, will report back!
Edit: ROM is very nice and is flying by. Only downside is that camera app is VERY slow... Also, woofer is not working (as expected).
What I like the most is that it is AOSP, i.e. no LineageOS stuff like AudioFX, etc. Customisation features are nice and the experience is close to Pixel with Stock OpenGapps. If the camera app is fixed, then this would be perfect (I believe it will, since this is the first RC release)!
Further notes: Capacitive buttons backlight is off by default (can't find any standard option to turn on, maybe with a kernel tool?) and notification LED does not work either. Don't mind for the capacitive buttons too much, but the LED is a real problem.
errikosd said:
There is a DU Oreo-based build for the HTC 10: https://download.dirtyunicorns.com/?device=pme
For the time being it is under "RC". Downloading now, will report back!
Edit: ROM is very nice and is flying by. Only downside is that camera app is VERY slow... Also, woofer is not working (as expected).
What I like the most is that it is AOSP, i.e. no LineageOS stuff like AudioFX, etc. Customisation features are nice and the experience is close to Pixel with Stock OpenGapps. If the camera app is fixed, then this would be perfect (I believe it will, since this is the first RC release)!
Further notes: Capacitive buttons backlight is off by default (can't find any standard option to turn on, maybe with a kernel tool?) and notification LED does not work either. Don't mind for the capacitive buttons too much, but the LED is a real problem.
Click to expand...
Click to collapse
Yea I'm having that sane problem with the touch key lights not working n it bothers me a bit. I didn't notice if the led was working or not. Keep me posted if u figure out the the key problem plz.
XenonHD ROM for Xiaomi Mi Mix 2
A Team Horizon ROM
Based on AOSP r36 7.1.2
This ROM has all the features XenonHD has to offer.
All hardware functions including:
NFC
Bluetooth Audio
Fingerprint Scanner
Doze & Wake-up Gestures (dtw works after the first reboot)
And...many more things.
Magisk is no longer built in, so you'll need to flash it when first installing, and after every dirty flash.
VoLTE doesn't work (at least on T-Mobile). I believe most of the pieces are in place, but there may be something in the firmware that's preventing it? If I could figure out how to tap into the stock cust files, I might be able to figure out how to get it working.
Proximity Sensor is working:
Notification Light:
I have slowed down the notification light so it isn't all amped up. To make it completely usable, go to:
Fixed default notification blinks for built-in apps so they are slowed down without needing to go to settings.
For use-installed apps, add them to custom notification list in settings > notifications > gear icon > notification light > + in upper right corner > select app. Apps added to that list will have slow notification blinks.
I simply cannot find a way to make user-installed app notifications behave the same as built-in apps. Grrr!!
I have also made the light sensor wait longer before dimming the screen. This helps with left-handed activities blocking the light sensor and almost immediately dimming the screen.
Reduced time to go back from dim to bright. Screen will dim after 5 seconds, returns to bright after 2 seconds.
I've remove configpanel & pocketmode...they did little to nothing, and may have caused more battery drain than I care for.
Required prior to installing:
Unlock Bootloader
Install custom recovery: https://www.androidfilehost.com/?fid=962021903579490303
HUGE thanks to IceMan for bringing this to Mix 2!
A quirk with this TWRP: This one looks for backups in TWRP/BACKUPS/MIX_2 folder. Normally, the MIX_2 folder is named after serial number of your device.
So, you existing backups won't be found until you rename the folder in BACKUPS to MIX_2.
Installation Instructions:
Dirty flash is now available with the above TWRP and 10-26-2017 rom.
Download the most recent build: https://www.androidfilehost.com/?fid=673791459329071426
Download Gapps (I use Open Gapps Mini) --> http://opengapps.org/
All versions from 10-24-2017 are now encryptable.
From TWRP Recovery:
IF COMING FROM MIUI-BASED ROM: FULL WIPE AND FORMAT DATA!!
If you encounter ERROR 7, during XenonHD install, install Global MIUI ROM, then do full wipe and data format again, then install XenonHD rom.
If coming from AOSP-based ROM:
- Full wipe (Cache, Davlik/ART Cache, System & Data)
- Flash ROM zip
- Flash Gapps zip
Huge thanks to Mokee for bringing this device up and making a great place to start.
Also a very HUGE thanks to @Arasthel for his work on proximity sensor and figuring out the bluetooth reboot stuff and other hints, suggestions and incalculable work.
I'd also like to thank all of you folks here for trying this ROM and providing constructive feedback.
In addition, I appreciate your patience when issues come up that need to be fixed. I am not a developer, and I have a full time job and a wife that takes precedence most of the time
Sources:
Vendor:
https://github.com/hondajohn88/android_vendor_xiaomi_msm8998-common
https://github.com/hondajohn88/android_vendor_xiaomi_chiron/tree/xenonhd
Kernel:
https://github.com/hondajohn88/android_kernel_xiaomi_msm8998/tree/xenonhd
Device:
https://github.com/hondajohn88/android_device_xiaomi_chiron/tree/xenonhd
https://github.com/hondajohn88/android_device_xiaomi_msm8998-common/tree/xenonhd
reserved
reserved 2
Does safety net pass with or without magisk?
subashchandran said:
Does safety net pass with or without magisk?
Click to expand...
Click to collapse
With magisk its working
Gesendet von meinem MI Mix 2 mit Tapatalk
THX for the ROM @hondajohn88 ,very much appreciated. :good:
Is this 1st release identical to the beta?
Just curious,as I tried to dirty flash over the beta & got the same errors as if coming from another ROM (wouldn't flash).
Is a full wipe (less formatting data) necessary if updating ?
I don't mind setting up from new again,even if just updating from the beta build.
However,wondering if incremental updates are going to be an option on future builds.
THX.
Sent from my MI Mix 2 using XDA Labs
Bluetooth seems to be working fine for audio/calls. Need to try video/youtube audio output on car (will do it on the drive back home)
ROM is slick, its been good so far (2 hours since i have set everything up)
KOLIOSIS said:
THX for the ROM @hondajohn88 ,very much appreciated. :good:
Is this 1st release identical to the beta?
Just curious,as I tried to dirty flash over the beta & got the same errors as if coming from another ROM (wouldn't flash).
Is a full wipe (less formatting data) necessary if updating ?
I don't mind setting up from new again,even if just updating from the beta build.
However,wondering if incremental updates are going to be an option on future builds.
THX.
Sent from my MI Mix 2 using XDA Labs
Click to expand...
Click to collapse
Oh yeah...I need to add that to the OP, for some reason, dirty flash won't work. There's a couple weird things with this build, one is I can't make a dirty build or it breaks Wi-Fi, and can't dirty flash. I don't know the reasons, but if I figure it out, I'll be sure to let everyone here know. It's an extreme pain in the ass.
subashchandran said:
Bluetooth seems to be working fine for audio/calls. Need to try video/youtube audio output on car (will do it on the drive back home)
ROM is slick, its been good so far (2 hours since i have set everything up)
Click to expand...
Click to collapse
Glad everything is working for you so far. Bluetooth audio in car should work (it does on mine), but I found the volume on the car set to zero so needed to turn that up. That was a brief "oh crap" moment that I thought it wasn't working lol
subashchandran said:
Does safety net pass with or without magisk?
Click to expand...
Click to collapse
I think it fails without it, but magisk is built in, so if have to remove it to find out for sure.
hondajohn88 said:
Oh yeah...I need to add that to the OP, for some reason, dirty flash won't work. There's a couple weird things with this build, one is I can't make a dirty build or it breaks Wi-Fi, and can't dirty flash. I don't know the reasons, but if I figure it out, I'll be sure to let everyone here know. It's an extreme pain in the ass.
Click to expand...
Click to collapse
IT'S ALL GOOD @hondajohn88 . :good:
This ROM is daily-driver material,every update from here on out is a bonus & very much appreciated. :good:
hondajohn88 said:
Oh yeah...I need to add that to the OP, for some reason, dirty flash won't work. There's a couple weird things with this build, one is I can't make a dirty build or it breaks Wi-Fi, and can't dirty flash. I don't know the reasons, but if I figure it out, I'll be sure to let everyone here know. It's an extreme pain in the ass.
Click to expand...
Click to collapse
It seems that we both have faced this issue. I just got A2DP working yesterday on Resurrection Remix by using sagit as base - without msm-8998 common and all that -, imagine my surprise when I saw you also did .
Anyway, I think the WiFi bug may be related to something going wrong in the build. When you build the ROM, kernel sources are used and you can see that the wlan.ko module is built. The problem is, wlan.ko is also a binary blob found in vendor. I believe that on the 2nd build, if dirty, one of these modules overwrites the other - which worked. Maybe you can test this idea, I will be doing it too on the next days.
Arasthel said:
It seems that we both have faced this issue. I just got A2DP working yesterday on Resurrection Remix by using sagit as base - without msm-8998 common and all that -, imagine my surprise when I saw you also did .
Anyway, I think the WiFi bug may be related to something going wrong in the build. When you build the ROM, kernel sources are used and you can see that the wlan.ko module is built. The problem is, wlan.ko is also a binary blob found in vendor. I believe that on the 2nd build, if dirty, one of these modules overwrites the other - which worked. Maybe you can test this idea, I will be doing it too on the next days.
Click to expand...
Click to collapse
That's cool you got the Bluetooth working on RR, knocking little things out one by one ?
Thanks for the idea on the Wi-Fi, I'll look into that this evening. Maybe there's a file I can delete before dirtybuilding. That would make testing things a lot faster! ??
By the way, does android auto work on your rr?
Everything except proximity sensor works and works as good as stock. I have installed custom font, black swift substratum OMS theme without any hiccups. The rom is buttery smooth and I've been getting a better battery drain trend on this compared to resurrection/mokee. I have naptime doze installed to see if i can ooze out more battery goodness to the levels of epic Rom(miui 9)
Overall this is super encouraging to see a daily driver rom this early for mi mix 2.
There is one edge case which might be a bug, when connected on car Bluetooth and watching something on YouTube.. And then you get a call, i pressed answer on the car knobs/buttons.. I couldn't hear the person talking.. Car was displaying "audio disabled message ”. But talking/call and video/music in isolation works just fine.
Android auto works for me. I'm on RR now. Might come to this if we can get Android auto working. How did you guys fix your Bluetooth audio on RR (we can move this to the RR thread if you prefer) @Arasthel
slyyke said:
Android auto works for me. I'm on RR now. Might come to this if we can get Android auto working. How did you guys fix your Bluetooth audio on RR (we can move this to the RR thread if you prefer) @Arasthel
Click to expand...
Click to collapse
Thanks for the info about android auto on RR. I'll take a look at their repo and see if I messed up a USB setting somehow.
As far as I'm concerned, other ROMs can be discussed here.
Open source should be crowd sourced for maximum problem resolution.
RR probably (?) Did the same as me... Mokee made a commit in qcom/audio that did the trick.
hondajohn88 said:
That's cool you got the Bluetooth working on RR, knocking little things out one by one
Thanks for the idea on the Wi-Fi, I'll look into that this evening. Maybe there's a file I can delete before dirtybuilding. That would make testing things a lot faster! ?
By the way, does android auto work on your rr?
Click to expand...
Click to collapse
Hi... Thank you again for the wlan.ko tip. I deleted all instances of that in my out folder, dirty built and it's all good. Sped up my test time considerably! Woohoo! :good:
Thanks op for adding this to to the mix. Much appreciated. I am not sure if I can leave Resurrection due to all the customization options. Does this room offer as many customization options? Thanks so much!
stu5797 said:
Thanks op for adding this to to the mix. Much appreciated. I am not sure if I can leave Resurrection due to all the customization options. Does this room offer as many customization options? Thanks so much!
Click to expand...
Click to collapse
I haven't used rr for this phone, but I think at this point rr probably has more options. This one has quite a few, and as son as I get most of this ROM straightened out, I'll try adding more options.
I'll add some screen shots of the settings to help people decide.
Thanks ?
Great work by a great Dev,
Thanks for putting in the work, smoothhhh rom~
This little zip will fix the bug of no voice in calls when updating to december firmware/modem, with this combined 10.0.3.0 actually gives louder voice in calls.
**Will also fix 10.0.2.0 if you don't want to update for whatever reason.
Insructions:
1. Flash your favorit ROM, Mine is Joeyhuab's version of PE.
2. Flash 10.0.3.0.PDHMIFK Firmware from joeyhuab's thread.
3. Than flash thia fix, and reboot.
Congrats! now you got the latest modem working.
MVPAsafS said:
This little zip will fix the bug of no voice in calls when updating to december firmware/modem, with this combined 10.0.3.0 actually gives louder voice in calls.
**Will also fix 10.0.2.0 if you don't want to update for whatever reason.
Insructions:
1. Flash your favorit ROM, Mine is Joeyhuab's version of PE.
2. Flash 10.0.3.0.PDHMIFK Firmware from joeyhuab's thread.
3. Than flash thia fix, and reboot.
Congrats! now you got the latest modem working.
Click to expand...
Click to collapse
Can you provide the link to 10.0.3.0. firmware
Download it from joeyhuab's thread;
https://forum.xda-developers.com/mi-a1/themes/twrp-baseband-modem-april-stock-rom-t3777901
Call voice not fixed still.
Im on sgsi moun 6.2 December patch .
Can anyone help me out
deadshot367 said:
Call voice not fixed still.
Im on sgsi moun 6.2 December patch .
Can anyone help me out
Click to expand...
Click to collapse
It's wasn't meant for GSI!!
Very helpful.. thanks for the fix
MVPAsafS said:
This little zip will fix the bug of no voice in calls when updating to december firmware/modem, with this combined 10.0.3.0 actually gives louder voice in calls.
**Will also fix 10.0.2.0 if you don't want to update for whatever reason.
Insructions:
1. Flash your favorit ROM, Mine is Joeyhuab's version of PE.
2. Flash 10.0.3.0.PDHMIFK Firmware from joeyhuab's thread.
3. Than flash thia fix, and reboot.
Congrats! now you got the latest modem working.
Click to expand...
Click to collapse
It is not working on pixel experience 9.0. plz help me
alien__x said:
It is not working on pixel experience 9.0. plz help me
Click to expand...
Click to collapse
DUDE HE JUST SAID SO COMMENTS AOVE ITS FOR PURE STOCK ROM OF MI A1 NOT CUSTOM ROMS!!!!:laugh:
No more need for this as new 10.0.4.0 is fixed.
PE latest version based on 10.0.4.0 Jan firmware. So not it wont work there!
I never said this is for stock rom, it's fkr stock firmware 10.0.3.0....even the most custom rom have no choice but stock fw..
Unless you use a GSI, And your ROM is more or less close to AOSP it will work.
Anyway the thread is relevant only to those with 10.0.2.0 and 10.0.3.0 (December FW) as Jan FW don't need the fix anymore.
My Savior
MVPAsafS said:
This little zip will fix the bug of no voice in calls when updating to december firmware/modem, with this combined 10.0.3.0 actually gives louder voice in calls.
**Will also fix 10.0.2.0 if you don't want to update for whatever reason.
Insructions:
1. Flash your favorit ROM, Mine is Joeyhuab's version of PE.
2. Flash 10.0.3.0.PDHMIFK Firmware from joeyhuab's thread.
3. Than flash thia fix, and reboot.
Congrats! now you got the latest modem working.
Click to expand...
Click to collapse
Dude. You are my savior. I scratch my head 2 days on this issue. Your solution works like charm. :good::laugh: