View Single Post
Old 04-16-2022, 01:13 PM   #768
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
Quote:
Originally Posted by davidfor View Post
For whatever reason, the design is that WiFi gets enabled whenever Bluetooth is enabled.
That's because the kernel only exposes a single way to power on the single chip that handles BT & Wi-Fi, so using BT *requires* powering-on the Wi-Fi chip (because it's also the BT chip).
Historically, killing Wi-Fi on NTX boards entailed powering it down, too (probably for power efficiency reasons), so powering the WI-Fi chip was somewhat fairly heavily tied with enabling Wi-Fi .

Which means that making the two *distinct* UI-wise is tricky: you'd have to uncouple toggling Wi-Fi power from toggling Wi-Fi connection (which probably entails mostly always leaving the chip powered on, which is... meh', especially on a board that already suffers from terrible power management. Ironically enough, that BT+Wi-Fi chip might be the most power efficient thing in there ).
NiLuJe is offline   Reply With Quote