yashsingh1/xdaforums huggingface dataset:
[LG Optimus G (International)] akahroba:
[MENTION=4647521]PsychoGame[/MENTION] I think these are the main problem of official CM12.1

1. App watch dog bark (green screen) problem. Not sure if it's fixed now or not

2. camera is a bit dark not connecting in some apps. stock KK camera and vendors are already ported but they don't add it.

3. Signal keeps connecting and disconnecting

the solution is available for the first two and just need to be sent via gerrits. but the last one is still a mystery.
[LG Optimus G (International)] PsychoGame:
I agree with you on the fact that the current CM Team isn't as opensource friendly as it was in the beginning.

Not that they closed their sources of course, but changes submitted by others sometimes take a long time to get pushed upstream.

My guess is that since they also develop their commercial version of CM, they are less interested in delivering a stable CM for a big range of devices.

This is my guess, but I think I'm in the right direction cause a lot of troubles at CM started when they commercialized to CM Corp.

That a lot of developers don't get quick response at their submitted code, demotivates a lot of developers to push more code upstream, as they feel it has no point wasting a lot of time to get things pushed trough by a maintainer.

I'm also easily demotivated when it comes to these problems.

Further for the green screen problem, I haven't experienced this one yet in the CM12.1 builds. The camera problems is indeed fixable by using KK camera binaries and sources, but big changes like these unfortunately don't get pushed upstream very easily. See my thoughts on that earlier. The RIL troubles in CM12.1 I think are related also due to outdated RIL binaries and code. What I did so far was create a -eng build instead of a -userdebug build, so I have more debugging info and tools at hand to track down problems. What I found at this moment was that the RIL crashes very frequently. This also causes the SIM Pin bug to my current knowledge, as the RIL crashes with the same frequency as the tries that are necessary to get the SIM Pin accepted. The error which occurs is found in the dmesg (kernel logging output) of a running CM12.1 build. First it whines about old 32-bit code which is found, so it falls back to legacy mode. Also found in the dmesg is the fact that RIL crashes with a sig=11 crash warning, with the description 'memory violation'. I'm very busy tracking down what exactly might cause this to happen.
[LG Optimus G (International)] akahroba:
Thanks for sharing your investigations. Can we port RIL from Stock ROM and add it to see if it helps or not? There's a guide here for sony devices: http://xdaforums.com/showthread.php?t=2475352
[LG Optimus G (International)] PsychoGame:
That may be possible, but currently I'm trying to fix some stuff using the mako sources.

In fact the Nexus 4 (Mako) is almost the same as the geehrc with some small differences like the camera sensors.

Just like many before me have tried, I will try to rebase the e975 sources against the mako sources and try to convert to using mako lollipop binaries.

I know this is possible as my device from the past (I9001 Samsung Galaxy S Plus) with originally Gingerbread as final rom also received the CM12.1 roms.

This wouldn't have been possible when they weren't able to use binaries from other devices/roms which were based on the same hardware.

And mako already received the official lollipop update, so technically it should be possible to use mako binaries/kernel source and be able to create a mis between geehrc and mako source/binaries.

Greetings PsychoGame
[LG Optimus G (International)] akahroba:
I'm not sure if you already know this or not but we have unofficial CM sources which are all Mako based. And yeah, they don't have this signal problem. Here's Kevin sources: https://github.com/lollipop-og/android_device_lge_geehrc

Also faust93 once did a great job and made E975 stock KK kernel compatible with custom ROMs. you can see the sources here: https://github.com/faust93/F93_LGE975_KK_Kernel

I'm just letting you know of the already done jobs so that you won't have to take the same steps and we can fix things faster.
[LG Optimus G (International)] PsychoGame:
I knew of these repositories indeed.

I'll take a look at these things as well, but I'll also rerun all the steps they took to port the stuff over to mako, so I know all the ins and outs of these steps.

This way I have full understanding of all the stuff thats going on in the system.
[LG Optimus G (International)] iakoboss7:
can somebody implement a lower dim setting for the screen? compaired to stock the lowest setting is way brighter!
[LG Optimus G (International)] dadi11:
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..

