Leaderboard

Regarding sailfish, the port is certainly still in development and has not stalled. I use it as my daily driver with few issues. The latest releases are available from the continuous integration build server at https://gitlab.com/sailfishos-porters-ci/t5-ci/-/jobs Regular users are advised to install the "testing" releases, as the other releases are from the devel branch. I try my hardest to not break the testing repository, but breakage may happen in the devel repository, and I wont give you sympathy if you are running that version 😉 The current releases of the devel ver

Apparently there was an issue with the build server configuration. https://buildkite.com/lineageos/android/builds/25787#2280946e-4537-4166-9eaa-79e9dbfb50d5 You can track all Lineage builds here: https://buildkite.com/lineageos/android/builds Note the nice pretty shade of red all the way down the page... 😄

Meh. I don't think we should be bothered by it. It'll probably be the same form factor as we've come to get used from BB. It being a slider phone is a chance of 1 in a million...

If you boot to the boot/recovery that you built (by using fastboot to flash it), you should have no signature issues with the package. Just a guess, but perhaps the microg signature spoofing is getting in the way of the metadata signatures? The easiest solution might be to fastboot flash your built images instead of using recovery to install them. You'll probably need boot, system, vbmeta, vendor. You can find them in out/target/product/pro1 under your build tree.

I use a 500mA chargers, with 1A it is always swapping between low\fast charging, and I guess it's not good for battery and controller. In fast charging the phone is quite hot as a cooktop. With 500mA it takes about 5-6 hours for plenty charging, I also use a DIY-adjustable-timing power socket, so I usually never reach 100% charging. I also use an electronic heat sink (from an old audio power amplifier) it works great as the pro1 has a metal case cover. See the picture. Edit : normal functionning (no charging), with #sudo dumpsys battery, 35°C. With dissipator 27°C...35° s

Date: Tue, 18 Aug 2020 20:34:55 +1000 From: FX Technology Limited <[email protected]> Subject: Pro1 manufacturing update Hello! We hope you are well and keeping safe. The last few months have been a bit of a challenge for us all but we are pushing through! Thank you so much for your continued patience and support, we really do appreciate it. Whilst we have experienced some minor delays to the manufacturing and shipping of Pro1’s, the factory has been working as best they can to keep up with demand. We will have another batch of Pro1’s ready to ship early Septemb

Ehh...I am pretty sceptic considering how BB's last deal went with TCL (from lack of updates to extremely bad build quality everything went wrong, I wonder who remembers the fall out screens on the Key1...), also the "magic security" is bollocks and only shortens the phone's lifespan by a huge amount because you can't even unlock the bootloader.

Thanks for the hints, I'll start the build again as build artifacts got cleaned as I can see... Add Thank you so much for all the work with Lineage!!

I am by far an expert in this, though I have used some time digging into it. The first part of the quote is clearly right in broad terms, but it is actually more complex. If we are below 50% and the battery is at room temperature high currents are not a problem, it is when the battery get more filled up and&or the temperature rises that the high currents are problematic. On the second part, this sounds really confusing and against normal physics. I never heard of a charger overheating by supplying a low charge (On the contrary cheap ones can overheat while producing high currents

Well the answer is that to care for the battery as slow as possible - it is a matter of keeping the temperature at room temperature below 30°C. BUT it is not that it is killed immediately by fast charging, or a very sharp limit at 30. it is like fast-food: Occasional usage can be very convenient, but very bad for the health and overall lifespan if used daily. I have written a lot more on my blog with links. Start e.g. here

So I was told that it was this thread where I could brag about typing speeds (I completely forgot about it since I got my (used) phone four months after my last visit). Comparison: up to 250 keystrokes with Clavis software keyboard on a smaller phone (G3, traveling distance matters) up to 280 keystrokes (if I remember correctly) back in the days of the Droid 4 / Photon Q up to 440 keystrokes with my laptop and cramped fingers up to 250 keystrokes with my Pro1 keyboard just a month ago (now up to 300). Sadly I can't do the german tests since sticky shift doesn't work in kiwi br

Updated 18 Aug 2020: Updated flashable package to 3.3.0.16. Many thanks to Adam Pigg who has fixed many bugs and implemented many featured including fingerprint reader and encrypting user data, which will be available shortly. Another change for this package is after flashing, user will be on testing repository instead of devel, it's highly recommended for previous users to switch to. Disclaimer: This is the unofficial community build of Sailfish OS, and it's still work in progress and in Alpha state. It is not yet suitable for daily use. Flash at your own risk. If you wish to restor

using my own boot image did the trick :) Install works smooth now, but after boot settings app and others just crash all the time and the system is not really working. I deleted cache and userdata so I guess there is a problem with the build itself now

