I have been daily driving FLX1 from Furilabs for few weeks now.

Believe me this is the phone which will finally gain some market share to linux mobile.
It has all the best achievements of the linux mobile community.
It has been in market for month and it is allready better than any other linux phone that I ever had (I basicly have/had them all - starting from the BQ Aquaris)

Feel free to ask questions I can try answer. #flx1 #furilabs #linuxmobile #mobilelinux #phosh @furilabs

@alaraajavamma @furilabs No mainline though, just libhybris and Halium. So not actually that interesting

@bart @furilabs

In my mobile linux adventure I understanded that all I wanted was similar experience what I get from laptop linux aka. it should compete with Windows but you can choose how it behaves or looks. Honestly, there have never been options like this before.
In the perfect world this would be mainline device. But I literally have all the options side by side. This is enjoyable to use. Mainline devices are enjoyable to use if you choose to love them before you use them.

@bart @furilabs (I have not tried all mainline devices because thanks to pmos and people like you the list is growing rapidly). So just to be clear I don't want to be rude - I love pmos and I have donated pmos.

But when I said "best achievements of the linux mobile community" I literally ment also libhybris and halium.

This will be the device which you could give to your grandmother (maybe in 2025) and she could enjoy it and make call for you (just an example of the idea - mines are dead lol)

@alaraajavamma @furilabs I just think the fact it doesn't run on mainline isn't mentioned enough. It's not "just" a Linux phone, it's one with caveats. Your kernel is still outdated, you can't run everything you want (for example KDE Plasma), you're missing out on modern components of the Linux mobile stack like ModemManager.

For existing Android phones that could be argued to be acceptable, but this is a brand new phone targeting the Linux mobile crowd. That makes it _not_ acceptable

@bart @furilabs Personally, I don't want another new phone that I crowdfund or donate to volunteer developers that will be almost good (again) in the next five years.
I've seen/been that route too many times already.

I understand what you're getting at and partially agree. Often the problem is just that if you try to achieve perfection, you don't even achieve tolerable level.

Or is your point that you want Furilabs to mention it more clear on the website? I can ask them to do that.

@bart @alaraajavamma @furilabs Sure, it may have a bit older kernel, sure you can't run everything out there in mainline land, but let's be real here, you can't run a lot of things on mainline either. Graphics driver bugs, missing support for hardware like fingerprint sensors and NFC, and to top it off in my testing all mainline devices have a variety of telephone functionality issues. Calling is the major issue...
@bart @alaraajavamma @furilabs For example, on my Librem 5 in postmarketOS and Mobian a lot of the functionality that works in PureOS, like bluetooth headphones in calls, simply don't work. Calling is also less reliable. My oneplus 6 while it now can have working VoLTE thanks to 81voltd (if you compile it on PMOS edge) doesn't have reliable call audio, and even if you get a call where call audio works the mute button doesn't and you can't use bluetooth headphones or speakerphone.

@BrianA 81voltd is packaged in #postmarketOS now: https://pkgs.postmarketos.org/package/master/postmarketos/aarch64/81voltd

I am quite positive that 81voltd will land in postmarketOS 24.12 (or, maybe, before in a service pack, so that you can use stable - which does not suffer from 'breakage by upstream' as much as edge does).

Also, regarding Plasma Mobile: Plasma Mobile 6 is a lot better than previous releases, I am writing this from Plasma Mobile on OnePlus 6, happily accepting rare weirdness for a better virtual keyboard.

81voltd - postmarketOS packages

@linmob That's awesome, but 81voltd isn't the issue, and neither is edge. Even in PMOS stable call issues still happen on the OP6.

Plasma Mobile is definitely a lot better from a few years ago, but I do not think its in a usable state still. There's a number of virtual keyboard bugs and quirks, text selection overlays are broken, WiFi disconnects from time to time (not something that happens in phosh on the same device in my experience), and a bunch of other issues.

@BrianA Edge is part of the problem, having audio stack updates break configs can't be avoided when rolling.

Yes, there are more problems, but they are intermittent and hard to debug - and an excellent opportunity to contribute 😉

Regarding the PlaMo WiFi issue: https://gitlab.com/postmarketOS/pmaports/-/issues/1049#note_825620485 That workaround solves it, and yeah, one could just package, e.g, a daily cronjob that uses sed to alter every config file and pretend to have solved the issue - I am glad postmarketOS don't do that.

