david
Members-
Content Count
1,255 -
Joined
-
Last visited
-
Days Won
22
Everything posted by david
-
I think they try to get you to enable it by default during setup. There is also another area where individual apps can have permissions to control the wifi. If you find it is still happening, you can look to see which apps have that permission. This article explains how to get there: https://www.megebyte.com/how-to-disable-app-to-control-wifi-in-android-p-9/
-
Go into your system settings wifi screen where it shows all the access point names. Scroll below those and there is a submenu for wifi preferences. In there is an option to automatically turn wifi back on under certain conditions.
-
Another combo is volume up and volume down and power for a very long time. That one might be for a minute or two?
-
Power + volume down for 20-30 seconds didn't bring it back to life?
-
Depends on if the phone is from Minnesota or California. 😉
-
Or at absolute zero! I do feel your pain, however, @SchattengestaIt. My Relay 4Gs (many of them) would get to that state with the ribbon cable for the screen, and I'd have to heat them up or cool them down, depending on how they were feeling at the time. Due to the delay in getting the Pro1, and because I had exhausted my supply of spare Relay 4Gs, I finally had to acquire some ribbon cables (they are almost impossible to find now) and replace them in a couple of the phones so that I had something to get me by until my Pro1 arrived. I'm ashamed to say that did use a Pixel 1,
-
Sorry, regarding accessing /system, I thought that is where the keyboard files were. I see now that they are in /sys. I doubt you can access that from the stock recovery, unless some change has been made to it. Seems like if you can get back into fastboot, your only recourse is to flash .img files over the top of the various partitions? If there is another way you can access files when in fastboot or recovery, I'd be interested in learning about that.
-
Ugh. That sucks. Maybe try holding power and volume down for about 20 or 30 seconds to see if that brings it back to life. I don't know enough about how the LOS build is set up. Can you do any file copying with ADB when you are in recovery? If you can get into recovery, you could possibly mount system in recovery and use ADB to copy the previous version of the keyboard file over. I don't remember if I tried to read anything from /system with ADB when I was in recovery and connected to my computer, so I don't know that is accessible with the stock recovery. Alternatively, have th
-
After a solid month, I give up. I need to vent.
david replied to fxyo1's topic in Pro1 - Thoughts & questions
@elvissteinjr's solution in this post solved this particular problem for me, nicely. The keyboard backlight turns off every time the scree turns off, so if you set your screen to not turn off as often, then you'll face the keyboard backlight issue less often too. However, with the above solution, every time the screen comes back on, it will turn the keyboard on too, so the screen off timer duration won't matter anymore, other than having to unlock the phone (if you have it password/fingerprint/pattern) locked. If you are like me, and have never used Tasker, to import the profile fi -
Can you bring up a different keyboard for different special key combinations (or long presses)? If so, that would be a way to implement what @EskeRahn has mentioned as an idea to have multiple levels of special characters available for each physical key. It would also require the button mapper allowing for key combinations to represent those keys on the physical keyboard, not just tapping them on the virtual keyboard, which would be more of a "cheat sheet"/reminder of which physical key combinations map to special characters.
-
How about clearing the cache and data on the play services and the google apps?
-
Chat (= RCS = Rich Communication Services) is the revamped texting protocol that allows for guaranteed delivery, full sized images and videos, read receipts, typing indicator, longer message limits, wifi chat, and other features (NOT including encryption). It has to be supported by the messaging app and the cellular provider. Google provides the app for Android, called "Messages", and has worked with the cellular providers to make things work on the back end. It will still fall back to SMS/MMS if the other side doesn't have Chat. Formally, non-OEM, 3rd party texting apps aren't allowed acc
-
After a solid month, I give up. I need to vent.
david replied to fxyo1's topic in Pro1 - Thoughts & questions
They make these near where I live: -
Possible from Tasker, but I am guessing you mean with a system setting?
-
I implemented this and it works great. Thanks!
-
Certain keys not working initially? [fixed bug in old ROM]
david replied to cerialphreak's topic in Support
I thought I only got it at boot. In reality, I get it at boot and any other time the screen goes off. -
After a solid month, I give up. I need to vent.
david replied to fxyo1's topic in Pro1 - Thoughts & questions
Missing keypresses might be due to a bug, where you can't press the next key before the last key is released. That should be fixed in one of the new firmware updates. For the / and ? problem, clear your keyboard language selection so that it reads "Default". Then the button next to the left control key will get you / and ? The other 2 are known issues. Hopefully they will be fixed in a newer firmware. -
Certain keys not working initially? [fixed bug in old ROM]
david replied to cerialphreak's topic in Support
That's a great idea. 😉 -
Thanks. Around 20 MB/s sequential read/write is consistent with what I and others have gotten. Something is making it perform well under the UHS-1 speeds.
-
Are you getting 100 MB/s on benchmark apps running on the Pro1 for that card?
-
Certain keys not working initially? [fixed bug in old ROM]
david replied to cerialphreak's topic in Support
Let's put it this way. I *thought* that mine was behaving differently than other people's phones. That's because I was not seeing the problem when I was opening and closing my keyboard. But what I was missing is that my screen wasn't shutting off in the middle of testing. When my screen shuts off (whether by itself or with me tapping the power button), then the problem happens. I'm postulating that other people have their screen go off when they are in closed keyboard mode at some point. They then open their phones and wake up the screen and go to type something and it doesn't work a -
Certain keys not working initially? [fixed bug in old ROM]
david replied to cerialphreak's topic in Support
I'm suggesting it isn't behaving differently, just being interpreted differently, based on state.