Leaderboard

I have been playing with chroot on the Pro¹ lately, extremely happy with it, even though it is still rough around the edges. Even my N900 never felt so close to an actual pocketable computer. Therefore, moar pics. I typed this post and uploaded images using the Pro¹. cmus (not affected by SFOS volume, but it has its own volume settings anyway): cmus and nnn file manager side by side, I really appreciate tiling since SFOS does not allow that: And an additional tile for another tool: Some random programs in different terminals in Tilix and the sidebar showing c

Yes exactly! That is the point! We are concluding on assumptions. Some seem to assume they are crooks and deduce from that, I assume they are honest and deduce from that (as a Dane I'm a little handicapped here, we generally trust people unless we see they do things that proves they were not worhty of our trust). Nor I nor they can prove or disprove the point of view with the information we got. It is like arguing between religions - totally fruitless.

I don't feel the situation as bad as @Gon009 feels. Personally, I have learned these button placements. I agree fingerprint sensor could have been placed a bit higher as I have also touched it occasionally but otherwise I can find convenient positions of my fingers to use it, so it may not be a huge problem. However, it still has bugs in software like forgetting fingerprint settings after reboot. For me, it is a really good device. Performance-wise it is very good, keyboard is awesome, and the image quality of the screen is brilliant, GPS reception is perfect (better than on my prev

My phone is from clove.co.uk too, have try to lift screen now with nails on each edge and all corners - now, i can't, and there isn't any gaps, looks like monolith element with case, despite the fact that my device already was disassemlbed in the phone service some days ago.

Well, @silversolver, you are probably gonna hate what I'm about to say. The reason why I want a refund is that I already own it. I'm writing this on the Pro1 and I'm very happy with it. I got it on DragonBox. I kinda feel bad for skipping in queue but I also absolutely love the device. I'm just worried because I got a very fast answer when I first contacted suppot and now it's silent.

This is definitely not by design, impossible on my unit, the whole edge of the glass is supposed to be recessed. I think the screen is even supposed to be glued (not strongly but enough to dustproof) on the edge. I think you should contact support to get it repaired or replaced.

Then you should be aware of the differences between that and a company like F(x)tec. Differences which substantiate different judgements about delays for both, the perhaps most obvious being one sounds more like B2B and the other is B2C. If you cannot see that for yourself, or what such differences actually mean, I wish you good luck with your small company, which you then might need more than you might like. P.S.: I would have ordered the Pro¹ for the price they were asking even if it would have come with the Snapdragon 636 I've currently got in my Moto Z3 Play, which is already more tha

Yes, indeed. And you knew that when you pre-ordered, didn't you? No-one forced you to. You could have just waited until GA. In constitutional states the general principle is to give the accused the benefit of doubt (in dubio pro reo), as long as there is no evidence against them. One of my most important IT forums which is, all in all, moderated liberally, has a general rule, though, of not allowing an accusation of lie at all. That's on the simple grounds that it is significantly harder to tell whether something was deliberate than to know, subsequently, that something turned o

Ç or ç (c-cedilla) is a Latin script letter, used in the Albanian, Azerbaijani, Manx, Tatar, Turkish, Turkmen, Kurdish, Zazaki, and Romance alphabets. Romance languages that use this letter include Catalan, French, Friulian, Ligurian, Occitan, and Portuguese as a variant of the letter C. It is also occasionally used in Crimean Tatar and in Tajik (when written in the Latin script) to represent the /d͡ʒ/ sound. It is often retained in the spelling of loanwords from any of these languages in English, Basque, Dutch, Spanish and other Latin script spelled languages. 😉

I don't find it amusing at all. The Titan is a "simple" form factor. The Pro1 involves more construction than that slab, so I'm not surprised the Titan is in the wild faster than the Pro1...

You do realize this also works the other way around, right? There's no proof that they weren't lies, and it practically can't be proven nor disproven since that would require in-depth internal information on the production status and such which they're very unlikely to share. The assumption in that case is that F(x)tec isn't lying, but there's proof of that for some of these individual statements. Sure there are previous situations in which they were truthful and honest, like offering refunds when the keyboard mod crowdfund didn't go according to plan, but that's not proof that these individua

Please note that I'm independent, so don't blame F(x)tec for anything I write.

That is not possible. If it were, anyone could do the same and it would defeat the purpose of verification. Only the OEM has the signing key and only the OEM can create signed images to pass verified boot. As mentioned, yes, some of the IdeaLTE bits/blobs are used to build Lineage. But only those necessary to support the hardware. In general, OEMs that do stupid and/or sneaky things place them into the upper layers of Android which Lineage does not use. Briefly, code running on Qualcomm devices (and most/all Android devices) can be divided into four broad

Idk, it looks fine on my end

I've always said that the curved screen was a mistake, but it may have been inevitable; my understanding is that they couldn't find a supplier for anything else since that is the current fashion trend (and yes, it is all about fashion.) I despise working in portrait. This is why I don't daily drive a pristine and perfectly-functioning PRIV I own. I still use a Droid 4 as my daily driver. I bought the PRIV to replace it, but couldn't accept the portrait keyboard. I work in landscape almost exclusively. I take the phone out of my pocket and open the keyboard almost 100% of the time unless i

The keyboard of Pro1 itself is great but suffers currently from software issues that are being worked on. Once they fix it it will be a mile better than virtual one. Also it takes a lot of time to learn to use it properly. The performance is also great. The phone looks great with opened keyboard but as soon as I close it I feel like the "magic" goes away. I used Samsung mid-range phones before and I hated their performance and planned obsolescence but now I see that they were much more comfortable to use in portrait than Pro1... not because of size but because of button placement, every button

I did not mention letter shifted qwerty being a flaw at all. The wobble is in closed position at the bottom of the phone, it wobbles from the left to right making sounds when it moves. I asked people here about that and so far nobody else had the same issue. By "right side buttons" I meant volume, power and fingerprint sensor. Not the keyboard. I feel like you completely didn't understand my previous post. Where did I want a PC with phone capabilities? I wanted a smartphone with keyboard and issues I mentioned happen in portrait mode. The phone is annoying to use in portrait,

I think you are spot on, on our current needs for the large majority (if not all) of us interested in the Pro1. BUT if there will not be a Pro2 in a couple of years, then the Pro1 might have to last for ten years, and if so we would like it as 'modern' as possible to last usable as long as possible.

As of comments previously in the thread, they just started retail sales before serving the pre orders... And there is nothing "flawed" in the Pro1 design. It would be just as silly at to claim that it is a "flaw" of the Titan that you need to open it to use the display.. To be fair the Pro1 just targets a user group that want a phone with a keyboard and not an ultra portable pc with phone capabilities. Different target groups, though with overlap. No need to bash either. And @michael.bosscha I would not call the hinge of the Titan simpler, just more traditional. Actually I think it i

The problem with Pro1 is that most design flaws are not related to being a slider. Bad placement of right side buttons(the worst I've seen in any smartphone), bad camera button(the worst I've seen in any phone, there's no press feeling between "focus" and "make photo" stages), loose sim tray that makes sounds, curved screen that in my case I can lift with nails at the sides and only one flaw that the Pro1 has because of being a slider, the wobble on the bottom of my unit, is there because the bottom part of the phone lacks the second support like the top part. It can't be fixed with simple sof

This doesn't look right to me for what I can tell from the photo there seems to be a gap between the screen and the part it is attached to. There is definitely no gap where dust could get in on mine, I would advice to contact support about this.

UR behind the times 😪 this was mentioned yesterday: And already given a credible response: On ‎1‎/‎10‎/‎2020 at 6:41 AM, Artemis-kun said: The thing with Unihertz is they are a Chinese company based in Shanghai, so of course they get automatic priority over any other companies looking to do business in China....

Well this describes sort of in the core of any conspiracy theory or religion. An unfounded claim that can neither be proven nor disproven. So many logical deductions start with an assumption, that people tend to forget the assumption was there. You even see this in what is seen as science. You build a logical self-consistent structure, but forget that it is based on assumptions. Astronomy is a clear example, forgetting that they got several basic assumptions. e.g. "constants of nature", assuming that these are really constant over the entire universe, and in all its lifespan. Some religio

@tdm Thank you so much for the information you're posting here, it's very interesting. I do have a question about the "firmware" though, some people say that custom ROMs will lack the firmware updates that official (still supported) ROMs have, and thus can be less secure in that way. Are they talking about what you're calling the "vendor bits" for hardware support? And how out of date could these be for this ROM or LineageOS for the Pro1?

This fallacy again huh. I already did, what's your point? That apparently it's okay to slip dates by half a year? That delays are bound to happen? That communication like this is the only way things can go? Getting real tired of this. And that means this time you're guaranteed to get it? This is a startup, and there are risks involved. It's absolutely possible that they'll not deliver all devices, though I hope F(x)tec will prosper obviously. It's not a "hoax", that would imply they planned to never deliver and just run with the money. They've already delivered (a small number

That's correct, it is a separate issue in the same driver. The latest version of the driver I have is merged with those changes also. (I may have stated otherwise in the past due to not realizing merging with newer driver from stock inadvertently to me also fixed the crashes.)

My imagination is better than patience. I am a software and hardwear engineer. Also a co-founder of a small company that produces equipment for aviation. Believe me, no one would ever contact my company if I had promised one delivery time, but I would have done another time. This is not serious. And do not forget gentlemen, while we are waiting here, our phone is "aging" snapdragon 835 - a chip that is almost 3 years old. I do not want to water anyone with dirt, I sincerely hoped to get my device in 4-6 weeks.

This reeks of a TCL NDA that prevents others from finding out about the thing no one was supposed to know about!!1!!1111!1!!11 /silliness

Thanks @tdm for this build, this is awesome. My only question is, in the absense of OTA, how feasible is it to create updated builds? And I presume there'd be no data loss on upgrade, like updating LOS? I noticed that last week when I did my first LOS build for my Droid 4, Android security patch level is "5 December 2019".

Well, this looks promising... tommy@neuron:~$ echo x > foo tommy@neuron:~$ fastboot flash avb_custom_key foo target reported max download size of 536870912 bytes sending 'avb_custom_key' (0 KB)... OKAY [ 0.009s] writing 'avb_custom_key'... OKAY [ 0.003s] finished. total time: 0.011s tommy@neuron:~$ fastboot erase avb_custom_key erasing 'avb_custom_key'... OKAY [ 0.003s] finished. total time: 0.003s tommy@neuron:~$

The original driver may indeed miss keypresses if you type fast, I tested similarly typing "fjfjfjfjfjfjfjfj" and similar sequences fast and it would give something the likes of "fjfjffjffjjfj". Currently all I can provide is a boot+vendor image that require a factory reset to be installed and break OTA but fix this issue (if you need it let me know, i haven't written proper instructions down as of yet and it's sorta confusing), but soon an OTA update should come that fixes this. [edit] Note that if I am not mistaken this happens in the relatively rare situation where the driver is still

(Calm down, it's just a meme)

I hope this device isn't all just one huge hoax … with delays upon delays and the lack of information regarding the delays makes me think it is... but with that said I'm still waiting. I wont ask for a refund just yet … I know it's coming .... shortly

Yeah I cannot believe how people can be upset after being repeatedly baited for 6 months straight. Even worse, they dare to have some doubt about statements when others have not turned out to be true before! Shame on them! If we're having a patience contest here, I have a Pyra pre-pre-order from October 2015. It's all about how it's handled.

Page load really is quick, much faster than with the Sailfish Browser, and it can handle up to ten tabs with no memory issue. Scrolling is fast, sometimes too fast, you have to be more gentle than with a mobile browser. Most of all, the video shows that I can operate tabs and navigation just from the keyboard (new tabs, close tabs, focus address field, reopen tabs, switch tabs, previous/next), which not only feels great, but also is very efficient and faster than anything else I could imagine on a phone. Coming back to the Sailfish Browser really feels painful just when I need to open a tab or

So I've been thinking about this custom key that AVB allows, and I've also read a bit of the source for abl where it's implemented. I've come to the conclusion that AVB is worthless at best and dangerously misleading at worst on devices that have Secure Boot (*) disabled, and the Pro1 is such a device by design. Let me explain... The security that AVB intends to provide is to ensure that you are running code that has been signed, either by your OEM or by your custom ROM vendor that does AVB signing (Copperhead, Graphene, etc.) Note that it does not ensure the integrity of your d

Thanks for the detailed thoughts. I'm still lurking the forum trying to decide whether to get one once they reach retail availability, and it's good to see thoughtful feedback, positive or negative. Right now I don't know if I still want a Pro1. My phone is an important communication tool and my de facto primary computing device. Virtual keyboards suck so I do want a physical keyboard, but not at the expense of the rest of the device's functionality. I'd rather have a good phone and put up with a virtual keyboard, than have a keyboard on a bad phone. I await with interest what happens in

In this case, I would take "firmware" to mean everything closed source. Particularly the abl partition and the vendor bits for hardware support which occasionally have security issues. The official Lineage policy for device maintainers is to assert on the latest firmware version from the OEM (eg. fail to install if it is out of date). Some maintainers are better than others at following through on this. Here's an example of how this is supposed to work. I have been using OnePlus devices for the last year or so. Every time they release a new firmware, the maintainer

I really hope they will update their driver in next OTA which includes also this improved keyboard handling.

Weren't the only one. I went through 2 before I moved on. I loved the priv.

Esc only do Back in the stock version, that is one of the things fixed with FinQwerty, using the Fallback

So, I've looked into the keychar files that Eske provided. Thanks again! We have a "ç" with ALT+c (which is interesting since I thought that's only used in catalan spain). Some accents are typed with [vocal] + ALT which seems strange to me. But as they wish... FN+[key] being used for many different characters seems very odd to me. I'd probably change that to ALT or SHIFT. Also, I think to know the reason for the non-sticky shift key. It could be the keypad type not being "ALPHA". They used "FULL", which has a different behavior. I don't know though what happens to "FN" if that's chang

Different launchers will handle the landscape/portrait shift differently. So you might be better of selecting a quadratic paper where the two crops will be suitable for your launcher. Some I have tried make the crops like a rotated T, or an up side down L

I agree that currently FinQwerty is close to being a must. I simply can not understand why the stock does not duplicate the shift and fn action on the digits and symbols key. I can not imagine why anyone would prefer shift ignored. So though FxTec strictly has handled the keyboard-driver, it is far from optimal - and it seems pretty silly on a device where the keyboard is THE selling point, to not do the utmost to deliver a perfect keyboard experience stock...

The soft button is the least bad option available for me too. Personally I would wish Android made a "Late auto-rotate". That is you would have to tilt it to say 90+30 degrees before it tilted 90 (and you tilt it back to 90). This way you could lie down on a sofa with the device without triggering the auto rotate, and only get the rotate when you actually want/need it, and more inuitivly than pressing the soft button.

@Artemis-kun – I agree with virtually all of what you said (and appreciate your saying it) so far. Just two remarks to minor points: While that would surely help getting an understanding that could prevent most of the rants, it sounds a bit like "do not criticize if you can't do it better yourself", which wouldn't really be an acceptable argument... Oh, there are many other reasons for that. And I guess we shouldn't overestimate the importance and the potency of just a handful of complainants, even though they're particularly loud and persevering. And after all, it's like every

You guys must be living on another planet, the cosmo updates are light years ahead of fxtec's abysmal communication: https://www.indiegogo.com/projects/cosmo-communicator#/updates/all They have delivered over 3500 cosmos, whereas fxtec regularly promises that "all pre-orders will be shipped by X" and doesn't even ship much stock at all. You remember when Erik wrote mid november that all is on track for completing all pre orders by christmas with surplus stock? Do you realize now that they hadn't even STARTED producing 3/10th of the stock at that time (since we are told that this batch was

Unmodified letters and digits should be fine in any layout (except the adapted German QWERTZ) on QWERTY Pro1s as the driver sends the correct key code for those. Everything else probably not. And since QWERTZ Pro1 is just a different keymat and nothing else, every unadapted layout will be shifted. At least that's what I've gathered from looking at the driver source. Can't confirm this theory myself due lack of phone.

It's incredible how a Kickstarter qwerty phone (Unihertz Titan) actually released during the time period they had actually promised and this phone three times the price, with glossy pictures, active Instagram, v etc cannot provide proper dates for pre orders. Specs read old last year, today they read ancient and let's pray to our gods that the keyboard sliding mechanic turns out good/is robust... I have a feeling I might have bought an out of date expensive paperweight that I might not get until March... Jesus H! This is so disappointing...

Yes, I experienced something similar. If you start with the 3.2.0.12 release then zypper update, you'll loose mobile data/sim cards. The fix is to update to 3.2.1.20 right away, following these steps (recommended by TheKit): devel-su ssu re 3.2.1.20 version --dup dd if=/boot/hybris-boot.img of=/dev/block/bootdevice/by-name/boot_a sed -e "s/return allowed/return Orientation.All/" -i /usr/lib/qt5/qml/Sailfish/Silica/Page.qml