Leaderboard

This is what Chen replied on Twitter when somebody asked about 2nd batch: "They are leaving end of this week! Will send out fulfillment mails later :)" https://mobile.twitter.com/chenliangchen/status/1197500492848549896

I have experienced those as well... , when we designed the internal I made USB board separately from main board. It's on a mini PCB so replacing it would be cheap as you don't need to change CPU, memory etc...

The edges of the OLED are rounded, so It's a Hardware thing. One could only shrink the display size via software to fit the screen inside of a rectangle.

It's because you have to bake all the hardware drivers into the image. Desktop OSes tend to have a bazillion drivers for common hardware baked into the image, but storage on mobile is much more limited, and this waste of space is more noticeable. On top of that, generic handles for things like video and storage to make something work without hardware-specific drivers are nearly universal on x86 machines (although servers can be fiddly), but ARM devices need the specific drivers for the hardware to even work in most cases. edit: lots of great answers to this question from others.

Give me a device and time. I'm sure I'd have an answer for you whether I wanted one or not...

Just a suggestion - could one of the moderators keep a concise list of known issues/bugs in the first post? That's typical approach on xda developer forums, and it really helps get a quick overview. On a related sidenote - is any of the problems found so far a complete dealbreaker for daily use? I'm thinking sensor-poking apps crashing isn't ideal, but it's not something one needs every day. Headset pairing is a bit of a bummer from what I see. Anything else?

I don't think (however, I don't know "today" means which time zone, it is 19:44 here). So, I should be in the second batch as an IGG preorderer and still not received e-mail about it. Also, I think "Will send out fulfillment mails later" statement doesn't mean later in today but maybe later next week. Also they said most of the preorderers they wanted to be in second batch, so there is a high chance you may also. 🙂

I just received this email: "I just wanted give you a quick update with regards to your headphones. They are being sent shortly, so you should receive them by middle to end of next week depending on postage times from london" YES!

A modification. The soft shell case type for "Huawei P20 Pro" is actually a better fit than the "Samsung Note 7" soft shell case. As the existing cut outs is closer to the Pro1. So IF we can find a RIGHT SIDE hinged flip case, it would be close to a full match. Oddly I have not been able to find those, though it is the obvious way for two handed usage for right handed people to hold it in your left and operate it with your right hand fingers... I found a LOT of different LEFT SIDED hinged (This goes for the Note 7 cases too), those would have the best fit used up side down on the P

I think you misunderstood something. 2nd and 3rd batch weren't on their way by then (maybe the second batch has left the factory by now), but they were talking about those all the time. So yeah, there will be a second batch much bigger than the first one and (from their view) hopefully covering all preorders. General availability should be there in mid-december so all devices will (according to their plan) be shipped by then.

Because every phone is different. 🙂 I mean any of them use a specific SoC (like SDM835 in this case), but different solutions in hardware. Different sensors are connected to different ports (other I²C or SPI), the CS pin of an SPI device may be connected to different outputs, enable signal for specific power supplies may be connected to different outputs, after hardware switches on it may have a "self-powering" technique which has to be driven, uSD can be connected to different port (if there are more), displays are different (resolution, driving method / driver IC, mirroring, etc), tou

Yeah - except the Linux kernel itself already includes a lot of drivers to a point where on the x86 architecture every imagineable driver is already included. And the entire thing barely reaches 90 MB of space. Driver size isn't the issue. As others mentioned, ARM doesn't have a BIOS equivalent (which I didn't knew.) and a lot of propiertary drivers (why companies do that is beyond me.) @netman thank you for that explanation Also: Apparently Ubuntu Touch can be compiled if one has the kernel sources of the phone available. I think Waxberry once said they would put those

As soon as I get my device 🙂 I'm not in first batch, so it's gonna take some time.

Sounds to me like Fxtec better sets up a bug tracker before too many devices are delivered, so stuff gets collected in an ordered manner.

Why? They're creating what we've desired for years but the big phone companies were too busy making what they thought we should desire instead. Helping them help us is how we get what we really wished we could have! :) I'll be lucky to have mine by Christmas (couldn't keep my preorder, had to place a regular order) but hey, when it comes, it's Christmas again. :) EDIT: I'm still using a Droid 4, for crying out loud. :P I am indeed that committed to having a physical keyboard. I'm using it to post this!

