Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 08/25/2020 in all areas

  1. Don't know why ota would fail like that but you can always sideload to fix it. The reason adb goes to 47% and stops is because Google expects about 210% data transfer over usb. Once to verify signature, once to install, plus some overhead. So the percent you see is scaled. But lineage recovery caches data and only transfers 100% exactly. So it gets to 47% and then stops while the ota is installed. Lineage adb shows a nice little ASCII spinner to let you know it's alive.
    5 points
  2. SUCCESS! I managed to install the update by flashing via Lineage Recovery / ADB sideload. For anyone who might be in the same pickle as I was, the procedures I described a few posts above were the solution. The most difficult part was getting to boot into recovery, I don't know why. I am sure I chose "Boot to Recovery" a few times at the bootloader but it never worked. What worked for me was the Power Button + Volume Up button method. Talk about relief..! 😁 TL/DR: 20200824 OTA broke my LineageOS setup. Fixed it by: 0) Downloading the latest (20200824) Line
    3 points
  3. Reboot to recovery is mandatory after sideloding LOS because that will switch you to the correct slot.
    3 points
  4. Interesting - shouldn't the A/B slot system be for just these cases - updated slot fails to boot and you can boot the previous slot which is still OK (without the update)? Can you switch the active slot at bootloader mode to previous one and try to boot that one?
    3 points
  5. I've updated OTA to 20200824 and everything went fine. I am using OpenGapps, not rooted.
    2 points
  6. For future reference, a reboot to recovery is on the advanced menu in the Lineage Recovery itself. Glad it all worked out. 🙂
    2 points
  7. You might want to investigate 3rd party camera apps first I cannot recommend any, since I rarely record video and the issue is not urgent to me. But others in the forum surely can help you with suggestions
    2 points
  8. I will just say that manual sideloading of the 20200824 update went smoothly. I always sideload, have never trusted OTAs (not because I have ever tried them, so I don't actually have a good basis for not trusting them). So, AFAICT, there is nothing wrong with the nightly zip. (I also always resideload addonsu and Gapps-- I don't trust the "Preserving Gapps" stuff. 😉
    2 points
  9. 2 points
  10. Landscape support is now in the stable release also (no more just beta). Microsoft Launcher v6 update enables landscape mode and new Feed design
    2 points
  11. This sounds really bad! Let us tag @Erik so he can find out what has gone wrong.
    2 points
  12. Yes, you are right, it is quite normal. I was just trying to alert agent008 in case this was his first sideload and he thought another problem had popped up. 🙂
    1 point
  13. It seems to always do this, did on all the test/images too, so quite normal. Actually the gaps also 'stops' at 47% but is so much faster that we usually do not notice. (I wonder why they did not choose to stop at 42 😁😇)
    1 point
  14. Note that, on my computer, after issuing the adb sideload command to flash LOS, the % tally stops at 47%. It just sits there like that for a long while with occasional text popping up on the phone. You have to be patient, it will complete. Make sure you reboot to recovery after you have flasjed LOS. Also, when you try to sideload Gapps, recovery will complain and ask if it is safe (it's some signature problem I think). Just say yes.
    1 point
  15. Do you mean flash light / torch? If so it's just in the pull down settings menu for quick access.
    1 point
  16. Try this and there's a lot of things I don't understand... But this thread can be closed, buy a new SIM and work flawlessly..
    1 point
  17. Same here, no gapps at all. I tried downgrading (unsupported, I know), but the recovery doesn't accept sideloading in either case (both 20200803 and 20200824). I'm simply getting adb: sideload connection failed: no devices/emulators found adb: trying pre-KitKat sideload method... adb: pre-KitKat sideload connection failed: no devices/emulators found
    1 point
  18. Meh. I don't think we should be bothered by it. It'll probably be the same form factor as we've come to get used from BB. It being a slider phone is a chance of 1 in a million...
    1 point
  19. Regarding sailfish, the port is certainly still in development and has not stalled. I use it as my daily driver with few issues. The latest releases are available from the continuous integration build server at https://gitlab.com/sailfishos-porters-ci/t5-ci/-/jobs Regular users are advised to install the "testing" releases, as the other releases are from the devel branch. I try my hardest to not break the testing repository, but breakage may happen in the devel repository, and I wont give you sympathy if you are running that version 😉 The current releases of the devel ver
    1 point
  20. Ordered: 2019-Nov-07 Shipped: 2020-Jul-29 Delivered: 2020-Aug-03 Shipped from TUEN MUN HK Delivered in Ohio, United States Delivered by Fedex with tracking info. #41xxx; QWERTY; Ah, it's finally here. What a relief 🙂
    1 point
  21. The angels descended before me. My sincere thanks to Fxtec staff.
    1 point
  22. Thanks I just tried it, unfortunately landscape mode is just a stretch of your portait configuration and as such is ugly and not convenient.
    0 points
  23. I'm quoting myself to post an update on this... It's now been 124 days or 4 months since I last heard from fxtec. I have sent in my fxtec phone 217 days or 7 months ago. It's a shame.
    0 points
×
×
  • Create New...

Important Information

Terms