WiFi does not autoconnect (#1049) · Issues · postmarketOS / pmaports · GitLab

Describe your issue Wifi does not connect automatically after reboot How to reproduce your...

GitLab
@bart @alaraajavamma @furilabs The Pixel 3A XL only has calls with wired headphones, and the PinePhone has unreliable calls and texts still in addition to the same problems as the others. I am all for mainline, I have several mainline Linux phones for that reason. But I just do not believe it is better. Sure, the kernel is more up to date, you can *possibly* run more if the stars align. But what does that matter when you don't have the basic functionality of a phone working properly?
@bart @alaraajavamma @furilabs I'll take a Droidian device and give up Plasma Mobile (which in itself is extremely buggy) in exchange for a stable phone that I can still enjoy the Linux ecosystem on for the most part, which doesn't spy on me, has fully working waydroid support, has all it's sensors and hardware working, and above all is still open source and is able to get security patches on it's older kernel. Do I wish mainline worked better? Absolutely. But it likely won't for a long time.
@alaraajavamma @furilabs I'm just waiting on 4G and 5G support in the USA and then I'll be going all in on the device. Hopefully they figure it out.
@BrianA @furilabs I don't want to promise too much (because I don't know exactly), but as far as I understand, Jesus got that resolved. It's just incredibly problematic because there can be different operators in different cities and guaranteed to be different in different countries. And again Furilabs want to release only functional updates (as in phones 2024) so it will take a while when you can try out.
@alaraajavamma @furilabs Unfortunately he hasn't yet. The new firmware hasn't yet worked on my device. He did say he had some success with someone else's device.
@BrianA Call support with integrated microphone landed 3 days ago for pixel 3a and pixel 3a xl, feel free to update 🥳
@pan Does call audio work fully now on the device? Is calling reliable? What about texts and cellular data?
@BrianA i didn't have the time to test it, it should be as reliable as sdm845 phones (as long as you disable suspend)
@alaraajavamma @furilabs Have you tried any other UI's besides phosh on it?
@zachdecook @furilabs No. Afaik the idea is more to get Phosh rock solid state - not to support "anything for anyone". I believe it is the only way to make this reality but I am not sure what furilabs people are thinking :). I think I saw someone trying Plasma allready - and it is open source so if someone wants to try something else they are free to do so.
@alaraajavamma @zachdecook While we do not support other user interfaces, Plasma mobile does run fine on our device. Users have tested and came out successful on the latest version of Plasma from Debian!
Although, as mentioned above, we do not provide any support, and any bugs within the stack will not be looked into by our team.
@zachdecook @alaraajavamma @furilabs That'll be hard due to not running mainline Linux with regular Mesa means no Plasma Mobile or GNOME Mobile
@alaraajavamma @furilabs so how is the battery life like ? how much on screen hours can we expect, how much does the battery drains over night ? does the screen dims enough to use in complet darkness, is it bright enough in plain sunlight ? is there a fingerprint scanner ? working ?
@grinceur @furilabs At the moment if you just idle the battery will last something like 48 hours. If you use it constantly maybe 12 hours. Screen is bright enough in plain sunlight but at the moment little bit too bright in completel dark (afaik there is fix coming in the next update). Fingerprint scanner works and you can even use it with Phosh out of the box.
@alaraajavamma @furilabs interesting thanks. last question, are mms supported ? 
@grinceur @furilabs mms support will land on next update (more weeks than months). FLX1 will support even multiply APN connections at the same time - this has been issue with modemmanager/networkmanager stack for a long time but it works in ofono.
@alaraajavamma
I imagine the support is good? Any pain points? Aso any cool points? One reason I find the PinePhone so cool is the extendible pogo pins, only phone where you can actually do a partial upgrade or tinker around with.

@RannyBergamotte Support is excellent, Furilabs people are very friendly and active in Telegram group.

Pain points: I am speaking as end-user and I have not find out anything big. Some small issues but they will be fixed in the next update cycle.

SCool points: this is designed to be mobile phone from the beginning - so it is fast but does not eat your battery or turn hot when use it. Removable battery. Waterproof. Fully working camera. Working finger print scanner with Phosh integration oob.

