How does HFR mode work? No matter which resolution I choose, I am told that
I guess there are other Options to be set as well.
I guess there are other Options to be set as well.
Try again with latest magisk canaryHi, I have the same problem, in the past (including on another device on A11, Poco F1) I was always able to get it working. Here is what I attempted and that in the past at the end worked:
Maybe can this be tackled in some way by the DEVs? This was definitely working in the previous version 17.1
- Installed Viper 2.7.2.1 Magisk module, rebooted, granted SU permission.
- V4A prompted for the installation of the driver, granted, rebooted and V4A asks again. So the problem is that the installation of the driver in the system fails.
- Attempted to install Busybox in various ways (Meefik in play store, both via the app and via the Recovery zip method, and Stericson via play store, which usually works because it allows tro try system/xbin and system/bin, but this as well failed) . I am pretty sure that V4A uses Busybox in some way to install the driver so since Busybox fails to install, V4A fails to install the driver too.
- OR, Busybox is no longer required for the installation of V4A, BUT.... the fact that there is no way to install Busybox in the system has the same root cause of the failed installation of V4A driver too! So I investigated this more
- It turns out that there is no way to mount the system as RW in this version of LOS? I tried everything and it just doesn't mount as RW, so I am not wondering why both Busybox and V4A fails to install.
I never thought of this before, but you could be right. The Singularity is near....
Has anyone had a chance to look into this? Lineage camera doesn't take as good pictures as the stock oneDid anyone report issues attempting to use Google Camera during testing? This didn't happen on 17.1, but I'm having an issue where the app appears to not connect with the hardware, with the end result being the settings are unavailable and the viewfinder doesn't display anything. It's not a huge issue for me, as this no longer is my primary device and the LineageOS camera does work. But it would be nice.
I'll get you guys a logcat later if needed, but the brief look I had at it revealed an informational comment in the log regarding not being able to find a symbol in a .so file.
EDIT: Additional information. If I use the "Take a selfie" or "Take a video" long-press menus both functions work. As soon as I switch to the back camera to take a still photo the app crashes.
I'll take a look. Can you file a bug report according to wiki guide with logcat?Does anyone have Netflix working? I use a DRM Checker and it shows that this ROM (or maybe it's because of the MindTheGApps package?) doesn't have Widevine at all. So Netflix won't work - I don't even get a sign in screen, just an error. I assume this is because it can't initalise the Widevine DRM.
I did a full wipe before installing!
That's pretty much a known thing. We lack the Google processing. Use an old Google Camera if you want that. Or a newer GCam port.Has anyone had a chance to look into this? Lineage camera doesn't take as good pictures as the stock one
Does anyone have Netflix working? I use a DRM Checker and it shows that this ROM (or maybe it's because of the MindTheGApps package?) doesn't have Widevine at all. So Netflix won't work - I don't even get a sign in screen, just an error. I assume this is because it can't initalise the Widevine DRM.
I did a full wipe before installing!
Having carrier stability issue possibly due to apns config fix for giffgaff merged early April (14.04.21). Carrier issue (giffgaff ) also on official crDroid thread (7.5 update, April) posts #922 & #923.
I don't. Can you toss a log up according to the bug report page on wiki.lineageos.org?Does anyone else have back camera problems? Camera won't focus, blurry all the time. If any one has solved this problem please let me know. Love this ROM it's the best!
Give me the right APN and I'll push a fix.Having carrier stability issue possibly due to apns config fix for giffgaff merged early April (14.04.21). Carrier issue (giffgaff ) also on official crDroid thread (7.5 update, April) posts #922 & #923.
Give me the right APN and I'll push a fix.To add a bit more info to Uplander's comment above, I have a Nexus 5 and a Nexus 6, both running crDroid 7.6. I understand that crDroid is based on LOS sources.
I didn't know about the Giffgaff commit until Uplander mentioned it, but the timeline makes it look as if this was the cause of the instability.
My Nexus 6 has a Giffgaff SIM. (Giffgaff is a virtual UK network running on the larger O2 network). On crDroid 7.4 (March) mobile data was stable. 7.5 and 7.6 (April/May) have a mobile data signal which blinks in and out second by second. The same happens with LOS 18.1 10th May.
My Nexus 5 has an O2 SIM. The mobile data is stable on crDroid 7.6.
To me this indicates that the problem is with the Giffgaff component.
I'll look into it! Probably easy to fix.Running into the same issue as well even with Magisk 23.0 installed and SafetyNet checks passing. "DRM Info" doesn't show Widevine at all.
Symptoms:
1. Netflix encounters error on load.
2. Disney+ encounters error on playback start.
3. Udemy videos appear to play but have no image or audio.
4. Udemy videos within Chrome attempt to play multiple times but ultimately report a video error.
No issue with YouTube or other videos on the web so does appear to be DRM related.
Give me the right APN and I'll push a fix.For anyone having issues with giffgaff (UK carrier) instability see posts #926 & #927 on official crDroid Android 11 v7.6 Shamu thread for possible workaround.
volume matches stock, proximity sensor die after some years, possible it's getting flakey, make sure it doesn't happen on stock too.Thank you very much for this nice rom. The volume is a little low, I wonder if there is a way to raise this. however the proximity sensor does not work sometimes
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
That paper doesn't understand how any of this works, and the fact it paints /e/ in a good light really makes me question it's integrity. Plus, the chart that shows the "reporting" we do to google - none of it is correct. We do none of that - unless you install gapps - which is an aftermarket user choice.Interesting Privacy article out 6 Oct, lots on the interweb today. Android in general, and also LineageOS discussed. There is the usual tradeoff between data needed for functionality and innovation vs just revenue. The point is it could be more transparent, and give users some choices.
Full article: https://www.scss.tcd.ie/Doug.Leith/Android_privacy_report.pdf
Nope! Builds are rolling right now!I can't believe my eyes!! Thanks!!!
EDIT: Wait... is this an april fools joke? -__-
No I'm just crazy busy, it's on my to-do list albeit low atmAwesome to see the continued development!!
I assume the IMS development has been dropped? https://github.com/wavedashdoc/android_device_moto_shamu
Thank you for the tip an nudge in the right direction !!!Maybe deleting the .key files like explained here could be a workaround.
Google removed the support for our legacy hardware based hashing of passwords/pins/patterns, ..
Our wiki unfortunatly doesn't state that a wipe is needed. I'll be adding that.
Like said above maybe deleting the .key files is a workaround, but we can't make it the default install method for obvious reasons.