Leaderboard

Today i got the headphones accompanying my very early delivery from November. I am very satisfied with the build quality. The cables are soft but sturdy enough to not knot easily. There is no plastic smell, all components feel worthy. Compared to quiet neutral Sennheiser, the the mids and bass are nicely emphasized. No distortion in the heights even at unbearable 100%. They sit very comfy and yet tight. My expectations are met, Thank you at F(x)tec.

That is the story of all of Europe. But big parties should not forget 80% did NOT vote for a nazist party, so going more in that direction has the chance to scare of 80% of people to the other side...

What are we defining as large file transfers, exactly? At 480mbps, copying 1GB takes 20-30 seconds depending on your USB controller--no, they're not created equal! I can move tons of junk in a few minutes. Makes me think of this: https://www.gocomics.com/calvinandhobbes/1995/08/17

@Swond Regarding phone automation, look for Situations in the google play store. There was a "Nokia Situations" back in "the good 'ol days" and this android version was created (and still maintained) by the same people behind the original. It does exactly what you are looking for...if this condition (wifi, bluetooth, location, time...etc), then do xxxx. I use it to switch ringtones, volume (like an old symbian profile) automatically when I'm at work. It works like a champ; solid. https://play.google.com/store/apps/details?id=com.pastillilabs.situations2 https://pastillilabs.com/

It has an option to draw visual borders (shades) but you can turn visualization off.

Hi everyone, Exciting update today. Liangchen is visiting the factory in China at the minute and he expects all of the pre-orders will be produced by the 18th of January, so in less than 5 days now. We have already produced a very significant number of pre-order devices, which are waiting for the full list to complete by the 18th. As you are all well aware by now, once the devices are all produced on the 18th, the stock will be rotated between our warehouses, so there will be, I'd say, 1 more week after complete production before you receive your tracking. Just so I don't overpromise

In general, yes. But companies might not want to advertise an option that makes criminals out of naive users who just don't know the laws about recording calls, which I guess might be a large percentage of the people in those states where the laws demand two-party consent.

Sorry some communication mixup, cuz that's what I thought I suggested in the first place.

I know that @Craig had to input an APN for his AT&T MNVO. You might check their web site or ask customer service what apn you should use in your area.

On my Relay 4G, my SD card is faster than my internal storage. I use an app called Link2SD (https://play.google.com/store/apps/details?id=com.buak.Link2SD&hl=en_US) to allow me to run apps and have them store their data on the SD card (in a special partition). I was worried about that slowing them down, but before I went through that transformation, I tested the storage speeds with another app and was pleasantly surprised that the SD card was faster. I'm sure that isn't the case in newer phones, but in older phones it can apparently be true. After utilizing Link2SD, not only did I

I'm guessing you are talking about non-fast charging chargers or Qualcomm Quick Charge chargers. Those are all typically Type-A connectors. Quick Charge is Qualcomm's proprietary standard. Power Delivery is another fast charge standard that newer phones use. It is an open standard created by the group that handles all the USB standards. Apple's phones use it. Google's phones use it. And some number of other, newer Android's phone use it. It supports delivering more power than Quick Charge. Quick Charge tops out at 18 watts. Power Delivery tops out at 100 watts. But you typically

Except that I don't think I want to get every last drop of it out of the carton when that happens! :-)

While milk can also become a thick product quite easily.

Some pages ago during December I requested a refund for preorder, and decided to wait till FxTec could actually deliver. Everything has been processed in a friendly and timely manner :-). What I can also tell is that I bought a Pro1 from a friend who had a preorder with IGG. He received the phone last week and found it to large as his daily driver. So since yesterday evening I am now the owner of a Pro1! I can tell you all it is worth the wait. Yes the phone has pro's and cons which I will describe later in the "Independent reviews" topic. For all who are curious, S/N is 000211.

I honestly don't know how many pairs of shoes I have, what I do know is that I need to buy a new shoe cabinet 😄

