LineageOS13-port-R1-HD (camera-mostly- works)

roboman2444

Member
Sep 22, 2015
28
1
0
So the camera issue is still there, even with the stock camera. The first photo after a reboot is fine, but every photo afterwards just hangs. Maybe it's related to trying to save the photo to the SD card or internal storage?


Edit: setting the storage location to SD card fixes the issue (at least in stock cm camera). Perhaps it's a permissions issue?
 
Last edited:
G

GuestK00465

Guest
Hey guys I've got a fresh install of the latest version of this, and I've noticed on my blu that the ui is laggy. I have the 2GB Prime model, I was wondering if anyone else has been having this issue.
 

RubnLee

Member
Jun 25, 2014
22
0
0
28
Bejuma
Looks great

Testing, looks awesome, the dual sim sistem works perfectly, the only thing this rom needs is the frontal camera/flash and spanish language support
:good: Good Job :good:
 
Last edited:

roboman2444

Member
Sep 22, 2015
28
1
0
So the camera issue is still there, even with the stock camera. The first photo after a reboot is fine, but every photo afterwards just hangs. Maybe it's related to trying to save the photo to the SD card or internal storage?


Edit: setting the storage location to SD card fixes the issue (at least in stock cm camera). Perhaps it's a permissions issue?
Still has trouble... saving images takes a while, or sometimes hangs the app and appears to get worse and worse over time after a reboot.
 

joedajoester

Senior Member
Aug 11, 2012
744
100
0
on tmobile im not getting VoLTE and if my phone is locked it will not ring for calls and will not notify me that i missed a call. Its a shame but i guess im going back to stock :/
 

roboman2444

Member
Sep 22, 2015
28
1
0
Still has trouble... saving images takes a while, or sometimes hangs the app and appears to get worse and worse over time after a reboot.
I think it might be related to writing the file to the camera roll... Apps that don't usually write a file to the camera roll work fine (facebook messenger, etc), but OpenCamera and "stock" snap both hang 95% of the time. Rebooting sometimes helps, but it usually only gets through 1 photo before it starts hanging again. If it does manage to save a photo, it takes a few seconds for it to work. Clearing dalvik/cache didnt help.

