@freeyia
you can try it, it may be fixed, it has been a while since the report of wifi being broken
it may work
it may not, in which case you can try and post logcat and maybe will help me debug it
DivestOS 19.1 for vayu requires firmware version V13.0.5.0.SJUMIXM and 20.0 requires V14.0.3.0.TJUMIXM
Thanks for the quick reply. Any easy way to enable this on my device (since it was working fine for LOS) through settings/ terminal ?
@sriracha
no, it isn’t compiled into the system at all
@SkewedZeppelin
Ok, no worries, could this be an option for future lemonadep builds? Or does it become to much hassle to change this for just 1 build in between all the supported devices you provide ? Which i would totally understand btw.
Also, im a graphic designer, also industrial designer, if i could ever help you out with anything, please let me know i’d be happy to contribute.
again, I purposely remove it because of the risk it has of leaving devices in a state where they CANNOT charge at all permanently.
I will not ship such a broken “feature”.
I have that logcat in Vayu, DOS 20.0:
09-24 09:25:26.674 859 859 E WifiHAL : Timed out wating on Driver ready …
09-24 09:25:26.674 859 859 E android.hardware.wifi@1.0-service: Failed or timed out awaiting driver ready
09-24 09:25:26.674 859 859 E android.hardware.wifi@1.0-service: Failed to start legacy HAL: TIMED_OUT
09-24 09:25:26.675 1174 1865 E HalDevMgr: executeChipReconfiguration: configureChip error: 9 (, timed out)
09-24 09:25:26.675 1174 1865 E HalDevMgr: Teardown Wifi internal state
09-24 09:25:26.675 1174 1865 I WifiNative: Vendor HAL died. Cleaning up internal state.
09-24 09:25:26.675 1174 1865 E HalDevMgr: createIfaceIfPossible: Failed to create iface for ifaceType=0, requestorWs=WorkSource{10116 com.android.systemui}
09-24 09:25:26.675 1174 1865 E WifiVendorHal: Failed to create STA iface
09-24 09:25:26.675 1174 1865 E WifiNative: Failed to create iface in vendor HAL
09-24 09:25:26.676 1174 1865 E WifiClientModeManager[unknown]: Failed to create ClientInterface. Sit in Idle
09-24 09:25:26.676 1174 1865 E WifiActiveModeWarden: ClientModeManager start failed!ConcreteClientModeManager{id=322945 iface=null role=null}
09-24 09:25:26.676 1174 1865 D WifiScanRequestProxy: Sending scan available broadcast: false
09-24 09:25:26.676 1174 1872 I WifiScanningService: Received a request to disable scanning, UID = 1000
09-24 09:25:26.676 1174 1872 I WifiScanningService: wifi driver unloaded
09-24 09:25:26.677 1174 1865 I WifiScanRequestProxy: Scanning is disabled
09-24 09:25:26.677 1174 1865 I WifiCountryCode: No active mode, call onDriverCountryCodeChanged with Null
09-24 09:25:26.677 1174 1865 E WifiActiveModeWarden: One of the native daemons died. Triggering recovery
09-24 09:25:26.677 1174 1865 E WifiSelfRecovery: Triggering recovery for reason: WifiNative Failure
09-24 09:25:26.678 1174 1865 E WifiSelfRecovery: Already restarted wifi 2 times in last 1 hour. Disabling wifi
09-24 09:25:26.693 1174 1865 D WifiConfigStore: Writing to stores completed in 15 ms.
09-24 09:25:26.693 1174 1865 E WifiActiveModeWarden: One of the native daemons died. Triggering recovery
09-24 09:25:26.693 1174 1865 E WifiSelfRecovery: Triggering recovery for reason: WifiNative Failure
09-24 09:25:26.693 1174 1865 E WifiSelfRecovery: Already restarted wifi 2 times in last 1 hour. Disabling wifi
09-24 09:25:26.694 1174 1865 D WifiController: STA disabled, return to DisabledState.
09-24 09:25:26.694 1174 1865 D WifiController: EnabledState.exit()
09-24 09:25:26.694 1174 1865 D WifiController: DisabledState.enter()
09-24 09:25:26.694 1174 1865 D WifiController: Recovery has been throttled, disable wifi
09-24 09:25:26.694 1174 1865 D WifiActiveModeWarden: Shutting down all mode managers
09-24 09:25:26.694 1174 1865 D WifiController: Recovery has been throttled, disable wifi
09-24 09:25:26.694 1174 1865 D WifiActiveModeWarden: Shutting down all mode managers
09-24 09:25:26.903 1174 1866 W WifiDiags: could not flush ringbuffer
09-24 09:25:27.127 1174 1866 W WifiDiags: could not flush ringbuffer
@freeyia
is that with firmware version V14.0.3.0.TJUMIXM ?
Yes, even I was using LOS 20.0 working normally. Let me know if I can help with anything else, checking something, I won’t uninstall it.
@freeyia
thank you for testing, but you probably should switch to Lineage or Divest/19 because it is unlikely to be fixed soon
Ok, I’m available for any further testing if that would help, it’s not my main phone so I can stay without this one for a few days for any testing.
I have two questions:
Can I install GAPPS on DivestOS? I don’t trust MicroG, I prefer to use the official Google apps.
Why is DivestOS 20.0 “broken” for Vayu? Vayu is a very popular device.
@Zorosuro
DivestOS does not support any gapps/“Google app” packages.
It has optional unprivileged microG enablement.
See: Faq - DivestOS Mobile
vayu 20.0 has non-functional Wi-Fi: [vayu]wifi is broken under 20.0 · Issue #340 · Divested-Mobile/DivestOS-Build · GitHub
So what happens if i try to install gapps?
If you need Google Services activate and use unprivileged MicroG, if you need the original GApps use LineageOS and install it, I think he was clear in answering that it is not supported.
What Vayu firmware version do you recommend for DivestOS 19.1? Can I install firmware 14.0.3.0 without any problems, or do I have to install a firmware version based on Android 12 such as 13.0.3.0 to use DivestOS 19.1?
wait, so the open source API implementation you don’t trust, but you do trust the proprietary closed source from the billion dollars fined abuser? 
I use it with the latest one, the 14.0.3.0