Leaderboard

Most threats can be avoided by installing only trusted (if possible open-source) software on the device. This includes an up-to-date web browser. No one is forced to use the default browser shipping with the OS. Of course, having AOSP security fixes would be nice, and we would readily apply them if we could have them without the functional regressions related to upgrading to a higher Android version.

I do not understand this point. Actually, the Pro1-X SoC still has a long support life ahead. After all, that was the reason for the switch. With its longer EoL, the 662 Pro1-X may also eventually have better software support: I doubt that newer Android versions will ever appear for the original Pro1. Ubuntu development is probably focusing on the Pro1-X right now. In the long run, the 662 may also have better chances regarding mainline Linux support than the de-facto obsolete 835-Pro1 ... Finally, the redesign of the mainboard may be a chance for FxTec to fix a few quirks of the ori

I have one phone i stuck an iphone 4 keypad to I found still in stock in a local webshop after a long search: I cut off the edge of the iphone case thing with a knife and put double-sided tape on there. Removing the case entirely wasn't possible as it's integral part of the sliding mechanism. It works allright but there only being a shift key on the left side is rather annoying, also it slightly interferes with the camera when closed but if I'd been more thoughtful before sticking it on there that could have been prevented I think. Also the keypad is quite low quality and it's

OK more updates... Mine went absolutely nuts again, couldn't even control it. Out of desperation, I tried loosening and retorquing the screws mounting the screen with, seems like it helped. Somehow I managed to get it back in control to a usable level. One theory was that it could be due to the mounting of the screws causing a torsion on the screen, since sometimes pressing on the side frame it would trigger the issue. Could be fluke, not sure. Guess I'll just have to keep experimenting till I get my replacement screen.

...and my cat today in a very dark environment:

That is a very good point, indeed. With PCs, "compatibilty" (with the IBM XT/AT) was seen as an advantage. With phones, we obviously must have taken a wrong turn somewhere ... The good news is that a World of incompatible devices could prevent SkyNet from spreading all too easily. 😉

You're right. I just checked by powering it back to life. I've put lineage 14 at that time. And it's damn slow... It boots and charge the battery though. It's funny how it looked big at the time I got it, and now it is cute and the good size to me. Sad in a sense...

I have a Droid4 I can send you (from France should be easy), but it is one I got used and yet in a pretty bad outside shape. If I remember correctly I've put cyanogenMod on it...

Here is the keypad before sticking it to the phone:

The PRO1 doesn't have any locks or any artificial limitations applied. However, some providers lock it out or make the process harder to allow the PRO1 to work in their networks.

I tried version 7.2 for pixel, but it doesn't recognize our camera button. The shutter sound works tho, unlike stock snapdragon camera. I see there's lotsa different gcam ports. Anyone know one that works well with Pro¹? Maybe a device that has a camera button (assuming pixel doesnt...)?

Well the hardware is just fine. The default app is a bit so-so, but a LOT of camera apps can access the camera using the Camera2 API. As long as you stay away from HDR (there is an odd bug in the implementation of the API for the Pro1, that add odd shadows when the app try to stitch the two together. HDR in the the Stock app works though.

...and she is my 15 years old cat four days before the rainy day above, in a sunny day:

The following photo was taken a few minutes later:

The following photo was taken afternoon in a rainy day mid-March, it was raining a bit. I had to reduce the resolution of following images because of 2 MB upload limit.

The short story: the keyboard layouts seem to need a factory reset after upgrade to 18.1 For the long story, see the error report linked above...

Right, but if SoC manufacturer does not help, mainline Linux support will come later (if ever), then the hardware becomes obsolete, manufacturing stops, people change hardware and also maintainers may move and the code may be also obsolete in the kernel (sooner or later). However, a chip being supported fully by the mainline kernel would be a very good effect for the long-term future, that is absolutely right. I am writing this on a 4-5 years old PC (Thinkpad P50) which was replaced an around 10 years old another one last year (Dell Latitude E6510), but basically the same system runs

That is why we eventually need mainline Linux support. And truly open-source phone operating systems. 🙂 I am typing this post using a fully-updated Linux OS running on a 12-year old PC (Thinkpad T400). If the hardware endures, nothing will prevent me from installing the most recent Debian distribution on it for ages to come. Remember: the most recent Linux kernel can run happily on an i386 with 32 MB of RAM ... That is where we want to go with phones, too! I am of course half-joking here: You are completely right that money its made (in obscene amounts) from planned obsolescence. The

You are right, however, this industry is moving too fast, so 662 will also be obsolete in a few years (but it is currently relatively new), so better support is very likely in a long run, but this too short production time of the SoC definitively results in a poor software support later. 😞 I don't like how fast these replacement process is while technology should be good enough for years, so it is not driven by development but simply to sell newer units making old ones waste... It is not about F(x)tec, it's about the phone industry itself. Right, also looking at correct alig

Well i don't know about that but if anyone really needs them, they are still available on the discord channel.

Have you guys looked at an android security bulletin lately? https://source.android.com/security/bulletin The appeal to target android devices is incredible for attackers, since there are so many older devices around. I can't wrap my head around the "I'll stick with stock" or "I'll stick with LOS16" messages around here. That seems like insanity for a device that isn't airgapped or even worse if you actually operate a browser on it and access arbitrary web pages.

That is not true. As I wrote, I had LOS 16 from the point it became official and applied every update until support was dropped. None of the weekly OTA's broke anything related to the chroot set-up. AOSP security fixes do not change system behaviour on that level. Major upgrades, on the other hand, do. That's why they are called major, need to be well prepared, and, therefore, should not be necessary very often. Yes, you can still build LineageOS 16 and 17.1 yourself for the Pro1, which should merge-in the upstream fixes automatically. Retrospectively, I should have learned how to

Why not? No OTA update of LineageOS 16 (and I did apply all of them) ever broke that set-up. Why should it? After all, what I do there is not black magic. I make use of system interfaces that are, explicitly or implicitly, defined to behave in a certain way. As long as the Kernel, Android features, or root management did not change, I could be fairly certain no upstream security fix would break anything. I had simply expected LOS 16 to continue to receive security patches as long as upstream Android 9 does. That it didn't is disappointing and, yes, unprofessional. As you confirm

It'll likely get worse from this point onwards. I'm not seeing that many vendors on Taobao selling replacement screens for Elephone U Pro (same LCD used by the Pro 1), so it could mean it's a discontinued part.

The case in black.

Tried to extend the opengapps table with MindTheGapps: The last two I THINK could be included as obligatory in say "Google System Base" for OpenGapps. (I got them on AICP Q + OpenGapps 10 Pico also)

Note that one is a preorder, the other a indiegogo perk. That is the first is a conventional buy with the buyer rights that offer. The second is an investment without the same rights. Or said otherwise on the first FxTec have the risk, on the second you have. That is the reason for the pricedifference. But you should be able to cancel the preorder anytime, and take the IGG perk instead if you wish to - but you can not cancel a perk (except some days after picking it) I would suggest sending a mail to info@fxtec.com

...As long as we avoid HDR mode, yes. Currently HDR works with the stock app, but not trough the api with other apps. Be aware that the HDR mode does not work as intended. It do take a high and low light image as it is supposed to, but some metadata handling in the Camera2 API interface must be wrong, so when the software tries to stitch the two together, we get odd shadow-results. e.g. OpenCamera HDR works just fine on a Samsung S8, so not the app that is wrong. it must be the returned images that does not match the requested shuttertime/ISO settings. And this obviously confuses the

Based on your description it seems that Snapdragon camera is hardcoded to the camera button. I think this is a bug, as it should launch the default camera.