Leaderboard

These tools change the way Android works. If they have a bug or if they are misconfigured, it is difficult to track down the issue. So users will frequently file bug reports against the device in Lineage and waste developer time trying to reproduce an issue that doesn't really exist. For me, personally, I don't like to give that kind of power to any program that I have not personally built and reviewed. And both of these tools are complex enough that I'm not going to go through their source code. Further, they both have a modular system where anyone can contribute. This means

New update on the IGG-Page: 2) We have been looking into dbrand for Pro1-X skins, as well as an alternative protective casing to the leather pouch that already comes with the phone. There have been a huge number of requests for a protective case & we want to make sure your Pro1-X stays safe! I personally like dbrand 🙂 (But a real case would be so much better as a skin)

So turns out the phone was sent back (went to the apartment building and talked to them directly on Monday), but the phone was sent back almost immediately after it was received, so it's been over 3 weeks since it was returned to sender. I put a ticket request in to fxtec on october 27th to let me know what the status was on the phone that was sent out, to this day have not been responded to on that ticket. I'm hoping the phone was properly returned in the end...

OK. Problem solved (for now). I re-flashed the same 16.0-20201026-NIGHTLY-pro1 via sideload and guess what: GPS is working again. Previously it had been installed via OTA update. No idea what may have gone wrong there. Thanks to all for your support.

Hi, There's no good reason for me to post, I don't have one of your phones, yet. However I'm signing up on the indigogo tonight. Really all I want to say is that I just watched your interview on Linux for Everyone's YouTube channel. Right at the start Adrian says you wanted to bring back the hardware keyboard to a modern device. That line was brilliant ... I really think you should put that clip front and centre! The line completely hooked me as the same thing I've been hunting for ... I carry 2 phones, one of which is the BlackBerry key2, nuff said? No? Well otherwise I resurrecte

Yeah, specially because Linus audience is much different from the niche. It did get some exposure for us. I know some people responded in the comments there about the phone with interest while some just reiterated about old SoC and such. He knows how to make a show, he knows how to put parts together to build a PC.... However He doesn't know (and didn't understand at the time) why the PRO¹ is stuck with a SnDr 835 (and not an 855). He isn't into keyboards, because he types just fine, etc... Unfortunately, the camera software leaves a lot to desire when comparing to other flagship phon

For those asking why AICP, I personally have two main reasons: It has more customization options than Lineage. It is more fun to work on, Lineage takes themselves too seriously. I've been using custom ROMs on my devices since my first Android phone in 2012. I have always run AOKP for the above reasons. But AOKP is gone now and AICP fills the same needs for me. That said, I'm aware Lineage is perfectly fine for a lot of folks. That's great. The beauty of it is that you can choose what you like. 🙂

I've done a first build of AICP Q using the Lineage 17.1 sources as a base. After it is tested for a while, I will probably try to get official support. The boot image is used just as in the Lineage test builds. Flash it with fastboot, boot into recovery, and then flash the main zip. If you want gapps, I tested OpenGapps pico for Android 10.0. Don't forget to switch slots before flashing gapps. Please report any issues and I will try to sort them out. Boot image for initial flash: http://files.nwwn.com/android/pro1/aicp_pro1-q-boot.img

I haven't found a technical datasheet but it may be a software configuration during boot or also a hardware configuration which may need a minor modification like pulling a pin up or down or keep floating. So currently it is an open question. 🙂 Right but having support of another protocol sounds really great if it is possible to support both at the same time.

Chen wrote the following in Indiegogo comments: So it seems Pro1-X will have support for USB-PD if everything go right. If it can be enabled in Pro1 is a good question, maybe it is a question of how complicated it is but currently Pro1 does not support USB-PD.

Also we should not forget: Phone reviewers had to focus on small hardware changes! There wasn't anything besides that. In this function you will start to get picky about that stuff, and loose the sight for what is important. The SoC isn't really the limiting factor of phones nowadays. For most people it is the small screen or the touchscreen. This phone does improve on both of this factors. But this doesn't anything for you if your job literally is to test new phone stuff. If you are writing code or even E-Mails (Like most people do) this does help!