@RannyBergamotte @alaraajavamma

Just for the record: The Librem 5 has pogo pins for extension. There's a breakout board for that (https://shop.puri.sm/shop/librem-5-rigid-flex-breakout-board/) but you can also do without it.

There's also a breakout board to repurpose the M.2 slot:
https://source.puri.sm/Librem5/librem5-m2-breakout

Librem 5 Rigid-Flex Breakout Board – Purism

@alaraajavamma @furilabs Do you have issues connecting to mobile data? I have those issues sometimes on a Google Pixel 3a running Droidian. Also batman (battery manager) did really cause some headache but that was eliminated lately it seems.

@EgeusGreen @furilabs

Yes and.no. At the moment there is issue that I have to toggle mobile data on/off after reboot before it works. After that it works.

But there are still something odd - like signal shows 5G strenght like 3% and still got faster download/upload speed than from my wifi.

Furilabs are working on both of those things.

@EgeusGreen Hello! Could you give me some details about your mobile data problem? I use Droidian and lately I've been experiencing some problems that I didn't have a month ago. In my case, I suddenly lose mobile data and sometimes there's no way to recover it until I restart the device. Are your problems similar to this?
@anyDr0id Yes similiar, restarting or changing back and forth from 4G to 2G helps sometimes.
@EgeusGreen Have you reported the issue in the Droidian Telegram group?
@anyDr0id Telegram is not for me :)
@alaraajavamma @furilabs 🤩 nice to see phosh being involved in this.
@phosh @furilabs Indeed 😍 . Phosh is one thing what makes this so awesome.
@alaraajavamma @furilabs Does the cellular network work in North America?

@fisherdude @furilabs

I am not in North America so I am not sure. I have been following the conversation in the Furilabs Telegram group and I believe they got it working atleast for one people in the USA.

@fisherdude @alaraajavamma @furilabs Not yet. Only 2.75G on T-Mobile. I gave one of their developers SSH access to my device to work on the modem, so we'll see if they can get it working. The hardware in theory should support the US cellular bands, but they need to be enabled and the modem needs to properly communicate with the US cell towers. They've gotten a connection, but there seems to be a userspace issue preventing it from working in the OS.
@alaraajavamma @furilabs I'm guessing this is using Halium/libhybris?
@newbyte @furilabs Yes indeed. There is one option to mainline it in far future because Furilabs did bought everything (sources etc.) from the manufacturer but now the idea is more to have reliable 2024 standard mobile phone which will work ootb. And it is allready reality - there are some small issues but nothing crucial

@alaraajavamma
@furilabs

My deGoogled android reports my location to my Home Assistant server. It's fairly important for some of my automations.
I'm trying to figure out how to make that happen on Linux phone. Not having one to test on makes that difficult, lol. None of my Linux machines have GPS in them.

Also, I rely pretty heavily on GPS navigation to get around. How well is that working on the FLX1?

@hellomiakoda @furilabs
Should be quite easy because at the moment FLX1 works like this:
If you use android-container the GPS is locked to android apps - and GPS works as good as any modern smartphone. You will get location immediately.
If you use this method you can use the same methods as you use with deGoogled android device.

If you choose to go with linux route you need to first stop android-container. GPS works then also there and there are methods to share location with linux too.

@alaraajavamma
@furilabs

Sounds like the ideal workflow is to eventually migrate away from using the Android container.

@alaraajavamma
@furilabs

Oof, sorry for repeatative replies earlier. Pain can really cause confusion and disorentarion. #embarassed

@hellomiakoda @furilabs No worries.

I am not sure are there any as polished options as in android - maybe with Nextcloud ther is, I am not sure.
What my end-user brains would suggest for an idea:
Use mmcli to get location details and output that for example to txt file.
Then if you wan't do some formatting for that information so the location info is easier to understand.
Then sync that periodically with cron or similar.

But options are endless :)

@alaraajavamma @furilabs So far, it looks like attempting gpsd might be my best bet. But I can't test cause I don't have anything Linux with GPS yet.

I guess plan B is
if WiFi ssid = KodaNet, Miakoda is home.

Wait... I might actually be able to pull that from my router, seeing if [Mac address] is connected. My router is already connected with a HA integration. Broken at the moment, but I haven't attempted to fix that yet, might be as simple as needing to reauth.