Anyone else having an increased battery drain after using the wifi hotspot?
Somebody mentioned this in the past. I'd only expect that the hotspot causes an increased battery drain, or perhaps some energy consumption optimisations are not yet set up for WLAN, especially when in AP mode.
Anyone else having an increased battery drain after using the wifi hotspot?
Steps to reproduce:
1) mobile data ON and wifi OFF (battery drain <= 1% per hour)
2) enable wifi, enable hotspot (connman wifi)
3) disable hotspot, disable wifi
4) observe increased battery drain (around 6% per hour)
# on Jolla
1) enable dev mode
2) set password
3) optional: set ip address for usb connectivity
# Then configure Win host:
1) connect your Jolla with usb to the Win machine
2) from the pc, open network & sharing center and select "Change adapter settings" or Win+R and type control netconnections
3) open the adapter labeled with "Remote NDIS based Internet sharing device"
4) go to properties
5) select entry for IP V4
6) enter a static ip (in the same subnet of the phone). So if your phone has 192.168.2.15 (default), you can put 192.168.2.10 for example
7) set phone ip address as gateway & dns entries as well.
also disable
-Internet Protocol Version 6 (TCP/IPv6)
-Link-Layer Topology Discovery Mapper I/O Driver
-Link-Layer Topology Discovery Responder
Wrong version probably. Guess will clone the one I use on Galaxy and try it.
I had missing sound and thought it was spotify. But it turns out it was sound from all android apps. A restart didn't change anything but after a second restart (with a wait to make sure all systems had time to start properly) the sound came back.
This may have been related to bluetooth as I was using and experimenting with a headset at the time and it may have disconnected "uncleanly", but sound from the native media player wasn't affected.
when starting the shell on the phone it always goes to root and doesn't run the login scripts, even if the user is nemo. Anyone know a solution to that yet?o It bugs the hell out of me.
when starting the shell on the phone it always goes to root and doesn't run the login scripts, even if the user is nemo. Anyone know a solution to that yet?o It bugs the hell out of me.
After interacting with a window (new message, refresh the browser, etc.) on the multitaksing screen (and hence opening of this particular app) the app does not move to the first position (top left), like it should. It just stay where it was...
