How to enable the UVC driver in Lineage OS 14.1 - G2 Q&A, Help & Troubleshooting

I need the OTG camera function, but don`t want to to back to stock. Would i have to recompile the kernel to enable it?

I just encountered the same issue while trying out my brand-new USB endoscope camera with a recent version of Lineage OS 14.1. I just wondered if you already tried to build a custom image?
Sharing some useful or not so useful bit of information. It seems that the custom-built kernel from Dorimanx for Android 4.4.2 had at least the driver source in place. *Edit* I'm not allowed to post Links just yet, sry! *Edit*
If nobody else is commenting, I will probably take the time to set up a Build-VM at the weekend and try building my first custom ROM. How hard can it be, right

daFritz84 said:
I just encountered the same issue while trying out my brand-new USB endoscope camera with a recent version of Lineage OS 14.1. I just wondered if you already tried to build a custom image?
Sharing some useful or not so useful bit of information. It seems that the custom-built kernel from Dorimanx for Android 4.4.2 had at least the driver source in place. *Edit* I'm not allowed to post Links just yet, sry! *Edit*
If nobody else is commenting, I will probably take the time to set up a Build-VM at the weekend and try building my first custom ROM. How hard can it be, right
Click to expand...
Click to collapse
Good luck, i went back to stock, really miss the snappiness of los.

Related

USB Device (Flir One) not detected on any MM-rom

I recently bought a FLIR ONE thermal imaging camera. Unfortunately, the device is not detected on my D802 using any marshmallow ROM.
I was using Resurrection Remix rom, but also tried Paranoid, XOSP, Dirty Unicorns, AICP, .... with no luck. Also, flashing Dorimanx and Lambda kernel didn't help.
When I run Chainfire USB Host Diagnostics, it says the kernel supports it, but OS does not.
On Lollipop (stock-based) roms, there is no issue, and the device is detected.
Can someone explain why the marshmallow ROMs miss this support. Is there any way to get this working ? I'm now running a LP rom again, just to be able to use the cam, but it really feels like a downgrade.
Same here, did you manage to fix it?
tehsYs said:
Same here, did you manage to fix it?
Click to expand...
Click to collapse
No fix other than going to stock based ROM or other phone.
All mm/aosp/caf roms are using a generic otg driver that breaks support for usb host intent filters. In other words, the phone won't broadcast to applications the a usb otg device has been plugged in.
It's not just your device in question, any device other than flash storage doesn't get detected. A developer could probably fix this but as it is broken in all non-stock roms it would probably be challenging to fix.
I do android development Mostly for the droid turbo, apps and tweaks. I think i may be able to help out here.
I did manage to get flir one working on none stock rom last night. It worked fine on stock. Then i seen this post installed cm and no joy. So after a bit of tweaking i did get it to work. I will see if i can come up with some kind of Universal patch for all users.
I will try and post a how to video to get it working on non stock roms. I am going to pull out some other phones to see if the patch works on all phones.
Keep an eye on my youtube channel http://www.youtube.com/iphostway/videos
I will work on a Universal fix starting today.
computerfreek274 said:
I do android development Mostly for the droid turbo, apps and tweaks. I think i may be able to help out here.
I did manage to get flir one working on none stock rom last night. It worked fine on stock. Then i seen this post installed cm and no joy. So after a bit of tweaking i did get it to work. I will see if i can come up with some kind of Universal patch for all users.
I will try and post a how to video to get it working on non stock roms. I am going to pull out some other phones to see if the patch works on all phones.
Keep an eye on my youtube channel http://www.youtube.com/iphostway/videos
I will work on a Universal fix starting today.
Click to expand...
Click to collapse
That would be really cool
If I can help testing your fix, please let me know.

How to build AOSP for Motorola devices?

I am having trouble finding decent instructions for getting the sources for a standard build for Motorola devices, specifically for athene.
I have built for Freescale products before and it usually involves some combination of repo init and patches, but that doesn't seem to be the case for Motorola.
I know the kernel and other sources are available on Github (https://github.com/MotorolaMobilityLL), but I don't see a manifest repository there. Nor can I find a device repo.
The closest thing to instructions I found was this readme (https://github.com/MotorolaMobilityLLC/readme/blob/master/MMI-MPJ24.139-23.4.txt) (xda wont let me post links, I'm too new a user here).
I am starting to suspect that Motorola is being as lazy as possible and only fulfilling the bare minimum of open source obligations, and thus doesn't provide a device repo, or manifest repo, etc.
Is that the case? I am new to running builds for standard phone manufacturers - are ROM developers around here forced to do legwork filling in what the manufacturers refuse to publish?
Or am I just missing the rest of the instructions from somewhere?
I have the same issue, did you ever manage to successfully complete a build? Thanks.
TheGreatCabbage said:
I have the same issue, did you ever manage to successfully complete a build? Thanks.
Click to expand...
Click to collapse
Nope, my impression of the situation remains the same, though I have not re-investigated. I would like if someone more knowledgeable confirmed though.
It is a shame, as I would really like a "known good" base to work off of and put in root support and remove unnecessary softwares in a legitimate way.
You *can* build LineageOS for athene: (https://wiki.lineageos.org/devices/athene/build)
I ran LineageOS for several months, but eventually switched back to stock. Has some strange issues in regards to texting (seems to only work when making a call).
Thanks for your reply. I've just managed to build Lineage OS for my device, and it seems to work ok.
I was previously using Resurrection Remix OS (which I didn't build, just downloaded a zip) and it worked very well, so if I have any issues with Lineage then I'll try to restore my TWRP backup of RR.
I wish I could use the AOSP codebase directly, though...

TLS Wifi login problems -- Cloudpath

Hey guys,
I'm just looking for someone to point me in the right direction. Basically, my school has this web portal logon thing called Cloudpath (formerly xpressconnect) that requires you to log on to the portal's network in order to follow the instructions in your web browser for your specific OS. The problem arises with Android. It requires you to download an app, which does all the nitty gritty certificate installation and configuration for you. However, whenever I try this on a CUSTOM ROM (LOS-based and DU), I end up in a connecting loop. I never get connected to the secured network even though the certs appear to be installed correctly. I've tried using the app and doing it manually by downloading the certs myself. This only occurs on custom nougat roms, but works on stock MM (I haven't tried MM roms, because I want nougat).
As far as I know this problem only affects this phone after I install the rom and OpenGapps. Some of my peers have LOS and have gotten it to work, so I'm the only one, and the tech staff have no idea what to do. I don't have the log file on me, but if you need it, I can post it (they're pretty long, but seem to be detailed up until the connection part which just flops between CONNECTED and DISCONNECTED).
Is this a problem with the modem or the roms themselves? I was going to wait until the nougat kernel blobs got integrated to LOS, before trying again as I don't want to use the experimental build because it's a month old now. This problem has been around since at least January of this year. If there is a non-los based nougat rom, I would be glad to try that too. otherwise, I'm at a loss and I need some direction.
Any help is appreciated!
Seeings as how all of our Nougat ROMs are a mixed bag of partial MM and part Nougat still, and all custom ROM's for the MXPE use LoS's device tree, I am thinking this is a ROM issue, probably with some binary blob we don't have yet. The kernel source just released a few weeks ago, give it time and custom ROM's will get better (we think), and if the MXPE ever gets official Nougat, we will probably have better binary blobs too.
If it works on stock Marshmallow, it obviously isn't a radio thing, because your Nougat ROM's use the same radio firmware.
I don't have much else to say, but I would try a custom Marshmallow ROM and see if it works... if it fails as well, the problem is something in the LoS core device tree and it will need some developer's special attention (good luck with that, since we are considered to have a stable device tree it takes some work to get it changed), but if it works, chances are good that once custom Nougat ROMs get updated more it will likely work.
In a last ditch effort. I tried flashing the experimental build after posting this article, and it actually works! Now, this isn't the ideal situation given that there are some bugs (that I haven't run into yet) and that this build is a month old now. But for now, I'm satisfied. I just hope these blobs get integrated to official LOS soon.
Progress on that is here: https://review.lineageos.org/#/q/project:LineageOS/android_device_motorola_clark
If there are any roms out there that are considered stable and have these implemented now, I would appreciate it, otherwise, I think I'll be set for a little while. Thanks for your help!

LineageOS on Xperia X Compact?

Hi there,
does anyone know a working version of LineageOS (V14.X) for our Xperia X Compact?
The last version i´ve found is not updated since April:
https://forum.xda-developers.com/x-compact/help/rom-lineageos-14-1-sonylos-7-1-binaries-t3584504
Is there a newer Version?
Kind regards,
Chris
I cannot find any either, but Omni has a working rom with official weeklies, you can maybe try that.
Edit: It's more like a monthly, though. Last build is from Nov. 20
I'm not a developer, but I've made an attempt yesterday to build LineageOS. After several build errors (and dirty (possibly horribly wrong) hacks to circumvent them), the build completed but I was unable to successfully boot the resulting zipfile (it bootloops every couple of seconds). I then flashed the kernel (boot.img) from the older LineageOS-rom that is shared on androidfilehost, and I was able to boot the rom but the simcard isn't detected, so the rom is basically useless...
It is sad that there are no people out there that can maintain a weekly build for LineageOS. If an inexperienced builder like me can build and boot a rom it really shouldn't be that hard to improve the build.
Coirpre said:
I cannot find any either, but Omni has a working rom with official weeklies, you can maybe try that.
Edit: It's more like a monthly, though. Last build is from Nov. 20
Click to expand...
Click to collapse
Thanks! Could you say anything about the differences between Lineage and Omni? Omni's website is extremely sparse - no main point of differentiation, no feature list, no installation instructions - nothing. All it says is, it's AOSP "enriched", but not how. Their wiki link goes to a github page with a Code of conduct and a License Agreement - not very useful either.
Just noticed this - https://www.lineageosroms.org/forums/forum/sony/xperia-x-compact-kugo-f5321/
Plus AOSP Oreo - https://androidfilehost.com/?fid=817906626617948176
lineageosroms.org
lineageosroms.org
any more infos about that site?
looks quite impressive with the ammount of unofficial devices.
@Tom Mix: Looks to me like a lot of pointless clicking without any actual roms being offered. Seems like a scam (although I cant figure out their revenue model)

Rom request (Dot OS)

Hello, i was in the process of finding out how to compile Dot OS rom to share here but realized that my my computer isnt strong enough to do so. Is there anyone willing to compile the rom for those of us who would like to use it? please and thanks. Also, if asking for a rom is in violation of anything please remove this post ;D
That would be great
I am actually planning to do a personal build of DotOS, if I succeed I will share it. (this only depends on my internet connection - which is slow: I will probably buy a VPS to do so).
That great yes
I didn't see this beforehand but I'm actually compiling a build of Dot-OS 2.4 based on 8.1 oreo Right now.
By all means, if someone was planning on maintaining unofficial builds be my guest. Still, I'll post my build on this comment when it's done in an hour or so.. Made with los tree, kernel and muppets vendor.
edit: I removed my build because of some issues with system overlays
AnierinB said:
I didn't see this beforehand but I'm actually compiling a build of Dot-OS 2.4 based on 8.1 oreo Right now.
By all means, if someone was planning on maintaining unofficial builds be my guest. Still, I'll post my build on this comment when it's done in an hour or so.. Made with los tree, kernel and muppets vendor.
edit: well here is my build based on the mentioned sources https://androidfilehost.com/?w=files&flid=279723
Click to expand...
Click to collapse
I actually wasn't planning to maintain it, you are free to do so. I successfully built my own version as well, but I have some issues with DotUICenter - basically the overlays do not work.
I am trying to download your build but AFH has a temporary mirror and it's extremely slow (60 to 80KB/s). Do the overlays work on your build?
Hello Any news about rom thanks
jet-27 said:
Hello Any news about rom thanks
Click to expand...
Click to collapse
Well I've personally discontinued work due to some overlay issues that I don't have the time to look into and fix.

Categories

Resources