Leaderboard

Alright things are moving right along now... I've got the touch screen margin/deadzone implemented and a nice little settings preference for it. The display margin will not happen until later, if at all. That's much more difficult to implement and intrusive to the system (it will likely require a reboot to take effect). I'll be adding a keyboard layout setting (qwerty/qwertz) next. Then I'll see what I can do with the fingerprint reader mitigations.

Yes it would be nice with a formalised channel for this. Currently we have two threads: One for discussing and testing possible bugs and the like, and one that was supposed to have confirmed bugs... But they are not 'clean', so hard to find anything in them. There is an unofficial bug-list here that is more easy to read. But a more formalised system would certainly be to everyone's benefit....

As a preorderer I would easily pay 100€ more for no accessories but the phone itself.

This is very interesting! Are you able to reproduce the issue? If you can then maybe Pro1 is rebooting in specific situation when there is no network or the network is changing. Reboots seems to happen during traveling. It is common that there are areas without network when you are driving between cities. Similar thing might happen when you put phone to metal locker which blocks network (like a Faraday cage).

No. 1: Full TWRP support No. 2: ExFAT support for large sdcards (generally 64gb+) No. 3: to take a time out @tdm after all that hard work/support 🙂

I think it's safe to say that we're by-and-large the 'tinkering' types that enjoy spending time on an unrestricted/unlocked device even if it makes no rational sense. I like having something different. It makes me proud even if it's behind the times and absolutely flawed lol.

I suggest reading up on what Magisk does and why. With great power comes great responsibility and it doesn't sound like you exactly knew what you were doing. You can get by fine with rooting stock, but modifying the system partition for real will break delta updates as OTAs are, so even if they'd allow it, it would not be a great idea.

Poking around a bit in the touchscreen driver. Adding code for the side dead zones is trivial and it works here. Hooking it up to a sysfs node and adding a setting item in the settings app will be a bit more work, but very doable. Not sure about the fingerprint reader yet. I may implement two options: one to only activate the reader when the screen is not off and one to limit the amount of time between reads. I personally like the latter -- I love to be able to unlock the device without pressing any physical keys. But I'm not really sure exactly how to implement either of them

https://github.com/tdm/android_device_fxtec_pro1/issues/31

There is an add-on su package for Lineage. See the extras download page.

I've been working on that two weeks ago (didn't have time after that), I was still stuck at the building stage with caf sources. I'll try it this weekend without caf, maybe that's my issue.

The Tasker Profile "Edge Block" created by @elvissteinjr works really well to solve the problem with typing the top number row on the physical keyboard. You don't even have to really know how to use Tasker. Lol. I don't. Just import by tapping the Profile and scenes tabs and away you go. Has advantages over Edge Null as explained in the post, especially the not getting kicked out by Android.

For me, I have tried to check what bands my carriers support but it does not seem to be an easy task. It seems both of them currently support only B3, B7 and B20 for LTE. The provider which I don't use for data has B1 and B8 bands for 3G. The other service provider which I have 4G and mobile data, only supports B1 for 3G. Both of them have 2G as fallback (at 900/1800 MHz). Looking at coverage map, the carrier I use also for data has good coverage for 4G but fair coverage for 3G and practically full coverage at 2G. The other carrier has fair coverage for 4G but good coverage f

Now having caught up a bit 😄 "What is the maximum dead-zone that allows us to drag an icon from one screen to the next in various launchers? With Trebuchet you have to be really close before it moves over." The Microsoft launcher also has this problem of needing to be very close to the edge you have to be on the curve for it to trigger the other screen.

Erhmm did you read what we have been debating in this thread since yesterday? Just asking... 😇

With this would it be possible to have the screen size generally reduced so the curved parts are not used for display at all?

My Pro1 restarts itself when I put it into a metal locker. WiFi connected, both SIMs inserted.

4.4.153-perf

Did you mean that Night Sight is slow? The whole idea behind it is to take sevaral shots and combine them to one picture. There are some algorithms that can produce geat pictures in low light. It is the "magic" behind Gcam.

