• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

[ROM][UNOFFICAL]LineageOS 13 6/11/2017

This log is specific to my camera, I have the imx111 but in the log it only shows stuff for the imx219, for example:
Code: 
02-26 15:03:41.538 E/mm-camera-sensor(  991): eeprom_load_library:1017 eeprom_load_library lib_name libmmcamera_imx219_eeprom.so

Code: 
C:\Windows\System32>adb ls /sys/bus/i2c/drivers
000041ed 00000000 58b34527 .
000041ed 00000000 58b34527 ..
000041ed 00000000 58b34527 touch_atmel
000041ed 00000000 58b34527 tabla-i2c-core
000041ed 00000000 58b34527 ir-kbd-i2c
000041ed 00000000 58b34527 dummy
000041ed 00000000 58b34527 pn544
000041ed 00000000 58b34527 msm_proxy
000041ed 00000000 58b34527 apds9130
000041ed 00000000 58b34527 bma2x2
000041ed 00000000 58b34527 bmg160
000041ed 00000000 58b34527 camera
000041ed 00000000 58b34527 bmm050
000041ed 00000000 58b34527 imx111
000041ed 00000000 58b34527 lp5521
000041ed 00000000 58b34527 msm_eeprom
000041ed 00000000 58b34527 lge_ts_misc
000041ed 00000000 58b34527 touch_melfas
000041ed 00000000 58b34527 wcd9xxx-i2c-core

I don't know if it has anything to do with the other issues in the log or not but hopefully it helps.
 

Attachments

Everything works fine for me on my volt except the most important part.

Why does Google dialer crash my volt now? I can't make or receive calls. There is no dialog to make it a default dialer and there is no setting in apps to make it a default and if I clear all defaults it still never asks to be the default. Even installing third party dialers never ask to be made default.

This ROM is essentially useless to me like this.

Update: After trying a few more dialer apps, drupe dialer set the defaults for me now all is well.
 
Last edited:
stygianumbra said:
Everything works fine for me on my volt except the most important part.

Why does Google dialer crash my volt now? I can't make or receive calls. There is no dialog to make it a default dialer and there is no setting in apps to make it a default and if I clear all defaults it still never asks to be the default. Even installing third party dialers never ask to be made default.

This ROM is essentially useless to me like this.
Click to expand...

What Google dialer? From the Google voice app? The hangouts dialer? The Google dialer only works on Nexus or pixel phones.
 
I said I would do this and I am a man of my word. Sorry it took so long guys but better late than never right? We are going to have to see if lineage os 14 for the w7 or any of the other msm8x26 devices has quickremote support yet and ill work on getting that working too once lineage os 14 builds start rolling eventually.

We cant use the nice fancy zip that the other msm8x26 devices get to use because their bootloaders are unlocked and they dont need bump. We need bump, and I feel its a waste of time trying to incorporate it into the zip. So heres the method:

spock1104: in init.qcom.rc inside your ramdisk, just incorporate this into your device tree:

CHANGE THIS:

export LD_SHIM_LIBS /system/vendor/lib/libmmqjpeg_codec.so|libboringssl-compat.so

TO THIS:

export LD_SHIM_LIBS /system/vendor/lib/libmmqjpeg_codec.so|libboringssl-compat.so:/system/lib/libirrc.so|liblgir.so

ADD THIS:

chmod 0660 /dev/msm_IRRC_pcm_dec
chown system audio /dev/msm_IRRC_pcm_dec

RIGHT UNDER THIS:

#Create NETMGR daemon socket area
mkdir /dev/socket/netmgr 0750 radio radio

AND ADD THIS:

service irrcServer /system/bin/irrcServer
class main
user audio
group audio system
onrestart restart irrcServer

RIGHT UNDER THIS:

on property:init.svc.brcm_hwaddrs=stopped
chmod 644 /data/misc/wifi/config
chmod 644 /data/misc/bdaddr
start brcm_hwaddrs2

