Leaderboard

I 100% agree that running inside a chroot or LXC container is 98% of what people would need. But one thing I would gain from using a mainline kernel, is kernel updates almost in perpetuity, rather than running a container on a fork of a 4 year old kernel. Additionally, it provides a path forward in de-blobbing many of the drivers and features inside our phones, which is a security improvement. I understand that right now this is mostly philosophical and problems for future sspiff, but I've been into handheld Linux devices for long enough to have felt the pain of not being able to upgrade

I saw today that both Pros are supported in the current release of Droidian https://github.com/droidian-images/droidian/releases/tag/droidian%2Fbookworm%2F24 AFAIK we should use the fastboot images to flash. Backup your persist partition Download the realease Unpack zip Use flash_all.sh --- First and foremost, backup your "persist" partition. Better safe than sorry. Instructions are in other guides, Please, do not skip that step, there is no other way back to the vanilla persist partition. We are seeing more and more users losing their attestat

In this topic, which I'll update every time I find something useful, I will share configurations that are safe and configurations that are risky that you can try yourself on your own PRO¹-X. Everything shown here requires system permissions. The only way for you to get system permissions is by rooting the phone. There's no way around. That's how Android works. Because these are settings using sysfs. By design, they are temporary. Rebooting your phone will reset them to their default values. If you break something and you don't know how or what, one way that usually solves it is shutt

On Droidian, note that @Benni has discovered this

Hope does strange things to perception. 😉

I'm not very skilled, just been around long enough 🙂 No harm in trying to explain things, I don't mind or take offense to things like that pretending to be above learning things. There is no way for you to know what I understand or know or not, and you're trying to help. I still have my Nokia N810 and there is no modern kernel that supports its LCD or graphics chip, unfortunately. I used to have a ton of Sharp Zaurus (these used to be the gold standard) and a couple of HP Jornada & NEC MobilePro handheld PCs where we used Windows CE as a sort of bootloader for Linux/BSD.

I ported Google Camera to the Cosmo Communicator, which has a "24MP" Quad Bayer sensor (as advertised). My work can be found in the OESF forum. The stock camera app produces horrific interpolated 24MP images with smudged detail, no shadow detail, and often burnt or washed-out colors. GCam produces a clean 6MP RAW image with high detail (for a 6MP sensor) and accurate colors, and 6MP JPEG images of similar high quality. The sensor definitely performs better in low light than conventional Bayer sensors of even higher resolution (for cell phones and tiny pocket cameras). So in my experience,

less slippery? This is huge for me. Fuck.... You are all pushing me into spending too much on a phone again.

Tadi and Bru AI on Telegram are proficient in rooting the Pro¹-X already. I'll try to compile some step-by-step instructions when they showed me how to.

Thanks @mosen Reflashed (edl on linux) stock android, edl reset, and used edl to flash stock persist. I now have landscape rotation, keyboard backlight, but still no main camera. I guess my backup persist partition has become useless somehow. I'll investigate by mounting it on loopback when I have time.

According to the "USB OTG Checker" App the only thing missing is adding "android.hardware.usb.host.xml" in /system/etc/permissions.

Hello, be aware everyone of the following issue: Yesterday I tried to check the GPS functionality with this: https://docs.ubports.com/de/latest/userguide/dailyuse/location.html I turned on WLAN, insert a SIM Card and connect the charging cable. 15 min the device was very hot and shut down. I had recognize it to late because I only looked the display. After that I let the device cool down and booted up again. Greetings

Pff.... Misread 😖

If you want to run mainline Linux out of principle, I totally respect that. 👍 But, on the practical side: what do you think you would miss if you ran your favourite GNU distro in a container of Android, Sailfish or UBTouch, as proposed by @matf-kabouik or @Rob. S.? Many think of an Android/Lineage chroot or an UBTouch/Sailfish LXC as an "emulator" or a "virtual machine", and therefore have the gut feeling that any software installed in such environments would not be "really" running on their phone. That its speed of execution would be slower compared to the "host OS". That it would s

@VaZsogreat to see! Thanks for the longish first impressions! Can confirm, the built quality is excellent imo Kudos to @Erik btw for designing that awesome animated bootsplash logo. Care to share what format you used and where you pushed it to 😅 I could try make one for SailfishOS and UB.

