-
@AppLee I believe OP is already in the porter's group. They hit an obstacle with their port that has them stuck, but it seems very device specific, or else difficult to diagnose without having the port in front of you, so the suggestions of the other porters have not led to any breakthrough.
-
@arubislander Yes, I'm stuck
And I'm also still stuck that sometimes I can't connect to the internet when I restart the device● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2024-09-29 12:00:03 -05; 1min 55s ago Docs: man:NetworkManager(8) Main PID: 4342 (NetworkManager) Tasks: 3 (limit: 5560) Memory: 3.4M CGroup: /system.slice/NetworkManager.service └─4342 /usr/sbin/NetworkManager --no-daemon sep 29 12:00:15 ubuntu-phablet NetworkManager[4342]: <info> [1727629215.9285] device (p2p-dev-swlan0): supplicant management interface state: 4way_handshake -> disconnected sep 29 12:00:16 ubuntu-phablet NetworkManager[4342]: <info> [1727629216.0273] device (swlan0): supplicant interface state: disconnected -> scanning sep 29 12:00:16 ubuntu-phablet NetworkManager[4342]: <info> [1727629216.0274] device (p2p-dev-swlan0): supplicant management interface state: disconnected -> scanning sep 29 12:00:18 ubuntu-phablet NetworkManager[4342]: <warn> [1727629218.5755] device (swlan0): no secrets: No agents were available for this request. sep 29 12:00:18 ubuntu-phablet NetworkManager[4342]: <info> [1727629218.5756] device (swlan0): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed') sep 29 12:00:18 ubuntu-phablet NetworkManager[4342]: <info> [1727629218.5759] manager: NetworkManager state is now DISCONNECTED sep 29 12:00:18 ubuntu-phablet NetworkManager[4342]: <warn> [1727629218.5761] device (swlan0): Activation: failed for connection '#########' sep 29 12:00:18 ubuntu-phablet NetworkManager[4342]: <info> [1727629218.5765] device (swlan0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') sep 29 12:00:19 ubuntu-phablet NetworkManager[4342]: <info> [1727629219.6213] device (swlan0): supplicant interface state: scanning -> disconnected sep 29 12:00:19 ubuntu-phablet NetworkManager[4342]: <info> [1727629219.6213] device (p2p-dev-swlan0): supplicant management interface state: scanning -> disconnected -
phablet@ubuntu-phablet:~/Downloads$ cat pe.log | grep wlan [ 8.105718] wlan: Loading driver v5.2.022.3V-HS221230A [ 8.106494] wlan_hdd_state wlan major(510) initialized [ 8.108139] cnss: pinctrl_select_state wlan_en_sleep [ 8.109147] cnss: pinctrl_select_state wlan_en_active [ 8.389427] cnss: FW name added with prefix: qca6390/bdwlan.elf [ 8.391856] cnss: Downloading BDF: qca6390/bdwlan.elf, size: 57836 [ 9.006058] cnss_pci 0000:01:00.0 wlp1s0: renamed from wlan0 [ 9.030189] IPv6: ADDRCONF(NETDEV_UP): swlan0: link is not ready [ 9.030290] wlan: [4374:I:DP] 00000000: 10 76 12 29 c0 08 16 7a 99 6a a9 17 e1 e2 40 00 [ 9.030296] wlan: [4374:I:DP] 00000010: 39 c1 75 ef [ 9.030299] wlan: [4374:I:DP] 00000000: 57 2c 2c b7 09 e3 09 18 0b 90 f7 e2 a8 40 d2 6f [ 9.030302] wlan: [4374:I:DP] 00000010: 58 9d 29 73 5f c5 fe 3a 90 b2 c2 25 ed 9c d8 68 [ 9.030305] wlan: [4374:I:DP] 00000020: 1c f3 29 57 3b 17 90 cc 35 f6 7a 48 [ 9.084482] IPv6: ADDRCONF(NETDEV_UP): swlan0: link is not ready [ 9.171887] IPv6: ADDRCONF(NETDEV_UP): swlan0: link is not ready [ 9.270260] IPv6: ADDRCONF(NETDEV_UP): swlan0: link is not ready [ 9.846611] init: processing action (vendor.wlan.ramdump_mode=2) from (/vendor/etc/init/wifi_qcom_ap_exynos.rc:46) -
@Sota4Ever_k hello?
-
@Sota4Ever_k Are you DenPe on Telegram? If so. You are already in the best place to receive help there.
The reason you are not getting more help is because your issues are appearantly very device specific, and dificult to diagnose for people not having the device in their hands. -
@arubislander I noticed something about the wifi, it's that after a while the wifi works again.
And in my repository I implemented several devices of the same processor and little by little it is working
-
@Sota4Ever_k said in Samsung S20 FE UT (Ubuntu Touch) | Android 13:
little by little it is working
Alway do things little by little.
Sorry, I couldn't help myself
-
@Keneda xd, Well there have been many changes in the kernel
-
Hello, are there any updates to this effort? I have a samsung S21 and would like to run UT on it. Are there any efforts on a UT port for samsung s21? I'd appreciate any information.
-
@gn-lin s21 is a different phone, has a different SoC and not really related to this s20 fe effort
