• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Official CM11 Nightlies

George55155 said:
What's the difference between the unofficial and official version of today and the newest nightly? (: I'd really like to go to the official version but I don't want to give up stability or my camera so is it safe to switch over? (:
Click to expand...
I have a bit more RAM free in my unofficial build. Other than that, not much. They're just doing cleanup of the KK code, afaik.
 
Neph81 said:
I have a bit more RAM free in my unofficial build. Other than that, not much. They're just doing cleanup of the KK code, afaik.
Click to expand...
Thanks, Neph. Do you know if your other patch(es) have been merged? I think you did something to fix the clock in recovery, right? (or did that get reverted?)

Anything else in your unofficial (other than your blood, sweat, and tears) that hasn't made it to a CM commit yet?
 
nathanhaywood said:
Thanks, Neph. Do you know if your other patch(es) have been merged? I think you did something to fix the clock in recovery, right? (or did that get reverted?)

Anything else in your unofficial (other than your blood, sweat, and tears) that hasn't made it to a CM commit yet?
Click to expand...


That was a fix with enabling the Real-Time Clock in the kernel. For some reason LG never saw fit to enable it in the source. I'm unsure if it was merged, you'd have to check the kernel source changes.
 
nathanhaywood said:
Thanks, Neph. Do you know if your other patch(es) have been merged? I think you did something to fix the clock in recovery, right? (or did that get reverted?)

Anything else in your unofficial (other than your blood, sweat, and tears) that hasn't made it to a CM commit yet?
Click to expand...
RMCC did his own fix for the time issue, but I had compile issues with it. I would assume that his fix works just as well as mine, but I have not run any official nightlies in a while, to test it.
 
I moved to the latest nightly (2/13) and ran my canary app, Grooveshark, which hasn't worked in some time and always displayed the LG symbol.

On this build it still fails and displays the LG logo, but it's for a very short instant before the screen blanks.

Everything else is working, still have the occasional freeze after a full charge and have to reboot after the unplug.
 
I just tried CyanDelta from the play store to update the latest nightly 2/26 to 3/01. Not to shabby, it's supposed to reduce download data.
 
Having reboot frequently while driving in the car. I want to record video on the road. I saw phone often reboot. In home reboot was rare. I think this conflict with CarDock feature in LG Spectrum. Here last_kmsg paste if this helpful. VS920 camera crash and rebooted - Pastebin.com

Edit: I did turn airplane mode on but still rebooting.
In log I see vibration messages - probably was LG LED Notification app.
In beginning after first reboot I started a stock camera app and it was photo mode. I switched to video and got crashed. Opened camera app again and can start video recording with delay. Then recorded for about minute and phone rebooted. After that second time reboot again. I copied last_kmsg to sdcard after third reboot.
FYI in fryo I remember annoying CarDock popup when I stayed in home and my car nearby.
version nightly 02/26/2014
 
Thank you for the log. This is something I haven't seen happen before, so I will see if I can recreate the issue on my builds.
 
Did wipe data and dalvik then flash nightly 11-20140309 two days ago. Did not occur random reboot. This works very well. Same delay after touched start record button.

Today on my phone got message. I need it report to Jira.
"No APN specified on the device."

Edit: Reported on Jira https://jira.cyanogenmod.org/browse/CYAN-3687?filter=-2
 

Attachments

  • Screenshot_2014-03-11-19-53-43 APN.jpg
    Screenshot_2014-03-11-19-53-43 APN.jpg
    26.9 KB · Views: 131
Weird. Either your phone is reporting an unknown APN number, or the APN file is missing/corrupt. Does this happen if you go back to an earlier nightly?

Edit:

Can you get me a copy of "adb logcat -v long" ? I see a lot of APN disconnects in the logcat you put on Jira, but it's missing info that I would need to troubleshoot your issue.
 
I wouldn't flash back just to get a log. Whenever you update to the next nightly, or if someone else runs into the same issue, is fine.
 
