yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Rushead:
http://goo.im/gapps
[Samsung Galaxy Nexus] asianrage:
Does Google Play Music work for anyone? It crashes when I try to stream music.

And does YouTube show up too? I keep getting errors and it ask to touch to retry, and yet, not showing anything.
[Samsung Galaxy Nexus] 7175:
Been looking into the radio issue further. I tried copying over a couple sets of the Galaxy Nexus toro proprietary cdma/LTE drivers from here (https://developers.google.com/android/nexus/drivers?csw=1#toro) to no avail.

Then I went another route and checked out the dmesg/logcat.

dmesg | grep ril (in Android terminal emulator)
# or
adb logcat | grep ril (from a linux PC)

Output:

[ 44.044738] init: Warning! Service ril-daemon needs a SELinux domain defined; please fix!

[ 44.388610] type=1400 audit(946684841.953:6): avc: denied { execmem } for pid=147 comm="rild" scontext=u:r:init:s0 tcontext=u:r:init:s0

Trying to execute the rild daemon to restart it gives another "avc: denied {execute}" entry. I'll look into this some more, but I don't remember seeing these pop up in 4.3 or 4.4. Also, killing the rild daemon and restarting it generates the first error as well.

edit: Here's another "dmesg | grep rild" log after startup for good measure:

[ 44.594879] type=1400 audit(1415768902.125:6): avc: denied { execmem } for pid=147 comm="rild" scontext=u:r:rild:s0 tcontext=u:r:rild:s0 tclass=process
[ 44.767486] type=1400 audit(1415768902.296:7): avc: denied { write } for pid=192 comm="sh" name="switch" dev=sysfs ino=6983 scontext=u:r:rild:s0 tcontext=u:object_r:sysfs:s0 tclass=file
[ 47.320220] type=1400 audit(1415768904.851:11): avc: denied { write } for pid=147 comm="rild" name="control" dev=sysfs ino=7421 scontext=u:r:rild:s0 tcontext=u:object_r:sysfs:s0 tclass=file
[ 49.780456] type=1400 audit(1415768907.304:12): avc: denied { write } for pid=147 comm="rild" name="accept_ra_defrtr" dev=proc ino=5053 scontext=u:r:rild:s0 tcontext=u:object_r:proc_net:s0 tclass=file
[ 102.263244] type=1400 audit(1415768959.789:72): avc: denied { connectto } for pid=1586 comm="IILReceiver" path=00696D7364 scontext=u:r:platform_app:s0 tcontext=u:r:rild:s0 tclass=unix_stream_socket
[ 140.830291] type=1400 audit(1415768998.838:144): avc: denied { write } for pid=438 comm="rild" name="autoconf" dev=proc ino=28322 scontext=u:r:rild:s0 tcontext=u:object_r:proc_net:s0 tclass=file
[ 140.840454] avc: granted { set } for property=net.rmnet0.ipv6.pcscf0 scontext=u:r:rild:s0 tcontext=u:object_r:net_radio_prop:s0 tclass=property_service
[ 140.841033] avc: granted { set } for property=net.rmnet0.ipv6.pcscf1 scontext=u:r:rild:s0 tcontext=u:object_r:net_radio_prop:s0 tclass=property_service
[ 140.841461] avc: granted { set } for property=net.rmnet0.ipv6.pcscf2 scontext=u:r:rild:s0 tcontext=u:object_r:net_radio_prop:s0 tclass=property_service
[Samsung Galaxy Nexus] Dirty_Jerz:
The SELinux is running in permissive mode. You can verify by

#getenforce

I don't think the denials are actually denying anything. In permissive mode the avc denials are still logged for debugging purposes.

What I think is worth looking into are the radio logs.

#logcat -b radio

They throw an error about RIL_REQUEST_CDMA_SET_BROADCAST_CONFIG REQUEST_NOT_SUPPORTED

Another one that seems to be an issue is, after an airplane mode cycle, you get this:

D/use-Rlog/RLOG-RIL_BIP_STK ( 8016): SIM is not loaded from the card yet so send the TR currently unable to proces, SIM will again try after some time

I vaguely remember this being a problem with KitKat in the beginning. Will look into this.
[Samsung Galaxy Nexus] DBISGOD:
It seems google play services isn't working on the 5.0 ROM after I flash it and the gapps. Am I doing something wrong or is this a known issue?
[Samsung Galaxy Nexus] zzpianoman:
Google Play Services is included in the gapps package (PrebuiltGmsCore.apk). After you flash gapps in recovery and then reboot into the system, log in with your Google account and it will update Google Play Services if needed.
[Samsung Galaxy Nexus] DBISGOD:
How do you login? Store won't refresh, do I add/remove the google accounts?
[Samsung Galaxy Nexus] zzpianoman:
I have a feeling that whatever got radio working in KitKat will get it working again in Lollipop. The radio issue is really the only thing preventing this from being a usable daily driver. Everything else (important) seems to work. Even the screen off audio glitch that was prevalent in KitKat seems to have been fixed.

I did have an issue with a kernel wakelock (gps-lock) which I've resolved for the time being by manually releasing it using "echo gps-lock > /sys/power/wake_unlock". It seems to appear even when locations services are turned off. Not sure how or why this is triggered but after manually releasing it, phone goes to sleep. It's interesting now that I think about it because using that method to release wakelocks has never worked for kernel wakelocks.

---------- Post added at 04:14 AM ---------- Previous post was at 04:06 AM ----------

Add your account manually through Settings/Accounts, then open Play Store.

---------- Post added at 04:20 AM ---------- Previous post was at 04:14 AM ----------

If anyone is interested in AppOps I can confirm that this works on L:

https://github.com/theblixguy/AppOps/tree/master/apk
[Samsung Galaxy Nexus] MongolPup:
To every person that has posted in this thread about problems they've explored, things they've looked into, deeper issues they've discovered and potential solutions they've tried...I want to thank you.

I know sometimes writing long posts like those seems pointless but I've found them super educational and I bet others have too.
[Samsung Galaxy Nexus] zzpianoman:
Found something interesting today...

#logcat -b system -d

Shows this:

D/ConnectivityService( 451): NetworkAgentInfo [MOBILE (LTE) - 119] EVENT_NETWORK_INFO_CHANGED, going from null to CONNECTED
D/ConnectivityService( 451): Adding iface rmnet1 to network 119
D/ConnectivityService( 451): Setting MTU size: rmnet1, 1500
E/ConnectivityService( 451): exception in setMtu()java.lang.IllegalStateException: command '482 interface setmtu rmnet1 1500' failed with '400 482 Failed to get MTU (Invalid argument)'
D/ConnectivityService( 451): Adding Route [0.0.0.0/0 -> 100.76.189.1 rmnet1] to network 119
E/ConnectivityService( 451): Exception in addRoute for gateway: java.lang.IllegalStateException: command '483 network route add 119 rmnet1 0.0.0.0/0 100.76.189.1' failed with '400 483 addRoute() failed (No such process)'
D/ConnectivityService( 451): Adding Route [::/0 -> 2600:1001:b013:9af1::1 rmnet1] to network 119

It appears that ConnectivityService fails to add the routing for the default gateway on the modem interface.

root@toro:/ # ip route show
root@toro:/ #

As you can see, the kernel routing table is empty whereas on KitKat with mobile data connected, it shows like this:

shell@toro:/ # ip route show
default via 100.64.28.1 dev rmnet1
100.64.28.1 dev rmnet1 scope link
173.194.123.46 via 100.64.28.1 dev rmnet1

As far as I can tell, the radio logs are fairly consistent between KitKat and Lollipop, so this might just be a routing issue. You can clearly see that the gateway is set when I connect via wifi:

root@toro:/ # ip route show
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.4
root@toro:/ #

DNS is also set:

root@toro:/ # getprop | grep dns
[dhcp.wlan0.dns1]: [192.168.1.1]
[dhcp.wlan0.dns2]: []
[dhcp.wlan0.dns3]: []
[dhcp.wlan0.dns4]: []
[net.change]: [net.dns4]
[net.dns1]: [198.224.184.135]
[net.dns2]: [198.224.185.135]
[net.dns3]: [2001:4888:10:ff00:132:d::]
[net.dns4]: [2001:4888:11:ff00:137:d::]
root@toro:/ #

I think this routing issue might be the key to solving our data problems.
[Samsung Galaxy Nexus] RW-1:
Very nice find! I would agree.
[Samsung Galaxy Nexus] Dirty_Jerz:
I still think that the root cause is deeper. There won't be any routes set up unless the DCs are set up properly. Once the RIL and telephony are patched again, as they had to be for KitKat, then the kernel can establish the routes needed. It seems!s to be the whole CDMA debacle again. You can check it out by looking under cellular networks in settings-> wireless & networks->more (...) When you change to 4G preferred, nothing is updated in preferred network type. Also, if you look in the phone testing menu, the correct preferred network type overlay is not enumerated to the corresponding setting.

Edit: It looks like MWisBest has forked RIL and opt/telephony and is addressing this issue.
[Samsung Galaxy Nexus] 7175:
Can't wait for the next build.

Haven't seen cujo post in a while so here you go..
[Samsung Galaxy Nexus] zzpianoman:
I think you are right on this one because even after setting up the routing manually, it still showed up as having no internet connection. I remember doing some of my own modifications to the data connection tracker (in smali) to try to fix the 3g/LTE handoff issues back in the early days of KitKat on the Galaxy Nexus, but I wasn't paying close enough attention to learn what the developers did to get mobile data to work.
[Samsung Galaxy Nexus] Dirty_Jerz:
Heydenm315 over on CM's forum outlined them, at least from ShinyROM: http://forum.cyanogenmod.org/topic/98061-m9/#entry481820
[Samsung Galaxy Nexus] zzpianoman:
Yikes! I had no idea it was so involved! I really do appreciate everyone's hard work on this.
[Samsung Galaxy Nexus] Dirty_Jerz:
Got data working on 3g at least. I built last night using the (1/3), (2/3), and (3/3) ' bizarre ' commits and flashed. Just switched to 3G. Gonna try 4G now.

Edit: Ughhh, it worked for a second. WTF. Back to the logs...
[Samsung Galaxy Nexus] zzpianoman:
Found this in the logs:

D/ConnectivityService( 449): reportBadNetwork(NetworkAgentInfo [MOBILE (LTE) - 103]) by 10019

Apparently this function was introduced in API 21 so this might be worth looking in to.

http://developer.android.com/refere...ger.html#reportBadNetwork(android.net.Network)
[Samsung Galaxy Nexus] Dirty_Jerz:
Can you check if you see a ' Data Enabled' checkbox under cellular networks? I don't. All I have is 'Data Roaming' 'Prefered network type' and 'System Select'

nevermind. Looks like it was AOSP removed.
[Samsung Galaxy Nexus] zzpianoman:
Same here. I was thinking about that earlier, how there doesn't seem to be an option to enable or disable mobile data from the network settings menu. I tried "svc data enable" and "svc data disable" from the shell but that didn't seem to have any effect - all it seemed to do was cycle rmnet1 and clear the manual routing I had configured for the default gateway.

Edit: I checked settings.db from /data/data/com.android.providers.settings/databases and it appears that the field "mobile_data" is set to 1, indicating that it is enabled in the system.
[Samsung Galaxy Nexus] seriousia:
You can enable/disable the data from notification signal toggle.
[Samsung Galaxy Nexus] bagarwa:
After flashing the 20141109 zip of the rom and gapps, entire device is on its knees. Every Google app is crashing on its own, without even opening. And I'm logged out of the account, it seems. :confused:
[Samsung Galaxy Nexus] xsirex:
Dirty Flash? (not wiping User Data between rom changes)

But if your not wanting to lose your accounts then updating to 5.0 is probably not ready for you quite yet. This ROM is still working on getting a Cellular data connection working.
[Samsung Galaxy Nexus] bagarwa:
I should've also mentioned that I had previously flashed the first build of this 5.0 ROM and the previous basic gapps package (which didn't have the setup wizard), after a factory reset. I dirty flashed this second build on top of that.
[Samsung Galaxy Nexus] zzpianoman:
Just got LTE to work.....details to follow.
[Samsung Galaxy Nexus] Zer0_Cool:
NICE! Does 3g work as well, or just LTE?
[Samsung Galaxy Nexus] zzpianoman:
It "was" just LTE - no 3g - and now I'm thinking it may have just been a fluke. I'm trying now to figure out the exact sequence of events that led to acquiring the data connection.

