Leaderboard

Hello. If any of you experienced poor sound quality, here comes the solution! Our Pro1 definitely has some problems with sound quality. In particular it couldn't play 24-bit audio sources in more advanced audio players, like PowerAmp (16-bit played quietly on headpones causes a lot of hiss/noise). I also found some annoying clicks on some games (i.e. Talisman). These problems are caused by Snapdragon 835 energy savings, which disable high quality DAC chip and switches it to some limited operation mode. The apk I attached can enable hq sound. After installation 24-bit playback on Powe

Okay all, I finally found some time to look at this some more. As it turns out, the xbl partitions are not actually being written by the current package due to a bug in the programming instructions. Or, well, a mismatch between what the programming instructions say and what my program expects it to say. Anyway, I'll fix this and have a new package up shortly. This should be able to fix the currently bricked devices (I know there are at least two out there at the moment).

Been playing around with the new keyboard driver and it's working quite well. The only issue I've found that makes it behave differently from a regular keyboard is that the shift-key-unshift sequence breaks key repeat. I will look into deferring the unshift until the fn key is released to fix that.

Sorry for the delay the last couple of days. I have been playing around with the keyboard driver because I really hate the way that idealte did the keyboard logic. It is, from my perspective, a gross hack that needs to go away. Background: the bulk of the keys are handled by the aw9523b keyboard driver. But the shift, ctrl, alt, fn (yellow arrows), and "fancy f" (aka. fxtec key) are wired up as gpio pins separately. The easiest way for the oem to deal with this was to map the yellow fn keys in userspace. It's a bit difficult to explain, so here's an example of how it works: wh

Let us help F(x)tec with some show casing! I hope everybody will flash it around and spread the word to everybody they think might be just a little bit interested, or might know one that is... At Crackberry a guy was asking where he could try it hands on. So if you are willing to be contacted by someone that wants a hands on before buying, here is a tread to post your Country, state/region, nearest larger town, Then people can create an account in here and send a PM to arrange further. Please mark the geography in bold and/or a larger font, to make i

Hmm, okay. If the hardware codes are the same then I should be able to work that out. My plan is to allow the user to select the keyboard variant, qwerty or qwertz. The selection should be saved (eg. in /persist) so it only needs to be done once. User space will write the variant to a kernel sysfs node, which will switch the hardware keymap. The end result is that you should be able to operate the keyboard exactly like a USB keyboard, selecting the built-in German layout.

Yes I could certainly add an option to pass the fn key through. Which would basically mean behaving like the stock keyboard. Or pretty much anything else that is desired. Oh, this reminds me. You probably already know this but others here may not. The two shift keys only generate a single key. That is, the left and right shift key are indistinguishable at the hardware layer. Same with ctrl. But the fn keys are distinct -- you can tell the left from the right. I don't know how this affects alternate keyboard layouts, but I though I'd mention it.

I hope these improvements will be also available in stock Android. @Waxberry, @Erik?

Just to follow up on my previous post: Phone pairs just fine with my car over Bluetooth, and Android Auto works via USB cable Android Wear works, but it took a couple of tries to pair correctly with the watch Regarding wi-fi calling, it is working after going to the Phone app (NOT "Network & Internet" in the phone settings) > Settings (three dots in top right) > Calling accounts > tap the SIM card at the top with <your carrier> (in my case, "T-Mobile") > Wi-Fi calling > Set to On with "Wi-Fi preferred" (thanks again to @SirBaconIII for pointing me in

First, I'd like to apologize for my laziness. I'm just copying and pasting a part of my post from another thread, and I accidently cleared this the first time I was working on it. Hope this helps.

So, how much more of a delay would have been acceptable to you, for them to continue slogging through that list? There comes a point where you just need to ship it. Thing is, I give them a ton of room -- they are a startup, it's their first phone, and they had to partner with a bunch of companies to get this done. Other phone companies that were far better funded have churned out some hot garbage. Blackberry or Blackberry/TCL released the PRIV, a mess of a phone with overheating problems, terrible RAM management, and no updates, then the KEYone with displays that fell out, no updates, and

Me: "I am so sick of this damned thing slipping out of my hand every time I pick it up. Hubby: "What do you want? Just something that will give you some grip?" Me: "Yes, but I don't want anything permanent. I want something that will come off cleanly with no residue." Hubby: "Are you looking for practical or pretty?" Me: "Functional. I don't care what it looks like." Hubby: "Let me work..." So I give you generic Ruggies and a perfect tactile grip that comes off clean, low profile, doesn't make the phone heat up.. And I am pretty sure with it looking like this NO ONE will be inte

Yes. To see what the layout actually produce selecting stock, @Anssi Hannula has added the stock layout for selecting nothing and selecting German here Note that the Geman layout (currently, QX1000_EEA_20200106110245) has a few bugs, as it does not exactly match the yellow prints...

Well then. Color me embarrassed. @SirBaconIII had it exactly right. My previous experience with wi-fi calling had it in the network settings (if you do a search in settings it will actually show up as a result), although I did look around the phone app at one point but I guess I didn't look hard enough (and I didn't dig deep enough here either). Wi-fi calling is now active. Thanks everybody 🙂 (Now if I could get visual voicemail working through the phone app that would be the cherry on top :P)

