• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

Official Cyanogenmod 12 Lollipop

Search This thread

malimukk

Senior Member
Aug 20, 2012
555
134
Anyone got problems with CELL STANDBY draining battery? It's not draining while screen is off, but when I'm using the phone I can not get more than 2hours screen on time with the lowest brightness and wifi on
Also signal in my area is really strong and time without signal is 0%
 

teacher77

Senior Member
Oct 6, 2009
135
11
Milan
I think that camera darkness is the real problem of lollipop roms for e975 and I don't know if it will be fixed without LG releasing any camera drivers for e975 for Lollipop...
 

vamvax

Member
Mar 3, 2010
17
2
experience with cm12

Having spent 3 days on cm12, the experience I got is with mixed emotions. The current build is not yet stable enough for the layman, however it doesn't seem to be very far from becoming. The wifi has issues connecting to certain rooters for no obvious reasons. There have been some random reboots but nothing alarming. The messaging app is not functional as it is crushing all the time. There is an issue with whatsapp and its notification pop up, while answering to messages. The Delta app for small updates for new nightlies works great. The themes section of the os is very well structured and operational. there is no fm radio app, while spirit2 is operating with very distorted sound, so I wouldn't recommend it.
The email app with exchange seems to work uninterrupted. The notification scheme is ok but needs some extra touch. The way to re obtain root took me a while to figure it out so an explanation is required at the installation process.

All in all, an experienced user can find his way for a day to day use of the os but wouldn't suggest a new user to install just yet!
 
  • Like
Reactions: franky_z

vamvax

Member
Mar 3, 2010
17
2
update on wifi

It seems that for those rooters that the phone can't connect to, if you change their settings into open access, then the phone connects with no problem.
 

Toomkee

Member
Aug 4, 2013
35
3
Im currently having issues getting a fresh install to work. I tried build 20150313 and 20150319 but everytime i come to the point after i added a CM account, even if i just skiped, i get a crash saying the setupwizard has stoped working.

Im using the e975, TWRP 2.6.3.0 (the only one that works without problems), wiped every partition and installed CM via sideload without GAPPS.
 

teacher77

Senior Member
Oct 6, 2009
135
11
Milan
Im currently having issues getting a fresh install to work. I tried build 20150313 and 20150319 but everytime i come to the point after i added a CM account, even if i just skiped, i get a crash saying the setupwizard has stoped working.

Im using the e975, TWRP 2.6.3.0 (the only one that works without problems), wiped every partition and installed CM via sideload without GAPPS.

It's a known problem. Use an older build and update!

Sent from my LG-E975 using XDA Free mobile app
 

aaa29

Senior Member
Jun 21, 2013
69
6
Roma
I have a problem with the version 20150318. The camera does not work with external app, for example with google translator. How can I fix? And how can I fix for the bug camera dark? Thank you very much.

Inviato dal mio LG-E975 utilizzando Tapatalk
 

alexisgt

Senior Member
Oct 4, 2009
165
18
Im currently having issues getting a fresh install to work. I tried build 20150313 and 20150319 but everytime i come to the point after i added a CM account, even if i just skiped, i get a crash saying the setupwizard has stoped working.

Im using the e975, TWRP 2.6.3.0 (the only one that works without problems), wiped every partition and installed CM via sideload without GAPPS.
It's a known problem. Use an older build and update!

Sent from my LG-E975 using XDA Free mobile app

Same problem here! Please help!
Which build is recommended..?
 

Leavard

Senior Member
Aug 9, 2012
130
51
Sydney
Im currently having issues getting a fresh install to work. I tried build 20150313 and 20150319 but everytime i come to the point after i added a CM account, even if i just skiped, i get a crash saying the setupwizard has stoped working.

Im using the e975, TWRP 2.6.3.0 (the only one that works without problems), wiped every partition and installed CM via sideload without GAPPS.

Use the Aroma file manager in recovery and rename /system/priv-app/SetupWizard/SetupWizard.apk to SetupWizard.apk.old