Edit: No 3g or voice, I should have said....Another thing I noticed was that after I set the preferred network type to "LTE only" using the secret menu, the preferred network type under cellular network settings shows up as "4G (recommended)" which is strange, because the "LTE only" setting from the secret menu corresponds to the setting where you get ONLY LTE data and no voice calls so something is definitely weird.

Also from the logs, I can see that radio technology is being set to 14, which should correspond to the "LTE Only" option.

D/PHONE ( 812): [ServiceState] setDataRadioTechnology=14
D/CdmaSST ( 812): [CdmaLteSST] handlPollStateResultMessage: CdmaLteSST setDataRegState=0 regState=1 dataRadioTechnology=14
[Samsung Galaxy Nexus] barnesk9:
I can't get the Google sign in to work, everytime I go to enter my email it pauses after a few seconds and then closed, I've cleared app data and cache and reinstalled and it hasn't worked, any ideas?
[Samsung Galaxy Nexus] christianpeso:
Which version are you running? What date is it?
[Samsung Galaxy Nexus] RW-1:
Getting closer, I can feel it ..... Mobile Data! :)
[Samsung Galaxy Nexus] barnesk9:
I'm running 20141106 and the latest Gapps

---------- Post added at 12:45 PM ---------- Previous post was at 12:45 PM ----------

