Jump to content

Hook

Keymaster
  • Content Count

    2,054
  • Joined

  • Last visited

  • Days Won

    332

Everything posted by Hook

  1. Sorry, no, I meant an app in the play store called "Finqwerty" (the developer is Finnish) that gives you alternative key mappings for the Pro1 hardware keyboard. https://android.onse.fi/finqwerty/#pro1 It's free and the "US for Physical Qwerty" is wonderful. One of the things it does is allow you to use shift for almost all the yellow characters except ? and /, which have to be left on the L and the P keys and require the arrow key because it is more or less hard wired. https://play.google.com/store/apps/details?id=fi.onse.qwerty.finnish EDIT to add: Finqwerty is n
  2. If you are using stock, unselect US English for the Physical keyboard and select "default" and you will get ? and / back. The spacebar behaviior in one app I have no explanation for. You might also investigate Finqwerty for an even better experience.
  3. You simply rename the .apk file to .zip (apk files are really a type of zip/archive), then flash it from recovery. Here are the actual instructions from the web site, under Custom Recovery: https://topjohnwu.github.io/Magisk/install.html#custom-recovery
  4. @Jeffrey I edited your message. It is a really bad idea to post email addresses and phone numbers on forums. It invites collection of that personal information. I left the email in a less bot-recognizable format. You should only provide things like a phone number by DM.
  5. The rule about updates is ambiguous. It just uses the term "monthly," which is satisfied as long as an update is made once each calendar month. So, technically, an update on the 1st of one month and the 31st of the next month would satisfy the criteria.
  6. Thanks for confirming that... I was pretty sure I saw connectors of some sort under that wrap. I just wasn't sure how important the wrap was or if it was just a protective wrap. I'll eventually get curious enough to investigate, but for now I'm not too worried.
  7. I flash Magisk as a zip in recovery when I first flash Lineage. After first boot, I download and open Magisk Manager and choose the install option where Magisk Manager does all the boot image patching shuffle and rebooting automagically itself. After that, I never touch Magisk Manager again (I only root for SU, I don't use any of the modules-- or at least I don't change any defaults) and I keep root after OTA.
  8. OTA worked great as well. By the way, since I had to recently do a first flash after leaving my Droidian experiment, I now have the newer MindTheGapps-13.0.0-arm64-20230408_162909. They are fine, and I don't notice any difference, so probably no reason to update.
  9. My guess would be they ship the batteries with about 50% charge, so I'm not too worried. What I'm not sure is how one would charge the battery with those converters... can you link to one. Unlike any battery Ive ever seen (but they were all removable), there are no visible + and - contacts. I have a universal charger for batteries like that. But this battery is sealed except for a very thing cable with a connector on the end. Probably the connector has tiny pins for + and - contacts, but I'm really not knowledgeable in this area. So, I'm hoping I'm right, they sent with a decent storag
  10. Lol, I hadn't even noticed, but, sure enough, my Pro1 on Lineage 20 doesn't go green. It has had a couple of screen replacements done by FxTec so I can't swear it's LOS... The next time I flash back to stock (probably before I try Sailfish) I'll stop and test on stock.
  11. Wow, I guess US Banks are (thankfully) less security conscious. Bank of America has no problem with either LOS 20 or my Pro1x being rooted (although I just did this as a test-- I actually do my banking on my not rooted cheap moto). Frankly, it makes me happy that BoA doesn't mind. Maybe makes up for having such crappy carriers. 😄
  12. I have no experience with a Surface Pro (and very little with Win 11), but Windows has always been a bit finicky with fastboot and adb (or, rather, properly connecting with the phone you are using them on. If you have a USB2 hub around, I would try that, USB2 often works better than USB3. Also try different ports, if the Surface has more than one, and different cables. I assume you enabled Developer Options for Android on your Pro1x and then turned on debug? I gave up on using my Windows 10 laptop for this and now use an old Thinkpad X230 running Manjaro Linux and a USB 2.0 Hub atta
  13. Just got around to updating to the 20230511 nightly (Official) OTA and everything is fine. It has the May 2023 security patch.
  14. 1. LineageOs doesn't mess with the persist partition. 2. You need to erase userdata before installing Lineage. So after you flash the dtbo.img and the recovery.img, as per the instructions, you reboot into recovery and select factory reset on the recovery menu. Then you are finally ready to adb sideload the Lineage zip file.
  15. Yes, as the title states (and threads here can get caught up in issues) this is the thread for the Official version. They are referred to as "nightlies," but they are posted weekly, so, yeah, a little confusing. Each one is the current official version with updated security patches. There is a change log available on the Lineage site where you download the files for first flash. After that, you can update OTA. The links are in the OP.
  16. Unless, as in my case, you bought it to be a wifi pocket computer (it's not a tablet). I should demand a refund... they sent me a phone. 😉
  17. Well, I'm back. Everything just started working this morning with the folks on Droidian telegram, still including @matf-kabouik, walking me through steps I thought I had already taken, but maybe in my frustration never all of them in the right sequence. Plus fastboot seems to be behaving again. Whatever, I have Droidian bootable again on my Pro1. I love that we are not just buying phones but also a great community of folks willing to help. Thanks all of you.
  18. Did phone calls work consistently on stock? Lineage really doesn't really change that, as far as I can tell.
  19. MindTheGapps 13 are linked here. https://wiki.lineageos.org/gapps Just noticed, they have been updated to April 2023... we have been using the Oct 2022 package. 🙂 Make sure you grab the Arm64 version.
  20. Glad you pulled it all together. MindTheGaps is officially sanctioned for a reason-- it works reliably. You want the version for Android 13. If you did not flash them before booting Lineage, you will have to re-flash lineage, including rebooting to recovery after flashing and then flash MindTheGapps after that, then reboot. MindTheGapps only has one size and it isn't a minimal set, but also not a full set. Open Gapps does not seem to get along well with Lineage any more. There may be other packages people here know, but I don't, sorry.
  21. I think, for Windows, the files you are trying to flash should be in the same directory as the fastboot and adb executables. I suspect that is what that output is about (not sure as I have never encountered it). At least that's how I always did things in Windows and thought at the time it was necessary. So, locate the boot.img file and whatever else you will end up abd sideloading in the directory with all the Google tools like adb and fastboot. Try again. And, yes, your Pro1x is unlocked. They ship that way.
  22. I would need a lot more context of what you have and haven't done, in an orderly step-wise fashion. The troubles with your USB-C port I can't address, but it sounds like you have it working if fastboot devices returns fastboot in a terminal screen on Windows. I also can't really address using Windows for this. Although I am a Windows (10) user and have done this with Windows in the past, Windows is so tempramental with this flashing stuff that I switched to an old Thinkpad running Manjaro Linux for all of this. By the way, you don't need to set your usb connection to file transfer
  23. The easy fix is, of course, a tiny piece of black electrician tape cut to the size of the finger print sensor. Actually, the black stickers that cover the screws on the back of the screen (on the Pro1x they are invisible, unlike the Pro) are exactly the right width and can be chained across to cover the length of the fingerprint sensor. I have sheets of those black screw covers, if you want to DM me your address. I think Fxtec has enough on their plate, I doubt the feature request would get a lot of attention right now. I have only heard of this consequence of the sensor being activ
  24. It doesn't happen with Firefox. It does happen with Chrome, Chromium based browsers and I found a couple of other apps that will react to it, but most don't and, being a Firefox user, not using my fingerprint reader and 99% using the device with keyboard out, I never even noticed it before someone called my attention to it.
×
×
  • Create New...

Important Information

Terms