Always be sure to have those replacement pcbs around when you go on holidays. I don't know why, but they always brake when you are far away from home! (good thing that you can build a temporary connection with some plastic and a cut open usb cable. But don't burn your hotel down with that...)

Updated the SFOS image to the latest 3.2

Did someone say general availability before christmas?

I've seen a few photos now since there are some Pro1s in the wild, and the corners of the display image strike me every time. Personally I find it quite annoying. Is there an option to disable the rounding on the corners of the display? Or is it in hardware?

Just tried, and Autorotate, well the function is there, but as they seem to assume the same icon grid, rotating the icons in the grid, and stretching the grid, When it looks OK in Portrait, in landscape extremely spaced in one direction, and cramped together in the other (Or vice versa) - but not unusable. All the functionality is there, and with Ctrl+Arrow you can jump around the screens. An oddity with keyboard navigation is that you have to leave one of the the left most column spaces free as arrow-navigating there in landscape BOTH marks that empty space and the icon in the launch-bar

adb shell wm overscan 16,20,16,20 Matches the curves AND reduces the risk of accidental edge-touches. Note that "wallpaper" or "background" might be displayed beyond these boundaries. BUT not all programs handle it correctly. Various odd issues. e.g. the Danish National Broadcast DR.DK TV-app, gets confused, and adds additional borders when attempting full screen.... Problems like that typically occur if people coding are not consistent in working with the size of the physical or the logical display. Fiddling with the density also, can fix some, but can make it worse f

I have 2 of them new in their boxes. and 3 of them with the original battery and working flawlessly. I upgraded 1 of the N900 with great speakers and the sound is soooo great.

Thanks. I'm not bothered about the missing pixels, I just think a rounded rectangle display on a rectangular phone looks weird. I'm sure I'll get used to it!

Just to be clear, Android is aware of the rounded corners and lets software know about them via "display cutouts". Good developers can work around them or have their apps "shrink" to avoid them. The option to shrink your display at an OS level is something some versions of Android support, but I don't think the stock Pro1 has such a feature. You may need to install a different OS.

They just need a public issue tracker 😉

@VaZso yeah, I'm now clear on the reasons. All the hardware com stuff - I didn't know about that since I assumed that there would be some kind of BIOS that handles that for the operating system - similiar to x86. All good now in the sense that I got the message ;).

Yet... Let's be hopeful, to get sailfish etc there is also a want to get hybris working on the device and that code can be shared i believe 🙂. Because there is no standards for bootloader, how to tell the OS what devices are connected where, drivers, etc. The image has to be built to know where and what about the hardware. It's a regrettable fact of life, but shows you how good we have it with modern PC/laptop hardware. It's almost the same way it was back before when IBM PC type stuff took over, and instead of the BIOS abstracting the hardware for the OS there was only a manual tellin

Also for many devices. I have had a number of Droid devices which would reboot instead of power off when plugged in, and also would not boot (even enough to charge!) if the battery was below a certain level and the power cord didn't give it what it needed.

Considering the community worked together on the Pro1 QWERTZ layout back in March and QWERTZ being planned even for the Moto Mod, I'd disagree on that. It was late to be actually added to the order process, though. That aside however, it's not like all EU orders are QWERTZ. There have been QWERTY phones shipped as well, just outside the US. This has nothing to do with the layouts.

Yes I copied the boot.img from the factory restore thread to my SD card, then did the "Patch file" install from Magisk Manager. It created magisk_patched.img. I copied that back to the pc, and ran "fastboot flash boot magisk_patched.img". There was no need for TWRP to be installed. It is a shame because I would have liked an unrooted and rooted stock backup for easy restore.

I think you were replying to the wrong comment *LOL*. But the charging while off issue seems to be for any source, including PC-data connection.

Arrived today 🙂

Pro1 came in the mail, man what a device! Really need to get used to it. Guess i'll keep using my N900 for writing stuff though. EDIT: Why would I keep using my N900 for writing stuff? osso-notes is perfect, plus I don't want Google to know about the weird (and wonderful) shit I write.

