yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] zzpianoman:
Does the mute icon show on the status bar? My fix for in-call mute disables the highlight on the mute button, but if the microphone icon shows on the status bar, then the call is in fact muted. I'm working on a fix for the button.
[Samsung Galaxy Nexus] Zen_Man:
No status bar icon and I can't get to mute to do anything. Let me know if I can be of assistance.
[Samsung Galaxy Nexus] zzpianoman:
Well, I would have to take a look at the source code to figure out what is going on. Without that, It's difficult to troubleshoot.
[Samsung Galaxy Nexus] musical_chairs:
Yeah, sorry I don't have a github account...I've thought about starting one but haven't looked into how big of a deal it would be. I certainly don't expect you to do my troubleshooting for me, I highly respect your dev skills and don't want to distract you from your own projects. I'm probably missing something simple.
[Samsung Galaxy Nexus] zzpianoman:
It's no trouble, really. Always willing to help.
[Samsung Galaxy Nexus] zzpianoman:
I found out what the issue was:

Have to declare the INJECT_EVENTS permission in the manifest for Telecom. Something must have changed recently in the CM source code, because it was working fine for me until I synced yesterday.

Revert the original Telecomm commit, and then apply this one, and you should be good to go.
[Samsung Galaxy Nexus] musical_chairs:
Thank you very much! I'll find out in a bit for sure. If you're right, it'll be comforting to know that (at least this time) it wasn't due to me doing something stupid (which is a distinct possibility, BTW.)

My goal in building this ROM has been to keep things simple, staying as close as possible to upstream sources. My main motivations are, it's fun, and I want to run cm nightlies on my phone. I'm slowly learning a bit about git along the way. Since I can't write my own code, I cherry-pick patches from cool people like [MENTION=1048318]zzpianoman[/MENTION], applying them to my local branch. I sync with cm regularly, usually before every build (unless I'm doing some serious experimenting). Then, I go through each project in which I have changes, and merge my local branch back in. That way, I stay up to date and can sync fairly painlessly - painlessly compared to some of the things I tried as I was learning, anyway. Currently the changes I need are spread across ten projects. The whole 'keep it simple' idea is slowly spiraling out of control... :eek:
[Samsung Galaxy Nexus] zzpianoman:
That's pretty much how I started too - but it's very easy to get carried away with all the customizations and stuff.

I actually want to implement a more robust mute fix (interfacing directly with either the telephony layer or the telephony service), but I haven't had time to sit down and work through it just yet.

I haven't experienced any issues with the current method, aside from the fact that the mute button does not stay highlighted when the call is muted. It's really crazy how complicated the telephony stuff has become compared to earlier Android, when it was pretty much just confined to a single app. I guess now we have more VOIP/VoLTE stuff so the phone app doesn't always necessarily interface with just the radio layer - which is probably why they moved the microphone mute function from the RIL to the system audio manager.

Unfortunately, our device doesn't support controlling the microphone through audio manager so unless someone implements this for our audio drivers, we will have to stick with this method for the time being.
[Samsung Galaxy Nexus] musical_chairs:
New build up. Two 'big' fixes this time:

1. In-call mute works, thanks to [MENTION=1048318]zzpianoman[/MENTION]. As he said when he released his rom with this fix:

2. Offmode charging works, thanks to a fix from [MENTION=3390093]MWisBest[/MENTION]. He makes this stuff look so easy...

