Jump to content

VaZso

Members
  • Content Count

    1,633
  • Joined

  • Last visited

  • Days Won

    105

Everything posted by VaZso

  1. VaZso

    Spare Parts

    Thank you for sharing the photo. So the whiter part of the bottom appeared later if I understood well. I hope F(x)tec will help somehow or in worst case scenario, another screen from Ebay will help. However, luckily you are able to use the phone while waiting for a replacement screen. Anyway, the replacement should be done by someone who is familiar with electronics to not cause damage in the phone itself. The repairability should be good according to what they said earlier.
  2. For me, I think a portrait holder is good for a car. The keyboard may not be opened even with horizontal holder, but more importantly, I think navigation is much better in portrait mode... at least with the programs I tried, portrait mode was more informative about the road and the way itself.
  3. Just a question - which is that project?
  4. VaZso

    Spare Parts

    At first, I would contact F(x)tec directly and ask them what is their suggestion. Maybe you may also order a replacement screen from them. Anyway, how did your screen break - what happened? Just curious what circumstances were lead to it - maybe to learn what not to do, etc Have you used a screen protector? If so, what kind of it? Anyway, if I somehow could not get help from F(x)tec, I would buy the mentioned screen for Elephone U Pro and replace it, but first I would ask what F(x)tec says.
  5. Not really if the layout is QWERTY so despite of where Z and Y are printed, you may still use QWERTY positions. However, I dislike the shifted QWERTY keyboard and that was the only reason of choosing the QWERTZ variant.
  6. As far as I know, they handle all orders prior general availability as pre-orders (somebody of them wrote it somewhere). ...so you should also receive your order before general availability, but your order is somewhere near the end of the queue.
  7. I have ordered another Pro1 from DragonBox Shop to be able to set it up prior back to work for busy weeks while I keep my pre-order with IGG coupon to be able to test some things or other systems (I would like to have a working Sailfish OS). ...but FedEx has sucked me today by waiting the whole day for them to arrive but it seems the deliverer did not want to even work on the last day before Christmas which causes me another 7 days of waiting because of FedEx "service". As I see anyway delivery is a bit slow and communication is not really good but they are working hard on it and slo
  8. I have not received tracking number or stock assigned message for my pre-order with IGG coupon yet, but I have also ordered a Pro1 from DragonBox Shop because I wanted to set it up during the Holiday season and my January and February will be extremely busy. So everything seemed to be on its way. FedEx received the package and showed expected delivery by the end of 23rd. On the morning of 23rd (around 2 am) I have received an e-mail about "Delivery scheduled for today". Tracking showed the last city as the capital city of my country and that my package is in the vehicle for delivery t
  9. Yes, it may be the reason. However, I would have been much happier if I read that in one of their update e-mails / messages. I understand that there is not always worth to share some information with wide public but if something strange will definitively happen then some prior information may help to understand the situation. Also, they may be some earlier IGG backers but most likely their partners who have contracts with them. ...and as of this, they may loose much more money based on a clause of their contract or a possibility of loosing a partner may have higher impact on sold
  10. I have just ordered a Pro1 at Dragonbox. Despite I am an IGG backer, I see no chance of receiving my Pro1 prior Christmas and almost no chance to receive it between Christmas and the new year. (I gave relatively high chance for the stock to disappear as I ate my dinner and waited a bit, but availability was still there and temptation was extremely high.) As I will not work from this Friday to the second week in January, I will definitively have much more time spending with Pro1 (so moving to it) than in January which is the expected arrival of my Pro1 pre-order and also January (an
  11. I think this specific issue is a bug and not an expected behaviour. Backlight timeout setting is a good feature request anyway.
  12. I agree. However, if I would worry about loosing this option, I would contact F(x)tec to ask for an option to initiate a refund then pay it again - so practically the payment will have extended protection and the order remain exists. I don't know if that is possible (it also takes effort at f(x)tec's side), but it may worth a try.
  13. @Erik I would like to ask the state of batch 3 - has it arrived to UK or batch 3 was not shipped but going to ship devices directly from China even for those who were supposed to be in batch 3?
  14. Which I don't understand is the third batch had to be already sent to UK warehouse and they told us stock assignment e-mails will arrive soon. Now, if I understand well, they will also ship these devices directly from China to EU. So, does mentioned third batch exists or parctically no shipments happened since the last e-mail mentioning the light leak issue? In other words, is there any chance for Pro1 to arrive this year for those who still not received stock assignment e-mails yet? However, I think no - and last deadline is end of January...
  15. For me, here it is: - Oder date : 2.4.2019 at 9:02 pm UTC +2 (April) - Order number: 116xx - IGG coupon: Yes - Model: QWERTZ - Location: EU (Hungary) - Payment request mail: 1.8.2019 09.56 am UTC +2 (August) - Day of Payment: 1.8.2019 09.58 am UTC +2 (August) - Stock assigned mail : No - Tracking number : No - Phone received : No
  16. You left out "IGG coupon applied" as it is also a factor anyway... theoretically...
  17. VaZso

    A few odd issues

    Yes, I think it is unrelated. I think it is maybe an other cable coming from the keyboard, that is why I think some of the keys may not functional if it is going at the same ribbon cable - but it depends on the actual solution.
  18. VaZso

    A few odd issues

    As the USB port is on another board, its connector may be loose somehow... but it sound strange how it is related to keyboard backlight - maybe it is also loose a bit but that case I would assume not all keys are working...
  19. VaZso

    A few odd issues

    I don't know how it looks like inside, but maybe some cable(s) slipped out (maybe partly) inside - or worse, a connector may have been felt off partly. I would contact F(x)tec directly and ask them what is their suggestion and if they could help find out what can be the cause of your problem. Maybe warranty covers it or at least they have other suggestion - a service may be able to repair it if you (as most of the users) not have the appropriate skills to open/work on such a device. Suggestion: do not open the device if you are not familiar with electronics and definitively not ope
  20. If a non-shifted US layout was existed when I have ordered my device, then I would picked that instead of QWERTZ.
  21. I think your quote is wrong. 🙂
  22. Just avoid the Chinese counterfeit products of products of China. 🙂 (So it is another technological level when lower quality Chinese counterfeits arriving of Chinese products which have high quality.)
  23. The resolution and color depth mainly depends on the amount of available video RAM - so 1024x768 at 24 bit requires 1024*768*3=2359296 bytes (2.25 Mbyte) of available video RAM while 1600x1200 at 16 bit requires 3.66 MB of video RAM. "Modern" monitors had "VESA DDC" capability and current monitors also have similar (improved) communication. In modern, I mean maybe the middle of 1990's. Earlier monitors had no communication so no way to determine if they are able to use a specific resolution and refresh rate. Vodoo is a relatively new thing, I don't think a lot of DOS games used i
  24. I see. TheKit wrote it seems the kernel driver was written that way but the reason is unknown - so it may happen to be better later. Edit: So currently it should have similar behaviour also under Sailfish.
×
×
  • Create New...

Important Information

Terms