OK, so here's what I see in that list.
Code: 
7461
[ 03-12 01:39:32.546   613:  628 D/CountryDetector ]
7463
The first listener is added
7467
[ 03-12 01:39:32.566   758:  758 D/PhoneStatusBarPolicy ]
7469
updateSimState for subscription :0
7473
[ 03-12 01:39:32.566   758:  758 D/StatusBar.NetworkController ]
7475
In updateSimIcon simState= READY
7479
[ 03-12 01:39:32.596   758:  758 D/KeyguardUpdateMonitor ]
7481
ACTION_SIM_STATE_CHANGED intent received on sub = 0
7491
[ 03-12 01:39:32.676   758:  758 D/PhoneStatusBarPolicy ]
7493
updateSimState for subscription :0
7497
[ 03-12 01:39:32.686   758:  758 D/StatusBar.NetworkController ]
7499
In updateSimIcon simState= UNKNOWN
7503
[ 03-12 01:39:32.706   758:  758 D/KeyguardUpdateMonitor ]
7505
ACTION_SIM_STATE_CHANGED intent received on sub = 0
7509
[ 03-12 01:39:32.716   758:  758 D/KeyguardUpdateMonitor
That, along with all the network disconnects are before BOOT_COMPLETE, so I'm not concerned about those. Later in your log, it shows you are connected to VZWINTERNET, so it is reading your LTE card, from the looks of things.

Then we get near the end.
Code: 
[ 03-12 01:40:46.054  1137: 1137 V/TransactionSettings ]
28705
APN setting: MMSC: null looked for: current IS NOT NULL AND apn=?
28709
[ 03-12 01:40:46.054  1137: 1137 V/TransactionService ]
28711
   empty MMSC url, bail
28715
[ 03-12 01:40:46.074   758:  758 D/StatusBar.NetworkController ]
28717
updateConnectivity: intent=Intent { act=android.net.conn.CONNECTIVITY_CHANGE flg=0x4000010 (has extras) }
28721
[ 03-12 01:40:46.084   758:  758 D/StatusBar.NetworkController ]
28723
updateConnectivity: networkInfo=NetworkInfo: type: mobile[LTE], state: CONNECTED/CONNECTED, reason: connected, extra: ZWINTERNET, roaming: false, failover: false, isAvailable: true, isConnectedToProvisioningNetwork: false
28727
[ 03-12 01:40:46.094   758:  758 D/StatusBar.NetworkController ]
28729
updateConnectivity: connectionStatus=0
28733
[ 03-12 01:40:46.154   864:  930 D/TelephonyProvider ]
28735
Column apn id key is 'apn_id'
28739
[ 03-12 01:40:47.536  1137: 1137 E/RetryScheduler ]
28741
Response status is: 134
28745
[ 03-12 01:40:47.746   613:  628 D/ConnectivityService ]
28747
stopUsingNetworkFeature: teardown net 0: enableMMS
28751
[ 03-12 01:40:47.756  1137: 1137 V/TransactionService ]
28753
mms releaseWakeLock
28757
[ 03-12 01:40:47.826  1137: 1137 D/MmsSystemEventReceiver ]
28759
TYPE_MOBILE_MMS available = true, isConnected = true
28763
[ 03-12 01:40:47.846   795:  795 D/CMStats  ]
28765
Waiting for next sync : 23 hours
28769
[ 03-12 01:40:47.876   864:  864 D/PhoneApp ]
28771
mReceiver: ACTION_ANY_DATA_CONNECTION_STATE_CHANGED
28775
[ 03-12 01:40:47.876   864:  864 D/PhoneApp ]
28777
- state: DISCONNECTED
28781
[ 03-12 01:40:47.876   864:  864 D/PhoneApp ]
28783
- reason: dataDisabled
28787
[ 03-12 01:40:47.876   613:  613 D/MobileDataStateTracker ]
28789
mms: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=mms
28793
[ 03-12 01:40:47.876   613:  613 D/MobileDataStateTracker ]
28795
mms: Received state=DISCONNECTED, old=CONNECTED, reason=dataDisabled
28799
[ 03-12 01:40:47.876   613:  613 D/MobileDataStateTracker ]
28801
mms: setDetailed state, old =CONNECTED and new state=DISCONNECTED
28805
[ 03-12 01:40:47.876   613:  744 D/ConnectivityService ]
28807
ConnectivityChange for mobile_mms: DISCONNECTED/DISCONNECTED
28811
[ 03-12 01:40:47.896   864:  864 D/NotificationMgr ]
28813
hideDataDisconnectedRoaming()...
You're getting an unknown APN response and losing data, if I'm reading that correctly. Being as your LTE Card works on ICY Fusion, I'm thinking that the CM Team broke something in Telephony on one of the latest builds.

TDM:

Thoughts on this?
 
Neph81 said:
OK, so here's what I see in that list.
Code: 
7461
[ 03-12 01:39:32.546   613:  628 D/CountryDetector ]
7463
The first listener is added
7467
[ 03-12 01:39:32.566   758:  758 D/PhoneStatusBarPolicy ]
7469
updateSimState for subscription :0
7473
[ 03-12 01:39:32.566   758:  758 D/StatusBar.NetworkController ]
7475
In updateSimIcon simState= READY
7479
[ 03-12 01:39:32.596   758:  758 D/KeyguardUpdateMonitor ]
7481
ACTION_SIM_STATE_CHANGED intent received on sub = 0
7491
[ 03-12 01:39:32.676   758:  758 D/PhoneStatusBarPolicy ]
7493
updateSimState for subscription :0
7497
[ 03-12 01:39:32.686   758:  758 D/StatusBar.NetworkController ]
7499
In updateSimIcon simState= UNKNOWN
7503
[ 03-12 01:39:32.706   758:  758 D/KeyguardUpdateMonitor ]
7505
ACTION_SIM_STATE_CHANGED intent received on sub = 0
7509
[ 03-12 01:39:32.716   758:  758 D/KeyguardUpdateMonitor
That, along with all the network disconnects are before BOOT_COMPLETE, so I'm not concerned about those. Later in your log, it shows you are connected to VZWINTERNET, so it is reading your LTE card, from the looks of things.

Then we get near the end.
Code: 
[ 03-12 01:40:46.054  1137: 1137 V/TransactionSettings ]
28705
APN setting: MMSC: null looked for: current IS NOT NULL AND apn=?
28709
[ 03-12 01:40:46.054  1137: 1137 V/TransactionService ]
28711
   empty MMSC url, bail
28715
[ 03-12 01:40:46.074   758:  758 D/StatusBar.NetworkController ]
28717
updateConnectivity: intent=Intent { act=android.net.conn.CONNECTIVITY_CHANGE flg=0x4000010 (has extras) }
28721
[ 03-12 01:40:46.084   758:  758 D/StatusBar.NetworkController ]
28723
updateConnectivity: networkInfo=NetworkInfo: type: mobile[LTE], state: CONNECTED/CONNECTED, reason: connected, extra: ZWINTERNET, roaming: false, failover: false, isAvailable: true, isConnectedToProvisioningNetwork: false
28727
[ 03-12 01:40:46.094   758:  758 D/StatusBar.NetworkController ]
28729
updateConnectivity: connectionStatus=0
28733
[ 03-12 01:40:46.154   864:  930 D/TelephonyProvider ]
28735
Column apn id key is 'apn_id'
28739
[ 03-12 01:40:47.536  1137: 1137 E/RetryScheduler ]
28741
Response status is: 134
28745
[ 03-12 01:40:47.746   613:  628 D/ConnectivityService ]
28747
stopUsingNetworkFeature: teardown net 0: enableMMS
28751
[ 03-12 01:40:47.756  1137: 1137 V/TransactionService ]
28753
mms releaseWakeLock
28757
[ 03-12 01:40:47.826  1137: 1137 D/MmsSystemEventReceiver ]
28759
TYPE_MOBILE_MMS available = true, isConnected = true
28763
[ 03-12 01:40:47.846   795:  795 D/CMStats  ]
28765
Waiting for next sync : 23 hours
28769
[ 03-12 01:40:47.876   864:  864 D/PhoneApp ]
28771
mReceiver: ACTION_ANY_DATA_CONNECTION_STATE_CHANGED
28775
[ 03-12 01:40:47.876   864:  864 D/PhoneApp ]
28777
- state: DISCONNECTED
28781
[ 03-12 01:40:47.876   864:  864 D/PhoneApp ]
28783
- reason: dataDisabled
28787
[ 03-12 01:40:47.876   613:  613 D/MobileDataStateTracker ]
28789
mms: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=mms
28793
[ 03-12 01:40:47.876   613:  613 D/MobileDataStateTracker ]
28795
mms: Received state=DISCONNECTED, old=CONNECTED, reason=dataDisabled
28799
[ 03-12 01:40:47.876   613:  613 D/MobileDataStateTracker ]
28801
mms: setDetailed state, old =CONNECTED and new state=DISCONNECTED
28805
[ 03-12 01:40:47.876   613:  744 D/ConnectivityService ]
28807
ConnectivityChange for mobile_mms: DISCONNECTED/DISCONNECTED
28811
[ 03-12 01:40:47.896   864:  864 D/NotificationMgr ]
28813
hideDataDisconnectedRoaming()...
You're getting an unknown APN response and losing data, if I'm reading that correctly. Being as your LTE Card works on ICY Fusion, I'm thinking that the CM Team broke something in Telephony on one of the latest builds.

TDM:

Thoughts on this?
Click to expand...

I'm not really a radio expert and I don't have vzw service to test with, so I'm afraid I can't be much help here.
 
Hello, seem my WiFi is broken too, couldnt be able to switch it on. Rolled back to older version still couldnt turn wifi on. Reboot several times still no luck. I just formatted and installed clean still no Wifi. How can I get WiFi working? I did everything no luck. Am on LTE (thank god am on grandfather plan) My girlfriend have same phone, hers WiFi working fine, we're on same verison (nightly 3/22/13) Seem my WiFi is broken? I Hope to get WiFi fix soon.
 
4.4.3 should be minor changes, so I do not see why not. 4.5.0 should be easy enough as well. 5.0 may be a bit of a headache as we're behind on getting some core issues cleared up.
 
You must log in or register to reply here.
Back
Top Bottom