Craig

There is no dream OS. Everything has tradeoffs. But mainline linux with real X support with good touch UI window manager and full android app support with optional full google safetynet (tap-to-pay etc). And if we're dreaming it can run x86 and x64 apps too. And since already getting ridiculous with dreams, also it can run dos & windows apps.

I get a notification that i have an incognito tab open. cant get rid of it. closed every single app, still there.

Thanks much, thats awesome, looks like real ubuntu. and code box is [ code ] and [ /code ] without spaces. So is it possible to run gtk etc desktop apps, assuming they're made for arm/arch? Or are the gui apps limited to whats in their appstore? How bout appimages, snaps, flatpaks, any of those work?

Yeah; I could change the value and confirm it set, but it didn't change behavior. I set it high but In the same terminal it still started repeating fast on longpress, and in apps that support accents the popup appeared fast, so no effect. My default before playing with it was 400ms.

Check out Wikipedia and Ubports Website Ubuntu 16.04.6 was released on 28 February 2019, so if ubports is pulling in upstream stuff that's not *so* far out of date, and 16.04LTS general support goes thru April next year, and extended/security support til 2024. Yeah yeah, I wouldn't mind if its a newer ubuntu base too, but it's not that bad... and I know very little, for all we know they may have a plan within the next yearh to up to 18 or 20... or maybe waiting for 64-bit libhybris, that' d be cool... For anyone running it, I'd be curious the result of: uname -a

Is it possible to increase the delay before OS triggers longpress action? Like increase from 300ms to 500ms or higher... perhaps that could avoid the issue, at least in lineage... when I was stock, usually when I got the repeating letter quick it was about 8 or 9 of the same letter iirc, so however long it it takes do repeat that many letters add it to the delay or something.... I'd be happy to test with an overley high delay (like 1 or 2 seconds) to see if it keeps happening to me, cuz for me its a daily issue.

FYI, I did report this on your issue tracker in April; you marked it as upstream bug. https://github.com/tdm/android_device_fxtec_pro1/issues/52 I was unsure if netmans keyboard driver (pushed to stock early march) fixed it or not since I've been on lineage (which now results in accent chooser instead of bunch of repeated characters) but sounds like still an issue there too...

You've probably answered this in the past but I've forgotten... when it does go official, will we be able to dirty flash official, or should we wipe & start over then?

I do, since December 2019, but not for sale. And I was waiting since 2017; IGG backer.

I wonder who was surprised by getting it earlier than expected. I'm surprised that happened 😉

They exist all right, I've had mine more than 6 months. All good things come to those who wait.

I summarized it on reddit, but the main things are keyboard working a lot more like it should and no more audio crackle.

While I agree with you by using those layouts you can avoid the need for this feature, it is still useful if you don't want to install additional layouts. Lineage includes the standard AOSP layouts. The US International included has dead key on apostrophe, making normal english annoying, and there is no version with deadkeys only with altgr like pcs (and sailfishos) and those addon layouts have. Second, for english users who rarely use accents, it's easier than remembering key combinations rarely used. When used regularly, like é in José or résumé or ¹ in Pro¹ you memorize them etc n

Sailfish 2.0? or the liquidmorphium?

At one point it said summer 2019. You would think so. But the past has shown us this is not the case. The last time they shipped to retailers (dragonbox and clove) forum users (and others) snapped them up quickly, those with preorders with fxtec then cancelling their order. But also the past has shown is FxTec is not always accurate with their estimates. And if that Japanese site isn't even known for reliability, that makes it even less likely. I doubt they'll have them for sale mid July, and based on someone above saying Fxtec told them they won't get theirs til August, it do

I observed similar things when opening keyboard in stock too. It's because the firmware send a keypress when keyboard opens/closes instead of using the android method. This was reported to them last year, we're waiting for a fix in stock. But it is resolved in lineage. Although I see it was sold quite a while ago.

I agree a wiki FAQ would be useful, especially if it was not too restrictive who was allowed to edit. And also glad to hear we can now finally update OPs.

Thought it worth mentioning, if someone wants a non google alternative to stock camera, I assume opencamera would work without google services .https://f-droid.org/en/packages/net.sourceforge.opencamera/

That's great, cuz it sounded like a pretty weird issue.

My understanding is yes. My safetynet quit passing around March, I looked up why, and that's why. Google pushes the update silently. There's more info about it out there and I certainly could be wrong, but I gave up on my device passing safetynet anymore... To the best of my knowledge the only way to past safetynet now is on stock software w/o root.

Yes, that was one of its major points. Google changes just made it impossible to workaround. https://twitter.com/topjohnwu/status/1237656703929180160

This is indeed true. And although tdm implied magisk can workaround, I do not believe this to be the case any longer. In my experience, the problems lack of safetynet cause are certain apps not in playstore (netflix, disney +) and no tap-to-pay.

I'm the opposite. I just don't understand why people would voluntarily pay another bill if their company already was paying for it. When work gave me a cellphone, I ported my number to it so that I wouldn't have to have two phones. Why keep paying for my own service when I get it free from company? But the smartphones offered had no keyboard. And the SIM was AT&T. So i bought my own photon q, hardware mod to add sim slot (thx cornholio), trimmed my company-paid SIM and put it in. Best of both worlds. Personal phone but company SIM.

Seems very disappointing reading this Can anyone confirm *ANYTHING* at all was fixed in this (besides upstream security update that doesn't actually affect most people.) . Very very very very disappointed. I don't get why they're taking so long to fix the software. Give one guy a week and $1000 and they could fix 90% of the problems, and lineage source is open so all those fixes are easy to copy.

It's worked for me since my first smartphone in around 2013 running kitkat. Back then I'd install adblock plus in firefox. So I have no idea what problems you had two years ago, there has never been a time I didn't have an adblock extension in firefox, mobile or othersie.... on pc that's I think *WHY* I started using firefox version 3 or so was for adblock plus, so continued that practice on phone.