I'm running 20141106 and the latest Gapps
[Samsung Galaxy Nexus] christianpeso:
That is your problem. That version had known issues with the Browser and any app that might try to access it, such as Twitter apps and trying to login to your Google account/Play Store. Go the 1st page and download the latest build and latest gapps which both have the date of November 9th. That will get you logged into the Play Store and your account.
[Samsung Galaxy Nexus] MWisBest:
I've made some progress on the RIL, but still no data yet. The route thing is showing up now at least.
[Samsung Galaxy Nexus] zzpianoman:
That's great news! I'm still kind of frustrated that I was able to get a data connection, but then it went away and won't come back! Oh well, at least I have a sceenshot to remind me of better days.
[Samsung Galaxy Nexus] RW-1:
All good things .... I'm sure you guys will figure it out eventually.

Besides, I still bet you guys crack it before all those N6's finally reach their owners :)
[Samsung Galaxy Nexus] zzpianoman:
What's frustrating about it is that everything APPEARS to be connected - mobile DNS populates, gateways are routed, IP address assigned, proper interfaces are brought up but the phone doesn't think it has a data connection.
[Samsung Galaxy Nexus] Zer0_Cool:
I'm sure they will, especially considering mine won't be here until December :p
[Samsung Galaxy Nexus] RW-1:
I hear you on that front.

