Leaderboard

UPDATED: Hi everyone, there is a new OTA update stamped 2020-03-06, offered. This REPLACES the OTA stamped 2020-03-04, that proved to have an error with Safetynet. IF you already updated to the 2020-03-04, you will NOT be offered the 2020-03-06. But both groups will be offered a common OTA, hopefully in the coming week. The two updates contains the same fixes, but the 04 had slightly newer security patches, and that broke Safetynet OLD message on the 2020-03-04 : Hi everyone, @Waxberry has shared a little sneak view of some expected to be in t

test9 is up. Changes: * Fix notification light. * Fix WiFi signal strength indicator. * Add fingerprint mitigations. Notes: The vibrator seems to work but I am seeing errors in the log. Please let me know if it works or not. Either way I will be looking into fixing the errors. The fingerprint backoff defaults to 2 seconds per attempt. This can be controlled via these properties: persist.vendor.fingerprint.auth_delay: the auth delay in seconds, defaults to 2. persist.vendor.fingerprint.auth_backoff: whether to backoff between attempts, d

All parts test printed, I will do some adjustments tomorrow and post the design 😃 Then I will try and print it in one piece during the weekend. Th msla I am using is just so slow, to print it in one piece I need to print it standing and it takes about 1h/cm.

Thanks to @Raksura for posting this in another thread, but let me put it here too, for more to see the progress.

today is the day, latest ota fixes all these 🙂

THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU!

Yes absolutely.

Hell yeah the keyboard feels miles better now. Good job Fxtec!

I got the OTA this morning. Installed no problem, verified that the keyboard fix is good. Glad to see signs of life.

This issue appears to be resolved with the newest OTA.

Installed it right away, thanks! It seems that security patch level is also updated to 5th October 2019. EDIT: I can confirm that keyboard issue is indeed fixed. I can now play Sonic and Mario or whatever like a charm. Super awesome! It looks like that all keyboard driver issues are fixed now. I can now press "7", "U", "J", "N", ".", "UP" and "Enter" keys (QWERTZ) right after I wake up the screen. I don't need to press some other key first.

Recovery shows the current slot on the screen. It can also be found in Android by "getprop | grep slot", and there is even a fastboot variable "fastboot getvar current-slot".

Restarted and all's well in F(x)tec Pro1 land.😁

they pulled my version of the keyboard driver, the issue should be well and truely gone along with randomly missing keys and now multiple simultaneous keys should work too 🙂

At least for me the update worked from internal storage.

Silly question, can I flash this update onto my phone without deleting my user data? I legit just installed v8 two days ago and don't want to go through the mess of reinstalling everything.

I'm trying to push a release out today, but it may slip to tomorrow morning (Seattle time, naturally). The current fixes include fixed notification lights, fixed wifi signal strength, and a delay for failed fingerprint authentication. COVID-19 affects development because I am in Seattle which is currently in full freak-out mode over the virus. Fortunately it hasn't hampered me that much (yet).

I believe it is not limited to a weak/failing signal, but combined with the bands relevant for the carrier. As more of us would see it if it was just the lost signal.

Fx Service is an Android application notably enabling Pro1 smart case support. It also provides various solutions to common Pro1 problems or simply new features including: Smart case support: configurable lock and wake functionalities. Screen filter overlay to lower display brightness beyond system settings. Configurable vibration upon keyboard key action. Alternative auto-rotate solution to bypass system auto-rotate which tends to get stuck. Filter out unwanted system key input. Feel free to post here to discuss bugs and feature requests.

@david just documented a walkthru of the procedure to update stock to the March 4th OTA while keeping magisk root: https://community.fxtec.com/topic/2849-new-ota-update-stamped-2020-03-04/?do=findComment&comment=46403

I uploaded them from my phone and posted it as-is, and then edited the post on my laptop. You caught it in between my edits. :-)

It worked. OTA info screen: I then went into Magisk Manager and uninstalled it, telling it to restore the previous image. Next, started the download for the OTA: One interesting thing was that it automatically started installing after the download. I thought in the past that it gave you an option tap something to start the install after the download was done, but I could be mistaken about that. This means it is important to uninstall Magisk before even starting the download. It also showed 100% complete immediately after the download was com

I'll buy you a beer if you do so! Or I will buy one anyway, but I'll make it a sixpack at least.

So now key-chording/rollover works in Sailfish, Lineage, and finally stock with yesterdays OTA! I want my game gripper 😉

Follow the first part of this tutorial (not the FlashFire part): https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md

I did some more adjustments now based on the test print, should be quite OK. If anyone wish to test and print it: https://aelv.se/hka/ul/FxTecPro1_case.stl And the files for modifying it are here: https://aelv.se/hka/ul/modelFiles.7z I can post it to shapeway when I have tested printing it and is satisfied with it, but seemed expensive, $22 for the cheapest option and about $50 for TPU.

I am rooted with magisk. I am doing a backup of my apps and settings before I do the update (just to be safe...that has nothing to do with being rooted). I'll then tell Magisk Manager to disable root, do the OTA, not reboot, and then tell Magisk Manager that the OTA is done, then reboot. If the OTA is flaky and forces a reboot in the middle of the update, I'll lose root and will have to manually re-root the phone. I'm hoping that doesn't happen. I should be able to report my results in the next hour.

My manual update got stuck at 43% and then it rebooted my phone spontaneously, but all evidence says I got the full update. 😉 🙄