then post the x5irblasterfix.zip in your op and tell users to flash it if they want ir blaster support on par with the other msm8x26 devices in the lg family.

link to zip: https://www.androidfilehost.com/?fid=673368273298934792

NOTE: if you guys want support for the latest build from spock until he incorporates the above into the device tree, here it is. use twrp to flash the boot image onto the boot partition and then flash the zip right above this and you should be good to go. DO NOT USE THIS ANYMORE ONCE SPOCK POSTS A NEW BUILD UNLESS HE TELLS YOU ITS OK TO FLASH!!!!!!!!!!!

link to boot image based off current 02/19/2017 build for ir blaster: https://www.androidfilehost.com/?fid=745425885120711513

I tested the above and it works. No I cant add more tv devices or satellite box devices or etc etc, but maybe with some google-fu and some time one of you fine forum goers can!
 
whoshotjr2006 said:
I said I would do this and I am a man of my word. Sorry it took so long guys but better late than never right? We are going to have to see if lineage os 14 for the w7 or any of the other msm8x26 devices has quickremote support yet and ill work on getting that working too once lineage os 14 builds start rolling eventually.

We cant use the nice fancy zip that the other msm8x26 devices get to use because their bootloaders are unlocked and they dont need bump. We need bump, and I feel its a waste of time trying to incorporate it into the zip. So heres the method:

spock1104: in init.qcom.rc inside your ramdisk, just incorporate this into your device tree:

CHANGE THIS:

export LD_SHIM_LIBS /system/vendor/lib/libmmqjpeg_codec.so|libboringssl-compat.so

TO THIS:

export LD_SHIM_LIBS /system/vendor/lib/libmmqjpeg_codec.so|libboringssl-compat.so:/system/lib/libirrc.so|liblgir.so

ADD THIS:

chmod 0660 /dev/msm_IRRC_pcm_dec
chown system audio /dev/msm_IRRC_pcm_dec

RIGHT UNDER THIS:

#Create NETMGR daemon socket area
mkdir /dev/socket/netmgr 0750 radio radio

AND ADD THIS:

service irrcServer /system/bin/irrcServer
class main
user audio
group audio system
onrestart restart irrcServer

RIGHT UNDER THIS:

on property:init.svc.brcm_hwaddrs=stopped
chmod 644 /data/misc/wifi/config
chmod 644 /data/misc/bdaddr
start brcm_hwaddrs2

then post the x5irblasterfix.zip in your op and tell users to flash it if they want ir blaster support on par with the other msm8x26 devices in the lg family.

link to zip: https://www.androidfilehost.com/?fid=673368273298934792

NOTE: if you guys want support for the latest build from spock until he incorporates the above into the device tree, here it is. use twrp to flash the boot image onto the boot partition and then flash the zip right above this and you should be good to go. DO NOT USE THIS ANYMORE ONCE SPOCK POSTS A NEW BUILD UNLESS HE TELLS YOU ITS OK TO FLASH!!!!!!!!!!!

link to boot image based off current 02/19/2017 build for ir blaster: https://www.androidfilehost.com/?fid=745425885120711513

I tested the above and it works. No I cant add more tv devices or satellite box devices or etc etc, but maybe with some google-fu and some time one of you fine forum goers can!
Click to expand...
Thank you! I'll have to see if there's a way to script this.

Or maybe just integrate it minus the APKs so Lineage doesn't get in trouble if/when our builds are integrated.
 
spock1104 said:
Thank you! I'll have to see if there's a way to script this.

Or maybe just integrate it minus the APKs so Lineage doesn't get in trouble if/when our builds are integrated.
Click to expand...

Yeah I'd say just make the changes in init.qcom.rc and call it good on your ROM building end. Lineage should be OK with the text links to libraries as long as the actual libraries and binaries aren't part of the ROM zip so they don't have to claim any liability, and that's what the x5irblasterfix.zip is for so you can just offer it separately for users to download if they so choose. Just make sure to give credit to the original uploader of the zip whoever it was, can't think of it off the top of my head right now but I remember giving a link to the original zip somewhere in the old rom thread.