I know this will sound stupid, but what about proxies? I'm only going by PC's - I've seen after a malware attack that it's connected, has all it's info, etc. but one still cant browse - typically because the option for a proxy was checked for IE.

Could something similar be going on, or simply something else that makes anything looking for a mobile data connection get told by the OS that it doesn't have it? (Basically either the OS knows it's connected and this isn't relayed correctly to the apps requesting access or it is missing one thing to confirm ... yeah ... frustrating)
[Samsung Galaxy Nexus] ruccarucca:
data

this is going to sound strange but when the HTC One M8 on Verizon first got a GPE port ROM the only way the data would connect and work is if it thought it was roaming. we had to spoof a roaming connection even though it wasn't actually roaming for our device to access data at first. it had all the same problems we are having now but would only function on global and "roaming" at first if we wanted data.
[Samsung Galaxy Nexus] MWisBest:
What the ****. I seem to have some sort of half-assed 4G LTE connection:

[IMG="Lollipop Galaxy Nexus LTE Data"]http://i.imgur.com/xx9gEjw.png[/IMG]

Seems a lot of websites and apps have issues with it... I think it just only works with IPv6 addresses or something. But I guess it's progress.

Already racked up 50MB of data usage so far, so I don't think I'm dreaming...
[Samsung Galaxy Nexus] ruccarucca:
*Golf Clap* I hope you share in due time.
[Samsung Galaxy Nexus] HaRdC0r3:
Use sysctl to turn off ipv6 and see if it defaults to ipv4
[Samsung Galaxy Nexus] cgutman:
If you're on an IPv6 APN, perhaps CLAT isn't working.