Select another layout supplied by FinQWERTY (in stock Geman the question mark is currently put on SHIFT + sharp S, and the yellow symbols on E, R, M and Ü are not working, hope they fix it soon)

Have you tried to raise your voice, like if you were at a meeting? In my experience it is when the volume gets below a certain level it is cut off. This obviously is not a solution, but if this generally is a workaround, it is 'merely' a need of adjusting some limit somewhere....

I tested latest BSG Gcam build and viewfinder was NOT upside down in Night Sight. However, picture quality was very grainy so it is not usable for Pro1. BSG build confirms that it is possible to rotate the viewfinder.

Maybe a similar official fix could be included in an update by F(x)tec?

The Priv served me well for 4 years despite it's many shortcomings so it's a shame that we likely won't be seeing any more Blackberry devices but the Fxtec Pro1 is a more than reasonable replacement. The writing was on the wall for about a year though with the lack of a Key3.

@sequestris http://www.skinomi.com/sk35070-note-10-phone-black-carbon-protector.html

From 04/19 - 12/19 I waited. Sure it was a bit much, but it's not like fxtec wasn't transparent. @Erik and @Waxberry have been more than helpful. I never once posted a nastygram or sent them emails saying WTF. I was nice, said good day, wished them happy holidays...sometimes I sent them emails just to thank them for what they were doing with this project. I'm happy I got my phone. But I had posted that I didn't expect it anytime soon. I even joked that I was hoping my Nexus 5 would last until June. So cancel your order if you don't want to wait. Others have and have gotten refund

Yeah, that was annoying me too. Just hold down on the notification and it will give you the option to not show you that notification anymore.

Hey Vaz, don't worry too much. Chen and team are aware of these improvements and some will be included in next OTA update. Be aware the software engineer that can implement such changes and get them pushed out OTA is currently stuck @ home along with the rest of China, and doesn't have access to dev tools, so patience may be required. Odds are, lineage will be official before fxtec pushes out the next OTA 🙂

In crowded China, the safest place for FX workers to be is at the factory right now. What do they have like 5 people working there? *going by earlier posted picks of their assembly line*

When I saw the title and text I expected an image of an aPple Iphone ...... 😇😇😇

I had the same problem when I received my phone today - actually I had to press my ear firmly to the phone, regardless if open or closed. After much fiddling with it and test software, turned out that the plastic behind the upper left part of the phone (behind the screen, not on the keyboard body) has been loose. When I pressed it with fingers behind and in front of the screen, it went "click" and the receiver audio suddenly started working all the time. This is interesting as there is supposed to be a screw there - it has one of the screw caps that are all over the screen back. Can somebody t

You can try contacting them on facebook. Their support group on Facebook is widely regarded as being best at getting you what you need.

I'm guessing here: As these are kind people, it could be that they given the short interval between the refund and the new buy, simply remembered her and handled it as a 'regretted refund' and put her back in her old place in the queue, that is the first payment date (Aug 1st), that could explain things.

