claude0001

Because this thread received a like recently: I have moved to a Pro1-X several months ago and have not made any new builds of LineageOS 16.0 for the (SD835) Pro1 since. Even though I liked LOS 16.0 more than recent versions of Android, there is no realistic going back for me. If you really want an updated LOS 16 for your Pro1, p.n. me. I'll then see what I can do ...

@EskeRahn , I think that other thread was much about running desktop-Linux-like systems in chroot environments or similar container techniques that all use the Android Linux kernel. This one is specifically about mainlining progress. I do not think we have that already. Edit: Ok see what you mean. This started to mix in the latest posts ...

No, I think you got me wrong. No offence but, like many, you do not seem to understand what "Linux" really is. Do not worry, you are not alone in this. Especially people with many years of experience in running Linux on x86/64 servers or workstations often make wrong assumptions when it comes to embedded systems, like phones. Android does use a real Linux kernel, and thus is a true Linux system. You can grab its kernel source from kernel.org, configure it to you liking and create your own custom ROMs based on it. The only limitation is that you practically can only run the single major ke

Droidian, like all functional alternative OS's for the Pro1X (Ubuntu, Sailfish, Droidian), works by specifically not using the "mainline" (i.e. upstream) Linux kernel. Under the hood, they all run a minimal version of Android 11, including its original (downstream) kernel version and closed-source driver binaries. That hidden Android OS is then interfaced from the GNU userspace via middleware layers like Halium and libhybris. While this technically works well, it also means that critical bugs in the driver blobs are present in these OS's just as if you were running the original Android 11 OS t

Hi @Casey. Thanks for your thoughts on this problem. Indeed, as I tried to make clear above, I cannot really exclude I did break the antenna contacts myself. One I certainly did. No, I did not track this down because I heard something rattling inside the phone. I had previously opened the Pro1X's main body several times in the context of the battery depletion bug I had experienced, and because of the right-speaker-noise-at-full-charge issue. At that time, I did not pay much attention to the state of the contact springs (I did not even know what their purpose was). Though I do not rem

Let's not jump to conclusions prematurely. I had opened the Pro1-X multiple times, so I cannot exclude that I broke these contacts off myself. One I definitely did, as noted above. That's also the reason why I did not try to make a warranty claim out of this. Then again, two of the connectors seem to really have disappeared, so maybe they were missing from the start indeed. For sure the Pro1-X had its connection issues since the first time I put a SIM in it. Lets see if others affected by the issue find the courage to open their devices, and discover similar problems. Indeed,

@MonCon I've experienced a "battery depletion event" once with the Prawn-X. As documented here: The battery voltage, as measured with an external voltmeter, was "0.000 V" indeed. So booting into whatever runlevel of Android would not have been physically possible any more. In that situation, the only way forward is to charge the battery using some external power supply, as documented in my post above. I guess this is also what F(x)tec are doing if you send in your device for repair.

So, it appears that I was able to repair my Pro1-X's radios. Previously, telephony and mobile data wouldn't work for me, as documented earlier in this thread. WiFi, Bluetooth and GPS had always worked perfectly. It turned out that my Pro1X was missing most of its "antenna" connector springs. My main antenna (aka. USB) board was missing two of its three connectors, and the last one broke off while I was diagnosing the problem. See picture attached. It appears these things are really fragile. Also my "diversity" antenna board was missing one connector, which I found rattling in a

Contrary to popular belief, that setting cannot protect you from the battery depletion bug. As @Sean McCreary clarified in some other thread, Android devices are not really "off" during "off-mode-charging". The charging screen is just a different runlevel of the operating system. The bottom line is that the Pro1X's Linux kernel has to be up and running in order to actively switch the power source from the battery to the USB charger. That won't happen "on its own". So also with off-mode-charging enabled, there has to be enough remaining battery juice for an initial boot of the OS, oth