Can someone (who's camera works fine) post what the permissions look like for their camera save locations?
 

mrmazak

Senior Member
Jun 16, 2013
3,212
1,324
253
I think it might be related to writing the file to the camera roll... Apps that don't usually write a file to the camera roll work fine (facebook messenger, etc), but OpenCamera and "stock" snap both hang 95% of the time. Rebooting sometimes helps, but it usually only gets through 1 photo before it starts hanging again. If it does manage to save a photo, it takes a few seconds for it to work. Clearing dalvik/cache didnt help.

Can someone (who's camera works fine) post what the permissions look like for their camera save locations?
Have you been able to change save to location to the external sdcard, and has that made any difference.
 

bringy

Member
Jul 24, 2017
9
4
3
I seem to be having some trouble installing the 3.1.1-0 TWRP. I'm using the vampirefo 3.0.3-0 version.

Every time i try flashing it i get a message saying " Invalid zip file format error installing zip file"

I'm using llineage-13.0-R1-HD-Port-3.8..

Any one have any suggestions ?
 

mrmazak

Senior Member
Jun 16, 2013
3,212
1,324
253
I seem to be having some trouble installing the 3.1.1-0 TWRP. I'm using the vampirefo 3.0.3-0 version.

Every time i try flashing it i get a message saying " Invalid zip file format error installing zip file"

I'm using llineage-13.0-R1-HD-Port-3.8..

Any one have any suggestions ?
The 3.1.1 recovery zip is not a flashable zip. It is an img file in a zip. It needs to be unzipped. Then you can install it as an img.
 

roboman2444

Member
Sep 22, 2015
28
1
0
I think it might be related to writing the file to the camera roll... Apps that don't usually write a file to the camera roll work fine (facebook messenger, etc), but OpenCamera and "stock" snap both hang 95% of the time. Rebooting sometimes helps, but it usually only gets through 1 photo before it starts hanging again. If it does manage to save a photo, it takes a few seconds for it to work. Clearing dalvik/cache didnt help.

Can someone (who's camera works fine) post what the permissions look like for their camera save locations?

So here are my findings.
Just the camera roll save location. Messenger saves the photos to its own storage just fine. (/storage/emulated/0/pictures/Messenger/), even if the camera currently "isnt working"
SD card (/storage/whatever/DCIM/Camera/) SOMETIMES works, and will usually work immediately after a reboot.
local storage (/storage/emulated/0/DCIM/Camera/) has the same issue.
At this point i decided to try and delete the "Camera" directory or the DCIM directory on the SD card. Whenever i tried to do it, Amaze would crash. Local DCIM was deleted fine. This seemed very odd.

So I got a shell and checked the permissions. Everything looked ok, "drwxrwx--x root sdcard_rw" for both Facebook's save location and the DCIMs.
So I just decided to delete both DCIM directories, reboot, and try again.

At this point it seems to have fixed the issue, but i will post if it didn't.

What i think could've caused it: I did a complete wipe when first flashing this (i think it was the "v3"), but i didn't do a wipe before any updates across versions. It could possibly something in the way the camera stored the photos changed between those versions, and just needed a wipe to fix it. No idea on the specifics, but the fact that Amaze would crash whenever trying to delete the SD card DCIM directory probably has something to do with it.
 

mrmazak

Senior Member
Jun 16, 2013
3,212
1,324
253
So here are my findings.


At this point i decided to try and delete the "Camera" directory or the DCIM directory on the SD card. Whenever i tried to do it, Amaze would crash. Local DCIM was deleted fine. This seemed very odd.

So I got a shell and checked the permissions. Everything looked ok, "drwxrwx--x root sdcard_rw" for both Facebook's save location and the DCIMs.
So I just decided to delete both DCIM directories, reboot, and try again.

At this point it seems to have fixed the issue, but i will post if it didn't.

What i think could've caused it: I did a complete wipe when first flashing this (i think it was the "v3"), but i didn't do a wipe before any updates across versions. It could possibly something in the way the camera stored the photos changed between those versions, and just needed a wipe to fix it. No idea on the specifics, but the fact that Amaze would crash whenever trying to delete the SD card DCIM directory probably has something to do with it.
Thanks for the investigation. It might have been the no-wipe, but my camera on testing phone(always total clean wipe and format before fresh flash) has the camera stop issue.
I think something in my boot.img port is not right. At the moment I have reached road block on the slim-port so think I will start back on this again.
 
Last edited:

mrmazak

Senior Member
Jun 16, 2013
3,212
1,324
253
Uploaded V5.3

So far my tests show the different boot.img changes have solved camera issue. Need some more test reports.
 

ipdev

Senior Member
Feb 14, 2016
1,186
1,216
133
port V5.2.zip

I tried Camera MX, Open Camera, Google Camera, along with stock cm snap.

Camera was working fine. I had some issues with the home button and notification / pull down not working.

- This was caused by my initial setup. I used my default gapps script. (Probably webview? or maybe it was su?)

Another wipe and clean flash with just v5.2, opengapps pico only script, magisk 13.3 - Everything seems to be working so far.

Hope this helps.

Sent from my R1_HD_Port using XDA Labs

Edit :

Magisk failed to install.
 
Last edited:

mrmazak

Senior Member
Jun 16, 2013
3,212
1,324
253
port V5.2.zip

I tried Camera MX, Open Camera, Google Camera, along with stock cm snap.

Camera was working fine. I had some issues with the home button and notification / pull down not working.

- This was caused by my initial setup. I used my default gapps script. (Probably webview? or maybe it was su?)

Another wipe and clean flash with just v5.2, opengapps pico only script, magisk 13.3 - Everything seems to be working so far.

Hope this helps.

Sent from my R1_HD_Port using XDA Labs

Edit :

Magisk failed to install.

Thank you. Root is already built in. Just enable it in developers options menu.

Have you made phone calls? I have a report of the other port not working with dialer.

I had used it in the last port with FreedomPop, but that uses it's own dialer not the stock one, or Google dialer either.
 
Last edited:

ipdev

Senior Member
Feb 14, 2016
1,186
1,216
133
Have you made phone calls? I have a report of the other port not working with dialer.
I originally made a call and sent a text.

I just tried again and neither worked. I use StraightTalk for testing. (I know card and account work. Was recently working in a nexus 4 and nextbit robin.)

Had to download Carrier Services from google. Now it seems to be working.

I don't have a current 6.0 gapps script. I have a 4.4, 5.1 everything else runs 7.x. I'll try again with mostly google. (Message, Dialer, Contacts..)

Sent from my R1_HD_Port using XDA Labs

Edit :

Just noticed, it shows AT&T instead of Home on lock screen. :confused:

(Yes it is an AT&T StraightTalk card.)
 

Attachments

Last edited: