My screen suddenly became garbled, like static TV noise in colour, but the phone seems to be working in the background.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The pattern is different when I press the power button twice to "cycle" the screen on and off.
I can switch it on and off, the fingerprint reader wakes up the phone, my router can see the phone and gives it an IP.
I can list the phone with adb with a USB cable connected:
Code:
$ adb devices
List of devices attached
XxxxXXxx unauthorized
Unfortunately my current computer is not authorized. Is it possible to change the "adb ID" of the computer so that the phone recognizes it as authorized (I might have a backup of an older computer that might contain some keys).
Does anybody have any idea what I can try to fix this, or what could be broken? I'm afraid it's something hardware related or in the screen, so that it has to be replaced.
I've only been using it as a backup phone lately, so I don't think I have anything important on the phone, maybe there is a way to factory reset it and see if the screen starts working properly again?
I've also tried shaking and tapping, to see if there was a physical glitch that could be unglitched .
OK, so the way to change the computer's adb ID (the one that the phone sees) is to replace the key pairs ~/.android/adbkey[.pub]. That didn't help me unfortunately, since none of my backup keys were accepted on the phone since before.
I managed to enter my unlock PIN after a few attempts in the blind though (which means input is working fine, just not output), and also to accept the computers adb ID, so I am now backing up what I can with adb pull .
The screen problem might be due to a broken "data choke" (filter?). At least this is a known problem on some Samsung models and Pixel 2, according to:
I haven't seen an easy way to solve this for the Oneplus 5T yet though (that is, I haven't seen anything looking like the small components in that video on videos or pictures of the internals of a 5T.
Anyone know of this, or know what the components are called and if there are components like this for the 5T?
Related
I was playing with my phone the other day and the home button and the search buttons suddenly stopped working. Totally out of the blue.
I have tried different ROMs, and they started working again for an hour or so and then stopped again. The keytest in recovery registers the key presses.
What do you think may be wrong?
It's probably hardware, there have been other reports of buttons that stop functioning, run a search and you'll find them.
Repair is the only solution I guess.
I doubt its hardware, I tried setting the volume up button to the hone function with an app, but that does nothing either.
Sent from my HTC Desire using XDA App
I hope it's not hardware too but this kind of complaint isn't the first
http://forum.xda-developers.com/showthread.php?t=761494
http://forum.xda-developers.com/showthread.php?t=798089
http://forum.xda-developers.com/showthread.php?t=778793
...and others.
Can you access the *#*#3424#*#* test menu. If you can run the button test.
Another think you may try, is booting in safe mode to check if they would work then.
If you cant get it working take a look at this.
Edit: This app has just been released on the market, search for 'button savior'.
The app was made for the HD2 but is working fully on my desire running cyanogenmod, haven't tried any other roms.
I hope you get it working and don't need it though
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3722 said:
I hope it's not hardware too but this kind of complaint isn't the first
http://forum.xda-developers.com/showthread.php?t=761494
http://forum.xda-developers.com/showthread.php?t=798089
http://forum.xda-developers.com/showthread.php?t=778793
...and others.
Can you access the *#*#3424#*#* test menu. If you can run the button test.
Another think you may try, is booting in safe mode to check if they would work then.
Click to expand...
Click to collapse
Some success, I installed CM 6.1 and had my home and search buttons back. THEN, I restored a bunch of apps with titanium backup, I soon restarted my phone and bam, buttons no longer function on the reboot.
My problems don't seem to be the same as the above links, keytest in recovery has no problems with the buttons, they have not been playing up over a long period of time, and they are not erratic. They either work or they do not.
I suppose I should uninstall apps till I find the culprit?
I can't think of a better fix than that, might take a while but at least you should be with a fully functioning phone in the end
Probably it's better to first install the quality apps that you know are not causing the issue, and then install one by one apps that are from not so renowned devs.
I've been using my One X for several weeks now (I think the hboot date is around early June so it's not one of the early batches) and so far didn't have any problem except for the following:
Twice, first a few weeks ago and the second time last night I saw some "artifacts". I'm not quite sure but I think different parts of the screen were affected each time. What happens is that everything is shown how it's supposed to be except for a 30%-40% area which looks a little like a computer screen right after a software/driver crash can look like. Without doing anything, it disappeared each time after less than a second.
I wasn't able to take a screenshot but the following photo shows how it roughly looked like. In my case, there were only lines and cubes in black, white and bright green instead of the more "fuzzy" parts shown in the photo.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is this a driver issue? A lose connection? A display fault? I was close to unlocking my phone but with this having happened twice so far I wonder whether I should wait a little longer...
PS: It's probably unrelated, but like a minute later I encountered some "keypad ghosting" via swiftkey, i.e. I was pressing some keys on the keyboard and it was inserting several different ones each time. I do suppose that it's a software glitch, though, as I tried the stock keyboard another minute later and this worked fine.
If you can still swap your device with your retailer I would do that, just to be on the save side...
did u update to latest already?
if yes,
was it there before u updated..??
it doesn't look like a hardware issue
Did it act like this: http://www.youtube.com/watch?v=HIY0_Hy2_mA ?
CAPSGUY said:
Did it act like this: http://www.youtube.com/watch?v=HIY0_Hy2_mA ?
Click to expand...
Click to collapse
No, everything was where it was supposed to be and the artifacts faded away after probably less than a second.
I still have the latest stock Rom, haven't updated yet. I do think it's been more of a software glitch but I couldn't find information on here or anywhere else which would state a similar problem. Which is good?
Sent from my HTC One X using xda app-developers app
Has anyone else had the talk-to-text voice recognition features change on their phone without them doing anything?
The voice recognition used to look like the first screen shot below when used in any application. After speaking it would recognize that you stopped talking and then give you 3 options to choose from for what it thought you might have said.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This second screen shot shows what the talk-to-text looks like now. It just appears at the bottom of the apps its called in. However, it also doesn't recognize that you've stopped talking and it no longer gives the suggestions.
Has anyone else had this issue with their phone? Anyone know how to fix it or change it back to the way that it was when it actually worked?
I certainly hope it's not the new way it's going to be because it blows pretty hard.
Bakefield2 said:
Has anyone else had the talk-to-text voice recognition features change on their phone without them doing anything?
The voice recognition used to look like the first screen shot below when used in any application. After speaking it would recognize that you stopped talking and then give you 3 options to choose from for what it thought you might have said.
This second screen shot shows what the talk-to-text looks like now. It just appears at the bottom of the apps its called in. However, it also doesn't recognize that you've stopped talking and it no longer gives the suggestions.
Has anyone else had this issue with their phone? Anyone know how to fix it or change it back to the way that it was when it actually worked?
I certainly hope it's not the new way it's going to be because it blows pretty hard.
Click to expand...
Click to collapse
Did you just upgrade from ICS to Jelly Bean? I never used speech-to-text in ICS, and the speech-to-text popup in JB has always looked like the second version for me. In Jelly Bean, it will still sense when you have stopped talking, there is just a longer delay. You can also tell it that you have stopped by tapping the microphone symbol again. If it recognized your words incorrectly, you can tap the incorrect words if they are underlined. Alternate words will be displayed.
I recently bought a bluetooth keyboard to type faster. Initially it wouldn't detect some keys like Shift or Ctrl, so I had no way to capitalize letters. At some point, after installing the Google keyboard (gboard), these keys worked. I could press simultaenously the "Shift + a" and then I got an "A". Yes, pretty basice. The thing is that after a day, it went back to not detecting these keys anymore. That means that I can't choose the special characters above the numbers (like brackets, @, etc).
I tried to root and use a "Bluetooth keyboard fix" app from the market. Unfortunately, nothing works.
I'm lost and I desperately need a solution. I tried to connect the keyboard to my phone (Huawei P9 Lite) and I get the same result: no Shift, no Ctrl.
Anyone knows how to solve it? Thanks!
Sounds to me like the might be a hardware defect? Which ROM are you on? I've had trouble with Bluetooth keyboards sometimes, but usually not something as basic as the shift key. Occasionally stuff may go wrong with the keyboard switching to a wrong mode, but that would normally affect the letter buttons for me, not shift.
Generally on any android version from lollipop upwards I haven't had to use an external keyboard app for anything on my various Bluetooth keyboards.
I'm in stock ROM, the latest that Samsung put at our disposal: 5.1.1.
Sounds like a software glitch but can't make sure!
Given you describe that the same issue occurs on another device, I'm afraid it sounds to me like a problem with the keyboard. Switching off these buttons would seem like a strange software feature -though I can't say for sure, of course.
Thanks, I have written to the seller.
I had nothing to lose, so I've decided to open the keyboard. It had several clips around the plastic "grid". There is a flat cable connector; I reassured it and... bang! I'm posting the picture to help others (though I think I was the only one with this weird problem).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Glad to hear it's working now and that it was a defect you were able to fix yourself!
Enjoy typing
First off, I Love the phone. Hardware is great, Android 12 is mostly great but there are some weird things I've noticed that haven't really been an issue on previous phones pre-Android 12. I got rid of a OnePlus 8 pro for the Pixel 6 pro.
1: I have to use a Bluetooth to 3.5mm adapter (Bluetooth to auxillary input) on my car to Bluetooth to my stereo. Issue is, the adapter is ALWAYS on and when in range my phone is ALWAYS connected to that adapter. Android 12 gives you the option to quickly switch when you're playing music or watching a YouTube video in the volume slider menu but not say when you're playing a Facebook video, Instagram video or similar. The workaround has been to just completely disconnect Bluetooth which interferes with other devices like my Fitbit and such.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2: AOD doesn't come on when it's dark out. I usually get up at around 4am, and of course it's dark in my room. When it's pretty dark, not even pitch black AOD doesn't turn on. It's almost like the phone lacks a proximity sensor and relies souly on a light sensor for AOD. Another scenario was I was out with my family trick or treating tonight, in the suburbs where there was plenty of light and AOD still didn't come on when I pulled out the phone to check the time. Of course this isn't a huge issue, just an inconvenience
3: the lack of ability to set your own lock screen shortcuts. I don't use Google pay, nor do I control devices using the Google home app or shortcut.. it would be nice to set those to whatever I want. To add into that, I do have those both disabled but occasionally the Google home shortcut appears when I click the power button to turn the phone on. If I click it of and back on about 80% of the time it disappears.
I don't want anyone to take these as complaining, just thought maybe I'd chime in on some "issues" I've noticed.