... as to Reportedly (some?) issues related to WiFi were fixed via OTA. Is your device up to date? (I do not have a Titan, but am seriously considering it as my Pro1's keyboard is getting worse and worse ... 😥 )

It seems like many Titan power users install the Blackberry Keyboard app to improve behaviour in that respect. Have you tried that by any chance? As written above, I'd be most interested in a way to fluently enter all those symbols for coding and terminal work, i.e. things like | > { } [ ] ...

@Hook, he needs the sources, apparently including the exact building configuration. ROMs contain only the resulting binaries in executable form. @pAn : You probably have good reasons for what you are doing. But out of interest: If you kernel project works well with LineageOS, why don't you just use that?

The "stock" kernel sources (you didn't mention if you are on Pro1 or Pro1-X) are available. That's what the LineageOS trees are using. Of course @EskeRahn is right that those do not contain the source code of all the (mission-critical) vendor blobs.

The Pro1X's USB port does not support GPU-out via alt-mode. Therefore things like UBTouch congvergence mode will never work, contrary to what was promised. As far as I understand, the solution that was demonstrated with that "USB to HDMI" cable relies on screengrabing and -casting over a network protocol and thus works independently of the GPU on any recent Android device. The screengrabbing part is probably the reason for the extensive permission requirements. It's also the reason why things like Netflix or Prime cannot be displayed using such tehniques (as they have DRM mechanisms

Agree 100%. This party's over.

I have uploaded a new build of LineageOS 16.0 for Pro1 (SD835) at: https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 It gives you ASB fixes backported to Android 9 up to patchlevel "5 August 2023". There are no other changes with respect to the June update above. I will continue to make new builds of LOS 16 as long as I use my Pro1 or until Markus stops backporting the ASBs, whatever comes first. However, as the Pro1/X community -- and by extension this forum -- seems to be dying, I'm not sure I will keep updating this thread much longer. If you are using my builds

Unfortunately, there are flaws with the devices that cannot be fixed by the LineageOS folks. The most prominent is the the mobile connectivity issue, preventing many devices to effectively work as mobile phones. Then there is the dreaded "battery depletion" bug which results in a bricked device for Average Joe. There are more - less disabling - issues that will never be fixed with F(x)tec being effectively broke, like the "right loudspeaker fail at high battery charge bug" and others... I had genuinely believed the Pro1-X (QX1050) could be a viable successor to my Pro1 (QX1000). It c

Nope. The Pro1-X project is dead in the water, with most ordered (and paid) devices not even delivered to customers yet. Reportedly, the phones have actually been manufactured. But for almost a year, F(x)tec have been unable to pay for continued shipping. They seemingly are also unable to refund disappointed customers cancelling their orders. At least one of their other products (linxdot) seems to be haunted by similar troubles, suggesting the company is nearly broke. I actually expect them to announce end-of-business in one of the next IGG updates.

The "T" in "T-Mobile" actually refers to the German company "Deutsche Telekom AG". The various T-Mobiles around the world were initially independent operators that have been purchased by Telekom and incorporated into their brand. Of course, inspite of the similar name, the radio frequencies in use are different for all of those networks, as they are governed by the different national authorities.

Battery depletion bug. Send your phone to Fxtec (good luck with that) or fast forward to here:

The competing Switch is hugely popular with its 1280x720 pixel 7-inch display, so the screen itself is probably fine for people. One may argue that, as the Deck is (also) supposed to run games made primarily for (larger) PC displays, there may be a case for a higher-resolution built-in display here. While far from a gaming expert, my experience with Steam on Linux (which is what the SteamDeck is running) is that the total number of pixels to be rendered still matters as much as in the olden days. It also seems to be agreed among users that, when using the Steam Deck's (much) higher resolu

I've uploaded another build of LineageOS 16.0 at https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 which includes backported ASB fixes up to "5 June 2023". Go for the ROM dated 20230628. Based on @raymo's feedback above, I have removed @Slion's "fn-tab = alt-tab" patch from the keyboard driver for now. It was the only mod that -- while significantly modifying the driver code -- was never included in any later official LOS trees. Based on my own testing, I still do not think it introduces any problems with regard to keyboard response, but I want to give it a shot. I

@raymo: So I installed a test build of my ROM with all my keyboard-related modifications disabled. I.e. the driver is the same than in (official) LOS 16.0 and 17.1. My sometimes unresponsive keys ("N" is the most problematic one for me) are definitely still there. As I remembered, I get a lot more unwanted doubles ("douubless") this way, as the respective patch introduced in LOS 18.1 is now missing.

@raymo: I'm a bit confused now. I had understood your initial report in a way that, with my unofficial LOS 16.0, you experienced keyboard problems that you didn't previously on 17.1 and also not on your present 20.0? I anyway just built a test-rom with all my keyboard mods and backports disabled, and will test that on my device. However, I too believe that my keyboard in fact just has (small) hardware issues. It is true that the proximity sensor is sometimes slow to react when you take the phone off your ear, but eventually the screen always does switch on for me. I did nothing

Hi @raymo, Thanks for your interest and feedback. So you are saying you had no HW keyboard issues with LOS 17.1, but input problems started when you tried my ROM? That is interesting: My keyboard driver indeed contains several mods with respect to the upstream LOS 16.0/17.1 one, as documented in my patch log. Partly, those are backports from LOS 18.1 and above that are actually supposed to improve keyboard behavior ... E.g. I think unwanted multiple presses of the same key became much fewer (for me) after I had backported the respective patch from 18.1. I do experience problems with