http://dan.drown.org/android/clat/
[Samsung Galaxy Nexus] Dirty_Jerz:
root@toro:/ # echo 1 > /proc/sys/net/ipv6/conf/rmnet1/disable_ipv6

just kills the connection no fallback.

D/ClatdController( 134): starting clatd
D/ClatdController( 134): clatd started
I/clatd (18001): Starting clat version 1.3 on rmnet0 netid=110 mark=0xf006e
I/clatd (18001): Detecting NAT64 prefix from DNS...
E/clatd (18001): plat_prefix/dns(ipv4only.arpa) status = 7/No address associated with hostname
W/clatd (18001): dns64_detection -- error, sleeping for 1 seconds
I/clatd (18001): Detecting NAT64 prefix from DNS...
E/clatd (18001): plat_prefix/dns(ipv4only.arpa) status = 7/No address associated with hostname
W/clatd (18001): dns64_detection -- error, sleeping for 2 seconds
I/clatd (18001): Detecting NAT64 prefix from DNS...
E/clatd (18001): plat_prefix/dns(ipv4only.arpa) status = 7/No address associated with hostname
W/clatd (18001): dns64_detection -- error, sleeping for 4 seconds
I/clatd (18001): Detecting NAT64 prefix from DNS...
E/clatd (18001): plat_prefix/dns(ipv4only.arpa) status = 7/No address associated with hostname
W/clatd (18001): dns64_detection -- error, sleeping for 8 seconds
I/clatd (18001): Detecting NAT64 prefix from DNS...
E/clatd (18001): plat_prefix/dns(ipv4only.arpa) status = 7/No address associated with hostname
W/clatd (18001): dns64_detection -- error, sleeping for 16 seconds
[Samsung Galaxy Nexus] zzpianoman:
If you can bring up the APN list editor (I am using Nova Launcher with a custom shortcut to the APN list settings activity) you can modify the currently active APN to only use IPV4. I've already tried this in my troubleshooting procedure and the logs show that I can independently disable IPV4 or IPV6. Also, I believe rmnet0 is used for IPV6 and rmnet1 is for IPV4, so you could just ifconfig rmnet0 down, and see if that kills it.
[Samsung Galaxy Nexus] dekraan:
Hi all, i've flashed the lollipop ROM for my gnex yesterday after a factory reset and cache/dalvik wipe. It all seems to work, but i cannot connect to my mobile provider. Wifi works, but no cell. Is that a common problem? Do i need to wipe /system (and how to do that with clockwork recovery?)? I hope anyone can help because the ROM felt fantastic!
[Samsung Galaxy Nexus] Dirty_Jerz:
Error: Activity class {android.provider.Settings/android.provider.Settings.ACTION_APN_SETTINGS} does not exist.

What is the activity name?
[Samsung Galaxy Nexus] zzpianoman:
Settings$ApnSettingsActivity
[Samsung Galaxy Nexus] Dirty_Jerz:
No go. It just kept rtying to retry. The SST was only feeding it IPV4V6 connections.
[Samsung Galaxy Nexus] zzpianoman:
Do any of you guys know if it's possible to change a single framework file without having to rebuild the entire cache on boot?
[Samsung Galaxy Nexus] MWisBest:
Thing is, it's not an IPv6-only APN.

EDIT: Wait... can I MAKE it an IPv6-only APN? That could maybe do the trick...