I'm running 7.1 on my Droid 4. Before I hijacked that ROM onto it 4.1 and the Priv I tried briefly and still have because no one wants to buy it is on 7.0 so......this is still a giant leap for keyboardkind. The physical keyboard options existant other than Pro1 are all much more dated than 9.0. Personally, think they did it right. Perfect the hardware, not focus on the next shiny thing in OSes, release now with 9, get their manufacturing stream going great guns so the orders can flow freely, and THEN focus on making a 10 update that is as "practically perfect in every way" as the hardwar

You can do something like this to manage your display size and crop out the rounded corners: https://android.stackexchange.com/questions/57267/resize-screen-for-dead-touch-zone

Interesting! So it's almost working! I wonder how you can add arbitrary shortcuts to the homescreen...

I'd never paid attention to curved screens but know many people expressed their opinion against them when it was announced. Then when first photos/screenshots showed rounded corners on the display I wondered if that is a problem because of the curved screen, seems it is. Guess just another thing to have to get used to. On the plus side, I imagine 16:9 video won't show those rounded corners when fullscreen cuz our screen is 2:1.

I can launch the activity, but when attempting to crate a shortcut it does not appear on the homescreen (nor app list). (it is launched disregarding the selected dark theme though) Output from similar app

Well actually it more or less follows the shape of the device that is not entirely rectangular either. Personally I'm so old-fashioned that I would have preferred it rectangular too though (I have applied a third party screen protector on top on the below)

I guess you should be able to map a shortcut key to the launcher itself but telling it to go to the app list not sure :S

That's why I proposed one of those small mice that you have in the keyboards of ThinkPads. I used those a lot and if space is missing, they do a very nice job. Of course, there won't be a mouse on the Pro1. I think it's because they use different chipsets with components that don't work plug and play. You basically include some sort of drivers in a chipset that are not available to the public. So one compatible device doesn't mean others are.

Yeah but seems like Pro1 isn't supported. I really don't understand that about smartphones - why do they all need seperate images? That is such a frustrating thing about Android/ARM.

I don't understand this stuff well enough myself to explain it, but if you need a desktop solution that works today, I think your best bet is sfos with linux chroot. For example Filez and more infoz here: https://github.com/elros34/sailfish_ubu_chroot It's up to Ubuntu 19.04 now and appears actively maintained. I recognize the name elros34 as he did the sfos port for photon q.

After 13 months we're very likely at a stage where the phones are sold from stock and also have other retailers available. For example, the DragonBox Shop, based in Germany, is already taking additional pre-orders. That would be one option for EU customers to avoid importing if Brexit happens. Nothing to really worry about at this stage indeed.

My "unboxing"....keep it simple. Another proof of reality for all unbelievers 🙂 https://youtu.be/hn4RHNfDPLE

When it comes to remote access to Windows, my favorite is Parsec. It is aimed at gaming, but that doesn't mean it can't be used for other purposes. I admit, I have not touched RDP based stuff in a good while, but unless they stepped up a ton, Parsec offers a way smoother and lower latency experience. In the local network it's very close to sitting in front of the screen itself. In my experience it's also a tad bit better in latency compared to similar technology, such as Steam Link. It does support hardware keyboard/mouse/gamepad input from the Android client, so it would be a good fit for

Thank you for another update written with openness. I personally am disappointed by the lack of case, since where am I to get one otherwise? And the lack of clarity about it. A sleeve is of no use, because it won't be on the phone during use which is the most likely time for dropping it. But it is not a massive issue and it makes complete sense about the difficulties based on the unique design of the Pro1, and I can understand why no case is better than a bad case! It's a tough job you're doing, bringing this product to market, and I do appreciate the challenges you must be facing.

That's not how I use my phone, but I could be in the minority. I get text messages or other instant messages all through the day. I keep my phone in its holster. When I get a message, I take it out, open it, reply to the message(s), close it again, and return it to the holster (or desk/table). And without any bezel on this, I'll be sure to close it every single time I'm not holding it in case it falls. I do my browsing in landscape mode with the keyboard out. Email = keyboard out. I don't use a lot more apps as often as the ones that require keyboard input.