As a former computer security professional, I want to emphasize that everything tdm has said is correct. But any serious discussion about security needs to be very concrete about the threat model, or it becomes very difficult to determine what the effects of any change might be. Google has produced a detailed white paper describing the security model of Android, and it lists 15 different threats in section 2.3. Only the first two critically depend upon secure boot, i.e. the cases where, "Adversaries can get physical access to Android devices," and the primary attack vector involves modifying t

So just a quick update regarding Secure Boot. I had considered posting a new thread about this but I'm not sure it's warranted. So I'll just drop this here... I spoke with FxTec and they confirmed that they disabled Secure Boot intentionally. The rationale was that it makes the device more developer friendly, especially for non-Android OS's. I'm not sure I agree with this conclusion, but that is/was the decision. The one thing that disabling Secure Boot allows is building a custom abl (boot loader). I have yet to see anything that requires a custom abl. But it does leave the

I am pleased to announce a new member of the Pro1 ROM family: "Ungoogled Stock". What is it? This is the stock ROM as built from the BSP directly from IdeaLTE with the following changes, and only these changes: Removed AdUps OTA update code. Removed GMS (Google Apps). Where is it? The current version is: http://files.nwwn.com/android/pro1/QX1000-user-nogms-noadups-20191208.zip MD5: 01c90007a843328b869bb294c8f88330 SHA1: 3aff440c50ec2464437c5698bc1c7740ed827c34 Source synced to BSP as of Nov 29, 2019. How do I flash it

@Swond IFTTT and Tasker are probably the most common/popular automation apps.

I really think XFCE is the desktop solution that works if you want it. OpenOffice works great. Ubuntu has huge repo of software. And, correcting my earlier post, etr works great! https://twitter.com/enigma9o7/status/1217272071178215424 And here's some random screenshots (not actually random, made them to show someone else how I did my scaling settings)

Oh wow. That's very minimalist. I'm a dude, and I like to think I'm a man's man, but I've got WAY more shoes than that. I guess it's because I have to function in professional circles, outdoor activities, some of which are pretty hard work, and 6 MONTHS OF WHITE FLAKES TRYING TO BURY ME because I'm an idiot and live in Northern Michigan. ROFL!

Perhaps I wasn't clear. ZRAM creates a virtual swapspace (used by the kernel as extra RAM) which is backed by system RAM, and stuff going into it is compressed to save space. I created a TRUE swapspace as a file on my SD card and use that instead of ZRAM. A 256MB swap file gives about the same amount of additional usable RAM but without the additional CPU overhead of ZRAM (no compression, just I/O) and my phone is much more stable that way. I used to get random reboots every few days at most; I can't think of when I had one with a page file. One time I forgot and yanked the SD card; that predi

It really is a shame that apps don't draw relative to the logical size, or give the users the option to have them work against logical or physical. Agreed that this would be best done by fxtec. And it does seem appropriate, since the curved screen is part of the phone design and does cause some people issues (whether functional or visual). And by that, I mean not just replicating the edge null functionality, but also re-setting the physical display size so that we can have the display end before the curves (user configurable, of course).

History is definitely on your side. 😂

As mentioned previously, I use a WebDAV server on my phone and a WebDAV client on my PC to map the phone as a drive letter. I then use an optimized file copy application on the PC to do the copying, for maximum speed over a wifi connection. There are a lot of variables here (phone hardware speed, phone software speed, wifi network speed (a lot of variables just in that area), PC speed, etc.). I use the above for both speed reasons and to transfer large files. I've only found one WebDAV server for android that doesn't choke on very large files (in my case the files were approximately 4

WebDAV is built into Windows too. You can map it to a drive letter the same way you can an FTP server, in explorer, without installing anything. I don't remember if it was the performance or if it was flaky in some way, but I elected to pay for a product to take the place of the built in WebDAV client in Windows. But it is there, and probably works for most use cases.

Running a ftp server on phone is easy cuz all PCs support it, you can add it as a favorite/bookmark to file manager in windows or linux or anything else, without installing anything on the PC end. I use this one, super easy to configure, even has an option to auto-connect when you're on home wifi, so basically whenever you're at home your phone is available in your PC file manager. https://f-droid.org/en/packages/be.ppareit.swiftp_free/ (fyi, fdroid version is same as full version from playstore, even tho it says free.)

True. But for some reason, I think the planets are more in alignment this time. I'm guessing they'll at least get out a good chunk of them this time. I could be wrong, of course. :-)