Edit: I think the ROM will still boot with that in init.qcom.rc without the zip being flashed, but don't quote me on it. Forgot to test that and I had to leave my volt and dev machine for the night so if someone wants to try to just clean flash the newest ROM and the boot image I posted without flashing the qremote zip and see if it boots normally that would be amazing.
 
Last edited:
ShapeShifter499 said:
@whoshotjr2006 whoa hey!

Is camera working for you on LineageOS 14.1? Or have you gotten it to work? I've been running a few builds myself and it fails to work. Black screen on camera app.
Click to expand...

heyo! lol

i havnt synced the source yet. ive been working on lineage 13 for the g stylo and almost have it booting with gps/location services and powerhal being my major issues but im close to resolving those. i figure ill sync los 14 once i get 13 finished and ill hop in with you guys.
 
habibie said:
Unless I can get the latest version Android OS for my LG KoT49I.LS740ZV6 phone, I just wanted save me some steps to replace the original Android OS with the LineageOS.
Click to expand...
Okay, I don't think you understand. To flash a ROM u have to have TWRP installed. And since you didn't do that... Follow the brick guide and get your phone working. Then install TWRP and then flash linageOS
 
Loving the ROM after taking the plunge. It actually works well. And even works well with OTG. You all are amazing with this insane progress.
 
Ok so if your Volt is overheating, enabling one of two thermal options built into Kernel Auditor may help to give your Volt a better CPU operating temperature under load. There is the Core Control setting and the SoC temperature limit toggle. I'm currently stress testing the Core Control setting under a 15 minute stress test. I'll try the SoC temperature limit toggle setting next with the same 15 minute stress test and post my results. I had them both enabled at the same time without knowing doing so could potentially cause "unexpected behavior" according to a warning that Kernel Auditor has on the 2nd Page of the Thermal setting. Last night my CPU temp went over 75C, but it's staying between 58C and 62C during this stress test with only Core Control enabled.

So far I'm seeing similar if not identical temps with either setting enabled, but I'm not getting anywhere close to the highest temp I hit last night just watching a video. Think I'm going to stick with SoC temperature limit toggle enabled now because I think it may be best for performance. It seems to be a better setting for multi-tasking because it utilizes all the cores more often, but honestly that's just a guess... Hell, I dunno what I'm talking about....Don't judge me. LOL!!!

Still having WiFi issues....
 
Last edited:
spock1104 said:
The wifi issues are being caused by a kernel issue. I Just need to work out the exact cause.
Click to expand...

Ok, I'm not sure what the average time is before the kernel starts causing wifi issues, or how random the issue is, but it's worth mentioning that depending on what settings I've applied on my repeater and router configuration pages there's a noticeable difference in how long I keep my wifi signal before it drops out. Some settings work way better than others, and sometimes the signal on my Volt lasts to the same extent that my other devices hold their wifi signals too, which is for many hours at a time.
 
Last edited:
JoshD said:
I've been having the issue since installing cm13 & still having it on the 2/19 build of Lineage.
Click to expand...
my main ish.... its constant bt, wifi, and LTE glitches. Other than that... i love it. Hoping one day this gets updated. Thank you all for pushing forward.
 
SykkNyzz said:
my main ish.... its constant bt, wifi, and LTE glitches. Other than that... i love it. Hoping one day this gets updated. Thank you all for pushing forward.
Click to expand...
Wifi Hotspot is the sordid culprit for some reason. It resets after some time.
 
Ok guys, sorry that the last ROM turned into a turd. I finally had a chance this weekend to poke around and made some adjustments. I'd like some feedback on this one before I say it's good to go, but it's been OK throughout the afternoon for me. The previous ROM was so bad my phone was rebooting every few hours.

http://www.mediafire.com/file/7tjlmu36hgxqk76/lineage-13.0-20170326-UNOFFICIAL-x5.zip
MD5: E55D2B121646FB3089099717D55EFB41
 
You must log in or register to reply here.
Back
Top Bottom