- Edited
Upstate1618 I already use 2024102400. And it's not fixed. I will create issues later. But how I can get logs? It's not create toast with "crashed"
Looks like it's already exist https://github.com/GrapheneOS/os-issue-tracker/issues/4175
Upstate1618 I already use 2024102400. And it's not fixed. I will create issues later. But how I can get logs? It's not create toast with "crashed"
Looks like it's already exist https://github.com/GrapheneOS/os-issue-tracker/issues/4175
phone-company We turn on the Hotspot WiFi function. Turn it off. Turn on wifi, connect to the network. Disconnect wifi.
We can no longer turn on WiFi or Hotspot, the switch instantly returns to the position disconnected. Need reboot phone
GrapheneOS please apply wifi fix for p8p. It's affected to
Upd: I think I found the cause and it has to do with the latest update.
Any service listening on 0.0.0.0 on the device no longer accepts connections via 10.1.10.1 when distributing WiFi. Before the update it was possible to connect exactly to services on the device distributing WiFi through this ip. Now only through a unique ip from the 192.168.x.x pool at each connection.
Upstream bug or feature?
other8026 I apologize, my English is not that good
Yes. Google pixel runs a sing-box client on Google pixel, it is such a proxy. It raises a local proxy to socks: / //0.0.0.0.0:1080
And now it's impossible to connect to it from a pc that Google pixel gives WiFi to.
This may not be a popular scheme, but technically it should work. Distribution on 0.0.0.0.0 allows any client in the local network to connect to it.
It also makes it impossible to transfer files from phone to PC via WiFi, only by wire
First of all I will note that this problem did not occur 4-5 OS versions ago. I haven't updated GrapheneOS for a long time, about a month, today I updated to the latest 2024071600 version. And now internet distribution from my phone doesn't work as it should
I am using vpn service on Pixel, it listens the same way on socks 0.0.0.0:1080. In the morning still I was giving out internet, through this proxy pc was easily connected to the network. But after updating GrapheneOS connection does not happen. At all. Pixel and vpn service on it don't even receive connection request, vpn logs in trace mode don't contain any mention of connection attempts except those related to Pixel itself. Rebooting the devices did not help. It is impossible to roll back to the previous version of GrapheneOS.
This may be due to the latest "backport mainline APEX module patches for Media Provider, Network Stack, Remote Key Provisioning and Wi-Fi" update or work on VPN leak protection
Upd: it work well on 2024070201
de0u Unfortunately there are no other options. Google has disabled 5 and 6Ghz distribution in all countries where there are no official sales. Even reminding them that in Linux kernel there are no such restrictions in many countries and distribution of 5 and 6Ghz is allowed does not help, they would have done at least like in Linux kernel, there are also these restrictions by country for WiFi modules, but no, Google made its own list, on the Google support forum one complaint is more than three years old, no one is trying to fix it. If you don't live in the USA or Europe, you don't need these features, nobody cares what laws you have in your country.
roamer4223 this will be fixed if this PR will be merged. https://github.com/GrapheneOS/platform_packages_apps_Settings/pull/246
Thank you for the implementation. This is a very useful feature that many users have been waiting for several years. I would like to get more documentation for it, whether it works before the first unlocking of the device, how best to set it up and in general tips from developers on how to use it
P.s: please merge this pull request https://github.com/GrapheneOS/platform_packages_apps_Settings/pull/246