Note: I know we're all excited to try Android 5.1. [MENTION=3390093]MWisBest[/MENTION] has already released a build of it, and [MENTION=2633638]Ziyan[/MENTION] is feverishly working on it, I've decided to wait a bit. If CyanogenMod is extra-slow in merging it, maybe I'll do a toro build of zmod-5.1.
[Samsung Galaxy Nexus] KShion619:
What it's zMod?
[Samsung Galaxy Nexus] musical_chairs:
Ziyan's name on github for his Android 5.1 repos. What I was saying was, I might do a toro variant of Ziyan's 5.1 build if I get impatient.
[Samsung Galaxy Nexus] zzpianoman:
Just remember that Xposed will not work with 5.1, so that's something to consider if you are using that framework.
[Samsung Galaxy Nexus] past_pluto:
Love this ROM. No more deep sleep issues for me once off charge. Excellent battery life and little to no lag.
[Samsung Galaxy Nexus] demlv:
Delete . . .
[Samsung Galaxy Nexus] jetsman:
So I am stock rooted 4.2.2. I'm wanting to try this out but for some reason the gapps will not flash. Any advice would be great. Thanks
[Samsung Galaxy Nexus] past_pluto:
Which gapps are you using? I prefer the gapps-lp-20150212-minimal-edition-gps436-320dpi-signed.zip version. The PA ones never flash for me.
[Samsung Galaxy Nexus] jetsman:
Were can I find those?
[Samsung Galaxy Nexus] musical_chairs:
New build up. No major changes that I am aware of. Enjoy!
[Samsung Galaxy Nexus] past_pluto:
The gapps are located in one of the lollipop threads. I think poo76 liquid one?

What minfree settings do I need to keep Pandora running when using Facebook or navigation? That's the only annoying thing about running lollipop.
[Samsung Galaxy Nexus] past_pluto:
Given cool tool I'm never short on memory. It's 100% CPU that's causing my issues. Problem is the processes causing issue are normal ones. Facebook being the main culprit. Not sure what you do about that. At same time I can get great battery life. Had 3.2 hours screen on time with WiFi yesterday using Pandora and YouTube at times.
[Samsung Galaxy Nexus] svonavja:
Other than the Camera issues this is a sweet ROM, I had to go back to my Gnex while my Nexus 6 is getting repaired and this made the whole transition much easier, stock was killing my batteries. Thanks again, really good work!!
[Samsung Galaxy Nexus] christianpeso:
I think they pushed cm12.1 to their repos. Is this new build 12.1 or 12.0?
[Samsung Galaxy Nexus] musical_chairs:
It's still Android 5.0.2.

They did, but I haven't synced that branch yet. The thing is, once I do, I'll probably quit compiling cm12.0. What do you guys think? Should this be the final build of cm12.0?
[Samsung Galaxy Nexus] christianpeso:
I guess it would depend on how stable 12.1 is out of the gate. If it runs like it does now on 12.0, then I would say kill it. If there are major bugs, I would continue doing 12.0 builds and an occasional 12.1 build until it got stable. Totally up to you though.
[Samsung Galaxy Nexus] zzpianoman:
One day....they will invent a hard disk with unlimited capacity!

I'm hesitant to switch over to CM-12.1 until Xposed is made to be compatible - and until I hear any reports of how stable it is for daily use.
[Samsung Galaxy Nexus] musical_chairs:
...and one day, I will have nothing else pressing to do with my time. But hopefully by then, the Galaxy Nexus will be out of date by forty or fifty years.

Currently, I'm playing with Ziyan's domx updates. I think I'll hold on for just a bit to see if we can get some improvements on that front before I pull the trigger on Android 5.1.
[Samsung Galaxy Nexus] lovemachine35:
No data with 041015 5.1 Build

This ROM is very smooth and works awesomely! on my GNEX. However, I don't have data. I installed the APN Fix and I now have 3G. Can you incorporate this in your next build please:good:

Thanks for all the hard work you've done. I love my phone and I still have unlimited data from Verizon :laugh:
[Samsung Galaxy Nexus] zzpianoman:
Do you also have 4G?
[Samsung Galaxy Nexus] lovemachine35:
[YOUTUBE][/YOUTUBE]

Not yet, but I haven't left my house yet this evening. I usually get a 4G signal in my house, but we had storms come through and maybe the cell tower took a hit. I'll let you know when I get to work tomorrow.

