this post was submitted on 05 Aug 2023

21 points (95.7% liked)

Android

27546 readers

618 users here now

DROID DOES

Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.

The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:

Rules

1. All posts must be relevant to Android devices/operating system.

2. Posts cannot be illegal or NSFW material.

3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.

4. Non-whitelisted bots will be banned.

5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.

6. Memes are not allowed to be posts, but are allowed in the comments.

7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.

8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.

Community Resources:

We are Android girls*,

In our Lemmy.world.

The back is plastic,

It's fantastic.

*Well, not just girls: people of all gender identities are welcomed here.

Our Partner Communities:

[email protected]

founded 1 year ago

MODERATORS

[email protected]

Greyed out USB preferences (not a bad cable) (lemmy.sdf.org)

submitted 1 year ago by [email protected] to c/[email protected]

7 comments fedilink hide all child comments

Hey everybody,

I installed LineageOS 20 (Android 13) on an old cellphone I had lying around. It works fine, apart from an odd problem: when I connect the phone to my computer by USB, the "Charging this device via USB" notification appears but all the USB preference options are greyed out.

Data transfer works however: if I go into System > Developer options > Default USB configuration, set it to Data Transfer, unplug the USB cable and plug it back in, the options are still greyed out, but File Transfer is selected and the drive appears on the PC. So it's not the cable, and my ports or plugs don't need cleaning.

It's very inconvenient to have to enable and disable this in the Developer options each time I want to transfer a file, and I most certainly don't want to leave Data tranfer enabled all the time.

I've been looking for a solution everywhere, and it seems plenty of people have the same problem with a lot of different phones, but nobody has a solution.

Anybody knows what might be going on here? Any adb shell command I could issue to reenable what might be disabled?

top 7 comments

sorted by: hot top controversial new old

[–] [email protected] 3 points 1 year ago (1 children)

Yesterday I had to switch between 3 cables before I found one where USB transfer worked.

[–] [email protected] 2 points 1 year ago (1 children)

Data transfer does work. It's just that I can't enable it using the notification menu thing.

[–] [email protected] 2 points 1 year ago

Fair enough, hope you find a solution.

[–] [email protected] 1 points 1 year ago (1 children)

This may be a "safety" measure in the bios of the phone itself that was triggered when you flashed the rom. Can you try to flash back to stock android and see if that works? (Tho, depending on the manufacturer, that may be a bridge already burned.) Also, it could be that android 13 dropped driver support for the phone in question and no longer "officially" supports it, so some options are grayed out unless you enable them in developer options. Probably not much help for you, but that's the best I can think of.

[–] [email protected] 1 points 1 year ago

I would try it, but it took me several hours of trying just about everything to finally manage to flash this (unofficial) LineageOS ROM onto the phone, I almost bricked the phone several times until it finally worked and installed properly at some point, and I'm not sure what I did exactly to make it work.

I don't really want to ruin the installation at this point :) I'm not sure I'll be able to re-flash the stock Nokia ROM again safely, and I'm certainly not sure I'll be able to return back to LineageOS. I think I only got lucky once with that one.

But I don't need to do that: I used that phone for a very long time with the stock Nokia ROM and it worked fine.

I've been reading reports of this problem also happening in other brands of phones with the stock ROM also. Like this one for example: the guy has the problem with a stock Redmi phone and solved it by installing a custom ROM. Kind of the reverse of my experience :)

I think maybe it has something to do with latter revisions of Android: the last Nokia ROM my phone ran was Android 10. This LineageOS ROM is Android 13. I have a feeling the Android version number is the clincher here.

I thought perhaps Google in their infinite wisdom unilateraly decided to disable something useful in AOSP like they usually do, and perhaps there was some adb trick to bring the usefulness back. Hence my initial question. But come to think of it, my Fairphone 4 running CalyxOS is also Android 13 and it works perfectly fine. So maybe not...

[–] [email protected] 1 points 11 months ago (1 children)

Did you ever figure this out? I'm having the same issue trying to connect a Nokia G60 with stock Android One ROM to two macs. Though only most of the time; rarely it just works.

[–] [email protected] 2 points 11 months ago

No. Sadly I never found out why my phone is misbehaving. But this isn't my primary device: it's just a test cellphone so it doesn't matter too much to me. It would certainly be a showstopper if it was my daily driver.