Leaderboard

Again @Raksura has helped forwarding an update:

The update is great. The "multiple keys at once" fix has vastly increased my typing speed. Before I couldn't break 40 WPM before I stopped getting dropped keys; now I am 50-60 WPM on a good day. Thank you f(x)tec for fixing this! Before the fix, it was a great phone; now it is stellar.

On the plus side, I might get my Pro1 just after the first anniversary of my pre-order. But then again, since France is about to go into full lockdown, chances are I will not be allowed to go get it from the delivery depot.

https://xkcd.com/2280/

Yeah, the update feels like it has tremendously improved keyboard useability. I thought I'd be stuck with non-responsive keys because it would've seemed a hardware issue but this is golden. No issues here!

No, I pass.

Got it working, there is a bug in the patcher-script, not taking SaR into account. I'll provide the patcher tomorrow after work. Tag me if I forget it.

OK, so not sure if this is actually a bug or not, but need to see if anybody else is experiencing this issue. Note: my device has never been dropped, and this behaviour started yesterday evening. Multiple reboots have not resolved the issue. Essentially, whenever I'm using my device, it intermittently registers multiple touches along a single line of the digitizer, causing completely unanticipated behaviour which as you can imagine, is very frustrating and makes the device very difficult to use - I even had difficulty recording it! (but I managed). Please see the linked video file, w

@acoppens there you go http://pro1.hidingin.space/NanoDroid-patcher-SaR_ONLY-22.6.20200208.zip please do not distribute this file. It is a dirty patch, without any checks of my changes (and I didn't tidy up the changed code because I don't want to set up my Pro1 again). All credits goes to Christopher Bratusek from nanolx.org. I just found bug and made an unclean fix, which only works for SaR devices. Be aware, first flash your ROM (lineage), then reboot into recovery (very important), then you can flash NanoDroid. The NanoDroid SetupWizard configuration should not be stor

I use a magisk module under LOS called safetypatch that makes it pass. I dont think re-flashing will do anything different. Besides bootloader & root, lineage test versions dont have selinux, unsigned, etc, so more reasons to fail.

I have seen several wishing for that. I remember for my Xperia (Neo) Pro that it was quite handy - but that was at a time where portrait was used primarily for phone calls. But what about some smarter version of that! Lock the display IF you do not interact with he display after close in say 3s (could be same lock time-out slider as the flip close) It could EITHER be implemented by turning the display off, but allowing a Power press to turn it back on OR it could hesitate turning the display off, perhaps with a pop-up count-down. that people could just touch to cancel, say "Locking i

Just released v0.6.0 adding support for locking the screen upon closing your keyboard. Mostly for people not using flip case I guess.

When I was at the supermarket the other day, the liquor shelves were still well-stocked! 😉

There was one offer from somebody who doesn't have the devices either... I'm still looking forward on buying a Pro1. I'd even offer a bottle of desinfectant!

In case anyone is wondering, yes, it is possible to scrub down the Pro1 keyboard with 70% isopropyl alcohol without causing any damage. No prizes will be awarded for guessing how I know this.

In theory, yes. But actually it isn't that simple; there isn't only "infected" and "not infected". Technically there is group of "infected", of which illness has been proven by corona virus test, and the other group is "unclear", which includes all the people with no symptoms. So it includes: a) healthy, not infected people b) infected, but no symptoms, which can further be divided to: a) no symptoms yet b) no symptoms to come These last two groups are most dangerous in hospital world, because they are mistakenly threaten as "healthy", so they can infect both staff and

Now this is interesting.....if the nurses and doctors have the same disease as the patient, there's no danger of provider to patient transmission of illness. As long as what everyone has is known, people with mild cases can treat those with severe cases of the same thing. Internal segregation in the hospitals should already be in place, and make this possible. Of course you'd hate to be that doctor or nurse who has to work while you feel lousy, but sometimes that's life. Sometimes we all have to work when we feel lousy. Thus far it seems that the biggest danger is not how serious the illn

I just got my shipment of 1600 black dots from the UK. It's 8 sheets of 200 dots. They look perfect for the Pro1 screw covers. Whats more, I believe cutting one dot in half would work for the keyboard corners. Lol. 1600. 😄 😎

...Suggestion: Left of the "Cancel" add a "Lock now", can make sense if people have set it a little high, and do not want to wait, before putting it in say the pocket. Of course we can just press the Power, but would make sense next to "Cancel", and Power could have it's own delay, is selected in the standard settings. Have you any news on getting it to work on LineageOS? The sensor here act somewhat different, repeatedly sending a close, and a different key...

Well, yes, some of those high proof types will do it. Maybe a little more expensive than isopropyl alcohol. Lol

Minor bug with new function. If you open&close when locked, and then touch the fingerprint to unlock, it does, and count down to lock again.... (And for some reason sometimes the box is shown slightly smaller without the cancel - I have not been able to spot the pattern)

80% Stroh Rum? (that is 160 for the US public)

My initial idea too but it turns out Android won't let you do that apparently. Even turning off the display without locking the screen and without the proximity sensor is apparently not possible. If you think about it does make sense too.

That's exactly what was implemented 😁

Strong enough to feel good, not strong enough to kill the virus. 🍸😁

I wonder about that... People may touch the popup... I'm afraid of a "good intentions; bad implementation". IMO, it's really hard to know if a screen touch is meant as a "continue using" or as a "ups, I touched by accident". Maybe canceling the lock by mistake can be mitigated with a noise and rumble? Just bringing this up to avoid no one thinking about it.

