Jump to content

pebert

Members
  • Content Count

    83
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by pebert

  1. Thanks I will give this a try tomorrow.
  2. How do I preform a adb sideload on that? Or do you mean fastboot?
  3. Where do I find the latest software? And why is the OTA endpoint no longer responding? Is fxtec out of business?
  4. Oh, yes, EDL i mean. Pretty close though, M is only one step away from L. The software I used is dated 2020-07-07 on this page http://files.nwwn.com/android/pro1/factory.html I did a check for a OTA system update, but there where none. Isn't that a bit strange?
  5. Fastboot flashing procedure went flawless under win10. Unfortunately the phone got stuck in a boot loop, changed the active slot, but still didn't boot. Did a EDM flash instead, so now the phone boots up as it should on stock software. The reason for flashing my phone was the fix the issue with the touch unresponsive margins on the sides, but this time it didn't work, so I still have that behavior. Any idea why?
  6. Fastboot flashing procedure went flawless under win10. Unfortunately the phone got stuck in a boot loop, changed the active slot, but still didn't boot. Did a EDM flash instead, so now the phone boots up as it should on stock software.
  7. Interesting reading, Maybe the easiest way is to boot from my previous harddrive with windows 10 then.
  8. That's so Microsoft, I guess a Windows phone doesn't have any issues. Will give it a try from my Linux machine instead, even though I'm sceptical that it will work, I'm running a Dell enterprise server, and that USB implementation/driver is a little bit "one of a kind" //Per
  9. I have encountered an issue, my phone won't stay on fastboot mode, as soon as I send the first fastboot command (regardless if it's a "fastboot devices" or any other command the phone exits fastboot, shows the fxtec logo together with a small text in the upper left corner telling me that the any key will preform a reboot. Just pushing one of the volume buttona it reboots back to LOS. Any ideas on this?
  10. Å A Long Time Ago, in a Galaxy Far, Far Away... It is a period of civil war. Rebels seem to have issues with their phones, the display have a tendency to crack , flashing from a hidden base haven't won their fvictory against the evil unresponsive edges. So, as already stated above also I can confirm that the app for flashing the display doesn't work anymore from the newer LOS versions. Other issue I encountered is that my phone won't stay on fastboot mode, as soon as I send the first fastboot command (regardless if it's a "fastboot devices" or any other command t
  11. Yhe WAF is a important part. According to a study made by Consumer Electronics Association (CEA) the wife is controlling 88% of the electronic purchases, either directly by buying it herself or, as in the majority of the cases, indirectly by "mind fucking", black mailing or in other manners manipulatibg and controlling her husband.
  12. I think that is a really important well choosen decision they made. 1. The first, most obvious reason, is what already been compiled here, something needs to bring money in to the company for financing the RnD. 2. I believe it's a strategically wise decision to implement other kind of products to the company portfolio. The brand will be more known and when you are operating in different business areas you are not so sensible for ups'n downs in the market. 3. LoRaWAN is really a hot topic right now, its a technology the really grows on the market. It's a technology mainly (if
  13. Hi I´m still struggling a bit with this, How do I find the scan codes for the "F" and "arrow up" buttons? the Key-loggers or dmesg don´t show anything. Running LinageOS18.1 also when I look at the original keychars file I don´t find symbols related to the "arrow up" button, (for example I don´t see anything about "/" being associated to "P" //Per
  14. I trying to understand how this works. My intention is to merge the LinageOS stock Key Character map with the pro1_qwerty_swe_1.kcm from finqwerty. the stock map file has type ALPHA while finqwerty has type OVERLAY, what does this mean? Do I need to merge the two files together, meaning replace the entries in the stock file with those from finqwerty? Or can I load the two files after each other? Do I need to edit anything in the key layout file? finqwerty also has the following entries: # orig FORWARD_DEL map key 111 PLUS
  15. Is this still an issue? And in that case, what is the issue? Running lineage-18.1-20210726-nightly-pro1-signed.zip and just copied /vendor/usr/keychars/Builtin_Keyboard.kcm to /data/system/devices/keychars/Vendor_181d_Product_5018.kcm Changed letter "A" to "P" as a test and it works flawless
  16. After installing LineageOS 16 and then back to 18.1 together wit nikgapps core it works like a charm.
  17. can someone help me setting up the development environment for building lineage OS for Pro1?
  18. I have installed both lineage-18.1-20210614-nightly-pro1-signed and lineage-18.1-20210712-nightly-pro1-signed both of them acting strange, when I try to make a phone call, the dialer app doesn´t go into the call active mode, but stays as it was before pressing the green handset. nothing in the status bar show an active call either, so only way the end the call is to power off the phone. then Some Microsoft Office 365 apps won´t start, like Onedrive and excel, but Teams and sharepoint works fine. this issue was seen on the 20210614 build, stayed when doing an OTA upg
  19. it was laying in the middle of the highway for ~30 minutes before I managed to pick it up.
  20. Even in a reply there is a limit on maximum 2MB in total, which is a bit low in order to get any decent photos. So,even tough I reduced the size by 50% I need to post photos one by one.
  21. You can have the main board, just pay the shipping. Will take some photos.
  22. Wasn't think to do, do you want to have anything of it? I will keep the keyboard and sliding mechanism to do som experimenting on, try to make custom keys, and fix the play in the hinges
  23. Did some tests of my device last weekend. There has been quite much skepticism however the construction of the sliding mechanism is robust enough. Hypothesis During severe mechanical impact the sliding mechanism will take the most damage. Method Put the device on the roof of an automobile and drive 3km on the highway in 100km/h Result Everything broke except sliding mechanism and the keyboard. Reflection It is not recommended to transport your device on the roof of your car. The sliding mechanism of the F(x)tec Pro1 is a strong an
×
×
  • Create New...

Important Information

Terms