Dear Community, I have just received my Pro¹X yesterday (photoed near a Pro¹): Its build quality is absolutely perfect, it has no rattling effect, buttons are even and not too loose (similar to Pro¹). Its colour is good - I like original black colour but this deep blue also looks good. I see there is some room for improvement at software side (and I have not used it extensively), but so far I don't see its radios are significantly worse than Pro¹'s radios (however, there are some improvements yet to be done). I feel keyboard's backlight is different - either Pr

I received a blue Pro1x today and was planning on flashing it on it tonight, but got a bit sidetracked with LXC containers in SFOS. I have Droidian on a Pro1 and it's really nice and flexible, the main issue being battery life which is not optimized yet. I'll be playing with it on the Pro1x over the night or the week-end, for sure. I was only waiting for the delivery to test it. [Edit]

Confirmed for the 835 Pro1. Toggling that flag causes the Pro1 to ignore the connected power cable and drain its battery instead.

I wonder if that suspended battery charging could be related to the issue behind this:

Awesome findings, thanks. I did not test the (unsafe) battery capacity-faking bit (yet). 😉 The battery charging control works the same on the original (835) Pro1. The keyboard backlight control also works similarly, except that, on the Pro1, the respective sysfs files are located under /sys/class/leds/keyboard-backlight/ rather than "/sys/class/leds/button-backlight/".

Thanks for this heads-up. Having my Pro1 so nicely set-up as daily driver almost feels like a burden, now. If I only had a spare Pro1 or Pro1X for tinkering with such promising projects ... At first glance, I can find no review or video online about Droidian even for the original Pro1, which is strange given it is one of the only three officially supported devices ... @steeb did you test on Pro1 or Pro1X?

I didn't spend a ton of time in Droidian, as I'm actaully quite enjoying using the Android ROM as a daily driver so far, but I did flash it and give it a go. I like that it has a real version of Firefox in which I can install & use extensions. The maps app isn't the worst map app I've ever used. There's a native Telegram app that actually works and may be usable in landscape mode with just a little tiny bit of UI tweaking. Location services worked great. Did not seem to suck down much more battery than the stock ROM. The actual Gnome interface is pretty bad in landscape mode, which is

Ah sorry! that option is for Lineage and AICP not stock android DAMNED!!, so the whole idea crashes, and I believe there is no recovery image to boot into by stock either... So it will require a weird approach of flashing the bootloader for LineageOS or AICP first, to fetch the Persist that way.... Then it is getting (almost) as complex as the edl

Don't think it's your fault, most likely it's just the forum not sending notifications. Waiting on Franciscos reply on what to do next, but i expect to send it to fxtec. Most likely i could fix the speaker issue by myself as it seems to be a contact issue, but i'm not opening the phone before they fix the backlight.

We got it on LineageOS for the Pro1, I do not know if it can easily be added to stock android though.

Same situation here. I had broken sensors, but working attestation, but then when I reflashed my persist backup, which ostensibly valid keys, I lost attestation.

Ditto. After a couple days my Pro1X with SailfishOS seemed to cause wifi problems and yesterday I had to reboot the router twice. Turned off the device last night and haven't had network problems since. The issue I'm experiencing reminded me of the Google home/Chromecast bug that was killing wifi by sending bursts (< 100k) of MDNS multicast discovery packets when the device exits sleep The linked article also mentions "phone" so maybe mobile devices could contain the firmware bug but hard to believe since it was like 5 years ago. If it is the same bug then it would expla

In the stock ROM I've been testing radio connections a lot in these days. I have LTE, WCDMA and GSM. I have a perfectly working Mi 9T Pro. Comparing the signal levels, there is no significant difference (maximum 5%) on any of the networks. I noticed that with LTE (B20 for sure, B3 I don't know yet) the Pro1X randomly drops the network for a moment (about half a second) and reconnects. This happens roughly every 20-100 seconds. I don't know if anything has an effect on it. Sometimes the upload and download arrows next to the 4G icon on the notification bar disappear for a second and then return

Thanks to MaemoLeste, the N900 can run a 5.x.y kernel now (I should try it at some point). However also here, they had to somehow reuse the original closed-source driver for 3D graphics, and sadly, also the remaining hardware is only mostly supported. And that is 13 years after the device was released ... Not to be misunderstood: the MaemoLeste people do great work here, they are just too late to the party. Pretty good illustration of my point above, about how obsolescence catches up with the phones before their support in mainline Linux matures sufficiently for being practically useful. 😞

Before you do, can you try flashing it back (it will break the sensors again), and try if device attestation still works for you? I backed up my persist partition when device attestation still worked (but rotation etc did not), and reflashing the original backup did not restore attestation. I'm just curious if this is just me having messed up somewhere, or if there is more going on here.