[MENTION=4647521]PsychoGame[/MENTION] how is your work going on? have you got your repos on gh?

Sent from LG Optimus G
[LG Optimus G (International)] PsychoGame:
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
[LG Optimus G (International)] Ardath Bey:
The RIL problem started with version 06/06/2015.
[LG Optimus G (International)] dadi11:
I saw your commits on cm Gerrit. but we don't want to wait for your fixes. should I wait for cm to merge it or I can cherry-picked it now to my sources? what has been fixed until now?

Sent from LG Optimus G
[LG Optimus G (International)] PsychoGame:
Hello Dadi11,

You can cherry-pick these commits without any problems.

They have been tested before uploading the commits to gerrit (at least the commits which I +1'ed).

At this moment they don't really fix any obvious bugs, but rather update the outdated code to the newer mako 5.1.1 device codebase.

The RIL bug I'm still working on, but the problem isn't very easily fixable, once I found a breaktrough which fixes this problem I'll contact you through PB on xda.

Greetings PsychoGame
[LG Optimus G (International)] dadi11:
thank you for your work :) today I will cherry-pick all your +1'ed commits and I will also follow your work on cm Gerrit and this thread :)

Sent from LG Optimus G
[LG Optimus G (International)] iakoboss7:
what is the problem with RIL? i mean what will i see as a user? i am asking so i can avoid updating before it gets fixed!

PsychoGame thank you for your work!
[LG Optimus G (International)] dadi11:
read previous posts..

I'm trying to compile with your commits merged, [MENTION=4647521]PsychoGame[/MENTION]. you can add me on hangouts if you want to contact faster. or pm me :)

Sent from LG Optimus G
[LG Optimus G (International)] sonty:
since every 6 months or so I decide to update my rom, I tried this week to compile carbon and ran into the same SIM PIN issue you have here. I spent almost the whole day yesterday and I think I managed to solve it.

First of all:

[cristic@vm gproj-common]$ git diff ril/telephony/java/com/android/internal/telephony/LgeLteRIL.java
diff --git a/ril/telephony/java/com/android/internal/telephony/LgeLteRIL.java b/ril/telephony/java/com/android/internal/telephony/LgeLteRIL.java
index 4109c3c..be3b60e 100644
--- a/ril/telephony/java/com/android/internal/telephony/LgeLteRIL.java
+++ b/ril/telephony/java/com/android/internal/telephony/LgeLteRIL.java
@@ -155,7 +155,11 @@ public class LgeLteRIL extends RIL implements CommandsInterface {
status.setUniversalPinState(p.readInt());
status.mGsmUmtsSubscriptionAppIndex = p.readInt();
status.mCdmaSubscriptionAppIndex = p.readInt();
- status.mImsSubscriptionAppIndex = p.readInt();
+// status.mImsSubscriptionAppIndex = p.readInt();
+
+ boolean oldRil = needsOldRilFeature("icccardstatus");
+ if (!oldRil)
+ status.mImsSubscriptionAppIndex = p.readInt();

int numApplications = p.readInt();

the idea came from here: http://review.cyanogenmod.org/#/c/90257/

and then I reverted a bunch of commits from CM, but the last one that did the trick was: http://review.cyanogenmod.org/#/c/100719/1

the other commits that didn't work without 100719 are:

http://review.cyanogenmod.org/#/c/100718/1

http://review.cyanogenmod.org/#/c/100717/1

http://review.cyanogenmod.org/#/c/100726/1

on my e975 it worked first time after clean flash (twice) and after reboot (again twice).

later edit: I don't know if it's related or not but LTE works, but rarely. Mostly it just jumps to HSPA and stays there.
[LG Optimus G (International)] PsychoGame:
Hello [MENTION=3282052]sonty[/MENTION],

I'll take a look at the patches you mentioned.

I don't think the CM Team is willing to revert these patches.

I'm thinking of correcting the mentioned patches so that these patches will not be included in the gproj builds, but will still be included for other devices which still depend on these patches.

This should be as simple as some if and else clauses which will exclude these patches if a predefined variable is set.

Thanks for the research work you put into this.

Edit 1: I'll also research you're problem regarding the LTE signal dropping constantly

Update 2: I checked the patches which you reverted to make the RIL work again. First of all I'll try to create a workaround for the problem, using the solution you suggested. When studying this problem and also the patches that have to be reverted my suspicion gets confirmed more and more. The code and also the source and binaries from the (TheMuppets) github are very very outdated. If I'm correct they still originate from the Jellybean stock rom which the device was released with. The correct solution would really be to bring the code up to date again, which will be very difficult if the CM-Team decides not to work with us.

Greetings PsychoGame
[LG Optimus G (International)] sonty:
I narrowed it down to 100726 and 100719.

my opinion is that the binaries should be fine, these changes are in the way the framework handles its subscribers and the only subscriber here I think is the phone app. so from my point of view it's just a bug in CM.

and now I see 100719 was reverted yesterday in the main branch.
[LG Optimus G (International)] PsychoGame:
The binaries are fine, as in they work for the releases yes. But the binaries still originate from the jellybean release which the e975 originally shipped with.

LG released KK for the device which introduced new KK optimized and updated binaries and libraries.

I agree with you on the matter that it seems the binaries aren't directly responsible for the RIL bug.

I checked if 100719 was reverted, but this is not the case. I posted a comment on the commit which upped the commit in the review list.

I hope to get in touch with Ricardo, so he can alter the commit in the way he likes.

If he doesn't respond timely, I'll create a patch which excludes this commit from the e975 builds.

Greetings PsychoGame

Update 1: Hello [MENTION=3282052]sonty[/MENTION],

I've investigated the troubling commits some more and the only commit responsible for the Sim Pin problem is 100719.

I also found out most of this commit is functioning okay, except for one small line of code which is: setDefaultDataSubId(subId);

If this line is disabled again the RIL functions okay.

So I'll be creating the patch and upload it later on.

Hopefully CM Team will include it soon in their main code.
[LG Optimus G (International)] Btob6:
Thanks a lot. What about the network problem? Network not found. :confused:
[LG Optimus G (International)] PsychoGame:
My patch has been applied to the cyanogenmod gerrit.

As long as it's still not implemented you can cherrypick it from here: http://review.cyanogenmod.org/#/c/101766/

Now it's up to the CM Team to mainline the patch.

Greetings PsychoGame
[LG Optimus G (International)] enapah:
By the looks of it, that patch will be sidelined for a "proper" RIL solution (whose cause, at RIL level, isn't even identified).

Meanwhile they should (but won't) just stop building for our device, as the current builds pretty much don't have cellular connection (which makes that a severe regression and essentially a useless build to the majority of users).

Still, don't let that affect you, keep up the good work (same also goes for everyone else -- good work).
[LG Optimus G (International)] PsychoGame:
Hello [MENTION=5983145]enapah[/MENTION]

Thanks for you're support.

Currently I'm trying to reach out to Danny Baumann and Brandon McAnsh.

I already adjusted the patch to Brandon McAnsh liking, but like you said indeed Danny Baumann doesn't think this will be the proper way to do it.

Hopefully I get in touch with Danny to create a solution which satisfies everybody.

I'll keep everyone updated on this matter, and I won't give up that easy if they're thinking that.

The Optimus G community deserves a working android build.

Greetings PsychoGame
[LG Optimus G (International)] iakoboss7:
sir, thank you for your efforts and patience!
[LG Optimus G (International)] akahroba:
thanks for your efforts [MENTION=4647521]PsychoGame[/MENTION]. If possible, please ask them to implement stock kk ported camera blobs: https://github.com/dadi11/android_vendor_lge_e975
[LG Optimus G (International)] PsychoGame:
Hello akahroba,

I'll implement the KK camera blobs later on.

At the moment I'm busy porting the KK ril blobs, as a (hopefully) possible fix for the ril problems we're having.

In the IRC channels a lot of other developers also suggested that the blobs that are used for the builds are too outdated.

When the porting of the KK RIL blobs is finished I'll move on to update all the other blobs as well (one step at a time).

Hopefully the RIL will be fixed this way, then we won't need the hacky patch that CM-Team doesn't like anymore.

Greetings PsychoGame
[LG Optimus G (International)] akahroba:
Thanks [MENTION=4647521]PsychoGame[/MENTION]. today, a snapshot build is out! Is it fixed? or a snapshot with no signal? Because snapshot builds are supposed to be the most stable builds.
[LG Optimus G (International)] Btob6:
Without "Clean Install Rom" you will get a "Bootloop".
[LG Optimus G (International)] PsychoGame:
Unfortunately the snapshot has the same bug we are dealing with. The patch I created will not be mainlined by CM team as it's more of a hack than a solution.

In the meantime i'm working on a more permanent solution, which is updating the RIL blobs and their dependencies. At this moment I guess i've already done 25% of the porting work, but i'm facing some problems with qmuxd which I neef tot figure out before I will make more progress

Greetinga PsychoGame
[LG Optimus G (International)] teacher77:
Now, I'm wondering why to do a snapshot where network doesn't work in a (smart)phone.

I'm a bit disappointed by CM team...
[LG Optimus G (International)] Btob6:
Whats going on? Nothing happens by Developers of CM!
[LG Optimus G (International)] Beeperz:
:D
[LG Optimus G (International)] PsychoGame:
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
[LG Optimus G (International)] iakoboss7:
anyone got a link with the latest cm12.1 that has working RIL?
[LG Optimus G (International)] PsychoGame:
Hello iakoboss,

There hasn't been a single CM-12.1 build which was completely good.

The sim/pin bug got introduced in the transition between CM-12.0 to CM-12.1.

Currently I'm still trying to work it out, with help of some other developers like Seth.

Our current first goal is to replace the old RIL blobs from jellybean with the newer available blobs from Kitkat.

See my post on the page before on the status of the project.

It's not progressing very fast (as fast as I like it to be), but I know we can do it.

Greetings PsychoGame
[LG Optimus G (International)] iakoboss7:
thank you for your fast reply and everything you are doing for the community!

right now i am at 3/6/2015 cm12.1 build and "everything" works fine for me (i DONT use pin for the sim card so its fine for me).

after the phone starts up for 30 sec it switches lots of time from "all ok" to "sim not found" and after that everything is fine (network is fine and i can make calls perfectly).

can i make calls (i dont care about sim pin) in the latest builds?

thank you for your time!
[LG Optimus G (International)] Btob6:
No, not possible! :(
[LG Optimus G (International)] akahroba:
Good luck with this job [MENTION=4647521]PsychoGame[/MENTION] : https://github.com/PsychoGame/android_kernel_lge_msm8064

you can get the help of Vlad's source to make it faster: https://github.com/faust93/F93_LGE975_KK_Kernel
[LG Optimus G (International)] PsychoGame:
Hello akahroba,

I'm surprised how sharp you are :p

You spotted the new github and I suppose you already know what's going on.

But I will publicly announce it now.

Unfortunately I will not be able to directly use Vlad's source.

The kernel which I will be using will be based upon CAF once more.

I attempted this already for stockrom which seemed a successful project.

Unfortunately I came to the conclusion that the KK blobs will not work nicely with the current gproj kernel.

So the kernel work needs to be completely redone, which I will be basing on CAF sources cause this will make it easier to import CAF patches later on.

Currently my github is mirroring the CAF msm kernel repo, and from there the fun part will begin.

Greetings PsychoGame
[LG Optimus G (International)] akahroba:
Haha :laugh: I really appreciate your linux knowledge and follow your activities. So, you have many things to do. Take your time. Let's see if gproj can get back to stage or not. This is also a good step toward android M I believe.:good:
[LG Optimus G (International)] Vampir1c:
Would this ril issue be the cause of my recent builds (Gproj) of Blisspop for the E970 having no sim and not connecting to the network problem?
[LG Optimus G (International)] patalao:
Yes

Enviado do meu Optimus G através de Tapatalk
[LG Optimus G (International)] akahroba:
[MENTION=2599199]psych[/MENTION]Game you broke up with your girl friend? :P no further progress from then. All gproj projects are stopped. like these ones that you may not know about: http://4pda.ru/forum/index.php?showtopic=621762&st=20#entry36064563
[LG Optimus G (International)] Btob6:
It seems "Game is over". :(
[LG Optimus G (International)] enapah:
For now the best we can do is compile the ROM ourselves with the work-around posted earlier (http://review.cyanogenmod.org/#/c/101766/).

I just don't know why the heck they are building for this device without that patch... the ROM as it is is virtually useless, very few will want a phone without working cellular connection -- and we are well past the initial stages when a phone is new and people do this as "Proof-of-Concept".
[LG Optimus G (International)] Btob6:
What do you mean? In build.prop there is no entry with "ro.telephony.ril.v3=xxxxx". What i have to do?
[LG Optimus G (International)] iakoboss7:
then can someone that knows how, do the good thing and do it please??? (in a weekly bases if its easy? >.<)
[LG Optimus G (International)] enapah:
You are reading a suggestion to make the patch better (that requires a different implementation to work). Look at the modified SubscriptionController.java, that's how it was actually done.

(It should be noted that this work-around was found by [MENTION=3282052]sonty[/MENTION] and then submited by [MENTION=4647521]PsychoGame[/MENTION] as a way to have a functioning phone up until a proper solution was realized -- read the binary blobs update/potential RIL fix)

It's easy in the sense it's not complex, but it does require lots of computational power (CPU + RAM / SSD vividly recommended) otherwise it will take quite some time to complete. Meaning that you need someone with a proper build machine, otherwise it's just a painfully slow task that will take a lot of time whilst killing all your productivity in that machine. (The Cyanogenmod is already building for the device nightly, so why not just make their builds *useful* instead of wasting time and energy?)
[LG Optimus G (International)] Btob6:
If someone upload the modified build.prop and to substitute it with the origin, it's working or not?
[LG Optimus G (International)] enapah:
If you want that kind of elegance you could do it by changing the device local manifest (at compile time), but things can be made much (much) simpler (specially given this is a work-around, not a final solution).

The easiest way is to (at compile time) cherrypick or just replace the file in the CyanogenMod/android_frameworks_opt_telephony repository at src/java/com/android/internal/telephony with the SubscriptionController.java of this ticket (http://review.cyanogenmod.org/#/c/101766/).

There are at least two reports of someone who did that and it does indeed still work (with the same nuisances as the last working build, namely a connection that goes up and down until it eventually stabilizes and stays working).

But the thing is, why doesn't the CM team do that themselves (instead of continuing making useless nightly builds).
[LG Optimus G (International)] Btob6:
Is there anyone to compile the newest Nighly and upload it for everyone? Would be kindly appreciated (Zippyshare 2 Parts, restricted to 199MB).
[LG Optimus G (International)] ilmagico88:
Here you can find a working build (remove 3 spaces to can access the link):

https : // jira.cyanogenmod.org/browse/NIGHTLIES-1407?focusedCommentId=75432&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-75432
[LG Optimus G (International)] j4yd3n:
Thanks :) I just finished flashing the update, i tried not flashing the Gapps again, when it booted up all the apps i got was still there :)
[LG Optimus G (International)] leouzcategui:
SuperUser

Hi all, do I have to flash the superSU zip like other custom roms or only Rom and Gapps zip? Thank you
[LG Optimus G (International)] howaboudno:
CM usually comes with root, so I'm guessing you dont have to. If the previous sentence is false, go back to recovery and flash superSU
[LG Optimus G (International)] j4yd3n:
hi there, i flashed the new update zip from their website. It seem to have fixed the dim camera, but the wrong ratio is still there.
[LG Optimus G (International)] koxminator:
guys, does fm radio work with this new official cm12? thanks in advance
[LG Optimus G (International)] tietganFTW:
That's what I thought so too. Apparently CM is going to integrate root permissions with their Privacy Guard function but I haven't seen any options for root access built-in as of yet so I had to flash supersu to gain root access. Maybe they'll implement in the near future after they've got everything sorted out?