[ROM][6.0.1][OFFICIAL] OmniROM

[musical_chairs]

Builds can be found at: http://dl.omnirom.org/toroplus/

This OP was shamelessly copied from the official maguro thread: http://forum.xda-developers.com/galaxy-nexus/development/rom-omnirom-04-16-t3360596

-----------------------------------------------------------------------------------------------------------------------

Google Apps can be found at http://opengapps.org/?api=6.0&variant=nano - beware that if you choose OpenGApps, only the nano version will fit! Also, starting from M, it's recommended to install gapps before the initial boot so the permissions are properly set up.

Bugs:
- Sometimes, quiet speaker pop sounds can be heard at the beginning and/or end of some audio streams (ie. touch sounds - the workaround is to disable them). For some reason, this isn't affecting everyone.

FAQ:
Does this ROM has CMA?
- Yes!

Does this ROM supports F2FS?
- Yes, on /data.

Does this ROM uses DDK 1.9?
- Yes, with all the camera issues (ie. pink lines, rare crashes) resolved.

Why does the initial boot take so long, and where are my live wallpapers?!
- To make room on the system partition for the (bigger) M gapps packages, I had to sacrifice dexpreopt and the live wallpapers. This can result in pretty long initial boots or upgrade boots, and dexpreopt might run during the first time setup wizard as well, slowing down the system for an additional couple minutes.

XDA:DevDB Information
[ROM][6.0.1][OFFICIAL] OmniROM, ROM for the Samsung Galaxy Nexus

Contributors
musical_chairs, Ziyan
Source Code: https://github.com/omnirom/

ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: OmniROM

Version Information
Status: Nightly

Created 2016-07-31
Last Updated 2016-08-03

 

[musical_chairs]

Please test! We would like to turn on official nightlies soon.

Soon we will have more ROMs that users for this phone.

 

[Ckpe4]

Great!
Can we expect for a official TWRP builds?
As far as I know, they must be based on omni, and if there will be official omni nightlies, it should not be a problem.

 

[musical_chairs]

Great!
Can we expect for a official TWRP builds?
As far as I know, they must be based on omni, and if there will be official omni nightlies, it should not be a problem.

That's the whole point of this exercise.

 

[Max Frost]

I'll give it a shot and see how it does . I've been running 4.4.4 lately since LTE came to our area . I haven't had any luck getting LTE up on Lollipop or MM roms for this device . Does Omni use their own device tree or CM's ?

 

[musical_chairs]

I'll give it a shot and see how it does . I've been running 4.4.4 lately since LTE came to our area . I haven't had any luck getting LTE up on Lollipop or MM roms for this device . Does Omni use their own device tree or CM's ?

Omni uses their own source code, including device trees and vendor trees. I did the bringup on both of those, so I would be surprised if LTE works. The telephony stack is a good bit different that cm's, though, so who knows?

 

[musical_chairs]

https://gerrit.omnirom.org/#/c/18747/

 

[Max Frost]

https://gerrit.omnirom.org/#/c/18747/

Installed Omni today . Seems fast and snappy . I'm not in an LTE area today but will be soon . Is there no way to install themes on Omni ? I'd really like to customize it . Am I overlooking something ? Thanks .

 

[Cardcaptor_RLH85]

https://gerrit.omnirom.org/#/c/18747/

So, I am in a 4G area, and I've switched my preferred network from 3G/CDMA to 4G/LTE but, I'm not getting a connection. What information do you need to help diagnose this?

EDIT: Is the device encryption in OmniROM decryptable by TWRP? I want to enable device encryption but, I still need to be able to update my device and the last time I did it (on CM 12.1) TWRP couldn't decrypt my partitions so it couldn't actually update my device.

 

[tomm1e]

So, I am in a 4G area, and I've switched my preferred network from 3G/CDMA to 4G/LTE but, I'm not getting a connection. What information do you need to help diagnose this?

If you have the debugging tools installed on your PC, save the radio log after it fails to connect to 4G:
adb logcat -b radio > radiofail.log