I'm getting a Pro1 mostly because the Priv2 was never created. I love the design of the Priv, had a Q10 before it. Unfortunately I didn't take care of the battery nearly as well as @EskeRahn (I've only just done my homework on what I was *supposed* to be doing..) so the thing's failing on me pretty badly now. A full charge will hit 50% by evening, and then (based on some criteria I can't determine) has a chance to shut itself off, reboot, get stuck in the adroid optimizing apps screen for ~10 minutes, and then come back up with 12% somehow. Here's hoping my Pro1 gets he

Basically, Pro1 comes with shifted QWERTY keyboard. Its keyboard generates the same codes written on this shifted QWERTY keyboard as it should. On QWERTZ keyboard of Pro1, hardware is exactly the same, only printing of keyboard is different. So although QWERTZ has most of the keys moved back to its original location, the hardware's behaviour makes it shifted, generated keycodes are usually not match their original codes. So on QWERTZ, these keys should be unshifted by software to be usable. So he means the primary keyboard of Pro1 is QWERTY which is shifted (not the same as a r

Finqwerty just provides a bunch of .kcm files to android via an API. Where I imagine that could become difficult is that currently there are mappings that use fn-key combinations that are not any fn-key combination on the physical print, if the driver absorbs the fn key events there would be no way to remap those combinations in userspace I guess. A possible solution would be to provide an extra extra physical layout on the driver level as suggested for qwertz, where fn is a normal key and the user can figure out how to use it.

I really don't know about IMS support. All I've ever cared about on my phones was basic GSM service (voice, SMS, MMS, and data). But the proprietary file list (which was stolen from the 1+5/5t) has an entire IMS section, so I would hope it works: https://github.com/tdm/android_device_idealte_msm8998-common/blob/lineage-16.0/proprietary-files-qc.txt#L944

Thanks @VaZso. Got it. Settings > Calling Accounts > "specific SiM card" > GSM call settings > Additional Settings > Caller ID. Talk about being buried in the menu settings!

Won't this make handling different physical layouts like the qwertZ version of the phone and having custom mappings such as with finqwerty more difficult?

Great idea! I'd like to try one before buying it in a few months.

I would try connecting the phone to your PC, using a USB 3 port, and then in the USB Preferences screen, in the phone, turn on USB tethering. You shouldn't have to enable USB debugging first, but if it doesn't work for some reason, you can try that. Your PC (assuming windows) will pop up asking if you want the network to be a Home, Work or Public network. You can pick Home, since nothing can spy on that network anyway, since it is only between the phone and the PC, over the USB cable. You may need to disable your wifi on the PC (if is running wifi) or unplug the ethernet cable (if it is

My device has sound quality issues on speaker phone I am told it is really difficult to hear me on the other end of the call when on speakerphone Also the phone rebooted twice when attempting a WhatsApp videocall

Right now there is a known bug that when the screen goes off and the backlight does too, the backlight doesn't come back on with the screen. You have to close and reopen the keyboard. I believe it is being worked on. I don't know if that applies to all your cases or not.

There's a long thread about them. Alternatively, the TL;DR is here: https://eskerahn.dk/?p=3620

If BB took the Priv and just refreshed it (more efficient processor, bigger battery, fingerprint sensor) I probably would have gotten it!

They were always terrible with having fluid software... but I loved all their hardware. I know the die-hard enthusiasts will scoff and say that the Priv/Key keyboards weren't as good as the old Blackberries and while that's true, they were still a hell of a lot better than the software keyboard. Not to mention some of us are way better with portrait qwerty than landscape -- I'm still getting used to it!

I usek BB KeyOne before Pro1. KeyOne is a very decent phone, very convenient to use. You can, for example, type on physical keyboard while it is locked in car holder. I also set Tasker to use physical keyboard shortcuts to run different apps easily, no matter what app was running at the moment. Very, very convenient. Unfortunately it is still locked and root-proof, didn't get updates past Oreo. Even though I still find it a great phone.

I don't know about the magic phrase. I called T-Mobile and (because I have been a customer since 1998) was transferred to my special support team. I asked them to turn it on and they did. Wish I could help you more.

Curiously, I've been using it on my device. Works great! The backlight was finicky but this fixes it.

Consider that the phone you are using is a relic (we're talking "it belongs in a museum" here, as did/do a lot of the phones customers looking for hardware keyboard had/have), it used to fit your needs, but these grew and the phone is starting to have a lot of problems. Here comes the Pro1, pretty much a direct upgrade, you can still do all of what you are currently doing and more. Problem is, it's not cheap. You already paid for it, and there's no real replacement for your current phone on the market so you can't just buy a cheap one in the meantime (or you simply don't have the money to

It didnt disable them, you are using the one with dead keys on first two levels. Switch to the layout with altgr dead keys, then everything will behave normal. The way I read the last post in that git thread, from 7 days ago, implies the us-intl with alt-gr dead keys is already the default, but it seems its not? Either way doing it following kabouik's method works until its fully resolved. Explanation of dead-keys and difference between the two us-intl layouts. A dead key is a key that, on a typewriter would not advance the cursor, so they are typically used for accented le

If the 12 is not something locked by android but within your control, it would be SUPER elegant, if you rather than twelve had one for each of the letter&symbol-keys so we pressing the Sym had a staggered keyboard map pop up, and then pressing say the M got what ever symbol we put there. (Optimally with the HW-printed letter&symbols in faint small print, and the symbols in clear print in this helper display) If Sym was used as a modifier with the M, we could have the symbol directly without the helper screen popping up. And this system could be expanded to allow Sym+modifier

I believe this may be somewhat relevant to the thread; I went and implemented a Polish programmer's keyboard layout for the QWERTY Pro1 based on FinQwerty. For anyone interested in the changes, they are in a pull request waiting for feedback and an eventual merge: https://github.com/anssih/finqwerty/pull/9 .

Those were the days. I knew what EVERY file on my pc was for and knew what EVERY setting in the ini-files meant, and what values they could have.... Totally forgotten most of that,,, But It was quite useful for support and educating supervisors.

a screenshot in windows