Otherwise, I'm very pleased with this release. Thanks to MusicalChairs and yourself for helping him out.
[Samsung Galaxy Nexus] zzpianoman:
Ah okay. The reason I ask is that I'm having trouble getting a 4G signal with my latest build, which is also CM12.1. I wasn't having any trouble with the first CM12.1 build I did, and I can't see any telephony changes between those two builds that could be causing this to happen. I even reverted to my original 12.1 build and am having the same trouble so I'm wondering if it could somehow be related to the Verizon network and the fact that it's only appearing now is merely coincidental.
[Samsung Galaxy Nexus] musical_chairs:
4G has been working for me. I thought I had the right APNs included with the ROM, but apparently not.
[Samsung Galaxy Nexus] zzpianoman:
The stock CyanogenMod APNs don't seem to work with Verizon.

I get 4G "sometimes" but not in my house. So I know that the phone is able to connect to 4G network, but it just doesn't seem to want to stay connected. I've been debugging LTE signal parameters (RSRP, RSSNR, CQI, ASU, etc) and the signal appears to be adequate, so I'm not quite sure what is going on.

I also tried flashing another 5.1 ROM and I seem to be having the same connectivity problems. Perhaps there is a systemwide 4G outage here - which seems kind of odd considering I'm in the NYC area.

Oh well....I'll probably let it go for the time being and see how things progress over the coming days.

Also, with the APNs - the only real difference between my APNs and the stock Android APNs (other than the fact that I removed all of the extra ones), is that I have resolved the MMS server to an IP address - otherwise MMS sending will refuse to work. It also appears this is an issue with the maguro variant, so I'd like to figure out a more universal fix. After all, one day Verizon might decide to change their IP address, at which point, a new APNs file will have to be created.
[Samsung Galaxy Nexus] lovemachine35:
It's showing LTE instead of 3G now. I am at work and have a strong signal here. It took a while to get the LTE connection while driving.
[Samsung Galaxy Nexus] arigr:
deleted
[Samsung Galaxy Nexus] zzpianoman:
Ah okay. Thanks for the update.

I did some investigating, and found something a bit interesting that has changed in the code relevant to signal status:

from frameworks/base/telephony/java/android/telephony/SignalStrength.java:

private static final int RSRP_THRESH_TYPE_STRICT = 0;
private static final int[] RSRP_THRESH_STRICT = new int[] {-140, -115, -105, -95, -85, -44};
private static final int[] RSRP_THRESH_LENIENT = new int[] {-140, -128, -118, -108, -98, -44};
//
int rsrpThreshType = Resources.getSystem().getInteger(com.android.internal.R.integer.
config_LTE_RSRP_threshold_type);
int[] threshRsrp;
if (rsrpThreshType == RSRP_THRESH_TYPE_STRICT) {
threshRsrp = RSRP_THRESH_STRICT;
} else {
threshRsrp = RSRP_THRESH_LENIENT;
}

if (mLteRsrp > threshRsrp[5]) rsrpIconLevel = -1;
else if (mLteRsrp >= threshRsrp[4]) rsrpIconLevel = SIGNAL_STRENGTH_GREAT;
else if (mLteRsrp >= threshRsrp[3]) rsrpIconLevel = SIGNAL_STRENGTH_GOOD;
else if (mLteRsrp >= threshRsrp[2]) rsrpIconLevel = SIGNAL_STRENGTH_MODERATE;
else if (mLteRsrp >= threshRsrp[1]) rsrpIconLevel = SIGNAL_STRENGTH_POOR;
else if (mLteRsrp >= threshRsrp[0]) rsrpIconLevel = SIGNAL_STRENGTH_NONE_OR_UNKNOWN;

and in the config resources file used to set this parameter:

<!-- Flag indicating whether strict threshold is used, or lenient threshold
is used when evaluating RSRP for LTE antenna bar display
0. Strict threshold
1. Lenient threshold
-->
<integer name="config_LTE_RSRP_threshold_type">1</integer>