Agree with both of you. Funny in that I have never referred to my phones as sliders (although they have been, or pop-up, or flip and spin, lol). I just always referred to them as tactile, or physical, landscape keyboard phones. This was perfectly descriptive, and never became confusing in conversation. Speaking to someone who isn't familiar with a Pro1 they wouldn't have a clue what a clack phone, or a clacker is and I would be afraid it would just introduce more confusion.

I take it that he is referring to a traditional slider where the screen isn't angled, but is parallel with the keyboard (a good example is my Droid 4).

I'm not saying that it is a big issue, just some lost functionality, that might be missed. There might be other issues we do not know of. Say some app that requires an edge swipe to reach the very edge, or really close by. What is the maximum dead-zone that allows us to drag an icon from one screen to the next in various launchers? With Trebuchet you have to be really close before it moves over. So I like the software-bezel idea David mentioned with completely reducing the apparent display size. Optimally an option reducing either just touch or touch+display or perhaps even a

The other reason is for aesthetics, so someone who doesn't want to see content on a curved display can have a flat display. Related to that, would be square corners, not rounded. Aesthetics are probably way down on the priority list, but just mentioning for the future. I have no idea if you have control over things like this, but the pull down menu that has all the system shortcuts in it does not fit the screen when in landscape mode with the default settings for screen size and font size. The edit and settings buttons are off screen and can barely be accessed by tapping the

You can scroll with a vertical swipe anywhere on the screen for that. The scroll bar is just a visual indicator of your position in the list. I couldn't imagine requiring the user to hit that tiny scroll bar with their finger.

I don't use LOS yet, but just contributing ideas. With the dead zones, an option to change the physical resolution that is reported to apps would also be nice. That way, edge UI elements that a null solution would make inactive can be solved for. Another to add to the list is double tap on screen to wake it. I can't remember if that is already available.

Holy crap, I finally got a2dp working. That took waaaaaaay too long, but it's working now. Next build will have it, probably tomorrow since I am a bit busy today and there's some other stuff I want to fix/add also.

When I first saw there was going to be a tilt, not straight slider, I was concerned the angle would be annoying when holding the device. I've found that isn't the case, and the angle makes it better for reading when placed on a table (like while eating alone or something). I've got much better with opening than December, but I still feel this will remain an ongoing complaint by reviewers and new users. And if there were competition, and someone walked into a phone store w/o any prior experience and compared pro¹ to any other regular slider, they'd buy the regular slider, cuz pro¹ so d

Did you read the post right before yours? In fact, tdm is building it into the OS, and at that point, those using tasker to do it will no longer need to. But also note tasker works with stock too, for those who haven't moved to lineage (yet), so it's still a good solution imo.

You are really doing an awesome job, can't repeat it enough Less the Google certification some need for banking apps and the like I will say that the Lineage implementation is better than the stock one in several ways. I certainly hope they will adapt some of it in stock.

http://en.key-test.ru/ I had been using that site as one way to verify my Fkeys keymap worked right, and for no particular reason decided to verify all the other keys too. Most behave as expected, but for some unexplained reason, - and ' arent identified correctly. In Firefox, both keys identify as left click. In Chrome, ' registers as ` while - identifies as left click. In both browsers, if I actually type those characters into address bar or text field somewhere, they work as expected. And Supertux identifies them normally. So something about the way that particular w

Hi, about those dead zones: I would just need one on the bottom when the keyboard is open: Then my thumbs sometimes touch the screen when using the top row of keys. But it is not a big deal, so if it is easy to implement together with the usual dead zones it would be nice, but if not it is probably at the bottom of the list (or not even on it, if too complicated of if I am the only one with this problem).

*Captain Kirk scream* SWIFTKEEEYYYYYYY!!!!!!

Moved the further Spontaneous reboot discussion over here

No. All photos are slow to be taken especially dim light ones. I have no idea what that option is and have not used Gcam yet, only Snapdragon and OpenCamera. David thanks for the link I will try it out. Edit: Bless the heavenly fathers. Now I have an actual useable camera. A million thanks.