EDIT2: Nope, but I fixed IPv4 anyway. :) New builds should be available later today, I'm about to go to class...
[Samsung Galaxy Nexus] blackout23:
Thanks a lot for your work and good luck with your studies!
[Samsung Galaxy Nexus] RW-1:
So it was related to ipv4 APN settings? I'd love details later when you post a build etc.

Enjoy class ...
[Samsung Galaxy Nexus] Dirty_Jerz:
Depends on which framework and its dependencies. All stale dependencies will be rebuilt on boot.
[Samsung Galaxy Nexus] zzpianoman:
Ah, I figured as much. It's just annoying to have to wait while the device rebuilds the entire cache after you make one small change in a single part of the framework. On older versions of Android, this wasn't so bad because dalvik would build relatively quickly but ART takes forever and appears to also rebuild the caches for user apps as well.
[Samsung Galaxy Nexus] Dirty_Jerz:
Agreed. Easiest/quickest is to run a lean ROM. Only essentials. Less to rebuild that way. Just make a nandroid and use a fresh install to test on.

Though there may be a way to prebuild cache on your buildbox. If there is a way, I'm not sure how to implement. That's a question for the ROM devs with serious buildroot-fu
[Samsung Galaxy Nexus] swordrune10:
I'll be flashing this tomorrow after work.. but I wanted to ask if ur interested in cm since they now have a KitKat manifest out?
[Samsung Galaxy Nexus] MWisBest:
I'm thinking about it... at the moment I'm kinda liking being just based on AOSP, it's the first time I've not had to worry about changes somebody else makes breaking my stuff! :laugh:
[Samsung Galaxy Nexus] sonic147862:
great so far

the only bugs is when I say "ok google" on the launcher the results have the black over them like in the stock browser. Otherwise this is a great ROM I have been using it since it came out. Thanks!

Also haven't had any freezes either! :D
[Samsung Galaxy Nexus] joeb3786:
Not sure if it's been mentioned in this thread or not, but I saw a tip in a thread on that other site about checking the "Don't keep activities" box under developer settings as a way to cut back on the random reboots. This, along with disabling all animations, has given me a totally reboot-free day. I was averaging 4-8 per day before following that advice! Also can confirm the *#*#4636#*#* fix for LTE, however if you do get a reboot this setting doesn't seem to stick and must be changed again (at least for me - but I'm on a different 4.4 build them this one)
[Samsung Galaxy Nexus] MWisBest:
Yeah Google Now is one of those things that uses the stock browser's rendering engine or whatever you want to call it. Maybe I can just revert whatever introduced that... *adds to To-Do List*

Glad to hear you're enjoying the ROM, thank you for your continued support!

The "Don't keep activities" thing just makes it so apps can't idle in the background and are instead closed instantly, I'm not sure how that would help except with maybe memory management issues in a kernel... hmm. Personally, I have animations enabled, haven't touched any mobile data settings... really, I haven't done anything different than I would with 4.3.x, and I haven't had any reboots for the last few builds. To each their own however, glad you're enjoying KitKat, even if it's not with FML. :highfive:
[Samsung Galaxy Nexus] :
i assume no luck yet with twrp yet? i may as well flash cwm,flash the rom, then reflash twrp after the rom is installed. want to know if its worth flashing though
[Samsung Galaxy Nexus] AirBoss24K:
I was happy to see in the changelog that attention was directed at the freezing issue - I can deal with the graphical shenanigans but having my phone freeze on me is a pain in the butt when I have a case and a finicky battery panel (I have a 3800mah sucker wedged back there). Just flashed your new 11-06 build, so we'll put it to the test tomorrow. Fingers crossed for a freeze-free day!

By the way, the previous build held my power consumption needs for a little over 12 hours - very heavy usage today. I took note that I had around 4 hours of screen on time (roughly 40% brightness) when my battery hit the 4% remaining threshold. I also lost probably close to 5-10% from a freeze I didn't notice right away. So I'm thinking in a 12 hour day on my 3800mah battery, I probably would have racked up 4.5 hours of screen time. Pretty damn good, imo!

For those of you wondering, the screen time consisted of texting, email, and a long study session using a flashcard application :cool:

Thanks for the timely update. I'm loving the ROM so far!