NFC is working?? ?This issue will most likely be fixed with a coming update. I know that PixelExperience ROM has a fix for it for next update from @Valap, the hero behind fixing NFC, and now he fixed fingerprint.
NFC is working?? ?This issue will most likely be fixed with a coming update. I know that PixelExperience ROM has a fix for it for next update from @Valap, the hero behind fixing NFC, and now he fixed fingerprint.
Do I understand correctly that I dont need to fix the CFWv2 first if I'm already on POSP? Just use the update center on the phone?ROM Updated (v3.2.2+18)
Changelog:
- Fix offline charging (custom kernels may break it! Requires CFWv2)
- August security patch
- Add support for MiSoundFX
- Added a brand new AudioFX equalizer! (Screenshots below)
- Upstream kernel to latest Linux 4.14.194
- Enable vDSO in kernel
- Update drivers from begonia-q-oss
- Enforcing selinux
- Fix Netflix 1080p crashes (Needs CFWv2)
- Misc performance and stability improvements
If you're already using a POSP CFW build, just hit the download and then install button in the Center app!
Download: Sourceforge
[08-26 11:28:54.536 1339:2535 I/WifiService]
startScan uid=1000
[08-26 11:28:54.546 1324:1324 E/wificond]
NL80211_CMD_TRIGGER_SCAN failed: Network is down
[08-26 11:28:54.547 1339:1479 E/WificondScannerImpl]
Failed to start scan, freqs=null
[08-26 11:28:54.548 1339:1476 E/WifiScanRequestProxy]
Scan failure received. reason: -1,description: Scan failed
I've encountered the same issue on this ROM and PEAfter flashing CFW and POSP I am sometimes discconnected from WiFi and then my phone can't find any networks. Everything worked fine on MIUI. Here is the logcat of that part:
I arleady tried clean flashing, didn't fix.
I tried also flashing DemonSlayer kernel and it didn't fix the issue.
This bug is affecting my phone too.I've encountered the same issue on this ROM and PE
Kinda workaround is to toggle WiFi off and back on when this happens, but it'll happen again really fast.This bug is affecting my phone too.
Are there any fixes?
Mashed indicates a beta build, the release channel for Android 10 is "croquette"Hi!, what's the difference between mashed and croquette on Source Forge? I dont know which one to download?
Yeah, I noticed this recently too. I'm pretty sure this is to do with the StaState changes. Long story short, you should be happy WiFi works alongside IMS at all. Pretty much every ROM will have this issue rn, and I guess happens only on weak WiFi signal (especially on 5GHz for me). It's probably IMS service doing weird things while reporting a StaState change when trying to use features like VoWiFi. You might be able to disable VoWiFi using a prop to workaround this (assuming you only care of VoLTE). The StaState API is still only partially ported and registers empty callbacks to make the ImsService not crash and work nicely with AOSP. This is an indirect reminder of how diverged MediaTek changes are from AOSP spec; it takes time and effort to reverse things and make them work properly against AOSPAfter flashing CFW and POSP I am sometimes discconnected from WiFi and then my phone can't find any networks. Everything worked fine on MIUI. Here is the logcat of that part:
I arleady tried clean flashing, didn't fix.Code:[08-26 11:28:54.536 1339:2535 I/WifiService] startScan uid=1000 [08-26 11:28:54.546 1324:1324 E/wificond] NL80211_CMD_TRIGGER_SCAN failed: Network is down [08-26 11:28:54.547 1339:1479 E/WificondScannerImpl] Failed to start scan, freqs=null [08-26 11:28:54.548 1339:1476 E/WifiScanRequestProxy] Scan failure received. reason: -1,description: Scan failed
I tried also flashing DemonSlayer kernel and it didn't fix the issue.
CFWv2 is only required for fixing offline charging and properly using Widevine L1 (Netflix 1080p). If you don't need either, you can stay with CFWv1 (Offline charging will never get triggered on v1, device will directly boot)Do I understand correctly that I dont need to fix the CFWv2 first if I'm already on POSP? Just use the update center on the phone?
Perfect! ThanksCFWv2 is only required for fixing offline charging and properly using Widevine L1 (Netflix 1080p). If you don't need either, you can stay with CFWv1 (Offline charging will never get triggered on v1, device will directly boot)![]()
Mashed indicates a beta build, the release channel for Android 10 is "croquette"
After flashing CFW and POSP I am sometimes discconnected from WiFi and then my phone can't find any networks. Everything worked fine on MIUI. Here is the logcat of that part:
Yeah, I noticed this recently too. I'm pretty sure this is to do with the StaState changes. Long story short, you should be happy WiFi works alongside IMS at all. Pretty much every ROM will have this issue rn, and I guess happens only on weak WiFi signal (especially on 5GHz for me). It's probably IMS service doing weird things while reporting a StaState change when trying to use features like VoWiFi. You might be able to disable VoWiFi using a prop to workaround this (assuming you only care of VoLTE). The StaState API is still only partially ported and registers empty callbacks to make the ImsService not crash and work nicely with AOSP. This is an indirect reminder of how diverged MediaTek changes are from AOSP spec; it takes time and effort to reverse things and make them work properly against AOSP
I'll look into this soon, though I'm focusing on upstream AOSP R previews and AOSP master right now. Toggling WiFi will resolve it, but may occur again on low signal strengths.
CFWv2 is only required for fixing offline charging and properly using Widevine L1 (Netflix 1080p). If you don't need either, you can stay with CFWv1 (Offline charging will never get triggered on v1, device will directly boot)![]()
I don't care about either of them, dows anyone know the required prop values to disable them? I searched and found only values that enable them, with no information what prop does what and the values of it.You might be able to disable VoWiFi using a prop to workaround this (assuming you only care of VoLTE).
This happens even if I am next to the router and on all the networks not only 5G.Mashed indicates a beta build, the release channel for Android 10 is "croquette"
After flashing CFW and POSP I am sometimes discconnected from WiFi and then my phone can't find any networks. Everything worked fine on MIUI. Here is the logcat of that part:
Yeah, I noticed this recently too. I'm pretty sure this is to do with the StaState changes. Long story short, you should be happy WiFi works alongside IMS at all. Pretty much every ROM will have this issue rn, and I guess happens only on weak WiFi signal (especially on 5GHz for me). It's probably IMS service doing weird things while reporting a StaState change when trying to use features like VoWiFi. You might be able to disable VoWiFi using a prop to workaround this (assuming you only care of VoLTE). The StaState API is still only partially ported and registers empty callbacks to make the ImsService not crash and work nicely with AOSP. This is an indirect reminder of how diverged MediaTek changes are from AOSP spec; it takes time and effort to reverse things and make them work properly against AOSP
I'll look into this soon, though I'm focusing on upstream AOSP R previews and AOSP master right now. Toggling WiFi will resolve it, but may occur again on low signal strengths.
Anyone?Does anyone else have issues with gesture typing? I have turned it off/on multiple times but it doesn't seem to work.
Greek dictionary does not seem to work either.
Is this part of gapps or the ROM? I installed Open Gapps a few days later than the ROM if this is relevant
Does not work for me either. Typing this response is quiet a challenge right now.Anyone?