anyone try to customize remote control to allow the phone to learn a device not located in the remote control database??
i am suprising it have this feature, for me it is very useful, but when i try to allow to detect signal from a physical remote control, nothing happen. seems not detecting the signal at all
working or no? kindly any one check this and reply me
Wouldn't work for my telewest remote even trying to customise it.
Anyone with working custom Ir? When I try to teach the Smart Controller custom Ir code it says something like The Ir code was received, but it doesn't work when I use it. I'm on Mate 10 pro 8.0.0.127 c432
You might need to try it a few times until it works.
For example,after the phone had detected the signal, test if it can control the device.
If it can't, remove the signal and try it again.
Sometimes it works after during the first try.
Sometimes it might take more than 5 tries.
I found a method that seems to work fairly reliably on my mate 10 pro: hold the phone and remote about 5cm apart, and extremely steadily (I hold the phone in my left hand normally, hold the remote upside down in my right hand, and support my right hand under the top right corner of the phone), then hold the button down while keeping everything as steady as possible until it registers (should be a second or two unless you are not pointing the remote at the correct sensor). Only had to redo one or two buttons after I started programming it this way.
Related
Hello guys,
I am having this issue with my device - sometimes when I press the home button the Voice talk / command powered by Vlingo starts. I always press the button just once (I understand that it should happen when one double-presses the home button) and it is very annoying :-(
Note, that I have Settings/Motion/Double tap turned off as well. Is there any way to fix this or do you have any idea what may be wrong??
Thanks in advance!
Sent from my GT-I9100 using XDA App
while in the motion settings, you can see the tutorial clip and that double tap has nothing to do with the home button, but with double tapping the top side of the device to start voice control instead of saying "hi galaxy". so even with that switched off, your device will react to hitting the home button twice and does not really help diagnose the initial problem.
either you have a slight hardware defect in the home button, a software issue (or maybe user error). since hardware would be more severe, let's see the software side first. what exact rom do you have? device rooted or not? anything that could mess with voice input (connected bluetooth hands free, market vlingo or other tts or stt software installed...)?
also, just to exclude user error, let another person try.
P.S. are there special circumstances when this happens? like only from deep sleep, only when charging, with a connected headset, running certain apps or whatever?
Chef_Tony said:
while in the motion settings, you can see the tutorial clip and that double tap has nothing to do with the home button, but with double tapping the top side of the device to start voice control instead of saying "hi galaxy". so even with that switched off, your device will react to hitting the home button twice and does not really help diagnose the initial problem.
either you have a slight hardware defect in the home button, a software issue (or maybe user error). since hardware would be more severe, let's see the software side first. what exact rom do you have? device rooted or not? anything that could mess with voice input (connected bluetooth hands free, market vlingo or other tts or stt software installed...)?
also, just to exclude user error, let another person try.
P.S. are there special circumstances when this happens? like only from deep sleep, only when charging, with a connected headset, running certain apps or whatever?
Click to expand...
Click to collapse
Hello, thanks for your reply. I am running the device with an unmodified SW i.e. stock rom (having a branded phone from orange slovakia), no rooted just some apps installed from the android market. It is XXKE4/XWKE7, running android 2.3.3. I dont use bluetooth or handset nor dock or anything like that.
The issue seems to be completely random to me, while I usually notice it during browsing web with opera, but it happens with more apps. I don't know what is tts or stt sw, nor market vlingo. If you would like to know some more details please let me know what would be relevant for you.
I already thought about the hw issue, but I am not sure if they would accept the warranty claim as it is quite random. I thought there would be some way to completely disable voice talk as I dont expect to use it anytime in the future anyway...
As of the user error, it happens both to me as well as to my gf while using the phone for common internet use.
Sent from my GT-I9100 using XDA App
ok, that gave us something to work with. for future reference, when asking a question like this, it might speed up the process by giving as much information in the initial post as possible and let me explain why:
the fact that you use your unrooted stock rom tells me, that it is not a common and maybe reported bug that comes with a custom rom, and with an unrooted device, it is rather unlikely, that you screwed up a system component like this.
bluetooth, docks and handfrees could influence the voice input and its triggering by having their own triggers, but that is not the case.
if it happens to other people with your phone as well, it excludes your personal behaviour, tremors or whatever (no offense, you never know, just to cover everything, some people are shaky).
if it happened only in a special state, like only while sleeping for a minute or while charging, it would ensure, that it has something to do with deep sleep.
about the other things: with tts i was referring to text to speech, the engine that reads out display content, like incoming calls, text messages or navigation instructions, stt refers to speech to text, like voice input, saying hi galaxy, telling where to navigate or dictating notes...
vlingo is the engine that is used for voice talk and voice command and there is also a 3rd version, that can be downloaded on the android market, coming with yet other features and having them all present and maybe screwed up settings might have influenced anything there, however, this doesn't seem to be the case either.
so this leaves few options for how to proceed. in your place i would start off with reading this thread: http://forum.xda-developers.com/showthread.php?t=1097153
it deals with home button issues and a theory on how the home button sometimes might react as much as 15-30 minutes later than initially pressed, which might coincide with an actual press and being registered as a double press (although that's a stretch at best).
and when it comes to a next step, if you made sure, that does not apply to you, i would be uncertain, which way to go. a factory reset might help, but if, after hours of setting the device up again, you realize there has not been any change, it was nothing but work. then there are 2 things left:
either flash a newer rom using odin and any rom from here: http://forum.xda-developers.com/showthread.php?t=1075278 (full guide and download links included)
OR decide to send it in for warranty first and see what's what.
flashing a rom might solve your problems but influence your warranty state, if not done correctly and cautiously, which would make sending it in risky.
sending it in first and not getting that bug recognized or repaired for free would mean you might end up with weeks without your phone and/or a huge bill and the same issue as before.
i guess i would get a usb jig, read up on flashing, try several stock roms, not root the device and see if the bug is gone, if not, flash back to stock, make sure the flashing is not traceable and then try a local store or your carrier for a hardware replacement or repair.
Hey guys,
any solutions ?
http://en.miui.com/thread-3921003-1-1.html
tried automate (tasker alt), autoinput, no luck!
this is especially important while driving! (keep everything nice & safe & hands free)
Really disappointing, they fixed 'OK Google' (though had to clear google app's data before is worked), but broke this, give me some creative solutions
Set face unlock as it's now available for all regions. Tap on the screen when the screen is off and it will unlock while you're driving without a need do do anything else. Not sure if that's what you meant but hope it helps.
Apparently not for Israel, anyway when I switched the region to India and the option appeared, it still didn't work and said it could not recognize me.
At least saying OK Google not only works now but actually unlocks swipe lockscreen, and then the secure one gets unlocked by my amazfit stratos watch... so I guess I will just say OK Google every time I want to turn on the screen instead and well ... use it.
tl;dr: skip to end
Ok so an update / clarification...
up untill now... on miui 9.5...
I had 'automate' (like tasker), when connected to car's Bluetooth, and I would press volume down and up on my bluetooth media button on my steering wheel, turn on the screen, straight to the PIN entry screen, which would be auto unlocked via bluetooth by my amazfit watch, and then 'ok google' would be launched via shortcut (since saying the words didn't work anyway I figured it's way more convenient to have buttons... also because sometimes it doesn't hear / understand you through the noise, and you look like an idiot turning off music and ac and saying Ok Google multiple times ?)
also when I would connect to car's audio when I started the car... screen would be unlocked and spotify would open up and start playing without me touching anything.... now it's stuck at lockscreen untill I dismiss it
Anyay I figured out why Autoinput does not work... because I always use some 'device admin' app to lock the phone (fingerprint quick action \ dts widget \ all in one gestures)
when using the power button, autoinput works
I want my convenience back so what I ask from you:
can anyone report if this issue exists in the beta versions?!
thank you!
Greetings fellow techno-wizards! Got a big problem that I'm hoping you can help me with.
Long story short, my trusty Pixel 2 had one too many drops, now the screen won't turn on and won't respond to touch. The logic board is operating, and I haven't rebooted since then, so I can unlock with the fingerprint sensor.
I plan on getting an Pixel 5 when it releases, and have an LTE Tablet to limp along until then.
My biggest problem is authenticators on my phone that I may or maynot have the backup QR code for, as well as many other things I'd like to get off the phone before I retire it.
I have the following things at my disposal:
Pixel 2, with USB Debugging turned on, and recently trusted the PC. No screen, no touchscreen.
WearOS watch paired to phone (can get notifications and texts)
Bluetooth Mouse
Wired mouse with USB to USB C adapter
Chromecast
Win PC with Scrcpy installed, already tried to use it to show the screen on the PC, I'm guessing its been too long and I have to press a notification to trust the PC.
The Goal:
To cast the screen to a chromecast and pair a bluetooth mouse, and/or get Scrcpy working by accepting the dialog that I can't see. This would allow me to use the migrate tool to the new phone I will eventually get.
I tried long ago to use a USB C to HDMI adapter, that doesn't work. Google wants you to use a Chromecast for such things (Thanks a ton Google )
The thing I need to figure out next is how to use ADB to force the phone to start casting to a Chromecast, or to remotely accept the dialog. The wired mouse with adapter should work to control the phone instead of the touchscreen, but without any video out, I'm clicking blindly. The microphones are working, but I've never tried to command the assistant to start casting before.
Can anyone suggest the next step I should try?
Just had a thought, there are accessibility features for blind people that would let them use the screen without seeing it. Is there any ADB command to enable these features? If I plug in a keyboard, is there a keystroke combination to turn them on?
TheGeek007 said:
Just had a thought, there are accessibility features for blind people that would let them use the screen without seeing it. Is there any ADB command to enable these features? If I plug in a keyboard, is there a keystroke combination to turn them on?
Click to expand...
Click to collapse
Since you say ADB is enabled on the phone you should be able to pull out by means of ADB-driver the data in mind to your Windows computer.
Try Method 2 only if you're sure your Remote has no problem and is connected properly. First is trying to determine the course of action. If you just bricked it. Then there's nothing you can do unless you take it to the care center or if you had adb enabled then you can force it into fast boot look after connecting it to your pc. That will be in another post. For now troubleshooting it is our concern.
So you have tried to use the TV Box and you can't force it to go into recovery mode neither have you had any luck with the usb stick update.
Method 1:
The problem is Mi TV Box won't boot and will infinitely boot loop unless the paired remote is connected. So most likely the boot loop is caused as the remote and tv box isn't communicating. Your remote may either be damaged or need a change of batteries or may have been unpaired/disconnected after the update.
So grab a USB mouse or USB Keyboard. Try mouse click and there will be a blank screen. Wait for 5-10 minutes. It takes time to load or is simply slower when disconnected from the remote.
Some keyboards don't work. But if they do, keep pressing either Esc or Enter till the Bootloop ends and brings you to a blank screen. Be patient and use a mouse/keyboard arrow keys to navigate to settings and Remote & Accessories. Then select Xiaomi RC and click on Unpair. The Battery % will be shown if it was connected properly. So then re-pair the remote and then restart. You can restart by holding the power button till the power menu pops up. That's it and that's all. Be careful since both Mi TV and Mi TV Boxes will not make it past the boot screen unless the paired or stock remote is connected properly. You can't find a totally working replacement/spare remote since the remote and the tv box are one unit and if either is damaged or has a manufacturing defect, it can't be easily replaced. As both have sort of link. So suppose you buy two Mi TV 4K Boxes and use both at the same time. The remotes will pair up and be forever linked to one particular at the time of set up. You can't randomly change it after that. Exceptions are always there but this is the case for the most part. Or so I believe it to be.
Method 2: If the above method didn't fix it. The issue is software related. You may need to perform a hard reset using either the recovery or get a keyboard with the same or equivalent combination of keys you'll use on the remote. Considering the remote not working or unable to boot into recovery using the remote. If possible get two people to do the recovery sequence on the remote. Since the remote is good quality and sensitivity for button press. Then load up the stable or latest beta update available onto a pen drive. Make sure that the update package is renamed to update.zip. Before installing Wipe/Reset All Data and it'll ask for confirmation. Confirm it and then proceed to install update.zip. The Pen Drive used may also result in success or failure. So use a reliable know good USB 3.0/2.0 stick. SanDisk gave me issues. I had to re-install thrice to get it to work properly. Also don't use sizes above 16 GB. Upto 32 GB is supported. And it may support external harddisk drives but the format is to be kept in mind. Any pendrive larger than 32 GB comes out of the box with either NTFS or exFAT File System Format. So check that before you put the update on it.
Hi all.
The LCD of my A52s is broken. Android 12
I wanted to make an Backup but I cant access the files unless the display is unlocked.
I have registered a pattern and a Fingerprint.
Tried to use fingerprint : vibrating but not working
Tried Samsung Find my mobile to unlock screen : Not working, says "Remote unlocking is deactivated"
What are my options if there are any?
Dont want to root it.
Thank you in advance.
//edit :
Not sure if USB Debugging is enabled.
Otg usb adapter and a mouse
joke19 said:
Otg usb adapter and a mouse
Click to expand...
Click to collapse
The LCD is broken, not the glass :/ Its just black with some lines if activated. I cant see anything on the display at all
Fseggl84 said:
The LCD is broken, not the glass :/ Its just black with some lines if activated. I cant see anything on the display at all
Click to expand...
Click to collapse
Sorry
Mouses are relative positioning things. That makes life more difficult.
A digitizer pad would be better, but those too do a bit of panning.
You want an absolute pointer device.
I had an old hardware project that I just updated and used to debug some media commands.
It uses a serial port from a desktop that feeds a µC that is a peripheral to an Android over OTG.
So you can put absolute positioned clicks into an unrooted, non-ADB device.
But it seems to have a bug now. I have to look into it.
Dumb question: Do you need to swipe to enter your password or can you just click?
Renate said:
Mouses are relative positioning things. That makes life more difficult.
A digitizer pad would be better, but those too do a bit of panning.
You want an absolute pointer device.
I had an old hardware project that I just updated and used to debug some media commands.
It uses a serial port from a desktop that feeds a µC that is a peripheral to an Android over OTG.
So you can put absolute positioned clicks into an unrooted, non-ADB device.
But it seems to have a bug now. I have to look into it.
Dumb question: Do you need to swipe to enter your password or can you just click?
Click to expand...
Click to collapse
By password you mean the pattern to unlock? Its swiping.
Fseggl84 said:
By password you mean the pattern to unlock? Its swiping.
Click to expand...
Click to collapse
Yeah, I've never used it so I didn't know if you could just tap the dots in succession along the path.
Not a big deal or difference, if I could just get the HID report descriptor working.
Edit: Ah, got it working. Android doesn't seem to like it when a USB peripheral is a keyboard, consumer control, mouse and digitizer.
So I took the mouse out.
Did I guess your swipe pattern?
Do the swipe dots appear in your login screen centered exactly vertically?
Renate said:
Yeah, I've never used it so I didn't know if you could just tap the dots in succession along the path.
Not a big deal or difference, if I could just get the HID report descriptor working.
Edit: Ah, got it working. Android doesn't seem to like it when a USB peripheral is a keyboard, consumer control, mouse and digitizer.
So I took the mouse out.
Did I guess your swipe pattern?
Do the swipe dots appear in your login screen centered exactly vertically?
Click to expand...
Click to collapse
It looks like this =)
Thats not my display by the way.
When I try to use the fingerprint, it vibrates but the phone does not recognize it.
It's kind of pesky that the aspect ratio, the vertical position and the scale of the layout are all a bit variable.
At least the aspect ratio is a solid number. Height in pixels/Width in pixels. I make yours to be 2.18?
Too bad you didn't try to do this when your display was working!
My setup works fine, but that isn't really going to help you any at this stage.
I was thinking of getting a separate Android to use as the "digitizer" but that means getting a Linux USB HID gadget working.
That looks like a bunch of work and moreover it's not universal for any Android.
So, I don't know that this is going anywhere. It's even possible your device locks out USB OTG when you're not logged in.
That's easy enough to check, just use a OTG adapter and a USB device with a LED, flash drive, mouse, keyboard...
If you can borrow a Wacom tablet from someone that might operate in absolute coordinates.
The problem is, it can operate in relative mode too and without the Wacom software installed you won't be able to switch it.
The last Wacom I had just plugged into Windows and operated as relative.
https://support.wacom.com/hc/en-us/articles/1500006340122-What-is-Absolute-Positioning-
Unless you have an ATMega32u4 and a UART I don't know what we can do.
The Raspberry Pi 0W could do this too, but I'd have to write all the code for it.
Renate said:
It's kind of pesky that the aspect ratio, the vertical position and the scale of the layout are all a bit variable.
At least the aspect ratio is a solid number. Height in pixels/Width in pixels. I make yours to be 2.18?
Too bad you didn't try to do this when your display was working!
My setup works fine, but that isn't really going to help you any at this stage.
I was thinking of getting a separate Android to use as the "digitizer" but that means getting a Linux USB HID gadget working.
That looks like a bunch of work and moreover it's not universal for any Android.
So, I don't know that this is going anywhere. It's even possible your device locks out USB OTG when you're not logged in.
That's easy enough to check, just use a OTG adapter and a USB device with a LED, flash drive, mouse, keyboard...
If you can borrow a Wacom tablet from someone that might operate in absolute coordinates.
The problem is, it can operate in relative mode too and without the Wacom software installed you won't be able to switch it.
The last Wacom I had just plugged into Windows and operated as relative.
https://support.wacom.com/hc/en-us/articles/1500006340122-What-is-Absolute-Positioning-
Unless you have an ATMega32u4 and a UART I don't know what we can do.
The Raspberry Pi 0W could do this too, but I'd have to write all the code for it.
Click to expand...
Click to collapse
I really appreciate the time and thoughts you put into this problem.
But -> "no backup no sympathy"
I was my fault not doing a regular Backup and so I guess the data is gone. I might just let samsung change the display and hope they wont reset the device.
It's too bad you're not local. This would be a piece of cake.
It's actually so much fun watching this thing login.
I wrote a cleaned-up Windows program for this. Now the command is:
Code:
C:\>swiper /c3 /a2 /y0.683 /u 791364
The "password" uses the position of the digits on the keypad.
Unfortunately I've never done a deep dive into the whole encryption of /data
Is there a TWRP that can decrypt? Does that require swiping too?
I dunno, I might be able to mail you a RPi0 with code on it.
Still, if you didn't leave ADB on, it will be a big pain to enable it.
You could also buy a replacement screen and just connect it up floppy-wise without removing the old screen.
Sometimes the most simple ideas are the best.
We used cling film on the same model and painted dots on the film where the pattern is.
Put that cling film on my phone and swiped my pattern. After a few tries it unlocked.
Using my fingerprint wasn possible.
Oh! I thought that the touch screen itself was non-responsive.
I had presumed that you had unlocked it enough times that you could unlock it without looking.
In any case, I've had fun with this. My new secret unlock pattern is:
This has maximal pointyness and requires coordination to swipe between the dots without catching the wrong ones.
If they only gave us a choice of 4x4 or 5x5 we could come up with a pattern that a human couldn't do!