Fairphone 3/3+ (FP3/FP3+) Port - Halium 10
-
Hi! I have been outside today with my kids and I noticed something:
I used bluetooth headset all afternoon (12pm to 4pm connected but not playing anything) and noticed that the FP3+ got really warm in my pocket. I went to check it out and the battery was at 15%. I left the house with 80%. I guess bluetooth drains battery a lot more than before. I ised to have the same headset connected to the FP3+ the entire day without issues.
I also got a call but I couldnt get the call through the headset. Is there a setting I need to do to be able to use the headset for calls? The headset works for music (Futify) just fine though.
-
Seems like my battery issue might be something else than bluetooth. I came back home for dinner and recharged my phone fully. It went from 100% down to 38% in 5h with minimal use (been playing Red Dead Redemption 2 all evening). It is strange to see the battery drain so quickly. Any suggestions or recomendations on what could be causing this?
-
@oden is it still running hot without doing something?
Did you do a reboot in the meantime? -
@luksus I rebooted after charging it overnight. So far, it hasnt been incredibly warm. Its been roughly 2 hours since the full charge and its at 86%. Im heading to the zoo with the kids. I can update on the battery status when we are on our way back.
Minor update: 40min after my previous post, I can feel the FP3+ heating up in my pocket. The battery level is at 74% as I type this. Losing 12% battery when it has been in my pocket is probably an issue.
-
This post is deleted! -
@oden Hi, I also encountered the heating issue, though I don't know, what caused it.
I noticed, that it gets hot in the lower left corner on the backside, but I don't believe it's caused by the NFC chip...I got the Impression, that it has somethin to do with mobile data/cellular network.
I believe it cooled down, when I disabled mobile data, and it did not get hot again, after turning it on again... -
Hey, with the latest build video recording should work now.
I also added some short instructions for waydroid in the first post. -
Hi @ all,
I have now time to install and test the newest version again.
Unfortunately I have deleted all my data by unlocking the boot manager
But that makes it a lot easier to back up the data * lool *Iยดm currently downloading the image to first flash android and then the halium-image.
Should take a while, I will respond what things are working and what not
-
Hi again,
I have installed the new system now.
First thing I try is to use the new anbox.Anbox-Halium is installed successfully and showing the following:
Kernel: OK
System: OK
Enabled: YES
Running: YESBut, there is always no internet connection
I have installed a app and use adb shell with ping, but no connection
Some ideas ?I must get some apps working this week or switch again to /e/os....
-
Some more informations:
2|armv7-a-neon:/ $ ifconfig lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope: Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:16 errors:0 dropped:0 overruns:0 frame:0 TX packets:16 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:1784 TX bytes:1784 eth0 Link encap:Ethernet HWaddr b2:73:18:d9:39:98 inet addr:192.168.250.2 Bcast:192.168.250.255 Mask:255.255.255.0 inet6 addr: fe80::b073:18ff:fed9:3998/64 Scope: Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:28 errors:0 dropped:0 overruns:0 frame:0 TX packets:24 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2216 TX bytes:2632
ifconfig system itself:
anbox0 Link encap:Ethernet HWaddr fe:2a:b3:d5:a0:e9 inet addr:192.168.250.1 Bcast:0.0.0.0 Mask:255.255.255.0 inet6 addr: fe80::fc2a:b3ff:fed5:a0e9/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:25 errors:0 dropped:0 overruns:0 frame:0 TX packets:29 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2352 (2.3 KB) TX bytes:1900 (1.9 KB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:13594 errors:0 dropped:0 overruns:0 frame:0 TX packets:13594 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:42874430 (42.8 MB) TX bytes:42874430 (42.8 MB) rmnet_data0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:10.153.4.213 Mask:255.255.255.252 UP RUNNING MTU:1280 Metric:1 RX packets:12 errors:0 dropped:0 overruns:0 frame:0 TX packets:13 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1088 (1.0 KB) TX bytes:1000 (1000.0 B) rmnet_ipa0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 UP RUNNING MTU:2000 Metric:1 RX packets:10 errors:0 dropped:0 overruns:0 frame:0 TX packets:13 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1232 (1.2 KB) TX bytes:1104 (1.1 KB) rndis0 Link encap:Ethernet HWaddr ce:52:67:4b:4b:b2 inet addr:10.15.19.82 Bcast:10.15.19.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) rndis1 Link encap:Ethernet HWaddr 96:9f:ef:40:8c:0e inet6 addr: fe80::f580:2371:b587:c8e1/64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) vethG19L1N Link encap:Ethernet HWaddr fe:2a:b3:d5:a0:e9 inet6 addr: fe80::fc2a:b3ff:fed5:a0e9/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:25 errors:0 dropped:0 overruns:0 frame:0 TX packets:34 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2702 (2.7 KB) TX bytes:2636 (2.6 KB) wlan0 Link encap:Ethernet HWaddr 84:cf:bf:93:0e:b1 inet addr:192.168.178.80 Bcast:192.168.178.255 Mask:255.255.255.0 inet6 addr: fe80::b9bc:13b6:a60c:f404/64 Scope:Link inet6 addr: 2a02:2454:8b64:7400:649b:946e:40d8:5a94/64 Scope:Global inet6 addr: 2a02:2454:8b64:7400:8012:a19a:5db9:2495/64 Scope:Global UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:6502 errors:0 dropped:0 overruns:0 frame:0 TX packets:713 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:395733 (395.7 KB) TX bytes:95722 (95.7 KB)
sudo anbox-bridge restart:
no errorsTried on WiFi and on LTE
-
@contralto it sounds like if you are using the old anbox... New anbox-halium has nothing to do with anbox-tool app.
Did you follow my updated instructions in the first post?
-
Hi @luksus,
Yes, I do your steps and remount the whole system, changed it to the same priority, upgraded the system and then execute the following command:
"wget -O - https://github.com/Anbox-halium/anbox-halium/raw/lineage-17.1/scripts/install.sh | bash" -
@contralto ok, and did you run the container with
sudo /home/anbox/run-container.sh
? -
@luksus yes.
But...
Oh...
I think...
...all things must be do/installed in this container ?Ops, thatยดs my failure
I will try it again, if I have some time... -
@contralto i will clarify instructions in the first post...
-
@luksus Is there a way to buy you a coffee/beer to help developement along? I'd love to have Ubuntu on the Fairphone 3+!
-
@jesta030 I would want to help too, if possible!
-
-
K Keneda referenced this topic on