Leaderboard

Couple updates, especially for the developers out there... I'm working with one of the upper level Lineage guys on getting the device/kernel officially imported. He has made quite a few comments and suggestions for cleaning and improving the device tree. So the lineage-16.0 branch on my device tree is going to be rebased and rearranged quite a few times in the next couple days. I tagged test18 so it doesn't get lost. Said Lineage guy is actually interested in the Pro1 and I will probably send him a prototype unit. So that's even more development support. Which is g

Do you know what you are talking about? I understand you can do something DIY but to design a phone (both electronically and mechanically), do correct measurements, design antenna system, design manufacturing process for mass production, do certifications, etc are another matter. It is a long and costly project and you also have to work on software side which also has some stages. Anyway, they have also reached that stage what you are speaking about a long time ago but it is only one part of the whole process. Also, you had a phone to work with and not counted the time and eff

test19 is up. Changes: * Code cleanup for official submit to Lineage. * Add VoLTE props to fix VZW. Please verify everything works properly. FYI, this is my remaining TODO list before submission: * Verify WiFi and BT MAC addrs are set as in stock. * Regenerate vendor blobs from latest stock. * Fix poor kernel commits (fix stuff, fix more stuff). * Verify WiFi works on clean install. * Go over remaining oneplus specific stuff in rc-files, sepolicy, etc. Additionally, here is the updated proposal for the wiki pages: https://

Not sure why you are giving him such a serious detailed response... he does, after all, admit at the outset that he's a troll. 😄

I know it's hard, but it is very difficult for them to be exact and has always been that way. If you got a order allocated email earlier this week, know that it is indeed coming. But even going back to December, "end of the week" would often wrap around to sometime the next week. Not because they are messing with you but because they don't control all aspects of the operation-- that is, they depend on others. Just a little longer. Trust me, the wait is worth it.

Lol. Can't wait to get my SIM back Monday. I'm dying to try out Verizon! 😉 Thanks so much,

Nah, mine was better years ago but good try anyway. However, F(x)tec Pro1 is the best! Qwerty Keyboard Slider [DIY] Pics: https://m.imgur.com/a/Pbvpo

Hmm, unsure. ☺️ You are right that his / her nickname is self-speaking. 😄

I was waiting for my pro1> six months. Fed by promises, I canceled the order. (which I will stick with you, because you support the wrong manufacturer). It took me 6 days to attach the keyboard to the phone: select the base for the keyboard, build a schematic, write 2 huge programs, make corrections to the kernel code. What has fxtec been doing for years? Shame. https://www.youtube.com/watch?v=K1XQ5Hv0sZo

Same thing happens with Chrome. Only difference is that in Chrome the incognito notification will close incognito tabs and remove the notification. In Fulguris the notification opens incognito tabs so the notification never goes off. However, I don't know why the notification doesn't go away when you remove browser in recent apps. Probably it is related to Android's memory management. In general you should not "kill" apps by swipping them from recent apps menu. Closing Apps to Save Your Battery Only Makes Things Worse

I get exactly the same behaviour with Fulguris sometimes. After killing the browser completely, snapping the keyboard slider open and closed switches to the task manager screen (whether incognito or not) and the only way to fix it is to restart the phone. Interestingly enough, it also happens with K-9 Mail once in a while, too.

Still unable to get it to work 100% with my device. I don't use any battery saving settings though. I've been through settings with a fine tooth comb and can't find anything that looks like it could be causing conflicts, not even in developer settings. Once I switch off the accessibility for FXService then the prox sensor comes back online and works every time under testing. 🤔

Still no support of aptx (HD) after the recent OS update. Let’s hope for next one 🤞😌

I just had that same issue. Though I have been using Fx Service for months and never seen it before. To fix it I just restarted the accessibility service. I can see two possible root cause: The last release slightly changed the way it uses the proximity sensor. Maybe that regression was introduced then. However you were first reporting that issue in an earlier release. Maybe it has something to do with Battery Saver mode as I recently started using it.

I have also called service provider's IVR system and I haven't noticed call is quieter than before... or at least it is still too loud.

No I haven't - I'll take a look. But I just wanted to report back on whether any of these issues had been addressed in the ROM, since people were wondering.

I just called my mailbox and it's still pretty loud, even on the lowest call volume setting. mailbox = German for voicemail-thingy

Sadly I can confirm that wake- and backlight-on-keypress are not enabled with this update 😞 And Sym key seems to do nothing still...

I have it the other way round. The most annoying bugs should have highest priority. Most likely what ever customisation they do can be moved over from P to Q at some point. And I would much rather have a stable P than a buggy unstable Q

I also feel the Pro1 hardware is more than enough and the keyboard is a huge plus, so I would not trade my Pro1 for anything else... However, about photos... have you tried GCam mods like "Poco F1"? It takes really good photos even in dark environment - so basically also its camera is good, just need a better software than stock one.

New mailing from Fxtec: Hello! We hope you are well and keeping safe. We just wanted to get in touch to give you an update with regards to manufacturing and shipping of remaining customer orders, but also to fill you in on everything that has been going on with the F(x)tec team. We are still currently understaffed as some of the F(x)tec team are on on furlough. This has undoubtedly resulted in our customer service and email responses taking much longer than usual to sort through and respond to, and for this we really do apologise. We are working through queries as quickly as we ca