I tried this under lineage, which handles it a little differently already. With landscape lock, it does indeed force apps landscape that wouldnt do it before (games, hangouts). However, I have to stop service or set it to force portrait to get portrait, even with keyboard closed. I imagine this is how its supoosed to work, but something funky in stock lets it go both ways.

It didn't in my experiences. But, in general, the magic in GCam does seem to revolve around taking many pictures in the background and doing some magical processing on them to come up with a good looking composite picture, so it can be slower, depending on the mode used. If you use regular HDR+, that's faster than HDR+ Enhanced, for instance, but the output isn't as good in difficult situations. Of course, I'm speaking in nitpicky terms. All of this is much better than the camera sensors and software of several years ago, which is what I am transitioning from. 🙂 This is the GCam p

Retractable micro laptop? 🙂

I could extract images from the current stock and make a EDL package and/or a fastboot package. But I've been rather busy and quite honestly it's not a priority. The only use I have for stock is extracting vendor blobs for the Lineage build... 😄

I have no idea what's taking place with your carrier, but with AT&T in the US all the switches are grayed out for me too; however, but both VoLTE and VoWiFi work. The only way to turn VoLTE off is to use the switch enable/disable 4G/LTE switch in the mobile network configuration. If it is on it will place VoLTE calls by default (when service allows), if it is off then it won't. The fact that they are grayed out in the off position is a known Android issue.

What I really enjoy is reading with the keyboard open and the book forced to portrait. This might only be a pleasure for right-handers, but wrapping my left hand around the keyboard gives me a very firm, comfortable grip while my right index finger turns pages, or my right hand grabs my coffee. My hand doesn't get tired holding it this way. It's perfect for reading.

No issues with getting insurance here. Mine is covered for theft and accidental damage in and outside my home. Don't bother with online insurers, if you've got contents insurance on your dwelling have a word with your provider, they should be able to provide cover for a fraction of the cost of say Gadget Cover etc. For reference my home contents is with Barclays.

No, but it's still fun to read.

I am too lazy to get ye olde oscilloscope out of the cabinet, but I too suspect it to be electrical noise. Possibly not even from the charger itself. The ghosting only happens when the phone sits on the plastic surface of the table. IT is a height adjustable office table with a laptop and two screens on it. Maybe the table itself acts like a capacitor and the surface of the phone gets charged electrically when it is in contact with the table surface while connected to a power outlet. Oh my, so much text and I bet @[email protected] is not even struggling with ghost touches only while chargin

I always felt absolute zero qualified as 'cold'.

Or at absolute zero! I do feel your pain, however, @SchattengestaIt. My Relay 4Gs (many of them) would get to that state with the ribbon cable for the screen, and I'd have to heat them up or cool them down, depending on how they were feeling at the time. Due to the delay in getting the Pro1, and because I had exhausted my supply of spare Relay 4Gs, I finally had to acquire some ribbon cables (they are almost impossible to find now) and replace them in a couple of the phones so that I had something to get me by until my Pro1 arrived. I'm ashamed to say that did use a Pixel 1,

Generally an AC high voltage input might have the issue, and a low voltage DC is very unlikely. Could be induction but I guess surface currents could be an issue too, or simply an 'unclean' ripled DC signal. It would be nice with a setting for the sensitivity, to adjust to match different humidity and skin texture.

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

Although its's more of FedEX issue but I will pushing / checking with out logistics partner see if there is anything we could do to speed that up. That seems rediculous to me as well!

I was going to say the same thing. I would have no problem if they wanted to have dynamic display technology on the top of the keys. That would also be efficient from the perspective of manufacturers, so they wouldn't have to have different hardware keys. But the keys would need to be like the ones on the Pro1, where they are staggered, rounded on top, spaces in between, rounded corners on the keys, etc. There would need to be an override to put it back to the stock keyboard in any apps where the apps decide to re-write the keyboard too (last picture). Ideally, the norm would be tha