Leaderboard

Just installed it and it looks like the certification issue is fixed cause I can now download disney+ 😁 It did not fix my touch screen issues, unsurprisingly...

Flies with honey. Ever just talk to them and say hi?

There's an OTA available right now: QX1000_EEA_20200620223710_20200620-2238

@VaZso I got it too, installed it but I am not impressed. The audio crackling is still not fixed in games even though Lineage had it sorted AGES ago. I wish they could cross update or send each other bugfixes or whatever because it's pretty annoying... A change log would be nice too. But at least they finally got this one certified so it's getting pushed out now......

I see you mentioned Intune in the post title. FWIW I installed Intune on my Pro1 (from the Google store) to access our corporate systems with no issues, working fine. Locked device, In Fastbood mode I get the same screen as you (except that my serial number is visible - guessing/hoping you blacked it out) - that is, no Secure Boot, Device locked. So I don't think Secure Boot is your problem (at least not specifically for installing Intune). Only difference I can think of: my device is showing up as Certified in the Play Store, though I'm on the 20200304 OTA. And that doesn't mean it passe

A lot of the retweets from the official Twitter are from Japanese users I find.

Wow it could get pretty big if they really manage to sell in Japan because they love "old" tech, many companies still use fax machines lol.

I simply hope Fxtec to be fair toward pre-ordered customers. In Japan, a retailer announced today that Pro1 will be sold on July 4th.

Just ran the update.... was stuck on the Pro 1 screen for a bit but turned over eventually. So far I see: - Qualcomm Camera button bugs are all still there (no preview when launched with camera button, brings you to the home screen when you try to select a camera mode) - Widevine still only L3 - ESC key still doesn't work and brings you to the home screen - Audio still goes snap crackle pop Yeah, I don't think this fixed anything aside from the security update. Probably only pushed to fix the "userdebug9".

You are one of those with the not yet certified software... 😥 EDIT: I have just been offered the new OTA update.... Just checked it passes SafetyNet check now. 🙂

On the bright side, as far as my understanding goes, the crackling can be patched without having Google to certify the new version (only needs to happen for security patch levels). So let's hope they can get to that now. Long overdue anyways, considering how often they put gaming into the spotlight on the Twitter account.

My Pro1 also displays this new firmware (I am currently on the update which was available for a short time and had safetynet lost, so it may be the more complicated part of the upgrade arriving). It wants to download 265MB of data and has 20200620223710 in its name. I will install it later (maybe late afternoon / early evening). Edit: Security patch is 2020 April

The fingerprint storage in /persist is probably full: https://community.fxtec.com/topic/2799-deleted-fingerprints-not-deleted/?do=findComment&comment=45138

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.

Another: AptX (HD) still doesn't work.

As @Slion mentioned most were on 0306 and did NOT have the issue. A few had 0304, and we did have problems. And a few had an early 0411 version of the April security update delivered with new phones. We are yet to hear if they automatically update correctly to the new 0620 version, or they would need to flash an older.

Very few early adopters had it, including myself. Once we reported the issue they withdraw that OTA. Unfortunately that meant we got stuck with broken cert for months. No Disney+ 😱😁 Since I'm a lucky guy my touch screen started malfunctioning a couple of days before they eventually fix it 🤣

Maybe they already know something - I also hope pre-ordered customers will also have a surprise soon (I know nothing anyway).

Just checked it passes SafetyNet check now. 🙂