Worked for me. Took me ages to figure it out though. Was stuck at work for about two hours with no functional OS on my phone and a very security conscious IT policy (i.e. couldn't plug my phone into a pc)

Flashing without gapps doesn't help because Setup Wizard is a CM app that wraps around the normal Google Setup app and it still runs even if the Google one isn't there.

Sent from my LG-E975 using Tapatalk
 
  • Like
Reactions: ircalf

Toomkee

Member
Aug 4, 2013
35
3
Use the Aroma file manager in recovery and rename /system/priv-app/SetupWizard/SetupWizard.apk to SetupWizard.apk.old

Worked for me. Took me ages to figure it out though. Was stuck at work for about two hours with no functional OS on my phone and a very security conscious IT policy (i.e. couldn't plug my phone into a pc)

Flashing without gapps doesn't help because Setup Wizard is a CM app that wraps around the normal Google Setup app and it still runs even if the Google one isn't there.

Sent from my LG-E975 using Tapatalk

i dont even have these file locations after installing a build o_O
 

Top Liked Posts

  • There are no posts matching your filters.
  • 10
    Hello everybody,

    Currently my developing time is limited due to some graduation assignments which I need to finish for my study.
    To fix the RIL problems we're having, in my opinion and also some recognized CM developers' opinion, is to get the binary blobs (at least for the RIL) up-to-date with the KK blobs or preferably higher (mako blobs for example).
    This opinion is backed by the knowledge that for some reason the mako based geehrc builds related to the gproj build do not experience the RIL/SIM PIN bugs we are experiencing.
    The blobs which are currently in use in the Jenkins build process are still from the Jellybean release which the Optimus G was originally released with onto the market.
    In my porting process I focused on using MAKO blobs as they still get updated, unlike the official Optimus G blobs.
    With a small kernel change I was able to get a lot of mako blobs working already for the E975.
    The kernel change which need to be made is the following:
    Replace drivers/usb/misc/ks_bridge.c from the gproj kernel source with mako version of ks_bridge: ks_bridge.c
    The ks_bridge.c from mako initializes the kernel sockets ks_bridge and efs_bridge which were used in gproj under ks_hsic_bridge and efs_hsic_bridge which are the new sockets used in the mako builds.
    To initialize these sockets with the right permissions for android to work with some uevent.geehrc.rc changes are necessary as well.
    Code:
    /dev/ks_bridge              0660  system        system
    /dev/efs_bridge            0660  system        system
    [COLOR="Orange"]Needs to be replaced with:[/COLOR]
    /dev/ks_hsic_bridge              0660  system        system
    /dev/efs_hsic_bridge            0660  system        system
    This change is necessary to be able to use the mako efsks an ks binaries.
    When these changes are made the original gee efsks and ks binaries are no longer usable.
    This is no problem since the mako ks and efsks also work with the JB RIL I found out.
    In the list below I highlight in green which blobs are currently working in the e975 builds I built.
    As everybody can see still a lot of files blobs need to be made compatible but at least there is some start.
    Most of the blobs which still do not work are directly related to qmuxd
    What I know is that the following list of blobs are all RIL related. I left out libril.so and the rild binary because when possible I prefer source build rild and libril.so. For now we don't know if this is possible for as long the remaining blobs still need to be ported

    Update 1:
    Using Mako blobs apparently was a mistake. A lot of kernel stuff needs to be changed that way. Maybe in the future this will be a project I will look into, but for now I switched over to E975 V20A Kitkat blobs for porting. This porting process still involves the replacement of the file ks_bridge.c from the gproj kernel source with the ks_bridge.c from the V20A kernel source available from LG Opensource Release Center. I updated the list of blobs which are already in my current rom and still prove to deliver a rom with functioning RIL (still sim/pin bug occurring so don't ask for test builds please.). Once the project is finished I make sure it gets pushed into CM github so everybody can enjoy it.

    Binaries:

    • [*]efsks
      [*]ks
      [*]netmgrd
      [*]qcks
    • qmuxd
      [*]rmt_storage
    Libraries:

    • [*]libdiag.so
    • libDiagService.so
    • libdsi_netctrl.so
      [*]libdsutils.so
      [*]libidl.so
      [*]libnetmgr.so
    • libqcci_legacy.so
    • libqdi.so
    • libqdp.so
    • libqmi.so
    • libqmiservices.so
    • libqmi_cci.so
    • libqmi_client_qmux.so
    • libqmi_common_so.so
    • libqmi_csi.so
    • libqmi_csvt_srvc.so
    • libqmi_encdec.so
    • libril-qc-qmi-1.so
    • libril-qcril-hook-oem.so

    Hopefully I've given everybody some insight in what I found out and what I've been doing. When somebody still has some questions please don't hesitate to ask, and hopefully some other developers are willing to help me getting the remaining blobs ported over to gproj.

    Greetings PsychoGame
    10
    Hello everybody,

    Today I was working with some gproj sources but in the corner of my eye I did see recognized CyanogenMod developer "rmcc" better known as Ricardo Cerqueira pushed a RIL change upstream which bypassed CM code review.
    His patch can be found over here: https://github.com/CyanogenMod/andr...mmit/84e44a43ac2d0de4e3acd86322ffff43c38904e7
    I'm not yet sure what impact his patch actually has but I think it's worth to keep an eye on this change.
    This may be a workaround for the SIM Pin bug we are still working on.

    Update 1:
    I did some investigation on this pushed patch.
    It should fix the constant RIL crashing which occurs on our device, due to RIL calling for an unimplemented function.
    This may also fix the "deep sleep" issues, as I suspect the constantly crashing RIL may cause this but this claim I'm not sure about it's just a hypothesis which I had.
    Currently I'm building CM-12.1 to try and find out the real implications of the patch and verify what has been improved exactly.

    Update 2:
    This is the second update.
    The build I tried worked like a charm no RIL bug anymore!
    It was just like I suspected due to constant crashing of the RIL,
    I just suspected this due to outdated and old blobs in use, but "Ricardo Cerqueira" proved this was also fixable on the RIL side.
    Unfortunately the "deep sleep" issue still hasn't been solved.
    In the meantime I will just continue porting over KK blobs and try to make LG OG more CAF codebased.
    This fix will assure you at least can enjoy stable CM-12.1 for now until I got everything sorted out and 100% working right.

    Update 3:
    I'm currently trying to find out what might cause problem of the phone not entering "deep sleep"
    What I suspect currently is something with a service called qseecomd which is crashing.
    When looking into kernel "dmesg" I found that the "power management" related stuff about exiting deep sleep is constantly right after qseecomd crashing.
    Currently I'm busy trying to find a way to fix this issue.

    Update 4:
    I found out there are actually 2 wakelock issues which prevent the phone from entering "Deep Sleep".
    First wakelock is: pm8xxx_adc_wakelock, which I already found a solution for. This patch I will try to upload to gerrit codereview today.
    The second wakelock is a more difficult one to track down.
    The name of the wakelock is "KeyEvents" but I really can't seem to find out what exactly is causing this.
    What I know is that it's RIL/Radio related as when I put the phone in "Airplane Mode" this wakelock is released and phone goes into "Deep Sleep" without any problems.
    I will keep investigating this problem and hopefully find a proper solution soon.
    When someone has any suggestions please let me know.
    And in the meantime I hope CM Team will merge my patch for the pm8xxx_adc_wakelock (Fingers Crossed)
    The patch I uploaded can be found over here: http://review.cyanogenmod.org/#/c/113721/

    Greetings PsychoGame
    7
    Hello everybody,

    Sorry for being quite for a while.
    Status on the bug is unfortunately still the same.
    I'm a bit stuck in porting the Mako RIL over to the gproj based devices.
    To speed things up a little, together with Seth Shelnutt from CM-Team we decided it would be wise to first just port over the KK rom as it's an official released rom for the Optimus G.
    We are still working on this issue, but things are a little more complicated than I anticipated in the beginning so it just doesn't go that fast.
    When CM Roms are working again with stable RIL, I'll continue on updating the device code and trying to rebase a lot of stuff over to mako source and binaries.
    But that's a project for later on when there's time to experiment.

    Greetings PsychoGame
    5
    Hello everybody,

    I'm starting to grow a little bit tired of CyanogenMod Team.
    I uploaded my workaround some time ago and spoke to CM Team dev which promised me he would push the workaround through.
    Unfortunately he didn't keep his promise, and so the fix is still pending.
    To be honest I don't think the workaround will be pulled in as there is to less interest in it by the CM Team devs in my opinion.
    In the meantime I'm still working on the updated builds.
    Hopefully CM will merge them in the end. (Finger crossed)
    5
    we can add problems with autorotate to bug list. it's weird. I noticed that it works only once for YouTube. hangouts rotating only chat, not main window and other (but maybe not every) apps rotating always..
    @PsychoGame how is your work going on? have you got your repos on gh?

    Sent from LG Optimus G

    Hello Dadi11,

    I'm not working through github, as I make a lot of changes during the day so uploading them everytime would result in a lot of commits which may not do anything.
    Once I fixed something I'll upload the full changes at once to gerrit code review of CM.
    Currently I'm trying to update the CM e975 codebase as much as possible with the mako code as the codebase which is build upon still originates from mako 4.3_r2.1 while mako's code is on 5.1.1 already.
    Currently the RIL unfortunately in the latest nightly builds is completely broken and isn't able to get any mobile network at all (at least in my case, I don't know if you guys experience the same problems?).
    I'm still investigating this RIL bug, and it has my top priority at this moment as this is a serious bug which renders the CM12.1 roms completely useless at this moment.
    The RIL stopped fully working between the build 09/06/2015 and 11/06/2015, so a change in CM code between these two builds should be responsible for this problem.
    Currently I'm bisecting it to find out exactly which commit.

    Greetings PsychoGame