[ROM] [OFFICIAL] LineageOS 17.1 for Oneplus2 | Android 10

Search This thread

MuRF2

New member
Sep 21, 2020
3
0
I can confirm that this solves the bootloop.
After that I run into the problem of "Google keeps stopping" though.
Dirty-flashing (LOS+GAPPS) did not solve the problem.

Any advice?

If you reinstall all google apps like gmail, this error should go away.
 

Johannes1098

Senior Member
Jul 19, 2017
158
177
Update to 20210213 went fine. I wiped /system complete. Installed LOS.zip, OpenGapps.zip and Magisk.zip and wiped cache & dalvik cache.

Will test if the camera memory leak is gone..

What camera app do you use? Stock LOS quality isn't that good in my opinion.
Is there a GCAM Mod oder OOS Mod for OP2? Tried some GCAM Mods for OP3 but that didn't work very wel..

What camera app do you use?
 

Johannes1098

Senior Member
Jul 19, 2017
158
177
Anyone tested?
Yeah it seems working.. But it only appeared some time so there could be also a chance that it just didn't appear yet.. but I hope the best and that it's fixed with your merges.

I'll report if the problem reappears.

but thank you.. :)

Another problem I found: Sound/loudspeaker sometimes doesn't work after plugging in headphones and out. I think we already had this problem some time ago but I don't remember exactly..
 

mike125a

New member
May 16, 2017
3
0
Anyone tested?

I have tested it today and the issue still persists. Build lineage-17.1-20210213 clean flash without gapps.
Default camera settings (1080p). After starting video recording through the default camera app it records for ~15-20 minutes and then freezes. After closing the camera app and reopening it, I can see a camera preview for ~0.3-0.5 sec, and then it freezes again. Issue persists till reboot

Logs(the first crash - camera was running for ~10 minutes already):

Logs(reopening camera after freeze):

I had to trim logs due to pastebin limit but should you need logs since system boot I can upload them to mega or somewhere else.
 

Johannes1098

Senior Member
Jul 19, 2017
158
177
I have tested it today and the issue still persists. Build lineage-17.1-20210213 clean flash without gapps.
Default camera settings (1080p). After starting video recording through the default camera app it records for ~15-20 minutes and then freezes. After closing the camera app and reopening it, I can see a camera preview for ~0.3-0.5 sec, and then it freezes again. Issue persists till reboot

Logs(the first crash - camera was running for ~10 minutes already):

Logs(reopening camera after freeze):

I had to trim logs due to pastebin limit but should you need logs since system boot I can upload them to mega or somewhere else.
Hmm, this is the other issue.

I thought that we tried to fix the thing, that the camera is crashing random. And not only after a longer period of filming..
So my main problem was: Camera is crashing, for example if taken one photo. Which camera app doesn't matter. And then it says: Service is not available till a reboot.

But sure, there was / is this other issue that you described..

I'm now not really sure for what the fix was for.. hmm
 
  • Like
Reactions: Jakic007

mike125a

New member
May 16, 2017
3
0
Hmm, this is the other issue.

I thought that we tried to fix the thing, that the camera is crashing random. And not only after a longer period of filming..
So my main problem was: Camera is crashing, for example if taken one photo. Which camera app doesn't matter. And then it says: Service is not available till a reboot.

But sure, there was / is this other issue that you described..

I'm now not really sure for what the fix was for.. hmm

Hmm... I've only seen comments regarding the video calls/recording camera freeze (whats app/camera app)
so I assumed that was the issue to be fixed with the patch. In addition to that, we got some new error messages after recent changes - I haven't seen "ioctl() failed" before

Code:
02-19 18:21:35.324  4826  8615 E QCamera3Channel: request: On-the-fly buffer registration failed -12
02-19 18:21:35.324  4826  8615 E QCamera3HWI: processCaptureRequest: request failed
02-19 18:21:35.334   716  8592 E mm-camera: v4l2 ioctl() failed. rc:-1, trans_code:-11, stream_id=3
02-19 18:21:35.334   716  8592 E mm-camera: retry=0
02-19 18:21:35.338   716  8592 E mm-camera: v4l2 ioctl() failed. retry=0
02-19 18:21:35.338   716  8592 E mm-camera: retry=1
02-19 18:21:35.339   716  8592 E mm-camera: v4l2 ioctl() failed. retry=1
02-19 18:21:35.340   716  8592 E mm-camera: retry=2
02-19 18:21:35.341   716  8592 E mm-camera: v4l2 ioctl() failed. retry=2
02-19 18:21:35.341   716  8592 E mm-camera: retry=3
02-19 18:21:35.342   716  8592 E mm-camera: v4l2 ioctl() failed. retry=3
02-19 18:21:35.342   716  8592 E mm-camera: retry=4
02-19 18:21:35.343   716  8592 E mm-camera: v4l2 ioctl() failed. retry=4
02-19 18:21:35.344   716  8592 E mm-camera: drop this frame
02-19 18:21:35.344   716  8592 E mm-camera: drop this frame
02-19 18:21:35.344   716  8592 E mm-camera: cpp_thread_handle_process_buf_event:325, dropped frame id=32505 identity=0x20003
02-19 18:21:35.348  4826  8767 E QCamera3HWI: translateFromHalMetadata: Invalid CAC camera parameter: 1065340927
02-19 18:21:35.356  4826  8615 E Parcel  : fcntl(F_DUPFD_CLOEXEC) failed in Parcel::read, i is 0, fds[i] is -1, fd_count is 1, error: Too many open files
02-19 18:21:35.357  4826  8615 E Camera3-OutputStream: getBufferLockedCommon: Stream 3: Can't dequeue next output buffer: Invalid argument (-22)
02-19 18:21:35.357  4826  8615 W Camera2Client: notifyError: Received recoverable error 3 from HAL - ignoring, requestId 20000010
 

