Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 08/29/2020 in all areas

  1. My ear speaker broke lately. (The one you use in calls) Not exactly sure how. Maybe the phone fell too hard onto my couch, or I've used it too rough? Who knows. Anyway I quickly found out after not hearing anyone whom I've called - but the normal speaker did work. So I had to speak to them with the loudspeaker on in public, like a moron. As I didn't want to send back the phone and wait for repair I've asked the support if I can fix it on my own. My initial guess was a simple loose contact as the speaker functions if I firmly press on the speakers region. This is what you should also
    10 points
  2. Lineage recovery will offer to install from sdcard if, and only if, a physical sdcard is present and it is able to be read without any decryption (eg. it is not used as adoptable storage). Lineage recovery will not offer to install from /data (including "internal storage" because the data partition is encrypted and Lineage recovery does not have any decryption capability. And yes, file-based encryption counts, because all files in /data/media are encrypted under FBE. This is not a bug. This is how recovery is supposed to work. TWRP bends the rules with data decryptio
    9 points
  3. This is what I have done to solve a couple of key problems I was wrestling with. Verizon connectivity (both Stock and Lineage) and problems with Android Auto (Lineage). Also, the fact that I want to keep Lineage and not return to stock. This is not a solution for everyone. Some may even say it isn't a solution at all. However, it has made me very happy! I first should provide some context for why I have done what I have done and why it works for me. I retired at the end of 2019 and then Covid hit. I am older and thus remain very cautious, even with the world trying to open up. I st
    9 points
  4. Sorry guys, I'm a bit busy with work lately, plus just had a couple kids birthdays. But I'll get the kernel with stock keyboard driver as soon as I can.
    8 points
  5. The majority of the orders are complete. It's only natural for people to discuss a problem in the community, not the lack of. We barely ever hear from the customers who have received their devices in contrast to those who haven't. It's the cycle of purchasing a Pro1 - order > join the community to see if you're the only one waiting > receive the device a few months later > exit community. Of course, we are lucky to have very supportive Pro1 advocates who discuss the positive experiences with their Pro1, but a complain is typically a lot more of a reason to speak than a posit
    7 points
  6. Here are the files again: https://www.dropbox.com/sh/vydlyn2obudlv5x/AAAEa3yOoUxzSIg5INjXqv5ma?dl=0 As I don't like to use cases myself I lost interest:P But happy if it helps someone make a good case 🙂
    7 points
  7. An update has been delivered to my device!
    7 points
  8. People here have ordered replacement screens for about $50 on aliexpress.
    7 points
  9. Sit down at your desk and the doorbell will ring immediately. Talk about your shipping wait time and you'll get your stock assigned email the following week. Order #445xx (Dec 2019 QWERTY) is assigned. I'll be back on the forums in a couple weeks to ask very basic questions about adups and Lineage, I'm sure.
    6 points
  10. Could you email your order ID to [email protected]? I don't see one linking to this community account.
    6 points
  11. I was scared about that one too when I read the forum. As recommended by the community I used the app app edge null. I set border with portrait to 23 and border with landscape to 21. With that I had zero accidental touch on android stock from the beginning (and I do not use a case). I also activated the features to "detect edged swipes" which means you can still use the edges when you do a swipe move. I still manage to use the margin to scroll through contacts, applists. Not an issue for me.
    6 points
  12. All issues for the radio (cell modem) are going to be exactly the same as stock. All of the radio code is closed source. WiFi is mostly open source, but I have taken the stock qcom code for this with no changes. So it should be pretty much the same as stock. There may be some differences in the wifi configuration file that affect performance. I haven't looked at that in a while. As for the keyboard, I really am at a loss to say why @DieBruine is having so many problems while others are not. I suppose I could make a Lineage kernel with the stock keyboard driver to t
    6 points
  13. Hi all, I just updated to 20200831 by downloading the zip file from LOS website to my sdcard, and then applying the update via Recovery. This time around I tried opengapps 'aroma' flavour so I could tweak which google apps I really want. Turned out installing not much, and especially ommitting gboard so I could take advantage of LOS's AOSP keyboard (sticky Shift, SYM shortcut, etc.). So, if anyone is wondering whether they can use opengapps-aroma? IT WORKS. Oh, by the way. The Lineage stock apps seem to be cool. I ended up installing a minimal set o Gapps and feel good I did it
    6 points
  14. The device is rather busy for a couple minutes after boot. So the issue is probably load related (as I think we have all suspected for some time). I'm currently out of town, but I'll try to get you a debug kernel next week that shows what keys are being pressed and released. You can correlate that to your typing to see if the issue is in the kernel or in Android.
    6 points
  15. I've gotten the stock keyboard driver to work with Lineage, mostly. I was having an issue generating forward slash on QWERTY, but other FN combinations seem to work. And the any-key-to-wakeup feature is not there. But other than that it seems usable for a test. @DieBruine and whoever else is having keyboard issues, can you please try this? Make sure to backup your existing boot image so you can easily go back to it. http://files.nwwn.com/android/pro1/boot-stock-kbd-1.img I've put the code here just in case anyone wants to look: https://github
    5 points
  16. Alright I got the stock keyboard driver transplanted into the Lineage kernel and it builds. Now I just need to take care of the key mappings and make the FN key work like it does in Lineage. Hopefully I can get that done tomorrow.
    5 points
  17. @acrux a lot of us in here are not fluent in English, and that is fine. Please bear with us. I do hope you see the irony in that you fail using the quoting functionality correctly in your pointing out someone's error... 🙄
    5 points
  18. I can't speak for the solutions others have been using, but accidental presses have not been an issue for me using my Tasker profile for edge blocking. Not sure about the scroll bar issue. I never really use them, but after checking they're fine in my setup (small font, default element size), but problematic when element size is set to small. No case.
    5 points
  19. Hello, I must say, wifi and data connectivity feel better since I disabled NFC in my parameters. The phone was always lost when switching data/wifi networks. I saw always a problem with NFC (using #sudo dmesg), and I never used NFC. If it can help anyone...and thanks for the good work with LOS, there are some issues with ghostering keys who suddenly appears when typing, and keyboard who is lost sometimes when typing message (when I use Alt or Sym) but for my normal daily use it's ok.
    5 points
  20. I can not thank you guys enough for the work done. But the number of hours i bet you guys have used on this versus the price of the two devices would still leave room for quite some donations without anyone could reasonably consider you greedy...
    5 points
  21. I'll assume by September, you mean September 2020? This is a user to user forum, so unfortunately there are no answers here, only guesses,. The bad news is that they haven't yet managed to fulfill all the "pre-orders". They said something about another batch going out in early September, but we haven't had that confirmed, nor do we know how large a batch. The good news is, if they do succeed in fulfilling all the pre-orders, there probably isn't a huge number of new orders yet, so it really could be sooner rather than later. You'll really have to ask at [email protected] and se
    5 points
  22. I really wish FxTec was more communicative. It's super sad to see all the reading between the lines, guessing, and tossing information together because nobody is told what is actually happening or not. I'm not officially authorized to say anything about OTAs, but I will just say don't hold your breath for stock Q or R. But of course Lineage should have Q in probably a couple weeks and then R pretty much as soon as all the other devices.
    5 points
  23. I have removed and anonymised the account as per your request.
    5 points
  24. Agree, a lot of us seem to have forgotten how long it took the get used to a n900 and such alike. Yeah it was easier, but because we switched over from t9 which was even slower than touchscreens. At the beginning I also though I am using the touchscreen quite a lot. Now after 9 months, it is all fluid. I use the touchscreen to answer a quick 'yes' on a message, get a reply, switch open the keyboard, type in an answer. All done in a natural movement without thinking about it. The longer I use it, the more important the Keyboard gets
    5 points
  25. in my case, the update seems to have really fixed the issue related to the "Wifi signal lost => phone crashing". In the past days, I have switched off my second wifi access point and connected directly to the router only (to test). Previously the phone would crash within 30 seconds due to loss of wifi signal. in the past days, not a single crash (as they promised). What surprises me is that now the wifi signal reception on the phone is constant, even in the most remote room (without the second wifi access point). It seems that the signal reception has improved (or is it the weathe
    5 points
  26. Here is the debug kernel: http://files.nwwn.com/android/pro1/boot-keylog.img The file /sys/devices/soc/c17a000.i2c/i2c-6/6-0058/keylog records the last 256 key press/release events, one per line. The line format is: xxxxxxxx dK Where: xxxxxxxx is the time stamp in jiffies (1/100 sec), in hex. d is the direction, > for press, < for release. K is the key (without modifiers). It will only log the normal keys, not the gpio keys (shift, ctrl, alt, logo). You will need root access to read the file. I suggest an adb root session.
    5 points
  27. I don't think that the frame is the same since it looks so much different on Elephone U Pro. Pictures of Pro1: https://mobile.twitter.com/chenliangchen/status/1163524008471605249
    5 points
  28. Certainly the fingerprint reader works. Google Pay will not work by default. Other users you can make it work by using magisk hide. But I cannot help with that, I don't use magisk.
    4 points
  29. I still did not use the new display too much, but I feel I have a working Pro1 again. 🙂 I mostly notice the working of touch panel is smooth again, so I was not able to enter my unlock pattern while I saw the lines but now it is possible. My touch keyboard often used to be stuttering but now it is fluent as it was before. The display is shiny. Color temperature was greatly improved also with original display using stock display and latest firmware and I don't have a possibility of a side-by-side comparison but it seems to be relatively good also in lower brightness. So I don't real
    4 points
  30. So after almost three weeks, I can say that there is definitely an improvement. I have not had any random reboots at all, even at my work site (which was a known problem area)
    4 points
  31. I think, given current global conditions, waiting 10 weeks is not that bad. FxTec is still a start-up, at least that's how I see it. This is a niche product, hand assembled craftmenship 🤣. It still hurts, but I am anxiously waiting for my Pro1 to be returned 🥰 .
    4 points
  32. I got a tracking number and they apparently just replaced it. Looking forward to that delivery.
    4 points
  33. The majority (2/3) of Pro1 pre-orders were placed in the first few months of us accepting pre-orders. Those were the small percentage of people who are happy to pre-order a product and wait for it. The biggest rush was in the first few days, as that's when everyone was rushing to be amongst the first. Most people who want a Pro1 haven't placed an order because it doesn't ship tomorrow like most people are used to. That is a segment we haven't explored yet as we haven't really launched with readily available stock. In contrast to how much we have shipped, the remaining orders are very few.
    4 points
  34. To update from a test build to a signed official nightly, you first have to flash the boot image (in this case the one dated 20200914). Then you use this new official and signed recovery to sideload the signed nightly.
    4 points
  35. A big thank you to everyone for all the replies! What a welcoming community! With this information I have decided to place my order for a pro1 today, looking forward to being able to share my experiences with you all!
    4 points
  36. I'm with the majority here. Not that hard to adapt to, non-existent with Edge Null on Stock or with a setting on Lineage OS (which I am using). Unlike the majority, I don't like cases and will never have one. 😉
    4 points
  37. It matters what "display size" (and perhaps "font size"?) that has been selected too, if the elements are small, the scrollbar on the apps-list can get too narrow to activate. You can still swipe throuh the apps so not a huge thing in that app. But could be in other apps. But I think it is safe to categorise as a rare issue, that will affect few users only.
    4 points
  38. Oh sorry, I will put it up again soon. I would attach it here but max size is 2MB and the file is 9MB.
    4 points
  39. Not an issue for me either. Then again I've been using mostly curved edge devices for the last 4 or 5 years.
    4 points
  40. First of remedies for the issue exists. For the LineageOS it is build in, for stock Android a third party app. Disabling the touch sensitivity of the outermost pixels. Very few android apps use extra slim scrollbars, that works less than optimal when the outermost pixel are not active. To the question on how annoying the issue is, the answer is a little more complex. The first weeks I used the Pro1 it annoyed me while picking it up, slowly I adapted to handling it differently. Then I modified a Huawei P20 Pro flipcase for it, for protection. and since the problem has vanished completely.
    4 points
  41. Same here, they will send me a new display when they get new ones. Also they asked me to send them the old one for investigation. I hope they can get money back from their supplier as this really looks like a production fault.
    4 points
  42. I just today morning shot a video for Fxtec support about this issue, and they promised to send me a new display. Quite fast response from their side!
    4 points
  43. Apologies to the Eagles... It's Hotel Pro1, you can logout anytime you like but you can never leave. 😂 Seriously though, I have no idea. Perhaps PM an admin?
    4 points
  44. I Just received my order of the Snakehive flip case and pouch today. I only tried the pouch briefly, just to test for fit and I would say that after a bit of use, it'll be the perfect fit. It's a tight fit but not something that you're left struggling with to get out with two hands.
    4 points
  45. One thing I did differently is I go over the matrix twice, because my anti-ghosting is somewhat naive in that it gets confused if the state of the matrix changes during the scan (so i re-scan to be sure that's not possible). It's probably possible to do this in one go when you do the anti-ghosting better and I believe the way you approached it should work from reading the code, however I haven't tested it. So I don't think it's relevant but since we are possibly looking for a difference between the drivers i figured it's worth mentioning.
    4 points
  46. So ... last update: after applying some regular minor system update (58 megabytes) and a restart, the touchscreen started working again. It seems everything works now as expected, though it is weird I had to do something in order to be able to use "fastboot set_active a". Edit: locking it again (as it was supposed to be), worked, too. Why? Because in general I'd like to be able to use banking apps, that might not work otherwise. Thanks everyone for their efforts! Also: locking the phone erases the data.
    4 points
  47. Thanks, I ordered Querty because Quertz is out of stock 🙂 So I will ask the support. If I find the answer helpful I will add the information to this topic. Thank you!
    4 points
  48. By the way, I believe the relevant date for warranty is when it was shipped, not when it was ordered.
    4 points
  49. Currently sideload does not keep addons, so you must do the following: 1. sideload the new Lineage zip. 2. reboot recovery to switch slots. 3. sideload gapps and/or su. 4. reboot into android. This process takes about 5 minutes. OTA keeps addons, so just install and reboot. But since it is done in the background, it can take up to an hour or so.
    4 points
  50. I got trough the support instructions, i'm not new to the ADB, root, flashing and custom things but those instruction wasn't an easy one BUT! it all ended with a complete working touch screen without replacing it again so i'm pretty happy with all this thanks
    3 points
×
×
  • Create New...

Important Information

Terms