Jump to content

VaZso

Members
  • Content Count

    1,633
  • Joined

  • Last visited

  • Days Won

    105

Everything posted by VaZso

  1. VaZso

    Spare Parts

    As @EskeRahn wrote, replacement display is available on Aliexpress. However, you have to separate original display from the frame and glue the new one in. So you may need some tools like "guitar picker", but it seems it usually comes together with these replacement screens. I have changed my screen a few months ago as my original screen started to get spontaneous touch actions. However, yesterday I had to replace my replaced screen again as it has started to has problems which initially seemed to be "solved" by turning the screen off/on again, but yesterday it became completely dead
  2. I think nobody told it is the case. I don't know the progress of stock Android 10, but LineageOS does provide it anyway and I don't think they stop supporting it in the near future. I don't think it is hard to continue supporting Pro1 while there is official support... so later Android support is a bigger question... What is worse, it seemed to be some effort of FOSS community supporting SDM835 more deeply which will not happen because of this step of Snapdragon. ...and trust me, it will also happen with this model in a few (maybe two, maybe three) years. One of the reasons
  3. You are right, the biggest question is if they have enough spare PCB for repair purposes. Anyway, they may have some replaced mainboards which has clear faults like the broken UFS flash chip which may be repaired by replacing these chips if they find a company who has appropriate tools for it. So even if they currently don't have working motherboard, they may be able to repair some if they did not do it yet.
  4. It would definitively need lot more money. One thing is the complete antenna redesign, testing and related certification which they wrote in the update, and another one is the difference between an SoC with similar functions and pinout which is much easier to apply even if it has slight differences or modified package and a completely differerent SoC which would need a more complex modification of the PCB or even almost a complete redesign. So the latter case is much complicated and takes much more time of design and testing.
  5. ...and the best is that they are still able to make modifications on hardware if necessary. ...and it should also include certifications, Google-related payments which also require additional money.
  6. I am sure it is not a complete restart from scratch as at this time, other components are seem to be unchanged. The keyboard for example is an already developed part. I think a lot of support for the new SoC are already in the kernel but it does not mean all parts of development are already done, also testing should be done. ...but a lot of development related to keyboard and landscape functions, curved screen part, etc. are already in LineageOS and should remain there... If something has to be changed, it should not be in high level in this relation.
  7. The timeframe is believable and decision is right for being relatively fast. Re-certifications will be needed anyway. Performance loss is really an unfortunate thing, but I don't feel I need high amount of Pro1 existing performance, so it may be also enough... However, camera resolution may also gain some positive change compared to original Pro1. Also, Covid situation may be better as vaccination increases, so I hope it will not delay Pro1-X further.
  8. I think some clarity has been arrived in a form of update at Indiegogo campaign a few minutes ago. Not an easy problem anyway and that is the biggest problem in the tech industry in general. It is moving fastly and long-term availability is not a main goal for chip manufacturers.
  9. We don't know what they have found, but it is clearly display-related problem - most probably a display fault, but I may think also a small possibility which may be fixing related... ...but it is clearly not related to other components and I don't think it is a design failure.
  10. Maybe it is hard to learn during an unpredictably moving industry (as a result of COVID and lockdowns and maybe also uncertain supply channels)... Manufacturing partners may also be overoptimistic. I am just guessing, but these may be also real problems.
  11. Just to clarify even further, they promised we (who applied the voucher based on Keyboard Mod) will have priority in receiving the phone which was mostly happened.
  12. Just for clarity, instead of refund, another option was to get some discount later on a phone they just started to develop. Initially, they have called it Q-Device (which name was subject to change later) and they have received a lot of critics on Keyboard Mod Indiegogo site and also at maemo forum. A lot of users were in doubt they will ever able release a phone. So a lot of users went for a refund instead, which they have received. As of others, they were waiting for Q-Device which became F(x)tec Pro1. So that is the connection with Pro1 here. 🙂 As of Moto Z, that was an i
  13. That is why I have bought a charger which has two USB connectors: - One for Quick Charge compatibility - Another one which only supports 5V 1A I use the latter to charge my phone and it can charge it in a reasonably fast rate which allows me to plug it to charger for evening and have it charged in the morning (after a few hours it is done). The other port still makes possible to use fast charging when I may need it (if the phone is depleted in the morning as I may have not connected it in time). Also, I have a QC compatible charger in my car in case of "emergency", so I may cha
  14. Yes, it has twon SIMs. ...or it may have one SD-Card and one SIM. @claude0001wanted to say if there is enough space on internal storage, there may no need of using an SD-Card, so there is a possibility of using both SIM slots.
  15. Without deeper knowledge of the specific chip, it is hard to tell it. ...even that if the sensor chip provides jpg data, however, I doubt it.
  16. I think the app processes the image in a way it represents the orientation of the sensor placed in the original phone it was written for. It may depend on the sensor communication if it is possible to get image data accordingly. However, I don't think basically it is ideal to have real orientation rotated, although it is possible. So image data may be available from the sensor which could be handled natively if the program is prepared for the specific placement of the sensor...
  17. It also works well for video. Night mode also works but viewfinder is not good in that mode. Anyway, one problem of the photos taken is they are rotated by 180°... Android rotates is back on viewing but the file itself is in wrong orientation which can be corrected easily.
  18. I don't know where I have downloaded it from, but if everything are right, the current mod I use is called F1v9.6_6.2.030.apk (at least I have it downloaded). Also this website looks familiar to me, I may have been downloaded it from that website. This is working fine for me on stock Android 9, however, if I remember well, v10 version was made for Android 10, so under a newer OS, that may be the appropriate one. (I also have F1v10.3_7.0.009.apk downloaded, but as far as I remember well, that did not work as it was needed newer OS.)
  19. I have heard a lot of surprise also apply to UK residents when they notice the TAX / VAT and additional customs handling fee. So it is a two-way problem...
  20. That is "Poco F1" using stock Android. I have heard about focusing problems under Lineage OS (which is I think much closer to AICP than stock Android of Pro1) but I don't know if it also affects GCam ports - it works well under stock OS.
  21. I have used to take relatively good photos using my N900 but its time was over. It had good lens, great focus, but relatively low resolution compared to today's phones (5 MP) and relatively noisy photos in darker environment. In its time (when it was manufactured), it was a really great device including its sensor equipped with Carl Zeiss optics. I did not like the photos created by a lot of later Android phones anyway as often focus was not very good and aggressive noise filtering (like digitally smoothing then sharpening the image) caused a lot of loss in details - that is how I saw
  22. I don't think these are bad photos and I did not have much attention on their quality... All of them was taken indoors with not really high amount of light.
  23. This is my 70mai A800 when I had to disassemble it because of power button problem.
×
×
  • Create New...

Important Information

Terms