I instale the ( Lineage os 17.1.20200415 and Gapps) on my S8+ . All ok ,Thanks to the developer . The only problem is with Android Auto and the usb connection in Lineage software... maybe authorities usb choice is not to file tranfer...
In S8+ with original samsung os "android 9" the application android auto with same version as above function very well.
I think the problem is the way that lineage manage the usb connection with Android Auto!!!
When Android Auto strat in the infotainment the phone usb force (goes) to "without file transfer" and the connection stops
Any help
Wrong section bro. You don't need to open two threads for this. Try asking in the Telegram group of the specific ROM.
You will get help there faster
Related
So, I was looking through the Developer Options on my Android 6.0.1 Galaxy S6 and found a setting for USB Configuration. Now, at first this seemed rather obvious, MTP mode, PTP mode, Charge Only, etc... until I found the Audio Source option. I tried selecting this and connecting to my Windows 10 PC and it detected what it thought was a generic "USB Audio Device", but returned an IO error and couldn't start the device. I'm guessing Windows needs a more specific driver to recognize my phone as an audio source, but where can I find such a driver?
It's not working somehow. The implementation isn't meant to work from what i heard. I wrote to the (German) Samsung twitter account and they said it's not working (idk why). But they said it's not working
I instale the Android 10 (lineage.. and Gapps) on my S8+ . All ok ,Thanks to the developer . The only problem is with Android Auto and the usb connection in Lineage software... maybe authorities usb choice is not to file tranfer...
In S8+ with original samsung os "android 9" the application android auto with same version as above function very well.
I think the problem is the way that lineage manage the usb connection with Android Auto!!!
When Android Auto strat in the infotainment the phone usb force (goes) to "without file transfer" and the connection stops
Please help
Hello
I don't know why but I cannot use ADB since android Q. (Option is of course enabled for USB and also network)
When I connect a computer with adb binary (windows, linux and live linux) the mido detect it because I get a notification in notification bar, but the computer is always unautorised, and I believe there is a problem in displaying the authorisation RSA popup. Never show this popup in android Q !!!
No problem with android 9 I see the autorisation popup and ADB work correctly.
But with android 10, there is no popup for authorisation ! --> the computer is alwas unauthorized .
I try a lot Android Q rom (system-roar-arm64-aonly-floss.img, caos-v224-201029-arm64-avN.img, Havoc-OS-v3.8-20200821-Official-arm64, RROS-Q-8.6.4-20201111-mido-Official) all have the same problem. No popup for ADB authorisation.
I reinstall android 9 (AOSP Extended) and no problem !!!! All is working correctly.
- I always wipe all partitions with mido flash_all or flash_factory, every time I flash a new ROM. (I can do it more because there is no important data for the time)
- On computer I restart and remove adbpub keys also without result.
What can I do more ? Any idea ? (I cannot debug the local debuger without adb )
Thanks
neo_mat said:
Hello
I don't know why but I cannot use ADB since android Q. (Option is of course enabled for USB and also network)
When I connect a computer with adb binary (windows, linux and live linux) the mido detect it because I get a notification in notification bar, but the computer is always unautorised, and I believe there is a problem in displaying the authorisation RSA popup. Never show this popup in android Q !!!
No problem with android 9 I see the autorisation popup and ADB work correctly.
But with android 10, there is no popup for authorisation ! --> the computer is alwas unauthorized .
I try a lot Android Q rom (system-roar-arm64-aonly-floss.img, caos-v224-201029-arm64-avN.img, Havoc-OS-v3.8-20200821-Official-arm64, RROS-Q-8.6.4-20201111-mido-Official) all have the same problem. No popup for ADB authorisation.
I reinstall android 9 (AOSP Extended) and no problem !!!! All is working correctly.
- I always wipe all partitions with mido flash_all or flash_factory, every time I flash a new ROM. (I can do it more because there is no important data for the time)
- On computer I restart and remove adbpub keys also without result.
What can I do more ? Any idea ? (I cannot debug the local debuger without adb )
Thanks
Click to expand...
Click to collapse
Very interesting. I don't remember to have this issue on my previous A10 roms, which were CrDroid and DerpFest. However, just two days ago I switched to official Resurrection Remix and I didn't have the need to grant ADB permission yet. So when I saw your post, I searched for cable and tested ADB, and yes - no popup at all! It might suggest the issue is yet ROM/source-related and you just had a bad luck
The solution I found after searching a while on XDA:
[SOLVED] ADB 'unauthorized', no RSA prompt, and no 'Revoke USB debugging' option
After fighting with this for nearly a month and reading dozens of threads on xda, stack-overflow, etc... I finally figured out this issue, so I'm putting it here in hopes it saves someone else the frustration. The issue presented itself on my...
forum.xda-developers.com
Just tried and worked. No popup, but device is authorized now.
Yes !!! it's working with PC !! thanks
Effectively I think it's a regression in adb source.
Now I must find the public key of the mido itself because I use applications that work in loopback network ADB in order to monitor RUN_IN_BACKGROUD permission and BOOTUP permission.
File transfer to pc (windows 10) doesn't work with android 11 based rom (Only sounds when connect usb cable to pc and click on file tranfer option in usb preference in phone but Device doesn't show in windows file explorer). When I select file transfer in usb preference. It doesn't work, but other option in usb preference like ptp, usb tethering, charging work.
I reverted back to android 10 and checked, it again worked. Then I again flashed this Rom but file transfer with usb doesn't work.
I think it is a problem or bug with android 11.
If any guy has it's solution, plz tell.
mahadev111 said:
File transfer to pc (windows 10) doesn't work with android 11 based rom (Only sounds when connect usb cable to pc and click on file tranfer option in usb preference in phone but Device doesn't show in windows file explorer). When I select file transfer in usb preference. It doesn't work, but other option in usb preference like ptp, usb tethering, charging work.
I reverted back to android 10 and checked, it again worked. Then I again flashed this Rom but file transfer with usb doesn't work.
I think it is a problem or bug with android 11.
If any guy has it's solution, plz tell.
Click to expand...
Click to collapse
Had a similer issue with multiple A11 roms , but tried DotOS 5.2 based on A11 , and it works fine .
* charing speed is back to 1.4 A was 0.5 on Lineage OS .
* USB transfer works as usual .
_
- GPS is bad , not fixing at all
- drainage a little over 20% overnight
- a bit laggy for my taste.
_
~ recommended if u want A11, else stick with A10
link : https://www.droidontime.com/devices/mido
stick with the gapps version for peace of mind
Hello, I'm facing this problem from many years in my phone, i can't plug in my mate 10 to any pc, it always says usb not recognized,
all drivers installed correcly with hisuite , my cable usb is new,
i changed today the USB charging port of the phone at Huawei care service, and i reset factory the phone , still same problem.
I'm still having the same stock rom on the device,
is the "usb not recognized" problem can be a software problem in the phone? thank you for your experience.
chahine21 said:
Hello, I'm facing this problem from many years in my phone, i can't plug in my mate 10 to any pc, it always says usb not recognized
Click to expand...
Click to collapse
I'll try to help you but I'm not an expert, and yet I've had EVERY problem you seem to be speaking about.
a. I have had broken USB ports
b. I have had broken USB cables
c. I have had the USB drivers not install on Windows
etc.
Given I've had some of the same problems, I feel for you, so my first advice is to simply give up on USB for everything that you can.
Specifically, if you can turn on USB debugging and Wireless debugging in the Developer options, you can operate the phone over Wi-Fi using the Windows monitor, keyboard and mouse as shown in my screenshots below.
You don't need anything installed on Android to use these FOSS solutions on Windows to operate the entire phone over Wi-Fi as of Android 12 (which eliminated the need for an initial USB connection to establish the Wi-Fi connection).
In summary, I have had similar problems with USB where I've given up on USB and switched to operating Android over Wi-Fi and even mounting the entire Android file system as a Windows drive letter over Wi-Fi using free software.
a. adb
b. scrcpy
c. vysor
d. webdav
Use Windows Event Viewer to check for error messages on the PC.
If the problem is the PC it will likely show up there and give you more troubleshooting clues.
Thread closed at OP's request.