Or you can install the CatLog app from Play store, but root is required to read the logs, in CatLog go to Settings (bottom right menu button on app, under "More"), and in Log Buffers make sure only Radio is checked. These logs can get HUGE so best way to take a clean log snapshot is set the preferred network mode to 4G/LTE, reboot the phone, then save the logs after a few minutes of running

The most repeated error in the logs:

08-09 23:46:22.401 E/use-Rlog/RLOG-RIL[C](256): findApnInfo() no apns in apn_info
08-09 23:46:22.401 E/use-Rlog/RLOG-RIL[C](256): findApnInfo() no apns in apn_info
08-09 23:46:22.401 E/use-Rlog/RLOG-RIL[C](256): getAttachCid(): Unable to find attach apn info

Wild guesses:
- Internal problem with loading the APN during 4G and not necessarily a missing/misconfigured APN? (although 3G APNs work)
- Android 5.0+ RIL Library / Kernel incompatible with the toroplus' LTE radio, due to some change in code?

On 4.4, when Preferred network was set to LTE/CDMA auto, if LTE was out of range it would fall back to 3G, I think that's what eHRPD network is for, to switch between 4G/3G.
On 5.0+, it just gets stuck trying to connect to LTE, the network ends up showing either eHRPD or 1xRTT, and seems like it retries over and over, instead of stopping and connecting to 3G, you can feel the performance of the phone drop when it's trying to connect to LTE, some function keeps running in the background

 

[Roman20]

I install this rom today but a couldn't receive text message, when i tried to authenticate my Gmail i never get the text message notification. when i change back the rom to cyanogenmod all notification arrive to my phone. i send a text message from another phone too and it never arrive.

 

[Cardcaptor_RLH85]

If you have the debugging tools installed on your PC, save the radio log after it fails to connect to 4G:
adb logcat -b radio > radiofail.log

Or you can install the CatLog app from Play store, but root is required to read the logs, in CatLog go to Settings (bottom right menu button on app, under "More"), and in Log Buffers make sure only Radio is checked. These logs can get HUGE so best way to take a clean log snapshot is set the preferred network mode to 4G/LTE, reboot the phone, then save the logs after a few minutes of running

The most repeated error in the logs:

08-09 23:46:22.401 E/use-Rlog/RLOG-RIL[C](256): findApnInfo() no apns in apn_info
08-09 23:46:22.401 E/use-Rlog/RLOG-RIL[C](256): findApnInfo() no apns in apn_info
08-09 23:46:22.401 E/use-Rlog/RLOG-RIL[C](256): getAttachCid(): Unable to find attach apn info

Wild guesses:
- Internal problem with loading the APN during 4G and not necessarily a missing/misconfigured APN? (although 3G APNs work)
- Android 5.0+ RIL Library / Kernel incompatible with the toroplus' LTE radio, due to some change in code?

On 4.4, when Preferred network was set to LTE/CDMA auto, if LTE was out of range it would fall back to 3G, I think that's what eHRPD network is for, to switch between 4G/3G.
On 5.0+, it just gets stuck trying to connect to LTE, the network ends up showing either eHRPD or 1xRTT, and seems like it retries over and over, instead of stopping and connecting to 3G, you can feel the performance of the phone drop when it's trying to connect to LTE, some function keeps running in the background

So, here's a log from a few minutes of being unable to connect to 4G. It ends with me receiving a phone call which, of course, ended my testing cycle. Tell me if you need a longer sample. Also, this is using yesterday's (2016-08-09) nightly, if that changes anything.

 

[musical_chairs]

The most repeated error in the logs:

08-09 23:46:22.401 E/use-Rlog/RLOG-RIL[C](256): findApnInfo() no apns in apn_info
08-09 23:46:22.401 E/use-Rlog/RLOG-RIL[C](256): findApnInfo() no apns in apn_info
08-09 23:46:22.401 E/use-Rlog/RLOG-RIL[C](256): getAttachCid(): Unable to find attach apn info

Wild guesses:
- Internal problem with loading the APN during 4G and not necessarily a missing/misconfigured APN? (although 3G APNs work)
- Android 5.0+ RIL Library / Kernel incompatible with the toroplus' LTE radio, due to some change in code?