This post is kind of off-topic, so sorry about that. It should be hidden because of that.

Hmmmm.... 1 hour drive to crossing, then half hour to 'HK Dispatch Center". Wikipedia says the crossing is open 24 hours, but dunno if they actually close for holiday or something. https://en.wikipedia.org/wiki/Lok_Ma_Chau_Control_Point If what Chen predicted comes true and they finish making them this week, they've got all next week to get them to HK and send to ppl... seems doable... and if they miss that, HK doesn't have quite as long as holiday as PRC, only a few days... so shipping by end of the month is possible (which is the last business day of the week commencing on the

The subject is really complex – Wikipedia has an overview at least for some countries. Laws differ between European nations just as they differ between US-American states. Some countries, some states are fine with one-party consent, others demand two-party consent. The question whether a company is allowed to "record all calls" (without the works council agreeing) is an even more complex matter, because it is affected by labour protection laws, too...

FTP over wifi is probably faster and more reliable than anything you get over that shoddy MTP over USB to be honest. If you had mass storage mode, that would be a different story of course.

I hope someone find a case that naturally opens in the other direction. Maybe we should be looking in countries with right-to-left reading direction, as they would have the wanted book direction as the natural one (The cover opening to the right). So If we can find a Japanese phone with the right dimensions we might get a good chance. I can not read Japanese at all, so are limited to translations, but perhaps we got someone in here that can do the right search? Similar to this search but including all the a Japanese devices GSMarena does not. I optimistically tried this: https://www.

But to be on topic a little, I'm still not sure if I would want a case for the Pro1. Of course I would like to protect it because it will be the most expensive phone I ever had but I'm not sure if I want to sacrifice the ability to quickly open it whenever I want or spoil the looks of the device with a bulky case.

Edge Null does draw over other apps. With a dead zone on the whole right and left. This does on one side mean that it is running constantly and also draining a bit of battery. The bigger problem for me is, that drawing over other apps is a potential security risk. To be clear I am not aware how android currently implements the draw over app function. But it at least was a thing that some apps were drawing over the whole screen record all your input and dispatch the input down to the underlying apps. So it was easy to get hold of passwords etc. After all the app has full network acce

That looks exactly like mine. also USB 2, but don't care for the same reason @Craig doesn't care. Large file transfers are pretty rare for me, so even the 2,0 speeds are fine with me.

Just a guess, but a reason for device manufacturers to not make call recording available could be legal, rather than technical. Under quite a number of jurisdictions call recording is illegal (without explicit consent of both parties)...

Thanks for the link 😊 I installed FinQwerty v1.5.2 on the Jan 10th Android 10 GSI build and it seems to work.

So I've been thinking about this custom key that AVB allows, and I've also read a bit of the source for abl where it's implemented. I've come to the conclusion that AVB is worthless at best and dangerously misleading at worst on devices that have Secure Boot (*) disabled, and the Pro1 is such a device by design. Let me explain... The security that AVB intends to provide is to ensure that you are running code that has been signed, either by your OEM or by your custom ROM vendor that does AVB signing (Copperhead, Graphene, etc.) Note that it does not ensure the integrity of your d

In this case, I would take "firmware" to mean everything closed source. Particularly the abl partition and the vendor bits for hardware support which occasionally have security issues. The official Lineage policy for device maintainers is to assert on the latest firmware version from the OEM (eg. fail to install if it is out of date). Some maintainers are better than others at following through on this. Here's an example of how this is supposed to work. I have been using OnePlus devices for the last year or so. Every time they release a new firmware, the maintainer

