Not sure if this is LOS 20 related, but my FP4 isn’t detected in File Transfer mode no matter the computer I plug it on.
Definitely not a driver issue, as I’ve tested it on 4 different computers that do see my 2 others devices.
Funny thing is I can run adb/fastboot commands without any issue.
Photo storage mode is also working.
It appears really only File Transfer mode is somehow broken. I think this has appeared since I updated from LOS 19 to 20 but can’t be 100% sure as I do not use this mode very often. Anyone else experiencing this ?
I assume you’re referring to microG Service Core? If so, yeah, I did. Aside from that, I also added FakeStore. SafetyNet check still yields CTS profile mismatch, unfortunately. I’ll try a few other options, though I might just end up switching to NikGApps.
I had the same issue happen to me recently; disabling USB debugging seems to have helped. Though this only occured once, on my Windows boot, where I haven’t enabled USB debugging since. On Linux it appears to mount properly either way.
Edit #1: Just tested it on a different machine running Windows. Results in the exact situation you described, with PTP working and file transfer (MTP) being broken. It seems Windows does not recognize the device as an MTP source when in ADB+MTP mode for some reason.
Edit #2: It seems it was a driver issue after all. When USB debugging and MTP are enabled, an unrecognized MTP device appears under “Other devices” in Device Manager with apparently no drivers available for it. To fix this, you need to select said device, and navigate to “Update driver” → “Browse my computer for drivers” → “Let me pick from a list of available drivers on my computer” → “Portable devices” → “(Standard MTP Device)” → “MTP USB Device”. Then click next and proceed against the warning. Windows should now correctly recognize your phone as an MTP device even with USB debugging enabled. As for why this occurs, I can’t really elaborate further.
This absolutely mind blowing.
How weird that multiple computers, simultaneously lose the ability to detect the device as MTP USB ?
This was so unlikely I didn’t even thought about checking the device manager. How silly of me…
Anway, thanks a lot
I wouldn’t say they lost the ability to detect it as an MTP source, rather the phone changed the USB data it reports to the computer upon connection.
the product ID for FP4 changes (from 0x4EE1 to 0x4EE2) when in ADB+MTP mode, thereby making the same USB MTP interface appear as a separate device;
additionally, in the same ADB+MTP mode, the bus driver fails to report a compatible ID of USB\MS_COMP_MTP for the MTP interface (possibly due to LOS 20 not providing enough data to Windows to classify it as such) which is required to identify the device as a viable candidate for the MTP driver (see line 37 of %SystemRoot%\System32\DriverStore\FileRepository\wpdmtp.inf_*_*\wpdmtphw.inf; INF files are used during device installation processes); or, alternatively, …
the MTP interface should have bInterfaceClass = 0x06, bInterfaceSubClass = 0x01, and bInterfaceProtocol = 0x01 (see line 38 of the same file), but in our case it has the values 0xFF, 0xFF, and 0x00, respectively.
Given the above, it seems reasonable that the MTP driver is not considered to be appropriate (since neither of the two conditions to do so are met) and the MTP interface is left untouched.
Now, to understand why the bus driver fails to report a compatible ID of USB\MS_COMP_MTP when USB debugging is enabled requires, I would imagine, at least a superficial understanding of the USB and MTP protocols, and their implementation within Windows and/or Linux. Neither of which I have, so my journey ends here.
I’m still using LOS 19, but only because I didn’t have time to update.
Since I installed LOS (on my FP4 of course), I can’t receive SMS anymore.
Does anyone have any idea what this could be due to?
Thanks a lot!
Thanks a lot for all this answers. I’ll try to re answer them all in once.
I’m not sure whether I use the phone before I installed LOS or not. Sending SMS definitely works fine. So I think it’s not about the app.
I used LOS before on all my other phone and never had any problems. @mapfeld How to check or set the number of the “SMS central”? I haven’t found anything related to that.
Using *#*#4636#*#*, you can enter the number entering the top option menu, wait a sending for the menu to load and scroll to the very bottom to the field labeled SMSC. Where this helped me earlier I just saw that I can send SMS without having anything set there.
The problem has been solved by my provider.
If this problem occurs again with someone else, here is the cause.
When I applied for the eSIM, I automatically got a contract with the Multicard option. But only one of these cards can receive SMS. The provider can set which of the cards should receive SMS.
sorry for the late reaction, I was quite busy in the last weeks.
I have the same issues with the newest build, I couldn’t update using OTA. I hadn’t the time to test flashing it manually, thanks for confirming flashing it via USB does not solve the issue. I will take the broken build offline & rebuild today.
PS: You probably discovered it already, but for others as well: You can configure your eSIM from my build.
Updated from the September 19.1 build to the current 20 build just fine. Did run into one thing which I thought I’d share: the update enabled the always-on display feature which I’d had disabled previously, and removed the toggle for it in settings (although weirdly it still shows up in search). There’s a quick settings tile called “Ambient display” that toggles it off, though.
trying to build lineageos 20 for the fp4 via the microg4lineageos docker container, i keep running into these errors near the end of the build process:
frameworks/base/services/core/java/com/android/server/pm/ComputerEngine.java:1607: error: cannot find symbol
Bundle metaData = p.getMetaData();
symbol: class Bundle
location: class ComputerEngine
frameworks/base/services/core/java/com/android/server/pm/ComputerEngine.java:1663: error: cannot find symbol
symbol: variable name
location: variable ps of type PackageStateInternal
is anyone else encountering this, and ideally could provide a fix?