Both are realistic possibilities I think. I know on toro, we need to use older APNs - although there, data won't connect at all with the stock APNs. I'm used to seeing the logs filled with APN info, it's strange that it totally fails to load any APNs at all. I highly doubt the kernel is to blame, but there have been plenty of changes in the RIL code since 4.4.

So, here's a log from a few minutes of being unable to connect to 4G. It ends with me receiving a phone call which, of course, ended my testing cycle. Tell me if you need a longer sample. Also, this is using yesterday's (2016-08-09) nightly, if that changes anything.

That log should be long enough, it looks like your phone got bored and quit trying about two minutes before you got your phone call. In addition to the log snippet posted by socialentry, I find this sequence interesting:

08-10 19:23:24.232 1088 1088 D DCT : [0]setInitialApn: defaultApnSetting=[ApnSettingV3] null, 0, null, null, null, null, null, null, null, 3, default | mms | supl | hipri | fota | ims | cbs, IP, IP, true, 0, 0, 0, false, 0, 0, 0, 0, ,
08-10 19:23:24.232 1088 1088 D RILJ : Set RIL_REQUEST_SET_INITIAL_ATTACH_APN [SUB0]
08-10 19:23:24.232 1088 1088 D RILJ : [3770]> RIL_REQUEST_SET_INITIAL_ATTACH_APN, apn:null, protocol:IP, authType:3, username:null, password:null [SUB0]
08-10 19:23:24.242 266 299 D secril-shim: onRequestShim: got request RIL_REQUEST_SET_INITIAL_ATTACH_APN: forwarded to RIL.
08-10 19:23:24.242 266 299 E use-Rlog/RLOG-RIL[C]: CreateAndPushRequest CreateRequest() Failed.

I'd venture to guess that the APN info failing to appear is a problem, though whether it is the main problem or just a result of something going wrong earlier in the chain, I don't know.

 

[Max Frost]

If you have the debugging tools installed on your PC, save the radio log after it fails to connect to 4G:
adb logcat -b radio > radiofail.log

Or you can install the CatLog app from Play store, but root is required to read the logs, in CatLog go to Settings (bottom right menu button on app, under "More"), and in Log Buffers make sure only Radio is checked. These logs can get HUGE so best way to take a clean log snapshot is set the preferred network mode to 4G/LTE, reboot the phone, then save the logs after a few minutes of running

The most repeated error in the logs:

08-09 23:46:22.401 E/use-Rlog/RLOG-RIL[C](256): findApnInfo() no apns in apn_info
08-09 23:46:22.401 E/use-Rlog/RLOG-RIL[C](256): findApnInfo() no apns in apn_info
08-09 23:46:22.401 E/use-Rlog/RLOG-RIL[C](256): getAttachCid(): Unable to find attach apn info

Wild guesses:
- Internal problem with loading the APN during 4G and not necessarily a missing/misconfigured APN? (although 3G APNs work)
- Android 5.0+ RIL Library / Kernel incompatible with the toroplus' LTE radio, due to some change in code?

On 4.4, when Preferred network was set to LTE/CDMA auto, if LTE was out of range it would fall back to 3G, I think that's what eHRPD network is for, to switch between 4G/3G.
On 5.0+, it just gets stuck trying to connect to LTE, the network ends up showing either eHRPD or 1xRTT, and seems like it retries over and over, instead of stopping and connecting to 3G, you can feel the performance of the phone drop when it's trying to connect to LTE, some function keeps running in the background

Great post and it's the same with all the L and M roms . I feel like it's so close to being there . The sprint variant is the only one not getting LTE , right ?

 

[tomm1e]

Great post and it's the same with all the L and M roms . I feel like it's so close to being there . The sprint variant is the only one not getting LTE , right ?

Correct, users reporting LTE working on verizon's toro

I've attached some radio logs, maybe they are overkill, although the 6.0.1 logs were not in a strong LTE area hopefully it will help explain why it's not falling back to 3G if 4G fails?