No. This a userdebug build (which shouldn't really be on shipped devices, but eh), so it's not certified by Google. But it seems like an official update just came out (finally!) that should fix this issue. I don't have a Pro1 myself right now, so I don't know if you can just update from this build to the new certified or have to reflash completely, but either way you should be able to get Safetynet working on this device with the right OS version.

That sucks!

Maybe the most important part was the security update itself but I hope they will also work on bugfixes.

Yeah, sorry, did not mean it was due to the OTA. But because of the OTA I had te reboot, which meant no more FP 🙃

Just published release v0.9.8 which improves some settings screens.

Just received an OTA April 5th 202000620-2238. Installed it, reboot, no more working fingerprints again pfffff. Guess I'll have to root to fix this annoying bug.

Wait what? Since when is that available? I tried Firefox roughly 2 years ago and I'm very certain that you couldn't install any add-ons back then... In any case, thank you for telling me that!

Thanks for the input folks helps a lot. I checked the play protect and it is not certified. I assumed locking it would enable this but completely forgot to check. ( My inexperience with dealing with under the hood android) Phone version My question now is should safetynet be working on this version?

If the charger is not really good (maybe noisy) it can happen. I have also experienced it with older phones and not really good charger.

But it could be somehow related that the touch is sensitive to the electric potential, and as other have suggested static charge. Try (for the test) to make sure you are grounded by holding e.g. a water pipe, and see if that effects anything. (It could be the fabric of the clothes we are wearing, and the humidity in the air that make the static charge we build up change)

OH! Just a thought. I have often problems using the touch while charging, Could that explain what you see?

It's still kinda readable actually, if you shine a light at the right angle you see the number. Still useless and not really thought out.

That is why I have removed it immediately from my daily driver as I saw in this forum that it worn quickly. I put it to my F(x)tec greeting card card in the box. ...then I put a durable foil on the back of the phone... 🙂 Also, I cut a P20 back case and my phone sits in that since then and it also has a foil on the screen. 🙂 I hope they will protect the phone when it is necessary.

I'm honestly not sure how you read his post and came to this conclusion. He pretty much said that secure boot is nothing to worry about since its status cannot be read from Android so it can't be a factor of locking you out. With that being said, can't you get in contact with the person who is responsible for corporate environment? Surely they'd know a bit better than just "yeah, because not locked". As far as states that could be read out from an app go, it's almost definitely Safetynet anyways. Recent devices were shipped with test OS builds for some reason as Eske mentioned, but I'd ac

Does it pass the Safetynet test? A few devices were sent out with a not yet certified software version, And those will not pass the safetynet test, if that is the case, you should contact support. You can also check your software version under Settings, System, Advanced, System updates, that has a long name including dates in the version name.

I'll buy it.

Secure Boot is a Qualcomm-specific mechanism that enforces the phone must run signed (trusted) code from power-on to the bootloader. This setting cannot be changed by the user, it is a very low level setting that can only be enabled at the factory (and, once enabled, can never be disabled -- it's a hardware fuse). The "device state" (locked or unlocked) is a bootloader setting that may be toggled by the user with the fastboot tool. As far as I know, the Secure Boot flag is not visible to Android in any way at all. I don't do corporate stuff on my personal device, so I can't say

Feel free to register on http://slions.net and give it a five stars rating 🙂 Do let me know if you do register there as I'll need to validate your registration and I'm usually getting a lot of spams.

I'm working on publishing it on Google Play.

AFAIK you can only import bookmarks from text file ATM. Bookmarks panel is also very basic. I'll improve it as soon as I get a chance. It would be nice to be able to reorder bookmarks much like tabs.

I dont recall ever having problems installing extensions on firefox mobile... currently I have uBlock Origin working just fine.... just click the three dots for menu then select Add-ons.

Would be nice if they can formally open up a semi-public beta program for end-users to test updates, maybe provide OTA packages there. Just don't do it like BlackBerry who pretty much allows anyone who can fill a form in, at least vet the participants for technical background who can actually help with bugs and quality feedback. I'd gladly help, with my former full-time background as Software QA.

Would be great to have a way for people on Lineageos (or on another 3rd party OS) to track stock OTAs as they might contain firmware updates with security fixes etc. Fairphone does that quite nicely on their code.fairphone.com website. You can just download the latest version and the zip contains all the relevant updates to the firmware partitions (even with a .sh file giving you an idea how to flash them with fastboot). Maybe this would be possible for the Pro1 as well @Waxberry? I think @tdm mentioned somewhere that he wanted to package firmware for updating as well. I would g

I agree with most of what you said. Except perhaps the part about comparing app permissions to a desktop OS. Every desktop OS allows apps (we used to call them programs or executables, remember?) to do pretty much whatever they want whenever they want. Please note that there are two distinct meanings for "secure" / "security" in terms of a device. There is security from the corporate perspective, which includes things like DRM and evidence of tampering. And then there is security from the user perspective, which includes exploiting vulnerabilities, hacking, malware, etc. Whene

Or do what every other phone company does... just flash it into the phone's system.