@tdm Thank you so much for the information you're posting here, it's very interesting. I do have a question about the "firmware" though, some people say that custom ROMs will lack the firmware updates that official (still supported) ROMs have, and thus can be less secure in that way. Are they talking about what you're calling the "vendor bits" for hardware support? And how out of date could these be for this ROM or LineageOS for the Pro1?

Well, this looks promising... tommy@neuron:~$ echo x > foo tommy@neuron:~$ fastboot flash avb_custom_key foo target reported max download size of 536870912 bytes sending 'avb_custom_key' (0 KB)... OKAY [ 0.009s] writing 'avb_custom_key'... OKAY [ 0.003s] finished. total time: 0.011s tommy@neuron:~$ fastboot erase avb_custom_key erasing 'avb_custom_key'... OKAY [ 0.003s] finished. total time: 0.003s tommy@neuron:~$

There's a bit more info here: https://source.android.com/security/verifiedboot/device-state So your co-worker was right (the original key is permanently baked into the hardware), but you can also in theory supply another key to use. It guess this feature isn't widely implemented though (or at least, nobody cares / hasn't tried it) - supposedly OnePlus 5/5T and a Xiaomi phone in addition to Google's own devices.

That is not possible. If it were, anyone could do the same and it would defeat the purpose of verification. Only the OEM has the signing key and only the OEM can create signed images to pass verified boot. As mentioned, yes, some of the IdeaLTE bits/blobs are used to build Lineage. But only those necessary to support the hardware. In general, OEMs that do stupid and/or sneaky things place them into the upper layers of Android which Lineage does not use. Briefly, code running on Qualcomm devices (and most/all Android devices) can be divided into four broad

That's an interesting perspective. May I ask how you came to that conclusion? My feeling is exactly opposite. The OEM may or may not provide security updates for a period of time after release. My copy of the BSP is on tag LA.UM.7.4.r1-05500-8x98.0 which was released August 23, 2019. Incremental updates may have newer code, I'm not sure because I don't do OTAs. But either way, IdeaLTE will stop publishing updates at some point. As a member of Lineage and former Cyanogen employee, I can assure you that many/most of the Lineage developers care a great deal about secu

Hey all! I am very happy about another Rom for the Pro 1 🙂 Thanks to all being involved into the progress! I've had some problems that I managed to work around, as a total noob. Previously I've had installed the Linage test rom. After flashing all the "ungoogled files" (Powershell says everything was succesfull), the device wouldn't boot into the system and I had no option to wipe, as told in the example in the first post. Easier way: First restore the factory rom -> than flash the ungoogled rom. That worked fine for me. Now I'm happy to explore, what's working 🙂

Well...... yes but not exactly. Lineage is built on the open source portion of Android (AOSP) and the portions of the Qualcomm code that are released as open source (the CodeAurora project, or CAF). The portions that Qualcomm does not release as open source are taken as binary blobs from the stock firmware and integrated into the Lineage build to make a complete package. Because this is a sort of legal gray area, these blobs are kept strictly partitioned from the Lineage project and made available under the github account TheMuppets (really!) The portions t

Unfortunately, no. The BSP is proprietary. FxTec has shared the BSP code with a few developers, but it is not generally available. This is one of the reasons that Lineage exists. And please don't get upset at FxTec and IdeaLTE. The bulk of the BSP is licensed to OEMs by Qualcomm. It is only through the generosity and trust in developers that FxTec has made the BSP available to developers at all. They did not need to do this and, in fact, are not really supposed to do it. Also note FxTec and IdeaLTE could release their device code if they chose, but it wouldn't do much good w

I'm not going to try right now, but the short answer is no because the kernel binary is not signed with the device keys, which means the stock kernel modules in /vendor would not load and WiFi would not work. You could work around this by putting the stock kernel binary into my boot image. However, at that point, you may as well use a stock boot image. Additionally, the following things come to mind: The adups properties are not present. This will likely prevent OTA updates from downloading. Which is fine, because: The build is signed with test keys, so recovery will refuse to