Fairphone 3/3+ (FP3/FP3+) Port - Halium 10
-
Hi @luksus, first of all: Thanks for all your great work on this port. I installed it on my Fairphone 3+. In my case, I had to wipe the data partition using TWRP.
-
@Luksus
Same story here, works as you descibed but had to clean data partition with TWRP prior to installation.
I have to say my phone rang when i had a call, so that seems to work too.
Just no mobile data so far.
So happy with this! Thanks a lot! -
@koens & @AlphaZingarus : thank you both, for giving it a try.
Are you also being able to receive calls, if WiFi is inactive?
For me that is currently not working. -
@luksus no problem, with much pleasure ;-).
Just testes again to be sure. Wifi and incomming calls are working.
Just trying to access adb shell. Strange thing is that in device manager my device is now a Remote NDIS based Internet Sharing Devices. Only in boot mode I get ADB.
I follow this tut: https://docs.ubports.com/en/latest/userguide/advanceduse/adb.html but just can't get it to work -
@koens adb is currently not activated/supported.
you can just connect through ssh over usb.If device is connected to your PC, just open an SSH connection for example in terminal:
ssh phablet@10.15.19.82 -
@luksus i must say i had some problems with the connection to my cellular network. When Mobile Internet is enabled, it only works when i choose 2G/3G If 2G/3G/4G is selected then i have no connection at all.
Thanks. Made it work by ssh over wifi. Synchronized my contacts from my Nextcloud server
-
@Luksus it seems that Anbox is not supported yet, is that correct? Any other way to install apk files?
-
@koens No, Anbox is not supported yet and there is no other way...
Until some days ago, Anbox did not work for arm64 anyway, that is why I did not apply it to the kernel, yet.
But since it works, I will try to apply the necessary patches to the kernel. -
@luksus said in Fairphone 3/3+ (FP3/FP3+) Port - Halium 10:
@koens No, Anbox is not supported yet and there is no other way...
Until some days ago, Anbox did not work for arm64 anyway, that is why I did not apply it to the kernel, yet.
But since it works, I will try to apply the necessary patches to the kernel.Good luck with that. Looking forward to this
-
@koens I just updated it yesterday, see first post.
-
@luksus After a week of using it as my daily driver I want to give some feedback: I can confirm all points from your edited first post. Mobile data is not working at all on my FP3+ (no matter if 2G/3G or 2G/3G/4G).
I`m impressed how stable it is running at this early stage. I used a Nexus 5 with UT before and expected the Fairphone 3+ to be more buggy, because the port is not as matured yet. Keep up your great work! -
@luksus Thanks, will update today!
After some days of testing i must say that my wifi signal is weaker as before.
Sometimes I don't have reception of my gsm provider, while it is indaicated as connected. Enebeling and disableing 2/3G fixes this apperantly. Missed some calls that i noticed after a reboot. While talking to a person, sometimes the other person doen't understands me (weak signal i suppose) -
@Luksus
Anbox is ready to rock!At first I had no reception on mobile. Wifi was working.
I shut down the phone, removed battery, switched SIM1 -> SIM2.After that i have no longer wifi, but guess what, cellular data is working now
making calls, no problem.EDIT. My mistake. SIM2 works for calling, no cellular data, wifi works but doesn't show networks anymore. So i don't see i have wifi connection, but i'm connected.
And seems like i can't use the SD card.EDIT2: After another reboot wifi's are showing up again, but have the indication that i am not connected to cellular network, but can make calls.
-
Hi! First of all @Luksus, thanks for your incredible work!
I am trying to flash my FP3+ and eventually I am stuck in the "Fairphone - Powered by android screen"; I've already read posts related to this, but it may be that instructions are scattered or that I am not understanding them properly:Here is what I did, maybe @KoenS or @AlphaZingarus could help me out too.
First, I checked that I have Android 10, unlocked OEM, downloaded latest Halium 10 build and went into fastboot mode. Then:Attempt 1
- Unlock flashing:
fastboot flashing unlock - Wipe data using TWRP, having downloaded twrp image:
fastboot boot twrp-3.5.2_9-0-FP3.img. Then, from TWRP menu, slide for "Swipe to Allow Modifications" -> "Wipe" -> "Format Data". - Flash boot image:
fastboot flash boot boot.img-> SUCCESS - Flash system image:
fastboot flash system system.img-> SUCCESS - Power on the FP3 -> Stucked in android start screen
Attempt 2
- Unlock flashing:
fastboot flashing unlock - Flash boot image:
fastboot flash boot boot.img-> SUCCESS - Flash system image:
fastboot flash system system.img-> SUCCESS - Wipe data using TWRP, exactly the same way as in Attempt 1
- Power on the FP3 -> Stucked in android start screen
Any ideas? Is it related to wiping data process? Am I doing something wrong? Thank you very much in advance!
- Unlock flashing:
-
@thrill_seeker I had the same issues, been playing with this now since this morning.
When you are in the fast boot mode, there is an option to do a recovery.
I re-installed this multiple times now and each time i have to do a recovery. After that things start to work@Luksus
Found out some more problems:- When the screen appears for entering pin code, there also is a keyboard that pops up. Impossible to press the button to accept the pin code then. When i push the on/off button twice, the keyboard is gone and i can enter pin.
- Sometimes i have no wifi icon, but wifi allways works.
- Mobile signal has a x but phone calls works.
- I can enable Anbox now and even install apllications, which is great, but the network is not shared to anbox, althow when i take a look with ifconfig it appears to be correct.
- Anbox applications (testing with DavX now) does not allways starts - first time it works, also after a reboot but then it hangs on a black screen.
- After a reboot i have all the apps included in Abox twice on my screen
Thank you so much for following this up.
-
@koens You are absolutely right! Just started recovery mode and that fixed it!
Thank you very much! -
@koens yeah, I also got this confusing things, except of that mobile data never worked for me.
Sometimes the wifi gets "hidden" by the mobile data "sign", but it is still the WiFi network, which is connected.
As long as WiFi is connected I can make calls...If WiFi is not connected, the phone does not ring or something but I noticed, that the mobile data sign "L" switches to "3g" while the call is incoming. After that, it switches back to "L".
Strange things...
Do you get an internet connection in anbox-Apps?
Just saw, that you don't get internet in Anbox.
I believe that most Anbox issues are not port-specific, but Halium or UBports or just Anbox issues.Regarding keyboard on startup, that bug exists also in the Halium9 version, I am not sure what causes it. You can just swipe it down to hide it.
@thrill_seeker: Great that it works for you.
That recovery mode boot fix is totally new to me... but I have to say, that I don't have an FP3+, but an FP3 with new modules. Perhaps there are some differences in this regard. -
Hello @luksus !
My brand new Fairphone 3+ should arrive today.
The first thing I will do is to install your FP3+ Port !Keep up that great work !
-
Okay...
So installation success.
Boots if I first start it with the recovery mode !
I have tested many things and have more info for you:If I start a navigation program, the compass and GPS seems not to work.
And there is not internet connection through 3G/LTE.All other functions are working nicely.
If you can fix the above, you are my man
-
@contralto GPS should work. If I remember it correctly it is inactive at the first boot, so make sure to activate it.
Then you need to be outside (with a GPS using app active) and it can take up to 5-10 minutes to get the first fix.
After that, it should work.The GPS in UBports is currently not assisted by wifi or mobile network, as it is on Android, which makes them really fast on getting a first GPS-position fix.