Seems to be a bug in AdUps. I rebooted after waiting a bit to make sure it was done. The update was successful.

Interesting. Have tried it 3 times, it just aborted without any info at all. But nice to hear. Maybe I have an app interfering with it. Anyway if someone has a problem, try the SD card!

Attention, the file MUST be placed on the SD-Card. Pointing to a place on your internal storage just aborts the update (At least for me). Can not to further Research since it worked with the SD card. UPDATE: See posts below! Update from Internal Storage should be possible, I don't know why it didn't work for me. If you have problems try from the SD card!

Here is a detailed informaation which tells what does the "Emulated CPU Clock Speed" do. - long version: https://forums.dolphin-emu.org/Thread-help-understanding-the-new-cpu-clock-settings?pid=358116#pid358116 - short version: https://forums.dolphin-emu.org/Thread-help-understanding-the-new-cpu-clock-settings?pid=358118#pid358118 If you select lower than 100% the emulation may work better but FPS is lower like you said.

I'll also be curious if it persists correctly thru the next test update, I expect that might bring back the aosp apps (until we're official doing lineage OTAs)... but either way flashing it is easy, and unlike mindthegapps, the actual apps work too (without uninstall/reinstall). And it didnt prompt me for google setup stuff again like mindthegapps did every time. I'm quite pleased. Thanks again tdm for all your work!

I also agree he should spend time getting Lineage perfect, with the hope that when ideallte does get back to work, they implement as much of it as possible in stock themself! My understanding is all of tdms work is open for ideallte to look at and straight out copy if they want, or maybe I should pay attention to licenses and stuff... but doubt they do unless forced to by whoever hires them 😉

I had issues with slots and it has also had issues with lineage recovery in the past, but that may have been fixed. I always used to use opengapps just out of habit, but never liked it because their installer script is insanely complicated. After having issues with A/B devices I switched to MtG and I'm not going back.

I would be one of those. If I don't reinstall GApps, I just get not stop errors from the apps crashing.

You can choose to install to either slot after the initial Lineage install. Just be aware that recovery will install to the opposite slot as the running one. gapps is supposed to persist if you have it installed. But people have reported issues with that, and I have not yet investigated. But it is always safe to flash gapps ... it will just over-write itself harmlessly. Again, be aware of the slots and remember to reboot recovery prior to flashing gapps.

That's up to you. Just make sure you activate the correct one afterward. GApps does need reflashed and you may also have to uninstall then reinstall some of the Google apps.

This will be great to share on shapeways once you have refined it. That way we can order and print in any matierial of our choosing. https://www.shapeways.com/?utm_campaign=search_branded_desktop&utm_source=google&utm_medium=cpc&utm_term=%2Bshapeways&gclid=Cj0KCQiAwP3yBRCkARIsAABGiPrft4iy12F44thmg4yTuAhKiBLDt6ZL_fVAG2iG7Po4MkfUo3UOXEQaAmqOEALw_wcB

Thanks for the link. The UK one says it doesn't ship to USA, but the China one does. Last week I started ordering more to try and I ordered this1 and this2 since I couldn't find yours but this seems like a similar clasp at least. I didn't think about adding measurements to my original post, but it's a good idea: 162 mm long x 82 mm wide x 26 mm (+2 on clasp area) thick (if you can trust someone who uses imperial system). The CoverON bumper by itself looks to be 158 mm long x 77 mm wide x 10 mm thick (trying to measure while mounted in flip case).

Certainly it would be nice if someone official created an issue tracker. But until that happens, I think github issue tracker is much nicer than a spreadsheet. If someone could import the spreadsheet into the issue tracker that would be really nice. Heck, I might even make a new stock build with some of the issues fixed... 😄

Yeah that is probably a good idea, I'll update that. When I have something that prints ok I will post all files. The entire thing did not fit in my printer, but I printed the top part for testing and the camera hole is correct (camera position is actually visible in scan), but other holes need some adjustment.

Foil lined potato chip bag maybe? It kinda worked for Sarah Conner... or maybe in the microwave....

Lol. I hope what we got as a manual install is the same as the OTA... 😅

Remember that they are small, so they easily will be pushed aside when a larger customer wants stuff. Hard to fight the giants. Even though they may already be using multiple sources for standard parts, their volumes are so small that doing so for specialised parts, would add heavy surcharges.

Something between 40-55 is fine.

I think the idea @tdm is using is to handle which physical keyboard-print we got first, mapping either to be usable by the standard android language files on top. This should mean that there will be no hard need for additional mapping for normal text and the most ordinary symbols. We MIGHT want some additional mapping for extra symbols etc, but that same mapping would then also work on any other qwerty-phone, and not be Pro1 specific (nor specific to qwertY or qwertZ) That is, if you want a special symbol pressing say Shift+Ctrl+Alt+Sym+Q you would get that no matter where the Q key

@tdm Thanks for the update. Building now. 😎

OK STEP BY STEP COMING UP... 1. Ensure keyboard mapping is set to no keyboard mapping 2. Click Advanced keyboard settings 3. Click Key repeating 4. Currently I have selected Slight key delay (recommended) 5. Open your keyboard 6. Go to your web browser and select the address bar, so that the flashing text entry cursor is flashing. 7. A little keyboard icon will appear at the top right of your screen in landscape. (unfortunately unscreenshotable.) 8. Click on the icon and Select Keyboard helper rather than Gboard. 9. You will notice now when you clo