So the values that frameworks considers "strict" are actually the same values as they have been since Jelly Bean and the "lenient" values are new. According to the config file, the lenient values are the default unless otherwise overridden in an overlay. Now, one would think that by using more lenient values, the LTE signal strength should "improve" in appearance but maybe the opposite is happening? I'm going to try setting it back to strict threshold to see if that fixes the problem.

Also, I'm not even sure if this would affect the decision to handoff from 4G to 3G or if this is just for the signal display in the statusbar. The handoff logic might actually exist in the radio firmware, in which case, there isn't much that can be done about it.
[Samsung Galaxy Nexus] techgeek24:
Phone not waking?

First of all, thanks much for you work on this, I didn't really expect to see CM 12 on my Galaxy Nexus and am super grateful and pretty impressed that it works so well. :)

However, I'm having an issue where occasionally my screen won't wake. I think my phone is still on, but I haven't actually verified. It's done this to me probably 4 times in the last few weeks, twice in the last couple days. The only thing I can do to get it to respond is to pull the battery and boot it up again. Have you guys had an issue at all like this or is my phone dying?
[Samsung Galaxy Nexus] musical_chairs:
I've seen that too, it might be an issue with the 'Prevent accidental wake-up' setting. Come to think of it, it always happened around home (when my phone is in my pocket) and has never happened at work (where my phone is always in a holster on my belt). Go to Settings / Display & lights and de-select 'Prevent accidental wake-up', and see if that helps..
[Samsung Galaxy Nexus] techgeek24:
Now that you mention that, I think the last two times it happened were after it was in my pocket so I'll definitely give that a try. Thanks much!
[Samsung Galaxy Nexus] musical_chairs:
New build up:

- Android 5.1.1

- off-made charging works now

- videos are still jerky

Regarding the phone being unable to wake sometimes, a user posted elsewhere that plugging in the charger will wake it up. But I'm pretty sure disabling 'Prevent accidental wake-up' fixes it.
[Samsung Galaxy Nexus] obsidianchao:
Was camera ever fixed, MC? I'm still back a couple builds (last update build, before the CM nightly merges) and it's buggy.
[Samsung Galaxy Nexus] lovemachine35:
Square Register Swiper

Question: anyone know why my Square Register Credit Card reader won't work with my Gnex using this latest unofficial CM12.1 (Android 5.1.1) ROM? It works with my Nexus 7 2013 Wifi using the latest CM12.1 nightly (5.1.1). Was wondering if anyone knew of any patches.
[Samsung Galaxy Nexus] musical_chairs:
Camera is still pretty buggy, fixing that goes far beyond my limited skills. I try to stay up to date with the latest stuff from Ziyan and MWisBest, who are the guys doing the real work toward fixing that. If you want better camera stability, use [MENTION=1048318]zzpianoman[/MENTION]'s CM build (the one marked DDK 1.8).

Probably related to this: http://xdaforums.com/showpost.php?p=60345849&postcount=2371

