Just got a Gamesir x2 in for my old Nokia 7.1, but the controller isn't detected. It is on my Galaxy S10e, so I know the controller isn't defective. Nokia 7.1 is fully up-to-date running stock Android 10. I was having issues getting out detected by adb (had to manually flash security patch updates. Long story). Any help would be appreciated.
Related
First, thank you to all the people who have contributed questions and answers about the Samsung Galaxy S phones. If only the company was as good as their phones!
Here is the problem for which I seek a solution:
Started with unlocked Vibrant I9000M from Bell in Canada.
It arrived with Froyo 2.1-update 1, kernel 2.6.29, UGJH2.
Everything worked, phone worked with an AT&T SIM.
Then I let Kies upgrade to Froyo 2.2, kernel 2.6.32.9, UGJK4.
Problems: headphone jack=no output
USB=no connection with Linux or Windows
screen orientation stays landscape no matter what I do. (except for dial pad).
And worst of all , NO ROOT!
Android recovery 3rd edition will not let me use the update.zip method.
No computer I have used with Android SDK will find the device with adb.
It does not show up as connected with USB in WinXP, WinVista, Win7, Ubuntu, or Kubuntu. I have installed all manner of Samsung USB drivers. Best result to date is in Windows, "device failed to start" Code 10!
So who among us has the way to re-establish a connection with the device so I can get root again and change the ROM to something other than a Samsung ROM apparently designed to close the door on open source?
drddx66
Google Nexus One
Clockwork Recovery
Cyanogen Mod (like 6.1.0-RC1 best)
you wont find much help here because you have a different galaxy s phone. check here
I am trying to use this guide to update my moto z to nougat. I know it works, but I cant get it to. When I try to do it, I get to step 5 which is "Run flashfile.bat which will flash the Rogers firmware to your device (WILL WIPE EVERYTHING EXCEPT MICRO SD CARD)" but I just get "waiting for any device" in the command prompt window. I dont know what to do to fix this.
I have a unlocked Moto Z bought through Amazon
retus software channel
Android 6.0.1
July 1, 2016 security patch
SKU XT1650-03
Your computer isn't communicating with your phone. It is one or more of these things: You didn't install the drivers, you installed the wrong drivers, your usb port is bad, your not plugging your usb in the same usb port as you did when you installed the drivers, your cable is bad. Good luck.
Are you on Windows 10?
If so, that's the problem. RSDLite and Windows 10 don't play nicely with each other as of right now.
Hello,
I was trying to develop an app that uses USB Host/Accessory mode to communicate with a python script on another linux device (for now it's my PC). I noticed that getAccessoryList() and getDeviceList() both return null/empty and after searching a lot I came across USB Host Diagnostics from chainfire.
And when I tried it this was the result: usbhost(dot)chainfire(dot)eu/?search=1382824
As you can see, the kernel supports OTG while the OS doesn't. My devices are Samsung S5 and Note 8.0 and both gave the same exact results. My devices are rooted but that was the only modification i've done to them.
So is there a way to fix this issue ?
Thanks in advance.
Hi,
I have got a Windows CE 6.0 head unit for my car. When I try to use mirrorlink I get error "Fail to Initialize mutually control service, please retry".
I have tried two different phones both Samsung A5 2017 and Samsung S8 (both running Android 8) and none of them works.
Tried different cables but still no joy. Easy connect software is installed, Developer mode is enabled, All the apps have been granted permission to install via USB still no joy.
I tried my friends Samsung S6 edge and that worked, it runs Android 7 and there is an option to allow unknown installation via USB.
Can someone please suggest a solution to this problem?
Anyone?
I have the same issue with Huawei p10 Plus (Android 8).
Now with Android 9!!
Please use this link for apk
This will work
https://drive.google.com/file/d/181jsT3m5BuLAEQK24ve_sS8Xh7F4KDVb/view?usp=drivesdk
Hello!
Here are the system specs:
Device: Kindle Fire HDX 8.9 (3rd gen, apollo)
Android Version: 7.1.2
LineageOS: 14.1 (ggow's most recent build for this device)
TWRP 3.2.3-1
OpenGApps 7.1 (nano/arm)
Bluetooth devices I've tried to connect without success:
Keyboard: AmazonBasics Wireless Keyboard model KT-1267
Headphones: Anker SoundBuds NB10 model AK-A32600M1
Headphones: Anker SoundBuds NB10 model AK-A3260011
Here's what I did to set this Kindle up with Lineage OS and OpenGApps:
Using adb and fastboot from my Linux desktop, I flashed TWRP
Did a complete wipe of the device from TWRP
Installed Lineage OS and OpenGApps using TWRP
I did this process a couple of times to try Magisk and MagiskManager, but the most recent time I did those steps I did not install Magisk or MagiskManager. The device is rooted, and each time I went through those steps I did a complete re-wipe to start fresh.
When trying to connect headphones, the device shows up in the list of available devices on the Kindle. I select them, it grays out to show that it's Pairing... and never connects successfully. Both headphones connect to other devices successfully.
When trying to connect the keyboard, I get to the part where I'm given a pairing code to type in. I type it in, hit enter, and nothing happens. Eventually I get an error: "Couldn't pair AmazonBasics keyboard because of an incorrect pin or passkey"
Here's what I've tried:
Replaced batteries in keyboard.
Connected the keyboard and headphones to other devices (all have successfully paired with phone and desktop)
On my Lineage OS Kindle, I went to Settings > Apps > Selected Show system > Bluetooth extensions > Storage > Clear Data (there was no cache to clear so I couldn't click that button as well)
I also reset the network settings via Settings > More (under Wireless & networks ) > Network settings reset
Restarted my kindle after each of the previous to steps.
The headphones are from 2017 and the keyboard is from 2015. I'm mostly sure this isn't a problem with backwards compatible Bluetooth versions but I haven't been able to figure out which version each device is using.
At this point I may just get a mini-USB keyboard to use with my tablet but I'd love to hear anyone's ideas on getting Bluetooth to work. Bluetooth did work a few days ago when I was running a Fire Nexus ROM from 2016 (I had Android version 4 with that ROM).
Thank you for your time <3
And a huge thank you to the team behind Lineage OS, and to this community. On Android v4 I couldn't use Termux so my tablet was mostly for reading. Even if I can't get Bluetooth working I'm stoked to have Android v7 and can't wait to start doing way more with it!
I am having the same problem as you on a HDX 7 I just unlocked with 1-Click and flashed with Lineage OS 14.1 yesterday. Bluetooth seems to be working and finds new devices, but pairing process fails. BT was working fine with stock OS previously.
Take a look at this thread (down the page a bit), it seems the same thing happens with AOSP and it might be an inherent problem with the HDX. They do describe ways to get devices paired, and once paired they are easy to re-connect. My HDX is at home and I have not tried their suggestions yet:
https://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-aospextended-t3691138/page27
Using the tips in that thread I posted, I have now been able to pair multiple Bluetooth devices (2 sets of earphones, keyboard, and trackpad) and once paired, re-connecting is seamless so far on my 8.9 HDX running Lineage 14.1.
I was able to easily connect a Zagg Limitless Bluetooth keyboard on the first attempt. After that, I was able to pair other devices by tapping keys on the connected keyboard while pairing with the other devices. Doing it that way, everything else paired on the first try and has worked great.
From reading around, only 4.4 KitKat ROMs have bug-free Bluetooth (I loaded a 4.4 based Lineage on my 7" HDX and the Bluetooth works without a hitch there.) But if you can manage to pair one device, you should be able to pair others after that on newer ROMs.
After a little more usage, I am finding the Bluetooth is sometimes flaky- some devices always re-connect great, some are not consistent. Also, I sometimes need to turn wifi off and on to re-connect after sleep.
For these reasons I decided to install Lineage 11 which is 4.4 based, so far these things seem more consistent (have not used too long yet though.) Anyway it's amazing to have options for such an old device.
Thank you for posting this! I forgot to check back on this thread, but I'm going to give this a shot and see if I can make it happen.