Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 08/29/2022 in all areas

  1. Updated the first post with warnings regarding the restore of backups. Sadly, i could not identify a pattern in which case restoring a backup works reliably. Even after days of trying and countless reflashes/lock/unlock BL... I managed to put a device in the perilous state where a restored backup with contained keys does not make those usable in Android. And was not able to recover from that state by any means. I documented the way i reached that. But the unsettling thing is, i did nothing different than during the successful restores. Until someone else with deeper knowledge solves t
    4 points
  2. aw9523b: key press: key_nr=38 keycode=0012 ff=0000 gpm=0000 glm=0000 aw9523b_irq_work: enter polling mode: p0_mask=ff aw9523b: key release: key_nr=38 keycode=0012 gpm=0000 glm=0000 aw9523b_poll_work: enter irq mode aw9523b_irq_handler: enter If I understand correctly, the process with the aw9523 chip is so : 1-key press, 2-enter polling mod, (the CPU repeatedly asks the keyboard for it's state) 3-key release 4-enter interrupt mod after polling 5-send an interrupt to the CPU via i2c When
    3 points
  3. Very interesting to see progress on this topic, especially on system level. A quick feedback on my progress so far: uninstalling a couple of apps (although rarely used) and killing background processes improved the problem. Next step is limiting background processes to 4. I don't totally know what this does, but maybe it reduces background activities.
    2 points
  4. It is highly advised to take a backup of your device specific partitions right after you receive the device. Update 20220829: tl:dr: Community has not found a safe way to restore backups as of yet. Making below described backups is still highly advised for a future where some wizard found a reliable way to restore those backups. For now, if you have broken sensors from flashing another OS, the restorecon method described in the "Repair sensors/ folder..." section does 100% work to fix those while retaining your attestation keys. While restoring any backup has a high chance to make the keys
    1 point
  5. Interesting indeed, but what's puzzling to me is how much the OS is managing charging nowadays... I feel it should be less, but huh... progress I guess...
    1 point
  6. Interesting, thanks I hadn't realised that such a bug would be an Android wide problem. I was on Android 9 before this. It's crazy that such a major issue hasn't been fixed by Android yet. Did have me worried that I'd have to part with my new phone if I couldn't rely on it charging but it seems that others are also affected.
    1 point
  7. Thanks, this option disappear when using mozilla with the phone. Had to use "computer version" button
    1 point
  8. I'm not sure why having VoLTE would create problems with calls (and I mean that, I am not super knowledgable so I literally don't know) , but when you said you couldn't disable VoLTE, were You talking about in Android settings or using the phone menu (*#*#4636#*#*)? Mint, like so many MNVOs now is a T-Mobile MNVO. I wonder if in your area T-Moble is relying more on a couple of the bands they've acquired that the Pro 1/ 1x don't have (e.g., band 71).
    1 point
  9. I also managed to install Waydroid now. By installing the Aurora Store, most Google Play apps I used before also run well. But if an application uses the built-in Android browser for authentification issues, the browser just shows an error page that a proprietary app-specific URL scheme isn't supported. A possible workaround is to deactivate the built-in Android browser in the Android system settings and to install Microsoft Edge from the Aurora store. If the apps use Edge for online authentifications, it works. Google Chrome isn't installable due to a missing library. My other exper
    1 point
  10. I decided to make my own case as a learning experience. So far it's just the base as I wanted something to replace the plastic holder in my Snakehive case. I have not included the hole for the headphones as it would leave a gap in the upper edge of the case and reduced it's grip on the phone. I will upload the STL's onto Printables when they're ready. I'm still tweaking small measurements atm. pro1_case.mp4
    1 point
  11. I tossed my SIM card from my Pixel 2 XL into the pro1-x when it came in to check it out. I live in the midwest, near a rural city (30k or so). Verizon, last I checked, is the only thing that mostly works at my house (depending on where you are it might not even work). Anyways, the por1-x worked as well or better. I tested SMS with the default app, made and received calls (speaker, mic, and bluetooth) which all worked fine. Since I am not ready to make this my daily driver I toss the SIM back into the Pixel 2XL. I did not enable WiFi calling as I wanted to tested the cell network.
    1 point
  12. I got sound working in LXC! I will now try to make that work in the default install and then the app shouldn't be far from hitting the Chum repo for easy installation, but it'll be some work to automate that.
    1 point
  13. Sorry, but based on an n=2, that's flatly false. First time I sent mine in, one month, second time was 6 months because they didn't have parts, but they were clear about that when I sent it in and I had it back 3 weeks after parts became available. They probably, as said, can supply the battery, but given it is a new phone under warranty and the exact nature of the problem hasn't been established, myself, I would send it in. They will tell you what to expect when you work out the trouble ticket with them before sending it in.
    1 point
  14. Problem is, until now, the battery cannot be found anywhere but at Fxtec. Might actually be a unique design for them. On the other hand, I'd at least expect Fxtec to be able to ship batteries some time soon.
    1 point
  15. Agree with this, I tryied this possibility but even with heavy load or quite no load it works with same behaviour. It could be relative long time without issue, and sometimes it's quite useless. AFAIK a hard reboot don't really affect this. strange...
    1 point
  16. @raymo That's good to know. I had many keyboard issues with double inputs in the past and ghost writing (i.e. thi1es instead of this) in the past. Since pressing hard also means writing slowly, it could be an software issue too. I'll try to uninstall some apps and free up some ram, maybe it does help. If not, the system will get reinstalled in a few weeks anyways, I'll tell you if it helped.
    1 point
  17. I have used min four three years now, and a few keys are becoming 'unstable', that is 0, 1 or 2 characters when pressed. As the device is going to be retired as a test/backup device, it is not a huge issue for me, hopping to get my Pro1X soon. If we can get it as a spare part it should not be that hard to swap, with the help of some heat. Try taking contact with support.
    1 point
  18. I just added the microG repository to F-Droid with no problem at all. Seemed to work identically to native Android.
    1 point
  19. I just tested and on my Pixel 2XL (LinageOS 18.1) I do not get anything from the finger print scanner when it's not being requested, so I am thinking this is a change they could make in software/firmware...or wait until LinageOS comes to the phone.
    1 point
  20. I tried out Adam's latest kernel tonight, and I'm glad to report that although I still can't get the more recent UT kernels to boot, Adam's does boot, and also I've got Waydroid up and running just fine. Whether or not it's in a usable state is a different question of course. 🙂
    1 point
  21. @fxnoma Like Kabouik mentioned, Android sync apps will not work since the SailfishOS android layers do not support to relay bluetooth to the system. On the native sync client side we have Adams Amazfish, originally written to support Amazfit products. But adam maded it nicely modular and now the PineTime and bangle.js are supported as well. https://github.com/piggz/harbour-amazfish Then there is rockpool, providing support for all pebbles. I used that on the Pro¹ for some time. You might have heard of AsteroidOS, a full linux replacement to WearOS on 19 supported watches. The pitty, tho
    1 point
  22. What is the current status of SFOS on Pro-1[X]? Last time I used it (Jolla) even copy&paste was barely existing. Smartwatches that needed Android apps also did not work, as Android apps did have access to internet, but could not use bluetooth. Any updates on that front?
    1 point
  23. You are welcome, for details see this.
    1 point
  24. @mosen Oddly, this did fix the sensors, but not attestation. I feel quite certain it was working when I backed up the image, but unfortunately I dont have time to try re-flashing again this afternoon.
    1 point
  25. I've had my Pro1X since Aug 1, and noticed today that the fingerprint scanner had separated from the case. It still works; the electrical connection is on the other end of it. I've taped it down with a bit of electrical tape for now. What's the best way to stick it down permanently? Should I disable it until it's been fixed? I don't use it anyway.
    0 points
  26. After using my used Pro1 for over half a year I am getting my first hardware issues. The first keys start to not work when pressed normally, I have to press them quite hard to get the key. It started with the 'c' but I now have four or five keys that often do not get registered when pressed. The 'f' and 'c' being the most obvious keys. Is there any kind of replacement or fix for hardware keyboard issues? Also, am I the first one encountering this problem? I haven't found any post in the forum about this (or I failed at searching).
    0 points
  27. I went into that setting and everything is greyed out and I'm unable to switch it on or off. If that's the setting that means the sim card from mint only uses VoLTE settings? Sorry im not tech savvy with phones. Maybe my phone has an connectivity issue or that's how fx pro 1x are at the moment
    0 points
  28. My Pro1 has problems with the "a" and "d" buttons. It doesn't feel quite like a hardware issue. More like the software sometimes swallow a character. Whenever I see an "a" or "d" missing, pressing either of these two buttons very lightly works the second time. I don't see anything suspicious in the logcat either. This might be the last straw for me and I am thinking about retiring my Pro1 ... with a sledge hammer. Yes, I am that disappointed! With the hardware keyboard having become unreliable, the phone is a nuisance to use. I hate the narrow screen with its curved edges.
    0 points
  29. With the current stock firmware, that is correct. You can not.
    0 points
  30. Sadly the lack of a proper hard shell case now that I have gotten my phone (a week or so ago) has pretty much forced my hand into just selling my Pro1 X. I wanted it to become my daily driver and without a solid case solution I don't even want to risk it.
    0 points
×
×
  • Create New...

Important Information

Terms