On 6.0.1 logs, I've used the 4.4 APN that was working with LTE, and I deleted the OTA sprint APN, sometimes it was selected as default apn. Once I can get in a stronger LTE area I'll post new logs.

 

[tomm1e]

Today I replaced the default apns-conf.xml (attached) in /system/etc with the CM11 apns file, went to Access Point Names, and "Reset to default", now I can switch between 3G and 4G in the menu. However, when I select 4G it successfully connects to the eHRPD network to 3G if theres no 4G (takes about 30 seconds), but the 3G icon has the exclamation point, and it says Network is unreachable

CM11 APN settings:

<apn carrier="Sprint" mcc="310" mnc="120" apn="Sprint" user="Sprint" server="*" type="mms" password="*" mmsc="http://mms.sprintpcs.com" mmsproxy="68.28.31.7" mmsport="80" authtype="3"/>
<apn carrier="Sprint LTE ota" mcc="310" mnc="120" apn="otasn" type="fota" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="14" />
<apn carrier="Sprint EHRPD ota" mcc="310" mnc="120" apn="otasn" type="fota" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="13" />
<apn carrier="Sprint LTE internet" mcc="310" mnc="120" apn="n.ispsn" type="default,mms,supl,hipri" mmsc="http://mms.sprintpcs.com" mmsproxy="68.28.31.7" mmsport="80" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="14" />
<apn carrier="Sprint EHRPD internet" mcc="310" mnc="120" apn="n.ispsn" type="default,mms,supl,hipri" mmsc="http://mms.sprintpcs.com" mmsproxy="68.28.31.7" mmsport="80" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="13" />

Old APN settings:

<apn carrier="Sprint" mcc="310" mnc="120" apn="sprint" type="default,supl,mms,ims,cbs" mmsc="http://mms.sprintpcs.com" mmsproxy="68.28.31.7" mmsport="80" bearer_bitmask="4|5|6|7|8|12" /> <!-- bearer 4, 5, 6, 7, 8, 12 -->
<apn carrier="Sprint" mcc="310" mnc="120" apn="sprint" type="default,supl,mms,ims,cbs,dun" mmsc="http://mms.sprintpcs.com" mmsproxy="68.28.31.7" mmsport="80"bearer_bitmask="4|5|6|7|8|12" profile_id="1" />
<apn carrier="SPCS Global" mcc="310" mnc="120" apn="cinet.spcs" mmsc="http://mms.sprintpcs.com" mmsproxy="68.28.31.7" mmsport="80" type="default,supl,mms,dun" bearer_bitmask="1|2|3|9|10|11|15|16" />
<apn carrier="Sprint CdmaNai" mcc="312" mnc="530" mmsproxy="68.28.31.7" mmsport="80" mmsc="http://mms.sprintpcs.com" authtype="3" type="default,mms" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer_bitmask="6" />
<apn carrier="Sprint" mcc="312" mnc="530" apn="cinet.spcs" user="none" server="*" password="none" mmsproxy="68.28.31.7" mmsport="80" mmsc="http://mms.sprintpcs.com" type="default,mms" bearer_bitmask="1|2|3|9|10|11|15|16" />
<apn carrier="Sprint APN" mcc="316" mnc="010" apn="cinet.spcs" user="none" server="*" password="none" mmsproxy="68.28.31.7" mmsport="80" mmsc="http://mms.sprintpcs.com" type="default" />

Deleted:

<apn carrier="OTA" mcc="310" mnc="120" apn="otasn" type="fota,ia" protocol="IPV4V6" user="null" password="null" />

 

[musical_chairs]

Today I replaced the default apns-conf.xml (attached) in /system/etc with the CM11 apns file, went to Access Point Names, and "Reset to default", now I can switch between 3G and 4G in the menu. However, when I select 4G it successfully connects to the eHRPD network to 3G if theres no 4G (takes about 30 seconds), but the 3G icon has the exclamation point, and it says Network is unreachable.