Johannes1098

Senior Member
Jul 19, 2017
158
177
Hmm... I've only seen comments regarding the video calls/recording camera freeze (whats app/camera app)
so I assumed that was the issue to be fixed with the patch. In addition to that, we got some new error messages after recent changes - I haven't seen "ioctl() failed" before
Yeah, and maybe it's also the same problem, and only appears at different using cases. (general camera issue, not only after filming x minutes..)

Code:
02-19 18:21:35.324  4826  8615 E QCamera3Channel: request: On-the-fly buffer registration failed -12
02-19 18:21:35.324  4826  8615 E QCamera3HWI: processCaptureRequest: request failed
02-19 18:21:35.334   716  8592 E mm-camera: v4l2 ioctl() failed. rc:-1, trans_code:-11, stream_id=3
02-19 18:21:35.334   716  8592 E mm-camera: retry=0
02-19 18:21:35.338   716  8592 E mm-camera: v4l2 ioctl() failed. retry=0
02-19 18:21:35.338   716  8592 E mm-camera: retry=1
02-19 18:21:35.339   716  8592 E mm-camera: v4l2 ioctl() failed. retry=1
02-19 18:21:35.340   716  8592 E mm-camera: retry=2
02-19 18:21:35.341   716  8592 E mm-camera: v4l2 ioctl() failed. retry=2
02-19 18:21:35.341   716  8592 E mm-camera: retry=3
02-19 18:21:35.342   716  8592 E mm-camera: v4l2 ioctl() failed. retry=3
02-19 18:21:35.342   716  8592 E mm-camera: retry=4
02-19 18:21:35.343   716  8592 E mm-camera: v4l2 ioctl() failed. retry=4
02-19 18:21:35.344   716  8592 E mm-camera: drop this frame
02-19 18:21:35.344   716  8592 E mm-camera: drop this frame
02-19 18:21:35.344   716  8592 E mm-camera: cpp_thread_handle_process_buf_event:325, dropped frame id=32505 identity=0x20003
02-19 18:21:35.348  4826  8767 E QCamera3HWI: translateFromHalMetadata: Invalid CAC camera parameter: 1065340927
02-19 18:21:35.356  4826  8615 E Parcel  : fcntl(F_DUPFD_CLOEXEC) failed in Parcel::read, i is 0, fds[i] is -1, fd_count is 1, error: Too many open files
02-19 18:21:35.357  4826  8615 E Camera3-OutputStream: getBufferLockedCommon: Stream 3: Can't dequeue next output buffer: Invalid argument (-22)
02-19 18:21:35.357  4826  8615 W Camera2Client: notifyError: Received recoverable error 3 from HAL - ignoring, requestId 20000010
Oh yes, also didn't see this messages before
 

AlpacaDev

Member
Aug 25, 2020
36
8
No!
I seem to have a Locked BL with this ROM installed. Has been locked for ages. As a test, I tried to flash TWRP, which failed. "Flashing not allowed" or similar popped up.
Is this normal? OTAs work fine, BTW.
IMG_20210226_013347.jpg
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    I was experiencing another bootloop today after OTA-Update.
    Flashing Gapps resolved it once again.

    Anyone else in the same situation?
    Will we have to re-flash Gapps after every update?
    1
    I can confirm Google Family Link is still having issues on LineageOS. Will crash on setup, so you can't add a supervised child account on a phone running LOS17.1.
    I thought I fixed it but it did not work. Maybe it can be fixed in another way but not sure if lineage will accept it. Let me try.
  • 33
    LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

    Instructions :
    • Download the latest build and gapps
    • Reboot to recovery
    • Flash the latest build and gapps
    • Reboot
    Downloads :
    Reporting Bugs
    • DO NOT Report bugs if you're running a custom kernel or you installed Xposed
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    • If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
    • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
    Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.

    Code:
    What is your--
    LineageOS version:
    LineageOS Download url:
    Gapps version:
     
    Did you--
    wipe:
     restore with titanium backup:
    reboot after having the issue:
     
    Are you using--
    a task killer:
    a non-stock kernel:
    other modifications:
     
    Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:

    XDA:DevDB Information
    LineageOS, ROM for the OnePlus 2

    Contributors
    aviraxp
    Source Code: [url]https://github.com/LineageOS[/URL]

    ROM OS Version: Windows 8 Mobile
    ROM Kernel: Windows Kernel 1

    Version Information
    Status: Testing

    Created 2019-09-19
    Last Updated 2019-10-08
    25
    I borrowed one oneplus2 from a friend and did the final work to make it official. Builds will be there once lineage build server is up.
    6
    I guess almost all bugs are fixed.
    5
    Because of covid-19 I cannot go back to school and my op2 is left there.
    5
    Oneplus2 is nearly stable. I am just lazy to build.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone