claude0001
-
Content Count
676 -
Joined
-
Last visited
-
Days Won
84
Posts posted by claude0001
-
-
2 hours ago, EskeRahn said:
The second is that it is virtually impossible to get to things not printed on the keyboard
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 | > { } [ ] ...
-
1
-
-
@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?
-
1
-
-
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.
-
1
-
-
18 hours ago, Hook said:
But the statement you quote is not wrong. It is simply that only one USB-c to HDMI cable works and requires an app and only mirrors.
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 in place to prevent screengrabbing), unlike with true HDMI-out.
-
2 hours ago, xelo said:
I think it's time to close the door and move on.
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, check my website above for ROM updates.
-
1
-
1
-
-
3 hours ago, cdoublejj said:
So basically for those that have them already it is what is it's just a matter of updating lineage os and keeping them going.
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 cannot.
-
2
-
1
-
-
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.
-
2
-
-
2 hours ago, david said:
I didn't realize T-mobile was in other countries.
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.
-
3
-
-
Battery depletion bug.
Send your phone to Fxtec (good luck with that) or fast forward to here:
-
3
-
-
1 hour ago, Rob. S. said:
After all, at least for younger people than me, 1280x800 may come across as rather low-res even on a 7" screen...
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 resolutions as already supported via HDMI-out, the FPS do suffer.
However, the main problem with a higher-resolution built-in display will probably be the increased power consumption of the GPU. The battery life seems to be the weak point of the device already now, even though Valve implemented workarounds like FPS-limiters and shading rate dividers. I guess a FHD+ display won't help with that ....
-
1
-
-
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. If "fn-tab=alt-tab" is super-important to you, please PN me, I'll then make a dedicated ROM for you.
As usual, all my code modifications with respect to upstream LOS 16.0 can be followed from the patch tarball linked above.
Have a lot of fun.
-
1
-
-
@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.
-
1
-
-
@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 to change that sensor's behaviour in my rom. Yes, I am based on the same code and blobs than the last official LOS 16.0 OTA (20201026-nightly) was built from. Of course, on top of that, I include all the ASB fixes that were made in the 2.5 years since. Those are quite a few patches indeed, but none of those was device-specific to the Pro1 ...
-
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 (sometimes) unresponsive keys on my Pro1, but was assuming this was due to the ageing of the keyboard ... Maybe I was fooling myself ... I am currently compiling a test build with all my keyboard-related mods disabled, i.e. with the original driver as it came with (official) 16.0 and 17.1, and will see what difference that makes on my device. Thanks for reporting.
Unfortunately, I cannot reproduce your other two issues:
While I rarely use the original camera app, it does seem to do its job on my Pro1 with my latest ROM (May 2023 ASB). I normally have OpenCamera set as default, though, so I never really battle-tested it.
Also screen brightness auto-adjusts fine during voice calls for me (if set to auto) and can also be manually adjusted using the top-bar slider. But maybe I misunderstand the problem here.
-
4 minutes ago, EskeRahn said:
@claude0001& @steff
The DO have other products than the phones, and they have said that they er using some of the revenue from that....so ... what keeps them from working on the Pro1-X's Android OS or at least explaining why they chose to stop development?
-
2
-
-
15 hours ago, Slion said:
Long spent I figure, I mean they can't afford to pay for shipping and can't refund customers.
Of course they are out of money. On the other hand, as they are neither producing nor selling devices right now, what else is there to work on except software development?
Since last summer they - reportedly - were chasing all those Pro1X bugs with highest priority. And for months they were confident to release a new OTA soon. Then, with the April update, all news on stock Android development stopped. What sense would it make to abort such development at a stage when, apparently, 95% of the work has already been spent?
Rather than financial issues, I suspect that either 1) all their devs have left the company by now and only "management" personnel is left, or 2) they realized that all of the Pro1X's faults are actually in hardware and cannot be worked around with firmware fixes.
Any way, they should at least make a statement about this. They are fully aware that many users are left with an unusable phone right now, and for months have kept their hopes up that a new firmware might improve things. Suddenly going radio silence on this, and instead filling update after update with useless accounts of other people's OS porting efforts is clearly smokescreen strategy and, frankly, disrespectful.
-
2
-
-
3 hours ago, gordon said:
I would very much like to get an Pro1 X but it seems they've stopped shipping
Given that a significant number of Pro1-Xes have been grey-marketed, and given the significant problems it causes many users, unboxed-but-unused Pro1-X pop up on E-bay all the time. It shouldn't be hard to get one if you really want it.
Be warned though: my Pro1-X absolutely cannot work as a smartphone due to missing LTE connectivity in my area (EU/Germany). I have a perfectly-working original Pro1 as direct comparison. The X has quite a number of other bugs, but none is as dealbreaking as its missing mobile network connection ...
-
1 minute ago, Slion said:
Of course they can't keep paying for this when it does not bring any income.
All the income on the preorders and IGG perks has already been generated. They have all that money already ...
-
50 minutes ago, Slion said:
most of us are still waiting for it and those who have it can confirm it is unusable as a smartphone...
Most who actually have one got it via Expansys' grey-marketing (myself included).
But F(x)tec's delays in delivering the preorders/perks is one thing. What is imho more worrying is that all technical activity on their side seems to have come to a halt. They appear to mostly manage the logistics disaster the Pro1-X has become. The bragging about community-supplied OSes in their IGG updates appears like a helpless attempt to mask the fact that their in-house development work has essentially stopped. Considering that the Pro1-X's stock Android (on which also all alternate OSes rely) still has significant bugs, this is bad news for the longevity of the device.
I agree that we have been quite lucky with the Pro1 ...
-
1
-
-
2 hours ago, VaZso said:
Latest IGG update here:
Like they did already in May, they fill their update with information on an alternative OS that is entirely community-developed (besides all this information on Droidian being readily available on this forum anyway).
What about the work the community cannot do? What about stock Android? Will we ever get that update towards which we have been "sprinting" for the better part of a year now? Any news on firmware fixes related to LTE connectivity? Battery depletion bug? Anything at all?
I wonder if the prawn-X might be the first device to be EoL'd before even all preorders have shipped ... 😄
-
1
-
-
On 6/13/2023 at 2:24 PM, EskeRahn said:
Just a thought. I believe there is a chip on the battery side too. Could that be the culprit?
At least for the Pro1-X, the battery connector directly contacts the cell electrodes. Otherwise charging with an external PSU would not be possible in the way that has been shown to work. I'd be surprised if the Pro1 was any different in this respect ...
-
1
-
-
13 hours ago, david said:
Infinix Smart, X5010:
The polarity on that one seems to be inverted with respect to the Pro1-X's ribbon cable (compare the labels P+/P- with those from @Whitey's picture).
Everyone, be sure to always connect your charger in the right way ("+ to +, - to -"). Otherwise bad things may happen.
-
1
-
-
3 hours ago, Wunder Wungiel said:
[deleted]
Edit: OK, had not seen your last edit. I guess problem is solved?
Unihertz Titan Slim
in General Discussion
Posted
... 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 ... 😥 )