Even though F(x)tec is small, the companies f(x)tec has no choice but to rely on are not. Usually that is true because they have no outside dependencies. In this case, there are many dependencies. Having an OTA update approved by google for Android costs 10000$ or more per build. Snapdragon has preference on the priority for the chips Cases have to be mass-produced, although not in the millions, which requires a factory willing to accept. Otherwise, it's prohibitively expensive to produce. How do you know the prototype they have shown is actually a good product? It l

Linus is too picky about phones 😄

I regularly either mute myself or activate some other function by accident on "traditional" phone calls with this phone. And it's also slow to turn the screen on when I move the phone away from my head. There is definitely something weird with this proximity sensor, more so than other phones I've used.

Maybe, if I can find the time.

OH! 😮 Very surprised! So does this mean a Pro1-X is NOT just a Pro1 in blue with different memory/storage option? Now I'm getting very curious on whether this is just a software update away, or there are other hardware differences??? The roughly 18W is what we currently get by the QC 3.0 BTW

Interesting. I'm using sideloading too so that could be why I did not see it, (gave up on OTA for Lineage a while back)

We haven't gotten any word about batches, how many orders they have left, when they will be in general availability. Official or otherwise

I have personally cut a skin for my Pro1 and generally I think it is a good thing. However, it will not replace a good case which - in my eyes - is a hard rubber-like thing which can be applied to the phone and used together with it. That is the hardest part if one would like to solve it by hand. So I agree, a real case is the most important which can be used together with a skin.

Hey @Slion, how about swapping the left AltGr with Fn? This would make it closer to the current layout and hence maybe increase chances of having it approved. That's one of the reasons which contributed to making this choice for the qwerty proposal and it would be consistent. Both AltGr are still independent so one could configure Alt_L on the left AltGr if they don't need two Alt_R, and that would make easy Ctrl+Alt combinations on both sides. Also, Fn+Alt would be easier by default, which could be useful for Alt+F1-12. Ctrl+F1-12 would become a tad more difficult, however. Is it necessa

I have also experienced a similar issue using my Moto G6 and its stock Android. That case the solution was I think switching an option what tells what kind of sources Android may use for location services (maybe WLAN, Mobile tower, etc)... I don't remember the exact name but I had to switch it to other option then back to work it again. Switching GPS off did not help, restarting did not help, GPS had no lock. Other phone and other system, but it may worth a try.

May I ask why you don't want Magisk on your phone? In my opinion, Magisk is as important a "tool" as the Xposed framework. Being able to modify /system without actually touching the system partition is ... magic 🙂 Magisk also brought Xposed to Pie and Oreo with Riru. OK, it gets fishy and suspicious here ... despite that, I would not touch a phone I could not run Magisk and Xposed modules on 😁

Thanks, Other have reported that too 😥, so somehow this can get loose, but its luckily possible to click back in.

The earpiece on my phone stopped working. It would work when I pressed down on the screen in that area. Almost like a cable was unplugged. It was like that for at least few months. Not sure how long because I rarely talk on the phone. Last week, I was cleaning the screen and pressed a bit hard on one of the corners. Heard and felt a pop. Now it works properly. A bit strange

Just wanted to weigh in that this particular layout looks fantastic to me! Especially if the slant arrow also got me F1 (slant+1) through F12 (slant+equals).

I will be maintaining AICP for a long time, I'm sure.

Maybe this 36 pages long thread have finally been seen as an indication of some users being interested in protecting the Pro1(x)... 😇

Well, one argument I get to hear way too often is "Too many options/settings confuse most users!". It might be as simple as that. In addition, even settings that exist and work on LOS or AOSP might not be easily accessible because it would be too much work to add them to the settings UI (for just a few power users). Having said that, I don't know why the AICP does not add all these settings to LOS and maybe hide them in an "advanced" tab. Apparently, AICP also contains additional software, not just easy access to settings through the UI.

AICP has an impressive list of features: https://github.com/AICP/vendor_aicp/blob/q10.0/docs/features.md It looks like they implemented features from GravityBox and other customisation apps and Xposed modules. @tdm Will AICP be maintained like LOS, or is there a chance development for AICP will stop sometime in the future? I don't have a clue about how much work is involved in maintaining two or three Android varieties instead of just one.