Interesing, so it's something in the apns that is causing them to fail to load when 4G is selected? Maybe the bearer is the issue. I don't think our ril's like the bearer_bitmask part that was added in 6.0. That wouldn't explain why 4G fails in 5.1, though there have been some reverse-engineering ril blob updates for 6.0, so it's not out of the realm of possibility that we could get things working on 6.0 and the fix may not work on 5.1.

Some little ideas to try:
- Try setting the protocol to IPV4 only - obviously the attempts at IPV6 aren't going well in your log.
- Try deleting "default" from the 'Type' field in the Sprint LTE internet apn.
- Try deleting "bearer" from the eHRPD apn. (I got that idea from here: https://github.com/CyanogenMod/android_vendor_cm/commit/0c80c8c3e7bb4224cecc7a1ee579e60ea1a69079)

 

[tomm1e]

So I renamed n.ispsn back to sprint

<apn carrier="Sprint" mcc="310" mnc="120" apn="Sprint" user="Sprint" server="*" type="mms" password="*" mmsc="http://mms.sprintpcs.com" mmsproxy="68.28.31.7" mmsport="80" authtype="3"/>
<apn carrier="Sprint LTE ota" mcc="310" mnc="120" apn="otasn" type="fota" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="14" />
<apn carrier="Sprint EHRPD ota" mcc="310" mnc="120" apn="otasn" type="fota" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="13" />
<apn carrier="Sprint LTE internet" mcc="310" mnc="120" apn="sprint" type="default,mms,supl,hipri" mmsc="http://mms.sprintpcs.com" mmsproxy="68.28.31.7" mmsport="80" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="14" />
<apn carrier="Sprint EHRPD internet" mcc="310" mnc="120" apn="sprint" type="default,mms,supl,hipri" mmsc="http://mms.sprintpcs.com" mmsproxy="68.28.31.7" mmsport="80" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="13" />

Now the eHRPD network transfers to the EvDO-A network successfully when preferred network type is set to 4G/LTE. I have not tested in a LTE area though.

 

[tomm1e]

Well, I had a few minutes in a LTE area, The LTE apn wasn't working, so I renamed the apn back to n.ispsn and set the "LTE only" network setting, it immediately showed 4G icon but with the exclamation point Then when I removed "default" from the types, it wouldn't show 4G anymore, only a bare icon. I didn't have time to remove the bearer in the file but next time I will try it.

 

[musical_chairs]

Well, I had a few minutes in a LTE area, The LTE apn wasn't working, so I renamed the apn back to n.ispsn and set the "LTE only" network setting, it immediately showed 4G icon but with the exclamation point Then when I removed "default" from the types, it wouldn't show 4G anymore, only a bare icon. I didn't have time to remove the bearer in the file but next time I will try it.

It shows that it's connected:
08-12 23:43:01.820 D/CDMALTEPhone(1017): getDataConnectionState apnType=default ret=CONNECTED

Also looks like a route is set up:
08-12 23:43:01.772 D/DC-1 (1017): REQ_GET_LINK_PROPERTIES linkProperties{InterfaceName: rmnet1 LinkAddresses: [29.234.83.179/32,] Routes: [0.0.0.0/0 -> 29.234.83.1 rmnet1,] DnsAddresses: [66.1.68.132,66.1.64.132,] Domains: null MTU: 1422 TcpBufferSizes: 524288,1048576,2097152,262144,524288,1048576}

For reference, the equivalent line on toro with 4G connected looks like this:
08-13 06:26:34.958 1271 1421 D DC-2 : REQ_GET_LINK_PROPERTIES linkProperties{InterfaceName: rmnet1 LinkAddresses: [100.111.33.101/32,2600:1002:b004:65eb:0:5b:c4bb:d601/64,] Routes: [0.0.0.0/0 -> 100.111.33.1 rmnet1,::/0 -> 2600:1002:b004:65eb::1 rmnet1,] DnsAddresses: [198.224.188.236,198.224.189.236,2001:4888:15:ff00:194:d::,2001:4888:14:ff00:196:d::,] Domains: null MTU: 1500 TcpBufferSizes: 524288,1048576,2097152,262144,524288,1048576}

Thanks for your work on this!