So, I was planning to jump to LOS Test 11 when I took a look at the issue tracker and saw that it is still being reported as not working with Verizon. That would be a deal breaker for me and I would have to very quickly wipe and return to stock. While part of me say "Aw, go ahead, try it. Maybe it will work for you 😅" most of me is hesitant to go through all of that just for a short test. @tdm What is the status of this. Will it have to get worked out before it becomes official? Is the path to solving it understood? What is your confidence this can be solved soon? This isn't a d

Good luck getting alcohol nowadays!

Indeed. And this isn't a matter of a decision between leading an unhappy life in senseless panic and fear on one hand vs. a happy, fulfilled but risky life on the other, either, as if those two were the only options we had. If someone can only lead a happy and fulfilled life in acting risky and endangering others, if taking just a few easy precautions and minding just a few restrictions for a while to help keeping others alive and well will make someone's life unhappy and unfulfilled, I feel sorry for them. By the way, things are accelerating around me – I've been suspended from work this

I saw both situation on stock OS, reboots in idle or while using the phone.

As long as you follow the instructions and you don't install anything that modifies the system partition, then you should be able to update via OTA. You just have to be sure to follow the proper steps before and after you do the OTA and don't reboot in between.

I still had only two reboots on the same motorway and same direction where signal probably was very weak but the phone was in my pocket both times. After last reboot, I was on the same road once more without reboot...

All of that makes sense to me. It might not be obvious at first but you have to take in account how Magisk operates. The OTA will only update a clean boot image (it's a delta update, so it wouldn't work even if it let you). So you have Magisk uninstall restore the old one. Uninstalling Magisk means having an unpatched boot image. That is what Magisk is. Due to how Magisk operates, this change will only apply to a running system after rebooting, so root persists until then. This is good since now the boot image is clean and can be updated but there's still root to read the boot partition and

Xperia X Compact is a different story since it's based on the same socket as other Xperia Xs (Snapdragon 650). XA2 are using Snapdragon 630. As I am not an expert on porting I'm not sure, but as I have understood, the socket is pretty much the most time consuming part of the porting process (i.e. fixing the compability bugs). Alien Davik is however closed source and Jolla has done some tinkering into it for the latest Android kernels. Android support for community devices has been in discussion multiple times, but so far we have not heard anything concrete. Best effort was and idea that som

Thank you, David, for providing instructions. I will add some particulars of my experience installing the OTA that showed up a couple days ago on my rooted phone. I uninstalled magisk using magisk manager. I clicked "uninstall" on the bottom and then "restore images." I think it's probably important to choose "restore images" rather than "complete uninstall." It said "restore complete." Then I downloaded the OTA. The second screen "Installing.." said 100% with no status bar. There was never a dialog to reboot. Finally after waiting several I hours, started poking around to see wh

I updated mine to 80.0.3987.132, and I still see "Add to dictionary" and "Delete" in the list box.

So far just about everything in this OS is working well for me (many thanks to @tdm!), except that every 3-4 days either the display does not wake up on any button, or it does but the digitizer does not register touches. I would then either hold power till it restarts, or (if just the digitizer is unresponsive) I would use the keyboard to press "restart". I imagine there's probably not much that can be done about this without logs, but how would I go about getting logs for incidents like these?

Yes, I heard the same. And hospital personnel have to work even if sick. Horrible decisions for doctors to have to make, not just once, but continuously.

I'm hearing from someone with contacts to italian medical personnel, that some hospitals already have to use triage, that they already need to make the choice which severely affected covid-19 patients will get treatment and which don't (= will be left to possibly die, although saving their lives might very well be possible). And this still is only the beginning.

Production and software updates are the fault of IdeaLTE. Lack of communication is clearly the fault of FxTec.

This issue is fixed in the latest OTA-update. There is also a work around available: - https://f-droid.org/en/packages/com.punksta.apps.volumecontrol/ Please, use the search function next time since this is third thread to same issue. https://docs.google.com/spreadsheets/d/15uE12Yv5nMvIF42U33cY5FQoF6M66QIn00cC876uf7Y/htmlview#gid=0

A little graph from here on the age distribution of the mortality from China. The numbers are from this report. (attached) COVID-19[1].pdf

Regarding SafetyNet I'm not entirely sure but I get the feeling that keeping an older Android version doesn't mean you'll be fine. I only have very surface level understanding, but while the key attestation is not fully enforced yet across the board, served sided checks and Play Services updates should bring it to older devices all the same. The server side check will prevent any modded Play Services to get around this. And since the data is signed by the hardware that you have no control over at all... yeah, good night.

Good point. Yes, this is crucial! 😁

Thanks, works like a charm AND you forgot to advertise that it nicely re-awakes the screen by the magnet only, if re-opened before the Lock-time-out. 😎

Just released v0.4.0 : Screen goes off as soon as you close the case whatever is your lock timeout. Seamless brightness adjustments using ALT+UP/DOWN if you are using Fx Qwerty or other keyboard layout providing brightness control. Settings look better and screen brightness is easier to access from there. Remember long press on the Fx quick settings tile take you to the settings.

You need to do one yourself 🙂 I've used Huawei P20 Pro Cases - Snakehive. Search the forum for more screenshots. Minimal modifications needed. Then you need to slide in a flat magnet at the right position in the credit card holder. I used some sticky tape to keep it in place. It's totally invisible. Some of the app features do not need a smart case though.

https://community.fxtec.com/topic/2075-protective-case-suggestions-and-ideas/?do=findComment&comment=44757