EDL works with locked bootloader. Fastboot does not. Might a locked bootlaoder be the issue?

The persist partition is locked in fastboot mode. Rebooting into EDL mode and flashing it with the EDL python scripts does work (at least on Mac and Linux) I see some of these errors while flashing as well, does not seem to affect the process at all - I've checked a couple of those partitions and I can read them back and the checksums match those of the images I've flashed. I've restored to stock a couple of times over the past week and I've had these error messages from the start.

You are obviously very skilled with Linux and embedded systems. Sorry for spamming you with technical details on chroots and LXCs that must be completely clear to you. 😄 Hopefully my post can still serve to encourage others who just want to run a GNU desktop environment on their handheld without sacrificing regular smartphone capabilities ... All your points a perfectly valid, and I couldn't agree more that support in upstream Linux should be the ultimate goal, always. Unfortunately, the mobile phone world being what it is, this often means that the hardware reaches obsolescence before it

Looks like your persist.img broke. Did you backup your persist.img before flashing Linux? If not, then a simple fix to solve sensor issues would be to flash the stock persist.img (can be found inside the .tar.gz stock ROM) using: adb reboot bootloader fastboot flash persist <file_path>persist.img As far as I understand, this method won't fix the lost attestation key problem, but it will fix gyroscope; accelerometer; proximity; and magnetometer issues that occur after flashing from a different OS. Corrections from others are always welcome 🙂

I am using it on Pro¹ and I hope to be available running similarly well for Pro¹X later.

I talked to a friend with a lot more experience in these subjects than I, and he suggested using something like a HackRF One to look at the radio transmissions themselves to see what's going on. That's a little out of my pay grade (and I don't own a HackRF One), but perhaps someone else has those skills. Unfortunately this isn't a local friend, so I can't easily bring him over to have a look himself.

Quite a discussion here if you have some time:

I don't have such feeling - maybe the pre-production unit you have has a bit slimmer backplate.

Also check if Caps changes. And if you are in E.g.Settings search (at the top), does the fake keyboard disappear when you slide open the real one. (Trying to find out if it is the light in it self that is the issue, or it does not detect the keyboard being opened)

I noticed another small difference the Pro1x is ~10g lighter and way less slippery than the Pro1.

You may also check if your Pro¹X stays in landscape mode when the keyboard is open while you rotating the device.

Firstly, congratz! The backlight should auto switch on and off when you slide the keyboard from android build 2.1.0 on. Check in the bottom most settings item for the build number. it should say 2.1.2 since that's what the production run was flashed with. In that case, i'd advise to contact support@fxtec.com. If its a lower build number, you could try flashing a newer on. dd`

Nice! I just received my Pro1X (Black/6GB/128GB) yesterday, just unboxed it today and still haven't played with it much yet. I do have the original Pro1 and used the hell out of the thing. I installed SFOS, an Arch Linux ARM container and some apps, it's one of my favorite Linux PDA.

Nice comparison, and good looking Pro1 (I bet it's a spare)! Thanks @VaZso.

Nope. There were early unit as early as spring 2019. So some half year after that for the first test build an another half year for release bulid of 16 AND that was for a chipset where there were other devices... I do not know how early they have had test units for developers on the Pro1X. At the earliest this spring would be my guess. Does anyone know if there are any 662 powered phones with LineageOS currently

If I recall right @tdm and a few other did the LineageOS 16 for the Pro1 before going public, though they at some point showed some test-versions, see this

...and not necessarily hosted at GitHub or GitLab... Sometimes it is better to filter unnecessary "noises" around a project till a point it needs more testing and it may have more contributors after a specific point of development...

Not ALL on git is public... You could easily have a closed channel for developing something, and later either move it to an open channel or make the channel public

Not necessarily. Even a developer may work on the code locally then release it at a later point in time. Also it may happen some developers are using a specific repository while developing which you will not find officially.

Here's mine, finally got it yesterday! Yay! 🙂 (QWERTZ 8/256 GB IGG order from Oct 2020, with the QWERTY 8/256 GB website order from Sept 2019 hopefully arriving soon too, though no tracking confirmation yet.) Coming from a (shifted) QWERTY, 8/128 GB Pro¹ with LineageOS 18.1 (didn't bother to upgrade to 19.1 yet with the Pro¹ X now actually within reach), I thought going back to stock Android would be a significant change for the worse, but so far I don't feel it is. Except for the right/lower speaker dropout problem, I haven't found any issues yet, which of course doesn't