Thee first weeks after it went official we got weekly Monday builds. But not the last two Mondays. I see a lot of pending stuff described here https://download.lineageos.org/pro1/changes/ Anyone knows what is preventing these from going 'live'?

Let us hope for those preferring the keyboard in the wrong direction that this will be something less humongous that the Titan. The larger the variation the larger a target audience that can get what suits their needs.

Good news for the BB lovers, I guess.

Thought this might interest people here: https://www.businesswire.com/news/home/20200819005202/en/OnwardMobility-Announces-Agreements-BlackBerry-Foxconn-Subsidiary-FIH

As far as I know, (and using LineageOS, it could be different with stock-android), for me there are here three parameters for Li-on battery : - 1 : less heat is better for long time battery usage, with 1A power my phone is swapping between normal/fast charging, I guess it's not good. That's the reason why I use an (old) usb adaptator who deliver only 500mA. For a night charge every day. - 2 : the better use with this type of battery is : -not under 30% -every day charging a bit is better for durability, so you are at 30-80% most the time - 3 : Fast charging never reach

I don't have mobile until the PIN for SIM1 is entered.

I bought a secondary prepaid SIM which I'm going to activate next week. For now it sits in slot 2. To not get warnings I've deactivated slot 2. In this state when I turn on the Pro1 it doesn't ask for the PIN of SIM1 right after startup. I have to lock the phone first and then unlock it again for the SIM unlock screen to pop up.

I ordered in July I think I will just stop coming here and hopefully forget about it will have a nice surprise when the device arrives sometime next year

I bought three Snakehive cases and completely forgot to order a pouch for myself 😩. Really annoying, because six months later I actually still want to try it. It's not even that expensive. I just hate the shipping costs 😅.

Minute I meant... for a moment I actually thought I was a fast typer ._.

...so i have contacted fx support now 🙂 On photon i was util june this year... and then for short time on nokia 6.1. ...sooo on photon i was approx 7 long years 😄 Yess i have modded approx 800-1000 photons. For you was it on 2013 - i still have emails from you 🙂

@tdm are providing builds faster than you can test them 🤣

And here's AICP... http://ota.nwwn.com/roms/aicp/9.0/pro1/aicp_pro1-ota-9.0-test1.zip

Okay got AEX working... please test and I'll toss up a thread later. http://ota.nwwn.com/roms/aex/9.0/pro1/aosp_pro1-ota-9-test1.zip EDIT: If you need a recovery to flash this with, my latest Lineage test recovery should work... http://files.nwwn.com/android/pro1/lineage-16.0-pro1-test22-boot.img

....I can not help the feeling that you might have put more time into developing software for the Pro1 since autumn than Idealte....

And I'm now an AICP dev also. w00t! 😄

Got AICP built but it's not booting properly. Need to investigate, but not right now. I'll try building AEX next.

Looks like both AospExtended and AICP have Lineage compatible device trees. So I can look into building those.

I am also building it myself. It is quite easy actually with the docker container: https://gist.github.com/dicer/3543ef27cbee845c0cbba9cf3f15242a You just need a lot of RAM (I think 16GB?) and disk space (>100GB). You won't get OTAs though. You will have to rebuild yourself once in a while Regarding the boot image: You can just use the one from TDMs website as far as I know. There is also a way to extract them from the generated zip files but I forgot how, since you only need to do that once as a base. You install the boot image in slot A, boot to its recovery and install you

64 wpm from the Pro1. Physical keyboard, of course 😋 When I first got the phone in January, I struggled to break 30 WPM (and that was also before the OTA update that fixed the key ghosting problems). Things have gotten much better with practice.

If someone is willing to send me a phone, I'll try 😄

FAQ - Reserved for later with assumption we can edit Q: Can I use a microphone and speech to text? A: Sure. Go ahead and try. If you can do that faster than a keyboard accurately, then there is no need for another keyboard phone.