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

Root [ROM][4.0.4][BETA] AOKP ICS for Virgin Mobile and Sprint 10/3/2013

phenomx4

Android Expert
Recognized Developer
This is a beta release of AOKP for the Optimus Elite so please don't expect this to be 100% stable. You may get random reboots and lockups or you may not. Before flashing this rom I recommend you make a NAND backup just in case.



About: (taken from the aokp website.)

What is AOKP?

AOKP stands for Android Open Kang Project. It is a custom ROM distribution for several high-end Android devices. The name is a play on the word kang and AOSP (Android Open Source Project). The name was sort of a joke, but it just stuck, just like our infatuation with unicorns.
We fork the source code of Android that Google puts out in the open with every major version release, and we then add the magical unicorn bytes (read: we add some of the coolest features that are both useful and make your ROM awesome).
With AOKP, you can generally do a lot more with your device than what you could do with the original firmware that came installed on it.



What works:


  • Audio/speaker phone
  • Headset/headphones
  • Calls and texts
  • Touchscreen
  • Lights/brightness
  • Offline charging
  • External SD
  • Bluetooth
  • Wifi
  • Proximity sensor
  • Overclocking
  • Tethering using an app called "Wifi Tether for Root Users" from the play store with the settings used in F.A.Q below.
  • Mass storage
  • Camera


What's partially working:


  • Data (stuck on 1x but get 3g speeds.)
  • NFC ( NFC tags and google wallet are non functional.)
What's not working:


  • You tell me.


Issues:

  • you may have random reboots or lock ups or you may not.
  • Google Wallet doesn't work and opening it causes nfc to not work until you do a reboot. Will fix this soon.

Installation instructions:

To install this rom you must first have a custom recovery installed onto your phone.
You can learn how to do this here " http://androidforums.com/elite-all-things-root/620742-faq-guide-clockworkmod-optimus-elite.html"


  • 1. Download the appropriate rom for your phone and then Gapps. (Gapps is needed if you need to use google services such as Google Play.)
  • 2. You need to copy the downloaded rom and Gapps to your internal memory or your external memory.
  • 3. Boot into recovery.
  • 4. If you are coming from a Gingerbread rom you need to do a full wipe. (cache, davlik cache, data, and system.) If you are coming from an other ICS rom e.g CM9 then you just need to wipe cache and davlik cache.
  • 5. Select install zip from where ever you put the files onto. So if you put it on the external sd card you would pick "Install from SD Card".
  • 6. Install in the following order. "Rom and then Gapps"
  • 7. Reboot.
Please note that the first install will take some time ( About 3 to 5 minutes.)

F.A.Q

Q. What settings do I use to get tethering to work?
A.
Device-Profile: Generic ICS/JB (wlan0)
Change Setup-Method: WEXT (ad-hoc)
MSS clamping checked
Routing fix checked



Want to report a issue you are having with the rom? Then use getlogs.
[APP] GetLogs - Get dmesg, logcat, radio, etc with one click! - xda-developers

Will update this post later

Change Log
HTML:
10/3/2013
Added DSP Manager
Add separate headset and speaker volumes
MMS should be fixed.
Honeycomb lockscreen works well enough to use but it needs work.
Switched to Tiny RCU
Enabled Compaction
Enabled tun.ko to be built.

 09/29/2013

Fixed rotated camera preview 
fixed video recording 
fixed weather panel 
Always show 3G enabled 
Added fast charge support into kernel. 

09/28/2013 
 Initial release


Credits and thanks:
AOKP
Cyanogenmod
LG
Dorregaray
G60madman
Downthemachine

Giantpune
Starkraving

and everyone else I missed.


Gapps:

Goo.im Downloads - Downloading gapps-ics-20120429-signed.zip


Virgin Mobile:

Dev-Host - VMAOKPICSm3s-ota-eng.phenomx4.zip(10-3-2013) - The Ultimate Free File Hosting / File Sharing Service

Sprint:


Dev-Host - LSAOKPICSm3s-ota-eng.phenomx4(10-3-2013).zip - The Ultimate Free File Hosting / File Sharing Service

Screenshots:

Comming soon.

While donating is not required to use this rom it's always appreciated
Donations:

 
Sending text messages works but I can't send a picture message. It is just stuck on "sending "

I've re-produced this issue as well.