I'll change the kernel config to use the older power management drivers in the next build, hopefully that will fix it.
[Samsung Galaxy Nexus] lovemachine35:
Thanks MC. I can use my credit reader now.
[Samsung Galaxy Nexus] musical_chairs:
New build up, now using older power management drivers. This should fix issues with headset controls and lots of other stuff that plugs in there.
[Samsung Galaxy Nexus] lovemachine35:
MC, sorry, but the file says toroplus and won't install on my toro. Once fixed, I can't wait to try my credit card reader. Thanks.
[Samsung Galaxy Nexus] musical_chairs:
Sorry, I must have been asleep when I uploaded that. :o The toro build does indeed exist, and will be on its way in a little while.
[Samsung Galaxy Nexus] musical_chairs:
OK, the new build is actually up now: https://www.androidfilehost.com/?fid=23991606952592829
[Samsung Galaxy Nexus] past_pluto:
I haven't been able to get mobile data to connect since 4/18. Hopefully this one works.
[Samsung Galaxy Nexus] musical_chairs:
If it doesn't, try flashing zzpianoman's MMS fix (modified APN's) in recovery:

http://xdaforums.com/showpost.php?p=58148653&postcount=88

For some reason, my build isn't copying in the APN's I am trying to tell it to, and our toro's don't like CM's APN's.
[Samsung Galaxy Nexus] Zen_Man:
Yeah that works, I had the same issue with mobile data and I used the MMS fix to get it working. I've had no problems since then.
[Samsung Galaxy Nexus] zzpianoman:
Try this.
[Samsung Galaxy Nexus] musical_chairs:
New build up. Data should work now on a clean install, no need to flash the MMS / APN fix.
[Samsung Galaxy Nexus] lovemachine35:
For some reason the last couple of builds I can't get mobile data to work. This new one I did a clean install.

Update: 5/4 - I had to go back to my 4/23 backup to get my mobile data back.

Update 5/7 - I did another clean install of the latest 4/30 build. I did a factory reset from TWRP recovery and then a system wipe. Installed ROM then Minimal GAPPs for 5.1.x. Instead of having Google Play reload all my apps from backup, I slowly added critical apps I use everyday. So far so good. I have mobile data. However, Google Play Services keeps failing. I've gone into Privacy Guard and messed with wake lock settings for Google Play Services, but it doesn't seem to help. I also loaded MyAndroidTools and deactivated SystemUpdateService under Google Play Services. Still having some problems. I am functional as a daily driver, just kind of frustrating. I know it's not your fault MC, just giving you an update of what I've done. Thanks for all your work.
[Samsung Galaxy Nexus] musical_chairs:
New build up. Notable changes:

- Camera crashes should mostly be fixed. Thanks Ziyan!

- Videos are no longer cropped to remove the green line. Fixed by zzpianoman. Note that videos taken with the front camera still have a purple line at the side.
[Samsung Galaxy Nexus] kb8no:
What gapps should we use? OP links closed. Link please...
[Samsung Galaxy Nexus] musical_chairs:
I'm not sure where I got the package I am using. Here's a thread that looks like it should have a good minimal gapps package:

http://xdaforums.com/android/software/gapps-google-apps-minimal-edition-t2943330

Looks like he has an AOSP calendar sync add-on too, maybe that would fix the issue people are having with needing to install Google Calendar to get calendar syn to work. If I get a few confirmations that this gapps package works well (and if I get time to test it myself), I'll update the link in the OP.
[Samsung Galaxy Nexus] kb8no:
It would be the Android 5.1 version on the OP of this link to try, right?

Note: 5.1 version seemed to work fine. There may be nuances but up and running.
[Samsung Galaxy Nexus] past_pluto:
Minimal gapps works just fine with this. That's what I've always used on both KitKat and Lollipop. It doesn't work well with FML though. For that ROM use the gapps in his thread.
[Samsung Galaxy Nexus] christianpeso:
This still does not have f2fs support, correct?
[Samsung Galaxy Nexus] musical_chairs:
Actually, I think it does on the most recent build. Ziyan added the code to the kernel and the tuna device tree, and it is working on his builds. I haven't tested it yet, though I intend to shortly.
[Samsung Galaxy Nexus] wavedashdoc:
I can confirm it does support f2s. Just make sure you're system partition is EXT4.
[Samsung Galaxy Nexus] christianpeso:
Up and running great on F2FS. Haven't used this device in a while as it is not my daily driver. MMS working fine with built-in messenger. Going to use this for the next few days as I wanted to try out the latest 5.1.1 OS and my Note 3 is still on Kit Kat. Looking forward to the next few days. Thank you for this Musical!
[Samsung Galaxy Nexus] musical_chairs:
New build up. Includes MWisBest's audio hal fixes (pops and clicks should be gone now), and GPU max frequency can now be set with Trickster. You may need to disable per-app performance profies (in Settings/performance) to get this to work. I'm suspicious that having the GPU oc'd to 512 may have been causing reboots for some users, so if you've had reboots that appear to be display-related, try setting your max GPU frequency to 384.
[Samsung Galaxy Nexus] past_pluto:
Miss running this on my toro. I had to finally give it up for an S4. Which since I haven't rooted or installed CM is an absolutely terrible device. Hardware is great but omg touchwiz is a nightmare.
[Samsung Galaxy Nexus] elbi14:
no toroplus update? :(
[Samsung Galaxy Nexus] musical_chairs:
Yeah, it's up now too. I have to do them one at a time because my internet connection is slow.
[Samsung Galaxy Nexus] cmf45:
I just wanted to sign in and say thanks for this. Given all the issues with previous versions of cyanogen and the APN/radios mess, I thought I would be stuck in kit kat land. I don't have the money (I'm a grad student) for a new phone, so my galaxy nexus is still my daily driver. I installed the latest build with minimal gapps and the apn and mms fixes, and everything seems to be running beautifully. LTE came on right away and everything.

Thanks to everyone for your hard work at giving some new life to my old phone!

c
[Samsung Galaxy Nexus] kb8no:
[MENTION=4531957]musical_chairs[/MENTION] This, I agree, is a very nice build. Its my wife's phone and the last version drew lots of complaints in her language about lagging. She likes this ROM cuz it fixed it and it makes the GNex sing.

We're traveling now which gave me some time to experience it. It is slow to switch between 3G and 4G. I'm learning there is often an ! by the signal bars while it is struggling to switch during which there is no data. Never saw an ! by the signal bars before.

Also, my S3 will have switched to 4G much earlier before the GNex makes the change.

This doesn't make it unusable and I'm very happy with this ROM. Maybe it is old hardware or radio problems. On the other hand, maybe you can improve it if you know about it. I'm guessing when I'm home and mostly on one tower it will not be noticeable and constant tower jumping on the road exposed it.

Thanks for giving us these ROM's and we appreciate the work.

Edit: Same problem around town after returned home. Getting lost in 3g LTE handoff lag. My wife needed to reboot.
[Samsung Galaxy Nexus] baldybill:
Interested in using for this my daily driver GNex. I take it you got the latest build from this forum. Where did you get the fixes for APN and MMS and were they hard to install?
[Samsung Galaxy Nexus] Zen_Man:
On the latest build you don't need to apply those fixes and mobile data works.
[Samsung Galaxy Nexus] cmf45:
Yeah, I used the ones from the first page, but I guess it's not necessary. I've been running it ever since and it's been fantastic. Even slightly better battery life. Definitely brought new life to the phone. Only issue I've had is that chrome beta's not working great, but everything else has improved. I can even get and send MMS, which I haven't been able to do on a long time.

c
[Samsung Galaxy Nexus] musical_chairs:
Since I was building an f2fs-enabled TWRP recovery for toroplus, here's one for toro as well: https://www.androidfilehost.com/?fid=23991606952615425
[Samsung Galaxy Nexus] PowurPlayr:
best gApps for latest build would be?
[Samsung Galaxy Nexus] quickdraw86:
http://xdaforums.com/showthread.php?t=3116347

Pico is all win.
[Samsung Galaxy Nexus] PowurPlayr:
2 days in, pico rocks on latest build! Battery life much better and very stable here. Thanks for all your work!
[Samsung Galaxy Nexus] SynbiosVyse:
I'm still getting random sound pops and clicks with the latest build. Any way to fix this?
[Samsung Galaxy Nexus] musical_chairs:
Disable UI touch sounds and they will go away. They supposedly were fixed a number of weeks ago, but you're not the only one who says they are still there.

And, there is a new build up. Not much to say about it, just synced the latest CM sources. Enjoy!
[Samsung Galaxy Nexus] quickdraw86:
Latest build is dated as 6-14 (yesterday)? Is that the new build you're talking about?
[Samsung Galaxy Nexus] musical_chairs:
Yes, I just didn't get a chance to upload it sooner.
[Samsung Galaxy Nexus] PowurPlayr:
Where to find UI touch sounds to disable & does that disable keyboard sounds as well?