Jump to content

VaZso

Members
  • Content Count

    675
  • Joined

  • Last visited

  • Days Won

    8

Everything posted by VaZso

  1. That is also my hope as it is the closest successor of Maemo which may also have Android app support.
  2. Right, that is what I did so far when I wanted to reach my files. However, I usually ended up using a more convenient and faster solution (I mean without using MTP).
  3. Thank you. Unfortunately, it was written in C#, so there is no much chance to be compiled to run under Linux. However, maybe also MTP/PTP handling would be also different otherwise. ...but it should be a useful program for Windows.
  4. For me, an up-to-date Maemo with Android app support...
  5. Right, FinQwerty is mandatory for proper using of international layouts. Interesting... it seems I use both of them as small. ...maybe that was why I was wondering one of the web pages I often visit loads in a mobile-like outfit (it is a Drupal system which moves sidebars to the bottom if resolution is below 1024 pixels). However, it seems logical resolution is still below this value. I have tried this application and it looks good, but I had problems with my keyboard when it was installed (slower appearing of characters and unintended repeat of characters). Maybe it is better with the improved keyboard driver now, but I had a feeling it was not designed to handle a lot of buttons what Pro1 has. So I don't want to say not to use it as its features are valuable, just to say if you experiencing problems, you may try to remove it to see if that helps. I use the same port and it makes really good photos using Pro1.
  6. Yes. I use "Poco F1" port anyway. I think not all versions were compatible with Android 9.
  7. Thank you your detailed reply. Apart from these symptoms, when the phone starts properly, I don't feel any defects. Phone calls come up delayed but the phone works well otherwise. I will try the bugreport / logcat but I am happy it is currently working and I am afraid if I restart it, then I may not be able to boot it up again. Also, I am currently a bit busy and it is my daily driver, so if it becomes unbootable, that is a really bad situation for me. Maybe when my other Pro1 comes back from RMA, then I can start to experiment a bit more and find out what is the cause of my current problem. However, I really hope it is a software fault (be it anything) and not hardware as the latter is much more complicated to repair. Thank you, I will try it. My first idea was the same, but I may do a factory reset later, so when I receive my other Pro1... Does it mean by adb backup, I can backup my applications and their settings? The other one is the storage I also see in a file manager I think. So if I can backup / restore my phone this way then I would feel a bit better about experimenting... Anyway, 32,53 GB occupied on my internal flash, so I have about 75% free space remaining (everything else are on my SD Card). Yes, I keep my eyes on LineageOS thread and I think that system is already much more usable than stock one, so it seems to be a better choice for long-term use. Also a proper backup/restore (TWRP if I am right) will be a very good reason to use LineageOS. Moreover, it looks to become official really soon which means a good choice also for a daily driver. Anyway, behind my idea of having another Pro1 was primarily a backup phone, but also a phone for testing other systems like LineageOS and Sailfish. I was really hoping for a fully supported version of Sailfish OS as I come from Linux and I still know why I liked Maemo so much but LineageOS seems to be the best option of Android and also Pro1 support seems to be in a very good state thanks to you. So my idea of testing became a bit striked out as I did not want to worn a device which I knew I have to send back for RMA (not even tested the device itself anyway).
  8. Hi, I have a Pro1 since late December. I like it, I like the keyboard, it does not rattle more than it should and I have no problems with the screen apart of an always-on, but hardly noticeable pixel. However, since a while, I have noticed if I restart it, the starting of the system is hard (it is the stock Android). If I start using it, it complains about "system" is not responding, lock screen does not come up after unlocked, restart / shutdown does not work and not all applications are available... but it goes black after maybe a minute, then it restarts (it does not asks for PIN again anyway). For example, my default software keyboard (Hacker's keyboard) is also unavailable, another one comes up instead. On my home screen, charge signal is 100% instead of real value, clock is not present on my home screen and SD card is not available. I have also noticed if I turn the phone on, I enter PIN, then leave it alone for a while, it starts normally. Also I have noticed maybe near the time when it started to do this on restart, that when someone calls me, it starts to ring, but often it takes 3-5(!) rings for the display to turn on - so I just looking at the phone and waiting for appear who is calling me. If I press power button, ringing stops, display comes up, I can unlock the phone but I don't see the incoming call. Instead, it appears later in status bar or simply a notice appears of a missed call. Today, my fingerprint reader stopped working again (hardware is unreachable), so I restarted my phone. After entered PIN, I left it alone for a while. Later, I see the phone is still starting (phone no service --> service change), still my background screen is not built up (charge signal is 100% instead of real value and clock is still absent). After a while, screen goes black, then it restarts. It even does the same if I connect it to a charger. I had five photos still not synchronized and my SD card was also unavailable, so I wanted to enable WLAN and copy these files to local network before automatic restart, while the phone is still alive. However, it did not remember the passphrase. I have entered a passphrase of my test network, then it complained about unable to save it... then I have synchroniced them through mobile network and my e-mail client before it restarted again. I have also tried forced power off by long-pressing power button. It requests PIN, then it does the same loop also if I don't touch it. Then I have connected it again to charger and did not enter PIN and waited. After a while, I have noticed it still waits for entering PIN, so I have entered it and waited again. Later, I see the phone started and everything seem to work. So, here come my questions... What the ...strange thing my Pro1 or my stock system does on restarts? I don't know what to think... may the flash (UFS) slow or becomes unreachable at that time? Do I have too many applications starting at the same time? Do I have too many applications subscribed to an event? How could I find out the bottleneck? If it would be a Linux or if I had root account, I may have more informations, maybe some io stats or process / load information would help, but Android basically is still a restricted system. So I currently don't know if it is a hardware or software issue and as Android does not have a proper backup/restore solution, I don't even able to test it without a lot of time setting it up again. Also, my other Pro1 is still at F(x)tec since about two and a half weeks because it had excessive rattling and a crack on its display frame like if it had some issues in the factory - so I am also afraid if I start to reset / reinstall system, I may end up a non-working Pro1, so I have to use a keyboardless phone. @tdm, does Android have something like a watchdog which ensures the system started properly and does something like a restart if a mandatory component is unreachable? I wrote this post using my Pro1 anyway. Any suggestions?
  9. It may happen the system they use thought your message is spam with higher chance if you use your own (or corporate) domain which does not have proper SPF / DKIM records set. Maybe try to contact them using their web form.
  10. This is a Lesser stag-beetle taken with my Pro1 on Saturday. I have cropped the photo. So it is the small variant of stag-beetle, maybe around 1.5-2 cm only.
  11. Thank you, now I think I have found it. ...however, "thankfully" they have translated it and I have two "Vezeték nélküli frissítés" apps. One with blue background and an Android-like logo and another one which have an arrow facing down... it would be good to know what it is as it looks strange anyway.
  12. Is it part of the stock launcher?
  13. Could you please tell me more about this "Ellipsis"? I have also noticed this sign...
  14. Please write in English here, generally we don't understand Czech language only by Google Translate... Anyway, I think you bought a QWERTZ device and selected Czech language. The basic keyboard of Pro1 is QWERTY which is shifted and that is why the shifted layout you experience. Download FinQwerty which also has Czech layout for QWERTZ version of Pro1 and set it as your layout. It is not an active program but it registers appropriate files and it will work the way as any stock layouts. So FinQwerty is what you need.
  15. Do you mean the settings of "Auto check when connected to" ...wifi/etc, check interval, auto download, SD card update, etc? Those settings still working for me (at least I can reach them).
  16. Maybe they already know something - I also hope pre-ordered customers will also have a surprise soon (I know nothing anyway).
  17. I think there was a fix in the update which broke safetynet then was reverted, so it should be included in this release. If I recall well it was an improvement in keyboard driver which allows of pressing more buttons at once.
  18. Maybe the most important part was the security update itself but I hope they will also work on bugfixes.
  19. My Pro1 also displays this new firmware (I am currently on the update which was available for a short time and had safetynet lost, so it may be the more complicated part of the upgrade arriving). It wants to download 265MB of data and has 20200620223710 in its name. I will install it later (maybe late afternoon / early evening). Edit: Security patch is 2020 April
  20. If the charger is not really good (maybe noisy) it can happen. I have also experienced it with older phones and not really good charger.
  21. That is why I have removed it immediately from my daily driver as I saw in this forum that it worn quickly. I put it to my F(x)tec greeting card card in the box. ...then I put a durable foil on the back of the phone... 🙂 Also, I cut a P20 back case and my phone sits in that since then and it also has a foil on the screen. 🙂 I hope they will protect the phone when it is necessary.
  22. I am really sad it was not a successful story for you but I think you will sell it easily. Maybe it would help if you provide your country or approximate place of the globe near you (continent, etc). Anyway, for me, it is easy to operate the slider even without noise, but I don't know exactly what disorder you have. It is also true for your touch screen problem - if it is the edge touching, you can make it better using a software. If it is too sensitive for you (causing problem to touch something when your finger is close to the display but not touching it yet) that is another question which may be solved in software or not (I don't know).
  23. Here is a teardown made by a forum member here. Also, if you contact F(x)tec, then they can provide a service document to do this replacement.
  24. It may happen the screen has quality problems but it may most likely reveal in a few weeks or a few months. However, I hope it is only a minority and it is most likely not happen later on. Anyway, my phone is almost seven months old so I really hope its display will remain working... Also, if it would be a common issue, this forum would be full of this problem - I hope replacing the screen will resolve this issue permanently.
×
×
  • Create New...

Important Information

Terms