CatLog:
09-29 22:44:07.313 I/ActivityManager(264): Start proc com.android.mms for broadcast com.android.mms/.transaction.MmsSystemEventReceiver: pid=844 uid=10025 gids={3003, 1015}
09-29 22:44:23.457 I/ActivityManager(264): No longer want com.android.mms (pid 844): hidden #16
09-30 08:35:23.850 I/ActivityManager(264): START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.mms/.ui.ConversationList bnds=[224,282][298,364]} from pid 493
09-30 08:35:24.010 I/ActivityManager(264): Start proc com.android.mms for activity com.android.mms/.ui.ConversationList: pid=5596 uid=10025 gids={3003, 1015}
09-30 08:35:25.832 I/ActivityManager(264): START {cmp=com.android.mms/.ui.ComposeMessageActivity} from pid 5596
09-30 08:36:28.673 D/ConnectivityService(264): startUsingNetworkFeature reconnecting to 0: enableMMS
09-30 08:36:28.703 D/ConnectivityService(264): ConnectivityChange for mobile_mms: CONNECTED/CONNECTED
09-30 08:37:13.848 D/Mms (5596): [467] markAsRead: update read/seen for thread uri: content://mms-sms/conversations/1
09-30 08:37:28.732 D/ConnectivityService(264): stopUsingNetworkFeature: teardown net 0: enableMMS
09-30 08:37:28.782 D/ConnectivityService(264): ConnectivityChange for mobile_mms: DISCONNECTED/DISCONNECTED
09-30 08:39:58.180 I/ActivityManager(264): START {cmp=com.android.mms/.ui.ConversationList} from pid 5596
09-30 08:39:58.330 W/Mms/cache(5596): RecipientId 1 not in cache!
09-30 08:40:02.053 I/ActivityManager(264): START {dat=content://mms-sms/conversations/1 cmp=com.android.mms/.ui.ComposeMessageActivity} from pid 5596
09-30 08:40:02.254 D/Mms/compose(5596): [1] [initialize] savedInstanceState = null intent = Intent { dat=content://mms-sms/conversations/1 cmp=com.android.mms/.ui.ComposeMessageActivity } mConversation = [425-XXX-YYYY] (tid 1)
09-30 08:40:02.884 I/ActivityManager(264): Displayed com.android.mms/.ui.ComposeMessageActivity: +720ms
09-30 08:40:10.774 D/Mms (5596): [482] markAsRead: update read/seen for thread uri: content://mms-sms/conversations/1
09-30 08:56:46.968 I/ActivityManager(264): START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.mms/.ui.ConversationList bnds=[208,282][282,364]} from pid 493
09-30 08:57:47.287 I/ActivityManager(264): No longer want com.android.mms (pid 5596): hidden #16
09-30 08:57:47.367 W/InputDispatcher(264): channel '415c9400 com.android.mms/com.android.mms.ui.ConversationList (server)' ~ Consumer closed input channel or an error occurred. events=0x8
09-30 08:57:47.367 E/InputDispatcher(264): channel '415c9400 com.android.mms/com.android.mms.ui.ConversationList (server)' ~ Channel is unrecoverably broken and will be disposed!
09-30 08:57:47.367 W/InputDispatcher(264): Attempted to unregister already unregistered input channel '415c9400 com.android.mms/com.android.mms.ui.ConversationList (server)'
09-30 08:57:47.367 W/InputDispatcher(264): channel '40cb8d28 com.android.mms/com.android.mms.ui.ComposeMessageActivity (server)' ~ Consumer closed input channel or an error occurred. events=0x8
09-30 08:57:47.367 E/InputDispatcher(264): channel '40cb8d28 com.android.mms/com.android.mms.ui.ComposeMessageActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
09-30 08:57:47.367 W/InputDispatcher(264): Attempted to unregister already unregistered input channel '40cb8d28 com.android.mms/com.android.mms.ui.ComposeMessageActivity (server)'
09-30 08:57:47.367 I/WindowManager(264): WINDOW DIED Window{415c9400 com.android.mms/com.android.mms.ui.ConversationList paused=false}
09-30 08:57:47.367 I/WindowManager(264): WINDOW DIED Window{40cb8d28 com.android.mms/com.android.mms.ui.ComposeMessageActivity paused=false}
09-30 08:57:47.377 W/ActivityManager(264): Scheduling restart of crashed service com.android.mms/.transaction.TransactionService in 5000ms
09-30 08:58:10.469 I/ActivityManager(264): START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.mms/.ui.ConversationList bnds=[224,282][298,364]} from pid 493
09-30 08:58:10.499 I/ActivityManager(264): Start proc com.android.mms for activity com.android.mms/.ui.ComposeMessageActivity: pid=6358 uid=10025 gids={3003, 1015}
09-30 08:58:10.780 I/ActivityThread(6358): Pub mms_temp_file: com.android.mms.TempFileProvider
09-30 08:58:10.780 I/ActivityThread(6358): Pub com.android.mms.SuggestionsProvider: com.android.mms.SuggestionsProvider
09-30 08:58:10.790 V/MmsConfig(6358): mnc/mcc: 311490
09-30 08:58:10.790 V/MmsConfig(6358): tag: bool value: enabledMMS - true
09-30 08:58:10.790 V/MmsConfig(6358): tag: int value: maxMessageSize - 307200
09-30 08:58:10.790 V/MmsConfig(6358): tag: int value: maxImageHeight - 480
09-30 08:58:10.790 V/MmsConfig(6358): tag: int value: maxImageWidth - 640
09-30 08:58:10.790 V/MmsConfig(6358): tag: int value: defaultSMSMessagesPerThread - 500
09-30 08:58:10.790 V/MmsConfig(6358): tag: int value: defaultMMSMessagesPerThread - 50
09-30 08:58:10.790 V/MmsConfig(6358): tag: int value: minMessageCountPerThread - 10
09-30 08:58:10.790 V/MmsConfig(6358): tag: int value: maxMessageCountPerThread - 5000
09-30 08:58:10.790 V/MmsConfig(6358): tag: string value: uaProfUrl - http://www.google.com/oha/rdf/ua-profile-kila.xml
09-30 08:58:10.790 V/MmsConfig(6358): tag: int value: recipientLimit - -1
09-30 08:58:10.790 V/MmsConfig(6358): tag: int value: smsToMmsTextThreshold - 4
09-30 08:58:10.790 V/MmsConfig(6358): tag: bool value: enableMultipartSMS - true
09-30 08:58:10.790 V/MmsConfig(6358): tag: bool value: enableSplitSMS - true
09-30 08:58:10.800 V/MmsConfig(6358): tag: bool value: enableSlideDuration - true
09-30 08:58:10.800 V/MmsConfig(6358): tag: int value: maxMessageTextSize - -1
09-30 08:58:11.400 D/Mms/conv(6358): Conversation.get: created new conversation xxxxxxx
09-30 08:58:11.410 D/Mms/compose(6358): [1] [initialize] savedInstanceState = Bundle[{android:viewHierarchyState=Bundle[mParcelledData.dataSize=2640], recipients=425-XXX-YYYY}] intent = Intent { act=android.intent.action.VIEW dat=content://mms-sms/conversations/1 cmp=com.android.mms/.ui.ComposeMessageActivity } mConversation = [425-XXX-YYYY] (tid 1)
09-30 08:58:11.951 I/ActivityManager(264): Displayed com.android.mms/.ui.ComposeMessageActivity: +1s462ms
09-30 08:58:12.271 E/Mms (6358): [511] Tried to add duplicate Conversation to Cache for threadId: 1 new conv: [(425) XXX-YYYY] (tid 1)
09-30 08:58:33.584 V/TransactionSettings(6358): APN setting: MMSC: null looked for: null
09-30 08:58:33.594 D/ConnectivityService(264): startUsingNetworkFeature reconnecting to 0: enableMMS
09-30 08:58:41.690 D/ConnectivityService(264): ConnectivityChange for mobile_mms: CONNECTED/CONNECTED
09-30 08:58:43.061 D/Mms (6358): [527] markAsRead: update read/seen for thread uri: content://mms-sms/conversations/1
09-30 08:58:44.550 V/TransactionSettings(6358): APN setting: MMSC: null looked for: null
09-30 08:58:44.550 V/TransactionService(6358): empty MMSC url, bail
09-30 08:59:33.207 D/ConnectivityService(264): stopUsingNetworkFeature: teardown net 0: enableMMS
09-30 08:59:33.217 D/ConnectivityService(264): ConnectivityChange for mobile_mms: DISCONNECTED/DISCONNECTED
 
Great so far!

However, the only way to turn off the torch is to reboot the phone. The on/off toggle is broken.

CatLog:

09-30 09:14:48.133 E/GlobalActions(264): Adding TorchToggle
09-30 09:14:48.624 E/GlobalActions(264): Adding TorchToggle
09-30 09:14:48.854 I/ActivityManager(264): START {act=com.android.systemui.INTENT_TORCH_OFF flg=0x10000000 cmp=com.android.systemui/.Torch} from pid 264
09-30 09:14:48.924 I/Torch (336): onCreate
09-30 09:14:50.505 I/ActivityManager(264): START {act=com.android.systemui.INTENT_TORCH_ON flg=0x10000000 cmp=com.android.systemui/.Torch} from pid 264
09-30 09:14:50.536 I/Torch (336): onCreate
09-30 09:14:51.867 D/Torch (336): wakeLock is null, getting a new WakeLock
09-30 09:14:51.867 D/Torch (336): PowerManager acquired
09-30 09:14:51.867 D/Torch (336): WakeLock set
09-30 09:14:51.867 D/Torch (336): WakeLock acquired
09-30 09:14:52.247 I/ActivityManager(264): Displayed com.android.systemui/.Torch: +1s720ms (total +3s329ms)
09-30 09:14:55.320 E/GlobalActions(264): Adding TorchToggle
09-30 09:14:55.801 E/GlobalActions(264): Adding TorchToggle
09-30 09:14:56.161 I/ActivityManager(264): START {act=com.android.systemui.INTENT_TORCH_OFF flg=0x10000000 cmp=com.android.systemui/.Torch} from pid 264
09-30 09:14:56.341 I/Torch (336): Flash mode: off
09-30 09:14:56.341 I/Torch (336): Flash modes: [off, auto, on, torch]
09-30 09:14:57.172 I/ActivityManager(264): START {act=com.android.systemui.INTENT_TORCH_ON flg=0x10000000 cmp=com.android.systemui/.Torch} from pid 264
09-30 09:14:57.342 I/Torch (336): onCreate
09-30 09:14:57.462 E/Torch (336): Camera.open() failed: Fail to connect to camera service
09-30 09:14:57.462 D/Torch (336): Camera not Found!
09-30 09:14:57.582 W/System.err(336): at com.android.systemui.Torch.surfaceCreated(Torch.java:278)
09-30 09:14:57.632 I/ActivityManager(264): Displayed com.android.systemui/.Torch: +310ms
09-30 09:15:02.577 E/GlobalActions(264): Adding TorchToggle
09-30 09:15:03.068 E/GlobalActions(264): Adding TorchToggle
09-30 09:15:03.268 I/ActivityManager(264): START {act=com.android.systemui.INTENT_TORCH_OFF flg=0x10000000 cmp=com.android.systemui/.Torch} from pid 264
09-30 09:15:04.749 I/ActivityManager(264): START {act=com.android.systemui.INTENT_TORCH_ON flg=0x10000000 cmp=com.android.systemui/.Torch} from pid 264
09-30 09:15:04.890 I/Torch (336): onCreate
09-30 09:15:05.951 D/Torch (336): wakeLock is null, getting a new WakeLock
09-30 09:15:05.951 D/Torch (336): PowerManager acquired
09-30 09:15:05.951 D/Torch (336): WakeLock set
09-30 09:15:05.951 D/Torch (336): WakeLock acquired
09-30 09:15:06.061 I/ActivityManager(264): Displayed com.android.systemui/.Torch: +1s174ms
 
Can someone pull me the framework, mms apk from the CM9 9/17/2013 build also the build prop. I think I know what's wrong with mms.
 
It is. Using an encrypted text app off market called textsexure that allows you to manually input your mmsc , proxy and port works once you add the information. There is no apn present when you use voice dialer to "Open APNs"

I am familiar with that app and I suspected this is the problem with AOKP and MMS. Thanks for digging in!

I think this is it...
Generic Virgin settings:
<apn type="mms" apn="0" mnc="490" mcc="311" carrier="Virgin Mobile US" mmsport="81" mmsproxy="205.239.233.136" mmsc="http://mmsc.vmobl.com:8088/mms?" port=""/>
 
It is. Using an encrypted text app off market called textsexure that allows you to manually input your mmsc , proxy and port works once you add the information. There is no apn present when you use voice dialer to "Open APNs"

Hey can u share the market link to that app. I can't seem to find it ;)
 
uploadfromtaptalk1380569593484.jpg
uploadfromtaptalk1380569606984.jpg
uploadfromtaptalk1380569628487.jpg

Trying it again...
 
Back
Top Bottom